Search results
Search results 1-20 of 74.
Quoted Originally posted by palinkas ...Adjusting the width of the konqueror window will scale the font. So if you have a very small window you will get large fonts. Hmmm. thanx for the tip...........Will have to give it a go. PS - That trick seems to work...........I usually have the window maximized, so now I've adjusted the "Restore" size to the width I want for a good printer output.............Then I can maximize the window for normal browsing and "restore" it for printing.............Beat...
I've tried both the +/- font size buttons, and as I mentions also adjusting the font sizes through the "Settings" menu............The only thing that works is to change the desktop resolution everytime I want to print a web page.......... This problem seems to be inversely related to the size of the desktop resolution (mine is 1280x1024)...........The larger the desktop resolution, the smaller the font appears when printing a web page, which means having to adjust the desktop to a smaller resolu...
When I print a web page in Konqueror, the font size is very tiny................How do I adjust the size for the print job........I've tried changing the font size of the page before printing through the "Configure Konqueror" settings, yet it doesn't affect the font size for the print job......I'm using KDE 3.3.2 in Debian Sarge........... Any help appreciated.........
Oops..........nevermind, I had it backwards....... :roll:
Instead of using the'su' command, can you change the user permission on the script.......replacing the 'su' command with the following: [code:1]chown $(who | awk '/:0/ {print $1}') /tmp/kdialog_cmd [/code:1] Note, there is a drawback using the 'who' command for finding the user........if the username is more than eight characters, it will be shortened to exactly eight characters.......Maybe using the $USER variable would be a better solution.........
FYI - I just had a problem connecting to this forum and thought I should bring this to your attention................Here's the error msg I received: Quoted phpBB : Critical Error Could not connect to the database Hope it's not too serious.........
Quoted Original von thegeekster ..Now, is there a way to do it thru the command line, suitable for a cron job, to periodically save the session automatically?... I found the answer to this at dot.kde.org: how do I save my session? This is the command to issue according to that page at dot.kde.org: [code:1]dcop ksmserver default saveCurrentSession [/code:1] Now I can save the session periodically, thru the command line, and still save the current session when logging out using the "Restore previ...
Thank you, anda_skoa I found the option "Restore manually saved session" in the Session Manager, which did the trick.............. Now, is there a way to do it thru the command line, suitable for a cron job, to periodically save the session automatically? Many thanx
I would like to know if there is a way to save a user's current session in KDE without having to log off and log back in, as a way to update sessions in case something happens like a power failure or the pc locks up.......... Thanx
anda_skoa has a good point about adding to an over-crowded app like the Control Cener...............and splitting it up into two main centers, one for the normal user and another for the superuser is a great idea......... I already do this by having two Control Centers in my Kmenu................The one normally installed into Kmenu, and then I've added another one which requires the root password to use.....................Works for me.....
I'm curious, too...........I know how to add KWeather to the task bar (right-click on the task bar, then Add -> Applet -> KWeather)....................and about the option in the Desktop configuration dialog box to "Allow programs in desktop window" (though what that means or how it works, I don't know)................but not how to make it work on the desktop itself...............
I like the idea of having the configuration in one place............ As for the problem of differing hardware and configurations, why not use the approach similar to how webmin works in some of the modules..............Take the Apache module for instance...............You can set certain parameters using a dialog box, but you also have the ability to view the whole configuration file in an internal editor.............That way you can use the dialog box to make changes, but you also can look at t...
My vote is for Slaclware................I've tried a few of the others, and as soon as I tried Slack, it was love at frist sight....... But that 3D desktop looks intriguing.................I wonder how easy it is to tweak and maintain under the hood?.........
Xorg is the default X windows system in Slack 10, not XFree86............At least it was witht the ISOs I downloaded..............I did a virgin install of Slack 10 on a separate partition and Xorg was installed................ As for the 2.6 kernel, Slack still uses the 2.4 kernel by default as it being more stable and doesn't break a lot of things like the 2.6 kernel does...........However, in the Slackware-10.0 directory in the mirror sites, look in testing/packages/linux-2.6.7 for the kernel...
I hope everything is fixed, too....................I was getting timeout errors when trying to browse here.........
So far, I like this 3.2 build best.............I recently compiled and installed KDE-3.2.2 on my Slackware OS, making Slackware pkgs in the process, and it seems to be running better than 3.2.1..............I used to get random crashes with Konq when used as a file manager on a daily basis with earlier versions...................but since I installed the latest version of KDE, I haven't had a crash yet................ Since version 3.2. I've been compiling from source and making the Slackware pk...
Yes, it is a necessity to upgrade X to 4.4.0 with Slackware when upgrading KDE to 3.2..........The slackware pkgs are compiled with xinerama support and you'll need those libraries supplied by XFree86 4.4.0...... Unless you compiled the pkgs yourself without the xinerama support...........
type ~ in the address bar to see which home directory it takes you to..... Or, use the Home button.....
Not quite.........you must compile and install arts before compiling any other kde pkg.............The order is: arts kdelibs kdebase and the rest It is also recommeded to compile and install kdeaddons last................Take a look at BLFS (Beyond Linux From Scratch) for some good advice about compiling and installing KDE.................You can also take a look at the "KDE.SlackBuild" script in the source/kde/ directory from one of the Slackware mirrors for the order Slackware uses to compile...