Thinkpad X230 & Ubuntu 12.10

Trackpad:

• No easy tool to control touchpad.

Using xinput

jony@Icarus:~/bin$ xinput
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ TPPS/2 IBM TrackPoint id=13 [slave pointer (2)]
⎜ ↳ SynPS/2 Synaptics TouchPad id=11 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Video Bus id=7 [slave keyboard (3)]
↳ Sleep Button id=8 [slave keyboard (3)]
↳ Integrated Camera id=9 [slave keyboard (3)]
↳ AT Translated Set 2 keyboard id=10 [slave keyboard (3)]
↳ ThinkPad Extra Buttons id=12 [slave keyboard (3)]

To switch off trackpad : xinput set-prop 11 “Device Enabled” 0

To switch on trackpad : xinput set-prop 11 “Device Enabled” 1

• How to control the sensitivity of trackpoint?

Audio Issues:

• Internal speakers doesn’t work. Fixed with the new kernel (3.5.0-18-generic) update.
• Mute button light is inconsistent. Sometime it comes up sometimes it doesn’t

Laptop Mode

• Install laptop mode - http://blog.agdunn.net/?p=62

Sublime Text syntax definition for Google Protocol Buffers

Sublime Text  Syntax definition for Google Protocol Buffers.

Not robust – But its a start.

{ “name”: “ProtoBuf”,
“scopeName”: “source.proto”,
“fileTypes”: ["proto"],
“foldingStartMarker”: “{“,
“foldingStopMarker”: “}”,
“patterns”: [
{ "match": "\\s+[0-9]*”,
“name”: “constant.numeric.proto”,
“comment”: “Field numbers”
},
{ “match”: “double|float|int32|int64|uint32|uint64|sint32|sint64|long|fixed32|fixed64|sfixed|sfixed64|bool|string|bytes”,
“name”: “storage.type.source.proto”,
“comment”: “Scalar Value types.”
},
{ “match”: “optional|required|repeated|default”,
“name”: “storage.modifier.source.proto”,
“comment”: “Field Rules”
},
{ “match”: “^message|^package|^option|^import|^extend|^service”,
“name”: “entity.name.function.proto”,
“comment”: “Message section”
},
{ “match”: “\/\/.*”,
“name”: “comment.line.double-slash.proto”,
“comment”: “Comments”
}
],
“uuid”: “f6a112ba-072a-47b3-b3e3-7714156b3614″
}

Update : Moved to emacs. But still still two-timing …

Update : Moved to emacs.

End of a book : Johnny in Novell

Last day in Novell.

Started out as an intern in the GNOME team about 5 years back. Jumped between Evolution and iFolder a few times for different (voluntary/involuntary) reasons. Met a lot of good engineers. Had both good / bad times. Learned a lot work / non-work.

Gnomers,

I loved working on Evolution, Evolution MAPI (may not be perfect, but had a awesome time with it And i’m yet to cash in on the few beers i’ve been offered), Attachment Reminder (Trivial, but looks like you guys liked/hated/loved it), Redesign of Evolution search bar and so on. Best bug that I’ve worked on so far was changing a ’1′ to ‘-1′ in EText (Oh those early days! Had no clue what GDB can do.. Used hundreds of ‘printf’s, lots of coffee and tested the patience of office night guards and that adrenalin rush!). Thanks to Novell for the opportunity to contribute full-time and getting paid for that.

Special thanks to my mentor Srini. I’m looking forward for more new awesome fun things in GNOME.

Thanks.

I’ll miss the 1-1 coffee breaks talking games/gadgets/music, discussions on research papers that I don’t have a clue about, conversations during ‘tea breaks’ outside office (you would see me very inspired/productive after those sessions), thursday nights & nice friends that I found beyond ‘work’.

The End.

Push Email for GNOME Evolution’s Exchange MAPI provider (exchange 2007)

 

After few days of crazy bug hunting (and creating the same) , we have a nice push event notification framework for Evolution-MAPI. When Evolution is running all the changes happening in user’s mailbox in server would immediately be synced. This avoids those long fetches from server.  A short screen cast (watch in HD) :

Currently I’ve got “new mail” event handled and is limited to mailer. Would be working on other events. This feature has some major issues to be solved before it can land in master.

It is FUN !

 

Me.

GDB Scripting : A short article for a internal magazine

I wrote a small article for a internal magazine and few of my friends wanted me to post it to this blog.

This is for people who are new to GDB and still exploring itz features. So if you’ve used GDB for more than few weeks please ignore and skip

GDB – Scripting

A good majority of novice programmers tend to use printf functions to trace function calls and to printout the debug data. This forces you to change the code and compile again and again. To eliminate these superfluous tasks from your day-to-day work, use GDB. The GDB has facilities for scripting and helps in saving plenty of your time.

Tracing Function Calls

If you want to know whether a function is called or not, create a break point and write a simple script.

<code>

#Set the breakpoint

(gdb) b mapi_sync

Breakpoint 1 at 0x7fffd75f36e2: file camel-mapi-folder.c, line 741

#Tell GDB what to do when the breakpoint is reached

(gdb) commands

Type commands for when breakpoint 1 is hit, one per line.

End with a line saying just “end”.

> continue

> end

(gdb)

</code>

continue – Come out of break and continue

end – terminate command list

Run the program now. The GDB prints the function name when the breakpoint is hit and automatically continues running the program.

Breakpoint 1, mapi_sync (folder=0xc9c1a0, expunge=0, ex=0xf3a0c0) at camel-mapi-folder.c:741

741             CamelMapiStore *mapi_store = CAMEL_MAPI_STORE (folder->parent_store);

Using the GDB Scripts for Analyzing the Data

Suppose that you have a singly-linked list that has strings in it. At some point, you might want to know the contents of the list. To do this, use the GDB scripting instead of adding the debug statements in your code.

<code>

#Example for gslist traversal.

define p_gslist_str

set $list = ($arg0)

while ((GSList *)$list->next != 0)

p (char *)(GSList *)$list->data

set $list = (GSList *)$list->next

end

end

document p_gslist_str

p_gslist_str <list>: Dumps the strings in a GSList

end

</code>

Add the above snippet into a file and load it into the GDB as follows:

<code>

(gdb) source /home/jjohnny/scripts/gdb/gslist.gdb

</code>

Now, anywhere you want to take a look in the GSList, simply break and

<code>

(gdb) p_gslist_str server_uid_list

$17 = 0x7fffd81101b0 “7666BC1E000000015870BD1E00000001″

$18 = 0x7fffd810e330 “7666BC1E000000015970BD1E00000001″

$19 = 0x7fffd810cbe0 “7666BC1E000000015C70BD1E00000001″

</code>

Simple scripts thus can save you a lot of time from adding or removing the debugging statements from your code. Now go ahead and create a suite of scripts to aid the library you are writing.

More cool developer tricks later. Have fun !

— End —

Thanks to Radhika for editing the article.

Btw when is Archer branch  (Python scripting) getting into GDB ? I’ve been using it a bit .

GDB

- Scripting

A good majority of novice programmers tend to use printf functions to trace function calls and to printout the debug data. This forces you to change the code and compile again and again. To eliminate these superfluous tasks from your day-to-day work, use GDB, the GNU Project Debugger. The GDB has facilities for scripting and helps in saving plenty of your time.

Tracing Function Calls

If you want to know whether a function is called or not, create a break point and write a simple script.

<code>

#Set the breakpoint

(gdb) b mapi_sync

Breakpoint 1 at 0x7fffd75f36e2: file camel-mapi-folder.c, line 741

#Tell GDB what to do when the breakpoint is reached

(gdb) commands

Type commands for when breakpoint 1 is hit, one per line.

End with a line saying just “end”.

> continue

> end

(gdb)

</code>

continue – Come out of break and continue

end – terminate command list

Run the program now. The GDB prints the function name when the breakpoint is hit and automatically continues running the program.

Breakpoint 1, mapi_sync (folder=0xc9c1a0, expunge=0, ex=0xf3a0c0) at camel-mapi-folder.c:741

741             CamelMapiStore *mapi_store = CAMEL_MAPI_STORE (folder->parent_store);

Using the GDB Scripts for Analyzing the Data

Suppose that you have a singly-linked list that has strings in it. At some point, you might want to know the contents of the list. To do this, use the GDB scripting instead of adding the debug statements in your code to print out the data.

</code>

#Example for gslist traversal.

define p_gslist_str

set $list = ($arg0)

while ((GSList *)$list->next != 0)

p (char *)(GSList *)$list->data

set $list = (GSList *)$list->next

end

end

document p_gslist_str

p_gslist_str <list>: Dumps the strings in a GSList

end

</code>

Add the above snippet into a file and load it into the GDB as follows:

<code>

(gdb) source /home/jjohnny/scripts/gdb/gslist.gdb

</code>

Now, anywhere you want to take a look in the GSList, simply break

<code>

(gdb) p_gslist_str server_uid_list

$17 = 0x7fffd81101b0 “7666BC1E000000015870BD1E00000001″

$18 = 0x7fffd810e330 “7666BC1E000000015970BD1E00000001″

$19 = 0x7fffd810cbe0 “7666BC1E000000015C70BD1E00000001″

</code>

Simple scripts thus can save you a lot of time from adding or removing the debugging statements from your code.

Now go ahead and create a suite of scripts to aid the library you are writing.

More cool developer tricks later. Have fun !

openSUSE 11.1 on PS3

Woohoo ! After a long delays and issues (in the last few days) I’ve managed to install openSUSE 11.1 in my PS3.  Running a full blown desktop is very sluggish. Reminds me of my first computer (amdk6 500mhz). Some screenies :

Now onto get the Cell SDK running … Synergetic Processing Elements (SPE) here i come !

Makespace – Plugin for GNOME Evolution

I’ve written (incomplete) simple plugin for Evolution which provides a combo box + menu for switching folders. Now you can hide the sidebar. This really helps in freeing up some space in your screen and can have good vertical view layout. This would help computers with smaller screen size.

Screenshots :

Sidebar hidden. Small combo box in top left corner

Switching folders

To try out this plugin / For more information :   http://www.johnnyjacob.org/makespace.html .

One other feature that I would like to have is simple folder bookmarks. Bookmarked folders would appear in the top of the menu (You don’t have to navigate all the way down in the menus)

Let me know what you think and if you would like to have any features put it down in the comments.

Evolution MAPI update release. (0.26.0.1)

Hello,  I just released a update to evolution-mapi. 0.26.0.1 has fix for Bug 574784 without which the package is totally unusable.

Thanks !

1 reason to run GDB & 2 reasons to run emacs from source

CODE :

GDB : Compiling from Project Archer, you get to have python scripting inside gdb. This opens up numerous possibilities and nice tricks that helps you to debug  faster. http://tromey.com/blog/?cat=17 has few example + demo scripts.  Falling in love  with these ..

EMACS : emacs 23 (in cvs) gives you MultiTTY Support , XFT Font rendering (and more). Looks better with XFT and multitty support rocks !

LIFE :

??

Evolution MAPI : Debut tarball release & RPM Repos are online

We have started the tarball releases for evolution-mapi. It’ll be in sync with GNOME release schedule. evolution-mapi-0.25.3 is available for download [0].

Thanks to Suman [1], openSUSE repositories [2] are back online.

Matthew has repositories for Fedora [3] [4]

—-
[0] http://ftp.gnome.org/pub/GNOME/sources/evolution-mapi/0.25/

[1] http://mail.gnome.org/archives/evolution-list/2008-December/msg00097.html

[2] http://download.opensuse.org/repositories/GNOME://Evolution://mapi/

[3] http://mbarnes.fedorapeople.org/mapi/

[4] http://mail.gnome.org/archives/evolution-list/2008-December/msg00086.html

Evolution MAPI : Contributions… Testing… Bugzilla …

Development is more active after our move to new svn ! Julien (of openchange.org) has patched evolution-mapi to be compatible with libmapi 0.8 .Patches are welcome !

Some of the cool things with libmapi 0.8 is the possibility of having multiple exchange accounts (multiple sessions) in Evolution (Yep. you read that right! ). But they will hit the trunk little later .

Now more focus is on real world testing on servers other than few test servers we are running. What doesn’t work in different setups is something we would like to know and fix them all ! Thanks to those who have been reporting issues and TIA

NEWS :

+ evolution-mapi is proposed for GNOME 2.26. Yay !

+ we have a new product ‘evolution-mapi’ in GNOME bugzilla.

+ Wiki page is updated with information on building evolution-mapi .