[Gpe-bugs] [Bug 14] New: event_flush calls gpe_error_box on error

bugzilla-daemon at linuxtogo.org bugzilla-daemon at linuxtogo.org
Tue Jan 9 20:48:35 CET 2007


http://bugs.linuxtogo.org/show_bug.cgi?id=14

           Summary: event_flush calls gpe_error_box on error
           Product: libeventdb
           Version: 0.30
          Platform: Nokia 770
        OS/Version: Linux
            Status: NEW
          Severity: minor
          Priority: P4
         Component: default
        AssignedTo: gpe-bugs at linuxtogo.org
        ReportedBy: g+gpe at cobb.uk.net
   Estimated Hours: 0.0


If event_flush gets an error it automatically calls gpe_error_box.

Unfortunately, if the application does not have a window (for example gpesyncd)
this produces many strange and very confusing errors:

gpesyncd[1346]: GLIB CRITICAL ** Gtk - gtk_settings_get_for_screen: assertion
`GDK_IS_SCREEN (screen)' failed
gpesyncd[1346]: GLIB CRITICAL ** GLib-GObject - g_object_get: assertion
`G_IS_OBJECT (object)' failed
gpesyncd[1346]: GLIB WARNING ** GLib-GObject - value "TRUE" of type `gboolean'
is invalid or out of range for property `visible' of type `gboolean'
gpesyncd[1346]: GLIB WARNING ** Gtk - Screen for GtkWindow not set; you must
always set
a screen for a GtkWindow before using the window
gpesyncd[1346]: GLIB CRITICAL ** Gdk - gdk_pango_context_get_for_screen:
assertion `GDK_IS_SCREEN (screen)' failed
gpesyncd[1346]: GLIB CRITICAL ** Pango - pango_context_set_base_dir: assertion
`context != NULL' failed
gpesyncd[1346]: GLIB CRITICAL ** Pango - pango_context_set_font_description:
assertion `context != NULL' failed
gpesyncd[1346]: GLIB CRITICAL ** Pango - pango_context_set_language: assertion
`context != NULL' failed
gpesyncd[1346]: GLIB CRITICAL ** Pango - pango_layout_new: assertion `context
!= NULL' failed
gpesyncd[1346]: GLIB CRITICAL ** Pango - pango_layout_set_text: assertion
`layout != NULL' failed
gpesyncd[1346]: GLIB CRITICAL ** Pango - pango_layout_set_attributes: assertion
`layout != NULL' failed
gpesyncd[1346]: GLIB CRITICAL ** Pango - pango_layout_set_alignment: assertion
`layout != NULL' failed
gpesyncd[1346]: GLIB CRITICAL ** Pango - pango_layout_set_ellipsize: assertion
`PANGO_IS_LAYOUT (layout)' failed
gpesyncd[1346]: GLIB CRITICAL ** Pango -
pango_layout_set_single_paragraph_mode: assertion `PANGO_IS_LAYOUT (layout)'
failed
gpesyncd[1346]: GLIB CRITICAL ** Pango - pango_layout_set_width: assertion
`layout != NULL' failed
gpesyncd[1346]: GLIB CRITICAL ** Pango - pango_layout_get_extents: assertion
`layout != NULL' failed
gpesyncd[1346]: GLIB CRITICAL ** Gtk - gtk_icon_theme_get_for_screen: assertion
`GDK_IS_SCREEN (screen)' failed
gpesyncd[1346]: GLIB CRITICAL ** Gtk - gtk_settings_get_for_screen: assertion
`GDK_IS_SCREEN (screen)' failed
gpesyncd[1346]: GLIB CRITICAL ** Gtk - gtk_icon_size_lookup_for_settings:
assertion `GTK_IS_SETTINGS (settings)' failed
gpesyncd[1346]: GLIB WARNING ** Gtk - Invalid icon size 6
gpesyncd[1346]: GLIB CRITICAL ** Gtk - gtk_icon_theme_load_icon: assertion
`GTK_IS_ICON_THEME (icon_theme)' failed
Segmentation fault

It would be nice if the call to gpe_error_box could be supressed (or
gpe_error_box takes no action) if the application does not have a window.


-- 
Configure bugmail: http://bugs.linuxtogo.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Gpe-bugs mailing list