within 15 minutes libreoffice writer crashed 5 times.

Please try resetting the user profile, sometimes solves strange issues.
https://wiki.documentfoundation.org/UserProfile
Usually it's enough renaming/deleting the file "user/registrymodifications.xcu",  it affects all the options in Menu/Tools/Options, and the files "user/basic/dialog.xlc" and "scrip.xlc" are overwritten, additionally custom colors in "user/config/standard.soc" are lost.

As for crashes, upgrading to more stable Windows platform should solve most of them.

dear urmas!

could you please (1) read and (2) think before you answer?

(1) => i don't use windows
(2) => it's not windows or linux constantly crahsing. it's the libreoffice suite that crashes on several occasions. other applications don't crash. just the office suite.

and for your information: i use 2 different linux distributions and libreoffice does not work properly IN BOTH!

so why would i change the operating system due to the office suite having several bugs and constantly crashing? is there any reasonable explanation for this comment? are you a developer? you sure sound like one. because your way of logically thinking would explain the bugs.

@m.a.riosv ... thanks. i'm not sure it's going to solve the problems. but i'll give it a try.

Maybe Urmas missed a few commas in his comment?

As in: "Maybe upgrading to a more stable, Windows, platform..." 

(Sorry, could not resist. Popcorn time?)

I'm sorry to disappoint, but yes, there are lots of bugs, and only so many people working on getting rid of them.

Anyway, you could also try step 3. (Graphics-related issues) from [1].

Getting and attaching a backtrace from a crash could give a clue what might be causing that particular crash [2]. The different crashes are likely related, and have the same basic cause.

[1] https://wiki.documentfoundation.org/QA/FirstSteps
[2] https://wiki.documentfoundation.org/QA/BugReport/Debug_Information#GNU.2FLinux:_How_to_get_a_backtrace

On the danger of causing more rampage:

poft: please keep in mind that currently there are over 10k confirmed bugs for LO. The change you are seeing one of those if fairly high.

But the only way to improve this situation is fix bugs and that can only be done one bug at a time. Which is why there is the rule to post one bug per issue. And that makes sense since otherwise things get out of hand much too quickly.

So I suggest to follow the described general debugging steps (reset user profile) etc and if any issues persist after that, file new bugs. And when doing that, please:

* post exact reproduce steps
* post a sample document with which you are seeing the problem (should the problem be related to a document)
* provide as much info as possible

Random rampage will neither help you nor the devs.

Closing this as invalid. Since violating the one bug per issue rule.

From the tone of your initial report I take your frustration level is on 10 already. So if you do not want to go through this process, you don't have to of course. But again, keep in mind that that's the only way to improve status quo and make a better office suite for other humans to follow.

And I can assure you one last thing: I have been following LO QA for a few years now and got into that stressful time consuming occupation out of the same frustration you are in. And things have improved a lot. Just recently a lot of regressions have been fixed. The regression count went down from ~760 to 634 atm. This is a huge accomplishment but if you are not involved it may look like nothing is happening behind the scenes.

Have a nice day,
-_-

(In reply to steve -_- from comment #7)
> On the danger of causing more rampage:
> 
> poft: please keep in mind that currently there are over 10k confirmed bugs
> for LO. The change you are seeing one of those if fairly high.
> 
> But the only way to improve this situation is fix bugs and that can only be
> done one bug at a time. Which is why there is the rule to post one bug per
> issue. And that makes sense since otherwise things get out of hand much too
> quickly.
> 
> So I suggest to follow the described general debugging steps (reset user
> profile) etc and if any issues persist after that, file new bugs. And when
> doing that, please:
> 
> * post exact reproduce steps
> * post a sample document with which you are seeing the problem (should the
> problem be related to a document)
> * provide as much info as possible
> 
> Random rampage will neither help you nor the devs.
> 
> Closing this as invalid. Since violating the one bug per issue rule.
> 
> From the tone of your initial report I take your frustration level is on 10
> already. So if you do not want to go through this process, you don't have to
> of course. But again, keep in mind that that's the only way to improve
> status quo and make a better office suite for other humans to follow.
> 
> And I can assure you one last thing: I have been following LO QA for a few
> years now and got into that stressful time consuming occupation out of the
> same frustration you are in. And things have improved a lot. Just recently a
> lot of regressions have been fixed. The regression count went down from ~760
> to 634 atm. This is a huge accomplishment but if you are not involved it may
> look like nothing is happening behind the scenes.
> 
> Have a nice day,
> -_-



first of all, i can't "keep" something in mind, that hasn't been there. in terms of libreoffice i am a user. so, i don't know how many bugs it has. and although i find that better, it feels like i'm finding out at a record-breaking fast pace.

bugs can only be fixed one at a time? that's wrong too. besides one fix could fix more than one problem, theoretically speaking, does libreoffice have only ONE developer? if not, more than one bug at a time can be fixed. if there are 5 developers for libreoffice, 5 at a time can be fixed. if there are 100 developers, 100 can be fixed simultaniously.

now, here is an interesting question. and i would really like to know the answer to that. because in the past years, software problems became more and more and more.

so here is the question: how is it possible to generate 10k bugs? 

before you answer this question, let me paint a picture for you: we create a simple program. we call it a calculator. so, first this calculator has to learn how to take the first operator. so, we create this function. now we check, if it works. there are 2 options. as a developer you might have heard of an "if". so, here is your 2 options if: IF it doesn't work => go back and fix it. IF it works => move on to the next task. next step is say, taking the second operator. so, you create that feature. again, you CHECK IF IT WORKS. IF it doesn't work => back to the ol' drawing board. it if works => next task. we add a function "addition". now we check. does it work? you know the 2 options. meanwhile our program has 3 features and it still works and has no bugs. if libreoffice has 10k bugs, i really wonder, how many features it has and how many WORKING features it has. because i've never heard of an official and released software, even less so a standard for various linux distributions, that is out there despite 10k flaws. well, i'm no measure though. just saying.

so, how is it possible, a program like libreoffice has 10k bugs?

know how that's possible? that's possible if today i work on this and tomorrow i work on that and the day after i do something else ... and very important: never check the result. 10k bugs is only possible, if i create feature after feature after feature, without checking if anything actually works.

here is another question: what are 1000 features good for, if 900 of them crash the software and another 70 of them work only under certain circumstances. the truth is, you have 30 features that work and 970 are a waste of time and cause more trouble than they help with.

@m.a.riosv ... i tried clearing the config folder. actually it turns out, i tried that before too. libreoffice still crashes every time i try to paste a url for a hyperlink. former version. the version i use now ... by the way: the current version is also WAY slower than the former one. as if the former one wasn't slow enough already.

to continue: so, if libreoffice crashes every time i paste a link, and in my document i have 23 links, ... i can ether never finish my work, because i can't paste the links. or it takes me say half an hour extra to write all the links in there manually. a task that could have been done in like 5 minutes with the paste function. here is the thing: that's only ONE problem. i mentioned 8 and there are some i forgot to mention. including libreoffice, my average day has i guess like 1000 of these time wasters? so, i'm not kidding if i say, a task i could perform in a text editor in say 5 hours, takes 3 days in libreoffice. so, what is the software good for? shouldn't it make my life easier, not more stressful? if this software has 10k bugs and changes are, i find 100 of them in a week, why does anyone waste time on this software. let's all go back to nano. at least that one works! are you seriously wondering about a rampage, if you tell me, the application has 10k bugs? 10k???

libreoffice makes my documents look more professional than plain texts. yet, something that could be done in 2 days, takes 2 weeks due to all the problems and crashes. so, what is it good for?

why do i install an office suite and when i perform some random change in the system, it takes me 14 hours to figure out, why suddenly the spell check in the office suite doesn't work anymore. you can't tell me that's thought through developing. this just can't be right. i love linux and tons of applications coming with it. but you know why linux can't compete with windows? here is one good reason! my spell check features stops working from one day to the other and it takes me 14 hours to figure out why. and at this point it's mere coincidence i stumble across the solution. because tons of people just seem to guess and nobody has a real SOLUTION! 14 hours! 14 hours in which i should have been doing my work! 14 hours of my life lost forever ...

what you are doing, is not coordinated. also, what's with the one bug rule? so, now i do the work for you? i use the program. waste tons of time because of the problems. next i don't continue my work. instead i go back and recreate all my steps to be able to send you an adequate report. of course along with my business files. also, now instead of one report, i take the time to create 8 reports. one for every single bug i've found within 2 hours. next, since that is not enough, i go back and test some theories ... so, now i don't run a business anymore. i'm no a software tester for you and i work for free?

here is a more likely scenario: i just stop using libreoffice. switch to windows. pay for microsoft office. and it's worth it because due to microsoft office not crashing when i paste links, i save tons of time, which in turn i can use for not only pleasure but also to MAKE money instead of losing it. in this scenario i don't need to "rampage". also developers ... i need to correct this term at this point ... from now on i make them "bug collectors" ... don't need to do something they don't seem to have a talent for. like developing.

seriously: staroffice, openoffice, libreoffice ... more than 20 years of history ... is there every going to come a point, where the office suite in linux is going to work? or are we going to develop backwards?

let me ask you yet another question: since according to some of the texts and the software behavior here nobody is working professional anymore and we are all here for the fun and for fooling around ... how are you guys paying your bills? i'm really curious. no offense. but obviously i miss something here. nothing works. nothing makes sense. but it seems, everybody is happy. HOW does that work? you tell me, you can only fix one bug at a time. but i have to do like 3 jobs at a time? my own, as well as testing and reporting for you? is there anybody who has family? hobbies? can you please help me? i'm really lost here. seriously. i don't understand how you do it. because i lose time here, i lose time there, ... time waste always and everywhere. so, how does it work for you? how do you work happily with software that has 10k bugs and tell me in all coolness "that's how it is. live with it" how?

but even though a number of people seem to be incapable of it, let's just start with something simple, maybe even logical. let's see if anyone can help with that.

the ONE BUG RULE:

so, bug 1: every time i paste a url in a hyperlink, the whole libreoffice writer crashes. let's start with that one. 

so, tell me: how do you as professionals paste a link into the url field (target? mine is not in english) in libreoffice without crashing writer? let's just start with that. changing version doesn't help. deleting the config folder doesn't work. 

simple. ONE BUG: how can i paste a url in a hyperlink in libreoffice writer, without writer crashing on me. let's start with that. one bug at a time, right?

in case you wanna know, version i currently run is 5.1.5.2.

how does it happen: i open the document. i highlight a hyperlink. i hit the hyperlink symbol in the icon bar. i click on the target url. i highlight it with crtl+a. i paste the url with crtl+v ... and gone it is.

the document is something very extraordinary. it's approx. 25 pages of legal statements. no images. no special characters. ... just legal statements with yes ... some hyperlinks. oh ... but in case you wanna know ... the text actually is maybe not that average though. as it turns out, even though you format everthing the same way, it's not the same. i'm not mentioning it as a bug, because of the one bug rule. i'm mentioning it, because you want to know about the "document that's causing the crash". what are the chances, hidden span tags you can't access in a text document could have something to do with hyperlink crashes? so, forget i mentioned it. one bug rule. paste a url in a hyperlink without crashing writer.

poft - it may surprise you to know that there is considerable academic literature on software development that discusses this problem the issues of defect density and so on. The problems space in an Open Source world is exacerbated by the need to encourage volunteers to work to fix bugs, and/or finding an economic model that funds and sustains significant bug fixing.

One of the problems motivating volunteers in the project is, unfortunately people such as yourself providing highly negative and non-constructive feedback; I would strongly recommend that you interact more positively.

Thank you for at least filing a bug; although I suspect that having several bugs wrapped into one is not optimal; Also your experience is far from normal, I use LibreOffice on Linux every day without these problems, I suspect that there is some problem with your Linux system that is causing these issues.

Can you provide full details of your linux system; its vendor, version, which desktop you're running under etc. [ is this some self-built thing? ;-], also - I would love to get some debuginfo packages installed, and get some stack traces out of LibreOffice when it crashes; quite possibly there is some common (and most likely OS related) problem here outside the scope of LibreOffice.

Thanks.

Attach the hyperlink crash document ASAP.

Not even commercial software customer support could troubleshoot such a case without a sample document and you know it.

And I'd still point out my suggestions in comment 6. Even if the crash isn't graphics-related, having a backtrace would be useful.

just fyi: ubuntu has over 100k bugs. chrome over 47k.

the length of your last post, assumes volunteers have insane amounts of time at their liberty. I can only speak for myself and my time is very limited. assuming otherwise of a very thin QA team is highly unconstructive.

also this is not a help desk or discussion round but a bug tracker and with that I end my engagement with this specific bug and OP.

Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

MassPing-NeedInfo-20170328