Bug 695198 - [abrt] openoffice.org-writer-1:3.3.0-20.2.fc14: cupsGetDests (SIGABRT)
Summary: [abrt] openoffice.org-writer-1:3.3.0-20.2.fc14: cupsGetDests (SIGABRT)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: cups
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2f8417840e1e85407e26c1ea9ea...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-11 04:33 UTC by DemetrisK
Modified: 2012-08-16 16:34 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 16:34:02 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (116.93 KB, text/plain)
2011-04-11 04:33 UTC, DemetrisK
no flags Details

Description DemetrisK 2011-04-11 04:33:24 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 119739 bytes
cmdline: /usr/lib64/openoffice.org3/program/swriter.bin -writer file:///home/dimitris/%CE%88%CE%B3%CE%B3%CF%81%CE%B1%CF%86%CE%B1/%CE%BC%CF%85%CE%B8%CF%85%CF%83%CF%84%CF%8C%CF%81%CE%B7%CE%BC%CE%B1.odt
comment: usually reopening it after the first crash end up opening the file without crashing
component: openoffice.org
Attached file: coredump, 226721792 bytes
crash_function: __libc_message
executable: /usr/lib64/openoffice.org3/program/swriter.bin
kernel: 2.6.35.11-83.fc14.x86_64
package: openoffice.org-writer-1:3.3.0-20.2.fc14
rating: 4
reason: Process /usr/lib64/openoffice.org3/program/swriter.bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1302469168
uid: 500

How to reproduce
-----
1. open any file assigned to openoffice writter for the first time
2.
3.

Comment 1 DemetrisK 2011-04-11 04:33:45 UTC
Created attachment 491140 [details]
File: backtrace

Comment 2 Caolan McNamara 2011-04-11 08:18:18 UTC
Hmm, that lcl_signal_action is the handler that gets called by a SIGSEGV, SIGBUS or SIGABRT during cupsGetDests

What happens if you open e.g. gedit and go to file->print to get its print dialog up and visible ?

Comment 3 DemetrisK 2011-04-11 15:31:34 UTC
>What happens if you open e.g. gedit and go to file->print to get its print
dialog up and visible ?

No crash. The dialog is visible and I can use the functions alright.

Comment 4 Tim Waugh 2011-04-26 16:07:29 UTC
Caolan: how come there are no symbols in the libcups part of the stack trace?

Comment 5 Caolan McNamara 2011-05-27 13:35:28 UTC
twaugh: No idea. Presumably that's a question for the abrt/gdb people. That cupsGetDests is run in a thread, though that shouldn't affect getting symbols.

Comment 6 Fedora End Of Life 2012-08-16 16:34:05 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached 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 to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.