Welcome!
Important information
-- Spectre and Meltdown vulnerabilities
-- Change in MX sources

News
-- MX Linux on social media: here
-- Mepis support still here

Current releases
-- MX-17.1 Final release info here
-- antiX-17 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

mucked up KDE 4.8.4 again in MEPIS 12 64 bit

Here is where all questions and discussions about KDE should go.
Message
Author
User avatar
uncle mark
Forum Veteran
Forum Veteran
Posts: 4982
Joined: Sat Nov 11, 2006 10:42 pm

Re: mucked up KDE 4.8.4 again in MEPIS 12 64 bit

#21 Post by uncle mark » Mon May 26, 2014 3:39 pm

eemaestro wrote:For some unknown reason, I am still not getting taskbar icons corresponding to instances of open KDE applications or Konsole CLI sessions.
Add the Task Manager widget to the Panel.
Desktop: Custom build Asus/AMD/nVidia -- MEPIS 11
Laptop: Acer Aspire 5250 -- MX-15
Assorted junk: assorted Linuxes

User avatar
eemaestro
Forum Guide
Forum Guide
Posts: 1010
Joined: Wed Aug 02, 2006 12:12 pm

Re: mucked up KDE 4.8.4 again in MEPIS 12 64 bit

#22 Post by eemaestro » Mon May 26, 2014 4:39 pm

I watched the KDE 4 video, so I knew to double-mouse-click the widget icon. YAY! It worked. Thanks, uncle mark.

User avatar
eemaestro
Forum Guide
Forum Guide
Posts: 1010
Joined: Wed Aug 02, 2006 12:12 pm

Re: mucked up KDE 4.8.4 again in MEPIS 12 64 bit

#23 Post by eemaestro » Tue May 27, 2014 7:39 am

Am following http://superuser.com/questions/174306/h ... nd-history to see about enabling the BASH command history.

Code: Select all

$set -o | grep history 
returns nothing.
However, none of the environment variables pertaining to history, i.e., HISTFILE, HISTSIZE, HISTFILESIZE are defined after I log out and then log back in. I conclude that .bashrc is NOT being executed upon login. What the heck happened?

If I add touch ~/booger to .bashrc is this one way to verify that it gets run after I logout and then log backin?
(assuming I purposefully make sure no such file exists before logging out)

I get this at the command line:

Code: Select all

$ shopt -s histappend
/bin/sh: 9: shopt: not found

User avatar
eemaestro
Forum Guide
Forum Guide
Posts: 1010
Joined: Wed Aug 02, 2006 12:12 pm

Re: mucked up KDE 4.8.4 again in MEPIS 12 64 bit

#24 Post by eemaestro » Wed May 28, 2014 12:45 pm

Not sure what this means.

Code: Select all

$set -o history
/bin/sh: 24: set: Illegal option -o history
Yeah, I know this probably does not pertain to KDE. Does this mean that BASH is not my default shell ? How do I make BASH my default shell?

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9353
Joined: Wed Jul 12, 2006 2:26 pm

Re: mucked up KDE 4.8.4 again in MEPIS 12 64 bit

#25 Post by kmathern » Wed May 28, 2014 1:02 pm

eemaestro wrote:Not sure what this means.

Code: Select all

$set -o history
/bin/sh: 24: set: Illegal option -o history
Yeah, I know this probably does not pertain to KDE. Does this mean that BASH is not my default shell ? How do I make BASH my default shell?
Do you still have a .bashrc file?

Code: Select all

ls -l ~/.bashrc
If not I think there should be one in the /etc/skel folder that you can copy over to your /home/<username> folder.

User avatar
eemaestro
Forum Guide
Forum Guide
Posts: 1010
Joined: Wed Aug 02, 2006 12:12 pm

Re: mucked up KDE 4.8.4 again in MEPIS 12 64 bit

#26 Post by eemaestro » Wed May 28, 2014 1:53 pm

Code: Select all

$ cd ~
$ ls -altr .bashrc 
-rwxr--r-- 1 jon jon 3755 May 27 21:45 .bashrc
Yes.

User avatar
kmathern
Forum Veteran
Forum Veteran
Posts: 9353
Joined: Wed Jul 12, 2006 2:26 pm

Re: mucked up KDE 4.8.4 again in MEPIS 12 64 bit

#27 Post by kmathern » Wed May 28, 2014 2:12 pm

eemaestro wrote:

Code: Select all

$ cd ~
$ ls -altr .bashrc 
-rwxr--r-- 1 jon jon 3755 May 27 21:45 .bashrc
Yes.
The ownership and permissions are slightly different for my .bashrc (I'm not talking about the obvious difference of 'kent' vs 'jon')

Code: Select all

kent@mx1:~
$ ls -l ~/.bashrc
-rw-r--r-- 1 kent users 3754 May 28 12:57 /home/kent/.bashrc
kent@mx1:~
What's posted above is for my MX14 install, but I think the ownership & permissions were the same in M12 (and M11 & M8.5 and ...)



Maybe try this to change the ownership (changing groups from 'jon' to 'users')

Code: Select all

chown jon:users ~/.bashrc 
And this to change the permissions

Code: Select all

chmod 644 ~/.bashrc

User avatar
eemaestro
Forum Guide
Forum Guide
Posts: 1010
Joined: Wed Aug 02, 2006 12:12 pm

Re: mucked up KDE 4.8.4 again in MEPIS 12 64 bit

#28 Post by eemaestro » Wed May 28, 2014 4:41 pm

Okay, I made your two changes to the file, logged out, and logged back in. I thought .bashrc was supposed to be executable by user. Perhaps not ? Didn't seem to make a difference. SHELL still undefined. history still not working

User avatar
Richard
Posts: 2142
Joined: Fri Dec 12, 2008 10:31 am

Re: mucked up KDE 4.8.4 again in MEPIS 12 64 bit

#29 Post by Richard » Wed May 28, 2014 4:52 pm

@eemaestro,
I'm curious about something.
Did you have no bash history since installing?
Or is it something you broke afterwards?

Code: Select all

set -o history
in a user console turns on history keeping, if it is off.
MX171: Lenovo T430: Intel Ivy Bridge i5-3320M, 8GB RAM, 4.18.0-2-amd64, 119GB SSD
MX171: AA1/EeePC: DualCore N270, 1GB RAM, 4.9.126-antix.1-686-smp-pae, 150GB HDD
Thunar/Doublecmd, LibO613, Dropbox, Firefox, CherryTree, Vbox. LinuxCounter #208633

User avatar
eemaestro
Forum Guide
Forum Guide
Posts: 1010
Joined: Wed Aug 02, 2006 12:12 pm

Re: mucked up KDE 4.8.4 again in MEPIS 12 64 bit

#30 Post by eemaestro » Thu May 29, 2014 12:24 pm

Richard wrote:@eemaestro,
I'm curious about something.
Did you have no bash history since installing?
Or is it something you broke afterwards?

Code: Select all

set -o history
in a user console turns on history keeping, if it is off.
I originally had bash history working.

Then, after replacing my ~/.kde following Joany's advice in Post #340732, it stopped
working. To remind you, I did this to rectify the problem I first described in Post #340703,
the beginning of this thread.

Now, history works fine for superuser. But for user, it fails. When I try to turn BASH history on as user, I get the error message in Post #341006.

I am still trying to figure out what happened and how to fix it. I could just blame Kuser, which I used to create all the new user accounts. I copied ./kde from one of these new accounts. So this "default KDE user configuration" was created by Kuser. This was my first time using Kuser. So maybe I failed to do something in Kuser to set BASH as the default shell ? or to enable BASH history?

I suppose I could start doing a subdirectory-by-subdirectory comparison between ~/.kde and ~/.kdebak. But where to start?

Post Reply

Return to “KDE”