Bug 678012

Summary: [abrt] dconf-editor-0.7.2-3: g_object_ref: Process /usr/bin/dconf-editor was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: dconfAssignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: jlaska, mclasen, rhughes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:1650d6e6925b23de35b32cc320982efe7be7a26b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-07 00:59:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Joachim Frieben 2011-02-16 13:51:06 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 190514 bytes
cmdline: dconf-editor
component: dconf
Attached file: coredump, 14573568 bytes
crash_function: g_object_ref
executable: /usr/bin/dconf-editor
kernel: 2.6.38-0.rc4.git7.1.fc15.x86_64
package: dconf-editor-0.7.2-3
rating: 4
reason: Process /usr/bin/dconf-editor was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Rawhide)
time: 1297864181
uid: 501

How to reproduce
-----
1. Run dconf-editor.

Comment 1 Joachim Frieben 2011-02-16 13:51:18 UTC
Created attachment 479112 [details]
File: backtrace

Comment 2 James Laska 2011-02-28 13:37:22 UTC
Package: dconf-editor-0.7.2-3
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1. Start dconf-editor
2. Expand the [+] Desktop section
3. Attempt to resize the dconf-editor window by dragging the bottom right corner


Comment
-----
Start dconf-editor and attempt to resize the window by dragging a corner

Comment 3 Matthias Clasen 2011-04-07 00:59:24 UTC

*** This bug has been marked as a duplicate of bug 691364 ***