GNOME Bugzilla – Bug 97233
Maildir format for in box (mutliple Maildir)
Last modified: 2009-08-15 18:40:50 UTC
Package: balsa Severity: major Version: 2.0.3 Synopsis: Maildir format for in box (mutliple Maildir) Bugzilla-Product: balsa Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.0.5) Description: Description of Problem: I'd like to use the Maildir format for my inbox outbox and so on. So I created this with the maildirmake from qmail and I could use that. I also createt multiple Maildir mailboxes in the base directory and sometimes in a subdirectory of the base directory. Steps to reproduce the problem: First, delete the mail directory of balsa and delete the balsa entry in ${HOME]/.gnome2 rm ${HOME)/.gnome2/balsa rm -r mail 1. mkdir mail cd mail /var/qmail/bin/maildirmake inbox same for outbox, trash, draftbox and sentbox. 2. create some more mailboxes in Maildir format in this folder and subfolder. mkdir ${HOME}/mail/FreeBSD cd ${HOME]/mail/FreeBSD /var/qmail/bin/maildirmake questions same for gnome ports misc stable mkdir ${HOME}/mail/Private cd ${HOME}/mail/Private /var/qmail/bin/maildirmake Anna and a view others... I can send you my whole tree if you want... most of them are empty by now, a fiew boxes have some content. 3. Start Balsa use standard configuration, exept the inbox in step 2 I think must be modified. Actual Results: The tree of the mailboxes does not work correctly and balsa crashes there sometimes... The mailboxtree doesn't show all the mailboxes, sometimes on mouse over the mailboxes apear, and then they disapear again, mostly nothing happends. By chance I could open any other mailbox like ${HOME}/mail/Jugend/KD. But balsa crashes often. Expected Results: That should work correctly. How often does this happen? I can click and click and click and after a view times balsa crashes. So it happens every time if I want. Additional Information: Debugging Information: Backtrace was generated from '/usr/X11R6/bin/balsa' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x29094b44 in __sys_poll () from /usr/lib/libc_r.so.4
+ Trace 29640
------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-10-30 11:22 ------- The original reporter (martin.klaffenboeck@gmx.at) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, pawsa@theochem.kth.se.
I could not duplicate this. I started Balsa with no config file, used the Druid to designate an existing maildir mailbox (~/mail/something) as the Inbox, and it all worked. However, I didn't use qmail tools to make the maildir boxes--I used Balsa's file->new->maildir tool. Does the qmail tool do something different? Balsa creates directories `path', 'path/new', `path/cur', and `path/tmp', which are all otherwise empty. Can you provide some OS info?
I build my balsa again with -g (debugging) and now I can see something when I'm running balsa within gdb, and there I can see something: (gdb) bt
+ Trace 29650
sorry, I couln't get a balsa.core file, I don't know why... I'm using FreeBSD. Why doesn't the gnome2 bugzilla get all this informatinon? FreeBSD 4.7 (yesterday) Martin
could you try with balsa-1.4 and see what happens ? I'm not sure if this is a backend or frontend bug
with balsa 1.4 its running ok, and faster... ;-) But I'd like to use 2.x because of the look of gnome2... Martin
tkx, that means it's a frontend bug.
The stack seems to be trashed. I don't see how a call to balsa_mblist_get_type can be sandwiched in those gtk_tree_* calls. What was the event that gave you back the gdb prompt?
Sorry, I'm not that familar with gdb that I know now what you really mean. I'll paste here the last output of my gdb, could be that that is what you want to know? Otherwise, please tell me ... last output: (balsa:26415): Gtk-CRITICAL **: file gtktreestore.c: line 645 (gtk_tree_store_iter_next): assertion `iter->user_data != NULL' failed (balsa:26415): Gtk-CRITICAL **: file gtktreeview.c: line 3077 (gtk_tree_view_bin_expose): assertion `has_next' failed. There is a disparity between the internal view of the GtkTreeView, and the GtkTreeModel. This generally means that the model has changed without letting the view know. Any display from now on is likely to be incorrect. (balsa:26415): Gtk-CRITICAL **: file gtktreestore.c: line 619 (gtk_tree_store_get_value): assertion `iter->stamp == GTK_TREE_STORE (tree_model)->stamp' failed (balsa:26415): GLib-GObject-CRITICAL **: file gobject.c: line 989 (g_object_set_property): assertion `G_IS_VALUE (value)' failed (balsa:26415): GLib-GObject-CRITICAL **: file gvalue.c: line 147 (g_value_unset): assertion `G_IS_VALUE (value)' failed (balsa:26415): Gtk-CRITICAL **: file gtktreestore.c: line 619 (gtk_tree_store_get_value): assertion `iter->stamp == GTK_TREE_STORE (tree_model)->stamp' failed (balsa:26415): GLib-GObject-CRITICAL **: file gobject.c: line 989 (g_object_set_property): assertion `G_IS_VALUE (value)' failed (balsa:26415): GLib-GObject-CRITICAL **: file gvalue.c: line 147 (g_value_unset): assertion `G_IS_VALUE (value)' failed (balsa:26415): Gtk-CRITICAL **: file gtktreestore.c: line 619 (gtk_tree_store_get_value): assertion `iter->stamp == GTK_TREE_STORE (tree_model)->stamp' failed (balsa:26415): GLib-GObject-CRITICAL **: file gobject.c: line 989 (g_object_set_property): assertion `G_IS_VALUE (value)' failed (balsa:26415): GLib-GObject-CRITICAL **: file gvalue.c: line 147 (g_value_unset): assertion `G_IS_VALUE (value)' failed (balsa:26415): Gtk-CRITICAL **: file gtktreestore.c: line 619 (gtk_tree_store_get_value): assertion `iter->stamp == GTK_TREE_STORE (tree_model)->stamp' failed (balsa:26415): GLib-GObject-CRITICAL **: file gobject.c: line 989 (g_object_set_property): assertion `G_IS_VALUE (value)' failed (balsa:26415): GLib-GObject-CRITICAL **: file gvalue.c: line 147 (g_value_unset): assertion `G_IS_VALUE (value)' failed (balsa:26415): Gtk-CRITICAL **: file gtktreestore.c: line 619 (gtk_tree_store_get_value): assertion `iter->stamp == GTK_TREE_STORE (tree_model)->stamp' failed (balsa:26415): GLib-GObject-WARNING **: gtype.c:2835:g_type_value_table_peek(): type id `0' is invalid (balsa:26415): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x289b5bb5 in gtk_tree_model_get_valist () from /usr/X11R6/lib/libgtk-x11-2.0.so.0 (gdb)
Yes, that helps a lot--clearly, something bad happened internal to GtkTree* stuff! One more test, if you could: in gdb, start Balsa with `run --g-fatal-warnings', and trigger the errors. You should get the gdb prompt when the first of those `Gtk-CRITICAL's is emitted: please get the stack trace (`bt', or `info stack'), and post it.
Oh, I guessed, it would have to do with GtkTree. With --g-fatal-warnings I just get: (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGABRT, Aborted. 0x2907c530 in kill () from /usr/lib/libc_r.so.4 (gdb) bt
+ Trace 29661
I hope I did everything correct here... Martin
Yes, it looks as though you did everything correctly...but this wasn't the stack I expected! Have you been getting other GtkCRITICAL messages? This one seems to derive from some other problem completely. I know this seems to go on for ever, but...could you start Balsa the same way, and just `continue' (`c') past these messages until you see the one from gtk_tree_store_iter_next? *That's* the stack that might help debug Balsa!
(gdb) c Continuing. Program exited with code 01. (gdb) And there come the Message to send a Bug Report. I think, that doesn't help?
You're right! I'm stumped...and with no FreeBSD setup to test on, I don't see any way forward. You might want to post to balsa-list@gnome.org to see if other FreeBSD-ers have any suggestions.
Created attachment 12115 [details] Schreenshot of balsa-1.4.3
Created attachment 12116 [details] Screenshot of balsa-2.0.3
I add a view screenshots, mabye that helps? On Balsa-2.0.3 the things in the Tree change when I roll my mouse over the items... Martin
Maybe you can have a look at this again. I'll submit my Maildir hirarchie in a shell script (just run it by 'sh filename' and you will get my maildir hirarchie under the ${USER}/mail if your there). Maybe you can try to open that hirarchy with balsa. Please make sure to compare the result hirarchy from Balsa with the structure on your hard disk. Martin
Created attachment 12403 [details] A Shell Archive of my Maildir Hirarchy.
Martin: have you looked at the bugs that are shown as dependencies? Bug #93629 looks quite similar.
Still cannot reproduce it. BTW, can you try configure --disable-threads and get a stack trace then?
It works now. I build with --disable-thread and it worked, so I tryed to enable it again and it also worked. I don't know why. Mabe the gtk2 libraries are updatet on freebsd and caused balsa to work. Thanks... Martin
How can I close this?
I apologize for the spam, but in talking to David Kennedy on #bugs we decided that it might be useful for me to add a comment to a lot of bugs that have nearly identical stack traces that aren't very useful. (It took me a while because I gave up on several bugzilla queries that simply hung). Anyway, I may have caught some bugs with this query that aren't relevant, so I apologize again if this bug is one of those. If not: The following comment from 100709 may be relevant: "It turns out this was an accidental FreeBSD ABI change during the import of gcc-3.2.1. div(), a structure returning function, was the culprit."
balsa-2.0.10 relased.