After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 686230 - Crashes on start
Crashes on start
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
: 685108 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-10-16 16:28 UTC by Bastien Nocera
Modified: 2012-10-17 13:37 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastien Nocera 2012-10-16 16:28:57 UTC
It crashes on startup because self->introspection_data is NULL. It's NULL, because the data isn't in a format that's understood. With a bit more debug:
** (file-roller:13920): CRITICAL **: Failed to parse D-Bus introspection data: 103:2: Error on line 103 char 2: Document must begin with an element (e.g. <book>)

  • #0 on_bus_acquired_for_archive_manager
    at main.c line 577
  • #1 connection_get_cb
    from /lib64/libgio-2.0.so.0
  • #2 g_simple_async_result_complete
    from /lib64/libgio-2.0.so.0
  • #3 complete_in_idle_cb
    from /lib64/libgio-2.0.so.0
  • #4 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #5 g_main_context_iterate.isra.24
    from /lib64/libglib-2.0.so.0
  • #6 g_main_context_iteration
    from /lib64/libglib-2.0.so.0
  • #7 g_application_run
    from /lib64/libgio-2.0.so.0
  • #8 main
    at main.c line 952

Comment 1 Paolo Bacchilega 2012-10-16 18:03:02 UTC
Can you please check if the problem is fixed in master now?
Comment 2 Bastien Nocera 2012-10-17 07:57:35 UTC
Works for me.
Comment 3 Paolo Bacchilega 2012-10-17 09:12:27 UTC
(In reply to comment #2)
> Works for me.

Does it write a warning message when started? I ask because I cannot reproduce the bug.
Comment 4 Bastien Nocera 2012-10-17 09:32:12 UTC
(In reply to comment #3)
> (In reply to comment #2)
> > Works for me.
> 
> Does it write a warning message when started? I ask because I cannot reproduce
> the bug.

Nothing related.
Comment 5 Paolo Bacchilega 2012-10-17 13:37:15 UTC
*** Bug 685108 has been marked as a duplicate of this bug. ***