Bug 401259 - Receiving desktop notification in telegram while taking screenshot crashes user.
Summary: Receiving desktop notification in telegram while taking screenshot crashes user.
Status: RESOLVED WORKSFORME
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: 18.08.3
Platform: Manjaro Linux
: NOR grave
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-21 07:08 UTC by vlandemart
Modified: 2019-04-01 04:33 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description vlandemart 2018-11-21 07:08:22 UTC
SUMMARY
Receiving system notification from telegram messenger while taking screenshot in rectangular region ends session.
I'm not sure whether it is Spectacle's fault, or Telegram's but it works only if telegram's notifications are set in desktop notifications. I wasn't able to test it with other desktop notifications.

STEPS TO REPRODUCE
1. In telegram-desktop (version 1.4.3-1) head into settings > notifications and make sure "Desktop notifications" checkbox is ticked.
2. Start taking screenshot in rectangular region with spectacle (version 18.08.3-1)
3. Receive message and get desktop notification in telegram.

OBSERVED RESULT
User sessions end, terminating all apps and sending you to login screen.

EXPECTED RESULT
Notification shouldn't appear, screenshot should be taken normally.

SOFTWARE/OS VERSIONS
Linux: Manjaro KDE 64bit
KDE Plasma Version: 5.14.3
KDE Frameworks Version: 5.52.0
Qt Version: 5.11.2
Comment 1 Julian Steinmann 2019-03-02 14:13:37 UTC
I cannot reproduce this behavior when sending a normal desktop notification, so I would assume that Telegram is at fault here. Does the problem still occur? If yes, does the user session end also when receiving another, "normal" desktop notification?
Comment 2 Bug Janitor Service 2019-03-17 04:33:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2019-04-01 04:33:11 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!