impossible to open the preferences (crash)

Bug #318146 reported by Cedynamix
10
Affects Status Importance Assigned to Milestone
Déjà Dup
Fix Released
Critical
Michael Terry

Bug Description

impossible to open the preferences (crash)

Revision history for this message
Cedynamix (cedynamix) wrote :
Revision history for this message
Michael Terry (mterry) wrote :

Thank you for the bug report! I'm not seeing it over here, so I'd like a little bit more information to track this down. First, what version of deja-dup (can see by running 'deja-dup --version')?

Second, could you please do the following?
1. sudo apt-get install deja-dup-dbg # (if on Ubuntu, else recompile deja-dup with the --enable-debug flag to configure)
2. gdb deja-dup-preferences
3. At the gdb prompt, type run:
(gdb) run
4. When the preferences dialog crashes, get a backtrace:
(gdb) bt
5. Post the result here.

Thanks for your help with this.

Changed in deja-dup:
status: New → Incomplete
importance: Undecided → Critical
Revision history for this message
Cedynamix (cedynamix) wrote :

Resultat:

#0 0x08052c30 in ?? ()
#1 0x094b9750 in ?? ()
#2 0x098ada38 in ?? ()
#3 0x00000001 in ?? ()
#4 0x00000003 in ?? ()
#5 0x00000008 in ?? ()
#6 0x00000009 in ?? ()
#7 0x00000005 in ?? ()
#8 0x00000004 in ?? ()
#9 0x00000003 in ?? ()
#10 0x00000003 in ?? ()
#11 0x00000003 in ?? ()
#12 0x0001c939 in ?? ()
#13 0x00000004 in ?? ()
#14 0x094e3800 in ?? ()
#15 0x094b6998 in ?? ()
#16 0x094b9750 in ?? ()
#17 0x094f39d8 in ?? ()
#18 0x094b9998 in ?? ()
#19 0x094b6ce0 in ?? ()
#20 0x094b9a08 in ?? ()
#21 0x094b9a78 in ?? ()
#22 0x094f3ad8 in ?? ()
#23 0x094b6d40 in ?? ()
#24 0x09898d40 in ?? ()
#25 0x097be250 in ?? ()
#26 0x09897ed0 in ?? ()
#27 0x098980a8 in ?? ()
#28 0x09898e40 in ?? ()
#29 0x094ff678 in ?? ()
#30 0x09898118 in ?? ()
#31 0x09898f40 in ?? ()
#32 0x094ff768 in ?? ()
#33 0x098ad9c8 in ?? ()
#34 0x098ada38 in ?? ()
#35 0x098af128 in ?? ()
#36 0xb7000678 in ?? () from /usr/lib/libgobject-2.0.so.0
#37 0x094baef0 in ?? ()
#38 0x094e36b8 in ?? ()
#39 0x00000033 in ?? ()
#40 0xb6f7b9c8 in ?? () from /usr/lib/libglib-2.0.so.0
#41 0x094e2980 in ?? ()
#42 0x00000000 in ?? ()

Revision history for this message
Michael Terry (mterry) wrote :

Thanks for the output! Unfortunately, that's wasn't as fruitful as I hoped.

Here's an idea. Can you run the following?

gconftool-2 --dump /apps/deja-dup > /tmp/deja-prefs.xml

Then upload /tmp/deja-prefs.xml to this bug? That would let me reproduce the same settings you have, and hopefully hit this bug. I can then investigate further why it crashes.

Revision history for this message
Cedynamix (cedynamix) wrote :

sorry for the response time :-)

Here is the file.

Revision history for this message
Michael Terry (mterry) wrote :

Well, thank you for all the help you've given so far, but I still can't reproduce the crash.

How did you get this copy of Deja Dup? From the PPA? Did you compile it yourself? Which version? Does the crash happen on 6.0?

Revision history for this message
Cedynamix (cedynamix) wrote :

Hello,

got the source of version 6.0 on launchpad and I have compiled myself for distribution Frugalware.

I used the following dependencies for the compilation:

depends = ( 'libgnomeui' 'libsm' 'popt' 'gnome-vfs'' openssl '' esd '' gail '' libart_lgpl '' unique '' atk '' pango '' libxau '' libxdmcp '' freetype2 '' libxdamage ' 'libxinerama' 'libxi' 'libxrandr' 'libXcursor' 'libnotify')
makedepends = ( 'gnome-doc-utils'' intltool '' valid ')

I do not think I forgot something because the compilation is going very well. Perhaps a problem version. If you have an idea I'm interested.

Thank you

Revision history for this message
Michael Terry (mterry) wrote :

I don't see anything obviously wrong with those depends (i.e. I don't see you depending on 'libbreak-my-build').

I can say that your preferences are exceedingly normal (you only seemed to change one setting -- how often to automatically backup). So that doesn't seem like you have an unexpected setup or odd input that deja-dup chokes on.

The backtrace you gave me doesn't have any symbols, which if you compiled with --enable-debug, indicates to me it's going way off the deep end. I'd expect to see at least some deja-dup symbols there. Instead it seems memory is very corrupted.

So I'm stumped. Without being able to reproduce this, I can't do much.

Maybe try turning gcc optimizations off? Is this on a non x86 architecture?

Revision history for this message
Michael Terry (mterry) wrote :

Confirmed by duplicate bug 355362. Still not sure what causes this...

Changed in deja-dup:
status: Incomplete → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

OK, I figured this out. The bug is that Deja Dup crashes if there is no gconf value for which backend to use. Normally, this is provided by the gconf schema. But I'm guessing that since you both were compiling this yourselves, somehow either you didn't install the gconf schema or you installed it to some place where it isn't being used.

Next version should fix this.

Michael Terry (mterry)
Changed in deja-dup:
assignee: nobody → Michael Terry (mterry)
status: Confirmed → Fix Committed
Revision history for this message
Michael Terry (mterry) wrote :

Fixed in 9.0. Thanks for both your help in tracking this down.

Changed in deja-dup:
status: Fix Committed → Fix Released
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

Remote bug watches

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