Ask Your Question

marko7's profile - activity

2019-03-04 04:05:26 -0600 received badge  Notable Question (source)
2018-08-14 06:26:47 -0600 received badge  Popular Question (source)
2018-02-17 15:24:43 -0600 asked a question GNOME on Xorg freezes on restart or shutdown, Problem Reporting says tainted kernel

When I'm using GNOME on Xorg and try to restart or shutdown the computer, the entire system freezes and I have to do force shutdown by holding the power button on my laptop. This has started happening yesterday and it happens every time now. These are all the packages/updates that were installed in the period since I started having this issue. The issue does not appear with GNOME (on Wayland).

ernel-headers-4.15.3-300.fc27.x86_64         Sat 17 Feb 2018 12:31:39 AM CET
libsane-hpaio-3.17.11-8.fc27.x86_64           Sat 17 Feb 2018 12:31:35 AM CET
kernel-modules-extra-4.15.3-300.fc27.x86_64   Sat 17 Feb 2018 12:31:35 AM CET
kernel-4.15.3-300.fc27.x86_64                 Sat 17 Feb 2018 12:31:35 AM CET
hplip-3.17.11-8.fc27.x86_64                   Sat 17 Feb 2018 12:31:35 AM CET
hplip-libs-3.17.11-8.fc27.x86_64              Sat 17 Feb 2018 12:31:33 AM CET
hplip-common-3.17.11-8.fc27.x86_64            Sat 17 Feb 2018 12:31:33 AM CET
kernel-modules-4.15.3-300.fc27.x86_64         Sat 17 Feb 2018 12:31:28 AM CET
kernel-core-4.15.3-300.fc27.x86_64            Sat 17 Feb 2018 12:31:26 AM CET
sane-backends-libs-1.0.27-12.fc27.x86_64      Sat 17 Feb 2018 12:31:23 AM CET
sane-backends-1.0.27-12.fc27.x86_64           Sat 17 Feb 2018 12:31:23 AM CET
gpg-pubkey-beb6d886-551540f4                  Fri 16 Feb 2018 10:26:12 PM CET
gpg-pubkey-2e1c0b95-573c97c9                  Fri 16 Feb 2018 10:10:41 PM CET

Also, in both cases (Wayland and Xorg), Problem Reporting throws 5 very similar issues on each startup, as shown in the following picture: https://imgur.com/a/Q5kPl. I've uploaded the full details (the entire data directory) for one of them to Google Drive and they can be accessed here: https://drive.google.com/open?id=1ofpq0ncMz9XiLF8BRZ1f2vy7CiGv1X. But it says that I cannot report them because the kernel has been "tainted", even though right now (in a Wayland session), running dmesg | grep -i taint gives nothing, and running cat /proc/sys/kernel/tainted returns 0.

After first log in to a Xorg session, cat /proc/sys/kernel/tainted returns 512, and dmesg | grep -i taint returns this:

[ 1890.014257] CPU: 1 PID: 6225 Comm: Xorg Not tainted 4.15.3-300.fc27.x86_64 #1
[ 1892.020897] CPU: 5 PID: 6225 Comm: Xorg Tainted: G        W        4.15.3-300.fc27.x86_64 #1
[ 1894.022234] CPU: 1 PID: 6225 Comm: Xorg Tainted: G        W        4.15.3-300.fc27.x86_64 #1
[ 1896.023690] CPU: 5 PID: 6225 Comm: Xorg Tainted: G        W        4.15.3-300.fc27.x86_64 #1
[ 1898.025194] CPU: 1 PID: 6225 Comm: Xorg Tainted: G        W        4.15.3-300.fc27.x86_64 #1
[ 1900.026671] CPU: 5 PID: 6225 Comm: Xorg Tainted: G        W        4.15.3-300.fc27.x86_64 #1
[ 1902.027978] CPU: 1 PID: 6225 Comm: Xorg Tainted: G        W        4.15.3-300.fc27.x86_64 #1
[ 1904.039878] CPU: 5 PID: 6225 Comm: Xorg Tainted: G        W        4.15.3-300.fc27.x86_64 ...
(more)
2018-02-16 20:22:25 -0600 asked a question Fedora hangs (cannot login) after uncommenting EnableWayland=false

After uncommenting the line EnableWayland=false in /etc/gdm/custom.conf, I can no longer log in to Fedora 27, that is, the system hangs on the gray screen after entering the account password. Fedora is fully updated.

2018-02-16 10:07:36 -0600 asked a question Settings app hangs when selecting "Details", causes GNOME to hang as well

When selecting the "Details" section in the built-in Settings app in Fedora 27, the app just hangs with high CPU usage, which makes the entire desktop environment stutter and hang. When that happens, I have to force kill the Settings app.

I'm using Fedora 27, with the latest updates, on a Lenovo Legion Y520 laptop (Intel Kaby Lake i7, 8GB RAM, Intel HD Graphics + GTX 1050), in a dual-boot configuration with Windows 10. The same thing happens with both the Wayland and the Xorg versions of GNOME.

I see that I am not the only one experiencing this issue.