Doesn't recognize hashtags with umlauts

Bug #464696 reported by Sebastian Wiesinger
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gwibber (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gwibber

Hello,

Gwibber is unable to detect #hashtags with umlauts in them (and probably other non-ascii chars).

To reproduce:

Search for #nürnberg with the integrated search. The hashtag in the results is recognized as "#n" instead of "#nürnberg"

ProblemType: Bug
Architecture: i386
Date: Fri Oct 30 13:08:56 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: gwibber 2.0.0~bzr476-0ubuntu3
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: gwibber
Uname: Linux 2.6.31-14-generic i686

Revision history for this message
Sebastian Wiesinger (sebastianw) wrote :
skep (skep)
Changed in gwibber (Ubuntu):
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

True, marking this as triaged, thanks for the report.

Changed in gwibber (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Revision history for this message
Richard Wecker (r1u2) wrote :

Is gwibber probably using the wrong language? My system is set to German but gwibber appears completely in English. LANGUAGE=en_US.UTF-8 Might this cause the bug?

Revision history for this message
Victor Vargas (kamus) wrote :

I tried to reproduce this issue using gwibber daily and works fine for me (I am using es_CL language under Karmic), please could you try upgrade your gwibber version using daily version and check if this issue is still affecting you? Thanks in advance.

Omer Akram (om26er)
Changed in gwibber (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Christoph Korn (c-korn) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you encounter that this issue is still occurring or even better if you can check in latest Ubuntu Lucid version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!

Changed in gwibber (Ubuntu):
status: Incomplete → Invalid
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.