' { Q ! 0 < 0 H y ( A [ N y $ _ ! G ?" i # # $ $ $ $ $ ! % .% a A% % % $ % % & ,& I& % d& & & 4 & & & < ' 5 >' t' ' , ' ' ' " '
( ( 8( # S( w( ( 3 ( * ( ) ) () 5) O) ' j) $ ) ) * ) # ) * ' -* U* t* * + * 8 *
+ / #+ S+ k+ + + + 5 + / + %, 2, I, a, t,
, , > , 6 ,
3- A-
R- `- l- , - - - - - . !. 5. =. 0 V. ' . . . . $ . / ; 7/ s/ / / 8 / / - / @ "0 " c0 > 0 0 0 C 0 % :1 A `1 7 1 # 1 " 1 1 !2 S2 Y2 { m2 2 3 3 8 A3 ? z3 = 3 3 4 ) 4 + 4 % 4 1 %5 W5 %6 6 6 6 ! 7 07 D7 . `7 7 7 . 7 7
7 7 7 8 + "8 B N8 8 8 8 8 8 8 8 a 8 \9 u9 ' 9 9 1 9 9 " : , 6: c: u: x: f; v; ; ; a ; O < W< 2 k< <
< < < < = = 1= L= l= y= = = = = = 4 = 5 $> E Z> > < > 5 > 6 "? Y? f? v? ? ? ? + ? @ 0 @ Q@ a@ s@ @ 1 @ 0 @ @
A "A 3A SA oA ~A A A A A A
A A 0 A ? #B $ cB B B B Q B C 8C 6 TC C C & C C C # C ' D GD eD d mD D D D
D D 6 E * CE N nE 1 E l E s \F ) F w F # rG 5 G $ G G G xI J L M M D M dM pM yM ) M M M M M & M N "N A ;N h }N y O `P T S > nS i T U U U " U V /V BV cV R uV V V ! V W ;W ZW xW W W W 4 W W X E X 0 dX X X ' X X X 5 Y i } Qi i i ' i j - 9j gj j 0 j j j j k k k l J l B Sl l 4 l l l m m "m 5m Km ^m rm m # m m m m m m $
n $ 2n 1 Wn n E n 0 n 9
o Go Wo do " o " o o / o
p * "p Mp `p vp p ! p ! p p p q ' "q ! Jq lq q q q q q q q q * r 9 -r % gr r r r N r s -s # Fs js {s ! s s s 1 s 2 t ;t [t K et t t t
t t ! t ) u O :u 9 u X u _ v $ }v { v ! w * @w kw w < ) / g
x } P & 1 6 h
# K w 2 ^ ] z ( L _ \ R b v V e
p . f q s ; G [ J B ' 0 { F U d Q Y 3 8 5 Z - : M S a i + I ! % A ` > E " r O C X m l k D , c 4 | * $ ~ N T u 7 j ? W n H t o 9 y @ =
& [-v] [-c CONFFILE] -d DIR
or:
& [-v] [-c CONFFILE] [-d DIR] -t[ID] FILE...
Reports a problem to RHTSupport.
If not specified, CONFFILE defaults to
& [-vbf] [-c CONFFILE] -d DIR
or:
& [-v] [-c CONFFILE] [-d DIR] -t[ID] FILE...
Reports problem to Bugzilla.
The tool reads DIR. Then it logs in to Bugzilla and tries to find a bug
with the same abrt_hash:HEXSTRING in 'Whiteboard'.
If such bug is not found, then a new bug is created. Elements of DIR
are stored in the bug as part of bug description or as attachments,
depending on their type and size.
Otherwise, if such bug is found and it is marked as CLOSED DUPLICATE,
the tool follows the chain of duplicates until it finds a non-DUPLICATE bug.
The tool adds a new comment to found bug.
The URL to new or modified bug is printed to stdout and recorded in
'reported_to' element.
If not specified, CONFFILE defaults to
No changes were detected in the report
The report has been updated # Architecture # Backtrace
# Check that it does not contain any sensitive data (passwords, etc.) # Command line # Component # Core dump # Describe the circumstances of this crash below # Executable # Kernel version # Package # Reason of crash # Release string of the operating system # This field is read only
%llu bytes, %u files & -o [-d] DIR
newt tool to report problem saved in specified DIR & [-v] --target TARGET --ticket ID FILE...
Uploads FILEs to specified ticket on TARGET.
This tool is provided to ease transition of users of report package
to libreport. Recognized TARGETs are 'strata' and 'bugzilla',
first one invokes upload to RHTSupport and second - to Bugzilla.
Configuration (such as login data) can be supplied via files
& [-v] -d DIR [-c CONFFILE]
Sends contents of a problem directory DIR via email
If not specified, CONFFILE defaults to & [-v] -d DIR [-c CONFFILE] [-u URL]
Uploads compressed tarball of problem directory DIR to URL.
If URL is not specified, creates tarball in /tmp and exits.
URL should have form 'protocol://[user[:pass]@]host/dir/[file.tar.gz]'
where protocol can be http(s), ftp, scp, or file.
File protocol can't have user and host parts: 'file:///dir/[file.tar.gz].'
If URL ends with a slash, the archive name will be generated and appended
to URL; otherwise, URL will be used as full file name.
Files with names listed in $EXCLUDE_FROM_REPORT are not included
into the tarball.
CONFFILE lines should have 'PARAM = VALUE' format.
Recognized string parameter: URL.
Parameter can be overridden via $Upload_URL. & [-v] -d DIR [-o FILE] [-a yes/no] [-r]
Prints problem information to standard output or FILE & [-v] [-c CONFFILE]... -d DIR
Reports kernel oops to kerneloops.org (or similar) site.
Files with names listed in $EXCLUDE_FROM_REPORT are not included
into the tarball.
CONFFILE lines should have 'PARAM = VALUE' format.
Recognized string parameter: SubmitURL.
Parameter can be overridden via $KerneloopsReporter_SubmitURL. & [-vpod] [-g GUI_FILE] [-n PROG_NAME] DIR
GUI tool to analyze and report problem saved in specified DIR & [-vsp] -L[PREFIX] [DUMP_DIR]
or: & [-vsp] -e EVENT DUMP_DIR
or: & [-vsp] -a[y] DUMP_DIR
or: & [-vsp] -c[y] DUMP_DIR
or: & [-vsp] -r[y|o|d] DUMP_DIR '%s' is not an ordinary file 'strata' or 'bugzilla' (binary file, %llu bytes) (click here to view/edit) (no description) (not needed, '%s' already exists) --- Running %s --- Your comments are not private. They may be included into publicly visible problem reports. Add %s to CC list Add program names to log Add to existing Red Hat Support case Adding attachments to bug %i Adding comment to case '%s' Adding new comment to bug %d Address of Bugzilla server Address of the Red Hat support portal Advanced Alternate GUI file Analyze, collect and report problem data in DUMP_DIR Analyzing Analyzing did not start yet Analyzing failed. You can try another analyzer if available. Analyzing finished. You can proceed to the next step. Analyzing... Append Append new reports or overwrite the old one. Append to, or overwrite FILE Archive is created: '%s' Attach FILEs [to bug with this ID] Attach a file Attaching '%s' to case '%s' Attaching better backtrace Attaching problem data to case '%s' Bad value for '%s': %s Base URL to upload to Bug %i is CLOSED as DUPLICATE, but it has no DUP_ID Bug %i is CLOSED, but it has no RESOLUTION Bug is already reported: %i Bugzilla Bugzilla URL Bugzilla account password Bugzilla account user name Bugzilla couldn't find parent of bug %d Caching files from {0} made from {1} Can't copy '%s': %s Can't create a temporary directory in /tmp Can't create temporary file in /tmp Can't delete: '%s' Can't disable repository '{0!s}': {1!s} Can't extract files from '{0}' Can't extract package '{0}' Can't find crash thread Can't find packages for {0} debuginfo files Can't open '%s' for writing. Please select another file: Can't parse backtrace Can't remove %s, probably contains an error log Can't remove '{0}': {1} Can't setup {0}: {1}, disabling Can't write to '{0}': {1} Cancel Cancelled by user. Cannot run vi: $TERM, $VISUAL and $EDITOR are not set Case number (default:previously reported case): Case number: Check SSL key validity Checking for duplicates Checking for hints Click 'Apply' to start reporting Collecting Collecting did not start yet Collecting failed. You can try another collector if available. Collecting finished. You can proceed to the next step. Collecting... Compressing data Con_figure %s Config file Configuration file Configuration file (may be given many times) Configure E_vent Confirm data to report Create new Red Hat Support case Create reported_to in DIR Creating a new bug Creating a new case Details Display version and exit Do you still want to create a RHTSupport ticket? Documentation which might be relevant: Don't ask me again Don't store passwords Download cancelled by user Downloading ({0} of {1}) {2}: {3:3}% Downloading package {0} failed Downloading {0:.2f}Mb, installed size: {1:.2f}Mb. Continue? Dump directory Email was sent to: %s Empty RHTS login or password Empty login or password, please check your configuration Error Error in case creation at '%s', HTTP code: %d Error in case creation at '%s', HTTP code: %d, server says: '%s' Error in case creation at '%s': %s Error in case creation at '%s': no Location URL, HTTP code: %d Error in comment creation at '%s', HTTP code: %d Error in comment creation at '%s', HTTP code: %d, server says: '%s' Error in comment creation at '%s': %s Error in comment creation at '%s': no Location URL, HTTP code: %d Error initializing yum (YumBase.doConfigSetup): '{0!s}' Error retrieving filelists: '{0!s}' Error retrieving metadata: '{0!s}' Essential element '%s' is missing, can't continue Event Event Configuration Examples: ftp://[user[:pass]@]host/dir/[file.tar.gz], scp://[user[:pass]@]host/dir/[file.tar.gz], file:///dir/[file.tar.gz] Existing Red Hat Support case Extracting cpio from {0} Find BUG-ID according to DUPHASH Force reporting even if this problem is already reported Found the same comment in the bug history, not adding a new one Gnome Keyring is not available, your settings won't be saved! Go to next step How did this problem happen (step-by-step)? How can it be reproduced? Any additional comments useful for diagnosing the problem? Please use English if possible. How would you like to report the problem? How you would like to analyze the problem?
I don't know what caused this problem I reviewed the data and _agree with submitting it If you are reporting to a remote server, make sure you removed all private data (such as usernames and passwords). Backtrace, command line, environment variables are the typical items in need of examining. If you want to report the problem to a different destination, collect additional information, or provide a better problem description and repeat reporting process, press 'Forward'. Include Initializing yum Invalid boolean value '%s' Invalid input, program exiting... Invalid number '%s' Invalid utf8 character '%c' Item '%s' already exists and is not modifiable Kerneloops URL Kerneloops.org List possible events [which start with PREFIX] Log File Log to syslog Logger Logging into Bugzilla at %s Logging out Looking for needed packages in repositories Looks like corrupted xml response, because '%s' member is missing. Mailx Message subject Missing mandatory member 'bugs' Missing mandatory value N Name Name of the logfile Need writable directory, but '%s' is not writable. Move it to '%s' and operate on the moved data? New Red Hat Support case New bug id: %i No processing for event '%s' is defined No reporters available Noninteractive: don't ask questions, assume 'yes' Not attaching empty file '%s' Note: was already reported to '%s' Notify only (Do not mark the report as sent) OS release string Ok On the following screens, you will be asked to describe how the problem occurred, to choose how to analyze the problem (if needed), to review collected data, and to choose where the problem should be reported. Click 'Forward' to proceed. Oops server url Output file Packages to download: {0} Password Please try to install debuginfo manually using the command: "debuginfo-install %s" and try again
Possible sensitive data detected, please review the highlighted tabs carefully. Problem description Problem reported via %d report events (%d errors)
Provide additional information RH Portal URL Recipient Recipient's email Red Hat customer password Red Hat customer user name Regenerate backtrace Remove DIR after reporting Remove DUMP_DIR after reporting Removing {0} Report to Bugzilla bug tracker Report uploader Reporter(s): Reporting Reporting cancelled Reporting did not start yet Reporting disabled because the backtrace is unusable Reporting disabled because the backtrace is unusable. Reporting disabled because the rating does not contain a number '%s'. Reporting done Reporting failed. You can try another reporter if available. Reporting finished. You can proceed to the next step. Reporting has finished. You can close this window now. Reporting... Review the data Run EVENT on DUMP_DIR Run analyze event(s) on DUMP_DIR Run collect event(s) on DUMP_DIR Save as text file Save the problem data to a *.tar.gz in /tmp Save to tar archive Select additional files to attach to the report: Select analyzer Select analyzer: Select collector Select collector(s): Select how you would like to analyze the problem: Select how you would like to report the problem: Select reporter Select reporter(s): Send Binary Data Send binary files like coredump Send to kernel oops tracker Send via email Sender Sender's email Sending %s to %s Sending an email... Setting up yum repositories Show log Show password Size: Skip analyze steps, go through report steps only Specify this only if you modified your /etc/system-release file Status: %s%s%s %s/show_bug.cgi?id=%u Subject Submitting oops report to %s Successfully sent %s to %s The backtrace is incomplete, please make sure you provide the steps to reproduce. The report was appended to %s The report was stored to %s There were %d errors while collecting additional data
Ticket/case ID URL Unpacking failed, aborting download... Unsupported option type Updates which possibly help: Upload FILEs [to case with this ID] Upload as tar.gz file (via FTP/SCP/...) Uploaded: %llu of %llu kbytes Usage: Use this button to generate more informative backtrace after you installed additional debug packages User name Username Value Verify SSL View/edit a text file What additional information would you like to collect? When creating bug, attach binary files too Where do you want to upload the tarball with report in form login:password@url With -r: do not run analyzers, run only reporters Wrong settings detected for %s, reporting will probably fail if you continue with the current configuration. Wrong settings detected for %s, reporting will probably fail if you continue with the current configuration. You are trying to copy a file onto itself You can create bugzilla.redhat.com account <a href="https://bugzilla.redhat.com/createaccount.cgi">here</a> You have chosen number out of range You need to fill the how to before you can proceed... Your input is not valid, because of: y Project-Id-Version: libreport
Report-Msgid-Bugs-To:
POT-Creation-Date: 2013-08-06 13:55+0200
PO-Revision-Date: 2013-07-30 05:41+0000
Last-Translator: Wei Liu
Language-Team: Chinese (China)
Language: zh_CN
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=1; plural=0;
& [-v] [-c CONFFILE] -d DIR
or:
& [-v] [-c CONFFILE] [-d DIR] -t[ID] FILE...
向 RHTSupport 报告问题。
If not specified, CONFFILE defaults to
& [-vbf] [-c CONFFILE] -d DIR
or:
& [-v] [-c CONFFILE] [-d DIR] -t[ID] FILE...
向 Bugzilla 报告问题。
The tool reads DIR. Then it logs in to Bugzilla and tries to find a bug
with the same abrt_hash:HEXSTRING in 'Whiteboard'.
If such bug is not found, then a new bug is created. Elements of DIR
are stored in the bug as part of bug description or as attachments,
depending on their type and size.
Otherwise, if such bug is found and it is marked as CLOSED DUPLICATE,
the tool follows the chain of duplicates until it finds a non-DUPLICATE bug.
The tool adds a new comment to found bug.
The URL to new or modified bug is printed to stdout and recorded in
'reported_to' element.
If not specified, CONFFILE defaults to
未查出报告有更改
该报告已更新 # 架构 # 回溯
# 检查它是否包含任何敏感数据（密码等等） # 命令行 # 组件 # 核转储 # 在下面描述此崩溃的发生环境 # 可执行 # 内核版本 # 软件包 # 崩溃原因 # 操作系统的发行版本字符串 # 该字段为只读
%llu字节，%u个文件 & -o [-d] DIR
报告保存在指定 DIR 中问题的 newt 工具 & [-v] --target TARGET --ticket ID FILE...
将 FILE 上传到 TARGET 中指定的 ticket。
这个工具是用来简化用户向 libreport 提交报告软件包
的过程。可识别的 TARGET 为 'strata' 和 'bugzilla'，
第一个请求上传到 RHTSupport，而第二个请求上传到 Bugzilla。
可使用文件提供配置（比如登录数据）。
& [-v] -d DIR [-c CONFFILE]
使用电子邮件发送问题目录 DIR 中的内容
如未指定，则 CONFFILE 默认为 & [-v] -d DIR [-c CONFFILE] [-u URL]
向 URL 上传问题目录 DIR 的压缩 tarball。
如果没有指定 URL，请在 /tmp 中生成 tarball 并退出。
URL 的格式应为 'protocol://[user[:pass]@]host/dir/[file.tar.gz]'，
其中 protocol 可以是 http(s), ftp, scp, 或者 file。
文件 protocol 不能包含 user 和 host 部分：'file:///dir/[file.tar.gz].'
如果 URL 以斜线结束，则会生成归档名称，并附加到
URL 中；否则会将 URL 作为完整文件名使用。
在 tarball 中不包含 $EXCLUDE_FROM_REPORT 中所列
名称的文件。
CONFFILE 行应为 'PARAM = VALUE' 格式。
可识别字符串参数为：URL。
可使用 $Upload_URL 覆盖参数。 & [-v] -d DIR [-o FILE] [-a yes/no] [-r]
向标准输出或 FILE 输出问题信息 & [-v] [-c CONFFILE]... -d DIR
向 kerneloops.org（或类似）网站报告内核 oops。
在 tarball 中不包括在 $EXCLUDE_FROM_REPORT 中
列出的文件名。
CONFFILE 行应使用 'PARAM = VALUE' 格式。
可识别的字符串参数为：SubmitURL。
可使用 $KerneloopsReporter_SubmitURL 覆盖参数。 & [-vpod] [-g GUI_FILE] [-n PROG_NAME] DIR
分析和报告保存在指定 DIR 中的问题的 GUI 工具 & [-vsp] -L[PREFIX] [DUMP_DIR]
or: & [-vsp] -e EVENT DUMP_DIR
or: & [-vsp] -a[y] DUMP_DIR
or: & [-vsp] -c[y] DUMP_DIR
or: & [-vsp] -r[y|o|d] DUMP_DIR '%s' 不是普通文件 'strata' 或者 'bugzilla' （二进制文件，%llu字节） （点击这里查看/编辑） （没有说明） （不需要，'%s' 已存在） --- 运行 %s --- 您的注释不是保密的。会将其包含在公开的问题报告中。 在 CC 列表中添加 %s 在日志中添加程序名 添加到现有红帽支持案例 在 bug %i 中添加附件 在个案 '%s' 中添加注释 在 bug %d 中添加新注释 Bugzilla 服务器地址 红帽支持门户网站地址 高级 备用 GUI 文件 分析、收集并报告 DUMP_DIR 中的问题数据 分析中 分析还没有开始 分析失败。可以的话可以尝试使用另一个分析程序。 分析失败。您可以进行下一个步骤。 分析中...... 附加 附加新报告或者覆盖旧报告。 附加到，或者覆盖 FILE 生成归档：'%s' 附加 FILE【添加到使用这个 ID 的 bug 中】 附加文件 在案例 '%s' 中附加 '%s' 附加更好的 backtrace 在个案 '%s' 中添加问题数据 '%s' 值错误: %s 要上传的基本 URL 因为重复关闭 Bug %i，但它没有 DUP_ID Bug %i 已关闭，但还没有解决方案 Bug 已经被报告：%i Bugzilla Bugzilla URL Bugzilla 账户密码 Bugzilla 账户用户名 Bugzilla 无法找到 bug %d 的上级 bug 从 {0} 缓存来自 {1} 的文件 无法复制 '%s'：%s 无法在 /tmp 中创建临时目录 无法在 /tmp 中创建临时文件 无法删除：'%s' 无法禁用库 '{0!s}': {1!s} 无法从 '{0}' 中提取文件 无法提取软件包 '{0}' 无法找到崩溃线程 无法为 {0} debuginfo 文件找到软件包 无法打开 '%s' 进行编写。请选择另一个文件： 无法解析 backtrace 无法删除 %s，可能包含出错记录 无法删除 '{0}'：{1} 无法设置 {0}：{1}，禁用 无法写入 '{0}'：{1} 取消 用户取消。 无法运行 vi：还没有设置 $TERM、$VISUAL 和 $EDITOR 案例号 (默认：之前报告的案例): 案例号： 查看 SSL 密钥是否可用 检查是否有重复 检查是否有提示 点击 '应用' 开始报告 收集中 还没有开始收集 收集失败。可以的话可以尝试使用另一个收集程序。 收集失败。您可以进行下一个步骤。 收集中...... 压缩数据 配置 %s（_f） 配置文件 配置文件 配置文件（可在任意时间给出） 配置事件 (_v) 确认要报告的数据 创建新红帽支持案例 在 DIR 中创建 reported_to 生成新 bug 创建一个新个案 详情 显示版本并退出 您还想生成 RHT 支持 ticket 吗？ 可能的相关文档： 不再询问 不要保存密码 用户取消下载 下载（{1} 中的 {0}）{2}：{3:3}% 下载软件包 {0} 失败 正在下载 {0:.2f}Mb，已安装：{1:.2f}Mb。继续吗？ 转储目录 已发送电子邮件至：%s 空白 RHTS 登录或者密码 空白登录或者密码，请检查您的配置。 出错 在 ‘%s' 创建个案时出错，HTTP 代码：%d 在 '%s' 创建个案时出错，HTTP 代码：%d，服务器称：'%s' 在 '%s' 创建个案时出错：%s 在 '%s' 创建个案时出错：没有地址 URL，HTTP 代码：%d 在 '%s' 创建注释时出错，HTTP 代码：%d 在 '%s' 创建注释时出错，HTTP 代码：%d，服务器称：'%s' 在 '%s' 创建注释时出错：%s 在 '%s' 创建注释时出错：没有地址 URL，HTTP 代码：%d 启动 yum 出错（YumBase.doConfigSetup）： '{0!s}' 检索文件列表出错：'{0!s}' 检索元数据出错：'{0!s}' 缺少重要元素 '%s'，无法继续。 事件 事件配置 例如：ftp://[user[:pass]@]host/dir/[file.tar.gz], scp://[user[:pass]@]host/dir/[file.tar.gz], file:///dir/[file.tar.gz] 退出红帽支持案例 从 {0} 中提取 cpio 根据 DUPHASH 查找 BUG-ID 强制报告即时已报告了该问题 如果在 bug 历史记录中找到相同的注释则不要再添加 Gnome 令牌不可用，无法保存您的设置！ 进入下一步 这个问题是如何发生的（具体步骤）？怎样才可以复制？是否有其他可帮助诊断该问题的附加注释？请尽量使用英语。 您希望如何报告该问题？ 您希望如何分析该问题？
我不知道造成这个问题的原因 我检查了数据并同意（_a）提交 如果您是要向远程服务器报告，请确定删除所有私人数据（不如用户名和密码）。Backtrace、命令行、环境变量是检查所需的常规项目。 如果您要向不同的地点报告这个问题、收集附加信息或者更好地描述这个问题并重复报告过程，请按“前进”。 包括 启动 yum 无效的布尔值 '%s' 无效输入，程序正在退出... 无效的数字 '%s' 无效的 utf8 字符 ‘%c' 项目 '%s' 已存在且不可修改 Kerneloops URL Kerneloops.org 列出可能的事件【使用 PREFIX 开始】 日志文件 记录到 syslog 日志程序 在 %s 登录到 Bugzilla 退出 在库中查找所需软件包 看起来象是崩溃的 xml 响应，因为缺少 '%s' 成员。 Mailx 信息标题 缺少必要成员‘bugs’ 缺少必需值 N 名称 日志文件名称 需要可写入的目录，但 '%s' 不是可写入目录。将其移动到 '%s'，并在移动后的数据中进行操作。 新红帽支持案例 新 bug id：%i 没有定义针对事件 `%s' 的处理 没有可用的报告程序 无互动：不要提问，假设为“是” 不要附加空白文件 '%s' 注：已向 '%s' 提交报告 只是通知 (不要将报告标记为已发送) OS 发行本字符串 确定 在下面的页面中，会询问您该问题是如何发生的，选择如何分析该问题（如果有必要），查看收集的信息，并选择向哪里报告该问题。点击“前进”继续。 Oops 服务器 url 输出结果文件 要下载的软件包：{0} 密码 请尝试用命令"debuginfo-install %s"手动安装除错信息并重试
探测到可能的敏感数据，请仔细检查突出的标签。 问题描述 使用 %d report events (%d errors) 报告的问题
提供附加信息 红帽门户网站 URL 收件人 收件人电子邮件 红帽客户密码 红帽客户用户名 重新生成回溯 报告后删除 DIR 报告后删除 DUMP_DIR 正在删除 {0} 向 Bugzilla bug 跟踪程序报告 报告上传程序 报告程序： 报告 取消报告 报告还没有开始 因为回溯不可用而禁用报告 不能报告因为回溯不可用。 禁用报告因为 rating 不包括数字 '%s'。 报告完成 报告失败。可以的话可以尝试使用另一个报告程序。 报告失败。您可以进行下一个步骤。 报告已经结束。您现在可以关闭这个窗口。 报告中…… 审核数据 在 DUMP_DIR 中运行 EVENT 在 DUMP_DIR 中运行分析事件 在 DUMP_DIR 中运行集合事件 保存为文本文件 将有问题的数据保存到 *.tar.gz in /tmp 保存到 tar 归档 选择附加到该报告的附加文件： 选择分析程序 选择分析程序： 选择收集程序 选择收集程序： 选择怎样分析这个问题： 选择如何报告这个问题： 选择报告程序 选择报告程序： 发送二进制数据 发送类似核转储的二进制文件 发送到内核 oops 跟踪程序 通过电子邮件发送 发送者 发送者电子邮件 向 %s 发送 %s 发送电子邮件...... 设置 yum 库 显示日志 显示密码 大小： 跳过分析步骤，只执行报告步骤 如果您修改 /etc/system-release 文件请指定它。 状态：%s%s%s %s/show_bug.cgi?id=%u 标题 向 %s 提交 oops 报告 成功向 %s 发送 %s 回溯是不完整的，请确定您提供了重复该错误的完整步骤。 将该报告附加到 %s 将该报告保存到 %s 收集额外数据出现 %d 错误
Ticket/案例 ID URL 提取失败，中断下载...... 不支持的操作类型 可能有帮助的更新： 将 FILE 上传【到使用这个 ID 的案例】 作为 tar.gz 文件上传（使用 FTP/SCP/...） 上传的：%llu kb 中的 %llu 用法： 在您安装附加调试包后使用这个按钮来生成更多回溯信息 用户名 用户名 值 确认 SSL 查看/编辑文本文件 您要收集哪种额外信息？ 生成 bug 时也请附加二进制文件 您希望向哪里上传报告的 tarball 文件，格式为 login:password@url 使用 -r：不运行分析程序，只运行报告程序 检测到 %s 的错误设置，如果您继续使用当前配置，报告可能失败。 检测到 %s 的错误设置，如果您继续使用当前配置，报告可能失败。 您正在将文件复制到它本身 您可以在 <a href="https://bugzilla.redhat.com/createaccount.cgi">here</a> 创建 bugzilla.redhat.com 账户 您选择的数字超出了范围 执行前您需要填写如何进行...... 您的输入无效，因为： y