[Fedora-i18n-bugs] [Bug 981479] New: [abrt] imsettings-1.6.3-1.fc19: g_variant_iter_next_value: Process /usr/libexec/imsettings-check was killed by signal 11 (SIGSEGV)
https://bugzilla.redhat.com/show_bug.cgi?id=981479
Bug ID: 981479 Summary: [abrt] imsettings-1.6.3-1.fc19: g_variant_iter_next_value: Process /usr/libexec/imsettings-check was killed by signal 11 (SIGSEGV) Product: Fedora Version: 19 Component: imsettings Severity: unspecified Priority: unspecified Assignee: tagoh@redhat.com Reporter: j.mark.brooks@gmail.com QA Contact: extras-qa@fedoraproject.org CC: i18n-bugs@lists.fedoraproject.org, tagoh@redhat.com
Version-Release number of selected component: imsettings-1.6.3-1.fc19
Additional info: reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/imsettings-check --check-modulesettings -d crash_function: g_variant_iter_next_value executable: /usr/libexec/imsettings-check kernel: 3.9.8-300.fc19.x86_64 runlevel: N 5 uid: 1000 var_log_messages: Jul 4 17:39:37 localhost abrt[27341]: Saved core dump of pid 27334 (/usr/libexec/imsettings-check) to /var/tmp/abrt/ccpp-2013-07-04-17:39:37-27334 (9330688 bytes) xsession_errors:
Truncated backtrace: Thread no. 1 (3 frames) #0 g_variant_iter_next_value at gvariant.c:3032 #1 g_variant_iter_next at gvariant.c:4961 #2 _check_modules at imsettings-check.c:240
https://bugzilla.redhat.com/show_bug.cgi?id=981479
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |j.mark.brooks@gmail.com Flags| |needinfo?(j.mark.brooks@gma | |il.com)
--- Comment #10 from Akira TAGOH tagoh@redhat.com --- Is this issue reproducible? did it happen during logging into your desktop? can you attach $HOME/.cache/imsettings/log too?
https://bugzilla.redhat.com/show_bug.cgi?id=981479
--- Comment #11 from Fedora End Of Life endoflife@fedoraproject.org --- This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'.
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.
Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 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 this bug is closed as described in the policy above.
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.
https://bugzilla.redhat.com/show_bug.cgi?id=981479
Akira TAGOH tagoh@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |CURRENTRELEASE Flags|needinfo?(j.mark.brooks@gma | |il.com) | Last Closed| |2015-01-16 03:56:31
--- Comment #12 from Akira TAGOH tagoh@redhat.com --- Assuming this issue is gone in the latest version. please reopen if it still persists.
i18n-bugs@lists.fedoraproject.org
-
Red Hat Bugzilla