Bug 1202282

Summary: [abrt] bluefish: fill_uri(): bluefish killed by SIGSEGV
Product: [Fedora] Fedora Reporter: nuno ferreira <self>
Component: bluefishAssignee: Paul Howarth <paul>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: paul, peljasz, wisekaa03
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/836626d0f6079dd25f8f5d6dc50db7bf2569c9df
Whiteboard: abrt_hash:21d7037359e647dd5ae10d88f6befd63f31ee321
Fixed In Version: bluefish-2.2.8-1.fc22 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-02-02 23:53:05 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: open_fds
none
File: proc_pid_status none

Description nuno ferreira 2015-03-16 09:53:57 UTC 
Description of problem:
opened html file in nemo (cinnamon) that was stored in smb folder and bluefish crashed.

Version-Release number of selected component:
bluefish-2.2.7-1.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        bluefish /run/user/1000/gvfs/smb-share:server=192.168.99.100,share=web/html/homeostatos/index.html
crash_function: fill_uri
executable:     /usr/bin/bluefish
kernel:         3.18.9-200.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000
var_log_messages: [System Logs]:\n-- Logs begin at Sáb 2015-01-10 22:15:41 WET, end at Seg 2015-03-16 09:49:05 WET. --

Truncated backtrace:
Thread no. 1 (7 frames)
 #0 fill_uri at file_treemodel.c:462
 #1 add_multiple_uris at file_treemodel.c:817
 #2 enumerate_next_files_lcb at file_treemodel.c:889
 #3 next_async_callback_wrapper at gfileenumerator.c:305
 #4 g_simple_async_result_complete at gsimpleasyncresult.c:763
 #5 complete_in_idle_cb at gsimpleasyncresult.c:775
 #10 gtk_main at gtkmain.c:1207

Potential duplicate: bug 1066710
Comment 1 nuno ferreira 2015-03-16 09:54:00 UTC 
Created attachment 1002174 [details]
File: backtrace
Comment 2 nuno ferreira 2015-03-16 09:54:01 UTC 
Created attachment 1002175 [details]
File: cgroup
Comment 3 nuno ferreira 2015-03-16 09:54:02 UTC 
Created attachment 1002176 [details]
File: core_backtrace
Comment 4 nuno ferreira 2015-03-16 09:54:04 UTC 
Created attachment 1002177 [details]
File: dso_list
Comment 5 nuno ferreira 2015-03-16 09:54:05 UTC 
Created attachment 1002178 [details]
File: environ
Comment 6 nuno ferreira 2015-03-16 09:54:06 UTC 
Created attachment 1002179 [details]
File: exploitable
Comment 7 nuno ferreira 2015-03-16 09:54:07 UTC 
Created attachment 1002180 [details]
File: limits
Comment 8 nuno ferreira 2015-03-16 09:54:08 UTC 
Created attachment 1002181 [details]
File: maps
Comment 9 nuno ferreira 2015-03-16 09:54:09 UTC 
Created attachment 1002182 [details]
File: open_fds
Comment 10 nuno ferreira 2015-03-16 09:54:10 UTC 
Created attachment 1002183 [details]
File: proc_pid_status
Comment 11 Paul Howarth 2015-03-17 12:35:59 UTC 
Reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=746342
Comment 12 Paul Howarth 2015-10-29 10:18:34 UTC 
Upstream says this is fixed in upcoming 2.2.8 release.
Comment 13 Fedora End Of Life 2015-11-04 15:54:44 UTC 
This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. 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 EOL if it remains open with a Fedora  'version'
of '21'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.
Comment 14 lejeczek 2015-12-17 15:00:40 UTC 
Another user experienced a similar problem:

I tried to open a .xml file from a gvfs samba mount.

reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        bluefish /run/user/1000/gvfs/smb-share:server=172.25.12.203,share=it.related/vpnToCCNR/ccnr.xml
crash_function: fill_uri
executable:     /usr/bin/bluefish
global_pid:     30982
kernel:         4.4.0-0.rc4.git2.1.fc24.x86_64
package:        bluefish-2.2.7-1.fc22
reason:         bluefish killed by SIGSEGV
runlevel:       N 5
type:           CCpp
uid:            1000
Comment 15 Fedora Update System 2016-01-25 10:07:22 UTC 
bluefish-2.2.8-1.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2016-0e9815baf0
Comment 16 Fedora Update System 2016-01-26 04:23:29 UTC 
bluefish-2.2.8-1.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-0e9815baf0
Comment 17 Fedora Update System 2016-02-02 23:53:01 UTC 
bluefish-2.2.8-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Comment 18 Paul Howarth 2016-02-03 12:56:46 UTC 
*** Bug 1304373 has been marked as a duplicate of this bug. ***