Ubuntu
bluefish package

bluefish crashed with SIGSEGV in file_checkNsave_cancel()

Bug #858992 reported by mrDoctorWho
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Bluefish
Fix Released
Medium
bluefish (Fedora)
Fix Released
Undecided
bluefish (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

when i minimize it

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: bluefish 2.0.3-1ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.23-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Sun Sep 25 22:41:45 2011
ExecutablePath: /usr/bin/bluefish
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.3)
ProcCmdline: bluefish /media/092b04cf-bd56-4fb7-b222-eaae1d088b9e/home/username/Рабочий\ стол/simpleapps
ProcEnviron:
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x808dae4 <file_checkNsave_cancel+4>: mov 0xc(%eax),%eax
 PC (0x0808dae4) ok
 source "0xc(%eax)" (0x0000000c) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: bluefish
StacktraceTop:
 file_checkNsave_cancel ()
 remove_autosave ()
 doc_set_modified ()
 ?? ()
 ?? ()
Title: bluefish crashed with SIGSEGV in file_checkNsave_cancel()
UpgradeStatus: Upgraded to oneiric on 2011-09-24 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
In , Stéphane (stphane-redhat-bugs) wrote :

abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 14063 bytes
cmdline: bluefish
component: bluefish
Attached file: coredump, 26193920 bytes
crash_function: file_checkNsave_cancel
executable: /usr/bin/bluefish
kernel: 2.6.35.11-83.fc14.x86_64
package: bluefish-2.0.3-2.fc14
rating: 4
reason: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299683340
uid: 500

How to reproduce
-----
1.fermeture de l'application
2.
3.

Revision history for this message
In , Stéphane (stphane-redhat-bugs) wrote :

Created attachment 483236
File: backtrace

Revision history for this message
In , Jim (jim-redhat-bugs) wrote :

Created attachment 483341
Patch

Patch is attached for a change made upstream to workaround the bug. This does not fix the root issue which appears to be that an autosave is being cancelled that isn't running.

The problem appears to randomly happen only when closing Bluefish.

Revision history for this message
In , Paul (paul-redhat-bugs) wrote :

There are a number of autosave/closing bugs from 2.0.2 that might be related or provide some clues perhaps?

* Bug #678737
* Bug #675377
* Bug #670000
* Bug #668784
* Bug #658468
* Bug #648096

I'll prepare an update with the workaround in the meantime.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

bluefish-2.0.3-3.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/bluefish-2.0.3-3.fc15

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

bluefish-2.0.3-3.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/bluefish-2.0.3-3.fc14

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

bluefish-2.0.3-3.el6 has been submitted as an update for Fedora EPEL 6.
https://admin.fedoraproject.org/updates/bluefish-2.0.3-3.el6

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

bluefish-2.0.3-3.fc13 has been submitted as an update for Fedora 13.
https://admin.fedoraproject.org/updates/bluefish-2.0.3-3.fc13

Revision history for this message
In , Jim (jim-redhat-bugs) wrote :

(In reply to comment #3)

> * Bug #678737

Appears to be a different bug. Don't recall ever seeing that specific backtrace. Appears to be a bug never reported upstream.

> * Bug #675377

Should that be #675357? Doesn't appear to be autosave related. Appears to be a bug never reported upstream.

> * Bug #670000

This is an autosave bug. This should be fixed with 2.0.3.

> * Bug #668784

Appears to be the same bug as #678737

> * Bug #658468

This should be fixed with 2.0.3.

> * Bug #648096

Appears to be that same bug as Bug #658468. Should be fixed with 2.0.3.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

bluefish-2.0.3-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , Paul (paul-redhat-bugs) wrote :

*** Bug 688061 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Paul (paul-redhat-bugs) wrote :

*** Bug 689084 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

bluefish-2.0.3-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

bluefish-2.0.3-3.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

bluefish-2.0.3-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
mrDoctorWho (mrdoctorwho) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in bluefish (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel Leidert (dleidert-deactivatedaccount) wrote :

Possible fix will be in bluefish 2.2.0

Changed in bluefish (Ubuntu):
status: Confirmed → In Progress
Bug Watch Updater (bug-watch-updater)
Changed in bluefish:
importance: Unknown → Medium
status: Unknown → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package bluefish - 2.2.0-2ubuntu1

---------------
bluefish (2.2.0-2ubuntu1) precise; urgency=low

  * Merge from Debian unstable.
  * Enable LP810663_blacklist_from_appmenu.patch.

bluefish (2.2.0-2) unstable; urgency=low

  * debian/control (bluefish-dbg/Suggests): Replace libgtk2.0-0-dbg by
    libgtk-3-0-dbg.

bluefish (2.2.0-1) unstable; urgency=low

  * New upstream release (closes: #623122; LP: #858992).
  * Acknowledge NMU (closes: #643737).
  * debian/compat: Increased dh compatibility level to 7.
  * debian/control (Standards-Version): Bumped to 3.9.2.
    (Build-Depends): Replaced libgtk2.0-dev, libgucharmap2-dev and
    libgucharmap-dev by libgtk-3-dev and libgucharmap-2-90-dev. Increased
    required debhelper version.
    (Conflicts): Changed to Breaks to fix conflicts-with-version.
  * debian/copyright: Minor update.
  * debian/rules: Rewritten for debhelper 7.
  * debian/watch: Added support for .bz2 suffix.
  * debian/source/format: Added for format 3.0 (quilt).
  * debian/patches/LP810663_blacklist_from_appmenu.patch: Added for Ubuntu.
  * debian/patches/series: Added empty.

bluefish (2.0.3-1.1) unstable; urgency=low

  * Non-maintainer upload, for the GNOME 3 transition.
  * Disable charmap plugin, as the GTK+ 2.0 version of libgucharmap7 is
    going away and loading GTK+ 2.0 and 3.0 in the same process is not
    allowed (closes: #643737).
  * Move Build-Depends on libgucharmap2-dev to Build-Conflicts as there
    isn't a configure switch to disable the plugin.
 -- Felix Geyer <email address hidden> Fri, 25 Nov 2011 17:56:53 +0100

Changed in bluefish (Ubuntu):
status: In Progress → Fix Released
Bug Watch Updater (bug-watch-updater)
Changed in bluefish (Fedora):
importance: Unknown → Undecided
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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