Þ•í„“ì8)¹9)€ó)'t/œ/¹/QÈ/0 )0 500A0 r00 0š0(¬06Õ0 1'1-G1u1¸Š1>C2[‚2†Þ3¢e4_5Gh5×°6xˆ8‡9‰9¦9Ä9Û9ú9:1:K:e:$v:›:ª:ɽ:a‡;>é;¬(<DÕ<U=2p=£=¼=Ñ=ï= >(>'E>m>%ˆ>®>Ì>+Õ>?R?:g?>¢?á?,è?@2@K@"h@ ‹@™@µ@#Ð@ô@ A!A 'A32A*fA‘AB­AðA ùAB B';BcBtB B$˜B@½BAþB@C*[C†C£CÃC-×C&D,DLDbD3uD5©DAßD'!EIEhE+„E8°EQéE8;FtF/ŽF¾FÖFöFGG;*GfG5‚G¸GÏGçGAúG% M0LMC}M%ÁMAçM7)N#aN"…N ¨N#²N1ÖNXOXaOºO…ÁO GP2SP†P ŸP ©PÊPåPQ Q:Q+SQ9Q¹Q8ÉQR!R>R#]R?RÁR ÈR ÓR ßR-€S!®S)ÐSúS%T2=T1pTÍ¢T-pU´žUÅSV.W(HWÊqWœX6ÛX;YNY.jY™Y¨Y7·Y=ïY2-Z.`ZZ ˜Z¦Z­Z ÉZCÕZE[+_[(‹[B´[÷[ý[\-\E\a\c\h\a|\bÞ\A]P]'i]‘]Z¨]1^5^,T^^í„^r_ ‚_Ž_¨_N±_a`Mb`&°`$×`$ü`v!a@˜a6Ùamba~b!àbOc Rc$^cOƒcÓcçc7ùc81d:jd;¥d<ád=e8\e9•e6Ïe7f3>f4rf<§f=äf2"g3Ug ‰g”g±gÁg5Ôg hBhÊbh-iAEi ‡i•i´i ¹i ÇiÑiãiüij1j"Lj oj|jƒj"“j ¶j'×j,ÿj2,k_k~kkªk Äk Îk5Øk@l6Ol†lŒ–l#m"Am‹dmðmnn+n?nTnhnzn>nÀnÛn!ôno'oGogoƒo’o™o¨o"½o#àopp$5p$Zp%p&¥pÌpèp ñp–ÿp–qœqS¯q[r$_r&„r«rq³r%sPCs”s)£sÍsês7tQ:t@ŒtbÍt,0u.]uãŒutpv&åv w*w)FwEpw@¶w0÷w/(x'Xx`€x+áx/ y=yF\y£y9²yìy*ðy-z4Iz&~z&¥zÌzäz#{'&{N{,b{#{³{Ñ{Ù{ñ{d |9p|:ª|-å|,} @}J}S}j} p}{}q‘}M~KQ~*~NÈ~ )!wK#Õç5}4³1è$‚*?‚9j‚¤‚¬‚³‚¼‚À‚Ä‚Ê‚ЂÖ‚Û‚Iì‚36ƒcjƒI΃7„7P„/ˆ„"¸„Û„:î„a)…‹……’…—…«…Æ…Ú…ô… ††&†9†PV†§†u©†æˆ‰>##b†p• ‘‘"‘G2‘z‘‰‘ ™‘¥‘#¸‘;Ü‘ ’9’2T’‡’ö¢’O™“­é“Í—•Çe–g-—¬•—ëB™Š.›‡¹›+Aœ3mœ¡œ4½œ#òœ0&G*n™>ª éö  ž~ŸA–ŸÕØŸ`® k¡A{¡%½¡ã¡!ú¡.¢*K¢(v¢%Ÿ¢Å¢Ý¢û¢£) £J£_]£>½£Pü£M¤KU¤ ¡¤ ¤ã¤)ÿ¤)¥'8¥-`¥4Ž¥!Ã¥å¥þ¥¦\¦Yz¦%Ô¦\ú¦ W§ a§o§!‡§B©§ì§ü§ ¨6¨fU¨\¼¨,©?F©1†©.¸©+ç©>ª1Rª+„ª*°ª ÛªEüªFB«{‰«G¬+M¬3y¬Q­¬Sÿ¬iS­Z½­2®QK®'®9Å®"ÿ®"¯!*¯\L¯3©¯\ݯ:°T°g°Ty°7ΰ± ±*±9±@±/O±±˜±´±]ϱ-²H²_²x²I‰² Ó² Þ²ì²9³i@³#ª³γ$ê³:´)J´1t´W¦´“þ´m’µ&¶ '¶5¶7=¶Lu¶*¶Kí¶39·Hm·&¶·FÝ·5$¸JZ¸M¥¸ ó¸Hþ¸SG¹y›¹yº º€™º»8+»d» »»¢»(»»ä»þ»(¼:@¼I{¼żPÖ¼*'½R½;r½>®½^í½L¾S¾b¾Òr¾GE¿+¿.¹¿$è¿. À3<ÀEpÀç¶ÀQžÁÆðÁÔ·ÂCŒÃ,ÐÃÔýÃÒÄÚÄíÄ-Å6ÅWNÅU¦ÅZüÅWÆOtÆÄÆÔÆ?äÆQ$Ç;vÇB²ÇõÇÈÈ#ÈBÈfQÈa¸È8É-SÉ^ÉàÉ5çÉÊ/Ê3EÊyÊ{Ê‚Ê›˜Êl4Ë¡Ë!´Ë7ÖË+Ì{:Ì7¶Ì+îÌAÍ\Í'dÍŒÎγÎÒÎkÚÎaFÏM¨Ï,öÏ1#Ð3UÐj‰ÐEôÐ::ÑouÑ{åÑ1aÒ{“Ò Ó)ÓwGÓ¿ÓÎÓ:ãÓ;Ô6ZÔ7‘Ô;ÉÔ<Õ;BÕ<~Õ5»Õ6ñÕ1(Ö2ZÖ8Ö9ÆÖ4×/5× e×5o× ¥×$³×LØ×'%ØnMؼØ&ÃÙPêÙ ;ÚIÚ_ÚgÚvÚ…Ú¡Ú¸Ú ÏÚðÚÛ&Û 6ÛDÛ.XÛ"‡Û&ªÛ6ÑÛ?Ü$HÜmÜ~Ü™Ü ¶ÜÁÜZÉÜc$ÝVˆÝßÝ«ðÝ œÞ0½Þ‹îÞzߌߧ߽ßÓßéßÿßàT#àxà—à4³àèà2á+:á)fáá¥á·áÖá&ñáâ8âQâ-oâ/â,Íâ-úâ(ãHãWãœkãää[#äbä$âä=åEå…Må'Óånûåjæ4yæ#®æ/Òæ;çq>ç_°ç|èAèCÏè×é‘ëé6}ê'´ê'Üê8ëC=ëCë>Åë=ì'Bì_jì7Êì;í)>íUhí¾íKÐíî9!îC[îHŸî+èîGï"\ï'ï,§ï3Ôïð5#ð$Yð-~ð ¬ð¸ðËð|éðHfñR¯ñ8ò6;òrò„ò•ò­ò ²ò¾ò~Þòz]ó{Øó9TôeŽô ôô5õŽ7õ4Æõìûõ;è÷6$øT[ø@°ø;ñøP-ù ~ù Šù –ù¡ù°ù ´ù ¿ù ËùÖùÞùFøù0?úapúIÒú2û1Oû*û1¬ûÞû8úû^3ü ’üœüžü#¥ü*Éüôü3 ý#Aýeýyýý*”ýQ¿ýþ½Ì\Æð¤r(Çw=}‰ÓI™ÜË1œGSâ.Fl°¸÷Fãþö¨ ly'6˜_àºz¶ˆLhW0ÑŒX²-ͫîoêæi¼"Vv–×¹ gc|ÚÐ^£ëA(7ïRí&c|GìçEÆ8,qj:Ï2f£]¼24 Áƒ!qÄ#s"Èb¬‡YÊ5ÅÏ-úKäÂY‡Ž·ÈéÍÙS=€ ñÀ*huãoeß¾ÒçÑ»m›'P©Ÿ±UN¦åä9t½e?k´õž %ÀÁW7Kà/á^«* M ÚA»êDÒI„Ê`”}a…PU•ò>—; ³ÙÇ—ÓœÎwXƒÕ Û¬épü ·³v16+ˆH…Z?ÖÝ+&Ü3™§bá‚[‘ŽØZâëpR~ó0>í²ù°¢èžtLÔ$”æ­ÉaJEè3~„‚†xÿ`sM)Š[nu_¨Ì)y‹Õ šŸ¾zÎÅ,É<{ýj\H$kOµV%Û]@¢‹‰;B¡#´˜Ë“¦ŒØ‘§€¿¥¹.×ÝOd î±›5šC<9©¯å’ìøû†g–¥f®CÞºNÖQ­n¸“ĵQ•ªimÞ/:¶’ª4B!ÿßôxTСT8dJD¯@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 ---%s is not properly configured. You can configure it now or provide the required information later. Read more about the configurationYour 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 attachments to bug %iAdding comment to case '%s'Adding new comment to bug %dAdditional files included in 'auth' keyAddress of Bugzilla serverAddress of the Red Hat support portalAddress of uReport webserviceAdvancedAllow insecure connection to ureport serverAlternate GUI fileAnalyze 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 a fileAttaching '%s' to case '%s'Attaching better backtraceAttaching problem data to case '%s'Bad value for '%s': %sBase URL to upload toBasicBe verboseBug %i is CLOSED as DUPLICATE, but it has no DUP_IDBug %i is CLOSED, but it has no RESOLUTIONBug is already reported: %iBug.search(quicksearch) return value did not contain member 'bugs'BugzillaBugzilla URLBugzilla account passwordBugzilla account user nameBugzilla couldn't find parent of bug %dBugzilla productBugzilla product versionC_onfigureCaching files from {0} made from {1}Can't call method '%s' over DBus on path '%s' interface '%s': %sCan't connect over DBus to name '%s' path '%s' interface '%s': %sCan't continue without URLCan't continue without email address of %sCan't continue without loginCan't continue without passwordCan't copy '%s': %sCan't create a secret item for event '%s': %sCan't create a temporary directory in Can't create temporary file in Can't delete '%s': %sCan't delete: '%s'Can't determine Bugzilla Product from problem data.Can't determine RH Support Product from problem data.Can't disable async download, the output might contain artifacts!Can't disable repository '{0!s}': {1!s}Can't extract files from '{0}'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 open '%s' for writing. Please select another file:Can't parse backtrace: %sCan't remove %s, probably contains an error logCan't remove '{0}': {1}Can't setup {0}: {1}, disablingCan't write to '{0}': {1}CancelCancelled by user.Cannot check backtrace rating because of invalid event nameCannot copy file '{0}': {1}Cannot run vi: $TERM, $VISUAL and $EDITOR are not setCheck 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 dataCon_figure %sConfig 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 caseCustomD-Bus Secrets Service ReadAlias('%s') method failed: %sDebugDetailsDisplay 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?Email 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: %sEmergency analysisErrorError in case creation at '%s', HTTP code: %dError in case creation at '%s', HTTP code: %d, server says: '%s'Error in case creation at '%s': %sError in case creation at '%s': no Location URL, HTTP code: %dError in comment creation at '%s', HTTP code: %dError in comment creation at '%s', HTTP code: %d, server says: '%s'Error in comment creation at '%s': %sError in comment creation at '%s': no Location URL, HTTP code: %dError initializing yum (YumBase.doConfigSetup): '{0!s}'Error retrieving filelists: '{0!s}'Error retrieving metadata: '{0!s}'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 information to a text fileExtracting cpio from {0}FTP ProxyFailed on submitting the problemFailed to close TAR writerFailed to create a new bug.Failed to finalize TAR archiveFailed to open TAR writerFailed to save file '%s'Failed to upload uReport to the server '%s'Failed to upload uReport to the server '%s' with curl: %sForbidden wordsForce reporting even if this problem is already reportedFormatting file for a new caseFormatting file for an emailFormatting file for duplicatesFormatting file for initial commentFound the same comment in the bug 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 don't know how to describe it, you canIf 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 hostnameIn 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. su -c "yum install fros-gnome"IncludeInitializing yumInvalid 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 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 BZ login:Login is not provided by configuration. Please enter your RHTS login:Looking for needed packages in repositoriesLooking for similar problems in bugzillaLooks like corrupted xml response, because '%s' member is missing.MailxMalformed url to Bugzilla '%s'.Message subjectMissing mandatory valueMissing required item: '%s'NNameName of the logfileNeed writable directory, but '%s' is not writable. Move it to '%s' and operate on the moved data?Neither environment variable 'uReport_ContactEmail' nor configuration option 'ContactEmail' is setNew bug id: %iNo description availableNo processing for event '%s' is definedNo reporters availableNo reporting targets are defined for this problem. Check configuration in /etc/libreport/*Noninteractive: don't ask questions, assume 'yes'Not uploading an empty uReportNotify only (Do not mark the report as sent)OkOn the following screens, you will be asked to describe how the problem occurred, to choose how to analyze the problem (if needed), to review collected data, and to choose where the problem should be reported. Click 'Forward' to proceed.Oops server urlOutput filePackages to download: {0}PasswordPassword is not provided by configuration. Please enter the password for '%s':Please add a comprehensive description of the problem you have. This is a very long place holder.Please enter a URL (scp, ftp, etc.) where the problem data is to be exported:Please enter password for '%s//%s@%s':Please enter password for uploading:Please enter 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.PreferencesPrint BUG_ID which has given DUPHASHProblem '{0!s}' occured while downloading from mirror: '{1!s}'. Trying next oneProblem descriptionProblem directoryProcess the C/C++ crash using the Fedora infrastructureProcess the C/C++ crash using the Red Hat infrastructureProcess the Java exception using the Fedora infrastructureProcess the Java exception using the Red Hat infrastructureProcess the X Server problem using the Fedora infrastructureProcess the X Server problem using the Red Hat infrastructureProcess the kernel crash using the Fedora infrastructureProcess the kernel crash using the Red Hat infrastructureProcess the kerneloops using the Fedora infrastructureProcess the kerneloops using the Red Hat infrastructureProcess the problem using the Fedora infrastructureProcess the problem using the Red Hat infrastructureProcess the python exception using the Fedora infrastructureProcess the python exception using the Red Hat infrastructureProcess the report using the Fedora infrastructureProcess the report using the Red Hat infrastructureProcessingProcessing did not start yetProcessing doneProcessing failed.Processing finished, please proceed to the next step.Processing finished.Processing interrupted: can't continue without writable directory.Processing of the problem failed. This can have many reasons but there are three most common: â–« network connection problems â–« corrupted problem data â–« invalid configurationProcessing was canceledProcessing was interrupted because the problem is not reportable.Processing...Provide additional informationQuitRH Portal URLRecipientRecipient's emailRed Hat Customer SupportRed Hat customer passwordRed Hat customer user nameRemove DIR after reportingRemove PROBLEM_DIR after reportingRemoving {0}RepeatReport UploaderReport a bug to Fedora maintainersReport a bug to Red Hat BugzillaReport a bug to Red Hat Customer PortalReport result label mustn't be empty string.Report result label mustn't contain ':' character.Report to Bugzilla bug trackerReport to FedoraReport to Red Hat BugzillaReport to Red Hat supportReported:ReportingReporting 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 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 eventsSSH 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 serverServer 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 yum 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 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-releaseStatus: %s%s%s %s/show_bug.cgi?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 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 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 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). %sTicket/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 for analysisUpload the problem data for further analysisUpload the problem data to a serverUploaded: %llu of %llu kbytesUsage: Use HTTP AuthenticationUse client authenticationUse this button to generate more informative backtrace after you installed additional debug packagesUse 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'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?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 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 or bothYour 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_Yesadd a screencastattach 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': %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)dataffilegzip 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: POT-Creation-Date: 2019-10-01 17:40+0200 PO-Revision-Date: 2016-08-22 06:40+0000 Last-Translator: Eun-Ju Kim Language-Team: Korean Language: ko 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를 사용하여 Bugzilla 사ì´íŠ¸ì— 있는 ì´ë¯¸ ìž‘ì„±ëœ ë²„ê·¸ì— FILEì„ ì—…ë¡œë“œí•©ë‹ˆë‹¤. 버그 IDê°€ -d DIRë¡œ ì§€ì •ëœ ë””ë ‰í† ë¦¬ì—ì„œ 검색ë©ë‹ˆë‹¤. DIRì— ìžˆëŠ” 문제 ë°ì´í„°ê°€ Bugzillaì— ë³´ê³ ë˜ì§€ ì•Šì€ ê²½ìš° 업로드를 실패하게 ë©ë‹ˆë‹¤. 옵션 -tID를 사용하여 Bugzilla 사ì´íŠ¸ì—ì„œ ì§€ì •ëœ IDê°€ 있는 ë²„ê·¸ì— FILEì„ ì—…ë¡œë“œí•©ë‹ˆë‹¤. -d DIR는 무시ë©ë‹ˆë‹¤. 옵션 -w를 사용하여 ë²„ê·¸ì˜ CC 목ë¡ì— bugzilla 사용ìžë¥¼ 추가합니다. 옵션 -rì„ ì‚¬ìš©í•˜ì—¬ URL í•„ë“œì˜ TRACKER_NAME ì•žì— ë¶™ëŠ” reporter_to 요소ì—ì„œ 마지막으로 ì ‘ì†í•œ urlì„ ì„¤ì •í•©ë‹ˆë‹¤. ì´ ì˜µì…˜ì€ ìƒˆë¡œìš´ 버그가 ìž‘ì„±ëœ ê²½ìš°ì—만 ì ìš©ë©ë‹ˆë‹¤. ê¸°ë³¸ê°’ì€ 'ABRT Server'입니다. 지정ë˜ì–´ 있지 ì•Šì„ ê²½ìš° CONFFILEì´ ê¸°ë³¸ê°’ì´ ë©ë‹ˆë‹¤ ë³´ê³ ì„œì—ì„œ 변경 ì‚¬í•­ì„ ê°ì§€í•˜ì§€ 못했습니다 보고서가 변경ë˜ì—ˆìŠµë‹ˆë‹¤# 아키í…처# 백트레ì´ìŠ¤ # ê°œì¸ì—게 민ê°í•œ 정보를 í¬í•¨í•˜ì§€ëŠ” 않았는지 검토하십시오(암호 등)# 명령 í–‰# 구성요소# 코어 ë¤í”„# ì´ë²ˆ í¬ëž˜ì‹œê°€ ë°œìƒí•œ í™˜ê²½ì„ ì•„ëž˜ì— ì„¤ëª…í•˜ì‹­ì‹œì˜¤.# 실행파ì¼# ì»¤ë„ ë²„ì „# 패키지# í¬ëž˜ì‹œ ì›ì¸# ìš´ì˜ ì²´ì œ 릴리즈 문ìžì—´# root 디렉토리ì—ì„œ ìš´ì˜ ì²´ì œ 릴리즈 문ìžì—´# ì½ê¸° ì „ìš© 필드입니다 # os-release 설정 파ì¼# root 디렉토리ì—ì„œ os-release 설정 파ì¼%llu ë°”ì´íŠ¸, %u íŒŒì¼ %sì´/ê°€ 올바르게 설정ë˜ì–´ 있지 않습니다. 지금 설정한 후 ë‚˜ì¤‘ì— í•„ìš”í•œ 정보를 입력할 수 있습니다. ì„¤ì •ì— ëŒ€í•œ ìžì„¸í•œ ë‚´ìš©ì€ https://access.redhat.com/site/articles/718083ì—ì„œ 참조하십시오.& [-d] DIR 지정한 DIRì— ì €ìž¥ëœ ë¬¸ì œë¥¼ë³´ê³ í•˜ê¸° 위한 newt ë„구& [-v] --target TARGET --ticket ID FILE... TARGETì— ì§€ì •ëœ í‹°ì¼“ì— FILEì„ ì—…ë¡œë“œí•©ë‹ˆë‹¤. ì´ ë„구는 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ì˜ ì••ì¶•ëœ íƒ€ë³¼ì„ URLì— ì—…ë¡œë“œí•©ë‹ˆë‹¤. URLì´ ì§€ì •ë˜ì–´ 있지 ì•Šì„ ê²½ìš° íƒ€ë³¼ì„ ìƒì„±í•©ë‹ˆë‹¤ & [-v] -d DIR [-o FILE] [-a yes/no] [-r] 문제 ë‚´ìš©ì„ í‘œì¤€ 출력ì´ë‚˜ FILEë¡œ 출력합니다 & [-v] [-c CONFFILE]... -d DIR kerneloops.org (ë˜ëŠ” 유사한) 사ì´íŠ¸ì— ì»¤ë„ oops를 보고합니다. $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] micro report를 업로드하거나 micro reportì— ì²¨ë¶€ 파ì¼ì„ 추가합니다 기본 ì„¤ì •ì„ ë¶ˆëŸ¬ì˜µë‹ˆë‹¤& [-vpdx] [-e EVENT]... [-g GUI_FILE] PROBLEM_DIR ì§€ì •ëœ 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(으)ë¡œ 종료ë¨) (ì‹œê·¸ë„ %uì— ì˜í•´ '%s'ì´/ê°€ ì¢…ë£Œë¨ ) (ë°”ì´ë„ˆë¦¬ 파ì¼, %llu ë°”ì´íŠ¸) (보기/편집하려면 여기를 í´ë¦­) (설명 ì—†ìŒ) (필요하지 ì•ŠìŒ, ë°ì´í„°ê°€ ì´ë¯¸ 존재합니다: %s)(필수: %s)-- %s 실행 중--- %sì´/ê°€ 올바르게 설정ë˜ì–´ 있지 않습니다. 지금 설정한 후 ë‚˜ì¤‘ì— í•„ìš”í•œ 정보를 입력할 수 있습니다. ì—ì„œ ì„¤ì •ì— ëŒ€í•œ ìžì„¸í•œ ë‚´ìš©ì„ ì°¸ì¡°í•˜ì‹­ì‹œì˜¤ê·€í•˜ì˜ ì˜ê²¬ì€ 비공개ë˜ì§€ 않습니다. ì´ëŠ” 공개ë˜ì–´ ë³¼ 수 있는 문제 ë³´ê³ ì— í¬í•¨ë©ë‹ˆë‹¤. 'reported_to'ì—ì„œ 추가 URLì„ ìœ„í•œ 버그 트래커 ì´ë¦„ 비공개 티켓 ìƒì„±ì´ 요청ë˜ì—ˆì§€ë§Œ ê·¸ë£¹ì´ ì§€ì •ë˜ì–´ 있지 않습니다. 보다 ìžì„¸í•œ ë‚´ìš©ì€ https://github.com/abrt/abrt/wiki/FAQ#creating-private-bugzilla-ticketsì—ì„œ 참조하십시오올바른 디버그 ì •ë³´ê°€ 누ë½ë˜ì–´ 있거나 코어 ë¤í”„ê°€ ì†ìƒë˜ì–´ 있습니다.DBus 보안 서비스ì—ì„œ 프롬프트 결과를 기다리는 ë™ì•ˆ 제한 ì‹œê°„ì„ ì´ˆê³¼í–ˆìŠµë‹ˆë‹¤.CC 목ë¡ì— bugzilla ì‚¬ìš©ìž [ì´ ID를 갖는 버그] ì¶”ê°€ë¡œê·¸ì— í”„ë¡œê·¸ëž¨ ì´ë¦„ 추가 CC 목ë¡ì— %s 추가버그 %iì— ì™¸ë¶€ URLì„ ì¶”ê°€ë²„ê·¸ %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ì´(ê°€) 중복 (DUPLICATE)으로 종료 (CLOSED)ë˜ì—ˆì§€ë§Œ DUP_IDê°€ 없습니다. 버그 %iì´(ê°€) 종료 (CLOSED)ë˜ì—ˆì§€ë§Œ í•´ê²° 방법 (RESOLUTION)ì´ ì—†ìŠµë‹ˆë‹¤ ì´ë¯¸ 버그가 ë³´ê³ ë˜ì—ˆìŒ: %i Bug.search(quicksearch)ì˜ ë°˜í™˜ê°’ì—는 멤버 'bugs'ê°€ í¬í•¨ë˜ì–´ 있지 않습니다Bugzilla Bugzilla URL Bugzilla 계정 암호 Bugzilla 계정 ì‚¬ìš©ìž ì´ë¦„ Bugzilla는 버그 %dì˜ ë¶€ëª¨ 버그를 ì°¾ì„ ìˆ˜ 없습니다 Bugzilla 제품Bugzilla 제품 버전설정(_O){1}ì—ì„œ 만들어진 {0}ì—ì„œ 파ì¼ì„ ìºì‹œ 중 메서드 '%s'ì„/를 DBus를 통해 경로 '%s' ì¸í„°íŽ˜ì´ìŠ¤ '%'ì— í˜¸ì¶œí•  수 없습니다: %sDBus를 통해 ì´ë¦„ '%s' 경로 '%s' ì¸í„°íŽ˜ì´ìŠ¤ '%'ì— ì—°ê²°í•  수 없습니다: %sURL ì—†ì´ ê³„ì† ì§„í–‰í•  수 없습니다%sì˜ ì´ë©”ì¼ ì£¼ì†Œ ì—†ì´ ê³„ì† ì§„í–‰í•  수 없습니다로그ì¸ì—†ì´ ê³„ì† ì§„í–‰í•  수 ì—†ìŠµë‹ˆë‹¤ì•”í˜¸ì—†ì´ ê³„ì† ì§„í–‰í•  수 없습니다'%s'ì„(를) 복사할 수 없습니다: %sì´ë²¤íŠ¸ '%s'ì˜ ë³´ì•ˆ í•­ëª©ì„ ë§Œë“¤ 수 없습니다: %sìž„ì‹œ 디렉토리를 ìƒì„±í•  수 없습니다임시 파ì¼ì„ ìƒì„±í•  수 없습니다'%s'ì„/를 삭제할 수 없습니다: %s삭제할 수 없습니다: '%s'문제 ë°ì´í„°ì—ì„œ Bugzilla ì œí’ˆì„ ì§€ì •í•  수 없습니다.문제 ë°ì´í„°ì—ì„œ RH ì§€ì› ì œí’ˆì„ ì§€ì •í•  수 없습니다.비ë™ê¸° 다운로드를 비활성화할 수 없습니다. ì¶œë ¥ì— ì•„í‹°íŒ©íŠ¸ê°€ í¬í•¨ë˜ì–´ ìžˆì„ ìˆ˜ 있습니다!리í¬ì§€í„°ë¦¬ '{0!s}'ì„/를 비활성화할 수 없습니다: {1!s}'{0}'ì—ì„œ 파ì¼ì„ 추출할 수 ì—†ìŒ íŒ¨í‚¤ì§€ '{0}'ì„(를) 추출할 수 없습니다 {0} 디버그 ì •ë³´ 파ì¼ì— 해당하는 패키지를 ì°¾ì„ ìˆ˜ 없습니다 ìŠ¤íƒ íŠ¸ë ˆì´ìŠ¤ ì„¤ëª…ì„ ìƒì„±í•  수 ì—†ìŒ (í¬ëž˜ì‹œ 스레드가 ì—†ìŒ?)ì´ ë¬¸ì œê°€ Bugzillaì— ë³´ê³ ë˜ì–´ 있지 않기 ë•Œë¬¸ì— Bugzilla ID를 가져올 수 없습니다.쓰기를 위한 '%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 í‹°ì¼“ì„ ì •ë§ë¡œ ìƒì„±í•˜ì‹œê² ìŠµë‹ˆê¹Œ? ì´ì „ì— ë¡œë“œëœ ì„¤ì •ì„ ì‚¬ìš©í•˜ì§€ ì•Šê³  대기를 중지하고 ê³„ì† ë³´ê³ í•˜ì‹œê² ìŠµë‹ˆê¹Œ?관련 ê°€ëŠ¥ì„±ì´ ìžˆëŠ” 문서: 다시 묻지 않습니다 암호를 저장하지 마십시오 사용ìžì— ì˜í•´ 다운로드가 취소ë˜ìžˆìŠµë‹ˆë‹¤ {2} 다운로드 중 ({1}중 {0}): {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 코드: %dyum 초기화 오류 (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 writer 닫기 실패새 버그 ìƒì„±ì— 실패했습니다.TAR archive 종료 실패TAR writer 열기 ì‹¤íŒ¨íŒŒì¼ '%s' ì €ìž¥ì— ì‹¤íŒ¨í–ˆìŠµë‹ˆë‹¤ì„œë²„ '%s'ì— uReport를 업로드하지 못했습니다curlì´ ìžˆëŠ” 서버 '%s'ì— uReport를 업로드하지 ëª»í–ˆìŠµë‹ˆë‹¤ê¸ˆì§€ëœ ë¬¸ìžì´ 문제가 ì´ë¯¸ ë³´ê³ ë˜ì–´ 있는 경우ì—ë„ ê°•ì œë¡œ 보고합니다 새 기술 ë¬¸ì˜ ìš© 파ì¼ì„ í¬ë§· 중ì´ë©”ì¼ ìš© íŒŒì¼ í¬ë§· 중중복 확ì¸ì„ 위해 파ì¼ì„ í¬ë§·í•˜ê³  있습니다초기 ì½”ë©˜íŠ¸ì— ëŒ€í•œ 파ì¼ì„ í¬ë§·í•˜ê³  있습니다버그 기ë¡ì— ë™ì¼í•œ 주ì„ì´ ë°œê²¬ëœ ê²½ìš° 새 주ì„ì„ ì¶”ê°€í•˜ì§€ 않습니다 그룹HTTP 프ë¡ì‹œHTTPS 프ë¡ì‹œì´ 문제가 어떻게 ë°œìƒí–ˆëŠ”지 단계별로 설명합니다. 재현 ë°©ë²•ì„ ì„¤ëª…í•©ë‹ˆë‹¤. 문제 ì§„ë‹¨ì— ë„ì›€ì´ ë  ì¶”ê°€ 주ì„ì´ ìžˆìŠµë‹ˆê¹Œ? 있다면 ì˜ì–´ë¡œ 설명해 주십시오. 문제를 어떻게 재현할 수 있습니까 (í•œ ì¤„ì— í•œ 단계)?문제를 어떻게 재현 가능합니까?어떻게 문제를 보고하시겠습니까? 문제를 재현할 수 ìžˆìŠµë‹ˆë‹¤ì´ ë¬¸ì œì˜ ì›ì¸ì„ ì•Œ 수 없습니다. 처ìŒìœ¼ë¡œ ì´ëŸ¬í•œ 문제가 ë°œìƒí–ˆìŠµë‹ˆë‹¤ë°ì´í„°ë¥¼ 검색했습니다. ë°ì´í„° ì „ì†¡ì— ë™ì˜í•©ë‹ˆë‹¤.ì›ê²© ì„œë²„ì— ë³´ê³ í•˜ëŠ” 경우, 모든 ê°œì¸ ë°ì´í„° (ì‚¬ìš©ìž ì´ë¦„ê³¼ 암호 등)ê°€ ì‚­ì œë˜ì—ˆëŠ”지 확ì¸í•©ë‹ˆë‹¤. 백트레ì´ìŠ¤, 명령행, 환경 변수 ë“±ì€ ê²€ì‚¬í•´ì•¼ 하는 ì¼ë°˜ì  항목입니다. 어떻게 설명해야 í•  지를 모르는 경우 다ìŒì„ í•  수 있습니다다른 ìž¥ì†Œì— ë¬¸ì œë¥¼ ë³´ê³ í•˜ê³ ìž í•  경우 추가 정보를 수집하거나 보다 ìƒì„¸í•˜ê²Œ 문제를 설명하여 ë³´ê³  절차를 반복 실행한 후 '앞으로'를 누릅니다. ì„¤ì •ì„ ì—…ë°ì´íŠ¸í•˜ê³  다시 보고하려면 애플리케ì´ì…˜ ë©”ë‰´ì— ìžˆëŠ” 환경 설정 í•­ëª©ì„ ì—´ê³  설정 변경 ì‚¬í•­ì„ ì ìš©í•œ 후 반복 실행 ë²„íŠ¼ì„ í´ë¦­í•©ë‹ˆë‹¤.ë³´ê³  ê²°ê³¼ '%s'ì˜ ìž˜ëª»ëœ ISO 날짜가 무시ë˜ì—ˆìŠµë‹ˆë‹¤ì²´ê³„ ë° í˜¸ìŠ¤íŠ¸ ì´ë¦„ì—†ì´ URL ë¬´ì‹œë‚´ìž¥ëœ ìŠ¤í¬ë¦° ìºìŠ¤íŒ… ê¸°ëŠ¥ì„ ì‚¬ìš©í•˜ë ¤ë©´ fros-gnome 패키지를 설치해야 합니다. ì´ íŒ¨í‚¤ì§€ë¥¼ 설치하려면 ë‹¤ìŒ ëª…ë ¹ì„ ì‹¤í–‰í•˜ì‹­ì‹œì˜¤. su -c "yum install fros-gnome"í¬í•¨ yum 초기화 중 ìž˜ëª»ëœ ë¶€ìš¸ ê°’ '%s' ìž˜ëª»ëœ ìž…ë ¥. 종료하고 있습니다. ìž˜ëª»ëœ ë²ˆí˜¸ '%s' 암호 ë˜ëŠ” 로그ì¸ì´ 잘못ë˜ì—ˆìŠµë‹ˆë‹¤. '%s'ì˜ ì•”í˜¸ë¥¼ 입력하십시오:암호 ë˜ëŠ” 로그ì¸ì´ 잘못ë˜ì—ˆìŠµë‹ˆë‹¤. BZ 로그ì¸ì„ 입력하십시오:암호 ë˜ëŠ” 로그ì¸ì´ 잘못ë˜ì—ˆìŠµë‹ˆë‹¤. Red Hat 로그ì¸ì„ 입력하십시오:ìž˜ëª»ëœ 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'ì´ ì„¤ì •ë˜ì–´ 있지 않습니다새 버그 id: %i 사용 가능한 ì„¤ëª…ì´ ì—†ìŒì´ë²¤íŠ¸ '%s'ì— ëŒ€í•œ 처리가 ì •ì˜ë˜ì§€ ì•ŠìŒ ì‚¬ìš© 가능한 보고서가 없습니다 ì´ ë¬¸ì œì— ëŒ€í•œ ë³´ê³  대ìƒì´ 지정ë˜ì–´ 있지 않습니다. /etc/libreport/*ì—ì„œ ì„¤ì •ì„ í™•ì¸í•˜ì‹­ì‹œì˜¤ë¹„대화ì‹: ì§ˆë¬¸ì„ í•˜ì§€ ì•Šê³  '예'ë¡œ 간주 빈 uReport를 업로드하지 않습니다알림 만 실행 (보고서를 전송으로 표시하지 ì•ŠìŒ)í™•ì¸ ë‹¤ìŒ í™”ë©´ì—서는 어떻게 문제가 ë°œìƒí–ˆëŠ”지를 설명하ë¼ëŠ” ìš”ì²­ì´ ë‚˜íƒ€ë‚©ë‹ˆë‹¤. 필요한 경우 문제 ë¶„ì„ ë°©ë²•ì„ ì„ íƒí•˜ê³  수집한 ë°ì´í„°ë¥¼ 확ì¸í•œ 후 문제를 ë³´ê³ í•  위치를 ì„ íƒí•©ë‹ˆë‹¤. '앞으로'를 í´ë¦­í•˜ì—¬ ê³„ì† ì§„í–‰í•©ë‹ˆë‹¤. Oops 서버 url 출력 ê²°ê³¼ íŒŒì¼ ë‹¤ìš´ë¡œë“œí•  패키지: {0}암호 설정ì—ì„œ 암호가 지정ë˜ì–´ 있지 않습니다. '%s'ì— í•´ë‹¹í•˜ëŠ” 암호를 입력하십시오:ë¬¸ì œì˜ ì¢…í•©ì ì¸ ì„¤ëª…ì„ ê¸°ìž¬í•˜ì‹­ì‹œì˜¤. ì´ëŠ” 매우 긴 ìžë¦¬ 표시ìžìž…니다.문제 ë°ì´í„°ë¥¼ 내보내기할 URL (scp, ftp 등)ì„ ìž…ë ¥í•˜ì‹­ì‹œì˜¤:'%s//%s@%s'ì˜ ì•”í˜¸ë¥¼ 입력하십시오:업로드를 위해 암호를 입력하십시오:'%s//%s'ì˜ ì‚¬ìš©ìž ì´ë¦„ì„ ìž…ë ¥í•˜ì‹­ì‹œì˜¤:ë¬¸ì œì— ëŒ€í•œ 간단한 설명과 문제를 ìž¬í˜„í•˜ëŠ”ë° ì‚¬ìš©í•œ 절차를 기입해 주십시오.문제를 ìž¬í˜„í•˜ëŠ”ë° ì‚¬ìš©í•œ 절차를 기입해 주십시오.ì´ ë¬¸ì œë¥¼ ABRT 개발ìžì—게 ë³´ê³ í•´ 주십시오.보고하기 ì „ ë°ì´í„°ë¥¼ 확ì¸í•˜ì‹­ì‹œì˜¤. ì„ íƒí•œ ë³´ê³  대ìƒì— ë”°ë¼ ê³µê°œë  ìˆ˜ 있습니다."debuginfo-install %s" ëª…ë ¹ì„ ì‚¬ìš©í•˜ì—¬ 수ë™ìœ¼ë¡œ 디버그 정보를 설치한 후 다시 ì‹œë„í•´ 보십시오.%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 서버 문제를 처리Fedora ì¸í”„ë¼ë¥¼ 사용하여 ì»¤ë„ í¬ëž˜ì‹œë¥¼ 처리Red Hat ì¸í”„ë¼ë¥¼ 사용하여 ì»¤ë„ í¬ëž˜ì‹œë¥¼ 처리Fedora ì¸í”„ë¼ë¥¼ 사용하여 kerneloops를 처리Red Hat ì¸í”„ë¼ë¥¼ 사용하여 kerneloops를 처리Fedora ì¸í”„ë¼ë¥¼ 사용하여 문제를 처리Red Hat ì¸í”„ë¼ë¥¼ 사용하여 문제를 처리Fedora ì¸í”„ë¼ë¥¼ 사용하여 python 예외를 처리Red Hat ì¸í”„ë¼ë¥¼ 사용하여 python 예외를 처리Fedora ì¸í”„ë¼ë¥¼ 사용하여 보고서를 처리Red Hat ì¸í”„ë¼ë¥¼ 사용하여 ë³´ê³  처리처리중작업 처리를 ì•„ì§ ì‹œìž‘í•˜ì§€ 않았습니다.처리 완료작업 ì²˜ë¦¬ì— ì‹¤íŒ¨í–ˆìŠµë‹ˆë‹¤.ìž‘ì—… 처리가 완료ë˜ì—ˆìŠµë‹ˆë‹¤. ë‹¤ìŒ ë‹¨ê³„ë¡œ ì´ë™í•˜ì‹­ì‹œì˜¤.ìž‘ì—… 처리가 완료ë˜ì—ˆìŠµë‹ˆë‹¤.ìž‘ì—… 처리가 중단ë˜ì—ˆìŠµë‹ˆë‹¤: 쓰기 가능한 ë””ë ‰í† ë¦¬ì—†ì´ ê³„ì† ì§„í–‰í•  수 없습니다.문제 ì²˜ë¦¬ì— ì‹¤íŒ¨í–ˆìŠµë‹ˆë‹¤. 다양한 ì›ì¸ì´ ìžˆì„ ìˆ˜ 있지만 세 ê°€ì§€ì˜ ê°€ìž¥ ì¼ë°˜ì ì¸ ì›ì¸ì€ 다ìŒê³¼ 같습니다: â–« ë„¤íŠ¸ì›Œí¬ ì—°ê²° 문제 â–« ì†ìƒëœ ë°ì´í„°ì— ì˜í•œ 문제 â–« ìž˜ëª»ëœ ì„¤ì •ìž‘ì—… 처리가 취소ë˜ì—ˆìŠµë‹ˆë‹¤ë¬¸ì œë¥¼ ë³´ê³ í•  수 없기 ë•Œë¬¸ì— ìž‘ì—… 처리가 중단ë˜ì—ˆìŠµë‹ˆë‹¤.처리 중...추가 ì •ë³´ 제공 종료 RH í¬í„¸ URL 받는 사람 받는 ì‚¬ëžŒì˜ ì´ë©”ì¼ Red Hat ê³ ê° ì§€ì› Red Hat ê³ ê° ì•”í˜¸ Red Hat ê³ ê° ì‚¬ìš©ìž ì´ë¦„ ë³´ê³  후 DIR ì‚­ì œ ë³´ê³  후 PROBLEM_DIR 제거 {0} 제거 중 반복 실행보고서 ì—…ë¡œë”Fedora 유지 관리ìžì—게 버그를 ë³´ê³ Red Hat Bugzillaì— ë²„ê·¸ ë³´ê³  Red Hat ê³ ê° í¬í„¸ì— 버그 ë³´ê³ ë³´ê³  ê²°ê³¼ ë ˆì´ë¸”ì„ ë¹„ì›Œë‘˜ 수 없습니다.ë³´ê³  ê²°ê³¼ ë ˆì´ë¸”ì— ':'ì„ í¬í•¨í•´ì„œëŠ” 안ë©ë‹ˆë‹¤.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 공개 키 파ì¼í…스트 파ì¼ë¡œ 저장 검색 비밀 서비스를 사용할 수 없습니다. ì„¤ì •ì´ ì €ìž¥ë˜ì§€ 않습니다!실행할 워í¬í”Œë¡œ ì„ íƒ:실행할 ì´ë²¤íŠ¸ ì„ íƒ:ì´ ë¬¸ì œë¥¼ ë³´ê³ í•  ë°©ë²•ì„ ì„ íƒí•˜ì‹­ì‹œì˜¤ë°”ì´ë„ˆë¦¬ ë°ì´í„° 전송 코어ë¤í”„와 ê°™ì€ ë°”ì´ë„ˆë¦¬ íŒŒì¼ ì „ì†¡ ì´ë©”ì¼ì„ 통해 문제 ë°ì´í„° ì „ì†¡ì»¤ë„ oops 트래커로 전송합니다 ì´ë©”ì¼ë¡œ 전송 보내는 사람 보내는 ì‚¬ëžŒì˜ ì´ë©”ì¼ %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> ì— ì „ì†¡í•©ë‹ˆë‹¤.ìµëª…으로 í¬ëž˜ì‹œ ë³´ê³ ì„œ 제출ìµëª…으로 í¬ëž˜ì‹œ ë³´ê³ ì„œ 제출 - 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'ì—ì„œ bug ID를 ì°¾ì„ ìˆ˜ 없습니다bugzilla URL '%s'ì—ì„œ bug 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 남ìŒ). 계ì†í•˜ì‹œê² ìŠµë‹ˆê¹Œ? 버그 ìƒì„± ì‹œ ë°”ì´ë„ˆë¦¬ 파ì¼ë„ 첨부합니다 login:password@url 형ì‹ìœ¼ë¡œëœ ë³´ê³ ì„œì˜ íƒ€ë³¼ (tarball)ì„ ì—…ë¡œë“œí•˜ê³ ìž í•˜ëŠ” 위치 워í¬í”Œë¡œíŒŒì¼ì„ íŒŒì¼ ìžì²´ì— 복사하려고 합니다 <a href="https://bugzilla.redhat.com/createaccount.cgi">여기</a>ì—ì„œ bugzilla.redhat.com ê³„ì •ì„ ìƒì„±í•  수 있습니다 범위를 ë²—ì–´ë‚œ 번호를 ì„ íƒí•˜ì…¨ìŠµë‹ˆë‹¤ 특정 ê·¸ë£¹ì˜ ë°ì´í„°ì—만 액세스할 수 있ë„ë¡ ìš”ì²­ë˜ì—ˆìœ¼ë©° ì´ ë²„ê·¸ëŠ” ì¤‘ë³µëœ ë²„ê·¸ìž…ë‹ˆë‹¤: %s/%u ì¤‘ë³µëœ ë²„ê·¸ì˜ ê²½ìš° 기존 버그 리í¬íŠ¸ì— 새로운 코멘트가 추가ë˜ì§€ë§Œ ì´ëŸ¬í•œ ì½”ë©˜íŠ¸ì— íŠ¹ì • 그룹만 액세스할 수 있ë„ë¡ ì œí•œí•  수 없습니다. 새 버그 리í¬íŠ¸ë¥¼ 작성하고 ì´ë¥¼ ê¸°ì¡´ì˜ ê²ƒê³¼ ì¤‘ë³µëœ ê²ƒìœ¼ë¡œ 하여 종료하시겠습니까? 그렇지 ì•Šì„ ê²½ìš° 버그 ë³´ê³  절차는 종료ë©ë‹ˆë‹¤.처리하기 ì „ ë°©ë²•ëž€ì„ ìž‘ì„±í•˜ì…”ì•¼ 합니다... 첨부할 uReportì˜ bthash를 지정해야 합니다.버그 ID ë˜ëŠ” ì´ë©”ì¼ ì£¼ì†Œ 중 하나 ë˜ëŠ” 모ë‘를 지정해야 합니다다ìŒê³¼ ê°™ì€ ì´ìœ ë¡œ ìž…ë ¥ì´ ìœ íš¨í•˜ì§€ 않습니다: %s(으)ë¡œ ì¸í•´ 문제가 ë°œìƒí•œ 것 같습니다 %s ë‹¤ìŒ ì¤‘ í•œ 가지 ì›ì¸ìœ¼ë¡œ ì¸í•´ 문제가 ë°œìƒí•œ 것 같습니다: 취소(_C) 종료(_C) 다ìŒ(_F)아니요(_ N)_OK열기(_O)저장 (_S)중지(_S)예(_Y)스í¬ë¦°ìºìŠ¤íŠ¸ 추가ureporte 첨부 ATTACHMENT_TYPE으로 DATA 첨부 (-l|-L과만 사용)RHBZ 버그 첨부 (-a|-A 필수, -B와 충ëŒ)마지막 ë³´ê³  ê²°ê³¼ì˜ FIELD [URL]ì— ë‚ ì§œ 첨부 (-a|-A , -r ë° -T 필수, -lê³¼ 충ëŒ)reported_toì—ì„œ 최신 RHBZ 버그 첨부 (-a|-A 필수, -b와 충ëŒ)reported_toì—ì„œ bthashì— ì²¨ë¶€ ( -a와 충ëŒ)ê°’ 첨부 (r -a|-A ë° -T 필수, -Lê³¼ 충ëŒ)첨부할 uReportì˜ bthash (-A와 충ëŒ)'%s'ì˜ ë³´ì•ˆ ê°’ì„ ì–»ì„ ìˆ˜ 없습니다: %së³´ê³ í•  수 없습니다 ë‹´ë‹¹ìž ì´ë©”ì¼ ì£¼ì†Œ (-a|-A 필수, -E와 충ëŒ)환경 ë˜ëŠ” 설정 파ì¼ì— 있는 ë‹´ë‹¹ìž ì´ë©”ì¼ ì£¼ì†Œ (-a|-A 필수, -e와 충ëŒ)ë°ì´í„°f파ì¼%dë¡œ gzipì´ ì¢…ë£Œë˜ì—ˆìŠµë‹ˆë‹¤%d 신호로 gzipì´ ì¢…ë£Œë˜ì—ˆìŠµë‹ˆë‹¤gzip 프로세스 실패다른 í”„ë¡œì„¸ìŠ¤ì— ì˜í•´ 잠금ë˜ì—ˆìŠµë‹ˆë‹¤ë¬¸ì œ 디렉토리가 ì•„ë‹™ë‹ˆë‹¤ì ‘ê·¼ì´ ê±°ë¶€ë¨uReportuReport 서버 URLUID ê°’ì´ ì˜¬ë°”ë¥´ì§€ 않습니다: '%s'reported_toì—ì„œ FIELD 검색 ì‹œ REPORT_RESULT_TYPEì„ ì‚¬ìš© (-L과만 사용)y