Bug 1096181

Summary: [abrt][KDE] libreoffice-core: poll(): soffice.bin killed by SIGABRT
Product: [Fedora] Fedora Reporter: Vaso VV <fuckel>
Component: libreofficeAssignee: Lukáš Tinkl <ltinkl>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: caolanm, dtardon, erack, jgrulich, ltinkl, mstahl, sbergman
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/190cdb81b070cd5b4f1f364cb8b7f67a8e388e49
Whiteboard: abrt_hash:2a6d1d687eb8a0601539c9698e6b5361343e6aa3
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 20:32:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: hs_err.log
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Vaso VV 2014-05-09 11:19:30 UTC
Description of problem:
1. Open new spreadsheet
2. Go to  Tools / Macros / Organize macros / LibreOffice Basic…
3. In "Macro form" find "Module1" under "My Macros / Standart" then hold it by mouse left click and make some movement (by mouse of cause))
4. Voilà! LibreOffice is successfully crushed.

Version-Release number of selected component:
libreoffice-core-4.2.3.3-9.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        /usr/lib64/libreoffice/program/soffice.bin --calc file:///tmp/000/now-listener.ods --splash-pipe=5
crash_function: poll
executable:     /usr/lib64/libreoffice/program/soffice.bin
kernel:         3.14.3-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1002

Truncated backtrace:
[New LWP 4486]
[New LWP 4503]
[New LWP 4491]
[New LWP 4506]
[New LWP 4497]
[New LWP 4508]
[New LWP 4510]
[New LWP 4511]
[New LWP 4480]
[New LWP 4505]
[New LWP 4504]
[New LWP 4507]
[New LWP 4509]
[New LWP 4525]
[New LWP 4513]
[New LWP 4484]
[New LWP 4512]
[New LWP 4514]
[New LWP 4479]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Traceback (most recent call last):
  File "/usr/share/gdb/auto-load/usr/lib64/libgobject-2.0.so.0.3800.2-gdb.py", line 9, in <module>
    from gobject import register
  File "/usr/share/glib-2.0/gdb/gobject.py", line 3, in <module>
    import gdb.backtrace
ImportError: No module named backtrace
warning: File "/var/cache/abrt-di/usr/lib/debug/usr/lib64/libpython3.3m.so.1.0.debug-gdb.py" auto-loading has been declined by your `auto-load safe-path' set to "$debugdir:$datadir/auto-load:/usr/bin/mono-gdb.py".
To enable execution of this file add
	add-auto-load-safe-path /var/cache/abrt-di/usr/lib/debug/usr/lib64/libpython3.3m.so.1.0.debug-gdb.py
line to your configuration file "/home/neuser/.gdbinit".
To completely disable this security protection add
	set auto-load safe-path /
line to your configuration file "/home/neuser/.gdbinit".
For more information about this security protection see the
"Auto-loading safe path" section in the GDB manual.  E.g., run from the shell:
	info "(gdb)Auto-loading safe path"
Core was generated by `/usr/lib64/libreoffice/program/soffice.bin --calc file:///tmp/000/now-listener.'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00000033d0035c39 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56	  return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig);

Thread 19 (Thread 0x7fc97c703880 (LWP 4479)):
#0  0x00000033d00ea9dd in poll () at ../sysdeps/unix/syscall-template.S:81
No locals.
#1  0x00007fc9755507fd in gpoll_wrapper (ufds=ufds@entry=0x253da80, nfds=nfds@entry=4, timeout=timeout@entry=499) at /usr/src/debug/libreoffice-4.2.3.3/vcl/unx/kde4/KDEXLib.cxx:274
        release = {m_nYieldCount = 3}
#2  0x00000033d38495b4 in g_main_context_poll (priority=2147483647, n_fds=4, fds=0x253da80, timeout=499, context=0x1932a70) at gmain.c:4007
        poll_func = 0x7fc9755507c0 <gpoll_wrapper(GPollFD*, guint, gint)>
#3  g_main_context_iterate (context=context@entry=0x1932a70, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3708
        max_priority = 2147483647
        timeout = 499
        some_ready = <optimized out>
        nfds = 4
        allocated_nfds = 4
        fds = 0x253da80
#4  0x00000033d38496dc in g_main_context_iteration (context=0x1932a70, may_block=1) at gmain.c:3774
        retval = <optimized out>
#5  0x00007fc9751f9ad5 in QEventDispatcherGlib::processEvents (this=0x1927b40, flags=...) at kernel/qeventdispatcher_glib.cpp:425
        d = 0x18f1b90
        canWait = <optimized out>
        savedFlags = {i = 0}
        result = <optimized out>
#6  0x00007fc9745ced66 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
        d = 0x18f1b90
        saved_flags = {i = 0}
Timeout exceeded: 240 seconds, killing gdb.
Looks like gdb hung while generating backtrace.
This may be a bug in gdb. Consider submitting a bug report to gdb developers.
Please attach coredump from this crash to the bug report if you do.

Comment 1 Vaso VV 2014-05-09 11:19:39 UTC
Created attachment 894004 [details]
File: backtrace

Comment 2 Vaso VV 2014-05-09 11:19:41 UTC
Created attachment 894005 [details]
File: cgroup

Comment 3 Vaso VV 2014-05-09 11:19:43 UTC
Created attachment 894006 [details]
File: core_backtrace

Comment 4 Vaso VV 2014-05-09 11:19:46 UTC
Created attachment 894007 [details]
File: dso_list

Comment 5 Vaso VV 2014-05-09 11:19:48 UTC
Created attachment 894008 [details]
File: environ

Comment 6 Vaso VV 2014-05-09 11:19:51 UTC
Created attachment 894009 [details]
File: hs_err.log

Comment 7 Vaso VV 2014-05-09 11:19:53 UTC
Created attachment 894010 [details]
File: limits

Comment 8 Vaso VV 2014-05-09 11:19:56 UTC
Created attachment 894011 [details]
File: maps

Comment 9 Vaso VV 2014-05-09 11:19:58 UTC
Created attachment 894012 [details]
File: open_fds

Comment 10 Vaso VV 2014-05-09 11:20:00 UTC
Created attachment 894013 [details]
File: proc_pid_status

Comment 11 Vaso VV 2014-05-09 11:20:02 UTC
Created attachment 894014 [details]
File: var_log_messages

Comment 12 Vaso VV 2014-05-09 11:27:56 UTC
(In reply to Vaso VV from comment #0)
> Description of problem:
> 1. Open new spreadsheet
> 2. Go to  Tools / Macros / Organize macros / LibreOffice Basic…
> 3. In "Macro form" find "Module1" under "My Macros / Standart" then hold it
> by mouse left click and make some movement (by mouse of cause))
Sorry! Not in "Macro form" but in "Organizer…" Modules tab you should try to drug the Module1 to reproduce the bug.

Comment 13 Stephan Bergmann 2014-05-12 10:46:34 UTC
cannot reproduce under gnome, attached dso_list shows this is under kde

Comment 14 Vaso VV 2014-05-12 11:37:38 UTC
Cann't reproduce after update to 4.2.4.2, but as I can see it was realized by disabling KDE integration (LibreOffice dialogs is used in spite of this option is disable).

Comment 15 Fedora End Of Life 2015-05-29 11:48:16 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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 20 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.

Comment 16 Fedora End Of Life 2015-06-29 20:32:31 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.