GNOME Bugzilla – Bug 578224
cannot specify event time any more
Last modified: 2017-08-05 18:44:23 UTC
Since I updated to ubuntu jaunty beta, featuring gnome 2.26, I cannot manage my events' time any more. If I open en existing event that has its time specified, the time isn't showed in the corresponding window field, and saving lets the event as an all-day-long event. If I add a new event, I have the same problem: I can generate only all-day-long event. Trying to specify the time with the time drop down list results in the time not been shown in the corresponding window element.
Can I get a screenshot attached in this bug report, please?
Created attachment 132626 [details] screeshot: scheduled event with time 18.30-19.15 hasn't time indication when opened
The bug appears only when running evolution with italian locales: $ locale LANG=it_IT.UTF-8 LC_CTYPE="it_IT.UTF-8" LC_NUMERIC="it_IT.UTF-8" LC_TIME="it_IT.UTF-8" LC_COLLATE="it_IT.UTF-8" LC_MONETARY="it_IT.UTF-8" LC_MESSAGES="it_IT.UTF-8" LC_PAPER="it_IT.UTF-8" LC_NAME="it_IT.UTF-8" LC_ADDRESS="it_IT.UTF-8" LC_TELEPHONE="it_IT.UTF-8" LC_MEASUREMENT="it_IT.UTF-8" LC_IDENTIFICATION="it_IT.UTF-8" LC_ALL= if I run it with LC_ALL=C the bug isn't present
http://mail.gnome.org/archives/gnome-i18n/2009-April/msg00171.html
For more info in Italian language to workaround this issue, see here [1]. [1] https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes/it#Evolution%20non%20%C3%A8%20in%20grado%20di%20salvare%20gli%20appuntamenti
I exectuted the commands in https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes/it#Evolution%20non%20%C3%A8%20in%20grado%20di%20salvare%20gli%20appuntamenti , but when I restarted evolution nothing had changed. I saw that I had : $ vdir /usr/share/locale-langpack/it/LC_MESSAGES/ |grep evolution -rw-r--r-- 1 root root 403680 2009-04-13 06:16 evolution-2.26.mo -rw------- 1 root root 94989 2009-04-16 23:26 evolution-data-server-2-26.mo -rw-r--r-- 1 root root 94023 2009-04-13 06:16 evolution-data-server-2.26.mo -rw-r--r-- 1 root root 23917 2009-04-13 06:16 evolution-exchange-2.26.mo -rw-r--r-- 1 root root 1428 2009-04-13 06:16 evolution-indicator.mo -rw-r--r-- 1 root root 3541 2009-04-13 06:16 evolution-webcal.mo i.e. 2 instances of evolution-data-server-2-26.mo, with different date e different permissions. It's supposed that my evolution couldn't see the correct evolution-data-server-2-26.mo , and I mv'ed the old one to *.save and changed the permissions of the correct one to -rw-r--r-- After that all was ok. Please update https://wiki.ubuntu.com/JauntyJackalope/ReleaseNotes/it#Evolution%20non%20%C3%A8%20in%20grado%20di%20salvare%20gli%20appuntamenti
(In reply to comment #6) > i.e. 2 instances of evolution-data-server-2-26.mo They do have different names (and different permissions): -rw------- 1 root root 94989 2009-04-16 23:26 evolution-data-server-2-26.mo -rw-r--r-- 1 root root 94023 2009-04-13 06:16 evolution-data-server-2.26.mo Compare 2.26 and 2-26
(In reply to comment #7) > (In reply to comment #6) > > i.e. 2 instances of evolution-data-server-2-26.mo > > They do have different names (and different permissions): > -rw------- 1 root root 94989 2009-04-16 23:26 evolution-data-server-2-26.mo > -rw-r--r-- 1 root root 94023 2009-04-13 06:16 evolution-data-server-2.26.mo > Yep, the filename was wrong, blame Milo :) We have updated the page using the proper filename, we'll check for file permissions later. However, please note that file is for jaunty, I'm not sure other distro will use the same naming scheme...
I checked file permissions downloading the .mo file from Ubuntu's wiki: they look right to me (-rw-r--r--).
This bug has been fixed as of revision... well, as of this: http://git.gnome.org/cgit/evolution-data-server/commit/?h=gnome-2-26&id=e7872958082a3182afe46eda3e1f6049a053671e
(In reply to comment #10) > This bug has been fixed as of revision... well, as of this: > I'm not sure we can close the bug with this. Maybe a deeper analysis of strftime (or similar) usage could be good, as well as translator comments suggesting to avoid %-H usage if unsupported.
@Luca: shouldn't it be better to reassign the bug to e-d-s component though?
Where is "%-H" defined? What does it mean? Any URL? If you want to have a translator comment please file a separate bug report with explicit steps to reproduce and references. This bug here is about Evo in Italian language not working.
(In reply to comment #13) > Where is "%-H" defined? What does it mean? Any URL? See stfrtime(3) man page, for example here[1]. It seems that dash (-) is a Glibc extension (the effect is "Do not pad a numeric result string", we need if for Italian localization in order to have hours in range 0~23, not 00~23) It seems also that POSIX stfrtime(3) described here[2] don't provide neither %k, nor dash extensions :( (I was aware only about the %k) Finally this translator comment was added some time ago to nautilus/eel #. Today, use special word. #. * strftime patterns preceeded with the widest #. * possible resulting string for that pattern. #. * #. * Note to localizers: You can look at man strftime #. * for details on the format, but you should only use #. * the specifiers from the C standard, not extensions. #. * These include "%" followed by one of #. * "aAbBcdHIjmMpSUwWxXyYZ". There are two extensions #. * in the Nautilus version of strftime that can be #. * used (and match GNU extensions). Putting a "-" #. * between the "%" and any numeric directive will turn #. * off zero padding, and putting a "_" there will use #. * space padding instead of zero padding. # #: ../libnautilus-private/nautilus-file.c:3726 #: ../src/nautilus-file-management-properties.c:472 msgid "today at %-I:%M:%S %p" Previously, in nautilus, we was using %k, but we switched to %-H due to this note. This is the reason I'm think it's not only an Italian translation issue. [1] http://linux.die.net/man/3/strftime [2] http://www.opengroup.org/onlinepubs/009695399/functions/strftime.html
*** Bug 580720 has been marked as a duplicate of this bug. ***
Luca: Feel free to file a separate ticket about that. This bug report is about the italian translation ONLY and I wonder why it is still open.
*** Bug 584915 has been marked as a duplicate of this bug. ***
*** Bug 585187 has been marked as a duplicate of this bug. ***
*** Bug 585604 has been marked as a duplicate of this bug. ***
Hallo all, I applied the solution [1] but I noticed that if a delete a just created event (created with the correct time limit) evolution freezes. I noticed also that if I change calendar->mail -> calendar and delete the event, everything is ok.
dexMilano: If Evolution freezes please provide a stacktrace with debug symbols. Please see http://live.gnome.org/GettingTraces/ .
Hy André, I don't know how to do it. I follow the instructions in the link, I installed the evolution-dbg and evolution-data-server-dbg. I recreate the error but I don't understand how to retrieve the stack trace. Any help is welcome dex
Please see http://live.gnome.org/GettingTraces/Details how to run Evolution in gdb. When Evolution freezes press "Control+C" and enter "thread apply all bt" to get the stacktrace.
Hallo André questions: what do you mean "enter "thread apply all bt"" However if I press Ctrl+FC nothing happens (see below) In fact now every time I enter in the calendar X (itself) freezes, so I have to restart the pc with Ctrl+Alt+Backspace. At the moment the Calendar feature is not usable. dex
Uhm, X freezes? That was not clear from your former comments. No idea. Would be nice if the Italian translators could comment here, and also update the status with regard to Ubuntu if they know.
Great BAD news! :-((( Now everytime I enter in calendar gnome/X11 freeze and I've to Ctrl+Alt-Bksp to reset X11. Perhaps it could be useful to add another piece of info that till now I didn't mention: I use Palm to sync event on the calendar. It could be possible the conduit conflicts with the modification we did? I'm available to dump backtrace but I didn't understand how to do it. I've Bug-buddy installed but when I execute it, it says "Either --appname or --package arguments are required." I tried bug-buddy --evolution or bug-buddy --evolution-dbg but the system says "** (bug-buddy:23656): CRITICAL **: Failed to parse arguments: Unknown option --evolution" Any suggestion on how to backtrace will be welcome Any suggestion on how to restore a so_and_so working calendar will be welcome dex
> I've Bug-buddy installed but when I execute it, As written please use gdb as described earlier.
Here you can find the backtrace using GDB Some note before: just because X11 frezzes when I launch the calendar, I should run GDB saving on file. When X11 frezzed it was not possible to press "Control+C" and enter "thread apply all bt" because the terminal I used to start evolution was frozen as all applications. (I hope this makes sense) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb6026770 (LWP 560)] ** (evolution:560): DEBUG: mailto URL command: evolution %s ** (evolution:560): DEBUG: mailto URL program: evolution [New Thread 0xb5494b90 (LWP 576)] [New Thread 0xb4c93b90 (LWP 577)] [Thread 0xb4c93b90 (LWP 577) exited] [New Thread 0xb4c93b90 (LWP 578)] [New Thread 0xb446db90 (LWP 580)] [New Thread 0xb3affb90 (LWP 581)] [New Thread 0xb32feb90 (LWP 582)] [New Thread 0xb2afdb90 (LWP 583)] [Thread 0xb2afdb90 (LWP 583) exited] [New Thread 0xb2afdb90 (LWP 584)] [New Thread 0xb1e52b90 (LWP 585)] [New Thread 0xb1651b90 (LWP 586)] [New Thread 0xb0e50b90 (LWP 587)] [New Thread 0xb064fb90 (LWP 588)] [Thread 0xb1651b90 (LWP 586) exited] [New Thread 0xb1651b90 (LWP 591)] ** (evolution:560): DEBUG: EI: SHELL STARTUP ** (evolution:560): DEBUG: EI: mail_read_notify ** (evolution:560): DEBUG: MAIL SERVER: Count changed: 0 [Thread 0xb064fb90 (LWP 588) exited] [Thread 0xb446db90 (LWP 580) exited] [Thread 0xb1651b90 (LWP 591) exited] [New Thread 0xb1651b90 (LWP 595)] [New Thread 0xb446db90 (LWP 596)] [New Thread 0xb064fb90 (LWP 597)] [New Thread 0xafbb0b90 (LWP 598)] [Thread 0xb1e52b90 (LWP 585) exited] [Thread 0xb064fb90 (LWP 597) exited] [Thread 0xafbb0b90 (LWP 598) exited] [New Thread 0xafbb0b90 (LWP 604)] [Thread 0xb1651b90 (LWP 595) exited] [New Thread 0xb1651b90 (LWP 605)] [Thread 0xb1651b90 (LWP 605) exited] [New Thread 0xb1651b90 (LWP 606)] [Thread 0xb1651b90 (LWP 606) exited] [New Thread 0xb1651b90 (LWP 607)] [New Thread 0xb064fb90 (LWP 608)] [Thread 0xb064fb90 (LWP 608) exited] [New Thread 0xb064fb90 (LWP 609)] [Thread 0xb064fb90 (LWP 609) exited] [New Thread 0xb064fb90 (LWP 610)] [Thread 0xb064fb90 (LWP 610) exited] [Thread 0xb446db90 (LWP 596) exited] [Thread 0xb1651b90 (LWP 607) exited] [Thread 0xafbb0b90 (LWP 604) exited] [New Thread 0xb1e52b90 (LWP 612)] [New Thread 0xafbb0b90 (LWP 615)] [New Thread 0xb1651b90 (LWP 616)] [Thread 0xb1651b90 (LWP 616) exited] [New Thread 0xb1651b90 (LWP 617)] [Thread 0xb1651b90 (LWP 617) exited] [New Thread 0xb1651b90 (LWP 618)] [Thread 0xb1651b90 (LWP 618) exited] [New Thread 0xb1651b90 (LWP 619)] [New Thread 0xb446db90 (LWP 620)] [Thread 0xb446db90 (LWP 620) exited] [New Thread 0xb446db90 (LWP 621)] [Thread 0xb446db90 (LWP 621) exited] [New Thread 0xb446db90 (LWP 622)] [Thread 0xb446db90 (LWP 622) exited] [New Thread 0xb446db90 (LWP 623)] [Thread 0xb446db90 (LWP 623) exited] [Thread 0xb1651b90 (LWP 619) exited] [Thread 0xafbb0b90 (LWP 615) exited] Program received signal SIGHUP, Hangup. [Switching to Thread 0xb5494b90 (LWP 576)] 0xb7efb430 in __kernel_vsyscall () (gdb)
After many tries and some trick i retrieve the following. I hope this helps ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ dex@dex-e4300-ulx:~$ gdb evolution GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) run Starting program: /usr/bin/evolution [Thread debugging using libthread_db enabled] [New Thread 0xb60d0770 (LWP 6771)] ** (evolution:6771): DEBUG: mailto URL command: evolution %s ** (evolution:6771): DEBUG: mailto URL program: evolution [New Thread 0xb553eb90 (LWP 6778)] [New Thread 0xb4d3db90 (LWP 6779)] [Thread 0xb4d3db90 (LWP 6779) exited] [New Thread 0xb4d3db90 (LWP 6780)] [New Thread 0xb41ffb90 (LWP 6781)] [New Thread 0xb39feb90 (LWP 6782)] [New Thread 0xb31fdb90 (LWP 6783)] [New Thread 0xb29fcb90 (LWP 6784)] [Thread 0xb29fcb90 (LWP 6784) exited] [New Thread 0xb1ca4b90 (LWP 6785)] [New Thread 0xb29fcb90 (LWP 6788)] [New Thread 0xb1c63b90 (LWP 6789)] [Thread 0xb1c63b90 (LWP 6789) exited] [New Thread 0xb1c63b90 (LWP 6790)] [Thread 0xb1c63b90 (LWP 6790) exited] [New Thread 0xb1c63b90 (LWP 6791)] [Thread 0xb1c63b90 (LWP 6791) exited] [New Thread 0xb1c63b90 (LWP 6792)] [New Thread 0xb1462b90 (LWP 6793)] [Thread 0xb1462b90 (LWP 6793) exited] [New Thread 0xb1462b90 (LWP 6794)] [Thread 0xb1462b90 (LWP 6794) exited] [New Thread 0xb1462b90 (LWP 6795)] [Thread 0xb1462b90 (LWP 6795) exited] [Thread 0xb41ffb90 (LWP 6781) exited] ** (evolution:6771): DEBUG: EI: SHELL STARTUP [Thread 0xb29fcb90 (LWP 6788) exited] [New Thread 0xb29fcb90 (LWP 6797)] [New Thread 0xb41ffb90 (LWP 6800)] [New Thread 0xb1462b90 (LWP 6801)] [New Thread 0xb0b4bb90 (LWP 6802)] [New Thread 0xafb49b90 (LWP 6804)] [New Thread 0xb034ab90 (LWP 6803)] [Thread 0xafb49b90 (LWP 6804) exited] [Thread 0xb41ffb90 (LWP 6800) exited] [Thread 0xb29fcb90 (LWP 6797) exited] [Thread 0xb1c63b90 (LWP 6792) exited] [Thread 0xb034ab90 (LWP 6803) exited] [Thread 0xb0b4bb90 (LWP 6802) exited] [New Thread 0xb0b4bb90 (LWP 6812)] [Thread 0xb0b4bb90 (LWP 6812) exited] [New Thread 0xb0b4bb90 (LWP 6813)] [Thread 0xb0b4bb90 (LWP 6813) exited] [New Thread 0xb0b4bb90 (LWP 6814)] [New Thread 0xb034ab90 (LWP 6815)] [New Thread 0xb1c63b90 (LWP 6816)] [Thread 0xb1c63b90 (LWP 6816) exited] [New Thread 0xb1c63b90 (LWP 6817)] [Thread 0xb1c63b90 (LWP 6817) exited] ** (evolution:6771): DEBUG: Not inbox [New Thread 0xb1c63b90 (LWP 6818)] [Thread 0xb1c63b90 (LWP 6818) exited] [New Thread 0xb1c63b90 (LWP 6819)] [Thread 0xb1c63b90 (LWP 6819) exited] [Thread 0xb1462b90 (LWP 6801) exited] [Thread 0xb034ab90 (LWP 6815) exited] [Thread 0xb0b4bb90 (LWP 6814) exited] [New Thread 0xb0b4bb90 (LWP 6823)] [New Thread 0xb034ab90 (LWP 6824)] [New Thread 0xb1462b90 (LWP 6825)] [New Thread 0xb1c63b90 (LWP 6826)] [New Thread 0xb29fcb90 (LWP 6827)] [New Thread 0xafb49b90 (LWP 6828)] [New Thread 0xaebffb90 (LWP 6829)] [Thread 0xb1c63b90 (LWP 6826) exited] [New Thread 0xb1c63b90 (LWP 6831)] [Thread 0xb0b4bb90 (LWP 6823) exited] [Thread 0xafb49b90 (LWP 6828) exited] [Thread 0xb29fcb90 (LWP 6827) exited] [New Thread 0xb0b4bb90 (LWP 6832)] [New Thread 0xb29fcb90 (LWP 6833)] [Thread 0xb29fcb90 (LWP 6833) exited] [New Thread 0xb29fcb90 (LWP 6834)] [Thread 0xb29fcb90 (LWP 6834) exited] [New Thread 0xb29fcb90 (LWP 6835)] [Thread 0xb29fcb90 (LWP 6835) exited] [Thread 0xb1c63b90 (LWP 6831) exited] [Thread 0xb0b4bb90 (LWP 6832) exited] [Thread 0xaebffb90 (LWP 6829) exited] [New Thread 0xaebffb90 (LWP 6839)] [New Thread 0xb0b4bb90 (LWP 6841)] [New Thread 0xb1c63b90 (LWP 6842)] [Thread 0xb1c63b90 (LWP 6842) exited] [New Thread 0xb1c63b90 (LWP 6843)] [Thread 0xb1c63b90 (LWP 6843) exited] [Thread 0xb0b4bb90 (LWP 6841) exited] [Thread 0xaebffb90 (LWP 6839) exited] [New Thread 0xaebffb90 (LWP 6850)] [Thread 0xaebffb90 (LWP 6850) exited] [New Thread 0xaebffb90 (LWP 6857)] [New Thread 0xb0b4bb90 (LWP 6858)] [Thread 0xb0b4bb90 (LWP 6858) exited] [New Thread 0xb0b4bb90 (LWP 6859)] [New Thread 0xb1c63b90 (LWP 6860)] [Thread 0xb1c63b90 (LWP 6860) exited] [New Thread 0xb1c63b90 (LWP 6861)] calendar-gui-Message: Check if default client matches (1221471815.7859.18@dex-asus-ubuntu 1205311116.13180.9@dex-ausus-ubuntu) [New Thread 0xb29fcb90 (LWP 6864)] [New Thread 0xafb49b90 (LWP 6865)] calendar-gui-Message: Check if default client matches (1221471815.7859.18@dex-asus-ubuntu 1221471815.7859.18@dex-asus-ubuntu) [Thread 0xafb49b90 (LWP 6865) exited] [Thread 0xb1c63b90 (LWP 6861) exited] [Thread 0xb29fcb90 (LWP 6864) exited] [Thread 0xb0b4bb90 (LWP 6859) exited] [Thread 0xaebffb90 (LWP 6857) exited] [New Thread 0xaebffb90 (LWP 6879)] [Thread 0xaebffb90 (LWP 6879) exited] [New Thread 0xaebffb90 (LWP 6883)] [New Thread 0xb0b4bb90 (LWP 6884)] [Thread 0xaebffb90 (LWP 6883) exited] [Thread 0xb0b4bb90 (LWP 6884) exited] [New Thread 0xb0b4bb90 (LWP 6888)] [Thread 0xb0b4bb90 (LWP 6888) exited] [New Thread 0xb0b4bb90 (LWP 6893)] [Thread 0xb0b4bb90 (LWP 6893) exited] [New Thread 0xb0b4bb90 (LWP 6895)] [New Thread 0xaebffb90 (LWP 6896)] [Thread 0xaebffb90 (LWP 6896) exited] [Thread 0xb0b4bb90 (LWP 6895) exited] ^C Program received signal SIGINT, Interrupt. [Switching to Thread 0xb60d0770 (LWP 6771)] 0xb7fa5430 in __kernel_vsyscall () (gdb) thread apply all bt
+ Trace 216025
Thread 1 (Thread 0xb60d0770 (LWP 6771))
(gdb)
Hmm. Is there still an issue nowadays, or can this be closed as obsolete?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment. Thanks!