glunarclock applet crashed after Karmic upgrade

Bug #463869 reported by Mark Fiedler
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
glunarclock (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: glunarclock

upgraded to karmic
at first login got crash with glunarclock applet

ProblemType: Crash
Architecture: i386
Date: Thu Oct 29 18:30:38 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/gnome-panel/glunarclock-applet-2
Package: glunarclock 1:0.32.4-11ubuntu2
ProcCmdline: /usr/lib/gnome-panel/glunarclock-applet-2 --oaf-activate-iid=OAFIID:GNOME_GLunarclockApplet_Factory --oaf-ior-fd=26
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x4e09ba <strcmp+10>: cmp (%edx),%al
 PC (0x004e09ba) ok
 source "(%edx)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: glunarclock
StacktraceTop:
 strcmp () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
 panel_applet_marshal_BOOLEAN__STRING (closure=0x85c2870,
 IA__g_closure_invoke (closure=0x85c2870,
 bonobo_closure_invoke_va_list ()
Title: glunarclock-applet-2 crashed with SIGSEGV in strcmp()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #459389, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-i386-retrace
Revision history for this message
vulfgar (vulfgar) wrote :

A bit wierd, when I try to look at the bug that this is a duplicate of, I get the message
"Not allowed here

Sorry, you don't have permission to access this page. "

Why am I not allowed to view that bug? It's not a very efficient way to avoid duplicates by not letting people watch the already filed bugs. :(

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.