01-14-2011
KDE 4.4.3 in Slackware 13.1 x86 doesn't save my settings!
Hello everybody,
I'm not new to slackware, but i'm new to KDE 4.
I've just installed Slackware 13.1 and found out that the new KDE desktop environment is excellent!, so i've customized it to fit my needs (Screen resolution 1024x768, wallpaper, keyboard layout and graphical effects), but when i log out or reboot and log in again, the desktop environment loads the default settings, or mine are not applied!
In example, my resolution settings are ignored and the desktop loads 800x600 again.
I've already solved other bugs in Slackware 13.1 that could be related to this, like the MySQL and akonadi errors, i've marked "Restore previous session" in System Settings, etc.
What am i missing? How can i do to for making KDE to save my settings?
Thanks in advance, and please excuse my english.
Last edited by semash!; 01-15-2011 at 10:05 AM..
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Anyone who uses, has used, or would like to use Solaris on Intel-compatible hardware should rush right over to this site:
http://www.save-solaris-x86.org/
If you want it, make sure you speak up! (3 Replies)
Discussion started by: LivinFree
3 Replies
2. Shell Programming and Scripting
hi there !
i have exactly the same problem like this guy here
https://www.unix.com/shell-programming-scripting/127668-getting-curl-output-verbose-file.html
i am not able to save the curl verbose output..
the sollution in this thread (redirecting stderr to a file) does not work for me.... (0 Replies)
Discussion started by: crabmeat
0 Replies
3. Slackware
when i attach HP 1020 leaser jet printer on slackware 13.1 via usb port it detects and display message "Ready to print", in printing window (start->setting->printing) it detects & its properties(Printer->properties) is
Description : Hewlett-Packard HP LaserJet 1020
Location : Divya
Device... (0 Replies)
Discussion started by: hitlar
0 Replies
4. Slackware
I want to know more about the Concurrency(Process Synchronization, Deadlocks) of a slackware, i know already the Concurrency but i want to know further what else is the Concurrency(Process Synchronization, Deadlocks) of a slackware. :cool: (1 Reply)
Discussion started by: green12
1 Replies
5. Slackware
Hello everyone. I am a newbie in operating systems. so far I've been playing with Ubuntu and I like it a lot. I heard about Slackware and I wanna try it. Last night I download the iso but It didn't fit in my usb or Dvd. it is a 4.2 GB. Is there one less than 4.2GB that will fit in my usb or DVD? ... (1 Reply)
Discussion started by: openation1
1 Replies
6. Shell Programming and Scripting
I am trying to modify the "corestat v1.1" code which is in Perl.The typical output of this code is below:
Core Utilization
CoreId %Usr %Sys %Total
------ ----- ----- ------
5 4.91 0.01 4.92
6 0.06 ... (0 Replies)
Discussion started by: Zam_1234
0 Replies
KDED4(8) KDE User's Manual KDED4(8)
NAME
kded4 - KDE daemon - triggers Sycoca database updates when needed.
SYNOPSIS
kded4 [--help] [Generic options] [Qt-options] [KDE-options] [--check]
DESCRIPTION
kded4 is responsible for creating the sycoca file, i.e. the binary cache of servicetypes, mimetypes, and services for a particular user.
It monitors the directories containing .desktop files. When a file is added/removed, it waits 5 seconds (in case of series of updates), and
then launches kbuildsycoca.
GENERIC OPTIONS
--author
Show author information.
--help Show help about options.
--help-all
Show all options.
--help-kde
Show KDE specific options.
--help-qt
Show Qt specific options.
--license
Show license information.
-v --version
Show version information
APPLICATION OPTIONS
--check
Check Sycoca database only once.
USAGE
If kded4 is called without parameters and is already running, it shows the message:
KDE Daemon (kded) already running.
If kded4 is called with kded4 --check, then it updates the KDE sycoca using kbuildsycoca.
SEE ALSO
kdeoptions(7), qtoptions(7), kbuildsycoca(8)
BUGS
There are probably tons of bugs. Use bugs.kde.org: http://bugs.kde.org to report them.
AUTHORS
David Faure <faure@kde.org>, Waldo Bastian <bastian@kde.org>.
2008-11-12 KDED4(8)