CrunchBang Linux Forums / Waldorf development images ready for testing

Re: Waldorf development images ready for testing

dummy@example.com (nonvolatile) — Fri, 03 Aug 2012 16:00:13 +0000

pidsley wrote:

You will get better help with these questions if you start a new thread in the Help and Support (Testing/Unstable) section.

Oh, I didnt know they existed, thanks...
http://crunchbanglinux.org/forums/post/247858/#p247858

Re: Waldorf development images ready for testing

dummy@example.com (pidsley) — Fri, 03 Aug 2012 15:37:41 +0000

You will get better help with these questions if you start a new thread in the Help and Support (Testing/Unstable) section.

Re: Waldorf development images ready for testing

dummy@example.com (nonvolatile) — Fri, 03 Aug 2012 15:27:03 +0000

I could use a little help and a hint in the right direction with my AMD HD graphic cards.
Id like to use Waldorf with fglrx, but Wheezy doesnt work with fglrx because the current xserver doesnt afaik. What do you recommend?
-Use Waldorf with fglrx with a fugly but stable hack (is there one?)
-Downgrade xserver (how?)
-Give radeon another try (then please tell me - how the heck do I get my two AMD graphic cards to work as a triple or quad head?! randr doesnt even see the cards and outputs, and xorg.conf hates me)
-Wait until fglrx works with Wheezy again (when?)
-Other solutions?
My primary goal is a stable multiple monitor Waldorf system.
I know Im asking many questions - Im not just lazy but just spent too many hours trying stuff and frustrated that windows is my only working system right now... Thanks in advance!

Re: Waldorf development images ready for testing

dummy@example.com (pvsage) — Fri, 27 Jul 2012 20:51:29 +0000

^ No, I often use it out loud, and in public. I've also used "B*eber" as a euphemism (dysphemism?) in public...

Re: Waldorf development images ready for testing

dummy@example.com (VastOne) — Fri, 27 Jul 2012 20:42:51 +0000

^^ And here I thought I was the only one who still used fugly in any context...

Re: Waldorf development images ready for testing

dummy@example.com (pvsage) — Fri, 27 Jul 2012 13:29:58 +0000

¡Gracias Hefe!

Re: Waldorf development images ready for testing

dummy@example.com (corenominal) — Fri, 27 Jul 2012 13:05:01 +0000

pvsage wrote:

Trying again in Waldorf; same problem, even if I've copied the file to /home/crunchbang on the LiveUSB. Same failure from command line. VLC acts as if I'm not enclosing the file name in double quotes.

crunchbang@crunchbang:~$ vlc "A Token of the Wreckage - Megan Slankard.mp4"
VLC media player 2.0.1 Twoflower (revision 2.0.1-0-gf432547)
Warning: option --plugin-path no longer exists.
Warning: option --plugin-path no longer exists.
[0x94118f0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[0x944dec0] filesystem access error: cannot open file /home/crunchbang/A (No such file or directory)
[0x944edd8] main input error: open of `file:///home/crunchbang/A' failed
[0x94800e8] filesystem access error: cannot open file /home/crunchbang/Token (No such file or directory)
[0x944dec0] main input error: open of `file:///home/crunchbang/Token' failed
[0x94832f8] filesystem access error: cannot open file /home/crunchbang/of (No such file or directory)
[0x947ffb8] main input error: open of `file:///home/crunchbang/of' failed
[0x9483948] filesystem access error: cannot open file /home/crunchbang/the (No such file or directory)
[0x94831e8] main input error: open of `file:///home/crunchbang/the' failed
[0x94832f8] filesystem access error: cannot open file /home/crunchbang/Wreckage (No such file or directory)
[0x947ffb8] main input error: open of `file:///home/crunchbang/Wreckage' failed
[0x94833f8] main stream error: cannot pre fill buffer

If "/path/to/Video File.ext" is renamed to "/path/to/VideoFile.ext", VLC opens it just fine.

crunchbang@crunchbang:~$ vlc "ATokenoftheWreckage-MeganSlankard.mp4"
VLC media player 2.0.1 Twoflower (revision 2.0.1-0-gf432547)
Warning: option --plugin-path no longer exists.
Warning: option --plugin-path no longer exists.
[0x9d108f0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.

Perhaps this is an old bug that has been fixed since Philip built the Waldorf Live images?

EDIT: Also, VLC in Waldorf *does* open files with spaces and special characters properly when selected from the open file dialog...

Hmm, I think I may know what is causing this. There is/was a known bug with VLC where it would fail to start in a live environment. To fix this, I created a fugly wrapper script for the binary, but I think I probably forgot to wrap the arguments in quotes.

Sorry

Re: Waldorf development images ready for testing

dummy@example.com (pvsage) — Fri, 27 Jul 2012 12:49:34 +0000

So...are yous guys saying nobody else here can replicate this VLC bug in the Waldorf AMD64 LiveISO? If those with Waldorf 64-bit installed cannot replicate, I suppose that means this was an upstream bug that has been fixed...web search verifies that this is an old bug with VideoLAN across platforms that keeps popping up again...

Re: Waldorf development images ready for testing

dummy@example.com (pvsage) — Thu, 26 Jul 2012 20:07:42 +0000

Safely-ejecting charging Rockboxed iPod...running out cat5e cable (Waldorf doesn't work with my wifi dongle)...rebooting...

@Wolfy: Nope, images with spaces open with no problems in viewnoir; same with PDF and text files (with spaces in filenames) in evince and Geany...

EDIT: ytpo. Also, apologies for sounding snippy in that first paragraph; mostly I'm annoyed with myself for backing the wrong horse with that wifi dongle.

Re: Waldorf development images ready for testing

dummy@example.com (mariannemarlow) — Thu, 26 Jul 2012 15:29:48 +0000

machinebacon wrote:

@marianne: this is just a hint that vlc can be opened without GUI if needed.
@pvsage: shot in the dark: is the drive written in fstab or hotplugged? If in fstab, you could add options like nls=utf8 or something - maybe compare waldorf's fstab with that of statler? The problem seems to be the space in the filename, just like backslashes or asteriks make troubles.

Yes (I know I googled it) just wanted to know if it had been tried.

Re: Waldorf development images ready for testing

dummy@example.com (machinebacon) — Thu, 26 Jul 2012 15:28:57 +0000

@marianne: this is just a hint that vlc can be opened without GUI if needed.

@pvsage: shot in the dark: is the drive written in fstab or hotplugged? If in fstab, you could add options like nls=utf8 or something - maybe compare waldorf's fstab with that of statler? The problem seems to be the space in the filename, just like backslashes or asteriks make troubles.

Edit: nls=utf8 is not needed if you use ntfs-3g, by the way.

Edit #2: just saw your edit

Re: Waldorf development images ready for testing

dummy@example.com (SabreWolfy) — Thu, 26 Jul 2012 15:25:45 +0000

@pvsage: Is it just VLC that chokes on filenames with spaces in your test environment? Or is it more general, which would mean the problem may lie elsewhere.

Re: Waldorf development images ready for testing

dummy@example.com (mariannemarlow) — Thu, 26 Jul 2012 15:19:45 +0000

I am probably way off - I usually am but what happens when you type

 cvlc "A Token of the Wreckage - Megan Slankard.mp4"

as it says

Use 'cvlc' to use vlc without interface.

Re: Waldorf development images ready for testing

dummy@example.com (pvsage) — Thu, 26 Jul 2012 15:03:38 +0000

crunchbang@crunchbang:~$ vlc "A Token of the Wreckage - Megan Slankard.mp4"
VLC media player 2.0.1 Twoflower (revision 2.0.1-0-gf432547)
Warning: option --plugin-path no longer exists.
Warning: option --plugin-path no longer exists.
[0x94118f0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.
[0x944dec0] filesystem access error: cannot open file /home/crunchbang/A (No such file or directory)
[0x944edd8] main input error: open of `file:///home/crunchbang/A' failed
[0x94800e8] filesystem access error: cannot open file /home/crunchbang/Token (No such file or directory)
[0x944dec0] main input error: open of `file:///home/crunchbang/Token' failed
[0x94832f8] filesystem access error: cannot open file /home/crunchbang/of (No such file or directory)
[0x947ffb8] main input error: open of `file:///home/crunchbang/of' failed
[0x9483948] filesystem access error: cannot open file /home/crunchbang/the (No such file or directory)
[0x94831e8] main input error: open of `file:///home/crunchbang/the' failed
[0x94832f8] filesystem access error: cannot open file /home/crunchbang/Wreckage (No such file or directory)
[0x947ffb8] main input error: open of `file:///home/crunchbang/Wreckage' failed
[0x94833f8] main stream error: cannot pre fill buffer

If "/path/to/Video File.ext" is renamed to "/path/to/VideoFile.ext", VLC opens it just fine.

crunchbang@crunchbang:~$ vlc "ATokenoftheWreckage-MeganSlankard.mp4"
VLC media player 2.0.1 Twoflower (revision 2.0.1-0-gf432547)
Warning: option --plugin-path no longer exists.
Warning: option --plugin-path no longer exists.
[0x9d108f0] main libvlc: Running vlc with the default interface. Use 'cvlc' to use vlc without interface.

Perhaps this is an old bug that has been fixed since Philip built the Waldorf Live images?

EDIT: Also, VLC in Waldorf *does* open files with spaces and special characters properly when selected from the open file dialog...

Re: Waldorf development images ready for testing

dummy@example.com (pvsage) — Thu, 26 Jul 2012 14:23:26 +0000

Well, they open fine in Statler...