| Server IP : 85.193.89.191 / Your IP : 3.147.7.215 Web Server : Apache System : Linux 956367-cx40159.tmweb.ru 3.10.0-1160.105.1.el7.x86_64 #1 SMP Thu Dec 7 15:39:45 UTC 2023 x86_64 User : bitrix ( 600) PHP Version : 8.1.27 Disable Function : NONE MySQL : OFF | cURL : OFF | WGET : ON | Perl : ON | Python : ON | Sudo : ON | Pkexec : ON Directory : /proc/978/cwd/usr/share/locale/zh_CN/LC_MESSAGES/ |
Upload File : |
�� � � � L �) � �) � �* ' 0 40 Q0 Q `0 �0 �0 �0 0 �0
1 1 (1 21 ( D1 6 m1 �1 �1 - �1
2 � "2 > �2 [ 3 � v4 � �4 _ �5 G 6 � H7 x 9 � �9 !: >: \: s: �: �: �: �: �: $ ; 3; B; � U; a < > �< � �< D m= U �= 2 > ;> T> i> �> �> �> ' �> ? % ? F? d? + m? �? R �? : �? > :@ y@ , �@ �@ �@ �@ " A
#A 5 1A 0 gA �A �A # �A �A
B B
&B 3 1B * eB �B B �B �B �B C C ' :C bC sC
�C $ �C @ �C A �C - ?D mD * �D �D �D �D - E & 2E YE yE �E 3 �E 5 �E A F ' NF vF �F + �F 8 �F Q G 8 hG �G / �G �G H #H =H DH ; WH �H 5 �H �H �H I A 'I % iI �I
�I �I
�I �I , �I J 'J >J Q TJ �J �J �J �J 7 �J &K ,K 4K 0 MK \ ~K ' �K L L ,L $ GL lL ; �L ^ �L R &M yM �M �M - �M @ �M " N > :N 0 yN C �N % �N A O 7 VO # �O " �O �O # �O 1 P X 5P X �P �P � �P tQ 2 �Q �Q �Q �Q �Q R .R MR gR + �R 9 �R �R 8 �R /S NS kS # �S ? �S �S
�S T � T - �T ! �T ) �T 'U % DU 2 jU 1 �U � �U - �V � �V � �W . FX ( uX � �X iY qY �Y �Y �Y > �Y 6 Z ; ?Z {Z . �Z �Z �Z 7 �Z = [ 2 Z[ . �[ �[
�[ �[ �[ �[ C \ E F\ + �\ ( �\ B �\ $] *] J] Z] r] �] �] �] a �] b ^ n^ }^ ' �^ �^ Z �^ 1 0_ b_ , �_ �_ � �_ �` �` �` �` N �` a -a M �a G �a & %b $ Lb $ qb v �b @
c 6 Nc m �c a �c ! Ud O wd �d $ �d O �d He \e 7 ne 8 �e : �e ; f < Vf = �f 8 �f 9
g 6 Dg 7 {g 3 �g 4 �g < h = Yh 2 �h 3 �h
�h i &i 6i 5 Ii i B �i � �i �j A �j
�j *
k 5k Tk
Yk gk qk �k �k �k �k " �k l l #l " 3l Vl ' wl , �l 2 �l �l m /m Jm dm nm 5 xm @ �m 6 �m &n � 6n �n " �n � o �o �o �o �o �o �o p p > !p `p {p ! �p �p �p �p q #q 2q 9q Hq " ]q # �q �q �q $ �q $ �q % r & Er lr �r
�r � �r 6s <s S Os [ �s $ �s & $t Kt q St �t P �t 4u ) Cu mu �u 7 �u Q �u @ ,v b mv , �v . �v � ,w t x & �x �x �x ) �x E y @ Vy 0 �y / �y ' �y ` z + �z / �z �z F �z C{ 9 R{ �{ * �{ - �{ 4 �{ & | & E| l| �| # �| ' �| �| , } # /} S} q} y} �} d �} 9 ~ : J~ - �~ , �~ �~ �~ �~
q 1 M � K � � =� * � N � [� ) e� w �� # � � +� 5 �� 4 �� 1 ,� $ ^� * �� 9 �� � � �� � � � � � � � I 0� 3 z� c �� I � 7 \� 7 �� / ̆ " �� � : 2� a m� χ ԇ և ۇ �
� � 8� P� b� j� }� P �� � | � � j� � $� � +� ?� D H� �� �� �� ) �� ؑ � � �� & � 5 5� k� �� , �� Ȓ � � E �� h Ǔ � 0� � �� T Z� ? �� � � y Ǚ � A� ɚ � �� � /� E� " a� �� �� $ �� ܛ � � � R �� < � � E� B � 3 F� A z� �� ؞ �� � /� # J� % n� �� �� Ο � 0 � $� E 6� 6 |� 4 �� � * � � 8� L� % h� �� 7 �� 0 ӡ � %� ?� `� t� �� �� 2 �� + Ң % �� 7 $� \� e� r� �� * �� ̣ ܣ � " � B $� F g� * �� ٤ % � � 3� L� ( c� �� �� ĥ ۥ 1 � 3 !� 6 U� ! �� �� Φ - � 6 � C O� < �� Ч * � � ,� L� e� l� 3 |� �� : Ψ � ' '� O� - e� - �� �� ԩ � � �� * � 1� J� i� H �� Ϊ � � � 3 � T� [� b� ( x� N �� � � � )� & <� c� = ~� T �� D � V� t� �� 3 �� G #
� D .� 1 s� G �� # � D � 7 V� " �� �� ѯ 0 ݯ ) � X 8� W �� � � � v� * �� �� ű ٱ �
� "� :� X� * q� 7 �� Բ 0 � � $ 1� V� ! r� D �� ٳ ݳ � � �� - �� �� ! ݴ �� ' � ! C� 2 e� � �� * J� � u� � � , �� ( � � � ��
�� Ÿ ݸ �� 7 � ; I� 6 �� �� $ ٹ ��
� 0 � F M� 6 �� , ˺ �� � � #� =� > J� @ �� ʻ % � A � Q� , W� �� �� �� �� �� �� } Ӽ O Q� �� �� ' Ľ � ] � - f� �� ) �� ܾ � � �� ʿ ݿ �� : � W ;� > �� 3 � " � )� % H� K n� * �� - � ] � X q� �� Q �� <� F� B f� �� �� - �� + �� , � * J� 2 u� 0 �� , �� * � 6 1� * h� & �� $ �� . �� , � & ;� ' b� �� �� �� �� ' �� �� 5 �� � 2� �� - �� "� + 2� ^� q� x� �� �� �� �� �� �� ! � '� 8� E� $ X� $ }� . �� - �� , �� % ,� R� c� �� �� �� * �� 3 �� 9 � R� O _� �� �� y �� O� \� r� �� �� �� �� �� 9 ��
� ! ,� N� j� * �� ' �� ! �� �� � � .� $ L� q� �� �� �� # �� $ � % (� N� ]� j� c w� �� �� M �� P G� % �� ( �� �� l �� [� R t� �� & �� % �� #� - 3� N a� 1 �� P �� 0 3� , d� � �� > =� |� �� �� ' �� B �� < 9� + v� & �� �� N �� $ .� $ S� x� A �� �� 6 �� � , � 2 L� 6 � " �� ! �� �� � 4 0� 2 e� �� ' �� �� �� � � ,� K ?� ; �� > �� ) � ) 0� Z� d� n� ��
�� �� Q �� Y � U [� � �� ) c� P �� �� $ �� {
� ! �� P �� * �� 7 '� I _� �� $ �� 1 �� � .� =� L� X� g� v� �� �� �� U �� / � e 9� G �� 0 �� 3 � / L� " |� �� 7 �� Q �� 6� =� ?� F� \� x� �� �� �� �� �� �� [ �� T� � & � � � � � � � � � e � � � � � | � � � � � � O x ' � : � � , Z S � R � � 2 � n � � � � � � � ! � � $ [ M w 3 � � � � � � � � � I J B � � " � � , � - � � O � � r s � � � p � � ; � � 0 � W � m W 4 D � � � f � � � u * + � � � � � g � � P � � � - L � � = � J n � E l o � � 2 s C � � & ] � = � � � 6 k ' � � � # � _ � Y � G / � � ~ � � t � Q F � � � 8 � ) � � m � � � \ � X c � ( � 7 � � � . � < � " � 4 T � � � 7 < � t \ U � B
� z � � �
� � � � � } w � � � � � R � � � � � ; � � b V � H � ^
� C f � � � � � � � � ( ` % � � v r � 3 0 k � Z F q � L / � � � � : ? e � a � � � ! N � � � � | � � l � 1 � Y K � � { { b � � ~ V p * � � } q � � � d � � ^ Q P � � . � h + � � > � a � j 9 D c T � @ 8
� H � i � ) � g � � 9 � ] u � � K � G � i $ � � � � � � � � A ` 5 � S y � E � d � � j v 6 � � % � X � ? � N � � 5 I � � � 1 � � y � z h @ _ � o A � U > � � M � # [ � x � � �
& [-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
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
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 %llu bytes, %u files %s is not properly configured. You can configure it now or provide the required information later.
Read more about the configuration at: https://access.redhat.com/site/articles/718083 & [-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] [-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]\
[-A -a bthash -B -b bug-id -E -e email] [-d DIR]
Upload micro report or add an attachment to a micro report
Reads the default configuration from & [-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 'strata' or 'bugzilla' ('%s' completed successfully)
('%s' exited with %u)
('%s' was killed by signal %u)
(binary file, %llu bytes) (click here to view/edit) (no description) (not needed, data already exist: %s) (requires: %s) --- Running %s --- <b>%s</b> is not properly configured. You can configure it now or provide the required information later.
<a href="https://access.redhat.com/site/articles/718083">Read more about the configuration</a> <b>Your comments are not private.</b> 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 info A 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 log Adding %s to CC list Adding External URL to bug %i Adding attachments to bug %i Adding comment to case '%s' Adding new comment to bug %d Additional files included in 'auth' key Address of Bugzilla server Address of the Red Hat support portal Address of uReport webservice Advanced Allow insecure connection to ureport server Alternate GUI file Analyze the problem locally and export the problem data information to a text file Analyze the problem locally and send information via email Analyze the problem locally and upload the data via scp or ftp Append Append new reports or overwrite the old one. Append to, or overwrite FILE Archive is created: '%s' Ask Red Hat Support for help Attach FILEs [to bug with this ID] Attach a file Attach crash data to an existing Red Hat support case Attach the data to existing Red Hat support case Attaching '%s' to case '%s' Attaching better backtrace Attaching problem data to case '%s' Bad value for '%s': %s Base URL to upload to Basic Be verbose Bug %i is CLOSED as DUPLICATE, but it has no DUP_ID Bug %i is CLOSED, but it has no RESOLUTION Bug is already reported: %i Bug.search(quicksearch) return value did not contain member 'bugs' Bugzilla Bugzilla URL Bugzilla account password Bugzilla account user name Bugzilla couldn't find parent of bug %d Bugzilla product Bugzilla product version C_onfigure Caching files from {0} made from {1} Can't call method '%s' over DBus on path '%s' interface '%s': %s Can't connect over DBus to name '%s' path '%s' interface '%s': %s Can't continue without RHTSupport case number Can't continue without URL Can't continue without email address of %s Can't continue without login Can't continue without password Can't copy '%s': %s Can't create a secret item for event '%s': %s Can't create a temporary directory in Can't create temporary file in Can't delete '%s': %s Can'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}' Can't extract package '{0}' Can't find packages for {0} debuginfo files Can't generate stacktrace description (no crash thread?) Can't get Bugzilla ID because this problem has not yet been reported to Bugzilla. Can't open '%s' for writing. Please select another file: Can't parse backtrace: %s Can't remove %s, probably contains an error log Can't remove '{0}': {1} Can't setup {0}: {1}, disabling Can't write to '{0}': {1} Cancel Cancelled by user. Cannot check backtrace rating because of invalid event name Cannot copy file '{0}': {1} Cannot run vi: $TERM, $VISUAL and $EDITOR are not set Check SSL key validity Checking for duplicates Checking for hints Clear the search bar to see the list of security sensitive words. Closing bug %i as duplicate of bug %i Compressing data Con_figure %s Config file Configuration Configuration file Configuration file (may be given many times) Configuration file for uReport Confirm data to report Contact email address Create new Red Hat Support case - I would like to be contacted by Red Hat Support Create reported_to in DIR Creating a new bug Creating a new case Custom D-Bus Secrets Service ReadAlias('%s') method failed: %s Debug Details Display version and exit Do 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 again Don't store passwords Download cancelled by user Downloading ({0} of {1}) {2}: {3:3}% Downloading package {0} failed Downloading {0:.2f}Mb, installed size: {1:.2f}Mb. Continue? Email address of %s was not specified. Would you like to do so now? If not, '%s' is to be used Email address that can be used by ABRT server to inform you about news and updates Email was sent to: %s Emergency analysis Error Error in case creation at '%s', HTTP code: %d Error in case creation at '%s', HTTP code: %d, server says: '%s' Error in case creation at '%s': %s Error in case creation at '%s': no Location URL, HTTP code: %d Error in comment creation at '%s', HTTP code: %d Error in comment creation at '%s', HTTP code: %d, server says: '%s' Error in comment creation at '%s': %s Error in comment creation at '%s': no Location URL, HTTP code: %d Error initializing yum (YumBase.doConfigSetup): '{0!s}' Error retrieving filelists: '{0!s}' Error retrieving metadata: '{0!s}' Error: %s Error: can't make cachedir, exiting Essential element '%s' is missing, can't continue Event '%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? Events Examples:
ftp://[user[:pass]@]host/dir/[file.tar.gz]
scp://[user[:pass]@]host/dir/[file.tar.gz]
file:///dir/[file.tar.gz] Expert mode Export the problem data information to a text file Extracting cpio from {0} FTP Proxy Failed on submitting the problem Failed to close TAR writer Failed to create a new bug. Failed to finalize TAR archive Failed to open TAR writer Failed to save file '%s' Failed to upload uReport to the server '%s' Failed to upload uReport to the server '%s' with curl: %s Forbidden words Force reporting even if this problem is already reported Formatting file for a new case Formatting file for an email Formatting file for duplicates Formatting file for initial comment Found the same comment in the bug history, not adding a new one Groups HTTP Proxy HTTPS Proxy How 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 problem I don't know what caused this problem I have experienced this problem for the first time I reviewed the data and _agree with submitting it If 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 don't know how to describe it, you can 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 <b>Preferences</b> item
in the application menu and after applying the configuration changes click <b>Repeat</b> button. Ignored invalid ISO date of report result '%s' Ignoring URL without scheme and hostname In order to enable the built-in screencasting functionality the package fros-gnome has to be installed. Please run the following command if you want to install it.
<b>su -c "yum install fros-gnome"</b> Include Initializing yum Invalid boolean value '%s' Invalid input, exiting. Invalid number '%s' Invalid password or login. Please enter the password for '%s': Invalid password or login. Please enter your BZ login: Invalid password or login. Please enter your Red Hat login: Invalid utf8 character '%c' Item '%s' already exists and is not modifiable Kerneloops URL Kerneloops.org Learn more about restricted access in the configuration Linking ABRT crash statistics record with contact email: '%s' Linking ABRT crash statistics record with the case List possible events [which start with PREFIX] Log File Log to syslog Logger Logging into Bugzilla at %s Logging out Login is not provided by configuration. Please enter your BZ login: Login is not provided by configuration. Please enter your RHTS login: Looking for needed packages in repositories Looking for similar problems in bugzilla Looks like corrupted xml response, because '%s' member is missing. Mailx Malformed url to Bugzilla '%s'. Message subject Missing mandatory value Missing required item: '%s' N Name Name of the logfile Need 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 set New bug id: %i No description available No processing for event '%s' is defined No reporters available No reporting targets are defined for this problem. Check configuration in /etc/libreport/* Noninteractive: don't ask questions, assume 'yes' Not uploading an empty uReport Notify only (Do not mark the report as sent) Ok On 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 url Output file Packages to download: {0} Password Password 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 user name for '%s//%s': 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. Preferences Print BUG_ID which has given DUPHASH Problem '{0!s}' occured while downloading from mirror: '{1!s}'. Trying next one Problem description Problem directory Process the C/C++ crash using the Fedora infrastructure Process the C/C++ crash using the Red Hat infrastructure Process the Java exception using the Fedora infrastructure Process the Java exception using the Red Hat infrastructure Process the X Server problem using the Fedora infrastructure Process the X Server problem using the Red Hat infrastructure Process the kernel crash using the Fedora infrastructure Process the kernel crash using the Red Hat infrastructure Process the kerneloops using the Fedora infrastructure Process the kerneloops using the Red Hat infrastructure Process the problem using the Fedora infrastructure Process the problem using the Red Hat infrastructure Process the python exception using the Fedora infrastructure Process the python exception using the Red Hat infrastructure Process the report using the Fedora infrastructure Process the report using the Red Hat infrastructure Processing Processing did not start yet Processing done Processing 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:
▫ <b>network connection problems</b>
▫ <b>corrupted problem data</b>
▫ <b>invalid configuration</b> Processing was canceled Processing was interrupted because the problem is not reportable. Processing... Provide Red Hat Support with crash details Provide additional information Quit RH Portal URL Recipient Recipient's email Red Hat Customer Support Red Hat customer password Red Hat customer user name Remove DIR after reporting Remove PROBLEM_DIR after reporting Removing {0} Repeat Report Uploader Report a bug to Fedora maintainers Report a bug to Red Hat Bugzilla Report a bug to Red Hat Customer Portal Report result label mustn't be empty string. Report result label mustn't contain ':' character. Report to Bugzilla bug tracker Report to Fedora Report to Red Hat Bugzilla Report to Red Hat support Reported: Reporting Reporting disabled because the backtrace is unusable. Reporting disabled because the rating does not contain a number. Reporting has finished. You can close this window now. Restrict access Restrict 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 report Restrict access to this group only Restrict the access to specified groups <a href="https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-tickets">?</a> Review the data Run only these events SSH Private key file SSH Public key file SSH private key file SSH public key file Save as text file Search Secret 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 problem Send Binary Data Send binary files like coredump Send the problem data via email Send to kernel oops tracker Send via email Sender Sender's email Sending %s to %s//%s Sending ABRT crash statistics data Sending a notification email to: %s Sending an email... Sends ureports to FAF server Server responded with an error: '%s' Sets the proxy server to use for FTP Sets the proxy server to use for HTTP Sets the proxy server to use for HTTPS Setting up yum repositories Show log Show password Since crashes without a known reproducer can be difficult to diagnose, please provide a comprehensive description of the problem you have encountered. Size: Specify server URL Specify this only if you needed different product than specified in /etc/os-release Specify this only if you needed different product version than specified in /etc/os-release Status: %s%s%s %s/show_bug.cgi?id=%u String doesn't seem to be a date: '%s' Subject Submit <a href="https://access.redhat.com/articles/642323">micro-report</a> when creating a new case. Submit anonymous crash report Submit anonymous crash report - I do not want to be contacted by Red Hat Support Submit uReport Submit uReport before creating a new case Submitting oops report to %s Successfully created %s 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 range 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 %s The report was stored to %s The response from '%s' has invalid format The 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 not been reported to '%s'. This problem has not been reported to Bugzilla. This problem occurs repeatedly This problem should not be reported (it is likely a known problem). %s Ticket/case ID Type mismatch has been detected in the response from '%s' URL Unable 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': %d Unpacking failed, aborting download... Unsupported option type Updates which possibly help: Upload FILEs [to case with this ID] Upload as tar.gz file (via FTP/SCP/...) Upload for analysis Upload the problem data for further analysis Upload the problem data to a server Uploaded: %llu of %llu kbytes Usage: Use HTTP Authentication Use client authentication Use this button to generate more informative backtrace after you installed additional debug packages Use this field if you do not want to have password in URL Use this field if you do not want to have user name in URL Use this field to specify SSH private keyfile Use this field to specify SSH public keyfile User name Username Using Bugzilla ID '%s' Value Verify SSL View/edit a text file Warning, private ticket groups already specified as cmdline argument, ignoring the env variable and configuration Warning: 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? We 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 too Where do you want to upload the tarball with report in form login:password@url Workflows You are trying to copy a file onto itself You can create bugzilla.redhat.com account <a href="https://bugzilla.redhat.com/createaccount.cgi">here</a> You have chosen number out of range You 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 or both Your 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 _Yes add a screencast attach DATA as ureporte 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 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': %s cannot be reported contact e-mail address (requires -a|-A, conflicts with -E) contact e-mail address from environment or configuration file (requires -a|-A, conflicts with -e) data f file gzip exited with %d gzip killed with signal %d gzip process failed locked by another process not a problem directory permission denied uReport uReport Server URL uid value is not valid: '%s' use REPORT_RESULT_TYPE when looking for FIELD in reported_to (used only with -L) y Project-Id-Version: PACKAGE VERSION
Report-Msgid-Bugs-To:
POT-Creation-Date: 2019-10-01 17:40+0200
PO-Revision-Date: 2019-10-09 04:52+0000
Last-Translator: Tony Fu <tfu@redhat.com>
Language-Team: Chinese (China)
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: Zanata 4.6.2
& [-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 组名]... [-c 配置文件]... [-F FMT文件] [-A FMT文件2] -d 目录
或:
& [-v] [-c 配置文件]... [-d 目录] -t[ID] 文件...
或:
& [-v] [-c 配置文件]... [-d 目录] -t[ID] -w
或:
& [-v] [-c 配置文件]... -h DUPHASH
报告问题至 Bugzilla。
该工具读取目录，之后登录至 Bugzilla 去尝试寻找‘白板(Whiteboard)’中包含相同 ABRT 哈希值 HEXSTRING 的 Bug。
如果这样的 Bug 没有找到，那么将创建一个新的。目录中的元素将依据它们的类型和大小，分别做为 Bug 描述或附件保存。
否则，如果找到相同的 Bug 并且被标识为 CLOSED DUPLICATE。
该工具会查询重复记录链条直到找到一个非重复的 Bug 为止。
然后将发现的 Bug 做为评论添加上去。
指向新创建或者修改的 Bug 的 URL 将会打印至标准输出并保存到
'reported_to' 元素中。
选项 -t 上传指定文件到在 Bugzilla 站点上已经存在的 Bug 上。
Bug ID 通过选项 -d 指定的目录提取。
如果包含在指定目录中的问题数据从未报告至 Bugzilla，上传会失败。
选项 -tID 上传指定文件到 Bugzilla 上的指定 ID 上。
选项 -d 指定目录会被忽略。
选项 -w 添加 Bugzilla 用户到 Bug 抄送列表上。
选项 -r 设定来自 reporter_to 元素最后一个以指定
跟踪系统名为前缀的 URL 作为 URL 域。 该选项仅在提交一个新 Bug 误时使用。
默认值为 'ABRT Server'
如果未指定，配置文件默认为
未查出报告有更改
该报告已更新 # 架构 # 回溯
# 检查它是否包含任何敏感数据（密码等等） # 命令行 # 组件 # 核转储 # 在下面描述此崩溃的发生环境 # 可执行 # 内核版本 # 软件包 # 崩溃原因 # 操作系统的发行版本字符串 # 来自根目录的操作系统发行版本字符串 # 该字段为只读
# os-release 配置文件 # 来自根目录的 os-release 配置文件 %llu字节，%u个文件 未正确配置 %s。可现在进行配置，或稍后提供所需信息。
有关配置的详情，请参考：https://access.redhat.com/site/articles/718083 & [-d] DIR
用来报告在指定目录中所保存问题的新工具 & [-v] --target TARGET --ticket ID FILE...
将 FILE 上传到 TARGET 中指定的 ticket。
这个工具是用来简化用户向 libreport 提交报告软件包
的过程。可识别的 TARGET 为 'strata' 和 'bugzilla'，
第一个请求上传到 RHTSupport，而第二个请求上传到 Bugzilla。
可使用文件提供配置（比如登录数据）。
& [-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]
向标准输出或 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] [-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]\
[-A -a bthash -B -b bug-id -E -e email] [-d DIR]
Upload micro report or add an attachment to a micro report
Reads the default configuration from & [-vpdx] [-e 事件]... [-g GUI 文件] 问题目录
分析并报告保存在指定 PROBLEM_DIR 下问题的 GUI 工具 & [-vsp] -L[PREFIX] [PROBLEM_DIR]
or: & [-vspy] -e EVENT PROBLEM_DIR
or: & [-vspy] -d PROBLEM_DIR
or: & [-vspy] -x PROBLEM_DIR '%s' 不是普通文件 '%s' 不是正确的文件名 'strata' 或者 'bugzilla' ('%s' 成功完成)
('%s' 以 %u 退出)
('%s' 被信号 %u 杀死)
（二进制文件，%llu字节） （点击这里查看/编辑） （没有说明） (不必要，数据已经存在: %s) (需要: %s) --- 正在运行 %s --- 未正确配置 <b>%s</b>。 可现在进行配置，或稍后提供所需信息。
<a href="https://access.redhat.com/site/articles/718083">了解更多有关配置的信息</a> <b>您的注释不是保密的。</b>会将其包含在公开的问题报告中。 ''reported_to'中附加 URL 所指 Bug 跟踪系统的名字 一个隐私 Ticket 请求已创建，但是尚未指定可访问用户组。请访问 https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-tickets 以了解更多详细信息。 可能丢失了正确的出错信息或者内核转储被污染。 等待 DBus 安全服务请求结果已经超时。 添加 Bugzilla 用户到[可选指定 ID 的 Bug]抄送列表上 在日志中添加程序名 正在添加 %s 至抄送列表 添加外部 URL 至 Bug %i 在 Bug %i 中添加附件 添加评论至个案 '%s' 正在向 Bug %d 中添加新留言 'auth' 密钥中包含的附加文件 Bugzilla 服务器地址 Red Hat 支持门户网站地址 uReport 网络服务器地址 高级 允许使用非加密链接到 uReport 服务器 备用 GUI 文件 本地分析该问题并将该问题数据信息导出为文本文件 本地分析该问题并通过电子邮件发送信息 本地分析问题并通过 scp 或 ftp 上传数据 附加 附加新报告或者覆盖已有报告。 附加到，或者覆盖 FILE 生成归档：'%s' 向红帽支持寻求帮助 附加 FILE [可选指定 ID 的 Bug] 附加文件 为已存在的红帽支持问题单附加 crash 数据 为已存在的红帽支持问题单附加数据 在问题单 '%s' 中附加 '%s' 附加更好的 backtrace 添加问题数据至个案 '%s' '%s' 值错误：%s 要上传的基本 URL 基本 详细输出 Bug %i 因为重复被关闭，但它没有 DUP_ID Bug %i 已关闭，但还没有解决方案 该 Bug 之前已经被汇报至：%i Bug.search(quicksearch) 返回值未包含成员 'bugs' Bugzilla Bugzilla URL Bugzilla 账户密码 Bugzilla 账户用户名 Bugzilla 无法找到 Bug %d 的父类 Bug Bugzilla 产品 Bugzilla 产品版本 配置（_O） 从 {0} 缓存来自 {1} 的文件 无法通过 DBus 调用方法 '%s' 在路径 '%s' 接口 '%s': %s 无法通过 DBus 连接至名称 '%s' 路径 '%s' 的接口 '%s' : %s 没有 RHTSupport 问题单号无法继续 需要 URL 才可继续 需要 %s 的电子邮箱才可继续 需要登录名才可继续 需要密码才可继续 无法复制 '%s'：%s 无法为事件 '%s' 创建保密项: %s 无法创建临时目录于 无法创建临时文件于 无法删除 '%s'：%s 无法删除：'%s' 无法从问题数据中确定 Bugzilla 产品。 无法确定问题数据中的红帽支持产品。 无法禁用异步下载，输出可能存在假象！ 无法禁用仓库 '{0!s}': {1!s} 无法从 '{0}' 中提取文件 无法提取软件包 '{0}' 无法为 {0} debuginfo 文件找到软件包 无法生成堆栈跟踪描述 (没有崩溃线程？) 无法取得 Bugzilla ID 因为该问题尚未汇报至 Bugzilla。 无法打开 '%s' 进行编写。请选择另一个文件： 无法解析回溯：%s 无法删除 %s，可能包含出错记录 无法删除 '{0}'：{1} 无法设置 {0}：{1}，禁用 无法写入 '{0}'：{1} 取消 用户取消。 由于无效的事件名，无法检查回溯评级 无法复制文件 '{0}': {1} 无法运行 vi：尚未设置 $TERM、$VISUAL 和 $EDITOR 查看 SSL 密钥是否可用 正在检查该问题是否已经汇报 检查是否有提示 清除搜索栏查看安全性敏感词列表 将 bug %i 作为 bug %i 的重复 bug 关闭 正在压缩数据 配置（_f）%s 配置文件 配置 配置文件 配置文件（可在任意时间给出） 为 uReport 配置文件 确认要上传的汇报数据 联系人电子邮件地址 生成新的红帽支持问题单 - 希望红帽支持团队与我联络 在 DIR 中创建 reported_to 正在创建新 Bug 创建一个新个案 自定义 DBus 保密服务 ReadAlias('%s') 方法失败：%s 除错 详情 显示版本并退出 您还想生成 RHTSupport ticket 吗？ 您想要停止等待并在未正确载入配置的情况下继续汇报吗？ 可能的相关文档： 不再询问 不要保存密码 用户取消下载 下载（{1} 中的 {0}）{2}：{3:3}% 下载软件包 {0} 失败 正在下载 {0:.2f}Mb，已安装：{1:.2f}Mb。继续吗？ 未指定 %s 的电子邮箱。您想要现在制定吗？如果不，将使用 '%s' ABRT 服务器用来向您发送新闻和更新的电子邮件地址 已发送电子邮件至：%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}' 错误：%s 错误：无法创建缓存目录，正在退出 缺少重要元素 '%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} 中提取 cpio FTP 代理服务器 提交问题失败 关闭 TAR 写入程序失败 创建新 Bug 失败。 完成 TAR 归档失败 打开 TAR 写入程序失败 保存文件 '%s' 失败 将 uReport 上传到服务器 '%s' 失败 无法使用 curl 上传 uReport 至服务器 '%s'：%s 禁用单词 即使已经报告过该问题依然强行报告 为新问题单格式化文件 为某个电子邮件格式化文件 格式化文件用于副本 格式化文件用于首次评论 如果在 Bug 历史记录中找到相同的注释则不要再添加 组 HTTP 代理 HTTPS 代理 这个问题是如何发生的（具体步骤）？怎样才可以复制？是否有其他可帮助诊断该问题的附加注释？请尽量使用英语。 如何重现这个问题（每行一步）？ 如何重现这个问题？ 您希望如何报告该问题？ 我可以重现这个问题 我不知道造成这个问题的原因 我是第一次遇到这个问题 我已经检查了数据并且同意提交（_A） 如果您是要向远程服务器报告，请确定删除所有私人数据（不如用户名和密码）。Backtrace、命令行、环境变量是检查所需的常规项目。 如果您不知道如何描述，您可以 如果您要向不同的地点报告这个问题、收集附加信息或者更好地描述这个问题并重复报告过程，请按“前进”。 如果要更新配置并尝试再次报告问题，请打开应用程序菜单中的 <b>首选项</b>，
并在应用配置更改后，点击 <b>重新报告</b> 按钮。 忽略报告结果 '%s' 的无效 ISO 日期 将忽略没有方案和主机名的 URL 要启用内置截屏视频功能，则必须安装软件包 fros-gnome。如果要安装该软件包，请运行以下命令：
<b>su -c "yum install fros-gnome"</b> 包括 启动 yum 无效的布尔值 '%s' 无效输入，正在退出。 无效的数字 '%s' 无效的密码或登录名。请输入 '%s' 的密码: 无效的密码或登录名。请输入您的 BZ 登录名: 无效密码或登录。请输入您的红帽登录： 无效的 utf8 字符 ‘%c' 项目 '%s' 已存在且不可修改 Kerneloops URL Kerneloops.org 了解更多有关配置中限制访问的信息 正在将 ABRT 崩溃统计记录与联系人电子邮件关联：'%s' 正在将 ABRT 崩溃统计记录与该问题单关联 列出可能的事件【以 PREFIX 开头】 日志文件 记录至 syslog 日志程序 在 %s 登录到 Bugzilla 正在退出 配置中未提供登录信息。请输入您的 BZ 登录名: 配置中未提供登录信息。请输入您的 RHTS 登录名: 在库中查找所需软件包 正在 Bugzilla 中寻找类似问题 看起来象是崩溃的 xml 响应，因为缺少 '%s' 成员。 Mailx 连接至 Bugzilla '%s' 的 URL 不规范。 信息标题 缺少必需值 缺少必要项: '%s' N 名称 日志文件名称 需要可写入的目录，但 '%s' 不是可写入目录。将其移动到 '%s'，并在移动后的数据中进行操作。 环境变量 'uReport_ContactEmail' 和配置选项 'ContactEmail' 都未设置 新 Bug id：%i 没有可用描述 没有定义针对事件 `%s' 的处理 没有可用的报告程序 尚未给此类问题指定报告目的地。检查位于 /etc/libreport/* 中的配置文件 无互动：不要提问，假设为“是” 无法上传空白的 uReport 仅通知(不将报告标记为已发送) 确定 在下面的页面中，会询问您该问题是如何发生的，选择如何分析该问题（如果有必要），查看收集的信息，并选择向哪里报告该问题。点击“前进”继续。 错误汇报服务器 URL 输出结果文件 要下载的软件包：{0} 密码 配置中未提供密码。请输入用于 '%s' 的密码: 请添加有关您所遇到问题的详细描述。在这里可以输入大量内容。 请输入要导出问题数据的 URL（scp、ftp 等等）： 请输入需要为其附加数据的问题单号： 请为 '%s//%s@%s' 输入密码： 请输入上传所需密码： 请为 '%s//%s' 输入用户名称： 请提供该问题之简短描述，并包括您重现此问题的步骤。 请提供用来重现此问题的步骤。 请报告此问题给 ABRT 项目开发者。 请在报告前检查数据。取决于选择的报告程序，内容可能会公开可见。 请尝试使用命令: "debuginfo-install %s" 手动安装除错信息并再次尝试。 请输入 %s 的电子邮箱： 探测到可能的敏感数据，请根据需要编辑报告并删除该数据。 首选项 打印具备 DUPHASH 的 BUG_ID 从镜像: '{1!s}' 下载时发生问题 '{0!s}'。尝试下一个 问题描述 问题目录 使用 Fedora 基础架构处理 C/C++ 崩溃 使用红帽基础架构处理 C/C++ 崩溃 使用 Fedora 基础架构处理 Java 异常 使用红帽基础架构处理 Java 异常 使用 Fedora 基础架构处理 X 服务器故障 使用红帽基础架构处理 X 服务器问题 使用 Fedora 基础架构处理内核崩溃 使用红帽基础架构处理内核崩溃 使用 Fedora 基础架构处理内核异常（Oops） 使用红帽基础架构处理内核故障 使用 Fedora 基础架构处理问题 使用红帽基础架构处理问题 使用 Fedora 基础架构处理 Python 异常 使用红帽基础架构处理 Python 异常 使用 Fedora 基础架构处理报告 使用 Red Hat 基础架构处理报告 处理中 处理尚未开始 处理完成 处理失败。 处理结束，请前往下一步骤。 处理结束。 处理被中断: 目录不可写入，无法继续。 处理该问题失败。原因可能有很多种，但最常见的是以下三种情况：
▫ <b>网络连接问题</b>
▫ <b>问题数据受损</b>
▫ <b>无效配置</b> 处理被取消 由于无法报告该问题而中断处理。 处理中…… 向红帽支持提供 crash 的详细数据 提供附加信息 退出 Red Hat 门户网站 URL 收件人 收件人电子邮件 红帽客户支持 Red Hat 客户密码 Red Hat 客户用户名 报告后删除 DIR 报告完成后删除 PROBLEM_DIR 正在删除 {0} 重新报告 报告上传工具 向 Fedora 维护者报告一个 bug 向红帽 Bugzilla 提交 Bug 报告 向 Red Hat 客户门户网站报告一个 bug 报告结果标签不得为空白字符串。 报告结果标签不得包含 ':' 字符。 汇报至 Bugzilla 缺陷跟踪系统 汇报至 Fedora 向红帽 Bugzilla 提交报告 汇报至红帽全球支持 已报告： 正在报告 由于回溯不可用，已禁用汇报。 由于分级栏中不包含数字而禁用报告。 汇报已完成，您现在可以关闭这个窗口了。 访问限制 通过用户组限制可访问 Bug 的用户(了解更多请进入高级选项) 限制报告访问 仅限此组访问 仅限特定组访问 <a href="https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-tickets">?</a> 审核数据 只运行这些事件 SSH 私钥文件 SSH 公钥文件 SSH 私钥文件 SSH 公钥文件 保存为文本文件 搜索 保密服务不可用，您的设置将不会被保存！ 选择要运行的工作流： 选择一个要运行的事件： 选择如何汇报此问题 发送二进制数据 发送类似内核转储的二进制文件 通过电子邮件发送该问题数据 发送到内核错误跟踪程序 通过电子邮件发送 发送者 发送者电子邮件 正在将 %s 发送至 %s//%s 正在发送 ABRT 崩溃统计数据 向 %s 发送通知邮件 发送电子邮件...... 向 FAF 服务器发送 uReports 服务响应错误：'%s' 设定用于 FTP 的代理服务器 设定用于 HTTP 的代理服务器 设定用于 HTTPS 的代理服务器 设置 yum 库 显示日志 显示密码 由于系统故障无法出现，因此很难诊断，请提供您所遇到问题之完整描述。 大小： 指定服务器 URL 只当您使用的产品和 /etc/os-release 中不同时在此处特别指出 只当您所使用产品版本和 /etc/os-release 中不同时在此特别指出 状态：%s%s%s %s/show_bug.cgi?id=%u 字符串好像不是一个日期：'%s' 标题 创建新问题单时提交 <a href="https://access.redhat.com/articles/642323">micro-report</a> 提交匿名故障报告 提交匿名故障报告，使用 -l 是不希望红帽支持团队与其联络。 提交 uReport 创建新问题单前请提交 uReport 正在向 %s 提交内核异常报告 成功创建 %s URL '%s' 不存在(服务器返回错误 404) 回溯是不完整的，请确定您提供了重复该错误的完整步骤。 该回溯可能无法帮助开发者诊断 Bug。 '%s' 已发布有故障的程序。是否要向红帽支持报告这个问题？ 日期：'%s' 包含无法识别的后缀：'%s' 日期：'%s' 在 UNIX 时间戳范围以外 这个问题出现过一次，但尚不了解如何重现此问题。请确保可以为我们的支持团队提供详细信息。要继续并建立新支持问题单吗？ 红帽未提供 '%s'。是否要向红帽报告这个问题？ 报告结果 '%s' 缺少 URL。 报告已被附加至 %s 报告已被保存至 %s 来自 '%s' 的响应包含无效格式 位于 '%s' 的服务器当前无法处理请求(得到错误 503) 位于 '%s' 的服务器遇到内部错误(得知错误 500) 位于 '%s' 的服务器响应错误：'%s' 该问题没有指派一个 uReport。 已报告该问题。 该问题已经汇报至 Bugzilla '%s' ，与预配置 Bugzilla '%s' 不同。 已向 '%s' 报告了这个问题。 该问题尚未汇报至 Bugzilla。 这个问题反复出现 该问题可能不应该汇报 (很有可能为已知问题)。%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/...） 上传并分析 提交问题数据以便进一步分析 提交问题数据至服务器 上传的：%llu kb 中的 %llu 用法： 使用 HTTP 认证 使用用户认证 在您安装附加调试包后使用这个按钮来生成更多回溯信息 如果不想在 URL 中出现密码则请使用这个字段 如果不想在 URL 中出现用户名则请使用这个字段 使用这个字段指定 SSH 私钥文件 使用这个字段指定 SSH 公钥文件 用户名 用户名 使用 Bugzilla ID '%s' 值 确认 SSL 查看/编辑文本文件 警告，已在命令行参数指定私有标签组，忽略环境变量和配置 警告：缓存目录 '{0}' (剩余 {1:.2f}Mb) 中没有足够的空闲空间。继续？ 警告：临时目录 '{0}' (剩余 {1:.2f}Mb)没有足够的空闲空间。继续？ 我们发现一个类似的红帽支持问题单 %s。您是希望为这个问题单附加数据吗？如果不是，您需要提供一个已存在的红帽支持问题单号。 生成 Bug 时也请附加二进制文件 以 login:password@url 格式向其上传附带报告的 tarball 文件的位置 工作流 您正在将文件复制到它本身 您可以在 <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 冲突) 从 reported_to 附加到 bthash (与 -a 冲突) 添加值 （需要 -a|-A 和 -T，与 -L 冲突） 要附加的 uReport 的 bthash (与 -A 冲突) 无法获得 '%s' 的保密值: %s 无法报告 联系电子邮件地址 (需要 -a|-A，与 -E 冲突) 联系来自环境或配置文件中的电邮地址(需要 -a|-A，与 -e 冲突) 数据 f 文件 使用 %d 退出 gzip 使用信号 %d 杀死 gzip gzip 进程失败 已被另一个进程锁住 不是问题目录 拒绝访问 uReport uReport 服务器 URL UID 值无效: '%s' 在 reported_to 中查找 FIELD 时使用 REPORT_RESULT_TYPE（仅可与 -L 配合使用） y