SilverSurfer60

Right Jim. For the BBC site you need mplayer. Install mplayer-plugin for firefox and also install win32codecs. Now you should find in your /home/.mozilla/plugins all the plugins you need. This definitely works with the BBC I have just been and watched the news.

Not wishing to throw confusion in Jim but I always use helixplayer and real player codecs. It's listed in the mcc so you should have no problem installing it. I use that regularly for watching nasa tv. You can also have media player launch for windows formats just remember to install win32-codecs also in your mcc lists. I use both methods with little problem. If movie player is launching instead of media player then you will have totem player plugin in firefox. Remove it from your ./firefox folder in your home folder. You may well find that all will work as it should. Best of luck.

All your address book and your email messages are in your /home directory so they will be safe if you don't format it. Anything that's user orientated like that is usually in your home folder, including firefox stuff. Best of Luck and put it down to learning, I still do it so don't worry, you are not the only one.

Hello again JimTim. I totally agree with Greg2 on this one. Your system must be such a mish mash now that to help you help us to help you a new install of 2007.0 is a good idea. What I do in these cases when I wnat to do a clean re-install is copy my /home directory to a spare partition that I have and during install I can reformat both /root and /home just in case there i some gunge in there. After the re-install I copy back from the old /home into my new shiny /home things like documents, downloads etc. Basically data that I have put in there, that way all the config files will be refreshed. Unfortunately all the settings for 'Firefox' etc. I have to put in from scratch. Then I can safely delete the old /home directory once I have what I need from it. In fact this is what I will do when the official spring release is available. Go for it Jim re-install. :P

Always look on the bright side :P You have learnt quite a bit about mandriva linux. There's nothing like getting your hands dirty.

It would be worth a try. I cannot promise anything at this stage as I have not come across this before. It is strange behaviour. Best of luck. Report back with your results please.

Sorry I was ahead of you there. You need to open the kde control center -> regional & accessibility -> keyboard layout See if there is a checkmark in enable keyboard layouts. If there isn't one then kde will not be altering your keyboard codes. If there is one make sure that France is listed and first in the list in the main window and that Keyboard Model is the same as in xorg.conf. If all that checks out then I don't have anything further I can add, except if you take the re-install option then back up your home folder to another device and reformat the /home partition as well. You can always copy back into the new /home folder that will be created. This way if there is anything in your current home folder that is causing you the problem it will not be there when you re-install.

Don't worry that there is two xorg.conf that is quite normal, whenever mcc writes to this file it will often rename the orignal to xorg.conf.old The section you want to look at is :- Section "InputDevice" Identifier "Keyboard1" Driver "kbd" [b]Option "XkbModel" "pc105" Option "XkbLayout" "fr"[/b] Option "XkbOptions" "compose:rwin" EndSection Now check in KDE control center under location and make sure that the selections in there correspond. The ones in xorg.conf will be what you selected when installing mandriva.

The xkbd layout is in /etc/X11/xorg.conf and should be made to correspond to what you set in Kde Control Center. If any has been changed then it would be in KDE. Take note of what is in your keyboard layout in xorg.conf and make sure you have the same set in kde control center. You may need to set yourself a new root password. I hope this helps you.

Another question Jimtim did you have a reboot or something whilst installing katapult? If you did then you may well have a still lock on drakconf.real or something. It's possible to shutdown without clearing locks you see.

I think we may be getting somewhere now. There are two references to katapult in your list. By all means delete them, but don't delete a whole bunch of them they will be needed by other apps. However they should not give you any problems as they are only called on when needed. Rather like your dll in windows. Can you post a screen shot of the dialog box that requests your root password? You can aquire a snapshot by pressing 'Print Screen/SysRq' as this should bring up ksnapshot. You will know when you have it on screen, and, I'm sure you'll know what to do if it comes up. If the application does not launch you will need to install it. Take a snapshot of just the dialog box and post it. I'm curious to know if it is a standard dialog box or something else.

To put in very simple terms the 'key' verifies the rpm package is from whom it says is it is. Of cousre there is more to it than that. There is very detailed information if you google for 'rpm+key'.

It's not usually fatal to NOT have a key, but they are there for verification and normally present. I would still proceed as I suggest , that way you can rule it out of the equation. One can always re-install if it turns out not to be the problem. For me it would be niggling in the back of my mind, but then that's me. ;)

Well I've been googling around and find that katapult is an application that uses plugins for quick launch of other applications. I really do think this could be the cause of your problems. It may be worth your while un-installing katapult and delete any reference to it in your home directory and in the root directory. Root has a desktop folder as well as a root folder so there maybe references to katapult in any of these places. Also check in your /etc directory for a config file or something. You will need to do this whilst root in a console.

One thing you could try (as a shot in the dark) is change your root password via a console (terminal). Just incase you are not sure of how to do this, open a console and su to root then passwrd root On pressing enter you will be prompted for a new password and confirmation of the new password. On completion all your tokens will be updated. This will have the effect of clearing any botched tokens that you may have. Don't forget your new password See how that goes. Best of luck.

With your reply here I assume you logged in as a normal user. Would this be correct? If so then it's highly unlikely the keyboard translation is at fault. I say this because you would be using kde to log in. Is this just the root password that is affected in gui?

Are we seeing cracks appear in the ivory tower? What with all the legal wranglings, massive law suits and now issuing square peg software for round hole application. Even the giant can only stand so many losses before becoming vulnerable. Come on Linux I say.

Once again neddie you are correct, I tried it myself and uncompressed the files no problem, although it has to be done from the command line.

Of course you are right neddie. I failed to put my brain in gear before opening my mouth. That'll teach me to have a coffee before posting.

Hello bobmac, the file extension is incomplete. It could be either 'gz', or 'bz2' Try changing just the extender and see if you can unzip the file. Don't forget Linux is case sensitive, so the GZ is not equal to gz or Gz or gZ. They are all different. on a Linux system.

The ndiswrapper -i should have been ndiswrapper -l Sorry a bit difficult to distinguish. The '-i tries to install the driver you give, which in your statement is 'driver.inf' of course there will be no such file. The ndiswrapper -l will give you a list of drivers installed and tell you if the hardware is present. E.G. Installed drivers bcmwl5 driver Installed,hardware present If you do not get output like that then either the driver is not installed, the card has not been detected or ndiswrapper would appear to have been corrupted.

Could you also give the printout from 'ndiswrapper -l' please? That will give the list of drivers installed for ndiswrapper.

Unless anyone knows of a way to do this via software, and I cannot find anyway, it seems to be a hardware fix. This leaves a couple or three options. As I don't know your capabilities I would suggest buying an extension cable. These shouldn't be too hard to track down, and should not cost the earth to buy. If you cannot buy one and are capable make your own, this is not very challenging, unless you are physically challenged yourself (no rudeness intended here). Another option would be to split the existing cable and rejoin swapping the wires at the joint. This is a bit messy and so is not the preferred method. I cannot think further input for you so I hope I have been of help.

Perhaps a bit more info on your setup would help. You say you switched your speakers around. This gives the impression they are wired and separate from your 'puter. That was my understanding from the way you presented your question. Obviously I was wrong. :mellow:

If I may answer your question with a question like :- Would it be easier to switch the wires over? That's the way I would do the task. I don't know of a way to do it from the CLI.