tuxpaint displays warnings at startup such as: Error: plugin /usr/lib/tuxpaint/plugins/puzzle.so is missing get_tool_count Error: plugin /usr/lib/tuxpaint/plugins/puzzle.so is missing get_name Error: plugin /usr/lib/tuxpaint/plugins/puzzle.so is missing get_icon for the puzzle.so plugin. Sure enough, puzzle.so seems to be missing just about all exports: $ nm -D /usr/lib/tuxpaint/plugins/puzzle.so w _Jv_RegisterClasses 000014c0 A __bss_start w __cxa_finalize w __gmon_start__ 000014c0 A _edata 000014c8 A _end 000003a8 T _fini 00000248 T _init compared to the other plugins in that directory, which seem to have all the exports that tuxpaint complains about (with a prefix equal to the plugin name). There is also no sign of the puzzle plugin in the tuxpaint GUI at run-time.
Hi, thanks for reporting this bug. Assigned to the package maintainer. (Please set the status to 'assigned' if you are working on it)
Keywords: (none) => TriagedAssignee: bugsquad => anaselli
Fixed in cauldron using an upstream patch. That plugin seems to be commented so not built. I will provide an update for mga 1 as soon as possible.
URL: (none) => http://sourceforge.net/mailarchive/forum.php?thread_name=E1Maq0u-0007Bk-1p%40ddv4jf1.ch3.sourceforge.com&forum_name=tuxpaint-cvs
There is now tuxpaint-0.9.21-3.1 in core/updates_testing to validate: RPMS: tuxpaint-0.9.21-3.1.mga1 tuxpaint-debug-0.9.21-3.1.mga1 tuxpaint-devel-0.9.21-3.1.mga1 SRPMS: tuxpaint-0.9.21-3.1.mga1.src.rpm advisory text: Tuxpaint 0.9.21 was released without puzzle stamp, and that produced some errors on startup. This package fixed this issue adding puzzle back.
Status: NEW => ASSIGNED
Assignee: anaselli => qa-bugs
Testing complete on i586 for the srpm tuxpaint-0.9.21-3.1.mga1.src.rpm Before the update, several errors in the console such as Error: plugin /usr/lib/tuxpaint/plugins/puzzle.so is missing get_tool_count After the update, no errors.
CC: (none) => davidwhodgins
Tested OK x86_64 but I did notice another bug with tuxpaint. It isn't a regression and not a blocker so I'll create another bug for it. When I create a pretty picture and print it, it returns a message saying "Sorry" Your picture could not be printed.". It does actually print it though. In the print queue and cups logs it appears as being sent from (stdin) and not tuxpaint. Validating this update. Advisory -------- Tuxpaint 0.9.21 was released without puzzle stamp, and that produced some errors on startup. This package fixes the issue, adding puzzle back. -------- SRPM: tuxpaint-0.9.21-3.1.mga1.src.rpm Could sysadmin please push from core/updates_testing to core/updates Thankyou!
Keywords: Triaged => validated_updateCC: (none) => sysadmin-bugsHardware: i586 => All
CC: (none) => anaselli
Bug 4379 created for printing problem
Claire, i don't think printing problem is a regression. Can someone confirm that also?
I mean that is not a regression but an already existing problem :)
No it isn't a regression Angelo, it is present in release version also. I mentioned in comment 5 and the on other bug. This update has been validated and awaiting push, unless you want to apply a fix for the printing problem (bug 4379) first? If you do then please set it as "depends on" bug 4379 and leave a comment. The printing error problem can be handled separately in bug 4379 and both bugs closed together with one update pushed. Otherwise this one will be pushed and another later. Thanks!
Claire this bug can be closed and the update pushed. About bug 4379 I have to investigate the printing problem and look for an upstream patch if there is any, or trying to fix it, if i am able of course :)
Thanks Angelo Sysadmin please push, see comment 5 for details. Thankyou!
update pushed
Status: ASSIGNED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED