March 2019 - openSUSE Support - openSUSE Mailing Lists

[opensuse-support] user disappeared
by Adam Mizerski 16 Apr '19

16 Apr '19

Hi, I've got an odd problem, that probably deserves a bug report, but I don't know where to start looking for evidence. I'm running openSUSE 15.0 "transactional server" on a vps. I had freenet daemon installed, running as a dedicated "freenet" user. What happened is that the "freenet" user suddenly disappeared. It's not mentioned in /etc/passwd, /etc/shadow nor /etc/group. If I do "ls -l" in /home/freenet, there are numbers instead of owner and group. Service obviously fails to start. I had a look at logs, but there's nothing alarming. Do you have any clues, what could go wrong? Recent logs for freenet service: http://susepaste.org/view/a0905f56 Systemd service file: # /etc/systemd/system/freenet.service [Unit] Description=FreeNet Service After=local-fs.target network.target time-sync.target [Service] User=freenet Type=forking WorkingDirectory=/home/freenet/Freenet/ ExecStart=/home/freenet/Freenet/run.sh start ExecStop=/home/freenet/Freenet/run.sh stop PIDFile=/home/freenet/Freenet/Freenet.pid [Install] WantedBy=multi-user.target -- Adam Mizerski

5 10

[opensuse-support] Unresponsive desktop
by Carlos E. R. 08 Apr '19

08 Apr '19

Hi, Last December I reported this problem on my laptop, and now my desktop also exhibits it. After several days running, this morning it locked as soon as I changed workspaces. I noticed kswapd0 was busy long time, and that firefox had about 10 gigs of virtual memory. The disk activity led was solid blue. I couldn't find out more, the machine froze and had to be hard rebooted. A week before it also froze, but that time I could not observe anything. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

9 45

[opensuse-support] After upgrade to 15.0, restore from hibernation crashes the machine.
by Carlos E. R. 05 Apr '19

05 Apr '19

Black display, keyboard light responds initially, then not. ssh from another machine says there is no route to machine (works instantly after reboot). Means that network is dead on desktop. Log: <10.6> 2019-01-10 20:20:01 Telcontar cron 27759 - - pam_unix(crond:session): session opened for user cer by (uid=0) <10.6> 2019-01-10 20:20:02 Telcontar CRON 27759 - - pam_unix(crond:session): session closed for user cer <3.6> 2019-01-10 20:23:50 Telcontar systemd 1 - - Reached target Sleep. <3.6> 2019-01-10 20:23:50 Telcontar systemd 1 - - Starting Hibernate... <0.7> 2019-01-10 20:23:50 Telcontar kernel - - - [117583.419978] PM: Hibernation mode set to 'platform' <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - INFO: running /usr/lib/systemd/system-sleep/grub2.sleep for hibernate <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - INFO: Running prepare-grub .. <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - 2019-01-10 20:23:50+01:00 - Hibernating the system now... <3.4> 2019-01-10 20:23:50 Telcontar systemd-sh - - - Hibernating the system now... <3.6> 2019-01-10 20:23:50 Telcontar systemd-sleep 27981 - - service: no such service upsd.service <3.6> 2019-01-10 20:23:51 Telcontar systemd-sleep 27981 - - running kernel is grub menu entry openSUSE Leap 15.0 (vmlinuz-4.12.14-lp150.12.28-default) <3.6> 2019-01-10 20:23:51 Telcontar systemd-sleep 27981 - - preparing boot-loader: selecting entry openSUSE Leap 15.0, kernel /boot/4.12.14-lp150.12.28-default <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - running /usr/sbin/grub2-once "openSUSE Leap 15.0" <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - time needed for sync: 5.2 seconds, time needed for grub: 0.2 seconds. <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - INFO: Done. <3.6> 2019-01-10 20:23:56 Telcontar systemd-sleep 27981 - - Suspending system... <0.6> 2019-01-10 20:23:57 Telcontar kernel - - - [117590.115929] PM: Syncing filesystems ... 2019-01-11 11:07:16+01:00 - Booting the system now ================================================================================ Linux Telcontar 4.12.14-lp150.12.28-default #1 SMP Mon Dec 3 16:46:15 UTC 2018 (b91289f) x86_64 x86_64 x86_64 GNU/Linux <3.6> 2019-01-11 11:07:18 Telcontar systemd 1 - - systemd 234 running in system mode. (+PAM -AUDIT +SELINUX -IMA +APPARMOR -SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT -GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID -ELFUTILS +KMOD -IDN2 -IDN default-hierarchy=hybrid) Hibernation has worked in this machine reliably for about a decade - till 15.0 :-( -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

4 14

[opensuse-support] Docking station - extending ports of HP notebooks
by Vojtěch Zeisek 04 Apr '19

04 Apr '19

Hi, I need to extend ports available on HP ProBook 650 G2 and HP X2 210 G2 (both running TW) by something like HP USB-C Travel HUB, HP USB-C Mini Dock #AC3,HP Spectre USB-C, HP USB-C mini dock or HP USB-C Universal Dock + 4.5mm and USB Dock Adapter. They are connected to the notebook via USB-C and extend ports available in the notebook. Do You have experiences with that? Is it well supported? Does it reliably work with anything You connect via the dock? I need charging of the notebook (the X2), more USB, Ethernet. I suppose ports in notebook (HDMI, USB, ...) are still working as expected. Do You use something like that? Thanks in advance, V. -- Vojtěch Zeisek Komunita openSUSE GNU/Linuxu Community of the openSUSE GNU/Linux https://www.opensuse.org/ https://trapa.cz/

2 3

[opensuse-support] 15.0 most boots halt in emergency mode
by Felix Miata 01 Apr '19

01 Apr '19

# inxi -b System: Host: i2134 Kernel: 4.12.14-lp150.12.48-default x86_64 bits: 64 Desktop: Trinity R14.0.6 Distro: openSUSE Leap 15.0 Machine: Type: Desktop System: Apple product: iMac7,1 v: 1.0 serial: QP7440XDX89 Mobo: Apple model: Mac-F42386C8 v: PVT serial: 1 UEFI: Apple v: IM71.88Z.007A.B03.0803051705 date: 03/05/08 CPU: Dual Core: Intel Core2 Duo T7700 type: MCP speed: 1794 MHz min/max: 800/2400 MHz Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV630/M76 [Mobility Radeon HD 2600 XT/2700] driver: radeon v: kernel Display: server: X.Org 1.19.6 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1200~60Hz OpenGL: renderer: AMD RV630 (DRM 2.50.0 / 4.12.14-lp150.12.48-default LLVM 5.0.1) v: 3.3 Mesa 18.0.2 Network: Device-1: Broadcom Limited BCM4321 802.11a/b/g/n driver: b43-pci-bridge Device-2: Marvell 88E8058 PCI-E Gigabit Ethernet driver: sky2 Drives: Local Storage: total: 931.51 GiB used: 26.31 GiB (2.8%) Info: Processes: 156 Uptime: N/A Memory: 3.84 GiB used: 486.4 MiB (12.4%) Shell: bash inxi: 3.0.32 # journal -b | grep ailed: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-failed-201903292030.txt full journal: http://fm.no-ip.com/Tmp/SUSE/Leap/imac150-jrnl-201903292030.txt # cat /etc/fstab: LABEL=EFI /boot/efi vfat codepage=437 0 0 LABEL=st10swapper swap swap defaults 0 0 LABEL=st10suseleap / ext4 noatime 1 1 LABEL=st10linuxnext /disks/s151 ext4 noatime 1 2 LABEL=st10susehome /home ext4 noatime 1 2 /dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part2 /macsys hfsplus ro,nofail 0 0 /dev/disk/by-id/ata-ST1000DM003-1SB10C_Z9A1LQPM-part4 /home/macdata hfsplus force,uid=501,gid=100,umask=002,noatime,nofail 0 0 I don't see any clues to why this happens on most boots. Immediate Ctrl-D always triggers successful init completion. Can anyone see what I am missing to cause this? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

5 19

[opensuse-support] How can I get nvidia.ko installed in 15.0?
by Carlos E. R. 01 Apr '19

01 Apr '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 startx complains it could not modprobe nvidia.ko. The module does not exist. Telcontar:~ # rpm -ql nvidia-gfxG03-kmp-default | less /etc/modprobe.d/nvidia-default.conf /lib/modules/4.12.14-lp150.11-default /lib/modules/4.12.14-lp150.11-default/updates /lib/modules/4.12.14-lp150.11-default/updates/nvidia.ko <-- /usr/lib/nvidia ... But it is not there. Why? Telcontar:~ # l /lib/modules/4.12.14-lp150.11-default/updates total 8 drwxr-xr-x 2 root root 4096 Oct 12 15:55 ./ drwxr-xr-x 3 root root 4096 Mar 29 12:42 ../ Telcontar:~ # I look into the rpm with mc, and the file is not there. How can I then create it? How can I find why it was not created? There is nothing in the log. [...] I install the rpm manually. I get this: Telcontar:/data/storage_c/repositorios_zypp/15_0/download.nvidia.com-leap/x86_64 # rpm --install --force nvidia-gfxG03-kmp-default-340.107_k4.12.14_lp150.11-lp150.12.1.x86_64.rpm make: *** /usr/src/linux-obj/x86_64/default: No such file or directory. Stop. make: *** /usr/src/linux-obj/x86_64/default: No such file or directory. Stop. /usr/src/kernel-modules/nvidia-340.107-default / NVIDIA: calling KBUILD... make[1]: *** /lib/modules//source: No such file or directory. Stop. NVIDIA: left KBUILD. nvidia.ko failed to build! make: *** [Makefile:192: nvidia.ko] Error 1 / install: cannot stat '/usr/src/kernel-modules/nvidia-340.107-default/nvidia.ko': No such file or directory depmod: WARNING: could not open modules.order at /lib/modules/4.12.14-lp150.11-default: No such file or directory depmod: WARNING: could not open modules.builtin at /lib/modules/4.12.14-lp150.11-default: No such file or directory Modprobe blacklist files have been created at /etc/modprobe.d to prevent Nouveau from loading. This can be reverted by deleting /etc/modprobe.d/nvidia-*.conf. .... then it goes on with dracut. As you can see, the make procedure failed, yet YaST said nothing and continues with dracut, making one think that everything was alright. The local problem is here: Telcontar:/data/storage_c/repositorios_zypp/15_0 # Telcontar:/usr/src/linux-obj/x86_64 # l default lrwxrwxrwx 1 root root 47 Mar 28 19:39 default -> ../../linux-4.12.14-lp151.22-obj/x86_64/default Telcontar:/usr/src/linux-obj/x86_64 # Installation of the 15.0 kernel after removing 15.1 kernel did not make the correct link. - -- Cheers Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXJ5PxRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVIWAAniZ5TAdnHmB2wtHPA1Fi HK5WI1jkAJsEpVixYpqELfpEW8T51x5cepyEnQ== =3IXb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 2

[opensuse-support] X server dies after resuming from hibernation
by mh＠mike.franken.de 31 Mar '19

31 Mar '19

Hi *, sometimes, but not always my X server dies after the system has successfully resumed from hibernation. It is restarted then, so I can login, but of course my previous session is lost. Xorg.log.old contains: ------------------------< snip snip snip >----------------------------- ... [ 65043.707] (II) AIGLX: Suspending AIGLX clients for VT switch [ 65050.192] (II) AIGLX: Resuming AIGLX clients after VT switch [ 65050.212] (EE) modeset(0): failed to set mode: Invalid argument [ 65050.212] (EE) Fatal server error: [ 65050.212] (EE) EnterVT failed for screen 0 [ 65050.212] (EE) [ 65050.212] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 65050.212] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 65050.212] (EE) [ 65050.216] (II) AIGLX: Suspending AIGLX clients for VT switch [ 65050.266] (EE) Server terminated with error (1). Closing log file. ------------------------< snip snip snip >----------------------------- journal says: ------------------------< snip snip snip >----------------------------- org.a11y.Bus[2632]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" org.a11y.Bus[2632]: after 23769 requests (23769 known processed) with 0 events remaining. ------------------------< snip snip snip >----------------------------- - openSUSE Tumbleweed with latest snapshot - Linux thunder 5.0.3-1-default #1 SMP Fri Mar 22 17:30:35 UTC 2019 (2a31831) x86_64 x86_64 x86_64 GNU/Linux - notebook Dell Inc. XPS 13 9370/0F6P3V, BIOS 1.8.1 02/14/2019 - Thunderbolt docking station CalDigit TS3 Plus - my monitor is connected to the display port connector of this docking station Any idea, what might be causing this? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] 42.3 Newmoon 28.3.1 from network repo useless
by Felix Miata 30 Mar '19

30 Mar '19

Does it work for anyone? I installed the rpm with zypper, but clicking anywhere in the UI causes a segfault: ###!!! ABORT: X_CreatePixmap: BadAlloc (insufficient resources for operation); 4 requests ago: file /home/abuild/rpmbuild/BUILD/UXP-PM28.3.1_Release/toolkit/xre/nsX11ErrorHandler.cpp, line 135 Segmentation fault (core dumped) Do all or any of the instructions on http://linux.palemoon.org/help/installation/ apply when installing the rpm? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] Trying to use the 15.1 kernel on 15.0
by Carlos E. R. 28 Mar '19

28 Mar '19

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: <alpine.LSU.2.21.1903282012470.4036(a)Telcontar.valinor> Hi, As mentioned previously, I have a problem with hibernation, and I need to try if a more advanced kernel solves the problem. So I have installed the 15.1 kernel on 15.0 (instead of trying the TW kernel), and the 15.1 NVidia driver. So this is what I installed: x11-video-nvidiaG03-340.107-lp151.12.2.x86_64 2019-03-28T19:42:17 CET nvidia-computeG03-340.107-lp151.12.2.x86_64 2019-03-28T19:42:13 CET nvidia-glG03-340.107-lp151.12.2.x86_64 2019-03-28T19:42:09 CET nvidia-uvm-gfxG03-kmp-default-340.107_k4.12.14_lp151.22-lp151.12.25.x86_64 2019-03-28T19:41:00 CET nvidia-gfxG03-kmp-default-340.107_k4.12.14_lp151.22-lp151.12.26.x86_64 2019-03-28T19:39:49 CET kernel-syms-4.12.14-lp151.22.9.x86_64 2019-03-28T19:39:47 CET kernel-default-devel-4.12.14-lp151.22.9.x86_64 2019-03-28T19:39:46 CET kernel-default-4.12.14-lp151.22.9.x86_64 2019-03-28T19:39:12 CET cer@Telcontar:~> uname -a Linux Telcontar 4.12.14-lp151.22-default #1 SMP Thu Feb 28 15:45:32 UTC 2019 (25279f0) x86_64 x86_64 x86_64 GNU/Linux cer@Telcontar:~> Graphic crashes - as I half feared: cer@Telcontar:~> startx xauth: file /home/cer/.serverauth.3927 does not exist X.Org X Server 1.19.6 Release Date: 2017-12-20 X Protocol Version 11, Revision 0 Build Operating System: openSUSE SUSE LINUX Current Operating System: Linux Telcontar 4.12.14-lp151.22-default #1 SMP Thu Feb 28 15:45:32 UTC 2019 (25279f0) x86_64 Kernel command line: BOOT_IMAGE=/vmlinuz-4.12.14-lp151.22-default root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 resume=/dev/disk/by-label/ssd-swap splash=verbose Build Date: 14 March 2019 12:00:00PM Current version of pixman: 0.34.0 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/home/cer/.local/share/xorg/Xorg.0.log", Time: Thu Mar 28 19:57:18 2019 (==) Using config file: "/etc/X11/xorg.conf" (==) Using config directory: "/etc/X11/xorg.conf.d" (==) Using system config directory "/usr/share/X11/xorg.conf.d" xf86EnableIOPorts: failed to set IOPL for I/O (Operation not permitted) (EE) Fatal server error: (EE) no screens found(EE) (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. (EE) Please also check the log file at "/home/cer/.local/share/xorg/Xorg.0.log" for additional information. (EE) GA Arbitration: Cannot restore default device.(EE) Server terminated with error (1). Closing log file. V ^Cxinit: giving up xinit: unable to connect to X server: Connection refused xinit: unexpected signal 2 - ------------------------------------------------------------------------------------------- xinit failed. /usr/bin/Xorg is not setuid, maybe that's the reason? If so either use a display manager (strongly recommended) or adjust /etc/permissions.local and run "chkstat --system --set" afterwards cer@Telcontar:~> (I had to press ctrl-c to stop to get back the prompt) The "/home/cer/.local/share/xorg/Xorg.0.log" is attached. I don't see why it crashes, except that it says "Failed to initialize the NVIDIA kernel module.", but not why. It says to see syslog. The relevant portion is this: <10.6> 2019-03-28 19:56:54 Telcontar login - - - LOGIN ON tty2 BY cer <3.6> 2019-03-28 19:56:55 Telcontar systemd 1 - - Started Clamav antivirus Deamon. <3.6> 2019-03-28 19:56:55 Telcontar systemd 1 - - Starting Amavisd-new Virus Scanner interface... <3.6> 2019-03-28 19:56:56 Telcontar systemd 1 - - Started Amavisd-new Virus Scanner interface. <3.6> 2019-03-28 19:56:56 Telcontar systemd 1 - - Starting Postfix Mail Transport Agent... <3.6> 2019-03-28 19:56:56 Telcontar echo 3820 - - Starting mail service (Postfix) <3.6> 2019-03-28 19:56:58 Telcontar systemd 1 - - Started Postfix Mail Transport Agent. <3.6> 2019-03-28 19:56:58 Telcontar systemd 1 - - Started Command Scheduler. <3.6> 2019-03-28 19:56:58 Telcontar systemd 1 - - Reached target Multi-User System. <3.6> 2019-03-28 19:56:58 Telcontar systemd 1 - - Starting Plays a welcome sound when target multi-user is reached... <9.6> 2019-03-28 19:56:58 Telcontar cron 3917 - - (CRON) INFO (RANDOM_DELAY will be scaled with factor 31% if used.) <3.6> 2019-03-28 19:56:58 Telcontar systemd 1 - - Starting Update UTMP about System Runlevel Changes... <9.6> 2019-03-28 19:56:58 Telcontar cron 3917 - - (CRON) INFO (running with inotify support) <3.6> 2019-03-28 19:56:58 Telcontar systemd 1 - - Started Update UTMP about System Runlevel Changes. <3.6> 2019-03-28 19:56:58 Telcontar Mine - - - Saying hello world. <3.6> 2019-03-28 19:56:58 Telcontar systemd 1 - - Started Plays a welcome sound when target multi-user is reached. <3.6> 2019-03-28 19:57:45 Telcontar systemd 1 - - Starting Console Mouse manager... <1.6> 2019-03-28 19:57:45 Telcontar 3982 - - *** info [daemon/startup.c(136)]: <1.6> 2019-03-28 19:57:45 Telcontar 3982 - - Started gpm successfully. Entered daemon mode. <3.6> 2019-03-28 19:57:45 Telcontar systemd 1 - - Started Console Mouse manager. <4.6> 2019-03-28 19:58:14 Telcontar systemd-logind 1537 - - New session 3 of user cer. I started gpm in order to paste the error log in text mode, so I know the instant startx failed. - -- Cheers Carlos E. R. (from 15.0 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXJ0eTxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVYwEAn0V1QbWK2sEl6AOWq5fi ES2DYnRAAJwJIeDJQ5i2JjHvQhdqPPt0gaLIQA== =Wm5R -----END PGP SIGNATURE-----

1 0

[opensuse-support] Tumbleweed kernel 5.x: kdump can't be loaded
by mh＠mike.franken.de 27 Mar '19

27 Mar '19

Hi *, starting with kernel 5.x on my Tumbleweed machines kdump can't be loaded any longer with "kexec_load failed: Permission denied". Excerpt from my journal: ------------------------< snip snip snip >----------------------------- load.sh[1742]: kexec_file_load failed: Permission denied kernel: ima: impossible to appraise a kernel image without a file descriptor; try using kexec_file_load syscall. load.sh[1742]: kexec_load failed: Permission denied load.sh[1742]: entry = 0x4ade9c730 flags = 0x3e0001 load.sh[1742]: nr_segments = 8 load.sh[1742]: segment[0].buf = 0x1e207e0 load.sh[1742]: segment[0].bufsz = 0x70 load.sh[1742]: segment[0].mem = 0x4a2000000 load.sh[1742]: segment[0].memsz = 0x1000 load.sh[1742]: segment[1].buf = 0x1e28820 load.sh[1742]: segment[1].bufsz = 0x168 load.sh[1742]: segment[1].mem = 0x4a2001000 load.sh[1742]: segment[1].memsz = 0x1000 load.sh[1742]: segment[2].buf = 0x7f22cc853010 load.sh[1742]: segment[2].bufsz = 0x1252c74 load.sh[1742]: segment[2].mem = 0x4aadad000 load.sh[1742]: segment[2].memsz = 0x1253000 load.sh[1742]: segment[3].buf = 0x7f22cdaaa410 load.sh[1742]: segment[3].bufsz = 0x7cdae0 load.sh[1742]: segment[3].mem = 0x4ac000000 load.sh[1742]: segment[3].memsz = 0x1e4d000 load.sh[1742]: segment[4].buf = 0x1e1a420 load.sh[1742]: segment[4].bufsz = 0x457c load.sh[1742]: segment[4].mem = 0x4ade97000 load.sh[1742]: segment[4].memsz = 0x5000 load.sh[1742]: segment[5].buf = 0x1e13070 load.sh[1742]: segment[5].bufsz = 0x70e0 load.sh[1742]: segment[5].mem = 0x4ade9c000 load.sh[1742]: segment[5].memsz = 0x9000 load.sh[1742]: segment[6].buf = 0x1e11f80 load.sh[1742]: segment[6].bufsz = 0xc00 load.sh[1742]: segment[6].mem = 0x4adea5000 load.sh[1742]: segment[6].memsz = 0x4000 load.sh[1742]: segment[7].buf = 0x7f22cc7fb010 load.sh[1742]: segment[7].bufsz = 0x57000 load.sh[1742]: segment[7].mem = 0x4adea9000 load.sh[1742]: segment[7].memsz = 0x57000 kdump[24916]: FAILED to load kdump kernel: /sbin/kexec -p /boot/vmlinuz-5.0.2-1-default --append="quiet no_console_suspend consoleblank=0 systemd.log_target=kmsg log_buf_len=1M printk.devkmsg=on elevator=deadline sysrq=yes reset_devices acpi_no_memhotplug cgroup_disable=memory nokaslr numa=off irqpoll nr_cpus=1 root=kdump rootflags=bind rd.udev.children-max=8 disable_cpu_apicid=0 panic=1" --initrd=/boot/initrd-5.0.2-1-default-kdump , Result: kexec_load failed: Permission denied entry = 0x4ade9c730 flags = 0x3e0001 nr_segments = 8 segment[0].buf = 0x1e207e0 segment[0].bufsz = 0x70 segment[0].mem = 0x4a2000000 segment[0].memsz = 0x1000 segment[1].buf = 0x1e28820 segment[1].bufsz = 0x168 segment[1].mem = 0x4a2001000 segment[1].memsz = 0x1000 segment[2].buf = 0x7f22cc853010 segment[2].bufsz = 0x1252c74 segment[2].mem = 0x4aadad000 segment[2].memsz = 0x1253000 segment[3].buf = 0x7f22cdaaa410 segment[3].bufsz = 0x7cdae0 segment[3].mem = 0x4ac000000 segment[3].memsz = 0x1e4d000 segment[4].buf = 0x1e1a420 systemd[1]: kdump.service: Main process exited, code=exited, status=255/EXCEPTION systemd[1]: kdump.service: Failed with result 'exit-code'. systemd[1]: Failed to start Load kdump kernel and initrd. ------------------------< snip snip snip >----------------------------- Any idea what to do to get kdump back? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 7

[opensuse-support] /proc/sys/net/ipv4/conf/all/rp_filter = 1 might break connectivity checking for IPv4 on this device
by mh＠mike.franken.de 25 Mar '19

25 Mar '19

Hi *, since the last update of my Tumbleweed machines I get the following warnings in my journal: Mär 25 21:16:53 client NetworkManager[1757]: <warn> [1553545013.0450] device (p3p2): connectivity: "/proc/sys/net/ipv4/conf/all/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device Mär 25 21:16:53 client NetworkManager[1757]: <warn> [1553545013.0562] device (wlp2s0): connectivity: "/proc/sys/net/ipv4/conf/all/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device Only information I could find was a kb article named "Applying SLES 11 SP 1 Causing Communication Issues": https://support.microfocus.com/kb/doc.php?id=7007649 Should I follow the instructions in this article? Or should I ignore the warnings on my clients, which are not multi homed? Thx and bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] Digest verification failed when doing system upgrade
by Ey P 24 Mar '19

24 Mar '19

Hi. I got "Digest verification failed for file 'glibc-devel-2.26-lp150.11.9.1.x86_64.rpm'" warning when doing system upgrade using 'sudo zypper up' on Leap 15.0. Anyone can help me out of this? Thanks. -- >From Ey P -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 4

[opensuse-support] failing boot, apparently not reading EFI partitioin
by Patrick Shanahan 24 Mar '19

24 Mar '19

toshiba satellite laptop S55-C5274 dualboot via grub Tumbleweed (primary) and win10 cannot boot into either system did have broken xfs on /dev/sda7 (home) backed up entire /home/<user> to an external disk correct brokenness with xfs_repair -L made partition mountable do not appear to have lost anything # efibootmgr RootCurrent: 0003 Timeout: 0 seconds BootOrder: 2001 2003 2002 Boot0000* Realtek PXE Boot0001* Realtek PXE Boot0003* EFI USB Device (ASIX AX88772 USB Fast Ethernet Controller) Boot2001* EFI USB Device Boot2002* EFI DVD/CDROM Boot2003* EFI Network grep efi /etc/fstab UUID=52B7-E591 /boot/efi vfat defaults 0 0 from "journalctl -xb" Mar 20 16:13:52 toshiba systemd[1]: dev-disk-by\x2duuid-52B7\x2dE591.device: Job dev-disk-by\x2duuid-52B7\x2dE591.device/start timed out. Mar 20 16:13:52 toshiba systemd[1]: Timed out waiting for device /dev/disk/by-uuid/52B7-E591. -- Subject: A start job for unit dev-disk-by\x2duuid-52B7\x2dE591.device -- has failed -- Defined-By: systemd -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- A start job for unit dev-disk-by\x2duuid-52B7\x2dE591.device has -- finished with a failure. full output from "journalctl -xb" is here http://wahoo.no-ip.org/~paka/journalctl.xb.txt machine is booted to kernel-default 4.20.12 using an openSUSE live disk but is in maintenence mode other information available but I don't know what else is relevant or necessary. help appreciated, tks -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

7 43

[opensuse-support] Questions on dnsmasq
by Hagen Buliwyf 22 Mar '19

22 Mar '19

In order to learn more about DNS, DNSSEC, ... i'm playing around with DNSMASQ (openSUSE Leap 15.0, KDE, NetworkManager) as a local DNS-Server (no DHCP). It works fine so far. However, although dnssec is enabled in dnsmasq.conf the log shows that only 12% of all queries return an IP validated as SECURE. Queries for opensuse.pool.ntp.org, de.pool.ntp.org, opensuse.org or my NetBankingSite return IPs validated as INSECURE. Currently i have enabled dnsmasq (systemctl enable dnsmasq) and use dns=none in a NetworkManager config file in /etc/NetworkManager/conf.d/. Would it be better to give the dnsmasq-handling to NetworkManager (dns=dnsmasq) ? Is there a(nother) way to improve security (like using DNS-over-TLS, DNS-over-HTTPS, ...) and if so how can i implement it? Thank you for any advice! Regards Hagen -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 3

[opensuse-support] Tumbleweed on DELL XPS 13 9370: fwupdmgr: Secure boot is enabled, but shim isn't installed to the EFI system partition
by mh＠mike.franken.de 21 Mar '19

21 Mar '19

Hi *, on my DELL XPS13 9370 running Tumbleweed with the latest snapshot I get an error, when trying to update the system BIOS via fwupdmgr: $ fwupdmgr update No upgrades for XPS 13 9370 Thunderbolt Controller, current is 33.00: 33.00=same, 28.00=older Downloading 0.1.8.1 for XPS 13 9370 System Firmware... Decompressing… [***************************************] Authenticating… [***************************************] Updating XPS 13 9370 System Firmware… ] Scheduling… [***************************************] Secure boot is enabled, but shim isn't installed to the EFI system partition My /boot/efi/EFI tree looks like this: /boot/efi/EFI ├── Boot │ ├── bootx64.efi │ ├── en-us │ │ └── bootx64.efi.mui │ ├── fallback.efi │ └── shimx64.efi ├── Microsoft │ └── Boot │ ├── BCD │ ├── BCD.LOG │ ├── Fonts │ │ ├── chs_boot.ttf │ │ ├── cht_boot.ttf │ │ ├── jpn_boot.ttf │ │ ├── kor_boot.ttf │ │ ├── malgun_boot.ttf │ │ ├── meiryo_boot.ttf │ │ ├── msjh_boot.ttf │ │ ├── msyh_boot.ttf │ │ ├── segmono_boot.ttf │ │ ├── segoe_slboot.ttf │ │ └── wgl4_boot.ttf │ ├── Resources │ │ └── bootres.dll │ └── en-us ├── dell │ ├── bios │ │ └── recovery │ │ └── bios_cur.rcv │ └── logs │ └── diags_current.xml ├── opensuse │ ├── MokManager.efi │ ├── boot.csv │ ├── fw │ ├── fwupdx64.efi │ ├── grub.cfg │ ├── grub.efi │ ├── grubx64.efi │ └── shim.efi ├── opensuse-tumbleweed │ ├── MokManager.efi │ ├── boot.csv │ ├── fw │ │ ├── fwupd-3b8c8162-188c-46a4-aec9-be43f1d65697.cap │ │ └── fwupd-7ceaf7a8-0611-4480-9e30-64d8de420c7c.cap │ ├── fwupdx64.efi │ ├── grub.cfg │ ├── grub.efi │ ├── grubx64.efi │ └── shim.efi └── ubuntu ├── MokManager.efi ├── MokSBStateSet.efi ├── fw ├── fwupx64.efi ├── grub.cfg ├── grubx64.efi └── shimx64.efi I couldn't find any hint for this exact message. What is missing here exactly? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 2

[opensuse-support] package database corruption - SOLVED
by DennisG 20 Mar '19

20 Mar '19

On 3/19/19 7:43 PM, DennisG wrote: > On 3/19/19 7:01 PM, Knurpht-openSUSE wrote: >> Op dinsdag 19 maart 2019 23:44:47 CET schreef DennisG: >>> After having run a routine YaST Online Update, somehow my package >>> database appears to have gotten corrupted. >>> >>> ... >>> >>> I assume that the package database is somehow corrupted. What can I do >>> to correct this problem? >> If it's the rpmdb: >> rpm --rebuilddb > > Thanks, Knurpht! > > I found the "zypper clean -a" command, which fixed about half the > errors. But I could not get any further, tried all the zypper ref > commands with no success (even though the man page indicates "refresh" > can rebuild the db; that is apparently something different). > > However, using rpm to rebuild the database allowed zypper to remove > the old version entries. All is good now. > > Thanks again. > > --dg Sent my reply directly to Knurpht rather than to the list - my bad. Also, thanks Patrick and Felix for your helpful suggestions, both of which would have probably worked. I confess I never really learned rpm, have always gotten by with YaST/zypper. Thanks again to all. --dg -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support] Tde and opensuse
by Christian Schmitz 20 Mar '19

20 Mar '19

Hi everyone I have TDE installed on my opensuse tumbleweed. All is working almost fine. start the computer, the sytem boot, and load trinity desktop and my session. The problem is when i want shutdown the system, i select "power off", TDE is closed but i get the graphical login (¿SDDM?). The TDE mailing list said that i need switch to TDM login manager and suggest edit /etc/sysconfig file but nothing change. I read that in newes distributions is not longer used sysconfig file to admin display manager. ¿why sddm do not talk with TDE to shutdown? ¿how i can switch to TDM? Best Regards. Christian -- Be Free, Be Linux -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 3

[opensuse-support] Keep kernel from Kernel:Stable until Leap 15.1 release
by Vinzenz Vietzke 20 Mar '19

20 Mar '19

Hi there, I have a laptop here which is only partially working with Leap 15.0 kernel but works fine with current 15.1 kernel version. The needed fixes would be too much work to be backported, especially as Leap 15.1 is incoming soon. [1] So, is there a way to install the laptop with Leap 15.0 plus Leap 15.1 kernel and to - as soon as it's released - pull the rest of the system up to 15.1 as well? And if so - are there any severe troubles to expect? Regards, vinz. [1] https://bugzilla.opensuse.org/show_bug.cgi?id=1129762 -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 2

[opensuse-support] Scripting problem
by Carlos E. R. 20 Mar '19

20 Mar '19

Hi, I have a scripting problem. I want to create relative paths. Googling told me I need to use: realpath --relative-to=something someotherthing But I can't find the correct concoction. I have the following structure (TV recordings): /home/cer/FusionTst/Videos/3_MyBook_Videos/Lore.mpeg /home/cer/FusionTst/Videos/3_MyBook_Videos/Big Bang/notes /home/cer/FusionTst/Videos/3_MyBook_Videos/Big Bang/Season 6/06x01.mpeg From that list of absolute paths, I want to produce a relative one: 3_MyBook_Videos/Lore.mpeg or ./3_MyBook_Videos/Lore.mpeg ../3_MyBook_Videos/Big Bang/notes ../../3_MyBook_Videos//Big Bang/Season 6/06x01.mpeg I got a headache, but no working solution. Example: cer@Isengard:~/FusionTst/Videos> realpath --relative-to="/home/cer/FusionTst/Videos/" "/home/cer/FusionTst/Videos/3_MyBook_Videos/Lore.mpeg" ../../../../data/My_Book/Fusion/Videos/Lore.mpeg cer@Isengard:~/FusionTst/Videos> cer@Isengard:~/FusionTst/Videos> realpath --relative-to="/home/cer/FusionTst/Videos/3_MyBook_Videos/Lore.mpeg" "/home/cer/FusionTst/Videos/" ../../../../../home/cer/FusionTst/Videos cer@Isengard:~/FusionTst/Videos> Previous to that I was using a method of my own that worked on some, failed on others. Then I stumbled into this "realpath" command, but I can not make it work as I need. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

7 18

[opensuse-support] A stop job is running for User Manager for UID 0 (nnnnnnnnn/2min)
by Felix Miata 20 Mar '19

20 Mar '19

This huge reboot/shutdown delay is highly annoying. When shutdown needs to happen, it needs to happen now, not at the whim of systemd. I haven't figured out what triggers it, but it seems like maybe something that happens during zypper dup related to KDM(3 or 4) or Plasma5. It doesn't always happen. Last to happen here was on TW20190314 host big31 on first post-dup boot. What make ps -A produce " 983 ? 00:00:00 (sd-pam)"? What exactly is "User Manager"? Is this just happening to me? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

5 8

[opensuse-support] package database corruption
by DennisG 20 Mar '19

20 Mar '19

After having run a routine YaST Online Update, somehow my package database appears to have gotten corrupted. Specifically, I have ~30 packages where YaST/zypper thinks that the older (replaced) version is still installed and therefore should be deleted. The new version was installed in the update, and YaST Software shows that as the installed version. However, when YaST/zypper attempts to delete that older version, it fails because that version is no longer found on the system. Yet when I run "zypper se -s", it reports that both versions are installed. If I tell zypper to rm the older version with the -f (force) option, it errors on being unable to find it. If I tell zypper to delete the entire package (so I can just reinstall the new version), it again returns an error saying that it cannot find it, displaying the old version number. Forcing a reinstall again installs the newest version, but the problem still exists. I've checked the dates on a sampling of files from these packages, and they are the newest, so the initial updates were done correctly. The old package versions and the old files indeed do not exist - except in the mind of libzypp. I assume that the package database is somehow corrupted. What can I do to correct this problem? TIA, --dg -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

5 4

[opensuse-support] Tumbleweed kernel 5.x: ima: impossible to appraise a kernel image without a file descriptor; try using kexec_file_load syscall.
by mh＠mike.franken.de 19 Mar '19

19 Mar '19

Hi *, any idea, what ima: impossible to appraise a kernel image without a file descriptor; try using kexec_file_load syscall. means? I get this message on my Tumbleweed machines since kernel 5.x. TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] Re: [opensuse-factory] What alternative kernel can we use on Leap 15.0?
by Michal Kubecek 19 Mar '19

19 Mar '19

On Tuesday, 19 March 2019 11:37 Carlos E. R. wrote: > I have problems with hibernation crashing in my 15.0 machine, on > restore. The situation has improved, but it always crashes after 3..6 > cycles. The remaining recommendation is to use a more modern kernel. > > The > <https://download.opensuse.org/repositories/Kernel:/stable/standard/x8 > 6_64/> has version 5. This is way too advanced for Leap 15.0. In which sense? You may also want newer versions of system utilities like iproute2 or ethtool if you want access to some new features but in general, kernel is relatively independent of the rest of the system. I'm using Kernel:stable kernel on one of my 15.0 systems (and Kernel:HEAD on another, but that's mostly to test it) and there is no obvious incompatibility. > <http://download.opensuse.org/tumbleweed/repo/oss/x86_64/> has > version 5. But just yesterday I managed to download version 4.20 from > there, today they have disappeared. ... > Which is the best kernel to use for people on 15.0 that need a more > modern kernel? > > Michal Kubecek said that the TW kernel would make more sense > (<https://lists.opensuse.org/opensuse-factory/2019-01/msg00325.html>) > > Takashi Iwai said re OBS Kernel:stable "another bigger disadvantage is > the lack of KMPs" and "Also, the Nvidia KMP build is often broken > with each kernel version update. It'd be another reason to stick > with TW kernel, not the bleeding edge one in OBS Kernel:stable." > (<https://lists.opensuse.org/opensuse-factory/2019-01/msg00232.html>) Kernel:stable OBS project builds daily snapshot of the "stable" branch in our repository. This is where kernel for Tumbleweed is submitted from so there is not much of a difference. Kernel:stable is a bit ahead, usually few days but it can be up to 2-3 weeks when switching to a new version. And with Tumbleweed, you know the kernel has passed openQA automatic tests so that the risk that it's seriously broken is lower. As for the out-of-tree (or even closed source) modules, there is no difference: neither Kernel:stable nor Tumbleweed kernels preserve kABI or (kernel) API so that you have to expect problems form time to time. > <https://download.opensuse.org/repositories/Kernel:/openSUSE-15.0/stan > dard/x86_64/> has the same version as Leap. The relationship between Kernel:openSUSE-15.0 and Leap 15.0 updates similar to Kernel:stable vs. Tumbleweed repository, i.e. the former are daily snapshots built from the git branch. Michal Kubecek -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

Re: [opensuse-support] problems with new kernel-default-5.0.1-1.2.x86_64
by Patrick Shanahan 17 Mar '19

17 Mar '19

cannot compile kernel module for nvidia 390.87 (last for my card) with new kernel-default-5.0.1-1.2.x86_64 sh ./NVIDIA-Linux-x86_64-390.87.run -aqs --install-libglvnd --no-drm /var/log/nvidia-installer.log is here: http://wahoo.no-ip.org/~paka/nvidia-installer.log cannot run newer version NVIDIA* as my GTS450 card is no longer supported. rebooted to kernel-default-4.20.13-1.2.x86_64 successfully rebuilt nvidia 390.87 changed to graphical.target system did not switch to vt7, and graphical interface did not display returned to multi-user.target and ran successfully startx -- :0 tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 1

[opensuse-support] [SOLVED] nvidia 390.87 build fails with kernel-default-devel-5.0.1-1.2.x86_64
by Patrick Shanahan 17 Mar '19

17 Mar '19

* Patrick Shanahan <paka(a)opensuse.org> [03-15-19 18:04]: > cannot compile kernel module for nvidia 390.87 (last for my card) with new > kernel-default-devel-5.0.1-1.2.x86_64 > > sh ./NVIDIA-Linux-x86_64-390.87.run -aqs --install-libglvnd --no-drm > > /var/log/nvidia-installer.log is here: > http://wahoo.no-ip.org/~paka/nvidia-installer.log > > cannot run newer version NVIDIA* as my GTS450 card is no longer supported. NVIDIA-Linux-x86_64-390.116.run package works with 5.0* kernel-default. tks Larry Finger -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] Weird kernel message during boot
by Neil Rickert 16 Mar '19

16 Mar '19

Tumbleweed (64-bit) at 20190314: The following lines are from "dmesg" output: [ 1.774479] Couldn't get size: 0x800000000000000e [ 1.774490] fbcon: Taking over console [ 1.774491] MODSIGN: Couldn't get UEFI db list [ 1.774513] Couldn't get size: 0x800000000000000e [ 1.774515] Couldn't get UEFI MokListRT [ 1.774535] Couldn't get size: 0x800000000000000e [ 1.774536] Couldn't get UEFI dbx list I am seeing 4 of those lines on the screen in early boot (before prompted for LUKS passphrase. The lines on the boot screen are the three "Couldn't get size" lines and the "MODSIGN" line. It is not causing problems, and I am ignoring for now. But I'm posting this in case they matter. I see these only with the 5.0 kernel. I did not see them with the previous 4.20 kernels. I do not see this with a legacy BIOS. I do not see this with a 64-bit UEFI BIOS. I only see it with a 32-bit UEFI BIOS ("ia32"). I should add that this is on a KVM virtual machine, with the OVMF UEFI firmware. I do not have a physical machine with ia32 firmware. My best guess is that the kernel sees that this is a UEFI system but fails to recognize that it is using 32-bit UEFI rather than 64-bit UEFI. -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 2

[opensuse-support] clamav
by mike 16 Mar '19

16 Mar '19

Hi, Still getting freshclam stopping on update with nearly 100% cpu, having to stop it with Cntrl-C. Also recommending update to clamav-0.101.1. Should I wait for opensuse-tumbleweed update or do it myself?? mike s -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

1 0

[opensuse-support] kernel: pstore: Unknown compression: deflate
by mh＠mike.franken.de 16 Mar '19

16 Mar '19

Hi *, I updated one of my openSUSE Leap 15.0 servers to kernel 5.0.2-2.gd1f1d19-default today. Everything seems to work ok - and it is significantly faster, especially regarding network performance. I get one error message during boot, though: kernel: zswap: loaded using pool lzo/zbud perth kernel: pstore: Unknown compression: deflate I couldn't find any information for this message. Any idea, how to solve it? TIA. Bye. Michael. -- Michael Hirmke -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support] LEAP 15 live image via PenDrive YUMI
by David T-G 11 Mar '19

11 Mar '19

Hi, all -- I am trying to load the LEAP 15 live image after having use PenDrive's YUMI to install it on my thumb drive. When it boots, however, it asks for the installation medium path, giving me cd:/ hd:/ Enter another URL choices. Neither preset appears to work, and I don't know what I'd put as "another". Any suggestions? TIA & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 1

[opensuse-support][TW] menus black Plasma screen
by Felix Miata 11 Mar '19

11 Mar '19

Today is not the first time getting black screens trying to use Plasma's app menu. KDM and XDM are the only installed DMs. After duping to 20190307 (32bit today, but other TW installations 64 bit), first attempt to multi-user.target startx Plasma session produced a black screen. I killed the session, deleted content of ~/.cache/, then tried again. Session opened normally, but attempting to open an app from menu turned the screen black. I had to move the mouse near upper right corner and left click to unblack the screen. Then I right clicked the starter to see what the menu style is (non-default, KDE3-style) and the screen turned black again, this time non-recoverably except to close the session via remote login. .xsession-errors was last written 2 months ago. If journal or dmesg contain clues, I'm missing them. Ctrl-Alt-BS instead of closing the session powered down the PC. On reboot IceWM from startx worked as expected. Reboot without vga=791 or video=1440x900@60 and with 5 produces working KDM and succeeds to open IceWM working as expected. Plasma from KDM is still blacking the screen in similar fashion to opening from startx. Right click on desktop also blacks, and Ctrl-Alt-BS worked as expected on last try. # inxi -G Graphics: Device-1: Advanced Micro Devices [AMD/ATI] RV370 [Radeon X600/X600 SE] driver: radeon v: kernel Display: server: X.org 1.20.4 driver: ati,radeon unloaded: fbdev,modesetting,vesa tty: 189x52 # uname -a Linux gx151 4.20.13-1-pae #1 SMP Wed Feb 27 18:03:26 UTC 2019 (fb7c4a5) i686 i686 i386 GNU/Linux -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 5

[opensuse-support] Overall 42.3 responsiveness way down. SSD going/gone bad?
by Felix Miata 10 Mar '19

10 Mar '19

# cat /proc/mdstat Personalities : [raid1] md5 : active raid1 sdb10[0] sdc10[2] 655359808 blocks super 1.0 [2/2] [UU] bitmap: 0/5 pages [0KB], 65536KB chunk md1 : active raid1 sdb6[0] sdc6[2] 4095936 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk md4 : active raid1 sdc9[2] sdb9[0] 217087808 blocks super 1.0 [2/2] [UU] bitmap: 0/2 pages [0KB], 65536KB chunk md3 : active raid1 sdc8[2] sdb8[0] 73727872 blocks super 1.0 [2/2] [UU] bitmap: 1/1 pages [4KB], 65536KB chunk md2 : active raid1 sdc7[2] sdb7[0] 8191936 blocks super 1.0 [2/2] [UU] bitmap: 0/1 pages [0KB], 65536KB chunk md0 : active raid1 sdb5[0] sdc5[2] 8834944 blocks super 1.0 [2/2] [UU] bitmap: 1/1 pages [4KB], 65536KB chunk unused devices: <none> # df -lhT Filesystem Type Size Used Avail Use% Mounted on /dev/sda10 ext4 18G 7.8G 8.7G 48% / /dev/sda3 ext2 1.2G 641M 550M 54% /disks/boot /dev/md3 ext4 70G 26G 44G 38% /home /dev/md0 ext4 8.4G 1.7G 6.3G 21% /tmp /dev/md1 ext4 3.9G 1.7G 2.2G 43% /usr/local /dev/md4 ext4 206G 119G 88G 58% /private /dev/md2 ext4 7.8G 1.8G 6.0G 23% /srv /dev/md5 ext4 620G 422G 199G 68% /secret # fstrim -av /disks/boot: 0 B (0 bytes) trimmed /: 0 B (0 bytes) trimmed # grep -i trim /etc/fstab # parted -l Model: ATA PNY CS900 120GB (scsi) Disk /dev/sda: 120GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 264MB 263MB primary fat16 type=06 2 264MB 2781MB 2517MB primary hidden, type=17 3 2781MB 4039MB 1258MB primary ext2 boot, type=83 4 4039MB 120GB 116GB extended type=05 5 4039MB 21.5GB 17.4GB logical linux-swap(v1) type=82 6 21.5GB 25.7GB 4194MB logical ext3 type=83 7 25.7GB 44.5GB 18.9GB logical ext4 type=83 8 44.5GB 63.4GB 18.9GB logical ext4 type=83 9 63.4GB 82.3GB 18.9GB logical ext4 type=83 10 82.3GB 101GB 18.9GB logical ext4 type=83 11 101GB 120GB 18.9GB logical ext4 type=83 # hdparm -tT /dev/sda /dev/sdb /dev/sdc /dev/sda: Timing cached reads: 13988 MB in 2.00 seconds = 7010.44 MB/sec Timing buffered disk reads: 22 MB in 3.10 seconds = 7.09 MB/sec /dev/sdb: Timing cached reads: 14114 MB in 2.00 seconds = 7074.17 MB/sec Timing buffered disk reads: 358 MB in 3.01 seconds = 118.77 MB/sec /dev/sdc: Timing cached reads: 14530 MB in 1.99 seconds = 7283.44 MB/sec Timing buffered disk reads: 406 MB in 3.02 seconds = 134.23 MB/sec # smartctl -t long /dev/sda ... Testing has begun. Please wait 30 minutes for test to complete. ... # smartctl -a /dev/sda smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.165-81-default] (SUSE RPM) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: PNY CS900 120GB SSD Serial Number: PNY06182239150108A56 LU WWN Device Id: 5 f8db4c 061808a56 Firmware Version: CS900612 User Capacity: 120,034,123,776 bytes [120 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Form Factor: 2.5 inches Device is: Not in smartctl database [for details use: -P showall] ATA Version is: Unknown(0x0ff8) (minor revision not indicated) SATA Version is: SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Thu Feb 21 12:12:21 2019 EST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (65535) seconds. Offline data collection capabilities: (0x79) SMART execute Offline immediate. No Auto Offline data collection support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 30) minutes. Conveyance self-test routine recommended polling time: ( 6) minutes. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0 9 Power_On_Hours 0x0012 100 100 000 Old_age Always - 4244 12 Power_Cycle_Count 0x0012 100 100 000 Old_age Always - 172 168 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 0 170 Unknown_Attribute 0x0003 088 088 000 Pre-fail Always - 134 173 Unknown_Attribute 0x0012 100 100 000 Old_age Always - 262151 192 Power-Off_Retract_Count 0x0012 100 100 000 Old_age Always - 128 194 Temperature_Celsius 0x0023 067 067 000 Pre-fail Always - 33 (Min/Max 33/33) 218 Unknown_Attribute 0x000b 100 100 050 Pre-fail Always - 0 231 Temperature_Celsius 0x0013 100 100 000 Pre-fail Always - 99 241 Total_LBAs_Written 0x0012 100 100 000 Old_age Always - 110 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 4244 - # 2 Extended offline Completed without error 00% 3802 - # 3 Extended offline Interrupted (host reset) 00% 3777 - # 4 Extended offline Completed without error 00% 3130 - # 5 Extended offline Completed without error 00% 2291 - # 6 Extended offline Completed without error 00% 1748 - # 7 Extended offline Completed without error 00% 1620 - # 8 Extended offline Completed without error 00% 1619 - # 9 Extended offline Completed without error 00% 1204 - #10 Extended offline Completed without error 00% 948 - #11 Extended offline Completed without error 00% 109 - #12 Short offline Completed without error 00% 46 - #13 Short offline Completed without error 00% 40 - #14 Short offline Completed without error 00% 36 - #15 Extended offline Completed without error 00% 35 - #16 Short offline Completed without error 00% 26 - #17 Short offline Interrupted (host reset) 00% 24 - SMART Selective self-test log data structure revision number 0 Note: revision number not 1 implies that no selective self-test has ever been run SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. /dev/sda was new in July 2018. What should I do next? -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

5 14

[opensuse-support] How to keep X session in background active?
by Maximilian Trummer 07 Mar '19

07 Mar '19

When running two X sessions (KDE Plasma), I've found that the currently inactive one seems to get "hibernated" somehow. I couldn't find an answer online because all questions I found were about SSH timeouts and whatnot. The most annoying side effect of that is network connections being terminated, but it also has other effects like the analog clock widget being halted so you see the cursor jump after you switch back to that session. Sometimes the secondary X session also locks the screen as you switch to it, because it suddenly awoke from its slumber and noticed that it should be locked already after that time. What's the reason for this behaviour? Is there any way to keep everything active and running in inactive X sessions? regards

8 13

[opensuse-support] Freshclam hangs with 100% CPU
by Bjoern Voigt 06 Mar '19

06 Mar '19

Freshclam hangs today with 100% CPU time after downloading daily-25380.cdiff. I already stopped freshclam, cleared /var/lib/clamav and started Freshclam again as a service or manually. Setup: - openSUSE Tumbleweed 20190301 - ClamAV 0.100.2/25379/Tue Any ideas? Greetings, Björn -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

2 2

[opensuse-support] Find out what pulls in new packages on 'zypper dup'
by Maximilian Trummer 05 Mar '19

05 Mar '19

I'm trying to do a 'zypper dup' on a headless server, but it wants to install a load of unnecessary packages. Many of them are gtk stuff, but also cryptsetup, mdadm, PackageKit and fuse. The upgrade would be from the currently running 20190222 to 20190301, which upgrades the schemes 'base', 'basesystem' and 'minimal_base'. How can I find out what package is trying to pull in these new dependencies? regards

5 14

[opensuse-support] Has anybody experimented with reiserfs4?
by Carlos E. R. 05 Mar '19

05 Mar '19

Hi, Has anybody experimented with reiserfs4? I see packages, but no wiki page on our system. I do not know how to do it. I'm getting curious because I heard it supports compression. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

2 4

[opensuse-support] Help with wifi adapter [tp-link Archer T2U]
by Ralph 03 Mar '19

03 Mar '19

[os Leap 15, xfce] Help please. Trying to get the following usb wifi device working with Leap 15. OS sees it (lsusb) but doesn't seem to know what to do with it. Device works as expected when tested on a win10 boot on same machine so it and the port(s) are functional. Device in question is sold under the name "tp-link" as "Model: Archer T2U (US) Ver 2.0" and it's an "AC600 Wireless Dual Band USB Adapter". 67: USB 00.0: 0000 Unclassified device [Created at usb.122] Unique ID: ADDn.83qT90Beo9D Parent ID: k4bc.2DFUsyrieMD SysFS ID: /devices/pci0000:00/0000:00:14.0/usb1/1-1/1-1:1.0 SysFS BusID: 1-1:1.0 Hardware Class: unknown Model: "Ralink MT7610U ("Archer T2U" 2.4G+5G WLAN Adapter" Hotplug: USB Vendor: usb 0x148f "Ralink Technology, Corp." Device: usb 0x761a "MT7610U ("Archer T2U" 2.4G+5G WLAN Adapter" Revision: "1.00" Serial ID: "1.0" Speed: 480 Mbps Module Alias: "usb:v148Fp761Ad0100dc00dsc00dp00icFFisc02ipFFin00" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #61 (Hub) Thanks. Ralph -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 6

[opensuse-support] How can I hibernate in shutdown mode?
by Carlos E. R. 02 Mar '19

02 Mar '19

Hi, some weeks ago I said I had crashes on restore from hibernation. Andrei Borzenkov told me to use HibernateMode=shutdown in systemd-sleep.conf. After reading man systemd-sleep.conf I fail to find a syntax that works. If I write Telcontar:~ # cat /etc/systemd/sleep.conf HibernateMode=shutdown Telcontar:~ # I get this message in syslog: > <4.4> 2019-02-28 03:52:59 Telcontar systemd-logind 1664 - - /etc/systemd/sleep.conf:1: Assignment outside of section. Ignoring. So I add a section: Telcontar:~ # cat /etc/systemd/sleep.conf [sleep] HibernateMode=shutdown Telcontar:~ # Now I get: <4.4> 2019-03-01 03:50:49 Telcontar systemd-logind 1639 - - /etc/systemd/sleep.conf:1: Unknown section 'sleep'. Ignoring. So, what is the correct syntax? Manual page systemd-sleep.conf(5) says: The following options can be configured in the "[Sleep]" section of /etc/systemd/sleep.conf or a sleep.conf.d file: SuspendMode=, HibernateMode=, HybridSleepMode= So the section is correct, isn't it? I don't understand :-( -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)

4 7

[opensuse-support] Virus or XORG?
by Christian Schmitz 01 Mar '19

01 Mar '19

Hello everyone: I have installed opensuse tumbleweed upgraded few days ago. Since few days (after last update) i found some extraneous folders in my home. They have 2 characters and sometimes AU/ bJ/ *A/ etc. My first suspect was a virus in my linux. The impossible does not exist but is really not probable because i am very carrefull use noscript, ghostery,adblockplus. i am after a firewal (my sever)l After search a little i found thar TDE create those folders and contain Xorg LOG. wolf@wolf:~/�U/.local/share/sddm> cd ~ #lsof |grep home\/wolf tdeio_fil 9185 wolf 2w REG 0,70 20764 6310086 /home/wolf/�U/.local/share/sddm/xorg-session.log tdeio_pop 9515 wolf 2w REG 0,70 20764 6310086 /home/wolf/�U/.local/share/sddm/xorg-session.log #ps ax 9515 ? S 0:00 tdeio_pop3 [tdeinit] pop3s /tmp/tdesocket-wolf/tdelauncherXiu5vQ.s 9185 ? S 0:00 tdeio_file [tdeinit] file /tmp/tdesocket-wolf/tdelauncherXiu5vQ.sl #ps axl 1 1000 9185 2041 20 0 71760 13300 core_s S ? 0:00 tdeio_file [tdeinit] file /tmp/tdesocket-wolf/tdelauncherXiu5vQ.s 1 1000 9515 2041 20 0 298932 19168 core_s S ? 0:00 tdeio_pop3 [tdeinit] pop3s /tmp/tdesocket-wolf/tdelauncherXiu5vQ.s PARENT=2041 1 1000 2041 1 20 0 68776 8108 core_s Ss ? 0:00 [tdeinit] tdeinit Running... Any hint will be appreciated. Best Rebards Christian Schmitz -- Be Free, Be Linux -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

3 3