Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After upgrading iceweasel to experimental, I no longer experienced any problems with running iceweasel under KDE.

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Version: 38.4.0esr-1 Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After the following upgrade, iceweasel locks up upon attempting to restore multiple windows,

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Version: 38.4.0esr-1 Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Still getting a lock-up when starting from the KDE start menu (resuming lots of windows and tabs), starts alright from command line

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Version: 38.4.0esr-1 Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Another normal run of iceweasel under a slightly different kernel than last time: [Thread

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Version: 38.4.0esr-1 Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After upgrading gcc-5 related packages to latest version in unstable, iceweasel locks up when

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Version: 38.4.0esr-1 Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? running iceweasel under gdb under KDE gdb iceweasel GNU gdb (Debian 7.10-1) 7.10 Copyright (C)

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Version: 38.4.0esr-1 Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? After upgrading packages based on qt5base-opensource-src from 5.5.1+dfsg-7 to 5.5.1+dfsq-8 I again

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Version: 38.4.0esr-1 Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Running iceweasel from a konsole prompt under KDE: [New Thread 0x7fffd19ff700 (LWP 5998)]

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Version: 38.4.0esr-1 Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** I'm again getting iceweasel locking up when running under KDE from unstable since the upgrade of libqt5* packages from 5.5.1+dfsg-6

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Version: 38.4.0esr-1 Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Problem has returned... will try running under gdb again soon. *** End of the template - remove these template lines *** --

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Followup-For: Bug #804060 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** After more upgrades in Debian unstable, the problem no-longer occurs. Please close this bug. *** End of the template - remove these template lines ***

Bug#804060: iceweasel: SIGPIPE when running under KDE

Package: iceweasel Version: 38.4.0esr-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Running current version or 38.3.0esr-1 of iceweasel under KDE, would get a lockup of KDE session when run