stable

kernel-5.6.11-100.fc30 and kernel-headers-5.6.11-100.fc30

FEDORA-2020-513d099847 created by jforbes 4 years ago for Fedora 30

The 5.6.11 stable kernel update contains a number of important fixes across the tree.


The 5.6.10 stable kernel update contains a number of important fixes across the tree.

Reboot Required
After installing this update it is required that you reboot your system to ensure the changes supplied by this update are applied properly.

How to install

Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:

sudo dnf upgrade --refresh --advisory=FEDORA-2020-513d099847

This update has been submitted for testing by jforbes.

4 years ago

This update's test gating status has been changed to 'waiting'.

4 years ago

This update's test gating status has been changed to 'ignored'.

4 years ago

This update has obsoleted kernel-5.6.10-100.fc30, and has inherited its bugs and notes.

4 years ago

This update has been pushed to testing.

4 years ago
User Icon samoht0 commented & provided feedback 4 years ago
karma

wfm

karma

This update can be pushed to stable now if the maintainer wishes

4 years ago

This update has been submitted for stable by jforbes.

4 years ago

still long time of login to Xfce after logout of gnome

What's the bug for that, and does it have logs showing this as kernel?

I'm sorry I'm not sure whether it has bug. It has appeared after kernel upgrade.

Some log is here but I'm not sure whether this bug is here:

May 11 20:00:44 fedora dbus-broker-launch[3033]: Service file '/usr/share/dbus-1/services/org.xfce.Tumbler.Thumbnailer1.service' is not named after th>

May 11 20:00:44 fedora systemd[1184]: Starting D-Bus User Message Bus...

May 11 20:00:44 fedora systemd[1184]: Failed to start Portal service.

May 11 20:00:44 fedora systemd[1184]: xdg-desktop-portal.service: Failed with result 'timeout'.

May 11 20:00:44 fedora systemd[1184]: xdg-desktop-portal.service: Start operation timed out. Terminating.

May 11 20:00:44 fedora systemd[1184]: at-spi-dbus-bus.service: Failed with result 'signal'.

May 11 20:00:44 fedora systemd[1184]: dbus-broker.service: Failed with result 'signal'.

May 11 20:00:44 fedora systemd[1184]: dbus-broker.service: Main process exited, code=killed, status=9/KILL

May 11 20:00:44 fedora systemd[1184]: pulseaudio.service: Failed with result 'signal'.

May 11 20:00:44 fedora systemd[1184]: pulseaudio.service: Main process exited, code=killed, status=9/KILL

May 11 20:00:44 fedora systemd[1184]: Failed to get initial list of names: Connection timed out

May 11 20:00:25 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=123456789 ses=123456789 subj=system_u:system_r:init_t:s0 msg='unit=packagekit comm="s>

May 11 20:00:25 fedora systemd[1]: packagekit.service: Succeeded.

May 11 20:00:25 fedora PackageKit[1534]: daemon quit

May 11 19:59:28 fedora audit[1]: SERVICE_STOP pid=1 uid=0 auid=123456789 ses=123456789 subj=system_u:system_r:init_t:s0 msg='unit=dbus-:1.8-org.fedo>

May 11 19:59:28 fedora systemd[1]: dbus-:1.8-org.fedoraproject.Setroubleshootd@1.service: Succeeded.

May 11 19:59:24 fedora audit[3005]: USER_START pid=3005 uid=0 auid=1000 ses=3 subj=system_u:system_r:xdm_t:s0-s0:c0.c1023 msg='op=PAM:session_open gra>

May 11 19:59:23 fedora lxdm-session[3012]: Passphrase file wrapped

May 11 19:59:23 fedora lxdm-session[3005]: pam_unix(lxdm:session): session opened for user u by (uid=0)

May 11 19:59:23 fedora gnome-keyring-daemon[3011]: couldn't bind to control socket: /home/u/.cache/keyring-xxxxxx/control: No such file or directory

May 11 19:59:23 fedora systemd[1]: Started Session 3 of user u.

May 11 19:59:23 fedora gnome-keyring-daemon[3011]: couldn't create socket directory: /home/u/.cache/keyring-xxxxxx: No such file or directory

May 11 19:59:23 fedora systemd-logind[918]: New session 3 of user u.

This update has been pushed to stable.

4 years ago

Right, with the logs you have posted (in almost every kernel update recently) this does not look kernel related. You will need to open up a bug in bugzilla either way. If it were kernel, we don't do bug tracking here. When you post here, and I don't see anything kernel related, I don't worry about it and move on. If it were in bugzilla, it could be assigned to the correct package, and all of the history goes with it.

I'm sorry for inconvenience. I've posted logs because these have appeared after kernel upgrade. I'm sorry I don't have enough time to investigate it until become 100 % sure it's kernel related.

I couldn't find any documentation about what to post or not post here.


Please login to add feedback.

Metadata
Type
bugfix
Karma
2
Signed
Content Type
RPM
Test Gating
Settings
Unstable by Karma
-3
Stable by Karma
disabled
Stable by Time
disabled
Dates
submitted
4 years ago
in testing
4 years ago
in stable
4 years ago

Automated Test Results

Test Cases

0 0 Test Case kernel regression