gtkpod crashed with SIGSEGV in tm_data_compare_func()

Bug #587544 reported by yamo
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gtkpod (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: gtkpod

Hi,
I had trouble with preferences, I cannot save the value witch have changed!

And after that gtkpod crashed!

I think this bug is different of Bug #537997

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gtkpod 0.99.14-2ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic x86_64
Architecture: amd64
Date: Sun May 30 16:52:03 2010
ExecutablePath: /usr/bin/gtkpod
ProcCmdline: gtkpod
ProcEnviron:
 PATH=(custom, user)
 LANG=fr_FR.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x445a1a <tm_data_compare_func+218>: sub 0x60(%rdx),%eax
 PC (0x00445a1a) ok
 source "0x60(%rdx)" (0x00000081) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gtkpod
StacktraceTop:
 tm_data_compare_func ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_sequence_sort_changed_iter ()
Title: gtkpod crashed with SIGSEGV in tm_data_compare_func()
UserGroups: adm admin cdrom dialout kqemu kvm lpadmin plugdev sambashare

Revision history for this message
yamo (stephane-gregoire) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 tm_data_compare_func (model=<value optimized out>,
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_sequence_sort_changed_iter ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gtkpod (Ubuntu):
status: New → Confirmed
Revision history for this message
markling (markling) wrote :

I appear to have the same problem.

gtkod would not allow me to <Quit> unless I saved changes. I had not done anything. I did not want to save changes.

gtkpod forced changes on my ipod library that I had not requested and I did not want it to make.

It happend like this:

1. ipod alread mounted
2. launch gtkpod
3. gtkpod asked me to choose which model of ipod i had
4. gtkpod did not have my model, so I closed the window
5. I selected <file / Quit>
6. gtkpod asked if I wanted to save my changes - 'quit without saving' was shaded out.
7. I did <Alt-W> to quite without saving anyway, and the save window went away, but gtkpod stayed open.
8. So I tried 5. again and the same thing (6. & 7.) happend.
9. So I pressed [x] to close the window without saving changes
10. gtkpod said something like: "Synchronzing"
11. My ipod said: "Synchronizing"
12. gtkpod said: "Duplicate detection / The following 25 duplicate tracks have been removed.", and it listed 25 tracks it claimed to have deleted from my ipod.
13. I thought, unlucky for me. I didn't ask anyone to delete any of my tunes of my ipod. I thought, I came here to put tunes on my ipod, not take them off. I thought, I'm not very happy about this.

Now gtkpod might have been doing me a favour if it really was removing duplicates. But I would rather have a choice. And be left to decide for myself if they are indeed duplicates. In any case, I don't want any automated file removal from my personal directories, thank you. Even if I did, I would not trust file deletion to a program that refused to go away quietly when I told it to.

Hope this helps.

Revision history for this message
markling (markling) wrote :

It generated a crash report. Have filed it. Step 6. - might have been <Save changes>. Makes no difference aside to perhaps the level of outrage you might feel about the non-authorised sync and file deletion thing.

Revision history for this message
markling (markling) wrote :

No, that last comment, should have said Step 9. - might have been <save changes>.

I can now confirm, having unwittingly gone through all this again, that step 9 was in fact:

9. So I pressed [x] to close the window without saving changes

And that gtkpod did in fact insist on the sync and file deletion despite this.

The second time, strangley it said it had again removed 25 duplicates. They look like the same duplicates it removed before.

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.