Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#28740 - [shotwell] coredumps on startup

Attached to Project: Community Packages
Opened by David Raymond (djraymondnm) - Friday, 02 March 2012, 02:30 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 17 May 2012, 11:05 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:

shotwell (a photo manager) dumps core on startup when it has been installed
after the package librsvg. Generally, librsvg is already installed,
as a lot of things depend on it.

The problem is fixed if librsvg is reinstalled after shotwell is
installed. Once shotwell has been installed, removing it and
reinstalling it does not require a reinstall of librsvg.


Additional info:
* package version(s)

shotwell 0.11.6-1
librsvg 2.34.2-3

* config and/or log files etc.

Here is output from shotwell as it core dumps.

swallow:~$ shotwell
** Message: GConfEngine.vala:188: Error loading or parsing gsettings convert keyfile: Valid key file could not be found in search dirs
** (process:28609): DEBUG: GConfEngine.vala:191: Converting GConf settings to gsettings...
** Message: GConfEngine.vala:201: Error 133 running gsettings-data-convert: stdout="" stderr="
GLib-GIO-ERROR **: Settings schema 'org.yorba.shotwell.sharing.facebook' does not contain a key named 'session-key'
"
** (process:28609): DEBUG: GConfEngine.vala:205: GConf to gsettings conversion completed
** ERROR **: Resources.vala:808: Couldn't recognize the image file format for file '/usr/share/shotwell/icons/crop.svg'
Trace/breakpoint trap (core dumped)




Steps to reproduce:

Install shotwell on a machine (32 or 64 bit) on which it has not been
installed previously. Then, attempt to run it.

Once librsvg has been reinstalled, it is hard to recreate the bug, as
uninstalling librsvg breaks a lot of other stuff. I have two
other arch machines that I haven't installed shotwell on, so I can
easily try out fixes twice before having to do major surgery on an
arch installation to reproduce the bug.

I would guess that installing librsvg does some shotwell configuration
when it is installed if shotwell is present. If I knew where to look
I might be able to track down what librsvg does when shotwell is or is
not present.

Note that I do not have Gnome installed; maybe something in Gnome fixes
this problem. (I do have gnumeric, evince, and epiphany installed
which brings in some, but not all Gnome libraries.)
This task depends upon

Closed by  Sergej Pupykin (sergej)
Thursday, 17 May 2012, 11:05 GMT
Reason for closing:  Works for me
Additional comments about closing:  can not reproduce and no response
Comment by John Pate (jpate) - Saturday, 03 March 2012, 22:01 GMT
On my machine, the error output is much more brief:

$ shotwell

** ERROR **: Resources.vala:808: Couldn't recognize the image file format for file '/usr/share/shotwell/icons/crop.svg'
Trace/breakpoint trap



A simple # pacman -S librsvg fixes everything
Comment by Alexander F. Rødseth (xyproto) - Saturday, 03 March 2012, 22:11 GMT
Does it solve the problem if shotwell depends on the very latest version of librsvg?
Comment by John Pate (jpate) - Saturday, 03 March 2012, 22:30 GMT
I can't reproduce the error after pacman -S librsvg, but "pacman -S librsvg" only reinstalled the same version (librsvg and everything else on my system were fully up-to-date). That is, the sequence was:

# pacman -Syu # this ran to completion with no problems or pacnew files or anythin
$ shotwell

** ERROR **: Resources.vala:808: Couldn't recognize the image file format for file '/usr/share/shotwell/icons/crop.svg'
Trace/breakpoint trap
# pacman -S librsvg
$ shotwell # this runs fine

Removing shotwell, reinstalling librsvg, then reinstalling shotwell doesn't reproduce the error. Like the original poster, I have some gnome programs and libraries installed, but not full Gnome.
Comment by David Raymond (djraymondnm) - Saturday, 03 March 2012, 23:37 GMT
Confirming the comment by John Pate, reinstalling librsvg does not install a new
version; it just reinstalls the old version.
Comment by Laurent Carlier (lordheavy) - Monday, 09 April 2012, 19:10 GMT
Can you try with version in community-testing ?
Comment by David Raymond (djraymondnm) - Tuesday, 10 April 2012, 02:39 GMT
I am having trouble turning on community-testing at this point and would rather not do it because it would potentially involve screwing up a machine that is mission-critical. I would be happy to try out the new version of shotwell once it makes it into community.
Comment by Alexander F. Rødseth (xyproto) - Monday, 30 April 2012, 15:07 GMT
You can install packages from community-testing without enabling it in pacman.conf. You can download the PKGBUILD and build it with makepkg.

Loading...