Bug 1247778

Summary: [abrt] kdelibs: LIBMTP_Release_Device(): kdeinit4 killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Fabio Correa <facorread>
Component: kdelibsAssignee: Than Ngo <than>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: jgrulich, jreznik, kevin, ltinkl, rdieter, rnovacek, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/b87e8fb7720a31339eba84c09f7606b4cb7f597c
Whiteboard: abrt_hash:1cac5ce0c961d4f5fabee64c686e3ffe55642719
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 17:14:30 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: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status none

Description Fabio Correa 2015-07-28 20:45:55 UTC 
Description of problem:
Transferring files to Nexus 7

Version-Release number of selected component:
kdelibs-4.14.9-2.fc22

Additional info:
reporter:       libreport-2.6.1
backtrace_rating: 4
cmdline:        'kdeinit4: kio_mtp [kd' e
crash_function: LIBMTP_Release_Device
executable:     /usr/bin/kdeinit4
global_pid:     30056
kernel:         4.0.8-300.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 LIBMTP_Release_Device at libmtp.c:2357
 #1 CachedDevice::~CachedDevice at ../devicecache.cpp:59
 #3 DeviceCache::deviceRemoved at ../devicecache.cpp:187
 #4 QMetaObject::activate at kernel/qobject.cpp:3567
 #5 Solid::DeviceNotifier::deviceRemoved at ./devicenotifier.moc:107
 #6 Solid::DeviceManagerPrivate::_k_deviceRemoved at ../../../solid/solid/devicemanager.cpp:207
 #7 QMetaObject::activate at kernel/qobject.cpp:3567
 #8 Solid::Ifaces::DeviceManager::deviceRemoved at ifaces/devicemanager.moc:107
 #9 Solid::Backends::UDev::UDevManager::slotDeviceRemoved at ../../../solid/solid/backends/udev/udevmanager.cpp:270
 #10 QMetaObject::activate at kernel/qobject.cpp:3567
Comment 1 Fabio Correa 2015-07-28 20:46:08 UTC 
Created attachment 1057122 [details]
File: backtrace
Comment 2 Fabio Correa 2015-07-28 20:46:10 UTC 
Created attachment 1057123 [details]
File: cgroup
Comment 3 Fabio Correa 2015-07-28 20:46:12 UTC 
Created attachment 1057124 [details]
File: core_backtrace
Comment 4 Fabio Correa 2015-07-28 20:46:16 UTC 
Created attachment 1057125 [details]
File: dso_list
Comment 5 Fabio Correa 2015-07-28 20:46:21 UTC 
Created attachment 1057126 [details]
File: environ
Comment 6 Fabio Correa 2015-07-28 20:46:24 UTC 
Created attachment 1057127 [details]
File: limits
Comment 7 Fabio Correa 2015-07-28 20:46:27 UTC 
Created attachment 1057128 [details]
File: maps
Comment 8 Fabio Correa 2015-07-28 20:46:37 UTC 
Created attachment 1057129 [details]
File: mountinfo
Comment 9 Fabio Correa 2015-07-28 20:46:42 UTC 
Created attachment 1057130 [details]
File: namespaces
Comment 10 Fabio Correa 2015-07-28 20:46:44 UTC 
Created attachment 1057131 [details]
File: open_fds
Comment 11 Fabio Correa 2015-07-28 20:46:47 UTC 
Created attachment 1057132 [details]
File: proc_pid_status
Comment 12 Fedora End Of Life 2016-07-19 17:14:30 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.