• Weird X freeze (Mageia 7)

    From William Unruh@2:250/1 to All on Wed Sep 16 21:14:04 2020
    I am suddenly having a problem with my X. I am on Mga 7 with Plasma
    desktop. In the past couple of days my system has suddenly begun to
    misbehave. If I leave it for say 1/2 and hour, when I come back the X
    screen is frozen-- no updates, no dragging or typing or anything. If I
    do alt-ctrl-F2 to go to a terminal, and immediately do alt-ctrl-F1 to go
    back to X, everything works fine, and it is clear that the system heard
    what I tried to do when the screen was frozen, and thought it had
    changed things, because the screen now has the updates I thought I did.
    Things work fine, as log as I do not leave the machine alone and X
    unused for some time.

    I have no idea what could be doing this. Looking in journalctl, the only
    thing that might be suspicious is powerdevil. Here are the lines from
    the output of journalctl from around the time when I came back and found
    it frozen.


    Sep 16 12:23:57 tunnel.physics.ubc.ca kernel: Shorewall:net-fw:DROP:IN=eno1 OUT= MAC=4c:ed:fb:c2:2a:f3:a0:ab:1b:88:6e:58:08:00 SRC=124.65.18.102 DST=192.168.0.3 LEN=48 TOS=0x00 PREC=0x00 TTL=119 ID=50972 PROTO=TCP SPT=35397 DPT=22 WINDOW=65535 RES=0x00 SYN URGP=0
    Sep 16 12:25:01 tunnel.physics.ubc.ca crond[32358]: pam_unix(crond:session): session opened for user root by (uid=0)
    Sep 16 12:25:01 tunnel.physics.ubc.ca CROND[32364]: (root) CMD (/usr/local/bin/ssh-ipset-attempt)
    Sep 16 12:25:01 tunnel.physics.ubc.ca CROND[32358]: pam_unix(crond:session): session closed for user root
    Sep 16 12:28:19 tunnel.physics.ubc.ca org_kde_powerdevil[6274]: powerdevil: Kbd backlight brightness value: 0
    Sep 16 12:30:01 tunnel.physics.ubc.ca crond[32628]: pam_unix(crond:session): session opened for user root by (uid=0)
    Sep 16 12:30:01 tunnel.physics.ubc.ca CROND[32635]: (root) CMD (/usr/local/bin/ssh-ipset-attempt)
    Sep 16 12:30:01 tunnel.physics.ubc.ca CROND[32628]: pam_unix(crond:session): session closed for user root
    Sep 16 12:33:43 tunnel.physics.ubc.ca kernel: Shorewall:net-fw:DROP:IN=eno1 OUT= MAC=4c:ed:fb:c2:2a:f3:a0:ab:1b:88:6e:58:08:00 SRC=92.118.161.13 DST=192.168.0.3 LEN=44 TOS=0x00 PREC=0x00 TTL=246 ID=54321 PROTO=TCP SPT=63454 DPT=22 WINDOW=65535 RES=0x00 SYN URGP=0
    Sep 16 12:33:49 tunnel.physics.ubc.ca org_kde_powerdevil[6274]: powerdevil: ACTIVE SESSION PATH CHANGED: "/"
    Sep 16 12:33:49 tunnel.physics.ubc.ca org_kde_powerdevil[6274]: powerdevil: Switched to inactive session - leaving unchanged
    Sep 16 12:33:49 tunnel.physics.ubc.ca acpid[1034]: client 5373[0:0] has disconnected
    Sep 16 12:33:49 tunnel.physics.ubc.ca acpid[1034]: client connected from 5373[0:0]
    Sep 16 12:33:49 tunnel.physics.ubc.ca acpid[1034]: 1 client rule loaded
    Sep 16 12:33:49 tunnel.physics.ubc.ca org_kde_powerdevil[6274]: powerdevil: ACTIVE SESSION PATH CHANGED: "/org/freedesktop/login1/session/c3"
    Sep 16 12:33:49 tunnel.physics.ubc.ca org_kde_powerdevil[6274]: powerdevil: Current session is now active
    Sep 16 12:33:49 tunnel.physics.ubc.ca kwin_x11[6240]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 52345, resource id: 27246112, major code: 18 (ChangeProperty), minor code: 0
    Sep 16 12:33:49 tunnel.physics.ubc.ca kcminit[379]: Initializing "kcm_mouse" : "kcminit_mouse"
    Sep 16 12:33:49 tunnel.physics.ubc.ca kwin_x11[6240]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 52441, resource id: 60817413, major code: 18 (ChangeProperty), minor code: 0


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From J.O. Aho@2:250/1 to All on Wed Sep 16 21:32:18 2020
    On 16/09/2020 22:14, William Unruh wrote:
    I am suddenly having a problem with my X. I am on Mga 7 with Plasma
    desktop. In the past couple of days my system has suddenly begun to misbehave.

    Have you recently added a new widget?
    Or you using one that fetches data externally?

    If yes on one or more of those, I would start to remove the widgets and
    see if you get the stability back.


    --

    //Aho

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Wed Sep 16 21:45:50 2020
    On 2020-09-16, J.O. Aho <user@example.net> wrote:
    On 16/09/2020 22:14, William Unruh wrote:
    I am suddenly having a problem with my X. I am on Mga 7 with Plasma
    desktop. In the past couple of days my system has suddenly begun to
    misbehave.

    Have you recently added a new widget?
    Or you using one that fetches data externally?

    No I have not.


    If yes on one or more of those, I would start to remove the widgets and
    see if you get the stability back.



    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From faeychild@2:250/1 to All on Wed Sep 16 23:00:55 2020
    On 17/9/20 6:14 am, William Unruh wrote:

    I have no idea what could be doing this. Looking in journalctl, the only thing that might be suspicious is powerdevil. Here are the lines from
    the output of journalctl from around the time when I came back and found
    it frozen.

    I encountered baffling erratic Plasma behavior after an update.

    I found (stumbled upon) that my nvidia driver had been replaced with
    nouveau.


    --
    faeychild
    Running plasmashell 5.15.4 on 5.7.19-desktop-1.mga7 kernel.
    Mageia release 7 (Official) for x86_64 installed via Mageia-7-x86_64-DVD.iso


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Thu Sep 17 02:22:47 2020
    On 2020-09-16, faeychild <faeychild@nomail.afraid.org> wrote:
    On 17/9/20 6:14 am, William Unruh wrote:

    I have no idea what could be doing this. Looking in journalctl, the only
    thing that might be suspicious is powerdevil. Here are the lines from
    the output of journalctl from around the time when I came back and found
    it frozen.

    I encountered baffling erratic Plasma behavior after an update.

    I found (stumbled upon) that my nvidia driver had been replaced with nouveau.

    Unfortunately/fortunately I have Intel video.
    00:02.0 VGA compatible controller: Intel Corporation 8th Gen Core Processor Gaussian Mixture Model
    on a Canon Lake processor.


    My suspicion is that some sort of screen saver is coming in-- not
    actually doing anything to "screen save" but managing to switch off X
    without actually replacing it. Unfortunately all of the attempts to find
    what it is, and what program might be doing this have not succeeded yet.




    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Thu Sep 17 04:07:11 2020
    Hmm, I finally looked at SystemSetings->PowerMangement->EnergySavings.
    It was set up to blank the screen after 20 min., which made sense since
    my problems seemed to be going at about that time. I removed the check
    mark, and, so far, it is not behaving badly anymore (Just went out for
    an hour's walk and when I cam back, the Desktop was on and working).
    So something seems to getting in the way of the screen blanking, but the desktop is being shut off, but hitting a key or moving the mouse does
    not get it out of that. Looks like a bug to me, but is it me that is
    the bug, or some program?

    On 2020-09-17, William Unruh <unruh@invalid.ca> wrote:
    On 2020-09-16, faeychild <faeychild@nomail.afraid.org> wrote:
    On 17/9/20 6:14 am, William Unruh wrote:

    I have no idea what could be doing this. Looking in journalctl, the only >>> thing that might be suspicious is powerdevil. Here are the lines from
    the output of journalctl from around the time when I came back and found >>> it frozen.

    I encountered baffling erratic Plasma behavior after an update.

    I found (stumbled upon) that my nvidia driver had been replaced with
    nouveau.

    Unfortunately/fortunately I have Intel video.
    00:02.0 VGA compatible controller: Intel Corporation 8th Gen Core Processor
    Gaussian Mixture Model
    on a Canon Lake processor.


    My suspicion is that some sort of screen saver is coming in-- not
    actually doing anything to "screen save" but managing to switch off X
    without actually replacing it. Unfortunately all of the attempts to find
    what it is, and what program might be doing this have not succeeded yet.




    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Melzzzzz@2:250/1 to All on Thu Sep 17 05:20:09 2020
    On 2020-09-17, William Unruh <unruh@invalid.ca> wrote:
    On 2020-09-16, faeychild <faeychild@nomail.afraid.org> wrote:
    On 17/9/20 6:14 am, William Unruh wrote:

    I have no idea what could be doing this. Looking in journalctl, the only >>> thing that might be suspicious is powerdevil. Here are the lines from
    the output of journalctl from around the time when I came back and found >>> it frozen.

    I encountered baffling erratic Plasma behavior after an update.

    I found (stumbled upon) that my nvidia driver had been replaced with
    nouveau.

    Unfortunately/fortunately I have Intel video.
    00:02.0 VGA compatible controller: Intel Corporation 8th Gen Core Processor
    Gaussian Mixture Model
    on a Canon Lake processor.


    My suspicion is that some sort of screen saver is coming in-- not
    actually doing anything to "screen save" but managing to switch off X
    without actually replacing it. Unfortunately all of the attempts to find
    what it is, and what program might be doing this have not succeeded yet.

    What DE are you using?





    --
    current job title: senior software engineer
    skills: c++,c,rust,go,nim,haskell...

    press any key to continue or any other to quit...
    U ničemu ja ne uživam kao u svom statusu INVALIDA -- Zli Zec
    Svi smo svedoci - oko 3 godine intenzivne propagande je dovoljno da jedan narod poludi -- Zli Zec
    Na divljem zapadu i nije bilo tako puno nasilja, upravo zato jer su svi
    bili naoruzani. -- Mladen Gogala

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: usenet-news.net (2:250/1@fidonet)
  • From J.O. Aho@2:250/1 to All on Thu Sep 17 06:45:24 2020
    On 16/09/2020 22:45, William Unruh wrote:
    On 2020-09-16, J.O. Aho <user@example.net> wrote:
    On 16/09/2020 22:14, William Unruh wrote:
    I am suddenly having a problem with my X. I am on Mga 7 with Plasma
    desktop. In the past couple of days my system has suddenly begun to
    misbehave.

    Have you recently added a new widget?
    Or you using one that fetches data externally?

    No I have not.

    Checked your ~/.xsession-errors for error messages?

    --

    //Aho


    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Grimble@2:250/1 to All on Thu Sep 17 15:55:56 2020
    On 16/09/2020 21:14, William Unruh wrote:
    I am suddenly having a problem with my X. I am on Mga 7 with Plasma
    desktop. In the past couple of days my system has suddenly begun to misbehave. If I leave it for say 1/2 and hour, when I come back the X
    screen is frozen-- no updates, no dragging or typing or anything. If I
    do alt-ctrl-F2 to go to a terminal, and immediately do alt-ctrl-F1 to go
    back to X, everything works fine, and it is clear that the system heard
    what I tried to do when the screen was frozen, and thought it had
    changed things, because the screen now has the updates I thought I did. Things work fine, as log as I do not leave the machine alone and X
    unused for some time.
    <snip>
    I too have occasional problems with "desktop effects restarted"
    messages, clock freezing and icons on the bottom bar (I can never
    remember the name) going out of sync with the applications they
    represent .
    Environment Mageia 7/Plasma/nVidia/nVidia driver.
    Created bug 411858, but from the comments I'm not confident anything
    will be found

    --
    Grimble
    Registered Linux User #450547
    Machine 'Handel' running Plasma 5.15.4 on 5.7.19-desktop-1.mga7 kernel.
    Mageia release 7 (Official) for x86_64

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From William Unruh@2:250/1 to All on Thu Sep 17 17:12:06 2020
    n 2020-09-17, Melzzzzz <Melzzzzz@zzzzz.com> wrote:
    On 2020-09-17, William Unruh <unruh@invalid.ca> wrote:
    On 2020-09-16, faeychild <faeychild@nomail.afraid.org> wrote:
    On 17/9/20 6:14 am, William Unruh wrote:

    I have no idea what could be doing this. Looking in journalctl, the only >>>> thing that might be suspicious is powerdevil. Here are the lines from
    the output of journalctl from around the time when I came back and found >>>> it frozen.

    I encountered baffling erratic Plasma behavior after an update.

    I found (stumbled upon) that my nvidia driver had been replaced with
    nouveau.

    Unfortunately/fortunately I have Intel video.
    00:02.0 VGA compatible controller: Intel Corporation 8th Gen Core Processor Gaussian Mixture Model
    on a Canon Lake processor.


    My suspicion is that some sort of screen saver is coming in-- not
    actually doing anything to "screen save" but managing to switch off X
    without actually replacing it. Unfortunately all of the attempts to find
    what it is, and what program might be doing this have not succeeded yet.

    What DE are you using?
    KDE Plasma






    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Mike Easter@2:250/1 to All on Thu Sep 17 17:20:58 2020
    Grimble wrote:
    icons on the bottom bar (I can never remember the name)

    The generic name is taskbar, but various DEs like to create their own neologism such as gnome-panel or dock.

    wp has a nice article covering the history and the present https://en.wikipedia.org/wiki/Taskbar

    --
    Mike Easter

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1@fidonet)
  • From Paul@2:250/1 to All on Thu Sep 17 22:00:19 2020
    Grimble wrote:
    On 16/09/2020 21:14, William Unruh wrote:
    I am suddenly having a problem with my X. I am on Mga 7 with Plasma
    desktop. In the past couple of days my system has suddenly begun to
    misbehave. If I leave it for say 1/2 and hour, when I come back the X
    screen is frozen-- no updates, no dragging or typing or anything. If I
    do alt-ctrl-F2 to go to a terminal, and immediately do alt-ctrl-F1 to go
    back to X, everything works fine, and it is clear that the system heard
    what I tried to do when the screen was frozen, and thought it had
    changed things, because the screen now has the updates I thought I did.
    Things work fine, as log as I do not leave the machine alone and X
    unused for some time.
    <snip>
    I too have occasional problems with "desktop effects restarted"
    messages, clock freezing and icons on the bottom bar (I can never
    remember the name) going out of sync with the applications they represent . Environment Mageia 7/Plasma/nVidia/nVidia driver.
    Created bug 411858, but from the comments I'm not confident anything
    will be found


    Have you ever typed "dmesg" and had a look at the log ?

    It's not the only log on the machine, but occasionally
    you'll see some interesting stuff in there.

    For example, I can see Nouveau "losing contact" with my GTX1080.

    This is why my Test Machine has an RS232 serial port wired
    to it, and the cable runs to this machine. When funny stuff
    happens, I can use a console session running over RS232 to
    keep an eye on things. Even if the X11 screen freezes, I can talk
    to the machine. Now, there are other ways to do that, and that's
    just an example. The Test Machine has a ttyS0 on the surface
    of the motherboard, and to use it, I had to make up a custom
    cable (2x5 header) and run the cable through an I/O slot.

    You *can* do a ctrl-alt-F2, when it's working. But if that
    key combo elicits no response at all, the RS232 serial port
    is also an option. If Nouveau is on its lunch break, I don't
    really expect miracles to happen.

    Paul

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: A noiseless patient Spider (2:250/1@fidonet)
  • From Jasen Betts@2:250/1 to All on Fri Sep 18 06:23:26 2020
    On 2020-09-17, Paul <nospam@needed.invalid> wrote:
    Grimble wrote:
    On 16/09/2020 21:14, William Unruh wrote:
    I am suddenly having a problem with my X. I am on Mga 7 with Plasma
    desktop. In the past couple of days my system has suddenly begun to
    misbehave. If I leave it for say 1/2 and hour, when I come back the X
    screen is frozen-- no updates, no dragging or typing or anything. If I
    do alt-ctrl-F2 to go to a terminal, and immediately do alt-ctrl-F1 to go >>> back to X, everything works fine, and it is clear that the system heard
    what I tried to do when the screen was frozen, and thought it had
    changed things, because the screen now has the updates I thought I did.
    Things work fine, as log as I do not leave the machine alone and X
    unused for some time.
    <snip>
    I too have occasional problems with "desktop effects restarted"
    messages, clock freezing and icons on the bottom bar (I can never
    remember the name) going out of sync with the applications they represent . >> Environment Mageia 7/Plasma/nVidia/nVidia driver.
    Created bug 411858, but from the comments I'm not confident anything
    will be found


    Have you ever typed "dmesg" and had a look at the log ?

    It's not the only log on the machine, but occasionally
    you'll see some interesting stuff in there.

    For example, I can see Nouveau "losing contact" with my GTX1080.

    This is why my Test Machine has an RS232 serial port wired
    to it, and the cable runs to this machine. When funny stuff
    happens, I can use a console session running over RS232 to
    keep an eye on things. Even if the X11 screen freezes, I can talk
    to the machine. Now, there are other ways to do that, and that's
    just an example. The Test Machine has a ttyS0 on the surface
    of the motherboard, and to use it, I had to make up a custom
    cable (2x5 header) and run the cable through an I/O slot.

    You *can* do a ctrl-alt-F2, when it's working. But if that
    key combo elicits no response at all, the RS232 serial port
    is also an option. If Nouveau is on its lunch break, I don't
    really expect miracles to happen.

    I usually use ssh if I need a to get behind a wedged X session
    but when that doesn't work a serial console is a good fallback.

    In my day job I operate about 40 servers spread around the world
    they are all headless and maintained via ssh primarily, but there's
    also a serial console that can be reached via the BMC in-case I mess
    up the network settings, the OOM reaper kills sshd or some other
    mishap renders them unreachable.

    --
    Jasen.

    --- MBSE BBS v1.0.7.17 (GNU/Linux-x86_64)
    * Origin: JJ's own news server (2:250/1@fidonet)