openSUSE Users May 2021

users@lists.opensuse.org

70 participants
61 discussions

On one computer, xfce4-panel is using 1.4 GB.

by Carlos E. R.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 View of top, sorting by memory: top - 13:27:09 up 12 days, 9:30, 5 users, load average: 5.12, 3.70, 2.15 Tasks: 408 total, 4 running, 404 sleeping, 0 stopped, 0 zombie %Cpu(s): 14.3 us, 7.3 sy, 0.0 ni, 24.6 id, 53.5 wa, 0.0 hi, 0.3 si, 0.0 st KiB Mem : 7995344 total, 857392 free, 5739144 used, 1398808 buff/cache KiB Swap: 9446396 total, 9354748 free, 91648 used. 1616044 avail Mem PID USER PR NI VIRT RES SHR SWAP S %CPU TIME+ COMMAND 3971 cer 20 0 1702692 1.122g 12312 0 S 0.000 1:13.24 xfce4-panel <===== 5154 cer 20 0 3924304 1.033g 33148 0 S 0.000 69:28.87 WebExtensions 4021 cer 20 0 4299592 922428 129636 0 S 8.125 552:36.75 firefox 5103 cer 20 0 3893680 398436 102932 0 R 25.62 2938:04 Web Content 19778 cer 20 0 2644216 355808 57124 0 S 3.125 1470:05 kodi-x11 18478 cer 20 0 3141844 335740 101772 0 S 0.625 42:10.54 Web Content 19741 cer 20 0 3250292 228088 39508 0 S 0.625 163:18.54 Web Content I'm very surprised by the high memmory usage of xfce4-panel. 1.2 Gigs? Process tree (ps -fx): PID TTY STAT TIME COMMAND ... 2429 ? Sl 0:00 /usr/bin/sddm 2432 tty7 Ssl+ 304:20 \_ /usr/bin/X -nolisten tcp -auth /run/sddm/{cb0ab23f-eda4-4c5d-bf88-a9504ffda949} -background none -noreset -displayfd 17 -seat seat0 vt7 3819 ? S 0:00 \_ /usr/lib/sddm/sddm-helper --socket /tmp/sddm-auth567d414c-8028-40ca-97ed-a8779b3d8335 --id 1 --start startxfce4 --user cer 3835 ? Sl 0:04 \_ xfce4-session 3888 ? Ss 0:04 \_ /usr/bin/ssh-agent /usr/bin/gpg-agent --sh --daemon --keep-display /etc/X11/xinit/xinitrc 3889 ? Ss 0:34 \_ /usr/bin/gpg-agent --sh --daemon --keep-display /etc/X11/xinit/xinitrc 3945 ? Sl 88:42 \_ xfwm4 --display :0.0 --sm-client-id 27ef593e4-abdd-45de-87e1-06f1cda34cda 3971 ? Sl 1:13 \_ xfce4-panel --display :0.0 --sm-client-id 2c36722ba-067e-4ae0-8417-a8245488ea39 <====== 3986 ? Sl 2:39 | \_ /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libwhiskermenu.so 1 16777223 whiskermenu Whisker Menu Show a menu to easily access installed applications 3991 ? Sl 18:15 | \_ /usr/lib/xfce4/panel/wrapper-1.0 /usr/lib64/xfce4/panel/plugins/libmultiload.so 15 16777224 multiload Multiload A system load monitor that graphs processor, memory, and swap space use, plus network and disk activity. 3992 ? Sl 20:09 | \_ /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libpulseaudio-plugin.so 6 16777225 pulseaudio PulseAudio Plugin Adjust the audio volume of the PulseAudio sound system 3993 ? Sl 0:28 | \_ /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libxfce4powermanager.so 13 16777226 power-manager-plugin Power Manager Plugin Display the battery levels of your devices and control the brightness of your display 3995 ? Sl 0:02 | \_ /usr/lib/xfce4/panel/wrapper-2.0 /usr/lib64/xfce4/panel/plugins/libsystray.so 7 16777227 systray Notification Area Area where notification icons appear 3982 ? Sl 0:00 \_ Thunar --sm-client-id 2dfa4a24a-8d69-4a3d-a93d-5f51febf0e5e --daemon cer@Isengard:~> uptime 13:32:22 up 12 days 9:36, 5 users, load average: 4.56, 4.13, 2.81 How can it be? - -- Cheers Carlos E. R. (from 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYEoO1xwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVhFwAn0XgAg1KtZqP1FSQdgAK OQ5hNRhGAKCSL32uSBCbbYc4QxjjPAdXo4HtzQ== =8ukM -----END PGP SIGNATURE-----

1 month

Upgrade from Leap 15.1 to 15.2 Desktop Failure

by Jim Flanagan

Greetings, 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 file:file///sur/share/plasma/plasmoids/org.kde.plasma.kicker/contents/ui/main.qml:27:1: 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. Jim F

1 month

Leap 15.3 RC Gnome and Tumbleweed XFCE: Logitech Marble Mouse not working (40-libinput.conf missing)

by Peter McD

Hi, 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 ---------------------------------------------------------------- Section "InputClass" Identifier "Marble Mouse" MatchProduct "Logitech USB Trackball" MatchDevicePath "/dev/input/event*" Driver "libinput" # default button assignments. # Option "ButtonMapping" "1 2 3 4 5 6 7 8 9" # right-hand-mapping # Option "ButtonMapping" "1 8 3 4 5 6 7 2 9" # left-hand-mapping 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" EndSection ---------------------------------------------------------------- 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? Peter

1 month

Packman and certificates

by Roger Oberholtzer

If I download a package from Packman and install it directly, I get this warning: libvo-amrwbenc0-0.1.3-pm151.1.4.x86_64 (Plain RPM files cache): Signature verification failed [4-Signatures public key is not available] 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? -- Roger Oberholtzer

1 month, 4 weeks

supported fingerprint sticks

by suse＠a-domani.nl

Hi all, 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. URL: https://www.luxwallet.nl/product-categorie/usb-opslag/vingerafdruk-usb/ 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 perfect.) Kind Regards, Hans.

2 months

Compositing crashing KWin on Login

by Matthias Bach

Hi all, 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 herring. 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. Kind Regards, Matthias -- Dr. Matthias Bach www.marix.org „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

2 months

Re: Moving from Freenode to Libera.Chat

by Carlos E. R.

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 >>> established. >> >> If nothing else, this is going off-topic here - FWIW, it worked just >> fine with konversation. No userid, no password, but there was a >> third >> 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: https://susepaste.org/81396729 -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)

2 months

We knew there was something funny about the new Tbirds and gpg ...

by David C. Rankin

Icarus moment: Mozilla Thunderbird was saving OpenPGP keys in plaintext after encryption snafu Cockup has since been patched in latest release 6 Comments https://go.reg.cx/tdml/dfd67/60d51c7f/70bba22e/3ZNf Gives me the shivers about ever updating.... -- David C. Rankin, J.D.,P.E.

2 months

IRC moving from freenode to libera

by Per Jessen

... continued from factory. Carlos, you have the wrong server specified. It is 'irc.libera.chat', not 'libera.chat'. -- Per Jessen, Zürich (14.6°C) Member, openSUSE Heroes.

2 months

bind mount and yast partitioner

by Marc Chamberlin

Hello, I am running a number of OpenSuSE systems on my SOHO network at 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 - [slash] 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. slash -fstype=cifs,rw,dir_mode=0777,file_mode=0777,credentials=/etc/smb1.auth ://bigbang/slash 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 the 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. Thanks, Marc

2 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

1997

1996

1995

1994

1993

1992

openSUSE Users May 2021