Description of problem: ran /usr/bin/rtorrent with an existing collection of active torrents Version-Release number of selected component: rtorrent-0.9.8-10.fc38 Additional info: reporter: libreport-2.17.9 type: CCpp reason: rtorrent killed by SIGABRT journald_cursor: s=3772fea4bd19444c9f281dc0a7e5c395;i=1d879;b=00feb2cbcf1e40c299beeb564960518d;m=41f0b18;t=5f9b613f49a2d;x=11d4f49852982c06 executable: /usr/bin/rtorrent cmdline: rtorrent cgroup: 0::/user.slice/user-1000.slice/user/app.slice/app-org.gnome.Terminal.slice/vte-spawn-2437f6e3-0c79-46f7-989b-a23f25154c49.scope rootdir: / uid: 1000 kernel: 6.2.11-300.fc38.x86_64 package: rtorrent-0.9.8-10.fc38 runlevel: N 5 backtrace_rating: 4 crash_function: snprintf comment: ran /usr/bin/rtorrent with an existing collection of active torrents Truncated backtrace: Thread no. 1 (4 frames) #8 snprintf at /usr/include/bits/stdio2.h:54 #9 utils::Lockfile::try_lock at utils/lockfile.cc:101 #10 core::DownloadStore::enable at core/download_store.cc:74 #11 Control::initialize at /usr/src/debug/rtorrent-0.9.8-10.fc38.x86_64/src/control.cc:115
Created attachment 1958372 [details] File: proc_pid_status
Created attachment 1958373 [details] File: maps
Created attachment 1958374 [details] File: limits
Created attachment 1958375 [details] File: open_fds
Created attachment 1958376 [details] File: mountinfo
Created attachment 1958377 [details] File: os_info
Created attachment 1958378 [details] File: cpuinfo
Created attachment 1958379 [details] File: core_backtrace
Created attachment 1958380 [details] File: dso_list
Created attachment 1958381 [details] File: backtrace
Created attachment 1958382 [details] File: environ
#8 snprintf at /usr/include/bits/stdio2.h:54 #9 utils::Lockfile::try_lock at utils/lockfile.cc:101 #10 core::DownloadStore::enable at core/download_store.cc:74 #11 Control::initialize at /usr/src/debug/rtorrent-0.9.8-10.fc38.x86_64/src/control.cc:115 This is almost certainly fallout from https://fedoraproject.org/wiki/Changes/Add_FORTIFY_SOURCE%3D3_to_distribution_build_flags This usage of snprintf is obviously incorrect: 97 char buf[256]; 98 int pos = ::gethostname(buf, 255); 99 100 if (pos == 0) { 101 ::snprintf(buf + std::strlen(buf), 255, ":+%i\n", ::getpid()); (There are not guaranteed to be 255 bytes in 'buf' beyond 'buf + strlen(buf)'.) ":+%i\n" is going to be, like, ~15 bytes total, so we definitely don't need 255.
Scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=100147491
Rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=100147545 F38: https://koji.fedoraproject.org/koji/taskinfo?taskID=100147616
*** Bug 2188138 has been marked as a duplicate of this bug. ***
Ah, you beat me to it: it looks like upstream addressed it here: https://github.com/rakshasa/rtorrent/pull/1169
FEDORA-2023-6f1d4e2d5b has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-6f1d4e2d5b
(In reply to Ed Marshall from comment #16) > Ah, you beat me to it: it looks like upstream addressed it here: > https://github.com/rakshasa/rtorrent/pull/1169 Ah, I didn't see the upstream fix. We can probably just keep this patch until upstream (finally) releases a new version.
FEDORA-2023-6f1d4e2d5b has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-6f1d4e2d5b` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-6f1d4e2d5b See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2023-6f1d4e2d5b has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.