GNOME Bugzilla – Bug 738245
Shotwell crashes on startup (crash in g_type_create_instance)
Last modified: 2017-02-08 11:35:08 UTC
Shotwell tries to find new files and crashes then. If I click on don't monitor new files in the setting dialog, it doesn't crash any more.
Created attachment 288146 [details] gdb backtrace
Could you try removing the gstreamer-0.10-good package and trying again? http://kaosx.us/phpBB3/viewtopic.php?f=10&t=358
Removing gstreamer-0.10-good package on arch linux didn't work. However, it crashed complaining about the file /usr/lib/gstreamer-1.0/libgstavi.so, which belongs to gst-plugins-good. Removing gst-plugins-good solves the problem. However, it also removes totem, gnome-contacts, etc.
I feel like I need to hand this off to the GStreamer guys. It sounds like gst-plugins-good is doing something at initialization time causing a crash in GType.
"VideoImportParams" is not defined by GStreamer anywhere but by shotwell in src/VideoSupport.vala. That warning would be a bug in shotwell or vala and is completely unrelated to GStreamer. The backtrace here also contains nothing at all about GStreamer. You say that there was another crash when you removed the GStreamer 1.x AVI plugin. Can you provide a new backtrace for that?
It works now on Arch Linux with gst-plugins-good installed since they rebuilt the package so I can't test it anymore. After removing the gst-plugins-good package it worked on Arch. Then I upgraded and gnome 3.14.1 was installed. Shotwell didn't work any more. Then they rebuilt the shotwell package and it works now again even with gst-plugins-good installed. https://bugs.archlinux.org/task/42473 https://bugs.archlinux.org/task/42460
Thanks for testing and confirming it's no longer an issue.
Created attachment 289288 [details] gdb backtrace
It crashes again after adding new photos...
Could you please install debugging symbols for libglib, libgstreamer, gst-plugins-base and gst-plugins-good? (There should be -dbg packages on debian/ubuntu), and then make a new stack trace? I also note that there are quite a few other non-gstreamer criticals before this.
Ah, wait, sorry. I was confusing the GType init error with something we've seen in the past related to GStreamer at initialization. It may be two different problems here. The first trace appears to be from a fundamental type being registered twice in Shotwell. It's probably a thread safety issue. The second trace tudor submitted looks like something entirely different. Regarding the critical GdkPixbuf warnings in the second trace, those are coming off the Shotwell video thumbnailer, a process spawned for each video imported, and so the main process' state is unaffected by those warnings. I'll look into the warnings. Tim, if you agree, we can break these out into two tickets.
Sure, and there's clearly a problem in avidemux as well, it's just that we need a stack trace to get a better idea what the issue might be.
Ok, I'm converting this back to a Shotwell bug. The new bug report (w/ originals stack trace) is at bug #739146. tudor, please install the debug symbols Tim-Philipp requested and post a new stack trace there. This ticket is for the original crash you reported, which is a GType initialization bug.
tudor, what version of Shotwell are you running?
Which packages would this be on Arch Linux for the debugging symbols? I have the latest package of shotwell.
I couldn't tell you the Arch Linux package names. On Debian/Ubuntu it's shotwell-dbg. I would think Arch would use a similar naming scheme.
Arch has no debug packages, you'll have to rebuild the relevant packages yourself. See https://wiki.archlinux.org/index.php/Debug_-_Getting_Traces
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!