SilverSurfer60

:lol: :lol: :lol: ROFL

You will find the log files in /var/log and you will need to su root to gain access. Two files will be of interest and they are messages and syslog. Both are quite long but if you look for reference to your softphone usage you may find something. The forum address I was talking about before is http://www.nabble.com/Ekiga-f1245.html if you want to give that a try. I have just fired up Ekiga and logged into my accounts without any problems. I can't use it though because I am behind that BT Home Hub and they won't let me use any other softphone without putting my machine into a DMZ.

Have you had a look through the logs Mitchell? Maybe something in there that could help. Also there is forum type website for Ekiga 'Nabble' something or other like that. I think there is a link in the app help menu. It is a text only website but is very useful. I'll try and look up the address for you when I get home.

If I follow your description correctly Dexter, instead of cropping to your selection you should select clear from the edit menu. Then you can select what you need, and copy it. Then create a new image and select from options (or whatever it is) to have the background as transparent instead of background colour, Then paste your copied image from your first selection. That should give you the required result I think. I hope all that makes sense to you. :unsure:

Just to let you know that someone is reading your post. I can't answer your question. I did use Ekiga for quite a while on mandy 2006 with little or no problem. Have not used it quite a while.

What's wrong with Helixplayer & Real-codecs I ask? :mellow: I use that combination quite often to watch streaming video (NASA tv). It's the only one that keeps the audio in sync with the video, fully resizeable and very rarely fails for me. For audio I use xmms player, only because I'm used to it and it doesn't seem to hog resources.

That used to happen with Beryl. Never bothered about it as it was only the splash.

Well I have just tried it and my set up works just fine. I have mplayer mozilla-plugin installed with win32codecs, selected from the player preferences to play with windows media and off she goes. It did take a few seconds to begin but it worked fine. Tried it with realplayer but it fell over with that. Running Firefox by the way.

If it is the word 'Menu' you want to get rid of then right click on the button and select one of the optional styles of button you want. One option is 'Switch to Mandriva Button' This will give you a white star on a light blue background.

It has been my experience that when using 'metese' that as you say when logging off the only option is to end current session, but if using 3d cube then all options are shown for logging off. It has been this way for me from the introduction of 3d Desktop. Metese is a gnome desktop whereas 3d cube is kde, and I think gnome handles these things differently.

Just to add my twopenneth best release I've had the pleasure of installing. Give all the guys and gals a pat on the back.

The one I use most is kdenlive.It needs more than a few clicks but does a darned good job at editing film strips.

It'd be a lot less bother changing the wife me thinks. :P

In that case the cpu is a good suspect. Let us know how you get on with the one you have in now please. I know I will get Nah Nah told you so from persons, but that's life. :P

Just to clear things up a little, have you run this pc on windows without freezing?

I beg to differ about a dodgey keyboard plug as I have one myself. Occasionally and very rarely my computer will freeze. A reset will clear the problem but it will freeze quite son after, only when I have seated the keyboard plug in its socket correctly will it perform for some time. Sorry but I have experience of this happening.

I will agree that it could well be hardware, but my way of thinking is it's much cheaper to rule out any software glitches first. It's all well chucking new hardware at the computer and still not hit the right fault. It could be as simple as the keyboard plug rocking in it's socket that will freeze up, so would a mouse cable. Do you see where I'm coming from?

Your Linux knowledge level is going up here. The next time your system freezes make a note of the time. After rebooting, start up your Konsole and type in su root when prompted enter your root password. As I'm not sure of your level of confidence stick to these instructions as once logged in as root you can quite easily trash your system. Type in your Konsole less /var/log/messages this will bring up the contents of another logfile. I use this method for displaying logfiles because it is easier to search through the file by using the page up and down keys. Now look through this very large file for the time when your system froze and you restarted. Around this point in your logfile before you crashed it should tell you what the system was doing and maybe tell you of an instruction that could not be handled. Cut and paste into your next reply about 20 lines of the contents of your logfile before and including the time of the crash, then we can have a look and maybe spot the problem. Close the konsole after doing this. If you have the confidence and see what is causing the problem by all means fix it. As ever in Linux there is more than one way to do some things so don't be surprised if someone else comes up with another solution for you.

Sorry didn't realize you were a noob, that was my oops!. The safest way for you to access the logs is through the mandriva control panel, also known as mcc. Select from your menu 'Configure Your Computer' and when prompted enter your root user password. Once the Control Panel has appeared on screen select 'system' then select from the options 'view and search system logs'. The log file that we are interested in is called 'syslog'. Search through this log, it is a text log and can be rather long. Look for a place in this log where you restarted your 'puter after a crash. You will get the idea after looking at the log for a while. Having found where the crash happened, look back through the log a few lines and look for an entry with oops! in the line. Paste a few lines either side of this entry in a reply and let's see what it says. If you can't find an oops! paste a few lines either side of the crash and restart anyway.

Is there anything in the logs just prior to the time of the crash? In particular look for an oops!

Could you also give us more information as to your set-up? Computer type PC, Laptop etc.

or this way apachectl start This is how I do it after editing the httpd.conf.

Dunno about your problems with k3b, but I use qdvdauthor for my authoring of dvd discs and finish off with k3b to do the burning. qdvdauthor gives me everything needed to create a title page with full menus etc. Give that a whirl.

For some reason k3b gets put under system->archiving->CD burning on the menu. That's on my 2007.1 install

I've been using kdenlive for creating captured movies from tv, cutting out all the adverts etc. and rearranging the titles. It's pretty good IMHO a bit lacking in the transition department, but it's still under development. It most certainly will output DVD format and a bunch of others. Not sure about ripping though, I'll let someone else come in on that. Just remembered k3b will do the ripping for you. I've never used it so I can't vouch for it.