upgrading online some 15.3 to 15.4 just today (beta? rc?) via zypper
and golbal parameter --releasever=15.4 went fine over here with a
rather simple test system.
Too bad 15.4 is very conservative and old in various software versions
and so on. Is a tumbleweed more suited when not wanting to risk
stability and not opting in for data loss?
TW fish filesystem bug in dolphin.
Dolphin tries to open directories such as conf.d as a regular file when
clicked on. Navigating via the address bar works fine. The underlying
sshfs fused filesystem is working fine i.e. F4 open terminal in Dolphin
and changing directory works fine.
How to reproduce:
1. Open fish://server.com/some-dir/
2. Open directory with .d extension by clicking
Expected result; directory opens in dolphin
Observed result; dolphin tries to open the directory as a regular file.
When something I am installing requires a list of perl modules I have
to figure out how to install them. I first have to search the rpm
repositories for the module. If the module is available in rpm
repositories I can use zypper to install it. Other times I have to use
CPAN to install it.
Does anyone know of a script that will install a list of modules by
searching for it and installing from the necessary location?
In openSUSE 15.1, memtest, as installed, would not work with UEFI. Has
this been fixed in 15.2? There is a version on the memtest website that
will work with it.
To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse+owner(a)opensuse.org
I use openSUSE Leap 15.3. Trouble is, when I attach USB sticks from
16-128 GB there are no problems. They are mounted and read immediately
upon being attached.
When I attach large external USB disks, there is a different story. The
disks most often do not show up. Sometimes they do, but most times I
must read the disks (formatted with EXT4, FAT32 and EXFAT) on a Mac
laptop in order to access them. Which, admittedly, makes me ashamed.
The question is why this happens.
To elucidate the problem, I have typed fdisk -l and dmesg, and the
results are in the links below. I shall be extremely thankful if you can
have a look at these outputs and see if you can spot the source of my
problem. If these files do not provide a clue, please tell me what
commands I should try next.
In both cases, an external disk was attached. However, the system failed
to see it.
The fdisk -l output:
The dmesg output:
Per Inge Oestmoen, Norway
is anyone else having issues with the latest zoom (5.10.0-2450) on Tumbleweed?
It keeps crashing on me, directly at start, even the crash report form doesn't
stay on screen, but vanishes before I can type in anything.
Since one of the latest updates of my TW computers(*) mutt (running in XTerm,
but it's the same in konsole) no longer is showing special characters (like
accented ones). Are others seeing that, too? Any hints what to look for? I
didn't change any of my settings...
(*) one is running TW20220421/mutt 2.2.3, the other one TW20220419/mutt 2.1.5
With LANG=en_GB.UTF-8 I get, e.g., "ZurÃ¼ck", LANG=en_DE.UTF-8 displays it
as two questionmarks, "Zur??ck"
I remember making the switch from 15.2 to 15.3, it was very messy in
the early days in the rc stages or something, or at least me, I was
not aware that there were those brand new backports and sle-update
repos coming in additionally to those standard repos ever since until
so here is the question, are we getting another set of new additional
or completely differing repo addresses on 15.4?
anything to be aware of? where can one find such elementary changes
and stuff if such stuff happens except for going for a clean install
on clean new hardware and first observing and looking through all
sorts of things there, and then manually "backporting" such stuff as
addl repo urls to other existing but aged opensuse installs?
-----BEGIN PGP SIGNED MESSAGE-----
#### YaST2 conflicts list - generated 2022-04-22 22:07:07 ####
the to be installed patch:openSUSE-SLE-15.3-2022-1273-1.noarch conflicts with 'libSDL-devel.x86_64 < 1.2.15-150000.3.19.1' provided by the installed libSDL-devel-1.2.15-lp153.93.2.x86_64
[ ] Following actions will be done:
install libSDL-devel-1.2.15-150000.3.19.1.x86_64 from vendor SUSE LLC <https://www.suse.com/>
replacing libSDL-devel-1.2.15-lp153.93.2.x86_64 from vendor obs://build.opensuse.org/games
install libSDL-1_2-0-1.2.15-150000.3.19.1.x86_64 from vendor SUSE LLC <https://www.suse.com/>
replacing libSDL-1_2-0-1.2.15-lp153.97.1.x86_64 from vendor obs://build.opensuse.org/games
[ ] do not install patch:openSUSE-SLE-15.3-2022-1273-1.noarch
#### YaST2 conflicts list END ###
What is this, in plain language?
Carlos E. R.
(from 15.3 x86_64 at Telcontar)
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----
Hi - If I mount a filesystem, from a different computer system on my
local network, on my laptop using autofs (automount actually), where
samba exported cifs shares from the other remote system, I run into a
snag. How do I get ls -al or the abbreviated for - ll to show me both a
link name and the file/dir being pointed at, in the same way of using ls
-al or ll on a local file system shows me symlinks?
For example if I use ll (or ls -al) to show me the contents of directory
on my laptop -
drw-rw-r-- 2 root bacula 4096 Aug 16 2020 etc_bacula5.2
drw-rw-r-- 2 root bacula 4096 Aug 16 2020 etc_bacula7.4
drw-rw-r-- 2 root bacula 4096 Jun 23 2021 etc_bacula9.0.3
drw-rw-r-- 2 root bacula 4096 Apr 4 16:41 etc_bacula9.6.6
lrwxrwxrwx 1 root bacula 15 Apr 3 18:21 etc_SYMLINK-> etc_bacula9.6.6
drw-rw-r-- 2 root bacula 4096 Apr 4 16:43 etc_systemd_system
lrwxrwxrwx 1 root bacula 56 Aug 16 2020 README->
lrwxrwxrwx 1 root bacula 41 Apr 3 20:11
drw-rw-r-- 2 root bacula 4096 Apr 4 16:44 usr_lib_tmpfiles.d
drw-rw-r-- 2 root bacula 4096 Apr 3 20:26 usr_sbin
lrwxrwxrwx 1 root bacula 17 Oct 4 2020 var_spool_bacula_SYMLINK->
drw-rw-r-- 2 root bacula 4096 Aug 16 2020 working_bacula5.0
Note that all the entries in this directory, that are symlinks, the ll
or ls -al commands show both the name of the symlink and the path that
the symlink follows to the target of the symlink.
I use autofs to mount various samba (cifs) file systems under
/mnt/samba/SuSE/<system name>/<remote file system>
My autofs automounter maps, on my laptop, look something like this for
mounting shares from a remote system named bigbang -
But if I show this same directory, by following an automount to another
system (named bigbang here) and then follow an automount path back to my
laptop to show the above /srv/bacula directory, I get the following
display that does not show the symlinked paths -
drwxrwxrwx 2 root root 0 Aug 16 2020 etc_bacula5.2
drwxrwxrwx 2 root root 0 Aug 16 2020 etc_bacula7.4
drwxrwxrwx 2 root root 0 Jun 23 2021 etc_bacula9.0.3
drwxrwxrwx 2 root root 0 Apr 4 16:41 etc_bacula9.6.6
drwxrwxrwx 2 root root 0 Apr 4 16:41 etc_SYMLINK
drwxrwxrwx 2 root root 0 Apr 4 16:43 etc_systemd_system
-rwxrwxrwx 1 root root 13616 Mar 1 20:52 README
-rwxrwxrwx 1 root root 1411 Apr 3 21:33
drwxrwxrwx 2 root root 0 Apr 4 16:44 usr_lib_tmpfiles.d
drwxrwxrwx 2 root root 0 Apr 3 20:26 usr_sbin
drwxrwxrwx 2 root root 0 Apr 5 02:20 var_spool_bacula_SYMLINK
drwxrwxrwx 2 root root 0 Aug 16 2020 working_bacula5.0
I used this example to somewhat dramatically illustrate the problem, but
following a single automount point and displaying a remote directory
also does not show symlink paths.
Where I am really having problems is when I use Beyond Compare to
compare files and directories on both a local filesystem and a remote
filesystem accessed via an automount point. It is critical to know when
I am working with a symlink on a remote filesystem, otherwise Beyond
Compare is blind to them and can easily clobber and ruin a remote system
by overwriting a symlink. AFAIK Beyond Compare is being blinded by the
automount system dropping the symlink information.
Hope I have been clear and hopefully some nice guru with have a magic
incantation I can use to solve this issue. Google has not been my friend
on this issue! Thanks as always in advance for helping me...
*"The Truth is out there" - Spooky*
*_ _ . . . . . . _ _ . _ _ _ _ .
. . . _ . . . . _ _ . _
_ _ . . . . _ _ . _ . . _ . _
_ _ _ . _ . _ . _ . _ . *
Computers: the final frontier.
These are the voyages of the user Marc.
His mission: to explore strange new hardware.
To seek out new software and new applications.
To boldly go where no Marc has gone before!
(/This email is digitally signed and the OpenPGP electronic signature is
added as an attachment. If you know how, you can use my public key to
prove this email indeed came from me and has not been modified in
transit. My public key, which can be used for sending encrypted email to
me also, can be found at -
https://firstname.lastname@example.org or just ask me
for it and I will send it to you as an attachment. If you don't
understand all this geek speak, no worries, just ignore this explanation
and ignore the OpenPGP signature key attached to this email (it will
look like gibberish if you open it) and/or ask me to explain it further
if you like./)