1.0.4-1 has landed in Saucy and seems to start up and run in my Saucy VM
ok.
Having said that I just get a blackscreen on my main AMD/ATI graphics
main machine - but whatever, that's a different bug fromt his one.
** Changed in: barrage (Ubuntu)
Status: Triaged => Fix Released
--
You rec
** Changed in: barrage (Debian)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008011
Title:
Barrage does not open - crashes with SIGABRT
To manage notifica
** Changed in: barrage (Debian)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008011
Title:
Barrage does not open - crashes with SIGABRT
To manage notifications abo
The attachment "Fix the name field in the menuentry" of this bug report
has been identified as being a patch. The ubuntu-reviewers team has
been subscribed to the bug report so that they can review the patch. In
the event that this is in fact not a patch you can resolve this
situation by removing
** Changed in: barrage (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008011
Title:
Barrage does not open - crashes with SIGABRT
To manage notifications about
bah, after writing that fix I noticed it was already fixed in 1.04
upstream (but not in Debian yet)
** Bug watch added: Debian Bug tracker #696562
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696562
** Also affects: barrage (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=
Here's a fix; it was carefully snprintf'ing with a limit of 24 into a 20
char buffer - and then terminating at 23 chars for good luck.
** Changed in: barrage (Ubuntu)
Status: Confirmed => Triaged
** Patch added: "Fix the name field in the menuentry"
https://bugs.launchpad.net/ubuntu/+s
This issue is still reproducible on Ubuntu Raring. Barrage ran fine on
my Debian Sid system though, so it looks like this is likely an Ubuntu-
specific issue.
** Tags added: quantal raring
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
** Description changed:
- Barrage does not open. A window pops open, and then a SIGABRT from a
- raise in /lib/x86_64-linux-gnu/libc.so.6 crashes the program.
+ Barrage does not open. A window pops open. Then a SIGABRT is raise()'d
+ from /lib/x86_64-linux-gnu/libc.so.6, crashing the program.
Medium-> A bug that has a severe impact on a non-core application.
** Changed in: barrage (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008011
Title:
Ba
Yep, I get the same:
dg@major:~$ barrage
BARRAGE v1.0.3
Copyright 2003-2010 Michael Speck (http://lgames.sf.net)
Released under Gnu GPL
---
main loop delay: 0 ms
loading /usr/share/games/barrage/gfx/ground.bmp ... ok
loading /usr/share/games/barrage/gfx/particles.bmp ... ok
loading /usr/share/game
** Tags added: precise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008011
Title:
Barrage does not open - crashes with SIGABRT
To manage notifications about this bug go to:
https://bugs.launchpad
12 matches
Mail list logo
