evolution-alarm-notify crashed with signal 5 in main()

Bug #125321 reported by Vivian Stewart on 2007-07-11
42
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: evolution

dominos

ProblemType: Crash
Architecture: i386
Date: Thu Jul 12 08:03:53 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/evolution/2.12/evolution-alarm-notify
NonfreeKernelModules: nvidia cdrom
Package: evolution 2.11.5-Oubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/lib/evolution/2.12/evolution-alarm-notify --sm-config-prefix /evolution-alarm-notify-nSDvPY/ --sm-client-id 117f000101000118415820200000064650000 --screen 0
ProcCwd: /home/vivy
ProcEnviron:
 LANGUAGE=en_NZ.UTF-8
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: evolution
Stacktrace:
 #0 0xb6f08cab in g_logv () from /usr/lib/libglib-2.0.so.0
 #1 0xb6f08f29 in g_log () from /usr/lib/libglib-2.0.so.0
 #2 0x0805dfa0 in main ()
StacktraceTop: main ()
Title: evolution-alarm-notify crashed with signal 5 in main()
Uname: Linux lapy2 2.6.22-7-generic #1 SMP Mon Jun 25 17:33:14 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip disk fax floppy lpadmin plugdev scanner tape video

Vivian Stewart (vivichrist) wrote :

StacktraceTop:?? ()
?? ()
?? ()
?? ()
?? ()

C de-Avillez (hggdh2) wrote :

Thanks for your bug report. Unfortunately, the stacktrace does not seem to be usable. 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

StacktraceTop:main (argc=7, argv=0xbf95aa24) at notify-main.c:153

C de-Avillez (hggdh2) wrote :

Is this bug reproducible? If it is, please follow my previous instructions re. getting a backtrace.

Pedro Villavicencio (pedro) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

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

Duplicates of this bug

Other bug subscribers