Created attachment 74072 [details] photo of Win7 laptop at Print dialog screen Installed 4.0.0.3 on a Win7 [64-bit] laptop. No printers are listed/shown available to be used. Installed 4.0.0.3 over .2. 4.0.0.2 prints just fine, but .3 does not. The display "screen" that shows the image of the page shows the page in a "zoomed" fashion. Nothing was changed/modified during the install process of .3 Print dialog just does not list any printers. Laptop - Dell Inspiron 1525 OS - Windows 7 64-bit
Jmadero pinged me on IRC to test this one as fast I can... Therefore: can't reproduce using Windows 7 x64, updated from LibreOffice 4.0 rc2 to LibreOffice rc3 ... This bug is indeed marked correctly as a blocker when you opened it, but because I can't confirm -> lowering priority. Following [1] I'll mark this as 'Major High' [1] https://wiki.documentfoundation.org/images/0/06/Prioritizing_Bugs_Flowchart.jpg
Tim - did you try resetting your profile like I suggested? Because Joren cannot confirm I suspect it's a messed up profile. Please report back as soon as you can
On 02/01/2013 05:15 PM, bugzilla-daemon@freedesktop.org wrote: > > *Comment # 2 <https://bugs.freedesktop.org/show_bug.cgi?id=60177#c2> > on bug 60177 <https://bugs.freedesktop.org/show_bug.cgi?id=60177> from > Joel Madero <mailto:jmadero.dev@gmail.com> * > Tim - did you try resetting your profile like I suggested? Because Joren cannot > confirm I suspect it's a messed up profile. Please report back as soon as you > can > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. > I reinstalled .2 and it worked. Same profile. Installing it on an XP laptop to see if it does the same thing.
Tim, Did a command line msiexec.exe default installation as administrator Windows 7 Ent sp1 64-bit OS No errors noted in a verbose install log. Version 4.0.0.3 (Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89) True that the start panel has no printer active or associated, but on launching any LO application, print option enables and full list of printers available to Windows applications is populated. Check if you have printing capability once inside a LO component. If not, can you completely uninstall and run the 4.0.0.3 installer from command line with verbose logging? Enter: msiexec.exe /i LibreOffice_4.0.0.3_Win_x86.msi /L*v lo4install.log Then post up the verbose installer log. Stuart
Tim, As Joel suggests, rename your profile folder... C:\Users\<username>\AppData\Roaming\LibreOffice to LibreOfficeOLD And then reinistall.
I tried to uninstall 4.0.0.3 using the Control Panel, but it told me I was not the administrator. I did a clean install going from Vists 32-bit to Win7 64-bit and there is only one user - me. So, I reinstalled .2 It would not open, so I tried again. This time the install for .2 gave me a "repair" option. Once done, I had .2 back and the printer worked fine. What you want me to do is install .3 in the command line? XP did not have any problems with .3 install from 3.6.4 though. ---- I had to go offline after my last email due to not having any lunch and really needing to eat soon of get sick. Then the pain in my back hit hard, again, and went to my bed and read for 4 hours. I just am taking a few minutes before beg to look at some emails that do not take much brain-power or vision to deal with. ---- Will take time tomorrow to do a new install of .3 via the command line, with your "script". I will let you know. On 02/01/2013 05:49 PM, bugzilla-daemon@freedesktop.org wrote: > V Stuart Foote <mailto:vstuart.foote@utsa.edu> changed bug 60177 > <https://bugs.freedesktop.org/show_bug.cgi?id=60177> > What Removed Added > CC vstuart.foote@utsa.edu > > *Comment # 4 <https://bugs.freedesktop.org/show_bug.cgi?id=60177#c4> > on bug 60177 <https://bugs.freedesktop.org/show_bug.cgi?id=60177> from > V Stuart Foote <mailto:vstuart.foote@utsa.edu> * > Tim, > > Did a command line msiexec.exe default installation as administrator Windows 7 > Ent sp1 64-bit OS > > No errors noted in a verbose install log. > > Version 4.0.0.3 (Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89) > > True that the start panel has no printer active or associated, but on launching > any LO application, print option enables and full list of printers available to > Windows applications is populated. > > Check if you have printing capability once inside a LO component. > > If not, can you completely uninstall and run the 4.0.0.3 installer from command > line with verbose logging? Enter: > > msiexec.exe /i LibreOffice_4.0.0.3_Win_x86.msi /L*v lo4install.log > > Then post up the verbose installer log. > > Stuart > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. >
(In reply to comment #6) > I tried to uninstall 4.0.0.3 using the Control Panel, but it told me I > was not the administrator. I did a clean install going from Vists > 32-bit to Win7 64-bit and there is only one user - me. > > So, I reinstalled .2 > It would not open, so I tried again. This time the install for .2 gave > me a "repair" option. Once done, I had .2 back and the printer worked fine. > > What you want me to do is install .3 in the command line? > > XP did not have any problems with .3 install from 3.6.4 though. > Correct, open a command window "Run as administrator" and then enter the msiexec.exe command as given in comment #4. Deletion, or renaming, of the old profile removes one variable from working through the problem. After uninstalling the 4.0.0.2 rc2 and the profile, you should be starting from a clean system. But sometimes running a conservative registry clean-up (e.g. CCleaner) will resolve any lingering issues, simpler to just clean it all off and reboot to start fresh. If the printer issue resolves by removing the old profile, you could dig deeper and restore items from the old 4.0.0.2 profile piece by piece. My opinion is that profile migration, especially for the upgrade process from 3.6.x -> 4.0.0 is experimental at best. If the profile turns out to have been the issue for you, obviously that becomes a different bug. Take your time with the uninstall--cleanup--reinstall of 4.0.0.3 rc3 build. And be certain to "Run as Administrator" so all Windows registry and LibreOffice registry elements on initial launch are correctly written.
NOT reproducible with "LibO 4.0.0.3 rc - GERMAN UI / German Locale [Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89)]" {tinderbox: @6, pull time 2013-01-31 11:30(?)} on German WIN7 Home Premium (64bit) with User Profile updated from 4.0.0.2 @all: Can you please stop that excessive citing? It's tedious to have to read all that useless repetitions. Only If you do not reply to the comment before it is useful to use the Bugzilla [reply] function. If you think it's necessary for understanding of your reply, you can cite 1 ... 2 relevant lines of the comment directly before you reply, but not a fullquote. What also means: please do not use the mail interface for your comments, please reply here on the web page. Thx!
On 02/01/2013 05:49 PM, bugzilla-daemon@freedesktop.org wrote: > V Stuart Foote <mailto:vstuart.foote@utsa.edu> changed bug 60177 > <https://bugs.freedesktop.org/show_bug.cgi?id=60177> > What Removed Added > CC vstuart.foote@utsa.edu > > *Comment # 4 <https://bugs.freedesktop.org/show_bug.cgi?id=60177#c4> > on bug 60177 <https://bugs.freedesktop.org/show_bug.cgi?id=60177> from > V Stuart Foote <mailto:vstuart.foote@utsa.edu> * > Tim, > > Did a command line msiexec.exe default installation as administrator Windows 7 > Ent sp1 64-bit OS > > No errors noted in a verbose install log. > > Version 4.0.0.3 (Build ID: 7545bee9c2a0782548772a21bc84a9dcc583b89) > > True that the start panel has no printer active or associated, but on launching > any LO application, print option enables and full list of printers available to > Windows applications is populated. > > Check if you have printing capability once inside a LO component. > > If not, can you completely uninstall and run the 4.0.0.3 installer from command > line with verbose logging? Enter: > > msiexec.exe /i LibreOffice_4.0.0.3_Win_x86.msi /L*v lo4install.log > > Then post up the verbose installer log. > > Stuart > ------------------------------------------------------------------------ > You are receiving this mail because: > > * You reported the bug. > This install worked. I started with 4.0.0.2 again and then used your command line script. Now shows the printers. In other message, the question of profile between 3.6.4 to 4.0.0.x did not convert over. It was clean with no user informationbrought over from 3.6.4 to 4.0.0.x.. Did the same thing when I went from 3.5.x to 3.6.x.. So I was working with a good profile for 4.0.0.2 when I went to 4.0.0.3. I do custom install to reduce the dictionaries to English only. I also check the "support assistive technology tools". So this time the install worked. I can only state it did not work before, but did not. Why, I do not know. If this happens to someone else, then we need to have this command line install posted somewhere. Do you still want me to post the log file?
Since the printing configuration issue can not be reproduced, have been resolved by OP, and are otherwise working correctly marking this as Resolved, Invalid. To recap, Windows printing configuration issues were observed during RC upgrade from 4.0.0.2 to 4.0.0.3. It was a custom install, and neither the Windows registry or the LibreOffice registry user profile had been cleaned. No capture of a Windows installer log of any of the faulting installations, only of the final successful installation. Resolved with successful installation run from command window "Run as administrator" with user profile renamed or deleted (allowing profile to be rebuilt). It would have been helpful to have a verbose windows installer log and perhaps zipped up user profile from the faulting installation--because there could be subtle windows installer issues with recent work on the parsing of existing user profiles for upgrade. Anyone experiencing similar behavior--please reopen this bug and document. @Tim: With the Bugzilla interface (where comments are fully serialized) the flow is sequential as a bug is worked. Usually no need to use the reply function for including quoted text. If need be fine, the reply mechanism allows that by fully quoting a specific comment and marking it as a reply, Bugzilla etiquette is to then minimize the quote to only what is immediately needed. Some folks will fuss if the discussion is not terse enough.