I can't reproduce with current Cauldron, do you have samba installed?

Status: NEW => UNCONFIRMED
Ever confirmed: 1 => 0

I can reproduce this report in mga6 upgraded from mga5.

Install drakwizard and run draksambashare and am prompted to install samba.
then configure samba using draksambashare.
Delete smb.conf and rerun draksambashare, output

'draksambashare 
Ignore the following Glib::Object::Introspection & Gtk3 warnings
Subroutine Gtk3::main redefined at /usr/lib/perl5/vendor_perl/5.22.0/Gtk3.pm line 525.
atom n� 0 is not a section'

So the question is should draksambashare wizard create smb.conf if it is missing or invalid?

My response is no. smb.conf is part of the samba-server package not draksambashare.

Any comments?

CC: (none) => nic
Status: UNCONFIRMED => NEW
Ever confirmed: 0 => 1

Confirmed, the strage is if draksambashare is run for first time works well
The issue is when you clear of remove the file smb.conf

To workarround i put some basic information in smb.conf

# Global parameters
[global]
       workgroup = HOME
       netbios name = SAMBA
       server string = Samba Server %v
       map to guest = Bad User
       log file = /var/log/samba/log.%m
       max log size = 50
       preferred master = No
       local master = No
       security = User

with that draksambashare start

(In reply to katnatek from comment #4)
> To workarround i put some basic information in smb.conf
> 
> # Global parameters
> [global]
>        workgroup = HOME
>        netbios name = SAMBA
>        server string = Samba Server %v
>        map to guest = Bad User
>        log file = /var/log/samba/log.%m
>        max log size = 50
>        preferred master = No
>        local master = No
>        security = User
> 
> with that draksambashare start

Run but stuck in the final step if you try to reconfigure samba

still valid. 

I will try to take a look

CC: (none) => mageia

what is the best ? add a dummy config file or restart the wizard ?

I would vote for the second option.

I am reviving & updating this bug because exactly the same problem has arisen with Mageia 8. This old bug has more information than the new.
Duplicate to announce.

See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=30090
Version: Cauldron => 8
Assignee: mageia => mageia
CC: mageia => lewyssmith
Source RPM: drakx-net-2.23-1.mga6.src.rpm => drakx-net-2.55-1.mga8.src.rpm

*** Bug 30252 has been marked as a duplicate of this bug. ***

CC: (none) => philippe.mallocci

update from Bug 30252: 
I didn't manage to start draksambashare with the smb.conf file provided above but it works fine with the default .conf file coming from Linux Mint. Looking forward to reading from you.

So it fails to start when there is an invalid smb.conf (which is the case when it is empty or missing). The obvious fix for it (creating a file with default values when it fails to read any part of it) would be very risky so it should probably instead ask a question like "Failed to load a valid smb.conf, start with a default configuration? WARNING any custom configuration of Samba will be lost." and not silently overwrite existing invalid config.

The suggestion in Comment 11 sound good.

Can we have this bug finally resolved?

For 9 RC, or in Cauldron after release?

CC: (none) => fri

We stopped supporting Mageia 8 almost 8 months ago 
https://blog.mageia.org/en/2023/12/30/mageia-8-end-of-life/

That means we also stopped fixing Mageia 8 bugs and that this bug report needs to be closed, regardless of whether it was fixed for Mageia 8 or not.

If this particular bug did not get fixed for Mageia 8, then we do regret that.

If this issue is still present in Mageia 9 or cauldron, then please reopen this report, write a comment and adjust the "Version:" field.

If you are not yet a member of one or our teams, then please consider becoming one. https://wiki.mageia.org/en/Contributing
Mageia is a community project, meaning that we, the users, make Mageia together.

The more active contributors we have, the more bug reports will get fixed.
Besides, being active in a team can be very rewarding. It was and is certainly rewarding to me :-D

Status: NEW => RESOLVED
Resolution: (none) => OLD