I tried also Chromium, and after crash Ubuntu asks me for sending crash report, but after while said, that I cant fill the report, cause the software is not from canonical. When I tried seccond time with Chromium, Every windows frame dissapered (unity-window-decorator).
Only after Opera crashed, I have some file in /var/crash, but trying to send:
pmanski@thinkpad:~$ unity-window-decorator ubuntu-bug /var/crash/_usr_lib_opera_opera.1000.crash
The program 'unity-window-decorator' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 4172 error_code 11 request_code 53 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.)
I've tried to generate crash report, but I cant.
pmanski@thinkpad:~$ sudo service apport start force_start=1
[sudo] password for pmanski:
apport start/running
So, apport is running. Now I resized TERMINAL, EMPATHY, BANSHEE, SHOTWELL, and ther was not any file in /var/crash
pmanski@thinkpad:~$ ls -al /var/crash
razem 8
drwxrwxrwt 2 root root 4096 2011-05-26 08:31 .
drwxr-xr-x 15 root root 4096 2011-04-23 00:02 ..
I tried also Chromium, and after crash Ubuntu asks me for sending crash report, but after while said, that I cant fill the report, cause the software is not from canonical. When I tried seccond time with Chromium, Every windows frame dissapered (unity- window- decorator) .
Only after Opera crashed, I have some file in /var/crash, but trying to send:
pmanski@thinkpad:~$ unity-window- decorator ubuntu-bug /var/crash/ _usr_lib_ opera_opera. 1000.crash window- decorator' received an X Window System error.
The program 'unity-
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 4172 error_code 11 request_code 53 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.)