Sudden issues - slow plasma start, can't shutdown, yast freezes, firefox freezes, slow dolphin

I have a bunch of weird random issues making my system very difficult to use. The last time I used this machine was on 4/29 when I also installed available updates.

I am experiencing the following problems:

  • Plasma slower than usual to start… The progress bar shows up for a long time, and then I see the desktop without widgets for quite a long time before they appear. I tried enabling the KDE logs but it’s so noisy I can’t really tell if any of it is relevant to this issue. I do see lots of “QXcbConnection: XCB error: 3 (BadWindow)” errors though.
  • Dolphin takes a very long time to open
  • Yast GUI gets stuck on Detecting Network Devices if I open Network Settings. The last line in the y2log is:

[Ruby] modules/Linuxrc.rb:55 Reading install.inf, but file doesn’t exist!!!"

  • Hardware Information from Yast hangs at “0% - fingerprint”. Last line in y2log is:

    [Interpreter] clients/hwinfo.rb:210 SCR::Dir() failed

  • Firefox freezes randomly but also every single time I open http://www.opensuse.org/searchPage, though this works fine in Chromium. Tried clearing history and cache without luck.

  • I can’t soft shutdown or reboot - plasma closes but the system freezes at the login prompt

I checked /var/log/boot.log and the only sort of failure I see is “Network Manager is not active: Dependency failed for Network Manager Wait Online”, but after that it appears to fire up some network related services called wicked succesfully.

I tried enabling the KDE logs but it’s so noisy I can’t really tell if any of it is relevant to this issue. I do see lots of “QXcbConnection: XCB error: 3 (BadWindow)” errors though.

The only thing that stands out at me as a possible issue from my update history is that aaa_base and aaa_base-extras were updated which both seem to contain a wide variety of config file changes.

I don’t really know what to do next to debug this stuff… Any help is appreciated!

Well, I accidentally fixed it by unplugging my Xbox One controller via USB. I usually boot into windows for gaming and typically put the controller away when I am done, but had not today.

Doing some googling, it seems like this might be an issue with the latest xb1 controller firmware and a bug in the kernel? Apparently it is fixed in the 4.5 kernel…

Glad it’s fixed but wish I had learned how to debug the issue myself rather than stumbling across it :slight_smile: