once you force quit totem it doesn't open again

[Ujwal Medithi]

Binary package hint: totem-gstreamer

while using seek bar too fast, totem froze. i force quit it and tried to open it again but it refuses to do so. i use feisty(if that helps)

ProblemType: Bug
Architecture: i386
Date: Wed Aug 15 22:03:00 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.18.1-0ubuntu3.1
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/ujwal
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: gnome-panel
Uname: Linux ujwal-desktop 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. May you try to run totem from a command line and paste the output to this report?. thanks in advance.

[Ujwal Medithi (ujwal10101)]

when i simply type totem, nothing happens.
but when i type sudo totem this is what i got:

** (totem:6052): WARNING **: Failed to connect to the session bus: Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.

** (totem:6052): WARNING **: Error connecting to DBus: Did not receive a
reply. Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.

** (totem:6052): CRITICAL **: totem_remote_window_activated: assertion
`DBUS_IS_G_PROXY (remote->media_player_keys_proxy)' failed

** (totem:6052): CRITICAL **: totem_remote_window_activated: assertion
`DBUS_IS_G_PROXY (remote->media_player_keys_proxy)' failed

and then totem opened but it was not able to show any video.

i typed sudo totem again and i got a longer message:

** (totem:6284): WARNING **: Failed to connect to the session bus: Did not
receive a reply. Possible causes include: the remote application did not
send a reply, the message bus security policy blocked the reply, the reply
timeout expired, or the network connection was broken.

** (totem:6284): WARNING **: Error connecting to DBus: Did not receive a
reply. Possible causes include: the remote application did not send a reply,
the message bus security policy blocked the reply, the reply timeout
expired, or the network connection was broken.

** (totem:6284): CRITICAL **: totem_remote_window_activated: assertion
`DBUS_IS_G_PROXY (remote->media_player_keys_proxy)' failed

** (totem:6284): CRITICAL **: totem_remote_window_activated: assertion
`DBUS_IS_G_PROXY (remote->media_player_keys_proxy)' failed

** (totem:6284): CRITICAL **: totem_remote_window_activated: assertion
`DBUS_IS_G_PROXY (remote->media_player_keys_proxy)' failed

** (totem:6284): CRITICAL **: totem_remote_window_activated: assertion
`DBUS_IS_G_PROXY (remote->media_player_keys_proxy)' failed
No accelerated IMDCT transform found
No accelerated IMDCT transform found
Stream with high frequencies VQ coding

** (totem:6284): CRITICAL **: totem_remote_window_activated: assertion
`DBUS_IS_G_PROXY (remote->media_player_keys_proxy)' failed
the above line was repeated 12 lines.

On 8/16/07, Pedro Villavicencio <email address hidden> wrote:
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. May you try to run totem from a command line and paste
> the output to this report?. thanks in advance.
>
> ** Changed in: totem (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: New => Incomplete
>
> --
> once you force quit totem it doesn't open again
> https://bugs.launchpad.net/bugs/132731
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Pedro Villavicencio (pedro)]

Why are you running totem with sudo anyways? you should do it. Just running it with your user.

[Ujwal Medithi (ujwal10101)]

bcoz nothing happens when u click on totem in the menu as well as when u
type totem in terminal. but thats only after u force quit it.
btw its not a very big problem. i havent force quitted totem for a long time

On 9/7/07, Pedro Villavicencio <email address hidden> wrote:
>
> Why are you running totem with sudo anyways? you should do it. Just
> running it with your user.
>
> --
> once you force quit totem it doesn't open again
> https://bugs.launchpad.net/bugs/132731
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Pedro Villavicencio (pedro)]

Still an issue?

[Pedro Villavicencio (pedro)]

The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Gutsy Gibbon. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

[Ujwal Medithi (ujwal10101)]

I don't have a very fast net connection and my ISP charges me for every MB i
download. So I cant download Gutsy Gibbon to test it. Perhaps someone else
could do it. I sincerely hope it is fixed before the final release.

On 10/2/07, Pedro Villavicencio <email address hidden> wrote:
>
> The issue that you reported is one that should be reproducible with the
> live environment of the Desktop CD of the development release - Gutsy
> Gibbon. It would help us greatly if you could test with it so we can
> work on getting it fixed in the next release of Ubuntu. You can find out
> more about the development release at http://www.ubuntu.com/testing/ .
> Thanks again and we appreciate your help.
>
> --
> once you force quit totem it doesn't open again
> https://bugs.launchpad.net/bugs/132731
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Pedro Villavicencio (pedro)]

I'm closing this report for now, feel free to re open it or report a new one if you can reproduce the problem with a Gutsy Gibbon installation, thanks.