Activity for wseverin
-
wseverin posted a comment on discussion Feature Requests
I'm guessing that the behavior you'd like to see is a button (or similar) to hide all of the currently displayed attach points, both in the list and in the charts. A similar behavior would be would be to have a button to clear and forget all of the found attach points, effectively starting from scratch, but of course the list and charts would fill up again with all of the previously cleared entries. Am I correct that the first behaviour is the one you're looking for, and not the second?
-
Version 3.6 now latest, OK, so I've been really bored. Plus, my neighbor just installed a mesh network with 16(!) attach points!. Dual band, so 8 nodes. One for each room in his house plus a bathroom or two. (What is he thinking!?) Another neighbor has a mesh as well, so now able to see if LinSSID can decipher mesh. This release makes an attempt to decipher mesh according to 802.11s. WDS is still up in the air.
-
I got bored and made another couple of tweeks to LinSSID. Version 3.5 is now current. What changed: Vendor database now includes not just IEEE MAC large block subscribers, but also medium and small block subscribers. The trick was to find a way to match 6-nibble, 7-nibble, and 9-nibble MAC address groups in a binary chop search. SSID display now shows "<hidden>" instead of just blank for hidden attach points.
-
Version 3.4 is now current. This is a bug-fix revision. It fixes the issue that began in version 3.1, where the necessity of using Policykit caused the preferences and datalog files to be stored in /root and owned by root. Now, using the standard .desktop launch with pkexec, the preferences and and datalog files are placed in $HOME and owned by $USER as it should be. Also fixed is the vendor database file which in version 3.3 had some extraneous characters at the end of the vendor names that played...
-
Dear Vítězslav, Thank you for the report. I will look into it immediately. Edit 20180613_0103 UTC: I have gone through my stack of WiFi USB adapters and all work with LInSSID with two adapters active. I can not reproduce the problem. If you will launch LinSSID in a terminal window with: linssid-pkexec 2>&1 and report any error messages it will be helpful. Thanks! -Warren
-
Dear Vítězslav, Thank you for the report. I will look into it immediately.
-
Latest LinSSID is 3.3. This version adds the ability to select table font size within a limited range. A small feature, but a lot of work. You wouldn't believe.
-
Latest LinSSID is 3.2. The channel plots now place a marker for the control channel on the plots of APs of 40 MHz or greater bandwidth. Also a small change to fix a potential but unverified memory leak.
-
I have just posted a significant update to LinSSID, now version 3.1. I hope to have fixed most of the hang problems. From the README file: - Big change - now requires polkit (policykit) authentication. No way around this as debian/ubuntu/etc has emasculated su and sudo. A step backward IMHO. Now the whole app must run as root. So, all of the prefs and log files are now in /root and are owned by root. And, the whole app must run as root instead of just well-tested system parts. - Major rewrite of...
-
I have just posted a significant update to LinSSID, now version 3.1. I hope to have fixed most of the hang problems. From the README file: Big change - now requires polkit (policykit) authentication. No way around this as debian/ubuntu/etc has emasculated su and sudo. A step backward IMHO. Now the whole app must run as root. So, all of the prefs and log files are now in /root and are owned by root. And, the whole app must run as root instead of just well-tested system parts. Major rewrite of the...
-
I have just posted a significant update to LinSSID, now version 3.1. I hope to have fixed most of the hang problems. From the README file: Big change - now requires polkit (policykit) authentication. No way around this as debian/ubuntu/ has emasculated su and sudo. A step backward IMHO. Now the whole app must run as root. So, all of the prefs and log files are now in /root and are owned by root. And, the whole app must run as root instead of just well-tested system parts. Major rewrite of the synchronization...
-
I have just posted a significant update to LinSSID, now version 3.1. I hope to have fixed most of the hang problems. From the README file: Big change - now requires polkit (policykit) authentication. No way around this as debian/ubuntu/ has emasculated su and sudo. A step backward IMHO. Now the whole app must run as root. So, all of the prefs and log files are now in /root and are owned by root. And, the whole app must run as root instead of just well-tested system parts. Major rewrite of the synchronization...
-
I have just posted a significant update to LinSSID, now version 3.1. I hope to have fixed most of the hang problems. From the README file: Big change - now requires polkit (policykit) authentication. No way around this as debian/ubuntu/ has emasculated su and sudo. A step backward IMHO. Now the whole app must run as root. So, all of the prefs and log files are now in /root and are owned by root. And, the whole app must run as root instead of just well-tested system parts. Major rewrite of the synchronization...
-
I have just posted a significant update to LinSSID, now version 3.1. I hope to have fixed most of the hang problems. From the README file: Big change - now requires polkit (policykit) authentication. No way around this as debian/ubuntu/ has emasculated su and sudo. A step backward IMHO. Now the whole app must run as root. So, all of the prefs and log files are now in /root and are owned by root. And, the whole app must run as root instead of just well-tested system parts. Major rewrite of the synchronization...
-
I've been a frequent user of zenity and just a few days ago decided to see what I could do with yad. Here is the fruit – a simple random password generator that lets the user pick symbol sets and some constraints. I'm sure there are better ways to do some of the things here, but it may be a helpful example for future yad users. This works with yad 0.38.2 on Ubuntu 17.10 (Artful). 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43...
-
The first question is, have you disconnected your laptop from your WiFi attach point when you initiate LinSSID? This is important. Scans, as from LinSSID, will take up nearly 100% of the availability of your WiFi card. Meanwhile, if your laptop is connected to an attach point, other processes are trying to do periodic communications with their mother ships. In this case queues get backed up and not all WiFi drivers and versions of the OS handle this well. So, if you've not done so, disconnect your...
-
Version 2.9 is released. (Version 2.8 was never released.) This new version is a...
-
This is true. LinSSID was designed to alternatively be launched with sudo or gksudo,...
-
I hope the problem has been merely some silliness between the wifi card and its driver....
-
Just to let you know that the next revision is well underway. Linssid has NOT gone...
-
Thanks for you help in squashing bugs in Linssid!! Yes, Linssid works on x386 as...
-
It's too bad the backtrace doesn't go farther back. It tells us that the problem...
-
Thanks for the tip. I will incorporate it into the next release. That's underway...
-
What happens on your system if you just comment out (or delete) the #include <QtWidgets>...
-
Sorry for tardy response. I'm on the road for a few weeks. Happy to hear the password...
-
Odd behavior. I'm beginning to wonder if maybe there are two compounding problems;...
-
Hi, Jack, A few things to try: 1) The preferred way to run LinSSID is as a user process,...
-
2014-08-31: I am beginning development on version 2.8. The purpose is to convert...
-
I am beginning development on version 2.8. Hopefully it will include reporting on...
-
What distribution and version of Linux are you running? Also, what card or USB device...
-
Version 2.7 is now released. This (hopefully) fixes a problem with the program hanging...
-
This has been reported by some folks previously but I could never get it to happen...
-
There remain some outstanding issues with cards and USB devices that just don't seem...
-
Version 2.6 is released. This version fixes a potential bug in the interface discovery...
-
So far I've been avoiding unnecessary complexity. However, if there are folks who...
-
The Linux open source community is a beautiful thing.
-
There are a few small bug fixes and minor features added, but if 2.1 works OK then...
-
Version 2.5 is up there. Thanks a ton, Alex. And Darkstrike, please let me know if...
-
Try using your favorite package manager to install libboost-regex, version 1.54 or...
-
WOW! Thanks, Alex. Looks like zsh works differently from most of the other shells....
-
Hi, Alex, This is very interesting. I want to find the problem and fix it. Which...
-
Hello, Aliaksandr, Thank you very much for taking a look at the code. I greatly respect...
-
I have just posted LinSSID 2.4. This is identical source code to version 2.3, and...
-
Version 2.3 just posted. Give it a try. Also make note of the comments on the status...
-
I have just posted LinSSID 2.3. This version (hopefully) fixes problems with some...
-
One of the RTL8187SE cards came in the mail today and I tested it and its driver....
-
You don't need to build from source. The distributed binaries should work on your...
-
Hi, Darkstrike, Just checking out what might be causing the problem. It looks like...
-
Yeah. That's why I put in the "nap time" slider. It seems that depending on the wifi...
-
Hi, Al, Can you be more specific what happens when LinSSID "crashes"? Does it crash...
-
I have just posted the version 2.2 update. The source and deb files are available...
-
Just to let you know, I am working on an updated version. The purpose of the next...
-
Hummm. LinSSID doesn't do anything different between 2.4G and 5G connections. Well,...
-
4.8 should be just fine. I've built it many times on 4.8 and 4.8.1. Again, if the...
-
Linssid is designed and tested with QT4, as that is the most widely distributed version....
-
Find in files... enable selection of grep -P instead of -E option
-
That is most odd. The really odd piece is that it appears to be segfaulting in libqwt....
1
