<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments for Linux Beginner</title>
	<atom:link href="http://linux.radioactiveliberty.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://linux.radioactiveliberty.com</link>
	<description>Installing and Using Linux for Beginners</description>
	<pubDate>Thu, 18 Mar 2010 08:41:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on How to Fix KDE 4.1 Plasma Workspace by BEAR</title>
		<link>http://linux.radioactiveliberty.com/uncategorized/fix-kde-41-plasma-workspace/comment-page-1/#comment-12</link>
		<dc:creator>BEAR</dc:creator>
		<pubDate>Tue, 13 Jan 2009 12:59:38 +0000</pubDate>
		<guid isPermaLink="false">http://linux.radioactiveliberty.com/?p=4#comment-12</guid>
		<description>I did find the two files in ~/.kde4/share/config 
(last time I was poking in ~/.kde/share/config). Ok, so I removed them then reboot.
Same error. I nearly freaked out. But I remembered I read somewhere that loging  with another user works. So why not log-in with "root"?
Here is what I did to fix it:
At the error message I clicked close &#62; CTRL+ALT+DEL &#62; Log-out
I get the graphic log-in menu. I log-in as root and I get my plasma workspace running again with default settings. Then, from there I go to "Users" I deleted my old user (I kept the files in his home directory), and created a new one.
And now it works. 
Only one thing that bugs me that it's not automated log-in. 
I have to type the password every time. Other than that everything is OK.
I now know not to mess with the panel (too much) :D! 
It takes less time to re-customize my workspace than reinstalling the whole OS.
Thanks for the help :).
See you around.</description>
		<content:encoded><![CDATA[<p>I did find the two files in ~/.kde4/share/config<br />
(last time I was poking in ~/.kde/share/config). Ok, so I removed them then reboot.<br />
Same error. I nearly freaked out. But I remembered I read somewhere that loging  with another user works. So why not log-in with &#8220;root&#8221;?<br />
Here is what I did to fix it:<br />
At the error message I clicked close &gt; CTRL+ALT+DEL &gt; Log-out<br />
I get the graphic log-in menu. I log-in as root and I get my plasma workspace running again with default settings. Then, from there I go to &#8220;Users&#8221; I deleted my old user (I kept the files in his home directory), and created a new one.<br />
And now it works.<br />
Only one thing that bugs me that it&#8217;s not automated log-in.<br />
I have to type the password every time. Other than that everything is OK.<br />
I now know not to mess with the panel (too much) :D!<br />
It takes less time to re-customize my workspace than reinstalling the whole OS.<br />
Thanks for the help :).<br />
See you around.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Fix KDE 4.1 Plasma Workspace by admin</title>
		<link>http://linux.radioactiveliberty.com/uncategorized/fix-kde-41-plasma-workspace/comment-page-1/#comment-11</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Tue, 13 Jan 2009 05:04:20 +0000</pubDate>
		<guid isPermaLink="false">http://linux.radioactiveliberty.com/?p=4#comment-11</guid>
		<description>I'm really not sure what to do. Can you get to the command, just your basic command line in the default view from your home folder and run 

&lt;b&gt;vdir ~/.kde/share/config&lt;/b&gt;
or
&lt;b&gt;vdir ~/.kde4/share/config&lt;/b&gt;

depending on how Suse is configured to use KDE4.

and copy and paste the output here. There are a lot of filenames that start with "k" in the directory, because that's how the programs are named, but I can't seem to NOT find the two plasma configuration files, as long as it's in the right directory.

Unfortunately, I have just never used Suse at all.</description>
		<content:encoded><![CDATA[<p>I&#8217;m really not sure what to do. Can you get to the command, just your basic command line in the default view from your home folder and run </p>
<p><b>vdir ~/.kde/share/config</b><br />
or<br />
<b>vdir ~/.kde4/share/config</b></p>
<p>depending on how Suse is configured to use KDE4.</p>
<p>and copy and paste the output here. There are a lot of filenames that start with &#8220;k&#8221; in the directory, because that&#8217;s how the programs are named, but I can&#8217;t seem to NOT find the two plasma configuration files, as long as it&#8217;s in the right directory.</p>
<p>Unfortunately, I have just never used Suse at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Fix KDE 4.1 Plasma Workspace by BEAR</title>
		<link>http://linux.radioactiveliberty.com/uncategorized/fix-kde-41-plasma-workspace/comment-page-1/#comment-10</link>
		<dc:creator>BEAR</dc:creator>
		<pubDate>Tue, 13 Jan 2009 03:45:55 +0000</pubDate>
		<guid isPermaLink="false">http://linux.radioactiveliberty.com/?p=4#comment-10</guid>
		<description>I was talking about the ~/.kde4/share/config folder. Forgot to mention earlier, sorry.
I get to the folder like root. I typed exactly what it was suggested above and I get "file not found".
Strange thing is that none of the files in that folder does not include "plasma"  in their filenames. I can't find which one is the config file.

EDIT:
Just to let you know:
At the error message I tried pressing CTRL+TAB wich activates my DESKTOP CUBE, and it was working (and the background for the cube was there). But no Desktops were visible (invisible cube :)).</description>
		<content:encoded><![CDATA[<p>I was talking about the ~/.kde4/share/config folder. Forgot to mention earlier, sorry.<br />
I get to the folder like root. I typed exactly what it was suggested above and I get &#8220;file not found&#8221;.<br />
Strange thing is that none of the files in that folder does not include &#8220;plasma&#8221;  in their filenames. I can&#8217;t find which one is the config file.</p>
<p>EDIT:<br />
Just to let you know:<br />
At the error message I tried pressing CTRL+TAB wich activates my DESKTOP CUBE, and it was working (and the background for the cube was there). But no Desktops were visible (invisible cube :)).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Fix KDE 4.1 Plasma Workspace by admin</title>
		<link>http://linux.radioactiveliberty.com/uncategorized/fix-kde-41-plasma-workspace/comment-page-1/#comment-9</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Mon, 12 Jan 2009 23:40:38 +0000</pubDate>
		<guid isPermaLink="false">http://linux.radioactiveliberty.com/?p=4#comment-9</guid>
		<description>Bear, if you use the command in the first line as:
&lt;b&gt;cd ~/.kde4/share/config&lt;/b&gt;

Then will it work? I don't know much about Suse, but I think they might do like Kubuntu was doing and have the .kde folder for the KDE3 files, and a .kde4 folder for the KDE 4 files. Also, make sure the "dot" is there in trying to find the file. The folder is in your home folder as either (dot)kde or (dot)kde4.

I thought I was going to have to reinstall as well until I found the solution.  I hope you can work this out. It is a really quick fix if you can find the right files.</description>
		<content:encoded><![CDATA[<p>Bear, if you use the command in the first line as:<br />
<b>cd ~/.kde4/share/config</b></p>
<p>Then will it work? I don&#8217;t know much about Suse, but I think they might do like Kubuntu was doing and have the .kde folder for the KDE3 files, and a .kde4 folder for the KDE 4 files. Also, make sure the &#8220;dot&#8221; is there in trying to find the file. The folder is in your home folder as either (dot)kde or (dot)kde4.</p>
<p>I thought I was going to have to reinstall as well until I found the solution.  I hope you can work this out. It is a really quick fix if you can find the right files.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Fix KDE 4.1 Plasma Workspace by BEAR</title>
		<link>http://linux.radioactiveliberty.com/uncategorized/fix-kde-41-plasma-workspace/comment-page-1/#comment-8</link>
		<dc:creator>BEAR</dc:creator>
		<pubDate>Mon, 12 Jan 2009 21:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://linux.radioactiveliberty.com/?p=4#comment-8</guid>
		<description>I tried that but it did not work for me. I use openSUSE 11 and yes after I tried to make the panel smaller...."blam".

Problem is that those files are not there.
plasma-appletsrc
plasmarc

I checked with DIR. All files begin with kde.... or something like that.
Any ideas? I really don't want to reinstall again :).</description>
		<content:encoded><![CDATA[<p>I tried that but it did not work for me. I use openSUSE 11 and yes after I tried to make the panel smaller&#8230;.&#8221;blam&#8221;.</p>
<p>Problem is that those files are not there.<br />
plasma-appletsrc<br />
plasmarc</p>
<p>I checked with DIR. All files begin with kde&#8230;. or something like that.<br />
Any ideas? I really don&#8217;t want to reinstall again :).</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Fix KDE 4.1 Plasma Workspace by thotti</title>
		<link>http://linux.radioactiveliberty.com/uncategorized/fix-kde-41-plasma-workspace/comment-page-1/#comment-7</link>
		<dc:creator>thotti</dc:creator>
		<pubDate>Mon, 05 Jan 2009 07:43:08 +0000</pubDate>
		<guid isPermaLink="false">http://linux.radioactiveliberty.com/?p=4#comment-7</guid>
		<description>Great solution! it solved the same problem with kubuntu 8.10
Thanks</description>
		<content:encoded><![CDATA[<p>Great solution! it solved the same problem with kubuntu 8.10<br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Fix KDE 4.1 Plasma Workspace by admin</title>
		<link>http://linux.radioactiveliberty.com/uncategorized/fix-kde-41-plasma-workspace/comment-page-1/#comment-6</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Wed, 17 Dec 2008 03:51:24 +0000</pubDate>
		<guid isPermaLink="false">http://linux.radioactiveliberty.com/?p=4#comment-6</guid>
		<description>Hi Lezah. What I mean is when you start up you get to the login screen. That's where it has the little box that has your username, and you enter your password. Instead of logging in that way, when you get to that screen find the menu button, and it will list options such as "default" "kde" and "console login". I 'm not sure if those are the exact options or not, but it will look something like that. 

So don't log in on the login screen. Select the menu, then console login. Then you will have a black screen with your prompt to enter commands into it. You will have to then log in with your user name and password from what is a command line only session. The desktop will not load. It will only be a command line prompt.

Type the commands exactly as they are one line at a time. I think you will have to start with typing:

su - 

followed by the root password. Then one line at a time follow the above commands. What it does is delete the old plasma configuration file. This file is based on a version of plasma that was phased out, so it causes a conflict. When you restart, the file is regenerated based on the new version of plasma, and the conflict no longer exists.</description>
		<content:encoded><![CDATA[<p>Hi Lezah. What I mean is when you start up you get to the login screen. That&#8217;s where it has the little box that has your username, and you enter your password. Instead of logging in that way, when you get to that screen find the menu button, and it will list options such as &#8220;default&#8221; &#8220;kde&#8221; and &#8220;console login&#8221;. I &#8216;m not sure if those are the exact options or not, but it will look something like that. </p>
<p>So don&#8217;t log in on the login screen. Select the menu, then console login. Then you will have a black screen with your prompt to enter commands into it. You will have to then log in with your user name and password from what is a command line only session. The desktop will not load. It will only be a command line prompt.</p>
<p>Type the commands exactly as they are one line at a time. I think you will have to start with typing:</p>
<p>su - </p>
<p>followed by the root password. Then one line at a time follow the above commands. What it does is delete the old plasma configuration file. This file is based on a version of plasma that was phased out, so it causes a conflict. When you restart, the file is regenerated based on the new version of plasma, and the conflict no longer exists.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How to Fix KDE 4.1 Plasma Workspace by lezah</title>
		<link>http://linux.radioactiveliberty.com/uncategorized/fix-kde-41-plasma-workspace/comment-page-1/#comment-5</link>
		<dc:creator>lezah</dc:creator>
		<pubDate>Wed, 17 Dec 2008 02:58:04 +0000</pubDate>
		<guid isPermaLink="false">http://linux.radioactiveliberty.com/?p=4#comment-5</guid>
		<description>how to get in the console?</description>
		<content:encoded><![CDATA[<p>how to get in the console?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Beginning Linux and Hating Windows by Installing Fedora 8: First Impressions &#124; Linux Beginner</title>
		<link>http://linux.radioactiveliberty.com/linux/beginning-linux-hating-windows/comment-page-1/#comment-3</link>
		<dc:creator>Installing Fedora 8: First Impressions &#124; Linux Beginner</dc:creator>
		<pubDate>Sat, 09 Feb 2008 21:10:58 +0000</pubDate>
		<guid isPermaLink="false">http://linux.radioactiveliberty.com/?p=1#comment-3</guid>
		<description>[...] rebooted, Fedora 8 KDE started to lose its lustre. I&#8217;m supposed to have an installation of Debian Lenny and Kubuntu on the hard drive as well. It should be a triple boot setup, but F8 behaved as the only [...]</description>
		<content:encoded><![CDATA[<p>[...] rebooted, Fedora 8 KDE started to lose its lustre. I&#8217;m supposed to have an installation of Debian Lenny and Kubuntu on the hard drive as well. It should be a triple boot setup, but F8 behaved as the only [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
