In LibreOffice 5.2.3.2 printed on printer normal.
Empty file in writer and calc printed normal.
For the test, could you rename your LO directory profile (see https://wiki.documentfoundation.org/UserProfile) and give a new try? If you still reproduce this, would it be possible you attach a backtrace? (see https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#Windows:_How_to_get_a_backtrace)
rename my LO directory profile. For LibreOffice 5.2.3.3 normal, for 5.2.4.1 and 5.2.4.2 fnd 5.3.0.1 same problem. (windows 10 x64 libreoffice x64 5.3.0.1)
Does it crash for any file? (even with a brand new file with just "test" in it) or with a specific file only? Do you open the file from local hard disk, from network or from a mailer?
it crash for any file from local hard disk. New empty file printed normal. If input any letter in new empty file, then crash. In LibreOffice x86 same problem.
Thank you for all the extra information. I must recognize I don't know what could be the root cause. Anyway, since I don't have more questions, I'll put it back to UNCONFIRMED.
Please verify if some printer on the system is selected as default. If not, please select one and test if the issue remains. I have had some time ago problems with some program, althoug not with LibreOffice.
Hi the error appeared in LO 5. LO 4 works like charm but some HP LaserJet(?) (and not all of them) & LO 5 cause the problem. Now I use 5.3.0.1 (same with 5.2 and 5.1) and HP LaserJet 3500 (color) is ok, but HP LaserJet 1018 and 1606 is not. ok means I can print, not ok means LO 5 crashes when I try to print or select the printer in the dialog. If HP 1018 is the default, LO 5 craches if I click print. If PDF or XPS printer is the default, I can see the printer dialog box (till nmo crash) and the small preview on the left side. If I select HP LJ 3500 everything is ok, but If I select HP LJ 1018 or 1606 LO 5 craches. If the page is empty, I can print it. If anything is on the page (1 letter i.e. 'a') the error is back.
eventviewer: Application: soffice.bin, version: 5.3.0.1, timestamp: 0x585e4569 Modul: mergedlo.dll, version: 5.3.0.1, timestamp: 0x585e4524
5.2.3 portable version is perfect (mergedlo.dll is 66 MB) 5.3.0.1 installed version is buggy (mergedlo.dll is 55 MB) maybe the method how printed page is created for b&w printer is buggy?
<=5.1 is ok (mergedlo.dll is 67MB) >=5.2 is buggy (mergedlo.dll is 55MB)
*** Bug 104991 has been marked as a duplicate of this bug. ***
Since there's a dup, let's put this one to NEW
just tried to create a dump as described https://bugs.documentfoundation.org/show_bug.cgi?id=104991#c5 and https://bugs.documentfoundation.org/show_bug.cgi?id=104991#c6 but no error, I can print everything (5.4 alpha)
Hi, sorry for taking so long to report back. It seems 5.4 alpha is not compatible with Windows XP. I'll try installing it on a newer windows that has that specific printer. Maybe is just a Windows XP issue. If windows xp won't be supported anymore I might as well stick with 4.7.2 Thank you all.
(In reply to arielmazatlan from comment #16) > Hi, sorry for taking so long to report back. > > It seems 5.4 alpha is not compatible with Windows XP. I'll try installing it > on a newer windows that has that specific printer. Maybe is just a Windows > XP issue. > > If windows xp won't be supported anymore I might as well stick with 4.7.2 > > Thank you all. Badfully, XP is still supported according to https://www.libreoffice.org/get-help/system-requirements/#windows. So if you've got problem to install LO 5.4, don't hesitate to ask for some help in LO user forum (see http://nabble.documentfoundation.org/Users-f1639498.html) or on IRC (see https://wiki.documentfoundation.org/Website/IRC)
does anyone know any information what the diff is between 5.3 and 5.4? no mergedlo.dll at all and no problem while printing in 5.4 but in 5.3.0.1
(In reply to Kiss-Kálmán Dániel from comment #18) > does anyone know any information what the diff is between 5.3 and 5.4? no > mergedlo.dll at all and no problem while printing in 5.4 but in 5.3.0.1 They're 2 different branches. More precisely, 5.4 branch correspond to master branch (the bleeding edge for dev), 5.3 corresponds to the branch which provides soon the release 5.3.0 (see https://wiki.documentfoundation.org/ReleasePlan/5.3) So it seems we need bibisect here (see https://wiki.documentfoundation.org/QA/Bibisect)
(In reply to Julien Nabet from comment #19) > (In reply to Kiss-Kálmán Dániel from comment #18) > > does anyone know any information what the diff is between 5.3 and 5.4? no > > mergedlo.dll at all and no problem while printing in 5.4 but in 5.3.0.1 > > They're 2 different branches. > More precisely, 5.4 branch correspond to master branch (the bleeding edge > for dev), 5.3 corresponds to the branch which provides soon the release > 5.3.0 (see https://wiki.documentfoundation.org/ReleasePlan/5.3) > So it seems we need bibisect here (see > https://wiki.documentfoundation.org/QA/Bibisect) I mean in this context
No such problem detected on LO 5.2.4.1 , 5.3.0.0. LO master on Win 7 with HP LaserJet 1200 series
Hello Krom, Dániel, Ariel. Since Zineta didn't reproduce, I'm suggesting that you: - get http://tdf.io/siguiexe to easily get and run "parallel" LO in Windows (extract without installation) - run different extracted versions and architectures (32-bit or 64-bit) related to this bug in order to test crash and, if possible, since it's not overly complicated: - use procdump (part of free and useful Sysinternaly Suite) during LO run in order to get a dump - run procdump manually after LO start (path-to\SYSINTERNALSSUITE\procdump.exe soffice.bin -h path-to\soffice.bin.dmp) for reproducible bugs like this one, OR via simple batch file like attachment 129814 [details], that is used instead of LO icon to start LO, for intermittent bugs - analyze dump with WinDbg configured per https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg (set "Symbol File Path") - attach WinDbg result("backtrace") here as an attachment If you're able to consistently reproduce the bug with 5.2.4.2 and 5.3.0.1 but not with master 5.4 alpha that might indicate bug was resolved in the meantime. No need to analyze specific file (mergedlo.dll), rather LO versions (or builds).
win 7, 10 & LO 5.3 & HP LJ 1020, 1018, 1010, P1102 causes error win 7, 10 & LO 5.4 & any HP LJ no error, perfect so 5.4 seems unaffected Never created dump and backtrace but I'll try and send one if succeeded.
Dániel, care to try bibisecting the bug to help find the commit that caused this issue? (basic info on bibisecting: [1] and [2]) You need git (from Cygwin for example) and bibisect-win32-5.3 git repository from [3]. I know it sounds alien, but it can help pinpoint the exact commit responsible for the crash (a backtrace would still be helpful additionally). [1] https://wiki.documentfoundation.org/QA/Bibisect [2] https://wiki.documentfoundation.org/QA/Bibisect/Windows [3] https://wiki.documentfoundation.org/QA/Bibisect/Windows#bibisect-win32-5.3
(In reply to Aron Budea from comment #24) > Dániel, care to try bibisecting the bug to help find the commit that caused > this issue? (basic info on bibisecting: [1] and [2]) > > You need git (from Cygwin for example) and bibisect-win32-5.3 git repository > from [3]. I know it sounds alien, but it can help pinpoint the exact commit > responsible for the crash (a backtrace would still be helpful additionally). > > [1] https://wiki.documentfoundation.org/QA/Bibisect > [2] https://wiki.documentfoundation.org/QA/Bibisect/Windows > [3] > https://wiki.documentfoundation.org/QA/Bibisect/Windows#bibisect-win32-5.3 Hi Aron, pls help. So I have to download the bibisec source of LO. It is special kinda LO to find bugs (normal LO is not good for that). I need to build/compile an LO. I need to start that spec LO (swriter) & procdump to catch the crash. It creates a dump file (automatically when crash happens?), and I have to windbg somehow that dump file. Am I right? Waiting for your answer, an alien from planet Win10 ;)
hi all, just installed 5.3.0.2. Error disappeared, can print to all my HPLJs. thanks
Per Comment 15 and Comment 26 I close as WFM. If Krom or someone else reproduces this bug with 5.3.0.2 or higher, please feel free to set as NEW again. Bibisecting still would be fine. Or, we might conclude where this was fixed from https://wiki.documentfoundation.org/ReleasePlan/5.3#5.3.0_release looking at RC2 but somehow it's not populated as it should be. Until then, I kindly ask Dániel to test with 5.2.5 and, if not correct, with 5.2.6.
(In reply to Timur from comment #27) Hi all 5.2.5.1 is perfect (free from that kindda bug) huurraayy ;) Could find 5.2.6 so unable to try it. regards, Daniel
If 5.2.5 is OK, that's it. This one is likely a duplicate of Bug 105015. Starting from LO 5.2, there's crash report which is very useful. It wasn't mentioned here, though. It's sth. like crashreport.libreoffice.org/stats/crash_details/5dc29b47-91aa-401b-b95e-30aa4e024ee4 so please next time (which will hopefully never come) note that if experienced.