Jun 20
Free Software Ok, so I used Gnome Shell before it was officially released. I stopped using it because I thought it was intriguing, but awkward to use in its beta stages. Then Gnome 3 was released and gnome-shell was no longer an interesting option, it was the compulsory way to use the operating system; and I wrote at the time about some of the problems. Many were solved, but the underlying troubles in the design of Gnome Shell were a problem for me. And I've really tried to like it, I really have, and I don't. I hate it. It makes almost every workflow I have tedious and exasperating. It has damaged my productivity. It looks pretty, it looks stylish, but it's frankly slow and painful to get things done. I tried lots of other window managers and was frustrated at having the leave the good things of Gnome behind.

Until someone told me about Cinnamon. I looked at the website and thought it might be just the ticket. Unfortunately it's not officially packaged for Debian (yet), and I currently lack the time to start building my own packages. Fortunately someone else has done it. I installed the packages on my laptop and breathed a sigh of relief (once I diagnosed a problem with the settings dialog). I installed it on my other boxes (that have GUIs), and now, well, the best thing is I am enjoying all the great things about Gnome 3 now. I'm even enjoying the great things about Gnome Shell, since Cinnamon is actually a fork, but all the stupid bits are gone.

There is a nice, elegant panel, so much cleaner than the Gnome Fallback mode. It looks like it belongs in Gnome 3, it does. Notifications are more subtle, coming up in out of the way bits of the screen. The screen effects are subtle but pleasant. In short it is what Gnome 3 should have been, or at least optionally. The "new" interface of Gnome Shell may suit many users, many devices, many workflows, but it most certainly does not suit all.

I have my nice comfortable desktop and workflow back after many months; kudos to the Cinnamon team, and kudos for them really showcasing all the excellence of Gnome 3 rather better.

If you want to try it out on Debian, follow the instructions here, and note the possible problem with the settings dialog.

Posted by Colin Turner

Defined tags for this entry: , , ,
Twitter Bookmark Cinnamon; adding needed spice to Gnome 3  at del.icio.us Facebook Google Bookmarks FriendFeed Digg Cinnamon; adding needed spice to Gnome 3 Mixx Cinnamon; adding needed spice to Gnome 3 Bloglines Cinnamon; adding needed spice to Gnome 3 Technorati Cinnamon; adding needed spice to Gnome 3 Fark this: Cinnamon; adding needed spice to Gnome 3 Bookmark Cinnamon; adding needed spice to Gnome 3  at YahooMyWeb Bookmark Cinnamon; adding needed spice to Gnome 3  at Furl.net Bookmark Cinnamon; adding needed spice to Gnome 3  at reddit.com Bookmark Cinnamon; adding needed spice to Gnome 3  at blinklist.com Bookmark Cinnamon; adding needed spice to Gnome 3  at Spurl.net Bookmark Cinnamon; adding needed spice to Gnome 3  at NewsVine Bookmark Cinnamon; adding needed spice to Gnome 3  at Simpy.com Bookmark Cinnamon; adding needed spice to Gnome 3  at blogmarks Bookmark Cinnamon; adding needed spice to Gnome 3  with wists wong it! Bookmark using any bookmark manager! Stumble It! Print this article! E-mail this story to a friend! Identi.ca
Oct 30
Free Software I use the Debian operating system on several computers. My "main" computer (Imladris) runs Debian unstable (Sid) while the others mostly run on testing. I've been anticipating the Gnome 3 upgrade for some time, mainly because of the switch to Gnome Shell which is a completely new way of using the desktop. I had played with Gnome Shell a while ago, and was kind of impressed and worried by it in equal measure, I decided it wasn't ready for prime time so stopped using it. Naturally I assumed it would be much more impressive upon release; especially since Debian is not (by far) the first GNU/Linux distribution to include Shell.

A while ago a big upgrade came through on imladris, and it was clear it was the Gnome 3 upgrade. I share this computer with three other users, two of which are children for whom I have implemented password less login (locally only). I can only say I think Gnome have significantly mishandled the upgrade. Here are some reasons why.

Login is seriously slow

The display manager can take up to a whole minute to display the list of users (and often doesn't display the icons). There are some bug reports about a possible race condition that causes this, but seriously on a reasonable spec computer this is unacceptably slow. The same problems occurs when switching user.

I couldn't login

My, admittedly old user account simply wouldn't launch a working desktop. I had to (at a command prompt) delete configuration directories to get my account working again.

Absolutely zero support for the user in transition

So the average user does the upgrade and suddenly their entire desktop has changed. But when they first login there will be some guidance about where everything is gone... right? No. Having already used Shell, I knew, but I had to try and show everyone else how to use the machine again. It's not that spectacularly intuitive.

Actually, a lot of functions have just gone

There's a huge removal of existing functionality. All your carefully tweaked panels: gone. All your applets: gone. And bizarrely often with no working alternative.

Not friendly for children

It was possible to set up a Gnome 2 account to make it easy for kids. Low res graphics, and big panels with big select icons. The new paradigm completely ignores all that in favour of a sleek minimalist environment which is probably not that easy for young children to understand.

Dictatorial design choices

It's been decided that we don't need minimise buttons or maximise buttons. It's been decided not to honour old desktop backgrounds. It's been decided not to honour existing resolution settings. It's been decided not to show anything on the Desktop (much to the confusion of many users). It's been decided we can't right click on the desktop.

Some of this kind of nonsense is exactly why I don't like some other operating systems who believe they know what's best for you with Messianic Zeal (I'm looking at you Apple).

All in all I find this transition very disappointing. There are lots of basic things no-one seems to have thought of, and years of desktop customisation have been swept away with an extraordinary arrogance. Don't get me wrong, I support the idea of trying a new Desktop paradigm: but, for instance, if people used to have applets on their desktop for the weather, or for system monitoring, it's because they needed it. Rolling out a new desktop that simply ignores these things in favour of how some people thing everyone should use their desktop is exasperating.

I'm seriously hoping that Gnome Shell improves significantly and fast. I won't hold my breath.

Posted by Colin Turner

Defined tags for this entry: , , ,
Twitter Bookmark Gnome 3, or Gnome Shell issues  at del.icio.us Facebook Google Bookmarks FriendFeed Digg Gnome 3, or Gnome Shell issues Mixx Gnome 3, or Gnome Shell issues Bloglines Gnome 3, or Gnome Shell issues Technorati Gnome 3, or Gnome Shell issues Fark this: Gnome 3, or Gnome Shell issues Bookmark Gnome 3, or Gnome Shell issues  at YahooMyWeb Bookmark Gnome 3, or Gnome Shell issues  at Furl.net Bookmark Gnome 3, or Gnome Shell issues  at reddit.com Bookmark Gnome 3, or Gnome Shell issues  at blinklist.com Bookmark Gnome 3, or Gnome Shell issues  at Spurl.net Bookmark Gnome 3, or Gnome Shell issues  at NewsVine Bookmark Gnome 3, or Gnome Shell issues  at Simpy.com Bookmark Gnome 3, or Gnome Shell issues  at blogmarks Bookmark Gnome 3, or Gnome Shell issues  with wists wong it! Bookmark using any bookmark manager! Stumble It! Print this article! E-mail this story to a friend! Identi.ca
Aug 4
Free Software For some years now, basically since Aimee became old enough to use a computer, I have had a need for decent multi-user sound. Specifically I would often have intricate work open in multiple work spaces on my desktop, and Aimee would want to do some artwork.

I guess Aimee was about two when she started using my computer a fair bit, and I immediately had a separate account for her with lower resolution graphics, easier menus, simple shortcuts and the like. I also had a graphics tablet for her, which she mastered very quickly. Another important reason to have a separate account was that if stuff got really badly messed up I could just nuke the account and start again, and she couldn't really hurt my configuration.

As you would imagine, lots of the excellent free software for children, like GCompris, and Tuxpaint is very rich in its sound effects, and sometimes the sound is not just desirable, but essential for the activities. So a very annoying persistent problem has been that, once in a while, something in the sound stack in my login would stop Aimee's sound from working.

Now I share my main PC with two other people, Tamsin and Aimee, and soon Matilda too, so this recurrent problem is more of an issue, it's also very hard to nail down. Despite protests to the contrary the default ALSA setup still has this problem; ConsoleKit on its own doesn't seem to get it quite right. I tried PulseAudio for a while, and generally it was an improvement, but the problem did still occur sometimes. I even made sure all the users were members of the right groups including pulse-rt.

Then I found this entry in the PulseAudio FAQ.

Sound doesn't work when switching users

PulseAudio works with a single user, but when an additional user logs in (fast user switching), sound/audio does not work for the additional user.

Check that no users are part of the "audio" group.

In simple setups (e.g. singe user, without PulseAudio), users must be a member of the "audio" group to access the sound devices (/dev/snd/* (which have group "audio" write permissions)). Switching users will not automatically stop programs using those sound devices though, so those sound devices will not be accessible to a new (faster user switched) user's programs.

By removing all users from the "audio" group (the PulseAudio server still runs in the "audio" group), PulseAudio is able manage access to sound devices (/dev/snd/*) amongst multiple users with the help of ConsoleKit.



It would never have occurred to me to remove the users from the audio group, but doing so seems to have solved the problem. I almost don't want to say that, because every "solution" up to now has been partial, but so far no problems, so maybe this will be the fix.

Posted by Colin Turner

Defined tags for this entry: ,
Twitter Bookmark Multi User Sound in GNU/Linux  at del.icio.us Facebook Google Bookmarks FriendFeed Digg Multi User Sound in GNU/Linux Mixx Multi User Sound in GNU/Linux Bloglines Multi User Sound in GNU/Linux Technorati Multi User Sound in GNU/Linux Fark this: Multi User Sound in GNU/Linux Bookmark Multi User Sound in GNU/Linux  at YahooMyWeb Bookmark Multi User Sound in GNU/Linux  at Furl.net Bookmark Multi User Sound in GNU/Linux  at reddit.com Bookmark Multi User Sound in GNU/Linux  at blinklist.com Bookmark Multi User Sound in GNU/Linux  at Spurl.net Bookmark Multi User Sound in GNU/Linux  at NewsVine Bookmark Multi User Sound in GNU/Linux  at Simpy.com Bookmark Multi User Sound in GNU/Linux  at blogmarks Bookmark Multi User Sound in GNU/Linux  with wists wong it! Bookmark using any bookmark manager! Stumble It! Print this article! E-mail this story to a friend! Identi.ca
Jan 17
Free Software I've had a Logitech QuickCam Pro 9000 for some time now, and it works well, but I did have one bizarre problem with it when I used it with my main desktop machine (running Debian (Sid)). Namely, that if I had the camera plugged in (usb) at boot time the sound on the computer did not work, if you plugged it in after boot, everything was fine.

This was pretty irritating because if I forgot I would often have dozens of windows open and ready for work before I realised.

Normally this happens because the cards are loaded in the wrong sequence by udev. But, if you listed the sound cards with

cat /proc/asound/cards
 
the main card wasn't just in the wrong order, it simply wasn't there. I tried comparing modules loaded with and without the camera (at boot) and manually loading the differences, but this did not help. I tried forcing the index to be zero on the correct card, but this also did not help.

In the end, I made the following edit to /etc/modprobe.d/alsa-base.conf

# Keep USB (webcam from being loaded as first card)
options snd_usb_audio index=-2
 
and this did the trick. So if like me you were searching for the answer to this, I hope it helps.

Posted by Colin Turner

Defined tags for this entry: ,
Twitter Bookmark Boot time sound problems with QuickCam Pro 9000 webcam  at del.icio.us Facebook Google Bookmarks FriendFeed Digg Boot time sound problems with QuickCam Pro 9000 webcam Mixx Boot time sound problems with QuickCam Pro 9000 webcam Bloglines Boot time sound problems with QuickCam Pro 9000 webcam Technorati Boot time sound problems with QuickCam Pro 9000 webcam Fark this: Boot time sound problems with QuickCam Pro 9000 webcam Bookmark Boot time sound problems with QuickCam Pro 9000 webcam  at YahooMyWeb Bookmark Boot time sound problems with QuickCam Pro 9000 webcam  at Furl.net Bookmark Boot time sound problems with QuickCam Pro 9000 webcam  at reddit.com Bookmark Boot time sound problems with QuickCam Pro 9000 webcam  at blinklist.com Bookmark Boot time sound problems with QuickCam Pro 9000 webcam  at Spurl.net Bookmark Boot time sound problems with QuickCam Pro 9000 webcam  at NewsVine Bookmark Boot time sound problems with QuickCam Pro 9000 webcam  at Simpy.com Bookmark Boot time sound problems with QuickCam Pro 9000 webcam  at blogmarks Bookmark Boot time sound problems with QuickCam Pro 9000 webcam  with wists wong it! Bookmark using any bookmark manager! Stumble It! Print this article! E-mail this story to a friend! Identi.ca
Dec 31
Free Software I use client side virtual folders a bit for my mail. Specifically, I tag messages with IMAP flags like todo and important, and then in Icedove / Thunderbird, I set up a special folder as a saved search which shows message that are either unseen, or marked todo in my inbox. It works rather well, and I use the same set-up on my laptop, and work and home desktop machines.

But it's not very useful on my phone, which doesn't allow such sophisticated client side behaviour. My phone mail applications shows the most recent 25 messages in a folder, but there are times when it would be really useful to look up messages that are labeled as important but rather old. It would be time consuming to look through the older messages, and difficult to find the one I want anyway.

As a result, I've been looking at the possibility of using virtual server side folders using dovecot on my Debian mail server. I was put off by the documentation which left a lot of questions unanswered.

Here's how I did it on Debian. First of all edit the config file /etc/dovecot/dovecot.conf, back up this file first, so you can restore working behaviour if something goes wrong.

#
# You have to add the default namespace
# which is normally NOT added explicitly before
#
namespace private {
  prefix =
  separator = /
  # the next line is very specific to where you keep your mail
  location = mbox:~/Mail/:INBOX=/var/mail/%u
  list = yes
  inbox = yes
  subscriptions = yes
  hidden = no
}

#
# Then add the virtual namespace
#
namespace private {
    prefix = virtual/
    separator = /
    # pick where the virtual folders will be
    location = virtual:~/Mail/virtual
    list = yes
    inbox = no
    subscriptions = yes
    hidden = no
}
 


You must also add the virtual folder plugin.

##
## IMAP specific settings
##

protocol imap {

  # ... you need to enable the plugin
  mail_plugins = virtual
 


Now restart dovecot and check your normal folders are working.

/etc/init.d/dovecot restart
 
Note that I found dovecot will generally not serve physical folders correctly if the virtual mail folder (even if empty) does not exist. I consider this a bug, but one that needs to be worked around, at least for me.

If that's all done and working you can begin to create virtual folders. I created two directories within my ~/Mail/virtual folders; which were inbox-todo and inbox-important respectively. Inside each I put the following files.


# ~/Mail/virtual/inbox-todo/dovecot-virtual
INBOX
  OR (OR (OR KEYWORD $TODO KEYWORD todo) KEYWORD $label4) unseen
 
which shows all unseen and mail labelled todo in my inbox and

# ~/Mail/virtual/inbox-important/dovecot-virtual
INBOX
  OR (OR KEYWORD $IMPORTANT KEYWORD important) KEYWORD $label1
 
which shows only important mail in my inbox.

It seems to be working, my normal folders appear to be working perfectly correctly (but I'll know better in a couple more hours/days); my phone has successfully subscribed to the two virtual folders, though the folder list shows a number of files which I'm certain it should not, again, this looks like a dovecot bug to be honest.

Posted by Colin Turner

Defined tags for this entry: , , ,
Twitter Bookmark Virtual folders with Dovecot and Debian  at del.icio.us Facebook Google Bookmarks FriendFeed Digg Virtual folders with Dovecot and Debian Mixx Virtual folders with Dovecot and Debian Bloglines Virtual folders with Dovecot and Debian Technorati Virtual folders with Dovecot and Debian Fark this: Virtual folders with Dovecot and Debian Bookmark Virtual folders with Dovecot and Debian  at YahooMyWeb Bookmark Virtual folders with Dovecot and Debian  at Furl.net Bookmark Virtual folders with Dovecot and Debian  at reddit.com Bookmark Virtual folders with Dovecot and Debian  at blinklist.com Bookmark Virtual folders with Dovecot and Debian  at Spurl.net Bookmark Virtual folders with Dovecot and Debian  at NewsVine Bookmark Virtual folders with Dovecot and Debian  at Simpy.com Bookmark Virtual folders with Dovecot and Debian  at blogmarks Bookmark Virtual folders with Dovecot and Debian  with wists wong it! Bookmark using any bookmark manager! Stumble It! Print this article! E-mail this story to a friend! Identi.ca
Dec 15
Free Software hardware I've had my Google development phone, the g1, for some time now. I haven't had the luxury of time to write anything for it, but I mainly wanted it to try out Android anyway. I've reviewed the phone before, and again after some canonical firmware upgrades.

I use the truly excellent K9 application for mail, it has good support for self signed certificates, now has IMAP push support and is generally excellent. However, it stores all the mail on the shockingly limited internal memory on the device. That, and upgrades to things like Google Maps, adding truly excellent new functionality, left me constantly looking for applications to remove.

This is why in the end I decided to try Cyanogen's ROMs. Since I have a development phone, I didn't need to root it, and just followed the relevant instructions (in truth, I couldn't be bothered to downgrade the OS to root it first).

Here are some observations about the new ROM:

  • Apps2sd is amazing.
    I have the whole pleasure of trying different apps all over again, without sweating about every byte. I don't have to worry about how much data is in my contacts (whether I assign them icons), my emails, and so on. I have plenty of room. I was delighted to be able to install DocumentsToGo. Which makes the phone much more useful for work emails. Loads of great apps I had to remove have been reinstated, and I can play with others, like the awesome Google Googles.
  • Extra workspaces
    There are five workspaces, making for more widget playroom. I now have a calendar app taking up a whole workspace with the events to come. Excellent.
  • It fixes several problems I had with MMS functionality.
    • It fakes a variety of user agents, meaning that a test video message I sent myself on o2 finally worked, for the first time ever.
    • The stock ROM allows you to prevent data access when roaming, which is good. But it also doesn't fetch MMS when roaming, which is (for me) a nuisance, and these are usually on a different tariff system. So when you receive an MMS on roaming, you end up enabling all data access to quickly receive the MMS, and then turn it off again. The Cyanogen ROM has an option to retrieve MMS on roaming.
  • UI feels snappier
  • USB tethering
    can be enabled, which JustWorks (TM) with Debian. Excellent.
On the downside, I have had some reset problems, but admittedly I have sometimes been pushing the phone very hard indeed to test it. And the battery life on the g1 is still awful. I know Noodles has solved the problem by not actually using his phone :-), but I want to use mine.

Another minor problem I encountered some weeks ago was the accelerometer suddenly starting serious misreporting on one axis. This problem seems to be becoming less severe, but even reinstalling the stock and then cyanogen ROM did not fix it. However, note I did not wipe the user data.

Cyanogen has made my phone fun to have again. And I will still replace it when a new Android handset comes out that I really like, but a lot of the urgency has gone. I'll certainly buy him a beer for Christmas.

Posted by Colin Turner

Defined tags for this entry: , , , , , ,
Twitter Bookmark Cyanogen Android ROM on the g1  at del.icio.us Facebook Google Bookmarks FriendFeed Digg Cyanogen Android ROM on the g1 Mixx Cyanogen Android ROM on the g1 Bloglines Cyanogen Android ROM on the g1 Technorati Cyanogen Android ROM on the g1 Fark this: Cyanogen Android ROM on the g1 Bookmark Cyanogen Android ROM on the g1  at YahooMyWeb Bookmark Cyanogen Android ROM on the g1  at Furl.net Bookmark Cyanogen Android ROM on the g1  at reddit.com Bookmark Cyanogen Android ROM on the g1  at blinklist.com Bookmark Cyanogen Android ROM on the g1  at Spurl.net Bookmark Cyanogen Android ROM on the g1  at NewsVine Bookmark Cyanogen Android ROM on the g1  at Simpy.com Bookmark Cyanogen Android ROM on the g1  at blogmarks Bookmark Cyanogen Android ROM on the g1  with wists wong it! Bookmark using any bookmark manager! Stumble It! Print this article! E-mail this story to a friend! Identi.ca
Jun 29
Free Software I note that the controversy of Mono in Debian which reached fever pitch with the inclusion of Tomboy as part of the default Gnome applications rages on, and now RMS has entered the fray.

I respect Stallman a lot. I'm a fellow of FSFE. His positions are usually well thought and argued, though I can't say I agree with him on all of them, and I don't agree with this one.

On the issue of the plain usefulness of Mono apps; well some of them are just excellent. I use f-spot for managing my photo collection and have to say no other application I've used comes close. Tomboy is itself a considerable improvement on the almost useless sticky notes applet that's been in Gnome for some time; though I've yet to work out what minimum I need for ssh synchronization (to be fair, I've hardly tried).

And I should declare an interest. I thought Gnome-Do was absolutely excellent when I stumbled upon it, and I helped in a modest way to initially package it for Debian (specifically I updated the Ubuntu stuff for the plugins package and prepared that for its initial import to the archive), albeit I haven't worked on it since. It's fairly clear to me that implementing this in, for example, C++ looks like it could be a lot more work. I can't say I've studied it in total depth, but that was my feeling when working with the code.

Anyway, never mind all the issues of sheer practicality; Jo Shields of the Debian Mono team, wrote an excellent rebuttal to some of the nonsense that was posted about Mono. It makes excellent reading. It is calmly delivered (with an undertone of quite justified and controlled anger), carefully argued and a cautionary tale about some of the nonsense we in the Free Software community can get wrapped up in, it's value extends well beyond the current debacle.

Posted by Colin Turner

Defined tags for this entry: , ,
Twitter Bookmark Mono in Debian  at del.icio.us Facebook Google Bookmarks FriendFeed Digg Mono in Debian Mixx Mono in Debian Bloglines Mono in Debian Technorati Mono in Debian Fark this: Mono in Debian Bookmark Mono in Debian  at YahooMyWeb Bookmark Mono in Debian  at Furl.net Bookmark Mono in Debian  at reddit.com Bookmark Mono in Debian  at blinklist.com Bookmark Mono in Debian  at Spurl.net Bookmark Mono in Debian  at NewsVine Bookmark Mono in Debian  at Simpy.com Bookmark Mono in Debian  at blogmarks Bookmark Mono in Debian  with wists wong it! Bookmark using any bookmark manager! Stumble It! Print this article! E-mail this story to a friend! Identi.ca