Description of problem:
Started thunderbird. It seems to relate to the lightning plugin. I clicked on the lighting calender tab and
the thunderbird window expands to a huge width, the right hand side probably 10000 pixels away.
Next there was some flickering, around the redering of the tabs. Xorg crashed.
My thunderbird account is old, 10-15 years. I note it says for thunderbird lightning is now built into, but I cannot find this.
If I uninstall the lightning, google provider add-ons, and there are no calender available.
So I continue to install the plugin.
Version-Release number of selected component:
cmdline: /usr/libexec/Xorg -background none :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch
pkg_fingerprint: 73BD E983 81B4 6521
pkg_vendor: Fedora Project
runlevel: N 5
Thread no. 1 (10 frames)
#9 glamor_set_destination_pixmap_fbo at glamor_pixmap.c:72
#10 glamor_set_destination_drawable at glamor_transform.c:97
#11 glamor_poly_fill_rect_gl at glamor_rects.c:118
#12 glamor_poly_fill_rect at glamor_rects.c:163
#13 damagePolyFillRect at damage.c:1194
#14 miPaintWindow at miexpose.c:540
#15 miWindowExposures at miexpose.c:394
#16 xf86XVWindowExposures at xf86xv.c:1062
#17 miHandleValidateExposures at miwindow.c:226
#18 miResizeWindow at miwindow.c:613
Created attachment 1245820 [details]
Created attachment 1245821 [details]
Created attachment 1245822 [details]
Created attachment 1245823 [details]
Created attachment 1245824 [details]
Created attachment 1245825 [details]
Created attachment 1245826 [details]
Created attachment 1245827 [details]
Created attachment 1245828 [details]
Created attachment 1245829 [details]
Created attachment 1245830 [details]
Created attachment 1245831 [details]
(In reply to igiwatson from comment #0)
> Description of problem:
> Started thunderbird. It seems to relate to the lightning plugin. I clicked
> on the lighting calender tab and
> the thunderbird window expands to a huge width, the right hand side probably
> 10000 pixels away.
Actually 32767 pixels:
glamor_set_destination_pixmap_fbo (glamor_priv=<optimized out>, fbo=0x0, x0=0, y0=0, width=32767, height=1119) at glamor_pixmap.c:72
So I reckon this is client error, not Xorg nor glamor at fault here, the client expands its window to a size larger than supported.
But the client should not be able to crash the Xserver so easily...
I tried to reproduce using Xwayland from server-1.19-branch but it works, no matter the window size I throw at it (using Xephyr -glamor).
Then I noticed this is reported against F24 and xserver-1.18, there are a number of fixes in glamor between server-1.18-branch and server-1.19-branch, including commit de959ec "glamor: Handle GL_OUT_OF_MEMORY when allocating texture images" which might avoid this issue.
Can you reproduce using Xwayland 1.19.1 with Fedora 25?
Having upgrade to FC25, I ran the following command, hopefully what you are after.
Xephyr -glamor -screen 300x32768 :1
Xephyr -glamor -screen 32768x300 :1
(EE) 0: Xephyr (OsLookupColor+0x139) [0x5b34b9]
(EE) 1: /lib64/libpthread.so.0 (__restore_rt+0x0) [0x7f33c04645bf]
(EE) 2: Xephyr (glamor_get_pixmap_texture+0x30) [0x440250]
(EE) 3: Xephyr (OsVendorInit+0x2c26) [0x430936]
(EE) 4: Xephyr (_start+0x1548) [0x42a1f8]
(EE) 5: Xephyr (InitFonts+0x2c5) [0x467bf5]
(EE) 6: /lib64/libc.so.6 (__libc_start_main+0xf1) [0x7f33c00ab401]
(EE) 7: Xephyr (_start+0x2a) [0x42782a]
(EE) 8: ? (?+0x2a) [0x2a]
(EE) Segmentation fault at address 0x0
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
Aborted (core dumped)
Reported as Bug 1431633.
glamor from, xorg-x11-server-Xorg-1.19.1-3.fc25.x86_64.
I tried repeating the original issue with thunderbird, lightning & provider plugin's, but with out success.
I did try creating large windows with python+Gtk3, but Gdk spots the window sizes and limits the requests.
NOTE: I am using KDE/plasma spin so I am not sure that wayland is being used here.
kf5-kwayland is installed, but not kwin-wayland.
/var/log still has an active Xorg.0.log file.
journalctl --since=today, has no wayland comments in it.
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.