-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Listing missing content #1
Comments
And the content is also empty: ❯ for i in {1..10}; do go-networkmanager-qrcode-generator -f plain -i $i; done
Got 37 connections
QR code should contain:
WIFI:S:"";;
Got 37 connections
QR code should contain:
WIFI:S:"";;
Got 37 connections
QR code should contain:
WIFI:S:"";;
Got 37 connections
QR code should contain:
WIFI:S:"";;
Got 37 connections
QR code should contain:
WIFI:S:"";;
Got 37 connections
QR code should contain:
WIFI:S:"";;
Got 37 connections
QR code should contain:
WIFI:S:"";;
Got 37 connections
QR code should contain:
WIFI:S:"";;
Got 37 connections
QR code should contain:
WIFI:S:"";;
Got 37 connections
QR code should contain:
WIFI:S:"";; Using networkmanager with plasma-nm if that matters. |
That's indeed a bit wrong. For me
The number of printed lines is also for me smaller than the printed number (
Obviously I assume you are running on a device with wifi connections. Could it be none of them is WPA/WPA2 Personal or WEP? Beyond these guesses I'm afraid there's not much debug output I added that would help us narrow down why your connections come out empty. Have you tried with the tui?
OR I recently discovered https://github.com/kokoye2007/wifi-qr which aims to provide the same functionality. I'm curious if that works for you. Those potential issues i listed should be the same as for wifi-qr but if that works for you, you at least get your qr codes, and we have a hint that the issue is something my tool should be able to handle |
https://github.com/dlenski/wifi2qr worked fine, I usually use WPA2-PSK |
I thought it would output the connection names ^^
The text was updated successfully, but these errors were encountered: