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.

Topics - jedi

Pages: 1 2 [3] 4 5
General Support / (SOLVED) GMB looks like *&#^
« on: May 10, 2014, 08:11:15 AM »
Hello all...
Recently opened GMB and the looks of it were less than desirable.  Did an rm -rf ~/gmusicbrowser, and then did a git in order to be sure I had the latest version.  (I do)  Below are a couple of scrots to explain things.  I've lost the title bar at the top of the windows as you can see.  I can still do an alt left click and drag them wherever, just would like to have the title bars back.
Also the 2nd issue, my layouts are all screwed!  The one in use in the scrot below is VastOne Latest.  It obviously should not be so large and with the play indicator spread over half my screen real estate, with the titles a mile up and to the left...
Any advice/help appreciated.  Tried hakerdefoe's Trolltech.conf trick a while back with very pleasing results.  This had no effect at all at the time on GMB during the subsequent weeks I used that Trolltech.conf file.  I changed it back to the original Trolltech.conf file with no results.  (Didn't fix anything)
I love VastOne's layouts, and am really wanting them to go back to normal.  Anyone else seen this behavior?

The terminal is showing the output when started from the terminal...

The layout current look.  (VastOne Latest is the layout I'm using)

And as you can see here, no title bars...

Thanks guys and gals...

VSIDO News & Announcements / Liquorix 3.14-2
« on: May 04, 2014, 10:13:27 PM »
Runs great...

Artwork & Screenshots / April 2014 Screenshots
« on: April 01, 2014, 07:47:28 AM »
Time for some scrots of April, and since I've been on a Fringe binge the last week or two, here it is in another color...  Gotta love the gifts to Peter from his dad Dr. Bishop!

General Support / gdebi not working [SOLVED]
« on: March 27, 2014, 11:50:46 AM »
Yes I know it is the lazy mans tool.  I am a lazy man!  I can do a 'dpkg --install foo.deb' with the best of them, but gdebi has always been so convenient.  Just double-click on any .deb file, gdebi automatically started, installed the .deb and all was good.  Now however, double-clicking on a .deb file results in gdebi opening for just a brief second then closing with no error, and failing to install the selected .deb file.
Just wondering if it is my machine or if others are seeing this as well...

Some shots of the latest blizzard results.  These things happen so often up here, they don't even make the news.  Another 2 feet last night!  I'm ready to shed this mortal coil and head someplace a lot warmer!  5 hours of steady snow removal yesterday, and I get to look forward to it again tomorrow!  Well, actually, I have some to do today as the wind hasn't stopped and is slowly filling the driveway again.  The house you see with the snow almost to the roof is my next door neighbor...
As an aside, the roofs look bare due to the high winds dumping all the snow in my driveway.
The tire tracks in the driveway are from windblown snow "after" getting it cleared and having to run for gas...
My poor neighbors;

My front yard;

View from the side door looking West down my driveway;

View looking North from the end of my driveway;

Again, looking west down the driveway at my snowbound Jeep;

Taken the night before during the storm;

This was originally intended for an Asus G73 laptop.  I have an Asus G55VW laptop, and it works great. (It requires the installation of 2 separate scripts!)  I didn't even change the directory name.  (/home/jed/g73)
This is taken directly from the README file included with the g73 script;

1. Clone this repository to your home directory (or wherever you want to, I'll do this example for ~/ for simplicity)

        git clone git:// g73

2. Make sure all scripts are marked executable:

        cd g73
        chmod +x *.sh

3. Take a look at these scripts to make sure you trust them, why? Because they'll need root access, without asking for the password.  Now, we'll add these scripts to allow `sudo`to run them without asking for any password:

        su -c 'visudo' # or 'sudo visudo' if you're a sudoer (on VSIDO etc)

Then just add the following lines at the end of the sudoer file (or similar, with the script names etc). Of course, replace `ktoso` and `/home/ktoso/` with your *username* and *your home directory*. (ktoso is the author of the g73 script, and here's a heartfelt "Thank-You" to ktoso!)

        ## allow running keyboard backlight scripts

Once you have the script installed, open your ~/.fluxbox/keys file and add the following lines (changing username and home directory of course)  I used xev to determine the numbers for the keybindings.  xev is included with VSIDO by default.

# Keyboard Brightness Controls
# keys: dim 237, bright 238
237 :Exec /home/jed/g73/
238 :Exec /home/jed/g73/

Next you'll need to install the 2nd script that is attached below.  There is a README with it as well explaining how to "get 'er done"!  This script adds the necessary files and folders to /sys/class/leds/asus.  This is where the other script gets the info to turn on and off the lights, as well as a dim, bright, brighter setting!

Now with all that said, there is one other little detail I hadn't considered when asked to share this info.  It is intended to work with an Asus laptop as I stated above.  It also relies on the attached scripts to be installed.  This may be a show stopper as it is specific to an Asus laptop.  I'm not sure if names can be changed to protect the innocent, err, I mean work with a different brand/model or not.  This was all just kind of thrown together over the last couple of nights.  Mainly it is here so I can recreate this scenario on my laptop in the event a disaster occurs on my machine!  You'd be amazed at how much simpler this way is than the outrageous hack I had working before!

If you find this confusing, don't worry, I did too!  Patience and Google do pay off.  (I've also been told I'm as stubborn as a mule)  I will also try to help if there are questions.  When it gets right down to it, I don't see why these two scripts couldn't be edited to work with any brand of laptop out there.  I also am not a programmer/scripter by any stretch of the imagination.  I have learned the greatest lesson to be learned in Linux;  Copy/Paste (otherwise known as Ctrl-c, and Ctrl-v)  Seriously.  Scripts are basically 'human readable code', and as such, with a little determination and study you can usually edit them to do what you want.  (I have even got to the point of having written a couple for myself!)

I said all that to say this;  If I can do it, anyone can do it!  BUT, don't expect me, or anyone associated with VSIDO to be responsible for you machine if something goes horribly awry after this exercise.  I mean seriously, would you let a chimp drive your Corvette?

This topic has been moved to How To's.

I'm just going to post my entire xorg.conf file here for perusal.

If, on the other hand, you are happy using the 'nouveau' driver, you will most likely have no xorg.conf file and you should stop reading now.

I've been playing around with graphics on Linux since probably the beginning of the Bumblebee project at least.  (for those interested in Bumblebee for "hybrid-graphics", there is a HowTo I posted here in the HowTo section, and there are several "Bumblebee" articles I've written at

Some may have noticed that upon making the leap to the real deal Nvidia driver, your font sizes are messed up.  By adding the following to your /etc/X11/xorg.conf file, you should be quite happy with the results.

This is a pretty typical xorg.conf file if you happen to need one!  Minor adjustments may be needed to suit your particular hardware!

Code: [Select]
Section "ServerLayout"
Identifier     " Configured"
Screen      0  "Screen0" 0 0
InputDevice    "Mouse0" "CorePointer"
InputDevice    "Keyboard0" "CoreKeyboard"

Section "Files"
ModulePath   "/usr/lib/xorg/modules"
FontPath     "/usr/share/fonts/X11/misc"
FontPath     "/usr/share/fonts/X11/cyrillic"
FontPath     "/usr/share/fonts/X11/100dpi/:unscaled"
FontPath     "/usr/share/fonts/X11/75dpi/:unscaled"
FontPath     "/usr/share/fonts/X11/Type1"
FontPath     "/usr/share/fonts/X11/100dpi"
FontPath     "/usr/share/fonts/X11/75dpi"
FontPath     "built-ins"

Section "Module"
Load "glx"

Section "InputDevice"
Identifier  "Keyboard0"
Driver      "kbd"

Section "InputDevice"
Identifier  "Mouse0"
Driver      "mouse"
Option     "Protocol" "auto"
Option     "Device" "/dev/input/mice"
Option     "ZAxisMapping" "4 5 6 7"

Section "Monitor"
Identifier   "Monitor0"
VendorName   "Monitor Vendor"
ModelName    "Monitor Model"

Section "Device"
        ### Available Driver options are:-
        ### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
        ### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
        ### <percent>: "<f>%"
        ### [arg]: arg optional
        #Option     "SWcursor"            # [<bool>]
        #Option     "HWcursor"            # [<bool>]
        #Option     "NoAccel"            # [<bool>]
        #Option     "ShadowFB"            # [<bool>]
        #Option     "VideoKey"            # <i>
        #Option     "WrappedFB"          # [<bool>]
        #Option     "GLXVBlank"          # [<bool>]
        #Option     "ZaphodHeads"        # <str>
        #Option     "PageFlip"            # [<bool>]
        #Option     "SwapLimit"          # <i>
        #Option     "AsyncUTSDFS"        # [<bool>]
Identifier  "Card0"
Driver "nvidia"
Option      "Coolbits" "1"
Option      "AddARGBGLXVisuals" "true"
Option      "TripleBuffer" "false"
BusID       "PCI:1:0:0"

Section "Screen"
Identifier "Screen0"
Device     "Card0"
Monitor    "Monitor0"
        Option "DPI" "90 x 90"   #these are the two lines to add!!!
        Option "nologo" "true"         #these are the two lines to add!!!
SubSection "Display"
Viewport   0 0
Depth     1
SubSection "Display"
Viewport   0 0
Depth     4
SubSection "Display"
Viewport   0 0
Depth     8
SubSection "Display"
Viewport   0 0
Depth     15
SubSection "Display"
Viewport   0 0
Depth     16
SubSection "Display"
Viewport   0 0
Depth     24

Section "Extensions"
Option      "Composite" "enable"
# Option      "RENDER" "disable"

In the part of the file thats heading says 'Section "Screen"', underneath the "Monitor   Monitor0" line there are two additions you need to make.  These are both "Option" settings.  They are as follows;
Code: [Select]
        Option "DPI" "90 x 90"
        Option "nologo" "true"

The DPI option reduces the fonts system wide to the normal 90 x 90 that the nouveau driver was showing you all this time.  (the easy explanation  ;) )  The next line will stop the Nvidia splash logo from appearing everytime you reboot.  (right before it gets to the lightdm login screen)


PS there is also the option (which has NEVER worked for me) of supposedly being able to enable the FN key on laptops to adjust the brightness level of your screen.  You can add it right after the two lines you added above.  It is as follows;

Code: [Select]
Option "RegistryDwords" "EnableBrightnessControl=1"
Adding it wont hurt anything, but good luck getting it to work.  If someone here on the forums is great at describing how to "map keybindings" please post here how to do it!  (or PM me and I'll be happy to write it up and credit whoever gets me correct directions)  I have been totally unsuccessful at mapping the FN keys on my laptop, short of some outrageous hacks that I'd never post here out of sheer embarrassment!  (i.e. Keyboard backlight brightness FN keys, Volume Up, Down, and Mute FN keys, the brightness control keys, etc...)

How To's / USB 3-1.3: device descriptor read/64, error -110
« on: March 04, 2014, 01:31:24 AM »
"USB 3-1.3: device descriptor read/64, error -110" or "-60" or "-32" or "-71" and so on...

This has been an ongoing issue for me for a long time.  It can also be seen as something like "Bluetooth patch file failed to load" or something similar.  Also as "ath3k failed to load" type errors.

In order to fix it I did a Google search for "ath3k-1.fw for Debian Sid".  Followed the link to the ftp site for Debian SID, downloaded the .deb file, and then ran it using g-debi.  (yes I'm lazy and g-debi works just great)  Or, alternatively, you could just do a simple "sudo apt-get install firmware-atheros"!!!  Once it installed, I went to /etc/modules and added ath3k to the list that is in the modules file.  (you'll have to edit that file as root)  Then from a terminal, I ran "sudo modprobe -v ath3k".  (with no errors!  If you get an error, I'm sorry, I haven't experimented any further since this worked for me.)  After all of this was completed, since I have a laptop, I did a full shutdown, pulled the battery, and let the laptop sit for a couple of minutes.  Put the battery back in, plugged it in, booted it up, and voilà!  No more error on boot-up.

Hope this helps someone.  On some reboots it was taking up to a couple of minutes to boot up.  I am now back to "almost" instantaneous boots!  I'm glad it is finally resolved, and yes, I had this issue with systemd, as well as with sysVinit.  It pokes it's head up as various errors, but always comes back to the Atheros chip firmware.  I did just recently hear that it'll be included in future builds of VSIDO!  As to the cause of the error, the more I read the more "reasons" for the error I came up with!  Long story short, the above should help, and if not, just keep Google busy till a better fix can be found.

I've Got a Life / Some pics taken at or around my house
« on: February 18, 2014, 09:19:35 PM »
I live in Northern Maine, in the great North Maine Woods!  A very beautiful part of Maine folks here refer to as The County.  People in Central and Southern Maine, call this area "The Other Maine".
In spare time, when "I've Got a Life", I love to take pic's.  I'm not the best at it, and having a very nice DSLR (Nikon with about a dozen different lenses) makes it real easy to get some good shots once in a while.
I'll post some of the ones I've taken over the last 4 or 5 years, up to today, for you to get a chuckle out of!

Backyard Racoon;


The view from my wife's parents front yard;

Backyard critters;

General Support / Host Name - exim4 - Internal Mail - DNS issue?
« on: February 05, 2014, 03:26:05 AM »
Not having troubles per se, but was wondering if someone smarter than me could point me to the file to fix this;

Code: [Select]
jed@vsido U=jed P=local S=294
My hostname is jedsdesk on my VSIDO install.  /etc/hosts and /etc/hostname both reflect that correctly...  However, I've had to reinstall 'exim4' in order to get the internal mail working.  This was the error just prior to re-installing 'exim4'.

Code: [Select]
jed@jedsdesk:~$ mail jed
Subject: test
Cc: 2014-02-04 20:43:28 1WArWS-00061S-Ci Cannot open main log file "/var/log/exim4/mainlog": Permission denied: euid=102 egid=105
2014-02-04 20:43:28 1WArWS-00061S-Ci <= jed@vsido U=jed P=local S=294
2014-02-04 20:43:28 1WArWS-00061S-Ci Cannot open main log file "/var/log/exim4/mainlog": Permission denied: euid=102 egid=105
exim: could not open panic log - aborting: see message(s) above
Can't send mail: sendmail process failed with error code 1

Advice/help appreciated!

Artwork & Screenshots / December 2013 Screenshots
« on: December 04, 2013, 05:24:46 AM »
Start off December with one of mine...
Some really great scrots for November!

My first weather template for mrpeachy's v9000 weather script.  Just wanted something simple...

Feedback & Suggestions / Linux writers wanted!
« on: November 15, 2013, 03:22:03 PM »
Hey everyone!  If there are any of you interested in writing anything to do with Linux and allowing me to post it on I would be humbly grateful.  Anything from why you use it, to how to use something in particular.  Tips and tricks, Howto's, anything to point people to VSIDO, or just Linux in general.  Anything to pull in new Linux users.
I am trying to be more dedicated in my posting there, and it is paying off in site visits!  If your interested, let me know and I can set it up so you can post there whenever you feel that creative urge kicking in.
Of course anything posted there about VSIDO is also welcome to be posted here as well.  Just trying to get the good word out about VSIDO and Linux!

This weeks ISO's were built by me, (jedi) as we're testing for disaster recovery situations. 

VSIDO Raptor 32bit & 64bit ISO’s updated 27-Oct-2013 22:40 EDST

Both ISO's were updated, built, installed, tested and uploaded today with no issues

    Updated to the latest SID levels

Pages: 1 2 [3] 4 5