chris z

happened to me once after an upgrade to a newer version of OOo. try this........ close OOo if you have it open. go to /home/you & rename the .openoffice folder to .openoffice~. (don't delete it in case you might want to copy over some things later) restart OOo. it will create a new setting folder in /home. try to print. Chris

for what it's worth, i've always had the best success using all PLF packages where MPlayer is concerned. i haven't run across a Windows media file that i can't play with it. if you go the PLF route, make sure you get all the codec packs. there are several of them. just use Mandrake Control Center->software->install & type codec in the search & get all of them that show up. you shouldn't have any problems once everything is installed. Chris

this happened to me once. turned out i hadn't installed MPlayer fonts. do you have those installed? go to Mandrake Control Center->software management->install & type mplayer in the search. look for a package called mplayer-fonts-<version #>. or, you could also do as root from a terminal urpmi mplayer-fonts if you're one of those cli hardcores. install the package, then try running MPlayer. Chris

check out my post #3 in this thread. it's nothing fancy, just for a simple edit of the squid.conf to get it up & running. Chris

i have 3 temp readings for lmsensors........... mobo, chassis, & cpu. so, the unknown one could be chassis. but, 127 C is way too hot for any of the above, so it could either be a bogus entry, or it could be that the divider being used to calculate the temp is wrong. have a look at your /etc/sensors.conf file. look for the entry for the particular sensor(s) you're using & see if there's any info there about tweaking the divider being used. i had to do that for my fan speed. the divider was set too low & giving me an incorrect fan speed. Chris

have you tried, setting the volumes in aumix first, saving them, then setting things in kmix (making sure pertinent settings are not muted) then saving those settings? aumix is system wide, kmix is kde specific. if you set kmix first, then aumix, aumix will override kmix. Chris

it sounds like your video/monitor isn't conffiged correctly. when you boot & get to the prompt, login as root. to do so, type.......... su hit enter then type the root password (hit enter). then type the following....... XFdrake hit enter that CaPs sensitive, too. that will run the X config module for your video settings. make sure you pick the correct driver (or something compatable) for your card, check the monitor refresh & res settings, then use the "test" feature after setting it up. if it passes the test, you're ok. if not, keep trying diffferent video card drivers until you get one that works. the default choice that MDK uses for some cards sometimes isn't always the correct choice. Chris

ok, here's the "device" section from my xorg.conf. try entering what i have highlighted in red to your xorg.conf, exactly as it looks in mine. that option specifies to use kernel AGP support first, if that fails, then use Nvidia AGP. other options you can use are....... "0" (uses no agp support) "1" (uses nvidia agpart only) "2" (tries kernel agpart only) note: you don't have to do this edit by killing X & using vim (or whatever). you can use a text editor in GUI to make the edit. you will have to restart X for the option to take effect. Chris

can you post the contents of your /etc/X11/xorg.conf file here, please? there are a few options that you can add in there & might need to make Nvidia drivers play nicely with MDK. it could be as simple as editing that file a bit, to get you back to normal. i need to see it first, though. Chris

use Grip. very nice app. endlessly configurable, GUI interface, works in any Desktop environment, converts mp3's to wav. use MCC software installer, type grip in the search to install if you don't have it installed already. or, in terminal as root do urpmi grip. Chris

if it helps, here's my "failsafe" lilo entry........ that's a pretty generic "failsafe" entry for lilo. it'll boot you to a prompt to help in trouble shooting. resume= specifies the /swap partition to use devfs=nomount tells it not to auto mount any partitions. see man lilo.conf for tons of other options, but the above should prolly do what you're after. Chris

if anybody is still having the mouse problem, try editing the "InputDevice" section of xorg.conf. it seems udev doesn't like the old /dev/mouse path on some set ups, for some reason. here's an example of mine using a ps2 scroll wheel mouse........... if your entry for "Device" read /dev/mouse try changing to the above. Chris

in addition to Steve's suggestion, you can also go to KControl (IE: Configure Your Desktop)->components->session manager & check the "start with an empty session" box if you want to prevent things like that from happening again. checking that option doesn't mean that you'll lose all your desktop settings, it just prevents apps that you may have left running at reboot/shutdown from restarting next time you log into KDE. Chris

right click on the Google search bar. a drop down box with options should appear. select "orientation" then choose the place you want it. the choices are "top", "left", "right", "bottom", "float". Chris

yes, all .bin must be chmod'd to make them executable. congrats, glad you got it working! if you check this out again & are having no problems, could you please mark this thread as "solved"? Chris

not really sure what you mean, sorry. do you mean multiple tabs in Konqueror? if so, in the toolbar click "location->new tab" to add tabs. you can also place a button in the tool bar for that by clicking "settings->configure toolbars", then use the left panel, find the "new tab" button, add it to the right panel, move it up or down for placement, then "apply"->"ok". to save the configuration, click "settings->save view profile......". if that's not what you're talking about, could you please attach a screenie, perhaps, to give me (or anybody) a visual reference? Chris

check to see if you have magicdev installed. it's a replacement for supermount. it automatically mounts/unmounts drives. in terminal as root do........ rpm -qa|grep magicdev if it finds nothing, that means it isn't installed. to install it, either use Mandrake Control Center->software management->install & type magicdev in the search, or in terminal as root do........ urpmi magicdev magicdev seems to be an improvement over the old supermount, but i don't personally use it because i prefer to mount/unmount manually. edit: note, if you want to, & you're using KDE, you can also right click the desktop, choose create new->device, set the path to that device, & create a desktop icon for it. then, when you right click the icon, you will have an option to mount/unmount the device. just a suggestion if you decide to go the magicdev route & you find you don't like it or it's giving you problems. Chris

if what aRTee suggested doesn't work, look into power management issues. go to Mandrake Control Center->system->services & see if any of the following are running/set to start at boot.......... apm apmd acpi if they are, try disabling them one at a time & see if you can power down as normal. if that doesn't help, look at your "append=........" line in /etc/lilo.conf for an acpi entry. if it says acpi=on or acpi=ht, change it to acpi=off. here's what mine looks like for an example.......... if you change that entry, make sure you run lilo to save the changes. to do so, in terminal as root do the following.......... lilo -v hit enter. Chris

i don't know if this will work, but you could try the old sndconfig detect method. in a terminal as root type........... sndconfig (hit enter) if you get a command not found error, install it with........ urpmi sndconfig .......then run it. it's on the CD's but i don't know if it's installed by default any more. after you run it, it might seem to hang & do nothing for awhile. let it go, it's just searching for installed sound cards. if it finds one, it will bring up a dialogue box telling you what it found & ask you if you want to use it. it will then install the proper driver & give you the option to test it. like i said, not sure it will work, but it won't hurt to try. Chris

i wonder if this problem happened to anybody else in 10.1 after the intial install while trying to get updates? i had the same thing happen to me. same error message, same scenerio. when i finally did get to the updates (more on that in a moment) i noticed there were updates for GURPMI & PERL-URPMI. so i'm thinking maybe it's a bug that the updates fix. after i got the upates installed, the problem stopped happening. what i did.......... first, it seems alot of the mirrors that MDK supplies as default choices are either not up to date, or inaccessible. i'd suggest going to the Easy URPMI link i supplied above & trying the Proax mirrors from France. those mirrors have always been fast, reliable, & up to date (for me, at least). get all of the above sources i mentioned...... plf, contrib, main, updates, & jpackage. add them per the instructions at Easy URPMI. if you find you have trouble adding a mirror, then just add an update mirror for now & get the rest later. after you have the sources added, go to Mandrake Control Center->software management & try the update function. if it errors out, try it several times. it worked intermittently for me at first. if you find you're still getting the error, then go to media manager & unselect all sources except for the install CD's & the update source. that's what finally did the trick for me. get all of the updates available. if it tells you that you can't select a few packages, ignore them this time around & get what you can. that happened to me, also. coincidentally enough, 2 of the packages i couldn't install at first were the urpmi related ones. after you get the packages installed, reboot. if you get a GTK error when trying to quit MCC (or find that the "quit" button doesn't work), close it out with the X in the upper right corner. again, another glitch i ran into. after you reboot, go back to the update section of MCC & search for updates again. get any that it might list. reboot again, then re-check the sources you disabled earlier, or re-add them via Easy URPMI if you couldn't add them the first time around. let me know if it all worked out. and, again, i'd like to hear if anybody else ran into this problem. Chris

i've run into that. it seems (to me) to be a bug of some sort. i've found a work around & a fix.... work around....... close out the error box & click update several times. eventually it works properly. fix.......... go HERE, add update, main, contrib, plf, & jpackage sources. (first, remove any of those sources you might already have via media manager in MCC). i don't know why, but the mirror sources that MDK offers you either don't work at all, or give the error you're getting. it all stopped for me when i picked alternate sources from the above site. try the proax mirrors from France. they're fast, reliable, & up to date. Chris

try going to Mandrake Control Center->harware->hardware. make sure the camera is plugged in, then look at the usb settings. if things are detected & the camera is showing, try looking at GnomeMeeting settings & make sure those are correct. if nothing shows in MCC, probe for new USB connection. Chris

those instructions are a bit confusing & not quite right. try looking HERE , instead. Chris

you must make the .bin file executable. to do so, open a terminal as root & change to the directory where the .bin file is located. then, issue the following command........ chmod +x jdk-1_5_0_<version>-linux-i586.bin where <version> is the actual version number. then, you need to run the installer with this command........ ./jdk-1_5_0_<version>-linux-i586-rpm.bin that will create the .rpm file for installation. run that by doing the following......... rpm -iv jdk-1_5_0_<version>-linux-i586.rpm java will then be installed. all you'll need to do is get the plugins to work with various browsers. for a "how to", check HERE Chris

you could manually edit the etc/X11/xorg.conf file. look for the following section....... just make sure you set it within your monitor's parameters. you can easily fry a monitor if you try to set it beyond what it's capable of. Chris