[Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min

2020-09-15 Thread dann frazier
@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 dep

[Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min

2020-09-17 Thread dann frazier
** 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 sy

[Bug 1862559] Re: ubuntu 19.10: unresponsive/freezes on ThunderX2 if system is idle for ~22min

2020-09-21 Thread dann frazier
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 whe

[Bug 1958583] Re: entering gnome lockscreen causes display to hang

2022-01-20 Thread dann frazier
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 disabl

[Bug 1958583] Re: entering gnome lockscreen causes astfb displays to hang

2022-01-20 Thread dann frazier
** 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,

[Bug 1783138] [NEW] hinic interfaces aren't getting predictable names

2018-07-23 Thread dann frazier
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 St

[Bug 1783138] Re: hinic interfaces aren't getting predictable names

2018-07-23 Thread dann frazier
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 aff

[Bug 1783138] Re: hinic interfaces aren't getting predictable names

2018-07-23 Thread dann frazier
* 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 system

[Bug 1863812] Re: tells me an update is available, but i'm running a newer version

2020-03-17 Thread dann frazier
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 me

[Bug 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login

2023-04-05 Thread dann frazier
** 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 notificatio

[Bug 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login

2023-04-11 Thread dann frazier
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 t

[Bug 2016193] [NEW] "switch to" a new user immediately aborts, returns to previous user's session

2023-04-13 Thread dann frazier
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

[Bug 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login

2023-04-13 Thread dann frazier
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/b18128bc669a4a4d1f371a58f4f5d719833ab52c5ab794dbbc9d9e55b45d12516efcc5085f9d93e4d219bc6948f530cdaa31ddf8e34b7e9

[Bug 2015386] Re: gnome-shell crashes after "switching to" a new user from an existing login

2023-04-13 Thread dann frazier
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 subscr

[Bug 2015386] Re: NVIDIA quad-GPU system crashes starting Wayland session

2023-04-14 Thread dann frazier
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://bug

[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

2023-04-17 Thread dann frazier
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 betwe

[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

2023-04-17 Thread dann frazier
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

Re: [Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

2023-04-18 Thread dann frazier
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

[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

2023-04-19 Thread dann frazier
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 wi

Re: [Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

2023-04-19 Thread dann frazier
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 is

[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

2023-04-21 Thread dann frazier
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://bug

[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

2023-04-21 Thread dann frazier
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.She

[Bug 2006059] Re: systemd refuses to start secondary Xorg logins [org.gnome.Shell@x11.service: Skipped due to 'exec-condition'.]

2023-04-24 Thread dann frazier
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

[Bug 1863812] [NEW] tells me an update is available, but i'm running a newer version

2020-02-18 Thread dann frazier
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*: chann

[Bug 1686784] [NEW] no predictable names for platform (non-PCI) NICs

2017-04-27 Thread dann frazier
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

[Bug 1714431] Re: Can not login after switch to runlevel 3 from 1

2017-09-01 Thread dann frazier
** 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

[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)

2017-01-13 Thread dann frazier
** 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/1

[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)

2017-01-13 Thread dann frazier
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

[Bug 1656474] Re: FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)

2017-01-13 Thread dann frazier
** 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.

[Bug 1656474] [NEW] FTBFS on arm64: make[4]: *** [../../lisp/cedet/semantic/bovine/c-by.el] Segmentation fault (core dumped)

2017-01-13 Thread dann frazier
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 __flockf

[Bug 1560545] Re: Some or all OSA devices may be unavailable after boot if too many are visible

2016-03-22 Thread dann frazier
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:

[Bug 1546714] Re: System not booting when /home is on separate LUKS-encrypted partition

2016-04-08 Thread dann frazier
** 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 sepa

[Bug 1349566] [NEW] systemd-logind triggered poweroffs ignore upstart services

2014-07-28 Thread dann frazier
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 thi

[Bug 1354306] [NEW] gpio shutdown trigger for ProLiant m400 cartridges

2014-08-08 Thread dann frazier
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 mem

[Bug 1354306] Re: gpio shutdown trigger for ProLiant m400 cartridges

2014-08-08 Thread dann frazier
** 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 membe

[Bug 1347776] Re: shutdown trigger on gpio_keys.X for armhf hardware

2014-08-08 Thread dann frazier
** 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 membe