[Bug 42571] Re: eog won't delete images on different volume
Bug still exists in 2022. Observed on an ext4fs that is mounted over smb. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/42571 Title: eog won't delete images on different volume To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/42571/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1743366] Re: Systemd .path units are not working properly in Bionic
This bug was filed pre-Bionic and explicitly mentions Bionic, but looks like the issue is still present in Jammy: $ systemctl --user is-active graphical-session.target inactive verified in a clean Jammy install and also on Impish (thanks ~ogayot). Other than the .path units under /usr/lib/systemd/user/graphical- session.target.wants/ all the .service units under /usr/lib/systemd/user/graphical-session-pre.target.wants/ are also not being executed. These are: gnome-keyring-ssh.service gnome-keyring.service session-migration.service ssh-agent.service I'm retitling the bug as it's not only about .path units. ** Summary changed: - Systemd .path units are not working properly in Bionic + The user session should run under systemd ** Description changed: + Currently the user session doesn't run under systemd. + As a consequence: + + [Original Description] In Bionic the systemd .path units are not properly activated. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1743366 Title: The user session should run under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1743366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1743366] Re: The user session should run under systemd
Maybe useful: https://wiki.gnome.org/Initiatives/SystemdUser I'll add that I was confused by this as systemd.special(7) says about graphical-session.target: This target is active whenever any graphical session is running. [...] and it took me a while to figure out that's not true in our case. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1743366 Title: The user session should run under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1743366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1743366] Re: The user session should run under systemd
Apologies for the confusion. I was not using a fresh Impish install. I just did a clean install and graphical-session.target is reported as active. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1743366 Title: The user session should run under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1743366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1743366] Re: The user session should run under systemd
Interesting, thanks for verifying. I just re-tested this and indeed for `systemctl --user is-active graphical-session.target` we have - Impish clean install: active - Jammy clean install: inactive So looks like this we switched to systemd sessions at some point, but this bug never got closed, and then something regressed in Jammy. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1743366 Title: The user session should run under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1743366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1743366] Re: The user session should run under systemd
** Tags added: rls-jj-incoming -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1743366 Title: The user session should run under systemd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1743366/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1901446] Re: Add gir1.2-tepl-5 package depedency
gedit no longer uses tepl, so I'm closing this bug. ** Changed in: gedit (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1901446 Title: Add gir1.2-tepl-5 package depedency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1901446/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960737] Re: /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_flags
thank for the reply, closing then, it's not really possible to figure out what was wrong without access to the system to get the details ** Changed in: gtk+3.0 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1960737 Title: /usr/lib/x86_64-linux-gnu/libgtk-3-0/gtk-query-immodules-3.0: symbol lookup error: /usr/lib/x86_64-linux-gnu/libgdk-3.so.0: undefined symbol: wl_proxy_marshal_flags To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960737/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960857] [NEW] gdm3 self-enables during upgrade
Public bug reported: I've been running Ubuntu 20.04 LTS on some servers for a while. This week, they started going non-responsive. Plugging in monitors and keyboards to them, I found they had gone to sleep, and waking them up showed the purple gdm login screen. Before, they've always just had my good friend getty showing a black and white "login: " prompt. Watching their behaviour for about an hour, I found the suspends were happening at 20 minute intervals, which is gdm's default sleep timer, so I'm reasonably confident my downtime problem was because gdm had self- activated unexpectedly. I checked my logs and found that unattended-upgrades had installed a new version overnight. I'd never noticed I even had gdm3 installed because it was never active before, and I'm still working out why that is, and I've disabled and purged it, but regardless I am surprised that the upgrade self-activated it like that without my consent. I would like to ask that gdm3's configure script takes account of the current `service enable`/`service disable`/`systemctl enable`/`systemctl disable` state, if it's not already doing that. Or, just don't touch `service` at all during an upgrade. During an install is fine, but please not during an upgrade. Here's version details from the two servers I've seen this on so far: root@romane:~# lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 root@romane:~# apt-cache policy gdm3 gdm3: Installed: (none) Candidate: 3.36.3-0ubuntu0.20.04.4 Version table: 3.36.3-0ubuntu0.20.04.4 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.3-0ubuntu0.20.04.2 500 500 http://ca.archive.ubuntu.com/ubuntu focal-security/main amd64 Packages 3.34.1-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages root@rosenberg:~# lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 root@rosenberg:~# apt-cache policy gdm3 gdm3: Installed: 3.36.3-0ubuntu0.20.04.4 Candidate: 3.36.3-0ubuntu0.20.04.4 Version table: *** 3.36.3-0ubuntu0.20.04.4 500 500 http://ca.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.3-0ubuntu0.20.04.2 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 3.34.1-1ubuntu1 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages Here's the relevant upgrade logs from the two: root@romane:~# grep 2022-02-10 /var/log/dpkg.log | grep gdm3 2022-02-10 06:22:56 install gdm3:amd64 3.36.3-0ubuntu0.20.04.3 3.36.3-0ubuntu0.20.04.4 2022-02-10 06:22:56 status half-installed gdm3:amd64 3.36.3-0ubuntu0.20.04.3 2022-02-10 06:22:56 status unpacked gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-10 06:25:01 configure gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-10 06:25:01 status unpacked gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-10 06:25:01 status half-configured gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-10 06:25:02 status installed gdm3:amd64 3.36.3-0ubuntu0.20.04.4 root@rosenberg:~# grep 2022-02-13 /var/log/dpkg.log | grep gdm3 2022-02-13 06:08:05 install gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:08:05 status half-installed gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:08:06 status unpacked gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:11:52 configure gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:11:52 status unpacked gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:11:52 status half-configured gdm3:amd64 3.36.3-0ubuntu0.20.04.4 2022-02-13 06:11:53 status installed gdm3:amd64 3.36.3-0ubuntu0.20.04.4 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960857 Title: gdm3 self-enables during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960857] Re: gdm3 self-enables during upgrade
Oh also maybe this would be handy, I use etckeeper(8) with unattended- upgrades(8) so I can show you that the change happened when gdm went from 3.36.3-0ubuntu0.20.04.3 -> 3.36.3-0ubuntu0.20.04.4: root@romane:~# etckeeper vcs log fea52b81f4bbc9c171206a56a4d53087bf82b82d~..fea52b81f4bbc9c171206a56a4d53087bf82b82d commit fea52b81f4bbc9c171206a56a4d53087bf82b82d Author: root Date: Thu Feb 10 06:25:28 2022 -0500 committing changes in /etc made by "/usr/bin/python3 /usr/bin/unattended-upgrade" Package changes: +aptdaemon-data 1.1.1+bzr982-0ubuntu32.3 all -avahi-daemon 0.7-4ubuntu7 amd64 +avahi-daemon 0.7-4ubuntu7.1 amd64 +avahi-utils 0.7-4ubuntu7.1 amd64 -bluez 5.53-0ubuntu3.1 amd64 +bluez 5.53-0ubuntu3.5 amd64 +cheese-common 3.34.0-1ubuntu1 all +colord-data 1.4.4-2 all +dconf-cli 0.36.0-1 amd64 -evolution-data-server 3.36.4-0ubuntu1 amd64 +evolution-data-server 3.36.5-0ubuntu1 amd64 +evolution-data-server-common 3.36.5-0ubuntu1 all -fprintd 1.90.1-1ubuntu1 amd64 +fprintd 1.90.9-1~ubuntu20.04.1 amd64 +gcr 3.36.0-2build1 amd64 -gdm3 3.36.3-0ubuntu0.20.04.3 amd64 +gdm3 3.36.3-0ubuntu0.20.04.4 amd64 +gir1.2-accountsservice-1.0 0.6.55-0ubuntu12~20.04.5 amd64 +gir1.2-atk-1.0 2.35.1-1ubuntu2 amd64 +gir1.2-atspi-2.0 2.36.0-2 amd64 +gir1.2-freedesktop 1.64.1-1~ubuntu20.04.1 amd64 +gir1.2-gck-1 3.36.0-2build1 amd64 +gir1.2-gcr-3 3.36.0-2build1 amd64 +gir1.2-gdesktopenums-3.0 3.36.0-1ubuntu1 amd64 +gir1.2-gdkpixbuf-2.0 2.40.0+dfsg-3ubuntu0.2 amd64 +gir1.2-gdm-1.0 3.36.3-0ubuntu0.20.04.4 amd64 +gir1.2-geoclue-2.0 2.5.6-0ubuntu1 amd64 +gir1.2-gnomebluetooth-1.0 3.34.3-0ubuntu1 amd64 +gir1.2-gnomedesktop-3.0 3.36.8-0ubuntu1 amd64 +gir1.2-graphene-1.0 1.10.0-1build2 amd64 +gir1.2-gtk-3.0 3.24.20-0ubuntu1 amd64 +gir1.2-gweather-3.0 3.36.1-1~ubuntu20.04.1 amd64 +gir1.2-ibus-1.0 1.5.22-2ubuntu2.1 amd64 +gir1.2-json-1.0 1.4.4-2ubuntu2 amd64 +gir1.2-mutter-6 3.36.9-0ubuntu0.20.04.2 amd64 +gir1.2-nm-1.0 1.22.10-1ubuntu2.3 amd64 +gir1.2-nma-1.0 1.8.24-1ubuntu3 amd64 +gir1.2-notify-0.7 0.7.9-1ubuntu2 amd64 +gir1.2-packagekitglib-1.0 1.1.13-2ubuntu1.1 amd64 +gir1.2-pango-1.0 1.44.7-2ubuntu4 amd64 +gir1.2-polkit-1.0 0.105-26ubuntu1.2 amd64 +gir1.2-rsvg-2.0 2.48.9-1ubuntu0.20.04.1 amd64 +gir1.2-secret-1 0.20.4-0ubuntu1 amd64 +gir1.2-soup-2.4 2.70.0-1 amd64 +gir1.2-upowerglib-1.0 0.99.11-1build2 amd64 +gir1.2-vte-2.91 0.60.3-0ubuntu1~20.04 amd64 +gjs 1.64.5-0ubuntu0.20.04.01 amd64 +gkbd-capplet 3.26.1-1 amd64 -gnome-control-center-data 1:3.36.5-0ubuntu1 all +gnome-control-center 1:3.36.5-0ubuntu3 amd64 +gnome-control-center-data 1:3.36.5-0ubuntu3 all +gnome-control-center-faces 1:3.36.5-0ubuntu3 all +gnome-desktop3-data 3.36.8-0ubuntu1 all +gnome-keyring-pkcs11 3.36.0-1ubuntu1 amd64 +gnome-online-accounts 3.36.1-0ubuntu1 amd64 +gnome-session-bin 3.36.0-2ubuntu1 amd64 -gnome-settings-daemon 3.36.1-0ubuntu1 amd64 -gnome-shell 3.36.7-0ubuntu0.20.04.1 amd64 +gnome-settings-daemon 3.36.1-0ubuntu1.1 amd64 +gnome-settings-daemon-common 3.36.1-0ubuntu1.1 all +gnome-shell 3.36.9-0ubuntu0.20.04.2 amd64 +gnome-shell-common 3.36.9-0ubuntu0.20.04.2 all +gnome-startup-applications 3.36.0-2ubuntu1 amd64 +gnome-user-docs 3.36.2+git20200704-0ubuntu0.1 all +gstreamer1.0-clutter-3.0 3.0.27-1 amd64 +gstreamer1.0-plugins-base 1.16.2-4ubuntu0.1 amd64 +gstreamer1.0-plugins-good 1.16.2-1ubuntu2.1 amd64 +gstreamer1.0-x 1.16.2-4ubuntu0.1 amd64 +ibus-data 1.5.22-2ubuntu2.1 all +ibus-gtk 1.5.22-2ubuntu2.1 amd64 +ibus-gtk3 1.5.22-2ubuntu2.1 amd64 +language-selector-gnome 0.204.2 all +libaa1 1.4p5-46 amd64 +libappindicator3-1 12.10.1+20.04.20200408.1-0ubuntu1 amd64 +libappstream4 0.12.10-2 amd64 +libasyncns0 0.8-6 amd64 +libavahi-core7 0.7-4ubuntu7.1 amd64 +libavahi-glib1 0.7-4ubuntu7.1 amd64 +libavc1394-0 0.5.4-5 amd64 +libbluetooth3 5.53-0ubuntu3.5 amd64 +libcaca0 0.99.beta19-2.1ubuntu1.20.04.2 amd64 +libcamel-1.2-62 3.36.5-0ubuntu1 amd64 +libcanberra-gtk3-0 0.30-7ubuntu1 amd64 +libcanberra-gtk3-module 0.30-7ubuntu1 amd64 +libcanberra-pulse 0.30-7ubuntu1 amd64 +libcdparanoia0 3.10.2+debian-13 amd64 +libcheese-gtk25 3.34.0-1ubuntu1 amd64 +libcheese8 3.34.0-1ubuntu1 amd64 +libclutter-1.0-0 1.26.4+dfsg-1 amd64 +libclutter-1.0-common 1.26.4+dfsg-1 all +libclutter-gst-3.0-0 3.0.27-1 amd64 +libclutter-gtk-1.0-0 1.8.4-4 amd64 +libcogl-common 1.22.6-1 all +libcogl-pango20 1.22.6-1 amd64 +libcogl-path20 1.22.6-1 amd64 +libcogl20 1.22.6-1 amd64 +libcolord-gtk1 0.2.0-0ubuntu1 amd64 +libcolorhug2 1.4.4-2 amd64 +libdaemon0 0.14-7 amd64 +libdbusmenu-glib4 16.04.1+18.10.20180917-0ubuntu6 amd64 +libdbusmenu-gtk3-4 16.04.1+18.10.20180917-0ubuntu6 amd64 +libdv4
[Bug 1960336] Re: No login screen after recent update
hi, this machine has not been much customised. I only switched display manager because the supplied one did not work. I cannot reinstall and lose data. Display link does not work on at least 2 of my systems with kernel 5.13 and they reopened a bug because I reported it - those drivers are always behind and rather unstable in my experience, especially with nouveau currently. I hope devs can come up with a better answer because I bet a lot of folks will run into this issue. I uninstalled caffeine, removed plugins from /usr/share and the problem remains. I would say I am rather handy with Linux, that is why I run dev builds sometimes and report issues. If I want buggy drivers and no support I can just install windows, man even macOS runs better on both machines. Please notify the gdm3 devs and gnome-extensions ones, because stuff changed there. You can also close the bug, but I am not gonna waste my time on finding the issue anymore then. Isn´t the whole point of open source software that users make it better :)? Also, I the time of reporting was right after the update, so it can´t be too hard to find. This issue does not occur on another machine with a recent install of 20.04 and having that updated. That said, this machine certainly does not go further back than 18.04, I think actually 20.04 too. How about we try to find the cause? You have not answered the question about where to find this plugins that are in the bug report, like xcaffeine. thanks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960336] Re: No login screen after recent update
from the newly installed system with 20.04, warnings came for /var/lib/gdm3.config and .local not being empty. root@ubuntu-inspiron-5482:/var/lib/gdm3# ls -lrta total 32 drwxr-xr-x 3 root root 4096 feb 5 12:33 .config drwx-- 3 gdm gdm 4096 feb 5 12:34 .nv drwx-- 4 gdm gdm 4096 feb 5 12:35 .local drwx-- 6 gdm gdm 4096 feb 5 12:35 .cache drwxr-xr-x 101 root root 4096 feb 5 12:37 .. -rw-r--r-- 1 gdm gdm feb 13 23:26 greeter-dconf-defaults drwx--x--x 6 gdm gdm 4096 feb 13 23:26 . is what that looks like on the broken system. On the one with warning, it shows 755 instead of 700 permissions. There is also no .nv dir. I will wipe it out, reinstall and see what happens. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960857] Re: gdm3 self-enables during upgrade
Thank you for taking the time to report this bug and helping to make Ubuntu better. Bug reporting is mostly about finding & fixing problems thus preventing future users from hitting the same bug. I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709 Ubuntu Servers don't have GNOME or `gdm3` installed as they are desktop packages. Your issue appears to have occurred because of packages added to your system, thus you'd benefit more from support I suspect. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 1960857 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960857 Title: gdm3 self-enables during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960336] Re: No login screen after recent update
> those drivers are always behind and rather unstable in my experience, especially with nouveau currently. I was suggesting the 5.5 beta driver which is the latest (December 2021) - https://www.synaptics.com/products/displaylink- graphics/downloads/ubuntu. It works with the official jammy kernel 5.15. I know that because it's what I'm using in development. Also please don't use the nouveau driver. It causes too many bugs so you should always stick to the Nvidia proprietary driver instead. --- The next steps here are: 1. Enable debug mode in /etc/gdm3/custom.conf: [debug] Enable=true 2. Reboot and reproduce the no-login-screen problem again. 3. Reboot again, this time into recovery/safe mode and run: journalctl -b-1 > debugprevboot.txt 4. Attach the resulting text file here. If you find the help you're getting here inadequate for any reason then you can also report the issue to GDM directly at: https://gitlab.gnome.org/GNOME/gdm/-/issues If you do that then please let us know the new issue ID here. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960336 Title: No login screen after recent update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960857] Re: gdm3 self-enables during upgrade
** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960857 Title: gdm3 self-enables during upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1960857/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960868] [NEW] Dell Precision 5520 boots to the wrong VT (black screen)
You have been subscribed to a public bug: I have several Dell Laptops model Precision 5520. Ubuntu LTS 20.04.2 seems to run fine without issues. After do a software update which appears to update to LTS 20.04.3, the laptops no longer boot properly. I end up at a black screen with an underscore cursor blinking at the upper left. If I then hold the Alt key down and click the right arrow a few times followed by the left arrow a few times, eventually I see the normal GUI login screen and I can log in. Please let me know if there is anything that can be done to avoid this problem. I have tried on several Dell laptops and I get the same behavior on all of them. There seems to be something broken in Ubuntu 20.04.3 for these lapotops. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-28.31~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file. .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file. .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file. .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 510.47.03 Mon Jan 24 22:58:54 UTC 2022 GCC version: ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 14 14:37:36 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 630 [1028:07bf] Subsystem: Dell GM107GLM [Quadro M1200 Mobile] [1028:07bf] InstallationDate: Installed on 2022-02-14 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:24a0 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 004: ID 0c45:6713 Microdia Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Precision 5520 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-28-generic root=UUID=58eb98db-d059-4fbb-8a18-0c258fd3ab72 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2020 dmi.bios.release: 1.20 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.20.0 dmi.board.name: 0R6JFH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.asset.tag: 1203062 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.20.0:bd07/21/2020:br1.20:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0R6JFH:rvrA00:cvnDellInc.:ct10:cvr:sku07BF: dmi.product.family: Precision dmi.product.name: Precision 5520 dmi.product.sku: 07BF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug false-gpu-hang focal freeze ubuntu -- Dell Precision 5520 boots to the wrong VT (black screen) https://bugs.launchpad.net/bugs/1960868 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960868] Re: Dell Precision 5520 no longer boots properly (black screen)
Sounds like a variation of bug 1878838. ** Summary changed: - Xorg freeze + Dell Precision 5520 no longer boots properly (black screen) ** Summary changed: - Dell Precision 5520 no longer boots properly (black screen) + Dell Precision 5520 boots to the wrong VT (black screen) ** Package changed: xorg (Ubuntu) => gdm3 (Ubuntu) ** Also affects: nvidia-graphics-drivers-510 (Ubuntu) Importance: Undecided Status: New ** Tags added: nvidia -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960868 Title: Dell Precision 5520 boots to the wrong VT (black screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1960868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960868] Re: Dell Precision 5520 boots to the wrong VT (black screen)
XorgLogOld.txt is showing that Xorg crashed. If that's a recurring issue then it might explain this bug. It looks most likely to be bug 1811023 which is also the most common Xorg crash globally for Ubuntu right now. It also seems to mostly affect Nvidia users. Please reproduce the issue a few more times and if you keep seeing Xorg crashes like: [ 4.932] (EE) Backtrace: [ 4.932] (EE) 0: /usr/lib/xorg/Xorg (OsLookupColor+0x13c) [0x55ac57b32aec] [ 4.933] (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7f2b8ea073c0] [ 4.933] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (gsignal+0xcb) [0x7f2b8e84418b] [ 4.933] (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 (abort+0x12b) [0x7f2b8e823859] [ 4.934] (EE) unw_get_proc_name failed: no unwind info found [-10] [ 4.934] (EE) 4: /lib/x86_64-linux-gnu/libc.so.6 (?+0x0) [0x7f2b8e823729] [ 4.934] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (__assert_fail+0x46) [0x7f2b8e834f36] [ 4.934] (EE) 6: /usr/lib/xorg/Xorg (dixRegisterPrivateKey+0x239) [0x55ac579efb39] [ 4.934] (EE) 7: /usr/lib/xorg/modules/libglamoregl.so (glamor_init+0xcf) [0x7f2a0961b37f] or log messages like: privates.c:384: dixRegisterPrivateKey: Assertion `!global_keys[type].created' failed. then this is bug 1811023. ** Package changed: gdm3 (Ubuntu) => xorg-server (Ubuntu) ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete ** Changed in: nvidia-graphics-drivers-510 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1960868 Title: Dell Precision 5520 boots to the wrong VT (black screen) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-510/+bug/1960868/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate()
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5078 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5078 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5078 Importance: Unknown Status: Unknown ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/1959937 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1959937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960585] Re: gnome-shell crashed with SIGSEGV in maybe_update_frame_info() from notify_view_crtc_presented() from meta_kms_page_flip_data_flipped() from flush_callbacks() from callback_idle()
** Changed in: mutter (Ubuntu) Status: In Progress => Fix Committed ** Tags added: fixed-in-42 fixed-upstream -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1960585 Title: gnome-shell crashed with SIGSEGV in maybe_update_frame_info() from notify_view_crtc_presented() from meta_kms_page_flip_data_flipped() from flush_callbacks() from callback_idle() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1960585/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1959937] Re: gnome-shell crashed with SIGSEGV in meta_context_terminate()
** Bug watch added: Red Hat Bugzilla #2036604 https://bugzilla.redhat.com/show_bug.cgi?id=2036604 ** Also affects: gnome-shell (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=2036604 Importance: Unknown Status: Unknown -- 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/1959937 Title: gnome-shell crashed with SIGSEGV in meta_context_terminate() To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1959937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960898] [NEW] Since Update to Jelly Wayland do not work
Public bug reported: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages -- 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/1960898 Title: Since Update to Jelly Wayland do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1960898/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960898] Re: Since Update to Jelly Wayland do not work
Thanks for the bug report. Can you explain in more detail what is not working? Maybe with a photo or video? ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Package changed: gnome-shell (Ubuntu) => ubuntu -- 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/1960898 Title: Since Update to Jelly Wayland do not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1960898/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960898] [NEW] Since Update to Jelly Wayland do not work
You have been subscribed to a public bug: Hardware: https://linux-hardware.org/?probe=1055dc7082 Worked without Problem in 21.04 Had some flicker and problem with the left dock in 21.10 not working since updating to 22.04 now I'm running xorg. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 41.3-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckMismatches: ./pool/restricted/n/nvidia-graphics-drivers-450/libnvidia-gl-450_450.102.04-0ubuntu2_amd64.deb CasperMD5CheckResult: fail CurrentDesktop: ubuntu:GNOME Date: Tue Feb 15 08:07:04 2022 DisplayManager: gdm3 InstallationDate: Installed on 2021-08-15 (183 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-02-14 (0 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug jammy third-party-packages -- Since Update to Jelly Wayland do not work https://bugs.launchpad.net/bugs/1960898 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960898] Re: Since Update to Jelly Wayland do not work
Oh sorry, I see the problem: [ 76.192764] Klappi org.gnome.Shell.desktop[3287]: Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) [ 76.201950] Klappi org.gnome.Shell.desktop[3287]: Bail out! Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) [ 76.202235] Klappi org.gnome.Shell.desktop[3287]: GNOME Shell crashed with signal 6 [ 76.202346] Klappi org.gnome.Shell.desktop[3287]: == Stack trace for context 0x560ede973210 == [ 76.202456] Klappi org.gnome.Shell.desktop[3287]: #0 560ee0d94590 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:1108 (32b00966a330 @ 13) [ 76.202558] Klappi org.gnome.Shell.desktop[3287]: #1 560ee0d944e8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:1180 (32b009663e70 @ 33) [ 76.202650] Klappi org.gnome.Shell.desktop[3287]: #2 560ee0d94448 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:1235 (32b009663ce0 @ 127) [ 76.202743] Klappi org.gnome.Shell.desktop[3287]: #3 560ee0d943b8 i /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/locations.js:1150 (32b00966a150 @ 15) ** Package changed: ubuntu => mutter (Ubuntu) ** Package changed: mutter (Ubuntu) => gnome-shell (Ubuntu) ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Since Update to Jelly Wayland do not work + Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1960898] Re: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject())
1.) Start Ubuntu 2.) Login 3.) Gnome-Shell appear for a short time 4.) I end back on the login screen 5.) I change to xorg and log in succesfully I reportat this on: https://discourse.ubuntu.com/t/since-update-to-jelly-wayland-do-not-anymore-work/26681 According to the feedback i got I Created this bug-report with 'ubuntu-bug gnome-shell' now I try to do 'ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash' I got the feedback, that it was already reportet on: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1959507 So I'm currently not sure if it is a duplicate or not. -- 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/1960898 Title: Wayland sessions crash with Gjs:ERROR:../gi/interface.cpp:101:bool InterfacePrototype::has_instance_impl(JSContext*, const JS::CallArgs&): assertion failed: (args[0].isObject()) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1960898/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
