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(qqsgsfCttOtu!uI=uIuGuLvYfvv_{wtw`PxNxiyjyTrzHz{ {{Z>||||||,|#+}#O}>s}}Q}$~)?~i~|~~~'~b~v72%E&kX"&NEeX#;#Tx#$݃m&~ Ƅӄ$*1?q@˅ޅ )Hc{/Æ$$B'[53$'+?+k:҈$#9P%hE#ԉ3(,U m1.,N28,@mUiÌE-s؍ HD;`;؎ *Ibw 9Ώ3<(F0*I t" ݑ9Up*Ò3ג+ 7Nhm֓588,q#”ݔ#%1Wl!ĕݕ ($8] D'l<4:8,&e!(Ę363j9ҙ )'G,o!/5:ph/;Ԝ  *9@ z N "&I = Z!g0͟' *%3P,!VӠ*= P]p%C < [|'T+ZAe]%u+AǤ+ !5+W4$ݥa6w$3Ӧf n{$$#ۧ%4$Z' ب#  >_p 05٩-=Sl!4CMWT+],!:*\3$u{V'Ұ0+?>1~) ڱ-7e {β~8)I5sE$8QmtN& ,Gt1K-}*,־? C N Y g_r0ҿZ!q$!/7Mf'##20W ^]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: 2015-07-17 07:14-0400 Last-Translator: Terry Chuang Language-Team: Chinese (Taiwan) (http://www.transifex.com/projects/p/fedora-abrt/language/zh_TW/) Language: zh-TW Plural-Forms: nplurals=1; plural=0; X-Generator: Zanata 3.9.6 損壞的模組：%s。 若啟用此選項，當 ABRT 偵測到敏感資訊時總會以限制存取方式建立臭蟲回報。 啟用此選項後，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]... 刪除於 DIRs 目錄中的問題目錄 (-d) 或檔案 (-f)，直到它們小於 SIZE。 FILEs 會被保留 (永不刪除)。& [-v] [-od] FILE... 為分割的 oops 訊息掃描檔案。可以列印與/或刪除它們。& [-v] [-r[RELEASE]] (-b ID1[,ID2,...] | PKG-NAME) [PKG-NAME]... 在 bodhi 伺服器上搜尋是否有可用更新& [-v] [-r] -d DIR 從核心傾印與相對應的二進位檔建立 coredump-level 追蹤資料& [-v] [DIR]... 新問題被 ABRT 偵測到時通知使用者的面板程式 & [-vs] [-F STR]... FILE PROG [ARGS] 監看記錄檔 FILE，當該檔案變大或被取代時執行 PROG& [-vs] [-w NUM] [-c MiB] [UPLOAD_DIRECTORY] 監視 UPLOAD_DIRECTORY，並將傳入的封存檔解開放入 abrt.conf 中指定的 DumpLocation 如果沒有提供 UPLOAD_DIRECTORY 位置，則使用 abrt.conf 中 WatchCrashdumpArchiveDir 選項的其中一值& [-vsoxm] [-d DIR]/[-D] [FILE] 從 FILE (或標準輸出) 抽出 Xorg 當機資訊& [-vusoxm] [-d DIR]/[-D] [FILE] 從 FILE (或標準輸入) 抽出 oops& [-y] [-i BUILD_IDS_FILE|-i -] [-e PATH[:PATH]...] [-r REPO] 為列在 BUILD_IDS_FILE 中的所有 build-id 安裝 debuginfo 套件至 ABRT 系統快取。& [選項]& [選項] -d DIR 在問題目錄 DIR 內分析 C/C++ 追蹤資訊、產生複本雜湊、 追蹤資料評等、辨識當機函式& [選項] -d DIR 分析問題目錄 DIR 內的核心傾印，產生並儲存追蹤資訊& info [選項] DIR...& list [options]& report [選項] DIR...& status無法修改「%s」元素「%s」辨識出一個以上的問題目錄「%s」不是有效的元素名稱「%s」不是有效的問題目錄若要使用回追伺服器，「%s」必須是一般檔案。「{0}」處理成功(除錯) 不要從此目錄內的傾印目錄刪除已建立的暫存封存檔：(除錯) 顯示接收的 HTTP 標頭- 代表 STDIN，預設值為：build_ids遭遇已知問題遭遇新問題遭遇到問題已回報問題已有此問題相關的臭蟲回報：Kernel 發生問題因為 BIOS 損壞。很不幸的，kernel 維護人員無法修正此問題。發生了一項 kernel 問題，不過您的硬體不受到支援，因此 kernel 維護人員無法修正此問題。遭遇一項內核問題，但您的內核已經損壞 (旗標：%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 目錄回追伺服器的位址所有的 debuginfo 檔案皆可用伺服器端遭遇錯誤。當連接至「%s」時遭遇錯誤當連接至伺服器時遭遇錯誤目前有個更新可用，或許它能修正您的問題。您可以藉由執行此動作來安裝它：%s。您想要繼續回報臭蟲嗎？分析 VM 核心在 DIR 內分析並回報問題資料正在分析核心傾印「%s」數學例外在佔用目錄前詢問在上傳核心傾印前詢問意願自動臭蟲回報工具自動傳送 uReport追蹤資訊已產生並儲存，計 %u 位元組%s 的追蹤解析失敗接收到不良憑證。主體「%s」，發行單位「%s」。未指定 COREFILE無法存取問題無法存取問題以修改無法存取問題以閱讀無法切換目錄至「{0}」無法 chown 「%s」：%s無法關閉通知：%s無法連接至「%s」無法透過 DBus 連接至 NetworkManager：%s無法連接至系統 DBus：%s無法將「{0}」複製至「{1}」無法建立「{0}」目錄無法建立暫存檔「%s」無法建立暫存檔於無法在「{0}」中建立工作目錄無法從問題目錄「%2$s」刪除「%1$s」元素無法透過 NetworkManager 判定網路狀態：%s無法執行「%s」無法抽出 oops 訊息：「{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}」無法更新問題：找到超過一份 oops無法寫入「%s」。問題「%s」不會從忽略的問題「%s」中移除使用者已取消沒有密碼無法繼續 憑證由未受信任的發行單位簽署：「%s」。憑證發行單位無法辨識：「%s」。憑證主體名稱「%s」不符合目標主機名稱「%s」。檢查您的家目錄是否有 .vimrc 與 .gvimrc，並將它們個別儲存為 user_vimrc 與 user_gvimrc。檢查 /etc 內是否有 vimrc 與 gvimrc，並將它們個別儲存為 system_vimrc 與 system_gvimrc。目錄擁有者變更失敗。請檢查紀錄檔瞭解更多細節。收集 .xsession-errors收集 GConf 組態收集系統域 vim 組態檔收集您的 vim 組態檔直接與使用者溝通組態檔核心傾印參照 {0} 份 debuginfo 檔，其中的 {1} 份尚未安裝沒有找到崩潰執行序在 DIR 內為每個找到的 oops 建立新的問題目錄在 DIR 內為每個找到的當機資料建立問題目錄目前指令：幕後處理為投票操作而延遲刪除此目錄內的檔案刪除找到的 oops 其檔案刪除整個問題目錄正在刪除「%s」刪除問題目錄失敗：%s除以零不要在幕後運行不要製作雜湊指紋您是否希望啟用自動提交的匿名當機回報？您是否希望啟用自動提交的當機回報？您想要在本機上生成堆疊追蹤嗎？(這可能需要下載巨量資料，不過報告若無堆疊追蹤便無法繼續。)若找不到 STR 時則不要執行 PROG下載 debuginfo 軟體包並透過本地端的 GDB 產生追蹤資訊僅下載指定的檔案需要問題目錄或者是核心傾印。錯誤：%s錯誤：GDB 未傳回任何資料在回報完成後執行在停止使用 NUM 秒後離開正在離開使用者指令可利用性分析結果為空 可利用等級 (0-9 規模)：從核心抽出 oops 內文無法關閉 SSL socket。無法編譯 regex無法完成 SSL 握手：NSS 錯誤 %d。無法啟用 SSL3。無法啟用 TLS。無法啟用對於 SSL socket 的客戶端握手。無法取得 slot「PEM Token #0」：%d。無法初始化 NSS。無法初始化安全模組。無法開啟與作業階段管理員的連線：「%s」，通知可能會在下次登入時再次出現無法從 pipe 讀取無法重設握手。無法傳送長度 %d 的 HTTP 標頭：NSS 錯誤 %d無法傳送長度 %d 的 HTTP 標頭：NSS 錯誤 %d。無法傳送資料：NSS 錯誤 %d (%s)：%s無法設定網址為 SSL socket。無法設定憑證 hook。無法設定握手回呼。無法設定 socket 阻擋模式。無法關閉 NSS。無法透過 SSL 包裝 TCP socket。檔案 {0} 不存在建立與批次操作下個問題請按 ENTER 鍵。狀態、追蹤、紀錄等操作正在產生追蹤資訊正在 core_backtrace...HTTP 身份認證自動回報隱藏永遠忽略忽略的選項無效指示 (跳入隨機位址？)資料不完整的問題通常在電腦關機動作之時，或是使用者正在登出時被偵測到。為了提供有價值的問題回報，ABRT 不會允許您提交此類問題報告。不安全安裝內核 debuginfo 軟體包，產生內核紀錄與 oops 訊息引數數量無效來自伺服器的回應無效：遺失 HTTP 訊息本文。來自伺服器的回應無效：遺失 X-Task-Id。來自伺服器的回應無效：遺失 X-Task-Password。來自伺服器的無效回應：遺失 X-Task-Status。發行單位憑證無效：「%s」。內核傳送的工作控制訊號跳入無效的位址若 gdb 執行超過 NUM 秒就終止它可能的崩潰原因：臭蟲 ID 清單僅列出尚未回報的問題僅列出比指定的時間戳記更近期的問題僅列出比指定的時間戳記更之前的問題列出 [DIRs 中] 的問題本地端 GNU 除錯器本地端的軟體包版本比可用更新的版本還新紀錄至 syslog即使加上 -d 參數也紀錄至 syslog讓問題目錄全世界都可以讀取格式不良的 HTTP 回應標頭：「%s」格式不良的 chunked 回應。最大快取大小，單位為 MiB。預設為 遺失組建 id：%s遺失 debuginfo 檔：{0}請求的檔案遺失：{0}已載入「%s」模組 - 不會回報此當機資訊需要下載 debuginfo 軟體包，並且可能會花上一段時間以及消耗一些磁碟空間。然而，這不像 RetraceServer，所以不會傳送核心傾印資料至遠端機器。需要安裝內核 debuginfo 軟體包，並且可能會花上一段長時間以及消耗磁碟空間。無工作器可用，緩衝也塞滿。略過「%s」封存無剩餘問題空間沒有這個問題目錄「%s」找不到此軟體包的更新無崩潰相關訊號非互動式，假設所有問題的答案皆為「是」未授權不是目錄：「{0}」不是「%s」檔案中的數字會通知使用者有關於 ABRT 所發現的問題的通知區域面板程式通知不完整的問題同時工作序數量。預設為 確定要上傳核心傾印？(它可能包含敏感資料)。若您的答案為「否」，將會在本地建立堆疊追蹤。(這可能需要下載大量資料)。Oops 內文已成功抽出開啟密碼：搜尋軟體庫時所使用的格式，預設值為：*debug*張貼回報正在準備要上傳的封存檔保留這個目錄將找到的崩潰資料列印在標準輸出上列印找到的 oops列印找到的 oops 於標準輸出上列印有關 DIR 的資訊僅列印問題數目而不帶任何訊息僅列印比指定的時間戳記更近期的問題將搜尋字串列印在 stdout 上並離開列印最近程式崩潰的數目已啟用私密報告，請使用 'abrt-cli -a COMMAND' 以取得偵測到的問題。問題回報組態偵測到的問題問題目錄處理多項問題正在查詢伺服器設定值退出資料接收失敗：NSS 錯誤 %d。Red Hat Support 密碼；如果未提供密碼，將會發出提示Red Hat Support 使用者名稱遠端憑證已經過期。在回報後移除 PROBLEM_DIR從問題目錄 DIR 移除檔案回報正在回報「%s」內含敏感訊息故申請隱私請票回追失敗。請稍候重試，若這個問題持續發生，請回報此議題。回追工作已開始回追伺服器網址回追伺服器無法使用，因為當掉資訊過大。請嘗試本地端回追處理。回追伺服器無法處理軟體包「%s.%s」。 該軟體包是否來自官方「%s」軟體庫？於 DIR 執行 EVENT執行 gconftool-2 --recursive-list /apps/executable 並儲存為「gconf_subtree」元素。SSL 用戶端身份憑證自動回報SYS 訊號 (未知的 syscall 被呼叫？)與 -d DumpLocation 相同，DumpLocation 於 abrt.conf 內指定從您的家目錄儲存 .vimrc 與 .gvimrc儲存 /etc/vimrc 與 /etc/gvimrc從應用程式的 GConf 目錄儲存組態從 ~/.xsession-error 檔案儲存相關的紀錄列將抽出的資訊存入 PROBLEM 中掃描 ~/.xsession-errors 檔案並儲存那些包含執行檔名稱的紀錄列。結果會以「xsession_errors」元素儲存。搜尋是否有更新請見 'abrt-cli COMMAND --help' 以瞭解更多資訊僅選取時間戳記之後的問題傳送核心傾印至遠端回追伺服器來分析傳送核心傾印至遠端回追伺服器來分析，若遠端分析失敗或可執行本地端分析簡短回報顯示詳細的回報訊號截止以寫入損壞的導管訊號截止以寫入關閉的導管訊號有 siginfo.si_code = SI_USERalarm(N) 過期傳送的訊號訊號由鍵盤傳送訊號由 timer/IO/async 事件傳送訊號由使用者空間代碼傳送視窗重新調整大小傳送的訊號靜默簡短回報略過：「{0}」(含有 ..)略過：「{0}」(含有空白)略過：「{0}」(含有跳格符)略過：「{0}」(以 . 起頭)略過：「{0}」(以 / 起頭)正睡眠 %d 秒指定 bodhi 伺服器 URL指定發行版堆疊溢位副常式回傳無效的位址 (堆疊損毀？)TRAP 訊號 (可能是除錯器或追蹤器的臭蟲)工作事項 Id：%s 工作事項密碼：%s 作業狀態：%s %s 需要工作事項 id。需要工作事項密碼。大於此的文字會刪減顯示Autoreporting 功能已停用。請考慮以擁有 root 權限的使用者 身份，透過「abrt-auto-reporting enabled」 來啟用它 此問題已被回報過封存檔包含惡意檔案 (像是 symlinks) 因此無法處理。需要有核心傾印檔案才能生成堆疊追蹤資訊，而這個動作既費時又費空間。ABRT 提供以核心傾印生成堆疊追蹤資訊的服務，但您必須將核心傾印檔上傳到此服務中。停用此選項後，ABRT 不須詢問就會上傳核心傾印檔案。Kernel 日誌顯示已偵測到硬體錯誤。 這很可能不是軟體上的錯誤。 「%s」名稱已遺失，請確認其他擁有該名稱的服務並未執行中。 問題資料並不完整。這通常發生在電腦關機動作之時，或是使用者正在登出之時偵測到問題。為了提供有價值的問題回報，ABRT 不會允許您提交此種問題報告。若您有時間，且也想幫助開發者來處理此問題，請直接聯繫開發者。回追伺服器不支援「%s」發行版。將傳送的回報未包含任何安全性敏感資料。因此下次不需要再打擾您，也不會要求您進一步動作。 伺服器已拒絕您的請求。伺服器不支援 xz 壓縮版 tarball。伺服器目前完全被佔線。請稍候重試。伺服器無法處理您的請求。您的封存檔大小為 %lld 位元組，但是回追伺服器僅接受小於或等於 %lld 位元組的封存檔。您的當掉資訊大小為 %lld 位元組，但是回追伺服器僅接受小於或等於 %lld 位元組的當掉資訊。此程式必須以 root 身份執行。節制問題目錄的建立速度為每秒 1 個關閉身份認證無法取得目前的工作目錄，因為它可能已被刪除無法啟動「%s」，錯誤訊息為：「%s」來自伺服器的未預期回應：%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 - 詳盡 -d - 刪除上傳的封存檔 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=VMCORE]使用 NUM 作為客戶端 UID用於資料庫的更新驗證「{0}」上的錯誤警告是否使用不安全的連線啟用此選向後，在問題通知氣泡中點按「回報」按鈕而展開的回報程序會在 uReport 送出後中斷。您仍可以用預設的問題瀏覽器回報完整報告。寫入「insecure」來允許不安全的連線 <a href="https://fedorahosted.org/abrt/wiki/AbrtRetraceServerInsecureConnection" >(warning)</a>寫入無效的位址XCPU 訊號 (超過 CPU 時限)XFSZ 訊號 (超過檔案大小限制)使用 --password 時必須指定 --username您正要將特定問題的通知消音。您將不再看見此問題的浮出式氣泡通知；然而，ABRT 仍會偵測此問題，而您也可以從 ABRT 的圖形使用介面中回報它 您想要繼續嗎？您即將上傳 %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回追伺服器網址回追伺服器連接埠Eunju Kim , 2009. Terry Chuang , 2009, 2010. Cheng-Chia Tseng , 2011, 2012.uReport SSL 憑證路徑或憑證類型uReport 是簡短且完全匿名的問題描述。ABRT 使用 uReport 以快速偵測全域是否有重複問題。預設組態下，uReport 會在回報過程的開頭送出。啟用此選項後，在偵測到問題當下會立即送出 uReport。uReport 已經送出，不再傳送{0} 個debuginfo 檔案尚未安裝