gnome-disks crashed with SIGSEGV in udisks_partition_table_get_type_()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-disk-utility (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Distributor ID: Ubuntu
Description: Ubuntu Bionic Beaver (development branch)
Release: 18.04
Codename: bionic
gnome-disk-utility:
Installed: 3.27.90-1ubuntu1
Candidate: 3.27.90-1ubuntu1
Version table:
*** 3.27.90-1ubuntu1 500
500 http://
100 /var/lib/
Crashes when attempting to format a partition as vfat without erasing.
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: gnome-disk-utility 3.27.90-1ubuntu1
ProcVersionSign
Uname: Linux 4.15.0-11-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 3 11:59:27 2018
ExecutablePath: /usr/bin/
InstallationDate: Installed on 2018-01-10 (52 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180101)
ProcCmdline: /usr/bin/
ProcEnviron:
XDG_RUNTIME_
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
SegvAnalysis:
Segfault happened at: 0x7fd3090cf6a9 <udisks_
PC (0x7fd3090cf6a9) 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:
udisks_
finish_cb ()
g_closure_invoke () at /usr/lib/
() at /usr/lib/
g_signal_
Title: gnome-disks crashed with SIGSEGV in udisks_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip git kvm libvirt libvirtd lpadmin lxd plugdev sambashare sudo
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 #1750289, 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.