Description of problem: Steps to reproduce on new Fedora 31 install: 1. Download a dircolors file from https://github.com/trapd00r/LS_COLORS 2. Put eval $(dircolors -b path/to/LS_COLORS/file) to .bashrc 3. Reboot and try to login via GDM The dircolors file is probably valid and so is the resulting LS_COLORS variable, because it works as intended. But gnome-session-binary crashes every time I try to login via GDM with the mentioned eval in .bashrc. Version-Release number of selected component: gnome-session-3.34.2-2.fc31 Additional info: reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-2.scope cmdline: /usr/libexec/gnome-session-binary crash_function: match executable: /usr/libexec/gnome-session-binary journald_cursor: s=ffca0efacba5477eb76a418572336815;i=501a;b=244e2d2ce61745f096e5c877591cc5b5;m=fc1a0f;t=59cdede0694ec;x=4ce6234cca314d71 kernel: 5.4.12-200.fc31.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 0 (1 frames) #0 match at pcre_exec.c:522 Potential duplicate: bug 1415442
Created attachment 1655054 [details] File: backtrace
Created attachment 1655055 [details] File: core_backtrace
Created attachment 1655056 [details] File: cpuinfo
Created attachment 1655057 [details] File: dso_list
Created attachment 1655058 [details] File: environ
Created attachment 1655059 [details] File: exploitable
Created attachment 1655060 [details] File: limits
Created attachment 1655061 [details] File: maps
Created attachment 1655062 [details] File: mountinfo
Created attachment 1655063 [details] File: open_fds
Created attachment 1655064 [details] File: proc_pid_status
Similar problem has been detected: Added a program call to .bashrc. When you try to log in, gdm returns to the login page without starting the session. reporter: libreport-2.11.3 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-2.scope cmdline: /usr/libexec/gnome-session-binary crash_function: match executable: /usr/libexec/gnome-session-binary journald_cursor: s=c56e427319a34f8090a52e8973c09f70;i=6bf2;b=74c477da3d5e4172a60fb27a8415da9d;m=1ae26ec;t=59d1aa512e2b6;x=9bfac4ffa0540c25 kernel: 5.4.13-201.fc31.x86_64 package: gnome-session-3.34.2-2.fc31 reason: gnome-session-binary killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: This has happened in both RHEL 7.6 as well as Fedora 31. Started happening with Cinnamon Desktop (4.4), but also tested with Gnome3 (3.34) and MATE (1.22). Starting any of these desktop environments from the DM (RHEL 7.6) or LightDM display managers will start loading he desktop environment, then drop back to the display manager/login screen. Logging in as OpenBox (on RHEL 7.6) LXQt (0.14) or KDE Plasma (5.17) will load those desktops/shells with no problem. Have installed Fedora 31 on the system that used to have RHEL 7.6, so that particular test environment is not available anymore. Also, to verify this isn't an issue with my particular hardware, I copied the home directory from the primary machine (Lenovo ThinkPad P50) to another machine (Lenovo ThinkPad T430). Previously this method of copying the home directory had worked (testing a mogration from RHEL to Fedora), so it should be a comparable environment. As this happens in three desktops, I will be pasting this note to those reports as well. reporter: libreport-2.12.0 backtrace_rating: 4 cgroup: 0::/user.slice/user-1000.slice/session-6.scope cmdline: /usr/libexec/gnome-session-binary crash_function: match executable: /usr/libexec/gnome-session-binary journald_cursor: s=9f560bcd5b704e24adefe158709e8d7b;i=891e;b=7dc8ca86efd44eacac4331b758e34292;m=3b8b7c88;t=5a092aa845db3;x=d2f636f64288f15f kernel: 5.5.8-200.fc31.x86_64 package: gnome-session-3.34.2-2.fc31 reason: gnome-session-binary killed by SIGSEGV rootdir: / runlevel: N 5 type: CCpp uid: 1000 xsession_errors:
Something I've found in my own particular setup, how relevant to others' similar issues they would have to check themselves. This is what fixed mine: ================================================================== So I went through the steps I had done to migrate my profile to a fresh install, and came across the setting for customizing the colors for the "ls" command (which had been in my old .bashrc file but not the default one created by the install. Removed this and the login failure went away. https://github.com/trapd00r/LS_COLORS Hadn't changed any of it's default settings yet, so it would be whatever values the sample file has. Can't understand why a settings file for LS would mess up a login, unless it's because the variable would be large.
Still facing this issue in Fedora 32. In my attempt the sweet spot for the character limit seems to be 8175. Stack traces[1] for the segfault seem to indicate its libpcre, which suggests a string parsing issue? --- $ uname -a Linux fedora 5.6.14-300.fc32.x86_64 #1 SMP Wed May 20 20:47:32 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/system-release Fedora release 32 (Thirty Two) [1] $ dmesg | grep segfault [ 261.983954] gnome-session-b[39670]: segfault at 7ffdcad65e90 ip 00007fa04f7be391 sp 00007ffdcad65e80 error 6 in libpcre.so.1.2.12[7fa04f7ab000+56000] [ 706.625393] gnome-session-b[43424]: segfault at 7ffceb191e90 ip 00007fc4ce574391 sp 00007ffceb191e80 error 6 in libpcre.so.1.2.12[7fc4ce561000+56000] [ 1066.473008] gnome-session-b[47600]: segfault at 7fff0825efc0 ip 00007fa8eda67391 sp 00007fff0825efb0 error 6 in libpcre.so.1.2.12[7fa8eda54000+56000] [ 2252.432719] gnome-session-b[51775]: segfault at 7ffd73183fa0 ip 00007fce3970a391 sp 00007ffd73183f90 error 6 in libpcre.so.1.2.12[7fce396f7000+56000] [ 2656.126178] gnome-session-b[65358]: segfault at 7ffcc8857ff8 ip 00007f0656eded76 sp 00007ffcc8858000 error 6 in libpcre.so.1.2.12[7f0656e8a000+56000] [ 2663.082240] gnome-session-b[65608]: segfault at 7fff565cff10 ip 00007f8f767d5391 sp 00007fff565cff00 error 6 in libpcre.so.1.2.12[7f8f767c2000+56000] [ 2692.785409] gnome-session-b[66055]: segfault at 7ffd6a32af50 ip 00007f881834e391 sp 00007ffd6a32af40 error 6 in libpcre.so.1.2.12[7f881833b000+56000] [ 2710.858387] gnome-session-b[66501]: segfault at 7ffe34cd6fc0 ip 00007fd8b4a00391 sp 00007ffe34cd6fb0 error 6 in libpcre.so.1.2.12[7fd8b49ed000+56000] [ 2799.375550] gnome-session-b[69706]: segfault at 7fff8c31cff8 ip 00007f1c00fdb389 sp 00007fff8c31d000 error 6 in libpcre.so.1.2.12[7f1c00fc8000+56000] [ 2806.880055] gnome-session-b[69941]: segfault at 7ffe510ecff0 ip 00007f529c6e5efd sp 00007ffe510ecff8 error 6 in libpcre.so.1.2.12[7f529c6d2000+56000] [ 2899.091042] gnome-session-b[72038]: segfault at 7ffe18998e80 ip 00007f31a6b8d391 sp 00007ffe18998e70 error 6 in libpcre.so.1.2.12[7f31a6b7a000+56000] [ 2922.745279] gnome-session-b[72502]: segfault at 7ffcac0d8f80 ip 00007fc95dabe391 sp 00007ffcac0d8f70 error 6 in libpcre.so.1.2.12[7fc95daab000+56000] [ 2943.779662] gnome-session-b[72950]: segfault at 7ffd4f4cbef0 ip 00007f9125fb6391 sp 00007ffd4f4cbee0 error 6 in libpcre.so.1.2.12[7f9125fa3000+56000] [ 3010.534717] gnome-session-b[75608]: segfault at 7ffc6b8d3f00 ip 00007ff95000d391 sp 00007ffc6b8d3ef0 error 6 in libpcre.so.1.2.12[7ff94fffa000+56000] [ 3024.691096] gnome-session-b[76046]: segfault at 7ffd05751e90 ip 00007feba8c0b391 sp 00007ffd05751e80 error 6 in libpcre.so.1.2.12[7feba8bf8000+56000] [ 3042.084531] gnome-session-b[76500]: segfault at 7ffec2492fe0 ip 00007f19c9c72391 sp 00007ffec2492fd0 error 6 in libpcre.so.1.2.12[7f19c9c5f000+56000] [ 3088.512449] gnome-session-b[79105]: segfault at 7ffdbf339ee0 ip 00007f3664e5a391 sp 00007ffdbf339ed0 error 6 in libpcre.so.1.2.12[7f3664e47000+56000] [ 3105.895593] gnome-session-b[79553]: segfault at 7ffcc424afb0 ip 00007fd0c65b9391 sp 00007ffcc424afa0 error 6 in libpcre.so.1.2.12[7fd0c65a6000+56000]
PCRE api spec[1] defines 'error 6' in two places, compile time 'missing terminating ] for character class' or runtime 'PCRE_ERROR_NOMEMORY'. I'd say given the examples above, the latter would hold true, but not overly familiar with these myself. --- [1] https://www.pcre.org/original/doc/html/pcreapi.html
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. 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 '31'. 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 31 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 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 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.