Description of problem: Version-Release number of selected component: gnome-session-3.22.2-3.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: /usr/libexec/gnome-session-binary --session gnome-xorg crash_function: compile_branch executable: /usr/libexec/gnome-session-binary global_pid: 1424 kernel: 4.9.13-200.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (6 frames) #0 compile_branch at pcre_compile.c:6169 #1 compile_regex at pcre_compile.c:8405 #2 pcre_compile2 at pcre_compile.c:9385 #3 regex_compile at gregex.c:1421 #4 g_regex_new at gregex.c:1338 #5 gsm_util_export_activation_environment at gsm-util.c:514
Created attachment 1260967 [details] File: backtrace
Created attachment 1260968 [details] File: cgroup
Created attachment 1260969 [details] File: core_backtrace
Created attachment 1260970 [details] File: dso_list
Created attachment 1260971 [details] File: environ
Created attachment 1260972 [details] File: exploitable
Created attachment 1260973 [details] File: limits
Created attachment 1260974 [details] File: maps
Created attachment 1260975 [details] File: mountinfo
Created attachment 1260976 [details] File: namespaces
Created attachment 1260977 [details] File: open_fds
Created attachment 1260978 [details] File: proc_pid_status
Created attachment 1260979 [details] File: var_log_messages
Hello, Some background/context : GDM stopped working almost a week ago, after an upgrade (I couldn't tell what was upgraded though). After some digging, I found that the segfault was in /usr/libexec/gnome-session-binary (which is called by gdm through gnome-session). I removed every package related to desktops, PCRE (which seems involved in some way), removed "updates" repository, reinstalled everything, and tried to launch gnome-session-binary to see what was happening... I didn't know well abrt-cli so maybe I didn't send the good report (I thought I was sending the one generated by gdm itself), so if you need any other information I can put it here. Thanks !
Hi, The bug seems to be coming from PCRE or PCRE2 packages. I used "sudo dnf downgrade pcre --allowerasing" and "sudo dnf downgrade pcre2 ---allowerasing" and gnome-session is working again. Versions used : - up to date versions (which seem to cause the bug, from "updates" repository) : 8.40-5.fc25 (PCRE) and 10.23-2.fc25 (PCRE2) - downgraded versions (from "@System" repository) : 8.39-6.fc25, 10.23-2.fc25 Let me know if you need anything else for debugging.
Sorry, the downgraded version from PCRE2 is 10.22-5.fc25
I found that a very long CLASSPATH environment variable seemed to trigger the segfault. My guess is that a recent change in libpcre has made libpcre crash, if some environment value is too large. In my /etc/profile.d, I have a file java.sh with the following content: ====================================================== if [ -z "$CLASSPATH" ]; then for jar_dir in /usr/share/java "${HOME}/java/jars"; do [ -d "$jar_dir" ] && { for j in $(find "$jar_dir" -name *.jar); do if [ -z "$CLASSPATH" ]; then CLASSPATH="$j" else CLASSPATH="${CLASSPATH}:$j" fi done } done export CLASSPATH fi ====================================================== I removed a bunch of java packages on my system, and that seemed to bring down my automatically generated CLASSPATH to a length which no longer puts pcre in a bad mood. Still, if I'm right about the above assumptions, then I believe there's a bug in PCRE -- probably introduced in v. 8.40.
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.