[GH-ISSUE #114] `3ginfo.sh`: Error `awk: cmd. line:1: Unexpected token`. LuCI-site: `JSON.parse: bad control character in string literal at line 7 column 15 of the JSON data`. #90

New issue

Open

opened 2026-03-04 11:58:32 +03:00 by kerem · 1 comment

kerem commented

2026-03-04 11:58:32 +03:00

Owner

Originally created by @dreirund on GitHub (Mar 4, 2025).
Original GitHub issue: https://github.com/4IceG/luci-app-3ginfo-lite/issues/114

Ahoj,

I have installed your package (version 1.0.75-r20250126) on OpenWRT (23.05.4, variant "FriendlyWRT").

There are two issue:

Running /usr/share/3ginfo-lite/3ginfo.sh prints an error message at the beginning:
```
awk: cmd. line:1: Unexpected token
```
Opening in LuCI the "Details" page of the package, /cgi-bin/luci/admin/modem/3ginfo-lite/3gdetail`, there are two error messages and no information:

SyntaxError
JSON.parse: bad control character in string literal at line 7 column 15 of the JSON data

and

Error: JSON.parse: bad control character in string literal at line 7 column 15 of the JSON data

Screenshot:

Regards!

Originally created by @dreirund on GitHub (Mar 4, 2025). Original GitHub issue: https://github.com/4IceG/luci-app-3ginfo-lite/issues/114 Ahoj, I have installed your package (version 1.0.75-r20250126) on OpenWRT (23.05.4, variant "FriendlyWRT"). There are two issue: * Running `/usr/share/3ginfo-lite/3ginfo.sh` prints an error message at the beginning: ``` awk: cmd. line:1: Unexpected token ``` * Opening in LuCI the "Details" page of the package, /cgi-bin/luci/admin/modem/3ginfo-lite/3gdetail`, there are two error messages and no information: > **SyntaxError** > `JSON.parse: bad control character in string literal at line 7 column 15 of the JSON data` and > Error: JSON.parse: bad control character in string literal at line 7 column 15 of the JSON data Screenshot: --- ![Image](https://github.com/user-attachments/assets/00a33511-7302-4dc9-b448-a1955d098c55) --- Regards!

kerem commented

2026-03-04 11:58:33 +03:00

Author

Owner

@przemekp1 commented on GitHub (Apr 5, 2025):

U mnie to samo po przejściu z Openwrt 23.05.5 na 24.10
SyntaxError

JSON.parse: bad control character in string literal at line 50 column 12 of the JSON data

Error: JSON.parse: bad control character in string literal at line 50 column 12 of the JSON data
co to może być? może jakiejś biblioteki json brakuje ?

@przemekp1 commented on GitHub (Apr 5, 2025): U mnie to samo po przejściu z Openwrt 23.05.5 na 24.10 SyntaxError JSON.parse: bad control character in string literal at line 50 column 12 of the JSON data Error: JSON.parse: bad control character in string literal at line 50 column 12 of the JSON data co to może być? może jakiejś biblioteki json brakuje ?