Bug 583269 - [abrt] crash in gedit-1:2.28.3-1.fc12: functions.py:282:capture_end_execute_panel:AttributeError: 'gtk.TextBuffer' object has no attribute 'get_uri'
[abrt] crash in gedit-1:2.28.3-1.fc12: functions.py:282:capture_end_execute_p...
Product: Fedora
Classification: Fedora
Component: gedit (Show other bugs)
i686 Linux
low Severity medium
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-04-17 10:37 EDT by bvishal
Modified: 2010-12-03 10:46 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-12-03 10:46:35 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: backtrace (930 bytes, text/plain)
2010-04-17 10:37 EDT, bvishal
no flags Details

  None (edit)
Description bvishal 2010-04-17 10:37:20 EDT
abrt 1.0.8 detected a crash.

architecture: i686
cmdline: gedit
component: gedit
executable: /usr/lib/gedit-2/plugins
package: gedit-1:2.28.3-1.fc12
reason: functions.py:282:capture_end_execute_panel:AttributeError: 'gtk.TextBuffer' object has no attribute 'get_uri'
release: Fedora release 12 (Constantine)

functions.py:282:capture_end_execute_panel:AttributeError: 'gtk.TextBuffer' object has no attribute 'get_uri'

Traceback (most recent call last):
  File "/usr/lib/gedit-2/plugins/externaltools/functions.py", line 282, in capture_end_execute_panel
    language = lmanager.guess_language(doc.get_uri(), mtype)
AttributeError: 'gtk.TextBuffer' object has no attribute 'get_uri'

Local variables in innermost frame:
lmanager: <gtksourceview2.LanguageManager object at 0xa0859dc (GtkSourceLanguageManager at 0x9580aa0)>
end: <GtkTextIter at 0xa21a448>
capture: <Capture object at 0xa0f861c (externaltools+capture+Capture at 0xa23df40)>
doc: <gtk.TextBuffer object at 0xa0f8c84 (GtkTextBuffer at 0x99cac40)>
exit_code: 0
mtype: 'text/plain'
start: <GtkTextIter at 0xa13eb38>
output_type: 'new-document'
panel: <externaltools.outputpanel.OutputPanel instance at 0xa0f4d8c>
view: <gedit.View object at 0xa0f8554 (GeditView at 0x9684678)>
Comment 1 bvishal 2010-04-17 10:37:23 EDT
Created attachment 407274 [details]
File: backtrace
Comment 2 Bug Zapper 2010-11-03 12:54:31 EDT
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  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 '12'.

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 12'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 12 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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 3 Bug Zapper 2010-12-03 10:46:35 EST
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.