Closed GoogleCodeExporter closed 9 years ago
ffmpeg should be in your path... you can override the location path but it's
better
to use the default supported by the program
Original comment by ps3mediaserver@gmail.com
on 25 Jan 2009 at 12:48
Cool story, ffmpeg is at /usr/bin/ffmpeg as said in the bug report.
/usr/bin is in my $PATH
And I can't override the location path without editing the source because I
can't see
the ui to change anything... As said in the bug report.
Original comment by code...@gmail.com
on 26 Jan 2009 at 2:21
actually the ffmpeg location is not at fault, it seems application does not
succeed
to parse output result from ffmpeg to determine its existence
Besides this has nothing to do with java empty window. It seems this happens
sometimes if you have enabled something like beryl or xgl on your linux. if
this is
the case, you have to set the following variable
export AWT_TOOLKIT="MToolkit"
Original comment by ps3mediaserver@gmail.com
on 26 Jan 2009 at 11:34
When I add that, it cycles the following error:
Jan 28, 2009 6:40:26 PM java.util.prefs.FileSystemPreferences
checkLockFile0ErrorCode
WARNING: Could not lock System prefs.Unix error code 32530.
Jan 28, 2009 6:40:26 PM java.util.prefs.FileSystemPreferences syncWorld
WARNING: Couldn't flush system prefs: java.util.prefs.BackingStoreException:
Couldn't
get file lock.
Which I researched, added the /etc/.java/.userPrefs or whatever it was dir, and
that
didn't help anything. Adding the LIBXCB_ALLOW_SLOPPY_LOCK=true didn't seem to
help
either.
As an aside, ln -s /usr/bin/ffmpeg ./ffmpeg and ln -s /bin/mkfifo ./mkfifo
fixed the
ffmpeg problem... so path has at least something to do with the ffmpeg errors.
Finally, I really like ps3media server, thanks for all your work on it. It's
the
best DLNA server out there, even with any weird bugs I'm seeing on x86_64.
Original comment by code...@gmail.com
on 28 Jan 2009 at 11:44
the first verifications have been disabled (too much troubles)
and the preferences API is now used only on Windows
Original comment by ps3mediaserver@gmail.com
on 26 Feb 2009 at 7:05
Original issue reported on code.google.com by
code...@gmail.com
on 25 Jan 2009 at 4:13Attachments: