We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on
You can try to obtain a backtrace following the instructions at
http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace
(as an attachment) to the bug report.
--
totem crashes when streaming
https://bugs.launchpad.net/bugs/447463
You received this bug notification because you are a
The bug there is not a crash one, are you sure the software is crashing?
--
totem crashes when streaming
https://bugs.launchpad.net/bugs/447463
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to totem in ubuntu.
--
desktop-bugs mailing
The bug there is not a crash one, are you sure the software is
crashing?
Sorry, I'm new here, and English isn't my first language. Consider it
wrongly phrased, maybe one can just edit the title to Totem obscures my
screen thus making my computer uttely unusable. Maybe it wasn't a
crash, so your
Do you get the issue every time? Can you switch to a vt when getting the
bug?
** Changed in: totem (Ubuntu)
Status: Invalid = Incomplete
--
totem crashes when streaming
https://bugs.launchpad.net/bugs/447463
You received this bug notification because you are a member of Ubuntu
Desktop
Not sure what a vt is. And I hadn't got this particular black screen for
a long time, for I don't use the streaming function much. I've also
taken a look at the above link for DebuggingProgramCrush, but personally
found the explanation convoluted. Thanks anyway. But I've learnt that
the right
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33370931/Dependencies.txt
** Attachment added: ProcMaps.txt
http://launchpadlibrarian.net/33370933/ProcMaps.txt
** Attachment added: ProcStatus.txt
http://launchpadlibrarian.net/33370934/ProcStatus.txt
--
totem
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, your crash report is either missing or
challenging to deal with as a .crash file. Please follow these
instructions to have apport report a new bug about your crash that can
be dealt with by the automatic
Hi Pedro. I'm sure this is an automated message, so I don't know if
you'll read this. However, this afternoon I had already reported this
bug, and had already got the above message. For this reason, I enabled
Apport as indicated, restarted, and reported this very bug. How come my
crash report is