Using apport for this crash is unacceptable due to the fact that it
sends the core file which has sensitive data (i.e. accounts/passwords)
in it. I have complained over and over again about the inability to
remove sensitive data from apport reports but it seems to get ignored
over and over again.
That said, I am happy to attach specific attachments from an apport-
unpack here, but I will not attach my CoreDump.
I previously mentioned in comment #2 that this is likely a duplicate of
bug 660455 where I have included a stack trace and that stack trace
looks the same as the one I have in the StackTrace attachment of my
apport crash report:
#0 __strcmp_ia32 () at ../sysdeps/i386/i686/multiarch/../strcmp.S:39
No locals.
#1 0x083db252 in _run (self=0x9c87b90, pac=0x9cab140, url=0x9c2de40) at
pacrunner_webkit.c:197
str = <value optimized out>
val = <value optimized out>
tmp = <value optimized out>
ctxs = 0x9c8e430
#2 0x00d35b52 in px_proxy_factory_get_proxies (self=0x9c044a8, url=0x9cb1cf8
"http://weather.noaa.gov/cgi-bin/mgetmetar.pl?cccc=CYGK";) at proxy.c:401
pacrunners = 0x9cb3010
response = 0x9c96570
confurl = <value optimized out>
confign = 0x9c98248 ""
config = 0xd373ef
realurl = 0x9c2de40
networks = <value optimized out>
configs = 0x9c7f980
ignore_split = <value optimized out>
#3 0x00f28db2 in ?? () from /usr/lib/libsoup-gnome-2.4.so.1
No symbol table info available.
#4 0x00f29199 in ?? () from /usr/lib/libsoup-gnome-2.4.so.1
No symbol table info available.
#5 0x008463d4 in g_thread_pool_thread_proxy (data=0x9c12418) at
/build/buildd/glib2.0-2.26.0/glib/gthreadpool.c:319
task = 0x9cab540
pool = 0x9cb1cf8
#6 0x0084448f in g_thread_create_proxy (data=0x9cb4a48) at
/build/buildd/glib2.0-2.26.0/glib/gthread.c:1897
__PRETTY_FUNCTION__ = "g_thread_create_proxy"
#7 0x00776cc9 in start_thread (arg=0xb5bedb70) at pthread_create.c:304
__res = <value optimized out>
__ignore1 = <value optimized out>
__ignore2 = <value optimized out>
pd = 0xb5bedb70
now = <value optimized out>
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {7897076, 0, 4001536,
-1245785368, -304624184, 2125135523}, mask_was_saved = 0}}, priv = {pad = {0x0,
0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}}
not_first_call = <value optimized out>
robust = <value optimized out>
freesize = <value optimized out>
__PRETTY_FUNCTION__ = "start_thread"
#8 0x00e506ae in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
I would suggest rather than closing this as Invalid, closing it as a
duplicate of bug 660455. It may seem somewhat pointless to change
Invalid to Duplicate, but it will at least point people to a more
relevant bug.
--
gnome-panel clock applet crashes behind a firewall
https://bugs.launchpad.net/bugs/669971
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
