Bug 813647 - Stacktrace when closing a bug
Summary: Stacktrace when closing a bug
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: 4.2-1
Assignee: Simon Green
QA Contact:
URL:
Whiteboard:
: 813927 (view as bug list)
Depends On:
Blocks: BZ42
TreeView+ depends on / blocked
 
Reported: 2012-04-18 06:22 UTC by Krzysztof Daniel
Modified: 2018-12-09 06:29 UTC (History)
4 users (show)

Fixed In Version: 4.2.0-0.b26
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-20 05:00:39 UTC
Embargoed:


Attachments (Terms of Use)

Description Krzysztof Daniel 2012-04-18 06:22:04 UTC
I have observed this behaviour when using Eclipse Mylyn.

(1) Install eclipse and eclipse-mylyn-*
(2) Open any bug that is on QA state.
(3) Try to move it to 'CLOSED'
(4) Error appears that indicates bugzilla error:

(Eclipse says) Error may result when QAContact field not enabled.
((Embedded browser shows)
 Undef to trick_taint at Bugzilla/Util.pm line 67
       Bugzilla::Util::trick_taint('undef') called at Bugzilla/Bug.pm line
 4525
       Bugzilla::Bug::LogActivityEntry(766608, 'cf_last_closed', 'undef',
 '2012-04-17 07:22:48', 324097, '2012-04-17 07:22:48') called
 at ./extensions/RedHat/Extension.pm line 992
 
 ugzilla::Extension::RedHat::bug_end_of_update('Bugzilla::Extension::RedHat=HASH(0xa930c0)', 'HASH(0xe243760)') called at Bugzilla/Hook.pm line 33
       Bugzilla::Hook::process('bug_end_of_update', 'HASH(0xe243760)') called
 at Bugzilla/Bug.pm line 1157
       Bugzilla::Bug::update('Bugzilla::Bug=HASH(0xddf60d0)') called
 at /var/www/html/bugzilla/process_bug.cgi line 498

Comment 1 Simon Green 2012-04-18 11:13:45 UTC
I noticed this a few hours before you filed the bug. It applies to all cases where you close a bug for the first time. Will get it fixed tomorrow hopefully.

Comment 2 Simon Green 2012-04-18 21:45:34 UTC
*** Bug 813927 has been marked as a duplicate of this bug. ***

Comment 3 Simon Green 2012-04-20 05:00:39 UTC
Fix will be visible in the next update

  -- simon


Note You need to log in before you can comment on or make changes to this bug.