After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 736069 - Evolution window content not drawn
Evolution window content not drawn
Status: RESOLVED INCOMPLETE
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2014-09-04 16:16 UTC by Paul Menzel
Modified: 2018-09-18 13:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Blank window with red button (6.07 KB, image/png)
2014-09-17 22:03 UTC, Paul Menzel
Details
Blank window without red button (5.18 KB, image/png)
2014-09-17 22:05 UTC, Paul Menzel
Details

Description Paul Menzel 2014-09-04 16:16:50 UTC
With Evolution 3.12.2 and 3.12.5 I experienced that suddently the Evolution window as not drawn anymore. Only the red stop button showed sometimes. There is nothing in the Linux kernel logs. Evolution-Data-Server seems to run fine in the background and the notification of new messages are shown.

Pressing Ctrl + n or something else does not have any effect. I first thought it was a Radeon driver problem, reported as bug 81239 in the freedesktop.org Bugzilla [1], but owen in #gtk+@irc.gnome.org told me that is very unlikely and looks more like an Evolution problem with WebKitGTK+. So I am creating a new ticket here and closing it in the fdo bug tracker.

Unfortunately I am *not* able to reproduce it reliably.

Here is the backtrace with Evolution 3.12.2.




[1] https://bugs.freedesktop.org/show_bug.cgi?id=81239
Comment 1 Paul Menzel 2014-09-17 22:02:41 UTC
Today I was able to reproduce it with Evolution 3.12.6. I’ll attach two screenshots captured with GIMP.
Comment 2 Paul Menzel 2014-09-17 22:03:20 UTC
Created attachment 286424 [details]
Blank window with red button
Comment 3 Paul Menzel 2014-09-17 22:05:10 UTC
Created attachment 286425 [details]
Blank window without red button

The red button is the only thing that appears after some seconds.

The message area is normally filled with the image of the virtual desktop I was before, that means is not redrawn.

Messages are still received as I get the notifications about new messages.
Comment 4 Paul Menzel 2014-09-18 10:17:51 UTC
It happened again, when closing the preference window. The preference window border was still show. Here is the backtrace.


Comment 5 Paul Menzel 2014-09-18 10:20:41 UTC
Michael, could you please check the last backtrace again to verify that it is unrelated to the Radeon driver? That’d be awesome.
Comment 6 Michel Dänzer 2014-09-22 09:47:07 UTC
I don't see anything directly pointing to the Radeon drivers.

radeon_drm_cs_emit_ioctl is a helper thread routine for submitting OpenGL command streams to the kernel radeon driver. Since no other thread is waiting in any OpenGL related code AFAICT, it seems unlikely that the problem is OpenGL related. Unless maybe one of the poll()s is waiting for activity from the X11 display file descriptor?
Comment 7 Paul Menzel 2014-09-23 07:29:57 UTC
(In reply to comment #6)

[…]

> Unless maybe one of the poll()s is waiting for activity from the X11 display
> file descriptor?

Is there a way to check that next time I experience this problem?
Comment 8 Milan Crha 2015-03-04 16:41:06 UTC
Thanks for a bug report. I do not see anything odd in the backtraces, just usual threads, most of them from your IMAPx accounts, but none really stuck. Even the main thread is not stuck, which means the drawing should be fine.

The webkitgtk part in evolution is only with the message preview (and other view's previews), otherwise the webkitgtk is not used (it'll be also used in the message composer in 3.16.0).

I do not know what to do with this within evolution itself. I can give you a little application with only gtk and webkitgtk being involved, but you can probably use devhelp the same, to test whether you can reproduce the issue out of evolution.
Comment 9 Milan Crha 2018-09-18 13:09:25 UTC
I'm closing this, because it had been a long time since the last comment and because many things changed meanwhile, in the drivers, in Evolution (most notably port from webkit1gtk to webkit2gtk) and in webkitgtk+ itself as well.