[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=393478

Albert Astals Cid  changed:

   What|Removed |Added

 CC||giampisa...@gmail.com

--- Comment #19 from Albert Astals Cid  ---
*** Bug 419030 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=393478

Albert Astals Cid  changed:

   What|Removed |Added

 CC||xionbox33...@gmail.com

--- Comment #18 from Albert Astals Cid  ---
*** Bug 404078 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=393478

Albert Astals Cid  changed:

   What|Removed |Added

 CC||l...@pt.lu

--- Comment #17 from Albert Astals Cid  ---
*** Bug 401428 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Tobias Deiminger]

https://bugs.kde.org/show_bug.cgi?id=393478

Tobias Deiminger  changed:

   What|Removed |Added

 CC||niko...@iversenmail.dk

--- Comment #16 from Tobias Deiminger  ---
*** Bug 394824 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=393478

Albert Astals Cid  changed:

   What|Removed |Added

 CC||japabras...@gmail.com

--- Comment #15 from Albert Astals Cid  ---
*** Bug 394226 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Nopeinger]

https://bugs.kde.org/show_bug.cgi?id=393478

Nopeinger  changed:

   What|Removed |Added

 CC||sebastian.englbrecht@kabelm
   ||ail.de

--- Comment #14 from Nopeinger  ---
Thank you Tobias!
For me it worked :)

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=393478

Albert Astals Cid  changed:

   What|Removed |Added

 Status|NEEDSINFO   |RESOLVED
 Resolution|WAITINGFORINFO  |FIXED

--- Comment #13 from Albert Astals Cid  ---
Tobias fixed this, he forgot to use the correct syntax so it did not autoclose.

https://cgit.kde.org/okular.git/commit/?id=fa7a1b3d0674b234a61ac784dd879ad705a2f515

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Tobias Deiminger]

https://bugs.kde.org/show_bug.cgi?id=393478

--- Comment #12 from Tobias Deiminger  ---
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?

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Tobias Deiminger]

https://bugs.kde.org/show_bug.cgi?id=393478

Tobias Deiminger  changed:

   What|Removed |Added

 CC||haxti...@posteo.de

--- Comment #11 from Tobias Deiminger  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=393478

--- Comment #10 from sebastian.englbre...@tum.de ---
I can also reproduce this bug

Kubuntu 18.04
Okular 1.3.3
Pulsaudio 11.1

Is there a big ID for Pulsaudio?

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[bugzilla_noreply]

https://bugs.kde.org/show_bug.cgi?id=393478

sebastian.englbre...@tum.de changed:

   What|Removed |Added

 CC||sebastian.englbre...@tum.de

--- Comment #9 from sebastian.englbre...@tum.de ---
*** Bug 398720 has been marked as a duplicate of this bug. ***

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=393478

--- Comment #8 from Albert Astals Cid  ---
Most probably

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Christoph Feck]

https://bugs.kde.org/show_bug.cgi?id=393478

--- Comment #7 from Christoph Feck  ---
Duplicate of bug 394226?

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Dr . Chapatin]

https://bugs.kde.org/show_bug.cgi?id=393478

--- Comment #6 from Dr. Chapatin  ---
(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.9% sure it does, it's probably that you already pressed "don't
> show again" before, no?

Maybe. However I do not remember it.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=393478

--- Comment #5 from Albert Astals Cid  ---
(In reply to Dr. Chapatin from comment #4)
> Okular does not show such message on Arch Linux.

I'm 99.9% sure it does, it's probably that you already pressed "don't show
again" before, no?

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Dr . Chapatin]

https://bugs.kde.org/show_bug.cgi?id=393478

--- Comment #4 from Dr. Chapatin  ---
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.

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=393478

--- Comment #3 from Albert Astals Cid  ---
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?

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Dr . Chapatin]

https://bugs.kde.org/show_bug.cgi?id=393478

--- Comment #2 from Dr. Chapatin  ---
$ 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 

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Albert Astals Cid]

https://bugs.kde.org/show_bug.cgi?id=393478

Albert Astals Cid  changed:

   What|Removed |Added

 Status|UNCONFIRMED |NEEDSINFO
 Resolution|--- |WAITINGFORINFO
 CC||aa...@kde.org

--- Comment #1 from Albert Astals Cid  ---
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?

-- 
You are receiving this mail because:
You are watching all bug changes.

[okular] [Bug 393478] crash when I exit presentation mode and enter again

[Dr . Chapatin]

https://bugs.kde.org/show_bug.cgi?id=393478

Dr. Chapatin  changed:

   What|Removed |Added

Summary|crash when I exit   |crash when I exit
   |presentention mode and  |presentation mode and enter
   |enter again |again

-- 
You are receiving this mail because:
You are watching all bug changes.