Image 01


Martin Koller , Austria
Dolphin Service Menus
Graphic Apps
System Software
Various Plasma 5 Improvements

Various Plasma 5 Improvements 6 comments

Score 70.0%
Aug 16 2018
The latest source is always here - Dec 17 2018
I'm using kmix. - Aug 16 2018

Graphic Apps 58 comments

Score 78.6%
Dec 18 2016
I added this now in version 1.9 - Sep 27 2014
This seems to be a limitation of Qt4. I tested now with a mouse which has a tilt wheel. Although with "xev" I can see the left/right tilt of the wheel to deliver button 6 and 7, in Qt I get no mouse event for these.
Also I found that my implementation was wrong, as Qt does not deliver the button number but some Qt defined value (e.g. left button = 1, right = 2, mid = 4).
I think this issue can only be solved with Qt5/KDE-Frameworks5 - Sep 27 2014
ok, I see your problem. You have a panel ON TOP, which I did not take into account. This is a bug, and I have fixed it now.
I'm uploading a fixed version 1.8.2 - Sep 26 2014
I implemented this now in 1.8.1 - May 26 2013
I added now the possibility to configure the previous/next mouse buttons in the new version 1.8
However, as I do not have a mouse with more than the usual 3 Buttons (+wheel), I could not test if it works with more buttons.
Can you try 1.8 and tell me if it works for you, please ? - Apr 06 2013
There are some simple solutions to your problem:

1.) moving ANY window can be done by holding the Alt-Key and press the left mouse anywhere inside the window. I don't know if that is the default of kwin since I'm using this since ages, but at least it can be configured this way in Window Manager Settings -> "Configure keyboard and mouse settings"

2.) ShowImage shows the toolbar either in the top area of the window or also on the bottom area, that is: simply move your mouse to the bottom and you'll get the overlay with the tool buttons and the image information - Apr 06 2013
As internally a KDE action can only have 2 shortcuts, I added 2 more hardcoded. That is: quitting the app can be done with Ctrl+Q, Enter, Return, Escape

But I found a better way with which you now can configure or remove all four.
I'll release an updated version - Apr 06 2013
This are the standard texts ... I'll change them - Apr 06 2013
Good idea and simple to solve. I've already added this to my local source.
Will upload a new version soon - Apr 03 2013
you can go directly to the openSuse build service repository: - Sep 22 2012
you are right, but this is a problem of the whole kde-apps site.
I can only try to contact the site admin. - Sep 22 2012
I'll have a look. Hopefully I find some time... - Feb 20 2012
I'm trying to build xUbuntu packages on openSuse build service now and while fiddling with that I found the missing package.

It's kdelibs5-dev NOT kdelibs4-dev which seems to be the development package for the old KDE3) - Aug 28 2011
I found the following page:

Maybe it's this package: kdesdk-scripts ?

As this is a specific distribution problem, please ask the question on a kubuntu forum.

I'm using openSuse so I can't really help you here - sorry. - Aug 28 2011
Looking into /usr/share/cmake/Modules/FindKDE4.cmake I find the comment:

# Please look in FindKDE4Internal.cmake and KDE4Macros.cmake for more information.
# They are installed with the KDE 4 libraries in $KDEDIRS/share/apps/cmake/modules/.

I'd say you definitely need the kdelibs-devel package and the qt-devel package. - Aug 27 2011
You're right, this is a bug.
I've already fixed it and will upload a new version. - Aug 23 2011
I took your ideas and implemented the most of them in the new version 1.5 (printing is still missing). - Aug 06 2011
no, it does not need anything else but Qt and KDE4.
The problems with the availability of imlib was the reason why I implemented a new tool as replacement of kuickshow.

- on right click add
a) properties
b) save as
c) print

=> I'll add it to my TODO

- add an icon for use by task manager
Hmm ... I set an icon, but a generic one as I do not bundle one. The name is x-shape-image, which KDE finds here in

probably I'll need to bundle one... - Jul 27 2011

System Software 105 comments

Score 70.0%
Jan 13 2018
There's a misunderstanding.
Medium: 1, [ 61% ] Size: 593GiB
means: The medium 1 (the target where you archive to) is now 61% full and has an overall size of 593GiB

Medium: 1, [ 0% ] Size: 221.6GiB
"Backup successfully finished",
...finished slice
-- Filtered Files: 65561

This now means: the backup did not write anything (therefore the target medium you write to is 0% full) and the global size of the target medium is 221.6GiB. (it seems the full backup is ~370GiB large)
As you hit the "Start backup" button simply a second time, it tried to do an incremental backup, that is: archiving only changed files since the last backup.
As you did not change anything after the full backup, it did not archive anything and therefore all files (65561) were filtered (e.g. not put into the archive). - May 01 2014
You should exclude the system special directories like /dev, /proc, /sys, /run - they do not contain real files but things the Linux Kernel generates on the fly.
You will not need them for a restore. - Nov 30 2013
You can disable the compression completely via a profile setting.

The reason for compressing each file was the idea to allow for archive slices with a maximum size but still have compressed data.
To be able to know if a file still fits into a slice, I have to compress it before putting it into the slice, otherwise I can not know how large the slice will be when I compress the complete slice.

Of course this does not rule out another option to compress the complete uncompressed tar file after creation - it just does not make much sense in combination with a slice size limit.

I'll put it onto my TODO list - Jul 27 2012
Have a look here:

The restore functionality is not yet implemented due to lack of time, sorry. - Jun 14 2012
I think the problem here is only the connection to DBUS. See the message
"Session bus not found".

I run kbackup here also as root started from within crontab and it works.
On this system, when I run kbackup as root from a shell (not inside a KDE session), I see that a new dbus session bus process is started.

Probably this is not happening on the Debian system ? - Sep 15 2010
Are you still using kbackup 0.5.x ?
If so, then this is the limit Qt3 can handle.
Try it with the current 0.6.x version instead. - Dec 06 2009
There are other constraints:
In the source I made the following comment:

// calculate how large a slice can actually be
// - limited by the target directory (when we store directly into a local dir)
// - limited by the "tmp" dir when we create a tmp file for later upload via KIO
// - limited by Qt (64bit int)
// - limited by user defined maxSliceMBs

I will add this to the documentation.

So in your case it must be the KDE-tmp-dir free disc space. - Oct 24 2009
Depending on how you installed it, it is either in the source package, or in some other rpm package, etc.
E.g. on openSuse it's in the extra package kbackup-lang-0.6.3-3.1.i586.rpm - Oct 23 2009
> From the manual looks like compression is done to
> every file individually.

Yes, until you deactivate compression completely, which
you can define in the profile settings.

> Generally when I do
> restores I to a command like:
> tart -xvf backup.tgz -C /mnt/harddisk
> If I am to uncompress this archive, wouldn't I
> have to do something like:
> tar backup.tar | bzcat *

After you extracted it from the tar-file (tar -xvf
backupfile.tar), you can then uncompress all files
from the current directory recursively down with
the following command:

find . -name \*bz2 -print0 | xargs -0 bunzip2 - Jun 27 2009
> I selected "Compress Files" in the profile settings and thought I'd get a compressed archive (for example backup.tgz).

Have a look in the online handbook, chapter "Archive compression"

> Also, I saved my backup to my backup directory and it included the temp file:

This is a bug. I have code in it which should make sure that does not happen, but it seems there was a change in behaviour between the KDE3 and KDE4 libraries, which I did not notice.
I'll check if I can fix this easily.

Thanks for your feedback! - Jun 20 2009
It should _never_ crash. I have to analyze why it did that ... - Jun 20 2009
> This file was also left (not sure what it is):

This is a temporary file used during the tar-file creation. This seems to be a KDE internal way of creating the file and when it's finished, it's renamed to the final name.

>1) Maybe it's my theme but I can't tell from a main directory checkbox if a subdirectory has something in it. I noticed however a blue outline when I ran the program as root.

Hmm ... seems to be a style thing. I defined to show the entries in a tree in blue when a directory has partly selected subitems.
What Style are you using ? What KDE version are you on ?

> 2) No idea just what "medium" means.

originally the program was written to support changeable media, e.g. ZIP-disks. A "medium" is a changeable unit, e.g. a disk.

> 3) I have no idea what the trailing numbers (following the date) in the filename mean.

It's the slice sequence number. Have a look in the online handbook chapter "Archive slices" - Jun 20 2009
I can't say. Seems to be some general KDE problem.
Are you already using KDE4 ? - Nov 07 2008
After you extracted it from the tar-file (tar -xvf backupfile.tar), you can then uncompress all files from the current directory recursively down with the following command:

find . -name \*bz2 -print0 | xargs -0 bunzip2 - Jun 17 2008
To avoid compression, uncheck the "compression" flag in the profile settings (this then avoids compression at all).
The fact I do not compress the whole archive has to do with the slice sice handling. See my reply to "Re: Individual compress "

The point for compressing all files, even already compressed ones, is that when I finally have a restore, I would not know if the file originally was already compressed or not. Now I know I can uncompress either all or none. - Mar 08 2008
hidden files before normal files is something I seem to have forgotten.
I already fixed it locally.

The sort order of the normal files (capital/non capital) is nothing I define in the application. It depends on your locale. check LC_COLLATE - Mar 08 2008
You can already specify the size you wish to use (profile settings).
The pity with Qt3/KDE3 is, that it is not possible to use larger files than 4GB.
What you have selected as size will be shown to the right of the medium progress bar (in fact it shows what size is currently possible, limited also by the local file system free space). Note: please use version 0.5.4, where the size limitations where implemented.
The size all selected files/dirs would need could be calculated - the problem with that is, that it would need a rather long time to calculate, as it would need to recursively traverse all selected dirs, therefore I don't think this is something a user wants to wait for. - Mar 01 2008
Hi, I checked the given webpage, but to be honest, I did not understand what I can use gtkatalog for.
Maybe you can describe which functionality you are thinking of. - Feb 24 2008
Hi Dan,
I think I now found the problem:
The KDE libs use Qt file operations and they are limited with file sizes to 4 Byte ... which means they simply can not deal with files larger than 4GB...
I will modify kbackup to automatically limit a single slice to that size. - Dec 22 2007
You can disable the compression completely via a profile setting.

The reason for compressing each file was the idea to allow for archive slices with a maximum size but still have compressed data.
To be able to know if a file still fits into a slice, I have to compress it before putting it into the slice, otherwise I can not know how large the slice will be when I compress the complete slice. - Oct 14 2007
You have to pass only the full path to the scriptfile, e.g.
kbackup --script /home/pierre/Documents/Scripts/RotateBackup - Oct 14 2007
I found a problem with kbackup and large files: It does not deal correctly with files larger than 2GB
I'm about to fix these problems and will release a new version in the next days. - Sep 30 2007 be able to tell what's wrong I would need the tar file for analysis ... which might be problematic here.
Could you try to make smaller backups for test and see if it works at all ? - Sep 28 2007
Ah yes. Use the following instead:

find . -name \*bz2 -print0 | xargs -0 bunzip2 - Feb 04 2007
You can use konqueror and use the right mouse button menu "Extract to...".

Or if you have all the .bz2 files, you can do the following to unzip all files from the current directory recursively down:

find . -name \*bz2 | xargs bunzip2

There is currently no direct way from within kbackup (it's on my TODO list) - Feb 03 2007
You don't need to decide the target format, it is done automatically and it chooses the best one depending on the availability (which normally will be bzip2) - Dec 23 2006
As I do not provide debian packages (I have no Debian based system), you should download the source and compile/install it.
See the included README file.
P.S.: you need to have some development packages installed, e.g. g++, kdelibs-devel, etc. - Nov 10 2006

Email 9 comments

Score 50.0%
Jun 17 2018
When it blocks/hangs - does it ever come back with any error ?
I've now added an additional handling when Qt sends me an error signal but without a finished() signal (but I don't know if that is even possible)...please test with the latest version 1.3 I've now uploaded.
If that still does not solve your issue, then I might need to implement a timer which forces an abort of the communication. - Sep 28 2013
The error tells you that the connection could not be established because of SSL errors, e.g. illegal certificates, etc.
I've uploaded a newer version where I dump the SSL errors in detail (always the first and with -debug all of them) but also in addition I always ignore SSL errors so the download should continue but you should really check the SSL errors. - Sep 27 2013
The READE tells you you'll need libwbxml2

You normally need to install the development package of it, e.g. here on my openSuse it is libwbxml2-devel - Apr 14 2013