date:20200113

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

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

Title:
  [SRU]Not able to adjust Audio input UI volume after connecting headset

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project bionic series:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  Not able to adjust Audio input UI volume if this device doesn't have a
  internal mic, the volume bar will be gray.

  [ Test Case ]

  1. Boot ubuntu without any external headset connected.
  2. Launch gnome-control-center and switch to Sound->Input tab.
  3. Connect external headset, then you will find the input show up but can not 
adjust the volume.

  [ Regression potential ]

  Low. change is the workaround to active/deactivate some bugs which
  didn't report things in the right order. It will just have extra
  active/deactiveate actions in normal situation(which the machines
  don't have this issue).

  Verified on built-in and non built-in input device machines , no
  regression found yet.

  Package in this PPA:
  https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages

  

  Summary:Not able to adjust Audio input UI volume, it's gray

  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack

  Expected result:
  System can be recording audio from external mic

  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox

  Failure rate:100%

  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

  Note:20.04, 19.10, 19.04 are immune on the bug

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

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

[Desktop-packages] [Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a LG Thin
Client[0], can fix this issue

[0] https://www.lg.com/global/business/monitor/monitor-products/lg-
CK500W

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

Title:
  [SRU]Not able to adjust Audio input UI volume after connecting headset

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project bionic series:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  Not able to adjust Audio input UI volume if this device doesn't have a
  internal mic, the volume bar will be gray.

  [ Test Case ]

  1. Boot ubuntu without any external headset connected.
  2. Launch gnome-control-center and switch to Sound->Input tab.
  3. Connect external headset, then you will find the input show up but can not 
adjust the volume.

  [ Regression potential ]

  Low. change is the workaround to active/deactivate some bugs which
  didn't report things in the right order. It will just have extra
  active/deactiveate actions in normal situation(which the machines
  don't have this issue).

  Verified on built-in and non built-in input device machines , no
  regression found yet.

  Package in this PPA:
  https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages

  

  Summary:Not able to adjust Audio input UI volume, it's gray

  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack

  Expected result:
  System can be recording audio from external mic

  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox

  Failure rate:100%

  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

  Note:20.04, 19.10, 19.04 are immune on the bug

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

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

[Desktop-packages] [Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a hp Small Form
Factor PC[0], can fix this issue

[0] https://www8.hp.com/us/en/desktops/product-details/21353680

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

Title:
  [SRU]Not able to adjust Audio input UI volume after connecting headset

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project bionic series:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  Not able to adjust Audio input UI volume if this device doesn't have a
  internal mic, the volume bar will be gray.

  [ Test Case ]

  1. Boot ubuntu without any external headset connected.
  2. Launch gnome-control-center and switch to Sound->Input tab.
  3. Connect external headset, then you will find the input show up but can not 
adjust the volume.

  [ Regression potential ]

  Low. change is the workaround to active/deactivate some bugs which
  didn't report things in the right order. It will just have extra
  active/deactiveate actions in normal situation(which the machines
  don't have this issue).

  Verified on built-in and non built-in input device machines , no
  regression found yet.

  Package in this PPA:
  https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages

  

  Summary:Not able to adjust Audio input UI volume, it's gray

  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack

  Expected result:
  System can be recording audio from external mic

  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox

  Failure rate:100%

  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

  Note:20.04, 19.10, 19.04 are immune on the bug

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

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

[Desktop-packages] [Bug 1019293] Re: "gpg: can't handle text lines longer than 19995 characters" error when backing up

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

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  "gpg: can't handle text lines longer than 19995 characters" error when
  backing up

Status in deja-dup package in Ubuntu:
  Expired

Bug description:
  When I run deja-dup, and it encounters some data* it asks for the
  password to be reentered, and when you do that, it tries again, and
  gets in the same loop, over and over until you cancel. Nothing ends up
  being backed up.

  * e.g. my gpg public keyring, but when I exclude .gnupg, it has what
  may be the same problem on something else too, so I think that's
  coincidence.

  The last part of the log is at the bottom of this, and I'll attach the
  final 1000 lines. I don't think this is a duplicate of bug #883742, as
  the source of the error is quite different.

  DUPLICITY: DEBUG 1
  DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf

  DUPLICITY: DEBUG 1
  DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf') and None

  DUPLICITY: DEBUG 1
  DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf') 
/home/robin/.gnupg/gpg.conf reg) and None

  DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf'
  DUPLICITY: . A home/robin/.gnupg/gpg.conf

  DUPLICITY: DEBUG 1
  DUPLICITY: . Selecting /home/robin/.gnupg/gpg.conf~

  DUPLICITY: DEBUG 1
  DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'gpg.conf~') and None

  DUPLICITY: DEBUG 1
  DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'gpg.conf~') 
/home/robin/.gnupg/gpg.conf~ reg) and None

  DUPLICITY: INFO 4 'home/robin/.gnupg/gpg.conf~'
  DUPLICITY: . A home/robin/.gnupg/gpg.conf~

  DUPLICITY: DEBUG 1
  DUPLICITY: . Selecting /home/robin/.gnupg/pubring.gpg

  DUPLICITY: DEBUG 1
  DUPLICITY: . Comparing ('home', 'robin', '.gnupg', 'pubring.gpg') and None

  DUPLICITY: DEBUG 1
  DUPLICITY: . Getting delta of (('home', 'robin', '.gnupg', 'pubring.gpg') 
/home/robin/.gnupg/pubring.gpg reg) and None

  DUPLICITY: INFO 4 'home/robin/.gnupg/pubring.gpg'
  DUPLICITY: . A home/robin/.gnupg/pubring.gpg

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-_XHa0A-tempdir/mkstemp-DS0LuL-1

  DUPLICITY: DEBUG 1
  DUPLICITY: . Removing still remembered temporary file 
/tmp/duplicity-_XHa0A-tempdir/mktemp-w2gx_c-2

  DUPLICITY: INFO 1
  DUPLICITY: . GPG error detail: Traceback (most recent call last):
  DUPLICITY: .   File "/usr/bin/duplicity", line 1403, in 
  DUPLICITY: . with_tempdir(main)
  DUPLICITY: .   File "/usr/bin/duplicity", line 1396, in with_tempdir
  DUPLICITY: . fn()
  DUPLICITY: .   File "/usr/bin/duplicity", line 1366, in main
  DUPLICITY: . full_backup(col_stats)
  DUPLICITY: .   File "/usr/bin/duplicity", line 500, in full_backup
  DUPLICITY: . globals.backend)
  DUPLICITY: .   File "/usr/bin/duplicity", line 378, in write_multivol
  DUPLICITY: . globals.gpg_profile, globals.volsize)
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 
332, in GPGWriteFile
  DUPLICITY: . file.close()
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 
221, in close
  DUPLICITY: . self.gpg_failed()
  DUPLICITY: .   File "/usr/lib/python2.7/dist-packages/duplicity/gpg.py", line 
206, in gpg_failed
  DUPLICITY: . raise GPGError, msg
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: . 
  DUPLICITY: . 

  DUPLICITY: ERROR 31 GPGError
  DUPLICITY: . GPGError: GPG Failed, see log below:
  DUPLICITY: . = Begin GnuPG log =
  DUPLICITY: . gpg: can't handle text lines longer than 19995 characters
  DUPLICITY: . = End GnuPG log =
  DUPLICITY: .

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: deja-dup 22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18
  Uname: Linux 3.2.0-25-generic x86_64
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: amd64
  Date: Fri Jun 29 14:04:01 2012
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: deja-dup
  UpgradeStatus: Upgraded to precise on 2012-05-08 (52 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1019293/+subscriptions

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

[Desktop-packages] [Bug 1848279] Re: Nautilus GUI does not work

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

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

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

Title:
  Nautilus GUI does not work

Status in nautilus package in Ubuntu:
  Expired

Bug description:
  
  Dear Nautilus development and bug report staff,

  on a fresh Linux install I just used Arduino IDE and Matlab R2019b, then 
attached an external usb hard disk and my smartphone for a file transfer, and 
everything worked. The day after, the white nautilus folder icon on the left 
bar could not make me open the folders, I could do it just from the terminal. 
  So I used:

  sudo dpkg-reconfigure --default-priority nautilus

  and everything seemed to be fine. The day after, the white folder icon
  was not working, and the folders that I put on the desktop
  disappeared. I then used:

  sudo apt-get purge nautilus

  then log off, then

  sudo apt-get install nautilus

  but nothing changed. What can I do to restore the GUI. Now I just can use the 
CLI. 
  I have (through lsb_release -rd):
  Description:  Ubuntu 19.04
  Release:  19.04

  and (through apt-cache policy nautilus:
  nautilus:
Installato: 1:3.32.1-0ubuntu0.19.04.0
Candidato:  1:3.32.1-0ubuntu0.19.04.0
Tabella versione:
   *** 1:3.32.1-0ubuntu0.19.04.0 500
  500 http://it.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:3.32.0-0ubuntu2 500
  500 http://it.archive.ubuntu.com/ubuntu disco/main amd64 Packages

  
  I already looked for similar issues in Ask Ubuntu. Best regards.

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

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

[Desktop-packages] [Bug 1740238] Re: 'operation already pending' error when drive gets available, manual start required

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

** Changed in: deja-dup (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  'operation already pending' error when drive gets available, manual
  start required

Status in deja-dup package in Ubuntu:
  Expired

Bug description:
  I have scheduled daily backups for a laptop to be kept forever on a
  drive that is often disconnected from the laptop. I connect it when I
  can; when I connect it, it gives a 'Backups failed' error stating that
  an operation is already pending. I must then open Backups from the
  launcher for this pending backup to begin. Please fix these two bugs
  (or single bug causing two problems?) so that the backup starts
  without telling me an operation (presumably the backup that starts) is
  already pending, and without me having to open Backups for it to
  start.

  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: deja-dup 34.2-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.14
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 27 17:51:10 2017
  InstallationDate: Installed on 2017-11-20 (36 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: deja-dup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/deja-dup/+bug/1740238/+subscriptions

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

[Desktop-packages] [Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a hp desktop
mini machine[0], can fix this issue

[0] http://h20195.www2.hp.com/v2/GetDocument.aspx?docname=c06339658

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

Title:
  [SRU]Not able to adjust Audio input UI volume after connecting headset

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project bionic series:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  Not able to adjust Audio input UI volume if this device doesn't have a
  internal mic, the volume bar will be gray.

  [ Test Case ]

  1. Boot ubuntu without any external headset connected.
  2. Launch gnome-control-center and switch to Sound->Input tab.
  3. Connect external headset, then you will find the input show up but can not 
adjust the volume.

  [ Regression potential ]

  Low. change is the workaround to active/deactivate some bugs which
  didn't report things in the right order. It will just have extra
  active/deactiveate actions in normal situation(which the machines
  don't have this issue).

  Verified on built-in and non built-in input device machines , no
  regression found yet.

  Package in this PPA:
  https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages

  

  Summary:Not able to adjust Audio input UI volume, it's gray

  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack

  Expected result:
  System can be recording audio from external mic

  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox

  Failure rate:100%

  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

  Note:20.04, 19.10, 19.04 are immune on the bug

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

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

[Desktop-packages] [Bug 1859555] [NEW] Calculator does not work in GNOME activities search

2020-01-13 Thread Alexandre Forte

Public bug reported:

Ubuntu release: 18.04.3
Package version: (deb) 1:3.28.2-1~ubuntu18.04.3


What was expected to happen: calculation results are displayed in activities 
search.
What happens instead: no results are displayed.

The bug started happening after the last update of the package. The
previous version worked properly.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-calculator 1:3.28.2-1~ubuntu18.04.3
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Jan 14 00:58:57 2020
InstallationDate: Installed on 2019-10-15 (91 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calculator
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic third-party-packages

** Attachment added: "The results are not displayed"
   
https://bugs.launchpad.net/bugs/1859555/+attachment/5320016/+files/Captura%20de%20tela%20de%202020-01-14%2001-10-32.png

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

Title:
  Calculator does not work in GNOME activities search

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  Ubuntu release: 18.04.3
  Package version: (deb) 1:3.28.2-1~ubuntu18.04.3

  
  What was expected to happen: calculation results are displayed in activities 
search.
  What happens instead: no results are displayed.

  The bug started happening after the last update of the package. The
  previous version worked properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calculator 1:3.28.2-1~ubuntu18.04.3
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jan 14 00:58:57 2020
  InstallationDate: Installed on 2019-10-15 (91 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calculator
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1819779] Re: Stick to the 3.30 serie still?

I'm working on rebasing on the Debian 3.34 version.

** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Stick to the 3.30 serie still?

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  The new serie/version is having stability issues (see bug #1817223 for 
example, which means we got no testing of the refactoring at this point) and we 
don't have the resources to deal with the fallout.
  There are also no change in the NEWS that we consider essential to get this 
cycle (backporting the new icon/appmenu change might be worth doing though)

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

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

[Desktop-packages] [Bug 1859260] Re: Cant go back to primary monitor when app indicator menu is open

2020-01-13 Thread Sidney Lins

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

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

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

Title:
  Cant go back to primary monitor when app indicator menu is open

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This bugs happens if you:

  1. Open app indicator menu (top right);
  2. Move your cursor to the right monitor;

  Now you can't go back. The only way is pressing ESC to close app
  indicator menu so that you can go back to the first monitor.

  This only happens when ubuntu-dock autohide is on.

  Maybe it can be useful: https://github.com/micheleg/dash-to-
  dock/issues/743

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-ubuntu-dock 67ubuntu19.10.1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 11 00:01:41 2020
  InstallationDate: Installed on 2019-12-31 (11 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-ubuntu-dock
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1859390] Re: Blurred texts, icons and character typed on login screen after logout or switching user

2020-01-13 Thread Sidney Lins

** Summary changed:

- Blurred texts, icons and character typed on login screen after logout
+ Blurred texts, icons and character typed on login screen after logout or 
switching user

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

Title:
  Blurred texts, icons and character typed on login screen after logout
  or switching user

Status in lightdm package in Ubuntu:
  New

Bug description:
  I login to my account normally. But, when I click on "switch user"
  from app indicator, the clock in login screen will be completely
  blurred, impossible even to perceive it is a clock/time, except if I
  wait one minute so that the last number will update and it will show
  correctly (only the last number).

  If I press enter or click-up, I see the login form with the same
  problem: I can see that there are two users but they are completely
  indistinguishable and blurred. If I click on it, I can type my
  password but still blurred, even the chars I type are blurred.

  The app indicator icons are blurred too, but when I put the cursor
  over them, instantly they are fixed.

  PS: I have two enabled monitors and two users, but the second user is
  not logged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 00:13:45 2020
  InstallationDate: Installed on 2019-12-31 (13 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

tried gnome-control-center 1:3.28.2-0ubuntu0.18.04.6 in a built-in
speaker/microphone laptop[0], still works well, didn't find any
Regression potential.

[0] https://support.hp.com/ro-en/document/c05994943

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

Title:
  [SRU]Not able to adjust Audio input UI volume after connecting headset

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project bionic series:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  Not able to adjust Audio input UI volume if this device doesn't have a
  internal mic, the volume bar will be gray.

  [ Test Case ]

  1. Boot ubuntu without any external headset connected.
  2. Launch gnome-control-center and switch to Sound->Input tab.
  3. Connect external headset, then you will find the input show up but can not 
adjust the volume.

  [ Regression potential ]

  Low. change is the workaround to active/deactivate some bugs which
  didn't report things in the right order. It will just have extra
  active/deactiveate actions in normal situation(which the machines
  don't have this issue).

  Verified on built-in and non built-in input device machines , no
  regression found yet.

  Package in this PPA:
  https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages

  

  Summary:Not able to adjust Audio input UI volume, it's gray

  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack

  Expected result:
  System can be recording audio from external mic

  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox

  Failure rate:100%

  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

  Note:20.04, 19.10, 19.04 are immune on the bug

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

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

[Desktop-packages] [Bug 1857253] Re: Network-manager-applet doesn't store VPN password

This bug was fixed in the package network-manager-applet -
1.8.24-1ubuntu1

---
network-manager-applet (1.8.24-1ubuntu1) focal; urgency=medium

  * Resynchronize on Debian
- Support for SAE authentication (WPA3 Personal) was added.
  (lp: #1848339)
- Fixed external UI mode without interactive secrets. (lp: #1857253)

 -- Sebastien Bacher   Mon, 13 Jan 2020 23:28:29
+0100

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

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

Title:
  Network-manager-applet doesn't store VPN password

Status in Network Manager Applet:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Released

Bug description:
  Network-manager-applet doesn't store VPN password.

  Also opened here : https://gitlab.gnome.org/GNOME/network-manager-
  applet/issues/59

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

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

[Desktop-packages] [Bug 1848339] Re: Add WPA3-SAE (WPA3-Personal)

This bug was fixed in the package network-manager-applet -
1.8.24-1ubuntu1

---
network-manager-applet (1.8.24-1ubuntu1) focal; urgency=medium

  * Resynchronize on Debian
- Support for SAE authentication (WPA3 Personal) was added.
  (lp: #1848339)
- Fixed external UI mode without interactive secrets. (lp: #1857253)

 -- Sebastien Bacher   Mon, 13 Jan 2020 23:28:29
+0100

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

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

Title:
  Add WPA3-SAE (WPA3-Personal)

Status in network-manager-applet package in Ubuntu:
  Fix Released

Bug description:
  With the release of fixes for bug #1844422, support for WPA3-SAE was
  added to respectively Network-Manager and Gnome-Shell for Eoan.

  What is missing is WPA3-SAE support for the NM-Applet, this matters for those 
that do not use Gnome as their desktop environment.
  (Note: NM-Applet is part of the "network-manager-gnome" package, as is the 
nm-connection-editor).

  Currently, WPA3-SAE support for NM-Applet (which is at ver. 1.8.22-2ubuntu1) 
is non-existent.
  This leads to problems when using the applet for connecting to Wi-Fi networks 
that have WPA3-enabled, even if WPA2 is also available for said network.

  [Problem Description]:
  When trying to connect to my AP's WLAN (which is set to WPA2/WPA3 mixed mode) 
using NM-Applet, the authentication dialog will popup, but the password field 
is missing, so connecting to the WLAN, using the applet is impossible.
  (I've added a screenshot depicting the issue).

  NM-connection-editor for Eoan, as of now,  lacks support for WPA3-SAE
  so when connected to the WLAN using WPA3 "Wifi-Security is shown as
  "None" and NM-connection-editor does not offer the option to set
  security to WPA3.

  [Resolution]:
  Support for WPA3-SAE for NM-applet was finalized upstream last week.

  The following commit (merge-requests) depicts the changes made:
  
https://gitlab.gnome.org/GNOME/network-manager-applet/commit/1b59bb544f565ae4d8cdebe0645d41acbcb63b6f

  A more detailed view of the individual commits can be found here:
  
https://gitlab.gnome.org/GNOME/network-manager-applet/commits/master?utf8=%E2%9C%93=sae

  Please back-port WPA3-SAE support (which is available upstream) to
  network-manager-applet for Ubuntu 19.10.

  TL;DR
  So this is a request to back-port WPA3-SAE support to network-manager-applet 
for Ubuntu Eoan.

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

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

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

2020-01-13 Thread Bug Watch Updater

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

** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues 
#328
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/328

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

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1609700]

2020-01-13 Thread thaller

I don't think it's helpful to reopen bugs that were closed for years.

The original issue was identified and confirmed to be fixed.

It's unlikely that the new symptoms have the same cause as the original
one. But even so, it would require information to understand the new
symptoms better.

Let's discuss this on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/328.

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1609700]

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

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1609700]

2020-01-13 Thread udayreddy

This is happening to me with F30 with the latest updates as of date.

NetworkManager-openconnect-1.2.6-2.fc30.x86_64

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1609700]

Please test the Fedora 30 build with that commit reverted, at
https://koji.fedoraproject.org/koji/taskinfo?taskID=36857342

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1609700]

That build seems not to fix it. I tried to build locally to bisect, but
can't seem to get the local build to work at all. May have to leave this
to the NM maintainers.

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1609700]

2020-01-13 Thread compubear

Just wanted to mention that this 'bug/issue' is also present in the
current Fedora 31 beta with the following packages:

NetworkManager-openconnect-gnome-1.2.6-2.fc31.x86_64
NetworkManager-openconnect-1.2.6-2.fc31.x86_64
NetworkManager-1.20.4-1.fc31.x86_64

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1609700]

2020-01-13 Thread champetier.etienne

This is happening to me with F31 and some Anyconnect VPNs

NetworkManager-openconnect-gnome-1.2.6-2.fc31.x86_64
NetworkManager-openconnect-1.2.6-2.fc31.x86_64
NetworkManager-1.20.6-1.fc31.x86_64

My workaround:
nmcli con mod VPNNAME vpn.secrets 
'form:main:group_list=GROUPNAME','form:main:username=USERNAME','save_passwords=yes'

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1609700]

According to https://bugs.launchpad.net/bugs/1609700 this bug has
reoccurred in f30.

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1609700]

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

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1609700]

I wonder if this regression is caused by
https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=009f7560867e939
?

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

Title:
  username is not saved in openconnect connection dialog

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

Bug description:
  Happening again on Eoan 19.10!


  Hi,

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

  This happens for a SSLVPN configuration.

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

  openconnect: 7.06-2build2

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

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

[Desktop-packages] [Bug 1825842] Re: [vmware] Background goes white when using scaling (200%, 300% or 400%)

2020-01-13 Thread Juan Martinez

Same issue - 19.10 running on VMWare

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

Title:
  [vmware] Background goes white when using scaling (200%, 300% or 400%)

Status in mutter package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-vmware package in Ubuntu:
  Confirmed

Bug description:
  As soon as I set my display to scaled (any percentage) via Settings ->
  Displays -> Scale, the background image disappears and become all
  white. When I choose a different background image via Settings ->
  Background initially nothing happens. As soon as I switch back to 100%
  scaling, the image I choose before now appears.

  This problem started right after updating to 19.04. No such issues
  with either 18.04 or 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 15:35:49 2019
  DistUpgraded: 2019-04-21 17:34:15,063 DEBUG icon theme changed, re-reading
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2019-03-01 (51 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: VMware, Inc. VMware Virtual Platform
  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.0.0-13-generic 
root=UUID=c8dc93a3-fd95-4152-9c04-0211309b2dc7 ro find_preseed=/preseed.cfg 
auto noprompt priority=critical locale=en_US quiet
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-04-21 (0 days ago)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: 6.00
  dmi.board.name: 440BX Desktop Reference Platform
  dmi.board.vendor: Intel Corporation
  dmi.board.version: None
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd04/13/2018:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: VMware Virtual Platform
  dmi.product.version: None
  dmi.sys.vendor: VMware, Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1857253] Re: Network-manager-applet doesn't store VPN password

2020-01-13 Thread Bug Watch Updater

** Changed in: network-manager-applet
   Status: Unknown => Fix Released

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

Title:
  Network-manager-applet doesn't store VPN password

Status in Network Manager Applet:
  Fix Released
Status in network-manager-applet package in Ubuntu:
  Fix Committed

Bug description:
  Network-manager-applet doesn't store VPN password.

  Also opened here : https://gitlab.gnome.org/GNOME/network-manager-
  applet/issues/59

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

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

[Desktop-packages] [Bug 1828996] Re: "Advanced Network Configuration" is displayed in both Utilities and Sundry categories

** Changed in: network-manager-applet (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  "Advanced Network Configuration" is displayed in both Utilities and
  Sundry categories

Status in gnome-menus package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  Fix Released

Bug description:
  The "Advanced Network Configuration" is displayed in both Utilities
  and Sundry categories instead of just the Utilities category. It was
  moved to the Utilities category in upstream, but it probably needs a
  related gnome-software code to be backported from 3.32 into the older
  version used in Ubuntu.

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

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

[Desktop-packages] [Bug 1848148] Re: Routes editing dialog is incorrectly displayed

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Routes editing dialog is incorrectly displayed

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

Bug description:
  When I open the routes editing dialog, parts of the window are transparent 
(see attachment).
  That's obviously not by design.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: network-manager-gnome 1.8.22-2ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1
  Uname: Linux 5.3.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Oct 15 10:29:43 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from /etc/network/interfaces.d:
   source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2019-09-26 (18 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  IpRoute:
   default via 192.168.111.2 dev ens33 proto dhcp metric 100 
   10.20.10.0/24 dev ens38 proto kernel scope link src 10.20.10.100 metric 101 
   169.254.0.0/16 dev ens38 scope link metric 1000 
   192.168.111.0/24 dev ens33 proto kernel scope link src 192.168.111.130 
metric 100
  IwConfig:
   ens33 no wireless extensions.
   
   lono wireless extensions.
   
   ens38 no wireless extensions.
  RfKill:
   
  SourcePackage: network-manager-applet
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH   
   CONNECTIONCON-UUID   
   CON-PATH
   ens33   ethernet  connected  full  full  
/org/freedesktop/NetworkManager/Devices/2  NAT   
52e7dfdb-10e3-3dc1-b53b-c314a602ae48  
/org/freedesktop/NetworkManager/ActiveConnection/22 
   ens38   ethernet  connected  limited   limited   
/org/freedesktop/NetworkManager/Devices/3  CPE - 10.20.10.1  
984da49a-f0b1-3e7d-8bec-031736b5c2fd  
/org/freedesktop/NetworkManager/ActiveConnection/23 
   lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1848339] Re: Add WPA3-SAE (WPA3-Personal)

** Changed in: network-manager-applet (Ubuntu)
Status: Triaged => Fix Committed

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

Title:
Add WPA3-SAE (WPA3-Personal)

Status in network-manager-applet package in Ubuntu:
Fix Committed

Bug description:
With the release of fixes for bug #1844422, support for WPA3-SAE was
added to respectively Network-Manager and Gnome-Shell for Eoan.

What is missing is WPA3-SAE support for the NM-Applet, this matters for those
that do not use Gnome as their desktop environment.
(Note: NM-Applet is part of the "network-manager-gnome" package, as is the
nm-connection-editor).

Currently, WPA3-SAE support for NM-Applet (which is at ver. 1.8.22-2ubuntu1)
is non-existent.
This leads to problems when using the applet for connecting to Wi-Fi networks
that have WPA3-enabled, even if WPA2 is also available for said network.

[Problem Description]:
When trying to connect to my AP's WLAN (which is set to WPA2/WPA3 mixed mode)
using NM-Applet, the authentication dialog will popup, but the password field
is missing, so connecting to the WLAN, using the applet is impossible.
(I've added a screenshot depicting the issue).

NM-connection-editor for Eoan, as of now, lacks support for WPA3-SAE
so when connected to the WLAN using WPA3 "Wifi-Security is shown as
"None" and NM-connection-editor does not offer the option to set
security to WPA3.

[Resolution]:
Support for WPA3-SAE for NM-applet was finalized upstream last week.

The following commit (merge-requests) depicts the changes made:

https://gitlab.gnome.org/GNOME/network-manager-applet/commit/1b59bb544f565ae4d8cdebe0645d41acbcb63b6f

A more detailed view of the individual commits can be found here:

https://gitlab.gnome.org/GNOME/network-manager-applet/commits/master?utf8=%E2%9C%93=sae

Please back-port WPA3-SAE support (which is available upstream) to
network-manager-applet for Ubuntu 19.10.

TL;DR
So this is a request to back-port WPA3-SAE support to network-manager-applet
for Ubuntu Eoan.

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

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

[Desktop-packages] [Bug 1857253] Re: Network-manager-applet doesn't store VPN password

** Changed in: network-manager-applet (Ubuntu)
   Importance: Undecided => High

** Changed in: network-manager-applet (Ubuntu)
   Status: New => Fix Committed

** Bug watch added: gitlab.gnome.org/GNOME/network-manager-applet/issues #59
   https://gitlab.gnome.org/GNOME/network-manager-applet/issues/59

** Also affects: network-manager-applet via
   https://gitlab.gnome.org/GNOME/network-manager-applet/issues/59
   Importance: Unknown
   Status: Unknown

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

Title:
  Network-manager-applet doesn't store VPN password

Status in Network Manager Applet:
  Unknown
Status in network-manager-applet package in Ubuntu:
  Fix Committed

Bug description:
  Network-manager-applet doesn't store VPN password.

  Also opened here : https://gitlab.gnome.org/GNOME/network-manager-
  applet/issues/59

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

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

[Desktop-packages] [Bug 1856196] Re: Lower the snapd recommends to a suggests

Confirmed that snapd-glib 1.49-0ubuntu0.19.04.1 on disco only suggests
snapd, not recomends it.

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

** Changed in: snapd-glib (Ubuntu Disco)
   Status: Won't Fix => Fix Committed

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

Title:
  Lower the snapd recommends to a suggests

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Disco:
  Fix Committed
Status in snapd-glib source package in Eoan:
  Fix Committed
Status in snapd-glib source package in Focal:
  Fix Released

Bug description:
  * Impact

  libsnapd-glib is a small library used to talk to snapd. It's currently
  used by gnome-software but has been added to pulseaudio in bug
  #1781428. It currently recommends snapd but the library works fine
  without it and there is no reason to pull snapd from library clients.

  
  * Test case

  $ sudo apt install libsnapd-glib1

  -> snapd shouldn't be pulled in

  
  * Regression potential

  That's only a depends change, snapd isn't going to be pulled in when
  installing the library anymore but that's wanted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196/+subscriptions

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

[Desktop-packages] [Bug 1856196] Re: Lower the snapd recommends to a suggests

Confirmed that snapd-glib 1.49-0ubuntu0.19.10.1 on eoan only suggests
snapd, not recomends it.

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

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

Title:
  Lower the snapd recommends to a suggests

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Disco:
  Won't Fix
Status in snapd-glib source package in Eoan:
  Fix Committed
Status in snapd-glib source package in Focal:
  Fix Released

Bug description:
  * Impact

  libsnapd-glib is a small library used to talk to snapd. It's currently
  used by gnome-software but has been added to pulseaudio in bug
  #1781428. It currently recommends snapd but the library works fine
  without it and there is no reason to pull snapd from library clients.

  
  * Test case

  $ sudo apt install libsnapd-glib1

  -> snapd shouldn't be pulled in

  
  * Regression potential

  That's only a depends change, snapd isn't going to be pulled in when
  installing the library anymore but that's wanted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196/+subscriptions

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

[Desktop-packages] [Bug 1856877] Re: [firefox 72 beta] Unity global menu: opening a menu makes a duplicate menubar appear in the window

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

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

Title:
  [firefox 72 beta] Unity global menu: opening a menu makes a duplicate
  menubar appear in the window

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  This is a regression observed in firefox 72.0 beta builds
  (https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next).

  In a 16.04 VM with the default Unity session, a menubar is displayed
  in the top panel. As soon as I click on one of the menus to open it, a
  second, identical, menubar appears in the window, below the titlebar,
  thus resizing the web content. After opening a menu in that second
  menubar and closing it, it disappears again.

  See the attached screenshot.

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

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

[Desktop-packages] [Bug 1856196] Re: Lower the snapd recommends to a suggests

Confirmed that snapd-glib 1.49-0ubuntu0.16.04.1 on xenial only suggests
snapd, not recomends it.

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

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

Title:
  Lower the snapd recommends to a suggests

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Disco:
  Won't Fix
Status in snapd-glib source package in Eoan:
  Fix Committed
Status in snapd-glib source package in Focal:
  Fix Released

Bug description:
  * Impact

  libsnapd-glib is a small library used to talk to snapd. It's currently
  used by gnome-software but has been added to pulseaudio in bug
  #1781428. It currently recommends snapd but the library works fine
  without it and there is no reason to pull snapd from library clients.

  
  * Test case

  $ sudo apt install libsnapd-glib1

  -> snapd shouldn't be pulled in

  
  * Regression potential

  That's only a depends change, snapd isn't going to be pulled in when
  installing the library anymore but that's wanted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196/+subscriptions

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

[Desktop-packages] [Bug 1858504] Re: Firefox 72 Released

** Changed in: firefox (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Firefox 72 Released

Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  New release of firefox today, see: 
https://www.phoronix.com/scan.php?page=news_item=Firefox-72-Available
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  BuildID: 20191205220404
  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 20.04
  InstallationDate: Installed on 2020-01-02 (4 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200101)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: firefox 71.0+build5-0ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Profiles:
   Profile1 (Default) - LastVersion=None/None (Out of date)
   Profile0 - LastVersion=71.0/20191205220404 (In use)
  Tags:  focal
  Uname: Linux 5.4.0-9-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/1858504/+subscriptions

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

[Desktop-packages] [Bug 1856196] Re: Lower the snapd recommends to a suggests

Confirmed that snapd-glib 1.49-0ubuntu0.18.04.1 on bionic only suggests
snapd, not recomends it.

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

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

Title:
  Lower the snapd recommends to a suggests

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Disco:
  Won't Fix
Status in snapd-glib source package in Eoan:
  Fix Committed
Status in snapd-glib source package in Focal:
  Fix Released

Bug description:
  * Impact

  libsnapd-glib is a small library used to talk to snapd. It's currently
  used by gnome-software but has been added to pulseaudio in bug
  #1781428. It currently recommends snapd but the library works fine
  without it and there is no reason to pull snapd from library clients.

  
  * Test case

  $ sudo apt install libsnapd-glib1

  -> snapd shouldn't be pulled in

  
  * Regression potential

  That's only a depends change, snapd isn't going to be pulled in when
  installing the library anymore but that's wanted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196/+subscriptions

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

[Desktop-packages] [Bug 1859485] Re: remmina crashed with SIGSEGV

2020-01-13 Thread Antenore Gatta

See my comments on gitlab.

We will update this bug report later on

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

Title:
  remmina crashed with SIGSEGV

Status in remmina-ppa:
  Unknown
Status in remmina package in Ubuntu:
  New

Bug description:
  Close session of Win10(remote).

  ---

  https://gitlab.com/Remmina/Remmina/issues/2059

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: remmina 1.3.10+dfsg-1ubuntu1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 12:08:00 2020
  ExecutablePath: /usr/bin/remmina
  InstallationDate: Installed on 2018-12-02 (406 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: remmina
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f9442a77ac0:movdqu 0x10(%rax),%xmm2
   PC (0x7f9442a77ac0) ok
   source "0x10(%rax)" (0x7f941f872a60) not located in a known VMA region 
(needed readable region)!
   destination "%xmm2" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: remmina
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   pixman_blt () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: remmina crashed with SIGSEGV
  UpgradeStatus: Upgraded to focal on 2018-12-02 (406 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/remmina-ppa/+bug/1859485/+subscriptions

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

[Desktop-packages] [Bug 1856196] Re: Lower the snapd recommends to a suggests

** Changed in: snapd-glib (Ubuntu Disco)
   Status: Fix Committed => Won't Fix

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

Title:
  Lower the snapd recommends to a suggests

Status in snapd-glib package in Ubuntu:
  Fix Released
Status in snapd-glib source package in Xenial:
  Fix Committed
Status in snapd-glib source package in Bionic:
  Fix Committed
Status in snapd-glib source package in Disco:
  Won't Fix
Status in snapd-glib source package in Eoan:
  Fix Committed
Status in snapd-glib source package in Focal:
  Fix Released

Bug description:
  * Impact

  libsnapd-glib is a small library used to talk to snapd. It's currently
  used by gnome-software but has been added to pulseaudio in bug
  #1781428. It currently recommends snapd but the library works fine
  without it and there is no reason to pull snapd from library clients.

  
  * Test case

  $ sudo apt install libsnapd-glib1

  -> snapd shouldn't be pulled in

  
  * Regression potential

  That's only a depends change, snapd isn't going to be pulled in when
  installing the library anymore but that's wanted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd-glib/+bug/1856196/+subscriptions

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

Re: [Desktop-packages] [Bug 1857815] Re: cups-browsed assert failure: corrupted double-linked list

2020-01-13 Thread lpluys

Hi Till,

The problem is solved as I installed the new version of HPLIP 
(https://developers.hp.com/hp-linux-imaging-and-printing)
I will do your suggestion tomorrow and give you feedback.

BR.

Luc

- Oorspronkelijk bericht -
Van: "Till Kamppeter" <1857...@bugs.launchpad.net>
Aan: "luc" 
Verzonden: Maandag 13 januari 2020 19:09:34
Onderwerp: [Bug 1857815] Re: cups-browsed assert failure: corrupted 
double-linked list

seb128, as you have found a way to reliably reproduce the bug, I want to
ask you to do the following:

Run the command

cupsctl --debug-logging

to activate logginf by CUPS.

Edit the /etc/cups/cups-browsed.conf file, making sure that it contains
a line

DebugLogging file

with no "#" in the beginning.

Stop cups-browsed with

sudo systemctl stop cups-browsed

Wait some minutes, click away any apport pop-up.

If you get a crash now it is NOT yet covered by the debug logging.

Now start cups-browsed with

sudo systemctl start cups-browsed

wait some minutes, run "lpstat -v" repeatedly until no more remote
queues get discovered.

If it did not crash yet, shut down cups-browsed with

sudo systemctl stop cups-browsed

Wait some minutes.

If it did not crash yet, repeat this procedure until you get a crash.

Now attach the following files:

/etc/cups/cups-files.conf
/etc/cups/cupsd.conf
/etc/cups/cups-browsed.conf
/var/log/cups/error_log
/var/log/cups/cups-browsed_log

Please attach the files one-by-one, do not compress them and do not
package them together.

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1858103).
https://bugs.launchpad.net/bugs/1857815

Title:
  cups-browsed assert failure: corrupted double-linked list

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  Same bug on Focal

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.26.0-1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AssertionMessage: corrupted double-linked list
  CupsErrorLog:
   
  Date: Thu Dec 26 08:18:13 2019
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2019-12-12 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191211)
  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 002: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=ada0b905-9f6f-4911-9311-d1930ae73b8a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa8703a73a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7fa8703a54d3 "corrupted double-linked 
list") at malloc.c:5332
   unlink_chunk (p=p@entry=0x55c22905f000, av=0x7fa8703d8b80 ) at 
malloc.c:1460
   _int_malloc (av=av@entry=0x7fa8703d8b80 , bytes=bytes@entry=184) 
at malloc.c:4041
   __libc_calloc (n=, elem_size=) at malloc.c:3428
  Title: cups-browsed assert failure: corrupted double-linked list
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd05/17/2019:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  separator:

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

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

Title:
  cups-browsed assert failure: corrupted double-linked list

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  Same bug on Focal

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.26.0-1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AssertionMessage: corrupted

[Desktop-packages] [Bug 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1

2020-01-13 Thread Zack Kollar

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

This is scary thread for a relatively easy fix, for some reason dnsmasq
and OpenVPN don't play well together, it's as simple as commenting out
the "dns=dnsmasq" line in /etc/NetworkManager/NetworkManager.conf and
then restarting network manager.

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

Title:
  DNS server from vpn connection is not being used after network-manager
  upgrade to 1.2.6-0ubuntu0.16.04.1

Status in network-manager package in Ubuntu:
  Confirmed
Status in resolvconf package in Ubuntu:
  Invalid

Bug description:
  I use my company's cisco vpn via network-manager in Ubuntu 16.04.2
  LTS. After recent upgrade of network-manager:amd64 from version
  1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS
  resolution of VPN's server hostnames does not work. Roll back to
  version 1.2.2-0ubuntu0.16.04.4 solves the problem.

  Steps for reproducing:
  1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to 
version 1.2.6-0ubuntu0.16.04.1
  2. connect to VPN via network-manager applet
  3. nslookop servername.internal --> ** server can't find servername.internal: 
NXDOMAIN
  4. disconnect from VPN via network-manager applet
  5. roll back network-manager via command: sudo apt-get install 
network-manager=1.2.2-0ubuntu0.16.04.4
  6. restart network-manager via sudo service network-manager restart
  7. connect to VPN via network-manager applet
  8. nslookop servername.internal --> the server is resolved correctly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Mar  9 19:49:55 2017
  InstallationDate: Installed on 2015-10-05 (520 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Desktop-packages] [Bug 1859514] [NEW] Ubuntu 16.04 - keyboard and mouse unresponsive after install

2020-01-13 Thread Esteban Richey

Public bug reported:

I installed xserver-xorg-input-synaptics in an attempt to fix my dell
inspiron 15 3567 laptop's problems with the touchpad. I have ubuntu
16.04 installed and a synaptics touchpad. After installing xserver-xorg-
input-synaptics and its two dependencies, my laptop's keyboard and
mouse, when running ubuntu. is completely unresponsive. Please let me
know what I can do to fix this problem, aside from a total reinstall of
ubuntu. My email is e [dot] vince0130 [at] gmail [dot] com

** Affects: xserver-xorg-input-synaptics (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu 16.04 - keyboard and mouse unresponsive after install

Status in xserver-xorg-input-synaptics package in Ubuntu:
  New

Bug description:
  I installed xserver-xorg-input-synaptics in an attempt to fix my dell
  inspiron 15 3567 laptop's problems with the touchpad. I have ubuntu
  16.04 installed and a synaptics touchpad. After installing xserver-
  xorg-input-synaptics and its two dependencies, my laptop's keyboard
  and mouse, when running ubuntu. is completely unresponsive. Please let
  me know what I can do to fix this problem, aside from a total
  reinstall of ubuntu. My email is e [dot] vince0130 [at] gmail [dot]
  com

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1859514/+subscriptions

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

[Desktop-packages] [Bug 1859515] [NEW] device no longer recognized after activating Tethering USB

2020-01-13 Thread betteropensource

Public bug reported:

I connect my Android device to the PC with a USB cable.
It appears in the devices section in nautilus and I can read its data.
If I activate Tethering USB on the device, I can use the internet connection 
but immediately the device  being no longer available in nautilus, nemo, and 
every other program that read the smartphone data.
If I deactivate USB tethering, the device reappear in the "devices" section.
This problem weren't present in the 18.04 version...
I'm using the same computer with the same USB cable with the same smartphone, 
so the problem is sure due to something other. The problem occurs only since 
when I installed Ubuntu 19.10, until some days ago with the 18.04 all was 
working fine.

lsb_release -rd:
Description:Ubuntu 19.10
Release:19.10

apt-cache policy nautilus:
nautilus:
  Installed: 1:3.34.1-1ubuntu1
  Candidate:  1:3.34.1-1ubuntu1
  Version table:
 *** 1:3.34.1-1ubuntu1 500
500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status

apt-cache policy nemo:
nemo:
  Installed: 4.0.6-1
  Candidate:  4.0.6-1
  Version table:
 *** 4.0.6-1 500
500 http://it.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 13 20:14:02 2020
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'maximized' b'true'
 b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
 b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
 b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
InstallationDate: Installed on 2020-01-09 (4 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug devices eoan usb-tethering

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

Title:
  device no longer recognized after activating Tethering USB

Status in nautilus package in Ubuntu:
  New

Bug description:
  I connect my Android device to the PC with a USB cable.
  It appears in the devices section in nautilus and I can read its data.
  If I activate Tethering USB on the device, I can use the internet connection 
but immediately the device  being no longer available in nautilus, nemo, and 
every other program that read the smartphone data.
  If I deactivate USB tethering, the device reappear in the "devices" section.
  This problem weren't present in the 18.04 version...
  I'm using the same computer with the same USB cable with the same smartphone, 
so the problem is sure due to something other. The problem occurs only since 
when I installed Ubuntu 19.10, until some days ago with the 18.04 all was 
working fine.

  lsb_release -rd:
  Description:  Ubuntu 19.10
  Release:  19.10

  apt-cache policy nautilus:
  nautilus:
Installed: 1:3.34.1-1ubuntu1
Candidate:  1:3.34.1-1ubuntu1
Version table:
   *** 1:3.34.1-1ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  apt-cache policy nemo:
  nemo:
Installed: 4.0.6-1
Candidate:  4.0.6-1
Version table:
   *** 4.0.6-1 500
  500 http://it.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: nautilus 1:3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  Uname: Linux 5.3.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 20:14:02 2020
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.list-view' b'default-zoom-level' b"'small'"
   b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 
'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 
'date_modified_with_time', 'date_accessed', 'recency', 'starred', 
'detailed_type']"
  InstallationDate: Installed on 2020-01-09 (4 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  ProcEnviron:

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

** Package changed: network-manager-openconnect (Ubuntu) => gnome-shell
(Ubuntu)

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

Title:
  username is not saved in openconnect connection dialog

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Same issue as https://bugs.launchpad.net/ubuntu/+source/network-
  manager-openconnect/+bug/1609700

  This was marked resolved. The report of its reappearance in Ubuntu
  19.04 and 19.10 has not been acknowledged.

  This was working for me in 18.10, but a fresh install of 19.04 and
  19.10 show that it is back. The password is saved when the option to
  save passwords is selected, but the username must be entered manually
  upon connection.

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

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

[Desktop-packages] [Bug 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome

2020-01-13 Thread Norbert

@Daniel van Vugt (vanvugt)

`apport-bug /var/crash/_usr_lib_xorg_Xorg.0.crash` says that the problem
is already known and redirects me here, to this bug report. So I can't
report the problem as new bug. If you are interested, please
parse/unpack crash file above in comment 8.

Installing proposed updates does not change the situation.

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

Title:
  X11 crashed when attempting to open Budgie and MATE Welcome

Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in ubuntu-mate-welcome package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Went to the menu button in upper left corner. Attempted to open Budgie
  Welcome and the X11 session crashed. About 4 lines of error code were
  displayed for a few seconds then the login screen appeared.

  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10
  budgie-welcome:
Installed: (none)
Candidate: 0.6.1
Version table:
   0.6.1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages

  Seems to not be installed on a fresh install. So solved but needs
  fixing?

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.20.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AssertionMessage: Xorg: ../../../../../../include/privates.h:121: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  BootLog:
   [[0;32m  OK  [0m] Stopped Snappy daemon.
Starting Snappy daemon...
  CompositorRunning: None
  CrashCounter: 1
  Date: Fri Oct  5 20:36:30 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  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 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 
(20181005)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 
"../../../../../../include/privates.h", line=121, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", 
file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, 
function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101
   ?? ()
  Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS IX FORMULA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1857815] Re: cups-browsed assert failure: corrupted double-linked list

2020-01-13 Thread Till Kamppeter

seb128, as you have found a way to reliably reproduce the bug, I want to
ask you to do the following:

Run the command

cupsctl --debug-logging

to activate logginf by CUPS.

Edit the /etc/cups/cups-browsed.conf file, making sure that it contains
a line

DebugLogging file

with no "#" in the beginning.

Stop cups-browsed with

sudo systemctl stop cups-browsed

Wait some minutes, click away any apport pop-up.

If you get a crash now it is NOT yet covered by the debug logging.

Now start cups-browsed with

sudo systemctl start cups-browsed

wait some minutes, run "lpstat -v" repeatedly until no more remote
queues get discovered.

If it did not crash yet, shut down cups-browsed with

sudo systemctl stop cups-browsed

Wait some minutes.

If it did not crash yet, repeat this procedure until you get a crash.

Now attach the following files:

/etc/cups/cups-files.conf
/etc/cups/cupsd.conf
/etc/cups/cups-browsed.conf
/var/log/cups/error_log
/var/log/cups/cups-browsed_log

Please attach the files one-by-one, do not compress them and do not
package them together.

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

Title:
  cups-browsed assert failure: corrupted double-linked list

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  Same bug on Focal

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.26.0-1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AssertionMessage: corrupted double-linked list
  CupsErrorLog:
   
  Date: Thu Dec 26 08:18:13 2019
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2019-12-12 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191211)
  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 002: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=ada0b905-9f6f-4911-9311-d1930ae73b8a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa8703a73a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7fa8703a54d3 "corrupted double-linked 
list") at malloc.c:5332
   unlink_chunk (p=p@entry=0x55c22905f000, av=0x7fa8703d8b80 ) at 
malloc.c:1460
   _int_malloc (av=av@entry=0x7fa8703d8b80 , bytes=bytes@entry=184) 
at malloc.c:4041
   __libc_calloc (n=, elem_size=) at malloc.c:3428
  Title: cups-browsed assert failure: corrupted double-linked list
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd05/17/2019:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  separator:

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

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

[Desktop-packages] [Bug 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome

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

** Changed in: ubuntu-mate-welcome (Ubuntu)
   Status: New => Confirmed

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

Title:
  X11 crashed when attempting to open Budgie and MATE Welcome

Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in ubuntu-mate-welcome package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Went to the menu button in upper left corner. Attempted to open Budgie
  Welcome and the X11 session crashed. About 4 lines of error code were
  displayed for a few seconds then the login screen appeared.

  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10
  budgie-welcome:
Installed: (none)
Candidate: 0.6.1
Version table:
   0.6.1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages

  Seems to not be installed on a fresh install. So solved but needs
  fixing?

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.20.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AssertionMessage: Xorg: ../../../../../../include/privates.h:121: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  BootLog:
   [[0;32m  OK  [0m] Stopped Snappy daemon.
Starting Snappy daemon...
  CompositorRunning: None
  CrashCounter: 1
  Date: Fri Oct  5 20:36:30 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  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 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 
(20181005)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 
"../../../../../../include/privates.h", line=121, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", 
file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, 
function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101
   ?? ()
  Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS IX FORMULA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1796437/+subscriptions

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

[Desktop-packages] [Bug 1796437] Re: X11 crashed when attempting to open Budgie and MATE Welcome

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

** Changed in: ubuntu-mate-meta (Ubuntu)
   Status: New => Confirmed

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

Title:
  X11 crashed when attempting to open Budgie and MATE Welcome

Status in ubuntu-mate-meta package in Ubuntu:
  Confirmed
Status in ubuntu-mate-welcome package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Won't Fix

Bug description:
  Went to the menu button in upper left corner. Attempted to open Budgie
  Welcome and the X11 session crashed. About 4 lines of error code were
  displayed for a few seconds then the login screen appeared.

  Description:  Ubuntu Cosmic Cuttlefish (development branch)
  Release:  18.10
  budgie-welcome:
Installed: (none)
Candidate: 0.6.1
Version table:
   0.6.1 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu cosmic/universe i386 Packages

  Seems to not be installed on a fresh install. So solved but needs
  fixing?

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: xserver-xorg-core 2:1.20.1-3ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AssertionMessage: Xorg: ../../../../../../include/privates.h:121: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  BootLog:
   [[0;32m  OK  [0m] Stopped Snappy daemon.
Starting Snappy daemon...
  CompositorRunning: None
  CrashCounter: 1
  Date: Fri Oct  5 20:36:30 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  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 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 18.10 "Cosmic Cuttlefish" - Beta amd64 
(20181005)
  MachineType: System manufacturer System Product Name
  ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth 
/var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=21545d40-8bcb-45b5-b710-8521590b95a5 ro quiet splash vt.handoff=1
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   __assert_fail_base (fmt=0x7f29afb85858 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=0x55c50dca64bb "key->initialized", file=0x55c50dcaa9b0 
"../../../../../../include/privates.h", line=121, function=) at 
assert.c:92
   __GI___assert_fail (assertion=0x55c50dca64bb "key->initialized", 
file=0x55c50dcaa9b0 "../../../../../../include/privates.h", line=121, 
function=0x55c50dccc0c0 "dixGetPrivateAddr") at assert.c:101
   ?? ()
  Title: Xorg assert failure: Xorg: ../../../../../../include/privates.h:121: 
dixGetPrivateAddr: Assertion `key->initialized' failed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/14/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1301
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS IX FORMULA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd03/14/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSIXFORMULA:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1build1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-meta/+bug/1796437/+subscriptions

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

[Desktop-packages] [Bug 1858500] Re: Upgrading from 19.04 to 19.10 will keep the 19.04 chromium-browser due to a higher version than the transitional deb in 19.10

2020-01-13 Thread Sønke Lorenzen

This worked for me too after enabling eoan-proposed, I have now the snap
on that installation.

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

Title:
  Upgrading from 19.04 to 19.10 will keep the 19.04 chromium-browser due
  to a higher version than the transitional deb in 19.10

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  Users upgrading from 19.04 to 19.10 will not get the latest chromium snap 
replacing the chromium-browser deb package as intended.
  This is because the version number in 19.04 is greater than the version in 
19.10. Bumping the version number in 19.10 is enough to fix this.

  [Test Case]

   * On a machine running 19.04, ensure that the chromium snap is *not* 
installed, then install the chromium-browser deb package: sudo apt install 
chromium-browser
   * Upgrade that machine to Ubuntu 19.10
   * When upgrading, the chromium-browser package becomes a transitional 
package that installs the chromium snap
   * Verify that the chromium snap is installed

  [Regression Potential]

   * The chromium snap has some known shortcomings and regressions compared to 
the deb package, they are being tracked at 
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap.
 Auto-upgrading users from the deb to the snap is the desired behaviour though.
   * Version 79.0.3945.79-0ubuntu0.19.10.2 which is being uploaded also 
contains a couple of minor unrelated changes, but those are harmless. They are 
included because they were already pushed to the source package's VCS:
 - 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1525
 - 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1526

  [Original Description]

  19.04 has got a higher version chromium-browser now than the
  transitional deb package that install the snap version, so the 19.04
  version will be kept when someone upgrades since 19.04 got a higher
  version, and then no further updates.

  apt show chromium-browser -a
  Package: chromium-browser
  Version: 79.0.3945.79-0ubuntu0.19.04.3
  Status: install ok installed
  Priority: optional
  Section: web
  Maintainer: Ubuntu Developers 
  Installed-Size: 225 MB
  Provides: chromium-browser-inspector, www-browser
  Pre-Depends: dpkg (>= 1.15.6)
  Depends: libasound2 (>= 1.0.16), libatk-bridge2.0-0 (>= 2.5.3), libatk1.0-0 
(>= 2.2.0), libatspi2.0-0 (>= 2.9.90), libc6 (>= 2.29), libcairo2 (>= 1.6.0), 
libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.9.14), libexpat1 (>= 2.0.1), libgcc1 (>= 
1:4.0), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), libgtk-3-0 
(>= 3.9.10), libnspr4 (>= 2:4.9-2~), libnss3 (>= 2:3.22), libpango-1.0-0 (>= 
1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libstdc++6 (>= 7), libx11-6 (>= 
2:1.4.99.1), libx11-xcb1, libxcb1 (>= 1.6), libxcomposite1 (>= 1:0.3-1), 
libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3 (>= 
1:5.0), libxi6 (>= 2:1.2.99.4), libxrandr2 (>= 2:1.2.99.3), libxrender1, 
libxss1, libxtst6, bash (>= 4), xdg-utils, chromium-codecs-ffmpeg-extra (= 
79.0.3945.79-0ubuntu0.19.04.3) | chromium-codecs-ffmpeg (= 
79.0.3945.79-0ubuntu0.19.04.3)
  Recommends: chromium-browser-l10n
  Suggests: webaccounts-chromium-extension, unity-chromium-extension, 
adobe-flashplugin
  Conflicts: chromium-browser-inspector
  Replaces: chromium-browser-inspector
  Homepage: https://chromium.googlesource.com/chromium/src/
  Download-Size: unknown
  APT-Manual-Installed: yes
  APT-Sources: /var/lib/dpkg/status
  Description: Chromium web browser, open-source version of Chrome
   An open-source browser project that aims to build a safer, faster, and more
   stable way for all Internet users to experience the web.

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1.19.10.1
  Priority: optional
  Section: universe/web
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 163 kB
  Provides: www-browser
  Pre-Depends: debconf, snapd
  Depends: debconf (>= 0.5) | debconf-2.0
  Homepage: https://chromium.googlesource.com/chromium/src/
  Download-Size: 48.7 kB
  APT-Sources: http://dk.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 
Packages
  Description: Transitional package - chromium-browser -> chromium snap
   This is a transitional dummy package. It can safely be removed.
   .
   chromium-browser is now replaced by the chromium snap.

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1~snap1
  Priority: optional
  Section: universe/web
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 163 kB
  Provides: www-browser
  Pre-Depends: debconf, snapd
  Depends: debconf (>= 0.5) |

[Desktop-packages] [Bug 1826056] Re: Desktop context: Keep aligned, Organize desktop by name missing in 19.04

2020-01-13 Thread Joseph-conner

Applies to 19.10 as well

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

Title:
  Desktop context: Keep aligned, Organize desktop by name missing in
  19.04

Status in gnome-shell-extension-desktop-icons:
  Fix Released
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 18.10 to 19.04 the desktop context menu no longer
  contains the choices:

  Keep aligned
  Organize desktop by name

  These were very useful to me. I would like them to be restored.

  Ubuntu 19.04, 64bit
  Gnome 3.32.1

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

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

[Desktop-packages] [Bug 1857815] Re: cups-browsed assert failure: corrupted double-linked list

You are right Till, it seems to segfault when the service is stopped, following 
your step, when doing
$ sudo systemctl stop cups-browsed
the apport prompt is displayed

the error_log is empty though

Can you try if you get the issue on stopping the service?


Note that the valgrind log error is not happening on stop so there is still 
something weird/buggy in that codepath

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

Title:
  cups-browsed assert failure: corrupted double-linked list

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  Same bug on Focal

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.26.0-1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AssertionMessage: corrupted double-linked list
  CupsErrorLog:
   
  Date: Thu Dec 26 08:18:13 2019
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2019-12-12 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191211)
  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 002: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=ada0b905-9f6f-4911-9311-d1930ae73b8a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa8703a73a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7fa8703a54d3 "corrupted double-linked 
list") at malloc.c:5332
   unlink_chunk (p=p@entry=0x55c22905f000, av=0x7fa8703d8b80 ) at 
malloc.c:1460
   _int_malloc (av=av@entry=0x7fa8703d8b80 , bytes=bytes@entry=184) 
at malloc.c:4041
   __libc_calloc (n=, elem_size=) at malloc.c:3428
  Title: cups-browsed assert failure: corrupted double-linked list
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd05/17/2019:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  separator:

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

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

[Desktop-packages] [Bug 1853574] Re: Syntax error in /usr/bin/chromium-browser when xdg-settings get default-web-browser is empty

2020-01-13 Thread Laurent Bonnaud

The problem is also fixed on my system.
Thanks everybody for the fix!

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

Title:
  Syntax error in /usr/bin/chromium-browser when xdg-settings get
  default-web-browser is empty

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  Minor. Apparently under certain circumstances "xdg-settings get 
default-web-browser" can return an empty string (although I haven't been able 
to reproduce this myself), and this will make the /usr/bin/chromium-browser 
wrapper script spit out a console error (but it won't prevent it from running 
the browser).
  This is trivial to fix by enclosing the call to "xdg-settings get 
default-web-browser" in double quotes, to cater for the empty result case (see 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1526).

  
  [Test Case]

  1. Install chromium-browser
  2. Patch /usr/bin/xdg-settings to make the get_browser_gnome3() function 
return an empty string (replace its body with 'echo ""')
  3. From a terminal, run "chromium-browser"

  Expected result: no error
  Current result: /usr/bin/chromium-browser: 12: [: =: unexpected operator

  
  [Regression Potential]

  Low, enclosing a call to a command in double quotes in bash shouldn't
  have any undesirable side effect, and that's all that the patch does.

  
  [Original Description]

  Hi,

  here is the error:

  $ chromium-browser
  /usr/bin/chromium-browser: 12: [: =: unexpected operator
  [...]

  Here is line 12 in /usr/bin/chromium-browser:

  if [ $(xdg-settings get default-web-browser) = "chromium-
  browser.desktop" ]; then

  The error occurs because on my system the default-web-browser setting
  is unset:

  $ xdg-settings get default-web-browser
  [nothing]

  I suggest putting double quotes around:

  if [ "$(xdg-settings get default-web-browser)" = "chromium-
  browser.desktop" ]; then

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  Uname: Linux 5.3.12-050312-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.3
  Architecture: amd64
  CurrentDesktop: KDE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAJ5csGAAEaAQSVIhN4CvmglV1ZlCkkUFQBAQEBAQEBAQEBAQEBAQEBGjuAJHE4PEAwIDYAWMIQAAAa/S2ADnE4KEAwIDYAWMIQAAAa/gBSTUpDWYBOVjE1TjQyQSKWABoBCiAgAMg=
   modes: 1920x1080 1920x1080
  Date: Fri Nov 22 10:27:14 2019
  DiskUsage:
   Filesystem  Type   Size  Used Avail Use% Mounted on
   /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
   tmpfs   tmpfs  7.8G  124M  7.7G   2% /dev/shm
   /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse 
(M-BT58)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.12-050312-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
intel_iommu=on quiet splash vt.handoff=7
  Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.108 
(4b26898a39ee037623a72fcfb77279fce0e7d648-refs/branch-heads/3904@{#889})
  Snap.ChromiumVersion:
   /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
   Chromium 78.0.3904.108 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0VYDFF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd07/19/2019:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0VYDFF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5590
  dmi.product.sku: 0817
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1859485] Re: remmina crashed with SIGSEGV

2020-01-13 Thread El jinete sin cabeza

** Also affects: remmina-ppa via
   https://gitlab.com/Remmina/Remmina/issues/2059
   Importance: Unknown
   Status: Unknown

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

Title:
  remmina crashed with SIGSEGV

Status in remmina-ppa:
  Unknown
Status in remmina package in Ubuntu:
  New

Bug description:
  Close session of Win10(remote).

  ---

  https://gitlab.com/Remmina/Remmina/issues/2059

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: remmina 1.3.10+dfsg-1ubuntu1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 12:08:00 2020
  ExecutablePath: /usr/bin/remmina
  InstallationDate: Installed on 2018-12-02 (406 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: remmina
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f9442a77ac0:movdqu 0x10(%rax),%xmm2
   PC (0x7f9442a77ac0) ok
   source "0x10(%rax)" (0x7f941f872a60) not located in a known VMA region 
(needed readable region)!
   destination "%xmm2" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: remmina
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   pixman_blt () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: remmina crashed with SIGSEGV
  UpgradeStatus: Upgraded to focal on 2018-12-02 (406 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/remmina-ppa/+bug/1859485/+subscriptions

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

[Desktop-packages] [Bug 1853574] Re: Syntax error in /usr/bin/chromium-browser when xdg-settings get default-web-browser is empty

Verified. I followed the steps in the test case by installing chromium-
browser in a clean eoan VM and verified that after patching
get_browser_gnome3() in /usr/bin/xdg-settings I got the error message in
the console. I then enabled eoan-proposed, installed the chromium-
browser update (79.0.3945.79-0ubuntu0.19.10.2), and after that the error
is gone when running chromium-browser.

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

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

Title:
  Syntax error in /usr/bin/chromium-browser when xdg-settings get
  default-web-browser is empty

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  Minor. Apparently under certain circumstances "xdg-settings get 
default-web-browser" can return an empty string (although I haven't been able 
to reproduce this myself), and this will make the /usr/bin/chromium-browser 
wrapper script spit out a console error (but it won't prevent it from running 
the browser).
  This is trivial to fix by enclosing the call to "xdg-settings get 
default-web-browser" in double quotes, to cater for the empty result case (see 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1526).

  
  [Test Case]

  1. Install chromium-browser
  2. Patch /usr/bin/xdg-settings to make the get_browser_gnome3() function 
return an empty string (replace its body with 'echo ""')
  3. From a terminal, run "chromium-browser"

  Expected result: no error
  Current result: /usr/bin/chromium-browser: 12: [: =: unexpected operator

  
  [Regression Potential]

  Low, enclosing a call to a command in double quotes in bash shouldn't
  have any undesirable side effect, and that's all that the patch does.

  
  [Original Description]

  Hi,

  here is the error:

  $ chromium-browser
  /usr/bin/chromium-browser: 12: [: =: unexpected operator
  [...]

  Here is line 12 in /usr/bin/chromium-browser:

  if [ $(xdg-settings get default-web-browser) = "chromium-
  browser.desktop" ]; then

  The error occurs because on my system the default-web-browser setting
  is unset:

  $ xdg-settings get default-web-browser
  [nothing]

  I suggest putting double quotes around:

  if [ "$(xdg-settings get default-web-browser)" = "chromium-
  browser.desktop" ]; then

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  Uname: Linux 5.3.12-050312-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.3
  Architecture: amd64
  CurrentDesktop: KDE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAJ5csGAAEaAQSVIhN4CvmglV1ZlCkkUFQBAQEBAQEBAQEBAQEBAQEBGjuAJHE4PEAwIDYAWMIQAAAa/S2ADnE4KEAwIDYAWMIQAAAa/gBSTUpDWYBOVjE1TjQyQSKWABoBCiAgAMg=
   modes: 1920x1080 1920x1080
  Date: Fri Nov 22 10:27:14 2019
  DiskUsage:
   Filesystem  Type   Size  Used Avail Use% Mounted on
   /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
   tmpfs   tmpfs  7.8G  124M  7.7G   2% /dev/shm
   /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse 
(M-BT58)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.12-050312-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
intel_iommu=on quiet splash vt.handoff=7
  Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.108 
(4b26898a39ee037623a72fcfb77279fce0e7d648-refs/branch-heads/3904@{#889})
  Snap.ChromiumVersion:
   /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
   Chromium 78.0.3904.108 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0VYDFF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd07/19/2019:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0VYDFF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude

[Desktop-packages] [Bug 1858500] Re: Upgrading from 19.04 to 19.10 will keep the 19.04 chromium-browser due to a higher version than the transitional deb in 19.10

Verified working. I followed the steps in the test case: in a clean
disco VM, I installed chromium-browser (and verified that the chromium
snap wasn't installed). I then dist-upgraded the VM to eoan, and
verified that chromium-browser hadn't been updated, and that the
chromium snap still wasn't there. I then enabled eoan-proposed in
/etc/apt/source.list, updated, installed the chromium-browser update
that was available (79.0.3945.79-0ubuntu0.19.10.2), and the chromium
snap got installed, as expected.

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

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

Title:
  Upgrading from 19.04 to 19.10 will keep the 19.04 chromium-browser due
  to a higher version than the transitional deb in 19.10

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  Users upgrading from 19.04 to 19.10 will not get the latest chromium snap 
replacing the chromium-browser deb package as intended.
  This is because the version number in 19.04 is greater than the version in 
19.10. Bumping the version number in 19.10 is enough to fix this.

  [Test Case]

   * On a machine running 19.04, ensure that the chromium snap is *not* 
installed, then install the chromium-browser deb package: sudo apt install 
chromium-browser
   * Upgrade that machine to Ubuntu 19.10
   * When upgrading, the chromium-browser package becomes a transitional 
package that installs the chromium snap
   * Verify that the chromium snap is installed

  [Regression Potential]

   * The chromium snap has some known shortcomings and regressions compared to 
the deb package, they are being tracked at 
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap.
 Auto-upgrading users from the deb to the snap is the desired behaviour though.
   * Version 79.0.3945.79-0ubuntu0.19.10.2 which is being uploaded also 
contains a couple of minor unrelated changes, but those are harmless. They are 
included because they were already pushed to the source package's VCS:
 - 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1525
 - 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1526

  [Original Description]

  19.04 has got a higher version chromium-browser now than the
  transitional deb package that install the snap version, so the 19.04
  version will be kept when someone upgrades since 19.04 got a higher
  version, and then no further updates.

  apt show chromium-browser -a
  Package: chromium-browser
  Version: 79.0.3945.79-0ubuntu0.19.04.3
  Status: install ok installed
  Priority: optional
  Section: web
  Maintainer: Ubuntu Developers 
  Installed-Size: 225 MB
  Provides: chromium-browser-inspector, www-browser
  Pre-Depends: dpkg (>= 1.15.6)
  Depends: libasound2 (>= 1.0.16), libatk-bridge2.0-0 (>= 2.5.3), libatk1.0-0 
(>= 2.2.0), libatspi2.0-0 (>= 2.9.90), libc6 (>= 2.29), libcairo2 (>= 1.6.0), 
libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.9.14), libexpat1 (>= 2.0.1), libgcc1 (>= 
1:4.0), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), libgtk-3-0 
(>= 3.9.10), libnspr4 (>= 2:4.9-2~), libnss3 (>= 2:3.22), libpango-1.0-0 (>= 
1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libstdc++6 (>= 7), libx11-6 (>= 
2:1.4.99.1), libx11-xcb1, libxcb1 (>= 1.6), libxcomposite1 (>= 1:0.3-1), 
libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3 (>= 
1:5.0), libxi6 (>= 2:1.2.99.4), libxrandr2 (>= 2:1.2.99.3), libxrender1, 
libxss1, libxtst6, bash (>= 4), xdg-utils, chromium-codecs-ffmpeg-extra (= 
79.0.3945.79-0ubuntu0.19.04.3) | chromium-codecs-ffmpeg (= 
79.0.3945.79-0ubuntu0.19.04.3)
  Recommends: chromium-browser-l10n
  Suggests: webaccounts-chromium-extension, unity-chromium-extension, 
adobe-flashplugin
  Conflicts: chromium-browser-inspector
  Replaces: chromium-browser-inspector
  Homepage: https://chromium.googlesource.com/chromium/src/
  Download-Size: unknown
  APT-Manual-Installed: yes
  APT-Sources: /var/lib/dpkg/status
  Description: Chromium web browser, open-source version of Chrome
   An open-source browser project that aims to build a safer, faster, and more
   stable way for all Internet users to experience the web.

  Package: chromium-browser
  Version: 77.0.3865.120-0ubuntu1.19.10.1
  Priority: optional
  Section: universe/web
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 163 kB
  Provides: www-browser
  Pre-Depends: debconf, snapd
  Depends: debconf (>= 0.5) | debconf-2.0
  Homepage: https://chromium.googlesource.com/chromium/src/
  Download-Size: 48.7 kB
  APT-Sources: http://dk.archive.ubuntu.com/ubuntu eoan-updates/universe amd64 
Packages
  Description: Transitional package -

[Desktop-packages] [Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode

2020-01-13 Thread Colin Watson

@mevsme: This isn't acceptable in Launchpad; please see the Ubuntu Code
of Conduct.  I've hidden this comment.

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

Title:
  Mouse cursor gets stuck in "drag and drop" mode

Status in OpenShot Video Editor:
  New
Status in X.Org X server:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in rapidsvn package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: rapidsvn

  When clicking on the Bookmark root or on one of the bookmarks below
  the mouse cursor gets stuck in "drag n drop" mode, blocking all
  keyboard entry and also mouse clicks for the the whole GUI
  (systemwide).

  Unfortunately I cannot provide any debug or other information, as I
  have to reboot everytime.

  I am running Ubuntu 9.04 with compiz enabled.

  Many thanks in advance for your help with this problem,
  /nxT

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

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

[Desktop-packages] [Bug 1806232] Re: Graphical artifacts/glitches on Intel Atom x5 - Screen Tearing

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

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

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

Title:
  Graphical artifacts/glitches on Intel Atom x5 - Screen Tearing

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  There is screen tearing on the left side of the screen, and it's
  especially apparent when there's motion on the entire screen. This is
  happening on Ubuntu 18.10 on an Asus T102HA with an Atom x5 Cherry
  Trail.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec  2 00:59:01 2018
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series 
PCI Configuration Registers [8086:22b0] (rev 36) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor 
x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1400]
  InstallationDate: Installed on 2018-12-02 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: ASUSTeK COMPUTER INC. T102HA
  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-11-generic 
root=UUID=6d4342e4-1f2b-42ea-850e-63e34c955cd3 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: T102HA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: T102HA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrT102HA.204:bd07/18/2016:svnASUSTeKCOMPUTERINC.:pnT102HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT102HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: T
  dmi.product.name: T102HA
  dmi.product.sku: ASUS-TabletSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  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 N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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

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

[Desktop-packages] [Bug 1859485] Re: remmina crashed with SIGSEGV

2020-01-13 Thread El jinete sin cabeza

https://gitlab.com/Remmina/Remmina/issues/2059

** Information type changed from Private to Public

** Description changed:

  Close session of Win10(remote).
+ 
+ ---
+ 
+ https://gitlab.com/Remmina/Remmina/issues/2059
  
  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: remmina 1.3.10+dfsg-1ubuntu1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 12:08:00 2020
  ExecutablePath: /usr/bin/remmina
  InstallationDate: Installed on 2018-12-02 (406 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: remmina
  ProcEnviron:
-  SHELL=/bin/bash
-  LANGUAGE=es_CL:es
-  LANG=es_CL.UTF-8
-  XDG_RUNTIME_DIR=
-  PATH=(custom, no user)
+  SHELL=/bin/bash
+  LANGUAGE=es_CL:es
+  LANG=es_CL.UTF-8
+  XDG_RUNTIME_DIR=
+  PATH=(custom, no user)
  SegvAnalysis:
-  Segfault happened at: 0x7f9442a77ac0:movdqu 0x10(%rax),%xmm2
-  PC (0x7f9442a77ac0) ok
-  source "0x10(%rax)" (0x7f941f872a60) not located in a known VMA region 
(needed readable region)!
-  destination "%xmm2" ok
+  Segfault happened at: 0x7f9442a77ac0:movdqu 0x10(%rax),%xmm2
+  PC (0x7f9442a77ac0) ok
+  source "0x10(%rax)" (0x7f941f872a60) not located in a known VMA region 
(needed readable region)!
+  destination "%xmm2" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: remmina
  StacktraceTop:
-  () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
-  () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
-  pixman_blt () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
-  () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
-  () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
+  () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
+  () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
+  pixman_blt () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
+  () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
+  () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: remmina crashed with SIGSEGV
  UpgradeStatus: Upgraded to focal on 2018-12-02 (406 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

** Bug watch added: gitlab.com/Remmina/Remmina/issues #2059
   https://gitlab.com/Remmina/Remmina/issues/2059

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

Title:
  remmina crashed with SIGSEGV

Status in remmina package in Ubuntu:
  New

Bug description:
  Close session of Win10(remote).

  ---

  https://gitlab.com/Remmina/Remmina/issues/2059

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: remmina 1.3.10+dfsg-1ubuntu1
  Uname: Linux 5.4.11-050411-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 12:08:00 2020
  ExecutablePath: /usr/bin/remmina
  InstallationDate: Installed on 2018-12-02 (406 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: remmina
  ProcEnviron:
   SHELL=/bin/bash
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SegvAnalysis:
   Segfault happened at: 0x7f9442a77ac0:movdqu 0x10(%rax),%xmm2
   PC (0x7f9442a77ac0) ok
   source "0x10(%rax)" (0x7f941f872a60) not located in a known VMA region 
(needed readable region)!
   destination "%xmm2" ok
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: remmina
  StacktraceTop:
   () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   pixman_blt () at /usr/lib/x86_64-linux-gnu/libpixman-1.so.0
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
   () at /usr/lib/x86_64-linux-gnu/libcairo.so.2
  Title: remmina crashed with SIGSEGV
  UpgradeStatus: Upgraded to focal on 2018-12-02 (406 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

** Description changed:

  [ Impact ]
  
  Not able to adjust Audio input UI volume if this device doesn't have a
  internal mic, the volume bar will be gray.
  
  [ Test Case ]
  
  1. Boot ubuntu without any external headset connected.
  2. Launch gnome-control-center and switch to Sound->Input tab.
  3. Connect external headset, then you will find the input show up but can not 
adjust the volume.
  
  [ Regression potential ]
  
- Low.
+ Low. change is the workaround to active/deactivate some bugs which
+ didn't report things in the right order. It will just have extra
+ active/deactiveate actions in normal situation(which the machines don't
+ have this issue).
+ 
+ Verified on built-in and non built-in input device machines , no
+ regression found yet.
  
  Package in this PPA:
  https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages
  
  
  
  Summary:Not able to adjust Audio input UI volume, it's gray
  
  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack
  
  Expected result:
  System can be recording audio from external mic
  
  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox
  
  Failure rate:100%
  
  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2
  
  Note:20.04, 19.10, 19.04 are immune on the bug

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

Title:
  [SRU]Not able to adjust Audio input UI volume after connecting headset

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project bionic series:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  Not able to adjust Audio input UI volume if this device doesn't have a
  internal mic, the volume bar will be gray.

  [ Test Case ]

  1. Boot ubuntu without any external headset connected.
  2. Launch gnome-control-center and switch to Sound->Input tab.
  3. Connect external headset, then you will find the input show up but can not 
adjust the volume.

  [ Regression potential ]

  Low. change is the workaround to active/deactivate some bugs which
  didn't report things in the right order. It will just have extra
  active/deactiveate actions in normal situation(which the machines
  don't have this issue).

  Verified on built-in and non built-in input device machines , no
  regression found yet.

  Package in this PPA:
  https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages

  

  Summary:Not able to adjust Audio input UI volume, it's gray

  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack

  Expected result:
  System can be recording audio from external mic

  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox

  Failure rate:100%

  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

  Note:20.04, 19.10, 19.04 are immune on the bug

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

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

[Desktop-packages] [Bug 1859437] Re: gnome-software crashed with SIGSEGV in as_app_add_provide()

2020-01-13 Thread El jinete sin cabeza

** Information type changed from Private to Public

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

Title:
  gnome-software crashed with SIGSEGV in as_app_add_provide()

Status in gnome-software package in Ubuntu:
  New

Bug description:
  I don't know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.30.6-2ubuntu11
  Uname: Linux 5.4.10-050410-generic x86_64
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 10 07:52:49 2020
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2018-12-02 (406 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.6-2ubuntu11
   gnome-software-plugin-snap3.30.6-2ubuntu11
  ProcCmdline: /usr/bin/gnome-software --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=es_CL:es
   LANG=es_CL.UTF-8
  SegvAnalysis:
   Segfault happened at: 0x7f0fdeeb2c84 :mov
(%rdx,%rax,8),%r14
   PC (0x7f0fdeeb2c84) ok
   source "(%rdx,%rax,8)" (0x2e70) not located in a known VMA region 
(needed readable region)!
   destination "%r14" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: gnome-software
  StacktraceTop:
   as_app_add_provide () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
   () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
   as_store_add_apps () at /usr/lib/x86_64-linux-gnu/libappstream-glib.so.8
   () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so
   () at /usr/lib/x86_64-linux-gnu/gs-plugins-12/libgs_plugin_flatpak.so
  Title: gnome-software crashed with SIGSEGV in as_app_add_provide()
  UpgradeStatus: Upgraded to focal on 2018-12-02 (406 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1859468] [NEW] dialog windows spanning across dual monitors poorly

2020-01-13 Thread pleabargain

Public bug reported:

lsb_release -rd
Description:Ubuntu 19.10
Release:19.10


apt-cache policy xorg
xorg:
  Installed: 1:7.7+19ubuntu12
  Candidate: 1:7.7+19ubuntu12
  Version table:
 *** 1:7.7+19ubuntu12 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status


the dialog windows are spanning across my two monitors.

1 open dialog for saving file
2 window opens and spans across the two monitors
3 user buttons open/cancel/save are hidden in the UI. The task bar on the left 
side is covering/hiding the dialog window buttons


desired behavior
dialog windows fit INSIDE a single monitor UI


please see the attached screenshots

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
Uname: Linux 5.3.0-26-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 13 15:41:37 2020
DistUpgraded: 2019-10-23 09:33:56,809 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, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:84ca]
InstallationDate: Installed on 2015-08-23 (1603 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to eoan on 2019-10-23 (82 days ago)
dmi.bios.date: 07/21/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2501
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z77-V LX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
xserver.bootTime: Mon Aug 20 17:24:57 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug eoan ubuntu

** Attachment added: "Screenshot (1).png"
   
https://bugs.launchpad.net/bugs/1859468/+attachment/5319789/+files/Screenshot%20%281%29.png

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

Title:
  dialog windows spanning across dual monitors poorly

Status in xorg package in Ubuntu:
  New

Bug description:
  lsb_release -rd
  Description:  Ubuntu 19.10
  Release:  19.10


  
  apt-cache policy xorg
  xorg:
Installed: 1:7.7+19ubuntu12
Candidate: 1:7.7+19ubuntu12
Version table:
   *** 1:7.7+19ubuntu12 500
  500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status


  
  the dialog windows are spanning across my two monitors.

  1 open dialog for saving file
  2 window opens and spans across the two monitors
  3 user buttons open/cancel/save are hidden in the UI. The task bar on the 
left side is covering/hiding the dialog window buttons

  
  desired behavior
  dialog windows fit INSIDE a single monitor UI


  please see the attached screenshots

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu

[Desktop-packages] [Bug 1853584] Please test proposed package

Hello hugh, or anyone else affected,

Accepted gnome-control-center into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.28.2-0ubuntu0.18.04.6 in a few hours, and then
in the -proposed repository.

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

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

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

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

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

Title:
  [SRU]Not able to adjust Audio input UI volume after connecting headset

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project bionic series:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  Not able to adjust Audio input UI volume if this device doesn't have a
  internal mic, the volume bar will be gray.

  [ Test Case ]

  1. Boot ubuntu without any external headset connected.
  2. Launch gnome-control-center and switch to Sound->Input tab.
  3. Connect external headset, then you will find the input show up but can not 
adjust the volume.

  [ Regression potential ]

  Low.

  Package in this PPA:
  https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages

  

  Summary:Not able to adjust Audio input UI volume, it's gray

  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack

  Expected result:
  System can be recording audio from external mic

  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox

  Failure rate:100%

  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

  Note:20.04, 19.10, 19.04 are immune on the bug

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

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

[Desktop-packages] [Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

The regression potential field does not provide enough information. I
will accept it into -proposed, but could you please include some
regression potential analysis in the description before we start looking
into releasing it to updates? Thank you!

** Changed in: gnome-control-center (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  [SRU]Not able to adjust Audio input UI volume after connecting headset

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project bionic series:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed

Bug description:
  [ Impact ]

  Not able to adjust Audio input UI volume if this device doesn't have a
  internal mic, the volume bar will be gray.

  [ Test Case ]

  1. Boot ubuntu without any external headset connected.
  2. Launch gnome-control-center and switch to Sound->Input tab.
  3. Connect external headset, then you will find the input show up but can not 
adjust the volume.

  [ Regression potential ]

  Low.

  Package in this PPA:
  https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages

  

  Summary:Not able to adjust Audio input UI volume, it's gray

  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack

  Expected result:
  System can be recording audio from external mic

  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox

  Failure rate:100%

  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

  Note:20.04, 19.10, 19.04 are immune on the bug

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

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

[Desktop-packages] [Bug 1813441] Re: Can no longer drag and drop files between desktop and applications

2020-01-13 Thread Efthimios Chaskaris

Applies to 19.10 as well

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

Title:
  Can no longer drag and drop files between desktop and applications

Status in gnome-shell-extension-desktop-icons:
  New
Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Triaged

Bug description:
  In releases before 19.04, you could drag and drop files from the
  desktop into applications.

  This no longer works.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-shell-extension-desktop-icons 19.01-1
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu19
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 26 21:47:14 2019
  InstallationDate: Installed on 2019-01-02 (24 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-desktop-icons
  UpgradeStatus: Upgraded to disco on 2019-01-21 (5 days ago)

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

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

[Desktop-packages] [Bug 1849135] Re: Clicking Activities in the corner doesn't work

2020-01-13 Thread Douglas Silva

Let me add that I also tested a GNOME session (package 'gnome-session')
and there was no difference from the results of testing the Ubuntu Xorg
session. The proposed package does NOT fix the issue for me.

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

Title:
  Clicking Activities in the corner doesn't work

Status in GNOME Shell:
  Fix Released
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Committed

Bug description:
  [ Impact ]

  Starting from Ubuntu 19.10, the top-left corner of the screen is
  unclickable. It's where the Activities button is. It is unresponsive
  to clicks to open the overlay, BUT it responds to clicks to close it.

  The unclickable spot is exactly one pixel large.

  Edit: At first it seemed to be reproducible only on Xorg sessions, but
  after using it for a while on Wayland, I am having the issue again.

  Specs:
  - Graphics: AMD RX 560
  - CPU: Intel Core i3-8100
  - Ubuntu 19.10 Eoan

  [ Test case ]

  - Move the mouse to the top-left corner pixel and click on it
  - Activities should open

  [ Regression potential ]

  Mouse picking location could be wrong in all clutter operations

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

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

[Desktop-packages] [Bug 1849135] Re: Clicking Activities in the corner doesn't work

2020-01-13 Thread Douglas Silva

I have tested 'mutter' version 3.34.3-1ubuntu1~19.10.1 from eoan-
proposed on an Xorg session, and it doesn't fix the issue. Testing was
made after package installation, followed by a system reboot.

mutter/eoan-proposed,now 3.34.3-1ubuntu1~19.10.1 amd64 [installed]

I don't know what other information to get from this.

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

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

Title:
  Clicking Activities in the corner doesn't work

Status in GNOME Shell:
  Fix Released
Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Committed

Bug description:
  [ Impact ]

  Starting from Ubuntu 19.10, the top-left corner of the screen is
  unclickable. It's where the Activities button is. It is unresponsive
  to clicks to open the overlay, BUT it responds to clicks to close it.

  The unclickable spot is exactly one pixel large.

  Edit: At first it seemed to be reproducible only on Xorg sessions, but
  after using it for a while on Wayland, I am having the issue again.

  Specs:
  - Graphics: AMD RX 560
  - CPU: Intel Core i3-8100
  - Ubuntu 19.10 Eoan

  [ Test case ]

  - Move the mouse to the top-left corner pixel and click on it
  - Activities should open

  [ Regression potential ]

  Mouse picking location could be wrong in all clutter operations

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

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

[Desktop-packages] [Bug 402892] Re: Mouse cursor gets stuck in "drag and drop" mode

2020-01-13 Thread mevsme

2020 and it's fucking still exist.

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

Title:
  Mouse cursor gets stuck in "drag and drop" mode

Status in OpenShot Video Editor:
  New
Status in X.Org X server:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in rapidsvn package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: rapidsvn

  When clicking on the Bookmark root or on one of the bookmarks below
  the mouse cursor gets stuck in "drag n drop" mode, blocking all
  keyboard entry and also mouse clicks for the the whole GUI
  (systemwide).

  Unfortunately I cannot provide any debug or other information, as I
  have to reboot everytime.

  I am running Ubuntu 9.04 with compiz enabled.

  Many thanks in advance for your help with this problem,
  /nxT

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

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

[Desktop-packages] [Bug 1857815] Re: cups-browsed assert failure: corrupted double-linked list

2020-01-13 Thread Till Kamppeter

Right before the

memset(deleted_master, 0, sizeof(remote_printer_t));

deleted_master is allocated via

if (deleted_master == NULL &&
(deleted_master =
 (remote_printer_t *)calloc(1, sizeof(remote_printer_t))) == NULL) {
  debug_printf("ERROR: Unable to allocate memory.\n");
  if (in_shutdown == 0)
recheck_timer ();
  return FALSE;
}

and in case on unsuccessful allocation it is exited from the function
before the memset() call.

So at this point I do not see why it is going wrong.

So I still need the log, to see whether deleted_master gets overwritten
/re-assigned somewhere.

** Changed in: cups-filters (Ubuntu)
   Status: New => Incomplete

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

Title:
  cups-browsed assert failure: corrupted double-linked list

Status in cups-filters package in Ubuntu:
  Incomplete

Bug description:
  Same bug on Focal

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.26.0-1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AssertionMessage: corrupted double-linked list
  CupsErrorLog:
   
  Date: Thu Dec 26 08:18:13 2019
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2019-12-12 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191211)
  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 002: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=ada0b905-9f6f-4911-9311-d1930ae73b8a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa8703a73a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7fa8703a54d3 "corrupted double-linked 
list") at malloc.c:5332
   unlink_chunk (p=p@entry=0x55c22905f000, av=0x7fa8703d8b80 ) at 
malloc.c:1460
   _int_malloc (av=av@entry=0x7fa8703d8b80 , bytes=bytes@entry=184) 
at malloc.c:4041
   __libc_calloc (n=, elem_size=) at malloc.c:3428
  Title: cups-browsed assert failure: corrupted double-linked list
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd05/17/2019:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  separator:

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

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

[Desktop-packages] [Bug 1819779] Re: Stick to the 3.30 serie still?

2020-01-13 Thread AsciiWolf

Are there any news about the possible gnome-software version in Focal?
Debian Testing/Unstable currently has gnome-software 3.34.2, however
Ubuntu is still on 3.30.6.

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

Title:
  Stick to the 3.30 serie still?

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  The new serie/version is having stability issues (see bug #1817223 for 
example, which means we got no testing of the refactoring at this point) and we 
don't have the resources to deal with the fallout.
  There are also no change in the NEWS that we consider essential to get this 
cycle (backporting the new icon/appmenu change might be worth doing though)

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

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

[Desktop-packages] [Bug 1848522] Re: Backport packages for 18.04.4 HWE stack

Hey Timo! How is this update looking? Is it looking good for the
upcoming point release? Thanks!

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

Title:
  Backport packages for 18.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-9 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server-hwe-18.04 package in Ubuntu:
  Invalid
Status in libclc source package in Bionic:
  Fix Committed
Status in libdrm source package in Bionic:
  Fix Committed
Status in llvm-toolchain-9 source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in xorg-server-hwe-18.04 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 18.04.4 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  Check upgrade from stock bionic.

  [Regression potential]

  libdrm: very minimal chance for regressions

  llvm-9: a new package, no regression potential on it's own

  libclc: more or less just adds support for new llvm

  mesa: a new major release, but we'll pull the final stable release of
  19.2.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new git snapshot (or maybe a point-release)

  xorg drivers: modest updates, mainly just new ati/amdgpu

  [Other info]

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

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

[Desktop-packages] [Bug 1853574] Re: Syntax error in /usr/bin/chromium-browser when xdg-settings get default-web-browser is empty

Hello Laurent, or anyone else affected,

Accepted chromium-browser into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/chromium-
browser/79.0.3945.79-0ubuntu0.19.10.2 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: chromium-browser (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

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

Title:
  Syntax error in /usr/bin/chromium-browser when xdg-settings get
  default-web-browser is empty

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  Minor. Apparently under certain circumstances "xdg-settings get 
default-web-browser" can return an empty string (although I haven't been able 
to reproduce this myself), and this will make the /usr/bin/chromium-browser 
wrapper script spit out a console error (but it won't prevent it from running 
the browser).
  This is trivial to fix by enclosing the call to "xdg-settings get 
default-web-browser" in double quotes, to cater for the empty result case (see 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1526).

  
  [Test Case]

  1. Install chromium-browser
  2. Patch /usr/bin/xdg-settings to make the get_browser_gnome3() function 
return an empty string (replace its body with 'echo ""')
  3. From a terminal, run "chromium-browser"

  Expected result: no error
  Current result: /usr/bin/chromium-browser: 12: [: =: unexpected operator

  
  [Regression Potential]

  Low, enclosing a call to a command in double quotes in bash shouldn't
  have any undesirable side effect, and that's all that the patch does.

  
  [Original Description]

  Hi,

  here is the error:

  $ chromium-browser
  /usr/bin/chromium-browser: 12: [: =: unexpected operator
  [...]

  Here is line 12 in /usr/bin/chromium-browser:

  if [ $(xdg-settings get default-web-browser) = "chromium-
  browser.desktop" ]; then

  The error occurs because on my system the default-web-browser setting
  is unset:

  $ xdg-settings get default-web-browser
  [nothing]

  I suggest putting double quotes around:

  if [ "$(xdg-settings get default-web-browser)" = "chromium-
  browser.desktop" ]; then

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  Uname: Linux 5.3.12-050312-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.3
  Architecture: amd64
  CurrentDesktop: KDE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAJ5csGAAEaAQSVIhN4CvmglV1ZlCkkUFQBAQEBAQEBAQEBAQEBAQEBGjuAJHE4PEAwIDYAWMIQAAAa/S2ADnE4KEAwIDYAWMIQAAAa/gBSTUpDWYBOVjE1TjQyQSKWABoBCiAgAMg=
   modes: 1920x1080 1920x1080
  Date: Fri Nov 22 10:27:14 2019
  DiskUsage:
   Filesystem  Type   Size  Used Avail Use% Mounted on
   /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
   tmpfs   tmpfs  7.8G  124M  7.7G   2% /dev/shm
   /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse 
(M-BT58)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5590

[Desktop-packages] [Bug 1858500] Re: Upgrading from 19.04 to 19.10 will keep the 19.04 chromium-browser due to a higher version than the transitional deb in 19.10

Hello Sønke, or anyone else affected,

Accepted chromium-browser into eoan-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/chromium-
browser/79.0.3945.79-0ubuntu0.19.10.2 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Changed in: chromium-browser (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

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

Title:
  Upgrading from 19.04 to 19.10 will keep the 19.04 chromium-browser due
  to a higher version than the transitional deb in 19.10

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

  Users upgrading from 19.04 to 19.10 will not get the latest chromium snap 
replacing the chromium-browser deb package as intended.
  This is because the version number in 19.04 is greater than the version in 
19.10. Bumping the version number in 19.10 is enough to fix this.

  [Test Case]

   * On a machine running 19.04, ensure that the chromium snap is *not* 
installed, then install the chromium-browser deb package: sudo apt install 
chromium-browser
   * Upgrade that machine to Ubuntu 19.10
   * When upgrading, the chromium-browser package becomes a transitional 
package that installs the chromium snap
   * Verify that the chromium snap is installed

  [Regression Potential]

   * The chromium snap has some known shortcomings and regressions compared to 
the deb package, they are being tracked at 
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap.
 Auto-upgrading users from the deb to the snap is the desired behaviour though.
   * Version 79.0.3945.79-0ubuntu0.19.10.2 which is being uploaded also 
contains a couple of minor unrelated changes, but those are harmless. They are 
included because they were already pushed to the source package's VCS:
 - 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1525
 - 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1526

  [Original Description]

  19.04 has got a higher version chromium-browser now than the
  transitional deb package that install the snap version, so the 19.04
  version will be kept when someone upgrades since 19.04 got a higher
  version, and then no further updates.

  apt show chromium-browser -a
  Package: chromium-browser
  Version: 79.0.3945.79-0ubuntu0.19.04.3
  Status: install ok installed
  Priority: optional
  Section: web
  Maintainer: Ubuntu Developers 
  Installed-Size: 225 MB
  Provides: chromium-browser-inspector, www-browser
  Pre-Depends: dpkg (>= 1.15.6)
  Depends: libasound2 (>= 1.0.16), libatk-bridge2.0-0 (>= 2.5.3), libatk1.0-0 
(>= 2.2.0), libatspi2.0-0 (>= 2.9.90), libc6 (>= 2.29), libcairo2 (>= 1.6.0), 
libcups2 (>= 1.4.0), libdbus-1-3 (>= 1.9.14), libexpat1 (>= 2.0.1), libgcc1 (>= 
1:4.0), libgdk-pixbuf2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.31.8), libgtk-3-0 
(>= 3.9.10), libnspr4 (>= 2:4.9-2~), libnss3 (>= 2:3.22), libpango-1.0-0 (>= 
1.14.0), libpangocairo-1.0-0 (>= 1.14.0), libstdc++6 (>= 7), libx11-6 (>= 
2:1.4.99.1), libx11-xcb1, libxcb1 (>= 1.6), libxcomposite1 (>= 1:0.3-1), 
libxcursor1 (>> 1.1.2), libxdamage1 (>= 1:1.1), libxext6, libxfixes3 (>= 
1:5.0), libxi6 (>= 2:1.2.99.4), libxrandr2 (>= 2:1.2.99.3), libxrender1, 
libxss1, libxtst6, bash (>= 4), xdg-utils, chromium-codecs-ffmpeg-extra (= 
79.0.3945.79-0ubuntu0.19.04.3) | chromium-codecs-ffmpeg (= 
79.0.3945.79-0ubuntu0.19.04.3)
  Recommends: chromium-browser-l10n
  Suggests: webaccounts-chromium-extension, unity-chromium-extension, 
adobe-flashplugin
  Conflicts: chromium-browser-inspector
  Replaces: chromium-browser-inspector
  Homepage: https://chromium.googlesource.com/chromium/src/
  Download-Size: unknown

[Desktop-packages] [Bug 1859436] [NEW] Rhythmbox doesn't respond to media keys

2020-01-13 Thread GUI_Junkie

Public bug reported:

This is similar to previously reported bugs (for instance Feisty from
2010). Ever since I updated to Ubuntu 19.10, I have intermittent
problems with the media keys.

I have, once, solved this changing keyboard settings, but after
restarting Ubuntu, the problem returned.

Once, the problem disappeared spontaneously... but after restarting
Ubuntu, the problem returned.

Pushing next song key
Expected behavior: plays next song.
Actual behavior: nothing happens.

Similar for pause/play button and previous song key.

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

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

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

Title:
  Rhythmbox doesn't respond to media keys

Status in rhythmbox package in Ubuntu:
  New

Bug description:
  This is similar to previously reported bugs (for instance Feisty from
  2010). Ever since I updated to Ubuntu 19.10, I have intermittent
  problems with the media keys.

  I have, once, solved this changing keyboard settings, but after
  restarting Ubuntu, the problem returned.

  Once, the problem disappeared spontaneously... but after restarting
  Ubuntu, the problem returned.

  Pushing next song key
  Expected behavior: plays next song.
  Actual behavior: nothing happens.

  Similar for pause/play button and previous song key.

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

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

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

[Desktop-packages] [Bug 1857037] Re: Update to 3.34.2 and SRU it

This bug was fixed in the package yaru-theme - 19.10.5

---
yaru-theme (19.10.5) eoan; urgency=medium

  * gnome-shell: Sync with 3.34.2 changes (LP: #1857037)
  * debian/gbp.conf: Target ubuntu/eoan branch

 -- Marco Trevisan (Treviño)   Wed, 08 Jan 2020
13:54:22 +

** Changed in: yaru-theme (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Update to 3.34.2 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in gnome-shell source package in Eoan:
  Fix Committed
Status in mutter source package in Eoan:
  Fix Committed
Status in yaru-theme source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  The second stable release in the 3.34 series. There are some upstream
  theme changes which need to be mirrored and handled in yaru-theme too.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups. Check the default theme works properly. In particular
  concentrate on the drop down that appears when you click the clock in
  the top bar.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Most of commits were already included in stable ubuntu release, as per git 
snapshot.
  However we've still various fixes in handling windows workspaces and focus, 
so ensure that there are no focus issues, especially with Java apps.

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

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

[Desktop-packages] [Bug 1859431] [NEW] dist-upgrading to focal removed ubuntu-wallpapers-bionic

Public bug reported:

Yesterday I dist-upgraded my work laptop from eoan to focal. During the
upgrade process package ubuntu-wallpapers-bionic was marked for
automatic removal and removed, and when that happened my desktop
wallpaper turned plain black.

$ gsettings get org.gnome.desktop.background picture-uri
'file:///usr/share/backgrounds/Crocus_Wallpaper_by_Roy_Tanck.jpg'

(that file was installed by ubuntu-wallpapers-bionic).

Not sure why that package wasn't uninstalled in prior dist-upgrades like
bionic->cosmic, cosmic->disco or disco->eoan (on this machine I've been
dist-upgrading for every single release since 16.04).

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-wallpapers 19.10.3-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jan 13 12:02:15 2020
Dependencies: ubuntu-wallpapers-eoan 19.10.3-0ubuntu2
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-07-02 (1289 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: ubuntu-wallpapers
UpgradeStatus: Upgraded to focal on 2020-01-12 (0 days ago)

** Affects: ubuntu-wallpapers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  dist-upgrading to focal removed ubuntu-wallpapers-bionic

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  Yesterday I dist-upgraded my work laptop from eoan to focal. During
  the upgrade process package ubuntu-wallpapers-bionic was marked for
  automatic removal and removed, and when that happened my desktop
  wallpaper turned plain black.

  $ gsettings get org.gnome.desktop.background picture-uri
  'file:///usr/share/backgrounds/Crocus_Wallpaper_by_Roy_Tanck.jpg'

  (that file was installed by ubuntu-wallpapers-bionic).

  Not sure why that package wasn't uninstalled in prior dist-upgrades
  like bionic->cosmic, cosmic->disco or disco->eoan (on this machine
  I've been dist-upgrading for every single release since 16.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-wallpapers 19.10.3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 12:02:15 2020
  Dependencies: ubuntu-wallpapers-eoan 19.10.3-0ubuntu2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1289 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: Upgraded to focal on 2020-01-12 (0 days ago)

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

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

[Desktop-packages] [Bug 1853657] Re: librsvg 2.44.15 FTBFS in focal

** Changed in: librsvg (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  librsvg 2.44.15 FTBFS in focal

Status in librsvg package in Ubuntu:
  Fix Released

Bug description:
  focal currently has rustc 1.38 (1.38.0+dfsg0.2+llvm-0ubuntu1), and
  librsvg 2.44.15 fails to build from source with this version. It built
  fine with rustc 1.37 (although there was a unit test failure on
  ppc64el, which prevented it from leaving focal-proposed, see
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942022).

  The upstream commit that addresses this is 
https://gitlab.gnome.org/GNOME/librsvg/commit/de26c4d8.
  I backported it and added another patch to update the vendored crates in the 
source tarball accordingly, and the build succeeds again, but unit tests 
consistently fail, on all architectures.

  The upstream commit message says « Although you should rather be using
  the 2.46 branch of librsvg as 2.44 is EOL », so we should probably
  update librsvg in debian to 2.46 indeed.

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

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

[Desktop-packages] [Bug 1859431] Re: dist-upgrading to focal removed ubuntu-wallpapers-bionic

Re-installing ubuntu-wallpapers-bionic restored my wallpaper.

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

Title:
  dist-upgrading to focal removed ubuntu-wallpapers-bionic

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  Yesterday I dist-upgraded my work laptop from eoan to focal. During
  the upgrade process package ubuntu-wallpapers-bionic was marked for
  automatic removal and removed, and when that happened my desktop
  wallpaper turned plain black.

  $ gsettings get org.gnome.desktop.background picture-uri
  'file:///usr/share/backgrounds/Crocus_Wallpaper_by_Roy_Tanck.jpg'

  (that file was installed by ubuntu-wallpapers-bionic).

  Not sure why that package wasn't uninstalled in prior dist-upgrades
  like bionic->cosmic, cosmic->disco or disco->eoan (on this machine
  I've been dist-upgrading for every single release since 16.04).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-wallpapers 19.10.3-0ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 12:02:15 2020
  Dependencies: ubuntu-wallpapers-eoan 19.10.3-0ubuntu2
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (1289 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-wallpapers
  UpgradeStatus: Upgraded to focal on 2020-01-12 (0 days ago)

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

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

2020-01-13 Thread Robert

i take off earphones from the socket, my acoustics sounds correct(switch signal 
from earphones to acoustics)
but when i take on my earphones to socket, acoustics sounds , but earphones 
don't.

settings->sound, it chooses proper device(earphones), but it doesn't
work proper(not switch signal from acoustics to earphones)

it is my old bug description
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

-- 
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:
  Fix Released
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]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  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

2020-01-13 Thread Robert

not proper link
wrote(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884)

-- 
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:
  Fix Released
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]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  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 1828192] Re: Please stop build-depending on libgnome-keyring

** Branch linked: lp:~chromium-team/chromium-browser/disco-stable

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

Title:
  Please stop build-depending on libgnome-keyring

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Xenial:
  In Progress
Status in chromium-browser source package in Bionic:
  In Progress
Status in chromium-browser source package in Disco:
  In Progress

Bug description:
  libgnome-keyring is not maintained anymore, but chromium build-depends
  on it. It should be using libsecret instead. The generated binaries
  depend on neither library, which is a bit confusing.

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

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

[Desktop-packages] [Bug 1828192] Re: Please stop build-depending on libgnome-keyring

https://bazaar.launchpad.net/~chromium-team/chromium-browser/xenial-
stable/revision/1440

https://bazaar.launchpad.net/~chromium-team/chromium-browser/bionic-
stable/revision/1512

https://bazaar.launchpad.net/~chromium-team/chromium-browser/disco-
stable/revision/1544

** Changed in: chromium-browser (Ubuntu Disco)
   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/1828192

Title:
  Please stop build-depending on libgnome-keyring

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Xenial:
  In Progress
Status in chromium-browser source package in Bionic:
  In Progress
Status in chromium-browser source package in Disco:
  In Progress

Bug description:
  libgnome-keyring is not maintained anymore, but chromium build-depends
  on it. It should be using libsecret instead. The generated binaries
  depend on neither library, which is a bit confusing.

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

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

[Desktop-packages] [Bug 1828192] Re: Please stop build-depending on libgnome-keyring

** Branch linked: lp:~chromium-team/chromium-browser/xenial-stable

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

Title:
  Please stop build-depending on libgnome-keyring

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Xenial:
  In Progress
Status in chromium-browser source package in Bionic:
  In Progress
Status in chromium-browser source package in Disco:
  In Progress

Bug description:
  libgnome-keyring is not maintained anymore, but chromium build-depends
  on it. It should be using libsecret instead. The generated binaries
  depend on neither library, which is a bit confusing.

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

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

[Desktop-packages] [Bug 1828192] Re: Please stop build-depending on libgnome-keyring

** Changed in: chromium-browser (Ubuntu Xenial)
   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/1828192

Title:
  Please stop build-depending on libgnome-keyring

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Xenial:
  In Progress
Status in chromium-browser source package in Bionic:
  In Progress
Status in chromium-browser source package in Disco:
  In Progress

Bug description:
  libgnome-keyring is not maintained anymore, but chromium build-depends
  on it. It should be using libsecret instead. The generated binaries
  depend on neither library, which is a bit confusing.

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

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

[Desktop-packages] [Bug 1828192] Re: Please stop build-depending on libgnome-keyring

** Branch linked: lp:~chromium-team/chromium-browser/bionic-stable

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

Title:
  Please stop build-depending on libgnome-keyring

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Xenial:
  In Progress
Status in chromium-browser source package in Bionic:
  In Progress
Status in chromium-browser source package in Disco:
  In Progress

Bug description:
  libgnome-keyring is not maintained anymore, but chromium build-depends
  on it. It should be using libsecret instead. The generated binaries
  depend on neither library, which is a bit confusing.

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

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

[Desktop-packages] [Bug 1828192] Re: Please stop build-depending on libgnome-keyring

** Changed in: chromium-browser (Ubuntu Bionic)
   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/1828192

Title:
  Please stop build-depending on libgnome-keyring

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Xenial:
  In Progress
Status in chromium-browser source package in Bionic:
  In Progress
Status in chromium-browser source package in Disco:
  In Progress

Bug description:
  libgnome-keyring is not maintained anymore, but chromium build-depends
  on it. It should be using libsecret instead. The generated binaries
  depend on neither library, which is a bit confusing.

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

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

[Desktop-packages] [Bug 1845281] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [as

2020-01-13 Thread Edd Grant

Thanks! Have installed the package from eoan-proposed:

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version Architecture Description
+++-==-===--===
ii  mutter 3.34.3-1ubuntu1~19.10.1 amd64Example window manager 
using GNOME's window manager library
ii  mutter-common  3.34.3-1ubuntu1~19.10.1 all  shared files for the 
Mutter window manager

Will do some testing and report back.

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  meta_window_get_workspaces() [assertion failure "code should not be
  reached"]

Status in Mutter:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Won't Fix
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  Intellij and other java apps can cause GNOME shell to crash

  [ Test case ]

  1) Run this test case:
 https://gitlab.gnome.org/3v1n0/mutter/snippets/956
  2) Windows should appear and close correctly while
 Gnome shell must not crash

  [ Regression potential ]

  Parent-child relationship on some windows might be broken.

  ---

  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.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 
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/mutter/+bug/1845281/+subscriptions

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

[Desktop-packages] [Bug 1853574] Re: Syntax error in /usr/bin/chromium-browser when xdg-settings get default-web-browser is empty

** Description changed:

+ [Impact]
+ 
+ Minor. Apparently under certain circumstances "xdg-settings get 
default-web-browser" can return an empty string (although I haven't been able 
to reproduce this myself), and this will make the /usr/bin/chromium-browser 
wrapper script spit out a console error (but it won't prevent it from running 
the browser).
+ This is trivial to fix by enclosing the call to "xdg-settings get 
default-web-browser" in double quotes, to cater for the empty result case (see 
https://bazaar.launchpad.net/~chromium-team/chromium-browser/eoan-stable/revision/1526).
+ 
+ 
+ [Test Case]
+ 
+ 1. Install chromium-browser
+ 2. Patch /usr/bin/xdg-settings to make the get_browser_gnome3() function 
return an empty string (replace its body with 'echo ""')
+ 3. From a terminal, run "chromium-browser"
+ 
+ Expected result: no error
+ Current result: /usr/bin/chromium-browser: 12: [: =: unexpected operator
+ 
+ 
+ [Regression Potential]
+ 
+ Low, enclosing a call to a command in double quotes in bash shouldn't
+ have any undesirable side effect, and that's all that the patch does.
+ 
+ 
+ [Original Description]
+ 
  Hi,
  
  here is the error:
  
- $ chromium-browser 
+ $ chromium-browser
  /usr/bin/chromium-browser: 12: [: =: unexpected operator
  [...]
  
  Here is line 12 in /usr/bin/chromium-browser:
  
  if [ $(xdg-settings get default-web-browser) = "chromium-
  browser.desktop" ]; then
  
  The error occurs because on my system the default-web-browser setting is
  unset:
  
  $ xdg-settings get default-web-browser
  [nothing]
  
  I suggest putting double quotes around:
  
  if [ "$(xdg-settings get default-web-browser)" = "chromium-
  browser.desktop" ]; then
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  Uname: Linux 5.3.12-050312-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.3
  Architecture: amd64
  CurrentDesktop: KDE
  DRM.card0-DP-1:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  DRM.card0-HDMI-A-1:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  DRM.card0-HDMI-A-2:
-  enabled: disabled
-  dpms: Off
-  status: disconnected
-  edid-base64: 
-  modes:
+  enabled: disabled
+  dpms: Off
+  status: disconnected
+  edid-base64:
+  modes:
  DRM.card0-eDP-1:
-  enabled: enabled
-  dpms: On
-  status: connected
-  edid-base64: 
AP///wAJ5csGAAEaAQSVIhN4CvmglV1ZlCkkUFQBAQEBAQEBAQEBAQEBAQEBGjuAJHE4PEAwIDYAWMIQAAAa/S2ADnE4KEAwIDYAWMIQAAAa/gBSTUpDWYBOVjE1TjQyQSKWABoBCiAgAMg=
-  modes: 1920x1080 1920x1080
+  enabled: enabled
+  dpms: On
+  status: connected
+  edid-base64: 
AP///wAJ5csGAAEaAQSVIhN4CvmglV1ZlCkkUFQBAQEBAQEBAQEBAQEBAQEBGjuAJHE4PEAwIDYAWMIQAAAa/S2ADnE4KEAwIDYAWMIQAAAa/gBSTUpDWYBOVjE1TjQyQSKWABoBCiAgAMg=
+  modes: 1920x1080 1920x1080
  Date: Fri Nov 22 10:27:14 2019
  DiskUsage:
-  Filesystem  Type   Size  Used Avail Use% Mounted on
-  /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
-  tmpfs   tmpfs  7.8G  124M  7.7G   2% /dev/shm
-  /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
+  Filesystem  Type   Size  Used Avail Use% Mounted on
+  /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
+  tmpfs   tmpfs  7.8G  124M  7.7G   2% /dev/shm
+  /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
  Lsusb:
-  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
-  Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
-  Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse 
(M-BT58)
-  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
+  Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse 
(M-BT58)
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.12-050312-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
intel_iommu=on quiet splash vt.handoff=7
  Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.108 
(4b26898a39ee037623a72fcfb77279fce0e7d648-refs/branch-heads/3904@{#889})
  Snap.ChromiumVersion:
-  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
-  Chromium 78.0.3904.108 snap
+  /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
+  Chromium 78.0.3904.108 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log

[Desktop-packages] [Bug 1853574] Re: Syntax error in /usr/bin/chromium-browser when xdg-settings get default-web-browser is empty

@Łukasz, sorry, I meant to update this bug to make it SRU-ready, but I
somehow forgot to. SRU-wise the real important bug that the upload in
the eoan queue fixes is bug #1858500, but as the fix for this one was
already committed to the bzr branch, is minor and can't hurt, I don't
see a reason to exclude it. I'll SRUify that bug right away.

** Changed in: chromium-browser (Ubuntu Eoan)
   Status: Won't Fix => 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/1853574

Title:
  Syntax error in /usr/bin/chromium-browser when xdg-settings get
  default-web-browser is empty

Status in chromium-browser package in Ubuntu:
  Fix Released
Status in chromium-browser source package in Eoan:
  In Progress

Bug description:
  Hi,

  here is the error:

  $ chromium-browser 
  /usr/bin/chromium-browser: 12: [: =: unexpected operator
  [...]

  Here is line 12 in /usr/bin/chromium-browser:

  if [ $(xdg-settings get default-web-browser) = "chromium-
  browser.desktop" ]; then

  The error occurs because on my system the default-web-browser setting
  is unset:

  $ xdg-settings get default-web-browser
  [nothing]

  I suggest putting double quotes around:

  if [ "$(xdg-settings get default-web-browser)" = "chromium-
  browser.desktop" ]; then

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  Uname: Linux 5.3.12-050312-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.3
  Architecture: amd64
  CurrentDesktop: KDE
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64: 
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAJ5csGAAEaAQSVIhN4CvmglV1ZlCkkUFQBAQEBAQEBAQEBAQEBAQEBGjuAJHE4PEAwIDYAWMIQAAAa/S2ADnE4KEAwIDYAWMIQAAAa/gBSTUpDWYBOVjE1TjQyQSKWABoBCiAgAMg=
   modes: 1920x1080 1920x1080
  Date: Fri Nov 22 10:27:14 2019
  DiskUsage:
   Filesystem  Type   Size  Used Avail Use% Mounted on
   /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
   tmpfs   tmpfs  7.8G  124M  7.7G   2% /dev/shm
   /dev/mapper/MonVolume2-UbuntuRacine ext4   492G  235G  232G  51% /
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:58f6 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 002: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse 
(M-BT58)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5590
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.12-050312-generic 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
intel_iommu=on quiet splash vt.handoff=7
  Snap.ChromeDriverVersion: ChromeDriver 78.0.3904.108 
(4b26898a39ee037623a72fcfb77279fce0e7d648-refs/branch-heads/3904@{#889})
  Snap.ChromiumVersion:
   /bin/bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
   Chromium 78.0.3904.108 snap
  SourcePackage: chromium-browser
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.1
  dmi.board.name: 0VYDFF
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.1:bd07/19/2019:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0VYDFF:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5590
  dmi.product.sku: 0817
  dmi.sys.vendor: Dell Inc.

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

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

[Desktop-packages] [Bug 1859409] Re: Lighning fails to modify events and to store login credentials for Google calendars after update

>From the bug data, you're using Ubuntu 18.10, for which support was 
>discontinued in July 2019.
I strongly suggest to upgrade to 19.10 to get an up-to-date and supported set 
of software (19.04 is still supported but will soon cease to be, too).

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

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

Title:
  Lighning fails to modify events and to store login credentials for
  Google calendars after update

Status in thunderbird package in Ubuntu:
  Invalid

Bug description:
  Google calendar became inaccessible after a recent update. The boxes
  of the respective calendars are discoloured and displayed in grey. I
  installed the google provider add-on to facilitate the log in. With
  the plugin, the calendars are shown, but editing events and password
  storage is still not working. Every time, an event is created or
  modified, a login window pops up. When I supply my credentials, the
  login seems to succeed, but the changes are not transmitted to the
  server. Lightning also does not remember the credentials between
  sessions. Upon starting thunderbird the next time, the password input
  window pops up again. Beside the problems, I think that it is a
  nuisance that users have to explicitly install lightning and then
  manually download the Google provider add-on to access their Google
  calendars, this is a basic functionality that should be included in
  the standard thunderbird or at least lightning package.

  thunderbird   
1:60.8.0+build1-0ubuntu0.18.10.1
  xul-ext-lightning 
1:60.8.0+build1-0ubuntu0.18.10.1
  Provider for Google Calendar  4.4.2

  Versions 4.4.1 and 4.4 are also not working, in these versions, no
  login window pops up at all, and clicking on "Save and Close" has no
  effect. The "New Event" window stays open, until thunderbird is killed
  from the console.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: thunderbird 1:60.8.0+build1-0ubuntu0.18.10.1
  ProcVersionSignature: Ubuntu 4.18.0-25.26-generic 4.18.20
  Uname: Linux 4.18.0-25-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.10-0ubuntu13.4
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  pia4406 F pulseaudio
  BuildID: 20190705212218
  Channel: Unavailable
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jan 13 15:50:18 2020
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2015-11-05 (1529 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  IpRoute:
   default via 10.25.0.1 dev wlp3s0 proto dhcp src 10.25.131.222 metric 303 
   10.25.0.0/16 dev wlp3s0 proto dhcp scope link src 10.25.131.222 metric 303 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  Locales: extensions.sqlite corrupt or missing
  MostRecentCrashID: bp-6e5eb5a6-5e65-4ff2-9c9d-226c60191029
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefErrors: 'utf-8' codec can't decode byte 0xe4 in position 1174: invalid 
continuation byte
  Profiles: Profile0 (Default) - LastVersion=60.8.0/20190705212218 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: thunderbird
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (451 days ago)
  dmi.bios.date: 09/26/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6MET92WW (1.52 )
  dmi.board.name: 4384WRP
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6MET92WW(1.52):bd09/26/2012:svnLENOVO:pn4384WRP:pvrThinkPadT510:rvnLENOVO:rn4384WRP:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T510
  dmi.product.name: 4384WRP
  dmi.product.version: ThinkPad T510
  dmi.sys.vendor: LENOVO
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2019-03-07T21:28:39.455024

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

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

[Desktop-packages] [Bug 1857815] Re: cups-browsed assert failure: corrupted double-linked list

@Till, the error pointed out by valgrind happend when I manually start
cups-browsed at any time during the session, it's not a shutdown problem

==5706== Invalid write of size 8
==5706== at 0x124791: UnknownInlinedFun (string_fortified.h:71)
==5706== by 0x124791: update_cups_queues (cups-browsed.c:7381)

The error basically means that in cups-browsed.c at line 7381 it tries
to incorrect use a variable

the corresponding line in the code is
  memset(deleted_master, 0, sizeof(remote_printer_t));

but it's defined as 
static remote_printer_t *deleted_master = NULL;

but you don't seem to allocate an actual array there where you should?


Let me know if you still need the log but I think the code there is just wrong?


** Changed in: cups-filters (Ubuntu)
   Status: Incomplete => New

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

Title:
  cups-browsed assert failure: corrupted double-linked list

Status in cups-filters package in Ubuntu:
  New

Bug description:
  Same bug on Focal

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: cups-browsed 1.26.0-1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  AssertionMessage: corrupted double-linked list
  CupsErrorLog:
   
  Date: Thu Dec 26 08:18:13 2019
  ExecutablePath: /usr/sbin/cups-browsed
  InstallationDate: Installed on 2019-12-12 (17 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191211)
  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 002: ID 0cf3:e007 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 1bcf:2c01 Sunplus Innovation Technology Inc. 
Integrated Webcam
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 15 7000 Gaming
  Papersize: a4
  ProcAttrCurrent: /usr/sbin/cups-browsed (enforce)
  ProcCmdline: /usr/sbin/cups-browsed
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-9-generic 
root=UUID=ada0b905-9f6f-4911-9311-d1930ae73b8a ro quiet splash vt.handoff=7
  Signal: 6
  SourcePackage: cups-filters
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fa8703a73a5 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7fa8703a54d3 "corrupted double-linked 
list") at malloc.c:5332
   unlink_chunk (p=p@entry=0x55c22905f000, av=0x7fa8703d8b80 ) at 
malloc.c:1460
   _int_malloc (av=av@entry=0x7fa8703d8b80 , bytes=bytes@entry=184) 
at malloc.c:4041
   __libc_calloc (n=, elem_size=) at malloc.c:3428
  Title: cups-browsed assert failure: corrupted double-linked list
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 05/17/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.10.0
  dmi.board.name: 0P84C9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.10.0:bd05/17/2019:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn0P84C9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15 7000 Gaming
  dmi.product.sku: 0798
  dmi.sys.vendor: Dell Inc.
  separator:

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

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

[Desktop-packages] [Bug 1857037] Re: Update to 3.34.2 and SRU it

Hello Marco, or anyone else affected,

Accepted yaru-theme into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/yaru-theme/19.10.5
in a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: yaru-theme (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  Update to 3.34.2 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Eoan:
  Fix Committed
Status in mutter source package in Eoan:
  Fix Committed
Status in yaru-theme source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  The second stable release in the 3.34 series. There are some upstream
  theme changes which need to be mirrored and handled in yaru-theme too.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups. Check the default theme works properly. In particular
  concentrate on the drop down that appears when you click the clock in
  the top bar.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Most of commits were already included in stable ubuntu release, as per git 
snapshot.
  However we've still various fixes in handling windows workspaces and focus, 
so ensure that there are no focus issues, especially with Java apps.

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

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

[Desktop-packages] [Bug 1859411] [NEW] package fonts-noto-core 20200103-1 failed to install/upgrade: tentative de remplacement de « /usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf », qui appa

2020-01-13 Thread Joseph Maillardet

Public bug reported:

Error reported after upgrading my test machine

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: fonts-noto-core 20200103-1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu15
Architecture: amd64
Date: Fri Jan 10 09:30:56 2020
Dependencies:
 
ErrorMessage: tentative de remplacement de « 
/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf », qui appartient 
aussi au paquet fonts-noto-unhinted 20181227-1
PackageArchitecture: all
Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.5
SourcePackage: fonts-noto
Title: package fonts-noto-core 20200103-1 failed to install/upgrade: tentative 
de remplacement de « /usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf 
», qui appartient aussi au paquet fonts-noto-unhinted 20181227-1
UpgradeStatus: Upgraded to focal on 2018-11-14 (424 days ago)

** Affects: fonts-noto (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal

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

Title:
  package fonts-noto-core 20200103-1 failed to install/upgrade:
  tentative de remplacement de « /usr/share/fonts/truetype/noto
  /NotoSansJavanese-Bold.ttf », qui appartient aussi au paquet fonts-
  noto-unhinted 20181227-1

Status in fonts-noto package in Ubuntu:
  New

Bug description:
  Error reported after upgrading my test machine

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: fonts-noto-core 20200103-1
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 10 09:30:56 2020
  Dependencies:
   
  ErrorMessage: tentative de remplacement de « 
/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf », qui appartient 
aussi au paquet fonts-noto-unhinted 20181227-1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.6, python3-minimal, 
3.7.5-1ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17, python-minimal, 2.7.17-1
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu2
   apt  1.9.5
  SourcePackage: fonts-noto
  Title: package fonts-noto-core 20200103-1 failed to install/upgrade: 
tentative de remplacement de « 
/usr/share/fonts/truetype/noto/NotoSansJavanese-Bold.ttf », qui appartient 
aussi au paquet fonts-noto-unhinted 20181227-1
  UpgradeStatus: Upgraded to focal on 2018-11-14 (424 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1859411/+subscriptions

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

[Desktop-packages] [Bug 1857037] Re: Update to 3.34.2 and SRU it

Hello Marco, or anyone else affected,

Accepted mutter into eoan-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.34.3-1ubuntu1~19.10.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

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

** Changed in: gnome-shell (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  Update to 3.34.2 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Eoan:
  Fix Committed
Status in mutter source package in Eoan:
  Fix Committed
Status in yaru-theme source package in Eoan:
  In Progress

Bug description:
  [ Description ]

  The second stable release in the 3.34 series. There are some upstream
  theme changes which need to be mirrored and handled in yaru-theme too.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups. Check the default theme works properly. In particular
  concentrate on the drop down that appears when you click the clock in
  the top bar.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Most of commits were already included in stable ubuntu release, as per git 
snapshot.
  However we've still various fixes in handling windows workspaces and focus, 
so ensure that there are no focus issues, especially with Java apps.

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

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

[Desktop-packages] [Bug 1853584] Re: [SRU]Not able to adjust Audio input UI volume after connecting headset

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

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

** Changed in: oem-priority
   Status: New => Triaged

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

** Changed in: oem-priority/bionic
   Importance: Undecided => Critical

** Changed in: oem-priority/bionic
   Status: New => Triaged

** Changed in: oem-priority/bionic
 Assignee: (unassigned) => hugh chao (hugh712)

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

Title:
  [SRU]Not able to adjust Audio input UI volume after connecting headset

Status in gnome-control-center:
  New
Status in OEM Priority Project:
  Triaged
Status in OEM Priority Project bionic series:
  Triaged
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

  Not able to adjust Audio input UI volume if this device doesn't have a
  internal mic, the volume bar will be gray.

  [ Test Case ]

  1. Boot ubuntu without any external headset connected.
  2. Launch gnome-control-center and switch to Sound->Input tab.
  3. Connect external headset, then you will find the input show up but can not 
adjust the volume.

  [ Regression potential ]

  Low.

  Package in this PPA:
  https://launchpad.net/~hugh712/+archive/ubuntu/mysru/+packages

  

  Summary:Not able to adjust Audio input UI volume, it's gray

  Steps to reproduce:
  1. Plug 3 ring earphone with mic to appropriate jack

  Expected result:
  System can be recording audio from external mic

  Actual result:
  Not able to adjust Audio input UI volume, it's gray, and no volume detected 
in UI, but I can recording the input audio by checkbox

  Failure rate:100%

  Note.
  1. There is no internal mic, just a mic jack on the machine, this issue will 
happen
  2. gnome-control-center version : 1:3.28.2-0ubuntu0.18.04.2

  Note:20.04, 19.10, 19.04 are immune on the bug

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

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

Hello Didier, or anyone else affected,

Accepted gnome-shell into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.34.3-1ubuntu1~19.10.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: gnome-shell (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

-- 
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:
  Fix Released
Status in gnome-shell source package in Eoan:
  Fix Committed
Status in gnome-shell source package in Focal:
  Fix Released

Bug description:
  [ Impact ]

  Applications under X11 are closed if the shell is killed (crashed).

  [ Test case ]

  - Open some non dbus activated apps (so, not terminal for instance) like 
firefox
  - Kill the shell with SIGKILL (killall -SIGKILL gnome-shell)
  - The shell restarts and the ran applications are still running.

  [ Regression Potential ]

  GNOME shell not properly killed when the session is stopped

  ---

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

  ProblemType: BugDistroRelease: 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-1ubuntu1SourcePackage: 
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 1857037] Please test proposed package

Hello Marco, or anyone else affected,

Accepted gnome-shell into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.34.3-1ubuntu1~19.10.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  Update to 3.34.2 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Confirmed
Status in gnome-shell source package in Eoan:
  Fix Committed
Status in mutter source package in Eoan:
  Fix Committed
Status in yaru-theme source package in Eoan:
  In Progress

Bug description:
  [ Description ]

  The second stable release in the 3.34 series. There are some upstream
  theme changes which need to be mirrored and handled in yaru-theme too.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups. Check the default theme works properly. In particular
  concentrate on the drop down that appears when you click the clock in
  the top bar.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Most of commits were already included in stable ubuntu release, as per git 
snapshot.
  However we've still various fixes in handling windows workspaces and focus, 
so ensure that there are no focus issues, especially with Java apps.

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

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

[Desktop-packages] [Bug 1858683] Please test proposed package

Hello Marco, or anyone else affected,

Accepted gnome-shell into eoan-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.34.3-1ubuntu1~19.10.1 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  Update to 3.34.3 and SRU it

Status in gnome-shell package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  New
Status in gnome-shell source package in Eoan:
  Fix Committed
Status in mutter source package in Eoan:
  Fix Committed

Bug description:
  [ Description ]

  The third stable release in the 3.34 series.

  [ QA ]

  Run Ubuntu session, expect the shell to work normally with various
  setups

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  Most of commits were already included in stable ubuntu release, as per git 
snapshot.
  However we've still various fixes in handling windows workspaces and focus, 
so ensure that there are no focus issues, especially with Java apps.

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

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

[Desktop-packages] [Bug 1858683] Re: Update to 3.34.3 and SRU it