gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

[Tamas Toth]

Gnome Disks siply crashed while I tried to mountone partition. After the crash at the next try there were no further problem.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: gnome-disk-utility 3.16.0-0ubuntu1~vivid1 [origin: LP-PPA-gnome3-team-gnome3-staging]
ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4
Uname: Linux 3.19.0-26-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.3
Architecture: amd64
CurrentDesktop: GNOME
Date: Fri Aug 21 11:29:43 2015
ExecutablePath: /usr/bin/gnome-disks
InstallationDate: Installed on 2015-06-03 (78 days ago)
InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422)
ProcCmdline: gnome-disks
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f3d16e6bdbf <g_dbus_object_get_interface+15>: mov (%rbx),%rdi
 PC (0x7f3d16e6bdbf) ok
 source "(%rbx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-disk-utility
StacktraceTop:
 g_dbus_object_get_interface () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 udisks_object_peek_drive () from /usr/lib/x86_64-linux-gnu/libudisks2.so.0
 gdu_window_select_object ()
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
Title: gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers

[Ubuntu GNOME (ug-bot)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1470669, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.