opera 10.60 Internal pada

[bed]

Nazdarek mam ubuntu 9.04 a dlouho pouzivam operu po posledni aktualizaci mi pri navstiveni stranky stream.cz sekce hudba opera spadne nevite co stim. prikladam vypis z terminalu.

Kód: [Vybrat]

bed@bed-desktop:~$ opera
opera [crash logging]: CRASH!!
/usr/lib/opera/opera got signal SIGSEGV at address 08277BFC

Log was created here:
/var/tmp/crash20100702172129.txt
Killed
bed@bed-desktop:~$ opera [crash logging]: CRASH!!
/usr/lib/opera/opera got signal SIGSEGV at address 08277BFC

Log was created here:
/var/tmp/crash20100702172159.txt
opera [crash logging]: CRASH!!
/usr/lib/opera/opera got signal SIGSEGV at address 08277BFC

Log was created here:
/var/tmp/crash20100702172210.txt
opera [crash logging]: CRASH!!
/usr/lib/opera/opera got signal SIGSEGV at address 08277BFC

Log was created here:
/var/tmp/crash20100702172223.txt
The program 'operapluginwrapper' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 452 error_code 3 request_code 2 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'operapluginwrapper' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 452 error_code 3 request_code 2 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'operapluginwrapper' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 452 error_code 3 request_code 2 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)