Asking Questions/zh-tw: Difference between revisions
m (Created page with '* '''還有,試著確認你碰到的是 KDE 的問題'''而不是你係統裡其他元件的(比如,X 的問題或 alsa的問題)。如果可能的話,試一下其他...') |
m (Created page with '* '''確保你已經閱讀過手冊(The Fine Manual)和疑難排解頁面'''。儘管不是每個問題都在那有解答。如果你認為你的...') |
||
Line 21: | Line 21: | ||
* '''還有,試著確認你碰到的是 KDE 的問題'''而不是你係統裡其他元件的(比如,X 的問題或 alsa的問題)。如果可能的話,試一下其他的替代品,用非 KDE 程式看看是否問題依舊發生。當然,如果你不確定,那就問吧。 | * '''還有,試著確認你碰到的是 KDE 的問題'''而不是你係統裡其他元件的(比如,X 的問題或 alsa的問題)。如果可能的話,試一下其他的替代品,用非 KDE 程式看看是否問題依舊發生。當然,如果你不確定,那就問吧。 | ||
* ''' | * '''確保你已經閱讀過手冊(The Fine Manual)和[[Troubleshooting_(zh_TW)|疑難排解]]頁面'''。儘管不是每個問題都在那有解答。如果你認為你的問題是很常見的,別人也想要答案的話,試著在[http://forum.kde.org/ 論壇(英文)]或[http://moto.debian.org.tw/viewforum.php?f=39 KDE@Taiwan 討論區]提問。如果討論帶出了有趣的信息,你也可以發送建議給 [mailto:[email protected] [email protected]] 要求把他加進 wiki。 | ||
* '''Be prepared to wait!''' Often, someone will notice your question a little while after you ask it, so wait around for a while after you ask. There's nothing more annoying than typing out a long answer for someone, only to realise that they left 3 minutes after asking their question! | * '''Be prepared to wait!''' Often, someone will notice your question a little while after you ask it, so wait around for a while after you ask. There's nothing more annoying than typing out a long answer for someone, only to realise that they left 3 minutes after asking their question! |
Revision as of 04:21, 10 June 2010
Template:I18n/Language Navigation Bar
一般的指導方針
這裡有些問問題的提示,尤其是在Freenode的#kde(英文)頻道,在某種程度上說更有可能得到答案:
- 不要猶豫,直接問:#kde 是用戶支持頻道,我們期待你的問題- 問吧:-) 。
- 準備好任何有關你係統的細節:哪個發行版(發行版的具體版本?),你用的 KDE SC 版本,你怎麼安裝他的等等。你可能不需要立刻給出所有的信息,但你應該準備好以免有人問起。
- 問前試下自己解決故障:Google是你的良師益友(在Google中輸入錯誤信息通常能知道些有用的東西)。你應該看下 KDE 疑難排解 - 那兒的建議不管怎樣都會在 #kde 上說一遍的,所以可以先試下:-)。
- 還有,試著確認你碰到的是 KDE 的問題而不是你係統裡其他元件的(比如,X 的問題或 alsa的問題)。如果可能的話,試一下其他的替代品,用非 KDE 程式看看是否問題依舊發生。當然,如果你不確定,那就問吧。
- 確保你已經閱讀過手冊(The Fine Manual)和疑難排解頁面。儘管不是每個問題都在那有解答。如果你認為你的問題是很常見的,別人也想要答案的話,試著在論壇(英文)或KDE@Taiwan 討論區提問。如果討論帶出了有趣的信息,你也可以發送建議給 [email protected] 要求把他加進 wiki。
- Be prepared to wait! Often, someone will notice your question a little while after you ask it, so wait around for a while after you ask. There's nothing more annoying than typing out a long answer for someone, only to realise that they left 3 minutes after asking their question!
- If you don't get an answer on #kde, you can also try the channel for your distribution (eg, #suse, #kde-freebsd, etc), or an appropriate mailing list: see lists.kde.org or forum.
- Above all, be patient and polite. Remember that the people who help are all volunteers, and could be spending their time doing other things than helping.
If your problem is with sound in KDE, you might want to first read Sound_Problems.
If your question relates to development, please see this page
Operating-System-Specific Questions
For questions relating to the desktop use of KDE with a particular OS, you can try the above methods, but unless the question directly involves KDE or KDE/GNU/Linux you are unlikely to find the answer. If your question does not directly involve KDE, please do not post the question on the "normal" KDE mailing lists. Examples of questions that do not directly involve KDE: my sound card does not work. In that case, please direct your questions at sites devoted to helping users of that system. For example, for GNU/Linux questions you may try looking at www.linuxnewbie.org or www.linuxnewbie.com, or the kde-linux mailing list mentioned above. If you are not using GNU/Linux, you might want to try the kde-nonlinux (subscribe) mailing list. Also particularly useful are searches on your favorite search engine, such as Google, and searches on the Usenet archives.
In addition, many OS distributors have their own mailing lists which can address distribution-specific issues. You can find out more about these mailing lists at your distribution's website.
If you are searching for rpms you may consider checking the ftp servers for your distribution, including the "contrib" sections, as well as more general servers such as rpmfind.net.
Reporting KDE Bugs
Please report all KDE bugs and feature requests at bugs.kde.org. The site has a nice bug-reporting "wizard" and will permit far easier tracking of bugs than an email to a list.
How to open a console
Typically when reporting a problem in IRC or on a mailing list, your helpers will ask you to open a console. A console is a text-based window that you can use to give commands for your computer to execute. You can open a console by typing ALT_F2. An input box opens. Type
konsole
And a console will open. If this does not work, you may not have it installed. In this case, type ALT_F2 and call
xterm
Back to Getting_Help |