Segmentation fault on startup

Bug #340101 reported by Dennis Rasey
4
Affects Status Importance Assigned to Milestone
RedNotebook
Fix Released
High
Jendrik Seipp

Bug Description

I *think* this might be separate from 320492.

Using 0.6.1 on Ubuntu Jaunty, I receive a Seg Fault when trying to start RedNotebook.

AppDir: /usr/local/lib/python2.6/dist-packages/rednotebook
BaseDir: /usr/local/lib/python2.6/dist-packages
location: /usr/lib/xulrunner-1.9.0.7/libxpcom.so
before 3
First Start: False
The config file /usr/local/lib/python2.6/dist-packages/rednotebook/files/default.cfg was read
The config file /home/drasey/.rednotebook/configuration.cfg was read
Configuration has been saved
The environment variable LD_LIBRARY_PATH has value /usr/lib/xulrunner-1.9
The environment variable MOZILLA_FIVE_HOME has value /usr/lib/xulrunner-1.9
/usr/local/lib/python2.6/dist-packages/rednotebook/gui/mainWindow.py:70: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
  self.wTree = gtk.glade.XML(self.gladefile)
/usr/local/lib/python2.6/dist-packages/rednotebook/gui/mainWindow.py:330: Warning: g_object_ref: assertion `G_IS_OBJECT (object)' failed
  edit_toolbar.insert(single_menu_toolbutton, -1)
Segmentation fault (core dumped)

I've tried changing both the xulrunner path & disabling it (useGTKMozembed=0), in both configs (~/.rednotebook/configuration.cfg & /usr/local/lib/python2.6/dist-packages/rednotebook/files/default.cfg), to no avail.

I've also tried using python 2.5, similar result (though I'm not sure if I properly removed everything from python2.6)

v0.5.6 seems to startup fine (was this pre-PyGTK?)

Revision history for this message
Jendrik Seipp (jendrikseipp) wrote :

Does the error still happen with version 0.6.2?

Revision history for this message
Dennis Rasey (drasey) wrote :

Hi Jendrik,
I was just about to write saying the new released has fixed this for me; you beat me to it ;)

-Dennis

Changed in rednotebook:
assignee: nobody → Jendrik Seipp (jendrikseipp)
importance: Undecided → High
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.