- openSUSE Support

Curl failing frequently during zypper dup
by Marco Calistri 25 Sep '21

25 Sep '21

As per the subject. Today I get over 3000 packages to update and I had to frequently hit the "R" during zypper dup, in order to force curl to download the package again. Regards, Scarica Outlook per Android<https://aka.ms/AAb9ysg>

5 4

remote opensuse install
by jdd＠dodin.org 24 Sep '21

24 Sep '21

Hello, I use to have a remote server on the kimsufi.com dealer. I also used to install opensuse on it. alas opensuse don't seems to be anymore in the list of proposed distributions. I could install debian 10. I also have access to a remote rescue like interface to the server. So I may be able to install opensuse remotely I wonder what is the simpler way to do so, may be based on the https://en.opensuse.org/SDB:Remote_installation page I recently tried Yunohost, but this debian based server, cpanel clone, is really too much security paranoid, at the point I can't use my preferred applications, but the remote install is specially easy as explained here: https://yunohost.org/fr/install/hardware:vps_debian The disk is already partitioned, but I can probably redo it from the rescue system as needed I mostly need a web server (I know pretty well apache), a very basic install with yast is all I really need to start (no graphical system allowed) What do you think is the best/fastest option thanks jdd -- http://dodin.org

1 1

MS Teams does not work anymore after big system update
by Guadagnino Cristiano 24 Sep '21

24 Sep '21

Hi all, I know that MS Teams is not part of the standard repositories, but maybe someone has encountered the same problem I'm having. I need MS Teams for my work, so I added Microsoft's repo and installed it. It has been working flawlessly for some months now. Yesterday I got over 3000 packages to update. Everything went smoothly - apparently - but today I find that both Teams and Insync (a commercial Google Drive client) fail to start. Well, not exactly: they do start, but they don't work, and they keep producing core dumps until I kill them. Is anybody experiencing this problem? Hints? I'm on openSuse Tumbleweed 20210921. Thank you in advance Cris

4 5

waterfox browser fails, probably new glibc
by Patrick Shanahan 23 Sep '21

23 Sep '21

Anyone with a solution to using waterfox browser which fails since that last Tumbleweed upgrade which contained glibc 2.34? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode

3 2

TW with kernel 5.14.5 can't detect Realtek network devices
by Ariez Vachha - openSUSE 23 Sep '21

23 Sep '21

Folks! Did the upgrade latest TW upgrade with kernel 5.14.5 - Does not recognise either my Ethernet or Wifi devices. I have used grub to boot back to Kernel: 5.14.2-1-default. "hwinfo --network" only returns the loopback!!! Waiting for Realtek r8168 Ethernet and rtw89pci Wifi modules on Sauerland hardware repo, but I wonder if this will work if the kernel can't even detect the HW. Anyone else had this problem? -- Regards, Ariez ajv(a)opensuse.org

1 0

postfix fails to start automatically in laptop
by Carlos E. R. 17 Sep '21

17 Sep '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi, In this leap 15.2 laptop postfix fails to start atuomatically during boot, because network, handled by network manager, has not started yet: minas-tirith:~ # systemctl status postfix ● postfix.service - Postfix Mail Transport Agent Loaded: loaded (/usr/lib/systemd/system/postfix.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2021-08-28 14:10:44 CEST; 1h 34min ago Process: 3066 ExecStopPost=/etc/postfix/system/cond_slp deregister (code=exited, status=0/SUCCESS) Process: 2719 ExecStart=/usr/sbin/postfix start (code=exited, status=1/FAILURE) Process: 2699 ExecStartPre=/etc/postfix/system/update_postmaps (code=exited, status=0/SUCCESS) Process: 2695 ExecStartPre=/etc/postfix/system/update_chroot (code=exited, status=0/SUCCESS) Process: 2691 ExecStartPre=/etc/postfix/system/config_postfix (code=exited, status=0/SUCCESS) Process: 2668 ExecStartPre=/bin/echo Starting mail service (Postfix) (code=exited, status=0/SUCCESS) Tasks: 0 CGroup: /system.slice/postfix.service Aug 28 14:10:42 minas-tirith postfix[2719]: fatal: parameter inet_interfaces: no local interface found for 192.168.1.9 Aug 28 14:10:43 minas-tirith systemd[1]: postfix.service: Control process exited, code=exited status=1 Aug 28 14:10:44 minas-tirith systemd[1]: Failed to start Postfix Mail Transport Agent. Aug 28 14:10:44 minas-tirith systemd[1]: postfix.service: Unit entered failed state. Aug 28 14:10:44 minas-tirith systemd[1]: postfix.service: Failed with result 'exit-code'. minas-tirith:~ # And systemd does not try to start it again after network becomes available. Could something be changed in the service file to correct the situation? minas-tirith:~ # systemctl cat postfix # /usr/lib/systemd/system/postfix.service # This file is part of package postfix. # # Copyright (c) 2021 SuSE LINUX Products GmbH, Germany. # Authors: Werner Fink, Peter Varkoly # Please send feedback to https://bugs.opensuse.org/ # # Description: # # Used to start the postfix Mail Transport Agent service # which handles all mails stored at /var/spool/postfix/ and # all connections on port 25 aka smtp at localhost as well # as on all other network interfaces. # [Unit] Description=Postfix Mail Transport Agent After=nss-lookup.target network.target time-sync.target After=amavis.service mysql.service cyrus.service ldap.service openslp.service ypbind.service Conflicts=sendmail.service exim.service [Service] Type=forking PIDFile=/var/spool/postfix/pid/master.pid ExecStartPre=-/bin/echo 'Starting mail service (Postfix)' EnvironmentFile=-/etc/sysconfig/postfix ExecStartPre=/etc/postfix/system/config_postfix ExecStartPre=/etc/postfix/system/update_chroot ExecStartPre=/etc/postfix/system/update_postmaps ExecStart=/usr/sbin/postfix start ExecStartPost=/etc/postfix/system/wait_qmgr 60 ExecStartPost=/etc/postfix/system/cond_slp register ExecReload=/usr/sbin/postfix reload ExecReload=/usr/sbin/postfix flush ExecStop=/usr/sbin/postfix stop ExecStopPost=/etc/postfix/system/cond_slp deregister [Install] WantedBy=multi-user.target minas-tirith:~ # - -- Cheers, Carlos E. R. (from openSUSE Leap 15.2 x86_64 (Minas Tirith)) -----BEGIN PGP SIGNATURE----- iJIEAREIADoWIQQt/vKEw5659AgM/X2NrxRtxRYzXAUCYSo/nRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJEI2vFG3FFjNcCH8A/jFCI4mMJAEtro5ZmWF0 f5zV6ImW3pOzXTvkERWXcyGWAP9pgORQFrYXU2471LPWROerVmTvxU4c+MyVUI9x FacUgw== =Wx3+ -----END PGP SIGNATURE-----

3 6

Leap 15.2 - dovecot throws error "Invalid log_debug: event filter"
by mh＠mike.franken.de 16 Sep '21

16 Sep '21

Hi *, after the latest update for Leap 15.2 I get doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf: Invalid log_debug: event filter: syntax error, unexpected $end, expecting '=' or '>' or '<' Reason is log_debug = source:sieve in conf.d/10-logging.conf After commenting out this line dovecot starts without any further errors. But why is this line a problem all of a sudden? I couldn't find any reason. TIA. Bye. Michael.

1 0

[support] rebuild initrd configuration possible?
by Felix Miata 05 Sep '21

05 Sep '21

In Debians, whether to rebuild existing initrds for previously installed kernels when packages participating in their generation are updated is configurable. I don't remember the subject ever coming up in an openSUSE context, and I don't see any files in /etc/ that might cover the subject. Is this possible? My goal is to have them not rebuilt unless I decide for whatever reason they need to be. IOW, only build at kernel installation time, unless I expressly choose otherwise for any given kernel. For years I've been using immutable flags to prevent this, but I'm getting tired of the waste of time setting and unsetting the flag as kernels are added and removed. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata

2 1

Kernel:stable on Leap 15.3
by Bjoern Voigt 02 Sep '21

02 Sep '21

I always used the Kernel:stable repository on Leap 15.2 and now Leap 15.3. But updating this Kernels stopped with kernel-default-5.13.4-3.1.g91a0cca.x86_64, because requirements of newer Kernels are not met. # zypper in kernel-default-5.13.12 Loading repository data... Reading installed packages... Resolving package dependencies... Problem: the to be installed kernel-default-5.13.12-6.1.gd66b4c0.x86_64 conflicts with 'filesystem < 16' provided by the installed filesystem-15.0-11.3.2.x86_64 Solution 1: do not install kernel-default-5.13.12-6.1.gd66b4c0.x86_64 Choose the above solution using '1' or cancel using 'c' [1/c/d/?] (c): # rpm -q filesystem filesystem-15.0-11.3.2.x86_64 This is the ChangeLog message for kernel-default-5.13.12-6.1.gd66b4c0.x86_64: * Mo Aug 09 2021 ludwig.nussel(a)suse.de - Fix filesystem requirement and suse-release requires Reduce filesystem conflict to anything less than 16 to allow pulling the change into the next major stable version. Don't require suse-release as that's not technically required. Conflict with a too old one instead. - commit 913f755 "Next major stable version" means waiting for Leap 15.4? Greetings, Björn

6 7

Recent kernel update kills hibernate and power-off in Lenovo laptop.
by Carlos E. R. 26 Aug '21

26 Aug '21

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Recent kernel update kills hibernate and power-off in Lenovo laptop (Leap 15.2). Machine seems to proceed, but at the last moment is unable to power off, it seems, or gets stuck a bit earlier. kernel-default-5.3.18-lp152.84.1.x86_64 works kernel-default-5.3.18-lp152.87.1.x86_64 fails I don't have the time to collect any more information at this time, too busy. Later. Post what info you need and I'll answer later. - -- Cheers Carlos E. R. (from 15.1 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYSdpbRwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVsWgAnj/X6uUkdUaF8FfplAXJ Pci8rjYwAJ4kiCL8wN/CFG4Ryq2oOiLppocWjg== =rukP -----END PGP SIGNATURE-----

1 0