Bug 4184

Summary: Shotwell not able to startup
Product: Mageia Reporter: Herbert Poetzl <herbert>
Component: RPM PackagesAssignee: Damien Lallement <mageia>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: herbert, jani.valimaa, mageia, mageia, marja11, olav
Version: Cauldron   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: shotwell-0.12.0-0.git20111104.1.mga2.src.rpm CVE:
Status comment:

Description Herbert Poetzl 2012-01-18 17:37:08 CET
Description of problem:
shotwell doesn't startup properly
note that 'display' can show the image file in question quite fine.

Version-Release number of selected component (if applicable):
lib64gdk_pixbuf2.0_0-loaders-png12-2.25.0-1.mga2.x86_64
shotwell-0.12.0-0.git20111104.1.mga2.x86_64

How reproducible:
always

Steps to Reproduce:
1. open terminal
2. type shotwell
3. press enter

$ shotwell
** Message: GSettingsEngine.vala:457: Error 5 running gsettings-data-convert: stdout="" stderr="
GLib-GIO-WARNING **: g_settings_set_value: value for key 'print-wrap-mode' in schema 'org.gnome.gedit.preferences.print' is outside of valid range

GLib-GIO-WARNING **: g_settings_set_value: value for key 'action-double-click-titlebar' in schema 'org.gnome.desktop.wm.preferences' is outside of valid range

GLib-GIO-ERROR **: Settings schema 'org.gnome.Epiphany' does not contain a key named 'homepage-url'
"

GdkPixbuf-WARNING **: Bug! gdk-pixbuf loader 'png12' didn't set an error on failure.

** ERROR **: Resources.vala:806: Failed to load image '/usr/share/shotwell/icons/redeye.png': reason not known, probably a corrupt image file
Trace/breakpoint trap
Comment 1 Manuel Hiebel 2012-01-18 22:33:49 CET
Know bug iirc, but not reported yet in the bugzilla

CC: (none) => jani.valimaa, mageia, olav

Comment 2 Marja Van Waes 2012-01-19 16:06:17 CET
(In reply to comment #1)
> Know bug iirc, but not reported yet in the bugzilla

That means you confirm it... assigning to maintainer

CC: (none) => marja11
Assignee: bugsquad => mageia

Comment 3 Damien Lallement 2012-01-23 23:46:43 CET
I can't reproduce.
Are sure you are up-to-date Herbert?
Comment 4 Herbert Poetzl 2012-01-24 00:16:11 CET
how can I check?

# urpmi.update -a
medium "Core Release" is up-to-date
medium "Core Release Debug" is up-to-date
medium "Core Updates" is up-to-date
medium "Core Updates Debug" is up-to-date
medium "Core Updates Testing Debug" is up-to-date
medium "Core Backports Debug" is up-to-date
medium "Core Backports Testing Debug" is up-to-date
medium "Nonfree Release Debug" is up-to-date
medium "Nonfree Updates Debug" is up-to-date
medium "Core 32bit Release" is up-to-date
medium "Core 32bit Updates" is up-to-date

# urpmi --auto-select
Packages are up to date


$ shotwell
** Message: GSettingsEngine.vala:457: Error 5 running gsettings-data-convert: stdout="" stderr="
GLib-GIO-WARNING **: g_settings_set_value: value for key 'print-wrap-mode' in schema 'org.gnome.gedit.preferences.print' is outside of valid range

GLib-GIO-WARNING **: g_settings_set_value: value for key 'action-double-click-titlebar' in schema 'org.gnome.desktop.wm.preferences' is outside of valid range

GLib-GIO-ERROR **: Settings schema 'org.gnome.Epiphany' does not contain a key named 'homepage-url'
"

GdkPixbuf-WARNING **: Bug! gdk-pixbuf loader 'png12' didn't set an error on failure.

** ERROR **: Resources.vala:806: Failed to load image '/usr/share/shotwell/icons/redeye.png': reason not known, probably a corrupt image file
Trace/breakpoint trap
Comment 5 Damien Lallement 2012-01-24 11:48:17 CET
Are you really in Mageia Cauldron?
You told about Mageia 1 in Bug #4184...
Comment 6 Jani Välimaa 2012-01-24 16:31:21 CET
(In reply to comment #3)
> I can't reproduce.

Me neither (on x86_64).
Comment 7 Manuel Hiebel 2012-01-24 16:36:22 CET
Hum I was sure I have see this issue one day on the bugzilla, 

can you remove lib64gdk_pixbuf2.0_0-loaders-png12 then install lib64gdk_pixbuf2.0_0-loaders-png15 ?
Comment 8 Herbert Poetzl 2012-01-24 16:38:09 CET
_this_ is Bug #4184, you probably mean Bug #2937, but to answer your question:
Yes, I am in Mageia Cauldron AFAIK ...

# cat /etc/mageia-release 
Mageia release 2 (Cauldron) for x86_64

believe it or not, I have more than one system and on Mageia 1 shotwell starts, but doesn't see at least one of my cameras (Olympus C4040-Zoom)

note: this system was updated from Mageia 1, maybe that's the problem here?
Comment 9 Jani Välimaa 2012-01-24 16:38:24 CET
Actually I can reproduce this with lib64gdk_pixbuf2.0_0-loaders-png12.

But when using lib64gdk_pixbuf2.0_0-loaders-png15, it works.
Comment 10 Herbert Poetzl 2012-01-24 16:44:20 CET
(In reply to comment #7)
> Hum I was sure I have see this issue one day on the bugzilla, 

> can you remove lib64gdk_pixbuf2.0_0-loaders-png12 then install
> lib64gdk_pixbuf2.0_0-loaders-png15 ?

\o/ good catch!

I didn't remove lib64gdk_pixbuf2.0_0-loaders-png12 because it seems to be required by lsb-lib64-4.1-10.mga2.x86_64, which in turn is required to install google-chrome-stable, but _adding_ lib64gdk_pixbuf2.0_0-loaders-png15 makes shotwell run, so I'll test in a few minutes with the cameras ...

so, conclusion: shotwell should depend on the *-png15 package
Comment 11 Manuel Hiebel 2012-01-24 16:47:32 CET
So we have a big issue here, do we need to ping the -dev ml to ask for check that ?
Comment 12 Manuel Hiebel 2012-01-24 17:26:26 CET
in fact it should be good

line 35
http://svnweb.mageia.org/packages/cauldron/meta-task/current/SOURCES/prefer.vendor.list?revision=196531&view=markup

So I don't see why you have the png12
Comment 13 Herbert Poetzl 2012-01-24 17:52:44 CET
probably because of:

# rpm -q --requires lsb-lib64 | grep png 
lib64gdk_pixbuf2.0_0-loaders-png12  
lib64png12_0
Comment 14 Nicolas Lécureuil 2012-02-17 01:50:59 CET
here in my i586 i have 

libgdk_pixbuf2.0_0-loaders-png12  
libpng12_0

and it still works.

CC: (none) => nicolas.lecureuil

Comment 15 Nicolas Lécureuil 2012-02-17 01:56:36 CET
$ urpmq --requires-recursive  shotwell | grep png
lib64gdk_pixbuf2.0_0-loaders-png12|lib64gdk_pixbuf2.0_0-loaders-png15
lib64png15_15


so maybe urpmi installed only libgdk_pixbuf2.0_0-loaders-png12 instead of lib64gdk_pixbuf2.0_0-loaders-png15


was lib64gdk_pixbuf2.0_0-loaders-png15 installed on your machine ? or only lib64gdk_pixbuf2.0_0-loaders-png12
Comment 16 Herbert Poetzl 2012-02-29 08:44:45 CET
problem gone with recent cauldron, there are a bunch of errors reported when 
lib*gdk_pixbuf2.0_0-loaders-png12* is installed but shotwell starts fine.


GdkPixbuf-WARNING **: Bug! loader 'png12' didn't set an error on failure
GdkPixbuf-WARNING **: Bug! gdk-pixbuf loader 'png12' didn't set an error on failure.
GdkPixbuf-WARNING **: Bug! gdk-pixbuf loader 'png12' didn't set an error on failure.
Gtk-CRITICAL **: gtk_icon_set_render_icon_pixbuf: assertion `icon_set != NULL' failed
...

Status: NEW => RESOLVED
CC: (none) => herbert
Resolution: (none) => FIXED