scan-view fails

Bug #1578803 reported by Peter Hull on 2016-05-05
This bug affects 13 people
Affects Status Importance Assigned to Milestone
clang (Debian)
Fix Released
llvm-defaults (Ubuntu)

Bug Description

Running scan-view from the terminal, for example 'scan-view /tmp/scan-build-2016-05-05-204234-1723-1'
Gives an error message:
Traceback (most recent call last):
  File "/usr/bin/scan-view", line 143, in <module>
  File "/usr/bin/scan-view", line 140, in main
    run(port, args, args.root)
  File "/usr/bin/scan-view", line 70, in run
    import ScanView
ImportError: No module named ScanView
Unhandled exception in thread started by
sys.excepthook is missing
lost sys.stderr

This is reproducible always for me.

System Info

$ lsb_release -rd
Description: Ubuntu 16.04 LTS
Release: 16.04

$ apt-cache policy clang
  Installed: 1:3.8-33ubuntu3
  Candidate: 1:3.8-33ubuntu3
  Version table:
 *** 1:3.8-33ubuntu3 500
        500 xenial/universe i386 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: clang 1:3.8-33ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic i686
ApportVersion: 2.20.1-0ubuntu2
Architecture: i386
CurrentDesktop: LXDE
Date: Thu May 5 20:53:02 2016
InstallationDate: Installed on 2015-07-23 (287 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
SourcePackage: llvm-defaults
UpgradeStatus: Upgraded to xenial on 2016-04-21 (13 days ago)

Peter Hull (peterhull90) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in llvm-defaults (Ubuntu):
status: New → Confirmed
Peter Hull (peterhull90) wrote :

This seems to now be working for me. I cannot see what, if anything, has changed.

Changed in llvm-defaults (Ubuntu):
importance: Undecided → Medium
martijntje (martijntje) wrote :

@peterhull90: I think you must have installed some package that provides the ScanView module as I still have the same problem. Most likely it is a missing dependency somewhere. I just can't seem to find the package I need to fix this problem.

Could you perhaps post a list of your installed packages? Maybe looking at the differences can trigger an idea of what exactly is going wrong here.

Peter Hull (peterhull90) wrote :

As requested by martijntje, a list of packages on the system. Please let me know if I can provide more information.

I have report the same type of bug for Debian : (and it is now fixed)

Peter Hull (peterhull90) wrote :

Apologies. When I reported that the bug seemed to be fixed for me (comment #3) this was because I had added a symlink from /usr/share/scan-view to /usr/share/clang/scan-view-3.8/share and forgotten that I had done so.
Without this symlink the bug is still present.

Tully (tully.foote) wrote :

This appears to be fixed upstream but not deployed on my system 16.04. A quick workaround is to simply extend your python path.

`PYTHONPATH=/usr/share/clang/scan-view-3.8/share:$PYTHONPATH scan-view`

Anthony Coddington (antcodd) wrote :

The issue here is the patch (added in bug #1660622?) has a hardcoded fix with:

BASE_DIR = '/usr/share/clang/scan-view-3.9'

This has not been updated for the other or newer versions of the package!
If you have clang-3.9 installed other versions of scan-view will 'work' as they will actually effectively use parts of scan-view-3.9

This also applies to the upstream llvm apt repository, not sure if also applies to debian.

Changed in clang (Debian):
status: Unknown → Fix Released
Joan Massich (massich) wrote :

Is this still a present bug ?

I've the same behavior (with the difference that I'm using scan-view-4.0). So adding `export PYTHONPATH=/usr/share/clang/scan-view-4.0/share:$PYTHONPATH` to the `.zshrc` (or `.bashrc`) would do the workaround.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.