FS#49575 - [systemd] Upgrading to systemd 230 is resulting in freezed plasma applications

Attached to Project: Arch Linux
Opened by Nils Naumann (naund) - Sunday, 05 June 2016, 18:49 GMT
Last edited by Dave Reisner (falconindy) - Monday, 06 June 2016, 22:23 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: Shortly after upgrading to systemd 230 the plasma desktop freeze. That means task bar and desktop are not responsive (e.g. clock is stopped) but kicker and most other applications are working without problems. But it is not possible to launch new terminal sessions.


Additional info:
* package version(s)
systemd 230-3, plasma-desktop 5.6.4-1
* config and/or log files etc.
there is no special information in the journal
* System: x86_64, Intel Core2 Duo T7700, Intel GM965/GL960 Graphics

Steps to reproduce:
starting the plasma desktop
upgrading systemd to 230-2, after some time the desktio is freezing.
downgrading to 229-3, desktop is responsive again, without restart!
This task depends upon

Closed by  Dave Reisner (falconindy)
Monday, 06 June 2016, 22:23 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#49581 
Comment by Dave Reisner (falconindy) - Sunday, 05 June 2016, 21:12 GMT
And after rebooting with systemd 230? Do you see any errors in the journal when this happens?
Comment by Nils Naumann (naund) - Monday, 06 June 2016, 18:30 GMT
I have reproduced the freezing several times. The time where the desktop is frreezing is correlating with automatic unmounting of an nfs4 network share with systemd automount:

Jun 06 20:18:41 Athene systemd[1]: Unmounting /mnt/Musik...
Jun 06 20:18:41 Athene baloo_file[1873]: org.kde.baloo: false "/org/kde/fstab/pi:/srv/nfs4/Musik"
Jun 06 20:18:41 Athene systemd[1]: Unmounted /mnt/Musik.

I have disabled baloo as well, no change, except the corresponding line in the logfile is missing.

Loading...