Bugzilla – Bug 1102625
Snapshot 20180723 severely broke Kontact and Falkon
Last modified: 2018-08-05 23:41:32 UTC
Today I updated TW and found through trial and error that some common component of Kontact and Falkon (with kwallet plugin enabled) crashes in a way so bad, that it completely locks up the system. The fan ramps up and all typical system activity freezes.
I just discovered that the problem might be deeper than I thought. I can reliably crash the system by using the duckduckgo.com search engine in Firefox. Google is safe.
(In reply to Marek Paśnikowski from comment #1) > I just discovered that the problem might be deeper than I thought. I can > reliably crash the system by using the duckduckgo.com search engine in > Firefox. Google is safe. Except for a update of the "re2" lib I don't see any changes in that snapshot which might have an impact. If it completely locks up the system it's actually a kernel bug. Can you still login remotely or switch to different ttys?
Apologies for a late reply. When the system locks up, I can not switch to the other TTYs. I have no way of testing a remote login. Since then I run the current Leap as my main system. The broken Tumbleweed is still available on my disk for further tests.
I ended up testing a separate installation of Tumbleweed with GNOME and found that the same problem happened when I tried to access https://www.co-operativebank.co.uk/ on Firefox.
As you mention the combination of Tumbleweed, Gnome (probably wayland) certain web pages with Firefox and freezing, this could be duplicate of bug 1103136 Then it would be xorg related. Could you please: 1. test the packages as provided in https://bugzilla.opensuse.org/show_bug.cgi?id=1103136#c3 ? 2. try the tests from the above bug to reproduce the issue? (safe mode, certain web pages) Please report back the results of both points so it's clear if this is a duplicate.
The patched packages in the other bug report solved all my problems in the original system.
Thanks, marking this bug as duplicate *** This bug has been marked as a duplicate of bug 1103136 ***