Can't log in on after editing tint2rc

mcfundash · 2012-11-19 06:27:41

So I was editing my tint2rc in order to add a bit more customization and part of that was to install an extra font (ttf-atarismall) to use. Everything seemed fine but then suddenly when I logged out to activate the font, I couldn't log in. I rebooted hoping that would fix it but when it started up again I couldn't log in. Slim shows the login page fine and all but after I put in my password it just resets showing the text tty login for a sec and then the username prompt again. I have no clue what could have caused this hoping someone can help me, thanks!

lwfitz · 2012-11-19 07:23:05

If I you Id reboot and from tty enter login info then

sudo nano /home/your_name/.config/openbox/autostart

and stop tint2 from autostarting by uncommenting tint2 with an #. Im not on openbox but it would be something like

change

tint2 &

to

#tint2 &

If you are able to reboot and then log in you know its a tint2 issue and then you can remove the font you installed and run tint2 from a terminal so you can see if it starts with any errors.

Also you can update your font by running

sudo fc-cache -f -v

then restarting whatever program you want that font to show up in

Hope this helps

mcfundash · 2012-11-19 07:47:28

Unfortunately that changed nothing at all, so it doesn't seem to be tint2, I was also messing with screensavers and thought it might be xscreensaver so I tried reinstalling that but it didn't help. Thanks for the commands though.

machinebacon · 2012-11-20 03:33:07

cat ~/.config/openbox/autostart

Post it here.

pvsage · 2012-11-20 06:28:09

lwfitz wrote:

sudo nano /home/your_name/.config/openbox/autostart

This is wrong. There are a (very) few cases where you'd want to edit something in your home directory as root, and this is not one of them. (It messes up the file's ownership & permissions.) Since logging in as {user} at a tty automatically takes you to /home/{user}, this is probably the most appropriate command:

nano .config/openbox/autostart

@mcfundash: I doubt a borken tint2rc would do anything worse than keep Tint2 from starting, but just for s#!ts & giggles, could you post your ~/.config/tint2/tint2rc as well?

Far more likely is a borken ~/.config/openbox/rc.xml; is there any chance you changed this as well? Please post it.

Sary · 2012-11-20 07:46:16

I would look in ~/.xsession-errors , as well.

lwfitz · 2012-11-20 08:01:54

pvsage wrote:

lwfitz wrote:
sudo nano /home/your_name/.config/openbox/autostart
This is wrong. There are a (very) few cases where you'd want to edit something in your home directory as root, and this is not one of them. (It messes up the file's ownership & permissions.) Since logging in as {user} at a tty automatically takes you to /home/{user}, this is probably the most appropriate command:
nano .config/openbox/autostart

Yeah your absolutely right and I know better than that. I shouldve slept than posted tongue Thanks for the correction buddy.

As far as a broken tint2 causing issues with x starting, I had exactly that happen thats why I went to it first. I agree that it should just cause tint2 not to start but I had a simple typo that caused all kinds of crazy crap cool If it can be broken Ill break it!

lwfitz · 2012-12-04 08:58:25

Did this ever get figured out? Something very similar just happened to me. I was editing tint2 and when I saved my config everything froze and I had to hard reboot.
Upon reboot everything looked OK but slim won't start correctly its just a black screen and nothing else.

dura · 2012-12-04 09:03:19

Can you ctrl + alt + f1 to get to tty? If you can, login from there, then type startx

Your default tint2 config will be in /etc/skel/.config

Last edited by dura (2012-12-04 09:04:07)

lwfitz · 2012-12-04 09:26:23

Does nothing. Screen just stays black. I have stopped tint2 from starting so if it was a tint issue I should be able to log in. I'll try editing tint from recovery and then star x from there and let you know what it does. Thanks

Edit: thanks dura I'm just gonna try to figure this out tomorrow.

Last edited by lwfitz (2012-12-04 09:38:25)

dura · 2012-12-04 09:51:02

There isn't much to figure out with it really... Are you sure you haven't bodged your rc.xml?

CBizgreat! · 2012-12-04 13:21:26

+1 Pvsage and Dura ...

My guess ... whatever you borked can be unborked by logging into another tty and copying the default files for openbox or tint2 ( whichever you may've messed up.) to replace the ones in your /home/username. Recently seen someone saying the default files in #! are kept in something like /etc/skel, as they are in many distro's I believe. This thread is discussing something very similar.

Meant to do a babble how to on this carp. Aka: Using a diff tty and copying ( cp) over default config files to unbork. Someone can even of course use a different tty login and simply correct the stuff they messed up from cli ( command line) w/o need of resorting to restoring default. My guestimation ... often enough restoring the default config files is just quicker and/or easier. In other words blahblahblahblah ...

Would try to explain this madness better BUT ... a: I'm highly intoxicated atm + b. A lazy person ... read link and perhaps it will bring you joy ? tongue

Vll! smile

Last edited by CBizgreat! (2012-12-04 13:37:33)

dura · 2012-12-04 14:01:00

^ Yip- default rc.xml is in /etc/skel/.config/openbox

Default tint2rc config is in /etc/skel/.config/tint2

lwfitz · 2012-12-04 17:02:26

Thanks all, I didn't touch the rc.xml so how that got borked beats me. All I did was change the position of my tint2 config and then it crashed.
I'll try replacing the rc.xml and tint2 with the defaults and see what that does. This same thing happened about a month ago on an office PC but I didn't have time to trouble shoot so I just reinstalled.

Edit: OK I replaced the rc.xml and tint2 configs but it didn't seem to change anything. I'm about to boot into a live disk so I can post my error log.

Heres my ~/.xsession-errors

Last edited by lwfitz (2012-12-04 17:32:57)

dura · 2012-12-04 17:33:38

Replace your existing autostart.sh with the one you find in /etc/skel/.config/openbox and see if that makes any difference.

Use the cp command at a tty if you cannot login, or you could always chroot

dura · 2012-12-04 17:34:46

Can you just post it in a code box? I don't want to download it.

lwfitz · 2012-12-04 17:39:03

dura wrote:

Replace your existing autostart.sh with the one you find in /etc/skel/.config/openbox and see if that makes any difference.
Use the cp command at a tty if you cannot login, or you could always chroot

Thats what I thought also but it didnt make any difference.

As for the ~/.xsession-errors I cant post it here cuz its just to long and pastbin has a limit unless you pay for a pro account so if you know of another way ill try it but im not sure how else to get it posted here.

dura · 2012-12-04 17:40:53

You can't post it in code brackets?

Try pastie.org

Last edited by dura (2012-12-04 17:41:22)

lwfitz · 2012-12-04 17:45:58

No its to big to just post in code brackets and also in pastie.org sorry

dura · 2012-12-04 18:29:28

Lots of bad window errors. Hundreds. I don't know what to do with this, sorry. Others may.

lwfitz · 2012-12-04 18:54:45

dura wrote:

Lots of bad window errors. Hundreds. I don't know what to do with this, sorry. Others may.

Yeah I saw those and I dont have any clue why. I also saw the Nvidia errors but theres no Nvidia card on that computer so Im a bit baffled. If this doesnt get figured out today I will just reinstall and keep an eye on the error log

lwfitz · 2012-12-05 18:05:58

Ok everythings back up and running. For me it seems that it was a video driver issue . I had a total brain fart and forgot that I had run updates which installed the newest Debian kernel (3.2.0.4 I believe) so once I finally was able to get to tty I uninstalled then reinstalled the video driver and it booted up fine.

Thanks for the help everyone.

CrunchBang Linux

SEARCH

#1 2012-11-19 06:27:41

Can't log in on after editing tint2rc

#2 2012-11-19 07:23:05

Re: Can't log in on after editing tint2rc

#3 2012-11-19 07:47:28

Re: Can't log in on after editing tint2rc

#4 2012-11-20 03:33:07

Re: Can't log in on after editing tint2rc

#5 2012-11-20 06:28:09

Re: Can't log in on after editing tint2rc

#6 2012-11-20 07:46:16

Re: Can't log in on after editing tint2rc

#7 2012-11-20 08:01:54

Re: Can't log in on after editing tint2rc

#8 2012-12-04 08:58:25

Re: Can't log in on after editing tint2rc

#9 2012-12-04 09:03:19

Re: Can't log in on after editing tint2rc

#10 2012-12-04 09:26:23

Re: Can't log in on after editing tint2rc

#11 2012-12-04 09:51:02

Re: Can't log in on after editing tint2rc

#12 2012-12-04 13:21:26

Re: Can't log in on after editing tint2rc

#13 2012-12-04 14:01:00

Re: Can't log in on after editing tint2rc

#14 2012-12-04 17:02:26

Re: Can't log in on after editing tint2rc

#15 2012-12-04 17:33:38

Re: Can't log in on after editing tint2rc

#16 2012-12-04 17:34:46

Re: Can't log in on after editing tint2rc

#17 2012-12-04 17:39:03

Re: Can't log in on after editing tint2rc

#18 2012-12-04 17:40:53

Re: Can't log in on after editing tint2rc

#19 2012-12-04 17:45:58

Re: Can't log in on after editing tint2rc

#20 2012-12-04 18:29:28

Re: Can't log in on after editing tint2rc

#21 2012-12-04 18:54:45

Re: Can't log in on after editing tint2rc

#22 2012-12-05 18:05:58

Re: Can't log in on after editing tint2rc

Board footer