Bug 701172 - [abrt] gnote-0.7.3-4.fc14: gobj: Process /usr/bin/gnote was killed by signal 11 (SIGSEGV)
Summary: [abrt] gnote-0.7.3-4.fc14: gobj: Process /usr/bin/gnote was killed by signal ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnote
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Rahul Sundaram
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0290ab35394088fe93e58accf64...
: 657096 668741 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-01 19:29 UTC by rbz
Modified: 2012-08-16 14:37 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 14:37:52 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (35.84 KB, text/plain)
2011-05-01 19:29 UTC, rbz
no flags Details

Description rbz 2011-05-01 19:29:39 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 36699 bytes
cmdline: /usr/bin/gnote --panel-applet --oaf-activate-iid=OAFIID:GnoteApplet_Factory --oaf-ior-fd=25
component: gnote
Attached file: coredump, 24256512 bytes
crash_function: gobj
executable: /usr/bin/gnote
kernel: 2.6.35.12-90.fc14.x86_64
package: gnote-0.7.3-4.fc14
rating: 4
reason: Process /usr/bin/gnote was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1304278023
uid: 10000

How to reproduce
-----
1. edit a note
2. change its title (1st line)
3. answer yes or no to "update all notes" dialog

Comment 1 rbz 2011-05-01 19:29:43 UTC
Created attachment 496115 [details]
File: backtrace

Comment 2 robb 2011-05-01 19:51:43 UTC
FWIW, this occurred after the system had just been freshly (re-)booted, after the installation of some 53 updates (i.e. "yum update") on 1.5.2011. There was no update of of the gnote package itself, though some gnomey packages (and the kernel) were updated e.g.
> [rubicon 05.01 21:45:59]# grep yum /var/log/messages | grep -i gnome
> May  1 21:08:40 rubicon yum[12791]: Updated: wireshark-gnome-1.4.6-1.fc14.x86_64
> May  1 21:08:47 rubicon yum[12791]: Updated: 1:NetworkManager-gnome-0.8.4-1.fc14.x86_64
> May  1 21:09:13 rubicon yum[12791]: Updated: gnome-python2-extras-2.25.3-30.fc14.1.x86_64
> May  1 21:09:35 rubicon yum[12791]: Updated: gnome-python2-libegg-2.25.3-30.fc14.1.x86_64
> May  1 21:09:35 rubicon yum[12791]: Updated: gnome-python2-gtkhtml2-2.25.3-30.fc14.1.x86_64

> [rubicon 05.01 21:46:34]# rpm -qi gnote
> Name        : gnote                        Relocations: (not relocatable)
> Version     : 0.7.3                             Vendor: Fedora Project
> Release     : 4.fc14                        Build Date: Fri 17 Dec 2010 12:29:36 PM CET
> Install Date: Thu 20 Jan 2011 11:34:30 AM CET      Build Host: x86-14.phx2.fedoraproject.org

Although the crash count in abrt reached 3, after another restart of gnote it now seems to be functioning normally (wasn't brave enough yet to try renaming any more notes ;-))

Comment 3 freonmonkey 2011-05-11 01:58:38 UTC
Package: gnote-0.7.3-4.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Open a pre-existing note (I picked the "Start here" note)
2. Change the title of the note
3. Agree to rename all links when prompted


Comment
-----
This installation of Gnote shares notes with Tomboy from a different distribution. I have had no issues with reading or writing the notes between them so far.

Comment 4 Kenzi Hashimoto 2011-05-11 16:34:04 UTC
Package: gnote-0.7.3-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.make new title note.
2.it crashed
3.

Comment 5 Dylan Swift 2011-05-12 10:27:24 UTC
Package: gnote-0.7.3-4.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Renamed gnote
2. offered option of updating links in other notes, selected rename (ie yes)
3. around 20 seconds later - gnotes closes.


Comment
-----
Just renaming a gnote by prefixing the name with a string + _, ie diagrams to network_diagrams

Comment 6 Richard Schwarting 2011-05-19 07:22:45 UTC
Package: gnote-0.7.3-4.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. I renamed a note ":ToDo" to "MyToDo", multiple other notes linked to it
2. after renaming, I was prompted to update connections in other notes to this one, to reflect the name change
3. I chose yes


Comment
-----
It crashes semi-regularly on updating links for me.

Comment 7 ryans 2011-05-25 01:22:41 UTC
Package: gnote-0.7.3-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Open existing note from Gnote panel applet
2. rename note link
3. repeat


Comment
-----
Attempted to rename a link for an existing note using the Gnote panel applet.  This caused the applet to crash.  Choosing to recover note would loose all previous changes made to the note.

Comment 8 chessmarcosz 2011-08-10 12:23:11 UTC
Package: gnote-0.7.3-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.abri gnote
2. cort el texto completo incluyendo un vnculo
3.lo pegu en otra aplicacin quedando vaca la nota de Gnote


Comment
-----
1.abri gnote
2. cort el texto completo incluyendo un vnculo
3.lo pegu en otra aplicacin quedando vaca la nota de Gnote

Comment 9 bjass57 2011-08-15 09:57:40 UTC
Package: gnote-0.7.3-4.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.open a Gnote
2. edit its title
3. close and select 'Don't update links'


Comment
-----
Repeating the above will often cause the crash to repeat

Comment 10 Davide Repetto 2011-09-09 22:12:44 UTC
Package: gnote-0.7.3-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Gnote asked to rename references
answered YES

Comment 11 Wendell Baker 2011-12-22 22:01:26 UTC
Package: gnote-0.7.3-4.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. spontaneous?
2.
3.

Comment 12 abrt-bot 2012-03-30 14:12:31 UTC
*** Bug 657096 has been marked as a duplicate of this bug. ***

Comment 13 abrt-bot 2012-03-30 14:12:45 UTC
*** Bug 668741 has been marked as a duplicate of this bug. ***

Comment 14 Fedora End Of Life 2012-08-16 14:37:55 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.