Thanks for sharing your resuilts, David!
--
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/2026200
Title:
Snap update broke launching and printing on 20.04 Ubuntu.
Status in
Thanks Nathan,
I finally lined up all the ducks, and it appears to have worked.
- The dir I'm building in has to be in my home dir
- the xvfb-run seems necessary
- don't attempt to use --headless
- both --user-data-dir=/tmp/ChrUnsnapped and --class="ChrUnsnapped" seem
unnecessary
So,
As far as I know, Xvfb and --headless result in quite different
environments, as the first will run in normal graphical mode and the
latter won't.
I see no reason why this would affect your extension packing, however I
have no experience with extensions in Chromium. Could the graphical
This breaks our command-line pack of an in-house extension, under Ubuntu 20.04.
Is there a way to do this using the confined run?
Our current unconfined run build command-line (please excuse legacy from
years ago, eg --headless might be more appropriate now):
xvfb-run
@Nathan
Thank you for the clarity on the Core20 vs Core22, however, I will still
maintain that had this latest Chromium SNAP been built on Core20, as has
seemingly been until now, we wouldn't be having this dialog.
When Chromium has been built against Core20, I've been able to call
chromium
> (I still maintain that if Ubuntu 20.04 LTS is supported until April
> 2025, and its base SNAP is core20, it is not appropriate (if, only
> because of my biased opinion) to build snaps on core22, which, you
> admit, is the base snap core for Ubuntu 22.04)
I think there is a misunderstanding
-- Nathan
The symlink I'm referring to is the *current* in this path:
/snap/chromium/**current**/usr/lib/chromium-browser/chrome
... which is a symlink to build 2529 or, now I have 2497
(I still maintain that if Ubuntu 20.04 LTS is supported until April
2025, and its base SNAP is core20, it
-- Michaelus
> you're saying invoking chromium via a fully qualified, real-path, with
a SNAP-created symbolic link to a actual build directory, is a
"unsupported setup" ?
Yes, running a snap via /snap/chromium/current/usr/lib/chromium-
browser/chrome is unsupported. (I don't know how you
Thanks Nathan, I came to the same conclusion as the tickets you
provided, as we were trying to run the snap from a shared nfs mount, but
glad/sad to know that snap was the ultimate problem - sigh. I can now
run the snap directly, without glibc issues so hooray.
I'm now dealing with a different
Nathan Teodosio:
>> "That invocation is not supported, so one could argue that it breaks
unsupported setups."
My apologies, but that comes off as a rather convenient way of saying,
"Well, you shouldn't have been doing it that way in the first place, and
be happy it's worked for you this long."
I also appreciate your situation and I'm sorry this has been giving you
a hard time. I'm happy to help with what I can.
> 1. Is there any way we can influence where chromium looks for glibc to
> find the base 2.35? (Is this something that would be resolved if I
> could get /snap/bin/chromium
Am 07/07/2023 um 17:59 schrieb Michaelus:
> ... by the Apache user, and, because APT forces the SNAP Chromium
> package, rather than the standard Debian package, and because the Apache
> user's (www-data) home directory is /var/www and not /home/www-data, one
> cannot invoke Chromium via
Nathan, thanks for the detailed followup. I'm unfortunately not in a
good working state, as I introduced a typo in an environment variable
used to run our functional test harness when I converted to invoking
/snap/bin/chromium with `runuser` instead of a direct invocation form
our vagrant user.
I've been using headless chromium on the cli with the --print-to-pdf
parameter to generate PDF documents on Ubuntu 20.04 for well over a
year.
Chromium has been invoked at:
/snap/chromium/current/usr/lib/chromium-browser/chrome
... by the Apache user, and, because APT forces the SNAP Chromium
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Invalid
--
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/2026200
Title:
Snap update broke launching and
Previously, I'm used /snap/chromium/current/usr/lib/chromium-
browser/chrome to start Chrome in kiosk mode in order to access file://
on local system.
Now all work as expected using latest version (2529) when I execute
using : /snap/bin/chromium
--
You received this bug notification because you
Marcus, from what I gather, and correct me if I'm wrong, you were able
to fix all your problems in your headless environment with Chromium
edge. Not with Chromium stable?
And hats off to you for responding to the proposed questions and
investigating the issue. That was a great help and much
To be clear, the reason why this has hit you is that Chromium in the
stable channel switched from Core20 in 114.0.5735.106 to Core22 in
114.0.5735.198 (this is a downstream, in other words Ubuntu
maintainer's, decision, not Chromium's maintainers').
Core20 is a base from Ubuntu 20.04, while
Dalik, there is an upstream bug report about your observation of missing
*.bin files for CUPS on /var/lib/snapd/seccomp/bpf/:
https://github.com/OpenPrinting/cups-snap/issues/16
It is reported by GitHub user d3al. Is that you?
I am not able to reproduce this problem on Ubuntu 23.04 and 23.10.
@Nathan Teodosio:
Just tried running our test harness via runuser and that works with the
edge version of chromium - which is a valid path forward for me,
especially if running directly from the current/user snap path is not
supported.
But I'm still around if you want me to investigate further.
@Nathan Teodosio:
Running either produces the same issue:
```
$ /snap/bin/chromium
cannot open path of the current working directory: Permission denied
$ /snap/bin/chromium --enable-logging=stderr
cannot open path of the current working directory: Permission denied
```
I presume these are
If I execute the following command then I no more have issues :
snap refresh --channel stable/core20 chromium
--
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/2026200
Title:
3. Please specify whether the errors are only observed for headless
Chromium or if it is also observed for normal Chromium.
** Tags added: focal printing
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
Thank you very much for elaborating, that is much clearer. A couple of
questions:
1. When you do not use /snap/chromium/current/usr/lib/chromium-
browser/chrome, but rather chromium or /snap/bin/chromium, do you ever
get those GLIBC errors? If not, what is the exact error you get? You
mention
I need to execute :
snap revert chromium
In order to resolve the issue using Ubuntu 20.04 or 20.10.
-
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/2026200
Title:
Snap update broke
Anyone suffering the described problem, could you follow Nathan's
instructions if you have not done so yet, and could you run the
following commands and paste the output here?
lpstat -r
lpstat -v
lpstat -p
cuos.lpstat -r
cups.lpstat -v
cups.lpstat -p
Aleo try to print
Our CI server was manually updated to the edge version of the snap in an
attempt to resolve the issue, but it produces the same error output.
Edit: Our CI server is on Ubuntu 20.04.6 LTS
```
chromium 116.0.5845.4 2527 latest/edge canonical✓ -
```
Glibc version:
```
~$
Sure thing, I can provide any information you need.
1. Happened with the latest update to Chromium, has been working fine
for over a year. I use it for functional testing in combination with
selenium and facebook webdriver. Have it installed as a snap, so I
presume it was auto updated, but I do
Thanks for the confirmation, but I don't yet know the context of the
issue.
Did you update from Bionic to Focal or did you simply notice the issue
after the last Chromium update?
Is there any problem when running 'chromium' from a terminal or is it a
issue specific to the launcher?
Please try
Same issue for me on Ubuntu 20.04.1 LTS
Same version of chromium snap with the same error output as @Dalik
Output of `snap connections chromium`
```
Interface PlugSlot
Notes
audio-playback
You mention snap update in the title. What specific snap are you
referring to, Chromium, Cups or Snapd? The output of "snap changes"
could be useful. If you roll it back with "snap revert ",
does it work again?
> Launching chrome from menu shortcut that is managed by the snap works
> and it
31 matches
Mail list logo
