[Bug 1925750] Re: Ubuntu 21.04 not loading correctly intel graphics driver
I honestly don't know much about how these dual-GPU systems work. I suspect there must be some firmware interfaces for enabling/disabling the discrete GPU, I have no idea whether those are standardized or platform-specific. Assuming the kernel supports the interfaces for your platform, I also don't know what userspace packages are necessary to utilize those interfaces. You might want to try searching for instructions for your specific machine. You might also check the firmware setup, there may be options there related to enabling/disabling the discrete graphics. -- 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/1925750 Title: Ubuntu 21.04 not loading correctly intel graphics driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1925750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1925750] Re: Ubuntu 21.04 not loading correctly intel graphics driver
The reason you don't see any Intel graphics drivers in the "Addditional Drivers" tab is that none are needed. The Intel graphics driver (i915) is open source and already included in the kernel, and from your logs it has been loaded. There's nothing I'm seeing currently which indicates a kernel issue. My best guess as to which package decides whether or not to offer wayland sessions is gdm3, so I'll add that to the bug report. ** 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/1925750 Title: Ubuntu 21.04 not loading correctly intel graphics driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1925750/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1922545] Re: gnome-system-monitor fails to launch
I don't see a reason this was filed against the kernel. Changing to gnome-system-monitor. ** Package changed: linux (Ubuntu) => gnome-system-monitor (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1922545 Title: gnome-system-monitor fails to launch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1922545/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1776670] [NEW] systemd 237-3ubuntu10 ADT test failure with linux 4.17.0-2.3
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-cosmic-canonical-kernel-team-bootstrap/cosmic/i386/s/systemd/20180613_003420_38c07@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1776670 Title: systemd 237-3ubuntu10 ADT test failure with linux 4.17.0-2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1776670/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1731911] Re: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait()
My bug was duped to this one. After dist-upgrading 18.04 yesterday I consistently get a crash logging into any gnome sessions, only the unity session doesn't crash on me. -- 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/1731911 Title: Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1731911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1733328] Re: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9
** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1733328 Title: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1733328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1733328] [NEW] systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9
Public bug reported: Testing failed on: i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/i386/s/systemd/20171118_221900_c23d7@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/s/systemd/20171120_131930_c23d7@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1733328 Title: systemd 235-2ubuntu3 ADT test failure with linux 4.14.0-7.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1733328/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1727850] [NEW] systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure-hwe-edge-4.13 ** Tags added: kernel-adt-failure ** Description changed: Testing failed on: - amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz - s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/s390x/s/systemd/20171025_134325_0db62@/log.gz + amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial/xenial/amd64/s/systemd/20171025_152041_0db62@/log.gz -- 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/1727850 Title: systemd 229-4ubuntu20 ADT test failure with linux-hwe-edge 4.13.0-16.19~16.04.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727850/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1717928] [NEW] gnome crashes when using qemu display
Public bug reported: Using the qemu vga display under gnome is reliably causing gnome to crash on my laptop. I've seen this when using libvirt and also when invoking qemu from the command line. I've tried several display options for qemu: -vga qxl -vga virtio -display gtk All result in the crash. No crash report is appearing in /var/crash after this happens, but I checked dmesg the last time and found this: [15078.446564] gnome-shell[10327]: segfault at 8 ip 7f4c53c794af sp 7ffd7eb03e90 error 4 in libmutter-cogl-1.so[7f4c53c14000+a5000] The crash usually doesn't happen right away. Sometimes it happens a few seconds after the display is opened, other times it's happened when I've moved to another window and then select the qemu display using Alt-Tab. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 18 08:11:44 2017 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2017-03-30 (172 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170329) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-04-27 (143 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug artful wayland-session -- 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/1717928 Title: gnome crashes when using qemu display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1717928/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715397] Re: systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10
I see adt failures with 4.12 as well, looks like a regression in ppc64-diag. Changing affected package. ** Package changed: systemd (Ubuntu) => ppc64-diag (Ubuntu) -- 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/1715397 Title: systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppc64-diag/+bug/1715397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715397] [NEW] systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10
Public bug reported: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170906_131209_2a96a@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1715397 Title: systemd 234-2ubuntu9 ADT test failure with linux 4.13.0-9.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1715397/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712865] Re: systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13
armhf passed after re-running, so I guess we can ignore it. Since the s390x failure is fixed in -proposed I'll close the bug as invalid, I can hint away the kernel test failure since it's clearly not a kernel issue. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1712865 Title: systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1712865] [NEW] systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13
Public bug reported: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170823_191459_e2f1d@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/s390x/s/systemd/20170824_125405_e2f1d@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1712865 Title: systemd 234-2ubuntu6 ADT test failure with linux 4.12.0-12.13 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1712865/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1710654] [NEW] systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12
Public bug reported: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful/artful/armhf/s/systemd/20170814_062054_7f9b9@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1710654 Title: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-11.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1710654/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1707267] [NEW] systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-9.10
Public bug reported: Testing failed on: s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/s390x/s/systemd/20170728_111056_ccb5f@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1707267 Title: systemd 233-8ubuntu3 ADT test failure with linux 4.12.0-9.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1700806] Re: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5
I failed to follow up. There were no failures when re-running the test, and no errors with 4.12.0-5.6, so marking this invalid. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1700806 Title: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1700806] [NEW] systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5
Public bug reported: Testing failed on: ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-artful-canonical-kernel-team-unstable/artful/ppc64el/s/systemd/20170627_083238_11cda@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1700806 Title: systemd 233-8ubuntu1 ADT test failure with linux 4.12.0-4.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1700806/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1679764] [NEW] systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3
Public bug reported: Testing failed on: armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/armhf/s/systemd/20170329_172954_1ba5b@/log.gz ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: kernel-adt-failure ** Tags added: kernel-adt-failure -- 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/1679764 Title: systemd 232-21ubuntu2 ADT test failure with linux-raspi2 4.10.0-1001.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679764/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1679598] [NEW] TEST-03-JOBS faliing in ADT
Public bug reported: In recent ADT runs TEST-03-JOBS has started failing with various systemd versions. Here's one with 232-19: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/amd64/s/systemd/20170403_174708_e037b@/log.gz and another with 232-21ubuntu2: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/amd64/s/systemd/20170330_184645_3ab85@/log.gz ** 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/1679598 Title: TEST-03-JOBS faliing in ADT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1679598/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1677377] [NEW] ADT failure in boot-smoke test with linux-hwe-edge
Public bug reported: ADT boot-smoke test fails with 4.10 hwe-edge kernel in xenial. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-xenial/xenial/amd64/s/systemd/20170329_130746_29365@/log.gz checking that there are no running jobs FAIL: expected: '' actual: '663 lightdm.service start running' Possibly an issue with lightdm or the kernel, I haven't been able to determine the actual cause from the logs. I also haven't been able to reproduce this failure locally. ** 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/1677377 Title: ADT failure in boot-smoke test with linux-hwe-edge To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1677377/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672542] [NEW] systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15
Public bug reported: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/amd64/s/systemd/20170313_204550_ecb32@/log.gz i386: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/i386/s/systemd/20170311_013142_b5cf9@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-zesty/zesty/ppc64el/s/systemd/20170311_020037_b5cf9@/log.gz Upstream tests time out. Last thing displayed in the logs before the timeout is the login prompt from a VM. ** 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/1672542 Title: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0-13.15 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1672499] [NEW] systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf
Public bug reported: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-zesty/zesty/armhf/s/systemd/20170310_221057_b5cf9@/log.gz root-unittests fails: -> Unit a.service: Description: a.service Instance: n/a Unit Load State: not-found Unit Active State: inactive State Change Timestamp: n/a Inactive Exit Timestamp: n/a Active Enter Timestamp: n/a Activeerror: org.freedesktop.systemd1.NoSuchUnit: Unit c.service not found. Assertion 'r == 0' failed at ../src/test/test-engine.c:62, function main(). Aborting. Exit Timestamp: n/a ** 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/1672499 Title: systemd 232-18ubuntu1 ADT test failure with linux 4.10.0.13.15 on armhf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1672499/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1625217] [NEW] udev sometimes doesn't apply systemd tag to devices
Public bug reported: Since upgrading this machine to yakkety I've seen periodic hangs during booting. If I wait long enough systemd give up and drops to maintenance mode. Looking in the journal I see events like this: Sep 19 08:24:22 ubuntu-xps13 systemd[1]: dev-disk-by\x2duuid- 63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device: Job dev-disk-by \x2duuid-63cd6483\x2ddf95\x2d4426\x2d916e\x2d8c28becbfd8f.device/start timed out. Searching on the internet indicates that this happen if devices reported by udev don't have the "systemd" tag, and I find that they do not have the tag when the boot times out but they do have the tag when boot does not time out. This happens once for every 3 or 4 boots and with both 4.4 and 4.8 kernels. I'm attaching the output of 'journalctl -xb' and 'udevadm info --export-db' from a timed-out boot. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: udev 231-6 ProcVersionSignature: Ubuntu 4.8.0-11.12-generic 4.8.0-rc6 Uname: Linux 4.8.0-11-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 19 09:27:08 2016 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-19 (577 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110) MachineType: Dell Inc. XPS 13 9343 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-11-generic root=UUID=bdad03f3-06c0-439d-8869-32fad0b1851b ro quiet splash SourcePackage: systemd UpgradeStatus: Upgraded to yakkety on 2016-01-08 (254 days ago) dmi.bios.date: 05/15/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TM99H dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 13 9343 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug yakkety ** Attachment added: "Output of 'journalctl -xb'" https://bugs.launchpad.net/bugs/1625217/+attachment/4743654/+files/journal.txt -- 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/1625217 Title: udev sometimes doesn't apply systemd tag to devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1625217/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1317179] [NEW] lxc containers fail to start in trusty with newer kernels
Public bug reported: When running a trusty userspace with a newer kernel (e.g. 3.15-rc4), attempting to start a container fails: $ lxc-start -n p2 lxc_container: call to cgmanager_create_sync failed: invalid request lxc_container: Failed to create net_cls:p2 lxc_container: Error creating cgroup net_cls:p2 lxc_container: failed creating cgroups lxc_container: failed to spawn 'p2' Iiuc, this seems to be caused new cgroups in the kernel which aren't enabled for systemd but that lxc tries to configure anyway. ** Affects: systemd (Ubuntu) Importance: Medium Status: Fix Released ** Affects: systemd (Ubuntu Trusty) Importance: Medium Status: Confirmed ** Also affects: lxc Importance: Undecided Status: New ** No longer affects: lxc (Ubuntu) ** Also 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/1317179 Title: lxc containers fail to start in trusty with newer kernels To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1317179/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1016724] Re: Laptop brightness always reverts to maximum on 12.04
In general the kernel doesn't choose the backlight level, it only applies the backlight level chosen by userspace. It's usually g-s-d that provides the brightness values to the kernel, so I'm moving the bug to that package. ** Package changed: linux (Ubuntu) => gnome-settings-daemon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1016724 Title: Laptop brightness always reverts to maximum on 12.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1016724/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 974260] Re: Brightnes of laptop panel is set to minimum when system starts
This probably isn't a kernel issue. Backlight drivers generally only change the brightness when told to do so by userspace, although sometimes system firmware plays a role as well. But based on the described behavior, I suspect that it was userspace setting the brightness value when the login screen appeared. gnome- settings-daemon is what will actually be applying the brightness settings, so I'm going to reassign the Linux task to that. ** Package changed: linux (Ubuntu) => gnome-settings-daemon (Ubuntu) ** Changed in: gnome-settings-daemon (Ubuntu) Status: Triaged => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/974260 Title: Brightnes of laptop panel is set to minimum when system starts To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/974260/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 947748] Re: Brightness control not working after latest update
** Attachment added: "Debug output from g-s-d 3.3.91-0ubuntu1" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748/+attachment/2823034/+files/gsd-3.3.91-0ubuntu1.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/947748 Title: Brightness control not working after latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 947748] Re: Brightness control not working after latest update
Attaching g-s-d debug output from working and non-working versions. ** Attachment added: "Debug output from g-s-d 3.3.90-0ubuntu4" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748/+attachment/2823033/+files/gsd-3.3.90-0ubuntu4.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/947748 Title: Brightness control not working after latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 947748] Re: Brightness control not working after latest update
I've reproduced this on a MacBook Air 4,1. Everything is fixed if I back out g-s-d to 3.3.90-0ubuntu4. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/947748 Title: Brightness control not working after latest update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/947748/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 944903] [NEW] Screen and keyboard brightness reset to maximum on reboot/logout
Public bug reported: On the MacBook Air 4,1 I keep seeing the keyboard and screen backlights getting reset to maximum brightness. For the keyboard backlight it happens every time I log out and return to the display manager login screen. For the screen backlight it only happens after booting, but oddly enough it doesn't jump to maximum brightness until the display manager starts. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.90-0ubuntu4 ProcVersionSignature: Ubuntu 3.2.0-17.27-generic 3.2.6 Uname: Linux 3.2.0-17-generic x86_64 ApportVersion: 1.94-0ubuntu1 Architecture: amd64 Date: Fri Mar 2 09:46:40 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20111208) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/944903 Title: Screen and keyboard brightness reset to maximum on reboot/logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/944903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 944903] Re: Screen and keyboard brightness reset to maximum on reboot/logout
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/944903 Title: Screen and keyboard brightness reset to maximum on reboot/logout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/944903/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 933710] Re: MacBook Air 4,1 does not suspend when lid closed
Okay, it turns out the problem is in gnome_rr_output_is_laptop(), so I'm changing this over to libgnome-desktop-3-2. This function needs to check for outputs starting with eDP if it's going to work correctly for this machine. ** Package changed: gnome-settings-daemon (Ubuntu) => gnome-desktop3 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/933710 Title: MacBook Air 4,1 does not suspend when lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop3/+bug/933710/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 933710] Re: MacBook Air 4,1 does not suspend when lid closed
I determined that gsd is opting not to suspend the machine because it thinks an external display is connected. This is not the case, and the i915 driver is showing that only the eDP connector (i.e. the internal display connector) is connected. So it seems that there's some problem with the logic being used to determine whether or not a given output is the built-in panel. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/933710 Title: MacBook Air 4,1 does not suspend when lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/933710/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 933710] Re: MacBook Air 4,1 does not suspend when lid closed
-- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/933710 Title: MacBook Air 4,1 does not suspend when lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/933710/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 933710] [NEW] MacBook Air 4,1 does not suspend when lid closed
Public bug reported: Recently this machine stopped suspending when the lid is closed. It suspends just fine from the menu, but when the lid is closed the backlight turns off for a few seconds then comes back on, but the machine never suspends. I can't find any indication in the logs that anything even attempted to initiate a suspend. Often after opening the lid the desktop has become completely unresponsive. I'm not sure that this is a bug in gnome-settings-daemon, but I've traced it up the stack far enough to know that the events are coming out of the kernel and that upower is detecting the lid status changes and sending out events on dbus. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-settings-daemon 3.3.5-0ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-16.25-generic 3.2.6 Uname: Linux 3.2.0-16-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Thu Feb 16 12:03:27 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64+mac (20111208) ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug precise -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/933710 Title: MacBook Air 4,1 does not suspend when lid closed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/933710/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
