GnomeBaker error for Import Session

[jayseye]

Binary package hint: gnomebaker

GnomeBaker 0.6.2 under Ubuntu 7.10 (Gutsy Gibbon) fails to import a session which it has previously created. A dialog box reports "Error getting information / unknown error". This is a different symptom than reported for Bug #71684.

The error dialog occurs regardless of whether the CD is mounted; in fact, GnomeBaker will successfully unmount the CD when trying to import the session. However, the error occurs even if the CD is umounted manually before starting up GnomeBaker.

This appears to be a new error in Gutsy, as the function used to work, per message #6 in a thread:

 http://ubuntuforums.org/showthread.php?t=159835

K3b is able to import the first session from the same CD, so this appears to be a GnomeBaker import bug. Posts on the GnomeBaker forums appear to go unanswered for years, so am reporting here.

Steps to reproduce:
* Insert an appendable CD-R containing one session previously created using GnomeBaker

* Start via Applications > Sound & Video > CD/DVD Writer GnomeBaker

* File > New Project > Data CD (or click Data CD button)

* Project > Import Session

Expected Behavior: Previously recorded session should be imported

Actual Behavior: Error dialog as detailed above

[jayseye (jayseye)]

Brasero was able to import the session, and to burn a subsequent session. This is another difference from Bug #71684 where a comment claimed that it was a backend problem. Also, the workaround mentioned for that previous bug fails to help in this case.

[jayseye (jayseye)]

One of the Gnomebaker developers (Pygi) has replied to my posting #15 on this thread:

 http://ubuntuforums.org/showthread.php?t=159835

and we have been following up on this. In particular, I reported a workaround of manually editing a field to enter a mount point which the program fails to detect. Details are in post #22 of the thread.

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10?

[Pedro Villavicencio (pedro)]

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