This fixes RHBZ 2039093 for me. Thanks for the rebuild!
@amessina: that looks a lot like Bug 1976653, so you would be correct in deducing it's not directly kernel-related.
No issues of note. Appears to fully resolve issue 1632 on drm/amd.
Thanks for the quick patch.
Similar results to @okay_awright:
$ sudo lsinitrd /boot/initramfs-5.11.10-300.*.img |egrep '^(Image|Version|Arguments)'
Image: /boot/initramfs-5.11.10-300.fc34.x86_64.img: 42M
Version: dracut-051-1.fc34.1
Arguments: -f
[j39m@flaglock6 ~/Downloads/tmp]
$ sudo lsinitrd /boot/initramfs-5.11.11-300.*.img |egrep '^(Image|Version|Arguments)'
Image: /boot/initramfs-5.11.11-300.fc34.x86_64.img: 42M
Version: dracut-053-1.fc34
Arguments: -f
@throwaway, thanks for the bug reports.
I'm experiencing the same issue as antiv; backing out to 5.11.10-300 is also a viable workaround for me. The only salient detail for my device is that I'm using full-disk encryption.
$ sudo lsblk
[sudo] password for kalvin:
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
zram0 252:0 0 8G 0 disk [SWAP]
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 600M 0 part /boot/efi
├─nvme0n1p2 259:2 0 1G 0 part /boot
└─nvme0n1p3 259:3 0 929.9G 0 part
└─luks-c154495b-f916-49bb-8226-8236686cb807 253:0 0 929.9G 0 crypt
├─fedora_localhost--live-root 253:1 0 70G 0 lvm /
├─fedora_localhost--live-swap 253:2 0 10.8G 0 lvm [SWAP]
└─fedora_localhost--live-home 253:3 0 849.1G 0 lvm /home
Fixes alacritty issue 4824. Thanks for the update!
Ack, I didn't upgrade wlroots to 0.7.0. I didn't realize that was required with this update.
With wlroots 0.7.0, sway 1.2 comes up just fine. Sorry about that.
Sorry for the delay. Here's the backtrace:
[New LWP 10126]
[New LWP 10128]
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
warning: Loadable section ".note.gnu.property" outside of ELF segments
Core was generated by `sway -d'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007fe4a45c4abf in wl_list_insert () from /lib64/libwayland-server.so.0
[Current thread is 1 (Thread 0x7fe4a118aac0 (LWP 10126))]
#0 0x00007fe4a45c4abf in wl_list_insert () at /lib64/libwayland-server.so.0
#1 0x000055616087b42b in wl_signal_add (signal=<optimized out>, listener=0x5561628146d0) at /usr/include/wayland-server-core.h:435
seat = 0x556162814620
__PRETTY_FUNCTION__ = "seat_create"
#2 0x000055616087b42b in seat_create (seat_name=0x5561608a799a "seat0") at ../sway/input/seat.c:492
seat = 0x556162814620
__PRETTY_FUNCTION__ = "seat_create"
#3 0x000055616086b2d5 in server_init (server=0x5561608c1de0 <server>) at ../sway/server.c:157
renderer = <optimized out>
__PRETTY_FUNCTION__ = "server_init"
wlr_output = <optimized out>
#4 0x00005561608603c7 in main (argc=2, argv=0x7ffcd8336238) at ../sway/main.c:367
verbose = 0
debug = 1
validate = 0
allow_unsupported_gpu = 0
long_options = {{name = 0x5561608a64bd "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x5561608a9289 "config", has_arg = 1, flag = 0x0, val = 99}, {name = 0x5561608a64c2 "validate", has_arg = 0, flag = 0x0, val = 67}, {name = 0x5561608a64cb "debug", has_arg = 0, flag = 0x0, val = 100}, {name = 0x5561608a6421 "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x5561608a55e3 "verbose", has_arg = 0, flag = 0x0, val = 86}, {name = 0x5561608a64d1 "get-socketpath", has_arg = 0, flag = 0x0, val = 112}, {name = 0x5561608a64e0 "unsupported-gpu", has_arg = 0, flag = 0x0, val = 117}, {name = 0x5561608a64f0 "my-next-gpu-wont-be-nvidia", has_arg = 0, flag = 0x0, val = 117}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}}
config_path = 0x0
usage = 0x5561608a6800 "Usage: sway [options] [command]\n\n -h, --help", ' ' <repeats 13 times>, "Show help message and quit.\n -c, --config <config> Specify a config file.\n -C, --validate Check the validity of the config file, th"...
c = <optimized out>
I'm using libwayland-server-1.17.0-1.fc30.x86_64
. I have saved the core off if that's of interest, but I don't know where to share it.
This update appears DOA on my Lenovo Thinkpad E440 - it segfaults immediately upon startup:
Sep 08 00:23:11 flaglock3 audit[28153]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 pid=28153 comm="sway" exe="/usr/bin/sway" sig=11 res=1
Sep 08 00:23:11 flaglock3 kernel: sway[28153]: segfault at 7f83381c7f08 ip 00007f83381ddabf sp 00007ffdcb81c4b8 error 7 in libwayland-server.so.0.1.0[7f83381d7000+8000]
Sep 08 00:23:11 flaglock3 kernel: Code: c4 08 5b 5d 41 5c 41 5d c3 66 90 f3 0f 1e fa 48 89 3f 48 89 7f 08 c3 0f 1f 40 00 f3 0f 1e fa 48 8b 47 08 48 89 3e 48 89 46 08 <48> 89 77 08 48 8b 46 08 48 89 30 c3 0f 1f 44 00 00 f3 0f 1e fa 48
Sep 08 00:23:11 flaglock3 systemd[1]: Started Process Core Dump (PID 28156/UID 0).
Sep 08 00:23:11 flaglock3 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@6-28156-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Sep 08 00:23:12 flaglock3 systemd-coredump[28157]: Resource limits disable core dumping for process 28153 (sway).
Sep 08 00:23:12 flaglock3 systemd-coredump[28157]: Process 28153 (sway) of user 1000 dumped core.
Sep 08 00:23:12 flaglock3 audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-coredump@6-28156-0 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
I'm slowly trying to figure out what "resource limits" prevent me from acquiring a core...
Works fine on a Thinkpad E440.
No special migration needed and no fuss whatsoever - everything looks great to me.
Described workaround with the NSS plugin works great. +1 and thank you!
Pidgin comes up but the plugin can't seem to connect:
Unable to connect to b-api.facebook.com: SSL Handshake Failed
But hurrah, Pidgin comes up!
Thank you so much for the update — a huge relief to see issue 2219794 fixed.