[okular] [Bug 472764] PDF form dropdown doesn't show up

[Juan Navarro]

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

--- Comment #3 from Juan Navarro  ---
(In reply to Albert Astals Cid from comment #2)
> Git commit 532cb0cdcdd008fedb42f0a3ec690400b65820e1 by Albert Astals Cid.
> Committed on 05/08/2023 at 20:20.
> Pushed by aacid into branch 'master'.
> 
> Initial implementation of app.popUpMenuEx
> 
> It is defenitely not a full implementation but it's enough for the one
> file we have that needs it for now
> 

Thank you very much for your work! Okular now will be better PDF viewer than
others even the pdf.js used in browsers, where the menu didn't show up either
for me :)

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

[okular] [Bug 472764] New: PDF form dropdown doesn't show up

[Juan Navarro]

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

Bug ID: 472764
   Summary: PDF form dropdown doesn't show up
Classification: Applications
   Product: okular
   Version: 23.04.3
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: oneorj...@gmail.com
  Target Milestone: ---

Created attachment 160598
  --> https://bugs.kde.org/attachment.cgi?id=160598=edit
Video showing the expected behavior (using Acrobat Reader)

SUMMARY

A PDF form contains dropdowns with selectable choices. These don't show up in
Okular.

Using Okular v23.04.3, the latest version available in Flathub
(https://flathub.org/apps/org.kde.okular) as of today. Underlying platform is
Ubuntu 20.04.


STEPS TO REPRODUCE

1. Open the PDF file that was attached to bug report #472756
(https://bugs.kde.org/show_bug.cgi?id=472756). I'm just linking to the other
bug report in order to save on storage; if it's preferred that each report has
its own attachments, please tell me and I will duplicate it here.

2. A header bar shows up in Okular, saying that "This document has forms. Click
on the button to interact with them, or use View -> Show Forms."
Click the "Show Forms" button.

3. On the left-half of the document, on the very first cell of the table
(top-left) containing the text "Calle, plaza, avda., etc.", there is a
dropdown.
Pushing on its button does nothing.

4. On the right-half of the document, on the cell of the table containing the
text "Nivel de estudios terminados", there is a dropdown.
Pushing on its button does nothing.


OBSERVED RESULT

* Pushing on the dropdown of step 3 does nothing. The list of choices doesn't
show up.
* Pushing on the dropdown of step 4 does nothing. The list of choices doesn't
show up.


EXPECTED RESULT

* Pushing on the dropdown of step 3 shows a list of strings. Selecting one,
puts the text of that entry into the nearby text field.
* Pushing on the dropdown of step 4 shows a list of numbered strings. Selecting
one, puts the number of that entry into the nearby text field.


SOFTWARE/OS VERSIONS

As per Flatpak package indicated above:
NameDescription  Application ID  Version  Branch 
Remotes
Okular  Document Viewer  org.kde.okular  23.04.3  stable 
flathub

Running on an Ubuntu 20.04 system.


ADDITIONAL INFORMATION

The exact same issue can be seen in other programs tested:
* Xreader v3.2.2
* Firefox v115
* Chromium v114

Given that it doesn't work elsewhere, I'm inclined to think that it might be a
problem with the PDF file itself, and not a problem with Okular. Nevertheless,
I'm reporting as maybe this opens up the chance to improve something in Okular.

Attaching a screen capture video where the expected behavior is shown.
This was captured using Acrobat Reader on Windows.
Both dropdowns described at steps 3 and 4 show up and allow to select a single
option.

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

[okular] [Bug 472756] Infinite modal dialog in PDF form

[Juan Navarro]

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

--- Comment #2 from Juan Navarro  ---
Created attachment 160597
  --> https://bugs.kde.org/attachment.cgi?id=160597=edit
Video showing the expected behavior (using Acrobat Reader)

Attaching a screen capture video where the expected behavior is shown.
This was captured using Acrobat Reader on Windows.
The "DNI", "Pasaporte" and "NIE" boxes can be marked as selected right away.
The "T", "P", and "C" boxes should show the modal dialog once, and afterwards
they get marked as selected.

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

[okular] [Bug 472756] Infinite modal dialog in PDF form

[Juan Navarro]

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

--- Comment #1 from Juan Navarro  ---
Further info:

This dialog doesn't show up at all in other PDF viewers I've tested:
* Xreader v3.2.2
* Firefox v115
* Chromium v114

While these are indeed missing to show part of the PDF form to the user, the
lucky consequence of that is that it becomes possible to actually fill the form
successfully.

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

[okular] [Bug 472756] New: Infinite modal dialog in PDF form

[Juan Navarro]

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

Bug ID: 472756
   Summary: Infinite modal dialog in PDF form
Classification: Applications
   Product: okular
   Version: 23.04.3
  Platform: Flatpak
OS: Linux
Status: REPORTED
  Severity: major
  Priority: NOR
 Component: PDF backend
  Assignee: okular-de...@kde.org
  Reporter: oneorj...@gmail.com
  Target Milestone: ---

Created attachment 160593
  --> https://bugs.kde.org/attachment.cgi?id=160593=edit
Sample PDF file

SUMMARY

A modal dialog is shown by the PDF form I'm trying to fill. It is just an
informative dialog. The problem is that once closed, it shows up immediately
again. This repeats indefinitely, which causes the form to be unfillable, and
what's worse, Okular is captive in this dialog-loop, so it cannot be even
closed by normal means.

Using Okular v23.04.3, the latest version available in Flathub
(https://flathub.org/apps/org.kde.okular) as of today. Underlying platform is
Ubuntu 20.04.


STEPS TO REPRODUCE

1. Open the PDF file that I'm attaching to this report.

2. A header bar shows up in Okular, saying that "This document has forms. Click
on the button to interact with them, or use View -> Show Forms."
Click the "Show Forms" button.

3. On the right-half of the document, on the first row that contains this text:
(2) Tipo de documento de identidad
DNI  Pasaporte  NIE  T. Residencia

Click on any of the checkboxes. For example, click on the checkbox under "DNI".

4. A dialog appears with this text:
(1) En caso de Tarjeta de Residencia, indicar T (Temporal), P(Permanente),
C(Comunitaria)

And an OK button.


OBSERVED RESULT

Pressing the OK button closes the dialog, but it immediately appears again.
The application is then permanently captured by this modal dialog, and neither
of progressing with filling the form, or closing Okular, is possible.


EXPECTED RESULT

Pressing the OK button would close the dialog permanently.

IF the reappearance of the dialog is caused by bad viewer logic of Okular:

* Okular should be fixed to improve compatibility with documents like this one.

IF the issue is caused by faulty logic of the document itself, and is not an
issue in Okular itself, then:

* Okular might try to be useful: detect the case and inform the user about it.
* Okular ought to not allow a faulty document to make it into a dialog loop.
For this, a reappearance limit would be a good idea, either as a fixed limit or
as a UI checkbox in the dialog, giving the user the chance to silence future
instances of that dialog. This is a pattern that I have seen successfully
implemented in other software, such as web browsers.


SOFTWARE/OS VERSIONS
As per Flatpak package indicated above:

NameDescription  Application ID  Version  Branch 
Remotes
Okular  Document Viewer  org.kde.okular  23.04.3  stable 
flathub

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

[kate] [Bug 388453] New: XML multi-line self-closing tag doesn't decrease indentation

[Juan Navarro]

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

Bug ID: 388453
   Summary: XML multi-line self-closing tag doesn't decrease
indentation
   Product: kate
   Version: 15.12
  Platform: Mint (Ubuntu based)
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: indentation
  Assignee: kwrite-bugs-n...@kde.org
  Reporter: oneorj...@gmail.com
  Target Milestone: ---

When aligning the following example XML:






We get:

  


  

However the desired output would be:

  

  

(i.e. 1 indent less for the last 2 lines)

Reproducible: Always

Similar to #330174, but the fix probably didn't cover the case of when the
self-closing tag happens to be spread over multiple lines.

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

[systemsettings] [Bug 377156] New: Segmentation fault when changing Color Scheme

[Juan Navarro]

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

Bug ID: 377156
   Summary: Segmentation fault when changing Color Scheme
   Product: systemsettings
   Version: 5.8.5
  Platform: Neon Packages
OS: Linux
Status: UNCONFIRMED
  Keywords: drkonqi
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: plasma-b...@kde.org
  Reporter: oneorj...@gmail.com
  Target Milestone: ---

Application: systemsettings5 (5.8.5)

Qt Version: 5.7.1
Frameworks Version: 5.31.0
Operating System: Linux 4.4.0-64-generic x86_64
Distribution: KDE neon LTS User Edition 5.8

-- Information about the crash:
- What I was doing when the application crashed:
KDE neon LTS 5.8 freshly installed.
1. Open System Settings
2. Open Workspace Theme
3. Go back to All Settings
4. Open Color
5. Choose Oxygen Cold
6. Click Apply
7. Crash

It doesn't happen if Workspace Theme is not opened before Color.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings5), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f996d5f18c0 (LWP 2456))]

Thread 4 (Thread 0x7f99471a5700 (LWP 2461)):
#0  0x7f9964eb1a79 in g_mutex_lock () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x7f9964e6c7f7 in g_main_context_prepare () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9964e6d2bb in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f9964e6d49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7f996a63775b in QEventDispatcherGlib::processEvents
(this=0x7f9948c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#5  0x7f996a5e20ba in QEventLoop::exec (this=this@entry=0x7f99471a4ce0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#6  0x7f996a411f64 in QThread::exec (this=) at
thread/qthread.cpp:507
#7  0x7f9968d6ebf5 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#8  0x7f996a416b48 in QThreadPrivate::start (arg=0x15e3e00) at
thread/qthread_unix.cpp:368
#9  0x7f9966f286ba in start_thread (arg=0x7f99471a5700) at
pthread_create.c:333
#10 0x7f9969d2382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f995393e700 (LWP 2459)):
#0  0x7f9969d17b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f9964e6d38c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7f9964e6d49c in g_main_context_iteration () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x7f996a63775b in QEventDispatcherGlib::processEvents
(this=0x7f994c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#4  0x7f996a5e20ba in QEventLoop::exec (this=this@entry=0x7f995393dcd0,
flags=..., flags@entry=...) at kernel/qeventloop.cpp:212
#5  0x7f996a411f64 in QThread::exec (this=this@entry=0x7f996d7bcd60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread.cpp:507
#6  0x7f996d748735 in QDBusConnectionManager::run (this=0x7f996d7bcd60
<(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
qdbusconnection.cpp:178
#7  0x7f996a416b48 in QThreadPrivate::start (arg=0x7f996d7bcd60 <(anonymous
namespace)::Q_QGS__q_manager::innerFunction()::holder>) at
thread/qthread_unix.cpp:368
#8  0x7f9966f286ba in start_thread (arg=0x7f995393e700) at
pthread_create.c:333
#9  0x7f9969d2382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f995beee700 (LWP 2458)):
#0  0x7f9969d17b5d in poll () at ../sysdeps/unix/syscall-template.S:84
#1  0x7f996779ec62 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x7f99677a08d7 in xcb_wait_for_event () from
/usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x7f995e445d79 in QXcbEventReader::run (this=0x119ff40) at
qxcbconnection.cpp:1343
#4  0x7f996a416b48 in QThreadPrivate::start (arg=0x119ff40) at
thread/qthread_unix.cpp:368
#5  0x7f9966f286ba in start_thread (arg=0x7f995beee700) at
pthread_create.c:333
#6  0x7f9969d2382d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f996d5f18c0 (LWP 2456)):
[KCrash Handler]
#6  QQuickWindow::setColor (this=0x1055e, color=...) at
items/qquickwindow.cpp:3826
#7  0x7f996d1728b1 in KCModuleQml::::operator()
(__closure=0x170b870) at /workspace/build/src/kcmoduleqml.cpp:115
#8  QtPrivate::FunctorCall, QtPrivate::List<>, void,
KCModuleQml::showEvent(QShowEvent*):: >::call (arg=,
f=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:135
#9  QtPrivate::Functor,
0>::call, void> (arg=, f=...) at
/usr/include/x86_64-linux-gnu/qt5/QtCore/qobjectdefs_impl.h:192
#10
QtPrivate::QFunctorSlotObject,
0,