Broken wrapping in 1.4.0

[xbruno]

Hello,
since the update to dunst 1.4.0-1, the dynamic width does not work.
Here with this example : notify-send 'hello' 'hello world - hello world'

My dunstrc : https://pastebin.com/raw/ERgs9Z5c

• Version: 1.4.0-1
• Install type: pacman.
• Archlinux up to date.

Thanks

[tsipinakis]

This works on my end what do you see broken?

The screenshot you posted doesn't appear to load.

[xbruno]

The screenshot is on toile-libre.org and for the moment is '503 Service Unavailable'.

[tsipinakis]

Took a while to get to this but I wanted to find time to actually set up an Arch environment to try to reproduce this myself but I was entirely unsuccessful. Your dunstrc works fine both in Debian and in Arch for me.

Does reverting to 1.3 fix this?

Can you run a git bisect to determine the commit that caused this? Feel free to ask if you need help with this.

[xbruno]

I reverted to 1.3.2-2 and dunst works fine.

I look for run a git bisect.

[xbruno]

I have installed git and try.
can you tell me what to do?

[tsipinakis]

First clone & make sure you can compile dunst, run:

git clone https://github.com/dunst-project/dunst
cd dunst
make
./dunst

Make sure that this starts dunst up and it works, then do the following to find what broke it:

First start the bisect with:

make clean
git bisect start
git bisect bad HEAD
git bisect good v1.3.2

Then to do the actual bisect do

make
./dunst

Here send a notification from another terminal to see if the issue exists and run git bisect bad if it's broken or git bisect good if it's not.

Repeat the last 3 commands until it prints out the commit that broke it. It'll look something like

commit XYZ
Author: blah
...

[xbruno]

thank you for explanation.
Result:
4f510e1 is the first bad commit
commit 4f510e1
Author: Benedikt Heine [email protected]
Date: Mon Feb 25 19:01:34 2019 +0100

[hg8]

For those who need it you can downgrade to 1.3.2.2 on Arch Linux using :

$ sudo pacman -U https://archive.archlinux.org/packages/d/dunst/dunst-1.3.2-2-x86_64.pkg.tar.xz

---

I have the same issue, but could not solve it by downgrading. The issue seemed to be linked to the font used.

font = Iosevka 8

font = Hack 8

using

$ dunst --version
Dunst - A customizable and lightweight notification-daemon 1.4.0 (2019-03-30)

Hope this can gives pointers.

[tsipinakis]

The biggest change in the commit @xbruno pointed at is that we no longer assume DPI is 96 and calculate it from the screen dimensions by default.

@xbruno Can you try running:

echo "Xft.dpi: 96" | xrdb - merge

and restart dunst, does that fix it?

If so, I believe the issue is in older versions of dunst as well but the dpi change simply revealed it.

[tsipinakis]

The issue seemed to be linked to the font used.

I just tried installing Iosevka on Arch but still cannot reproduce this with the given notification.

@hg8 Can you upload your full dunstrc as well?

Also can you build tsipinakis@9935eb2, run dunst with -verbosity debug and upload the output? This is to find out the DPI as I suspect this has something to do with it.

[hg8]

Here is my dunstrc.

The biggest change in the commit @xbruno pointed at is that we no longer assume DPI is 96 and calculate it from the screen dimensions by default.

I have Xft.dpi: 220 in my .Xresources file. Setting my dpi to 96 don't have effects either.

Also can you build tsipinakis/dunst@9935eb2, run dunst with -verbosity debug and upload the output?

$ ./dunst -verbosity debug
DEBUG: RUN
DEBUG: Using DPI: 220.271003

The output is the same with whatever font I use.

[xbruno]

I run :
echo "Xft.dpi: 96" | xrdb -merge
restart dunst and now dunst 1.4.0-1 works fine.

[tsipinakis]

Weird. @hg8 can you also run a bisect and see what that gives?

[hg8]

@tsipinakis Maybe I should open a different issue ? I now think my problem is different, and I could not get to reproduce it with any other than font Iosevka. It's strange.

Weird. @hg8 can you also run a bisect and see what that gives?

That's not needed, even at 1.2.0 I can reproduce the issue.

[tsipinakis]

@hg8 Did this start happening recently or did you just discover it now?
There's also #624. As I've said there I have a feeling this is something to do with pango, our font rendering library.

It just seems weird that 4-5 people have similar but not quite the same issue at the same time - seemingly not tied to dunsts version.

[hg8]

@tsipinakis

Did this start happening recently or did you just discover it now?

I just started to use Dunst 2 days ago so I can't tell if it was working before.

---

Well now I have to say I am completely at loss...
After a reboot the issue is back on Hack font :

So I tried to switch to Iosevka font and ....

Reboot, Iosevka still working, Hack not working...
Downgrade to dunst-1.3.2.2, Iosevka still working, Hack not working...

I really don't understand what's going and I have no idea how to help you debug this...

But maybe you are right then, the issue may come from pango and not dunst itself?

[fwsmit]

Hi, is this still an issue with the current dunst version?