Could not start D-bus, can you call qdbus?











up vote
0
down vote

favorite
1












I am using fedora 22.



Yesterday it was working fine. But when I opened it today after entering my password it says "could not start D-bus, can you call qdbus?"



When I searched for the solution in net it asked to download some qdbus packages and I installed them and after that I don't see anything expect black screen...



Someone please help me fix this issue. I want to use it badly....



I have important files in the system and i want to access them ASAP....



Thank you










share|improve this question




























    up vote
    0
    down vote

    favorite
    1












    I am using fedora 22.



    Yesterday it was working fine. But when I opened it today after entering my password it says "could not start D-bus, can you call qdbus?"



    When I searched for the solution in net it asked to download some qdbus packages and I installed them and after that I don't see anything expect black screen...



    Someone please help me fix this issue. I want to use it badly....



    I have important files in the system and i want to access them ASAP....



    Thank you










    share|improve this question


























      up vote
      0
      down vote

      favorite
      1









      up vote
      0
      down vote

      favorite
      1






      1





      I am using fedora 22.



      Yesterday it was working fine. But when I opened it today after entering my password it says "could not start D-bus, can you call qdbus?"



      When I searched for the solution in net it asked to download some qdbus packages and I installed them and after that I don't see anything expect black screen...



      Someone please help me fix this issue. I want to use it badly....



      I have important files in the system and i want to access them ASAP....



      Thank you










      share|improve this question















      I am using fedora 22.



      Yesterday it was working fine. But when I opened it today after entering my password it says "could not start D-bus, can you call qdbus?"



      When I searched for the solution in net it asked to download some qdbus packages and I installed them and after that I don't see anything expect black screen...



      Someone please help me fix this issue. I want to use it badly....



      I have important files in the system and i want to access them ASAP....



      Thank you







      linux fedora kde d-bus plasma






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 13 '16 at 6:33

























      asked Nov 11 '16 at 8:13









      Manoj CS

      14




      14






















          1 Answer
          1






          active

          oldest

          votes

















          up vote
          -1
          down vote



          accepted










          I found the problem....



          Last day I modified the .bashrc file and included 2 lines to source a settings script of a software and that was causing the problem....



          Now that i removed those 2 lines my problem is solved....






          share|improve this answer























          • This doesn't tell people, coming along since with the same problem, what the settings were and how they caused the problem.
            – JdeBP
            Oct 4 '17 at 8:18











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f322527%2fcould-not-start-d-bus-can-you-call-qdbus%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes








          up vote
          -1
          down vote



          accepted










          I found the problem....



          Last day I modified the .bashrc file and included 2 lines to source a settings script of a software and that was causing the problem....



          Now that i removed those 2 lines my problem is solved....






          share|improve this answer























          • This doesn't tell people, coming along since with the same problem, what the settings were and how they caused the problem.
            – JdeBP
            Oct 4 '17 at 8:18















          up vote
          -1
          down vote



          accepted










          I found the problem....



          Last day I modified the .bashrc file and included 2 lines to source a settings script of a software and that was causing the problem....



          Now that i removed those 2 lines my problem is solved....






          share|improve this answer























          • This doesn't tell people, coming along since with the same problem, what the settings were and how they caused the problem.
            – JdeBP
            Oct 4 '17 at 8:18













          up vote
          -1
          down vote



          accepted







          up vote
          -1
          down vote



          accepted






          I found the problem....



          Last day I modified the .bashrc file and included 2 lines to source a settings script of a software and that was causing the problem....



          Now that i removed those 2 lines my problem is solved....






          share|improve this answer














          I found the problem....



          Last day I modified the .bashrc file and included 2 lines to source a settings script of a software and that was causing the problem....



          Now that i removed those 2 lines my problem is solved....







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jun 8 '17 at 7:11

























          answered Nov 13 '16 at 17:47









          Manoj CS

          14




          14












          • This doesn't tell people, coming along since with the same problem, what the settings were and how they caused the problem.
            – JdeBP
            Oct 4 '17 at 8:18


















          • This doesn't tell people, coming along since with the same problem, what the settings were and how they caused the problem.
            – JdeBP
            Oct 4 '17 at 8:18
















          This doesn't tell people, coming along since with the same problem, what the settings were and how they caused the problem.
          – JdeBP
          Oct 4 '17 at 8:18




          This doesn't tell people, coming along since with the same problem, what the settings were and how they caused the problem.
          – JdeBP
          Oct 4 '17 at 8:18


















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f322527%2fcould-not-start-d-bus-can-you-call-qdbus%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          List directoties down one level, excluding some named directories and files

          list processes belonging to a network namespace

          list systemd RuntimeDirectory mounts