Ok, that sounds good. I'm just curious because I'm on Impish and
experiencing issues with PackageKit due to this bug. So far I've been
restarting the service after I boot.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Nice! When do you think the Ubuntu package will be updated?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1943189
Title:
"cannot refresh whilst network offline" bug
Did you also submit this fix for the previous patch upstream?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1943189
Title:
"cannot refresh whilst network offline" bug
I tested 240-6ubuntu5.2, it fixes the issue on Ubuntu 19.04
** Tags removed: verification-needed-disco
** Tags added: verification-done-disco
** Tags removed: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed
Thanks, I will get it tested soon
--
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/1835809
Title:
AMD Ryzen 3000 series fails to boot
Status in systemd package in Ubuntu:
Sebastien, thanks for getting eyes on it!
Éric, these systems will not boot the 19.04 ISO without either new
firmware fixing the rdrand instruction, or a new ISO updating systemd
with this patch.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
I have tested the patch posted, and it produces a bootable system with
19.04. We will be releasing the patched version of systemd in the
following PPAs:
Pop!_OS - https://launchpad.net/~system76/+archive/ubuntu/pop
Ubuntu support for System76 computers -
A systemd package with this patch applied is building here:
- amd64 -
https://launchpad.net/~system76/+archive/ubuntu/proposed/+build/17236776
- i386 -
https://launchpad.net/~system76/+archive/ubuntu/proposed/+build/17236777
--
You received this bug notification because you are a member of
Public bug reported:
On the new AMD Ryzen 3000 series CPUs, there is an issue with systemd
preventing the boot process from completing. This issue does not affect
the older systemd version in 18.04, but affects the 19.04 version.
Here is a screenshot showing what happens:
When can we expect a release of the proposed xkb-data?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to userspace
I can confirm that xkb-data 2.23.1-1ubuntu1.18.04.1 fixes this issue for
me on bionic.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL
I will try it out on bionic in a few hours
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to userspace
Status in
I can confirm that xkb-data 2.23.1-1ubuntu1.18.10.1 fixes this issue for
me on cosmic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not
That sounds great!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Title:
KEY_RFKILL is not passed to userspace
Status in gnome-settings-daemon package in
Yes, this is still an issue. Please see the above scripts. I am not
aware of why gnome-settings-daemon does not receive the keypress and
trigger airplane mode, if those X11 packages are up to date.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Public bug reported:
Currently administrators are only added to the sudo group. This was
fixed a long time ago by https://bugs.launchpad.net/ubuntu/+source
/gnome-control-center/+bug/810907, but there has likely been a
regression.
** Affects: accountsservice (Ubuntu)
Importance: Undecided
I can also confirm that this fixed the issue in Pop!_OS and elementary
OS.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to fontconfig in Ubuntu.
https://bugs.launchpad.net/bugs/1749546
Title:
Booting a live session is slow
There is no issue with that. We will be able to keep our patches in
initial setup without any effort from Ubuntu and minimal effort from
Pop. We are going to be encouraging full disk encryption, the same as
Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch
In artful and later, a number of kernel drivers send KEY_RFKILL - which
is being ignored by the userspace handling code.
https://elixir.free-electrons.com/linux/v4.13.16/ident/KEY_RFKILL
** Also affects: libxkbcommon (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg
This may also be the cause of https://bugs.launchpad.net/ubuntu/+source
/gnome-settings-daemon/+bug/1722034
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libxkbcommon in Ubuntu.
https://bugs.launchpad.net/bugs/1740894
Thanks for the feedback Robert. I will work on updating my patch.
That does sound like a much cleaner approach.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
Here is a patch without symbol changes or whitespace changes
** Patch added: "accountsservice_encrypt_home.debdiff"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4997109/+files/accountsservice_encrypt_home.debdiff
--
You received this bug notification
Finally, the kernel model from a SATA drive:
$ cat /sys/block/sda/device/model
Samsung SSD 850
And from an NVME drive:
$ cat /sys/block/nvme0n1/device/model
Samsung SSD 950 PRO 256GB
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Here is the information from an NVME drive. Note that ID_MODEL is
missing:
$ udevadm info /dev/nvme0n1
P: /devices/pci:00/:00:1d.0/:6f:00.0/nvme/nvme0/nvme0n1
N: nvme0n1
S: disk/by-id/nvme-Samsung_SSD_950_PRO_256GB_S2GLNX0H717763V
S: disk/by-id/nvme-eui.0025385761b084ef
S:
12:36 seb128 dmj_s76, right, we are likely to get it reviewed next cycle
12:37 seb128 it hasn't been high priority for us since we don't use
gnome-inital-setup and don't plan to for next cycle either
12:37 seb128 but we should be able to review those changes anyways
12:51 jackpot51
IRC Log:
10:39 jackpot51 Can we talk about this patch again?
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216
···
10:39 ubot5 Ubuntu bug 1699216 in gnome-initial-setup (Ubuntu) "Encrypted
home support" [Wishlist,Confirmed]
10:40 jackpot51 I just saw a
This one updates the symbol names - they did not get updated with a
debuild -S
** Patch added: "accountsservice_encrypt_home.debdiff"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4966858/+files/accountsservice_encrypt_home.debdiff
--
You received this
Here is an updated version of the patch for accountsservice
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1699216
Title:
Encrypted home support
Status in
** Patch added: "accountsservice_encrypt_home.debdiff"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4966857/+files/accountsservice_encrypt_home.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
This affects pop-session as well, which uses session overrides similar
to how ubuntu-session does. The desktop icon settings are also
incorrect.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
I have extra whitespace changes in there, I will resubmit with `-w`
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1699216
Title:
Encrypted home support
Status
tsimonq2, here id a debdiff file
** Patch added: "Accountservice Encrypt Home Debdiff"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4945505/+files/accountsservice_encrypt_home.debdiff
--
You received this bug notification because you are a member of
Here is a better patch, ignoring whitespace changes.
** Patch added: "accountsservice_encrypt_home.debdiff"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4945507/+files/accountsservice_encrypt_home.debdiff
--
You received this bug notification because
tsimonq2, I have subscribed ubuntu-release. We have modifications in our
PPA that utilize this patch to accountsservice. If the patch to
accountsservice is not merged in Ubuntu's version, our version will be
overridden when there is another accountsservice release.
Since this is a feature that is
ximion, as I already said here:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/comments/11
Encrypted home cannot go upstream, as adduser --encrypt-home is only
implemented on Ubuntu.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
Simon, it is critical for our efforts that the accountsservice patches
make it upstream before 17.10. Can we focus only on those, leaving
inotial setup and control center patches for 18.04?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
Yes, I believe this still affects 16.04. I applied the patch on machines
that System76 ships, but it is not upstream. It is the same patch as was
applied to 17.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
seb128: I subscribed ubuntu-sponsors. Is there anything else I can do?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1699216
Title:
Encrypted home support
Would anyone like to comment on my patches?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
https://bugs.launchpad.net/bugs/1699216
Title:
Encrypted home support
Status in accountsservice
I made a mistake in the accountsservice patch. Here is an updated
version.
** Patch added: "encrypt_home.patch"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1699216/+attachment/4899663/+files/encrypt_home.patch
--
You received this bug notification because you are a
Ok, here are new patches that do not break the current API.
It is a little bit messier in accountsservice due to this.
** Patch added: "accountsservice_encrypt_home.patch"
** Patch added: "gnome-initial-setup_encrypt_home.patch"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4899524/+files/gnome-initial-setup_encrypt_home.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Patch added: "gnome-control-center_encrypt_home.patch"
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1699216/+attachment/4899523/+files/gnome-control-center_encrypt_home.patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
ximion, I am working on a more compatible patch, one that does not break
libaccountsservice API. As for going upstream, I would like to go into
Ubuntu first, as --encrypt-home is not implemented in other distros
right now.
--
You received this bug notification because you are a member of Ubuntu
If you would like to test these patches in action, you can add this PPA
and update:
https://launchpad.net/~system76/+archive/ubuntu/pop/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to accountsservice in Ubuntu.
Attached find a proposed patch for this, allowing for two more patches
to gnome-initial-setup and gnome-control-center that add encrypted home
support when creating users. I have tested it on Ubuntu GNOME 17.04, and
it works.
** Patch added: "encrypted_home.patch"
Attached you will find a patch for encrypted home support in gnome-
control-center. This patch will add a switch for "Encrypted Home
Folder", and send the correct value to CreateUser in accountsservice.
** Patch added: "encrypt_home.patch"
Attached you will find a patch for encrypted home support in gnome-
initial-setup. This patch will add a switch for "Encrypted Home Folder",
and send the correct value to CreateUser in accountsservice.
** Patch added: "encrypt_home.patch"
Public bug reported:
In the CreateUser D-bus call, allow the home directory of the new user
to be encrypted.
** Affects: accountsservice (Ubuntu)
Importance: Undecided
Status: Confirmed
** Affects: gnome-control-center (Ubuntu)
Importance: Undecided
Status: Confirmed
Would it be acceptable to have a patch to `wpa` to add `IgnoreOnIsolate`
for the time being? If we hold it in the Ubuntu debian/patches then we
can wait for a better solution to be done upstream.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
Here is how I have been working around this bug for System76's machines:
https://launchpadlibrarian.net/303137969/wpa_2.4-0ubuntu6_2.4-0ubuntu7~system76~1.diff.gz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
Yes, I am. I just need to know what is permissible - we can add
IgnoreOnIsolate in a ubuntu patch but it seems like the source of the
issue is in network manager - it should detect that wpa supplicant is
not running and restart it dynamically.
--
You received this bug notification because you
By the way, it is possible to trigger the bug running on your own
system. All you have to do is run `sudo systemctl isolate
default.target` while connected to WiFi
Bluetooth may also go down.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which
This is caused by wpa_supplicant being killed by systemctl isolate in
oem-config-firstboot
A potential fix is to add IgnoreOnIsolate=true to [Unit] in
wpa_supplicant.service
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
54 matches
Mail list logo
