derLaie
Anmeldungsdatum: 16. März 2008
Beiträge: Zähle...
|
Da ich mich riesig gefreut habe, als ich sah, dass in Natty Narwhal FlightGear 2.0.3 als Standard-Paket vorliegt, war die Entäuschung umso größer, als es nicht lief.
Die Foren geben noch nicht viel her und meine Versuche die Fehler zu finden um dann eine Lösung zu posten verschlangen eben mal gerade zehn Stunden. Am Ende vieler langen Versuche stand immer noch:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133 | FGMultiplayMgr - No receiver port, Multiplayermode disabled
Nasal runtime error: props.setAttribute() with invalid attribute
at /usr/local/share/FlightGear/Nasal/props.nas, line 25
called from: /usr/local/share/FlightGear/Nasal/gui.nas, line 137
Not overwriting write-protected property /sim[0]/fg-root
Not overwriting write-protected property /sim[0]/startup/browser-app
Not overwriting write-protected property /sim[0]/sound/voices/host
Not overwriting write-protected property /sim[0]/sound/voices/port
Not overwriting write-protected property /sim[0]/fg-home
Not overwriting write-protected property /sim[0]/fg-current
Nasal runtime error: foreach enumeration of non-vector
at /usr/local/share/FlightGear/Nasal/view.nas, line 632
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 99
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 99
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 99
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 99
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 99
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 113
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Not overwriting write-protected property /instrumentation/mk-viii/outputs/discretes/gpws-warning
Not overwriting write-protected property /instrumentation/mk-viii/outputs/discretes/gpws-alert
Not overwriting write-protected property /instrumentation/mk-viii/outputs/discretes/audio-on
Not overwriting write-protected property /instrumentation/mk-viii/outputs/discretes/gpws-inop
Not overwriting write-protected property /instrumentation/mk-viii/outputs/discretes/tad-inop
Not overwriting write-protected property /instrumentation/mk-viii/outputs/discretes/flap-override
Not overwriting write-protected property /instrumentation/mk-viii/outputs/discretes/glideslope-cancel
Not overwriting write-protected property /instrumentation/mk-viii/outputs/discretes/steep-approach
Not overwriting write-protected property /instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-1
Not overwriting write-protected property /instrumentation/mk-viii/outputs/arinc429/egpwc-logic-discretes
Not overwriting write-protected property /instrumentation/mk-viii/outputs/arinc429/mode6-callouts-discrete-1
Not overwriting write-protected property /instrumentation/mk-viii/outputs/arinc429/mode6-callouts-discrete-2
Not overwriting write-protected property /instrumentation/mk-viii/outputs/arinc429/egpws-alert-discrete-2
Not overwriting write-protected property /instrumentation/mk-viii/outputs/arinc429/egpwc-alert-discrete-3
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 202
called from: /usr/local/share/FlightGear/Nasal/multiplayer.nas, line 378
called from: /usr/local/share/FlightGear/Nasal/multiplayer.nas, line 446
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 202
called from: /usr/local/share/FlightGear/Nasal/io.nas, line 210
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 202
called from: /usr/local/share/FlightGear/Nasal/gui.nas, line 376
called from: /usr/local/share/FlightGear/Nasal/aircraft.nas, line 519
called from: /usr/local/share/FlightGear/Aircraft/c172p/Nasal/liveries.nas, line 3
KI266 dme indicator #0 initialized
loading scenario 'nimitz_demo'
creating 3D noise texture... DONE
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 99
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 113
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 99
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 113
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 99
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 99
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Nasal runtime error: bad/missing argument to subvec()
at /usr/local/share/FlightGear/Nasal/string.nas, line 225
called from: /usr/local/share/FlightGear/Nasal/string.nas, line 235
called from: /usr/local/share/FlightGear/Nasal/failures.nas, line 99
called from: /usr/local/share/FlightGear/Nasal/globals.nas, line 100
Initializing Nasal Electrical System
power up
|
Mal gespannt, ob ich den Fehler vor euch finde... ☺
Bis dann,
derLaie P.S.
noch schöner, ich schalte morgen den Rechner ein und finde hier:
Die Lösung ist -$ sudo apt-get install fgfs --without-any-bug
|
derLaie
(Themenstarter)
Anmeldungsdatum: 16. März 2008
Beiträge: 7
|
Bisher habe ich nur einen Fehler beheben können.
Es sieht ganz danach aus, dass Ubuntu 11.04 die Soundkarte Multimedia audio controller: Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) einfach nicht mehr unterstüzt. Den Fehler... bt_audio_service_open: connect() failed: Connection refused (111)
...kann man beheben durch:
sudo apt-get purge bluez-alsa Aber weiter ... 😢
|
derLaie
(Themenstarter)
Anmeldungsdatum: 16. März 2008
Beiträge: 7
|
Leider immer noch nichts Neues.
Ich habe einen Dell Vostro 200 nun ausprobiert und siehe da... beinahe die selben Fehlermeldungen. Mesa 7.10.2 implementation error: Bad renderbuffer format: 21
Please report at bugs.freedesktop.org
FGMultiplayMgr - No receiver port, Multiplayermode disabled
Nasal runtime error: bad/missing argument to subvec()
at /usr/share/games/FlightGear/Nasal/string.nas, line 225
called from: /usr/share/games/FlightGear/Nasal/string.nas, line 235
called from: /usr/share/games/FlightGear/Nasal/string.nas, line 202
called from: /usr/share/games/FlightGear/Nasal/io.nas, line 210
Nasal runtime error: bad/missing argument to subvec()
at /usr/share/games/FlightGear/Nasal/string.nas, line 225
called from: /usr/share/games/FlightGear/Nasal/string.nas, line 235
called from: /usr/share/games/FlightGear/Nasal/string.nas, line 202
called from: /usr/share/games/FlightGear/Nasal/multiplayer.nas, line 378
called from: /usr/share/games/FlightGear/Nasal/multiplayer.nas, line 446
Nasal runtime error: props.setAttribute() with invalid attribute
at /usr/share/games/FlightGear/Nasal/props.nas, line 25
called from: /usr/share/games/FlightGear/Nasal/gui.nas, line 137
Nasal runtime error: bad/missing argument to subvec()
at /usr/share/games/FlightGear/Nasal/string.nas, line 225
called from: /usr/share/games/FlightGear/Nasal/string.nas, line 235
called from: /usr/share/games/FlightGear/Nasal/string.nas, line 202
called from: /usr/share/games/FlightGear/Nasal/gui.nas, line 376
called from: /usr/share/games/FlightGear/Nasal/aircraft.nas, line 519
called from: /usr/share/games/FlightGear/Aircraft/c172p/Nasal/liveries.nas, line 3
KI266 dme indicator #0 initialized
loading scenario 'nimitz_demo'
creating 3D noise texture... ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
bt_audio_service_open: connect() failed: Connection refused (111)
DONE
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Initializing Nasal Electrical System
Scaling image '/usr/share/games/FlightGear/Textures.high/Signs/black.png' from (4096,128) to (2048,128)
Scaling image '/usr/share/games/FlightGear/Textures.high/Signs/framed.png' from (4096,128) to (2048,128)
Scaling image '/usr/share/games/FlightGear/Textures.high/Signs/yellow.png' from (4096,128) to (2048,128)
Scaling image '/usr/share/games/FlightGear/Textures.high/Signs/red.png' from (4096,128) to (2048,128)
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
power up
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
i915_program_error: Bad source->Index: 12
Vorläufig also Finger weg von dem verrückten Wal, wenn man Flightgear zum Leben braucht.
Ansonsten ist es einfach mal wieder ein total schönes Betriebssystem.
|
derLaie
(Themenstarter)
Anmeldungsdatum: 16. März 2008
Beiträge: 7
|
Und wenn man den Plattform unabhängigen Audacity benutzen möchte: $ audacity
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.surround71
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.hdmi
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream
Cannot connect to server socket err = Datei oder Verzeichnis nicht gefunden
Cannot connect to server socket
jack server is not running or cannot be started
Expression 'ret' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1666
Expression 'AlsaOpen( &alsaApi->baseHostApiRep, params, streamDir, &self->pcm )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 1826
Expression 'PaAlsaStreamComponent_Initialize( &self->capture, alsaApi, inParams, StreamDirection_In, NULL != callback )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2088
Expression 'PaAlsaStream_Initialize( stream, alsaHostApi, inputParameters, outputParameters, sampleRate, framesPerBuffer, callback, streamFlags, userData )' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 2760
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4537
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4537
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4537
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4537
Expression 'stream->playback.pcm' failed in 'src/hostapi/alsa/pa_linux_alsa.c', line: 4537
Also scheint mit Natty Narwhal noch einiges im Argen zu liegen...
|
Alice_wtfiA
Anmeldungsdatum: 6. Januar 2011
Beiträge: 1292
|
Hej, Du könntest ja mal versuchen FlightGear ohne Soundwiedergabe zu starten:
Nasal ist eine eingebettete Programmsprache mit der die Modelleigenschaften der Flieger umgesetzt werden, also auch der Sound. Richtiges Unterforum wäre dann System einrichten und verwalten Sticky bitte lesen. Vermutlich genügt es, wenn Du Dir 'alsa-oss' nachinstallierst...
|
Alice_wtfiA
Anmeldungsdatum: 6. Januar 2011
Beiträge: 1292
|
Wie? Schon gelöst? Ohne Rückmeldung? Benutzt Du eigentlich für den Spielstart FGrun? Das steht seit ein paar Tagen über das PPA von Jacob in Ubuntu-Natty zur Verfügung... Netter Gruss Alice wtfiA P.S.: Nachträglich noch: ♥ -lich Willkommen im Forum!
|
derLaie
(Themenstarter)
Anmeldungsdatum: 16. März 2008
Beiträge: 7
|
Nicht gelöst... nur gefrustet. Aber vielen, vielen Dank für die Hilfe. Ich poste, wenn ich Neues zu berichten habe.
|
Alice_wtfiA
Anmeldungsdatum: 6. Januar 2011
Beiträge: 1292
|
Bekommst Du die Fehlermeldung auch noch, wenn Du Flightgear ohne Ton startest? (Befehlzeile für's Terminal s.o.) Wäre schon interessant, denn bei mir läuft es klaglos mit KDE in Natty und mit dem FlightGear-Launcher FGrun aus dem PPA. Hast Du 32 oder 64-bit installiert? Interessant ist, dass das der Bluetoooth-Dienst wohl im Standard aktiviert ist, und deshalb zu der einen Fehlermeldung führt.
|
derLaie
(Themenstarter)
Anmeldungsdatum: 16. März 2008
Beiträge: 7
|
Zuerst hatte ich noch einiges versucht. - wie von dir vorgeschlagen ohne Sound gestartet - andere Soundkarte eingebaut - war aber auch keine neue ☺ - mich durchgegoogelt bis zum einschlafen... - http://pastebin.com/g22g1MvM - http://forum.audacityteam.org/viewtopic.php?f=18&t=55662 - https://bugs.launchpad.net/nouveau/+bug/744456 (gar nicht schön, was es dort zu lesen gibt) - http://www.flightgear.org/forums/viewtopic.php?f=17&t=11929 Um zu sehen, ob es an meinem Rechner liegt habe ich einfach nochmal 10.04.2 LTS neu aufgespielt und zunächst Flightgear 1.9 per Synaptic installiert.
Das ging ...
Dann habe ich 10.04.2 LTS nochmal neu installiert und Flightgear 2.0 von Hand ohne
Synaptic installiert ... wie das eben ein total verrückter Narwal auch machen würde.
So lief es auch... inklusive FGRUN. Und dann wieder 11.04 ganz, ganz neu... - 32-bit Version 11.04 - sudo apt-get update - nvidia-settings - alsaplayer → funktioniert - subversion (wegen terrasync) - die Flightgear-Pakete aus Synaptic + Altlas - FGrun habe ich über die Paketverwaltung aus der von dir genannten PPA installiert. Und siehe da... da sind sie wieder ...
Sonst bin ich ja eigentlich immer beruhigt, wenn ich einen Fehler
reproduzieren kann, aber mir scheint, dass ich da nichts ausrichten kann. Nochmal von vorne - erste Zeile neue Fehlermeldung
Not overwriting write-protected property /sim[0]/fg-root
Not overwriting write-protected property /sim[0]/startup/browser-app
Not overwriting write-protected property /sim[0]/sound/voices/host
Not overwriting write-protected property /sim[0]/sound/voices/port
Not overwriting write-protected property /sim[0]/fg-home
Not overwriting write-protected property /sim[0]/fg-current
Wer möchte eigentlich die Ordner und Dateien anlegen und warum darf /sie /er das nicht? sudo find / -type d -name voices
...findet gerade mal einen Ordner /usr/share/espeak-data/voices
|
Alice_wtfiA
Anmeldungsdatum: 6. Januar 2011
Beiträge: 1292
|
Hallo nochmal, Danke für die Info. Vermutlich ist das Flightgear-Forum die Anlaufstelle, die am ehesten helfen kann. Allerdings werden die nix machen können, ohne Angaben zum Betriebssystem,Grafikkarte, usw.
Forum rules
In order to help you, we need to know a lot of information. Make sure to include answers to at least the following questions in your initial post. * what OS (Windows Xp/Vista, Mac etc.) are you running? * what FlightGear version do you use? * what graphics card do you have? * does the problem occur with any aircraft, at any airport? * is there any output printed to the console (black window)?
Terminalbefehle um die Angaben zu ermitteln: aplay -l (Ausgabe aller soundcards + digitaler audio devices) lspci -nnk | grep -i audio -A2 (noch etwas mehr Info zu Audio) dpkg -l flightgear (Deine installierte FlightGear Version) lspci | grep VGA (Ausgabe ermittelt Deine Grafikkarte / evtl. wäre der verwendete Treiber noch wichtig) Ist wie hier im Forum, je genauer und vollständiger die Angaben sind, umso grösser die Chance, dass jemand helfen kann. Netter Gruss
|
derLaie
(Themenstarter)
Anmeldungsdatum: 16. März 2008
Beiträge: 7
|
Ich habe einen Teil der Fehlermeldungen wegbekommen.
Die Nasal-Fehler aber noch nicht.
Mein Eintrag im flightgear-Forum findet man hier. http://www.flightgear.org/forums/viewtopic.php?f=11&t=11512&p=125032#p125032
|