Getting Suspend and Hibernate to work with compiz fusion and the NVIDIA binary driver on a Dell E1505N

I spent several hours hacking this today, and I finally have a surefire (if somewhat hacky) way of getting suspend and resume to work on my Inspiron E1505N.

Because of a bug in the NVIDIA Binary (which supposedly is going to be fixed this september), compiz-fusion crashes pretty much everything on resume.

First: So the first thing you’ll need to do is update your /etx/X11/xorg.conf and add an

“Option “NvAGP” “1″ line in the “Section “Device”"“

Section "Device"          ...          Option           "NvAGP"          "1" EndSection...

Second: Disable warm-booting and vbe post/save options on resume by editing your /etc/default/acpi-support:

...

# Should we attempt to warm-boot the video hardware  on resume?POST_VIDEO=false

# Should we save and restore state using VESA BIOS Extensions?SAVE_VBE_STATE=false

...

Third: Create a file called 25-compiz-kill.sh in your /etc/acpi/resume.d/ After creating it, type in terminal: sudo chmod 711 /etc/acpi/resume.d/25-compiz-kill.sh

#!/bin/bash#/etc/acpi/resume.d/25-compiz-kill.shkillalll compiz.real

Fourth: Create a file in /etc/acpi/resume.d called 99-compiz-resume.sh
            Then type: sudo chmod 711 99-compiz-resume.sh

Edit this file to have the following

#!/bin/bash#/etc/acpi/resume.d/99-compiz-resume.sh

export DISPLAY=:0.0sudo -H -b -u your_user_id compiz --replace &

And lastly, go into compiz-config settings, under General Options, and Display settings, and uncheck v-sync to blank.

And that’s it =) Now it’s important to note that this only works for 1 user. Which is generally fine for a laptop, I wasn’t able to get it to work with the $USER wildcard. If anyone has improvements to this, please let me know. I’m not very good at scripting so there’s obviously a better solution, but this is a very very simple and direct way to do it, so if your more advanced scripts fail, this is pretty much guaranteed to work.

Edit: Thanks to Andy in comments.

Bashisms and a call for a new posix standard

##EDIT##
A friend of mine just advised me of the folly of this, so I retract it. Essentially it seems that *Linux* is the culprit, that when bash is invoked as /bin/sh it should not allow non-posix compliant commands, but does.
##/EDIT##

The prevalence of bash shows that mere codification of an open standard does not in itself mean that anyone will actually follow it, and in fact this might be particularly apt when it comes to open source.

While bash of course does have a posix mode, since bash is so common as the default shell, its very uncommon to use it, and its very common to use bashisms (That is, bash specific behavior that does not conform to POSIX sh). The segue in Ubuntu from bash to dash, and the numerous broken scripts that ensued is a bit of a testament to this.

In open source in particular, because the code is available, often the superior choice is readily apparent, whatever the standard might be. This can actually provide a wide impetus for open source coders to move away from the standard because of it, creating a new de-facto standard. While with a proprietary de-facto standard there is more impetus to move toward an open standard because of the unavailability of the code, and inability to make easy (or easier) transitions from one implementation to the next.

With specific regards to the shell, the particular problem with it is the ambiguity as to what /bin/sh really means. And the unique solution actually does rely in having an open standards: create a new POSIX standard to remove the ambiguity of /bin/sh.

We allready have the Shebang, and the fairly common editor encoding line afterwards which is frequently implemented in more and more editors.

Why not create a new comment line which simply defines what /bin/sh means in the context of the script? The shell can read that line before executing the script and simulate or redirect the script to that environment. Therefore, all that would be required to transition your scripts to a new default shell is to add the comment line to the script? Versions of a particular shell that predate this implementation would simply ignore it as a comment, and you could hack the script as is done now. However it certainly makes your scripts more portable among different distros which use different default environments to have this behavior.

So that is, in short, my call for a new posix standard for shell environments.

Deskbar and voice control

I had a thought while inspired by this little video of a hilarious attempt to use vista’s voice control and I got to thinking about just what is wrong with most attempts at voice control software, and what can be done right.

Essentially, unless you’re physically impaired (and maybe even then) you do not need voice control to work on every aspect of the OS, similarly you do not need it trying to parse input and commands all at once. Taking a lesson from Vim, you should have an input mode, a “command mode”, and perhaps a few more modes. So lets go over an example of what the program might do, comparing it to how I do things in deskbar.

If I want to open up my text editor, I hit alt+F3 and type in text, and it brings me up a list of actions: “Lanch gedit, launch scribes, etc.” all text editors, deskbar also gives me a bunch of other options, such as searching online for text, scrounging through my emails, etc.

With a Voice-deskbar like app, I’d say something along the lines of: “Computer: Open Scribes.”, I’d actually recommend something different from “Computer” such as “Linda” or “Serenity” or something else. Basically it’s a reference to tell the computer you want its attention.

Next you’d have a number of modes: Open, Input, Close, Suspend, Turn Off, Hibernate, Search, Find, Locate, Save, Dictate, Delete, etc. And maybe a visual cue to what “Mode” you’re in. This way, if you told the computer to open Scribes (or Tom Boy), You’d then say “Computer: Input.” and from there
it would save what you had said as voice input into Scribes or Tomboy. Telling it “Computer: Dictate” would instead start the record function, and save your voice as a .ogg file.

As a further example, “Computer: Search Yubnub, gis Firefly” Would search yubnub in firefox and parse: gis Firefly in it (which would in turn tell yubnub to search google image search for firefly. Hence Search is tied to the search engine field in firefox. Find would instead run the Find program in Nautilus, locate would instead use locate or tracker or beagle, respectively.

This is a far more useful application of voice control technology, than attempting to navigate menu items and such which would be better done with either the mouse or the keyboard. And I believe this is actually the right path for voice to take in terms of Human/Computer Interface. E.g., stop trying to do that which is better done by either the mouse or the keyboard.

Edit: Also, instead of using say “Computer” or any other voice command to get the computer’s attention, it could be activated via a modifier key. Such as an unused or seldom used media key, etc.

Desktop UI and Newbie Help Improvements

    This is just a short writeup on things I think could be done to both improve the UI of the linux desktop and also provide better help to complete newbies. First I’ll give you a look at my gnome-panel. I have it situated at the top of my screen, where the eye is naturally drawn to anyways.
    I have no bottom “window switcher” panel, because I instead use a compositing window manager (Compiz-fusion), and an application called Avant Window Navigator. It’s quite superior to the standard window-switcher applet, and also can function as a dock-bar. Anyways, take a look at my panel:

    You may be wondering what the “Start Button” is, it’s actually a program called Deskbar (I’ve just edited the icon file with my own icon)which in many many if not most ways is far superior to the standard category view style of “Application Menu” which happens to be the first icon after the start menu button. The advantage of the category view is that it’s good when you don’t really have any idea what you’re looking for, or what it’s called, in other words, when you just want to browse through your files. The disadvantage is that when you do know what you’re looking for, it’s slower than finding it via deskbar (especially since deskbar remembers the last dozen or so things you’ve done through it). What I percieve as a duplication of both effort and, to coin a term, “visual mindshare” is having to use two different applications to essentially do the same thing: quickly browse through my applications.

    Instead what would be better is to have an alternate “category” mode for deskbar. It could be brought up either through Ctrl+clicking it, or alt+F4 (instead of the default alt+f3), this would bring up a view similar to the standard Main-menu category view.

    Next, since I’ve taken to converting a few people to ubuntu I’ve taken to doing a couple of things to make their lives easier as new users. I usually leave a text file on their desktop with some very basic instructions of “what does what” and “how to do this” and “what not to do” essentially. This isn’t like the ubuntu guide, but rather a more basic explanation of what some of those strange sounding programs and such do. Another thing I do is immediately install a few Firefox extensions that will make their lives loads easier, as well as change the default UI somewhat. Have a look at my Firefox UI standard:

   
    While I install about 18 extensions (Linkification, 3 for AdBlock Plus, the theme I use above, delicious, stumble-upon, tiny menu, Perma tabs, All in one sidebar (not shown), Download statusbar, FireFTP, Unplug, Down Them All!, Cute Menus SVG, Link Alert, Colorful Tabs, and Faviconize tabs), most of them address things I think are shortcomings in Firefox’s default UI. Permanent Tabs however, is there to make their lives much easier. I immediately create a few permanent tabs: Google Homepage, The Ubuntu Guide, and The Ubuntu Forums (which I create an account for them as well).

    In the text file I leave on their desktop I also leave instructions on how to remove the permanent tabs…with a caveat to please read them first. I wish the Official Ubuntu Book was free to distribute in digital form, as It would be nice to just have that sitting on the desktop of every new ubuntu install as well.

    In my next post I’ll write down (since I lost the version I had been using) a new “super newbie guide”.