2012-02-10T11:23:35ZFluxBBhttps://bbs.archlinux.org/viewtopic.php?id=124268Thanks for the responses. Ready to lock out ]]>https://bbs.archlinux.org/profile.php?id=507082012-02-10T11:23:35Zhttps://bbs.archlinux.org/viewtopic.php?pid=1055477#p1055477My problem with segfault has solved after removing the simlink ~/.icons/default that I had in my homedir.]]>https://bbs.archlinux.org/profile.php?id=553522012-02-10T10:52:33Zhttps://bbs.archlinux.org/viewtopic.php?pid=1055475#p1055475Any body find a solution ? I am in the same boat ]]>https://bbs.archlinux.org/profile.php?id=507082012-01-08T14:30:24Zhttps://bbs.archlinux.org/viewtopic.php?pid=1037969#p1037969@joelb Me not. Also I tried some other lockers as temporary substitution and some of them throwed "Segmentation fault", too. It was: xscreensaver (!), slock and some other (I didn't remember).]]>https://bbs.archlinux.org/profile.php?id=553522011-12-22T21:45:21Zhttps://bbs.archlinux.org/viewtopic.php?pid=1031451#p1031451@sgtpep @akillito does either of you have experience with GDB and would be willing to help debug the problem?]]>https://bbs.archlinux.org/profile.php?id=424102011-12-22T20:49:37Zhttps://bbs.archlinux.org/viewtopic.php?pid=1031424#p1031424I have the same problem. Practically it can be solved by downgrading to previous version of slimlock (in case it was updated during some recent upgrade). But I cleared my pacman packages cache, so I can't try it out by myself.]]>https://bbs.archlinux.org/profile.php?id=553522011-12-22T18:36:49Zhttps://bbs.archlinux.org/viewtopic.php?pid=1031386#p1031386After updating my system, xmonad fails to spawn slimlock. I get a black screen for a moment, then back to where I was. At first, I thought this was a problem with xmonad, but running slimlock from a terminal frequently (but not always) produces a segmentation fault. Is anyone else experiencing this? Any suggestions on what to do now?]]>https://bbs.archlinux.org/profile.php?id=511602011-08-11T04:50:27Zhttps://bbs.archlinux.org/viewtopic.php?pid=974114#p974114