Bug 3514 - Claws Mail version 3.12.0
Summary: Claws Mail version 3.12.0
Status: RESOLVED INVALID
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Other (show other bugs)
Version: 3.12.0
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2015-09-05 10:28 UTC by bommel
Modified: 2015-09-05 20:05 UTC (History)
0 users

See Also:


Attachments

Description bommel 2015-09-05 10:28:53 UTC
GTK+ version 2.24.28 / GLib 2.44.1
Locale: de_DE.UTF-8 (charset: UTF-8)
Features: IPv6 iconv compface GnuTLS LDAP GNU/aspell libetpan libSM
Operating system: Linux 4.1.6-1-ARCH (x86_64)
C Library: GNU libc 2.22
Comment 1 bommel 2015-09-05 14:17:26 UTC
Claws-Mail Process (832) received Signal 11
Comment 2 bommel 2015-09-05 14:23:27 UTC
Claws-Mail Process(899) or (1187) received Signal 11
Comment 4 bommel 2015-09-05 18:24:24 UTC
How to reproduce:

1. Open Claws-Mail
2. Do something or nothing
3. Close Claws-Mail 
4. Then Claws-Mail shows the message:
GTK+ version 2.24.28 / GLib 2.44.1
Locale: de_DE.UTF-8 (charset: UTF-8)
Features: IPv6 iconv compface GnuTLS LDAP GNU/aspell libetpan libSM
Operating system: Linux 4.1.6-1-ARCH (x86_64)
C Library: GNU libc 2.22

When I start Claws-Mail per console the output is:

claws.c:102:Starting Claws Mail version Claws Mail 3.12.0
utils.c:1900:using default rc_dir /home/user/.claws-mail
main.c:2174:Using control socket /tmp/claws-mail-1000/58c107d390fa69c187b12327b2ba0270
main.c:2238:Opening socket /tmp/claws-mail-1000/58c107d390fa69c187b12327b2ba0270
main.c:769:runtime GTK+ 2.24.28 / GLib 2.44.1
main.c:777:buildtime GTK+ 2.24.28 / GLib 2.44.1
main.c:786:Compiled-in features:
main.c:791: compface
main.c:797: Enchant
main.c:803: GnuTLS
main.c:809: IPv6
main.c:815: iconv
main.c:827: LDAP
main.c:833: libetpan 1.6
main.c:839: libSM
main.c:845: NetworkManager
prefs_gtk.c:1037:new file '/home/user/.claws-mail/clawsrc'
prefs_gtk.c:996:new section 'Common'
prefs_gtk.c:996:new section 'Plugins_Common'
prefs_gtk.c:996:new section 'Plugins_GTK2'
prefs_gtk.c:996:new section 'Bogofilter'
prefs_gtk.c:1037:new file '/home/user/.claws-mail/folderitemrc'
prefs_gtk.c:996:new section '#imap/INBOX'
prefs_gtk.c:996:new section '#imap/INBOX/Trash'
prefs_gtk.c:996:new section '#imap/INBOX/Junk'
prefs_gtk.c:996:new section '#imap/INBOX/Junk Folder'
prefs_gtk.c:996:new section '#imap/INBOX/Sent'
prefs_gtk.c:996:new section '#imap/INBOX/User'
prefs_gtk.c:1037:new file '/home/user/.claws-mail/accountrc'
prefs_gtk.c:996:new section 'Account: 1'
prefs_gtk.c:996:new section 'Account: 2'
prefs_gtk.c:85:Reading configuration...
claws-mail: Fatal IO error 11 (Ressource is not available) on X server :0.0.


So Claws-Mail doesn't terminate correctly. 

Build-Date of Claws-Mail: 19th July 2015. See also: https://www.archlinux.de/?page=PackageDetails;repo=extra;arch=x86_64;pkgname=claws-mail

I don't know whether this bug also appears on other platforms.

I am using ARCHLINUX with MATE 1.10.2 as Desktop.

The problem also appears when no mailbox exists and no other applications are started.
Comment 5 Andrej Kacian 2015-09-05 19:32:38 UTC
That debug output doesn't look like it's from when Claws Mail is exiting, but rather from when it is starting. You say the crash happens when you close it.
Comment 6 bommel 2015-09-05 19:55:59 UTC
When I start Claws-Mail the console is empty. The output comes first when I close Claws-Mail.

I think you are correct. So the important line is 

claws-mail: Fatal IO error 11 (Ressource is not available) on X server :0.0.

Maybe the problem comes from X11 or MATE? Possibly GTK? It seems that it is not a problem of Claws-Mail. I can't offer more information about this phenomenon. Does Claws-Mail have any other Logs? Maybe a log file? 

You can close this report if you think that it isn't a problem of Claws-Mail.
Comment 7 bommel 2015-09-05 20:05:02 UTC
It seems that it is not really a problem of claws mail. See

https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/999191

and

https://bbs.archlinux.org/viewtopic.php?id=200797

Thanks for your help.

Note You need to log in before you can comment on or make changes to this bug.