Hi stemsee,
Improvement is the instructions dialog, but for me there's still no profile created in /root/.wifi-connect/profiles (did the same as before by only filling in the password at the profile setting dialog), so could not make wifi connection.

Code:

root@live:~# '/usr/sbin/Wifi-TrayNet'
no eth1
no usb0
cat: /root/.wifi-connect/geometry/Instructions: No such file or directory
cat: /tmp/Wifi-TrayNet/exip: No such file or directory
cat: /root/.wifi-connect/geometry/Connect: No such file or directory
sed: -e expression #1, char 3: extra characters after command
cat: '/root/.wifi-connect/static/"UPC44685"': No such file or directory
xvkbd: no process found
chmod: cannot access '/tmp/Wifi-TrayNet/netsel': No such file or directory
cp: cannot stat '/tmp/Wifi-TrayNet/netsel': No such file or directory
Successfully initialized wpa_supplicant
Failed to open config file '/tmp/qrc', error: No such file or directory
Failed to read or parse configuration '/tmp/qrc'.

EDIT: Now first time start runs OK, but second time (after quit) doesn't:

Code:

root@live:~# '/usr/sbin/Wifi-TrayNet'
bash: cleanfinish: command not found
/tmp/traynetm: line 3: kill: (5610) - No such process
root@live:~# Wifi-TrayNet: no process found

There it hangs, after ctlr+c, then running Wifi-TrayNet again it runs ok.

As regards the problem you say you experience with profile creation please watch these videos made with weX. But the only other possibility I could imagine is that the first time I ran BionicDog I noticed no /tmp in / ... so to maintain that condition I moved all /tmp/Wifi-TrayNet to $HOME/.wifi-connect/Wifi-TrayNet ... even so I could not replicate the failure to create profiles.

Hi stemsee, tried your latest 3.7 deb but still no profile is made.
I test always from a pristine Bionicdog install, the (older) previous version (as I see that you use that also (nice video's, btw )).
I think I do everything right, first left-click on the icon, wait a while, select my network and then at the profile dialog I only type my password and select busybox udhcpc ....
Output:

Code:

root@live:~# '/usr/sbin/Wifi-TrayNet'
no eth1
no usb0
Warning: Missing charsets in String to FontSet conversion
sed: -e expression #1, char 3: extra characters after command
cat: '/root/.wifi-connect/static/"UPC44685"': No such file or directory
xvkbd: no process found
chmod: cannot access '/root/.wifi-connect/Wifi-TrayNet/netsel': No such file or directory
cp: cannot stat '/root/.wifi-connect/Wifi-TrayNet/netsel': No such file or directory
Successfully initialized wpa_supplicant
Failed to open config file '/tmp/qrc', error: No such file or directory
Failed to read or parse configuration '/tmp/qrc'.

Tried also "Initiate connection" and set the profile again, same result, no profile in /root/.wifi-connect/profiles .

EDIT: Wifi-Scanner works for me, created profile and connection made.
Just to mention: clicking on "Select Wifi Card" does nothing.

Select Wifi card menu option only works when two or more wireless cards are detected ... your system has only one so that has no effect. To see the wireless card-name being used is in the Configuration-&-Connection gui.

So what could be preventing profile creation for TrayNet but allowing creation for Scanner? and also not even creating netsel, and Scanner also uses netsel. I am baffled, so do you know what it is?

Select Wifi card menu option only works when two or more wireless cards are detected ... your system has only one so that has no effect

Ah, of course, you said that earlier.

Quote:

So what could be preventing profile creation for TrayNet but allowing creation for Scanner? and also not even creating netsel, and Scanner also uses netsel. I am baffled, so do you know what it is?
If you have time make a video similar to the one I did.

I have no idea, with one of the earlier versions it worked OK to create profile, apparently you changed something.
I will make video, probably tomorrow.

I thought I would see a selection including config editor 'geany', because in that case I found I got the same errors you posted. Yesterday I tried without changes and I got the errors too. Today I fixed the error when selecting config editor, and then just now I booted without changes and without installing or uninstalling anything I executed only the script from out of tree on sdb1, and everything worked, except connection, until I copied over hook scripts.

One thing I notice is that you selected dhc editor for 'busybox udhcpc....' that gets priority over the hardcocded argument, but without altering it it makes no difference and is not necessary.

Another thing is that if the same network name is selected in the tray menu then 'tail -fn0 /file' does not respond and does not get the gui opened, this is why it is necessary to 'initiate connection', I guess tail in aploop function, must be re-initialised after each read. (EDIT: fixed by auto sending a dummy AP, which is excluded, to monitored file after real AP selection activates gui)

Also, tried the same script in BionicPup without problems.

So even though on my system there was no obvious problem, yet it seems the priorities of arguments from the gui caused the errors ... so now the final test is to see if the small changes I made work on your system.

So here is only the script ... which you could run out of tree.Last edited by stemsee on Wed 04 Jul 2018, 04:59; edited 1 time in total

Hi stemsee, sorry, your latest script didn't work either.
But I know now, my ssid "UPC44685" is boycotted by Wifi-Traynet !!
No, seriously, I think it has to do with wpa, trying other networks (wpa2) will create a profile just fine, and after that when trying my ssid, the profile is created but with the ssid of the previous network inside profile config, oh well...difficult to explain, see video:
https://drive.google.com/open?id=193itrVvreagneJPbUXseG9b8rtZXx6Mc

It's not in the video, but just now I tried creating another profile (from my neighbor from which I know he has also wpa) and it didn't work either, so must be a wpa thing, I guess.

EDIT: I tried some earlier versions and with 3.4 it works ok to create a (wpa) profile, and since you implemented the read-only fields the problem began (3.5).

Not sure what you mean. With the 3.4. version, yes, it did connect.
What you saw on the last screencast was just creating (wpa2) profiles from other networks (not mine) to show that it works for profile creating, but no connection made.

Quote:

Maybe should only create profile after successful connection!

Yes, maybe good, but if it makes things even more complicated, there's again the risk of creating new bugs, I'd say .

and post the output for your network. Le's try see if the ciphers or type are matched with the network block in the wpa profile.

Creating the profile after connection is just a matter of copying either qrc or netsel to profiles/$ssid+$bssid after the icon turns yellow (local connection) or green (internet), instead of after closing the password gui. That actually makes more sense. What could possibly go wrong!?

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum