[SOLVED] Unable to lock my system

linux_user · 2018-10-13 16:51:26

I am unable to lock my desktop. Super + L and 'Lock Screen' from main menu throws this error.

Strangely, I do not get that error all the time, but only at certain times. Most of the time, there is literally nothing that is happening during both methods of locking the system.

Last edited by linux_user (2018-10-19 10:06:26)

damo · 2018-10-13 18:49:36

Check your menu.xml for typos
Check your rc.xml - is Super+L also being used for the Help menu?

Does the problem persist if you copy in the default menu.xml from /usr/share/bunsen/skel/.config/openbox?

linux_user · 2018-10-13 19:10:30

damo wrote:

Check your menu.xml for typos
Check your rc.xml - is Super+L also being used for the Help menu?

From what I have checked and with my little knowledge, there are no typos.

damo wrote:

Does the problem persist if you copy in the default menu.xml from /usr/share/bunsen/skel/.config/openbox?

I replaced the files, restarted and yet the problem persists. Had the issue been with typos, I guess the default files would have solved the problem.

I further checked the lines where locking was specified in menu.xml.

<item label="Lock Screen">
    <action name="Execute">
        <command>
            bl-lock
         </command>
    </action>
</item>
<item label="Exit">
    <action name="Execute">
        <command>
            bl-exit
        </command>
    </action>
</item>

On dmenu, executing bl-exit brings up the exit window as its supposed to do. However executing bl-exit throws that same error.

ohnonot · 2018-10-14 09:49:16

please be precise.
does this happen only when you select that from the menu, or use the hotkey? or both for both commands?
what are the exact hotkeys you use?

do you always get the error about the help pipemenu, or others also?

Last edited by ohnonot (2018-10-14 09:50:23)

linux_user · 2018-10-14 14:11:34

ohnonot wrote:

please be precise.
does this happen only when you select that from the menu, or use the hotkey? or both for both commands?
what are the exact hotkeys you use?

I try to lock the desktop using all the three methods,

Super + L
Main menu > Exit
bl-lock from dmenu or run program window (Alt+F3)

Most of the time, there is nothing that happens when I lock using any/all of the above methods. But at times, I get the error attached in the screenshot.

Today, I tried locking using the terminal, typing bl-lock command, and here's the output.

toor@linux:~$ bl-lock 
/usr/bin/bl-lock: light-locker-command no such command.

ohnonot wrote:

do you always get the error about the help pipemenu, or others also?

I do not get any other errors, nor do I get the pipemenu error other than when locking the desktop at times.

S7.L · 2018-10-14 14:40:22

Console output might help, what is displayed when you run bl-lock from the terminal?

Have you tried another screen locker like say slock or i3lock ?

Slock is in suckless tools sorry, so you have to install this package i think.

apt-get install suckless-tools

Last edited by S7.L (2018-10-14 14:44:24)

linux_user · 2018-10-14 15:03:34

S7.L wrote:

Console output might help, what is displayed when you run bl-lock from the terminal?

As mentioned in my earlier post, this is the console/terminal output.

toor@linux:~$ bl-lock 
/usr/bin/bl-lock: light-locker-command no such command.

S7.L wrote:

Have you tried another screen locker like say slock or i3lock ?
Slock is in suckless tools sorry, so you have to install this package i think.
apt-get install suckless-tools

I haven't tried another screen locker. Nor am I a big fan of trying it. I want to fix my current issue.

S7.L · 2018-10-14 15:15:30

sorry my bad i didnt see that you had posted terminal output linux_user.

My thinking on the use of a separate screen locker might help with diagnosing the problem with bl-lock, so if say i3lock works then you have some sort of baseline to work with.

S7.L · 2018-10-14 15:24:43

I think maybe your script is missing a parameter.

bl-lock a wrapper for the 'light-locker-command -l' command

But your terminal output says

/usr/bin/bl-lock: light-locker-command no such command.

Possibly the wrapper script is missing the lock command.

LOCK_COMMAND=(light-locker-command -l)

the bl-lock wrapper script should look like this in /usr/bin/bl-lock:

#!/bin/bash
#
#    bl-lock: a wrapper for the 'light-locker-command -l' command.
#    If running in live mode, offer up a prompt detailing the live session password.
#    Else, run light-locker-command -l.
#    Copyright (C) 2012 Philip Newborough   <corenominal@corenominal.org>
#    Copyright (C) 2015-2016  John Crawley <john@bunsenlabs.org>
#
#    This program is free software: you can redistribute it and/or modify
#    it under the terms of the GNU General Public License as published by
#    the Free Software Foundation, either version 3 of the License, or
#    (at your option) any later version.
#
#    This program is distributed in the hope that it will be useful,
#    but WITHOUT ANY WARRANTY; without even the implied warranty of
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#    GNU General Public License for more details.
#
#    You should have received a copy of the GNU General Public License
#    along with this program.  If not, see <http://www.gnu.org/licenses/>.

LOCK_COMMAND=(light-locker-command -l)

HELP="    bl-lock a wrapper for the 'light-locker-command -l' command

Options:
    -h --help   show this message

No other options are supported.

If running in live mode, offer up a prompt detailing the live session password.
Else, run '${LOCK_COMMAND[*]}'
"
# look for a help option somewhere
for i in "$@"
do
    case "$i" in
    -h|--help)
        echo "$HELP"
        exit 0
        ;;
    esac
done

which ${LOCK_COMMAND[0]} >/dev/null 2>&1 || {
    echo "$0: ${LOCK_COMMAND[0]} no such command." >&2
    exit 1
}

if [[ -d /lib/live && ! -f $HOME/.config/bunsen/bl-lock ]]; then
    yad --image='bunsenlabs' --window-icon='distributor-logo-bunsenlabs' --center --borders=20 --button=gtk-ok --fixed --on-top --title='Lock screen info:' --text='Lock screen has detected you are running a live session.\nThe username needed to unlock the screen is "user" and the password is "live".\nThis notice will only be displayed once per live session.'
    mkdir -p "$HOME/.config/bunsen"
    touch "$HOME/.config/bunsen/bl-lock"
fi

"${LOCK_COMMAND[@]}"

exit 0

Last edited by S7.L (2018-10-14 15:29:43)

linux_user · 2018-10-14 17:46:54

S7.L wrote:

I think maybe your script is missing a parameter.
the bl-lock wrapper script should look like this in /usr/bin/bl-lock:

#!/bin/bash
#
#    bl-lock: a wrapper for the 'light-locker-command -l' command.
#    If running in live mode, offer up a prompt detailing the live session password.
#    Else, run light-locker-command -l.
#    Copyright (C) 2012 Philip Newborough   <corenominal@corenominal.org>
#    Copyright (C) 2015-2016  John Crawley <john@bunsenlabs.org>
#
#    This program is free software: you can redistribute it and/or modify
#    it under the terms of the GNU General Public License as published by
#    the Free Software Foundation, either version 3 of the License, or
#    (at your option) any later version.
#
#    This program is distributed in the hope that it will be useful,
#    but WITHOUT ANY WARRANTY; without even the implied warranty of
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#    GNU General Public License for more details.
#
#    You should have received a copy of the GNU General Public License
#    along with this program.  If not, see <http://www.gnu.org/licenses/>.

LOCK_COMMAND=(light-locker-command -l)

HELP="    bl-lock a wrapper for the 'light-locker-command -l' command

Options:
    -h --help   show this message

No other options are supported.

If running in live mode, offer up a prompt detailing the live session password.
Else, run '${LOCK_COMMAND[*]}'
"
# look for a help option somewhere
for i in "$@"
do
    case "$i" in
    -h|--help)
        echo "$HELP"
        exit 0
        ;;
    esac
done

which ${LOCK_COMMAND[0]} >/dev/null 2>&1 || {
    echo "$0: ${LOCK_COMMAND[0]} no such command." >&2
    exit 1
}

if [[ -d /lib/live && ! -f $HOME/.config/bunsen/bl-lock ]]; then
    yad --image='bunsenlabs' --window-icon='distributor-logo-bunsenlabs' --center --borders=20 --button=gtk-ok --fixed --on-top --title='Lock screen info:' --text='Lock screen has detected you are running a live session.\nThe username needed to unlock the screen is "user" and the password is "live".\nThis notice will only be displayed once per live session.'
    mkdir -p "$HOME/.config/bunsen"
    touch "$HOME/.config/bunsen/bl-lock"
fi

"${LOCK_COMMAND[@]}"

exit 0

I checked and the script is same. https://www.diffchecker.com/7vFCinr5

Last edited by linux_user (2018-10-14 17:48:24)

ohnonot · 2018-10-15 04:54:51

linux_user wrote:

I try to lock the desktop using all the three methods,
Super + L
Main menu > Exit
bl-lock from dmenu or run program window (Alt+F3)
Most of the time, there is nothing that happens when I lock using any/all of the above methods. But at times, I get the error attached in the screenshot.
ohnonot wrote:
do you always get the error about the help pipemenu, or others also?
I do not get any other errors, nor do I get the pipemenu error other than when locking the desktop at times.

what i meant: do you always get that error message specifically about the help pipemenu?
because there's no mention of that inside bl-lock.
i surmise that your rc.xml & menu.xml are messed up.
please post both in their entirety.

johnraff · 2018-10-15 06:18:57

Make sure you have the light-locker package installed.

S7.L · 2018-10-15 16:05:59

johnraff wrote:

Make sure you have the light-locker package installed.

I dont have bunsenlabs installed anymore due to some hard disk failures and had to get a new one (not due to bunsenlabs, just old hardware), but i have to ask is light-locker not packaged with the iso?

Ive never had any use for a screen locker so just curious.

Last edited by S7.L (2018-10-15 16:11:41)

johnraff · 2018-10-16 07:56:35

light-locker is indeed installed with BunsenLabs, but you might consider checking if it's still on your system.

linux_user · 2018-10-17 13:42:44

johnraff wrote:

Make sure you have the light-locker package installed.

Yes that worked. There were no light-locker and light-locker-command packages in the system. So I installed the package,

sudo apt install light-locker

I guess my menu.xml is messed up. Graphics, places, recent files, display keybinds, help and support show no sub menus. And errors pop us saying,

Failed to execute command from pipe-menu "bl-kb-pipemenu":
Failed to execute child process "bl-kb-pipemenu" (No such file or directory)

Likewise, I get for bl-multimedia-pipemenu, bl-places-pipemenu, bl-recent-files-pipemenu-rl15 and for menus mentioned above.

I compared by menu.xml with the menu.xml of my live working persistent USB stick for any changes. I couldn't find any expect that for 'Welcome to Bunsenlabs live' entry. I have changed keybindings for dmenu in both. The command for browser has been changed to firefox as well.

Last edited by linux_user (2018-10-19 10:09:00)

johnraff · 2018-10-18 07:35:53

This sounds like another missing package - check for bunsen-pipemenus.

How did you install your BunsenLabs system?

linux_user · 2018-10-19 10:06:01

sudo apt install bunsen-pipemenus

This solved it.

I installed the OS the usual way, using the live USB stick. It is actually many months old in fact and all were working perfectly fine. The system remained unused for the last couple of months in fact since I was traveling. Upon returning, I did an update/upgrade of the system. Over 70+ packages were upgraded. I am not sure when and where did bunsen-pipemenus and light-locker were removed.

johnraff · 2018-10-20 05:43:50

You could check for other possible missing packages like this:

apt-get --simulate install --no-install-recommends bunsen-meta-all

and see what get's printed out under the "The following NEW packages will be installed:" line. If there are a lot of packages there, especially any bunsen-something packages, then you may want to install those too.

linux_user · 2018-10-20 12:29:59

johnraff wrote:

You could check for other possible missing packages like this:
apt-get --simulate install --no-install-recommends bunsen-meta-all
and see what get's printed out under the "The following NEW packages will be installed:" line. If there are a lot of packages there, especially any bunsen-something packages, then you may want to install those too.

Thanks for that, this is what I get

The following NEW packages will be installed:
  bunsen-meta-all firefox-esr gnumeric libreoffice-base-core libreoffice-common
  libreoffice-core libreoffice-gtk libreoffice-gtk2 libreoffice-style-galaxy
  libreoffice-systray libreoffice-writer transmission-gtk

When trying to install bunsen-meta-all using sudo apt install bunsen-meta-all, I get the list of the same packages.

The following NEW packages will be installed:
  bunsen-meta-all firefox-esr gnumeric gnumeric-doc libpaper-utils libpython3.5 libreoffice-base-core libreoffice-common libreoffice-core libreoffice-gtk
  libreoffice-gtk2 libreoffice-math libreoffice-style-galaxy libreoffice-style-tango libreoffice-systray libreoffice-writer lp-solve python3-uno
  transmission-gtk

So bunsen-meta-all doesn't install anything bunsenish in itself. I guess everything is fine at the moment.

johnraff · 2018-10-21 05:28:59

Yes it looks as if you've already got everything you need. (Presuming you don't want Firefox, Libreoffice or Transmission.)

bunsen-meta-all depends on the BunsenLabs apps collection, but doesn't install anything itself. If anything had been missing, installing b-m-a would have pulled it in as a dependency.

#1 2018-10-13 16:51:26

[SOLVED] Unable to lock my system

#2 2018-10-13 18:49:36

Re: [SOLVED] Unable to lock my system

#3 2018-10-13 19:10:30

Re: [SOLVED] Unable to lock my system

#4 2018-10-14 09:49:16

Re: [SOLVED] Unable to lock my system

#5 2018-10-14 14:11:34

Re: [SOLVED] Unable to lock my system

#6 2018-10-14 14:40:22

Re: [SOLVED] Unable to lock my system

#7 2018-10-14 15:03:34

Re: [SOLVED] Unable to lock my system

#8 2018-10-14 15:15:30

Re: [SOLVED] Unable to lock my system

#9 2018-10-14 15:24:43

Re: [SOLVED] Unable to lock my system

#10 2018-10-14 17:46:54

Re: [SOLVED] Unable to lock my system

#11 2018-10-15 04:54:51

Re: [SOLVED] Unable to lock my system

#12 2018-10-15 06:18:57

Re: [SOLVED] Unable to lock my system

#13 2018-10-15 16:05:59

Re: [SOLVED] Unable to lock my system

#14 2018-10-16 07:56:35

Re: [SOLVED] Unable to lock my system

#15 2018-10-17 13:42:44

Re: [SOLVED] Unable to lock my system

#16 2018-10-18 07:35:53

Re: [SOLVED] Unable to lock my system

#17 2018-10-19 10:06:01

Re: [SOLVED] Unable to lock my system

#18 2018-10-20 05:43:50

Re: [SOLVED] Unable to lock my system

#19 2018-10-20 12:29:59

Re: [SOLVED] Unable to lock my system

#20 2018-10-21 05:28:59

Re: [SOLVED] Unable to lock my system

Board footer