introducing oblogout-manjaro

[oberon]

All my hard work to make it look perfect... Just *poof* gone after the update 

I just see that my install script in the last version was crap
Will fix it for the next update.
I hope you can still reproduce those changes...
Stay tuned! ... 

[Photon]

Maybe not exactly with the panel, sorry for the misleading information. The darkened area is not filling the screen, on the bottom there is a non-darkened strip: https://dl.dropboxusercontent.com/1/view/at7w0z5pzxfjjfr/Apps/Shutter/Workspace%201_005.png I thought that the strip height is exactly that of the panel on the top of the screen, but now I tried changing the panel height and running oblogout afterwards with no change to the strip height.

[lightbeam]

Oberon, is the blurlock feature available with this?  I'm not sure how to activate it.

Also, I have Compton handling transparency for inactive windows.  Er, windows become transparent when inactive, but then the lockscreen - with HTML color or PNG/JPEG - also becomes transparent, which of course means I see both the desktop and the lockscreen.  This is why I'd prefer to just use the blurlock feature if I could.

Thanks!

[oberon]

@Photon: It does indeed look like there is somehow a reserved space. Are you sure you don't have any of the panel settings interfering?
What happens if you move the panel to the bottom. Or check if you have any leftover extra panels maybe??

@lightbeam: This is the problem with blurlock: What it does is, it takes a screenshot at the moment you launch the script, then blurs it and uses that for i3lock. That will result in a blurred oblogout-screen - not exactly what we want, is it?
I wonder if the script could be altered in a way to first close the oblogout window and then take the screenshot

[oberon]

@lightbeam: I think I found a way
I'm hatching it now ...

[oberon]

Not quite there ... maybe someone can help with this:
From oblogout.conf I am calling

Code: [Select]

[commands]
lock = blurlock
which looks like this

Code: [Select]

#!/bin/bash
# /usr/bin/blurlock

pkill oblogout &&
scrot /tmp/screenshot.png
convert /tmp/screenshot.png -blur 0x5 /tmp/screenshotblur.png
i3lock -i /tmp/screenshotblur.png(requires scrot and imagemagick)

Now what happens is this: The Oblogout window closes BUT then the screen is locked with the blurred screenshot of the desktop with Oblogout still in the picture...  How is this possible?

[oberon]

I guess the problem is that blurlock in this scenario is a child process of oblogout?
Is there a better / proper way to close that window?
The source for oblogout is here... https://github.com/Cloudef/oblogout-fork/blob/master/oblogout/__init__.py

[oberon]

@lightbeam: If you can live with oblogout still visible in the blurlock the solution is quite simple:
create the above blurlock script (executable of course) whithout that 'pkill oblogout' line and edit oblogout.conf as mentioned.

[oberon]

I got it!
You have to take the screenshot BEFORE Oblogout launches!

[oberon]

So let say you launch oblogout by keybinding. Let that keybinding call a script instead:

Code: [Select]

#!/bin/bash
#/usr/bin/oblogout_blur

scrot /tmp/screenshot.png &&
oblogoutnow in /etc/oblogout.conf you still need

Code: [Select]

[commands]
lock = blurlockand that one will look like this now

Code: [Select]

#!/bin/bash
# /usr/bin/blurlock
convert /tmp/screenshot.png -blur 0x5 /tmp/screenshotblur.png
i3lock -i /tmp/screenshotblur.png
Leaving the 'convert...' line in blurlock will save the conversion time in case you are going to use an oblogout function that does not involve screenlocking, like restart or shutdown...

[oberon]

I will package a new version of oblogout-manjaro with a proper upgrade-script and include the blurlock later tonight.
Actually I wanted to do that from the beginning but now I finally know the how!... 

[oberon]

Ok. oblogout-manjaro 20150927-1 is available in unstable and testing now 
If you call it with

Code: [Select]

oblogout it will just lock with a black screen or whatever colour or picture (only .png is allowed!) you set in /usr/bin/ob_blurlock

If you want to use it with blurlock you have to invoke it with

Code: [Select]

oblogout_blur
And this is also fixed:

==> existing oblogout.conf will be saved as /etc/oblogout.conf.bak

Sorry again for that, oleerik! 

Enjoy your locking!!

[mips]

  I'm gonna be a killjoy here, having the options in the menu is way more efficient. I recall using oblogout but on old hardware it takes time to start whereas menu options were instantanoius. Yeah I get that people like big shiny buttons, maybe I'm just weird 

[oberon]

Sure! I completely understand! In i3 I lock/suspend/... or whatever simply with <mod>+0 plus the respective letter
We just all have our shiny days sometimes ... 

[oberon]

All my hard work to make it look perfect... Just *poof* gone after the update 

Oh, or did you change the icons?? Sounds like... That would not be a good idea without backing up your customizations...