March 2023 - openSUSE Users - openSUSE Mailing Lists

Buggy kernel update?
by James Knott 18 Mar '23

18 Mar '23

Today, both my computers got a kernel update and both are dead in the water, unless I boot a previous kernel. This is on a desktop system, with Gigabyte mom board and a ThinkPad. They lock up immediately after the boot menu, requiring killing the power to clear. Has anyone else noticed this? BTW, in the twenty odd years I've been running Linux, this is the first time I had to resort to using a previous kernel.

6 8

yesterday's X issue - xauth is all that is needed.
by Per Jessen 17 Mar '23

17 Mar '23

This issue has been gnawing at me all day. It seems to me that Carlos' use case is so straight forward, it should Just Work (R), i.e. without magical incantations and mysterious work-arounds :-) xauth is all that is needed. I admit I have not yet fully grasped exactly what's going on: I have two systems - destination = toshiba1 with Leap 15.2 and KDE origin = office68 with Leap 15.3 and KDE When physically logged in on toshiba1: In: xauth generate :0 . Out: Invalid MIT-MAGIC-COOKIE-1 key Check results with "xauth list", there ought to be a new line with toshiba1/unix:0 MIT-MAGIC-COOKIE-1 <hexkey> Physically logged in on office68: ssh toshiba1 xauth list grab the hexkey, paste it here: xauth add :0 . hexkey With this, I can start an xclock from office68 on toshiba1 thus: ssh toshiba1 DISPLAY=:0 xclock I can also start e.g. okular, kmines, kicad, but firefox doesn't seem to quite work. At least I was unable to connect to an existing instance - when I tried with "--new-instance", I got a pop up about needing a new profile. Closing down the running firefox (on toshiba1), and it worked fine. By default, the generated key expires after 60 seconds of inactivity, but there is a timeout option. Just trying that out now. -- Per Jessen, Zürich (9.4°C) Member, openSUSE Heroes (2016 - present) We're hiring - https://en.opensuse.org/openSUSE:Heroes

5 25

Problem with update because of apparent conflict with telegram dependencies
by Stakanov 16 Mar '23

16 Mar '23

entropy@localhost:~> sudo LC_ALL=en sudo zypper dup Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... 2 Problems: Problem: problem with the installed libswresample4-5.1.2-16.2.x86_64 Problem: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-5-mini-libs-5.1.2-10.1.x86_64 Problem: problem with the installed libswresample4-5.1.2-16.2.x86_64 Solution 1: deinstallation of libswresample4-5.1.2-16.2.x86_64 Solution 2: keep obsolete libswresample4-5.1.2-16.2.x86_64 Solution 1: deinstallation of libswresample4-5.1.2-16.2.x86_64 so if we try we get: Problem: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-5-mini-libs-5.1.2-10.1.x86_64 Solution 1: install libavutil57-5.1.2-10.1.x86_64 from vendor openSUSE replacing libavutil57-5.1.2-16.2.x86_64 from vendor http:// packman.links2linux.de Solution 2: deinstallation of telegram-desktop-4.6.5-3.1.x86_64 Solution 3: keep obsolete libavutil57-5.1.2-16.2.x86_64 Solution 4: break ffmpeg-5-mini-libs-5.1.2-10.1.x86_64 by ignoring some of its dependencies so, or you get into dependency hell from the packman side or you have a problem with telegram. I refrain for now from a bug report (as I have no membership of factory since they do not wish people to post there. Good, posting it here. If you try with 1: Computing distribution upgrade... 2 Problems: Problem: the to be installed libpostproc56-5.1.2-pm1599.17.1.x86_64 requires 'libavutil57 = 5.1.2-pm1599.17.1', but this requirement cannot be provided Problem: nothing provides 'this-is-only-for-build-envs' needed by the to be installed ffmpeg-5-mini-libs-5.1.2-10.1.x86_64 Problem: the to be installed libpostproc56-5.1.2-pm1599.17.1.x86_64 requires 'libavutil57 = 5.1.2-pm1599.17.1', but this requirement cannot be provided not installable providers: libavutil57-5.1.2-pm1599.17.1.i586[packman] libavutil57-5.1.2-pm1599.17.1.x86_64[packman] Solution 1: install libpostproc56-5.1.2-10.1.x86_64 from vendor openSUSE replacing libpostproc56-5.1.2-16.2.x86_64 from vendor http:// packman.links2linux.de Solution 2: do not install libavutil57-5.1.2-10.1.x86_64 Solution 3: break libpostproc56-5.1.2-pm1599.17.1.x86_64 by ignoring some of its dependencies and so on and so forth.

4 4

Bug 1203600 fixed or not?
by Philippe Andersson 16 Mar '23

16 Mar '23

Hello List, Bug 1203600 - tar extract fails with Unexpected inconsistency when making directory (https://bugzilla.suse.com/show_bug.cgi?id=1203600) was supposedly fixed in tar package version 'tar-1.34-150000.3.22.3', but we still see the same symptoms (in a "real life" scenario -- we're not using the reproducer) with tar-1.34-150000.3.31.1.x86_64 (= latest one) on a SLES 15 SP4 system. Should I re-open the bug, or is this regression already known and tracked somewhere else? Thanks in advance for any pointers. Ph. A. -- *Philippe Andersson* Unix System Administrator IBA Particle Therapy | Tel: +32-10-475.983 Fax: +32-10-487.707 eMail: pan(a)iba-group.com <http://www.iba-worldwide.com> Disclaimer | Use of IBA e-communication<https://iba-worldwide.com/disclaimer> The contents of this e-mail message and any attachments are intended solely for the recipient (s) named above. This communication is intended to be and to remain confidential and may be protected by intellectual property rights. Any use of the information contained herein (including but not limited to, total or partial reproduction, communication or distribution of any form) by persons other than the designated recipient(s) is prohibited. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free. Ion Beam Applications does not accept liability for any such errors. Thank you for your cooperation.

1 0

TW20230312: No (wired) network with kernel 6.2.2
by Pit Suetterlin 16 Mar '23

16 Mar '23

Hi list, I just DUPed my laptop to the latest TW (20230312), and was left without (wired) network :( From the journal: Mar 14 13:09:35 woodstock.pitnet NetworkManager[950]: <info> [1678795775.3538] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/6) Mar 14 13:09:35 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: (PCI Express:2.5GT/s:Width x1) 50:7b:9d:cf:13:43 Mar 14 13:09:35 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: Intel(R) PRO/1000 Network Connection Mar 14 13:09:35 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: MAC: 12, PHY: 12, PBA No: 1000FF-0FF Mar 14 13:09:35 woodstock.pitnet NetworkManager[950]: <info> [1678795775.3881] device (eth0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external') Mar 14 13:09:35 woodstock.pitnet systemd-networkd[826]: eth0: Link UP Mar 14 13:09:38 woodstock.pitnet systemd-networkd[826]: eth0: Gained carrier Mar 14 13:09:38 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 10 Mbps Full Duplex, Flow Control: None Mar 14 13:09:38 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: 10/100 speed: disabling TSO Mar 14 13:09:38 woodstock.pitnet kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Mar 14 13:09:38 woodstock.pitnet NetworkManager[950]: <info> [1678795778.9629] device (eth0): carrier: link connected Mar 14 13:09:38 woodstock.pitnet NetworkManager[950]: <info> [1678795778.9633] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed') Mar 14 13:09:38 woodstock.pitnet NetworkManager[950]: <info> [1678795778.9642] device (eth0): Activation: starting connection 'Wired connection 1' (44d9a1e3-ba1a-3cd2-b746-b172b9ac4f84) Mar 14 13:09:38 woodstock.pitnet NetworkManager[950]: <info> [1678795778.9643] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed') Mar 14 13:09:39 woodstock.pitnet NetworkManager[950]: <info> [1678795779.0713] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Mar 14 13:09:39 woodstock.pitnet NetworkManager[950]: <info> [1678795779.0723] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed') Mar 14 13:09:39 woodstock.pitnet NetworkManager[950]: <info> [1678795779.0727] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds) Mar 14 13:09:39 woodstock.pitnet systemd-networkd[826]: eth0: Lost carrier What? 10Mbps? What happened there? Booting with the previous kernel (6.1.12) everything works Mar 14 13:14:00 woodstock.pitnet kernel: e1000e 0000:00:1f.6 eth0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None Anyone else having issues with the network, or hints what has changed?

4 8

Bugzilla down?
by David C. Rankin 16 Mar '23

16 Mar '23

All, When I click "Login" to Bugzilla -- nothing happens (nothing). Is it on the fritz tonight? -- David C. Rankin, J.D.,P.E.

5 5

Leap 15.4 mailx quite dated
by David C. Rankin 15 Mar '23

15 Mar '23

Devs, mailx is a fantastic command line mailer, but the version for 15.4 is more than a DECADE out of date, e.g. $ mailx -V 12.5 7/5/10 Uhhh, that's July 2010 folks? Why are we not using the s-nail package which still enjoys active development? E.g. $ mailx -V mail v14.9.24, 2022-03-26 (built for Linux) At least that's only 11 months old, not 13 years... -- David C. Rankin, J.D.,P.E.

7 27

Test
by Peter Suetterlin 15 Mar '23

15 Mar '23

Sorry for the noise. But since some days I'm no longer receiving my own posts from the list - this is a test with changed settings...

2 1

Re: JOB | Linux: on-premises, automation, vm (Edinburgh)
by David C. Rankin 14 Mar '23

14 Mar '23

On 3/7/23 05:21, James Tobin wrote: > Hello, I'm working with a global platform that is looking to hire > someone to fulfill a position in Edinburgh that is similar to that of > a systems administrator or devops engineer where you will run and > mentor a small on-premises data center infrastructure team. VM and > automated deployment of servers is critical. Consequently, I had > hoped that some members of this list may like to discuss further. I > can be contact using "JamesBTobin (at) Gmail (dot) Com". Kind regards, > James Well ... at least James was smart enough to look in the right places, and should also drop by the Unix & Linux and Server Fault StackExchange sites. https://unix.stackexchange.com/ https://serverfault.com/ -- David C. Rankin, J.D.,P.E.

1 0

[oS-en] How to turn off wifi on terminal (not nmcli) [and solved]
by Carlos E. R. 13 Mar '23

13 Mar '23

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I have just upgraded my miniserver to 15.3. The wifi has turned automatically off, and I don't remember how to turn it off in the CLI. The command has rotated out of the command history. Problem is this noise: 0.4> 2023-03-05T21:10:26.569573+01:00 Isengard kernel - - - [ 3646.480233] IPv4: martian source 192.168.255.255 from 192.168.1.16, on dev wlan0 <0.4> 2023-03-05T21:10:26.569578+01:00 Isengard kernel - - - [ 3646.480247] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 <0.4> 2023-03-05T21:10:26.569580+01:00 Isengard kernel - - - [ 3646.481572] IPv4: martian source 192.168.255.255 from 192.168.1.16, on dev wlan0 <0.4> 2023-03-05T21:10:26.569583+01:00 Isengard kernel - - - [ 3646.481584] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 <0.4> 2023-03-05T21:10:28.409398+01:00 Isengard kernel - - - [ 3648.321785] IPv4: martian source 192.168.255.255 from 192.168.1.16, on dev wlan0 <0.4> 2023-03-05T21:10:28.409440+01:00 Isengard kernel - - - [ 3648.321791] ll header: 00000000: ff ff ff ff ff ff 4c cc 6a 61 50 a1 08 00 I tried: Isengard:~ # iw dev wlan0 disconnect command failed: Operation not permitted (-1) Isengard:~ # It is not network manager. sengard:~ # nmcli radio wifi off Error: NetworkManager is not running. Isengard:~ # iw dev wlan0 [tab][tab] doesn't work. Google search fails. Insist of using the GUI, or NM, or turning it ON. google "turn off wifi on terminal opensuse" FOUND IT! Isengard:~ # ifdown wlan0 wlan0 device-ready Isengard:~ # - -- Cheers Carlos E. R. (from 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZAT5uxwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVkygAoJE3eVF+PRjDPHnwMD0A VpIIl8MdAJ9a5/l3CaQCq86BlkTnFo3qW+eFTg== =m97E -----END PGP SIGNATURE-----

8 34