GRUB2 Editor

A KDE Control Module for configuring the GRUB2 bootloader.

Smoothly integrated in KDE System Settings, it is the central place for managing your GRUB2 configuration. Supports many GRUB2 configuration options, most notably:

  • Manage default boot entry
  • Manage boot timeout
  • Manage boot resolutions
  • Manage boot menu colors
  • Manage boot menu theme
  • Manage linux kernel arguments
  • Save and update the configuration files of GRUB2

Extra features include:

  • Recover GRUB2
  • Remove old entries
  • Create and preview GRUB2 splash images

Related Blog: http://ksmanis.wordpress.com/category/grub2-editor/

SourceForge Page: https://sourceforge.net/projects/kcm-grub2/

KDE-Apps.org Page: http://kde-apps.org/content/show.php?content=139643

KDE Extragear Page: https://projects.kde.org/projects/extragear/sysadmin/kcm-grub2

54 thoughts on “GRUB2 Editor

  1. I’ve been looking for something like this since moving to Fedora 16. Because the default boot loader configuration no longer works since Fedora made the move to grub2.
    Only problem is, is that it will not install on x86_64 systems because of a file conflict between an i686 file and an x86_64 file. Here’s the error:
    Test Transaction Errors: file /usr/share/ImageMagick-6.7.1/configure.xml from install of ImageMagick-6.7.1.9-3.fc17.i686 conflicts with file from package
    ImageMagick-6.7.1.9-3.fc17.x86_64

    So what can I do to get this working?

  2. I have packaged kcm-grub2 and installed, runned systemsettings but i dont see there any new entry to edit grub entries?

    • It should appear under ‘System Settings > Startup and Shutdown > GRUB2 Bootloader’.

      You can also run it with the command ‘kcmshell4 kcm_grub2′. If that fails, then it’s not installed.

  3. Yes i see it now, but if i run as regular user than outputs:
    No valid GRUB2/BURG instalation could be detected!

    It only appears if running systemsettings as root, and it should appear as regular user and if there were some changes ask for root password.

  4. I’m running KDE 4.8.3 in Gentoo. I have kcm-grub2 0.5.5 installed:

    # eix -I kcm-grub2
    [I] kde-misc/kcm-grub2
    Available versions: (4) (~)0.5.0 (~)0.5.5
    {{aqua +hwinfo imagemagick linguas_ca linguas_cs linguas_da linguas_de linguas_el linguas_es linguas_et linguas_fr linguas_ga linguas_hu linguas_lt linguas_nl linguas_pa linguas_pl linguas_pt linguas_pt_BR linguas_ru linguas_sv linguas_uk linguas_zh_TW packagekit}}
    Installed versions: 0.5.5(4)(13:20:02 17/06/12)(hwinfo linguas_pt_BR -aqua -imagemagick -linguas_ca -linguas_cs -linguas_da -linguas_de -linguas_el -linguas_es -linguas_et -linguas_fr -linguas_ga -linguas_hu -linguas_lt -linguas_nl -linguas_pa -linguas_pl -linguas_pt -linguas_ru -linguas_sv -linguas_uk -linguas_zh_TW -packagekit)
    Homepage: http://kde-apps.org/content/show.php?content=139643
    Description: KCModule for configuring the GRUB2 bootloader.

    I have the following executables:

    # ls -1 /sbin/grub*
    /sbin/grub2-install
    /sbin/grub2-mkconfig
    /sbin/grub2-mkdevicemap
    /sbin/grub2-mknetdir
    /sbin/grub2-probe
    /sbin/grub2-reboot
    /sbin/grub2-set-default
    /sbin/grub2-setup

    I set System Settings (System Administration) > Login Screen | Shutdown | Boot manager to be Grub2

    System Settings (System Administration) > Startup and Shutdown > GRUB2 Bootloader displays the error message “No valid GRUB2/BURG installation could be detected!”.

    System Settings (Lost and found) GRUB Editor prompts me for the root password and, when I enter it, System Settings crashes.

    Based on your post of April 5, 2012 on the KDE-Apps.org page for kcm-grub2, I tried the following (N.B. the files are in /sbin/, not /usr/sbin/):

    ln -s /sbin/grub2-install /usr/bin/grub2-install
    ln -s /sbin/grub2-mkconfig /usr/bin/grub2-mkconfig
    ln -s /sbin/grub2-probe /usr/bin/grub2-probe
    ln -s /sbin/grub2-set-default /usr/bin/grub2-set-default

    but that made no difference.

    How can I get kcm-grub2 to work? Thanks in advance for your help.

    • Save this patch (use the “Raw code” link top right to copy-paste it in a text editor) in /etc/portage/patches/kde-misc/kcm-grub2/50fb447.patch and re-emerge kcm-grub2. It will forward you from v0.5.5 to the current git HEAD (where the issue is resolved). Of course as soon as a new version rolls out, remove the patch or else it won’t emerge. I expect to make a new release soon though, because many distributions have outdated packages.

      Edit: Btw, I tried soft-linking and it works here with v0.5.5 (also using Gentoo). Dunno why it won’t work for you.. My GRUB executables are under /usr/sbin because I use version 2.00_beta6, I think. Perhaps you have a different version?

    • Please post the contents of /var/tmp/portage/kde-misc/kcm-grub2-0.5.5/temp/50fb447.patch.out

      Edit: I tried compiling with the same USE flags as you (hwinfo, linguas_pt_BR) and it compiles fine with the patch.

          • That second patch you posted enabled kcm-grub2 to merge. I can now access System Settings (System Administration) > Startup and Shutdown > GRUB2 Bootloader.

            However, when I try to apply any change (after entering the root user’s password in a pop-up window which opens behind the System Settings window and I have to bring to the front manually) a pop-up window opens displaying the error message:

            “Failed to save GRUB settings. DBus Backend error: could not contact the helper. Connection error: . Message error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.”

            Any suggestions?

            (By the way, my grub.cfg file is in the directory /boot/grub/, not in the directory /boot/grub2/. Does kcm-grub2 cater for grub.cfg being in a directory other than the /boot/grub2/ directory?)

            ευχαριστώ πάρα πολύ.

            • Yeah, upgrade, reboot and see if the problems persist. Also post the results of “equery l *polkit*” to see which policykit-related packages you have installed. In Gentoo the GRUB executables follow the grub2-xxxxxx naming scheme so your boot directory should also be /boot/grub2/.

              • Here is the output from the equery command:

                # equery l *polkit*
                * Searching for *polkit* …
                [IP-] [ ] gnome-extra/polkit-gnome-0.105:0
                [IP-] [ ] kde-misc/polkit-kde-kcmodules-0.98_pre20101127:4
                [IP-] [ ] sys-auth/polkit-0.105:0
                [IP-] [ ] sys-auth/polkit-kde-agent-0.99.0:4
                [IP-] [ ] sys-auth/polkit-qt-0.103.0:0

                Regarding the location of grub.cfg, I thought the location is up to the user? Even in Gentoo, I thought it is not mandatory to have it in /boot/grub2/? If the location of the grub.cfg file is a parameter of e.g. grub2-mkconfig, then presumably it is not mandatory?

                I’ll try to merge grub-2.00_beta6 now. Then should I re-merge kcm-grub2 with the first patch you posted, or is the second patch you posted still applicable in the case of grub-2.00_beta6?

                • The second patch is the same as the first one with the only difference that it was generated using the ‘–no-prefix’ option (‘man git-diff’ for explanations – it is related to the -p0 or -p1 option of the patch utility).

                  grub.cfg’s location is determined by the boot directory, which in turn is determined by the user upon GRUB’s installation. After you emerge GRUB 2.00_beta6, you will have to run a command like this: ‘grub2-install –boot-directory=/boot/ /dev/sda’ in order to install GRUB2 in your MBR(=Master Boot Record) and create a GRUB2 directory structure under /boot/. Gentoo’s executables are defined to create a /boot/grub2 subdirectory; it is a compile-time option I think.

                  • Well, grub-2.00_beta6 merged OK and I rebooted, but I still get the same pop-up window error message:

                    “Failed to save GRUB settings. DBus Backend error: could not contact the helper. Connection error: . Message error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.”

                    Also, the output from the command equery l *polkit* is the same as the output I posted earlier before merging grub-2.00_beta6.

                    I don’t have GRUB 2 installed in my MBR. I have the Windows bootloader installed in the MBR and it chainloads GRUB 2 which is installed in my boot partition (/dev/sda3). When I installed GRUB 2 a couple of years ago using the grub-install command (not the grub2-install command), I specified the boot partition /dev/sda3 (the directory /boot on my machine is in its own partition), not the MBR. The images are installed in /boot/grub/, not /boot/grub2/. I currently also have grub.cfg in /boot/grub/ and that works too.

                    But now I’m confused! You have explained to me that Gentoo’s grub2-install command insists on grub.cfg being in a sub-directory ./grub2/ and the user cannot specify that it is in a sub-directory ./grub/. Indeed, that is what ‘man grub2-install’ in Gentoo tells me too:

                    ” –boot-directory=DIR
                    install GRUB images under the directory DIR/grub2 instead of the /boot/grub2 directory”

                    which seems unecessarily restrictive. Anyway, in that case I assume that I will now have to use the following commands:

                    grub2-install /dev/sda3
                    grub2-mkconfig -o /boot/grub2/grub.cfg

                    which would mean I will get the GRUB 2 images and the file grub.cfg installed in the /boot/grub2/ directory. I’m going to try that, and have my fingers crossed that my machine will still boot after making the change from /boot/grub/ to /boot/grub2/.

                    But I assume that still does not explain the DBus error message, though?

                    • After mounting your boot partition, do ‘grub2-install –boot-directory=/boot/ –force /dev/sda3′. Please note that ‘–force’ is advised when installing on a partition. The ‘–boot-directory’ is not necessary I think, but it wouldn’t hurt to be more explicit. When you reboot, you should see a “beta6″ at the top of the GRUB menu.

                      The DBus error is not explained, indeed, and it is not an application-produced error message. Something’s wrong with DBus/PolicyKit.

                      Other than that, you got everything else right :-)

                    • I entered the following commands:

                      mount /dev/sda3 /boot
                      cp /boot/grub/splash.png /boot/grub2/
                      grub2-install –boot-directory=/boot/ –force /dev/sda3
                      grub2-mkconfig -o /boot/grub2/grub.cfg

                      Unfortunately it still shows “1.99” at the top of the GRUB 2 menu, and my boot splash picture no longer appears.

                      Anyway, I’ll try to work out why it didn’t work, as I’ve troubled you enough already. Thanks for your replies..

                    • I read most of your (quite lengthy tbh) thread and blog post and I have to say, you went through quite an adventure there ;-) By the way, you motivated me to make a new small release with the fixes included (the patch I sent you). Glad everything worked out, let me know if anything else goes amiss.

  5. I installed this in Xubuntu 12 but I can not find the app anywhere in the menus. I rebooted the box and still no change. No errors during the install and I even reinstalled it via the Ubuntu Software Center

    • It is located in KDE’s System Settings (‘Startup and Shutdown > GRUB2 Bootloader’). You can also manually invoke it by typing “kcmshell4 kcm_grub2″. In KDE, searching in KRunner for grub will also produce a result.

      • Thanks. I had to install the KDE Desktop as Xubuntu was using a different one. I have a machine with Xubuntu as well as Mint installed. The latter needs to have noapic and nomodeset as params. When I launch this app inside of Xubuntu and go to Advanced it shows quiet splash noapic nomodeset. It does not matter which entry from the pulldown on the General tab I select, even Mint these params are showing up on the Advanced tab. Is there no way of the app showing what a particular entry has in Grub and modifying that item alone?

        • No, it’s a GRUB2 limitation, you would have to manually create an entry in /etc/grub.d/40_custom. The Xubuntu/Mint entries are automatically generated by scripts (located in /etc/grub.d/).

  6. Downloaded the latest package (“kcm-grub2_0.5.8-3_amd64.deb”) from http://sourceforge.net/. But while trying to install it in my 64-bit Mint 13 edition, got the following error:
    —————————————————————————————————————–
    # dpkg -i Downloads/kcm-grub2_0.5.8-3_amd64.deb
    (Reading database … 210894 files and directories currently installed.)
    Unpacking kcm-grub2 (from …/kcm-grub2_0.5.8-3_amd64.deb) …
    dpkg: error processing Downloads/kcm-grub2_0.5.8-3_amd64.deb (–install):
    trying to overwrite ‘/etc/dbus-1/system.d/org.kde.kcontrol.kcmgrub2.conf’, which is also in package kde-config-grub2 0.5.0-0ubuntu3
    dpkg-deb (subprocess): subprocess data was killed by signal (Broken pipe)
    dpkg-deb: error: subprocess returned error exit status 2
    Errors were encountered while processing:
    Downloads/kcm-grub2_0.5.8-3_amd64.deb
    —————————————————————————————————————–

  7. Trying to install kcm-grub2_0.5.8-3_amd64.deb i always get an error message: Abhängigkeit nicht erfüllbar: libc6 (>=2.14) My libc6 is version 2.11 and there is no newer one for debian. My debian version is squeeze 6.0.6 and my platform is 64 bit amd. Please help….
    thank you in advance, jayveeone

    • First of all let me inform you that all packages I provide are built using the openSUSE Build Service.

      Due to legal restrictions, the openSUSE Build Service allows Ubuntu packages to have dependencies only from the core repository. In Ubuntu Quantal, the dependency that allows removing old kernels (libqapt-dev) was moved from core to universe so the Quantal packages do not provide the option to remove old kernels. Only a hand-made package can provide this. So poke your distro’s developer to package the latest version because as I see only up to version 0.5.0 is available in the Quantal repositories. The same applies for the Debian 6 package.

  8. Hello again!

    From sys-boot/grub-2.00_p5107-r1 onwards, GRUB 2 in Gentoo uses /boot/grub/ directory instead of /boot/grub2/ directory. I was wondering if this has any effect on kde-misc/kcm-grub2 and does the current version in Portage (0.6.4) handle the new Gentoo GRUB 2 directory structure?

    I also have a related question: If and when kde-misc/kcm-grub2 works with the new Gentoo GRUB 2 directory structure, would it then work also with the version of GRUB 2 used in Sabayon Linux?

    Gentoo GRUB 2 from 2.00_p5107-r1 onwards:
    Main directory used: /boot/grub/
    Directory in which GRUB 2 core.img file is stored: /boot/grub/i386-pc/core.img
    Command to install GRUB 2 in the MBR of HDD sda: grub2-install /dev/sda
    Command to create grub.cfg file: grub2-mkconfig -o /boot/grub/grub.cfg

    Sabayon GRUB 2:
    Main directory used: /boot/grub/
    Directory in which GRUB 2 core.img file is stored: /boot/grub/i386-pc/core.img
    Command to install GRUB 2 in the MBR of HDD sda: grub2-install /dev/sda
    Command to create grub.cfg file: either ‘grub-mkconfig -o /boot/grub/grub.cfg’ or ‘grub2-mkconfig -o /boot/grub/grub.cfg’ (grub-mkconfig is a symlink to grub2-mkconfig)

    • Hello!

      Starting with v0.6.4 (more specifically per this commit) any GRUB2 directory structure is supported, through the GRUB_FOO CMake cache variables as documented in the INSTALL file.

      The Gentoo package (=kde-misc/kcm-grub2-0.6.4) does not make use of this new, flexible structure and won’t work properly (because GRUB_ENV and GRUB_MEMTEST are pointing to wrong files). /boot/grub/grub.cfg is a symlink to /boot/grub2/grub.cfg so GRUB_MENU won’t be affected, although it would be still pointing to the old file. You should poke your friendly package maintainer and ask for a better ebuild. :-) To answer your second question, kcm-grub2 can work in Sabayon any time, as long as a proper package is created.

      Starting with this version I will consider GRUB-naming-scheme-related bugs as packaging issues because it really is a pain in the ass to detect every different directory structure. The 2 most prominent directory structures are auto-detected (vanilla GRUB2 and the ‘2’ suffix, as in grub2-foo-exe, /boot/grub2/ etc.) but for all the other cases, the packager should explicitly specify the GRUB2 directory structure of his distribution.

      • Thanks for your reply to my queries. However, in my case /boot/grub/grub.cfg is not a symlink to /boot/grub2/grub.cfg as I have completely eliminated the /boot/grub2/ directory and installed sys-boot/grub-2.00_p5017-r2 in the /boot/grub/ directory as explained in my Gentoo Forums post: http://forums.gentoo.org/viewtopic-p-7426312.html#7426312

        You mention that GRUB_ENV and GRUB_MEMTEST are pointing to the wrong files in Gentoo. In which file are those two environment variables assigned in Gentoo? Could I assign GRUB_ENV and GRUB_MEMTEST in /etc/default/grub and recreate /boot/grub/grub.cfg using again the command “grub2-mkconfig -o /boot/grub/grub.cfg”? If that would work, to what should I assign those two environment variables? Or would I need to hack the Gentoo ebuild for sys-boot/grub and assign them in there?

        • There has been a misunderstanding, I was referring to CMake cache variables which can only be defined when compiling kcm-grub2, not [environment] variables which are defined in /etc/default/grub and are used by the grub-mkconfig script to generate the GRUB menu. As I said, these variables are documented in the INSTALL file (found in the release tarball) and package maintainers should give it a read in order to create a proper package.

          Gentoo as of =sys-boot/grub-2.00_p5017-r2 uses a mixed installation (supposing the multislot USE flag is on) which means that several paths need to be explicitly defined: they cannot be auto-detected by CMake. Currently in Gentoo none of these variables are set by the ebuild, so kcm-grub2 won’t work properly because GRUB_MENU, GRUB_ENV and GRUB_MEMTEST point to wrong files. This happens because at compile-time when CMake tries to auto-detect the GRUB installation it [falsely] assumes that since all the executables follow the ‘2’ suffix naming scheme (e.g. grub2-mkconfig instead of grub-mkconfig, grub2-set-default instead of grub-set-default, etc.), the rest of the installation follows this naming scheme as well. Therefore GRUB_MENU points to ‘/boot/grub2/grub.cfg’ while it should point to ‘/boot/grub/grub.cfg’, GRUB_ENV points to ‘/boot/grub2/grubenv’ while it should point to ‘/boot/grub/grubenv’ and GRUB_MEMTEST points to ‘/etc/grub.d/20_memtest86+’ while it should point to ‘/etc/grub.d/39_memtest86+’ [1].

          This means that when compiling kcm-grub2, instead of ‘cmake ebuild_cmake_arguments’ the ebuild should specify ‘cmake ebuild_cmake_arguments -DGRUB_MENU=/boot/grub/grub.cfg -DGRUB_ENV=/boot/grub/grubenv -DGRUB_MEMTEST=/etc/grub.d/39_memtest86+’. By ebuild_cmake_arguments I mean any CMake argument that is already used in the ebuild. Ideally the package maintainer will update the ebuild. Non-ideally, any Gentoo user should be more than capable of setting up a local overlay with a modified version of the upstream ebuild. Being a Gentoo user myself, I know this to be true first-hand.

          All these might be a lot to take in, but unfortunately as far as I know there is no proper way of querying the GRUB installation for the right paths. The burden falls on packagers’ shoulders to create proper packages. This burden is even heavier for Gentoo package maintainers, considering that depending on the grub package version a different naming scheme is used (/boot/grub2/ for <sys-boot/grub-2.00_p5017-r2, /boot/grub/ for >=sys-boot/grub-2.00_p5017-r2), plus the multislot USE flag toggles the '2' suffix in the executables. Great configurability comes at a price.

          Sorry for the lengthy response but I tried to answer thoroughly. Let me know if any other questions pop to mind.

          [1] GRUB_MEMTEST is unrelated to the boot directory naming scheme: most distributions use '/etc/grub.d/20_memtest86+' by default, but Gentoo is an exception to this rule and uses the non-standard '/etc/grub.d/39_memtest86+'. If you don't properly set GRUB_MEMTEST, kcm-grub2 will still work, but you won’t be able toggle the memtest generation feature.

          • Ah, OK. Understood. Thanks for your detailed reply. From what you have written, it seems a fairly trivial exercise to hack the existing kcm-grub2-0.6.4 ebuild. I’ll create a kcm-grub2-0.6.4-r1 in my local overlay to try it out.

  9. kcm-grub2-0.6.4 in main Portage tree:

    # tail /usr/portage/kde-misc/kcm-grub2/kcm-grub2-0.6.4.ebuild

    src_configure() {
    local mycmakeargs=(
    “-DWITHQApt=OFF”
    $(cmake-utils_use_with packagekit QPackageKit)
    $(cmake-utils_use_with imagemagick ImageMagick)
    $(cmake-utils_use_with hwinfo HD)
    )
    cmake-utils_src_configure
    }

    Snip from emerge output:
    — ————————————————————————–
    — GRUB_INSTALL_EXE: /usr/sbin/grub2-install
    — GRUB_MKCONFIG_EXE: /usr/sbin/grub2-mkconfig
    — GRUB_PROBE_EXE: /usr/sbin/grub2-probe
    — GRUB_SET_DEFAULT_EXE: /usr/sbin/grub2-set-default
    — GRUB_MENU: /boot/grub2/grub.cfg
    — GRUB_CONFIG: /etc/default/grub
    — GRUB_ENV: /boot/grub2/grubenv
    — GRUB_MEMTEST: /etc/grub.d/20_memtest86+
    — ————————————————————————–

    kcm-grub2-0.6.4-r1 in my local overlay in Gentoo:

    # tail -n 18 /usr/local/portage/kde-misc/kcm-grub2/kcm-grub2-0.6.4-r1.ebuild

    src_configure() {
    local mycmakeargs=(
    -DWITHQApt=OFF
    -DGRUB_INSTALL_EXE=/usr/sbin/grub2-install
    -DGRUB_MKCONFIG_EXE=/usr/sbin/grub2-mkconfig
    -DGRUB_PROBE_EXE=/usr/sbin/grub2-probe
    -DGRUB_SET_DEFAULT_EXE=/usr/sbin/grub2-set-default
    -DGRUB_MENU=/boot/grub/grub.cfg
    -DGRUB_CONFIG=/etc/default/grub
    -DGRUB_ENV=/boot/grub/grubenv
    -DGRUB_MEMTEST=/etc/grub.d/39_memtest86+
    $(cmake-utils_use_with packagekit QPackageKit)
    $(cmake-utils_use_with imagemagick ImageMagick)
    $(cmake-utils_use_with hwinfo HD)
    )
    cmake-utils_src_configure
    }

    Snip from emerge output:
    — ————————————————————————–
    — GRUB_INSTALL_EXE: /usr/sbin/grub2-install
    — GRUB_MKCONFIG_EXE: /usr/sbin/grub2-mkconfig
    — GRUB_PROBE_EXE: /usr/sbin/grub2-probe
    — GRUB_SET_DEFAULT_EXE: /usr/sbin/grub2-set-default
    — GRUB_MENU: /boot/grub/grub.cfg
    — GRUB_CONFIG: /etc/default/grub
    — GRUB_ENV: /boot/grub/grubenv
    — GRUB_MEMTEST: /etc/grub.d/39_memtest86+
    — ————————————————————————–

    Works a treat. Thanks!

  10. I’m trying to update to version 43 and get the following yum message:

    Resolving Dependencies
    –> Running transaction check
    —> Package kcm-grub2.x86_64 0:0.6.4-41.1 will be updated
    —> Package kcm-grub2.x86_64 0:0.6.4-43.1 will be an update
    –> Processing Dependency: libMagick++.so.5()(64bit) for package: kcm-grub2-0.6.4-43.1.x86_64
    –> Processing Dependency: libMagickCore.so.5()(64bit) for package: kcm-grub2-0.6.4-43.1.x86_64
    –> Finished Dependency Resolution
    Error: Package: kcm-grub2-0.6.4-43.1.x86_64 (home_ksmanis)
    Requires: libMagickCore.so.5()(64bit)
    Error: Package: kcm-grub2-0.6.4-43.1.x86_64 (home_ksmanis)
    Requires: libMagick++.so.5()(64bit)
    You could try using –skip-broken to work around the problem
    You could try running: rpm -Va –nofiles –nodigest

    I get the rpms to install libMagick++.so.5()(64bit) and libMagickCore.so.5()(64bit) but it always fails to install.

    Help

    • Hello Tom,

      have you tried the suggestions provided by yum at the end of the message? If they don’t work, please refer to a forum related to your distribution, this is a package manager issue. I’m afraid I can’t help you further with this issue.

  11. Hello,

    problem installing the following RPM on opensuse: kcm-grub2-0.6.4-43.10.x86_64.rpm
    error: Failed dependencies:
    libMagick++-6.Q16.so.5()(64bit) is needed by kcm-grub2-0.6.4-43.10.x86_64

    I’ll try and solve this myself with zypper but a response and possible resolution would be appreciated

    all the best,
    Hugh

  12. Hello again,

    I discovered I’ve been using a different ImageMagick and K3b codecs due to using Factory and probably the packman repo as well
    .
    That’s a pity, I would have liked to use your OpenSUSE rpm but there you go – we can’t have everything, eh?

    Cheers

          • Hello again,

            I ordered a rebuild of the Factory rpms in order to pull the latest dependencies (in case there have been changes recently). If you’re using mixed repos I’m afraid you are on your own, I don’t think it’s supported.

            • Good Evening,

              It is good of you to consider a rebuild of Factory rpms.
              It would be difficult to find an openSUSE, Tumbleweed or Factory user who did not use mixed repos. For example – Packman repo for multimedia. I wouldn’t be on my own or lack support.

              I thought it courteous to let you know that I had found a problem.

              I’ll try the new RPM builds soon.

              Thanks again for your responses,
              Hugh

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s