=== guiverc2 is now known as guiverc [12:37] Hi all [13:08] <А> Hello everyone, I finally made sure that Viber does not slow down terribly, you need to install it through a flatpak [14:20] hello [17:01] Hello, [17:01] I just did an "update" (Discover), and after that, I had no more graphic interface. With "startx" I came back, but now I cannot change the driver anymore (that worked last time "I" did the nvidia "update". [17:01] What could I do now? [22:49] I'm running Kubuntu 22.04. There is another machine on my LAN running Debian. Is there a way that the Debian machine can trigger a pop up notification on the Kubuntu machine? The more noticible, the better. Something like kdialog --msgbox but since the alert is not coming from the local machine....??? [22:57] WJC42: Maybe install an SSH server on the Kubuntu machine? [22:57] Then you can disable password authentication and set up public key based authentication so that the Debian machine can execute commands on the Kubuntu machine. [22:58] Then you'd do something like "if [ condition is met ]; then ssh me@192.168.0.999 kdialog --msgbox ...; fi" [22:58] (You might have to arrange for the DISPLAY environment variable to be set to :0 so that the window appears on the right computer.) [22:59] arraybolt3: yes I thought of doing it that way but was trying to avoid that if possible because I don't want the Debian machine to be able to get into the Kubuntu machine via SSH. But I maybe am too paranoid [22:59] Hmm, good point. [22:59] In that instance you might be able to use some inventive netcat gymnastics to do it. [23:00] Something like "if [ condition is met ]; then echo "triggerNotification" | nc 192.168.0.999 9876; fi" on the Debian machine. [23:01] And then on the Kubuntu machine, "doNotification=`nc -l 192.168.0.999 9876`; if [ "$doNotification" = "triggerNotification" ]; then kdialog --msgbox ...; fi" [23:01] Or something along those lines. [23:01] Maybe run the Kubuntu side of things in a loop so you can get multiple notifications. [23:01] And perhaps feed the contents of $doNotification to kdialog. [23:01] Anyway, that should hopefully give you some ideas. [23:02] OK that's something to look into. I have not used netcat before but it's funny since this I was just reading about it 15 minutes ago for something totalyl unrelated [23:04] I'll read up a bit on netcat, but it sounds promising. Thank you! [23:04] Glad to help! [23:04] (I use netcat quite a bit for beaming files between computers. [23:05] It should be noted that it *doesn't* encrypt things, so be careful if the data you're transferring is sensitive.) [23:06] Yes that's why I was reading about it. I wanted to see if there was something faster than FTP because I read some comments somewhere about FTP having a lot of overhead. I had just set up an ftp server because I didn't want the overhead from SFTP encryption [23:32] WJC42: FTP sounds like you could get race conditions if you aren't careful (for instance if your Debian system sends two notifications in quick succession by modifying the same file you might only end up getting one of them). It would probably also be way harder to code for. [23:36] arraybolt3: my ftp / netcat prior reading was for a totally different application. I just mentioned it because I had never really heard of netcat before, but twice in 15 minutes was reading about it for different reasons. When I get to working on my notification script I'll read up a bit more about netcat. Thanks for the starting point, too!