[Bug 1867092] Re: Failed to set MokListRT: Invalid Parameter
The day before yesterday, I got the error as originally reported, except I was running Kubuntu 20.04, got the updates available prompt, opened Discover, updated shim and shim-signed, waited for both the regular software update and grub update to finish, and then restarted. I posted a question on Ask Ubuntu, then found a CentOS bug with a fix I was able to adapt to my own situation and answer my own question. If you're a bug fixer, read the first note on the CentOS bug; if you've got this same problem, read the Ask Ubuntu question and answer: https://bugs.centos.org/view.php?id=15522#c33203 https://askubuntu.com/questions/1277828/how-do-i-fix-broken-boot-after-shim-update ** Bug watch added: bugs.centos.org/ #15522 https://bugs.centos.org/view.php?id=15522 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867092 Title: Failed to set MokListRT: Invalid Parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1867092/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867402] Re: [snap] Icons in file picker are corrupted
Olivier: No, rm -rf ~/snap/chromium/common/.cache does not fix the problem. Icons still look to me exactly the same as in my screenshot in comment #21. Also I just noticed where Fernando said in comment #13 that he thought probably not many people open the file chooser in a browser. I regularly print/save pages as PDFs and save files to non-default locations, so I see the file chooser often, though these icons are not interfering with any of my tasks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867402 Title: [snap] Icons in file picker are corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1867402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1867402] Re: [snap] Icons in file picker are corrupted
I have this same problem. I'm running Kubuntu 20.04 with Chromium snap revision 1213. ** Attachment added: "Screenshot_20200709_073623.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1867402/+attachment/5391040/+files/Screenshot_20200709_073623.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1867402 Title: [snap] Icons in file picker are corrupted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1867402/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1864365] Re: [snap] Dialog font missing
Olivier: I am running revision 1213 on Kubuntu 20.04. Removing ~/snap/chromium/common/.cache fixed this issue for me, and it has not returned after multiple restarts nor after I installed the font as described in comment #11. Before I removed the .cache directory, my file dialogs did look very much like the screenshot Steven posted in comment #1, with rectangles instead of letters. But now that the letters are back, I notice that many of the icons are garbled, which is different from Steven's screenshot. So for sure at least the icon part is a different issue, and I will look to see if anyone else has posted it, or else I'll post it as a new bug. I am now assuming that my font problem was a different issue as well, so I'm going to stick with the revision I have, unless it would help you for me to try revision 1221 too, in which case please let me know. :-) ** Attachment added: "Screenshot_20200709_073623.png" https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+attachment/5391039/+files/Screenshot_20200709_073623.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864365 Title: [snap] Dialog font missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864365/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 59793] PID file problem
Public bug reported: Immediately after installing the package, I was able to launch Bricolage at localhost:8080. But after a reboot, the browser told me there was no server at that address. Manually running bric_apachectl start didn't help. My /var/log/bricolage/error.log read: [Fri Sep 8 03:17:24 2006] [info] created shared memory segment #4325399 [Fri Sep 8 03:17:25 2006] [notice] Apache/1.3.34 (Ubuntu) mod_perl/1.29 configured -- resuming normal operations [Fri Sep 8 03:17:25 2006] [info] Server built: Jan 7 2006 16:00:45 [Fri Sep 8 03:17:25 2006] [notice] Accept mutex: sysvsem (Default: sysvsem) [Fri Sep 8 03:35:07 2006] [error] access to /login failed for 127.0.0.1, reason: Invalid username or password. Please try again. [Fri Sep 8 03:36:50 2006] [error] access to /login failed for 127.0.0.1, reason: Invalid username or password. Please try again. [Fri Sep 8 03:45:53 2006] [warn] child process 32745 still did not exit, sending a SIGTERM [Fri Sep 8 03:45:53 2006] [warn] child process 32746 still did not exit, sending a SIGTERM [Fri Sep 8 03:45:53 2006] [warn] child process 482 still did not exit, sending a SIGTERM [Fri Sep 8 03:45:53 2006] [warn] child process 483 still did not exit, sending a SIGTERM [Fri Sep 8 03:45:53 2006] [warn] child process 484 still did not exit, sending a SIGTERM [Fri Sep 8 03:45:57 2006] [error] child process 32745 still did not exit, sending a SIGKILL [Fri Sep 8 03:45:57 2006] [error] child process 32746 still did not exit, sending a SIGKILL [Fri Sep 8 03:45:57 2006] [error] child process 482 still did not exit, sending a SIGKILL [Fri Sep 8 03:45:57 2006] [error] child process 483 still did not exit, sending a SIGKILL [Fri Sep 8 03:45:57 2006] [error] child process 484 still did not exit, sending a SIGKILL [Fri Sep 8 03:45:57 2006] [info] removed PID file /var/run/bricolage/bricolage.pid (pid=32744) [Fri Sep 8 03:45:57 2006] [notice] caught SIGTERM, shutting down fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid fopen: No such file or directory apache-perl: could not log pid to file /var/run/bricolage/bricolage.pid Further investigation revealed there was no bricolage directory in /var/run, which is owned by root. Others can read and execute there, but not write. Bricolage is set in the config file to run as user bricolage. I was able to get bricolage running again by manually creating /var/run/bricolage with sudo and making user bricolage the owner. I wish I'd been more patient during installation of the package, because I seem to recall some kind of errors or warnings involving permissions problems. I'd be happy to post any other logs I have that may help if you can tell me where to look for them. ** Affects: bricolage (Ubuntu) Importance: Untriaged Status: Unconfirmed -- PID file problem https://launchpad.net/bugs/59793 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
