Random silent crashes

[TheInfamousAlk]

Describe the Bug/Issue

The program will silently crash at some point after being online for a few hours. Almost once a day.

Your Environment

OS: Pop!_OS 22.04 LTS x86_64 Kernel: 6.9.3-76060903-generic Resolution: 1200x1920, 1920x1080, 2560x1440, 3840x2160 (yeah my monitor setup is wack, which is why I need cursr) DE: GNOME 42.9 WM: Mutter CPU: Intel i9-9900KF (16) @ 5.000GHz GPU: NVIDIA GeForce RTX 2080 Ti Rev. A

Cursr version 1.7.2

Latest log attached. (File removed by @ragauskl)

[TheInfamousAlk]

Here's my monitor configuration if this matters:

[ragauskl]

I downloaded the log file and removed it, I prefer to not keep full individual user logs in public place like github.

I do see compatibility issues, first thing is Xrandr is missing, you can try installing it and see if that will resolve the issue. Another issue is 'Error reading path of process from /proc/0/exe' and similar which I haven't seen before at all, unless I do some testing on Pop!_OS I can't say for sure what the underlaying issue may be as it's first reported occurrence. Both errors may or may not be related to the actual segmentation fault crash, but all could be due to Pop!_OS compatibility.

I noted down to look into this but right now can't promise a time estimate/when to expect a fix as right now there are higher priority tasks on my list. I'll provide an update when I'll start looking into this

[TheInfamousAlk]

Okay thank you for removing that.

It looks like on my repo, xrandr doesn't exist, and it says x11-xserver-utils replaces it. I will try installing that, or do you recommend I manually find and install Xrandr instead? Shown below, neither is listed in the dependencies for apt. EDIT: it turns out I already have x11-xserver-utils installed. So clearly that won't fix it lol

~$ apt-cache depends cursr
cursr
  Depends: libgtk-3-0
  Depends: libnotify4
  Depends: libnss3
  Depends: libxss1
  Depends: libxtst6
  Depends: xdg-utils
  Depends: libatspi2.0-0
  Depends: libuuid1
  Depends: libsecret-1-0
  Recommends: libappindicator3-1
    libayatana-appindicator3-1

Output when I tried to install Xrandr:

~$ sudo apt install xrandr
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package xrandr is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
  x11-xserver-utils

I don't know anything about the /proc/0/exe thing so I can't give any insight on that unless you have specific questions for me.

[ragauskl]

If x11-server-utils does not fix it, you can try looking for Xrandr but you may face more missing dependencies until you install everything required.

Regarding '/proc/0/exe ' the process number does not matter, my guess it's either Cursr not being able to read data about it's own processes or Cursr not being able to get data on other processes when it checks for any focused windows where 'auto-disable' should get triggered (if you have set auto-disable) on any of the processes.

I think it's more likely that xrandr issue is related to the crash than the '/proc/0/exe' one.

[ragauskl]

Before you look into Xrandr, can you delete old log files, enable Debug mode in settings and wait for the crash to happen, then send me the logs files (all app.log, like app2.log etc if there are any) to contact@cursr.app?

Then I may better understand if the crash happens when functions using xrandr are being called or is it something else - in which case Xrandr issue is small inconvenience but not the cause of the crash.

As long as the issue does not occur you can delete the logs as often as you'd like in case you're concerned about key strokes being included in the log from extended period of time.

[TheInfamousAlk]

Yeah, I will wait a couple days for it to crash again. I just deleted my logs and turned on Debug mode. Thanks!

[TheInfamousAlk]

So my power went out for 3 days as I got hit with hurricane Helene, but now I'm back! And it has happened again, but it seems like debug mode has been disabled without my input since I last enabled it, and no extra data was captured in the logs. I will now start keeping an eye on debug mode and enabling it manually when I notice it has been disabled, at least until we get the logs we need.