[Desktop-packages] [Bug 2060814] Re: dist-upgrade in noble fails when using TPM FDE

2024-04-10 Thread Ken VanDine
Yes, classic deb based ubuntu utilizing TPM FDE does use a snapped
kernel.  In fact, it boots ubuntu-core and pivots to classic.

ken@t14:~$ df -h /lib/firmware/
Filesystem  Size  Used Avail Use% Mounted on
/dev/loop1  328M  328M 0 100% /snap/pc-kernel/1669


** Changed in: foo2zjs (Ubuntu)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  dist-upgrade in noble fails when using TPM FDE

Status in foo2zjs package in Ubuntu:
  New

Bug description:
  When doing a dist-upgrade of noble during the devel cycle I'm hitting
  this upgrade bug in the package.  /lib/firmware is read-only because
  it's provided by the pc-kernel snap.

  
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
libpoppler134 poppler-utils
  The following packages will be upgraded:
printer-driver-foo2zjs
  1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
  416 not fully installed or removed.
  Need to get 0 B/142 kB of archives.
  After this operation, 12.3 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 140132 files and directories currently installed.)
  Preparing to unpack 
.../printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb ...
  Unpacking printer-driver-foo2zjs (20200505dfsg0-2ubuntu5) over 
(20200505dfsg0-2ubuntu3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb 
(--unpack)
  :
   error creating directory './lib/firmware/hp': Read-only file system
  dpkg: error while cleaning up:
   unable to remove newly-extracted version of '/lib/firmware/hp': Read-only 
file system
  Errors were encountered while processing:
   
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: printer-driver-foo2zjs 20200505dfsg0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 10 09:39:01 2024
  InstallationDate: Installed on 2024-03-08 (33 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: foo2zjs
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 2060814] [NEW] dist-upgrade in noble fails when using TPM FDE

2024-04-10 Thread Ken VanDine
Public bug reported:

When doing a dist-upgrade of noble during the devel cycle I'm hitting
this upgrade bug in the package.  /lib/firmware is read-only because
it's provided by the pc-kernel snap.


Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libpoppler134 poppler-utils
The following packages will be upgraded:
  printer-driver-foo2zjs
1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
416 not fully installed or removed.
Need to get 0 B/142 kB of archives.
After this operation, 12.3 kB of additional disk space will be used.
Do you want to continue? [Y/n] 
(Reading database ... 140132 files and directories currently installed.)
Preparing to unpack .../printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb 
...
Unpacking printer-driver-foo2zjs (20200505dfsg0-2ubuntu5) over 
(20200505dfsg0-2ubuntu3) ...
dpkg: error processing archive 
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb 
(--unpack)
:
 error creating directory './lib/firmware/hp': Read-only file system
dpkg: error while cleaning up:
 unable to remove newly-extracted version of '/lib/firmware/hp': Read-only file 
system
Errors were encountered while processing:
 /var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: printer-driver-foo2zjs 20200505dfsg0-2ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Wed Apr 10 09:39:01 2024
InstallationDate: Installed on 2024-03-08 (33 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: foo2zjs
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  dist-upgrade in noble fails when using TPM FDE

Status in foo2zjs package in Ubuntu:
  New

Bug description:
  When doing a dist-upgrade of noble during the devel cycle I'm hitting
  this upgrade bug in the package.  /lib/firmware is read-only because
  it's provided by the pc-kernel snap.

  
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
libpoppler134 poppler-utils
  The following packages will be upgraded:
printer-driver-foo2zjs
  1 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
  416 not fully installed or removed.
  Need to get 0 B/142 kB of archives.
  After this operation, 12.3 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  (Reading database ... 140132 files and directories currently installed.)
  Preparing to unpack 
.../printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb ...
  Unpacking printer-driver-foo2zjs (20200505dfsg0-2ubuntu5) over 
(20200505dfsg0-2ubuntu3) ...
  dpkg: error processing archive 
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb 
(--unpack)
  :
   error creating directory './lib/firmware/hp': Read-only file system
  dpkg: error while cleaning up:
   unable to remove newly-extracted version of '/lib/firmware/hp': Read-only 
file system
  Errors were encountered while processing:
   
/var/cache/apt/archives/printer-driver-foo2zjs_20200505dfsg0-2ubuntu5_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: printer-driver-foo2zjs 20200505dfsg0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 10 09:39:01 2024
  InstallationDate: Installed on 2024-03-08 (33 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240306)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: foo2zjs
  UpgradeStatus: No upgrade log present (probably fresh install)

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


-- 
Mailing list: 

[Desktop-packages] [Bug 2056506] Re: GNOME Shell crashes when I close any application by right click in the dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL) from ubuntu-d...@ubunt

2024-03-10 Thread Ken VanDine
I just did a clean install of noble and I'm hitting the crash pretty
regularly.  Or at least what looks like the same crash.

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

Title:
  GNOME Shell crashes when I close any application by right click in the
  dock [clutter_actor_dispose: assertion failed: (priv->parent == NULL)
  from ubuntu-d...@ubuntu.com/windowPreview.js:642]

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

Bug description:
  I'm using Noble for sometime and I'm having a very annoying and odd
  problem: everytime I close an application on x11 (Wayland doesn't work
  any better) clicking with the right button in the dock and choosing
  "Quit" I got that screen saying that something went wrong and I need
  to close the session and start over. Please, let me know what logs do
  you need. I couldn't find any meaningful information by myself.

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


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


[Desktop-packages] [Bug 2025447] Re: Incorrect Downloads directory for LDAP user in snapped firefox & chromium

2023-09-05 Thread Ken VanDine
The getent implementation pre-dates the existence of SNAP_REAL_HOME.  We
can probably leverage that.

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

Title:
  Incorrect Downloads directory for LDAP user in snapped firefox &
  chromium

Status in Snapcraft:
  New
Status in snapd:
  New
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  Test procedure:
  1. Log in to Gnome as a Active Directory user.
  2. Launch browser (firefox or chrome) - make sure there's no existing config 
(we are interested in the default Downloads location).
  3. Download a file via the browser.
  4. Check where it was downloaded.

  Expected result:
  The files are downloaded to ~/Downloads (or a translated equivalent).

  Actual result:
  The files are downloaded to:
  ~/snap/firefox/common/Downloads
  ~/snap/chromium/current/Downloads

  For local users the behavior is as expected (all files are downloaded
  to ~/Downloads).

  This is very inconvenient for enterprise environments where manual
  setting modification is needed on every host.

  This has been tested on 22.04 with the following versions:
  - firefox (116.0.3 Mozilla Firefox Snap for Ubuntu canonical-002 - 1.0)
  - chromium (Version 116.0.5845.110 (Official Build) snap (64-bit))
  - snapd 2.58+22.04.1

  [1] https://ubuntu.com/server/docs/service-sssd-ad

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


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


[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-06-12 Thread Ken VanDine
** Also affects: evince (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: apparmor (Ubuntu Lunar)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Confirmed
Status in apparmor source package in Jammy:
  Confirmed
Status in evince source package in Jammy:
  Confirmed
Status in apparmor source package in Lunar:
  Confirmed
Status in evince source package in Lunar:
  Confirmed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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


[Desktop-packages] [Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap

2023-06-12 Thread Ken VanDine
** Changed in: evince (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: evince (Ubuntu Jammy)
   Status: Incomplete => Confirmed

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

Title:
  Clicking a hyperlink in a PDF fails to open it if the default browser
  is a snap

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  Confirmed
Status in apparmor source package in Jammy:
  Confirmed
Status in evince source package in Jammy:
  Confirmed
Status in evince package in Debian:
  Confirmed

Bug description:
  [Impact]

   * Users cannot open a hyperlink in a PDF opened with evince when the default 
browser is a snap.
   * The fix creates a snap_browsers abstraction on AppArmor which can be used 
in a transition for when the browser is executed. The snap_browsers abstraction 
provides the minimal amount of permissions required to execute a browser 
provided through snaps. This is a workaround since AppArmor currently does not 
provide mediation/filtering on enhanced environment variables.

  [Test Plan]

   * Make sure the default browser is provided through the snap store.
   * Open a PDF that contains a hyperlink using evince and click on the URL.
   * The browser should open the requested URL. 

  [Where problems could occur]

   * If the browser or snap core update to have new requirements for
  opening a browser, then the current policy could become obsolete and
  will need to be updated again.

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


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


[Desktop-packages] [Bug 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m

2023-04-13 Thread Ken VanDine
Another crash file generated with waking from suspend

** Attachment added: "_usr_bin_gnome-shell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+attachment/5663843/+files/_usr_bin_gnome-shell.1000.crash

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

Title:
  gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid
  parameter attributes)'. (Details: serial  error_code 8
  request_code 131 (XInputExtension) minor_code 57)]

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Apr  2 01:49:43 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2023-03-30 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago)
  UserGroups: N/A
  separator:

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


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


[Desktop-packages] [Bug 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m

2023-04-13 Thread Ken VanDine
Another crash file from gnome-shell running as gdm

** Attachment added: "_usr_bin_gnome-shell.120.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+attachment/5663835/+files/_usr_bin_gnome-shell.120.crash

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

Title:
  gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid
  parameter attributes)'. (Details: serial  error_code 8
  request_code 131 (XInputExtension) minor_code 57)]

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Apr  2 01:49:43 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2023-03-30 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago)
  UserGroups: N/A
  separator:

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


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


[Desktop-packages] [Bug 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m

2023-04-13 Thread Ken VanDine
Another crash file from what appears to be from the gdm instance of
gnome-shell

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

Title:
  gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid
  parameter attributes)'. (Details: serial  error_code 8
  request_code 131 (XInputExtension) minor_code 57)]

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Apr  2 01:49:43 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2023-03-30 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago)
  UserGroups: N/A
  separator:

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


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


[Desktop-packages] [Bug 2014986] Re: gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid parameter attributes)'. (Details: serial xxxx error_code 8 request_code 131 (XInputExtension) m

2023-04-13 Thread Ken VanDine
I added MUTTER_SYNC=1 to my environment and got the attached crash file

** Attachment added: "_usr_bin_gnome-shell.1000.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2014986/+attachment/5663801/+files/_usr_bin_gnome-shell.1000.crash

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

Title:
  gnome-shell crashed with signal 5 [The error was 'BadMatch (invalid
  parameter attributes)'. (Details: serial  error_code 8
  request_code 131 (XInputExtension) minor_code 57)]

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in xserver-xorg-input-libinput package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/53564230b4b22425c80ba6615ecceab429c477e4

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Sun Apr  2 01:49:43 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2023-03-30 (2 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcCmdline: /usr/bin/gnome-shell
  RelatedPackageVersions: mutter-common 44.0-2ubuntu2
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: Upgraded to lunar on 2023-04-01 (0 days ago)
  UserGroups: N/A
  separator:

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


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


[Desktop-packages] [Bug 2016191] [NEW] gnome-shell crashed with signal 5 in _XEventsQueued()

2023-04-13 Thread Ken VanDine
*** This bug is a duplicate of bug 2014986 ***
https://bugs.launchpad.net/bugs/2014986

Public bug reported:

I'm seeing this crash on each login after a fresh install of 23.04.

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gnome-shell 44.0-2ubuntu3
ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
Uname: Linux 6.2.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: GNOME-Greeter:GNOME
Date: Thu Apr 13 19:06:05 2023
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:
 
InstallationDate: Installed on 2023-04-10 (3 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
ProcCmdline: /usr/bin/gnome-shell
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/false
 XDG_RUNTIME_DIR=
RelatedPackageVersions: mutter-common 44.0-2ubuntu3
Signal: 5
SourcePackage: gnome-shell
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /lib/x86_64-linux-gnu/libX11.so.6
 g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: gnome-shell crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
separator:

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


** Tags: amd64 apport-crash lunar

** Information type changed from Private 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 gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/2016191

Title:
  gnome-shell crashed with signal 5 in _XEventsQueued()

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  I'm seeing this crash on each login after a fresh install of 23.04.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 44.0-2ubuntu3
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Thu Apr 13 19:06:05 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
   
  InstallationDate: Installed on 2023-04-10 (3 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/false
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 44.0-2ubuntu3
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: gnome-shell crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  separator:

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


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


[Desktop-packages] [Bug 2013144] [NEW] gjs-console crashed with SIGABRT in g_assertion_message_expr()

2023-03-28 Thread Ken VanDine
*** This bug is a duplicate of bug 2012287 ***
https://bugs.launchpad.net/bugs/2012287

Public bug reported:

I don't know what triggered this crash report, but filing it here
anyway.

ProblemType: Crash
DistroRelease: Ubuntu 23.04
Package: gjs 1.75.90-1
ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
Uname: Linux 6.2.0-18-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Mar 28 22:12:21 2023
ExecutablePath: /usr/bin/gjs-console
ExecutableTimestamp: 1678210639
InstallationDate: Installed on 2023-03-29 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters 
--gapplication-service
ProcCwd: /home/ken
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
Signal: 6
SourcePackage: gjs
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
 g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
Title: gjs-console crashed with SIGABRT in g_assertion_message_expr()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sudo users
separator:

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


** Tags: amd64 apport-crash lunar wayland-session

** Information type changed from Private to Public

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

Title:
  gjs-console crashed with SIGABRT in g_assertion_message_expr()

Status in gjs package in Ubuntu:
  New

Bug description:
  I don't know what triggered this crash report, but filing it here
  anyway.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: gjs 1.75.90-1
  ProcVersionSignature: Ubuntu 6.2.0-18.18-generic 6.2.6
  Uname: Linux 6.2.0-18-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Mar 28 22:12:21 2023
  ExecutablePath: /usr/bin/gjs-console
  ExecutableTimestamp: 1678210639
  InstallationDate: Installed on 2023-03-29 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230328)
  ProcCmdline: /usr/bin/gjs-console /usr/bin/gnome-characters 
--gapplication-service
  ProcCwd: /home/ken
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Signal: 6
  SourcePackage: gjs
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgtk-4.so.1
   g_object_unref () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgjs.so.0
  Title: gjs-console crashed with SIGABRT in g_assertion_message_expr()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

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


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


[Desktop-packages] [Bug 2009886] [NEW] gnome-initial-setup uses wrong name and icon

2023-03-09 Thread Ken VanDine
Public bug reported:

In Lunar the icon displayed while gnome-initial-setup is missing and the
name displayed in the panel isn't set.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: gnome-initial-setup 44~beta-0ubuntu1
ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
Uname: Linux 6.1.0-16-generic x86_64
ApportVersion: 2.26.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  9 14:37:23 2023
InstallationDate: Installed on 2023-03-09 (0 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230309)
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
SourcePackage: gnome-initial-setup
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-initial-setup (Ubuntu)
 Importance: High
 Assignee: Jeremy Bícha (jbicha)
 Status: Confirmed


** Tags: amd64 apport-bug lunar rls-ll-incoming wayland-session

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

Title:
  gnome-initial-setup uses wrong name and icon

Status in gnome-initial-setup package in Ubuntu:
  Confirmed

Bug description:
  In Lunar the icon displayed while gnome-initial-setup is missing and
  the name displayed in the panel isn't set.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-initial-setup 44~beta-0ubuntu1
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  9 14:37:23 2023
  InstallationDate: Installed on 2023-03-09 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230309)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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


[Desktop-packages] [Bug 1991263] Re: duplicate appindicators

2022-09-29 Thread Ken VanDine
** Changed in: gnome-shell-extension-appindicator (Ubuntu Jammy)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu Jammy)
   Importance: Undecided => High

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

Title:
  duplicate appindicators

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Jammy:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Kinetic:
  Confirmed

Bug description:
  I'm seeing duplicate appindicators for snaps built with core22, like
  mattermost-desktop and discord.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell-extension-appindicator 42-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 29 09:46:07 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (863 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (29 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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


[Desktop-packages] [Bug 1991263] [NEW] duplicate appindicators

2022-09-29 Thread Ken VanDine
Public bug reported:

I'm seeing duplicate appindicators for snaps built with core22, like
mattermost-desktop and discord.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell-extension-appindicator 42-3ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Sep 29 09:46:07 2022
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
InstallationDate: Installed on 2020-05-18 (863 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: gnome-shell-extension-appindicator
UpgradeStatus: Upgraded to kinetic on 2022-08-30 (29 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

** Affects: gnome-shell-extension-appindicator (Ubuntu)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed

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

** Affects: gnome-shell-extension-appindicator (Ubuntu Kinetic)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed


** Tags: amd64 apport-bug kinetic third-party-packages wayland-session

** Attachment added: "unknown.png"
   
https://bugs.launchpad.net/bugs/1991263/+attachment/5620013/+files/unknown.png

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu)
   Importance: Undecided => High

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

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

** Also affects: gnome-shell-extension-appindicator (Ubuntu Kinetic)
   Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Confirmed

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

Title:
  duplicate appindicators

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-appindicator source package in Jammy:
  New
Status in gnome-shell-extension-appindicator source package in Kinetic:
  Confirmed

Bug description:
  I'm seeing duplicate appindicators for snaps built with core22, like
  mattermost-desktop and discord.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell-extension-appindicator 42-3ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 29 09:46:07 2022
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (863 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (29 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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


[Desktop-packages] [Bug 1988315] Re: gnome-shell crashed with SIGABRT [Clutter:ERROR:../clutter/clutter/clutter-actor.c:11749:clutter_actor_destroy_all_children: assertion failed: (self->priv->n_child

2022-09-06 Thread Ken VanDine
I've tried removing them all, and still seeing the crash.  Of interest
though, it looks like only some apps using the indicator are triggering
the crash.  For example, starting mattermost-desktop or discord triggers
the crash when it registers the appindicator.  But starting telegram-
desktop doesn't.  Perhaps something about the libappindicator being
utilized?  telegram-desktop isn't using the content snap.

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

Title:
  gnome-shell crashed with SIGABRT
  [Clutter:ERROR:../clutter/clutter/clutter-
  actor.c:11749:clutter_actor_destroy_all_children: assertion failed:
  (self->priv->n_children < prev_n_children)] in
  indicatorStatusIcon.js:317

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to kinetic gnome-shell is crashing on start when using
  wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 10:28:31 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (834 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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


[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2022-09-02 Thread Ken VanDine
@vanvugt actually my issue must have been different, I'm not using
mirror mode and it was happening to me without an external display (as
well as with).  The workaround did work though.

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

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

Status in GNOME Shell:
  New
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

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


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


[Desktop-packages] [Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2022-09-02 Thread Ken VanDine
@vanvugt actually my issue must have been different, I'm not using
mirror mode and it was happening to me without an external display (as
well as with).  The workaround did work though.

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

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

Status in GNOME Shell:
  New
Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  (initially reported as a comment on bug #1965085, and split into a
  separate bug report)

  After I lock my screen and let it blank, moving the mouse or pressing
  any key on the keyboard won't wake it up. The only reliable workaround
  I've found is to press Ctrl+Alt+F1.

  That's on a fully up-to-date jammy, my hardware is an Intel NUC with a
  single Samsung monitor connected with a standard HDMI cable. This is a
  regression that started happening yesterday (2022-04-05) if I can
  remember correctly (I do apply pending updates at least once daily).

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gdm3 42.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr  6 15:19:30 2022
  InstallationDate: Installed on 2020-09-16 (566 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200910)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to jammy on 2022-03-19 (17 days ago)

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


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


[Desktop-packages] [Bug 1988315] Re: gnome-shell crash with wayland on kinetic

2022-08-31 Thread Ken VanDine
I tried disabling the system extensions and logging in again, which did
work.  I was able to reenable them all and gnome-shell was still working
again.  Then of interest, launching an app that uses an appindicator
caused the shell to crash.  I can reliably reproduce this, the
appindicator extension is triggering the crash.  It happens when an app
registers with the indicator, which I have slack and mattermost set to
autostart on login, which in turns triggers my crash at start.

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

Title:
  gnome-shell crash with wayland on kinetic

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading to kinetic gnome-shell is crashing on start when using
  wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 10:28:31 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (834 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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


[Desktop-packages] [Bug 1988315] [NEW] gnome-shell crash with wayland on kinetic

2022-08-31 Thread Ken VanDine
Public bug reported:

After upgrading to kinetic gnome-shell is crashing on start when using
wayland.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gnome-shell 43~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
Uname: Linux 5.15.0-46-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.23.0-0ubuntu1
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 31 10:28:31 2022
DisplayManager: gdm3
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
InstallationDate: Installed on 2020-05-18 (834 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago)
modified.conffile..etc.default.apport: [modified]
mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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

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

Title:
  gnome-shell crash with wayland on kinetic

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  After upgrading to kinetic gnome-shell is crashing on start when using
  wayland.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43~beta-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39
  Uname: Linux 5.15.0-46-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 31 10:28:31 2022
  DisplayManager: gdm3
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-sutton-bionic-amd64-20200511-23+sutton-knuth-bionic-amd64+iso
  InstallationDate: Installed on 2020-05-18 (834 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20200511-12:31
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43~beta-3ubuntu2
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-08-30 (0 days ago)
  modified.conffile..etc.default.apport: [modified]
  mtime.conffile..etc.default.apport: 2020-05-11T08:18:53

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


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


[Desktop-packages] [Bug 1969303] Re: "No package to remove" error when attempting to uninstall

2022-05-02 Thread Ken VanDine
** Changed in: snap-store-desktop
   Status: Fix Committed => Fix Released

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Unknown
Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in gnome-software source package in Jammy:
  Triaged

Bug description:
  On a fresh install of Ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a software, there is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

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


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


[Desktop-packages] [Bug 1967121] Re: Dock auto-hides while right click context menus are open

2022-04-29 Thread Ken VanDine
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => High

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

Title:
  Dock auto-hides while right click context menus are open

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

Bug description:
  Currently testing a fresh install of the beta for 22.04.
  All packages are up to date.

  When having the dock auto-hide option enabled, a glitch occurs when opening 
the windows selector (when multiple instances of the same program are opened).
  The selector does open, but the dock will hide itself immediately instead of 
waiting for a selection. Selecting a window will then cause a glitch where the 
selector will align with the hidden dock in a non natural way before 
disappearing.

  A proposed fix would be to prevent the dock from auto-hiding when the
  miniatures selector opens and wait for a second input.

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


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


[Desktop-packages] [Bug 1970248] Re: .deb files open with Archive Manager by default

2022-04-25 Thread Ken VanDine
defaults.list is referencing the correct desktop file.  It's installed
in /var/lib/snapd/desktop/applications/snap-store_ubuntu-software-local-
file.desktop

I don't know why it's not the default though, perhaps alphabetical in
the picker?

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

Title:
  .deb files open with Archive Manager by default

Status in snap-store-desktop:
  Triaged
Status in desktop-file-utils package in Ubuntu:
  Triaged
Status in desktop-file-utils source package in Jammy:
  Triaged

Bug description:
  Impact
  --
  Someone who downloads a .deb file usually wants to install the .deb when they 
open it. Opening it with Archive Manager is really confusing.

  Test Case
  -
  Download a .deb
  Open your Downloads folder with the file manager.
  Double click on the .deb
  The Ubuntu Software app should open with a button that says Install.

  More Details
  
  desktop-file-utils provides /etc/gnome/defaults.list
  In that file, there is this line (and several other lines also referring to 
the same .desktop)

  application/vnd.debian.binary-package=snap-store_ubuntu-software-
  local-file.desktop

  But when I look at /snap/snap-store/575/usr/share/applications/
  there is gnome-software-local-file.desktop

  which is a different file name.

  I believe this issue can be fixed in either snap-store or with
  desktop-file-utils.

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


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


[Desktop-packages] [Bug 1969303] Re: "No package to remove" error when attempting to uninstall

2022-04-18 Thread Ken VanDine
Link to upstream bug https://gitlab.gnome.org/GNOME/gnome-
software/-/issues/1720

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

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Unknown
Status in snap-store-desktop:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a sottware, tthere is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

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


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


[Desktop-packages] [Bug 1969303] Re: "No package to remove" error when attempting to uninstall

2022-04-18 Thread Ken VanDine
I've also reproduced the same issue with the gnome-software 41.5 deb in
Jammy, output is slightly different:

14:26:55:0535 Gs  uninstall org.gnome.Cheese.desktop
14:26:55:0535 Gs  Chaining cancellation from 0x55d1dbee0fa0 to 0x55d1dc090820
14:26:55:0536 Gs  running remove on plugin=packagekit with dedupe-flags=7 with 
refine-flags=require-setup-action,require-origin with interactive=True with 
timeout=60 on apps 
system/package/manual:ubuntu-jammy-main/org.gnome.Cheese.desktop/*, elapsed 
time since creation 1ms
14:26:55:0538 Gs  Disconnecting cancellable 0x55d1dbee0fa0


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

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

** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1720
   https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1720

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

Title:
  "No package to remove" error when attempting to uninstall

Status in GNOME Software:
  Unknown
Status in snap-store-desktop:
  Confirmed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  On a fresh install of ubuntu 22.04, ubuntu-store won't uninstall any
  application

  If you want to uninstall a sottware, tthere is an error message : "no
  package to remove"

  No problem to uninstall this same software with synaptic for example

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


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


[Desktop-packages] [Bug 1969148] Re: [UIFe] Jammy default wallpaper update

2022-04-15 Thread Ken VanDine
** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

Title:
  [UIFe] Jammy default wallpaper update

Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Triaged
Status in ubuntu-mate-artwork package in Ubuntu:
  Fix Committed
Status in ubuntu-wallpapers package in Ubuntu:
  Fix Released

Bug description:
  Based on community feedback and internal review, we need to tweak the
  Jammy Jellyfish mascot wallpapers. Sorry for the inconvenience but
  it's important that things look as great as possible for the next LTS.

  Notifications:
  https://lists.ubuntu.com/archives/ubuntu-doc/2022-April/020839.html

  
  https://lists.ubuntu.com/archives/ubuntu-translators/2022-April/007836.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity-slideshow-ubuntu/+bug/1969148/+subscriptions


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


[Desktop-packages] [Bug 1966115] [NEW] wrong icon used with the new branding

2022-03-23 Thread Ken VanDine
Public bug reported:

Since the updated ubuntu branding has landed, the icon isn't just the
logo.  See attached screenshot

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


** Tags: iso-testing rls-jj-incoming

** Attachment added: "Screenshot from 2022-03-23 14-23-47.png"
   
https://bugs.launchpad.net/bugs/1966115/+attachment/5572274/+files/Screenshot%20from%202022-03-23%2014-23-47.png

** Tags added: iso-testing rls-jj-incoming

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

Title:
  wrong icon used with the new branding

Status in gnome-initial-setup package in Ubuntu:
  New

Bug description:
  Since the updated ubuntu branding has landed, the icon isn't just the
  logo.  See attached screenshot

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


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


[Desktop-packages] [Bug 1966114] [NEW] firefox-locale- needs to be dropped

2022-03-23 Thread Ken VanDine
Public bug reported:

Now that firefox is only available as a snap, we no longer need to
install a deb for the translations.

https://git.launchpad.net/ubuntu/+source/language-
selector/tree/data/pkg_depends?h=applied/ubuntu/devel#n14

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  firefox-locale- needs to be dropped

Status in language-selector package in Ubuntu:
  New

Bug description:
  Now that firefox is only available as a snap, we no longer need to
  install a deb for the translations.

  https://git.launchpad.net/ubuntu/+source/language-
  selector/tree/data/pkg_depends?h=applied/ubuntu/devel#n14

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1966114/+subscriptions


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


[Desktop-packages] [Bug 1965168] Re: jammy community competition wallpapers

2022-03-16 Thread Ken VanDine
** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Triaged

** Changed in: ubuntu-wallpapers (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  jammy community competition wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  Triaged

Bug description:
  We have the winning images, in full size and both under CC by SA 4.0

  The author of the first image is Elena Stravoravdi

  The author of the remaining images, both light and dark mode, is by
  hiking93

  If it is possible, we would like to include both the light and dark
  mode of the jellyfish image. If there is not enough room, please only
  include the light jellyfish image.

  Let me know if there are any other concerns or questions.

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


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


[Desktop-packages] [Bug 1965168] Re: jammy community competition wallpapers

2022-03-16 Thread Ken VanDine
** Summary changed:

- community competition wallpapers
+ jammy community competition wallpapers

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

Title:
  jammy community competition wallpapers

Status in ubuntu-wallpapers package in Ubuntu:
  New

Bug description:
  We have the winning images, in full size and both under CC by SA 4.0

  The author of the first image is Elena Stravoravdi

  The author of the remaining images, both light and dark mode, is by
  hiking93

  If it is possible, we would like to include both the light and dark
  mode of the jellyfish image. If there is not enough room, please only
  include the light jellyfish image.

  Let me know if there are any other concerns or questions.

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


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


[Desktop-packages] [Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)

2022-01-31 Thread Ken VanDine
I've confirmed that nvidia-470 is getting installed in jammy, not
nvidia-495.  AFAIK this is a bug, I thought nvidia-495 was in jammy?
Without it we don't get a wayland session with nvidia.

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

** Changed in: ubiquity (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Tags added: rls-jj-incoming

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

Title:
  "Launch using dedicated graphics card" option absent (nvidia,
  proprietary drivers, on-demand PRIME mode)

Status in OEM Priority Project:
  Invalid
Status in gnome-shell package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  New

Bug description:
  Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU
  Image: Jammy daily (20220126 build)

  Test steps
  ==

  Secure Boot enabled

  Installation options:

  - used ubiquity (not the new flutter installer)
  - normal installation
  - checked "Install third-party software for graphics and Wi-Fi hardware and 
additional media formats"
  - left "Configure Secure Boot" checked
  - Setup a password for Secure Boot MOK enrollment
  - Used "Erase disk and install Ubuntu" option

  After installation completes, the device reboots and I enroll the MOK
  in the UEFI BIOS.

  At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on
  Wayland"), which seems to be expected given that I am using NVidia
  proprietary drivers.

  Once logged in, nvidia-settings and GNOME Settings About screen both
  show that the GPU is available. It is set in "On-Demand" in nvidia-
  settings.

  
  $ switcherooctl 
  Device: 0
Name:Intel® UHD Graphics
Default: yes
Environment: DRI_PRIME=pci-_00_02_0

  Device: 1
Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile]
Default: no
Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1
  

  Expected result
  ===

  When right-clicking on an icon in the launcher (for instance Firefox
  or Files), a "Launch using dedicated graphics card" option is
  available and launches the selected software using Nvidia GPU.

  Actual result
  =

  However, there is no "Launch using dedicated graphics card" option
  available when right-clicking on an application launcher on the left.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 40.5-1ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 28 14:00:33 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2022-01-28 (0 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126)
  RelatedPackageVersions: mutter-common 41.3-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1959362/+subscriptions


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


[Desktop-packages] [Bug 1957779] Re: Regression: GNOME-specific interfaces not available in main

2022-01-13 Thread Ken VanDine
Thanks for the report, the MIR is already in progress at
https://bugs.launchpad.net/bugs/1953197

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

Title:
  Regression: GNOME-specific interfaces not available in main

Status in xdg-desktop-portal-gtk package in Ubuntu:
  New

Bug description:
  Historically, xdg-desktop-portal-gtk had two roles:

  * Generic GTK implementations of various interfaces, suitable for all
  GTK desktops (GNOME, XFCE, etc.) and also as a fallback implementation
  for desktops that do not have something more "native". Interfaces:
  Access, Account, AppChooser, Email, FileChooser, Inhibit, Lockdown,
  Notification, Print, Settings.

  * GNOME-specific implementations of various interfaces, suitable for
  GNOME Shell only (and mybe Budgie, but not XFCE, MATE or Cinnamon
  because they do not use gnome-settings-daemon or a libmutter-based
  compositor). Interfaces: Background, Remote Desktop, Screencast,
  Screenshot, Wallpaper.

  In 1.10.0-2, these roles were separated:

  * Generic GTK stuff is still in x-d-p-gtk

  * GNOME-specific functionality has moved to x-d-p-gnome, a separate
  source package, which is installed by the gnome-core metapackage in
  Debian

  In Ubuntu, x-d-p-gtk is in main but x-d-p-gnome is in universe (and
  presumably not installed by default). This means that users of Snap
  and Flatpak apps will not have access to the affected interfaces via
  xdg-desktop-portal any more, which is a regression, particularly if
  using native Wayland rather than X11.

  There are two possible solutions to this:

  1. Move x-d-p-gnome to main, and install it by default (in any
  installation that has GNOME Shell). GNOME upstream consider it to be
  part of a complete GNOME desktop. This is the long-term solution.

  2. Patch x-d-p-gtk to reinstate the build-dependencies that were
  disabled in 1.10.0-2, and re-enable them in d/rules. This provides an
  older version of these interfaces, which is no longer routinely tested
  by upstream or Debian. This solution will probably stop working in a
  future release when these interfaces are removed completely.

  I would recommend the first solution for Ubuntu 22.04 LTS.

  I am probably going to use the second solution in Debian bullseye-
  backports, and if Ubuntu people want to maintain a backport of x-d-p-
  gtk to older suites like focal, it's probably the right thing to do
  for those too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1957779/+subscriptions


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


[Desktop-packages] [Bug 1373069] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()

2021-09-28 Thread Ken VanDine
*** This bug is a duplicate of bug 1845362 ***
https://bugs.launchpad.net/bugs/1845362

** This bug has been marked a duplicate of bug 1845362
   gnome-font-viewer crashed with signal 5 in _XEventsQueued()

** Tags removed: rls-ii-incoming

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

Title:
  gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Inspecting the DroidSans font

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: gnome-font-viewer 3.12.0-1
  ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3
  Uname: Linux 3.16.0-17-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Sep 23 20:20:19 2014
  ExecutablePath: /usr/bin/gnome-font-viewer
  InstallationDate: Installed on 2014-09-14 (8 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140914)
  ProcCmdline: gnome-font-viewer /home/username/Harmattan/Font/DroidSans.ttf
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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


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


[Desktop-packages] [Bug 1944736] Re: gnome-font-viewer crashed with signal 5 in _XEventsQueued()

2021-09-28 Thread Ken VanDine
*** This bug is a duplicate of bug 1845362 ***
https://bugs.launchpad.net/bugs/1845362

** This bug is no longer a duplicate of bug 1373069
   gnome-font-viewer crashed with signal 5 in _XEventsQueued()
** This bug has been marked a duplicate of bug 1845362
   gnome-font-viewer crashed with signal 5 in _XEventsQueued()

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

Title:
  gnome-font-viewer crashed with signal 5 in _XEventsQueued()

Status in gnome-font-viewer package in Ubuntu:
  New

Bug description:
  This happened when launching fonts on an Ubuntu Impish daily live cd
  when running "Try Ubuntu".

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: gnome-font-viewer 40.0-2
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu69
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.465
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 23 13:47:00 2021
  ExecutablePath: /usr/bin/gnome-font-viewer
  LiveMediaBuild: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922)
  ProcCmdline: /usr/bin/gnome-font-viewer --gapplication-service
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANG=en_US.UTF-8
  Signal: 5
  SourcePackage: gnome-font-viewer
  StacktraceTop:
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: gnome-font-viewer crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  separator:

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


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


[Desktop-packages] [Bug 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

2021-07-16 Thread Ken VanDine
** Summary changed:

- NTP servers from DCHP are not propagated to timesyncd
+ NTP servers from DHCP are not propagated to timesyncd

** Changed in: network-manager (Ubuntu)
 Assignee: (unassigned) => Heather Ellsworth (hellsworth)

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

Title:
  NTP servers from DHCP are not propagated to timesyncd

Status in network-manager package in Ubuntu:
  New

Bug description:
  Network manager gets NTP servers from DHCP but do not update timesyncd to use 
it which keeps using ntp.ubuntu.com.
   
  This is a problem on private networks which do not have access to public 
internet. On this type of network the configuration of timesyncd must be 
updated manually instead of inheriting the conf from the dhcp servers.

  This can be integrated with a NM dispatcher script such as below:

  etc/NetworkManager/dispatcher.d/10-update-timesyncd for example:

  ==8<=8<=8<=8<=8<==
  #! /usr/bin/bash

  [ -n "$CONNECTION_UUID" ] || exit

  INTERFACE=$1
  ACTION=$2

  case $ACTION in
  up | dhcp4-change | dhcp6-change)
  [ -n "$DHCP4_NTP_SERVERS" ] || exit
  mkdir -p /etc/systemd/timesyncd.conf.d/
  cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  [Time]
  NTP=$DHCP4_NTP_SERVERS
  RootDistanceMaxSec=15
  EOF
  systemctl restart systemd-timesyncd
 ;;
  down)
  rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  systemctl restart systemd-timesyncd
  ;;
  esac
  ==8<=8<=8<=8<=8<==

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 28 14:08:52 2021
  InstallationDate: Installed on 2020-05-31 (393 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  RebootRequiredPkgs:
   linux-image-5.11.0-20-generic
   linux-base
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

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


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


[Desktop-packages] [Bug 1921405] Re: preseeded snaps prevent installing chromium-browser deb2snap in chroot, again

2021-04-15 Thread Ken VanDine
Please followup with @osomon if this is reproduced.

** Tags removed: rls-hh-incoming

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

Title:
  preseeded snaps prevent installing chromium-browser deb2snap in
  chroot, again

Status in chromium-browser package in Ubuntu:
  Incomplete

Bug description:
  preseeded snaps prevent installing chromium-browser deb2snap in
  chroot, again

  potentially https://bugs.launchpad.net/ubuntu/+source/chromium-
  browser/+bug/1882232 regressed since preseeded snaps landed in focal
  desktop.

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

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


[Desktop-packages] [Bug 1922839] Re: Opening new tab in gnome-terminal launched from nautilus loses most environment variables

2021-04-15 Thread Ken VanDine
** Tags removed: rls-hh-incoming

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

Title:
  Opening new tab in gnome-terminal launched from nautilus loses most
  environment variables

Status in gnome-terminal package in Ubuntu:
  New
Status in gnome-terminal source package in Hirsute:
  New

Bug description:
  [Impact]

  If you launch gnome-terminal by right clicking a directory in
  Nautilus, selecting "Open in Terminal", you get a fully functional
  terminal window.

  If you then press the new tab button, or ctrl-shift-t to open a new
  terminal tab, you will find that most environment variables have
  become unset, and you see the text:

  To run a command as administrator (user "root"), use "sudo ".
  See "man sudo_root" for details.

  Comparing printenv between:

  Normal terminal: https://paste.ubuntu.com/p/2hcCY9hbHQ/
  Broken new terminal tab: https://paste.ubuntu.com/p/zYsjRHVJH7/

  Most commands won't run in the new terminal tab, due to $HOME and
  $USER not being set.

  Note, if you launch gnome-terminal from gnome-shell or the dock, and
  create a new tab, everything works perfectly. Is something wrong with
  the Nautilus option for "Open in Terminal"?

  [Testcase]

  1. Launch Nautilus to home directory
  2. Right click > "Open in Terminal"
  3. Run "printenv" to see full list of env variables
  4. Click new tab button, or ctrl-shift-t
  5. Run "printenv" see the lack of env variables

  I have a test package available in the below ppa:

  https://launchpad.net/~mruffell/+archive/ubuntu/lp1922839-test

  The build in the ppa has 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
  reverted.

  If you install this package, environment variables will be set
  correctly.

  [Where problems could occur]

  I think there is some risk with re-instating a commit which has been
  reverted, and users could run into similar issues as found in the
  upstream bug.

  We do have some supporting evidence that the commit isn't too harmful,
  since it is applied to Groovy currently, things work as intended
  there, and users haven't complained about the issues in the upstream
  bug applying to Groovy.

  If a regression were to occur, then launching a new gnome-terminal or
  opening a new tab could land the user with a terminal with little to
  no environment variables set. A workaround will be to launch gnome-
  terminal from gnome-shell overview.

  [Other info]

  Focal and Groovy have the following commit applied:

  commit fd5ac772154426e2da5afd633b336414bca33be9
  Author: Christian Persch 
  Date:   Mon Mar 23 09:57:56 2020 +0100
  Subject: screen: Use clean env when creating new tab
  Link: 
https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/fd5ac772154426e2da5afd633b336414bca33be9

  This was then reverted in 3.38.1 due to the upstream bug:

  https://gitlab.gnome.org/GNOME/gnome-terminal/-/issues/253

  The reverted commit is:

  commit 16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac
  Author: Christian Persch 
  Date:   Thu Sep 17 17:10:47 2020 +0200
  Subject: Revert "screen: Use clean env when creating new tab"
  Link: 
https://gitlab.gnome.org/GNOME/gnome-terminal/-/commit/16bd9f6a4181d37af2769e7ca5a1f9a1211cfaac

  This revert seems to have broken Hirsute. If we revert the revert,
  that is, apply the commit again, things work as intended.

  To fix this, we need to re-apply
  fd5ac772154426e2da5afd633b336414bca33be9.

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

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


[Desktop-packages] [Bug 1922772] Re: Overview search causes the workarea to reshape, desktop-icons-ng to restart and the new window to lose focus

2021-04-15 Thread Ken VanDine
** Tags removed: rls-hh-incoming

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

Title:
  Overview search causes the workarea to reshape, desktop-icons-ng to
  restart and the new window to lose focus

Status in gnome-shell package in Ubuntu:
  Fix Committed

Bug description:
  Release: Ubuntu 21.04 (20210406 iso image)

  Software, version: gnome-shell, 3.38.4-1ubuntu1

  How to reproduce:
  1) Boot up Ubuntu 21.04 image (live session or installed)
  2) Once inside shell, go to overview (either using Super key or clicking on 
Activities)
  3) Search for any application (eg., terminal) and launch it.

  Expected:
  The application launches normally and usable.

  Actual:
  The application launches but the window looses focus. When the application is 
launching, the desktop icons disappear for few seconds and reappear. When they 
reappear the launched application window will not have focus.

  If we launch the application from the app grid (without searching
  first) or from the dock, the window retains the focus.

  Tested on VM (quickemu and virt-manager).

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: gnome-shell 3.38.4-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  6 22:14:04 2021
  DisplayManager: gdm3
  InstallationDate: Installed on 2021-04-06 (0 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210405)
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1
  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/1922772/+subscriptions

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


[Desktop-packages] [Bug 1921949] Re: math save icon reset upon click or arrow action

2021-04-06 Thread Ken VanDine
Can you please look for an upstream bug reference, and submit a bug
there if necessary

** Changed in: libreoffice (Ubuntu Hirsute)
 Assignee: (unassigned) => Heather Ellsworth (hellsworth)

** Changed in: libreoffice (Ubuntu Focal)
 Assignee: (unassigned) => Heather Ellsworth (hellsworth)

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

Title:
  math save icon reset upon click or arrow action

Status in libreoffice package in Ubuntu:
  New
Status in libreoffice source package in Focal:
  New
Status in libreoffice source package in Hirsute:
  New

Bug description:
  libreoffice 7.1.2.2

  Changes are not being stored properly.

  Steps to reproduce:
  1. open new math doc
  2. add any equation -> see the save icon indicates there are changes that 
need to be saved.
  3. click anywhere or arrow anywhere -> see the save icon go back to 
indicating there are no changes.

  Additionally you can close the doc in this state and you will not be
  prompted to save/discard changes.

  True in both focal and hirsute vms, in both the snap and the debs from
  the prereleases ppa.

  This problem *does not manifest* in an updated debian testing vm, with
  7.1.2~rc2 from experimental.

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

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


[Desktop-packages] [Bug 1921083] Re: evince master snap fails to build

2021-03-24 Thread Ken VanDine
This will get fixed with the update to gnome-3-38 extension

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

Title:
  evince master snap fails to build

Status in evince package in Ubuntu:
  Confirmed

Bug description:
  The current version requires libhandy-1 which isn't part of the gnome
  platform in use

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

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


[Desktop-packages] [Bug 1917926] [NEW] Window focus issues in 3.38.3-3ubuntu1

2021-03-05 Thread Ken VanDine
Public bug reported:

I switched to an Xorg session in hirsute today after upgrading gnome-
shell and mutter packages which just hit the release package.  There are
very strange focus issues.  Clicking on a window doesn't raise it to the
front, alt-tab seems to only switch between a subset of the one windows.
It's impossible to move windows with the mouse and resizing does not
work.

This occurred with:
gnome-shell=3.38.3-3ubuntu1
mutter=3.38.3-3ubuntu1

Downgrading these packages fixed it:
gnome-shell=3.38.3-2ubuntu2
mutter=3.38.3-2ubuntu1

** Affects: mutter (Ubuntu)
 Importance: Critical
 Status: Triaged


** Tags: rls-hh-incoming

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

Title:
  Window focus issues in 3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

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

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


[Desktop-packages] [Bug 1917926] Re: Window focus issues in 3.38.3-3ubuntu1

2021-03-05 Thread Ken VanDine
** Tags added: rls-hh-incoming

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

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

Title:
  Window focus issues in 3.38.3-3ubuntu1

Status in mutter package in Ubuntu:
  Triaged

Bug description:
  I switched to an Xorg session in hirsute today after upgrading gnome-
  shell and mutter packages which just hit the release package.  There
  are very strange focus issues.  Clicking on a window doesn't raise it
  to the front, alt-tab seems to only switch between a subset of the one
  windows. It's impossible to move windows with the mouse and resizing
  does not work.

  This occurred with:
  gnome-shell=3.38.3-3ubuntu1
  mutter=3.38.3-3ubuntu1

  Downgrading these packages fixed it:
  gnome-shell=3.38.3-2ubuntu2
  mutter=3.38.3-2ubuntu1

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

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


[Desktop-packages] [Bug 1883886] Re: Print dialogue's height in Libreoffice Writer is too high to see and click buttons.

2021-03-02 Thread Ken VanDine
** Tags removed: rls-ff-incoming

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

Title:
   Print dialogue's height in Libreoffice Writer is too high to see and
  click buttons.

Status in LibreOffice:
  Fix Released
Status in libreoffice package in Ubuntu:
  In Progress

Bug description:
  Hello,

  I have the bug that is denoted here
  https://ask.libreoffice.org/en/question/240651/print-dialogue-too-
  large-to-select-ok-to-print/ and here
  https://bugs.documentfoundation.org/show_bug.cgi?id=127782#c67.

  Essentially, the libreoffice writer print's dialog box is too high for
  me to view and press the buttons with the mouse. A workaround is to
  just press ENTER to print.

  Please see the following screenshot for an example:
  https://snipboard.io/vc1X0f.jpg

  My information is as follows:

  Results of lsb_release -rd

  Description: Ubuntu 20.04 LTS
  Release: 20.04

  Results of apt-cache policy libreoffice-writer

  libreoffice-writer:
Installed: 1:6.4.3-0ubuntu0.20.04.1
Candidate: 1:6.4.3-0ubuntu0.20.04.1
Version table:
   *** 1:6.4.3-0ubuntu0.20.04.1 500
  500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:6.4.2-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

  
  Just FYI in case it is necessary: I am using Lubuntu 20.04 LTS with LXQt. 

  Best regards,

  
  Owen Charles

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libreoffice-writer 1:6.4.3-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.3
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Wed Jun 17 12:47:56 2020
  InstallationDate: Installed on 2020-06-05 (11 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1915161] Re: deja dup won't restore a folder where name contains apostrophe and space

2021-03-02 Thread Ken VanDine
** Changed in: deja-dup (Ubuntu Groovy)
   Status: Triaged => Won't Fix

** Changed in: duplicity (Ubuntu Groovy)
   Status: Triaged => Won't Fix

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

Title:
  deja dup won't restore a folder where name contains apostrophe and
  space

Status in deja-dup package in Ubuntu:
  Fix Released
Status in duplicity package in Ubuntu:
  Fix Released
Status in deja-dup source package in Groovy:
  Won't Fix
Status in duplicity source package in Groovy:
  Won't Fix

Bug description:
  I have a folder entitled Mothers' Union. I use Deja-Dup to backup it
  up (along with many other folders) on Ubuntu 20.10. When I open Deja-
  Dup and click on the restore option and pick a back-up date it shows
  all the folders in the backup except this one (Mothers' Union). If I
  remove the apostrophe from the folder name it backs it up fine and can
  be restored. Other folders where the apostrophe is in the name but not
  followed by a space (e.g. John's Documents) also backup and restore
  correctly. Not sure if this is a bug but it's unfortunate that with
  this combination of an apostrophe and a space in the name I can't
  restore the folder.

  1. Ubuntu 20.10
  2. deja-dup 42.2-1ubuntu1
  3. I expected to be able to restore the folder with the apostrophe and space 
in the name (Mothers' Union)
  4. The folder is not available in any of the restore points.

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

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


[Desktop-packages] [Bug 1914374] Re: Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

2021-03-02 Thread Ken VanDine
** Changed in: ubiquity (Ubuntu Groovy)
   Status: Triaged => Won't Fix

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

Title:
  Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

Status in OEM Priority Project:
  Fix Released
Status in ubiquity package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released
Status in ubuntu-drivers-common source package in Focal:
  Fix Released
Status in ubiquity source package in Groovy:
  Won't Fix
Status in ubuntu-drivers-common source package in Groovy:
  New

Bug description:
  I've installed the focal-desktop-amd64.iso image with SHA-256 sum
  b928163990d9e148605c230c5d3e7bc563bb67269d551f741abc804553f3477c from
  http://cdimage.ubuntu.com/focal/daily-live/20210202.1/ on the HP ZBook
  15 G7 laptop (CID 202009-28216).

  There are multiple issues:

  * The graphical desktop isn't launched. The screen remains black except for a 
cursor blinking erratically in the top left corner of the screen. If I hammer 
Control+Alt+F[12345] for a while, the graphical desktop starts eventually.
  * The screen resolution is 3840x2160 but there is no scaling, so everything 
is tiny.
  * The touchpad does not work.
  * WLAN does not work.
  * Ethernet does not work. I tried two dongles (a USB A as well as a USB C 
dongle).
  * No sound.

  $ cat /proc/version_signature
  Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18

  $ lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1914374/+subscriptions

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


[Desktop-packages] [Bug 1911802] Re: Video glitches playing hardware accelerated video through VAAPI

2021-02-23 Thread Ken VanDine
** Also affects: mesa (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Tags removed: rls-ff-incoming

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

Title:
  Video glitches playing hardware accelerated video through VAAPI

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New

Bug description:
  Same issue as the post here describes:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3681

  The video is scaled unevenly in the vertical axis, with a black bar
  appearing in the bottom of the video window for a few frames. It
  happens seemingly on all videos able to be hardware decoded, upon
  starting the video and upon seeking.

  The regression happened somewhere between 20.0.8-0ubuntu1~20.04.1 and
  20.2.6-0ubuntu0.20.04.1 but apparently has been fixed in mesa 20.3

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

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


[Desktop-packages] [Bug 1910838] Re: stopped working after latest update

2021-02-23 Thread Ken VanDine
** Tags removed: rls-ff-incoming

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

Title:
  stopped working after latest update

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Incomplete

Bug description:
  dec 16 the following updates were installed after which gnome-shell-
  extension-appindicator stopped working as expected:

  apport (2.20.11-0ubuntu27.13) to 2.20.11-0ubuntu27.14
  apport-gtk (2.20.11-0ubuntu27.13) to 2.20.11-0ubuntu27.14
  firefox (83.0+build2-0ubuntu0.20.04.1) to 84.0+build3-0ubuntu0.20.04.1
  firefox-locale-en (83.0+build2-0ubuntu0.20.04.1) to 
84.0+build3-0ubuntu0.20.04.1
  gir1.2-gnomedesktop-3.0 (3.36.3.1-0ubuntu1) to 3.36.8-0ubuntu1
  gnome-desktop3-data (3.36.3.1-0ubuntu1) to 3.36.8-0ubuntu1
  gnome-shell-extension-appindicator (33-1) to 33.1-0ubuntu0.20.04.1
  gnome-system-monitor (3.36.0-1) to 3.36.1-0ubuntu0.20.04.1
  imagemagick (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 8:6.9.10.23+dfsg-2.1ubuntu11.2
  imagemagick-6-common (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 
8:6.9.10.23+dfsg-2.1ubuntu11.2
  imagemagick-6.q16 (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 
8:6.9.10.23+dfsg-2.1ubuntu11.2
  libevdev2 (1.9.0+dfsg-1) to 1.9.0+dfsg-1ubuntu0.1
  libgnome-desktop-3-19 (3.36.3.1-0ubuntu1) to 3.36.8-0ubuntu1
  libinput-bin (1.15.5-1ubuntu0.1) to 1.15.5-1ubuntu0.2
  libinput10 (1.15.5-1ubuntu0.1) to 1.15.5-1ubuntu0.2
  libmagickcore-6.q16-6 (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 
8:6.9.10.23+dfsg-2.1ubuntu11.2
  libmagickcore-6.q16-6-extra (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 
8:6.9.10.23+dfsg-2.1ubuntu11.2
  libmagickwand-6.q16-6 (8:6.9.10.23+dfsg-2.1ubuntu11.1) to 
8:6.9.10.23+dfsg-2.1ubuntu11.2
  libwhoopsie0 (0.2.69ubuntu0.1) to 0.2.69ubuntu0.2
  python3-apport (2.20.11-0ubuntu27.13) to 2.20.11-0ubuntu27.14
  python3-problem-report (2.20.11-0ubuntu27.13) to 2.20.11-0ubuntu27.14
  whoopsie (0.2.69ubuntu0.1) to 0.2.69ubuntu0.2

  
  ever since this update, the HP printer driver applet (hplip-systray) reports:
  "No system tray detected on this system.
  Unable to start, exiting."

  this used to work before dec. 16

  gnome-tweak-tool indicates that is loaded, so not sure what's going on here
  (have the same problem also on another ubuntu-machine)

  thanks,
  Daniel

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell-extension-appindicator 33.1-0ubuntu0.20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-60.67-generic 5.4.78
  Uname: Linux 5.4.0-60-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Fri Jan  8 21:31:13 2021
  InstallationDate: Installed on 2019-09-04 (492 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to focal on 2020-05-03 (251 days ago)

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

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


[Desktop-packages] [Bug 1905370] Re: Qt-based tray icons not displayed on start-up

2021-02-23 Thread Ken VanDine
** Tags removed: rls-ff-incoming rls-gg-incoming

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

** Also affects: gnome-shell-extension-appindicator (Ubuntu Hirsute)
   Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Triaged

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

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

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

** Changed in: gnome-shell-extension-appindicator (Ubuntu Groovy)
   Importance: Undecided => Medium

** Changed in: gnome-shell-extension-appindicator (Ubuntu Focal)
   Importance: Undecided => Medium

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

Title:
  Qt-based tray icons not displayed on start-up

Status in Ubuntu AppIndicators:
  Unknown
Status in gnome-shell-extension-appindicator package in Ubuntu:
  Triaged
Status in gnome-shell-extension-appindicator source package in Focal:
  New
Status in gnome-shell-extension-appindicator source package in Groovy:
  New
Status in gnome-shell-extension-appindicator source package in Hirsute:
  Triaged

Bug description:
  My system version is 20.10. I upgraded from 20.04. I found such a
  problem, the tray icon cannot be displayed when the system is turned
  on or restarted, but if I kill the process and restart it, it will be
  fine.

  I searched on Google and didn't see a similar problem.This is my
  hardware configuration:

  CPU: Two Intel® Xeon(R) CPU E5-2680 v4 @ 2.40GHz × 56
  GPU: NVIDIA Corporation GP106 [P106-100] / NVIDIA Corporation GP106 
[GeForce 1060]

  https://i.stack.imgur.com/ybiVj.png

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome (not installed)
  ProcVersionSignature: Ubuntu 5.8.0-28.30-generic 5.8.14
  Uname: Linux 5.8.0-28-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu50.1
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 24 16:34:31 2020
  InstallationDate: Installed on 2020-10-24 (31 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  RebootRequiredPkgs:
   gnome-shell
   linux-image-5.8.0-29-generic
   linux-base
  SourcePackage: meta-gnome3
  UpgradeStatus: Upgraded to groovy on 2020-10-25 (29 days ago)

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

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


[Desktop-packages] [Bug 1915449] Re: XWayland hangs at 100% of CPU causing gnome-shell to hang

2021-02-16 Thread Ken VanDine
** Tags removed: rls-hh-incoming

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

Title:
  XWayland hangs at 100% of CPU causing gnome-shell to hang

Status in X.Org X server:
  Unknown
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  This is happening in Hirsute (running in vmware player) quite easily,
  just move around a firefox (or any other x11 window) around, hitting
  the shell edges and you'll get all freezing with Xwayland process at
  100%.

  Hangs seems to have this trace:

  0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0) at 
../../../../../hw/xwayland/xwayland.c:869
  869   ../../../../../hw/xwayland/xwayland.c: No such file or directory.
  (gdb) bt
  #0  0x55b9abfb69b1 in xwl_screen_post_damage (xwl_screen=0x55b9ac423dd0) 
at ../../../../../hw/xwayland/xwayland.c:869
  #1  block_handler (data=0x55b9ac423dd0, timeout=) at 
../../../../../hw/xwayland/xwayland.c:1037
  #2  0x55b9ac0ecf3e in BlockHandler 
(pTimeout=pTimeout@entry=0x7ffdc8574204) at ../../../../dix/dixutils.c:388
  #3  0x55b9ac119a52 in WaitForSomething (are_ready=0) at 
../../../../os/WaitFor.c:201
  #4  0x55b9ac0e8297 in Dispatch () at ../../../../dix/dispatch.c:421
  #5  0x55b9ac0ec5a4 in dix_main (argc=16, argv=0x7ffdc85743e8, 
envp=) at ../../../../dix/main.c:276
  #6  0x7f5ab299d565 in __libc_start_main (main=0x55b9abfb5a80 , 
argc=16, argv=0x7ffdc85743e8, init=,
  fini=, rtld_fini=, 
stack_end=0x7ffdc85743d8) at ../csu/libc-start.c:332
  #7  0x55b9abfb5abe in _start ()

  (gdb) info local
  xwl_window = 0x55b9acbf18f0
  next_xwl_window = 0x7ffdc8574150
  commit_window_list = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
  xwl_window = 
  next_xwl_window = 
  commit_window_list = {next = , prev = }

  (gdb) print commit_window_list
  $1 = {next = 0x55b9acbf1910, prev = 0x55b9acbf1910}
  (gdb) print commit_window_list->next
  $2 = (struct xorg_list *) 0x55b9acbf1910
  (gdb) print commit_window_list->next->next
  $3 = (struct xorg_list *) 0x7ffdc8574170
  (gdb) print commit_window_list->next->next->next
  $4 = (struct xorg_list *) 0x55b9acbf1910
  (gdb) print commit_window_list->next->next->next->next
  $5 = (struct xorg_list *) 0x7ffdc8574170
  (gdb) print commit_window_list->next->next->next->next->next
  $6 = (struct xorg_list *) 0x55b9acbf1910
  (gdb) print commit_window_list->next->next->next->next->next->next
  $7 = (struct xorg_list *) 0x7ffdc8574170

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1915449/+subscriptions

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


[Desktop-packages] [Bug 1883370] Re: system-config-printer hangs when trying to change driver

2021-02-09 Thread Ken VanDine
** Changed in: system-config-printer (Ubuntu Focal)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

** Changed in: system-config-printer (Ubuntu Groovy)
 Assignee: (unassigned) => Till Kamppeter (till-kamppeter)

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

Title:
  system-config-printer hangs when trying to change driver

Status in System Config Printer:
  Fix Released
Status in system-config-printer package in Ubuntu:
  Fix Released
Status in system-config-printer source package in Focal:
  New
Status in system-config-printer source package in Groovy:
  New

Bug description:
  gnome-control-center is able to find and install my network printer
  (Samsung M287x) automatically.  When I attempt to change the printer
  driver (default printer driver doesn't support duplex printing) via
  system-config-printer, system-config-printer will hang.  Please see
  attached log captured via system-config-printer --debug.  I am running
  stock Ubuntu 20.04.  Changing the driver worked fine in ubuntu 19.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: system-config-printer 1.5.12-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CupsErrorLog:
   
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 13 10:34:15 2020
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationDate: Installed on 2020-05-17 (27 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterpreterPath: /usr/bin/python3.8
  Lpstat: device for M267x-287x: socket://192.168.1.166
  MachineType: LENOVO 20KHCTO1WW
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/M267x-287x.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/M267x-287x.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=d86e16c0-e48c-492e-9cf8-05a068340cd7 ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/20/2020
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET71W (1.46 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET71W(1.46):bd02/20/2020:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/system-config-printer/+bug/1883370/+subscriptions

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


[Desktop-packages] [Bug 1914868] Re: gnome-software-dev doesn't contain all the header files in /usr/include/gnome-software

2021-02-09 Thread Ken VanDine
** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

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

** Also affects: gnome-software (Ubuntu Hirsute)
   Importance: Undecided
 Assignee: Sebastien Bacher (seb128)
   Status: Confirmed

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

Title:
  gnome-software-dev doesn't contain all the header files in
  /usr/include/gnome-software

Status in gnome-software package in Ubuntu:
  Confirmed
Status in gnome-software source package in Focal:
  New
Status in gnome-software source package in Hirsute:
  Confirmed

Bug description:
  I have tried to compile example plugin mentioned here:
  
https://gitlab.gnome.org/GNOME/gnome-software/-/blob/master/contrib/gs-plugin-example.c
  and here:
  https://developer.gnome.org/gnome-software/stable/plugins.html
  I have installed package gnome-software-dev (required for compilation)

  But I am not able to compile it:

  $ gcc -shared -o libgs_plugin_example.so gs-plugin-example.c -fPIC  
`pkg-config --libs --cflags gnome-software`  
-DI_KNOW_THE_GNOME_SOFTWARE_API_IS_SUBJECT_TO_CHANGE
  In file included from gs-plugin-example.c:5:
  /usr/include/gnome-software/gnome-software.h:16:10: fatal error: 
gs-app-collation.h: No such file or directory
 16 | #include 
|  ^~~~
  compilation terminated.

  
  It appears package gnome-software-dev lacks some headers.

  
  This issue was already reported here: 
  https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1119#note_1002516

  My system:
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04

  Package version:
  apt-cache policy gnome-software-dev 
  gnome-software-dev:
Zainstalowana: 3.36.1-0ubuntu0.20.04.0
Kandydująca:   3.36.1-0ubuntu0.20.04.0
Tabela wersji:
   *** 3.36.1-0ubuntu0.20.04.0 500
  500 http://pl.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   3.36.0-0ubuntu3 500
  500 http://pl.archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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


[Desktop-packages] [Bug 1876879] Re: gnome-software cannot install classic snaps if a channel is selected

2020-12-19 Thread Ken VanDine
This is now fixed in the stable channel.

** Changed in: snap-store-desktop
   Status: Confirmed => Fix Released

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

Title:
  gnome-software cannot install classic snaps if a channel is selected

Status in snap-store-desktop:
  Fix Released
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  I tried installing Android Studio from gnome-software. In the top
  right dropdown, it asks for the source. For Andoid Studio it displays
  Ubuntu. I was suspicious of it being a deb and not a snap. So I
  clicked on it and it shown me 3 Snap channel options. I selected
  latest/stable. The source changed according to my selection. Then I
  tried installing it but it failed saying:

  Unable to install "Android Studio": snap "android-studio" requires
  classic confinement

  I was puzzled. So I went back to the search menu, I clicked again on
  Android Studio and the source was now again on Ubuntu (note that this
  is not an option available in the dropdown). I checked the details and
  indeed it's the snap package from channel latest/stable, just the
  source is somehow misleading. Now it installed the software without
  issues.

  
  What doesn't work:
  - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel
  - Selecting a channel breaks the install functionality for classic snaps (it 
seems like it attempts to install them without --classic)

  Workaround:
  Do not select any channel, just use what is provided, and it works. If 
needing to use a different channel, use the command line (or perhaps check if 
this works in the Snap Store, if it has not the same issue).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 11:09:26 2020
  InstallationDate: Installed on 2020-04-03 (31 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.36.0-0ubuntu3
   gnome-software-plugin-snap3.36.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768

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

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


[Desktop-packages] [Bug 1876879] Re: gnome-software cannot install classic snaps if a channel is selected

2020-12-17 Thread Ken VanDine
** Changed in: snap-store-desktop
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: snap-store-desktop
   Importance: High => Critical

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

Title:
  gnome-software cannot install classic snaps if a channel is selected

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

Bug description:
  I tried installing Android Studio from gnome-software. In the top
  right dropdown, it asks for the source. For Andoid Studio it displays
  Ubuntu. I was suspicious of it being a deb and not a snap. So I
  clicked on it and it shown me 3 Snap channel options. I selected
  latest/stable. The source changed according to my selection. Then I
  tried installing it but it failed saying:

  Unable to install "Android Studio": snap "android-studio" requires
  classic confinement

  I was puzzled. So I went back to the search menu, I clicked again on
  Android Studio and the source was now again on Ubuntu (note that this
  is not an option available in the dropdown). I checked the details and
  indeed it's the snap package from channel latest/stable, just the
  source is somehow misleading. Now it installed the software without
  issues.

  
  What doesn't work:
  - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel
  - Selecting a channel breaks the install functionality for classic snaps (it 
seems like it attempts to install them without --classic)

  Workaround:
  Do not select any channel, just use what is provided, and it works. If 
needing to use a different channel, use the command line (or perhaps check if 
this works in the Snap Store, if it has not the same issue).

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-software 3.36.0-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  Date: Tue May  5 11:09:26 2020
  InstallationDate: Installed on 2020-04-03 (31 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401)
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.36.0-0ubuntu3
   gnome-software-plugin-snap3.36.0-0ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apport.crashdb.conf: [modified]
  mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768

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

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


[Desktop-packages] [Bug 1904640] Re: [SRU] [groovy] New upstream microrelease flatpak 1.8.3

2020-11-24 Thread Ken VanDine
** Also affects: flatpak (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Changed in: flatpak (Ubuntu Groovy)
 Assignee: (unassigned) => Andrew Hayzen (ahayzen)

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

Title:
  [SRU] [groovy] New upstream microrelease flatpak 1.8.3

Status in flatpak package in Ubuntu:
  Fix Released
Status in flatpak source package in Groovy:
  In Progress

Bug description:
  This is a request to SRU the latest release of flatpak into groovy.

  [Impact]

  New upstream release of flatpak, which brings fixes and improvements.

  Groovy is currently at 1.8.2, whereas 1.8.3 is available upstream.

  [Test Case]

  The bugs being resolved are not simple to reproduce, see the test plan
  below for testing flatpak itself.

  [Regression Potential]

  Flatpak has a test suite, which is run on build across all
  architectures and passes.

  There is also a manual test plan
  https://wiki.ubuntu.com/Process/Merges/TestPlan/flatpak. I have
  confirmed that 1.8.3 passes with this test plan on groovy.

  Flatpak has autopkgtests enabled
  http://autopkgtest.ubuntu.com/packages/f/flatpak which is passing on
  groovy.

  Regression potential is low, and upstream is very responsive to any
  issues raised.

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

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


[Desktop-packages] [Bug 1898205] Re: Thunderbird snap should be maintained by Canonical

2020-10-14 Thread Ken VanDine
Store request submitted https://forum.snapcraft.io/t/transfer-
thunderbird-to-canonical/20562

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

Title:
  Thunderbird snap should be maintained by Canonical

Status in thunderbird package in Ubuntu:
  New

Bug description:
  At the moment, the Thunderbird snap is maintained by Kev Van Dine.
  Obviously, nothing personal, and THANKS for packaging! :-)

  But, as Firefox snap, it would be more logical that Canonical handles
  the authoring, as this software needs somewhat the Canonical official
  support if a later defaulting/recommending of the snap version is
  done.

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

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


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

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

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

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

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

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

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

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

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

  Expected result
  Nothing is displayed.

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

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

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


[Desktop-packages] [Bug 1893113] Re: [SRU] Rhythmbox: Cannot add more music after a collection has been created

2020-09-01 Thread Ken VanDine
** Changed in: rhythmbox-plugin-alternative-toolbar (Ubuntu Focal)
 Assignee: (unassigned) => fossfreedom (fossfreedom)

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

Title:
  [SRU] Rhythmbox: Cannot add more music after a collection has been
  created

Status in rhythmbox-plugin-alternative-toolbar package in Ubuntu:
  Fix Released
Status in rhythmbox-plugin-alternative-toolbar source package in Focal:
  Triaged
Status in rhythmbox-plugin-alternative-toolbar source package in Groovy:
  Fix Released

Bug description:
  * In progress - need to complete*

  [Impact]

   * An explanation of the effects of the bug on users and

   * justification for backporting the fix to the stable release.

   * In addition, it is helpful, but not required, to include an
 explanation of how the upload fixes this bug.

  [Test Case]

   * detailed instructions how to reproduce the bug

   * these should allow someone who is not familiar with the affected
 package to reproduce the bug and verify that the updated package fixes
 the problem.

  [Regression Potential]

   * discussion of how regressions are most likely to manifest as a
  result of this change.

   * It is assumed that any SRU candidate patch is well-tested before
 upload and has a low overall risk of regression, but it's important
 to make the effort to think about what ''could'' happen in the
 event of a regression.

   * This both shows the SRU team that the risks have been considered,
 and provides guidance to testers in regression-testing the SRU.

  [Other Info]
   
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance

  Please refer:

  https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1790

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox-plugin-alternative-toolbar/+bug/1893113/+subscriptions

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


[Desktop-packages] [Bug 1891478] Re: orca ftbfs in focal (amd64 only)

2020-09-01 Thread Ken VanDine
** Also affects: orca (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: at-spi2-atk (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: orca (Ubuntu Focal)
 Assignee: (unassigned) => Marcus Tomlinson (marcustomlinson)

** Changed in: orca (Ubuntu Focal)
   Status: New => In Progress

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

** Changed in: at-spi2-atk (Ubuntu Focal)
   Status: New => Fix Committed

** Changed in: at-spi2-atk (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: at-spi2-atk (Ubuntu)
   Status: Fix Committed => Invalid

** Changed in: orca (Ubuntu)
   Status: In Progress => Invalid

** Tags removed: rls-ff-incoming

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

Title:
  orca ftbfs in focal (amd64 only)

Status in at-spi2-atk package in Ubuntu:
  Invalid
Status in orca package in Ubuntu:
  Invalid
Status in at-spi2-atk source package in Focal:
  Fix Committed
Status in orca source package in Focal:
  In Progress

Bug description:
  seen in a focal test rebuild:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal-updates/+build/19791402

  [...]
  checking for ATSPI2... yes
  checking for ATKBRIDGE... no
  configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met:

  Package 'atk', required by 'atk-bridge-2.0', not found

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1891478/+subscriptions

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


[Desktop-packages] [Bug 1891476] Re: gtkmm3.0 ftbfs in focal

2020-09-01 Thread Ken VanDine
** Also affects: gtkmm3.0 (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: gtkmm3.0 (Ubuntu Focal)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Changed in: gtkmm3.0 (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: gtkmm3.0 (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: gtkmm3.0 (Ubuntu)
   Status: Confirmed => Invalid

** Tags removed: rls-ff-incoming

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

Title:
  gtkmm3.0 ftbfs in focal

Status in gtkmm3.0 package in Ubuntu:
  Invalid
Status in gtkmm3.0 source package in Focal:
  Confirmed

Bug description:
  seen in a focal test rebuild, all architctures:
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200810-focal/+build/19795016

  g++ -std=c++11 -DHAVE_CONFIG_H   -I.. -I../gdk  -I../gtk  -pthread -pthread 
-I/usr/include/atkmm-1.6 -I/usr/include/giomm-2.4 
-I/usr/lib/x86_64-linux-gnu/giomm-2.4/include -I/usr/include/pangomm-1.4 
-I/usr/lib/x86_64-linux-gnu/pangomm-1.4/include -I/usr/include/glibmm-2.4 
-I/usr/lib/x86_64-linux-gnu/glibmm-2.4/include -I/usr/include/cairomm-1.0 
-I/usr/lib/x86_64-linux-gnu/cairomm-1.0/include -I/usr/include/sigc++-2.0 
-I/usr/lib/x86_64-linux-gnu/sigc++-2.0/include 
-I/usr/include/gtk-3.0/unix-print -I/usr/include/gtk-3.0 
-I/usr/include/at-spi2-atk/2.0 -I/usr/include/at-spi-2.0 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/gtk-3.0 -I/usr/include/gio-unix-2.0 -I/usr/include/cairo 
-I/usr/include/pango-1.0 -I/usr/include/fribidi -I/usr/include/harfbuzz 
-I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/pixman-1 
-I/usr/include/uuid -I/usr/include/freetype2 -I/usr/include/libpng16 
-I/usr/include/gdk-pixbuf-2.0 -I/usr/include/libmount -I/usr/include/blkid 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include 
-DDEMOCODEDIR=\"""\"  -Wdate-time -D_FORTIFY_SOURCE=2 -Wall 
-DGLIBMM_DISABLE_DEPRECATED -DGIOMM_DISABLE_DEPRECATED 
-DGTKMM_DISABLE_DEPRECATED -DGDKMM_DISABLE_DEPRECATED -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -c -o gtk-demo/gtkmm_demo-example_appwindow.o `test -f 
'gtk-demo/example_appwindow.cc' || echo './'`gtk-demo/example_appwindow.cc
  gtk-demo/demowindow.cc:54:1: error: ‘demo_columns’ function uses ‘auto’ type 
specifier without trailing return type
 54 | const auto& demo_columns()
| ^
  gtk-demo/demowindow.cc:54:1: note: deduced return type only available with 
‘-std=c++14’ or ‘-std=gnu++14’
  make[4]: *** [Makefile:733: gtk-demo/gtkmm_demo-demowindow.o] Error 1
  make[4]: *** Waiting for unfinished jobs

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

-- 
Mailing list: https://launchpad.net/~desktop-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 is too small in mutter 3.36.4-0ubuntu0.20.04.2

2020-09-01 Thread Ken VanDine
** Also affects: mutter (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: mutter (Ubuntu Focal)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

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

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

** Tags removed: rls-ff-incoming

-- 
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 is too small in mutter 3.36.4-0ubuntu0.20.04.2

Status in mutter package in Ubuntu:
  Confirmed
Status in mutter source package in Focal:
  Confirmed

Bug description:
  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:GNOME
  DistroRelease: 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 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed

2020-09-01 Thread Ken VanDine
** Also affects: pam (Ubuntu Groovy)
   Importance: Undecided
   Status: Invalid

** Also affects: gdm3 (Ubuntu Groovy)
   Importance: Low
 Assignee: Marco Trevisan (Treviño) (3v1n0)
   Status: Confirmed

** Tags removed: rls-gg-incoming

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

Title:
  gdm-smartcard pam config needs to be updated for Ubuntu and installed

Status in gdm:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in pam package in Ubuntu:
  Invalid
Status in gdm3 source package in Groovy:
  Confirmed
Status in pam source package in Groovy:
  Invalid

Bug description:
  the pam profile for gdm-smartcard is missing. gdm refuses to login
  with a smartcard. Looking at ubuntu/+source/gdm3, other pam files are
  pregenerated into debian/ and installed from there; gdm-smartcard is
  left out.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.4
  ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
  Uname: Linux 5.3.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb 28 14:30:30 2020
  InstallationDate: Installed on 2016-05-23 (1376 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901

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

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


[Desktop-packages] [Bug 1893729] Re: Keyboard shortcuts stop working

2020-09-01 Thread Ken VanDine
** Changed in: gnome-settings-daemon (Ubuntu)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Tags removed: rls-gg-incoming

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

Title:
  Keyboard shortcuts stop working

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  On Groovy keyboard shortcuts and media keys stopped working.
  Reproducible on a fresh installation and an upgrade of an installed system.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: gnome-shell 3.36.4-1ubuntu2~build1
  ProcVersionSignature: Ubuntu 5.8.0-16.17-generic 5.8.0
  Uname: Linux 5.8.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep  1 07:16:50 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2020-05-31 (92 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  RelatedPackageVersions: mutter-common 3.36.4-1ubuntu2
  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-settings-daemon/+bug/1893729/+subscriptions

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


[Desktop-packages] [Bug 1872441] Re: Switching to another channel page, then back on an installed snap shows the snap as not installed and some system snaps as uninstallable

2020-07-22 Thread Ken VanDine
** Also affects: gnome-software (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => Medium

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

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

** Changed in: gnome-software (Ubuntu)
   Status: Triaged => Confirmed

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

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

Title:
  Switching to another channel page, then back on an installed snap
  shows the snap as not installed and some system snaps as uninstallable

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

Bug description:
  When opening a details page for some snap that is already installed
  (for example the Snap Store itself), then selecting another channel
  from the Channels drop down menu, then selecting a channel from which
  the snap is installed, the details page now behaves like the snap is
  not installed, there is a "Install" button, the "Permissions" button
  disappears etc. It also seems that for some system snaps (for example
  the GTK2 Common Themes), the "Remove" button appears!

  I have a latest Snap Store from latest/stable/ubuntu-20.04 and latest
  snapd 2.44.3+20.04 from proposed repo.

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

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


[Desktop-packages] [Bug 1886854] Re: Race in load-module snap policy check in classic confinement

2020-07-08 Thread Ken VanDine
** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => James Henstridge (jamesh)

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

Title:
  Race in load-module snap policy check in classic confinement

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  SUMMARY
  =
  When running a snap in classic confinement, that needs access to 
PA_COMMAND_LOAD_MODULE and PA_COMMAND_UNLOAD_MODULE. These sometimes succeed 
and sometimes fail with "Access denied".

  After running "pacmd unload-module module-snap-policy" and unloading
  the snap policy module, these work reliably.

  I have verified this in a fresh install of Ubuntu 20.04 in a VM.

  STEPS TO REPRODUCE
  =
  a) Either build a snap with classic confinement that sends these commands on 
the pulseaudio native protocol socket. (This is how I found the bug)
  b) Or, what I did here to easier reproduce, abuse the sandbox of a random 
classic snap:

  Download the attached bug.tgz with a minimal reproducer. It contains
  the source code for a program that sends load and unload commands to
  pulse. Unfortunately `pacmd` has a pid-file check that fails inside
  the sandbox and doesn't work. The reproducer does essentially the same
  as "pacmd load/unload-module" though.

  (a pre-compiled x64 binary is also included in case you don't have a
  go compiler and dare to run an untrusted binary in a VM)

  Unpack the tgz, build it, if necessary with "go mod download && go
  build"

  Grab a random classic mode snap to use its sandbox as a test bed:

  $ sudo snap install atom --classic
  atom 1.48.0 from Snapcrafters installed

  Open a shell in its sandbox:

  snap run --shell atom
  
  Navigate to the compiled binary and execute it a few times:

  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:10 PulseAudio connection created successfully
  2020/07/08 18:46:10 Couldn't load module, error message: PulseAudio 
error: commandLoadModule -> Access denied
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:11 PulseAudio connection created successfully
  Loaded Module sucessfully at index: 40
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:12 PulseAudio connection created successfully
  Loaded Module sucessfully at index: 41
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:12 PulseAudio connection created successfully
  2020/07/08 18:46:12 Couldn't load module, error message: PulseAudio 
error: commandLoadModule -> Access denied
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:14 PulseAudio connection created successfully
  2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio 
error: commandLoadModule -> Access denied
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:14 PulseAudio connection created successfully
  2020/07/08 18:46:14 Couldn't load module, error message: PulseAudio 
error: commandLoadModule -> Access denied
  user@user-Standard-PC-Q35-ICH9-2009:~/bug$ ./bug 
  2020/07/08 18:46:15 PulseAudio connection created successfully
  2020/07/08 18:46:15 Couldn't load module, error message: PulseAudio 
error: commandLoadModule -> Access denied

  Succeeds and fails apparently at random.

  Now from a non-sandboxed shell, run

  pacmd unload-module module-snap-policy

  to unload the snap-policy module from pulseaudio, now run ./bug a few
  more times. It now succeeds reliably, every time.

  Side note, with the real program on my actual machine, the race seems
  to behave slightly differently. It seems not to work the first time an
  application is started, but closing it and reopening it seems to make
  it work pretty reliably afterwards. Restarting "snapd", causes the
  following run the snap to fail again.

  EXPECTED BEHAVIOUR
  ==

  The pulseaudio snap policy module should correctly determine and
  enforce it's policy.

  ACTUAL BEHAVIOUR
  

  The pulseaudio snap policy module seemingly at random denies access
  when the snap has the permissions to do an operation.

  ADDITIONAL INFORMATION
  ==

  $ lsb_release -rd
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  $ apt-cache policy pulseaudio
  pulseaudio:
Installed: 1:13.99.1-1ubuntu3.3
Candidate: 1:13.99.1-1ubuntu3.3
Version table:
   *** 1:13.99.1-1ubuntu3.3 500
  500 http://ch.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:13.99.1-1ubuntu3.2 500
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
   1:13.99.1-1ubuntu3 500
  500 http://ch.archive.ubuntu.com/ubuntu focal/main amd64 Packages

To manage notifications about this 

[Desktop-packages] [Bug 1884428] Re: calculator won't open (error while loading shared libraries: libgtk-3.so.0: cannot open shared object file: No such file or directory)

2020-06-29 Thread Ken VanDine
There is an interface that isn't connected.  Not sure why.

This will fix it:

sudo snap connect gnome-calculator:gnome-3-34-1804

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

Title:
  calculator won't open (error while loading shared libraries:
  libgtk-3.so.0: cannot open shared object file: No such file or
  directory)

Status in gnome-calculator package in Ubuntu:
  New

Bug description:
  new bug

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 18:21:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1858636] Re: snapd generates incomplete fontconfig caches, result in emoji rendering issue in chromium

2020-06-25 Thread Ken VanDine
For reference, this PR might fix it. https://github.com/snapcore/fc-
cache-static-builder/pull/2/files

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

Title:
  snapd generates incomplete fontconfig caches, result in emoji
  rendering issue in chromium

Status in chromium-browser package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I’ve recently noticed that Chromium no longer can display emoji. All I
  get are square boxes and some black & white symbols. E.g.
  https://getemoji.com renders like the screenshot I posted to
  https://discourse.ubuntu.com/t/call-for-testing-chromium-browser-deb-
  to-snap-transition/11179/237.

  I'm like 95% sure that this is a recent problem, and that I didn't
  have it when I first upgraded to Ubuntu 19.10 and to the snapified
  Chromium.

  Note that I don't have fonts-symbola installed, and I do have fonts-
  not-color-emoji installed.  I've also noticed a bunch of

  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:40 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:41 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file
  saus. 07 14:08:43 blynas chromium_chromium.desktop[4802]: Fontconfig error: 
Cannot load default config file

  messages in journalctl when I first launch chromium.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DRM.card0-DP-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-3:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAebfl2IdYEAAkbAQOAUCJ46sqVplVOoSYPUFQla4BxQIGAgcCpwLMA0cCBANHPzUYAoKA4H0AwIDoAHk4xAAAaKVkAoKA4J0AwIDoAHk4xAAAa/QA4Sx5aGAAKICAgICAg/ABMRyBVTFRSQVdJREUKAZACAxrxIwkHB0cQBAMBHxMSgwEAAGUDDAAQAIwK0Iog4C0QED6WAB5OMQAAGP8ANzA5TlRXRzlBOTYxCgAAQg==
   modes: 2560x1080 2560x1080 1920x1080 1920x1080 1920x1080 1920x1080 1920x1080 
1680x1050 1600x900 1280x1024 1280x1024 1280x800 1152x864 1152x864 1280x720 
1280x720 1280x720 1280x720 1024x768 1024x768 832x624 800x600 800x600 720x576 
720x480 720x480 720x480 720x480 640x480 640x480 640x480 640x480
  DRM.card0-DP-4:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-DP-5:
   enabled: disabled
   dpms: On
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-1:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-HDMI-A-2:
   enabled: disabled
   dpms: Off
   status: disconnected
   edid-base64:
   modes:
  DRM.card0-eDP-1:
   enabled: enabled
   dpms: On
   status: connected
   edid-base64: 
AP///wAGry1aAAAcAQSlHRF4Au6Vo1RMmSYPUFQBAQEBAQEBAQEBAQEBAQEBtDeAoHA4PkA6KjUAJaUQAAAYDwAg/gBBVU8KICAgICAgICAg/gBCMTMzSEFOMDUuQSAKAHA=
   modes: 1920x1080
  DiskUsage:
   Filesystem Type   Size  Used Avail Use% Mounted on
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
   tmpfs  tmpfs  7,7G  164M  7,6G   3% /dev/shm
   /dev/nvme0n1p5 ext4   284G  241G   29G  90% /
  DistroRelease: Ubuntu 19.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2019-06-12 (208 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20Q0CTO1WW
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: chromium-browser 77.0.3865.120-0ubuntu1.19.10.1
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic 
root=UUID=ad2946f7-6a38-471f-b7d1-779e8e9fd109 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10
  Snap.ChromeDriverVersion: ChromeDriver 79.0.3945.79 
(29f75ce3f42b007bd80361b0dfcfee3a13ff90b8-refs/branch-heads/3945@{#916})
  Snap.ChromiumVersion: Chromium 79.0.3945.79 snap
  Tags:  eoan wayland-session snap
  Uname: Linux 5.3.0-24-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-18 (80 days ago)
  UserGroups: adm cdrom dip docker libvirt lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 07/18/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET73W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20Q0CTO1WW
  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.modalias: 

[Desktop-packages] [Bug 1884428] Re: calculater not open

2020-06-23 Thread Ken VanDine
Please check which interfaces are connected and paste the output of:

snap connections gnome-calculator

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

Title:
  calculater not open

Status in gnome-calculator package in Ubuntu:
  Incomplete

Bug description:
  new bug

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun 21 18:21:50 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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


[Desktop-packages] [Bug 1881918] Re: Update GNOME Software to 3.36.1 in Focal

2020-06-12 Thread Ken VanDine
** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Update GNOME Software to 3.36.1 in Focal

Status in One Hundred Papercuts:
  New
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Please, consider updating the deb version of GNOME Software to 3.36.1
  in Ubuntu 20.04. The 3.36.1 release has some important bug fixes,
  translation updates and other things.

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

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


[Desktop-packages] [Bug 1883015] Re: [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.3

2020-06-12 Thread Ken VanDine
** Summary changed:

- [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.2
+ [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.3

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

Title:
  [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.3

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Focal:
  Triaged
Status in vte2.91 source package in Focal:
  Triaged
Status in gnome-terminal source package in Groovy:
  Fix Released
Status in vte2.91 source package in Groovy:
  Fix Released

Bug description:
  [ Description ]

  Update as part of the GNOME 3.36 stable release series

  [ QA ]

  Check you can launch the terminal and use it. Maybe check that
  different themes, launching a custom command, custom terminal
  launchers, etc work.

  There is a standing SRU exception for GNOME:

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  If the update causes issues they should be pretty apparent when
  running gnome-terminal.

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

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


[Desktop-packages] [Bug 1883015] Re: [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.2

2020-06-10 Thread Ken VanDine
** Changed in: gnome-terminal (Ubuntu Groovy)
   Status: New => Fix Released

** Changed in: vte2.91 (Ubuntu Groovy)
   Status: New => Fix Released

** Changed in: gnome-terminal (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: vte2.91 (Ubuntu Focal)
   Importance: Undecided => Low

** Changed in: vte2.91 (Ubuntu Focal)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: gnome-terminal (Ubuntu Focal)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

** Changed in: vte2.91 (Ubuntu Focal)
   Status: New => Triaged

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

Title:
  [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.2

Status in gnome-terminal package in Ubuntu:
  Fix Released
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in gnome-terminal source package in Focal:
  Triaged
Status in vte2.91 source package in Focal:
  Triaged
Status in gnome-terminal source package in Groovy:
  Fix Released
Status in vte2.91 source package in Groovy:
  Fix Released

Bug description:
  [ Description ]

  Update as part of the GNOME 3.36 stable release series

  [ QA ]

  Check you can launch the terminal and use it. Maybe check that
  different themes, launching a custom command, custom terminal
  launchers, etc work.

  There is a standing SRU exception for GNOME:

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  If the update causes issues they should be pretty apparent when
  running gnome-terminal.

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

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


[Desktop-packages] [Bug 1883015] [NEW] [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.2

2020-06-10 Thread Ken VanDine
Public bug reported:

[ Description ]

Update as part of the GNOME 3.36 stable release series

[ QA ]

Check you can launch the terminal and use it. Maybe check that different
themes, launching a custom command, custom terminal launchers, etc work.

There is a standing SRU exception for GNOME:

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

[ Regresison potential ]

If the update causes issues they should be pretty apparent when running
gnome-terminal.

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

** Affects: vte2.91 (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: vte2.91 (Ubuntu Focal)
 Importance: Undecided
 Status: New

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

** Affects: vte2.91 (Ubuntu Groovy)
 Importance: Undecided
 Status: New

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

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

** Also affects: vte2.91 (Ubuntu Groovy)
   Importance: Undecided
   Status: New

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

** Also affects: vte2.91 (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  [SRU] gnome-terminal to 3.36.2 and vte2.91 to 0.60.2

Status in gnome-terminal package in Ubuntu:
  New
Status in vte2.91 package in Ubuntu:
  New
Status in gnome-terminal source package in Focal:
  New
Status in vte2.91 source package in Focal:
  New
Status in gnome-terminal source package in Groovy:
  New
Status in vte2.91 source package in Groovy:
  New

Bug description:
  [ Description ]

  Update as part of the GNOME 3.36 stable release series

  [ QA ]

  Check you can launch the terminal and use it. Maybe check that
  different themes, launching a custom command, custom terminal
  launchers, etc work.

  There is a standing SRU exception for GNOME:

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  [ Regresison potential ]

  If the update causes issues they should be pretty apparent when
  running gnome-terminal.

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

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


[Desktop-packages] [Bug 1876641] Re: gnome-shell leaks hundreds of megabytes when the dock option 'show-trash' is enabled.

2020-05-26 Thread Ken VanDine
** Tags removed: rls-ff-incoming

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

Title:
  gnome-shell leaks hundreds of megabytes when the dock option 'show-
  trash' is enabled.

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

Bug description:
  Gnome shell is the single largest resident memory user on my system.

  It was hovering at ~700mb, then with a few minutes of use of the
  system (nothing in particular, mostly shell windows, one google-chrome
  window) - spiked to ~980mb or so, before retreating to 903m.

  Even with 16gb of ram, that's a huge chunk of the system.

  I've not been able to identify anything in particular that I'm doing
  that triggers the growth.

  In https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1856838/comments/5, it was suggested to open a new bug,
  instead of adding to one of the several existing bugs for this.  I'm
  happy to help try and debug this, but it's not clear where to start.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-shell 3.36.1-5ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May  3 17:32:52 2020
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-11-18 (532 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to focal on 2020-04-18 (15 days ago)

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

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


[Desktop-packages] [Bug 1880564] Re: ubuntu-drivers-common now pulls in build tools on end-user systems

2020-05-26 Thread Ken VanDine
** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Tags removed: rls-ff-incoming rls-gg-incoming

** Also affects: ubuntu-drivers-common (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: ubuntu-drivers-common (Ubuntu Focal)
   Status: New => Triaged

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

Title:
  ubuntu-drivers-common now pulls in build tools on end-user systems

Status in ubuntu-drivers-common package in Ubuntu:
  Triaged
Status in ubuntu-drivers-common source package in Focal:
  Triaged

Bug description:
  In bug 1875339, a depends on dpkg-dev was added. This is pulling in
  all of build-essential on upgrades (or just binutils and make and
  patch if you pass --no-install-recommends).

  This needs to be reverted and fixed differently.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1880564/+subscriptions

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


[Desktop-packages] [Bug 1866134] Re: Yaru icons are not shown in Gnome-Software

2020-05-19 Thread Ken VanDine
** Changed in: snap-store
   Status: Fix Committed => Fix Released

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

Title:
  Yaru icons are not shown in Gnome-Software

Status in GNOME Software:
  New
Status in snap-store:
  Fix Released
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  When an icon theme different from Adwaita is selected, the icons from
  that theme are not shown in Gnome-Software.

  This is confusing for user because they now see two different icons
  for the same application (see the screenshot upstream).

  It would be great if Gnome-Software would look for the icon in the
  selected icon theme.

  
  

  Reported upstream here: https://gitlab.gnome.org/GNOME/gnome-
  software/issues/929

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

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


[Desktop-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal

2020-05-19 Thread Ken VanDine
** Changed in: snap-store
   Status: Fix Committed => Fix Released

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

Title:
  Many apps have no icon in Software on Focal

Status in GNOME Software:
  Unknown
Status in snap-store:
  Fix Released
Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-software source package in Focal:
  Confirmed
Status in ubuntu-meta source package in Focal:
  Fix Committed

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

  
  [Impact] 

   * Some apt packages do not include an icon in snap-store

  [Test Case]

   * Open snap-store, search for GCompris and confirm there is an
  appropriate icon

  [Regression Potential]

   * Very low.  Previous Ubuntu releases including apt-config-icons
  based on the depends in gnome-software.  This just adds an apt config
  that can be used to fetch icons for apt packages via apt.

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

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


[Desktop-packages] [Bug 1866134] Re: Yaru icons are not shown in Gnome-Software

2020-05-18 Thread Ken VanDine
** Changed in: snap-store
   Status: Triaged => Fix Committed

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

Title:
  Yaru icons are not shown in Gnome-Software

Status in GNOME Software:
  New
Status in snap-store:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  When an icon theme different from Adwaita is selected, the icons from
  that theme are not shown in Gnome-Software.

  This is confusing for user because they now see two different icons
  for the same application (see the screenshot upstream).

  It would be great if Gnome-Software would look for the icon in the
  selected icon theme.

  
  

  Reported upstream here: https://gitlab.gnome.org/GNOME/gnome-
  software/issues/929

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

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


[Desktop-packages] [Bug 1750818] Re: Already installed deb packages not showing as installed when opened

2020-05-15 Thread Ken VanDine
@asciiwolf, with just the other commit it definitely fixed the issue
described in the bug report.  I spent some time looking at the other and
might cherry-pick that as well.

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

Title:
  Already installed deb packages not showing as installed when opened

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

Bug description:
  If you open an already installed local deb file using GNOME Software
  (Ubuntu Software), it shows "Install" instead of the correct "Remove"
  option.

  Steps to reproduce:
  1. Open and install any local deb file using GNOME Software.
  2. Close the GNOME Software window.
  3. Open the local deb file again in GNOME Software.

  edit: Upstream fix is now available, see comment #8.

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

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


[Desktop-packages] [Bug 1750818] Re: Already installed deb packages not showing as installed when opened

2020-05-15 Thread Ken VanDine
** Changed in: snap-store
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: snap-store
   Status: New => Confirmed

** Changed in: snap-store
   Importance: Undecided => Low

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

Title:
  Already installed deb packages not showing as installed when opened

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

Bug description:
  If you open an already installed local deb file using GNOME Software
  (Ubuntu Software), it shows "Install" instead of the correct "Remove"
  option.

  Steps to reproduce:
  1. Open and install any local deb file using GNOME Software.
  2. Close the GNOME Software window.
  3. Open the local deb file again in GNOME Software.

  edit: Upstream fix is now available, see comment #8.

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

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


[Desktop-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal

2020-05-11 Thread Ken VanDine
** Description changed:

  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.
+ 
+ 
+ [Impact] 
+ 
+  * Some apt packages do not include an icon in snap-store
+ 
+ [Test Case]
+ 
+  * Open snap-store, search for GCompris and confirm there is an
+ appropriate icon
+ 
+ [Regression Potential]
+ 
+  * Very low.  Previous Ubuntu releases including apt-config-icons based
+ on the depends in gnome-software.  This just adds an apt config that can
+ be used to fetch icons for apt packages via apt.

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

Title:
  Many apps have no icon in Software on Focal

Status in GNOME Software:
  Unknown
Status in snap-store:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in gnome-software source package in Focal:
  New
Status in ubuntu-meta source package in Focal:
  Confirmed

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

  
  [Impact] 

   * Some apt packages do not include an icon in snap-store

  [Test Case]

   * Open snap-store, search for GCompris and confirm there is an
  appropriate icon

  [Regression Potential]

   * Very low.  Previous Ubuntu releases including apt-config-icons
  based on the depends in gnome-software.  This just adds an apt config
  that can be used to fetch icons for apt packages via apt.

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

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


[Desktop-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal

2020-05-11 Thread Ken VanDine
** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-meta (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: ubuntu-meta (Ubuntu Focal)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

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

** Changed in: ubuntu-meta (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => High

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

Title:
  Many apps have no icon in Software on Focal

Status in GNOME Software:
  Unknown
Status in snap-store:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed
Status in gnome-software source package in Focal:
  New
Status in ubuntu-meta source package in Focal:
  Confirmed

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

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

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


[Desktop-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal

2020-05-08 Thread Ken VanDine
I've pushed the fix from @ximion to snap-store in the beta channel for
testing.

This fix will be published to ubuntu-20.04 after thorough testing

Thanks!

** Changed in: snap-store
   Importance: Undecided => High

** Changed in: snap-store
   Status: New => Fix Committed

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

Title:
  Many apps have no icon in Software on Focal

Status in GNOME Software:
  Unknown
Status in snap-store:
  Fix Committed
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

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

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


[Desktop-packages] [Bug 1873658] Re: Deb Files are not associated with an application that manages packages

2020-05-06 Thread Ken VanDine
** Description changed:

- When you download a DEB file within 20.04 Ubuntu Beta and you double
- click it the file is opened by the archive manager.  I would expect the
- installer to open the file just like in previous versions of Ubuntu.
+ [Impact]
+ 
+  * When a deb is downloaded the default handler is not capable of
+ installing on 20.04.
+ 
+ [Test Case]
+ 
+  We should perform this test on Ubuntu 20.04 as well as some flavors to
+ ensure we do not regress.
+ 
+  * Download any deb in firefox, double click on the downloaded file
+- On Ubuntu this should open "Ubuntu Software"
+- On flavors it should open whatever their default app for handling debs is
+ 
+ [Regression Potential]
+ 
+  * For Ubuntu, very low, rarely would a user expect to open a deb with
+ file-roller
+ 
+  * Other flavors of ubuntu are overriding this default and should not be
+ affected.  We do need to test this on other flavors to ensure their
+ defaults are still honored.

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

Title:
  Deb Files are not associated with an application that manages packages

Status in desktop-file-utils package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Invalid
Status in desktop-file-utils source package in Focal:
  Confirmed
Status in gdebi source package in Focal:
  Invalid

Bug description:
  [Impact]

   * When a deb is downloaded the default handler is not capable of
  installing on 20.04.

  [Test Case]

   We should perform this test on Ubuntu 20.04 as well as some flavors
  to ensure we do not regress.

   * Download any deb in firefox, double click on the downloaded file
 - On Ubuntu this should open "Ubuntu Software"
 - On flavors it should open whatever their default app for handling debs is

  [Regression Potential]

   * For Ubuntu, very low, rarely would a user expect to open a deb with
  file-roller

   * Other flavors of ubuntu are overriding this default and should not
  be affected.  We do need to test this on other flavors to ensure their
  defaults are still honored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions

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


[Desktop-packages] [Bug 1874893] Re: Shouldn't hardcode gnome-software

2020-04-28 Thread Ken VanDine
** Changed in: xdg-desktop-portal-gtk (Ubuntu Bionic)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: xdg-desktop-portal-gtk (Ubuntu Focal)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: xdg-desktop-portal-gtk (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: xdg-desktop-portal-gtk (Ubuntu Focal)
   Importance: Undecided => Medium

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

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

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Importance: Medium => High

** Changed in: xdg-desktop-portal-gtk (Ubuntu Bionic)
   Importance: Medium => High

** Changed in: xdg-desktop-portal-gtk (Ubuntu Focal)
   Importance: Medium => High

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

Title:
  Shouldn't hardcode gnome-software

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gtk source package in Bionic:
  Triaged
Status in xdg-desktop-portal-gtk source package in Focal:
  Triaged

Bug description:
  Currently the app chooser dialog hardcodes gnome-software as the app
  to launch to find software.  This should use the system default.  For
  example on 20.04 it should launch snap-store.ubuntu-software.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xdg-desktop-portal-gtk 1.6.0-1build1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:01:56 2020
  InstallationDate: Installed on 2019-11-04 (171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: xdg-desktop-portal-gtk
  UpgradeStatus: Upgraded to focal on 2020-02-05 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1874893/+subscriptions

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


[Desktop-packages] [Bug 1874893] [NEW] Shouldn't hardcode gnome-software

2020-04-24 Thread Ken VanDine
Public bug reported:

Currently the app chooser dialog hardcodes gnome-software as the app to
launch to find software.  This should use the system default.  For
example on 20.04 it should launch snap-store.ubuntu-software.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xdg-desktop-portal-gtk 1.6.0-1build1
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 24 15:01:56 2020
InstallationDate: Installed on 2019-11-04 (171 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: xdg-desktop-portal-gtk
UpgradeStatus: Upgraded to focal on 2020-02-05 (79 days ago)

** Affects: xdg-desktop-portal-gtk (Ubuntu)
 Importance: Medium
 Assignee: James Henstridge (jamesh)
 Status: Triaged

** Affects: xdg-desktop-portal-gtk (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: xdg-desktop-portal-gtk (Ubuntu Focal)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
 Assignee: (unassigned) => James Henstridge (jamesh)

** Changed in: xdg-desktop-portal-gtk (Ubuntu)
   Importance: Undecided => Medium

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

** Also affects: xdg-desktop-portal-gtk (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: xdg-desktop-portal-gtk (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

Title:
  Shouldn't hardcode gnome-software

Status in xdg-desktop-portal-gtk package in Ubuntu:
  Triaged
Status in xdg-desktop-portal-gtk source package in Bionic:
  New
Status in xdg-desktop-portal-gtk source package in Focal:
  New

Bug description:
  Currently the app chooser dialog hardcodes gnome-software as the app
  to launch to find software.  This should use the system default.  For
  example on 20.04 it should launch snap-store.ubuntu-software.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xdg-desktop-portal-gtk 1.6.0-1build1
  ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
  Uname: Linux 5.4.0-26-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 24 15:01:56 2020
  InstallationDate: Installed on 2019-11-04 (171 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: xdg-desktop-portal-gtk
  UpgradeStatus: Upgraded to focal on 2020-02-05 (79 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1874893/+subscriptions

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


[Desktop-packages] [Bug 1873658] Re: Deb Files are not opened by the installer 20.04

2020-04-21 Thread Ken VanDine
** Changed in: gdebi (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Deb Files are not associated with an application that manages packages

Status in desktop-file-utils package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Invalid

Bug description:
  When you download a DEB file within 20.04 Ubuntu Beta and you double
  click it the file is opened by the archive manager.  I would expect
  the installer to open the file just like in previous versions of
  Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions

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


[Desktop-packages] [Bug 1873658] Re: Deb Files are not opened by the installer 20.04

2020-04-21 Thread Ken VanDine
** Changed in: desktop-file-utils (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

Title:
  Deb Files are not opened by the installer 20.04

Status in desktop-file-utils package in Ubuntu:
  Confirmed
Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When you download a DEB file within 20.04 Ubuntu Beta and you double
  click it the file is opened by the archive manager.  I would expect
  the installer to open the file just like in previous versions of
  Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/1873658/+subscriptions

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


[Desktop-packages] [Bug 1853830] Re: [FFe] gamemode

2020-04-17 Thread Ken VanDine
** Changed in: gamemode (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [FFe] gamemode

Status in gamemode package in Ubuntu:
  Fix Released
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released

Bug description:
  [Availability]

  Builds on amd64 only in Ubuntu and syncs from Debian. GameMode was
  designed primarily as a  solution to the Intel and AMD CPU powersave
  or ondemand governors, and intended for gaming; hence why it is amd64
  only.

  [Rationale]

  We would like to enable GameMode as it allows games to request a set
  of optimisations be temporarily applied to the host OS and improve
  gaming performance.

  The Ubuntu desktop team intend to seed gamemode.

  [Security]

  No CVE/known security issue. GameMode includes an user daemon that
  modifies the CPU governors and GPU clock state through pkexec-ed
  helpers.

  [Quality assurance]

  - The desktop-packages team is subscribed to the package
  - 2 bugs in Debian BTS which are being investigated. None in LP.
  - The package is actively maintained in Debian and in sync in Ubuntu.
  - No test suite, but difficult to integrate with autopkgtest due to hardware 
requirements.

  [Dependencies]

  All the Depends: are currently in main. There are no Recommends:

  - init-system-helpers (>= 1.52)
  - libc6 (>= 2.27)
  - libsystemd0 (>= 221)
  - libdbus-1-3 (>= 1.9.14)

  [Standards compliance]

  The package is using current (dh12) standards, the standards-version
  is 4.4.0, the package is in sync from Debian.

  [Maintenance]

  Upstream is active and the desktop team is going to look after the
  package in Ubuntu.

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

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


[Desktop-packages] [Bug 1781428] Re: please enable snap mediation support

2020-04-16 Thread Ken VanDine
All the xenial autopkgtests have passed.  What do we need to do to get
these published again?

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

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Committed
Status in pulseaudio source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  IMPORTANT: if updating pulseaudio while the session is running, either
  need to reboot for the test or kill pulseaudio so it can restart with
  the new snap policy

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  $ exit # out of snap run --shell

  For strict snaps with pulseaudio:
  $ sudo snap install test-snapd-pulseaudio --edge

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  For strict snaps with audio-playback/audio-record:
  $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04
  $ sudo snap install test-snapd-audio-record --edge

  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
  audio-record

[Desktop-packages] [Bug 1870600] Re: permissions pane only shows currently-connected snap interfaces

2020-04-15 Thread Ken VanDine
I can confirm that these only show up after connecting the interface.

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

Title:
  permissions pane only shows currently-connected snap interfaces

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  The applications applet in Gnome Control Center shows permissions that
  can be toggled on and off for installed applications and snap
  packages. When viewing a Snap package, only permissions that are
  currently enabled (interface is connected in Snap terms). Viewing the
  same Snap package's permissions in Gnome Software or the Snap Store
  Snap you can see that there are more permissions that can be enabled
  which are not currently.

  I have uploaded an example of both views to highlight the discrepency
  in a screenshot at:
  https://www.dropbox.com/s/zqr35hll94d37yg/photo_2020-04-03_19-49-06.jpg?dl=0

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr  3 19:48:07 2020
  InstallationDate: Installed on 2020-03-03 (30 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200303)
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1872864] Re: appstream metadata not created

2020-04-15 Thread Ken VanDine
** Changed in: snap-store
   Status: Triaged => Invalid

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

Title:
  appstream metadata not created

Status in snap-store:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  The gnome-software packaged depends on appstream, which was bringing
  in that binary package in previous releases.  With the switch to
  seeding the snap this is causing a problem with the appstream cache
  never getting populated.  The appstream package includes an apt config
  that triggered the appstream cache refresh after update.  We need to
  explicitly seed the appstream package in ubuntu-desktop.

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

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


[Desktop-packages] [Bug 1864307] Re: Many apps have no icon in Software on Focal

2020-04-14 Thread Ken VanDine
*** This bug is a duplicate of bug 1866134 ***
https://bugs.launchpad.net/bugs/1866134

** This bug has been marked a duplicate of bug 1866134
   Yaru icons are not shown in Gnome-Software

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

Title:
  Many apps have no icon in Software on Focal

Status in snap-store:
  New
Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  Many applications have no icon displayed in GNOME Software 3.35.91 on
  latest Ubuntu Focal. See the attached screenshot.

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

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


[Desktop-packages] [Bug 1872522] Re: Ubuntu software will not install .deb files on focal fossa

2020-04-14 Thread Ken VanDine
*** This bug is a duplicate of bug 1867610 ***
https://bugs.launchpad.net/bugs/1867610

** This bug has been marked a duplicate of bug 1867610
   snap-store cannot install local deb packages

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

Title:
  Ubuntu software will not install .deb files on focal fossa

Status in gnome-software package in Ubuntu:
  Incomplete

Bug description:
  On focal fossa Ubuntu software will not install .deb files (such as
  Google Chrome installer) however gdebi has no problem with the same
  files.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-software (not installed)
  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: ubuntu:GNOME
  Date: Mon Apr 13 19:36:10 2020
  InstallationDate: Installed on 2020-04-12 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200409)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Desktop-packages] [Bug 1872864] Re: appstream metadata not created

2020-04-14 Thread Ken VanDine
** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-meta (Ubuntu)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  appstream metadata not created

Status in snap-store:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  In Progress

Bug description:
  The gnome-software packaged depends on appstream, which was bringing
  in that binary package in previous releases.  With the switch to
  seeding the snap this is causing a problem with the appstream cache
  never getting populated.  The appstream package includes an apt config
  that triggered the appstream cache refresh after update.  We need to
  explicitly seed the appstream package in ubuntu-desktop.

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

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


[Desktop-packages] [Bug 1866134] Re: Yaru icons are not shown in Gnome-Software

2020-04-14 Thread Ken VanDine
** Also affects: snap-store
   Importance: Undecided
   Status: New

** Changed in: snap-store
   Importance: Undecided => Critical

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

** Changed in: snap-store
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Yaru icons are not shown in Gnome-Software

Status in GNOME Software:
  New
Status in snap-store:
  Triaged
Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  When an icon theme different from Adwaita is selected, the icons from
  that theme are not shown in Gnome-Software.

  This is confusing for user because they now see two different icons
  for the same application (see the screenshot upstream).

  It would be great if Gnome-Software would look for the icon in the
  selected icon theme.

  
  

  Reported upstream here: https://gitlab.gnome.org/GNOME/gnome-
  software/issues/929

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

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


[Desktop-packages] [Bug 1872258] Re: GS injects invalid metadata, causing "AppStream cache update completed, but some metadata was ignored"

2020-04-11 Thread Ken VanDine
** Changed in: gnome-software (Ubuntu)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => High

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

Title:
  GS injects invalid metadata, causing "AppStream cache update
  completed, but some metadata was ignored"

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  Hi!
  GNOME Software currently injects invalid AppStream metadata in Focal, causing 
a complaint message like "AppStream cache update completed, but some metadata 
was ignored due to errors." on every APT update.
  This can be fixed by applying this patch from upstream and Debian, which was 
present in GNOME's release candidate but was accidentally reverted: 
https://salsa.debian.org/gnome-team/gnome-software/-/blob/05553c1bfa2124a12e3afe5c63de510310377036/debian/patches/02_fix-appstream-featured-data.patch

  Debian already ships this patch.
  Thanks for considering!

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

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


[Desktop-packages] [Bug 1871787] Re: Screen sharing can not be enabled from the Gnome Control Center

2020-04-11 Thread Ken VanDine
I agree with @seb128, this is probably a duplicate of 1871351.

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

Title:
  Screen sharing can not be enabled from the Gnome Control Center

Status in gnome-control-center package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu Version: Ubuntu Focal Fossa
  Package version: 1:3.36.1-1ubuntu4
  Expected: Using Screen sharing as expected and often used before
  Result: Screen sharing is disabled and can't be reenabled

  I have checked the system logs and found this entry:
  gnome-control-c[223776]: couldn't list networks: 
GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid service name 
'vino-server'

  Then I have tried to reinstall the vino package in case that something broke 
in the update yesterday. This did not help so I tried executing the binary 
manually and this worked:
  /usr/lib/vino/vino-server 
  09/04/2020 10:16:55 Autoprobing TCP port in (all) network interface
  09/04/2020 10:16:55 Listening IPv6://[::]:5900
  09/04/2020 10:16:55 Listening IPv4://0.0.0.0:5900
  09/04/2020 10:16:55 Autoprobing selected port 5900
  09/04/2020 10:16:55 Advertising security type: 'TLS' (18)
  ... (shortened)

  The problem might be something related to DBus but I'm not shure.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: gnome-control-center 1:3.36.1-1ubuntu4
  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-0ubuntu25
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  9 10:09:05 2020
  InstallationDate: Installed on 2017-11-18 (872 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to focal on 2020-04-03 (5 days ago)

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

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


[Desktop-packages] [Bug 1872111] [NEW] gnome-software should not provide ubuntu-software

2020-04-10 Thread Ken VanDine
Public bug reported:

The gnome-software deb provides an ubuntu-software desktop file.  This
is now provided by the snap-store snap so should be removed from the deb
to prevent confusion

** Affects: gnome-software (Ubuntu)
 Importance: High
 Assignee: Robert Ancell (robert-ancell)
 Status: Triaged

** Changed in: gnome-software (Ubuntu)
   Importance: Undecided => High

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

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

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

Title:
  gnome-software should not provide ubuntu-software

Status in gnome-software package in Ubuntu:
  Triaged

Bug description:
  The gnome-software deb provides an ubuntu-software desktop file.  This
  is now provided by the snap-store snap so should be removed from the
  deb to prevent confusion

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

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


[Desktop-packages] [Bug 1870089] Re: yelp ftbfs in focal

2020-04-09 Thread Ken VanDine
This was fixed with 3.36 sync from debian

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

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

Title:
  yelp ftbfs in focal

Status in yelp package in Ubuntu:
  Fix Released

Bug description:
  seen in the second focal test rebuild
  
https://launchpad.net/ubuntu/+archive/test-rebuild-20200327-focal/+build/18988549/+files/buildlog_ubuntu-focal-amd64.yelp_3.34.0-1_BUILDING.txt.gz

  if test -f "data/yelp.appdata.xml"; then d=; else d="./"; fi; \
if test -n "/usr/bin/appstream-util"; \
then /usr/bin/appstream-util --nonet validate 
${d}data/yelp.appdata.xml; fi \
&& touch data/yelp.appdata.valid
  data/yelp.appdata.xml: 
  (appstream-util:13176): dconf-CRITICAL **: 17:24:25.186: unable to create 
directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will 
not work properly.

  (appstream-util:13176): dconf-CRITICAL **: 17:24:25.186: unable to
  create directory '/sbuild-nonexistent/.cache/dconf': Permission
  denied.  dconf will not work properly.

  (appstream-util:13176): dconf-CRITICAL **: 17:24:25.187: unable to
  create directory '/sbuild-nonexistent/.cache/dconf': Permission
  denied.  dconf will not work properly.

  (appstream-util:13176): dconf-CRITICAL **: 17:24:25.187: unable to
  create directory '/sbuild-nonexistent/.cache/dconf': Permission
  denied.  dconf will not work properly.

  (appstream-util:13176): dconf-CRITICAL **: 17:24:25.187: unable to
  create directory '/sbuild-nonexistent/.cache/dconf': Permission
  denied.  dconf will not work properly.

  (appstream-util:13176): dconf-CRITICAL **: 17:24:25.187: unable to
  create directory '/sbuild-nonexistent/.cache/dconf': Permission
  denied.  dconf will not work properly.

  (appstream-util:13176): dconf-CRITICAL **: 17:24:25.187: unable to
  create directory '/sbuild-nonexistent/.cache/dconf': Permission
  denied.  dconf will not work properly.

  (appstream-util:13176): dconf-CRITICAL **: 17:24:25.187: unable to
  create directory '/sbuild-nonexistent/.cache/dconf': Permission
  denied.  dconf will not work properly.

  (appstream-util:13176): dconf-CRITICAL **: 17:24:25.187: unable to
  create directory '/sbuild-nonexistent/.cache/dconf': Permission
  denied.  dconf will not work properly.

  (appstream-util:13176): dconf-CRITICAL **: 17:24:25.187: unable to create 
directory '/sbuild-nonexistent/.cache/dconf': Permission denied.  dconf will 
not work properly.
  FAILED:
  • tag-missing   :  required [use 
https://odrs.gnome.org/oars]
  • tag-missing   :  required
  Validation of files failed
  make[3]: *** [Makefile:4123: data/yelp.appdata.valid] Error 1
  make[3]: Leaving directory '/<>'
  make[2]: *** [Makefile:3358: check-recursive] Error 1
  make[2]: Leaving directory '/<>'
  make[1]: *** [Makefile:3654: check] Error 2
  make[1]: Leaving directory '/<>'
  dh_auto_test: error: make -j4 check VERBOSE=1 returned exit code 2

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

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


[Desktop-packages] [Bug 1870184] Re: Snap store not showing ubuntu repository apt apps inthe store

2020-04-01 Thread Ken VanDine
We're working on this already, it seems hit and miss.  I have a fresh
focal VM from this morning and it does find Tweaks if I search for it,
however my focal desktop doesn't find it right now.  Same version of
snap-store.

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

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

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

** Changed in: snap-store
   Status: New => Confirmed

** Changed in: snap-store
   Importance: Undecided => High

** Changed in: snap-store
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

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

Title:
  Snap store not showing ubuntu repository apt apps inthe store

Status in snap-store:
  Confirmed
Status in gnome-desktop package in Ubuntu:
  Invalid
Status in gnome-software package in Ubuntu:
  Invalid
Status in gnome-tweaks package in Ubuntu:
  Invalid

Bug description:
  OS : Ubuntu 20.04 (20200401)
  Problem : repository (apt) apps are not showing

  Problem Simulation:
  Install ubuntu 20.04 current daily build > open Snap Store> Search 
gnome tweak (or anyother apt apps) > no results

  Expected Solution:
  The Snap store should show repository apps or the gnome software 
should have installed by default.
  Thank you

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

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


[Desktop-packages] [Bug 1869905] [NEW] OnlyShowIn and NotShowIn not properly honored

2020-03-31 Thread Ken VanDine
Public bug reported:

glib provides g_app_info_should_show to determine if a desktop file
should be shown in the app grid based on OnlyShowIn and NotShowIn using
XDG_CURRENT_DESKTOP.  This isn't being honored in gnome-shell when
NotShowIn=ubuntu:GNOME or OnlyShowIn=ubuntu:GNOME and
XDG_CURRENT_DESKTOP is ubuntu:GNOME.

glib does have tests for this that are still passing and @seb128 wrote a
simple test case to show the glib API does the right thing.

The snap-store snap in the beta channel provides two desktop files, one
to be displayed when XDG_CURRENT_DESKTOP is ubuntu:GNOME and one for
when it isn't.

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


** Tags: rls-ff-incoming

** Attachment added: "glib test case"
   
https://bugs.launchpad.net/bugs/1869905/+attachment/5343824/+files/onlyshowin.c

** Tags added: rls-ff-incoming

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

Title:
  OnlyShowIn and NotShowIn not properly honored

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  glib provides g_app_info_should_show to determine if a desktop file
  should be shown in the app grid based on OnlyShowIn and NotShowIn
  using XDG_CURRENT_DESKTOP.  This isn't being honored in gnome-shell
  when NotShowIn=ubuntu:GNOME or OnlyShowIn=ubuntu:GNOME and
  XDG_CURRENT_DESKTOP is ubuntu:GNOME.

  glib does have tests for this that are still passing and @seb128 wrote
  a simple test case to show the glib API does the right thing.

  The snap-store snap in the beta channel provides two desktop files,
  one to be displayed when XDG_CURRENT_DESKTOP is ubuntu:GNOME and one
  for when it isn't.

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

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


  1   2   3   4   5   6   7   8   9   10   >