Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hyprland freezes after pressing e.g. Ctrl+Alt+F1 twice to switch to tty1 #4850

Closed
exit91 opened this issue Feb 26, 2024 · 6 comments
Closed
Labels
bug Something isn't working stale Not much going on

Comments

@exit91
Copy link

exit91 commented Feb 26, 2024

Hyprland Version

System/Version info

OS: NixOS 23.11.20240225.5bf1cad (Tapir) x86_64
Kernel: 6.6.1-zen1
Hyprland version: v0.32.3

Hyprland, built from branch  at commit v0.32.3  ().
Tag: 

flags: (if any)
debug

GPU (/dev/dri/card0): 03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6600/6600 XT/6600M] (rev c1)
GPU (/dev/dri/card1): 11:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael (rev c6)

Bug or Regression?

Bug

Description

Pressing Ctrl+Alt+F${N} twice freezes the screen (if Hyprland happens to run on tty${N})

How to reproduce

Suppose Hyprland runs on TTY1 (other TTY work too).

  1. Press Ctrl+Alt+F1 (this can happen by accident when the intention is to switch to another Hyprland session, say on TTY2)
  2. Screen freezes
    • Screen freezes
    • Sound still plays if it did before (using pipewire)
    • Mouse inputs are still recognized (I can stop a Youtube video by click)
    • Keyboard inputs work (I can stop a Youtube video by space bar)
    • Ctrl+Alt+F2 doesn't send me to TTY2

Note: Running sudo chvt 1 twice doesnt reproduce this behaviour.

Crash reports, logs, images, videos

====== At this moment I press Ctrl+Alt+F1 twice =====
[2024-02-26 23:16:56.322] [warning] [wireplumber]: '4294967295' is not a valid node ID. Ignoring node change.
[2024-02-26 23:16:56.322] [warning] [wireplumber]: '4294967295' is not a valid node ID. Ignoring node change.
[2024-02-26 23:17:02.503] [warning] [wireplumber]: (onMixerChanged) - Object with id 63 not found
[2024-02-26 23:17:02.514] [warning] [wireplumber]: (onMixerChanged) - Object with id 63 not found
[2024-02-26 23:17:02.514] [warning] [wireplumber]: '4294967295' is not a valid node ID. Ignoring node change.
[2024-02-26 23:17:02.514] [warning] [wireplumber]: '4294967295' is not a valid node ID. Ignoring node change.
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Unsupported maximum keycode 708, clipping.
>                   X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
====== After switching back to TTY1 by executing `sudo chvt 2` via ssh, then pressing `Ctrl+Alt+F1` =====
@exit91 exit91 added the bug Something isn't working label Feb 26, 2024
@vaxerski
Copy link
Member

please use the search feature. Dupe of #4839

@vaxerski vaxerski closed this as not planned Won't fix, can't repro, duplicate, stale Feb 26, 2024
@exit91
Copy link
Author

exit91 commented Feb 26, 2024

It's not the same behaviour.

Edit: In fact I cannot reproduce the bug you linked.
Edit2: Although the other issue sounds close enough, that there might be a chance its fix will fix this issue too 😅

@vaxerski
Copy link
Member

wdym its not the same

@exit91
Copy link
Author

exit91 commented Feb 26, 2024

The steps to reproduce #4839 are:

Start Hyprland on tty2 then switch to say tty1 and back and it freezes.

This doesn't happen on my system. Instead Hyprland freezes if I switch from tty2 to tty2 itself (via ctrl+alt+f2).

@vaxerski
Copy link
Member

ah

@vaxerski vaxerski reopened this Feb 26, 2024
@vaxerski vaxerski added the stale Not much going on label Apr 27, 2024
@exit91
Copy link
Author

exit91 commented Feb 20, 2025

No longer reproducable for a while tbh, but at least since

Hyprland 0.47.0 built from branch  at commit d01f9943e1d401b09fc53be3c161279ab4f2c5ba  ().
Date: 2025-02-17
Tag: v0.47.0, commits:
built against:
 aquamarine 0.7.2
 hyprlang 0.6.0
 hyprutils 0.5.0
 hyprcursor 0.1.11
 hyprgraphics 0.1.2

@exit91 exit91 closed this as completed Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Not much going on
Projects
None yet
Development

No branches or pull requests

2 participants