unity-2d-shell 5.6.0-0ubuntu1 crashes with symbol lookup error: /usr/lib/libunity-2d-private.so.0: undefined symbol: _ZN5unity4dash16FilesystemLensesC1ERKSs

Bug #948404 reported by Paul Sladen
30
This bug affects 6 people
Affects Status Importance Assigned to Milestone
unity-2d (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

ii libunity-2d-private0 5.6.0-0ubuntu1 Unity 2D shared library
ii unity-2d-shell 5.6.0-0ubuntu1 Dash and Launcher for the Unity 2D environment

  $ unity-2d-shell
  …
  unity-2d-shell: [DEBUG] virtual void Hotkey::connectNotify(const char*): Grabbing hotkey "Meta+S"
  unity-2d-shell: [DEBUG] virtual void Hotkey::connectNotify(const char*): Grabbing hotkey "Meta+T"
  unity-2d-shell: symbol lookup error: /usr/lib/libunity-2d-private.so.0: undefined symbol: _ZN5unity4dash16FilesystemLensesC1ERKSs

Revision history for this message
Paul Sladen (sladen) wrote :

(gdb) break _ZN5unity4dash16FilesystemLensesC1ERKSs
Breakpoint 2 at 0x7ffff5c227c0

Breakpoint 2, 0x00007ffff5c227c0 in unity::dash::FilesystemLenses::FilesystemLenses () from /usr/lib/libunity-2d-private.so.0
(gdb) bt
#0 0x00007ffff5c227c0 in unity::dash::FilesystemLenses::FilesystemLenses () from /usr/lib/libunity-2d-private.so.0
#1 0x00007ffff5c6b975 in Lenses::Lenses (this=0x1822680, parent=<optimized out>)
    at /build/buildd/unity-2d-5.6.0/libunity-2d-private/src/lenses.cpp:42
#2 0x00007fffe44fc530 in QDeclarativeElement (this=0x1822680) at /usr/include/qt4/QtDeclarative/qdeclarativeprivate.h:82
#3 QDeclarativePrivate::createInto<Lenses> (memory=<optimized out>) at /usr/include/qt4/QtDeclarative/qdeclarativeprivate.h:91
#4 0x00007ffff65ed7a8 in QDeclarativeVME::run (this=0x7fffffffdb70, stack=..., ctxt=0xb0fd80, comp=0xaba1f0, start=<optimized out>,
    count=<optimized out>, bindingSkipList=...) at qml/qdeclarativevme.cpp:287
#5 0x00007ffff65efb5b in QDeclarativeVME::run (this=<optimized out>, ctxt=<optimized out>, comp=<optimized out>, start=<optimized out>,
    count=<optimized out>, bindingSkipList=...) at qml/qdeclarativevme.cpp:133
#6 0x00007ffff65e3270 in QDeclarativeComponentPrivate::begin (parentContext=0xb10410, componentCreationContext=0x0, component=0xaba1f0, start=-1,
    count=-1, state=0x851268, errors=0x0, bindings=...) at qml/qdeclarativecomponent.cpp:871
#7 0x00007ffff65e374d in QDeclarativeComponentPrivate::beginCreate (this=0x8511b0, context=0xb10410, bindings=...)
    at qml/qdeclarativecomponent.cpp:836
#8 0x00007ffff65e3831 in QDeclarativeComponent::beginCreate (this=<optimized out>, context=<optimized out>) at qml/qdeclarativecomponent.cpp:798
#9 0x00007ffff6574e8f in QDeclarativeLoaderPrivate::_q_sourceLoaded (this=0x865710) at graphicsitems/qdeclarativeloader.cpp:387
#10 0x00007ffff65e2a23 in QDeclarativeComponentPrivate::complete (enginePriv=0x7f0360, state=0x8427d8) at qml/qdeclarativecomponent.cpp:962
#11 0x00007ffff65e30cf in completeCreate (this=<optimized out>) at qml/qdeclarativecomponent.cpp:1043
#12 QDeclarativeComponentPrivate::completeCreate (this=<optimized out>) at qml/qdeclarativecomponent.cpp:1039
#13 0x00007ffff65e12cf in QDeclarativeComponent::create (this=0x8423b0, context=<optimized out>) at qml/qdeclarativecomponent.cpp:768
#14 0x00007ffff64ca39f in QDeclarativeView::continueExecute (this=0x7fffffffdf60) at util/qdeclarativeview.cpp:552
#15 0x00000000004093f4 in main (argc=1, argv=<optimized out>) at /build/buildd/unity-2d-5.6.0/shell/app/shell.cpp:87

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity-2d (Ubuntu):
status: New → Confirmed
Revision history for this message
Gerry Boland (gerboland) wrote :

Performing an update should fix this. Can you confirm please?

Revision history for this message
David (kdavid93) wrote :

Could you please fix this problem?
With this bug I can't use any Unity environment.
I can't use Unity because of my VGA and now I can't even use Unity 2D because of this bug.
I had to install LXDE to be able to use my computer.

Revision history for this message
Silviu Grijincu (silviu.grijincu) wrote :

There is no unity-2d in my updated packages in the last 24 hours, so updating does not fix this.

Revision history for this message
Raphaël Badin (rvb) wrote :

I'm seeing this too.

Unity shell is not there when I log in and launching 'unity-2d-shell' manually triggers the error:
unity-2d-shell: symbol lookup error: /usr/lib/libunity-2d-private.so.0: undefined symbol: _ZN5unity4dash16FilesystemLensesC1ERKSs

I can't use unity 3d because of the awful performance I get from my GeForce 8400M GS. Now it's difficult to use unity-2d.

Revision history for this message
Albert Astals Cid (aacid) wrote :

What's the output you get from doing
    dpkg -l | grep -i libunity-core
in a shell?

Revision history for this message
Raphaël Badin (rvb) wrote :

$ dpkg -l | grep -i libunity-core
rc libunity-core-4.0-4 4.28.0-0ubuntu2 Core library for the Unity interface.
ii libunity-core-5.0-5 5.6.0-0ubuntu1 Core library for the Unity interface.

Revision history for this message
Albert Astals Cid (aacid) wrote :

Something went wrong with the packaging, https://launchpad.net/ubuntu/+archive/primary/+files/unity-2d_5.6.0.orig.tar.gz contains the line
   m_unityLenses = new unity::dash::FilesystemLenses("/usr/share/unity/lenses");
in libunity-2d-private/src/lenses.cpp that was removed in r929
  http://bazaar.launchpad.net/~unity-2d-team/unity-2d/trunk/revision/929
and 5.6.0 is supposed to be r948
  bazaar.launchpad.net/~unity-2d-team/unity-2d/trunk/revision/948
so the tarball should not contain that line of code

Revision history for this message
Didier Roche-Tolomelli (didrocks) wrote :

5.6.0 contained the revert of this commit as we released unity-2d 5.6.0-0ubuntu1 built with unity-core 5.4.

Yesterday, once unity-core 5.6 was rebuilt (but without ABI bump :/), I then rebuilt unity-2d 5.6.0-0ubuntu2 with the revert of the revert (btw you can see it in the diff.gz).

I think that the crash occured during the transition, as libunity-core didn't get an ABI break.

Changed in unity-2d (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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