afrog
afrog copied to clipboard
Can't open DevTools
Prerequisites
- [X] Put an X between the brackets on this line if you have done all of the following:
- Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
- Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
- Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
- Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
- Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages
Description
Can't open DevTools. I tries it did with Ctrl-Shift-I
, menu and with Ctrl-Shift-P
-> Windows: Toggle DevTools.
Steps to Reproduce
- Start Atom
-
Ctrl-Shift-I
Expected behavior:
DevTools pane is opened.
Actual behavior:
Nothing. No any mesages. New panes. Or errors. Just nothing.
Reproduces how often:
Always.
Versions
$ atom --version
Atom : 1.58.0
Electron: 9.4.4
Chrome : 83.0.4103.122
Node : 12.14.1
$ apm --version
apm 2.6.2
npm 6.14.13
node 12.14.1 x64
atom 1.58.0
python 3.10.1
git 2.34.1
$ cat /etc/fedora-release
Fedora release 35 (Thirty Five)
DevTools is opened when atom started as atom --no-sandbox
.
Same issue here, fedora 35 apm 2.6.2 npm 6.14.13 node 12.14.1 x64 atom 1.58.0 python 3.10.2 git 2.34.1
Are you still experiencing this issue?
Yes.
Me too still
I'm also experiencing this issue.
- Lenovo Thinkpad W530
- With hybrid graphics (intel + nvidia), drivers i915 & nouveau
- Fedora 35
- Wayland with sway
$ atom --version
Atom : 1.59.0
Electron: 9.4.4
Chrome : 83.0.4103.122
Node : 12.14.1
Trying to open Developer Tools causes core dump on the background while the editor stays open and keeps on working. Core is catched by systemd-coredump
.
Output of coredumpctl
PID: 60885 (atom)
UID: 1000 (askolsam)
GID: 1000 (askolsam)
Signal: 31 (SYS)
Timestamp: Mon 2022-02-21 13:55:24 EET (6min ago)
Command Line: $'/usr/share/atom/atom --type=renderer --enable-experimental-web-platform-features --field-trial-handle=16494123246955764627,13814427047022146522,131072 --enable-features=WebComponentsV0Enabled --disable-features=SpareRendererForSitePerProcess --lang=en-US --enable-crash-reporter=a42519b8-af3f-4b7b-9701-3c0a00170347,no_channel --global-crash-keys=a42519b8-af3f-4b7b-9701-3c0a00170347,no_channel,_companyName=GitHub,_productName=Atom,_version=1.59.0 --app-path=/usr/share/atom/resources/app.asar --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=9 --no-v8-untrusted-code-mitigations --shared-files=v8_snapshot_data:100'
Executable: /usr/share/atom/atom
Control Group: /user.slice/user-1000.slice/[email protected]/app.slice/app-org.gnome.Terminal.slice/vte-spawn-750c0916-0700-4047-824d-1276a7c3e245.scope
Unit: [email protected]
User Unit: vte-spawn-750c0916-0700-4047-824d-1276a7c3e245.scope
Slice: user-1000.slice
Owner UID: 1000 (askolsam)
Boot ID: <REDACTED>
Machine ID: <REDACTED>
Hostname: <REDACTED>
Storage: /var/lib/systemd/coredump/core.atom.1000.<REDACTED>.60885.1645444524000000.zst (present)
Disk Size: 1.7M
Message: Process 60885 (atom) of user 1000 dumped core.
Found module linux-vdso.so.1 with build-id: 1d2074168a56bb8ab87f2b2cb0fb1c9fa29ec1ee
Found module libbrotlicommon.so.1 with build-id: 9e92a8ec2d9efe80ec86e04fba0549cd3202ebc4
Found module libicudata.so.69 with build-id: fae0a612a5535b81eaec823e8cedb06c89719d94
Found module libgpg-error.so.0 with build-id: 081975d0a3416374b4883b2f1639fd3c9df42390
Found module libgmp.so.10 with build-id: 14dbc5e93375ccb760dc47c5aaecc0cdfc45a06a
Found module libhogweed.so.6 with build-id: 288da1bb6ffaf6600c2f8a126bec247f2e9a4628
Found module libnettle.so.8 with build-id: 62dba2572638edf8336bd4de5017fc70eaf0a567
Found module libtasn1.so.6 with build-id: be32a4fab2585b6114471e83bf582b3df020b594
Found module libunistring.so.2 with build-id: edcae9db236efd11e61995054ddf27a89ec6dc40
Found module libidn2.so.0 with build-id: f3ad1b0687f5b426beed2d3d3d18aa301932f7a3
Found module libp11-kit.so.0 with build-id: a7a93824ebf14980eeb37fe23c9d86dd201f947f
Found module libresolv.so.2 with build-id: 0fbe5191a8f9212dd09bf0f85b08fcec995d543a
Found module libcrypto.so.1.1 with build-id: 3ead607210606611d5f3398ee7e65198bd519de9
Found module libkeyutils.so.1 with build-id: 2560a16099ad1875f7ea2195ae25b97ea168a758
Found module libkrb5support.so.0 with build-id: 03649849c4d1813c307624a711b03fb15e7124cb
Found module libcom_err.so.2 with build-id: a1d791cd7600f5609702a895a64d9131d1cd7b8f
Found module libk5crypto.so.3 with build-id: 11238d51059ecf299699dc4d24a74e67a64aa725
Found module libkrb5.so.3 with build-id: 0582e999cc7d74e1ec2dc7b3c9f7aa4dae7342f6
Found module libbrotlidec.so.1 with build-id: 57cb8a53e33f31a620f3739919414c0d00549f87
Found module libbz2.so.1 with build-id: 19ce300b78962ee0b113afb0f1016727a2f3c37b
Found module libdatrie.so.1 with build-id: 9ebd99e63729783155e081cc2c2377a767b9e3c4
Found module libjson-glib-1.0.so.0 with build-id: ff150bb944b7d341fb33c367b230a0c005ac1833
Found module libsqlite3.so.0 with build-id: 072b1e135c03359061ea9c8346cdb61528950924
Found module libicui18n.so.69 with build-id: 96cea623123108e425250a0c59fa6221e96cadb2
Found module libicuuc.so.69 with build-id: 45119735453983eea1a3fb59b0ed34a6e61d8c5a
Found module libstemmer.so.0 with build-id: c36e99b36673aac08c24a26a9c71ce82938c62f7
Found module libxml2.so.2 with build-id: 8f21e0bbe0106c5c5cd35859487dcc074b8f13bd
Found module libgraphite2.so.3 with build-id: 58f949a538f65a6221e442879144b368f663f7e3
Found module libgcrypt.so.20 with build-id: 711d41580c5a8649a79a8430a985dac3e25b5ba2
Found module libcap.so.2 with build-id: 0214aa9cc6a8646eb9ec27ab7dda6a2219da6500
Found module liblz4.so.1 with build-id: fd02c4542a1ce1ad6c503b958447be1c37a4afee
Found module libzstd.so.1 with build-id: 7984add4b0ab24869c30e19cfba3637ca295dd7b
Found module liblzma.so.5 with build-id: 7fec53ce7cba9489f130c99cfd3ace82e9dde0ee
Found module libpcre2-8.so.0 with build-id: 67d78ee981939e51fee33d8885ff8000552e7a3d
Found module libblkid.so.1 with build-id: 0d23bd02d1ed06df97832d78f7ff38d617ac29d9
Found module libgnutls.so.30 with build-id: 725a333b137bd282d588279e04f20d99a3ea24c1
Found module libavahi-client.so.3 with build-id: a74102919e50a8c29f9f6b7cb561d387a82761fa
Found module libavahi-common.so.3 with build-id: 07bf073b57a037f9bb8e64e12d460499ead55a7c
Found module libgssapi_krb5.so.2 with build-id: c79d44cc56f67983ba388e5336c779d9f050114e
Found module libstdc++.so.6 with build-id: 455be2588680c3ff57e3a7defe212a13e2efdbd1
Found module libwayland-server.so.0 with build-id: 2c1f4aa811bc973c2b48d3dee4f14ef5f57196ec
Found module libxcb-render.so.0 with build-id: 36edcc5980076552c68ccef2c6199808cba68f98
Found module libxcb-shm.so.0 with build-id: a31877f8ca8058df0005532a160d93a1104c5401
Found module libfreetype.so.6 with build-id: 9999d5d839e4c66f038202b9c706f5ac7c17c593
Found module libpixman-1.so.0 with build-id: dc521afa5e1d55834eebac7bb3c97cfe5e73f384
Found module libthai.so.0 with build-id: 1f7b46f526e1fba04f29535981483f50c782775e
Found module libXinerama.so.1 with build-id: 72d169302fe5696536345d6da1605baeb6e3bc01
Found module libwayland-egl.so.1 with build-id: ff42fe0eeca6a4c95efc7c2b024e98dadf763267
Found module libwayland-cursor.so.0 with build-id: 3df8fa12f532612fc50f17938906c434e86106ad
Found module libxkbcommon.so.0 with build-id: 534d0218e01a780844e80ce6544afc33731e716a
Found module libwayland-client.so.0 with build-id: ecba40c75b2d78de955fa69baada38ed183fd4f9
Found module libtracker-sparql-3.0.so.0 with build-id: 0f5c589b707376d06aefe8ab2bfe8c05f32198d9
Found module libcloudproviders.so.0 with build-id: 5b10ee7ce7470f15b8429030cf810e671a185de5
Found module libepoxy.so.0 with build-id: f368f1c90cf2ea823acc67473f816e72f368bc43
Found module libcairo-gobject.so.2 with build-id: 7a1381e606b2601e779ccd25afbc719c5bc4e922
Found module libfribidi.so.0 with build-id: a4e245984a5c2e6d842a71adea32ec7c05cb7e40
Found module libfontconfig.so.1 with build-id: e50d477be88a082f6a2fd42a7db8278bb88466ca
Found module libpangoft2-1.0.so.0 with build-id: 8a2787ba1addef0da844b000c3537c8fc33785b8
Found module libharfbuzz.so.0 with build-id: 781c6377efbcd3ca2e7d238dc8c0e7401708d142
Found module libjpeg.so.62 with build-id: f50d5361714c8fe58ed898123a98aa0d6547068e
Found module libpng16.so.16 with build-id: afcd45d29b0d579615db44a29213544328adde6f
Found module libsystemd.so.0 with build-id: b61753e8440ecf39624b3e37f855941c18a69e9b
Found module libplds4.so with build-id: 0eda07de4f4a79f8a477841b1288edc47db3539d
Found module libplc4.so with build-id: b4395d28ec432fbfd596d6acce1b0a693074d739
Found module libXau.so.6 with build-id: b6a2d4859848c28bf0a4fc8744d04b1935879af6
Found module libselinux.so.1 with build-id: f805394f993c704b949315b56c344d22dfad801f
Found module libmount.so.1 with build-id: dac49fdb6963d60e2706cfacd2f2f5c0773ab008
Found module libz.so.1 with build-id: 5903f5c355c264403e4e7cdc66779584425ca3b8
Found module libgmodule-2.0.so.0 with build-id: daced268f49ec62d46980a053582bcc234526fc0
Found module libpcre.so.1 with build-id: fcbdb4731e50f20a47b62341a6841dd616fe495d
Found module libffi.so.6 with build-id: 0129f72b58e11d59546f7f207d2c90af7ebd9a5e
Found module ld-linux-x86-64.so.2 with build-id: 4e2c368b1240116994daff7f0f248a01f6e53198
Found module libc.so.6 with build-id: 881b4882a363c5c193cddf6e4991e1873f593364
Found module libgcc_s.so.1 with build-id: 0028b8616fa79ea1496e4812c3fc9c7bf9607a56
Found module libcups.so.2 with build-id: 8c38ae74a8dfb739863d8902d393c2d0488eeda6
Found module libatspi.so.0 with build-id: 93de58828b176bf6eb76897e1cb2e576a1d5fddf
Found module libasound.so.2 with build-id: 3d77cd90a5798c94b6258410a0c6ed24e65424ed
Found module libXss.so.1 with build-id: 150eb279e255be749790b098173060a2f0c1234c
Found module libgbm.so.1 with build-id: f4eba61e15e804e2efef46a1878eb2e1f5796494
Found module libdrm.so.2 with build-id: fc68e955c370337e29016e39ba13d13bd90f9b25
Found module libexpat.so.1 with build-id: 5e15db4b53c11a5e7602daa374b20a662570258a
Found module libXrandr.so.2 with build-id: eb8b304d315d3ee09980cafe7ceda9582daa40e8
Found module libm.so.6 with build-id: 47343f97c29c4e91c841e2bfd344329a264075ad
Found module libcairo.so.2 with build-id: 8a28f43397104b4ef517df6c119772b5d577f48e
Found module libpango-1.0.so.0 with build-id: 6d1029ef5e765e1fceb8ff057a1880f883037f71
Found module libpangocairo-1.0.so.0 with build-id: d410f48f069e60633f232cccc8423ad326ebbf22
Found module libgdk-3.so.0 with build-id: bf4963d3c7111f67ea984ed6d069dc0d79bf2ecf
Found module libgtk-3.so.0 with build-id: 8e15118e9bb3114b002a98ed06450c75667e689f
Found module libgdk_pixbuf-2.0.so.0 with build-id: b6e5e7c59ce90aecabf6b0b005ecd138dd6bae45
Found module libdbus-1.so.3 with build-id: 58e800f0865bde326c5c9ce510062d5b19902f67
Found module libatk-bridge-2.0.so.0 with build-id: 8df66b2fcb2033cdad8e26a3ad13ad7f3cdf4144
Found module libatk-1.0.so.0 with build-id: b3d190657efe01bedd3077177d2bd473b7b737df
Found module libnspr4.so with build-id: 0056e405d4917627cd6c826f6460b308392d00cd
Found module libsmime3.so with build-id: 18186bb66fc007573cea4c1e3e07b9ef541db444
Found module libnssutil3.so with build-id: 8f8163feb75c8babd1e8bbd4d136d572b4ee7bc3
Found module libnss3.so with build-id: 192d4bb2e5e0e695bf633846692efe6757cbc48b
Found module libXtst.so.6 with build-id: 97ddda29c72fa18b2cae1274026730a04f8b0ae2
Found module libXrender.so.1 with build-id: 45e135fd2ee2393b7eb0c94f964542b8326582e1
Found module libXi.so.6 with build-id: e1d4fcbcab03948da50a0e175ac2459c335e7939
Found module libXfixes.so.3 with build-id: e8020da14577d275b75ed0c4cb18b1050fc33595
Found module libXext.so.6 with build-id: 08e82aa07cb7910a08d8386fb16de7896ce290f4
Found module libXdamage.so.1 with build-id: 7ad2a44d600f984d1728b624701f5d41bba04067
Found module libXcursor.so.1 with build-id: fb3d6eb4c582d4761eab821bc0ceb77fc7c2654f
Found module libXcomposite.so.1 with build-id: 4223e166fff31d2e529cc5f856c7100fbdf67cd9
Found module libxcb-dri3.so.0 with build-id: 0f4fd31b851a10e0ac9726faf3b2b66a52a56162
Found module libxcb.so.1 with build-id: 1352e33391b3079347f320218799d6e531bd42f1
Found module libX11-xcb.so.1 with build-id: 50b389a40194174f2c224e530719862e4986b02e
Found module libX11.so.6 with build-id: b63e8f330442522b1d5872d1b2ccf32702767d80
Found module libgio-2.0.so.0 with build-id: 885a350082fb5150c77466144c54897321e3a93d
Found module libglib-2.0.so.0 with build-id: bd0f95869104fa48a76bc69569db926805203da4
Found module libgobject-2.0.so.0 with build-id: 9442204a99e355e956cc3f8a1862527294972b36
Found module librt.so.1 with build-id: 7942627f54693fdeb840897c0b959b7fd909f5b3
Found module libpthread.so.0 with build-id: ef966cfe5a73990033e35779603c0d78401013e6
Found module libdl.so.2 with build-id: 01afa92b2c758f2702ff6bdc0f6cadeac64456f7
Found module libffmpeg.so with build-id: ed11ec403fe639e0d12f9263a7aaa93f8bbf6a6c
Found module atom with build-id: 7836c459ba61a264a29878f37b81cd4047746e3a
Stack trace of thread 1:
#0 0x00007f911c7ca63d __clone3 (libc.so.6 + 0x11263d)
Additional information
- atom is started with env variable
DRI_PRIME=1
(= use intel GPU).- Trying to use Nvidia GPU (
DRI_PRIME=0
) causes a different core dump straight on startup and Electron apps in general tend to have issues whenDRI_PRIME=0
.
- Trying to use Nvidia GPU (
- Starting atom with
--no-sandbox
enables 'Developer Tools' to open without issues
bump -same issue @system76 oryp5 w/ pop_Os! 22.01 (installed from deb repo not flatpak)
DevTools is opened when atom started as
atom --no-sandbox
.
somehow this solved it
-ran it once in terminal -and now it just works as expected (without having to run it from terminal anymore)
thanks!
Workaround:
atom --no-sandbox
Be advised: using --no-sandbox disables the electron sandbox, and could leave you vulnerable to attacks when installing outdated/unverified packages.
https://github.com/electron/electron/issues/15760
Read more above to find info about the electron sandbox.
https://github.com/atom/atom/issues/23036#issuecomment-1139239233
This is a duplicate of #23036 and the issue should be closed. Please follow the link above for more information on this issue.
I am having this same issue. The workaround of opening with the --no-sandbox option works. However, unlike osscar's experience, doing this once did not resolve the problem. I can only open DevTools if I have opened atom with no sandbox.
Interesting coincidence that both me and one other person with the problem are both using System76 Oryx Pro machines, although I didn't have a crash, and have no coredump, and can't find any other logs with any errors or alerts that reference atom or DRI_PRIME.
Environment:
- System76 orpy6
- PopOS
- Pop!_OS 22.04 LTS
- 64-bit
- GNOME v. 42.2
- Windowing System is X11
- Atom installed via Pop!Shop - flatpak first, then I uninstalled and re-installed via deb. I had the same issue either way, though don't know if exact errors are the same, because I didn't get into DevTools to check that until after I uninstalled via flatpak and re-installed via deb.
Steps I took:
- Checked Keybinding Resolver - it showed DevTools in green, which I believe means it thinks the command executed?
- Tried from menu, too, but that didn't work either.
- Followed all suggestions in Debugging doc:
- Checked version - already at latest stable release (1.60.0)
- Opened in safe mode
- Disabled non-core packages ( I only had two - both for awk support)
- Cleared saved state
- Did the "reset to factory" renaming of my .atom dir
- Uninstalled atom flatpack package and chose the deb package for reinstall (both via Pop!Shop).
- Tried the
--no-sandbox
option - it works! - Per osscar's comment, tried closing and relaunching normally, but that did not work (I tried it several times).
Once I was able to open DevTools, I found these 5 warnings repeated every time I toggled DevTools off and back on again. I looked at the referenced paths on my computer.
There is an asar archive called app.asar, and there is also a directory called app.asar-unpacked. The unpacked dir does not have the files referred to in the the errors. I don't have the utils installed to see into the asar archive, but I would think it would reflect the same structure as the unpacked dir?
electron/js2c/renderer_init.js:15 (electron) crashReporter.start is deprecated in the renderer process. Call it from the main process instead.
log @ electron/js2c/renderer_init.js:15
DevTools failed to load SourceMap: Could not load content for file:///usr/share/atom/resources/app.asar/node_modules/focus-trap/dist/focus-trap.js.map:
DevTools failed to load SourceMap: Could not load content for file:///usr/share/atom/resources/app.asar/node_modules/focus-trap/node_modules/tabbable/dist/index.js.map:
DevTools failed to load SourceMap: Could not load content for file:///usr/share/atom/resources/app.asar/node_modules/dugite/build/lib/git-process.js.map:
DevTools failed to load SourceMap: Could not load content for file:///usr/share/atom/resources/app.asar/node_modules/dugite/build/lib/git-environment.js.map:
I've attached an xml doc (saved as txt) showing the file structure of everything under /usr/share/atom/resources, in case that's helpful
I am having this same issue. The workaround of opening with the --no-sandbox option works. However, unlike osscar's experience, doing this once did not resolve the problem. I can only open DevTools if I have opened atom with no sandbox.
Interesting coincidence that both me and one other person with the problem are both using System76 Oryx Pro machines, although I didn't have a crash, and have no coredump, and can't find any other logs with any errors or alerts that reference atom or DRI_PRIME.
Environment:
* System76 orpy6 * PopOS * Pop!_OS 22.04 LTS * 64-bit * GNOME v. 42.2 * Windowing System is X11 * Atom installed via Pop!Shop - flatpak first, then I uninstalled and re-installed via deb. I had the same issue either way, though don't know if exact errors are the same, because I didn't get into DevTools to check that until after I uninstalled via flatpak and re-installed via deb.
Steps I took:
* Checked Keybinding Resolver - it showed DevTools in green, which I believe means it thinks the command executed? * Tried from menu, too, but that didn't work either. * Followed all suggestions in Debugging doc: * Checked version - already at latest stable release (1.60.0) * Opened in safe mode * Disabled non-core packages ( I only had two - both for awk support) * Cleared saved state * Did the "reset to factory" renaming of my .atom dir * Uninstalled atom flatpack package and chose the deb package for reinstall (both via Pop!Shop). * Tried the `--no-sandbox` option - **it works!** * Per osscar's comment, tried closing and relaunching normally, but that did not work (I tried it several times).
Once I was able to open DevTools, I found these 5 warnings repeated every time I toggled DevTools off and back on again. I looked at the referenced paths on my computer.
There is an asar archive called app.asar, and there is also a directory called app.asar-unpacked. The unpacked dir does not have the files referred to in the the errors. I don't have the utils installed to see into the asar archive, but I would think it would reflect the same structure as the unpacked dir?
electron/js2c/renderer_init.js:15 (electron) crashReporter.start is deprecated in the renderer process. Call it from the main process instead. log @ electron/js2c/renderer_init.js:15 DevTools failed to load SourceMap: Could not load content for file:///usr/share/atom/resources/app.asar/node_modules/focus-trap/dist/focus-trap.js.map: DevTools failed to load SourceMap: Could not load content for file:///usr/share/atom/resources/app.asar/node_modules/focus-trap/node_modules/tabbable/dist/index.js.map: DevTools failed to load SourceMap: Could not load content for file:///usr/share/atom/resources/app.asar/node_modules/dugite/build/lib/git-process.js.map: DevTools failed to load SourceMap: Could not load content for file:///usr/share/atom/resources/app.asar/node_modules/dugite/build/lib/git-environment.js.map:
I've attached an xml doc (saved as txt) showing the file structure of everything under /usr/share/atom/resources, in case that's helpful
Atom has been sunset by Github. It is abandonedware.