Reopen BAT directory #44

Closed
opened 8 months ago by JorwLNKwpH · 3 comments

After charging the battery, the battery module gets "stuck" at 100%.

Yambar error:

err: modules/battery.c:294: /sys/class/power_supply/BAT0: No such file or directory

After charging the battery, the battery module gets "stuck" at 100%. Yambar error: `err: modules/battery.c:294: /sys/class/power_supply/BAT0: No such file or directory`
Owner

The directory is already re-opened each time we update the status. Meaning, your battery driver is probably removing it (possibly re-creating it later).

When you see the error message next time, can you check the contents of the /sys/class/power_supply directory?

If there is a BAT0 directory there, yambar would have to be updated re-try for a while, before giving up and erroring out.

The directory is already re-opened each time we update the status. Meaning, your battery driver is probably removing it (possibly re-creating it later). When you see the error message next time, can you check the contents of the `/sys/class/power_supply` directory? If there **is** a `BAT0` directory there, yambar would have to be updated re-try for a while, before giving up and erroring out.
dnkl added the
bug
label 8 months ago
Poster

If there is a BAT0 directory there, yambar would have to be updated re-try for a while, before giving up and erroring out.

Yes, I see the BAT0 directory after the error message. I don't know how long the delay between destroying and re-creating the directory is.

>If there is a BAT0 directory there, yambar would have to be updated re-try for a while, before giving up and erroring out. Yes, I see the `BAT0` directory after the error message. I don't know how long the delay between destroying and re-creating the directory is.
Owner

Hmm, ok. Fun stuff... :/

Let me ponder this a bit. We'll obviously have to retry, for some amount of time. Most likely, that delay between destroying and re-creating the directory, is short (in "human" time); so maybe retry once every second for 5-10s is good enough.

Hmm, ok. Fun stuff... :/ Let me ponder this a bit. We'll obviously have to retry, for some amount of time. Most likely, that delay between destroying and re-creating the directory, is short (in "human" time); so maybe retry once every second for 5-10s is good enough.
dnkl closed this issue 6 months ago
dnkl referenced this issue from a commit 6 months ago
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.