Franz: Franz freezes (due to error in libnotify?)

[johanneswerner]

I am running Franz with several services on current Debian testing. The window freezes every few minutes and I have to wait or to restart until it is usable again.

Running Franz from the command line only shows this line (about 10 times in 20-30 minutes).

(franz:8953): libnotify-WARNING **: Failed to connect to proxy

Expected Behavior

I would expect that it is not freezing.

Current Behavior

As described above, it is freezing and takes some time to use Franz again. However, if I disable notifications at all, Franz runs smoothly.

Possible Solution

Disable notifications, but I would like to know what I have to do to use notifications. Is this an error or a problem in libnotify?

Steps to Reproduce (for bugs)

1. Run Franz and wait
   (probably this is a problem which is only an issue on my computer due to a missing package maybe)

Context

see above, it was impossible to use the tool without interruptions every few minutes. disabling of notifications made it usable again.

Your Environment

• Franz Version used:
  5.0.0-beta.15

• Operating System and version:

$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux testing (buster)
Release:    testing
Codename:   buster

[mxxaur]

I have the exact same issue as you, but I'm running Archlinux "stable" (no testing, latest updates).

Also running beta.15 on Gnome 3 (X11), but it has been an issue since I started trying out Franz and that was one version before beta.14.

Disabling notifications solves the freezes as well for me, but that's obviously no real solution. I'd love to get a fix :)

notify-send "something" does work for me though and it is instant.

[johanneswerner]

notify-send "something" does work for me though and it is instant.

What does this mean?

[mxx82]

What does this mean?

that libnotify is working correctly over here (and still franz is freezing).
Are you on Gnome as well? X11 or Wayland?
BTW: just out of curiosity, do you run Franz as is or do you run it inside a network namespace?

[mxx82]

Easternbluebird, have you solved your problem?

I was missing $DBUS_SESSION_BUS_ADDRESS (I was running Franz in a network ns, which wasn't the issue, but I was using sudo to set it up without the "-E" switch to preserve environment variables).

So for me it does work now.

[johanneswerner]

I was missing $DBUS_SESSION_BUS_ADDRESS (I was running Franz in a network ns, which wasn't the issue, but I was using sudo to set it up without the "-E" switch to preserve environment variables).

The variable is set in my case, so the issue still exists for me.

[b3b0]

Same issue here using i3wm on Fedora 27. Freezes and becomes unresponsive. I'm typically just killing it and restarting the executable to use for another 10 minutes or so until it freezes again.

[Mercedes-Joy]

I am also seeing this.
Franz on Debian 9 platform.

[Mercedes-Joy]

Still having this issue. is there a primer on how I should document and pass back info about my system and services?
I am monitoring this thread as I believe I might be of assistance.

[gabrielps]

Debian GNU/Linux 9.4 (stretch) + GNOME 3.22.2 + franz_5.0.0-beta.18_amd64
I'm having no freezing issues, nor libnotify errors and notify-send is working as expected but I'm getting no notifications at all. I hope this can help in some way.

[heriipurnama]

yes
i use arch linux same
(franz:3048): libnotify-WARNING **: Failed to connect to proxy

[neutron-byte]

I have also the same issue.
Ubuntu 16.04.4 LTS, KDE 5.5.5

[gerardobot]

I'm having the same issue on Ubuntu 18.04 + GNOME 3.28.2 + franz_5.0.0-beta.18_amd64

[baisar]

I have the same issue on Linux Mint 18. Cant solve it. I tried to reinstall NodeJS, installed Node 8, 10, no changes.
Does anybody know the solution?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[johanneswerner]

A lot of people seem still to have the problem, has anyone a solution for it?

[dwightyy]

I'm having this problem with i3-wm 4.16-1 and Franz 5.0.0-beta.1 on Arch x86-64, the screen freezes completely and i have to kill it.

One thing that i noticed was that i'm having the same issue with the Discord and Whatsie app.

[jcubic]

I have the same issue with different application on Fedora so I think it's Fedora bug.

Here is my bug report in Claws-mail app on Fedora 29
https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4148

[jcubic]

I've reported the bug in Fedora/RedHat bug tracker you can subscribe and comment.

[voinovann]

Hi,

I had a similar problem with Slack notifications: it would freeze when a new message notification was to be displayed and there was the same libnotify error in the command line.

The problem in my case was the same as described here. Dbus was starting the KDE notification service instead of xfce4-notifyd(I am using xfce on my machine). Removing org.kde.plasma.Notifications.service from /usr/share/dbus-1/services/ made the problem dissapear. Although the "fix" might look a bit hackish, it was still good enough for me as a short term solution. I hope this info helps someone.

[bphd]

Same with Discord

And it's not related to a certain distro or a certain app, it's really libnotify who freeze the apps because he can't display the notification. I suggest a report on libnotify repo

(It works by installing a notification manager like dunst or kde or whatever but it's definitively not a solution, the computer shouldn't freeze just because we are receiving a notification and can't display it)

[NickWilde263]

until i though my Discord is unusable on linux for years

[641i130]

Can confirm this still happens for me (currently on arch linux). Though discord works fine. Very odd indeed.

Maybe its a WM based error. I use i3wm.

[jthadden]

Had the same for some days and digged into it. The reason here was that the notification daemon of my desktop manager xfce4 was not running any more. I just had to restart it with (I am on Fedora 32)
/usr/lib64/xfce4/notifyd/xfce4-notifyd &>/dev/null &
and everything instantly worked again. Overall I would say that a solution would be to queue notifications into a separate thread that is doing the actual notification in the background - thus the main thread can continue to work.

[NickWilde263]

Can confirm this still happens for me (currently on arch linux). Though discord works fine. Very odd indeed.

Maybe its a WM based error. I use i3wm.

i need to switch display manager to fix discord crashing when notification come in (idk how this related to notification)

[bphd]

Overall I would say that a solution would be to queue notifications into a separate thread that is doing the actual notification in the background - thus the main thread can continue to work.

I don't know why people still digging through this problem whereas it's obvious that the problem is identified and the author just ignore this case because il would need a big recode of the project

[NickWilde263]

try change your display manager or your desktop shell it fixed my issue about crashing due libnotify lbrary