| Server IP : 85.193.89.191 / Your IP : 3.135.211.85 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 : /usr/share/locale/zh_TW/LC_MESSAGES/ |
Upload File : |
�� � � � � 8) � 9) � �) ' t/ �/ �/ Q �/ 0 )0 50 0 A0 r0 0 �0 �0 ( �0 6 �0 1 '1 - G1 u1 � �1 > C2 [ �2 � �3 � e4 _ 5 G h5 � �6 x �8 � 9 �9 �9 �9 �9 �9 : 1: K: e: $ v: �: �: � �: a �; > �; � (< D �< U = 2 p= �= �= �= �= > (> ' E> m> % �> �> �> + �> ? R ? : g? > �? �? , �? @ 2@ K@ " h@
�@ �@ �@ # �@ �@ A !A
'A 3 2A * fA �A B �A �A �A B B ' ;B cB tB
�B $ �B @ �B A �B @C * [C �C �C �C - �C & D ,D LD bD 3 uD 5 �D A �D ' !E IE hE + �E 8 �E Q �E 8 ;F tF / �F �F �F �F G G ; *G fG 5 �G �G �G �G A �G % <H bH
sH �H
�H �H , �H �H �H I Q 'I yI �I �I �I 7 �I �I �I J 0 J \ QJ ' �J �J �J �J $ K ?K ; ^K ^ �K R �K LL bL uL - {L @ �L " �L >
M 0 LM C }M % �M A �M 7 )N # aN " �N �N # �N 1 �N X O X aO �O � �O GP 2 SP �P �P �P �P �P Q Q :Q + SQ 9 Q �Q 8 �Q R !R >R # ]R ? �R �R
�R �R � �R - �S ! �S ) �S �S % T 2 =T 1 pT � �T - pU � �U � SV . W ( HW � qW <X DX UX pX �X > �X 6 �X ; Y NY . jY �Y �Y 7 �Y = �Y 2 -Z . `Z �Z
�Z �Z �Z �Z C �Z E [ + _[ ( �[ B �[ �[ �[ \ -\ E\ a\ c\ h\ a |\ b �\ A] P] ' i] �] Z �] 1 ^ 5^ , T^ �^ � �^ r_ �_ �_ �_ N �_ a ` M b` & �` $ �` $ �` v !a @ �a 6 �a m b a ~b ! �b O c Rc $ ^c O �c �c �c 7 �c 8 1d : jd ; �d < �d = e 8 \e 9 �e 6 �e 7 f 3 >f 4 rf < �f = �f 2 "g 3 Ug
�g �g �g �g 5 �g
h B h � bh -i A Ei
�i �i �i
�i �i �i �i �i j 1j " Lj oj |j �j " �j �j ' �j , �j 2 ,k _k ~k �k �k �k �k 5 �k @ l 6 Ol �l � �l #m " Am � dm �m n n +n ?n Tn hn zn > �n �n �n ! �n o 'o Go go �o �o �o �o " �o # �o p p $ 5p $ Zp % p & �p �p �p
�p � �p �q �q S �q [ r $ _r & �r �r q �r %s P Cs �s ) �s �s �s 7 t Q :t @ �t b �t , 0u . ]u � �u t pv & �v w *w ) Fw E pw @ �w 0 �w / (x ' Xx ` �x + �x /
y =y F \y �y 9 �y �y * �y - z 4 Iz & ~z & �z �z �z # { ' &{ N{ , b{ # �{ �{ �{ �{ �{ d | 9 p| : �| - �| , } @} J} S} j}
p} {} q �} M ~ K Q~ * �~ N �~ ) ! w K # � � � 5 }� 4 �� 1 � $ � * ?� 9 j� �� �� �� �� �� Ă ʂ Ђ ւ ۂ I � 3 6� c j� I 7 � 7 P� / �� " �� ۄ : � a )� �� �� �� �� �� ƅ څ � � � &� 9� P V� �� � �� � =�
�� � � 1� G :� �� �� �� ) �� Џ ߏ � �� � , -� Z� p� ) �� �� � ϐ A �� i Ց � ?� � Ó S l� 1 �� � � | �� � =� ˘ & �
� %� =� ^� }� # �� �� % ʙ
� �� � � b ޚ 7 A� � y� F � ? X� K �� � ( � ,� M� i� �� ( �� ϝ ) ٝ � !� - (� V� N h� 6 �� 7 � &� ' -� U� m� $ �� - �� � % � � & 3� Z� t� �� �� P �� C � 1� 7 I� �� �� �� �� % ̡ � �
� = #� R a� G �� �� 1 � ! I� k� �� . �� У � � � . 7� . f� = �� ( Ӥ �� � + 7� 9 c� E �� 8 � � * :� e� ! �� �� �� Ʀ 9 ܦ ! � = 8� v� �� �� 9 �� / �� *�
=� K� U� \� ! f� �� �� �� M ը #� A� Z� p� 7 w� �� �� �� 0 ө E � J� i� y� ! �� % �� Ԫ @ � e -� ` �� � � � 6 #� S Z� + �� F ڬ 6 !� S X� + �� F ح ? � + _� ) �� �� - �� , � W � Y t� ί � կ [� 3 h� ��
�� �� Ѱ � � )� D� ) _� 7 �� �� 6 ѱ � ! '� ! I� ! k� ? �� Ͳ Բ � � � 0 �� �� ѳ � ' � 4� . S� � �� ' @� � h� � � 1 �� ( � � � �� ŷ ٷ $ � � > 1� I p� 9 �� � & � 9� H� * W� P �� 6 ӹ /
� :� D� U� _� v� I }� E Ǻ !
� ( /� : X� �� # �� �� ʻ ݻ �� � � | � S �� � � & � B� H ^� 9 �� � - �� '� � .� � � '� C� 8 J� < �� @ �� $ � ! &� * H� N s� 3 � 0 �� � '� _ �� " � H /� x� " �� T �� ��
� - � 4 E� , z� - �� 2 �� 1 � , :� 3 g� + �� 3 �� & �� ' "� . J� / y� & �� ' �� �� � � "� ' 2� Z� 6 j� � �� D� - T� �� �� ��
�� �� �� �� ��
� +� ?� ^� o� v� �� �� $ �� * �� . � " J� m� ~� �� �� �� 3 �� 0 � 3 1� e� � r� �� � � -� �� �� �� �� � � /� B� 6 I� ! �� �� ! �� �� ' �� $ � @� `� y� �� �� $ �� # �� � � & 7� ) ^� * �� + �� �� �� � u � �� �� V �� \ �� % \� # �� �� o �� � G 6� ~� # �� �� �� 1 �� K � < [� Y �� 4 �� , '� � T� e � ! f� �� �� & �� B �� = � 1 \� �� �� U �� # !� $ E� j� 5 �� �� 2 �� � 3 � 0 8� 4 i� + �� $ �� �� � ' *� , R� � ' �� ! �� ! �� �� � !� Q @� 8 �� A �� /
� / =� m� }� �� ��
�� �� Z �� [ 1� [ �� 3 �� R � p� 0 }� t �� #� Z B� 6 �� 8 �� ?
� M� # l� 4 ��
��
��
�� ��
��
��
�
� � "� N 5� 4 �� \ �� S � 1 j� / �� 8 �� % � +� = 8� [ v� �� �� �� �� � (� >� T� d� q� y� �� V �� �� � � \ � � � r ( � w = } � � I � � � 1 � G S � . F l � � � F � � � �
l y ' 6 � _ � � z � � L h W 0 � � X � - � � � � o � � i � " V v � � � � g � c | � � ^ � � A ( 7 � R � & c | G � � E � 8 , q j : � 2 f � ] � 2 4 � � ! q � # s " � � b � � Y � 5 � � - � K � � Y � � � � � � � S = � � � * h u � o e � � � � � � m � ' P � � � U N � � � 9 t � e ? k � � � % � � W 7 K � / � ^ � * M
� A � � D � I � � ` � } a � P U � � � > � ; � � � � � � � w X � �
� � � p � � � v 1 6 + � H � Z ? � � + & � 3 � � b � � [ � � � Z � � p R ~ � 0 > � � � � � � � t L � $ � � � � � � a J E � 3 ~ � � � x � � ` s M ) � [ n u _ � � ) y � � � � � � z � � , � < { � j \ H $ k O � V % � ] @ � � � ; B � # � � � � � � � � � � � � � . � � O d � � � � 5 � C < 9 � � � � � � � � � g � � f � � C � � N � Q � n � � � � Q � � i m � � / : � � � 4 B � ! � � � x T � � � T 8 d J D � @ r � � {
�
& [-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 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 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 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 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? 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: 2016-09-01 05:29+0000
Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>
Language-Team: Chinese (Taiwan)
Language: zh_TW
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Plural-Forms: nplurals=1; plural=0
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
將問題回報至 Bugzilla。
本工具會讀取 DIR，接著登入 Bugzilla，並嘗試尋找 'Whiteboard'
欄位中具備相同 abrt_hash:HEXSTRING 的臭蟲回報。
如果找不到這樣的臭蟲報告，則建立新的臭蟲回報。DIR
的元素會儲存在臭蟲回報中，取決於類型與大小，會作為
臭蟲的部份描述或作為附件。
否則，若有找到這樣的臭蟲，則標記為 CLOSED DUPLICATE，
本工具會追尋複本的鏈直到找到非 DUPLICATE 的臭蟲回報。
本工具會將相關資訊以新的評註附加到找到的臭蟲報告中。
新的或修改的臭蟲回報 URL，會列印到 stdout 中，並紀錄
到 'reported_to' 元素內。
選項 -t 會將 FILEs 上傳至 Bugzilla 中已建立的臭蟲回報中。
臭蟲 ID 則從 -d DIR 指定的目錄中擷取。
若放在 DIR 中的問題資料未曾回報至 Bugzilla，則上傳會失敗。
選項 -tID 會將 FILEs 上傳至 Bugzilla 上的指定 ID 臭蟲回報。
-d DIR 則被忽略。
選項 -w 會將 bugzilla 使用者加到臭蟲的 CC 寄件副本清單中。
選項 -r 會將上次 reporter_to element 內前綴為 TRACKER_NAME
的 URL 設定至 URL 欄位中。這個選項僅在提交新臭蟲回報時才會
套用。預設值為 'ABRT Server'
如果未特別指定，CONFFILE 預設值為
報告中未偵測到更動
報告已更新 # 架構 # 追蹤資訊
# 請確認它不包含任何敏感資料 (密碼等等) # 指令列 # 元件 # 核心傾印 # 在下方描述此程式崩潰的情況 # 可執行檔 # 內核版本 # 套件 # 程式崩潰的原因 # 作業系統的發行字串 # 來自根目錄的作業系統發行字串 # 此欄位為唯讀
# os-release 組態檔 # 來自根目錄的 os-release 組態檔 %llu 位元組，%u 個檔案 %s 未正確配置。您可現在為其進行配置或稍後提供必要的資訊。
欲取得更多有關於此配置的相關資訊，請參閱：https://access.redhat.com/site/articles/718083 & [-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] [-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]
上傳微報告或將附件加入至微報告中
從以下位置讀取預設組態： & [-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」不是個正確的檔案名稱 '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 的臭蟲追蹤器名稱 已請求建立私人申請單，但未指定群組，請見 https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-tickets 瞭解更多資訊 可能遺失適當的 debuginfo，或是核心傾印資料已損毀。 等候來自 DBus Secret Service 的提示結果已達時限。 加入 bugzilla 使用者至 [有此 ID 的臭蟲報告] 寄件副本清單 加入程式名稱至記錄中 正將 %s 加入寄件副本 (CC) 清單 正加入外部 URL 至臭蟲 %i 正加入附件至臭蟲 %i 正添加評註至案例「%s」 正新增評註至臭蟲 %d 「auth」金鑰中包含了額外檔案 Bugzilla Red Hat 支援入口的電子郵件地址 uReport 網路服務的位址 進階 允許對 ureport 伺服器的不安全連線 其他 GUI 檔案 於本機分析問題，並將問題資料資訊匯出至一個文字檔案中 於本機分析問題並透過電子郵件傳送資訊 於本機分析問題並透過 SCP 或 FTP 上傳資料 附加 附加新報告或覆寫舊的報告。 附加至或覆寫 FILE 封存檔案已建立：「%s」 向 Red Hat 支援部門尋求協助 附加 FILE [至含有此 ID 的臭蟲報告] 附加檔案 正在附加「%s」至案例「%s」 正附上更好的追蹤資料 正附加問題資料至案例「%s」 「%s」的值錯誤：%s 欲上傳至的基礎 URL 基本 詳盡 Bug %i 已 CLOSED (關閉) 為 DUPLICATE (重複項目)，不過它沒有 DUP_ID Bug %i 已 CLOSED (關閉)，不過沒有 RESOLUTION (解決方案) 臭蟲已回報過：%i Bug.search(quicksearch) 回傳值未包含成員 'bugs' Bugzilla Bugzilla URL Bugzilla 帳號密碼 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}」抽出檔案 無法抽出套件「{0}」 找不到 {0} 個 debuginfo 檔案的套件 無法產生堆疊追蹤描述 (無崩潰的執行序？) 無法取得 Bugzilla ID，因為此問題尚未回報至 Bugzilla。 無法開啟「%s」以寫入。請選擇其他檔案： 無法解析追蹤資訊：%s 無法移除 %s，可能包含錯誤記錄 無法移除「{0}」：{1} 無法設置 {0}: {1}，改停用 無法寫入「{0}」：{1} 取消 被使用者取消。 因為事件名稱無效而無法檢查追蹤資訊評等 無法複製檔案「{0}」：{1} 無法執行 vi：$TERM、$VISUAL 以及 $EDITOR 尚未設置 檢查 SSL 金鑰是否有效 檢查是否有重複 檢查是否有提示 清除搜尋列以查看安全性敏感字串的清單。 將臭蟲 %i 視為臭蟲 %i 的重複並關閉 正在壓縮資料 配置 %s(_F) 組態檔 組態 組態檔 組態檔 (可能會提供多次) uReport 的配置檔案 確認欲回報的資料 聯絡人電子郵件地址 建立新的 Red Hat 支援案例 – 我希望 Red Hat 支援部門聯絡我 在 DIR 中建立 reported_to 建立新的臭蟲回報 正在建立新案例 自訂 D-Bus Secrets Service ReadAlias('%s') 方法失敗：%s 除錯 詳情 顯示版本並離開 您仍然想建立 RHTSupport 的申請單嗎？ 您想要停止等候並繼續回報，但卻未適當載入組態？ 可能有所相關的文件： 不要再問我 不要儲存密碼 下載程序已被使用者中斷 正在下載 ({0} / {1}) {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}' 擷取 metadata 時發生錯誤：'{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} 抽取 cpio FTP 代理 提交問題時失敗 無法關閉 TAR 寫入器 建立新臭蟲回報失敗。 無法完成 TAR 封存檔案 無法開啟 TAR 寫入器 無法儲存檔案「%s」 無法上傳 uReport 至伺服器「%s」 無法以 curl 上傳 uReport 至伺服器「%s」：%s 禁止的字串 即使此問題已經回報過，仍然回報此問題 正為新案例格式化檔案 正為電子郵件格式化檔案 正為重複項目格式化檔案 正為初次評註格式化檔案 在臭蟲歷史中尋找同樣的評註，而不是新增評註 群組 HTTP 代理 HTTPS 代理 這問題是怎麼發生的 (詳述步驟)？如何再次產生此問題？任何說明可以幫助我們診斷問題？請儘可能使用英文。 可以如何重現問題 (每行一個步驟)？ 這個問題容易重現嗎？ 您希望如何回報問題？ 我可以重現這個問題 我不知道這問題是什麼造成的 我第一次遇到這個問題 我已檢視資料，並同意提交資料(_A) 如果您已回報了遠端伺服器，請確定您已移除所有私人資料 (例如使用者名稱與密碼)。追蹤資訊、指令列、環境變數等通常是需要檢視的東西。 若您不知道如何描述，您可以 若您希望將問題回報至不同的目的地，請蒐集額外資訊，或提供較詳盡的問題描述、重複回報程序，並按下「下一步」。 若您希望更新配置並重新嘗試回報，請開啟應用程式選單中的<b>偏好設定</b>
項目，並在套用配置變更之後按下<b>重複</b>按鈕。 已忽略報告結果「%s」的無效 ISO 日期 忽略沒有格式和主機名稱的 URL 若要啟用內建的 screencasting 功能，您必須先安裝 fros-gnome 套件。若您希望執行此套件，請執行下列指令。
<b>su -c "yum install fros-gnome"</b> 包含 正在初始化 yum 無效的布林值「%s」 無效的輸入，正離開程式。 無效的數字「%s」 無效的密碼或登入名稱。請輸入「%s」的密碼： 無效的密碼或登入名稱。請輸入您的 Bugzilla 登入資訊： 密碼或帳號無效。請輸入您的 Red Hat 帳號： 無效的 utf8 字元「%c」 項目「%s」已存在，無法修改 Kerneloops URL Kerneloops.org 瞭解更多有關組態中的受限存取 正在為 ABRT 當機數據紀錄與聯絡人電子郵件進行連結：「%s」 正在為 ABRT 當機數據紀錄與案例進行連結 列出可能的事件 [以 PREFIX 作為開頭] 記錄檔 紀錄至 syslog 紀錄器 登入 Bugzilla 於 %s 登出 登入資訊未由組態提供。請輸入您的 Bugzilla 登入資訊： 登入資訊未由組態提供。請輸入您的 RHTS 登入資訊： 從軟體庫中尋找所需套件 查詢 bugzilla 中是否有類似問題 看似損毀的 xml 回應，因為「%s」成員遺失。 Mailx 格式不良的 Bugzilla「%s」URL 訊息主旨 遺失必要的值 遺失需要的項目：「%s」 否(N) 名稱 記錄檔的名稱 需要可寫入的目錄，但「%s」並不是可寫入的目錄。將它移到「%s」並在移動後的資料中操作。 環境變數「uReport_ContactEmail」與組態選項「ContactEmail」皆未設定 新的臭蟲 ID：%i 沒有可用的描述 未定義「%s」事件的處理動作 沒有可用的回報程式 此問題未定義回報目標。請確認 /etc/libreport/* 中的組態 非互動式：不詢問問題，假設答案為「是」 不上傳空白 uReport 僅通知 (不要將回報標記為已送出) 確定 在接下來的畫面上，您將會被要求描述問題如何發生、選擇如何分析問題 (若有需要)、檢視蒐集的資料，以及選擇問題該向哪回報。請按下「下一步」以繼續進行。 Oops 伺服器 url 輸出檔案 要下載的軟體包：{0} 密碼 密碼未由組態提供。請輸入「%s」的密碼： 請加入問題的完整描述，這個預留位置很長。 請輸入要在其中匯入問題資料的 URL (scp, ftp 等)： 請輸入「%s//%s@%s」的密碼： 請輸入密碼以進行上傳： 請輸入「%s//%s」的使用者名稱： 請簡短描述問題，並請包括您在重現問題時所採取的步驟。 請提供您在重現問題時所採取的步驟。 請將此問題回報給 ABRT 專案開發者。 在問題回報之前，請先檢視資料。根據回報者的選擇而定，您提供的資料最後可能供大眾公開檢視。 請試著使用指令："debuginfo-install %s" 來手動安裝 debugifo，並再重試一次。 請輸入 %s 的電子信箱位址 已偵測到可能的敏感資料，請視需求編輯與移除報告。 偏好設定 列印具給定 DUPHASH 的 BUG_ID 當從鏡像站下載資料時遭遇問題「{0!s}」：'{1!s}'。改嘗試下一站 問題描述 問題目錄 使用 Fedora 基礎設施處理 C/C++ 崩潰 使用 Red Hat 基礎架構處理 C/C++ 崩潰問題 使用 Fedora 基礎設施處理 Java 例外 使用 Red Hat 基礎架構處理 Java 例外 使用 Fedora 基礎設施處理 X 伺服器問題 使用 Red Hat 基礎架構處理 X Server 問題 使用 Fedora 基礎設施處理內核崩潰 使用 Red Hat 基礎架構處理內核崩潰問題 使用 Fedora 基礎設施處理 kerneloops 使用 Red Hat 基礎架構處理 kerneloops 回報 使用 Fedora 基礎設施處理問題 使用 Red Hat 基礎架構處理問題 使用 Fedora 基礎設施處理 python 例外 使用 Red Hat 基礎架構處理 python 例外 使用 Fedora 基礎架構處理回報 使用 Red Hat 基礎設施處理回報 處理中 尚未開始處理 處理完成 處理失敗。 處理完成，請繼續下個步驟。 處理完成。 處理中斷：若無可寫入的目錄便無法繼續 處理問題失敗。這有許多原因，然而最常見的原因如下：
▫ <b>網路連線問題</b>
▫ <b>問題資料損毀</b>
▫ <b>配置無效</b> 已取消處理 處理程序因問題無法回報而中斷。 處理中... 提供額外資訊 退出 RH 入口 URL 收件者 收件者電子郵件地址 Red Hat 客戶支援服務 Red Hat 客戶密碼 Red Hat 客戶使用者名稱 回報後移除 DIR 在回報後移除 PROBLEM_DIR 正在移除 {0} 重複 報告上傳程式 回報臭蟲給 Fedora 維護者 回報臭蟲給 Red Hat Bugzilla 回報臭蟲給 Red Hat 客戶入口 報告結果標籤不可為空白字串。 報告結果標籤不可含有「:」字元。 回報至 Bugzilla 臭蟲追蹤器 回報至 Fedora 回報至 Red Hat Bugzilla 向 Red Hat 支援部門回報 已回報： 回報 已停用回報，因為無法使用追蹤功能。 回報已停用，因為評分未包含數字。 回報已完成。您現在可將此視窗關閉。 限制存取 限制所建立的 bugzilla 申請單之存取狀況，僅讓特定群組的使用者可以檢視 (請見進階設定瞭解更多細節) 限制報告的存取 限制僅有群組可存取 限制只讓特定群組存取 <a href="https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-tickets">?</a> 檢視資料 僅執行這些事件 SSH 私密金鑰檔案 SSH 公開金鑰檔案 SSH 私密金鑰檔案 SSH 公開金鑰檔案 儲存成文字檔 搜尋 無法使用祕密服務，不會儲存您的設定！ 選取要執行的工作流程： 選取要執行的事件： 請選取回報此問題的方式 傳送二元資料 傳送類似核心傾印的二元檔案 透過電子郵件傳送問題資料 傳送給 kernel oops 追蹤器 透過電子郵件傳送 寄件者 寄件者電子郵件地址 將 %s 傳送至 %s//%s 正在傳送 ABRT 當機數據資料 將通知電子郵件傳送至：%s 傳送電子郵件... 傳送 ureport 至 FAF 伺服器 伺服器端以錯誤回應：「%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>。 提交匿名當機報告 提交匿名當機報告 – 我不希望 Red Hat 支援部門聯絡我 提交 uReport 建立新案例前先提交 uReport 傳送 oops 報告至 %s 已成功建立 %s URL「%s」不存在 (伺服器給予 404 錯誤) 追蹤資訊不完整，請確認您已提供能夠重現問題的步驟。 追蹤資訊可能無法幫助開發者診斷臭蟲所在。 當機程式已由「%s」釋出。您是否要將問題回報給 Red Hat 支援部門？ 日期「%s」含有無法辨識的尾碼：「%s」 日期「%s」超出 UNIX 時間戳記範圍 問題只出現一次，且不確定是否能重現問題。請確認您能夠提供詳細資訊給我們的支援團隊。您是否要繼續並開立新的支援案例？ 程式「%s」似乎不是由 Red Hat 提供。您是否要將問題回報給 Red Hat 支援部門？ 報告結果「%s」缺少 URL。 報告已附加至 %s 報告已儲存至 %s 「%s」給予的回應為無效格式 「%s」的伺服器目前無法處理請求 (取得錯誤碼 503) 於「%s」的伺服器遭遇內部錯誤 (得到 500 錯誤) 於「%s」的伺服器以錯誤回應：「%s」 此問題沒有指派 uReport。 此問題已被回報過。 此問題尚未回報至 Bugzilla「%s」，而不是設定中的 Bugzilla「%s」。 此問題尚未回報至「%s」。 此問題尚未回報至 Bugzilla。 這個問題重複出現 此問題不應回報 (這很類似已知問題)。%s 申請單/專案 ID 偵測到「%s」的回應中其類型並不相符 URL 無法於 bugzilla URL「%s」中找到臭蟲 ID。 無法從 bugzilla URL「%s」解析臭蟲 ID。 無法解析來自「%s」ureport 伺服器的回應 「%s」傳來未預期的 HTTP 回應：%d 解壓縮失敗，放棄下載…… 不受支援的選項類型 可能有所幫助的更新： 上傳 FILE [至含有此 ID 的案例] 以 tar.gz 檔案上傳 (透過 FTP/SCP/...) 上傳以供分析 上傳問題資料以供進一步分析 將問題資料上傳至伺服器 已上傳：%llu / %llu 位元組 使用方法： 使用 HTTP 認證 使用者客戶端身份核對 使用此按鈕讓您在安裝額外的除錯套件後，產生更多追蹤訊息 若您不希望 URL 中包含密碼，請使用此欄位 若您不希望 URL 中包含使用者名稱，請使用此欄位 使用此欄位以指定 SSH 私密金鑰檔案 使用此欄位以指定 SSH 公開金鑰檔案 使用者名稱 使用者名稱 正使用 Bugzilla ID「%s」 值 驗證 SSL 檢視或編輯文字檔案 警告，私人請單群組已指定成 cmdline 引數，忽略環境變數與組態設定 警告：快取目錄「{0}」中的可用空間不足 (剩下 {1:.2f}Mb)。是否繼續？ 警告：暫存目錄「{0}」中的可用空間不足 (剩下 {1:.2f}Mb)。是否繼續？ 當建立臭蟲回報時，亦請附加二元檔案 您希望將含有報告的 tarball，以 login:password@url 格式上傳到何處 工作流程 您正試著將檔案複製到檔案自身之上 您可建立 bugzilla.redhat.com 帳號 <a href="https://bugzilla.redhat.com/createaccount.cgi">here</a> 您選擇的數目超出範圍 您已請求只允許特定群組存取您的資料，而此臭蟲是 %s/%u 的重複臭蟲。如果臭蟲重複，新的評註便會加到原始的臭蟲報告中，但評註無法限制只供特定群組存取。您是否要開始新的臭蟲報告，並將其視為原始報告的重複項來關閉？否則，臭蟲報告程序將會終止。 在繼續進行之前，您必須填入相關資訊... 您需要指定要加入附件的 uReport 其 bthash。 您必須指定臭蟲 ID、聯絡人電子郵件，或這兩者 您的輸入無效，因為： 您的問題似乎起因於 %s
%s
您的問題似乎由下列問題之一所導致：
取消(_C) 關閉(_C) 前進(_F) 否(_N) 確定(_O) 開啟(_O) 儲存(_S) 停止(_S) 是(_Y) 加入螢幕執演 附加 DATA 作為 ureporte 附件 ATTACHMENT_TYPE (僅與 -l|-L 搭配使用) 附上 RHBZ 臭蟲 (需要 -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)