[Hardy] kbuildsycoca and kdecore seem to have crashed X for no apparent reason?

[Kaminix]

I don't quite know what to make of this... X just crashed out of the blue and sent me back to KDM. I'll attach these files:
~/.xsession_error
/var/log/Xorg0.log

[Kaminix (kaminix)]

Ah, the title is just my interpretation of the problem after having read the xsession-errors file... could be anything as far as I know.

[Kaminix (kaminix)]

Got the error again, was opening a videofile in Kaffeine.
Will attach the log files again, any feedback requested will be given.

Stream info for the file says:
yes-it-has-a-filename-but-I-wont-tell-ya-lol.mpg
Length: 0:07:34
Mime: video/mpeg
Audio: A/52 2.0 (stereo) 224kb/s
Video: MPEG (libmpeg2) 853x480(720x480)

[Kaminix (kaminix)]

Got the error once again! Hooray!

Kaffeine this time too, here's the stream info of the file I was playing:

the-file-name-has-an-exclamation-mark-but-I-wont-tell-the-rest.AVI
Length: 0:32:08
Mime: video/x-msvideo
Audio: A/52 2.0 (stereo) 192kb/s
Video: ISO MPEG-4 (XviD, ffmpeg) 720x576(720x576)
Subtitle File: /path/to/the-file-name-has-an-exclamation-mark-but-I-wont-tell-the-rest.txt

The .txt file is not a subtitle really, it loaded out of stupidity. :)

I won't bother with the crash reports unless asked to this time......

[Harald Sitter (apachelogger)]

Seriously.
What version of Kubuntu?
What version of KDE?
What version of Kaffeine?
What packages for video codecs are installed?
Do you use medibuntu?
What version of the intel graphics driver?
What is the exact file name?
a) Xorg.0.log would be the one form the _current_ session, so it is of no use, attach .1.log for the previous (i.e. crashed session)
b) basically same applies for .xsession-error, just that getting the previous is a bit more complicate. You have 2 options: either you go right after the crash to tty1 (i.e. ctrl-alt-f1) and copy the file to crash-xsession-errors or something, or you create a new user and access the file (might also require a terminal though).

[Jonathan Thomas (echidnaman)]

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 the current status, under the Status column, and change the Status back to "New". Thanks again!