FS#75417 - [zettlr] requires [notification-daemon]

Attached to Project: Community Packages
Opened by Richard Kelly (rkelly) - Monday, 25 July 2022, 03:42 GMT
Last edited by Caleb Maclennan (alerque) - Monday, 26 June 2023, 12:21 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Caleb Maclennan (alerque)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After installation of zettlr package, GUI launches, but at almost every action, the program hangs temporarily with an error: libnotify-WARNING **: Failed to connect to proxy

Found that this goes away if notification-daemon is installed. Perhaps this should be included in the PKGBUILD depends list.

Additional info:
* package version(s): 2.3.0-1

Steps to reproduce:
- pacman -S zettlr on system without notification-daemon installed
- try to use program, encounter hangups when using certain functions

To solve, I installed notification-daemon and ran:
/usr/lib/notification-daemon-1.0/notification-daemon &
This task depends upon

Closed by  Caleb Maclennan (alerque)
Monday, 26 June 2023, 12:21 GMT
Reason for closing:  Works for me
Comment by Toolybird (Toolybird) - Monday, 25 July 2022, 21:56 GMT
Does it have to be notification-daemon? It looks like it's trying to interact with a "system" notification service [1].

[1] https://wiki.archlinux.org/title/Desktop_notifications
Comment by Richard Kelly (rkelly) - Tuesday, 26 July 2022, 01:41 GMT
I tried getting Zettlr to work with my existing KDE Plasma notification system, but am not convinced that this was set up properly. I then tried installing dunst as a replacement. Still had problems. Finally, only switching to the notification-daemon worked smoothly.

You are likely correct, though, in that any working "system" notification service should work. This Zettlr bug issue helped me zero in on the issue:
https://github.com/Zettlr/Zettlr/issues/2575

In that issue, the Zettlr dev implies that working notification service is not "strictly required". But in my experience, not having the service working made the program unusable.
Comment by Caleb Maclennan (alerque) - Monday, 22 August 2022, 10:16 GMT
I'm not yet convinced this is an issue with this package so much as a bug in some combination of zettlr, libnotify, or electron. I'm not sure which even, but having Electron in the mix sure makes things complicated. I don't think forcing `notification-daemon` in specific on people when there are so many alternatives is a good idea. Also not that while I happen to have it installed it is not running in my DE-free AwesomeWM setup and Zettlr runs fine for me.
Comment by Caleb Maclennan (alerque) - Monday, 26 June 2023, 12:21 GMT
I believe this bug is obsolete. I've tested it making sure I do *not* have notification daemon and current releases of Electron & Zettlr have not had this issue for some time. Note this conclusion even predates the current Electron and beta Zettlr releases currently in teh repository.

Note Zettlr beta is published in Arch repos against usual guidelines because we had to drop the old EOL Electron that it depended on to get some other important updates and rebuilds though.

If anybody still has this bug please feel free to refile/reopen this, but all my evidence suggests it is not not an issue.

Loading...