Ubiquity crashed during install of 18.04 with error 'BadAccess (attempt to access private resource denied)'

[PJSingh5000]

Ubiquity consistently crashes during install.
I use the "Something else" option.
It crashes after I've entered the user information and clicked Next.
No error message is displayed.

If I try to restart Ubiquity, I get a dialog with the message "ubi-partman failed with an exit code 10." If I click the dialog's try again button, I get the same message.

My system is broken, and I am only able to install 17.10.1.

$ sudo dmidecode | grep -A 9 "System Information"

System Information
 Manufacturer: HP
 Product Name: HP Spectre x360 Convertible 15-bl1XX
 Version:
 Serial Number: 5CD74284QL
 UUID: 37444335-3234-3438-514C-4C3432344435
 Wake-up Type: Power Switch
 SKU Number: 1VW22AV
 Family: 103C_5335KV HP Spectre

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Sat Apr 28 16:13:14 2018
InstallCmdLine: BOOT_IMAGE=(loop)/casper/vmlinuz boot=casper iso-scan/filename=/ubuntu-18.04.0-2018.04.28-desktop-amd64.iso noprompt noeject
LiveMediaBuild: Ubuntu 18.04.0 2018.04.28 LTS x64 "Custom Bionic Beaver"
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

[PJSingh5000 (pjsingh5000)]

I also tried the "Erase and Install" and "Reinstall" options, so this issue happens even when I don't use the "Something else" option.

[ZoFreX (zofrex)]

I have the same error I believe - BadAccess in my Ubiquity logs.

I was booting the installer off one USB drive and installing it onto another USB drive, running natively on my Macbook. I tried lots of different combinations of install options and it always crashes at that point.

As well as trying 18.04 I tried 17.10 with the same result.

I then moved on to testing within VMWare. Installing to a virtual hard disk worked as expected, but installing to the USB drive still crashes in the same way. I then tried a completely different USB drive (plugged into a different port) as the target and it still crashed.

Based on this it seems like in my situation at least it is something to do with the target drive being on USB?

[Launchpad Janitor (janitor)]

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

[Riccardo Pittau (rpittau)]

Same issue on a Dell XPS 9360
The issue seems to happen during or at the end of the files copying procedure as the partitions are correctly setup.

[Fouad (fouad-ramsis)]

Same here,

Trying to install 18.04 LTS on an Lenovo Yoga 920. Installer crashes shortly after filling in the user details and click on "continue"

A bit of a disappointing experience, one might think at least installation should work, after several "test versions".

[Mathieu Trudel-Lapierre (cyphermox)]

Could people please add the contents of /var/log/syslog from the installer system after the crash (if they can still get to it)?

PJSingh5000's logs contain a crash in libglib; we should check if that's how the issue presents for others too?

Is this all happening with standard, unmodified images (PJSingh5000's was not a standard unmodified image, it's showing as customized), directly on hardware, or are people booting from the network, in VMs, doing remote desktop or something else?

[Eric Desrochers (slashd)]

Can you please provide the following cmd outputs for each of your affected system ? and the content of "/var/log/installer/"

# lspci -nnvv
# dmidecode

[Sebastien Bacher (seb128)]

the issue looks similar to bug #1751252 syslog has the same glib/python errors

[Sebastien Bacher (seb128)]

if someone can reproduce the error it would be useful to install libgtk-3-0-dbgsym and start ubiquity under gdb with --sync and "b gdk_x_error" to get a backtrace of the xerror, see https://stackoverflow.com/questions/30078005/how-to-break-on-gdk-x-error-using-gdb

[Eric Desrochers (slashd)]

Seems like using "GDK_SYNCHRONIZE=1" might be the way to do it instead of --sync ?

[Eric Desrochers (slashd)]

https://developer.gnome.org/gtk3/stable/gtk-x11.html
...
GDK_SYNCHRONIZE. If set, GDK makes all X requests synchronously. This is a useful option for debugging, but it will slow down the performance considerably.

[Chris Jensen (crjensen)]

ubuntu@ubuntu:~$ sudo lspci -nnvv
00:00.0 Host bridge [0600]: Intel Corporation Broadwell-U Host Bridge -OPI [8086:1604] (rev 09)
 Subsystem: Apple Inc. Broadwell-U Host Bridge -OPI [106b:013f]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: [e0] Vendor Specific Information: Len=0c <?>
 Kernel driver in use: bdw_uncore

00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Graphics 6100 [8086:162b] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. Iris Graphics 6100 [106b:013f]
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 66
 Region 0: Memory at c0000000 (64-bit, non-prefetchable) [size=16M]
 Region 2: Memory at b0000000 (64-bit, prefetchable) [size=256M]
 Region 4: I/O ports at 3000 [size=64]
 [virtual] Expansion ROM at 000c0000 [disabled] [size=128K]
 Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Address: fee00018 Data: 0000
 Capabilities: [d0] Power Management version 2
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [a4] PCI Advanced Features
  AFCap: TP+ FLR+
  AFCtrl: FLR-
  AFStatus: TP-
 Kernel driver in use: i915
 Kernel modules: i915

00:03.0 Audio device [0403]: Intel Corporation Broadwell-U Audio Controller [8086:160c] (rev 09)
 Subsystem: Apple Inc. Broadwell-U Audio Controller [106b:013f]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 256 bytes
 Interrupt: pin A routed to IRQ 70
 Region 0: Memory at c1810000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: [50] Power Management version 2
  Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
  Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [60] MSI: Enable+ Count=1/1 Maskable- 64bit-
  Address: fee00638 Data: 0000
 Capabilities: [70] Express (v1) Root Complex Integrated Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0
   ExtTag- RBE-
  DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
   RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
   MaxPayload 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
 Kernel driver in use: snd_hda_intel
 Kernel modules: snd_hda_intel

00:14.0 USB controller [0c03]: Intel Corporation Wildcat Point-LP USB xHCI Controller [8086:9cb1] (rev 03) (prog-if 30 [XHCI])
 Subsystem: Intel Corporation Wildcat Point-LP USB xHCI Controller [8086:7270]
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- ...

[Chris Jensen (crjensen)]

ubuntu@ubuntu:~$ sudo dmidecode
# dmidecode 3.1
Getting SMBIOS data from sysfs.
SMBIOS 2.7 present.
32 structures occupying 1616 bytes.
Table at 0x8AFAC000.

Handle 0x0000, DMI type 7, 19 bytes
Cache Information
 Socket Designation: L1 Cache
 Configuration: Enabled, Not Socketed, Level 1
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 32 kB
 Maximum Size: 32 kB
 Supported SRAM Types:
  Synchronous
 Installed SRAM Type: Synchronous
 Speed: Unknown
 Error Correction Type: Parity
 System Type: Data
 Associativity: 8-way Set-associative

Handle 0x0001, DMI type 7, 19 bytes
Cache Information
 Socket Designation: L1 Cache
 Configuration: Enabled, Not Socketed, Level 1
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 32 kB
 Maximum Size: 32 kB
 Supported SRAM Types:
  Synchronous
 Installed SRAM Type: Synchronous
 Speed: Unknown
 Error Correction Type: Parity
 System Type: Instruction
 Associativity: 8-way Set-associative

Handle 0x0002, DMI type 7, 19 bytes
Cache Information
 Socket Designation: L2 Cache
 Configuration: Enabled, Not Socketed, Level 2
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 256 kB
 Maximum Size: 256 kB
 Supported SRAM Types:
  Synchronous
 Installed SRAM Type: Synchronous
 Speed: Unknown
 Error Correction Type: Single-bit ECC
 System Type: Unified
 Associativity: 8-way Set-associative

Handle 0x0003, DMI type 7, 19 bytes
Cache Information
 Socket Designation: L3 Cache
 Configuration: Enabled, Not Socketed, Level 3
 Operational Mode: Write Back
 Location: Internal
 Installed Size: 4096 kB
 Maximum Size: 4096 kB
 Supported SRAM Types:
  Synchronous
 Installed SRAM Type: Synchronous
 Speed: Unknown
 Error Correction Type: Multi-bit ECC
 System Type: Unified
 Associativity: 16-way Set-associative

Handle 0x0004, DMI type 4, 42 bytes
Processor Information
 Socket Designation: U3E1
 Type: Central Processor
 Family: Core i7
 Manufacturer: Intel(R) Corporation
 ID: D4 06 03 00 FF FB EB BF
 Signature: Type 0, Family 6, Model 61, Stepping 4
 Flags:
  FPU (Floating-point unit on-chip)
  VME (Virtual mode extension)
  DE (Debugging extension)
  PSE (Page size extension)
  TSC (Time stamp counter)
  MSR (Model specific registers)
  PAE (Physical address extension)
  MCE (Machine check exception)
  CX8 (CMPXCHG8 instruction supported)
  APIC (On-chip APIC hardware supported)
  SEP (Fast system call)
  MTRR (Memory type range registers)
  PGE (Page global enable)
  MCA (Machine check architecture)
  CMOV (Conditional move instruction supported)
  PAT (Page attribute table)
  PSE-36 (36-bit page size extension)
  CLFSH (CLFLUSH instruction supported)
  DS (Debug store)
  ACPI (ACPI supported)
  MMX (MMX technology supported)
  FXSR (FXSAVE and FXSTOR instructions supported)
  SSE (Streaming SIMD extensions)
  SSE2 (Streaming SIMD extensions 2)
  SS (Self-snoop)
  HTT (Multi-threading)
  TM (Thermal monitor supported)
  PBE (Pending break enabled)
 Version: Intel(R) Core(TM) i7-5557U CPU @ 3.10GHz
 Voltage: 1.1 V
 External Clock: 25 MHz
 Max Speed: 3100 MHz
 Current Speed: 3400 MHz
 Status: Populated, Enabled
 Upgrade: Socket BGA1168
 L1 Cache Handle: 0x0001
 L2 Cache Handle: 0x0002
 L3...

[Chris Jensen (crjensen)]

I got those commands to return. I apologize if I'm not posting these correctly, hopefully they help!

[Chris Jensen (crjensen)]

Probably should have mentioned I'm attempting to dual boot with Windows 10, GPT - UEFI, on a MacbookPro 12,1. Intend on installing rEFInd once I finished with this install and then take it from there. I already had the drives partitioned accordingly. Anything else you need to know, please don't hesitate to ask!

[Chris Jensen (crjensen)]

Eric Desrochers (slashd),

Did I post that correctly? I ended up having to run the commands as root. I didn't refresh before i started spewing, so I missed your response. If there's further requests or instructions, I'm all eyes! lol

[PJSingh5000 (pjsingh5000)]

The issue happens using the unmodified official 18.04 live ISO on bare hardware (not virtualzed).

I will attach the log files shortly.

[Eric Desrochers (slashd)]

Chris, yeah I see you are installing Ubuntu on a MAC (Apple inc). I was curious to see if there was a common HW to everyone (graphic card,...) but it doesn't seems like it so far)

As stated in comment#10 to comment#12, it would be good to have a dump in 'sync' mode.

[PJSingh5000 (pjsingh5000)]

syslog after crash

[PJSingh5000 (pjsingh5000)]

dmidecode

[PJSingh5000 (pjsingh5000)]

lspci

[PJSingh5000 (pjsingh5000)]

installer/debug

[PJSingh5000 (pjsingh5000)]

Contents of installer/version is...

ubiquity 18.04.14

[Eric Desrochers (slashd)]

I *think* I start to see a tendencies where affected system might all have a GeForce 3D controller.

So far:

Launchpad description : Product Name: HP Spectre x360 Convertible 15-bl1XX
https://store.hp.com/us/en/pdp/hp-spectre-x360-convertible-laptop-15t-touch-1wb97av-1 |
Processor and graphics
Intel® Core™ i7-8550U (1.8 GHz, up to 4 GHz, 8 MB cache, 4 cores) + NVIDIA® GeForce® MX150 (2 GB GDDR5 dedicated)

and 2 others:
* 3D controller [0302]: NVIDIA Corporation GP108M [GeForce MX150] [10de:1d10] (rev a1)
* 3D controller [0302]: NVIDIA Corporation GK107M [GeForce GT 750M] [10de:0fe4] (rev a1)

So far 3 affected system (minus the Apple machine) of them seems to report a GeForce,
I don't know yet if this might be related to some driver (nouveau) or else, but since this is non reproducible inside a VM, it may or may not be related to a specific type of HW.

[Eric Desrochers (slashd)]

By curiosity, does anyone one not having a GeForce graphic card affected by this bug so far (minus the Apple one) ?

[PJSingh5000 (pjsingh5000)]

The command
    gdb file /usr/bin/ubiquity
gives the error
    "not in executable format: File format not recognized"

What am I missing?

[Eric Desrochers (slashd)]

PJSingh5000 (pjsingh5000),

It's because you try to open the ubiquity python program directly with gdb.

Install python3 debug symbol (python3-dbg), then try something like this :

gdb -ex r --args /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity gtk_ui

or if the process is already running :

gdb python3 <PID>

The Cmdline is based on the crash file I got earlier by someone :

InterpreterPath: /usr/bin/python3.6
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity gtk_ui

[Cris Bennett (crispinb)]

I only found this issue after a failed installation attempt, so (apologies) I am short on detailed info. But I'm getting what looks superficially at least just like this issue, installing to a Macbook Pro (13", 2013). So no GeForce involved in my case.

I was booting from the Ubuntu 18.04 install iso on a small USB stick, and installing to a (new) ext4 partition on an external SSD (GUID partition map, with a couple of existing HFS+ partitions) mounted via USB.

[PJSingh5000 (pjsingh5000)]

@slashd, I will try again with the command you provided.

In the mean time, I was able to use gdb to attach to a running instance of Ubiquity.

Here is the backtrace at gdk_x_error.

[PJSingh5000 (pjsingh5000)]

Oops, in comment #25, I forgot to attach the installer/debug file.
Here it is.

[Sebastien Bacher (seb128)]

Thanks for the backtrace, it's not very useful without debug symbols installed though, could you install the libx11-6-dbgsym libgtk-3-0-dbgsym libglib2.0-0-dbgsym debs and get a new one?

[Daniel van Vugt (vanvugt)]

This does seem to be bug 1751252. Maybe we should discuss it there.

[PJSingh5000 (pjsingh5000)]

@seb128, the three packages libx11-6-dbgsym, libgtk-3-0-dbgsym, libglib2.0-0-dbgsym do not seem to be available in the repositories for bionic. Is there a PPA I need to add, or some other location to get these from?

[Eric Desrochers (slashd)]

@PJSingh5000,

Yes the instructions can be found here :
https://wiki.ubuntu.com/Debug%20Symbol%20Packages

#1
sudo echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted universe multiverse
deb http://ddebs.ubuntu.com $(lsb_release -cs)-updates main restricted universe multiverse
deb http://ddebs.ubuntu.com $(lsb_release -cs)-proposed main restricted universe multiverse" | \
sudo tee -a /etc/apt/sources.list.d/ddebs.list

#2
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01 C8CAB6595FDFF622

#3
sudo apt-get update

and then install the -dbg or -dbgsym associated packages.

[Eric Desrochers (slashd)]

If you manage to have a gdb with the proper debug symbol (with no ??) in 'sync' mode.

Could you please send us the output of
"(gdb) bt f" instead of "(gdb) bt"

Eric

[Eric Desrochers (slashd)]

and possibly keep the gdb session open for further instructions (if possible)

[Cubic PPA (cubic-wizard)]

@slashd,

Thanks for the instructions.
I will execute this tonight.
I will see if I can keep gdb open as well.

Should I attach the results to bug #1751252, instead of here?

[Andrey Arapov (andrey-arapov)]

This patch worked for me https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1751252/comments/37

[Tien Do (tiendo1011)]

The scaling factor is what caused the crash on my machine. By default it is 200 % and this makes Ubiquity crash. Changing to 100 % (even just before validating last input panel) prevents it from crashing.

Obviously this a bug.

[Kostas Peletidis (kpeletidis)]

I saw the same bug during installation of Xubuntu 18.04 LTS on a 32-bit Acer Aspire Revo (Intel Atom cpu, NVidia MCP79 chipset). It looks like the nvidia driver has something to do with it. I tried twice to install with the proprietary drivers (including nvidia) enabled and I saw the bug. The third time I installed without proprietary drivers and the installation worked fine. After installation I enabled the proprietary nvidia driver, no problems at all.
HTH