Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error whet try to start Deadd Notification Center #187

Open
AndresD172 opened this issue Feb 11, 2022 · 3 comments
Open

Error whet try to start Deadd Notification Center #187

AndresD172 opened this issue Feb 11, 2022 · 3 comments

Comments

@AndresD172
Copy link

AndresD172 commented Feb 11, 2022

Hello! I instaled Deadd Notification Center using make and sudo make install, and the install elapsed without problems. But at the moment to run deadd-notification-center in console i got the following problem

deadd-notification-center: symbol lookup error: deadd-notification-center: undefined symbol: pango_layout_deserialize_error_get_type
How I can solve the problem? I added a screenshot of the error showed in console.

Greetings! <3

2022-02-11-094249_1064x36_scrot

@AndresD172
Copy link
Author

Hello! It's me again.

I finally solved the problem! I removed the installation created with the make-make install method and reinstalled it with the method described for distributions like Ubuntu, Debian, etc.

But I have two small problems again. I have already started the notification daemon using the ddead-notification-center command and in theory it works now, but if a notification arrives the daemon does not show its notification instead of the default notification. And the other problem is that I don`t know how to open the notification center using polybar, I have tried to open it with rofi and with commands in cmd but nothing works. Can anyone help me to solve at least the first problem.... thanks to everyone who can help me!

@phuhl
Copy link
Owner

phuhl commented Feb 19, 2022

Hi @AndresD172, can you confirm e.g. by using htop, that ddead-notification-center is actually running?

@d3adb5
Copy link
Contributor

d3adb5 commented Jul 23, 2023

The first problem seems to me like a linking problem. With regards to the "default notification" being shown instead of a popup on deadd-notification-center: do you know what your default notification daemon is, @AndresD172? And if so, can you kill its process and see if notifications are handled by deadd?

Since both are likely connecting to DBus and waiting for notifications, I think the first one to have gotten there gets precedence. I'm no DBus expert, but I assume that is what is going on, as if I run Dunst and deadd, only one actually shows any notifications.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants