[faeychild@unimatrix .cache]$ cd /home/faeychild/.cache/kdenlive
[faeychild@unimatrix kdenlive]$ du -d 1 -h
15G ./proxy
916K ./qmlcache
32K ./1675126989097
15G .
[faeychild@unimatrix kdenlive]$

[faeychild@unimatrix kdenlive]$ ls -la
total 20
drwxrwxr-x 5 faeychild faeychild 4096 Feb 1 12:04 .
drwxrwxr-x 26 faeychild faeychild 4096 Feb 8 14:11 ..
drwxrwxr-x 5 faeychild faeychild 4096 Feb 1 12:04 1675126989097
drwxrwxr-x 2 faeychild faeychild 4096 Feb 1 12:04 proxy
drwxrwxr-x 2 faeychild faeychild 4096 Jan 14 15:22 qmlcache
[faeychild@unimatrix kdenlive]$

I don't know what is going on? 15G is going somehwere

--
Running KDE on x86_64 5.15.88-desktop-1.mga8
Mageia release 8

On Tue, 07 Feb 2023 22:22:42 -0500, faeychild <faeychild@nomail.afraid.org> wrote:
> I don't know what is going on? 15G is going somehwere

Run "konqueror ~" (note that's a tilde, not a dash).
Select "View". Move the mouse pointer to "View Mode", then move it right and select
the "File Size View". It should be clear where the space is being used.

Regards, Dave Hodgins

On 2023-02-08, faeychild <faeychild@nomail.afraid.org> wrote:
>
>
> [faeychild@unimatrix .cache]$ cd /home/faeychild/.cache/kdenlive
> [faeychild@unimatrix kdenlive]$ du -d 1 -h
> 15G ./proxy
> 916K ./qmlcache
> 32K ./1675126989097
> 15G .
> [faeychild@unimatrix kdenlive]$
>
>
>
> [faeychild@unimatrix kdenlive]$ ls -la
> total 20
> drwxrwxr-x 5 faeychild faeychild 4096 Feb 1 12:04 .
> drwxrwxr-x 26 faeychild faeychild 4096 Feb 8 14:11 ..
> drwxrwxr-x 5 faeychild faeychild 4096 Feb 1 12:04 1675126989097
> drwxrwxr-x 2 faeychild faeychild 4096 Feb 1 12:04 proxy
> drwxrwxr-x 2 faeychild faeychild 4096 Jan 14 15:22 qmlcache

ls does not give the size of all the files in the directory. It only
gives the size of the one file that contains the contents of the
director (ie the list of ffilenames directly under the directory and
their inodes and permissions)
Try doing

du -h proxy
which will list all of the files under the directory proxy and their
sizes.

Note that the -d 1 does not limit itself to looking only at the contents
of proxy say. it sums up all of the file sizes of the files under proxy
and only reports the top levels.

For example here is one of my file hirachies

>sudo du -h tmp/Maple
4.0K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/bleach
4.0K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/bs4/tests
4.0K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/bs4/builder
12K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/bs4
4.0K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/enum
4.0K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/google/protobuf/pyext
4.0K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/google/protobuf/compiler
4.0K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/google/protobuf/internal/import_test_package
8.0K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/google/protobuf/internal
4.0K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/google/protobuf/util
24K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/google/protobuf
28K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages/google
52K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6/site-packages
56K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib/python3.6
60K tmp/Maple/local/maple2018/Python.X86_64_LINUX/Lib
64K tmp/Maple/local/maple2018/Python.X86_64_LINUX
68K tmp/Maple/local/maple2018
72K tmp/Maple/local
76K tmp/Maple
crawler:0[unruh]>sudo du -h -d1 tmp/Maple
72K tmp/Maple/local
76K tmp/Maple

Note that du -d1 /tmp/Maple reports the same numbers as du /tmp/Maple
for the two directories /tmp/Maple and /tmp/Maple/local
Plus it gives more details of what is inside /tmp/Maple:
> [faeychild@unimatrix kdenlive]$
>
>
> I don't know what is going on? 15G is going somehwere
>

On 8/2/23 14:22, faeychild wrote:
>
>
> [faeychild@unimatrix .cache]$  cd /home/faeychild/.cache/kdenlive
> [faeychild@unimatrix kdenlive]$ du -d 1 -h
> 15G     ./proxy
> 916K    ./qmlcache
> 32K     ./1675126989097
> 15G     .
> [faeychild@unimatrix kdenlive]$

Because this warning occurred during an update I had no time to maneuver
and I just deleted the ~/.cache/kdenlive folder and recovered space

The folder has not since returned. Non of my kdenlive environment
settings point to the $HOME folder
I recently reinstalled kdenlive; it normally defaults to $HOME.

Something to be mindful of next time, it seems to leave active baggage.

--
Running KDE on x86_64 5.15.88-desktop-1.mga8
Mageia release 8

On 8/2/23 17:00, David W. Hodgins wrote:
> On Tue, 07 Feb 2023 22:22:42 -0500, faeychild
> <faeychild@nomail.afraid.org> wrote:
>> I don't know what is going on?  15G is going somehwere
>
> Run "konqueror ~" (note that's a tilde, not a dash).
> Select "View". Move the mouse pointer to "View Mode", then move it right
> and select
> the "File Size View". It should be clear where the space is being used.
>
> Regards, Dave Hodgins

It has been a while since I ran konqueror. I had forgotten about it

I got a bit rattled with the diminishing folder space during an upgrade
and panicked with the space down to < 45M.

I could have done the same "File Size" thing with dolphin if I had had
the presence of mind

Regards
--
Running KDE on x86_64 5.15.88-desktop-1.mga8
Mageia release 8

On 2/8/2023 6:18 PM, faeychild wrote:
> On 8/2/23 17:00, David W. Hodgins wrote:
>> On Tue, 07 Feb 2023 22:22:42 -0500, faeychild
>> <faeychild@nomail.afraid.org> wrote:
>>> I don't know what is going on?  15G is going somehwere
>>
>> Run "konqueror ~" (note that's a tilde, not a dash).
>> Select "View". Move the mouse pointer to "View Mode", then move it
>> right and select
>> the "File Size View". It should be clear where the space is being used.
>>
>> Regards, Dave Hodgins
>
>
>
> It has been a while since I ran konqueror. I had forgotten about it
>
> I got a bit rattled with the diminishing folder space during an upgrade
> and panicked with the space down to  < 45M.
>
> I could have done the same "File Size" thing with dolphin if I had had
> the presence of mind
>
> Regards

I prefer "du | sort -n". That way I get a list from smallest to
biggest.

On Wed, 08 Feb 2023 23:16:59 -0500, red floyd <no.spam.here@its.invalid> wrote:
> I prefer "du | sort -n". That way I get a list from smallest to
> biggest.

"du -ah |sort -h" would be better, so that 1G doesn't come before 4K.

It doesn't help find a subdirectory with a very large number of small files.
The file size view mode in konqueror will make such a directory more noticeable.

Regards, Dave Hodgins

On Wed, 08 Feb 2023 21:18:58 -0500, faeychild <faeychild@nomail.afraid.org> wrote:
> It has been a while since I ran konqueror. I had forgotten about it
>
> I got a bit rattled with the diminishing folder space during an upgrade
> and panicked with the space down to < 45M.
>
> I could have done the same "File Size" thing with dolphin if I had had
> the presence of mind

Dolphin doesn't have the file size view mode, just konqueror.

Regards, Dave Hodgins

On 10/2/23 02:28, David W. Hodgins wrote:

>
> Dolphin doesn't have the file size view mode, just konqueror.
>
> Regards, Dave Hodgins

Ah Ha I am totally at cross purposes here.

God! That is information dense

I forget that konqueror is multi purpose

It was my go-to browser before I fell into the clutches of the Firefox
and I always appreciated the "dot war" file format

I still spot the occasional "war" file in an old folder

regards

--
Running KDE on x86_64 5.15.88-desktop-1.mga8
Mageia release 8

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

faeychild wrote:
>
>
> [faeychild@unimatrix .cache]$ cd /home/faeychild/.cache/kdenlive
> [faeychild@unimatrix kdenlive]$ du -d 1 -h 15G ./proxy 916K
> ./qmlcache 32K ./1675126989097 15G . [faeychild@unimatrix
> kdenlive]$
>
>
>
> [faeychild@unimatrix kdenlive]$ ls -la total 20 drwxrwxr-x 5
> faeychild faeychild 4096 Feb 1 12:04 . drwxrwxr-x 26 faeychild
> faeychild 4096 Feb 8 14:11 .. drwxrwxr-x 5 faeychild faeychild
> 4096 Feb 1 12:04 1675126989097 drwxrwxr-x 2 faeychild faeychild
> 4096 Feb 1 12:04 proxy drwxrwxr-x 2 faeychild faeychild 4096 Jan
> 14 15:22 qmlcache [faeychild@unimatrix kdenlive]$
>
>
> I don't know what is going on? 15G is going somehwere
>

You can try filelight.
- --

Abraços

Gilberto F da Silva
-----BEGIN PGP SIGNATURE-----
Comment: +-----------------------------------------------------+
Comment: ! https://t.me/Gilberto_F_da_Silva !
Comment: +-----------------------------------------------------+

iF0EARECAB0WIQR6BybJIKBLy3+8xXcnG6Ba0yEbDgUCY+wdrAAKCRAnG6Ba0yEb
DuRFAJ9wynhYGRvfZmTtYddoREzKm6nNmACcDQsJ5aU74Nnd3Q6zwzbgOZI39T8=
=RSmS
-----END PGP SIGNATURE-----

On 2/14/23 15:47, Gilberto F da Silva wrote:
> faeychild wrote:
>
>
>> [faeychild@unimatrix .cache]$ cd /home/faeychild/.cache/kdenlive
>> [faeychild@unimatrix kdenlive]$ du -d 1 -h 15G ./proxy 916K
>> ./qmlcache 32K ./1675126989097 15G . [faeychild@unimatrix
>> kdenlive]$
>
>
>
>> [faeychild@unimatrix kdenlive]$ ls -la total 20 drwxrwxr-x 5
>> faeychild faeychild 4096 Feb 1 12:04 . drwxrwxr-x 26 faeychild
>> faeychild 4096 Feb 8 14:11 .. drwxrwxr-x 5 faeychild faeychild
>> 4096 Feb 1 12:04 1675126989097 drwxrwxr-x 2 faeychild faeychild
>> 4096 Feb 1 12:04 proxy drwxrwxr-x 2 faeychild faeychild 4096 Jan
>> 14 15:22 qmlcache [faeychild@unimatrix kdenlive]$
>
>
>> I don't know what is going on? 15G is going somehwere
>
>
> You can try filelight.

Or you can open a terminal and enter the following incantation,
which should give you a sorted list of files and sizes from smallest to
largest.
du -ah |sort -h

From experts at PCLinuxOS forums who will never forget our
shared ancestry in the OS.

bliss - on the ever-faithful Dell Latitude E7450, PCLinuxOS 2022
KDE Plasma 5.26.5Kernel Version: 6.1.11-pclos1 (64-bit)
KDE Frameworks 5.102.0 - Qt Version: 5.15.6
Graphics : X11 - Mesa Intel® HD Graphics 5500
15.5 GiB of RAM CPU 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
Actually 2 real cores and 2 virtual cores.

--
bliss dash SF 4 ever at dslextreme dot com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Bobbie Sellers wrote:
> On 2/14/23 15:47, Gilberto F da Silva wrote:
>> faeychild wrote:
>>
>>
>>> [faeychild@unimatrix .cache]$ cd
>>> /home/faeychild/.cache/kdenlive [faeychild@unimatrix kdenlive]$
>>> du -d 1 -h 15G ./proxy 916K ./qmlcache 32K
>>> ./1675126989097 15G . [faeychild@unimatrix kdenlive]$
>>
>>
>>
>>> [faeychild@unimatrix kdenlive]$ ls -la total 20 drwxrwxr-x 5
>>> faeychild faeychild 4096 Feb 1 12:04 . drwxrwxr-x 26
>>> faeychild faeychild 4096 Feb 8 14:11 .. drwxrwxr-x 5
>>> faeychild faeychild 4096 Feb 1 12:04 1675126989097 drwxrwxr-x
>>> 2 faeychild faeychild 4096 Feb 1 12:04 proxy drwxrwxr-x 2
>>> faeychild faeychild 4096 Jan 14 15:22 qmlcache
>>> [faeychild@unimatrix kdenlive]$
>>
>>
>>> I don't know what is going on? 15G is going somehwere
>>
>>
>> You can try filelight.
>
> Or you can open a terminal and enter the following incantation,
> which should give you a sorted list of files and sizes from
> smallest to largest. du -ah |sort -h
>
> From experts at PCLinuxOS forums who will never forget our shared
> ancestry in the OS.
>
> bliss - on the ever-faithful Dell Latitude E7450, PCLinuxOS 2022
> KDE Plasma 5.26.5Kernel Version: 6.1.11-pclos1 (64-bit) KDE
> Frameworks 5.102.0 - Qt Version: 5.15.6 Graphics : X11 - Mesa
> Intel® HD Graphics 5500 15.5 GiB of RAM CPU 4 × Intel® Core™
> i7-5600U CPU @ 2.60GHz Actually 2 real cores and 2 virtual cores.
>

I just showed an option that maybe the person didn't know. A graphical
representation is faster and easier to understand.

- --

Abraços

Gilberto F da Silva
-----BEGIN PGP SIGNATURE-----
Comment: +-----------------------------------------------------+
Comment: ! https://t.me/Gilberto_F_da_Silva !
Comment: +-----------------------------------------------------+

iF0EARECAB0WIQR6BybJIKBLy3+8xXcnG6Ba0yEbDgUCY+wsRQAKCRAnG6Ba0yEb
DuZMAKChW4Fg4h9oi8U4zKabcNSLo3vkfQCdGVAfd/DV2OkbuxKG6gPukvGKdKU=
=bAxh
-----END PGP SIGNATURE-----

On 2023-02-15, Bobbie Sellers <bliss@mouse-potato.com> wrote:
> On 2/14/23 15:47, Gilberto F da Silva wrote:
>> faeychild wrote:
>>
>>
>>> [faeychild@unimatrix .cache]$ cd /home/faeychild/.cache/kdenlive
>>> [faeychild@unimatrix kdenlive]$ du -d 1 -h 15G ./proxy 916K
>>> ./qmlcache 32K ./1675126989097 15G . [faeychild@unimatrix
>>> kdenlive]$
>>
>>
>>
>>> [faeychild@unimatrix kdenlive]$ ls -la total 20 drwxrwxr-x 5
>>> faeychild faeychild 4096 Feb 1 12:04 . drwxrwxr-x 26 faeychild
>>> faeychild 4096 Feb 8 14:11 .. drwxrwxr-x 5 faeychild faeychild
>>> 4096 Feb 1 12:04 1675126989097 drwxrwxr-x 2 faeychild faeychild
>>> 4096 Feb 1 12:04 proxy drwxrwxr-x 2 faeychild faeychild 4096 Jan
>>> 14 15:22 qmlcache [faeychild@unimatrix kdenlive]$
>>
>>
>>> I don't know what is going on? 15G is going somehwere
>>
>>
>> You can try filelight.
>
> Or you can open a terminal and enter the following incantation,
> which should give you a sorted list of files and sizes from smallest to
> largest.
> du -ah |sort -h

Or instead of searching through all the 10000 files, why not just search
the one directory that is problematic.
du -h /name/of/theproblematic/directory|sort -h

Note that that 15G could be made up of 15000 1MB files which make them
not stand out at all. Althernatively there could be a removed file (ie
no name in any directory) which is open and is is constantly having jumk
dumped into it.

On 15/2/23 11:18, Bobbie Sellers wrote:

>     Or you can open a terminal and enter the following incantation,
> which should give you a sorted list of files and sizes from smallest to
> largest.
>     du -ah |sort -h
>

Mozilla cache is the culprit her

It needs monitoring

--
Running KDE on x86_64 5.15.88-desktop-1.mga8
Mageia release 8

On 15/2/23 11:50, Gilberto F da Silva wrote:

>
> I just showed an option that maybe the person didn't know. A graphical
> representation is faster and easier to understand.
>

Indeed !! a picture being worth a thousand words

--
Running KDE on x86_64 5.15.88-desktop-1.mga8
Mageia release 8

On 15/2/23 13:49, William Unruh wrote:

> Note that that 15G could be made up of 15000 1MB files which make them
> not stand out at all. Althernatively there could be a removed file (ie
> no name in any directory) which is open and is is constantly having jumk
> dumped into it.

That is an interesting possibility. Can that actually happen..
I understand that a file can he deleted but still accessible if a
program is holding it open.

Many years ago I read an article about deleted file recovery if the file
handle was still in play. It involved Inodes

--
Running KDE on x86_64 5.15.88-desktop-1.mga8
Mageia release 8

On 2023-02-15, faeychild <faeychild@nomail.afraid.org> wrote:
> On 15/2/23 13:49, William Unruh wrote:
>
>> Note that that 15G could be made up of 15000 1MB files which make them
>> not stand out at all. Althernatively there could be a removed file (ie
>> no name in any directory) which is open and is is constantly having jumk
>> dumped into it.
>
>
> That is an interesting possibility. Can that actually happen..
> I understand that a file can he deleted but still accessible if a
> program is holding it open.
>
> Many years ago I read an article about deleted file recovery if the file
> handle was still in play. It involved Inodes

If a program has a file open, then it uses the inode, not the name. If
the file is in use, then the inode is not freed until the program
releases the file. So that program could keep dumping junk into the
file. If you switch off the machine, then that is broken and the inode
is liberated and all of the file space is freed up.

>

On 2023-02-15 17:34, faeychild wrote:
> On 15/2/23 11:18, Bobbie Sellers wrote:
>
>>      Or you can open a terminal and enter the following incantation,
>> which should give you a sorted list of files and sizes from smallest
>> to largest.
>>      du -ah |sort -h
>>
>
>
>
> Mozilla cache is the culprit her
>
> It needs monitoring
>
There are settings within Firefox to limit the size of the cache, though
I don't remember now what they are. I'm sure a DuckDuckGo search would
turn them up.

It is also possible to move the Firefox cache to RAM, if you have enough
to spare. There are advantages and disadvantages to each strategy - it
depends on your situation. Again, a search would turn up articles that
can explain it better than I can.

In my case, VirtualBox VMs are a far bigger user of /home space than
anything else, especially now, when I have active VMs for testing both
Mageia 8 updates and Cauldron.

Just shows that everyone's needs are different.

TJ

TJ wrote on 17/2/23 3:37 am:
> On 2023-02-15 17:34, faeychild wrote:
>> On 15/2/23 11:18, Bobbie Sellers wrote:
>>
>>>      Or you can open a terminal and enter the following incantation,
>>> which should give you a sorted list of files and sizes from smallest
>>> to largest.
>>>      du -ah |sort -h
>>
>> Mozilla cache is the culprit her
>>
>> It needs monitoring
>>
> There are settings within Firefox to limit the size of the cache, though
> I don't remember now what they are. I'm sure a DuckDuckGo search would
> turn them up.

faeychild, in SeaMonkey Suite, you set the maximum size of Cache in
Preferences -> Advanced -> Set Cache Options.

I think, in Firefox, the Preferences is found on the Tools drop-down.

If you need more assistance, try alt.comp.software.firefox.
--
Daniel

On Fri, 17 Feb 2023 03:39:56 -0500, Daniel65 <daniel47@nomail.afraid.org> wrote:

> TJ wrote on 17/2/23 3:37 am:
>> On 2023-02-15 17:34, faeychild wrote:
>>> On 15/2/23 11:18, Bobbie Sellers wrote:
>>>
>>>> Or you can open a terminal and enter the following incantation,
>>>> which should give you a sorted list of files and sizes from smallest
>>>> to largest.
>>>> du -ah |sort -h
>>>
>>> Mozilla cache is the culprit her
>>>
>>> It needs monitoring
>>>
>> There are settings within Firefox to limit the size of the cache, though
>> I don't remember now what they are. I'm sure a DuckDuckGo search would
>> turn them up.
>
> faeychild, in SeaMonkey Suite, you set the maximum size of Cache in
> Preferences -> Advanced -> Set Cache Options.
>
> I think, in Firefox, the Preferences is found on the Tools drop-down.
>
> If you need more assistance, try alt.comp.software.firefox.

In firefox, open "about:config" and search on cache. There are many options
controlling it.

For chromium, it can not be controlled using the gui. Create a text file
$ cat $HOME/.config/chromium/args.txt
--disk-cache-size=1073741824

Note the leading space. The above limits the disk cache to a maximum of 1 GiB.
The size must be specified in bytes.

The args.txt file is used by the script /usr/bin/chromium to set the options
when it calls the program /usr/lib64/chromium-browser/chrome. The leading space
in the file is needed as the contents of that line are appended to the options
already set in the script. If additional poorly documented options are to be
added, either keep them on the same line, or use " \" at the end of each line
except the last, for normal bash script line continuation.
I found the chromium option at
https://superuser.com/questions/378991/what-is-chrome-default-cache-size-limit
but had to run "bash -x -v /usr/bin/chromium" to figure out the leading space
was needed in the text file.

Regards, Dave Hodgins

On 2023-02-17, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
> On Fri, 17 Feb 2023 03:39:56 -0500, Daniel65 <daniel47@nomail.afraid.org> wrote:
>
>> TJ wrote on 17/2/23 3:37 am:
>>> On 2023-02-15 17:34, faeychild wrote:
>>>> On 15/2/23 11:18, Bobbie Sellers wrote:
>>>>
>>>>> Or you can open a terminal and enter the following incantation,
>>>>> which should give you a sorted list of files and sizes from smallest
>>>>> to largest.
>>>>> du -ah |sort -h
>>>>
>>>> Mozilla cache is the culprit her
>>>>
>>>> It needs monitoring
>>>>
>>> There are settings within Firefox to limit the size of the cache, though
>>> I don't remember now what they are. I'm sure a DuckDuckGo search would
>>> turn them up.
>>
>> faeychild, in SeaMonkey Suite, you set the maximum size of Cache in
>> Preferences -> Advanced -> Set Cache Options.
>>
>> I think, in Firefox, the Preferences is found on the Tools drop-down.
>>
>> If you need more assistance, try alt.comp.software.firefox.
>
> In firefox, open "about:config" and search on cache. There are many options
> controlling it.
>
> For chromium, it can not be controlled using the gui. Create a text file
> $ cat $HOME/.config/chromium/args.txt
> --disk-cache-size=1073741824
>
> Note the leading space. The above limits the disk cache to a maximum of 1 GiB.
> The size must be specified in bytes.
>
> The args.txt file is used by the script /usr/bin/chromium to set the options
> when it calls the program /usr/lib64/chromium-browser/chrome. The leading space
> in the file is needed as the contents of that line are appended to the options
> already set in the script. If additional poorly documented options are to be
> added, either keep them on the same line, or use " \" at the end of each line
> except the last, for normal bash script line continuation.
> I found the chromium option at
> https://superuser.com/questions/378991/what-is-chrome-default-cache-size-limit
> but had to run "bash -x -v /usr/bin/chromium" to figure out the leading space
> was needed in the text file.

I guess the reason the above does not work with chrome is that the
EXTRA_ARGS and the args.txt is a special addition by the Mageia people,
which of course does not apply to chrome because the source for that
program is google, not Mageia. One could put the addtion into chrome,
but would have to redo it each time you upgraded chrome.
So you mean that it is relatively impossible to add this feature to
chrome?

On Fri, 17 Feb 2023 13:18:42 -0500, William Unruh <unruh@invalid.ca> wrote:
> I guess the reason the above does not work with chrome is that the
> EXTRA_ARGS and the args.txt is a special addition by the Mageia people,
> which of course does not apply to chrome because the source for that
> program is google, not Mageia. One could put the addtion into chrome,
> but would have to redo it each time you upgraded chrome.
> So you mean that it is relatively impossible to add this feature to
> chrome?

Correct. Google doesn't want users to control their own systems, add options
that might confuse the average windows user, have to include documentation
or --help options that explain how their stuff works, etc.

It looks like the /usr/bin/chromium script is from google, but Mageia added
the method to allow users to supply additional options. Not the way I would
have written that part of the script, but at least it does work once you
figure out how.

Regards, Dave Hodgins

On 2023-02-17, David W. Hodgins <dwhodgins@nomail.afraid.org> wrote:
> On Fri, 17 Feb 2023 13:18:42 -0500, William Unruh <unruh@invalid.ca> wrote:
>> I guess the reason the above does not work with chrome is that the
>> EXTRA_ARGS and the args.txt is a special addition by the Mageia people,
>> which of course does not apply to chrome because the source for that
>> program is google, not Mageia. One could put the addtion into chrome,
>> but would have to redo it each time you upgraded chrome.
>> So you mean that it is relatively impossible to add this feature to
>> chrome?
>
> Correct. Google doesn't want users to control their own systems, add options
> that might confuse the average windows user, have to include documentation
> or --help options that explain how their stuff works, etc.
>
> It looks like the /usr/bin/chromium script is from google, but Mageia added

Yes, it is the same as the chrome script, except for the additions at
the end to allow one to change the variables.
It looks like you can add options in chrome but they have to be handed to script.

> the method to allow users to supply additional options. Not the way I would
> have written that part of the script, but at least it does work once you
> figure out how.
>
> Regards, Dave Hodgins