xfce4-appfinder crashed with SIGSEGV in xfconf_g_property_channel_disconnect()

[David Pires]

Running testcase Desktop (Xubuntu) Desktop i386 for 2013-08-19, Saucy Daily.
Upon opening, Application Finder, immediately crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: xfce4-appfinder 4.10.1-1
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic i686
ApportVersion: 2.12.1-0ubuntu2
Architecture: i386
Date: Tue Aug 20 12:41:34 2013
ExecutablePath: /usr/bin/xfce4-appfinder
InstallationDate: Installed on 2013-08-20 (0 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Alpha i386 (20130819)
MarkForUpload: True
ProcCmdline: xfce4-appfinder
SegvAnalysis:
 Segfault happened at: 0xb71677e0: mov (%esi),%edx
 PC (0xb71677e0) ok
 source "(%esi)" (0x000001d1) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-appfinder
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libxfconf-0.so.2
 g_closure_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: xfce4-appfinder crashed with SIGSEGV in g_closure_unref()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Yang (yang-redhat-bugs)]

Description of problem:
Set Windows super key to Application Finder - Press the Super key - Click Preference

Version-Release number of selected component:
xfce4-appfinder-4.10.0-3.fc18

Additional info:
backtrace_rating: 4
cmdline: xfce4-appfinder
crash_function: xfconf_g_property_channel_disconnect
executable: /usr/bin/xfce4-appfinder
kernel: 3.6.10-4.fc18.i686
remote_result: NOTFOUND
uid: 1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 xfconf_g_property_channel_disconnect at xfconf-binding.c:262
 #1 closure_invoke_notifiers at gclosure.c:249
 #2 g_closure_unref at gclosure.c:599
 #3 handler_unref_R at gsignal.c:645
 #7 xfconf_channel_property_changed at xfconf-channel.c:392
 #8 _xfconf_marshal_VOID__STRING_STRING_BOXED at xfconf-marshal.c:85
 #13 xfconf_cache_property_changed at xfconf-cache.c:473
 #14 _xfconf_marshal_VOID__STRING_STRING_BOXED at xfconf-marshal.c:85
 #15 marshal_dbus_message_to_g_marshaller at dbus-gproxy.c:1735
 #20 dbus_g_proxy_emit_remote_signal at dbus-gproxy.c:1788

Potential duplicate: bug 847107

[Yang (yang-redhat-bugs)]

Created attachment 691968
File: backtrace

[Yang (yang-redhat-bugs)]

Created attachment 691969
File: cgroup

[Yang (yang-redhat-bugs)]

Created attachment 691970
File: core_backtrace

[Yang (yang-redhat-bugs)]

Created attachment 691971
File: dso_list

[Yang (yang-redhat-bugs)]

Created attachment 691972
File: environ

[Yang (yang-redhat-bugs)]

Created attachment 691973
File: limits

[Yang (yang-redhat-bugs)]

Created attachment 691975
File: maps

[Yang (yang-redhat-bugs)]

Created attachment 691977
File: open_fds

[Yang (yang-redhat-bugs)]

Created attachment 691978
File: proc_pid_status

[Yang (yang-redhat-bugs)]

Created attachment 691980
File: var_log_messages

[Kevin (kevin-redhat-bugs)]

Can you duplicate this? Or was it a one time crash?

[Yang (yang-redhat-bugs)]

No, it crashed only once.

[Apport retracing service (apport)]

StacktraceTop:
 xfconf_g_property_channel_disconnect (user_data=0xb7ef3900, closure=0xb7ef1ad8) at xfconf-binding.c:262
 closure_invoke_notifiers (notify_type=<optimized out>, closure=<optimized out>) at /build/buildd/glib2.0-2.37.5/./gobject/gclosure.c:249
 g_closure_unref (closure=0xb7ef1ad8) at /build/buildd/glib2.0-2.37.5/./gobject/gclosure.c:599
 handler_unref_R (handler=0xb7f07f20, instance=0xb7d12960, signal_id=93) at /build/buildd/glib2.0-2.37.5/./gobject/gsignal.c:653
 signal_emit_unlocked_R (node=node@entry=0xb7d17ad8, detail=1388, instance=0xb7d12960, emission_return=emission_return@entry=0x0, instance_and_params=0xbfbf0a90) at /build/buildd/glib2.0-2.37.5/./gobject/gsignal.c:3600

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1214361

[Fedora (fedora-redhat-bugs)]

This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

[Fedora (fedora-redhat-bugs)]

Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.