[Bug 16748] New: Totem crashes on startup in Breezy LiveCD of 23 Sep 05

[bugzilla-daemon at bugzilla.ubuntu.com]

Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=16748
Ubuntu | totem

           Summary: Totem crashes on startup in Breezy LiveCD of 23 Sep 05
           Product: Ubuntu
           Version: unspecified
          Platform: i386
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: totem
        AssignedTo: seb128 at ubuntu.com
        ReportedBy: foner-ubuntu-bugzilla at media.mit.edu
         QAContact: desktop-bugs at lists.ubuntu.com
                CC: foner-ubuntu-bugzilla at media.mit.edu


I just tried booting the latest Breezy LiveCD (the file claims it was written on
23 Sep 05, though the banner when I actually started the CD claimed a build date
in March sometime).  Since Totem has never worked for me in Hoary, I tried it in
Breezy, and it crashed on startup, but in a different way than in Hoary.  In
Breezy, trying to start Totem from the Applications -> Sound and Video menu
causes Totem to pop up a dialog box claiming "The video output is in use by
another application.  Please close other video applications, or select another
video output in the Multimedia Systems Selector."  I haven't touched the default
settings in the MSS.  I also haven't (yet) tried this in a real install, but
I'll try that, soon.

(In Hoary, I was getting a startup error that just says "Resource busy or
unavailable."  I have no idea which resource that is; for all I know, it's a
video resource and Breezy's version of Totem simply has more-informative error
messages.)

I've reproduced this on two different machines, with different motherboards,
display cards, and displays.  Both are AMD CPU's.  I can provide more-complete
configuration information upon request.

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.