search

d99kris / nchat

Terminal-based Telegram / WhatsApp client for Linux and macOS
MIT License
524 stars 40 forks source link

"ABORTED" immidiately after launch #208

Closed hit0wnzzz closed 2 months ago

hit0wnzzz commented 3 months ago

Immidiately after launch, i get "ABORTED" message.

Sometimes removing the account and setting up again will have nchat working for a couple of days.

WSL Ubuntu 22.04.03 - Windows 10

attached log: log.txt

hit0wnzzz commented 3 months ago

image

d99kris commented 3 months ago

Hi @hit0wnzzz - thanks for the detailed bug report! It is possible this issue has been fixed in newer versions of nchat. According to the log you're using v4.13 (latest stable release), while latest master is v4.41. The next stable release is targetted this weekend. So if you prefer to use stable releases, you could wait until then, update and see if the problem is fixed.

If you don't mind doing some debugging, you could help to obtain the backtrace of the crash by following these steps:

1. Enable core dumps
ulimit -c unlimited

2. Run nchat
nchat

3. Upon encountering crash, the following should be output on the terminal:
Aborted (core dumped)

4. Reset terminal and check core dump location
reset
cat /proc/sys/kernel/core_pattern

6. Assuming the output is /mnt/wslg/dumps/core.%e, then do:
gdb $(which nchat) /mnt/wslg/dumps/core.nchat -ex backtrace -ex quit

7. Copy the output of above command and paste in a comment here.

Note: ulimit is per shell session, so it may be safest to call it every time before starting nchat, in case you rebooted or switched terminal window. In newer versions of nchat (from v4.25) one can enable core dumps using an app.conf setting, without the need to call ulimit.

d99kris commented 3 months ago

Hi - the quarterly stable release of nchat is available now. Please try it out and let me know if the crash is fixed. Thanks!

d99kris commented 2 months ago

Hi again - I cannot troubleshoot this further without more information, so I will proceed to close this issue. Feel free to re-open it if you're still facing the issue, and please help provide additional details mentioned in my earlier comment.