gedit crashed with SIGSEGV in g_main_context_dispatch()

Bug #1159287 reported by Felix Möller
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gedit (Ubuntu)
New
Undecided
Unassigned

Bug Description

editing a file with gedit on a gvfs-ftp share.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: gedit 3.6.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Sun Mar 24 01:47:49 2013
ExecutablePath: /usr/bin/gedit
InstallationDate: Installed on 2012-03-31 (357 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120331)
MarkForUpload: True
ProcCmdline: gedit /home/username/.gvfs/ftp:host=www.privatvermietung-kiel.de,user=297429-ftp/webseiten/drupal-7.21/sites/all/modules/imagefilter/imagefilter.module
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x440a48: mov 0x10(%rax),%rdi
 PC (0x00440a48) ok
 source "0x10(%rax)" (0xaaaaaaaaaaaaaaba) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: gedit
StacktraceTop:
 ?? ()
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 gtk_main () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: gedit crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to raring on 2013-01-23 (59 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Felix Möller (felix-derklecks) wrote :
description: updated
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 this software better. This particular crash has already been reported and is a duplicate of bug #1036621, 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.

information type: Private → Public
tags: removed: need-amd64-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.