• 0 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: June 2nd, 2023

help-circle
  • I think it’s possible that the filesystem ran out of inodes, so even though there is space on disk, there is no space in the filesystem metadata to store new files.

    Now, I don’t know off the top of my head how to check this, but I assume the answer is on the internet somewhere (am on phone and can’t help much more than this, sorry)



  • if you’re using windows and expect any privacy at all […] throw that notion out the window

    Correct. And the same is true even if you are using linux, macOS, android, or a butterfly to manipulate bits to send a message through the internet.

    Because if your message ends up on the screen of a windows user, it’s also going to be eaten by AI.

    And forget the notion of “anything you post on the internet is forever”, this is also true for private and encrypted comms now. At least as long as they can be decrypted by your recipient, if they use windows.

    You want privacy and use linux? Well, that’s no longer enough. You now also need to make sure that none of your communications include a (current or future) windows user as they get spyware by default in their system.

    Well maybe not quite by default, yet



  • Reread the OP. They say:

    not on GNOME, because you have a panel at the top

    And

    when usign GTK apps on those [non-GNOME] desktops

    So you would not “access the controls above the app”, because having controls above the app is not covered by this scenario.

    The scenario is:

    1. You don’t have a top panel
    2. You have a maximized GTK app

    Which makes the close button be in the corner of the screen, but without actually extending to it.

    On topic: never knew this was a problem, guess I got spoiled by the Qt environment




  • The “or later” is optional, the FSF specifically doesn’t have the power to update the terms of every GPL-licensed software because the wrote the clause in such a way that they don’t.

    If I give you software licensed under the GPL3, and a GPL3.1 comes out, it doesn’t apply to your copy of the software. Likewise the copyright holder of the work is also not forced to relicense their software under the GPL3.1. And even if they did, copies of the software distributed under the GPL3 would still be licensed under the GPL3.

    The “or later” clause simply means that if I received a copy of a GPL3 software, I can redistribute it under the GPL3.1 if I so wish (where “I” in the previous sentence is everyone with a copy of the work, as the GPL gives everyone with a copy redistribution rights)


  • Maybe Eidos would love to get another Deus Ex out there but there’s no publisher interest

    You know, they could just… Say this, and placate everyone. I’m honestly sick and tired of companies in general, and game companies specifically, being afforded this stupid level of opaqueness.

    If you were to talk to someone that would exclusively stonewall you, you’d be quick to stop talking to this person. When it’s game companies though, everyone bends over backwards to try to find justifications for their behavior on their behalf.



  • ugo@feddit.ittoLinux Gaming@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    7 months ago

    I don’t know how to help you directly, but you could write a script that turns vibration on, then sleeps for an appropriate amount of time, and loops indefinitely. This way even if vibration stops after a few seconds, the script will turn it back on immediately.

    As for vibration strength, I have no clue. SDL has controller APIs, maybe it’s able to control vibration intensity. In which case, one could write a CLI SDL-based program for this.




  • ugo@feddit.ittoLinux@lemmy.mlGamedev and linux
    link
    fedilink
    arrow-up
    29
    arrow-down
    1
    ·
    8 months ago

    In my somewhat limited but relevant experience, the amount of platform specific bugs is indeed that low. I mean, there’s of course a layer of platform-specific low level stuff which is highly subject to platform specific issues, but once you go above that layer and into game code proper, most bugs are just bugs.

    I didn’t fix 400 “Linux-only” bugs, but I did fix dozens of “seems Linux specific” and “only happened when at least one Linux client was connected” bugs, and a grand total of 2 were caused by platform differences. And of those two, zero were Linux specific. The platform difference in this case was about how different compilers optimise non-crashy types of UB.

    Of course, we don’t want UB at all so the fix is to remove it.