[OBSOLETE] The bunsenlabs 'exit' menu entry

Head_on_a_Stick · 2016-04-13 17:35:12

Sector11 wrote:

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"

Looks like a theme error -- will it work if you set the theme to Raleigh?

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

Nope:

xaos52 · 2016-04-14 09:10:53

@s11,

When you run my version of the bl-exit script, you get that error message - probably produced because your theme has some missing file - and then... nothing?

You need to break (Ctrl +C) to get your prompt back. Is that correct?

Could you try starting my script under the python debugger, like this:

pdb <your path to my version of the script>
> /usr/bin/bl-exit(4)<module>()
-> import gtk
(Pdb) c
.
.
.
(Pdb) bt

I have put the answers you should provide after the (Pdb) prompt in bold.
I am interested in what the debugger returns after you entered the 'bt' command.

To exit from the debugger, type 'exit' at the prompt. (without the surrounding quotes)

Explanation:
1. The first 'c' you enter is short for 'continue'
2. The 'bt' is short for 'backtrace'
It is possible that you don't get the second (Pdb) prompt because the program hangs.
In that case 'break' it with Ctrl+c and let me know.

Thanks for your cooperation.

xaos52 · 2016-04-14 09:21:58

I would appreciate it enormously if someone else could test the new version of the bl-exit script.
You can find an explanation on how to configure it here

It works for Hoas, but does not work for Sector11.
So its a tie at the moment and it is not possible to say if the new script is the culprit or the peculiar setup of Sector11.

Thanks

Sector11 · 2016-04-14 10:06:54

xaos52 wrote:

@s11,
When you run my version of the bl-exit script, you get that error message - probably produced because your theme has some missing file - and then... nothing?
You need to break (Ctrl +C) to get your prompt back. Is that correct?

First I changed themes to: Bunsen - to eliminate my theme being the culprit.
This is after [Ctrl]+c - didn't do that before.

 14 Apr 16 @ 06:44:38 ~
  $ bl-exit
^CTraceback (most recent call last):
  File "/home/sector11/bin/bl-exit", line 362, in <module>
    main(sys.argv[1:])
  File "/home/sector11/bin/bl-exit", line 356, in main
    graphical_processing()
  File "/home/sector11/bin/bl-exit", line 345, in graphical_processing
    Blexit().main()
  File "/home/sector11/bin/bl-exit", line 160, in main
    gtk.main()
KeyboardInterrupt
 
 14 Apr 16 @ 06:44:59 ~
  $

xaos52 wrote:

Could you try starting my script under the python debugger, like this:
pdb <your path to my version of the script>
> /usr/bin/bl-exit(4)<module>()
-> import gtk
(Pdb) c
.
.
.
(Pdb) bt
I have put the answers you should provide after the (Pdb) prompt in bold.
I am interested in what the debugger returns after you entered the 'bt' command.
To exit from the debugger, type 'exit' at the prompt. (without the surrounding quotes)
Explanation:
1. The first 'c' you enter is short for 'continue'
2. The 'bt' is short for 'backtrace'
It is possible that you don't get the second (Pdb) prompt because the program hangs.
In that case 'break' it with Ctrl+c and let me know.
Thanks for your cooperation.

Cooperation isn't a problem - glad to ßeta test.
"c" needed [Ctrl]+c to continue to the next (Pdb) and a final [Ctrl]+c to exit to the prompt.

 14 Apr 16 @ 06:56:30 ~
  $ pdb /home/sector11/bin/bl-exit
> /home/sector11/bin/bl-exit(3)<module>()
-> from __future__ import print_function
(Pdb) c
^CTraceback (most recent call last):
  File "/usr/lib/python2.7/pdb.py", line 1314, in main
    pdb._runscript(mainpyfile)
  File "/usr/lib/python2.7/pdb.py", line 1233, in _runscript
    self.run(statement)
  File "/usr/lib/python2.7/bdb.py", line 400, in run
    exec cmd in globals, locals
  File "<string>", line 1, in <module>
  File "/home/sector11/bin/bl-exit", line 3, in <module>
    from __future__ import print_function
  File "/home/sector11/bin/bl-exit", line 356, in main
    graphical_processing()
  File "/home/sector11/bin/bl-exit", line 345, in graphical_processing
    Blexit().main()
  File "/home/sector11/bin/bl-exit", line 160, in main
    gtk.main()
KeyboardInterrupt
Uncaught exception. Entering post mortem debugging
Running 'cont' or 'step' will restart the program
> /home/sector11/bin/bl-exit(160)main()
-> gtk.main()
(Pdb) bt
  /usr/lib/python2.7/pdb.py(1314)main()
-> pdb._runscript(mainpyfile)
  /usr/lib/python2.7/pdb.py(1233)_runscript()
-> self.run(statement)
  /usr/lib/python2.7/bdb.py(400)run()
-> exec cmd in globals, locals
  <string>(1)<module>()
  /home/sector11/bin/bl-exit(3)<module>()
-> from __future__ import print_function
  /home/sector11/bin/bl-exit(356)main()
-> graphical_processing()
  /home/sector11/bin/bl-exit(345)graphical_processing()
-> Blexit().main()
> /home/sector11/bin/bl-exit(160)main()
-> gtk.main()
(Pdb) 
Traceback (most recent call last):
  File "/usr/bin/pdb", line 1338, in <module>
    pdb.main()
  File "/usr/lib/python2.7/pdb.py", line 1330, in main
    pdb.interaction(None, t)
  File "/usr/lib/python2.7/pdb.py", line 210, in interaction
    self.cmdloop()
  File "/usr/lib/python2.7/cmd.py", line 130, in cmdloop
    line = raw_input(self.prompt)
KeyboardInterrupt
 
 14 Apr 16 @ 06:58:01 ~
  $

... a final [Ctrl]+c brought me back out to the prompt.

NOTE: exit didn't exit:

(Pdb) exit
Post mortem debugger finished. The /home/sector11/bin/bl-exit will be restarted
> /home/sector11/bin/bl-exit(3)<module>()
-> from __future__ import print_function
(Pdb)

Another note because of this:

You can find an explanation on how to configure it here

I did nothing to configure it. Using the script as it came.

xaos52 · 2016-04-14 10:29:27

I did nothing to configure it. Using the script as it came.

That is OK.
The script should work exactly like the 'official bl-exit' without configuration file.
You only need the configuration file if you want more or less buttons than the 'official' version shows.

While I am examining the results you reported, can you run strace for me on the new script:
1. install package 'strace' if you don(t have it installed already
2. from a terminal window, run

strace -o strace -f -tT <path-to-my-bl-exit-script>

this will create a rather large file strace in your current directory.

You will have to "break" it after say 30 seconds.

Post the content of the strace file via a pastebin of your choice and give me a link to it.

Thanks

Sector11 · 2016-04-14 10:46:08

WOW I'll say big - 8632 lines in ±30seconds.

Good for a week: https://dpaste.de/sWB2/raw

Hope it helps.

xaos52 · 2016-04-14 10:48:30

Don't bother with strace any more.

I think I found the problem.
There is a new version of the script available on github.
Can you try that one.

Thanks

damo · 2016-04-14 11:34:17

Testing latest version in VBox - all seems to be working there OK

Playing with various ini entries has worked so far, even "hibernate" (NB the path in this post should be $HOME/.config/bl-exit/bl-exitrc)

I will try it on the main system after I have finished a long-running render

xaos52 · 2016-04-14 11:59:06

Thanks for testing this, damo.

I have corrected path to config file in my post #38.

damo · 2016-04-14 12:12:52

Tested with all default BL gtk themes - OK;

Tested with random and gibberish entries in the ini file - OK.

Nice work

EDIT: tested on main box, and "Hibernate" is greyed-out as expected.

xaos52 · 2016-04-14 12:18:42

Thanks, damo.

I will mark this version 2.0.0

xaos52 · 2016-04-14 12:21:30

@Sector11,
I am pretty sure this version will work for you too.

Sorry for 'blaming' your setup. It was a script error.
But I will keep calling your setup 'peculiar'

Sector11 · 2016-04-14 12:42:39

You could get away with calling me 'peculiar', but the new script works just fine.

Anyway, glad to have helped.

Now to check out the config file and I'll switch to this.

xaos52 · 2016-04-14 12:55:38

OK.
Suggestions and error reports still welcome.

hhh · 2016-04-15 02:36:19

xaos52 wrote:

I would appreciate it enormously if someone else could test the new version of the bl-exit script.
You can find an explanation on how to configure it hereThanks

Sorry I missed this, Doc. I'll give it a go ASAP.

ASAP=after speedy ale purchase

hhh · 2016-04-15 03:49:27

@Rock Me Dr. Xaos, I put /bin/bl-exit in /usr/local/bin. No config, no change. Create ~/.config/bl-exit/bl-exitrc with your hibernate content, the button appears and my laptop hibernates (very glitchy and ugly on my 9 y.o. ThinkPad, but it works. Spotify picked up where it left off, sweet.)

Very slick, great work, and bravo. Take a bow for a very elegant solution.

-edit- Not all that glitchy or ugly, really, on second sight. I'm using it, it's great.

johnraff · 2016-04-17 04:44:58

Quick test on a VM.

Default (no config) works fine.

Use $HOME/.config/bl-exit/bl-exitrc

[hibernate]
show = maybe
onerror = visual

to add "Hibernate", and the button appears. Click it and the VM closes down.
Restart the VM and I get a black screen. No key or mouse action will get out of it, except using VirtualBox's R-Ctrl + Q to shutdown the VM. After that it comes back up OK but the session has been lost.

I guess that is an issue with Hibernate on that VM, possibly with LightDM or LightLocker.
At least I can say that bl-exit did not raise an error message when "Hibernate" was clicked.
However, Hibernate is not the sort of thing I ever expect to work anyway. (especially on a VM)

---

Possible unrelated suggestion: have bl-exit check /etc/bl-exit/bl-exitrc for a system-wide config file if there's no user file. We could ship a config that just spells out the hardcoded default settings, but would be a template for users to copy into ~/.config/bl-exit

Last edited by johnraff (2016-04-17 06:36:16)

Head_on_a_Stick · 2016-04-17 08:55:14

johnraff wrote:

Use $HOME/.config/bl-exit/bl-exitrc
[hibernate]
show = maybe
onerror = visual
to add "Hibernate", and the button appears. Click it and the VM closes down.
Restart the VM and I get a black screen. No key or mouse action will get out of it, except using VirtualBox's R-Ctrl + Q to shutdown the VM. After that it comes back up OK but the session has been lost.

I have not configured my machine to use hibernation and if I use the "Hibernate" button then my machine shuts down.

I think this is the expected behaviour but I use btrfs so I can't make a swap file to enable hibernation to check this

Peregrino69 · 2016-04-17 16:12:49

Late to the game but...

Q1. Would you use that functionalty?

Next laptop I'm buying will very very likely to be running BL. Yes, I definitely would use it.

Q2. For 'Hibernate' to work, you need to set up adequate swap space.
When the swap space is not sufficient to hibernate, choose one of the options below:
1. I don't want to see the hibernate button.

... BUT I'd appreciate a dialog during installation "your swap space isn't sufficient for Hibernate, so the option will not be available".

#61 2016-04-13 17:35:12

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

#62 2016-04-13 17:40:28

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

#63 2016-04-14 09:10:53

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

#64 2016-04-14 09:21:58

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

#65 2016-04-14 10:06:54

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

#66 2016-04-14 10:29:27

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

#67 2016-04-14 10:46:08

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

#68 2016-04-14 10:48:30

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

#69 2016-04-14 11:34:17

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

#70 2016-04-14 11:59:06

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

#71 2016-04-14 12:12:52

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

#72 2016-04-14 12:18:42

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

#73 2016-04-14 12:21:30

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

#74 2016-04-14 12:42:39

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

#75 2016-04-14 12:55:38

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

#76 2016-04-15 02:36:19

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

#77 2016-04-15 03:49:27

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

#78 2016-04-17 04:44:58

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

#79 2016-04-17 08:55:14

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

#80 2016-04-17 16:12:49

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

Board footer