[Bug 158862] New: LibreOffice crashes when attempting to inspect a UNO object in the Watch Window during debugging after successful initial inspection.
https://bugs.documentfoundation.org/show_bug.cgi?id=158862
Bug ID: 158862
Summary: LibreOffice crashes when attempting to inspect a UNO
object in the Watch Window during debugging after
successful initial inspection.
Product: LibreOffice
Version: 7.6.4.1 release
Hardware: x86-64 (AMD64)
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: medium
Component: BASIC
Assignee: libreoffice-bugs@lists.freedesktop.org
Reporter: jem203...@gmail.com
Description:
After successfully running the provided Basic subroutine, the LibreOffice
application allows for the initial inspection of the UNO object (textDoc) in
the Watch Window. The variable `textDoc`, its value, and type
("com.sun.star.text.TextDocument") are visible. However, attempting to perform
a deeper inspection, either by double-clicking the variable or clicking the
drop-down option, results in a consistent crash of LibreOffice. The crash
occurs specifically during attempts to inspect the variable further. The issue
persists even after restarting LibreOffice, resetting the user profile, and
running in Safe Mode.
Steps to Reproduce:
1.Open LibreOffice and create a new Basic module.
2.Add the following Basic subroutine:
`Sub Example
Dim textDoc As Object : textDoc =
CreateUnoService("com.sun.star.text.TextDocument")
End Sub`
3.Compile and execute the subroutine successfully.
4. Set a breakpoint at the `End Sub` line.
5. Debug the subroutine and observe the `textDoc` object in the Watch Window.
6. Double-click the `textDoc` variable or click the drop-down option to inspect
the `textDoc` object further.
Actual Results:
LibreOffice allows for the initial inspection of the `textDoc` object in the
Watch Window, displaying the variable's value and type. However, attempting to
perform a deeper inspection by double-clicking the variable or clicking the
drop-down option results in a crash of LibreOffice.
Expected Results:
The Watch Window should allow both initial and deeper inspection of the
`textDoc` object without causing LibreOffice to crash.
Reproducible: Always
User Profile Reset: Yes
Additional Info:
Version: 7.6.4.1 (X86_64) / LibreOffice Community
Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1
CPU threads: 20; OS: Windows 10.0 Build 22621; UI render: Skia/Raster; VCL: win
Locale: en-GB (en_US); UI: en-GB
Calc: CL threaded
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 61189] PDF printing mode problem: HP LaserJet + media type + no tray + user prompt (refer comment #10)
https://bugs.documentfoundation.org/show_bug.cgi?id=61189 Aron Budea changed: What|Removed |Added Status|RESOLVED|CLOSED URL|https://bellenmerken.com/sn | |apchat-nederland/ | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 116643] Crash when playing PPTX slide with MP4 video (comment 7)
https://bugs.documentfoundation.org/show_bug.cgi?id=116643 --- Comment #17 from JeansLome --- Experiencing a persistent crash issue while playing PPTX slides with MP4 videos, making the presentation process frustrating. It's essential to address this technical glitch promptly for seamless presentations. Meanwhile, if you're looking for a break from troubleshooting, check out this informative link https://casino358.com/minimitalletus/5-euron/ for information on 5 euro deposit online casinos in Finland. It offers authentic insights for those interested in online gaming with a minimal deposit. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 61189] PDF printing mode problem: HP LaserJet + media type + no tray + user prompt (refer comment #10)
https://bugs.documentfoundation.org/show_bug.cgi?id=61189 paulscott changed: What|Removed |Added URL||https://bellenmerken.com/sn ||apchat-nederland/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158651] Comment marker in Calc is not visible right after creation (kf5 and gen)
https://bugs.documentfoundation.org/show_bug.cgi?id=158651 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 90520] Base crashes with Oracle ODBC driver when sorting/filtering
https://bugs.documentfoundation.org/show_bug.cgi?id=90520 --- Comment #21 from QA Administrators --- Dear grongo2, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158645] Problem Syncing with Microsoft OneDrive
https://bugs.documentfoundation.org/show_bug.cgi?id=158645 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158653] Comment commands in Calc's menus need to be rearranged
https://bugs.documentfoundation.org/show_bug.cgi?id=158653 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 90380] VIEWING: Navigator causes constant cpu usage when it does not have focus in documents with lots of text frames and images
https://bugs.documentfoundation.org/show_bug.cgi?id=90380 --- Comment #10 from QA Administrators --- Dear Gordo, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 155940] AutoFilter would not go away even after restart
https://bugs.documentfoundation.org/show_bug.cgi?id=155940 --- Comment #4 from QA Administrators --- Dear Vara La Fey, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158648] Can't use scrollbar in presenter console's Slides view in RTL UI
https://bugs.documentfoundation.org/show_bug.cgi?id=158648 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158642] "Text boundaries" set to "automatic" obscure the cursor when line is empty
https://bugs.documentfoundation.org/show_bug.cgi?id=158642 QA Administrators changed: What|Removed |Added Whiteboard|| QA:needsComment -- You are receiving this mail because: You are the assignee for the bug.
[Bug 128392] Libreoffice for Mac OS X does not respect Dvorak-QWERTY keyboard layout for command keys.
https://bugs.documentfoundation.org/show_bug.cgi?id=128392 --- Comment #13 from QA Administrators --- Dear bugzilla, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 101958] "Find" toolbar field won't accept pasted text from the clipboard other than unformatted text after keyboard switch
https://bugs.documentfoundation.org/show_bug.cgi?id=101958 --- Comment #13 from QA Administrators --- Dear CTAC, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 53965] Character ` is inserted while cycling through the windows on macOS on some keyboard layouts
https://bugs.documentfoundation.org/show_bug.cgi?id=53965 --- Comment #18 from QA Administrators --- Dear erwanmotte, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 106976] Can't paste english text as a filename when russian keyboard is on
https://bugs.documentfoundation.org/show_bug.cgi?id=106976 --- Comment #13 from QA Administrators --- Dear Valentin, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158861] New: 保存的ODF格式不能被word2007打开
https://bugs.documentfoundation.org/show_bug.cgi?id=158861 Bug ID: 158861 Summary: 保存的ODF格式不能被word2007打开 Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rongshuy...@qq.com Description: 保存的ODF格式文件不能被word2007打开，提示文件损坏，是否修复。点击修复后可以打开文本。 Actual Results: 弹窗提示：文件损坏，是否修复。 Expected Results: 点击修复后，可以打开文本。 Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: zh-CN Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105526] Allow interactions for different events such as mouse over
https://bugs.documentfoundation.org/show_bug.cgi?id=105526 --- Comment #10 from JeansLome --- Enabling interactions like mouse over adds dynamic engagement to websites, enhancing user experience. Such features contribute to a more immersive environment, especially in online gaming. For instance, in the context of online casinos, it could elevate the gaming experience. If you're interested in exploring 5 euro deposit online casinos in Finland, check out https://casino358.com/minimitalletus/5-euron/ for valuable information. It's a great way to discover affordable and accessible gaming opportunities. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158860] I checked "Do not add leading (extra space) between lines of text" But when I past something after a period (.) it still adds an extra space.
https://bugs.documentfoundation.org/show_bug.cgi?id=158860 m.a.riosv changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO Ever confirmed|0 |1 --- Comment #2 from m.a.riosv --- Can you link from where and what you copy? Please paste here the information on Menu/Help/About LibreOffice (There is an icon to copy) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158860] I checked "Do not add leading (extra space) between lines of text" But when I past something after a period (.) it still adds an extra space.
https://bugs.documentfoundation.org/show_bug.cgi?id=158860 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg --- Comment #1 from m.a.riosv --- I think it has something to do with Autocorret. Menu/Tools/Autocorrect/Autocorrect options/Options - Both options to delete spaces. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113050] FILEOPEN: PDF freezes Draw, one page, 19 KB file
https://bugs.documentfoundation.org/show_bug.cgi?id=113050 Dave Gilbert changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=44 ||731 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 44731] PDF import problems with gradients and patterns
https://bugs.documentfoundation.org/show_bug.cgi?id=44731 Dave Gilbert changed: What|Removed |Added CC||freedesk...@treblig.org See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=11 ||3050 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113050] FILEOPEN: PDF freezes Draw, one page, 19 KB file
https://bugs.documentfoundation.org/show_bug.cgi?id=113050 --- Comment #19 from Dave Gilbert --- OK, so now I understand the source of the problem. On Page 17 of the presentation is a cut-art graphic of a hand; this hand has a few half-toned patterns on it; these are represented in the pdf as images and masks (about 8 of them). They're then repeated using a tiled pattern fill; and poppler calls us back for every repetition creating thousands of copies. (That minimum test case has part of that pattern in it) #0 pdfi::PDFOutDev::drawImageMask (this=0x7fffdc20, pState=0x78c080, str=0x794910, width=8, height=8, invert=false) at /discs/fast/core/sdext/source/pdfimport/xpdfwrapper/pdfioutdev_gpl.cxx:1031 #1 0x00484b32 in Gfx::doImage (this=this@entry=0x760540, ref=ref@entry=0x7fffcef0, str=0x794910, inlineImg=inlineImg@entry=false) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Gfx.cc:4300 #2 0x00487dce in Gfx::opXObject (this=0x760540, args=, numArgs=) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Object.h:441 #3 0x0047eba3 in Gfx::go (this=this@entry=0x760540, topLevel=topLevel@entry=false) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Gfx.cc:685 #4 0x0047f320 in Gfx::display (this=this@entry=0x760540, obj=obj@entry=0x75c708, topLevel=topLevel@entry=false) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Gfx.cc:646 #5 0x0047f7f7 in Gfx::drawForm (this=0x760540, str=0x75c708, resDict=, matrix=, bbox=0x75c698, transpGroup=, softMask=false, blendingColorSpace=0x0, isolated=false, knockout=false, alpha=false, transferFunc=0x0, backdropColor=0x0) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Gfx.cc:4836 #6 0x00483338 in Gfx::doTilingPatternFill (this=0x760540, tPat=0x75c680, stroke=, eoFill=, text=) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Gfx.cc:2185 #7 0x00483c4d in Gfx::opEOFill (this=0x760540, args=, numArgs=) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Gfx.cc:1775 #8 0x0047eba3 in Gfx::go (this=this@entry=0x760540, topLevel=topLevel@entry=true) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Gfx.cc:685 #9 0x0047f320 in Gfx::display (this=this@entry=0x760540, obj=obj@entry=0x7fffd8c0, topLevel=topLevel@entry=true) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Gfx.cc:646 #10 0x004cc330 in Page::displaySlice (this=0x75d680, out=0x7fffdc20, hDPI=, vDPI=7200, rotate=0, useMediaBox=true, crop=true, sliceX=-1, sliceY=-1, sliceW=-1, sliceH=-1, printing=true, abortCheckCbk=0x0, abortCheckCbkData=0x0, annotDisplayDecideCbk=0x0, annotDisplayDecideCbkData=0x0, copyXRef=false) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Page.cc:584 #11 0x004cc5d8 in Page::display (this=, out=out@entry=0x7fffdda0, hDPI=hDPI@entry=2.4858339854353144e-317, vDPI=vDPI@entry=-nan(0xf), rotate=rotate@entry=-1, useMediaBox=useMediaBox@entry=255, crop=crop@entry=255, printing=printing@entry=true, abortCheckCbk=0x0, abortCheckCbkData=0x0, annotDisplayDecideCbk=0x0, annotDisplayDecideCbkData=0x0, copyXRef=false) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/Page.cc:530 #12 0x004d4e42 in PDFDoc::displayPage (this=this@entry=0x7fffdaa0, out=0x7fffdda0, out@entry=0x7fffdc20, page=page@entry=1, hDPI=2.4858339854353144e-317, hDPI@entry=7200, vDPI=-nan(0xf), vDPI@entry=7200, rotate=-1, rotate@entry=0, useMediaBox=255, useMediaBox@entry=true, crop=255, crop@entry=true, printing=, abortCheckCbk=, abortCheckCbkData=, annotDisplayDecideCbk=, annotDisplayDecideCbkData=, copyXRef=false) at /discs/fast/core/workdir/UnpackedTarball/poppler/poppler/PDFDoc.cc:608 #13 0x004170ac in main (argc=, argv=) at /discs/fast/core/sdext/source/pdfimport/xpdfwrapper/wrapper_gpl.cxx:177 it looks like poppler has a hook to tell the output device about the whole pattern in one go (useTilingPatternFill and tilingPatternFill), so implementing that would do it. A hack would be to add an optimisatino into DrawXmlOptimizer I think - tree/drawtreevisiting.cxx I'll have a look. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158423] CppunitTest_unoxml_domtest failing with libxml-2.12
https://bugs.documentfoundation.org/show_bug.cgi?id=158423 --- Comment #7 from Rene Engelhard --- which means, because my tests ARE with 2.12.3, is that adding a simple header won't have an effect to *running the test* anyways. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158423] CppunitTest_unoxml_domtest failing with libxml-2.12
https://bugs.documentfoundation.org/show_bug.cgi?id=158423 --- Comment #6 from Rene Engelhard --- Ah, nevermind, that is because our libxml2 is 2.12.3.. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158423] CppunitTest_unoxml_domtest failing with libxml-2.12
https://bugs.documentfoundation.org/show_bug.cgi?id=158423
--- Comment #5 from Rene Engelhard ---
(In reply to Buovjaga from comment #2)
> (In reply to Gwyn Ciesla from comment #0)
> > Complete log:
> > https://kojipkgs.fedoraproject.org//work/tasks/2557/109622557/build.log
>
> The link is 404.
>
> I noticed there is a patch:
> https://gerrit.libreoffice.org/c/libvisio/+/160542
> tests: Fix build with libxml 2.12
> libxml 2.12.0 reorganized the headers, which removed `xmlParseMemory`
> function from the scope.
>
> Gwyn: can you try, if the fix for unoxml/qa/unit/domtest.cxx would be
> likewise simple?
btw, except this warning
importtest.cpp: In function 'librevenge::RVNGString
{anonymous}::getXPathContent(xmlDocPtr, const librevenge::RVNGString&)':
importtest.cpp:149:3: warning: case value '5' not in enumerated type
'xmlXPathObjectType' [-Wswitch]
149 | case XPATH_POINT:
| ^~~~
importtest.cpp:150:3: warning: case value '6' not in enumerated type
'xmlXPathObjectType' [-Wswitch]
150 | case XPATH_RANGE:
| ^~~~
importtest.cpp:151:3: warning: case value '7' not in enumerated type
'xmlXPathObjectType' [-Wswitch]
151 | case XPATH_LOCATIONSET:
| ^~~~
libvisio actually builds and the tests *do* run with libxml2 2.12. Just tried
here. Th e commit you mentioned btw doesn't actually change the warning.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 113050] FILEOPEN: PDF freezes Draw, one page, 19 KB file
https://bugs.documentfoundation.org/show_bug.cgi?id=113050 --- Comment #18 from Dave Gilbert --- OK, so these are 'DRAWMASK' entries; following the cookie crumbs we go out through xpdfimport and back through wrapper_gpl.cxx to a call to poppler that does the parsing. We can get our stream back by doing: ./instdir/program/xpdfimport page17.pdf xdpfwrapper-op 2>&1 which gives us a 67M file with 170 draw images and 157404 drawMask's! /me grabs a bigger shovel, and keeps digging. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158423] CppunitTest_unoxml_domtest failing with libxml-2.12
https://bugs.documentfoundation.org/show_bug.cgi?id=158423 Rene Engelhard changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |NEW See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8302 --- Comment #4 from Rene Engelhard --- how should a simple include help with *running the test*? I mean, the *build* already was fixed with https://cgit.freedesktop.org/libreoffice/core/commit/?id=c8f7408db73d2f2ccacb25a2b4fef8dfebdfc6cb out of https://bugs.documentfoundation.org/show_bug.cgi?id=158302 But one can try, I don't have much hope there, though. Confirming btw. (Also in 24.2) -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158860] New: I checked "Do not add leading (extra space) between lines of text" But when I past something after a period (.) it still adds an extra space.
https://bugs.documentfoundation.org/show_bug.cgi?id=158860 Bug ID: 158860 Summary: I checked "Do not add leading (extra space) between lines of text" But when I past something after a period (.) it still adds an extra space. Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ericamundso...@gmail.com Description: I went into Tools > Options > LibreOffice writer > Compatibility > and checked or unchecked everything to get rid of leading or trailing spaces including "Do not add leading (extra space) between lines of text". I also went into view > style > modify style (right clicked current style) > and checked "do not add space between paragraphs of same style" But when I past things after a period it still adds spaces between the period and what I pasted. Steps to Reproduce: 1.copy something 2.paste it after period 3.LibreOffice will automatically add a space, even after turning this option off. Actual Results: 1.copy something 2.paste it after period 3.LibreOffice will automatically add a space, even after turning this option off. Expected Results: 1.copy something 2.paste it after period 3.LibreOffice will automatically add a space, even after turning this option off. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: no -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158853] the MSI and deb archives could provide the main license in a single format
https://bugs.documentfoundation.org/show_bug.cgi?id=158853 Jérôme changed: What|Removed |Added Blocks||113358 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=113358 [Bug 113358] [META] Linux packaging/installation/removal bugs and enhancements -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113358] [META] Linux packaging/installation/removal bugs and enhancements
https://bugs.documentfoundation.org/show_bug.cgi?id=113358 Jérôme changed: What|Removed |Added Depends on||158853 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158853 [Bug 158853] the MSI and deb archives could provide the main license in a single format -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158853] the MSI and deb archives could provide the main license in a single format
https://bugs.documentfoundation.org/show_bug.cgi?id=158853 Jérôme changed: What|Removed |Added Summary|the MSI archive could |the MSI and deb archives |provide the main license in |could provide the main |a single format |license in a single format -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158853] the MSI archive could provide the main license in a single format
https://bugs.documentfoundation.org/show_bug.cgi?id=158853 Jérôme changed: What|Removed |Added OS|Windows (All) |All --- Comment #1 from Jérôme --- In libreofficedev24.8_24.8.0.0.alpha0-1_amd64.deb archive, the license is provided in 2 formats (txt and html) : opt/libreofficedev24.8/LICENSE opt/libreofficedev24.8/LICENSE.html -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158857] Keep Power Query when saving XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=158857 m.a.riosv changed: What|Removed |Added CC||miguelangelrv@libreoffice.o ||rg Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #1 from m.a.riosv --- As Calc does not have it implemented, it is probably not even imported. But you are right that it would be nice if it was preserved when opening/saving. It seems to me more like a request for enhancement than a bug. +1 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113050] FILEOPEN: PDF freezes Draw, one page, 19 KB file
https://bugs.documentfoundation.org/show_bug.cgi?id=113050 --- Comment #17 from Dave Gilbert --- It does indeed finish loading, after somewhere more than 30mins, and with LO taking about 2.5G of RAM; the elements are mostly N4pdfi12FrameElementE's all 48x48 pixels; so something has rasterised an image as frames, sometimes using 3 elements per pixel. DrawXmlEmitter::visit loop; count=173N4pdfi12FrameElementEw,h@x,y:48,-48@65147.1,21888 DrawXmlEmitter::visit loop; count=174N4pdfi12FrameElementEw,h@x,y:48,-48@65147.1,21888 DrawXmlEmitter::visit loop; count=175N4pdfi12FrameElementEw,h@x,y:48,-48@65147.1,21888 ... DrawXmlEmitter::visit loop; count=853N4pdfi12FrameElementEw,h@x,y:48,-48@75611.1,21888 DrawXmlEmitter::visit loop; count=854N4pdfi12FrameElementEw,h@x,y:48,-48@75611.1,21888 DrawXmlEmitter::visit loop; count=855N4pdfi12FrameElementEw,h@x,y:48,-48@65147.1,22032 DrawXmlEmitter::visit loop; count=856N4pdfi12FrameElementEw,h@x,y:48,-48@65147.1,22032 DrawXmlEmitter::visit loop; count=857N4pdfi12FrameElementEw,h@x,y:48,-48@65147.1,22032 DrawXmlEmitter::visit loop; count=858N4pdfi12FrameElementEw,h@x,y:48,-48@65195.1,21984 Keeping digging. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158859] New: Allow names for irregular ranges
https://bugs.documentfoundation.org/show_bug.cgi?id=158859 Bug ID: 158859 Summary: Allow names for irregular ranges Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: enhancement Priority: medium Component: LibreOffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: sanipache...@outlook.com.ar Description: Currently, if we select irregular ranges and try to assign them a name in LibreOffice Calc, it throws an error because it's not supported. However, in spreadsheets in general, this action is supported, and by not allowing it in Calc, it reduces interoperability between different programs. Steps to Reproduce: 1. Open Calc. 2. Select an irregular range. 3. Type a name in the name box. 4. Press ENTER. Actual Results: You will receive an error indicating that the action is not allowed. Expected Results: * The range receives a name. * When opening spreadsheets in other formats, they should be recognized and managed (selected, edited, deleted, etc.) in LibreOffice Calc. Reproducible: Always User Profile Reset: Yes Additional Info: In Excel, you can name discontinuous ranges by separating the different ranges with the argument separator character (in Argentina, the semicolon [;]; in some areas of Mexico and the United States, the comma [,]). For example: A1:B5;C8:D10;F1 In the case of Google Sheets, it doesn't support naming irregular ranges but does allow working with Excel files containing irregular ranges. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158858] Distorted image and incorrect size during hover over in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158858 PJF changed: What|Removed |Added CC||pjdape...@hotmail.com --- Comment #1 from PJF --- Created attachment 191592 --> https://bugs.documentfoundation.org/attachment.cgi?id=191592=edit Screen shot of the reported Calc bug. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158858] New: Distorted image and incorrect size during hover over in Calc
https://bugs.documentfoundation.org/show_bug.cgi?id=158858 Bug ID: 158858 Summary: Distorted image and incorrect size during hover over in Calc Product: LibreOffice Version: 7.6.4.1 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: pjdape...@hotmail.com Description: I inserted an image into a comment in Calc. I saved the size and position of the image in the comment. When I hover over the cell the comment, the photo in the comment is distorted and the image size is compressed . Actual Results: Add a comment to a cell. Insert an image into the comment. Save the size and position of the comment. Save the file. Open the file and hover over the cell with the comment. Expected Results: The image size was incorrect and the image was distorted. Reproducible: Always User Profile Reset: No Additional Info: Reproduced the comment at the size and positioned originally saved. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158857] New: Keep Power Query when saving XLSX
https://bugs.documentfoundation.org/show_bug.cgi?id=158857 Bug ID: 158857 Summary: Keep Power Query when saving XLSX Product: LibreOffice Version: 24.8.0.0 alpha0+ Master Hardware: All OS: All Status: UNCONFIRMED Keywords: filter:xlsx Severity: normal Priority: medium Component: Calc Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ti...@libreoffice.org CC: aron.bu...@gmail.com Created attachment 191591 --> https://bugs.documentfoundation.org/attachment.cgi?id=191591=edit Power query XLSX MSO supports Power Query [1]. Example of XLSX with Power Query set is attached, taken from [2]. When such XLSX is resaved in LO, MSO does not recognize query. So it is data loss. If data od query is not changed, LO should keep it so that MSO opens it. https://support.microsoft.com/en-us/office/about-power-query-in-excel-7104fbee-9e62-4cb9-a02e-5bfb1a6c536a https://www.ablebits.com/office-addins-blog/how-to-use-power-query-excel/ -- You are receiving this mail because: You are the assignee for the bug.
[Bug 113050] FILEOPEN: PDF freezes Draw, one page, 19 KB file
https://bugs.documentfoundation.org/show_bug.cgi?id=113050 Dave Gilbert changed: What|Removed |Added CC||freedesk...@treblig.org --- Comment #16 from Dave Gilbert --- pdfseparate -f 17 -l 17 aufschiebenfribourgpraesentation.pdf page17.pdf gets a single page pdf that also fails. I'm not sure this is actually a hang, as opposed to a crazy slowness. Annotating the DrawXmlEmitter::visit( PageElement& elem, I see that for my single page test it's called once and never gets out of it's loop, so I added: std::cerr << "DrawXmlEmitter::visit loop; size: " << elem.Children.size() << " count=" << count << std::endl; with count incrementing on the loop. There are 157589 elements for some reason in that simple page, and after 12 minutes it's got through about 8 of them, but it's slowing down quite a bit as it's adding them. I'll keep digging. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 105537] [META] Assertion failed crashes
https://bugs.documentfoundation.org/show_bug.cgi?id=105537 Bug 105537 depends on bug 143240, which changed state. Bug 143240 Summary: Crash with debug build when save special document in ODF1.3 strict https://bugs.documentfoundation.org/show_bug.cgi?id=143240 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |WORKSFORME -- You are receiving this mail because: You are the assignee for the bug.
[Bug 143240] Crash with debug build when save special document in ODF1.3 strict
https://bugs.documentfoundation.org/show_bug.cgi?id=143240 Regina Henschel changed: What|Removed |Added Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #4 from Regina Henschel --- It no longer crashes. Tested with a build of master (LO 24.8) from 2023-12-22. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158856] Spelling checker returns strange message
https://bugs.documentfoundation.org/show_bug.cgi?id=158856 --- Comment #1 from Elmar --- Created attachment 191590 --> https://bugs.documentfoundation.org/attachment.cgi?id=191590=edit error message on adding redlined word -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158554] Semaphore files are not deleted when in use path longer than 200 characters or shorter path with long file name
https://bugs.documentfoundation.org/show_bug.cgi?id=158554 --- Comment #12 from Mike Kaganski --- (In reply to edg from comment #4) > in this scenario (just one more character, 260, in the last level directory > name where the document is present) the lock/samaphore remain in place after > closing LO Writer: > > C: > \Users\Username\Documents\\lll\ll > lll\\ > \lll\ > lll.odt > > But here documents with the same name lenght, or more, can be created and > updated but always the lock files remains. I have tested this - the only different character was drive letter D:, so the path looked like D:\Users\Username\Documents\\lll\l\\\lll\lll.odt Opening the file with Version: 7.6.4.1 (X86_64) / LibreOffice Community Build ID: e19e193f88cd6c0525a17fb7a176ed8e6a3e2aa1 CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (en_US); UI: en-US Calc: CL threaded created the expected lockfile in the same directory (.~lock.lll.odt#); and that file was successfully removed, when I close Writer. I also tested with Version: 7.5.0.3 (X86_64) / LibreOffice Community Build ID: c21113d003cd3efa8c53188764377a8272d9d6de CPU threads: 24; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: en-US (en_US); UI: en-US Calc: threaded In that older version, it also worked fine. So you likely need to make sure you didn't miss some small detail - e.g., how the file was opened (I tried double-click in Explorer to start associated Writer; opening from inside LibreOffice using File->Open; and also from the LibreOffice's Recent File list). Possibly a screencast could also help. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158856] New: Spelling checker returns strange message
https://bugs.documentfoundation.org/show_bug.cgi?id=158856 Bug ID: 158856 Summary: Spelling checker returns strange message Product: LibreOffice Version: 24.2.0.0 beta1+ Hardware: All OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: rob...@iafrica.com Description: When I right click on a redlined word, select add to dictionary, egt error message Steps to Reproduce: 1.click on redined word 2.select add to dictionary 3. Actual Results: get error message "word cannot be added to dictionary for unknown reason" Expected Results: should add Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-GB Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes Version: 24.2.0.1.0+ (X86_64) / LibreOffice Community Build ID: a735f64391b5c194b38cacb577f14ef60556bcbc CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: gtk3 Locale: en-GB (en_GB.UTF-8); UI: en-GB Calc: threaded got same error when was using v24.8 question: what is the difference between 24.2 and 24.8 (is the latter simply the combined version of 24.2? -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158554] Semaphore files are not deleted when in use path longer than 200 characters or shorter path with long file name
https://bugs.documentfoundation.org/show_bug.cgi?id=158554 --- Comment #11 from Mike Kaganski --- (In reply to edg from comment #8) > > Recently there were Windows path fixes like ... bug 157820. ... > > It would be very nice if LO can support \\?\ unicode absolute path which > heve not the 256 characters limitation Please re-check the bug 157820 that Buovjaga mentioned. Let me try to repro the problem that you describe. -- You are receiving this mail because: You are the assignee for the bug.
[Bug 130447] [META] DOCX (OOXML) section-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=130447 Bug 130447 depends on bug 158855, which changed state. Bug 158855 Summary: An extra empty paragraph appears after a table before a section break in DOCX https://bugs.documentfoundation.org/show_bug.cgi?id=158855 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104444] [META] DOCX (OOXML) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=10 Bug 10 depends on bug 158855, which changed state. Bug 158855 Summary: An extra empty paragraph appears after a table before a section break in DOCX https://bugs.documentfoundation.org/show_bug.cgi?id=158855 What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug.
[Bug 75431] FILESAVE : DOCX : Page Orientation is not preserved when mixed orientation is present
https://bugs.documentfoundation.org/show_bug.cgi?id=75431 Aron Budea changed: What|Removed |Added See Also||https://bugs.documentfounda ||tion.org/show_bug.cgi?id=15 ||8855 -- You are receiving this mail because: You are the assignee for the bug.
[Bug 130447] [META] DOCX (OOXML) section-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=130447 Aron Budea changed: What|Removed |Added Depends on||158855 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158855 [Bug 158855] An extra empty paragraph appears after a table before a section break in DOCX -- You are receiving this mail because: You are the assignee for the bug.
[Bug 104444] [META] DOCX (OOXML) table-related issues
https://bugs.documentfoundation.org/show_bug.cgi?id=10 Aron Budea changed: What|Removed |Added Depends on||158855 Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=158855 [Bug 158855] An extra empty paragraph appears after a table before a section break in DOCX -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158855] An extra empty paragraph appears after a table before a section break in DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=158855 Mike Kaganski changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |ASSIGNED Assignee|libreoffice-b...@lists.free |mikekagan...@hotmail.com |desktop.org | -- You are receiving this mail because: You are the assignee for the bug.
[Bug 158855] New: An extra empty paragraph appears after a table before a section break in DOCX
https://bugs.documentfoundation.org/show_bug.cgi?id=158855 Bug ID: 158855 Summary: An extra empty paragraph appears after a table before a section break in DOCX Product: LibreOffice Version: unspecified Hardware: All OS: All Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mikekagan...@hotmail.com Created attachment 191589 --> https://bugs.documentfoundation.org/attachment.cgi?id=191589=edit A table and a section break The attached DOCX has a table covering the whole first page, and a Section Break (Next Page) immediately after the table. In total, there are two pages in the document. Importing into Writer, the document gets an additional paragraph immediately after the table; this paragraph flows to a next page, and then the page break appears, resulting in a total of three pages. -- You are receiving this mail because: You are the assignee for the bug.
