Bastyon crashes on different Ubuntu Mate releases and different Bastyon releases.

[lancelab]

We do not seem valid explanations that something is wrong with Mate, with PC etc. because other few dozen and possibly hundred applications do not crash.
Therefore, something probably has to be fixed in Bastyon code.

Bug screenshots are documented here:
https://bastyon.com/post?s=9cff987f49be178155d5dfef1104fa55ee9891620082762027c09299d198032a&ref=PX74b2z1sFUjP3adtpiWjzDXkmG9eqLiB1

https://bastyon.com/post?s=9cff987f49be178155d5dfef1104fa55ee9891620082762027c09299d198032a&ref=PX74b2z1sFUjP3adtpiWjzDXkmG9eqLiB1

Thank you for your attention.

[andyoknen]

We do not seem valid explanations that something is wrong with Mate, with PC etc. because other few dozen and possibly hundred applications do not crash. Therefore, something probably has to be fixed in Bastyon code.

Bug screenshots are documented here:
https://bastyon.com/post?s=9cff987f49be178155d5dfef1104fa55ee9891620082762027c09299d198032a&ref=PX74b2z1sFUjP3adtpiWjzDXkmG9eqLiB1

https://bastyon.com/post?s=9cff987f49be178155d5dfef1104fa55ee9891620082762027c09299d198032a&ref=PX74b2z1sFUjP3adtpiWjzDXkmG9eqLiB1

Thank you for your attention.

Could you provide the log output after the crash?

> journalctl -u bastyon

You can also try to launch bastyon through the terminal and wait for it to fall and send the terminal output.

[lancelab]

Thank you very much.

I don't know how to start bastyon in command line:
pol@pc:/ww$ man bastyon
No manual entry for bastyon
pol@pc:/ww$
Desktop shortcut does exist in this form
/opt/Bastyon/bastyon %U
but is the parameters %U specific only for desktop?

I removed Bastyon from autolaunch and started it manually. It works find, here is a console output while Bastyon is working:

pol@pc:~/ww$ bastyon
MESA-INTEL: warning: Haswell Vulkan support is incomplete
useSnowFlake2 false
21:47:10.073 › Checking for update
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
21:47:12.013 › Found version 0.9.129 (url: Bastyon.AppImage, BastyonSetup.deb, BastyonSetup.rpm)
autoLaunchIsEnabled {}
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor config successfully created
Tor start triggered
this.getpath() /home/pol/data/tor/tor /home/pol/data/tor
Tor running with pid: 6527
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor instance started again
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
(node:6430) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
(Use bastyon --trace-deprecation ... to show where the warning was created)
SOCKS5 proxy rejection
Tor retrying circuit
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
Tor retrying circuit
SOCKS5 proxy rejection
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit

[andyoknen]

@lancelab that is, running from the console works constantly and does not cause crashes? During the same time of operation, does the one launched through the shortcut fail?

[lancelab]

Thank you andyoknen. I've caught more crash info.

1. Here is the full log, when running manually from command line. It has few errors there meaning of which not clear to me.
2. Move important, I did remove Bastyon from launch-time list. But once I powere up the PC, bastyon suddenly started without my intervention and crashed.

So first 1) the cli log and second, the info about 2) unexpected launch.
pol@pc:$ cd ww
pol@pc:/ww$ bastyon
MESA-INTEL: warning: Haswell Vulkan support is incomplete
useSnowFlake2 false
21:47:10.073 › Checking for update
libva error: /usr/lib/x86_64-linux-gnu/dri/iHD_drv_video.so init failed
21:47:12.013 › Found version 0.9.129 (url: Bastyon.AppImage, BastyonSetup.deb, BastyonSetup.rpm)
autoLaunchIsEnabled {}
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor config successfully created
Tor start triggered
this.getpath() /home/pol/data/tor/tor /home/pol/data/tor
Tor running with pid: 6527
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor start triggered
Tor instance started again
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
(node:6430) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
(Use bastyon --trace-deprecation ... to show where the warning was created)
SOCKS5 proxy rejection
Tor retrying circuit
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
Tor retrying circuit
SOCKS5 proxy rejection
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
SOCKS5 proxy rejection
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
SOCKS5 proxy rejection
SOCKS5 proxy rejection
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
SOCKS5 proxy rejection
SOCKS5 proxy rejection
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
SOCKS5 proxy rejection
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
SyntaxError: Unexpected token 'U', "Unhandled "... is not valid JSON
at JSON.parse ()
at Request._callback (/opt/Bastyon/resources/app.asar/proxy16/remotelight.js:136:15)
at self.callback (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:185:22)
at Request.emit (node:events:518:28)
at Request. (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:1154:10)
at Request.emit (node:events:518:28)
at IncomingMessage. (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:1076:12)
at Object.onceWrapper (node:events:632:28)
at IncomingMessage.emit (node:events:530:35)
at endReadableNT (node:internal/streams/readable:1698:12)
Tor retrying circuit
Tor retrying circuit
SOCKS5 proxy rejection
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
SOCKS5 proxy rejection
Tor retrying circuit
Tor retrying circuit
Tor retrying circuit
autoLaunchIsEnabled {}
SOCKS5 proxy rejection
SOCKS5 proxy rejection
Tor retrying circuit
SOCKS5 proxy rejection
autoLaunchIsEnabled {}
Tor was idle for 5 minutes, switching it off
SyntaxError: Unexpected token 'U', "Unhandled "... is not valid JSON
at JSON.parse ()
at Request._callback (/opt/Bastyon/resources/app.asar/proxy16/remotelight.js:136:15)
at self.callback (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:185:22)
at Request.emit (node:events:518:28)
at Request. (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:1154:10)
at Request.emit (node:events:518:28)
at IncomingMessage. (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:1076:12)
at Object.onceWrapper (node:events:632:28)
at IncomingMessage.emit (node:events:530:35)
at endReadableNT (node:internal/streams/readable:1698:12)
SyntaxError: Unexpected token 'U', "Unhandled "... is not valid JSON
at JSON.parse ()
at Request._callback (/opt/Bastyon/resources/app.asar/proxy16/remotelight.js:136:15)
at self.callback (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:185:22)
at Request.emit (node:events:518:28)
at Request. (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:1154:10)
at Request.emit (node:events:518:28)
at IncomingMessage. (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:1076:12)
at Object.onceWrapper (node:events:632:28)
at IncomingMessage.emit (node:events:530:35)
at endReadableNT (node:internal/streams/readable:1698:12)
autoLaunchIsEnabled {}
autoLaunchIsEnabled {}
22:47:10.120 › Checking for update
22:47:11.404 › Found version 0.9.129 (url: Bastyon.AppImage, BastyonSetup.deb, BastyonSetup.rpm)
SyntaxError: Unexpected token 'U', "Unhandled "... is not valid JSON
at JSON.parse ()
at Request._callback (/opt/Bastyon/resources/app.asar/proxy16/remotelight.js:136:15)
at self.callback (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:185:22)
at Request.emit (node:events:518:28)
at Request. (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:1154:10)
at Request.emit (node:events:518:28)
at IncomingMessage. (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:1076:12)
at Object.onceWrapper (node:events:632:28)
at IncomingMessage.emit (node:events:530:35)
at endReadableNT (node:internal/streams/readable:1698:12)
SyntaxError: Unexpected token 'U', "Unhandled "... is not valid JSON
at JSON.parse ()
at Request._callback (/opt/Bastyon/resources/app.asar/proxy16/remotelight.js:136:15)
at self.callback (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:185:22)
at Request.emit (node:events:518:28)
at Request. (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:1154:10)
at Request.emit (node:events:518:28)
at IncomingMessage. (/opt/Bastyon/resources/app.asar/node_modules/request/request.js:1076:12)
at Object.onceWrapper (node:events:632:28)
at IncomingMessage.emit (node:events:530:35)
at endReadableNT (node:internal/streams/readable:1698:12)
23:47:10.120 › Checking for update
23:47:11.400 › Found version 0.9.129 (url: Bastyon.AppImage, BastyonSetup.deb, BastyonSetup.rpm)

[lancelab]

2. unexpected launch.

Full info here:
https://bastyon.com/index?v=6b49eeeccc2546984f4f543014aac94d82bac63c3e09972e5ab1dfb088c69816&video=1&ref=PX74b2z1sFUjP3adtpiWjzDXkmG9eqLiB1

including following part of the system log:

Thank you once again.

2025-08-21T08:45:01.813546-05:00 pc CRON[3564]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
2025-08-21T08:45:07.470126-05:00 pc systemd[1]: Started whoopsie.service - crash report submission.
2025-08-21T08:45:07.481605-05:00 pc whoopsie[3568]: [08:45:07] Using lock path: /var/lock/whoopsie/lock
2025-08-21T08:45:07.483996-05:00 pc whoopsie[3568]: [08:45:07] Parsing /var/crash/_opt_Bastyon_bastyon.1001.crash.
2025-08-21T08:45:07.586827-05:00 pc whoopsie[3568]: [08:45:07] Uploading /var/crash/_opt_Bastyon_bastyon.1001.crash.
2025-08-21T08:45:08.283014-05:00 pc kernel: audit: type=1400 audit(1755783908.281:165): apparmor="AUDIT" operation="userns_create" class="namespace" info="Userns create - transitioning profile" profile="unconfined" pid=3567 comm="bastyon" requested="userns_create" target="unprivileged_userns"
2025-08-21T08:45:08.284993-05:00 pc kernel: audit: type=1400 audit(1755783908.283:166): apparmor="DENIED" operation="capable" class="cap" profile="unprivileged_userns" pid=3573 comm="bastyon" capability=21 capname="sys_admin"
2025-08-21T08:45:08.311430-05:00 pc whoopsie[3568]: [08:45:08] Sent; server replied with: No error
2025-08-21T08:45:08.311512-05:00 pc whoopsie[3568]: [08:45:08] Response code: 200
2025-08-21T08:45:08.313551-05:00 pc whoopsie[3568]: [08:45:08] Reported OOPS ID 0cb298e9-7e95-11f0-b84e-fa163ec8ca8c
2025-08-21T08:45:08.319070-05:00 pc systemd[1]: whoopsie.service: Deactivated successfully.
2025-08-21T08:45:11.962905-05:00 pc dbus-daemon[1118]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.96' (uid=1001 pid=3567 comm="/opt/Bastyon/bastyon" label="unconfined")
2025-08-21T08:45:11.968052-05:00 pc systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).

[andyoknen]

@lancelab Maybe there will be something interesting in the /var/crash/_opt_Bastyon_bastyon.1001.crash file? Yeah, I see a video in the post. Please send this file, I will try to study it.

[lancelab]

Thank you. This file is 60 Megabytes big. You sure this log file does not leak sensitive/personal info about PC? Keys?

[andyoknen]

Thank you. This file is 60 Megabytes big. You sure this log file does not leak sensitive/personal info about PC? Keys?

I don't think so, but you can check it just in case, try to look for your private key or some other data in it.

[lancelab]

Thank you. This sounds scary:

"I don't think so, but you can check it just in case, try to look for your private key or some other data in it."

Well how can I check it? The keys may be slightly encoded and direct text comparison won't find them. And I may have 30 addresses/keys/accounts, this is quite a job.

I must be absolutely confident that logs cannot have traces of the keys. Perhaps a separate fresh PC should be setup for this job.

[andyoknen]

Thank you. This sounds scary:

"I don't think so, but you can check it just in case, try to look for your private key or some other data in it."

Well how can I check it? The keys may be slightly encoded and direct text comparison won't find them. And I may have 30 addresses/keys/accounts, this is quite a job.

I must be absolutely confident that logs cannot have traces of the keys. Perhaps a separate fresh PC should be setup for this job.

Strictly speaking, the node does not log private data anywhere in the code, even in encrypted form. I asked you to double check for your convenience;)