serpentine progress bar will not advance past "preparing files..."

Bug #24574 reported by Adam Wiggins
This bug report is a duplicate of:  Bug #22501: serpentine couldnt start to burn. Edit Remove
8
Affects Status Importance Assigned to Milestone
serpentine (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Having installed Ubuntu for the first time a few days ago (and being thoroughly
impressed with it all around), I decided to try out CD burning. Inserting a CD
popped up a nice dialog asking what I wanted to do, and I selected Burn Audio.
This launched Serpentine, to which I dragged a couple of .wav files and clicked
Write. This produced a progress dialog, but the bar never advanced (I waited
about ten minutes). The entire time it said "Preparing files..." I tried it
again from scratch and the same thing happened.

Oddly enough by closing Serpentine and then opening the CD-R icon on the gnome
desktop, I was able to drag the same wav files into the space on the file
browser and click "write disc" and that worked just fine.

Is there a log file or something for serpentine that I can produce to help debug
this?

Revision history for this message
Tiago Cogumbreiro (cogumbreiro) wrote :

Yes running serpentine from the command line, It's probably an exception that
was thrown and since you have no terminal you can't read it.

Revision history for this message
Adam Wiggins (hiro) wrote :

Ok, here it is. By the way I tested it with other files and it works fine - it
seems to be just this group of three files (which are podcasts converted to wav
by mpg321).

Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/serpentine/operations.py", line 228, in
 __start_next
    oper.start()
  File "/usr/lib/python2.4/site-packages/serpentine/converting.py", line 67, in
start
    self._send_finished_event (success = operations.SUCCESSFUL)
TypeError: _send_finished_event() got an unexpected keyword argument 'success'
Terminated

Here's a screenshot, too:

http://dusk.org/adam/tmp/serpentine.jpg

By the way, is there any way to kill this window (which is locked up - clicking
"cancel" does not work) easily using the Gnome desktop? I'm used to KDE where
trying to close a window that is hardlocked will produce a dialog asking if you
want to force-kill it, or barring that, you can press ctrl-alt-esc to get a
skull and crossbones and click on the window you want to kill. The only thing I
was able to do here was pop up the system monitor, scroll through a list of 50+
processes, finally figure out that the CD Burner process was named "python", and
kill it there. Not exactly user-friendly.

Revision history for this message
Tiago Cogumbreiro (cogumbreiro) wrote :

This bug has been marked as a duplicate of bug 22501.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.