Status bar hiccup with error on startup about voidrice

[yurisuki]

yeah, I had this one. try disabling mpd block, and then in the config disable mpd refresh. I know, you may miss this, but if you really want this work normally, then disable this.

[yurisuki]

I also don't have any idea what part of the code is causing this, but I assume that refresh script does it.

[LukeSmithxyz]

Are you saying you think the problem is i3mpd or i3mpdupdate? Why would this be at fault rather than anything else? Curious what you're thinking.

[yurisuki]

as it turns out i3mpdupdate is causing that and also it's taking more performance.

[LukeSmithxyz]

Okay, but what are you saying causes it? Frankly if you look at the error messages when that problem occurs, it's the [record] script that has an error code, so my reflex would be that that's the problem.

[yurisuki]

Sorry, but I didn't have the problem with that, I had the problem with i3mpdupdate, also I didn't notice that.

[yurisuki]

Simply; when I checked out the i3mpdupdate in the i3 config my problem was fixed.

[TylerJaacks]

@exploxd So what did u do exactly, I'm confused?

[yurisuki]

So what did u do exactly, I'm confused?

removed i3mpdupdate from i3 config.

[LukeSmithxyz]

I seriously doubt that i3mpdupdate is causing this problem. Especially considering the line in the i3 config has nothing to do with the bar. If you disabled the script and didn't get the error that doesn't really mean anything since the error message is infrequent regardless.

Aside from that i3mpdupdate is a necessary component of the system, so it's not possible to just "remove it".

Either way, I've added a minor change that will change any particular i3mpdupdate error from taking place in i3 to taking place in a subshell. Again, the likely problem is the record module since that's the module that has the error message.

[LukeSmithxyz]

Someone can feel free to say so if they still have problems, but some i3blocks change made within the past month or so seems to have eliminated this problem. I'm going to close this issue.