The Settings in k4dirstat allow you to change both the menu title and the command to open the selected directory.

So, changing

Konqueror

to

Dolphin

and

kmfclient openURL %p

to

dolphin --select %n

... makes the correct file manager's name display in the Menu Bar and it produces the desired action -- opening the highlighted directory in a new instance of Dolphin.

But, as soon the utility is closed, and then reopened, the changes are gone and it's back to the defaults.

Thinking it was a file permissions problem, I tried opening k4dirstat from terminal, as root, repeating the above edits, closing, reopening -- but it's the same -- it resets itself back to the Konqueror commands when reopened.

Can anyone here duplicate this problem and advise me as to what is happening?

I can confirm - It appears that the changes are not being saved into the rc file, would be saved into ~/.config/k4dirstatrc

you will need to contact the dev as to why this behavior

your default file manager is set to Konqueror? why not set it to Dolphin?

google01103 wrote:... your default file manager is set to Konqueror? why not set it to Dolphin?

Didn't know this would be possible.
Would you advise this be done through the utility's GUI, or a manual edit of k4dirstatrc?

On the first option, where would this be done? It's probably right there, but I didn't see it ...

As a side matter, would you say the terminal command I gave, for starting Dolphin with a specified directory, looks correct?

to change default apps: systemsettings -> default applications -> file manager

the command looks correct, but the command opens Dolphin in your /home with the selected folder highlighted (keywork "select"), try

Code: Select all

dolphin %n

google01103 wrote:to change default apps: systemsettings -> default applications -> file manager ...

That is strange.

I am looking at the window titled, 'Default Applications - System Settings' and as 'Default Component' it shows:

Browse directories using the following file manager:
[o] Dolphin

There is a second choice, but it is not checked: K4DirStat.

Also,
/home/ron/.config does not contain a file named k4dirstatrc -- on my system. How could this be?

in krunner run

Code: Select all

kbuildsycoca4 --noincremental  2> /dev/null

also try removing the Konqueror package

default applications appear to be controlled with the file ~/.local/share/applications/mimeapps.list

While doing what you suggested, to 'clean-out' the remains of Konqueror, when I'm in this directory, in Dolphin -

/home/ron/.config

and type

k4dir

kde.org is highlighted, and nothing else.

Would this indicate that the utility's configuration file is not here? I was looking for it so I could check its permissions -- but now I can't find the file itself.

Maybe I should also mention that the contents of my root partition (its on a separate volume) have expanded (for some reason?) until I now have 0% free space. This is the reason for the interest in this utility, to analyse and correct this problem. Could this be causing abnormal behavior of K4DirStat, I wonder?

that's where it is for me, it could be that for whatever reason there was no reason for it to be created

re root space:
start with the following folders which you can delete with console

/tmp
/var/tmp
/var/crash
/var/log

what size is your / ?

could it be when installing packages you don't delete them and they have grown ? no idea where Mint keeps them

if you are having problems running programs because of the lack of space on toot partition you can run a live cd to clean it out

google01103 wrote:... what size is your / ?

18GiB.

You've given me some good ideas and I think I should follow them to see if the abnormal behavior of K4DirStat may be connected with this. I found out about the partition size problem when print jobs started entering, but not leaving, the printer queue. Maybe it can cause other problems, as well.

I have noted your advice and will run PartedMagic to do some 'surgery', after finding out why root is so full -- then, if it's growing for a good reason, I can enlarge it. I didn't think root had to be so big from my reading prior to installing the OS, but maybe I erred on the 'too-small' side.

On where Mint keeps its packages, a good point, and I can easily find that on the Mint forum.

Let me work on this, and then come back to K4DirStat to see if that fixes the problem.

Thanks so much for your pointers -- the KDE community is really great!!

18gb should be a decent amount for / unless you install lots of desktop environments and dev tools and even then I would think you would be fine

also look at /opt

google01103 wrote:18gb should be a decent amount for / unless you install lots of desktop environments and dev tools and even then I would think you would be fine

I think I found the problem, or at least, one part of the problem. There are two files in /root that together are using up 99.9% of the available space (according to that line, in K4DirStat) in the /root partition, named and located as follows:
/root/.linuxmint/mintinstall/reviews.list
/root/.linuxmint/mintinstall/reviews.list.tmp

Edit: K4DirStat says 'files' are taking up over 99% of 'something', but it couldn't be the root volume, because together the two files add up to 9.2MB. So they are very large, but not so large as to give the 99% figure. Possibly other 'files' are being added to get this total. I am very new to K4DirStat and likely don't know how to read it ...

By the name of the directory containing the files, this is obviously something peculiar to mint, so I've posted that 'over there'.

... also look at /opt

/opt is 59.3MiB with 17 files and 13 subdirectories. Here we have program files for:

firefox
FoxitReader
LastPass
nymgo
Telegram

You raise a good point, in asking about /opt. This is a bulky directory, and I can't see why application files ('software') should be stored in an operating system partition. I've always used a separate volume for applications, even with the Microsoft operating systems. I see there is considerable discussion of moving /opt out of /root, for example in this (somewhat dated) post.
Any comments on this new information will be greatly appreciated!

the 99.9% is amount taken up in that folder

for you to get what you want out of K4dirstat you would need to select / and it will process all sub-folders including /home if it is mounted but you which will probably take excessive time and might be a bit weildy because of the number of folders and files

try this command which will show bytes in each top level folder under / (this assumes partitions are only / and /home)

Code: Select all

du -s /* --exclude=/home/*

results will be in bytes, after determining where the usage is change the command to determine what subfolders are using the space
ex

Code: Select all

du -s /var/* --exclude=/home/*

Sorry for the delay -- busy over the weekend.

I have done the above and the problem is not in the root directory, as you correctly guessed, but especially in two others, sharing the root partition.
After ~ > sudo du -s /* --exclude=/home/* I see, among other points, these:

609580655 /media
33908086 /mnt

Mint primarily mounts in /media.

Is it the mountpoints? Is there some way of controlling what mounts when I boot? I have triple-boot and there's no need to load system paritions, program partitions for the other operating systems. But, everything seems to be mounting automatically whenever I boot.

Any advice will be appreciated.

/mnt and /media I thought were no longer used, they were for removable devices that are now mounted in/var/run/media/ - at least in the latest distros (don't use Minit so.....)

the other / folders (other than /home) they don't account for the used disk?

what are in /mnt and /media ?

mounting the other system partitions should not take up space in your root partition

what is the results of the du command I gave you?

most importantly what is the result of

Code: Select all

df -k

Thanks for the fast reply!

google01103 wrote:the other / folders (other than /home) they don't account for the used disk?
/media seemed quite large ... that was a clipped portion I posted, from terminal output, when running the command you gave.
what are in /mnt and /media ?
in /media, there's floppy0, floppy1, then my username and under that a listing of all mounted drives -- in dolphin. I can't duplicate that listing in terminal, however. Baobab just shows a gray circle for that directiory and gives no further information.
...mounting the other system partitions should not take up space in your root partition...

what is the results of the du command I gave you?
The previous snips were copied from terminal output from the command you gave me. This shows the command, and the the entire result, from which the 'snips' were taken:

Code: Select all

~ > sudo du -s /* --exclude=/home/*
[sudo] password for ron:
9524    /bin
42136   /boot
4       /cdrom
4       /dev
32788   /etc
4       /home
0       /initrd.img
254604  /lib
16      /lost+found
609580655       /media*
33908086        /mnt*
60780   /opt
du: cannot access ‘/proc/4816/task/4816/fd/3’: No such file or directory
du: cannot access ‘/proc/4816/task/4816/fdinfo/3’: No such file or directory
du: cannot access ‘/proc/4816/fd/3’: No such file or directory
du: cannot access ‘/proc/4816/fdinfo/3’: No such file or directory
0       /proc
17792   /root
2676    /run
12700   /sbin
4       /srv
0       /sys
2600    /tmp
5248844 /usr*
1021748 /var*
0       /vmlinuz

I only added the asterisks as a reminder to me, of which were the largest file sizes.


most importantly what is the result of

Code: Select all

df -k

~ >

Code: Select all

df -k
Filesystem     1K-blocks      Used Available Use% Mounted on
/dev/sdb9       16699784  15584276    244196  99% /
none                   4         0         4   0% /sys/fs/cgroup
udev             1018092         4   1018088   1% /dev
tmpfs             206392      1540    204852   1% /run
none                5120         0      5120   0% /run/lock
none             1031952      1128   1030824   1% /run/shm
none              102400         8    102392   1% /run/user
/dev/sdb3        1650952     44588   1522500   3% /boot
/dev/sda5       41587248  13816132  25635568  36% /mnt/back-in-time
/dev/sda6      207881792  14678380 182620532   8% /mnt/system-back
/dev/sdb7        8409084   5642200   2766884  68% /mnt/Data
/dev/sdb10      49484532   8751892  38195892  19% /home
/dev/sdc1       80334832  74398296   5936536  93% /media/ron/FMT_14NOV03
/dev/sde9        4928492    824956   4103536  17% /media/ron/DVD Private
/dev/sde8        4928492   2733524   2194968  56% /media/ron/DVD Public
/dev/sde7         716783    659462     57321  93% /media/ron/CD Private
/dev/sde6         716783    704919     11864  99% /media/ron/CD Public
/dev/sde5        7679980    641192   7038788   9% /media/ron/SD card management
/dev/sdb6       12955644   4097116   8858528  32% /media/ron/Win7_Programs
/dev/sdb5       13317848   9782296   3535552  74% /media/ron/Programs
/dev/sdb8       51206140  18404860  32801280  36% /media/ron/Misc
/dev/sdb2       30715900  25635436   5080464  84% /media/ron/Win7
/dev/sdb1        7388156   5467212   1920944  74% /media/ron/Win2000
/dev/sde1      293600236 141945312 151654924  49% /media/ron/FMT_04JUN10
/dev/sda2      250877748  65419488 172691336  28% /media/ron/WinOS_bk-ups
/dev/sda3      212040700   3644940 208395760   2% /media/ron/Seagate 1TB Expansion-4
/dev/sda1      255991928 160247112  95744816  63% /media/ron/Seagate3-extUSB-1TB-part1
/dev/sdd2      307204092  76131116 231072976  25% /media/ron/Seagate2-extUSB-1TB-part2
/dev/sdd1      307199992  13527116 293672876   5% /media/ron/Seagate2-extUSB-1TB-part1
/dev/sdd3      362354104   7674212 354679892   3% /media/ron/Seagate2-extUSB-1TB-part3