Notifications buffer doesn't handle encrypted events (Pantalaimon not configured properly) #290
-
OS/platformLinux Emacs version and provenanceGNU Emacs 29.4, from GNU Guix, installed with Guix Emacs commandDefault xinit for EXWM that comes with the GNU Guix System, which starts with this process: Emacs frame typeGUI Ement package version and provenance0.15.1, from GNU Guix, installed with Guix Actions takenAfter connecting to my Matrix ID, I tried to run ‘ement-notifications’. Observed resultsError instead of notifications buffer when I try opening it for the first time. Quitting out of the backtrace creates a (mostly) blank notifications buffer (see §Etc.) upon re-executing ‘ement-notifications’. Killing the (blank) notifications buffer recreates the error running ‘ement-notifications’ the next time, and repeat. Expected resultsA populated notifications buffer. Backtrace(search-failed "> ")
re-search-forward("> ")
ement-notifications-log-to-buffer(#s(ement-session :user ... :server ... :token "syt_Zm56_hvFgC..." :transaction-id 1057976981 :rooms ... :next-batch "s5137346139_75..." :device-id "8dc1c360ddc167..." :initial-device-display-name "Ement.el: user..." :has-synced-p t :account-data ... :events #<hash-table equal 610/730 0x10e03621>) #s(ement-notification :room-id "!rGTuczgsIZEVa..." :event ... :readp :json-false))
run-hook-with-args(ement-notifications-log-to-buffer #s(ement-session :user ... :server ... :token "syt_Zm56_hvFgC..." :transaction-id 1057976981 :rooms ... :next-batch "s5137346139_75..." :device-id "8dc1c360ddc167..." :initial-device-display-name "Ement.el: user..." :has-synced-p t :account-data ... :events #<hash-table equal 610/730 0x10e03621>) #s(ement-notification :room-id "!rGTuczgsIZEVa..." :event ... :readp :json-false))
ement-notifications-callback(#s(ement-session :user ... :server ... :token "syt_Zm56_hvFgC..." :transaction-id 1057976981 :rooms ... :next-batch "s5137346139_75..." :device-id "8dc1c360ddc167..." :initial-device-display-name "Ement.el: user..." :has-synced-p t :account-data ... :events #<hash-table equal 610/730 0x10e03621>) (... ...))
apply(ement-notifications-callback (... ...))
#f(compiled-function (&rest args2) #<bytecode -0xade0d8be6fe5cf0>)(((notifications . ...) (next_token . "4553541953")))
#f(compiled-function () #<bytecode 0x151bb35b08a05010>)()
plz--respond(#<process plz-request-curl<1>> #<buffer *plz-request-curl*-26334> "finished\n")
apply(plz--respond (#<process plz-request-curl<1>> #<buffer *plz-request-curl*-26334> "finished\n"))
timer-event-handler([t 26286 40415 411547 nil plz--respond (#<process plz-request-curl<1>> #<buffer *plz-request-curl*-26334> "finished\n") nil 377000 nil])Etc.The blank notifications buffer consists of a single entry like this (redacted the username):
I am using Pantalaimon—but notifications have always worked before, and messaging encrypted rooms still works. I had mentioned earlier that this was the same error as my previous bug report, #288, but it’s only now—that that has been fixed—I remember that the error with the notifications buffer was different from the ‘magit-section’ one; the notifications buffer errored out like this ever since I upgraded to 0.15.1. 😅 |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 7 replies
-
|
Given that the message shows as being still encrypted, it would seem to suggest that you haven't configured Pantalaimon properly for that room's keys, so it can't decrypt the message, and Ement does not handle encrypted events, so it fails to format properly. |
Beta Was this translation helpful? Give feedback.
-
|
I am able to load and send messages to that room though. |
Beta Was this translation helpful? Give feedback.
-
|
It's no bother. There's probably room for improvement in how Ement handles these things, i.e. the case in which Pantalaimon isn't yet configured correctly for a room or something. I haven't actually used Pantalaimon myself though (I have to admit I'm a bit tired of typing that name out, haha), so I'm relying on user reports. Anyway, based on what I've learned, you probably need to use |
Beta Was this translation helpful? Give feedback.
-
|
I’m at a loss for what further configuration to do with Pantalaimon. I’ve been using Ement + Pantalaimon for months, and I can both message and get notifications from the same room that Pantalaimon at first wasn’t able to decrypt. I guess I’ll try to compile its master branch, because I think the version packaged in Guix is a bit old now.
As a Pantalaimon (and EXWM) user, I’ll let you into a little trick: type “Pan” and then ‘hippie-expand’ (which is ‘M-/’ for me). :3 |
Beta Was this translation helpful? Give feedback.
-
Or failing that, abbrev-mode? :) |
Beta Was this translation helpful? Give feedback.
-
|
Well, us Pantalaimon users probably type its name more than “pan”, so I don’t see why an abbrev can’t be made from that. ଘ(∩^o^)⊃━☆゜ |
Beta Was this translation helpful? Give feedback.
-
You might try scrolling back in history, maybe you'll find older messages that use a different key, or something like that. Or, who knows, maybe it was some kind of random or rare race condition bug in Pantalaimon that didn't load the key before trying to decrypt that event.
Yes, that might help.
If I were typing into this box with Emacs, yes, I've used hippie-expand for a long time. :) |
Beta Was this translation helpful? Give feedback.
-
|
Ah, but notifications from unencrypted rooms do show up properly… |
Beta Was this translation helpful? Give feedback.
Given that the message shows as being still encrypted, it would seem to suggest that you haven't configured Pantalaimon properly for that room's keys, so it can't decrypt the message, and Ement does not handle encrypted events, so it fails to format properly.