Upon starting shotwell, gsettings-data-convert crash with signal 5

Bug #1047859 reported by DrJohn on 2012-09-08
This bug affects 2 people
Affects Status Importance Assigned to Milestone
shotwell (Ubuntu)

Bug Description

Start shotwell; after a few seconds a crash notification pops up: "The application Gsettings Data Conversion has closed unexpectedly." Choosing "Send an error report to help fix this Problem" appears to do nothing; the Details portion cannot be copied to the clipboard. Title of details report is "gsettings-data-convert crash with signal 5"

Occurs everytime on first launch of Shotwell after login. Choosing "ReLaunch" for gsettings-data-convert, then quitting and restarting Shotwell succeeds without the gsettings crash.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: shotwell 0.12.3-0ubuntu0.1
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic i686
ApportVersion: 2.0.1-0ubuntu12
Architecture: i386
Date: Sat Sep 8 15:55:51 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu-Netbook 10.10 "Maverick Meerkat" - Release i386 (20101007)
 PATH=(custom, no user)
SourcePackage: shotwell
UpgradeStatus: Upgraded to precise on 2012-05-10 (120 days ago)

DrJohn (jhinshaw) wrote :
DrJohn (jhinshaw) wrote :

Also, same crash occurs on a second PC, also a 10.10 ... --> 12.04 upgraded system.

DrJohn (jhinshaw) wrote :

gsettings-data-convert crash also occurs again if choosing "Leave closed" from the bug dialog popup, and then later restarting Shotwell (w/o a new login). Counter-intuitive since choosing "Relaunch" for gsettings-data-convert and then restarting Shotwell does not crash gsettings... The gsettings crash seems to have zero impact on the function of Shotwell or anything else;

Launchpad Janitor (janitor) wrote :

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

Changed in shotwell (Ubuntu):
status: New → Confirmed
Lucas Beeler (lucas-yorba) wrote :

I've ticketed this upstream here: http://redmine.yorba.org/issues/5983

Jim Nelson (yorba-jim) wrote :

I have this problem on my home Precise machine. It turns out that the issue is with the onboard keyboard's GSettings convert file. Merely uninstalling the onboard package will remove this problem. The reason you see this with Shotwell is that we decided awhile back to run the GSettings convert program at startup; the only other time it ran was when the user logged in, and we were not happy with the idea that you would have to log out and log in after installing Shotwell for your settings to be preserved.

I realize removing the onboard keyboard isn't a viable option for everyone, so we will be removing the startup execution of the converted in 0.14: http://redmine.yorba.org/issues/6369

The bug for onboard.convert's bug has been reported at bug #1123789.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers