shotwell crashed with signal 5 in page_init_load_ui()

Bug #626091 reported by Roland Dreier
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Shotwell
Fix Released
Unknown
shotwell (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: shotwell

When starting shotwell (with a fairly large library of imported images, not sure if that matters), it prints a bunch of:

`menu_proxy_module_load': shotwell: undefined symbol: menu_proxy_module_load

(shotwell:19188): Gtk-WARNING **: Failed to load type module: (null)

`menu_proxy_module_load': shotwell: undefined symbol: menu_proxy_module_load

(shotwell:19188): Gtk-WARNING **: Failed to load type module: (null)

and then finally crashes with:

** ERROR **: Page.vala:475: Error loading UI file /usr/share/shotwell/ui/import_queue.ui: Failed to open file '/usr/share/shotwell/ui/import_queue.ui': Too many open files
aborting...

Trace/breakpoint trap (core dumped)

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: shotwell 0.7.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.35-19.26-generic 2.6.35.3
Uname: Linux 2.6.35-19-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Sat Aug 28 18:50:49 2010
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/shotwell
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
ProcCmdline: shotwell
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
Signal: 5
SourcePackage: shotwell
StacktraceTop:
 page_init_load_ui ()
 page_init_ui_start ()
 page_init_ui ()
 import_queue_page_construct ()
 library_window_construct ()
Title: shotwell crashed with signal 5 in page_init_load_ui()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Roland Dreier (roland.dreier) wrote :
Revision history for this message
Roland Dreier (roland.dreier) wrote :

By the way, the crash does not happen every time -- I am usually able to start shotwell fine, and once it starts it's quite stable.

Revision history for this message
Roland Dreier (roland.dreier) wrote :

This bug is still there -- just got this crash with shotwell 0.7.1-0ubuntu2 today.

visibility: private → public
Revision history for this message
Adam Dingle (adam-yorba) wrote :

Roland,

the symbol menu_proxy_module_load, which is showing up in the crash report, seems to be part of the appmenu-gtk package, which is part of Ubuntu's global menu implementation (see https://wiki.ubuntu.com/DesktopExperienceTeam/ApplicationMenu). Have you installed appmenu-gtk, from a PPA or otherwise? If so, what version of it are you running?

Revision history for this message
Roland Dreier (roland.dreier) wrote :

No, I don't have appmenu-gtk installed.

Just to be clear, I don't think the menu_proxy_module_load warnings are related to this crash anyway. It seems that pretty much all gtk applications print a bunch of those warnings with current maverick. (I just tried eog, gnomine and gnome-help and they all print the warnings)

Revision history for this message
Adam Dingle (adam-yorba) wrote :

Oh - you're running Maverick? I thought you were on Lucid since the crash report above contains this line:

InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)

It would be nice to know how many files and subdirectories exist under your library folder - that might be relevant here. When Shotwell starts up, it scans your library to see if any files are missing, and it looks like it's opening too many files in the process. In a terminal window, could you cd to the root of your photo library, and then run the following commands?

$ find . | wc
$ find . -type d | wc
$ du -s .

If you could post the output of these commands here that would be great - thanks!

Revision history for this message
Roland Dreier (roland.dreier) wrote :

Yes, I'm on Maverick. Not sure where apport got that InstallationMedia from since I definitely installed from a Maverick daily ISO, but I guess that doesn't matter. Anyway, I have a fair number of files and directories (I use a date-based scheme for saving my photos, so everything is in a directory tree with names like 2010/09/02/IMG_xxxx.JPG):

$ find Pictures/|wc
  17741 17964 833171
$ find Pictures/ -type d|wc
   1328 1329 44687
$ du -s Pictures/
94794340 Pictures/

Revision history for this message
Jim Nelson (yorba-jim) wrote :

This is on our Trac server at http://trac.yorba.org/ticket/2510

Omer Akram (om26er)
Changed in shotwell (Ubuntu):
importance: Undecided → Medium
status: New → Triaged
Changed in shotwell:
status: Unknown → Confirmed
Revision history for this message
Jim Nelson (yorba-jim) wrote :

I've committed a patch to our branch that I believe solves this problem. Roland, is it possible for you to compile and run it to verify the fix?

You would need to have Vala 0.9.5 or better installed (get it from http://live.gnome.org/Vala/Release). Then pull from our Subversion branch:

$ svn co svn://svn.yorba.org/shotwell/branches/shotwell-0.7

You may also need to install build dependencies. Instructions for that are at http://www.yorba.org/shotwell/install/#source

If you have any questions, please feel free to ask.

Thanks!

Revision history for this message
Roland Dreier (roland.dreier) wrote :

Yes, that appears to have fixed it. I haven't been able to duplicate the crash when I built that branch from source.

Revision history for this message
Jim Nelson (yorba-jim) wrote :

Thanks! I'm going to close the ticket on our end.

Changed in shotwell:
status: Confirmed → Fix Released
Changed in shotwell:
status: Fix Released → Unknown
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
ThreadStacktrace:

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Changed in shotwell (Ubuntu):
status: Triaged → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed
Download full text (3.5 KiB)

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1: installed version 1:4.5.1-2ubuntu2, latest version: 1:4.5.1-7ubuntu1
libavahi-common3: installed version 0.6.27-2ubuntu1, latest version: 0.6.27-2ubuntu3
mountall: installed version 2.16, latest version: 2.17
libudev0: installed version 161+git20100825-1, latest version: 162-1
libgstreamer-plugins-base0.10-0: installed version 0.10.30-1build1, latest version: 0.10.30-2
libcups2: installed version 1.4.4-3, latest version: 1.4.4-4
libwebkit-1.0-2: installed version 1.2.3-2ubuntu1, latest version: 1.2.4-1ubuntu1
libplymouth2: installed version 0.8.2-2ubuntu3, latest version: 0.8.2-2ubuntu4
libgtk2.0-common: installed version 2.21.6-1ubuntu2, latest version: 2.21.7-1ubuntu1
klibc-utils: installed version 1.5.18-1, latest version: 1.5.20-1
libglib2.0-0: installed version 2.25.14-1ubuntu2, latest version: 2.25.15-0ubuntu2
libgdk-pixbuf2.0-0: installed version 2.21.6-2ubuntu5, latest version: 2.21.7-1ubuntu3
gcc-4.5-base: installed version 4.5.1-2ubuntu2, latest version: 4.5.1-7ubuntu1
libgail18: installed version 2.21.6-1ubuntu3, latest version: 2.21.7-1ubuntu1
libklibc: installed version 1.5.18-1, latest version: 1.5.20-1
cpp-4.4: installed version 4.4.4-9ubuntu2, latest version: 4.4.4-14ubuntu4
libc-bin: installed version 2.12.1-0ubuntu1, latest version: 2.12.1-0ubuntu6
libcairo2: installed version 1.9.14-1ubuntu1, latest version: 1.10.0-1ubuntu1
libfreetype6: installed version 2.4.2-1, latest version: 2.4.2-2
passwd: installed version 1:4.1.4.2-1ubuntu2, latest version: 1:4.1.4.2-1ubuntu3
dpkg: installed version 1.15.8.4ubuntu2, latest version: 1.15.8.4ubuntu3
gcc-4.4-base: installed version 4.4.4-9ubuntu2, latest version: 4.4.4-14ubuntu4
udev: installed version 161+git20100825-1, latest version: 162-1
ifupdown: installed version 0.6.10ubuntu2, latest version: 0.6.10ubuntu3
libxslt1.1: installed version 1.1.26-1ubuntu1, latest version: 1.1.26-6
libpixman-1-0: installed version 0.18.2-1ubuntu1, latest version: 0.18.4-1
initramfs-tools: installed version 0.98ubuntu2, latest version: 0.98.1ubuntu3
libstdc++6: installed version 4.5.1-2ubuntu2, latest version: 4.5.1-7ubuntu1
libwebkit-1.0-common: installed version 1.2.3-2ubuntu1, latest version: 1.2.4-1ubuntu1
libavahi-common-data: installed version 0.6.27-2ubuntu1, latest version: 0.6.27-2ubuntu3
libc6: installed version 2.12.1-0ubuntu1, latest version: 2.12.1-0ubuntu6
libsoup2.4-1: installed version 2.31.90-0ubuntu1, latest version: 2.31.92-0ubuntu1
libgtk2.0-0: installed version 2.21.6-1ubuntu3, latest version: 2.21.7-1ubuntu1
shotwell: installed version 0.7.0-0ubuntu1, latest version: 0.7.2-0ubuntu1
libavahi-client3: installed version 0.6.27-2ubuntu1, latest version: 0.6.27-2ubuntu3
libsqlite3-0: installed version 3.7.0.1-1, latest version: 3.7.2-1
initramfs-tools-bin: installed version 0.98ubuntu2, latest version: 0.98.1ubuntu3
plymouth: installed version 0.8.2-2ubuntu3, latest version: 0.8.2-2ubuntu4
gconf2-...

Read more...

tags: removed: need-amd64-retrace
Changed in shotwell:
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.