Desktop environment (KDE, LXQT…):
Any but mostly KDE/Plasma5
Description of the issue (screenshots if relevant):
I experience occaisonal crashes or freezes. Sometimes the KDE menu panel goes blank and I simply need to logout/login. Other times when I leave computer unattended like overnight and come back I have no display and no access to kbd and mouse so have to restart computer with restart button. (That isn’t good.)
Relevant informations (hardware involved, software version, logs or output…):
What I most commonly see right before the “computer unattended freeze” in journal is red lines about nmb.service and smb.service. These are related to Samba which I don’t use as there is no Windows partition on this computer.
So I’m going to try disabling these services and see if that helps, but it will take time to find out.
$ systemctl status smb.service
● smb.service - Samba SMB Daemon
Loaded: loaded (/lib/systemd/system/smb.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2018-04-14 15:08:12 CDT; 1min 34s ago
Main PID: 7104 (smbd)
Status: "smbd: ready to serve connections..."
Tasks: 4 (limit: 4915)
Memory: 7.2M
CGroup: /system.slice/smb.service
├─7104 /usr/sbin/smbd --foreground --no-process-group
├─7106 /usr/sbin/smbd --foreground --no-process-group
├─7107 /usr/sbin/smbd --foreground --no-process-group
└─7108 /usr/sbin/smbd --foreground --no-process-group
Apr 14 15:08:12 ben79-pc smbd[7104]: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Apr 14 15:08:12 ben79-pc smbd[7104]: [2018/04/14 15:08:12.645566, 0] ../lib/util/debug.c:1053(reopen_logs_internal)
Apr 14 15:08:12 ben79-pc smbd[7104]: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Apr 14 15:08:12 ben79-pc smbd[7104]: [2018/04/14 15:08:12.645593, 0] ../lib/util/debug.c:1053(reopen_logs_internal)
Apr 14 15:08:12 ben79-pc smbd[7104]: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
Apr 14 15:08:12 ben79-pc smbd[7104]: [2018/04/14 15:08:12.652275, 0] ../lib/util/become_daemon.c:124(daemon_ready)
Apr 14 15:08:12 ben79-pc smbd[7104]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
Apr 14 15:08:12 ben79-pc systemd[1]: Started Samba SMB Daemon.
Apr 14 15:08:12 ben79-pc smbd[7108]: [2018/04/14 15:08:12.653440, 0] ../lib/util/debug.c:1053(reopen_logs_internal)
Apr 14 15:08:12 ben79-pc smbd[7108]: Unable to open new log file '/usr/local/samba/var/log.smbd': No such file or directory
$ systemctl status nmb.service
● nmb.service - Samba NMB Daemon
Loaded: loaded (/lib/systemd/system/nmb.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2018-04-14 15:08:22 CDT; 19min ago
Main PID: 7114 (nmbd)
Status: "nmbd: ready to serve connections..."
Tasks: 1 (limit: 4915)
Memory: 2.7M
CGroup: /system.slice/nmb.service
└─7114 /usr/sbin/nmbd --foreground --no-process-group
Apr 14 15:08:24 ben79-pc nmbd[7114]: standard_fail_register: Failed to register/refresh name BEN79-PC<00> on subnet 192.168.0.101
Apr 14 15:13:37 ben79-pc nmbd[7114]: [2018/04/14 15:13:37.296203, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Apr 14 15:13:37 ben79-pc nmbd[7114]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.101 for name MYGROUP<1d>.
Apr 14 15:13:37 ben79-pc nmbd[7114]: This response was from IP 192.168.0.104, reporting an IP address of 192.168.0.104.
Apr 14 15:18:39 ben79-pc nmbd[7114]: [2018/04/14 15:18:39.618523, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Apr 14 15:18:39 ben79-pc nmbd[7114]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.101 for name MYGROUP<1d>.
Apr 14 15:18:39 ben79-pc nmbd[7114]: This response was from IP 192.168.0.104, reporting an IP address of 192.168.0.104.
Apr 14 15:23:43 ben79-pc nmbd[7114]: [2018/04/14 15:23:43.012725, 0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
Apr 14 15:23:43 ben79-pc nmbd[7114]: query_name_response: Multiple (2) responses received for a query on subnet 192.168.0.101 for name MYGROUP<1d>.
Apr 14 15:23:43 ben79-pc nmbd[7114]: This response was from IP 192.168.0.104, reporting an IP address of 192.168.0.104.
The posted lines are typical of the continual red lines I get in journal about these 2 services.
Now I reboot and maybe in 3 to 7 days I’ll be able to see some results one way or the other.
Edit: This is speculation on my part at this time whether these have anything to do with the issue but I thought to post in case anyone else with crashes or freezes wants to try this.
And perhaps there are other unused services being enabled by default in OM Lx 3 that contribute to these crashes/freezes. If anyone has any ideas on this I would like to hear it.
My first question was why is this stuff enabled by default on OM systems. @Colin says it is because OM has always come with Samba stuff enabled by default. There are developers that think this is not a good idea. How many users actually use Samba? I don’t use it even on computers with Windows.
As far as why “it” is looking in /usr/local I don’t know.
Samba is widely used in mixed networks. I guess it is used to share folder between computers. For example Dolphin has the ability to reach shared remote folder without any particular configuration and this may be appreciated by people operating with mixed environment.
As far as I have ever heard it is used to share stuff between a Linux system and a Windows system. It can be used in other ways but I’ve never heard of anyone doing so.
More to the point. What I’m trying to get to is why after all this time do we have users including me that report freezes and crashes in Plama5 desktop. My thought is that in OM we are enabling a lot of unused services in a effort to make a system that works our of the box for most all users.
So in that vein I have started with 2 services that:
They go together, both are from package samba-server
They are not needed or used on my computers
They are what creates the most red lines in journal logs on both of my computers
Edit: And it is ironic that developers are working on Lx4 while we still have problems with freezes/crashes in Lx3.
Edit2: Which leads me to wonder if these will ever be resolved in Lx3…
Update on this. The above seems to have eliminated the shut downs I would get if I leave computer on over night. It has not done anything that I can tell to stop the occasional menu panel crash.
Edit: Or maybe it has helped with menu panel crash.
