Jump to content

ianw1974

Admin
  • Posts

    14090
  • Joined

  • Last visited

  • Days Won

    8

Posts posted by ianw1974

  1. If it cannot be removed due to dependencies, you'll need to stop it starting when you login to your system. It probably can be disabled from your auto-running applications. If it's running as a service, then the service can be disabled from MCC and the services section.

     

    That way it shouldn't give the popups although it'll still be installed, so it won't cause a problem by being missing because of the dependencies.

  2. Yes, the SA does appear after the 6 - 9 numbers, and that's what I was needing to accomplish. First, identify the 6 - 9 numbers, then replace the SA that follows.

     

    As I mentioned earlier, a colleague managed to do it with perl, so it's not that important, but I expected sed could do it somehow. I'm just limited in my knowledge of sed to be able to complete it, and so was interested in how it might work.

     

    I tried a combination of pauls with silversurfers:

     

    sed 's/^*[0-9]{6,9}SA/-newsa-/ 1' < file > file2

     

    find the numbers from 6 - 9 in length, then locate the SA which follows, but it didn't work.

  3. Probably kernel-desktop-latest doesn't have PAE enabled, and this is why you are missing the additional 700MB.

     

    What kernel's have you now got installed? Since it was working before, I think we need to choose the kernel that was previously running and not the desktop one, so:

     

    rpm -qa | grep -i kernel

     

    will provide us a list of what packages with kernel in their name are installed. Then simply reboot, and choose the other kernel instead of the kernel desktop. Once you are back to the 4GB, do:

     

    urpme kernel-desktop-latest

     

    and revert to this. Alternatively, check out the list of available kernels to install, maybe you'll find one that has pae in the kernel name for installation, or an alternative one that will have pae enabled. Maybe your pauses are due to something else, and not the server kernel exactly. Maybe some other running services.

  4. You don't understand. Fonts are fonts and they are generally not 32 bit or 64 bit. They are installed under /usr/lib and so both 32 bit and 64 bit applications should see them. The same path for /usr/share/fonts/TTF is the same for both 32 bit and 64 bit systems.

     

    The problem is not your fonts, but your 32 bit application probably doesn't know where to find them. It is looking in the wrong place. You would need to ask on the Zendstudio forum as chances are the configuration files for this application need to be updated correctly to search in the right place.

  5. As to why Mandriva dropped the traditional install media in favour of Live only media for installation your guess is good as mine. :wall:

     

    Agree totally. I've never ever used a LiveCD to test or use my system. I've always installed the sytem and then used it normally. Was much better before without the Live stuff, there was less CD/DVD images for a start and everything was on one DVD. Previously, if I remember correctly, they even had auto-detection which meant it would complete a 32 bit or 64 bit installation depending on your hardware. That way, one DVD for 32 bit and 64 bit systems. Now it seems it's reverted and been segregated again :wall:

  6. In the error above, you are missing:

     

    libXext.so.6

     

    Search for this file, and install the appropriate package, and then try running the xendstudio installer again. You can do this using MCC, the package will be available with the use of urpmi or MCC.

     

    Alternatively, as I've just searched for you:

     

    urpmi libxext6

     

    should do the trick. Then try again. You don't mention which version of Mandriva? 2010?

  7. John,

     

    Just in case it happens again, you can boot a livecd and then chroot into your install and then remove the packages. That would save you your reinstall. Although some console stuff needs to be done, which I know you don't like too much :) but it could work out a bit quicker this way to reverse something installed, then a fresh install.

  8. Something obviously went crazy in Mandriva that they felt they had to make so many ISO's in the first place. Originally when I started using Mandrake/Mandriva back in 2005 there was only a couple of ISO images, that could have still been maintained instead of creating so many separate ones in the first place. And they all had KDE/GNOME on them by default.

  9. There is text that appears before the first 6 to 9 numbers - this needs to be ignored.

    It needs to locate the 6 - 9 numbers and replace the SA that follows this.

    Therefore, any other instance of SA before these numbers is to be ignored and any SA that follows after the first instance of SA after the 6 - 9 numbers needs to be ignored.

  10. Oops bad move following a howto downloading rpms from pbone.net. The best way is doing it using the Mandy repositories through urpmi. You could have downloaded and installed the wrong rpms which put fonts in the wrong place. Also, we don't know if major changes to the directory structures have occurred since the take-over of Mandriva.

     

    If you had all your easyurpmi repos installed, you should have just been able to find a list of all packages that you could install that have ttf in their name. Of course, you won't need to install all the ones on the list, as a lot of them are for other languages as well other than English.

     

    urpmf --name ttf

     

    would filter all available packages for install with ttf in their name, from the console. Of course, you can use the GUI apps for installing packages as well. I'd suggest removing the ones you downloaded and installed manually.

  11. I'm currently on hols at the minute but will have to give it a go. Just to clarify, is what you posted to replace the "SA" that is located somewhere in the middle? Because this is the only instance it can replace. It could appear in the last four characters and this one I wouldn't want to replace.

     

    I won't be back in to check it until the end of the month :)

  12. If you upgraded your system from one release to another, it is possible that some KDE config files might not have upgraded correctly and could be causing problems. You can rename/remove the old KDE config, or alternatively, just create a new user, and move all your data across to this one, then you would be sure that no other config files are conflicting. I always do this, it's easy enough to reset config of KDE settings for look, etc, of course, some directories I copy into place like for pidgin and SSH as I need this config.

  13. One thing to try which I found while searching about the fbcon error. In your home directory, check to see if you have a .xinitrc file? If you have, delete it, or move it somewhere else so that it is not found in your home directory. This will be /home/username/.xinitrc, so move it to Documents or Downloads so that it won't be read.

     

    Another alternative, is to go to /etc/X11 and rename xorg.conf to xorg.conf.backup so that xorg will then dynamically run and detect everything automatically.

     

    Does your system work any better after that? If not, then the only thing next worth trying is opening a bug with PCLOS. But try moving that .xinitrc file first, see if any better. If not, rename the xorg.conf and restart and see if any better?

×
×
  • Create New...