grthtrhthjhtyjytjytkergtrhtrjytjerhrfh4:24 29/09/2026\)%22;3A8' >4>Q>Q`>> > >0> ?? (?2?(D?6m???-?$ @2@>G@[@AiB_ CGlCD*qFxGHHHHHTI\I{IIIIII? JaJJ>JJDKUK23LfLLLLLL M 'MHMeM'M'MM%MN=3N+qNN+NNN&O')OQO%oORO:O>#PbP,iPPPP"P$ Q 1Q5?Q0uQQQQ#Q!R8RNR TR3_R*RRBRS &S3SMS'hSSS S$S@SA+T2mTT*TTU#U-7U&eUUUU3U5 VA?V'V>VV+W80WQiWQW XX8.XgXXXX0XX.YFY`YgY)zY;YY5Y2ZEZ\ZtZAZ%ZZ [ [[,-[Z[y[[Q[[\%\9\.N\}\7\\.\\\0]\C]']]]]$ ^1^;P^,^^^R_k__8_!_%_-`@6`"w`>`0`C a%NaAta7a/a#b"Bb&eb b#b1bXbXEccc +d,7d2ddd d d'dee:e"Veyee4ee4f?9f"yf,f"ff9g@g/Yg0g+g9g8 hYhxh#hh#h?hAn6o;8oto;o,o.o(p7p7Fp=~p2p.pq 'q5q?7<w=23% Yd5ڂB2A W*e „̄ބ,"G jw~" '҅3.Nm~ Ά ؆6Rl| "'JֈI$FPk(I7/&g,'74:4o%1ʋ=2:m"Ԍ>Up!܍'.="R#uʎ$ڎ$%$&Jq 7/=mS[ԐS0[$ &&MqUǒP6)Eo-7ғQ @\b,.-J\[t&\)E@-0n/'Ϙ``X+/F4`{bܚ?9N*-4&&Ah#'œ6#!Ec9:-2,` Ξ qMKП/K*N i)ssw#5C4yA$*9@zH3c.I5ܦB7U7/ŧ":+afȨͨϨѨ֨3K]exPE$ҷD۷ , 5)A kw &5ȸ,.,[BhMһTq?Ƽv.X y"A(_j<B3A1s"#=#a%) ,BJ/0&/)V &E64Ez*%* K6X0%#BVm t2+%7> GTj*"BFI<% 'C(Z166Q!7-6,CcC<Lk+.)AH)X3:'=e0{-  *3KjH' C3M.(NL fs&=*TDD;!?&a3G#D(1mJ#D7S%" 0 &QXxW)0 $* *5)Hr0B'^?"*"78U)2*7/0g!$* !&DHK 3$!'*!R2tY,(*Ia7@9'a\~M$)N]0l=0, 9F Wd ~A@"-%PAv,!. < }O+,-Hv):W>w3" ,%<"bK*-]*XQ S]B} 0-.F/u,-5263i523/:,j-?6-<)j&'3*1B.t/&' ", ?L'\5|3'  &0F[p! &(76`$%!5 Q ^9h9 O9Ly_ O%L@r%F4 U*u*!==+:i&0?3<p% 9M"m*$!4 MWm$ ! #0$T%y  i 35=sMPS&\z%!(HrOE!&0%W}-N1* Z\ 0 , ? JU  gR    ' B4 <w + & ! N) Qx $ $ A-XoP6*a,e26"!AZ1w240P kv>D) )J t ~ QYKU))O U$_m{!n*.CIr$12AP _kz U1 e;G2>0[3/" 7 QX /<DZXnb,K >opPw Wd ~~}69K&eeW4SDF2u<f` LTMOX7xvJ((N7.C wyA{V+ z;cuvG"nGX7:W]?:jMo <M4dOVa%#Q. '\q` ^13pR8Zh*j'-IX =.> *}FNT$H8(Y5B]9C,R%2_\"VB!;:_#kQ^EsinE @aDScH[lmlH/{C\|1P6JOy"I9 K)5[Yr0kJTR3&$>6'#&AfYx/?i30F!$EtL r-)Gz;*mtBN -%!=Ag@@bh s+5S gUP80[q,QU41<) LZ?U|=2/DZ+I & [-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 ------ Skipping %s --- No matching actions found for this event. 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 fileAttach crash data to an existing Red Hat support caseAttach the data to existing Red Hat support caseAttaching '%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 Red Hat Support case numberCan'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 %s login: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 %s login:Login 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 commands could be found for processsing the crashdump. No 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 customer case number to which you want to attach the data: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 Red Hat Support with crash detailsProvide 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 problems coming from unpackaged executables.Report to AlmaLinux Bug TrackerReport to Bugzilla bug trackerReport to FedoraReport to Red Hat BugzillaReport to Red Hat supportReport unpackaged problemsReported:ReportingReporting has finished. You can close this window now.Reporting is disabled because the generated backtrace has low informational value.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 Bugzilla (see '%s'). Do you still want to create a new bug?This 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 bugsWe found a similar Red Hat support case %s. Do you want to attach the data to the case? Otherwise, you will have to enter the existing Red Hat support case number.When 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: 2020-07-18 16:28+0000 Last-Translator: Charles Lee Language-Team: Chinese (Simplified) Language: zh_CN MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=1; plural=0; X-Generator: Weblate 4.1.1 & [-v] [-c CONFFILE] [-F FMTFILE] -d DIR or: & [-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 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]] 向 Bugzilla 报告问题。 这个工具读取 DIR。然后它会登录到 Bugzilla，并尝试找到 在 'Whiteboard' 中具有同一 abrt_hash:HEXSTRING 的 bug。 如果没有找到这样的 bug，则会创建一个新 bug。 DIR 的元素 将保存在 bug 中作为 bug 描述的一部分或附件，这取决于 其类型和大小。 反之，如果找到了这样的 bug，且被标记为 CLOSED DUPLICATE， 该工具会沿着重复链查找，直到发现标记为 non-DUPLICATE 的 bug。 此工具将为找到的 bug 添加一条新评注。 新提交或已修改的 bug 的 URL 将会打印到标准输出，并在 'reported_to' 元素中进行记录。 选项 -t 会将 FILEs 上传到 Bugzilla 网站已创建的 bug 中。 bug ID 将在 -d DIR 所指定的目录中获取。 若从未在 Bugzilla 中报告 DIR 中的问题数据，则上传会失败。 选项 -tID 会将 FILEs 上传到 Bugzilla 网站所指定 ID 的 bug 中。 -d DIR 会被忽略。 选项 -w 会在 bug 的 CC 列表中添加 bugzilla 用户。 选项 -r 会将 URL 字段设定为 reporter_to 元素中的最后一个前缀 为 TRACKER_NAME 的 url 。这个选项只有在提交新 bug 时起作用。 默认值为 'ABRT Server'。 若未指定，则 CONFFILE 默认为 & [-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 向 MantisBT 报告问题。 该工具读取目录，之后尝试根据自定义字段 'abrt_hash' 中查找 具有相同 abrt_hash 的问题。 如果这样的问题没有找到，那么将创建一个新的问题。 DIR 中的元素将依据它们的类型和大小，作为问题描述 或附件保存到问题中。 否则，如果找到了这样的问题并且其被标记为 CLOSED DUPLICATE， 此工具将会追踪重复链条直到找到一个标记为 non-DUPLICATE 的问题为止。此工具会在找到的问题中添加一条新评注。 指向新创建或者已修改问题的 URL 将会打印至标准输出并记录到 'reported_to' 元素中。 选项 -t 将会上传 FILEs 到 MantisBT 网站上已经存在的问题中。 问题 ID 将在选项 -d DIR 指定的目录中获取。 如果 DIR 中的问题数据从未报告至 MantisBT，上传将会失败。 选项 -tID 会将文件上传到 MantisBT 网站所指定 ID 的问题中。 -d DIR 会被忽略。 选项 -r 会将 URL 字段设定为 reporter_to 元素中最后一个 前缀为 TRACKER_NAME 的 url。该选项仅在提交一个新问题时适用。 默认值为 'ABRT Server'。 如果未指定，CONFFILE 默认为 未查出报告有更改 该报告已更新# 架构# 回溯 # 检查它是否包含任何敏感数据（密码等等）# 命令行# 组件# 核转储# 在下面描述此崩溃的发生环境# 可执行# 内核版本# 软件包# 崩溃原因# 操作系统的发行版本字符串# 来自根目录的操作系统发行版本字符串# 该字段为只读 # os-release 配置文件# 来自根目录的 os-release 配置文件$DATA_DIRECTORY/%s（二进制文件，%s）%llu字节，%u个文件& [-d] DIR 用来报告保存在指定目录下问题的新工具& [-v] --target TARGET --ticket ID FILE... 将 FILE 上传到 TARGET 中指定的 ticket。 这个工具是用来简化用户向 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] 将问题目录的压缩 tarball 问卷上传到 URL。 若未指定 URL，则请创建 tarball 于 & [-v] -d DIR [-o FILE] [-a yes/no] [-r] 向标准输出或 FILE 输出问题信息& [-v] [-c CONFFILE]... -d DIR 向 kerneloops.org（或类似）网站报告内核错误。 在 tarball 中不包括在 $EXCLUDE_FROM_REPORT 中 列出的文件名。 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 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] 上传微报告或者在微报告中添加附件 读取默认配置 & [-v] [-d DIR] [-m MESSAGEID] [-F FMTFILE] [-p NONE|ESSENTIAL|FULL] [-s SYSLOGID] 向systemd 系统日志汇报问题信息。 此工具将问题目录 DIR 细节以消息形式发送至日志。 如果MESSAGEID 已定义，本工具同时还会创建目录信息。 & [-vpdx] [-e 事件]... [-g GUI 文件] 问题目录 分析及报告保存在指定目录下问题的图形化工具& [-vsp] -L[前缀] [问题目录] or: & [-vspy] -e 事件 问题目录 or: & [-vspy] -d 问题目录 or: & [-vspy] -x 问题目录'%s' 不是普通文件'%s' 不是正确文件名'comment' 文件为空'strata' 或者 'bugzilla''{0}' 必须为 abrt 拥有。请运行 '# chown -R abrt.abrt {0}' 解决这个问题。('%s' 成功完成) ('%s' 以 %u 退出) ('%s' 被信号 %u 杀死) （二进制文件，%llu字节）（点击这里查看/编辑）（没有说明）--- 运行 %s ------ 正在跳过 %s --- 没有找到匹配此事件的动作。 您的评注并不是私密的。 它们将被包含在公开可见的问题报告中。''reported_to'中附加 URL 所指 Bug 跟踪系统的名字已请求创建一个私密工单，但是尚未指定可访问用户组。请访问 https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-tickets 以了解更多信息可能丢失了正确的出错信息或者内核转储被污染。等待 DBus 安全服务请求结果已经超时。添加 Bugzilla 用户到[可选指定 ID 的 Bug]抄送列表上在日志中添加程序名正在添加 %s 至抄送列表添加外部 URL 至 Bug %i在问题中添加外部　URL在 Bug %i 中添加附件在问题 %i 中添加附件添加评注至案例 '%s'在 bug 报告中添加额外 cc %s正在向 Bug %d 中添加新评注向问题 %d 添加新评注'auth' 密钥中包含的附加文件AlmaLinux Bug 跟踪系统服务器地址Bugzilla 服务器地址Red Hat 支持门户网站地址uReport 网络服务器地址添加您的 Bugzilla 账户到已经汇报 Bug 的抄送列表。添加您的电邮到 Bugzilla Bug 抄送列表高级允许使用非加密链接到 uReport 服务器AlmaLinux Bug 跟踪系统AlmaLinux Bug 跟踪系统 URLAlmaLinux Bug 跟踪系统帐户密码AlmaLinux Bug 跟踪系统帐户用户名AlmaLinux Bug 跟踪系统项目AlmaLinux Bug 跟踪系统项目版本本地分析该问题并将该问题数据信息导出为文本文件在本地分析问题并通过电子邮件发送信息本地分析问题并通过 scp 或 ftp 上传数据附加附加新报告或者覆盖已有报告。附加到，或者覆盖 FILE生成归档：'%s'向红帽支持寻求帮助附加 FILE [可选指定 ID 的 Bug]添加 FILE [至使用这个 ID 的问题]附加文件附加崩溃数据到已存在的 Red Hat 支持案例附加数据到已存在的 Red Hat 支持案例在案例 '%s' 中附加 '%s'附加更好的 backtrace将文件 '%s' 附加到问题 %s 中添加问题数据至问题单 '%s''%s' 值错误：%s要上传的基本 URL基本详细显示Bug %i 因为重复被关闭，但它没有 DUP_IDBug %i 已关闭，但还没有解决方案该 Bug 之前已经被汇报至：%iBug.search(quicksearch) 返回值未包含成员 'bugs'BugzillaBugzilla URLBugzilla 账户密码Bugzilla 账户用户名Bugzilla 无法找到 Bug %d 的父类 BugBugzilla 产品Bugzilla 产品版本配置（_O）从 {0} 缓存来自 {1} 的文件无法通过 DBus 调用方法 '%s' 在路径 '%s' 接口 '%s': %s无法通过 DBus 连接至名称 '%s' 路径 '%s' 的接口 '%s' : %s在没有 Red Hat 支持案例编号的情况下无法继续需要 URL 才可继续需要 %s 的电子邮箱才可继续需要登录名才可继续没有密码则无法继续无法复制 '%s'：%s无法为事件 '%s' 创建保密项: %s无法创建临时目录于 无法创建临时文件于 无法删除 '%s'：%s无法删除：'%s'无法从问题数据中确定 Bugzilla 产品。无法从问题数据中确定 Red Hat 支持产品。无法禁用异步下载，输出可能存在假象！无法禁用仓库 '{0!s}': {1!s}无法从 '{0}' 中提取文件。详情请查看 '{1}'无法提取软件包 '{0}'无法为 {0} debuginfo 文件找到软件包无法生成堆栈跟踪描述 (没有崩溃线程？)无法取得 Bugzilla ID 因为该问题尚未汇报至 Bugzilla。无法取得 MantisBT ID 因为该问题尚未汇报至 MantisBT。无法定位 '%s'无法打开 '%s'无法打开 '%s' 进行编写。请选择另一个文件：无法打开问题 dir '%s'。无法解析回溯：%s无法读取 '%s'无法删除 '{0}'：{1}无法删除 {0}，可能包含错误记录无法设置 {0}：{1}，禁用无法上传 '%s'，它太大（%llu 字节）无法写入 '{0}': {1}取消用户取消。无法添加 'comment' 文件中的评注由于无效的事件名，无法检查回溯评级无法复制文件 '{0}': {1}无法运行 vi：尚未设置 $TERM、$VISUAL 和 $EDITOR目录信息 id查看 SSL 密钥是否可用正在检查该问题是否已经汇报检查是否有提示清空搜索栏查看安全性敏感词列表。将 bug %i 作为 bug %i 的重复 bug 关闭压缩数据配置文件配置配置文件配置文件（可在任意时间给出）uReport 的配置文件确认要上传的汇报数据联系人电子邮件地址生成新的红帽支持问题单 - 希望红帽支持团队与我联络在 DIR 中创建 reported_to正在创建新 Bug创建一个新个案生成新问题配置中未提供证书。自定义DBus 保密服务 ReadAlias('%s') 方法失败：%s除错设置 systemd 日志 SYSLOG_IDENTIFIER 字段详情显示版本并退出您还想生成 RHT 支持 ticket 吗？您想要停止等待并在未正确载入配置的情况下继续汇报吗？可能相关的文档： 不再询问不要保存密码用户取消下载下载（{1} 中的 {0}）{2}：{3:3}%下载软件包 {0} 失败正在下载 {0:.2f}Mb，已安装：{1:.2f}Mb。继续吗？将问题目录导出到 systemd 日志区未指定 %s 的电子邮箱。您想要现在制定吗？如果不，将使用 '%s'ABRT 服务器用来向您发送新闻和更新的电子邮件地址已发送电子邮件至：%s出错HTTP POST 出错，HTTP 代码：404 (Not found)，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}'检索元数据出错：'{0!s}'设置程序库出错：'{0!s}'错误：%s错误：无法创建缓存目录，正在退出缺少重要元素 '%s'，无法继续事件 '%s' 请求允许发布可能包含敏感数据的文件。 您想要继续吗？事件 '%s' 请求允许发送可能包含敏感数据的文件。您想要继续么？事件Examples: 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 写入程序失败创建新 Bug 失败。生成新问题 '%s' 失败转储 xml 节点失败。完成 TAR 归档失败从问题数据格式格式化重复评注失败格式化问题数据失败从问题数据生成微报告时失败从 '/etc/os-release' 获取 'REDHAT_BUGZILLA_PRODUCT 失败。获取 MantisBT 问题 '%s' 失败为 '%s' 项目获取自定义字段失败从名称中获取项目 id 失败打开 TAR 写入程序失败读取 '/etc/os-release' 获取 Bugzilla 产品失败。保存文件 '%s' 失败搜索 MantisBT 重复问题失败：'%s'根据 duphash 搜索 MantisBT 问题失败：'%s'将 uReport 上传到服务器 '%s' 失败无法使用 curl 上传 uReport 至服务器 '%s'：%s即使已经报告过该问题依然强行报告将文件格式化为新问题单正在为电子邮件格式化文件正在格式化用于目录信息的文件格式化文件用于副本格式化文件用于初始评注如果在 Bug 历史记录中找到相同的评注则不要再添加在该问题历史记录中找到相同的评注，不再添加新的评注组HTTP 代理HTTPS 代理这个问题是如何发生的（具体步骤）？怎样才可以重现？是否有其他可帮助诊断该问题的附加评注？请尽量使用英语。如何重现这个问题（每行一个步骤）？这个问题的可重现性如何？您希望如何报告该问题？我可以重现这个问题我不知道造成这个问题的原因我是第一次遇到这个问题我已经检查了数据并且同意提交（_A）如果您是要向远程服务器报告，请确定删除所有私人数据（不如用户名和密码）。Backtrace、命令行、环境变量是检查所需的常规项目。如果您要向不同的地点报告这个问题、收集附加信息或者更好地描述这个问题并重复报告过程，请按“前进”。如果要更新配置并尝试再次报告问题，请打开应用程序菜单中的 首选项， 并在应用配置更改后，点击 重新报告 按钮。忽略报告结果 '%s' 的无效 ISO 日期将忽略没有方案和主机名的 URL包括初始化软件包管理器无效的布尔值 '%s'无效重复格式文件：'%s无效格式文件：%s无效输入，正在退出。无效的数字 '%s'无效密码或登录。无效的密码或登录名。请输入 '%s' 的密码:无效密码或登录信息。请输入您的 %s 登录信息：无效密码或登录。请输入您的 Red Hat 登录：无效的 utf8 字符 ‘%c'问题 %i 已作为重复（DUPLICATE）问题关闭（CLOSED），但它没有 DUPLICATE_ID问题 %i 已关闭（CLOSED），但并未提供解决方案（RESOLUTION）项目 '%s' 已存在且不可修改Kerneloops URLKerneloops.org了解更多有关配置中限制访问的信息将 ABRT 崩溃统计记录与联系电子邮件关联：'%s'将 ABRT 崩溃统计记录与该问题单关联列出可能的事件【以 PREFIX 开头】日志文件记录至 syslog日志程序在 %s 登录到 Bugzilla正在退出配置中未提供登录信息。请输入您的 %s 登录信息:配置中未提供登录信息。请输入您的 RHTS 登录名:在库中查找所需软件包在 MantisBT 中查找类似问题正在 Bugzilla 中寻找类似问题看起来象是崩溃的 xml 响应，因为缺少 '%s' 成员。Mailx连接至 Bugzilla '%s' 的 URL 不规范。MantisBT '%s' 中的畸形 url。Bugzilla 无法找到问题 %d 的上级问题MantisBT 不包含自定义字段 '%s'，必须有该字段报告程序方可实现全部功能。还要继续生成新问题吗？信息标题缺少必需值缺少必要项: '%s'N名称日志文件名称需要可写入的目录，但 '%s' 不可写入。需要将其移动到 '%s'，并在移动后的数据中进行操作吗？环境变量 'uReport_ContactEmail' 和配置选项 'ContactEmail' 都未设置新 Bug id：%i未找到处理此核心转储的命令。 没有可用描述没有可用的报告程序无互动：不要提问，假设为“是”备注中不包含分级仅通知(不将报告标记为已发送)确定确定在下面的页面中，会询问您该问题是如何发生的，选择如何分析该问题（如果有必要），查看收集的信息，并选择向哪里报告该问题。点击“前进”继续。错误汇报服务器 URL输出结果文件要下载的软件包：{0}密码配置中未提供密码。请输入用于 '%s' 的密码:请添加有关您所遇到问题的详细描述。在这里可以输入大量内容。请输入要导出问题数据的 URL（scp、ftp 等等）：请输入您想附加数据的客户案例编号：请为 '%s//%s@%s' 输入密码：请输入密码以便上传：请输入密码请为 '%s//%s' 输入用户名称：请输入您的 MantisBT 登录：请提供该问题之简短描述，并包括您重现此问题的步骤。请提供用来重现此问题的步骤。请报告此问题给 ABRT 项目开发者。请在报告前检查数据。取决于选择的报告程序，内容可能会公开可见。请尝试使用命令: "debuginfo-install %s" 手动安装除错信息并再次尝试。请输入 %s 的电子邮箱：探测到可能的敏感数据，请根据需要编辑该报告并将其删除。首选项打印具备 DUPHASH 的 BUG_ID从镜像: '{1!s}' 下载时发生问题 '{0!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 服务器问题使用 AlmaLinux 基础架构处理内核崩溃使用 Fedora 基础架构处理内核崩溃使用 Red Hat 基础架构处理内核崩溃使用 AlmaLinux 基础架构处理内核异常（kerneloops）使用 Fedora 基础架构处理内核异常（Oops）使用 Red Hat 基础架构处理内核故障使用 AlmaLinux 基础架构处理问题使用 Fedora 基础架构处理问题使用 Red Hat 基础架构处理问题使用 AlmaLinux 基础架构处理 Python 3 异常使用 Fedora 架构处理 Python 3 异常使用 AlmaLinux 基础架构处理 Python 异常使用 Fedora 基础架构处理 Python 异常使用 Red Hat 基础架构处理 Python 异常使用 Fedora 基础架构处理报告使用 Red Hat 基础架构处理报告处理中处理尚未开始处理完成处理失败。处理结束，请前往下一步骤。处理结束。处理被中断: 目录不可写入，无法继续。处理该问题失败。原因可能有很多种，但最常见的是以下三种情况： ▫ 网络连接问题 ▫ 问题数据受损 ▫ 无效配置处理被取消由于该问题不可被汇报，处理已中止。处理中……向 Red Hat 支持提供崩溃的细节提供附加信息退出RH 门户网站 URL收件人收件人电子邮件Red Hat 客户支持Red Hat 客户密码Red Hat 客户用户名汇报后删除 DIR汇报完成后移除 PROBLEM_DIR正在删除 {0}重新报告Report 上传工具汇报 Bug 至 Fedora 维护者向 Red Hat Bugzilla 提交 Bug 报告向 Red Hat 客户门户网站报告 bug报告来自未被打包的可执行文件的问题。向 AlmaLinux Bug 跟踪系统报告汇报至 Bugzilla 缺陷跟踪系统向 Fedora 汇报向 Red Hat Bugzilla 提交报告汇报至 Red Hat 全球支持报告未被打包的问题已报告：汇报中汇报已完成，您现在可以关闭这个窗口了。由于产生的回溯信息价值低，已禁用回报。访问限制通过用户组限制可访问 Bug 的用户(了解更多请进入高级选项)限制报告访问仅限此组访问仅限特定组访问 <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 公钥文件保存为文本文件搜索保密服务不可用，您的设置将不会被保存！选择要运行的工作流： 选择一个要运行的事件： 选择如何汇报此问题发送二进制数据发送类似内核转储的二进制文件通过电子邮件发送问题数据发送到内核错误跟踪程序通过电子邮件发送发送者发送者电子邮件正在将 %s 发送至 %s//%s正在发送 ABRT 崩溃统计数据正在发送通知邮件至：%s发送电子邮件......发送 uReports 到 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>。提交匿名故障报告提交匿名崩溃报告 - 我不希望红帽支持团队与我联络提交 uReport创建新问题单前请提交 uReport正在向 %s 提交内核异常报告成功创建 %s尚未确定 MantisBT 项目。URL '%s' 不存在(服务器返回错误 404)回溯是不完整的，请确定您提供了重复该错误的完整步骤。该回溯可能无法帮助开发者诊断 Bug。此崩溃的程序由 '%s' 发布。您想要向红帽支持部门报告这一问题吗？日期：'%s' 包含无法识别的后缀：'%s'日期：'%s' 在 UNIX 时间戳范围以外只有可访问“私人问题”的用户可以访问该问题由于无效的数据该问题无法汇报。'%s' 文件不包含数字。这个问题仅出现过一次，并且复现问题的可能性未知。请确保您可以为我们的支持团队提供详细信息。要继续并建立新支持问题单吗？程序 '%s' 似乎并不是由红帽提供的。 您想要向红帽支持部门报告这一问题吗？报告结果 '%s' 缺少 URL。报告已被附加至 %s报告已被保存至 %s来自 '%s' 的响应包含无效格式位于 '%s' 的服务器当前无法处理请求(得到错误 503)位于 '%s' 的服务器遇到内部错误(得知错误 500)位于 '%s' 的服务器响应错误：'%s'该问题没有指派一个 uReport。该问题已经被汇报过了。该问题已经汇报至 Bugzilla '%s' ，与预配置 Bugzilla '%s' 不同。该问题已经汇报至 MantisBT '%s' ，但与配置的 MantisBT '%s' 不同。已向 '%s' 报告了这个问题。该问题尚未汇报至 Bugzilla。这个问题反复出现该问题可能不应该汇报 (很有可能为已知问题)。%s该问题已经被汇报至 Bugzilla（请查看 '%s'）。仍然要提交新 bug 吗？该问题已汇报至 MantisBT（请查看 '%s'）。还要生成新问题吗？Ticket/案例 ID在从 '%s' 得到的响应中检测到类型不匹配URL无法在 Bugzilla URL '%s' 中找到 Bug ID无法处理来自 Bugzilla URL '%s' 中的 Bug ID无法解析位于 '%s' 的 ureport 服务器的响应'%s' 中的意外 HTTP 响应：%d提取失败，中断下载......不支持的操作类型可能有帮助的更新： 将 FILE 上传【到使用这个 ID 的案例】作为 tar.gz 文件上传（使用 FTP/SCP/...）通过 scp 或 ftp 向远程目标系统上传数据提交问题数据至服务器上传的：%llu kb 中的 %llu未指定 url 或请求。用法： 使用 HTTP 认证使用用户认证如果不想要在 URL 中出现密码则请使用这个字段如果不想要在 URL 中出现用户名称则请使用这个字段使用这个字段指定 SSH 私钥文件使用这个字段指定 SSH 公钥文件用户名用户名使用 Bugzilla ID '%s'使用 MantisBT ID '%s'使用默认产品 '%s'值确认 SSL查看/编辑文本文件警告，已在命令行参数指定私有标签组，忽略环境变量和配置警告：缓存目录 '{0}' (剩余 {1:.2f}Mb) 中没有足够的空闲空间。继续？警告：临时目录 '{0}' (剩余 {1:.2f}Mb)没有足够的空闲空间。继续？关注 Bugzilla Bug关注已经报告的 Bug我们找到了一个相似的 Red Hat 支持案例 %s。您是否想要将数据附加到此案例上？否则，您需要输入一个已存在的 Red Hat 支持案例编号。生成 Bug 时也请附加二进制文件您希望向哪里上传报告的 tarball 文件，格式为 login:password@url工作流您正在将文件复制到它本身可创建 bugs.almalinux.org 帐户 <a href="https://bugs.almalinux.org/signup_page.php">here</a>您可以在 <a href="https://bugzilla.redhat.com/createaccount.cgi">here</a> 创建 bugzilla.redhat.com 账户您选择的数字超出了范围您要求只能由特定的组访问您的数据，而这个 bug 是 bug %s/%u 的重复。在 bug 重复的情况下，将会在最初的 bug 报告中添加一条新评注，但是对于那些评注的访问不能被限制到特定的组。您是否要新建一个 bug 报告，并将其作为最初那个报告的 重复（DUPLICATE）而关闭？否则，将终止 bug 报告的过程。执行前您需要填写如何进行......需要指定要添加的 uReport 的 bthash。您需要指定 bug ID、联络电子邮件、评注或上述全部内容您的输入无效，因为：您的问题似乎由 %s 导致 %s 您的问题似乎由以下原因之一导致： 取消（_C）关闭（_C）转发（_F）否（_N）确认（_O）打开（_O）保存（_S）停止（_S）是（_Y）将 DATA 作为 ureporte 附件 ATTACHMENT_TYPE 添加（仅与 -l|-L 配合使用）附上 RHBZ bug (需要 -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文件以 %d 退出的 gzip使用信号 %d 杀死 gzipgzip 进程失败已被另一个进程锁住不是问题目录拒绝访问uReportuReport 服务器 URLUID 值无效: '%s'在 reported_to 中查找 FIELD 时使用 REPORT_RESULT_TYPE（仅与 -L 配合使用）y