On Mon, 2008-09-29 at 15:45 +0000, Sebastien Bacher wrote: > the bug doesn't have useful information,
Just because there isn't any useful information, yes does not make the bug categorically invalid. > could you get a debug > stacktrace? I would most certainly if I could. How do you propose to debug this type of situation though... $ gdb /usr/lib/evolution/2.24/evolution-alarm-notify (gdb) run Starting program: /usr/lib/evolution/2.24/evolution-alarm-notify [Thread debugging using libthread_db enabled] [New Thread 0xb62f9720 (LWP 9546)] [New Thread 0xb6119b90 (LWP 9553)] ... [Thread 0xb60d8b90 (LWP 9557) exited] [Thread 0xb48d5b90 (LWP 9563) exited] [Thread 0xb58d7b90 (LWP 9581) exited] alarm-queue.c:1821 (check_midnight_refresh) Program terminated with signal SIGKILL, Killed. The program no longer exists. (gdb) I know of no way to discover back to find the originator of a signal, do you? b. -- evolution-alarm-notifier being killed https://bugs.launchpad.net/bugs/268331 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
