Bug 25670 - dolphin kwrite and okular hang
Summary: dolphin kwrite and okular hang
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-11-08 18:45 CET by papoteur
Modified: 2020-01-06 15:15 CET (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Strace of Okular trying to open a document (end) (11.54 KB, text/plain)
2019-11-08 18:56 CET, papoteur
Details
Strace of Dolphin when launching (11.54 KB, text/plain)
2019-11-08 18:57 CET, papoteur
Details
freezes with simple search in kwrite (84.10 KB, image/png)
2019-12-09 20:54 CET, roger herz-fischler
Details
just switching desktops (78.78 KB, image/png)
2019-12-09 20:55 CET, roger herz-fischler
Details
just pluggin in a USB stick (76.65 KB, image/png)
2019-12-09 20:56 CET, roger herz-fischler
Details
seafile_01.png (32.95 KB, image/png)
2020-01-06 15:12 CET, roger herz-fischler
Details
seafile02 (9.70 KB, image/png)
2020-01-06 15:15 CET, roger herz-fischler
Details

Description papoteur 2019-11-08 18:45:13 CET
Description of problem:
Since this afternoon, dolphin doesn't appears after launching. Okular is stuck when a file is opening.
With strace I get similar errors, the applications are closed in loop, with repeatedly:

write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffff45d4440) = 0
select(20, [19], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)

This occurs for now at each time I try to launch dolphin or open a file with okular.
I will try to reboot after that.
Comment 1 papoteur 2019-11-08 18:56:21 CET
Created attachment 11344 [details]
Strace of Okular trying to open a document (end)
Comment 2 papoteur 2019-11-08 18:57:29 CET
Created attachment 11345 [details]
Strace of Dolphin when launching

Dolphin's window didn't appear.
Comment 3 papoteur 2019-11-08 19:00:39 CET
Kwrite has the same behaviour
Comment 4 papoteur 2019-11-08 19:16:53 CET
The applications are fine after a reboot.
Some days ago, I switched from Plasma to LXQt, because of the same behaviour seemed to affect plasmashell and the session was becoming unusable.
Now, at least the desktop survives to such problems.
Comment 5 Lewis Smith 2019-11-08 19:40:38 CET
(In reply to papoteur from comment #4)
> The applications are fine after a reboot.
If they remain OK, can you please close this bug - perhaps 'worksforme'.

CC: (none) => lewyssmith

Comment 6 papoteur 2019-11-09 08:21:16 CET
Hi Lewis,
No, I don't to close it for the moment, because I suspect that this bad behaviour will come back later.
Rebooting a few times each day is not a good situation.
Comment 7 Lewis Smith 2019-11-10 21:38:19 CET
(In reply to papoteur from comment #6)
> Rebooting a few times each day is not a good situation.
This would of course be unacceptable.

> No, I don't to close it for the moment, because I suspect that this bad
> behaviour will come back later.
If the problem recurs, then we can assign the bug.
If it does not recur in the short term, please do close the bug; it can always be re-opened subsequently.
papoteur 2019-11-18 16:31:25 CET

Summary: dolphin and okular hang => dolphin kwrite and okular hang

Comment 8 papoteur 2019-11-18 16:37:28 CET
Hello,
Today, I got a hang of kwrite. I could kill it.
I relaunched it from console with strace.
After a moment without activity, I see that the console went with same kind of log, when the application was unresponsive, even from the closing cross.
here is a part of logs which are repeated without end:

...
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
write(5, "\1\0\0\0\0\0\0\0", 8)         = 8
nanosleep({tv_sec=0, tv_nsec=50000000}, 0x7ffd8ef0f950) = 0
select(19, [18], NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
...

At this time, okular and dolphin are working fine.
Comment 9 Lewis Smith 2019-11-20 10:07:16 CET
So the fault is arbitrary, but Plasma related. Thank you for the log information.
Assigning to the Plasma team.

Assignee: bugsquad => kde
CC: lewyssmith => (none)

Comment 10 papoteur 2019-11-23 13:44:01 CET
Note that some time, when killing the unresponsive application, the whole desktop freezes.
This occurs each day.

Severity: normal => major

Comment 11 papoteur 2019-11-23 13:45:03 CET
Konversation is affected too.
Comment 12 roger herz-fischler 2019-12-09 20:54:03 CET
Created attachment 11396 [details]
freezes with simple search in kwrite

It is almost certain that the problem  is with the  version of plasma in MAGEIA 7. I am attaching a few screen shots, but I have many more.  At first I thought it was the chipset so I had that replaced, but the phenomena persisted.

I reinstalled MAGEIA 6.1 (which I assume has an older version of plasma) and I have not had any problems. I looked on the KDE bugzilla page and saw that similar problems were reported there. I posted a comment similar to this one there
Comment 13 roger herz-fischler 2019-12-09 20:55:24 CET
Created attachment 11397 [details]
just switching desktops

note how the individual cpu usages are very small, but the total is 100%
Comment 14 roger herz-fischler 2019-12-09 20:56:25 CET
Created attachment 11398 [details]
just pluggin in a USB stick

CC: (none) => roger

Comment 15 papoteur 2019-12-10 08:13:34 CET
Hi Roger,
For what I see, the system comes back to a normal state after a while.
This is not the behaviour I reported. In my case, the application which freezes doesn't come back to a normal state, and when I kill it, most of the case it will kill also the desktop.
Comment 16 papoteur 2020-01-05 09:03:37 CET
Hi,
I disabled seafile and the problem never occured since.
Thus I suspect it was the culprit.
Closing now.

Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 17 roger herz-fischler 2020-01-06 15:12:29 CET
Created attachment 11444 [details]
seafile_01.png
Comment 18 roger herz-fischler 2020-01-06 15:15:17 CET
Created attachment 11445 [details]
seafile02

Note You need to log in before you can comment on or make changes to this bug.