Description of problem: Libnotify sometimes freezes the app that use it and it show warning: libnotify-WARNING **: 16:18:59.090: Failed to connect to proxy The app sometimes consume 100% of one of the CPU. Version-Release number of selected component (if applicable): libnotify-0.7.7-6.fc29.x86_64 How reproducible: Steps to Reproduce: 1. Install Claws-mail 2. Configure Notification plugin 3. Add mail box and short fetch email interval 4. Wait a while, untill it freezes Actual results: Claws-mail freezing Expected results: Claws-mail not freezing Additional info: sometime it take few hours using 15min fetch interval (I have 3 email account). Best is to just start claws and do other things, sometimes it consume 100% CPU right away and sometimes you need to focus the app and try to read emails (you can select different email but it don't switch and then consume 100% CPU) Reported to claws-mail (link attached) the bug includes stack trace from gdb (only claws, I can send from libnotify, if it'll be different, if you show me how) and another related bug is in Franz app (that app also show the same error/warning from libnotify and it's also freezeing, so it's not related to claws but may be bug in libnotify) as in franz issue comment also on my machine: notify-send "hello" # this shows message "hello" $ echo $DBUS_SESSION_BUS_ADDRESS unix:path=/run/user/1000/bus
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.