Summary: | Evolution window content not shown fully (only desktop background) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Paul Menzel <paulepanter> | ||||||||
Component: | DRM/Radeon | Assignee: | Default DRI bug account <dri-devel> | ||||||||
Status: | RESOLVED NOTOURBUG | QA Contact: | |||||||||
Severity: | normal | ||||||||||
Priority: | medium | CC: | paulepanter | ||||||||
Version: | XOrg git | ||||||||||
Hardware: | Other | ||||||||||
OS: | All | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Paul Menzel
2014-07-11 16:23:25 UTC
Please attach the Xorg.0.log file and the output of dmesg and glxinfo. Can you attach a screenshot or photo of the problem? Are you using GNOME or another desktop environment? Is compositing enabled? (In reply to comment #1) > Please attach the Xorg.0.log file and the output of dmesg and glxinfo. Unfortunately I was not able to reproduce this issue again. For being clear, it just happened once in the last two or three months. I’ll attach the files from a working system. > Can you attach a screenshot or photo of the problem? As I was not able to reproduce it again, I do not have a picture. I’ll take one next time it happens. > Are you using GNOME or another desktop environment? I am using awesome 3.4.15. > Is compositing enabled? How do I check that? Created attachment 102822 [details]
/var/log/Xorg.0.log (without problem)
`/var/log/Xorg.0.log` without the Evolution hang. (Linux kernel was upgraded in between.)
Created attachment 102823 [details]
`glxinfo` output
From a run without the problem.
mesa-utils 8.2.0-1
(In reply to comment #2) > (In reply to comment #1) > > Please attach the Xorg.0.log file and the output of dmesg and glxinfo. > > Unfortunately I was not able to reproduce this issue again. For being clear, > it just happened once in the last two or three months. Ugh, that makes it hard to do anything about the problem, or even confirm that it's fixed... > I am using awesome 3.4.15. AFAICT awesome doesn't support compositing itself, so unless you're explicitly running a separate compositing manager, you're probably not using compositing. So, assuming the problem is that the evolution process hangs, http://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=c4ae0e2cbcc0e2ebf9f13ee92d59b5120254a1dc might help. Or it might not be related to the graphics stack at all. Created attachment 102825 [details]
dmesg (with problem)
Copied messages from `/var/log/kern.log.1` and deleted the parts from the beginning.
$ sed -i 's/[^[]*//' /tmp/dmesg
(In reply to comment #6) > dmesg (with problem) Which lines of that dmesg output correspond to the problem? (In reply to comment #7) > (In reply to comment #6) > > dmesg (with problem) > > Which lines of that dmesg output correspond to the problem? I think there are no lines corresponding to the problem. If my notes are correct it happened between 1835.004463 and 5487.777677. Unfortunately there are no Radeon message in that period. I think I hit the same problem again today with Evolution 3.12.5, GTK+ 3.12.2-3+b1 and xserver-xorg-video-radeon 1:7.4.0-2. $ sudo perf top […] 7,22% libglib-2.0.so.0.4000.0 [.] g_main_context_prepare 5,71% libglib-2.0.so.0.4000.0 [.] 0x00090a0c 4,84% libglib-2.0.so.0.4000.0 [.] g_main_context_check […] The user owen in #gtk+@irc.gnome.org told me that it is probably not a driver problem but an Evolution/WebKitGTK/GTK+ problem. Thank you for all the help. I created ticket 736069 [1] in the GNOME Bugzilla bug tracker. [1] https://bugzilla.gnome.org/show_bug.cgi?id=736069 |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.