xavier666

joined 2 years ago
[–] xavier666@lemm.ee 3 points 9 months ago

Thanks. I completely forgot that the standard suntan or sunburn is caused by UV rays. A fireplace doesn't create UV rays.

[–] xavier666@lemm.ee 4 points 9 months ago* (last edited 9 months ago)

Note to self - Don't sit near a magnesium fireplace if you don't want to tan your bones, which are now exposed due to the flesh getting melted off by the said fireplace.

[–] xavier666@lemm.ee 0 points 9 months ago
[–] xavier666@lemm.ee 3 points 9 months ago (6 children)

Hypothetically speaking, will you get sunburnt if you sit near a fire all day?

[–] xavier666@lemm.ee 3 points 9 months ago
[–] xavier666@lemm.ee 1 points 9 months ago* (last edited 9 months ago)

Looks suspiciously like https://github.com/marktext/marktext

Edit: Ignore please, the project is dead

[–] xavier666@lemm.ee 1 points 9 months ago

"No officer, you can't shoot me. I have a LLM in my pocket. Without me, it'll stop learning"

[–] xavier666@lemm.ee 3 points 9 months ago

Duality of man...

[–] xavier666@lemm.ee 5 points 9 months ago* (last edited 9 months ago)

Please be a bit considerate. It's hard for him to form human connections when you are trying to be a plague on humanity.

[–] xavier666@lemm.ee 2 points 9 months ago

"Listen here you little shit..."

[–] xavier666@lemm.ee 0 points 9 months ago (1 children)

Wait, if GPU swap is in RAM, and RAM swap is in disk, is it technically possible that my frames are saved in disk temporarily?

[–] xavier666@lemm.ee 1 points 9 months ago (1 children)

Any reason for avoiding flatpak?

42
submitted 10 months ago* (last edited 10 months ago) by xavier666@lemm.ee to c/linux_gaming@lemmy.world
 

...before this account dies.

Sorry for being so dramatic, but since my instance is closing down, i'll quickly give away some GoG codes I have lying around.

Just mention which game you would want (and make sure you intend to play it) and also write one or two lines about some good gaming memories you would like to share.

One game per account and account must be more than a week old.

  • Blood Omen 2 : Legacy of Kain
  • Wild Country
  • Mordheim: City of the Damned
  • FATE
  • Death Squared
  • ~~Mail Time~~ (Code expired)
  • ~~Wolfenstein II: The New Colossus Digital Deluxe Edition (XBOX code)~~ (Code expired)
  • ~~Wolfenstein II: The New Colossus Digital Deluxe Edition (Microsoft Store code)~~ (Code expired)
  • ~~Thief II : The Metal Age~~ (Gone)
  • ~~Hypnospace Outlaw~~ (Code expired)
  • ~~Saints Row : Gat out of Hell~~ (Gone)
  • ~~Golf With Your Friends~~ (Gone)
 
  • Will it go away if I just clean the chair?
  • What species it this?
  • Do I have to burn my house down?
  • How to avoid them from reappearing?
 

I saw the update about Steam trying to provide a way to update the BIOS however, I didn't find much discussion about it elsewhere.

Some people are saying fwupd is great, others are saying it's not supported by OEMs.

What's the current status regarding this entire thing?

 

This is mainly a rant post.

I have to use Zscaler on my work PC. I use Sway (Moved from Gnome -> i3 -> sway).

Whenever Zscaler is launched, I used to get a weird error "proxy server not found" but it continued to work otherwise. Now at my company, we used a proxy at one time but we shifted to a no-proxy connection recently.

So I checked all my environment variables, output of set command. Everything was fine. People said it could be because of some weird compliance issue, or kernel etc etc. After a week or so, I gave up on debugging it because most of my work was fine with the 50% functional Zscaler.

One day, I opened Gnome instead of Sway to check something else, and saw that my proxy was on. This is the proxy set in Gnome Settings, not environment file.

I initially dismissed this finding because I thought Gnome is not active during sway so it should not affect it. But then i remembered it's possible to access the gnome settings using gsettings from any distro.

I switched to Sway, and sure enough, when I ran gsettings get org.gnome.system.proxy.http host, I could see the proxy IP. I set it to null and behold! Zscaler was working perfectly.

I'm like "Who the hell designs software like this? The application should read the environment variables, not Gnome variables!"

Anyway, this was just a reminder to software makers to kindly follow the norms. Don't design your software for one Distro. Follow the guidelines as mentioned in freedesktop.

 

Hello fellow lemmings

I am a long-time i3 user and have decided to switch to Sway. I have encountered a weird error which has left me utterly bamboozled.

I am using Ubuntu 24.04 which has gone from 20.04 -> 22.04 -> 24.04. It has Ubuntu-Gnome, i3 and Sway currently installed.

The issue

The error that I'm facing is when I'm using Sway, I simply don't have sudo access.

This is what the error looks like

$ sudo visudo
[sudo] password for xavier666:
Sorry, user xavier666 is not allowed to execute '/usr/sbin/visudo' as root on <HOSTNAME>.

When I switch back to i3, my permissions are fine for the same user. I have not done any crazy modifications to the sudoer's file as far as I can remember.

PS: I have added a command to no-sudo xavier666 ALL = NOPASSWD: /usr/bin/brightnessctl

The "fix"

I temporarily solved it by adding xavier666 ALL=(ALL:ALL) ALL to the sudoer's file.

IMO, I think this should not be required. I don't remember ever adding the default user to the file for all the installations that I have done. (But this is the first time I've installed Sway)

Logs/Outputs

Running sudo -l without the fix (on Sway)

Matching Defaults entries for xavier666 on <HOSTNAME>:
    env_reset, mail_badpass,
    secure_path=/usr/local/sbin\:/usr/local/bin\:/usr/sbin\:/usr/bin\:/sbin\:/bin\:/snap/bin,
    use_pty

User xavier666 may run the following commands on <HOSTNAME>:
    (root) NOPASSWD: /usr/bin/brightnessctl

When I run the same command on i3, i get this (ALL : ALL) ALL extra line in the output. And when I run sudo -l with my fix on Sway, (ALL : ALL) ALL is present and the permission issue is fixed.

What is causing Sway to remove the root permission for the user?

Note: I'm just asking for the standard sudo behaviour. I'm not trying to run GUI applications as root.

 

Basically the title.

I have seen the EU-OS/Suse discussions for some months now. However, Ubuntu/Arch/Fedora are extremely mature projects. So competing against them will be hard.

I want to know how realistic the scenario (described by the question) is.

 

I am using an RoG Ally and was using Bazzite. I'm currently back on Windows (for warranty purpose. I literally can't stand the Windows experience on handhelds). Once I get my device back, I have to decide between SteamOS and Bazzite.

I saw the latest SteamOS release works quite well, except for voltage control (I know you can control it using SimpleTDPcontrol).

If I want to tinker, I can always go back to Bazzite. But Bazzite has some very minor issues (screenshot does not work OOTB/gyro support is slightly cumbersome as you need to switch controller type/no fingerprint support). I have used it for 6 months and the experience for gaming has been fantastic. The Bazzite devs have all my support.

So my question is will we ever get a proper signal from Valve saying "Yup, it's now fully compatible with the RoG Ally". Right now, i'm getting the message "We are slowly adding support for the Ally. Only features x,y and z are not working".

Are any of you Bazzite users thinking of jumping ship?

 

 

From the article

Microsoft has officially announced its intent to move security measures out of the kernel, following the Crowdstrike disaster a few short months ago. The removal of kernel access for security solutions would likely revolutionise running Windows games on the Steam Deck and other Linux systems.

 

I have a question(s) regarding the various types of game controllers.

I need a wireless controller which supports PC (Steam Linux mainly and maybe Windows someday). While searching online, I see various types

  1. xbox/ps5/switch controllers : These are for their respective consoles
  2. Mobile/PC controllers : These usually connect via wire/bluetooth/2.4 GHz

Source: https://www.gamesir.hk/

However, I see in the product specifications page of the console controllers that they also support PC. And the PC controllers sometimes support some of the consoles. The only real difference between controllers, from a technology perspective, is that is some of them support bluetooth/2.4 GHz.

So I have two questions:

  1. If they are already cross-compatible, why even bother having different types?
  2. How should I decide which type of controller I should buy? It should support PC, console-support is not essential.

Note: I am a novice in game controllers but aware of different network stacks.

Edit: Thanks for the amazing response! These are my key takeaways from all the comments

  1. Hall-effect sensors are a must
  2. Default console controllers usually have stick drift
  3. If you need trackpad, take PS5
  4. 8bitdo is a reliable brand, as per multiple responses
  5. Most controllers have good support on Linux. But haptic feedback can be a hit/miss as it can be platform/game dependent
  6. There are various connectivity wireless standards. Dongles are the most reliable but you lose a USB port.
  7. Keep track of handsize/comfort and button layout
  8. PS controllers have excellent support on Linux/Steam
 

This is a post I wish I never had to make. Forgive my grammar and spelling as I am a bit emotional.

My Steam Deck was stolen and I just had it for less than 2 months.

It has been more than 2 weeks since it happened but it still hurts the same. I wanted to make this post because it was a very costly mistake from my side and I don't want it to happen to anyone else.

<story>

It happened when I was shifting from one house to another house and there were lots of maintenance workers at the destination house. After I kept my luggage inside the house, I left to buy some essentials. My mom was the only person left who was watching over the stuff. By the time I came back, the workers had left. I thought I have some free time so decided to pull the Steam Deck out but it was missing.

<vent>

I was absolutely devastated; I can't even begin to explain in words what it felt like. I asked, through the person who hired the workers, if they took it. But all the workers refused. I was just crushed; I could feel my heart dropping into my stomach. Even now, as I am typing this story, that emotion is replaying.

</vent>

After this happened, I removed all payment methods from my Steam account (Steam Guard 2FA was already active). I saw after 5 days that the Steam Deck was online for a brief period of time, via Steam Guard. I purposefully didn't sign out of the device because I wanted the thieves to make the mistake of signing in and giving me some clue about their location; the Steam Deck was still inside my city. I took the IPs and submitted it to the police and asked them if they could track it. They said they will try their best since getting the customer details from an IP is a "lengthy and time-consuming process". But at this point, I can't do anything; it's not possible for me to visit all the worker's home individually and check as I don't have the authority. I gave up and convinced myself to move on.

</story>

This taught me a lot of things and I wanted to share with the community, now that I have slightly recovered mentally.

Secure your luggage when moving

When you are moving, you usually have a million thoughts in your head. This can cause you to neglect your luggage's safety. If you are going to unload your luggage temporarily, KEEP IT IN A SECURE MANNER FIRST and then do everything else.

A secure manner could mean

  • Under someone's watch
  • Putting it far away from the exit
  • Putting a lock on the luggage
  • Putting it inside a cabinet and locking it

Don't just unload the luggage and start doing something mentally involving.

Be wary of outsiders

Sometimes, there will be outside people in your home. It's crucial to keep the Steam Deck out of reach of everyone. Not everyone is a thief but different people have different moral standards. Don't create a tempting scenario for others. Keep it secure when there are guests/workers at your place.

Put some form of tracking on the device

The Steam Deck is like a traditional laptop; it has no SIM or GPS. Once it's lost, it's really hard to get it back. There are methods by which you can track the Steam Deck (Steam Guard) but it involves IP and it's not enough to get an exact location. Other than law-enforcement, no one can find the customer details associated with an IP address.

An alternate approach, which can be slight pricey, is to put a Tile tracker on the device. There are tutorials on how it can be attached to the device.

Note: I'm not associated with Tile in any way.

Get the official Serial Number and MAC ID of the device

It will help you to uniquely identify the device IF it gets stolen. You may find the serial number on

  • The bill of purchase
  • Inside the Steam Deck settings section
  • On the Steam Deck package
  • You can ask Steam support for the serial number once it's associated with your account The MAC ID is present on the Steam Deck settings page (and also on your access point logs if it has connected even once).

I hope this post is educational and makes you wary of the physical dangers around us. Please keep your handhelds or any valuables safe

<vent>

What hurts even more is that the Steam Deck, which was the 1 TB OLED model, was a gift from a very special person and I feel like I have betrayed that person by losing it. I had lots of plans with the device, like making a couch plug-and-play setup, a retro gaming setup, a productivity device by using desktop mode, etc. But all my plans were shattered in an instance. I'm now convincing myself to move on to something else.

</vent>

Edit: As of 20th August, I can see via Steam Guard that the device was logged into a few hours ago (2 weeks post the burglary). I know the risks involved in keeping my device signed in. I'm counting on the person's stupidity. Any proper thief would have formatted the device.

view more: next ›