Difficulty with Desktop, Connman, & wifi

Forum Forums Official Releases antiX-21/22 “Grup Yorum” Difficulty with Desktop, Connman, & wifi

  • This topic has 7 replies, 4 voices, and was last updated Apr 28-3:52 pm by scruffyeagle.
Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #81428
    Member
    scruffyeagle

      I’m running AntiX v21.4 with a zzz-IceWM desktop. I’ve got the desktop working well, initializing with a black background, and 18 launchers. The startup routine is doing something different than v19.4, via throwing up a box for Connman into the middle of the screen when the desktop starts. I don’t really mind that, but it’s a small nuisance because Connman keeps turning the wifi on without being told to.

      Of those 18 launchers, only 5 refer to programs that launch via the root partition. The rest refer to files in partitions on my external hard drive. Those partitions are all encrypted, and I never use the root partition for storing data. So, the launchers don’t get assigned the colors & icons associated with the programs used to edit their respective files, until AFTER the external drive partitions have been mounted via VeraCrypt, AND the desktop has been refreshed at least once.

      The only way I know of for refreshing the desktop, is via clicking Desktop/Other Desktops/zzz-IceWM. Which of course triggers display of Connman, and turns the wifi back on.

      It would be nice if I could refresh the desktop without triggering Connman… Or at least, without turning the wifi back on. I thought, maybe Connman could be moved out of the zzz-IceWM routines, and into /.desktop-session/startup?

      • This topic was modified 1 year ago by scruffyeagle.
      #81433
      Member
      PPC
        Helpful
        Up
        0
        ::

        It would be nice if I could refresh the desktop without triggering Connman… Or at least, without turning the wifi back on. I thought, maybe Connman could be moved out of the zzz-IceWM routines, and into /.desktop-session/startup

        Hum… connman is in desktop-session.conf – it’s being run by the “network-check-antix”- try commenting out that line and restart your computer/session…

        the launchers don’t get assigned the colors & icons associated with the programs used to edit their respective files, until AFTER the external drive partitions have been mounted via VeraCrypt, AND the desktop has been refreshed at least once.

        I can think of a work around that problem – copy the .desktop files to your root’s applications folder and change their contents so the exec lines to point to the executable in the encripted folders BUT the icon’s are icons copied to an unencripted folder … It’s a bit of tedious work but the end result should look better, every time you start your computer.

        P.

        • This reply was modified 1 year ago by PPC.
        • This reply was modified 1 year ago by PPC.
        #81457
        Member
        scruffyeagle
          Helpful
          Up
          0
          ::

          Hi, PPC! I tried to apply your suggestions, but didn’t get far. There wasn’t any line containing “network-check” in the desktop-session.conf file.

          Maybe I didn’t express myself clearly before…
          The encrypted files are ordinary work files. “diary.odt”, for example. In this example, the simlink I’ve set on the desktop points to the file on encrypted partition 7 on the external hard drive. zzz-IceWM will show that link as an unadorned white page, when it can’t find the link’s target. After I mount the partition 7, then the target is available. But, the desktop can’t find it until I make it reload itself. During the reloading of the desktop, it traces the link, finds the target, and assigns & displays a colored icon (replaces the white) to the link based on whichever executable program is registered for working with that file type. (In this case, LibreOffice.) So, it’s not that the executable is being kept on the external hard drive; it’s just the work file.

          #81461
          Moderator
          BobC
            Helpful
            Up
            0
            ::

            Which desktop are you using?

            If it’s Rox-IceWM, try toggling the Rox panel off, and do it again to turn it on again.

            Main menu >> Desktop >> Roxpanel on/off

            If that works, you could either do that from the menu, or add a little icon to your toolbar, or map a key to do it for you.

            #81462
            Moderator
            caprea
              Helpful
              Up
              0
              ::

              Might in the /.dektop-session/startup file there is
              cmst -m &
              for starting connman, which could be outcommented

              Also in the settings of connman under “status” the wifi can be set to “off” for not auto connecting.

              #81887
              Member
              scruffyeagle
                Helpful
                Up
                0
                ::

                Hi, BobC. Thanks for the reply.

                I’m using zzz-IceWM.
                So, I’ve been making the desktop reload via Menu > Desktop > Other Desktops > zzz-IceWM.

                #81888
                Member
                scruffyeagle
                  Helpful
                  Up
                  0
                  ::

                  Hi, caprea. Thanks for the reply.

                  In my .desktop-session/startup file, the line was already commented out.
                  I found it as “#cmst -m & “.

                  Yes, that control is exactly what I meant, when I said it’s turning itself back on.
                  I repeatedly move the slider for wifi from on to off, to put the machine into airplane mode – but, every time connman refreshes (either from fresh startup, or desktop refresh), that slider gets moved back to “on”.

                  #82220
                  Member
                  scruffyeagle
                    Helpful
                    Up
                    0
                    ::

                    After draining the BIOS charge by disconnecting the coin battery inside the Dell Precision M6300 laptop, I was able to disable both wifi & bluetooth in the BIOS; effectively putting the laptop into persistent “airplane mode”.

                    This change was picked up on, by Connman. Now, when Connman initializes, it recognizes that there’s no wifi, and doesn’t include wifi in the status display. Problem solved. No more repeatedly turning off the wifi.

                    I think this thread can be marked as “solved”.
                    Thanks.

                  Viewing 8 posts - 1 through 8 (of 8 total)
                  • You must be logged in to reply to this topic.