(trunk) gstreamer error breaks the pipe (normal engine), and it's not shown in the dialog

Bug #939487 reported by Rocco Aliberti
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Exaile
Fix Released
Medium
Mathias Brodala

Bug Description

rev3926
normal engine.

When i try to play a track which no longer exists, but it's still in the collection, some problems occur.

-First, the error is not shown in the dialog, i get:

TypeError: Gtk.Label.set_markup() argument 1 must be string, not gst.Message

That's cause, in xl/player/_base.py lines 119-120, we have:

            a = message.parse_error()[0]
            event.log_event('playback_error', self, message)

Maybe it should be(?):
            a = message.parse_error()[1]
            event.log_event('playback_error', self, a)

- Second, if i try to play another track after that, the pipe is broken and i get:

(exaile.py:16919): GStreamer-WARNING **: Element 'bin1' already has parent

I also noticed that the breakage doesn't occur if the "fake-track" is in first position in the playlist.

I also tried with unified engine, but I get inconsistent results, sometimes it happens sometimes not.

I attach the concerned portion of the shell output.

Revision history for this message
Rocco Aliberti (eri.trabiccolo) wrote :
Revision history for this message
Rocco Aliberti (eri.trabiccolo) wrote :

The pipe breakage seems to be just a problem with my system configuration (slackware64-current with multilb).
I tried to reproduce it with another distribution (xubuntu11.10 amd64) and it doesn't occur.

Thus remains only the issue with the error which cannot be shown in the dialog.

Revision history for this message
Mathias Brodala (mathbr) wrote :

Errors are displayed in the main window for quite a while, your suggestion was applied with r3986 however.

Changed in exaile:
assignee: nobody → Mathias Brodala (mathbr)
importance: Undecided → Medium
milestone: none → 0.3.3.0
status: New → Fix Committed
Changed in exaile:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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