Musictracker doesn't work unless dcopserver is started

[Nic]

Hi, I installed musictracker plugin in pidgin from synaptics and when I enable it, it complains about :

nt271@constantines:~$ pidgin
DCOPClient::attachInternal. Attach failed Could not open network socket
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!
ERROR: Couldn't attach to DCOP server!

This only stops when I manually start dcopserver

This is on hardy 8.04.
Steps to reproduce:
1. enable music tracker plugin in pidgin.
2.close all the music players(though this may not be necessary)
3.restart pidgin.

[Colin Dean (colindean)]

I just encountered this problem, as well, but in Hardy amd64 final. One must start pidgin at the command line with "pidgin -n" and quickly disable the plugin before it attempts to contact the dcopserver.

MusicTracker should fail gracefully if it does not find dcopserver, as those not using any KDE things are probably not going to have dcop running.

[Colin Dean (colindean)]

I tracked it down to src/amarok.c. The plugin, if set to auto, polls every now and then, and if dcopserver is not running, then the call at line 25 eventually fails, but doesn't set any kind of state that dcop isn't running.

C is not strong with me--I'm not sure of the best way to tell if a process is running other than to check a pidfile or parse ps output.

[Serge van Ginderachter (svg)]

I'm running Ubuntu Hardy (Gnome, Pidgin, musictracker plugin and rhythmbox) and encountered that same error after installing a KDE applications, which brought in some KDE libs. After the following startup (= restart pidgin I guess?) it bumped up.

So somehow Piding must be compiled to use some kde libs when available, and only then this bug is triggered.

Removing all kde apps did stopped the bug from happening, and could be a workaround.

[smartalek65 (sahel-khan)]

Same issue. Ran dcopserver manually, and MSN stopped logging in, otherwise working okay.

[Jefferson Martins de Oliveira (jeffersonjbj)]

Problem in pidgin-musictracker. After uninstall start perfect...

[Andrew Conkling (andrewski)]

Seems indirectly related to two upstream bugs:
http://code.google.com/p/musictracker/issues/detail?id=68
http://code.google.com/p/musictracker/issues/detail?id=34

[Hew (hew)]

Known upstream.

[Hew (hew)]

Musictracker has a new upstream, and is now known as pidgin-musictracker. Changing sourcepackage.

Could you please test if this problem still exists with pidgin-musictracker 0.4.11-1 in Jaunty (once it builds and you are able)? Thanks in advance.

[Matthias Mendler (matyy)]

The problem is still there with 0.4.11-1 here on my pc.

[Chris Coulson (chrisccoulson)]

Thanks for trying

[Chris Coulson (chrisccoulson)]

I think this is the upstream report: http://code.google.com/p/musictracker/issues/detail?id=34

Launchpad can't track its status though

[Jon TURNEY (jon-turney)]

musictracker (http://code.google.com/p/musictracker/) is un-maintained.

This defect was thought to be fixed in pidgin-musictracker (http://code.google.com/p/pidgin-musictracker/) since 0.4.2 (with this change http://code.google.com/p/pidgin-musictracker/source/diff?spec=svn205&r=63&format=side&path=/trunk/src/amarok.c&old_path=/trunk/src/amarok.c&old=60)

Matthias,etc: if you can reproduce this bug, please attach output of "pidigin -d" here or raise an issue at http://code.google.com/p/pidgin-musictracker/issues/

[Hew (hew)]

pidgin-musictracker 0.4.11-1 still FTBFS. Matthias, which version did you test with, and where did you obtain it from?

I think it's best to just wait until there is a pidgin-musictracker version in Ubuntu that builds before we do any further testing on this bug, especially since it looks like it's been fixed with 0.4.2.

[Jmadero (jmadero)]

I'm still having this problem

[Hew (hew)]

Does the problem still occur with pidgin-musictracker 0.4.12-1 in Jaunty?

[Petr Kopač (petrkopac)]

Ubuntu 8.10, pidgin-musictracker 0.4.1-1
just updated libc6 (and maybe something more) and pidgin crashed after a while.

ERROR: Couldn't attach to DCOP server!
DCOPClient::attachInternal. Attach failed Could not open network socket

[Hew (hew)]

Petr, 0.4.12-1 in Jaunty is a major improvement over the version in Intrepid. We know the problem occurs in Intrepid. Please test with Jaunty to see if the problem has been fixed. Thanks.

[nicolas kleinklaus (nknico)]

Same problem. I resolved it running pidgin -n and quickly disable the music tracker plugin...

[canapone (fc-85)]

hi i've jaunty

i tried to start pidgin by root without musictracker
this is the bash log

later there is the log of enabling music tracker

root@kalappo:~# pidgin -d
(20:31:43) prefs: Reading /root/.purple/prefs.xml
(20:31:43) prefs: Reading /etc/purple/prefs.xml
(20:31:43) dbus: Failed to get connection: Failed to execute dbus-launch to autolaunch D-Bus session
(20:31:43) plugins: probing /usr/lib/pidgin/gevolution.so
(20:31:43) plugins: probing /usr/lib/pidgin/cap.so
(20:31:43) plugins: probing /usr/lib/pidgin/sendbutton.so
(20:31:43) plugins: probing /usr/lib/pidgin/spellchk.so
(20:31:43) plugins: probing /usr/lib/pidgin/notify.so
(20:31:43) plugins: probing /usr/lib/pidgin/extplacement.so
(20:31:43) plugins: probing /usr/lib/pidgin/xmppconsole.so
(20:31:43) plugins: probing /usr/lib/pidgin/pidginrc.so
(20:31:43) plugins: probing /usr/lib/pidgin/ticker.so
(20:31:43) plugins: probing /usr/lib/pidgin/nautilus.so
(20:31:43) plugins: probing /usr/lib/pidgin/gestures.so
(20:31:43) plugins: probing /usr/lib/pidgin/musictracker.so
(20:31:43) plugins: probing /usr/lib/pidgin/history.so
(20:31:43) plugins: probing /usr/lib/pidgin/gtkbuddynote.so
(20:31:43) plugins: probing /usr/lib/pidgin/iconaway.so
(20:31:43) plugins: probing /usr/lib/pidgin/timestamp_format.so
(20:31:43) plugins: probing /usr/lib/pidgin/timestamp.so
(20:31:43) plugins: probing /usr/lib/pidgin/musicmessaging.so
(20:31:43) plugins: probing /usr/lib/pidgin/pidgin-otr.so
(20:31:43) plugins: probing /usr/lib/pidgin/convcolors.so
(20:31:43) plugins: probing /usr/lib/pidgin/markerline.so
(20:31:43) plugins: probing /usr/lib/purple-2/buddynote.so
(20:31:43) plugins: probing /usr/lib/purple-2/libsametime.so
(20:31:43) plugins: /usr/lib/purple-2/libsametime.so has a prefs_info, but is a prpl. This is no longer supported.
(20:31:43) plugins: probing /usr/lib/purple-2/libmsn-pecan.so
(20:31:43) plugins: probing /usr/lib/purple-2/offlinemsg.so
(20:31:43) plugins: probing /usr/lib/purple-2/joinpart.so
(20:31:43) plugins: probing /usr/lib/purple-2/pidgin-libnotify.so
(20:31:43) plugins: probing /usr/lib/purple-2/libirc.so
(20:31:43) plugins: probing /usr/lib/purple-2/ssl-nss.so
(20:31:43) plugins: probing /usr/lib/purple-2/libmsn.so
(20:31:43) plugins: probing /usr/lib/purple-2/libsimple.so
(20:31:43) plugins: probing /usr/lib/purple-2/liboscar.so
(20:31:43) plugins: /usr/lib/purple-2/liboscar.so is not usable because the 'purple_init_plugin' symbol could not be found. Does the plugin call the PURPLE_INIT_PLUGIN() macro?
(20:31:43) plugins: probing /usr/lib/purple-2/idle.so
(20:31:43) plugins: probing /usr/lib/purple-2/libicq.so
(20:31:43) plugins: probing /usr/lib/purple-2/ssl.so
(20:31:43) plugins: probing /usr/lib/purple-2/libyahoo.so
(20:31:43) plugins: probing /usr/lib/purple-2/dbus-example.so
(20:31:43) plugins: probing /usr/lib/purple-2/libqq.so
(20:31:43) plugins: probing /usr/lib/purple-2/autoaccept.so
(20:31:43) plugins: probing /usr/lib/purple-2/newline.so
(20:31:43) plugins: probing /usr/lib/purple-2/statenotify.so
(20:31:43) plugins: probing /usr/lib/purple-2/perl.so
(20:31:43) plugins: probing /usr/lib/purple-2/log_reader.so
(20:31:43) plugins: probing /usr/lib/purple-2/libxmp...

[canapone (fc-85)]

i'm the same of previous post
when i force to quit the bash told me the memory map

^C(20:39:11) sighandler: Caught signal 2
(20:39:11) certificate: CertificateVerifier tls_cached unregistered
(20:39:11) certificate: CertificateVerifier singleuse unregistered
(20:39:11) certificate: CertificatePool tls_peers unregistered
(20:39:11) certificate: CertificatePool ca unregistered
(20:39:11) main: Unloading all plugins
(20:39:11) plugins: Unloading plugin Nautilus Integration
(20:39:11) nautilus: Stop nautilus plugin
*** glibc detected *** pidgin: corrupted double-linked list: 0x09c05d90 ***
======= Backtrace: =========
/lib/tls/i686/cmov/libc.so.6[0xb767007f]
/lib/tls/i686/cmov/libc.so.6[0xb7671b8d]
/lib/tls/i686/cmov/libc.so.6[0xb7672fbf]
/lib/tls/i686/cmov/libc.so.6(realloc+0x106)[0xb7673ee6]
/usr/lib/libglib-2.0.so.0(g_realloc+0x3a)[0xb789c03a]
/usr/lib/libgtk-x11-2.0.so.0[0xb7ab19ac]
/usr/lib/libgtk-x11-2.0.so.0(gtk_accel_group_connect_by_path+0xed)[0xb7ab245d]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_set_accel_path+0x15e)[0xb7cac76e]
/usr/lib/libgtk-x11-2.0.so.0[0xb7b96647]
/usr/lib/libgtk-x11-2.0.so.0[0xb7b9677a]
/usr/lib/libgobject-2.0.so.0(g_cclosure_marshal_VOID__OBJECT+0x8c)[0xb79288ac]
/usr/lib/libgobject-2.0.so.0[0xb791a3d9]
/usr/lib/libgobject-2.0.so.0(g_closure_invoke+0x1ab)[0xb791bc7b]
/usr/lib/libgobject-2.0.so.0[0xb7931688]
/usr/lib/libgobject-2.0.so.0(g_signal_emit_valist+0x7b9)[0xb7933489]
/usr/lib/libgobject-2.0.so.0(g_signal_emit+0x26)[0xb7933906]
/usr/lib/libgtk-x11-2.0.so.0(gtk_widget_set_parent+0x177)[0xb7cafb77]
/usr/lib/libgtk-x11-2.0.so.0[0xb7b9073a]
/usr/lib/libgtk-x11-2.0.so.0(gtk_menu_shell_insert+0xd4)[0xb7b9a374]
/usr/lib/libgtk-x11-2.0.so.0(gtk_menu_shell_append+0x20)[0xb7b9a3d0]
pidgin[0x8075bc0]
pidgin(pidgin_blist_update_plugin_actions+0x1bb)[0x8075e3b]
/usr/lib/libpurple.so.0(purple_marshal_VOID__POINTER+0x18)[0xb77ed038]
/usr/lib/libpurple.so.0(purple_signal_emit_vargs+0xb1)[0xb77edb01]
/usr/lib/libpurple.so.0(purple_signal_emit+0x33)[0xb77edc43]
/usr/lib/libpurple.so.0(purple_plugin_unload+0x2de)[0xb77d856e]
/usr/lib/libpurple.so.0(purple_plugin_destroy+0x33)[0xb77d86d3]
/usr/lib/libpurple.so.0(purple_plugins_destroy_all+0x2a)[0xb77d88ca]
/usr/lib/libpurple.so.0(purple_core_quit+0xfa)[0xb77c743a]
[0xb8034400]
/usr/lib/pidgin/musictracker.so(get_mpd_info+0x81)[0xb663d6b1]
/usr/lib/pidgin/musictracker.so[0xb66373b9]
/usr/lib/libglib-2.0.so.0[0xb7894186]
/usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x1e8)[0xb7893a58]
/usr/lib/libglib-2.0.so.0[0xb7896fbb]
/usr/lib/libglib-2.0.so.0(g_main_loop_run+0x1ca)[0xb789748a]
/usr/lib/libgtk-x11-2.0.so.0(gtk_main+0xb9)[0xb7b855c9]
pidgin(main+0x89a)[0x80c31ea]
/lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5)[0xb7616775]
pidgin[0x806db61]
======= Memory map: ========
08048000-0810e000 r-xp 00000000 08:08 11820 /usr/bin/pidgin
0810e000-0810f000 r--p 000c5000 08:08 11820 /usr/bin/pidgin
0810f000-08112000 rw-p 000c6000 08:08 11820 /usr/bin/pidgin
097cf000-0a5dd000 rw-p 097cf000 00:00 0 [heap]
b37c2000-b37f3000 r-xp 00000000 08:08 9518 /usr/lib/libcroco-0.6.so.3.0.1
b37f3000-b37f6000 rw-p 00030000 08:08 9518 /usr/lib/libcroco-0.6.so....

[Jon TURNEY (jon-turney)]

@canapone: thanks for the 'pidgin -d' output.

Does 'then i enable plugin and pidgin zombies' mean than pidgin hangs after writing that output?

You need to show that this doesn't occur when dcopserver is running for this to be the same problem as originally reported (this seems unlikey)

Looking at the second attachment, I would suggest disabling the pidgin nautilus integration plugin [nautilus-sendto package] as it seems to be known to cause crashes like that...

[JC Hulce (soaringsky)]

None of the people experiencing the problem ever replied to the questions in this bug report. Thus, this bug cannot be fixed and I am closing it.