Even aside from the issue of responsibility (game or WM), freedoom is
merely a lump of world data and does not draw any windows at all. The
window drawing is performed by an engine, most likely prboom.
** Changed in: freedoom (Ubuntu)
Status: New = Invalid
--
Window games should start in
freedm is calling whatever is providing /usr/games/boom on your
system, most likely prboom, and that is crashing. Freedoom and freedm
are essentially just game data, but they also carry a small shell script
(/usr/games/freed{oom,m}), a .desktop file, icon etc.
Please confirm which package is
P.S. I'd wager that you are experiencing
https://bugs.launchpad.net/ubuntu/+source/prboom/+bug/375498
--
freedm crashes after starting
https://bugs.launchpad.net/bugs/514454
You received this bug notification because you are a member of
Debian/Ubuntu Games Team, which is subscribed to freedoom
Relevant log excerpt:
Setting up rott (1.0+dfsg-2) ...
Gtk-WARNING **: Theme directory 256x256/emblems of theme Industrial has no
size field
dpkg: error processing rott (--configure):
subprocess post-installation script returned error exit status 1
If the Gtk-WARNING has been
At the moment, Fabian and I are working on implementing rott support in
game-data-packager. It should be quite trivial for us to extend that
support to the commercial data. One issue though is I do not currently
own a copy of the game. It looks like it can be bought from 3drealms.com
for about
*** This bug is a duplicate of bug 375498 ***
https://bugs.launchpad.net/bugs/375498
Fairly sure that this is a duplicate. Try the fixed package from
Maverick: 2:2.5.0+dfsg1-5ubuntu1
http://packages.ubuntu.com/maverick/prboom
** This bug has been marked a duplicate of bug 375498
prboom
Ing. Forigua, please read the bug description more carefully. Your
output does not match the behaviour in this bug. Your problem looks
more like https://bugs.launchpad.net/ubuntu/+source/prboom/+bug/375498 ,
which has been fixed in a package version for Maverick.
--
[apport] prboom crashed
Jeroen, I don't know what problem you are referring to but version
1.9-1.1 in all versions of Ubuntu carry doom1.wad (lowercase) and
version 1.9.fixed-2 in Debian also carry doom1.wad (lowercase). Your
problem is something else and not related to this bug.
--
wrong version is packaged: 1.8 not
*** This bug is a duplicate of bug 636050 ***
https://bugs.launchpad.net/bugs/636050
** This bug has been marked a duplicate of bug 636050
package freedoom 0.6.4-1 failed to install/upgrade: sub-processo script
post-installation instalado retornou estado de saída de erro 2
* You can
The fixed package is in Natty at least. I've marked the bug fix
released accordingly.
** Tags added: maverick
** Changed in: doom-wad-shareware (Ubuntu)
Status: New = Fix Released
--
You received this bug notification because you are a member of
Debian/Ubuntu Games Team, which is
Sorry I realise my response here was a bit curt. There is an existing
request for package for prboom-plus in Debian at
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559132 . I do not have
the time to take on any more doom packages, but I would be happy to
sponsor/mentor someone who was
Hi, thanks for the report. This is likely a local configuration with
your quake3 engine of choice (ioquake3) and not an issue with your data
package nor with game-data-packager. It would be helpful for further
diagnosis if you could report whether you get a different framerate with
different data,
Can you try either prboom or chocolate-doom with the '-nofullscreen'
command-line option? My hunch is the problem is related to trying to
change the display resolution whilst entering fullscreen mode.
It's likely actually an SDL1 bug. In Chocolate Doom's case, we are
moving to SDL2 with the next
13 matches
Mail list logo
