Disclaimer: I don’t represent KDE in any interaction with this account. I am just freeloading off of the kde.social server.

  • 5 Posts
  • 732 Comments
Joined 1 year ago
cake
Cake day: December 20th, 2023

help-circle


  • Doesn’t even startup on my box,

    It needs to startup and then go to that point (after you select the projection) to cause the crash.
    It definitely caused something other than the application to get into an invalid state. Which is why I am apprehensive about trying it out again to answer your comment. Probably was the display driver, which is why it didn’t just turn off after that.







  • There’s this game “HyperRougue”. Run it on Arch.

    hyperrogue-git version 13.0d.r60.g27fb2d92-1

    Go to settings -> 3D configuration -> projection -> projection type -> . Cycle through the projection types. One of them causes something good enough to call a crash.

    I don’t remember anymore if it was just a display driver crash or a kernel crash and I haven’t updated to a newer version (which might have fixed it).


  • What language were you using?
    Python maybe? I don’t know of any other interpreted language, that you may be calling system commands from, without saving to disk

    I use C and C++ and my IDEs save to disk before compiling. Makes sense to not try compiling when there are potentially 2 versions (one on RAM or /tmp and one on Disk) and the build system might be running multiple commands, which the IDE may/may not know of, in my case.