Description of problem: I moved an e-mail from one IMAP folder to another on the same server. Version-Release number of selected component: claws-mail-3.9.0-1.fc18 Additional info: backtrace_rating: 4 cmdline: claws-mail crash_function: ___fprintf_chk executable: /usr/bin/claws-mail kernel: 3.8.1-201.fc18.x86_64 uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 ___fprintf_chk at fprintf_chk.c:31 #1 fprintf at /usr/include/bits/stdio2.h:97 #2 newmail_hook at newmail.c:60 #3 hooks_marshal at hooks.c:108 #5 g_hook_list_marshal at ghook.c:676 #6 hooks_invoke at hooks.c:126 #7 do_copy_msgs at folder.c:3622 #8 folder_item_move_msgs at folder.c:3675 #9 procmsg_move_messages at procmsg.c:346 #10 summary_execute_move at summaryview.c:5115 Potential duplicate: bug 710107
Created attachment 706082 [details] File: backtrace
Created attachment 706083 [details] File: build_ids
Created attachment 706084 [details] File: cgroup
Created attachment 706085 [details] File: core_backtrace
Created attachment 706086 [details] File: dso_list
Created attachment 706087 [details] File: environ
Created attachment 706088 [details] File: limits
Created attachment 706089 [details] File: maps
Created attachment 706090 [details] File: open_fds
Created attachment 706091 [details] File: proc_pid_status
Created attachment 706092 [details] File: var_log_messages
It crashed in the NewMail plugin due to a NULL file ptr given to fprintf: #0 ___fprintf_chk (fp=0x0, ... And indeed, it's a duplicate of bug 710107 but there are no steps on how to reproduce it yet. If you start Claws Mail in a terminal, do you get any warning/error/messages from the NewMail plugin?
When I try to enable the NewMail plugin, I do get a popup box that says: The following error occurred while loading newmail.so : No such file or directory Also, when I start Claws, I get a different popup that says: The following plugin failed to load. Check the Plugins configuration for more information: NewMail Terminal output looks like this: $ claws-mail Newmail plugin unloaded ** (claws-mail:8454): WARNING **: plugin loading error: No such file or directory ** (claws-mail:8454): WARNING **: Trying to register gtype 'GtkCMUnit' as enum when in fact it is of type 'gint' sys:1: Warning: g_variant_unref: assertion `value->ref_count > 0' failed
Puzzling. According to the backtrace it _was_ loaded, 0x00007fee27338d40 0x00007fee27339248 Yes /usr/lib64/claws-mail/plugins/newmail.so and it had registered itself via the mail_postfiltering_hooklist, too: #2 newmail_hook (source=0x1b7dd80, data=<optimized out>) at newmail.c:60 The plugin file is located in /usr/lib64/claws-mail/plugins, which is the default location the "Plugins" dialog opens: $ rpm -ql claws-mail-plugins-newmail|grep lib /usr/lib64/claws-mail/plugins/newmail.so > $ claws-mail > Newmail plugin unloaded That's odd, too. If enabled, it would say "Newmail plugin loaded" for the first time when starting Claws Mail, and it would print the log file name, too. Could you attach the output of "grep -i newmail ~/.claws-mail/clawsrc"?
> ** (claws-mail:8454): WARNING **: plugin loading error: No such file or directory That one is interesting, too. It has run into a problem in ~/.claws-mail/clawsrc in one of the [Plugins_Foo] sections (with "Foo" out of "Common", "GTK", "GTK2" and so on.
Created attachment 706213 [details] clawsrc I re-enabled the NewMail plugin, and then looked at the clawrc file, and I noticed that it's in the Plugins_Common section.
One thing I've tried after lunch: $ unset HOME $ claws-mail Newmail plugin unloaded ** (claws-mail:7491): WARNING **: plugin loading error: No such file or directory Additionally, the "Plugins" dialog then says: | | Error: No such file or directory | Plugin is not functional. Trying to "Load" it nevertheless, I get an error dialog: |The following error occurred while loading newmail.so : | | No such file or directory Why did I try "unset HOME"? Because newmail.c relies on getenv("HOME"), and during plugin init it would unload the plugin on error. Assumably, it failed to getenv HOME and subsequently generated a bad file name for the log file. (void)snprintf (name, 256, "%s/Mail/NewLog", getenv ("HOME")); That doesn't explain the crash yet. Unless it could happen that it failed to unregister its hook method (although it _tries_ to do that during plugin unloading). Hmmm...
I'm happy enough to just remove the newmail plugin from my system for now. Hopefully that will resolve the issue. Thanks for such prompt service, you definitely stand out from the crowd!
корявый модуль backtrace_rating: 4 Package: claws-mail-3.9.0-1.fc18 Architecture: i686 OS Release: Fedora release 18 (Spherical Cow)
For the fprintf NULL ptr crash, upstream has committed an obvious safety-check only: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2885#c9
The remaining part is in bug 896696.