digiwf terminates with SIGSEV and SIGABRT

Bug #571664 reported by André Barmasse
20
This bug affects 3 people
Affects Status Importance Assigned to Milestone
DigiWf
New
Critical
Stefaan Vanderheyden

Bug Description

Hello Stefaan

If your tool works with writing XMP correctly to one image or a folder full of images (or maybe other data as well), then it will be one of the hottest nautilus extension available. And it is much needed, because XMP for me seems to be the future of metadata, as it has all advantages of XML, wich is openly readable and with the help of its tags also easy accessible with (for example) PHP. I always hated my friends working with Lightroom and editing XMP metadata with an incredible easyness.

For the moment digiwf crashed with Lucid Lynx RC with the following informations. I have attached a full report taken with strace to this bug report.

/usr/lib/ruby/1.8/i486-linux/gtkmozembed.so: [BUG] Segmentation fault
ruby 1.8.7 (2010-01-10 patchlevel 249) [i486-linux]

Please keep up the excellent work on this project. If I can help you with a german translation, please let me know.
Best wishes! André

Revision history for this message
André Barmasse (barmassus) wrote :
Revision history for this message
Stefaan Vanderheyden (svd) wrote :

Dear André,

I haven't tested DigiWf on Lucid yet.

I'll be releasing an updated version for Ubuntu's latest & greatest.

BR,

Stefaan

Changed in digiwf:
importance: Undecided → Critical
assignee: nobody → Stefaan Vanderheyden (svd)
milestone: none → 0.4.1
Revision history for this message
Stefaan Vanderheyden (svd) wrote :

Hello André,

I have updated my PPA with a release for Lucid Lynx.

It seems to be working fine on my PC.

Could you please check that your /etc/apt/sources.list points to my Lucid PPA and check if you still get the error with the latest version?

Thanks,

Stefaan

Revision history for this message
André Barmasse (barmassus) wrote :

Hello Stefaan

Same situation as before: With a right click on an image the option "Edit metadata" appears, but if I select it nothing happens. "Stracing" digiwf produces again a segmentation fault (see below). I have added your PPA to my apt sources list, but there was the same digiwf version (0.3.3-0ubuntu1) in it as in the deb packet available for download (released on 2009-05-07). Is this correct? Or should there be a newer version?

Keep up the good work! André

---------------

--- SIGSEGV (Segmentation fault) @ 0 (0) ---
write(2, "/usr/lib/ruby/1.8/i486-linux/gtk"..., 45/usr/lib/ruby/1.8/i486-linux/gtkmozembed.so: ) = 45
write(2, "[BUG] ", 6[BUG] ) = 6
write(2, "Segmentation fault", 18Segmentation fault) = 18
write(2, "\nruby 1.8.7 (2010-01-10 patchlev"..., 54
ruby 1.8.7 (2010-01-10 patchlevel 249) [i486-linux]

) = 54
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
tgkill(2530, 2530, SIGABRT) = 0
--- SIGABRT (Aborted) @ 0 (0) ---
+++ killed by SIGABRT +++
Aborted

Revision history for this message
mausahid (maocobox-net) wrote :

hi, any more news for the problem at hand? thanks.

Revision history for this message
Stefaan Vanderheyden (svd) wrote :

So far I have been unable to reproduce this problem on my own system.

I will try with a fresh install to see if I can reproduce it.

Revision history for this message
André Barmasse (barmassus) wrote :

Hi Stefaan

Today I ugraded to Maverick Meerkat Alpha 2. I have uninstalled everything somehow connected with ruby form ubuntu and then freshly reinstalled the dep package 0.3.3 of digiwf. The old SIGSEV and SIGABRT have gone, but now the program terminates with another message:

/usr/lib/ruby/1.8/glib2.rb:71:in `require': no such file to load -- glib2.so (LoadError)
 from /usr/lib/ruby/1.8/glib2.rb:71
 from /usr/lib/ruby/1.8/gtk2/base.rb:11:in `require'
 from /usr/lib/ruby/1.8/gtk2/base.rb:11
 from /usr/lib/ruby/1.8/gtk2.rb:10:in `require'
 from /usr/lib/ruby/1.8/gtk2.rb:10
 from /usr/lib/ruby/1.8/libglade2.rb:8:in `require'
 from /usr/lib/ruby/1.8/libglade2.rb:8
 from /usr/bin/digiwf:26:in `require'
 from /usr/bin/digiwf:26

The library glib2.so exists - not in /usr/lib/ruby/1.8/ but in /usr/lib/ruby/1.8/i486-linux/. I can now put an symbolic link to the i486-linux folder (sudo ln -s /usr/lib/ruby/1.8/i486-linux/glib2.so /usr/lib/ruby/1.8/), but after that more broken paths are popping up (atk.so pango.so etc.) every time I try to start digiwf from the console. In nautilus the option "Edit metadata" appears, but selecting it does nothing.

I hope you can solve this ugly ruby problems! André

Revision history for this message
sv (shawnboy) wrote :

This effect me too. I thought I had finally found the GUI tagging front-end I've been looking for so long. It worked ok in Ubuntu 9.10 64-bit but I get this error on my Ubuntu 10.04 32-bit system. I hope you keep working on this software. It is much needed in the Linux world.

Revision history for this message
Kari Haapanen (karsta62) wrote :

I agree sv. So close to a MUCH needed tool, but...

I'm having this problem on my Ubuntu 10.10 32bit:

# digiwf -d
/usr/lib/ruby/1.8/i686-linux/gtkmozembed.so: [BUG] Segmentation fault
ruby 1.8.7 (2010-06-23 patchlevel 299) [i686-linux]

Aborted

Revision history for this message
Kari Haapanen (karsta62) wrote :

As well as in Linux Mint 11 32bit. Same version of ruby.

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

Duplicates of this bug

Other bug subscribers

Bug attachments

Remote bug watches

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