[Touch-packages] [Bug 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
Tested with 22.02.0-2ubuntu0.4 and working fine. Thanks!
** Tags removed: verification-needed-jammy
** Tags added: verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to poppler in Ubuntu.
https://bugs.launchpad.net/bugs/1980836
Title:
Regression in Ubuntu 22.04: Content of form field stored invisibly
Status in Poppler:
Fix Released
Status in evince package in Ubuntu:
Invalid
Status in poppler package in Ubuntu:
Triaged
Status in evince source package in Jammy:
Invalid
Status in poppler source package in Jammy:
Fix Committed
Bug description:
[ Impact ]
The bug causes text entered in certain PDF form fields to be stored
but both displayed and printed white (on white background).
[ Test Plan ]
1. Download the attached 230-muster-01.pdf.
2. Try to input to any of the main content fields starting with 06-09
("Anrede des Zahlungspflichtigen etc").
3. Observe that it does not work.
4. Install the updated poppler package versions
5. Try the same fields and see they're functoning properly now with visible
text.
6. Test also that the fields like "Aktenzeichen", "TL-Nr." or
"Buchungsstelle" that weren't broken, continue to work.
[ Where problems could occur ]
It is a merged upstream fix to Annot.cc file that fixed two upstream
bugs https://gitlab.freedesktop.org/poppler/poppler/-/issues/1189 and
https://gitlab.freedesktop.org/poppler/poppler/-/issues/1267.
There are no indications of upstream regressions caused by this fix,
and it was released in upstream stable release 22.08.0 (Ubuntu 22.04
LTS has version based on 22.02.0).
However, since it's an individual cherry-pick there could always be a
PDF somewhere having issues with this, so it's useful to let it be
tested with various files in addition to the problematic ones.
--- original report ---
Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly
anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu
20.04.
The symptom is that one can edit the form content and also save it,
but that the entered text is only visible when the form field is
focused and in edit mode. Otherwise the text it is invisible, also on
printouts.
Such bugs have been reported against Evince for a long time (e.g.,
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I
am reporting this as a new bug because for the current form with which
I am experiencing this it is a regression.
I have attached the problematic form with two form fields filled out, one in
the upper left corner and the big one in the lower half.
I have produced this by taking the original, empty form (produced by somebody
else) and first opened it in Evince 41.4, which I have installed from the snap
package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field
and saved the form.
Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and
entered text in the big field and saved the form.
Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince
41.4.
When I open the PDF again, only the text in the first field is
visible. The text in the second field is visible only if I click into
the field. The visibility of the field contents is the same for Evince
41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems
that the problem is with Evince 42.3 incorrectly saving the field
content, not with displaying it.
Firefox shows and prints the content of both fields, though.
Note that I cannot switch back to Evince 41 because for some other
forms that I have the exact same problem happens only with the old
version and the new version fixes it. So it seems that something
changed that fixed it for some forms and broke it for others.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 42.3-0ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jul 6 14:32:27 2022
InstallationDate: Installed on 2021-11-26 (222 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
RebootRequiredPkgs: Error: path contained symlinks.
Snap.Changes:
ID Status Spawn Bereit
Zusammenfassung
137 Done2022-07-06T12:48:33+02:00 2022-07-06T12:48:41+02:00
Installiere "evince" Snap
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2022-06-22 (13 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/poppler/+bug/1980836/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.laun
[Touch-packages] [Bug 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
I would like to repeat that this is a regression in Ubuntu 22.04, it has a fix released upstream and the patch applies cleanly if backported. So it seems that this should be a low hanging fruit to fix and I would really appreciate it if the fix could be shipped to Ubuntu 22.04. Thank you very much in advance! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1980836 Title: Regression in Ubuntu 22.04: Content of form field stored invisibly Status in Poppler: Fix Released Status in evince package in Ubuntu: Invalid Status in poppler package in Ubuntu: Triaged Bug description: Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04. The symptom is that one can edit the form content and also save it, but that the entered text is only visible when the form field is focused and in edit mode. Otherwise the text it is invisible, also on printouts. Such bugs have been reported against Evince for a long time (e.g., https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I am reporting this as a new bug because for the current form with which I am experiencing this it is a regression. I have attached the problematic form with two form fields filled out, one in the upper left corner and the big one in the lower half. I have produced this by taking the original, empty form (produced by somebody else) and first opened it in Evince 41.4, which I have installed from the snap package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field and saved the form. Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and entered text in the big field and saved the form. Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince 41.4. When I open the PDF again, only the text in the first field is visible. The text in the second field is visible only if I click into the field. The visibility of the field contents is the same for Evince 41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems that the problem is with Evince 42.3 incorrectly saving the field content, not with displaying it. Firefox shows and prints the content of both fields, though. Note that I cannot switch back to Evince 41 because for some other forms that I have the exact same problem happens only with the old version and the new version fixes it. So it seems that something changed that fixed it for some forms and broke it for others. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:32:27 2022 InstallationDate: Installed on 2021-11-26 (222 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: ID Status Spawn Bereit Zusammenfassung 137 Done2022-07-06T12:48:33+02:00 2022-07-06T12:48:41+02:00 Installiere "evince" Snap SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-06-22 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1980836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
Thanks! Version 249.11-0ubuntu3.5 of systemd fixes this issue for me: I rebooted the machine and the bind mount to the NFS mount was correctly mounted automatically. Previously this had always failed. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Jammy: Fix Committed Status in systemd source package in Kinetic: Fix Released Bug description: [Impact] Some NFS setups that have worked on previous versions of Ubuntu are now broken. Specifically, when creating a bind mount, systemd will fail if the directory already exists on NFS. [Test Plan] This test plan requires an NFS server to be in place. The exact setup is not important, but for the purposes of this test plan we will assume the server exports /data, which contains a directory called home. * Make sure nfs-common is installed: $ apt install nfs-common -y * Check the NFS server exports using showmount: $ showmount -e $NFS_SERVER_IP Export list for $NFS_SERVER_IP: /data * * Add the appropriate entries to /etc/fstab. In this example, we will make /home2 a bind mount to /data/home: # /etc/fstab $NFS_SERVER_IP:/data /data nfs defaults,nfsvers=3 0 0 /data/home /home2 none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 * Check systemctl status home2.mount. On an affected system, we should see a permission denied error: $ systemctl status home2.mount x home2.mount - /home2 Loaded: loaded (/etc/fstab; generated) Active: failed (Result: resources) Where: /home2 What: /data/home Docs: man:fstab(5) man:systemd-fstab-generator(8) systemd[1]: home2.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home2.mount: Failed to run 'mount' task: Permission denied systemd[1]: home2.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home2. * On a patched system, we expect /home2 to be mounted successfully. [Where problems could occur] The patch makes it so that systemd will not fail bind mounts immediately if creating the directory fails. Thus, any regressions would be seen during bind mounts with systemd. N.B. that this patch restores previous behavior in systemd. [Original Description] I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates appl
[Touch-packages] [Bug 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
A fix has been committed upstream now. Could this be backported to Ubuntu? I tested https://gitlab.freedesktop.org/poppler/poppler/-/commit/a89c3c27e02e9c300aa667c966d91fdf787c7d0a by cherry-picking it on top of poppler-22.02.0. Tt applies and compiles cleanly and with it Evince on Ubuntu 22.04 behaves as it should with respect to form fields for several PDFs that I checked, including the original problematic file. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1980836 Title: Regression in Ubuntu 22.04: Content of form field stored invisibly Status in Poppler: New Status in evince package in Ubuntu: Invalid Status in poppler package in Ubuntu: Triaged Bug description: Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04. The symptom is that one can edit the form content and also save it, but that the entered text is only visible when the form field is focused and in edit mode. Otherwise the text it is invisible, also on printouts. Such bugs have been reported against Evince for a long time (e.g., https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I am reporting this as a new bug because for the current form with which I am experiencing this it is a regression. I have attached the problematic form with two form fields filled out, one in the upper left corner and the big one in the lower half. I have produced this by taking the original, empty form (produced by somebody else) and first opened it in Evince 41.4, which I have installed from the snap package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field and saved the form. Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and entered text in the big field and saved the form. Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince 41.4. When I open the PDF again, only the text in the first field is visible. The text in the second field is visible only if I click into the field. The visibility of the field contents is the same for Evince 41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems that the problem is with Evince 42.3 incorrectly saving the field content, not with displaying it. Firefox shows and prints the content of both fields, though. Note that I cannot switch back to Evince 41 because for some other forms that I have the exact same problem happens only with the old version and the new version fixes it. So it seems that something changed that fixed it for some forms and broke it for others. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:32:27 2022 InstallationDate: Installed on 2021-11-26 (222 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: ID Status Spawn Bereit Zusammenfassung 137 Done2022-07-06T12:48:33+02:00 2022-07-06T12:48:41+02:00 Installiere "evince" Snap SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-06-22 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1980836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
The fix https://github.com/systemd/systemd/pull/24122 is now merged upstream. The change should be easy to backport, is it possible that this could be done for Ubuntu? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu 22.04 - Linux 5.15.0-40-generic - systemd 249.11-0ubuntu3.3 - util-linux 2.37.2-4ubuntu3 This appears on both Ubuntu 22.04 machines that I have (a hardware machine and a VM). To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1979952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1979952] Re: Bind mount to NFS mount fails on Ubuntu 22.04
Somebody else has reported this upstream (https://github.com/systemd/systemd/issues/24120) and a fix is being developed as https://github.com/systemd/systemd/pull/24122. ** Bug watch added: github.com/systemd/systemd/issues #24120 https://github.com/systemd/systemd/issues/24120 ** Also affects: systemd via https://github.com/systemd/systemd/issues/24120 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1979952 Title: Bind mount to NFS mount fails on Ubuntu 22.04 Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I have the following setup: - /data is an NFS mount. - /home is a bind mount to /data/home. Configured in /etc/fstab with these lines: $FILE_SERVER:/data /data nfs defaults 0 0 /data/home /home none bind,_netdev,x-systemd.requires-mounts-for=/data 0 0 This has worked with the same configuration for me on at least Ubuntu 18.04 and Ubuntu 20.04, but on Ubuntu 22.04 the mount of /home fails when attempted by systemd. So not only is /home not mounted after boot, but also when I run "sudo systemctl start home.mount", it fails. The journal entries are this: sudo[1316]: wendler : TTY=pts/0 ; PWD=/home/wendler ; USER=root ; COMMAND=/usr/bin/systemctl start home.mount sudo[1316]: pam_unix(sudo:session): session opened for user root(uid=0) by wendler(uid=1000) systemd[1]: home.mount: Directory /home to mount over is not empty, mounting anyway. systemd[1]: home.mount: Failed to make bind mount source '/data/home': Permission denied systemd[1]: home.mount: Failed to run 'mount' task: Permission denied systemd[1]: home.mount: Failed with result 'resources'. systemd[1]: Failed to mount /home. However, when I run "sudo mount /home" it works. Now the weird thing is that after I have mounted /home manually once and unmounted it again, then "sudo systemctl start home.mount" suddenly also works! But of course only until the next reboot. And even if I just do "ls /data" once (either as root or as my user), it also makes "sudo systemctl start home.mount" start working! To be fully clear: - Booting the system (/home fails to mount) - sudo systemctl start home.mount # fails - sudo ls /data # shows correct output - sudo systemctl start home.mount # works! Additional information: The NFS export for /data has root_squash set and if I remove this option, the bind mount of /home works as it should. However, both /data and /data/home have mode rwxr-xr-x, so root is able to enter and read these directories even despite root_squash. It is not a network or mount-order problem. Not only is the bind mount to /home correctly attempted after /data is mounted during boot, remember that the bind mount also fails when I try it with "sudo systemctl start home.mount" minutes afterwards. Versions (system is a recent installation with all updates applied): - Ubuntu 22.04 - Linux 5.15.0-40-generic - systemd 249.11-0ubuntu3.3 - util-linux 2.37.2-4ubuntu3 This appears on both Ubuntu 22.04 machines that I have (a hardware machine and a VM). To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1979952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly
I found out that the bug is actually in poppler and have reported a bug upstream, where it is being worked on. ** Also affects: poppler (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/poppler/poppler/-/issues #1267 https://gitlab.freedesktop.org/poppler/poppler/-/issues/1267 ** Also affects: poppler via https://gitlab.freedesktop.org/poppler/poppler/-/issues/1267 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/1980836 Title: Regression in Ubuntu 22.04: Content of form field stored invisibly Status in Poppler: Unknown Status in evince package in Ubuntu: New Status in poppler package in Ubuntu: New Bug description: Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04. The symptom is that one can edit the form content and also save it, but that the entered text is only visible when the form field is focused and in edit mode. Otherwise the text it is invisible, also on printouts. Such bugs have been reported against Evince for a long time (e.g., https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I am reporting this as a new bug because for the current form with which I am experiencing this it is a regression. I have attached the problematic form with two form fields filled out, one in the upper left corner and the big one in the lower half. I have produced this by taking the original, empty form (produced by somebody else) and first opened it in Evince 41.4, which I have installed from the snap package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field and saved the form. Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and entered text in the big field and saved the form. Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince 41.4. When I open the PDF again, only the text in the first field is visible. The text in the second field is visible only if I click into the field. The visibility of the field contents is the same for Evince 41.4 (snap), Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems that the problem is with Evince 42.3 incorrectly saving the field content, not with displaying it. Firefox shows and prints the content of both fields, though. Note that I cannot switch back to Evince 41 because for some other forms that I have the exact same problem happens only with the old version and the new version fixes it. So it seems that something changed that fixed it for some forms and broke it for others. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.3-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Jul 6 14:32:27 2022 InstallationDate: Installed on 2021-11-26 (222 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap.Changes: ID Status Spawn Bereit Zusammenfassung 137 Done2022-07-06T12:48:33+02:00 2022-07-06T12:48:41+02:00 Installiere "evince" Snap SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-06-22 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1980836/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1633413] Re: Obsolete authenthication requests for WiFi
I agree that this is very inconvenient. For example, I have a system at home that I leave unattended but I need it to reconnect automatically to my wifi, because I need to access it from abroad. If there is a disconnect and it can't reconnect immediately (e.g., because of a router reboot), the password dialog will prevent network manager from connecting to my wifi again, effectively killing my access to this machine. So I would say that even if network manager needs to ask for the password because it can't know whether the password is correct, this should not block all other operations: network manager should try connecting to the wifi in the background (and if it succeeds, hide the dialog). This is also asked here: https://bugzilla.gnome.org/show_bug.cgi?id=680625 Maybe https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1407907, https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1316634 and https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1010745 are related? Users have requesting this since 2010: http://askubuntu.com/q/19137/51272 ** Bug watch added: GNOME Bug Tracker #680625 https://bugzilla.gnome.org/show_bug.cgi?id=680625 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1633413 Title: Obsolete authenthication requests for WiFi Status in network-manager package in Ubuntu: Confirmed Bug description: When a WiFi connection behaves unstable over longer time (eg. long range), sometimes the user is asked for the password again (the requester come up already filled), even if it is correct. The request can come up at any time, depending on the connection quality, and likely force the user to look up the already correctly entered password again. This is very annoying for kiosk-like systems or when using fullscreen apps. This bug is stone old and iv'e seens this year by year over a broad range of Ubuntu versions as well devices (Intel and ARM platform). It still happens as of Ubuntu 16.04. So I wonder if this is inevitable by the fact that NetworkManager sometimes can't decide between an authetication failed by wrong password vs. authentication failed by bad connection. If not, it should finally be fixed. There may be a security problem, for locked down kiosk applications, as the password may be obtained by kiosk users if the request pops up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1633413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373598] Re: apt-get update fails, hash sum mismatches (trusty)
We experience this problem also. $ ping -c 2 de.archive.ubuntu.com PING ubuntu.mirror.tudos.de (141.30.13.20) 56(84) bytes of data. 64 bytes from c13020.dip.tu-dresden.de (141.30.13.20): icmp_seq=1 ttl=55 time=12.8 ms 64 bytes from c13020.dip.tu-dresden.de (141.30.13.20): icmp_seq=2 ttl=55 time=12.5 ms --- ubuntu.mirror.tudos.de ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 12.532/12.693/12.855/0.196 ms Sometimes it also uses the 141.30.13.10 machine, never any other machine. We are also at a German university, and thus connected to tudos.de directly via DFN (German Research Network): > tracepath de.archive.ubuntu.com 1?: [LOCALHOST] pmtu 1500 1: mikado.fim.uni-passau.de 0.364ms 1: mikado.fim.uni-passau.de 0.353ms 2: Transfer-Lst-Brandenburg-FW.c6006.rz.uni-passau.de0.802ms 3: uni-fw-1.rz.uni-passau.de 0.529ms 4: core.rz.uni-passau.de 1.170ms 5: xr-reg1-ge8-6.x-win.dfn.de3.493ms 6: cr-erl1-be5.x-win.dfn.de 7.399ms 7: kr-dre106.x-win.dfn.de 12.860ms 8: 141.30.1.74 21.586ms 9: cat6k-bar.campus.urz.tu-dresden.de 12.892ms 10: c13010.dip.tu-dresden.de 14.231ms reached -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1373598 Title: apt-get update fails, hash sum mismatches (trusty) Status in apt package in Ubuntu: Confirmed Status in ubuntu-release-upgrader package in Ubuntu: Confirmed Bug description: 1. Release: Description: Ubuntu 14.04.1 LTS Release: 14.04 2. not a package. The whole distro is broken. 3. I always expect apt-get update to work, at least with Ubuntu's own repositories. 4. "apt-get update" failed, and later "apt-get dist upgrade" It started with this when doing a normal "apt-get update" W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/source/Sources Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/main/binary-amd64/Packages Hash Sum mismatch W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/trusty- updates/universe/binary-i386/Packages Hash Sum mismatch E: Some index files failed to download. They have been ignored, or old ones used instead. When doing a dist-upgrade, I then got this: E: mkinitramfs failure cpio 141 gzip 1 update-initramfs: failed for /boot/initrd.img-3.13.0-36-generic with 1. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Failed to process /etc/kernel/postinst.d at /var/lib/dpkg/info/linux-image-extra-3.13.0-36-generic.postinst line 1025. No apport report written because the error message indicates its a followup error from a previous failure. dpkg: error processing package linux-image-extra-3.13.0-36-generic (--configure): subprocess installed post-installation script returned error exit status 2 dpkg: dependency problems prevent configuration of linux-image-generic: linux-image-generic depends on linux-image-extra-3.13.0-36-generic; however: Package linux-image-extra-3.13.0-36-generic is not configured yet. dpkg: error processing package linux-image-generic (--configure): dependency problems - leaving unconfigured Setting up linux-headers-3.13.0-36 (3.13.0-36.63) ... Setting up linux-headers-3.13.0-36-generic (3.13.0-36.63) ... Examining /etc/kernel/header_postinst.d. run-parts: executing /etc/kernel/header_postinst.d/dkms 3.13.0-36-generic /boot/vmlinuz-3.13.0-36-generic Setting up linux-headers-generic (3.13.0.36.43) ... No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of linux-generic: linux-generic depends on linux-image-generic (= 3.13.0.36.43); however: Package linux-image-generic is not configured yet. dpkg: error processing package linux-generic (--configure): dependency problems - leaving unconfigured And later this at the end: Processing triggers for libc-bin (2.19-0ubuntu6.3) ... E: Sub-process /usr/bin/dpkg returned an error code (1) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.5 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
For auditing my PAM config, could you please tell me which PAM config the lock
screen uses
(i.e., which file in /etc/pam.d is used)?
So far I could not find any differences between them.
The LDAP config is in common-{auth,account}, which are included in most files
in this directory.
All these services (login, lightdm, polkit-1, sudo, sshd) are working fine.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
https://bugs.launchpad.net/bugs/1311316
Title:
After locking screen there is no input field to type password for
unlock
Status in Unity:
Confirmed
Status in Unity 7.2 series:
Confirmed
Status in unity package in Ubuntu:
Fix Released
Bug description:
Sometimes (but not always) after locking the screen there is the
situation not having any input field where I can type the password to
unlock the session again. The shaded gray area simply does not have
the input field. I can't do anything, I have to switch to text console
and stop/start lightdm service to cure the problem loosing all of my
session :(
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: unity 7.2.0+14.04.20140416-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9
Uname: Linux 3.13.0-24-generic i686
ApportVersion: 2.14.1-0ubuntu3
Architecture: i386
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: Unity
Date: Tue Apr 22 22:17:57 2014
InstallationDate: Installed on 2012-03-03 (780 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
SourcePackage: unity
UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I cannot imagine how a missing password input field in the lock screen could be related to an LDAP configuration issue on our side. If the authentication would fail after entering the password, then yes, of course this could be such a problem. But a password field should always be shown by the unlock screen, regardless of the authentication backend. Also our LDAP configuration is working for several years now without problems. Only since the upgrade to Ubuntu 14.04 this problem with the lock screen has started appearing. All other applications, including the login screen (lightdm) are working fine. By the way, we have a dual monitor setup, too. Our home file systems are on an NFS fileserver, mounted using automount and with root_squash enabled (this means that root does not have full access to my home directory, but only the same rights as all other accounts). If there is a root process trying to access files in my home this would fail. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
We also have this problem on several machines, and I hope I can contribute to getting it fixed. Removing light-locker fixed the "double unlock" problem, but not this problem. The machine is a fully up-to-date Ubuntu 14.04 with LDAP authentication. The output of ls -l /sbin/unix_chkpwd is -rwxr-sr-x 1 root shadow 35536 Jan 31 2014 /sbin/unix_chkpwd I cannot post full auth.log because of personal data, but I will try to remember to grap the last lines of the log the next time the problem appears. The problem occurs only randomly and not very often (maybe once per week). It happens less often now that the "double unlock" problem is fixed, I guess simply because I have to enter my password less often now. A reliable work around is to switch to a text console, login as the same user, and run "unity --replace". This restores the password input field. After unlocking, the panels are missing but I can fix this by opening a terminal window and running "unity --replace" there. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
