Code::Blocks "process terminted with signal 255 (0 minutes, 0 seconds)"

Yesterday after I came home from work I thought I'd try working on a project I've been working on this past weekend.
I was away from home this weekend, so all the work I'd done had been on another computer, in a virtual Ubuntu installation, so I hadn't yet tried it at home.

Trying to build it went fine. Running it from a terminal went fine. Even compiling and running on another Ubuntu installation (my work laptop, non-virtual) went fine, but Code::Blocks reported to me that whenever I tried running my application on my Fedora 11 home installation that it terminated with signal 255.
I couldn't find what was wrong, I knew the application worked since I tested it in another terminal window and if I debugged it it'd go great up to the point where it met with a cin or cout.
Being tired from a really long day (getting up at 5:00am, get on train at 6:25am, get off train at 8:30am and at work 8:50am), I gave up fairly quickly.

This morning though the itch got worse and I just had to investigate further.
After about a minute of looking around I found someone at the Ubuntu Forums asking about the exact same thing and it turns out that the problem was that xterm wasn't installed. So a simple

su -c "yum install xterm"

was enough to fix the problem.

Now I can start developing my application again!

Low Resolution in Fedora 11 with Nvidia drivers

Finally, after hours of looking and working I have finally again found how to set the resolution to what I need (have 1280x1024, had 640x480). I've had trouble with my resolution in Fedora before, but I don't ever remember it being this much of a pain, but then again I don't remember much about it at all, wish I'd remembered how I fixed it.
So to help me remember and perhaps even help someone else work around it, here's how I finally got it working.

I'm now using the Nouveau driver with a generic LCD Panel 1280x1024. I tried setting this in

system-config-display

many times, but it just wouldn't accept my monitor.
So in the end I looked at

system-config-display --help

and noticed

--reconfigure

, which doesn't base the new configuration file on an old one.
Using this option and setting my driver to nv and my monitor to generic 1280x1024 and then

su -c "init 3"
[log in]
su -c "init 5"

got me the right resolution again. However the nv driver is just a little too basic, so I thought I'd try the same thing with the proprietary driver, so I did everything exactly as before, only I used the driver nvidia instead of nv.
Now again X wouldn't start at all, so I ran

livna-config-display -a

to get it to my old low-res configuration, and then I tried it a third time, this time using the nouveau driver (which I've heard is better then nv) and that worked!

I know that supposedly you're also able to use xorg.conf to set certain Modes values for your display, but this didn't do anything for me at all in fedora, did help me in ubuntu, but then there I got the weirdest resolution.

finally I can look at a normal screen again.

Now I should get going to work, I'm gonna be really late (this really bugged me!)

Convert .VOB to .WMV with ffmpeg in Linux

A fairly simple command gets the job done:

ffmpeg -i filename.vob -vcodec wmv2 -acodec wmav2 -sameq -s 720x576 filename.wmv