After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 395021 - GPM systray: UPS icons can't be found
GPM systray: UPS icons can't be found
Status: RESOLVED FIXED
Product: gnome-power-manager
Classification: Deprecated
Component: gnome-power-manager
2.17.x
Other All
: Normal normal
: ---
Assigned To: GNOME Power Manager Maintainer(s)
GNOME Power Manager Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2007-01-10 14:19 UTC by Arnaud Quette
Modified: 2007-01-11 07:48 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description Arnaud Quette 2007-01-10 14:19:21 UTC
Please describe the problem:
it seems there is a glitch in the ups icon lookup.
gpm should search ie gpm-ups-100-charging.png, but the ups part seems translated.
as a result, gpm search for gpm-onduleur-100-charging.png (onduleur is the french work for ups), which obviously can't be found.

Steps to reproduce:
1. use a non US system
2. plug an ups, possibly through addon-hid-ups, or through nut's hal support
3. check gpm systray


Actual results:
the systray icon is not found (got a red cross icon)

Expected results:
get the defined icon, ie gpm-ups-100-charging.png

Does this happen every time?
yes

Other information:
Comment 1 Arnaud Quette 2007-01-10 14:45:06 UTC
the problem sits src/gpm-power.c -> gpm_power_kind_to_string().
These string should really not be translated at all!
don't know how to avoid gettext'ization there.
Comment 2 Richard Hughes 2007-01-10 22:49:08 UTC
Already fixed, sorry for the inconvenience:

2006-12-31  Pascal Terjan  <pterjan@linuxfr.org>

	* src/gpm-power.c: (gpm_power_kind_to_string):
	Don't localise string as this is used internally for icon name.
Comment 3 Arnaud Quette 2007-01-11 07:48:15 UTC
merci Pascal.
Sorry for not having digged enough the Changelog.
This bug was against the package in ubuntu feisty (2.17.4) and the above mentionned fix was done a bit later.
I'll bug ubuntu.