Closed
Bug 1339658
Opened 9 years ago
Closed 9 years ago
Why I am getting error: Unable to open the chart datafile ./data/mining/0-> when I tried to select "Old Charts" under Reports(using Bugzilla 5.0.1 in Fedora Linux 22 + MariaDB)
Categories
(Bugzilla :: Bugzilla-General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: fmalek, Unassigned)
Details
Attachments
(1 file)
|
22.53 KB,
application/vnd.openxmlformats-officedocument.wordprocessingml.document
|
Details |
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; rv:11.0) like Gecko
Steps to reproduce:
Environment:
Linux; Fedora 64 bits
DB: MaiaDB
Bugzilla version: 5.0.1
Step I took:
1. Log into Bugzilla database
2. Select Report
3. Select Old Chart
4. Got error :Unable to open the chart datafile ./data/mining/0
Actual results:
Unable to open the chart datafile ./data/mining/0
Expected results:
https://gcc.gnu.org/bugzilla/page.cgi?id=gcc/weekly-bug-summary.html
Comment 1•9 years ago
|
||
Several things:
* Fedora Linux 22 is an ancient version that was supported until July 2016. It is nowadays full of security issues. You have way bigger problems than Bugzilla Reports not working.
* The message "Unable to open the chart datafile" shows a lot of results in an internet search engine; https://wiki.mozilla.org/Bugzilla:FAQ#Old_Charts_complain_about_.22Unable_to_open_the_chart_datafile_..2Fdata.2Fmining.2F-All-.22 being one of them. In any case that is a not a "bug" (a problem in existing program code) or a feature request, but a support request (changing the settings, adjusting your installation, questions how to do something). Please use http://www.bugzilla.org/support/ for that - Thanks!
* Even if you solved your problem, you will never get your "Expected results" because the link you posted is custom code in GCC Bugzilla which is not included in the Bugzilla code base itself.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•