Bug 210418 - Crash printing any pdf file on remote cups server
Summary: Crash printing any pdf file on remote cups server
Status: RESOLVED WORKSFORME
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: print-dialog (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2009-10-13 10:53 UTC by Iacopo
Modified: 2018-10-27 04:08 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Iacopo 2009-10-13 10:53:10 UTC
Application that crashed: okular
Version of the application: 0.9.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.30-2-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
When i print any pdf (both via Ctrl+P shortcut and via File-> Print) the printer dialog appears: whatever option/printer i choose okular crashes

 -- Backtrace:
Application: Okular (okular), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  0x00007f34cc350a56 in _cupsStrRetain () from /usr/lib/libcups.so.2
#6  0x00007f34cc333db5 in cupsAddDest () from /usr/lib/libcups.so.2
#7  0x00007f34cc33401e in ?? () from /usr/lib/libcups.so.2
#8  0x00007f34cc334bd7 in cupsGetDests2 () from /usr/lib/libcups.so.2
#9  0x00007f34e0d984ba in QCUPSSupport (this=0x7fff31da4780) at painting/qcups.cpp:136
#10 0x00007f34e0d2366e in QPrinter::init (this=0x7fff31da4840, mode=<value optimized out>) at painting/qprinter.cpp:668
#11 0x00007f34e0d239a9 in QPrinter (this=0x7fff31da4840, mode=QPrinter::ScreenResolution) at painting/qprinter.cpp:621
#12 0x00007f34d8992f82 in Part::slotPrint (this=0x9a3c90) at ../../okular/part.cpp:1889
#13 0x00007f34d89966fd in Part::qt_metacall (this=0x9a3c90, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff31da49f0) at ./part.moc:228
#14 0x00007f34e1763df2 in QMetaObject::activate (sender=0xc1e090, from_signal_index=<value optimized out>, to_signal_index=6, argv=0x8e) at kernel/qobject.cpp:3112
#15 0x00007f34e0bc2147 in QAction::triggered (this=0x1, _t1=false) at .moc/release-shared/moc_qaction.cpp:236
#16 0x00007f34e0bc35c0 in QAction::activate (this=0xc1e090, event=<value optimized out>) at kernel/qaction.cpp:1167
#17 0x00007f34e0fbe15d in QMenuPrivate::activateCausedStack (this=0xc37d70, causedStack=..., action=0xc1e090, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:967
#18 0x00007f34e0fc408f in QMenuPrivate::activateAction (this=0xc37d70, action=0xc1e090, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:1060
#19 0x00007f34e24347a1 in KMenu::mouseReleaseEvent (this=0xc4b050, e=0x7fff31da5630) at ../../kdeui/widgets/kmenu.cpp:456
#20 0x00007f34e0c1837f in QWidget::event (this=0xc4b050, event=0x7fff31da5630) at kernel/qwidget.cpp:7554
#21 0x00007f34e0fc67eb in QMenu::event (this=0xc4b050, e=0x7fff31da5630) at widgets/qmenu.cpp:2358
#22 0x00007f34e0bc801d in QApplicationPrivate::notify_helper (this=0x88ea30, receiver=0xc4b050, e=0x7fff31da5630) at kernel/qapplication.cpp:4065
#23 0x00007f34e0bd07ca in QApplication::notify (this=<value optimized out>, receiver=0xc4b050, e=0x7fff31da5630) at kernel/qapplication.cpp:3767
#24 0x00007f34e23630db in KApplication::notify (this=0x7fff31da73b0, receiver=0xc4b050, event=0x7fff31da5630) at ../../kdeui/kernel/kapplication.cpp:302
#25 0x00007f34e174ec9c in QCoreApplication::notifyInternal (this=0x7fff31da73b0, receiver=0xc4b050, event=0x7fff31da5630) at kernel/qcoreapplication.cpp:610
#26 0x00007f34e0bcfa78 in QCoreApplication::sendSpontaneousEvent (receiver=0xc4b050, event=0x7fff31da5630, alienWidget=0x0, nativeWidget=0xc4b050, buttonDown=<value optimized out>, 
    lastMouseReceiver=...) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#27 QApplicationPrivate::sendMouseEvent (receiver=0xc4b050, event=0x7fff31da5630, alienWidget=0x0, nativeWidget=0xc4b050, buttonDown=<value optimized out>, lastMouseReceiver=...)
    at kernel/qapplication.cpp:2924
#28 0x00007f34e0c38814 in QETWidget::translateMouseEvent (this=0xc4b050, event=<value optimized out>) at kernel/qapplication_x11.cpp:4345
#29 0x00007f34e0c3740f in QApplication::x11ProcessEvent (this=0x7fff31da73b0, event=0x7fff31da7000) at kernel/qapplication_x11.cpp:3552
#30 0x00007f34e0c5f76c in x11EventSourceDispatch (s=0x8927f0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#31 0x00007f34dd3ef12a in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#32 0x00007f34dd3f2988 in ?? () from /lib/libglib-2.0.so.0
#33 0x00007f34dd3f2b3c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#34 0x00007f34e177739c in QEventDispatcherGlib::processEvents (this=0x875790, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#35 0x00007f34e0c5ef1f in QGuiEventDispatcherGlib::processEvents (this=0x1, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#36 0x00007f34e174d562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#37 0x00007f34e174d934 in QEventLoop::exec (this=0x7fff31da7330, flags=...) at kernel/qeventloop.cpp:201
#38 0x00007f34e174fba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#39 0x00000000004081c4 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../okular/shell/main.cpp:81

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-14 03:22:17 UTC
Looks like a Qt/cups issue.
- Can you check if trying to print from any other KDE app trigger the same crash ?
Thanks
Comment 2 Iacopo 2009-10-14 08:19:03 UTC
Sorry i didn't checked that before reporting bug: other kde apps (kate, kdevelop) crashes in the same way.
Qt apps works regularly.
Comment 3 Dario Andres 2009-10-14 13:47:54 UTC
Thanks for checking
Comment 4 Christoph Feck 2013-09-12 21:36:28 UTC
This crash report is at least 3 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in recent KDE 4 versions or the backtrace is no longer applicable to the current KDE 4 sources.

If the crash still happens with a recent KDE version (4.10.5 or 4.11), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or CONFIRMED)
Comment 5 Andrew Crouthamel 2018-09-24 01:57:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 04:08:00 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!