Ubuntu
onboard package

onboard crashed with signal 5 in g_settings_get_value()

Bug #1617108 reported by valdecir martins on 2016-08-26

10

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Onboard	New	Undecided	Unassigned
	onboard (Ubuntu)	New	Medium	Unassigned

Bug Description

crash, when start de system

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: onboard 1.3.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
Uname: Linux 4.4.0-33-generic x86_64
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Fri Aug 19 21:17:15 2016
ExecutablePath: /usr/bin/onboard
InstallationDate: Installed on 2016-04-26 (122 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160424)
InterpreterPath: /usr/bin/python3.5
ProcCmdline: /usr/bin/python3 /usr/bin/onboard --xid
Signal: 5
SourcePackage: onboard
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
g_settings_get_value () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6
ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6
Title: onboard crashed with signal 5 in g_settings_get_value()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Tags:

Revision history for this message

valdecir martins (val-markhbh) wrote on 2016-08-26:

#1

Dependencies.txt Edit (8.4 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (913 bytes, text/plain; charset="utf-8")
JournalErrors.txt Edit (19.0 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (318 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (50.8 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (914 bytes, text/plain; charset="utf-8")
Registers.txt Edit (685 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (3.2 KiB, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (4.3 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2016-08-26:

#2

StacktraceTop:
g_settings_schema_get_value () from /tmp/apport_sandbox_PLN43H/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
g_settings_schema_key_init () from /tmp/apport_sandbox_PLN43H/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
g_settings_get_value () from /tmp/apport_sandbox_PLN43H/usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
ffi_call_unix64 () from /tmp/apport_sandbox_PLN43H/usr/lib/x86_64-linux-gnu/libffi.so.6
ffi_call () from /tmp/apport_sandbox_PLN43H/usr/lib/x86_64-linux-gnu/libffi.so.6

Revision history for this message

Apport retracing service (apport) wrote on 2016-08-26: Stacktrace.txt

#3

Stacktrace.txt Edit (3.6 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2016-08-26: StacktraceSource.txt

#4

StacktraceSource.txt Edit (2.5 KiB, text/plain)

Revision history for this message

Apport retracing service (apport) wrote on 2016-08-26: ThreadStacktrace.txt

#5

ThreadStacktrace.txt Edit (4.1 KiB, text/plain)

Changed in onboard (Ubuntu):
importance:	Undecided → Medium
tags:	removed: need-amd64-retrace

Revision history for this message

Sebastien Bacher (seb128) wrote on 2016-08-26:

#6

the error suggests it tries to use a non existant gsettings key but the backtrace/log doesn't tell which one, can you try to start it manually and copy the error to the bug?

information type:

Private → Public

Revision history for this message

marmuta (marmuta) wrote on 2016-09-02:

#7

@Francesco, it's not clear to me yet that upstream onboard is affected. I did tests with a fresh pt_BR install of Yakkety and couldn't reproduce the issue. The answer to #6 would be helpful. Until then my best guess is there is a version mismatch between onboard and its installed gsettings schema.

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

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