oneconf-service crashed with signal 5 in g_object_newv()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oneconf (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
this is my test-ubuntu-
after update
ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: oneconf 0.3.3
ProcVersionSign
Uname: Linux 3.8.0-1-generic x86_64
ApportVersion: 2.8-0ubuntu2
Architecture: amd64
Date: Fri Jan 25 12:45:19 2013
ExecutablePath: /usr/share/
InstallationDate: Installed on 2013-01-24 (1 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130123)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitec
ProcCmdline: /usr/bin/python3.3 /usr/share/
ProcEnviron:
SHELL=/bin/bash
XDG_RUNTIME_
PATH=(custom, no user)
LANG=fr_FR.UTF-8
Signal: 5
SourcePackage: oneconf
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
g_object_newv () from /usr/lib/
g_object_
g_object_new () from /usr/lib/
Title: oneconf-service crashed with signal 5 in g_object_newv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
information type: | Private → Public |
This crash has the same stack trace characteristics as bug #901689. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.