waveterm icon indicating copy to clipboard operation
waveterm copied to clipboard
Published 1 month ago • verified publisher icon wavetermdev

[Bug]: Waveterm crash on startup with single-instance-lock error

Open Zinodel opened this issue 1 year ago • 3 comments

Current Behavior

On startup, application crashes with waveterm-app could not get single-instance-lock, shutting down line in logs

Expected Behavior

App successfully started

Steps To Reproduce

  1. Linux fedora 6.11.7-300.fc41.x86_64
  2. Run Waveterm 0.11.0
  3. App crashes

Wave Version

0.11.0

Platform

Linux

OS Version/Distribution

Fedora

Architecture

x64

Anything else?

I used waveterm for a while. But in any moment, i tried to start the application, and it doesn't start.

logs:

2025-01-30 13:41:53.198 WaveObj updated window:8ed13c49-6d6d-4d7f-8a1f-eddac97ecbc5
2025-01-30 13:41:53.200 [service] window.SetWindowPosAndSize | 12ms
2025-01-30 13:41:53.206 [service] object.GetObject window:8ed13c49-6d6d-4d7f-8a1f-eddac97ecbc5 | 10ms
2025-01-30 13:41:53.206 WaveObj resolved window:8ed13c49-6d6d-4d7f-8a1f-eddac97ecbc5 10ms
2025-01-30 13:41:53.254 fe-log Init Bare
2025-01-30 13:41:53.276 ensureHotSpareTab
2025-01-30 13:41:53.277 createBareTabView
2025-01-30 13:41:53.508 tabview init 904ms
2025-01-30 13:41:53.529 before wave ready, init tab, sending wave-init a0a88927-32ab-4179-b404-7d3f522028d6
2025-01-30 13:41:53.531 fe-log Init Wave {"tabId":"a0a88927-32ab-4179-b404-7d3f522028d6","clientId":"2996dcd3-426e-481c-90dc-736214c22d2f","windowId":"8ed13c49-6d6d-4d7f-8a1f-eddac97ecbc5","activate":true}
2025-01-30 13:41:53.541 [wavesrv] 2025/01/30 13:41:53.541255 [websocket] new connection: tabid:a0a88927-32ab-4179-b404-7d3f522028d6 connid:484dfa8a-b589-412a-972c-6fb097ecc909 routeid:tab:a0a88927-32ab-4179-b404-7d3f522028d6
2025-01-30 13:41:53.541 [wavesrv] 2025/01/30 13:41:53.541290 [router] registering wsh route "tab:a0a88927-32ab-4179-b404-7d3f522028d6"
2025-01-30 13:41:53.568 fe-log Error in initWave Cannot read properties of undefined (reading 'layoutstate')
2025-01-30 13:41:53.864 fe-log Init Bare
2025-01-30 13:41:54.035 tabview init 741ms
2025-01-30 13:42:07.374 waveterm-app starting, data_dir=/home/user/.local/share/waveterm, config_dir=/home/user/.config/waveterm electronpath=/opt/Wave/resources/app.asar/dist gopath=/opt/Wave/resources/app.asar.unpacked/dist arch=linux/x64
2025-01-30 13:42:07.378 waveterm-app could not get single-instance-lock, shutting down
2025-01-30 13:42:10.383 waiting for wavesrv to exit...
2025-01-30 13:48:08.802 waveterm-app starting, data_dir=/home/user/.local/share/waveterm, config_dir=/home/user/.config/waveterm electronpath=/opt/Wave/resources/app.asar/dist gopath=/opt/Wave/resources/app.asar.unpacked/dist arch=linux/x64
2025-01-30 13:48:08.806 waveterm-app could not get single-instance-lock, shutting down
2025-01-30 13:48:11.811 waiting for wavesrv to exit...
2025-01-30 13:49:43.690 waveterm-app starting, data_dir=/home/user/.local/share/waveterm, config_dir=/home/user/.config/waveterm electronpath=/opt/Wave/resources/app.asar/dist gopath=/opt/Wave/resources/app.asar.unpacked/dist arch=linux/x64
2025-01-30 13:49:43.694 waveterm-app could not get single-instance-lock, shutting down
2025-01-30 13:49:46.699 waiting for wavesrv to exit...

Questionnaire

  • [ ] I'm interested in fixing this myself but don't know where to start
  • [ ] I would like to fix and I have a solution
  • [ ] I don't have time to fix this right now, but maybe later

Zinodel avatar Jan 30 '25 08:01 Zinodel

If you run ps do you see another instance of Wave running?

esimkowitz avatar Jan 31 '25 02:01 esimkowitz

If you run ps do you see another instance of Wave running?

Before starting waveterm:

ps aux | grep wave                                                                                                                                                    ─╯
dufimts+    4449  0.0  0.0 230496  2476 pts/0    S+   11:16   0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox --exclude-dir=.venv --exclude-dir=venv wave

After starting:

ps aux | grep wave                                                                                                                                                    ─╯
dufimts+    4486 29.0  1.1 1216815612 191036 ?   Sl   11:16   0:01 /opt/Wave/waveterm --enable-features --ozone-platform-hint --no-sandbox UseOzonePlatform auto
dufimts+    4490  2.3  0.5 34472784 83256 ?      S    11:16   0:00 /opt/Wave/waveterm --type=zygote --no-zygote-sandbox --no-sandbox
dufimts+    4491  2.3  0.5 34472788 83752 ?      S    11:16   0:00 /opt/Wave/waveterm --type=zygote --no-sandbox
dufimts+    4508  2.1  0.1 2215952 28096 ?       Sl   11:16   0:00 /opt/Wave/resources/app.asar.unpacked/dist/bin/wavesrv.x64
dufimts+    4539  5.7  0.5 34650800 84736 ?      Sl   11:16   0:00 /opt/Wave/waveterm --type=gpu-process --no-sandbox --enable-crash-reporter=934ec0fc-0a55-45d6-aeca-a66514a6670b,no_channel --user-data-dir=/home/dufimtsev/.config/Wave --gpu-preferences=UAAAAAAAAAAgAAAEAAAAAAAAAAAAAAAAAABgAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAABAAAAAAAAAAEAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAA --shared-files --field-trial-handle=3,i,12347985032719591278,18248163973267811239,262144 --disable-features=SpareRendererForSitePerProcess --variations-seed-version
dufimts+    4543  4.0  0.6 34277064 102504 ?     Sl   11:16   0:00 /opt/Wave/waveterm --type=utility --utility-sub-type=network.mojom.NetworkService --lang=ru --service-sandbox-type=none --no-sandbox --enable-crash-reporter=934ec0fc-0a55-45d6-aeca-a66514a6670b,no_channel --user-data-dir=/home/dufimtsev/.config/Wave --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,12347985032719591278,18248163973267811239,262144 --disable-features=SpareRendererForSitePerProcess --variations-seed-version
dufimts+    4572 18.8  0.8 1216802108 136476 ?   Sl   11:16   0:00 /opt/Wave/waveterm --type=renderer --enable-crash-reporter=934ec0fc-0a55-45d6-aeca-a66514a6670b,no_channel --user-data-dir=/home/dufimtsev/.config/Wave --app-path=/opt/Wave/resources/app.asar --enable-sandbox --no-sandbox --lang=ru --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=4 --time-ticks-at-unix-epoch=-1738304096435575 --launch-time-ticks=112448346 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,12347985032719591278,18248163973267811239,262144 --disable-features=SpareRendererForSitePerProcess --variations-seed-version
dufimts+    4589 20.9  0.8 1216801724 134652 ?   Sl   11:16   0:00 /opt/Wave/waveterm --type=renderer --enable-crash-reporter=934ec0fc-0a55-45d6-aeca-a66514a6670b,no_channel --user-data-dir=/home/dufimtsev/.config/Wave --app-path=/opt/Wave/resources/app.asar --enable-sandbox --no-sandbox --lang=ru --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=5 --time-ticks-at-unix-epoch=-1738304096435575 --launch-time-ticks=113107818 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,12347985032719591278,18248163973267811239,262144 --disable-features=SpareRendererForSitePerProcess --variations-seed-version
dufimts+    4611  0.0  0.0 230496  2368 pts/0    S+   11:16   0:00 grep --color=auto --exclude-dir=.bzr --exclude-dir=CVS --exclude-dir=.git --exclude-dir=.hg --exclude-dir=.svn --exclude-dir=.idea --exclude-dir=.tox --exclude-dir=.venv --exclude-dir=venv wave

Zinodel avatar Jan 31 '25 06:01 Zinodel

I had similar issues. Waveterm started the first time, but then crashed for some reason and despite deleting the entire config directory and the Wave directory, and even restarting the entire computer, the app doesnt want to start again.

I have no idea whats going on. Its starting and running but no user interface shows up, so cant do anything. Very frustrating.

Too bad, seemed like a nice terminal to explore. But ive never had a terminal not show its user interface before after a crash and clean config.

Im on Arch Linux using Gnome under Wayland.

linux-cultist avatar Mar 22 '25 15:03 linux-cultist