Closed niclasborlin closed 1 year ago
Ubuntu 20.04.5 LTS
AMD® Ryzen 7 3800x 8-core processor × 16
AMD® Radeon rx 5600 xt
GNOME version 3.36.8
Similar behavior is happening for me for:
Ubuntu 22.04.1 LTS with Regolith 2.1
AMD® Ryzen 7 pro 5850u with radeon graphics × 16
AMD® Renoir
GNOME version 42.4
Tested both with .deb package and AppImage.
Update: After below comment I also tested 1.10.0 and Stretchly still crashes.
Same happening to me for:
I noticed the pattern since upgrading Stretchly to v. 1.11.0.
stefan@fedora ~ $ stretchly
09:58:12.888 › Stretchly: initializing...
09:58:12.900 › Stretchly: loading preferences
09:58:12.911 › Stretchly: starting Idle time monitoring
09:58:12.912 › Stretchly: starting Do Not Disturb monitoring
09:58:12.959 › Stretchly: loading default break ideas
libva error: vaGetDriverNameByIndex() failed with unknown libva error, driver_name = (null)
09:58:12.989 › Stretchly: loading default break ideas
10:13:02.916 › Stretchly: showing Mini Break notification
10:13:13.159 › Stretchly: showing window 1 of 2
10:13:13.160 › Stretchly: starting Mini Break
10:13:13.180 › Stretchly: showing window 2 of 2
10:13:33.161 › Stretchly: finishing Mini Break (shouldPlanNext: true)
10:13:50.946 › Stretchly: arguments received from second instance:
10:13:50.947 › Stretchly: command 'help' executed in second instance, dropped in main instance
10:28:13.164 › Stretchly: showing Long Break notification
10:28:33.425 › Stretchly: showing window 1 of 2
10:28:33.427 › Stretchly: starting Long Break
10:28:33.437 › Stretchly: showing window 2 of 2
10:32:28.195 › Stretchly: finishing Long Break (shouldPlanNext: true)
Update: Problem persists after downgrading to 1.10.0.
A similar thing is happening to me after I log back in after putting my computer to sleep. Ubuntu 20.4
could you guys see this issue, might be the same: https://github.com/hovancik/stretchly/issues/633#issuecomment-687633349
trying with gdb
might give more useful debug info
@hovancik Thanks for the pointer. I've been running Stretchly 1.12.0 for a half day now with gdb debugging, but this error hasn't occurred (before it took less than that to surface). After running 1.11.0 with gdb debugging again this error hasn't surfaced. Something must have change in the underlying system - in my case Ubuntu 22.04.
After reviewing apt history for the hunt of libappindicator
upgrade I found out that in my system it is provided via libayatana-appindicator3-1:amd64 (0.5.5-3)
and it hasn't been touched since system installation in fall last year. Hard to tell what else has changed that could have fixed this issue, however it does not occur to me anymore.
Thanks for you work!
I've commented on the testing prematurely. Stretchly 1.11.0 just crashed on me with following gdb stack trace:
Thread 1 "stretchly" received signal SIGSEGV, Segmentation fault.
0x00007fffe55fcdc5 in ?? () from /lib/x86_64-linux-gnu/libappindicator3.so.1
I'm going back to running 1.12.0…
After running Stretchly 1.12.0 for straight two days now, with one hibernate in the meantime I haven't encountered this error.
@hovancik In the changelog you've mentioned you've trimmed down tray requests. I suppose it could have fixed or hidden this bug. As per bug report you've linked this is a bug in upstream library, with fix that probably hasn't been introduced to all distros, yet.
Yeah, with latest version, the tray is updated much less frequent, so probably lower chance of the issue happening :)
I'm closing this, if issue appears again, we can reopen.
Also, Electron has now new tray implementation, so new Stretchly version will have that.
Version
Known issues
Existing issues
What operating system are you using?
Linux
Operating System Version
Ubuntu 20.04, Linux earth 5.15.0-46-generic #49~20.04.1-Ubuntu SMP Thu Aug 4 19:15:44 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Reproduction steps
Expected Behavior
no crash
Actual Behavior
crash after some time
Relevant log output
Preferences
Additional information
Code of Conduct