t @!A!uW!!-Q"J""!"S"SE#J#M#W2$$W>%e%\%SY&`&'Q(LT(( >)J)]);*S*d*~**/* *%*;+Y+Av+"+!++,5,L,+h,u,y --.-#.$Q.Dv..!..//J/&H01o00 00!0%1*A10l112&/2V2n22222*2"34B3w33)3$334.4K4-a4 444 45'(5=P5555%55)6)?63i666%667!78A7z7+7%7788#82\8828T8*9!<93^9+9C9y:r|:>:.;G;+c;%; ;;F;0<8G<5<<<<"<= 3= T=%b====F=< >G>#>D>9?/W? ?"?(?$?@&@ A@"b@@@/@@A0A&GAnA%A_AB)B5DB6zB*B BB!C#?CcC!{CCCC)CD1D!KDmDrDD/DDyEGEE8E0F6PF4F$F!FG-GLGbGrG;G5GHH</H lHzH)H$HH&I'IQRQTeQ`QR[,R'R(R?R0SJS5jS0S)SST2T.T4Uk7UUU"U"U$V"7VZV#rVVVVV W+W!JW#lWWWWW:W/XOXnXXX,XX%gYVY-Yi[[|[_[88]q]^3<^.p^.^q^q@_!_3_`B%`-h`+` ```a'aDaTafa~aaaF|cd'd8d3f=1i"oii"iii)ijjk!k"k2k&l/m/Bm,rm.mSm"n)n 0n:nc@n+nnanKo eoso%oo)oop"p15p&gp.q(qqsjs`NttPtu$"uLGuLuFuO(vVxvvjwew\XxDxlxgyYXz\z{ {{U[||||||&}#;} _}8}}?} ~!-~O~h~~~~%~]~f.w (&$OTtɀ ހɁN&01W$ւ3sRƃ&׃ )?^w1:Մ#!9![} υ13Sm(/͆31Gg...݇ ( Hi84 (Aj7.ى-ML5Ċ%? p`pыBB)ی N h8u; #$?d} Ў3-}K6ɏ@A*Z ؐ'3[y*֑/,H`M͒58/,h!Г!"#F[w$Ԕ 0,] D<9L.42#!Ac(yΗ'*=X9m))1[r2ܙh;>W$o=  <,i"Fe l7v ם-34h*-ǞM_r %ş>*B[w"Qʠ2WF`a"z&GĢ5 !B.d,xݣV)i*6i _l--&ۥ!):d' ަ #? c"q 65!*Lbu0IGbMRA/4d!, -9$gir'i' 9Ʈ*&+ R_z-կ  6Gc)t?,)H^w~F߹%,;h$;0`-/? /: I T]_6HPiz/ѽz+*Ѿ,ǿ#0W ^]bPQNb28hR3{:F'I-,q<-et#(ZX1vs) lSIGkp'C K>/dE%;q|?y!VzC[]GhJ6mBdOB#H9 a`; g%z@ =a~W 3\>}w ~nuFURup7^.[&O7S 9DmyKgAv2:!T@M_oeJr +wY$_t&s"fVD4}L0U `5(rHcEZ61j$T)xX5M{ixj\PYAknc<?fo+,*/*li.8Q |N="L4 Tainted modules: %s. With this option enabled ABRT always create bug ticket with restricted access if possibly sensitive data are dected. With this option enabled ABRT never shows notifications of reported problems. Takes effect only if Shortened reporting is enabled.%s and the diagnostic data has been submitted%sRun 'abrt-cli report %s' for creating a case in Red Hat Customer Portal & [ & [-v -i] -e|--event EVENT DIR...& [-v] -d DIR Calculates and saves UUID and DUPHASH for oops problem directory DIR& [-v] -d DIR Calculates and saves UUID and DUPHASH for xorg problem directory DIR& [-v] -d DIR Calculates and saves UUID and DUPHASH of python crash dumps& [-v] -d DIR Calculates and saves UUID of coredump in problem directory DIR& [-v] [-c CONFFILE] -d DIR Query package database and save package and component name& [-v] [-d SIZE:DIR]... [-f SIZE:DIR]... [-p DIR] [FILE]... Deletes problem dirs (-d) or files (-f) in DIRs until they are smaller than SIZE. FILEs are preserved (never deleted).& [-v] [-od] FILE... Scans files for split oops message. Can print and/or delete them.& [-v] [-r[RELEASE]] (-b ID1[,ID2,...] | PKG-NAME) [PKG-NAME]... Search for updates on bodhi server& [-v] [-r] -d DIR Creates coredump-level backtrace from core dump and corresponding binary& [-v] [DIR]... Applet which notifies user when new problems are detected by ABRT & [-vs] [-F STR]... FILE PROG [ARGS] Watch log file FILE, run PROG when it grows or is replaced& [-vs] [-w NUM] [-c MiB] [UPLOAD_DIRECTORY] Watches UPLOAD_DIRECTORY and unpacks incoming archives into DumpLocation specified in abrt.conf If UPLOAD_DIRECTORY is not provided, uses a value of WatchCrashdumpArchiveDir option from abrt.conf& [-vsoxm] [-d DIR]/[-D] [FILE] Extract Xorg crash from FILE (or standard input)& [-vusoxm] [-d DIR]/[-D] [FILE] Extract oops from FILE (or standard input)& [-y] [-i BUILD_IDS_FILE|-i -] [-e PATH[:PATH]...] [-r REPO] Installs debuginfo packages for all build-ids listed in BUILD_IDS_FILE to ABRT system cache.& [options]& [options] -d DIR Analyzes C/C++ backtrace, generates duplication hash, backtrace rating, and identifies crash function in problem directory DIR& [options] -d DIR Analyzes coredump in problem directory DIR, generates and saves backtrace& info [options] DIR...& list [options]& report [options] DIR...& status'%s' element can't be modified'%s' identifies more than one problem directory'%s' is not a valid element name'%s' is not a valid problem directory'%s' must be a regular file in order to use Retrace server.'{0}' processed successfully(debug) do not delete temporary archive created from dump dir in (debug) show received HTTP headers- means STDIN, default: build_idsA Known Problem has OccurredA New Problem has OccurredA Problem has OccurredA Problem has been ReportedA bug was already filed about this problem:A kernel problem occurred because of broken BIOS. Unfortunately, such problems are not fixable by kernel maintainers.A kernel problem occurred, but your hardware is unsupported, therefore kernel maintainers are unable to fix this problem.A kernel problem occurred, but your kernel has been tainted (flags:%s). Kernel maintainers are unable to diagnose tainted reports.A problem has been detectedA problem in the %s package has been detectedA server-side error occurred on '%s'ABRT has detected %u problem(s). For more info run: abrt-cli list%s ABRT notification appletABRT signal (abort() was called?)ABRT stores problem data in directories. Whenever ABRT needs writable directory, the directory is moved from the system location to your home directory. With this option disabled ABRT will move the problem directory without asking.AboutAbout System Config ABRTAccess past the end of mapped file, invalid address, unaligned access, etcActions: remove(rm), info(i), skip(s):Actions: remove(rm), report(e), info(i), skip(s):Add program names to logAdditional debuginfo directoriesAddress of the retrace serverAll debuginfo files are availableAn error occurred on the server side.An error occurred while connecting to '%s'An error occurred while connecting to the serverAn update exists which might fix your problem. You can install it by running: %s. Do you want to continue with reporting the bug?Analyze VM coreAnalyze and report problem data in DIRAnalyzing coredump '%s'Arithmetic exceptionAsk before stealing directoryAsk before uploading coredumpAutomatic Bug Reporting ToolAutomatically send uReportBacktrace is generated and saved, %u bytesBacktrace parsing failed for %sBad certificate received. Subject '%s', issuer '%s'.COREFILE is not specifiedCan't access the problemCan't access the problem for modificationCan't access the problem for readingCan't change directory to '{0}'Can't chown '%s': %sCan't close notification: %sCan't connect to '%s'Can't connect to NetworkManager over DBus: %sCan't connect to system DBus: %sCan't copy '{0}' to '{1}'Can't create '{0}' directoryCan't create temporary file '%s'Can't create temporary file in Can't create working directory in '{0}'Can't delete the element '%s' from the problem directory '%s'Can't determine network status via NetworkManager: %sCan't execute '%s'Can't extract the oops message: '{0}'Can't find problem '%s'Can't get problem data from abrt-dbus: %sCan't get problem list from abrt-dbus: %sCan't get signal no and do exploitability analysis Can't get size of '%s'Can't move '{0}' to '{1}'Can't open directory for writing '%s'Can't open {0}: {1}Can't process {0}: {1}Can't read from gio channel: '%s'Can't rename '%s' to '%s'. Failed to remove problem '%s'Can't resolve host name '%s'.Can't resolve host name '%s'. NSS error %d.Can't set encoding on gio channel: %sCan't show notification: %sCan't take ownership of '%s'Can't test whether the element exists over abrt-dbus: %sCan't turn on nonblocking mode for gio channel: %sCan't unpack '{0}'Can't update the problem: more than one oops foundCan't write to '%s'. Problem '%s' will not be removed from the ignored problems '%s'Cancelled by userCannot continue without password Certificate is signed by an untrusted issuer: '%s'.Certificate issuer is not recognized: '%s'.Certificate subject name '%s' does not match target host name '%s'.Checks if there are .vimrc and .gvimrc in your home directory and saves them as user_vimrc and user_gvimrc, respectively.Checks if there are vimrc and gvimrc files in /etc and saves them as system_vimrc and system_gvimrc, respectively.Chowning directory failed. Check system logs for more details.Collect .xsession-errorsCollect GConf configurationCollect system-wide vim configuration filesCollect yours vim configuration filesCommunicate directly to the userConfiguration fileCoredump references {0} debuginfo files, {1} of them are not installedCrash thread not foundCreate new problem directory in DIR for every oops foundCreate problem directory in DIR for every crash foundCurrent instruction: DaemizeDelay for polling operationsDelete files inside this directoryDelete files with found oopsesDelete whole problem directoriesDeleting '%s'Deleting problem directory failed: %sDivision by zeroDo not daemonizeDo not hash fingerprintsDo you want to enable automatically submitted anonymous crash reports?Do you want to enable automatically submitted crash reports?Do you want to generate a stack trace locally? (It may download a huge amount of data but reporting can't continue without stack trace).Don't run PROG if STRs aren't foundDownload debuginfo packages and generate backtrace locally using GDBDownload only specified filesEither problem directory or coredump is needed.Error: %sError: GDB did not return any dataExecuted after the reporting is finishedExit after NUM seconds of inactivityExiting on user commandExploitability analysis came up empty Exploitable rating (0-9 scale): Extracting the oops text from coreFailed to close SSL socket.Failed to compile regexFailed to complete SSL handshake: NSS error %d.Failed to enable SSL3.Failed to enable TLS.Failed to enable client handshake to SSL socket.Failed to get slot 'PEM Token #0': %d.Failed to initialize NSS.Failed to initialize security module.Failed to open connection to session manager: '%s', notification may reappear on the next loginFailed to read from a pipeFailed to reset handshake.Failed to send HTTP header of length %d: NSS error %dFailed to send HTTP header of length %d: NSS error %d.Failed to send data: NSS error %d (%s): %sFailed to set URL to SSL socket.Failed to set certificate hook.Failed to set handshake callback.Failed to set socket blocking mode.Failed to shutdown NSS.Failed to wrap TCP socket by SSL.File {0} doesn't existFor create and batch operationsFor next problem press ENTER:For status, backtrace, and log operationsGenerating backtraceGenerating core_backtraceHTTP Authenticated auto reportingHideIgnore foreverIgnored optionIllegal instruction (jump to a random address?)Incomplete problems are detected while computer is shutting down or user is logging out. In order to provide valuable problem reports, ABRT will not allow you to submit these problems.InsecureInstall kernel debuginfo packages, generate kernel log and oops messageInvalid number of argumentsInvalid response from server: missing HTTP message body.Invalid response from server: missing X-Task-Id.Invalid response from server: missing X-Task-Password.Invalid response from server: missing X-Task-Status.Issuer certificate is invalid: '%s'.Job control signal sent by kernelJump to an invalid addressKill gdb if it runs for more than NUM secondsLikely crash reason: List of bug idsList only not-reported problemsList only the problems more recent than specified timestampList only the problems older than specified timestampList problems [in DIRs]Local GNU DebuggerLocal version of the package is newer than available updatesLog to syslogLog to syslog even with -dMake the problem directory world readableMalformed HTTP response header: '%s'Malformed chunked response.Maximal cache size in MiB. Default is Missing build id: %sMissing debuginfo file: {0}Missing requested file: {0}Module '%s' was loaded - won't report this crashNeeds to downloads debuginfo packages, which might take significant time, and take up disk space. However, unlike RetraceServer, doesn't send coredump to remote machines.Needs to install kernel debuginfo packages, which might take significant time, and take up disk space.No free workers and full buffer. Omitting archive '%s'No problem space leftNo such problem directory '%s'No updates for this package foundNon-crash related signalNoninteractive, assume 'Yes' to all questionsNot AuthorizedNot a directory: '{0}'Not a number in file '%s'Notification area applet that notifies users about issues detected by ABRTNotify incomplete problemsNumber of concurrent workers. Default is Ok to upload core dump? (It may contain sensitive data). If your answer is 'No', a stack trace will be generated locally. (It may download a huge amount of data).Oops text extracted successfullyOpenPassword:Pattern to use when searching for repos, default: *debug*Post reportPreparing an archive to uploadPreserve this directoryPrint found crash data on standard outputPrint found oopsesPrint found oopses on standard outputPrint information about DIRPrint only the problem count without any messagePrint only the problems more recent than specified timestampPrint search string(s) to stdout and exitPrint the count of the recent crashesPrivate Reports is enabled, use 'abrt-cli -a COMMAND' to get the detected problems.Problem Reporting ConfigurationProblem detectedProblem directoryProcess multiple problemsQuerying server settingsQuitReceiving of data failed: NSS error %d.Red Hat Support password, if not given, a prompt for it will be issuedRed Hat Support user nameRemote certificate has expired.Remove PROBLEM_DIR after reportingRemove problem directory DIRReportReporting '%s'Request private ticket for sensitive informationRetrace failed. Try again later and if the problem persists report this issue please.Retrace job startedRetrace server URLRetrace server can not be used, because the crash is too large. Try local retracing.Retrace server is unable to process package '%s.%s'. Is it a part of official '%s' repositories?Run EVENT on DIRRuns gconftool-2 --recursive-list /apps/executable and saves it as 'gconf_subtree' element.SSL Client Authenticated auto reportingSYS signal (unknown syscall was called?)Same as -d DumpLocation, DumpLocation is specified in abrt.confSave .vimrc and .gvimrc from your home directorySave /etc/vimrc and /etc/gvimrcSave configuration from application's GConf directorySave relevant lines from ~/.xsession-errors fileSave the extracted information in PROBLEMScans through ~/.xsession-errors file and saves those lines which contain executable's name. The result is saved as 'xsession_errors' element.Searching for updatesSee 'abrt-cli COMMAND --help' for more informationSelects only problems detected after timestampSend core dump to remote retrace server for analysisSend core dump to remote retrace server for analysis or perform local analysis if the remote analysis failsShortened reportingShow detailed reportSignal due to write to broken pipeSignal due to write to closed pipeSignal has siginfo.si_code = SI_USERSignal sent by alarm(N) expirationSignal sent by keyboardSignal sent by timer/IO/async eventSignal sent by userspace codeSignal sent by window resizeSilent shortened reportingSkipping: '{0}' (contains ..)Skipping: '{0}' (contains space)Skipping: '{0}' (contains tab)Skipping: '{0}' (starts with dot)Skipping: '{0}' (starts with slash)Sleeping for %d secondsSpecify a bodhi server urlSpecify a releaseStack overflowSubroutine return to an invalid address (corrupted stack?)TRAP signal (can be a bug in a debugger/tracer)Task Id: %s Task Password: %s Task Status: %s %s Task id is needed.Task password is needed.Text larger than this will be shown abridgedThe Autoreporting feature is disabled. Please consider enabling it by issuing 'abrt-auto-reporting enabled' as a user with root privileges The Problem has already been ReportedThe archive contains malicious files (such as symlinks) and thus can not be processed.The coredump file is necessary for generating stack trace which is time and space consuming operation. ABRT provides a service which generates the stack trace from the coredump but you have to upload the coredump to this service. With this option disabled ABRT will upload the coredump without asking.The kernel log indicates that hardware errors were detected. This is most likely not a software problem. The name '%s' has been lost, please check if other service owning the name is not running. The problem data are incomplete. This usually happens when a problem is detected while computer is shutting down or user is logging out. In order to provide valuable problem reports, ABRT will not allow you to submit this problem. If you have time and want to help the developers in their effort to sort out this problem, please contact them directly.The release '%s' is not supported by the Retrace server.The report which will be sent does not contain any security sensitive data. Therefore it is not necessary to bother you next time and require any further action by you. The server denied your request.The server does not support xz-compressed tarballs.The server is fully occupied. Try again later.The server is not able to handle your request.The size of your archive is %lld bytes, but the retrace server only accepts archives smaller or equal %lld bytes.The size of your crash is %lld bytes, but the retrace server only accepts crashes smaller or equal to %lld bytes.This program must be run as root.Throttle problem directory creation to 1 per secondTurns the authentication offUnable to get current working directory as it was probably deletedUnable to start '%s', error message was: '%s'Unexpected HTTP response from server: %d %sUnknown errorUnknown file type: '{0}'Unknown operation: %s.Unknown option value: '%s' Unknown package sent to Retrace server.Unpacking '{0}'Upload successfulUploading %d megabytes Uploading %d%% Uploading %lld bytes Uploads coredump to a server, which generates backtrace and returns it. If user doens't want to upload his coredump to anywhere the event performs local analysis. Local analysis is run event if remote analysis fails. Pros: no need for debuginfo downloads. Retrace server's database of debuginfos is more complete. Retrace server may generate better backtraces. Cons: coredump you upload contains all the data from the crashed program, including your private data, if any.Uploads coredump to a server, which generates backtrace and returns it. Pros: no need for debuginfo downloads. Retrace server's database of debuginfos is more complete. Retrace server may generate better backtraces. Cons: coredump you upload contains all the data from the crashed program, including your private data, if any.Usage: %s [-v]Usage: %s [-v] [-o OUTFILE] -c COREFILEUsage: %s [-vd] ABRT_SPOOL_DIR UPLOAD_DIR FILENAME -v - Verbose -d - Delete uploaded archive ABRT_SPOOL_DIR - Directory where valid uploaded archives are unpacked to UPLOAD_DIR - Directory where uploaded archives are stored FILENAME - Uploaded archive file name Usage: %s [-vy] [--ids=BUILD_IDS_FILE] [--tmpdir=TMPDIR] [--cache=CACHEDIR[:DEBUGINFODIR1:DEBUGINFODIR2...]] [--size_mb=SIZE] [-e, --exact=PATH[:PATH]...] Installs debuginfos for all build-ids listed in BUILD_IDS_FILE to CACHEDIR, using TMPDIR as temporary staging area. Old files in CACHEDIR are deleted until it is smaller than SIZE. -v Be verbose -y Noninteractive, assume 'Yes' to all questions --ids Default: build_ids --tmpdir Default: @LARGE_DATA_TMP_DIR@/abrt-tmp-debuginfo-RANDOM_SUFFIX --cache Default: /var/cache/abrt-di --size_mb Default: 4096 -e,--exact Download only specified files --repo Pattern to use when searching for repos. Default: *debug* Usage: abrt-cli [--authenticate] [--version] COMMAND [DIR]...Usage: {0} [-v[v]] [--core=VMCORE]Use NUM as client uidUsed for updating of the databasesVerification error on '{0}'WarningWhether or not to use insecure connectionWith this option enabled reporting process started by click on Report button in problem notification bubble will be interrupted after uReport is sent. You can always use the default problem browser to make complete report.Write "insecure" to allow insecure connection <a href="https://fedorahosted.org/abrt/wiki/AbrtRetraceServerInsecureConnection" >(warning)</a>Write to an invalid addressXCPU signal (over CPU time limit)XFSZ signal (over file size limit)You also need to specify --username for --passwordYou are going to mute notifications of a particular problem. You will never see a notification bubble for this problem again, however, ABRT will be detecting it and you will be able to report it from ABRT GUI. Do you want to continue?You are going to upload %d megabytes. Continue?You can use either --anonymous or --certificateYou can use either --username or --anonymousYou can use either --username or --certificateYour problem directory is corrupted and can not be processed by the Retrace server._About_Close_Defaults_Quitabrt-retrace-client [options] Operations: create/status/backtrace/log/batch/exploitableallow insecure connection to retrace serveranonymous auto reportingdo not check whether retrace server is able to process given package before uploading the archiveid of your task on serverlog to syslogpassword of your task on serverread data from ABRT problem directoryread data from coredumpreporter-ureport failed with exit code %dretrace server URLretrace server porttranslator-creditsuReport SSL certificate paths or certificate typeuReport is short and completely anonymous description of a problem. ABRT uses uReports for fast global duplicate detection. In default configuration uReport is sent at beginning of reporting process. With this option enabled uReports are sent automatically immediately after problem detection.uReport was already sent, not sending it again{0} of debuginfo files are not installedProject-Id-Version: PACKAGE VERSION Report-Msgid-Bugs-To: jmoskovc@redhat.com POT-Creation-Date: 2017-05-15 16:10+0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit PO-Revision-Date: 2016-09-12 06:33-0400 Last-Translator: Alex Eng （新伦） Language-Team: Chinese (China) (http://www.transifex.com/projects/p/fedora-abrt/language/zh_CN/) Language: zh-CN Plural-Forms: nplurals=1; plural=0; X-Generator: Zanata 3.9.6 受污染的模块：%s。启用这个选项后，一旦检测到敏感数据，ABRT 将创建有优先访问权限的 bug ticket。启用该选项后 ABRT 不再提示汇报问题。仅在缩略报告启用的情况下生效。已提交 %s 和诊断数据%s 运行 'abrt-cli report %s' 在 Red Hat 客户门户网站中创建问题单 & [ & [-v -i] -e|--event EVENT DIR......& [-v] -d DIR 为 oops 问题目录 DIR 计算并保存 UUID 以及 DUPHASH& [-v] -d DIR 为 xorg 问题目录 DIR 计算并保存 UUID 以及 DUPHASH& [-v] -d DIR 计算并保存 python 崩溃转储的 UUID 和 DUPHASH& [-v] -d DIR 在有问题的目录 DIR 中计算并保存核心转储的 UUID& [-v] [-c CONFFILE] -d DIR 查询软件包数据库并保存软件包和组件名称& [-v] [-d SIZE:DIR]... [-f SIZE:DIR]... [-p DIR] [FILE]... 删除 DIR 中的问题 dirs（-d)）或 files（-f）直到其大小小于 SIZE。 保留 FILE（永远不要删除）。& [-v] [-od] 文件... 扫描多个文件寻找分割的出错信息。可以打印并/或删除它们。& [-v] [-r[RELEASE]] (-b ID1[,ID2,...] | PKG-NAME) [PKG-NAME]... 在 Bodhi 服务器上搜索更新& [-v] [-r] -d DIR 根据核心转储和对应二进制信息创建核心转储级回溯。& [-v] [DIR]... ABRT 探测到问题后，小程序会通知用户 & [-vs] [-F STR]... FILE PROG [ARGS] 监视日志文件 FILE，当它增长或被替换时运行程序 PROG& [-vs] [-w 工作者数] [-c MiB] [上传目录] 监视指定上传目录，将新加入的档案解压至 abrt.conf 中 指定的转储位置 如未指定上传目录，则使用 abrt.conf 中 指定的 WatchCrashdumpArchiveDir 选项& [-vsoxm] [-d DIR]/[-D] [FILE] 从文件 FILE (或标准输入)提取 Xorg 崩溃信息& [-vusoxm] [-d 目录]/[-D] [文件] 从指定文件(或标准输入)中提取出错信息& [-y] [-i BUILD_IDS_FILE|-i -] [-e PATH[:PATH]...] [-r REPO] 为 BUILD_IDS_FILE 中列出的所有 build-id 在 ABRT 系统缓存中 安装 debuginfo 软件包。& [options]& [options] -d DIR 在有问题的目录 DIR 中分析 C/C++ 回溯文件，生成副本哈希值，回溯评级， 以及识别崩溃函数的功能。& [options] -d DIR 分析问题目录 DIR 中的问题，生成并保存回溯文件& info [选项] DIR...& list [选项]& report [options] DIR...& status无法修改 '%s' 元素'%s' 标识出多于一个问题目录'%s' 不是一个有效的元素名'%s' 不是有效的问题目录'%s' 必须是常规文件才可使用追溯服务器。成功处理 '{0}'（调试）不删除转储目录创建的临时档案，位于(调试)显示收到的 HTTP 头- 即 STDIN，默认 ：build_ids发生一个已知问题发生一个新问题发生一个错误一个问题已被提交已存在有关这个问题的 bug：由于 BIOS 出错出现内核问题。遗憾的是内核维护者尚未解决这个问题。出现内核问题，但由于不支持您的硬件，因此内核维护者无法修复这个问题。发生了内核问题，但您的内核已被污染（标志：%s）。内核维护器无法诊断被污染的报告。已检测到一个问题检测到 %s 软件包中的一个问题服务器发生有关 '%s' 的错误ABRT 已检测到 '%u' 个问题。预了解详细信息请执行：abrt-cli list%s ABRT 通知小程序ABRT信号 (abort() 被调用? )ABRT 将问题数据保存在目录中。当 ABRT 需要可写入目录时，该目录从系统位置移动到您的主目录。当禁用此选项后 ABRT 移动问题目录时将不再询问。关于关于系统配置 ABRT访问超过映射文件结尾，无效的地址，未对齐的访问或其他动作：remove(rm), info(i), skip(s):动作：remove(rm), report(e), info(i), skip(s):在日志中添加程序名附加的 debuginfo 目录追溯服务器地址所有调试信息文件均可用。服务器发生错误。连接至 '%s' 时发生错误连接服务器时发生错误软件包已有一个可能解决问题的更新，您可以通过执行 %s 来安装。是否继续报告问题？分析 VM 核心分析并报告 DIR 中的问题数据正在分析核心转储 '%s'运算异常占用目录前询问在上传核心转储前询问错误自动报告工具自动发送 uReport回溯已经生成并保存，大小为 %u 字节 %s 回溯解析失败接收到坏证书。主题“%s”，发行者“%s”。未指定 COREFILE无法访问该问题无法访问该问题进行修改无法访问该问题进行读取无法该为目录 '{0}'无法变更 '%s' 的属主：%s无法关闭通知：%s无法连接至 '%s'无法通过 DBus 连接到至 NetworkManger：%s无法连接系统 DBus：%s无法从 '{0}' 迁复制 '{1}'无法创建 '{0}' 目录无法创建临时文件 '%s'无法创建临时文件无法在 '{0}' 在这创建工作目录无法从问题目录 '%s' 中删除元素 '%s'无法通过 NetworkManager 确定网络状态：%s无法执行 ”%s“无法提取异常信息: '{0}'无法找到问题 '%s'无法从 abrt-dbus 中获取问题数据：%s无法从 abrt-dbus 中获取问题列表：%s无法获得信号编号并执行安全分析 无法获取 '%s' 的大小无法从 '{0}' 迁移到 '{1}'无法打开目录以写入 '%s'无法打开 {0}：{1}无法执行 {0}: {1}无法读取 gio 频道：'%s'无法重命名 '%s' 为 '%s'。移除问题 '%s' 失败无法解析主机名 '%s'。无法解析主机名 '%s'。发生 NSS 错误 %d。无法在 gio 频道中设定编码：%s无法显示通知：%s无法获取 '%s' 的所有权无法通过 abrt-dbus 测试该元素是否存在：%s无法为 gio 频道设定非阻断模式：%s无法解压缩 '{0}'无法更新问题：发现超过一个异常无法写入 '%s'。问题 '%s' 将不会从已忽略问题 '%s' 中被移除用户已取消需要密码才可继续 证书由不受信任的发行者签名：“%s”。无法识别证书发行者：'%s'。证书标题名称 '%s' 与目标主机名称 '%s' 不匹配。检查在您的主目录中是否有 .vimrc 和 .gvimrc，并将其分别保存为 user_vimrc 和 user_gvimrc。检查在 /etc 中是否有 vimrd 和 gvimrc 文件，并将其分别保存为 system_vimrc 和 system_gvimrc。变更目录属主失败。请检查系统日志以了解更多。收集 .xsession-errors收集 GConf 配置在系统范围内收集 vim 配置文件收集您的 vim 配置文件直接联系用户配置文件核心转储需要 {0} 个 debuginfo 软件包，其中有 {1} 个尚未安装崩溃线程在 DIR 中为每个发现的 oops 生成新问题目录在 DIR 中为每个发现的崩溃生成新的问题目录当前指令：在后台运行因轮询操作而推迟删除该目录中的文件删除已找到的内核错误文件删除全部问题目录正在删除 '%s'删除问题目录失败：%s被零整除不要在后台运行不计算指纹散列值您想要启用自动提交匿名崩溃报告吗？您想要启用自动提交崩溃报告吗？您想在本地生成一个栈跟踪吗？(这可能会下载大量数据，但没有栈跟踪就无法继续报告问题)。如果未找到字符串 STR，则不运行程序 PROG下载 debuginfo 软件包并用 GDB 在本地生成回溯数据只下载指定的文件需要问题目录或核心转储之一。错误： %s错误： GDB 为返回完成报告后执行闲置 NUM 秒后退出由于用户命令正在退出安全分析返回结果为空 可使用的等级 (0-9级)正在从核心提取异常文字信息关闭 SSL 套接字失败。编译正则表达式失败无法完成 SSL 握手：NSS 错误 %d。启用 SSL3 失败。启用 TLS 失败。启用客户端与 SSL 插槽的握手失败。获取“PEM Token #0”插槽失败：%d。初始化 NSS 失败。初始化安全模块失败。打开会话管理器 :'%s', 失败，通知会在下次登录时重新出现从管道读取失败重置握手失败。发送长度为 %d 的 HTTP 头失败：NSS 错误 %d无法发送长度为 %d 的 HTTP 头：NSS 错误 %d。发送数据失败：NSS 错误 %d (%s)：%s设置 SSL Socket 网址失败。设置证书钩失败。设置握手回调失败。设置插槽阻塞模式失败。关闭 NSS 失败。以 SSL 包装 TCP 插槽失败。文件 {0} 不存在用于创建和批量操作下一个问题请按 ENTER：用于状态、回溯和日志操作正在生成回溯文件正在生成核心转储HTTP 认证的自动报告隐藏永远忽略忽略的选项非法指令（转跳至一个随机地址？）不完整的问题通常在电脑关机或用户登出时发生。为提供有价值的问题报告，ABRT 将不允许您提交此类问题。不安全安装内核 debuginfo 软件包，生成内核日志和 oops 信息无效参数值来自服务器的无效响应：缺少 HTTP 消息体。无效的服务器响应：缺少 X-Task-Id。无效的服务器响应：缺少 X-Task-Password。无效的服务器响应：缺少 X-Task-Status。发行者证书无效：“%s”。内核发出的作业控制信号跳转至无效地址如果 gdb 运行超过 NUM 秒就终止可能的崩溃原因:Bug 错误 ID 列表只列出未报告的问题仅列出比指定时间更晚的问题仅列出比指定时间戳更早的问题列出 [in DIRs] 的问题本地 GNU 调试器该软件包的本地版本比可用更新的版本要高记录至 syslog即使加入 -d 选项也记录至 syslog使问题目录可读异常的 HTTP 响应头：'%s'异常的分块响应。以 MiB 计最大缓存尺寸。默认为缺少构建 id：'%s'缺少 debuginfo 文件：{0}缺少所需文件：{0}已载入模块 '%s' - 将不会报告这个崩溃需要下载 debuginfo 软件包，这可能需要花较长时间并占用很多磁盘空间。然而和追溯服务器不同的是，它不需要发送核心转储至远程服务器上。需要安装内核 debuginfo 软件包，安装该软件包需要很长时间，并占用磁盘空间。没有空闲的工作者和完整缓存。忽略档案 '%s'没有留出问题空间没有问题目录 '%s'未找到该软件包的可用更新非崩溃相关信号非互动性，假设所有问题的答案都是 ‘Yes’。未授权不是一个目录：'{0}'不是文件 '%s' 中的数字用来将 ABRT 检测到的问题通知给用户的小程序通知不完整的问题并行工作者数量。 默认为可以上传核心转储了吗(可能包含敏感数据)？如果您的回答为“否”，则会在本地生成一个栈跟踪(可能会下载大量数据)。成功提取异常文字信息打开密码：搜索存储库时使用的模式，默认为：*debug*提交报告正在准备上传的归档保留该目录在标准输出上输出找到的崩溃数据打印已找到的内核错误打印在标准输出中找到的严重错误(Oops)输出有关 DIR 的信息仅显示问题计数。仅显示比指定时间更晚的问题。输出搜索字符串至标准输出并退出显示最近的崩溃计数启用专用报告，使用 'abrt-cli -a COMMAND' 获取探测到的问题。配置错误报告检测到问题问题目录处理多个问题正在查询服务器设置退出接收数据失败：NSS 错误 %d。Red Hat 支持密码，如果不输入密码则会有提示。Red Hat 支持用户名远程证书已过期。报告后删除 PROBLEM_DIR删除问题目录 DIR报告正在报告 '%s'为敏感信息请求专用 ticket追溯失败，请稍后再试。如果问题仍然存在，请上报该问题。追溯任务已开始追溯服务器 URL由于崩溃数据过大，导致追溯服务器无法使用。请使用本地追溯。回溯服务器无法处理软件包 '%s.%s'。 是否确定它来自于官方软件源 '%s' ？在 DIR 中运行 EVENT 运行 gconftool-2 --recursive-list /apps/executable 并将其保存为 'gconf_subtree' 元素。SSL 客户端认证的自动报告SYS 信号 (调用了未知 syscall ?)与 -d DumpLocation 相同，是在 abrt.conf 中指定 DumpLocation。保存您主目录中的 .vimrc 和 .gvimrc 文件。保存 /etc/vimrc 和 /etc/gvimrc保存应用程序的 GConf 目录中的配置从 ~/.xsession-errors 文件保存有关行保存提取信息到PROBLEM扫描 ~/.xsession-errors 文件并保存包含可执行文件名称的行。结果已存为 'xsession_errors' 元素。正在搜索更新详情请查看 'abrt-cli COMMAND --help'只选择时间戳之后探测到的问题发送核心转储至远程追溯服务器以供分析向远程回溯服务器发送核心转储供于分析，或在远程分析失败时执行本地分析。缩略报告显示详细报告由写入被中断的管道而产生的信号由写入已关闭的管道而产生的信号信号具备 siginfo.si_code = SI_USER警报(N)到时发出的信号由键盘发送的信号信号由时钟、IO、异步事件发送信号由用户区代码发送由调整窗口大小而产生的信号静默式缩略报告跳过：'{0}'（包含..）跳过：'{0}'（包含空格）跳过：'{0}'（包含 tab）跳过：'{0}'（以点开始）跳过：'{0}'（以斜杠开始）休眠 %d 秒指定一个 Bodhi 服务器地址指定一个发行版本号堆栈溢出子路线返回一个无效的地址（栈损坏？）TRAP 信号(可以是调试器/追溯器中的错误)任务 ID：%s 任务密码：%s 任务状态：%s %s 需要任务 ID。需要任务密码。超出此大小的文字会在显示时被删节已禁用自动报告功能。请考虑启用该功能，方法是 作为有 root 特权的用户使用命令 'abrt-auto-reporting enabled' 该问题已经被提交该档案包含可疑文件(例如符号链接)，因此无法处理。核心转储文件是生成费时费空间栈回溯的必要操作。ABRT 提供从核心转储生成栈回溯的服务，但您必须将核心转储上传到到该服务。当禁用此选项后 ABRT 将自动上传核心转储而不再询问。内核日志提示探测到硬件错误。 这很可能不是软件问题。 名称 '%s' 已丢失，请检查其它拥有该名称的服务是否未运行。 问题数据不完整。这些通常是正在关机或注销时发生的问题。为了提供有效的问题报告，ABRT 将不允许您提交该问题。如果您有时间想帮助开发者找出问题的根源，请直接与他们联系。追溯服务器不支持该发行版本 '%s'。将要发送的报告中不包含任何安全敏感数据。因此不需要再次打扰您，或者需要您有进一步的动作。 服务器拒绝了您的请求。服务器不支持 tar.xz 格式的档案。服务器目前已满载。请稍后再试。服务器无法处理您的请求。您的归档大小为 %lld 字节，但是追溯服务器只接收小于或等于 %lld 字节的档案。您的崩溃数据大小是 %lld 字节，但追溯服务器只接受小于或等于 %lld 字节的崩溃数据。此程序必须以 root 权限运行。每 1 秒创建一个控流问题目录关闭认证无法获取当前工作目录因为可能已将其删除无法启动 '%s'，出错信息为：'%s'非预期服务器 HTTP 响应：%d %s未知错误未知文件类型：'{0}'未知操作：%s。未知选项值：'%s' 已向追溯服务器发送未知软件包。正在解压缩 '{0}'上传成功正在上传 %d MB 已上传 %d%% 正在上传 %lld 字节 向服务器上传核心转储，这样会生成并返回回溯。如果用户不想向任何服务器上传核心转储，则会执行本地分析。即使远程分析失败也可运行本地分析。这样的话，优点就是不需要下载 debuginfo 软件包，因为追溯服务器的 debuginfo 数据库更全面。追溯服务器可能生成更好的回溯。缺点就是您上传的核心转储可能会包含崩溃程序的所有数据，即便隐私数据也无法幸免。上传核心转储至服务器，由服务器生成回溯数据并返回。优点：无需下载 debuginfo；追溯服务器的 debuginfo 数据库更加完整；追溯服务器可以生成更好的回溯。缺点：您上传的核心转储包含崩溃程序的所有数据，如果有私人数据，也将会包含在其中。用法：%s [-v]用法：%s [-v] [-o OUTFILE] -c COREFILE用法：%s [-vd] ABRT_SPOOL_DIR UPLOAD_DIR FILENAME -v - Verbose -d - Delete uploaded archive ABRT_SPOOL_DIR - 将有效上传归档解压缩到该目录 UPLOAD_DIR - 保存已上传归档的目录 FILENAME - 已上传归档文件吗 用法：%s [-vy] [--ids=BUILD_IDS_FILE] [--tmpdir=TMPDIR] [--cache=CACHEDIR[:DEBUGINFODIR1:DEBUGINFODIR2...]] [--size_mb=SIZE] [-e, --exact=PATH[:PATH]...] Installs debuginfos for all build-ids listed in BUILD_IDS_FILE to CACHEDIR, using TMPDIR as temporary staging area. Old files in CACHEDIR are deleted until it is smaller than SIZE. -v Be verbose -y Noninteractive, assume 'Yes' to all questions --ids Default: build_ids --tmpdir Default: @LARGE_DATA_TMP_DIR@/abrt-tmp-debuginfo-RANDOM_SUFFIX --cache Default: /var/cache/abrt-di --size_mb Default: 4096 -e,--exact Download only specified files --repo Pattern to use when searching for repos. Default: *debug* 用法：abrt-cli [--authenticate] [--version] COMMAND [DIR]...用法: {0} [-v[v]] [--core=虚拟核心数]使用 NUM 作为客户端 UID用于更新数据库'{0}' 中的验证错误警告是否使用不安全连接启用该选项后，将会在 uReport 发送后中断由问题气泡通知中报告按钮开始的报告进程。您依然可以使用默认问题浏览器完成报告。在所有不安全连接中写入 "insecure" <a href="https://fedorahosted.org/abrt/wiki/AbrtRetraceServerInsecureConnection" >(warning)</a>向无效地址写入XCPU信号 (超出CPU的时限)XFSZ信号 (超出文件大小限制)您还需要为 --password 指定 --username您要将某个具体问题的通知静音。您将再也无法看到这个问题的通知气泡，但 ABRT 将继续对其进行探测，同时您也可以使用 ABRT GUI 报告该问题。 您要继续吗？即将上传 %d MB，是否继续？您可以使用 --anonymous 或者 --certificate您可以使用 --username 或者 --anonymous您可以使用 --username 或者 --certificate您的问题目录已损坏，无法由追溯服务器处理。关于(_A)关闭（_C）默认(_D)退出(_Q)abrt-retrace-client <操作> [选项] 操作： create/status/backtrace/log/batch/exploitable允许与追溯服务器通过不安全的连接通信匿名自动报告在上传档案前不检查服务器是否有能力处理指定软件包服务器上的任务 ID记录至 syslog服务器上的任务密码从 ABRT 目录中读取数据从核心转储读取数据reporter-ureport 失败并给出退出代码 %d追溯服务器 URL追溯服务器端口Fedora Simplified Chinese Translation Group Tommy He uReport SSL 证书路径或者证书类型uReport 是问题的简要且完全匿名的描述。ABRT 使用 uReport 进行快速的全局重复检查。在默认配置下 uReport 在报告过程的一开始发送。当启用该选项后 uReports 将在发现问题后立即自动发送。已发送 uReport，请不要再次发送。未安装 {0} 的 debuginfo 文件