Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1301730

Summary: [abrt] hamster-time-tracker: strlen(): python2.7 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: piio <bugzilla>
Component: hamster-time-trackerAssignee: Ankur Sinha (FranciscoD) <sanjay.ankur>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: fschwarz, projects.rg, sanjay.ankur
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b8d6a12b214b172a74ce4d38e516e6331e4960f7
Whiteboard: abrt_hash:c30b681aa04dedee928feaba42939fc73c810730;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-27 14:04:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description piio 2016-01-25 20:48:37 UTC 
Version-Release number of selected component:
hamster-time-tracker-2.0-0.1.rc1.fc24

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        python2 /usr/bin/hamster-service
crash_function: strlen
executable:     /usr/bin/python2.7
global_pid:     23319
kernel:         4.5.0-0.rc0.git9.1.fc24.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 strlen at ../sysdeps/x86_64/strlen.S:106
 #1 _ih_sub_new at inotify-sub.c:38
 #3 g_inotify_file_monitor_start at ginotifyfilemonitor.c:64
 #4 g_local_file_monitor_start at glocalfilemonitor.c:777
 #5 g_local_file_monitor_new_for_path at glocalfilemonitor.c:861
 #6 g_file_monitor_file at gfile.c:5328
 #7 ffi_call_unix64 at ../src/x86/unix64.S:76
 #8 ffi_call at ../src/x86/ffi64.c:525
 #9 pygi_invoke_c_callable at pygi-invoke.c:674
 #10 pygi_function_cache_invoke at pygi-cache.c:859
Comment 1 piio 2016-01-25 20:48:45 UTC 
Created attachment 1118202 [details]
File: backtrace
Comment 2 piio 2016-01-25 20:48:46 UTC 
Created attachment 1118203 [details]
File: cgroup
Comment 3 piio 2016-01-25 20:48:48 UTC 
Created attachment 1118204 [details]
File: core_backtrace
Comment 4 piio 2016-01-25 20:48:49 UTC 
Created attachment 1118205 [details]
File: dso_list
Comment 5 piio 2016-01-25 20:48:50 UTC 
Created attachment 1118206 [details]
File: environ
Comment 6 piio 2016-01-25 20:48:52 UTC 
Created attachment 1118207 [details]
File: exploitable
Comment 7 piio 2016-01-25 20:48:53 UTC 
Created attachment 1118208 [details]
File: limits
Comment 8 piio 2016-01-25 20:48:55 UTC 
Created attachment 1118209 [details]
File: maps
Comment 9 piio 2016-01-25 20:48:56 UTC 
Created attachment 1118210 [details]
File: mountinfo
Comment 10 piio 2016-01-25 20:48:58 UTC 
Created attachment 1118211 [details]
File: open_fds
Comment 11 piio 2016-01-25 20:48:59 UTC 
Created attachment 1118212 [details]
File: proc_pid_status
Comment 12 piio 2016-01-25 20:49:01 UTC 
Created attachment 1118213 [details]
File: var_log_messages
Comment 13 Raphael Groner 2016-01-26 12:40:09 UTC 
Unfortunately, the provided backtrace is not useful.
What did you do to cause the crash? Can you reproduce?
Comment 14 piio 2016-01-27 08:00:07 UTC 
Hi,

I reinstalled python and glib packages, there were also some updates, now in rawhide this problem don't happen again.
If it happen again I will submit it as new bug.
Comment 15 Raphael Groner 2016-02-13 18:37:37 UTC 

*** This bug has been marked as a duplicate of bug 1307256 ***