Salckware or kde 3.5, is it really so SENSITIVE???
hi hi!
I was just wondering if it is just me or slackware is kind of sensitive?? or is it kde... I dont get it... examples: I open konqueror, and go to any folder, drag and drop it to the desktop and try to link it, what happens is that it tries to make a file called "media:/[some random data here]" which crashes my desktop... only way to fix it is to go console and delete the file... another one is, I wanted to share some documents with my XP machine, i made a file called /etc/smb.conf, opened control center, went to samba and configured everything up. it didnt work, so i read a little bit and found out that i had to create a file in /etc/samba/smb.conf.... I went deleted /etc/smb.conf and created everything as it should but when i go to control center > samba, it simply crashes.... reinstalling samba and kde dont fix anything... i keep getting this: Code:
[KCrash handler] Am i becoming one of those that everything they touch go to hell?? |
Definitely not Slackware because it's by far the most stable GNU/Linux around.
I recommend you not to use KDE to manage your system's configuration. Use a text editor :^). Faster and cleaner. For samba, you can use a tool named swat. Look around this forum and you'll find some nice tutorials. |
I was thinking the same, it cant be slackware but i was not sure...
about using text editor, vi is my preferred editor but there is two issues... 1) im kind of new to linux so configuring by directly editing stuff is sometimes little bit more complicated than using gui interface... 2) i dont know much of the configuration syntax of a lot of things that i need to config and sometimes i just need to quickly setup something temporal, i cannot take my time to read the manual (which i love to do in other cases) like setting up a quick share to pass some documents to my wifes computer... that is an example of something that I can take my time to configure it better later on but i needed it working at that moment... another annoying thing is the Konsole program in KDE and vi... using the backspace and [delete] buttons dont work... i have no idea what is Konsole mapping to those buttons but i cannot use vi the normal way i do in a Terminal and it is sometimes annoying to switch to another terminal to edit a file when i can just open Konsole...I am starting to have some issues with KDE... but in slax i dont have the same issues... i dont know what is it. |
Now you know why so many of us prefer the lighter window managers like WindowMaker or Fluxbox. The KDE guys provide a lot of integrated system admin tools in the KDE control center. Unfortunately, most of them are complete pants!
Linux.tar.gz is quite right. Use the propper admin tools to configure things rather than some half-baked bolt on gui and you'll be much happier. |
If you're having issues with vi maybe give nano a try. nano is a simpler command line text editor.
|
Quote:
I dont have any problem with vi, but with the Konsole... it doesnt pass all my keystrokes to vi, and there are a bunch of commands that wont simply work under KDE's konsole... i have to Ctrl+Alt+F1, log in, and THEN use vi which is annoying. |
Quote:
may be I really have to switch. |
if you can't get konsole to work the way you want by playing with its settings, then 'xterm' ought to work fine. You really shouldn't need to return to the virtual console.
|
Give yakuake a try, it's a great konsole replacement.
|
The vi thing is definitely not a KDE's fault. It is vi's configuration.
Cannot help with that. But I am a vim user and can recommend it - same and more power and easier to use. By the way vi in Slackware is link to elvis. |
Quote:
but when i am out of KDE vi works perfectly... Also i dont think is KDE but rather Konsole which has the buttons Home, End, Delete, Backspace, mapped somewhere and dont pass them to vi... now can you explain me why trying to link to some folder or file I get a crash in KDE? I get so much weird stuff with the gui that i spend most of my time in terminal mode. :D |
Quote:
KDE4 is about at least 3 maybe 5 years from being beta and at least 6 years before it should have been included in slackware NEVER HAVE I SEEN SUCH A FUCKED UP PEACE OF CRAPWARE INCLUDED IN SLACKWARE |
Quote:
So, don't use KDE 4.2.4, stick with Slack 12.2, or run XFce in Slackware 13.0. Linux is all about choice. Use what you whatever environment you want. Your rant is a bit over the top. |
@rob.rice
Might I suggest decaf? |
@rob.rice: expressing yourself in that way can not be tolerated here on LQ. Do not do that again.
|
All times are GMT -5. The time now is 09:41 AM. |