fhein

joined 2 years ago
[–] fhein@lemmy.world 2 points 1 day ago

It was surprisingly difficult to find, the majority of comments about 6.3 were people saying it was working great, but I guess most people don't use ICC profiles for their monitors.

 

Just posting this since I spent over an hour trying to figure out why I couldn't open my desktop today.. After booting and logging in I got a black screen. Switched to a terminal but did not see any obvious errors in the logs.

Not fixed for Fedora 41 KDE yet, so I installed plasma-workspace-x11 to use in the meanwhile. Anyone who hasn't updated to 6.3 yet could probably change their display settings to not use ICC profiles to avoid it.

[–] fhein@lemmy.world 9 points 1 week ago (1 children)

Intel NUC running Linux. Not the cheapest solution but can play anything and I have full control over it. At first I tried to find some kind of programmable remote but now we have a wireless keyboard with built-in touchpad.

Biggest downside is that the hardware quality is kind of questionable and the first two broke after 3 years + a few months, so we're on our third now.

[–] fhein@lemmy.world 6 points 3 weeks ago

This is my wireguard docker setup:

version: "3.6"
services:
  wireguard:
    image: linuxserver/wireguard
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=116
      - PGID=122
      - TZ=Europe/Stockholm
      - ALLOWEDIPS=192.168.1.0/24
    volumes:
      - /data/torrent/wireguard/config:/config
      - /lib/modules:/lib/modules
    ports:
      - 192.168.1.111:8122:8122  # Deluge webui
      - 192.168.1.111:9127:9127  # jackett webui
      - 192.168.1.111:9666:9666  # prowlarr webui
      - 51820:51820/udp           # wireguard
      - 192.168.1.111:58426:58426  # Deluge RPC
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
      - net.ipv6.conf.all.disable_ipv6=1
      - net.ipv6.conf.default.disable_ipv6=1
    restart: unless-stopped

Can reach the webuis from LAN, no other network configuration was necessary. 192.168.1.111 is the server's LAN address. The other services are configured very similar to your qbittorrent, and don't expose any ports. Can't promise it's 100% correct but it's working for me.

[–] fhein@lemmy.world 1 points 1 month ago

As long as they are talking about normal things and not playing D&D 😃

[–] fhein@lemmy.world 16 points 2 months ago

My paranoia level: Even though I'm pretty good with computers in general, I would not trust myself to set up a safe public facing service, which is the reason that I don't have any of those on my home server. If I needed something like that I wouldn't self host it.

[–] fhein@lemmy.world 3 points 2 months ago

The question is probably more related to what he has done rather than what he is doing right now, and he is kind of famous for having created Linux in the past. To someone who doesn't know anything about Linux licenses I think it would be easy to suspect that Torvalds might have some kind of ownership of his creation.

[–] fhein@lemmy.world 1 points 2 months ago

If you're using Pipewire, have you checked if you can re-route the audio sink using qpwgraph?

[–] fhein@lemmy.world 13 points 3 months ago (2 children)

I was expecting more entries on a certain theme for version 420 ;)

[–] fhein@lemmy.world 5 points 3 months ago

Apex with EAC worked perfectly fine on Linux for the last 2 years, EA just decided to break it by replacing EAC with their own anti-cheat which is Windows only.

[–] fhein@lemmy.world 1 points 3 months ago

Add "site:reddit.com" to your google query.

[–] fhein@lemmy.world 7 points 3 months ago (2 children)

Sad thing is that search engines have got so bad, and usually return so much garbage blog spam that searching directly on reddit is more likely to give useful results. I hope a similar amount of knowledge will build up on Lemmy over time.

[–] fhein@lemmy.world 1 points 3 months ago

We just had Windows Update brick itself due to a faulty update. The fix required updating them manually while connected to the office network, making them unusable for 2-3 hours. Another issue we've had is that Windows appears to be monopolizing virtualization HW acceleration for some memory integrity protection, which made our VMs slow and laggy. Fixing it required a combination of shell commands, settings changes and IT support remotely changing some permission, but the issue also comes back after some updates.

Though I've also had quite a lot of Windows problems at home, when I was still using it regularly. Not saying Linux usage has been problem free, but there I can at least fix things. Windows has a tendency to give unusable error messages and make troubleshooting difficult, and even when you figure out what's wrong you're at the mercy of Microsoft if you are allowed to change things on your own computer, due to their operating system's proprietary nature.

 

I have calibrated my monitors to create icc profiles, they show up in KDE color management and everything used to work exactly as it should. Now every time I start my computer it goes like this:

  1. I log in to my account
  2. It shows my desktop, with the right colour correction.
  3. After a few seconds the colours revert to look un-calibrated on both monitors.
  4. I restart the colord service and it loads the colour correction again.

As an alternative to step 4, if I go to KDE colour settings, select the default profile and then back to my profile then it also starts looking good again.

This problem must've started a week or two ago, but unfortunately I haven't been able to pinpoint exactly when. I haven't touched anything related to colour management in months, and don't think I've done any changes to my system other than upgrading packages.

Can't see anything colour related in the syslog except colord loading the correct profiles. I removed all the old profiles that I wasn't using anyway. I removed dispcal's profile loader from autostart to make sure it wasn't interfering with something. The profiles are both installed system wide and in my user folder.

Using Fedora 39 KDE.

Anyone have any idea what could be wrong, or even how to debug this?

view more: next ›