joelburget / slimlock Goto Github PK

hi im trying to install slimlock but when I try to run the commands " make " and " sudo make install " its shows me this text. what should i do

g++ -Wall -I. -I/usr/include/freetype2 -I/usr/include/libpng16 -pthread -DPACKAGE="slimlock" -DVERSION="0.11" -DPKGDATADIR="/usr/share/slim" -DSYSCONFDIR="/etc" -c panel.cpp -o panel.o
panel.cpp: In constructor ‘Panel::Panel(Display*, int, Window, Cfg*, const std::string&)’:
panel.cpp:47:15: error: ordered comparison of pointer with integer zero (‘GC’ {aka ‘_XGC*’} and ‘int’)
47 | if (WinGC < 0) {
| ~~~~~~^~~
make: *** [Makefile:29: panel.o] Error 1

Hello, I usually lock my screen with slimlock and then I suspend my computer closing the lid (thanks to pm-suspend).
But after waking up, I'm prompted to type my password to unlock the screen, and once I unlock it, the mouse pointer disappears !
The mouse is still functional but his cursor is hidden...

Hi,

Could you add fprintd support for slimlock? It would be great.

solved: if you come across this issue and you are using gentoo, make sure you emerged imlib2 with useflag "png" enabled. that's it, pretty much. thanks @bryanbickford for pointing that out.

hi joel :)

i just downloaded the latest source 0.10.2, compiling and installing was working just without any problems. (using gentoo @ armv7l dynabook)

but starting the programm fails with the following message:
Slimlock: could not load panel image for theme 'slim-gentoo-simple'

i was looking at the source in panel.cpp and found the piece of code at line 107+
it seems it could not read the panel image indeed. now i added a line to the panel.cpp to print out the panelpng.c_str() variable to find out the full path and to verify the image is missing. well, the path was /usr/share/slim/themes/slim-gentoo-simple/panel.png - the path is correct and the image is existing. but it still tells me it can not be loaded.

btw, the same applies to background image: image is existing, but still can not be loaded.

slim is working without problems and displays correctly. slimlock - no idea what's wrong there....

cheers
donc_oe

hi,

i recently noticed that i can bypass slimlock after long times of inactivity. if i don't use the computer for more than 24h (estimated) i can unlock the screen without entering a password: moving the mouse displays the slimlock login screen, but pressing any key removes the lockscreen without entering a password.

while browsing the internet i found a similar problem posted by an arch linux user - https://bbs.archlinux.org/viewtopic.php?id=134300

i'm using gentoo with slimlock v0.11...

cheers

I have installed slimlock-0.11 in gentoo. Many times after unlocking I get a segfault.

The segfault ocurrs at line 228 in simlock.cpp (XCloseDisplay)

(gdb) bt
#0 0x00007ffff5eed8e8 in ?? () from /lib64/libc.so.6
#1 0x00007ffff5eee1a8 in ?? () from /lib64/libc.so.6
#2 0x00007ffff5ef148c in free () from /lib64/libc.so.6
#3 0x00007ffff7b4319c in XkbFreeClientMap () from /usr/lib64/libX11.so.6
#4 0x00007ffff7b45a8d in XkbFreeKeyboard () from /usr/lib64/libX11.so.6
#5 0x00007ffff7b38475 in ?? () from /usr/lib64/libX11.so.6
#6 0x00007ffff7ad2357 in _XFreeDisplayStructure () from /usr/lib64/libX11.so.6
#7 0x00007ffff7abdebf in XCloseDisplay () from /usr/lib64/libX11.so.6
#8 0x0000000000413d35 in main (argc=1, argv=0x7fffffffdf88) at slimlock.cpp:228

    themefile = "/usr/share/slim/themes/slim-gentoo-simple/slim.theme"
    themedir = "/usr/share/slim/themes/slim-gentoo-simple"
    ret = 0
    rc = -1
    themebase = "/usr/share/slim/themes/"
    loaded = true
    display = 0x7fffffffef44 ":0.0"
    cfg_dpms_off = 600
    raise_thread = 140737253328640
    wa = {background_pixmap = 8431389920, background_pixel = 0, border_pixmap = 0, 
      border_pixel = 4203517, bit_gravity = -1, win_gravity = 1, 
      backing_store = -134402048, backing_planes = 140737329803336, 
      backing_pixel = 140737353953280, save_under = 3071272, event_mask = 0, 
      do_not_propagate_mask = 4294967295, override_redirect = 1, 
      colormap = 140737329825200, cursor = 140737353953280}
    root = 172
    prev_fn = 0
    lock_file = -1
    cfg_passwd_timeout = 2
    pos = 18446744073709551615
    cfg_dpms_standby = 60

I just built it on debian wheezy, and did a "make install", and now

msoulier@cappuccino:~$ slimlock
slimlock: Failed to open default theme file /usr/share/slim/themes/default/slim.theme

shouldn't the install put a default theme there?

I do not think that you plan this but hell, here it is. Please add dual screen cap for Slimlock, now when I use dual screen (separate screens), slimlock takes two screens like it was one :)

Ahoy,

First, neat screen locker :-)

I am running Version 0.11-1 of slimlock on my machine, and something strange is happening which I am hoping you can help me understand; either I am not using slimlock correctly, or there is an issue with slimlock which I am hoping you can address.

When I step away from my computer, I run

xautolock -locknow

When I arrive back at my computer within a couple of hours afterwards, I get the desired effect: The slim-themed slimlock screensaver appears, and I can type my password to unlock my X session.

When I arrive at my computer the next day, however, I get the screensaver, but nothing happens when I type. I need to SSH to my computer and kill -9 $(pidof slimlock) to access my session again. Needless to say, this is quite annoying.

The content of my ~/.xinitrc:

#!/bin/bash
xsetroot -cursor_name left_ptr
xautolock -locker slimlock -time 10 &
setxkbmap -model pc -layout us -variant altgr-intl
exec xmonad
xautolock -exit

The content of my /etc/slimlock.conf:

dpms_standby_timeout            60
dpms_off_timeout                600

wrong_passwd_timeout            2
passwd_feedback_x               50%
passwd_feedback_y               10%
passwd_feedback_msg             Authentication failed
show_username                   1
show_welcome_msg                0
tty_lock                        0

All the best,
Willard.

Problems after update today,

$ ./slimlock
X Error of failed request: BadRRCrtc (invalid Crtc parameter)
Major opcode of failed request: 153 (RANDR)
Minor opcode of failed request: 20 (RRGetCrtcInfo)
Crtc id in failed request: 0x0
Serial number of failed request: 18
Current serial number in output stream: 18

$ slimlock -v
slimlock-0.11, © 2010-2012 Joel Burget

Please help me, thanks

Building on ArchLinux (and possibly other distros) fails due to DSOLinkChange. Please refer to this mailing list thread aswell as this wiki page on the fedora wiki.

Fixing the issue is as simple as adding -lXext to LIBS in the makefile.

"Did a quick test with the newest version and pm-suspend/s2disk continues not to do anything after slimlock has launched. It happens right on the first try so I don't think the problem was the fact that you didn't unlock it afterwards but rather the lock itself."

"Notice that I still can't hibernate while using slimlock (using i3lock for the time being)"

This is pretty slick. I'd like to get it added to the main Portage tree of Gentoo.

Before I can offer it to the masses, though, it'd be really nice to have proper tarballs to download rather than grabbing a tag snapshot.

Works fine except messagess in console:

$ ./slimlock 
error opening console: Permission denied
error locking console: Bad file descriptor
error unlocking console: Bad file descriptor

"Since the upgrade to 0.10.1 it sometimes freezes when I resume from suspend (cannot type anything). The mouse still moves. I have to kill my computer since I cannot switch tty." - aur comment