Trivial notes about Feisty

Feisty has been released yesterday, congrats!

I have been using Feisty ever since sometime before beta release, it
was a time I was still fight with my exams and the early upgrading
really put me into a chaos. It’s the earliest upgrading for me ever
since, which leads to two results — on one hand, I got somehow
disappointed about the new version because of the bugs I met were more
than ever as well, on the other hand, I therefore started reporting
bugs via [Launchpad]. This amazing platform for collaboration really
taught me the importance of participation and the responsibility of a
person in a community.

I won’t focus on the new features of Feisty, for a guy who uses Ubuntu
for sometimes and spends only couple of hours every month on windows
for Winning 11 and Video Chatting via Skype, I see more familiarity
and usability from it. To newbies, there are quite a lot HOWTOs,
tutorials out there. When you have problems, remember, Google is your
friend. I also have said, that for Feisty most of the tricks work
as the same as in the Edgy era, so the previous post may still
help to some extent.

Then, What to write for now?

Firstly, I want to mention that even though Feisty has been released,
there are still numbers of bugs stay unsolved. Maybe just their
impact is not significant enough to slow down the release schedule.
However, to some specific people, certain bugs could be very annoying.
Now I’m gonna list some, which I am concerned about, together with
possible temporary solutions. (the last three are in fact not native
ubuntu bugs, but they still bring some trouble, I guess it’s better
to point them out here. )

  1. Some models of Thinkpad series laptop will suffer from an inaudible
    state upon resuming from hibernation. When this occurs, even a
    reboot will not fix the sound while an absolute shut down will
    work. I found out yesterday that if you suspend the machine after
    this inaudible state is triggered, the wake-up action also can
    bring the sound back. (https://bugs.launchpad.net/bugs/80893)

  2. (Some) external storage device, especially those external hard
    disks could not be ejected via GUI. When click on the menu item
    “Eject”, the device is unmounted and soon mounted again with a
    error message prompting on the screen. A possible solution is to
    remove the file
    /usr/share/hal/fdi/policy/10osvendor/10-storage-policy.fdi
    temporarily. (https://bugs.launchpad.net/bugs/63090)

    Update: after the upgrade of several packages related hal
    yesterday(May 12, 2007), the “eject” menu item becomes “unmount”
    and seemingly solves the problem.

  3. Nautilus has a weird bug: the file save dialog deletes file name
    when changing directory. I don’t recall to have such a boring flaw
    in Edgy and sometimes it really makes you angry in Feisty. In case
    you don’t understand what I’m saying, there is a
    screencast I captured to make things clear.
    (https://bugs.launchpad.net/bugs/93396)

  4. The new amarok (1.4.5) and libgpod (0.4.2) can deal with album
    artworks very well now, except when you use a new iPod (2gen Nano,
    or 5.5gen iPod). Because the new firmware only create an empty
    iPod_Control/Device/SysInfo file which is used by libgpod to
    determine the right version of iPod you are using, without which it
    can not transfer the album artworks correctly. A work-around
    currently is to use gtkpod to manually set the model of your new
    iPod, which actually write those information into the file
    mentioned above. Amarok also have the ability to set iPod model
    built-in but unfortunately it doesn’t work at present. It’s said
    that the next version (1.4.6) will fix it. (source:

    http://amarok.kde.org/wiki/Media_Device:IPod#Artwork_not_working)

  5. If you are using Cisco’s VPN client, probably you will have problem
    compiling and installing the client. The reason is some where in
    the source code, a head file which is no longer existed in the
    kernel source after 2.6.19 is included (several times).
    There is a patch and a simple tutorial telling you how to
    make it work.

  6. If azureus keeps crashing or behaves strangely, try the jar
    file
    from official website.

  7. If you’re gonna install Feisty on a laptop with Intel graphic
    chipset, the by default installed xserver-xorg-driver-i810 may
    not give you the right screen solution, especially for 16:9 screen,
    even after you tweak the xorg.conf. To solve this, just install
    the package xserver-xorg-driver-intel instead. (you may need to
    use sudo dpkg-reconfigure xserver-xorg to get proper resolution)

Then, there is some tiny feelings about Feisty:

  1. HPLIP is very useful to those who have HP devices.

  2. Love the new keyboard binding of Evince, the right and left key now
    work as navigating to next/previous page, more intuitive, more
    consistent with Adobe Reader.

  3. As Google Maps has been powerful enough, there is no use to install
    Google Earth, so the high GL performance is not that important for
    me. Therefore, the open-sourced ATI driver could fulfill most
    daily tasks and work harmoniously with Compiz/Beryl. Nevertheless,
    I can not help despising ATI corp. who neither makes the driver
    open-sourced nor adds the basic composite functionality into the
    driver.

  4. Love sudoku, love Gnome-Sudoku

At last, a list of some nifty tools I start to use recently.

  1. Glipper: a useful clipboard manager.

  2. Brasero: The best CD/DVD burning tool with GTK interface.

  3. GTK-RecordMyDesktop: Compared with Istanbul, it could
    be set to encode the video after recording so the video recording
    process could be more smooth with slow hardware.

  4. Gnome-ISO: easy to mount/unmount CD images. (seems not translated
    into English)

  5. Métamorphose: A rename tool based on Python.

Advertisements

About this entry