[Fedora-i18n-bugs] [Bug 868333] New: [abrt] ibus-1.4.99.20120914-2.fc17: g_logv: Process /usr/libexec/ibus-dconf was killed by signal 5 (SIGTRAP)

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=868333

Bug ID: 868333
        QA Contact: [e-mail]
          Severity: unspecified
        Whiteboard: abrt_hash:c4a59ad353b1a5bc9fff1abe2305a78601d8e77e
           Version: 17
          Priority: unspecified
                CC: [e-mail],
                    [e-mail], [e-mail]
          Assignee: [e-mail]
           Summary: [abrt] ibus-1.4.99.20120914-2.fc17: g_logv: Process
                    /usr/libexec/ibus-dconf was killed by signal 5
                    (SIGTRAP)
        Regression: ---
      Story Points: ---
    Classification: Fedora
                OS: Unspecified
          Reporter: [e-mail]
              Type: ---
     Documentation: ---
          Hardware: x86_64
        Mount Type: ---
            Status: NEW
         Component: ibus
           Product: Fedora

Version-Release number of selected component:
ibus-1.4.99.20120914-2.fc17

Additional info:
libreport version: 2.0.14
abrt_version:   2.0.13
backtrace_rating: 4
cmdline:        /usr/libexec/ibus-dconf
crash_function: g_logv
kernel:         3.6.2-4.fc17.x86_64

truncated backtrace:
:Thread no. 1 (10 frames)
: #0 g_logv at gmessages.h:101
: #2 dconf_engine_refresh_system at ../engine/dconf-engine.c:188
: #3 dconf_engine_setup at ../engine/dconf-engine.c:218
: #4 dconf_engine_new at ../engine/dconf-engine.c:376
: #5 dconf_client_construct at dconf-client.c:1508
: #6 dconf_client_new at dconf-client.c:1531
: #7 ibus_config_dconf_init at config.c:251
: #8 g_type_create_instance at gtype.c:1892
: #9 g_object_constructor at gobject.c:1849
: #11 g_object_new_valist at gobject.c:1830

[Fedora-i18n-bugs] [Bug 868333] [abrt] ibus-1.4.99.20120914-2.fc17: g_logv: Process /usr/libexec/ibus-dconf was killed by signal 5 (SIGTRAP)

[Red Hat Bugzilla]

https://bugzilla.redhat.com/show_bug.cgi?id=868333

fujiwara  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(hufeng1987@gmail.
                   |                            |com)

--- Comment #10 from fujiwara  ---
(In reply to comment #3)
> Created attachment 630063 [details]
> File: backtrace
> #0  g_logv (log_domain=0x0, log_level=G_LOG_LEVEL_ERROR, format=0x3107a07dc8 "Unable to open '%s', specified in dconf profile\n", args1=args1@entry=0x7fff46488158) at gmessages.h:101
> #1  0x0000003108a4eb22 in g_log (log_domain=log_domain@entry=0x0, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x3107a07dc8 "Unable to open '%s', specified in dconf profile\n") at gmessages.c:792
>         args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7fff46488230, reg_save_area = 0x7fff46488170}}
> #2  0x0000003107a03628 in dconf_engine_refresh_system (engine=0x9b6ed0, i=<optimized out>) at ../engine/dconf-engine.c:188
>         filename = 0x9c0780 "/etc/dconf/db/ibus"

It's curious that your system does not have "/etc/dconf/db/ibus" .

% rpm -q --scripts ibus
posttrans scriptlet (using /bin/sh):
dconf update

The ibus post script runs 'dconf update' and it creates "/etc/dconf/db/ibus".

Does not 'dconf update' create "/etc/dconf/db/ibus" in your system?

[Fedora-i18n-bugs] [Bug 868333] [abrt] ibus-1.4.99.20120914-2.fc17: g_logv: Process /usr/libexec/ibus-dconf was killed by signal 5 (SIGTRAP)

[Red Hat Bugzilla]

Product: Fedora
https://bugzilla.redhat.com/show_bug.cgi?id=868333

fujiwara  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |CLOSED
         Resolution|---                         |WORKSFORME
              Flags|needinfo?(hufeng1987@gmail. |
                   |com)                        |
        Last Closed|                            |2012-12-10 05:37:29

--- Comment #11 from fujiwara  ---
If you still reproduce this problem, please comment here.