Posted by: richlyn | October 6, 2011

RIP Steve Jobs

The Tech World has lost a visionary and a genius….Words fail to describe this man. I am not going to describe him or give his biography (all of that and more  including rare pictures are overflowing on the web) or write more that just a few lines.

Steve Jobs …you will be greatly missed. My heartfelt condolences to Family, Friends and all at Apple.

from his 2005 commencement speech at Stanford University:

“Remembering that I’ll be dead soon is the most important tool I’ve ever encountered to help me make the big choices in life. Because almost everything—all external expectations, all pride, all fear of embarrassment or failure—these things just fall away in the face of death, leaving only what is truly important. Remembering that you are going to die is the best way I know to avoid the trap of thinking you have something to lose. You are already naked. There is no reason not to follow your heart.

Your time is limited, so don’t waste it living someone else’s life. Don’t be trapped by dogma—which is living with the results of other people’s thinking. Don’t let the noise of others’ opinions drown out your own inner voice.”

Posted by: richlyn | May 26, 2011

Gnome 3 PPA in Oneiric

Oneiric development has started and word it that Gnome 3 PPA will be included in the Ubuntu main repos unlike in Natty.

Thats some news to Gnome loyalists who have been using Ubuntu all this while! Due to the high priority of Unity in the Ubuntu 11.04 development cycle, the inclusion of GNOME3 into Ubuntu were postponed until 11.10, and Unity was shipped in Ubuntu 11.04 as a shell for GNOME2 instead. In 11.10 Moreover, since the Unity shell will run on the GNOME3 stack for 11.10, installing GNOME3 with GNOME Shell won’t affect the Unity desktop session and you will have a choice to boot into either Unity or GNOME Shell at the login screen.

For Appindicators a smart detection mechanism will be implemented to only show AppIndicators if a Unity desktop is detected. If instead vanilla GNOME is found it will fall back to the default upstream behaviour seamlessly.

Posted by: richlyn | May 23, 2011

Upgrading to Gnome 3 on Maverick Meerkat

I tried Upgrading to Gnome 3 Desktop shell on Ubuntu 10.10 but got there error, However was able to have a glimpse of Gnome 3 which was simply beautiful.

richlyn@richlyn-maverick:~$ sudo add-apt-repository ppa:gnome3-team/gnome3

Executing: gpg –ignore-time-conflict –no-options –no-default-keyring –secret-keyring /etc/apt/secring.gpg –trustdb-name /etc/apt/trustdb.gpg –keyring /etc/apt/trusted.gpg –primary-keyring /etc/apt/trusted.gpg –keyserver keyserver.ubuntu.com –recv 9D542E3D52C801D9F8E31682F1773AF13B1510FD

gpg: requesting key 3B1510FD from hkp server keyserver.ubuntu.com

gpg: key 3B1510FD: public key “Launchpad PPA for GNOME3 Team” imported

gpg: Total number processed: 1

gpg:               imported: 1  (RSA: 1)

richlyn@richlyn-maverick:~$ sudo apt-get update

Get:1 http://extras.ubuntu.com maverick Release.gpg [72B]                      

Ign http://extras.ubuntu.com/ubuntu/ maverick/main Translation-en             

Get:2 http://ppa.launchpad.net maverick Release.gpg [316B]                    

Ign http://ppa.launchpad.net/bisigi/ppa/ubuntu/ maverick/main Translation-en  

Ign http://ppa.launchpad.net/bisigi/ppa/ubuntu/ maverick/main Translation-en_IN

Get:3 http://archive.canonical.com maverick Release.gpg [198B]                

Ign http://archive.canonical.com/ maverick/partner Translation-en             

Ign http://extras.ubuntu.com/ubuntu/ maverick/main Translation-en_IN          

Hit http://extras.ubuntu.com maverick Release                                 

Get:4 http://archive.ubuntu.com maverick Release.gpg [198B]                   

Ign http://archive.ubuntu.com/ubuntu/ maverick/main Translation-en            

Ign http://archive.ubuntu.com/ubuntu/ maverick/main Translation-en_IN         

Get:5 http://ppa.launchpad.net maverick Release.gpg [316B]                    

Ign http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ maverick/main Translation-en

Ign http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ maverick/main Translation-en_IN

Hit http://ppa.launchpad.net maverick Release                                 

Ign http://archive.canonical.com/ maverick/partner Translation-en_IN          

Hit http://archive.canonical.com maverick Release                             

Hit http://extras.ubuntu.com maverick/main Sources                            

Ign http://archive.ubuntu.com/ubuntu/ maverick/multiverse Translation-en      

Ign http://archive.ubuntu.com/ubuntu/ maverick/multiverse Translation-en_IN   

Ign http://archive.ubuntu.com/ubuntu/ maverick/restricted Translation-en      

Ign http://archive.ubuntu.com/ubuntu/ maverick/restricted Translation-en_IN   

Ign http://archive.ubuntu.com/ubuntu/ maverick/universe Translation-en        

Ign http://archive.ubuntu.com/ubuntu/ maverick/universe Translation-en_IN     

Get:6 http://archive.ubuntu.com maverick-updates Release.gpg [198B]           

Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/main Translation-en    

Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/main Translation-en_IN 

Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/multiverse Translation-en

Get:7 http://ppa.launchpad.net maverick Release [9,742B]                      

Hit http://archive.canonical.com maverick/partner amd64 Packages              

Hit http://extras.ubuntu.com maverick/main amd64 Packages                     

Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/multiverse Translation-en_IN

Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/restricted Translation-en

Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/restricted Translation-en_IN

Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/universe Translation-en

Ign http://archive.ubuntu.com/ubuntu/ maverick-updates/universe Translation-en_IN

Get:8 http://archive.ubuntu.com maverick-security Release.gpg [198B]          

Ign http://archive.ubuntu.com/ubuntu/ maverick-security/main Translation-en   

Ign http://archive.ubuntu.com/ubuntu/ maverick-security/main Translation-en_IN

Ign http://archive.ubuntu.com/ubuntu/ maverick-security/multiverse Translation-en

Ign http://archive.ubuntu.com/ubuntu/ maverick-security/multiverse Translation-en_IN

Hit http://ppa.launchpad.net maverick/main Sources                            

Hit http://ppa.launchpad.net maverick/main amd64 Packages                     

Ign http://archive.ubuntu.com/ubuntu/ maverick-security/restricted Translation-en

Ign http://archive.ubuntu.com/ubuntu/ maverick-security/restricted Translation-en_IN

Ign http://archive.ubuntu.com/ubuntu/ maverick-security/universe Translation-en

Ign http://archive.ubuntu.com/ubuntu/ maverick-security/universe Translation-en_IN

Hit http://archive.ubuntu.com maverick Release                                

Get:9 http://ppa.launchpad.net maverick/main Sources [14B]                    

Get:10 http://ppa.launchpad.net maverick/main amd64 Packages [14B]            

Hit http://archive.ubuntu.com maverick-updates Release                        

Hit http://archive.ubuntu.com maverick-security Release                       

Hit http://archive.ubuntu.com maverick/main Sources                           

Hit http://archive.ubuntu.com maverick/restricted Sources                     

Hit http://archive.ubuntu.com maverick/universe Sources                       

Hit http://archive.ubuntu.com maverick/multiverse Sources                     

Hit http://archive.ubuntu.com maverick/main amd64 Packages                    

Hit http://archive.ubuntu.com maverick/restricted amd64 Packages              

Hit http://archive.ubuntu.com maverick/universe amd64 Packages                

Hit http://archive.ubuntu.com maverick/multiverse amd64 Packages

Hit http://archive.ubuntu.com maverick-updates/main Sources

Hit http://archive.ubuntu.com maverick-updates/restricted Sources

Hit http://archive.ubuntu.com maverick-updates/universe Sources

Hit http://archive.ubuntu.com maverick-updates/multiverse Sources

Hit http://archive.ubuntu.com maverick-updates/main amd64 Packages

Hit http://archive.ubuntu.com maverick-updates/restricted amd64 Packages

Hit http://archive.ubuntu.com maverick-updates/universe amd64 Packages

Hit http://archive.ubuntu.com maverick-updates/multiverse amd64 Packages

Hit http://archive.ubuntu.com maverick-security/main Sources

Hit http://archive.ubuntu.com maverick-security/restricted Sources

Hit http://archive.ubuntu.com maverick-security/universe Sources

Hit http://archive.ubuntu.com maverick-security/multiverse Sources

Hit http://archive.ubuntu.com maverick-security/main amd64 Packages

Hit http://archive.ubuntu.com maverick-security/restricted amd64 Packages

Hit http://archive.ubuntu.com maverick-security/universe amd64 Packages

Hit http://archive.ubuntu.com maverick-security/multiverse amd64 Packages

Fetched 11.3kB in 51s (220B/s)

Reading package lists… Done

richlyn@richlyn-maverick:~$ sudo apt-get install gnome3-session

Reading package lists… Done

Building dependency tree      

Reading state information… Done

The following packages were automatically installed and are no longer required:

  linux-headers-2.6.35-22-generic linux-headers-2.6.35-22

Use ‘apt-get autoremove’ to remove them.

The following extra packages will be installed:

  gir1.0-atk-1.0 gir1.0-clutter-1.0 gir1.0-freedesktop gir1.0-gconf-2.0

  gir1.0-gdkpixbuf-2.0 gir1.0-gtk-2.0 gir1.0-json-glib-1.0 gir1.0-mutter-2.31

  gir1.0-pango-1.0 gjs gnome-shell libgjs0a libglew1.5 libmutter-private0

  mesa-utils mutter mutter-common xserver-xephyr

Suggested packages:

  desktop-base glew-utils gnome-themes

The following NEW packages will be installed:

  gir1.0-atk-1.0 gir1.0-clutter-1.0 gir1.0-freedesktop gir1.0-gconf-2.0

  gir1.0-gdkpixbuf-2.0 gir1.0-gtk-2.0 gir1.0-json-glib-1.0 gir1.0-mutter-2.31

  gir1.0-pango-1.0 gjs gnome-shell gnome3-session libgjs0a libglew1.5

  libmutter-private0 mesa-utils mutter mutter-common xserver-xephyr

0 upgraded, 19 newly installed, 0 to remove and 114 not upgraded.

Need to get 1,623kB/3,061kB of archives.

After this operation, 9,613kB of additional disk space will be used.

Do you want to continue [Y/n]? y

Get:1 http://archive.ubuntu.com/ubuntu/ maverick/universe gnome-shell amd64 2.31.5-2ubuntu2 [613kB]

Get:2 http://archive.ubuntu.com/ubuntu/ maverick/universe gnome3-session all 2.32.0-0ubuntu1 [3,004B]

Get:3 http://archive.ubuntu.com/ubuntu/ maverick-updates/main xserver-xephyr amd64 2:1.9.0-0ubuntu7.3 [1,006kB]

Fetched 1,393kB in 1min 59s (11.6kB/s)                                         

Selecting previously deselected package gir1.0-atk-1.0.

(Reading database … 227486 files and directories currently installed.)

Unpacking gir1.0-atk-1.0 (from …/gir1.0-atk-1.0_1.32.0-0ubuntu1_amd64.deb) …

Selecting previously deselected package gir1.0-freedesktop.

Unpacking gir1.0-freedesktop (from …/gir1.0-freedesktop_0.9.3-0ubuntu4_amd64.deb) …

Selecting previously deselected package gir1.0-json-glib-1.0.

Unpacking gir1.0-json-glib-1.0 (from …/gir1.0-json-glib-1.0_0.10.2-2ubuntu2.1_amd64.deb) …

Selecting previously deselected package gir1.0-pango-1.0.

Unpacking gir1.0-pango-1.0 (from …/gir1.0-pango-1.0_1.28.2-0ubuntu1.1_amd64.deb) …

Selecting previously deselected package gir1.0-clutter-1.0.

Unpacking gir1.0-clutter-1.0 (from …/gir1.0-clutter-1.0_1.2.12-0ubuntu13_amd64.deb) …

Selecting previously deselected package gir1.0-gconf-2.0.

Unpacking gir1.0-gconf-2.0 (from …/gir1.0-gconf-2.0_2.31.91-0ubuntu3.1_amd64.deb) …

Selecting previously deselected package gir1.0-gdkpixbuf-2.0.

Unpacking gir1.0-gdkpixbuf-2.0 (from …/gir1.0-gdkpixbuf-2.0_2.22.0-0ubuntu1_amd64.deb) …

Selecting previously deselected package gir1.0-gtk-2.0.

Unpacking gir1.0-gtk-2.0 (from …/gir1.0-gtk-2.0_2.22.0-0ubuntu1_amd64.deb) …

Selecting previously deselected package gir1.0-mutter-2.31.

Unpacking gir1.0-mutter-2.31 (from …/gir1.0-mutter-2.31_2.31.5-0ubuntu9_amd64.deb) …

Selecting previously deselected package libgjs0a.

Unpacking libgjs0a (from …/libgjs0a_0.7.1-1ubuntu4_amd64.deb) …

Selecting previously deselected package gjs.

Unpacking gjs (from …/gjs_0.7.1-1ubuntu4_amd64.deb) …

Selecting previously deselected package mutter-common.

Unpacking mutter-common (from …/mutter-common_2.31.5-0ubuntu9_all.deb) …

Selecting previously deselected package libmutter-private0.

Unpacking libmutter-private0 (from …/libmutter-private0_2.31.5-0ubuntu9_amd64.deb) …

Selecting previously deselected package mutter.

Unpacking mutter (from …/mutter_2.31.5-0ubuntu9_amd64.deb) …

Selecting previously deselected package libglew1.5.

Unpacking libglew1.5 (from …/libglew1.5_1.5.2-0ubuntu1_amd64.deb) …

Selecting previously deselected package mesa-utils.

Unpacking mesa-utils (from …/mesa-utils_8.0.1-0ubuntu1_amd64.deb) …

Selecting previously deselected package gnome-shell.

Unpacking gnome-shell (from …/gnome-shell_2.31.5-2ubuntu2_amd64.deb) …

Selecting previously deselected package gnome3-session.

Unpacking gnome3-session (from …/gnome3-session_2.32.0-0ubuntu1_all.deb) …

Selecting previously deselected package xserver-xephyr.

Unpacking xserver-xephyr (from …/xserver-xephyr_2%3a1.9.0-0ubuntu7.3_amd64.deb) …

Processing triggers for gconf2 …

Processing triggers for man-db …

Processing triggers for desktop-file-utils …

Processing triggers for python-gmenu …

Rebuilding /usr/share/applications/desktop.en_IN.cache…

Processing triggers for libglib2.0-0 …

Processing triggers for python-support …

Setting up gir1.0-atk-1.0 (1.32.0-0ubuntu1) …

Setting up gir1.0-freedesktop (0.9.3-0ubuntu4) …

Setting up gir1.0-json-glib-1.0 (0.10.2-2ubuntu2.1) …

Setting up gir1.0-pango-1.0 (1.28.2-0ubuntu1.1) …

Setting up gir1.0-clutter-1.0 (1.2.12-0ubuntu13) …

Setting up gir1.0-gconf-2.0 (2.31.91-0ubuntu3.1) …

Setting up gir1.0-gdkpixbuf-2.0 (2.22.0-0ubuntu1) …

Setting up gir1.0-gtk-2.0 (2.22.0-0ubuntu1) …

Setting up gir1.0-mutter-2.31 (2.31.5-0ubuntu9) …

Setting up libgjs0a (0.7.1-1ubuntu4) …

Setting up gjs (0.7.1-1ubuntu4) …

Setting up mutter-common (2.31.5-0ubuntu9) …

Setting up libmutter-private0 (2.31.5-0ubuntu9) …

Setting up mutter (2.31.5-0ubuntu9) …

Setting up libglew1.5 (1.5.2-0ubuntu1) …

Setting up mesa-utils (8.0.1-0ubuntu1) …

Setting up gnome-shell (2.31.5-2ubuntu2) …

Setting up gnome3-session (2.32.0-0ubuntu1) …

Setting up xserver-xephyr (2:1.9.0-0ubuntu7.3) …

Processing triggers for libc-bin …

ldconfig deferred processing now taking place

richlyn@richlyn-maverick:~$ gnome-shell –replace

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

      JS LOG: GNOME Shell started at Mon May 23 2011 10:53:21 GMT+0530 (IST)

      JS LOG: Failed to acquire org.freedesktop.Notifications; trying again

    JS ERROR: !!!   Exception was: TypeError: this._gdm.list_users is not a function

    JS ERROR: !!!     lineNumber = ’70’

    JS ERROR: !!!     fileName = ‘/usr/share/gnome-shell/js/ui/statusMenu.js’

    JS ERROR: !!!     message = ‘this._gdm.list_users is not a function’

    JS ERROR: !!!     stack = ‘([object _private_Gdm_UserManager])@/usr/share/gnome-shell/js/ui/statusMenu.js:70

([object _private_Gdm_UserManager])@/usr/share/gjs-1.0/lang.js:110

Error(“Chained exception”)@:0

(“Chained exception”)@gjs_throw:0

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/Signs.VOB”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/Signs.VOB’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/Kippur (2000) CD1.avi”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/Kippur%20(2000)%20CD1.avi’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/India Vs Pakistan – WC SF Highlights HDTV.mp4”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/India%20Vs%20Pakistan%20-%20WC%20SF%20Highlights%20HDTV.mp4’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/The Backup Plan.2010.mkv”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/The%20Backup%20Plan.2010.mkv’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/case 39/Case 39.avi”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/case%2039/Case%2039.avi’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/The.Royal.Wedding.2011.Pre-Wedding.Preparations.and.Opening.of.Doors.CD1.avi”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/The.Royal.Wedding.2011.Pre-Wedding.Preparations.and.Opening.of.Doors.CD1.avi’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/Taxi Driver.avi”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/Taxi%20Driver.avi’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/The.Royal.Wedding.2011.Pre-Wedding.Preparations.and.Opening.of.Doors.CD2.avi”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/The.Royal.Wedding.2011.Pre-Wedding.Preparations.and.Opening.of.Doors.CD2.avi’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/The Final.mkv”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/The%20Final.mkv’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/Re_urgrove.com.mkv”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/Re_urgrove.com.mkv’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/media/DA1B-9B04/royal.wedding.part.two.cd3.avi”

totem-video-thumbnailer couldn’t open file ‘file:///media/DA1B-9B04/royal.wedding.part.two.cd3.avi’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/media/DA1B-9B04/royal.wedding.part.one.cd2.hdtv.xvid-2hd.avi”

totem-video-thumbnailer couldn’t open file ‘file:///media/DA1B-9B04/royal.wedding.part.one.cd2.hdtv.xvid-2hd.avi’

Reason: Location not found..

Error loading document: Error opening file: No such file or directory

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/media/DA1B-9B04/royal.wedding.part.two.cd1.avi”

totem-video-thumbnailer couldn’t open file ‘file:///media/DA1B-9B04/royal.wedding.part.two.cd1.avi’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/media/DA1B-9B04/The.Royal.Wedding.2011.Part.One.Pre-Wedding.Preparations.and.Opening.of.Doors.HDTV.XviD-2HD.avi”

totem-video-thumbnailer couldn’t open file ‘file:///media/DA1B-9B04/The.Royal.Wedding.2011.Part.One.Pre-Wedding.Preparations.and.Opening.of.Doors.HDTV.XviD-2HD.avi’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/media/HDD/Movies/What Women Really Want.avi”

totem-video-thumbnailer couldn’t open file ‘file:///media/HDD/Movies/What%20Women%20Really%20Want.avi’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/media/DA1B-9B04/royal.wedding.part.one.cd1.hdtv.xvid-2hd.avi”

totem-video-thumbnailer couldn’t open file ‘file:///media/DA1B-9B04/royal.wedding.part.one.cd1.hdtv.xvid-2hd.avi’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/Disclosure [1994]/Disclosure.1994.by.Noodle.rmvb”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/Disclosure%20%5B1994%5D/Disclosure.1994.by.Noodle.rmvb’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/home/richlyn/Videos/NnWBGn.2010.BRRip_urgrove.com.mkv”

totem-video-thumbnailer couldn’t open file ‘file:///home/richlyn/Videos/NnWBGn.2010.BRRip_urgrove.com.mkv’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/media/DA1B-9B04/WILIAM.DVD_urgrove.com.mkv”

totem-video-thumbnailer couldn’t open file ‘file:///media/DA1B-9B04/WILIAM.DVD_urgrove.com.mkv’

Reason: Location not found..

** Message: Error: Resource not found.

gstfilesrc.c(1055): gst_file_src_start (): /GstPlayBin2:play/GstURIDecodeBin:uridecodebin0/GstFileSrc:source:

No such file “/media/DA1B-9B04/Salaam Bombay_2.avi”

totem-video-thumbnailer couldn’t open file ‘file:///media/DA1B-9B04/Salaam%20Bombay_2.avi’

Reason: Location not found..

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

    JS ERROR: !!!   Unhandled type int32 releasing GArgument

Posted by: richlyn | May 23, 2011

Unity Vs Gnome3

At the Ubuntu Developer Summit in Orlando Mark Shuttleworth   announced that  Canonical  will be shipping the Unity environment in the Ubuntu desktop edition. This news came as a surprise to many in the Linux World and Sock Ubuntu Loyalists.  Before there were questions thrown he also said “Ubuntu is a GNOME distribution, we ship the GNOME stack, we will continue to ship GNOME apps, and we optimize Ubuntu for GNOME. The only difference is that Unity is a different shell for GNOME, but we continue to support the latest GNOME Shell development work in the Ubuntu archives.”

Questions arise as to Why the change, what will be different and then what’s the best.

Why?

Unity is Ubuntu’s alternative for Gnome Shell. Canonical didn’t like the direction Gnome was going, I think partly because they prioritize new users and the intuitiveness of the interface. Also, Canonical hopes to make future versions of Ubuntu tablet-ready, while Gnome Shell is, I think, moving in a touch-unfriendly direction.

Jeff Waugh tweeted  “Unity as default shell == brand before community, differentiation before collaboration.” Canonical values the Ubuntu brand, as they should – but in recent times there has been a move to favour that brand over a better core product that all can share. Canonical wanted their own ideas and design to be embedded within a desktop environment and call it their own baby hence Unity was born though its still based on the Gnome without its Shell.  Some OStatic readers who favor GNOME as a desktop environment are miffed. BastetFurry writes: “Either someone makes a branch distro with GNOME or its bye-bye Ubuntu for me.” And  Matt W: “Canonical, please remember beauty and usability are opinions held by the end user.” Now, Stormy Peters, Executive Director of the GNOME Foundation has weighed in, and she makes a number of good points. In Peters’ post “What’s Next in GNOME’s Future?” she writes:

“Many developers were really disappointed to hear that Unity will be the default shell on Ubuntu. Some are disappointed because they don’t like Unity. Others are disappointed because they feel like Canonical is doing its own thing instead of working with the greater GNOME community to reach a compromise that works for all.

What’s different?

Although its development is being managed by Canonical, Unity can be run on any distro that meets the requirements of Gnome and Compiz and is slated to be included in the repos for future iterations of Debian. Unity and Gnome Shell both depend on Gnome and are simply applications running over a Gnome session (minus a few ordinarily required sessions and services) so there’s always the option of logging into a Classic session. Unity will be themed in the usual GTK method and now accepts panel themes; Gnome Shell can’t be easily themed yet but is using CSS, which will make themes easy to develop in the near future.

Check the basic difference in this image  and the wiki page here.

Gnome Shell depends on Mutter (Metacity + Clutter) and conflicts with Compiz, while Unity depends on Compiz with Mutter as a fallback for low-end machines. This means that Unity is normally a Compiz Fusion plugin but conflicts with some old plugins (for instance, the Desktop Cube.) On the other hand, Unity retains a higher degree of visual continuity with Compiz than the Classic desktop. For instance, Expo doesn’t treat the new Panel and Launcher as a window tied to a particular desktop, so the panel remains accessible during desktop switching.

In terms of direct usability, Unity uses a more conventional method of task switching, workplace management, and window control, while Gnome Shell uses new features like automatic workspaces and has apparently dropped the idea of minimizing windows altogether.

Ubuntu Unity, at first glance, will be much more accessible to new users. Why? The new user is not going to immediately know to hover their mouse in the upper left corner or click the Activities button to open up the launcher menu. In Unity, the launchers are right there on the desktop, waiting to be clicked and used.

Once you get beyond the surface, a few glaring issues start popping up for Ubuntu Unity. I will highlight the most glaring.

Connect to server:  One of the most handy menu entries in GNOME (for me at least) is the Connect to Server entry in the Places menu. This allows the user to connect to nearly any type of server quickly and easily. The user can even connect to a Windows Share from here. In Unity – you won’t find that. In fact, you will be hard pressed to find any means to connect to a server in Ubuntu Unity. The only way to make any sort of connection in Ubuntu Unity is:

  1. Open Nautilus from the command line.
  2. Click Go | Network and then attempt to connect to your Windows network.

This, however, did not work for me. From GNOME Shell I could effortlessly connect to my shared folders using the Connect to Server wizard. From Ubuntu Unity…no dice. Even though I know Samba is configured correctly and working, Ubuntu Unity simply wouldn’t play along.

Configuring the desktop:  In order to configure the GNOME Shell desktop the user only has to right-click the desktop as they have for years. Ubuntu Unity? No dice. In order to configure desktop with Unity, the user must click Applications | System | Appearance. Most new users aren’t even going to know how to get to Systems from within Applications. And if they do figure it out (it’s not difficult), chances are they won’t know that Appearance configuration is tucked into the System category. Shouldn’t there be a Preferences category? Bad call on Unity’s part.

And while we’re at it…both desktops are still using Mutter. I realize that Unity is in major transition from X to Wayland and the rumors have been flip flopping since the announcement as to which compositor it will use. (I just googled it and still find instances where some are saying Mutter and some are saying Compiz.) Regardless of which it uses, just make sure compositing can be customized. That has been one of the best features of Linux desktop – customization!

What? No run dialog? :  That’s right. Ubuntu Unity has forsaken the trusty run dialog. I don’t know about you, but that dialog has been my bread and butter for launching applications for a very long time. Why would a desktop designer think removing that tool is anything but a horrible idea? GNOME Shell? Of course, you can have your run dialog!

What? I can’t change my window manager?:  This is the case for both desktops. You can not change your window manager. Say you prefer Emerald over the standard window manager…if you’re using either GNOME Shell or Ubuntu Unity, you’re out of luck. One of the draws of the Linux desktop has always been its flexibility. If you’re using either GNOME Shell or Ubuntu Unity, kiss that flexibility goodbye.

The largest difference between the two interfaces is that GNOME 3 uses a minimum of two screens: one in which open windows displays, and the overview in which the system is configured and applications chosen and run.

By contrast, Unity remains oriented towards a single screen unless you use virtual workspaces. For light usage, this setup is less confusing and tiresome; in GNOME 3, it can sometimes seems like you are changing screens every few seconds. However, on a netbook in particular, Unity opens many windows full-screen — or near enough to make no difference. If you work with more than a couple of windows open at the same time, the effect is not much different than working in GNOME 3.

GNOME 3 and Unity also eliminate the traditional drop-down menu. Considering that almost all monitors these days are wide-screen, with more horizontal than vertical space, this decision seems logical, especially for interfaces that might be used on netbooks. Instead, both add a panel on the left side of the screen, often referred to as the dashboard in GNOME 3, and as the launcher in Unity. But, whatever the name, this new feature displays basic and running applications.

Of the two, Unity’s launcher is the most flexible. Since GNOME 3’s dashboard displays on a separate screen – no applications run on this screen – it does not need to auto-hide when a window needs its space, and in its current incarnation it is mostly uncustomizable. GNOME 3’s dashboard also has the problem of shrinking to near illegibility if you open too many apps, forcing you to fall back on the mouseover help to identify the icons.

In contrast, you can customize some of the icons on Unity’s launcher. The launcher also accommodates large numbers of open windows by showing a collapsed view at the bottom that opens quickly when you need to scan them. Unity’s launcher also replaces a task indicator with small arrows to mark open applications. Although these arrows are easy to miss at first, they are an elegantly economical use of space once you are aware of them.

However, Unity’s icon for virtual workspaces is perhaps too easy to overlook or work with. GNOME 3’s panel for multiple workspaces on the right of the overview is much more efficient, at least until you open more than four or five workspaces at the same time.

At right angles to GNOME 3’s dashboard is another menu across the top with items for open windows and applications, with sub-items that appear as large icons on the desktop and can be filtered by a variety of views or by a search window — both of which are easy to miss on the far right of the desktop.

Unity, on the other hand, opens its application menu from its launcher (and, rather confusingly, refers to the resulting view as the dash). Unity’s dash is filterable by categories, and includes a search field that is much easier to find than GNOME 3’s.

However, Unity’s sub-menus do have the annoying habit of displaying only a single line of items plus a link announcing how many items are not displayed — even if there is only one. While shrinking icons to fit the space is obviously not a solution if dozens of other items exist, I can’t help wondering whether an exception couldn’t be made when only a few other items are available.

For that matter, you might question whether the change from drop-down menus is worth the effort by the developers or the trouble that users must take to familiarize themselves with it. In the efforts to avoid the menus overlaying too much of the screen, both GNOME 3 and Unity have created alternatives that cover the screen far more thoroughly than any drop-down menu. The result is easier to read for the visually challenged, but otherwise might be said to exchange one set of problems for its exact equivalent.

The same might also be said for the handling of windows, especially in GNOME 3. By default, neither interface allows resizing of windows beyond switching between their default size and maximizing them. Moreover, both use hot spots on the edges of their desktops to minimize or maximize, or tile windows. But GNOME 3 takes the extra step of eliminating title bar buttons to minimize or maximize buttons, forcing users to rely on the hot spots. Like the change in the menus, these changes seem to enforce an orthodoxy and limit user choice for no clear benefit.

What’s better?

I tried installing Gnome 3 on Meerkat but got some errors, however I just got a glimpse for a few moments and Gnome 3 is simply beautiful! Both are getting some flax from loyalists and the Linux community is distraught on Ubuntu’s decision. The war is almost on: GNOME Shell vs. Ubuntu Unity. Both have been available long enough to draw the conclusion as to which will rise above and find success. Time will tell who wins.

Ubuntu Unity simply does not perform or behave up to the standards users have grown to expect from a Linux desktop. My fear is this will actually do more to harm than to help the Linux desktop cause. When new users install Ubuntu 11.04 they will be greeted with a desktop designed for netbooks and will feel cheated.

As for GNOME Shell…that’s a tougher one. It’s certainly not a step back because it functions so well and offers a lot of really nice “evolutions” to the current state of the desktop. My biggest gripe with GNOME Shell is its lack of flexibility. But GNOME Shell certainly does have a lot more polish and looks worlds more professional (where Unity seems to be convinced looking like a toy is a better take on the desktop.)

Given the choice between the two, I would choose GNOME Shell any day. What about you? What is your take on the GNOME Shell vs. Ubuntu Unity battle?

Posted by: richlyn | April 25, 2011

Ubuntu 11.04 Installation Screenshots

Have come across this post of screen shots of Natty’s screenshots. Ubuntu 11.04 releases April 29th. Ubuntu 11.04 Natty installation screenshots Gallery

Posted by: richlyn | February 13, 2011

Ubuntu 11.04 – Que sera sera

Recent news for “Natty Narwhal” Ubuntu’s 11.04 Version says that there will not be any RC (which according to original time-line fell on 21st April) as it would be a bit late. A release candidate is a development version which should be, unless flaws are found, ready for distribution as the final version. they have decided to add a Beta 2 release on 14 April, immediately after freezing the kernel. The release date of 28 April for Natty Narwhal is unchanged. The day after the release is a bank holiday (public holiday) in the UK, not in celebration of the release of Ubuntu 11.04, but because there is a royal wedding taking place.

I was a bit disappointed though for i will miss my favorite applications in Natty. Ubuntu has replaced F-Spot with Shotwell as the default photo manager, Rhythmbox(I am attached to it) with Banshee as the default audio player, Compiz with Mutter as the default window manager, and OpenOffice.org 3.2 with LibreOffice 3.3(sad) and ofcourse includes Unity, developed in-house by the Ubuntu developers, as the distribution’s default desktop, replacing the GNOME Shell. Ubuntu sound menu is as significant as any other change. It simplifies the top panel in a big way and it has even started to look good. There is a distinct glow for the buttons now when you hover the mouse pointer over it. Small changes like these could completely reinvent the Ubuntu experience. The default sidebar dock has also changed by a lot. Ubuntu Software Center now comes up with the “recommendations” option.

So many new applications has made me avoid 11.04 so far and i will wit for the release and test the see if it looks great, only then i will decide by May first week, if i need to have the Natty.

Posted by: richlyn | January 2, 2011

2010 in review

The stats helper monkeys at WordPress.com mulled over how this blog did in 2010, and here’s a high level summary of its overall blog health:

Healthy blog!

The Blog-Health-o-Meter™ reads This blog is doing awesome!.

Crunchy numbers

Featured image

A helper monkey made this abstract painting, inspired by your stats.

A Boeing 747-400 passenger jet can hold 416 passengers. This blog was viewed about 6,400 times in 2010. That’s about 15 full 747s.

 

In 2010, there were 11 new posts, growing the total archive of this blog to 32 posts. There were 28 pictures uploaded, taking up a total of 3mb. That’s about 2 pictures per month.

The busiest day of the year was May 3rd with 55 views. The most popular post that day was Separate Boot Partition Vs Dedicated Boot partition.

Where did they come from?

The top referring sites in 2010 were ubuntuforums.org, google.com, symbianize.com, google.co.in, and linuxquestions.org.

Some visitors came searching, mostly for dedicated grub partition, ubuntu lucid bootup, lucid lynx, grub2 partition, and separate grub partition.

Attractions in 2010

These are the posts and pages that got the most views in 2010.

1

Separate Boot Partition Vs Dedicated Boot partition April 2010

2

Burg April 2010
1 comment

3

Removing Old Kernels March 2010

4

Making a dedicated Grub partition July 2009
3 comments

5

Dedicated Burg Partition April 2010

Posted by: richlyn | December 25, 2010

Battery Life

Let’s start with the most basic fact of mobile devices – most have batteries made with Lithium technology (LI-ON mostly). These have a typical life of 2-3 years because then have a limited number of charge/discharge cycles. Keeping your mobile battery in good shape will make it last longer. Hence,

  1. Don’t keep the mobile device plugged into mains all the time; letting the battery discharge is important for it’s longevity. If you must do leave it in all the time, consider removing the battery (at the risk of losing your work on power failure).
  2. Don’t expose the battery to high temperatures. The cooler your working environment (including your laptop chassis), the longer your battery will keep its charge.

Ubuntu has been working ( Brainstorm ) on power management applications to prolong the battery life. Every second person now uses a laptop or notebook and each of us want to extend the battery life to the fullest hence the importance of this idea has garnered support by many. Hoping to something of this genre in the next release.

Posted by: richlyn | June 27, 2010

Change Lucid Bootup and Login Screen

Ubuntu Lucid Lynx has switched from usplash to a Plymouth for display screen while the boot up completes. There is a general discontent with the purple color of the screen and the progress bars. A little delving in to Plymouth revealed it source to be the Ubuntu-logo script. So here is how a little tweak will change the boot up screen color to your choice.

Changing the Ubuntu logo:

edit the ubuntu-logo image in  /lib/plymouth/themes/

Changing the background color of the boot up screen:

  • sudo gedit ubuntu-logo.script

Find these lines:

Window.SetBackgroundTopColor (0.16, 0.00, 0.12); # Nice colour on top of the screen fading to
Window.SetBackgroundBottomColor (0.16, 0.00, 0.12); # an equally nice colour on the bottom

change the color value to one of your choice, 0.0.0 will give you a black background. i found this color calculator helpful.

Window.SetBackgroundTopColor (0.00, 0.00, 0.00); # Nice colour on top of the screen fading to
Window.SetBackgroundBottomColor (0.00, 0.00, 0.00); # an equally nice colour on the bottom

  • uname -r
  • sudo update-initramfs -c -k ‘uname -r’

Changing the login screen:

Move your wallpaper (jpg format only) to the system wallpaper directory

sudo mv /wallpaper.jpg /usr/share/backgrounds

Activate the appearance window on loginlucid-login-appearance

sudo cp /usr/share/applications/gnome-appearance-properties.desktop /usr/share/gdm/autostart/LoginWindow

Close the terminal and logout.

Login again and an appearance window will show up, choose your choice of wallpaper as the background.

click on Add if you are unable to find your wallpaper. This will change your login screen.

After you login deactivate the appearance window on login

sudo unlink /usr/share/gdm/autostart/LoginWindow/gnome-appearance-properties.desktop

you can change the Ubuntu logo by editing image in:

  /lib/plymouth/themes/ubuntu-logo

Posted by: richlyn | June 6, 2010

Home folder on a separate partition

When I  installed Lucid Lynx i did not set up the home folder to on a  separate  partition and  was facing a space crunch hence I moved the Home folder to a separate partition on a different hard disk. My Lucid was on sda10 and the dedicated partition was sdb2.

I booted with a live cd and mounted the old(sda10) and new (sdb2)partitions:

sudo mkdir /old
sudo mount -t ext3
/dev/sda10 /old
sudo mkdir /new
sudo mount -t ext3
/dev/sdb2 /new

Back up the /home directory on the old partition and move it to the new partition:

cd /old/home
sudo find . -depth -print0 | cpio –R id –null –sparse -pvd /new/
sudo mv /old/home /old/home_backup
sudo mkdir /old/home

Next, I specified to use the new home partition as /home:

sudo cp /old/etc/fstab /old/etc/fstab_backup
gksudo gedit /old/etc/fstab

The /etc/fstab file opened in the Gedit text editor. Add in this line at the end of the file:

/dev/sdb2 /home ext3 nodev,nosuid 0 2

Save the file and exit Gedit. After you reboot, you should be now using your new /home partition.

If you find that you are running out of room on your old partition and you’re pretty confident everything is working as it should be, then go ahead and delete the backup of home:

sudo rm -rf /home_backup

If you reboot and are getting  some errors having to do with the $HOME/.dmrc file and/or .ICEauthority file, boot into recovery mode. Once in recovery mode, type:

chown -R username:username /home/username
chmod 644 /home/
username/.dmrc
chmod 644 /home/
username/.ICEauthority
exit

where username is your actual username. Obviously, you’d repeat the first three commands for all users experiencing the problem before you typed exit.

if you get any errors for the first command above do this:

sudo chown username /home/username/.dmrc
sudo chmod 644 /home/username/.dmrc
sudo chmod 755 /home/username
sudo chown username:username /home/username/.ICEauthority

Once you’ve exited recovery mode, resume the normal boot and log in.

If, for some reason, no matter what you try, the separate /home doesn’t work, that’s why we have a live CD, so we can fix things.

Boot up the live CD, go to a terminal, and paste in (being sure to change the partition device name, of course):

sudo mkdir /recovery
sudo mount -t ext3
/dev/sda1 /recovery
sudo cp -R /recovery/home_backup /recovery/home
sudo cp /recovery/etc/fstab_backup /recovery/etc/fstab

Then, reboot.

« Newer Posts - Older Posts »

Categories