Skip to content

Monthly Archives: November 2009

Twitter Weekly Updates for 2009-11-30

seamstress = šuvju stresotāja # Interesanti: cik ES mums samaksātu CO2 subsīdijās, lai visus vilcienus pārvestu uz elektro (arī kravas)? # Šodien @ltvpanorama rubrikā 'Šeit ir darbs' būs mana jaunā darba vieta – Accenture. Silti iesaku visiem IT cilvekiem paskatīties. # http://gauja.lv/html/index.php?id=26882 – kāds ir jau izmēģinājis Capital Gauja A1R? Izskatās smuki, un arī bez [...]

Twitter Weekly Updates for 2009-11-23

Esam @TurKebab – viņi ir iegājuši super ātrā ritmā: viss gatavs bija minūtes laikā. Saimniece pie kasses. Stilā # The flu is in da house # Yay! Man arī beidzot piešķīra Retweet funkciju twitterī un, kas ir vēl svarīgāk, retweet indikāciju tā itkā tweets nāk no sākotnējā avota # Četratā skatāmies 'Lie to me' – [...]

Twitter Weekly Updates for 2009-11-16

Ubuntu 9.10 fail – there is no usb-creator.exe on the CD images (or anywhere on the web) despite the docs saying that it is the only way. # Labrīt tauta ! See you at the annual LATA conference – http://lata.org.lv # Zalāns: "pat mēs nezinam cik uz IT tiek tērēts. IT izmaksas ir noslēptas dziļi [...]

Twitter Weekly Updates for 2009-11-09

You know what is perverse? Installing Windows 7 in Sun VirtualBox on Ubuntu 9.10 just ot get new music on my iPhone. And it is great! # The best thing is that I can continue working/relaxing with all my Ubuntu apps while iTunes does all the weird things it does for an hour. # http://bit.ly/1HjDsH [...]

Twitter Weekly Updates for 2009-11-02

The more I use htop, the more cool features I find. Never using regular top anymore – htop is AWESOME! # Also planning to go to local Ubuntu 9.10 launch event – http://bit.ly/5NaMN (in latvian) # http://bit.ly/1e2rmc – Football Hero. It's madness! # Lūk ko tādu kā Football Hero TELE2 vajadzēja taisīt – reāli pozitīvu [...]

Gnome typing break has no way to lock the screen

Want a definition of a paper cut bug? Here it is. And here and here are two more side effects of the same bug. The original bug report will be 6 years old in a month. Can we do something to prevent this bug surviving that long?