At this point, since this bug is so old, it's pretty much on the
developers of the individual electron apps to get their electron
versions up-to-date. The electron version that fixes the problem is
ancient now. This is no longer Ubuntu or anybody else's fault, so I
think necro-bumping this bug
I'm on 22.04 jammy (clean install) and code42 (Crashplan SMB 8.8.4, just
installed) is crashing on start with
"6272:0508/105039.170247:FATAL:gpu_data_manager_impl_private.cc(445)]
GPU process isn't usable. Goodbye.".
--
You received this bug notification because you are a member of Ubuntu
Bugs,
"Expect? Oh yes, expect.." - Marvin, in The Hitch-hiker's Guide to the
Galaxy, fit the 7th.
Two Electron-based programs I use that don't work with Jammy are
BalenaEtcher (only works if run as root) and Code42 (the desktop
application for Crashplan for Small Businesses online backup, which
At this point I expect jammy glibc to use the clone3 syscall. The only
application I've had complaints about is rstudio and they have a plan
(which is roughly speaking "start using Election").
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
If it wasn't taken care of in Jammy, a new bug report would've been
filed. Let's stop necro-bumping closed bugs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications
Is this taken care of on 22.04 (jammy)? Some electron projects may not
have a new enough electron version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all
FYI RStudio is currently affected again, Ubuntu Jammy dev.
https://github.com/rstudio/rstudio/issues/9854
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all
Doesn't Electron need regular security updates for its browser engine?
If true, these projects really need to figure out how to rebuild
regularly against current Electron versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Noah,
I'm not completely opposed to that but I would rather not. Which
projects are affected? Can we put some pressure on them to rebuild?
It'll be well over 6 months from this becoming an issue to the release
of 22.04 and all that's required is a rebuild with the latest point
release of whatever
@mwhudson
A number of open source projects I use haven't had the capacity to patch
their releases with the fix for Electron :( Would you be willing to add
your patched version of glibc that disables clone3 back to your
repository?
--
You received this bug notification because you are a member
I think you have things a bit backwards there. You are using a Docker
image that has clone3 enabled in its libc and the container runtime in
the environment the github action is running in is the thing that is not
supporting the clone3 syscall. Whether the glibc in Ubuntu 21.10 issues
the clone3
Note disabling clone3 syscall in glibc breaks all containers (using
docker) running on Ubuntu that are linked against glibc that does
support the syscall.
One example is opensuse/tumbleweed and one can see the failure e.g. at GitHub
Actions:
This bug was fixed in the package glibc - 2.34-0ubuntu3
---
glibc (2.34-0ubuntu3) impish; urgency=medium
* d/patches/git-updates.diff: Update from release/2.34/master branch.
- d/patches/ubuntu/Fix-close_range-closefrom-tests.patch,
Great!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash upon launch
To manage notifications about this bug go to:
@mikethebos1 You'll see that the fix is in the proposed pocket[1],
awaiting migration. However, since glibc pretty much touches
*everything* it has a lot of hoops to jump through with autopkgtests
before it can migrate to the release pocket[2]. Rest assured, it's work-
in-progress at this point
@mwhudson Since many applications have not updated to the patched
electron and qt distributions, should this glibc patch be integrated
into impish?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I confirm that all electron apps (build with electron version < 14) does
not open devTools. So, for some applications this is critical (for
example it is one of main function of react-native-debugger).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm @mwhudson's glibc build from
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt fixed the issue
for me with VSCode.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
I can confirm @mwhudson's glibc build from
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt fixed the issue
for me as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
I am seeing the same issue with the newest Discord .deb.
Running with the --no-sandbox is working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash upon
MS Teams (.deb) worked for me with the glibc patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash upon launch
To manage notifications about this bug
@mwhudson Without your glibc the Electron apps I tested, 1Password and
MS Teams, open up a blank screen. When I install your glibc than works
as expected. About the Widevine I will look for another bug report or
create one. With or without your glibc the Widevine crashes. The only
way to avoid it
glibc patch didn't help with vscode and ms teams. both only work with
--no-sandbox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash upon launch
To
I installed your glibc packages and 1Password start to work again.
However I had problems with Widevine in Firefox (.deb package).It was
crashing when I used GMP sandboxing. If I disabled temporarily the
sandbox Netflix and other services worked again. Someone could test to
see if it's a general
@mwhudson I can also confirm using your ppa version. Plus, apps bundled
with Qt begin to work again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash
@mwhudson can confirm using your ppa version, Slack and other electron
apps started working again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash upon
** Changed in: glibc (Ubuntu Impish)
Milestone: None => ubuntu-21.10
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash upon launch
To manage
Brackets installed by using the following commands
```
cd ~/Downloads
wget
https://github.com/adobe/brackets/releases/download/release-1.14.1/Brackets.Release.1.14.1.64-bit.deb
dpkg-deb -R ./Brackets.Release.1.14.1.64-bit.deb Brackets
sed -i 's/libcurl3/libcurl3 | libcurl4/'
If I had to install from the PPA, would I have a clean upgrade path if
the patch gets adopted in the main archives?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron
I've made a patched glibc package with clone3 disabled at
https://launchpad.net/~mwhudson/+archive/ubuntu/devirt/+packages?field.name_filter=glibc,
would be interesting to hear if it helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Related:
https://github.com/rstudio/rstudio/issues/9854
** Bug watch added: github.com/rstudio/rstudio/issues #9854
https://github.com/rstudio/rstudio/issues/9854
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Would reverting re-break QtWebEngine based apps fixed in LP: #1939993 ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash upon launch
To manage
@Michael, it's pretty clear than some electron based applications aren't
going to be updated before impish is out, reverting is what makes the
most sense probably there
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ah, glad to hear the fix is making it's way back. I still wonder if
disabling clone3 for impish release is the pragmatic thing to do, I
don't know if vscode, slack, skype etc etc are going to get an update in
the next 4 weeks.
--
You received this bug notification because you are a member of
** Tags removed: rls-ii-incoming
** Also affects: glibc (Ubuntu Impish)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron
** Tags added: fr-1740
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash upon launch
To manage notifications about this bug go to:
FYI, the fix is now being backported to Electron 13 and also Electron 12
https://github.com/electron/electron/pull/31091
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron
Dylan, looks like Electron 14+ has the fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash upon launch
To manage notifications about this bug go to:
On 23/09/2021 05:12, Michael Hudson-Doyle wrote:
> 1) it's a real problem
> 2) it's related to the new clone3 syscall
>
> Do electron apps use seccomp by default? It seems code has some way to
> turn this off automagically but if I run code --enable-sandbox it
> reliably crashes. Haven't been
It also looks a bit as if crashing on an unknown syscall is unintended. So
there might be more than one bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all
That's a good question and I don't know off the top of my head. I'll try to
find out tomorrow unless someone can weigh in with some clues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
@mwhudson WHixh stable versions of electron incorporate that commit? It
would be useful to tell that to application maitnainers so they could
update their electron dependency.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Oh looks like these electron apps were built with a chromium that lacks
this commit
https://chromium.googlesource.com/chromium/src/+/218438259dd795456f0a48f67cbe5b4e520db88b
- which was only 4 months ago. And Chromium's sandbox defaults to crashing
on unknown syscalls. So I guess we're back to the
So I am having a bit of a hard time debugging this. My conclusions so
far:
1) it's a real problem
2) it's related to the new clone3 syscall
Do electron apps use seccomp by default? It seems code has some way to
turn this off automagically but if I run code --enable-sandbox it
reliably crashes.
It also affects slack desktop and insync.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
Electron applications all crash upon launch
To manage notifications about this bug go to:
As far as my testing went, this affects VS COde, Azure Data Studio, MS
Teams and Skype. Using --no-sandbox or even --disable-gpu-sandbox allows
all these to launch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1944468
Title:
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1944468
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
It's due to the new glibc, confirmed using vscode
download and install using
https://code.visualstudio.com/sha/download?build=stable=linux-deb-x64
$ code
on an hirsute machine it works correctly, add an impish source and
upgrade libc6 and it fails to start with the error reported
** Package
I suspect these may be related:
https://github.com/electron/electron/pull/30893 "fix: crash when
launching app with systemd v249"
https://github.com/microsoft/vscode/issues/132609 "Electron 14+
required? Potential systemd 249 / nVidia issue"
Electron patch backported from Chromium:
50 matches
Mail list logo
