Package: gedit-source-code-browser-plugin
Version: 3.0.3-3
Severity: important

Hi,

This plugin does not work with gedit 3.12 - the tab in the side panel to
browse the source never appears.

I also get various errors while using gedit:
  Traceback (most recent call last):
    File "/usr/lib/gedit/plugins/sourcecodebrowser/plugin.py", line 333, in 
do_activate
      panel.add_item(self._sourcetree, "SymbolBrowserPlugin", "Source Code", 
self.icon)
  AttributeError: 'Stack' object has no attribute 'add_item'

  Traceback (most recent call last):
    File "/usr/lib/gedit/plugins/sourcecodebrowser/plugin.py", line 352, in 
do_deactivate
      for obj, hid in self._handlers:
  AttributeError: 'SourceCodeBrowserPlugin' object has no attribute '_handlers'

  Traceback (most recent call last):
    File "/usr/lib/gedit/plugins/sourcecodebrowser/plugin.py", line 452, in 
on_setting_changed
      self._load_active_document_symbols()
    File "/usr/lib/gedit/plugins/sourcecodebrowser/plugin.py", line 396, in 
_load_active_document_symbols
      if not panel.item_is_active(self._sourcetree):
  AttributeError: 'Stack' object has no attribute 'item_is_active'

Thanks,
James

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gedit-source-code-browser-plugin depends on:
ii  dconf-gsettings-backend [gsettings-backend]  0.20.0-2
ii  exuberant-ctags [ctags]                      1:5.9~svn20110310-7
ii  gedit                                        3.12.1-1
pn  python:any                                   <none>

gedit-source-code-browser-plugin recommends no packages.

gedit-source-code-browser-plugin suggests no packages.

-- no debconf information


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to