OK, this bug is really freaking me out; I've studied all the code paths leading up to it about half a dozen times and can't figure out how it could be happening.
Could somebody who can reproduce this exact problem (crash dump ending with "RuntimeError: first member of each text/response id pair must be a string") please:
* Open /usr/lib/python2.4/site-packages/ubiquity/frontend/gtkui.py in a text editor (you'll need to start the text editor as root);
* Search for "gtk.Dialog" until you find the line reading "dialog = gtk.Dialog(title, transient, gtk.DIALOG_MODAL, tuple(buttons))" (should be the first match, I think);
* Insert a line *above* that line as follows:
print >>sys.stderr, title, msg, option_templates, self.locale, buttons
Make sure you enter this exactly as above on a single line (no word-wrapping), and that the line begins with eight (8) spaces;
* Run the installer again and reproduce the problem;
* Attach the resulting /var/log/installer/syslog file to this bug report.
With any luck that should provide me with enough information to track this down. Thanks in advance!
OK, this bug is really freaking me out; I've studied all the code paths leading up to it about half a dozen times and can't figure out how it could be happening.
Could somebody who can reproduce this exact problem (crash dump ending with "RuntimeError: first member of each text/response id pair must be a string") please:
* Open /usr/lib/ python2. 4/site- packages/ ubiquity/ frontend/ gtkui.py in a text editor (you'll need to start the text editor as root); installer/ syslog file to this bug report.
* Search for "gtk.Dialog" until you find the line reading "dialog = gtk.Dialog(title, transient, gtk.DIALOG_MODAL, tuple(buttons))" (should be the first match, I think);
* Insert a line *above* that line as follows:
print >>sys.stderr, title, msg, option_templates, self.locale, buttons
Make sure you enter this exactly as above on a single line (no word-wrapping), and that the line begins with eight (8) spaces;
* Run the installer again and reproduce the problem;
* Attach the resulting /var/log/
With any luck that should provide me with enough information to track this down. Thanks in advance!