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)
--
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
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
--
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:
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
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
--
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
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
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:
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
** 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
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
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-
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:
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
**
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
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:
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:
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
**
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
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:
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:
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
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:
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.
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:
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
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:
** 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
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:
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
**
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
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
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
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
35 matches
Mail list logo
