Bug 798473 - [abrt] gvfs-smb-1.10.1-3.fc16: Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT)
[abrt] gvfs-smb-1.10.1-3.fc16: Process /usr/libexec/gvfsd-smb was killed by s...
Product: Fedora
Classification: Fedora
Component: gvfs (Show other bugs)
i686 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Tomáš Bžatek
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-02-28 18:45 EST by Richard Haakma
Modified: 2015-03-03 18:04 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 17:51:45 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: dso_list (4.57 KB, text/plain)
2012-02-28 18:45 EST, Richard Haakma
no flags Details
File: maps (12.83 KB, text/plain)
2012-02-28 18:45 EST, Richard Haakma
no flags Details
File: backtrace (13.26 KB, text/plain)
2012-02-28 18:45 EST, Richard Haakma
no flags Details

  None (edit)
Description Richard Haakma 2012-02-28 18:45:45 EST
libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        /usr/libexec/gvfsd-smb --spawner :1.4 /org/gtk/gvfs/exec_spaw/5
comment:        using thunar file manager in xfce to browse a samba (ubuntu) share.
executable:     /usr/libexec/gvfsd-smb
kernel:         3.2.7-1.fc16.i686
pid:            5476
pwd:            /
reason:         Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT)
time:           Tue 28 Feb 2012 10:46:13 PM NZDT
uid:            1000
username:       richard
var_log_messages: Feb 28 22:46:13 r51e abrt[5482]: Saved core dump of pid 5476 (/usr/libexec/gvfsd-smb) to /var/spool/abrt/ccpp-2012-02-28-22:46:13-5476 (27066368 bytes)

backtrace:      Text file, 13582 bytes
dso_list:       Text file, 4683 bytes
maps:           Text file, 13137 bytes



:UUID: 043ec862-d027-4d92-8a65-73aaaaac6e80
:OS: Fedora release 16 (Verne)
:Default run level: Unknown
:Language: en_US.UTF-8
:Platform: i686
:BogoMIPS: 2792.22
:CPU Vendor: GenuineIntel
:CPU Model: Intel(R) Celeron(R) M processor         1.40GHz
:CPU Stepping: 8
:CPU Family: 6
:CPU Model Num: 13
:Number of CPUs: 1
:CPU Speed: 1400
:System Memory: 874
:System Swap: 1759
:Vendor: IBM
:System: 184336M ThinkPad R51e
:Form factor: Notebook
:Kernel: 3.2.7-1.fc16.i686
:SELinux Enabled: 1
:SELinux Policy: targeted
:SELinux Enforce: Enforcing
:MythTV Remote: Unknown
:MythTV Role: Unknown
:MythTV Theme: Unknown
:MythTV Plugin: 
:MythTV Tuner: -1
:(4098:23096:4116:1438) pci, pcieport, PCI/PCI, RS480 PCI Bridge
:(4172:44118:5136:1320) pci, yenta_cardbus, PCI/CARDBUS, PCI1510 PC card Cardbus Controller
:(4098:17270:4116:1427) pci, pata_atiixp, STORAGE, IXP SB400 IDE Controller
:(4098:17266:4116:1426) pci, piix4_smbus, SERIAL, IXP SB400 SMBus Controller
:(4098:17271:4116:1428) pci, None, PCI/ISA, IXP SB400 PCI-ISA Bridge
:(4098:17264:4116:1414) pci, snd_atiixp, MULTIMEDIA_AUDIO, IXP SB400 AC'97 Audio Controller
:(4098:17265:0:0) pci, None, PCI/PCI, IXP SB400 PCI-PCI Bridge
:(4098:17272:4116:1415) pci, snd_atiixp_modem, SIMPLE, SB400 AC'97 Modem Controller
:(4098:23138:4116:1437) pci, radeon, VIDEO, RC410 [Radeon Xpress 200M]
:(5348:5758:4116:1405) pci, tg3, ETHERNET, NetXtreme BCM5751F Fast Ethernet PCI Express
:(4098:23094:4116:1438) pci, pcieport, PCI/PCI, RS480 PCI Bridge
:(4098:17267:4116:1425) pci, ehci_hcd, USB, IXP SB400 USB2 Host Controller
:(5772:19:5224:1032) pci, ath5k, ETHERNET, ThinkPad 11b/g Wireless LAN Mini PCI Adapter
:(4098:23089:4116:1413) pci, None, HOST/PCI, N/A
:(4098:17269:4116:1424) pci, ohci_hcd, USB, IXP SB400 USB Host Controller
:(4098:17268:4116:1423) pci, ohci_hcd, USB, IXP SB400 USB Host Controller
:(4098:23103:4116:1429) pci, None, PCI/PCI, RS480 PCI Bridge
:Filesystem Information
:device mtpt type bsize frsize blocks bfree bavail file ffree favail
:/dev/mapper/vg_r51e-lv_root / ext4 4096 4096 5686282 3710279 3653367 1425408 1265306 1265306
:/dev/sda2 /boot ext4 1024 1024 508745 412531 386931 128016 127781 127781
Comment 1 Richard Haakma 2012-02-28 18:45:50 EST
Created attachment 566419 [details]
File: dso_list
Comment 2 Richard Haakma 2012-02-28 18:45:52 EST
Created attachment 566421 [details]
File: maps
Comment 3 Richard Haakma 2012-02-28 18:45:54 EST
Created attachment 566422 [details]
File: backtrace
Comment 4 Fedora End Of Life 2013-01-16 13:45:38 EST
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
Comment 5 Fedora End Of Life 2013-02-13 17:51:48 EST
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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.