• 32 Posts
  • 38 Comments
Joined 10 months ago
cake
Cake day: March 25th, 2025

help-circle















  • I have the hyprland portals installed, and the kde ones, due to some issue I had to explicitly install them so idk if that will mess with the way applications handle it, assuming not, and yes I have two gpus, one dgpu, and one igpu, the dgpu is directly connected to my hdmi, does OBS stuggle with 2 gpus? still, that sounds like it would be a issue with capturing the monitor managed by my igpu. Not a reason to stop a second pipewire capture.

    What logs do you need? I provided some from running OBS but i assume it isnt enough, what logs should I collect, or is there a flag i need to run with OBS





















  • Weird thing is, is that. I only had one mscp in my app state, it was behind a arc mutex and code that accessed it was running asynchronously, but, somehow they all got the same messages for a bit, then like, stopped or got very partial messages except the intended recipient (they got the full message). Is this some memory issue, or race condition?

    I don’t have this issue switching to broadcast but I’m confused




  • Nevermind, fixed, this is what I tried applying, or maybe i should have waited for a bit and it might of worked, regardless, just incase its useful to anyone:

    apiVersion: v1
    kind: ConfigMap
    metadata:
      name: coredns
      namespace: kube-system
    data:
      Corefile: |
        .:53 {
            errors
            health
            ready
            kubernetes cluster.local in-addr.arpa ip6.arpa {
                pods insecure
                fallthrough in-addr.arpa ip6.arpa
            }
            hosts /etc/coredns/NodeHosts {
                ttl 60
                reload 15s
                fallthrough
            }
            prometheus :9153
            forward . 1.1.1.1 1.0.0.1 8.8.8.8 8.8.4.4
            cache 30
            loop
            reload
            loadbalance
        }
    
    

    The issue is solved now, thanks