app_indicator_new() just calls g_object_new and there is no special constructor set in AppIndicator, so it will only fails in OOM condition which we usually do not check for. Sure there is a bug somewhere in indicator-application, but it does not make sense to check for something which is always valid and will not prevent that bug from happen.
>From the stacktrace it is obvious that the AppIndicator instance is not NULL: dbus_g_connection_register_g_object (connection=0x8438d0c, check_connect (self=0x840e000) app_indicator_set_menu (self=0x840e000, menu=0x845caf0) -- Support Application Indicators https://bugs.launchpad.net/bugs/497870 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
