Description of problem: Steps to Reproduce: 1. I make an installation as shown in the bug report # 575 2. I run the command sh /usr/share/bootsplash/scripts/switch-themes Mageia-Default 3. I get the message Can't call method "get_resolution" on an undefined value at -e line1. Reproducible: Steps to Reproduce:
I'm quite not sure but bootsplash should be the old graphical boot process (last used Mandriva 2009.0?!). We actually use plymouth for that. To set the plymouth-theme use: plymouth-set-default-theme -R Mageia-Default Are you facing problems with the graphical boot process or why do you try to set it manually? Regards, TeaAge
CC: (none) => tvl83
(In reply to comment #1) > I'm quite not sure but bootsplash should be the old graphical boot process > (last used Mandriva 2009.0?!). We actually use plymouth for that. > To set the plymouth-theme use: > plymouth-set-default-theme -R Mageia-Default > > Are you facing problems with the graphical boot process or why do you try to > set it manually? > > Regards, > TeaAge If you check /usr/share/bootsplash/scripts/switch-themes, you'll see it's using plymouth.
@TeaAge The command "sh /usr/share/bootsplash/scripts/switch-themes" is simply used to create the file /usr/share/mga/backgrounds/default.jpg This file is currently not automatically created.
Hello, I think I found the source of the problem. During the installation of themes Mageia, there is yet no file /etc/X11/xorg.conf. This comes from the fact that I'm starting a minimal installation without X server. It is in a second step that I installed the packages I really need. The solution is to install the X server from the beginning. However, this solution will install about 130 packages which I do not need. I open another bug report for this.
Status: NEW => RESOLVEDResolution: (none) => FIXED
Reopening, there's a missing dependency somewhere, if /usr/share/bootsplash/scripts/switch-themes requires the get_resolution function from drak* then it should depend on the package that has that function. (My guess is drakx-kbd-mouse-x11). Adding drakx people to CC.
Status: RESOLVED => REOPENEDCC: (none) => mageia, pterjan, thierry.vignaudResolution: FIXED => (none)
(In reply to comment #5) > Reopening, there's a missing dependency somewhere, if > /usr/share/bootsplash/scripts/switch-themes requires the get_resolution > function from drak* then it should depend on the package that has that > function. (My guess is drakx-kbd-mouse-x11). > Please disregard this, it's totally wrong.
I think the file /etc/X11/xorg.conf is created during the initial installation of Mageia, in step "resume, display server configuration". If that is the case, it is normal not to have this file when the X server is not installed. In any case, just install X from the start that everything works. It's finally a logical choice to do, at the initial installation of Mageia. I had done differently because, with Mandriva, a minimal install with X was installing too many unnecessary packages. Is still the case with Mageia (See bug 609). I think that solving the bug 609, and the bug 576 will automatically be obsolete.
OK, closing this one back.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
You were right, pterjan investigated the issue yesterday, and it gives that error if xorg.conf isn't available on the system (which would happen if you didn't configure X during the installation or if you're using a headless chroot).
*** Bug 5822 has been marked as a duplicate of this bug. ***
CC: (none) => lists.jjorge
(In reply to comment #10) > *** Bug 5822 has been marked as a duplicate of this bug. *** bug valid in cauldron again
Status: RESOLVED => REOPENEDResolution: FIXED => (none)Source RPM: (none) => mageia-theme
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
Keywords: (none) => NEEDINFO
Given the various problems encountered with this method of installation, I adopted another method. I can no longer rule. For me, the report can be closed.
CC: (none) => malo
Keywords: NEEDINFO => (none)
It seems that this bug disturbs any more nobody.
Status: REOPENED => RESOLVEDResolution: (none) => WONTFIX