deja-dup-monitor crashed with signal 7 in g_object_newv()

Bug #946733 reported by Ralph Forbes on 2012-03-04
This bug affects 4 people
Affects Status Importance Assigned to Milestone
d-conf (Ubuntu)

Bug Description

 I think my problems were caused by using Bleachbit.

Ubuntu 12.04 LTS Beta 1

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: deja-dup 21.90-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 1.94-0ubuntu1
Architecture: amd64
Date: Sun Mar 4 17:45:33 2012
ExecutablePath: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
ExecutableTimestamp: 1330022001
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120301)
ProcCmdline: /usr/lib/deja-dup/deja-dup/deja-dup-monitor
ProcCwd: /home/ralph
 PATH=(custom, no user)
Signal: 7
SourcePackage: deja-dup
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/
 ?? () from /usr/lib/x86_64-linux-gnu/gio/modules/
 g_object_newv () from /usr/lib/x86_64-linux-gnu/
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/
Title: deja-dup-monitor crashed with signal 7 in g_object_newv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Ralph Forbes (rvforbes) wrote :

 dconf_engine_refresh_user (engine=0x19bd2d0) at ../engine/dconf-engine.c:146
 dconf_engine_refresh (engine=0x19bd2d0) at ../engine/dconf-engine.c:197
 dconf_engine_get_state (engine=0x19bd2d0) at ../engine/dconf-engine.c:207
 outstanding_watch_new (name=0x19e77c0 "/org/gnome/deja-dup/", dcsb=0x19d3810) at dconfsettingsbackend.c:538
 dconf_settings_backend_subscribe (backend=<optimized out>, name=<optimized out>) at dconfsettingsbackend.c:626

Changed in deja-dup (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Launchpad Janitor (janitor) wrote :

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

Changed in deja-dup (Ubuntu):
status: New → Confirmed
Michael Terry (mterry) on 2012-03-16
visibility: private → public
Michael Terry (mterry) wrote :

Not sure what to do with this. It crashes in dconf, so I'll re-assign there. But the stack doesn't look incomplete, so there might be some memory corruption.

affects: deja-dup (Ubuntu) → d-conf (Ubuntu)
happytian (tianlefdu) on 2012-06-03
Changed in d-conf (Ubuntu):
assignee: nobody → happytian (tianlefdu)
assignee: happytian (tianlefdu) → nobody
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers