i3-nagbar: Message text doesn't seem to wrap

[kbhasi]

I'm submitting a…

[x] Bug
[ ] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

I simulated an error message for a project I'm working on (where I plan to recommend i3 for the WM, and provide a custom configuration to use with it), and found that the text gets cut off, and/or hidden behind buttons.

Ignore the red error text in i3bar, as I'll be using a different status bar provider later on.

Expected Behavior

The text should be soft wrapped, so that the full message is visible, and not cut off nor hidden behind buttons.

Reproduction Instructions

1. The resolution I set my Xephyr window in the screenshots to, is 1404x1872 at 192 dpi. However, I have observed this bug on Xephyr screens with 600 pixels or lower horizontal resolution at 96 dpi.
2. Just bring up a terminal window and run an i3-nagbar command with a long amount of text.
   • Here's the command I used in the first screenshot:

i3-nagbar -t error -m "Project Barry startup failed for the following reason: Unable to find Calibre in directories indicated in your PATH variable." -f "pango:Liberation Serif 10" -B "Restart i3" "i3-msg restart"

Environment

I'm using the version 4.16.1 provided in the Debian 10 "main" repository.
Output of i3 --moreversion 2>&-:

Binary i3 version:  4.16.1 (2019-01-27) © 2009 Michael Stapelberg and contributors

Running version: < 4.2-200

I had posted my configuration file on Pastebin here, and it's primarily the default configuration, with some elements copied from a separate configuration file I'll be using for the project.

Logfile URL:

- Linux Distribution & Version: Debian 10 on "testing" branch, inside a schroot environment on the same distro version/branch on the host
- Are you using a compositor (e.g., xcompmgr or compton): No.

[i3bot]

I don’t see a link to logs.i3wm.org. Did you follow https://i3wm.org/docs/debugging.html? (In case you actually provided a link to a logfile, please ignore me.)

[kbhasi]

APT in my test environment is broken, so I can't install bzip2 and curl to be able to send the log. I think I'll rebuild the environment, when I have the time to do so.

[orestisfl]

#2765 (comment):

i3-nagbar is to be used only by i3, and as such should only contain the features we absolutely need in i3. Adding features upon user request for non-i3-internal use-cases is a slippery slope.

[kbhasi]

@orestisfl Thanks a bunch! It looks like I'll have to find a way to redirect commands sent to i3-nagbar and swaynag over to something else. I hope it's possible.