Closed je-vv closed 6 months ago
CarterLi
commented
6 months ago Terminal: screen
It is expected. For other terminal multiplexor like tmux you can't detect the real terminal. For screen you can detect the real terminal because screen doesn't use daemon process, I just report screen to be consistant with other multiplexors.
CarterLi
commented
6 months ago Also, fastfetch it's not detecting wifi
What does ifconfig print?
je-vv
commented
6 months ago Terminal: screen
It is expected. For other terminal multiplexor like tmux you can't detect the real terminal. For screen you can detect the real terminal because screen doesn't use daemon process, I just report screen to be consistant with other multiplexors.
Ohh that's what you prefer, so on purpose. Not that I agree, but I understand then.
je-vv
commented
6 months ago Also, fastfetch it's not detecting wifi
What does
ifconfigprint?
in-wired-0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 38:22:e2:2a:bb:96 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 memory 0xe9200000-e9220000
in-wireless-0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet <...> netmask <...> broadcast <...>
inet6 <...> prefixlen 64 scopeid 0x20<link>
ether <...> txqueuelen 1000 (Ethernet)
RX packets 18829351 bytes 20986377019 (19.5 GiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10052341 bytes 1618699492 (1.5 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 177217 bytes 18819411 (17.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 177217 bytes 18819411 (17.9 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
...Those are the fixed names assigned to the interfaces, the NIC/eth one and the wireless one... Not sure if expecting only certain pattern in the wireless interface to detect wifi...
CarterLi
commented
6 months ago Not sure if expecting only certain pattern in the wireless interface to detect wifi...
No we don't.
What does iw dev and ls -l /sys/class/net/*/phy80211 print?
je-vv
commented
6 months ago % iw dev
phy#0
Unnamed/non-netdev interface
wdev 0x2
addr <...>
type P2P-device
Interface in-wireless-0
ifindex 3
wdev 0x1
addr <...>
type managed
channel 153 (5765 MHz), width: 80 MHz, center1: 5775 MHz
txpower 22.00 dBm
multicast TXQ:
qsz-byt qsz-pkt flows drops marks overlmt hashcol tx-bytes tx-packets
0 0 0 0 0 0 0 0 0
% ls -l /sys/class/net/*/phy80211
lrwxrwxrwx 1 root root 0 Apr 26 02:53 /sys/class/net/in-wireless-0/phy80211 -> ../../ieee80211/phy0/Can you try the latest dev build? you may download it here: https://github.com/fastfetch-cli/fastfetch/actions/runs/8847532032
CarterLi
commented
6 months ago No more information, closing
je-vv
commented
6 months ago wow, @CarterLi that was just too fast, hahaha. I didn't have time to test a later build before.
I build/install the AUR fastfetch-git package, which is currently using head of the dev branch:
git+https://github.com/fastfetch-cli/fastfetch.git#branch=devAnd guess what, wifi does work with it:
{
"type": "Wifi",
"result": [
{
"inf": {
"description": "in-wireless-0",
"status": "up"
},
"conn": {
"status": "",
"ssid": "<my_ssid>",
"bssid": "<my_bssid>",
"protocol": "",
"security": "",
"signalQuality": 88.0,
"rxRate": null,
"txRate": null
}
}
],
"stat": 16
},Strange it doesn't show up when calling fastfetch, but now I see wifi and its signal strenght is detected...
Thanks !
CarterLi
commented
6 months ago Please try fastfetch -s wifi --show-errors
je-vv
commented
6 months ago % fastfetch -s wifi --show-errors
' Wifi: <my_ssid>
'o'
'ooo'
'ooxoo'
'ooxxxoo'
'oookkxxoo'
'oiioxkkxxoo'
':;:iiiioxxxoo'
`'.;::ioxxoo'
'-. `':;jiooo'
'oooio-.. `'i:io'
'ooooxxxxoio:,. `'-;'
'ooooxxxxxkkxoooIi:-. `'
'ooooxxxxxkkkkxoiiiiiji'
'ooooxxxxxkxxoiiii:'` .i'
'ooooxxxxxoi:::'` .;ioxo'
'ooooxooi::'` .:iiixkxxo'
'ooooi:'` `'';ioxxo'
'i:'` '':io'
'` `'
%There my ssid shows up, :), no additional info, but it shows up...
General description of bug:
Notice that I'm using alacritty + screen as multiplexor, and I have set $TERM to
screen-256color, not sure if fastfetch is based on that to output screen as the terminal.On neofetch this doesn't happen, it properly detects alacritty:
Also, fastfetch it's not detecting wifi:
Though I don't use network manager, neither I use iw/iwd... I just use plain wpa_supplicant and dhcpcd.
What should happen: Alacritty should have been the output for
Terminal. And I don't know what wifi shows, but I guess the ESSID used and perhaps its signal strenght...Fastfetch version used: 2.10.2.
Did it work in an older version: no
Where did you get the binary: Archlinux repo
Screenshot:
The content of the configuration file you use (if any):
Output of
fastfetch -c ci.jsonc --format json: fastfetch_jsonc.txtOutput of
fastfetch --list-features: