Launching any executable opens a terminal (command) window before starting the executable. The terminal window shows the following message
NOTE: you should run 'diskperf -y' to enable the disk statistics
Obviously the terminal window can not be closed, otherwise it will terminate the program window.
This occurs for the Master MSVC (2011-11-09) and for Master MinGW (2011-11-13)
NOTE: Kendy asked me to add the link to the MinGW bugs (41883) but this is a general bug on the Master build running in Windows
Created attachment 53530 [details]
Screenshot of error message on master install
Correction: the message in the terminal window only shows with the MinGW binaries. The terminal window launched by the MSVC binaries is empty.
During install of the MSVC version I got the error shown in the attached image (I have no idea if this is related)
I eee the same error with my LO3.5 build. I see in the WinXP task manager only one soffice.exe and one soffice.bin, as it should be. Closing either the terminal window or the Office will close the other part too.
LibO-dev 3.5.0 Build ID: 3f170f2-533e3c6-ca7e6f5-9125509-ce71330
on WinXP 32b
Starting 'scalc.exe' in 'program' folder shows "bar size width 759" in the command window (see attached screenshot 'fdo#42914').
See also 'Bug 42826 - Error message during installation'.
Created attachment 53537 [details]
As a comment to manj_k's screenshot: please notice that the application icon on the top left corner is not the Calc icon. Independently of the module opened it always shows that same odd icon in the MSVC binaries. On the MinGW binaries the Windows standard icon is displayed, as reported in Bug 41898
DUP of or related to "Bug 42826 - Error message during installation"?
I see various messages also with MSVC version.
Definitively not "Depends on: 41883", that one is only for MinGW specific bugs, so deleted.
Lasting bug should be marked as 'Blocks "Bug 37361 LibreOffice 3.5 most annoying bugs"'
Seems to cause no bigger problems, but not acceptable for release
Basically, one should add -mwindows to the linker flags for the exes. Will look at it if someone else does not look before.
Sigh, so this bug report now mentions at least five different problems. Why is it so hard to report just one thing in each bug report...?
Also, the corret term is "console window". Not "command window", not "terminal window". (And especially not "DOS box", although luckily nobody has even tried to use that term here...)
1) Starting the MSVC-built LO, an empty console window opens. Please, could we have a screenshot of that, or at least tell what the title of the console window says.
2) Starting a MinGW-built LO, a console window with the mysterious "NOTE: you should run 'diskperf -y' to enable the disk statistics" text appears. Again, screenshot pleast, or at least tell what the window title is.
3) Then in some cases during *installation*, the error message shown in the screenshot in comment #1 appears.
4) Then according to comment #3 a console window with the text "bar size width 759" appears when running Calc. (Without doing anything in it?)
5) Then some complaints about the "icon" displayed in the title bar in comment #5.
Now, I *think* we should in *this* bug concentrate on problem 1).
Created attachment 53831 [details]
Screenshot of command window
The text in the title bar of the command window is the string, which I put in the property of the link, from which I launch soffice.exe.
I have compiled it with MSCV 2008 Express on WinXP (32bit).
(In reply to comment #10)
> Sigh, so this bug report now mentions at least five different problems. Why is
> it so hard to report just one thing in each bug report...?
It's not. I was just being lazy :)
> Also, the corret term is "console window". Not "command window", not "terminal
> window". (And especially not "DOS box", although luckily nobody has even tried
> to use that term here...)
Thank you for the correction. It's not really relevant since it's easily understandable. Are there physical punishments for users who use the expression "DOS box"? :)
> 1) Starting the MSVC-built LO, an empty console window opens. Please, could we
> have a screenshot of that, or at least tell what the title of the console
> window says.
The title of the console is the same as the filename of the link file. If I start LibO-Dev the console title is LibO-Dev and remains so even if the program window name changes (e.g. when starting a new Text Document.
I fixed it with an ugly hack for MSVC builds.
(In reply to comment #13)
> I fixed it with an ugly hack for MSVC builds.
Just for the record, Bjoern fixed it a few hours later in the correct way for both MinGW and MSVC.
I can confirm that it is indeed fixed in MSVC build 130028f-b211287-090bcba-45cf606-05891e7 and in MinGW build 93e3a869-b211287-090bcba-45cf606
Yes, works fine with Server installation of Master "LibO-dev 3.5.0 – WIN7 Home Premium (64bit) GERMAN UI [Build ID: 130028f-b211287-090bcba-45cf606-05891e7]" Win-x86@9-Voreppe - 111130).
From what tinderbox did you get your build?
I'm currently observing strange differences between the builds from different tinderboxes, but it also might be that we have big changes from build to build.
The MSVC from Win-x86_9 and the MinGW from Win-x86_7
And as you notice, the MSVC build "numbers" aren't even comparable with the MinGW
That is why I submitted this request
I think it's fairly important that not only developers but also people in QA can understand if the build they downloaded is based on a newer or older source...
I know. I decided to do no further MinGW tests because it's too buggy. I would be interested to check whether there are differences (concerning general bugs) between Win-x86@6 and Win-x86@9
(In reply to comment #18)
> I know. I decided to do no further MinGW tests because it's too buggy. I would
> be interested to check whether there are differences (concerning general bugs)
> between Win-x86@6 and Win-x86@9
The only obstacle is that tinderbox #6 hasn't been able to finish successfully since the 28th so the builds aren't based on the same source code...
Fix is not in Server Installation of "LibreOffice 3.5.0 Beta0 - WIN7 Home Premium (64bit) German UI [Build:ef91e38-b1d4df6-090bcba-45cf606-05891e7]"
(In reply to comment #20)
> Fix is not in Server Installation of "LibreOffice 3.5.0 Beta0 - WIN7 Home
> Premium (64bit) German UI [Build:ef91e38-b1d4df6-090bcba-45cf606-05891e7]"
Yes, it is not there, because beta0 was tagged before the fix was committed. Yet, it is fixed. I saw it fixed in my own build.
In between I know, thanks for closing
*** Bug 43845 has been marked as a duplicate of this bug. ***