- openSUSE Support

Re: Recovery of damaged instalation- upgrade from USB not working>resolvable.rb crash
by Axel Braun 04 Feb '22

04 Feb '22

Hello Peter, Am Freitag, 4. Februar 2022, 15:24:41 CET schrieb Peter Fodrek,ml.-súkromne: > Dear SUSE experts, > > I would like to recover damaged Tubleweed instalation with som > Factory repos active via using install bootable DVD. > > > 1.I am able to mount all partions of the system use files but chroot do > sometimes crashes as well as zypper and rpm -i crashes in every attempt > > > 2. I am to try to recover system via use of update from Tumbleweed > DVSD image. It works ok. Sometimes there is "grub2-editenv missing" > even it is present as a symlink form /mnt/bin at correct path. But > grub2 settings are reading correctly That would have been my proposal as well, use the 'update' option of installation media. Last time (in December) I did that (on a Leap system) it worked flawless > 3. Upgrade crashes on > /mounts/im001/usr/share/YaST2/lib/y2pacakger/resolvable.rb !#@ in > 'method missing' > > .... > > @name="openSUSE", @source=-1, @version="20210524-0" > > > even if install DVD is version 20220201. That looks like the installation repository of the original installation. Question is what steps did you takeup to that point? > Is there any revomendation, how to enable system recovery, plese? > > Crash was made by copying some system libraries to other system.- > Maybe there was used move instlead of copy of the files Could you not recover from a previous snapshot? Actually, this is more a question for our support list. Pls continue on that list (in cc)! Thanks Axel

1 0

Bluez not working on latest TW
by Marco Calistri 03 Feb '22

03 Feb '22

"The name org.bluez.obex was not provided by any service file" How to resolve this? Thanks and regards! -- Marco Calistri Build: openSUSE Tumbleweed 20220130 Kernel:5.16.2-1-default Desktop: XFCE (4.16.0)

1 0

Re: Samba update today failed to restart if printer lines in smb.conf
by Carlos E. R. 02 Feb '22

02 Feb '22

On 2022-02-02 04:45, Larry Len Rainey wrote: > Samba broke in todays 15.3 update - is it apparmor or bug? You do not write apparmor info to see if it can be an apparmor issue. Try "aa-logprof". > > LLR1:~ # systemctl status smb > > ● smb.service - Samba SMB Daemon > Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; > vendor prese> > Active: failed (Result: exit-code) since Tue 2022-02-01 21:27:13 > CST; 8s a> > Docs: man:smbd(8) > man:samba(7) > man:smb.conf(5) > Process: 9455 > ExecStartPre=/usr/share/samba/update-apparmor-samba-profile (> > Process: 9460 ExecStart=/usr/sbin/smbd --foreground --no-process-group $SMB> > Main PID: 9460 (code=exited, status=1/FAILURE) > Status: "daemon failed to start: Samba failed to init printing subsystem" > Error: 13 (Permission denied) > > Feb 01 21:27:13 LLR1 systemd[1]: Starting Samba SMB Daemon... > Feb 01 21:27:13 LLR1 smbd[9460]: [2022/02/01 21:27:13.529676, 0] ../../source3> > Feb 01 21:27:13 LLR1 smbd[9460]: smbd version 4.15.4-git.324.8332acf1a6315030> > Feb 01 21:27:13 LLR1 smbd[9460]: Copyright Andrew Tridgell and the Samba Team> > Feb 01 21:27:13 LLR1 systemd[1]: Started Samba SMB Daemon. > Feb 01 21:27:13 LLR1 smbd[9460]: [2022/02/01 21:27:13.548557, 0] ../../lib/uti> > Feb 01 21:27:13 LLR1 smbd[9460]: exit_daemon: daemon failed to start: Samba f> > Feb 01 21:27:13 LLR1 systemd[1]: smb.service: Main process exited, code=exited,> > Feb 01 21:27:13 LLR1 systemd[1]: smb.service: Failed with result 'exit-code'. > > I had to delete these lines to make it work. > [printers] > comment = All Printers > path = /var/tmp > printable = Yes > create mask = 0600 > browseable = No > printable = yes > > [print$] > comment = Printer Drivers > path = /var/lib/samba/drivers > write list = @ntadmin root > force group = ntadmin > create mask = 0664 > directory mask = 0775 > > LLR1:/etc/samba # systemctl status smb > ● smb.service - Samba SMB Daemon > Loaded: loaded (/usr/lib/systemd/system/smb.service; enabled; > vendor prese> > Active: active (running) since Tue 2022-02-01 21:33:13 CST; 10min ago > Docs: man:smbd(8) > man:samba(7) > man:smb.conf(5) > Process: 10353 > ExecStartPre=/usr/share/samba/update-apparmor-samba-profile > > Main PID: 10365 (smbd) > Status: "smbd: ready to serve connections..." > Tasks: 13 (limit: 4915) > CGroup: /system.slice/smb.service > ├─10365 /usr/sbin/smbd --foreground --no-process-group > ├─10367 /usr/sbin/smbd --foreground --no-process-group > ├─10368 /usr/sbin/smbd --foreground --no-process-group > ├─10369 /usr/lib64/samba/samba-bgqd --ready-signal-fd=47 > --parent-> > ├─10384 /usr/sbin/smbd --foreground --no-process-group > ├─11235 /usr/sbin/smbd --foreground --no-process-group > ├─12174 /usr/sbin/smbd --foreground --no-process-group > ├─12175 /usr/sbin/smbd --foreground --no-process-group > ├─12176 /usr/sbin/smbd --foreground --no-process-group > ├─12177 /usr/sbin/smbd --foreground --no-process-group > ├─12178 /usr/sbin/smbd --foreground --no-process-group > ├─12179 /usr/sbin/smbd --foreground --no-process-group > └─12181 /usr/sbin/smbd --foreground --no-process-group > > Feb 01 21:33:12 LLR1 systemd[1]: Starting Samba SMB Daemon... > Feb 01 21:33:12 LLR1 update-apparmor-samba-profile[10353]: Reloading updated Ap> > Feb 01 21:33:13 LLR1 smbd[10365]: [2022/02/01 21:33:13.129861, 0] ../../source> > Feb 01 21:33:13 LLR1 smbd[10365]: smbd version 4.15.4-git.324.8332acf1a631503> > Feb 01 21:33:13 LLR1 smbd[10365]: Copyright Andrew Tridgell and the Samba Tea> > Feb 01 21:33:13 LLR1 systemd[1]: Started Samba SMB Daemon. > Feb 01 21:33:13 LLR1 systemd[1]: smb.service: Got notification message from PID> > Feb 01 21:43:16 LLR1 smbd[12180]: [2022/02/01 21:43:16.567854, 0] ../../source> > Feb 01 21:43:16 LLR1 smbd[12180]: Invalid SMB packet: first request: 0x0001 > -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)

4 7

grub fails to rescue prompt: '/boot/grub2/x86_64-efi' not found.
by Eric 30 Jan '22

30 Jan '22

In short: I added btrfs subvolumes (including @/boot/grub2/x86_64-efi ) to try to get snapshot booting in the grub2 menu to work, and after running an update grub fails to the recovery console and reports error: ../../grub-core/fs/btrfs.c:1997:file '/boot/grub2/x86_64-efi' not found. error: ../../grub-core/fs/btrfs.c:1997:file '/boot/grub2/x86_64-efi/normal.mod' not found. From the grub rescue prompt I can ls @/boot/grub2/x86_64-efi and it successfully reads that folder. Why can it see this path with the @ and not without the @ and how can I fix this? --------------------- Longer version My openSUSE system only had a @ subvolume for / and a @home subvolume (which was not a child of the @ subvolume, but a sibling, FWIW). To try to get the grub menu snapshots working, I created subvolumes for /var /usr/local /srv /root and /boot/grub2/x86_64-efi, copying over the contents of the directories they would replace and then moving the subvolumes into the place of the old directories (using single user mode for a couple of these such as /var), and added /etc/fstab entries for them. I did a few at a time, rebooting in between to make sure things were working properly. I added SUSE_BTRFS_SNAPSHOT_BOOTING=true into /etc/default/grub and made sure grub2-snapper-plugin was installed. The system booted fine after all of these changes but I hadn't refreshed grub. At this point I ran a full zypper update, since I was overdue, figuring it would take care of the grub refresh. And I guess it did, but now grub is broken. I've booted with a usb LIVE image and set up a chroot to run grub2-mkconfig and grub2-install to try to fix it (including once with SUSE_BTRFS_SNAPSHOT_BOOTING disabled again) but I still get the same error.

2 4

Tried and tried and tried, can't log in
by mark neidorff 27 Jan '22

27 Jan '22

2 1

openSUSE Leap 15.3 - here: install scdl-2.6.1-9.1 package
by michael.kasimir＠gmx.de 27 Jan '22

27 Jan '22

Hello all, actually I cannot handle sucessfully a specific downstream with the installed version: rpm -qi scdl https://download.opensuse.org/repositories/utilities/openSUSE_Factory/noarc… scdl-2.6.1-9.1.noarch.rpm[1] installation sequence supplies: $ sudo zypper in scdl-2.6.1-9.1.noarch.rpm Loading repository data... Reading installed packages... Resolving package dependencies... Problem: nothing provides 'python(abi) = 3.8' needed by the to be installed scdl-2.6.1-9.1.noarch Solution 1: do not install scdl-2.6.1-9.1.noarch Solution 2: break scdl-2.6.1-9.1.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): c installed python versions are: $ ls -al /usr/bin/pytho* lrwxrwxrwx 1 root root 9 Oct 12 08:19 /usr/bin/python -> python2.7 lrwxrwxrwx 1 root root 9 Oct 12 08:19 /usr/bin/python2 -> python2.7 -rwxr-xr-x 1 root root 6296 Oct 12 08:19 /usr/bin/python2.7 lrwxrwxrwx 1 root root 9 Jan 4 15:04 /usr/bin/python3 -> python3.6 lrwxrwxrwx 1 root root 16 Jan 4 15:04 /usr/bin/python3-config -> python3.6-config -rwxr-xr-x 2 root root 10472 Jan 4 15:04 /usr/bin/python3.6 lrwxrwxrwx 1 root root 17 Jan 4 15:04 /usr/bin/python3.6-config -> python3.6m-config -rwxr-xr-x 2 root root 10472 Jan 4 15:04 /usr/bin/python3.6m -rwxr-xr-x 1 root root 3440 Jan 4 15:04 /usr/bin/python3.6m-config -rwxr-xr-x 1 root root 6296 Aug 20 11:50 /usr/bin/python3.9 lrwxrwxrwx 1 root root 45 Jun 9 2020 /usr/bin/pythontex -> ../share/texmf/scripts/ pythontex/pythontex.py What can I do to solve, due to the fact I had installed python 3.9? Are there specific internals in python 3.8 ?? Many greetings Michael Be Free, Be Linux -------- [1] https://download.opensuse.org/repositories/utilities/openSUSE_Factory/noarc… scdl-2.6.1-9.1.noarch.rpm

3 2

Postfix gives unsupported dictionary type: btree on Leap 15.3
by Freek de Kruijf 18 Jan '22

18 Jan '22

I have a recent installed Leap 15.3 system on a Raspberry Pi 4B and I try to configure it as an email server. The access port 25 should offer STARTTLS, which has been configured as well. This requires also the parameter smtpd_tls_session_cache_database = btree:/ var/lib/postfix/smtpd_tls_session_cache However when I access using STARTTLS to port 25 I get the warning: postfix/tlsmgr[13932]: warning: btree:/var/lib/postfix/smtpd_tls_session_cache is unavailable. unsupported dictionary type: btree I do see the file /var/lib/postfix/smtpd_tls_session_cache.db Should I file a bug report? -- fr.gr. member openSUSE Freek de Kruijf

2 1

KMail Leap 15.3 - unread mails
by Axel Braun 06 Jan '22

06 Jan '22

Hi, I have one PC that still runs Leap, and since the update to Leap 15.3 the number of unread mails as shown in the Kmail overview is some random number that does not match the real number of unread mails (which is usually Zero): [1] Selecting 'Mark read' from the context menu does not work, neither does akonadictl fsck/ vacuum fix the problem. DB backend is Postgres. Any idea what else to try? Cheers Axel -------- [1] Bild1

3 3

error message in journal about XMLHttpRequest.<anonymous> (https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js:1:135369) - spyware/tracker/feature?
by Stakanov 06 Jan '22

06 Jan '22

Entry goes as: (sudo journalctl -r) ---snip---- gen 02 08:04:32 silversurfer plasmashell[2540]: requesting unexisting screen -1 gen 02 08:04:32 silversurfer plasmashell[2540]: requesting unexisting screen -1 gen 02 08:04:29 silversurfer plasmashell[2540]: js: worker received a message {"action":"modify","symbols": ["0656.HK","CTJ1.F","C2L.F","CUBB.F","NIO","3988.HK"],"model": {"objectName":"","count":0,"engine":""}} gen 02 08:04:29 silversurfer plasmashell[2540]: js: worker received a message {"action":"modify","symbols": ["9868.HK","688567.SS","DASTY","VOW.DE","BKTPF","2357.HK","601766.SS","1766.HK","000270.KS","HYU.F","0855.HK","CUBB.SG","000962.SZ","600549.SS","0656.HK","0981.HK","GAZ.DE","8TI.DE","RIO1.DE","DAI.DE","DTG.DE","UFGD.F> gen 02 08:04:27 silversurfer plasmashell[2540]: Entry is not valid "ktp- contactlist.desktop" QSharedPointer(0x55a2e60d1980) gen 02 08:04:27 silversurfer plasmashell[2540]: Entry is not valid "kontact.desktop" QSharedPointer(0x55a2e6d09e30) gen 02 08:04:27 silversurfer plasmashell[2540]: Entry is not valid "applications:writer.desktop" QSharedPointer(0x55a2e7b15500) gen 02 08:04:27 silversurfer plasmashell[2540]: requesting unexisting screen -1 gen 02 08:04:27 silversurfer plasmashell[2540]: requesting unexisting screen -1 gen 02 08:04:27 silversurfer plasmashell[2540]: js: worker received a message {"action":"modify","symbols": ["1992.HK","2196.HK","2362.HK","300750.SZ","600196.SS","6BT.F","AMD","L87A.F","L87A.MU","LI","LKCO","NIO","XPEV"],"model": {"objectName":"","count":0,"engine":""}} gen 02 08:04:27 silversurfer plasmashell[2540]: requesting unexisting screen -1 gen 02 08:04:27 silversurfer plasmashell[2540]: requesting unexisting screen -1 gen 02 08:04:27 silversurfer plasmashell[2540]: requesting unexisting screen -1 gen 02 08:04:27 silversurfer plasmashell[2540]: requesting unexisting screen -1 gen 02 08:04:22 silversurfer plasmashell[2540]: js: Uncaught (in promise) TypeError: Failed to fetch gen 02 08:04:17 silversurfer plasmashell[2540]: js: ERROR in messagingWithoutDetection: RequestError: Server request error: 0 () at XMLHttpRequest.<anonymous> (https://cdn.privacy-mgmt.com/ wrapperMessagingWithoutDetection.js:1:135369) gen 02 08:04:17 silversurfer plasmashell[2540]: trying to show an empty dialog --- snap ---- I get this in my journal and do only understand that it is apparently connected to plasma. Research on this site gives nothing but a "high volume of traffic in Germany" (this site is very popular). The thing is registered in Panama and apparently no owners known. There is one blacklist entry in MyWOT but it is not clear what it refers to. https://www.urlvoid.com/scan/privacy-mgmt.com/ So if anybody knows what software causes this and why it tries to phone home am taker.

2 3

xscreensaver: password initialization failed
by Peter Münster 03 Jan '22

03 Jan '22

Hello, I cannot unlock the screen with the latest version of xscreensaver. (xscreensaver-6.02-lp153.88.2.x86_64) I get the message "password initialization failed" in the unlock-window and when using the "--verbose" flag, I get this message on the terminal: pwnam: couldn't get password of "peter" There is no such problem with version 5.44-5.3.1. How could I get the unlocking working please? TIA for any hints, -- Peter

1 1