Totem crashed while installing ubuntu and crashes on every run

Thank you for your bug. What video card and video driver do you use? Do you have anything to /var/log/messages /var/log/syslog or /var/log/Xorg.0.log about that?

Hi,
My graphics controller is an Intel Mobile 915 GM / GMS /910GML Express. Or that's what it says under Device Driver. Sorry for being clueless but i don't know how to check my video drivers.
I think the Ubuntu installation also overwrote my MBR so i'm actually stuck in linux now unable to boot windows (can't check driver names in windows which i know how to do), but that's a separate issue.

could you have a look to the files pointed by the previous comment or attach them to the bug? the driver is listed to the /etc/X11/xorg.conf configuration

hey,
sorry. slightly busy. Ubuntu installation didn't detect windows so I couldn't boot it, then I tried to fix it with the super grub disk, which completely screwed my main boot record, then I had to run down to the computer vendor's office and get the XP disk which didn't come with the laptop. Will be a bit busy for the next 2 days or so with work piling up : ) sorry! thx for bein patient.

Hi, sorry for the long hiatus! Got sidetracked by exams. Anyway, I had a look at the files you gave, and /var/log/messages was very long and full of numbers in particular. Searched for 'totem' in all the logfiles you listed and didn't find anything (should I have searched for something else?). Nothing looked like it documented anything about totem to the best of my ability.

/etc/x11/xorg.conf lists this as my video card and driver:

Section "Device"
 Identifier "Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller"
 Driver "i810"
 BusID "PCI:0:2:0"
EndSection

Is that what you wanted? Thanks so much for helpin me out n with the long wait!

can you attach the log files to the bug?

yup attached are the files. Briefly, what are these? i gather that /var/log/message is what the OS is instructed to tell you and /var/log/syslog is a log of the system (or system events i suppose) but what's Xorg.0.log? (briefly, just a quick explanation)

Xorg.0.log are the log from the graphical server. Did you get those log after a crash? at what time the crash happened? from a quick look I didn't spot any probolem, that's not a totem bug for sure, not sure if that's xorg or the videodriver or linux to blame though

Hey sebastien,
Attached another set of the 3 logs. Crash happened at 4:26pm when I tried to run the movie player again. Don't really think i'm capable of looking through them and finding out what is wrong.

If the logfiles are normal as per what you've said, think anything else might be the case? where can I look to help solve the problem and get the movie player working? It's never worked since I've installed ubuntu. Video under windows works fine though (running a dual boot)

thank you for the efforts on that. Could you also attach /var/log/kern.log?

that log starts a 4:27pm, it has probably be rotated after the reboot and the error might be to kern.log.0 then

No useful information to that log neither. I'm unsetting the package, that's not a totem bug, might be xorg or linux, maybe somebody else will have an idea on the problem

hey sebastien,
thanks so much for your help. Hoping this thread will go somewhere.
There anything I can do to help in the solving of this problem?

You can try to debug it, otherwise not a lot to do until somebody else pick on the problem and ask you other questions about it

I've also listed my problem on ubuntuforums at the following address:
http://ubuntuforums.org/showthread.php?t=368423

I've listened to the advice of someone there and installed VLC media player, which also promptly crashed. Looks like you were right after all : ) it's not a totem problem... how do I figure out what's wrong with my graphics card or whatever which is causing the problem?

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? If so, please reopen the bug. Thanks in advance.