Enter your search query in the box above ^, or use the forum search tool.

You are not logged in.

#1 Re: Off Topic / General Chat » Coffee room » 2015-07-21 03:51:13

Hello, popping in to say Hi, it has been a while  :8

#2 Help & Support (Other) » Wheezy netinstall suspend on laptop lid close » 2015-04-01 11:33:52

Replies: 4

Hello folks.

I have a Wheezy netinstall with openbox, and have this issue I hope someone can help me with:

This works:
+ boot to tty, log in (no Window Manager is running)
+ close the laptop lid, the machine suspends OK

Does not work:
+ run startx (openbox)
+ close the laptop lid, suspend does not trigger

Weird, huh?

When I open the lid again I get the notification: "power manager, not authorized".

I then:

+ Enabled verbose debug messages for pm-utils [1] and no errors are logged to /var/log/pm-suspend.log, darn.
+ Checked that I don't have HAL installed, as it interferes with pm-utils (per same the link [1]).

The post [2] indicates that authorization is handled via consolekit and session manager, but the "exec ck-launch-session" line answer in that post did not help.

When I run "exec ck-launch-session openbox-session" it drops me back to a login prompt (openbox-session reports that the $DISPLAY environment variable is unset even though it is)

~$ echo $DISPLAY


The only way I can suspend at the moment is with "sudo pm-suspend", and that gets tedious quickly. I could add myself to sudoers without password for pm-suspend, but I would prefer to get this working how it is intended (TM). Any ideas?

Signed, perplexed monkey


#3 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-20 05:24:16

I can't believe it has been 3 weeks already since this started and look at how it has grown.
smacz, nice test-pack you ran through there.
Thanks woodape!

#4 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-18 06:01:26

detinith wrote:

Hey guys, I've finally been able to read up on this thread @woodape keeps telling me about. After reading through the thread and updating my understanding of the program a bit, I think I can help contribute now haha.

Welcome detinith!

I'm liking the direction this is taking and am keen to play with the modified code  8)

To make things easier I am going to update the original post to point to the GitHub repository woodape set up, to make getting new versions easier  O:)

Edit: had a quick look at the new look of this menu and, oh my hat, great work!

#5 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-15 06:39:15

Updated the original post with the latest from woodape (Load/Kill menus).

I am enjoying how the scope and ideas for this is changing so rapidly, this is fun smile

@smacz thanks for your input. How far did you get with your pygobject implementation? I can fork the BunsenLab repository and include this pipemenu, but even so a pull request will only be feasible after a week (or a few) of running with this to see how it performs in terms of user experience and usability (ahem bugs).

Edit: No - the Load/Kill toggling in the menus replace the disabled menu items (with batteries included IMO)

Oh my hat I wish I had a whole day to play around with this - will be back in a day or two  O:)

#6 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-15 05:55:55

Wow this is amazing... everyone seems to dig this pipemenu smile

The Load/Kill toggling is much nicer than the sub-menus, kudos @woodape for adding all of that! It is working well here. (Noted the rename to .conkyrc - thumbs up)

It got a bit confusing for a moment because I think we all had a different idea of how we organise our conky configs. This new mechanism of Loading configs satisfies both use-cases (single or combined running configs). Wonderful!

I am excited to go through the code and learn what has changed, still out of town and doubt I will get a moment today, but looking forward to it! I will update the OP with this code above, and for learning sake: mapping string formats by key-value pairs is available for Python 2 and up smile

#7 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-13 13:10:01

What an interesting idea, thank you Sector11 - adding conky's to the list of running instances for combine layouts? hmmm, I will think on this while I drive home from work...

In the mean time I am imagining adding two menu items, to kill all conky's and another toggle-option that determines if running instances are killed first when a new conky is run.

This way you can click through multiple configs in any order to combine layouts (but would require some extra logic to preserve any session.log entries)

Conky Switcher
--------------> Config 1
                Config 2
                Config 3
                kill all
                [x] Combine Mode

I will see if I can steal some time this weekend to play around with this idea - will be out of my home-town until Sunday.  O:)

#8 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-13 06:32:41

Your changes work wonderfully @woodape and @detinith thank you. I updated the original post and included the shell script to resume the session from autostart. I was wondering how to support multiple conky's and your idea just seems so elegant and simple  cool

#9 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-12 10:57:08

@woodape and @detinith that is a great change, particularly how it supports multiple conky scripts across sessions - thank you! I am eager to try it out later at home  smile

#11 Re: Tips, Tricks & Scripts » Post your .Xdefaults and terminal apps colorschemes with screenshot » 2015-03-10 06:21:16

Solarized theme for rxvt

! --------------------------------------
! Solarized URxvt colors
! $base03:    #002b36;
! $base02:    #073642;
! $base01:    #586e75;
! $base00:    #657b83;
! $base0:     #839496;
! $base1:     #93a1a1;
! $base2:     #eee8d5;
! $base3:     #fdf6e3;
! $yellow:    #b58900;
! $orange:    #cb4b16;
! $red:       #dc322f;
! $magenta:   #d33682;
! $violet:    #6c71c4;
! $blue:      #268bd2;
! $cyan:      #2aa198;
! $green:     #859900;

URxvt.background:       #002b36
URxvt.foreground:       #839496
URxvt.colorBD:          #93a1a1
URxvt.cursorColor:      #93a1a1
! URxvt.throughColor:     #8080f0
URxvt.highlightColor:   #eee8d5

! Black (not tango) + DarkGrey
*color0:  #000000
*color8:  #657b83
! DarkRed + Red
*color1:  #dc322f
*color9:  #dc322f
! DarkGreen + Green
*color2:  #859900
*color10: #859900
! DarkYellow + Yellow
*color3:  #b58900
*color11: #b58900
! DarkBlue + Blue
*color4:  #268bd2
*color12: #268bd2
! DarkMagenta + Magenta
*color5:  #d33682
*color13: #d33682
!DarkCyan + Cyan (both not tango)
*color6:  #2aa198
*color14: #2aa198
! LightGrey + White
*color7:  #eee8d5
*color15: #fdf6e3
! --------------------------------------

#12 Re: Help & Support (Crunchbang 11 "Waldorf") » Wine: Leapfrog Tag Reader » 2015-03-09 13:55:45

When it comes to WINE you should always check the WINE Application Database. I cannot assist you with your question directly, but it is also worth talking in the WINE HQ Forums as you may find other users who have tried what you are wanting to achieve, already.

Good luck  smile

#13 Re: Off Topic / General Chat » man baby » 2015-03-09 10:11:27

^ That was an enjoyable read, thanks AnInkedSoul  ]:D

#14 Re: Artwork & Screenshots » March 2015 Screenshot Thread » 2015-03-09 06:27:18

First scrots of my adventure into a BunsenLab!

Before (Openbox + URxvt defaults):



I customized tint2 around the Solarized colours (config post coming later), and plan to make a Solarized conky too.
The Openbox and GTK themes are from hhh. Thanks hhh big_smile

#15 Re: Development » Default GTK/Openbox/Notification Theme » 2015-03-09 06:16:23

@hhh, using the grey theme + blue flame wallpaper, and it looks great - cheers!

#16 Re: Development » Pushing changes to Bunsen github/ problems with installing packages » 2015-03-06 06:26:03

As I understand distributed workflow, you Fork one of the Bunsen Lab repositories, commit your changes to your Fork and create a Pull Request. Your changes can then be looked over and merged into the BL repository. It is a good practice to make changes in branches too.

The alternative is if you are given write permission to the BL repo and commit there directly. This is an older workflow dating back to the days of centralized source control, and does tend to trip one up and people can step on each other's changes. Of course this is at the discretion of the repo owners  big_smile

#17 Re: Artwork & Screenshots » March 2015 Screenshot Thread » 2015-03-06 06:06:59

ZMR wrote:

Still running CrunchBang but playing with ideas for BunsenLabs.

(Original wallpaper)

Nice touch on the mono-spaced switcher font and border-less terminal. A very grabbing desktop  smile

#19 Re: Artwork & Screenshots » March 2015 Screenshot Thread » 2015-03-05 12:28:16

pingu wrote:

I found an hdd that is at least 10 years old. A 60gb ide drive from when 60 gb was a "good" size. It came with a pentium 3 box (my first "real" computer). The drive was mounted with an ide-usb adaptor and a bunch of relics found. Amognst them were my dog and an Ubuntu 7.04 iso.

(and I decided to go full bloat on my arch and got cinnamon to remind me of the good'ol gnome2 days) big_smile

edit: Here's the drive, and some dust.

edit2: It's very, very, noisy.

It's fun finding these digital time-capsules isn't it smile As a side-note and superfluous fact, my first real pc was a 486 DX2  ]:D

#20 Re: Artwork & Screenshots » March 2015 Screenshot Thread » 2015-03-05 12:19:56

CTTKDKing wrote:

#! on a Dell Inspiron 1200 my sister had laying in a closet. 1.3ghz celeron with 768 mb RAM. Works out of box and the machine is suprisingly fast this way.

Nice one CTTKDKing  big_smile

#21 Re: Ideas & Suggestions » Lockscreen for BunsenLabs » 2015-03-05 12:06:04

@borborygmi Great script to auto-size the lockscreen background! Excellent find on using stdout  8)

#22 Off Topic / General Chat » man baby » 2015-03-05 11:59:31

Replies: 9

I thought this was pretty clever, and I just had to share the fun lol

BABY(1) 										  BABY(1)

       baby -- create new process from two parents

       baby -sex [m|f] [-name name]

       baby  is  initiated  when one parent process polls another server process through a socket
       connection in the BSD version or through pipes in the System V implementation.  baby  runs
       at  low	priority  for  approximately  forty weeks and then terminates with a heavy system
       load.  Most systems require constant monitoring when baby reaches its final stages of exe-

       Older  implementations  of baby did not require both initiating processes to be present at
       the time of completion.	In those versions the initiating process which	was  not  present
       was  awakened  and  notified of the results upon completion.  It has since been determined
       that the presence of both parent processes result in a generally lower system load at com-
       pletion,  and thus current versions of baby expect both parent processes to be active dur-
       ing the final stages.

       Successful completion of baby results in the creation and naming of a new process.  Parent
       processes then broadcast messages to all other processes, local and remote, informing them
       of their new status.

       -sex   define the gender of the created process

       -name  assign the name name to the new process

	      baby -sex f -name Jacqueline

       completed successfully on July 9, 1992 at 9:11pm.  Jacqueline's vital statistics: 8 pounds
       3  oz,  20  inches,  long  dark hair.  The parent process, Kim Dunbar, is reportedly doing

       cigar(6), dump(5), cry(3).

       Despite its complexity, baby only knows one signal, SIGCHLD, (or SIGCLD in  the	System	V
       implementation),  which	it uses to contact the parent processes.  One or both parent pro-
       cesses must then inspect the baby process to determine the cause of the signal.

       The sleep(1) command may not work as expected on  either  parent  process  for  some  time
       afterward, as each new instance of baby sends intermittent signals to the parent processes
       which must be handled by the parents immediately.

       A baby process will frequently dump core, requiring either or  both  parent  processes  to
       clean up after it.

       Despite the reams of available documentation on invoking and maintaining baby, most parent
       processes are overwhelmed.

       From a man page by Joe Beck, <>.


#23 Re: Tips, Tricks & Scripts » Conky Switcher (Pipe Menu) » 2015-03-03 07:37:19

@damo I tried escaping the text to &amp; without luck, but will try using semi-colons between commands. Cheers!

@tknomanzr, it certainly is. And now there is a graphical menu too! Everybody loves to have choices  ]:D

#24 Re: Tutorials » postbang » 2015-03-03 07:29:17

Thank you brontosaurusrex! First time setting up from a netinstall and it is easier than I imagined (even got me side-tracked into trying out fluxbox again). I love these new-installation adventures.

#25 Re: Artwork & Screenshots » March 2015 Screenshot Thread » 2015-03-03 06:25:46

@twoion nice wallpaper.

crunchbang waldorf with a BunsenLabs wallpaper and a seamod conky (with tweaks by S11) smile


Edit: A base debian netinstall with fluxbox

Hoping to steal some time to learn more about setting up base systems.

Board footer

Powered by FluxBB

Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.
Server: acrobat

Debian Logo