A few months/weeks/days back I had installed and configured the 'awesomewm' and will confess to still having it installed.  I use Fluxbox daily and probably always will.  scrots to prove it below.  never got the wifi indicator to work.  it eluded me.  It is no harder to navigate in, and once you learned all the key-bindings that come preconfigured in it, things are nice.  Not 'awesome' though.  I played with both the rc/wi.lua files and just never could get that wifi indicator going...





If it just wasn't all 'lua' based.  text configs are the greatest.  as you can see above, i can still log-in and nibble at it...

*****This is a very dated post.  Most new (if not all)  SSD's come with all of this as a standard feature, or it is otherwise built into the Kernel now.*****

I have edited the posts where I advised using the "discard" option in your fstab to enable TRIM.

First, since 2011 or so, TRIM has been enabled by default in the Linux Kernel but not what you'd call optimally.  I don't know the why of that so don't ask!  I have learned over the last few weeks that enabling TRIM using the "discard" option in /etc/fstab will end up significantly slowing your drive down.  That option will make Linux use TRIM the same way Windows does.  (which can cause your drive to slow down)  TRIM tells the SSD drive to delete the information in the blocks and then write to them.  In reality, there is no need to do this every time you write to the disk in Linux.  (yes I know it is arguable, but this seems to be the consensus of the majority)

The smart thing to do is to create a 'cron' job to deal with TRIM, say, once a day, or once a week.  You can do this with the 'fstrim' command.  To see if your SSD drive even supports TRIM try the following in your terminal;

sudo fstrim -v /

If you see no error, and it tells you "/: 19 GiB (20374241280 bytes) trimmed" you'll know you have a TRIM capable drive!  (obviously your size will differ from mine probably).  The above command is a way for you to manually TRIM your SSD drive whenever you like.  The above command was to TRIM the '/' (or root) partition or your SSD.  Do the same thing for your '/home' partition if you create separate partitions on your SSD when you do an install.  So, for '/home';

sudo fstrim -v /home

The 'cron' job would look just a tiny bit different.  Your not going to use the -v option.  Here is a simple and effective way to create your own 'cron' job to TRIM your SSD drives;

sudo medit /etc/cron.daily/fstrim

and create a file with the following


#!/bin/sh
fstrim / && fstrim /home


That takes care of the '/' (or root) and '/home' partitions.

Do not forget to go into the properties of the files you just created and mark them as 'executable'.

You should now get consistent performance from your SSD, as well as quite possibly extending it's lifetime!

Hello all,
Is anyone else noticing a memory leak in LightDM over time?  The longer my system is up the more memory LightDM is consuming.  Rebooted last night when it reached 390Mb's.  Currently after only 5 hrs of uptime it is sitting at 90Mb.  I've not noticed this behavior until only recently.
Thoughts or ideas welcome!

[edit] in just the last few minutes since posting the above, the mem usage has climbed to 112Mb's...
Something weird is going on with my setup evidently.

In regards to this thread > http://vsido.org/index.php?topic=917.0
I got to thinking...
Most of you know what that means.  Here comes the novel...

Linux, PPAPI, and the Browser...  (Originally posted at jedsdesk.com)

In the beginning, was Lynx.  And, it was good.  The time was 1992.  Linux was in it's infancy.  The Internet was becoming more easy to access.  Linux as we know it had reached a milestone.  It was now 1 year old.

I am going to cite some Linux history below to give perspective to why I wrote this article, and further explain my anger at Adobe and Microsoft.

The most popular web server has always been FLOSS since such data has been being collected. For example, Apache is the current #1 web server powering the Internet.  To my knowledge, it has never fell below this statistic.  Contrary to what Microsoft would have you believe, they have never held the number one position.  Ever.  Some current estimates put the number of Internet servers running Linux at or better than 95%.  Microsoft?  About 1%.  Ironically enough, Microsoft's own Azure Cloud services offer "Linux Infrastructure as a Service" (IaaS).

According to the The OSS/FLOSS Numbers Database, Windows NT actually crippled a U.S. Navy Cruiser in 1998.  Almost all of Europe's governments use Linux in some form or fashion, or are in the process of converting existing systems including their educational institutions.  In the U.S. check out the statistics for banks, ATM machines, or mobile devices, or, for that matter, look at the U.S. governments most secretive 3 letter agencies and you'll find they too depend on Linux.  From the NSA, to the CIA, and the Department of Homeland Security.  It is not simply that Linux is free, and the government has run out of money (which they have as we all know seeing how we just passed $18,000,000,000,000 dollars in debt), it is because of the SECURITY.  It is unparalleled in OS history.

Perhaps one of the best papers written regarding OSS/FLOSS, can be found on David Wheeler's site at http://www.dwheeler.com/oss_fs_why.html.  A direct quote from his paper on the site says the following; "More recently, The U.S. Department of Defense Information Systems Agency (DISA) has certified Linux distributor Red Hat's Advanced Server operating system as a "Common Operating Environment" (COE), meaning the server product meets the agency's software security and interoperability specification".

Lets jump ahead to Feb. 22, 2012.  Adobe announces it will no longer be providing updates to Flash for Linux.  The following month, in March, they released version 11.2, officially saying goodbye to Linux.  At the time, Flash was the most common video rendering software available to users on the Internet.  So, Adobe officially has crawled into bed with Microsoft.  While I am of the belief that Flash has outlived its usefulness, it is still widely used and even required to view some websites.  Facebook for example.

Today Adobe has accepted Google's PPAPI code-named "Pepper".  Chrome is the 'ONLY' browser available that can use the PPAPI.  Mozilla, and most other Linux compliant browsers only support NPAPI.  (the N in NPAPI stands for Netscape, the predecessor of Firefox and Iceweasel)  Mozilla has decided (right from the beginning, and stuck to their guns) that they will not work or develop PPAPI implementation for any Mozilla based browser.

It is well known and has been for a long time that the NPAPI has many security flaws and vulnerabilities.  It is an old API.  The problem here is licensing.  Mozilla is concerned by all of the proprietary code involved in the PPAPI, as well as the absolutely horrible documentation from Google.  Iceweasel uses the GNU/GPL licensing allowing it to be used in Linux distro's that firmly support OSS/FLOSS.  PPAPI will never (IMO) adhere to that license.  Firefox to a lesser degree also uses a type of this licensing that while it is not as open as that of Iceweasel, still allows it to be a part of the OSS project.

By stripping NPAPI support, browsers like Firefox and Iceweasel, not to mention numerous other OSS/FLOSS browsers no longer have the ability to serve up video that will now require the PPAPI.  While hopefully HTML5 and CSS3 will eventually solve this problem, for the foreseeable future, Linux users will be forced to use Google's browsers or simply not be able to watch video on the web.  I know that is a broad statement, and perhaps simplifying the situation to some degree, but in fact, an accurate one no less.  Yes, I know there are wrappers that you can use in place of the NPAPI, however, they are not a total fix.  While the 'Youtube All HTML5' plugin allows the user to watch Youtube videos, it is simply not a solution for other video sites on the Internet.  The same holds true with the 'Fresh Player Plugin' a wrapper that supposedly allows the user to take advantage of the PPAPI.  It is a sketchy solution that the last time I checked, was still in the 'Alpha' stage and barely worked on the sites I tried.

I do not have cable, satellite, nor even an antennae to watch television, I do have Netflix.  The various news outlet sites on the Internet provide me with all the news I care to hear about.  Netflix allows me to watch most popular TV shows.  My two kids have never complained about our situation, and personally I think we are better off as a family without television.  I believe the media's purpose is truly the "dumbing down of society".  Another article for another time.  That being said, I do enjoy watching the occasional show on Netflix.  As a Linux user, up until recently the only way I could do this was through a Virtual Machine installed on my Linux box.  Thanks to Google's Chrome browser this is now no longer the case.  Because of this, I have left Firefox and Iceweasel behind.  I have used Mozilla browsers since the early '90's, going all the way back to when it was Netscape.  I loved Mozilla.

I have tried Chromium, which has a more tolerable license than does Chrome, but still no Netflix support.  While I can freely choose to use Chrome, I loathe the fact that the decision is being made for me.  Google claims to utilize the OSS/FLOSS principles when it comes to their browser licensing, but it is a non-free piece of software.  This entirely rules Chrome out for a lot of the Linux community who adhere strongly to their principles when following the GNU/GPL OSS/FLOSS philosophy.  Alas, I am not so firmly entrenched in my philosophy that I wont use Chrome.  I enjoy video on the web, and have made the change to Chrome.  It is an entirely personal choice, and I am in no way endorsing Chrome.  Yes, I could continue to use a VM, but that is an even worse choice as I was forced to use one of those "other" OS's.

For Linux, and all it's non Google browsers, NPAPI is the past.  For me, this falls into the realm of "Unfair Business Practices/Monopoly" category.  The rest of the browser world should have, at the very least, been allowed the opportunity come up with a palatable solution to the PPAPI.  By not having that opportunity, the entire Linux community is being punished IMO by Google, and by default Adobe and Microsoft.  I believe it was an intentional move on all three companies parts to just that end.  Google has gone so far as to remove any NPAPI supported apps/plugins from the Google Play store.  I find this a remarkable move on the part of Google as their Android OS is a Linux distribution itself.  Of course, it comes with Chrome so for their part, this is all a non-issue.

For the rest of the Linux world, everyone should be raising their voice in anger at this type of practice.  Especially from Google!



Apple's iPads and iPhones have never supported Flash.  However Mac's Safari browser, like Microsoft's Internet Explorer, continue to receive updated Flash software from Adobe.  While Linux has been stuck at version 11.2, not so for MS and Apple.  Example below...  (taken directly from the Adobe Flash website)

Adobe Flash Player updates available for OS X on December 12, 2014

Adobe Flash Player updates address a recently identified Adobe Flash Player web plug-in vulnerability.

Huh!

Currently Microsoft and Apple are on version 16.0.0.257.  Adobe stated that security and bug updates would be provided for Linux version 11.2 of the Flash player in Feb. of 2012 for the next 5 years.  My math gives them 2 more years...

Hopefully, as flawed and vulnerable as Flash is, it will be dead and gone long before then.

Jed

Wishing all my VSIDO friends a very Merry Christmas and a really great New Year!  All of you guys make VSIDO what it is, and I must say, this is definitely a pretty Merry place!  Hope all of you and your families have the greatest of Holidays this year!

PS, what better gift to give this year than a VSIDO LiveCD to all your friends and family!

On any new install I do, I always choose the no swap choice from the menu.  However, on the very next reboot, and subsequent reboots after that, it takes quite a while for the system to boot.  This is because in /etc/fstab there is always an entry for /dev/swap that is not commented out.  I have to physically go into fstab and edit this line by commenting it out in order for my boot times to be normal.

This is a look at my fstab after a brand new install;

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc /proc proc defaults 0 0
# /dev/sda1
/dev/sda1 / ext4 relatime,errors=remount-ro 0 1
# /dev/sda2 home
/dev/sda2 /home ext4 relatime 0 0
# /dev/
/dev/ none swap sw 0 0
# cdrom
/dev/cdrom /media/cdrom udf,iso9660 user,noauto,exec,utf8 0 0



After editing it, I have this;

# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>

proc /proc proc defaults 0 0
# /dev/sda1
/dev/sda1 / ext4 defaults,noatime 0 1
# /dev/sda2 home
/dev/sda2 /home ext4 defaults,noatime 0 0
# /dev/
# /dev/ none swap sw 0 0
# cdrom
/dev/cdrom /media/cdrom udf,iso9660 user,noauto,exec,utf8 0 0



Anyone else running into this issue on new installs?  If so, please respond ASAP here.  Be nice to know if it is just me or if it is happening to everyone.  On my installs, I choose to have a separate "/" and "/home".  (as you can see in the fstab posted above)  (The "defaults,noatime" is an edit I make due to having SSD drives.)  I can't imagine what is causing this.  Any input appreciated...

Thanks

I've been waiting for this since Netflix started.  I've been a sullen paying customer for about 7 years now.  Tonight, I'm a happy subscriber!  Forget doing this in a VM, (laggy, unwatchable, and you need to install a compatible OS besides) and for that matter Wine as well!  No more Wine!!!  If I was a hog, I'd be rolling in the mud squealing!!!
So, first thing you have to have is either the beta version or the dev version of Google Chrome.
These are the links for whichever version you go with.  I chose the 'beta' version;

Google Chrome Beta

Google Chrome Dev

If you already use this browser, please be aware that by installing either of the two above versions will overwrite you current install.  Once you have it installed, you'll need to open it and follow these steps using whichever browser you chose above, obviously! 

Once you have installed the browser, you'll need the User Agent Switcher Extension

Once you have that installed, you'll see a new icon at the top right of the browser window.  Right click on it and choose 'Options'.  Your browser window will change and you'll need some information to fill in the appropriate blanks.


   

• Name: Netflix Linux
• String: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/38.0.2114.2 Safari/537.36
• Group: (is filled in automatically)
• Append?: Select 'Replace'
• Flag: IE

The above is the info you need to fill in the blanks.  When your done you should see something like this if it all went right; (the Group box should be filled automagically after you enter the string, just click in the 'Group' box for it to autofill.)



Click the 'Add' button at the far end to save your UA.
Now, load 'netflix.com' in a new tab, and click the User-Agent Switcher toolbar icon, click 'Chrome' and select the 'Netflix Linux' entry. This will reload the page.
BUT, this is even better, you can fix it so it does all this automatigically so you don't have to manually click the button everytime you want to watch Netflix.
You can set a permanent spoof rule to force this user-agent to take effect when loading Netflix:



Same deal, right click the button at the top right in the browser, click on 'Options', and select 'Permanent Spoof List'.  Fill in the domain box with "netflix.com" (no quotes) and in the drop down box select the 'Netflix Linux' rule you created at the beginning.  Voila!  This will work on 32bit and 64bit versions of VSIDO.

Enjoy TV on your most awesome distro, VSIDO!  OK, I'm off to watch an episode of "Caprica"!



Please note that Netflix could at any time stop this "Spoof" from working.  As it is only one line of text, that seems unlikely to me, but stranger things have happened
I also believe special thanks are in order to Mat Enders for these steps.  Also thanks to, wait for it, never thought I'd be saying this, OMG! Ubuntu.   

I like to have the nice desktop layouts that VastOne has created showing on my desktop.  I'm not certain how long it's been happening, (a while now) but I can't resize them.  i.e. they are taking up a third of my desktop no matter which desktop widget layout I use, i.e. VastOne Thin Layout IV.  Instead of nice and small down in the corner like usual it is very very large.  The time slider covers half the screen and the album cover displayed is 4 or 5 times larger than it should be.

Anyone else seeing this, and if so is there a fix?  I really like having it there, but as large as they are, (no matter which layout I choose, not just VastOne's) it makes for an ugly desktop...

I also just did a rm -rf ~/gmusicbrowser and repulled via git.  No change...

Picture is worth a thousand words;

Get it while you can!  Half price through May...

It's here, it's running great!  Get it while you can...

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...

Runs great...

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!

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...
Thanks...

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)

        cd
        git clone git://github.com/ktoso/g73-keyboard-backlight-sh.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
        YOURUSERNAME ALL=(ALL) NOPASSWD:/home/YOURUSERNAME/g73/*

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/light_down.sh
238 :Exec /home/jed/g73/light_up.sh

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.

http://vsido.org/index.php?topic=728.0

This topic has been moved to How To's.

http://vsido.org/index.php?topic=729.0

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 jedsdesk.com)

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!


Section "ServerLayout"
Identifier     "X.org Configured"
Screen      0  "Screen0" 0 0
InputDevice    "Mouse0" "CorePointer"
InputDevice    "Keyboard0" "CoreKeyboard"
EndSection

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"
EndSection

Section "Module"
Load "glx"
EndSection

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

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

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

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"
EndSection

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
EndSubSection
SubSection "Display"
Viewport   0 0
Depth     4
EndSubSection
SubSection "Display"
Viewport   0 0
Depth     8
EndSubSection
SubSection "Display"
Viewport   0 0
Depth     15
EndSubSection
SubSection "Display"
Viewport   0 0
Depth     16
EndSubSection
SubSection "Display"
Viewport   0 0
Depth     24
EndSubSection
EndSection



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


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

Enjoy!

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;

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

"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.