Plasma Desktop - Filesystem is not responding

DeathStar · 2020-04-25 01:31:50

Hello everyone,

I am currently running plasma 5.18.4 and have been running previous versions of plasma without issues but after I updated yesterday my log into Plasma takes a lot longer. It can take thirty seconds to a minute to login and when it finally does login, it displays this message in the corner:

Plasma Desktop Workspace
Filesystem is not responding
Filesystem mounted at "/" is not responding

I checked around online before coming here and I found that fstab might be an issue but it looks fine to me and the system totally works outside of a painfully slow login. This is a pure Arch x86_64 install following the official install guide with only a few AUR packages installed.

Thank your for your time and I appreciate any suggestions for this problem.

Last edited by DeathStar (2020-04-25 01:34:06)

jasonwryan · 2020-04-25 01:46:31

Read your journal.

DeathStar · 2020-04-25 02:31:40

jasonwryan wrote:

Read your journal.

Hi there,

Thank you for your input, I think I see what might be the problem, in my journal there is a line that says inotify_add_watch(/root) failed: (Permission denied). A quick google search reveals that that error is in fact fstab related so I booted into a livecd of Arch and recreated my fstab. However, that did not fix it and I am kind of running out of ideas.

Good idea though, I don't see anything else suspicious with my journal.

Last edited by DeathStar (2020-04-25 02:45:10)

jasonwryan · 2020-04-25 02:51:19

Paste the entire journal: https://wiki.archlinux.org/index.php/Li … in_clients

starcatman · 2020-04-25 03:09:43

I am also having this problem on two separate machines after updating. I updated my laptop first this morning and discovered this. After checking the disk and finding no problems, I backed up my system, and then tried a fresh install and have the same problem. I just updated one of my desktops to see if it was my laptop the desktop is now experiencing the same thing. So, ocams razor...some package was updated that is causing this problem.

Last edited by starcatman (2020-04-25 03:10:32)

DeathStar · 2020-04-25 03:17:17

jasonwryan wrote:

Paste the entire journal: https://wiki.archlinux.org/index.php/Li … in_clients

At the risk of sounding like a noob, how do I post my entire journal? Its over 150 MBs of data and well over a million lines of output.

starcatman wrote:

I am also having this problem on two separate machines after updating. I updated my laptop first this morning and discovered this. After checking the disk and finding no problems, I backed up my system, and then tried a fresh install and have the same problem. I just updated one of my desktops to see if it was my laptop the desktop is now experiencing the same thing. So, ocams razor...some package was updated that is causing this problem.

Well that confirms my suspicion that the update did it. That might be a good thing actually, usually when updates break things, they tend to fix themselves in future updates or at least that has been my experience with Arch Linux. The error is not too high of a priority to fix since its not system breaking but very annoying.

jasonwryan · 2020-04-25 03:20:20

Did you not read the link I posted? It explicitly describes how to do exactly that...

starcatman · 2020-04-25 03:43:43

jasonwryan wrote:

Did you not read the link I posted? It explicitly describes how to do exactly that...

Here is my journal from the desktop.

http://ix.io/2jrn

huyizheng · 2020-04-25 03:54:34

I also have this issue today. After checkout my pacman log and do some trying, I found out that downgrade every kde applications from 20.04.0 to 19.12.3 solves this issue.

I'm still trying to figure out which package(s) cause this issue.

DeathStar · 2020-04-25 04:00:58

jasonwryan wrote:

Did you not read the link I posted? It explicitly describes how to do exactly that...

My bad, I tried to use ix and it returns no url when I ran journalctl with it. I am on wireless so it might be a poor internet connection, I was able to upload a test/dummy output so I'll look at some of the other pastebin options and get back with this thread.

huyizheng · 2020-04-25 04:19:24

huyizheng wrote:

I also have this issue today. After checkout my pacman log and do some trying, I found out that downgrade every kde applications from 20.04.0 to 19.12.3 solves this issue.
I'm still trying to figure out which package(s) cause this issue.

After doing some more trying, I found that it seems caused by one or more telepathy-* package.

I downgrade all telepathy-* package to 19.12.3, while remains other kde applitions at 20.04.0, and this issue disappears.

DeathStar · 2020-04-25 04:52:27

huyizheng wrote:

huyizheng wrote:
I also have this issue today. After checkout my pacman log and do some trying, I found out that downgrade every kde applications from 20.04.0 to 19.12.3 solves this issue.
I'm still trying to figure out which package(s) cause this issue.
After doing some more trying, I found that it seems caused by one or more telepathy-* package.
I downgrade all telepathy-* package to 19.12.3, while remains other kde applitions at 20.04.0, and this issue disappears.

I can confirm that this works, if you don't have the older packages on your computer you can use the Arch Linux Archive.

I would mark this as solved but I guess this is only a work around at this point.

mcloaked · 2020-04-25 09:38:06

I have reported the issue of the long delay to login which was related to apparent bugs in the telepathy-kde package upstream at https://bugs.kde.org/show_bug.cgi?id=420549

I have also seen the issue concerning the Filesystem not responding, during plasma desktop login, but did not add anything about that to the report I linked to above. If the telepathy package downgrade also fixes the filesystem not responding issue could you add a comment to my upstream report? The filesystem not responding was intermittent for me, and happened perhaps once in every three logins before I downgraded the telepathy-kde packages. I haven't tried to login multiple times since then, so I don't know if that problem will also not occur with the workaround.

starcatman · 2020-04-25 15:12:16

mcloaked wrote:

I have reported the issue of the long delay to login which was related to apparent bugs in the telepathy-kde package upstream at https://bugs.kde.org/show_bug.cgi?id=420549
I have also seen the issue concerning the Filesystem not responding, during plasma desktop login, but did not add anything about that to the report I linked to above. If the telepathy package downgrade also fixes the filesystem not responding issue could you add a comment to my upstream report? The filesystem not responding was intermittent for me, and happened perhaps once in every three logins before I downgraded the telepathy-kde packages. I haven't tried to login multiple times since then, so I don't know if that problem will also not occur with the workaround.

Thanks for reporting this, much appreciated. I too have noticed the intermittency of the File System not responding message, and to your point, it maybe related to the login delay. The Filesystem not responding error only appears once every three or so logins.

PonJar · 2020-04-26 16:00:14

I have experienced the same issue along with an issue with timeshift which was broken by the same pacman -Syu update

https://bbs.archlinux.org/viewtopic.php?id=255013

Possibly related in some way.

petruknisme · 2020-04-28 05:57:10

I've experiencce the same issue plus krunner is freeze after launching alt + space.

△ ~ journalctl -b -1 | grep KdedIntegrationModule
Apr 27 14:45:32 localhost dbus-daemon[1358]: [session uid=1000 pid=1358] Activating service name='org.freedesktop.Telepathy.Client.KTp.KdedIntegrationModule' requested by ':1.16' (uid=1000 pid=1447 comm="/usr/lib/telepathy/mission-control-5 ")
Apr 27 14:47:32 localhost dbus-daemon[1358]: [session uid=1000 pid=1358] Failed to activate service 'org.freedesktop.Telepathy.Client.KTp.KdedIntegrationModule': timed out (service_start_timeout=120000ms)

Last edited by petruknisme (2020-04-28 06:04:23)

jonny88 · 2020-04-28 19:37:54

I can confirm that the downgrade of the telepathy-kde-* packages works. I had the same delay on login after the update of the kde packages to 20.04.0-1 and I also received the notification of "The filesystem not responding". Downgrading the telepathy-kde-* packages to 19.12.3-1 fixed both issues.

theodore · 2020-04-28 21:27:20

Same problem here as well, downgrading telepathy-kde-* packages resolved the issue. In my case except the delay on login and the notification of "The filesystem not responding" I've noticed high GPU usage from Kwin leading the fans in my laptop to get noisy.

PonJar · 2020-04-29 09:41:19

mcloaked wrote:

I have reported the issue of the long delay to login which was related to apparent bugs in the telepathy-kde package upstream at https://bugs.kde.org/show_bug.cgi?id=420549

There is an easy workaround to this issue among the comments to the bug post above.I can confirm it works for me.

$ cd /usr/lib/qt/plugins/kf5/kded/
$ sudo ln -sv ktp_integration.so ktp_integration_module.so

credit to Lex Onderwater

mcloaked · 2020-04-29 15:52:46

PonJar wrote:

mcloaked wrote:
I have reported the issue of the long delay to login which was related to apparent bugs in the telepathy-kde package upstream at https://bugs.kde.org/show_bug.cgi?id=420549
There is an easy workaround to this issue among the comments to the bug post above.I can confirm it works for me.
$ cd /usr/lib/qt/plugins/kf5/kded/
$ sudo ln -sv ktp_integration.so ktp_integration_module.so
credit to Lex Onderwater

This workaround resolves the issue for me also - perhaps it is merely a typo in the source code for ktp_integration.so that is the underlying cause? I have added a comment to the upstream bug too.

Edit: The issue is fixed in telepathy-kde-integration-module 20.04.0-2

Last edited by mcloaked (2020-04-30 19:10:48)

Arch Linux

#1 2020-04-25 01:31:50

Plasma Desktop - Filesystem is not responding

#2 2020-04-25 01:46:31

Re: Plasma Desktop - Filesystem is not responding

#3 2020-04-25 02:31:40

Re: Plasma Desktop - Filesystem is not responding

#4 2020-04-25 02:51:19

Re: Plasma Desktop - Filesystem is not responding

#5 2020-04-25 03:09:43

Re: Plasma Desktop - Filesystem is not responding

#6 2020-04-25 03:17:17

Re: Plasma Desktop - Filesystem is not responding

#7 2020-04-25 03:20:20

Re: Plasma Desktop - Filesystem is not responding

#8 2020-04-25 03:43:43

Re: Plasma Desktop - Filesystem is not responding

#9 2020-04-25 03:54:34

Re: Plasma Desktop - Filesystem is not responding

#10 2020-04-25 04:00:58

Re: Plasma Desktop - Filesystem is not responding

#11 2020-04-25 04:19:24

Re: Plasma Desktop - Filesystem is not responding

#12 2020-04-25 04:52:27

Re: Plasma Desktop - Filesystem is not responding

#13 2020-04-25 09:38:06

Re: Plasma Desktop - Filesystem is not responding

#14 2020-04-25 15:12:16

Re: Plasma Desktop - Filesystem is not responding

#15 2020-04-26 16:00:14

Re: Plasma Desktop - Filesystem is not responding

#16 2020-04-28 05:57:10

Re: Plasma Desktop - Filesystem is not responding

#17 2020-04-28 19:37:54

Re: Plasma Desktop - Filesystem is not responding

#18 2020-04-28 21:27:20

Re: Plasma Desktop - Filesystem is not responding

#19 2020-04-29 09:41:19

Re: Plasma Desktop - Filesystem is not responding

#20 2020-04-29 15:52:46

Re: Plasma Desktop - Filesystem is not responding

Board footer