Luca,
I think I may have been misunderstood; when I said it works I mean't that it 
didn't crash..
I have done some more detective work and I'm fairly certain I've found the 
issue. I have been using Roberts iso for these tests.
The problem could be that sddm does not fail gracefully on an non-existent 
file. 
/usr/sbin/nologin does not exist. If you remove just this entry from sddm.conf 
you will find that a line containing :-
HideShells=/sbin/nologin,/bin/false will boot without issue but only the first 
entry will be active (as you discovered) 
if a third existing entry is added (I used /bin/sync) the system still boots 
fine. So a third entry is parsed without issue as long as the path exists
so this looks like a bug in sddm.
I've re-tested all this with a new install and it's repeatable. 
I'll build a new version with the change and file a bug against sddm.
Best,
Colin


On Monday 07 Dec 2015 14:44:40 luca pedrielli wrote:
> Il 07/12/2015 14:30, Colin Close ha scritto:
> > Luca,
> > Well Luca I can only go by the evidence the same the "broken" conf file 
> > works perfectly in vmware and in a cooker install on real hardware.
> > Try this: Copy the three lines of offending config entry in sddm.conf and 
> > put them at the end of the file. Then comment them out in the earlier 
> > location.
> > For me VB then works with commas delimiting the fields.
> > Smells of a race condition to me.
> > Best,
> > Colin
> 
> Hi Colin,
> for several years now when there is something wrong the culprit it is 
> always VB.
> but it was never true.
> so, to avoid misunderstandings, I removed my test version in VB.
> it is useless to waste time with an environment where you do not trust.
> 
> Best, Luca.
> 
> 
> >
> >
> > On Monday 07 Dec 2015 12:23:46 luca pedrielli wrote:
> >> Il 07/12/2015 12:18, Colin Close ha scritto:
> >>> Luca,
> >>> That's a bit sneaky reading the original conf file especially when I 
> >>> specified an alternate location so it was clear that I wanted a new one.
> >>> I guess we had better file an upstream bug.
> >>> Just as a tjhought could one specify HideShells = /sbin/nologin
> >>> i.e HideShells = /usr/sbin/nologin
> >>> etc
> >>> It's weird though as parsing only fails in VirtualBox. It doesn't happen 
> >>> in VMware-playeror in a hardware install so I guess it could be some kind 
> >>> of race condition in VB.
> >>> Best,
> >>> Colin
> >> I'm surprised if you think that C++, to parse a string, works in a
> >> different way in vbox......
> >>
> >>
> >>
> >>>
> >>> On Monday 07 Dec 2015 11:40:21 luca pedrielli wrote:
> >>>> Il 07/12/2015 10:57, Colin Close ha scritto:
> >>>>> Luca,
> >>>>> It's ok... try this sddm --example-config > ~/sddm.conf.
> >>>>> If you check the file you'll find that the hideshells line is delimited 
> >>>>> by colons.
> >>>>> Phew :)
> >>>>> Colin
> >>>> you can try in this way:
> >>>>
> >>>> comment HideShells
> >>>>
> >>>> set MinimumUid=0
> >>>>
> >>>> so you can see all users.
> >>>>
> >>>> then try to set HideShells
> >>>>
> >>>> I have noticed that colons doesn't work and spaces neither
> >>>>
> >>>> and if you set only one shell it works
> >>>>
> >>>> HideShells=  for example.
> >>>>
> >>>> so i think comma is needed, but sddm parser fails somehow
> >>>>
> >>>>
> >>>>> On Monday 07 Dec 2015 10:01:44 luca pedrielli wrote:
> >>>>>> Il 07/12/2015 01:13, Colin Close ha scritto:
> >>>>>>> If you look at other multiple entries in sddmm.conf you'll notice 
> >>>>>>> that the delimiter is a ':' .
> >>>>>>> Replacing the commas with colons gives a working configuration and as 
> >>>>>>> you rightly observed Luca It now boots in VirtualBox.
> >>>>>>> Best,
> >>>>>>> Colin
> >>>>>> are you sure that with colons shells are well parsed?
> >>>>>> usually colons are used for paths.
> >>>>>>
> >>>>>>
> >>>>>>> On Saturday 05 Dec 2015 09:48:09 luca pedrielli wrote:
> >>>>>>>> commenting
> >>>>>>>>
> >>>>>>>> #HideShells=/sbin/nologin,/bin/false,/usr/sbin/nologin
> >>>>>>>>
> >>>>>>>> it works.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> Il 05/12/2015 05:55, Robert Xu ha scritto:
> >>>>>>>>> Got it. Here's the stacktrace:
> >>>>>>>>>
> >>>>>>>>> https://carousel.dropbox.com/photos/cc/WbkW5M7ylONYMYA
> >>>>>>>>>
> >>>>>>>>> Looks like it's barfing on string references (splitting by commas 
> >>>>>>>>> when
> >>>>>>>>> there is no value? No idea.)
> >>>>>>>>>
> >>>>>>>>> Anyone more C++ savvy?
> >>>>>>>>>
> >>>>>>>>> On 4 Dec 2015 12:17, "Tomasz Gajc" <[email protected]
> >>>>>>>>> <mailto:[email protected]>> wrote:
> >>>>>>>>>
> >>>>>>>>>         I've enabled debug mode in sddm so please install 0.13.0-7 
> >>>>>>>>> version
> >>>>>>>>>
> >>>>>>>>>         https://abf.io/build_lists/2603793
> >>>>>>>>>
> >>>>>>>>>         2015-12-03 15:47 GMT+01:00 Robert Xu <[email protected]
> >>>>>>>>>         <mailto:[email protected]>>:
> >>>>>>>>>
> >>>>>>>>>             I checked the coredump - it's crashing at configuration:
> >>>>>>>>>
> >>>>>>>>>             
> >>>>>>>>> https://github.com/sddm/sddm/blob/master/src/common/ConfigReader.cpp#L133
> >>>>>>>>>
> >>>>>>>>>             
> >>>>>>>>> https://www.dropbox.com/s/f1kz9ljbs5yjg33/Screenshot%202015-12-03%2009.45.37.png?dl=0
> >>>>>>>>>
> >>>>>>>>>             It's crashing on one of the trimmed() areas, but I 
> >>>>>>>>> can't check
> >>>>>>>>>             further
> >>>>>>>>>             because there's a lack of debug information (and no 
> >>>>>>>>> debuginfo
> >>>>>>>>>             packages...)
> >>>>>>>>>
> >>>>>>>>>             On 2 December 2015 at 12:10, Tomasz Gajc 
> >>>>>>>>> <[email protected]
> >>>>>>>>>             <mailto:[email protected]>> wrote:
> >>>>>>>>>             >
> >>>>>>>>>             > It's virtualbox issue.
> >>>>>>>>>             >
> >>>>>>>>>             > To clear things up. SDDM is using advanced OpenGL 
> >>>>>>>>> features
> >>>>>>>>>             through Qt5. In
> >>>>>>>>>             > case of virtualbox there is a well know issue that 
> >>>>>>>>> after
> >>>>>>>>>             some 4.x version
> >>>>>>>>>             > vbox lost it's ability to properly handle OpenGL (3D
> >>>>>>>>>             acceleration).
> >>>>>>>>>             > Make sure you have installed latest vbox additions,
> >>>>>>>>>             sometimes it helps.
> >>>>>>>>>             >
> >>>>>>>>>             >
> >>>>>>>>>             > My suggestion (also for myself :) is to use different
> >>>>>>>>>             virtualization tool,
> >>>>>>>>>             > as vbox is becoming dead end.
> >>>>>>>>>             >
> >>>>>>>>>             > _______________________________________________
> >>>>>>>>>             > OM-Cooker mailing list
> >>>>>>>>>             > [email protected]
> >>>>>>>>>             <mailto:[email protected]>
> >>>>>>>>>             >
> >>>>>>>>>             
> >>>>>>>>> http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>             --
> >>>>>>>>>             cheers, Robert :: github.com/robxu9 
> >>>>>>>>> <http://github.com/robxu9>
> >>>>>>>>>             _______________________________________________
> >>>>>>>>>             OM-Cooker mailing list
> >>>>>>>>>             [email protected]
> >>>>>>>>>             <mailto:[email protected]>
> >>>>>>>>>             
> >>>>>>>>> http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>         _______________________________________________
> >>>>>>>>>         OM-Cooker mailing list
> >>>>>>>>>         [email protected] 
> >>>>>>>>> <mailto:[email protected]>
> >>>>>>>>>         
> >>>>>>>>> http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> _______________________________________________
> >>>>>>>>> OM-Cooker mailing list
> >>>>>>>>> [email protected]
> >>>>>>>>> http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
> >>>>>>> _______________________________________________
> >>>>>>> OM-Cooker mailing list
> >>>>>>> [email protected]
> >>>>>>> http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
> >>>>>>> .
> >>>>>>>
> >>>>> _______________________________________________
> >>>>> OM-Cooker mailing list
> >>>>> [email protected]
> >>>>> http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
> >>>>>
> >>>>
> >>> _______________________________________________
> >>> OM-Cooker mailing list
> >>> [email protected]
> >>> http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
> >>>
> >>
> >>
> > _______________________________________________
> > OM-Cooker mailing list
> > [email protected]
> > http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org
> >
> 
> 
> 
_______________________________________________
OM-Cooker mailing list
[email protected]
http://ml.openmandriva.org/listinfo.cgi/om-cooker-openmandriva.org

Reply via email to