[Gpe-list] Gpe-bugs Digest, Vol 3, Issue 3

Wed Jan 10 12:01:22 CET 2007

Send Gpe-bugs mailing list submissions to
	gpe-bugs at linuxtogo.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/gpe-bugs
or, via email, send a message with subject or body 'help' to
	gpe-bugs-request at linuxtogo.org

You can reach the person managing the list at
	gpe-bugs-owner at linuxtogo.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gpe-bugs digest..."

Today's Topics:

   1. [Bug 14] New: event_flush calls gpe_error_box on error
      (bugzilla-daemon at linuxtogo.org)
   2. [Bug 15] New: Closing event DB causes fatal error
      (bugzilla-daemon at linuxtogo.org)
   3. [Bug 16] New: Need an About Box (bugzilla-daemon at linuxtogo.org)

----------------------------------------------------------------------

Message: 1
Date: Tue, 09 Jan 2007 20:48:35 +0100
From: bugzilla-daemon at linuxtogo.org
Subject: [Gpe-bugs] [Bug 14] New: event_flush calls gpe_error_box on
	error
To: gpe-bugs at linuxtogo.org
Message-ID: <bug-14-7 at http.bugs.linuxtogo.org/>

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.

------------------------------

Message: 2
Date: Wed, 10 Jan 2007 00:11:42 +0100
From: bugzilla-daemon at linuxtogo.org
Subject: [Gpe-bugs] [Bug 15] New: Closing event DB causes fatal error
To: gpe-bugs at linuxtogo.org
Message-ID: <bug-15-7 at http.bugs.linuxtogo.org/>

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

           Summary: Closing event DB causes fatal error
           Product: libeventdb
           Version: 0.30
          Platform: Nokia 770
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P4
         Component: default
        AssignedTo: gpe-bugs at linuxtogo.org
        ReportedBy: g+gpe at cobb.uk.net
   Estimated Hours: 0.0

In gpesyncd I open the event DB using event_db_new(filespec). At the end, I
close the event DB by doing a g_object_unref on the object that event_db_new
gave me.

However, if I have written anything to the database, the g_object_unref causes
the following error:

gpesyncd[1479]: GLIB CRITICAL ** default - event_flush: library routine called
out of sequence

Following the execution using gdb, what is happening is that the g_object_unref
causes sqlite_db_finalize to be called, which THEN calls event_db_finalize. 
However, event_db_finalize needds to do an event_flush on the cached events,
which involves writing to the database.  Sqlite rejects these (presumably as
sqlite_db_finalize has already been called) with the "out of sequence" error.

In principle this could be causing data loss (as cached events are not being
flushed).  However, the events do seem to be in the database, so it just causes
the annoying error.

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

------------------------------

Message: 3
Date: Wed, 10 Jan 2007 00:36:03 +0100
From: bugzilla-daemon at linuxtogo.org
Subject: [Gpe-bugs] [Bug 16] New: Need an About Box
To: gpe-bugs at linuxtogo.org
Message-ID: <bug-16-7 at http.bugs.linuxtogo.org/>

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

           Summary: Need an About Box
           Product: gpe-contacts
           Version: 0.46
          Platform: Nokia 770
        OS/Version: Linux
            Status: NEW
          Severity: enhancement
          Priority: P4
         Component: default
        AssignedTo: gpe-bugs at linuxtogo.org
        ReportedBy: doc.evans at gmail.com
   Estimated Hours: 0.0

This should really be filed against all the GPE components, but I'm filing it
just against contacts, since that's the one I use most.

There seems to be no way to discover exactly which release of a component one
is running. (For example, bugzilla is telling me that I'm filing this against
version 0.46, but I have no way to know whether that is the version I'm
running.)

So there should be some sort of "About" screen that at the very least tells the
user the version number of the application. Other items such as the place to
file bugs might also usefully be included on the same screen.

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

------------------------------

_______________________________________________
Gpe-bugs mailing list
Gpe-bugs at linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/gpe-bugs

End of Gpe-bugs Digest, Vol 3, Issue 3
**************************************