| Summary: | gscan2pdf does not allow saving of files due to an interaction bug with the perl Gtk2 bindings | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Alberto Girlando <girlando> |
| Component: | RPM Packages | Assignee: | Jerome Quelin <jquelin> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | High | CC: | DShelbyD, jquelin, longlegged.guy, marja11, pterjan, thierry.rouillon, thierry.vignaud, valdemar, yann |
| Version: | 1 | Keywords: | Triaged |
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| URL: | https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/608695 | ||
| Whiteboard: | |||
| Source RPM: | gscan2pdf 0.9.32, release 5.mga1, perl-Gtk2-1.230.0-5.mga1 | CVE: | |
| Status comment: | |||
|
Description
Alberto Girlando
2011-06-16 12:13:16 CEST
I found https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/608695 which says that the problem is with the perl-Gtk2 bindings, the problem is we can't revert to the older version, so this bug should be fixed in gscan2pdf... Adding the perl maintainer to CC. Keywords:
(none) =>
Triaged Yep, I just got bitten by this bug after scanning 17 pages a couple of nights ago. I hope they get this fixed upstream and soon, because that was downright inconvenient, to say it with civility! ;-) CC:
(none) =>
DShelbyD The Ubuntu folks seem to have the problem fixed as of 2011-08-10. Are we able to do the same? It seemed to have to do with syncing to new versions of libglib-perl and libgtk2-perl per what I see in the bug thread Ahmad links to above.
Valdemar Boersting
2011-09-07 12:37:47 CEST
CC:
(none) =>
valdemar If the problem is the same one exhibited in Unbuntu, it's understood and easily fixed. Is Mageia just going to wait for its next release? Nothing really beats gscan2pdf for simply scanning paper pages into a pdf. It's unusable if it can't save. I understand that Mageia resources are limited, but what's the point of a distribution that has basic features broken and no ability to repair them even when the problem is well understood.
Aaron Sosnick
2011-09-28 04:14:31 CEST
Priority:
Normal =>
High aaron, this bug is not critical. critical means distribution cannot be distributed, which is not the case. back to the problem - ubuntu just synced perl-Gtk2 to 1.222 while we are already shipping 1.231, and perl-Glib 1.223 while we are shipping 1.232 i'm adding thierry in copy, since he's the one really following the releases. ==> thierry, is the bug known upstream? CC:
(none) =>
thierry.vignaud They didn't specify which change actually fixed it. There weren't that many changes in 1.222. The only non test change was "Make Gtk2::ListStore->remove()'s return value consistent on gtk+ 2.0" That fix ended in master on 2009-12-17 and thus ended in 1.230 we shipped in Mageia 1. So we would need to ask ubuntu maintainer about what exactly was the issue. Does it work better on Cauldron? URL:
(none) =>
https://bugs.launchpad.net/ubuntu/+source/gscan2pdf/+bug/608695 Especially, does Cauldron's perl-Gtk2-1.232 fixes it? Keywords:
(none) =>
NEEDINFO I am not a developer, but simply a user (also if I try to cooperate as much as I can). So I do not have a unstable installation for testing. I tried to download gscan2pdf from Cauldron. It did not install as a more recent version of perl-base was required. I downloaded also that one, but then the program ask to install many other libraries and programs, some also for i586 (I have a 64 bit release). So I stopped there, I did not want to spoil my system. Same as above when I tried to install the only perl-GTK2. Tried also to force installation of gscan2pdf alone, but then it did not work. I have to say that since Mandriva decided to shift to KDE-only system, I would like to pass definitely to Mageia. However, I am stopped in installing it on my portable computer, just for the problem of gscan2pdf, that I need in my work.
Yann Lejeune
2011-10-12 21:27:41 CEST
CC:
(none) =>
yann On a up-to-date Cauldron (gscan2pdf 1.0.0 and perl-Gtk2-1.232), I don't see the problem. I tried again, forcing the installation of the above packages (plus perl-Glib). gscan2pdf does not start (other pieces of perl are needed, but perl is important for many other programs), including drakconf. So I had problem in removing the packages I have installed by Cauldron. I made a new installation of mageia (32) on virtualbox. Added cauldron repos, and installed directly gscan2pdf and all the related software the *.rpm was asking. So the version I installed was the 1.0.0 - the cauldron one. When I ran the program from a terminal windows, I have got the message: *** This build of Glib was compiled with Glib 2.30.0, but is currently running with 2.28.6, which is too old. We'll continue, but expect problems ! *** This build of Gtk2 was compiled with gtk+ 2.24.6, but is currently running with 2.24.4, which is too old. We'll continue, but expect problems ! Then the program opens, and seems to be working well, except of course at the save process. In this case, it writes an empty pdf, and crashes without further warning or message. There is some other trial I should do, for instance upgrading Glib and Gtk2 ? Incidentally, now drakconf does not start, due to a symbol lookup error in perl ! As I said in my previous message, I wish to help, but I am not an expert, so please tell me what also have to try. @ Alberto When you installed Mageia on virtual box, which of the following did you do: 1) add cauldron repos and immediately afterwards install gscan2pdf 2) first update to cauldron and install gscan2pdf afterwards If you did 1), it was bound to fail. It is a pity we don't have a gscan2pdf maintainer cc'ing one more person from the changelog CC:
(none) =>
marja11, pterjan Too much time has passed... I probably followed route 1), but then for sure I also tried to upgrade all the software in Cauldron. But did not help. As soon I have some spare time, I will try route 2 (maybe also Cauldron has changed in between). The Ubuntu bug points to Debian bug which was resolved by reverting to stable perl-Gtk2-1.222 as 1.230 introduced the bug. It also points to https://bugzilla.gnome.org/show_bug.cgi?id=549138 which for some unknown reason is still open 3 years later while the reporter, a perl-Gtk developer, attached a patch at that time. To Marja: Yes, I finally follow route 2 completely, by following instruction to pass to the complete cauldron release (if I remember properly, before I have added the repo, without removing the normal ones). gscan2pdf is working in Cauldron (32 bit). Does it mean that is working (or will be working) in Mageia 2 ? I don't know if I have to close this bug. Probably not, because in non-Cauldron it is not working, and myself and other do not want to use Cauldron for production, but only for testing (I installed it on virtualbox). @ Alberto Thanks for the feedback :) It means it is expected to work in Mageia 2 stable and that it would surprise me if it doesn't (current cauldron is Mageia 2 Alpha 3). You're right, this report should stay open for Mageia 1. (In reply to comment #15) > The Ubuntu bug points to Debian bug which was resolved by reverting to stable > perl-Gtk2-1.222 as 1.230 introduced the bug. > Thanks, Pascal :) cauldron has perl-Gtk2-1.241.0-1.mga2, that version seems to solve it, too (the version of gscan2pdf is 10 in cauldron, btw) assigning to perl-Gtk2 maintainer Keywords:
NEEDINFO =>
(none)
thierry rouillon
2012-03-12 15:27:28 CET
CC:
(none) =>
thierry.rouillon Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D alberto, is the bug fixed with mageia 2? Yes it is: in the three installations I made (all 64 bits) this bug is no more present. marking bug as fixed then. Status:
NEW =>
RESOLVED |