Banshee crashes very frequently

Bug #1041661 reported by Nazar Mokrynskyi
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
banshee (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Banshee crashes on start, on track changing, on setting rating of the track, on removing track from the library.
Crashes are random, but it is very easy to repeat them, but once on every 30-40 starts it stops crashing and may work without crashes whole day, mystic behaviour.
Output of banshee runned in debug mode in attachment.
---
ApportVersion: 2.5.1-0ubuntu2
Architecture: amd64
DistroRelease: Ubuntu 12.10
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
Package: banshee 2.4.1-3ubuntu2
PackageArchitecture: amd64
ProcEnviron:
 LANGUAGE=ru_UA:ru
 TERM=xterm
 PATH=(custom, no user)
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
Tags: quantal running-unity
Uname: Linux 3.6.0-rc2-bulldozer-xen-pci x86_64
UpgradeStatus: Upgraded to quantal on 2012-06-28 (58 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote :
tags: added: apport-collected running-unity
description: updated
Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote : Dependencies.txt

apport information

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in banshee (Ubuntu):
status: New → Confirmed
Revision history for this message
Nazar Mokrynskyi (nazar-pc) wrote :

Now (version 2.6.0) it works much more stable.
But sometimes at the end of song banshee just closes without any notification.

Revision history for this message
Chow Loong Jin (hyperair) wrote : Re: [Bug 1041661] Re: Banshee crashes very frequently

On 10/10/2012 06:09, Nazar Mokrynskyi wrote:
> Now (version 2.6.0) it works much more stable.
> But sometimes at the end of song banshee just closes without any notification.
>

Could you upload the ~/.config/banshee-1/log file before restarting Banshee the
next time it crashes like this?

  status incomplete

--
Kind regards,
Loong Jin

Changed in banshee (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for banshee (Ubuntu) because there has been no activity for 60 days.]

Changed in banshee (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :

Nazar Mokrynskyi reported "Banshee crashes on start, on track changing, on setting rating of the track, on removing track from the library."
 For me, it's more often just random, either between songs or in the middle of one. But it's frequent, e.g. 5 times per hour in steady use.

I'm attaching the log from after a crash.

Changed in banshee (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Christopher Barrington-Leigh (cpbl) wrote :

... continued:

By the way, I'm using the latest Banshee updates on Ubuntu 14.04.

I think 5 times per hour is an underestimate of the actual crash rate.
If I start banshee from a terminal, I get similar crash output to that in the log file, but including

[Warn 22:57:23.115] Caught an exception - System.Xml.XmlException: a name did not start with a legal character 32 ( ) Line 7, position 23. (in `System.Xml')
  at Mono.Xml2.XmlTextReader.ReadName (System.String& prefix, System.String& localName) [0x00000] in <filename unknown>:0
  at Mono.Xml2.XmlTextReader.ReadName () [0x00000] in <filename unknown>:0
  at Mono.Xml2.XmlTextReader.ReadEntityReference (Boolean ignoreEntityReferences) [0x00000] in <filename unknown>:0
  at Mono.Xml2.XmlTextReader.ReadReference (Boolean ignoreEntityReferences) [0x00000] in <filename unknown>:0
  at Mono.Xml2.XmlTextReader.ReadText (Boolean notWhitespace) [0x00000] in <filename unknown>:0
  at Mono.Xml2.XmlTextReader.ReadContent () [0x00000] in <filename unknown>:0
  at Mono.Xml2.XmlTextReader.Read () [0x00000] in <filename unknown>:0
  at System.Xml.XmlTextReader.Read () [0x00000] in <filename unknown>:0
  at System.Xml.XmlDocument.ReadNodeCore (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
  at System.Xml.XmlDocument.ReadNodeCore (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
  at System.Xml.XmlDocument.ReadNodeCore (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
  at System.Xml.XmlDocument.ReadNodeCore (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
  at System.Xml.XmlDocument.ReadNode (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
  at System.Xml.XmlDocument.Load (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
  at System.Xml.XmlDocument.LoadXml (System.String xml) [0x00000] in <filename unknown>:0
  at Migo.Syndication.RssParser..ctor (System.String url, System.String xml) [0x00000] in <filename unknown>:0
[Warn 22:57:23.115] Caught an exception - System.FormatException: Invalid XML document. (in `Migo')
  at Migo.Syndication.RssParser..ctor (System.String url, System.String xml) [0x00000] in <filename unknown>:0
  at Migo.Syndication.FeedUpdateTask.OnDownloadDataReceived (System.Object sender, Migo.Net.DownloadStringCompletedEventArgs args) [0x00000] in <filename unknown>:0

[1]+ Segmentation fault (core dumped) banshee

Revision history for this message
Chow Loong Jin (hyperair) wrote :

On Mon, Mar 02, 2015 at 11:24:04AM -0000, Christopher Barrington-Leigh wrote:
> ... continued:
>
> By the way, I'm using the latest Banshee updates on Ubuntu 14.04.
>
> I think 5 times per hour is an underestimate of the actual crash rate.
> If I start banshee from a terminal, I get similar crash output to that in the log file, but including
>
>
> [Warn 22:57:23.115] Caught an exception - System.Xml.XmlException: a name did not start with a legal character 32 ( ) Line 7, position 23. (in `System.Xml')
> at Mono.Xml2.XmlTextReader.ReadName (System.String& prefix, System.String& localName) [0x00000] in <filename unknown>:0
> at Mono.Xml2.XmlTextReader.ReadName () [0x00000] in <filename unknown>:0
> at Mono.Xml2.XmlTextReader.ReadEntityReference (Boolean ignoreEntityReferences) [0x00000] in <filename unknown>:0
> at Mono.Xml2.XmlTextReader.ReadReference (Boolean ignoreEntityReferences) [0x00000] in <filename unknown>:0
> at Mono.Xml2.XmlTextReader.ReadText (Boolean notWhitespace) [0x00000] in <filename unknown>:0
> at Mono.Xml2.XmlTextReader.ReadContent () [0x00000] in <filename unknown>:0
> at Mono.Xml2.XmlTextReader.Read () [0x00000] in <filename unknown>:0
> at System.Xml.XmlTextReader.Read () [0x00000] in <filename unknown>:0
> at System.Xml.XmlDocument.ReadNodeCore (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
> at System.Xml.XmlDocument.ReadNodeCore (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
> at System.Xml.XmlDocument.ReadNodeCore (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
> at System.Xml.XmlDocument.ReadNodeCore (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
> at System.Xml.XmlDocument.ReadNode (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
> at System.Xml.XmlDocument.Load (System.Xml.XmlReader reader) [0x00000] in <filename unknown>:0
> at System.Xml.XmlDocument.LoadXml (System.String xml) [0x00000] in <filename unknown>:0
> at Migo.Syndication.RssParser..ctor (System.String url, System.String xml) [0x00000] in <filename unknown>:0
> [Warn 22:57:23.115] Caught an exception - System.FormatException: Invalid XML document. (in `Migo')
> at Migo.Syndication.RssParser..ctor (System.String url, System.String xml) [0x00000] in <filename unknown>:0
> at Migo.Syndication.FeedUpdateTask.OnDownloadDataReceived (System.Object sender, Migo.Net.DownloadStringCompletedEventArgs args) [0x00000] in <filename unknown>:0

Yours looks like it's caused by a broken RSS feed. Could you file a new bug with
this backtrace and the full output of banshee --debug please? That output should
show which podcast Banshee is having trouble parsing.

--
Kind regards,
Loong Jin

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.