That is nice and ok, but does it help to figure out why the automatic switch from libhd25 to libhd26 on the TO’s system does not work?
I picked out one of the packges from the TO’s system which is marked as “System package” as it depends on libhd25 (indirectly through ntfs-3g -> ntfsprogs -> libntfs-3g90 ->libhd2*) whereas the updated packages depend on libhd26.
No.
I guess that the real question is how this “simply installing again” was done.
Yep, if it is a fresh install, there shouldn’t be libhd25 at all. libhd26 is available since June 2026.
I’ll install pdfmixtool.
About installation 99.9% I installed (years ago) Tumbleweed in the partition where I had 15.4 formatting it. Usually I format always root partition when install.
Tried first zypper dup because is easy but I get same message I had before.
~> zypper pa --orphaned
Loading repository data...
Reading installed packages...
S | Repository | Name | Version | Arch
---+------------+------------------------------------------+-----------------------------------------+-------
i+ | @System | boost-license1_91_0 | 1.91.0-4.1 | noarch
i+ | @System | cnijfilter2 | 5.70-1 | x86_64
i+ | @System | epsonscan2 | 6.7.65.0-1 | x86_64
i+ | @System | epsonscan2-non-free-plugin | 1.0.0.6-1 | x86_64
i+ | @System | libbluray3 | 1.4.1-1.3 | x86_64
i+ | @System | libboost_filesystem1_91_0 | 1.91.0-4.1 | x86_64
i+ | @System | libboost_filesystem1_91_0-x86-64-v3 | 1.91.0-4.1 | x86_64
i+ | @System | libboost_iostreams1_91_0 | 1.91.0-4.1 | x86_64
i+ | @System | libboost_iostreams1_91_0-x86-64-v3 | 1.91.0-4.1 | x86_64
i+ | @System | libboost_locale1_91_0 | 1.91.0-4.1 | x86_64
i+ | @System | libboost_locale1_91_0-x86-64-v3 | 1.91.0-4.1 | x86_64
i+ | @System | libboost_program_options1_91_0 | 1.91.0-4.1 | x86_64
i+ | @System | libboost_program_options1_91_0-x86-64-v3 | 1.91.0-4.1 | x86_64
i+ | @System | libboost_thread1_91_0 | 1.91.0-4.1 | x86_64
i+ | @System | libboost_thread1_91_0-x86-64-v3 | 1.91.0-4.1 | x86_64
i+ | @System | libdvdcss2 | 1.4.3+3-12.6 | x86_64
i+ | @System | libgpgme11 | 1.24.3-2.1 | x86_64
i+ | @System | libgpgmepp6 | 1.24.3-2.1 | x86_64
i | @System | libkdecorations3private1 | 6.3.1-1.1 | x86_64
i | @System | libopenh264-7 | 2.3.1-2.suse1699.101 | x86_64
i | @System | libopenjph0_31 | 0.31.0-1.1 | x86_64
i+ | @System | libopenshot31 | 1.0.0-1.3 | x86_64
i | @System | libpoppler146 | 25.02.0-1.2 | x86_64
i | @System | libpoppler147 | 25.03.0-1.1 | x86_64
i+ | @System | libpoppler162 | 26.07.0-1.2 | x86_64
i+ | @System | libprotobuf-lite34_2_0 | 34.2-1.4 | x86_64
i | @System | libprotobuf-lite36_1_0 | 36.1-1.1 | x86_64
i+ | @System | libprotobuf34_2_0 | 34.2-1.4 | x86_64
i | @System | libprotobuf36_1_0 | 36.1-1.1 | x86_64
i | @System | libSPIRV-Tools-2026_2_rc2 | 2026.2~rc2-1.1 | x86_64
i+ | @System | libSPIRV-Tools-2026_3_rc1 | 2026.3~rc1-1.2 | x86_64
i+ | @System | libutf8_range-34_2_0 | 34.2-1.4 | x86_64
i | @System | libutf8_range-36_1_0 | 36.1-1.1 | x86_64
i+ | @System | libvtk1 | 9.7.0-1.1 | x86_64
i | @System | libwx_baseu-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_baseu_net-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_baseu_xml-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_aui-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_core-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_gl-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_html-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_media-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_propgrid-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_qa-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_ribbon-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_richtext-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_stc-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_webview-suse14_0_0 | 3.2.6-4.2 | x86_64
i | @System | libwx_gtk3u_xrc-suse14_0_0 | 3.2.6-4.2 | x86_64
i+ | @System | libx264-164 | 0.164+git20231001.31e19f92-1699.1.pm.26 | x86_64
i | @System | libx265-188 | 3.3-2.56 | x86_64
i | @System | libx265-209 | 3.6-1699.2.pm.12 | x86_64
i+ | @System | libxml2-2 | 2.13.8-3.1 | x86_64
~> sudo zypper up ntfs-3g
[sudo] password for root:
Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following package is going to be upgraded:
ntfs-3g
1 package to upgrade.
Package download size: 129.4 KiB
Package install size change:
| 313.7 KiB required by packages that will be installed
0 B | - 313.7 KiB released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y):
Why did you not perform the second command? There is no conflict.
You can update every package which is in the list of your comment.
sudo zypper up libntfs-3g90
sudo zypper up hwinfo
sudo zypper up ntfsprogs
...
…and so on. See where it gets stuck.
I get the feeling that your rpm database is corrupted.
And no, according the packages in the output of this comment, this system is definitely NOT a fresh Tumbleweed installation.
Done with only 1 conflict solved, zypper dup still with conflict.
I’ll start again “zypper dup” and accept substitution. If system will have problem I’ll install Tumbleweed again formatting root partition.
Show it (zypper dup). We might be able to help you further.
Thanks.
Already done “zypper dup” and I don’t take note. But I remember conflict with something like libopenshot.
If you prefer to keep using pdfsam-basic, it doesn’t need to be installed as a package. It’s just a shell script that launches a java applet.
The official website provides a .deb package for Debian-based distributions and a tar.gz for everyone else. You can extract the .tar.gz to somewhere convenient (I keep a ~/.local/opt/ directory for such occasions), then start it with pdfsam-basic-6.0.6-linux-x64/bin/pdfsam.sh. Add a .desktop file for it in ~/.local/share/applications/ for easy access.
Useful explication. Thanks.
And thanks a lot to all that helped.