• Restarting plasma or GDM or X from tty terminal?


    First of, I use KDE as a DE. My video card is an NVIDIA one running the proprietary drivers. System is up to date.

    Quite frequently, when the machine is under heavy load Plasma kind of freezes. Mouse movement is not possible or extremely(!) laggy and it doesn’t recover. Videos however continue to run, it’s just that the screen is frozen but the voice continues.
    What I can do is Ctrl+Alt+F3/F4/etc. into a tty terminal. F1 brings me to the GDM login prompt but I can’t click anything there, just no effect as if it was just a wallpaper. F2 is the crashed Plasma Desktop.

    I’d like to restart what ever has crashed there but nothing really works, so I always end up using ‘reboot’ which ungracefully kills all the running processes such as open spreadsheets, running VM etc.
    If I use ‘ps’ in such a tty window it doesn’t show the processes of tty2.

    So, the million dollar question is, how do I access tty2 from a different tty console and what do I have to kill and restart? Is it X or GDM or plasmashell?

    This problem is bugging me really hard. :/

  • may this:

    kquitapp5 plasmashell && kstart plasmashell
    

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • @joekamprad

    I switched to tty3 to test this. The plasmashell on tty2 was running just fine when I tried this.
    The commands returned:

    kstart: cannot connect to X server
    

    When I switched back to tty2 the background was black and the bars were gone.
    It is as if I have no access to the plasma session when I switch to a different tty.

  • I read that if it is only the plasmashell that crashes you can still use latte-dock, or you can create a keyboard shortcut for executing the command plasmashell

    whati give you before is not working because of TTY terminals are not working here…

    https://forum.antergos.com/topic/7391/kde-desktop-environment-crashing-log-files/8?page=2

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • I have latte-dock installed but currently only use docky. What advantage would it have if latte-dock were still working? What should I do then?

    Regarding the shortcut I 'll try to do this.

    Edit: Just realized you posted a link as well. I’ll see if latte dock helps and if the shortcuts work. Thanks for your help so far. I’ll get back to you if something changes.

  • I’m sorry to bother you yet again but I’m having trouble with the shortcuts. Here are pictures of how I have configured it but when performing the shortcut nothing happens. Auslöser= trigger
    0_1509111209245_Screenshot_20171027_153052.png
    0_1509111299929_Screenshot_20171027_153146.png

  • i’m german so no problem reading here ;)

    as @Jeannie____ say in the thread i post the link is only the command plasmashell
    is needed…

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • I can confirm that such more or less complete freezes of the plasmashell (with sound or even videos continuing to play and the mouse cursor still being responsive) have begun to occur here too. This started earlier this week, not sure if it’s related to the plasma upgrades that came in. The only way to recover my machine in such cases is to pull the power plug.
    CPU: Intel i7/7700
    GPU: Nvidia GTX 1060
    Nvidia 387.12 proprietary driver.
    J.

  • so complete freeze, with no way to recover… that’s another thing then…
    If you have another linux machine you can try to enable ssh service and login via ssh from remote, also possible with android and such app like juicessh then you will be able to do a sudo systemctl rebootor sudo systemctl restart gdm/lightdm/sddmget a watch to the journal or dmesg, is also possible after reboot with the right command:

    journalctl --since "20 minutes ago"
    

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • No second linux device here, and my life is android (and smartphone) free.
    J.

  • @Jeannie____ said in Restarting plasma or GDM or X from tty terminal?:

    …my life is android (and smartphone) free.
    J.

    I know @Jeannie____ ;)
    0_1509187228982_Screenshot_2017-10-28-12-37-44.png

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • journalctl -f gives no usable information imho:

    – Logs begin at Sat 2017-08-12 16:27:28 CEST. –
    Okt 28 12:36:36 p707 plasmashell[681]: Currrent active notifications: QHash()
    Okt 28 12:36:36 p707 plasmashell[681]: Guessing partOf as: 0
    Okt 28 12:39:06 p707 plasmashell[681]: Currrent active notifications: QHash()
    Okt 28 12:39:06 p707 plasmashell[681]: Guessing partOf as: 0
    Okt 28 12:39:06 p707 plasmashell[681]: New Notification: "[email protected]" “[Antergos Community Forum] Restarting plasma or GDM or X from tty terminal?” -1 & Part of: 0
    Okt 28 12:39:25 p707 kwin_x11[673]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 55090, resource id: 60817415, major code: 18 (ChangeProperty), minor code: 0
    Okt 28 12:39:26 p707 plasmashell[681]: QObject::startTimer: Timers cannot be started from another thread
    Okt 28 12:39:37 p707 kwin_x11[673]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 57934, resource id: 60817408, major code: 18 (ChangeProperty), minor code: 0
    Okt 28 12:39:37 p707 kwin_x11[673]: QXcbConnection: XCB error: 3 (BadWindow), sequence: 57938, resource id: 60817409, major code: 18 (ChangeProperty), minor code: 0

    J.

  • @Jeannie____ maybe it is not plasmashell crashing, may it is caused by nvidia-driver issue…
    @DOS-6-1 you are on nvidia also?

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • @joekamprad

    Yep, NVIDIA here, and it seems that NVIDIA drivers are ALWAYS the culprit. ;)
    I think the freeze happened quite a few times when watching a movie using SMplayer and watching it from the rar files directly. It is not limited to that though.

    I also already have juice ssh on my Droid but ssh is not activated on my desktop. I can still reboot in the tty terminal so that SSH wouldn’t help me much. I want to avoid that the running VM gets killed by the reboot every time. One day it will break I fear.

    I need to find useful logfiles but so far nothing pointed to an error. I’ll try this journalctl next time.

    @Jeannie____
    I’m kind of glad to read that your shortcut doesn’t work anymore because it does nothing for me as well. :/

  • If it’s really caused by the combination plasma/nvdidia proprietary, I am kind of f*cked, as I detest all GTK3 DEs.
    Then I fear it’s time for me to switch to a different operating system.
    J.

  • i get the same freeze also under GNOME also nvidia drivers, i try all the extra options for nvidia aviable, like persistence service and early boot… so i do not think it is related to DE while i am reading here that plasma is also effected to the same… but there is a new nvidia version comming soon (already use it under win10)
    And i have 3 other machines running Antergos on INTEL graphics and older nvidia card without any issues like this…

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • mesa is updated today! and it have a strong relation to nvidia ;)
    https://www.mesa3d.org/relnotes/17.2.3.html

    [updates once a week] = [90% less problems]
    [Li{u}n//u//{i}x] since 1988 - overcoming failure means success
    howto-install-antergos
    how to add system logs
    i3 GNOME

  • Okt 28 22:10:17 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: INFO:caffeine.core:Process smplayer detected. No change.
    Okt 28 22:10:27 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: INFO:caffeine.core:Process smplayer detected. No change.
    Okt 28 22:10:28 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 1638400/1654784/16384, res+swap = 1978368/1982464/4096
    Okt 28 22:10:33 antergos-GNOME plasmashell[3875]: Currrent active notifications: QHash()
    Okt 28 22:10:33 antergos-GNOME plasmashell[3875]: Guessing partOf as: 0
    Okt 28 22:10:33 antergos-GNOME plasmashell[3875]:  New Notification:  "Telegram" "DAO/TAO The Movement - Unstoppable Organization (3 neue Nachrichten) ‐ Drokzid hat "https://medium.com/@..." in der Gru
    Okt 28 22:10:33 antergos-GNOME plasmashell[3875]: error activating kdeconnectd: QDBusError("", "")
    Okt 28 22:10:34 antergos-GNOME plasmashell[3875]: Currrent active notifications: QHash(("notification 290", "KDE-ConnectTelegram"))
    Okt 28 22:10:34 antergos-GNOME plasmashell[3875]: Guessing partOf as: 290
    Okt 28 22:10:34 antergos-GNOME plasmashell[3875]:  New Notification:  "Telegram" "DAO/TAO The Movement - Unstoppable Organization ‐ Drokzid hat "https://medium.com/@..." in der Gruppe DAO/TAO The Movem
    Okt 28 22:10:34 antergos-GNOME plasmashell[3875]: error activating kdeconnectd: QDBusError("", "")
    Okt 28 22:10:35 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: TCP connection done (i'm the existing device)
    Okt 28 22:10:35 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: Starting server ssl (I'm the client TCP socket)
    Okt 28 22:10:35 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: Socket succesfully stablished an SSL connection
    Okt 28 22:10:35 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: It is a known device "htc"
    Okt 28 22:10:35 antergos-GNOME plasmashell[3875]: Currrent active notifications: QHash(("notification 290", "KDE-ConnectTelegram"))
    Okt 28 22:10:35 antergos-GNOME plasmashell[3875]: Guessing partOf as: 0
    Okt 28 22:10:35 antergos-GNOME plasmashell[3875]:  New Notification:  "Drokzid @ DAO/TAO The Movement - Unstoppable Organization" "hat Nachricht angeheftet" -1 & Part of: 0
    Okt 28 22:10:37 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: INFO:caffeine.core:Process smplayer detected. No change.
    Okt 28 22:10:47 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: INFO:caffeine.core:Process smplayer detected. No change.
    Okt 28 22:10:59 antergos-GNOME dockerd[469]: time="2017-10-28T22:10:58.720832096+02:00" level=error msg="libcontainerd: failed to receive event from containerd: rpc error: code = Internal desc = transport is clo
    Okt 28 22:11:01 antergos-GNOME dockerd[469]: time="2017-10-28T22:10:59.817493323+02:00" level=info msg="libcontainerd: new containerd process, pid: 1169"
    Okt 28 22:11:02 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 1658880/1662976/4096, res+swap = 1986560/1990656/4096
    Okt 28 22:11:03 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: (II) event0  - (II) Logitech M705: (II) SYN_DROPPED event - some input events have been lost.
    Okt 28 22:11:10 antergos-GNOME dockerd[469]: time="2017-10-28T22:11:10.575174118+02:00" level=info msg="libcontainerd: new containerd process, pid: 1174"
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c: snd_pcm_avail() gibt einen Wert zurück, der außerordentlich groß ist: 331524 bytes (626 ms).
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c: Dies ist wahrscheinlich ein Fehler im ALSA-Treiber »snd_ctxfi«. Bitte melden Sie dieses Problem den ALSA-Entwicklern.
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c: snd_pcm_dump():
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c: Hardware PCM card 0 'Creative X-Fi' device 0 subdevice 0
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c: Its setup is:
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   stream       : PLAYBACK
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   access       : MMAP_INTERLEAVED
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   format       : S16_LE
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   subformat    : STD
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   channels     : 6
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   rate         : 44100
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   exact rate   : 44100 (44100/1)
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   msbits       : 16
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   buffer_size  : 4408
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   period_size  : 1102
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   period_time  : 24988
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   tstamp_mode  : ENABLE
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   tstamp_type  : MONOTONIC
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   period_step  : 1
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   avail_min    : 1102
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   period_event : 1
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   start_threshold  : -1
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   stop_threshold   : 4962966789362286592
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   silence_threshold: 0
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   silence_size : 0
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   boundary     : 4962966789362286592
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   appl_ptr     : 2759371
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   hw_ptr       : 2800185
    Okt 28 22:11:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c: snd_pcm_delay() gibt einen Wert zurück, der außerordentlich groß ist: -309552 Bytes (-584 ms).
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c: Dies ist wahrscheinlich ein Fehler im ALSA-Treiber »snd_ctxfi«. Bitte melden Sie dieses Problem den ALSA-Entwicklern.
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c: snd_pcm_dump():
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c: Hardware PCM card 0 'Creative X-Fi' device 0 subdevice 0
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c: Its setup is:
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   stream       : PLAYBACK
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   access       : MMAP_INTERLEAVED
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   format       : S16_LE
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   subformat    : STD
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   channels     : 6
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   rate         : 44100
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   exact rate   : 44100 (44100/1)
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   msbits       : 16
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   buffer_size  : 4408
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   period_size  : 1102
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   period_time  : 24988
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   tstamp_mode  : ENABLE
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   tstamp_type  : MONOTONIC
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   period_step  : 1
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   avail_min    : 1102
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   period_event : 1
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   start_threshold  : -1
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   stop_threshold   : 4962966789362286592
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   silence_threshold: 0
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   silence_size : 0
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   boundary     : 4962966789362286592
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   appl_ptr     : 2790227
    Okt 28 22:12:13 antergos-GNOME pulseaudio[3887]: E: [alsa-sink-ctxfi] alsa-util.c:   hw_ptr       : 2829939
    Okt 28 22:11:52 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: TCP connection done (i'm the existing device)
    Okt 28 22:13:31 antergos-GNOME dockerd[469]: time="2017-10-28T22:11:27.967818742+02:00" level=info msg="libcontainerd: new containerd process, pid: 1179"
    Okt 28 22:13:31 antergos-GNOME dockerd[469]: time="2017-10-28T22:11:47.675349901+02:00" level=info msg="libcontainerd: new containerd process, pid: 1184"
    Okt 28 22:13:31 antergos-GNOME dockerd[469]: time="2017-10-28T22:12:06.411957832+02:00" level=info msg="libcontainerd: new containerd process, pid: 1190"
    Okt 28 22:13:31 antergos-GNOME dockerd[469]: time="2017-10-28T22:12:21.033281343+02:00" level=info msg="libcontainerd: new containerd process, pid: 1195"
    Okt 28 22:13:31 antergos-GNOME dockerd[469]: time="2017-10-28T22:12:39.628188847+02:00" level=info msg="libcontainerd: new containerd process, pid: 1200"
    Okt 28 22:13:31 antergos-GNOME dockerd[469]: time="2017-10-28T22:13:02.585784668+02:00" level=info msg="libcontainerd: new containerd process, pid: 1203"
    Okt 28 22:13:55 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 1703936/1708032/4096, res+swap = 1994752/1998848/4096
    Okt 28 22:13:55 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 1712128/1716224/4096, res+swap = 2002944/2007040/4096
    Okt 28 22:12:27 antergos-GNOME dbus[443]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service'
    Okt 28 22:11:57 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: Starting server ssl (I'm the client TCP socket)
    Okt 28 22:14:13 antergos-GNOME dockerd[469]: time="2017-10-28T22:13:38.693074602+02:00" level=info msg="libcontainerd: new containerd process, pid: 1206"
    Okt 28 22:14:13 antergos-GNOME dockerd[469]: time="2017-10-28T22:14:07.084506547+02:00" level=info msg="libcontainerd: new containerd process, pid: 1207"
    Okt 28 22:14:19 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: (II) event0  - (II) Logitech M705: (II) SYN_DROPPED event - some input events have been lost.
    Okt 28 22:14:06 antergos-GNOME dbus[443]: [system] Failed to activate service 'org.freedesktop.nm_dispatcher': timed out
    Okt 28 22:12:10 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: Socket succesfully stablished an SSL connection
    Okt 28 22:14:43 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2027520/2027520/0, res+swap = 2281472/2285568/4096
    Okt 28 22:14:43 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2031616/2035712/4096, res+swap = 2285568/2289664/4096
    Okt 28 22:14:43 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2265088/2269184/4096, res+swap = 2461696/2465792/4096
    Okt 28 22:14:43 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2306048/2318336/12288, res+swap = 2498560/2510848/12288
    Okt 28 22:15:00 antergos-GNOME dockerd[469]: time="2017-10-28T22:14:32.878839749+02:00" level=info msg="libcontainerd: new containerd process, pid: 1208"
    Okt 28 22:15:00 antergos-GNOME dockerd[469]: time="2017-10-28T22:14:56.272048590+02:00" level=info msg="libcontainerd: new containerd process, pid: 1209"
    Okt 28 22:14:21 antergos-GNOME dbus[443]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit NetworkManager-dispatcher.service is not loaded properly: Connection t
    Okt 28 22:14:21 antergos-GNOME dbus[443]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Unit NetworkManager-dispatcher.service is not loaded properly: Connection t
    Okt 28 22:12:13 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: It is a known device "htc"
    Okt 28 22:15:19 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2318336/2322432/4096, res+swap = 2510848/2514944/4096
    Okt 28 22:12:18 antergos-GNOME NetworkManager[451]: <info>  [1509221538.6286] connectivity: (enp0s25) timed out
    Okt 28 22:15:27 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2322432/2326528/4096, res+swap = 2514944/2519040/4096
    Okt 28 22:12:57 antergos-GNOME systemd[1]: Failed to subscribe to NameOwnerChanged signal for 'org.freedesktop.nm_dispatcher': Connection timed out
    Okt 28 22:15:33 antergos-GNOME dockerd[469]: time="2017-10-28T22:15:28.251283862+02:00" level=info msg="libcontainerd: new containerd process, pid: 1211"
    Okt 28 22:12:58 antergos-GNOME systemd[1]: NetworkManager-dispatcher.service: Cannot watch bus name org.freedesktop.nm_dispatcher: Connection timed out
    Okt 28 22:13:35 antergos-GNOME kdeinit5[3922]: kf5.kio.core: couldn't create slave: "Keine Verbindung zu klauncher: Did not receive a reply. Possible causes include: the remote application did not send a reply, 
    Okt 28 22:15:53 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2334720/2338816/4096, res+swap = 2527232/2531328/4096
    Okt 28 22:15:59 antergos-GNOME dockerd[469]: time="2017-10-28T22:15:55.037886708+02:00" level=info msg="libcontainerd: new containerd process, pid: 1212"
    Okt 28 22:16:26 antergos-GNOME dockerd[469]: time="2017-10-28T22:16:23.579479396+02:00" level=info msg="libcontainerd: new containerd process, pid: 1215"
    Okt 28 22:16:30 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2338816/2347008/8192, res+swap = 2531328/2539520/8192
    Okt 28 22:16:43 antergos-GNOME dbus[443]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 53444ms)
    Okt 28 22:16:47 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: (II) event0  - (II) Logitech M705: (II) SYN_DROPPED event - some input events have been lost.
    Okt 28 22:16:52 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: (II) event1  - (II) HID Keyboard Device: (II) SYN_DROPPED event - some input events have been lost.
    Okt 28 22:16:56 antergos-GNOME dockerd[469]: time="2017-10-28T22:16:50.483740863+02:00" level=info msg="libcontainerd: new containerd process, pid: 1216"
    Okt 28 22:17:00 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2347008/2351104/4096, res+swap = 2539520/2543616/4096
    Okt 28 22:17:20 antergos-GNOME dockerd[469]: time="2017-10-28T22:17:19.835808592+02:00" level=info msg="libcontainerd: new containerd process, pid: 1219"
    Okt 28 22:17:21 antergos-GNOME NetworkManager[451]: <info>  [1509221840.8785] connectivity: (enp0s25) timed out
    Okt 28 22:17:32 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2355200/2359296/4096, res+swap = 2547712/2551808/4096
    Okt 28 22:17:51 antergos-GNOME dockerd[469]: time="2017-10-28T22:17:48.942716974+02:00" level=info msg="libcontainerd: new containerd process, pid: 1221"
    Okt 28 22:17:58 antergos-GNOME dbus[443]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 34425ms)
    Okt 28 22:18:05 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: TCP connection done (i'm the existing device)
    Okt 28 22:18:16 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: Starting server ssl (I'm the client TCP socket)
    Okt 28 22:18:25 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2445312/2449408/4096, res+swap = 2633728/2637824/4096
    Okt 28 22:18:32 antergos-GNOME dockerd[469]: time="2017-10-28T22:18:27.615123716+02:00" level=info msg="libcontainerd: new containerd process, pid: 1223"
    Okt 28 22:19:20 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: (II) event0  - (II) Logitech M705: (II) SYN_DROPPED event - some input events have been lost.
    Okt 28 22:19:32 antergos-GNOME dockerd[469]: time="2017-10-28T22:19:29.570896405+02:00" level=info msg="libcontainerd: new containerd process, pid: 1225"
    Okt 28 22:19:40 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: Socket succesfully stablished an SSL connection
    Okt 28 22:19:49 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2449408/2453504/4096, res+swap = 2637824/2641920/4096
    Okt 28 22:19:52 antergos-GNOME kdeconnectd[3873]: kdeconnect.core: It is a known device "htc"
    Okt 28 22:20:12 antergos-GNOME dockerd[469]: time="2017-10-28T22:20:10.970945981+02:00" level=info msg="libcontainerd: new containerd process, pid: 1226"
    Okt 28 22:20:20 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2457600/2461696/4096, res+swap = 2646016/2650112/4096
    Okt 28 22:20:25 antergos-GNOME dbus[443]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 121243ms)
    Okt 28 22:20:26 antergos-GNOME dbus[443]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 111395ms)
    Okt 28 22:20:44 antergos-GNOME kdeconnectd[3873]: kdeconnect.plugin.notification: Not found noti by internal Id:  "-1|android|17040412|null|1000"
    Okt 28 22:20:53 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2461696/2465792/4096, res+swap = 2650112/2654208/4096
    Okt 28 22:20:59 antergos-GNOME dockerd[469]: time="2017-10-28T22:20:51.581654118+02:00" level=info msg="libcontainerd: new containerd process, pid: 1228"
    Okt 28 22:21:08 antergos-GNOME kdeconnectd[3873]: kdeconnect.plugin.notification: Not found noti by internal Id:  "-1|android|17040412|null|1000"
    Okt 28 22:21:11 antergos-GNOME dbus[443]: [system] Connection has not authenticated soon enough, closing it (auth_timeout=30000ms, elapsed: 30861ms)
    Okt 28 22:21:20 antergos-GNOME kdeconnectd[3873]: kdeconnect.plugin.notification: Not found noti by internal Id:  "-1|android|17040412|null|1000"
    Okt 28 22:21:29 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: Memory pressure relief: Total: res = 2465792/2469888/4096, res+swap = 2654208/2658304/4096
    Okt 28 22:21:34 antergos-GNOME dockerd[469]: time="2017-10-28T22:21:28.279302522+02:00" level=info msg="libcontainerd: new containerd process, pid: 1229"
    Okt 28 22:21:36 antergos-GNOME kdeconnectd[3873]: kdeconnect.plugin.notification: Not found noti by internal Id:  "-1|android|17040412|null|1000"
    Okt 28 22:22:02 antergos-GNOME /usr/lib/gdm/gdm-x-session[3776]: (II) event0  - (II) Logitech M705: (II) SYN_DROPPED event - some input events have been lost.
    -- Reboot --
    
    

    I succesfully managed to crash the PC again in order to provide you with the logs. ;)
    The taskbar froze when the clock showed 22:10 so I copy/pasted the log from there. The event triggering the freeze was starting Opera browser which usually takes 2 GB RAM when it starts.
    As you can see the RAM was pretty much maxed out due to a VM, 2 browsers running and watching a movie.
    I think I’ll have to set up SSH for the desktop and then try to kill processes one after the other and see if it helps. I could kill Firefox and then Opera. That would free half of the RAM but I expect ssh to be unresponsive as well.

Posts 18Views 318
Log in to reply