[SOLVED] Terminal Emulator Opens in Root (Slackware 14.1 stable, Xfce)

tronayne · 02-08-2014, 12:21 PM

So, for some strange reason, logged in as "me," startx, open Terminal Emulator and it opens as me in root (not in /home/me) -- the log in opens in my home directory.

Huh.

Deleted the launcher, created a new one, same thing.

Huh.

Go on a bug hunt, can't find anything (obvious) in either ~/.cache or ~/.config. Tried other log ins, no problem.

Huh.

OK, past experience with Xfce, delete ~/.cache, stop X, log out, log back in, startx, problem gone.

Huh.

Question is, how the heck does this happen -- Xfce glitch? Me fumble-fingering something? Magic? Only thing I've done different or new is the past 24 hours is use growisofs to burn a couple of DVDs and I can't imagine that caused any problem (never knew there was such a thing as growisofs until yesterday, found out about it after problems with K3b -- don't burn many DVDs as a rule -- thanks to Didier Spaier).

How the heck did this happen?

Drakeo · 02-08-2014, 02:17 PM

this happen to me a long time ago when I did a mirror of one of my slackware systems and moved it was also strange never figured it out either still scratching my head.

chemfire · 02-09-2014, 07:39 AM

If you go into "Preferences" for the terminal app and check "Run Command as Login Shell" does the problem go away? If it does it might be something in your xintric or xfce's session manager is changing the current working directory.

tronayne · 02-09-2014, 10:02 AM

I always run the terminal emulator as a login shell, I do a lot of command line and text work and a login shell guarantees my desired environment settings. So, given that, I suppose a login shell didn't make any difference. Too, I don't have ~/.xinitrc files in any of the accounts on the system; I use KornShell exclusively and there is a ~/.kshrc file (that sets a couple of aliases, a ~/.exrc that set modes for vi and a ~/.profile that sets a couple of paths and the like (these files have been in use for at least 15 years with virtually no change made to them from System 3 to System V to Solaris to Slackware).

I did "fix" the problem by blowing away the ~/.cache directory (not much of a fix but prior experience with Xfce taught that removing the cache cleaned up various problems. Quickly. I'm just wondering what the heck caused it in the first place (I have never, ever seen that behavior on any Unix or Linux system since, oh, the early 1980's). It's a concern when I can't figure out how it happened (I looked though the entire shell history of every login account I've used over the past week for some hint and there's nothing there that looks remotely responsible -- and I can't duplicate it either).

Tiz a puzzlement.

tronayne · 04-27-2014, 09:06 AM

As of today, 27 Apr, this has happened again. Open a terminal, I'm in root (the actual root, not root's home). I can cd and I'm in my actual home directory:

Code:

fubar-trona-/: cd
fubar-trona-/home/trona:

Seems like something, somewhere is doing this (no idea what) and I don't want to blow away the ~/.cache directory -- which has been the "fix" -- without chasing down what's causing it.

Looking at /home/trona/.cache/sessions/xfce4-session-fubar:0 I see:

Code:

Client3_RestartCommand=xfdesktop,--display,:0.0,--sm-client-id,28e5fb353-d897-45d3-a898-1f1bfc79b404
Client3_CurrentDirectory=/home/trona                                                                
Client3_Program=xfdesktop                                                                           
Client3_UserId=trona                                                                                
Client3_Priority=35                                                                                 
Client3_RestartStyleHint=2                                                                          
Client4_ClientId=2e503dc1b-25a6-40d1-a319-a0b535e77052                                              
Client4_Hostname=local/fubar                                                                        
Client4_CloneCommand=xfce4-power-manager                                                            
Client4_RestartCommand=xfce4-power-manager,--restart,--sm-client-id,2e503dc1b-25a6-40d1-a319-a0b535e
77052                                                                                               
Client4_CurrentDirectory=/                                                                          
Client4_DesktopFile=/etc/xdg/autostart/xfce4-power-manager.desktop                                  
Client4_Program=xfce4-power-manager
Client4_UserId=trona
Client4_Priority=50
Client4_RestartStyleHint=0
Client5_ClientId=22f9c4fce-f1c6-4db0-b759-59fdb237c2b4
Client5_Hostname=local/fubar
Client5_CloneCommand=/usr/bin/gkrellm
Client5_RestartCommand=/usr/bin/gkrellm,--sm-client-id,22f9c4fce-f1c6-4db0-b759-59fdb237c2b4
Client5_Program=/usr/bin/gkrellm
Client5_UserId=trona
Client5_Priority=50
Client5_RestartStyleHint=0
Client6_ClientId=22f037889-4325-4bda-81dc-bef10796e3d3
Client6_Hostname=local/fubar
Client6_RestartCommand=/usr/bin/kactivitymanagerd,-session,22f037889-4325-4bda-81dc-bef10796e3d3_139
8516307_933134
Client6_Program=/usr/bin/kactivitymanagerd
Client6_UserId=trona
Client6_Priority=50
Client6_RestartStyleHint=0
Client7_ClientId=220f3f7f6-0585-4847-a6ec-6aecd3bce29d
Client7_Hostname=local/fubar
Client7_RestartCommand=/usr/bin/hp-systray,-session,220f3f7f6-0585-4847-a6ec-6aecd3bce29d_1398516307
_934181
Client7_Program=/usr/bin/hp-systray
Client7_UserId=trona
Client7_RestartStyleHint=0
Count=8
LegacyCount=0
Screen0_ActiveWorkspace=0
LastAccess=1398516307

Which makes no sense whatsoever.

Anybody have any ideas (other than blow away ~/.cache)?

tronayne · 04-28-2014, 11:32 AM

Well, I've dug around all over the place trying to identify the cause and have come up empty.

Easy solution: rm -r ~/.cache.

Phooey.

Habitual · 04-28-2014, 01:25 PM

Quote:

Originally Posted by tronayne

Well, I've dug around all over the place trying to identify the cause and have come up empty.

Easy solution: rm -r ~/.cache.

Phooey.

Surprising how often that "fixes" stuff.

GazL · 04-28-2014, 05:56 PM

Random and unpredictable behaviour/breakage used to be the province of MS Windows. This used to happen to me with KDE apps and the ~/.kde directory, but it's sad to see it spreading to other linux desktop environments as well.

There's something to be said for sticking with a basic window-manager and 'xterm'. You'll probably get labelled a 'Luddite' by the unenlightened, but you never have to deal with nonsense like this.

tronayne · 04-28-2014, 06:17 PM

Quote:

Originally Posted by GazL

Random and unpredictable behaviour/breakage used to be the province of MS Windows.

Ah, but it still is.

Quote:

Originally Posted by GazL

This used to happen to me with KDE apps and the ~/.kde directory, but it's sad to see it spreading to other linux desktop environments as well.

Uh, yeah. That's why I abandoned KDE two release or so ago.

Quote:

Originally Posted by GazL

There's something to be said for sticking with a basic window-manager and 'xterm'. You'll probably get labelled a 'Luddite' by the unenlightened, but you never have to deal with nonsense like this.

Naw. Wouldn't go quite that far. Plain ol' xterm? No, thanks, I'll put up with the random breakage, methinks.

Still, gotta wonder what and why, eh?