Skip to content

[bug] "2 unread messages", but not visible anywhere in app

Open @trwnh.com opened this issue 1 reply
  1. @trwnh.com Bluesky reported

    Type
    Bug report
    Area
    Reroute app
    Platform
    Linux
    Version
    0.3.2-rc.5

    1. open reroute 2. make sure you've read all the messages you see expected behavior: 0 unread messages actual behavior: 2 unread messages (the status notifier item has a red dot on it and it's taunting me)

  2. @trwnh.com Reporter

    ``` Reroute 0.3.2-rc.5 on linux x86_64 · 1 account System: Arch Linux, kernel 6.18.63-3-lts Web view: 2.54.2 Desktop: wayland session, GNOME, GDK_BACKEND -, Wayland display set Media plugins (GStreamer, for video in the web view): MP4 yes · H.264: openh264 yes · AAC: fdkaac yes · libav plugin yes (decodes what its FFmpeg has) · WebM: vpx yes · sound out: autodetect yes, pulseaudio yes Running for 0h 4m Wire version: Tieroute 2 Calls: relay only (the default) 01:36:58 stream: open 01:37:00 server: GET profile/tr:<id> failed after 0.0 s: 404 not-found 01:37:00 server: GET profile/tr:<id> failed after 0.0 s: 404 not-found 01:37:07 community: a delivery wasn't processed: process: ValidationError(UnableToDecrypt(SecretTreeError(TooDistantInThePast))) (×4, last at this time) 01:37:07 community: a delivery wasn't processed: process: ValidationError(UnableToDecrypt(SecretTreeError(SecretReuseError))) 01:37:07 community: a delivery wasn't processed: process: ValidationError(UnableToDecrypt(SecretTreeError(TooDistantInThePast))) (×5, last at this time) 01:37:07 community: a delivery wasn't processed: process: ValidationError(UnableToDecrypt(SecretTreeError(SecretReuseError))) (×2, last at this time) 01:37:18 server: GET profile/tr:<id> failed after 0.0 s: 404 not-found 01:37:20 server: GET profile/tr:<id> failed after 0.0 s: 404 not-found 01:40:04 server: GET profile/tr:<id> failed after 0.3 s: 404 not-found 01:40:04 server: GET profile/tr:<id> failed after 0.3 s: 404 not-found 01:40:06 server: GET chain/tr:<id> failed after 0.0 s: 404 not-found (×4, last at this time) 01:40:06 v2: adding a migrated member: waiting for an account history being fetched (×2, last at this time) 01:41:04 server: GET profile/tr:<id> failed after 0.1 s: 404 not-found 01:41:04 server: GET profile/tr:<id> failed after 0.1 s: 404 not-found ```

Sign in with a Bluesky or fediverse account to reply. To confirm that you can reproduce this issue, reply with your platform and version.