CaptainBloodz
CaptainBloodz
Deadly busy for the next 24h, will do my best via console disconnection method All I can say now is that there is a stack displayed at shutdown. I expect...
Here's the thingie: Did it via following sequence nmcli r wifi on nmcli r wifi off So I extracted data properly there could be some log from the 1st command...
FYI, the whole Xorg stack seems stuck and could not be restarted by stopping and restarting the xdm service (gentoo here), but terminal/console survived. Le 26/06/2015 07:13, Luc Pierard de...
Identical with 4.1.0, 4,1,1, 4,1,1-r1 Any news?
Unfortunately 68.0.2 has gone out of the package tree for a while now. There're clues to bring it back though. Surely will provide results if I do. Thks 4 ur...
I don't know how to debug swayidle. Anyhow here's the original /sway/config snippet: exec swayidle timeout 3600 '~/apps/grim/grim-master/build/grim /tmp/screen_locked.png && convert /tmp/screen_locked.png -scale 5% -scale 2000% /tmp/screen_locked.png && swaylock -f...
switching to "exec swayidle timeout 1000..." works fine, same command line length.
> I had similar issues on void, I think due to conflict with agetty. By default, greetd runs the greeter on tty1, where I duplicate your issue when I also...
Cancelling c1:12345:respawn:/sbin/agetty 38400 tty1 linux --noclear in /etc/inittab didn't change anything here.
Thks 4 ur prompt reply. At least I will stop to fiddle around kernel configuration. Warning remains in master branch... Any reason to keep it?