gnome-disks crashed with SIGSEGV in g_dbus_object_get_interface()

Bug #1547340 reported by 100best
72
This bug affects 16 people
Affects Status Importance Assigned to Milestone
gnome-disk-utility (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

crashed when making a usb fat32 and did not finish making a fat32 file system.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-disk-utility 3.18.3.1-1ubuntu1
ProcVersionSignature: hostname 4.4.0-4.19-generic 4.4.1
Uname: Linux 4.4.0-4-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 19 01:10:08 2016
ExecutablePath: /usr/bin/gnome-disks
InstallationDate: Installed on 2016-02-18 (1 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160217)
ProcCmdline: /usr/bin/gnome-disks --gapplication-service
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7fa8b4a38b6f <g_dbus_object_get_interface+15>: mov (%rbx),%rdi
 PC (0x7fa8b4a38b6f) 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 ()
 ?? ()
 ?? () 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

Revision history for this message
100best (jm-100best-deactivatedaccount) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_dbus_object_get_interface () from /tmp/apport_sandbox_zVCA_y/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 udisks_object_peek_drive (object=0x0) at udisks-generated.c:31392
 gdu_window_select_object (window=0x189eb20, object=object@entry=0x0) at gduwindow.c:849
 create_partition_cb (source_object=0x183eb60, res=<optimized out>, user_data=0x1adedc0) at gducreatepartitiondialog.c:374
 g_task_return_now () from /tmp/apport_sandbox_zVCA_y/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-disk-utility (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 gnome-disk-utility (Ubuntu):
status: New → Confirmed
information type: Private → Public
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1547340

tags: added: iso-testing
Revision history for this message
sudodus (nio-wiklund) wrote :

Workarounds: gparted and mkusb manage to do what gnome-disks cannot do (I have tested in the same system).

Revision history for this message
sudodus (nio-wiklund) wrote :

Second workaround: gnome-disks works if wiping the whole device (in the format menu) before creating the partition and file system. But this is very slow.

It is enough to wipe the first megabyte (actually mibibyte 1024x1024 bytes) which takes less than 1 second compared to 6-16 minutes to wipe the whole device in typical 4 GB pendrives. Wiping the whole device is also causing unnecessary wear of the flash hardware.

It possible to do it stepwise. First the partition is created and in the next step the file system.

The tools are there but the internal work flow is buggy. Average users will give up long before they have explored all the alternatives.

-o-

Third workaround: It works with root privileges, but I guess this is not what you developers want ;-)

sudo -H gnome-disks

First 'Format disk' to create a new partition table, then 'Create partition in unallocated place' at the plus sign.

Revision history for this message
Kamilion (kamilion) wrote :

Some notes -- This seems to happen after creation of the partition, but before formatting it.
Easiest workaround I have is just relaunch gnome-disks and format the partition it created just before crashing.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

I was creating a Ext4 filesystem on an SD card. AS far as I could tell the process had completed several seconds before the crash report came up.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Actually, having looked at the SD card again it seems that the old partitions were removed but the new partition was not added.

Revision history for this message
Thomas A. F. Thorne (tafthorne) wrote :

Making a second attempt after reopening the Disks application seemed to work.

tags: added: yakkety
Revision history for this message
Perlover (perlover) wrote :

Hi,

I have Linux Mint 18.3 (it's based on Ubuntu 16.04)
I am about UDisks 2.1.7 (gnome-disks)

When i try to make LUKS partition in USB flash drive (SSD Samsung 1Tb) i regulary got crash
When i run from 'root' (sudo -H gnome-disks) user i got crash again but i have core file. I got backtrace there (to see atached file)

I hope this will help to understand this bug and to patch it. It's annoying users (i am sure) :( I cannot make partition through standard utility of disks for Linux Mint.

Perlover

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.