Launchpad has imported 16 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=392145.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2018-03-21T19:12:56+00:00 Paul Worrall wrote:
Plasma 5.12.3 was working fine on Kubuntu 17.10 plus backports ppa
On upgrading to Kubuntu 18.04 beta, plasmashell crashes every login
leaving an empty black screen.
The only clues I can see are:
1. /home is an NFS share
2. .xsession-errors contains:
KActivities: Database can not be opened in WAL mode. Check the SQLite
version (required >3.7.0). And whether your filesystem supports shared
memory
followed by multiple reports of:
KActivities: FATAL ERROR: Failed to contact the activity manager daemon
Does NFS support shared memory?
If I unmount /home and use a local /home then all seems fine.
sqlite -version says 2.8.17
Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma-
workspace/+bug/1758402/comments/0
On 2018-03-27T17:38:33+00:00 Paul Worrall wrote:
paul@desktop:~/.local/share/kactivitymanagerd/resources$ sqlite3 database
SQLite version 3.22.0 2018-01-22 18:45:57
Enter ".help" for usage hints.
sqlite> pragma journal_mode;
Error: disk I/O error
sqlite> pragma journal_mode=wal;
Error: disk I/O error
sqlite>
Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma-
workspace/+bug/1758402/comments/5
On 2018-03-28T19:27:04+00:00 Paul Worrall wrote:
Comment 1 was on 18.04 beta.
With 17.10 + Plasma 5.12.3 and the same NFS mounted /home:
paul@paul-BB-64004H:~/.local/share/kactivitymanagerd/resources$ sqlite3 database
SQLite version 3.19.3 2017-06-08 14:26:16
Enter ".help" for usage hints.
sqlite> pragma journal_mode;
wal
sqlite>
which seems to show that sqlite has a problem with NFS on 18.04 (which
has a different sqlite version)
Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma-
workspace/+bug/1758402/comments/6
On 2018-03-28T21:33:13+00:00 Paul Worrall wrote:
As a work-around on 18.04: if I make the kactivitymanagerd/resources
directory a symlink to directory on the local (non-NFS) disk then plasma
does not crash.
Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma-
workspace/+bug/1758402/comments/7
On 2018-03-28T21:35:31+00:00 Rex Dieter wrote:
*** This bug has been marked as a duplicate of bug 387979 ***
Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma-
workspace/+bug/1758402/comments/8
On 2018-04-07T17:39:59+00:00 Paul Worrall wrote:
I do not think this is a duplicate of 387979:
1. If I mount the same NFS share as /home on a Kubuntu 17.10 machine
all is well, so the database isn't corrupt.
2. deleting ~/.local/share/kactivitymanagerd/ doesn't help like it did
for 387979
3. this bug is manifest only if ~/.local/share/kactivitymanagerd/ is on
an NFS mounted folder (see comment 3
Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma-
workspace/+bug/1758402/comments/9
On 2018-04-07T18:06:37+00:00 Rex Dieter wrote:
Strictly the fix is the same. A crashing kactivitiesmanagerd will no
longer crash plasmashell.
Remaining issue: kactivitiesmanagerd is still (sometimes?) crashing (or
otherwise failing to start properly) when db is storged on nfs :(
Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma-
workspace/+bug/1758402/comments/10
On 2018-04-23T17:31:02+00:00 Tibbs wrote:
I just wanted to add that it may be related to NFS, but there is also
something else involved which I don't yet understand.
Basically, I have a couple of hundred users all of which have ~ on NFS
and this problem occurs for only three of them. I do not know what is
special about those three, nor have I figured out what I can delete to
get things to go back to normal. The three users don't even have their
homes on the same NFS server, and other users are fine even when they
share the same NFS server or even the same volume on that server. All
of the client machines have the same software: Fedora 27 with all
applied updates, which includes sqlite 3.20.1 and framesworks 5.44.0 and
plasma 5.12.4.
Reply at: https://bugs.launchpad.net/ubuntu/+source/plasma-
workspace/+bug/1758402/comments/11
On 2018-04-23T17:57:33+00:00 Paul Worrall wrote:
@Jaso
