This bug was reported on Ubuntu Launchpad as:
when doing something with firefox i switched from one tab to another and xfwm was lost for 5 sec and then came back
DistroRelease: Ubuntu 10.04
Package: xfwm4 4.6.1-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 184.108.40.206+drm33.2
Uname: Linux 2.6.32-22-generic i686
*__GI___poll (fds=0x440ff4, nfds=4, timeout=9)
IA__g_poll (fds=0x98c2f88, nfds=4, timeout=9)
(polkit-gnome-authentication-agent-1:1218): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
(Pidgin:1200): libnotify-CRITICAL **: notify_get_server_caps: assertion `proxy != NULL' failed
(nm-applet:1214): libnotify-CRITICAL **: notify_get_server_caps: assertion `proxy != NULL' failed
Unfortunately, the stacktrace shows no trace of xfwm4 code at all, just gtk+
Could you please provide either a core file of the binary (unstripped) or a way to reproduce?
Could be related to the gtk+ engine used, does that occur with other theme/engine as well?
maybe its here?
couse LP bug report gives info that its the latest version.
> maybe its here?
> couse LP bug report gives info that its the latest version.
Unfortunately not, that's the package for Ubuntu, the core file is an image of the process' memory when it crashed, this is not something that can be provided by the distribution.
Beside, I am not using Ubuntu so this won't help.
There was a more detailed stacktrace here: https://launchpadlibrarian.net/52081640/Stacktrace.txt
(but again, the crash doesn't occur in xfwm4 code…)