This bug is 100% reproducible. I am using Lucid Lynx.

I have attached my crash file. I enabled apport, but it refuses to
upload the crash:

"The problem cannot be reported: The program crashed on an assertion
failure, but the message could not be retrieved. Apport does not support
reporting these crashes."

Why are assertions enabled in production code? And if you choose to
enable them, the apport bug reporter should be able to handle them like
any other crash.


** Attachment added: "_usr_lib_gnome-panel_clock-applet.1002.crash"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/580735/+attachment/2399536/+files/_usr_lib_gnome-panel_clock-applet.1002.crash

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/580735

Title:
  Clock Applet crashes for no reason

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/580735/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to