Re: New committer
Thanks a lot everybody! On Friday, 7 August 2015 6:41 PM, Albino B Neto b...@riseup.net wrote: 2015-08-06 16:50 GMT-03:00 jan i j...@apache.org: Welcome to Manik Malhotra who just accepting being openoffice committer. Congratulations! -- Albino B Neto twitter.com/b1n0anb Debian. Freedom to code. Code to freedom! faw - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: STATE OF AOO: Overall Bugzilla Activity through July 2015
Top posting. If the closure of all old bugs is decided, I would like the team to consider keeping the bugs that have gathered votes. The threshold remains to be agreed on. We cannot just dump enhancement requests or bugs that draw much attention from users. That would mean that AOO does not want to take the whole inheritance of OOo. Hagar Le 07/08/2015 09:13, Marcus a écrit : Am 08/06/2015 09:11 PM, schrieb Dennis E. Hamilton: Marcus, the queries I did for identification of open issues found only issues with no resolution of any kind. That automatically excluded issues with any of DUPLICATE, ..., WON'T FIX, and CLOSED status. OK Older open issues, some from long before Apache OpenOffice was established, continue to receive discussion and comments and, even in 2015, sometimes become resolved, including with fixes. I think it is good to hold onto the history simply to be able to reflect that. Nevertheless I would like to see them closed. It's possible to reopen an issue when one has the impression it's worth it. IMHO Sometimes is not enough to justify to leave billions (may feeling) of issue open. I agree that immediate concerns are best explored by looking more deeply into the 2015 issues and discussions to gain better perspective. I suspect the older open issues to look more closely at first are ones that are still being discussed, including being duplicated by new issue reports. OK, maybe older issues with newer comments should be left open. But duplicates are coming even when issues are already closed. People setting themselves at CC in the old, closed issue and then open a new issue. The summary at the end is not seldom I've the same problem. Let's cleanup our issue base. For this we don't need a (new) volunteer. We can discuss about the criteria and then just close them. Marcus -Original Message- From: Marcus [mailto:marcus.m...@wtnet.de] Sent: Thursday, August 6, 2015 05:18 To: dev@openoffice.apache.org Subject: Re: STATE OF AOO: Overall Bugzilla Activity through July 2015 Thanks for generating the numbers. Even when it is no surprise that we have many unsolved issues, it's always good to know the current values. In general I agree with Juergen and Roberto, we should focus on the newer times of AOO. Suggestion: To get rid of old issues we need to close all issues that are already in a state short before closure [*]: Duplicate, Irreproducible, Obsolete, Not_an_issue, Verified, Wont_fix As second step we can close all issues that are in status Resolved and last updated months/years ago. Then we have a much lower base of open issues and can filter better about age, importantance and severity. Finally it's then easier to decide what to do with the remaining open issues. [*] This makes it necessary to stop all BZ notification mails. Otherwise we get flooded by billions of mails and get hit by the Infra team all summer long. ;-) Marcus [ ... ] - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Buildbot: buildslave aoo_mac-mini was lost
The Buildbot working for 'ASF Buildbot' has noticed that the buildslave named aoo_mac-mini went away It last disconnected at Sat Aug 8 10:20:17 2015 (buildmaster-local time) The admin on record (as reported by BUILDSLAVE:info/admin) was 'Apache OpenOffice dev@openoffice.apache.org '. Sincerely, The Buildbot http://ci.apache.org/ http://ci.apache.org/buildslaves/aoo_mac-mini - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
build breaker/Issue 126449/ svx module
Hi There, I'm a developer using AOO in some of my applications. To debug some AOO problems I decided to build AOO with symbols to try and find a solution. I followed the instructions on how to build but got stuck when trying to build the svx module. used svn to get fresh start and tried building without debug, same problem. I opend an Issue on bugzilla but was kindly directed this way. see the issue for a complete log. configure was run like: configure --with-package-format=installed --disable-gnome-vfs trying to build fails with : [ build LNK ] Library/libsvxcore.so /home/martin/Downloads/aoo/main/solver/420/unxlngx6.pro/workdir/CxxObject/svx/source/fmcomp/fmgridif.o: In function `FmXGridControl::createPeer(com::sun::star::uno::Referencecom::sun::star::awt::XToolkit const, com::sun::star::uno::Referencecom::sun::star::awt::XWindowPeer const)': fmgridif.cxx:(.text+0x68b2): undefined reference to `non-virtual thunk to WindowListenerMultiplexer::acquire()' /usr/bin/ld: /home/martin/Downloads/aoo/main/solver/420/unxlngx6.pro/workdir/CxxObject/svx/source/fmcomp/fmgridif.o: relocation R_X86_64_PC32 against undefined symbol `_ZThn48_N25WindowListenerMultiplexer7acquireEv' can not be used when making a shared object; recompile with -fPIC Kind Regards, Martin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Buildbot: buildslave aoo_mac-mini was lost
The Buildbot working for 'ASF Buildbot' has noticed that the buildslave named aoo_mac-mini went away It last disconnected at Sat Aug 8 14:20:44 2015 (buildmaster-local time) The admin on record (as reported by BUILDSLAVE:info/admin) was 'Apache OpenOffice dev@openoffice.apache.org '. Sincerely, The Buildbot http://ci.apache.org/ http://ci.apache.org/buildslaves/aoo_mac-mini - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Buildbot: buildslave aoo_mac-mini was lost
The Buildbot working for 'ASF Buildbot' has noticed that the buildslave named aoo_mac-mini went away It last disconnected at Sat Aug 8 17:12:26 2015 (buildmaster-local time) The admin on record (as reported by BUILDSLAVE:info/admin) was 'Apache OpenOffice dev@openoffice.apache.org '. Sincerely, The Buildbot http://ci.apache.org/ http://ci.apache.org/buildslaves/aoo_mac-mini - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
REPORTING Windows 10 Upgrade Issues: BASIC SITUATION
We are reading reports of some users being able to edit in OpenOffice after upgrading to Windows 10. We have not been able to reproduce the situation from that information alone. Many of us have upgraded to Windows 10 without difficulty. If you or someone you know is having this problem show up in OpenOffice, please help us by working with the Windows 10 computer that is involved. Reply only to dev@openoffice.apache.org and not to individuals. If you reply to me, I will assume that I have permission to post your reply to this list and personally forward it to the list. BASIC SITUATION INFORMATION This is a little lengthy. It is to obtain just the basics. Depending on the basic information, there will be follow-ups to obtain further details. 1. SCOPE OF PROBLEM Have you noticed this problem on files other than those you use with OpenOffice? If you don't know or if you only use OpenOffice to work on documents, no problem. If you can easily determine that this problem goes beyond OpenOffice, it is important to know that. If you notice the problem with other files and applications let us know. That is very important. Because you are having the difficulty with OpenOffice either way, please go through the remainder of this procedure anyhow. 1. SYSTEM CONFIGURATION In Windows 10, right click on the Windows button (leftmost symbol on the task bar), and then select System. Please report the following information from the display that appears. Windows edition The name of the edition (complete first line below Windows edition): System Processor: Installed memory (RAM): System type: Pen and Touch: 2. OPEN OFFICE CONFIGURATION Now left click on the Windows button On the left sidebar of the Start display that shows all programs, scroll down to the letter O where you see a folder named OpenOffice. If you don't see a list of all programs, click the All apps item at the bottom of the sidebar to show the list. If you do not see a left sidebar at all, click the menu button (a stack of three horizontal lines) in the upper-left corner of the start page. What is the full name of that OpenOffice folder (including any version number)?: Click on the OpenOffice entry in the all-programs entry. In the list that opens up, click on the first entry, for OpenOffice itself. Do not click on any of the individual components. OpenOffice should open and present its dashboard view. This provides a white frame including buttons for the six types of documents processed by OpenOffice. At the top of the opened OpenOffice window, there is a menu row. Click on the Help item. In the little pop-down list that opens, click About OpenOffice What is the version information in the About ... OpenOffice display that opens up? Name and version of the software (e.g., Apache OpenOffice 4.1.1: Rev. number (in line below name and version number) if any (e.g., 1617669): Click OK on the About ...OpenOffice display. On the dashboard, there is a diagram of a file folder with an arrow emerging from it. Click on the down pointer to the right of that image. (Not the folder, the down pointer). Do you see a list of the last few documents you worked on? How many items are in the list (default maximum is 10): IF THERE ARE NONE, STOP HERE. Let us know the information requested above and there will be a follow-up question. IF THERE ARE ITEMS IN THE LIST, CONTINUE. The items in the list are numbered. This information will be important later. Write down the numbers and the full names of the files at each number. You may have to put your mouse over any name that has been abbreviated to see the full name. The full names are important for forensic work. PLEASE REVIEW ALL OF THE QUESTIONS BELOW SO YOU CAN WORK THROUGH THE LIST ONLY ONCE: How many will open by clicking on their filenames in that list (do this in reverse order)?: (This is about opening in any mode, editable or not. To go through them one at a time, you will have to close the opened one without attempting any changes, then re-open OpenOffice to try the next one.) This procedure cannot open a file that has been moved from where it was last used in OpenOffice. OpenOffice will report this. How many of those are there? How many of those open with no problem and no indication they cannot be edited?: How many of those that open are identified as being read-only or not editable?: How do you determine that they are not editable? That is, what is the indication in the opened-document window. Is it the same for all of the documents that open read-only? Include the list of documents that open but that are not editable. The follow-up will ask you to narrow in on those files to see what about them is a problem. THAT'S MANY QUESTIONS When we see your response, we will have other questions about the locations of those documents, or of other OpenOffice
Re: Build Problem (solved)
Hi Regina Thank you for the advice here. I followed what you said and moved the source into the root of C drive, placing it in a directory with no special characters. I did subsequently encounter an issue with building the modules associated with the SDK, but I re-ran configure with SDK disabled using the --disable-odk command. Accordingly, the build completed and I was able to install from the build. I will not move onto some of the tutorials kindly provided on the OO wiki and have a go at hacking some of the code on my own computer. Hopefully from there I can tackle some of the smaller issues identified on Bugzilla and so make a meaningful contribution. Best regards Jason Sent from Windows Mail From: Regina Henschel Sent: Tuesday, 21 July 2015 12:51 To: dev@openoffice.apache.org Hi Jason, Jason Marshall schrieb: Hi Regina Thank you for looking at this. I have ensured that with a new Cygwin session I have run the following successfully: /source winenv.set.sh/ Following that, I have run the following: /build --all:comphelper 21 | tee mybuild.log/ The build again did not progress past building the 'comphelper' module and appeared to have the same error as previously. However, I have attached the log file, 'mybuild.log' that was produced. When I ran the 'configure' command, I ran this with the following parameters: /./configure --with-frame-home=$SDK_PATH --with-psdk-home=$SDK_PATH --with-midl-path=$SDK_PATH/bin --with-ant-home=/cygdrive/c/ant --with-jdk-home=/cygdrive/c/Java/jdk1.8.0_45 --with-dmake-url=//https://github.com/mohawk2/dmake/archive/DMAKE_4_12.tar.gz//; --with-epm-url=//https://www.msweet.org/files/project2/epm-4.2-source.tar.gz//; --enable-pch --disable-atl --disable-activex --without-junit --disable-directx/ Please try with removed --enable-pch pch is precompiled header support --with-epm-url is not needed for Windows builds. You might want to add --without-fonts, download of gentium sometimes fails. I have also included as a file attachment the output of running 'configure' and can confirm that no errors were generated, although two warnings were as follows, which appear to not be related to the issue here: /checking which cppunit to use... configure: WARNING: not using cppunit/ /configure: WARNING: NSIS not found, no self contained installer will be build./ I also note from the 'configure' output that the source code is identified as being in the 'tmp' directory as follows: /The variable SRC_ROOT is set to: C:/cygwin/tmp/aoo-4.1.1/main/ Do you think that it may be better for me to delete the part of the build that has succeeded and then unpack the source into another directory that is not temp? If so, would this simply be to the root of the Cygwin file system? Yes, I think it is better to put the source not under tmp or any other directory, which is set somewhere as temp-directory. I have always use a directory directly under C: I have always use names without special characters. I have never tried to put the source somewhere inside cygwin, so I cannot say, whether that is possible. To test, whether the tmp directory is the problem, please move the folder aoo-4.1.1 under C: and rename it to e.g. aoo411 You need to remove all remainders of previous build tries then. In cygwin change to the main folder of your source, then use the following command (all in one line) find . -maxdepth 2 -name wntmsci12* | xargs rm -rf In addition you have to manually delete the wntmsci12* folders in main/solver in all subfolders of ext_libraries in all subfolders of extras Start with a new configure with parameters. Hopefully it works better then. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: REPORTING Windows 10 Upgrade Issues: BASIC SITUATION
Hello Dennis, I think in the first line of your text you mean, reports of some users NOT being able to edit in Openoffice after upgrading to Win 10. This is what I read from the mails in this list. I must say I haven't had any problems at all after I upgraded to Win 10; everything is in correct working order. As to the read-only files, maybe people who experience this should check in their file explorer if the files in the folder they are using for OpenOffice are set to read only. Seems like the likeliest thing to me. Max Am 08.08.2015 um 19:28 schrieb Dennis E. Hamilton: We are reading reports of some users being able to edit in OpenOffice after upgrading to Windows 10. We have not been able to reproduce the situation from that information alone. Many of us have upgraded to Windows 10 without difficulty. If you or someone you know is having this problem show up in OpenOffice, please help us by working with the Windows 10 computer that is involved. Reply only to dev@openoffice.apache.org and not to individuals. If you reply to me, I will assume that I have permission to post your reply to this list and personally forward it to the list. BASIC SITUATION INFORMATION This is a little lengthy. It is to obtain just the basics. Depending on the basic information, there will be follow-ups to obtain further details. 1. SCOPE OF PROBLEM Have you noticed this problem on files other than those you use with OpenOffice? If you don't know or if you only use OpenOffice to work on documents, no problem. If you can easily determine that this problem goes beyond OpenOffice, it is important to know that. If you notice the problem with other files and applications let us know. That is very important. Because you are having the difficulty with OpenOffice either way, please go through the remainder of this procedure anyhow. 1. SYSTEM CONFIGURATION In Windows 10, right click on the Windows button (leftmost symbol on the task bar), and then select System. Please report the following information from the display that appears. Windows edition The name of the edition (complete first line below Windows edition): System Processor: Installed memory (RAM): System type: Pen and Touch: 2. OPEN OFFICE CONFIGURATION Now left click on the Windows button On the left sidebar of the Start display that shows all programs, scroll down to the letter O where you see a folder named OpenOffice. If you don't see a list of all programs, click the All apps item at the bottom of the sidebar to show the list. If you do not see a left sidebar at all, click the menu button (a stack of three horizontal lines) in the upper-left corner of the start page. What is the full name of that OpenOffice folder (including any version number)?: Click on the OpenOffice entry in the all-programs entry. In the list that opens up, click on the first entry, for OpenOffice itself. Do not click on any of the individual components. OpenOffice should open and present its dashboard view. This provides a white frame including buttons for the six types of documents processed by OpenOffice. At the top of the opened OpenOffice window, there is a menu row. Click on the Help item. In the little pop-down list that opens, click About OpenOffice What is the version information in the About ... OpenOffice display that opens up? Name and version of the software (e.g., Apache OpenOffice 4.1.1: Rev. number (in line below name and version number) if any (e.g., 1617669): Click OK on the About ...OpenOffice display. On the dashboard, there is a diagram of a file folder with an arrow emerging from it. Click on the down pointer to the right of that image. (Not the folder, the down pointer). Do you see a list of the last few documents you worked on? How many items are in the list (default maximum is 10): IF THERE ARE NONE, STOP HERE. Let us know the information requested above and there will be a follow-up question. IF THERE ARE ITEMS IN THE LIST, CONTINUE. The items in the list are numbered. This information will be important later. Write down the numbers and the full names of the files at each number. You may have to put your mouse over any name that has been abbreviated to see the full name. The full names are important for forensic work. PLEASE REVIEW ALL OF THE QUESTIONS BELOW SO YOU CAN WORK THROUGH THE LIST ONLY ONCE: How many will open by clicking on their filenames in that list (do this in reverse order)?: (This is about opening in any mode, editable or not. To go through them one at a time, you will have to close the opened one without attempting any changes, then re-open OpenOffice to try the next one.) This procedure cannot open a file that has been moved from where it was last used in OpenOffice. OpenOffice will report this. How many of those are there? How many of those open with no problem and no
Re: Build Problem (solved)
Hi Jason, Jason Marshall schrieb: Hi Regina Thank you for the advice here. I followed what you said and moved the source into the root of C drive, placing it in a directory with no special characters. I did subsequently encounter an issue with building the modules associated with the SDK, but I re-ran configure with SDK disabled using the --disable-odk command. Accordingly, the build completed and I was able to install from the build. That is good news. Congratulation. I will not move onto some of the tutorials kindly provided on the OO wiki and have a go at hacking some of the code on my own computer. Hopefully from there I can tackle some of the smaller issues identified on Bugzilla and so make a meaningful contribution. When you have identified an area of interest, you should write a note. OpenOffice is huge. Perhaps you can get then some useful hints and tips from our experts. Kind regards Regina From: Regina Henschel Sent: Tuesday, 21 July 2015 12:51 To: dev@openoffice.apache.org Hi Jason, Jason Marshall schrieb: Hi Regina Thank you for looking at this. I have ensured that with a new Cygwin session I have run the following successfully: /source winenv.set.sh/ Following that, I have run the following: /build --all:comphelper 21 | tee mybuild.log/ The build again did not progress past building the 'comphelper' module and appeared to have the same error as previously. However, I have attached the log file, 'mybuild.log' that was produced. When I ran the 'configure' command, I ran this with the following parameters: /./configure --with-frame-home=$SDK_PATH --with-psdk-home=$SDK_PATH --with-midl-path=$SDK_PATH/bin --with-ant-home=/cygdrive/c/ant --with-jdk-home=/cygdrive/c/Java/jdk1.8.0_45 --with-dmake-url=//https://github.com/mohawk2/dmake/archive/DMAKE_4_12.tar.gz//; --with-epm-url=//https://www.msweet.org/files/project2/epm-4.2-source.tar.gz//; --enable-pch --disable-atl --disable-activex --without-junit --disable-directx/ Please try with removed --enable-pch pch is precompiled header support --with-epm-url is not needed for Windows builds. You might want to add --without-fonts, download of gentium sometimes fails. I have also included as a file attachment the output of running 'configure' and can confirm that no errors were generated, although two warnings were as follows, which appear to not be related to the issue here: /checking which cppunit to use... configure: WARNING: not using cppunit/ /configure: WARNING: NSIS not found, no self contained installer will be build./ I also note from the 'configure' output that the source code is identified as being in the 'tmp' directory as follows: /The variable SRC_ROOT is set to: C:/cygwin/tmp/aoo-4.1.1/main/ Do you think that it may be better for me to delete the part of the build that has succeeded and then unpack the source into another directory that is not temp? If so, would this simply be to the root of the Cygwin file system? Yes, I think it is better to put the source not under tmp or any other directory, which is set somewhere as temp-directory. I have always use a directory directly under C: I have always use names without special characters. I have never tried to put the source somewhere inside cygwin, so I cannot say, whether that is possible. To test, whether the tmp directory is the problem, please move the folder aoo-4.1.1 under C: and rename it to e.g. aoo411 You need to remove all remainders of previous build tries then. In cygwin change to the main folder of your source, then use the following command (all in one line) find . -maxdepth 2 -name wntmsci12* | xargs rm -rf In addition you have to manually delete the wntmsci12* folders in main/solver in all subfolders of ext_libraries in all subfolders of extras Start with a new configure with parameters. Hopefully it works better then. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
REPORTING Windows 10 Upgrade Issues: BASIC SITUATION - Correction
We are reading reports of some users *not* being able to edit in OpenOffice after upgrading to Windows 10. We have not been able to reproduce the situation from that information alone. Many of us have upgraded to Windows 10 without difficulty. If you or someone you know is having this problem show up in OpenOffice, please help us by working with the Windows 10 computer that is involved. Reply only to dev@openoffice.apache.org and not to individuals. If you reply to me, I will assume that I have permission to post your reply to this list and personally forward it to the list. BASIC SITUATION INFORMATION This is a little lengthy. It is to obtain just the basics. Depending on the basic information, there will be follow-ups to obtain further details. 1. SCOPE OF PROBLEM Do you see this problem using files in applications other than OpenOffice? If you notice the problem with other files and applications let us know. That is very important. Because you are having the difficulty with OpenOffice either way, please go through the remainder of this procedure anyhow. 1. SYSTEM CONFIGURATION In Windows 10, right click on the Windows button (leftmost symbol on the task bar), and then select System. Please report the following information from the display that appears. Windows edition The name of the edition (complete first line below Windows edition): System Processor: Installed memory (RAM): System type: Pen and Touch: 2. OPEN OFFICE CONFIGURATION Now left click on the Windows button On the left sidebar of the Start display that shows all programs, scroll down to the letter O where you see a folder named OpenOffice. If you don't see a list of all programs, click the All apps item at the bottom of the sidebar to show the list. If you do not see a left sidebar at all, click the menu button (a stack of three horizontal lines) in the upper-left corner of the start page. What is the full name of that OpenOffice folder (including any version number)?: Click on the OpenOffice entry in the all-programs entry. In the list that opens up, click on the first entry, for OpenOffice itself. Do not click on any of the individual components. OpenOffice should open and present its dashboard view. This provides a white frame including buttons for the six types of documents processed by OpenOffice. At the top of the opened OpenOffice window, there is a menu row. Click on the Help item. In the little pop-down list that opens, click About OpenOffice What is the version information in the About ... OpenOffice display that opens up? Name and version of the software (e.g., Apache OpenOffice 4.1.1: Rev. number (in line below name and version number) if any (e.g., 1617669): Click OK on the About ...OpenOffice display. On the dashboard, there is a diagram of a file folder with an arrow emerging from it. Click on the down pointer to the right of that image. (Not the folder, the down pointer). Do you see a list of the last few documents you worked on? How many items are in the list (default maximum is 10): IF THERE ARE NONE, STOP HERE. Let us know the information requested above and there will be a follow-up question. IF THERE ARE ITEMS IN THE LIST, CONTINUE. The items in the list are numbered. This information will be important later. Write down the numbers and the full names of the files at each number. You may have to put your mouse over any name that has been abbreviated to see the full name. The full names are important for forensic work. PLEASE REVIEW ALL OF THE QUESTIONS BELOW SO YOU CAN WORK THROUGH THE LIST ONLY ONCE: How many will open by clicking on their filenames in that list (do this in reverse order)?: (This is about opening in any mode, editable or not. To go through them one at a time, you will have to close the opened one without attempting any changes, then re-open OpenOffice to try the next one.) This procedure cannot open a file that has been moved from where it was last used in OpenOffice. OpenOffice will report this. How many of those are there? How many of those open with no problem and no indication they cannot be edited?: How many of those that open are identified as being read-only or not editable?: How do you determine that they are not editable? That is, what is the indication in the opened-document window. Is it the same for all of the documents that open read-only? Include the list of documents that open but that are not editable. The follow-up will ask you to narrow in on those files to see what about them is a problem. THAT'S MANY QUESTIONS When we see your response, we will have other questions about the locations of those documents, or of other OpenOffice documents that you tried to open that are not on that list of recent documents. Thank you for reporting your difficulty. Your answers will be instrumental in helping us to narrow down the case to
RE: REPORTING Windows 10 Upgrade Issues: BASIC SITUATION
Thanks max, you are correct about the missing not. Thanks. I'll correct that. We don't know if it is a global change of permissions, or some change related to account privileges, so far. The SCOPE OF PROBLEM section is intended to identify that case. Does that help? This is apparently a rare problem, not something done in all upgrades. We want to understand it. If it is not specific to OpenOffice, it is still important to support OpenOffice users in finding a resolution. - Dennis -Original Message- From: Max Merbald [mailto:max.merb...@gmx.de] Sent: Saturday, August 8, 2015 10:46 To: dev@openoffice.apache.org Subject: Re: REPORTING Windows 10 Upgrade Issues: BASIC SITUATION Hello Dennis, I think in the first line of your text you mean, reports of some users NOT being able to edit in Openoffice after upgrading to Win 10. This is what I read from the mails in this list. I must say I haven't had any problems at all after I upgraded to Win 10; everything is in correct working order. As to the read-only files, maybe people who experience this should check in their file explorer if the files in the folder they are using for OpenOffice are set to read only. Seems like the likeliest thing to me. Max Am 08.08.2015 um 19:28 schrieb Dennis E. Hamilton: We are reading reports of some users being able to edit in OpenOffice after upgrading to Windows 10. We have not been able to reproduce the situation from that information alone. Many of us have upgraded to Windows 10 without difficulty. If you or someone you know is having this problem show up in OpenOffice, please help us by working with the Windows 10 computer that is involved. Reply only to dev@openoffice.apache.org and not to individuals. If you reply to me, I will assume that I have permission to post your reply to this list and personally forward it to the list. BASIC SITUATION INFORMATION This is a little lengthy. It is to obtain just the basics. Depending on the basic information, there will be follow-ups to obtain further details. 1. SCOPE OF PROBLEM Have you noticed this problem on files other than those you use with OpenOffice? If you don't know or if you only use OpenOffice to work on documents, no problem. If you can easily determine that this problem goes beyond OpenOffice, it is important to know that. If you notice the problem with other files and applications let us know. That is very important. Because you are having the difficulty with OpenOffice either way, please go through the remainder of this procedure anyhow. 1. SYSTEM CONFIGURATION In Windows 10, right click on the Windows button (leftmost symbol on the task bar), and then select System. Please report the following information from the display that appears. Windows edition The name of the edition (complete first line below Windows edition): System Processor: Installed memory (RAM): System type: Pen and Touch: 2. OPEN OFFICE CONFIGURATION Now left click on the Windows button On the left sidebar of the Start display that shows all programs, scroll down to the letter O where you see a folder named OpenOffice. If you don't see a list of all programs, click the All apps item at the bottom of the sidebar to show the list. If you do not see a left sidebar at all, click the menu button (a stack of three horizontal lines) in the upper-left corner of the start page. What is the full name of that OpenOffice folder (including any version number)?: Click on the OpenOffice entry in the all-programs entry. In the list that opens up, click on the first entry, for OpenOffice itself. Do not click on any of the individual components. OpenOffice should open and present its dashboard view. This provides a white frame including buttons for the six types of documents processed by OpenOffice. At the top of the opened OpenOffice window, there is a menu row. Click on the Help item. In the little pop-down list that opens, click About OpenOffice What is the version information in the About ... OpenOffice display that opens up? Name and version of the software (e.g., Apache OpenOffice 4.1.1: Rev. number (in line below name and version number) if any (e.g., 1617669): Click OK on the About ...OpenOffice display. On the dashboard, there is a diagram of a file folder with an arrow emerging from it. Click on the down pointer to the right of that image. (Not the folder, the down pointer). Do you see a list of the last few documents you worked on? How many items are in the list (default maximum is 10): IF THERE ARE NONE, STOP HERE. Let us know the information requested above and there will be a follow-up question. IF THERE ARE ITEMS IN THE LIST, CONTINUE. The items in the list are numbered. This information will be important later. Write down the numbers and the
Re: [NOTICE] Windows build machine setted up
BTW: Do you still have the access problem with your people@a.o account? If so, we (maybe together with Infra) should solve this. Then you can save the binaries there to indicate that the work comes from an AOO committer and not from somewhere else. hrin Yes, I have still this problems. Solving this will be great. Thanks ! /hrin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [NOTICE] Windows build machine setted up
On 8 August 2015 at 20:21, Michal Hriň h...@apache.org wrote: BTW: Do you still have the access problem with your people@a.o account? If so, we (maybe together with Infra) should solve this. Then you can save the binaries there to indicate that the work comes from an AOO committer and not from somewhere else. hrin Yes, I have still this problems. Solving this will be great. Thanks ! you wrote you had uploaded the SSH keys to id.apache.org, that is a good first step. Next a couple of questions: - which terminal program do you use ? I use putty, and had to generate the keys with puttygen, you also have to remember to configure the terminal program to use SSH (not telnet) and give a path to your part of the key. - What exactly happens ? is your key rejected or do you get some kind of key error ? rgds jan i. /hrin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [RELEASE] Contents of OpenOffice 4.1.2
On 19/07/2015 Andrea Pescetti wrote: On 12/07/2015 Andrea Pescetti wrote: * Existing dictionaries: no problem, we will integrate them as usual. A deadline will be agreed upon and sent to the l10n list. * New dictionaries: no problem, we will integrate them as usual. A deadline will be agreed upon and sent to the l10n list. We keep dictionaries pending, waiting for the Extensions site to be fully available again The Extensions site has come back to normal operation for a few weeks, so I now propose, subject to lazy consensus, 16 August as a deadline for suggesting new/updated dictionaries. Later additions can be considered depending on other activities, but updates requested by 16 August are guaranteed to appear in 4.1.2. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Buildbot: buildslave aoo_mac-mini was lost
The Buildbot working for 'ASF Buildbot' has noticed that the buildslave named aoo_mac-mini went away It last disconnected at Sat Aug 8 23:45:40 2015 (buildmaster-local time) The admin on record (as reported by BUILDSLAVE:info/admin) was 'Apache OpenOffice dev@openoffice.apache.org '. Sincerely, The Buildbot http://ci.apache.org/ http://ci.apache.org/buildslaves/aoo_mac-mini - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
