December 2022 - openSUSE Support - openSUSE Mailing Lists

getting systemd-status-mail to work
by Axel Braun 11 Jan '23

11 Jan '23

Hi, I'm trying to get the recently announced systemd-status-mail to work I'm using the following configuration: ---- # cat /etc/default/systemd-status-mail # ADDRESS is the mail account to which the status mails should be send ADDRESS=myaddress(a)gmx.de # Set HOSTNAME if the system does not set it or if you need to override # the system default #HOSTNAME=myhostname # Valid values for MAILER: "sendmail" or "mailx" MAILER="mailx -Sverbose -Ssmtp-use-starttls -Ssmtp-auth=login -Ssmtp-auth-user="myaddress(a)gmx.de" -Ssmtp-auth-password="TopSecret" " # RELAYHOST specifies the mail relay used by mailx if specified RELAYHOST=smtp.gmx.net ---- So far so good, when it comes to send the mail (journalctl) Dez 11 00:04:45 systemd[1]: transactional-update.service: Triggering OnFailure= dependencies. Dez 11 00:04:45 systemd[1]: transactional-update.service: Consumed 22.964s CPU time. Dez 11 00:04:45 systemd[1]: Starting Send status mail for transactional-update.service... Dez 11 00:04:45 systemd[1]: systemd-status-mail(a)transactional-update.service.service: Deactivated successfully. Dez 11 00:04:45 systemd[1]: Finished Send status mail for transactional-update.service. That looks good, but no mail did arrive. Nothing in the journal, nor anything in /var/log that looks useful. Any idea how to nail that problem? Thanks Axel

5 11

Two issues with XFCE DE
by Marco Calistri 26 Dec '22

26 Dec '22

Hello! As per subject: 1) bluetooth applet stop starting at login and now I get no any icon on my system tray. Tried to put blueman-tray or blueman-applet into start/session/auto-start without any success! 2) Cannot set a specific avatar per user into lightdm greeter, I feel that it could be improved providing a more flexible editing not just for the default setting but including a per user feature. Thanks! Season's Greetings! -- Marco Calistri Build: openSUSE Tumbleweed 20221224 Kernel: 6.1.0-1-default - XFCE: (4.18.0)

3 4

dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1
by mh＠mike.franken.de 26 Dec '22

26 Dec '22

Hi, after patching my Leap 15.4 machines with the latest hotfixes today, I get dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 when logging in via ssh. Any idea, what to do to solve this problem? TIA. Bye. Michael.

5 21

Leap 15.4: zypper ps shows "/usr/sbin/haveged (deleted)" after a reboot on vms with VirtIO disks
by Andreas Vetter 21 Dec '22

21 Dec '22

Hi, I have a strange problem with vms running Leap 15.4. After a reboot, I do "zypper ps" and it outputs: # zypper ps The following running processes use deleted files: PID | PPID | UID | User | Command | Service | Files ----+------+-----+------+-------------------+---------+------------------------------ 177 | 1 | 0 | root | haveged (deleted) | haveged | /lib64/ld-2.31.so | | | | | | /usr/lib64/libhavege.so.2.0.0 | | | | | | /lib64/libc-2.31.so | | | | | | /usr/sbin/haveged (deleted) You may wish to restart these processes. See 'man zypper' for information about the meaning of values in the above table. No core libraries or services have been updated since the last system boot. Reboot is probably not necessary. # This is only on virtual machines that use VirtIO (/dev/vda) as disk. It is not on real hardware (using /dev/sda). It is not on vms using SCSI (/dev/sda) as disk. Hypervisor for vms is Leap 15.4 KVM (qemu). (It also happens on a proxmox 7.2 Hypervisor, but lets stay at the Leap 15.4 KVM). All vms are updated and have the same repos. Software versions of haveged, lsof and zypper are the same. Bonus info: On the vms with SCSI disks haveged is restarted after boot: # journalctl _SYSTEMD_UNIT=haveged.service Dez 21 01:24:43 wpyc057 haveged[172]: haveged: command socket is listening at fd 3 Dez 21 01:24:49 wpyc057 haveged[172]: haveged: Stopping due to signal 15 Dez 21 01:24:49 wpyc057 haveged[172]: haveged starting up Dez 21 01:24:49 wpyc057 haveged[620]: haveged: command socket is listening at fd 3 # On vms with VirtIO disks, it is not restarted: # journalctl _SYSTEMD_UNIT=haveged.service Dez 21 01:23:43 localhost haveged[177]: haveged: command socket is listening at fd 3 # Any hint for debugging?

2 2

Firefox 107.0.1 (64 bit) JPEG rendering for some palette tints is bad
by Marco Calistri 19 Dec '22

19 Dec '22

Hello, As per the subject: After latest TW update, I noticed that some JPEG pictures are not displayed correctly in FireFox whereas the same are if using Google Chrome or by opening them with any Picture Viewers. It looks like the browser is not displaying correctly some tints, in particular I think the YELLOW, since for example the emoticons that we always know and see as YELLOW, get displayed in FF as RED! Anybody else is having this issue with FF?? Thanks and regards, -- Marco Calistri Build: openSUSE Tumbleweed 20221206 Kernel: 6.0.8-1-default - XFCE: (4.16.0)

1 1

question on microcode version verification for leap 15.3/4 on a x64 bit cpu PC
by Stakanov 18 Dec '22

18 Dec '22

I tried to run the command for TW on Leap but obviously ...that did not work. The command I did run was: /lib64/ld-linux-x86-64.so.2 --help One workaround would be to use life DVD with TW but .... if there is a command anybody is aware of in Leap, I am taker.

4 8

particular problem with a Leap 15.3 system: symbol error when starting kmail
by Stakanov 18 Dec '22

18 Dec '22

After an update Kontact does not start, however Akonadi the "usual suspect" this time is not the culprit at all and runs flawlessly. I have the suspect the user (which did a zypper up) might have some repo or library that induced a mix between 32 bit and 64 bit. But I am no way sure and honestly I do not know how I could debug the presence of the problem. To make it worse I have only the output in Italian, so please disregard if "non imperial outputs"are politically too incorrect. It is just what I have under hand, but should be quite understandable and is not used with any intent to set whatever "precedent" here. First: the system is Leap 15.3 and should be, procrastination tendencies of the user permitting, soon be updated to 15.4. But I am somewhat prudent to do this now with the error active, as this might then break as well the upgrade. What repos are active: # | Alias | Name | Enabled | GPG Check | Refresh | Type ---+-------------------------------------- +-------------------------------------+-----------+--------------- +---------------+------- 1 | https-download.opensuse.org-44cfee8e | openSUSE:Backports:SLE-15-SP3 | Sì | (r ) Sì | Sì | rpm-md 2 | https-download.opensuse.org-f3464cb7 | security | Sì | (r ) Sì | Sì | rpm-md 3 | opensuse-guide.org-repo | Libdvdcss Repository | Sì | (r ) Sì | Sì | rpm-md 4 | packman | packman | Sì | (r ) Sì | Sì | rpm-md 5 | repo-backports-debug-update | Update repository with updates fo- > | No | ---- | ---- | NONE 6 | repo-backports-update | Update repository of openSUSE Bac- > | Sì | (r ) Sì | Sì | rpm-md 7 | repo-debug | Repository di debug | Sì | (r ) Sì | Sì | rpm-md 8 | repo-debug-update | Repository degli aggiornamenti (D- > | Sì | (r ) Sì | Sì | rpm-md 9 | repo-non-oss | Repository Non-OSS | Sì | (r ) Sì | Sì | rpm-md 10 | repo-oss | Repository principale | Sì | (r ) Sì | Sì | rpm-md 11 | repo-sle-debug-update | Update repository with debuginfo - > | No | ---- | ---- | NONE 12 | repo-sle-update | Update repository with updates fr- > | Sì | (r ) Sì | Sì | rpm-md 13 | repo-source | Source Repository | Sì | (r ) Sì | Sì | rpm-md 14 | repo-source-non-oss | Source Repository (Non-OSS) | Sì | (r ) Sì | Sì | rpm-md 15 | repo-update | Repository principale degli aggio- > | Sì | (r ) Sì | Sì | rpm-md 16 | repo-update-non-oss | Repository degli aggiornamenti (N- > | Sì | (r ) Sì | Sì | rpm-md What is the error message when the user starts kmail: kmail: symbol lookup error: /usr/lib64/libKF5ContactEditor.so.5: undefined symbol: _ZN9KContacts9Addressee16staticMetaObjectE I came about a reference of a case with Leap in 2018 I think, where the user at the end discovered that he had torn inadvertently a library 32 bit in the 64 bit system. But I did not find a reference how to find which. When I tried and told the user to "zypper in libKF5ContactEditor.so.5 the following endless conflict list produced (unfortunately in Italian). Please scroll down to solution "2" below to come to the point. Problema: libKF5ContactEditor5-20.04.2-bp153.2.2.1.i586 da installare presenta un'architettura inferiore Soluzione 1: Verranno eseguite le azioni indicate: installa libKF5ContactEditor5-20.04.2-bp153.2.2.1.i586 nonostante l'architettura inferiore modifica di architettura di libKF5ContactEditor5-20.04.2-bp153.2.2.1.x86_64 in libKF5ContactEditor5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5AkonadiContact5-20.04.2-bp153.2.2.1.x86_64 in libKF5AkonadiContact5-20.04.2-bp153.2.2.1.i586 installa akonadi-contact-20.04.2-bp153.2.2.1.i586 nonostante l'architettura inferiore installa libKF5AkonadiCore5-20.04.2-bp153.4.2.1.i586 nonostante l'architettura inferiore installa libKF5AkonadiWidgets5-20.04.2-bp153.4.2.1.i586 nonostante l'architettura inferiore installa libKF5AkonadiPrivate5-20.04.2-bp153.4.2.1.i586 nonostante l'architettura inferiore installa libKF5Mime5-20.04.2-bp153.2.2.1.i586 nonostante l'architettura inferiore modifica di architettura di akonadi-contact-20.04.2-bp153.2.2.1.x86_64 in akonadi-contact-20.04.2-bp153.2.2.1.i586 disinstallazione di libKF5IncidenceEditor5-20.04.2-bp153.2.2.1.x86_64 modifica di architettura di libKF5LibkdepimAkonadi5-20.04.2- bp153.2.2.1.x86_64 in libKF5LibkdepimAkonadi5-20.04.2-bp153.2.2.1.i586 disinstallazione di libKF5MailCommon5-20.04.2-bp153.2.2.1.x86_64 modifica di architettura di libKF5PimCommonAkonadi5-20.04.2- bp153.2.2.1.x86_64 in libKF5PimCommonAkonadi5-20.04.2-bp153.2.2.1.i586 disinstallazione di messagelib-20.04.2-bp153.2.2.1.x86_64 disinstallazione di libdigikamcore7-7.1.0-bp153.1.23.x86_64 disinstallazione di libKF5AkonadiCalendar5-20.04.2-bp153.2.2.1.x86_64 disinstallazione di korganizer-20.04.2-bp153.2.2.1.x86_64 disinstallazione di kmail-20.04.2-bp153.3.2.1.x86_64 disinstallazione di kdepim-runtime-20.04.2-bp153.2.2.1.x86_64 modifica di architettura di kdepim-apps-libs-20.04.2-bp153.2.2.1.x86_64 in kdepim-apps-libs-20.04.2-bp153.2.2.1.i586 disinstallazione di kdepim-addons-20.04.2-bp153.2.2.1.x86_64 disinstallazione di kaddressbook-20.04.2-bp153.2.2.1.x86_64 modifica di architettura di akonadi-plugin-contacts-20.04.2- bp153.2.2.1.x86_64 in akonadi-plugin-contacts-20.04.2-bp153.2.2.1.i586 disinstallazione di libKF5EventViews5-20.04.2-bp153.2.2.1.x86_64 disinstallazione di akonadi-import-wizard-20.04.2-bp153.2.2.1.x86_64 modifica di architettura di knotes-20.04.2-bp153.2.2.1.x86_64 in knotes-20.04.2-bp153.2.2.1.i586 disinstallazione di akregator-20.04.2-bp153.2.23.x86_64 disinstallazione di digikam-plugins-7.1.0-bp153.1.23.x86_64 modifica di architettura di libkdepim-20.04.2-bp153.2.2.1.x86_64 in libkdepim-20.04.2-bp153.2.2.1.i586 disinstallazione di libKPimImportWizard5-20.04.2-bp153.2.2.1.x86_64 disinstallazione di mbox-importer-20.04.2-bp153.1.25.x86_64 disinstallazione di pim-data-exporter-20.04.2-bp153.1.25.x86_64 disinstallazione di showfoto-7.1.0-bp153.1.23.x86_64 disinstallazione di libKF5CalendarSupport5-20.04.2-bp153.2.2.1.x86_64 disinstallazione di kontact-20.04.2-bp153.2.2.1.x86_64 disinstallazione di kdepim-addons-lang-20.04.2-bp153.2.2.1.noarch disinstallazione di akonadi-calendar-tools-20.04.2-bp153.2.2.1.x86_64 disinstallazione di mbox-importer-lang-20.04.2-bp153.1.25.noarch disinstallazione di pim-data-exporter-lang-20.04.2-bp153.1.25.noarch disinstallazione di akregator-lang-20.04.2-bp153.2.23.noarch modifica di architettura di libKF5AkonadiCore5-20.04.2-bp153.4.2.1.x86_64 in libKF5AkonadiCore5-20.04.2-bp153.4.2.1.i586 modifica di architettura di libKF5AkonadiWidgets5-20.04.2-bp153.4.2.1.x86_64 in libKF5AkonadiWidgets5-20.04.2-bp153.4.2.1.i586 modifica di architettura di libKF5Mime5-20.04.2-bp153.2.2.1.x86_64 in libKF5Mime5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5AkonadiMime5-20.04.2-bp153.2.2.1.x86_64 in libKF5AkonadiMime5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5AkonadiSearch-20.04.2-bp153.2.2.1.x86_64 in libKF5AkonadiSearch-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5AkonadiXml5-20.04.2-bp153.4.2.1.x86_64 in libKF5AkonadiXml5-20.04.2-bp153.4.2.1.i586 disinstallazione di libKF5AlarmCalendar5-20.04.2-bp153.2.2.1.x86_64 modifica di architettura di libKF5MailImporterAkonadi5-20.04.2- bp153.2.2.1.x86_64 in libKF5MailImporterAkonadi5-20.04.2-bp153.2.2.1.i586 disinstallazione di libKF5MailTransportAkonadi5-20.04.2-bp153.2.2.1.x86_64 modifica di architettura di libKF5AkonadiAgentBase5-20.04.2- bp153.4.2.1.x86_64 in libKF5AkonadiAgentBase5-20.04.2-bp153.4.2.1.i586 disinstallazione di kmymoney-5.1.1-bp153.2.2.1.x86_64 disinstallazione di kmailtransport-20.04.2-bp153.2.2.1.x86_64 disinstallazione di kmail-account-wizard-20.04.2-bp153.2.2.1.x86_64 modifica di architettura di akonadi-server-20.04.2-bp153.4.2.1.x86_64 in akonadi-server-20.04.2-bp153.4.2.1.i586 modifica di architettura di akonadi-search-20.04.2-bp153.2.2.1.x86_64 in akonadi-search-20.04.2-bp153.2.2.1.i586 modifica di architettura di akonadi-plugin-mime-20.04.2-bp153.2.2.1.x86_64 in akonadi-plugin-mime-20.04.2-bp153.2.2.1.i586 disinstallazione di akonadi-plugin-kalarmcal-20.04.2-bp153.2.2.1.x86_64 disinstallazione di akonadi-plugin-calendar-20.04.2-bp153.2.2.1.x86_64 modifica di architettura di libKF5AkonadiPrivate5-20.04.2-bp153.4.2.1.x86_64 in libKF5AkonadiPrivate5-20.04.2-bp153.4.2.1.i586 modifica di architettura di libKPimItinerary5-20.04.2-bp153.2.2.1.x86_64 in libKPimItinerary5-20.04.2-bp153.2.2.1.i586 disinstallazione di libksieve-20.04.2-bp153.2.2.1.x86_64 modifica di architettura di libKF5Mbox5-20.04.2-bp153.2.2.1.x86_64 in libKF5Mbox5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5IMAP5-20.04.2-bp153.2.2.1.x86_64 in libKF5IMAP5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5AkonadiNotes5-20.04.2-bp153.2.2.1.x86_64 in libKF5AkonadiNotes5-20.04.2-bp153.2.2.1.i586 modifica di architettura di kleopatra-20.04.2-bp153.2.2.1.x86_64 in kleopatra-20.04.2-bp153.2.2.1.i586 disinstallazione di kmymoney-lang-5.1.1-bp153.2.2.1.noarch modifica di architettura di libKF5MailImporter5-20.04.2-bp153.2.2.1.x86_64 in libKF5MailImporter5-20.04.2-bp153.2.2.1.i586 downgrade di libKF5CalendarCore5-17.12.3-bp150.2.2.x86_64 a libKF5CalendarCore5-5.76.0-bp153.2.2.1.i586 modifica di architettura di libKF5CalendarCore5-17.12.3-bp150.2.2.x86_64 in libKF5CalendarCore5-5.76.0-bp153.2.2.1.i586 modifica di architettura di libKF5IdentityManagement5-20.04.2- bp153.2.2.1.x86_64 in libKF5IdentityManagement5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5PimCommon5-20.04.2-bp153.2.2.1.x86_64 in libKF5PimCommon5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5PimTextEdit5-20.04.2-bp153.2.2.1.x86_64 in libKF5PimTextEdit5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5CalendarUtils5-20.04.2-bp153.2.2.1.x86_64 in libKF5CalendarUtils5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5Tnef5-20.04.2-bp153.2.2.1.x86_64 in libKF5Tnef5-20.04.2-bp153.2.2.1.i586 disinstallazione di libKPimGAPICalendar5-20.04.2-bp153.3.2.1.x86_64 disinstallazione di libKPimGAPITasks5-20.04.2-bp153.3.2.1.x86_64 modifica di architettura di libKF5Ldap5-20.04.2-bp153.2.2.1.x86_64 in libKF5Ldap5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5Gravatar5-20.04.2-bp153.2.2.1.x86_64 in libKF5Gravatar5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5Libkleo5-20.04.2-bp153.2.2.1.x86_64 in libKF5Libkleo5-20.04.2-bp153.2.2.1.i586 modifica di architettura di kldap-20.04.2-bp153.2.2.1.x86_64 in kldap-20.04.2-bp153.2.2.1.i586 modifica di architettura di kcalutils-20.04.2-bp153.2.2.1.x86_64 in kcalutils-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5GrantleeTheme5-20.04.2-bp153.2.2.1.x86_64 in libKF5GrantleeTheme5-20.04.2-bp153.2.2.1.i586 modifica di architettura di libKF5KontactInterface5-20.04.2- bp153.2.2.1.x86_64 in libKF5KontactInterface5-20.04.2-bp153.2.2.1.i586 Soluzione 2: non chiedere di installare un risolubile che fornisce libKF5ContactEditor.so.5 Which is in plain English: either install all of the above with dependency hell or: do not ask to install a resolution that delivers libKF5ContactEditor.so.5 For what I understand at that point that one of the apps or whatever else program / libraries installed has a requires or? recommend that point to the need of libKF5ContactEditor.so.5, hence Kmail loads that module or whatever when starting up and runs into the conflict and crashes/aborts. Installation of the library is obviously not useful in this 64 bit system given the awful impact that would have. Is there a way to find out which file I have to get rid of in order to neutralize the problem with kmail? I will be thankful for whatever suggestion. P.S. I forgot, below the output when akonadi is started on the CLI, all seems perfect. hermes@azzurro:~> akonadictl status Akonadi Control: running Akonadi Server: running Akonadi Server Search Support: available (Remote Search, Akonadi Search Plugin) Available Agent Types: akonadi_akonotes_resource, akonadi_archivemail_agent, akonadi_birthdays_resource, akonadi_contacts_resource, akonadi_davgroupware_resource, akonadi_ews_resource, akonadi_ewsmta_resource, akonadi_followupreminder_agent, akonadi_googlecalendar_resource, akonadi_googlecontacts_resource, akonadi_ical_resource, akonadi_icaldir_resource, akonadi_imap_resource, akonadi_indexing_agent, akonadi_kalarm_dir_resource, akonadi_kalarm_resource, akonadi_knut_resource, akonadi_kolab_resource, akonadi_maildir_resource, akonadi_maildispatcher_agent, akonadi_mailfilter_agent, akonadi_mbox_resource, akonadi_migration_agent, akonadi_mixedmaildir_resource, akonadi_newmailnotifier_agent, akonadi_notes_agent, akonadi_notes_resource, akonadi_openxchange_resource, akonadi_pop3_resource, akonadi_sendlater_agent, akonadi_tomboynotes_resource, akonadi_unifiedmailbox_agent, akonadi_vcard_resource, akonadi_vcarddir_resource

7 21

FireFox 102.6.0 ESR - pleasant surprise. ty.
by cagsm 15 Dec '22

15 Dec '22

support, pleasant surprise, that FireFox 102.6.2 ESR has been released very quickly to leap 15.4 users. ty.

1 0

problems with meld
by Hartmut Rosch 09 Dec '22

09 Dec '22

Hi, let me answer: it is from tumbleweed with rpm -qi: Signature : RSA/SHA256, Do 08 Sep 2022 22:19:36 CEST, Key ID b88b2fd43dbdc284 Source RPM : meld-3.22.0-1.1.src.rpm Build Date : Do 08 Sep 2022 22:19:05 CEST Build Host : cloud122 checkingrpm -ql meld|gc python it only shows "/usr/lib/python3.10/site-packages/meld/*" and python3 --version says "Python 3.10.8" I am really puzzled regards Hartmut Rosch Delmenhorst

3 2

Re: Problems with meld
by Dominique Leuenberger / DimStar 09 Dec '22

09 Dec '22

Hi Hartmut, On Fri, 2022-12-09 at 12:00 +0100, Hartmut Rosch wrote: > Hello to all, > > I don't if this kist is the right one This list is about development of Tumbleweed and the directions it takes. Your query rather belongs to the support list (I cross-posted this reply to support; please only reply to the support list, not factory for this topic) > > if I to run meld, i.e, Is this the meld version from Tumbleweed? ("rpm -qi meld" please) > meld (from the command line, i receive the following) > Traceback (most recent call last): > File "/usr/bin/meld", line 96, in <module> > import meld.conf # noqa: E402 > ModuleNotFoundError: No module named 'meld' That sounds very strange, and somewhat implies that the meld verison you have installed is either defective or not compatible with the default python interpreter on your system. Please check the outputs of: rpm -qV meld if that gives no putput, check "rpm -ql meld" and take note of the lines containing python.*/site-packages. Then verify "python3 --version"; does the version number found in the output earlier match the one from python3 --version (only the first two are relevant, so in case it gives 3.10.8, only 3.10 is relevant) > then running (downloaded from meldmerge.org/) > > meld-3.22.0/bin/meld > > I got two windows > one with "meld" in the titlebar and nothing else > and a second one with "meld" also in the titlebar and additionally saying > "Meld requires Gtk+3.20 or higher" That's something for upstream to answer. Tumbleweed ships meld as a package which is integrated into the sytsem. Cheers, Dominique

1 0