Bug 431566 - msg and call notifications from Android phone are coming all again after disconnecting and later reconnecting the phone
Summary: msg and call notifications from Android phone are coming all again after disc...
Status: RESOLVED DUPLICATE of bug 411598
Alias: None
Product: kdeconnect
Classification: Applications
Component: plasmoid (other bugs)
Version First Reported In: 1.4
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-01-13 21:17 UTC by Michael
Modified: 2023-04-07 21:17 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael 2021-01-13 21:17:17 UTC
the repeatedly notification make it difficult to read them, clicking X they also come again, they just stop coming when I delete the msg from on the phone what eventually is not what I want

I am now on the computer below (kdeconnect/focal,now 1.4-0ubuntu5 amd64 [installed]) but happens exactly the same on the latest Kde Neon after the upgrade two days ago, if you need it I can send tomorrow the exact data

the only thing i can do now is disabling all communications in the setup, then it stops 

thanks


System:    Host: hm-mint Kernel: 5.10.6-hmich-tl-frt-2.32 x86_64 bits: 64 
           Desktop: KDE Plasma 5.18.5 Distro: Linux Mint 20.1 Ulyssa 
CPU:       Topology: Quad Core model: AMD Phenom 9550 bits: 64 type: MCP L2 cache: 2048 KiB 
           Speed: 1100 MHz min/max: 1100/2200 MHz Core speeds (MHz): 1: 1100 2: 1100 3: 2200 
           4: 1100 
Graphics:  Device-1: NVIDIA GK208 [GeForce GT 710] driver: nouveau v: kernel 
           Display: x11 server: X.Org 1.20.9 driver: nouveau resolution: 1280x1024~60Hz 
           OpenGL: renderer: llvmpipe (LLVM 11.0.0 128 bits) v: 4.5 Mesa 20.2.6
Comment 1 Albert Vaca Cintora 2023-04-07 21:17:04 UTC
This should be fixed now, see #411598

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