Bug 1074144 - [abrt] nemo: expiry_func(): nemo killed by SIGSEGV
Summary: [abrt] nemo: expiry_func(): nemo killed by SIGSEGV
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nemo
Version: 22
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: leigh scott
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:7f290e91c4f00eae5474e8bf4ba...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-03-08 07:49 UTC by Moez Roy
Modified: 2016-07-19 11:07 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-07-19 11:07:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (35.23 KB, text/plain)
2014-03-08 07:49 UTC, Moez Roy
no flags Details
File: cgroup (172 bytes, text/plain)
2014-03-08 07:50 UTC, Moez Roy
no flags Details
File: core_backtrace (13.96 KB, text/plain)
2014-03-08 07:50 UTC, Moez Roy
no flags Details
File: dso_list (10.13 KB, text/plain)
2014-03-08 07:50 UTC, Moez Roy
no flags Details
File: environ (1.15 KB, text/plain)
2014-03-08 07:50 UTC, Moez Roy
no flags Details
File: exploitable (82 bytes, text/plain)
2014-03-08 07:50 UTC, Moez Roy
no flags Details
File: limits (1.29 KB, text/plain)
2014-03-08 07:50 UTC, Moez Roy
no flags Details
File: maps (51.96 KB, text/plain)
2014-03-08 07:50 UTC, Moez Roy
no flags Details
File: open_fds (2.13 KB, text/plain)
2014-03-08 07:50 UTC, Moez Roy
no flags Details
File: proc_pid_status (1.06 KB, text/plain)
2014-03-08 07:50 UTC, Moez Roy
no flags Details
File: var_log_messages (369 bytes, text/plain)
2014-03-08 07:50 UTC, Moez Roy
no flags Details

Description Moez Roy 2014-03-08 07:49:56 UTC
Version-Release number of selected component:
nemo-2.0.8-9.fc21

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 4
cmdline:        nemo
crash_function: expiry_func
executable:     /usr/bin/nemo
kernel:         3.14.0-0.rc5.git2.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (3 frames)
 #1 expiry_func at accessible-leasing.c:122
 #6 g_main_context_iteration at gmain.c:3795
 #7 g_application_run at gapplication.c:2114

Comment 1 Moez Roy 2014-03-08 07:49:58 UTC
Created attachment 872104 [details]
File: backtrace

Comment 2 Moez Roy 2014-03-08 07:50:00 UTC
Created attachment 872105 [details]
File: cgroup

Comment 3 Moez Roy 2014-03-08 07:50:01 UTC
Created attachment 872106 [details]
File: core_backtrace

Comment 4 Moez Roy 2014-03-08 07:50:03 UTC
Created attachment 872107 [details]
File: dso_list

Comment 5 Moez Roy 2014-03-08 07:50:04 UTC
Created attachment 872108 [details]
File: environ

Comment 6 Moez Roy 2014-03-08 07:50:06 UTC
Created attachment 872109 [details]
File: exploitable

Comment 7 Moez Roy 2014-03-08 07:50:08 UTC
Created attachment 872110 [details]
File: limits

Comment 8 Moez Roy 2014-03-08 07:50:09 UTC
Created attachment 872111 [details]
File: maps

Comment 9 Moez Roy 2014-03-08 07:50:10 UTC
Created attachment 872112 [details]
File: open_fds

Comment 10 Moez Roy 2014-03-08 07:50:12 UTC
Created attachment 872113 [details]
File: proc_pid_status

Comment 11 Moez Roy 2014-03-08 07:50:13 UTC
Created attachment 872114 [details]
File: var_log_messages

Comment 12 Jaroslav Reznik 2015-03-03 15:33:26 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22

Comment 13 Fedora End Of Life 2016-07-19 11:07:05 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.