Using a supported version?

• I have searched open and closed issues for duplicates.
• I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Overall summary

I’ve set notes to self to disappear after 1 day. I chose one message to be pinned, was prompted to select the time to pin the message for, and selected 7 days. I was shown the message in the title.

I’m now unsure whether the message will be unpinned and removed after 1 day or 7 days. My guess would be 7 days, but either way, I think the message should make this explicit, or at least unambiguous wrt. which timer takes precedence.

Steps to reproduce

1. set notes to self to disappear after 1 day
2. send a note to yourself
3. choose to pin the message
4. select to pin the message for 7 days

Expected result

Any of these, in order of preference:

1. ”This disappearing message will be unpinned and removed from the chat after 7 days.”
2. ”This disappearing message will be unpinned and removed from the chat after 1 day.”
3. ”Disappearing messages will be unpinned and the removed from the chat when the pinning timer expires.”
4. ”Disappearing messages will be unpinned and the removed from the chat when the disappearance timer expires.”

Actual result

”Disappearing messages will be unpinned when their timer expires and the message is removed from the chat.”

Screenshots

No response

Signal version

8.7.0

Operating system

Ubuntu 24.04

Version of Signal on your phone

8.6

Alright, from my brief testing it would seem this does not reproduce under Wayland.

My recipe above appears to be quite sensitive to details: I have a test user with a clean desktop (with little more customization apart from the extension), and there the recipe works just as written. On the other hand, with my main user account it doesn’t. To clarify: while the steps listed above fail to reproduce the issue with my main account, my main account does manifest the issue too; just not with those exact steps.

My main account starts up the Signal desktop client, Nextcloud client and some other stuff upon login, but so far I haven’t found which of those (if any) causes this difference.

I was, however, able to reproduce the ”see-through hole” effect under both accounts: instead of maximizing Gnome terminal (in step 3), I tile it to cover the left half of my screen, then start up Chrome/Firefox, tile itover the terminal window (i.e. to also cover the left half of the screen), before turning the display off and on again. Firefox then also manifests the hole, as does Gnome terminal when brought back to foreground from below. (Chrome does not manifest the hole, but then again Chrome has always appeared oblivious to the extension here.)

I should mention that I’m leaving the display off for about 4-5 seconds before turning it back on again. I’m not sure if that makes any difference, I’m just doing to to be sure that the ”I’m off” signal has time to propagate back to the system.