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

Seems don’t work for me #2

Closed
bepolymathe opened this issue Nov 8, 2022 · 19 comments
Closed

Seems don’t work for me #2

bepolymathe opened this issue Nov 8, 2022 · 19 comments

Comments

@bepolymathe
Copy link

Hi @sethyuan

Waiting for this for a long time. Thanks for that... but it don’t work for me with 0.8.10 on linux (Fedora).
Nothing appeared.

@sethyuan
Copy link
Owner

sethyuan commented Nov 8, 2022

Oh my, I don't use Linux desktop, and I'm not sure if Linux has some kind of system level notification center.

@bepolymathe
Copy link
Author

bepolymathe commented Nov 8, 2022

Ok. Yes there is a notification system build on libnotify and use with the notify-send command. It works with Gnome or KDE desktop. Just an introduction here.
It would be really practical to have it also under linux. In my case, I use linux at home and windows at work with logseq synchronize on both machines (+ the phone).

@sethyuan
Copy link
Owner

sethyuan commented Nov 8, 2022

Can you use console (ctrl+shift+i) and capture a screenshot of the errors? This should happen at the moment the system notification is supposed to appear.

BTW, did you install the plugin using the marketplace?

@bepolymathe
Copy link
Author

BTW, did you install the plugin using the marketplace?

Yes !

Can you use console (ctrl+shift+i) and capture a screenshot of the errors? This should happen at the moment the system notification is supposed to appear.

No errors 🤔

image

@sethyuan
Copy link
Owner

sethyuan commented Nov 8, 2022

Strange. Can you type Notification.permission in the console and see what it says?

@bepolymathe
Copy link
Author

bepolymathe commented Nov 8, 2022

Same behaviour...

image

image

@sethyuan
Copy link
Owner

sethyuan commented Nov 8, 2022

You wrote it in the wrong place. You should execute it below "41 issues", after the arrow pointing right.

@bepolymathe
Copy link
Author

Oups...
image

@sethyuan
Copy link
Owner

sethyuan commented Nov 9, 2022

I'm out of ideas. It looks like the methods are executed, but still nothing is popping up. I think it may be a bug in Electron (the foundation framework Logseq is built on).

@bepolymathe
Copy link
Author

All right. I understand. I'll try to look into it on my end and let you know

@emms007
Copy link

emms007 commented Nov 15, 2022

I have the same case with Windows. I see no error, it seems that the plugin is not detecting that it is time to "ring".
Any way to debug further?

@bepolymathe
Copy link
Author

I have the same case with Windows

Strange. It works for me on windows machine 🤔

@emms007
Copy link

emms007 commented Nov 15, 2022

Not sure how nor why but it worked after another attempt tonight.
Now I am not just not sure how to access to the "snooze reminder". I understand i need to click on the popup but nothing is happening.

@sethyuan
Copy link
Owner

Sometimes, it's recommended to restart Logseq after installing a plugin.
As of snooze in Windows, it's a known issue. It seems that Electron in Windows does not fire the notification click event. We need to wait for Logseq to update its Electron version to see if it can solve this problem.

@sethyuan
Copy link
Owner

@lobbia Be sure you have Logseq running, this is not a system service level alert, so the software has to be running and the respective graph opened in order to work.

@sourcebert
Copy link

sourcebert commented Jun 29, 2023

This worked for me (Ubuntu 23.04 - GNOME, Logseq Flatpak):

  • install Flatseal (Flatpak permissions manager): flatpak install flathub com.github.tchx84.Flatseal
  • in Flatseal change the following settings for Logseq
    • session bus section > add permission: org.freedesktop.Notifications
    • portals section > enable notifications

Hope that helps!

@clobrano
Copy link

clobrano commented Nov 7, 2023

#2 (comment)
This also worked for me

@clobrano
Copy link

clobrano commented Nov 7, 2023

It might be a good idea to report this somehow in the Readme page (or somewhere else) to support Linux users 😊

@sethyuan
Copy link
Owner

sethyuan commented Nov 7, 2023

Good idea, I will add this to the README file.

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

6 participants
@emms007 @clobrano @sethyuan @sourcebert @bepolymathe and others