SEARCH

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

You are not logged in.

#1 2015-05-02 16:49:44

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Keeping Crunchbang while upgrading to Jessie (Debian 8)

Jessie upgrade ontop of Chrunchbang Keeping Wordolf after Jessie

As john raff gave us a post on how to go from a basic Jessie install to a pseudo Crunchbang as best as possible.
http://crunchbang.org/forums/viewtopic.php?id=38994

"So many people are buiding their crunchy respins of Debian Jessie or Sid - these are exciting times!" John Raff


I kept my crunchbang then "backwards" engineered it. I only ran into a few glitches that no longer worked, than fixed them. I've had no problems so far. So if you'd like to try what I did upgrade to Debian 8 with crunchbang. Here is what I did. but first the prefix. 

The first time I did this it was by accident. I was bored, and curious so I changed my sources.list to install unstable. It installed Jessie.

This was about 3 weeks before it was released. When I found problems, fixed them problems. Kept tinkering with it until I broke it. Then had to re-install Crunchbang again. I liked some of the new updated things and the BAM Shutdown, Logout, and Reboot was a lot faster too.

So I went back to the how do I put Debian 8 in here with just openbox not lxde, but just openbox and tint2? My Laptop not wanting to cooperate with any of the different ways to install Debian 8. I went to trying to upgrade it again.

But me being me. I didn't do it the way I'd put money on it that it should have been done. I just changed my sources.list than tried to install one thing. Apt-get had all kinds of new things it wanted to put it as well. I just said y. then ran into problems with dependencies. that is when I tired to install Dedian 8 with the help from Head_on_a_Stick from the get go, only to get a no go.

So a fresh install of Crunchbang, then upgraded from that next gets me what I got now. A working Crunchbang operating with Debian 8 underneath it.

So if you want to keep your #! on with Debian 8 new and updated apps. this is what I did to do that.

first remove tint2conf.

sudo apt-get purge tint2conf

Don't worry about having to remove tint2 than re-install it. the upgrade to it will now work because tint2conf is no longer stopping it from doing so. (that is what messed me up, I removed tint2 than tried to reinstall just that and got everything along with it. Probably should have done some kind of apt-get --Just install that switch)

then change your etc/apt/sources.list to this

## CRUNCHBANG -- no longer supported :(
## Compatible with Debian Wheezy, but use at your own risk.
#deb http://packages.crunchbang.org/waldorf waldorf main
#deb-src http://packages.crunchbang.org/waldorf waldorf main

## DEBIAN
deb http://http.debian.net/debian/ jessie main contrib non-free
deb http://ftp.debian.org/debian/ jessie-updates main contrib non-free

#deb-src http://http.debian.net/debian jessie main contrib non-free

# MULTIMEDIA
deb http://www.deb-multimedia.org jessie main non-free
deb http://www.deb-multimedia.org jessie-backports main

## DEBIAN SECURITY

deb http://security.debian.org/ jessie/updates main contrib non-free
#deb-src http://security.debian.org/ jessie/updates main

Remember to comment out all of Crunchbang sources. Change the wheezy to jessie. If you want Debian Multimedia.
http://www.deb-multimedia.org/ this is a simple matter. Remember that after you add the Multimedia line then do your apt-get update. You then HAVE TO install the key-ring for multimedia first and foremost before moving on. Just add this in your favorite term hit enter than volia it gets done.

sudo apt-get install deb-multimedia-keyring

then repeat apt-get update. then apt-get dist-upgrade. if you see anything that looks like this before you do that.

Reading package lists... Done
W: There is no public key available for the following key IDs:
9D6D8F6BC857C906
W: There is no public key available for the following key IDs:
7638D0442B90D010
W: There is no public key available for the following key IDs:
7638D0442B90D010
NO_PUBKEY CBF8D6FD518E17E1

Don't worry too much. I just went ahead and did the sudo apt-get upgrade. Let it Run. grab a cup of coffee or your favorite drink or whatever. It's going to take a while to update everything. It updated mine with out a Hitch. The key-ring errors just went away after it was done upgrading.

Now to what I've noticed no longer works as it should so you can fix them.

cd-exit - just hangs and does not reboot or shutdown as it should.
polkit-1 - Accessing HDD's that where mounted but getting a permissions denied access to that drive message box.

With cb-exit I only had to change three things. Found it in a post in here.  http://crunchbang.org/forums/viewtopic.php?pid=369370

sudo geany /usr/bin/cb-exit

Remember to back up files just incase. Save it as a backup file then change it then just do SaveAs changing the
file name back to cb-exit. After you've replaced these three lines. Look for where you see the

 os.system 

line this is what you want to replace with this to each function acording to the same function.
What to look for to find where it is you need to be to change the actions code.

def suspend_action(self,btn):

def reboot_action(self,btn):

def shutdown_action(self,btn):

Replace the whole line where it starts with os.system with this.

#To Suppend the System. With this one MAKE sure you do NOT remove the 
# gtk.main_quit() on the last line. That stays there. 
 
os.system("dbus-send --system --print-reply --type=method_call --reply-timeout=2000 --dest=org.freedesktop.UPo
wer /org/freedesktop/UPower org.freedesktop.UPower.Suspend")

#To Restart the System

os.system("dbus-send --system --print-reply --type=method_call --reply-timeout=2000 --dest=org.freedesktop.Con
soleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart")

#To Shutdown the System

os.system("dbus-send --system --print-reply --type=method_call --reply-timeout=2000 --dest=org.freedesktop.Con
soleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop")

Save file as cb-exit in /usr/bin/ then everything with cb-exit now works again. BAM it shuts down in a millisecond. Mine does now anyways.

Now on to the polkit-1 problem. As polkit-1 is already installed. Just got a add a file and maybe tweek another one is all. No reboot or logout for it to work again.

you may have to create a file for automounting and accessing the dirves or add some of this to it if it is already there.

sudo geany /etc/polkit-1/localauthority/50-local.d/automount.pkla or you can name the file what ever you want as long as the extention is .pkla  - automount is a good key word though.

[Allow Automount]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesystem-mount*
ResultAny=yes
ResultInactive=yes
ResultActive=yes

[Allow Eject]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.eject-media*
ResultAny=yes
ResultInactive=yes
ResultActive=yes

[Allow Mounting of fstab]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesystem-fstab*
ResultAny=yes
ResultInactive=yes
ResultActive=yes

Check this file to ensure it is setup right. http://crunchbang.org/forums/viewtopic. … 98#p425598

 On double checking /usr/share/polkit-1/actions/org.freedesktop.udisks2.policy here is the portion that seems relevant:

<action id="org.freedesktop.udisks2.filesystem-fstab">
    <description>Mount/unmount filesystems defined in the fstab file with the x-udisks-auth option</description>
    <defaults>
      <allow_any>auth_admin</allow_any>
      <allow_inactive>auth_admin</allow_inactive>
      <allow_active>auth_admin_keep</allow_active>
    </defaults>
  </action>

This has been stripped of all the xml lang entries to clarify things. So, assuming you have correct /etc/fstab entries for your ntfs drives, this will allow you to mount them as a user. Edit /etc/fstab for the ntfs partitions in question and change auto to noauto in the options.

Change the above polkit rule to any instead of auth_admin.
Also, to be able to eject drives as a normal user, change the following to any from auth_admin:

<action id="org.freedesktop.udisks2.eject-media">
    <description>Eject media</description>
    <defaults>
      <allow_any>auth_admin</allow_any>
      <allow_inactive>auth_admin</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
  </action>
  
 

now be sure you saved both files. Then go back and click on the drives that did not let you in to be sure it worked. Mine did. if yours did not then .... you did something wrong time to post a help me file in here .. big_smile big_smile big_smile or go back and check it again.



If you use PCManFM the upgrade removes root privileges. how to get that back again.
http://wiki.lxde.org/en/PCManFM#Run_as_root


PCManFM
Run as root

in .local/share/  you may have to make two new sub-directories. file-manager than in that directory /actions so it is as such. /.local/share/file-manager/actions . In that bottom directory /actions put this in the file you created on your very own by utilizing one of the best features ever invented by man - "copy" than "paste".

[Desktop Entry]
Name = Open as Root
Tooltip = Open the folder as root
Icon = terminal
Profiles = on_folder;

[X-Action-Profile on_folder]
Name = Open as Root
MimeTypes = inode/directory;
SelectionCount = 1
Schemes = file;
Exec = gksudo pcmanfm %f

Save that in the /actions folder as

 root.desktop 

now when you right click on a folder look for it. it will say "Open as root". Done!

if you want to make your menu look spectacular do this.
http://crunchbang.org/forums/viewtopic.php?id=39322

sudo apt-get install cpanminus build-essential git # Assuming build-essential & git are not already installed
git clone git://github.com/trizen/obmenu-generator
sudo cp obmenu-generator/obmenu-generator /usr/bin
sudo cpanm Linux::DesktopFiles
sudo cpanm Data::Dump
sudo chmod +x /usr/bin/obmenu-generator

I modded the schema.pl file like this. I commended out the things I didn't want to use in my menu than replaced them with what I wanted in my menu first. PCmanFM, and Firefox in my ~/bin .
placed this file in your home directory /.config/obmenu-generator/ .     File name schema.pl . this is all that needs to be in that directory for this to work.

#!/usr/bin/perl

# obmenu-generator - schema file

=for comment

    item:      add an item inside the menu               {item => ["command", "label", "icon"]},
    cat:       add a category inside the menu             {cat => ["name", "label", "icon"]},
    sep:       horizontal line separator                  {sep => undef}, {sep => "label"},
    pipe:      a pipe menu entry                         {pipe => ["command", "label", "icon"]},
    raw:       any valid Openbox XML string               {raw => q(xml string)},
    begin_cat: begin of a category                  {begin_cat => ["name", "icon"]},
    end_cat:   end of a category                      {end_cat => undef},
    obgenmenu: generic menu settings                {obgenmenu => ["label", "icon"]},
    exit:      default "Exit" action                     {exit => ["label", "icon"]},

=cut

# NOTE:
#    * Keys and values are case sensitive. Keep all keys lowercase.
#    * ICON can be a either a direct path to an icon or a valid icon name
#    * Category names are case insensitive. (X-XFCE and x_xfce are equivalent)

require "$ENV{HOME}/.config/obmenu-generator/config.pl";

## Text editor
my $editor = $CONFIG->{editor};

our $SCHEMA = [
	{item => ['gmrun', 'Run Program', 'system-run']},
	
	{sep => undef},
	
	{item => ['terminator', 'Terminal', 'terminal']},
	#{item => ['x-www-browser', 'Web Browser', 'web-browser']},
	{item => ['/home/userx/bin/firefox/firefox', 'Web Browser', 'web-browser']},
	#{item => ['thunar', 'File Manager', 'file-manager']},
	{item => ['pcmanfm', 'File Manager', 'file-manager']},
	{item => ['geany', 'Text Editor', 'text-editor']},
	{item => ['vlc', 'Media Player', 'media-player']},
	
	{sep => undef},
    
    {cat => ['utility',     'Accessories', 'applications-utilities']},
    {cat => ['development', 'Development', 'applications-development']},
    {cat => ['education',   'Education',   'applications-science']},
    {cat => ['game',        'Games',       'applications-games']},
    {cat => ['graphics',    'Graphics',    'applications-graphics']},
    {cat => ['audiovideo',  'Multimedia',  'applications-multimedia']},
    {cat => ['network',     'Network',     'applications-internet']},
    {cat => ['office',      'Office',      'applications-office']},
    {cat => ['other',       'Other',       'applications-other']},
    {cat => ['settings',    'Settings',    'applications-accessories']},
    {cat => ['system',      'System',      'applications-system']},

    #{cat => ['qt',          'QT Applications',    'qt4logo']},
    #{cat => ['gtk',         'GTK Applications',   'gnome-applications']},
    #{cat => ['x_xfce',      'XFCE Applications',  'applications-other']},
    #{cat => ['gnome',       'GNOME Applications', 'gnome-applications']},
    #{cat => ['consoleonly', 'CLI Applications',   'applications-utilities']},

    #                  LABEL          ICON
    #{begin_cat => ['My category',  'cat-icon']},
    #             ... some items ...
    #{end_cat   => undef},

    #            COMMAND     LABEL        ICON
    #{pipe => ['obbrowser', 'Disk', 'drive-harddisk']},

    ## Generic advanced settings
    {sep       => undef},
    
    {obgenmenu => ['Openbox Settings', 'openbox']},
    
    {sep       => undef},
    
    {pipe => ['cb-places-pipemenu', 'Places', 'places']},
    {pipe => ['cb-recent-files-pipemenu', 'Recent Files', 'recent-files']},
    
	{sep => undef},
	
	{item => ['cb-lock', 'Lock Screen', 'lock-screen']},
	{item => ['cb-exit', 'Exit', 'exit']},
]

then run the command line arguments in user mode not sudo. I ran just about every option to have it create the other files it needs too. $obmenu-generator -p -s -i -t -u -r -d -c     that does it all and gives you really pretty icons on the menu now too.

https://github.com/trizen/obmenu-generator

usage: obmenu-generator [options]

options:
    -p         : (re)generate a pipe menu
    -s         : (re)generate a static menu
    -i         : include icons in menus
    -m <id>    : menu id (default: 'root-menu')
    -t <label> : menu label text (default: 'Applications')

other:
    -S <file>  : path to the schema.pl file
    -C <file>  : path to the config.pl file
    -o <file>  : path to the menu.xml file
    -u         : update the config file
    -r         : regenerate the config file
    -d         : regenerate icons.db
    -c         : reconfigure openbox automatically
    -R         : reconfigure openbox and exit

Help:
    -h  : print this message and exit
    -v  : print version and exit

Examples:
   ** Static menu without icons:
        obmenu-generator -s -c

   ** Dynamic menu with icons:
        obmenu-generator -p -i

if you don't want to write all of that stuff every time you add a program then make a shell bash file

#/bin/bash
#put options afterobmenu-generator per https://github.com/trizen/obmenu-generator

obmenu-generator -p -s -i -t -u -r -d -c

save it chmod +x filename run it - volia you're done.

Everything is now done. Chruchbang on top of Debian 8 Jessie. no extra wm or dm stuff or what ever. Just Crunchbang on top of Debian 8. You can go back to doing whatever else you'd like to do now.


Special Thanks goes to:

tknomanzr - polkit-1 automount fix
Alad      - cb-exit fix
Google    - PCmanFM root user fix
obsolete-hw - obmenu-generator add on

Edit:
I too added a nice program that crunchbang already has in here I just made it better then wrote a script to run it too. If you like to automatically cycle your background images and colors or just sizing the image without having to do it first before using it for your background then this is the program for you.

goto here http://sourceforge.net/projects/mhsetro … rce=navbar

Download mhsetroot-v1.6.2-amd32_64.tar.gz it runs on 32 and 64 bit --

unpack it -

install

sudo apt-get install libimlib2-dev

cd into that directory

./configure
make
sudo make install

copy this into a file name it setbg  chmod +x setbg  then either command line it ./setbg <number for how many minuets you want it to wait before it changes the image] >/dev/null 2>/dev/null then press enter or add it to your autostart file

be sure to update it to tell it where you keep all of your images for wall paper first before you run it. it defaults to every 3 minutes

#!/bin/bash

# written just for mhsetroot 
# changes the set time intervals when the wallpaper and color changes right from the command line
# default is 3 minutes 
#
# just type this in at the command line if you put it in your home directory
#
# ./<script name> <time you want the WP to change in minues> >/dev/null 2>/dev/null
#
# or add it to your autostart file ./setbg >dev/null 2>/dev/null &
#
#written by Michael Heras aka userx Nov. 30, 2013
#
# 


stTime=1
Ntime=$1


function rst(){

if [[ Ntime -le stTime ]]; then
	resetT=$((3*60)) #default 3 minutes 
	else
	resetT=$((Ntime*60))
return $resetT #pass the var to space land

fi

}

rst

#kill the prior pids leaving the new one when running from command line
function killoldPid(){
# add the script name <script name> remove the < > brackets also, when adding the what ever you named this script
if [ $(pgrep -u $USER setbg | wc -l) -ge 2 ] && [ $(pgrep -u $USER sleep | wc -l ) -ge 1 ]; then
	echo $(pgrep -u $USER setbg | wc -l) "pid# --" $(pgrep -u $USER sleep | wc -l)
	pkill -u $USER -o sleep
	pkill -u $USER -o setbg # <--you need to add what you call this script here <script-name>
else
         # add script name here  
echo "setbg pid $(pgrep -u $USER setbg ) sleep pid $(pgrep -u $USER sleep)"
fi

}
		
# gets a random color to use		
color() { 
echo \#$(head -n 1 /dev/urandom | od -t x1 -N 9 | awk '{print $2 $3 $4}') 
}

# gets a random color to use	
color2() { 
echo \#$(head -n 1 /dev/urandom | od -t x1 -N 9 | awk '{print $2 $3 $4}') 
}

# gets a random color to use	
color3() {
	echo \#$(head -n 1 /dev/urandom | od -t x1 -N 9 | awk '{print $2 $3 $4}')
}

# gets a random color to use	

tint() { 
echo \#$(head -n 1 /dev/urandom | od -t x1 -N 3 | awk '{print $2 $3 $4}') 
}



addSetNum1()
{
 RANGE=90
 echo
 number=$RANDOM
let "number %= $RANGE"
  
 }
 
 
 addSetNum2()
{
 RANGE=90
 echo
 number=$RANDOM 
 (( number=numberx3+RANDOM))
 let "number %= $RANGE"
  
 }
 
 
 
 setGradient()
 {
	 
	 RANGE=360
	 number=$RANDOM
	 let "number %= $RANGE"
 }
 
 
 
 setContrast()
 {
	 RANGE=3
	 number=$RANDOM
	 let "number %= $RANGE"
 }
 


#gets random options to set wallpaper differently every time it resets to the size the user tells it to show
flipI() {
    local option=( "-dcenter" "-dfimgd" "-dtilehv" "-dfimgv" ) 
    local index=$(( RANDOM % ${#option[@]} ))
    setI=${option[$index]}
   }
   
flipI

#gets random option to set the image on screen differently each time it resets

flipIM() {
		local option=( "-fimgh" "-fill" "-center" "-tilehv" "-fimgd" "-fimgv" "-tile" )
		local index=$(( RANDOM % ${#option[@]} ))
		setIM=${option[$index]}
	}
flipIM

#gets random option to flip the entire screen before it sets in differently each time it resets

flipS() {
    local options=("" "-fliph" "-flipd" "-flipv")
    local index=$(( RANDOM % ${#options[@]} ))
    setS=${options[$index]}
   }


#searches for all of the images jpg or png files 
function wps(){


if [[ $resetT -gt 10 ]]; then

nw="$resetT"


#set your wallpaper directory here
WALLPAPERS=/home/userx/Copy/bgs

echo ${WALLPAPERS}

{
    while true; do   
		## gets the image randomly then adds all the options in the order needed to set the wallpaper
		find "${WALLPAPERS}" -type f \( -name '*.jpg' -o -name '*.png' \) -print0 | shuf -n 1 -z | xargs -0 \
		mhsetroot -addd $(color) 3 -addd $(color2) 5 -addd $(color3) 3 -addd $(color) 8 -addd $(color3) 6 -addd $(tint) 4 \
		-gradient "$(setGradient)" ${setI} 500x500

		echo "sleep time changed to $(($nw/60)) minutes"
			
		sleep "$nw"
		
	
	done &
}
	
		
killoldPid
fi
}

#call function to make it work
wps

Last edited by userx-bw (2015-05-02 17:42:31)


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

Help fund CrunchBang, donate to the project!

#2 2015-05-02 16:55:59

tknomanzr
#! Die Hard
From: Heavener, OK
Registered: 2014-12-09
Posts: 777

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Great stuff! I'm glad to see you got it all working. There is likely other minor things from Crunchbang that might not work as expected. However, if you have a working #! box tracking Jessie, it is as simple as cloning the BunsenLabs stuff off their git and putting it where it needs to go. A lot of the custom #! scripts have been updated to work with Jessie.

Offline

#3 2015-05-02 16:59:59

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

[redacted]

Last edited by Head_on_a_Stick (2015-06-24 20:34:03)

Offline

#4 2015-05-02 18:29:24

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Head_on_a_Stick wrote:

Amazing!

Thank you!
smile

NP you got to read your mention right? I had to get you in there somewhere for trying to help me with this ma-nosh


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#5 2015-05-02 18:32:19

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

[redacted]

Last edited by Head_on_a_Stick (2015-06-24 20:34:21)

Offline

#6 2015-05-13 20:16:30

Graybyrd
Member
Registered: 2012-04-01
Posts: 28

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Great stuff! I did all of the mount & unmount tweaks. Thunar and PCmanFM are mounting/unmounting drives with no problem ... except for ejecting a thumb drive.

Inserting a thumb drive into my USB port mounts immediately, & displays in Thunar/PCmanFM. But I cannot eject the thumb drive. I get this error message:

Error checking authorization: GDBus.Error:org.freedesktop.PolicyKit1.Error.
Failed: Action org.freedesktop.udisks2.power-off-drive is not registered (polkit-error-quark, 0).

I'm no Linux ex'spurt here; just trying to stay on an even keel. I checked the /etc/fstab file ... no thumb drive listing there. All of this is a real tangle!

Any clues? Thanks!

-=GB=-

Offline

#7 2015-05-13 21:17:09

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Graybyrd wrote:

Great stuff! I did all of the mount & unmount tweaks. Thunar and PCmanFM are mounting/unmounting drives with no problem ... except for ejecting a thumb drive.

Inserting a thumb drive into my USB port mounts immediately, & displays in Thunar/PCmanFM. But I cannot eject the thumb drive. I get this error message:

Error checking authorization: GDBus.Error:org.freedesktop.PolicyKit1.Error.
Failed: Action org.freedesktop.udisks2.power-off-drive is not registered (polkit-error-quark, 0).

I'm no Linux ex'spurt here; just trying to stay on an even keel. I checked the /etc/fstab file ... no thumb drive listing there. All of this is a real tangle!

Any clues? Thanks!

-=GB=-

what you got running for a OS? I updated a #! to Jessie then had to mod my polkit file to make it mount and unmount -- right now I just did a clean install of Jessie - lxde / openbox


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#8 2015-05-13 23:45:50

Graybyrd
Member
Registered: 2012-04-01
Posts: 28

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

I installed #! Waldorf, then changed the repo to Jessie, just as shown at the top of this thread, and did all the apt-get update/dist-upgrade stuff. So I'm running Debian 8 "Jessie" with the #! interface. Then I made the changes to Polkit-1 as included in this thread (except for the menu auto-update stuff).

This is all running on an old Compaq Presario S4000T w/ Pentium4 i686 threaded, 3gb RAM. It screams with this OS! cool

All of the mount/unmount actions work fine ... except for ejecting/unmounting USB thumb drives (with the error message). Oddly enough, plugging in the USB thumb drive, it mounts instantly and opens to show files in either Thunar and PCmanfm. It's only the "eject" function that fails.

Add info: ejecting a CD triggers the same error message:

Error checking authorization: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: 
Action org.freedesktop.udisks2.eject-media is not registered (polkit-error-quark, 0).

However, pressing the CD drive tray button unmounts the drive, clears the File Manager display, and ejects the disc.

Last edited by Graybyrd (2015-05-14 02:17:05)

Offline

#9 2015-05-14 14:58:01

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

I'm going to have to show some humility and be honest, I have no idea, I'm new at this too. big_smile  With me I just unplug my USB items because they are hot mounted as long as you know nothing is being written to them then no harm done, as in no data loss. so it's no big deal to me that I do not click that unmount me first button. It still works.

read up on polit actions 

http://udisks.freedesktop.org/docs/late … tions.html

it is doing as it should when you do this

However, pressing the CD drive tray button unmounts the drive, clears the File Manager display, and ejects the disc.

the file manager just thinks you no longer need it when yo udo that so it shuts itself down.

With me what I was still running it. When ever I pluged in a USB External Hard Drive. I'd try to mount it twice. I'd get a message about it. No Data Loss or major upset happened. So I put that on my not to worry about list.

Though, you do have to understand what I did and why I mixed two systems together, and that Crunchbang is not a pure Debian Distro. It has been modified so it will never act like a pure Distro. With me mixing it like I did just so I could still have Crunchbang and all the new updated apps that I use. It is like putting regular gas into a engine that requires high octane.

It will work but you're going to see some problems. It is just to keep your Crunchbang alive with updates as best as possible until something better comes along. I accepted that then tried it to see what I'd end up with, then shared what I did so others that wanted to keep there old and have some new would have a different option other then reinstalling everything and perhaps trying what john raff figured out to do and shared that with the people. For me that was not an option at the time. So I shared what I did for others that do not have that option either.

The only problems I ever ran into was logging out. I'd ended up using Terminal to shutdown and reboot off the command line. No big deal. Gnu/Linux is a command line keyboard driven Operating System, its based off of Unix before they invented the mouse. It is not Windows, and it is better then Unix in the respect that it is an open source operating system.

With that a user with the proper rights can go in and modify everything and even try to fix what ever is not working properly all by themselves and not have to always rely on the one that actually wrote the program.

If just unplugging your USB Stick without clicking the unmount button causes you too many problems and you cannot figure it out. Try two things, maybe three, or more.

1. Reinstall Crunchbang and keep it like it is and track it into Old Stable. You can still modify it anyway you so choose to do, or try to do within the limitations of the System and program your messing with.

2. Install a pure Debian 8 lxde it comes with Openbox. That is what LXDE uses. You can get just log into an Openbox session instead. Then if you kept all of your autostart files, and openbox files from Crunchbang, along with what other files you modified other then the polkit. Because Debian 8 will already set up your system for that. That is part of the mixed in with the old Crunchbang. Its new systemd stuff from what I know about this.

Then you can make it look like a crunchbang, or look like what ever you want. Personally I like a Debian base. For ease of installing stuff. And Openbox to cut back on all of that GUI stuff. Then just mix and match the rest.


3. You can try what john raff suggested.

4. you can just keep trying other Distributions of GNU/Linux until you find something you'd like to use.

5. Go back to Windows then just wait until someone gets another system like Crunchbang up and in the public then go back and try it again. Waisting a lot of learning time. big_smile

6. ??? open to your own thoughts.

The best thing about GNU/Linux is not that it is free, but you can always modify everything. I mean everything. Even the Linux Kernel to get your system working the way you want it to work and take out all of the bulk making it even smaller so it will load even faster.

That free part us just the bonus part. Because even the people that started this still got a eat.

Regardless of what you choose to do. Back up all of your files that you modified. They may come in handy later on in that just in case you do have to reinstall scenario. Than you'll already have that part done. Just back up the original,

 cp filename filename-bk

then copy your files into where they need to be. Or just find, then add what parts you need to the other files. It saves lots of time.

I go to the manual mode then I just delete the partition -  re-establish it, with all the proper settings, then install a new system. its faster that way. smile #! was a 20 minute full install tops for me. I liked that! This Debian 8 install took a lot longer to install it. Almost had to go take a nap waiting for it to finish. sad

If you just want to open up files and hack at them to see what it does to your system to learn. Do it! But keep in mind that sometimes you may get to the point of a fresh copy is all that will fix it. This is why backing up your files too is important. Especially just before you go modifying them. So always back up, and keep what worked, so you do not have to do that again, then go on to doing something else to learn about that instead.

GNU/Linux is made up of so many different programs to run it. It is too much for any one person to know everything about every little bit of it. The ones that you do find that know a lot about everything in Linux. If you ask them you'll see that most of them have been at this even before Linux came to life, with a Unix background or something similar.

So it is better to at least know a little bit about every bit of it. If you want to modify it all the time then just read code. Learn one then apply it to all the others. Most cases its all the some just a different syntax. Just learn the rules that the code your reading uses. You may see that it's just a language with different dialects.

I seem to make it sound easy. But it's not. Not for me anyways. Someday I'll be coding something then look at it later on and even amaze myself. I wrote that?

GNU/Linux can be and is full of "how do I fix that's" or How can I change that?" SO don't be afraid to experiment and be prepared to re-install a system or just install a different one just to see what that one does. If you've backed up properly all the files you need and copy pasted all of the help files you found that where useful to you. Or kept your home directory  .mozilla file with everything in it. Then your web links you saved are safe too. Just copy over the new one after you did your apt-get update.

Providing you use the same web browser. Which usually is a derivative of Firefox. So you should be safe there too.

So don't be sad or disappointed if my option of what one can do to try and keep crunchbang and have Debian 8 too together doesn't work for you. There is another option else where that you can try too, then just utilize the bonus that comes with GNU/Linux and party on Garth!! big_smile


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#10 2015-05-14 18:28:47

Head_on_a_Stick
CatMod
From: A world of pure imagination
Registered: 2014-01-21
Posts: 4,797

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Graybyrd wrote:

Inserting a thumb drive into my USB port mounts immediately, & displays in Thunar/PCmanFM. But I cannot eject the thumb drive. I get this error message:

Error checking authorization: GDBus.Error:org.freedesktop.PolicyKit1.Error.
Failed: Action org.freedesktop.udisks2.power-off-drive is not registered (polkit-error-quark, 0).

Try adding this stanza to /etc/polkit-1/localauthority/50-local.d/automount.pkla

[Allow Power-Off]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.power-off-drive
ResultAny=yes
ResultInactive=yes
ResultActive=yes

Offline

#11 2015-05-15 22:27:09

Graybyrd
Member
Registered: 2012-04-01
Posts: 28

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

@ userx-bw: Thanks for the advice and commentary. Anyone reading this thread should know that I'm delighted with how this OS install and conversion has worked out. With the exception of the "eject" polkit-1 glitch, all else seems to work very well.

Yes, I'm a "debian junkie" ... it is my preferred base; and I've become very impressed with "Jessie" stable. I see no reason to change. All of my gear is older stuff; the latest 'puter here is a Lenovo T-400.  My current desktop is an old Compaq Presario S4000T with a pentium 4 cpu.  So a lightweight windows manager on top of debian 8 is the real answer: using the #! interface on top of debian 8 lets this old S4000T run free & fast. It's delightfully responsive.

As far as converting orphaned distro's to act as interface to debian 8, I've been forced to do TWO of them. I'd become quite fond of a debian variant called SolydXK ... with a choice of either the KDE or the XFCE desktop. I chose SolydX for our home machines, dual-booted with WinXP and Win7 installs. And then, wouldn't you know it, the developer decided to abandon the 32-bit version and left us hanging.

I changed the SolydX repo's to debian Jessie, and retained certain of the SolydX repo stuff. That was an exorcism from hell, the first time, with dependency conflicts, but it all sorted out after a restart or two. Now I've got a lovely choice: debian 8 "Jessie" with either XFCE or OpenBox, depending on which I boot into.

Oh ... the partitioning: yes, manual selection. I retain the "home" partition, and reformat only the "/" boot partition for an OS reinstall. All files & data are retained that way.

Yes, the learning curve for Linux tends to be infinite. I'm always amazed at folks who can spit out a batch of terminal strings and line entries. I've got a bookshelf of O'Reilly linux books, but that doesn't begin to cover even a portion of Linux knowledge. You're quite right: with thousands and thousands of individual parts and pieces that make up a typical installation, it's impossible to know it all. My biggest complaint, and I've heard others say the same thing: it's a rare coder who can be persuaded to slow down enough to document their work; and even after some man page or documentation has been written ... the code has moved forward and the docs are obsolete. As for "reading" the code ... I'm in agreement with those Perl critics who say the code reads like "line noise" ... (grin).

Anyway, I use Linux to run our (wife & I) computers, to get the job done. Interest in the workings of it are just a side interest with me, not a serious commitment.

- - -

@Head_on_a_Stick: I added that stanza to the "automount.pkla". No joy. But thanks for the help.

I'm reasonably certain (as userx-bw suggested) that as long as there's no data waiting to be written to the USB thumb drive, I can remove it without damage. That's been the case so far, since making the changes.

- - -

As a side note, I'm wishing that the #! enthusiasts who jumped onto the "bunsen lab" bandwagon would have first made a nice, clean install of the #! flavor of the OpenBox interface on top of Debian "Jessie" and then just called it something simple like "bang-box" to satisfy the policy change, and issued an iso of that. Life would have been so much simpler! Then they could fork it and make something that suited their taste.

When all is said and done, I suppose one should just go the pure Debian route and pick a desktop variant that suits. But I'd grown very fond of the #! distro ... and wanted to keep that super-elegant simplicity.

-=GB=-

Offline

#12 2015-05-18 23:28:48

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Graybyrd wrote:

I added that stanza to the "automount.pkla". No joy. But thanks for the help.

I'm reasonably certain (as userx-bw suggested) that as long as there's no data waiting to be written to the USB thumb drive, I can remove it without damage. That's been the case so far, since making the changes.

- - -

As a side note, I'm wishing that the #! enthusiasts who jumped onto the "bunsen lab" bandwagon would have first made a nice, clean install of the #! flavor of the OpenBox interface on top of Debian "Jessie" and then just called it something simple like "bang-box" to satisfy the policy change, and issued an iso of that. Life would have been so much simpler! Then they could fork it and make something that suited their taste.

When all is said and done, I suppose one should just go the pure Debian route and pick a desktop variant that suits. But I'd grown very fond of the #! distro ... and wanted to keep that super-elegant simplicity.

-=GB=-

When I had a stright Debian Jessie installed I copied all of the polkit-1 files out of share dir
from:
/usr/share/polkit-1/actions/org.freedesktop.udisks.policy

where it read Eject Media and drive detach -- maybe you don't got that -- something to look in to if you feel like it.

I put all of the files in Dropbox in this link good for a while before I unlink it. you can Download the zip or look though the directories in name usr/actions. there is two files that have to do with disks that I seen ...udisks... and ....udisks2....

https://www.dropbox.com/sh/ev6yttsnv4xl … =232110218

  <action id="org.freedesktop.udisks.drive-eject">
    <description>Eject media from a device</description>
    <defaults>
      <allow_any>no</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
  </action>

  <action id="org.freedesktop.udisks.drive-detach">
    <description>Detach a drive</description>
    <defaults>
      <allow_any>no</allow_any>
      <allow_inactive>no</allow_inactive>
      <allow_active>yes</allow_active>
    </defaults>
  </action>

"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#13 2015-06-08 20:47:16

Rhuks
Member
Registered: 2012-06-14
Posts: 23

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Thanks Userx-bw for this awesome way to keep my #! running... Now my laptop (Acer aspire 3690) looks like always I've wanted (Thanks Corenominal!)... Just a question:

dmenu it's "not" working: it starts normally, but there's no programmes list at all. the script is in the same place ~/.config/dmenu/dmenu-bind.sh and it reads the same code before the process, the same code pure Waldorf has.

Any suggestions? For me, dmenu is better than a graphic launcher, and it's an useful tool for everyday work.

Offline

#14 2015-06-08 21:01:20

damo
#! gimpbanger
From: N51.5 W002.8 (mostly)
Registered: 2011-11-24
Posts: 5,434

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Rhuks wrote:

...
dmenu it's "not" working: it starts normally, but there's no programmes list at all. the script is in the same place ~/.config/dmenu/dmenu-bind.sh and it reads the same code before the process, the same code pure Waldorf has.

Any suggestions? For me, dmenu is better than a graphic launcher, and it's an useful tool for everyday work.

Is it this bug, and fix? dist-upgrade and dmenu problem


BunsenLabs Group on deviantArt
damo's gallery on deviantArt
Openbox themes
Forum Moderator smile

Offline

#15 2015-06-11 20:27:37

Rhuks
Member
Registered: 2012-06-14
Posts: 23

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Thanks damo... all working as usual.. Great. smile

Last edited by Rhuks (2015-06-11 20:29:25)

Offline

#16 2015-06-18 21:17:26

Rhuks
Member
Registered: 2012-06-14
Posts: 23

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Hello again...  :8
I'm here with another question: How can I configure Slim?
typing 'slimconf', I get this:

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:57:17: Theming engine 'unico' not found

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:289:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:323:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1828:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1845:21: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:1861:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets.css:2146:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:16:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:93:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:183:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:503:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:850:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:925:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:941:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:957:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:1012:21: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:1020:21: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:1034:21: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:1103:21: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gtk-widgets-backdrop.css:1237:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: gnome-panel.css:94:21: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: nautilus.css:18:18: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: nautilus.css:18:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: nautilus.css:81:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: nautilus.css:86:20: Not using units is deprecated. Assuming 'px'.

(slimconf:4412): Gtk-WARNING **: Theme parsing error: nautilus.css:145:20: Not using units is deprecated. Assuming 'px'.
Traceback (most recent call last):
  File "/usr/bin/slimconf", line 121, in <module>
    builder.get_object("sessions").set_text(sessions)
NameError: name 'sessions' is not defined

First, I see there is a call for unico-engine, you know, it's a GUI... no problem with that (I think so...)
But the "line 121" stuff... I don't know what it refers to. Using CS, I change it to 'openbox' but nothing happens.
Well, that the spirit of CS...
Suggestions?

Offline

#17 2015-06-18 21:45:58

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

sudo update-alternatives --config x-window-manager

https://wiki.archlinux.org/index.php/SLiM

tells you what you need to know in setting up SLiM


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#18 2015-06-18 21:47:57

damo
#! gimpbanger
From: N51.5 W002.8 (mostly)
Registered: 2011-11-24
Posts: 5,434

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Rhuks wrote:

Hello again...  :8
I'm here with another question: How can I configure Slim?
typing 'slimconf', I get this:......etc
Suggestions?

A forum search may show you slimconf is from the cb repos, and is broken anyway eg here.

You don't need it - it is easier to just edit slim.conf directly wink

gksudo geany /etc/slim.conf & 

BunsenLabs Group on deviantArt
damo's gallery on deviantArt
Openbox themes
Forum Moderator smile

Offline

#19 2015-07-07 03:21:33

Rhuks
Member
Registered: 2012-06-14
Posts: 23

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Hello!! I'm here again... with another question, or comment :8

After a month, my laptop is working perfectly (#! with Jessie's heart) thanks to your post . But two things begin to fail AFTER I've created a new user:
1. nm-applet don't work at all: well, it's running normally, but if I want to change the wi-fi network, it shows this error message

(32) No session found for uid 1000 (unknown)

and it's shown each time a try to change something, even if I use other user's account. Looking for answers, the explanation: a bug, and the common sense solution: start it as root do the thing.

2. the cb-exit tweak works well until the new user was added to the system: it hangs... nothing happens. It was working as usual... CS solution? sudo poweroff...

As you see, no big deal, but if you have any ideas, please, share it to an "user" in broad sense.

Have a nice day. smile

Offline

#20 2015-07-07 12:04:31

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

@Rhuks   for cb-exit, update it with this code, this is what I am now using in Slackware with Openbox and i3 and any other wm I got up running (if i so choose to) and it works fine (for me) but make sure it has the proper permissions on it, owner and group. if it doesn't then here are the commands to make it so.

su or sudo chown root:root <path/ filename>
su or sudo chmod 755 <path/filename>
# to get this
-rwxr-xr-x 1 root root 

os yes it goes in /usr/bin/




#!/usr/bin/env python

import pygtk
pygtk.require('2.0')
import gtk
import os
import getpass

class cb_exit:
	def disable_buttons(self):
		self.cancel.set_sensitive(False)
		self.logout.set_sensitive(False)
		self.suspend.set_sensitive(False)
		self.reboot.set_sensitive(False)
		self.shutdown.set_sensitive(False)

	def cancel_action(self,btn):
		self.disable_buttons()
		gtk.main_quit()

	def logout_action(self,btn):
		self.disable_buttons()
		self.status.set_label("Exiting Openbox, please standby...")
		os.system("openbox --exit")

	def suspend_action(self,btn):
		self.disable_buttons()
		self.status.set_label("Suspending, please standby...")
		os.system("cb-lock")
		os.system("dbus-send --system --print-reply --dest=\"org.freedesktop.UPower\" /org/freedesktop/UPower org.freedesktop.UPower.Suspend")
		gtk.main_quit()

	def reboot_action(self,btn):
		self.disable_buttons()
		self.status.set_label("Rebooting, please standby...")
		os.system("dbus-send --system --print-reply --dest=\"org.freedesktop.ConsoleKit\" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Restart")

	def shutdown_action(self,btn):
		self.disable_buttons()
		self.status.set_label("Shutting down, please standby...")
		os.system("dbus-send --system --print-reply --dest=\"org.freedesktop.ConsoleKit\" /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop")

	def create_window(self):
		self.window = gtk.Window()
		title = "Log out " + getpass.getuser() + "? Choose an option:"
		self.window.set_title(title)
		self.window.set_border_width(5)
		self.window.set_size_request(500, 80)
		self.window.set_resizable(False)
		self.window.set_keep_above(True)
		self.window.stick
		self.window.set_position(1)
		self.window.connect("delete_event", gtk.main_quit)
		windowicon = self.window.render_icon(gtk.STOCK_QUIT, gtk.ICON_SIZE_MENU)
		self.window.set_icon(windowicon)

		
		#Create HBox for buttons
		self.button_box = gtk.HBox()
		self.button_box.show()
		
		#Cancel button
		self.cancel = gtk.Button(stock = gtk.STOCK_CANCEL)
		self.cancel.set_border_width(4)
		self.cancel.connect("clicked", self.cancel_action)
		self.button_box.pack_start(self.cancel)
		self.cancel.show()
		
		#Logout button
		self.logout = gtk.Button("_Log out")
		self.logout.set_border_width(4)
		self.logout.connect("clicked", self.logout_action)
		self.button_box.pack_start(self.logout)
		self.logout.show()
		
		#Suspend button
		self.suspend = gtk.Button("_Suspend")
		self.suspend.set_border_width(4)
		self.suspend.connect("clicked", self.suspend_action)
		self.button_box.pack_start(self.suspend)
		self.suspend.show()
		
		#Reboot button
		self.reboot = gtk.Button("_Reboot")
		self.reboot.set_border_width(4)
		self.reboot.connect("clicked", self.reboot_action)
		self.button_box.pack_start(self.reboot)
		self.reboot.show()
		
		#Shutdown button
		self.shutdown = gtk.Button("_Power off")
		self.shutdown.set_border_width(4)
		self.shutdown.connect("clicked", self.shutdown_action)
		self.button_box.pack_start(self.shutdown)
		self.shutdown.show()
		
		#Create HBox for status label
		self.label_box = gtk.HBox()
		self.label_box.show()
		self.status = gtk.Label()
		self.status.show()
		self.label_box.pack_start(self.status)
		
		#Create VBox and pack the above HBox's
		self.vbox = gtk.VBox()
		self.vbox.pack_start(self.button_box)
		self.vbox.pack_start(self.label_box)
		self.vbox.show()
		
		self.window.add(self.vbox)
		self.window.show()
		
	def __init__(self):
		self.create_window()


def main():
    gtk.main()

if __name__ == "__main__":
    go = cb_exit()
    main()

nw-manager is bug listed, where this person downgraded the nw-manager, whereas I went to their sight back when I was still running this configuration, and downloaded their 1.0 compiled and installed it. I don't remember if I had to play with any dependencies to satisfy the 1.0 version of nw-manager. but if I did then it couldn't have been that hard for me to figure out as I do remember getting it to work. wink Though I installed it for other reasons then this one.

too: this seems to be a problem with others as well, here
https://bbs.archlinux.org/viewtopic.php?id=146190

I seen a fix to this problem --

Package: network-manager
Version: 0.9.8.0-5
Severity: grave

Hi

Disclaimer: have set the severity to grave as it renders for me an
non-working network connection (but I'm unable to replicate the
problem on a second system -- but with a different setup).

After updating network-manager from 0.9.8.0-5 to 0.9.8.8-4 which
entered unstable network-manger looses the network connection.
Selecting in the Wifi-Connection the desired connection leads to:

Failed to add/activate connection
(32) No session found for uid 1000 (unknown)

Downgrading to network-manager/0.9.8.0-5 (and restarting the service)
works. libpam-systemd is installed (204-8).

check to be sure user is in group  netdev

sorry I can't be more of help

Last edited by userx-bw (2015-07-07 16:52:29)


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#21 2015-08-05 22:17:55

Anne_Frankenstein
Member
From: Texas
Registered: 2014-12-12
Posts: 18

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Somehow... somehow I messed this up.
Now when I startup, i get

"PNMixer Error: Failed to load pixbuf file: /usr/share/pnmiser/pixmaps/pnmixer-muted.png Couldn't recognize the image file format for the '/usr/share/pnmixer/pixmaps/pnmixer-muted.png'"

"PNMixer Error: Failed to load pixbuf file: /usr/share/pnmiser/pixmaps/pnmixer-low.png Couldn't recognize the image file format for the '/usr/share/pnmixer/pixmaps/pnmixer-low.png'"

""PNMixer Error: Failed to load pixbuf file: /usr/share/pnmiser/pixmaps/pnmixer-medium.png Couldn't recognize the image file format for the '/usr/share/pnmixer/pixmaps/pnmixer-medium.png'"

"PNMixer Error: Failed to load pixbuf file: /usr/share/pnmiser/pixmaps/pnmixer-muted.png Couldn't recognize the image file format for the '/usr/share/pnmixer/pixmaps/pnmixer-muted.png'"

..and my desktop is some sort of neutral grey color without anything but the system information.

...halp?

**Edit** I attempted to restart tint2, and the same errors popped up, so I'm guessing it has to do with that?

**Further Edit** Nevermind, I purged tint2, and it all worked proper. My apologies. -_-

Last edited by Anne_Frankenstein (2015-08-05 22:46:39)

Offline

#22 2015-08-05 22:47:06

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

Anne_Frankenstein wrote:

Somehow... somehow I messed this up.
Now when I startup, i get

"PNMixer Error: Failed to load pixbuf file: /usr/share/pnmiser/pixmaps/pnmixer-muted.png Couldn't recognize the image file format for the '/usr/share/pnmixer/pixmaps/pnmixer-muted.png'"

"PNMixer Error: Failed to load pixbuf file: /usr/share/pnmiser/pixmaps/pnmixer-low.png Couldn't recognize the image file format for the '/usr/share/pnmixer/pixmaps/pnmixer-low.png'"

""PNMixer Error: Failed to load pixbuf file: /usr/share/pnmiser/pixmaps/pnmixer-medium.png Couldn't recognize the image file format for the '/usr/share/pnmixer/pixmaps/pnmixer-medium.png'"

"PNMixer Error: Failed to load pixbuf file: /usr/share/pnmiser/pixmaps/pnmixer-muted.png Couldn't recognize the image file format for the '/usr/share/pnmixer/pixmaps/pnmixer-muted.png'"

..and my desktop is some sort of neutral grey color without anything but the system information.

...halp?

**Edit** I attempted to restart tint2, and the same errors popped up, so I'm guessing it has to do with that?

**Further Edit** Nevermind, I purged tint2, and it all worked proper. My apologies. -_-



http://crunchbang.org/forums/viewtopic.php?id=34321


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

#23 2015-08-12 03:21:24

vlax
#! CrunchBanger
From: Alcatraz
Registered: 2012-12-25
Posts: 101
Website

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

really useful resource indeed ,, , I'm sure I would try this soon..

as far I understand, debian 8 is now using systemd by default, do you have any concern or opinion on how remove it in case somebody prefer to preserve and old-style #! enviroment ? this, for example, is advice to be a real way to do it well: http://crunchbang.org/forums/viewtopic. … 49#p435249


'_[=]_'

Offline

#24 2015-08-12 12:09:01

userx-bw
#! Die Hard
From: stuck in an unknown reality
Registered: 2013-11-19
Posts: 735

Re: Keeping Crunchbang while upgrading to Jessie (Debian 8)

vlax wrote:

really useful resource indeed ,, , I'm sure I would try this soon..

as far I understand, debian 8 is now using systemd by default, do you have any concern or opinion on how remove it in case somebody prefer to preserve and old-style #! enviroment ? this, for example, is advice to be a real way to do it well: http://crunchbang.org/forums/viewtopic. … 49#p435249


that seems the only option to rid oneself of systemD if they decide to keep Debian / openbox / #! running on their PC's. I personally have never tried it.

not trying to sponsor a different "type" of GNU/Linux.  but I've instead moved to Slackware and VOidLinUx who's init system called runit. Written by VoidLinux. Slackware does not use systemD either. With them you have to compile and install deps and apps, where Void Linux is a completely stripped down system. after install you only have the OS, and DE and some basic tools needed to get around inside of it and internet and nothing else. you have to install everything else that you want inside of it. by a system similar to apt-get, I am using i3 as a Wm. Openbox one needs to their know to's.

but if one cannot afford to start over due to time consumption finding all of their custom scripts and trying to remember everything they did to customize their system. then try to save that too. having to remember where it goes after they have installed a fresh system. that is why I did what I did with this post, so one can move into ver 8 without having to lose everything and start from scratch again.

as far as systemD -- I'm no longer having to deal with it, so I do not worry about it. @Head_On_a_Stick (HOaS) seems to understand that system from what he has read up on, if he is experimenting with the two just so he can gain knowledge of it to then share with it others I do not know, you'd have to ask him.


"How can you learn how to fix it, if you don't break it first? :8
"the only way to get away with murder is - by killing time" swp 1997  8o
"A computer is only as smart as the person using it"
"Just plug it in and see if it blows up, if not then take it apart and figure out how it works."

Offline

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