Bug 57169 - Sometimes everything except units and facillities is black
Summary: Sometimes everything except units and facillities is black
Status: RESOLVED WORKSFORME
Alias: None
Product: boson
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: The Boson Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-12 23:29 UTC by Felix Seeger
Modified: 2004-01-23 19:46 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Seeger 2003-04-12 23:29:32 UTC
Version:           0.8 (using KDE 3.1.9)
Compiler:          gcc version 3.2.3 20030407 (Debian prerelease)
OS:          Linux (i686) release 2.4.20-rc4

Sometimes the map switches to black. I cannot see water, bombs, particles...
Only the units and the buildings.
Comment 1 Felix Seeger 2003-04-12 23:37:00 UTC
More Info: 
 
When this happens: 
 New units aren't visible (testet with transall) 
 Crash when win, not sure if related but last game (without black problem) there was not crash: 
 
[New Thread 16384 (LWP 21014)] 
0x41840b89 in wait4 () from /lib/libc.so.6 
#0  0x41840b89 in wait4 () from /lib/libc.so.6 
#1  0x418b4000 in sys_sigabbrev () from /lib/libc.so.6 
#2  0x41688061 in waitpid () from /lib/libpthread.so.0 
#3  0x40e1a9f8 in KCrash::defaultCrashHandler(int) (sig=11) at kcrash.cpp:235 
#4  0x417cd9d8 in sigaction () from /lib/libc.so.6 
#5  0x412f9024 in QDialog::accept() () from /opt/qt-copy/lib/libqt-mt.so.3 
#6  0x40bfcde8 in KDialogBase::slotOk() (this=0x92fbec0) 
    at kdialogbase.cpp:1089 
#7  0x40bff964 in KDialogBase::qt_invoke(int, QUObject*) (this=0x92fbec0,  
    _id=73, _o=0xbfffef00) at kdialogbase.moc:359 
#8  0x08122bff in GameOverDialog::qt_invoke(int, QUObject*) (this=0x92fbec0,  
    _id=73, _o=0xbfffef00) at gameoverdialog.moc:77 
#9  0x411bc336 in QObject::activate_signal(QConnectionList*, QUObject*) () 
   from /opt/qt-copy/lib/libqt-mt.so.3 
#10 0x411bc1f3 in QObject::activate_signal(int) () 
   from /opt/qt-copy/lib/libqt-mt.so.3 
#11 0x41448658 in QButton::clicked() () from /opt/qt-copy/lib/libqt-mt.so.3 
#12 0x41230bb4 in QButton::mouseReleaseEvent(QMouseEvent*) () 
   from /opt/qt-copy/lib/libqt-mt.so.3 
#13 0x411e989b in QWidget::event(QEvent*) () 
   from /opt/qt-copy/lib/libqt-mt.so.3 
#14 0x411680b2 in QApplication::internalNotify(QObject*, QEvent*) () 
   from /opt/qt-copy/lib/libqt-mt.so.3 
#15 0x4116796a in QApplication::notify(QObject*, QEvent*) () 
   from /opt/qt-copy/lib/libqt-mt.so.3 
#16 0x40d96b40 in KApplication::notify(QObject*, QEvent*) (this=0xbffff720,  
    receiver=0x92f0ac8, event=0xbffff2c0) at kapplication.cpp:459 
#17 0x411171c6 in QETWidget::translateMouseEvent(_XEvent const*) () 
   from /opt/qt-copy/lib/libqt-mt.so.3 
#18 0x41114dc9 in QApplication::x11ProcessEvent(_XEvent*) () 
   from /opt/qt-copy/lib/libqt-mt.so.3 
#19 0x41127e4c in QEventLoop::processEvents(unsigned) () 
   from /opt/qt-copy/lib/libqt-mt.so.3 
#20 0x4117972b in QEventLoop::enterLoop() () 
   from /opt/qt-copy/lib/libqt-mt.so.3 
#21 0x411795e8 in QEventLoop::exec() () from /opt/qt-copy/lib/libqt-mt.so.3 
#22 0x411682ac in QApplication::exec() () from /opt/qt-copy/lib/libqt-mt.so.3 
#23 0x08164f00 in main (argc=1, argv=0xbffff894) at main.cpp:125 
 
Comment 2 Rivo Laks 2003-04-13 16:07:39 UTC
I once had this problem when working on missiles. Some missiles had z-coordinate 
in infinity IIRC. When I fixed this, everything was normal again. No idea what exactly 
caused it though. 
 
Rivo 
 
Comment 3 Rivo Laks 2003-10-22 16:45:50 UTC
Is this still happening?
Few months ago or so, I had some problems with particles. They simply weren't rendered, even though rendering counts showed that they should be rendered. But lately, it hasn't happened anymore...

Rivo
Comment 4 Felix Seeger 2003-10-22 17:40:18 UTC
I had this some weeks ago.
Transall bomb might be the reason for this
Comment 5 Andreas Beckermann 2004-01-23 19:46:34 UTC
3 months without additional info and I've never faced this problem. I believe it has been fixed meanwhile, so I am closing this now. Please reopen, if it happens again.

CU
Andi