Skip to content
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.

Sign up for GitHub

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

Jump to bottom

various "printf: x%: not completely converted" errors #8

Open
ralsei opened this issue Jun 29, 2016 · 3 comments · May be fixed by #11
Open

various "printf: x%: not completely converted" errors #8

ralsei opened this issue Jun 29, 2016 · 3 comments · May be fixed by #11

Comments

@ralsei
Copy link

ralsei commented Jun 29, 2016 

λ d /etc/wiconfig iwm0
doas ([email protected]) password: 
Currently connected to <SSID>.
Would you like to connect to a different network (y/n)? y
Performing wireless scan...
printf: 79%: not completely converted
printf: 64%: not completely converted
printf: 46%: not completely converted
printf: 43%: not completely converted
printf: 43%: not completely converted
printf: 41%: not completely converted
printf: 38%: not completely converted
printf: 31%: not completely converted
printf: 31%: not completely converted
printf: 29%: not completely converted
printf: 26%: not completely converted
printf: 26%: not completely converted
printf: 25%: not completely converted
printf: 25%: not completely converted
printf: 23%: not completely converted
printf: 23%: not completely converted
printf: 22%: not completely converted
printf: 17%: not completely converted
printf: 11%: not completely converted
<SSID> found.  Would you like to reconnect (y/n)?
@brycied00d
Copy link
Member

I just tested this running the latest current and wasn't able to reproduce your issue. Could you provide a few more details:

  1. OpenBSD release you're running
  2. The output from ifconfig iwm0 scan on your system.

It's possible that there's an SSID around you that's got some funky characters that's breaking up a split, or something else "funny" about ifconfig's scan output in your release.

@brycied00d
Copy link
Member

After a bit of coincidental investigation (related to a project of @qbit's) I understand now that ifconfig scan will output network signal strength in % if the interface driver knows/has the maximum RSSI of the device. If the maximum RSSI is not known to the driver, then ifconfig scan shows signal strength in the relatively absolute dBm.

Sounds like wiconfig needs to be adjusted to handle both cases cleanly, escaping % when passing the string through printf.

@ralsei
Copy link
Author

ralsei commented Jul 22, 2016

Yes, I noticed that when switching from my laptop's built-in iwm card to a run USB dongle.

@brycied00d brycied00d mentioned this issue Apr 14, 2017
Open
@tomryanx tomryanx linked a pull request Dec 10, 2017 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

handle relative signal strength
2 participants
@brycied00d @ralsei