After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 629447 - banshee crashes with assertation failure in 10.10 beta
banshee crashes with assertation failure in 10.10 beta
Status: RESOLVED FIXED
Product: banshee
Classification: Other
Component: general
1.7.5
Other Linux
: High critical
: 1.x
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-09-12 18:31 UTC by Chow Loong Jin
Modified: 2010-11-02 18:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
bugreport created by bug-buddy (18.17 KB, text/plain)
2010-09-13 11:20 UTC, terri.bugs
Details

Description Chow Loong Jin 2010-09-12 18:31:26 UTC
Originally reported at:
  https://bugs.launchpad.net/bugs/636403

Binary package hint: banshee

In 10.10 beta Banshee 1.7.5 crashes with assertation failure after starting the program. Apport appears and when you choose to report the problem apport takes a few moments and then tells you that the problem cannot be reported because reporting assertation failures is not supported (or something similar). I'll include the log file I found in /home/user/.config/banshee-1/log in case it is of some use.
Comment 1 Felipe Besoaín Pino 2010-09-13 00:13:47 UTC
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 terri.bugs 2010-09-13 11:20:26 UTC
Created attachment 170134 [details]
bugreport created by bug-buddy
Comment 3 terri.bugs 2010-09-13 11:24:25 UTC
I'm not sure if that crash (from which the bug report was generated) was due to assertation failure as this time apport didn't launch at all. And the first time it was apport that told me that it was assertation failure. However, I hope that crash report helps. If you need another crash I can try to produce one.
Comment 4 David Nielsen 2010-09-13 15:48:25 UTC
Thank you for the report.

It appears that you are getting permission denied errors and file not found errors. While this could be handled more gracefully this isn't on the face a Banshee issue as we simply can't access the files in question.

However the log on launchpad does not appear to be complete and does not run in debug mode.

Can you reproduce the problem when running:

banshee-1 --debug --redirect-log

Then the log should be in ~/.config/banshee-1/log

If banshee hangs instructions for correctly obtaining the information we need can be found on http://banshee.fm/contribute/file-bugs
Comment 5 terri.bugs 2010-09-14 13:08:24 UTC
I haven't been able to reproduce the problem with

banshee-1 --debug --redirect-log

in a way that Apport would pop up and tell me that crash was due to assertation failure, I can get the application to hang, but that's completely different bug. The original crash may have been caused by some bizarre chain of event's that I am not able to recreate. 

BTW, should banshee scan all available usb devices for music & videos after it starts up, even when the extension for library watcher is not enabled? Or is this a bug that should be reported?
Comment 6 David Nielsen 2010-09-14 13:16:20 UTC
Since you say you can't reproduce the assertion bug I am closing this. As for scanning the system I believe that is intended behavior (as I recall presently that is an Ubuntu specific change). Thank you for the report, feel free to reopen this if it happens again or open a new bug for any additional issues you may encounter.
Comment 7 Chow Loong Jin 2010-11-02 18:23:32 UTC
Seems to have been fixed in 1.8.0, apparently.