Trusty Unity desktop crashes on search or shutdown

Asked by Jaime Cruz on 2017-11-07

Not sure what happened but hoping someone can help. Running Trusty Tahr on a Thinkpad T410. Ever since Thursday morning (October 26) when I applied the latest updates, Unity crashes every time I click the "Search your computer" icon at the top of the launcher. Pressing the "Super" key causes the same crash. The "Shutdown" and "Restart" buttons don't do anything (I have to open the terminal and enter "sudo shutdown" to shut down the computer). HELP! More than happy to provide ANY documentation you require. My desktop computer (an HP Pavilion) is at the exact same maintenance level and is not experiencing this problem.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Manfred Hampl
Solved:
2017-11-24
Last query:
2017-11-24
Last reply:
2017-11-24

If you log in as guest, is the system OK?

Jaime Cruz (jaime-cruz) said : #2

No, it crashed in the same manner.

Jaime Cruz (jaime-cruz) said : #3

Is there any other information I can provide? I can reproduce this issue at will. Occasionally the error reporter will pop up, but it doesn't seem to be transmitting the data even though I tell it to. I tried copying the information into the clipboard so I could paste it into gedit, but that didn't work either. Is there a log somewhere with this information?

Launchpad Janitor (janitor) said : #4

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Jaime Cruz (jaime-cruz) said : #5

Doesn't anyone have any helpful information for me?

Manfred Hampl (m-hampl) said : #6

How does this "crash" from the search button look like?
Can you continue to use the computer afterwards?
Are there any error messages in the system logs (command "dmesg | tail" after such crash)?

Jaime Cruz (jaime-cruz) said : #7

First the desktop freezes, then Unity restarts but all of my "desktops" get rearranaged. Sometimes the problem reporter pops-up, but it doesn't seem to ever send any information. I just recreated it and issued the command you suggested (thank you, that's one of the things I was looking for) and came up with:

[90311.826845] [UFW BLOCK] IN=wlp3s0 OUT= MAC=58:94:6b:c9:62:f4:20:c0:47:2c:fc:f5:08:00 SRC=176.182.119.27 DST=192.168.1.6 LEN=112 TOS=0x00 PREC=0x00 TTL=52 ID=10490 DF PROTO=UDP SPT=8316 DPT=4904 LEN=92
[90331.571207] [UFW BLOCK] IN=wlp3s0 OUT= MAC=58:94:6b:c9:62:f4:20:c0:47:2c:fc:f5:08:00 SRC=24.185.88.79 DST=192.168.1.6 LEN=112 TOS=0x00 PREC=0x00 TTL=117 ID=29 PROTO=UDP SPT=5196 DPT=4904 LEN=92
[90352.303920] [UFW BLOCK] IN=wlp3s0 OUT= MAC=58:94:6b:c9:62:f4:20:c0:47:2c:fc:f5:08:00 SRC=88.7.227.126 DST=192.168.1.6 LEN=112 TOS=0x00 PREC=0x00 TTL=117 ID=31540 PROTO=UDP SPT=7674 DPT=4904 LEN=92
[90373.585931] [UFW BLOCK] IN=wlp3s0 OUT= MAC=58:94:6b:c9:62:f4:20:c0:47:2c:fc:f5:08:00 SRC=31.173.86.99 DST=192.168.1.6 LEN=112 TOS=0x08 PREC=0x00 TTL=47 ID=0 DF PROTO=UDP SPT=28789 DPT=4904 LEN=92
[90391.851894] [UFW BLOCK] IN=wlp3s0 OUT= MAC=58:94:6b:c9:62:f4:20:c0:47:2c:fc:f5:08:00 SRC=62.182.32.65 DST=192.168.1.6 LEN=112 TOS=0x00 PREC=0x00 TTL=52 ID=15777 DF PROTO=UDP SPT=8366 DPT=4904 LEN=92
[90411.532022] [UFW BLOCK] IN=wlp3s0 OUT= MAC=58:94:6b:c9:62:f4:20:c0:47:2c:fc:f5:08:00 SRC=5.18.238.1 DST=192.168.1.6 LEN=112 TOS=0x00 PREC=0x00 TTL=51 ID=56319 DF PROTO=UDP SPT=11457 DPT=4904 LEN=92
[90425.736847] compiz[3915]: segfault at 0 ip 00007f9a7ae8deb6 sp 00007fff76c85ea0 error 4 in i965_dri.so[7f9a7a8ab000+82d000]
[90432.633396] [UFW BLOCK] IN=wlp3s0 OUT= MAC=58:94:6b:c9:62:f4:20:c0:47:2c:fc:f5:08:00 SRC=5.18.238.1 DST=192.168.1.6 LEN=112 TOS=0x00 PREC=0x00 TTL=51 ID=59022 DF PROTO=UDP SPT=11457 DPT=4904 LEN=92
[90451.657067] [UFW BLOCK] IN=wlp3s0 OUT= MAC=58:94:6b:c9:62:f4:20:c0:47:2c:fc:f5:08:00 SRC=107.77.252.122 DST=192.168.1.6 LEN=112 TOS=0x18 PREC=0x40 TTL=52 ID=0 DF PROTO=UDP SPT=5846 DPT=4904 LEN=92
[90471.694256] [UFW BLOCK] IN=wlp3s0 OUT= MAC=58:94:6b:c9:62:f4:20:c0:47:2c:fc:f5:08:00 SRC=95.90.208.93 DST=192.168.1.6 LEN=112 TOS=0x00 PREC=0x00 TTL=52 ID=19650 DF PROTO=UDP SPT=29028 DPT=4904 LEN=92
jaime@jaime-ThinkPad-T410:~$

Manfred Hampl (m-hampl) said : #8

The only interesting message (that's not coming from the firewall) is
compiz[3915]: segfault at 0 ip 00007f9a7ae8deb6 sp 00007fff76c85ea0 error 4 in i965_dri.so[7f9a7a8ab000+82d000]

What is the output of the diagnostic commands

uname -a
lsb_release -crid
apt-cache policy i965_dri.so

Jaime Cruz (jaime-cruz) said : #9

uname -a
Linux jaime-ThinkPad-T410 4.10.0-40-generic #44~16.04.1-Ubuntu SMP Thu Nov 9 15:37:44 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

lsb_release -crid
Distributor ID: Ubuntu
Description: Ubuntu 16.04.3 LTS
Release: 16.04
Codename: xenial

apt-cache policy i965_dri.so
N: Unable to locate package i965_dri.so
N: Couldn't find any package by glob 'i965_dri.so'
N: Couldn't find any package by regex 'i965_dri.so'

That last is interesting... how can I be getting a segfault in something that's not installed??

Manfred Hampl (m-hampl) said : #10

Sorry, this was my fault, the file i965_dri.so is provided by the package libgl1-mesa-dri

The command should have been

apt-cache policy libgl1-mesa-dri

Jaime Cruz (jaime-cruz) said : #11

libgl1-mesa-dri:
  Installed: 17.2.4-0ubuntu1~16.04.0
  Candidate: 17.2.4-0ubuntu1~16.04.0
  Version table:
 *** 17.2.4-0ubuntu1~16.04.0 500
        500 http://ppa.launchpad.net/ubuntu-x-swat/updates/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status
     17.0.7-0ubuntu0.16.04.2 500
        500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
     11.2.0-1ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

Best Manfred Hampl (m-hampl) said : #12

There are different version of the libgl1-mesa-dri package in the repositories.
You are using a version form a PPA, but an updated version is already available in xenial-proposed and will probably be officially published in the xenial-updates repository in the coming days.

I suggest that you wait for that new version, or eventually install it from xenial-proposed.
If that new version solves the problem, it is fine, but if it doesn't, then you might consider creating a bug report.

Jaime Cruz (jaime-cruz) said : #13

THANK YOU! I have removed the X-Swat PPA from my system and reverted back to the mainline repository for mesa. I don't even know why I added that PPA, as I don't play games on this laptop. Odd as I do have that same repository on my desktop PC, but that is an AMD-based system with Radeon graphics. I guess that driver doesn't have the same issue. In any event, my laptop is stable once again. Thanks for your assistance!

Jaime Cruz (jaime-cruz) said : #14

Thanks Manfred Hampl, that solved my question.