icewm: could not open windows

Forum Forums Orphaned Posts antiX-17 “Heather Heyer, Helen Keller” icewm: could not open windows

  • This topic has 6 replies, 3 voices, and was last updated Dec 16-2:05 am by isminaki.
Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #14232
    Member
    isminaki

      Good morning,

      randomly, I have one very strange problem: I can not open any more programs.
      I could not really figure out when it happens.
      It happens only after some time of working with the machine and a lot of windows are open (12 – 15).
      After closing some windows, the problem disappears.
      Did anyone have this problem as well?
      What more information do you need?

      I am running testing 64 bit install.

      sunny regards

      #14233
      Member
      isminaki
        Helpful
        Up
        0
        ::

        Just now it happened again. Maybe 6 or 7 windows open.
        I wanted to switch to RoxJWM Desktop and was thrown back to login screen. (luckily, no unsaved data)

        #14238
        Anonymous
          Helpful
          Up
          0
          ::

          Did you check your CPU utilization short before the moment when it happens?
          Which applications did you use at the time?

          Both could easily be the reason.

          (Never run Debian Testing.)

          #14243
          Member
          isminaki
            Helpful
            Up
            0
            ::

            Did you check your CPU utilization short before the moment when it happens?

            Very little. Nothing CPU consuming running. One digit percentage.

            Which applications did you use at the time?

            Slimjet
            Palemoon
            LO Writer
            LO Calc
            Rox-filer 2 or 3 times
            spacefm

            (Never run Debian Testing.)

            Why not?

            #14250
            Anonymous
              Helpful
              Up
              0
              ::

              (Never run Debian Testing.)

              Why not?

              I prefer a dozen of dead pilots TESTING over myself, sitting in there and hoping “everything’s gonna be fine”. And you?

              #14266
              Anonymous
                Helpful
                Up
                0
                ::

                ismaniki, it’s likely the events related to the error condition are logged. Do you know the “dmesg” command?
                Toward troubleshooting prior events, I would inspect the contents of .xsession-errors file in home directory, and the logfiles residing within /var/log/

                #14282
                Member
                isminaki
                  Helpful
                  Up
                  0
                  ::

                  I know very little of the dmesg command. In the past, I only searched it for “error”.
                  Just now, I had a look at it and I found some red lines. (red in LXTerminal):

                  [  624.674970] mei_me 0000:00:16.0: wait hw ready failed
                  [  624.674980] mei_me 0000:00:16.0: hw_start failed ret = -62
                  [  624.675002] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING fw status = 1E000245 60002306 00000200 00004400 00000000 40000010
                  [  624.675008] mei_me 0000:00:16.0: H_RST is set = 0x80000011
                  [  626.722922] mei_me 0000:00:16.0: wait hw ready failed
                  [  626.722932] mei_me 0000:00:16.0: hw_start failed ret = -62
                  [  626.722963] mei_me 0000:00:16.0: unexpected reset: dev_state = RESETTING fw status = 1E000245 60002306 00000200 00004400 00000000 40000010
                  [  626.722966] mei_me 0000:00:16.0: reset: reached maximal consecutive resets: disabling the device
                  [  626.722971] mei_me 0000:00:16.0: device disabled = -19
                  

                  Sorry, but in my home-directory, there is no .xsession-errors file.

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