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.
** Changed in: pidgin-musictracker (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubu
@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 a
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: CertificatePoo
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
r...@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 co
Same problem. I resolved it running pidgin -n and quickly disable the
music tracker plugin...
--
Musictracker doesn't work unless dcopserver is started
https://bugs.launchpad.net/bugs/199438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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.
--
Musictracker doesn't work unless dcopserver is started
https://bugs.launchpad.net/bugs/199438
You received
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
--
Musictracker doesn't work unless dcopserver is started
https:
Does the problem still occur with pidgin-musictracker 0.4.12-1 in
Jaunty?
** Changed in: musictracker (Ubuntu)
Status: New => Invalid
--
Musictracker doesn't work unless dcopserver is started
https://bugs.launchpad.net/bugs/199438
You received this bug notification because you are a membe
I'm still having this problem
--
Musictracker doesn't work unless dcopserver is started
https://bugs.launchpad.net/bugs/199438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
http
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
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&pa
I think this is the upstream report:
http://code.google.com/p/musictracker/issues/detail?id=34
Launchpad can't track its status though
--
Musictracker doesn't work unless dcopserver is started
https://bugs.launchpad.net/bugs/199438
You received this bug notification because you are a member of U
Thanks for trying
** Changed in: pidgin-musictracker (Ubuntu)
Status: Incomplete => Triaged
** Also affects: pidgin-musictracker
Importance: Undecided
Status: New
** Tags removed: dcop musictracker pidgin
--
Musictracker doesn't work unless dcopserver is started
https://bugs.l
The problem is still there with 0.4.11-1 here on my pc.
--
Musictracker doesn't work unless dcopserver is started
https://bugs.launchpad.net/bugs/199438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
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.
** Changed in: pidgin-musictracker (Ubuntu)
Sour
Known upstream.
** Changed in: musictracker (Ubuntu)
Importance: Undecided => Medium
Status: New => Triaged
--
Musictracker doesn't work unless dcopserver is started
https://bugs.launchpad.net/bugs/199438
You received this bug notification because you are a member of Ubuntu
Bugs, which
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
--
Musictracker doesn't work unless dcopserver is started
https://bugs.launchpad.net/bugs/199438
You received this bug notification be
Problem in pidgin-musictracker. After uninstall start perfect...
--
Musictracker doesn't work unless dcopserver is started
https://bugs.launchpad.net/bugs/199438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing lis
Same issue. Ran dcopserver manually, and MSN stopped logging in,
otherwise working okay.
--
Musictracker doesn't work unless dcopserver is started
https://bugs.launchpad.net/bugs/199438
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
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
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
proces
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
22 matches
Mail list logo
