unity-scope-home crashed with signal 5 in g_wakeup_new()

Bug #1199715 reported by Michał Sawicz
46
This bug affects 4 people
Affects Status Importance Assigned to Milestone
libunity
Fix Released
High
Michal Hruby
libunity (Ubuntu)
Fix Released
Undecided
Unassigned
unity-scope-home (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Not sure what happened here, just started my session.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: unity-scope-home 6.8.1+13.10.20130705-0ubuntu1
ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: nvidia wl
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Wed Jul 10 10:44:49 2013
ExecutablePath: /usr/lib/x86_64-linux-gnu/unity-scope-home/unity-scope-home
MarkForUpload: True
ProcCmdline: /usr/lib/x86_64-linux-gnu/unity-scope-home/unity-scope-home
Signal: 5
SourcePackage: unity-scope-home
StacktraceTop:
 g_wakeup_new () at /build/buildd/glib2.0-2.37.3/./glib/gwakeup.c:163
 g_cancellable_make_pollfd (cancellable=cancellable@entry=0x1ae22b0, pollfd=pollfd@entry=0x7f2580a21b20) at /build/buildd/glib2.0-2.37.3/./gio/gcancellable.c:402
 socket_source_new (cancellable=0x1ae22b0, condition=(G_IO_IN | G_IO_ERR | G_IO_HUP), socket=0x1b09130) at /build/buildd/glib2.0-2.37.3/./gio/gsocket.c:3264
 g_socket_create_source (socket=0x1b09130, condition=condition@entry=(G_IO_IN | G_IO_ERR | G_IO_HUP), cancellable=cancellable@entry=0x1ae22b0) at /build/buildd/glib2.0-2.37.3/./gio/gsocket.c:3329
 _g_socket_read_with_control_messages (socket=0x1b09130, buffer=0x7f2580589f10, count=16, messages=0x1b0cb00, num_messages=0x1b0cb08, io_priority=<optimized out>, cancellable=0x1ae22b0, callback=0x7f258b2a6160 <_g_dbus_worker_do_read_cb>, user_data=0x1b0ca70) at /build/buildd/glib2.0-2.37.3/./gio/gdbusprivate.c:201
Title: unity-scope-home crashed with signal 5 in g_wakeup_new()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo

Related branches

Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_wakeup_new () at /build/buildd/glib2.0-2.37.3/./glib/gwakeup.c:163
 g_cancellable_make_pollfd (cancellable=cancellable@entry=0x1ae22b0, pollfd=pollfd@entry=0x7f2580a21b20) at /build/buildd/glib2.0-2.37.3/./gio/gcancellable.c:402
 socket_source_new (cancellable=0x1ae22b0, condition=(G_IO_IN | G_IO_ERR | G_IO_HUP), socket=0x1b09130) at /build/buildd/glib2.0-2.37.3/./gio/gsocket.c:3264
 g_socket_create_source (socket=0x1b09130, condition=condition@entry=(G_IO_IN | G_IO_ERR | G_IO_HUP), cancellable=cancellable@entry=0x1ae22b0) at /build/buildd/glib2.0-2.37.3/./gio/gsocket.c:3329
 _g_socket_read_with_control_messages (socket=0x1b09130, buffer=0x7f2580589f10, count=16, messages=0x1b0cb00, num_messages=0x1b0cb08, io_priority=<optimized out>, cancellable=0x1ae22b0, callback=0x7f258b2a6160 <_g_dbus_worker_do_read_cb>, user_data=0x1b0ca70) at /build/buildd/glib2.0-2.37.3/./gio/gdbusprivate.c:201

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in unity-scope-home (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity-scope-home (Ubuntu):
status: New → Confirmed
Michał Sawicz (saviq)
information type: Private → Public
Changed in unity-scope-home:
status: New → Confirmed
importance: Undecided → High
Revision history for this message
Paweł Stołowski (stolowski) wrote :

Crash caused by too many open file descriptors (cancellables, dee model sockets), and that is because there is currently now way to detect if search channel should be closed. This fix: https://bugs.launchpad.net/unity-scope-home/+bug/1228260 will reduce number of fds a bit, but it doesn't fix the root problem. A fix in libunity is needed to detect dead channels.

Michal Hruby (mhr3)
Changed in libunity:
status: New → In Progress
importance: Undecided → High
assignee: nobody → Michal Hruby (mhr3)
Revision history for this message
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:libunity at revision 294, scheduled for release in libunity, milestone 7.0.0

Changed in libunity:
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in libunity (Ubuntu):
status: New → Confirmed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libunity - 7.1.1+13.10.20130927-0ubuntu1

---------------
libunity (7.1.1+13.10.20130927-0ubuntu1) saucy; urgency=low

  [ Michal Hruby ]
  * Auto-close channels when their owner disappears from the bus. (LP:
    #1228097, #1199715)
  * Allow metadata=None when creating SearchContext from python. (LP:
    #1231390)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 295
 -- Ubuntu daily release <email address hidden> Fri, 27 Sep 2013 03:10:38 +0000

Changed in libunity (Ubuntu):
status: Confirmed → Fix Released
no longer affects: unity-scope-home
Changed in unity-scope-home (Ubuntu):
status: Confirmed → Invalid
Michal Hruby (mhr3)
Changed in libunity:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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