Asking Questions/nl: Difference between revisions

    From KDE UserBase Wiki
    (Created page with ''''Hoe een console te openen'''')
    (Updating to match new version of source page)
    (57 intermediate revisions by 4 users not shown)
    Line 1: Line 1:
    {{Template:I18n/Language Navigation Bar|Asking_Questions}}
    <languages />  
    <languages />  
    __TOC__
    ==IRC gebruiken om geholpen te worden==
    Nu volgens een aantal tips voor het stellen van vragen om de kans op antwoorden te vergroten, in het bijzonder in #kde op Freenode:


    * '''Vraag niet of je een vraag mag stellen, stel gewoon je vraag''': het irc.freenode.net kanaal #kde is een kanaal voor ondersteuning van gebruikers, dus we verwachten uw vragen - ga uw gang [[Image:Face-smile.png]].


    __TOC__
    * '''Be ready with as much relevant details about your system as you can find''': Questions you are likely to be asked are:
    ** What distribution do you use (and what version?) e.g. Kubuntu 12.1
    ** what version of KDE you are running &mdash; if you don't know, open '''Konsole''' and type <code>kde4-config --kde-version</code> and look at the version numbers given there
    ** how you installed it &mdash; mostly likely from your distribution repositories.
     
    You probably won't need to give all of this information straight away, but if you know how to find it quickly it often helps
     
    * '''Probeer eerst zelf het probleem op te lossen alvorens een oplossing te vragen''': Google is uw vriend (zoeken naar foutmeldingen met Google levert vaak nuttige informatie). Kijk ook bij [[Special:myLanguage/Troubleshooting|Oplossen van KDE problemen]] - het advies wat daar staat is waarschijnlijk wat ook in #kde wordt geadviseerd, dus kijk hier eerst [[Image:Face-smile.png]].
     
    * '''Probeer ook zeker te weten of het probleem door KDE veroorzaakt wordt''' en niet door een ander onderdeel van uw systeem (zoals bijvoorbeeld een probleem met [http://nl.wikipedia.org/wiki/X_Window_System X] of [http://nl.wikipedia.org/wiki/Advanced_Linux_Sound_Architecture ALSA]). Probeer, indien mogelijk, een alternatieve niet-KDE applicatie om te zien of het probleem zich daar ook voordoet. Natuurlijk is het geen probleem om vragen te stellen als u er niet uitkomt.
     
    * '''Use [http://forum.kde.org/ the Forum]'''. Try asking a question on [http://forum.kde.org/ the forum]. If the discussion brings up interesting information you might add it to UserBase, so that it can help others.
     
    * '''Be prepared to wait!''' Often on IRC, 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!  In some cases there could be hours between your question being asked and someone who knows the answer coming on-line (remember that KDE users are all over the world) so sometimes you just have to ask again at a different time of day.


    == Algemene richtlijnen ==
    * '''Als u geen antwoord krijgt in #kde, dan kunt u ook het kanaal van uw distributie proberen''' (bijv. #suse, #kde-freebsd, etc), of een mailing list: zie [http://lists.kde.org lists.kde.org] of het forum.


    Nu volgens een aantal tips voor het stellen van vragen om de kans op antwoorden te vergroten, in het bijzonder in #kde op Freenode:
    * '''Het belangrijkste is dat u geduldig en beleefd bent.''' Onthoud dat de mensen die helpen allemaal vrijwilligers zijn, en het druk kunnen hebben met andere dingen dan helpen.


    * '''Don&#039;t ask to ask, just ask''': #kde is a user support channel, so we expect your questions - go right ahead :-).
    Als u een probleem met geluid hebt in KDE, lees dan eerst [[Special:MyLanguage/Sound_Problems|Problemen met geluid]].


    * '''Be ready with any relevant details about your system''': What distribution (what version?), what version of KDE you&#039;re running, how you installed it and so on. You probably won&#039;t need to give all of this information straight away, but you should have it available in case someone asks.
    Als uw vraag over ontwikkeling gaat, kijk dan op [http://techbase.kde.org/Contribute de pagina over hoe bijdragen op KDE TechBase]


    * '''Try to do some troubleshooting yourself before asking''': Google is your friend (entering error messages into Google often finds something useful). You should take a look at [[Troubleshooting|Troubleshooting KDE Problems]] - the advice there is probably what you&#039;ll be told in #kde anyway, so try it first :-).
    Because KDE is so actively developed, changes arrive very frequently, so don't be surprised if you can't find any written information.  Ask in IRC, the Forum or a mailing list, and when you have an answer, register an account on UserBase and add the information to the relevant page. At the same time as learning about your system you will be helping others do the same {{smiley}}


    * '''Also, try to make sure that the problem you&#039;re having is a problem with KDE''' and not some other component of your system (for example, a problem with X or with alsa). If possible, try an alternative, non-KDE application to see whether the problem also occurs there.  Of course, if you&#039;re not sure, please ask.
    == The Forums ==


    * '''Make sure that you have Read The Fine Manual and the [[Troubleshooting]] pages'''. Although not every question is answered there, many are. If you think that your question is a common one that others would like the answer to, try asking it on [http://forum.kde.org/ the forum]. If the discussion brings up interesting information you might also want to suggest it to [mailto:community-wg@kde.org community-wg@kde.org] with a view to getting it included on the wiki.
    Another great place to get help is the [http://forum.kde.org/ KDE Community Forums]. It is always a good idea to search the forums first. Maybe your question has already been answered. If not, find an appropriate forum and start a thread. Don't expect an immediate answer, but remember to come back regularly to participate in the discussion as it gets going. Remember that the forums are run by users like yourself.  


    * '''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&#039;s nothing more annoying than typing out a long answer for someone, only to realise that they left 3 minutes after asking their question!
    The KDE Community forums offer a "guided post" feature that can help you post your question in the appropriate forum, increasing the chance of having it seen by people knowledgeable on the matter. It is accessible as a large "New Post" button on the forums' homepage, so if you have any doubts, that is the place to start.


    * '''If you don&#039;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 [http://lists.kde.org lists.kde.org] or forum.
    The forums have an extensive search feature: prior to posting try finding if your question has already been answered, or there are hints that might help you solve your issue. If there is no satisfactory solution for your problem, make a new post. To search, enter keywords in the upper right box of any forum page. By default this will search the whole forums. For extended searches, click on the "Search" link under the "KDE Community Forums" banner.  


    * '''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 question has been properly answered, consider marking a topic as "solved". It is a very little step, but quite helpful for other users and staff, because it tells them that there are no more issues. To mark a topic as solved, choose the topic with the best answer in the thread, and click the green tick mark under it. If you go back to the topic list you will notice a green tick mark next to the topic's title as well.  


    If your problem is with sound in KDE, you might want to first read [[Sound_Problems]].


    If your question relates to development, please see [http://techbase.kde.org/Contribute this page]
    Most distributions have forums of their own; these can also be valuable. The web pages of your distribution should provide links to its forums.


    ==Operating-System-Specific Questions==
    ==Specifieke vragen over besturingssystemen==


    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 [http://www.linuxnewbie.org www.linuxnewbie.org] or [http://www.linuxnewbie.com www.linuxnewbie.com], or the [http://mail.kde.org/mailman/listinfo/kde-linux kde-linux] mailing list mentioned above. If you are not using GNU/Linux, you might want to try the [mailto:http://mail.kde.org/mailman/listinfo/kde-nonlinux kde-nonlinux] [mailto:[email protected]?subject=subscribe (subscribe)] mailing list. Also particularly useful are searches on your favorite search engine, such as [http://www.google.com/ Google], and searches on the [http://groups.google.com/ Usenet archives].
    For questions relating to the desktop use of KDE with a particular operating system (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''. An example of questions that do not directly involve KDE is "''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 [http://www.linuxnewbie.org www.linuxnewbie.org] or [http://www.linuxnewbie.com www.linuxnewbie.com], or the [http://mail.kde.org/mailman/listinfo/kde-linux kde-linux] mailing list mentioned above.


    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.
    Als u geen GNU/Linux gebruikt, kunt u de [http://mail.kde.org/mailman/listinfo/kde-nonlinux kde-nonlinux] [mailto:kde-nonlinux-subscribe@kde.org?subject=subscribe (aanmelden)] mailing list proberen. Ook bijzonder nuttig zijn zoekopdrachten op uw  favoriete zoekmachine, zoals [http://www.google.com/ Google], en zoekt op de [http://groups.google.com/ Usenet-archieven].


    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.  
    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 or find them through your browser search engine.


    If you are searching for packages you may consider checking the ftp servers for your distribution, including the "contrib" sections, as well as indexing servers such as rpmfind.net.  Wherever possible, install the package that your distro offers directly through its package manager.
    <span id="Reporting KDE Bugs"></span>
    == Fouten in KDE rapporteren ==
    == Fouten in KDE rapporteren ==


    Please report all KDE bugs and feature requests at [http://bugs.kde.org/ 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.  
    Het melden van bugs is een kleine, maar waardevolle bijdrage aan KDE, en er is een website waar u elke bug kunt melden of nieuwe functionaliteit voor KDE kunt aanvragen: [http://bugs.kde.org/ bugs.kde.org]. De enige eis aan uw kant is basiskennis van het Engels. Daarmee zult u, na enkele aanvullende richtlijnen, nuttige bugmeldingen kunnen ingeven en dus de hele KDE-gemeenschap en uzelf kunnen helpen.
     
    Eerste moet u een account openen op de website. U kunt dat [https://bugs.kde.org/createaccount.cgi hier] doen. Zodra uw account bevestigd is, kunt u bugs melden.
     
    Er zijn gewoonlijk twee verschillende situaties om een ​​bug te melden:
     
    * You notice something which is not working properly or not working at all, a bad design, a missed functionality... If this is your case, open the application <menuchoice>Help -> Report Bug...</menuchoice> menu. You will then be guided to [http://bugs.kde.org bugs.kde.org]. Some information will be automatically picked up, like the application version number.
     
    * Your program disappears and another window appears named "The KDE crash Handler". Don't get scared! You will be guided to efficiently report this crash. The link in the dialog "Learn more about bug reporting" will explain you the process. If you choose to report the problem, click on <menuchoice>Report Bug</menuchoice> and an assistant will guide you through the steps. The requisite to report a crash is to have your distribution debug packages installed in order to provide a valid backtrace.
     
    And these are a few tips on how to write good bug reports:
     
    * Write it in English. You can switch every KDE application language through <menuchoice>Help -> Switch Application Language...</menuchoice>, so go there and choose American English as the primary language. Then restart the application. That can help you in explaining what happens.
     
    * Be specific. One bug per report only! Do not mix different problems in the same report.
     
    * Be clear. Explain the steps that lead to the bug so that we can reproduce them easily.
     
    * Include screenshots: a picture is worth many words so attach a screenshot to the bug report. You can use [[Special:mylanguage/KSnapshot|KSnapshot]] to take screenshots. Also, do not link to an external web link which can expire, use the Attachments link at the bottom of the bug report.
     
    * Include the backtrace within the bug report as a comment, it makes it easier to find duplicates for us (do not attach the backtrace as a text file).
     
    * Clearly separate facts from speculation: only describe what happens. For a design problem, include a mock-up if possible.
     
    If you are testing trunk or the beta, if you kept your precedent settings, sometimes you will want to check with a new user.
     
    Also notice that [http://forums.kde.org Forums] have a [http://forum.kde.org/viewforum.php?f=201 section about Beta Releases].
     
    A good guide to bug reporting can be found [http://blogs.fsfe.org/myriam/2011/10/when-is-a-bug-report-useful/ here].


    ----
    ----
    Line 45: Line 91:
    '''Hoe een console te openen'''
    '''Hoe een console te openen'''


    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
    Bij het melden van een probleem op IRC of op een mailing list komt het vaak voor dat uw helpers u vragen een console (ook terminal genoemd) te openen. Een console is een tekstvenster dat u kunt gebruiken om commando's aan uw computer te geven. U kunt een console openen door op ALT_F2 te drukken. Een invoervenster opent. Type het volgende om een console te openen:
     
    {{input|1=konsole}}
    <pre>konsole</pre>
     
    And a console will open. If this does not work, you may not have it installed. In this case, type ALT_F2 and call


    <pre>xterm</pre>
    Als dit niet werkt, kan het zijn dat u het niet geïnstalleerd hebt. Toets in dit geval ALT_F2 en voer in:
    {{input|1=xterm}}




    {|style="text-align:right"
    {|style="text-align:right"
    |'''Back to [[Getting_Help]]'''
    |'''Terug naar [[Special:myLanguage/Getting_Help|Hulp]]'''
    |}
    |}


    [[Category:Getting Started]]
    [[Category:Aan de slag/nl]]

    Revision as of 06:00, 14 November 2017

    IRC gebruiken om geholpen te worden

    Nu volgens een aantal tips voor het stellen van vragen om de kans op antwoorden te vergroten, in het bijzonder in #kde op Freenode:

    • Vraag niet of je een vraag mag stellen, stel gewoon je vraag: het irc.freenode.net kanaal #kde is een kanaal voor ondersteuning van gebruikers, dus we verwachten uw vragen - ga uw gang .
    • Be ready with as much relevant details about your system as you can find: Questions you are likely to be asked are:
      • What distribution do you use (and what version?) e.g. Kubuntu 12.1
      • what version of KDE you are running — if you don't know, open Konsole and type kde4-config --kde-version and look at the version numbers given there
      • how you installed it — mostly likely from your distribution repositories.

    You probably won't need to give all of this information straight away, but if you know how to find it quickly it often helps

    • Probeer eerst zelf het probleem op te lossen alvorens een oplossing te vragen: Google is uw vriend (zoeken naar foutmeldingen met Google levert vaak nuttige informatie). Kijk ook bij Oplossen van KDE problemen - het advies wat daar staat is waarschijnlijk wat ook in #kde wordt geadviseerd, dus kijk hier eerst .
    • Probeer ook zeker te weten of het probleem door KDE veroorzaakt wordt en niet door een ander onderdeel van uw systeem (zoals bijvoorbeeld een probleem met X of ALSA). Probeer, indien mogelijk, een alternatieve niet-KDE applicatie om te zien of het probleem zich daar ook voordoet. Natuurlijk is het geen probleem om vragen te stellen als u er niet uitkomt.
    • Use the Forum. Try asking a question on the forum. If the discussion brings up interesting information you might add it to UserBase, so that it can help others.
    • Be prepared to wait! Often on IRC, 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! In some cases there could be hours between your question being asked and someone who knows the answer coming on-line (remember that KDE users are all over the world) so sometimes you just have to ask again at a different time of day.
    • Als u geen antwoord krijgt in #kde, dan kunt u ook het kanaal van uw distributie proberen (bijv. #suse, #kde-freebsd, etc), of een mailing list: zie lists.kde.org of het forum.
    • Het belangrijkste is dat u geduldig en beleefd bent. Onthoud dat de mensen die helpen allemaal vrijwilligers zijn, en het druk kunnen hebben met andere dingen dan helpen.

    Als u een probleem met geluid hebt in KDE, lees dan eerst Problemen met geluid.

    Als uw vraag over ontwikkeling gaat, kijk dan op de pagina over hoe bijdragen op KDE TechBase

    Because KDE is so actively developed, changes arrive very frequently, so don't be surprised if you can't find any written information. Ask in IRC, the Forum or a mailing list, and when you have an answer, register an account on UserBase and add the information to the relevant page. At the same time as learning about your system you will be helping others do the same

    The Forums

    Another great place to get help is the KDE Community Forums. It is always a good idea to search the forums first. Maybe your question has already been answered. If not, find an appropriate forum and start a thread. Don't expect an immediate answer, but remember to come back regularly to participate in the discussion as it gets going. Remember that the forums are run by users like yourself.

    The KDE Community forums offer a "guided post" feature that can help you post your question in the appropriate forum, increasing the chance of having it seen by people knowledgeable on the matter. It is accessible as a large "New Post" button on the forums' homepage, so if you have any doubts, that is the place to start.

    The forums have an extensive search feature: prior to posting try finding if your question has already been answered, or there are hints that might help you solve your issue. If there is no satisfactory solution for your problem, make a new post. To search, enter keywords in the upper right box of any forum page. By default this will search the whole forums. For extended searches, click on the "Search" link under the "KDE Community Forums" banner.

    If your question has been properly answered, consider marking a topic as "solved". It is a very little step, but quite helpful for other users and staff, because it tells them that there are no more issues. To mark a topic as solved, choose the topic with the best answer in the thread, and click the green tick mark under it. If you go back to the topic list you will notice a green tick mark next to the topic's title as well.


    Most distributions have forums of their own; these can also be valuable. The web pages of your distribution should provide links to its forums.

    Specifieke vragen over besturingssystemen

    For questions relating to the desktop use of KDE with a particular operating system (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. An example of questions that do not directly involve KDE is "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.

    Als u geen GNU/Linux gebruikt, kunt u de kde-nonlinux (aanmelden) mailing list proberen. Ook bijzonder nuttig zijn zoekopdrachten op uw favoriete zoekmachine, zoals Google, en zoekt op de Usenet-archieven.

    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 or find them through your browser search engine.

    If you are searching for packages you may consider checking the ftp servers for your distribution, including the "contrib" sections, as well as indexing servers such as rpmfind.net. Wherever possible, install the package that your distro offers directly through its package manager.

    Fouten in KDE rapporteren

    Het melden van bugs is een kleine, maar waardevolle bijdrage aan KDE, en er is een website waar u elke bug kunt melden of nieuwe functionaliteit voor KDE kunt aanvragen: bugs.kde.org. De enige eis aan uw kant is basiskennis van het Engels. Daarmee zult u, na enkele aanvullende richtlijnen, nuttige bugmeldingen kunnen ingeven en dus de hele KDE-gemeenschap en uzelf kunnen helpen.

    Eerste moet u een account openen op de website. U kunt dat hier doen. Zodra uw account bevestigd is, kunt u bugs melden.

    Er zijn gewoonlijk twee verschillende situaties om een ​​bug te melden:

    • You notice something which is not working properly or not working at all, a bad design, a missed functionality... If this is your case, open the application Help -> Report Bug... menu. You will then be guided to bugs.kde.org. Some information will be automatically picked up, like the application version number.
    • Your program disappears and another window appears named "The KDE crash Handler". Don't get scared! You will be guided to efficiently report this crash. The link in the dialog "Learn more about bug reporting" will explain you the process. If you choose to report the problem, click on Report Bug and an assistant will guide you through the steps. The requisite to report a crash is to have your distribution debug packages installed in order to provide a valid backtrace.

    And these are a few tips on how to write good bug reports:

    • Write it in English. You can switch every KDE application language through Help -> Switch Application Language..., so go there and choose American English as the primary language. Then restart the application. That can help you in explaining what happens.
    • Be specific. One bug per report only! Do not mix different problems in the same report.
    • Be clear. Explain the steps that lead to the bug so that we can reproduce them easily.
    • Include screenshots: a picture is worth many words so attach a screenshot to the bug report. You can use KSnapshot to take screenshots. Also, do not link to an external web link which can expire, use the Attachments link at the bottom of the bug report.
    • Include the backtrace within the bug report as a comment, it makes it easier to find duplicates for us (do not attach the backtrace as a text file).
    • Clearly separate facts from speculation: only describe what happens. For a design problem, include a mock-up if possible.

    If you are testing trunk or the beta, if you kept your precedent settings, sometimes you will want to check with a new user.

    Also notice that Forums have a section about Beta Releases.

    A good guide to bug reporting can be found here.


    Hoe een console te openen

    Bij het melden van een probleem op IRC of op een mailing list komt het vaak voor dat uw helpers u vragen een console (ook terminal genoemd) te openen. Een console is een tekstvenster dat u kunt gebruiken om commando's aan uw computer te geven. U kunt een console openen door op ALT_F2 te drukken. Een invoervenster opent. Type het volgende om een console te openen:

    konsole

    Als dit niet werkt, kan het zijn dat u het niet geïnstalleerd hebt. Toets in dit geval ALT_F2 en voer in:

    xterm


    Terug naar Hulp