July 2019 - openSUSE Support - openSUSE Mailing Lists

[opensuse-support] Mailinglist outage yesterday
by Christian Boltz 19 Jul '19

19 Jul '19

Hello, (sorry for the massive cross-post - if you answer, please reply only on one mailinglist) TL;DR: If you sent a mail to one of the openSUSE mailinglists yesterday and it didn't arrive, please re-send it. Please also re-send any mail you sent to admin(a)o.o or board(a)o.o yesterday. Longer version: As you probably noticed by observing the silence in your inbox, the mailinglists were down yesterday. This downtime which had two reasons: a) postfix not starting on our outgoing mailserver after a kernel update and reboot - one of the server's IPs wasn't configured fast enough on boot and prevented starting postfix b) our mailinglist software needing additional AppArmor permissions after a kernel update. This is a known change for newer kernel versions, but shouldn't happen as part of a kernel update, therefore I opened https://bugzilla.opensuse.org/show_bug.cgi?id=1142120 The downtime started around 7:00 UTC (9:00 CEST). I noticed it in the evening, and around 21:50 UTC (23:50 CEST) everything worked again. a) wouldn't be too bad - the sending mailservers queues the mails, and they "just" get delayed. Unfortunately issue b) is more problematic - it seems the mailinglist software failed with $? = 0 so postfix thought the mails were successfully delivered, but in fact they are more or less lost. (Our mailinglist admin found them in the incoming/ directory, but he's on vacation with terrible internet access and probably can't do much about this in the next days. Sending out the then-old mails when he's back doesn't really make sense IMHO.) Therefore: If you sent a mail to one of our mailinglists yesterday and it didn't arrive, please re-send it. Please also re-send any mail you sent to admin(a)o.o or board(a)o.o yesterday. Regards, Christian Boltz -- Should you ever feel lonely or be overwhelmed with spare time: you know where to find us. [Dominique Leuenberger in opensuse-project] -- 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: Aw: Re: [opensuse-factory] Many problems since about Kernel 5.1.x on Tumbleweed Client - KDE isn't useable anymore
by Hans-Peter Jansen 17 Jul '19

17 Jul '19

Hi Ulf, first of all, given our subscriptions succeeded, let's keep the discussion here and only here, please, which will automatically avoid HTML as well ;-) Am Dienstag, 16. Juli 2019, 15:39:08 CEST schrieb ulfbart(a)gmx.net: > Gesendet: Dienstag, 16. Juli 2019 um 13:07 Uhr; Von: "Hans-Peter Jansen" > > Am Montag, 15. Juli 2019, 09:58:32 CEST schrieb ub22@xxxxxxx: > > Server (NFS 4 Server which is sharing /home config via YaST): > |- Client1 (/home mounted via & user via NIS) > > > Using a similar setup here. FYI: I'm using {open,}SUSE since > 20 years as well in both, commercial and private, settings. > Yes, allways done by YasT: > 1. Install NIS Client with Automount enabled This is the automount fstab pattern, that I use now: server:/path /net/server/path nfs noauto,x-systemd.automount,x-systemd.device- timeout=10,timeo=14 0 0 > On the most Clients KDE Plasma Crashes many times after login > > > Plasma runs fine here. > > Depends on the user. I switched to an newer user and the > Problem seams to be not available on it. I've only trouble > to forward some settings like the kwallet which was > encrypted with a key which seams to be on the new > user in kleopatra and also in kwallet5 not visible. If kwallet5 finds a plain kwallet4 config, it tries to convert the wallet to the new format with an assistant asking for both credentials. You need to remove the damaged kwallet5 settings beforehand. You can export/import kwallets manually as well. I've had cases with very old KDE{3,4} configs, which had some trouble as well. I tend to start with a new config then, and recover selective configs (e.g. firefox bookmarks and passwords). kmail config should be started anew. > > A general note: > > > > A NFS homed KDE is sub-optimal, when it comes to (heavy uses of) akonadi > > et.al. Thus, I'm using a different scheme for power users: I place /home > > on a > > local ssd, and symlink everything interesting from my shared server home. > > akonadi on this user don't work, due to a mail account which can't be > changed > since years, so kmail crashes before I can open it. Given, you get the basics behave again, you can reanimate akonadi with: rm -rf /home/$USER/.local/share/akonadi and start over again. You need to adjust the folders for all email identities in this case. > But anyway, this looks crazy, so I expect that temporary files should be > used > on local /tmp which is on my side always on a fast SSD No, akonadi stores its databases in the path above. Use a symlink to relocate that one onto your local ssd. > > server:/home /home/nfs nfs > > nfsvers=4,x-systemd.requires=nfs-mountd.service,x- > > > >systemd.requires=/home 0 0 > > > > If kmail is still too slow, switch to postgresql for akonadi. > > I will doublecheck this later on. So in the moment I don't use kmail anymore I cannot confirm your experience. I'm using TW and KDE including kmail successfully in NFS shared environments, but manage users with ldap, not yp. Most data is hosted by NFS, including VBox VMs(!), and all is working well. Server: openSUSE 15.0, Clients: TW. All smooth. Cheers, Pete -- 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] Many problems since about Kernel 5.1.x on Tumbleweed Client - KDE isn't useable anymore
by Hans-Peter Jansen 16 Jul '19

16 Jul '19

[just subscribed on opensuse-support, but replying to Ulfs original mail to factory, hence threading will be damaged. Sorry] Am Montag, 15. Juli 2019, 09:58:32 CEST schrieb ub22(a)gmx.net: > Hi Together, > > since some month I've a lot of trouble with my about 20 Years > old Home network, which was all running on Tumbleweed: > > Server (NFS 4 Server which is sharing /home config via YaST): > |- Client1 (/home mounted via & user via NIS) > |- Client2 (/home mounted via & user via NIS) > > ... > > |- Client5 (/home mounted via & user via NIS) Using a similar setup here. > On the most Clients KDE Plasma Crashes many times after login Plasma runs fine here. > If they are starting - it takes about 10 up to 30 minutes!!!! This much sounds like some kind of hardware issue. What does "ip --stats link show eth0" say (on both sides!)? > Afterwords the system hangs from time to time with normal > load and only the tracker extract info below. What can I do? > One client I installed the last ISO (from 8th July) but this > one don't mount /home well, so I need to unmount it and mount > again via: > > umount -f /home ; systemctl start home.mount ; systemctl status home.mount This is a well known problem. Try this: 192.168.2.1:/mnt/nfs4/home /home nfs nfsvers=4,x-systemd.requires=nfs- mountd.service 0 0 > # cat /etc/fstab (extract) > 192.168.2.1:/mnt/nfs4/home /home nfs defaults 0 0 In another mail, you wrote: > At the nfs-kernel-server the settings are at all host > fsid=0,crossmnt,rw,root_squash,sync,no_subtree_check Mind changing this to: rw,root_squash,async,no_subtree_check The sync option might develop more delays with more advanced kernel versions. A general note: A NFS homed KDE is sub-optimal, when it comes to (heavy uses of) akonadi et.al. Thus, I'm using a different scheme for power users: I place /home on a local ssd, and symlink everything interesting from my shared server home. server:/home /home/nfs nfs nfsvers=4,x-systemd.requires=nfs-mountd.service,x- systemd.requires=/home 0 0 If kmail is still too slow, switch to postgresql for akonadi. Good luck, Pete -- 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] NVIDIA repo not repsonding?
by Wayne Patton 12 Jul '19

12 Jul '19

I am running Tumbleweed and it's up to date. This morning I did a zypper ref and the NVIDIA repo isn't responding. Curious if other are seeing this as well?? zypper lr -u output for that repo: 1 | download.nvidia.com-tumbleweed | nVidia Graphics Drivers | Yes | (r ) Yes | Yes | https://download.nvidia.com/opensuse/tumbleweed I followed this guide when installing the NVIDA drivers: https://en.opensuse.org/SDB:NVIDIA_drivers Thanks Wayne

4 5

[opensuse-support][kde3] sounds accompanied by speaker clicks since upgrade 42.3 to 15.1
by Felix Miata 11 Jul '19

11 Jul '19

Most of upgrade went well enough, but this is annoying. At the start of any sound event, e.g. speaker-test -Dplug:front -c2 -l5 -twav, normal sound is accompanied by a double click in the speaker. At the end of any sound event, normal sound is accompanied by a single click. This never happened before the upgrade, but none of pulseaudio except for libpulse0 was ever installed before either. https://en.opensuse.org/SDB:Audio_troubleshooting makes no apparentl mention of this kind of output defect. Searching "speaker click linux -ubuntu -windows" produces no hit summaries resembling this annoyance. :-( alsa-info.sh output: http://fm.no-ip.com/Tmp/SUSE/Leap/alsa-info-msi85-s151.txt Connection is analog, since video to my display is via DVI. My motherboard has HDMI out, but my display only has DisplayPort and pin jack as audio inputs. Any suggestions? -- 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] No manual entry for .bash_history
by Felix Miata 04 Jul '19

04 Jul '19

How does one translate #1554421101 from .bash_history to a humanly recognizable date and time? -- 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 2

[opensuse-support] Is this a good forum for SLES12 + systemd questions?
by Brian Reichert 01 Jul '19

01 Jul '19

I use SLES 12 at $JOB, and have questions about the internals of systemd. I tried to subscribe to the systemd-devel mailing list, to ask questions there directly, but they don't seem to have a correctly-configured mail server; the confirmation email fails thusly: <systemd-devel-request(a)lists.freedesktop.org>: 131.252.210.177 does not like recipient. Remote host said: 550 5.1.1 <systemd-devel-request(a)lists.freedesktop.org>: Recipient address rejected: User unknown in local recipient table Giving up on 131.252.210.177. If there is a better forum to ask questions about systemd SLES 12, I'd appreciate a pointer. Nothing at http://lists.suse.com/mailman/listinfo/ seemed obvious... -- Brian Reichert <reichert(a)numachi.com> BSD admin/developer at large -- To unsubscribe, e-mail: opensuse-support+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse-support+owner(a)opensuse.org

4 5

[opensuse-support] DNS problems after upgrade 15.0 -> 15.1
by Sven Seeberg 01 Jul '19

01 Jul '19

Dear list, after upgrading from 15.0 to 15.1, DNS resolution does not work for most programs. It seems that NetworkManager is working correctly. The content of the /etc/resolv.conf is correctly updated with the nameservers in my LAN. The tools dig and nslookup also produce correct results. However, Firefox, Thunderbird, Nextcloud, ping, etc cannot resolve hostnames. Has anyone else experienced this? Is there a solution? Can it be related to systemd and its DNS resolution service? Thanks Sven *One other question: is there no Bugzilla anymore for Leap 42 and 15?

4 6