Calender closes when clicked

Bug #165234 reported by nomojob
2
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

Whenever I click on the Calender tab, it just closes the application immediately. No error message or anything.

ProblemType: Bug
Architecture: i386
Date: Mon Nov 26 14:05:33 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/evolution
Package: evolution 2.12.1-0ubuntu1
PackageArchitecture: i386
ProcCmdline: evolution --component=mail
ProcCwd: /home/diamondsteve
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: evolution
Uname: Linux diamondsteve-desktop 2.6.22-14-generic #1 SMP Sun Oct 14 23:05:12 GMT 2007 i686 GNU/Linux

Tags: apport-bug
Revision history for this message
nomojob (freedomcentral) wrote :
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in evolution:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
nomojob (freedomcentral) wrote : Re: [Bug 165234] Re: Calender closes when clicked
Download full text (19.4 KiB)

I couldnt find the log file that it was supposed to create, so I just
copied all the info in the terminal and attached it as a txt file. Let
me know if you need anything else.

On Mon, 2007-11-26 at 19:16 +0000, Pedro Villavicencio wrote:
> Thanks for your bug report. Please try to obtain a backtrace
> http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the
> bug report. This will greatly help us in tracking down your problem.
>
> ** Changed in: evolution (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
> Status: New => Incomplete
>

Loaded symbols for /usr/lib/libgsf-1.so.114
Reading symbols from /usr/lib/libcroco-0.6.so.3...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libcroco-0.6.so.3
Reading symbols from /lib/libbz2.so.1.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libbz2.so.1.0
Reading symbols from /usr/lib/pango/1.6.0/modules/pango-basic-fc.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/pango/1.6.0/modules/pango-basic-fc.so
Reading symbols from /usr/lib/evolution/2.12/plugins/liborg-gnome-mail-notification.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/evolution/2.12/plugins/liborg-gnome-mail-notification.so
Reading symbols from /usr/lib/evolution/2.12/plugins/liborg-gnome-groupwise-features.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/evolution/2.12/plugins/liborg-gnome-groupwise-features.so
Reading symbols from /usr/lib/evolution/2.12/plugins/liborg-gnome-new-mail-notify.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/evolution/2.12/plugins/liborg-gnome-new-mail-notify.so
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
(gdb) continue
Continuing.
[New Thread -1301685360 (LWP 7914)]
[New Thread -1301951600 (LWP 7916)]
[New Thread -1310344304 (LWP 7918)]
[New Thread -1318737008 (LWP 7919)]
[New Thread -1327129712 (LWP 7920)]
[New Thread -1335522416 (LWP 7921)]
[New Thread -1343915120 (LWP 7923)]
[New Thread -1352307824 (LWP 7924)]
[New Thread -1360700528 (LWP 7925)]
[New Thread -1369093232 (LWP 7926)]
[Thread -1360700528 (LWP 7925) exited]
[New Thread -1377485936 (LWP 7927)]
[New Thread -1360700528 (LWP 7928)]
[New Thread -1385878640 (LWP 7930)]
[Thread -1318737008 (LWP 7919) exited]
[New Thread -1318737008 (LWP 7931)]
[New Thread -1394271344 (LWP 7932)]
[New Thread -1402664048 (LWP 7933)]
[Thread -1369093232 (LWP 7926) exited]
[Thread -1394271344 (LWP 7932) exited]
[Thread -1402664048 (LWP 7933) exited]
[Thread -1352307824 (LWP 7924) exited]
[Thread -1343915120 (LWP 7923) exited]
[Thread -1335522416 (LWP 7921) exited]
[Thread -1301951600 (LWP 7916) exited]
[Thread -1310344304 (LWP 7918) exited]
[Thread -1327129712 (LWP 7920) exited]
[Thread -1377485936 (LWP 7927) exited]
[Thread -1360700528 (LWP 7928) exited]
[Thread -1385878640 (LWP 7930) exited]
[Thread -1318737008 (LWP 7931) exited]
[New Thread -1318737008 (LWP 7935)]
[New Thread -1385878640 (LWP 7936)]
[New Thread -1360700528 (LWP 7937)]
[New Thread -1377485936 (LWP 7938)]
[New Thread -1327129712 (LWP 7939)]
[New Thread -1301951600 (LWP 7940)]
[...

Revision history for this message
nomojob (freedomcentral) wrote : [Bug 165234] Re: Calender closes when clicked]
Download full text (19.0 KiB)

I couldnt find the log file that it was supposed to create, so I just
copied all the info in the terminal and attached it as a txt file. Let
me know if you need anything else.

Loaded symbols for /usr/lib/libgsf-1.so.114
Reading symbols from /usr/lib/libcroco-0.6.so.3...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libcroco-0.6.so.3
Reading symbols from /lib/libbz2.so.1.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libbz2.so.1.0
Reading symbols from /usr/lib/pango/1.6.0/modules/pango-basic-fc.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/pango/1.6.0/modules/pango-basic-fc.so
Reading symbols from /usr/lib/evolution/2.12/plugins/liborg-gnome-mail-notification.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/evolution/2.12/plugins/liborg-gnome-mail-notification.so
Reading symbols from /usr/lib/evolution/2.12/plugins/liborg-gnome-groupwise-features.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/evolution/2.12/plugins/liborg-gnome-groupwise-features.so
Reading symbols from /usr/lib/evolution/2.12/plugins/liborg-gnome-new-mail-notify.so...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/evolution/2.12/plugins/liborg-gnome-new-mail-notify.so
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()
(gdb) continue
Continuing.
[New Thread -1301685360 (LWP 7914)]
[New Thread -1301951600 (LWP 7916)]
[New Thread -1310344304 (LWP 7918)]
[New Thread -1318737008 (LWP 7919)]
[New Thread -1327129712 (LWP 7920)]
[New Thread -1335522416 (LWP 7921)]
[New Thread -1343915120 (LWP 7923)]
[New Thread -1352307824 (LWP 7924)]
[New Thread -1360700528 (LWP 7925)]
[New Thread -1369093232 (LWP 7926)]
[Thread -1360700528 (LWP 7925) exited]
[New Thread -1377485936 (LWP 7927)]
[New Thread -1360700528 (LWP 7928)]
[New Thread -1385878640 (LWP 7930)]
[Thread -1318737008 (LWP 7919) exited]
[New Thread -1318737008 (LWP 7931)]
[New Thread -1394271344 (LWP 7932)]
[New Thread -1402664048 (LWP 7933)]
[Thread -1369093232 (LWP 7926) exited]
[Thread -1394271344 (LWP 7932) exited]
[Thread -1402664048 (LWP 7933) exited]
[Thread -1352307824 (LWP 7924) exited]
[Thread -1343915120 (LWP 7923) exited]
[Thread -1335522416 (LWP 7921) exited]
[Thread -1301951600 (LWP 7916) exited]
[Thread -1310344304 (LWP 7918) exited]
[Thread -1327129712 (LWP 7920) exited]
[Thread -1377485936 (LWP 7927) exited]
[Thread -1360700528 (LWP 7928) exited]
[Thread -1385878640 (LWP 7930) exited]
[Thread -1318737008 (LWP 7931) exited]
[New Thread -1318737008 (LWP 7935)]
[New Thread -1385878640 (LWP 7936)]
[New Thread -1360700528 (LWP 7937)]
[New Thread -1377485936 (LWP 7938)]
[New Thread -1327129712 (LWP 7939)]
[New Thread -1301951600 (LWP 7940)]
[New Thread -1310344304 (LWP 7941)]
[New Thread -1335522416 (LWP 7942)]
[New Thread -1343915120 (LWP 7943)]
[New Thread -1352307824 (LWP 7944)]
[New Thread -1369093232 (LWP 7945)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1233619280 (LWP 7863)]
0xb7e92daa in ?? () from /usr/lib/evolution/2.12/libetable.so.0
(gdb) backtrace full
#0 0xb7e92daa in ?? () from /usr/lib/evolution/2.12/libetable.so.0
No symbol table info av...

Revision history for this message
Pedro Villavicencio (pedro) wrote :

May you please install the following packages: evolution-dbgsym, libglib2.0-0-dbgsym, libgtk2.0-0-dbgsym, libedataserverui1.2-8-dbgsym and libedataserver1.2-9-dbgsym and try to get a new trace? this time please attach the file to the report instead of putting it as a comment, thanks!.

Revision history for this message
nomojob (freedomcentral) wrote : Re: [Bug 165234] Re: Calender closes when clicked

First, I am new to Ubuntu. How do I install these? Also, does this
debugger create a debugging log somewhere? Where do I find that?

Thanks!

On Tue, 2007-11-27 at 18:43 +0000, Pedro Villavicencio wrote:
> May you please install the following packages: evolution-dbgsym,
> libglib2.0-0-dbgsym, libgtk2.0-0-dbgsym, libedataserverui1.2-8-dbgsym
> and libedataserver1.2-9-dbgsym and try to get a new trace? this time
> please attach the file to the report instead of putting it as a comment,
> thanks!.
>

Revision history for this message
Pedro Villavicencio (pedro) wrote :

That's ok, you need to add these lines to your /etc/apt/sources.list :

deb http://people.ubuntu.com/~ubuntu-archive/ddebs gutsy main universe
deb http://people.ubuntu.com/~ubuntu-archive/ddebs gutsy-updates main universe
deb http://people.ubuntu.com/~ubuntu-archive/ddebs gutsy-proposed main universe
deb http://people.ubuntu.com/~ubuntu-archive/ddebs gutsy-security main universe

then run apt-get update and install the packages

Then you need to follow these instructions for getting a backtrace : https://wiki.ubuntu.com/Backtrace if you have any doubt don't hesitate in asking us, thanks!

Revision history for this message
nomojob (freedomcentral) wrote :

In the instructions it says to:

"Attach the complete output from GDB, contained in gdb-<program>.txt, in
your bug report. "

I can't find this .txt file anywhere. What am I missing here?

On Tue, 2007-11-27 at 19:59 +0000, Pedro Villavicencio wrote:
> That's ok, you need to add these lines to your /etc/apt/sources.list :
>
> deb http://people.ubuntu.com/~ubuntu-archive/ddebs gutsy main universe
> deb http://people.ubuntu.com/~ubuntu-archive/ddebs gutsy-updates main universe
> deb http://people.ubuntu.com/~ubuntu-archive/ddebs gutsy-proposed main universe
> deb http://people.ubuntu.com/~ubuntu-archive/ddebs gutsy-security main universe
>
> then run apt-get update and install the packages
>
> Then you need to follow these instructions for getting a backtrace :
> https://wiki.ubuntu.com/Backtrace if you have any doubt don't hesitate
> in asking us, thanks!
>

Revision history for this message
Basilio Kublik (sourcercito) wrote :

hi there
in the instructions where it said gdb-<program>.txt the "<program>" part meant to be replaced by the name of the program you're trying to get a backtrace from. in this case will be evolution, and this file will be created after you run the commands described in the documentation.

hope this helps to clarify things out.

Revision history for this message
nomojob (freedomcentral) wrote :

I have followed the instructions about 5 times now and each time it does
not create that .txt file anywhere. I do a search for it one the whole
filesystem and it turns up nothing. What am I missing here? In the
terminal it looks as if everything is going as planned, except for
creating the .txt file.

On Tue, 2007-11-27 at 20:50 +0000, Basilio Kublik wrote:
> hi there
> in the instructions where it said gdb-<program>.txt the "<program>" part meant to be replaced by the name of the program you're trying to get a backtrace from. in this case will be evolution, and this file will be created after you run the commands described in the documentation.
>
> hope this helps to clarify things out.
>

Revision history for this message
nomojob (freedomcentral) wrote :

I have followed the instructions about 5 times now and each time it does
not create that .txt file anywhere. I do a search for it one the whole
filesystem and it turns up nothing. What am I missing here? In the
terminal it looks as if everything is going as planned, except for
creating the .txt file.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However the stacktrace you submitted isn't good enough to determine where's the problem. Please follow these instuctions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in evolution:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.