October 2022 - openSUSE Support - openSUSE Mailing Lists

how did I screw up grub? and how do I fix it?
by David T-G 16 Nov '22

16 Nov '22

Hi, all -- I have a system with a 128G SSD /dev/sda that is my boot, swap, and data drive. It is sliced into partitions with a GPT layout and it has been working fabulously for over a year. My long-term plans are to add a 256G SSD, set up either the disk or the slices as [a] mirror[s], migrate from small to large, and then replace the small with another large that gets added to the mirror[s]. I've had /dev/sde in place for a while across a couple of reboots and have been waiting for the right time to copy the XFS content across. I also have a RAID-0 stripe of RAID-5 slices across 10T disks, and the other day I bought another to add to grow the slices. I shut down, installed it, and thought to myself it would be a great time to do the xfs dump->restore thing to get ready to swing. Should be simple, right? Somehow I have tanked grub2. If the box gets anywhere at all, it only gets as far as "GRUB2 loading" (or whatever it says; I can't access remotely when it's dead and so I can't mouse the message) and then hangs. Mostly it doesn't even get that far. I have unplugged everything except the RAID-5 big disks, even going so far as to rip out the new 256G, to no avail. I can boot into a Leap 15.2 rescue system on a thumb drive and even mount /dev/sda2 manually, but when I then try to reinstall grub2 it complains that it can't work on a GPT system. But it was working before! Exactly once I was able to use the boot menu in my BIOS to tell it to boot from SATA0 (aka /dev/sda), although it threw another error much further down the line and wanted a root password for a shell. I've never had a separate /boot or /efi partition and I've switched over to GPT long ago; this system was built with GPT tables. But it somehow used to boot ... How do I repair grub2 to get back to booting on sda first, just so that we can be back where we were and I can start adding the slices? I'll tackle migration from sda (raw) to sde (mirrors) once it's up and running again; for now I just want to get back to where I was. TIA & HAND :-D -- David T-G See http://justpickone.org/davidtg/email/ See http://justpickone.org/davidtg/tofu.txt

8 62

/usr/sbin/vpnc: unknown host `xxxxxxxxxx.myfritz.net:42986'
by Axel Braun 31 Oct '22

31 Oct '22

Hi, I'm trying to establish a VPN connection to my home router (a Fritz Box). VPN access is set up and working. In my TW system (KDE) I have set-up an according VPN connection, but that fails to conneect: Okt 27 16:12:05 X1E NetworkManager[1067]: <info> [1666879925.8098] vpn[0x55733a8c2170,57c0c03a-b954-4082-b18f-e4a596ab8ab5,"FritzBox@home"]: starting vpnc Okt 27 16:12:05 X1E NetworkManager[1067]: <info> [1666879925.8102] audit: op="connection-activate" uuid="57c0c03a-b954-4082-b18f-e4a596ab8ab5" name="FritzBox@home" pid=2048 uid=1001 result="success" Okt 27 16:12:10 X1E NetworkManager[19073]: /usr/sbin/vpnc: unknown host `xxxxxxxxxxxxxx.myfritz.net:42986' Okt 27 16:12:10 X1E NetworkManager[1067]: <warn> [1666879930.8875] vpn[0x55733a8c2170,57c0c03a-b954-4082-b18f-e4a596ab8ab5,"FritzBox@home"]: dbus: failure: connect-failed (1) Okt 27 16:12:10 X1E NetworkManager[1067]: <warn> [1666879930.8876] vpn[0x55733a8c2170,57c0c03a-b954-4082-b18f-e4a596ab8ab5,"FritzBox@home"]: dbus: failure: connect-failed (1) 'Unknown host' is clearly a wrong message, as I can resolve the host and it has an IPv4 address (as mentioned in one post I found with regard to this issue) My feeling is that vpnc is invoked wrongly. Are there additional steps required to set it up? Just asking before creating a bug with KDE team.... Thanks Axel

2 2

Mozilla Firefox 106.0.1 (64 bit)
by Marco Calistri 25 Oct '22

25 Oct '22

Hi, I noticed an issue with this browser: e-commerce chat windows (most likely javascript based) are not opening. Site: https://shopee.com.br/ I need to use Google Chrome to be able to do it. Thanks and regards, -- Marco Calistri Build: openSUSE Tumbleweed 20221023 Kernel: 6.0.2-1-default - XFCE: (4.16.0)

3 5

Syntax for locking a patch
by Bjoern Voigt 24 Oct '22

24 Oct '22

On openSUSE 15.4 I want to ignore the patch patch:openSUSE-SLE-15.4-2022-2969-1.noarch, but in general I want to install all available patches. But what it the correct syntax for this? I tried several variants, but still YaST wants to install patch:openSUSE-SLE-15.4-2022-2969-1.noarch. # zypper help addlock addlock (al) [OPTIONS] <LOCKSPEC>... Add a package lock. LOCKSPEC is formed by '[KIND:]NAME[ OP EDITION]', where NAME may also be a glob pattern using * and ? wildcard characters. Non-package types may to have their KIND: string prepended (e.g. 'patch:foo') or use the commands --type option. The basic form will lock all editions of the matching items. You can optionally restrict the lock to match a specific edition or edition range using =, <, <=, >, >= or != followed an EDITION. Command options: -t, --type <TYPE> Type of package (package, patch, pattern, product). -r, --repo <ALIAS|#|URI> Restrict the lock to the specified repository. -m, --comment <STRING> Reason for specific lock. Default: comments string # zypper addlock -t patch openSUSE-SLE-15.4-2022-2969-1.noarch Specified lock has been successfully added. # zypper addlock -t patch openSUSE-SLE-15.4-2022-2969-1 Specified lock has been successfully added. # zypper addlock -t patch openSUSE-SLE-15.4-2022-2969-1\* Specified lock has been successfully added. # zypper addlock -t patch patch:openSUSE-SLE-15.4-2022-2969-1.noarch # zypper addlock -t patch patch:openSUSE-SLE-15.4-2022-2969-1 # zypper addlock -t patch patch:openSUSE-SLE-15.4-2022-2969-1\* # zypper patch --with-optional Loading repository data... Reading installed packages... Resolving package dependencies... Problem: the to be installed patch:openSUSE-SLE-15.4-2022-2969-1.noarch conflicts with 'libswscale5_9.x86_64 < 4.4-150400.3.2.1' provided by the installed libswscale5_9-4.4-pm154.2.7.x86_64 Solution 1: Following actions will be done: install libswscale5_9-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing libswscale5_9-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install libswresample3_9-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing libswresample3_9-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install libpostproc55_9-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing libpostproc55_9-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install libavutil56_70-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing libavutil56_70-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install libavresample4_0-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing libavresample4_0-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install libavformat58_76-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing libavformat58_76-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install libavfilter7_110-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing libavfilter7_110-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install libavdevice58_13-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing libavdevice58_13-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install libavcodec58_134-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing libavcodec58_134-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install ffmpeg-4-libswscale-devel-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing ffmpeg-4-libswscale-devel-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install ffmpeg-4-libswresample-devel-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing ffmpeg-4-libswresample-devel-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install ffmpeg-4-libavutil-devel-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing ffmpeg-4-libavutil-devel-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install ffmpeg-4-libavresample-devel-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing ffmpeg-4-libavresample-devel-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de install ffmpeg-4-4.4-150400.3.2.1.x86_64 from vendor SUSE LLC <https://www.suse.com/> replacing ffmpeg-4-4.4-pm154.2.7.x86_64 from vendor http://packman.links2linux.de Solution 2: do not install patch:openSUSE-SLE-15.4-2022-2969-1.noarch Choose from above solutions by number or cancel [1/2/c/d/?] (c): Greetings, Björn

2 2

help understanding power saving methods (laptop) on current opensuse
by cagsm 21 Oct '22

21 Oct '22

Support, apparently utter and total noob here understanding or making use of power saving methods on laptop on current leap here. major brand rather current generation laptop hardware here. default leap with kde install. when i sleep (technical name: suspend?) the laptop from via kde menu or close the lid, it still eats away huge amounts of the battery of this laptop. also it plays sounds and clickery effects from the speaker when for example i turn off my power outlet (switch off power) for example. the laptop apparently doesnt sleep at all or i have very different understanding and reasoning what sleep would mean. coming from a windows world, my (older) laptops back ages ago really went still, powered down the cpu and memory and disks, would not cause heat at all, or barely eat away the battery at all. i am not talking memory-saving-to-disk here at all (technical term: hibernation) thats what I am trying to avoid, as it really writes away so much amount of ram completely to SSD these days, and still takes like a lot of time. i am first trying to make use of normal sleep (suspend). i wonder if linux is so incapable of saving power to begin with, or if this is a configuration issue, or an opensuse leap issue or kernel issue or whatever. for example: when i put the system to sleep via kde menu, the close the lid only after that, i have the feeling that the system still reacts to the lid even as if it would unsleep the machine again, like a switch button, sleep from kde menu = suspend swith pressed. lid closing = suspend switch button pressed once again thus un-suspend waking it again. when having the lid closed and i turn off the laptops power then (unplug it from ac socket etc.) then the laptops creates sound in reaction to that, showin the user (me) that some power event happened or once again suspend switch pressed once more figuratively. this all dont make sense to me, how can an already sleeping laptop in the fist place react to closing the lid. in my universe that would only acknowledge the wanted sleeping suspend state by the user, but apparently it is not. then pulling the ac power after that even creates for another contradicting event on addition on top of that. i am really confused. my windows machine once put to sleep, does not generate sounds, and does not re-ware up or change its state when i pull the plug, or reconnect the ac plug and more. i am seriously missing the KDE configuration gui what happens when i close the lid and when i pull the power etc apparently there is only three major categories as a state of things, running on ac, running on battery and running on low battery. but this does not reflect my true reality of things. what am I getting wrong here? ty.

3 2

[TW] Moving /home to a new drive
by Bob Williams 20 Oct '22

20 Oct '22

I am trying to move /home from a rather tired hdd to a new ssd on this desktop Tumbleweed system running KDE Plasma. / is on an nvme drive. I have formatted (xfs) a partition on the new drive (/dev/sda1) and copied /home from the old drive to the new drive. I have edited /etc/fstab to mount /dev/sda1 on /home and commented the line defining the hdd's mount point. When I reboot, I get as far as the login screen, but my password is not accepted. The login screen keeps reappearing asking for a password. Any suggestions as to what I may have missed out? Thanks Bob -- Bob Williams No HTML please. Plain text preferred. https://useplaintext.email/

5 5

korganizer: can't send invitation mails
by mh＠mike.franken.de 19 Oct '22

19 Oct '22

Hi, with the latest Tumbleweed snapshot and korganizer-22.08.1-1.1.x86_64 it is no longer possible to send invitation mails when using a CalDAV server like SabreDAV (Nextcloud, baikal). When creating an invitation and adding an email address, it is converted to something like CN=<name>;RSVP=TRUE;PARTSTAT=ACCEPTED;ROLE=REQ- PARTICIPANT;CUTYPE=INDIVIDUAL;X-UID=94351025505088:mailto:<mail address> which obviously isn't a valid email address. Therefore no email is sent. On clicking "OK" to save the invitation, Korganizer even shows a dialog box, that it isn't a valid email address and asks to remove this recipient. This makes korganizer nearly unusable for me. Everything works on Android (DavX) and Windows clients (Outlook plugin), so it doesn't seem to be a server problem. I already opened a bug for this (https://bugzilla.suse.com/show_bug.cgi? id=1204362), but perhaps someone here can help with a workaround. TIA. Bye. Michael.

1 1

Support for remote display?
by Freek de Kruijf 17 Oct '22

17 Oct '22

I have a smart TV that I can configure as a remote display. In Windows I can start a remote display as if it is another (second) display in my system. This system uses a network connection to transfer the data to the TV screen. Does openSUSE or any other Linux system supports the same feature? -- fr.gr. member openSUSE Freek de Kruijf

2 1

Mariadb refuses to start
by Jogchum Reitsma 13 Oct '22

13 Oct '22

Hi, Since some time my mariadb does not start at system start. I don't use the mariadb databases a lot, so I didn't notice it immediately. Hence I'm unsure when the problem occurred first time. When trying to start is manually, I gor the message [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.8. Searching that message, I saw a post on https://bbs.archlinux.org/viewtopic.php?id=259364 Like me, he had a non-default location for the databases configured in /etc/my.cnf. The solution that worked for him was to change that to another location in my.cnf, starting the database (which now succeeded), and copy the existing databases to that new location. So I decided to mimic that: commented out the existing database location, entered an new one, and started the database server (as root) with systemctl start mariadb After a while, the new location is created (owned by mysql:root) and populated: l mysql_recover totaal 111048 drwx------ 6 mysql root 243 2 okt 21:33 ./ drwxr-xr-x 225 jogchum users 16384 2 okt 21:26 ../ -rw-rw---- 1 mysql mysql 417792 2 okt 21:27 aria_log.00000001 -rw-rw---- 1 mysql mysql 52 2 okt 21:27 aria_log_control -rw-rw---- 1 mysql mysql 942 2 okt 21:27 ib_buffer_pool -rw-rw---- 1 mysql mysql 12582912 2 okt 21:27 ibdata1 -rw-rw---- 1 mysql mysql 100663296 2 okt 21:27 ib_logfile0 drwx------ 2 mysql mysql 4096 2 okt 21:27 mysql/ -rw-rw---- 1 root root 14 2 okt 21:27 mysql_upgrade_info drwx------ 2 mysql mysql 28 2 okt 21:27 performance_schema/ drwx------ 2 mysql mysql 8192 2 okt 21:27 sys/ drwx------ 2 mysql mysql 28 2 okt 21:27 test/ But unlike the posting at bbs.archlinux.org just mentioned, the server crashed again, now with the following messages in journalctl: #################################################################################3 journalctl -xeu mariadb.service A start job for unit mariadb.service has finished with a failure. The job identifier is 2782226 and the job result is failed. okt 02 21:20:47 linux-mkay systemd[1]: Starting MariaDB database server... Subject: A start job for unit mariadb.service has begun execution Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit mariadb.service has begun execution. The job identifier is 2790830. okt 02 21:20:47 linux-mkay mysql-systemd-helper[44977]: 2022-10-02 21:20:47 0 [Note] /usr/sbin/mysqld (server 10.8.3-MariaDB) starting as process 44977 ... okt 02 21:20:48 linux-mkay systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Subject: Unit process exited Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel An ExecStart= process belonging to unit mariadb.service has exited. The process' exit code is 'exited' and its exit status is 1. okt 02 21:20:48 linux-mkay systemd[1]: mariadb.service: Failed with result 'exit-code'. Subject: Unit failed Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel The unit mariadb.service has entered the 'failed' state with result 'exit-code'. okt 02 21:20:48 linux-mkay systemd[1]: Failed to start MariaDB database server. Subject: A start job for unit mariadb.service has failed Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit mariadb.service has finished with a failure. The job identifier is 2790830 and the job result is failed. okt 02 21:26:55 linux-mkay systemd[1]: Starting MariaDB database server... Subject: A start job for unit mariadb.service has begun execution Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel A start job for unit mariadb.service has begun execution. The job identifier is 2792404. okt 02 21:26:55 linux-mkay mysql-systemd-helper[45372]: Creating MySQL privilege database... okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: Two all-privilege accounts were created. okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: One is root@localhost, it has no password, but you need to okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: be system 'root' user to connect. Use, for example, sudo mysql okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: The second is mysql@localhost, it has no password either, but okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: you need to be the system 'mysql' user to connect. okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: After connecting you can set the password, if you would need to be okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: able to connect as any of these users with a password and without sudo okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: See the MariaDB Knowledgebase at https://mariadb.com/kb okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: Please report any problems at https://mariadb.org/jira okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: The latest information about MariaDB is available at https://mariadb.org/. okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: Consider joining MariaDB's strong and vibrant community: okt 02 21:27:17 linux-mkay mysql-systemd-helper[45384]: https://mariadb.org/get-involved/ okt 02 21:27:17 linux-mkay mysql-systemd-helper[45468]: 2022-10-02 21:27:17 0 [Note] /usr/sbin/mysqld (server 10.8.3-MariaDB) starting as process 45468 ... okt 02 21:27:17 linux-mkay mysql-systemd-helper[45468]: 2022-10-02 21:27:17 0 [Warning] Can't create test file /home/jogchum/mysql_recover/linux-mkay.lower-test okt 02 21:27:17 linux-mkay mysql-systemd-helper[45468]: [103B blob data] okt 02 21:27:17 linux-mkay mysql-systemd-helper[45468]: 2022-10-02 21:27:17 0 [ERROR] Aborting okt 02 21:27:17 linux-mkay systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Subject: Unit process exited Defined-By: systemd Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ############################################################################################3 Anyone an idea why /home/jogchum/mysql_recover/linux-mkay.lower-test cna't be created an how to solve that? Thans in advance! regards, Jogchum

2 3

TW - Cant remove own files
by Axel Braun 10 Oct '22

10 Oct '22

H, dunno if this is a quirky on TW 20221004, or a more general issue, but I cant remove files which I own: docb@X1E:~/Downloads> whoami docb docb@X1E:~/Downloads> dir openSUSE-MicroOS-DVD-x86_64-Snapshot20220719- Media.iso -rw-r--r-- 1 docb users 4018143232 23. Jul 20:12 openSUSE-MicroOS-DVD-x86_64- Snapshot20220719-Media.iso docb@X1E:~/Downloads> rm openSUSE-MicroOS-DVD-x86_64-Snapshot20220719- Media.iso rm: cannot remove 'openSUSE-MicroOS-DVD-x86_64-Snapshot20220719-Media.iso': Permission denied Deletion works only as root. Anyone seen his before? Cheers Axel

4 4