[Libreoffice-bugs] [Bug 85355] New: Pivot grouping options not available
https://bugs.freedesktop.org/show_bug.cgi?id=85355 Bug ID: 85355 Summary: Pivot grouping options not available Product: LibreOffice Version: 4.3.2.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Libreoffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: jananikumar...@gmail.com Hi, Is Pivot grouping options available in Libre office? if so how. Thank You, Regards, SriJanani -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85349] Broken display of slanted images
https://bugs.freedesktop.org/show_bug.cgi?id=85349 --- Comment #6 from Ralf Habacker ralf.habac...@freenet.de --- For the record: libreoffice 4.2.6.2 on opensuse 13.1 x86_64 does not show this bug. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85356] New: Hindi script improperly rendered in LibreOffice (in some cases)
https://bugs.freedesktop.org/show_bug.cgi?id=85356 Bug ID: 85356 Summary: Hindi script improperly rendered in LibreOffice (in some cases) Product: LibreOffice Version: 4.3.1.2 release Hardware: Other OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Localization Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: langbo...@gmail.com Created attachment 108280 -- https://bugs.freedesktop.org/attachment.cgi?id=108280action=edit This document contains Hindi script that reproduces the problem. LibreOffice Writer and Calc (probably others) are not properly rendering half letters in Hindi in one particular case. In most cases, the rendering is working properly. An attached file shows the problem. The problem combination is when you use the Windows 8 Hindi keyboard to type द्व. In this combination, the second letter should appear beneath the first letter. The current rendering is technically correct, but is not ideal. This seems to be a problem with the component that renders glyphs, because the same issue occurs in Calc, Impress, etc. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84854] Calc issues with screen drawing(all Windows and 32-bit Linux)
https://bugs.freedesktop.org/show_bug.cgi?id=84854 --- Comment #59 from Beluga todven...@suomi24.fi --- Created attachment 108283 -- https://bugs.freedesktop.org/attachment.cgi?id=108283action=edit Chart invisible in 4.4 alpha File source: https://bugs.freedesktop.org/show_bug.cgi?id=51671 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 46635] FILESAVE Endless loop during autorecovery if format not writable
https://bugs.freedesktop.org/show_bug.cgi?id=46635 --- Comment #60 from Ales a...@tosovsky.eu --- Affects me too: LibreOffice 4.2.6.3, Windows 8.1 Steps to reproduce: 1. open new document, start writing but don't save it manually 2. wait for automatic save time (e.g. 5 mins) Writer starts to autosave the document and tries it over and over again. Saving progress bar blinks repeatedly and all UI is pretty much frozen. When you want to save the document you have to try many times. Ones you save it, everything is all right. Maybe LibreOffice writes someplace where it doesn't have rights or something like that. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85215] Sorting a column of linked formula gives Error 523
https://bugs.freedesktop.org/show_bug.cgi?id=85215 --- Comment #3 from ribotb rib...@gmail.com --- With attachment file of JBF and steps to reproduce : - when UpdateReferenceOnSort is set to false, I get 'Err:523' in each cell in the range D2-E23; - when UpdateReferenceOnSort is set to true, 'Err:523' does not appear. Version: 4.4.0.0.alpha1+ Build ID: 9ecac3874d179b1d7aa6b45337001b1def06a9dd TinderBox: Win-x86@42, Branch:master, Time: 2014-10-22_06:31:01 Regards, Bernard -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85360] New: LibreOffice crashes and crashes desktop too on inserting 4th slide
https://bugs.freedesktop.org/show_bug.cgi?id=85360 Bug ID: 85360 Summary: LibreOffice crashes and crashes desktop too on inserting 4th slide Product: LibreOffice Version: 4.3.2.2 release Hardware: x86 (IA32) OS: Linux (All) Status: UNCONFIRMED Severity: blocker Priority: medium Component: Presentation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: st...@market-footprint.co.uk I am using OpenSuse 13.1 Yesterday I started having problems with libreoffice 4.3.1 where it would crash and also crash the desktop back to the login prompt when inserting the 4th slide in a presentation. Then libreoffice wouldnt start at all. Starting from the command prompt - it just sits there - no output and no error messages. Tried reinstalling LibreOffice 4.3.1 via Yast - wouldn't start. Ended up installing apache openoffice which also wouldnt start. Then uninstalled 4.3.1 and openoffice and installed libreoffice 4.3.2 via rpms as re-installation of 4.3.1 wouldnt run (at least using Yast) I now have 4.3.2 running now but the problem of it crashing and crashing the desktop on inserting the 4th slide is still there. I thought it might be a problem with my presentation but exactly the same happens on a blank presentation. 4th slide crashes it and the desktop so definitely severe and unusable. Spreadsheet seems fine - havent tried other apps -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85360] LibreOffice crashes and crashes desktop too on inserting 4th slide
https://bugs.freedesktop.org/show_bug.cgi?id=85360 Steve Roberts st...@market-footprint.co.uk changed: What|Removed |Added Priority|medium |high --- Comment #1 from Steve Roberts st...@market-footprint.co.uk --- Not directly related to this but changes to the system yesterday : - Tried installing import.io which needed oxygen-theme (this was a tar not an rpm). Installed gtk3-oxygen-theme via yast - didnt get import.io working so removed it using Yast -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85004] Writer: Crash when clicking the Reminder icon on the Navigation toolbar
https://bugs.freedesktop.org/show_bug.cgi?id=85004 --- Comment #5 from sophie gautier.sop...@gmail.com --- (In reply to Joel Madero from comment #4) Ubuntu 14.04 x64 Master built two days ago. No crash - assuming I'm not following instructions right. - add some Reminders in the document I've never added reminders, should I see some result when I do this? Is this the same as Set Reminder.? Yes, it's the same. There is no visible mark when you set them. The crash still happens for me, I think it's a problem between the Header and Reminder icons. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on OS X
https://bugs.freedesktop.org/show_bug.cgi?id=42082 Adolfo Jayme f...@libreoffice.org changed: What|Removed |Added Depends on||52004 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 60540] Some outline/formatting issues with the dmg installer for Mac OS X
https://bugs.freedesktop.org/show_bug.cgi?id=60540 Adolfo Jayme f...@libreoffice.org changed: What|Removed |Added See Also|https://bugs.freedesktop.or | |g/show_bug.cgi?id=52004 | -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 60540] Some outline/formatting issues with the dmg installer for Mac OS X
https://bugs.freedesktop.org/show_bug.cgi?id=60540 Adolfo Jayme f...@libreoffice.org changed: What|Removed |Added Blocks|42082 | -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 42082] [META] Make LibreOffice shine and glow on OS X
https://bugs.freedesktop.org/show_bug.cgi?id=42082 Adolfo Jayme f...@libreoffice.org changed: What|Removed |Added Depends on|60540 | -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84554] WIKIHELP: My problem is with submitting bugs. None of the above choices fits the problem
https://bugs.freedesktop.org/show_bug.cgi?id=84554 sophie gautier.sop...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG Severity|normal |enhancement --- Comment #4 from sophie gautier.sop...@gmail.com --- Hi John, sorry that you experienced those problems. We are using a bug tracking tool named BugZilla. This is not a tool managed by the foundation, so there are some settings we cannot manage. That will soon change with our own BugZilla instance. In the mean time, to help our users, we have designed an assistant which is a gateway to BugZilla. So the first screenshot in your document is the LibreOffice website, the second is the Bug submission assistant, the third is BugZilla. The latter is a difficult tool for user, more dedicated to developers. It handles bugs and requests for enhancement, the second drop down list in front of Importance allow you to choose Enhancement (I set it). BugZilla is a database with a web frontend, so to find your bugs, you have to make a query using the Search link. I hope this helps you to understand the process you followed. I agree with you that it's a complicated and absolutely not user friendly tool, we are well aware of that, and that's why we designed the Bug Submission Assistant. But this tool is very effective for QA members and developers. Let me know if I can help you further. I'm closing your request because this is not a bug in the product, and it should be handled on the website mailing-list. But it you need further information, just let me know - Sophie -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 71411] PRINTING: Problem Printing Envelopes
https://bugs.freedesktop.org/show_bug.cgi?id=71411 Beluga todven...@suomi24.fi changed: What|Removed |Added CC||todven...@suomi24.fi --- Comment #1 from Beluga todven...@suomi24.fi --- Created attachment 108290 -- https://bugs.freedesktop.org/attachment.cgi?id=108290action=edit Envelope printed to PDF file in 4.4 alpha I don't get cut off text. Have you tried with 4.3? Version used for test: 4.4.0.0.alpha1+ Build ID: a8c24b25fd9fb21097a08a22797bf61b59099ea1 TinderBox: Win-x86@39, Branch:master, Time: 2014-10-21_06:33:33 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85056] Writer crash after copy paste specific text
https://bugs.freedesktop.org/show_bug.cgi?id=85056 --- Comment #5 from grofaty grof...@hotmail.com --- Created attachment 108292 -- https://bugs.freedesktop.org/attachment.cgi?id=108292action=edit backtrace I have installed WinDbg tool following instructions: https://wiki.documentfoundation.org/How_to_get_a_backtrace_with_WinDbg I am attaching backtrace file. Hope this helps. I am not an expert, but there is interesting error: Fatal Python error: Py_Initialize: can't initialize sys standard stream It looks like Python (probably integrated LibreOffice Python) crashes at initialize process. Just for note, I my LibreOffice is installed in the following path: C:\Programs\LibreOffice4. Is Python expecting some other path like C:\Program files\LibreOffice4 or something? Do you need some additional info? -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85340] Better tooltip for spacing
https://bugs.freedesktop.org/show_bug.cgi?id=85340 --- Comment #2 from Heiko Tietze heiko.tie...@user-prompt.com --- Below the (paragraph) spacing is the line spacing, which is more important, IMHO, since most users separate paragraphs by line breaks. Tooltips of similar functions should always have similar text. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 78214] rename of '1.2 extended (compat mode)'
https://bugs.freedesktop.org/show_bug.cgi?id=78214 Adolfo Jayme f...@libreoffice.org changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED Whiteboard||target:4.4.0 --- Comment #5 from Adolfo Jayme f...@libreoffice.org --- http://cgit.freedesktop.org/libreoffice/core/commit/?id=691851b0f97bc0ff7206919ffd46ec90fe6a07ae -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 83991] remove bogus folding comments...
https://bugs.freedesktop.org/show_bug.cgi?id=83991 --- Comment #17 from Michael Meeks michael.me...@collabora.com --- Pushed; as a next step - it'd be great to start pushing to gerrit if you can get that setup - it's much easier to review / merge from there =) Thanks ! -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84121] PDF import: no images when password protected
https://bugs.freedesktop.org/show_bug.cgi?id=84121 Xisco Faulí aniste...@gmail.com changed: What|Removed |Added CC||aniste...@gmail.com Whiteboard|BSA bibisectRequest |BSA bibisected --- Comment #5 from Xisco Faulí aniste...@gmail.com --- bibisected: 55ecbc9a293276f2506a41e364da2331b22535ab is the first bad commit commit 55ecbc9a293276f2506a41e364da2331b22535ab Author: Bjoern Michaelsen bjoern.michael...@canonical.com Date: Thu Oct 17 16:50:06 2013 + source-hash-b1f7dd66b898b03cb4bd8d434b6370310ea95946 commit b1f7dd66b898b03cb4bd8d434b6370310ea95946 Author: Fridrich Štrba fridrich.st...@bluewin.ch AuthorDate: Mon Jul 8 19:07:55 2013 +0200 Commit: Fridrich Štrba fridrich.st...@bluewin.ch CommitDate: Mon Jul 8 19:08:37 2013 +0200 Use a real name of the library Change-Id: I5f9ec12b507e332d304b931ddb31103ee3f0766d :100644 100644 2453a385e152e0cdd1050935445b4d4eb51fd135 e10397005b24d777f96736399a8894d9d86d4b3f Mccache.log :100644 100644 9c6fb08ec2569d26e1f9c0d6f8d2f5dbda2494a9 214046467ff20f8f93675ec1617e5695a43b1ef7 Mcommitmsg :100644 100644 bb9b4796ae6e1dc88fa01e55e1d86da1519c30db 731af927fdf5e1ba24689e9fe4f8bd81a650c310 Mdev-install.log :100644 100644 1c711ff8ed8c46f5350d26cd6d7dcbb3699ded22 a182eaffd84ef341133216dea5d2f402b9a56789 Mmake.log :04 04 12e90c21e9922ff3e9f76387f19cc1a287a522db f8d793e97e2d282b48f2d72d2153da46411bea86 Mopt # bad: [423a84c4f7068853974887d98442bc2a2d0cc91b] source-hash-c15927f20d4727c3b8de68497b6949e72f9e6e9e # good: [65fd30f5cb4cdd37995a33420ed8273c0a29bf00] source-hash-d6cde02dbce8c28c6af836e2dc1120f8a6ef9932 git bisect start 'latest' 'oldest' # good: [e02439a3d6297a1f5334fa558ddec5ef4212c574] source-hash-6b8393474974d2af7a2cb3c47b3d5c081b550bdb git bisect good e02439a3d6297a1f5334fa558ddec5ef4212c574 # bad: [4850941efe43ae800be5c76e1102ab80ac2c085d] source-hash-980a6e552502f02f12c15bfb1c9f8e6269499f4b git bisect bad 4850941efe43ae800be5c76e1102ab80ac2c085d # skip: [a043626b542eb8314218d7439534dce2fc325304] source-hash-9379a922c07df3cdb7d567cc88dfaaa39ead3681 git bisect skip a043626b542eb8314218d7439534dce2fc325304 # skip: [aba65c3e4c0df07e4909aeefb758cdb688242bf6] source-hash-827524abfb4b577d08276fde40929a9adfb7ff1a git bisect skip aba65c3e4c0df07e4909aeefb758cdb688242bf6 # skip: [aba65c3e4c0df07e4909aeefb758cdb688242bf6] source-hash-827524abfb4b577d08276fde40929a9adfb7ff1a git bisect skip aba65c3e4c0df07e4909aeefb758cdb688242bf6 # bad: [c81a8a0dcfc1ed095a80e4485c89dd0fcaf73f31] source-hash-c69ed33628ec0b7abf6296539cf280d6c4265930 git bisect bad c81a8a0dcfc1ed095a80e4485c89dd0fcaf73f31 # bad: [c81a8a0dcfc1ed095a80e4485c89dd0fcaf73f31] source-hash-c69ed33628ec0b7abf6296539cf280d6c4265930 git bisect bad c81a8a0dcfc1ed095a80e4485c89dd0fcaf73f31 # bad: [1d4980621741d3050a5fe61b247c157d769988f2] source-hash-89d01a7d8028ddb765e02c116d202a2435894217 git bisect bad 1d4980621741d3050a5fe61b247c157d769988f2 # bad: [ba096f438393091574da98fe7b8e6b05182a8971] source-hash-8499e78ca03c792f4fa2650e02b519094ba0baa8 git bisect bad ba096f438393091574da98fe7b8e6b05182a8971 # good: [9daa289e178460daaafa4b3911031df5b8736218] source-hash-704292996a3731a61339b1a4a5c90c9403aa095f git bisect good 9daa289e178460daaafa4b3911031df5b8736218 # bad: [34eab3946c46bb7273ba4ca395db9c4421dd232f] source-hash-e962805b31074d6b6a2ed0db6452769448337553 git bisect bad 34eab3946c46bb7273ba4ca395db9c4421dd232f # good: [7f958321368b190c941b23cc219d62d0420415af] source-hash-b3f41543851e9985c6c7ba133c32753c9bc732c1 git bisect good 7f958321368b190c941b23cc219d62d0420415af # bad: [3bffe99b15f359bb4c6941210623dcd0763987c9] source-hash-6768d2c7f2cf75c507ec2108cbbb5a8a6cf7fae9 git bisect bad 3bffe99b15f359bb4c6941210623dcd0763987c9 # bad: [55ecbc9a293276f2506a41e364da2331b22535ab] source-hash-b1f7dd66b898b03cb4bd8d434b6370310ea95946 git bisect bad 55ecbc9a293276f2506a41e364da2331b22535ab # first bad commit: [55ecbc9a293276f2506a41e364da2331b22535ab] source-hash-b1f7dd66b898b03cb4bd8d434b6370310ea95946 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85059] Unable to open big MB files
https://bugs.freedesktop.org/show_bug.cgi?id=85059 --- Comment #17 from Michael Meeks michael.me...@collabora.com --- Well - it's an enhancement really; I hope there is another tracker enhancement for deferring the work here until embedded objects are activated; this whole idea of that setting is a global embarrassment ;-) we should do it right. It'd be nice to look for that enhancement to mark this one as being blocked by it - if you can (?) -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84802] Huge Files not responding
https://bugs.freedesktop.org/show_bug.cgi?id=84802 --- Comment #16 from Michael Meeks michael.me...@collabora.com --- Crashing is bad; though there may be an out-of-memory condition I guess. Ultimately, big charts are rendered with the drawing-layer which is pretty fundamentally large slow I'm afraid =) it's quite a chunk of engineering work to improve that. Possibly OpenGL rendering would improve the rendering performance at least. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85340] Better tooltip for spacing
https://bugs.freedesktop.org/show_bug.cgi?id=85340 Jay Philips philip...@hotmail.com changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever confirmed|0 |1 --- Comment #3 from Jay Philips philip...@hotmail.com --- We discussed this in the design meeting and everyone did agree that it is suitable. The 'Spacing:' label has both paragraph and line spacing controls, so is increase and decrease buttons referring to changing paragraph or line spacing. Its about clarity and thats what tooltips are for, they should be as clear as possible, as we didnt use 'Above Spacing' instead of 'Above Paragraph Spacing'. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85340] Better tooltip for paragraph spacing buttons
https://bugs.freedesktop.org/show_bug.cgi?id=85340 Jay Philips philip...@hotmail.com changed: What|Removed |Added Assignee|libreoffice-b...@lists.free |philip...@hotmail.com |desktop.org | Summary|Better tooltip for spacing |Better tooltip for ||paragraph spacing buttons --- Comment #4 from Jay Philips philip...@hotmail.com --- Commit sent - https://gerrit.libreoffice.org/12076 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85335] Glue points window/dialog contains two title bars
https://bugs.freedesktop.org/show_bug.cgi?id=85335 --- Comment #2 from Gabriel Diosan gabs...@gmail.com --- Created attachment 108294 -- https://bugs.freedesktop.org/attachment.cgi?id=108294action=edit Screenshot of Glue Points Window/Dialog on Ubuntu Gnome 14.10 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85335] Glue points window/dialog contains two title bars
https://bugs.freedesktop.org/show_bug.cgi?id=85335 --- Comment #3 from Gabriel Diosan gabs...@gmail.com --- I have tested this on Ubuntu Gnome 14.10 and the problem is not present. I have attached another screenshot as well. Libreoffice Build: Version: 4.4.0.0.alpha1+ Build ID: 72f368f6bfedb680ffcbd1c7fe28e8fc6d19ad2b TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-10-22_22:23:11 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85363] New: OPTIONS: Accessing Microsoft Office load and save setting crashes LibO
https://bugs.freedesktop.org/show_bug.cgi?id=85363 Bug ID: 85363 Summary: OPTIONS: Accessing Microsoft Office load and save setting crashes LibO Product: LibreOffice Version: 4.4.0.0.alpha0+ Master Hardware: Other OS: All Status: UNCONFIRMED Keywords: regression Severity: normal Priority: medium Component: Libreoffice Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: philip...@hotmail.com Created attachment 108295 -- https://bugs.freedesktop.org/attachment.cgi?id=108295action=edit linux backtrace Opening Tools Options Load/Save Microsoft Office crashes LibO. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85363] OPTIONS: Accessing Microsoft Office load and save setting crashes LibO
https://bugs.freedesktop.org/show_bug.cgi?id=85363 Jay Philips philip...@hotmail.com changed: What|Removed |Added See Also||https://bugs.freedesktop.or ||g/show_bug.cgi?id=85081 Severity|normal |major -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85081] Crash when starting to connect to database via Tools Options Base ..
https://bugs.freedesktop.org/show_bug.cgi?id=85081 Jay Philips philip...@hotmail.com changed: What|Removed |Added See Also||https://bugs.freedesktop.or ||g/show_bug.cgi?id=85363 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85059] Unable to open big MB files
https://bugs.freedesktop.org/show_bug.cgi?id=85059 Jay Philips philip...@hotmail.com changed: What|Removed |Added Depends on||85364 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85364] New: FILEOPEN: Embedded objects should be converted on loading
https://bugs.freedesktop.org/show_bug.cgi?id=85364 Bug ID: 85364 Summary: FILEOPEN: Embedded objects should be converted on loading Product: LibreOffice Version: 4.4.0.0.alpha0+ Master Hardware: Other OS: All Status: NEW Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: philip...@hotmail.com CC: michael.me...@collabora.com Blocks: 85059 As mentioned in bug 85059, with the Tools-Options-Load/Save-Microsoft Office settings checked by default, embedded objects are being converted when a file is loaded (e.g. attachment 107871), which either slows down the loading on Linux or halts LibO on Windows. So the solution as stated by Meeks is we should convert them as/when we need to on activation / macro use etc. but ... it is there. as it Seems to be spending a lot of time re-saving the embedded objects as ODF etc. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85059] Unable to open big MB files
https://bugs.freedesktop.org/show_bug.cgi?id=85059 --- Comment #18 from Jay Philips philip...@hotmail.com --- Filed it - bug 85364. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 63388] MAILMERGE: LibreOffice freezes when clicking Test Settings button
https://bugs.freedesktop.org/show_bug.cgi?id=63388 --- Comment #7 from mrmister001 mrmister...@gmail.com --- Hello, I confirm THIS IS A BUG AND NEED URGENT SOLUTION please LibreOffice Writer crash miserably when I try to send documents via email I have my settings perfectly configured, port, ssl, smtp server, etc. and this freeze completely. I did the changes that Andrea suggested but in my case are not working... -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 63388] MAILMERGE: LibreOffice freezes when clicking Test Settings button
https://bugs.freedesktop.org/show_bug.cgi?id=63388 mrmister001 mrmister...@gmail.com changed: What|Removed |Added Priority|medium |high OS|Linux (All) |Windows (All) -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85364] FILEOPEN: Embedded objects should be converted on activation not loading
https://bugs.freedesktop.org/show_bug.cgi?id=85364 Michael Meeks michael.me...@collabora.com changed: What|Removed |Added CC||libreoff...@kohei.us Summary|FILEOPEN: Embedded objects |FILEOPEN: Embedded objects |should be converted on |should be converted on |loading |activation not loading --- Comment #1 from Michael Meeks michael.me...@collabora.com --- Thanks for filing Jay =) I think there may be a number of duplicates / similar performance issues out there - it'd be good to stack them up here =) -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85363] OPTIONS: Accessing Microsoft Office load and save setting crashes LibO
https://bugs.freedesktop.org/show_bug.cgi?id=85363 Cor Nouws c...@nouenoff.nl changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED CC||c...@nouenoff.nl Resolution|--- |DUPLICATE --- Comment #1 from Cor Nouws c...@nouenoff.nl --- as discussed, I'll make 85081 generic *** This bug has been marked as a duplicate of bug 85081 *** -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85081] Crash when starting to connect to database via Tools Options Base ..
https://bugs.freedesktop.org/show_bug.cgi?id=85081 Cor Nouws c...@nouenoff.nl changed: What|Removed |Added CC||philip...@hotmail.com --- Comment #17 from Cor Nouws c...@nouenoff.nl --- *** Bug 85363 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84467] Searching for font size does not always work
https://bugs.freedesktop.org/show_bug.cgi?id=84467 sophie gautier.sop...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||gautier.sop...@gmail.com Ever confirmed|0 |1 --- Comment #3 from sophie gautier.sop...@gmail.com --- Hi, confirmed with Version: 4.4.0.0.alpha1+ Build ID: 72f368f6bfedb680ffcbd1c7fe28e8fc6d19ad2b TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-10-22_22:23:11 Ubuntu 14.04 following your test case - Set as New - Sophie -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 76714] EDITING: Multiple Language not supported?
https://bugs.freedesktop.org/show_bug.cgi?id=76714 --- Comment #7 from GRB gbod...@gmail.com --- I'm a native English speaker, but I can't get French spelling to work in Libreoffice. Version: 4.2.6.3 Build ID: 420m0(Build:3) Mint 17 Mate version -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85365] New: Build failure: assertion failed in CppunitTest_writerperfect_stream with clang 3.5
https://bugs.freedesktop.org/show_bug.cgi?id=85365 Bug ID: 85365 Summary: Build failure: assertion failed in CppunitTest_writerperfect_stream with clang 3.5 Product: LibreOffice Version: 4.4.0.0.alpha0+ Master Hardware: x86 (IA32) OS: Linux (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Installation Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: lukebe...@hotmail.com Currently it's impossible to build LO with the compliers on Ubuntu 14.10. Bug 78174 prevents gcc from working. And this error prevents clang from working. $ lsb_release -rcd ; uname -rm Description:Ubuntu 14.10 3.16.0-22-generic i686 $ clang --version Ubuntu clang version 3.5.0-4ubuntu2 (tags/RELEASE_350/final) $ cat autogen.input CC=clang CXX=clang++ --disable-gstreamer-0_10 --enable-gstreamer Build log: [build CHK] filter [build CUT] writerperfect_stream /media/luke/69e81ab4-a375-4ae1-afad-ded6e0f00c45/home/luke/Downloads/lo/core/writerperfect/qa/unit/WPXSvStreamTest.cxx:330:(anonymous namespace)::WPXSvStreamTest::testStructured assertion failed - Expression: !pSubStream-isEnd() WPXSvStreamTest.cxx:330:Assertion Test name: (anonymous namespace)::WPXSvStreamTest::testStructured assertion failed - Expression: !pSubStream-isEnd() Failures !!! Run: 9 Failure total: 1 Failures: 1 Errors: 0 Error: a unit test failed, please do one of: export DEBUGCPPUNIT=TRUE# for exception catching export CPPUNITTRACE=gdb --args# for interactive debugging on Linux export CPPUNITTRACE=\[full path to devenv.exe]\ /debugexe # for interactive debugging in Visual Studio export VALGRIND=memcheck# for memory checking and retry using: make CppunitTest_writerperfect_stream /media/luke/69e81ab4-a375-4ae1-afad-ded6e0f00c45/home/luke/Downloads/lo/core/solenv/gbuild/CppunitTest.mk:76: recipe for target '/media/luke/69e81ab4-a375-4ae1-afad-ded6e0f00c45/home/luke/Downloads/lo/core/workdir/CppunitTest/writerperfect_stream.test' failed make[1]: *** [/media/luke/69e81ab4-a375-4ae1-afad-ded6e0f00c45/home/luke/Downloads/lo/core/workdir/CppunitTest/writerperfect_stream.test] Error 1 make[1]: *** Waiting for unfinished jobs Makefile:231: recipe for target 'build' failed make: *** [build] Error 2 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 83846] Bad allocation on Windows 8.1 x32 when working with master document
https://bugs.freedesktop.org/show_bug.cgi?id=83846 kkristov...@wmconnect.com changed: What|Removed |Added Component|Writer |Presentation Summary|Bad allocation on Windows |Bad allocation on Windows |7 x64 when working with |8.1 x32 when working with |master document |master document -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85356] Hindi script improperly rendered in LibreOffice (in some cases)
https://bugs.freedesktop.org/show_bug.cgi?id=85356 Adolfo Jayme f...@libreoffice.org changed: What|Removed |Added Attachment #108280|text/plain |application/vnd.oasis.opend mime type||ocument.text -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84924] FILESAVE Unexpected error cause software crash when saving as .xlsx with Edit Changes on
https://bugs.freedesktop.org/show_bug.cgi?id=84924 --- Comment #8 from Alan Jenkin alanjen...@gmail.com --- Using 4.3 seems to have solved the problem. Thanks. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85335] Glue points window/dialog contains two title bars
https://bugs.freedesktop.org/show_bug.cgi?id=85335 --- Comment #4 from Adolfo Jayme f...@libreoffice.org --- You can work around the problem by installing a compositor in Lubuntu, such as Compton. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85056] Writer crash after copy paste specific text
https://bugs.freedesktop.org/show_bug.cgi?id=85056 --- Comment #6 from Joel Madero jmadero@gmail.com --- Nope - that's sufficient for now. Thanks! We're always looking for new talent to join QA in triaging bugs. Since you were able to follow the instructions and get a backtrace, it would be great if you had a bit of time to help us get through our list of unconfirmed bugs. Send me an email if you're interested! Thanks :-D -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85342] Expert configuration: preference names and properties not sorted alphabetically
https://bugs.freedesktop.org/show_bug.cgi?id=85342 Xisco Faulí aniste...@gmail.com changed: What|Removed |Added Keywords||bisected CC||aniste...@gmail.com --- Comment #3 from Xisco Faulí aniste...@gmail.com --- I guess this issue was introduced by 0f9f361311967375cf8e3409ebc7168322641189 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84513] EDITING Cutting table row (or column) doesn't register an undo event
https://bugs.freedesktop.org/show_bug.cgi?id=84513 sophie gautier.sop...@gmail.com changed: What|Removed |Added Status|UNCONFIRMED |NEW CC||gautier.sop...@gmail.com Ever confirmed|0 |1 --- Comment #1 from sophie gautier.sop...@gmail.com --- Hi, tested with master under Linux, confirmed, set as New - Sophie -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 80137] EDITING: Paste array formula into range pastes as non-array formula
https://bugs.freedesktop.org/show_bug.cgi?id=80137 --- Comment #5 from Wolfgang j...@psilosoph.de --- Bug is very annoying. Unavoidable use of array formulae is likely to occur in a context where 'Fill' 'Down' would apply extensively. My most recent example: Reorganising a database-like data collections: extracting information from one to many cells. Resolving should be not too expensive as filling to the Left / Right is not broken. This is a vote for higher 'Importance'. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 70048] Other: No undo using table in Impress after moving from cell to another
https://bugs.freedesktop.org/show_bug.cgi?id=70048 sophie gautier.sop...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED CC||gautier.sop...@gmail.com Resolution|--- |WORKSFORME --- Comment #3 from sophie gautier.sop...@gmail.com --- Hi, tested today for a relative bug and it works fine using 4.3.2.1 and master both under Linux. I used Jérôme test case - Closing as worksforme, it should have been corrected with another bug. Sophie -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84506] docx opening not correct
https://bugs.freedesktop.org/show_bug.cgi?id=84506 Xisco Faulí aniste...@gmail.com changed: What|Removed |Added Status|NEW |RESOLVED CC||aniste...@gmail.com Resolution|--- |WORKSFORME --- Comment #2 from Xisco Faulí aniste...@gmail.com --- I change the status to WORKFORME as I can't reproduce this issue with Version: 4.4.0.0.alpha0+ Build ID: 0ea9722f72c1bece218013cce4c5d9097994408f TinderBox: Win-x86@51-TDF, Branch:MASTER, Time: 2014-09-23_06:09:39 nor Version: 4.4.0.0.alpha0+ Build ID: d72d71517ea3b13a1a5ddb685243c11ec7caa893 Time: 2014-07-10 OS: Ubuntu 14.04 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84315] Numeric values are not shown and displayed as 0 when using --enable-mergedlibs
https://bugs.freedesktop.org/show_bug.cgi?id=84315 --- Comment #29 from Björn Michaelsen bjoern.michael...@canonical.com --- (In reply to Dan Lewis from comment #27) Have they fixed the problem with a newer version of the download file? https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1373928/comments/23 This bug shall remain open though until this works again with --mergedlibs -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 83983] FILEOPEN: Regression in 4.4 master loading an ODT which contains a style with style:font-independent-line-spacing=true
https://bugs.freedesktop.org/show_bug.cgi?id=83983 Xisco Faulí aniste...@gmail.com changed: What|Removed |Added Keywords||bisected CC||aniste...@gmail.com Whiteboard||bibisected --- Comment #5 from Xisco Faulí aniste...@gmail.com --- It seems that the commit that caused this regression was identified. (Or at least a commit is suspected as the offending one.) Thus setting keyword bisected. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 68619] REPORTBUILDER: Functions in fields were changed to user-defined-functions in properties of the field
https://bugs.freedesktop.org/show_bug.cgi?id=68619 --- Comment #20 from rob...@familiegrosskopf.de --- Created attachment 108302 -- https://bugs.freedesktop.org/attachment.cgi?id=108302action=edit Functions in the report - Accumulation with some fields only user-defined Open the report for editing. Have a look at the different functions in the group-footer. All functions had been created by the Report-Builder. The functions of the fields on the right side look like user-defined functions. Only the fieldname differs from the other functions. If the fieldname has characters like _ or - the function is created as user-defined function. Could be it is the same with many other special characters. I haven't tested more than this. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 68619] REPORTBUILDER: Functions in fields were changed to user-defined-functions in properties of the field
https://bugs.freedesktop.org/show_bug.cgi?id=68619 rob...@familiegrosskopf.de changed: What|Removed |Added Version|4.1.1.2 release |Inherited From OOo --- Comment #21 from rob...@familiegrosskopf.de --- Changed the version to Inherited From OOo, because the bug could be reproduced with LO 3.3.0beta1 also. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85328] flat ODS data loss: converting chart data ranges to static chart data tables
https://bugs.freedesktop.org/show_bug.cgi?id=85328 --- Comment #2 from László Németh nem...@numbertext.org --- Workaround: instead of referring other sheets, copy the data of them to the sheet of the chart (as in the example file of the Bug 79676), and load the document in a LibreOffice version fixed in Bug 79676, eg. LO 4.3.1.2. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 83846] Bad allocation on Windows 7 x32 when working with master document
https://bugs.freedesktop.org/show_bug.cgi?id=83846 Darius Daniel Grigoras daniel.grigo...@movidius.com changed: What|Removed |Added Summary|Bad allocation on Windows |Bad allocation on Windows |8.1 x32 when working with |7 x32 when working with |master document |master document -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 83846] Bad allocation on Windows 7 x64 when working with master document
https://bugs.freedesktop.org/show_bug.cgi?id=83846 Darius Daniel Grigoras daniel.grigo...@movidius.com changed: What|Removed |Added Summary|Bad allocation on Windows |Bad allocation on Windows |7 x32 when working with |7 x64 when working with |master document |master document -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84927] Calc - Errors in function Conditional Formatting
https://bugs.freedesktop.org/show_bug.cgi?id=84927 Jacques Guilleron guillero...@aol.com changed: What|Removed |Added Status|UNCONFIRMED |NEEDINFO CC||guillero...@aol.com Ever confirmed|0 |1 --- Comment #1 from Jacques Guilleron guillero...@aol.com --- I Llogic, Once set conditional formatting for C2, you can use Paintbrush to copy and paste it to the range you want. Click on C2 to select the cell, click on paintbrush to copy the format and select the range you desire. Format is applied when you release mouse button. Another way to do that: Format Conditional Format Manage: Select C2. Edit: In the range windows insert : and set K31, for example, or D31. OK to apply our settings. you can delete C3, C4, C5 and D3, D4, D5. OK again. The whole range from C2 to D31 ot K31 is formated. Is there a problem to do this for you? Jacques -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85371] New: Redim with function name
https://bugs.freedesktop.org/show_bug.cgi?id=85371 Bug ID: 85371 Summary: Redim with function name Product: LibreOffice Version: 4.2.6.3 release Hardware: x86 (IA32) OS: Linux (All) Status: UNCONFIRMED Severity: minor Priority: medium Component: BASIC Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: ge.hu...@gmx.net Created attachment 108304 -- https://bugs.freedesktop.org/attachment.cgi?id=108304action=edit Nothing new here. Textfile with the code from the description. Trying to Redim a field inside a function with the function name fails with an Reading Error. Property is read only-error. Run this code, to see the error: Sub Main Dim FieldOfLongs() As Long Dim l As Long l = foo(FieldOfLongs) End Sub Function foo(FieldOfLongs() As Long) As Long Print foo ist actually foo Dim Zero As Long Redim FieldOfLongs(Zero) As Long 'Redim works Redim FieldOfLongs(foo) As Long 'Redim fails with error End Function The expected behaviour is, that the function name should behave just like any other variable within the function. Problem arises on Lubuntu 14.04 with Version: 4.2.6.3 Build-ID: 420m0(Build:3) The error actually says Lesefehler. Eigenschaft ist schreibgeschützt in my Germann version of LO. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84965] Writer crashes when opening specific document, or pasting its contents from Word or WordPad
https://bugs.freedesktop.org/show_bug.cgi?id=84965 --- Comment #10 from cant...@gmail.com --- Joel, I thought I did that already? Did you check the file I last attached? -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 70048] Other: No undo using table in Impress after moving from cell to another
https://bugs.freedesktop.org/show_bug.cgi?id=70048 --- Comment #4 from Jérôme Borme jer...@escreve.me --- (As original reporter,) I tested with 4.3.1.2 and the bug is not here any more. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84935] Intermittent crash on exit
https://bugs.freedesktop.org/show_bug.cgi?id=84935 --- Comment #5 from Matthew Francis fdb...@neosheffield.co.uk --- Created attachment 108307 -- https://bugs.freedesktop.org/attachment.cgi?id=108307action=edit Updated backtrace After commit a1fad26e045ff1fec0c63243e3516ef2da7f390d Differs at frame 16 -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85373] New: Suggestion: add option to flip light/dark areas of the display
https://bugs.freedesktop.org/show_bug.cgi?id=85373 Bug ID: 85373 Summary: Suggestion: add option to flip light/dark areas of the display Product: LibreOffice Version: 4.3.2.2 release Hardware: All OS: Windows (All) Status: UNCONFIRMED Severity: enhancement Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: john...@mail.be Problem description: I would like to suggest that all libreoffice components (but especially Writer and Calc) include the option for the user to reverse the light/dark areas of the display. That is, I would like to be able to have light text/menus on a dark background. Graphics could be displayed as they are, with a narrow white border around them. This would significantly reduce eye strain, especially in low light environments. And AFAIK it is a feature that macrosloth does not have! [Please note that this is not specific to the Version that I selected above - I had to select a version in order to be able to enter this text.] Current behavior: black text shown on white background Expected behavior: white text on black background -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 84854] Calc issues with screen drawing(all Windows and 32-bit Linux)
https://bugs.freedesktop.org/show_bug.cgi?id=84854 Jan Holesovsky ke...@collabora.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #61 from Jan Holesovsky ke...@collabora.com --- Thank you all for helping with this, and for finding out the exact commit that caused this! I have reverted the change, and the follow-up work there, Calc again works for me on Windows. The plan now is to use boost::rational in a less invasive way :-) The patches that fix this are: http://cgit.freedesktop.org/libreoffice/core/log/?qt=rangeq=0bab8aee77cfc2ffdbc6d3ef6a869284bc12dff4..31af61ea091cc895b893c849f2130aa35792b7db -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 79641] LibreOffice 4.4 most annoying bugs
https://bugs.freedesktop.org/show_bug.cgi?id=79641 Bug 79641 depends on bug 84854, which changed state. Bug 84854 Summary: Calc issues with screen drawing(all Windows and 32-bit Linux) https://bugs.freedesktop.org/show_bug.cgi?id=84854 What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85375] New: Existing Formattings can not be altered
https://bugs.freedesktop.org/show_bug.cgi?id=85375 Bug ID: 85375 Summary: Existing Formattings can not be altered Product: LibreOffice Version: 4.3.2.2 release Hardware: Other OS: Windows (All) Status: UNCONFIRMED Severity: normal Priority: medium Component: Writer Assignee: libreoffice-bugs@lists.freedesktop.org Reporter: mh...@gmx.net Opening the assistent/flyout with safed format-templates (F11) I can not get an existing format to get/keep the changes here: writer/table content Font 11pt == 10 pt: failed new build derived formats seems to work m. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 85179] FILEOPEN: RTF - Image border not preserved
https://bugs.freedesktop.org/show_bug.cgi?id=85179 Miklos Vajna vmik...@collabora.co.uk changed: What|Removed |Added Status|NEW |ASSIGNED Assignee|libreoffice-b...@lists.free |vmik...@collabora.co.uk |desktop.org | --- Comment #3 from Miklos Vajna vmik...@collabora.co.uk --- The problem is that we first create a shape (which has the proper border) and later we decide if it gets converted to a Writer picture or not. E.g. for rotated shapes, there is no such conversion. When there *is* such a conversion, we fail to copy the line properties as border properties over to the Writer picture. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31914] Writer: incorrectly formatting docx, and missing first page
https://bugs.freedesktop.org/show_bug.cgi?id=31914 --- Comment #11 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32420] Add TeX like \not to Math
https://bugs.freedesktop.org/show_bug.cgi?id=32420 --- Comment #5 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32252] [UI] Spreadsheet window without focus should not show cell cursor
https://bugs.freedesktop.org/show_bug.cgi?id=32252 --- Comment #4 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 30571] DRAW: 'graphics Mode' icon without function in vertical toolbar arrangement
https://bugs.freedesktop.org/show_bug.cgi?id=30571 --- Comment #28 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32664] Keyboard volume keys don't work when LibreOffice is in focus
https://bugs.freedesktop.org/show_bug.cgi?id=32664 --- Comment #50 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31555] Pasting test copied from Adobe Acrobat Reader messes up non-ascii characters
https://bugs.freedesktop.org/show_bug.cgi?id=31555 --- Comment #4 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 30744] Deprecate the gallery
https://bugs.freedesktop.org/show_bug.cgi?id=30744 --- Comment #8 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32418] Add an insert symbol to Math
https://bugs.freedesktop.org/show_bug.cgi?id=32418 --- Comment #5 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31915] Modal dialogs aren't on OS X and multiple copies can be opened simultaneously or menu entries activated
https://bugs.freedesktop.org/show_bug.cgi?id=31915 --- Comment #8 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32415] Add an option to use English names for Greek characters on Math
https://bugs.freedesktop.org/show_bug.cgi?id=32415 --- Comment #10 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31077] Copy/Paste from OOo Calc to LibreOffice Calc inserts OLE object
https://bugs.freedesktop.org/show_bug.cgi?id=31077 --- Comment #31 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32359] Collation in lists doesn’t take into account language-specific letters (Ñ for Spanish, ÅÄÖ for Swedish, …)
https://bugs.freedesktop.org/show_bug.cgi?id=32359 --- Comment #5 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32419] When inserted on Writer, get Base size for formulas from underlining paragraph
https://bugs.freedesktop.org/show_bug.cgi?id=32419 --- Comment #11 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32360] tabstops on TOC are no fully functional (do not support right and middle alignment)
https://bugs.freedesktop.org/show_bug.cgi?id=32360 --- Comment #4 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31491] 'Find Replace' across multiple open documents across different LibO applications
https://bugs.freedesktop.org/show_bug.cgi?id=31491 --- Comment #8 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32283] PDF not correctly imported when draged into LibO new empty document
https://bugs.freedesktop.org/show_bug.cgi?id=32283 --- Comment #12 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 30456] UI: Enhance Merge Cell Dialog with optionsshift content, keep content in covered cell, empty covered cell
https://bugs.freedesktop.org/show_bug.cgi?id=30456 --- Comment #17 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32581] [EDITING] Add the possibility to retrieve the filename of a movie or sound inserted in a document
https://bugs.freedesktop.org/show_bug.cgi?id=32581 --- Comment #8 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32281] Export a log of emails not sent in 'Sending e-mail messages' dialog
https://bugs.freedesktop.org/show_bug.cgi?id=32281 --- Comment #5 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 30716] Engineering Notation
https://bugs.freedesktop.org/show_bug.cgi?id=30716 --- Comment #23 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32521] [IMPRESS] Some borders of grouped cells have wrong style
https://bugs.freedesktop.org/show_bug.cgi?id=32521 --- Comment #7 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32362] Bad behavior of scalable brackets with large objects
https://bugs.freedesktop.org/show_bug.cgi?id=32362 --- Comment #24 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31092] Creating 3D smooth lines chart takes several minutes
https://bugs.freedesktop.org/show_bug.cgi?id=31092 --- Comment #6 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32484] Allow anchor settings in frame styles
https://bugs.freedesktop.org/show_bug.cgi?id=32484 --- Comment #9 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31398] RFE: LibreOffice Base should allow update/insert/drop query in sql-editor with hsqldb access controls
https://bugs.freedesktop.org/show_bug.cgi?id=31398 --- Comment #6 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32280] Add an option to 'Request read receipt' in 'Mail Merge Wizard'
https://bugs.freedesktop.org/show_bug.cgi?id=32280 --- Comment #5 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31241] faulty PDF from MATHTYPE equation
https://bugs.freedesktop.org/show_bug.cgi?id=31241 --- Comment #10 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32346] PRINTING 'fit to printable page' for large documents results in missing content
https://bugs.freedesktop.org/show_bug.cgi?id=32346 --- Comment #9 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31142] Runaway column selection in Calc
https://bugs.freedesktop.org/show_bug.cgi?id=31142 --- Comment #13 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32505] LibO Base - UI - Copy data dialog
https://bugs.freedesktop.org/show_bug.cgi?id=32505 --- Comment #13 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31683] Calc: Unable to display axis tick intervals with arbitrary label data.
https://bugs.freedesktop.org/show_bug.cgi?id=31683 --- Comment #7 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 31577] Calc INDIRECT range intermittently fails
https://bugs.freedesktop.org/show_bug.cgi?id=31577 --- Comment #14 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 32500] [Metabug] GTK style doesn't draw some elements via GTK
https://bugs.freedesktop.org/show_bug.cgi?id=32500 --- Comment #21 from QA Administrators qa-ad...@libreoffice.org --- Please read this message in its entirety before responding. Your bug was confirmed at least 1 year ago and has not had any activity on it for over a year. Your bug is still set to NEW which means that it is open and confirmed. It would be nice to have the bug confirmed on a newer version than the version reported in the original report to know that the bug is still present -- sometimes a bug is inadvertently fixed over time and just never closed. If you have time please do the following: 1) Test to see if the bug is still present on a currently supported version of LibreOffice (preferably 4.2 or newer). 2) If it is present please leave a comment telling us what version of LibreOffice and your operating system. 3) If it is NOT present please set the bug to RESOLVED-WORKSFORME and leave a short comment telling us your version and Operating System Please DO NOT 1) Update the version field 2) Reply via email (please reply directly on the bug tracker) 3) Set the bug to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
