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 379737 - crash when adjusting an appointment start
crash when adjusting an appointment start
Status: RESOLVED DUPLICATE of bug 339381
Product: evolution
Classification: Applications
Component: Calendar
2.6.x (obsolete)
Other other
: High critical
: ---
Assigned To: evolution-calendar-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2006-11-27 10:39 UTC by Stéphane Genaud
Modified: 2006-12-07 11:09 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14


Description Stéphane Genaud 2006-11-27 10:38:11 UTC 
Distribution: Ubuntu 6.06 (dapper)
Package: Evolution
Severity: critical
Version: GNOME2.14.3 2.6.x
Gnome-Distributor: Ubuntu
Synopsis: crash when adjusting an appointment start
Bugzilla-Product: Evolution
Bugzilla-Component: Calendar
Bugzilla-Version: 2.6.x
BugBuddy-GnomeVersion: 2.0 (2.14.1)
Description:
Description of the crash:


Steps to reproduce the crash:
1. Create an appointment in the calendar using the mouse: hold the left
mouse button to highlight for instance the zone reprensenting the
appointment time (e.g. 15:00 to 16:00). You get a blue marked zone.
2. Press "Enter" -> you get a cursor to write down some text in this
blue zone. Press "Enter" to validate the text and the appointement.
3. Move your mouse to the top (or bottom) edge of the box. The cursor
becomes a double arrow, allowing to move the line to adjust the start
(or end) time of appointment. Hold the mouse button, adjust time, and
erlease the button. This ends in a segfault.

Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/usr/bin/evolution-2.6'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1231578912 (LWP 13075)]
[New Thread -1371542608 (LWP 13130)]
[New Thread -1363149904 (LWP 13125)]
[New Thread -1334240336 (LWP 13103)]
[New Thread -1266832464 (LWP 13086)]
[New Thread -1249031248 (LWP 13084)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 89711

Thread 1 (Thread -1231578912 (LWP 13075))

  • #0 __kernel_vsyscall
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 es_menu_hook_get_type
  • #4 <signal handler called>
  • #5 e_calendar_view_get_tooltips
    from /usr/lib/evolution/2.6/components/libevolution-calendar.so
  • #6 g_main_context_is_owner
    from /usr/lib/libglib-2.0.so.0
  • #7 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #8 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #10 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #11 main
  • #0 __kernel_vsyscall 




------- Bug created by bug-buddy at 2006-11-27 10:39 -------
Comment 1 ebbywiselyn 2006-12-07 11:09:17 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.
339381

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