[Solved] Bad Xinit Command Broke Proteus

Get help with XFCE specific problems
Post Reply
johnywhy
Samurai
Samurai
Posts: 108
Joined: 29 Mar 2017, 17:26
Distribution: Kiosk
Location: Cali

[Solved] Bad Xinit Command Broke Proteus

Post#1 by johnywhy » 03 Sep 2018, 08:10

[this question was asked elsewhere, and solved. I add the solution below]

heh, i tried xinit.
/etc/X11/xinit/xinitc -> /etc/X11/xinit/xinitrc.xfce

Now i cannot login to xfce :shock:
i get the login screen, but when i enter username/password, a command screen flashes for a second, and then i'm back at the login screen. =@
any suggestions?

-----
ncmprhnsbl wrote:
02 Sep 2018, 08:01
can you access the root account?
if not, can you access another tty ? ( clt+alt+F1(or F<2,3,4,5,6>)
otherwise reboot in"Alway Fresh" mode and if your changes are a directory, you can edit them directly and undo what you did..
i think this is all i did.
/etc/X11/xinit/xinitc -> /etc/X11/xinit/xinitrc.xfce
first i exited the desktop to a command prompt, before executing it.
ncmprhnsbl wrote:
02 Sep 2018, 08:01
xinitrc is already linked to /etc/X11/xinit/xfce.xinitrc
you mean the code i executed above links xinitrc to xinitrc.xfce?
And it was already that way? Then why would it break the OS?
How to undo what i did, if what i did was already that way? :crazy:

Image

-----

i don't know what or where the offending file is. are you saying my dir should look the same as your example? and that's how i can identify the offending file?

not sure i have a 'changes' dir, i'm using a dat-file. will check now.

Update: i can't find a 'changes' directory. I'm getting same output as you:

Image

-----

Ok, I found that dir. Dev is most recent.

i found the suspicious symlink in changes/mnt:

Code: Select all

/mnt/live/memory/changes/mnt# ll
total 0
lrwxrwxrwx 1 root root 21 Sep  2 21:05 isoloop -> /mnt/live/mnt/isoloop/
drwxr-xr-x 2 root root 40 Sep  2 21:05 live/
drwxr-xr-x 2 root root 40 Sep  2 21:05 sda1/
drwxr-xr-x 2 root root 40 Sep  2 21:05 sda2/
drwxr-xr-x 2 root root 40 Sep  2 21:05 sda5/
drwxr-xr-x 2 root root 40 Sep  2 21:05 sda6/
drwxr-xr-x 2 root root 40 Sep  2 21:05 sdb1/
i deleted everything in the changes dir since my system broke. Is that how to roll back the changes?

still can't boot Porteus. Getting same guest login screen.

-----

Even without AlwaysFresh, I can boot to login screen. Then CTRL-ALT-F1 to get command prompt.

So, is AlwaysFresh still needed for my roll-back?
no, if you feel you don't need a gui..
tip: mc (midnightcommander) provides a handy console file manager.

THX
Linux porteus 4.16.3-porteus #1 SMP PREEMPT - x86_64 Intel(R) Pentium(R) Dual CPU T2310 @ 1.46GHz GenuineIntel GNU/Linux

johnywhy
Samurai
Samurai
Posts: 108
Joined: 29 Mar 2017, 17:26
Distribution: Kiosk
Location: Cali

[Solved] Bad Xinit Command Broke Proteus

Post#2 by johnywhy » 03 Sep 2018, 08:17

Solution provided by Ed_P

You need to boot Porteus in Always Fresh mode, mloop the save.dat file, edit/delete the change you don't want, then uloop the save.dat file and reboot with the updated save.dat file.

Should this not work you can restore your save.dat file from it's backup, (you do make backups before you make changes right? :D ) or create a new one and start all over. :x
Linux porteus 4.16.3-porteus #1 SMP PREEMPT - x86_64 Intel(R) Pentium(R) Dual CPU T2310 @ 1.46GHz GenuineIntel GNU/Linux

User avatar
ncmprhnsbl
DEV Team
DEV Team
Posts: 1553
Joined: 20 Mar 2012, 03:42
Distribution: 4.0-64bit all-DE+more
Location: australia
Contact:

[Solved] Bad Xinit Command Broke Proteus

Post#3 by ncmprhnsbl » 03 Sep 2018, 09:24

was about to get around to moving those posts :D but since you have summarized the entire exchange, i just cleaned up the other topic..
future reference: moderators can move posts :happy62:
Forum Rules : http://forum.porteus.org/viewtopic.php?f=35&t=44

Post Reply