[Desktop-packages] [Bug 1978053] Re: lubuntu kinetic live - firefox can't open libreoffice help file

[Maciej Borzecki]

I was able to confirm the problem exists with snapd 2.56+22.10. I've
also confirmed that it works correctly with snapd from edge as some
fixes were landed in master already.

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

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

Title:
  lubuntu kinetic live - firefox can't open libreoffice help file

Status in libreoffice package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Fix Committed

Bug description:
  Lubuntu kinetic jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  To re-create 
  - boot live media (Lubuntu kinetic)
  - open libreoffice (any, but I used the base app here)
  - seek help in menu or press F1

  ** Expected Results

  Firefox opens with some helpful text

  ** Actual Results

  Firefox opens at URL :
  
file:///usr/share/libreoffice/help/index.html?Target=swriter/.uno%3AHelpIndex=en-
  US=UNIX=7.3

  with message
  ---
  File not found

  Firefox can’t find the file at
  
/usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en-
  US=UNIX=7.3.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  
  ** Background Notes

  
  This issue was reported before in jammy; but was marked RESOLVED.  The 
directory though is different so something has changed..  I believe I'm 
thinking of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210

  I'm unsure if this is a firefox issue, Lubuntu config issue, or
  Libreoffice issue, but snap'd apps have issues due to confinement thus
  firefox issue is I fear suspected.

  Reported also at https://bugzilla.mozilla.org/show_bug.cgi?id=1773414
  though i suspect issue may not actually be with firefox snap.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.472
  CurrentDesktop: LXQt
  Date: Thu Jun  9 04:41:26 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1978053] Re: lubuntu kinetic live - firefox can't open libreoffice help file

[Maciej Borzecki]

What is the version of snapd (both the deb and the snapd snap)? There
was a related fix in snapd introduced in
https://github.com/snapcore/snapd/commit/103c652f30089c81d69a89714fb5a076c94ed365
but it is available only in snapd 2.56 and later.

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

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

Title:
  lubuntu kinetic live - firefox can't open libreoffice help file

Status in libreoffice package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  Lubuntu kinetic jammy live QA-test on
  - dell [optiplex] 780 (c2q-q9400, 8gb, amd/ati cedar radeon hd 
5000/6000/7350/8350)

  To re-create 
  - boot live media (Lubuntu kinetic)
  - open libreoffice (any, but I used the base app here)
  - seek help in menu or press F1

  ** Expected Results

  Firefox opens with some helpful text

  ** Actual Results

  Firefox opens at URL :
  
file:///usr/share/libreoffice/help/index.html?Target=swriter/.uno%3AHelpIndex=en-
  US=UNIX=7.3

  with message
  ---
  File not found

  Firefox can’t find the file at
  
/usr/share/libreoffice/help/index.html?Target=swriter/.uno:HelpIndex=en-
  US=UNIX=7.3.

  Check the file name for capitalization or other typing errors.
  Check to see if the file was moved, renamed or deleted.
  ---

  
  ** Background Notes

  
  This issue was reported before in jammy; but was marked RESOLVED.  The 
directory though is different so something has changed..  I believe I'm 
thinking of https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1951210

  I'm unsure if this is a firefox issue, Lubuntu config issue, or
  Libreoffice issue, but snap'd apps have issues due to confinement thus
  firefox issue is I fear suspected.

  Reported also at https://bugzilla.mozilla.org/show_bug.cgi?id=1773414
  though i suspect issue may not actually be with firefox snap.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libreoffice (not installed)
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.472
  CurrentDesktop: LXQt
  Date: Thu Jun  9 04:41:26 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220608)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Desktop-packages] [Bug 1776873] Re: Whitelisted allowedURLschemes breaks some desktop apps

[Maciej Borzecki]

Please make sure that you have xdg-desktop-portal installed, along with
xdg-desktop-portal-gtk (or xdg-desktop-portal-kde). The hardcoded list
of schemes is a legacy feature  which should only be relevant for very
old systems such as 16.04 and should not be getting any updates.

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

Title:
  Whitelisted allowedURLschemes breaks some desktop apps

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

Bug description:
  
https://github.com/snapcore/snapd/blob/7952972d4897e085030b288e44dc98b824f6723a/userd/launcher.go#L55

  snapd has a hard-coded list of allowed URL schemes. Currently that is
  limited to "http", "https", "mailto", "snap".

  We have a number of applications in the store which are trying to use
  protocol handlers outside this scope and break when that's not
  possible.

  e.g.

  Telegram Desktop: tg:/
  Github Desktop: git:/
  IRCCloud Desktop: irc:/

  These are the ones I know of, others may also be affected. Can we
  please at least expand the list to those that we know of, and perhaps
  research other popular protocol handlers?

  Ideally we wouldn't have a whitelist, because this delays our ability
  to land new applications with as-yet unknown url schemes.

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


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

[Desktop-packages] [Bug 1970025] Re: Tried to update Snapd from the GUI, it logged me out

[Maciej Borzecki]

I suspect this was caused by udev reload, which we have observed
previously and I believe it was fixed in gdm by
https://gitlab.gnome.org/GNOME/gdm/-/merge_requests/175

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

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

Title:
  Tried to update Snapd from the GUI, it logged me out

Status in gdm3 package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  This is a fresh install of 22.04 on X86_64, with Nvidia drivers,
  running X11 (can't get Wayland, but there already seems to be a bug
  report about that)

  Steps to reproduce
  1. launched Software Updater from the dashboard
  2. it asked to update snapd, I confirmed by click

  After a second the screen turned all black and after another second I
  was presented with the login screen

  I logged back in, ran Software Updater, the system was up to date

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


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

[Desktop-packages] [Bug 1963861] Re: Can't tell what application will be launched with custom schemes

[Maciej Borzecki]

@alexmurray that code has never listed or show which application would
handle given URL scheme. The change affected the implementation of
io.snapcraft.Launcher, which is only called as a fallback when a snap
calls xdg-open inside it's namespace. The primary handler that is tried
goes through the desktop portal https://flatpak.github.io/xdg-desktop-
portal/#gdbus-org.freedesktop.portal.OpenURI which AFAIU prompts to
select an application for some number of attempts, which then goes away
if the user chose consistently chose the same application each time. So
if the prompt was originally shows, but now it's not, my guess would be
that it's the portal.

The fallback code would open an application for which there is a desktop
handler registered in the mime db. Perhaps we could improve that to show
a prompt? Anyways, this code isn't part of any stable release yet.

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

Title:
  Can't tell what application will be launched with custom schemes

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

Bug description:
  If a url is opened such as:

  mailto:
  feed:

  The firefox snap package no longer shows what application will be
  launched. This means that websites can potentially trick a user to
  start applications.

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


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

[Desktop-packages] [Bug 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP

[Maciej Borzecki]

Can you try running `sudo snap set system experimental.robust-mount-
namespace-updates=false` ?

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

Title:
  The snap being updated in the background causes both old and new tabs
  to die to SIGTRAP

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

Bug description:
  The last few background updates of chromium have made some old tabs
  suddenly crash with SIGTRAP and it also makes it impossible to open
  new tabs, those die instantly with a SIGTRAP as well.

  This is incredibly destructive to whatever might be the dying tabs'
  unsaved state and there's no warning about it. Yet again a snap-
  related change rolled out to users with absolutely amateur-tier
  testing.

  Ubuntu: 20.04.2
  Snap: 2.48+20.04
  Chromium: 88.0.4324.150

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

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

[Desktop-packages] [Bug 1581713] Re: Ubuntu Software always asks for an Ubuntu Single Sign-On account when installing or removing a snap package

[Maciej Borzecki]

@ostraaten does running `snap install teams-for-linux` fail for you? If
so, please file a bug.

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

Title:
  Ubuntu Software always asks for an Ubuntu Single Sign-On account when
  installing or removing a snap package

Status in Ubuntu GNOME:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in snapd package in Ubuntu:
  Fix Released

Bug description:
  If I try to uninstall a snap using Ubuntu Software, it asks for an Ubuntu 
Single Sign-On account. It seems strange since if I use a terminal and do:
  $ sudo snap remove john-the-ripper

  Everything works as expected.

  BTW: Ubuntu Software takes ages to find out the size of the snap
  package.

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

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

[Desktop-packages] [Bug 1876083] Re: chromium snap from focal fails DNS lookups, or delays them

[Maciej Borzecki]

Probably needs more intricate knowledge of Chromium.

Just for the record, do you see any AppArmor denials when that happens?

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

** Changed in: snapd
   Status: New => Incomplete

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

Title:
  chromium snap from focal fails DNS lookups, or delays them

Status in snapd:
  Incomplete
Status in chromium-browser package in Ubuntu:
  New

Bug description:
  When working with the chromium snap included in focal, it sometimes
  takes a few seconds to lookup an URL, sometimes it cannot resolve the
  hostname of the URL at all.

  Doing the same browsing using firefox doesn't show such behavior, no
  timeouts, no failed lookups, no delays.

  Any way how to debug that?  That is using IPv6 only.

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

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

[Desktop-packages] [Bug 1862465] [NEW] recent HP LaserJet models cannot be used on 18.04

[Maciej Borzecki]

Public bug reported:

The hplip 3.17.10 version available in bionic is too old to support
recent low cost, consumer grade HP printers. For example, HP LaserJet
MFP M28 is supported only from hplip version 3.18.3 up. Meaning, the
current LTS release for widely available peripherals.

AFAICT, there's no other versions in bionic-updates nor bionic-
backports. Focal is currently at 3.19.12.

Not having a newer version available from the repositories, the users
need to download and install the driver directly form HP's support site,
or hunt down a random PPA that built hplip for Bionic.

Please consider adding a more recent version of hplip to bionic-
backports, so that the users don't have to deal with installing those
drivers from random unverified sources.

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

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

Title:
  recent HP LaserJet models cannot be used on 18.04

Status in hplip package in Ubuntu:
  New

Bug description:
  The hplip 3.17.10 version available in bionic is too old to support
  recent low cost, consumer grade HP printers. For example, HP LaserJet
  MFP M28 is supported only from hplip version 3.18.3 up. Meaning, the
  current LTS release for widely available peripherals.

  AFAICT, there's no other versions in bionic-updates nor bionic-
  backports. Focal is currently at 3.19.12.

  Not having a newer version available from the repositories, the users
  need to download and install the driver directly form HP's support
  site, or hunt down a random PPA that built hplip for Bionic.

  Please consider adding a more recent version of hplip to bionic-
  backports, so that the users don't have to deal with installing those
  drivers from random unverified sources.

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

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

[Desktop-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

[Maciej Borzecki]

Nonetheless it isn't clear whether it's a snapd problem or the actual
libraries. Switching to confirmed in snapd, but needs investigation from
desktop team too.

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

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  New
Status in gnome-themes-extra package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions

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

[Desktop-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

[Maciej Borzecki]

I've seen this happen occasionally with snaps on Arch too.

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  New
Status in gnome-themes-extra package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions

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

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

[Maciej Borzecki]

@sean

The snap command (part of snapd) takes care of
~/snap/packagename/current/, anything below (including .themes) is
handled by the actual snap package. I would look into desktop extensions
added by snapcraft.

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

Title:
  [snap] Broken link in theme directory

Status in gnome-characters package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Invalid

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

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

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

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

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

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

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

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

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

  ---

  Further investigation
  -

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

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

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

[Desktop-packages] [Bug 1850977] Re: Snap installs software without user having sudo access

[Maciej Borzecki]

Not sure whether removing files that came with distro packages is the
best idea long term. I think a better option would be to drop in a
custom rule that runs before the default ones. As usual ArchWiki has
some examples:
https://wiki.archlinux.org/index.php/Polkit#Administrator_identities

Specifically, if I'm reading this right, putting the following rule in
/etc/polkit-1/rules.d/00-override.rules should be enough:

/* Always authenticate Admins by prompting for the root
 * password, similar to the rootpw option in sudo
 */
polkit.addAdminRule(function(action, subject) {
return ["unix-user:root"];
});

Having this it's easy to build a package that can be later distributed
to other workstations.

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

Title:
  Snap installs software without user having sudo access

Status in gnome-software package in Ubuntu:
  Invalid
Status in policykit-1 package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Invalid

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
   3.28.1-0ubuntu4.18.04.12 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 3.28.1-0ubuntu4.18.04.8 100
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64

  What I expect to happen:
Software is not installed for a user without sudo access.

  What does happen:
  I'm logging in with an LDAP user. This user does not have sudo access.

  When I select software from gnome-software ("Ubuntu Software"), it
  pops up and asks for my users password. I enter this in, and the
  software then installs (tested with blender, libreoffice, opencl
  driver).

  My user does *not* have sudo access on the system.

  $ sudo su -
  [sudo] password for jason: 
  jason is not in the sudoers file.  This incident will be reported.

  It appears these *may* be being installed with Snaps ... which still:

  How, without having root access, can an unprivileged user install
  something onto the system?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 13:53:03 2019
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/1850977/+subscriptions

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

[Desktop-packages] [Bug 1850977] Re: Snap installs software without user having sudo access

[Maciej Borzecki]

I looked at the policy used by PackageKit. I believe gnome-software uses
it as a backend, so can you try installing something that is
specifically not a snap?

At this point, all snapd does is ask PolicyKit whether given the policy,
the user can install a package. PolicyKit responds with yes, therefore
the installation can proceed. There's not much we can do inside the
declared policy, as the defaults are fine IMO.

>From my perspective, this should likely be investigated by someone more
familiar with PolicyKit to find out why it's treating your user as
admin.

** Also affects: policykit-1 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Snap installs software without user having sudo access

Status in policykit-1 package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Incomplete

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  $ apt-cache policy gnome-software
  gnome-software:
Installed: 3.28.1-0ubuntu4.18.04.8
Candidate: 3.28.1-0ubuntu4.18.04.12
Version table:
   3.28.1-0ubuntu4.18.04.12 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
   *** 3.28.1-0ubuntu4.18.04.8 100
  100 /var/lib/dpkg/status
   3.28.1-0ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64

  What I expect to happen:
Software is not installed for a user without sudo access.

  What does happen:
  I'm logging in with an LDAP user. This user does not have sudo access.

  When I select software from gnome-software ("Ubuntu Software"), it
  pops up and asks for my users password. I enter this in, and the
  software then installs (tested with blender, libreoffice, opencl
  driver).

  My user does *not* have sudo access on the system.

  $ sudo su -
  [sudo] password for jason: 
  jason is not in the sudoers file.  This incident will be reported.

  It appears these *may* be being installed with Snaps ... which still:

  How, without having root access, can an unprivileged user install
  something onto the system?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-software 3.28.1-0ubuntu4.18.04.8
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 13:53:03 2019
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-limba   N/A
   gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.8
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.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/policykit-1/+bug/1850977/+subscriptions

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

[Desktop-packages] [Bug 1850282] Re: snap cannot be run while being upgraded − no user feedback

[Maciej Borzecki]

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

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

Title:
  snap cannot be run while being upgraded − no user feedback

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  I've just upgraded to Ubuntu 19.10 with the new snap version of
  Chromium a week or two ago

  On starting my system today, I found that Chromium had disappeared
  from the launcher and wasn't even in the apps list.   using the
  command 'chromium' didn't work either, giving me the message that
  chromium wasn't installed.   "You can install it using snap install
  chromium".  Then when I try to install it, I get the message "chromium
  is already installed".

  After about 10 minutes of digging around, I discovered that the
  chromium snap was disabled.  I couldn't enable it because it was being
  refreshed.

  Come on!  this is unacceptable behaviour for any tool but especially a
  browser which must be one of the most heavily used applications on
  Ubuntu.  This will really hit the reputation of ubuntu with any user
  who has to take maybe more than 10 minutes to discover the problem, or
  may never discover it - Chromium may just mysteriously reappear some
  time later.

  Desired behaviour:   Never disappear.  Allow refresh to happen under the 
covers, transparently (as it used to with apt).
  Minimally acceptable behaviour: never disappear, but display a message 
"chromium is being refreshed.  Please try later".

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  channels:
stable:78.0.3904.70 2019-10-29 (920) 160MB -
candidate: 78.0.3904.70 2019-10-29 (920) 160MB -
beta:  78.0.3904.70 2019-10-22 (907) 165MB -
edge:  79.0.3941.4  2019-10-21 (905) 159MB -
  installed:   78.0.3904.70(917) 167MB disabled

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

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

[Desktop-packages] [Bug 1850282] Re: snap cannot be run while being upgraded − no user feedback

[Maciej Borzecki]

** Changed in: snapd
   Status: New => In Progress

** Changed in: snapd
 Assignee: (unassigned) => Zygmunt Krynicki (zyga)

** Changed in: snapd
   Importance: Undecided => Medium

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

Title:
  snap cannot be run while being upgraded − no user feedback

Status in snapd:
  In Progress
Status in chromium-browser package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  New

Bug description:
  I've just upgraded to Ubuntu 19.10 with the new snap version of
  Chromium a week or two ago

  On starting my system today, I found that Chromium had disappeared
  from the launcher and wasn't even in the apps list.   using the
  command 'chromium' didn't work either, giving me the message that
  chromium wasn't installed.   "You can install it using snap install
  chromium".  Then when I try to install it, I get the message "chromium
  is already installed".

  After about 10 minutes of digging around, I discovered that the
  chromium snap was disabled.  I couldn't enable it because it was being
  refreshed.

  Come on!  this is unacceptable behaviour for any tool but especially a
  browser which must be one of the most heavily used applications on
  Ubuntu.  This will really hit the reputation of ubuntu with any user
  who has to take maybe more than 10 minutes to discover the problem, or
  may never discover it - Chromium may just mysteriously reappear some
  time later.

  Desired behaviour:   Never disappear.  Allow refresh to happen under the 
covers, transparently (as it used to with apt).
  Minimally acceptable behaviour: never disappear, but display a message 
"chromium is being refreshed.  Please try later".

  $ snap info chromium
  name:  chromium
  summary:   Chromium web browser, open-source version of Chrome
  publisher: Canonical✓
  contact:   
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bugs?field.tag=snap
  license:   unset
  description: |
An open-source browser project that aims to build a safer, faster, and more
stable way for all Internet users to experience the web.
  commands:
- chromium.chromedriver
- chromium
  snap-id:  XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R
  tracking: stable
  channels:
stable:78.0.3904.70 2019-10-29 (920) 160MB -
candidate: 78.0.3904.70 2019-10-29 (920) 160MB -
beta:  78.0.3904.70 2019-10-22 (907) 165MB -
edge:  79.0.3941.4  2019-10-21 (905) 159MB -
  installed:   78.0.3904.70(917) 167MB disabled

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

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

[Desktop-packages] [Bug 1840925] Re: [snap] chromium doesn't start under Wayland with GNOME 3.33

[Maciej Borzecki]

** Changed in: snapd
   Status: Fix Committed => Fix Released

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

Title:
  [snap] chromium doesn't start under Wayland with GNOME 3.33

Status in snapd:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Fix Released

Bug description:
  (initially reported by Laney on IRC)

  I upgraded my eoan VM with silo 3762¹ which contains the gnome 3.33.90
  update, and after logging out and back into a Wayland session, the
  chromium snap fails to start:

  $ chromium
  No protocol specified
  (chrome:1917): Gtk-WARNING **: 16:08:39.262: cannot open display: :0

  I'm seeing the following denial in the journal:

  name="/run/user/1000/.mutter-Xwaylandauth.5J7F6Z",
  requested_mask="r", denied_mask="r"

  ¹ https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/3762/+packages

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

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

[Desktop-packages] [Bug 1835024] Re: Links triggered within most snap apps open in a separate browser session

[Maciej Borzecki]

I could reproduce this problem using 18.04.3 live CD using Slack and
Atom. However, I don't think the problem is caused by snapd.

Slack, Skype and Atom are all classic snaps so they have full access to
the system. With Slack installed, clicking on the 'get started' link was
enough to get another Firefox window open. I collected the strace log. A
relevant piece is here:

10782 execve("/usr/local/sbin/xdg-open", ["xdg-open", 
"https://slack.com/ssb/add;], 0xb6c9467b000 /* 75 vars */) = -1 ENOENT (No such 
file or directory)
10782 execve("/usr/local/bin/xdg-open", ["xdg-open", 
"https://slack.com/ssb/add;], 0xb6c9467b000 /* 75 vars */) = -1 ENOENT (No such 
file or directory)
10782 execve("/usr/sbin/xdg-open", ["xdg-open", "https://slack.com/ssb/add;], 
0xb6c9467b000 /* 75 vars */) = -1 ENOENT (No such file or directory)
10782 execve("/usr/bin/xdg-open", ["xdg-open", "https://slack.com/ssb/add;], 
0xb6c9467b000 /* 75 vars */) = 0
10784 execve("/usr/bin/which", ["which", 
"gnome-default-applications-prope"...], 0x560d5fb594a8 /* 75 vars */) = 0
10784 +++ exited with 1 +++
10782 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=10784, 
si_uid=999, si_status=1, si_utime=0, si_stime=0} ---
10785 execve("/usr/bin/gio", ["gio", "help", "open"], 0x560d5fb594a8 /* 75 vars 
*/) = 0
10785 +++ exited with 0 +++
10782 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=10785, 
si_uid=999, si_status=0, si_utime=0, si_stime=0} ---
10786 execve("/usr/bin/gio", ["gio", "open", "https://slack.com/ssb/add;], 
0x560d5fb594a8 /* 75 vars */) = 0
10789 +++ exited with 0 +++
10786 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=10789, 
si_uid=999, si_status=0, si_utime=0, si_stime=0} ---
10790 execve("/usr/local/sbin/firefox", ["firefox", 
"https://slack.com/ssb/add;], 0x563485f1c6e0 /* 77 vars */) = -1 ENOENT (No 
such file or directory)
10790 execve("/usr/local/bin/firefox", ["firefox", 
"https://slack.com/ssb/add;], 0x563485f1c6e0 /* 77 vars */) = -1 ENOENT (No 
such file or directory)
10790 execve("/usr/sbin/firefox", ["firefox", "https://slack.com/ssb/add;], 
0x563485f1c6e0 /* 77 vars */) = -1 ENOENT (No such file or directory)
10790 execve("/usr/bin/firefox", ["firefox", "https://slack.com/ssb/add;], 
0x563485f1c6e0 /* 77 vars */) = 0
10791 +++ exited with 0 +++

Notice how slack attempts to run xdg-open (and does so successfully at
some point), then it proceeds to run `gio open ..`, and again does that
successfully, finally it just runs firefox with the URL. I believe this
is what triggers the new window to appear.

Another observation for Slack on 18.04 is that gnome-shell groups the
Firefox window *with* the slack one.

I tried diffing the environment between the inside and outside of snap:

--- in-shell2019-10-17 13:43:59.474529198 +
+++ in-snap-shell   2019-10-17 13:44:09.186624002 +
@@ -2,13 +2,14 @@ CLUTTER_IM_MODULE=xim
 COLORTERM=truecolor
 DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/999/bus
 DESKTOP_SESSION=ubuntu
+DISABLE_WAYLAND=1
 DISPLAY=:0
 GDMSESSION=ubuntu
 GJS_DEBUG_OUTPUT=stderr
 GJS_DEBUG_TOPICS=JS ERROR;JS LOG
 GNOME_DESKTOP_SESSION_ID=this-is-deprecated
 GNOME_SHELL_SESSION_MODE=ubuntu
-GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/113b5986_bfcc_47c1_8317_a37a7600b396
+GNOME_TERMINAL_SCREEN=/org/gnome/Terminal/screen/d399bea3_fa8f_4330_842a_0eaaac439533
 GNOME_TERMINAL_SERVICE=:1.143
 GPG_AGENT_INFO=/run/user/999/gnupg/S.gpg-agent:0:1
 GTK_IM_MODULE=ibus
@@ -27,7 +28,22 @@ QT_ACCESSIBILITY=1
 QT_IM_MODULE=ibus
 
SESSION_MANAGER=local/ubuntu:@/tmp/.ICE-unix/4000,unix/ubuntu:/tmp/.ICE-unix/4000
 SHELL=/bin/bash
-SHLVL=1
+SHLVL=2
+SNAP_ARCH=amd64
+SNAP_COMMON=/var/snap/atom/common
+SNAP_CONTEXT=yBpkxSLRYnnStMxl74JWW8f6GLLQDXlD6qC2rdmXVjsh
+SNAP_COOKIE=yBpkxSLRYnnStMxl74JWW8f6GLLQDXlD6qC2rdmXVjsh
+SNAP_DATA=/var/snap/atom/238
+SNAP_INSTANCE_KEY=
+SNAP_INSTANCE_NAME=atom
+SNAP_LIBRARY_PATH=/var/lib/snapd/lib/gl:/var/lib/snapd/lib/gl32:/var/lib/snapd/void
+SNAP_NAME=atom
+SNAP_REEXEC=
+SNAP_REVISION=238
+SNAP=/snap/atom/238
+SNAP_USER_COMMON=/home/ubuntu/snap/atom/common
+SNAP_USER_DATA=/home/ubuntu/snap/atom/238
+SNAP_VERSION=1.40.1
 SSH_AGENT_PID=4095
 SSH_AUTH_SOCK=/run/user/999/keyring/ssh
 TERM=xterm-256color
@@ -43,7 +59,7 @@ XDG_CONFIG_DIRS=/etc/xdg/xdg-ubuntu:/etc
 XDG_CURRENT_DESKTOP=ubuntu:GNOME
 
XDG_DATA_DIRS=/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop
 XDG_MENU_PREFIX=gnome-
-XDG_RUNTIME_DIR=/run/user/999
+XDG_RUNTIME_DIR=/run/user/999/snap.atom
 XDG_SEAT=seat0
 XDG_SESSION_DESKTOP=ubuntu
 XDG_SESSION_ID=2

However I could still spawn a separate Firefox window using a simple
`gio open http://`.

I've proceeded to install Chromium and set it to be my default browser.
At this point all the links and xdg-open calls I tried would open a new
tab in the current Chromium window.

Perhaps the problem is actually with Firefox and the method it uses to
find out whether there's antoher instance already running.

-- 
You received this bug