Bug 1227709 - zypper segfaults when downloading packages and Ctrl+C is pressed multiple times
Summary: zypper segfaults when downloading packages and Ctrl+C is pressed multiple times
Status: NEW
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: libzypp (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-12 12:03 UTC by Dominik Heidler
Modified: 2024-07-15 10:49 UTC (History)
3 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
zypper logs (392.39 KB, text/plain)
2024-07-15 10:49 UTC, Dominik Heidler
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Dominik Heidler 2024-07-12 12:03:15 UTC
# zypper up
[...]
900 packages to upgrade, 4 new, 1 to remove.
Overall download size: 1.40 GiB. Already cached: 3.5 MiB. After the operation, additional 25.4 MiB will be used.

    Consider to cancel:
    Product 'openSUSE Tumbleweed' requires to be upgraded by calling 'zypper dup'!

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y):
In cache openQA-bootstrap-4.6.1720717646.f39dffb1-6873.1.x86_64.rpm                                                                                                                           (1/904), 164.7 KiB
In cache ImageMagick-config-7-SUSE-7.1.1.34-1.2.x86_64.rpm                                                                                                                                    (2/904),  86.9 KiB
In cache boost-license1_85_0-1.85.0-2.1.noarch.rpm                                                                                                                                            (3/904),  12.3 KiB
In cache borgbackup-1.2.8-1.1.x86_64.rpm                                                                                                                                                      (4/904),   1.4 MiB
In cache branding-openSUSE-84.87.20240405-1.4.noarch.rpm                                                                                                                                      (5/904),   9.8 KiB
In cache ccache-4.10.1-1.1.x86_64.rpm                                                                                                                                                         (6/904), 559.7 KiB
In cache eza-0.18.21+0-1.1.x86_64.rpm                                                                                                                                                         (7/904), 795.1 KiB
In cache fakeroot-1.35.1-1.1.x86_64.rpm                                                                                                                                                       (8/904), 123.4 KiB
In cache ghc-unicode-data-0.4.0.1-5.1.x86_64.rpm                                                                                                                                              (9/904), 290.6 KiB
In cache ghc-zlib-0.6.3.0-6.1.x86_64.rpm                                                                                                                                                     (10/904),  84.3 KiB
Retrieving: git-core-2.45.2-1.2.x86_64 (Haupt-Repository (OSS))                                                                                                                              (11/904),   5.5 MiB
Retrieving: git-core-2.45.2-1.2.x86_64.rpm ...........................................................................<51%>==========================================================================[- (2.8 MiB/s)]^C
Trying to exit gracefully...
^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^C^CSpeicherzugriffsfehler (Speicherabzug geschrieben)
[root@midas dheidler]# ^C




The text at the end translates to: Segmentaion Fault (Core dumped)
Comment 1 Felix Miata 2024-07-14 10:47:59 UTC
The is very much not new behavior. Rpm resists being interrupted.
Comment 2 Benjamin Zeller 2024-07-15 05:31:46 UTC
Do you still have the zypper logs or backtrace? Very much likely this happens in libcurl which can be problematic to shut down in the middle of a download.
Comment 3 Dominik Heidler 2024-07-15 10:49:36 UTC
Created attachment 876050 [details]
zypper logs

[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `zypper up'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f2ae98991a6 in pthread_rwlock_wrlock@GLIBC_2.2.5 () from /lib64/libc.so.6
[Current thread is 1 (Thread 0x7f2ae852bb00 (LWP 32884))]
(gdb) bt
#0  0x00007f2ae98991a6 in pthread_rwlock_wrlock@GLIBC_2.2.5 () at /lib64/libc.so.6
#1  0x00007f2ae91f6119 in CRYPTO_THREAD_write_lock () at /lib64/glibc-hwcaps/x86-64-v3/libcrypto.so.3.1.4
#2  0x00007f2ae9226ac3 in RAND_get_rand_method () at /lib64/glibc-hwcaps/x86-64-v3/libcrypto.so.3.1.4
#3  0x00007f2ae9227aa6 in RAND_status () at /lib64/glibc-hwcaps/x86-64-v3/libcrypto.so.3.1.4
#4  0x00007f2ae9aee56c in ??? () at /lib64/libcurl.so.4
#5  0x00007f2ae9a9407e in ??? () at /lib64/libcurl.so.4
#6  0x00007f2ae9a897c1 in ??? () at /lib64/libcurl.so.4
#7  0x00007f2ae9afcc5b in ??? () at /lib64/libcurl.so.4
#8  0x00007f2ae9a8fab4 in curl_easy_cleanup () at /lib64/libcurl.so.4
#9  0x00007f2aea18b531 in ??? () at /lib64/libzypp.so.1734
#10 0x00007f2aea16eb80 in zypp::media::MediaHandler::disconnect() () at /lib64/libzypp.so.1734
#11 0x00007f2aea16f004 in zypp::media::MediaHandler::release(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () at /lib64/libzypp.so.1734
#12 0x00007f2aea19a26e in ??? () at /lib64/libzypp.so.1734
#13 0x00007f2aea1a3ba1 in ??? () at /lib64/libzypp.so.1734
#14 0x00007f2aea1a2aba in ??? () at /lib64/libzypp.so.1734
#15 0x00007f2ae98433c1 in __cxa_finalize () at /lib64/libc.so.6
#16 0x00007f2aea139e67 in ??? () at /lib64/libzypp.so.1734
#17 0x00007f2aea71cd20 in ??? ()
#18 0x00007f2aea725102 in _dl_call_fini () at /lib64/ld-linux-x86-64.so.2
#19 0x00007f2aea7291ee in _dl_fini () at /lib64/ld-linux-x86-64.so.2
#20 0x00007f2ae98439e6 in __run_exit_handlers () at /lib64/libc.so.6
#21 0x00007f2ae9843b30 in exit () at /lib64/libc.so.6
#22 0x0000564fbd1a471b in ??? ()
#23 0x0000564fbd1ada98 in ??? ()
#24 0x0000564fbd18d574 in ??? ()
#25 0x00007f2aea1c7282 in ??? () at /lib64/libzypp.so.1734
#26 0x00007f2aea1c1811 in zypp::repo::PackageProvider::providePackage() const () at /lib64/libzypp.so.1734
#27 0x00007f2aea1f2e13 in zypp::target::RepoProvidePackage::operator()(zypp::PoolItem const&, bool) () at /lib64/libzypp.so.1734
#28 0x00007f2aea20e540 in ??? () at /lib64/libzypp.so.1734
#29 0x00007f2aea1f24db in ??? () at /lib64/libzypp.so.1734
#30 0x00007f2aea1f314d in ??? () at /lib64/libzypp.so.1734
#31 0x00007f2aea1ed0c1 in zypp::target::CommitPackageCache::get(zypp::PoolItem const&) () at /lib64/libzypp.so.1734
#32 0x00007f2aea203002 in ??? () at /lib64/libzypp.so.1734
#33 0x00007f2aea2cadaa in ??? () at /lib64/libzypp.so.1734
#34 0x00007f2aea2b5470 in zypp::ZYpp::commit(zypp::ZYppCommitPolicy const&) () at /lib64/libzypp.so.1734
#35 0x0000564fbd274cb4 in ??? ()
#36 0x0000564fbd232d3d in ??? ()
#37 0x0000564fbd1e63c8 in ??? ()
#38 0x0000564fbd1af12b in ??? ()
#39 0x0000564fbd17d1f5 in ??? ()
#40 0x00007f2ae982a1f0 in __libc_start_call_main () at /lib64/libc.so.6
#41 0x00007f2ae982a2b9 in __libc_start_main_impl () at /lib64/libc.so.6
#42 0x0000564fbd17fad5 in _start ()
(gdb)