Hi Achim, ignore my wrong answer - it was an c'n'p error for an other ticket. Ulf

On 2022-09-01 23:32, ub22@gmx.net wrote:

I still not able to do updates :-(

Am Samstag, 27. August 2022, 12:50:38 CEST schrieb Achim Gratz:

...

ub22@gmx.net writes:

...

after it happens the second time, I created a bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1202840

Did zypper report some error conditions about "lua triggers not installed" and then errors about glibc not at the expected revision when it failed to install the new filesystem package? If so, you might have encountered the very same problem that I have reported on the support mailing list.

I can't see anything. Due to the fact that a look in logs are not possible (after update no program/application can be started anymore and after a snapper rollback the log will be also not more accessible).

I believe snapper doesn't rollback back the logs. At least, that's what the documentation I read years ago said. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

Thanks Achim :-) Am Freitag, 2. September 2022, 09:30:45 CEST schrieb ASSI:

Am 01.09.2022 um 23:32 schrieb ub22@gmx.net:

...

I can't see anything.

The error message is really prominent in the terminal. I almost never update with the KDE applet and any big updates will be done in one of the VT consoles so that zypper doesn't die if X11 crashes or something like that.

Depends on the PC I do it via App or zypper ref / zypper dup In this case I used I used zypper --> see bug report. https://bugzilla.opensuse.org/show_bug.cgi?id=1202840 Remark: with KDE there are 3/4 options: 1. via "Software update" at yast and app linked in KDE 2. via "Discover" or similar for other desktops 3. via "zypper" 4. via "Software management" at yast I think the standard not experienced user uses 1. and some are using 2.. Some longer time openSUSE users sometimes 4. The more experienced and professional ones 3. At least I would prefer that only one should be the default for the standard not so experianced user and should automatic generate a BUG report including all relevant infos - which can be like at a KDE crash half automatic via assistant shared via eMail or "Guest User" direct included in Bugzilla.

...

Due to the fact that a look in logs are not possible (after update no program/application can be started anymore and after a snapper rollback the log will be also not more accessible).

Try the fix mentioned in the FAQ part of

https://en.opensuse.org/openSUSE:Usr_merge Why and how the UsrMerge wasn't completed much earlier on your system remains to be determined if that is the reason for your troubles.

OK, but there was nothing really helpful: # /usr/lib64/ld-linux-x86-64.so.2 /usr/bin/ln -s /usr/lib64/ld-linux-x86-64.so.2 /lib64/ld-linux-x86-64.so.2 /usr/bin/ln: failed to create symbolic link '/lib64/ld-linux-x86-64.so.2': File exists # /usr/lib64/ld-linux-x86-64.so.2 /usr/bin/ln -s /usr/lib64/libc.so.6 /lib64/libc.so.6 /usr/bin/ln: failed to create symbolic link '/lib64/libc.so.6': File exists # cd /usr; ln -s . /usr/usr OK, was working What I did (I don't know if this was an good idea - I will see after the zypper dup: # ls / bin -> usr/bin lib -> usr/lib lib64 -> usr/lib64 to # ls / bin -> /usr/bin lib -> /usr/lib lib64 -> /usr/lib64 Thanks for info Regards Ulf

H Carlos, Am Samstag, 3. September 2022, 13:14:36 CEST schrieb Carlos E. R.:

AFAIK, the only supported method with Tumbleweed is "zypper dup".

Why than the other method's are there? They should either show a warning or use "zypper dup"! Remark: Many users which are using SUSE Linux much more than 10 years are happy to use Tumbleweed to use the latest SW. But they are not Linux base system professionals (only Linux professionals) and not familiar with the CLI! Ulf

Hi Patrick, Am Samstag, 3. September 2022, 21:43:22 CEST schrieb Patrick Shanahan:

* ub22@gmx.net [09-03-22 11:11]:

...

H Carlos,

Am Samstag, 3. September 2022, 13:14:36 CEST schrieb Carlos E. R.:

...

AFAIK, the only supported method with Tumbleweed is "zypper dup".

Why than the other method's are there?

all methods are there also for Leap and the different Leap versions.

Ok

it is assumed that one takes some little bit of care about what they are doing, and many have learned, "the hard way". it's called experience.

Yep, they do. But not all of them are able to repair a damaged system. For sure it will happen, but should be not so often. We from the LUGs are supporting them for sure.

...

They should either show a warning or use "zypper dup"!

Remark: Many users which are using SUSE Linux much more than 10 years are happy to use Tumbleweed to use the latest SW. But they are not Linux base system professionals (only Linux professionals) and not familiar with the CLI!

Ulf

sorry state that someone uses a distro for >10 years w/o learning *something* about it.

Yep, they are only users. Some of them are not the youngest (at least in Germany many Linux users are started with an age of > 60 years). At least in my LUG there are one lady using Linux since about 20 years and Tumbleweed since about 5 years. She is > 80 years old. For sure she knows a lot of the system. But mainly from desktop and application point of view (she is our Video expert ;-) )

no one can save you from yourself!

Yes, that's clear. But it shouldn't be the default and the support need to be always friendly ;-) Ulf

On 2022-09-03 17:09, ub22@gmx.net wrote:

H Carlos,

Am Samstag, 3. September 2022, 13:14:36 CEST schrieb Carlos E. R.:

...

AFAIK, the only supported method with Tumbleweed is "zypper dup".

Why than the other method's are there?

Because the distro, after all, must have all the tools Leap has. They have to be developed and tested somewhere.

They should either show a warning or use "zypper dup"!

Or document it well.

Remark: Many users which are using SUSE Linux much more than 10 years are happy to use Tumbleweed to use the latest SW. But they are not Linux base system professionals (only Linux professionals) and not familiar with the CLI!

IMHO, Tumbleweed is not for novices. It is aimed at users that can solve many problems on their own, with some admin knowledge. This, I think, was posted at some web page long ago but may have disappeared: after all, nobody wants to scare users away ;-) -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

Hi Patrick, Am Samstag, 3. September 2022, 21:59:16 CEST schrieb Patrick Shanahan:

...

IMHO, Tumbleweed is not for novices. It is aimed at users that can solve many problems on their own, with some admin knowledge. This, I think, was posted at some web page long ago but may have disappeared: after all, nobody wants to scare users away ;-)

any distro including windoz requires more than just sitting in front of the box. could you drive a car w/o some training and practice and care and you even had to obtain a license.

Yep, you need a driving license to use a care. But the car should work reliable and you don't need to be a car mechanics or car electronics (in the future more car SW developer ;-) ) But why always comparing other OS with Linux? Linux based systems are different but the should be also relay reliable and usable with a nice and stable SW ergonomic (during my study as Ingenieur-Informatik time there was a dedicated curse for this). Remark: Today I'm working as HW-architect for truck control units running with Linux and other OS - so I know what I talk about the comparison with cars ;-)) Ulf

Hi Carlos (and also Patrick and all Tumbleweed team members) Am Sonntag, 4. September 2022, 13:09:32 CEST schrieb Carlos E. R.:

What I say is, Tumbleweed is not for novices. The user can not be a plain user, must know something about repairs, because Tumbleweed is expected to break now and then.

See https://en.opensuse.org/Portal:Tumbleweed | Any user who wishes to have newer packages than are available in the I would assume there no IT study required. | openSUSE Leap repositories. This includes, but is not limited to, an updated | Linux kernel, SAMBA, git, desktops, office applications and many other | packages. | | Also, Tumbleweed should appeal most to Power Users, Software Developers (who | require the latest software stacks and IDEs) and openSUSE Contributors (who | need a reliable platform that is as close to openSUSE Factory as possible | while remaining usable). OK, but like I told you, what is a "power user"? According Wikipedia it is not 100% defined https://en.wikipedia.org/wiki/Power_user

Unfortunately, with Windows you can get a nephew or friend or neighbour to help. Everybody learns how to use Windows at school time. It is easy to get help. You can take the machine to a shop to have it "repaired". With Linux... Meh, you are often alone.

I don't say, that me and other Tumbleweed users in my LUG are newbies. The most of them uses Linux > 10 years (like I told in an other mail of this thread) and know the slightly higher risk. Especially they know, that I'm normally able to help them in case of trouble. I see no special problem that the risk of a damaged system is higher than with e.g. an LTS package. But according my experiance Tumbleweed is much more stable as Manjaro rolling release anyhow you use the standard stable settings. But why you think I would attack you, that's not the case. I hope that either Tumbleweed or in the future ALP/MicroOS Tumbleweed will be the really "Power User" but low IT specialist friendly solution. My intention was not blame you or others out of the team, I only will help you to improve the quality of TW! *you and all developers and other community members which supports Tumbleweed do a very good job* *Many thanks all Tumbleweed contributors* Best Regards Ulf

* ub22@gmx.net [09-04-22 06:46]:

Hi Patrick,

Am Samstag, 3. September 2022, 21:59:16 CEST schrieb Patrick Shanahan:

...

...

IMHO, Tumbleweed is not for novices. It is aimed at users that can solve many problems on their own, with some admin knowledge. This, I think, was posted at some web page long ago but may have disappeared: after all, nobody wants to scare users away ;-)

any distro including windoz requires more than just sitting in front of the box. could you drive a car w/o some training and practice and care and you even had to obtain a license.

Yep, you need a driving license to use a care. But the car should work reliable and you don't need to be a car mechanics or car electronics (in the future more car SW developer ;-) )

how to use the key if one how the gears work or how to select a gear how to turn on the windshield wiper how to fill the gas tank what type of gas/petrol to use many things more than just sitting at the steering wheel

But why always comparing other OS with Linux? Linux based systems are different but the should be also relay reliable and usable with a nice and stable SW ergonomic (during my study as Ingenieur-Informatik time there was a dedicated curse for this).

all OSs not just linux. there are others.

Remark: Today I'm working as HW-architect for truck control units running with Linux and other OS - so I know what I talk about the comparison with cars ;-))

and I worked 40 years for GM. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

* Carlos E. R. [09-04-22 14:45]:

On 2022-09-04 16:29, Patrick Shanahan wrote:

...

* ub22@gmx.net [09-04-22 06:46]:

...

Hi Patrick,

Am Samstag, 3. September 2022, 21:59:16 CEST schrieb Patrick Shanahan:

...

...

IMHO, Tumbleweed is not for novices. It is aimed at users that can solve many problems on their own, with some admin knowledge. This, I think, was posted at some web page long ago but may have disappeared: after all, nobody wants to scare users away ;-)

any distro including windoz requires more than just sitting in front of the box. could you drive a car w/o some training and practice and care and you even had to obtain a license.

Yep, you need a driving license to use a care. But the car should work reliable and you don't need to be a car mechanics or car electronics (in the future more car SW developer ;-) )

how to use the key if one how the gears work or how to select a gear

Over here, gears are part of the exam.

which means that one must learn to use the gears, or does the exam do that for you?

...

how to turn on the windshield wiper how to fill the gas tank what type of gas/petrol to use many things more than just sitting at the steering wheel

And I know drivers that do not know how to fill the tank, so they go to manned stations.

an if no "manned stations" are available. I cannot tell you where to find a "manned" station here.

And, there are some cars where opening the hood is forbidden to the owner/driver.

***unbelievable*** maybe *only* in Spain. makes sense thou, goes along with the water. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc

On 2022-09-03 17:18, ub22@gmx.net wrote:

Am Freitag, 2. September 2022, 09:30:45 CEST schrieb ASSI:

...

Am 01.09.2022 um 23:32 schrieb ub22@gmx.net:

After the changes (see previous mail) and a new zypper dup:

( 32/5869) Installing: file-5.42-3.2.x86_64 ................................................[done] error: unpacking of archive failed on file /root/bin: cpio: chown failed - Device or resource busy error: filesystem-84.87-7.1.x86_64: install failed error: filesystem-84.87-6.1.x86_64: erase skipped ( 33/5869) Installing: filesystem-84.87-7.1.x86_64 .........................................[error] Installation of filesystem-84.87-7.1.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): r error: unpacking of archive failed on file /root/bin: cpio: chown failed - Device or resource busy error: filesystem-84.87-7.1.x86_64: install failed error: filesystem-84.87-6.1.x86_64: erase skipped ( 33/5869) Installing: filesystem-84.87-7.1.x86_64 .........................................[error] Installation of filesystem-84.87-7.1.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): i ( 34/5869) Installing: findutils-lang-4.9.0-1.9.noarch ......................................[done]

I don't know what this error exactly means. Me, I would download the filesystem-84.87-7.1.x86_64 rpm somewhere (manually) (it may be cached locally), and install it (rather update) manually with the rpm command, which will be more verbose. It worked for me not long ago with another problem I had. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

On 2022-09-03 23:27, Jan Engelhardt wrote:

On Saturday 2022-09-03 21:56, Carlos E. R. wrote:

...

...

................................................[done] error: unpacking of archive failed on file /root/bin: cpio: chown failed - error: Device or resource busy

I don't know what this error exactly means. Me, I would download the filesystem-84.87-7.1.x86_64 rpm somewhere (manually) (it may be cached locally), and install it (rather update) manually with the rpm command, which will be more verbose.

Given zypp just calls /bin/rpm anyway, this should already be the same message that rpm would output.

In theory. Zypper doesn't output the whole text, it calls a library, not the command, I understand. The fact is, when it happened to me, calling rpm directly I got a lot more text. -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

Am Samstag, 3. September 2022, 21:56:18 CEST schrieb Carlos E. R.:

On 2022-09-03 17:18, ub22@gmx.net wrote:

I don't know what this error exactly means. Me, I would download the filesystem-84.87-7.1.x86_64 rpm somewhere (manually) (it may be cached locally), and install it (rather update) manually with the rpm command, which will be more verbose.

It worked for me not long ago with another problem I had.

So I expect to follow your proposal # zypper cc -a # zypper ref ; unmount ~/bin ; zypper dup --download-in-advance --allow-vendor-change ; mount ~/bin Retrieving repository 'Mozilla' metadata ............................................................................................................................[done] Building repository 'Mozilla' cache .................................................................................................................................[done] Retrieving repository 'Haupt-Repository (NON-OSS)' metadata .........................................................................................................[done] Building repository 'Haupt-Repository (NON-OSS)' cache ..............................................................................................................[done] Retrieving repository 'Haupt-Repository (OSS)' metadata .............................................................................................................[done] Building repository 'Haupt-Repository (OSS)' cache ..................................................................................................................[done] Retrieving repository 'Hauptaktualisierungs-Repository' metadata ....................................................................................................[done] Building repository 'Hauptaktualisierungs-Repository' cache .........................................................................................................[done] Retrieving repository 'packman' metadata ............................................................................................................................[done] Building repository 'packman' cache .................................................................................................................................[done] All repositories have been refreshed. Error: Try the command: umount Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... The following package is going to be upgraded: filesystem 1 package to upgrade. Overall download size: 67.7 KiB. Already cached: 0 B. No additional space will be used or freed after the operation. Continue? [y/n/v/...? shows all options] (y): Retrieving package filesystem-84.87-7.1.x86_64 (1/1), 67.7 KiB ( 1.3 KiB unpacked) Retrieving: filesystem-84.87-7.1.x86_64.rpm .........................................................................................................................[done] Checking for file conflicts: ........................................................................................................................................[done] error: unpacking of archive failed on file /root/bin: cpio: chown failed - Device or resource busy error: filesystem-84.87-7.1.x86_64: install failed error: filesystem-84.87-6.1.x86_64: erase skipped (1/1) Installing: filesystem-84.87-7.1.x86_64 ......................................................................................................................[error] Installation of filesystem-84.87-7.1.x86_64 failed: Error: Subprocess failed. Error: RPM failed: Command exited with status 1. Abort, retry, ignore? [a/r/i] (a): Problem occurred during or after installation or removal of packages: Installation has been aborted as directed. Please see the above error message for a hint. but I'm not sure if it to deinstall the old package like proposed at: https://www.reddit.com/r/openSUSE/comments/7mkmjw/how_do_i_remove_orphaned_p... I tested also: # zypper in --download-only filesystem Loading repository data... Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: filesystem 1 package to upgrade. Overall download size: 0 B. Already cached: 67.7 KiB. Download only. Continue? [y/n/v/...? shows all options] (y): In cache filesystem-84.87-7.1.x86_64.rpm (1/1), 67.7 KiB ( 1.3 KiB unpacked) # find /var/cache/zypp -iname "filesystem*rpm" /var/cache/zypp/packages/download.opensuse.org-oss/x86_64/filesystem-84.87-7.1.x86_64.rpm # rpm -ivh /var/cache/zypp/packages/download.opensuse.org-oss/x86_64/filesystem-84.87-7.1.x86_64.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:filesystem-84.87-7.1 ################################# [100%] error: unpacking of archive failed on file /root/bin: cpio: chown failed - Device or resource busy error: filesystem-84.87-7.1.x86_64: install failed # journalctl -xe Sep 04 13:05:14 peterle [RPM][9453]: Transaction ID 6314866a started Sep 04 13:05:14 peterle [RPM][9453]: install filesystem-84.87-7.1.x86_64: success Sep 04 13:05:14 peterle [RPM][9453]: install filesystem-84.87-7.1.x86_64: failure Sep 04 13:05:14 peterle [RPM][9453]: 1 elements failed, 0 scripts failed Sep 04 13:05:14 peterle [RPM][9453]: Transaction ID 6314866a finished: -1 # rpm -Uvh /var/cache/zypp/packages/download.opensuse.org-oss/x86_64/filesystem-84.87-7.1.x86_64.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:filesystem-84.87-7.1 ################################# [ 50%] error: unpacking of archive failed on file /root/bin: cpio: chown failed - Device or resource busy error: filesystem-84.87-7.1.x86_64: install failed error: filesystem-84.87-6.1.x86_64: erase skipped # journalctl -xe | tail Sep 04 13:07:51 peterle [RPM][11064]: Transaction ID 63148707 started Sep 04 13:07:51 peterle [RPM][11064]: install filesystem-84.87-7.1.x86_64: success Sep 04 13:07:51 peterle [RPM][11064]: erase filesystem-84.87-6.1.x86_64: success Sep 04 13:07:51 peterle [RPM][11064]: install filesystem-84.87-7.1.x86_64: failure Sep 04 13:07:51 peterle [RPM][11064]: 1 elements failed, 0 scripts failed Sep 04 13:07:51 peterle [RPM][11064]: Transaction ID 63148707 finished: -1 No further idea :-( But benefit - I can meanwhile install all other packages :-) thanks to ASSI (Achim) Ulf

Hi Carlos :-), ASSI (Achim) and all many thanks *solved* details see below Am Sonntag, 4. September 2022, 13:21:55 CEST schrieb Carlos E. R.:

On 2022-09-04 13:09, ub22@gmx.net wrote:

...

Am Samstag, 3. September 2022, 21:56:18 CEST schrieb Carlos E. R.:

...

On 2022-09-03 17:18, ub22@gmx.net wrote: # rpm -ivh /var/cache/zypp/packages/download.opensuse.org-oss/x86_64/filesystem-84.8> > 7-7.1.x86_64.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:filesystem-84.87-7.1 ################################# [100%]

...

error: unpacking of archive failed on file /root/bin: cpio: chown failed - *Ahh.. why I've not seen it before - /root/bin ^^^^^^^^^ was not able to unmount!*

...

Device or resource busy error: filesystem-84.87-7.1.x86_64: install failed

Oh :-(

*Upps.. I saw it - the problem is that ~/bin was not really unmounted* # lsof ~/bin lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. lsof: WARNING: can't stat() fuse.portal file system /run/user/1000/doc Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME watch_new 13762 root 255r REG 0,64 42322 18314290398 /root/bin/watch_new.sh (192.168.2.2:/home/users/Gemeinsame_Dokumente/bin) *^^^^^^^^^ - ups my monitoring script is blocking to unmount ~/bin !!!* *OK stopped watch_new.sh and it looks better :-D* # rpm -Uvh /var/cache/zypp/packages/download.opensuse.org-oss/x86_64/filesystem-84.87-7.1.x86_64.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:filesystem-84.87-7.1 ################################# [ 50%] Cleaning up / removing... 2:filesystem-84.87-6.1 ################################# [100%] # zypper ref ; unmount ~/bin ; zypper dup --download-in-advance --allow-vendor-change ; mount ~/bin Repository 'Mozilla' is up to date. Repository 'Haupt-Repository (NON-OSS)' is up to date. Repository 'Haupt-Repository (OSS)' is up to date. Repository 'Hauptaktualisierungs-Repository' is up to date. Repository 'packman' is up to date. All repositories have been refreshed. Error: Try the command: umount Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Nothing to do. *Tschacka :-) - solved* *New future comand line for zypper dup: # zypper ref ; unmount ~/bin && zypper dup --download-in-advance --allow-vendor-change ; mount ~/bin

You could try:

-v, --verbose Print verbose information - normally routine progress messages will be displayed.

-vv Print lots of ugly debugging information.

??

OK, like in other CLI tools too. But not required anymore - so issue closed Regards Ulf

On 2022-09-04 14:33, ub22@gmx.net wrote:

Hi Carlos :-), ASSI (Achim) and all

many thanks *solved* details see below

Am Sonntag, 4. September 2022, 13:21:55 CEST schrieb Carlos E. R.:

...

On 2022-09-04 13:09, ub22@gmx.net wrote:

...

Am Samstag, 3. September 2022, 21:56:18 CEST schrieb Carlos E. R.:

...

On 2022-09-03 17:18, ub22@gmx.net wrote: # rpm -ivh /var/cache/zypp/packages/download.opensuse.org-oss/x86_64/filesystem-84.8> > 7-7.1.x86_64.rpm Verifying... ################################# [100%] Preparing... ################################# [100%] Updating / installing... 1:filesystem-84.87-7.1 ################################# [100%]

...

error: unpacking of archive failed on file /root/bin: cpio: chown failed - *Ahh.. why I've not seen it before - /root/bin ^^^^^^^^^ was not able to unmount!*

I saw it, but did not know its significance. It baffled me. ...

*Tschacka :-) - solved*

:-)) -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

Am Dienstag, 6. September 2022, 09:39:35 CEST schrieb Achim Gratz:

ub22@gmx.net writes:

...

*Upps.. I saw it - the problem is that ~/bin was not really unmounted*

Why does your root account has something mounted at ~/bin

So all my desktop PCs uses the same scripts, which are partly running in /etc/ cron.* and in crontab. The newest version is available on my Server at myserver:/home/ This will be mounted via system daemon /etc/systemd/system/home.server.mount Afterwards in /etc/fstab I mount it via bind /home.maxi/bin /root/bin none bind 0 0 To have all scirpt savailable on all Desktops/Notebooks Remark: I had the issue in the past and there was the proposal to do it like this.

and why is that (apparently) in front of the system path components?

I don't know what you mean with "system path components" Best Regards Ulf

Am Mittwoch, 7. September 2022, 14:36:26 CEST schrieb Carlos E. R.:

cer@Telcontar:~> echo $PATH /home/cer/bin:/usr/local/bin:/usr/bin:/bin:/opt/kde3/bin:/usr/lib/mit/bin:/u sr/lib/mit/sbin:/usr/sbin:/usr/sbin cer@Telcontar:~>

# echo ${PATH} /sbin:/usr/sbin:/usr/local/sbin:/root/.local/bin:/root/bin:/usr/local/bin:/ usr/bin:/bin # -- Ulf

Am Mittwoch, 7. September 2022, 22:25:27 CEST schrieb Carlos E. R.:

On 2022-09-07 21:19, ub22@gmx.net wrote:

...

Am Mittwoch, 7. September 2022, 14:36:26 CEST schrieb Carlos E. R.:

...

cer@Telcontar:~> echo $PATH /home/cer/bin:/usr/local/bin:/usr/bin:/bin:/opt/kde3/bin:/usr/lib/mit/bin :/usr/lib/mit/sbin:/usr/sbin:/usr/sbin

cer@Telcontar:~>

# echo ${PATH} /sbin:/usr/sbin:/usr/local/sbin:/root/.local/bin:/root/bin:/usr/local/bin: /usr/bin:/bin #

There it is "/root/..." entries are before some other entries.

This is similar on all my Tumbleweed systems, this is from my Server # echo $PATH /sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/home/ bin/ Remark: I don't change anything in the /etc/profile (which I think is the source of the PATH settings). In my ~/.bashrc I typically add then my personal path like /home/bin/ via export PATH=${PATH}:/home/bin (Remark: I don't really use /home/bin) Ulf

* Patrick Shanahan [09-07-22 17:32]:

* ub22@gmx.net [09-07-22 17:14]:

...

Am Mittwoch, 7. September 2022, 22:25:27 CEST schrieb Carlos E. R.:

...

On 2022-09-07 21:19, ub22@gmx.net wrote:

...

Am Mittwoch, 7. September 2022, 14:36:26 CEST schrieb Carlos E. R.:

...

cer@Telcontar:~> echo $PATH /home/cer/bin:/usr/local/bin:/usr/bin:/bin:/opt/kde3/bin:/usr/lib/mit/bin :/usr/lib/mit/sbin:/usr/sbin:/usr/sbin

cer@Telcontar:~>

# echo ${PATH} /sbin:/usr/sbin:/usr/local/sbin:/root/.local/bin:/root/bin:/usr/local/bin: /usr/bin:/bin #

There it is "/root/..." entries are before some other entries.

This is similar on all my Tumbleweed systems, this is from my Server # echo $PATH /sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/home/ bin/

Remark: I don't change anything in the /etc/profile (which I think is the source of the PATH settings). In my ~/.bashrc I typically add then my personal path like /home/bin/ via export PATH=${PATH}:/home/bin

(Remark: I don't really use /home/bin)

it is correct that your $PATH has been changed for what-ever reason and may be the entire cause of your problems. I have many machines and none have /sbin or /usr/sbin in the front. and I long ago added ~/bin to the front of my $PATH before ~/.local/bin was a thing.

echo $PATH /home/paka/bin:/home/paka/.local/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin

why don't you try changing $PATH as presented to you and see if it offers you some relief? if not, your conversation here is only for your own benefit.

ps: your "export PATH=${PATH}:/home/bin" is also a mystery, "export PATH=/home/bin;${PATH} -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc