'{Q! 0 <0H y (A [Ny$_!G?"i##$$$$$! %.%aA%%%$%%&,&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.=.0V.'....$./;7/s///8//-/@"0"c0>000C0%:1A`171#1"11!2S2Y2{m223 38A3?z3=334)4+4%41%5W5%6666!707D7.`777.77 777 8+"8BN88888888a8\9u9'99199":,6:c:u:x:f; v;;;a;O<W<2k<< < <<<==1=L= l=y== = ===4=5$>EZ>><>5>6"? Y?f?v? ? ??+? @0 @Q@a@s@@1@0@@ A"A3ASAoA~AAAAAA AA0A?#B$cBBBBQBC8C6TCCC&CCC#C'DGDeDdmD DDD DD6 E*CENnE1ElEs\F)FwF#rG5G$GGGIJLLL>L 1M=MFM&UM|MMMMMM M;NeDN|O'PMR/SfMTTVUqU)U*UU#UVk"VVV$VV W"W 9W)CWmWtW1WWW-W'X(X8X'?XgX X%X XXX& Y4YNY5hY+YYY YY Z$*Z=OZZ'Z'ZZ&[.[M[i[+[=[[*\/\!K\m\\\=\6\]+]I]_]u] ]]-]']^ ^ $^ 2^ ?^'L^t^^!^^^^_ _0"_S_c_s_!_!__@_ #`0`#K`6o``6`S`+8aFda6aSa+6bFbb?b+b)c)?cic pcz}ccd+d6Hd>d>d deee'e/f5ffg gg'ggh$hChRh2ah hh hhh!h:h:i @iMimiiiirij.j&Ajhj0jj j3j"k8k?kl .l;lTl^[lBl l8 mCm Vm dmnmmmmmm n#n8n KnXn_non?n3n;n 2o-?o'mo3oo oo"p"&pIp6\pp-pppqq*%q*Pq{qqq*q"qr !r+rGr[rqr r r r*rKr%!sGsNsgsZsss6 tBtVt$Zttt't/t; uHuQXuuuu uu!u.vRDv3vavn-w0wtwBx6axxx<)/g x}P&16h #Kw2^]z(L _\RbvVe  p. fqs;G[JB'0{FUdQY3 85Z -:MSai+I!%A`>E"rOCXmlkD,c4| *$~NTu7j?W nHto9y@= & [-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 listAdd program names to logAdd to existing Red Hat Support caseAdding attachments to bug %iAdding comment to case '%s'Adding new comment to bug %dAddress of Bugzilla serverAddress of the Red Hat support portalAdvancedAlternate GUI fileAnalyze, collect and report problem data in DUMP_DIRAnalyzingAnalyzing did not start yetAnalyzing failed. You can try another analyzer if available.Analyzing finished. You can proceed to the next step.Analyzing...AppendAppend new reports or overwrite the old one.Append to, or overwrite FILEArchive is created: '%s'Attach FILEs [to bug with this ID]Attach a fileAttaching '%s' to case '%s'Attaching better backtraceAttaching problem data to case '%s'Bad value for '%s': %sBase URL to upload toBug %i is CLOSED as DUPLICATE, but it has no DUP_IDBug %i is CLOSED, but it has no RESOLUTIONBug is already reported: %iBugzillaBugzilla URLBugzilla account passwordBugzilla account user nameBugzilla couldn't find parent of bug %dCaching files from {0} made from {1}Can't copy '%s': %sCan't create a temporary directory in /tmpCan't create temporary file in /tmpCan'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 threadCan't find packages for {0} debuginfo filesCan't open '%s' for writing. Please select another file:Can't parse backtraceCan't remove %s, probably contains an error logCan't remove '{0}': {1}Can't setup {0}: {1}, disablingCan't write to '{0}': {1}CancelCancelled by user.Cannot run vi: $TERM, $VISUAL and $EDITOR are not setCase number (default:previously reported case):Case number:Check SSL key validityChecking for duplicatesChecking for hintsClick 'Apply' to start reportingCollectingCollecting did not start yetCollecting failed. You can try another collector if available.Collecting finished. You can proceed to the next step.Collecting...Compressing dataCon_figure %sConfig fileConfiguration fileConfiguration file (may be given many times)Configure E_ventConfirm data to reportCreate new Red Hat Support caseCreate reported_to in DIRCreating a new bugCreating a new caseDetailsDisplay version and exitDo you still want to create a RHTSupport ticket?Documentation which might be relevant: Don't ask me againDon't store passwordsDownload cancelled by userDownloading ({0} of {1}) {2}: {3:3}%Downloading package {0} failedDownloading {0:.2f}Mb, installed size: {1:.2f}Mb. Continue?Dump directoryEmail was sent to: %sEmpty RHTS login or passwordEmpty login or password, please check your configurationErrorError in case creation at '%s', HTTP code: %dError in case creation at '%s', HTTP code: %d, server says: '%s'Error in case creation at '%s': %sError in case creation at '%s': no Location URL, HTTP code: %dError in comment creation at '%s', HTTP code: %dError in comment creation at '%s', HTTP code: %d, server says: '%s'Error in comment creation at '%s': %sError in comment creation at '%s': no Location URL, HTTP code: %dError initializing yum (YumBase.doConfigSetup): '{0!s}'Error retrieving filelists: '{0!s}'Error retrieving metadata: '{0!s}'Essential element '%s' is missing, can't continueEventEvent ConfigurationExamples: 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 caseExtracting cpio from {0}Find BUG-ID according to DUPHASHForce reporting even if this problem is already reportedFound the same comment in the bug history, not adding a new oneGnome Keyring is not available, your settings won't be saved!Go to next stepHow 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 problemI reviewed the data and _agree with submitting itIf 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'.IncludeInitializing yumInvalid boolean value '%s'Invalid input, program exiting...Invalid number '%s'Invalid utf8 character '%c'Item '%s' already exists and is not modifiableKerneloops URLKerneloops.orgList possible events [which start with PREFIX]Log FileLog to syslogLoggerLogging into Bugzilla at %sLogging outLooking for needed packages in repositoriesLooks like corrupted xml response, because '%s' member is missing.MailxMessage subjectMissing mandatory member 'bugs'Missing mandatory valueNNameName of the logfileNeed writable directory, but '%s' is not writable. Move it to '%s' and operate on the moved data?New Red Hat Support caseNew bug id: %iNo processing for event '%s' is definedNo reporters availableNoninteractive: 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 stringOkOn 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 urlOutput filePackages to download: {0}PasswordPlease 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 descriptionProblem reported via %d report events (%d errors) Provide additional informationRH Portal URLRecipientRecipient's emailRed Hat customer passwordRed Hat customer user nameRegenerate backtraceRemove DIR after reportingRemove DUMP_DIR after reportingRemoving {0}Report to Bugzilla bug trackerReport uploaderReporter(s):ReportingReporting cancelledReporting did not start yetReporting disabled because the backtrace is unusableReporting disabled because the backtrace is unusable.Reporting disabled because the rating does not contain a number '%s'.Reporting doneReporting 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 dataRun EVENT on DUMP_DIRRun analyze event(s) on DUMP_DIRRun collect event(s) on DUMP_DIRSave as text fileSave the problem data to a *.tar.gz in /tmpSave to tar archiveSelect additional files to attach to the report:Select analyzerSelect analyzer: Select collectorSelect collector(s): Select how you would like to analyze the problem:Select how you would like to report the problem:Select reporterSelect reporter(s): Send Binary DataSend binary files like coredumpSend to kernel oops trackerSend via emailSenderSender's emailSending %s to %sSending an email...Setting up yum repositoriesShow logShow passwordSize:Skip analyze steps, go through report steps onlySpecify this only if you modified your /etc/system-release fileStatus: %s%s%s %s/show_bug.cgi?id=%uSubjectSubmitting oops report to %sSuccessfully sent %s to %sThe backtrace is incomplete, please make sure you provide the steps to reproduce.The report was appended to %sThe report was stored to %sThere were %d errors while collecting additional data Ticket/case IDURLUnpacking failed, aborting download...Unsupported option typeUpdates which possibly help: Upload FILEs [to case with this ID]Upload as tar.gz file (via FTP/SCP/...)Uploaded: %llu of %llu kbytesUsage: Use this button to generate more informative backtrace after you installed additional debug packagesUser nameUsernameValueVerify SSLView/edit a text fileWhat additional information would you like to collect?When creating bug, attach binary files tooWhere do you want to upload the tarball with report in form login:password@urlWith -r: do not run analyzers, run only reportersWrong 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 itselfYou can create bugzilla.redhat.com account <a href="https://bugzilla.redhat.com/createaccount.cgi">here</a>You have chosen number out of rangeYou need to fill the how to before you can proceed...Your input is not valid, because of:yProject-Id-Version: libreport Report-Msgid-Bugs-To: POT-Creation-Date: 2013-08-06 13:55+0200 PO-Revision-Date: 2013-08-01 06:58+0000 Last-Translator: Chester Cheng Language-Team: Chinese (Taiwan) Language: zh_TW 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。 如果未指定,CONFFILE 預設至 & [-vbf] [-c CONFFILE] -d DIR or: & [-v] [-c CONFFILE] [-d DIR] -t[ID] FILE... 回報問題至 Bugzilla。 這工具會讀取 DIR。然後登入 Bugzilla 並試圖在 'Whiteboard' 中, 尋找有著同樣 abrt_hash:HEXSTRING 的 bug。 如果找不到這樣的 bug,那就會建立新的 bug。DIR 的元素會儲存 在 bug 裡,根據類型與大小,作為描述或附加檔的一部份。 否則的話,如果有這樣的 bug,並標示為 CLOSED DUPLICATE 的話,這工具會循線找到最原始的 bug,並加入註解。 新的或修改過的 URL 會顯示在螢幕上,並記錄於 'reported_to' 元 素中。 如果未指定的話,CONFFILE 預設至 報告中未偵測到變更 報告已更新# 架構# 追蹤 # 檢查它不包含任何敏感資料 (密碼等等)# 指令列# 元件# 核心傾印# 在下方描述這項錯誤的狀態# 可執行檔# Kernel 版本# 套件# 當機原因# 作業系統的釋出字串# 此欄位為唯讀 %llu 個位元組,%u 個檔案& -o [-d] DIR 回報儲存在特定 DIR 中的 newt 工具& [-v] --target TARGET --ticket ID FILE... 上傳 FILE 到 TARGET 上的特定申請單。 這項工具是用來簡化回報套件至 libreport 的使用者轉換。 可辨識的 TARGET 為 'strata' 與 'bugzilla',第一個與上傳 至 RHTSupport 有關,第二個則是傳送至 Bugzilla。 配置(例如登入資料)可以透過檔案供給。 & [-v] -d DIR [-c CONFFILE] 透過電子郵件發送問題目錄 DIR 的內容 如果不指定的話,CONFFILE 預設至 & [-v] -d DIR [-c CONFFILE] [-u URL] 上傳問題目錄 DIR 的壓縮檔至 URL。 如果未指定 URL,會在 /tmp 中建立壓縮檔並退出。 URL 的格式應為 'protocol://[user[:pass]@]host/dir/[file.tar.gz]' 其中 protocol 可以是 http(s), ftp, scp, 或 file。 File protocol 不能擁有使用者與主機部分:'file:///dir/[file.tar.gz].' 如果 URL 以斜線結束,壓縮檔名稱會被產生,並連至 URL 後面; 否則的話,URL 會作為完整的檔案名稱。 $EXCLUDE_FROM_REPORT 中的檔案不會納入壓縮檔中。 CONFFILE 行的格式應為 'PARAM = VALUE'。 可辨識的字串參數:URL。 參數可以透過 $Upload_URL 覆寫。& [-v] -d DIR [-o FILE] [-a yes/no] [-r] 將問題資訊送往螢幕或 FILE& [-v] [-c CONFFILE]... -d DIR 回報 kernel oops 至 kerneloops.org 或類似網站。 包含在 $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」已存在)--- Running %s ---您的註解並非以私密方式處理。 它們可能被納入能公開查看的問題回報中。新增 %s 至 CC 清單加入程式名稱至紀錄檔新增現有的 Red Hat 支援案例新增附件至 bug %i正添加評註至案例「%s」新增備註至 bug %dBugzilla Red Hat 支援中心的電子郵件地址進階其它 GUI 檔案分析、蒐集、回報 DUMP_DIR 的問題資料分析尚未開始分析分析失敗,請使用其它分析程式。分析完成。請進行下一步驟。正在分析...附加附加新報告或複寫舊的報告。附加至或覆寫 FILE封存檔案已建立:「%s」附加 FILE [至含有此 ID 的 bug]附加檔案附加「%s」至專案「%s」附加更好的 backtrace正附加問題資料至案例「%s」「%s」的值錯誤:%s欲上傳至的基礎 URLBug %i 已 CLOSED 為 DUPLICATE,不過它無 DUP_IDBug %i 已關閉,不過尚無解決方法錯誤已回報:%iBugzillaBugzilla URLBugzilla 帳號密碼Bugzilla 帳號使用者名稱Bugzilla 找不到 bug %d 的 parent將來自 {0} 的檔案放入快取,這是由 {1} 所產生無法複製 '%s': %s無法在 /tmp 中建立暫時性目錄無法在 /tmp 中建立暫時性檔案無法刪除:'%s'無法停用軟體庫:'{0!s}': {1!s}無法從「{0}」展開檔案無法展開套件「{0}」找不到 crash 執行續找不到 {0} 個 debuginfo 檔案的套件無法開啟 '%s' 以進行寫入。請選擇其它檔案:無法剖析 backtrace無法移除 %s,可能包含錯誤日誌無法移除「{0}」:{1}無法設定 {0}: {1},停用中無法寫入「{0}」:{1}取消被使用者取消。無法執行 vi:$TERM、$VISUAL 以及 $EDITOR 尚未設置案例編號(預設值:之前回報的案例):案例編號:檢查 SSL 金鑰是否有效檢查是否有重複檢查是否有提示點擊「套用」開始回報蒐集中尚未開始蒐集蒐集失敗。請使用其它蒐集程式。蒐集完成。請進行下一步驟。蒐集中……壓縮資料配置 %s(_f)配置檔案配置檔案配置檔案(可能會提供多次)配置事件(_v)確認欲回報的資料建立新的 Red Hat 支援案例在 DIR 中建立 reported_to建立新的 bug正在建立新案例詳情顯示版本並退出您仍然想建立 RHTSupport 的申請單嗎?相關文件:不要再問我不要儲存密碼下載程序已被使用者中斷下載 ({1} 之 {0}) {2}:{3:3}%下載套件 {0} 失敗下載 {0:.2f}Mb,已安裝大小:{1:.2f}Mb。是否繼續?傾印目錄電子郵件已送往:%sRHTS 登錄名稱或密碼是空的登錄名稱或密碼是空的,請檢查您的配置錯誤於「%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}'擷取 metadata 時發生錯誤:'{0!s}'找不到基本元素 '%s',無法繼續事件事件組態例如:ftp://[user[:pass]@]host/dir/[file.tar.gz], scp://[user[:pass]@]host/dir/[file.tar.gz], file:///dir/[file.tar.gz]現有的 Red Hat 支援案例從 {0} 擷取 cpio根據 DUPHASH 尋找 BUG-ID即使此問題已經回報過,仍然回報此問題在 bug 歷史中尋找同樣的評論,而不是新增評論Gnome Keyring 無法使用,您的設定將不會被儲存!下一步這問題是怎麼發生的(詳述步驟)?如何再次產生此問題?任何說明可以幫助我們診斷問題?請儘可能使用英文。您希望如何回報問題?您希望如何分析問題? 我不知道這問題是什麼造成的我已檢視資料,並同意提交資料 (_a)如果您已回報了遠端伺服器,請確定您已移除所有私人資料(例如使用者名稱與密碼)。Backtrace、命令列、環境變數通常是需要檢視的東西。若您希望將問題回報至不同的目的地,請蒐集額外資訊,或提供較詳盡的問題描述、重複回報程序,並按下「下一步」。包含初始化 yum無效的布林值「%s」無效的輸入,程式正在退出...無效的數字「%s」無效的 utf8 字元「%c」項目 '%s' 已存在,無法修改Kerneloops URLKerneloops.org列出可能的事件(以 PREFIX 作為起始)日誌檔案紀錄至 syslog紀錄程式登入 Bugzilla 於 %s登出從軟體庫中尋找所需套件看似損毀的 xml 回應,因為「%s」成員遺失。Mailx訊息主旨必要的成員「bugs」遺失遺失必要的值否 (N)名稱日誌檔案的名稱需要可寫入的目錄,但 '%s' 並不是可寫入目錄。將它移到 '%s' 並在移動過的資料操作。新的 Red Hat 案例新的 bug id:%i未定義「%s」事件的處理動作沒有可用的回報程式非互動式:不詢問問題,假設「Yes」未連接空檔案 '%s'注意:已經回報至「%s」僅通知(不要將這報告標示為以發送)OS 發行版本字串確定在接下來的畫面上,您將會被要求描述問題如何發生、選擇如何分析問題(若有需要)、檢視蒐集的資料,以及選擇問題該向哪回報。請按下「下一步」以繼續進行。Oops 伺服器 url輸出檔案要下載的套件:{0}密碼請嘗試以指令手動式安裝 debuginfo:「debuginfo-install %s」,接著再次嘗試 偵測到疑為敏感性資料,請仔細檢視已標示資料。問題描述問題已透過 %d 回報事件回報(%d 項錯誤) 提供額外資訊RH 中心 URL收件者收件者電子郵件地址Red Hat 客戶密碼Red Hat 客戶使用者名稱重新產生追蹤訊息回報後移除 DIR回報完成後移除 DUMP_DIR移除 {0}向 Bugzilla bug 追蹤程式回報報告上傳程式回報者:回報已取消回報尚未開始回報已停用回報,因為追蹤(backtrace)功能無法使用已停用回報,因為無法使用追蹤功能。回報已停用,因為評分不包含一個數字「%s」回報完成回報失敗。請使用其它分析程式。回報完成。請進行下一步驟。回報已完成。您現在可將此視窗關閉。正在回報...檢視資料在 DUMP_DIR 上執行 EVENT在 DUMP_DIR 上執行事件分析在 DUMP_DIR 上執行蒐集事件儲存成文字檔將有問題的資料儲存至 /tmp 目錄的 *.tar.gz儲存至 tar 備份檔選擇要附加至此報告的額外檔案:選擇分析程式選擇分析程式:選擇蒐集者選擇蒐集者:選取您希望分析該問題的方式:選取您希望回報該問題的方式:選擇回報程式選擇回報程式:傳送二進位資料傳送類似核心傾印的二進位檔案發送到 kernel oops 追溯程式透過電子郵件傳送寄件者寄件者電子郵件地址將 %s 傳送至 %s傳送電子郵件...設定 yum 軟體庫顯示日誌顯示密碼大小:跳過分析步驟,僅進行回報步驟只有在您修改了 /etc/system-release 檔案之後,才指定此參數狀態:%s%s%s %s/show_bug.cgi?id=%u主旨傳送 oops 報告至 %s已成功將 %s 傳送至 %s追蹤(backtrace)資訊不完整,請確認您提供了能夠重現問題的步驟。報告已附加至 %s報告已儲存至 %sThere were %d errors while collecting additional data 申請單/專案 IDURL解壓縮失敗,放棄下載……不受支援的選項類型有所幫助的更新:上傳 FILE [至含有此 ID 的專案]以 tar.gz 檔案儲存(透過 FTP/SCP/...)已上傳:%llu 個位元組(總共 %llu 個位元組)使用方法:使用此按鈕讓您在安裝額外的除錯套件後,產生更多追蹤訊息使用者名稱使用者名稱值驗證 SSL檢視/編輯文字檔案您要蒐集哪些額外資訊?當建立 bug 時,亦請附加 binary 檔案您希望將包含了報告的 tarball,以 login:password@url 格式上傳到哪使用 -r:不執行分析,僅執行回報程式偵測到 %s 的設定值,若您以目前的組態繼續的話,回報動作可能會失敗。偵測到 %s 的設定值錯誤,若您以目前的組態繼續的話,回報動作可能會失敗。您正試著將檔案複製到同一個檔案上您可建立 bugzilla.redhat.com 帳號 <a href="https://bugzilla.redhat.com/createaccount.cgi">here</a>您選擇的數目超出範圍在繼續進行之前,您必須填入相關資訊...您的輸入無效,因為:是 (y)