Jump to content

jkerr82508

Members
  • Posts

    299
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by jkerr82508

  1. You should have /main, /contrib, and /non-free as well as the corresponding /updates repos. It's safest not to use /testing or /backports. (I would remove them entirely, and not just disable them. There was a bug in mandriva-update which caused them to be used sometimes, even if they were disabled.)

     

    Have you run mandriva-update? It should update your kernel to -18.

     

    If I understand correctly, an ML350 is a desktop machine, not a laptop and so -desktop would be the right kernel flavour.

     

    Jim

  2. What else was uninstalled when you "removed" beagle? It's always wise to check the list. Install task-kde. It may well put beagle back, but you can turn beagle off without un-installing it. That's usually the safer option with unwanted applications.

     

    Jim

  3. Perhaps you need to add your user to smbpasswd. IIRC the command is:

     

    smbpasswd -a

     

    This assumes that you use the same username on your windows boxes.

     

    Jim

     

    edit: Sorry, I've just realized that is for the samba server, not the client. For the client use kcontrol/Internet & Network/Local Network Browsing/Windows Shares.

     

    Jim

  4. I was bombarded with KDE crash handler messages about artsd failures.

     

    I experienced this on cooker a couple of weeks ago, but it was very quickly fixed. You may want to check bugzilla to see if anyone else is experiencing this now. I don't recall seeing any recent reports.

     

    Jim

  5. BitTorrent should show up no problem (probably under "Internet") but if it doesn't you can add it yourself.

     

    As with smart, the gui for bt is in a separate package. Searching in rpmdrake is generally easier than using urpmi, unless you know exactly what you want to install.

     

     

    Jim

  6. I'm sorry, my posts seem a little confusing. I'll try to clarify.

     

    I did DL and install the .rpm PUEL package from the VBox site (the very link scarecrow posted). I had uninstalled the previous installation (done earlier with the .run package found on their site) before running the .rpm (PUEL) package.

     

    I could not get it to work with that - it gave me the same error message as jgj posted in the first post.

     

     

    What I do when using the PUEL version:

     

    1. Uninstall ALL other vbox and virtualbox rpms (Enter vbox|virtualbox in the search box in the Software Manager)

     

    2. Make sure kernel-desktop-devel-latest is installed (or kernel-laptop-devel-latest if using the laptop kernel ). (The full kernel source may be OK, but is not necessary)

     

    3. Install the PUEL rpm.

     

    4. Add my user to the vboxusers group

     

    5. After booting into a new kernel, re-run the setup script. (On the first attempt to launch a vm after booting into a new kernel, a pop-up displays the exact command that must be run.)

     

    This works perfectly for me every time.

     

    Jim

  7. I don't know a way to add such an entry there, but you can easily add one to the main toolbar. Right-click on the main toolbar, select configure and in the main toolbar "available actions" on the left, you'll find "New tab". Add it anywhere in the toolbar that you want it.

     

    Jim

  8. rpmdrake in 2007.1 had a bug that caused it to always use the last repo defined in urpmi.cfg as the source for installed packages. In 2008.0 this has been "fixed" by simply not reporting any source for installed packages.

     

    Jim

  9. I'd like to keep my updates and what I download and install. How do I make it keep everything? I'd like to burn them so that I can reinstall everything without downloading again.

     

    Add the following option to /etc/urpmi/urpmi.cfg

     

     {
    post-clean :0
    }

     

    This will negate the default post-clean option

     

    See man urpmi.cfg.

     

    Jim

  10. Install wine, make sure the wine process is running, click on the setup.exe or install.exe. If you're lucky it will install and run. If you have problems, check out the AppDB at WineHQ for possible hints and tips. It looks as though this is a very new application and so there is likely to be very little experience of trying to run it under wine.

     

    Jim

×
×
  • Create New...