Arch Linux

The Piccion

Member

Registered: 2021-04-01

Posts: 8

[Solved] Whatsie crashes due to segmentation fault

Hi everyone,

I am currently using whatsie and it has been 2 or 3 days that the app keeps crashing after a while it is opened. I firstly checked if it was updated and it should be, as paru can't find any newer version.
I tried with strace to check what whatise is doing while the crash happens and this are last fiew lines in the output file:

clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=414806545}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=414838952}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=414871847}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=414904743}) = 0
ppoll([{fd=4, events=POLLIN}, {fd=112, events=POLLIN}, {fd=182, events=POLLIN}], 3, {tv_sec=0, tv_nsec=0}, NULL, 8) = 1 ([{fd=4, revents=POLLIN}], left {tv_sec=0, tv_nsec=0})
read(4, "\2\0\0\0\0\0\0\0", 8)          = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415007620}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415040097}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415072992}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415106307}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415139203}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415172587}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415204994}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415238309}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415271903}) = 0
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
write(4, "\1\0\0\0\0\0\0\0", 8)         = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415386374}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415419269}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415452165}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415485061}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415518166}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415551061}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415583957}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415616853}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415650167}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415683063}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415715959}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415841535}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415877294}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415910189}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415943085}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=415975981}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416008876}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416041632}) = 0
ppoll([{fd=4, events=POLLIN}, {fd=112, events=POLLIN}, {fd=182, events=POLLIN}], 3, {tv_sec=0, tv_nsec=0}, NULL, 8) = 1 ([{fd=4, revents=POLLIN}], left {tv_sec=0, tv_nsec=0})
read(4, "\2\0\0\0\0\0\0\0", 8)          = 8
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416144789}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416177684}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416220009}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416253882}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416286708}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416319883}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416352220}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416385115}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416418989}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416453281}) = 0
clock_gettime(CLOCK_MONOTONIC, {tv_sec=4774, tv_nsec=416486247}) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x248133abb1} ---
+++ killed by SIGSEGV (core dumped) +++

I hope that someone is able to understand what causes the segmentation fault as I honeslty don't get it

Last edited by The Piccion (2024-11-01 22:42:21)

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 12,482

Website

Re: [Solved] Whatsie crashes due to segmentation fault

Mod note: Moving to AUR Issues.

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

The Piccion

Member

Registered: 2021-04-01

Posts: 8

Re: [Solved] Whatsie crashes due to segmentation fault

Update to the new whatsie version (4.16.3) solved the problem