With the bug hunt out of the way, the last bit of bug fixing work is to attend any MustFix bugs. These are extremely serious bugs such as ones that cause frequent crashes, or that risk bad data loss.
I've gone through the current (as of 1/8/07) bug list and separated out the ones that a) we don't have enough info to debug, b) are out of our hands anyway, or c) don't cause crashes or data loss.
Please review this list and identify any you can show to be must fix bugs.
For a bug to be nominated to be a MUST FIX bug, it must also include a willing owner who can work on it right now, and some form of a plan for what to do about it. (Otherwise, blocking on it may prove unproductive.)
CRASHES OR DATA LOSS ------------------------------------------------------------------------ 1515192 make check failure 1630485 Inkview don't support blur / crashes 1630101 crash inkscape click in connectors network aling 1575829 Metadata are truncated at 4 chars and add a char 18 hexa 1464771 whiteboard: cannot connect to jabber server then crashses
REQUIRES UPSTREAM ACTION ------------------------------------------------------------------------ 969321 "Dialogs on top" does not work on Windows
REQUIRES MORE INFORMATION OR CONFIRMATION ------------------------------------------------------------------------ 1627110 Assertion hit in inkscape_get_repr when getting prefs 1612057 memory limit at 1GB 1538282 crash when switching to selection tool 1519462 OpenBSD: Inkscape hangs/segfaults 1418122 Conf corruption when opening files with non-UTF encoded 1507967 [INFO NEEDED] Cannot open svgz 1516476 build problems on Solaris 1395505 0.43 crash at startup on Win98se 1614820 Crash when moving nodes in XML Editor after duplicate. 1603579 Crash open file dialog start directory with 1513877 autopackage libcairo.so.2 dependency problem 1508157 GDKpixbufInput files to Init on SuSE 10.1 with 0.44pre4 1503564 win2003 SP1: crash on start 1467137 Shrinking a pattern causes lock-up 1624076 Crash after changing canvas size fields by click 1499971 detect and warn about installed libsmooth 1496718 Text paragraph display problem on OS X
MISBEHAVIOR BUT NO CRASH OR DATA LOSS ------------------------------------------------------------------------ 1469554 fixed length toolbars prevent working on narrow screens 1494967 Text toolbar: too difficult to close fonts drop-down 1495039 whiteboard backtrace reveals sensitive information 1448618 Fonts weight variants selection 1441003 flowRoot error with inkscape's svg 937347 symbol fonts not supported? 1586421 Mandarin TEXT RENDERING problem 1584935 blur not exported to pdf 1519730 Linked offset performance issues 1513484 icc compile error 1441767 OpenType fonts with postscript outlines not supported. 1370904 isnan issue, sun Solaris 8 gcc 1143821 COPY/PASTE doesn't work with system clipboard 1505549 drag and delete line crash Inkscape 0.45devel (crash fixed)
Bryce
I think these are certainly stoppers:
1630485 Inkview don't support blur / crashes 1575829 Metadata are truncated at 4 chars and add a char 18 hexa
Dunno about other listed as "crashers". Actually, I would like to caution people against overzealous bug fixing at this point. To avoid destabilizing, please concentrate either on serious crash bugs or on bugs which can be fixed as unintrusively as possible. Some of the bugs Bryce listed a more of RFEs than bugs, and now is certainly not the right time to work on them in the trunk (of course you can work on them locally to commit when 0.45 is out).
On Wed, Jan 10, 2007 at 04:40:13AM -0500, bulia byak wrote:
I think these are certainly stoppers:
1630485 Inkview don't support blur / crashes 1575829 Metadata are truncated at 4 chars and add a char 18 hexa
Do you have willing owners for these, and/or can you identify a plan for fixing them?
I assigned the latter bug to kees, but I should note that he will be out of the country for the next few weeks so will be unable to do bugfixes. Thus, if the metadata bug is to be considered a blocker, it must have someone else identified to own and resolve it.
I have a feeling that if a coder can reproduce the bug, it sounds like it should be very straightforward to fix.
Bryce
On 1/10/07, Bryce Harrington <bryce@...961...> wrote:
1630485 Inkview don't support blur / crashes
This one is fixed now.
On Wed, Jan 10, 2007 at 02:59:24AM -0800, Bryce Harrington wrote:
On Wed, Jan 10, 2007 at 04:40:13AM -0500, bulia byak wrote:
I think these are certainly stoppers:
1575829 Metadata are truncated at 4 chars and add a char 18 hexa
I assigned the latter bug to kees, but I should note that he will be out
With some help from mental, this is now fixed. General warning about using the .c_str() function on Glib::ustring's returned from objects: don't use 'em: they can get trashed on the heap. Instead, use a local Glib::ustring, and call it's .c_str() when you need it.
e.g.
No: char * str = Node->contents().c_str(); do_something( str );
Yes: Glib::ustring str = Node->contents(); do_something( str.c_str() );
On Fri, Jan 12, 2007 at 05:48:14PM -0800, Kees Cook wrote:
On Wed, Jan 10, 2007 at 02:59:24AM -0800, Bryce Harrington wrote:
On Wed, Jan 10, 2007 at 04:40:13AM -0500, bulia byak wrote:
I think these are certainly stoppers:
1575829 Metadata are truncated at 4 chars and add a char 18 hexa
I assigned the latter bug to kees, but I should note that he will be out
With some help from mental, this is now fixed. General warning about using the .c_str() function on Glib::ustring's returned from objects: don't use 'em: they can get trashed on the heap. Instead, use a local Glib::ustring, and call it's .c_str() when you need it.
e.g.
No: char * str = Node->contents().c_str(); do_something( str );
Yes: Glib::ustring str = Node->contents(); do_something( str.c_str() );
Cool, thanks for sorting this one out Kees!
Bryce
Kees Cook spiegò:
With some help from mental, this is now fixed. General warning about using the .c_str() function on Glib::ustring's returned from objects: don't use 'em: they can get trashed on the heap. Instead, use a local Glib::ustring, and call it's .c_str() when you need it.
e.g.
No: char * str = Node->contents().c_str(); do_something( str );
Yes: Glib::ustring str = Node->contents(); do_something( str.c_str() );
Just curious: any idea why?
Emanuele Aina wrote:
Kees Cook spiegò:
With some help from mental, this is now fixed. General warning about using the .c_str() function on Glib::ustring's returned from objects: don't use 'em: they can get trashed on the heap. Instead, use a local Glib::ustring, and call it's .c_str() when you need it.
e.g.
No: char * str = Node->contents().c_str(); do_something( str );
Yes: Glib::ustring str = Node->contents(); do_something( str.c_str() );
Just curious: any idea why?
My guess (I haven't checked) would be that Node->contents() returns a temporary object, like this for example: ----------- // Code return Glib::ustring("foobar"); } ----------- This object would only live for the duration of the statement in which Node->contents() is called and would therefore be gone when do_something is called. If that is the case something like this may have also solved this particular bug (although it depends a bit on what do_something does): ----------- do_something( Node->contents().c_str() ); -----------
All,
On Win32 when I use a daily snapshot all menus are not localized. The remain in plain English. (except some buttons from standard dialogs)
When I use a previous 0.44 menus gets localized perfectly. So I guess it is not settings related. I mentioned this some times in the chat to get a confirmation or negative response but there was no feedback. Thats why I did not post a defect for this.
If this is confirmed to be a bug this is also a must-fix.
pls win32-developer or tester give some feedback.
Adib. ---
Bryce Harrington schrieb:
With the bug hunt out of the way, the last bit of bug fixing work is to attend any MustFix bugs. These are extremely serious bugs such as ones that cause frequent crashes, or that risk bad data loss.
I've gone through the current (as of 1/8/07) bug list and separated out the ones that a) we don't have enough info to debug, b) are out of our hands anyway, or c) don't cause crashes or data loss.
Please review this list and identify any you can show to be must fix bugs.
For a bug to be nominated to be a MUST FIX bug, it must also include a willing owner who can work on it right now, and some form of a plan for what to do about it. (Otherwise, blocking on it may prove unproductive.)
CRASHES OR DATA LOSS
1515192 make check failure 1630485 Inkview don't support blur / crashes 1630101 crash inkscape click in connectors network aling 1575829 Metadata are truncated at 4 chars and add a char 18 hexa 1464771 whiteboard: cannot connect to jabber server then crashses
REQUIRES UPSTREAM ACTION
969321 "Dialogs on top" does not work on Windows
REQUIRES MORE INFORMATION OR CONFIRMATION
1627110 Assertion hit in inkscape_get_repr when getting prefs 1612057 memory limit at 1GB 1538282 crash when switching to selection tool 1519462 OpenBSD: Inkscape hangs/segfaults 1418122 Conf corruption when opening files with non-UTF encoded 1507967 [INFO NEEDED] Cannot open svgz 1516476 build problems on Solaris 1395505 0.43 crash at startup on Win98se 1614820 Crash when moving nodes in XML Editor after duplicate. 1603579 Crash open file dialog start directory with 1513877 autopackage libcairo.so.2 dependency problem 1508157 GDKpixbufInput files to Init on SuSE 10.1 with 0.44pre4 1503564 win2003 SP1: crash on start 1467137 Shrinking a pattern causes lock-up 1624076 Crash after changing canvas size fields by click 1499971 detect and warn about installed libsmooth 1496718 Text paragraph display problem on OS X
MISBEHAVIOR BUT NO CRASH OR DATA LOSS
1469554 fixed length toolbars prevent working on narrow screens 1494967 Text toolbar: too difficult to close fonts drop-down 1495039 whiteboard backtrace reveals sensitive information 1448618 Fonts weight variants selection 1441003 flowRoot error with inkscape's svg 937347 symbol fonts not supported? 1586421 Mandarin TEXT RENDERING problem 1584935 blur not exported to pdf 1519730 Linked offset performance issues 1513484 icc compile error 1441767 OpenType fonts with postscript outlines not supported. 1370904 isnan issue, sun Solaris 8 gcc 1143821 COPY/PASTE doesn't work with system clipboard 1505549 drag and delete line crash Inkscape 0.45devel (crash fixed)
Bryce
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=D... _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Adib Taraben wrote:
On Win32 when I use a daily snapshot all menus are not localized. The remain in plain English. (except some buttons from standard dialogs)
I indeed also experience this. It has to do with how the compiled language files are copied to the distribution dir. If I go to my locale dir (NL) and rename nl.mo to inkscape.mo and put it in directory "LC_MESSAGES", it works perfectly. I think this bug was introduced when we transferred to the (really amazing) buildtool + build.xml?
Indeed, this is a must fix.
On Wed, Jan 10, 2007 at 03:07:49PM +0100, J.B.C.Engelen@...1578... wrote:
Adib Taraben wrote:
On Win32 when I use a daily snapshot all menus are not localized. The remain in plain English. (except some buttons from standard dialogs)
I indeed also experience this. It has to do with how the compiled language files are copied to the distribution dir. If I go to my locale dir (NL) and rename nl.mo to inkscape.mo and put it in directory "LC_MESSAGES", it works perfectly. I think this bug was introduced when we transferred to the (really amazing) buildtool + build.xml?
Indeed, this is a must fix.
Is there a bug ID for this one? Also, for it to be a must fix, it must have an owner and a plan for how to achieve a fix. Who will adopt this bug or suggest an approach for fixing it?
Bryce
Bryce Harrington schrieb:
On Wed, Jan 10, 2007 at 03:07:49PM +0100, J.B.C.Engelen@...1578... wrote:
Adib Taraben wrote:
On Win32 when I use a daily snapshot all menus are not localized. The remain in plain English. (except some buttons from standard dialogs)
I indeed also experience this. It has to do with how the compiled language files are copied to the distribution dir. If I go to my locale dir (NL) and rename nl.mo to inkscape.mo and put it in directory "LC_MESSAGES", it works perfectly. I think this bug was introduced when we transferred to the (really amazing) buildtool + build.xml?
Indeed, this is a must fix.
Is there a bug ID for this one? Also, for it to be a must fix, it must have an owner and a plan for how to achieve a fix. Who will adopt this bug or suggest an approach for fixing it?
Bryce
I put one: 1632740 localisation does not work on Win32 http://sourceforge.net/tracker/index.php?func=detail&aid=1632740&gro...
HTH,
Adib. ---
participants (7)
-
unknown＠example.com -
Adib Taraben -
Bryce Harrington -
bulia byak -
Emanuele Aina -
Jasper van de Gronde -
Kees Cook