[Bug 2030963] Re: Window/app switcher highlights hard to see
For anyone who's struggled to use the task switcher since 22.04 and until this is finally fixed, a reasonably painless workaround is available: https://askubuntu.com/a/1492396/145568 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/2030963 Title: Window/app switcher highlights hard to see To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2030963/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
@ausbin: `aa-complain` is hardly a "fix": it bypasses AppArmor, which is not optimal, knowing how PDF documents are often used as a malware vector. Admittedly, malware is less likely to be targeted at Linux desktops but still... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04
Running APT evince 42.1-3 on stock Ubuntu 22.04/GNOME 42.0/Wayland. My issue is Evince opening in a tiny window every time it's fired off; this deployment was upgraded from 21.10, which didn't suffer from such issue. I attach below the output from `journalctl -f` while starting up Evince, which clearly shows AppArmor violations. I thus attempted the approach from https://askubuntu.com/a/886011/145568 . When running with `aa-complain evince`, Evince behaves properly; I accepted `aa-logprof`'s suggestion to grant /usr/bin/evince [owner /run/user/1000/at-spi/bus rw,]. Unfortunately as soon as I reinstate `aa-enforce evince`, the tiny window issue re-appears. (Note: at first I Ignored /usr/sbin/cups-browsed [capability sys_nice,] because I thought it was unrelated; I tried to grant it but this still doesn't solve the issue). ** Attachment added: "Evince 42.1-3 AppArmor debugging.txt" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+attachment/5587685/+files/Evince%2042.1-3%20AppArmor%20debugging.txt ** Summary changed: - Evince Document Viewer(42.0) does not remember last page in 22.04 + Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css'
Hi Daniel, Thanks to the pointer. I now have 3.30.1-2ubuntu1.18.10.2 and it seems the issue is resolved (not sure if this is the new version or the manual fix below, which I applied thanks to your pointer). I'd installed the Pop theme manually (through apt) atop stock 18.10. The slightly unorthodox thing I'd done was a soft-link from /usr/share /gnome-shell/theme/Yaru/gnome-shell.css onto ../gnome-shell.css, which is itself a soft-link to /usr/share/themes/Pop/gnome-shell/gnome- shell.css This would consistent theming of the lock screen, which doesn't appear to obey the control panel setting. Using the soft-links also makes it easier to spot when those files get overwritten by updates. So it looks like the changes introduced in 3.30.1-2ubuntu1.18.10.1 makes it impossible to follow symlinks from /usr/share/gnome-shell/theme/Yaru /gnome-shell.css ? I guess it's perhaps debatable whether the standard gnome-shell package should reference a hardcoded theme (or maybe that's a GNOME limitation?) Anyway, since I've worked around this issue, I guess this bug can be closed. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809092 Title: gnome-shell 3.30.1-2ubuntu1.18.10.1 fails to start with JS ERROR: Error: No valid stylesheet found for 'Yaru/gnome-shell.css' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login)
Hi Daniel, please see attached; apologies for delay. I hope the weird "gnome-session-binary[4266]: CRITICAL: We failed, but the fail whale is dead. Sorry" is a tell-tale sign? Cheers Christian ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+attachment/5224875/+files/prevboot.txt ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809092 Title: gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809092] [NEW] gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login)
Public bug reported: An upgrade to gnome-shell on 18.10 was recently released which made it impossible for me to log in to my DE. Upon typing my password, the gdm screen would disappear, only to re-appear a few seconds later. This was not a password typo as I didn't get the usual msg to that effect (I made at least 5 attempts, carefully typing my passwd). I solved the issue by switching to a terminal screen (using CTRL+ALT+F6 I believe), logging in, analyzing recent changes through /var/log/apt/history.log. Beside the gnome-shell packages, a handful of Wayland packages were also upgraded as follows (I use X.org so left those alone): Start-Date: 2018-12-19 09:13:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.8821' Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1) End-Date: 2018-12-19 09:13:31 I solved the issue by downgrading the just-updated gnome-shell packages as follows: sudo apt install gnome-shell-common=3.30.1-2ubuntu1 gnome- shell=3.30.1-2ubuntu1 Having done this, I switched back to the GDM screen and managed to log in as normal. I couldn't find any smoking gun in system logs but please let me know if there's a way to collect any useful debug info. One thing I'm using which differs from stock 18.10 is the System76 "Pop" theme (let me know if you need details). Presumably a theme cannot cause such issues and/or if the new version of gnome-shell is meant to be incompatible with themes other than Yaru, this should be clearly documented. The problematic versions are the "Candidate" shown below: gnome-shell: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 100 /var/lib/dpkg/status gnome-shell-common: Installed: 3.30.1-2ubuntu1 Candidate: 3.30.1-2ubuntu1.18.10.1 Version table: 3.30.1-2ubuntu1.18.10.1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages *** 3.30.1-2ubuntu1 500 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: cosmic regression-update ** Package changed: gnome (Ubuntu) => gnome-shell (Ubuntu) ** Summary changed: - gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access + gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809092 Title: gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809092] Re: gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login)
** Description changed: An upgrade to gnome-shell on 18.10 was recently released which made it impossible for me to log in to my DE. Upon typing my password, the gdm screen would disappear, only to re-appear a few seconds later. This was not a password typo as I didn't get the usual msg to that effect (I made at least 5 attempts, carefully typing my passwd). I solved the issue by switching to a terminal screen (using CTRL+ALT+F6 I believe), logging in, analyzing recent changes through /var/log/apt/history.log. Beside the gnome-shell packages, a handful of Wayland packages were also upgraded as follows (I use X.org so left those alone): Start-Date: 2018-12-19 09:13:20 Commandline: aptdaemon role='role-commit-packages' sender=':1.8821' Upgrade: libwayland-egl1:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), keybase:amd64 (2.11.0-20181204152506.f11f4191e3, 2.13.0-20181218221625.d72e065cbe), gnome-tweak-tool:amd64 (3.30.1-1, 3.30.2-0ubuntu1), gnome-tweaks:amd64 (3.30.1-1, 3.30.2-0ubuntu1), libwayland-client0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), gnome-shell-common:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), gnome-shell:amd64 (3.30.1-2ubuntu1, 3.30.1-2ubuntu1.18.10.1), libwayland-server0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1), libwayland-cursor0:amd64 (1.16.0-1ubuntu1, 1.16.0-1ubuntu1.1) End-Date: 2018-12-19 09:13:31 I solved the issue by downgrading the just-updated gnome-shell packages as follows: sudo apt install gnome-shell-common=3.30.1-2ubuntu1 gnome- shell=3.30.1-2ubuntu1 Having done this, I switched back to the GDM screen and managed to log - in as normal. I couldn't find anything useful in system logs but please - let me know if there's a way to collect such info. + in as normal. I couldn't find any smoking gun in system logs but please + let me know if there's a way to collect any useful debug info. One thing I'm using which differs from stock 18.10 is the System76 "Pop" theme (let me know if you need details). Presumably a theme cannot cause such issues and/or if the new version of gnome-shell is meant to be incompatible with themes other than Yaru, this should be clearly documented. The problematic versions are the "Candidate" shown below: gnome-shell: - Installed: 3.30.1-2ubuntu1 - Candidate: 3.30.1-2ubuntu1.18.10.1 - Version table: - 3.30.1-2ubuntu1.18.10.1 500 - 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages - *** 3.30.1-2ubuntu1 500 - 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 3.30.1-2ubuntu1 + Candidate: 3.30.1-2ubuntu1.18.10.1 + Version table: + 3.30.1-2ubuntu1.18.10.1 500 + 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages + *** 3.30.1-2ubuntu1 500 + 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + 100 /var/lib/dpkg/status gnome-shell-common: - Installed: 3.30.1-2ubuntu1 - Candidate: 3.30.1-2ubuntu1.18.10.1 - Version table: - 3.30.1-2ubuntu1.18.10.1 500 - 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages - 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages - *** 3.30.1-2ubuntu1 500 - 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages - 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages - 100 /var/lib/dpkg/status + Installed: 3.30.1-2ubuntu1 + Candidate: 3.30.1-2ubuntu1.18.10.1 + Version table: + 3.30.1-2ubuntu1.18.10.1 500 + 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages + 500 http://ch.archive.ubuntu.com/ubuntu cosmic-updates/main i386 Packages + *** 3.30.1-2ubuntu1 500 + 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages + 500 http://ch.archive.ubuntu.com/ubuntu cosmic/main i386 Packages + 100 /var/lib/dpkg/status -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809092 Title: gnome-shell 3.30.1-2ubuntu1.18.10.1 prevents DE access (unable to login) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1809092/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1566468] [NEW] systemd-modules-load.service: Failing due to missing module 'ib_iser'
Public bug reported: On a number of VMs using Xenial daily builds 20160330 and 20160403, out of the box (just after booting for the first time), the following appears in dmesg at boot time: systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: Failed to start Load Kernel Modules. systemd[1]: systemd-modules-load.service: Unit entered failed state. systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. The following related complaint appears in /var/log/syslog: ubuntu systemd-modules-load[352]: Inserted module 'iscsi_tcp' ubuntu systemd-modules-load[352]: Failed to find module 'ib_iser' It looks like 'ib_iser' is some Mellanox-related module, which I don't *think* is something that a stock cloudimg install should attempt to load but I may be wrong; in any case, it's not present (nor is there any similar whingeing) on similar VMs running off 14.04 cloudimg. More info: http://askubuntu.com/questions/753672/xenial-beta2-systemd- modules-load-service-failed-due-to-missing-module-ib-i --- root@testvm4:~# lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 root@testvm4:~# apt policy systemd systemd: Installed: 229-3ubuntu2 Candidate: 229-3ubuntu2 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1566468 Title: systemd-modules-load.service: Failing due to missing module 'ib_iser' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1566468/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
