[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Daniel van Vugt]

** Description changed:

+ [Impact]
+ 
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...
  
  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.
  
- I would be good if it would remember this choice so that I have
- to do it only once.
+ [Test Case]
  
- Or maybe (if that is technically possible)
- just output on both output devices by default - this would be
- even more user friendly for newbies who will have a hard time
- finding the right place to change this (or maybe have UI in the
- volume slider to select outputs if there are more than one?
- But anyway, my immediate concern is that it should just remember
- my choice :)
+ 0. Plug in a monitor that supports HDMI audio (one that appears in your
+ Settings>Sound)
  
- Please let me know if I can provide more information. Happy to
- dig into code if needed but I will need some pointers.
+ 1. Log out and in again.
  
- ---
+ Verify the default audio device in Settings is still speakers or
+ headphones. Not the monitor's HDMI audio device.
  
- WORKAROUND
+ [Regression Potential]
+ 
+ Low. The fix proposed just reverts to the same code used in PulseAudio
+ 12 and earlier. It has also been released and verified on focal already.
+ 
+ [Workaround]
  
  Comment out:
  
  load-module module-switch-on-port-available
  load-module module-switch-on-connect
  
  from /etc/pulse/default.pa

** Tags added: focal

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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

[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Daniel van Vugt]

Yes coming soon :)

https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/commit/?h=ubuntu-
eoan=9eb759d419b5d2302bd1376e88c621381358509e

** Patch added: "pulseaudio_13.0-1ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570/+attachment/5313577/+files/pulseaudio_13.0-1ubuntu1.1.debdiff

** Changed in: pulseaudio (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Committed
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  Low. The fix proposed just reverts to the same code used in PulseAudio
  12 and earlier. It has also been released and verified on focal
  already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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

[Desktop-packages] [Bug 1855893] Re: Properly let PCM leave suspended state when hardware doesn't support PCM resume

[Daniel van Vugt]

Also please provide links to upstream changes/bugs in the patch, and/or
here.

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

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, 
we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB 
dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to 
make device leave suspended state. This patch defaults to use snd_pcm_drop() to 
achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change 
intended. I also don't find any regression during some smoke test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855893/+subscriptions

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

[Desktop-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Daniel van Vugt]

** Changed in: pulseaudio (Ubuntu Eoan)
   Status: Triaged => In Progress

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  In Progress
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

  ---

  WORKAROUND

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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

[Desktop-packages] [Bug 1855893] Re: Properly let PCM leave suspended state when hardware doesn't support PCM resume

[Daniel van Vugt]

I just noticed the above patch. Now added to git:

https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/log/?h=ubuntu-
bionic

Please remember to put proposed changes in git so everyone is working
with the same source.

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

Title:
  Properly let PCM leave suspended state when hardware doesn't support
  PCM resume

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  [Impact]
  Headset Mic plugged into Dell WD19TB dock stops working after suspend/resume.

  [Fix]
  According to alia-lib's document, to make PCM properly leave suspended state, 
we only use snd_pcm_resume() if hardware support PCM resume.
  For hardware that doesn't support PCM resume, like snd-usb-audio on WD19TB 
dock, we should use snd_pcm_prepare(), snd_pcm_drop() or snd_pcm_drain() to 
make device leave suspended state. This patch defaults to use snd_pcm_drop() to 
achieve the goal.

  [Test]
  1. See if microphone on snd-usb-audio works in gnome-control-center/cheese.
  2. Suspend/resume.
  3. See if microphone still works in those apps.
  I can the issue is fixed after each suspend/resume cycle.

  [Regression Potential]
  Low. This fix makes PCM suspend/resume more reliable. No functional change 
intended. I also don't find any regression during some smoke test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1855893/+subscriptions

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

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

[Khaled El Mously]

** Changed in: linux-restricted-modules (Ubuntu Eoan)
   Status: In Progress => Fix Committed

** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

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

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-restricted-modules source package in Eoan:
  Fix Committed
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

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

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

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

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1828664] Re: [snap] Broken link in theme directory

[Launchpad Bug Tracker]

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

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

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

Title:
  [snap] Broken link in theme directory

Status in gnome-characters package in Ubuntu:
  Confirmed

Bug description:
  Reproduce steps
  ---
  1. $ snap install gnome-characters communitheme
  2. logoff and select communitheme session at the greeter (probably needs a 
reload of GDM or reboot, I'm running the wayland session but it also happened 
of X)
  3. $ snap run gnome-characters

  Affected snaps:
  gnome-characters
  gnome-calculator
  gnome-logs
  gnome-system-monitor
  libreoffice
  evince
  gnome-contacts
  eog

  Symptoms
  
  I'm using the communitheme and gnome-characters snap on Ubuntu 18.04 which 
broke at some point about two month ago. Screenshots are here: 
https://askubuntu.com/q/1142291/40581

  I found that ~/snap/gnome-characters/current/themes is a broken link
  even when removing the respective snap folder for the app, removing
  and then reinstalling the gnome-characters snap. This has worked
  before, please take a look at this.

  In the meantime I fixed this with the following commands, according
  the the error message:

  rm ~/snap/gnome-characters/current/.themes
  cp -av /snap/communitheme/current/share/themes 
~/snap/gnome-characters/current/.themes

  Version
  ---
  ```
  $ snap info {gnome-characters,communitheme} | grep -vE 
"^(summary|license|contact|description|commands):"
  name:  gnome-characters
  publisher: Canonical*
    Characters is a simple utility application to find and
    insert unusual characters.
    - gnome-characters
  snap-id:  qJcS3UjpF9AMJKWAiKwA5EWbm0y6Uduw
  tracking: stable
  refresh-date: heute um 04:19 CEST
  channels:
    stable:v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
    candidate: v3.32.1+git1.2050bba 2019-05-01 (258) 15MB -
    beta:  ^
    edge:  v3.32.0+git9.4424d0f 2019-05-08 (260) 15MB -
  installed:   v3.32.1+git1.2050bba(258) 15MB -
  ---
  name:  communitheme
  publisher: Didier Roche (didrocks)
    Yaru, formerly known as Communitheme, is the new Ubuntu theme built by the
    community. Yaru will become the default Ubuntu theme in Ubuntu 18.10. This
    package allows you to try out the theme on Ubuntu 18.04 LTS.

    To try out the theme, install this package on Ubuntu 18.04 LTS, restart
    your computer and select the "Ubuntu with communitheme snap" session from
    the login screen.

    More information is available at
    https://community.ubuntu.com/t/faq-ubuntu-new-theme/1930.
  snap-id:  Yd6CISPIf6tEf3ZEJ0cqSoEg9rG2VkRi
  tracking: stable
  refresh-date: 59 days ago, at 17:46 CET
  channels:
    stable:0.1 2019-03-13 (1768) 16MB -
    candidate: ^
    beta:  ^
    edge:  0.1 2019-05-08 (1799) 17MB -
  installed:   0.1(1768) 16MB -
  ```

  ---

  Further investigation
  -

  I'm also seeing broken links on an 19.04 machine where I'm not using
  the Communitheme snap but the preinstalled Yaru packages. I'm trying
  out the dark theme but all snaps launch with Adwaita instead.

  ```
  $ snap list
  Name Version Rev   Tracking  Publisher
 Notes
  android-studio   3.4.0.1875stablesnapcrafters 
 classic
  canonical-livepatch  9.3.0   77stablecanonical*   
 -
  core 16-2.38.1   6818  stablecanonical*   
 core
  core18   20190409941   stablecanonical*   
 base
  gedit3.30.2+git14.bed83e929  89stablecanonical*   
 -
  gnome-3-26-1604  3.26.0.20190228 82stable/…  canonical*   
 -
  gnome-3-28-1804  3.28.0-10-gaa70833.aa70833  40stablecanonical*   
 -
  gnome-calculator 3.32.1  406   stable/…  canonical*   
 -
  gnome-characters v3.32.1+git1.2050bba258   stablecanonical*   
 -
  gnome-logs   3.32.0-4-ge8f3f37ca861stable/…  canonical*   
 -
  gtk-common-themes0.1-16-g2287c87 1198  stable/…  canonical*   
 -

  
  $ find snap/gnome-characters -xtype l
  snap/gnome-characters/common/.cache/immodules/im-fcitx.so
  snap/gnome-characters/common/.cache/immodules/im-wayland.so
  snap/gnome-characters/common/.cache/immodules/im-broadway.so
  snap/gnome-characters/common/.cache/immodules/im-inuktitut.so
  snap/gnome-characters/common/.cache/immodules/im-cedilla.so
  snap/gnome-characters/common/.cache/immodules/im-ipa.so
  snap/gnome-characters/common/.cache/immodules/im-xim.so
  snap/gnome-characters/common/.cache/immodules/im-thai.so
  snap/gnome-characters/common/.cache/immodules/im-multipress.so

[Desktop-packages] [Bug 1856798] [NEW] vitrage-ml run error

[Qitao]

Public bug reported:

Vitrage  report error as follows  when adding config plugins =
jaccard_correlation


Dec 18 10:40:19 qihongtao vitrage-ml[6174]: Traceback (most recent call last):
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/lib/python3.6/multiprocessing/process.py", line 258, in _bootstrap
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.run()
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/lib/python3.6/multiprocessing/process.py", line 93, in run Dec 18 
10:40:19 qihongtao vitrage-ml[6174]: self._target(*self._args, 
**self._kwargs)
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_utils.py", line 63, in 
_bootstrap_process
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: target(*args, **kwargs)
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_service.py", line 161, in 
create_and_wait
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: sw = cls(*args, **kwargs)
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_service.py", line 175, in 
__init__
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.service = 
config.service(worker_id, *args, **kwargs)
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/opt/stack/vitrage/vitrage/machine_learning/service.py", line 32, in __init__
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.machine_learning_plugins = 
self.get_machine_learning_plugins() Dec 18 10:40:19 qihongtao 
vitrage-ml[6174]:   File 
"/opt/stack/vitrage/vitrage/machine_learning/service.py", line 75, in 
get_machine_learning_plugins
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: CONF))
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/oslo_utils/importutils.py", line 44, in 
import_object
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: return 
import_class(import_str)(*args, **kwargs)
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: TypeError: __init__() takes 1 
positional argument but 2 were given
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: INFO cotyledon._service_manager [-] 
Child 6217 exited with status 1
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: INFO cotyledon._service_manager [-] 
Forking too fast, sleeping

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

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

Title:
  vitrage-ml run error

Status in libssh package in Ubuntu:
  New

Bug description:
  Vitrage  report error as follows  when adding config plugins =
  jaccard_correlation

  
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: Traceback (most recent call last):
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/lib/python3.6/multiprocessing/process.py", line 258, in _bootstrap
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.run()
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/lib/python3.6/multiprocessing/process.py", line 93, in run Dec 18 
10:40:19 qihongtao vitrage-ml[6174]: self._target(*self._args, 
**self._kwargs)
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_utils.py", line 63, in 
_bootstrap_process
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: target(*args, **kwargs)
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_service.py", line 161, in 
create_and_wait
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: sw = cls(*args, **kwargs)
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_service.py", line 175, in 
__init__
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.service = 
config.service(worker_id, *args, **kwargs)
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/opt/stack/vitrage/vitrage/machine_learning/service.py", line 32, in __init__
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.machine_learning_plugins 
= self.get_machine_learning_plugins() Dec 18 10:40:19 qihongtao 
vitrage-ml[6174]:   File 
"/opt/stack/vitrage/vitrage/machine_learning/service.py", line 75, in 
get_machine_learning_plugins
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: CONF))
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/oslo_utils/importutils.py", line 44, in 
import_object
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: return 
import_class(import_str)(*args, **kwargs)
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: TypeError: __init__() takes 1 
positional argument but 2 were given
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: INFO cotyledon._service_manager 
[-] Child 6217 exited with status 1
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: INFO cotyledon._service_manager 
[-] Forking too fast, sleeping

To manage notifications about 

[Desktop-packages] [Bug 1856799] [NEW] vitrage-ml run error

[Qitao]

Public bug reported:

Vitrage  report error as follows  when adding config plugins =
jaccard_correlation


Dec 18 10:40:19 qihongtao vitrage-ml[6174]: Traceback (most recent call last):
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/lib/python3.6/multiprocessing/process.py", line 258, in _bootstrap
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.run()
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/lib/python3.6/multiprocessing/process.py", line 93, in run Dec 18 
10:40:19 qihongtao vitrage-ml[6174]: self._target(*self._args, 
**self._kwargs)
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_utils.py", line 63, in 
_bootstrap_process
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: target(*args, **kwargs)
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_service.py", line 161, in 
create_and_wait
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: sw = cls(*args, **kwargs)
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_service.py", line 175, in 
__init__
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.service = 
config.service(worker_id, *args, **kwargs)
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/opt/stack/vitrage/vitrage/machine_learning/service.py", line 32, in __init__
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.machine_learning_plugins = 
self.get_machine_learning_plugins() Dec 18 10:40:19 qihongtao 
vitrage-ml[6174]:   File 
"/opt/stack/vitrage/vitrage/machine_learning/service.py", line 75, in 
get_machine_learning_plugins
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: CONF))
Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/oslo_utils/importutils.py", line 44, in 
import_object
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: return 
import_class(import_str)(*args, **kwargs)
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: TypeError: __init__() takes 1 
positional argument but 2 were given
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: INFO cotyledon._service_manager [-] 
Child 6217 exited with status 1
Dec 18 10:40:19 qihongtao vitrage-ml[6174]: INFO cotyledon._service_manager [-] 
Forking too fast, sleeping

** Affects: libssh (Ubuntu)
 Importance: Undecided
 Assignee: Qitao (hontu)
 Status: New

** Changed in: libssh (Ubuntu)
 Assignee: (unassigned) => Qitao (hontu)

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

Title:
  vitrage-ml run error

Status in libssh package in Ubuntu:
  New

Bug description:
  Vitrage  report error as follows  when adding config plugins =
  jaccard_correlation

  
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: Traceback (most recent call last):
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/lib/python3.6/multiprocessing/process.py", line 258, in _bootstrap
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.run()
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/lib/python3.6/multiprocessing/process.py", line 93, in run Dec 18 
10:40:19 qihongtao vitrage-ml[6174]: self._target(*self._args, 
**self._kwargs)
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_utils.py", line 63, in 
_bootstrap_process
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: target(*args, **kwargs)
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_service.py", line 161, in 
create_and_wait
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: sw = cls(*args, **kwargs)
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/cotyledon/_service.py", line 175, in 
__init__
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.service = 
config.service(worker_id, *args, **kwargs)
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/opt/stack/vitrage/vitrage/machine_learning/service.py", line 32, in __init__
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: self.machine_learning_plugins 
= self.get_machine_learning_plugins() Dec 18 10:40:19 qihongtao 
vitrage-ml[6174]:   File 
"/opt/stack/vitrage/vitrage/machine_learning/service.py", line 75, in 
get_machine_learning_plugins
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: CONF))
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]:   File 
"/usr/local/lib/python3.6/dist-packages/oslo_utils/importutils.py", line 44, in 
import_object
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: return 
import_class(import_str)(*args, **kwargs)
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: TypeError: __init__() takes 1 
positional argument but 2 were given
  Dec 18 10:40:19 qihongtao vitrage-ml[6174]: INFO cotyledon._service_manager 
[-] Child 6217 exited with status 1
  Dec 18 10:40:19 qihongtao 

[Desktop-packages] [Bug 1856795] [NEW] X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5

[Mihai Moldovan]

Public bug reported:

The recent CVE fix broke SCP support in libssh, which X2Go Client
(x2goclient) relies on.

Sessions now fail with error messages such as "SCP: Warning: status code
1 received: scp: ~username/.x2go/ssh: No such file or directory\n".
(Also note the literal "\n" there, but I guess we don't really need to
care about that.)

The previous version worked fine and rolling the libssh4 package back
fixes this issue, but also leaves users vulnerable to the fixed security
issue in its scp implementation.


I've been looking at the debdiff, but spotting the actual changes is very 
difficult due to the reformatting that was done at the same time. This degraded 
the patch(es) into one big blob.

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

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

Title:
  X2Go Client broken by 0.8.0~20170825.94fa1e38-1ubuntu0.5

Status in libssh package in Ubuntu:
  New

Bug description:
  The recent CVE fix broke SCP support in libssh, which X2Go Client
  (x2goclient) relies on.

  Sessions now fail with error messages such as "SCP: Warning: status
  code 1 received: scp: ~username/.x2go/ssh: No such file or
  directory\n". (Also note the literal "\n" there, but I guess we don't
  really need to care about that.)

  The previous version worked fine and rolling the libssh4 package back
  fixes this issue, but also leaves users vulnerable to the fixed
  security issue in its scp implementation.

  
  I've been looking at the debdiff, but spotting the actual changes is very 
difficult due to the reformatting that was done at the same time. This degraded 
the patch(es) into one big blob.

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

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

[Desktop-packages] [Bug 1856702] Re: LibreOffice window behind Firefox was flickering when Firefox asked me for a passsword to access the CUPS logs.

[Daniel van Vugt]

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

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

Title:
  LibreOffice window behind Firefox was flickering when Firefox asked me
  for a passsword to access the CUPS logs.

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When I was attempting to access CUPS logs on the CUPS page on my PC,
  LibreOffice Writer's window started flickering uncontrollably.

  Ubuntu 19.10

  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
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 17 08:07:19 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  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.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BuildID: 20191205203726
  CurrentDesktop: ubuntu:GNOME
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:722
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: firefox 71.0+build5-0ubuntu0.19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=71.0/20191205203726 (In use)
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edwin  1403 F pulseaudio
  BuildID: 20191205203726
  Channel: Unavailable
  DistroRelease: Ubuntu 19.10
  ForcedLayersAccel: False
  

[Desktop-packages] [Bug 1856691] Re: libpulse-mainloop-glib0:i386 cannot be installed

[Daniel van Vugt]

It appears your packaging configuration is confused. You have one
package from

  bionic-proposed (1:11.1-1ubuntu7.5)

and are trying to install another from

  bionic-updates (1:11.1-1ubuntu7.4)

I wonder if that's something we did wrong. Did we revert the newer
version from updates to proposed? Looks like it...

Regardless, the solution would be to find all packages with version
1:11.1-1ubuntu7.5 and download the 1:11.1-1ubuntu7.4 equivalent deb
files from:

https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.4/+build/17893830

Then manually install them using:

  dpkg -i *.deb

An alternative solution would be to manually install all the newer
packages from:

https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.5/+build/18146193

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

Title:
  libpulse-mainloop-glib0:i386 cannot be installed

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  libpulse-mainloop-glib0:i386 cannot be installed because it needs
  libpulse0:i386 (= 1:11.1-1ubuntu7.4), but 1:11.1-1ubuntu7.5 is
  installed. I am running Linux Mint 19.2 which is using the Ubuntu
  bionic packages.

  user@computer:$ sudo apt policy libpulse-mainloop-glib0:i386
  libpulse-mainloop-glib0:i386:
Installiert:   (keine)
Installationskandidat: 1:11.1-1ubuntu7.4
Versionstabelle:
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$ sudo apt policy libpulse0:i386
  libpulse0:i386:
Installiert:   1:11.1-1ubuntu7.5
Installationskandidat: 1:11.1-1ubuntu7.5
Versionstabelle:
   *** 1:11.1-1ubuntu7.5 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$

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

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

[Desktop-packages] [Bug 1856691] Re: libpulse-mainloop-glib0:i386 cannot be installed

[Daniel van Vugt]

Since this is a fault in the Ubuntu archive/mirror, not in the
PulseAudio packages themselves, I have to mark it as Invalid sorry.

But we can keep discussing solutions here.

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

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

Title:
  libpulse-mainloop-glib0:i386 cannot be installed

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  libpulse-mainloop-glib0:i386 cannot be installed because it needs
  libpulse0:i386 (= 1:11.1-1ubuntu7.4), but 1:11.1-1ubuntu7.5 is
  installed. I am running Linux Mint 19.2 which is using the Ubuntu
  bionic packages.

  user@computer:$ sudo apt policy libpulse-mainloop-glib0:i386
  libpulse-mainloop-glib0:i386:
Installiert:   (keine)
Installationskandidat: 1:11.1-1ubuntu7.4
Versionstabelle:
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$ sudo apt policy libpulse0:i386
  libpulse0:i386:
Installiert:   1:11.1-1ubuntu7.5
Installationskandidat: 1:11.1-1ubuntu7.5
Versionstabelle:
   *** 1:11.1-1ubuntu7.5 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$

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

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

[Desktop-packages] [Bug 1856691] Re: libpulse-mainloop-glib0:i386 cannot be installed

[Daniel van Vugt]

I expect this problem will resolve itself after version
1:11.1-1ubuntu7.5 (or higher) gets re-released.

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

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

Title:
  libpulse-mainloop-glib0:i386 cannot be installed

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  libpulse-mainloop-glib0:i386 cannot be installed because it needs
  libpulse0:i386 (= 1:11.1-1ubuntu7.4), but 1:11.1-1ubuntu7.5 is
  installed. I am running Linux Mint 19.2 which is using the Ubuntu
  bionic packages.

  user@computer:$ sudo apt policy libpulse-mainloop-glib0:i386
  libpulse-mainloop-glib0:i386:
Installiert:   (keine)
Installationskandidat: 1:11.1-1ubuntu7.4
Versionstabelle:
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$ sudo apt policy libpulse0:i386
  libpulse0:i386:
Installiert:   1:11.1-1ubuntu7.5
Installationskandidat: 1:11.1-1ubuntu7.5
Versionstabelle:
   *** 1:11.1-1ubuntu7.5 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$

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

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

[Desktop-packages] [Bug 1856691] Re: libpulse-mainloop-glib0:i386 cannot be installed

[Daniel van Vugt]

Although it would be fixable in the PulseAudio packages if we just
bumped the version.

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

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

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

Title:
  libpulse-mainloop-glib0:i386 cannot be installed

Status in pulseaudio package in Ubuntu:
  Fix Committed

Bug description:
  libpulse-mainloop-glib0:i386 cannot be installed because it needs
  libpulse0:i386 (= 1:11.1-1ubuntu7.4), but 1:11.1-1ubuntu7.5 is
  installed. I am running Linux Mint 19.2 which is using the Ubuntu
  bionic packages.

  user@computer:$ sudo apt policy libpulse-mainloop-glib0:i386
  libpulse-mainloop-glib0:i386:
Installiert:   (keine)
Installationskandidat: 1:11.1-1ubuntu7.4
Versionstabelle:
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$ sudo apt policy libpulse0:i386
  libpulse0:i386:
Installiert:   1:11.1-1ubuntu7.5
Installationskandidat: 1:11.1-1ubuntu7.5
Versionstabelle:
   *** 1:11.1-1ubuntu7.5 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$

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

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

[Desktop-packages] [Bug 1856710] Re: Gnome's window manager put Firefox's window on the left half of the screen when Firefox was on the right side of the screen when I gave the PC a reboot command via

[Daniel van Vugt]

Please report the issue to the upstream developers at:

  https://gitlab.gnome.org/GNOME/gnome-shell/issues

and then tell us the new bug ID.

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

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

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

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

Title:
  Gnome's window manager put Firefox's window on the left half of the
  screen when Firefox was on the right side of the screen when I gave
  the PC a reboot command via the Menu Bar

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

Bug description:
  The Firefox Window was "Clipped" to the right side of the screen, as I
  dragged the window to the right screen border and the window changed
  size automatically. When I reopened Firefox after I rebooted, Firefox
  opened while snapped to the LEFT side of the screen before correcting
  itself later.

  Ubuntu 19.10

  gnome-shell:
Installed: 3.34.1+git20191024-1ubuntu1~19.10.1
Candidate: 3.34.1+git20191024-1ubuntu1~19.10.1
Version table:
   *** 3.34.1+git20191024-1ubuntu1~19.10.1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.34.1-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 08:51:29 2019
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  edwin  1403 F pulseaudio
  BuildID: 20191205203726
  Channel: Unavailable
  DistroRelease: Ubuntu 19.10
  ForcedLayersAccel: False
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.39 metric 600
  NoProfiles: True
  Package: firefox 71.0+build5-0ubuntu0.19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RunningIncompatibleAddons: False
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: mutter 3.34.1+git20191107-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1856691] Re: libpulse-mainloop-glib0:i386 cannot be installed

[Daniel van Vugt]

** Tags added: bionic

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

Title:
  libpulse-mainloop-glib0:i386 cannot be installed

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  libpulse-mainloop-glib0:i386 cannot be installed because it needs
  libpulse0:i386 (= 1:11.1-1ubuntu7.4), but 1:11.1-1ubuntu7.5 is
  installed. I am running Linux Mint 19.2 which is using the Ubuntu
  bionic packages.

  user@computer:$ sudo apt policy libpulse-mainloop-glib0:i386
  libpulse-mainloop-glib0:i386:
Installiert:   (keine)
Installationskandidat: 1:11.1-1ubuntu7.4
Versionstabelle:
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$ sudo apt policy libpulse0:i386
  libpulse0:i386:
Installiert:   1:11.1-1ubuntu7.5
Installationskandidat: 1:11.1-1ubuntu7.5
Versionstabelle:
   *** 1:11.1-1ubuntu7.5 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$

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

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

[Desktop-packages] [Bug 1856507] Re: [nvidia] Login screen doesn't show up after installing the Nvidia driver, on a desktop with only an Nvidia GPU

[Daniel van Vugt]

Thanks. This appears likely to be the problem; the Nvidia driver can't
find a monitor!?

Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (II) 
NVIDIA(0): Validated MetaModes:
Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (II) 
NVIDIA(0): "NULL"
Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (II) 
NVIDIA(0): Virtual screen size determined to be 640 x 480
Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (WW) 
NVIDIA(0): Unable to get display device for DPI computation.
...
Dec 17 15:07:44 shahar-desktop /usr/lib/gdm3/gdm-x-session[2137]: (II) 
NVIDIA(0): Setting mode "NULL"


** No longer affects: gdm3 (Ubuntu)

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

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

Title:
  [nvidia] Login screen doesn't show up after installing the Nvidia
  driver, on a desktop with only an Nvidia GPU

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

Bug description:
  Attempting to boot after installing nvidia-driver-435, the login
  screen does not show up.

  I tried editing /etc/gdm3/custom.conf and uncommenting the line:

#WaylandEnable=false

  And then rebooting. No apparent change. Still no login screen.

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nvidia-driver-435 435.21-0ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 10:46:58 2019
  InstallationDate: Installed on 2010-10-12 (3351 days ago)
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: nvidia-graphics-drivers-435
  UpgradeStatus: Upgraded to eoan on 2019-10-23 (53 days ago)

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

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

[Desktop-packages] [Bug 1856425] Re: Gnome Shell crashs sporadically

[Daniel van Vugt]

That one is from gnome-boxes, not gnome-shell.

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

Title:
  Gnome Shell crashs sporadically

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 19.10, all updated, sporadically (both in terms of timing and
  as an app I use), the gnome session crashs and re-opened by itself
  after about 1 second. However, closing the apps I was using, so as to
  lose everything. Now, just happened I saved all the logs via gnome
  logs, of 2 episodes where the problem occurred. It happened at a
  distance of not even a quarter of an hour. It's happened at 16.35 and
  16.48. In attached this log. I can see only "bluetoothd: Failed to set
  mode: Blocked through rfkill (0x12)" of relevant, in both times, but I
  don't know.

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

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

[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby 19.10

[Launchpad Bug Tracker]

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

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

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

Title:
  [nvidia] Background image corrupted after standby 19.10

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

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 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  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.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1855757] Re: [nvidia] Background image corrupted after standby 19.10

[Launchpad Bug Tracker]

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

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

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

Title:
  [nvidia] Background image corrupted after standby 19.10

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

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 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec  9 10:58:35 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed
   nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c]
  InstallationDate: Installed on 2019-11-29 (10 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: ASUSTek Computer Inc. G60JX
  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.3.0-24-generic 
root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/25/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G60JX
  dmi.board.vendor: PEGATRON CORPORATION
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: PEGATRON Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0:
  dmi.product.family: PEGA Family
  dmi.product.name: G60JX
  dmi.product.sku: 0
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTek Computer Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1856781] Re: /usr/bin/gnome-shell:free(): corrupted unsorted chunks

[Daniel van Vugt]

This bug is not useful because it is delayed heap corruption AND
presently shows no useful stack trace.

If you encounter a crash like this then please add:

  MALLOC_CHECK_=3

to your /etc/environment. Then reboot and report a new crash next time
it happens. Hopefully that one won't land here.

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

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

Title:
  /usr/bin/gnome-shell:free(): corrupted unsorted chunks

Status in gnome-shell package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.1+git20191024-1ubuntu1~19.10.1, the problem page at 
https://errors.ubuntu.com/problem/731708dc951c98fdf8e0d2693f74cf366138768d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

[Daniel van Vugt]

Thanks. That gives us a more formal issue to track: bug 1856781:
https://errors.ubuntu.com/problem/731708dc951c98fdf8e0d2693f74cf366138768d

But not really.

The problem with heap corruption issues like this is that regardless of
the root cause they will often look the same. So in this particular case
we should not join the two bugs together. To find the root cause for
your case please try adding:

  MALLOC_CHECK_=3

to your /etc/environment. Then reboot and send us more crash reports.
The crashes you get after that should be slightly different, crashing in
a different location more suggestive of the root cause of the bug.

Please also ensure you have UNINSTALLED all extensions.

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1809407] Re: [nvidia] Corrupted wallpaper after resuming from suspend or hibernation

[Daniel van Vugt]

This bug is closed. Some people have said they still see an issue
though, so please use bug 1855757 from now on...

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

Title:
  [nvidia] Corrupted wallpaper after resuming from suspend or
  hibernation

Status in GNOME Shell:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Disco:
  Won't Fix
Status in mutter source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  The Nvidia (Xorg) driver corrupts the desktop wallpaper (by design
  (1)) upon resuming from suspend. This creates a poor user experience
  and gives the impression of severe memory corruption.

  (1)
  
https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt

  [Test Case]

  0. Set up an Nvidia-only system using the proprietary Nvidia Xorg driver.
  1. Suspend and resume the machine.
  Expect: The wallpaper still looks like it did before suspending.

  [Regression Potential]

  Low. The exact same patch is in Gnome 3.34 (Ubuntu 19.10) already and
  has been used for a couple of months without issue.

  [Original Report]

  https://trello.com/c/i5hENxSO

  Every other wake from sleep presents a corrupted screen with no unlock
  app.  There's a dock and system menu on a black background with pixel
  garbage.  Some personal information in the dock's large window
  thumbnails.  Bitmap garbage flashes on the screen when interacting
  with anything.  Only workaround is doing another sleep-wake cycle.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Uname: Linux 4.18.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..4b.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:4b:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec 20 22:19:29 2018
  DistUpgraded: 2018-12-01 23:07:50,385 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.18.0-11-generic, x86_64: installed
   nvidia, 390.87, 4.18.0-12-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed
   virtualbox, 5.2.18, 4.18.0-12-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 3GB] [3842:6162]
  InstallationDate: Installed on 2018-10-28 (54 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. Default string
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic 
root=UUID=a8c839e7-c579-4699-999a-748f804ff9e0 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to cosmic on 2018-12-02 (18 days ago)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F24
  dmi.board.asset.tag: Default string
  dmi.board.name: X99P-SLI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF24:bd06/08/2017:svnGigabyteTechnologyCo.,Ltd.:pnDefaultstring:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX99P-SLI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Default string
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: 

[Desktop-packages] [Bug 1856781] [NEW] /usr/bin/gnome-shell:free(): corrupted unsorted chunks

[errors.ubuntu.com bug bridge]

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.1+git20191024-1ubuntu1~19.10.1, the problem page at 
https://errors.ubuntu.com/problem/731708dc951c98fdf8e0d2693f74cf366138768d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: bionic cosmic eoan kylin-18.04

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

Title:
  /usr/bin/gnome-shell:free(): corrupted unsorted chunks

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.1+git20191024-1ubuntu1~19.10.1, the problem page at 
https://errors.ubuntu.com/problem/731708dc951c98fdf8e0d2693f74cf366138768d 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen

[Daniel van Vugt]

This bug is closed so if you experience any problem at all then please
open a new one by running:

ubuntu-bug gnome-shell

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

Title:
  onscreen keyboard appears whenever i touch touchscreen

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Artful:
  Won't Fix
Status in gnome-shell package in Arch Linux:
  New

Bug description:
  Impact
  ==
  I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is 
disabled in System Preferences > Universal Access.  This didn't happen in any 
previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based.

  Test Case
  =
  0. Find a laptop with a touch screen that works.
  1. Settings > Universal Access > Typing > Screen Keyboard = OFF
  2. Touch the screen.

  Regression Potential
  

  Workaround
  ==
  https://extensions.gnome.org/extension/1326/block-caribou/

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

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

[Desktop-packages] [Bug 1856553] Re: libinput error: client bug: timer event3 debounce short: offset negative (-0ms) (#2041)

[Clinton H]

2:21:18 PM gnome-shell: WL: error in client communication (pid 8139)

 2:21:18 PM gnome-shell: libinput error: client bug: timer event4
debounce short: offset negative (-2ms)

 2:21:16 PM gnome-shell: libinput error: client bug: timer event4
debounce short: offset negative (-64ms)

 2:21:16 PM gnome-shell: libinput error: client bug: timer event4
debounce: offset negative (-51ms)

 2:21:09 PM gnome-shell: libinput error: client bug: timer event4
debounce short: offset negative (-9ms)

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

Title:
  libinput error: client bug: timer event3 debounce short: offset
  negative (-0ms) (#2041)

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

Bug description:
  1) Ubuntu 19.10
  2) mutter 3.34.1
  3) No error.
  4) Error in log app.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: mutter 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 16 05:36:05 2019
  InstallationDate: Installed on 2019-10-28 (49 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1798961] Re: Random unrecoverable freezes on Ubuntu 18.10

[Jamie Redmond]

Happening to me too. Full details available on this issue:
https://github.com/brave/brave-browser/issues/7439

** Bug watch added: github.com/brave/brave-browser/issues #7439
   https://github.com/brave/brave-browser/issues/7439

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

Title:
  Random unrecoverable freezes on Ubuntu 18.10

Status in Linux:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-intel package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Triaged
Status in xserver-xorg-video-intel source package in Bionic:
  Invalid
Status in linux source package in Cosmic:
  Triaged
Status in xserver-xorg-video-intel source package in Cosmic:
  Invalid
Status in linux source package in Disco:
  Triaged
Status in xserver-xorg-video-intel source package in Disco:
  Invalid

Bug description:
  First thing I notice is that the mouse cursor freezes as I'm using it,
  then I hit the CAPS LOCK key and the LED indicator doesn't respond.
  Then I try the "REISUB" command, but it doesn't do anything either.
  Only a hard reset works, pressing down the power button for a few
  seconds.

  How to reproduce?
  I couldn't figure out a consistent method. It is still random to me.

  Version: Ubuntu 4.18.0-10.11-generic 4.18.12
  System information attached.

  Also happens under Arch Linux and Fedora.
  I've talked to another user on IRC who seems to be having the same freezes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-10-generic 4.18.0-10.11
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dsilva 1213 F pulseaudio
   /dev/snd/controlC0:  dsilva 1213 F pulseaudio
  CurrentDesktop: XFCE
  Date: Sat Oct 20 09:54:50 2018
  InstallationDate: Installed on 2018-10-20 (0 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  MachineType: Dell Inc. Inspiron 5458
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-10-generic 
root=/dev/mapper/xubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/02/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A15
  dmi.board.name: 09WGNT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA15:bd02/02/2018:svnDellInc.:pnInspiron5458:pvr01:rvnDellInc.:rn09WGNT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5458
  dmi.product.sku: Inspiron 5458
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1849680] Re: audit spam in dmesg (libreoffice)

[Jamie Strandboge]

For the next libreoffice upload, the non-/home read-only accesses all
look fine to add to the libreoffice profile.

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

Title:
  audit spam in dmesg (libreoffice)

Status in libreoffice package in Ubuntu:
  New

Bug description:
  My dmesg is getting flooded by apparmor audit messages, mostly from
  libreoffice (profiles libreoffice-soffice and libreoffice-oosplash):

  $ dmesg | tail -n 25
  [13682.452555] audit: type=1400 audit(1571920851.001:3672): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [13682.453430] audit: type=1400 audit(1571920851.001:3673): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [13682.453933] audit: type=1400 audit(1571920851.001:3674): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [13682.455491] audit: type=1400 audit(1571920851.005:3675): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.cache/mesa_shader_cache/index" pid=17792 comm="soffice.bin" 
requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
  [13682.604100] audit: type=1400 audit(1571920851.153:3676): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.local/share/gvfs-metadata/smb-share:server=buddha,share=chris"
 pid=17791 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
  [13682.604138] audit: type=1400 audit(1571920851.153:3677): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.local/share/gvfs-metadata/smb-share:server=buddha,share=chris-22028640.log"
 pid=17791 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
  [13683.097648] audit: type=1400 audit(1571920851.645:3678): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.mozilla/firefox/vq2zzheq.chris-2019-09/cert8.db" pid=17791 
comm="soffice.bin" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
  [16676.510664] kauditd_printk_skb: 1210 callbacks suppressed
  [16676.510665] audit: type=1400 audit(1571923845.047:4889): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.511473] audit: type=1400 audit(1571923845.047:4890): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.550636] audit: type=1400 audit(1571923845.087:4891): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.551394] audit: type=1400 audit(1571923845.087:4892): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.552145] audit: type=1400 audit(1571923845.087:4893): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.552568] audit: type=1400 audit(1571923845.087:4894): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.553912] audit: type=1400 audit(1571923845.091:4895): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.cache/mesa_shader_cache/index" pid=18543 comm="soffice.bin" 
requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
  [16694.388901] audit: type=1400 audit(1571923862.923:4896): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/proc/18541/mountinfo" pid=18541 comm="soffice.bin" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=1000
  [16694.388972] audit: type=1400 audit(1571923862.923:4897): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/proc/18541/cgroup" pid=18541 comm="soffice.bin" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=1000
  [16694.388992] audit: type=1400 audit(1571923862.923:4898): 
apparmor="ALLOWED" operation="open" 

[Desktop-packages] [Bug 1849680] Re: audit spam in dmesg (libreoffice)

[Jamie Strandboge]

libreoffice ships this profile, so the bug should be tracked there.

** Package changed: apparmor (Ubuntu) => libreoffice (Ubuntu)

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

Title:
  audit spam in dmesg (libreoffice)

Status in libreoffice package in Ubuntu:
  New

Bug description:
  My dmesg is getting flooded by apparmor audit messages, mostly from
  libreoffice (profiles libreoffice-soffice and libreoffice-oosplash):

  $ dmesg | tail -n 25
  [13682.452555] audit: type=1400 audit(1571920851.001:3672): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [13682.453430] audit: type=1400 audit(1571920851.001:3673): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [13682.453933] audit: type=1400 audit(1571920851.001:3674): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [13682.455491] audit: type=1400 audit(1571920851.005:3675): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.cache/mesa_shader_cache/index" pid=17792 comm="soffice.bin" 
requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
  [13682.604100] audit: type=1400 audit(1571920851.153:3676): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.local/share/gvfs-metadata/smb-share:server=buddha,share=chris"
 pid=17791 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
  [13682.604138] audit: type=1400 audit(1571920851.153:3677): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.local/share/gvfs-metadata/smb-share:server=buddha,share=chris-22028640.log"
 pid=17791 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
  [13683.097648] audit: type=1400 audit(1571920851.645:3678): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.mozilla/firefox/vq2zzheq.chris-2019-09/cert8.db" pid=17791 
comm="soffice.bin" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
  [16676.510664] kauditd_printk_skb: 1210 callbacks suppressed
  [16676.510665] audit: type=1400 audit(1571923845.047:4889): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.511473] audit: type=1400 audit(1571923845.047:4890): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.550636] audit: type=1400 audit(1571923845.087:4891): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.551394] audit: type=1400 audit(1571923845.087:4892): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.552145] audit: type=1400 audit(1571923845.087:4893): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.552568] audit: type=1400 audit(1571923845.087:4894): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
  [16676.553912] audit: type=1400 audit(1571923845.091:4895): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/home/chris/.cache/mesa_shader_cache/index" pid=18543 comm="soffice.bin" 
requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
  [16694.388901] audit: type=1400 audit(1571923862.923:4896): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/proc/18541/mountinfo" pid=18541 comm="soffice.bin" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=1000
  [16694.388972] audit: type=1400 audit(1571923862.923:4897): 
apparmor="ALLOWED" operation="open" profile="libreoffice-soffice" 
name="/proc/18541/cgroup" pid=18541 comm="soffice.bin" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=1000
  [16694.388992] audit: type=1400 audit(1571923862.923:4898): 
apparmor="ALLOWED" operation="open" 

[Desktop-packages] [Bug 1856624] Re: Firefox freezes temporarily at 100% CPU when Chromium is opened

[ais523]

I can confirm that the bug described in the askubuntu.com link above is
the bug I'm seeing; the workaround stated there (renaming `~/.fonts`)
was enough to prevent it occurring.

I have fontconfig 2.12.6-0ubuntu2 installed (and my fontconfig-config is
the same version).

Should this bug report be moved to the fontconfig package, as apparently
it's the underlying cause of the bug? Presumably it will be fixed
if/when Ubuntu updates to a newer version of fontconfig.

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

Title:
  Firefox freezes temporarily at 100% CPU when Chromium is opened

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

Bug description:
  When Firefox is open, and I open Chromium, many features of Firefox
  fail to work for several seconds. (To reproduce, start with neither
  Firefox nor Chromium open; open Firefox, and allow one or more web
  pages to load; then open Chromium; the issue starts a second or two
  after Chromium is opened.) This is a temporary issue, lasting for
  several seconds; the length of time it lasts appears to depend on how
  many open tabs have been viewed since Firefox opened (on my computer,
  around 10 seconds with 1 tab having been viewed, around a minute with
  10 tabs having been viewed). This reproduces even when running Firefox
  as `firefox -safe-mode`.

  While the issue is ongoing (i.e. starting around a second after Chromium is 
open, and persisting for typically tens of seconds), some features of Firefox 
work, but most do not:
  - Scrolling the current tab short distances succeeds, showing the expected 
text on the page.
  - Scrolling the current tab long distances (several screeenfuls) causes the 
page to be "cut off" past a certain point, with only a blank background 
rendering.
  - Moving the mouse cursor over a link does not change the mouse cursor 
(expected behaviour, and behaviour while the issue is not ongoing, is for it to 
change to a hand shape).
  - Changing tab causes the resulting page not to display: rather, a grey 
background is displayed, and sometimes a loading spinner.
  - Changing tab back then causes the original page not to render, as if it 
were new, despite the fact it was correctly displayed earlier.
  - The address bar functions as normal; the issue does not appear to affect 
address bar functionality.
  Additionally, while the issue is ongoing, Firefox uses 100% CPU.

  At some point after the issue in question starts, it stops, and all
  Firefox features return to normal (including any missing or
  incorrectly rendered page content, which renders again when the issue
  ends).

  The trigger is specifically the act of opening Chromium: Firefox can
  function just fine once the issue ends, even if Chromium is still
  open, and functions just fine if Chromium is opened first.

  I have an (unconfirmed) theory that opening Chromium is causing some
  operation within Firefox to become very slow, using up all the CPU
  time, and the other observed misbehaviours within Firefox are a
  consequence of how slowly it is running; however, I've listed them all
  anyway in case it provides clarity into what the specific nature of
  the bug is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 71.0+build5-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ais523 1800 F pulseaudio
  BuildID: 20191205184924
  Channel: Unavailable
  CurrentDesktop: X-Cinnamon
  Date: Tue Dec 17 00:29:10 2019
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Français Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2019-11-11 (35 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 
600
  MostRecentCrashID: bp-935fd166-3720-454f-8fe5-0a1752140227
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:722
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - 

[Desktop-packages] [Bug 1848919] Re: [snap] Permission denied on Private encrypted folder

[Jamie Strandboge]

** Changed in: apparmor
   Status: Triaged => In Progress

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

Title:
  [snap] Permission denied on Private encrypted folder

Status in AppArmor:
  In Progress
Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Triaged

Bug description:
  When accessing the Private (/home/username/Private, Encrypted
  Directory) folder (e.g. via "Link save as...") it shows "Could not
  read contents of Private, Error opening directory ...: Permission
  denied"

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1

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

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

[Desktop-packages] [Bug 1852645] Re: WebAudio API does not behave as expected (Cannot mute videos)

[Olivier Tilloy]

Good that the issue seems to be fixed for you. I'm closing this bug,
feel free to re-open if the problem surfaces again.

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

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

Title:
  WebAudio API does not behave as expected (Cannot mute videos)

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  I initially posted this bug to the Firefox issue tracker here:
  https://bugzilla.mozilla.org/show_bug.cgi?id=1596397, but we
  determined it was specific to the Ubuntu package.

  When I play the video in this JSFiddle:
  https://jsfiddle.net/ea9h3bg7/, there should be no audio. This is the
  behavior in the Firefox 70 build that you can get from Mozilla's
  website. However, with the Ubuntu build, audio is still heard.

  ---

  Ubuntu 19.10, Firefox that shipped with the distro, upgraded to 70.0.1
  via the Ubuntu update manager.

  Firefox package version:

  firefox:
Installed: 70.0.1+build1-0ubuntu0.19.10.1
Candidate: 70.0.1+build1-0ubuntu0.19.10.1
Version table:
   *** 70.0.1+build1-0ubuntu0.19.10.1 500
  500 http://fr.archive.ubuntu.com/ubuntu eoan-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   69.0.3+build1-0ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BuildID: 20191031091608
  CurrentDesktop: ubuntu:GNOME
  DefaultProfileExtensions: extensions.sqlite corrupt or missing
  DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  DefaultProfileLocales: extensions.sqlite corrupt or missing
  DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  DefaultProfileThemes: extensions.sqlite corrupt or missing
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-09 (16 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: firefox 70.0.1+build1-0ubuntu0.19.10.1 [modified: 
usr/share/applications/firefox.desktop]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Profile3Extensions: extensions.sqlite corrupt or missing
  Profile3IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  Profile3Locales: extensions.sqlite corrupt or missing
  Profile3PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  Profile3PrefSources: prefs.js
  Profile3Themes: extensions.sqlite corrupt or missing
  Profiles:
   Profile3 - LastVersion=70.0.1/20191030021342 (Out of date)
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=70.0.1/20191031091608 (In use)
   Profile2 - LastVersion=72.0a1/20191114055112 (Out of date)
  Tags:  eoan
  Uname: Linux 5.3.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1849680] [NEW] audit spam in dmesg (libreoffice)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

My dmesg is getting flooded by apparmor audit messages, mostly from
libreoffice (profiles libreoffice-soffice and libreoffice-oosplash):

$ dmesg | tail -n 25
[13682.452555] audit: type=1400 audit(1571920851.001:3672): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[13682.453430] audit: type=1400 audit(1571920851.001:3673): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[13682.453933] audit: type=1400 audit(1571920851.001:3674): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=17792 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[13682.455491] audit: type=1400 audit(1571920851.005:3675): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/home/chris/.cache/mesa_shader_cache/index" pid=17792 comm="soffice.bin" 
requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
[13682.604100] audit: type=1400 audit(1571920851.153:3676): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/home/chris/.local/share/gvfs-metadata/smb-share:server=buddha,share=chris"
 pid=17791 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
[13682.604138] audit: type=1400 audit(1571920851.153:3677): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/home/chris/.local/share/gvfs-metadata/smb-share:server=buddha,share=chris-22028640.log"
 pid=17791 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
[13683.097648] audit: type=1400 audit(1571920851.645:3678): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/home/chris/.mozilla/firefox/vq2zzheq.chris-2019-09/cert8.db" pid=17791 
comm="soffice.bin" requested_mask="w" denied_mask="w" fsuid=1000 ouid=1000
[16676.510664] kauditd_printk_skb: 1210 callbacks suppressed
[16676.510665] audit: type=1400 audit(1571923845.047:4889): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[16676.511473] audit: type=1400 audit(1571923845.047:4890): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[16676.550636] audit: type=1400 audit(1571923845.087:4891): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[16676.551394] audit: type=1400 audit(1571923845.087:4892): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[16676.552145] audit: type=1400 audit(1571923845.087:4893): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/drirc.d/00-mesa-defaults.conf" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[16676.552568] audit: type=1400 audit(1571923845.087:4894): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/usr/share/libdrm/amdgpu.ids" pid=18543 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[16676.553912] audit: type=1400 audit(1571923845.091:4895): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/home/chris/.cache/mesa_shader_cache/index" pid=18543 comm="soffice.bin" 
requested_mask="wrc" denied_mask="wrc" fsuid=1000 ouid=1000
[16694.388901] audit: type=1400 audit(1571923862.923:4896): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" name="/proc/18541/mountinfo" 
pid=18541 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
[16694.388972] audit: type=1400 audit(1571923862.923:4897): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" name="/proc/18541/cgroup" 
pid=18541 comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
[16694.388992] audit: type=1400 audit(1571923862.923:4898): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/sys/fs/cgroup/memory/memory.limit_in_bytes" pid=18541 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
[16694.389011] audit: type=1400 audit(1571923862.923:4899): apparmor="ALLOWED" 
operation="open" profile="libreoffice-soffice" 
name="/sys/fs/cgroup/cpu,cpuacct/cpu.cfs_quota_us" pid=18541 comm="soffice.bin" 
requested_mask="r" denied_mask="r" fsuid=1000 

[Desktop-packages] [Bug 1856752] Re: recaptcha error chromium

[Olivier Tilloy]

I haven't been able to find ads on craigslist with phone numbers behind
a captcha. Could you maybe provide a link or two to such ads, so that
someone can confirm the problem?

Can you test https://recaptcha-demo.appspot.com/ and report whether the
captchas work there, or fail similarly to those on craigslist?

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

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

Title:
  recaptcha error chromium

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  this is a well known problem but it doesn't appear in the bug list.
  Chromium browser on sites like Craigslist using Google Recaptcha to
  verify not bot status result in errors. For example: Open browswer>nav
  to Craigslist> select category > select specific item > (in the case
  where contact information includes phone number Craigslist hides
  number behind a link included in the "reply" daughter window) > click
  "Reply" > long pause > Click Phone Number > Recaptcha logo launches
  and "working" indicator runs. After time, results= "An Error has
  occured" This is not once or twice but all the time and on more than
  one machine running same 18.04 - Chromium.  It also occurs where
  listing page has additional "Show Phone Number" link on the page. Any
  instance when recaptcha is deployed results in failure.

  Diagnosis so far,
  Force Chromium to load new profile (no extensions etc) 
  Reinstall Chromium
  Eliminate firewalls 
  Change I.P. address

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 79.0.3945.79-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic i686
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: i386
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-LVDS-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
   modes: 1024x768
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  Date: Tue Dec 17 14:39:04 2019
  Desktop-Session:
   'xubuntu'
   '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
   
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
  DetectedPlugins:
   
  Env:
   'None'
   'None'
  ExecutablePath: /usr/lib/chromium-browser/chromium-browser
  InstallationDate: Installed on 2018-11-24 (387 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 
(20180725)
  Load-Avg-1min: 0.69
  Load-Processes-Running-Percent:   0.2%
  MachineType: Panasonic Corporation CF-W8EWEZZAM
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=ba5f99a1-a0de-4e43-a887-4a4dc9070eb9 ro quiet splash vt.handoff=1
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/05/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.50L14
  dmi.board.name: CFW8W-1
  dmi.board.vendor: Panasonic Corporation
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Panasonic Corporation
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.50L14:bd06/05/2009:svnPanasonicCorporation:pnCF-W8EWEZZAM:pvr001:rvnPanasonicCorporation:rnCFW8W-1:rvr1:cvnPanasonicCorporation:ct10:cvr001:
  dmi.product.family: CFW8W-1
  dmi.product.name: CF-W8EWEZZAM
  dmi.product.version: 001
  dmi.sys.vendor: Panasonic Corporation
  modified.conffile..etc.default.chromium-browser: [deleted]

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

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

[Desktop-packages] [Bug 1856624] Re: Firefox freezes temporarily at 100% CPU when Chromium is opened

[Olivier Tilloy]

It is in fact a known bug, caused by versions of fontconfig < 2.13. See
https://bugzilla.mozilla.org/show_bug.cgi?id=1566053 and
https://askubuntu.com/questions/1076412/firefox-freezing-with-100-cpu-
usage-for-30-seconds-when-launching-chromium#answer-1089841.

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

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

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

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

Title:
  Firefox freezes temporarily at 100% CPU when Chromium is opened

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

Bug description:
  When Firefox is open, and I open Chromium, many features of Firefox
  fail to work for several seconds. (To reproduce, start with neither
  Firefox nor Chromium open; open Firefox, and allow one or more web
  pages to load; then open Chromium; the issue starts a second or two
  after Chromium is opened.) This is a temporary issue, lasting for
  several seconds; the length of time it lasts appears to depend on how
  many open tabs have been viewed since Firefox opened (on my computer,
  around 10 seconds with 1 tab having been viewed, around a minute with
  10 tabs having been viewed). This reproduces even when running Firefox
  as `firefox -safe-mode`.

  While the issue is ongoing (i.e. starting around a second after Chromium is 
open, and persisting for typically tens of seconds), some features of Firefox 
work, but most do not:
  - Scrolling the current tab short distances succeeds, showing the expected 
text on the page.
  - Scrolling the current tab long distances (several screeenfuls) causes the 
page to be "cut off" past a certain point, with only a blank background 
rendering.
  - Moving the mouse cursor over a link does not change the mouse cursor 
(expected behaviour, and behaviour while the issue is not ongoing, is for it to 
change to a hand shape).
  - Changing tab causes the resulting page not to display: rather, a grey 
background is displayed, and sometimes a loading spinner.
  - Changing tab back then causes the original page not to render, as if it 
were new, despite the fact it was correctly displayed earlier.
  - The address bar functions as normal; the issue does not appear to affect 
address bar functionality.
  Additionally, while the issue is ongoing, Firefox uses 100% CPU.

  At some point after the issue in question starts, it stops, and all
  Firefox features return to normal (including any missing or
  incorrectly rendered page content, which renders again when the issue
  ends).

  The trigger is specifically the act of opening Chromium: Firefox can
  function just fine once the issue ends, even if Chromium is still
  open, and functions just fine if Chromium is opened first.

  I have an (unconfirmed) theory that opening Chromium is causing some
  operation within Firefox to become very slow, using up all the CPU
  time, and the other observed misbehaviours within Firefox are a
  consequence of how slowly it is running; however, I've listed them all
  anyway in case it provides clarity into what the specific nature of
  the bug is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 71.0+build5-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ais523 1800 F pulseaudio
  BuildID: 20191205184924
  Channel: Unavailable
  CurrentDesktop: X-Cinnamon
  Date: Tue Dec 17 00:29:10 2019
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Français Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2019-11-11 (35 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 
600
  MostRecentCrashID: bp-935fd166-3720-454f-8fe5-0a1752140227
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:722
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   

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

[Seth Forshee]

I don't think any updates to nvidia-graphics-drivers-435 are necessary.
I don't know whether ubuntu-drivers-common needs to be updated.

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

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

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

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

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

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

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1852828] Re: Firefox youtube videos do not start automatically, when selected

[Olivier Tilloy]

Well, that's good news!
It would have been even better to understand the cause of it, but for now I'll 
close the bug. Feel free to re-open if the problem surfaces again.

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

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

Title:
  Firefox youtube videos do not start automatically, when selected

Status in firefox package in Ubuntu:
  Invalid

Bug description:
  When I select a youtube video, nothing happens. I have to stop and
  start the video to get it going. While it is stagnant, it slowly
  builds up its buffer till 2 minutes, but the video most left button
  displays, that it is running, but like I said, I have to stop and
  start it again. Chromium works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 70.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   2681 F pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   2681 F...m pulseaudio
   /dev/snd/timer:  bertadmin   2681 f pulseaudio
  BuildID: 20191031085722
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Fri Nov 15 20:45:24 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-03-11 (614 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IpRoute:
   default via 192.168.1.1 dev enp0s3 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000 
   192.168.1.0/24 dev enp0s3 proto kernel scope link src 192.168.1.104 metric 
100
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=70.0.1/20191031085722 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1856624] Re: Firefox freezes temporarily at 100% CPU when Chromium is opened

[ais523]

I have a total of 8 GB of RAM and 2 GB of swap.

Reproducing the issue with a memory monitor opened, however, showed that
the issue was not related to memory exhaustion: I had at least 2 GB of
unused RAM at all times, and although the swap was enabled, it was not
used (the swap usage remained at 0 throughout the entire period).

Also observed during this test: eight Firefox processes (seven Web
Content and one WebExtensions) were running at 50% CPU usage each
throughout the time of nonresponsiveness (my computer has 4 cores, so
between them they were using up the entire CPU usage of the computer).

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

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

Title:
  Firefox freezes temporarily at 100% CPU when Chromium is opened

Status in firefox package in Ubuntu:
  New

Bug description:
  When Firefox is open, and I open Chromium, many features of Firefox
  fail to work for several seconds. (To reproduce, start with neither
  Firefox nor Chromium open; open Firefox, and allow one or more web
  pages to load; then open Chromium; the issue starts a second or two
  after Chromium is opened.) This is a temporary issue, lasting for
  several seconds; the length of time it lasts appears to depend on how
  many open tabs have been viewed since Firefox opened (on my computer,
  around 10 seconds with 1 tab having been viewed, around a minute with
  10 tabs having been viewed). This reproduces even when running Firefox
  as `firefox -safe-mode`.

  While the issue is ongoing (i.e. starting around a second after Chromium is 
open, and persisting for typically tens of seconds), some features of Firefox 
work, but most do not:
  - Scrolling the current tab short distances succeeds, showing the expected 
text on the page.
  - Scrolling the current tab long distances (several screeenfuls) causes the 
page to be "cut off" past a certain point, with only a blank background 
rendering.
  - Moving the mouse cursor over a link does not change the mouse cursor 
(expected behaviour, and behaviour while the issue is not ongoing, is for it to 
change to a hand shape).
  - Changing tab causes the resulting page not to display: rather, a grey 
background is displayed, and sometimes a loading spinner.
  - Changing tab back then causes the original page not to render, as if it 
were new, despite the fact it was correctly displayed earlier.
  - The address bar functions as normal; the issue does not appear to affect 
address bar functionality.
  Additionally, while the issue is ongoing, Firefox uses 100% CPU.

  At some point after the issue in question starts, it stops, and all
  Firefox features return to normal (including any missing or
  incorrectly rendered page content, which renders again when the issue
  ends).

  The trigger is specifically the act of opening Chromium: Firefox can
  function just fine once the issue ends, even if Chromium is still
  open, and functions just fine if Chromium is opened first.

  I have an (unconfirmed) theory that opening Chromium is causing some
  operation within Firefox to become very slow, using up all the CPU
  time, and the other observed misbehaviours within Firefox are a
  consequence of how slowly it is running; however, I've listed them all
  anyway in case it provides clarity into what the specific nature of
  the bug is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 71.0+build5-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ais523 1800 F pulseaudio
  BuildID: 20191205184924
  Channel: Unavailable
  CurrentDesktop: X-Cinnamon
  Date: Tue Dec 17 00:29:10 2019
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Français Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2019-11-11 (35 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 
600
  MostRecentCrashID: bp-935fd166-3720-454f-8fe5-0a1752140227
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:722
  PrefSources: 

[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start

[Tim Passingham]

OK (I didn't do so before because the python3 command seemed to work).

find /usr -type d -name duplicity -ls
  1602725  4 drwxr-xr-x   2 root root 4096 Dec 15 20:10 
/usr/share/doc/duplicity
  1602642  4 drwxr-xr-x   4 root root 4096 Dec 15 20:10 
/usr/lib/python3/dist-packages/duplicity

find /usr -type f -name duplicity -ls
   658314  8 -rwxr-xr-x   1 root root 5265 Dec 15 17:37 
/usr/bin/duplicity


I would have replied earlier but I don't seem to be getting emails regarding 
comments as quickly as I used to (in fact none about your last 2 posts).

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

Title:
  Duplicity fails to start

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

Bug description:
  I am on 19.10.  Duplicity crashes as soon as I try to start a backup,
  as below. It was running fine on 19.04.

  Traceback (innermost last):
File "/usr/bin/duplicity", line 107, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 93, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in 
main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, 
in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in 
get_backend_object
  return factory(pu)
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", 
line 81, in __init__
  ensure_dbus()
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", 
line 37, in ensure_dbus
  lines = output.split(u'\n')
   TypeError: a bytes-like object is required, not 'str'

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

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

[Desktop-packages] [Bug 1856752] [NEW] recaptcha error chromium

[Anthony Hamberg]

Public bug reported:

this is a well known problem but it doesn't appear in the bug list.
Chromium browser on sites like Craigslist using Google Recaptcha to
verify not bot status result in errors. For example: Open browswer>nav
to Craigslist> select category > select specific item > (in the case
where contact information includes phone number Craigslist hides number
behind a link included in the "reply" daughter window) > click "Reply" >
long pause > Click Phone Number > Recaptcha logo launches and "working"
indicator runs. After time, results= "An Error has occured" This is not
once or twice but all the time and on more than one machine running same
18.04 - Chromium.  It also occurs where listing page has additional
"Show Phone Number" link on the page. Any instance when recaptcha is
deployed results in failure.

Diagnosis so far,
Force Chromium to load new profile (no extensions etc) 
Reinstall Chromium
Eliminate firewalls 
Change I.P. address

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: chromium-browser 79.0.3945.79-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic i686
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: i386
DRM.card0-DP-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
DRM.card0-LVDS-1:
 enabled: enabled
 dpms: On
 status: connected
 edid-base64: 
 modes: 1024x768
DRM.card0-VGA-1:
 enabled: disabled
 dpms: Off
 status: disconnected
 edid-base64: 
 modes:
Date: Tue Dec 17 14:39:04 2019
Desktop-Session:
 'xubuntu'
 '/etc/xdg/xdg-xubuntu:/etc/xdg:/etc/xdg'
 
'/usr/share/xubuntu:/usr/share/xfce4:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/usr/share'
DetectedPlugins:
 
Env:
 'None'
 'None'
ExecutablePath: /usr/lib/chromium-browser/chromium-browser
InstallationDate: Installed on 2018-11-24 (387 days ago)
InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release i386 (20180725)
Load-Avg-1min: 0.69
Load-Processes-Running-Percent:   0.2%
MachineType: Panasonic Corporation CF-W8EWEZZAM
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=ba5f99a1-a0de-4e43-a887-4a4dc9070eb9 ro quiet splash vt.handoff=1
SourcePackage: chromium-browser
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/05/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.50L14
dmi.board.name: CFW8W-1
dmi.board.vendor: Panasonic Corporation
dmi.board.version: 1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Panasonic Corporation
dmi.chassis.version: 001
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.50L14:bd06/05/2009:svnPanasonicCorporation:pnCF-W8EWEZZAM:pvr001:rvnPanasonicCorporation:rnCFW8W-1:rvr1:cvnPanasonicCorporation:ct10:cvr001:
dmi.product.family: CFW8W-1
dmi.product.name: CF-W8EWEZZAM
dmi.product.version: 001
dmi.sys.vendor: Panasonic Corporation
modified.conffile..etc.default.chromium-browser: [deleted]

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


** Tags: apport-bug bionic i386

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

Title:
  recaptcha error chromium

Status in chromium-browser package in Ubuntu:
  New

Bug description:
  this is a well known problem but it doesn't appear in the bug list.
  Chromium browser on sites like Craigslist using Google Recaptcha to
  verify not bot status result in errors. For example: Open browswer>nav
  to Craigslist> select category > select specific item > (in the case
  where contact information includes phone number Craigslist hides
  number behind a link included in the "reply" daughter window) > click
  "Reply" > long pause > Click Phone Number > Recaptcha logo launches
  and "working" indicator runs. After time, results= "An Error has
  occured" This is not once or twice but all the time and on more than
  one machine running same 18.04 - Chromium.  It also occurs where
  listing page has additional "Show Phone Number" link on the page. Any
  instance when recaptcha is deployed results in failure.

  Diagnosis so far,
  Force Chromium to load new profile (no extensions etc) 
  Reinstall Chromium
  Eliminate firewalls 
  Change I.P. address

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: chromium-browser 79.0.3945.79-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic i686
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: i386
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-LVDS-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
   modes: 1024x768
  DRM.card0-VGA-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   

[Desktop-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly

[Pushpendra Kumar]

I am facing same issue while re-connecting to my TunnelBear VPN. TunnelBear VPN 
uses open-vpn service. I have configured VPN as per instructions by TunnelBear. 
And it works fine when connect first time, but after that when choose "Turn 
Off" from Netowrok-Manager then choose "Connect" again, then I see this same 
error. See snapshot from syslog:
Dec 17 20:45:25 KUMAR-PC NetworkManager[902]:   [1576611925.5171] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN plugin: state changed: starting (3)
Dec 17 20:45:25 KUMAR-PC NetworkManager[902]:   [1576611925.5172] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN connection: (ConnectInteractive) reply received
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: WARNING: --keysize is DEPRECATED and 
will be removed in OpenVPN 2.6
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: OpenVPN 2.4.4 x86_64-pc-linux-gnu 
[SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on May 
14 2019
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: library versions: OpenSSL 1.1.1  11 
Sep 2018, LZO 2.08
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: WARNING: --ns-cert-type is 
DEPRECATED.  Use --remote-cert-tls instead.
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: the current --script-security 
setting may allow this configuration to call user-defined scripts
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: TCP/UDP: Preserving recently used 
remote address: [AF_INET]103.228.153.233:443
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: UDP link local: (not bound)
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: UDP link remote: 
[AF_INET]103.228.153.233:443
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: chroot will be delayed because 
of --client, --pull, or --up-delay
Dec 17 20:45:25 KUMAR-PC nm-openvpn[6237]: NOTE: UID/GID downgrade will be 
delayed because of --client, --pull, or --up-delay
Dec 17 20:45:27 KUMAR-PC nm-openvpn[6237]: [9563/server] Peer Connection 
Initiated with [AF_INET]103.228.153.233:443
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Option 'explicit-exit-notify' in 
[PUSH-OPTIONS]:3 is ignored by previous  blocks
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Note: option tun-ipv6 is ignored 
because modern operating systems do not need special IPv6 tun handling anymore.
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: ERROR: Cannot ioctl TUNSETIFF tun0: 
Device or resource busy (errno=16)
Dec 17 20:45:28 KUMAR-PC nm-openvpn[6237]: Exiting due to fatal error
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]:   [1576611928.9900] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN plugin: failed: connect-failed (1)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]:   [1576611928.9901] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN plugin: failed: connect-failed (1)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]:   [1576611928.9902] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN plugin: state changed: stopping (5)
Dec 17 20:45:28 KUMAR-PC NetworkManager[902]:   [1576611928.9903] 
vpn-connection[0x5568a73e41c0,d79431f3-7dda-41cb-b74b-e7b71ed48592,"TunnelBear 
India",0]: VPN plugin: state changed: stopped (6)

If someone needs, then I can reproduce this with additional traces. But as much 
I could learn from this problem is that, while "Turn Off" from Netowrk-Manager, 
Network-Manager is not able to stop openvpn process.
If I stop this openvpn process manually, then try to "Connect" from 
Network-Manager menu, it works fine.

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

Title:
  "Activation of network connection failed" popup shows incessantly

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  All network connections work normally, however the popup "Activation
  of network connection failed" keeps showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:04:56 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 
600 
   192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 
linkdown 
   192.168.122.0/24 

Re: [Desktop-packages] [Bug 1852828] Re: Firefox youtube videos do not start automatically, when selected

[BertN45]

The problem disappeared :)


On Tue, 2019-12-17 at 17:08 +, Olivier Tilloy wrote:
> Sorry for the lack of timely feedback BertN45.
> Are you still seeing this issue with the update to firefox
> 71.0+build5-0ubuntu0.18.04.1 ?
> 
> ** Changed in: firefox (Ubuntu)
>Status: New => Incomplete
>

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

Title:
  Firefox youtube videos do not start automatically, when selected

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When I select a youtube video, nothing happens. I have to stop and
  start the video to get it going. While it is stagnant, it slowly
  builds up its buffer till 2 minutes, but the video most left button
  displays, that it is running, but like I said, I have to stop and
  start it again. Chromium works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 70.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   2681 F pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   2681 F...m pulseaudio
   /dev/snd/timer:  bertadmin   2681 f pulseaudio
  BuildID: 20191031085722
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Fri Nov 15 20:45:24 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-03-11 (614 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IpRoute:
   default via 192.168.1.1 dev enp0s3 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000 
   192.168.1.0/24 dev enp0s3 proto kernel scope link src 192.168.1.104 metric 
100
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=70.0.1/20191031085722 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1723857] Re: onscreen keyboard appears whenever i touch touchscreen

[esauvisky]

Can confirm this issue is, yet again, back. It's definitely gnome-
shell's fault, and doesn't relates to Ubuntu, as I'm using gnome-shell
3.34 "classic" session under Arch Linux. So this bug should probably be
at GNOME team's watch.

As a sidenote, Block Caribou doesn't seem to work any longer as well.


** Also affects: gnome-shell (Arch Linux)
   Importance: Undecided
   Status: New

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

Title:
  onscreen keyboard appears whenever i touch touchscreen

Status in GNOME Shell:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Artful:
  Won't Fix
Status in gnome-shell package in Arch Linux:
  New

Bug description:
  Impact
  ==
  I'm in 17.10. Whenever I touch the touchscreen, the keyboard appears. It is 
disabled in System Preferences > Universal Access.  This didn't happen in any 
previous Ubuntus, including 17.04 GNOME, nor in Fedora, which is GNOME based.

  Test Case
  =
  0. Find a laptop with a touch screen that works.
  1. Settings > Universal Access > Typing > Screen Keyboard = OFF
  2. Touch the screen.

  Regression Potential
  

  Workaround
  ==
  https://extensions.gnome.org/extension/1326/block-caribou/

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

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

[Desktop-packages] [Bug 1482852] Re: apparmor profile usr.bin.firefox missing abstractions/ubuntu-helpers

[Jamie Strandboge]

** Package changed: apparmor (Ubuntu) => firefox (Ubuntu)

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

Title:
  apparmor profile usr.bin.firefox missing abstractions/ubuntu-helpers

Status in firefox package in Ubuntu:
  New

Bug description:
  When trying to open link to a torrent apparmor denies my bittorrent client.
  the log message I got is:

  audit: type=1400 audit(1439028251.208:1075): apparmor="DENIED"
  operation="exec" info="profile not found" error=-13
  profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/usr/bin
  /transmission-gtk" pid=32092 comm="firefox" requested_mask="x"
  denied_mask="x" fsuid=1000 ouid=0

  Although ubuntu-helpers is included in abstractions/ubuntu-bittorrent-clients
  to allow x access to transmission, firefox profile also need to include 
abstractions/ubuntu-helpers.

  It is also strange that when I add definition of ubuntu-helpers to
  usr.bin.firefox aa-enforce fails during bootup with message

  Multiple definitions for hat sanitized_helper in profile (null)
  exist,bailing out.

  but when I restart it it seam to set profiles OK with no error.

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

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

[Desktop-packages] [Bug 1853199] Re: Ctrl + c (copy) anywhere some times crashes gnome session

[Boris Rybalkin]

This one is definitely after the crash:
https://errors.ubuntu.com/oops/94669eda-2034-11ea-a701-fa163ee63de6

Strange thing that, file says Dec 16, 18:47:

tv@tv:/var/crash$ ll
total 22492
drwxrwsrwt  2 root whoopsie 4096 Dec 17 07:35 ./
drwxr-xr-x 15 root root 4096 Aug  8 08:05 ../
-rw-r-  1 gdm  whoopsie 23015251 Dec 16 18:47 
_usr_bin_gnome-shell.123.crash
-rw-r--r--  1 root whoopsie0 Dec 16 18:47 
_usr_bin_gnome-shell.123.upload
-rw---  1 whoopsie whoopsie   37 Dec 16 18:48 
_usr_bin_gnome-shell.123.uploaded

But report on my whoopsie page says:

OccurredReceivedProblem TypeProgram
2019-12-13 09:122019-12-16 18:12 UTCCrash   gnome-shell

Uploaded file content is the same.

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

Title:
  Ctrl + c (copy) anywhere some times crashes gnome session

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Copy text anwyhere (browser, terminal) crashes user session and shows login 
screen.
  It may take few login attempts to actually login back.

  I have HDMI Tv attached to a Shuttle pc with Intel graphics. Box is
  always ON but tv is ON amd OFF as needed. Every time I turn tv ON and
  try to do something and use ctrl + c it would restart gnome session.
  After login it seem to work fine and ctrl+c does not break anything.
  Then the next day the similar thing happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 20:55:37 2019
  DistUpgraded: 2019-10-26 19:58:25,451 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
     Subsystem: Holco Enterprise Co, Ltd/Shuttle Computer HD Graphics 630 
[1297:4057]
  InstallationDate: Installed on 2019-07-21 (121 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 006: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
   Bus 001 Device 002: ID 413c:2107 Dell Computer Corp. Dell USB Entry Keyboard
   Bus 001 Device 003: ID 25a7:2402 2.4G 2.4G Wireless Device
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Shuttle Inc. XH270
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic 
root=UUID=381b92c2-4c86-47ab-a37b-6e1f7a708bf7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (24 days ago)
  dmi.bios.date: 01/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: Default string
  dmi.board.name: FH270
  dmi.board.vendor: Shuttle Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd01/09/2018:svnShuttleInc.:pnXH270:pvr1.0:rvnShuttleInc.:rnFH270:rvr1.0:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: X
  dmi.product.name: XH270
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Shuttle Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1482852] [NEW] apparmor profile usr.bin.firefox missing abstractions/ubuntu-helpers

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When trying to open link to a torrent apparmor denies my bittorrent client.
the log message I got is:

audit: type=1400 audit(1439028251.208:1075): apparmor="DENIED"
operation="exec" info="profile not found" error=-13
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" name="/usr/bin
/transmission-gtk" pid=32092 comm="firefox" requested_mask="x"
denied_mask="x" fsuid=1000 ouid=0

Although ubuntu-helpers is included in abstractions/ubuntu-bittorrent-clients
to allow x access to transmission, firefox profile also need to include 
abstractions/ubuntu-helpers.

It is also strange that when I add definition of ubuntu-helpers to
usr.bin.firefox aa-enforce fails during bootup with message

Multiple definitions for hat sanitized_helper in profile (null)
exist,bailing out.

but when I restart it it seam to set profiles OK with no error.

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


** Tags: bittorrent-clients firefox patch ubuntu-helpers
-- 
apparmor profile usr.bin.firefox missing abstractions/ubuntu-helpers
https://bugs.launchpad.net/bugs/1482852
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to firefox 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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[BloodyIron]

Any word how long before this might hit main repos for 19.10?

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Triaged
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

  ---

  WORKAROUND

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

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

[Desktop-packages] [Bug 1856611] Re: Update 68.3.0 not in repo

[Olivier Tilloy]

** Changed in: thunderbird (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Update 68.3.0 not in repo

Status in thunderbird package in Ubuntu:
  In Progress

Bug description:
  https://www.thunderbird.net/en-US/thunderbird/68.3.0/releasenotes/
  https://www.mozilla.org/en-US/security/advisories/mfsa2019-38/

  Update 68.3.0 is not in Eoan repo yet.

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

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

[Desktop-packages] [Bug 1852874] Re: Version 78.0.3904.97 (Official Build) snap (64-bit) cannot connect to internet with VPN enabled. Connects fine with VPN disabled.

[Olivier Tilloy]

Note to self: to visualize the net-export log, use https://netlog-
viewer.appspot.com/.

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

Title:
  Version 78.0.3904.97 (Official Build) snap (64-bit) cannot connect to
  internet with VPN enabled. Connects fine with VPN disabled.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium Version 78.0.3904.70 (Official Build) snap (64-bit) on Ubuntu
  19.10, Intel® Core™ i7-8550U CPU @ 1.80GHz × 8, GeForce GTX
  1050/PCIe/SSE2. Since my upgrade to 19.10, snap chromium will not
  connect when VPN is enabled. Chromium does connect when VPN is
  disabled. Access NetworkManager service is enabled in chromium snap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 16 14:52:46 2019
  InstallationDate: Installed on 2019-10-05 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (21 days ago)

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

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

[Desktop-packages] [Bug 1852874] Re: Version 78.0.3904.97 (Official Build) snap (64-bit) cannot connect to internet with VPN enabled. Connects fine with VPN disabled.

[Olivier Tilloy]

Sorry for the lack of timely feedback Kevin. Has the latest update
(79.0.3945.79) resolved the problem, by any chance?

What is your setup like for DNS? Can you share the output of "cat
/etc/resolv.conf" ?

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

Title:
  Version 78.0.3904.97 (Official Build) snap (64-bit) cannot connect to
  internet with VPN enabled. Connects fine with VPN disabled.

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Chromium Version 78.0.3904.70 (Official Build) snap (64-bit) on Ubuntu
  19.10, Intel® Core™ i7-8550U CPU @ 1.80GHz × 8, GeForce GTX
  1050/PCIe/SSE2. Since my upgrade to 19.10, snap chromium will not
  connect when VPN is enabled. Chromium does connect when VPN is
  disabled. Access NetworkManager service is enabled in chromium snap.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser (not installed)
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 16 14:52:46 2019
  InstallationDate: Installed on 2019-10-05 (42 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: chromium-browser
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (21 days ago)

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

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

[Desktop-packages] [Bug 1580463] Re: Snap blocks access to system input methods (ibus, fcitx, ...)

[Jamie Strandboge]

@Gunnar - I am preparing the focal upload now, though there is a parser
bug (bug 1856738) which means I cannot use @{HOME} in the rule and
instead hardcode /home/*/. This will cover all typical situations (ie,
not the atypical /root/.cache/ibus...) except when the user updates
/etc/apparmor.d/tunables/home.d/ to add a different directory for home.
With snaps (this bug) we don't support alternate locations for /home
just yet, so this is not a regression.

We plan to fix that parser bug for 20.04. You may want to hold off on a
1.5.22 upload (or revert the XDG patch) until this is updated to avoid
regression non-snap, ibus abstraction apparmor users with non-default
home.

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

Title:
  Snap blocks access to system input methods (ibus, fcitx, ...)

Status in ibus:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in ibus package in Ubuntu:
  In Progress
Status in im-config package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Fix Released
Status in im-config source package in Xenial:
  Fix Released
Status in snapd source package in Xenial:
  Fix Released
Status in apparmor source package in Yakkety:
  Fix Released
Status in im-config source package in Yakkety:
  Fix Released
Status in snapd source package in Yakkety:
  Fix Released

Bug description:
  = SRU im-config =
  [Impact]
  ibus-daemon by default uses a unix socket name of /tmp/dbus-... that is 
indistinguishable from dbus-daemon abstract sockets. While dbus-daemon has 
AppArmor mediation, ibus-daemon does not so it is important that its abstract 
socket not be confused with dbus-daemon's. By modifying ibus-daemon's start 
arguments to use "--address 'unix:tmpdir=/tmp/ibus'" AppArmor can continue 
mediating DBus abstract sockets like normal and also mediate access to the 
ibus-daemon-specific abstract socket via unix rules. This also tidies up the 
abstract socket paths so that it is clear which are for ibus-daemon, which for 
dbus-daemon, etc.

  The upload simply adjusts 21_ibus.rc to start ibus-daemon with "--
  address 'unix:tmpdir=/tmp/ibus'" and adds a comment. No compiled code
  changes are required.

  [Test Case]
  1. start a unity session before updating to the package in -proposed

  2. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/dbus-Vyx8fGFA,guid=28e8e7e89f902c8d4e9d77c5557add76

  3. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 2973 jamie8u unix 0x  0t0   29606 
@/tmp/dbus-oxKYpN30 type=STREAM

  4. update the package in -proposed and perform '2' and '3'. The
  IBUS_ADDRESSES should be the same as before

  5. logout of unity, then log back in

  6. $ grep IBUS_ADDRESS ~/.config/ibus/bus/*-unix-0
  
IBUS_ADDRESS=unix:abstract=/tmp/ibus/dbus-SpxOl8Fc,guid=06d4bbeb07614c6dffbf221c57473f4e

  (notice '/tmp/ibus/' in the path)

  7. $ lsof -p $(pidof ibus-daemon) | grep '/dbus'
  ibus-daem 3471 jamie8u unix 0x  0t0  26107 
@/tmp/ibus/dbus-SpxOl8Fc type=STREAM
  ...

  (notice '@/tmp/ibus/' in the path)

  In addition to the above, you can test for regressions by opening
  'System Settings' under the 'gear' icon in the panel and selecting
  'Text Entry'. From there, add an input source on the right, make sure
  'Show current input source in the menu bar' is checked, then use the
  input source panel indicator to change input sources.

  Extended test case to verify input support still works in unconfined
  and confined applications:

  1. Systems Settings Language Support, if prompted install the complete 
language support
  2. Install Chinese (simple and traditional)
  3. sudo apt-get install ibus-pinyin ibus-sunpinyin
  4. logout / login
  5. System Settings / Text Entry - add Chinese (Pinyin) (IBus)
  6. select pinyin from the indicator
  7. sudo lsof | grep ibus | grep @ # will use @/tmp/dbus-...
  8. open gnome-calculator and try to type something in (should get a pop-up)
  9. open evince and try to search a pdf (should get a pop up)
  10. upgrade apparmor and im-config from xenial-proposed
  11. logout and back in
  12. sudo lsof | grep ibus | grep @ # will use @/tmp/ibus/...
  13. open gnome-calculator and try to type something in (should get a pop-up)
  14. open evince and try to search a pdf (should get a pop up)
  15. verify no new apparmor denials

  [Regression Potential]

  The regression potential is considered low because there are no
  compiled code changes and because the changes only occur after ibus-
  daemon is restarted, which is upon session start, not package upgrade.
  When it is restarted, the files in ~/.config/ibus/bus/*-unix-0 are
  updated accordingly for other applications to pick up.

  This change intentionally requires a change to the unity7 

[Desktop-packages] [Bug 1852828] Re: Firefox youtube videos do not start automatically, when selected

[Olivier Tilloy]

Sorry for the lack of timely feedback BertN45.
Are you still seeing this issue with the update to firefox 
71.0+build5-0ubuntu0.18.04.1 ?

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

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

Title:
  Firefox youtube videos do not start automatically, when selected

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When I select a youtube video, nothing happens. I have to stop and
  start the video to get it going. While it is stagnant, it slowly
  builds up its buffer till 2 minutes, but the video most left button
  displays, that it is running, but like I said, I have to stop and
  start it again. Chromium works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 70.0.1+build1-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bertadmin   2681 F pulseaudio
   /dev/snd/pcmC0D0p:   bertadmin   2681 F...m pulseaudio
   /dev/snd/timer:  bertadmin   2681 f pulseaudio
  BuildID: 20191031085722
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Fri Nov 15 20:45:24 2019
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2018-03-11 (614 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180310)
  IpRoute:
   default via 192.168.1.1 dev enp0s3 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000 
   192.168.1.0/24 dev enp0s3 proto kernel scope link src 192.168.1.104 metric 
100
  Locales: extensions.sqlite corrupt or missing
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:930
  PrefSources: prefs.js
  Profiles: Profile0 (Default) - LastVersion=70.0.1/20191031085722 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

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

[Desktop-packages] [Bug 1856611] Re: Update 68.3.0 not in repo

[Launchpad Bug Tracker]

** Branch linked: lp:thunderbird

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

Title:
  Update 68.3.0 not in repo

Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  https://www.thunderbird.net/en-US/thunderbird/68.3.0/releasenotes/
  https://www.mozilla.org/en-US/security/advisories/mfsa2019-38/

  Update 68.3.0 is not in Eoan repo yet.

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

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

[Desktop-packages] [Bug 1841762] Re: package nvidia-dkms-430 430.40-0ubuntu2 failed to install/upgrade: installed nvidia-dkms-430 package post-installation script subprocess returned error exit status

[Oleksandr Suvorov]

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

The issue is that patch "do-not-call-pci_save_state.patch" can't be
applied to nvidia/nv.c

Workaround (checked with 430.64, probably should work on other 430.x
versions):

1. Install broken package, get an error.
2. Go to nvidia source dir (like /usr/src/nvidia-430.64)
3. Remove from dkms.conf the line 'PATCH[1]="do-not-call-pci_save_state.patch"'
4. Build nvidia driver with dkms: dkms build -m nvidia -v 430.64
5. Install nvidia driver: sudo dkms install -m nvidia -v 430.64

Note, this patch doesn't need anymore as there is no more call of
pci_save_state() in nv_power_management().

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

Title:
  package nvidia-dkms-430 430.40-0ubuntu2 failed to install/upgrade:
  installed nvidia-dkms-430 package post-installation script subprocess
  returned error exit status 10

Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Confirmed

Bug description:
  Error window popped up without any intervention from me.

  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: nvidia-dkms-430 430.40-0ubuntu2
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  Date: Wed Aug 28 11:10:40 2019
  ErrorMessage: installed nvidia-dkms-430 package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-08-26 (1 days ago)
  InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 
(20190416.2)
  Python3Details: /usr/bin/python3.7, Python 3.7.4, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu1
   apt  1.9.3
  SourcePackage: nvidia-graphics-drivers-430
  Title: package nvidia-dkms-430 430.40-0ubuntu2 failed to install/upgrade: 
installed nvidia-dkms-430 package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to eoan on 2019-08-28 (0 days ago)

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

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

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

[Seth Forshee]

https://lists.ubuntu.com/archives/kernel-team/2019-December/106438.html

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

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

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

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

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

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

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1856731] [NEW] Cannot add a Google accounts with GOA

[Heather Ellsworth]

Public bug reported:

On a freshly installed 20.04 system, going through the initial setup and
I'm presented with the Online Accounts panel where I selected Google,
entered my email and password. Then Google's 2-factor authentication
kicks in and instructs me to check my phone. I do and approve the
connection, but the online accounts page on the laptop never updates
until it eventually asks if I want the authentication to be resent.

There are two older bugs that looks like this - both are fix committed:
- https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1687019
- https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1175122

Opening a new bug since the issue definitely exists and the other bugs
have been fix committed for years.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-online-accounts 3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu14
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Dec 17 09:17:06 2019
InstallationDate: Installed on 2019-12-17 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Cannot add a Google accounts with GOA

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  On a freshly installed 20.04 system, going through the initial setup
  and I'm presented with the Online Accounts panel where I selected
  Google, entered my email and password. Then Google's 2-factor
  authentication kicks in and instructs me to check my phone. I do and
  approve the connection, but the online accounts page on the laptop
  never updates until it eventually asks if I want the authentication to
  be resent.

  There are two older bugs that looks like this - both are fix committed:
  - https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1687019
  - https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1175122

  Opening a new bug since the issue definitely exists and the other bugs
  have been fix committed for years.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-online-accounts 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu14
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 17 09:17:06 2019
  InstallationDate: Installed on 2019-12-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1687019] Re: Cannot add a Google account using Online Accounts in Ubuntu Gnome

[Heather Ellsworth]

** Also affects: webkit2gtk (Ubuntu Focal)
   Importance: High
   Status: Fix Released

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

Title:
  Cannot add a Google account using Online Accounts in Ubuntu Gnome

Status in gnome-online-accounts:
  Unknown
Status in Ubuntu GNOME:
  Fix Released
Status in WebKit:
  Fix Released
Status in webkit2gtk package in Ubuntu:
  Fix Released
Status in webkit2gtk source package in Xenial:
  Fix Released
Status in webkit2gtk source package in Yakkety:
  Fix Released
Status in webkit2gtk source package in Zesty:
  Fix Released
Status in webkit2gtk source package in Focal:
  Fix Released
Status in webkit2gtk package in Debian:
  Fix Released

Bug description:
  Impact
  -
  Users will be unable to log in to a Google account using GNOME Online Account 
which is used by default in Ubuntu GNOME and Ubuntu Budgie.

  Any other browser or service that uses webkit2gtk is similarly broken,
  such as the Epiphany browser.

  The second issue fixed here is that any user who opted in to the new
  YouTube will only get a white screen when they attempt to visit
  YouTube. The new YouTube is still opt-in now but will eventually
  become the default for everyone.

  Test Case
  -
  1. Install the updated webkit2gtk on Ubuntu GNOME.
  2. Restart your computer (this may be necessary because of LP: #1610944)
  3. Log in. Open Settings>Online Accounts. Remove any Google accounts already 
configured. Add your Google account.
  4. Install Evolution if it's not already installed and verify that your Gmail 
account loads.

  Optional, because the beta is closed to new entrants:
  5. Install epiphany-browser
  6. Open the Web app (epiphany-browser) and log in to your Google account.
  7. Visit https://www.google.com/new to make sure that your browser is set to 
use the "new YouTube."
  8. If the new YouTube only shows a white screen, this part of the bug is not 
fixed.

  Regression Potential
  
  The regression potential was limited by only cherry-picking the commits to 
fix these 2 high-profile issues. 2.16.2 is being rolled out to most distros now.

  Other Info
  --
  Fixed in 17.10 Alpha "artful" by updating to 2.16.2

  Original Bug Report
  ---
  With Ubuntu Gnome 17.04 (brand new 64bit install on a Dell XPS13 laptop), I 
cannot add a Google account using Online-Accounts. If I choose to add a new 
Google account in Online Accounts, a window appears where I can enter my Google 
email. After entering my email and pressing the Next button, a window appears 
where I can enter my Google password. After entering the password and pressing 
the Next button, an empty window appears and nothing else happens. I expected 
this to show something useful, and actually add the Google account to my Gnome 
environment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1687019/+subscriptions

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

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

[Seth Forshee]

** Description changed:

+ SRU Justification
+ 
+ Impact: The nvidia-435 drivers are missing from linux-restricted-modules
+ in eoan. On install ubuntu-drivers picks 435 as the newest version, and
+ users must use self-signed dkms drivers and enroll a MOK.
+ 
+ Fix: Add nvidia-435 dkms builds to linux and l-r-m for eoan.
+ 
+ Test Case: A test build is available in ppa:sforshee/test-builds. Verify
+ that signed drivers for nvidia-435 can be installed for eoan via the
+ linux-modules-nvidia-435-{generic,lowlatency} packages.
+ 
+ Regression Potential: The nvidia-435 l-r-m drivers are new packages
+ built from the same source as the nvidia-435 dkms driver, so regressions
+ are unlikely.
+ 
+ ---
+ 
  The linux-restricted-modules package exists so that users who install
  the nvidia drivers can get known-good, signed modules instead of having
  to locally self-sign and enroll a signing key through MOK.  But lrm in
  eoan is only building driver packages for nvidia 390 and 430, and nvidia
  435 is present in eoan.
  
  So on a new Ubuntu 19.10 install, ubuntu-drivers is picking 435 as the
  newest driver instead of using the signed 430 driver.
  
  We should never allow the archive to get into this situation.  We should
  be enforcing that any version of the nvidia driver that we expect
  ubuntu-drivers to install by default on any hardware is integrated into
  linux-restricted-modules, and we should ensure that ubuntu-drivers
  always prefers the signed drivers over other options.

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

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

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

Bug description:
  SRU Justification

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

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

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

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

  ---

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

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

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

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

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

[Desktop-packages] [Bug 1850064] Re: Please upgrade it to 68.x on Ubuntu 18.04 LTS

[Olivier Tilloy]

I'm very sorry for the trouble you had to go through to restore a
working thunderbird.

As I wrote in comment #18, I don't know where that apparmor profile for
thunderbird comes from, not from the archive it seems. So I'm reluctant
to taking action until I understand better where this comes from, and
how many users are potentially affected. But I'll keep an eye on the
issue, for sure.

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

Title:
  Please upgrade it to 68.x on Ubuntu 18.04 LTS

Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released

Bug description:
  Now the official upgrade way from 60 to 68 got open by mozilla.

  Plus there are security fixes and performance enhancements.
  
https://www.mozilla.org/en-US/security/known-vulnerabilities/thunderbird/#thunderbird68.2

  NOTE TO SRU TEAM: Please do not release this package without
  consulting first. This is a security update pushed via -proposed to
  get a bit more testing. Will be released via it's own processes.

  Packages that are part of this security update: thunderbird, mozilla-
  devscripts, jsunit and enigmail.

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

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

[Desktop-packages] [Bug 1853731] Re: [snap] chromium stops working after a while, fails to render new tabs/pages

[Olivier Tilloy]

This sounds like it might be a problem specific to the NVidia card. Can
you open chrome://gpu in chromium, save the page and share it here?

Also, can you run chromium from the command line with "chromium
--enable-logging=stderr", let it run until the problem happens, and
share the output from that terminal?

Thanks!

** Summary changed:

- chromium snap stops working after awhile, fails to render new tabs/pages
+ [snap] chromium stops working after a while, fails to render new tabs/pages

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

Title:
  [snap] chromium stops working after a while, fails to render new
  tabs/pages

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more 
stable way for all
Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: beta
  refresh-date: 2 days ago, at 15:17 AEDT
  channels:
stable:78.0.3904.108 2019-11-21 (949) 160MB -
candidate: 78.0.3904.108 2019-11-22 (952) 160MB -
beta:  79.0.3945.45  2019-11-22 (951) 155MB -
edge:  80.0.3962.2   2019-11-11 (945) 155MB -
  installed:   79.0.3945.45 (951) 155MB -

  I recently upgraded to Ubuntu 19.10. I have an old Nvidia card which
  relies on the 340 drivers, so I cannot use Wayland.

  I can launch Chromium browser ok, but then, after what seems like an
  interdeterminate period of time, new "things" will fail to render in
  the interface, and the only solution is to killall chrome.

  When the issue kicks in, existing webpages are fine, but following fail:
  * Navigate to a new web page (tab is blank)
  * Open a new tab (tab is blank)
  * Open a new window (entire window is blank)

  Chromium continues to respond to keystrokes, and you can see it
  loading things in the status bar, just the display does not render.
  Killing chromium and restarting it works until it happens again.

  I understand this is vague and would appreciate information on how to
  report problems with the chromium snap. apport tells me it can't do
  it, because it's a snap. Am happy to supply additional info if it
  happens again, as long as I know what I need to report.

  I switched to the beta snap after experiencing the problem with the stable 
snap.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/sdc1  ext4   2.7T  865G  1.8T  34% /home
   tmpfs  tmpfs  3.9G  103M  3.8G   3% /dev/shm
   /dev/sdc1  ext4   2.7T  865G  1.8T  34% /home
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2016-01-21 (1422 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: Gigabyte Technology Co., Ltd. P55A-UD4
  NonfreeKernelModules: nvidia
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-25-generic 
root=UUID=c8c5f257-b889-41be-8ee5-fbb3abe7711e ro nomodeset quiet splash 
vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-25.27-generic 5.3.13
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan snap
  Uname: Linux 5.3.0-25-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-02 (42 days ago)
  UserGroups: adm cdrom dialout dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/16/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F15
  dmi.board.name: P55A-UD4
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF15:bd09/16/2010:svnGigabyteTechnologyCo.,Ltd.:pnP55A-UD4:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP55A-UD4:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P55A-UD4
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2018-11-10T13:06:57.396750

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

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

[Desktop-packages] [Bug 1855736] Re: Duplicity fails to start

[Kenneth Loafman]

OK, what's happening is two factor:

1) Something in setup is changing the shebang line to Python 2 and,
2) It's libraries are being installed on Python 3.

which means duplicity can't find its libraries.

Please run the following:

$ find /usr -type d -name duplicity -ls
$ find /usr -type f -name duplicity -ls

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

Title:
  Duplicity fails to start

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

Bug description:
  I am on 19.10.  Duplicity crashes as soon as I try to start a backup,
  as below. It was running fine on 19.04.

  Traceback (innermost last):
File "/usr/bin/duplicity", line 107, in 
  with_tempdir(main)
File "/usr/bin/duplicity", line 93, in with_tempdir
  fn()
File "/usr/lib/python3/dist-packages/duplicity/dup_main.py", line 1522, in 
main
  action = commandline.ProcessCommandLine(sys.argv[1:])
File "/usr/lib/python3/dist-packages/duplicity/commandline.py", line 1200, 
in ProcessCommandLine
  globals.backend = backend.get_backend(args[0])
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 225, in 
get_backend
  obj = get_backend_object(url_string)
File "/usr/lib/python3/dist-packages/duplicity/backend.py", line 211, in 
get_backend_object
  return factory(pu)
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", 
line 81, in __init__
  ensure_dbus()
File "/usr/lib/python3/dist-packages/duplicity/backends/giobackend.py", 
line 37, in ensure_dbus
  lines = output.split(u'\n')
   TypeError: a bytes-like object is required, not 'str'

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

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

[Desktop-packages] [Bug 1856611] Re: Update 68.3.0 not in repo

[Olivier Tilloy]

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

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

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

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

Title:
  Update 68.3.0 not in repo

Status in thunderbird package in Ubuntu:
  Triaged

Bug description:
  https://www.thunderbird.net/en-US/thunderbird/68.3.0/releasenotes/
  https://www.mozilla.org/en-US/security/advisories/mfsa2019-38/

  Update 68.3.0 is not in Eoan repo yet.

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

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

[Desktop-packages] [Bug 1856624] Re: Firefox freezes temporarily at 100% CPU when Chromium is opened

[Olivier Tilloy]

I am unable to observe the issue in a virtual machine, launching
chromium-browser while firefox is running doesn't make it unresponsive.

This sounds like it could be a shortage of memory where your system
starts swapping, thus making firefox unresponsive for a while. How much
RAM do you have, and do you have swap set up?

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

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

Title:
  Firefox freezes temporarily at 100% CPU when Chromium is opened

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  When Firefox is open, and I open Chromium, many features of Firefox
  fail to work for several seconds. (To reproduce, start with neither
  Firefox nor Chromium open; open Firefox, and allow one or more web
  pages to load; then open Chromium; the issue starts a second or two
  after Chromium is opened.) This is a temporary issue, lasting for
  several seconds; the length of time it lasts appears to depend on how
  many open tabs have been viewed since Firefox opened (on my computer,
  around 10 seconds with 1 tab having been viewed, around a minute with
  10 tabs having been viewed). This reproduces even when running Firefox
  as `firefox -safe-mode`.

  While the issue is ongoing (i.e. starting around a second after Chromium is 
open, and persisting for typically tens of seconds), some features of Firefox 
work, but most do not:
  - Scrolling the current tab short distances succeeds, showing the expected 
text on the page.
  - Scrolling the current tab long distances (several screeenfuls) causes the 
page to be "cut off" past a certain point, with only a blank background 
rendering.
  - Moving the mouse cursor over a link does not change the mouse cursor 
(expected behaviour, and behaviour while the issue is not ongoing, is for it to 
change to a hand shape).
  - Changing tab causes the resulting page not to display: rather, a grey 
background is displayed, and sometimes a loading spinner.
  - Changing tab back then causes the original page not to render, as if it 
were new, despite the fact it was correctly displayed earlier.
  - The address bar functions as normal; the issue does not appear to affect 
address bar functionality.
  Additionally, while the issue is ongoing, Firefox uses 100% CPU.

  At some point after the issue in question starts, it stops, and all
  Firefox features return to normal (including any missing or
  incorrectly rendered page content, which renders again when the issue
  ends).

  The trigger is specifically the act of opening Chromium: Firefox can
  function just fine once the issue ends, even if Chromium is still
  open, and functions just fine if Chromium is opened first.

  I have an (unconfirmed) theory that opening Chromium is causing some
  operation within Firefox to become very slow, using up all the CPU
  time, and the other observed misbehaviours within Firefox are a
  consequence of how slowly it is running; however, I've listed them all
  anyway in case it provides clarity into what the specific nature of
  the bug is.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: firefox 71.0+build5-0ubuntu0.18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ais523 1800 F pulseaudio
  BuildID: 20191205184924
  Channel: Unavailable
  CurrentDesktop: X-Cinnamon
  Date: Tue Dec 17 00:29:10 2019
  ExecutablePath: /usr/lib/firefox/firefox
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions:
   English (South Africa) Language Pack - langpack-en...@firefox.mozilla.org
   Français Language Pack - langpack...@firefox.mozilla.org
   English (GB) Language Pack - langpack-en...@firefox.mozilla.org
   Default - {972ce4c6-7e08-4474-a285-3208198ce6fd}
  InstallationDate: Installed on 2019-11-11 (35 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.101 metric 
600
  MostRecentCrashID: bp-935fd166-3720-454f-8fe5-0a1752140227
  PrefErrors: Unexpected character ',' before close parenthesis @ 
/usr/lib/firefox/omni.ja:greprefs.js:722
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=71.0/20191205184924 (In use)
  RunningIncompatibleAddons: True
  SourcePackage: firefox
  UpgradeStatus: 

[Desktop-packages] [Bug 1855889] Re: Can't run Chromium since upgrade to Ubuntu 19.10

[Olivier Tilloy]

Where is your $HOME directory?

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

Title:
  Can't run Chromium since upgrade to Ubuntu 19.10

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I try to run Chromium from the menu and nothing happens.
  If I run it from the CLI I get:
  cannot perform operation: mount --rbind /root /tmp/snap.rootfs_vWwNbw//root: 
Permission denied

  I tried uninstalling and reinstalling. I tried uninstalling and
  reinstalling snapd. Tried anything related I could find on-line, but
  nothing works.

  Upgrade snap to the latest version on the pre-release channel.

  For some reason Chromium does not show up in the Software centre
  either.

  Thanks for any help.

  $ lsb_release  -rd
  Description:  Ubuntu 19.10
  Release:  19.10

  $ snap list chromium
  Name  VersionRev  Tracking  Publisher   Notes
  chromium  78.0.3904.108  958  stablecanonicalâ  -

  $ apt-cache policy chromium-browser
  chromium-browser:
Installed: 77.0.3865.120-0ubuntu1.19.10.1
Candidate: 77.0.3865.120-0ubuntu1.19.10.1
Version table:
   *** 77.0.3865.120-0ubuntu1.19.10.1 500
  500 http://mirror.overthewire.com.au/ubuntu eoan-updates/universe 
amd64 Packages
  100 /var/lib/dpkg/status
   77.0.3865.120-0ubuntu1~snap1 500
  500 http://mirror.overthewire.com.au/ubuntu eoan/universe amd64 
Packages

  
  $ snap list chromium
  Name  VersionRev  Tracking  Publisher   Notes
  chromium  78.0.3904.108  958  stablecanonicalâ  -

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonicalâ
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more 
stable way for all
Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  refresh-date: today at 23:00 ACST
  channels:
stable:78.0.3904.108 2019-11-25 (958) 160MB -
candidate: 78.0.3904.108 2019-11-22 (952) 160MB -
beta:  79.0.3945.74  2019-12-06 (966) 155MB -
edge:  80.0.3983.2   2019-12-05 (964) 156MB -
  installed:   78.0.3904.108(958) 160MB

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

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

[Desktop-packages] [Bug 1853112] Re: Applications are closed when killing the Shell (like on a hang)

[Sebastien Bacher]

** Tags removed: rls-ff-incoming

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

Title:
  Applications are closed when killing the Shell (like on a hang)

Status in gnome-shell package in Ubuntu:
  Triaged
Status in gnome-shell source package in Focal:
  Triaged

Bug description:
  - Open some non dbus activated apps (so, not terminal for instance) in your 
dock
  - Kill the shell with SIGKILL
  - Applications are being killed with the Shell being killed, apart from the 
dbus activated ones.

  This wasn't the case before 19.10 on X11. (caused by dbus user
  session?)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7
  Uname: Linux 5.3.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 19 09:42:11 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-05-24 (543 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2019-01-08 (314 days ago)

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

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

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

[Martin Wimpress]

Assign Seth Forshee during the desktop team meeting in #ubuntu-desktop
on December 17th. If it turns out these assignments are incorrect we can
reassign them.

** Changed in: nvidia-graphics-drivers-435 (Ubuntu Eoan)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: ubuntu-drivers-common (Ubuntu Eoan)
 Assignee: (unassigned) => Seth Forshee (sforshee)

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

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

Status in linux package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Confirmed
Status in ubuntu-drivers-common package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  In Progress
Status in linux-restricted-modules source package in Eoan:
  In Progress
Status in nvidia-graphics-drivers-435 source package in Eoan:
  Confirmed
Status in ubuntu-drivers-common source package in Eoan:
  Confirmed

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

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

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

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

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

[Desktop-packages] [Bug 1856718] Re: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking

[Seija Kijin]

** Attachment added: "nmap.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313411/+files/nmap.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/1856718

Title:
  CUPS server has an internal error whenever I attempt to add my HP
  OfficeJet8600 printer to configured devices via networking

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to add my HP OfficeJet8600 printer and configure it
  for printing on my Ubuntu PC, CUPS has an internal error and it is
  unable to configure the device or install drivers.

  This happened when I ran "system-config-printer" and selected the
  printer from the list of network printers and clicked "Forward"

  Instead of configuring the printer and installing drivers, CUPS had an
  error.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 09:37:45 2019
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Martin Wimpress]

** Changed in: gnome-session (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Incomplete
Status in gnome-session source package in Eoan:
  Incomplete
Status in gnome-shell source package in Eoan:
  Incomplete

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1856718] Re: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking

[Seija Kijin]

** Attachment added: "dnssd.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313412/+files/dnssd.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/1856718

Title:
  CUPS server has an internal error whenever I attempt to add my HP
  OfficeJet8600 printer to configured devices via networking

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to add my HP OfficeJet8600 printer and configure it
  for printing on my Ubuntu PC, CUPS has an internal error and it is
  unable to configure the device or install drivers.

  This happened when I ran "system-config-printer" and selected the
  printer from the list of network printers and clicked "Forward"

  Instead of configuring the printer and installing drivers, CUPS had an
  error.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 09:37:45 2019
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1856718] Re: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking

[Seija Kijin]

** Attachment added: "access_log.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313417/+files/access_log.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/1856718

Title:
  CUPS server has an internal error whenever I attempt to add my HP
  OfficeJet8600 printer to configured devices via networking

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to add my HP OfficeJet8600 printer and configure it
  for printing on my Ubuntu PC, CUPS has an internal error and it is
  unable to configure the device or install drivers.

  This happened when I ran "system-config-printer" and selected the
  printer from the list of network printers and clicked "Forward"

  Instead of configuring the printer and installing drivers, CUPS had an
  error.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 09:37:45 2019
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1856718] Re: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking

[Seija Kijin]

** Attachment added: "lpinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313413/+files/lpinfo.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/1856718

Title:
  CUPS server has an internal error whenever I attempt to add my HP
  OfficeJet8600 printer to configured devices via networking

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to add my HP OfficeJet8600 printer and configure it
  for printing on my Ubuntu PC, CUPS has an internal error and it is
  unable to configure the device or install drivers.

  This happened when I ran "system-config-printer" and selected the
  printer from the list of network printers and clicked "Forward"

  Instead of configuring the printer and installing drivers, CUPS had an
  error.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 09:37:45 2019
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1847514] Re: libssh-0.8 is detected as 0.7

[Martin Wimpress]

** Tags added: rls-bb-notfixing

** Tags removed: bionic

** No longer affects: libssh (Ubuntu Bionic)

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

Title:
  libssh-0.8 is detected as 0.7

Status in libssh package in Ubuntu:
  Fix Released

Bug description:
  QEMU consumes the library and its configure script use the libssh pkg-config 
cflags.
  The it checks if ssh_get_server_publickey() is present and assume it is a 
libssh-0.8 based.

  Ubuntu libssh is not based on upstream 0.8 but on the 0.7 branch, with commit 
bbd052202 cherry-picked. This commit adds the ssh_get_server_publickey() 
function that QEMU uses to check 0.8 compatibility.
  Now commit 963c46e4f is present in libssh-0.8 but has not been cherry-picked 
by Ubuntu, so QEMU fails at compiling because the ssh_known_hosts_e enums this 
commit introduced are missing.

  QEMU tracker is https://bugs.launchpad.net/qemu/+bug/1838763

  How to reproduce:

  - install libssh-dev

  - try to build QEMU 4.1 (sources from
  https://www.qemu.org/download/#source)

  $ ./configure
  ...
  libssh support yes
  ...

  $ make
  ...
CC block/ssh.o
  block/ssh.c: In function 'check_host_key_knownhosts':
  block/ssh.c:281:28: error: storage size of 'state' isn't known
   enum ssh_known_hosts_e state;
  ^
  block/ssh.c:289:13: error: implicit declaration of function 
'ssh_session_is_known_server' [-Werror=implicit-function-declaration]
   state = ssh_session_is_known_server(s->session);
   ^~~
  block/ssh.c:289:13: error: nested extern declaration of 
'ssh_session_is_known_server' [-Werror=nested-externs]
  block/ssh.c:293:10: error: 'SSH_KNOWN_HOSTS_OK' undeclared (first use in this 
function); did you mean 'SSH_OPTIONS_HOSTKEYS'?
   case SSH_KNOWN_HOSTS_OK:
^~
SSH_OPTIONS_HOSTKEYS
  block/ssh.c:293:10: note: each undeclared identifier is reported only once 
for each function it appears in
  block/ssh.c:297:10: error: 'SSH_KNOWN_HOSTS_CHANGED' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_OK'?
   case SSH_KNOWN_HOSTS_CHANGED:
^~~
SSH_KNOWN_HOSTS_OK
  block/ssh.c:301:48: error: 'SSH_PUBLICKEY_HASH_SHA256' undeclared (first use 
in this function); did you mean 'SSH_PUBLICKEY_HASH_SHA1'?
   r = ssh_get_publickey_hash(pubkey, SSH_PUBLICKEY_HASH_SHA256,
  ^
  SSH_PUBLICKEY_HASH_SHA1
  block/ssh.c:307:27: error: implicit declaration of function 
'ssh_get_fingerprint_hash'; did you mean 'ssh_get_pubkey_hash'? 
[-Werror=implicit-function-declaration]
   fingerprint = ssh_get_fingerprint_hash(SSH_PUBLICKEY_HASH_SHA256,
 ^~~~
 ssh_get_pubkey_hash
  block/ssh.c:307:27: error: nested extern declaration of 
'ssh_get_fingerprint_hash' [-Werror=nested-externs]
  block/ssh.c:324:10: error: 'SSH_KNOWN_HOSTS_OTHER' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_OK'?
   case SSH_KNOWN_HOSTS_OTHER:
^
SSH_KNOWN_HOSTS_OK
  block/ssh.c:329:10: error: 'SSH_KNOWN_HOSTS_UNKNOWN' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_CHANGED'?
   case SSH_KNOWN_HOSTS_UNKNOWN:
^~~
SSH_KNOWN_HOSTS_CHANGED
  block/ssh.c:333:10: error: 'SSH_KNOWN_HOSTS_NOT_FOUND' undeclared (first use 
in this function); did you mean 'SSH_KNOWN_HOSTS_UNKNOWN'?
   case SSH_KNOWN_HOSTS_NOT_FOUND:
^
SSH_KNOWN_HOSTS_UNKNOWN
  block/ssh.c:337:10: error: 'SSH_KNOWN_HOSTS_ERROR' undeclared (first use in 
this function); did you mean 'SSH_KNOWN_HOSTS_OTHER'?
   case SSH_KNOWN_HOSTS_ERROR:
^
SSH_KNOWN_HOSTS_OTHER
  block/ssh.c:281:28: error: unused variable 'state' [-Werror=unused-variable]
   enum ssh_known_hosts_e state;
  ^
  cc1: all warnings being treated as errors
  rules.mak:69: recipe for target 'block/ssh.o' failed
  make: *** [block/ssh.o] Error 1

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libssh-dev 0.8.0~20170825.94fa1e38-1ubuntu0.2
  Uname: Linux 5.2.17-200.fc30.x86_64 x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Oct  9 18:21:25 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
  SourcePackage: libssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1856718] Re: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking

[Seija Kijin]

** Attachment added: "ping.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313410/+files/ping.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/1856718

Title:
  CUPS server has an internal error whenever I attempt to add my HP
  OfficeJet8600 printer to configured devices via networking

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to add my HP OfficeJet8600 printer and configure it
  for printing on my Ubuntu PC, CUPS has an internal error and it is
  unable to configure the device or install drivers.

  This happened when I ran "system-config-printer" and selected the
  printer from the list of network printers and clicked "Forward"

  Instead of configuring the printer and installing drivers, CUPS had an
  error.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 09:37:45 2019
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1856718] Re: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking

[Seija Kijin]

** Attachment added: "ifconfig.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313414/+files/ifconfig.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/1856718

Title:
  CUPS server has an internal error whenever I attempt to add my HP
  OfficeJet8600 printer to configured devices via networking

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to add my HP OfficeJet8600 printer and configure it
  for printing on my Ubuntu PC, CUPS has an internal error and it is
  unable to configure the device or install drivers.

  This happened when I ran "system-config-printer" and selected the
  printer from the list of network printers and clicked "Forward"

  Instead of configuring the printer and installing drivers, CUPS had an
  error.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 09:37:45 2019
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.

[Sebastien Bacher]

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: gnome-shell (Ubuntu Eoan)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  [nvidia] Automatic login fails and then all subsequent logins fail.
  Killing gnome-session-binary fixes it, or just not using automatic
  login.

Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-session package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gdm3 source package in Eoan:
  Incomplete
Status in gnome-session source package in Eoan:
  Incomplete
Status in gnome-shell source package in Eoan:
  Incomplete

Bug description:
  I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM
  login screen (which I shouldn't; I have auto login enabled), and
  logging in just takes me back to the same user selection screen even
  though the password is correct.

  If I switch to a TTY and run `sudo pkill gnome-session-binary`,
  logging in through GDM starts working again.

  I should add that the do-release-upgrade was rocky; I did it in a
  terminal from within gnome, went away for a while, and when I
  returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo
  dpkg --configure -a` and complete the upgrade, but I don't know if
  something's still messed up due to that.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4]
  InstallationDate: Installed on 2019-09-14 (13 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: MSI MS-7A67
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2.60
  dmi.board.asset.tag: Default string
  dmi.board.name: H270I GAMING PRO AC (MS-7A67)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A67
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1856718] Re: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking

[Seija Kijin]

** Attachment added: "route.txt"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1856718/+attachment/5313416/+files/route.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/1856718

Title:
  CUPS server has an internal error whenever I attempt to add my HP
  OfficeJet8600 printer to configured devices via networking

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to add my HP OfficeJet8600 printer and configure it
  for printing on my Ubuntu PC, CUPS has an internal error and it is
  unable to configure the device or install drivers.

  This happened when I ran "system-config-printer" and selected the
  printer from the list of network printers and clicked "Forward"

  Instead of configuring the printer and installing drivers, CUPS had an
  error.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 09:37:45 2019
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1856718] Re: CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking

[Seija Kijin]

Here is the thing: the printer works when I am sending from a laptop
running windows or macOS. Only ubuntu has this issue.

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

Title:
  CUPS server has an internal error whenever I attempt to add my HP
  OfficeJet8600 printer to configured devices via networking

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to add my HP OfficeJet8600 printer and configure it
  for printing on my Ubuntu PC, CUPS has an internal error and it is
  unable to configure the device or install drivers.

  This happened when I ran "system-config-printer" and selected the
  printer from the list of network printers and clicked "Forward"

  Instead of configuring the printer and installing drivers, CUPS had an
  error.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 09:37:45 2019
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1849773] Re: /usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection

[Sebastien Bacher]

** Changed in: poppler (Ubuntu Eoan)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  
/usr/bin/evince:11:strstr:TextSelectionPainter::hasGlyphLessFont:TextSelectionPainter::endPage:TextPage::drawSelection:poppler_page_render_selection

Status in poppler package in Ubuntu:
  Fix Released
Status in poppler source package in Eoan:
  In Progress

Bug description:
  [Impact]
  Selecting text in evince crashes for some files in eoan

  [Test case]

  Open the pdf in bug 1855596 and select some text.

  [Regression potential]
  This adds a check for a null pointer before using the pointer; it's limited 
to a small function checking if a font is glyphless so there is basically no 
risk for regressio

  [Error tracker]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
evince.  This problem was most recently seen with package version 3.34.1-1, the 
problem page at 
https://errors.ubuntu.com/problem/da5fffc9beac869c0cf863d931ef170c60bb7d93 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1637988] Re: Enable the nfs backend

[Martin Wimpress]

Following a discussion on December 17th in #ubuntu-desktop by the
desktop team we have determine this issue won't be resolved in 18.04.

** Changed in: gvfs (Ubuntu Bionic)
   Status: Fix Committed => Won't Fix

** Changed in: gvfs (Ubuntu Cosmic)
   Status: Fix Committed => Won't Fix

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

Title:
  Enable the nfs backend

Status in gvfs package in Ubuntu:
  Fix Released
Status in gvfs source package in Bionic:
  Won't Fix
Status in gvfs source package in Cosmic:
  Won't Fix

Bug description:
  * Impact
  The gio/nautilus nfs:// locations handling is missing

  * Test case
  Try to connect to/browse a nfs server from nautilus by using a nfs:// location

  * Regression potential
  It's a new backend being enabled, it shouldn't have an impact on the existing 
ones

  Note that the backend relies on libnfs which got promoted in disco and
  would need to be promoted in cosmic/bionic as well then

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

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

[Desktop-packages] [Bug 1856691] Re: libpulse-mainloop-glib0:i386 cannot be installed

[Julian]

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

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

Title:
  libpulse-mainloop-glib0:i386 cannot be installed

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  libpulse-mainloop-glib0:i386 cannot be installed because it needs
  libpulse0:i386 (= 1:11.1-1ubuntu7.4), but 1:11.1-1ubuntu7.5 is
  installed. I am running Linux Mint 19.2 which is using the Ubuntu
  bionic packages.

  user@computer:$ sudo apt policy libpulse-mainloop-glib0:i386
  libpulse-mainloop-glib0:i386:
Installiert:   (keine)
Installationskandidat: 1:11.1-1ubuntu7.4
Versionstabelle:
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$ sudo apt policy libpulse0:i386
  libpulse0:i386:
Installiert:   1:11.1-1ubuntu7.5
Installationskandidat: 1:11.1-1ubuntu7.5
Versionstabelle:
   *** 1:11.1-1ubuntu7.5 100
  100 /var/lib/dpkg/status
   1:11.1-1ubuntu7.4 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 
Packages
   1:11.1-1ubuntu7 500
  500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
  user@computer:$

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

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

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

[Seija Kijin]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1856480/+attachment/5313406/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

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

[Seija Kijin]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1856480/+attachment/5313408/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1856691] [NEW] libpulse-mainloop-glib0:i386 cannot be installed

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

libpulse-mainloop-glib0:i386 cannot be installed because it needs
libpulse0:i386 (= 1:11.1-1ubuntu7.4), but 1:11.1-1ubuntu7.5 is
installed. I am running Linux Mint 19.2 which is using the Ubuntu bionic
packages.

user@computer:$ sudo apt policy libpulse-mainloop-glib0:i386
libpulse-mainloop-glib0:i386:
  Installiert:   (keine)
  Installationskandidat: 1:11.1-1ubuntu7.4
  Versionstabelle:
 1:11.1-1ubuntu7.4 500
500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 Packages
 1:11.1-1ubuntu7 500
500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
user@computer:$ sudo apt policy libpulse0:i386
libpulse0:i386:
  Installiert:   1:11.1-1ubuntu7.5
  Installationskandidat: 1:11.1-1ubuntu7.5
  Versionstabelle:
 *** 1:11.1-1ubuntu7.5 100
100 /var/lib/dpkg/status
 1:11.1-1ubuntu7.4 500
500 http://ubuntu.unitedcolo.de/ubuntu bionic-updates/main i386 Packages
 1:11.1-1ubuntu7 500
500 http://ubuntu.unitedcolo.de/ubuntu bionic/main i386 Packages
user@computer:$

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


** Tags: bot-comment
-- 
libpulse-mainloop-glib0:i386 cannot be installed
https://bugs.launchpad.net/bugs/1856691
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to pulseaudio 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 1856480] ProcModules.txt

[Seija Kijin]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1856480/+attachment/5313407/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1856480] modified.conffile..etc.apport.crashdb.conf.txt

[Seija Kijin]

apport information

** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt"
   
https://bugs.launchpad.net/bugs/1856480/+attachment/5313409/+files/modified.conffile..etc.apport.crashdb.conf.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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  

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

[Seija Kijin]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1856480/+attachment/5313405/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1856480] ProcCpuinfo.txt

[Seija Kijin]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1856480/+attachment/5313404/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1856480] Locale.txt

[Seija Kijin]

apport information

** Attachment added: "Locale.txt"
   https://bugs.launchpad.net/bugs/1856480/+attachment/5313401/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1856480] CurrentDmesg.txt

[Seija Kijin]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1856480/+attachment/5313398/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1856480] KernLog.txt

[Seija Kijin]

apport information

** Attachment added: "KernLog.txt"
   
https://bugs.launchpad.net/bugs/1856480/+attachment/5313400/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1856480] PrintingPackages.txt

[Seija Kijin]

apport information

** Attachment added: "PrintingPackages.txt"
   
https://bugs.launchpad.net/bugs/1856480/+attachment/5313403/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1856480] Lspci.txt

[Seija Kijin]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1856480/+attachment/5313402/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1856480] Dependencies.txt

[Seija Kijin]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1856480/+attachment/5313399/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet printer even though the printer is configured within
  Ubuntu

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the
  printers are not configured according to Ubuntu.

  I expected the document I sent over the network to print without
  issue. However, I am unable to on ubuntu because it is apparently not
  configured.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Package: cups 2.2.12-2ubuntu1
  PackageArchitecture: amd64
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  

[Desktop-packages] [Bug 1856480] Re: "Could not start printer" message appears when I attempt to print to an OfficeJet printer even though the printer is configured within Ubuntu

[Seija Kijin]

apport information

** Tags added: apport-collected

** Description changed:

  Whenever I attempt to print a document to a printer over the network,
  Ubuntu finds the printer and acts as if it is configured until I
  actually send a print job. When I do this, I get a message that says
  "Printing" in LibreOffice, but then nothing happens because the printers
  are not configured according to Ubuntu.
  
  I expected the document I sent over the network to print without issue.
  However, I am unable to on ubuntu because it is apparently not
  configured.
  
  Description:  Ubuntu 19.10
  Release:  19.10
  
  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Sun Dec 15 15:01:50 2019
  InstallationDate: Installed on 2019-11-20 (25 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.3
  dmi.board.name: 09YTN7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.product.sku: 0810
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.2
+ Architecture: amd64
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2019-11-20 (26 days ago)
+ InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
+ Lpstat: device for Officejet_Pro_8600_AB0C33_: 
ipp://HP843497AB0C33.local:631/ipp/printer
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
+  Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
+  Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Dell Inc. Inspiron 5570
+ Package: cups 2.2.12-2ubuntu1
+ PackageArchitecture: amd64
+ Papersize: letter
+ ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
+ Tags:  eoan
+ Uname: Linux 5.3.0-24-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 05/15/2019
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.2.3
+ dmi.board.name: 09YTN7
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A00
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
+ dmi.product.family: Inspiron
+ dmi.product.name: Inspiron 5570
+ dmi.product.sku: 0810
+ dmi.sys.vendor: Dell Inc.
+ mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

** Attachment added: "CupsErrorLog.txt"
   
https://bugs.launchpad.net/bugs/1856480/+attachment/5313397/+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/1856480

Title:
  "Could not start printer" message appears when I attempt to print to
  an OfficeJet 

[Desktop-packages] [Bug 1856054] Re: pulseaudio now depends on libsnapd-glib1 which recommends snapd

[Martin Wimpress]

This issue is being addressed via https://pad.lv/1856196

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

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

Title:
  pulseaudio now depends on libsnapd-glib1 which recommends snapd

Status in pulseaudio package in Ubuntu:
  Won't Fix

Bug description:
  The latest update for pulseaudio (1:11.1-1ubuntu7.5) in bionic now has
  libsnapd-glib1 as a dependency.

  This is complete and utter nonsense. I do not want cascading
  dependencies that have no business being installed on the systems I
  manage.

  Please rectify this at once.

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

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

[Desktop-packages] [Bug 1856718] [NEW] CUPS server has an internal error whenever I attempt to add my HP OfficeJet8600 printer to configured devices via networking

[Seija Kijin]

Public bug reported:

Whenever I attempt to add my HP OfficeJet8600 printer and configure it
for printing on my Ubuntu PC, CUPS has an internal error and it is
unable to configure the device or install drivers.

This happened when I ran "system-config-printer" and selected the
printer from the list of network printers and clicked "Forward"

Instead of configuring the printer and installing drivers, CUPS had an
error.

Description:Ubuntu 19.10
Release:19.10

cups:
  Installed: 2.2.12-2ubuntu1
  Candidate: 2.2.12-2ubuntu1
  Version table:
 *** 2.2.12-2ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cups 2.2.12-2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
Date: Tue Dec 17 09:37:45 2019
InstallationDate: Installed on 2019-11-20 (26 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
 Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 5570
Papersize: letter
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/15/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 09YTN7
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn09YTN7:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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


** Tags: amd64 apport-bug eoan

** Attachment added: "Screenshot of configuring screen and terminal"
   
https://bugs.launchpad.net/bugs/1856718/+attachment/5313383/+files/Screenshot%20from%202019-12-17%2009-43-12.png

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

Title:
  CUPS server has an internal error whenever I attempt to add my HP
  OfficeJet8600 printer to configured devices via networking

Status in cups package in Ubuntu:
  New

Bug description:
  Whenever I attempt to add my HP OfficeJet8600 printer and configure it
  for printing on my Ubuntu PC, CUPS has an internal error and it is
  unable to configure the device or install drivers.

  This happened when I ran "system-config-printer" and selected the
  printer from the list of network printers and clicked "Forward"

  Instead of configuring the printer and installing drivers, CUPS had an
  error.

  Description:  Ubuntu 19.10
  Release:  19.10

  cups:
Installed: 2.2.12-2ubuntu1
Candidate: 2.2.12-2ubuntu1
Version table:
   *** 2.2.12-2ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: cups 2.2.12-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Tue Dec 17 09:37:45 2019
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0c45:6a06 Microdia Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5570
  Papersize: letter
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=9ff1c776-2a6a-46be-a74f-61646ac9ac90 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present 

[Desktop-packages] [Bug 1856713] modified.conffile..etc.apport.crashdb.conf.txt

[Seija Kijin]

apport information

** Attachment added: "modified.conffile..etc.apport.crashdb.conf.txt"
   
https://bugs.launchpad.net/bugs/1856713/+attachment/5313379/+files/modified.conffile..etc.apport.crashdb.conf.txt

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

Title:
  Whenever I open Settings by searching for a setting in Gnome's search
  bar and then clicking on Settings, the back button will take me back
  to the Settings I looked for, not the main settings menu, making other
  settings impossible to open.

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

Bug description:
  When I searched in Gnome for settings related to printing, I had a
  result that said "Settings - About", and so I clicked on it expecting
  to be able to go to Settings' main menu. However, the back button only
  took me to the submenu and then BACK to the About page, which makes
  going to the main menu impossible.

  One can reproduce this issue by searching for a setting in Gnome,
  clicking on it, and then clicking the back button only to be in a
  loop.

  Description:  Ubuntu 19.10
  Release:  19.10

  gnome-control-center:
Installed: 1:3.34.1-1ubuntu2
Candidate: 1:3.34.1-1ubuntu2
Version table:
   *** 1:3.34.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 17 09:10:47 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1856713] Dependencies.txt

[Seija Kijin]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1856713/+attachment/5313376/+files/Dependencies.txt

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

Title:
  Whenever I open Settings by searching for a setting in Gnome's search
  bar and then clicking on Settings, the back button will take me back
  to the Settings I looked for, not the main settings menu, making other
  settings impossible to open.

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

Bug description:
  When I searched in Gnome for settings related to printing, I had a
  result that said "Settings - About", and so I clicked on it expecting
  to be able to go to Settings' main menu. However, the back button only
  took me to the submenu and then BACK to the About page, which makes
  going to the main menu impossible.

  One can reproduce this issue by searching for a setting in Gnome,
  clicking on it, and then clicking the back button only to be in a
  loop.

  Description:  Ubuntu 19.10
  Release:  19.10

  gnome-control-center:
Installed: 1:3.34.1-1ubuntu2
Candidate: 1:3.34.1-1ubuntu2
Version table:
   *** 1:3.34.1-1ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Dec 17 09:10:47 2019
  ExecutablePath: /usr/bin/gnome-control-center
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-11-20 (26 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  RelatedPackageVersions: mutter-common 3.34.1+git20191107-1ubuntu1~19.10.1
  Tags:  eoan
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  mtime.conffile..etc.apport.crashdb.conf: 2019-11-27T12:43:30.211160

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

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

[Desktop-packages] [Bug 1856714] [NEW] update to 1:0.5.2.5 made system very heavy

[Mina Morose]

Public bug reported:

after update to 1:0.5.2.5 the system been heavy and i couldn't even
browsing after troubleshooting what happened  i found a process  called
babloo extract make heavy IO operation that made my system unusable the
problem solved by manually downgrade and that process didn't run again

--

PS : i use xubunto 
this process  was opened by sh that opened by xfce4  but i think the cause of 
it is ubunto-drivers somehow because it's happened after update and disappear  
after downgrade  and the effect was immediately and i tried to restart the 
system and that didn't the solve the problem   unless i downgraded 

---

NAME="Ubuntu"
VERSION="18.04.3 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.3 LTS"
VERSION_ID="18.04"
VERSION_CODENAME=bionic

--

if there any log you want just tell me

** Affects: ubuntu-drivers-common (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
   update to 1:0.5.2.5 made system very heavy

Status in ubuntu-drivers-common package in Ubuntu:
  New

Bug description:
  after update to 1:0.5.2.5 the system been heavy and i couldn't even
  browsing after troubleshooting what happened  i found a process
  called babloo extract make heavy IO operation that made my system
  unusable the problem solved by manually downgrade and that process
  didn't run again

  --

  PS : i use xubunto 
  this process  was opened by sh that opened by xfce4  but i think the cause of 
it is ubunto-drivers somehow because it's happened after update and disappear  
after downgrade  and the effect was immediately and i tried to restart the 
system and that didn't the solve the problem   unless i downgraded 

  ---

  NAME="Ubuntu"
  VERSION="18.04.3 LTS (Bionic Beaver)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 18.04.3 LTS"
  VERSION_ID="18.04"
  VERSION_CODENAME=bionic

  --

  if there any log you want just tell me

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1856714/+subscriptions

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