[Bug 870738] Re: transmission-gtk crashed with SIGABRT in raise()

2013-05-23 Thread Launchpad Bug Tracker
[Expired for transmission (Ubuntu) because there has been no activity for 60 days.] ** Changed in: transmission (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 870738] Re: transmission-gtk crashed with SIGABRT in raise()

2013-03-24 Thread Mikhail Krutov
stacktrace from 13.04. ** Attachment added: _usr_bin_transmission-gtk.1000.crash https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/870738/+attachment/3593497/+files/_usr_bin_transmission-gtk.1000.crash -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 870738] Re: transmission-gtk crashed with SIGABRT in raise()

2013-02-18 Thread Charles Kerr
Skai, thanks for helping to track this down. Could you provide a Stacktrace from the 13.04 crash? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870738 Title: transmission-gtk crashed with SIGABRT

[Bug 870738] Re: transmission-gtk crashed with SIGABRT in raise()

2013-01-27 Thread Skai Falkorr
Omer Akram yep. it's still an issue. just caught in 13.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/870738 Title: transmission-gtk crashed with SIGABRT in raise() To manage notifications about

[Bug 870738] Re: transmission-gtk crashed with SIGABRT in raise()

2013-01-27 Thread Charles Kerr
Is the crash in 13.04 following the same trace of event_errx (), evdns_cancel_request()? This looks more like a libevent issue than a Transmission one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 870738] Re: transmission-gtk crashed with SIGABRT in raise()

2013-01-17 Thread Omer Akram
Thanks for your bug report. Is that still an issue for you? From looking at the date on which is bug was created and given the fact there have been no duplicates to this bug report I would think otherwise. It would be really helpful if you could verify the issue not happening anymore. ** Changed