mandrivsen

Thank you very much, (It is called Window List). That fixed it! :) :) :)

I am not using KDE but GNOME instead. After rebooting I got a message that an application list could not be recovered I answered NO to the question Reload (y/n) since it kept failing to retrieve it. Now whenever I minimize an application window it disappears into the nowhere-land, and it does not appear on my panel, at the bottom. Most of the minimized applications are accumulating inaccessible beyond my reach, and no way to reactivate them! I checked ".gconf/apps/panel/toplevels/" directory for another user where it is working and I noticed that ".gconf/apps/panel/toplevels/bottom_panel/%gconf.xml" was missing todether with its directory "bottom_panel". I created the missing things, they are now identical for both users, of course also the ownership is correct. However, this did not change anything! I remember this already happened to me once, and I had to reload the OS and my of course all my data and configurations. This is almost prohibitive at this point! Does anybody know how to solve this problem. [moved from Software by spinynorman]

Thank you guys. I became a kind of a purist, and this time around didn't install KDE. As soon as I saw the "Kname", I knew what the problem was. I installed the missing program from the DVD. Thank you again! :D

I do not remember the spelling of its name. But it was part of Multimedia->Graphic, and enabled you to make an image of the entire screen. :P

I've updated my Mandriva and a few programs have disappeared. At this point I discovered that snapshot is missing. Can you please tell me if there is a way to install it again?

Thx dexter11, this fixed it! :P

My earlier Mandrake release was installed with Unicode as a default. However, when I recently installed new Mandriva release, on the very first installation screen "Language choice" I forgot to check the box "Use Unicode by default". Unfortunately gedit does not display files written with UTF-8 locale is not displayed correctly, and worse, if I modify or add text to old files, they can no longer be saved. I get the message Could not save file xyz; Invalid byte sequences in conversion input Is there a way to change my locale to be defined as Unicode (UTF-8) again. I would like to avoid reinstalling the system.

Perhaps this may also help you all? Fixing or misconfiguring your keyboard settings If you set up your computer for a multilingual use, you can change your keyboard layout (nationality) on a fly by a single click on your Desktop panel. The keyboard setting effects all applications currently opened on the desktop. I have noticed that this "keyboard type" selector setting may easily be misconfigured. I found it beneficial to use the "Keyboard Indicator" not only to toggle between different keyboards, but also to check that keyboard setting is not misconfigured. Namely, when two or more languages are set up, and you can not toggle between them, you can fairly conclude that keyboard setting is indeed misconfigured. When this is the case, to correct the problem you should set the default settings in your "Keyboard Preferences" window, which will remove all but system default keyboard from the "Keyboard Preferences". After that add those that were removed without checking any check-boxes beside them, or even worse, moving them to different positions by clicking either Up or Down buttons. These actions may very well be using a buggy procedure, because they prevent the toggle functionality, rather than merely change which keyboard should always be used as the default.

Jimtim, it looks, that your keyboard type is defined differently in either environment; (i.e: Generic 101-key PC, Generic 104-key PC, Generic 105-key (Intl) PC...). Somebody should help us find out how to determine what is your keyboard setting for console (text-screens). In GUI it is easy, to manage the keyboard. You can go to Preferences->Keyboard to check it out, but do not change anything as yet. I tried to decipher which of your keys behave differently, and can tell you with certainty that the following keys cause problems: right parent / parenthesis ..... ) dollar sign .................... $ percent ........................ % asterisk ....................... * exclamation .................... ! However, there are five more keys, which I can not identify. Without understanding which keys behave differently, is hard to do the quick fix, whereby you should reset your root password using only the keys that are the same in either environment, which is easy when you use bilingual system, where you usually know which keys are different in each. However, your's is the case of misconfiguration as it seams. I will give you the suggestion for the quick fix, if nobody is able to help you out from this point on. Note that that will not solve your problem with the keyboard, but I'm pretty sure we could fix your password.

Jimtim, no need to apologize, not everybody is so paranoid about images as I am! :o :D Obviously, your keyboard output in GUI is different than on the consoles <Ctrl+Alt+Fn> screens. My first guess is that some of your the "mode keys" {Alt, Shift, ...} and perhaps even <Enter> i.e. white-space characters and invisible behave differently in the two environments. I think the question is why you do not see the difference in the test we did at the beginning. BTW, when i said you should wrap your cut-n-paste into code (#) I meant: [code] your-cut-n-paste-goes-here [/cod E] It's good to know. I'm very happy, but still. people should know :D :P :P

Jimtim, one humble request. Please do not use screenshots to display your output. Instead wrap the cut-n-paste into code (#). There are more reasons for avoiding images in forums, the two of which are {a} security (I am not clicking any image anymore!), and {b} it is impossible to cut-n-paste, your answer on the reader's side which in this case is my side. Please post the cut-n-paste again, if you wish me to continue working with you.

Jimtim, you've missed the last quote. Repeat the command, but be careful to cut-n-paste the entire command, including the last quote.

Oooops, above I made a mistake earlier (damn Cut-n-paste) and corrected it just now. There should be no greater sign between diff /tmp/*-kcodes, as I had posted in my original, since corrected post. Perhaps you should now repeat the above slightly different and enter: diff /tmp/*-kcodes && echo "differences (Error=$?)" || echo "no differences (Error=$?)" This should tell you more verbally, whether the two files differ or not. Again, the message "no differences (Error=0)" (with the Error code equal to zero), confirms that you were right in concluding that keyboards behave correctly in both environments.

I am still not 100% sure, that your diagnosis is correct. Are you sure you have entered them in different places i.e. GUI and text-based screen? What about running the command cat /tmp/my-saved-passw in both places. Do you notice a difference. One ultimate test you can do to be absolutely sure that the two environments output use the same Key-Codes is the following: In GUI terminal enter dumpkeys > /tmp/g-kcodes In text (<Ctrl+Alt+Fn>) terminal enter dumpkeys > /tmp/t-kcodes In any terminal, better GUI so you can use Cut-n-paste, enter the following diff /tmp/*-kcodes echo "Error=$?" exactly as I spelled (note asterisk (*) before -kcodes. Be careful with spaces. Observe the output of the above diff command. If you get Error=0, and if you have saved the output of the two environments in question, only then we can be sure that your earlier assumption is correct! ADDITION: It is important that you do not enter or do anything between the last two commands, even better would be to enter the above in a single line as in the following: diff /tmp/*-kcodes || echo "Error=$?"

You get "permission denied" becaise you have have repeated these steps as a different user, perhaps as root first. To fix this enter the following as root: chmod 666 /tmp/my-saved-passw And then repeat all the steps as I told you before. Do not forget. The above command must be entered as root, which will relax permissions on the file that you unfortunately created with restrictions that second time around another user could not write to. Alternatively you root could also delete the /tmp/my-saved-passw. Whatever you do, be careful that you do not repeat the same mistake again and create a file with a different user, or root. Since your root password is broken you have be extra careful follow the steps exactly, and remain one and the same user for all actions. If you have to do something as root I suggest you logout immediately after root privileges are not needed any more! The first step with one greater sign (">") will always reinitialize the file anew with one password from one (say GUI) environment, and the second with the double greater sign (">>") will add a password to it in the other (non-GUI) environment. Providing you do not misspell your passwords or misskey the commands, or do some new blunders with permission issues, all these steps will, not do anything else but confirm the diagnosis, so we will know how to fix or avoid the problem. Do not delete and or reinstall half of your system before you know what's wrong! Good luck