Bug 576

Summary: Error with Mageia-Default theme
Product: Mageia Reporter: Georges Eckenschwiller <paiiou>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Normal CC: lists.jjorge, mageia, pmdenielou, pterjan, thierry.vignaud, tvl83
Version: Cauldron   
Target Milestone: ---   
Hardware: i586   
OS: Linux   
Whiteboard:
Source RPM: mageia-theme CVE:
Status comment:

Description Georges Eckenschwiller 2011-03-28 11:21:14 CEST
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:
Comment 1 Thorsten vanLil 2011-03-30 14:32:41 CEST
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

Comment 2 Ahmad Samir 2011-03-30 17:06:07 CEST
(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.
Comment 3 Georges Eckenschwiller 2011-03-30 20:29:50 CEST
@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.
Comment 4 Georges Eckenschwiller 2011-04-01 11:07:56 CEST
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 => RESOLVED
Resolution: (none) => FIXED

Comment 5 Ahmad Samir 2011-04-09 21:45:35 CEST
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 => REOPENED
CC: (none) => mageia, pterjan, thierry.vignaud
Resolution: FIXED => (none)

Comment 6 Ahmad Samir 2011-04-16 01:48:45 CEST
(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.
Comment 7 Georges Eckenschwiller 2011-04-17 10:01:50 CEST
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.
Comment 8 Ahmad Samir 2011-05-12 03:24:35 CEST
OK, closing this one back.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

Comment 9 Ahmad Samir 2011-05-16 18:46:22 CEST
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).
Comment 10 Manuel Hiebel 2012-05-11 01:31:52 CEST
*** Bug 5822 has been marked as a duplicate of this bug. ***

CC: (none) => lists.jjorge

Comment 11 Manuel Hiebel 2012-05-11 01:33:04 CEST
(In reply to comment #10)
> *** Bug 5822 has been marked as a duplicate of this bug. ***

bug valid in cauldron again

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)
Source RPM: (none) => mageia-theme

Comment 12 Marja Van Waes 2012-05-26 13:02:32 CEST
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

Comment 13 Georges Eckenschwiller 2012-06-02 18:01:23 CEST
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.
Malo DeniƩlou 2012-06-11 00:59:09 CEST

CC: (none) => malo

Manuel Hiebel 2012-06-27 21:52:40 CEST

Keywords: NEEDINFO => (none)

Comment 14 Georges Eckenschwiller 2012-07-02 07:19:43 CEST
It seems that this bug disturbs any more nobody.

Status: REOPENED => RESOLVED
Resolution: (none) => WONTFIX