Hi,
There doesn't seem to be any activity on this issue despite the fix
being available. Debian 12.1 point release is scheduled for July 22
which is one week away so it's probably not going to make it at this
point, but for future point releases — is there anything we can do to
move this forw
Setting the severity to important, because eating all memory and getting
killed by oom-killer "has a major effect on the usability of the
package".
There is a patch available. And it seems to effect everyone on bookworm.
So it would be super-awesome to get a package with a fix.
Thanks, and k
This is fixed in 4.0.1-1 (testing), but open in 3.00-2 (stable).
--
ilf
If you upload your address book to "the cloud", I don't want to be in it.
Sebastian,
it appears the NMU you performed at
https://tracker.debian.org/news/1326874/accepted-transmission-300-21-source-into-unstable/
is causing issues with transmission in stable -- are you going to
address these issues? ideally a fix should be committed to the repo
(or open an MR), a fix uplo
I am also reporting that I have an issue with memory leaks after
upgrade from Bullseye to Bookworm, where transmission-daemon changed
versions from "3.00-1" to "3.00-2.1".
The process gets killed because of OOM:
transmission.service: Main process exited, code=killed, status=9/KILL
It would be rea
Hi,
This is still an issue in stable. Gentoo has a simpler patch [1, also
attached for convenience] which also works and seems to not have this
issue. Maybe it's worth dropping current patch in favor of the Gentoo
one (which is also used by other distributions [2]) and do a stable PU
upload.
[1]
Package: transmission-daemon
Followup-For: Bug #1015003
X-Debbugs-Cc: pkre...@gmail.com
Recently upgraded from Bullseye to Bookworm and hit what I think is this issue.
Transmission-daemon gets killed by OOM every few hours. To be fair, I have a
really huge amount of torrents, but it was running
7 matches
Mail list logo
