Created attachment 2664
After the latest Xorg update to xorg-server 18.104.22.1681 either the X session or
the X server is killed when a program is started. It's not possible to run any
This happens with several Xfwm themes. I've tested it with the theme "Elegant
and with another theme I can't remember.
After changing the line
<property name="theme" type="string" value="Elegant Brit"/>
<property name="theme" type="string" value="Default"/>
in the file ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfwm4.xml it's working
I've attached slim.log which contains the relevant error messages in the xorg
I don't know if this bug is in Xorg, GTK, Xfwm or in the themes. So I first
report it here. I already posted a comment for "Elegant Brit".
If the X server crashes after upgrading the X server, why do you consider this as a bug in xfwm4? It's a bug in the X server unless proven otherwise.
Fatal server error:
exaGetPixmapFirstPixel called for invalid bpp 1
This is a bug in the ~X server
For ref. the issue has been reported here previously:
Could you please provide the info requested in this bugzilla (seems the original poster cannot help with investigations)
Bug already found. ;-)
I attached the slim.log. As soon as I know how to make a gdb backtrace I'll do it.
Can you tell me how I can do this? I have to admit that I don't know how to use gdb.
*** Bug 6672 has been marked as a duplicate of this bug. ***
(In reply to comment #5)
> Bug already found. ;-)
> I attached the slim.log. As soon as I know how to make a gdb backtrace I'll do
> Can you tell me how I can do this? I have to admit that I don't know how to use
Did you check this page, it may contain some helpful hints on how to get the gdb backtrace:
(In reply to comment #7)
> Did you check this page, it may contain some helpful hints on how to get the
> gdb backtrace:
Thanks for the link. The problem is that I still haven't got a second machine for doing this backtrace. As soon as I get one, I'll do this backtrace if it's still needed after your backtrace.
(In reply to comment #8)
> Thanks for the link. The problem is that I still haven't got a second machine
> for doing this backtrace. As soon as I get one, I'll do this backtrace if it's
> still needed after your backtrace.
No worries, I did it, posted in the bugzilla upstream, a patch is available thansk to Michel, I tested and it works for me.
Looks like it's fixed, that was a 5 min job really :-)
Well, it wasn't a matter of time for running the debugger, it was a matter of missing requirements. ;-)