nautilus crashed with SIGSEGV in g_timer_stop()

Bug #808105 reported by Dmitry
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

plugged IPhone into latop and gone for another cup of tea =))) Never liked iphones....

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.3-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic i686
Architecture: i386
CrashCounter: 1
Date: Sat Jul 9 23:21:52 2011
ExecutablePath: /usr/bin/nautilus
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: nautilus -n
ProcEnviron:
 LANGUAGE=ru_RU:en
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 LC_MESSAGES=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x38db6e <g_timer_stop+30>: andb $0xfe,0x10(%esi)
 PC (0x0038db6e) ok
 source "$0xfe" ok
 destination "0x10(%esi)" (0xaaaaaaba) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: nautilus
StacktraceTop:
 g_timer_stop () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/libgtk-3.so.0
 ?? () from /usr/lib/libgdk-3.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: nautilus crashed with SIGSEGV in g_timer_stop()
UpgradeStatus: Upgraded to oneiric on 2011-07-04 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Dmitry (musickiller) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #804891, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
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.