Thanks for this additional information. I was able to verify it now.
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
To simulate it you have to be a registered bzflag user. If I remember correctly
it doesn't
crash with a not-registered user.
Create an account on the official forum : http://my.bzflag.org/bb/ .
You should use the callsign/password provided there in your bzflag client to
connect
to a server.
I'm unable to verifiy the crash on a stock edgy install. This is
important for the sru-verificaton step. Do I need to connect to a
special server?
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It's random. Sometimes it would happen if I reconnected to a server,
but try four or five times in the same session and it should eventually
crash.
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
See bug #73447 for SRU request.
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Correction. Meant to say fix fixed in Feisty. An SRU is in progress for
edgy.
** Changed in: curl (Ubuntu)
Assignee: (unassigned) = Cody A.W. Somerville
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Rejecting bzflag: This is a bug in curl, not bzflag.
** Changed in: bzflag (Ubuntu)
Status: Confirmed = Rejected
** Bug watch added: SourceForge.net Tracker #1523466
http://sourceforge.net/support/tracker.php?aid=1523466
** Also affects: curl (upstream) via
Curl will be broken in edgy forever without SRU request. For SRU request
new bug report must be filled.
https://wiki.ubuntu.com/BugWorkflow?highlight=%28fix+committed%29:
Fix Committed: A fix has been included in the code, but this code is not
necessarily available in a released version.
--
From: Jari Sundell sundell.software_at_gmail.com
Date: 2006-07-16
On 7/16/06, Jari Sundell [EMAIL PROTECTED] wrote:
On 7/16/06, Jari Sundell [EMAIL PROTECTED] wrote:
Having looked at the splay code, I think the implementation could have
been cleaner and more robust.
The attached patch
On Mon, 27 Nov 2006, Cody A.W. Somerville wrote:
Please remove me as CC for this bug. This is not a bug in any recent curl,
but a bug in your version of curl and we (in the curl project) fixed it a long
time ago.
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs
Fixed in Edgy. Please file new bug report for sru.
Daniel: This should be the last e-mail you get.
** Changed in: curl (Ubuntu)
Status: Confirmed = Fix Released
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
This is still broken in Edgy and will be broken until Curl 7.15.5 is
available for general use.
This bug *needs* to be reopened.
As a workaround (for people that find this bug) I downloaded the source
and diff from the Feisty page for 7.15.5-1ubuntu1 and compiled the
packages for edgy. bzflag
curl still broken in edgy, re-opening
** Changed in: bzflag (Ubuntu)
Status: Fix Committed = Confirmed
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Steps to reproduce:
* Start bzflag -solo 5
* start server
* trying to connect
* crashes
** Attachment added: crash report (complete)
http://librarian.launchpad.net/5136223/_usr_games_bzflag.1000.crash
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs
Changing curl bug status to fix committed, because fix is in curl CVS.
** Changed in: curl (Ubuntu)
Status: Unconfirmed = Fix Committed
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Changing bzflag bug status to fix committed, because bug was in curl and
fix is already in the CVS of curl
** Changed in: bzflag (Ubuntu)
Status: Confirmed = Fix Committed
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
** Changed in: bzflag (Ubuntu)
Assignee: ville palo = (unassigned)
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Comments from upstream:
This looks like a libcurl bug, please refer it to them.
As a workaround, use an older version of libcurl.
** Also affects: curl (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs
More info from upstream:
It seems this issue has been raised with libcurl team before at
http://sourceforge.net/tracker/index.php?func=detailaid=1523466group_id=976atid=100976
According to the thread it may have been fixed in cvs.
--
Seg fault when connecting
https://launchpad.net/bugs/68074
** Changed in: bzflag (Ubuntu)
Assignee: (unassigned) = ville palo
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Happens on my edgy too, status changed to confirmed
** Attachment added: crashdump
http://librarian.launchpad.net/4939102/_usr_games_bzflag.ywOxrq.crash
** Changed in: bzflag (Ubuntu)
Status: Unconfirmed = Confirmed
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
Forwarded to upstream:
http://sourceforge.net/tracker/index.php?func=detailaid=1586194group_id=3248atid=103248
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
problem is the same.
ubuntu is edgy.
it happens about 4 times out of 5.
** Attachment added: apport trace
http://librarian.launchpad.net/4938265/_usr_games_bzflag.1000.crash
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
sorry, forgot: it just appeared a few days before edgy became non-beta. (i used
the beta one)
before it worked perfectly.
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
It seems to be something related to CURL...
** Attachment added: GDB Backtrace
http://librarian.launchpad.net/4934107/gdb-bzflag.txt
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
In Kubuntu edgy
no crash for me (i have a ati FireGL8800i and I use opensource 3d ati
drivers (r200))
--
Seg fault when connecting
https://launchpad.net/bugs/68074
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
26 matches
Mail list logo
