Description of problem: this abrt notification appear immediately after rebooting and loging to X session (xfce4). Additional info: WARNING: at drivers/gpu/drm/i915/intel_display.c:3882 intel_modeset_check_state+0x4b8/0x620 [i915]() Hardware name: P5E-VM HDMI wrong connector dpms state Modules linked in: rfcomm bnep bluetooth rfkill fuse bridge stp llc be2iscsi iscsi_boot_sysfs bnx2i cnic uio cxgb4i cxgb4 cxgb3i cxgb3 mdio libcxgbi ib_iser rdma_cm ib_addr iw_cm ib_cm ib_sa ib_mad ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi snd_usb_audio snd_usbmidi_lib snd_rawmidi gspca_ov519 gspca_main videodev media coretemp i2c_i801 iTCO_wdt iTCO_vendor_support snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_seq snd_seq_device snd_pcm snd_page_alloc snd_timer snd soundcore 8139too e1000e lpc_ich atl1 mfd_core mii asus_atk0110 microcode serio_raw vhost_net nfsd auth_rpcgss nfs_acl tun macvtap macvlan kvm_intel lockd kvm sunrpc uinput binfmt_misc ata_generic pata_acpi i915 video i2c_algo_bit firewire_ohci drm_kms_helper firewire_core crc_itu_t drm pata_jmicron i2c_core Pid: 998, comm: X Not tainted 3.8.1-201.fc18.i686.PAE #1 Call Trace: [<c044d862>] warn_slowpath_common+0x72/0xa0 [<f8654bd8>] ? intel_modeset_check_state+0x4b8/0x620 [i915] [<f8654bd8>] ? intel_modeset_check_state+0x4b8/0x620 [i915] [<c044d933>] warn_slowpath_fmt+0x33/0x40 [<f8654bd8>] intel_modeset_check_state+0x4b8/0x620 [i915] [<f8651b91>] ? intel_crtc_disable+0x81/0x110 [i915] [<f8655528>] intel_set_mode+0x788/0x9d0 [i915] [<c0584e5e>] ? __find_get_block+0xbe/0x1d0 [<f8655dbe>] intel_crtc_set_config+0x64e/0x880 [i915] [<f83d0e7c>] drm_framebuffer_remove+0x9c/0x110 [drm] [<f83d43a9>] drm_mode_rmfb+0x99/0xb0 [drm] [<f83d4310>] ? drm_mode_addfb2+0x750/0x750 [drm] [<f83c5d62>] drm_ioctl+0x422/0x480 [drm] [<f83d4310>] ? drm_mode_addfb2+0x750/0x750 [drm] [<c052f743>] ? handle_pte_fault+0x93/0xad0 [<c054b82b>] ? kmem_cache_free+0x1ab/0x1b0 [<c056bed8>] ? __d_free+0x38/0x60 [<c0530314>] ? handle_mm_fault+0x114/0x190 [<f83c5940>] ? drm_copy_field+0x80/0x80 [drm] [<c056970a>] do_vfs_ioctl+0x7a/0x590 [<c0637f0a>] ? inode_has_perm.isra.31.constprop.62+0x3a/0x50 [<c0639580>] ? file_has_perm+0xa0/0xb0 [<c045f515>] ? __set_task_blocked+0x35/0x80 [<c04614d3>] ? __set_current_blocked+0x33/0x50 [<c0639998>] ? selinux_file_ioctl+0x48/0xe0 [<c0569c8b>] sys_ioctl+0x6b/0x80 [<c09a070d>] sysenter_do_call+0x12/0x28
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.