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 656991 - Banshee.exe crashed with SIGABRT in raise()
Banshee.exe crashed with SIGABRT in raise()
Status: RESOLVED WONTFIX
Product: banshee
Classification: Other
Component: general
2.1.0
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2011-08-21 03:07 UTC by Chow Loong Jin
Modified: 2020-03-17 09:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Log of Banshee hanging (38.09 KB, text/plain)
2011-08-21 03:07 UTC, Chow Loong Jin
Details

Description Chow Loong Jin 2011-08-21 03:07:39 UTC
Created attachment 194318 [details]
Log of Banshee hanging

Originally reported at:
  https://bugs.launchpad.net/bugs/830041

Banshee is periodically crashing consuming upwards of 350 % of the CPU as indicated by running top via command line.   This occurs quite often bringing the OS to a crawl.  I am often running killall banshee to restore my performance.

Judging by the stack trace near the bottom, this could be related to gconf, or the lack thereof, since I believe Ubuntu Oneiric's switching to dconf.
Comment 1 Andrés G. Aragoneses (IRC: knocte) 2011-08-21 09:26:21 UTC
If there is no GConf, the configure script should have complained I think (or be configured as if you chose the --disable-gnome flag). Can you post your configuration summary?
Comment 2 Chow Loong Jin 2011-08-21 12:46:04 UTC
  Build Environment
    Install Prefix:        /usr
    Datadir:               /usr/share
    Libdir:                /usr/lib

    C Compiler:            gcc
    Mono C# Compiler:      /usr/bin/mono-csc -define:RELEASE
    Mono Runtime:          /usr/bin/mono
    Gtk#:                  2

  Video/Graphics:
    Graphics System:       X11
    X11 Video:             yes
    Clutter:               no

  Operating System/Desktop Environment:
    GNOME Support:         yes
    OSX Support:           no
    MeeGo Support:         yes

  Digital Audio Player (DAP) Support:
    Apple Device:          yes (libgpod-sharp)
    Karma:                 no
    Mass Storage:          yes
    MTP:                   yes

  Extra Features:
    Web Browser:           yes (webkit-1.0 >= 1.2.2, libsoup-2.4 >= 2.26)
      + GNOME Proxy        yes (libsoup-gnome-2.4 >= 2.26)
    Boo Scripting:         no
    DAAP:                  yes
    GIO Backend:           yes (glib >= 2.22, gtk-sharp-beans, and gio-sharp)
    GIO Hardware:          yes (gudev-sharp, gkeyfile-sharp)
    YouTube:               yes (gdata-sharp >= 1.4)
    Sound Menu:            yes
    Ubuntu One Store:      yes (ubuntuone-sharp >= 0.3.2)

  Build/Development:
    Unit Tests:            no (nunit >= 2.4.7)
    API Docs:              yes (monodocer and mdassembler)
    User Help:             yes (gnome-doc-utils >= 0.17.3)
    Release Build:         yes
    Vendor Build ID:       Ubuntu oneiric (development branch)

Full output found here: https://launchpadlibrarian.net/75104460/buildlog_ubuntu-oneiric-amd64.banshee_2.1.0-1ubuntu5_BUILDING.txt.gz

On the other hand, I believe the build process only checks for libgconf + gconftool-2, but does not require gconfd to run. Aren't the errors in the log due to gconfd not running?
Comment 3 André Klapper 2020-03-17 09:26:16 UTC
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather transfer the project
to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the
responsibility for active development again.
See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.