[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Yeah, looks like that test has a history of timing out, so I re-ran it and it passed this time. -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Good to hear, thanks for confirming @jurgen-schellaert-j! -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Verified: https://youtu.be/92cB1shLtXg ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
On Wed, Apr 19, 2023, 21:25 Daniel van Vugt <2006...@bugs.launchpad.net> wrote: > Thanks but I wonder if we can remove DGX from the test requirement. > Perhaps just "Nvidia driver" (not sure if a hybrid would work or it has > to be a purely Nvidia system). Perhaps just "a system on which this issue is reproducible"? I don't know how to state anything less equivocal. -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Test plan added to bug description. ** Description changed: [ Impact ] Switching to a second user falls back to Wayland even when Xorg was explicitly selected. [ Test Plan ] - TBC by affected users. + On an NVIDIA DGX Station (known to reliably reproduce the issue): + 1. Start with a default Ubuntu 22.04 Desktop install + 2. apt install dannf linux-modules-nvidia-525-server-generic nvidia-driver-525-server -y + 3. reboot (so new modules load) + 4. Login to a desktop session + 5. Create a new user using 'adduser' + 6. Attempt to "switch to" the new user from the existing login [ Where problems could occur ] Any part of the login procedure as that is what is being modified. [ Original Description ] I have three accounts and I need all three to run on xorg instead of wayland. For some reason, when switching accounts, two of them consistently start wayland even when I select plain gnome from the gdm menu. To get xorg, I need to log out and log in a second time. A solution that is supposed to work consists in customizing /etc/gdm3/custom.conf (see https://docs.fedoraproject.org/en-US/quick- docs/configuring-xorg-as-default-gnome-session/). This solution does not work. I have also experimented with the following options: DefaultSession=gnome-xorg.desktop and PreferredDisplayServer=xorg Neither appears to set xorg as the default... I have found the following bug reported upstream against gdm: https://gitlab.gnome.org/GNOME/gdm/-/issues/733. It looks like this was fixed a year ago but my system is still affected. Note that I am using the gnome-session package. I doubt whether it makes any difference but I am adding it for the sake of completeness. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gdm3 42.0-1ubuntu7 ProcVersionSignature: Ubuntu 6.0.0-1010.10-oem 6.0.9 Uname: Linux 6.0.0-1010-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: GNOME Date: Sun Feb 5 19:44:53 2023 InstallationDate: Installed on 2022-03-27 (315 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.gdm3.custom.conf: 2023-01-30T07:57:48.574915 -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
On Tue, Apr 18, 2023 at 12:36 AM Daniel van Vugt <2006...@bugs.launchpad.net> wrote: > > Wow, great work Dann! Would you like to distro patch it or shall I? I'm happy either way, though I don't know the workflow vis-à-vis salsa here. -dann -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
Upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/808 ** Bug watch added: gitlab.gnome.org/GNOME/gdm/-/issues #808 https://gitlab.gnome.org/GNOME/gdm/-/issues/808 ** Also affects: gdm via https://gitlab.gnome.org/GNOME/gdm/-/issues/808 Importance: Unknown Status: Unknown -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/gdm/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]
I could not reproduce with kinetic (see my steps in bug 2016193). I went back to a clean jammy install, reproduced, then upgraded just the gdm3 packages to kinetic's versions, and the problem went away, so it seems gdm3 in isolation is the relevant difference. I took a look at the differences between the jammy and kinetic gdm3 source, and there really isn't that much different. One piece that stood out is the following, which appears to be a typo: diff -urpN gdm3-42.0/daemon/gdm-local-display-factory.c gdm3-43.0/daemon/gdm-local-display-factory.c --- gdm3-42.0/daemon/gdm-local-display-factory.c2023-04-17 15:07:42.0 -0600 +++ gdm3-43.0/daemon/gdm-local-display-factory.c2022-09-20 09:22:21.0 -0600 @@ -402,7 +402,7 @@ gdm_local_display_factory_create_transie display = gdm_local_display_new (); g_object_set (G_OBJECT (display), "session-type", session_types[0], - "supported-session-tyes", session_types, + "supported-session-types", session_types, NULL); is_initial = TRUE; } On a lark, I rebuilt the jammy version of gdm3 to use "supported- session-types" here, and that seems to have fixed the problem for me. I can reliable downgrade to the jammy version of gdm3 and reproduce, and reliably *not* reproduce the bug after installing my patched version. -- 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/2006059 Title: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2006059/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015386] Re: NVIDIA quad-GPU system crashes starting Wayland session
The .crash file from comment 11 has been submitted via ubuntu-bug in bug 2016299 - I'll leave it to the developers to determine which one should be the dupe. -- 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/2015386 Title: NVIDIA quad-GPU system crashes starting Wayland session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2015386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
Attached ** Attachment added: "_usr_bin_gnome-shell.1001.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+attachment/5663851/+files/_usr_bin_gnome-shell.1001.crash -- 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
I reset all the relevant packages back to the versions used when I originally filed this bug (luckily I stashed an sosreport), and I was able to reproduce. https://errors.ubuntu.com/user/b18128bc669a4a4d1f371a58f4f5d719833ab52c5ab794dbbc9d9e55b45d12516efcc5085f9d93e4d219bc6948f530cdaa31ddf8e34b7e9242e050c269d729c3 Let me know if that is what you needed. This is using the UDA (non-server) drivers, but the user for originally reported the bug to me appears to have been using the -server drivers as you surmised. I tried switching to the 525-server driver and I still experienced an issue with switch user, but the symptoms are different. Instead of entering a new login for a few seconds followed by a gnome- shell crash, this seemed to immediately kick me out of the switched-to session with no gnome-shell crash. Since this is likely a different issue, I reported it as bug 2016193 to keep the threads separate. -- 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2016193] [NEW] "switch to" a new user immediately aborts, returns to previous user's session
Public bug reported: Split out from https://bugs.launchpad.net/ubuntu/+source/gnome- shell/+bug/2015386/comments/9 . I'm using the nvidia 525-server drivers. When I create a new user, then attempt to "switch to" that user from another user's GNOME session, the new session immediately aborts and returns me to the original user's session. ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sosreport-nvidia-dgx-station-c25989-2023-04-13-lncndqw.tar.xz" https://bugs.launchpad.net/bugs/2016193/+attachment/5663793/+files/sosreport-nvidia-dgx-station-c25989-2023-04-13-lncndqw.tar.xz -- 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/2016193 Title: "switch to" a new user immediately aborts, returns to previous user's session To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2016193/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
I need to deploy the machine from scratch each time I access it, so I won't be able to run that command in the same install. I tried reproducing again from scratch, but this time "switch user" immediately aborted w/o generating a gnome-shell crash. I'm not sure what was different - I do know that the nvidia driver I was using has been updated in the distro, so at least that had changed. Re: nouveau_dri.so - I realized that I'd only installed the nvidia driver packages and not the "full stack" - i.e. nvidia-driver-525 and dependencies. Perhaps I was running with an unsupported config the first time. I tried installing that stack and reproducing again, but this time I saw no problem doing "switch user" at all. At that point my reservation expired and I was unable to collect logs from this session. Next I'll try to do this all over again, making sure to install both nvidia-driver-525 linux-modules-nvidia-525-generic and see if I can reproduce. -- 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login
** Attachment added: "_usr_bin_gnome-shell.1002.crash" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2015386/+attachment/5661328/+files/_usr_bin_gnome-shell.1002.crash ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: 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/2015386 Title: gnome-shell crashes after "switching to" a new user from an existing login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2015386/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958583] Re: entering gnome lockscreen causes astfb displays to hang
** Attachment added: "sosreport-starbuck-2022-01-20-ziauesz.tar.xz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+attachment/972/+files/sosreport-starbuck-2022-01-20-ziauesz.tar.xz -- 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/1958583 Title: entering gnome lockscreen causes astfb displays to hang To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1958583/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1958583] Re: entering gnome lockscreen causes display to hang
I found that this issue also impacts upstream kernels, so I bisected and found that the problem was introduced in this commit: commit d6ddbd5c97d1b9156646ac5c42b8851edd664ee2 Author: Thomas Zimmermann Date: Thu May 7 11:06:40 2020 +0200 drm/ast: Don't check new mode if CRTC is being disabled I verified that this issue can still be reproduced with current upstream (currently between v5.16 & v5.17-rc1), and that reverting the above patch[*] causes it to go away. [*] The patch doesn't cleanly revert because the underlying code has evolved a bit, but it's straightforward to back out: diff --git a/drivers/gpu/drm/ast/ast_mode.c b/drivers/gpu/drm/ast/ast_mode.c index 956c8982192b..336c545c46f5 100644 --- a/drivers/gpu/drm/ast/ast_mode.c +++ b/drivers/gpu/drm/ast/ast_mode.c @@ -1012,9 +1012,6 @@ static int ast_crtc_helper_atomic_check(struct drm_crtc *crtc, const struct drm_format_info *format; bool succ; - if (!crtc_state->enable) - return 0; /* no mode checks if CRTC is being disabled */ - ast_state = to_ast_crtc_state(crtc_state); format = ast_state->format; ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Summary changed: - entering gnome lockscreen causes display to hang + entering gnome lockscreen causes astfb displays to hang ** Description changed: When I install ubuntu-desktop on servers with an AMI BMC, I find a - remote desktop running over BMC's virtual KVM display hangs when I + remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. A commonality of these systems is that they use the astfb driver. I've found that this symptom follows the kernel. If I run a jammy desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just the kernel back to focal's 5.4, the issue vanishes. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument ** Description changed: When I install ubuntu-desktop on servers with an AMI BMC, I find a remote desktop running on the BMC's virtual KVM display hangs when I transition to the lock screen. The screen either goes blank and fails to wake up on keyboard/mouse input - or the lock screen appears but freezes, leaving the clock display frozen in time. - - A commonality of these systems is that they use the astfb driver. - - I've found that this symptom follows the kernel. If I run a jammy - desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just - the kernel back to focal's 5.4, the issue vanishes. Correlated with the issue are the following messages in /var/log/syslog, which are emitted when I move the mouse cursor while the lock screen is frozen: Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jan 19 20:34:53 starbuck gnome-shell[5002]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument + + A commonality of these systems is that they use the astfb driver. + + I've found that this issue follows the kernel version. If I run a jammy + desktop with jammy's 5.15 kernel, this issue occurs. If I downgrade just + the kernel back to focal's 5.4, the issue vanishes. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu.
[Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
I asked our desktop team about this, and Iain Lane mentioned that Ubuntu overrides the GNOME default of auto-suspending, but that override only takes effect if you have the ubuntu-settings package installed. I tested this out on a Saber system, and I can confirm that it does seem to only happen when gdm is installed/running and ubuntu-settings is *not* installed. And that explains why I was unable to reproduce in Comment #5. There I had installed ubuntu-desktop which would bring in ubuntu- settings. It also explains why the CUDA-11 dependency chain *did* cause the problem on the x86 server in Comment #8. In that case, gdm3 is getting installed as a Recommends somewhere in the dependency chain - but it does not pull in gnome-settings. I'll therefore go ahead and close the 'linux' task as Invalid - this isn't a kernel bug. I'll mark the gdm3 bug as "Won't Fix" because, in theory, we could change the defaults inside of gdm3 itself - but we instead recommend users install ubuntu-settings to override the defaults. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Won't Fix -- 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/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
** Changed in: gdm3 (Ubuntu) Status: Incomplete => Confirmed -- 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/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min
@Naresh: see my comment #4, asking if you are running Ubuntu Desktop. dmesg doesn't tell me that - but an sosreport would, if you can attach that. We've recently hit this on an x86 server, and did tie that back to the system having a desktop installed (Nvidia CUDA 11 somehow brings in gdm as a dependency), so I'm still suspecting the same here. ** Also 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/1862559 Title: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1862559/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863812] Re: tells me an update is available, but i'm running a newer version
I suspect it did autorefresh, but didn't confirm. But yeah, the issue IMO is the UI one. Once I click update, I'd expect gnome-software to see that it was already up to date and respond as though the update was complete - i.e., go away :) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1863812 Title: tells me an update is available, but i'm running a newer version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1863812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1863812] [NEW] tells me an update is available, but i'm running a newer version
Public bug reported: Today I noticed that the software manager is telling me there's a juju update available (2.7.1), with an option to update. When I click update, it says "Unable to update juju: snap has no updates available". Sure enough, `snap info` confirms that I'm already on 2.7.*2*: channels: stable:2.7.2 2020-02-18 (10671) 72MB classic candidate: ↑ beta: ↑ edge: 2.8-beta1+develop-29900ab 2020-02-18 (10690) 81MB classic 2.7/stable:2.7.2 2020-02-18 (10671) 72MB classic 2.7/candidate: 2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic 2.7/beta: ↑ 2.7/edge: 2.7.3+2.7-aa61342 2020-02-18 (10691) 81MB classic 2.6/stable:2.6.102019-10-30 (9484) 69MB classic 2.6/candidate: ↑ 2.6/beta: ↑ 2.6/edge: 2.6.11+2.6-b96e1222020-01-22 (10408) 75MB classic 2.5/stable:2.5.8 2019-06-27 (8361) 67MB classic 2.5/candidate: ↑ 2.5/beta: ↑ 2.5/edge: 2.5.9+2.5-36af233 2019-07-24 (8546) 73MB classic 2.4/stable:2.4.7 2019-05-23 (6012) 58MB classic 2.4/candidate: ↑ 2.4/beta: ↑ 2.4/edge: ↑ 2.3/stable:2.3.9 2018-09-19 (5267) 55MB classic 2.3/candidate: ↑ 2.3/beta: ↑ 2.3/edge: 2.3.10+2.3-41313d12019-03-25 (7080) 55MB classic installed: 2.7.2(10671) 72MB classic gnome-software 3.35.2-0ubuntu2 snapd 2.43.3+git1.8109f8 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot from 2020-02-18 15-50-41.png" https://bugs.launchpad.net/bugs/1863812/+attachment/5329403/+files/Screenshot%20from%202020-02-18%2015-50-41.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1863812 Title: tells me an update is available, but i'm running a newer version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1863812/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783138] Re: hinic interfaces aren't getting predictable names
** Changed in: systemd (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => dann frazier (dannf) -- 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/1783138 Title: hinic interfaces aren't getting predictable names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783138] Re: hinic interfaces aren't getting predictable names
fyi, this appears to fix the problem for me. ** Patch added: "0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783138/+attachment/5166848/+files/0001-hinic-Link-the-logical-network-device-to-the-pci-dev.patch ** Also affects: linux (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/1783138 Title: hinic interfaces aren't getting predictable names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1783138] [NEW] hinic interfaces aren't getting predictable names
Public bug reported: On a HiSilicon D06 system we noticed that interfaces provided by a plug- in "HINIC" network card are not getting assigned predictable names. We're getting "ethX" names instead of the expected "enPblah" names. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Bionic) 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/1783138 Title: hinic interfaces aren't getting predictable names To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1783138/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1714431] Re: Can not login after switch to runlevel 3 from 1
** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu) Status: New => Fix Released ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- 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/1714431 Title: Can not login after switch to runlevel 3 from 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1714431/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1686784] [NEW] no predictable names for platform (non-PCI) NICs
Public bug reported: [Impact] Systems may have NICs attached to the "platform" bus. These are NICs that are onboard, but not attached to a PCI(-like) bus. Rather, they are described by firmware directly. None of the naming policies enabled by Ubuntu by default matches these NICs, so they end up having unpredictable names. In the case where other NICs are attached (e.g. PCIe cards), the ethN enumeration race occurs, making it impossible to have an interface name that is persistent across reboots. That is, if you do a network install over "eth0", on reboot that NIC now maybe "eth3", which causes it to fail to start the network on boot. The HiSilicon D05 boards are an example of this. It has 4 onboard NICs that are described by ACPI directly, and may also have other PCIe NICs plugged in. [Test Case] Boot a system with the characteristics described above, and check to see if any "ethN" interfaces exist. [Regression Risk] TBD - depends on the proposed solution. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Xenial) Importance: Undecided Status: Confirmed ** Affects: systemd (Ubuntu Yakkety) Importance: Undecided Status: New ** Affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Zesty) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Yakkety) Importance: Undecided Status: New ** Also affects: systemd (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Xenial) Status: New => Confirmed -- 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/1686784 Title: no predictable names for platform (non-PCI) NICs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1686784/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1656474] [NEW] FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)
Public bug reported: emacs25 25.1+1-3ubuntu1 reliably fails to build on the LP arm64 buildds. I wasn't able to reproduce this on bare metal but, while trying to simulate the buildd environment, I have found that it does *sometimes* occur when building in a KVM VM on an X-Gene system. #0 __flockfile (stream=0x0) at ../sysdeps/pthread/flockfile.c:28 #1 0x004e0cc4 in terminate_due_to_signal (sig=sig@entry=11, backtrace_limit=backtrace_limit@entry=40) at emacs.c:381 #2 0x004f74f8 in handle_fatal_signal (sig=sig@entry=11) at sysdep.c:1601 #3 0x004f7734 in deliver_thread_signal (sig=sig@entry=11, handler=0x4f74e8 ) at sysdep.c:1575 #4 0x004f77ac in deliver_fatal_thread_signal (sig=11) at sysdep.c:1613 #5 handle_sigsegv (sig=11, siginfo=, arg=) at sysdep.c:1695 #6 #7 unchain_marker (marker=marker@entry=0x130ad18) at marker.c:605 #8 0x005334a4 in free_marker (marker=marker@entry=19967257) at alloc.c:3850 #9 0x00505b98 in signal_before_change (preserve_ptr=0x0, end_int=44894, start_int=9854976) at insdel.c:2041 #10 prepare_to_modify_buffer_1 (start=start@entry=11223, end=end@entry=11223, preserve_ptr=preserve_ptr@entry=0x0) at insdel.c:1867 [...] ** Affects: emacs25 (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: emacs25 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to emacs25 in Ubuntu. https://bugs.launchpad.net/bugs/1656474 Title: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)
This does not appear to be reproducible w/ pristine upstream 25.1 source built with the following commands: ./autogen.sh CFLAGS="-g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wall" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-Bsymbolic-functions -Wl,-z,relro" REL_ALLOC=no ./configure --build aarch64-linux-gnu --prefix=/usr --sharedstatedir=/var/lib --libexecdir=/usr/lib --localstatedir=/var/lib --infodir=/usr/share/info --mandir=/usr/share/man --with-pop=yes --enable-locallisppath=/etc/emacs25:/etc/emacs:/usr/local/share/emacs/25.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/25.1/site-lisp:/usr/share/emacs/site-lisp --with-sound=alsa --build aarch64-linux-gnu --prefix=/usr --sharedstatedir=/var/lib --libexecdir=/usr/lib --localstatedir=/var/lib --infodir=/usr/share/info --mandir=/usr/share/man --with-pop=yes --enable-locallisppath=/etc/emacs25:/etc/emacs:/usr/local/share/emacs/25.1/site-lisp:/usr/local/share/emacs/site-lisp:/usr/share/emacs/25.1/site-lisp:/usr/share/emacs/site-lisp --with-sound=alsa --with-x=yes --with-x-toolkit=gtk3 --with-toolkit-scrol l-bars make -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to emacs25 in Ubuntu. https://bugs.launchpad.net/bugs/1656474 Title: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)
** Attachment added: "gdb bt full" https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+attachment/4804071/+files/gdb-bt-full.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to emacs25 in Ubuntu. https://bugs.launchpad.net/bugs/1656474 Title: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)
** Attachment added: "gdb bt" https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+attachment/4804070/+files/gdb-bt.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to emacs25 in Ubuntu. https://bugs.launchpad.net/bugs/1656474 Title: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/emacs25/+bug/1656474/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1546714] Re: System not booting when /home is on separate LUKS-encrypted partition
** Also affects: ubuntu-z-systems 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/1546714 Title: System not booting when /home is on separate LUKS-encrypted partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1546714/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1560545] Re: Some or all OSA devices may be unavailable after boot if too many are visible
Marking systemd and sysconfig-hardware as affected due to these messages in syslog: systemd-udevd[4387]: Process '/sbin/hwup -A -D /devices/css0/0.0.0600/0.0.2f17 ccw 0.0.2f17' failed with exit code 9. ** Package changed: ubuntu => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Dimitri John Ledkov (xnox) ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Also affects: sysconfig (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/1560545 Title: Some or all OSA devices may be unavailable after boot if too many are visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysconfig/+bug/1560545/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1354306] [NEW] gpio shutdown trigger for ProLiant m400 cartridges
Public bug reported: Similar to the m800 case in LP: #1347776, udev/systemd also needs to know how to trigger a graceful shutdown on ProLiant m400 cartridges. ** 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/1354306 Title: gpio shutdown trigger for ProLiant m400 cartridges To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1354306/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1354306] Re: gpio shutdown trigger for ProLiant m400 cartridges
** Bug watch added: freedesktop.org Bugzilla #82347 https://bugs.freedesktop.org/show_bug.cgi?id=82347 ** Also affects: systemd via https://bugs.freedesktop.org/show_bug.cgi?id=82347 Importance: Unknown Status: Unknown -- 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/1354306 Title: gpio shutdown trigger for ProLiant m400 cartridges To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1354306/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1347776] Re: shutdown trigger on gpio_keys.X for armhf hardware
** Bug watch added: freedesktop.org Bugzilla #82347 https://bugs.freedesktop.org/show_bug.cgi?id=82347 ** Also affects: systemd via https://bugs.freedesktop.org/show_bug.cgi?id=82347 Importance: Unknown Status: Unknown -- 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/1347776 Title: shutdown trigger on gpio_keys.X for armhf hardware To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1347776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1349566] [NEW] systemd-logind triggered poweroffs ignore upstart services
Public bug reported: systemd-logind has a facility to detect non-ACPI power-off events (e.g. a power button push) and initiate a system shutdown. This facility works in Ubuntu - it manages to shutdown the sysvinit services, but upstart services do not appear to be cleanly shutdown. Among other things, it means that local filesystems don't get properly unmounted. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Attachment added: Console log with --debug --verbose from boot through push of power button https://bugs.launchpad.net/bugs/1349566/+attachment/4164558/+files/console.log ** Summary changed: - systemd-login triggered poweroffs ignore upstart services + systemd-logind triggered poweroffs ignore upstart services -- 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/1349566 Title: systemd-logind triggered poweroffs ignore upstart services To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1349566/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
