You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am not sure if this is not a supported command anymore or I am doing something wrong. This is what I get when I try to clear the display.
pi@pwnagotchi:~ $ sudo pwnagotchi --clear
[2023-09-30 10:24:32,148] [INFO] gps plugin loaded for /dev/ttyS0
[2023-09-30 10:24:32,148] [INFO] Session-stats plugin loaded.
[2023-09-30 10:24:32,153] [INFO] GPIO Button plugin loaded.
[2023-09-30 10:24:32,154] [INFO] Added command: touch /root/.pwnagotchi-auto && systemctl restart pwnagotchi to GPIO #20
[2023-09-30 10:24:32,156] [INFO] Added command: shutdown -h -r now to GPIO #16
[2023-09-30 10:24:32,158] [INFO] [led] plugin loaded for /sys/class/leds/led0/brightness
[2023-09-30 10:24:32,159] [INFO] Added command: shutdown -h now to GPIO #19
Error: Read failed
[2023-09-30 10:24:32,213] [INFO] initializing waveshare v3 display
[2023-09-30 10:24:32,221] [INFO] BT-TETHER: Successfully loaded ...
[2023-09-30 10:24:33,735] [INFO] clearing the display ...
[2023-09-30 10:24:34,378] [ERROR] error while running gps.on_ui_update : cannot schedule new futures after shutdown
[2023-09-30 10:24:34,379] [ERROR] cannot schedule new futures after shutdown
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/pwnagotchi/plugins/init.py", line 95, in one
executor.submit(locked_cb, *locked_cb_args)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 151, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
[2023-09-30 10:24:34,384] [ERROR] error while running ups_lite.on_ui_update : cannot schedule new futures after shutdown
[2023-09-30 10:24:34,385] [ERROR] cannot schedule new futures after shutdown
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/pwnagotchi/plugins/init.py", line 95, in one
executor.submit(locked_cb, *locked_cb_args)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 151, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
[2023-09-30 10:24:34,387] [ERROR] error while running bt-tether.on_ui_update : cannot schedule new futures after shutdown
[2023-09-30 10:24:34,387] [ERROR] cannot schedule new futures after shutdown
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/pwnagotchi/plugins/init.py", line 95, in one
executor.submit(locked_cb, *locked_cb_args)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 151, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
[2023-09-30 10:24:35,408] [ERROR] error while running gps.on_ui_update : cannot schedule new futures after shutdown
[2023-09-30 10:24:35,409] [ERROR] cannot schedule new futures after shutdown
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/pwnagotchi/plugins/init.py", line 95, in one
executor.submit(locked_cb, *locked_cb_args)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 151, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
[2023-09-30 10:24:35,412] [ERROR] error while running ups_lite.on_ui_update : cannot schedule new futures after shutdown
[2023-09-30 10:24:35,413] [ERROR] cannot schedule new futures after shutdown
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/pwnagotchi/plugins/init.py", line 95, in one
executor.submit(locked_cb, *locked_cb_args)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 151, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
[2023-09-30 10:24:35,416] [ERROR] error while running bt-tether.on_ui_update : cannot schedule new futures after shutdown
The text was updated successfully, but these errors were encountered:
captclearleft
changed the title
pwnagotchi -clear returns errors.
pwnagotchi --clear returns errors.
Sep 30, 2023
I am not sure if this is not a supported command anymore or I am doing something wrong. This is what I get when I try to clear the display.
pi@pwnagotchi:~ $ sudo pwnagotchi --clear
[2023-09-30 10:24:32,148] [INFO] gps plugin loaded for /dev/ttyS0
[2023-09-30 10:24:32,148] [INFO] Session-stats plugin loaded.
[2023-09-30 10:24:32,153] [INFO] GPIO Button plugin loaded.
[2023-09-30 10:24:32,154] [INFO] Added command: touch /root/.pwnagotchi-auto && systemctl restart pwnagotchi to GPIO #20
[2023-09-30 10:24:32,156] [INFO] Added command: shutdown -h -r now to GPIO #16
[2023-09-30 10:24:32,158] [INFO] [led] plugin loaded for /sys/class/leds/led0/brightness
[2023-09-30 10:24:32,159] [INFO] Added command: shutdown -h now to GPIO #19
Error: Read failed
[2023-09-30 10:24:32,213] [INFO] initializing waveshare v3 display
[2023-09-30 10:24:32,221] [INFO] BT-TETHER: Successfully loaded ...
[2023-09-30 10:24:33,735] [INFO] clearing the display ...
[2023-09-30 10:24:34,378] [ERROR] error while running gps.on_ui_update : cannot schedule new futures after shutdown
[2023-09-30 10:24:34,379] [ERROR] cannot schedule new futures after shutdown
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/pwnagotchi/plugins/init.py", line 95, in one
executor.submit(locked_cb, *locked_cb_args)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 151, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
[2023-09-30 10:24:34,384] [ERROR] error while running ups_lite.on_ui_update : cannot schedule new futures after shutdown
[2023-09-30 10:24:34,385] [ERROR] cannot schedule new futures after shutdown
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/pwnagotchi/plugins/init.py", line 95, in one
executor.submit(locked_cb, *locked_cb_args)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 151, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
[2023-09-30 10:24:34,387] [ERROR] error while running bt-tether.on_ui_update : cannot schedule new futures after shutdown
[2023-09-30 10:24:34,387] [ERROR] cannot schedule new futures after shutdown
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/pwnagotchi/plugins/init.py", line 95, in one
executor.submit(locked_cb, *locked_cb_args)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 151, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
[2023-09-30 10:24:35,408] [ERROR] error while running gps.on_ui_update : cannot schedule new futures after shutdown
[2023-09-30 10:24:35,409] [ERROR] cannot schedule new futures after shutdown
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/pwnagotchi/plugins/init.py", line 95, in one
executor.submit(locked_cb, *locked_cb_args)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 151, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
[2023-09-30 10:24:35,412] [ERROR] error while running ups_lite.on_ui_update : cannot schedule new futures after shutdown
[2023-09-30 10:24:35,413] [ERROR] cannot schedule new futures after shutdown
Traceback (most recent call last):
File "/usr/local/lib/python3.7/dist-packages/pwnagotchi/plugins/init.py", line 95, in one
executor.submit(locked_cb, *locked_cb_args)
File "/usr/lib/python3.7/concurrent/futures/thread.py", line 151, in submit
raise RuntimeError('cannot schedule new futures after shutdown')
RuntimeError: cannot schedule new futures after shutdown
[2023-09-30 10:24:35,416] [ERROR] error while running bt-tether.on_ui_update : cannot schedule new futures after shutdown
The text was updated successfully, but these errors were encountered: