** Changed in: chromium-browser (Ubuntu)
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/1732482
Title:
[snap] doesn't properly sa
Nathan - yes, I checked stable only. When I first reported this, the
desktop icon didn't work at all on stable, so I was pleased to see it
working now.
I did see the app icon on the desktop though - that seems to differ from
Julian's tests.
Seeing it work on the desktop was good. Of course it wou
WBGSReject, you seem to have tested stable! And apparently you observed
the same as Julian (#34) in test A. So I also extend my question to you:
Do you expect the PWA on the desktop or as a launcher?
I'll be investigating if there is any consensus on that, but otherwise I
might simply combine the
Thanks for testing!
Julian, I think you already know that and just wanted to perform
thorough testing, but in case it was not clear, the fix is not yet in
stable.
Yet you noted something in test case A:
> File chrome-pdplehbldmmknfihajdehomkoigcbhib-Default.desktop was
created in ~/Desktop
Did
A. Tested https://signals.rotor-rig.com/ with stable version snap x64
(117.0.5938.88):
File chrome-pdplehbldmmknfihajdehomkoigcbhib-Default.desktop was created in
~/Desktop
#!/usr/bin/env xdg-open
[Desktop Entry]
Version=1.0
Terminal=false
Type=Application
Name=Signals
Exec=/snap/bin/chromium --
I have Chromium on Ubuntu 22.04.3 LTS and Chromium 116.0.5845.187
(Official Build) snap (64-bit).
I can confirm that my PWA does now install on my desktop. I have to
right-click the icon and select "Allow Launching" and then it works
correctly.
Thanks to everyone who worked on this.
My PWA used
This is supposedly fixed in edge and beta channels (x86 and ARMv8):
snap refresh --edge chromium
#Or
snap refresh --beta chromium
#And then connect the required plugs:
snap connect chromium:dot-local-share-applications
snap connect chromium:dot-local-share-icons
Your repor
** Changed in: chromium-browser (Ubuntu)
Status: In Progress => Fix Committed
--
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/1732482
Title:
[snap] doesn't properly sav
** Changed in: chromium-browser (Ubuntu)
Status: Triaged => In Progress
** Changed in: chromium-browser (Ubuntu)
Assignee: (unassigned) => Nathan Teodosio (nteodosio)
** Description changed:
For chrome apps, the create shortcuts action should create desktop files
but it doesn't.
For Youtube Music, I ended up setting the file like this:
```
#!/usr/bin/env xdg-open
[Desktop Entry]
Version=1.0
Terminal=false
Type=Application
Name=YouTube Music
Exec=/snap/bin/chromium --profile-directory=Default
--app-id=cinhimbnkkaeohfgghhklpknlkffjgod
Icon=/home/MYUSER/snap/chromium/common
** Changed in: chromium-browser (Ubuntu)
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
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/1732482
Title:
[snap] doesn't p
Yup, same with any PWA (or site). After almost 5(!!!) years, still no
progress here. Google being the obvious winner since that's the *only*
browser remaining where PWA's 'just work'. Would really appreciate a
response to #26.
--
You received this bug notification because you are a member of Desk
I still have the same issue installing Youtube Music Web app
(https://music.youtube.com/) in Ubuntu 22.04.
--
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/1732482
Title:
[snap
For Ubuntu users at least :
in the Exec line of the .desktop just replace the beginning
/snap/chromium//usr/lib/chromium-browser/chrome
by
chromium-browser
Maybe also look at Web App Manager offered by Mint team.
…and now Firefox will be packaged as a snap, what a sad joke.
--
You recei
Just quite bit of input. I landed here because of the same issue on
Chrome -- not Chromium. Well, my searching first landed me correctly on
a bug filed under "Chrome Browser", and that bug was shut down because
it was determined a duplicate of this one. And early in this thread it
was put to the s
@Sebastian Bacher - genuine question: does not a single person in the
chromium-snap team use this feature? Because I can't think of any other
reason why this regression (when compared to regular chromium) is
treated like a 'wishlist' item. Please, enlighten me.
Currently, on any Ubuntu recent Ubun
** Tags removed: chrome
** Tags added: desktop-lts-wishlist
--
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/1732482
Title:
[snap] doesn't properly save desktop files for "crea
Such a shame users are being pushed towards regular Chrome, since that's
the only feasible 'solution' to this bug for most users. Personally,
I've completely given up on Chromium for Ubuntu 20.04+.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscr
The workaround is only part of the solution, the link still opens as a
tab in regular chromium window rendering it useless. PWA's are still
broken for now since they are supposed to launch as a separate
'application' they way it works in the non-snap version of chromium.
--
You received this bug
I added a workaround to the askubuntu post.
https://askubuntu.com/a/1266706/612
--
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/1732482
Title:
[snap] doesn't properly save des
As per the views on https://askubuntu.com/questions/1233058/chromium-
snap-on-ubuntu-20-04-some-webapp-shortcuts-not-working-
workaround/1233059#1233059, this bug affects many more people than
indicated here.
--
You received this bug notification because you are a member of Desktop
Packages, whic
Not working for me with Chromium 81, snap version, on Ubuntu 20.04.
(Testing with music.youtube.com and twitter.com)
Icon is created on the desktop, but:
* Not executable (need to mark it)
* Just opens empty browser page (app does not run); work around from
@coeur-noir above, to replace the vers
Confirmed on 81
--
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/1732482
Title:
[snap] doesn't properly save desktop files for "create shortcuts"
action
Status in chromium-b
If the snap chromium is connected to removable-media, the shortcut is
correctly placed in ~/Desktop.
But this shortcut does not work, opens chromium on a blank page.
Tested today on UBudgie 19.10 and chromium-snap 80.0.3987.162 (Build
officiel) snap (64 bits).
--
You received this bug notificat
Replacing in Exec=
/snap/chromium/1071/usr/lib/chromium-browser/chrome
by
/snap/bin/chromium
allows .desktop to launch chromium on the expected page, but icon is
still not set accordingly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Attachment added: ".desktop file created on desktop, expected to open
twitter"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1732482/+attachment/5346653/+files/chrome-jgeocpdicgmkeemopbanhokmhcgcflmi-Default.desktop
--
You received this bug notification because you are a
I opened a bug 1863897 that is now closed as a duplicate of this one
which concerned the A2HS (add to home screen) functionality of PWAs
(progressive web apps). If you use the A2HS functionality it should
create a desktop icon and open the PWA in a Chromium standalone window
that looks similar to a
There's another problem I'm not sure if is related: even if the icon is
well handled, the opened window will not show as an individual one on
taskbar - it will still recognized as a window of Chromium itself with a
Chromium icon. On the deb version of Chromium is works correctly.
--
You received
Actually, the shortcuts were leftovers from the correctly working
Chromium on Ubuntu 19.04. After I removed the shortcuts, I can't
recreate them using the standard procedure anymore.
So yeah, this is the bug.
** Tags added: app chrome
--
You received this bug notification because you are a memb
Is this the issue because of which chromium apps' shortcuts launch
chromium and show its icon as indicator instead of the pinned app's
icon?
If so, this issue still is not fixed in Ubuntu 19.10.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscrib
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Triaged
--
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/1732482
Title:
[snap] doesn't properly save deskto
Another problem that was mentioned in duplicate bug #1848126 is that the
icons are created in
~/snap/chromium/current/.config/chromium/Default/Extensions/*/*/icons
(along with a manifest file), but they are not correctly linked in
~/.local/share/icons/hicolor/, so they cannot be seen by the desktop
It looks like the problem has evolved since it was originally reported.
Desktop files are now correctly created on $HOME/Desktop/, but there are (at
least) two problems with their contents:
- the Exec stanza runs /snap/chromium/861/usr/lib/chromium-
browser/chrome directly, i.e. unconfined
-
Right now ~/snap/chromium/current is a symlink to a specific version of
Chromium. So placing icons and desktop files there will break each time
Chromium is upgraded unless the files are copied from the previous
version-specific directory to the new one.
--
You received this bug notification becau
I did get a ".desktop" file to work by manually copying it from
~/Desktop to ~/.local/share/applications, on Ubuntu 18.04.
I experimented with making the Exec= paths that didn't include a hard-
coded version. I tried "/snap/bin/chromium", "chrome", "chromium" and
"/snap/chromium/821/usr/lib/chromi
I want to highlight that @jonny-boy's comment could be considered a
separate-but-related bug. The exec path being written out in these files
is not optimal. Here's one that was just used for me:
/snap/chromium/821/usr/lib/chromium-browser/chrome
Surely it would be better to refer to the "cur
There's a discussion on the snapcraft forum at
https://forum.snapcraft.io/t/how-to-expose-desktop-files-created-by-
snaps-to-the-de/2853, but no recent input on it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubunt
Any news on this? I am using chromium 66.0.3359.139 (283 stable snap) under
Fedora.
The create shortcuts action created a .desktop file under ~/Desktop, which is
not useful when using the Gnome shell.
The Exec part in the .desktop file points to
/snap/chromium/283/usr/lib/chromium-browser/chro
Appending $HOME/snap/chromium/current/.local/share to $XDG_DATA_DIRS
allows gnome shell (and likely other DEs) to see the desktop files and
to launch them using the chromium snap. Need to discuss how this can be
approached with the snapd team.
--
You received this bug notification because you are
Desktop files in $HOME/snap/chromium/current/.local/share/applications/ are not
very useful on a classic desktop, as gnome-shell (or others DEs) won't find
them there.
We could probably modify the xdg-desktop-menu script to write to a different
location. But $HOME/.local/share/applications/ won'
And now the shortcut for https://example.org started working,
mysteriously.
--
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/1732482
Title:
[snap] doesn't properly save desktop
If I add usr/bin/xdg-desktop-menu and usr/bin/xdg-icon-resource to the
snap, the errors go away, and indeed a desktop file is created in
$HOME/snap/chromium/current/.local/share/applications/.
These desktop files are not marked executables, so double-clicking on them in
nautilus won't work. After
With logging enabled, when trying to create a shortcut I'm seeing this:
LaunchProcess: failed to execvp:
xdg-desktop-menu
LaunchProcess: failed to execvp:
xdg-desktop-menu
LaunchProcess: failed to execvp:
xdg-icon-resource
[21693:21829:1115/175326.882133:WARNING:shell_integration_linux.cc(319)] Co
43 matches
Mail list logo
