I took a look at my xtrace log again, and I noticed that in the run-up
to the BadMatch error, I see several (harmless) BadWindow errors from
requests to the xsplash window. This suggests that the xsplash window no
longer exists:
000:<:065c: 24: Request(20): GetProperty delete=false(0x00) window=0x00400004
property=0x11d("WM_STATE") type=0x11d("WM_STATE") long-offset=0x00000000
long-length=0x00000000
000:>:65c:Error 3=Window: major=0, minor=20, bad=4194308
----
000:<:065e: 8: Request(15): QueryTree window=0x00400004
000:>:65e:Error 3=Window: major=0, minor=15, bad=4194308
Sure enough, when I look a bit further up in the log-file, gnome-
settings-daemon saw a DestroyNotify for the parent window of xsplash:
000:>:0658: Event UnmapNotify(18) event=0x000000fc window=0x01a00032
from-configure=false(0x00)
000:>:0658: Event DestroyNotify(17) event=0x000000fc window=0x01a00032
So, I wonder if the BadMatch is because some other process created a new
window, and it has the same ID as the previously destroyed xsplash
window?
--
gnome-settings-daemon crashed with signal 5 in xkl_process_error()
https://bugs.launchpad.net/bugs/321041
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
