Closed
Bug 712288
Opened 13 years ago
Closed 13 years ago
User autocomplete fails with error in JSON/RPC/Server.pm
Categories
(Bugzilla :: Creating/Changing Bugs, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 706753
People
(Reporter: bkuemmer, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20100101 Firefox/9.0 Build ID: 20111206234556 Steps to reproduce: On a new Bugzilla 4.0.2 install, I noticed that the autocomplete feature did not work in User fields. Actual results: Using Firebug (on Firefox 9), I noticed the following error being logged when entering something in a user field (CC, Assignee, etc): Undefined subroutine &JSON::RPC::Procedure::check called at /usr/local/share/perl/5.12.4/JSON/RPC/Server.pm line 316 ./checksetup.pl --check-modules does not log any missing modules (except for mod_perl and Apache-SizeLimit which we are not using). The JSON modules are available: Checking for JSON-RPC (any) ok: found v1.01 Checking for JSON-XS (v2.0) ok: found v2.32 Expected results: The partially entered username should have resolved to a list of users for autocompletion
if you're running debian sid, this is most likely a duplicate of bug 706753.
Reporter | ||
Comment 2•13 years ago
|
||
The OS is Ubuntu 11.10 (GNU/Linux 3.0.0-12-server x86_64)
Comment 3•13 years ago
|
||
(In reply to Bernd Kuemmerlen from comment #0) > Undefined subroutine &JSON::RPC::Procedure::check called at > /usr/local/share/perl/5.12.4/JSON/RPC/Server.pm line 316 > Checking for JSON-RPC (any) ok: found v1.01 As far as I know, JSON::RPC 1.01 no longer contains JSON/RPC/Server.pm. The last stable version to have it is 0.96. I'm not sure how you managed to get this file doing a call. Looks like a broken package to me.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Reporter | ||
Comment 4•13 years ago
|
||
OK, thanks, after some manual perl module juggling (I didn't realize that Bugzilla also had "local" versions of modules when they were installed through install-module.pl), it finally works now!
You need to log in
before you can comment on or make changes to this bug.
Description
•