Whenever the mail editor window closes, the whole application crashes

[Lyon Lemmens]

After the upgrade to kubuntu 12.04, this bug popped up.

Claws starts OK. I can edit a mail, but as soon as I close the window (either by saving the mail as draft, sending it, or just clicking the window closed), the whole application crashes. The mail itself is saved in the draft or outbox, depending on how I close the window.

Other windows, like the preference windows don't have the same issue.

There's no useful info in the .xsession-errors file:

The program 'claws-mail' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 114367 error_code 3 request_code 155 minor_code 3)

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: claws-mail 3.8.0-1ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu6
Architecture: amd64
Date: Fri Apr 27 17:39:27 2012
InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011)
ProcEnviron:
 LANGUAGE=en_US:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: claws-mail
UpgradeStatus: Upgraded to precise on 2012-04-27 (0 days ago)

[Ron (ron-f1)]

can confirm the Bug

The program 'claws-mail' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 77601 error_code 3 request_code 152 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

[Lyon Lemmens (lugdunum)]

gdb backtrace attached

[Antony King (ant-0)]

Just a 'me too' on this bug - this is what I got after starting claws-mail and sending myself an email:

ron@sklaptop:~$ claws-mail
194 + 23 < 1024
194 + 46 < 1024
194 + 69 < 1024
The program 'claws-mail' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 54349 error_code 3 request_code 151 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error()
   function.)

This is on Kubuntu 12.04. uname gives:

Linux sklaptop 3.2.0-24-generic #37-Ubuntu SMP Wed Apr 25 08:43:52 UTC 2012 i686 i686 i386 GNU/Linux

it's an Atom 330 cpu. Was working fine before the recent upgrade from 11.10 .

[Edza Niknais (edza)]

Same here with kubuntu after upgrade to 12.04. When i send mail, open prefences and then close that dialog - claws mail crashes.

[Antony King (ant-0)]

i wonder if its related to this ssl bug? My mail sends encrypted iirc (on a different box right now so can't check)

https://bugs.archlinux.org/task/29390

[Edza Niknais (edza)]

mine uses ssl for smtp too

[Colin Leroy-Mira (colin-colino)]

This may be, according to the gdb backtrace, a theme problem. Can you try with other themes that don't use the Oxygen engine ?

Thanks

[Edza Niknais (edza)]

the same with cleanlooks, so i think it`s not theme

[Colin Leroy-Mira (colin-colino)]

Can you attach a gdb backtrace when crashing with Cleanlooks ?

Thanks

[Edza Niknais (edza)]

.xsession-errors:

10:00:16.560 DEBUG unknown "OK"
The program 'claws-mail' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 21962 error_code 3 request_code 155 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

now learning how to use gdb :)

[Edza Niknais (edza)]

(gdb) run
Starting program: /usr/bin/claws-mail
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[New Thread 0xb7dcfb40 (LWP 10481)]
[New Thread 0xb73ffb40 (LWP 10482)]
[New Thread 0xb294eb40 (LWP 10483)]
The program 'claws-mail' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 13798 error_code 3 request_code 155 minor_code 3)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[Thread 0xb294eb40 (LWP 10483) exited]
[Thread 0xb73ffb40 (LWP 10482) exited]
[Thread 0xb7dcfb40 (LWP 10481) exited]
[Inferior 1 (process 10478) exited with code 01]

[Antony King (ant-0)]

Running claws in gdb gave aspell as the last thing that it touched before crashing. Disabling aspell in the claws config didn't help though. running in gdb and trying to get a backtrace resulted in 'no stack' - that was using --sync --debug and 'break gdk_x_error' so not sure what's happening there.

Installing E17 (apt-get install e17) and logging in using that as the desktop shell instead of KDE resulted in claws-mail working perfectly; no unexpected termination.

[Antony King (ant-0)]

Found a work-around:

Back in KDE, I used the system settings tool to change the toolkit used by GTK+ apps from Oxygen-gtk to Raleigh. That has stopped the crashing problem, and is a reasonable workaround from my point of view. For googlers, that setting is in Application appearance/GTK+ appearance in the KDE system settings tool (I searched for GTK and it was the only thing that popped up).

[Edza Niknais (edza)]

For me it`s crashing with Raleigh too or restart/relogin needed?

[Colin Leroy-Mira (colin-colino)]

Hi Edza,

I don't know, maybe you face another bug. I would need a gdb backtrace to know what your crash is with Raleigh. You need to install the libgtk2.0-0-dbg package, then run the following :

$ gdb claws-mail
(gdb) break gdk_x_error
(gdb) run --sync
[...] make it crash
(gdb) backtrace full

HTH !

[Andrew Simpson (andrew-simpson)]

This looks to be related to a bug reported - and fixed - in Fedora and KDE in the oxygen gtk2-engine

https://bugzilla.redhat.com/show_bug.cgi?id=804790 See comment 11 for fix.

https://bugs.kde.org/show_bug.cgi?id=295875

[Andrew Simpson (andrew-simpson)]

Add gtk2-engines-oxygen since upstream bug reports indicate this is the cause.

[Edza Niknais (edza)]

Thanks Andrew Simpson - https://launchpad.net/ubuntu/+source/gtk2-engines-oxygen/1.2.3-0ubuntu1/+build/3467448 fixed crash error

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Andrew Simpson (andrew-simpson)]

Update for gtk2-engines-oxygen appeared on my machine today (1.2.2-0ubuntu1). After downloading and installing the bug is fixed.