mirror of
https://github.com/JakeStanger/ironbar.git
synced 2026-07-11 12:15:22 +01:00
[GH-ISSUE #594] OS error 2 #3003
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#3003
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 @madfanat on GitHub (May 18, 2024).
Original GitHub issue: https://github.com/JakeStanger/ironbar/issues/594
Describe the bug
Today I installed all available updates and then restarted my computer. Everything works fine, but ironbar won't start. Here is the output I am getting::
To Reproduce
Steps to reproduce the behavior:
1.Type
paru -Syu2. Restart a computer
3. See error
System information:
Configuration
Config
Styles
@JakeStanger commented on GitHub (May 18, 2024):
Do you always see that
dbind-WARNINGmessage, or do you know if that's new? The crash is coming from the tray client initialization code, which is dbus related, as is that warning.It looks like this may be due to a dbus-related system issue, but hard to tell.
Are you able to re-run with
IRONBAR_LOG=trace RUST_BACKTRACE=fulltoo please, and share the log (it will probably be a lot bigger)? Hopefully this should give a few more clues as to what's going on.@madfanat commented on GitHub (May 18, 2024):
Yep, here is the output
@madfanat commented on GitHub (May 18, 2024):
Well, I would bet the
dbind-WARNINGmessage is new.@madfanat commented on GitHub (May 18, 2024):
By the way, I guess this warning isn't actually a problem. It just tells you that Gnome Accessibility tool can't be found.
Fixed by running with NO_AT_BRIDGE=1 flag. But ironbar still won't run and then I think the issue isn't related to dbus.
@madfanat commented on GitHub (May 18, 2024):
Ohhh, found some kind of workaround. Now I'm able to run ironbar via dbus-launch. But still getting some errors related to swaync, will try to figure out the reason. Here is the short general output:
And here is what I get if click on the notifications button:
@JakeStanger commented on GitHub (May 18, 2024):
Is swaync running? It will need to be for the module to work. If it is, there's definitely a dbus issue your machine.
Running with
dbus-launchalso should not be required.It could potentially be a similar issue/solution to this, but I'm not sure.
@madfanat commented on GitHub (May 18, 2024):
Thank you.
It's so stupid and cringe. The error occurred because of sddm: it rewrited the hyprland entry and removed the
dbus-run-sessionprefix. Now it's finally fixed.@JakeStanger commented on GitHub (May 18, 2024):
Glad to hear it's sorted