In Kubuntu 14.10 Printer Module crashes when clicking on the Configure button

[Michael]

I am filing this Bug manually because the debug symbols can not be found for this package steps and some crash report is below.

Steps:
1. I click on the printers module in Kde on Kubuntu 14.10.
2. I click on the configure button inside of the printer module and it crashes each time.
3. A bug reporting window opens.
4. I have let it install libqt4-dbg. I proceed with the bug reporting tool.
5. It tells me that it can not find the debug symbols for the backtrace for the package.
6. I manually save whatever it has to bring here instead of to KDE.org.

I Expected:
To be able to see the configuration box to be able to fine tune my printer settings.

I Witnessed:
It crashes each time performing the above.

Side Effects of What I Have Witnessed:
The Advanced printing tab in any KDE application is grayed out.

Crash Report As Possible:

Application: configure-printer (0.3.0)
KDE Platform Version: 4.14.1
Qt Version: 4.8.6
Operating System: Linux 3.16.0-29-generic x86_64
Distribution: Ubuntu 14.10

-- Information about the crash:
<In detail, tell us what you were doing when the application crashed.>

The crash can be reproduced every time.

-- Backtrace:
Application: ConfigurePrinter (configure-printer), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7eff528608c0 (LWP 5390))]

Thread 2 (Thread 0x7eff3f9f7700 (LWP 5391)):
#0 0x00007eff4fc6b3d6 in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x00007eff4be4bee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007eff4be4bffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3 0x00007eff510b804e in QEventDispatcherGlib::processEvents (this=0x7eff380008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4 0x00007eff510894f1 in QEventLoop::processEvents (this=this@entry=0x7eff3f9f6ce0, flags=...) at kernel/qeventloop.cpp:149
#5 0x00007eff51089805 in QEventLoop::exec (this=this@entry=0x7eff3f9f6ce0, flags=...) at kernel/qeventloop.cpp:204
#6 0x00007eff50f87c39 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#7 0x00007eff521d9a17 in KCupsConnection::run() () from /usr/lib/libkcupslib.so
#8 0x00007eff50f8a39f in QThreadPrivate::start (arg=0x14e8170) at thread/qthread_unix.cpp:349
#9 0x00007eff4eff70a5 in start_thread (arg=0x7eff3f9f7700) at pthread_create.c:309
#10 0x00007eff4fc7588d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7eff528608c0 (LWP 5390)):
[KCrash Handler]
#5 0x00007eff521df720 in KCupsRequest::errorMsg() const () from /usr/lib/libkcupslib.so
#6 0x00000000004134df in ?? ()
#7 0x0000000000413db9 in ?? ()
#8 0x0000000000418380 in ConfigureDialog::ConfigureDialog(QString const&, bool, QWidget*) ()
#9 0x000000000040bb26 in ?? ()
#10 0x0000000000419056 in ?? ()
#11 0x00007eff51415bf6 in QDBusConnectionPrivate::deliverCall (this=this@entry=0x135b700, object=object@entry=0x14e82b0, msg=..., metaTypes=..., slotIdx=4) at qdbusintegrator.cpp:951
#12 0x00007eff51416d29 in QDBusConnectionPrivate::activateCall (this=this@entry=0x135b700, object=0x14e82b0, flags=flags@entry=273, msg=...) at qdbusintegrator.cpp:856
#13 0x00007eff51417798 in QDBusConnectionPrivate::activateObject (this=0x135b700, node=..., msg=..., pathStartPos=<optimized out>) at qdbusintegrator.cpp:1427
#14 0x00007eff5141791b in QDBusActivateObjectEvent::placeMetaCall (this=0x14e9480) at qdbusintegrator.cpp:1541
#15 0x00007eff510a2f41 in QObject::event (this=0x14e81f0, e=<optimized out>) at kernel/qobject.cpp:1222
#16 0x00007eff5041711c in QApplicationPrivate::notify_helper (this=this@entry=0x13842a0, receiver=receiver@entry=0x14e81f0, e=e@entry=0x14e9480) at kernel/qapplication.cpp:4570
#17 0x00007eff5041d870 in QApplication::notify (this=0x7fff5f0122a0, receiver=0x14e81f0, e=0x14e9480) at kernel/qapplication.cpp:4356
#18 0x00007eff51d7857a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0x00007eff5108a86d in QCoreApplication::notifyInternal (this=0x7fff5f0122a0, receiver=receiver@entry=0x14e81f0, event=event@entry=0x14e9480) at kernel/qcoreapplication.cpp:953
#20 0x00007eff5108df41 in sendEvent (event=0x14e9480, receiver=0x14e81f0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#21 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x1343e60) at kernel/qcoreapplication.cpp:1577
#22 0x00007eff5108e3d3 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470
#23 0x00007eff510b7ed3 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#24 postEventSourceDispatch (s=0x1373c10) at kernel/qeventdispatcher_glib.cpp:287
#25 0x00007eff4be4bc5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#26 0x00007eff4be4bf48 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#27 0x00007eff4be4bffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#28 0x00007eff510b8031 in QEventDispatcherGlib::processEvents (this=0x1345340, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#29 0x00007eff504ba4e6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x00007eff510894f1 in QEventLoop::processEvents (this=this@entry=0x7fff5f0121e0, flags=...) at kernel/qeventloop.cpp:149
#31 0x00007eff51089805 in QEventLoop::exec (this=this@entry=0x7fff5f0121e0, flags=...) at kernel/qeventloop.cpp:204
#32 0x00007eff5108ef67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#33 0x000000000040b001 in ?? ()
#34 0x00007eff4fb9cec5 in __libc_start_main (main=0x40ad40, argc=1, argv=0x7fff5f0123e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff5f0123d8) at libc-start.c:287
#35 0x000000000040b072 in _start ()

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1412058/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Michael (mick-capricorn)]

I have added the package name that I am filing the Bug Report against.