OK, second time I tried to report a bug. It's not me.
After putting a sentence explaining what I was doing before the crash, I get a dialog asking if I can tell some more. I choose no. Then my only choice is quit of save the information - not send it in. And, if I pick save, and then I see it means save to a file, and I cancel, the whole thing just quits. This is exactly what happened the last time. Really frustrating that I spent all the effort to download debuginfo, check dups, and it was a complete waste of time.
On Fri, Mar 19, 2010 at 12:05 PM, Neal Becker ndbecker2@gmail.com wrote:
OK, second time I tried to report a bug. It's not me.
After putting a sentence explaining what I was doing before the crash, I get a dialog asking if I can tell some more. I choose no. Then my only choice is quit of save the information - not send it in. And, if I pick save, and then I see it means save to a file, and I cancel, the whole thing just quits. This is exactly what happened the last time. Really frustrating that I spent all the effort to download debuginfo, check dups, and it was a complete waste of time.
Means the information given wasn't enough for a good bugreport. The first sentence is kinda a header telling the general problem. The second (you said no) is where to give more information/telling what you did. Without that information (tell some more) it's not a useful bugreport. The behavior changed lately. Sending old style bugreports, without further information isn't possible any more AFAIK.
Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:05 PM, Neal Becker ndbecker2@gmail.com wrote:
OK, second time I tried to report a bug. It's not me.
After putting a sentence explaining what I was doing before the crash, I get a dialog asking if I can tell some more. I choose no. Then my only choice is quit of save the information - not send it in. And, if I pick save, and then I see it means save to a file, and I cancel, the whole thing just quits. This is exactly what happened the last time. Really frustrating that I spent all the effort to download debuginfo, check dups, and it was a complete waste of time.
Means the information given wasn't enough for a good bugreport. The first sentence is kinda a header telling the general problem. The second (you said no) is where to give more information/telling what you did. Without that information (tell some more) it's not a useful bugreport. The behavior changed lately. Sending old style bugreports, without further information isn't possible any more AFAIK.
It should warn the user that if they say 'no, they can't give more info' that it will close without sending the report!
On Fri, Mar 19, 2010 at 12:52 PM, Neal Becker ndbecker2@gmail.com wrote:
Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:05 PM, Neal Becker ndbecker2@gmail.com wrote:
OK, second time I tried to report a bug. It's not me.
After putting a sentence explaining what I was doing before the crash, I get a dialog asking if I can tell some more. I choose no. Then my only choice is quit of save the information - not send it in. And, if I pick save, and then I see it means save to a file, and I cancel, the whole thing just quits. This is exactly what happened the last time. Really frustrating that I spent all the effort to download debuginfo, check dups, and it was a complete waste of time.
Means the information given wasn't enough for a good bugreport. The first sentence is kinda a header telling the general problem. The second (you said no) is where to give more information/telling what you did. Without that information (tell some more) it's not a useful bugreport. The behavior changed lately. Sending old style bugreports, without further information isn't possible any more AFAIK.
It should warn the user that if they say 'no, they can't give more info' that it will close without sending the report!
Agreed.
On Friday 19 March 2010 12:10:14 Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:52 PM, Neal Becker ndbecker2@gmail.com wrote:
Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:05 PM, Neal Becker ndbecker2@gmail.com
wrote:
OK, second time I tried to report a bug. It's not me.
After putting a sentence explaining what I was doing before the crash, I get a dialog asking if I can tell some more. I choose no. Then my only choice is quit of save the information - not send it in. And, if I pick save, and then I see it means save to a file, and I cancel, the whole thing just quits. This is exactly what happened the last time. Really frustrating that I spent all the effort to download debuginfo, check dups, and it was a complete waste of time.
Means the information given wasn't enough for a good bugreport. The first sentence is kinda a header telling the general problem. The second (you said no) is where to give more information/telling what you did. Without that information (tell some more) it's not a useful bugreport. The behavior changed lately. Sending old style bugreports, without further information isn't possible any more AFAIK.
It should warn the user that if they say 'no, they can't give more info' that it will close without sending the report!
Agreed.
Last time I saw it, it actually said if the bug report itself wasn't useful, and offered to download debug packages to improve matters. That was only a couple of days ago. Are you saying this isn't so any more?
Anne
2010/3/19 Anne Wilson cannewilson@googlemail.com:
On Friday 19 March 2010 12:10:14 Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:52 PM, Neal Becker ndbecker2@gmail.com wrote:
Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:05 PM, Neal Becker ndbecker2@gmail.com
wrote:
OK, second time I tried to report a bug. It's not me.
After putting a sentence explaining what I was doing before the crash, I get a dialog asking if I can tell some more. I choose no. Then my only choice is quit of save the information - not send it in. And, if I pick save, and then I see it means save to a file, and I cancel, the whole thing just quits. This is exactly what happened the last time. Really frustrating that I spent all the effort to download debuginfo, check dups, and it was a complete waste of time.
Means the information given wasn't enough for a good bugreport. The first sentence is kinda a header telling the general problem. The second (you said no) is where to give more information/telling what you did. Without that information (tell some more) it's not a useful bugreport. The behavior changed lately. Sending old style bugreports, without further information isn't possible any more AFAIK.
It should warn the user that if they say 'no, they can't give more info' that it will close without sending the report!
Agreed.
Last time I saw it, it actually said if the bug report itself wasn't useful, and offered to download debug packages to improve matters. That was only a couple of days ago. Are you saying this isn't so any more?
That's still the same. We spoke about "additional information" or "can you tell what you did as it crashed". Forgot the exact wording.
On Friday 19 March 2010 15:53:41 Thomas Janssen wrote:
2010/3/19 Anne Wilson cannewilson@googlemail.com:
On Friday 19 March 2010 12:10:14 Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:52 PM, Neal Becker ndbecker2@gmail.com
wrote:
Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:05 PM, Neal Becker ndbecker2@gmail.com
wrote:
OK, second time I tried to report a bug. It's not me.
After putting a sentence explaining what I was doing before the crash, I get a dialog asking if I can tell some more. I choose no. Then my only choice is quit of save the information - not send it in. And, if I pick save, and then I see it means save to a file, and I cancel, the whole thing just quits. This is exactly what happened the last time. Really frustrating that I spent all the effort to download debuginfo, check dups, and it was a complete waste of time.
Means the information given wasn't enough for a good bugreport. The first sentence is kinda a header telling the general problem. The second (you said no) is where to give more information/telling what you did. Without that information (tell some more) it's not a useful bugreport. The behavior changed lately. Sending old style bugreports, without further information isn't possible any more AFAIK.
It should warn the user that if they say 'no, they can't give more info' that it will close without sending the report!
Agreed.
Last time I saw it, it actually said if the bug report itself wasn't useful, and offered to download debug packages to improve matters. That was only a couple of days ago. Are you saying this isn't so any more?
That's still the same. We spoke about "additional information" or "can you tell what you did as it crashed". Forgot the exact wording.
But if it says it is not good enough, and you can't give any more information, what else do you want it to do? I see no point in additional 'warnings' - the point is already made when it said that it is not useful.
Anne
Anne Wilson wrote:
On Friday 19 March 2010 15:53:41 Thomas Janssen wrote:
2010/3/19 Anne Wilson cannewilson@googlemail.com:
On Friday 19 March 2010 12:10:14 Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:52 PM, Neal Becker ndbecker2@gmail.com
wrote:
Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:05 PM, Neal Becker ndbecker2@gmail.com
wrote:
> OK, second time I tried to report a bug. It's not me. > > After putting a sentence explaining what I was doing before the > crash, I get a dialog asking if I can tell some more. I choose > no. > Then my only choice is quit of save the information - not send it > in. And, if I pick save, and then I see it means save to a file, > and I cancel, the whole thing just quits. This is exactly what > happened the last time. Really frustrating that I spent all the > effort to download debuginfo, check dups, and it was a complete > waste of time.
Means the information given wasn't enough for a good bugreport. The first sentence is kinda a header telling the general problem. The second (you said no) is where to give more information/telling what you did. Without that information (tell some more) it's not a useful bugreport. The behavior changed lately. Sending old style bugreports, without further information isn't possible any more AFAIK.
It should warn the user that if they say 'no, they can't give more info' that it will close without sending the report!
Agreed.
Last time I saw it, it actually said if the bug report itself wasn't useful, and offered to download debug packages to improve matters. That was only a couple of days ago. Are you saying this isn't so any more?
That's still the same. We spoke about "additional information" or "can you tell what you did as it crashed". Forgot the exact wording.
But if it says it is not good enough, and you can't give any more information, what else do you want it to do? I see no point in additional 'warnings' - the point is already made when it said that it is not useful.
Anne
No, I strongly disagree. I gave some info. I have done these reports before. It used to be that if you only gave a short description, it asked if you could give more info, and if you said no, it would continue the report. Now it just quits without warning.
2010/3/19 Anne Wilson cannewilson@googlemail.com:
On Friday 19 March 2010 15:53:41 Thomas Janssen wrote:
2010/3/19 Anne Wilson cannewilson@googlemail.com:
On Friday 19 March 2010 12:10:14 Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:52 PM, Neal Becker ndbecker2@gmail.com
wrote:
Thomas Janssen wrote:
On Fri, Mar 19, 2010 at 12:05 PM, Neal Becker ndbecker2@gmail.com
wrote:
> OK, second time I tried to report a bug. It's not me. > > After putting a sentence explaining what I was doing before the > crash, I get a dialog asking if I can tell some more. I choose no. > Then my only choice is quit of save the information - not send it > in. And, if I pick save, and then I see it means save to a file, > and I cancel, the whole thing just quits. This is exactly what > happened the last time. Really frustrating that I spent all the > effort to download debuginfo, check dups, and it was a complete > waste of time.
Means the information given wasn't enough for a good bugreport. The first sentence is kinda a header telling the general problem. The second (you said no) is where to give more information/telling what you did. Without that information (tell some more) it's not a useful bugreport. The behavior changed lately. Sending old style bugreports, without further information isn't possible any more AFAIK.
It should warn the user that if they say 'no, they can't give more info' that it will close without sending the report!
Agreed.
Last time I saw it, it actually said if the bug report itself wasn't useful, and offered to download debug packages to improve matters. That was only a couple of days ago. Are you saying this isn't so any more?
That's still the same. We spoke about "additional information" or "can you tell what you did as it crashed". Forgot the exact wording.
But if it says it is not good enough, and you can't give any more information, what else do you want it to do? I see no point in additional 'warnings' - the point is already made when it said that it is not useful.
I know what you mean. The is not useful part is if you're missing debuginfo packages. You can have a 3 star report, but if you can't give info about what you did as it crashed it doesn't report at all. Well, you could trick it probably by giving "blah blah blah" as description and it would send it ;) But i doubt the devels would be happy :)
On Friday 19 March 2010 17:52:48 Thomas Janssen wrote:
But if it says it is not good enough, and you can't give any more information, what else do you want it to do? I see no point in additional 'warnings' - the point is already made when it said that it is not useful.
I know what you mean. The is not useful part is if you're missing debuginfo packages. You can have a 3 star report, but if you can't give info about what you did as it crashed it doesn't report at all.
How could you not know what you were doing when it crashed? It doesn't ask for technicalities, just a simple description.
Well, you could trick it probably by giving "blah blah blah" as description and it would send it ;) But i doubt the devels would be happy :)
Sorry, I simply don't understand this thread. I've just reported a crash. This is the first I've done since the version changed. It asked me to confirm that I'd checked the backtrace for sensitive information. Part 2 of the display asks for steps to re-create the crash. I left that empty. Part 3 is labelled comments. I wrote two sentences about what had happened. The report went. I really don't see how it could be easier.
Anne
-
Anne Wilson -
Neal Becker -
Thomas Janssen