Bug 1008811

Summary: [abrt] glom-1.22.1-1.fc18: glibmm_unexpected_exception: Process /usr/bin/glom was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: Kris <kris.metzker>
Component: glomAssignee: Haïkel Guémar <karlthered>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: ben, karlthered, murrayc
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:aabbed58db73e5ea3db71a3dd325a529702a9582
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:24:03 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Kris 2013-09-17 06:47:16 UTC 
Description of problem:
Just installed the program, this was first start.
I have other errors that may or may not be related;

Sep 16 23:38:51 localhost kernel: [19121.512043] usb 2-5: reset high-speed USB device number 2 using ehci-pci
Sep 16 23:38:56 localhost gnome-keyring-daemon[12282]: gkd_secret_service_publish_dispatch: assertion `!g_hash_table_lookup (client->dispatch, path)' failed
Sep 16 23:39:43 localhost kernel: [19173.609075] sd 5:0:0:0: [sdb] Test WP failed, assume Write Enabled
Sep 16 23:38:50 localhost kernel: [19121.386808] sd 5:0:0:0: [sdb] Asking for cache data failed
Sep 16 23:38:50 localhost kernel: [19121.386812] sd 5:0:0:0: [sdb] Assuming drive cache: write through

I have nothing plugged into usb. Also, this laptop has been dropped.
Sorry I can't be more help. Thx.

Version-Release number of selected component:
glom-1.22.1-1.fc18

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        glom
crash_function: glibmm_unexpected_exception
executable:     /usr/bin/glom
kernel:         3.10.10-100.fc18.i686
runlevel:       N 5
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #2 glibmm_unexpected_exception at exceptionhandler.cc:71
 #3 Glib::exception_handlers_invoke at exceptionhandler.cc:150
 #4 Gio::Application_Class::activate_callback at application.cc:659
 #5 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115
 #6 g_type_class_meta_marshalv at gclosure.c:997
 #7 _g_closure_invoke_va at gclosure.c:840
 #10 g_application_activate at gapplication.c:1420
 #11 Gio::Application::activate at application.cc:867
 #12 Glom::Application::on_command_line at glom/application.cc:209
 #13 Gio::Application_Class::command_line_callback at application.cc:694

Potential duplicate: bug 982085
Comment 1 Kris 2013-09-17 06:47:22 UTC 
Created attachment 798625 [details]
File: backtrace
Comment 2 Kris 2013-09-17 06:47:27 UTC 
Created attachment 798626 [details]
File: cgroup
Comment 3 Kris 2013-09-17 06:47:34 UTC 
Created attachment 798627 [details]
File: core_backtrace
Comment 4 Kris 2013-09-17 06:47:40 UTC 
Created attachment 798628 [details]
File: dso_list
Comment 5 Kris 2013-09-17 06:47:45 UTC 
Created attachment 798629 [details]
File: environ
Comment 6 Kris 2013-09-17 06:47:53 UTC 
Created attachment 798630 [details]
File: limits
Comment 7 Kris 2013-09-17 06:47:58 UTC 
Created attachment 798631 [details]
File: maps
Comment 8 Kris 2013-09-17 06:48:08 UTC 
Created attachment 798632 [details]
File: open_fds
Comment 9 Kris 2013-09-17 06:48:12 UTC 
Created attachment 798633 [details]
File: proc_pid_status
Comment 10 Kris 2013-09-17 06:48:18 UTC 
Created attachment 798634 [details]
File: var_log_messages
Comment 11 Murray Cumming 2013-10-21 08:27:21 UTC 
If this problem can still be reproduced, it would be nice to see if any warnings appear when starting Glom from the command line (terminal).
Comment 12 Ben Konrath 2013-10-21 11:14:24 UTC 
*** Bug 1013378 has been marked as a duplicate of this bug. ***
Comment 13 Ben Konrath 2013-10-21 11:15:07 UTC 
Here's the output on Fedora 19:

% glom 
bool GlomBakery::Document::write_to_disk(): m_file_uri is empty.

(glom:3818): glibmm-ERROR **: 
unhandled exception (type std::exception) in signal handler:
what: Error code from xmlParseChunk(): 111

zsh: trace trap (core dumped)  glom
Comment 14 Murray Cumming 2013-10-21 11:24:17 UTC 
Thanks. Then it's another duplicate of bug #1013033.
Comment 15 Ben Konrath 2013-10-21 14:22:32 UTC 
Ok, thanks.
Comment 16 Fedora End Of Life 2013-12-21 14:35:54 UTC 
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.
Comment 17 Fedora End Of Life 2014-02-05 22:24:03 UTC 
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.