compiz crashed with SIGSEGV in PlacesHomeView::Refresh()

Bug #762120 reported by Andrei Drynov on 2011-04-15
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Didier Roche
unity (Ubuntu)

Bug Description

Binary package hint: unity

Test case:
  1. disable unity in ccsm
  2. change a prefered applications in gnome-default-applications-properties
  3. check that there is no crash after installing the version in -proposed.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.8.8-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Fri Apr 15 20:29:14 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
ProcCmdline: compiz
Signal: 11
SourcePackage: unity
 PlacesHomeView::Refresh() () from /usr/lib/compiz/
 gconf_listeners_notify () from /usr/lib/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/
Title: compiz crashed with SIGSEGV in PlacesHomeView::Refresh()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Andrei Drynov (adrynov) wrote :

 PlacesHomeView::Refresh (this=0x29571b0) at /build/buildd/unity-3.8.8/src/PlacesHomeView.cpp:204
 notify_listener_list (listeners=0x1dcc0b0, all_above=0x7f560c0eb1c0 "/desktop/gnome/applications/browser/exec", callback=0x7f56213b0410 <notify_listeners_callback>, user_data=0x7fff0a0b4780) at gconf-listeners.c:590
 ltable_notify (listeners=0x1dcc0b0, all_above=0x7f560c0eb1c0 "/desktop/gnome/applications/browser/exec", callback=0x7f56213b0410 <notify_listeners_callback>, user_data=0x7fff0a0b4780) at gconf-listeners.c:656
 gconf_listeners_notify (listeners=0x1dcc0b0, all_above=0x7f560c0eb1c0 "/desktop/gnome/applications/browser/exec", callback=0x7f56213b0410 <notify_listeners_callback>, user_data=0x7fff0a0b4780) at gconf-listeners.c:185
 notify_one_entry (client=0x1dbd360, entry=0x3683200) at gconf-client.c:2607

Changed in unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Omer Akram (om26er) on 2011-04-22
Changed in unity:
status: New → Confirmed
Changed in unity (Ubuntu):
status: New → Confirmed
Didier Roche (didrocks) on 2011-04-26
Changed in unity:
status: Confirmed → Fix Committed
Changed in unity (Ubuntu):
status: Confirmed → Fix Committed
Changed in unity:
importance: Undecided → Medium
assignee: nobody → Didier Roche (didrocks)
milestone: none → 3.8.12
Didier Roche (didrocks) on 2011-04-27
Changed in unity:
status: Fix Committed → Fix Released
Didier Roche (didrocks) on 2011-04-27
description: updated

Accepted unity into natty-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Sebastien Bacher (seb128) wrote :

ok, I've just tried the testcase on the updated version and I can confirm there is no segfault

tags: added: verification-done
removed: verification-needed
Launchpad Janitor (janitor) wrote :

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

unity (3.8.12-0ubuntu1) natty-proposed; urgency=low

  * New upstream release.
    - Display garbled upon restoring original resolution or connecting external
      displays (LP: #753971)
    - crashed with NameError in __main__: name 'GError' is
      not defined (LP: #759744)
    - compiz crashed with SIGSEGV in PlacesHomeView::Refresh() (LP: #762120)
    - launcher loses focus (LP: #763883)
  * debian/patches/01_add_scp_to_systray.patch:
    - Whitelist systray to system-config-printer (LP: #771562)
 -- Didier Roche <email address hidden> Wed, 27 Apr 2011 11:04:17 +0200

Changed in unity (Ubuntu Natty):
status: Fix Committed → Fix Released
Martin Pitt (pitti) wrote :

Copied to oneiric as well.

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

Other bug subscribers