Version-Release number of selected component: plasma-workspace-5.4.3-1.fc22 Additional info: reporter: libreport-2.6.3 backtrace_rating: 3 cmdline: ksplashqml Breeze --pid executable: /usr/bin/ksplashqml global_pid: 27467 kernel: 4.2.5-201.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (5 frames) #3 ?? #4 g_malloc0 at gmem.c:127 #5 thread_memory_from_self at gslice.c:519 #6 g_slice_free1 at gslice.c:1088 #7 __nptl_deallocate_tsd at pthread_create.c:175
Created attachment 1095921 [details] File: backtrace
Created attachment 1095922 [details] File: cgroup
Created attachment 1095923 [details] File: core_backtrace
Created attachment 1095924 [details] File: dso_list
Created attachment 1095925 [details] File: environ
Created attachment 1095926 [details] File: limits
Created attachment 1095927 [details] File: maps
Created attachment 1095928 [details] File: mountinfo
Created attachment 1095929 [details] File: open_fds
Created attachment 1095930 [details] File: proc_pid_status
Created attachment 1095931 [details] File: var_log_messages
Another user experienced a similar problem: At log-in. reporter: libreport-2.6.3 backtrace_rating: 3 cmdline: ksplashqml Breeze --pid executable: /usr/bin/ksplashqml global_pid: 18917 kernel: 4.2.6-201.fc22.x86_64 package: plasma-workspace-5.4.3-3.fc22 reason: ksplashqml killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It happend while logging out. reporter: libreport-2.6.4 backtrace_rating: 3 cmdline: ksplashqml Breeze --pid executable: /usr/bin/ksplashqml global_pid: 1717 kernel: 4.4.3-201.fc22.x86_64 package: plasma-workspace-5.5.4-2.fc22 reason: ksplashqml killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.