nautilus/gmobilemedia issue: nautilus crashed with SIGSEGV in nautilus_marshal_VOID__STRING_STRING_ENUM_INT_INT()

Bug #241568 reported by Gergely Janossy
40
Affects Status Importance Assigned to Milestone
Nautilus
Fix Released
High
nautilus (Ubuntu)
Fix Released
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: nautilus

Steps to reproduce:

1) Install gmobilemedia package (and wammu)
2) Connect my Sony Ericsson K300i
3) Start gmobilemedia
4) Toolbar-->“Connect” which connects to my cellphone
5) navigate to a Pictures directory
6) Click on a picture (in the background, the picture is downloaded into the ~/.gmobilemedia/cache directory)
7) Drag the picture from the gmobilemedia window in the ~/ nautilus window
8) Nautilus crashes.

Although there are some errors in gmobilemedia-error-log.txt, it is able to list the directory of my phone and download files from it (to its cache directory), so I don’t think it’s a gmobilemedia bug. Gmobilemedia does not crash, only nautilus.

ProblemType: Crash
Architecture: i386
Date: Fri Jun 20 10:30:17 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/nautilus
Package: nautilus 1:2.22.3-0ubuntu2
PackageArchitecture: i386
ProcCmdline: nautilus --no-default-window --sm-client-id default2
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/home/username/bin
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 nautilus_marshal_VOID__STRING_STRING_ENUM_INT_INT ()
Title: nautilus crashed with SIGSEGV in nautilus_marshal_VOID__STRING_STRING_ENUM_INT_INT()
Uname: Linux 2.6.24-19-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

Revision history for this message
Gergely Janossy (marcabru) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:?? ()
?? ()
?? ()
?? ()
nautilus_marshal_VOID__STRING_STRING_ENUM_INT_INT ()

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus:
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Gergely Janossy (marcabru) wrote :

Added backtrace. (Sorry if incorrect.)

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks Gergely, may you please install the libglib2.0-0-dbgsym, libgtk2.0-0-dbgsym and get a new one, the one you submitted is missing some symbols, thanks in advance!.

Revision history for this message
Gergely Janossy (marcabru) wrote :

Added a backtrace now with nautilus, libglib2.0 and libgtk2.0 symbols included. I promise next time I will be smarter...

Revision history for this message
Pedro Villavicencio (pedro) wrote :

thanks for your report, that's known upstream you can track it here: http://bugzilla.gnome.org/show_bug.cgi?id=539780

Changed in nautilus:
assignee: nobody → desktop-bugs
status: Incomplete → Triaged
Changed in nautilus:
status: Unknown → New
Changed in nautilus:
status: New → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has been fixed upstream now

Changed in nautilus:
status: Triaged → Fix Committed
Revision history for this message
Sebastien Bacher (seb128) wrote :

the new version is in intrepid now

Changed in nautilus:
status: Fix Committed → Fix Released
Revision history for this message
goto (gotolaunchpad) wrote :

Is this fixed in Hardy? I think I found a similar (the same?) bug on a up2date hardy system. Bug #272529

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

bugmenot - this is fixed in Intrepid. I'm not sure it is fixed in Hardy though.

Revision history for this message
goto (gotolaunchpad) wrote :

Hm, okay, thanks for your answer. How are such bugs treated actually in ubuntu? Could one say they are generally only fixed in the next release (in this case intrepid) or for the current release, too?

Or: Should I be quite if I found a bug in Hardy that is fixed in Intrepid but gets on my nerves?

Revision history for this message
Chris Coulson (chrisccoulson) wrote :

bugmenot - You should find your answer at https://wiki.ubuntu.com/StableReleaseUpdates

Revision history for this message
goto (gotolaunchpad) wrote :

Thank you so much! :)

Changed in nautilus:
importance: Unknown → High
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.