Open RSirois opened 5 months ago
Please concretize the "connectivity issue". What exactly does the desktop notification show? (Please enable the desktop notification for debugging, if you don't have it already.)
It shows output of a ping command and it says it failed and the desklet changes from green to red
Best regards,
Randy Sirois
On Fri, Jan 26, 2024 at 12:19 Georg Sieber @.***> wrote:
Please concretize the "connectivity issue". What exactly does the desktop notification show? (Please enable the desktop notification for debugging, if you don't have it already.)
— Reply to this email directly, view it on GitHub https://github.com/linuxmint/cinnamon-spices-desklets/issues/1041#issuecomment-1912644434, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKMA6GWBC5UNA356ZSPUSH3YQQFWZAVCNFSM6AAAAABCMU2226VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJSGY2DINBTGQ . You are receiving this because you authored the thread.Message ID: @.***>
So the exact output of this ping command on the desktop notification would be interesting... As soon as this output reports a packet loss greater than 0%, the desklet says "CRIT". So I think you actually have short network dropouts since I'm not able to reproduce this behavior. It's not that unusual when using WiFi.
Have you looked what statistics your separate ping
command in the terminal reports after exiting it with Ctrl+C? Surely it reports a small packet loss >0% too.
0% from a running ping If it happens frequently in WiFi, which is what most people use, then it is useless
Best regards,
Randy Sirois
On Sat, Jan 27, 2024 at 04:04 Georg Sieber @.***> wrote:
So the exact output of this ping command on the desktop notification would be interesting... As soon as this output reports a packet loss greater than 0%, the desklet says "CRIT". So I think you actually have short network dropouts since I'm not able to reproduce this behavior. It's not that unusual using WiFi.
Have you looked what your separate ping command in the terminal says after exiting it with Ctrl+C? Surely it reports a small packet loss >0% too.
— Reply to this email directly, view it on GitHub https://github.com/linuxmint/cinnamon-spices-desklets/issues/1041#issuecomment-1913135408, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKMA6GW5XZEKBZNW3AFEBBDYQTUMJAVCNFSM6AAAAABCMU2226VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJTGEZTKNBQHA . You are receiving this because you authored the thread.Message ID: @.***>
then it is useless
Wow, what kind words. So how would you design a ping check to be "useful"??
Georg, I do like this desklet. However, it reports a different result than a running Debian ping. The Debian ping shows zero loss of response during the entire time that the desklet reports there is no response. The desklet should report accurate results. Randy
From: Georg Sieber @.> Sent: Monday, January 29, 2024 6:15 AM To: linuxmint/cinnamon-spices-desklets @.> Cc: RSirois @.>; Author @.> Subject: Re: [linuxmint/cinnamon-spices-desklets] Erroneous reporting of failing connection (Issue #1041)
then it is useless Wow, what kind words. So how would you design a ping check to be "useful"?? — Reply to this email directly, view it on GitHub https://github.com/linuxmint/cinnamon-spices-desklets/issues/1041#issuecomment-1914780317 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKMA6GQMNUFDQHFURCLMF3TYQ6VFHAVCNFSM6AAAAABCMU2226VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJUG44DAMZRG4 . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AKMA6GVHRAHCRSW4FBXNUSDYQ6VFHA5CNFSM6AAAAABCMU2226WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTSEE5J2.gif Message ID: @. @.> >
I don't know @RSirois . As you see in the notification output, it internally uses the normal ping command line. Since you are the only one reporting this issue and there is no idea how to improve it, I think this issue should be closed.
Ok thanks
Best regards,
Randy Sirois
On Thu, Feb 8, 2024 at 10:52 Georg Sieber @.***> wrote:
I don't know @RSirois https://github.com/RSirois . As you see in the notification output, it internally uses the normal ping command line. Since you are the only one reporting this issue and there is no idea how to improve it, I think this issue should be closed.
— Reply to this email directly, view it on GitHub https://github.com/linuxmint/cinnamon-spices-desklets/issues/1041#issuecomment-1934743874, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKMA6GQSSUEJZWVPL2VGT5DYSUNILAVCNFSM6AAAAABCMU2226VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZUG42DGOBXGQ . You are receiving this because you were mentioned.Message ID: @.***>
Desklet version/Build date
1.5
Cinnamon version
Cinnamon 6.0.4
Distribution
LMDE 6 (faye) x86_64
Graphics hardware and driver used
AMD ATI Radeon RX 6400/6500 XT/6500M, default debian driver
Desklet name and maintainer
hostcheck@schorschii @schorschii
What happened?
The desklet is set to report connectivity to the router. The computer and router are 8 feet from each other. Hostcheck reports a connectivity issue repeatedly spaced several minutes apart and the outage is reported for about half a minute. it is set to check every 15 seconds. I have a continuous ping running, and I am using the computer. there is no connectivity issue. I had to disable the desklet.
Other information
neofetch
.-::---.. randy@eagle .:++++ooooosssoo:. ----------- .+o++::.
.:oos+. OS: LMDE 6 (faye) x86_64 :oo:.-+oo: Host: X570S AERO G -CF
+o/.::::::-. .++-
Kernel: 6.1.0-17-amd64/s/ .yyyyyyyyyyo: +o-
Uptime: 14 hours, 53 minsso .ss ohyo
:s-: Packages: 2404 (dpkg), 17 (flatpak)s/ .ss h m myy/ /s`` Shell: bash 5.2.15
s:oo s m Myy+-o:
Resolution: 5120x2880oo :+sdoohyoydyso/. DE: Cinnamon 6.0.4 :o. .:////////++: WM: Mutter (Muffin)
/++ -:::::- WM Theme: Mint-Y-Dark-Blue (Mint-Y)++- Theme: Adwaita [GTK2/3]
/+- Icons: Adwaita [GTK2/3] .+/. Terminal: gnome-terminal .:+-. CPU: AMD Ryzen 7 3800X (16) @ 3.900GHz `--.`` GPU: AMD ATI Radeon RX 6400/6500 XT/6500M Memory: 11351MiB / 64193MiB