Description of problem: If you change the background at regular intervals in any way (with a script, with Wallpapoz, Variety etc ...) it happens that every now and then any new open window is black and any work background appears black. If you do ALT F2 and you restart the shell, unsolvable problem occurs and you have to logout. If you from Terminal-gnome-shell--replace you notice that the Windows are borderless and from Terminal is an error of ' segmentation fault. Note that this problem is much less frequent replacing nautilus with nemo. Today for example was completed a full cycle of 18 images without problems, then arrived at the second image the problem has re-tabled Version-Release number of selected component: gnome-shell-3.10.4-1.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: intel_miptree_attach_map executable: /usr/bin/gnome-shell kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 intel_miptree_attach_map at intel_mipmap_tree.c:869 #1 old_intel_miptree_map at intel_mipmap_tree.c:910 #2 intel_map_renderbuffer at intel_fbo.c:129 #3 map_attachment at swrast/s_renderbuffer.c:578 #4 _swrast_map_renderbuffers at swrast/s_renderbuffer.c:652 #5 _swrast_render_start at swrast/s_context.c:895 #6 _swsetup_RenderStart at swrast_setup/ss_context.c:202 #7 run_render at tnl/t_vb_render.c:276 #8 _tnl_run_pipeline at tnl/t_pipeline.c:163 #9 intelRunPipeline at intel_tris.c:1097
Created attachment 876969 [details] File: backtrace
Created attachment 876970 [details] File: cgroup
Created attachment 876971 [details] File: core_backtrace
Created attachment 876972 [details] File: dso_list
Created attachment 876973 [details] File: environ
Created attachment 876974 [details] File: exploitable
Created attachment 876975 [details] File: limits
Created attachment 876976 [details] File: maps
Created attachment 876977 [details] File: open_fds
Created attachment 876978 [details] File: proc_pid_status
Created attachment 876979 [details] File: var_log_messages
Good morning. Until now I failed to understand what could be the problem of ' black boxes '. I also tried to uninstall the vesa driver and do a downgrade to xorg.I have however discovered a precedent that may help understand the possible causes (I also tried to change bios settings about memory, but inconclusive): as it is located at 15897p 3 and http://forum.fedoraonline.it/viewtopic.php?id, in English, this: http://www.nvnews.net/vbulletin/showthread.php?t 162959. Have a nice day. Avvcivil
Here's what I just found out from the Terminal (output of glxgears): Running synchronized to the vertical refresh. The framerate should beapproximately the same as the monitor refresh rate. 303 frames in 5.0 seconds 60,509 FPS301 frames in 5.0 seconds 60,051 FPSXIO: fatal IO error 11 (Resource temporarily unavailable) on X server ': 0.0 ' after 2550 requests (2550 known processed) with 0 events remaining. How can you solve? Depends on the use of dedicated video card rather than integrated? If Yes, do I have to change bios settings? Thanks a lot. Avvcivil
Good morning. I note that it may be this bug: https://bugzilla.redhat.com/show_bug.cgi?id 949058. Maybe the background automatic transmission facilitates the occurrence of the problem, but is not the cause. Avvcivil lscpi: 'lspci' [andrea@HP ~]$ lspci 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM Controller (rev 02) 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express Integrated Graphics Controller (rev 02) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 02) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 02) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 02) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 02) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 02) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 02) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 02) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 02) 00:1d.3 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 02) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 02) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) 00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface Controller (rev 02) 00:1f.2 IDE interface: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port SATA Controller [IDE mode] (rev 02) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 02) 00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA Controller [IDE mode] (rev 02) 01:00.0 Network controller: Ralink corp. RT2561/RT61 rev B 802.11g 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
(In reply to Avvocato Andrea Marengoni from comment #14) > Good morning. I note that it may be this bug: > https://bugzilla.redhat.com/show_bug.cgi?id 949058. Maybe the background > automatic transmission facilitates the occurrence of the problem, but is not > the cause. Avvcivil > > lscpi: > 'lspci' > [andrea@HP ~]$ lspci > 00:00.0 Host bridge: Intel Corporation 82G33/G31/P35/P31 Express DRAM > Controller (rev 02) > 00:02.0 VGA compatible controller: Intel Corporation 82G33/G31 Express > Integrated Graphics Controller (rev 02) > 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #4 (rev 02) > 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #5 (rev 02) > 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI > Controller #2 (rev 02) > 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio > Controller (rev 02) > 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port > 1 (rev 02) > 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port > 3 (rev 02) > 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #1 (rev 02) > 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #2 (rev 02) > 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #3 (rev 02) > 00:1d.3 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI > Controller #6 (rev 02) > 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI > Controller #1 (rev 02) > 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92) > 00:1f.0 ISA bridge: Intel Corporation 82801IR (ICH9R) LPC Interface > Controller (rev 02) > 00:1f.2 IDE interface: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 4 port > SATA Controller [IDE mode] (rev 02) > 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev > 02) > 00:1f.5 IDE interface: Intel Corporation 82801I (ICH9 Family) 2 port SATA > Controller [IDE mode] (rev 02) > 01:00.0 Network controller: Ralink corp. RT2561/RT61 rev B 802.11g > 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
(In reply to Avvocato Andrea Marengoni from comment #13) > Here's what I just found out from the Terminal (output of glxgears): Running > synchronized to the vertical refresh. The framerate should beapproximately > the same as the monitor refresh rate. 303 frames in 5.0 seconds 60,509 > FPS301 frames in 5.0 seconds 60,051 FPSXIO: fatal IO error 11 (Resource > temporarily unavailable) on X server ': 0.0 ' after 2550 requests (2550 > known processed) with 0 events remaining. How can you solve? Depends on the > use of dedicated video card rather than integrated? If Yes, do I have to > change bios settings? Thanks a lot. Avvcivil I apologize for this comment not relevant. I understand that the Terminal signaled simply when you close the window. I think the message today can be much more useful in finding the cause of the problem, how to link to previous bug made available. Good job, and in any case congratulations to Fedora which is really excellent and I am sure will improve again with Fedora Next!!! With many cordial greetings. Avvcivil
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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' of '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed.