[SOLVED] regarding arch derivative - manjaro. prevent personalization changes after each upgrade
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
This i was told is tty shell or ssh shell (same as taken from /etc/passwd
Code:
╰─ echo $SHELL
/bin/bash
This however is the current shell that is using .. which i do commandline with on emulated terminal which is zsh.
Code:
╭─ ~
╰─ echo $0
/bin/zsh
You see, there are 2 shell "profile" , one for konsole (emulated terminal) and one for the real tty shell.
Only the first code snippet tells you anything about the default shell for user1.
For the last 2 I wonder: why did you use $SHELL and $0, not just $SHELL for both?
And: where are those snippets from? I guess they aren't both from just opening the default terminal in KDE, so what's the difference?
OK I went ahead and looked at manjaro.org. Dog, I hate that website. The update announcements are apparently here. What an effing mess, good luck finding out how your default shell changed. After I while I found this thread which looks strangely familiar.
I'm not sure (OP doesn't appear to be well-informed, just angry) but they later say:
Quote:
I’m a idiot - you know what it is … konsole sets it’s own shell rather than respecting the users… duh!
I hope you understand that this is not the same as changing the default shell.
However: this is most likely something that Manjaro devs did, not KDE/konsole itself.
Hence, my satement stands:
Quote:
Originally Posted by ondoho
OK, theoretically any distro can do anything with their updates, but I know for a fact that the underlying archlinux would never do anything like that, and any distro that does would be seriously broken and should not be used, full stop.
And, sorry to harp on it, but you really need to get a better grasp on your OS if you want to tinker with it.
You can't be an eternal newbie AND have full control over your system.
The main folder to back up from the home folder then is the .local folder, that contains all your user preferences.
I would like to know:
Let's say i have backup my ".local" folder (which is now 500Mb on my pc)
Then arch upgrade again (changes default of theme, default windows style, default shell on emulated terminal, changes default login manager...etc)
I run the arch upgrade.
After successfully upgraded my arch,
I replace the whole ".local" folder from /home with the ".local" folder that i have backup earlier...
**The question now is: will this causes Problem to any part of my system (eg: Desktop manager ) ?
Use Virtual Machines, and try several flavours and find one you like, I used to use Desktop Environments, but these days use Window Managers like openbox or i3 etc, it just depends on what you use your system for as to the best way to go, so try them all and find one you like!
This is a bit of branching of thread title:
I couldn't help it but wondering :
Since you said you used to use DE (KDE, GNOME, XFCE, LXDE, LQXT.....) ,but now you prefer to using window manager like (openbox, i3.... i suppose fluffybox also) ?
I am confused here.
You said these days, you are no longer using DE , you just use window manager ??
I have got window manager here on KDE plasma as well.. Isn't it window manager is default in all linux with gui ? Desktop manager rely on window manager to function.. Then i can use window manager on top of KDE (chuck away my kde (DE) ) ??
Does window manager can function like Desktop manager ?? then why bother to have a duplicate of it on KDE or Gnome eco system ?
I am a bit confused here.
Some people want the convenience of STUFF that DEs like Plasma provide.
Some people prefer their OS to provide just the WM part, and have the greater control/precision of manually providing their own STUFF.
(There is no better - it's an individual choice - and a good choice for one person may be a bad choice for another person.)
KWin is the window manager the Plasma desktop environment uses; apparently one can run Plasma on other window managers, but that seems a good way to discover more weird quirks/annoyances.
I hope you understand that this is not the same as changing the default shell.
However: this is most likely something that Manjaro devs did, not KDE/konsole itself.
Yes, i understand now.
As regarding your question on why i use "echo $SHELL" and "echo $0". Well it was due to i never use a zsh shell before and i didn't knew there is different between tty shell and emulated shell, hence i was in a mess asking for help.
Later i learnt that my tty shell didn't change, still bash as "echo $SHELL" tells me that.
one person in manjaro forum told me that to know what shell i am using in Emulated shell, i should use "echo $0" instead.
I would like to know:
Let's say i have backup my ".local" folder (which is now 500Mb on my pc)
Then arch upgrade again (changes default of theme, default windows style, default shell on emulated terminal, changes default login manager...etc)
I run the arch upgrade.
After successfully upgraded my arch,
I replace the whole ".local" folder from /home with the ".local" folder that i have backup earlier...
**The question now is: will this causes Problem to any part of my system (eg: Desktop manager ) ?
NO.
System updates do not touch stuff under your $HOME.
And despite being snarky about it before, I don't think Manjaro is so broken that it would attempt that.
________________________________________
To wrap all this up...
I was thinking the other day - the word "default shell" is really a little ambiguous.
Usually it just means "the shell a normal user gets after a console login" and is not very important for GUI users, because:
The terminal emulator (remember this is just a GUI program like any other) usually defaults to the user login shell, but most have a config option to change that. I believe that is what has been happening to you, and simply trying another terminal emulator (xterm, urxvt, xfce4-terminal etc. etc.) would have been enough to clarify. This is called troubleshooting, something we keep preaching to newbs like you (sorry for the lecture).
OTOH though, what shell does the system "default" to? Or the root user? I guess it is whatever is linked to /bin/sh.
Try it on your system:
Code:
ls -l /bin/sh
On Debian systems it should be dash, on Arch systems it should be bash (by default).
The terminal emulator (remember this is just a GUI program like any other) usually defaults to the user login shell, but most have a config option to change that. I believe that is what has been happening to you, and simply trying another terminal emulator (xterm, urxvt, xfce4-terminal etc. etc.).
OTOH though, what shell does the system "default" to? Or the root user? I guess it is whatever is linked to /bin/sh.
Try it on your system:
Code:
ls -l /bin/sh
On Debian systems it should be dash, on Arch systems it should be bash (by default).
Thanks for telling me that terminal emulator is just an another GUI program, i thought it is something different.. lol
[code]ls -l /bin/sh[/code
Yes, default is bash still.
System updates do not touch stuff under your $HOME.
And despite being snarky about it before, I don't think Manjaro is so broken that it would attempt that.
Thanks for remind this again.
So , now i know my default terminal emulator (gui program) has got a default personalization config file that is located outside of /home . .hence when they upgrade it, they change the config file to run zsh instead of bash.
When i personalized terminal emulator, it actually generate personalized config file in my /home (whatever location), hence this will prevent future changed due to upgrade.
Is the logic still true to my <b>wall paper</b> ? it changes everytime after upgrade..
If you back up your .local folder, and restore it after a fresh install, you should be back at a familiar place with your settings restored.
This thread addressed various things over its course, but as far as the last 10 or so posts are concerned, no.
It seems Manjaro itself changed some konsole settings after an update.
Changing things under $HOME would not fix this problem. As was said numerous times now, was actually an important point for OP to understand: updates don't change things under $HOME.
System updates do not touch stuff under your $HOME.
And despite being snarky about it before, I don't think Manjaro is so broken that it would attempt that.
Quote:
Originally Posted by ondoho
It seems Manjaro itself changed some konsole settings after an update.
Changing things under $HOME would not fix this problem. As was said numerous times now, was actually an important point for OP to understand: updates don't change things under $HOME.
Now i am confused !
On one hand you said system upgrades won't touch stuff under $HOME.
On the other hand you said, manjaro itself changed some konsole settings after an update; changing things under $HOME would not fix this problem (this statement simply means things in $HOME will be change ...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.