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 656202 - Banshee doesn't start
Banshee doesn't start
Status: RESOLVED DUPLICATE of bug 656203
Product: banshee
Classification: Other
Component: general
2.0.0
Other Windows
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-08-09 10:17 UTC by Erez Segal
Modified: 2011-08-09 10:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Erez Segal 2011-08-09 10:17:41 UTC
I've downloaded the windows version and tried to start Banshee.
Nothing happens.
I've monitored the Task Manager and seen Nereid.exe shows up for a brief second and disappear again.
I've tried repairing the installation but it had no effect (which makes sense because the fresh, first, installation had the same problem too).
I've tried running Munishee.exe instead of Nereid.exe (not sure what it is, actually) and got the output below.

Also a window popped up reporting "Encountered a Fatal Error"
Extension node not found path /Banshee/ServiceManager/Service


C:\PROGRA~1\Banshee\bin>Muinshee.exe
Logging to C:\Documents and Settings\Erez Segal\Application Data\banshee-1\log

(Muinshee:3864): Gtk-CRITICAL **: gtk_window_resize: assertion `width > 0' faile
d

(Muinshee:3864): Gtk-WARNING **: Error parsing gtk-icon-sizes string:
        'gtk-menu=16,16:gtk-small-toolbar=22,22:gtk-large-toolbar=22,22:gtk-butt
on=16,16:gtk-dnd=22,22:gtk-dialog:32,32'

(Muinshee:3864): Gdk-CRITICAL **: gdk_property_change: assertion `window != NULL
' failed

(Muinshee:3864): Gdk-CRITICAL **: gdk_property_change: assertion `window != NULL
' failed

(Muinshee:3864): Gdk-CRITICAL **: gdk_property_change: assertion `window != NULL
' failed

C:\PROGRA~1\Banshee\bin>
Comment 1 Akhil Laddha 2011-08-09 10:55:06 UTC

*** This bug has been marked as a duplicate of bug 656203 ***