Bug 1221117

Summary:	zypper hardlocks.
Product:	[openSUSE] openSUSE Distribution	Reporter:	Carlos Robinson <carlos.e.r>
Component:	libzypp	Assignee:	E-mail List <zypp-maintainers>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Leap 15.6
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	zypper log of crashed zypper session

Description Carlos Robinson 2024-03-07 12:13:06 UTC

Created attachment 873298 [details]
zypper log of crashed zypper session

"zypper install" hard locks, kill 9 fails. Ctrl c acknowledges, does not exit.

"ip addr", same thing.

Might be related to Bug 1221114 - Kernel oopses when trying to connect via WiFi

Comment 1 Stefan Hundhammer 2024-03-07 14:03:49 UTC

Zypper is not YaST. There is a separate Bugzilla component for it: libzypp.

Reassigning.

It might still be a kernel problem, though. But let's have the libzypp / zypper maintainers have a look at this first.

Comment 2 Carlos Robinson 2024-03-07 21:36:57 UTC

Sorry, I looked for zypper under "zypper", starting with letter "z". The component list combo could be improved to have a search feature, and then I would have been able to find "libzypp". Searching visually on a long list is limited, as you have experienced.

Comment 3 Michael Andres 2024-03-08 07:55:49 UTC

Likely the kernel issue. The log shows nothing suspicious, but the commands stop immediately after having entered curl.
> MediaCurl.cc(doGetFileCopyFile):1200 URL: http...
> [END]

One could try
> ZYPP_MEDIA_CURL_DEBUG=3 zypper ...

This would increase the verbosity of libcurl. It will show the connect, SSL handshakes and the exchange of headers. It might give a hint when the OOps occurs, but I somewhat doubt that this can be solved inside libzypp/libcurl.

I'd close it as duplicate/followup of bug#1221114.

Comment 4 Michael Andres 2024-03-08 07:56:23 UTC

.

*** This bug has been marked as a duplicate of bug 1221114 ***