Re: bugreport: segfault after editing filetypes
- From: tpgww@xxxxxxxxxxx
- To: emelfm2@xxxxxxxxxxxxx
- Date: Wed, 8 Mar 2006 22:53:14 -0500
On Tue, 7 Mar 2006 13:34:13 +0100
Atman Sense <mattenklicker@xxxxxxx> wrote:
> Edit a new filetype, associate a command to it, and press ok. If you
> want to edit the file-type again:
>
> (emelfm2:15940): Gtk-CRITICAL **: gtk_tree_store_set: assertion
> `VALID_ITER (ite r, tree_store)' failed
>
> (emelfm2:15940): Gtk-CRITICAL **: gtk_list_store_set: assertion
> `iter->stamp == list_store->stamp' failed
> Speicherzugriffsfehler
>
> emelfm2: emelfm2-tom-20060216
> Build platform: GTK+ 2.8.8 Linux 2.6.15-gentoo-r1/i686
> gcc-Version 3.4.5
A mal-formed data structure is highly likely to be the cause of your problem.
Creating a new filetype from scratch requires some care, you must replicate the
tree structure seen for existing categories. It is safest (and probably
easiest) to copy an existing one, paste it where you want, then change the
details.
Otherwise, you need to add the new category, 2 children (in english, labelled
"extensions" and "commands"), >= 1 "grand-child" for each child, for the
extension-child(ren) optional color strings, and for the command-child(ren),
values for menu label and the actual command - all in the correct tree
relationship.
Regards
Tom
--
Users can unsubscribe from the list by sending email to
emelfm2-request@xxxxxxxxxxxxx with 'unsubscribe' in the subject field or by
logging into the web interface.
- References:
- bugreport: segfault after editing filetypes
- From: Atman Sense
Other related posts:
- » bugreport: segfault after editing filetypes
- » Re: bugreport: segfault after editing filetypes
- bugreport: segfault after editing filetypes
- From: Atman Sense