Our News Team @ 11 with host Snot Flickerman


Yes, I can hear you, Clem Fandango!

  • 0 Posts
  • 37 Comments
Joined 3 years ago
cake
Cake day: October 24th, 2023

help-circle






  • I’m accepting that I’m becoming a little of a pointy head boss here.

    Dilbert fans are almost always as big of losers as Scott Adams was.

    Scott Adams once made a sockpuppet account on MetaFilter to make positive comments about himself, got outed almost immediately, then claimed that was always his goal. What a fucking loser.



  • Once again, this isn’t a bug thread, this is literally me, talking about an issue with the Linux community, which was ignored in favor of… all my complaints.

    If you guys can’t wrap your mind around that I don’t know what to tell you. I didn’t need help, I know there’s not currently a solution for me. I need people to not be asshats and assuming I must be doing it wrong because I have a problem to begin with… because it couldn’t possibly be Linux that has an edge case! No, it’s the users who are wrong!

    Fucking jackasses.





  • Hey look, it’s one of the folks I’m talking about:

    I’m assuming you’re trying to turn your monitor off while there is still an active HDMI signal for some reason? Otherwise why wouldn’t you just let the monitor put itself to sleep when it detects no signal like everyone else I know?

    Nah, I’m trying to let the monitors put themselves to sleep, genius. That’s what’s not working. There shouldn’t still be an active HDMI signal. Disabling DCC/CI doesn’t fix the problem, either, it just goes back to the monitors not actually ever shutting off, just turning off for a moment and then coming back on, with plasmashell crashing instead of the power monitor. I don’t care at all about controlling monitor brightness with DCC/CI but when the defaults cause crashes that’s an issue.

    This is an out-of-the-box fresh install with no old dotfiles moved, complete refresh. These were the defaults I was given. Deciding to set your monitors to power down after 10 mins of inactivity shouldn’t be causing crashes. i shouldn’t have to manually turn my monitors off or do hacky shit with xscreensaver to get it working in fucking wayland just to not have monitor burn-in







  • Another pain in the ass for me — connecting dualsense controller via bluetooth. It connects, then just disconnects. There a workaround that includes fetching it’s ID via terminal, then using commands to connect and entrust that device. After that it connects fine. Until you need to reconnect it, that is, cause it stops being recognized. Apparently that was fixed like, a year ago. Yeah, right.

    Well uhh, guess there go my plans to eventually get a dualshock controller…


  • I mean, I’m not trying to be dismissive of the hard work the devs do at all.

    My real issue is with the endless “It’s easier than Windows now lolz!” I’ve literally been browbeaten and downvoted I don’t know how many fucking times by asshats PROMISING me that problems like this don’t fucking exist and it’s FINE to load up Linux for fucking Grandma. Oh so when the power subsystem keeps crashing and Grandma doesn’t know how to send an error report, it’s just fine?

    The issue isn’t the lack of solution, the issue is Linux afficianodos acting like real problems like these are bullshit and it’s child’s play to make the jump from Windows/macOS to Linux.

    And it’s not! Linux is demands more of you! It doesn’t baby you or do it for you. The last ten years have been nothing but research and figuring shit out. Windows and mac treat users like babies and Linux treats users like adults and it’s not an easy transition for a lot of folks. Windows takes away your agency, Linux demands your agency.

    Sorry for the rant, I just want people to recognize Linux still has it’s quirks and that’s fine but acting like it’s for everyone is a fucking joke and a crock of shit.