Feeds:
Posts
Comments

Posts Tagged ‘kde’

Since version 2.6, you can tell Amarok to convert (transcode) every music track to MP3 when copying it to a given device.

There’s a bug, however which causes MP3 files converted from Ogg Vorbis to lose all metadata (artist, album, title etc). This is a showstopper for me.

This happens because Amarok needs to pass an option to ffmpeg to tell it to get the metadata from the first stream found in the Ogg file as opposed to the default of getting it from global metadata. Unfortunately as far as I can tell there’s no way to configure the ffmpeg command line used by Amarok. The solution then is to replace the ffmpeg binary in the path with a script that will do that, like this one:

#!/usr/bin/python
import os
import sys

AVCONV_FFMPEG = '/usr/bin/ffmpeg.distrib'
os.execv(AVCONV_FFMPEG, sys.argv + ['-map_metadata', '0:0,s0'])

In Debian or Ubuntu, you can divert the real ffmpeg binary and install the script above as /usr/bin/ffmpeg:

$ sudo dpkg-divert --add /usr/bin/ffmpeg
$ sudo cp /tmp/fake-ffmpeg.py /usr/bin/ffmpeg
$ sudo chmod +x /usr/bin/ffmpeg

There’s another bug where Amarok needlessly converts even MP3 files when copying them to the device.

Read Full Post »

I was downloading pics from my camera this weekend (strictly speaking, from its SD card) and found out about a nasty bug: digikam will fail to download an image for no good reason, and overwrite good images when you tell it to try again! I immediately opened a bug report, let’s how this progresses. A comment in the bug report suggests that downgrading back to 0.9.2 will avoid the problem. I didn’t test it, but I certainly will do that.

In addition, you need pay attention to the import wizard’s window to see if all images were downloaded correctly. If an error occurs, the only indication is a small red cross on the image itself. There’s no warning dialog or status message telling you that something went wrong. You have to check each image. I opened a bug report about this too.

This is actually the first problem I had with digikam, and have always had a great experience with it. I really recommend the application to organize your photos (well, just avoid version 0.9.3 🙂 ). Along with amarok, I think it’s one of KDE’s killer apps.

Read Full Post »

KDE vs XFCE in terms of memory usage

For the moment I have to cope with a low-memory machine at home, so I decided to switch it from KDE to XFCE. But is it really worth it, in terms of memory savings? I decided to measure…

First of all, I’m not trying to do rigorous analysis here but just do some estimates to make a decision for personal use. Still, if you find something in my method which invalidates the results I obtained, I’d be glad to know about it.

To know the memory consumption of each desktop system, I simply started a fresh session in that desktop, opened a terminal and obtained a process listing with ps -e. No other program was opened at the time. Because I did this using a new user account, the test was made with the default configuration and default loaded programs of each desktop system.

Since the important figure in the ps output is the RSS (resident set size) column, I also turned off the swap partition in my computer. The ps manpage says that the RSS field doesn’t count swapped memory from the process. Good thing I noticed this before it was too late!

Here is the result for KDE:

program vsz rss
Xorg 23,936 18,304
kded 35,608 16,136
kdesktop 33,452 15,200
konsole 33,512 14,540
kicker 34,888 14,388
korgac 33,520 12,788
kwin 30,520 11,628
kpowersave 30,792 11,024
knotify 36,400 10,688
klipper 28,456 9,652
ksmserver 27,124 8,368
artsd 22,452 8,168
kaccess 27,212 8,028
seahorse-agent 20,828 6,608
klauncher 27,476 6,324
kio_file 26,048 5,376
gconfd-2 6,692 3,736
bash 6,368 3,728
kdeinit 25,764 3,516
dcopserver 25,616 2,916
startkde 4,300 1,492
gam_server 3,108 1,408
ssh-agent 4,508 724
dbus-daemon 2,760 532
kwrapper ksmserver 1,692 364
dbus-launch 2,916 340
total 555,948 195,976

And here is the result for XFCE:

program vsz rss
Xorg 27,776 20,788
gnome-terminal 43,652 16,860
xfdesktop 57,172 14,848
update-notifier 24,996 14,480
xfce4-panel 20,580 12,340
notification-daemon 19,156 10,224
xfce4-session 18,016 10,092
xfwm4 16,216 8,344
xfce4-menu-plugin 15,780 7,856
seahorse-agent 20,864 6,772
xfce-mcs-manage 18,812 6,148
gnome-volume-manager 18,108 4,744
Thunar 13,880 4,472
gconfd-2 6,692 3,776
bash 6,412 3,740
bonobo-activation-server 15,264 2,892
xscreensaver 4,240 1,936
/bin/sh /etc/xdg/xfce4/xinitrc — /etc/X11/xinit/xserverrc 4,292 1,444
gam_server 3,108 1,408
dbus-daemon 2,760 892
gnome-pty-helper 2,720 756
ssh-agent 4,508 728
dbus-launch 2,916 440
total 367,920 155,980

So, XFCE uses 152MB of RAM, versus the 191MB KDE uses. Not bad, almost 40MB (20%) less!

That’s not the whole story, though. I also wrote down the output of the free command as a sanity check.

Using KDE:

  total used free shared buffers cached
Mem: 256112 245040 11072 0 20832 138236
-/+ buffers/cache: 85972 170140      
Swap: 0 0 0      

Using XFCE:

  total used free shared buffers cached
Mem: 256112 251340 4772 0 20332 127156
-/+ buffers/cache: 103852 152260      
Swap: 0 0 0      

Look at the “used” column, in the “-/+ buffers/cache” line. That is the actual memory amount being used by the running programs in the computer.

This is a very interesting and surprising result: at the end of the day, XFCE actually uses more memory than KDE! Why, if adding up the resident sizes of the processes from each desktop system you get a different conclusion?

One explanation would be that KDE actually shares more memory between processes than XFCE. Its programs most probably have a greater number of shared libraries in common, which enables the kernel to use the same memory pages for the text section of those libraries accross process images. Unfortunately I didn’t collect data to test that possibility, and it’s late at night now. But it makes sense.

The bottom line, surprisingly enough, is that you should stick with KDE to preserve memory. Or switch to a bare-bones window manager instead of a complete desktop system, like IceWM, Window Maker, Blackbox or something else. But I’m too spoiled by the amenities of a good desktop to do that. 🙂

By the way, the tests were made with KDE 3.5.8 and XFCE 4.4.2 under Debian GNU/Linux unstable (updated on 2008/01/06) on a 32-bit x86 machine.

Read Full Post »

keeping track of timezones

Working in the LTC means working with people spread around the globe. Or at least at a few different timezones…

I just found out about this feature in KDE which I suspect will become very handy for me from now on: have the taskbar’s clock show the time in different timezones:

To enable it, just right-click on the clock, select “Configure Clock…” and then the “Timezones” tab.

GNOME, of course, has the same feature. That’s how I had the idea to search for this in the first place…

Read Full Post »

O time do meu projeto está distribuído em 3 fusos horários, e às vezes surgem compromissos em um quarto fuso horário. Claro q são só contas de adição e subtração, mas é chato e muito fácil de errar e de confundir fusos horários.

Acabo de descobrir uma funcionalidade do KDE q vai se tornar muito útil daqui pra frente: o relógio da barra de tarefas consegue mostrar as horas em diversos fusos horários:

clock-timezones.png

Para configurar isso, basta clicar com o botão direito no relógio, clicar em “Configure Clock…” e selecionar a aba “Timezones”.

O GNOME, claro, tem a mesma coisa. Aliás, foi assim q tive a idéia de procurar isso no KDE.

Read Full Post »