No, not on modern system. We haven't used that technology for a while.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1756006
Title:
FFe: Support suspend-to-hibernate
St
Public bug reported:
Suspend to hibernate is a new feature that will put the system into
hibernate after a period of time spent in the system's supported sleep
state. This mode will be used on some systems that take suspend to idle
in the future with Ubuntu 18.04.
This feature is available in up
@cyphermox,
I can readily reproduce this using my company's guest network with
current systemd in Bionic. We use "securelogin.networks.dell.com" for
our redirector. If I can provide something useful, happy to do so.
--
You received this bug notification because you are a member of Ubuntu
Touch
** Bug watch added: Debian Bug tracker #890950
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890950
** Changed in: initramfs-tools (Debian)
Importance: Undecided => Unknown
** Changed in: initramfs-tools (Debian)
Status: New => Unknown
** Changed in: initramfs-tools (Debian)
Re
buntu)
Status: Confirmed => Fix Committed
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) => Mario Limonciello (superm1)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
** Changed in: umockdev (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to umockdev in Ubuntu.
https://bugs.launchpad.net/bugs/1724604
Title:
umockdev 0.9.4-1 causes test suite failures
** Bug watch added: github.com/martinpitt/umockdev/issues #64
https://github.com/martinpitt/umockdev/issues/64
** Also affects: umockdev via
https://github.com/martinpitt/umockdev/issues/64
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are
Public bug reported:
Updating to umockdev 0.9.4-1 is causing failures in the fwupd test suite
(which will lead to FTBFS on fwupd)
The output from the failed tests:
8/10 thunderbolt-self-test FAIL 0.20 s
--- command ---
LD_PRELOAD='libumockdev-preload.so.0'
/build/build/obj
Here you go. This is from a kernel built on 4.14-rc4 right after boot
where dhclient is failing.
** Attachment added: "sbin.dhclient"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1721278/+attachment/4974238/+files/sbin.dhclient
--
You received this bug notification because you ar
>This isn't really an *Ubuntu* issue per se as we've never claimed to
support apparmor profiles with non-Ubuntu kernels.
So I think the problem is that kernel team maintains a PPA of mainline
kernels and often will ask users to check stuff with mainline kernel
when there are bugs that come up. Th
And FWIW the /sbin/dhclient and /usr/lib/NetworkManager/nm-dhcp-helper
errors are also family="unix" denying create operations.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bug
I've personally confirmed this with both artful and xenial userspace with
4.14-rc4.
A temporary solution other than compiling without apparmor is to do
teardown/stop
# /etc/init.d/apparmor teardown
# /etc/init.d/apparmor stop
--
You received this bug notification because you are a member of Ubu
I've found that it's more than just cups blows up, some networking
related items (DHCP client, network manager IIRC) also explode.
** Summary changed:
- apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed"
+ apparmor="DENIED" operation="create" profile="/usr/sbin/cups-browsed" w/
Just to add clarity to this issue:
The ID's in the old FW release are not supported by CCID and have been removed
in git:
https://github.com/LudovicRousseau/CCID/commit/e6a7548623f35d428f9f410f4b885fd04e34070a
https://github.com/LudovicRousseau/CCID/commit/2f68054ce81aa10ec60adf9a92c66dca64bdd415
** Changed in: pcsc-lite (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.
https://bugs.launchpad.net/bugs/1596662
Title:
pcscd fails to read CAC card data,
dell-recovery has dropped the code related to aptdaemon.
https://github.com/dell/dell-recovery/commit/df1e943cd111c24e1cf3357701caace177f46de8
It will be part of the next release.
** Changed in: dell-recovery (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification bec
This was also happening in Unity7 and fixed with this kernel commit:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-xenial.git/commit/?id=8afcf4521804ffb323cd3a23b382159a35493582
I would expect that same fix to fix unity8, but you can confirm.
--
You received this bug notification because you are a
https://github.com/torvalds/linux/blob/v4.11-rc5/drivers/platform/x86
/intel-vbtn.c#L38
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: linux (Ubuntu)
Status: Incomplete => Opinion
** Changed in: linux (Ubuntu)
Status: Opinion => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net
Public bug reported:
Using the current Ubuntu 17.04 image and selecting the unity8 session,
the XPS 9365 does not automatically switch modes.
When switching to tablet mode, the ACPI driver INT33D6 which is bound to
intel-vbtn will emit a few 0xcc events. When switching to desktop mode,
the same
This is actually a kernel bug where the PWM isn't saved. It affects the
specific display type in this machine. It's been fixed upstream
already, and was brought into Ubuntu 16.04 (See SRU
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1625932).
The Precision 5510 however ships with Ubuntu
*** This bug is a duplicate of bug 1646537 ***
https://bugs.launchpad.net/bugs/1646537
** This bug has been marked a duplicate of bug 1646537
Backlight sometimes fails to resume from suspend & screen brightness
sometimes will not dim below 100%
--
You received this bug notification becau
** Package changed: fwupd (Ubuntu) => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1615964
Title:
Mouse pointer is invisible after suspend
Status in xorg pac
*** This bug is a duplicate of bug 1591868 ***
https://bugs.launchpad.net/bugs/1591868
** This bug is no longer a duplicate of bug 1602485
fwupd gnome-software eat cpu
** This bug has been marked a duplicate of bug 1591868
fwupd consuming 100% CPU
--
You received this bug notification
*** This bug is a duplicate of bug 1591868 ***
https://bugs.launchpad.net/bugs/1591868
** This bug is no longer a duplicate of bug 1602485
fwupd gnome-software eat cpu
** This bug has been marked a duplicate of bug 1591868
fwupd consuming 100% CPU
--
You received this bug notification
I've adjusted the description for the alternate approach in doing this
entirely in the kernel. I've submitted a patch to LKML for this here.
https://patchwork.kernel.org/patch/9148319/
** No longer affects: network-manager (Ubuntu)
** No longer affects: systemd (Ubuntu)
** Description changed:
** No longer affects: alsa-driver (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after startup in 16.04
Sta
Well that's interesting, it looks like your audio device might have a dfu
mode. I wonder if that's the case for the other reporters. Can you please
also share lsusb output? Everyone affected it would be great to share both
of these so that upstream can make sense of common denominations to figure
w
Great thanks, can you please also share sudo lsusb -v output?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1574079
Title:
USB audio device is not recognized after st
Abkishek,
Can you please try to reproduce it with fwupd running with debug flags as
listed above?
You might have to unplug it, run with debug flags and plug back in.
On Sat, May 28, 2016, 09:50 Abhishek Chaudhary
wrote:
> Confirmed bug. Audio interface "focusrite solo" isn't found on startup.
Hi @Jay and @Kingfriday,
If this is continuously reproducible for you, it would be great to get some
debug output from fwupd to figure out why this is happening. I unfortunately
haven't been able to reproduce it using my USB audio device (Dell TB15 dock).
Can you try to follow these steps to ge
Depends which problem was bothering you. It's coming in two updates. One to
upower (related to run time problems) and the other in unity settings
daemon (related to turning on at lock screen). The unity settings daemon
one is in proposed and if no regressions are found it will come to updates
in a
Sorry - USD one is related to turning on boot I mean.
On Wed, May 18, 2016, 09:59 Mario Limonciello
wrote:
> Depends which problem was bothering you. It's coming in two updates. One
> to upower (related to run time problems) and the other in unity settings
> daemon (related to
Changing kernel to confirmed. This is a backport request for when that
patch lands upstream. It's still in discussions.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Attachment added: "udev script"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1579984/+attachment/4659578/+files/dell_dock.sh
** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu)
Importance: Undecided
Statu
Public bug reported:
Dell systems with Type-C ports support a feature called "MAC address" pass
through.
This feature allows systems to set a persistent system MAC address to be used
with the TB15, WD15 and Type-C ethernet adapter.
More information is available here:
http://www.dell.com/support
*** This bug is a duplicate of bug 1576726 ***
https://bugs.launchpad.net/bugs/1576726
I backported that patch and manually tested a build with it applied. It
will be fixed also by moving to the 1.2.0 release.
--
You received this bug notification because you are a member of Ubuntu
Touch see
This might be https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1576215
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1575289
Title:
Wired Connectio
*** This bug is a duplicate of bug 1576726 ***
https://bugs.launchpad.net/bugs/1576726
Yes, I confirmed that patch has resolved it for me. Tried it 10 times
and didn't hit any failures. This patch is actually part of 1.2.0 which
is being SRU'ed right now.
https://bugs.launchpad.net/ubuntu/+
Public bug reported:
When I boot up my network doesn't automatically connect. I instead see
when I click the network manager applet that it's got no Wifi devices
listed. It thinks my wireless card is an ethernet device. This isn't
true and I have no ethernet devices in my system.
When this sit
I've definitely reproduced this as recently as today on a real machine on
16.04 (fully up to date) with similar symptoms described as reaching the
shutdown target and then just hanging for a while.
I also uses sysrq to recover at that point.
I've also noticed this in Virtualbox, particularly afte
I had a similar situation happen where it thought that my wireless
device was an ethernet device shortly after the NM upgrade. Sometimes
it's detected properly and I see networks in NM's applet, other times it
gets confused and thinks it's an ethernet device.
Snapshot of my kernel log when this h
At least in 16.04 ubuntu-desktop Recommends gnome-keyring which Depends
on pinentry-gnome3.
** Changed in: gnupg2 (Ubuntu)
Status: New => Invalid
** Changed in: gnome-keyring (Ubuntu)
Status: New => Fix Released
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Invalid
--
** Changed in: gpgme1.0 (Ubuntu)
Status: Fix Released => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1564234
Title:
gpgme1.0 doesn't work properly wit
Public bug reported:
In trying to debug
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1536871/comments/16
there has been the discovery that gpgme doesn't actually verify the
version of gnupg on the system and sends arguments to it that are only
supported in Gnupg 2.1.
http://git.gnupg.org/
The following two patches will resolve this issue:
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?h=for-next&id=e1e62b98ebddc3234f3259019d3236f66fc667f8
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/?h=for-next&id=f3b703326541d0c1ce85f5e570f6d2b6bd4296ec
** Changed in: dell-sputnik
Status: New => Invalid
** Changed in: alsa-driver (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bug
I reproduced this once, but it was while switching HDA and I2S modes, so
i'm suspecting that it might have been related to the default device
being selected. Are you still able to reproduce this on demand?
When I did reproduce it, xev did pick up keycodes, but no indicator in
the popup when they
Based on posts at that community forum, it sounds like this should be
fixed in 3.16. Affected users can try to install linux-generic-lts-
utopic on 14.04 to see if it resolves the issue.
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)
** Changed in: dell-sputnik
Status: New =>
101 - 149 of 149 matches
Mail list logo
