[OBSOLETE] The bunsenlabs 'exit' menu entry

Sector11 · 2016-04-13 13:17:54

Here you go:

 13 Apr 16 @ 10:15:52 ~
  $ which -a bl-exit
/home/sector11/bin/bl-exit
/home/sector11/bin/bl-exit
 
 13 Apr 16 @ 10:16:05 ~
  $

EDIT: and just because

 13 Apr 16 @ 10:18:36 ~
  $ which -a s11-exit
/home/sector11/bin/s11-exit
/home/sector11/bin/s11-exit
 
 13 Apr 16 @ 10:18:42 ~
  $

Last edited by Sector11 (2016-04-13 13:19:19)

xaos52 · 2016-04-13 13:30:43

Strange that the same path is listed twice.
From a terminal instance, post output of

env | grep PATH

if you don't mind.

Sector11 · 2016-04-13 13:41:50

Yea, I thought so to until I saw this:

 13 Apr 16 @ 10:33:01 ~
  $ $PATH
bash: /home/sector11/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/sector11/bin: No such file or directory
 
 13 Apr 16 @ 10:33:07 ~
  $

which of course raises another Q: Why twice there? :8

Ahhhh new command - don't mine at all:

 13 Apr 16 @ 10:37:15 ~
  $ env | grep PATH
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
PATH=/home/sector11/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games:/home/sector11/bin
 
 13 Apr 16 @ 10:37:26 ~
  $

... and again twice. Well of course $PATH is $PATH no matter how you look at it.

In case you are thinking about asking: There is no $PATH set in /home/sector11/.config/openbox/autostart. I recall at one time (#! Statler I think) I had set $PATH in autostart.sh to include ~/bin

Last edited by Sector11 (2016-04-13 13:44:22)

xaos52 · 2016-04-13 13:53:54

You have /home/sector11/bin twice in your PATH. Once at the front, and once at the end.

That explains why commands in /home/sector11/bin are listed twice when you run
which -a <command>

It does not explain why bl-exit does not work for you.

Does it work if you launch 'bl-exit' from a terminal window?

Sector11 · 2016-04-13 14:14:33

And /etc/login.defs doesn't have ~/bin at all.

Don't know how to edit $PATH .

Does not work in a terminal:

 13 Apr 16 @ 11:12:36 ~
  $ bl-exit
/home/sector11/.themes/S11-NS-brushed/gtk-2.0/panel.rc:32: Unable to locate image file in pixmap_path: "shadows/window-bg.png"

... but doesn't let the terminal continue to the closing prompt.

Mine works:

Last edited by Sector11 (2016-04-13 14:17:14)

xaos52 · 2016-04-13 14:26:20

Looks like a gtk theming problem? Or else you have an entirely different script in bl-exit.

less /home/sector11/bin/bl-exit

should start with

#!/usr/bin/env python2.7
# -*- coding: utf-8 -*-
from __future__ import print_function

import os
display = os.environ.get('DISPLAY') != None

import os
import getopt
import getpass
import subprocess
import sys

me = 'bl-exit'
# Default errorMessages dict
# key = result from _can_do_it
# value = string shown in error_message_dialog
canDoItErrorMessages = dict(
    no         = "Action is not allowed.",
    na         = "Action is not available.",
    challenge  = "Action is not authorized."
)

# Translate command-line option to method - command line only
actionToMethod = dict(
    logout    = 'Logout',
    l         = 'Logout',
    suspend   = 'Suspend',
    s         = 'Suspend',
    hybridsleep = 'HybridSleep',
    y           = 'HybridSleep',
    hibernate = 'Hibernate',
/home/me/bin/bl-exit

As to setting PATH, there are different methods to do it.
Here is how I do it to prepend $HOME/bin to PATH:

file $HOME/.profile:

# ~/.profile: executed by the command interpreter for login shells.
# This file is not read by bash(1), if ~/.bash_profile or ~/.bash_login
# exists.
# see /usr/share/doc/bash/examples/startup-files for examples.
# the files are located in the bash-doc package.
#
# Modified version provided by bunsen-configs.

# the default umask is set in /etc/profile; for setting the umask
# for ssh logins, install and configure the libpam-umask package.
#umask 022

# if running bash
if [ -n "$BASH_VERSION" ]; then
    # include .bashrc if it exists
    if [ -f "$HOME/.bashrc" ]; then
	. "$HOME/.bashrc"
    fi
fi

# include sbin in PATH
if [ -d "/sbin" ] ; then
    PATH="/sbin:$PATH"
fi
if [ -d "/usr/sbin" ] ; then
    PATH="/usr/sbin:$PATH"
fi
# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Q: Does the 'official' bl-exit work for you?

Sector11 · 2016-04-13 15:21:10

Yup, that's what I have - downloaded it this morning after getting an email notification of a new post here; your post #38

These are showing here but need their own thread:

My problem is, as you noticed I have two "~/bin" in my path and I can't find were/what to edit so there is only one. But that's a different problem.

Yea, my theme is missing some .pngs - must research that some day as well

xaos52 · 2016-04-13 15:27:58

Q: Does the 'official' bl-exit work for you?

I edited my previous post to add this question.

Sector11 · 2016-04-13 15:50:19

OH sorry ... just a sec ... will go find it.

Sector11 · 2016-04-13 16:04:06

:8 Don't have it ... where can I get it?

Be right back.

OK, I have it, it works. I used it to make my modified s11-exit script at one time.

xaos52 · 2016-04-13 16:10:42

Easiest way is to re-install package bunsen-utilities:

sudo apt-get install --reinstall bunsen-utilities

This will install bl-exit at /usr/bin/bl-exit

WARNING:
This will re-install all scripts that are contained within the package.

A second method is to download the zip file from github, unzip the archive and copy that version of bl-exit to your home directory or to /usr/bin.

Sector11 · 2016-04-13 16:22:59

Sorry, I had it ... and edited my post here.

Between a mess on the streets of Buenos Aires today and my wife making her comments about it and trying to do this I don't know if I'm coming or going.

Short story: mine works, the original works, your update doesn't. Wish someone else would try, it's quite possible the noob in me messed something up, in which case if we fix it, it will be "Certified Noob Proof".

xaos52 · 2016-04-13 16:26:30

OK.
Thanks for testing it.
Lets wait for other users reactions then and take it from there.

Sector11 · 2016-04-13 16:29:20

AHHHHHHHHHH CRAP. Looking at rget

 13 Apr 16 @ 13:24:53 ~
  $ alias rget
alias rget='sudo apt-get install --reinstall --no-install-recommends'
 
 13 Apr 16 @ 13:24:58 ~
  $

and look at this ....

It doesn't work from the command line:

 
 13 Apr 16 @ 13:27:41 ~
  $ rget bunsen-utilities
alias rget = sudo apt-get install --reinstall --no-install-recommends
[sudo] password for sector11: 
Sorry, try again.
[sudo] password for sector11: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Recommended packages:
  light-locker
The following NEW packages will be installed:
  bunsen-utilities
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 31.1 kB of archives.
After this operation, 140 kB of additional disk space will be used.
Get:1 http://pkg.bunsenlabs.org/debian/ bunsen-hydrogen/main bunsen-utilities all 8.6.5-1 [31.1 kB]
Fetched 31.1 kB in 1s (28.4 kB/s)                    
Retrieving bug reports... Done
Parsing Found/Fixed information... Done
Selecting previously unselected package bunsen-utilities.
(Reading database ... 168570 files and directories currently installed.)
Preparing to unpack .../bunsen-utilities_8.6.5-1_all.deb ...
Unpacking bunsen-utilities (8.6.5-1) ...
Setting up bunsen-utilities (8.6.5-1) ...
 
 13 Apr 16 @ 13:28:05 ~
  $ bl-exit
/home/sector11/.themes/S11-NS-brushed/gtk-2.0/panel.rc:32: Unable to locate image file in pixmap_path: "shadows/window-bg.png"

Sector11 · 2016-04-13 16:32:48

I reinstalled bunsen-utilities ... bl-exit doesn't work.

xaos52 · 2016-04-13 16:35:54

I would like to get to the bottom of this.
I will instrument bl-exit with debugging information and let you know when it is ready to be tested again. Won't be for today though.

Sector11 · 2016-04-13 16:58:15

When ever you want. PM me if need be, I'll gladly test it.

Head_on_a_Stick · 2016-04-13 17:09:42

This works perfectly for me:

I've been using a slightly modified version of bl-exit for my bspwm desktops and I couldn't figure out how to remove the unwanted buttons cleanly ( :8 ) so this is very useful for me.

Great work, thanks!

Head_on_a_Stick · 2016-04-13 17:15:40

@S11: in BunsenLabs, $PATH is set in /etc/profile and ~/.profile

~/.bash_profile is also sourced on login and ~/.bashrc is sourced when you open a new terminal window.

Check all those files for your duplicate PATH entry.

Sector11 · 2016-04-13 17:28:23

AHA! ~/.bashrc

# From CrunchBang forums - add ~/bin to path
export PATH=$PATH:~/bin
# PATH="$HOME/bin:$PATH"
# export PATH="$HOME/bin:$PATH"

# enable programmable completion features (you don't need to enable
# this, if it's already enabled in /etc/bash.bashrc and /etc/profile
# sources /etc/bash.bashrc).
if [ -f /etc/bash_completion ]; then
    . /etc/bash_completion
fi

{sigh} I'm such a noob! FIXED!

Now if I can figure out why this doesn't work for me....

#41 2016-04-13 13:17:54

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#42 2016-04-13 13:30:43

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#43 2016-04-13 13:41:50

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#44 2016-04-13 13:53:54

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#45 2016-04-13 14:14:33

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#46 2016-04-13 14:26:20

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#47 2016-04-13 15:21:10

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#48 2016-04-13 15:27:58

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#49 2016-04-13 15:50:19

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#50 2016-04-13 16:04:06

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#51 2016-04-13 16:10:42

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#52 2016-04-13 16:22:59

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#53 2016-04-13 16:26:30

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#54 2016-04-13 16:29:20

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#55 2016-04-13 16:32:48

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#56 2016-04-13 16:35:54

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#57 2016-04-13 16:58:15

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#58 2016-04-13 17:09:42

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#59 2016-04-13 17:15:40

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

#60 2016-04-13 17:28:23

Re: [OBSOLETE] The bunsenlabs 'exit' menu entry

Board footer