Yesterday the PC go in sleep mode, after résume, i get the login screen as usual, and after login the kde desk stay empty, with the green opensuse 13.2 wallpaper and no icons.
Right and left click gives nothing.
The problem is still the same even if i restart the PC.
I have no luck, today i restart the Pc and the problem is still here.
I think there is a problem with activity, there is one undefined that I couln’t erase and when i try to create a new one, kde create not the one I choose.
On the desktop which doesn’t work you can’t make a right click, you have no bottom bar and no possibilité to create a new activité or add a panel. So you can’t do nothing you have only the green opensuse wall papier.
You must have another activity selected as current before you can delete another. The widget in the activity list should show a wrench and another icon. select the other one and it should prompt you if you want to delete.
Removing ~/.kde4 should also reset all activities. Got no clue what may create a bad activity. Perhaps one of the templates is bad.
Check the file ~/.kde4/share/config/activitymanagerrc It may hold a clue and may also allow you to remove the bad activity
Yes, you have to add & after every command (assuming you want to perform this command asynchronously, in another thread).
The contents of .bashrc are executed every time you login to the system by a terminal. So, every time you open a ‘konsole’ window, .bashrc is executed (you can check this by adding ‘echo greetings from .bashrc’ in your .bashc). The contents of the .kde4/Autostart on the other hand are executed every time you perform a KDE login on your system.
I also forgot to say that if you add your command at a script in .kde4/Autostart, you can (and probably should) remove it from .bashrc.
Yes, it is the same with &. A script (like .bashrc or my_autostart.sh) is just a set of commands, and any command can be executed on the foreground or the background. Executing on the foreground means that you (or the system running them) has to wait for the command to finish before continuing. For example, the following script
executes the copy command (cp) in a separate thread. Thus, if you execute this second script, the system will start the copying, but won’t wait till it’s done to execute the echo command. Thus you will get the message earlier.
On 2015-06-21 22:36, billypap wrote:
> Yes, you have to add & after every command (assuming you want to perform
> this command asynchronously, in another thread).
> The contents of .bashrc are executed every time you login to the system
> by a terminal.
And by all terminals and all shell processes…
Cheers / Saludos,
Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)