brasero stalls when attempting to write to mounted media

Bug #487229 reported by daf on 2009-11-23
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
brasero (Ubuntu)
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: brasero

When attempting to re-write DVD+RW media that was automatically mounted by Nautilus (I assume), brasero asks if the user would like to erase the existing media. If the user accepts the erase, brasero stalls, leaving a dialog on screen which states "getting size".

If I unmount the media first (eg, through nautilus), then brasero performs the erase and goes on to do the write operation.

Expected: when asked if I would like to erase and re-write media, if I seleect "erase", the media should be automatically unmounted and erased.
Happened: brasero stalls, claiming that it's "getting size". The burn operation isn't even started.

ProblemType: Bug
Architecture: amd64
Date: Mon Nov 23 20:30:39 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027.1)
NonfreeKernelModules: nvidia
Package: brasero 2.28.2-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_ZA.UTF-8
 SHELL=/bin/zsh
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SourcePackage: brasero
Uname: Linux 2.6.31-15-generic x86_64

daf (davydm) wrote :
daf (davydm) wrote :

It seems this may be related to all of the prior issues I've had with the upgrade to Karmic (and the subsequent reload with re-use of my ~): it seems that there's something problematic in my .gconf, .local or .gconfd from the Jaunty days which doesn't play nice with Karmic gnome stuff:
I backed up and removed all of these three and found that this problem, amongst others, seems to be gone now. Of course, I had to set up my desktop the way I like it again, but at least things all work.

I;m quite willing to provide the before and after snapshots of these dirs in case anyone cares to track down the issue. I would imagine that the issues I've had and the resolution I've had would be not dissimilar to the issues and required resolution for so many people struggling with the Jaunty to Karmic upgrade.

Pedro Villavicencio (pedro) wrote :

Thanks for the report, please try to obtain a backtrace of the hang following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in brasero (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Medium
status: New → Incomplete

I've managed to make this problem go away by moving the following dirs and
letting them be re-created:

~/.local
~/.gconf
~/.gconfd

They were around from when I upgraded from Jaunty. I'll see if I can't
re-instate them and track down the issue. It's probably quite common for
people upgrading or installing new and re-using their old ~ dir.

-d

2009/11/25 Pedro Villavicencio <email address hidden>

> Thanks for the report, please try to obtain a backtrace of the hang
> following the instructions at
> http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace
> (as an attachment) to the bug report. This will greatly help us in
> tracking down your problem.
>
> ** Changed in: brasero (Ubuntu)
> Importance: Undecided => Medium
>
> ** Changed in: brasero (Ubuntu)
> Status: New => Incomplete
>
> ** Changed in: brasero (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
>
> --
> brasero stalls when attempting to write to mounted media
> https://bugs.launchpad.net/bugs/487229
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
There is no shame in not knowing; the shame is in not finding out.

Pedro Villavicencio (pedro) wrote :

please keep us posted, thanks for your testing.

Vish (vish) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. 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".

Changed in brasero (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers