Jump to content
funtoo forums
  • 0
Hund

I cannot get Dunst and libnotify to work

Question

I installed Funtoo (using the "pure64" and "workstation" profile) a few days ago and it works great - except for no notifications.

 

I have used Dunst and libnotify in the past with both Arch and Gentoo without any issues. But for some reason it do not want to work in Funtoo.

$ dunst
X Error of failed request:  BadRequest (invalid request code or no such operation)
  Major opcode of failed request:  139 (RANDR)
  Minor opcode of failed request:  42 ()
  Serial number of failed request:  42
  Current serial number in output stream:  42
The command "notify-send" shows nothing, no notification or any error message. I'm not sure how to debug this any further? Help? :)

Share this post


Link to post
Share on other sites

17 answers to this question

Recommended Posts

  • 0
This happens in dbus when I run "$ notify-send Hund" : https://pastebin.com/bjasAhNX

 

Edit: With "$ dunstify Hund" I get: 

 


Unable to send notification: Error calling StartServiceByName for org.freedesktop.Notifications: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.Notifications exited with status 1

Share this post


Link to post
Share on other sites
  • 0

I noticed this message when I closed X:
 

XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
after 314 requests (314 known processed) with 0 events remaining.

Share this post


Link to post
Share on other sites
  • 0

Hey, not sure about this at all, but this might be a dbus error. Is dbus working in general? If you are using a Window Manager, are you wrapping its launch script with dbus-launch?

 

I'm using dunst on my Funtoo desktop, so in general it can work.

 

Edit: Seeing your log only know it seems like dbus is indeed running and I'm on the wrong track.

Share this post


Link to post
Share on other sites
  • 0

After much help via IRC from several friendly users I managed to (finally) solve it.

 

I had by accident installed two notifications server (from all the testing), which resultet in that none of them worked. And the reason that Dunst didn't work, was that it needed the version 1.5 of RanR and I had only version 1.4.

 

And now it finally works! :D

Share this post


Link to post
Share on other sites
  • 0

I'm getting the same BadRequest X Error as Hund, but I only have one notification server installed (dunst), plus libnotify 0.7.6-r3 and xrandr 1.5.0.

 

This started happening after I switched to kits whilst keeping my profile the same ("desktop" flavor, "current" build)

 

Has anyone else come across this?

 

edit: @onli , my dunst used to work as well, before I switched to kits. So I'm wondering, have you made the switch as well?

Share this post


Link to post
Share on other sites
  • 0

edit: @onli , my dunst used to work as well, before I switched to kits. So I'm wondering, have you made the switch as well?

 

No, I wasn't aware of that and changed nothing.

Share this post


Link to post
Share on other sites
  • 0

I found a temporary solution. Need to downgrade the version to 1.1.0 do this by using the commands

 

emerge -C dunst

emerge =x11-misc/dunst-1.1.0

 

If you dont want it upgraded you need to add =x11-misc/dunst-1.2.0 to /etc/portage/package.mask

Share this post


Link to post
Share on other sites
  • 0

so i have been experimenting some more. Checked dunst changelog which says "Dropped Xinerama in favour of RandR, Xinerama can be enabled with the -force_xinerama option if needed". In the config file there is an option that says force_xinerama = false. Change it to true. If you dont have that option, it means that you are using the config file of dunst 1.1.0 still. You should update it because they have changed some other things to. You can copy it from /usr/share/dunst/dunstrc and put it in ~/.config/dunst/dunstrc

 

dont know why i cant use randr

Share this post


Link to post
Share on other sites
  • 0

I downgraded Xorg from version 1.19 to 1.17 today (due to unrelated issues) and Dunst 1.2.0 stopped working for me, but downgrading to version 1.1.0 solved it.

Share this post


Link to post
Share on other sites
  • 0

hund if you want to use version 1.2.0 of dunst read my previous comment and copy the config file from "/usr/share/dunst/dunstrc" and put it in "~/.config/dunst/dunstrc" then change the "force_xinerama = false" setting to "force_xinerama = true"

Share this post


Link to post
Share on other sites
  • 0

hund if you want to use version 1.2.0 of dunst read my previous comment and copy the config file from "/usr/share/dunst/dunstrc" and put it in "~/.config/dunst/dunstrc" then change the "force_xinerama = false" setting to "force_xinerama = true"

Oh, I totally missed that. Thank you!

Share this post


Link to post
Share on other sites
  • 0

agaric have you managed to solve it?

 

@checkulater Sorry for the late reply. I was continuing without dunst until your recommendation (setting force_xinerama to true) fixed it for me. Thank you very much.

 
"dunst will not be able to detect when a montitor is connected or disconnected" (according to /usr/share/dunst/dunstrc) sounds less than ideal, but at least the daemon runs. I can't tell whether the xrandr incompatibility is an upstream issue or an ebuild-related one. I haven't been able to find any related issues on https://github.com/dunst-project/dunst either.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×