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 534710 - crash in Deskbar: Deskbar load error
crash in Deskbar: Deskbar load error
Status: RESOLVED DUPLICATE of bug 517356
Product: deskbar-applet
Classification: Deprecated
Component: general
unspecified
Other All
: High critical
: ---
Assigned To: Deskbar Applet Maintainer(s)
Deskbar Applet Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2008-05-25 03:06 UTC by Buyant-Orgil
Modified: 2008-05-25 17:22 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Buyant-Orgil 2008-05-25 03:06:20 UTC 
What were you doing when the application crashed?
Deskbar load error


Distribution: Ubuntu 7.10 (gutsy)
Gnome Release: 2.20.1 2007-10-19 (Ubuntu)
BugBuddy Version: 2.18.1

System: Linux 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Human
Icon Theme: Human

Memory status: size: 0 vsize: 0 resident: 0 share: 0 rss: 0 rss_rlim: 0
CPU usage: start_time: 0 rtime: 0 utime: 0 stime: 0 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0



----------- .xsession-errors (11 sec old) ---------------------
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/logon/.evolutialarm-notify.c:368 (alarm_notify_new) - Alarm Notify New 
 alarm-notify.c:304 (alarm_channel_setup) - Channel Setup
 alarm-notify.c:243 (alarm_notify_init) - Initing Alarm Notify
alarm-queue.c:1870 (alarm_queue_init)
alarm-queue.c:200 (queue_midnight_refresh) - Refresh at Mon Apr 21 09:00:00 2008
 
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/logon/.evolution/calendar/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/logon/.evolution/calendar/local/system - Calendar Open Async... 0x80dc4c0
alarm-notify.c:220 (load_calendars) - Loading Calendar contacts:/// 
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/logon/.evolution/tasks/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/logon/.evolution/tasks/local/system - Calendar Open Async... 0x80df920
alarm-notify.c:220 (load_calendars) - Loading Calendar file:///home/logon/.evolution/memos/local/system 
alarm-notify.c:462 (alarm_notify_add_calendar) file:///home/logon/.evolu
(evolution-alarm-notify:5698): evolution-alarm-notify-WARNING **: Could not create the alarm notify service factory, maybe it's already running...
tion/memos/local/system - Calendar Open Async... 0x80dedd0
--------------------------------------------------
Traceback (most recent call last):

+ Trace 198568

  • File "/usr/lib/deskbar-applet/deskbar-applet", line 75 in <module> 
    parser = OptionParser(usage=usage)
  • File "optparse.py", line 1208 in __init__ 
    add_help=add_help_option)
  • File "optparse.py", line 1254 in _populate_option_list 
    self._add_help_option()
  • File "optparse.py", line 1239 in _add_help_option 
    help=_("show this help message and exit"))
  • File "gettext.py", line 581 in gettext 
    return dgettext(_current_domain, message)
  • File "gettext.py", line 545 in dgettext 
    codeset=_localecodesets.get(domain))
  • File "gettext.py", line 493 in translation 
    t = _translations.setdefault(key, class_(open(mofile, 'rb')))
  • File "gettext.py", line 180 in __init__ 
    self._parse(fp)
  • File "gettext.py", line 315 in _parse 
    self.plural = c2py(plural)
  • File "gettext.py", line 93 in c2py 
    raise ValueError, 'plural forms expression could be dangerous'
ValueError: plural forms expression could be dangerous 






Comment 1


Susana





          2008-05-25 17:22:28 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


*** This bug has been marked as a duplicate of 517356 ***