mobsenpai

cross-posted from: https://lemmy.world/post/25786274

cross-posted from: https://lemmy.world/post/25786273

cross-posted from: https://lemmy.world/post/25765733

general {
  after_sleep_cmd=hyprctl dispatch dpms on
  before_sleep_cmd=loginctl lock-session
  lock_cmd=hyprlock
}

listener {
  on-timeout=loginctl lock-session
  timeout=300
}

listener {
  on-resume=hyprctl dispatch dpms on
  on-timeout=hyprctl dispatch dpms off
  timeout=330
}

listener {
  on-timeout=systemctl suspend
  timeout=600
}

Guys I feel like there's something wrong or odd in this config, cuz, I don't know whats responsible for this but, it looks like things aren't working well together, I said it looks like cuz I never caugth an actual error. So what happens is that after I leave my laptop idle, the hypridle starts doing its thing and most of the times it works, my laptop is suspended, hyprlock works etc, but sometimes, after I press any button on my keyboard to wake my laptop, I can see that my laptop is up, but all I can see is black screen, and then I have to hard shutdown the laptop, so somethings is not adding up here.

cross-posted from: https://lemmy.world/post/25786273

cross-posted from: https://lemmy.world/post/25765733

general {
  after_sleep_cmd=hyprctl dispatch dpms on
  before_sleep_cmd=loginctl lock-session
  lock_cmd=hyprlock
}

listener {
  on-timeout=loginctl lock-session
  timeout=300
}

listener {
  on-resume=hyprctl dispatch dpms on
  on-timeout=hyprctl dispatch dpms off
  timeout=330
}

listener {
  on-timeout=systemctl suspend
  timeout=600
}

Guys I feel like there's something wrong or odd in this config, cuz, I don't know whats responsible for this but, it looks like things aren't working well together, I said it looks like cuz I never caugth an actual error. So what happens is that after I leave my laptop idle, the hypridle starts doing its thing and most of the times it works, my laptop is suspended, hyprlock works etc, but sometimes, after I press any button on my keyboard to wake my laptop, I can see that my laptop is up, but all I can see is black screen, and then I have to hard shutdown the laptop, so somethings is not adding up here.

cross-posted from: https://lemmy.world/post/25765733

general {
  after_sleep_cmd=hyprctl dispatch dpms on
  before_sleep_cmd=loginctl lock-session
  lock_cmd=hyprlock
}

listener {
  on-timeout=loginctl lock-session
  timeout=300
}

listener {
  on-resume=hyprctl dispatch dpms on
  on-timeout=hyprctl dispatch dpms off
  timeout=330
}

listener {
  on-timeout=systemctl suspend
  timeout=600
}

Guys I feel like there's something wrong or odd in this config, cuz, I don't know whats responsible for this but, it looks like things aren't working well together, I said it looks like cuz I never caugth an actual error. So what happens is that after I leave my laptop idle, the hypridle starts doing its thing and most of the times it works, my laptop is suspended, hyprlock works etc, but sometimes, after I press any button on my keyboard to wake my laptop, I can see that my laptop is up, but all I can see is black screen, and then I have to hard shutdown the laptop, so somethings is not adding up here.

general {
  after_sleep_cmd=hyprctl dispatch dpms on
  before_sleep_cmd=loginctl lock-session
  lock_cmd=hyprlock
}

listener {
  on-timeout=loginctl lock-session
  timeout=300
}

listener {
  on-resume=hyprctl dispatch dpms on
  on-timeout=hyprctl dispatch dpms off
  timeout=330
}

listener {
  on-timeout=systemctl suspend
  timeout=600
}

Guys I feel like there's something wrong or odd in this config, cuz, I don't know whats responsible for this but, it looks like things aren't working well together, I said it looks like cuz I never caugth an actual error. So what happens is that after I leave my laptop idle, the hypridle starts doing its thing and most of the times it works, my laptop is suspended, hyprlock works etc, but sometimes, after I press any button on my keyboard to wake my laptop, I can see that my laptop is up, but all I can see is black screen, and then I have to hard shutdown the laptop, so somethings is not adding up here.

cross-posted from: https://lemmy.world/post/21426498

I use nixos + greetd + tuigreet + hyprland. I missed to mention that I wanted to disable or hide the logs that gets shows when starting hyprland from tty terminal by writing Hyprland or when using greetd tuigreet. After entering my username and password, These logs show before hyprland starts, I want to avoid that

I use nixos + greetd + tuigreet + hyprland.

Edit: Solved, check the comments

cross-posted from: https://lemmy.world/post/21359091

Using this works:

    services.greetd = {
      enable = true;
      settings = {
        initial_session = {
          command = "Hyprland";
          user = "yashraj";
        };
        default_session = {
          command = "${lib.getExe pkgs.greetd.tuigreet} --time --cmd Hyprland";
          user = "yashraj";
        };
      };
    };

But using this doesn't:

    services.greetd = {
      enable = true;
      settings = {
        default_session = {
          user = "yashraj";
          command = "${pkgs.greetd.tuigreet}/bin/tuigreet --time --sessions ${pkgs.hyprland}/share/wayland-session --remember --remember-session";
        };
      };
    };

I wan't to be able to use --sessions. what could I be doing wrong? I am using latest nixos stable.

The only error returned here is after I enter my username 'yashraj' then my password 'nixos' is: expected Args or Cancel, got Pamresponse {resp: some("nixos")}

Notes:

I haven't commited the greetd file to my github yet. But I've still attached the link to my github if it may be relevant to solve this issue.

Please give any info

Using this works:

    services.greetd = {
      enable = true;
      settings = {
        initial_session = {
          command = "Hyprland";
          user = "yashraj";
        };
        default_session = {
          command = "${lib.getExe pkgs.greetd.tuigreet} --time --cmd Hyprland";
          user = "yashraj";
        };
      };
    };

But using this doesn't:

    services.greetd = {
      enable = true;
      settings = {
        default_session = {
          user = "yashraj";
          command = "${pkgs.greetd.tuigreet}/bin/tuigreet --time --sessions ${pkgs.hyprland}/share/wayland-session --remember --remember-session";
        };
      };
    };

I wan't to be able to use --sessions. what could I be doing wrong? I am using latest nixos stable.

The only error returned here is after I enter my username 'yashraj' then my password 'nixos' is: expected Args or Cancel, got Pamresponse {resp: some("nixos")}

Notes:

I haven't commited the greetd file to my github yet. But I've still attached the link to my github if it may be relevant to solve this issue.

Please give any info

I always use all:unset in my css files and I did the same when configuring the swaync notification but somehow when using it inside global selector *{} it doesn't show the volumeslider which is shows in a notification, related pictures will be attached. I wanna use all:unset and so I want to know how to re-enable volumeslider without removing all:unset. I've found this config to also use it but its in scss so I didn't test it.

with all:unset

without all:unset

Full style.css ->

* {
  all: unset;
  font-family: "FiraMono Nerd Font";
  font-size: 10pt;
  font-weight: normal;
}

.notification {
  background: #3c3836;
  border: 1px solid #504945;
  border-radius: 8px;
  padding: 7px;
}

.notification-content {
  background: #3c3836;
  color: #ebdbb2;
}

.notification-row {
  margin: 2px;
}

.close-button {
  background: #cc241d;
  border-radius: 50%;
  color: #282828;
}

.close-button:hover {
  background: #fb4934;
  transition: all 0.15s ease-in-out;
}

.time {
  color: #98971a;
  font-size: 9pt;
  margin-right: 24px;
}

.control-center {
  background: #3c3836;
  border: 1px solid #504945;
  border-radius: 8px;
  padding: 8px;
}

.control-center-list-placeholder {
  background: #3c3836;
  color: #7c6f64;
}

.widget-title {
  background: #3c3836;
  color: #ebdbb2;
}

.widget-title > button {
  background: #98971a;
  color: #282828;
  border-radius: 4px;
  padding: 2px;
}

.widget-title > button:hover {
  background: #b8bb26;
  color: #282828;
  transition: all 0.15s ease-in-out;
}

.widget-dnd {
  background: #3c3836;
  color: #ebdbb2;
}

.widget-dnd > switch {
  background: #665c54;
  border-radius: 4px;
}

.widget-dnd > switch:checked {
  background: #d65d0e;
}

.widget-dnd > switch slider {
  background: #282828;
  border-radius: 4px;
}

Edit: ended up removing the submenu functionality by adding no_actions=true in wofi's config.

My style.css ->

* {
  all: unset;
  font-family: "FiraMono Nerd Font";
  font-size: 10pt;
  font-weight: normal;
}

#window {
  background: #3c3836;
  border-radius: 8px;
  border: 1px solid #504945;
}

#input {
  background: #3c3836;
  border-bottom: 1px solid #504945;
  color: #ebdbb2;
  margin-bottom: 4px;
  padding: 4px;
}

#input > image.left {
  margin-right: 4px;
}

#input > image.right {
  margin-left: 4px;
}

#outer-box {
  padding: 4px;
}

#text {
  color: #ebdbb2;
}

#entry {
  border-radius: 4px;
  padding: 4px;
}

#entry:selected {
  background: #504945;
}

Are there any classes or a config option to set the icon to whatever I want?

Yes I know that there are workarounds for them to set to use the flake inputs but still.. I have set nixpkgs version to 23.11 stable release and that's good, but if I try to use nix shell, nix profile or even nix-env, they all seem to use the latest master/unstable branch to install the packages by default.

Just want to know why aren't they just default to use whatever is defined in flake.nix file? will it be implemented to use it by default in the near future?

Reason as to why I am asking -> This is what I am using to match nix shell and flake inputs, but as you can see they are just workarounds, plus seem to cause more errors and whatnot, plus by ideology one shouldn't need to specially define it to use some version when everything is already defined.

See I use wofi-emoji but this issue #308357 is haunting me. So I just wanted to know what my fellow users use cuz I guess not a lot of people use wofi-emoji.