Package: pidgin-musictracker
Version: 0.4.1-1
Severity: wishlist

Observing through debug window that musictracker seems to check every
ten seconds for a status update in music player (in my case, XMMS).

(17:03:24) core-musictracker: libxmms.so libxmms.so.1
(17:03:24) core-musictracker: Failed to load library libxmms.so
(17:03:24) core-musictracker: Got position 4460
(17:03:24) core-musictracker: Got state 2
(17:03:24) core-musictracker: Got title PERFORMER |  | TRACKNAME
(17:03:24) core-musictracker: XMMS,PERFORMER,,TRACKNAME,2
(17:03:24) core-musictracker: Formatted status: XMMS: TRACKNAME (7:07) by 
PERFORMER on 
(17:03:24) core-musictracker: Filtered status: XMMS: TRACKNAME (7:07) by 
PERFORMER on 
(17:03:24) core-musictracker: Status set for all accounts

This happens every ten seconds, and I'm concerned that unless the
libpurple internals are realising that the message isn't actually
changing when I'm in the same track, that I'm flooding my buddies with
status updates.

Additionally, if I get a crap track in random play, and I'm "next, next,
next" through the tracks in my playlist for more than ten seconds, does
that mean my buddies potentially get three updates in 22 seconds? If
this is the case, perhaps it'd be best to introduce some configurable
throttling (or perhaps this is the case and just needs to be
documented or I'm suffering a case of "domestic blindness").

Also, some of my tracks don't have album information (as shown in
example above) or may be singles etc. - perhaps conditional formatting
code to allow exclusion of a particular string sequence in the message
if the variable is null/whitespace?

Lastly - just out of curiosity - the failed to load library libxmms.so,
I take it that's just because it tries libxmms.so, then libxmms.so.1?
Once it's done it once successfully, shouldn't it cache rather than
banging away at something it knows doesn't exist, or is this in case
people change their software config whilst pidgin running?

... arguably if a library were changed, and then it failed, perhaps then
one would fall back to checking both before complaining? Maybe this is
related to autodetect (though I have it set specifically to XMMS).


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (700, 'unstable'), (600, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.23.1 (PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages pidgin-musictracker depends on:
ii  libatk1.0-0                   1.20.0-1   The ATK accessibility toolkit
ii  libc6                         2.7-6      GNU C Library: Shared libraries
ii  libcairo2                     1.4.14-1   The Cairo 2D vector graphics libra
ii  libdbus-1-3                   1.1.2-1    simple interprocess messaging syst
ii  libdbus-glib-1-2              0.74-1     simple interprocess messaging syst
ii  libfontconfig1                2.5.0-2    generic font configuration library
ii  libglib2.0-0                  2.14.5-2   The GLib library of C routines
ii  libgtk2.0-0                   2.12.5-2   The GTK+ graphical user interface 
ii  libpango1.0-0                 1.18.4-1   Layout and rendering of internatio
ii  libpcre3                      7.4-1      Perl 5 Compatible Regular Expressi
ii  libx11-6                      2:1.0.3-7  X11 client-side library
ii  libxcomposite1                1:0.4.0-1  X11 Composite extension library
ii  libxcursor1                   1:1.1.9-1  X cursor management library
ii  libxdamage1                   1:1.1.1-3  X11 damaged region extension libra
ii  libxext6                      1:1.0.3-2  X11 miscellaneous extension librar
ii  libxfixes3                    1:4.0.3-2  X11 miscellaneous 'fixes' extensio
ii  libxi6                        2:1.1.3-1  X11 Input extension library
ii  libxinerama1                  1:1.0.2-1  X11 Xinerama extension library
ii  libxrandr2                    2:1.2.2-1  X11 RandR extension library
ii  libxrender1                   1:0.9.4-1  X Rendering Extension client libra

pidgin-musictracker recommends no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to