interesting gmplayer behavior

DJOtaku · 08-12-2005, 08:17 AM

like a lot of other people here on the forums (yup, I did my research) I am getting the error of

Code:

"Linux RTC init error in ioctl (rtc_irqp_set 1024): Permission denied
Try adding "echo 1024 > /proc/sys/dev/rtc/max-uer-freq" to your system startup scripts

as well as

Code:

mplayer: could not connect to socket
mplayer: No such file or directory

But here's the really weird part:

If I launch gmplayer as

Code:

gmplayer&

It loads up the window and control panel, but the program is frozen. I can't use it and clicking on the "X" (in Gnome) does not close it. The only way to cause it to quit is a level 9 kill.

If I launch it as

Code:

gmplayer

Then everything works all perfectly. I can watch video files, listen to music, etc

Does anyone know what the heck is going on here? What difference does the & make? For me, it means being able to continue in the command line with other things, but what could it possibly mean to gmplayer?

And does the 1024 error have something to do with it?

Thanks,

biophysics · 08-12-2005, 09:36 AM

If you use gmplayer in command line you must not give '&' symbol.

As you might have seen when (g)mplayer is running it provides status line so do not put '&' in command line.

1. you can ignore the rtc error. It is not an error. Just that real time clock is not accessible.
if you dont want that message add the following to the command line:
-nortc

From mplayer man page: Turns off usage of the Linux RTC (realtime clock - /dev/rtc) as timing mechanism.

2. The next message (as error) can also be ignored.

DJOtaku · 08-12-2005, 09:56 AM

hey, thanks a lot! All this time I thought my mplayer was broken til I accidentally didn't use a &.... hehe...

Thank you!