Brasero crash on file rename

[Dennis Prochko]

Binary package hint: brasero

0. Start brasero via terminal
1. Create new Data project.
2. Add video file Monstry.Protiv.Prisheltsev.2009.RUS.BDRip.XviD.AC3.-HQ-ViDEO.avi
3. Select it, press F2 to rename. Try to move cursor at beginning of the file name (Home key) and try to select the part of the name (Shift + cursor keys)
4. The brasero crashes with the following error in the terminal:
$ brasero
brasero: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

The core dump file doesn't created (ulimit -c unlimited was executed)

ProblemType: Bug
Architecture: amd64
Date: Sat Nov 7 22:06:49 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: brasero 2.28.2-0ubuntu1
ProcEnviron:
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-9.152-rt
SourcePackage: brasero
Uname: Linux 2.6.31-9-rt x86_64

[Narcissus (narcissus)]

I confirm this behavior in Brasero 2.28.2-0ubuntu1 in Ubuntu 9.10 i386.

The complete error message was:

(brasero:3454): Gtk-CRITICAL **: gtk_tree_view_drag_begin: assertion `path != NULL' failed
brasero: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.

The same happens even when Brasero is not launched from a terminal.

[Pedro Villavicencio (pedro)]

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 retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.