[Bug 226460] devel/libical: segmentation fault with evolution-calendar-factory

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226460

            Bug ID: 226460
           Summary: devel/libical: segmentation fault with
                    evolution-calendar-factory
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Individual Port(s)
          Assignee: gnome at FreeBSD.org
          Reporter: cpm at freebsd.org
          Assignee: gnome at FreeBSD.org
             Flags: maintainer-feedback?(gnome at FreeBSD.org)

It seems that evolution-calendar-factory crashes at startup.

dmesg output shows these lines:

pid 1315 (evolution-calendar-), uid 1001: exited on signal 11 (core dumped)
pid 1321 (evolution-calendar-), uid 1001: exited on signal 11 (core dumped)
pid 1336 (evolution-calendar-), uid 1001: exited on signal 11 (core dumped)
pid 1340 (evolution-calendar-), uid 1001: exited on signal 11 (core dumped)
pid 1342 (evolution-calendar-), uid 1001: exited on signal 11 (core dumped)
pid 1346 (evolution-calendar-), uid 1001: exited on signal 11 (core dumped)
pid 1348 (evolution-calendar-), uid 1001: exited on signal 11 (core dumped)
pid 1351 (evolution-calendar-), uid 1001: exited on signal 11 (core dumped)
pid 3474 (evolution-calendar-), uid 1001: exited on signal 11 (core dumped)

Here is the backtrace:

[New LWP 100636]
[New LWP 100491]
Core was generated by `evolution-calendar-'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x000000080307b4ff in icaltzutil_fetch_timezone ()
   from /usr/local/lib/libical.so.2
[Current thread is 1 (LWP 100636)]

As a workaround, I run manually evolution-calendar-factory using the -w option
to wait running until at least one client is connected.

% /usr/local/libexec/evolution-calendar-factory -w &

-- 
You are receiving this mail because:
You are the assignee for the bug.