Bug 408546 - Message reply button on notification opens an absurd number of reply windows (default google messaging app)
Summary: Message reply button on notification opens an absurd number of reply windows ...
Status: RESOLVED DUPLICATE of bug 361525
Alias: None
Product: kdeconnect
Classification: Applications
Component: common (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-10 19:45 UTC by nickagodridge2
Modified: 2019-06-10 19:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
one press, 11 windows. no turbo/macro clicking (716.46 KB, image/png)
2019-06-10 19:45 UTC, nickagodridge2 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description nickagodridge2 2019-06-10 19:45:30 UTC 
Created attachment 120762 [details]
one press, 11 windows.  no turbo/macro clicking

SUMMARY
When choosing to reply to SMS from a desktop notification, 11+ response windows will open

STEPS TO REPRODUCE
1. Connect android phone via KDE-connect (pixel 3A in my case) 
2. Receive an SMS message on android phone via google's default messaging app
3. click reply in the notification dialogue on KDE desktop

OBSERVED RESULT
Multiple reply windows open for the same message, up to 11+ windows for the exact same message

EXPECTED RESULT
a single window opens per press of the reply button

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: Fedora 30
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.1

ADDITIONAL INFORMATION
It seems that more windows open each time the bug is repeated.  Started with 8, next reply opened 11 windows, number easily may continue to rise.

additionally, the bug seems either SMS or App-specific, the single facebook messenger notification I replied to correctly opened only a single window.
Comment 1 Simon Redman 2019-06-10 19:53:28 UTC 

*** This bug has been marked as a duplicate of bug 361525 ***