GD Bus error on startup & unable to shutdown/reboot using GUI …

Forum Forums New users New Users and General Questions GD Bus error on startup & unable to shutdown/reboot using GUI …

  • This topic has 21 replies, 5 voices, and was last updated Mar 8-4:25 pm by mikey777.
Viewing 5 posts - 16 through 20 (of 20 total)
  • Author
    Posts
  • #33363
    Moderator
    christophe
      Helpful
      Up
      0
      ::

      Incidentally, have you seen this?

      https://www.antixforum.com/forums/topic/lxpolkit-issue/

      Perhaps this has some effect on LXDE as well?

      confirmed antiX frugaler, since 2019

      #33364
      Moderator
      christophe
        Helpful
        Up
        0
        ::

        My first 2 LXDE setups were an experiment of “frugal-in-virtualbox.” So, today I reinstalled (from antiX core 19.1) as a regular install. (The new(er), improved cli-installer is super, by the way.)

        I was offered to download & install some packages useful to DE’s prior to install, which I did. Then I installed as normal, rebooted, ran apt update & upgrade, installed only xorg & lxde, then rebooted a final time. (Thanks for bearing with me this far!)

        Upon restart, the GDBus error DID NOT APPEAR. The screen locker option was in the preferences menu, and I unchecked it. And the system was able to shutdown from the GUI as normal.

        What do you think of that?

        • This reply was modified 3 years, 2 months ago by christophe. Reason: noted iso image version number

        confirmed antiX frugaler, since 2019

        #33366
        Anonymous
          Helpful
          Up
          0
          ::

          The message of the incoming mail says that consolekit is not found.
          Did he check if the package is installed?

          #33384
          Member
          mikey777
            Helpful
            Up
            0
            ::

            @christophe
            I have two other installations of antixcore-LXDE on SSD, on two other laptops and went to check these, concerning our discussion on screenlocker & disabling it. They have been working normally, since I installed them about 3 months ago – very stable, no problems whatsoever. In both cases, screenlocker is listed under Desktop Session Settings, though have never had any problems with it on those laptops. However, to mitigate against any potential problems in that direction, I have now turned screenlocker off, thanks to your suggestion. I have also installed xscreensaver & xscreensaver-data.

            I’ve come to the conclusion that the most likely cause for screenlocker not being listed on the netbook, under Desktop Session Settings, is the installed system had become corrupted. I think the most likely explanation for this corruption, was having to repeatedly use the netbook’s on/off switch, as the only means of shutting-down, when the display went blank. I thought this would eventually break the system – and it did. Following this, the GD Bus errors started, and the system failed to recognise attached USB-drives, and my falkon browser stopped working. Also, I noticed that when the netbook booted, it had changed from init to runit …

            I am going to reinstall antixcore-LXDE on the netbook. This time I’ll install a separate /home partition, to preserve configuration files, just in case things go awry again. Now that the the screenlocker issue appears to have been sorted out, I’m expecting things to continue more smoothly with the netbook. Many thanks again Christophe, I have really appreciated your help πŸ™‚

            Also thanks to sybok, fatmac & male for your ideas – much appreciated.

            • This reply was modified 3 years, 2 months ago by mikey777.
            • This reply was modified 3 years, 2 months ago by mikey777.
            • This reply was modified 3 years, 2 months ago by mikey777.

            β–ͺ 32-bit antix19.4-core+LXDE installed on :
            - (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
            β–ͺ 64-bit antix21-base+LXDE installed on:
            - (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
            - (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

            #33386
            Member
            mikey777
              Helpful
              Up
              0
              ::

              The message of the incoming mail says that consolekit is not found.
              Did he check if the package is installed?

              Thanks.
              Yes, it was already installed – checked with# dpkg –list

              β–ͺ 32-bit antix19.4-core+LXDE installed on :
              - (2011) Samsung NP-N145 Plus (JP04UK) – single-core CPU Intel Atom N455@1.66GHz, 2GB RAM, integrated graphics.
              β–ͺ 64-bit antix21-base+LXDE installed on:
              - (2008) Asus X71Q (7SC002) – dual CPU Intel T3200@2.0GHz, 4GB RAM. Graphics: Intel Mobile 4 Series, integrated graphics
              - (2007) Packard Bell Easynote MX37 (ALP-Ajax C3) – dual CPU Intel T2310@1.46GHz, 2GB RAM. Graphics: Silicon Integrated Systems.

            Viewing 5 posts - 16 through 20 (of 20 total)
            • You must be logged in to reply to this topic.