Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - VastOne

#3526
Just another case of me not Being ALL and Seeing ALL

@ Sector11, like anything else, a backup should always be done before applying a patch.  I can only worry about the default settings and the patch to the openbox menu does just that, it corrects the original menu

I completely forgot about vsido-exit-fb ... here it is.  Save it to /usr/bin and make sure it is executable

/usr/bin/vsido-exit-fb

#!/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 FluxBox, please standby...")
os.system("logout.sh")

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()


The spacefm has been corrected too

lwfitz, I like your logout setup .... I will look into replacing the current one with that

I do not understand the need to modify sudoers for it though... It adds a serious level of complexity to the shutdown and build by altering sudoers.. Perhaps it would be easier to add to groups

Thanks everyone for testing and pointing out these issues
#3527
Thank you!

Yes... It will work with your setup

It is copying files to your /home directory

It will correct the OB menu and add several new styles and correct the Fluxbox menu
#3528
^ Excellent and the colors are just right!

Well done EVERYONE!
#3529
Interesting...

I installed audacious

I then ran ran sudo update-menus but nothing changed

Is it possible something else needs to be installed?

Thanks vrkalak
#3530
Beginning with this thread, there will be scripts made available that will update users who have already installed VSIDO with the same updates

Attached is vsido_up.sh.  Simply save it to your /home directory and then follow these steps

Logout and drop to tty1 (ctrl + alt + f1)

chmod +x vsido_up.sh

sudo sh vsido_up.sh

At the end it suggests you reboot, but this is not necessary..

ctrl + d to log out of tty1

ctrl + f7  to get back to the login screen

Login

Profit

This particular update installs the correct conky menu xml and several new themes to Fluxbox and changes the Fluxbox menu to the normal default Fluxbox menu layout (for vrkalak)
#3531
Artwork & Screenshots / Re: March 2013 Screenshots
March 04, 2013, 02:16:11 AM
I knows (I think) ... Fluxbox is seeing it as a panel and controlling it through Slit

Right click on the desktop Fluxbox / Fluxbox Menu / Slit / Placement  and rearrange it there

It does this with my top level Conky but leaves Tint2 alone... hmmm
#3532
Introductions / Re: been here, done that
March 04, 2013, 01:26:45 AM
Quote from: jefsview on March 04, 2013, 01:23:31 AM
And I'm a Pisces -- I like lots of choices and sometimes I head for the extremes  :o

This we have in common! ... I bet you are a musician too
#3533
Sure...

I saw that endless loop chain one time too... It was because for some reason the install of Fluxbox did not have the correct rights on the directory and it could not write what was needed
#3534
I have tested several of these auto-update menu programs and I am not happy with any of them.. All of them take your current menu and replace it which is in no way 'updating' per se

Even the AntiX auto generating one does the same thing and removes everything from their default menu and replaces it

Most of us are used to OB and the menu system... I have no issue with Fluxbox and the need to manually update it for now ... I will keep searching
#3535
I will let you know in a bit lwfitz... Testing now
#3536
Quote from: lwfitz on March 04, 2013, 12:17:59 AM
Im about to install the new ISO and play with fluxbox  a bit and if that doesnt work Im just going to install Gnome3 and be done with it  :D

Blasphemy ! Do that and Be GONE!!!  ???
#3537
Here is an excellent read... Fluxbox Menu Management

Got to love the ArchWiki

This is a good starting point for a discussion on how VSIDO Fluxbox menus should be done

I will check with AntiX to see if their menu generator is available
#3538
Good question... I Have not installed anything new since using it. I know there are a couple of packages ... I know kendall_tristan created FM3 but it does not handle anything in the exec line except the command.  In VSIDO's menu there is 'launch' as part of the exec line which checks to make sure the app is not open already and does not launch a new instance

I am going to test a few things and will get back to you on what is happening with the menu and auto-updating
#3539
Introductions / Re: been here, done that
March 04, 2013, 12:06:02 AM
Welcome to VSIDO Jeff, we are glad that your lurking days are over!

Nice intro and background... It is good to know that people are using VSIDO without the need of these forums to get it going and keep it running

I appreciate the feedback and your kind word!
#3540
General Support / Re: inxi not finding glxinfo
March 03, 2013, 11:50:43 PM
Is it an issue?  I have always seen that and have never paid any attention to it

Doing a search on google for 'Resuming in non X mode: glxinfo not found'  I have found thousands of inxi -F outputs that show the same things

I have always allowed nVidia to handle all glxinfo... and it used to install glxinfo

Definition: glxinfo: display info about a GLX extension and OpenGL renderer.  The glxinfo program can be used to check whether a graphics adaptor provides the OpenGL support that is necessary to run CPN Tools under Linux. Huh?

But, exactly what is glxinfo needed for?  The only thing I ever saw it used on was cairo-dock and since I no longer use cairo, I no longer have needed it

What in VSIDO needs it?

I think it is part of inxi to be used against older video drivers and / or video cards