grthtrhthjhtyjytjytkergtrhtrjytjerhrfh4:24 29/09/2026N$H1I12A7'<<=Q(=z= = =0= == ==( >65>l>>->$>>>?[N?@1A_AG4B|C*9ExdFFeGGGGTG$HCHZHzHHHHaH>4IsID JUeJ2JJKK:KWKtKK KKK' L'4L\L%wLL=L+L%M+.MZMpM&M'MM%MRN:pN>NN,NO;OTO"qO$O OOOO#PBPYPoP uP3P*PPBP>Q GQTQnQ'QQQ Q$Q@ RALRR*RRRS-%S&SSzSSS3S5SA-T'oT>TT+T8UQWUQUU V8VUVrVVV0VV.W4WNWUW)hW;WW5W X3XJXbXAuX%XX X XY,YHYgY~YQYYZZ'Z.\,z\^\R]Y]o]8u]!]%]-]@$^"e^>^0^C^%<_Ab_7_/_# `"0`&S` z`#`1`X`X3aaa b,%b2Rbb b b'bb c(c"Dcgcc4cc4c?'d"gd,d"dd9d.e/Ge0we+e9e8fGfff#ff#f?fA*glg sg ~gg-+h!Yh){hh%h2h1iMijj.k(kkkl".lQlilll>l;l+m;Gm,m.mmm7m=5n2sn.nn nnn oEo+ao(o(oBo"p(pHp)hpp!q1qIqeqgqlqaqbqErTrmr1rr,rssss tt*tN3tatMt&2u$Yu~u$u!uvu@Zv6vmva@w!wOw x$ xOExxxx:x7y8>y=wy:y;yC,z@pzAz?z<3{=p{;{8{9#|9]|6|7|6}3=}4q}A}>}?'~<g~=~2~3 ITq5B"A GUt y ց" /<C"S v'߂* D N6X,"Jm I$iP(߅I7R&,'ކ7%4]4%LJ1=2]"Έ  2>9x!Ή߉;JQ`"u#Њ$$"%G&m ËZ/`S[SS[$ (&IpqxPY)h-Ǐ7Q-@b,#.PJ[ʑ&t &ē)E @P0/”'``{+ܕ/8FWb9J*N-y4&ܗ&*B#`'6#%EMe9:-," OYby qҚMDKޛ* N8 )sw/#˝5a4A̟$*39^ĠʠHϠ3cLI5B07s7/"6:Ia#7Qi{PkSLβGײ +4)Cm|  /ӳ)0&ZAlNӶSk1+|ƻCѼ!]9 н# 0<eT7F?ѿK](|  (>g#")0ONC-1%O.u%E607g' -$"R u%$&-GNPUC7: CPf% =RGm1!$@.Z..!=P(K."9QEB)8>#w+!78p+9!=1o623 FP W!aL5Ndt7-0$EU!%"@=-~eJ]xD',6SP+F6SN+F?2U+), -,EWrY$+ $- %0-Ft *#N'jD')!)K:f-<)'7Q6!!<?^? 9$'5].|i .*!!(J&e!!>HBXL&Ov0J6/G w E$#%(I:r#'%%  | S9![-q 8W>Z$*(!HJ60_.Q a"nT 0 ->4l/,-5,2b352122d/6.+-3Y)&'30:1k./&'# KU hu'9'  3Nc $#C"g 3 * huF"F%<=b1'*!E4g47& /0;`,"   # 1?R6Y!!'$+Pp $) , M&Z)*+  %l2 /V\DSY%O!u#o2AK'1 K?<Z4#/X<P`!6Xn&B=1, ^U[#M $q  5 e K 2_  0 - 4 +* $V {  ( , 1 !; !]     2 ; #K #o       Z2[[E\3xR 0 v=t)H678?p#4 ( 3 >I Q \ g r}C4\S[4@1%2W8% :X1 1KJ2}f]S?bv)L"F[QZr=1=T20;;Yt,>|SqfBW%xKoC N* *l >#)"r k3Awp/Ga"!XEwu+=`jEF K M^5J\*:?MJ',3sH~YI#&83 ,%Q!dIA&@R$m7 0CLP +T@1\9.tRmJ@2v_Di0 [^NK5x !eV4 e|kO:#8{-h_+zdW'}/)N(z>g'$G 7U54p-Mc yAB8lcs(gObuHH/6I$7-yL6Zn:9FV 9Pn<<6qC(Ehi~D{UD1 %?Go.XB;]a&`  .<j4 & [-v] [-c CONFFILE] [-F FMTFILE] -d DIR or: & [-v] [-c CONFFILE] [-d DIR] -t[ID] [-u -C UR_CONFFILE] FILE... Reports a problem to RHTSupport. If not specified, CONFFILE defaults to & [-vbf] [-g GROUP-NAME]... [-c CONFFILE]... [-F FMTFILE] [-A FMTFILE2] -d DIR or: & [-v] [-c CONFFILE]... [-d DIR] -t[ID] FILE... or: & [-v] [-c CONFFILE]... [-d DIR] -t[ID] -w or: & [-v] [-c CONFFILE]... -h DUPHASH [-p[PRODUCT]] 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. Option -t uploads FILEs to the already created bug on Bugzilla site. The bug ID is retrieved from directory specified by -d DIR. If problem data in DIR was never reported to Bugzilla, upload will fail. Option -tID uploads FILEs to the bug with specified ID on Bugzilla site. -d DIR is ignored. Option -w adds bugzilla user to bug's CC list. Option -r sets the last url from reporter_to element which is prefixed with TRACKER_NAME to URL field. This option is applied only when a new bug is to be filed. The default value is 'ABRT Server' If not specified, CONFFILE defaults to & [-vf] [-c CONFFILE]... [-F FMTFILE] [-A FMTFILE2] -d DIR or: & [-v] [-c CONFFILE]... [-d DIR] -t[ID] FILE... or: & [-v] [-c CONFFILE]... [-d DIR] -t[ID] -w or: & [-v] [-c CONFFILE]... -h DUPHASH Reports problem to MantisBT. The tool reads DIR. Then it tries to find an issue with the same abrt_hash in custom field 'abrt_hash'. If such issue is not found, then a new issue is created. Elements of DIR are stored in the issue as part of issue description or as attachments, depending on their type and size. Otherwise, if such issue is found and it is marked as CLOSED DUPLICATE, the tool follows the chain of duplicates until it finds a non-DUPLICATE issue. The tool adds a new comment to found issue. The URL to new or modified issue is printed to stdout and recorded in 'reported_to' element. Option -t uploads FILEs to the already created issue on MantisBT site. The issue ID is retrieved from directory specified by -d DIR. If problem data in DIR was never reported to MantisBT, upload will fail. Option -tID uploads FILEs to the issue with specified ID on MantisBT site. -d DIR is ignored. Option -r sets the last url from reporter_to element which is prefixed with TRACKER_NAME to URL field. This option is applied only when a new issue is to be filed. The default value is 'ABRT Server' 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# Release string of the operating system from root dir# This field is read only # os-release configuration file# os-release configuration file from root dir$DATA_DIRECTORY/%s (binary file, %s)%llu bytes, %u files& [-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] [-F FMTFILE] Sends contents of a problem directory DIR via email If not specified, CONFFILE defaults to & [-v] -d DIR [-c CONFFILE] [-u URL] [-b FILE] [-r FILE] Uploads compressed tarball of problem directory DIR to URL. If URL is not specified, creates tarball in & [-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.& [-v] [-c FILE] [-u URL] [-k] [-t SOURCE] [-h CREDENTIALS] [-A -a bthash -B -b bug-id -E -e email -O -o comment] [-d DIR] [-A -a bthash -T ATTACHMENT_TYPE -r REPORT_RESULT_TYPE -L RESULT_FIELD] [-d DIR] [-A -a bthash -T ATTACHMENT_TYPE -l DATA] [-d DIR] & [-v] [-c FILE] [-u URL] [-k] [-t SOURCE] [-h CREDENTIALS] [-i AUTH_ITEMS] [-d DIR] Upload micro report or add an attachment to a micro report Reads the default configuration from & [-v] [-d DIR] [-m MESSAGEID] [-F FMTFILE] [-p NONE|ESSENTIAL|FULL] [-s SYSLOGID] Reports problem information into systemd journal. The tool reads problem directory DIR and sends its details into systemd journal as a message. If MESSAGEID is defined, the tool creates a catalog message as well. & [-vpdx] [-e EVENT]... [-g GUI_FILE] PROBLEM_DIR GUI tool to analyze and report problem saved in specified PROBLEM_DIR& [-vsp] -L[PREFIX] [PROBLEM_DIR] or: & [-vspy] -e EVENT PROBLEM_DIR or: & [-vspy] -d PROBLEM_DIR or: & [-vspy] -x PROBLEM_DIR'%s' is not an ordinary file'%s' is not correct file name'comment' file is empty'strata' or 'bugzilla''{0}' must be owned by abrt. Please run '# chown -R abrt.abrt {0}' to fix the issue.('%s' completed successfully) ('%s' exited with %u) ('%s' was killed by signal %u) (binary file, %llu bytes)(click here to view/edit)(no description)--- Running %s ---Your comments are not private. They may be included into publicly visible problem reports.A name of bug tracker for an additional URL from 'reported_to'A private ticket creation has been requested, but no groups were specified, please see https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-tickets for more infoA proper debuginfo is probably missing or the coredump is corrupted.A timeout was reached while waiting for a prompt result from the DBus Secret Service.Add bugzilla user to CC list [of bug with this ID]Add program names to logAdding %s to CC listAdding External URL to bug %iAdding External URL to issueAdding attachments to bug %iAdding attachments to issue %iAdding comment to case '%s'Adding extra cc %s to bug reportAdding new comment to bug %dAdding new comment to issue %dAdditional files included in 'auth' keyAddress of AlmaLinux Bug Tracker serverAddress of Bugzilla serverAddress of the Red Hat support portalAddress of uReport webserviceAdds your Bugzilla login to CC List of already reported bugs.Adds your e-mail to CC List of Bugzilla bugAdvancedAllow insecure connection to ureport serverAlmaLinux Bug TrackerAlmaLinux Bug Tracker URLAlmaLinux Bug Tracker account passwordAlmaLinux Bug Tracker account user nameAlmaLinux Bug Tracker projectAlmaLinux Bug Tracker project versionAnalyze the problem locally and export the problem data information to a text fileAnalyze the problem locally and send information via emailAnalyze the problem locally and upload the data via scp or ftpAppendAppend new reports or overwrite the old one.Append to, or overwrite FILEArchive is created: '%s'Ask Red Hat Support for helpAttach FILEs [to bug with this ID]Attach FILEs [to issue with this ID]Attach a fileAttaching '%s' to case '%s'Attaching better backtraceAttaching file '%s' to issue %sAttaching problem data to case '%s'Bad value for '%s': %sBase URL to upload toBasicBe verboseBug %i is CLOSED as DUPLICATE, but it has no DUP_IDBug %i is CLOSED, but it has no RESOLUTIONBug is already reported: %iBug.search(quicksearch) return value did not contain member 'bugs'BugzillaBugzilla URLBugzilla account passwordBugzilla account user nameBugzilla couldn't find parent of bug %dBugzilla productBugzilla product versionC_onfigureCaching files from {0} made from {1}Can't call method '%s' over DBus on path '%s' interface '%s': %sCan't connect over DBus to name '%s' path '%s' interface '%s': %sCan't continue without URLCan't continue without email address of %sCan't continue without loginCan't continue without passwordCan't copy '%s': %sCan't create a secret item for event '%s': %sCan't create a temporary directory in Can't create temporary file in Can't delete '%s': %sCan't delete: '%s'Can't determine Bugzilla Product from problem data.Can't determine RH Support Product from problem data.Can't disable async download, the output might contain artifacts!Can't disable repository '{0!s}': {1!s}Can't extract files from '{0}'. For more information see '{1}'Can't extract package '{0}'Can't find packages for {0} debuginfo filesCan't generate stacktrace description (no crash thread?)Can't get Bugzilla ID because this problem has not yet been reported to Bugzilla.Can't get MantisBT ID because this problem has not yet been reported to MantisBT.Can't lseek '%s'Can't open '%s'Can't open '%s' for writing. Please select another file:Can't open problem dir '%s'.Can't parse backtrace: %sCan't read '%s'Can't remove '{0}': {1}Can't remove {0}, probably contains an error logCan't setup {0}: {1}, disablingCan't upload '%s', it's too large (%llu bytes)Can't write to '{0}': {1}CancelCancelled by user.Cannot attach comment from 'comment' fileCannot check backtrace rating because of invalid event nameCannot copy file '{0}': {1}Cannot run vi: $TERM, $VISUAL and $EDITOR are not setCatalog message idCheck SSL key validityChecking for duplicatesChecking for hintsClear the search bar to see the list of security sensitive words.Closing bug %i as duplicate of bug %iCompressing dataConfig fileConfigurationConfiguration fileConfiguration file (may be given many times)Configuration file for uReportConfirm data to reportContact email addressCreate new Red Hat Support case - I would like to be contacted by Red Hat SupportCreate reported_to in DIRCreating a new bugCreating a new caseCreating a new issueCredentials are not provided by configuration.CustomD-Bus Secrets Service ReadAlias('%s') method failed: %sDebugDefine SYSLOG_IDENTIFIER systemd journal fieldDetailsDisplay version and exitDo you still want to create a RHTSupport ticket?Do you want to stop waiting and continue in reporting without properly loaded configuration?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 problem dir into systemd journal fieldsEmail address of %s was not specified. Would you like to do so now? If not, '%s' is to be usedEmail address that can be used by ABRT server to inform you about news and updatesEmail was sent to: %sErrorError in HTTP POST, HTTP code: 404 (Not found), URL:'%s'Error in MantisBT request at '%s'Error in MantisBT request at '%s': %sError 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 reading repository configuration: '{0!s}'Error retrieving filelists: '{0!s}'Error retrieving metadata: '{0!s}'Error setting up repositories: '{0!s}'Error: %sError: can't make cachedir, exitingEssential element '%s' is missing, can't continueEvent '%s' requires permission to send possibly sensitive data. Do you want to continue?Event '%s' requires permission to send possibly sensitive data. Do you want to continue?EventsExamples: ftp://[user[:pass]@]host/dir/[file.tar.gz] scp://[user[:pass]@]host/dir/[file.tar.gz] file:///dir/[file.tar.gz]Expert modeExport the problem data for manual reportingExport the problem data information to a text fileExtracting cpio from {0}FTP ProxyFailed on submitting the problemFailed to add MantisBT issue note: '%s'Failed to attach file: '%s'Failed to close TAR writerFailed to create a new bug.Failed to create a new issue: '%s'Failed to dump xml node.Failed to finalize TAR archiveFailed to format duplicate comment from problem dataFailed to format problem dataFailed to generate microreport from the problem dataFailed to get 'REDHAT_BUGZILLA_PRODUCT' from '/etc/os-release'.Failed to get MantisBT issue: '%s'Failed to get custom fields for '%s' projectFailed to get project id from nameFailed to open TAR writerFailed to read '/etc/os-release' to get Bugzilla product.Failed to save file '%s'Failed to search MantisBT duplicate issue: '%s'Failed to search MantisBT issue by duphash: '%s'Failed to upload uReport to the server '%s'Failed to upload uReport to the server '%s' with curl: %sForce reporting even if this problem is already reportedFormatting file for a new caseFormatting file for an emailFormatting file for catalog messageFormatting file for duplicatesFormatting file for initial commentFound the same comment in the bug history, not adding a new oneFound the same comment in the issue history, not adding a new oneGroupsHTTP ProxyHTTPS ProxyHow 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 it can be reproduced (one step per line)?How reproducible is this problem?How would you like to report the problem?I can reproduce this problemI don't know what caused this problemI have experienced this problem for the first timeI 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'.If you want to update the configuration and try to report again, please open Preferences item in the application menu and after applying the configuration changes click Repeat button.Ignored invalid ISO date of report result '%s'Ignoring URL without scheme and hostnameIncludeInitializing package managerInvalid boolean value '%s'Invalid duplicate format file: '%sInvalid format file: %sInvalid input, exiting.Invalid number '%s'Invalid password or login.Invalid password or login. Please enter the password for '%s':Invalid password or login. Please enter your Red Hat login:Invalid utf8 character '%c'Issue %i is CLOSED as DUPLICATE, but it has no DUPLICATE_IDIssue %i is CLOSED, but it has no RESOLUTIONItem '%s' already exists and is not modifiableKerneloops URLKerneloops.orgLearn more about restricted access in the configurationLinking ABRT crash statistics record with contact email: '%s'Linking ABRT crash statistics record with the caseList possible events [which start with PREFIX]Log FileLog to syslogLoggerLogging into Bugzilla at %sLogging outLogin is not provided by configuration. Please enter your RHTS login:Looking for needed packages in repositoriesLooking for similar problems in MantisBTLooking for similar problems in bugzillaLooks like corrupted xml response, because '%s' member is missing.MailxMalformed url to Bugzilla '%s'.Malformed url to MantisBT '%s'.MantisBT couldn't find parent of issue %dMantisBT doesn't contain custom field '%s', which is required for full functionality of the reporter. Do you still want to create a new issue?Message subjectMissing mandatory valueMissing required item: '%s'NNameName of the logfileNeed writable directory, but '%s' is not writable. Move it to '%s' and operate on the moved data?Neither environment variable 'uReport_ContactEmail' nor configuration option 'ContactEmail' is setNew bug id: %iNo description availableNo reporters availableNoninteractive: don't ask questions, assume 'yes'Note does not contain ratingNotify only (Do not mark the report as sent)OKOkOn 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}PasswordPassword is not provided by configuration. Please enter the password for '%s':Please add a comprehensive description of the problem you have. This is a very long place holder.Please enter a URL (scp, ftp, etc.) where the problem data is to be exported:Please enter password for '%s//%s@%s':Please enter password for uploading:Please enter the password forPlease enter user name for '%s//%s':Please enter your MantisBT login:Please provide a short description of the problem and please include the steps you have used to reproduce the problem.Please provide the steps you have used to reproduce the problem.Please report this problem to ABRT project developers.Please review the data before it gets reported. Depending on reporter chosen, it may end up publicly visible.Please try to install debuginfo manually using the command: "debuginfo-install %s" and try again.Please, type email address of %s:Possible sensitive data detected, feel free to edit the report and remove them.PreferencesPrint BUG_ID which has given DUPHASHProblem '{0!s}' occured while downloading from mirror: '{1!s}'. Trying next oneProblem descriptionProblem detailsProblem directoryProcess the C/C++ crash using the AlmaLinux infrastructureProcess the C/C++ crash using the Fedora infrastructureProcess the C/C++ crash using the Red Hat infrastructureProcess the Java exception using the AlmaLinux infrastructureProcess the Java exception using the Fedora infrastructureProcess the Java exception using the Red Hat infrastructureProcess the JavaScript exception using the AlmaLinux infrastructureProcess the JavaScript exception using the Fedora infrastructureProcess the JavaScript exception using the Red Hat infrastructureProcess the X Server problem using the AlmaLinux infrastructureProcess the X Server problem using the Fedora infrastructureProcess the X Server problem using the Red Hat infrastructureProcess the kernel crash using the AlmaLinux infrastructureProcess the kernel crash using the Fedora infrastructureProcess the kernel crash using the Red Hat infrastructureProcess the kerneloops using the AlmaLinux infrastructureProcess the kerneloops using the Fedora infrastructureProcess the kerneloops using the Red Hat infrastructureProcess the problem using the AlmaLinux infrastructureProcess the problem using the Fedora infrastructureProcess the problem using the Red Hat infrastructureProcess the python 3 exception using the AlmaLinux infrastructureProcess the python 3 exception using the Fedora infrastructureProcess the python exception using the AlmaLinux infrastructureProcess the python exception using the Fedora infrastructureProcess the python exception using the Red Hat infrastructureProcess the report using the Fedora infrastructureProcess the report using the Red Hat infrastructureProcessingProcessing did not start yetProcessing doneProcessing failed.Processing finished, please proceed to the next step.Processing finished.Processing interrupted: can't continue without writable directory.Processing of the problem failed. This can have many reasons but there are three most common: ▫ network connection problems ▫ corrupted problem data ▫ invalid configurationProcessing was canceledProcessing was interrupted because the problem is not reportable.Processing...Provide additional informationQuitRH Portal URLRecipientRecipient's emailRed Hat Customer SupportRed Hat customer passwordRed Hat customer user nameRemove DIR after reportingRemove PROBLEM_DIR after reportingRemoving {0}RepeatReport UploaderReport a bug to Fedora maintainersReport a bug to Red Hat BugzillaReport a bug to Red Hat Customer PortalReport to AlmaLinux Bug TrackerReport to Bugzilla bug trackerReport to FedoraReport to Red Hat BugzillaReport to Red Hat supportReported:ReportingReporting has finished. You can close this window now.Restrict accessRestrict access to the created bugzilla ticket allowing only users from specified groups to view it (see advanced settings for more details)Restrict access to the reportRestrict access to this group onlyRestrict the access to specified groups <a href="https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-tickets">?</a>Review the dataRun only these eventsSOAP: Failed to add a new child node because of no node or no child name.SOAP: Failed to add method parametr.SOAP: Failed to add new issue parameters because the required items are missing.SOAP: Failed to add new issue parametrs.SOAP: Failed to create SOAP string because of invalid function arguments.SOAP: Failed to create a new property in custom fields.SOAP: Failed to create a new property.SOAP: Failed to create a new xml child item.SOAP: Failed to create xml text reader.SOAP: Failed to dump xml node.SOAP: Failed to get child element because of no parent.SOAP: Failed to get child node because of no parent.SOAP: Failed to get next element because of no node.SOAP: Failed to get xml root element.SOAP: Failed to parse xml (get related to issue).SOAP: Failed to parse xml (searching value at depth by name).SOAP: Failed to parse xml during creating request.SOAP: Failed to parse xml.SOAP: Failed to print SOAP string.SSH Private key fileSSH Public key fileSSH private key fileSSH public key fileSave as text fileSearchSecret Service is not available, your settings won't be saved!Select a workflow to run: Select an event to run: Select how to report this problemSend Binary DataSend binary files like coredumpSend the problem data via emailSend to kernel oops trackerSend via emailSenderSender's emailSending %s to %s//%sSending ABRT crash statistics dataSending a notification email to: %sSending an email...Sends ureports to FAF serverSensitive wordsServer responded with an error: '%s'Sets the proxy server to use for FTPSets the proxy server to use for HTTPSets the proxy server to use for HTTPSSetting up repositoriesShow logShow passwordSince crashes without a known reproducer can be difficult to diagnose, please provide a comprehensive description of the problem you have encountered.Size:Specify a Bugzilla product (ignored without -h)Specify server URLSpecify this only if you needed different product than specified in /etc/os-releaseSpecify this only if you needed different product version than specified in /etc/os-releaseSpecify this only if you needed different project than specified in /etc/os-releaseSpecify this only if you needed different project version than specified in /etc/os-releaseStatus: %s%s%s %s/show_bug.cgi?id=%uStatus: %s%s%s %s/view.php?id=%uString doesn't seem to be a date: '%s'SubjectSubmit <a href="https://access.redhat.com/articles/642323">micro-report</a> when creating a new case.Submit anonymous crash reportSubmit anonymous crash report - I do not want to be contacted by Red Hat SupportSubmit uReportSubmit uReport before creating a new caseSubmitting oops report to %sSuccessfully created %sThe MantisBT project has not been deretmined.The URL '%s' does not exist (got error 404 from server)The backtrace is incomplete, please make sure you provide the steps to reproduce.The backtrace probably can't help developer to diagnose the bug.The crashed program was released by '%s'. Would you like to report the problem to Red Hat Support?The date: '%s' has unrecognized suffix: '%s'The date: '%s' is out of UNIX time stamp rangeThe issue will be accessible only to users with access to 'Private Issues'The problem cannot be reported due to an invalid data. '%s' file does not contain a number.The problem has only occurred once and the ability to reproduce the problem is unknown. Please ensure you will be able to provide detailed information to our Support Team. Would you like to continue and open a new support case?The program '%s' does not appear to be provided by Red Hat. Would you like to report the problem to Red Hat Support?The report result '%s' is missing URL.The report was appended to %sThe report was stored to %sThe response from '%s' has invalid formatThe server at '%s' currently can't handle the request (got error 503)The server at '%s' encountered an internal error (got error 500)The server at '%s' responded with an error: '%s'This problem does not have an uReport assigned.This problem has already been reported.This problem has been reported to Bugzilla '%s' which differs from the configured Bugzilla '%s'.This problem has been reported to MantisBT '%s' which differs from the configured MantisBT '%s'.This problem has not been reported to '%s'.This problem has not been reported to Bugzilla.This problem occurs repeatedlyThis problem should not be reported (it is likely a known problem). %sThis problem was already reported to MantisBT (see '%s'). Do you still want to create a new issue?Ticket/case IDType mismatch has been detected in the response from '%s'URLUnable to find bug ID in bugzilla URL '%s'Unable to parse bug ID from bugzilla URL '%s'Unable to parse response from ureport server at '%s'Unexpected HTTP response from '%s': %dUnpacking failed, aborting download...Unsupported option typeUpdates which possibly help: Upload FILEs [to case with this ID]Upload as tar.gz file (via FTP/SCP/...)Upload the data via scp or ftp to a remote destinationUpload the problem data to a serverUploaded: %llu of %llu kbytesUrl or request isn't specified.Usage: Use HTTP AuthenticationUse client authenticationUse this field if you do not want to have password in URLUse this field if you do not want to have user name in URLUse this field to specify SSH private keyfileUse this field to specify SSH public keyfileUser nameUsernameUsing Bugzilla ID '%s'Using MantisBT ID '%s'Using default product '%s'ValueVerify SSLView/edit a text fileWarning, private ticket groups already specified as cmdline argument, ignoring the env variable and configurationWarning: Not enough free space in cache dir '{0}' ({1:.2f}Mb left). Continue?Warning: Not enough free space in tmp dir '{0}' ({1:.2f}Mb left). Continue?Watch Bugzilla BugWatch already reported bugsWhen creating bug, attach binary files tooWhere do you want to upload the tarball with report in form login:password@urlWorkflowsYou are trying to copy a file onto itselfYou can create bugs.almalinux.org account <a href="https://bugs.almalinux.org/signup_page.php">here</a>You can create bugzilla.redhat.com account <a href="https://bugzilla.redhat.com/createaccount.cgi">here</a>You have chosen number out of rangeYou have requested to make your data accessible only to a specific group and this bug is a duplicate of bug: %s/%u In case of bug duplicates a new comment is added to the original bug report but access to the comments cannot be restricted to a specific group. Would you like to open a new bug report and close it as DUPLICATE of the original one? Otherwise, the bug reporting procedure will be terminated.You need to fill the how to before you can proceed...You need to specify bthash of the uReport to attach.You need to specify bug ID, contact email, comment or all of themYour input is not valid, because of:Your problem seems to be caused by %s %s Your problem seems to be caused by one of the following: _Cancel_Close_Forward_No_OK_Open_Save_Stop_Yesattach DATA as ureport attachment ATTACHMENT_TYPE (used only with -l|-L)attach RHBZ bug (requires -a|-A, conflicts with -B)attach data of FIELD [URL] of the last report result (requires -a|-A, -r and -T, conflicts with -l)attach last RHBZ bug from reported_to (requires -a|-A, conflicts with -b)attach short text (requires -a|-A, conflicts with -D)attach short text from comment (requires -a|-A, conflicts with -d)attach to a bthash from reported_to (conflicts with -a)attach value (requires -a|-A and -T, conflicts with -L)bthash of uReport to attach (conflicts with -A)can't get secret value of '%s': %scannot be reportedcontact e-mail address (requires -a|-A, conflicts with -E)contact e-mail address from environment or configuration file (requires -a|-A, conflicts with -e)dataeffilegzip exited with %dgzip killed with signal %dgzip process failedlocked by another processnot a problem directorypermission denieduReportuReport Server URLuid value is not valid: '%s'use REPORT_RESULT_TYPE when looking for FIELD in reported_to (used only with -L)yProject-Id-Version: PACKAGE VERSION Report-Msgid-Bugs-To: PO-Revision-Date: 2017-09-12 07:46+0000 Last-Translator: Copied by Zanata Language-Team: Chinese (Taiwan) (http://www.transifex.com/projects/p/libreport/language/zh_TW/) Language: zh_TW MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=1; plural=0; X-Generator: Zanata 4.6.2 & [-v] [-c CONFFILE] [-F FMTFILE] -d DIR 或： & [-v] [-c CONFFILE] [-d DIR] -t[ID] [-u -C UR_CONFFILE] FILE... 回報問題給 RHTSupport。 若未指定，則 CONFFILE 預設為 & [-vbf] [-g GROUP-NAME]... [-c CONFFILE]... [-F FMTFILE] [-A FMTFILE2] -d DIR 或： & [-v] [-c CONFFILE]... [-d DIR] -t[ID] FILE... 或： & [-v] [-c CONFFILE]... [-d DIR] -t[ID] -w 或： & [-v] [-c CONFFILE]... -h DUPHASH [-p[PRODUCT]] 回報問題至 Bugzilla。 本工具會讀取 DIR。接著會登入 Bugzilla 並嘗試尋找「Whiteboard」中 有相同 abrt_hash:HEXSTRING 的臭蟲回報。 若找不到這樣的臭蟲，則新建臭蟲回報。DIR 的元素會儲存在回報中， 作為臭蟲描述的一部分，或是作為附件，取決於其類型與大小。 否則，若有找到這樣的臭蟲，則標記為 CLOSED DUPLICATE， 本工具會追尋重複項目的鏈結，直到找出 non-DUPLICATE 臭蟲為止。 本工具會增補新評註到找到的臭蟲中。 新臭蟲或修改之臭蟲回報 URL 會列印到 stdout 並記錄在 'reported_to' 元素中。 選項 -t 會上傳 FILEs 到 Bugzilla 站臺已經建立的臭蟲回報中。 臭蟲 ID 會從 -d DIR 指定的目錄中擷取出來。 若 DIR 中的從未回報到 Bugzilla，則會上傳失敗。 選項 -tID 會將 FILEs 上傳到 Bugzilla 站臺指定 ID 臭蟲回報中。 -d DIR 會被忽略。 選項 -w 會將 bugzilla 使用者加到臭蟲的 CC 副本清單中。 選項 -r 會根據前綴有 TRACKER_NAME 的 reporter_to 元素 設定上次的 URL 到 URL 欄位中。 這個選項僅在要提交新臭蟲的時候會套用。 預設值為「ABRT Server」 若未指定，則 CONFFILE 預設為 & [-vf] [-c CONFFILE]... [-F FMTFILE] [-A FMTFILE2] -d DIR 或： & [-v] [-c CONFFILE]... [-d DIR] -t[ID] FILE... 或： & [-v] [-c CONFFILE]... [-d DIR] -t[ID] -w 或： & [-v] [-c CONFFILE]... -h DUPHASH 回報問題給 MantisBT。 本工具會讀取 DIR。接著會在「abrt_hash」自訂欄位中嘗試尋找 有相同 abrt_hash 的相關議題。 若找不到這樣的議題，則會建立新議題。DIR 的元素會以議題的描 述部分或附件方式儲存在議題之中，取決於類型和大小而定。 否則，若有找到這樣的議題，則會將之標記為 CLOSED DUPLICATE， 本工具會追尋重複項目的鏈結，直到找出 non-DUPLICATE 議題為止。 本工具會增補新評註到找到的議題中。 新議題或修改之議題 URL 會列印到 stdout 並記錄在 'reported_to' 元素中。 選項 -t 會上傳 FILEs 到 MantisBT 站臺已經建立的議題中。 議題 ID 會從 -d DIR 指定的目錄中擷取出來。 若 DIR 中的從未回報到 MantisBT，則會上傳失敗。 選項 -tID 會將 FILEs 上傳到 MantisBT 站臺指定 ID 議題中。 -d DIR 會被忽略。 選項 -r 會根據前綴有 TRACKER_NAME 的 reporter_to 元素 設定上次的 URL 到 URL 欄位中。 這個選項僅在要提交新議題的時候會套用。 預設值為「ABRT Server」 若未指定，則 CONFFILE 預設為 報告中未偵測到更動 報告已更新# 架構# 回溯資料 # 請確認它不包含任何敏感資料 (密碼等等)# 指令列# 元件# 核心傾印# 在下方描述此程式崩潰的情況# 可執行檔# 內核心版本# 軟體包# 程式崩潰的原因# 作業系統的發行版字串# 來自根目錄的作業系統發行版字串# 此欄位為唯讀 # os-release 組態檔# 來自根目錄的 os-release 組態檔$DATA_DIRECTORY/%s (二進位檔，%s)%llu 位元組，%u 個檔案& [-d] DIR 回報儲存於指定 DIR 目錄中問題的新工具& [-v] --target TARGET --ticket ID FILE... 上傳 FILE 到 TARGET 上的特定申請單。 這項工具是用來簡化回報軟體包至 libreport 的使用者轉換。 可辨識的 TARGET 為 'strata' 與 'bugzilla'，第一個與上傳 至 RHTSupport 有關，第二個則是傳送至 Bugzilla。 組態 (例如登入資料) 可以透過檔案方式提供。 & [-v] -d DIR [-c CONFFILE] [-F FMTFILE] 透過電子郵件傳送問題目錄 DIR 的內容 若未指定，則 CONFFILE 預設為 & [-v] -d DIR [-c CONFFILE] [-u URL] [-b FILE] [-r FILE] 上傳壓縮的 DIR 問題目錄 tarball 到 URL。 若未指定 URL，則建立 tarball 於 & [-v] -d DIR [-o FILE] [-a yes/no] [-r] 將問題資訊送往標準輸出或 FILE& [-v] [-c CONFFILE]... -d DIR 回報 kernel oops 至 kerneloops.org 或類似網站。 包含在 $EXCLUDE_FROM_REPORT 中的檔案不會納入 tarball 中。 CONFFILE 必須要有 'PARAM = VALUE' 格式。 可辨識的字串參數：SubmitURL。 參數可透過 $KerneloopsReporter_SubmitURL 覆蓋。& [-v] [-c FILE] [-u URL] [-k] [-t SOURCE] [-h CREDENTIALS] [-A -a bthash -B -b bug-id -E -e email -O -o 評註] [-d DIR] [-A -a bthash -T ATTACHMENT_TYPE -r REPORT_RESULT_TYPE -L RESULT_FIELD] [-d DIR] [-A -a bthash -T ATTACHMENT_TYPE -l DATA] [-d DIR] & [-v] [-c FILE] [-u URL] [-k] [-t SOURCE] [-h CREDENTIALS] [-i AUTH_ITEMS] [-d DIR] 上傳微回報或將附件加到微回報中 閱讀預設組態檔，取自 & [-v] [-d DIR] [-m MESSAGEID] [-F FMTFILE] [-p NONE|ESSENTIAL|FULL] [-s SYSLOGID] 回報問題資料到 systemd 日誌中。 本工具會讀取 DIR 問題目錄的資料並將相關細節以訊息方式送到 systemd 日誌中。若 MESSAGEID 有定義，則本工具也會建立 目錄訊息。 & [-vpdx] [-e EVENT]... [-g GUI_FILE] PROBLEM_DIR 分析並回報儲存於指定 PROBLEM_DIR 中問題的圖形介面工具& [-vsp] -L[PREFIX] [PROBLEM_DIR] 或：& [-vspy] -e EVENT PROBLEM_DIR 或：& [-vspy] -d PROBLEM_DIR 或：& [-vspy] -x PROBLEM_DIR「%s」不是一般檔案「%s」不是正確檔名「comment」檔案空白'strata' 或 'bugzilla'「{0}」必須由 abrt 擁有。請執行「# chown -R abrt.abrt {0}」來修正此問題。(「%s」成功完成) (「%s」已離開，代碼 %u) (「%s」被訊號 %u 截殺) (二元檔，%llu 位元組)(請點擊此處以檢視或編輯)(無描述)--- 正在執行 %s ---您的評註並非隱私資訊。 它們可能被納入能夠公開查看的問題回報中。「reported_to」中額外 URL 的臭蟲追蹤器名稱已請求建立私人申請單，但未指定群組，請見 https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-tickets 瞭解更多資訊可能遺失適當的 debuginfo，或是核心傾印資料已損毀。等候來自 DBus Secret Service 的提示結果已達時限。加入 bugzilla 使用者至 [有此 ID 的臭蟲報告] 寄件副本清單加入程式名稱至記錄中正將 %s 加入寄件副本 (CC) 清單正加入外部 URL 至臭蟲 %i將外部 URL 加入議題中正加入附件至臭蟲 %i將附件加入議題 %i 中正添加評註至案例「%s」加入額外的 CC %s 到臭蟲回報中正新增評註至臭蟲 %d將新評註加入議題 %d 中「auth」key 中包含額外檔案AlmaLinux 臭蟲追蹤器伺服器Bugzilla 伺服器的位址Red Hat 支援入口的電子郵件地址uReport 網路服務的位址將您的 Bugzilla 登入資訊加入已回報臭蟲的寄件副本清單中。將您的電子郵件加入 Bugzilla 臭蟲的寄件副本清單中進階允許對 ureport 伺服器的不安全連線AlmaLinux 臭蟲追蹤器AlmaLinux 臭蟲追蹤器 URLAlmaLinux 臭蟲追蹤器帳號密碼AlmaLinux 臭蟲追蹤器帳號使用者名稱AlmaLinux 臭蟲追蹤器專案AlmaLinux 臭蟲追蹤器專案版本在本機分析問題並將問題資料資訊匯出到文字檔案中在本機分析問題並透過電子郵件傳送資訊於本機分析問題並透過 SCP 或 FTP 上傳資料附加附加新報告或覆寫舊的報告。附加至或覆寫 FILE封存檔案已建立：「%s」尋求 Red Hat Suppot 協助附加 FILE [至含有此 ID 的臭蟲報告]附加 FILEs [到此 ID 的議題]附加檔案正在附加「%s」至案例「%s」正附上更好的追蹤資料附上「%s」檔案到 %s 議題中正附加問題資料至案例「%s」「%s」的值錯誤：%s欲上傳至的基礎 URL基本詳盡Bug %i 已 CLOSED (關閉) 為 DUPLICATE (重複項目)，不過它沒有 DUP_IDBug %i 已 CLOSED (關閉)，不過沒有 RESOLUTION (解決方案)臭蟲已回報過：%iBug.search(quicksearch) 回傳值未包含成員 'bugs'BugzillaBugzilla URLBugzilla 帳號密碼Bugzilla 帳號使用者名稱Bugzilla 找不到臭蟲 %d 的親代Bugzilla 產品Bugzilla 產品版本設定(_O)將來自 {0} 的檔案放入快取，這是由 {1} 所產生無法透過 DBus 於路徑「%2$s」介面「%3$s」呼叫方法「%1$s」：%4$s無透過 DBus 連接至名稱「%s」路徑「%s」介面「%s」：%s沒有 URL 則無法繼續若沒有 %s 的電子郵件位址則無法繼續無法沒有登入資訊就繼續無法沒有密碼就繼續無法複製「%s」：%s無法為事件「%s」建立祕密項目：%s無法建立暫存目錄於 無法建立暫存檔於 無法刪除「%s」：%s無法刪除：「%s」無法從問題資料判定 Bugzilla 產品。無法從問題資料判定 RH 支援產品。無法停用 async 下載，輸出可能包含人為瑕疵！無法停用軟體庫「{0!s}」：{1!s}無法從「{0}」中抽出檔案：若要瞭解更多資訊請見「{1}」無法抽出軟體包「{0}」找不到 {0} 個 debuginfo 檔案的軟體包無法產生堆疊追蹤描述 (無崩潰的執行序？)無法取得 Bugzilla ID，因為此問題尚未回報至 Bugzilla。無法取得 MantisBT ID，因為此問題尚未匯入 MantisBT。無法 lseek「%s」無法開啟「%s」無法開啟「%s」以寫入。請選擇其他檔案：無法開啟「%s」問題目錄。無法解析回溯資料：%s無法讀取「%s」無法移除「{0}」：{1}無法移除 {0}，可能包含錯誤記錄無法設置 {0}: {1}，改停用無法上傳「%s」，容量過大（%llu 位元組）無法寫入「{0}」：{1}取消被使用者取消。無法根據「comment」檔案附上評註因為事件名稱無效而無法檢查回溯資料評等無法複製檔案「{0}」：{1}無法執行 vi：$TERM、$VISUAL 以及 $EDITOR 尚未設置目錄訊息 id檢查 SSL 金鑰是否有效檢查是否有重複檢查是否有提示清除搜尋列以查看安全性敏感字詞清單。關閉 %i 臭蟲因其為 %i 臭蟲的重複回報正在壓縮資料組態檔組態組態檔組態檔 (可能會提供多次)uReport 的組態檔確認欲回報的資料聯絡電子郵件位址開立新的 Red Hat Support 案例 - 我願意讓 Red Hat Support 聯絡我在 DIR 中建立 reported_to建立新的臭蟲回報正在建立新案例建立新議題組態檔沒有提供憑證。自訂D-Bus Secrets Service ReadAlias('%s') 方法失敗：%s除錯定義 SYSLOG_IDENTIFIER systemd 日誌欄位詳情顯示版本並離開您仍然想建立 RHTSupport 的申請單嗎？您想要停止等候並繼續回報，但卻未適當載入組態？可能有相關的文件：不要再問我不要儲存密碼下載程序已被使用者中斷正在下載 ({0} / {1}) {2}：{3:3}%下載軟體包 {0} 失敗下載 {0:.2f}Mb，已安裝大小：{1:.2f}Mb。是否繼續？將問題目錄傾印至 systemd 日誌欄位%s 的電子郵件位址尚未指定。您是否想要馬上設定？如果不是，則使用「%s」ABRT 伺服器可用來通知您有關消息與更新的電子郵件位址電子郵件已送往：%s錯誤HTTP POST 有錯誤，HTTP 碼：404（找不到），URL：「%s」「%s」的 MantisBT 請求中有錯誤「%s」的 MantisBT 請求中有錯誤：%s於「%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}'擷取 metadata 時發生錯誤：'{0!s}'設置軟體庫時遭遇錯誤：「{0!s}」錯誤：%s錯誤：無法創建 cachedir，只得離開找不到必要元素「%s」，無法繼續事件「%s」要求傳送可能具敏感資訊資料的許可。 您是否要繼續？事件「%s」要求傳送可能具有敏感資訊資料的許可。您是否要繼續？事件範例： ftp://[user[:pass]@]host/dir/[file.tar.gz] scp://[user[:pass]@]host/dir/[file.tar.gz] file:///dir/[file.tar.gz]專家模式匯出問題資料以供手動回報將問題資料資訊匯出到文字檔案中從 {0} 抽取 cpioFTP 代理提交問題時失敗無法加入 MantisBT 議題備註：「%s」無法附加檔案：「%s」無法關閉 TAR 寫入器建立新臭蟲回報失敗。無法建立新議題：「%s」無法傾印 XML 節點。無法完結 TAR 封存檔無法從問題資料格式化重複評註無法格式化問題資料無法根據問題資料生成微報告無法從「/etc/os-release」中取得 'REDHAT_BUGZILLA_PRODUCT'。無法取得 MantisBT 議題：「%s」無法為「%s」專案取得自訂欄位無法根據名稱取得專案 ID無法開啟 TAR 寫入器無法讀取「/etc/os-release」取得 Bugzilla 產品。無法儲存「%s」檔案無法搜尋 MantisBT 重複議題：「%s」無法根據重複雜湊碼搜尋 ManitsBT 議題：「%s」無法上傳 uReport 到「%s」伺服器無法以 curl 上傳 uReport 至伺服器「%s」：%s即使此問題已經回報過，仍然回報此問題為新案例格式化檔案為電子郵件格式化檔案為目錄訊息格式化檔案正為重複項目格式化檔案正為初次評註格式化檔案在臭蟲歷史中尋找同樣的評註，而不是新增評註議題歷史紀錄中找到相同評註，不會再加新評註群組HTTP 代理HTTPS 代理這問題是怎麼發生的（詳述各步驟）？如何再次產生此問題？任何說明可以幫助我們診斷問題？請儘可能使用英文。此問題的重現方式（一列寫下一個步驟）？此問題的可重現頻率？您希望如何回報問題？我知道重現這個問題的方法我不知道這問題是什麼造成的我第一次遇到這個問題我已檢視資料，並同意提交資料(_A)如果您已回報了遠端伺服器，請確定您已移除所有私人資料 (例如使用者名稱與密碼)。回溯資料、指令列、環境變數等通常是需要檢視的東西。若您希望將問題回報至不同的目的地，請蒐集額外資訊，或提供較詳盡的問題描述、重複回報程序，並按下「下一步」。若您想要更新設定組態並嘗試再回報一次，請開啟應用程式選單中的 「偏好設定」項目，並且在套用組態修改後點按「重複」按鈕。忽略無效的「%s」報告結果 ISO 日期忽略沒有 scheme 和主機名稱的 URL包含正在初始化軟體包管理員無效的布林值「%s」無效的重複格式檔案：「%s」無效的格式檔案：%s無效的輸入，離開程式。無效的數字「%s」無效的密碼或登入資訊。無效的密碼或登入名稱。請輸入「%s」的密碼：無效的密碼或登入資訊。請輸入您的 Red Hat 登入資訊：無效的 utf8 字元「%c」議題 %i 已 CLOSED（關閉）為 DUPLICATE（重複項目），不過它沒有 DUP_ID議題 %i 已 CLOSED（關閉），不過沒有 RESOLUTION（解決方案）項目「%s」已存在，無法修改Kerneloops URLKerneloops.org深入瞭解組態中受限存取的相關資訊正將 ABRT 崩潰統計數據記錄與連絡電子郵件連結：「%s」正將 ABRT 崩潰統計數據記錄與此案例連結列出可能的事件 [以 PREFIX 作為開頭]記錄檔紀錄至 syslog紀錄器登入 Bugzilla 於 %s登出登入資訊未由組態提供。請輸入您的 RHTS 登入資訊：從軟體庫中尋找所需軟體包查找 Mantis BT 中的相似問題查詢 bugzilla 中是否有類似問題看似損毀的 xml 回應，因為「%s」成員遺失。Mailx格式不良的 Bugzilla「%s」URLMantisBT「%s」的 URL 格式不良。MantisBT 找不到議題 %d 的上層MantisBT 不包含「%s」自訂欄位，而回報程式必須要有此欄位才能正常運作。您是否仍想要建立新議題？訊息主旨遺失必要的值遺失需要的項目：「%s」N名稱記錄檔的名稱需要可寫入的目錄，但「%s」並不是可寫入的目錄。將它移到「%s」並在移動後的資料中操作？環境變數「uReport_ContactEmail」與組態選項「ContactEmail」皆未設定新的臭蟲 ID：%i沒有可用的描述沒有可用的回報程式非互動式：不詢問問題，假定皆回答「是」備註不包含評等僅通知 (不要將回報標記為已送出)確定確定在接下來的畫面上，您將會被要求描述問題如何發生、選擇如何分析問題 (若有需要)、檢視蒐集的資料，以及選擇問題該向哪回報。請按下「下一步」以繼續進行。Oops 伺服器 url輸出檔案要下載的軟體包：{0}密碼密碼未由組態提供。請輸入「%s」的密碼：請加入您目前對該問題已知的詳盡描述。這裡可以輸入很多內容。請輸入問題資料要匯出的位置 URL (scp、ftp 等)：請輸入「%s//%s@%s」的密碼：請輸入密碼以上傳：請輸入密碼，身分為請輸入「%s//%s」的使用者名稱：請輸入您的 MantisBT 登入資訊：請提供問題的簡短描述，並請列出重現該問題的步驟。請提供如何重現您所見問題的逐項步驟。請將此問題回報給 ABRT 專案開發者。在問題回報之前，請先檢視資料。根據回報者的選擇而定，您提供的資料最後可能供大眾公開檢視。請試著使用指令："debuginfo-install %s" 來手動安裝 debugifo，並再重試一次。拜託，請輸入 %s 的電子郵件位址：偵測到敏感資料，請依自己的想法編輯回報並移除敏感資訊。偏好設定列印具給定 DUPHASH 的 BUG_ID當從鏡像站下載資料時遭遇問題「{0!s}」：'{1!s}'。改嘗試下一站問題描述問題細節問題目錄使用 AlmaLinux 基礎設施處理 C/C++ 崩潰使用 Fedora 基礎設施處理 C/C++ 崩潰使用 Red Hat 基礎設施處理 C/C++ 崩潰問題使用 AlmaLinux 基礎設施處理 Java 例外使用 Fedora 基礎設施處理 Java 例外使用 Red Hat 基礎設施處理 Java 例外使用 AlmaLinux 基礎設施處理 JavaScript 例外使用 Fedora 基礎設施處理 JavaScript 例外使用 Red Hat 基礎設施處理 JavaScript 例外使用 AlmaLinux 基礎設施處理 X 伺服器問題使用 Fedora 基礎設施處理 X 伺服器問題使用 Red Hat 基礎設施處理 X Server 問題使用 AlmaLinux 基礎設施處理內核心崩潰使用 Fedora 基礎設施處理內核心崩潰使用 Red Hat 基礎設施處理內核心崩潰問題使用 AlmaLinux 基礎設施處理 kerneloops使用 Fedora 基礎設施處理 kerneloops使用 Red Hat 基礎設施處理 kerneloops 回報使用 AlmaLinux 基礎設施處理問題使用 Fedora 基礎設施處理問題使用 Red Hat 基礎設施處理問題使用 AlmaLinux 基礎設施處理 python 3 例外使用 Fedora 基礎設施處理 python 3 例外使用 AlmaLinux 基礎設施處理 python 例外使用 Fedora 基礎設施處理 python 例外使用 Red Hat 基礎設施處理 python 例外使用 Fedora 基礎架構處理回報使用 Red Hat 基礎設施處理回報處理中尚未開始處理處理完成處理失敗。處理完成，請繼續下個步驟。處理完成。處理中斷：若無可寫入的目錄便無法繼續。問題處理失敗。這可能有許多原因，下列三種最為常見： ▫ 網路連線問題 ▫ 問題資料損毀 ▫ 設定組態無效已取消處理處理因問題無法回報而中斷。處理中...提供額外資訊退出RH 入口 URL收件者收件者電子郵件地址Red Hat 客戶支援服務Red Hat 客戶密碼Red Hat 客戶使用者名稱回報後移除 DIR在回報後移除 PROBLEM_DIR正在移除 {0}重復回報上傳器回報臭蟲給 Fedora 維護者回報臭蟲給 Red Hat Bugzilla回報臭蟲給 Red Hat 客戶入口回報給 AlmaLinux 臭蟲追蹤器回報至 Bugzilla 臭蟲追蹤器回報至 Fedora回報至 Red Hat Bugzilla向 Red Hat 支援部門回報已回報：回報回報已完成。您現在可將此視窗關閉。限制存取限制所建立的 bugzilla 申請單之存取狀況，僅讓特定群組的使用者可以檢視 (請見進階設定瞭解更多細節)限制報告的存取限制僅有群組可存取限制只讓特定群組存取 <a href="https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-tickets">?</a>檢視資料僅執行這些事件SOAP：因為無節點或無子名稱而無法加入新的子節點。SOAP：無法加入方法參數。SOAP：因為要求的項目遺失而無法加入新議題的參數。SOAP：無法加入新議題參數。SOAP：無法建立 SOAP 字串，因為函式引數無效。SOAP：無法在自訂欄位中建立新屬性。SOAP：無法建立新屬性。SOAP：無法建立新的 XML 子項。SOAP：無法建立 XML 文字閱讀器。SOAP：無法傾印 XML 節點。SOAP：因為沒有節點而無法取得子元素。SOAP：因為沒有上層而無法取得子節點。SOAP：因為沒有節點而無法取得下個元素。SOAP：無法取得 XML root 元素。SOAP：無法解析 XML（和議題相關）。SOAP：無法解析 XML（依據名稱深度搜尋值）。SOAP：無法在建立請求時解析 XML。SOAP：無法解析 XML。SOAP：無法列印 SOAP 字串。SSH 私鑰檔SSH 公鑰檔SSH 私鑰檔SSH 公鑰檔儲存成文字檔搜尋無法使用祕密服務，不會儲存您的設定！選取要執行的工作流程：選取要執行的事件：請選取回報此問題的方式傳送二元資料傳送類似核心傾印的二元檔案透過電子郵件傳送問題資料傳送給 kernel oops 追蹤器透過電子郵件傳送寄件者寄件者電子郵件地址正傳送 %s 到 %s//%s正在傳送 ABRT 崩潰統計數據正在傳送通知用電子郵件給：%s傳送電子郵件...傳送 ureport 至 FAF 伺服器敏感字詞伺服器端以錯誤回應：「%s」設定 FTP 所要使用的代理伺服器設定 HTTP 所要使用的代理伺服器設定 HTTPS 所要使用的代理伺服器正在設置軟體庫顯示記錄顯示密碼若沒有已知重現方式將使崩潰問題難以診斷，還請提供您所遭遇問題之詳盡描述。大小：指定 Bugzilla 產品（沒有 -h 則忽略）指定伺服器 URL若您需要的產品與 /etc/os-release 中指定的不同，才請您指定此參數若您需要的產品版本與 /etc/os-release 中指定的不同，才請您指定此參數只有在您需要使用與 /etc/os-release 中不同的專案時才指定此項目只有在您需要使用與 /etc/os-release 中不同的專案版本時才指定此項目狀態：%s%s%s %s/show_bug.cgi?id=%u狀態：%s%s%s %s/view.php?id=%u字串似乎不是日期：「%s」主旨當建立新案例時提交 <a href="https://access.redhat.com/articles/642323">micro-report</a>。提交匿名崩潰報告提交匿名崩潰報告 - 我不希望 Red Hat Support 聯絡我提交 uReport在提交 uReport 之前建立新案例傳送 oops 報告至 %s成功建立 %s尚未判定 MantisBT 專案。URL「%s」不存在 (伺服器給予 404 錯誤)回溯資料不完整，請確認您已提供能夠重現問題的步驟。回溯資料可能無法幫助開發者診斷臭蟲所在。崩潰的程式是由「%s」發行。您是否希望將問題回報給 Red Hat Support？日期：「%s」有無法辨識的後綴：「%s」日期：「%s」超出 UNIX 時間戳記範圍議題僅有可存取「私有議題」的使用者能存取無法回報問題，因為有資料無效。「%s」檔案並不包含數字。問題僅出現過一次，而且不清楚該如何重現這個問題。請確認您可以提供更多詳細資訊給我們的 Support Team。您是否要繼續並開立新的支援案例？「%s」程式似乎不是由 Red Hat 提供。您是否要將問題回報給 Red Hat Support？回報結果「%s」遺失 URL。報告已附加至 %s報告已儲存至 %s「%s」給予的回應為無效格式「%s」的伺服器目前無法處理請求 (取得錯誤碼 503)於「%s」的伺服器遭遇內部錯誤 (得到 500 錯誤)於「%s」的伺服器以錯誤回應：「%s」此問題沒有指派 uReport。此問題已被回報過。此問題尚未回報至 Bugzilla「%s」，而不是設定中的 Bugzilla「%s」。此問題已經回報給 MantisBT「%s」，而這和設定的 MantisBT「%s」有出入。此問題尚未回報到「%s」。此問題尚未回報至 Bugzilla。這個問題持續發生此問題不應回報 (這很類似已知問題)。%s這個問題已經有回報給 MantisBT（請見「%s」）。您是否仍希望建立新的議題？申請單/專案 ID偵測到「%s」的回應中其類型並不相符URL無法於 bugzilla URL「%s」中找到臭蟲 ID無法從 bugzilla URL「%s」解析臭蟲 ID無法解析來自「%s」ureport 伺服器的回應「%s」傳來未預期的 HTTP 回應：%d解壓縮失敗，放棄下載……不受支援的選項類型可能有幫助的更新：上傳 FILEs [至含有此 ID 的案例]以 tar.gz 檔案上傳 (透過 FTP/SCP/...)透過 SCP 或 FTP 上傳資料到遠端目的地將問題資料上傳至伺服器已上傳：%llu / %llu 位元組未指定 URI 或請求。用法：使用 HTTP 核對認證使用者客戶端身份核對若您不希望 URL 中有密碼請使用此欄位若您不希望 URL 中有使用者名稱請使用此欄位使用此欄位指定 SSH 私鑰檔使用此欄位指定 SSH 公鑰檔使用者名稱使用者名稱正使用 Bugzilla ID「%s」使用 MantisBT ID「%s」使用預設「%s」產品值驗證 SSL檢視或編輯文字檔案警告，私人請單群組已指定成 cmdline 引數，忽略環境變數與組態設定警告：快取目錄「{0}」中的可用空間不足 (剩下 {1:.2f}Mb)。是否繼續？警告：暫存目錄「{0}」中的可用空間不足 (剩下 {1:.2f}Mb)。是否繼續？關注 Bugzilla 臭蟲關注已回報過的臭蟲當建立臭蟲回報時，亦請附加二元檔案您希望將含有報告的 tarball，以 login:password@url 格式上傳到何處工作流程您正試著將檔案複製到檔案自身之上您可以註冊 bugs.almalinux.org 新帳號 <a href="https://bugs.almalinux.org/signup_page.php">here</a>您可建立 bugzilla.redhat.com 帳號 <a href="https://bugzilla.redhat.com/createaccount.cgi">here</a>您選擇的數目超出範圍您已請求您的資料只能讓特定族群的人士存取，而這個臭蟲又是另一個臭蟲回報的重複案例：%s/%u 我們對於重複臭蟲的回報作法，是將新的評註內容加到源初臭蟲回報下，但這樣就無法限定只讓特定人士存取評註內容。您是否想要開立新回報，並將這臭蟲回報以源初臭蟲回報的 DUPLICATE 重複項目關閉？否則，臭蟲回報程序即將終止。在繼續進行之前，您必須填入相關資訊...您需要指定要加入附件的 uReport 其 bthash。您需要指定臭蟲 ID、聯絡電子郵件、評註或全部您的輸入無效，因為：您的問題似乎起因於 %s %s 您的問題似乎由下列問題之一所導致： 取消(_C)關閉(_C)前進(_F)否(_N)確定(_O)開啟(_O)儲存(_S)停止(_S)是(_Y)附上 DATA 作為 ureport 附件 ATTACHMENT_TYPE (僅用於 -l|-L)附上 RHBZ 臭蟲 (需要 -a|-A，但與 -B 衝突)附上前次回報結果的 FIELD [URL] 資料 (需要 -a|-A、-r 或 -T，但和 -l 衝突)附上前次 reported_to 中的 RHBZ 臭蟲回報 (需要 -a|-A，但與 -b 衝突)附上簡短文字 (需要 -a|-A，但和 -D 衝突)取自評註附上簡短文字 (需要 -a|-A，但和 -d 衝突)從 reported_to 附加到 bthash (與 -a 衝突)附上值 (需要 -a|-A 和 -T，但和 -L 衝突)要加入為附件的 uReport 之 bthash (與 -A 衝突)無法取得「%s」的祕密值：%s無法回報聯絡電子郵件位址 (需要 -a|-A，但與 -E 衝突)取自環境變數或組態檔的聯絡電子郵件位址 (需要 -a|-A，與 -e 衝突)資料ef檔案gzip 以 %d 狀態離開gzip 被 %d 訊號截殺gzip 程序失敗由其他程序鎖上非問題目錄拒絕許可uReportuReport 伺服器 URLUID 值無效：「%s」在 reported_to 尋找 FIELD 時使用 REPORT_RESULT_TYPE (僅能用於 -L)y