Transmission-gtk crashes within a minute of starting it

Support Software & Applications
1

Transmission (gtk) crashes after within a minute of starting it. Nothing in the log files… gdb shows this

Thread 7 "transmission-gt" received signal SIGPIPE, Broken pipe.
[Switching to Thread 0x7fffe89ba6c0 (LWP 5960)]
0x00007ffff5b2810b in writev () from /usr/lib/libc.so.6
(gdb) bt
#0  0x00007ffff5b2810b in writev () from /usr/lib/libc.so.6
#1  0x00007ffff7f03847 in evbuffer_write_iovec (buffer=buffer@entry=0x7fffd2c9e790, fd=fd@entry=125, howmuch=0, howmuch@entry=318)
    at /usr/src/debug/libevent/libevent-2.1.12-stable/buffer.c:2460
#2  0x00007ffff7f08173 in evbuffer_write_atmost (buffer=0x7fffd2c9e790, fd=125, howmuch=318)
    at /usr/src/debug/libevent/libevent-2.1.12-stable/buffer.c:2546
#3  0x00005555556cd0a0 in libtransmission::Buffer::to_socket (this=0x7fffd2c9e498, sockfd=125, n_bytes=318, error=0x7fffe89b3058)
    at /usr/src/debug/transmission/transmission-4.0.6/libtransmission/tr-buffer.h:272
#4  tr_peer_socket::try_write (this=0x7fffd2c9e188, buf=..., max=318, error=0x7fffe89b3058)
    at /usr/src/debug/transmission/transmission-4.0.6/libtransmission/peer-socket.cc:82
#5  tr_peerIo::try_write (this=0x7fffd2c9df20, max=318) at /usr/src/debug/transmission/transmission-4.0.6/libtransmission/peer-io.cc:290
#6  0x00005555556c08d2 in tr_peerIo::flush (limit=3000, this=<optimized out>, dir=TR_CLIENT_TO_PEER)
    at /usr/src/debug/transmission/transmission-4.0.6/libtransmission/peer-io.cc:539
#7  tr_bandwidth::phaseOne (peers=..., dir=<optimized out>)
    at /usr/src/debug/transmission/transmission-4.0.6/libtransmission/bandwidth.cc:188
#8  0x00005555556dbacf in tr_bandwidth::allocate (period_msec=500, this=<optimized out>)
    at /usr/src/debug/transmission/transmission-4.0.6/libtransmission/bandwidth.cc:245
#9  tr_peerMgr::bandwidthPulse (this=0x555555a92d30) at /usr/src/debug/transmission/transmission-4.0.6/libtransmission/peer-mgr.cc:2231
#10 tr_peerMgr::tr_peerMgr(tr_session*)::{lambda()#1}::operator()() const (__closure=<optimized out>)
    at /usr/src/debug/transmission/transmission-4.0.6/libtransmission/peer-mgr.cc:689
#11 std::__invoke_impl<void, tr_peerMgr::tr_peerMgr(tr_session*)::{lambda()#1}&>(std::__invoke_other, tr_peerMgr::tr_peerMgr(tr_session*)::{lambda()#1}&) (__f=...) at /usr/include/c++/14.1.1/bits/invoke.h:61
#12 std::__invoke_r<void, tr_peerMgr::tr_peerMgr(tr_session*)::{lambda()#1}&>(tr_peerMgr::tr_peerMgr(tr_session*)::{lambda()#1}&) (
    __fn=...) at /usr/include/c++/14.1.1/bits/invoke.h:111
--Type <RET> for more, q to quit, c to continue without paging-- 
#13 std::_Function_handler<void (), tr_peerMgr::tr_peerMgr(tr_session*)::{lambda()#1}>::_M_invoke(std::_Any_data const&) (__functor=...)
    at /usr/include/c++/14.1.1/bits/std_function.h:290
#14 0x00007ffff7f17c45 in event_persist_closure (ev=<optimized out>, base=0x555555b416e0)
    at /usr/src/debug/libevent/libevent-2.1.12-stable/event.c:1623
#15 event_process_active_single_queue (base=base@entry=0x555555b416e0, activeq=0x555555b56790, 
    max_to_process=max_to_process@entry=2147483647, endtime=endtime@entry=0x0)
    at /usr/src/debug/libevent/libevent-2.1.12-stable/event.c:1682
#16 0x00007ffff7f193af in event_process_active (base=0x555555b416e0) at /usr/src/debug/libevent/libevent-2.1.12-stable/event.c:1783
#17 event_base_loop (base=0x555555b416e0, flags=4) at /usr/src/debug/libevent/libevent-2.1.12-stable/event.c:2006
#18 0x00005555556f2b5e in tr_session_thread_impl::sessionThreadFunc (this=0x555555a8e8a0, evbase=0x555555b416e0)
    at /usr/src/debug/transmission/transmission-4.0.6/libtransmission/session-thread.cc:245
#19 0x00007ffff5ce1cf4 in std::execute_native_thread_routine (__p=0x555555b4c8e0)
    at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/thread.cc:104
#20 0x00007ffff5aa339d in ?? () from /usr/lib/libc.so.6
#21 0x00007ffff5b2849c in ?? () from /usr/lib/libc.so.6
(gdb) quit

Moderator edit: In the future, please use proper formatting: [HowTo] Post command output and file content as formatted text

2 Likes
2

Arch patched curl to fix this this a few days ago. 8.9.1-2 is only available on Manjaro unstable branch right now.

3

When I couldn’t find a journal or log entry, or even a terminal output I was a bit lost till I found this post. Just installed gdb, but it doesn’t seem to get recognized by the system (command not found, didn’t try a reboot yet). Do you have a good resource on how to use gdb?

So what is the turnover time, when might we see the patch in stable? Is there a way to install a single package from unstable?

4

gdb needs debug symbols
all the “normal” packages are stripped - even if they where initially compiled with debug info.

no chance using it
you would need to build the software yourself - and allow and/or keep the debug info

no one else has got this problem - it’s not a problem with the software
rather it is with your machine setup and/or configuration

I never understood the trouble people have understanding the implications of deliberately holding back updates (Manjaro stable) vs just using the original (Arch or Manjaro unstable).

5

I’m sure this is fixable, but when I’ve to compile the source to use it I might not use it.

I don’t have a problem that packages get tested before being put into stable. That is the main reason I use Manjaro and not Arch. My question was what the turnover time is. I thought about 2 weeks, but I’m not sure.

6

:man_shrugging:

Simply downloading the package and installing it will work. In general don’t do this but it’s safe to do in this particular case.

https://ftp.halifax.rwth-aachen.de/manjaro/unstable/core/x86_64/curl-8.9.1-2-x86_64.pkg.tar.zst

7

Nice, simple, temporary fix! Thank you!

Will help anybody hoe is looking for an answer in this particular case and for those who don’t have the time to fumble around for hours.

8

curl 8.9.1-2 has been released to Testing branch - [Testing Update] 2024-08-16