Summary: | crash when I exit presentation mode and enter again | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Patrick Silva <bugseforuns> |
Component: | general | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | aacid, giampisalvi, haxtibal, lucl, nikolaj, pedrogabrieldp, sebastian.englbrecht, sebastian.englbrecht, xionbox33418 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Patrick Silva
2018-04-24 20:37:25 UTC
the backtrace is very strange. Can you try running okular under valgrind valgrind okular myfile.pdf and attaching the output you get when doing the same steps? $ valgrind okular o_futuro_roubado_completo.pdf ==24308== Memcheck, a memory error detector ==24308== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==24308== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info ==24308== Command: okular o_futuro_roubado_completo.pdf ==24308== --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0: --24308-- Ignoring non-Dwarf2/3/4 block in .debug_info --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0: --24308-- Last block truncated in .debug_info; ignoring --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0: --24308-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0: --24308-- Ignoring non-Dwarf2/3/4 block in .debug_info --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0: --24308-- Last block truncated in .debug_info; ignoring --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0: --24308-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2: --24308-- Ignoring non-Dwarf2/3/4 block in .debug_info --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2: --24308-- Last block truncated in .debug_info; ignoring --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2: --24308-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5.45.0: --24308-- Ignoring non-Dwarf2/3/4 block in .debug_info --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5.45.0: --24308-- Last block truncated in .debug_info; ignoring --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libKF5WaylandClient.so.5.45.0: --24308-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.10.0: --24308-- Ignoring non-Dwarf2/3/4 block in .debug_info --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.10.0: --24308-- Last block truncated in .debug_info; ignoring --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5.10.0: --24308-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0.3.0: --24308-- Ignoring non-Dwarf2/3/4 block in .debug_info --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0.3.0: --24308-- Last block truncated in .debug_info; ignoring --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0.3.0: --24308-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/qt5/plugins/phonon_platform/kde.so: --24308-- Ignoring non-Dwarf2/3/4 block in .debug_info --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/qt5/plugins/phonon_platform/kde.so: --24308-- Last block truncated in .debug_info; ignoring --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/qt5/plugins/phonon_platform/kde.so: --24308-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4800.2: --24308-- Ignoring non-Dwarf2/3/4 block in .debug_info --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4800.2: --24308-- Last block truncated in .debug_info; ignoring --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.4800.2: --24308-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4800.2: --24308-- Ignoring non-Dwarf2/3/4 block in .debug_info --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4800.2: --24308-- Last block truncated in .debug_info; ignoring --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.4800.2: --24308-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0.4800.2: --24308-- Ignoring non-Dwarf2/3/4 block in .debug_info --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0.4800.2: --24308-- Last block truncated in .debug_info; ignoring --24308-- WARNING: Serious error when reading debug info --24308-- When reading debug info from /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0.4800.2: --24308-- parse_CU_Header: is neither DWARF2 nor DWARF3 nor DWARF4 KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon ==24308== Syscall param writev(vector[...]) points to uninitialised byte(s) ==24308== at 0x8D44FFD: ??? (syscall-template.S:84) ==24308== by 0xBC18F28: ??? (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==24308== by 0xBC1931C: ??? (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==24308== by 0xBC19A76: ??? (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==24308== by 0xBC19C43: xcb_flush (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==24308== by 0x14AC3066: QXcbWindow::setCursor(unsigned int, bool) (in /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.10.0) ==24308== by 0x14ACF5A5: ??? (in /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.10.0) ==24308== by 0x767264C: QWindowPrivate::applyCursor() (in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.10.0) ==24308== by 0x767647B: QWindowPrivate::setCursor(QCursor const*) (in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.10.0) ==24308== by 0x6E5C228: ??? (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.10.0) ==24308== by 0x6E66638: QWidget::setCursor(QCursor const&) (in /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5.10.0) ==24308== by 0x614B855: ??? (in /usr/lib/x86_64-linux-gnu/libKF5WidgetsAddons.so.5.45.0) ==24308== Address 0x143380c6 is 4,582 bytes inside a block of size 21,152 alloc'd ==24308== at 0x4C2FB55: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==24308== by 0xBC188DB: xcb_connect_to_fd (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==24308== by 0xBC1C610: xcb_connect_to_display_with_auth_info (in /usr/lib/x86_64-linux-gnu/libxcb.so.1.1.0) ==24308== by 0x9C2E809: _XConnectXCB (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0) ==24308== by 0x9C1F391: XOpenDisplay (in /usr/lib/x86_64-linux-gnu/libX11.so.6.3.0) ==24308== by 0x14AA9B40: QXcbConnection::QXcbConnection(QXcbNativeInterface*, bool, unsigned int, char const*) (in /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.10.0) ==24308== by 0x14AAFD38: QXcbIntegration::QXcbIntegration(QStringList const&, int&, char**) (in /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5.10.0) ==24308== by 0x1486432C: ??? (in /usr/lib/x86_64-linux-gnu/qt5/plugins/platforms/libqxcb.so) ==24308== by 0x76535AA: QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) (in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.10.0) ==24308== by 0x7663120: QGuiApplicationPrivate::createPlatformIntegration() (in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.10.0) ==24308== by 0x7663BEC: QGuiApplicationPrivate::createEventDispatcher() (in /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5.10.0) ==24308== by 0x8469638: QCoreApplicationPrivate::init() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon KActivities: FATAL ERROR: Failed to contact the activity manager daemon Invalid write to eventfd: Bad file descriptor Code should not be reached at pulsecore/fdsem.c:199, function pa_fdsem_post(). Aborting. KCrash: crashing... crashRecursionCounter = 2 KCrash: Application Name = okular path = /usr/bin pid = 24308 KCrash: Arguments: /usr/bin/okular o_futuro_roubado_completo.pdf KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5__0 QSocketNotifier: Invalid socket 9 and type 'Read', disabling... ==24308== Thread 3 QDBusConnectionManager: ==24308== Invalid read of size 2 ==24308== at 0x84B9479: socketNotifierSourceCheck(_GSource*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0xE0C4DC0: g_main_context_check (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0xE0C532F: g_main_context_iterate.isra.29 (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0xE0C549B: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0x84B95AE: QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x8460649: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x8280553: QThread::exec() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x7F612C4: QDBusConnectionManager::run() (in /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0) ==24308== by 0x82856EA: QThreadPrivate::start(void*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0xC03B6B9: start_thread (pthread_create.c:333) ==24308== by 0x8D4F41C: clone (clone.S:109) ==24308== Address 0x18e92cf6 is 6 bytes inside a block of size 16 free'd ==24308== at 0x4C2F24B: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==24308== by 0x849B9A5: QSocketNotifier::setEnabled(bool) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x84B9478: socketNotifierSourceCheck(_GSource*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0xE0C4DC0: g_main_context_check (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0xE0C532F: g_main_context_iterate.isra.29 (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0xE0C549B: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0x84B95AE: QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x8460649: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x8280553: QThread::exec() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x7F612C4: QDBusConnectionManager::run() (in /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0) ==24308== by 0x82856EA: QThreadPrivate::start(void*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0xC03B6B9: start_thread (pthread_create.c:333) ==24308== Block was alloc'd at ==24308== at 0x4C2E0EF: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==24308== by 0x84BA0F1: QEventDispatcherGlib::registerSocketNotifier(QSocketNotifier*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x849B827: QSocketNotifier::QSocketNotifier(long long, QSocketNotifier::Type, QObject*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x7F6EE3C: qDBusAddWatch (in /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0) ==24308== by 0xCFDED91: _dbus_watch_list_set_functions (in /lib/x86_64-linux-gnu/libdbus-1.so.3.14.6) ==24308== by 0xCFC506E: dbus_connection_set_watch_functions (in /lib/x86_64-linux-gnu/libdbus-1.so.3.14.6) ==24308== by 0x7F71560: QDBusConnectionPrivate::setConnection(DBusConnection*, QDBusErrorInternal const&) (in /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0) ==24308== by 0x7F630C3: QDBusConnectionManager::executeConnectionRequest(QDBusConnectionManager::ConnectionRequestData*) (in /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0) ==24308== by 0x84904C8: QObject::event(QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x84623BA: QCoreApplication::notifyInternal2(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x8464FCA: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x84B9FA2: postEventSourceDispatch(_GSource*, int (*)(void*), void*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== ==24308== Invalid read of size 2 ==24308== at 0x84B9404: socketNotifierSourceCheck(_GSource*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0xE0C4DC0: g_main_context_check (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0xE0C532F: g_main_context_iterate.isra.29 (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0xE0C549B: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0x84B95AE: QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x8460649: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x8280553: QThread::exec() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x7F612C4: QDBusConnectionManager::run() (in /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0) ==24308== by 0x82856EA: QThreadPrivate::start(void*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0xC03B6B9: start_thread (pthread_create.c:333) ==24308== by 0x8D4F41C: clone (clone.S:109) ==24308== Address 0x18e92cf4 is 4 bytes inside a block of size 16 free'd ==24308== at 0x4C2F24B: operator delete(void*) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==24308== by 0x849B9A5: QSocketNotifier::setEnabled(bool) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x84B9478: socketNotifierSourceCheck(_GSource*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0xE0C4DC0: g_main_context_check (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0xE0C532F: g_main_context_iterate.isra.29 (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0xE0C549B: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.4800.2) ==24308== by 0x84B95AE: QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x8460649: QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x8280553: QThread::exec() (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x7F612C4: QDBusConnectionManager::run() (in /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0) ==24308== by 0x82856EA: QThreadPrivate::start(void*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0xC03B6B9: start_thread (pthread_create.c:333) ==24308== Block was alloc'd at ==24308== at 0x4C2E0EF: operator new(unsigned long) (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==24308== by 0x84BA0F1: QEventDispatcherGlib::registerSocketNotifier(QSocketNotifier*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x849B827: QSocketNotifier::QSocketNotifier(long long, QSocketNotifier::Type, QObject*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x7F6EE3C: qDBusAddWatch (in /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0) ==24308== by 0xCFDED91: _dbus_watch_list_set_functions (in /lib/x86_64-linux-gnu/libdbus-1.so.3.14.6) ==24308== by 0xCFC506E: dbus_connection_set_watch_functions (in /lib/x86_64-linux-gnu/libdbus-1.so.3.14.6) ==24308== by 0x7F71560: QDBusConnectionPrivate::setConnection(DBusConnection*, QDBusErrorInternal const&) (in /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0) ==24308== by 0x7F630C3: QDBusConnectionManager::executeConnectionRequest(QDBusConnectionManager::ConnectionRequestData*) (in /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5.10.0) ==24308== by 0x84904C8: QObject::event(QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x84623BA: QCoreApplication::notifyInternal2(QObject*, QEvent*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x8464FCA: QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== by 0x84B9FA2: postEventSourceDispatch(_GSource*, int (*)(void*), void*) (in /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.10.0) ==24308== QSocketNotifier: Invalid socket 17 and type 'Read', disabling... QSocketNotifier: Invalid socket 10 and type 'Read', disabling... [1]+ Stopped valgrind okular o_futuro_roubado_completo.pdf Invalid write to eventfd: Bad file descriptor Code should not be reached at pulsecore/fdsem.c:199, function pa_fdsem_post(). Aborting. This tells me there's something wrong going with your pulseaudio. Which version are you using? Maybe you should try opening a pulseaudio bug? My neon dev unstable runs pulseaudio 8.0. I can not reproduce the crash on Arch Linux running pulseaudio 11.1 and okular 1.4.0 I just noticed something: on neon okular shown a message when I changed to presentation mode talking about ways to exit (ESC key and a button). After I check "do not show again" I can not reproduce the crash anymore. Okular does not show such message on Arch Linux. (In reply to Dr. Chapatin from comment #4) > Okular does not show such message on Arch Linux. I'm 99.99999% sure it does, it's probably that you already pressed "don't show again" before, no? (In reply to Albert Astals Cid from comment #5) > (In reply to Dr. Chapatin from comment #4) > > Okular does not show such message on Arch Linux. > > I'm 99.99999% sure it does, it's probably that you already pressed "don't > show again" before, no? Maybe. However I do not remember it. Duplicate of bug 394226? Most probably *** Bug 398720 has been marked as a duplicate of this bug. *** I can also reproduce this bug Kubuntu 18.04 Okular 1.3.3 Pulsaudio 11.1 Is there a big ID for Pulsaudio? I can reproduce the bug and will have a look into it. Someone closed libpulses eventfd(2), while libpulse continues to write to it. A write to the already closed fd in pa_fdsem_post then triggers assertion. I modified pulseaudio to get a bit more debug info: $ strace -e close ./okular 2>&1 [...] close(19) = 0 close(15) = 0 # who is doing that? and why? close(15) = 0 close(15) = 0 close(19) = 0 close(21) = 0 [...] Invalid write to eventfd: fd=15, r=-1, errno=9 # pa_fdsem_post tried writing fd 15, too late, already closed I think next thing to check is where the close happened. Could be okular, Qt, or pulseaudio itself. Ok, got it. It's this place in PresentationWidget::inhibitPowerManagement m_sleepInhibitCookie = reply.value().fileDescriptor(); We must not store QDBusUnixFileDescriptor::fileDescriptor, but clone it before. From http://doc.qt.io/qt-5/qdbusunixfiledescriptor.html#fileDescriptor "It is ok to use it while this object is valid, but if one wants to store it for longer use, the file descriptor should be cloned using the Unix dup(2), dup2(2) or dup3(2) functions." Changing the code to m_sleepInhibitCookie = dup( reply.value().fileDescriptor() ); avoids crashing. Let me gather a bit more context to see if it's really that simple, then I'll send a patch at Phabricator. Maybe one can try and confirm the above code change in the meantime? Tobias fixed this, he forgot to use the correct syntax so it did not autoclose. https://cgit.kde.org/okular.git/commit/?id=fa7a1b3d0674b234a61ac784dd879ad705a2f515 Thank you Tobias! For me it worked :) *** Bug 394226 has been marked as a duplicate of this bug. *** *** Bug 394824 has been marked as a duplicate of this bug. *** *** Bug 401428 has been marked as a duplicate of this bug. *** *** Bug 404078 has been marked as a duplicate of this bug. *** *** Bug 419030 has been marked as a duplicate of this bug. *** |