https://bugs.kde.org/show_bug.cgi?id=294346 Summary: Bug reporter borked - multibug
Product: digikam
Version: 2.5.0
Platform: MS Windows
OS/Version: MS Windows
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo:
[hidden email]
ReportedBy:
[hidden email]
Version: 2.5.0
OS: MS Windows
I was not allowed to submit my crash on start bug of my brand new installation
of digikam (2.5.0 over 2.3.0) because the reporter failed to submit because
"comments can not be more than 65,535 bytes" ... so including the trace was a
bit of a hinderence bt at this point I could no longer use the back button to
change the crash report and when I tried to save the file apparently Windows
blocked saving the file to where I had specified and that jammed everything up
and the whole lot locked and needed killing from the windows console...
That, at my count is a lot of bugs and issues:
1) Crash on startup bug - sorry, no information due to following bugs
2) A crash report that is too big to save automatedly
3) Failure of the back button to work after an error has been identified in the
bug reporting mechanism
4) A save system that doesn't expect the save to ever fail due to lack of
permissions (which Windows is supposed to ask me about but never seems to do so
because the programs trying to save crash before it does)
If you really want the crash bug information (which I didn't seem to find any
information about in previous bugs?!?) I can submit it but at this moment I am
in no mood too... it's not like a didn't try nor spend a lot of time waiting
for the backtrace to compile (twice, the first time apparently I didn't have
enough information to submit a bug??)
It doesn't help that this has turned my working digiKam installation into a
brick *sigh* - so much for this "solution" - millennium hand and shrimp!
Reproducible: Always
Steps to Reproduce:
Try to report a crash bug with its backtrace and fill in a sentence for each of
the three categories listed as being helpful, try to use the greyed out back
button and then try and save the report temporarily to directory C: forgetting
for a split-second that this is a protected directory under Windows 7 because
it is the most obvious place to put it for the two minutes it will take to
transfer the contents into the online bug report mechanism.
Actual Results:
The whole things hangs and needs hard killed with Windows console
Expected Results:
1) Not crashed in the first place,
2) Submitted a standard bug report because 65,535 characters for a report
containing a backtrace is far too little,
3) Allow the use of the back button to make the report smaller,
4) Requested authorisation to save the file in a protected directory or else
timed out and requested a different directory.
MS Windows 7 Home Edition fully up to date as of today (18th Feb. 2012)
Previous install of digiKam was the supplied binary install of 2.3.0
Current install of digiKam is the supplied binary install of 2.5.0
--
Configure bugmail:
https://bugs.kde.org/userprefs.cgi?tab=email------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Locked
