Just did an upgrade from my stable Leap 15.1 install to 15.2. I
downloaded the DVD and did the upgrade from booting that. It asked me if
I wanted to used the online repos as I have an internet connection so I
said OK. Everything seemed to go well and booting into my KDE desktop.
But clicking the gecko start menu gives an error.
"Error loading QML
module "org.kde.plasma.private.kicker: is not installed"
The system is running and I see my desktop widgets doing their thing.
But I can't do anything. I can get to tty1 and login as root but I don't
know what to do from there.
I tried running yast in tty1 but get errors when I try software management.
This system was first installed with Leap 15.0, upgraded to 15.1, now to
a partially broken 15.2.
Any suggestions most welcome.
I have been using a Logitech Marble Mouse trackball and a Logitech
optical mouse with Leap 15.2/KDE for quite a while. Trackball
left-hand-mapping, and an optical mouse right-hand-mapping (one
computer, two users)
I left the the optical-mouse-setting as it came with the system, and
added for the trackball the configuration below.
Works the way I like it.
/etc/X11/xorg.conf.d/40-libinput.conf in Leap 15.2/KDE-Plasma
Identifier "Marble Mouse"
MatchProduct "Logitech USB Trackball"
# default button assignments.
# Option "ButtonMapping" "1 2 3 4 5 6 7 8 9"
# Option "ButtonMapping" "1 8 3 4 5 6 7 2 9"
Option "ButtonMapping" "3 8 1 4 5 6 7 2 9"
Option "ScrollMethod" "button"
# Option "ScrollButton" "8"
Option "ScrollButton" "9"
# Option "MiddleEmulation" "on"
# use instead Buttonmapping "3 8 1 ... 9"
But not so with Leap 15.3 RC Gnome or with the current Tumbleweed XFCE.
It seems that /etc/X11/xorg.conf.d/ is not used except for a
keyboard-configuration file in Tumbleweed XFCE. It is still there in
Leap 15.3 RC KDE-Plasma.
How could I get the trackball functionality in Tumbleweed XFCE?
If I download a package from Packman and install it directly, I get
libvo-amrwbenc0-0.1.3-pm151.1.4.x86_64 (Plain RPM files cache):
Signature verification failed [4-Signatures public key is not
Of course if I add the repository this is all managed. But if I want
to just install the RPM direct, is there a package with the
certificates that I can install so this message is not given?
We are looking for a fingerprint-protected usb-stick.
I noticed: two luxwallet devices, and on their site they clain (...)
that those are linux-compatible.
However, one must first initialize them, with windows-only software.
I've got lot of rubbish and junk here, but no W10.
I tried wine, but all i got was: "No U: drive", nothing else :-(
Anyone around here who got them working?
(or other recommendable devices? read/write is OK, bootable would be
Kind Regards, Hans.
For a while now I have this weird issue where, when logging into KDE after
system boot, KDE is in a weirdly broken state: compositing is disabled (no
wobbly windows, only half my windows are restored (curiously, Firefox always
is, Konsole is always missing), and the desktop itself is not being drawn,
resulting in remnants of moved windows staying on it.
This happens when using the official NVIDIA driver from the openSUSE-NVIDIA
repository on a GTX 1060. I have been using this same set-up for years but the
issue only popped up a couple months ago without me knowingly changing
anything. It also survived the move from Leap 15.2 to Leap 15.3 Beta / RC.
Only my main user seems to be affected by this. Two test users I use
irregularly don't seem to show the same behaviour.
When going to the compositing settings in that state, I get a message that
compositing crashed KWin and OpenGL detection has thus been disabled, see the
German-language screenshot attached. Reactivating the detection and either
doing a logout / login or running "kwin_x11 --replace" will result in
compositing working again.
I also have a slight impression that this is more likely to happen when there
is disk activity while initiating the login. But this might also be a red
Does anybody have any hints what log files might help to home in on the issue
causing this? I have a suspicion that I have some non-default configuration,
that I am not aware of, that either directly causes this or exposes some
underlying bug that is otherwise not triggered.
Dr. Matthias Bach
„Der einzige Weg, die Grenzen des Möglichen zu finden, ist ein klein wenig
über diese hinaus in das Unmögliche vorzustoßen.“ - Arthur C. Clarke
On 27/05/2021 13.37, Richard Brown wrote:
> On Thu, 2021-05-27 at 13:31 +0200, Per Jessen wrote:
>> Carlos E. R. wrote:
>>> Again. Pidgin requires the password BEFORE a connection is
>> If nothing else, this is going off-topic here - FWIW, it worked just
>> fine with konversation. No userid, no password, but there was a
>> step to verify my email address.
> Indeed - please can we relocate the "Carlos doesn't know how to connect
> to IRC" portion of this thread to the Support list please?
As long as somebody helps me there...
Connection doesn't work:
Cheers / Saludos,
Carlos E. R.
(from 15.2 x86_64 at Telcontar)
Icarus moment: Mozilla Thunderbird was saving OpenPGP keys in plaintext after
Cockup has since been patched in latest release
Gives me the shivers about ever updating....
David C. Rankin, J.D.,P.E.
Hello, I am running a number of OpenSuSE systems on my SOHO network
home and I keep hitting a small but annoying problem that I wonder if
there is a better workaround/solution to. This occurs on all versions of
OpenSuSE - 15.0, 15.1, and 15.2. I am not running 15.3 yet. All systems
are x64 architecture.
I want to access the complete file systems of each computer via samba
and autofs, which means I want to be able to access the "root" directory
/ on each system. Some years ago Samba stopped me from designating / as
a samba shared directory and exporting it. (I don't understand why
except from Googling it appears someone decided that to allow /, to be
exported as a Samba share, was a security problem. I get so annoyed at
all the layers of security and obfuscation so have not tried to track
down what is exactly going on with Samba and the "root" / directory.
Please don't try to dissuade me and tell me about the security risks of
making the "root" / directory available for mounting, this is a SOHO
network and I solely control all the computers on it.) I know Samba will
allow me to define a share for the "root" / directory but it doesn't
seem to work, at least autofs will not recognize/mount it and still
reports the directory does not exist if I try to cd into it. So to work
around this I do a bind mount of / as /slash and samba then allows me to
export /slash as a samba share.
In my various configuration files I use the name "slash" as the name of
the exported Samba share and I create a directory /slash so that my
configuration files will work regardless of whether /slash is a bind
mount or not. At least that is what I think I am doing.
The config line in fstab looks like this -
/ /slash none bind
smb.conf has the following definitions for the root directory -
available = Yes
browseable = Yes
comment = Root directory
inherit acls = Yes
path = /
read only = No
create mask = 0755
force user = root
autofs configuration for mounting the root directory / typically looks
like the following, only names of the remote host changes.
This works fine for autofs and most tools that work on the host or
across network file systems. All except, that is, the YaST2 partitioner.
For some unknown reason it picks up the bind mount /slash and
automagically reassigns all my mount points to be under /slash. So for
example if I tell it to mount my home partition at /home the partitioner
will reassign my mount point to be at /slash/home. More importantly, the
partitioner reassigns / to be mounted as /slash. Then if I want to make
any further change to partitions and save those changes, the partitioner
will complain that the mount point for / is undefined and it wants to
force me to define a / mount. The only workaround I have found is to
remove the bind mount from fstab and then reboot. After reboot I can
then use the YaST partitioner to make the changes I want, since because
without the bind mount the partitioner now sees all the mount points of
different partitions as subdirectories under / and not under /slash/.
But without the bind mount defined in fstab, tools like autofs will no
longer mount the "root" / directory though I do not grok why. So again I
have to add back in the bind mount to fstab so that Samba shares will
again work, and again I have to reboot. I have tried restarting all
appropriate services individually, such as nmb, smb, autofs, and network
but no joy getting the the remote host's "root" / dir to remount, so I
resort to rebooting the systems (a PITA) and that does the trick...
Perhaps I am missing some magic trick or there is a better way to
accomplish what I want to do, which ideally is to configure Samba to
really share the "root" / directory. Sorry this is complicated and will
be difficult to grok, it is for me! Any help would be much appreciated,
I would love to once and for all resolve this irritant because I have to
rediscover these issues and their resolutions each time something like
autofs breaks or I want to use the partitioner.