Summary: | After update : crash when new session is opened | ||
---|---|---|---|
Product: | [Unmaintained] printer-applet | Reporter: | Bruno Friedmann <bruno> |
Component: | general | Assignee: | Jonathan Riddell <jr> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | bruno |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
Bruno Friedmann
2011-08-03 08:13:50 UTC
Created attachment 62515 [details]
New crash information added by DrKonqi
python2 (1.7) on KDE Platform 4.7.00 (4.7.0) using Qt 4.7.3
- What I was doing when the application crashed: Tonight I come back on the network, where the printer was missing this morning.
So I plug the printer (power on) on the remote cups server, and it start to print all the pages. But in the meaning I get this crash.
I've also a constant nepomukstub crash segfault but without any backtrace.(even if all the debuginfo package are installed) I don't know if this is linked or not.
-- Backtrace (Reduced):
#6 QObject::startTimer (this=0x1044e30, interval=25000) at kernel/qobject.cpp:1601
[...]
#8 0x00007f1d4b7441ed in _dbus_timeout_list_add_timeout (timeout_list=0xebaef0, timeout=0xf33880) at dbus-timeout.c:320
#9 0x00007f1d4b7308c0 in _dbus_connection_attach_pending_call_unlocked (pending=0xea1c70, connection=0xef59b0) at dbus-connection.c:912
#10 dbus_connection_send_with_reply (connection=0xef59b0, message=0xf29080, pending_return=0x7fffc0650688, timeout_milliseconds=<optimized out>) at dbus-connection.c:3403
#11 0x00007f1d4b730b29 in dbus_connection_send_with_reply_and_block (connection=0xef59b0, message=0xf29080, timeout_milliseconds=-1, error=0x7fffc06506c0) at dbus-connection.c:3501
*** This bug has been marked as a duplicate of bug 278857 *** |