Bug 853599 - links are not completed to a note if a shorter title exists
Summary: links are not completed to a note if a shorter title exists
Keywords:
Status: ASSIGNED
Alias: None
Product: Fedora
Classification: Fedora
Component: tomboy
Version: rawhide
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Thomas Moschny
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-01 06:34 UTC by Sridhar Dhanapalan
Modified: 2013-11-11 10:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)
Image showing the results from the steps to reproduce (22.57 KB, image/jpeg)
2012-09-01 06:34 UTC, Sridhar Dhanapalan
no flags Details


Links
System ID Private Priority Status Summary Last Updated
GNOME Bugzilla 676649 0 None None None 2012-09-01 06:44:02 UTC
Launchpad 886742 0 None None None 2012-09-01 06:34:33 UTC

Description Sridhar Dhanapalan 2012-09-01 06:34:32 UTC
Created attachment 608768 [details]
Image showing the results from the steps to reproduce

Description of problem:
Connot make a link to a note if another note exists that has a shorter version of the same title.


Version-Release number of selected component:
tomboy-1.10.2-1.fc17.x86_64


How reproducible:
Always


Steps to Reproduce:
  1. create a new note, titled "testing new note"
  2. create a new note, titled "testing new note 2"
  3. in a new/existing note, try to create a link to the two newly-created notes, by typing their names


Actual results:
Two links are made to the "testing new note" note. The "2" is ignored.


Expected results:
Links are made to both notes


Problem also exists on:
Ubuntu 12.04 (Tomboy 1.10.1-0ubuntu1)
Ubuntu 11.10 (Tomboy 1.8.0)


This is not a problem on:
Fedora 14 (Tomboy 1.6.1)
Ubuntu 10.10

Comment 1 Thomas Moschny 2013-04-10 18:04:13 UTC
Thanks for reporting. I can reproduce the problem on F18.

We can track the issue here, however it has to be fixed upstream.


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