An error occurred Disconnected: Connection terminated - totem - jaunty jackalope

Bug #348002 reported by manzur
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
totem (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

i was playing a video with totem and suddenly this error message pop up and my audio was broken too, i know this because i could not hear pidgin's sounds anymore, i do not know what could be happening, if u need more details please ask...

Kurt Wall (kwall)
affects: ubuntu → totem (Ubuntu)
Revision history for this message
Ілля Романенко (ilyaromanenko) wrote :

same here after update to jaunty :(
but it could happen without any interference with pidgin - when i start totem audio broken - if i restart totem couple of times it begin to work fine....

Please fix this!

P.S. in 8.10 all was fine :(

Revision history for this message
Ілля Романенко (ilyaromanenko) wrote :

actually i want comment that same problem persists in rythmbox

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report, could you test the same with jaunty? and see if the issue is fixed there? what error message do you get? do you use pulseaudio, alsa or oss?

Changed in totem (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
manzur (sl-solaris) wrote :

I can not test it in jaunty because that means i have to reinstall my system, but it occurred in jaunty too and now in karmic.
I am using alsa

Revision history for this message
Sebastien Bacher (seb128) wrote :

do you still have the issue is current karmic?

Revision history for this message
Mihai Glont (mihai-glont) wrote :

Hi,

I'm currently using jaunty, and I'm receiving this error message quite often both in totem and in rhythmbox. I believe I'm currently using pulseaudio. Do you need any other info? Thanks.

Revision history for this message
sash (6-admin-interneta-inbox-ru) wrote :

hi all

try next:
in terminal
1)pulseaudio -k
2)pulseaudio
3)start videofile and wait error
4)if error in terminal is

Soft CPU time limit exhausted, terminating.
E: cpulimit.c: Received request to terminate due to CPU overload.

then
edit /etc/pulse/daemon.conf and change srting
;no-cpu-limit = no on
no-cpu-limit = yes

Revision history for this message
Mihai Glont (mihai-glont) wrote : Re: [Bug 348002] Re: An error occurred Disconnected: Connection terminated - totem - jaunty jackalope

Hey sash,

This is just to let you know that I am now using karmic and have had no
problems with totem whatsoever.

Thanks,
Mihai

2010/1/19 sash <email address hidden>

> hi all
>
> try next:
> in terminal
> 1)pulseaudio -k
> 2)pulseaudio
> 3)start videofile and wait error
> 4)if error in terminal is
>
> Soft CPU time limit exhausted, terminating.
> E: cpulimit.c: Received request to terminate due to CPU overload.
>
> then
> edit /etc/pulse/daemon.conf and change srting
> ;no-cpu-limit = no on
> no-cpu-limit = yes
>
> --
> An error occurred Disconnected: Connection terminated - totem - jaunty
> jackalope
> https://bugs.launchpad.net/bugs/348002
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “totem” package in Ubuntu: Incomplete
>
> Bug description:
> i was playing a video with totem and suddenly this error message pop up and
> my audio was broken too, i know this because i could not hear pidgin's
> sounds anymore, i do not know what could be happening, if u need more
> details please ask...
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/totem/+bug/348002/+subscribe
>

--
Remember who you are, what you stand for and there will always be a way!

Revision history for this message
Pedro Villavicencio (pedro) wrote :

ok thanks, closing the bug since seems to be fixed on karmic as per users comments.

Changed in totem (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Pandelis Xanthopoulos (pxanth) wrote :

This bug exists on Maverick RC. It may be related to Bug #410047.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.