mirror of
https://github.com/JakeStanger/ironbar.git
synced 2026-07-11 08:15:21 +01:00
[GH-ISSUE #488] The Focused module is not always display the currently focused window #1565
Labels
No labels
A:Build
A:CI
A:Client
A:Config
A:Core
A:Documentation
A:Documentation
A:IPC
A:Testing
A:UX/UI
blocked
BREAKING CHANGE
duplicate
good first issue
GTK4
help wanted
invalid
M:Battery
M:Battery
M:Bindmode
M:Bluetooth
M:Brightness
M:Cairo
M:Clipboard
M:Clock
M:Clock
M:Custom
M:Focused
M:Keyboard
M:Launcher
M:Menu
M:Music
M:Music
M:Music
M:Network Manager
M:Notifications
M:SysInfo
M:Tray
M:Volume
M:Workspaces
partially resolved
P:Critical
P:High
P:Low
P:Medium
pull-request
T:Bug
T:Bug
T:Core Enhancement
T:Module Enhancement
T:New Module
T:Question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
JakeStanger/ironbar#1565
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @bluebyt on GitHub (Mar 10, 2024).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/488
Describe the bug
The Focused module is not always display the currently focused window, sometime the module is blank even if the window is focused
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Focused on the windows all the time
System information:
In the video you can see that I try Wayfire, Hyprland and at the end I compared the Window focus module with Waybar.
https://streamable.com/7xzbwu
Configuration
Config
Styles
@JakeStanger commented on GitHub (Mar 10, 2024):
Thanks for the video, this seems like strange behaviour.
Could you reproduce this please with
IRONBAR_LOG=debugset and send the log file? Hopefully only a single example of focusing a window and it not working, then ie changing the tab to fix it should be enough.@bluebyt commented on GitHub (Mar 10, 2024):
Where I put this line IRONBAR_LOG=debug ?
@JakeStanger commented on GitHub (Mar 10, 2024):
That's an environment variable. You can for example start Ironbar with
@bluebyt commented on GitHub (Mar 10, 2024):
I start ironbar with IRONBAR_LOG=debug ironbar and now that working as expected! and then I though the problem come from that the way I started ironbar.
Until now I start ironbar from the terminal "$ironbar &" because when I tried to put it in wayfire.ini it does't started.
wayfire.ini
[autostart]
bar = ironbar
I will still investigating the issue.
It seem that every time I think I find a bug that is either my system of something I am doing wrong lol!
@bluebyt commented on GitHub (Mar 11, 2024):
It seem to happens less frequently. Here the log file.
Log file
@bluebyt commented on GitHub (Mar 11, 2024):
Sometime when I started Ironbar, I see this message of a crash and the focused module doesn't work, I don't know if it's related to this issue.
I have update the log file, but I dont see any message related to the focused module.
Log file
Also I have installed a VM with wayfire, ironbar, because I want to check if the problem is specific to my system,
2024-03-11T22:37:49.046744Z INFO ironbar: 111: Ironbar version 0.15.0-pre
2024-03-11T22:37:49.046764Z INFO ironbar: 112: Starting application
2024-03-11T22:37:49.048504Z ERROR ironbar::logging: 48: The application panicked (crashed).
Message: Failed to send message to channel: "Full(..)"
Location: src/clients/wayland/wlr_foreign_toplevel/mod.rs:82
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
2024-03-11T22:37:49.152512Z WARN ironbar::ipc::server: 31: Socket already exists. Did Ironbar exit abruptly?
2024-03-11T22:37:49.152538Z WARN ironbar::ipc::server: 32: Attempting IPC shutdown to allow binding to address
2024-03-11T22:37:49.152597Z INFO ironbar::ipc::server: 37: Starting IPC on /run/user/1000/ironbar-ipc.sock
2024-03-11T22:37:49.154372Z INFO ironbar::bar: 120: Initializing bar 'bar-24' on 'HDMI-A-1'
2024-03-11T22:37:49.159070Z ERROR ironbar::logging: 48: The application panicked (crashed).
Message: Failed to send message to channel: SendError { .. }
Location: src/clients/wayland/mod.rs:176
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
2024-03-11T22:37:49.161194Z INFO connect: mpd_protocol::connection: 306: connected successfully version="0.23.5"
2024-03-11T22:37:49.162266Z INFO mpd_utils::persistent_client: 65: Connected to 'localhost:6600'
@JakeStanger commented on GitHub (Mar 11, 2024):
You're right, there's nothing related to the focused module in the log. What's interesting though is this:
Immediately on startup the foreign-toplevel client (which is what listens to application windows, ie required for focused/launcher) crashes trying to send an event. This would mean for some reason the Wayland client stops receiving events, which is a fairly fundamental issue. I'm not sure what would cause that.
Are you compiling Ironbar yourself using a feature set other than the default? Anything out of the normal at all? Do you get this error on sway/hyprland, or is it just Wayfire? I'm wondering if Wayfire has a bugged protocol impl.
@bluebyt commented on GitHub (Mar 12, 2024):
I compiled with the instruction on the front page:
cargo build --release
Hyprland is broken on my system, I will try it later.
@bluebyt commented on GitHub (Mar 14, 2024):
The crash doesn't seem to happen after reboot, but I have a lot of problem both with Hyprland and Wayfire.
The video is self-explanatory, even when I have a focused window, the module become blank.
Focused module
If you need more detail let me know.
@JakeStanger commented on GitHub (Mar 14, 2024):
Is that video on Hyprland? Could you send your
hyprland.confplease? Seems unlikely it could be anything there given Wayfire had the same issue, but it could be I guess.@bluebyt commented on GitHub (Mar 14, 2024):
Yes this is Hyprland. I can record another video with wayfire, the focused become blank, but the behavior is little bit different.
hyprland.conf
@bluebyt commented on GitHub (Mar 15, 2024):
Hi, Are you able to replicate the issue?
@JakeStanger commented on GitHub (Mar 17, 2024):
I have just given this a go with your ironbar/hyprland config and I am still not able to replicate the issue. For me the
focusedmodule works without fault.I can't see any reason for it to not work for you. If the error in the first log no longer occurs, it should work, but with that error it should stop working entirely anyway, rather than partially as you're seeing.
Is your hardware particular weird/old? Are you running a particularly old version of Hyprland/Wayfire?
@bluebyt commented on GitHub (Mar 17, 2024):
Then I guess the problem is my system. Hyrland/Wayfire are up to date and my Hardware 2 years old only, nothing special.
@JakeStanger commented on GitHub (Mar 17, 2024):
I'll keep this open for now in case you find anything new, or in case anybody else hits the same issue, but for now I'm all out of ideas so I'm not sure I can do much I'm afraid. It does sound like you've got quite a few system issues - might be worth a refresh and seeing it that helps in general.
@JakeStanger commented on GitHub (Apr 17, 2024):
Hey @bluebyt did you manage to get anywhere with this, or is this still an issue?
@bluebyt commented on GitHub (Apr 17, 2024):
@JakeStanger I reinstated from scratch my system Arch, Gnome, Wayfire and Hyprland, but still the same issue.
If you want me to try something feel free to ask, I have no clue why the Window module become blank after one or 2 min. even though a Window is still focused.
@JakeStanger commented on GitHub (Apr 24, 2024):
Sorry for the delay on this one. #544 duplicates this issue & I was able to track this down to unfocused window title changes based on the repro info there (you'll spot this coincides with your music changing track). Should finally have a fix in place shortly!
@bluebyt commented on GitHub (Apr 24, 2024):
Thank you, I'm going to try that!