Ubuntu
unity package

unity crashed with SIGSEGV in unity_places_place_entry_remote_set_active()

Bug #634364 reported by Orestes Bueno
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Unity
Fix Released
High
Mikkel Kamstrup Erlandsen
Unity 2010-09-24 "0.2.44 Maverik RC"
unity (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: unity

Unity crashed while clicking in the left panel. I'm using Ubuntu Maverick Beta with the latest updates.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: unity 0.2.34-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
NonfreeKernelModules: nvidia wl
Architecture: amd64
Date: Thu Sep 9 16:10:47 2010
ExecutablePath: /usr/bin/unity
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: unity
ProcEnviron:
 LANGUAGE=es_PE:es:es_AR:es_BO:es_CL:es_CO:es_CR:es_DO:es_EC:es_ES:es_GT:es_HN:es_MX:es_NI:es_PA:es_PR:es_PY:es_SV:es_US:es_UY:es_VE:en
 LANG=es_PE.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc20c1522f8 <unity_places_place_entry_remote_set_active+40>: mov (%rbx),%rdi
 PC (0x7fc20c1522f8) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 unity_places_place_entry_remote_set_active () from /usr/lib/libunity-private.so.0
 ?? () from /usr/lib/libunity-private.so.0
 unity_places_view_on_entry_view_activated () from /usr/lib/libunity-private.so.0
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: unity crashed with SIGSEGV in unity_places_place_entry_remote_set_active()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

lp:~kamstrup/unity/crash-on-dbus-fail
Mirco Müller (community): Approve
Diff: 79 lines (+29/-12)
1 file modified
unity-private/places/places-place-entry.vala (+29/-12)
lp:ubuntu/maverick/unity
Revision history for this message
Orestes Bueno (obueno) wrote :
Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

I have a hunch that this may happen if the one of the place daemons crashes on startup on the dbus call to SetActive() never receives a reply. Milestoning for next week so we can get to the bottom of this.

Changed in unity:
milestone: none → 2010-09-16
importance: Undecided → Low
assignee: nobody → Mikkel Kamstrup Erlandsen (kamstrup)
milestone: 2010-09-16 → none
status: New → Triaged
milestone: none → 2010-09-16
Revision history for this message
Neil J. Patel (njpatel) wrote :

Mikkel, would this still be an issue now places is async?

Changed in unity:
milestone: 2010-09-16 → 2010-09-22
Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

Neil has introduced null-checks for these calls in the branch i just attached.

Changed in unity:
assignee: Mikkel Kamstrup Erlandsen (kamstrup) → Neil J. Patel (njpatel)
status: Triaged → In Progress
Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

We have to let this one slide from the 09-22 milestone unfortunately. A suitable fix has not been found. Bumping severity.

Changed in unity:
assignee: Neil J. Patel (njpatel) → Mikkel Kamstrup Erlandsen (kamstrup)
importance: Low → High
status: In Progress → Triaged
Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

I just found the following suspicious line in my .xession-errors:

 (mutter:1679): libunity-private-CRITICAL **: file places-place.c: line 571: uncaught error: Failed to execute program /use/libexec/unity-applications-daemon: Success (dbus-glib-error-quark, 23)

So indeed, /use/libexec/unity-applications-daemon fails to start, and for some reason the Vala DBus layer causes a crash under these circumstances.

Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

And - my previous comment also highlights why it fails in my case. Apparently I screwed it up because I manually installed it with prefix /use and not /usr. So that gives us a way to reproduce this at least :-)

Mikkel Kamstrup Erlandsen (kamstrup)
Changed in unity:
milestone: 2010-09-22 → 2010-09-24
Didier Roche-Tolomelli (didrocks)
Changed in unity (Ubuntu):
status: New → Triaged
importance: Undecided → High
Mikkel Kamstrup Erlandsen (kamstrup)
Changed in unity:
status: Triaged → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package unity - 0.2.44-0ubuntu1

---------------
unity (0.2.44-0ubuntu1) maverick; urgency=low

  * New upstream release:
    - refine launcher tile super key overlay aesthetic (LP: #633069)
    - improve Cof logo (LP: #644686)
    - fix a crasher in the place activation (LP: #634364)
    - fixes favorite loading for didrocks (thanks!) (LP: #645835)
    - workaround translation issue for Unity trash (LP: #646653)
    - MT final adjustement for maverick (LP: #645848, #640501)
  * debian/control:
    - depend on latest unity-asset-pool
  * backport fix to respect workspace layout
  * debian/libunity0.symbols:
    - updated
 -- Didier Roche <email address hidden> Fri, 24 Sep 2010 19:57:46 +0200

Changed in unity (Ubuntu):
status: Triaged → Fix Released
Omer Akram (om26er)
Changed in unity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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