[manjaro-dev] Fwd: Re: Adding new user & MDM problem
Philip Müller
philm at manjaro.org
Fri Jan 3 12:53:20 CET 2014
Please use the attached custom.conf from my previous e-mail. Otherwise
you have to modify your include line:
Include=piotr,bernadetta
From the /usr/share/mdm/defaults.conf
#MinimalUID=100
# Users listed in Include will be included in the face browser and in the
# mdmsetup selection list for Automatic/Timed login. Users should be
separated
# by commas.
#Include=
# Users listed in Exclude are excluded from the face browser and from the
# mdmsetup selection list for Automatic/Timed login. Excluded users
will still
# be able to log in, but will have to type their username. Users should be
# separated by commas.
#Exclude=bin,daemon,adm,lp,sync,shutdown,halt,mail,news,uucp,operator,nobody,mdm,postgres,pvm,rpm,nfsnobody,pcap
# By default, an empty include list means display no users. By setting
# IncludeAll to true, the password file will be scanned and all users
will be
# displayed except users excluded via the Exclude setting and user ID's less
# than MinimalUID. Scanning the password file can be slow on systems with
# large numbers of users and this feature should not be used in such
# environments. The setting of IncludeAll does nothing if Include is
set to a
# non-empty value.
#IncludeAll=false
Am 03.01.2014 12:42, schrieb Piotr Strebski:
> I forgot: my MDM is in 1.4.6-2 version, mdm-themes in 0.1.4-2
>
> Greetings
> Piotr
>
> Dnia 3 stycznia 2014 12:31 Piotr Strebski <strebski at o2.pl> napisa?(a):
>
> I used once again modified version of custom.conf which looks as
> following:
>
> # MDM Custom Configuration file.
> #
> # This file is the appropriate place for specifying your
> customizations to the
> # MDM configuration. If you run mdmsetup, it will
> automatically edit this
> # file for you and will cause the daemon and any running MDM
> GUI programs to
> # automatically update with the new configuration. Not all
> configuration
> # options are supported by mdmsetup, so to modify some values
> it may be
> # necessary to modify this file directly by hand.
> #
> # This file overrides the default configuration settings.
> These settings
> # are stored in the MDM System Defaults configuration file,
> which is found
> # at the following location.
> #
> # /usr/share/mdm/defaults.conf.
> #
> # This file contains comments about the meaning of each
> configuration option,
> # so is also a useful reference. Also refer to the
> documentation links at
> # the end of this comment for further information. In short,
> to hand-edit
> # this file, simply add or modify the key=value combination in the
> # appropriate section in the template below this comment section.
> #
> # For example, if you want to specify a different value for
> the Enable key
> # in the "[debug]" section of your MDM System Defaults
> configuration file,
> # then add "Enable=true" in the "[debug]" section of this
> file. If the
> # key already exists in this file, then simply modify it.
> #
> # Older versions of MDM used the "mdm.conf" file for
> configuration. If your
> # system has an old mdm.conf file on the system, it will be
> used instead of
> # this file - so changes made to this file will not take
> effect. Consider
> # migrating your configuration to this file and removing the
> mdm.conf file.
> #
> # If you hand edit a MDM configuration file, you can run the
> following
> # command and the MDM daemon will immediately reflect the
> change. Any
> # running MDM GUI programs will also be notified to update
> with the new
> # configuration.
> #
> # mdmflexiserver --command="UPDATE_CONFIG <configuration key>"
> #
> # e.g, the "Enable" key in the "[debug]" section would be
> "debug/Enable".
> #
> # You can also run mdm-restart or mdm-safe-restart to cause
> MDM to restart and
> # re-read the new configuration settings. You can also
> restart MDM by sending
> # a HUP or USR1 signal to the daemon. HUP behaves like
> mdm-restart and causes
> # any user session started by MDM to exit immediately while
> USR1 behaves like
> # mdm-safe-restart and will wait until all users log out
> before restarting MDM.
> #
> # For full reference documentation see the gnome help browser
> under
> # GNOME|System category. You can also find the docs in HTML
> form on
> # http://www.gnome.org/projects/mdm/
> #
> # NOTE: Lines that begin with "#" are considered comments.
> #
> # Have fun!
>
> [daemon]
>
> DefaultSession=xfce.desktop
>
> Greeter=/usr/lib/mdm/mdmwebkit
>
> SelectLastLogin=false
>
> [security]
>
> [xdmcp]
>
> [gui]
>
> [greeter]
>
> Browser=true
>
> HTMLTheme=Clouds
>
> MinimalUID=1000
>
> IncludeAll=true
>
> DefaultFace=/home/piotr/.face
>
> DefaultWelcome=false
>
> Welcome=Witaj! :)
>
> GraphicalTheme=manjaro
>
> [chooser]
>
> [debug]
>
> # Note that to disable servers defined in the MDM System Defaults
> # configuration file (such as 0=Standard, you must put a line
> in this file
> # that says 0=inactive, as described in the Configuration
> section of the MDM
> # documentation.
> #
>
> [servers]
>
> # Also note, that if you redefine a [server-foo] section, then
> MDM will
> # use the definition in this file, not the MDM System Defaults
> configuration
> # file. It is currently not possible to disable a
> [server-foo] section
> # defined in the MDM System Defaults configuration file.
> #
>
> and nothing - bug is still the same as on earlier attached pictures.
>
> And using custom.conf attached by you ALSO do not solve the prolem
> :( On Clouds style list is still empty (I used ctrl+c and ctrl+v
> to replace content of my custom.conf file).
>
> Any other suggestions?
>
> Greetings
> piotr
>
>
> Dnia 3 stycznia 2014 12:14 Piotr Strebski <strebski at o2.pl> napisa?(a):
>
> Thanks Phil!
> In my custom.conf there were no "IncludeAll=true" string -
> I've added it, but nothing happend - same on Clouds
> and Manjaro Green MDM style.
> Command 'cat /etc/passwd | grep bernadetta' gives correct
> 'bernadetta:x:1001:100::/home/bernadetta:/bin/bash'
> I'm using Manjaro since 0.8.6 version; my current
> '/etc/mdm/custom.conf' looks as following:
>
> # MDM Custom Configuration file.
> #
> # This file is the appropriate place for specifying your
> customizations to the
> # MDM configuration. If you run mdmsetup, it will
> automatically edit this
> # file for you and will cause the daemon and any running MDM
> GUI programs to
> # automatically update with the new configuration. Not all
> configuration
> # options are supported by mdmsetup, so to modify some values
> it may be
> # necessary to modify this file directly by hand.
> #
> # This file overrides the default configuration settings.
> These settings
> # are stored in the MDM System Defaults configuration file,
> which is found
> # at the following location.
> #
> # /usr/share/mdm/defaults.conf.
> #
> # This file contains comments about the meaning of each
> configuration option,
> # so is also a useful reference. Also refer to the
> documentation links at
> # the end of this comment for further information. In short,
> to hand-edit
> # this file, simply add or modify the key=value combination in the
> # appropriate section in the template below this comment section.
> #
> # For example, if you want to specify a different value for
> the Enable key
> # in the "[debug]" section of your MDM System Defaults
> configuration file,
> # then add "Enable=true" in the "[debug]" section of this
> file. If the
> # key already exists in this file, then simply modify it.
> #
> # Older versions of MDM used the "mdm.conf" file for
> configuration. If your
> # system has an old mdm.conf file on the system, it will be
> used instead of
> # this file - so changes made to this file will not take
> effect. Consider
> # migrating your configuration to this file and removing the
> mdm.conf file.
> #
> # If you hand edit a MDM configuration file, you can run the
> following
> # command and the MDM daemon will immediately reflect the
> change. Any
> # running MDM GUI programs will also be notified to update
> with the new
> # configuration.
> #
> # mdmflexiserver --command="UPDATE_CONFIG <configuration key>"
> #
> # e.g, the "Enable" key in the "[debug]" section would be
> "debug/Enable".
> #
> # You can also run mdm-restart or mdm-safe-restart to cause
> MDM to restart and
> # re-read the new configuration settings. You can also
> restart MDM by sending
> # a HUP or USR1 signal to the daemon. HUP behaves like
> mdm-restart and causes
> # any user session started by MDM to exit immediately while
> USR1 behaves like
> # mdm-safe-restart and will wait until all users log out
> before restarting MDM.
> #
> # For full reference documentation see the gnome help browser
> under
> # GNOME|System category. You can also find the docs in HTML
> form on
> # http://www.gnome.org/projects/mdm/
> #
> # NOTE: Lines that begin with "#" are considered comments.
> #
> # Have fun!
>
> [daemon]
>
> DefaultSession=xfce.desktop
>
> Greeter=/usr/lib/mdm/mdmgreeter
>
> SelectLastLogin=false
>
> [security]
>
> [xdmcp]
>
> [gui]
>
> [greeter]
>
> Browser=true
>
> HTMLTheme=Clouds
>
> MinimalUID=1000
> IncludeAll=true
>
> DefaultFace=/home/piotr/.face
>
> DefaultWelcome=false
>
> Welcome=Witaj! :)
>
>
> Include=piotr
>
>
> GraphicalTheme=manjaro
>
> [chooser]
>
> [debug]
>
> # Note that to disable servers defined in the MDM System Defaults
> # configuration file (such as 0=Standard, you must put a line
> in this file
> # that says 0=inactive, as described in the Configuration
> section of the MDM
> # documentation.
> #
>
> [servers]
>
> # Also note, that if you redefine a [server-foo] section, then
> MDM will
> # use the definition in this file, not the MDM System Defaults
> configuration
> # file. It is currently not possible to disable a
> [server-foo] section
> # defined in the MDM System Defaults configuration file.
> #
>
> Since 0.8.6 version - as I remember - we have MDM update.
> Maybe configuration file update was broken?
>
> I'll use your defaults.conf file and give you another feedback.
>
> Thanks once again,
> Piotr
>
> Dnia 3 stycznia 2014 11:05 Philip Müller <philm at manjaro.org>
> napisa?(a):
>
> Open a terminal and do:
>
> cat /etc/passwd | grep bernadetta
> bernadetta:x:1001:100::/home/bernadetta:/bin/bash
>
> ... so you might get some users there.
>
> Then open MDM and update your config /etc/mdm/custom.conf:
>
> MinimalUID=1000
> IncludeAll=true
>
> I did it on a fresh 0.8.8.0.909 live session:
>
> cat /etc/passwd | grep testuser
> testuser:x:1001:100::/home/testuser:/bin/bash
>
> See the screenshot. Nothing to set up. I also attached the
> default custom.conf.
>
> kind regards
>
> Phil
>
>
> Am 03.01.2014 09:01, schrieb Piotr Strebski:
>
> Hi All,
>
> there is problem related with adding new user to Manjaro via
> Manjaro Settings Manager -> User Accounts and displaying new
> added user account on the login list od MDM.
> After adding new user account on MDM list (style GDM -> Manjaro
> Green MDM) there is still only one (created during installation)
> account, or the list is empty (style HTML -> Clouds).
> I'm using fully updated Manjaro XFCE edition.
>
> Look at the pictures in attachment.
>
> Any suggestions how to fix it? Do you have similar problem? Thanks
> in advance!
>
> Piotr
>
>
>
> _______________________________________________
> manjaro-dev mailing list
> manjaro-dev at manjaro.org
> http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev
>
> _______________________________________________manjaro-dev
> mailing
> listmanjaro-dev at manjaro.orghttp://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev
>
>
>
>
>
> _______________________________________________manjaro-dev mailing
> listmanjaro-dev at manjaro.org
> </?cmd=compose&to=manjaro-dev at manjaro.org>http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev
>
>
>
>
>
> _______________________________________________
> manjaro-dev mailing list
> manjaro-dev at manjaro.org
> http://lists.manjaro.org/cgi-bin/mailman/listinfo/manjaro-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.manjaro.org/pipermail/manjaro-dev/attachments/20140103/44a3b128/attachment-0001.html>
More information about the manjaro-dev
mailing list