Comment # 18 on bug 1160995 from
(In reply to Fabian Vogt from comment #17)
> (In reply to GCC Da DiscoveryTechnologies from comment #15)
> > Found another user where kscreenlocker also crashes and asked him to collect
> > attached strace.
> 
> It crashes because nss is not allowed to open any sockets while running
> sandboxed.
> 
> Does it crash after entering the password? If so, I don't see a way around
> disabling the sandbox completely, which I'd have to discuss with upstream.
> (If so, you probably leaked your password in the strace output as it logged
> all X11 traffic as well).
> If not, the fix is either not working or not deployed.

According to the user, it "crashed by itself". So it crashed as soon as it got
activated.

> > Version of kscreenlocker package was 5.12.9-lp151.5.1 on this machine.
> 
> (In reply to GCC Da DiscoveryTechnologies from comment #16)
> > Hello Fabian,
> > 
> > is there a difference between the patch rpms you provided in comment #4
> > (version 5.12.9-lp151.5.1) and the official update in the openSUSE update
> > repo (version 5.12.9-lp151.2.4.1) ?
> 
> Nope.

Strange. I did some experiments and so far most of the crashes happened with
5.12.9-lp151.5.1 . I installed the official package 5.12.9-lp151.2.4.1 on all
systems in the meantime.

Will observe this closely and further I will install an additional system for
experiments today.


You are receiving this mail because: