Abiword 2.9.4 unstable was shipped in Mageia 3. Now the latest stable version of abiword 3.0 is released. Reproducible: Steps to Reproduce:
Component: Security => RPM PackagesQA Contact: security => (none)
MGA3 32-bit Updated my AbiWord to abiword-docs-en-3.0.0-1.mga3 abiword-3.0.0-1.mga3 and played with it on an active abw document. Found 3 problems, which I cannot say whether they were present before since I have no printer defined on this MGA3 system; need to try on others. 1] If you are in either 'normal' or 'web' view, then Print Preview (File menu) immediately crashes it. 2] If you are in either 'normal' or 'web' view, then Print (to file, PDF) crashes it at the print dialogue Print stage - the dialogue works OK to the point of asking whether you want to overwrite an existing file. 3] If you have the Ruler turned off, it is shown - despite the negative option - when you change to Normal view from either Page or Web views. The option remains unchecked. You can eliminate the ruler by turning it back on then off again. I tried under both KDE & Gnome Classic desktops; same results. I do not think this should go out with these faults. Shall I raise a bug for them? I do not think it matters whether they were in the previous version; they need fixing anyway.
CC: (none) => lewyssmith
Mga3 64 gnome I,m not a word person followed Lewis Smith installed abiword 3.0.0-1.mag3 and abiword-docs-en (1) Created a document File. Print preview works but if I try to print from print preview page a popup "Failed to print The selected printer '(null)' could not be found" If I File print "Network Printer" It prints fine. Same Document in Web view The print preview works It will also print from print preview. (2) Print to file as PDF all works ok confofmation to overwrite file works (3) I have not found any problems with ruler I can turn it on and off even remembers last setting if restarted The only problem I have found was printing from print preview page
CC: (none) => martynvidler
Have re-investigated problems noted in Comment 1 on other Linux's on the same box: LinuxMintDebian XFCE Abiword 2.9.2; OpenSuse 12.2 KDE Abiword 2.8.6. 1] & 2] crashes did *not* happen (although print preview under Suse was not too clever, a necessary dialogue box being hidden behind the main window, so you did not know it was there). 3] The ruler problem was always there. Clarified: if you turn off active rulers, they correctly disappear. If you then switch *to* Normal view mode, the top ruler only re-appears, the option remains unchecked. Turning rulers back on brings up both (side & top); off, they go. Trivial, no cause for action.
Mag3 64 I agree Comment 3 about rulers tried it as described by Lewis.
I have to revise my findings as stated in Comment1. Ignoring the trivial rulers thing, concentrating on crashing when printing/previewing, I now have the following: DESKTOP PRINT PREVIEW PRINT PRINT PREVIEW EX FILE MENU (TO PDF FILE) EX PRINT DIALOGUE Gnome Crash OK OK Gnome Crash OK OK Classic KDE4 Crash Crash OK LXDE Crash OK OK OpenBox Crash Crash Crash If someone can point me to investigating the 'crash' situations...
I realise that the tests in Comment5 did not take note of the document view mode (normal, web, page). It seems that AbiWord implicitly/sometimes changes that from 'normal' or 'web' to 'page' when invoking printing, so the table above should be 3 times bigger. Which is getting tedious... But clearly something is wrong.
*** Arch: i586 *** RPMs from 'core-updates_testing' ======================== abiword-3.0.0-1.mga3.i586.rpm abiword-devel-3.0.0-1.mga3.i586.rpm abiword-docs-en-3.0.0-1.mga3.noarch.rpm abiword-docs-fr-3.0.0-1.mga3.noarch.rpm abiword-docs-pl-3.0.0-1.mga3.noarch.rpm SRPMs from 'core-updates_testing' ======================== abiword-3.0.0-1.mga3.src.rpm abiword-docs-3.0.0-1.mga3.src.rpm *** Arch: x86_64 *** RPMs from 'core-updates_testing' ======================== abiword-3.0.0-1.mga3.x86_64.rpm abiword-devel-3.0.0-1.mga3.x86_64.rpm abiword-docs-en-3.0.0-1.mga3.noarch.rpm abiword-docs-fr-3.0.0-1.mga3.noarch.rpm abiword-docs-pl-3.0.0-1.mga3.noarch.rpm SRPMs from 'core-updates_testing' ======================== abiword-3.0.0-1.mga3.src.rpm abiword-docs-3.0.0-1.mga3.src.rpm
Funda, could you comment on Lewis's findings please.
Whiteboard: (none) => feedback
"Could you run abiword at the terminal and see what output it throws before it crashes? Matthew C." Tried quickly under KDE4, and all it outputs in terminal when it crashes is:- Aborted At the same time I noticed that when in normal|web view mode, doing Print[Preview] puts it in page mode in the menu, but not on screen - an inconsistency, like for the rulers. I need to play with this more precisely still, just for GnomeClassic (= Gnome3; I have no real Gnome3), KDE4, LXDE. I am using temporarily LightDM for login; will revert that to KDE just in case it has a bearing, which I doubt.
This goes from bad to worse: the number of variables increases. I am finding that behaviour is different from the File menu: Preview | Print; and Ctrl/P: Preview | Print; for different desktops; and possibly even the login manager because the KDE crashes noted in the table (using LightDM) did not all happen using KDE login manager. Not helped by the fact that if previewing/printing from normal | web view, I have discovered that AbiWord puts the document into page view, both the window and View menu (despite comment 9, not accurate); and it stays that way on returning to it. But the moment you click on the View menu, the window reverts to its previous view - but the View menu remains checked page view! Which confuses testing, since this is view-dependant. This is going to take ages to pin down. The inconveniences/inconsistencies can be overlooked, but not the crashes - *if* I can pin them down. Reminder: in certain circumstances, yet to be precisely identified, Preview and/or Print crash the program.
The more I try this, the fewer crashes happen; & more consistently. Having tried the following tests on a document always carefully in Normal view mode:- File -> Preview File -> Print -> Preview File -> Print -> Print (to file) Ctrl/P -> Preview Ctrl/P -> Preview -> Print (to file pre-selected) Ctrl/P -> Print (to file) via Display Managers: - KDE - LightDM using the following desktops: - GnomeClassic - KDE4 - LXDE I found that in *all* circumstances: - *all* the 3 File menu tests CRASHED. - *all* the Ctrl/P actions OK. No idea why things 'improved'. All crashes noted earlier were reproduceable at the time; system unchanged since. I did in fact get a crash via Ctrl/P with the view mode &/or ruler out of sync with the View menu, but could not reproduce it. The following caveats apply: - File -> Print -> Print (to file) went as far as asking to replace an existing destination PDF file before crashing on clicking 'Replace'. - Ctrl/P -> Preview -> Print (to file pre-selected) does not show -- the 'do you want to replace existing file?' dialogue -- the small page-by-page 'printing page x' progress window (unless hidden) of the more direct Ctrl/P -> Print path. Durable faults for me are thus: - Failure of all Preview/Print operations from File menu when in Normal or Web view; OK when in Page view. - The incorrectly displayed top ruler when changing to Normal view with rulers turned off; trivial. - The weird inconsistencies between the view menu and document window after preview/print operations from non-Page view, which -- Leave the window and view menu in Page view, ignoring its prior state. -- Revert the *window* to its previous mode (spurious ruler included) on simply clicking the View menu, leaving the *menu* on Page view unless specifically changed; trivial. I have to admit that if no-one else has the crashes, might as well let this go MGA3-i586-OK. For someone else.
Assigning Funda for now. Please reassign to QA when when you've had a chance to take a look. Thanks.
CC: (none) => qa-bugsAssignee: qa-bugs => fundawangWhiteboard: feedback => (none)
Mageia 3 changed to end-of-life (EOL) status 4 months ago. http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- The Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => OLD