date:20200922

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

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

Title:
  screen locking no longer works

Status in gdm3 package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New

Bug description:
  in the last week, the gnome screen locking functionality stopped
  working. I'm under the impression this is handled by gdm3, but if not,
  please point me at the correct package.

  in any case, now there's no lock icon in the power menu in the top
  right, win-L does nothing, and trying to invoke manually with the
  gnome-screensaver package times out after about a minute with the
  following error:

  $ gnome-screensaver-command -l

  ** (gnome-screensaver-command:212161): WARNING **: 18:46:25.014: unable to 
send message: Timeout was reached
  ** Message: 18:46:25.014: Did not receive a reply from the screensaver.

  
  as well, if I suspend the system, on resume it dumps right back to the 
desktop without a prompt to re-authenticate, so this is a security issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gdm3 3.34.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-47.51-lowlatency 5.4.55
  Uname: Linux 5.4.0-47-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 18:47:40 2020
  InstallationDate: Installed on 2020-07-15 (67 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1887425] Re: php files now open by default in Chrome

2020-09-22 Thread Adolfo Jayme

** Package changed: meta-gnome3 (Ubuntu) => shared-mime-info (Ubuntu)

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

Title:
  php files now open by default in Chrome

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Until at least 16.04, php files used to open by default in Gedit.

  I'm talking about when you double click on them in Nautilus (or the
  first "open with " options that shows up in the right-
  click menu)

  After I upgraded to 20.04 (not sure in which version the change was),
  now they open by default in Google Chrome. (I guess they open in the
  default browser which in my case is Chrome).

  This is a stupid default. Do I need to explain to you that php files
  are executed on the server? Opening them in a browser makes no sense
  in 99.99% of cases. When one opens a php file locally, the most
  likely scenario is that you are opening it in order to edit it.

  So if you had switched from gedit to some other text editor I could
  understand it, but opening it in the browser by default is an idiotic
  default for php files.

  I upgraded because I was sick of running age-old versions of almost
  every program, most no longer supported and full of bugs that were
  fixed years ago upstream, but I'm astonished at the amount of
  regressions and, worse, idiotic design decisions that have either been
  taken either with the specific purpose of making things worse, or were
  taken by idiots that didn't put the slightest amount of thought in it.

  Fucking unbelievable. Every major release of Ubuntu is a step backwards.
  Mostly because of Gnome.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
  Uname: Linux 5.4.0-40-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 13 21:10:37 2020
  InstallationDate: Installed on 2013-10-11 (2467 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to focal on 2020-07-12 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1887425/+subscriptions

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

[Desktop-packages] [Bug 1887425] [NEW] php files now open by default in Chrome

You have been subscribed to a public bug:

Until at least 16.04, php files used to open by default in Gedit.

I'm talking about when you double click on them in Nautilus (or the
first "open with " options that shows up in the right-click
menu)

After I upgraded to 20.04 (not sure in which version the change was),
now they open by default in Google Chrome. (I guess they open in the
default browser which in my case is Chrome).

This is a stupid default. Do I need to explain to you that php files are
executed on the server? Opening them in a browser makes no sense in
99.99% of cases. When one opens a php file locally, the most likely
scenario is that you are opening it in order to edit it.

So if you had switched from gedit to some other text editor I could
understand it, but opening it in the browser by default is an idiotic
default for php files.

I upgraded because I was sick of running age-old versions of almost
every program, most no longer supported and full of bugs that were fixed
years ago upstream, but I'm astonished at the amount of regressions and,
worse, idiotic design decisions that have either been taken either with
the specific purpose of making things worse, or were taken by idiots
that didn't put the slightest amount of thought in it.

Fucking unbelievable. Every major release of Ubuntu is a step backwards.
Mostly because of Gnome.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome (not installed)
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.11-0ubuntu27.3
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 13 21:10:37 2020
InstallationDate: Installed on 2013-10-11 (2467 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
SourcePackage: meta-gnome3
UpgradeStatus: Upgraded to focal on 2020-07-12 (1 days ago)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal
-- 
php files now open by default in Chrome
https://bugs.launchpad.net/bugs/1887425
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to shared-mime-info in Ubuntu.

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

[Desktop-packages] [Bug 1895839] Re: CVE-2020-24977

** Description changed:

+ GNOME project libxml2 v2.9.10 and earlier have a global buffer over-read
+ vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c.
+ 
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977
  
- Upstream patch:
- 
https://gitlab.gnome.org/GNOME/libxml2/-/commit/8e7c20a1af8776677d7890f30b7a180567701a49
+ Upstream patch: 
+ 
https://gitlab.gnome.org/GNOME/libxml2/-/commit/50f06b3efb638efb0abd95dc62dca05ae67882c2
  
- GNOME project libxml2 v2.9.10 and earlier have a global buffer over-read
- vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c.
+ Bug report: https://gitlab.gnome.org/GNOME/libxml2/-/issues/178

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

Title:
  CVE-2020-24977

Status in libxml2 package in Ubuntu:
  New
Status in libxml2 package in Debian:
  Unknown

Bug description:
  GNOME project libxml2 v2.9.10 and earlier have a global buffer over-
  read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c.

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

  Upstream patch: 
  
https://gitlab.gnome.org/GNOME/libxml2/-/commit/50f06b3efb638efb0abd95dc62dca05ae67882c2

  Bug report: https://gitlab.gnome.org/GNOME/libxml2/-/issues/178

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

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

[Desktop-packages] [Bug 1895839] Re: CVE-2020-24977

** Description changed:

  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977
  
  Upstream patch:
  
https://gitlab.gnome.org/GNOME/libxml2/-/commit/8e7c20a1af8776677d7890f30b7a180567701a49
+ 
+ GNOME project libxml2 v2.9.10 and earlier have a global buffer over-read
+ vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c.

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

Title:
  CVE-2020-24977

Status in libxml2 package in Ubuntu:
  New
Status in libxml2 package in Debian:
  Unknown

Bug description:
  https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24977

  Upstream patch:
  
https://gitlab.gnome.org/GNOME/libxml2/-/commit/8e7c20a1af8776677d7890f30b7a180567701a49

  GNOME project libxml2 v2.9.10 and earlier have a global buffer over-
  read vulnerability in xmlEncodeEntitiesInternal at libxml2/entities.c.

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

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

[Desktop-packages] [Bug 1896313] Re: package gir1.2-javascriptcoregtk-4.0:amd64 2.28.4-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it

2020-09-22 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package gir1.2-javascriptcoregtk-4.0:amd64 2.28.4-0ubuntu0.20.04.1
  failed to install/upgrade: package is in a very bad inconsistent
  state; you should  reinstall it before attempting configuration

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  I cannot install or uninstall any apps.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: gir1.2-javascriptcoregtk-4.0:amd64 2.28.4-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Sep 19 14:35:44 2020
  DuplicateSignature:
   package:gir1.2-javascriptcoregtk-4.0:amd64:2.28.4-0ubuntu0.20.04.1
   Setting up libnss3:amd64 (2:3.49.1-1ubuntu1.5) ...
   dpkg: error processing package gir1.2-javascriptcoregtk-4.0:amd64 
(--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-09-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.3
  SourcePackage: webkit2gtk
  Title: package gir1.2-javascriptcoregtk-4.0:amd64 2.28.4-0ubuntu0.20.04.1 
failed to install/upgrade: package is in a very bad inconsistent state; you 
should  reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1879024] Re: Error message : "Failed to scan - unable to connect to scanner" when using simple-scan

2020-09-22 Thread Igor Shabalov

Have exactly same error with Brother MFS-L8900CDW
Upgraded from 18.04.5 - was working well before upgrade.

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

Title:
  Error message : "Failed to scan - unable to connect to scanner" when
  using simple-scan

Status in simple-scan package in Ubuntu:
  Confirmed

Bug description:
  1) System and program information:
  I am using Ubuntu 20.04 LTS and am trying to use the brother printer/scanner 
combo MFC-J5910DW in order to scan documents with simple-scan:
   
  simple-scan:
   Installed: 3.36.0-0ubuntu1
Candidate: 3.36.0-0ubuntu1
Version table:
   *** 3.36.0-0ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  2) Description of what I did and what happened:
  I downloaded and installed the newest scanner driver deb-packages (2 of them) 
from the official brother web-page and installed them using

  $ sudo apt-get install ./'sannerdirverfilename'.deb

  and there was no error message. So I also installed simple-scan from
  the Ubuntu repository using:

  $ sudo apt-get install simple-scan

  This also worked just fine. But when I now try to use simple-scan, it
  doesn't work. I call the program from the terminal command line:

  $ simple scan

  and it opens an interactive window, searches for a scanner and finds
  the brother scanner. But when I then hit the 'scan' button, I get the
  error message

  "Failed to scan - unable to connect to scanner"

  3) Error Log for simple-scan:
  So I used simple-scan with the debug option, and here is the log-file:

  $ simple-scan --debug
  [+0,00s] DEBUG: simple-scan.vala:638: Starting simple-scan 3.36.0, PID=7992
  [+0,00s] DEBUG: unsetenv() is not thread-safe and should not be used after 
threads are created
  [+0,02s] DEBUG: _g_io_module_get_default: Found default implementation dconf 
(DConfSettingsBackend) for ‘gsettings-backend’
  [+0,06s] DEBUG: app-window.vala:1908: Loading state from 
/home/barbara/.cache/simple-scan/state
  [+0,06s] DEBUG: app-window.vala:1887: Restoring window to 600x400 pixels
  [+0,33s] DEBUG: app-window.vala:1983: Saving state to 
/home/barbara/.cache/simple-scan/state
  [+6,00s] DEBUG: scanner.vala:1541: sane_init () -> SANE_STATUS_GOOD
  [+6,00s] DEBUG: scanner.vala:1547: SANE version 1.0.29
  [+6,00s] DEBUG: scanner.vala:1608: Requesting redetection of scan devices
  [+6,00s] DEBUG: scanner.vala:828: Processing request
  [+6,15s] DEBUG: app-window.vala:1983: Saving state to 
/home/barbara/.cache/simple-scan/state
  [+14,91s] DEBUG: scanner.vala:341: sane_get_devices () -> SANE_STATUS_GOOD
  [+14,91s] DEBUG: scanner.vala:353: Device: name="brother4:bus2;dev2" 
vendor="Brother" model="MFC-J5910DW" type="USB scanner"
  [+15,02s] DEBUG: app-window.vala:1983: Saving state to 
/home/barbara/.cache/simple-scan/state
  [+41,02s] DEBUG: simple-scan.vala:455: Requesting scan at 150 dpi from device 
'brother4:bus2;dev2'
  [+41,02s] DEBUG: scanner.vala:1676: Scanner.scan ("brother4:bus2;dev2", 
dpi=150, scan_mode=ScanMode.GRAY, depth=2, type=single, paper_width=0, 
paper_height=0, brightness=0, contrast=0, delay=3000ms)
  [+41,02s] DEBUG: scanner.vala:828: Processing request
  [+41,02s] DEBUG: scanner.vala:889: sane_open ("brother4:bus2;dev2") -> 
SANE_STATUS_IO_ERROR
  [+41,02s] WARNING: scanner.vala:893: Unable to open device: Error during 
device I/O
  [+41,43s] DEBUG: app-window.vala:1983: Saving state to 
/home/barbara/.cache/simple-scan/state
  [+56,27s] DEBUG: app-window.vala:1983: Saving state to 
/home/barbara/.cache/simple-scan/state
  [+100,09s] DEBUG: autosave-manager.vala:201: Deleting autosave records
  [+100,09s] DEBUG: scanner.vala:1704: Stopping scan thread
  [+100,09s] DEBUG: scanner.vala:828: Processing request
  [+100,09s] DEBUG: scanner.vala:1715: sane_exit ()

  I have no idea why sane cannot open the I/O device.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: simple-scan 3.36.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 16 07:54:46 2020
  InstallationDate: Installed on 2020-04-24 (21 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Dell Inc. Latitude E5450
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=2bb62112-1254-42cd-ba84-e3f2edc0d4b2 ro quiet splash vt.handoff=7
  SimpleScanLog:
   
  SourcePackage: simple-scan
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/30/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 0DCPV1
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell I

[Desktop-packages] [Bug 1896313] Re: package gir1.2-javascriptcoregtk-4.0:amd64 2.28.4-0ubuntu0.20.04.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public Security

** Information type changed from Public Security to Public

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

Title:
  package gir1.2-javascriptcoregtk-4.0:amd64 2.28.4-0ubuntu0.20.04.1
  failed to install/upgrade: package is in a very bad inconsistent
  state; you should  reinstall it before attempting configuration

Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  I cannot install or uninstall any apps.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: gir1.2-javascriptcoregtk-4.0:amd64 2.28.4-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Sep 19 14:35:44 2020
  DuplicateSignature:
   package:gir1.2-javascriptcoregtk-4.0:amd64:2.28.4-0ubuntu0.20.04.1
   Setting up libnss3:amd64 (2:3.49.1-1ubuntu1.5) ...
   dpkg: error processing package gir1.2-javascriptcoregtk-4.0:amd64 
(--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2020-09-18 (0 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.3
  SourcePackage: webkit2gtk
  Title: package gir1.2-javascriptcoregtk-4.0:amd64 2.28.4-0ubuntu0.20.04.1 
failed to install/upgrade: package is in a very bad inconsistent state; you 
should  reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896367] Re: package ubuntu-software 3.36.1-0ubuntu0.20.04.0 failed to install/upgrade: problemas de dependencias - se deja sin configurar

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Title:
  package ubuntu-software 3.36.1-0ubuntu0.20.04.0 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in gnome-software package in Ubuntu:
  New

Bug description:
  error al actualizar

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-software 3.36.1-0ubuntu0.20.04.0
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  AptOrdering:
   firefox-locale-en:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Sep 12 12:42:50 2020
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2020-02-17 (215 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.36.1-0ubuntu0.20.04.0
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: gnome-software
  Title: package ubuntu-software 3.36.1-0ubuntu0.20.04.0 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to focal on 2020-05-10 (132 days ago)

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

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

[Desktop-packages] [Bug 1896367] [NEW] package ubuntu-software 3.36.1-0ubuntu0.20.04.0 failed to install/upgrade: problemas de dependencias - se deja sin configurar

You have been subscribed to a public bug:

error al actualizar

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: ubuntu-software 3.36.1-0ubuntu0.20.04.0
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
AptOrdering:
 firefox-locale-en:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Sep 12 12:42:50 2020
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2020-02-17 (215 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
InstalledPlugins:
 gnome-software-plugin-flatpak N/A
 gnome-software-plugin-snap3.36.1-0ubuntu0.20.04.0
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: gnome-software
Title: package ubuntu-software 3.36.1-0ubuntu0.20.04.0 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: Upgraded to focal on 2020-05-10 (132 days ago)

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


** Tags: amd64 apport-package focal
-- 
package ubuntu-software 3.36.1-0ubuntu0.20.04.0 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
https://bugs.launchpad.net/bugs/1896367
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-software in Ubuntu.

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

[Desktop-packages] [Bug 1890716] Re: misidentifies .html file as Perl script when it contains JavaScript "use strict"

** Also affects: kde-cli-tools (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in kde-cli-tools package in Ubuntu:
  New
Status in shared-mime-info package in Ubuntu:
  New
Status in shared-mime-info package in Debian:
  Unknown

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions

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

[Desktop-packages] [Bug 1857824] Re: kmimetypefinder5 misidentifies mimetype of python files containing certain strings

2020-09-22 Thread Kai Kasurinen

** Package changed: kde-cli-tools (Ubuntu) => shared-mime-info (Ubuntu)

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

Title:
  kmimetypefinder5 misidentifies mimetype of python files containing
  certain strings

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  Expected behavior:

  $ kmimetypefinder5 example.py 
  text/x-python3

  or

  $ kmimetypefinder5 example.py 
  text/x-python

  or

  $ kmimetypefinder5 example.py 
  text/plain

  Actual behavior:

  $ kmimetypefinder5 example.py 
  application/xhtml+xml

  Summary: Python scripts with a string containing HTML can be
  misidentified as HTML files by kmimetypefinder5.

  For example, this python script is identified as
  "application/xhtml+xml":

  #! /usr/bin/env python3
  example_string = \
  """\
  http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
  http://www.w3.org/1999/xhtml";>

  Example title


  Example body

  
  """
  print('Hello, world!')

  This difficulty is not shared by other mimetype identification tools.

  $ kmimetypefinder5 example.py 
  application/xhtml+xml
  $ cat example2.py #! /usr/bin/env python3
  print('Hello, world!')
  $ kmimetypefinder5 example2.py 
  text/x-python3
  $ mimetype 'example.py'
  example.py: text/x-python
  $ mimetype 'example2.py'
  example2.py: text/x-python
  $ file --mime-type 'example.py'
  example.py: text/plain
  $ file --mime-type 'example2.py'
  example2.py: text/plain

  $ lsb_release -rd
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  $ apt-cache policy kde-cli-tools
  kde-cli-tools:
Installed: 4:5.12.8-0ubuntu0.1
Candidate: 4:5.12.8-0ubuntu0.1
Version table:
   *** 4:5.12.8-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   4:5.12.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
  Uname: Linux 4.15.0-72-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sun Dec 29 13:28:37 2019
  InstallationDate: Installed on 2018-12-12 (381 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: kde-cli-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1857824/+subscriptions

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

[Desktop-packages] [Bug 1857824] [NEW] kmimetypefinder5 misidentifies mimetype of python files containing certain strings

You have been subscribed to a public bug:

Expected behavior:

$ kmimetypefinder5 example.py 
text/x-python3

or

$ kmimetypefinder5 example.py 
text/x-python

or

$ kmimetypefinder5 example.py 
text/plain

Actual behavior:

$ kmimetypefinder5 example.py 
application/xhtml+xml

Summary: Python scripts with a string containing HTML can be
misidentified as HTML files by kmimetypefinder5.

For example, this python script is identified as
"application/xhtml+xml":

#! /usr/bin/env python3
example_string = \
"""\
http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
http://www.w3.org/1999/xhtml";>
  
Example title
  
  
Example body
  

"""
print('Hello, world!')

This difficulty is not shared by other mimetype identification tools.

$ kmimetypefinder5 example.py 
application/xhtml+xml
$ cat example2.py #! /usr/bin/env python3
print('Hello, world!')
$ kmimetypefinder5 example2.py 
text/x-python3
$ mimetype 'example.py'
example.py: text/x-python
$ mimetype 'example2.py'
example2.py: text/x-python
$ file --mime-type 'example.py'
example.py: text/plain
$ file --mime-type 'example2.py'
example2.py: text/plain

$ lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04
$ apt-cache policy kde-cli-tools
kde-cli-tools:
  Installed: 4:5.12.8-0ubuntu0.1
  Candidate: 4:5.12.8-0ubuntu0.1
  Version table:
 *** 4:5.12.8-0ubuntu0.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 4:5.12.4-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: kde-cli-tools 4:5.12.8-0ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18
Uname: Linux 4.15.0-72-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: KDE
Date: Sun Dec 29 13:28:37 2019
InstallationDate: Installed on 2018-12-12 (381 days ago)
InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
SourcePackage: kde-cli-tools
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages
-- 
kmimetypefinder5 misidentifies mimetype of python files containing certain 
strings
https://bugs.launchpad.net/bugs/1857824
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to shared-mime-info in Ubuntu.

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

[Desktop-packages] [Bug 1890716] Re: kmimetypefinder5 *.html reports wrong type

2020-09-22 Thread Kai Kasurinen

** Changed in: shared-mime-info (Ubuntu)
   Status: Invalid => New

** Bug watch added: Debian Bug tracker #887709
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887709

** Also affects: shared-mime-info (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887709
   Importance: Unknown
   Status: Unknown

** Summary changed:

- kmimetypefinder5 *.html reports wrong type
+ misidentifies .html file as Perl script when it contains JavaScript "use 
strict"

** Bug watch added: gitlab.freedesktop.org/xdg/shared-mime-info/-/issues #80
   https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/80

** Also affects: shared-mime-info via
   https://gitlab.freedesktop.org/xdg/shared-mime-info/-/issues/80
   Importance: Unknown
   Status: Unknown

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

Title:
  misidentifies .html file as Perl script when it contains JavaScript
  "use strict"

Status in shared-mime-info:
  Unknown
Status in shared-mime-info package in Ubuntu:
  New
Status in shared-mime-info package in Debian:
  Unknown

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/1890716/+subscriptions

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

This bug was fixed in the package mutter - 3.38.0-1ubuntu1

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

  * Merge with debian, including new upstream stable release, remaining changes:
- debian/gbp.conf: update upstream branch to point to ubuntu/master
- debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
  + X11: Add support for fractional scaling using Randr
  * d/p/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Refresh as per upstream changes
- Don't update UI scale factor on xrandr-manager creation.
  This would trigger settings initializations that are supposed to happen
  after the clutter-x11 backend has been initialized, leading to saving
  too early the cached font-dpi scaling, and then making clutter backend
  to set a new (wrong) one. (LP: #1892440)
  * d/p/clutter-backend-x11-Don-t-set-the-font-dpi-computed-on-X1.patch:
- Don't set the font-dpi on clutter-backend-x11 (LP: #1892440)

mutter (3.38.0-1) experimental; urgency=medium

  * New upstream release:
- screencast: Only use DMA buffers for i915
- Fixed crashes
  * debian/patches: Refresh
  * d/p/input-mapper-Don-t-match-touchscreens-to-the-absence-of-a.patch:
- Dropped, applied upstream

mutter (3.37.92-2) experimental; urgency=medium

  * Team upload
  * d/p/input-mapper-Don-t-match-touchscreens-to-the-absence-of-a.patch:
Add patch to work around a crash with gnome-remote-desktop

mutter (3.37.92-1) experimental; urgency=medium

  * Team upload
  * New upstream release
- Fix stale cursor positions in remote desktop sessions
- xwayland: Add a setting to disable selected X extensions
- Fix screencasting when using QXL
- Cull actors that don't intersect with the redraw clip
- Optimize painting of backgrounds when culling is unavailable
- Improve support for Hangul input method
- Support debug paint overlay for opaque regions
- Fix launching flatpak applications when autostarting Xwayland
- Add support for capture scanouts in screencasts
- Allow integrated tablet devices to cycle outputs
- Improve mapping input devices to the most relevant output
- Only enable auto-rotation in touch mode
- Fix various crashes
  * d/control.in: Update libgbm build-dependency
  * d/copyright: Update
  * d/control.in, d/rules: Enable Pipewire on Debian (but not Ubuntu).
Now that we have Pipewire 0.3 in experimental, we can enable
screencasting and remote desktop support.
  * debian/libmutter-7-0.symbols: Update

 -- Marco Trevisan (Treviño)   Wed, 16 Sep 2020
14:06:53 +0200

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

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

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

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to

[Desktop-packages] [Bug 1890716] Re: kmimetypefinder5 *.html reports wrong type

I've reported a new bug providing a complete and correct description:
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682

This one can be safely closed.

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

Title:
  kmimetypefinder5 *.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Invalid

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions

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

[Desktop-packages] [Bug 1890716] Re: kmimetypefinder5 *.html reports wrong type

New bug reopened with complete and correct explanation: 
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1896682

** Changed in: shared-mime-info (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  kmimetypefinder5 *.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Invalid

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions

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

[Desktop-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

In groovy the code for vte-keep-FD patch has been refactored to support
new upstream code.

However, I think it's the time we plan to remove this next cycle, given
that gdebi is the only project using it so far [1], and that upstream
already suggested a better way to do it [2].

So, if someone is still interested in fixing gdebi to address this,
please act as otherwise it's very likely that next versions of vte will
break it.


[1] https://codesearch.debian.net/search?q=VTE_PTY_KEEP_FD&literal=1
[2] https://bugzilla.gnome.org/show_bug.cgi?id=320128#c23

** Bug watch added: bugzilla.gnome.org/ #320128
   https://bugzilla.gnome.org/show_bug.cgi?id=320128

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in vte2.91 source package in Bionic:
  Fix Released

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

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

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

2020-09-22 Thread Gilbertf

problem seems gone since 5.4.0-48-generic #52

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

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

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

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

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

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

  Sound was working fine with previous kernel.

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

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

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

[Desktop-packages] [Bug 1896393] Re: gedit not responding to keystrokes

2020-09-22 Thread Cliff Carson

Trying to produce the error delay in a restrictive environment without
great success.  Did get gedit running on some of my c++ programs
thinking maybe it was a plugin that was working.  Did see that when I
was looking at a line and moving the cursor with the arrow keys that
there was a definite delay.  As I moved the cursor across the line not
every key (arrow right/left) was immediate as I would expect (system was
doing nothing else).  Did dump the journal at the time and passing the
snippet of the time I started gedit and when I observed the delay.  Will
continue to try to better document this problem.

Sep 22 15:51:18 cliffps chromium_chromium.desktop[6876]: 
[6876:15002:0922/155118.463902:ERROR:get_updates_processor.cc(258)] 
PostClientToServerMessage() failed during GetUpdates with error 2
Sep 22 15:52:23 cliffps dbus-daemon[1602]: [session uid=1000 pid=1602] 
Activating service name='org.gnome.gedit' requested by ':1.39' (uid=1000 
pid=1871 comm="/usr/bin/gnome-shell " label="unconfined")
Sep 22 15:52:23 cliffps dbus-daemon[1602]: [session uid=1000 pid=1602] 
Successfully activated service 'org.gnome.gedit'
Sep 22 15:54:42 cliffps wpa_supplicant[894]: wlp3s0: Reject scan trigger since 
one is already pending
Sep 22 15:55:08 cliffps /usr/libexec/gdm-x-session[1687]: (II) Axis 0x1 value 
-429 is outside expected range [-26, 548]
Sep 22 15:55:08 cliffps /usr/libexec/gdm-x-session[1687]: See 
https://wayland.freedesktop.org/libinput/doc/1.16.1/absolute_coordinate_ranges.html
 for details
Sep 22 15:55:42 cliffps systemd[1590]: Started Application launched by 
gsd-media-keys.
Sep 22 15:55:42 cliffps systemd[1590]: Started VTE child process 15458 launched 
by gnome-terminal-server process 2731.
Sep 22 15:55:42 cliffps systemd[1590]: 
app-gnome-x\x2dterminal\x2demulator-15449.scope: Succeeded.

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

Title:
  gedit not responding to keystrokes

Status in gedit package in Ubuntu:
  New

Bug description:
  Don't know how to further document this except was is observed during
  the gedit session.

  While typing information into the gedit window the keystrokes get
  delayed 1-2 seconds from the time the keys are struct and when the
  character(s) show up on the screen.  It's as if the system was too
  busy to service the key input but that doesn't appear to be the case.
  This problem doesn't occur on the current gedit running under 20.04.

  Any suggestions on how to document this problem?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gedit 3.36.2-1
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 20 13:03:43 2020
  InstallationDate: Installed on 2020-08-28 (22 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200826)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gedit
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

2020-09-22 Thread Heather Ellsworth

Here is the upstream build that corresponds to the topmost commit included in 
6.4.6:
https://ci.libreoffice.org/job/gerrit_64/1652/

I found this by finding the topmost merge on the libreoffice-6-4-6 branch 
(which is where this package would have been built from):
https://gerrit.libreoffice.org/c/core/+/100055

And then tracing back to the ci job. I can add this in future
libreoffice SRU descriptions as well.

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

Title:
  [SRU] libreoffice 6.4.6 for focal

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Focal:
  Fix Committed

Bug description:
  [Impact]

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

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

  [Test Case]

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

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

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

  [Regression Potential]

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

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

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

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

[Desktop-packages] [Bug 1890716] Re: xdg-mime query filetype index.html reports wrong type

After running that commands I got the following output:

$ ...
Running kmimetypefinder5 "/home/alex/Desktop/index.html"
application/x-perl


It seems like that kmimetypefinder5 is major culprit here. I've found another 
unrelated bugreport here which was reported about a year ago: 
https://bugs.launchpad.net/ubuntu/+source/kde-cli-tools/+bug/1857824

In that case the program reports wrong type for *.py files with correct 
content. Weird!
I think it's wortht to rename this bugreport.

** Summary changed:

- xdg-mime query filetype index.html reports wrong type
+ kmimetypefinder5 *.html reports wrong type

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

Title:
  kmimetypefinder5 *.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Incomplete

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions

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

[Desktop-packages] [Bug 1756597] Re: Rhythmbox plugin "Song Lyrics" not working

2020-09-22 Thread crvi

Tracked in: https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1829

** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/-/issues #1829
   https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1829

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

Title:
  Rhythmbox plugin "Song Lyrics" not working

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  With either rhythmbox-plugins-3.0.2-0ubuntu2 (Linux Mint 17.3 Cinnamon) or 
rhythmbox-plugins-3.3-1ubuntu7 (Linux Mint 18.2 XFCE) when the "Song Lyrics" 
plugin is enabled and the following are checked, lyrics are never displayed:
  * WinampCN (www.winampcn.com)
  * Dark Lyrics (darklyrics.com)
  * Jetlyrics (jetlyrics.com)
  * I didn't use the other two since I speak only English

  Looking at the code in '/usr/lib/rhythmbox/plugins/lyrics/' and
  experimenting with the queries suggests that the remote web sites have
  changed.

  For example, 'JetlyricsParser.py' has:
  * q = title + ' - ' + artist
  * url = 'http://www.jetlyrics.com/search.php?q=%s' % (q)

  But http://www.jetlyrics.com/search.php?q=acdc-hells+bells is 404,
  while doing it manually from http://www.jetlyrics.com/ yields
  http://lyrics.jetmute.com/search.php?q=acdc+hells+bells&search=Search
  with some results.

  Likewise DarkLyricsParser.py has:
  * url = 'http://www.darklyrics.com/lyrics/%s/%s.html' % (best_match.artist, 
best_match.album)

  But http://www.darklyrics.com/lyrics/acdc/hells+bells.html returns a
  404/search page and the  search "acdc hells bells" from that page is
  null but manually working through the form you can get
  https://www.azlyrics.com/lyrics/acdc/hellsbells.html.

  In those examples both the base web site and search strings have
  changed, rendering the plugin code out of date.

  Also, CTRL-L no longer works in either Mint 17's RB 3.0.2 or Mint 18's
  3.0.0, but "View > Song Lyrics" works.

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

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

[Desktop-packages] [Bug 1896646] Re: bluetooth no longer installed

2020-09-22 Thread Ubuntu Foundations Team Bug Bot

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

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

Title:
  bluetooth no longer installed

Status in bluez package in Ubuntu:
  New

Bug description:
  22 september 2020 update removed bluetooth capability.  No Bluetooth
  hardware detected by system, cannot turn on or add devices.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
  Uname: Linux 5.4.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 22 12:53:31 2020
  InstallationDate: Installed on 2019-12-07 (290 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  InterestingModules: bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. USB2.0 VGA UVC 
WebCam
   Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
   |__ Port 5: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 
480M
   |__ Port 6: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
   |__ Port 6: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
  MachineType: ASUSTeK COMPUTER INC. X556UAM
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/06/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X556UAM.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X556UAM
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UAM.305:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX556UAM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X556UAM
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   
  rfkill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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

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

[Desktop-packages] [Bug 1896646] [NEW] bluetooth no longer installed

You have been subscribed to a public bug:

22 september 2020 update removed bluetooth capability.  No Bluetooth
hardware detected by system, cannot turn on or add devices.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 5.4.0-49.53-generic 5.4.65
Uname: Linux 5.4.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.9
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 22 12:53:31 2020
InstallationDate: Installed on 2019-12-07 (290 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
InterestingModules: bluetooth
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. USB2.0 VGA UVC 
WebCam
 Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
 |__ Port 5: Dev 2, If 0, Class=Vendor Specific Class, Driver=rtsx_usb, 480M
 |__ Port 6: Dev 3, If 0, Class=Video, Driver=uvcvideo, 480M
 |__ Port 6: Dev 3, If 1, Class=Video, Driver=uvcvideo, 480M
MachineType: ASUSTeK COMPUTER INC. X556UAM
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-49-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/06/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X556UAM.305
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X556UAM
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX556UAM.305:bd07/06/2016:svnASUSTeKCOMPUTERINC.:pnX556UAM:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UAM:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X556UAM
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
hciconfig:
 
rfkill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

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


** Tags: amd64 apport-bug focal
-- 
bluetooth no longer installed
https://bugs.launchpad.net/bugs/1896646
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to bluez in Ubuntu.

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

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

2020-09-22 Thread Heather Ellsworth

Here are also the test results of autopkgtests run for various
architectures in launchpad:

* AMD64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-hellsworth-libreoffice10/focal/amd64/libr/libreoffice/20200827_021732_c16ab@/log.gz
* ARMHF: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-hellsworth-libreoffice10/focal/armhf/libr/libreoffice/20200827_115410_b5cdf@/log.gz
* PPC64EL: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-hellsworth-libreoffice10/focal/ppc64el/libr/libreoffice/20200826_204018_36d47@/log.gz
* S390X: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-hellsworth-libreoffice10/focal/s390x/libr/libreoffice/20200826_193530_72dce@/log.gz

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

Title:
  [SRU] libreoffice 6.4.6 for focal

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Focal:
  Fix Committed

Bug description:
  [Impact]

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

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

  [Test Case]

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

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

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

  [Regression Potential]

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

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

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

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

[Desktop-packages] [Bug 1871148] Re: services start before apparmor profiles are loaded

2020-09-22 Thread Jamie Strandboge

This was fixed in snapd in 2.44 via
https://github.com/snapcore/snapd/pull/8467

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

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

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

Title:
  services start before apparmor profiles are loaded

Status in AppArmor:
  Invalid
Status in snapd:
  Fix Released
Status in apparmor package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released
Status in zsys package in Ubuntu:
  Invalid
Status in apparmor source package in Focal:
  Fix Released
Status in snapd source package in Focal:
  Fix Released
Status in zsys source package in Focal:
  Invalid

Bug description:
  Per discussion with Zyga in #snapd on Freenode, I have hit a race
  condition where services are being started by the system before
  apparmor has been started. I have a complete log of my system showing
  the effect somewhere within at https://paste.ubuntu.com/p/Jyx6gfFc3q/.
  Restarting apparmor using `sudo systemctl restart apparmor` is enough
  to bring installed snaps back to full functionality.

  Previously, when running any snap I would receive the following in the
  terminal:

  ---
  cannot change profile for the next exec call: No such file or directory
  snap-update-ns failed with code 1: File exists
  ---

  Updated to add for Jamie:

  $ snap version
  snap2.44.2+20.04
  snapd   2.44.2+20.04
  series  16
  ubuntu  20.04
  kernel  5.4.0-21-generic

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

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

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

2020-09-22 Thread Heather Ellsworth

More information about the upstream QA testing can be found here:
* Automated tests - 
https://wiki.documentfoundation.org/QA/Testing/Automated_Tests
* Automated UI tests - https://wiki.documentfoundation.org/Development/UITests
* Regression tests - 
https://wiki.documentfoundation.org/QA/Testing/Regression_Tests
* Feature tests - https://wiki.documentfoundation.org/QA/Testing/Feature_Tests

Recent test results of upstream's libreoffice-6-4 branch can be found here:
https://jenkins.libreoffice.org/job/gerrit_64/

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

Title:
  [SRU] libreoffice 6.4.6 for focal

Status in libreoffice package in Ubuntu:
  Fix Released
Status in libreoffice source package in Focal:
  Fix Committed

Bug description:
  [Impact]

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

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

  [Test Case]

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

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

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

  [Regression Potential]

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

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

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

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

[Desktop-packages] [Bug 1896654] Re: Windows flicker when resizing with mouse

2020-09-22 Thread Sam Lane

** Attachment added: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1896654/+attachment/5413297/+files/Lspci.txt

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

Title:
  Windows flicker when resizing with mouse

Status in mutter package in Ubuntu:
  New

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker. It only flickers when actively being
  resized, and when I stop dragging, it looks normal. This behavior is
  does not occur on same pc in 20.04. Sometimes the flickering is black,
  sometimes the flickering makes the wallpaper visible, even when there
  is a window behind the window being resized.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Sep 22 14:48:00 2020
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896654] [NEW] Windows flicker when resizing with mouse

2020-09-22 Thread Sam Lane

Public bug reported:

When resizing a window with the mouse by dragging the edge or corner,
the window begins to flicker. It only flickers when actively being
resized, and when I stop dragging, it looks normal. This behavior is
does not occur on same pc in 20.04. Sometimes the flickering is black,
sometimes the flickering makes the wallpaper visible, even when there is
a window behind the window being resized.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: mutter (not installed)
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Budgie:GNOME
Date: Tue Sep 22 14:48:00 2020
InstallationDate: Installed on 2020-09-22 (0 days ago)
InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200921)
SourcePackage: mutter
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug groovy

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

Title:
  Windows flicker when resizing with mouse

Status in mutter package in Ubuntu:
  New

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker. It only flickers when actively being
  resized, and when I stop dragging, it looks normal. This behavior is
  does not occur on same pc in 20.04. Sometimes the flickering is black,
  sometimes the flickering makes the wallpaper visible, even when there
  is a window behind the window being resized.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: mutter (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: Budgie:GNOME
  Date: Tue Sep 22 14:48:00 2020
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  SourcePackage: mutter
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_s

This bug has been already fixed as part of 3.36.4-0ubuntu0.20.04.2, and
opened by the SRU tool as it is included again in the changelog as it's
being part of a debian release we've merged with.

So marking as verified (as discussed with SRU team)

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

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

Title:
  gnome-shell crashed with SIGSEGV in get_top_visible_window_actor()
  from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack()
  from stack_tracker_sync_stack_later() from call_later_func()

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

Bug description:
  [ Impact ]

  GNOME Shell crashes

  [ Test case ]

  Four-finger gesture seems to trigger it, in any case it can be monitored via 
   - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.1+git20191024-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 
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/1857947/+subscriptions

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

[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))

This bug has been already fixed as part of 3.36.4-0ubuntu0.20.04.2, and
opened by the SRU tool as it is included again in the changelog as it's
being part of a debian release we've merged with.

So marking as verified (as discussed with SRU team)

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

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

Title:
  gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion
  failed: (META_IS_STAGE_X11 (impl))

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell crashes in meta_x11_get_stage_window.

  [ Test case ]

  Perform touch events via touchpad or touchscreen, eventually the shell
  will crash.

  Errors can be monitored at:
   https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  ---

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 22:08:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: 
gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)
  UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev 
sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

2020-09-22 Thread Cristiano Nunes

Thanks, Brian.

I'll test the new package coming soon.

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it

This bug has been already fixed as part of 3.36.4-0ubuntu0.20.04.2, and
opened by the SRU tool as it is included again in the changelog as it's
being part of a debian release we've merged with.

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

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

Title:
  Update to 3.36.4 and SRU it

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in X11 screencasting and touch-interaction, so
  ensure there are no problems with those.

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

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

[Desktop-packages] [Bug 1894606] Re: [SRU] Add profile-set for HP Thunderbolt Dock

This bug was fixed in the package pulseaudio - 1:13.99.1-1ubuntu11

---
pulseaudio (1:13.99.1-1ubuntu11) groovy; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/0001-alsa-mixer-Add-support-for-HP-Thunderbolt-Dock.patch
  * d/p/0002-alsa-mixer-Expand-comments-in-the-HP-Thunderbolt-Doc.patch
Add profile-sets for HP Thunderbolt Dock (LP: #1894606)

 -- Alberto Milone   Tue, 22 Sep 2020
10:09:09 +0200

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

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

Title:
  [SRU] Add profile-set for HP Thunderbolt Dock

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Released

Bug description:
  [Impact]
  HP Thunderbolt Dock has a USB audio device provides headset connector 
functionality. The Dock can also attach an optional USB audio module. Since 
they are both USB audio device, the input/output names are the same and it 
confuses user.

  [Fix]
  Add PulseAudio profile-sets for each USB device with different monikers.

  The merge request is already approved by maintainer, will be merged after 
14.0 release:
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/353

  [Test]
  With profile-set applied, two different USB audio device on HP TBT Dock have 
distinctive names.

  [Regression Potential]
  Currently I can't think of any regression risk, as this SRU only adds new 
profile-sets and description translation.

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

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

[Desktop-packages] [Bug 1896332] Re: SRU 3.36.6

Hello Marco, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  SRU 3.36.6

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.6

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in X11 device management, desktop background
  image handling, screen-casting and night-switch.

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

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

[Desktop-packages] [Bug 1870867] Re: gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion failed: (META_IS_STAGE_X11 (impl))

Hello Ivan, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  gnome-shell crashed with SIGABRT meta_x11_get_stage_window: assertion
  failed: (META_IS_STAGE_X11 (impl))

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell crashes in meta_x11_get_stage_window.

  [ Test case ]

  Perform touch events via touchpad or touchscreen, eventually the shell
  will crash.

  Errors can be monitored at:
   https://errors.ubuntu.com/problem/1d4cdd9f2e9cd378a3e0aeed140079f319454bf2

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  ---

  ProblemType: CrashDistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.0-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr  4 22:08:06 2020
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1Signal: 6SourcePackage: 
gnome-shell
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libmutter-6.so.0
  Title: gnome-shell crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago)
  UserGroups: adm cdrom dialout dip docker input libvirt lpadmin plugdev 
sambashare sudo
  separator:

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

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

[Desktop-packages] [Bug 1887998] Re: Update to 3.36.4 and SRU it

Hello Marco, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  Update to 3.36.4 and SRU it

Status in mutter package in Ubuntu:
  Fix Released
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/mutter/-/commits/3.36.4

  [ Test case ]

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  GNOME Shell and its components should continue working

  [ Regression potential ]

  There have been fixes in X11 screencasting and touch-interaction, so
  ensure there are no problems with those.

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

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

[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)

Hello Cristiano, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mutter (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
  on Nvidia)

Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  Fix Committed
Status in mutter source package in Groovy:
  Fix Committed

Bug description:
  [ Impact ]

  GNOME Shell starts with a wrong text size

  
  [ Test case ]

  In a terminal run:
- Xephyr :2

  In another one:
- env DISPLAY=:2 dbus-run-session gnome-shell --x11

  The shell should run in the embedded window, with the correct text
  size, running it again (without closing Xephyr window, but stopping
  the shell execution) should not bigger than expected.

  -- Other test case (hw dependant)

  - Login, ensure that the Shell text size matches the configured one.

  
  [ Regression potential ]

  Initial UI scaling when fractional scaling is enabled is wrong.

  
  [ Workaround ]

  Run on startup:
   - gsettings set org.gnome.desktop.interface scaling-factor \
   $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' 
-f2)

  
  ---

  See also bug 1892521.

  The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04
  causes small text in GNOME Shell menu with  NVIDIA cards.

  With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem 
is after update to the (3.36.4-0ubuntu0.20.04.2).
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2020-08-18 (2 days ago)
  InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" 
(20200815)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.36.4-0ubuntu0.20.04.2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Tags:  focal
  Uname: Linux 5.4.0-42-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2020-08-15T17:44:36

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

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

[Desktop-packages] [Bug 1558886] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info()

Hello Anthony, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: mutter (Ubuntu Focal)
   Status: In Progress => Fix Committed

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

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

Title:
  gnome-shell crashed with SIGSEGV in
  _clutter_input_device_reset_scroll_info()

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Fix Committed
Status in mutter source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Using Ubuntu 16.04 and 20.04 LTS Beta release. Was using gnome-shell
  and using Chrome web browser when computer became unresponsive to any
  commands or mouse clicks. About 3-4 minutes later a crash report
  popped up on my screen. I clicked report and now I am reporting this
  as a new bug as I have never had this happen before on previous
  versions of Ubuntu. I was attempting to copy and save an image from
  Google Chrome when this happened.

  Similar crash still happening, as per
  https://errors.ubuntu.com/problem/fda12af21f79f7f1e23ab3cc830da47eca410baa

  

  [  Test case ]

  Run xinput and figure device IDs for your mouse.
  Run this evil script with 9 changed (be sure to change both) to your id:

for ((;;)) do xinput disable 9; echo Disabled; xinput enable 9; echo
  Enabled; done

  While the script runs, open some context menu in some program. It may require 
a few clicks due to evil script enabling/disabling mouse.
  This will sometimes crash GTK programs due to a mirror bug in GTK.

  GNOME Shell should not crash

  [ Regression potential ]

  Devices might be not be properly recognized when plugged and unplugged

  
  

  Description:  Ubuntu Xenial Xerus (development branch)
  Release:  16.04

  lostprophet@DigitalDamage:~$ apt-cache policy google-chrome-stable
  google-chrome-stable:
    Installed: 49.0.2623.75-1
    Candidate: 49.0.2623.75-1
    Version table:
   *** 49.0.2623.75-1 100
  100 /var/lib/dpkg/status

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-14-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Mar 17 22:20:56 2016
  DisplayManager: lightdm
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2016-02-24 (22 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7f634ba78320:mov0xe0(%rdi),%rax
   PC (0x7f634ba78320) ok
   source "0xe0(%rdi)" (0x00e0) not located in a known VMA region (needed 
readable region)!
   destination "%rax" ok
  SegvReason: reading NULL VMASignal: 11SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   clutter_x11_handle_event () from 
/usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/libmutter.so.0
  Title: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()
  UpgradeStatus: Upgraded to xenial on 2016-03-03 (14 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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

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

[Desktop-packages] [Bug 1857947] Re: gnome-shell crashed with SIGSEGV in get_top_visible_window_actor() from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack() from stack_tracker_sync_s

Hello errors.ubuntu.com, or anyone else affected,

Accepted mutter into focal-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mutter/3.36.6-1ubuntu0.20.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

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

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

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

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

Title:
  gnome-shell crashed with SIGSEGV in get_top_visible_window_actor()
  from meta_compositor_sync_stack() from meta_stack_tracker_sync_stack()
  from stack_tracker_sync_stack_later() from call_later_func()

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

Bug description:
  [ Impact ]

  GNOME Shell crashes

  [ Test case ]

  Four-finger gesture seems to trigger it, in any case it can be monitored via 
   - https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 

  [ Regression potential ]

  Windows might not be closed correctly when requested via delete-events
  (clicking on clientside decoration close button).

  

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.1+git20191024-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/b0255fcaba794d0a5100e58aeb6f61d2f9d9fe66 
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/1857947/+subscriptions

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

[Desktop-packages] [Bug 1756597] Re: Rhythmbox plugin "Song Lyrics" not working

2020-09-22 Thread Adriaan Nel

If somebody can guide me how, I am willing to help update the plugin.
This is a really frustrating problem on Rhythmbox.

2 Years & still nothing has been done.  Please guide me, and I'll work
on it.

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

Title:
  Rhythmbox plugin "Song Lyrics" not working

Status in rhythmbox package in Ubuntu:
  Confirmed

Bug description:
  With either rhythmbox-plugins-3.0.2-0ubuntu2 (Linux Mint 17.3 Cinnamon) or 
rhythmbox-plugins-3.3-1ubuntu7 (Linux Mint 18.2 XFCE) when the "Song Lyrics" 
plugin is enabled and the following are checked, lyrics are never displayed:
  * WinampCN (www.winampcn.com)
  * Dark Lyrics (darklyrics.com)
  * Jetlyrics (jetlyrics.com)
  * I didn't use the other two since I speak only English

  Looking at the code in '/usr/lib/rhythmbox/plugins/lyrics/' and
  experimenting with the queries suggests that the remote web sites have
  changed.

  For example, 'JetlyricsParser.py' has:
  * q = title + ' - ' + artist
  * url = 'http://www.jetlyrics.com/search.php?q=%s' % (q)

  But http://www.jetlyrics.com/search.php?q=acdc-hells+bells is 404,
  while doing it manually from http://www.jetlyrics.com/ yields
  http://lyrics.jetmute.com/search.php?q=acdc+hells+bells&search=Search
  with some results.

  Likewise DarkLyricsParser.py has:
  * url = 'http://www.darklyrics.com/lyrics/%s/%s.html' % (best_match.artist, 
best_match.album)

  But http://www.darklyrics.com/lyrics/acdc/hells+bells.html returns a
  404/search page and the  search "acdc hells bells" from that page is
  null but manually working through the form you can get
  https://www.azlyrics.com/lyrics/acdc/hellsbells.html.

  In those examples both the base web site and search strings have
  changed, rendering the plugin code out of date.

  Also, CTRL-L no longer works in either Mint 17's RB 3.0.2 or Mint 18's
  3.0.0, but "View > Song Lyrics" works.

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

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

[Desktop-packages] [Bug 1896645] [NEW] Dual screen window size problem

2020-09-22 Thread Mitchell

Public bug reported:

Certain programs don't seem to co-operate well with a dual monitor
setup. If it is of any importance, my setup is a laptop with a TV
plugged in via HDMI. So far I've found that VLC media player and Oracle
Virtualbox won't play nicely with two monitors. When both monitors are
in use, virtualbox crashes before it can open, and vlc tends to freeze
the entire system, requiring a hard reboot. If I run these programs
while only one monitor is being used and plug in the second one, they'll
start misbehaving if moved to the other monitor. virtualbox and vlc will
both become way too huge to be usable.

Description:Ubuntu 18.04.5 LTS
Release:18.04

xorg:
  Installed: 1:7.7+19ubuntu7.1
  Candidate: 1:7.7+19ubuntu7.1
  Version table:
 *** 1:7.7+19ubuntu7.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:7.7+19ubuntu7 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 22 12:02:21 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8364]
InstallationDate: Installed on 2020-02-21 (214 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: HP HP Pavilion Laptop 15-cc0xx
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=da68f1b9-ec5f-4962-8098-08f28713396e ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8364
dmi.board.vendor: HP
dmi.board.version: 46.23
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd11/03/2017:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cc0xx
dmi.product.sku: 1KU17UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "Screen recordings of some of the issues"
   
https://bugs.launchpad.net/bugs/1896645/+attachment/5413232/+files/multiple-screen-problem.tar.xz

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

Title:
  Dual screen window size problem

Status in xorg package in Ubuntu:
  New

Bug description:
  Certain programs don't seem to co-operate well with a dual monitor
  setup. If it is of any importance, my setup is a laptop with a TV
  plugged in via HDMI. So far I've found that VLC media player and
  Oracle Virtualbox won't play nicely with two monitors. When both
  monitors are in use, virtualbox crashes before it can open, and vlc
  tends to freeze the entire system, requiring a hard reboot. If I run
  these programs while only one monitor is being used and plug in the
  second one, they'll start misbehaving if moved to the other monitor.
  virtualbox and vlc will both become way too huge to be usable.

  Description:  Ubuntu 18.04.5 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7.1
Candidate: 1:7.7+19ubuntu7.1
Version table:
   *** 1:7.7+19ubuntu7.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+19ubuntu7 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55
  U

[Desktop-packages] [Bug 1896644] [NEW] Dual screen window size problem

2020-09-22 Thread Mitchell

Public bug reported:

Certain programs don't seem to co-operate well with a dual monitor
setup. If it is of any importance, my setup is a laptop with a TV
plugged in via HDMI. So far I've found that VLC media player and Oracle
Virtualbox won't play nicely with two monitors. When both monitors are
in use, virtualbox crashes before it can open, and vlc tends to freeze
the entire system, requiring a hard reboot. If I run these programs
while only one monitor is being used and plug in the second one, they'll
start misbehaving if moved to the other monitor. virtualbox and vlc will
both become way too huge to be usable.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.17
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 22 12:02:21 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8364]
InstallationDate: Installed on 2020-02-21 (214 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
MachineType: HP HP Pavilion Laptop 15-cc0xx
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-47-generic 
root=UUID=da68f1b9-ec5f-4962-8098-08f28713396e ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/03/2017
dmi.bios.vendor: Insyde
dmi.bios.version: F.13
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8364
dmi.board.vendor: HP
dmi.board.version: 46.23
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.13:bd11/03/2017:svnHP:pnHPPavilionLaptop15-cc0xx:pvrType1ProductConfigId:rvnHP:rn8364:rvr46.23:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-cc0xx
dmi.product.sku: 1KU17UA#ABA
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

** Attachment added: "Screen recordings of some of the issues"
   
https://bugs.launchpad.net/bugs/1896644/+attachment/5413216/+files/multiple-screen-problem.tar.xz

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

Title:
  Dual screen window size problem

Status in xorg package in Ubuntu:
  New

Bug description:
  Certain programs don't seem to co-operate well with a dual monitor
  setup. If it is of any importance, my setup is a laptop with a TV
  plugged in via HDMI. So far I've found that VLC media player and
  Oracle Virtualbox won't play nicely with two monitors. When both
  monitors are in use, virtualbox crashes before it can open, and vlc
  tends to freeze the entire system, requiring a hard reboot. If I run
  these programs while only one monitor is being used and plug in the
  second one, they'll start misbehaving if moved to the other monitor.
  virtualbox and vlc will both become way too huge to be usable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.4.0-47.51~18.04.1-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.17
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 22 12:02:21 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:8364]
  InstallationDate: Installed on 2020-02-21 (214 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  MachineType: HP HP Pavilion Laptop 15-cc0xx
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=

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

This bug was fixed in the package gdm3 - 3.36.3-0ubuntu0.20.04.1

---
gdm3 (3.36.3-0ubuntu0.20.04.1) focal; urgency=medium

  [ Iain Lane ]
  * New upstream release (LP: #1894874).
- Always use separate session bus for greeter sessions
  This runs dbus-run-session, so the binary needs to be available
- Chrome remote desktop fix
- Don't hardcode path to plymouth
- Fixes for when GDM isn't started on its configured initial VT (LP:
  #1845801)
- keyutils has a .pc file so use it
- User switching fix
  * debian/{control,gbp.conf}: Update for ubuntu/focal & upstream/3.36.x

  [ Simon McVittie ]
  * Add Depends on dbus, for dbus-run-session
  * Update symbols file.
This ignores a change to private symbols: gdm_find_display_session_for_uid
isn't declared in a public header, and nothing in Debian/Ubuntu seems to
call it.

 -- Iain Lane   Tue, 08 Sep 2020 18:01:39 +0100

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

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

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

Status in OEM Priority Project:
  Fix Committed
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-session package in Ubuntu:
  Invalid
Status in grub2 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Invalid
Status in gdm3 source package in Focal:
  Fix Released
Status in gnome-session source package in Focal:
  Invalid
Status in grub2 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-390 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-430 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-435 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Invalid

Bug description:
  [ Impact ]
  In some platforms with specific Nvidia cards (with nvidia-driver-440), enable 
auto-login (either during installation or after installation) will fail (either 
stuck in gdm login screen and not able to login even typing correct password).

  [ Test Case ]
  Here are two scenario of auto login with groovy (20.10) daily build[1]:

  1) Checked "Install third-party software" (e.g. nvidia-driver) with
  enabling "Login automatically" during installation.

  2) Install groovy daily build with default options, after installation 
completed:
  2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive.
  2.2) Enable "Login automatically" from system settings.

  Then reboot.

  [Expected result]
  System will boot into desktop environment without the login page.

  [Actual result]
  System boots to login page, and can't login to desktop environment with the 
correct password.

  [ Regression potential ]
  Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) 
to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] 
and it works good. It passed the 30 times reboot stress test by using 
stress/reboot_30 from checkbox.

  [1] sha256sum: 
bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822
  [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 
https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01
  [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801

  ---

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Mod

[Desktop-packages] [Bug 1845801] Update Released

The verification of the Stable Release Update for gdm3 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

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

Status in OEM Priority Project:
  Fix Committed
Status in gdm3 package in Ubuntu:
  Fix Released
Status in gnome-session package in Ubuntu:
  Invalid
Status in grub2 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-430 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-435 package in Ubuntu:
  Invalid
Status in nvidia-graphics-drivers-440 package in Ubuntu:
  Invalid
Status in gdm3 source package in Focal:
  Fix Released
Status in gnome-session source package in Focal:
  Invalid
Status in grub2 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-390 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-430 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-435 source package in Focal:
  Invalid
Status in nvidia-graphics-drivers-440 source package in Focal:
  Invalid

Bug description:
  [ Impact ]
  In some platforms with specific Nvidia cards (with nvidia-driver-440), enable 
auto-login (either during installation or after installation) will fail (either 
stuck in gdm login screen and not able to login even typing correct password).

  [ Test Case ]
  Here are two scenario of auto login with groovy (20.10) daily build[1]:

  1) Checked "Install third-party software" (e.g. nvidia-driver) with
  enabling "Login automatically" during installation.

  2) Install groovy daily build with default options, after installation 
completed:
  2.1) Install nvidia-driver-440 (450.66-0ubuntu1) from ubuntu-archive.
  2.2) Enable "Login automatically" from system settings.

  Then reboot.

  [Expected result]
  System will boot into desktop environment without the login page.

  [Actual result]
  System boots to login page, and can't login to desktop environment with the 
correct password.

  [ Regression potential ]
  Medium, the patch comes from upstream[2] to use /dev/tty1 (instead of tty0) 
to prevent the auto-login user gets tty1. I did verified gdm3 from my PPA[3] 
and it works good. It passed the 30 times reboot stress test by using 
stress/reboot_30 from checkbox.

  [1] sha256sum: 
bf4359114660504ad3f6fbde5e0c3edbc67a4101e4480f576d3cbd4f59acf822
  [2] https://gitlab.gnome.org/GNOME/gdm/-/commit/f843233ad4 
https://gitlab.gnome.org/GNOME/gdm/-/commit/690b3c01
  [3] https://launchpad.net/~os369510/+archive/ubuntu/gdm3-1845801

  ---

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 19:55:42 2019
  DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit()
  DistroCodename: eoan
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVID

[Desktop-packages] [Bug 1894874] Re: [SRU] New upstream release 3.36.3

This bug was fixed in the package gdm3 - 3.36.3-0ubuntu0.20.04.1

---
gdm3 (3.36.3-0ubuntu0.20.04.1) focal; urgency=medium

  [ Iain Lane ]
  * New upstream release (LP: #1894874).
- Always use separate session bus for greeter sessions
  This runs dbus-run-session, so the binary needs to be available
- Chrome remote desktop fix
- Don't hardcode path to plymouth
- Fixes for when GDM isn't started on its configured initial VT (LP:
  #1845801)
- keyutils has a .pc file so use it
- User switching fix
  * debian/{control,gbp.conf}: Update for ubuntu/focal & upstream/3.36.x

  [ Simon McVittie ]
  * Add Depends on dbus, for dbus-run-session
  * Update symbols file.
This ignores a change to private symbols: gdm_find_display_session_for_uid
isn't declared in a public header, and nothing in Debian/Ubuntu seems to
call it.

 -- Iain Lane   Tue, 08 Sep 2020 18:01:39 +0100

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

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

Title:
  [SRU] New upstream release 3.36.3

Status in gdm3 package in Ubuntu:
  Fix Released
Status in gdm3 source package in Focal:
  Fix Released

Bug description:
  [ Description ]

  We should ship the stable update for gdm3

  - Always use separate session bus for greeter sessions
  - Chrome remote desktop fix
  - Don't hardcode path to plymouth
  - Fixes for when GDM isn't started on its configured initial VT (bug 
1845801)
  - keyutils has a .pc file so use it
    This runs dbus-run-session, so the binary needs to be available
  - User switching fix

  We have a GNOME MRE so upstream's fixes don't need to be explicitly
  verified.

  [ QA ]

  Test:

  1. Regular login
  2. Auto-login
  3. Fast user switching
  4. X and Wayland
  5. Launching different sessions

  [ Regression potential ]

  It's the program which logs you in to your session - the consequences
  could be severe up to and including nobody being able to log in using
  gdm.

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

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

[Desktop-packages] [Bug 1896637] [NEW] system booting is too slow. Application like chrome, spotify, Libre Office, etc open too slow.

2020-09-22 Thread Rahul Kumar Singh

Public bug reported:

This OS(Ubuntu 20.04 LTS) installed in Lenovo v310-15ISK laptop. It has
4GB RAM and core i3 6th gen processor. The main issue is booting time
too slow about 3-4 minutes and all apps take time to open and sometimes
after long uptime when I poweroff, it freezes for sometime then start
shut down after 1-2 minutes.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 22 21:07:25 2020
DisplayManager: gdm3
RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  system booting is too slow. Application like chrome, spotify, Libre
  Office, etc  open too slow.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  This OS(Ubuntu 20.04 LTS) installed in Lenovo v310-15ISK laptop. It
  has 4GB RAM and core i3 6th gen processor. The main issue is booting
  time too slow about 3-4 minutes and all apps take time to open and
  sometimes after long uptime when I poweroff, it freezes for sometime
  then start shut down after 1-2 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 22 21:07:25 2020
  DisplayManager: gdm3
  RelatedPackageVersions: mutter-common 3.36.4-0ubuntu0.20.04.2
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896622] Re: scp-dbus-service.py crashed with SIGSEGV

2020-09-22 Thread Esokrates

Thanks, will this land in focal too?

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

Title:
  scp-dbus-service.py crashed with SIGSEGV

Status in system-config-printer package in Ubuntu:
  Fix Committed

Bug description:
  I printed something, afterwards I wanted to print again, but the printer did 
not receive the print job, so I cancelled the job and tried to start it yet 
again. Unfortunately it did not resolve the situation. 
  So I cancelled the print job and while at it, I changed the driver from 
driverless to hpcups to allow me a more precise paper selection.

  Afterwards I succeeded to print. Somewhere in the middle of all that a
  crash happened (this is the relevant excerpt of the .crash file after
  running apport-retrace):

  SegvAnalysis:
   Segfault happened at: 0x506bd7:  mov%rcx,(%rdx)
   PC (0x00506bd7) ok
   source "%rcx" ok
   destination "(%rdx)" (0x0004) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: system-config-printer
  Stacktrace:
   #0  0x00506bd7 in  ()
   #1  0x7fde3b6819f5 in _Py_DECREF (filename=, 
lineno=541, op=) at /usr/include/python3.8/object.h:478
   tls = 0x7fde30002ad0
   #2  _Py_XDECREF (op=) at /usr/include/python3.8/object.h:541
   tls = 0x7fde30002ad0
   #3  destroy_TLS (value=0x7fde30002ad0) at cupsmodule.c:67
   tls = 0x7fde30002ad0
   #4  0x7fde4c4795a1 in __nptl_deallocate_tsd () at pthread_create.c:301
   data = 
   level2 = 0x7fde3a3aba10
   idx = 
   cnt = 0
   #5  0x7fde4c47a62a in __nptl_deallocate_tsd () at pthread_create.c:256
   pd = 
   unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140592436393728, 
-3499183623227771153, 140724867734478, 140724867734479, 140724867734624, 
140592436391872, 3516206840480593647, 3516466368495417071}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
   not_first_call = 1
   #6  start_thread (arg=) at pthread_create.c:488
   pd = 
   unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140592436393728, 
-3499183623227771153, 140724867734478, 140724867734479, 140724867734624, 
140592436391872, 3516206840480593647, 3516466368495417071}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
   not_first_call = 1
   #7  0x7fde4c5b6103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  StacktraceAddressSignature: 
/usr/share/system-config-printer/scp-dbus-service.py:11:/usr/bin/python3.8+e3bd7:/usr/lib/python3/dist-packages/cups.cpython-38-x86_64-linux-gnu.so+19f5:/usr/lib/x86_64-linux-gnu/libpthread-2.31.so+15a1:/usr/lib/x86_64-linux-gnu/libpthread-2.31.so+262a:/usr/lib/x86_64-linux-gnu/libc-2.31.so+fd103
  StacktraceSource:
   #0  0x00506bd7 in  ()
   #1  0x7fde3b6819f5 in _Py_DECREF (filename=, 
lineno=541, op=) at /usr/include/python3.8/object.h:478
 [Error: object.h was not found in source tree]
   #2  _Py_XDECREF (op=) at /usr/include/python3.8/object.h:541
 [Error: object.h was not found in source tree]
   #3  destroy_TLS (value=0x7fde30002ad0) at cupsmodule.c:67
 [Error: cupsmodule.c was not found in source tree]
   #4  0x7fde4c4795a1 in __nptl_deallocate_tsd () at pthread_create.c:301
 [Error: pthread_create.c was not found in source tree]
   #5  0x7fde4c47a62a in __nptl_deallocate_tsd () at pthread_create.c:256
 [Error: pthread_create.c was not found in source tree]
   #6  start_thread (arg=) at pthread_create.c:488
 [Error: pthread_create.c was not found in source tree]
   #7  0x7fde4c5b6103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
 [Error: clone.S was not found in source tree]
   
  StacktraceTop:
   ()
   _Py_DECREF (filename=, lineno=541, op=) at 
/usr/include/python3.8/object.h:478
   _Py_XDECREF (op=) at /usr/include/python3.8/object.h:541
   destroy_TLS (value=0x7fde30002ad0) at cupsmodule.c:67
   __nptl_deallocate_tsd () at pthread_create.c:301
  Tags: focal wayland-session
  ThreadStacktrace:
   .
   Thread 5 (Thread 0x7fde489b8700 (LWP 55391)):
   warning: Unexpected size of section `.reg-xstate/55391' in core file.
   #0  0x7fde4c5a996f in __GI___poll (fds=0x233d3a0, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
   resultvar = 18446744073709551100
   sc_cancel_oldtype = 0
   #1  0x7fde4b8c21ae in g_main_context_poll (priority=, 
n_fds=1, fds=0x233d3a0, timeout=, context=0x233d500) at 
../../../glib/gmain.c:4346
   ret = 
   errsv = 
   poll_func = 0x7fde4b8d1f10 
   max_priority = 2147483647
   timeout = -1
   some_ready =

[Desktop-packages] [Bug 1896475] Re: [FFe] Migrate to pipewire-0.3

2020-09-22 Thread Iain Lane

** Changed in: xdg-desktop-portal-kde (Ubuntu)
   Status: New => Fix Released

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Status: New => Fix Released

** Changed in: xdg-desktop-portal (Ubuntu)
   Status: New => Fix Released

** Changed in: weston (Ubuntu)
   Status: New => Fix Released

** Changed in: pipewire (Ubuntu)
   Status: New => Fix Released

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

** Changed in: krfb (Ubuntu)
   Status: New => Fix Released

** Changed in: gnome-remote-desktop (Ubuntu)
   Status: New => Fix Released

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

Title:
  [FFe] Migrate to pipewire-0.3

Status in gnome-remote-desktop package in Ubuntu:
  Fix Released
Status in krfb package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Fix Released
Status in weston package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Fix Released
Status in xdg-desktop-portal-kde package in Ubuntu:
  Fix Released

Bug description:
  Various packages are now depending on pipewire-0.3 (or, in some cases
  pipewire-0.2).

  While this is not a main component for ubuntu (yet) we have various
  projects depending on it, and some core components (actually mutter)
  have a build-only-dependency on it.

  Debian already completed this migration some weeks ago, while ubuntu
  doesn't provide pipewire-0.3 yet and this can be blocking many
  components to land in next cycle.

  As per this, we thought that was wiser to anticipate the migration now
  so that all the dependencies will be already in ubuntu at the
  beginning of the next cycle, and we could start earlier the actual
  usage of pipewire in the desktop for mutter (and other components such
  as the xdg-portals).

  All the packages have been prepared already in:
   https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4265.1/+packages

  You can refer to the diffs in https://bileto.ubuntu.com/#/ticket/4265
  to see the details of the changes.

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

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

[Desktop-packages] [Bug 1896622] Re: scp-dbus-service.py crashed with SIGSEGV

2020-09-22 Thread Till Kamppeter

Thanks for the hint to https://github.com/OpenPrinting/system-config-
printer/issues/176. If this is actually the cause of your problem an
updated of the python3-cups (pycups) package should solve the problem. I
have synced version 2.0.1 from Debian into Ubuntu Groovy (20.10) now. As
soon as it arrives please test.

** Bug watch added: github.com/OpenPrinting/system-config-printer/issues #176
   https://github.com/OpenPrinting/system-config-printer/issues/176

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

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

Title:
  scp-dbus-service.py crashed with SIGSEGV

Status in system-config-printer package in Ubuntu:
  Fix Committed

Bug description:
  I printed something, afterwards I wanted to print again, but the printer did 
not receive the print job, so I cancelled the job and tried to start it yet 
again. Unfortunately it did not resolve the situation. 
  So I cancelled the print job and while at it, I changed the driver from 
driverless to hpcups to allow me a more precise paper selection.

  Afterwards I succeeded to print. Somewhere in the middle of all that a
  crash happened (this is the relevant excerpt of the .crash file after
  running apport-retrace):

  SegvAnalysis:
   Segfault happened at: 0x506bd7:  mov%rcx,(%rdx)
   PC (0x00506bd7) ok
   source "%rcx" ok
   destination "(%rdx)" (0x0004) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: system-config-printer
  Stacktrace:
   #0  0x00506bd7 in  ()
   #1  0x7fde3b6819f5 in _Py_DECREF (filename=, 
lineno=541, op=) at /usr/include/python3.8/object.h:478
   tls = 0x7fde30002ad0
   #2  _Py_XDECREF (op=) at /usr/include/python3.8/object.h:541
   tls = 0x7fde30002ad0
   #3  destroy_TLS (value=0x7fde30002ad0) at cupsmodule.c:67
   tls = 0x7fde30002ad0
   #4  0x7fde4c4795a1 in __nptl_deallocate_tsd () at pthread_create.c:301
   data = 
   level2 = 0x7fde3a3aba10
   idx = 
   cnt = 0
   #5  0x7fde4c47a62a in __nptl_deallocate_tsd () at pthread_create.c:256
   pd = 
   unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140592436393728, 
-3499183623227771153, 140724867734478, 140724867734479, 140724867734624, 
140592436391872, 3516206840480593647, 3516466368495417071}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
   not_first_call = 1
   #6  start_thread (arg=) at pthread_create.c:488
   pd = 
   unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140592436393728, 
-3499183623227771153, 140724867734478, 140724867734479, 140724867734624, 
140592436391872, 3516206840480593647, 3516466368495417071}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
   not_first_call = 1
   #7  0x7fde4c5b6103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  StacktraceAddressSignature: 
/usr/share/system-config-printer/scp-dbus-service.py:11:/usr/bin/python3.8+e3bd7:/usr/lib/python3/dist-packages/cups.cpython-38-x86_64-linux-gnu.so+19f5:/usr/lib/x86_64-linux-gnu/libpthread-2.31.so+15a1:/usr/lib/x86_64-linux-gnu/libpthread-2.31.so+262a:/usr/lib/x86_64-linux-gnu/libc-2.31.so+fd103
  StacktraceSource:
   #0  0x00506bd7 in  ()
   #1  0x7fde3b6819f5 in _Py_DECREF (filename=, 
lineno=541, op=) at /usr/include/python3.8/object.h:478
 [Error: object.h was not found in source tree]
   #2  _Py_XDECREF (op=) at /usr/include/python3.8/object.h:541
 [Error: object.h was not found in source tree]
   #3  destroy_TLS (value=0x7fde30002ad0) at cupsmodule.c:67
 [Error: cupsmodule.c was not found in source tree]
   #4  0x7fde4c4795a1 in __nptl_deallocate_tsd () at pthread_create.c:301
 [Error: pthread_create.c was not found in source tree]
   #5  0x7fde4c47a62a in __nptl_deallocate_tsd () at pthread_create.c:256
 [Error: pthread_create.c was not found in source tree]
   #6  start_thread (arg=) at pthread_create.c:488
 [Error: pthread_create.c was not found in source tree]
   #7  0x7fde4c5b6103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
 [Error: clone.S was not found in source tree]
   
  StacktraceTop:
   ()
   _Py_DECREF (filename=, lineno=541, op=) at 
/usr/include/python3.8/object.h:478
   _Py_XDECREF (op=) at /usr/include/python3.8/object.h:541
   destroy_TLS (value=0x7fde30002ad0) at cupsmodule.c:67
   __nptl_deallocate_tsd () at pthread_create.c:301
  Tags: focal wayland-session
  ThreadStacktrace:
   .
   Thread 5 (Thread 0x7fde489b8700 (LWP 55391)):
   warning: Unexpected size of section `.reg-xstate/55391' in core file.
   #

[Desktop-packages] [Bug 1662430] Re: GNOME Software doesn't offer to update a .deb if it's already installed

2020-09-22 Thread Albert Lee

This is occurring for me on focal with 3.36.1-0ubuntu0.20.04.0. It seems
to affect all deb packages.


** Attachment added: "Screenshot from 2020-09-22 10-29-58.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1662430/+attachment/5413202/+files/Screenshot%20from%202020-09-22%2010-29-58.png

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

Title:
  GNOME Software doesn't offer to update a .deb if it's already
  installed

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Dear all,

  Sometimes I do the following:

  1. I download a new .deb package that provides an updated version of a package
  2. I open this package with Ubuntu Software 3.20.
  3. However, it only shows me "Remove" or "Launch" but not "Upgrade"
  4. I can still correctly and properly upgrade the software in question from 
the terminal

  Please see the attached GIF as an example.

  The package I was trying to upgrade was this one:
  https://github.com/slgobinath/SafeEyes/releases

  Yours,

  Robert

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

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

[Desktop-packages] [Bug 1896627] [NEW] Windows flicker when being reized with the mouse

2020-09-22 Thread Sam Lane

Public bug reported:

When resizing a window with the mouse by dragging the edge or corner,
the window begins to flicker.  It only flickers when actively being
resized, and when I stop dragging, it looks normal.  This behavior is
does not occur on same pc in 20.04.

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
Uname: Linux 5.8.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu45
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: Budgie:GNOME
CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
Date: Tue Sep 22 10:21:51 2020
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
InstallationDate: Installed on 2020-09-22 (0 days ago)
InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 (20200921)
MachineType: LENOVO 20FJS0AJ00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2016
dmi.bios.release: 1.13
dmi.bios.vendor: LENOVO
dmi.bios.version: N1KET26W (1.13 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FJS0AJ00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.5
dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET26W(1.13):bd10/07/2016:br1.13:efr1.5:svnLENOVO:pn20FJS0AJ00:pvrThinkPadT560:rvnLENOVO:rn20FJS0AJ00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T560
dmi.product.name: 20FJS0AJ00
dmi.product.sku: LENOVO_MT_20FJ_BU_Think_FM_ThinkPad T560
dmi.product.version: ThinkPad T560
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.1.7-1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug groovy reproducible ubuntu

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

Title:
  Windows flicker when being reized with the mouse

Status in xorg package in Ubuntu:
  New

Bug description:
  When resizing a window with the mouse by dragging the edge or corner,
  the window begins to flicker.  It only flickers when actively being
  resized, and when I stop dragging, it looks normal.  This behavior is
  does not occur on same pc in 20.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read 
kernel buffer failed: Operation not permitted
  Date: Tue Sep 22 10:21:51 2020
  DistUpgraded: Fresh install
  DistroCodename: groovy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:2231]
  InstallationDate: Installed on 2020-09-22 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 20.10 "Groovy Gorilla" - Alpha amd64 
(20200921)
  MachineType: LENOVO 20FJS0AJ00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-18-generic 
root=UUID=72bd1806-98fb-4fa6-be5b-638dec36ebc9 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.release: 1.13
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET26W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS0AJ00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassi

[Desktop-packages] [Bug 1896622] [NEW] scp-dbus-service.py crashed with SIGSEGV

2020-09-22 Thread Esokrates

Public bug reported:

I printed something, afterwards I wanted to print again, but the printer did 
not receive the print job, so I cancelled the job and tried to start it yet 
again. Unfortunately it did not resolve the situation. 
So I cancelled the print job and while at it, I changed the driver from 
driverless to hpcups to allow me a more precise paper selection.

Afterwards I succeeded to print. Somewhere in the middle of all that a
crash happened (this is the relevant excerpt of the .crash file after
running apport-retrace):

SegvAnalysis:
 Segfault happened at: 0x506bd7:mov%rcx,(%rdx)
 PC (0x00506bd7) ok
 source "%rcx" ok
 destination "(%rdx)" (0x0004) not located in a known VMA region (needed 
writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: system-config-printer
Stacktrace:
 #0  0x00506bd7 in  ()
 #1  0x7fde3b6819f5 in _Py_DECREF (filename=, 
lineno=541, op=) at /usr/include/python3.8/object.h:478
 tls = 0x7fde30002ad0
 #2  _Py_XDECREF (op=) at /usr/include/python3.8/object.h:541
 tls = 0x7fde30002ad0
 #3  destroy_TLS (value=0x7fde30002ad0) at cupsmodule.c:67
 tls = 0x7fde30002ad0
 #4  0x7fde4c4795a1 in __nptl_deallocate_tsd () at pthread_create.c:301
 data = 
 level2 = 0x7fde3a3aba10
 idx = 
 cnt = 0
 #5  0x7fde4c47a62a in __nptl_deallocate_tsd () at pthread_create.c:256
 pd = 
 unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140592436393728, 
-3499183623227771153, 140724867734478, 140724867734479, 140724867734624, 
140592436391872, 3516206840480593647, 3516466368495417071}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
 not_first_call = 1
 #6  start_thread (arg=) at pthread_create.c:488
 pd = 
 unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140592436393728, 
-3499183623227771153, 140724867734478, 140724867734479, 140724867734624, 
140592436391872, 3516206840480593647, 3516466368495417071}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
 not_first_call = 1
 #7  0x7fde4c5b6103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
StacktraceAddressSignature: 
/usr/share/system-config-printer/scp-dbus-service.py:11:/usr/bin/python3.8+e3bd7:/usr/lib/python3/dist-packages/cups.cpython-38-x86_64-linux-gnu.so+19f5:/usr/lib/x86_64-linux-gnu/libpthread-2.31.so+15a1:/usr/lib/x86_64-linux-gnu/libpthread-2.31.so+262a:/usr/lib/x86_64-linux-gnu/libc-2.31.so+fd103
StacktraceSource:
 #0  0x00506bd7 in  ()
 #1  0x7fde3b6819f5 in _Py_DECREF (filename=, 
lineno=541, op=) at /usr/include/python3.8/object.h:478
   [Error: object.h was not found in source tree]
 #2  _Py_XDECREF (op=) at /usr/include/python3.8/object.h:541
   [Error: object.h was not found in source tree]
 #3  destroy_TLS (value=0x7fde30002ad0) at cupsmodule.c:67
   [Error: cupsmodule.c was not found in source tree]
 #4  0x7fde4c4795a1 in __nptl_deallocate_tsd () at pthread_create.c:301
   [Error: pthread_create.c was not found in source tree]
 #5  0x7fde4c47a62a in __nptl_deallocate_tsd () at pthread_create.c:256
   [Error: pthread_create.c was not found in source tree]
 #6  start_thread (arg=) at pthread_create.c:488
   [Error: pthread_create.c was not found in source tree]
 #7  0x7fde4c5b6103 in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
   [Error: clone.S was not found in source tree]
 
StacktraceTop:
 ()
 _Py_DECREF (filename=, lineno=541, op=) at 
/usr/include/python3.8/object.h:478
 _Py_XDECREF (op=) at /usr/include/python3.8/object.h:541
 destroy_TLS (value=0x7fde30002ad0) at cupsmodule.c:67
 __nptl_deallocate_tsd () at pthread_create.c:301
Tags: focal wayland-session
ThreadStacktrace:
 .
 Thread 5 (Thread 0x7fde489b8700 (LWP 55391)):
 warning: Unexpected size of section `.reg-xstate/55391' in core file.
 #0  0x7fde4c5a996f in __GI___poll (fds=0x233d3a0, nfds=1, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
 resultvar = 18446744073709551100
 sc_cancel_oldtype = 0
 #1  0x7fde4b8c21ae in g_main_context_poll (priority=, 
n_fds=1, fds=0x233d3a0, timeout=, context=0x233d500) at 
../../../glib/gmain.c:4346
 ret = 
 errsv = 
 poll_func = 0x7fde4b8d1f10 
 max_priority = 2147483647
 timeout = -1
 some_ready = 
 nfds = 1
 allocated_nfds = 
 fds = 0x233d3a0
 #2  g_main_context_iterate (context=context@entry=0x233d500, 
block=block@entry=1, dispatch=dispatch@entry=1, self=) at 
../../../glib/gmain.c:4042
 max_priority = 2147483647
 timeout = -1
 some_ready = 
 nfds = 1
 allocated_nfds = 
 fds = 0x233d3a0
 #3  0x7fde4b8c22e3 in g_main_context_iteration (context=0x233d500, 
may_block=1) at ../../../glib/gmain.c:4108

[Desktop-packages] [Bug 1893969] Re: Screen corruption and delayed update using onboard Intel video

2020-09-22 Thread Ethan Blanton

It happens for sure in the following applications (which I think rules
out the application and toolkit, but not the compositor or Xorg):

* Firefox
* Emacs
* Electron apps (Keybase, Slack, Element)
* Okular
* OBS (maybe; this may be a different problem)
* FreeCAD (maybe; FreeCAD has painting problems in general)
* VMware (both the UI and the guest)

Interestingly, I don't think I have seen any misbehavior in urxvt, which
I use a lot.

I am not using GNOME.  My window manager is awesome and my compositor is
compton.  The mutter package is not installed on this machine.

I will try to get more screen shots, although this is hard to capture
because disturbing the window often causes a repaint.  I have tried to
capture video a few times, but as I am working with private information
that does not belong to me on this machine I haven't yet captured an
instance where there was nothing on my screen I am unable to share.

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

Title:
  Screen corruption and delayed update using onboard Intel video

Status in mutter package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I frequently get screen corruption or delayed screen updates using
  onboard Intel video (i7-10710U in a Dell XPS 13 7390).  I am attaching
  a screen shot of an example of this in Emacs, where you can see echoes
  of past cursor locations (center right side of screen, the highlighted
  word "boolean").

  A frequent failure is that an application updates its window, but the
  updates do not appear on screen until I take some action to disturb
  the window (move or resize it, change focus, change desktops, etc.),
  after which it cleans itself up.  Small changes (such as selecting
  text) will often clean up the image where the change is made without
  repainting the entire window.

  My display panel is 4K UHD+, and I have attached two external Full HD
  DisplayPort monitors using chaining with 2x2 scale using XrandR.  This
  corruption appears to happen on all three surfaces.  The configuration
  for my desktop is:

  HIX=3840
  HIY=2160
  HI=${HIX}x${HIY}
  xrandr --fb $(($HIX * 3))x$HIY \
 --output eDP-1 --auto --panning ${HI}+$(($HIX * 2))+0 \
 --output DP-2-8 --auto --panning ${HI}+$HIX+0 \
 --scale-from $HI --left-of eDP-1 --scale 2x2 \
 --output DP-2-1 --auto --panning $HI+0+0 \
 --scale-from $HI --left-of DP-2-8 --scale 2x2

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop:
   
  Date: Wed Sep  2 11:48:03 2020
  DistUpgraded: 2020-06-21 15:36:52,619 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0962]
  MachineType: Dell Inc. XPS 13 7390
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic 
root=UUID=aeb9197c-491f-493d-9a7a-7094efd5023c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-06-21 (72 days ago)
  dmi.bios.date: 11/25/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.0
  dmi.board.name: 0377MH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 7390
  dmi.product.sku: 0962
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Desktop-packages] [Bug 1882644] Re: f2 doesn't engage rename files

This should be fixed by latest SRU in focal as well

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

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell-extension-desktop-icons (Ubuntu Groovy)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

Title:
  f2 doesn't engage rename files

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Focal:
  Fix Released
Status in gnome-shell-extension-desktop-icons source package in Groovy:
  Fix Released

Bug description:
  desktop
  select file
  hit  f2
  no popup asking for user to rename file

  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 20.04 LTS
  Release:  20.04
  Codename: focal

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

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

[Desktop-packages] [Bug 1801814] Re: Environment overwrites XDG_DATA_DIRS

** No longer affects: flatpak (Ubuntu Bionic)

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

Title:
  Environment overwrites XDG_DATA_DIRS

Status in flatpak package in Ubuntu:
  Fix Released
Status in flatpak source package in Focal:
  Fix Released

Bug description:
  [Impact]

  Flatpak gdm environment overwrites any custom configuration (eg in
  ~/.config/environment.d ) while using the Wayland session.

  
  [Test Case]

  Create a local environment configuration

  $ mkdir -p ~/.config/environment.d
  $ echo "XDG_DATA_DIRS=${XDG_DATA_DIRS}:/tmp" >> 
~/.config/environment.d/test.conf

  Reboot and ensure you use the Wayland session. Then check your
  XDG_DATA_DIRS from systemctl, the issue occurs when /tmp is not set,
  the issue is resolved if it is set.

  $ systemctl --user show-environment |grep XDG_DATA_DIRS

  
  [Regression Potential]

  Low. This only affects users using the Wayland session with a custom
  environment (which are both non-standard configuration).

  
  [Original Description]

  Package contains this file:

  /usr/share/gdm/env.d/flatpak.env

  With this single line content:

  
XDG_DATA_DIRS=$HOME/.local/share/flatpak/exports/share/:/var/lib/flatpak/exports/share/:/usr/local/share/:/usr/share/

  This is setting the XDG_DATA_DIRS variable, irrespective of it's
  preexisting value.

  In my system I have snapd installed and I have a local configuration
  for that variable under .config/environment.d/, which gets overwritten
  and causes issues.

  

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

  Description:  Ubuntu 18.10
  Release:  18.10

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

  flatpak:
    Installed: 1.0.4-1
    Candidate: 1.0.4-1
    Version table:
   *** 1.0.4-1 500
  500 http://ie.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
  100 /var/lib/dpkg/status

  3) What you expected to happen

  To have XDG_DATA_DIRS variable populated with the package's value as
  well as my own.

  4) What happened instead

  Only the configuration from flatpak's package survived.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: flatpak 1.0.4-1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Nov  6 00:55:32 2018
  InstallationDate: Installed on 2018-05-16 (173 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: flatpak
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (18 days ago)

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

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

[Desktop-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

2020-09-22 Thread Victor Bloetjes

Linux Mint 19.3 user and I can also confirm this bug.

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in PulseAudio:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  In Progress
Status in Arch Linux:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
  dmi.bios.date: 06/07/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R07ET67W (2.07 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FW000TUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40705 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T460p
  dmi.product.name: 20FW000TUS
  dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
  dmi.product.version: ThinkPad T460p
  dmi.sys.vendor: LENOVO

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

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

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

2020-09-22 Thread Andreas Hasenack

I meant, see *also* https://bugs.launchpad.net/bugs/1895302, no idea yet
if it's related.

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Triaged
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  k) Test that supporting changes for xenial are in place:

i) verify grub-legacy-ec2 is not in the xenial server seed
ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server

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

[Desktop-packages] [Bug 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)

2020-09-22 Thread Giacomo Tazzari

@paelzer I have an update.

After correctly applying the big fix on the guest too, the bug was still 
occurring but much more rarely.
But now, after I tried disabling Klipper (the KDE clipboard history manager) on 
both host and guest, the bug seems to have disappeared completely (and 
copy&paste still works fine, just without history).

I have yet to test what happens: if I keep Klipper disabled without any spice 
agent fix; and if I 
keep Klipper disabled but with the small fix.

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

Title:
  Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM
  guests)

Status in qemu package in Ubuntu:
  Invalid
Status in spice package in Ubuntu:
  Invalid
Status in spice-protocol package in Ubuntu:
  Fix Released
Status in spice-vdagent package in Ubuntu:
  Fix Released
Status in virt-manager package in Ubuntu:
  Invalid
Status in spice-protocol source package in Focal:
  Incomplete
Status in spice-vdagent source package in Focal:
  Incomplete
Status in spice-vdagent package in Debian:
  Fix Released
Status in spice package in Fedora:
  Unknown

Bug description:
  https://gitlab.freedesktop.org/spice/linux/vd_agent/issues/9

  ---

  I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta.

  I installed Kubuntu 20.04 and virt-manager as I did many times on
  Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt,
  libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest
  or with Ubuntu 20.04 guest then clipboard doesn't work right.

  To test it, please install Kubuntu 20.04 and then install Kubuntu /
  Ubuntu 20.04 as VM (guest). Open some simple text editor and start
  Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of
  time it won't.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: virt-manager 1:2.2.1-3ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
  Uname: Linux 5.4.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu26
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Mon Apr 13 15:02:22 2020
  InstallationDate: Installed on 2020-04-09 (4 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  PackageArchitecture: all
  SourcePackage: virt-manager
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896615] Re: package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1

2020-09-22 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package install-info 6.7.0.dfsg.2-5 failed to install/upgrade:
  installed install-info package post-installation script subprocess
  returned error exit status 1

Status in texinfo package in Ubuntu:
  New

Bug description:
  I was installing an update and it failed, I dont know why

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: install-info 6.7.0.dfsg.2-5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Sep 22 09:05:37 2020
  DuplicateSignature:
   package:install-info:6.7.0.dfsg.2-5
   Processing triggers for install-info (6.7.0.dfsg.2-5) ...
   Not a directory: INITIAL_ADMIN.
   dpkg: error processing package install-info (--configure):
installed install-info package post-installation script subprocess returned 
error exit status 1
  ErrorMessage: installed install-info package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-09-07 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: texinfo
  Title: package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: 
installed install-info package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1896577] Re: FFE: new upstream release 20.2 and migrate to llvm 11

2020-09-22 Thread Timo Aaltonen

** Changed in: mesa (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  FFE: new upstream release 20.2 and migrate to llvm 11

Status in mesa package in Ubuntu:
  New

Bug description:
  Mesa 20.2.0 has been delayed by upstream, but we still want it in
  20.10. It's currrently at rc4, final was supposed to be out a month
  ago. It's been in debian experimental since rc1.

  The packaging in debian also migrates to use llvm 11.

  packages for groovy are available on ppa:canonical-x/x-staging

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

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

[Desktop-packages] [Bug 1896615] [NEW] package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: installed install-info package post-installation script subprocess returned error exit status 1

2020-09-22 Thread Federico Alesandro

Public bug reported:

I was installing an update and it failed, I dont know why

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: install-info 6.7.0.dfsg.2-5
ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
Uname: Linux 5.4.0-47-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Sep 22 09:05:37 2020
DuplicateSignature:
 package:install-info:6.7.0.dfsg.2-5
 Processing triggers for install-info (6.7.0.dfsg.2-5) ...
 Not a directory: INITIAL_ADMIN.
 dpkg: error processing package install-info (--configure):
  installed install-info package post-installation script subprocess returned 
error exit status 1
ErrorMessage: installed install-info package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2020-09-07 (14 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: texinfo
Title: package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: installed 
install-info package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package install-info 6.7.0.dfsg.2-5 failed to install/upgrade:
  installed install-info package post-installation script subprocess
  returned error exit status 1

Status in texinfo package in Ubuntu:
  New

Bug description:
  I was installing an update and it failed, I dont know why

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: install-info 6.7.0.dfsg.2-5
  ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55
  Uname: Linux 5.4.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.8
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Sep 22 09:05:37 2020
  DuplicateSignature:
   package:install-info:6.7.0.dfsg.2-5
   Processing triggers for install-info (6.7.0.dfsg.2-5) ...
   Not a directory: INITIAL_ADMIN.
   dpkg: error processing package install-info (--configure):
installed install-info package post-installation script subprocess returned 
error exit status 1
  ErrorMessage: installed install-info package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2020-09-07 (14 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: texinfo
  Title: package install-info 6.7.0.dfsg.2-5 failed to install/upgrade: 
installed install-info package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1888575] Re: Split motd-news config into a new package

2020-09-22 Thread Andreas Hasenack

See https://bugs.launchpad.net/bugs/1895302

On Tue, Sep 22, 2020, 07:41 Oliver Grawert <1888...@bugs.launchpad.net>
wrote:

> please note that the stable UbuntuCore18 images regressed due to this:
>
> https://github.com/snapcore/core18/issues/170
>
> ** Bug watch added: github.com/snapcore/core18/issues #170
>https://github.com/snapcore/core18/issues/170
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1888575
>
> Title:
>   Split motd-news config into a new package
>
> Status in base-files package in Ubuntu:
>   Fix Released
> Status in livecd-rootfs package in Ubuntu:
>   Invalid
> Status in ubuntu-meta package in Ubuntu:
>   Fix Released
> Status in base-files source package in Xenial:
>   Fix Released
> Status in livecd-rootfs source package in Xenial:
>   Triaged
> Status in ubuntu-meta source package in Xenial:
>   Fix Committed
> Status in base-files source package in Bionic:
>   Fix Released
> Status in livecd-rootfs source package in Bionic:
>   Invalid
> Status in ubuntu-meta source package in Bionic:
>   Fix Released
> Status in base-files source package in Focal:
>   Fix Released
> Status in livecd-rootfs source package in Focal:
>   Invalid
> Status in ubuntu-meta source package in Focal:
>   Fix Released
> Status in base-files source package in Groovy:
>   Fix Released
> Status in livecd-rootfs source package in Groovy:
>   Invalid
> Status in ubuntu-meta source package in Groovy:
>   Fix Released
>
> Bug description:
>   [Impact]
>   The motd-news script is largely useless for desktop users, as they
> rarely login via a text console. It makes more sense for server users.
>
>   We can use package dependencies to have the motd-news script enabled on
> servers, but disabled on desktops, and still handle upgrades. This is the
> plan:
>   - move /etc/default/motd-news from base-files into a new binary package
> (motd-news-config, produced by src:base-files)
>   - have ubuntu-server depend on motd-news-config
>   - have base-files break current ubuntu-server, so that if base-files if
> upgraded and ubuntu-server is installed, ubuntu-server will also be
> upgraded to the new version which has the depends on motd-news-config
>
>   Care must be taken to preserve a changed /etc/default/motd-news when
>   the upgrade installs the new motd-news-config package. For example, on
>   a server that has set ENABLED=0 in /etc/default/motd-news and upgrades
>   to the new base-files and ubuntu-server, and gets the new motd-config-
>   news package, ENABLED=0 must remain set.
>
>   [Test Case]
>   a) base-files installed, ubuntu-server installed, unmodified
> /e/d/motd-news
>   apt install base-files
>   - upgrades ubuntu-server
>   - installs motd-news-config
>   - /e/d/motd-news remains, motd-news remains enabled
>
>   b) base-files installed, ubuntu-server installed, modified /e/d/motd-news
>   apt install base-files
>   - upgrades ubuntu-server
>   - installs motd-news-config
>   - /e/d/motd-news remains with the original modification
>
>   c) base-files installed, ubuntu-server not installed, unmodified
> /e/d/motd-news
>   apt install base-files
>   - upgrades base-files
>   - removes /e/d/motd-news
>   - motd-news is disabled
>
>   d) base-files installed, ubuntu-server not installed, modified
> /e/d/motd-news
>   apt install base-files
>   - upgrades base-files
>   - /e/d/motd-news gets renamed to backup
>   - motd-news is disabled
>
>   e) removing motd-news-config will also remove ubuntu-server (since
>   it's a depends, and not a recommends)
>
>   f) upgrading just ubuntu-server should pull motd-news-config in, and
>   force-upgrade base-files
>
>   g) Removing motd-news-server leaves /e/d/motd-news around; purging
>   motd-news-server removes the /e/d/motd-news config file
>
>   h) base-files installed, ubuntu-server installed, removed /e/d/motd-news
>   - apt install base-files
>   - upgrades base-files, upgrades ubuntu-server, installs motd-news-config
>   - /e/d/motd-news is installed with ENABLED=0
>
>   i) base-files installed, ubuntu-server NOT installed, removed
> e/d/motd-news
>   - apt install base-files
>   - base-files is upgraded
>   - no /e/d/motd-news is installed, motd-news remains disabled
>
>   j) Perform a release upgrade from the previous ubuntu release to the
>   one being tested while having ubuntu-server NOT installed (or use a
>   desktop install). At the end, motd-news should be disabled. Verify
>   with:
>
>   $ sudo /etc/update-motd.d/50-motd-news --force
>   $ (no output)
>
>   k) Test that supporting changes for xenial are in place:
>
> i) verify grub-legacy-ec2 is not in the xenial server seed
> ii) verify that the rootfs manifest built from the ubuntu-cpc project
> contains the ubuntu-server package
> iii) verify that images built from the ubuntu-cpc project which purge
> grub-legacy-ec2 have retained ubuntu-server
>
>   [Regression Potential]
>   This update is about config fil

[Desktop-packages] [Bug 1890716] Re: xdg-mime query filetype index.html reports wrong type

The wrapper used depends of the environment, the previous one was under
a command line clean instance, on a GNOME based desktop

$  XDG_UTILS_DEBUG_LEVEL=1 xdg-mime query filetype index.html
Running gio info "/tmp/index.html"
text/html

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

Title:
  xdg-mime query filetype index.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Incomplete

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions

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

[Desktop-packages] [Bug 1890716] Re: xdg-mime query filetype index.html reports wrong type

in fact the script doesn't seem to used shared-mime-info

$ XDG_UTILS_DEBUG_LEVEL=1 xdg-mime query filetype index.html
Running mimetype --brief --dereference "/tmp/index.html"
text/html

could you try to use the command with the same environement variable and
share the output?

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

Title:
  xdg-mime query filetype index.html reports wrong type

Status in shared-mime-info package in Ubuntu:
  Incomplete

Bug description:
  For .html files `xdg-mime` reports wrong type. The culprit is the
  `"use strict"` phrase which is used in JavaScript. It should not
  mistake .html files for anything else except of text/html !

  STEPS TO REPRODUCE:
  Run the following step by step in any folder:
  1. $ echo "\"use strict\"" > index.html
  2. $ xdg-mime query filetype index.html # -> application/x-perl - this should 
be text/html!

  Platform:
  Ubuntu 20.04.1 LTS (Focal Fossa)"
  Linux version 5.4.0-42-generic (buildd@lgw01-amd64-038) (gcc version 9.3.0 
(Ubuntu 9.3.0-10ubuntu2))

  xdg-utils: 1.1.3-2ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1890716/+subscriptions

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

[Desktop-packages] [Bug 1896405] Re: Cannot install libglib2.0-dev on ubuntu 20.04.1

Great that it worked out. The downgrade was trying to remove things
because libglib binaries need to be on the same version so it was
necessary to downgrade libglib2.0-bin/focal in addition to the main
library

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

Title:
  Cannot install  libglib2.0-dev on ubuntu 20.04.1

Status in glib2.0 package in Ubuntu:
  Invalid

Bug description:
  I already tried running `apt update/upgrade`, but it did not make any
  difference.

  Why these versions conflicts are happening?

  1. libglib2.0-bin : Conflicts: libglib2.0-bin:i386 but 2.64.2-1~fakesync1 is 
to be installed
  1. libglib2.0-bin:i386 : Conflicts: libglib2.0-bin but 2.64.3-1~ubuntu20.04.1 
is installed
  1. libglib2.0-dev : Depends: libglib2.0-0 (= 2.64.2-1~fakesync1) but 
2.64.3-1~ubuntu20.04.1 is installed
  1. libglib2.0-0 : Breaks: libglib2.0-0:i386 (!= 2.64.3-1~ubuntu20.04.1) but 
2.64.2-1~fakesync1 is to be installed
  1. libglib2.0-0:i386 : Breaks: libglib2.0-0 (!= 2.64.2-1~fakesync1) but 
2.64.3-1~ubuntu20.04.1 is installed

  ```
  $ sudo aptitude install libglib2.0-dev
  The following NEW packages will be installed:
gcc-10-base:i386{a} libblkid-dev{a} libblkid1:i386{a} libc6:i386{a} 
libcrypt1:i386{a} libelf1:i386{a} libffi-dev{a} libffi7:i386{a} 
libgcc-s1:i386{a} libglib2.0-0:i386{ab} 
libglib2.0-bin:i386{ab} libglib2.0-dev{b} libglib2.0-dev-bin{a} 
libidn2-0:i386{a} libmount-dev{a} libmount1:i386{a} libpcre2-8-0:i386{a} 
libpcre2-dev{a} libpcre2-posix2{a} 
libpcre3:i386{a} libselinux1:i386{a} libselinux1-dev{a} libsepol1-dev{a} 
libunistring2:i386{a} zlib1g:i386{a} 
  0 packages upgraded, 25 newly installed, 0 to remove and 0 not upgraded.

  Need to get 8.701 kB of archives. After unpacking 41,3 MB will be used.
  The following packages have unmet dependencies:
   libglib2.0-bin : Conflicts: libglib2.0-bin:i386 but 2.64.2-1~fakesync1 is to 
be installed
   libglib2.0-bin:i386 : Conflicts: libglib2.0-bin but 2.64.3-1~ubuntu20.04.1 
is installed
   libglib2.0-dev : Depends: libglib2.0-0 (= 2.64.2-1~fakesync1) but 
2.64.3-1~ubuntu20.04.1 is installed
   libglib2.0-0 : Breaks: libglib2.0-0:i386 (!= 2.64.3-1~ubuntu20.04.1) but 
2.64.2-1~fakesync1 is to be installed
   libglib2.0-0:i386 : Breaks: libglib2.0-0 (!= 2.64.2-1~fakesync1) but 
2.64.3-1~ubuntu20.04.1 is installed
  open: 2; closed: 4; defer: 0; conflict: 0

  The following actions will resolve these dependencies:

   Keep the following packages at their current version:
  1) libglib2.0-0:i386 [Not Installed]  
  2) libglib2.0-bin:i386 [Not Installed]
  3) libglib2.0-dev [Not Installed] 

  Accept this solution? [Y/n/q/?] y
  No packages will be installed, upgraded, or removed.
  0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  Need to get 0 B of archives. After unpacking 0 B will be used.
  ```

  ```
  $ cat /etc/os-release 
  NAME="Ubuntu"
  VERSION="20.04.1 LTS (Focal Fossa)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu 20.04.1 LTS"
  VERSION_ID="20.04"
  HOME_URL="https://www.ubuntu.com/";
  SUPPORT_URL="https://help.ubuntu.com/";
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/";
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy";
  VERSION_CODENAME=focal
  UBUNTU_CODENAME=focal
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1896405/+subscriptions

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

[Desktop-packages] [Bug 1896581] Re: file-roller not operate .rar archice when rar and unrar is updated to 5.91

Thank you for your bug report but the Ubuntu packages aren't meant to
work with any random binary installation, if you install a local copy of
tools then you are the one that need to sort out their integration

** Changed in: file-roller (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: file-roller (Ubuntu)
   Status: New => Invalid

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

Title:
  file-roller not operate .rar archice when rar and unrar is updated  to
  5.91

Status in file-roller package in Ubuntu:
  Invalid

Bug description:
  I just removed the old rar and unrar which is provided by apt/apt-get
  and installed latest rar and unrar from their website extracted it and
  install in /usr/local/bin/unrar. Works fine in terminal. But the file-
  roller lose capability. Please provide a fix. As in terminal rar is
  working just normal but in file-roller it breaks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1896581/+subscriptions

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

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

2020-09-22 Thread Oliver Grawert

please note that the stable UbuntuCore18 images regressed due to this:

https://github.com/snapcore/core18/issues/170

** Bug watch added: github.com/snapcore/core18/issues #170
   https://github.com/snapcore/core18/issues/170

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

Title:
  Split motd-news config into a new package

Status in base-files package in Ubuntu:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Released
Status in livecd-rootfs source package in Xenial:
  Triaged
Status in ubuntu-meta source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Released
Status in livecd-rootfs source package in Bionic:
  Invalid
Status in ubuntu-meta source package in Bionic:
  Fix Released
Status in base-files source package in Focal:
  Fix Released
Status in livecd-rootfs source package in Focal:
  Invalid
Status in ubuntu-meta source package in Focal:
  Fix Released
Status in base-files source package in Groovy:
  Fix Released
Status in livecd-rootfs source package in Groovy:
  Invalid
Status in ubuntu-meta source package in Groovy:
  Fix Released

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  k) Test that supporting changes for xenial are in place:

i) verify grub-legacy-ec2 is not in the xenial server seed
ii) verify that the rootfs manifest built from the ubuntu-cpc project 
contains the ubuntu-server package
iii) verify that images built from the ubuntu-cpc project which purge 
grub-legacy-ec2 have retained ubuntu-server

  [Regression Potential]
  This update is about config file ownership transfer: /e/d/motd-news belonged 
to base-files, now it belongs to motd-news-config. We tried to handle two 
important cases here:
  a) /e/d/motd-news config was changed while it belonged to base-files. For 
example, an user could have set ENABLED=0. We need to transfer that change to 
the motd-news-

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

2020-09-22 Thread Felix Raynaud

Just a small contribution from my side: the bug is not fixed despite all
the latest updates. I'm having a Quadro K5200 with proprietary drivers
v440.100 on Ubuntu 20.04 and both fractional scaling (on one monitor)
and normal/fractional scaling on multiple monitors with different
scaling are broken.

I tried with the latest driver from the ppa:graphics-drivers/ppa
repository, no help there. I confirm that scaling is working with the
nouveau driver, but this is not a solution for me since I need features
like CUDA, opencl or compatibility with VMWare 3D acceleration.

No luck with all 3 ways to set the scaling: Gnome control center, xrandr
or nvidia-settings. I cannot contribute to the fix itself, but if more
details on my configuration is needed, feel free to ask.

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

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

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

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

2.
Select the screen setup in gnome control center

3.
Click the "Fractional scaling" toggle

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

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

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

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

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

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

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

[Desktop-packages] [Bug 1839380] Re: Nautilus freezes when restoring files and a copy already exists