I've updated my RM2 to v3.3.2.1666 and installed Toltec. After installing a few other packages, including changescrn to change the screen, the poweroff spash screen overlaps with the shutdown HUD, as can be seen in the image attached. This happens for the stock image and custom images.
Any idea on what could be causing this and how to fix it?
#Poweroff splash screen overlaps with shutdown HUD
1 messages · Page 1 of 1 (latest)
What other packages did you install?
@hexed kite
Hey, thanks for the quick reply, apologies for treating Discord as a slow chat...
Well, the first time I noticed it happening was only Toltec and changesscrn if I'm not mistaken. Maybe Doom was already installed and Oxido as well, but I'm not sure.
I ended up removing Oxide and installing Remux, after noticing the bug I have installed fingerterm and rmfakecloud-proxy.
Could you provide the full list of installed packages? opkg list-installed
Yes, here it is:
bash - 5.2.15-1
bash-completion - 2.11-3
ca-certificates - 20230311-1
changescrn - 1.0.0-2
coreutils - 9.3-1
coreutils-stat - 9.3-1
coreutils-tsort - 9.3-1
display - 1:0.0.33-1
doomarkable - 0.4.1-2
entware-opt - 227000-3
entware-rc - 0.1-1
entware-release - 2024.02-1
entware-upgrade - 1.0-1
findutils - 4.9.0-1a
fingerterm - 1.3.5-15
grep - 3.11-1
ip-full - 4.4.0-10b
kernelctl - 0.1-7
launcherctl - 0.0.1-2
libatomic - 8.4.0-11
libbz2 - 1.0.8-1a
libc - 2.27-11
libgcc - 8.4.0-11
libncurses - 6.4-2a
libncursesw - 6.4-2a
libnl-tiny - 2023-12-05-965c4bf4-1
libopenssl - 3.0.13-1
liboxide - 2.7-7
libpcre2 - 10.42-1
libpthread - 2.27-11
libpython3 - 3.11.7-1
libreadline - 8.2-1
librt - 2.27-11
libsentry - 0.5.0
libsqlite3 - 3410200-1
libssp - 8.4.0-11
libstdcpp - 8.4.0-11
libuuid - 2.39.3-1
linux-stracciatella - 5.4.70.4-1
locales - 2.27-9
micro - 2.0.13-1
opkg - 2022-02-24-d038e5b6-2
procps-ng - 4.0.4-1
procps-ng-pgrep - 4.0.4-1
procps-ng-ps - 4.0.4-1
python3-base - 3.11.7-1
python3-email - 3.11.7-1
python3-light - 3.11.7-1
python3-readline - 3.11.7-1
python3-sqlite3 - 3.11.7-1
python3-unittest - 3.11.7-1
python3-urllib - 3.11.7-1
python3-uuid - 3.11.7-1
python3-xml - 3.11.7-1
remux - 0.3.0-4
rm2-suspend-fix - 0.0.0-3
rm2fb-client - 1:0.0.33-1
rmfakecloud-proxy - 0.0.3-5
terminfo - 6.4-2a
toltec-base - 1.3-4
toltec-bootstrap - 0.4.1-1
toltec-completion - 0.4.0-2
toltec-deletions - 0.1-4
wg-quick - 1.0.20210914-1
wget-ssl - 1.21.4-1
wireguard-tools - 1.0.20210914-3
xochitl - 0.0.0-20
zlib - 1.3.1-1
zoneinfo-asia - 2024a-1
zoneinfo-core - 2024a-1
zoneinfo-europe - 2024a-1
Did you install a launcher before, or after this happened?
I'll also be getting you a command to test on your device in a little while. I'm just working through getting started with my day before I'll be at my computer
I think before, but I'm not sure
no rush, don't worry
Okay run remarkable-shutdown. It should display the power off screen. Don't worry, the device isn't powered off, just run launcherctl stop-launcher && launcherctl start-launcher restart things and get the display updated again.
Does the shutdown screen display properly?
Yeah remarkable-shutdown shows the poweroff screen just fine.
restarting the launcher, however, does not
it shows a blend between xochitl and the poweroff screen
refreshing the screen solves it
That shouldn't be the case. odd
What do you mean by refreshing the screen?
Also, what does launcherctl status output?
sending it to the suspended screen and turn it back on
Okay
Restarting the launcher should have done that properly
What was the console output when you restarted it?
Although remux may have left xochitl running
# launcherctl status
Launcher: remux
Status: running
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
find: ‘/etc/draft’: No such file or directory
Apps: 2 running find: ‘/etc/draft’: No such file or directory
3 installed
of launcherctl stop-launcher && launcherctl start-launcher? None.
Of the suspending and turning it back on was done manually, not in the terminal.
There should be console output when you run it
remarkable-shutdown does, not the stopping and starting.
Could you open an issue on the toltec repository about the find: ‘/etc/draft’: No such file or directory output
Right, but launcherctl should have output for those commands
sure, but I though I had only remux installed, so draft shouldn't be queried in any way, right?
remux reads draft config. That's besides the point though, there is unexpected output.
okay, I'll open a new ticket there
Should the issue be specifically about the output of launcherctl status , the no output of stop/start-launcher or about the overlapping of the poweroff screen?
Just the ticket for launcherctl status
As for the overlapping, I'm unable to replicate, so I'm still trying to sort out what the issue is
If you switch back to xochitl as your launcher, does it still have the issue?
launcherctl switch-launcher --start xochitl
No in that case everything is fine. I'm going to set it back to remux and see if it happens again.
Well I was trying to check if it only happens to remux or not but now I can't seem to connect to my Wi-Fi after a reboot xD
Maybe it's unrelated, just give me a minute
Sorry my Wifi is having issues
Anyways, I've switched back to remux, powered off, poweroff screen is fine, after booting running launcherctl status it reveals the same error and powering off reveals the "corrupted" shutdown screen
So this appears to be a remux bug. You should report the issue to the remux upstream repository
with xochitl as the launcher there's no error
alrighty then, I'll make the report there.
Just to clarify, the launcherctl issue should be opened on toltec, not remux
launcherctl is not remux
@hexed kite
Ah dammit, well I guess I'll move it there xD
Just the launcherctl issue
There it is: https://github.com/toltec-dev/toltec/issues/881
GitHub
Describe the issue Running launcherctl status when remux is set as the default launcher (doesn't happen if xochitl is the default) gives the following error # launcherctl status Launcher: remux...
I had already open one on remux repository so I closed it and mentioned that over there, if somebody is to have a similar issue.
Hopefully the bug report is clear enough
do say if you need some extra information from my side
You were reporting a completely different issue on remux
so don't close it
Ah, okay, so you're only going for the issue in launcherctl. I assumed these two to be related, hence opening only one issue in one repository.
Thanks once again!
They are unrelated
That's why I asked you two open an issue twice, once for launcherctl, and then another for remux
this