This bug report is being closed due to your last comment regarding this
being fixed with an update. For future reference you can manage the
status of your own bugs by clicking on the current status in the yellow
line and then choosing a new status in the revealed drop down box. You
can learn more a
None at all. Right now it has an uptime of 18 days, 21:56 hours, and
still counting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683906
Title:
transmission-daemon crashed with SIGSEGV in realloc()
Raúl, have you had any further crashes after upgrading?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683906
Title:
transmission-daemon crashed with SIGSEGV in realloc()
--
ubuntu-bugs mailing lis
Instead of building the 2.22 release, I ended using the one from
https://launchpad.net/~transmissionbt/+archive/ppa.
It's been running for 4 days in a row without crashing, while the 2.13
crashed in 2 days.
The 2.13 from maverick has been running more stable since a week ago or
so, maybe it's not
I've been testing 2.13 on Natty for a while in virtual machine, was
going to report it not crashing, and then it crashed 2 minutes ago.
Same thing, couldn't backtrace it.
I'll build the last release and try again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
El 07/03/11 22:56, jordan escribió:
> Raúl, I appreciate the Valgrind log very much; however, it doesn't seem
> to show the crash in realloc() that this ticket is about. I'm not sure
> how to proceed from here. Do you have any suggestions what I shou
Raúl, I appreciate the Valgrind log very much; however, it doesn't seem
to show the crash in realloc() that this ticket is about. I'm not sure
how to proceed from here. Do you have any suggestions what I should to
do trigger this error?
Also, if you try testing on a prerelease of 11.04, does Trans
** Attachment added: "Valgrind log"
https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/683906/+attachment/1801523/+files/transmission-daemon.valgrind.bz2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
I made the mistake of deleting the log (since there was no crash and
all), so I'll run it again for a day or two and send them.
I'm a little reluctant to use development releases on my servers, but I
may be able to assemble a virtual machine where to test it.
--
You received this bug notific
Hi Raúl,
It's possible that valgrind logged the error even if it didn't crash. If
you'd like to compress them and mail them to me at @transmissionbt.com, I'll take a look at them.
Another thing that we could try is you could upgrade to the version of
transmission-daemon. I don't run Ubuntu so I h
By the way, thanks for running valgrind for five(!) days. Valgrind is
not light on system resources :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/683906
Title:
transmission-daemon crashed with SI
After five days and a half running with valgrind without a problem, I
stopped it, rebooted the system and started it normally. Then, on first
access it failed again. In the attached screenshot it's visible that the
web interface is loaded without the transfer list (there should be at
least 3 torren
I'ts been running with valgrind for a day and a half without crashing
(still running).
While this test runs, I'm testing another pc without, with same
distribution, version, configuration and torrents, and it crashed 2
times. Both crashes happened while trying to connect to the web
interface from
I'll try to get a valgrind log, but it may take some time (I have
nothing to download right now).
Since you ask for suggestions, I think transmission-daemon should log
it's activities, like most services do.
Whenever I have a problem with a service, my first step to fix it is to
look at /var/log/
Raúl, thanks for reporting this.
I'm not sure how to proceed with this ticket: the crash isn't one that
I've seen elsewhere and I transmission-daemon isn't crashing for me.
Also, the retrace does't say very much, although base=0x looks
very suspicious to me.
Raúl, would you be willing to
** Visibility changed to: Public
--
transmission-daemon crashed with SIGSEGV in realloc()
https://bugs.launchpad.net/bugs/683906
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
16 matches
Mail list logo
