work around for gnome app user:
Delete or move dcop from /usr/bin/dcop
--
mplayer doesn't start immediately
https://bugs.launchpad.net/bugs/246675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package mplayer -
2:1.0~rc3+svn20090426-1ubuntu1
---
mplayer (2:1.0~rc3+svn20090426-1ubuntu1) karmic; urgency=low
* Switch to debian packaging for the mplayer package
* New upstream release, LP: #336697, #260918, #246675, #243453, #74282
* Fixes
This not seems an issue anymore for me (on Jaunty).
I have installed both kde3 libs and a complete kde4 desktop, no problems at all.
--
mplayer doesn't start immediately
https://bugs.launchpad.net/bugs/246675
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I still experience this - note that it does not occur if any kde
application has been started since login, as the kde application will
start up dcopserver.
--
mplayer doesn't start immediately
https://bugs.launchpad.net/bugs/246675
You received this bug notification because you are a member of
Davide, is this still an issue for you?
Benjamin, you set this to in progress and suggested a few solutions, but you
didn't attach the patch and didn't assign this to yourself. Are you actively
working on this? Are the solutions you proposed still valid?
--
mplayer doesn't start immediately
This is an old bug, it existed an hardy and feisty (I don't remember further).
This is not a regression as said in bug 292928.
--
mplayer doesn't start immediately
https://bugs.launchpad.net/bugs/246675
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hi,
I confirm that behaviour on Hardy.
On my system, it seems to hang at
xscreensaver_disable: Could not find XScreenSaver window.
GNOME screensaver disabled
After strace-ing the process, i could find that it's waiting for a child process
which is, according to the 'ps' command :
sh -c dcop
Hi again,
After investigation, it happens that the source of the problem is that the
screensaver-shuttingdown code (which is compiled-in on the packaged mplayer)
probes for the kde screensaver by calling dcop. This should work on pure
gnome desktop, as this command doesn't exists and returns
** Changed in: mplayer (Ubuntu)
Status: New = In Progress
--
mplayer doesn't start immediately
https://bugs.launchpad.net/bugs/246675
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Note that you can workaround the whole problem by disabling the
xscreensaver-disabling code.
Either add
stop-xscreensaver=0
to the ~/.mplayer/config
or reverse this setting in /etc/mplayer/mplayer.conf
--
mplayer doesn't start immediately
https://bugs.launchpad.net/bugs/246675
You received
I recall the first time I faced this problem was when I had installed
kubuntu and then uninstall some parts of it. It should be related to KDE
as you said.
--
mplayer doesn't start immediately
https://bugs.launchpad.net/bugs/246675
You received this bug notification because you are a member of
11 matches
Mail list logo
