On 02/02/2013 06:45 AM, Dale wrote: > walt wrote: >> On 02/01/2013 11:50 PM, Dale wrote: >>> Howdy, >>> >>> I use Gtkam to get pics from my Canon camera. I already put up with the >>> fact that it crashes a LOT.
>> I always start by running the problem program from a bash prompt so I can >> look for error messages. > > I get this: > > (gtkam:10897): Gtk-WARNING **: Unable to locate theme engine in > module_path: "clearlooks", clearlooks is the name of a gnome theme, and so you wouldn't have it on your kde machine. You can ignore that and other gtk "warnings". > (gtkam:10897): Gtk-CRITICAL **: > gtk_file_chooser_default_set_current_name: assertion `impl->action == > GTK_FILE_CHOOSER_ACTION_SAVE || impl->action == > GTK_FILE_CHOOSER_ACTION_CREATE_FOLDER' failed Now that one looks suspicious. The only idea that comes to mind is that gtkam for some reason is trying to save to some place you don't have write privileges, like / or /run, maybe. That's where I would trot out strace, which will allow you to see exactly where gtkam is trying to write when it fails. The other trick I use is to create a new user with a new home directory and try running gtkam from that account. Often I find that the new user doesn't see the same bug as my normal user, so at least I know the problem is somewhere in my home directory, and strace will narrow the scope of my debugging even more. The "-y" and "-e file" flags for strace are very handy for this kind of debugging problem.
