Intrepid Ibex reached end-of-life on 30 April 2010 so I am closing the
report. The bug has been fixed in newer releases of Ubuntu.
** Changed in: wesnoth (Ubuntu Intrepid)
Status: Triaged => Invalid
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/287158
You re
** Branch linked: lp:ubuntu/intrepid-proposed/wesnoth
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/287158
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.ubunt
Marking to Triaged per last comment.
** Changed in: wesnoth (Ubuntu Intrepid)
Status: Fix Committed => Triaged
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/287158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This upload will be superceded by security fixes in bug #336396. Once
those fixes are in the archive, please regenerate your proposed package
based the new security update. Thanks!
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/287158
You received this bug notificatio
Gerfried Fuchs wrote:
> I haven't done a direct diff, but usually wesnoth has strict guidelines
> for their stable updates: There won't be any feature changes at all
> because a stable release has to be compatible with every other patch
> update to it. So, most of the times, the only changes are t
* Emilio Pozuelo Monfort [2009-01-27 22:41:18 CET]:
> Not really. We want a Stable Release Update for a crasher, not a
> backport. Task opened, will try to look into this soonish, but if you
> can provide a diffstat and a diff of network_worker.cpp that would be
> nice.
>
> Gerfried, do you think
Accepted into intrepid-proposed, please test and give feedback here.
Please see https://wiki.ubuntu.com/Testing/EnableProposed for
documentation how to enable and use -proposed. Thank you in advance!
** Changed in: wesnoth (Ubuntu Intrepid)
Status: Confirmed => Fix Committed
** Tags added:
Uploaded, pending approval from an archive admin.
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/287158
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.co
ACK
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/287158
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
https://lists.ubuntu.com/mailman/listinfo/ub
Thanks Pauli! I've prepared an SRU for this. MOTU SRU, please confirm.
** Attachment added: "intrepid.debdiff"
http://launchpadlibrarian.net/21728408/intrepid.debdiff
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/287158
You received this bug notification because
Fix for this crash is just a few lines change:
http://svn.gna.org/viewcvs/wesnoth?rev=29514&dir_pagestart=100&view=rev
I don't know much what has changed in 1.4.x. But I think for wesnoth it
would be reasonable to always upgrade to the latest stable version. Code
wise it there is only bug fixes bu
Not really. We want a Stable Release Update for a crasher, not a
backport. Task opened, will try to look into this soonish, but if you
can provide a diffstat and a diff of network_worker.cpp that would be
nice.
Gerfried, do you think it's reasonably safe to put 1.4.7 into Intrepid,
or we rather ch
Marking as fix released as this bug is fixed in the latest development
release of Ubuntu (Jaunty). I would recommend filing a backport request
to Ubuntu 8.10 and possibly Ubuntu 8.04 following these instructions:
https://help.ubuntu.com/community/UbuntuBackports#How%20to%20request%20new%20packages
I checked 1.4.7 with valgrind (calgrind was just a typo in previous
post) and there is no trace of race condition in disconnect any more.
Solution to this might be either to push 1.4.7 to intrepid or backport
network_worker.cpp. I don't know which one is preferred but both should
fix the crash pr
Could you try if this still happens with the version in jaunty for you?
There were quite some bugfixes incorporated since and no feature
changes, it's still 1.4 compatible version.
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/287158
You received this bug notificatio
For me this seems a lot like crash could happen because of race
condition in network threading code. (Happened for me when couln't
connect to addons server 3 times in a row)
calgrind report would be usefull if anyone wants to debug
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchp
** Changed in: wesnoth (Ubuntu)
Importance: Undecided => Low
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/287158
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@l
** Visibility changed to: Public
--
wesnoth crashed with SIGSEGV in malloc()
https://bugs.launchpad.net/bugs/287158
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
https://lists.u
18 matches
Mail list logo
