Description of problem: SELinux is preventing gnome-shell from 'read' accesses on the lnk_file /var/lib/dbus/machine-id. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that gnome-shell should be allowed read access on the machine-id lnk_file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell # semodule -X 300 -i my-gnomeshell.pp Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:system_dbusd_var_lib_t:s0 Target Objects /var/lib/dbus/machine-id [ lnk_file ] Source gnome-shell Source Path gnome-shell Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-259.fc26.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.11.8-300.fc26.x86_64 #1 SMP Thu Jun 29 20:09:48 UTC 2017 x86_64 x86_64 Alert Count 5 First Seen 2017-07-02 01:15:33 CEST Last Seen 2017-07-02 01:15:37 CEST Local ID 4fedb138-9b36-4529-a477-2e33dd54e650 Raw Audit Messages type=AVC msg=audit(1498950937.406:208): avc: denied { read } for pid=1241 comm="ibus-x11" name="machine-id" dev="dm-2" ino=393325 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:system_dbusd_var_lib_t:s0 tclass=lnk_file permissive=0 Hash: gnome-shell,xdm_t,system_dbusd_var_lib_t,lnk_file,read Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: component: selinux-policy reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.8-300.fc26.x86_64 type: libreport
F25 is affected too: type=AVC msg=audit(1499284147.609:185): avc: denied { read } for pid=1301 comm="gnome-shell" name="machine-id" dev="dm-2" ino=1704189 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:system_dbusd_var_lib_t:s0 tclass=lnk_file permissive=0
Description of problem: el único problema que tengo es del botón del touchpad que debería activar y desactivar. gracias por su atencion. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.8-300.fc26.x86_64 type: libreport
*** Bug 1468407 has been marked as a duplicate of this bug. ***
*** Bug 1467085 has been marked as a duplicate of this bug. ***
*** Bug 1467407 has been marked as a duplicate of this bug. ***
Description of problem: Message issued every time I boot. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: Reproduce on Dell latititude e5430. 1. start laptop in ac mode 2. unplug power to battery 3. Replug ac power 4 . SELinux Error Reproducable: sometimes. Seems to have some relavance to his bug https://bugzilla.redhat.com/show_bug.cgi?id=1467036 Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.8-300.fc26.x86_64 type: libreport
Description of problem: en el momento en que se produjo el error la tapa de la laptop se encontraba cerrada Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.8-300.fc26.x86_64 type: libreport
Description of problem: Powertop service causing issues I believe - started right after enabling powertop as a service. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.8-300.fc26.x86_64 type: libreport
The previous comments about removing power from the laptop causing the issues might also be the cause, as removing power from the laptop is part of my validation process when working with powertop.
*** Bug 1470066 has been marked as a duplicate of this bug. ***
*** Bug 1467515 has been marked as a duplicate of this bug. ***
*** Bug 1467701 has been marked as a duplicate of this bug. ***
Description of problem: booted system (resident on a btrfs system) logged in sudo dnf update Bingo Selinux report Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.8-300.fc26.x86_64 type: libreport
Description of problem: Wake up from Standby Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: I resumed from sleep, and the alert was there. Today I resumed from sleep again (opened the lid), and another alert. I think it could be related. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: This happens every time I close the laptop Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: It appears on boot. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
*** Bug 1470666 has been marked as a duplicate of this bug. ***
*** Bug 1467850 has been marked as a duplicate of this bug. ***
Description of problem: UNK Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: happend during update reboot Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: This error is shown after I unplug DC adapter from my laptop. Version-Release number of selected component: selinux-policy-3.13.1-225.18.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.9-200.fc25.x86_64 type: libreport
Description of problem: Booted up laptop and denial was in logs Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: happens when booting fedora 25 Version-Release number of selected component: selinux-policy-3.13.1-225.18.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.9-200.fc25.x86_64 type: libreport
Description of problem: SELinux alert shows up randomly Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: I noticed this bug when I rebooted my computer into a new Linux kernel (version 4.12.1) that I compiled from source. After logging in, I noticed that the SELinux Troubleshooter reported 6 errors, including this one. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.1 type: libreport
Description of problem: Received a SELinux alert. Version-Release number of selected component: selinux-policy-3.13.1-225.18.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.9-200.fc25.x86_64 type: libreport
Description of problem: I just updated Fedora 25 to Fedora 26 using GUI tools ("Software" app). After rebooting I got that message about file access warning. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: gnome-shells tries to access machine-id Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: I enabled pptp traffic in firewalld with below commands: firewall-cmd --permanent --direct --add-rule ipv4 filter INPUT 0 -p gre -j ACCEPT firewall-cmd --permanent --direct --add-rule ipv6 filter INPUT 0 -p gre -j ACCEPT firewall-cmd --reload I also modprobed: nf_conntrack_pptp nf_conntrack_proto_gre all according to: https://ask.fedoraproject.org/en/question/94500/connection-via-vpn-pptp-does-not-work-unless-firewall-is-disabled/ Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: 1. upgrade to fedora 26 using the GUI propmt 2. use the OS briefly and let it go to sleep 3. unlock from sleep and saw the notification I have not connected my laptop to power during this time period. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: Estava fazendo a instalação do blender via terminal quando apareceu essa mensagem de erro. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: I started a HipChat video conference with Google Chrome and this SELinux alert showed up. Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: It is not clear to my how or when this happens, there does not seem to be a connection to anything I do. Programs that tend to run: shotwell, firefox, geary Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: Sale el error tras desbloqueo de pantalla después de un período de inactividad. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Regarding my bug report either, This Happens to me when I unplug it I think it's because of battery report of something, fedora calculation of remaining percentage and times is not correct, and I think it's because of this bug
Description of problem: I opened my laptop, and got the error. I really cant say ore then that... Version-Release number of selected component: selinux-policy-3.13.1-225.18.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.9-200.fc25.x86_64 type: libreport
Same here just after undocking my new laptop.
Description of problem: Just update F26. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: Appeared upon boot after upgrading Fedora 25 to 26. Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.10-300.fc26.x86_64 type: libreport
Description of problem: Añadiendo el editor de textos al dock con el editor abierto en ese momento. Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.10-300.fc26.x86_64 type: libreport
Additional Information to my previous comment, Apparently It happens after every hardware changes or every hardware state changes, like connecting or disconnecting external hard, mouse, or something similar, or plugging un unplugging charger and etc....
Description of problem: Immediately after login after startup. No actions taken before error occurred. Version-Release number of selected component: selinux-policy-3.13.1-225.18.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.9-200.fc25.x86_64 type: libreport
Description of problem: I closed my notebook, and when I opened the problem happened Version-Release number of selected component: selinux-policy-3.13.1-225.18.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.9-200.fc25.x86_64 type: libreport
Description of problem: After update to f26 sudo dnf update process just stops Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.10-300.fc26.x86_64 type: libreport
*** Bug 1472735 has been marked as a duplicate of this bug. ***
Description of problem: I have no experience to making decision on this trouble. Version-Release number of selected component: selinux-policy-3.13.1-225.18.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.9-200.fc25.x86_64 type: libreport
Description of problem: I exec command gsettings set org.gnome.desktop.interface show-battery-percentage true Then unplug power cable and plug in again. Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.10-300.fc26.x86_64 type: libreport
Description of problem: My system just encountered this problem all of a sudden when i was browsing the internet and using terminal. Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: I did a cold boot and the SELinux alert appeared immediately after login. It could be coincidence, but the TopIconsPlus extension also failed to load properly. When I attempted to disable and re-enable it, Gnome Shell crashed, sending me back to the login screen. Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.10-300.fc26.x86_64 type: libreport
Is it safe to create the selinux rule to allow the file in question to be read? Is that file read supposed to be happening? I'm guessing yes?
Description of problem: Issue occurs on reboot of laptop Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.12.2-1.fc26.x86_64 type: libreport
I didn't realize when this error happened exactly, but was after install ffmpeg io. After this I didn't do anything that could cause this error. SELinux is preventing gnome-shell from read access on the lnk_file /var/lib/dbus/machine-id. ***** Plugin catchall (100. confidence) suggests ************************** If você acredita que o gnome-shell deva ser permitido acesso de read em machine-id lnk_file por default. Then você deve informar que este é um erro. Você pode gerar um módulo de política local para permitir este acesso. Do allow this access for now by executing: # ausearch -c 'gnome-shell' --raw | audit2allow -M my-gnomeshell # semodule -X 300 -i my-gnomeshell.pp Additional Information: Source Context system_u:system_r:xdm_t:s0-s0:c0.c1023 Target Context system_u:object_r:system_dbusd_var_lib_t:s0 Target Objects /var/lib/dbus/machine-id [ lnk_file ] Source gnome-shell Source Path gnome-shell Port <Desconhecido> Host seguim-I5447 Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-260.1.fc26.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name seguim-I5447 Platform Linux seguim-I5447 4.11.10-300.fc26.x86_64 #1 SMP Wed Jul 12 17:05:39 UTC 2017 x86_64 x86_64 Alert Count 33 First Seen 2017-07-16 23:50:10 -03 Last Seen 2017-07-20 00:46:53 -03 Local ID 390a5968-6dd6-420f-a820-0ff59c29dcdd Raw Audit Messages type=AVC msg=audit(1500522413.373:394): avc: denied { read } for pid=1279 comm="gsd-power" name="machine-id" dev="sda6" ino=3017204 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:system_dbusd_var_lib_t:s0 tclass=lnk_file permissive=0 Hash: gnome-shell,xdm_t,system_dbusd_var_lib_t,lnk_file,read
Description of problem: It just occured to me all of a sudden, while i was using Xchat Version-Release number of selected component: selinux-policy-3.13.1-259.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.9-300.fc26.x86_64 type: libreport
Description of problem: Problem, after close and open, laptop screen. Don`t hibernate propertly. Thx. Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.10-300.fc26.x86_64 type: libreport
Description of problem: Lid close / Suspend / Lid Open Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.10-300.fc26.x86_64 type: libreport
Description of problem: 1. Setup auto-login on fedora 25 kernel 4.11.10 2. Upgrade to Fedora 26 via Software. 3. On boot-up after auto-login gnome-shell crashes. Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.10-300.fc26.x86_64 type: libreport
Description of problem: During 'dnf update' Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.10-300.fc26.x86_64 type: libreport
Description of problem: I was updating my Fedora 26 using "dnf upgrade -y". The violation happened during the pakage installation. Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.11-300.fc26.x86_64 type: libreport
selinux-policy-3.13.1-260.3.fc26 has been submitted as an update to Fedora 26. https://bodhi.fedoraproject.org/updates/FEDORA-2017-8f02d330ca
Description of problem: On awakening laptop from sleep. Was using mullvad vpn - not sure if related. Seems related to https://bugzilla.redhat.com/show_bug.cgi?id=1473118 Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.11-300.fc26.x86_64 type: libreport
*** Bug 1474433 has been marked as a duplicate of this bug. ***
Description of problem: Just showed up in normal use of a Fedora 25 Workstation system. I don't have any ibus-ish input methods configured at present. Version-Release number of selected component: selinux-policy-3.13.1-225.19.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.11-200.fc25.x86_64 type: libreport
Description of problem: Just unplugged power cord (switched to battery) Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.10-300.fc26.x86_64 type: libreport
selinux-policy-3.13.1-260.3.fc26 has been pushed to the Fedora 26 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2017-8f02d330ca
Description of problem: Often got this alert without doing anything special Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.11-300.fc26.x86_64 type: libreport
*** Bug 1468087 has been marked as a duplicate of this bug. ***
*** Bug 1471392 has been marked as a duplicate of this bug. ***
*** Bug 1474705 has been marked as a duplicate of this bug. ***
Description of problem: Not sure but it seems to have happened when I unplugged the external screen from the laptop Version-Release number of selected component: selinux-policy-3.13.1-225.18.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.11-200.fc25.x86_64 type: libreport
Description of problem: Switched on Laptop from Suspend to RAM (open Lid). Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.11-300.fc26.x86_64 type: libreport
Description of problem: Every time (or at least, pretty often) when my laptop wakes up from sleep, I get this alert Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.11-300.fc26.x86_64 type: libreport
Description of problem: Waking up from standby Version-Release number of selected component: selinux-policy-3.13.1-260.1.fc26.noarch Additional info: reporter: libreport-2.9.1 hashmarkername: setroubleshoot kernel: 4.11.11-300.fc26.x86_64 type: libreport
selinux-policy-3.13.1-260.3.fc26 has been pushed to the Fedora 26 stable repository. If problems still persist, please make note of it in this bug report.
Description of problem: Normal shell login. Version-Release number of selected component: selinux-policy-3.13.1-225.19.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.12-200.fc25.i686 type: libreport
Description of problem: The problem happened sometime when I put my laptop to sleep and was reported when I woke it up. Version-Release number of selected component: selinux-policy-3.13.1-225.19.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.12-200.fc25.x86_64 type: libreport
Description of problem: Reported automatically by Fedora Version-Release number of selected component: selinux-policy-3.13.1-225.18.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.9-200.fc25.x86_64 type: libreport
Description of problem: I don't know what happened here, but I turned on my notebook and this notification was in my notification bar. Version-Release number of selected component: selinux-policy-3.13.1-225.19.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.12-200.fc25.x86_64 type: libreport
Description of problem: Just plugged in my power adapter to recharge my box. Version-Release number of selected component: selinux-policy-3.13.1-225.19.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.12-200.fc25.x86_64 type: libreport
Description of problem: Plugged in Power adapter Version-Release number of selected component: selinux-policy-3.13.1-225.19.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.12-200.fc25.x86_64 type: libreport
Description of problem: This happens after a default F25 install (Workstation netinst) and booting the system for the first time. Version-Release number of selected component: selinux-policy-3.13.1-225.19.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.12-200.fc25.x86_64 type: libreport
This is not fixed in F25. Reopening.
Description of problem: tenia levantado el Gulp Watch_dev. De pronto haciendo consuntas entre las vistas que desarrollaba, se quedo congelado, imposibilitando incluso cerrar la paestaña de chrome Version-Release number of selected component: selinux-policy-3.13.1-225.19.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.12-200.fc25.x86_64 type: libreport
Description of problem: Plugged in A/C adapter. Version-Release number of selected component: selinux-policy-3.13.1-225.19.fc25.noarch Additional info: reporter: libreport-2.8.0 hashmarkername: setroubleshoot kernel: 4.11.12-200.fc25.x86_64 type: libreport
*** Bug 1486951 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.