Bug 24823 - Mageia Welcome isn't displayed after installation with Plasma
Summary: Mageia Welcome isn't displayed after installation with Plasma
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia tools maintainers
QA Contact:
URL:
Whiteboard:
Keywords: 7RC
Depends on:
Blocks:
 
Reported: 2019-05-15 10:09 CEST by André DESMOTTES
Modified: 2020-08-25 08:45 CEST (History)
2 users (show)

See Also:
Source RPM:
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description André DESMOTTES 2019-05-15 10:09:55 CEST 
Description of problem:
Mageia Welcome isn't displayed after installation with Plasma

Version-Release number of selected component (if applicable):
Mageia-7-rc

How reproducible:
Each time
André DESMOTTES 2019-05-15 10:11:44 CEST

Keywords: (none) => 7RC
Hardware: All => x86_64

Comment 1 André DESMOTTES 2019-05-15 20:57:11 CEST 
I want to add that Mageia Welcome doesn't show up on BIOS/MBR systems, it is OK on UEFI/GPT ones.
Marja Van Waes 2019-05-16 19:34:54 CEST

CC: (none) => marja11, yves.brungard_mageia
Assignee: bugsquad => mageiatools

Comment 2 papoteur 2019-05-17 09:55:28 CEST 
Hi Lebarhon,
When mageiawelcome doesn't open at start, does it start with the commandline:
mageiawelcome ?
If not, what are error messages?
Is the installation keeping the /home and same user?
Comment 3 André DESMOTTES 2019-05-17 20:31:15 CEST 
Hi papoteur,

Yes, it starts with the commandline mageiawelcome.

/home not formatted keeping the same user.

I had the same problem with beta2 and beta3.
Comment 4 papoteur 2019-05-19 22:01:33 CEST 
Hello,
The automatic launch is stopped when the file ~/.config/mageiawelcome/norun.flag exists, even from previous installation.
I presume that this file exists already. Which is creation date?
Comment 5 papoteur 2020-08-25 08:45:06 CEST 
Closing as old.

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.