[Touch-packages] [Bug 1869655] Re: Boot animations start too late to be useful

> No longer in progress. You can get to 100% fixed by adding kernel parameter 'plymouth.use-simpledrm' but I'm not totally sure that's something everyone will want. The main reasons that can be problematic are rotation right? I wonder if the right way to go about it is a heuristic within

[Touch-packages] [Bug 2061708] Re: Yubikey stopped working after noble upgrade

According to the upstream bug, this appears to be a new intended behavior with newer gnupg2: https://dev.gnupg.org/T6871 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu.

[Touch-packages] [Bug 2061708] Re: Yubikey stopped working after noble upgrade

I managed to get it working as a user by manually starting pcscd.service and with the following to force scdaemon to use it. # cat ~/.gnupg/scdaemon.conf card-timeout 5 disable-ccid To me this seems to be a regression in behavior from 2.2.27-3ubuntu2.1 to 2.4.4-2ubuntu17. ** Bug watch added:

[Touch-packages] [Bug 2061708] [NEW] Yubikey stopped working after noble upgrade

Public bug reported: In Ubuntu 22.04 I used by GPG key stored on a Yubikey smart card, but since upgrading to Noble I get the following trying to access it. $ gpg --card-status gpg: selecting card failed: No such device gpg: OpenPGP card not available: No such device If I run this as root it

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

Can you double check the framebuffer FB related conf options in your kconfig against those in Fedora? -- 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/1970069 Title:

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

The backend is a framebuffer driver. For example efifb which uses the framebuffer set up by GOP in pre-boot. If there are framebuffer drivers in tinydrm then maybe they matter for those architectures. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

Even if FRAMEBUFFER=Y wasn't added, I think that a change to stop adding all those other drm drivers makes a lot of sense. No use doubling the initrd size for the LUKS case. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

AFAICT; these initramfs-tools package changes would cover it: * hooks/framebuffer can be totally removed. * scripts/init-top/framebuffer should probably stay * conf/initramfs.conf needs FRAMEBUFFER=y added to it -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

Plymouth only gets added to the initrd when LUKS is enabled or you mark another reason for needing the framebuffer. So the suggestion I have from comment #49 is to mark needing the framebuffer by default, and then stop including any DRM modules because simpledrm is built into the kernel. -- You

[Touch-packages] [Bug 2053207] Re: glib requires gobject-introspection >= 1.78.1-13

It's marked failed to upload on all architectures right now: INFOgir1.2-glib-2.0-dev_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 INFOgir1.2-glib-2.0_1.78.1-15_amd64.deb: Version older than that in the archive. 1.78.1-15 <= 2.79.1-1 I guess that

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

With your change Fedora and Ubuntu are now behaving relatively similarly. * Both have a deficiency where the handoff from BGRT logo to Plymouth is doing a modeset for some reason. * Due to something in Fedora's GRUB it's a little clearer when GRUB starts. Here's various artifacts if you want

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

Ah I did have GRUB_TIMEOUT set; I hadn't expected that caused a black screen. Moving that to zero certainly helps. It's a lot better; but still not perfect. Let me get things back to as close as possible to stock and capture logs and a videos to compare with Ubuntu and Fedora with this exact

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

I tested it on Noble with a hand built kernel and it at least does what you planned (don't see any console messages), but also I'm not seeing the OEM vendor logo stick all the way through. There's a really long time of a black screen. Not sure if this is because it was an upstream kernel and

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

You could detect both parameters to avoid that corner case. Alternatively this is something I feel simpledrm will help you avoid hitting too. Otherwise it sounds good to me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

Yeah; so try forcing plymouth to the Ubuntu initrd like this: echo "FRAMEBUFFER=y" | sudo tee /etc/initramfs-tools/conf.d/splash Then if you rebuild the initrd you'll end up with plymouth in it. This unfortunately DOUBLES the initramfs size; but it's because it puts all the drm modules in

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

Something "big" I notice different is that by default Ubuntu doesn't put plymouth in the initramfs but Fedora does. Maybe plymouthd really isn't running at the time systemd-fsckd is running. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

> I don't really know if Fedora does that better or they just failed to notice the bug. I have Fedora 39 and Ubuntu both set up on a Z13 and Plymouth comes up in Fedora with simpledrm; never see the console. That's why I was thinking something might be missing and worth looking at. * Fedora

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

Have you already looked at everything Fedora is doing in this area? They already have simpledrm; but from what you described I would have thought they should still lose the fbcon race. Is it just that they don't have systemd-fsckd patch? I would think they still end up showing ERR/WARN kernel

[Touch-packages] [Bug 1970069] Re: Annoying boot messages interfering with splash screen

> But the feature would still be gated on the "splash" kernel parameter which is Plymouth-specific and may cause pushback from kernel developers. If the patch is the way you go another idea for you is to use the "quiet" keyword to key off instead for this behavior which is already used by the

[Touch-packages] [Bug 2046646] Re: package fwupd 1.7.9-1~22.04.3 failed to install/upgrade: installed fwupd package post-installation script subprocess returned error exit status 127

** Package changed: fwupd (Ubuntu) => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2046646 Title: package fwupd 1.7.9-1~22.04.3 failed

[Touch-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

This is the same issue as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573 Here is a commit that fixes the issue by changing default pre-emption policy since the kernel can't know about your mesa version.

[Touch-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

I've published a PPA here: https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages This has builds both for 22.04 (Jammy) and 23.04 (Lunar). Please upgrade to that, drop the module parameter and see if things improve. # sudo add-apt-repository ppa:superm1/gitlab2971 # sudo apt

[Touch-packages] [Bug 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Package changed: mutter (Ubuntu) => mesa (Ubuntu) ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New

[Touch-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception

From the upstream bug this is caused by PSR, so it's not a mesa issue. ** No longer affects: mesa (Ubuntu) ** No longer affects: mesa (Ubuntu Jammy) ** No longer affects: mesa (Ubuntu Lunar) ** No longer affects: mesa (Ubuntu Mantic) ** No longer affects: mesa (Ubuntu Noble) -- You received

[Touch-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception

It's unclear if this is a BIOS, mesa or kernel bug at this time, but it's certainly not an Xorg bug as it was reproduced in Wayland. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954

[Touch-packages] [Bug 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception

** Package changed: xorg (Ubuntu) => mesa (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception Status in

[Touch-packages] [Bug 2039868] Re: amdgpu reset during usage of firefox

6.5.6 has the fix for preemption issue, it should get fixed when stable updates come in Mantic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2039868 Title: amdgpu reset

[Touch-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault

Ok in this case can you please open an upstream mesa bug? ** Changed in: mesa (Ubuntu) Status: Fix Released => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu.

[Touch-packages] [Bug 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen

Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed right after you reported this issue. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you

[Touch-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault

I'd say that's very likely. That mesa upgrade just landed in the archive a few days ago and the trace you reported looks more like how a mesa bug manifests. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- You

[Touch-packages] [Bug 2037641] Re: amdgpu: [gfxhub0] no-retry page fault

Are you up to date on the current version of mesa in 23.10? 23.2.1-1ubuntu2? ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu.

[Touch-packages] [Bug 1987792] Re: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers

** Changed in: mesa (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1987792 Title: Totem and VLC crash when playing dvd with VAAPI

[Touch-packages] [Bug 2016435] Re: amdgpu driver randomly resets

Random resets are "typically" triggered by mesa or application bugs. Can you still trigger them in the latest mantic (which has a more up to date mesa and kernel)? ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Invalid ** Changed in: mesa (Ubuntu) Status: New =>

[Touch-packages] [Bug 1094959] Re: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 failed to install/upgrade

> NonfreeKernelModules: fglrx Nothing that will be done in mesa for an issue with fglrx anyway these days. ** Changed in: mesa (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to

[Touch-packages] [Bug 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen

In this case the kernel is the "messenger" for the page fault. This is more likely to be a mesa or application issue than a kernel issue. Can you please raise a ticket to the upstream mesa bug tracker? https://gitlab.freedesktop.org/mesa/mesa/ ** Also affects: mesa (Ubuntu) Importance:

[Touch-packages] [Bug 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second

** Also affects: mesa (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2

[Touch-packages] [Bug 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second

I believe this likely needs the VCN fixes from https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 ** Also affects: mesa (Ubuntu) Importance: Undecided

[Touch-packages] [Bug 2020604] Re: After Mesa upgrades, Chrome won't show graphics

I believe the same thing can likely happen if llvm updates but mesa stays the same. Can you embed both into the string? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604

[Touch-packages] [Bug 2020604] Re: After mesa upgrades, Chrome won't show graphics

It seems a way that this may be avoided is for GL_RENDERER string to always be updated when mesa updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2020604 Title: After

[Touch-packages] [Bug 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4

** 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 Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/2017142

[Touch-packages] [Bug 2017142] [NEW] [jammy] VA-API doesn't work on DCN 3.1.4

Public bug reported: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API *

[Touch-packages] [Bug 2008699] Re: fwupd-refresh.service always fails after hibernate

> Where? /usr/lib/systemd/system/fwupd-refresh.service only has After=network.target. Perhaps that'd be the fix. Ah... this was fixed in upstream already in 1.8.5 release. https://github.com/fwupd/fwupd/commit/fe5d93f7d2712f3b708e562a5f7e9be897e04d1d ** Also affects: systemd (Ubuntu Kinetic)

[Touch-packages] [Bug 2008699] Re: fwupd-refresh.service always fails after hibernate

BTW - fwupd already uses network-online.target for this unit. One could probably argue this is a systemd bug. > [Unit] > Description=Refresh fwupd metadata and update motd > Documentation=man:fwupdmgr(1) > After=network-online.target > > [Service] > Type=oneshot > CacheDirectory=fwupdmgr >

[Touch-packages] [Bug 1991761] Re: Backport packages for 22.04.2 HWE stack

At least from AMD's tests, backported mesa stack is working properly with RDNA3. Adjusting tag accordingly. ** 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

[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon

YC is in the process of doing an SRU for a bunch of other bugs in fwupd and the fix should come in that same SRU I expect. ** Changed in: fwupd (Ubuntu Jammy) Assignee: (unassigned) => Yosu (yc) ** Changed in: fwupd (Ubuntu Jammy) Assignee: Yosu (yc) => Yuan-Chen Cheng (ycheng-twn) --

[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon

** Changed in: fwupd (Ubuntu Impish) Status: Confirmed => Won't Fix -- 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/1969976 Title: DynamicUser=1 doesn't get along

[Touch-packages] [Bug 1981109] Re: server image pulls in ModemManager via fwupd, consumes 25MiB RAM in every container

One possible solution is to split the fwupd package along it's possible plugins into multiple packages. However I tend to agree that it has no use in a cloud or container seed. I also agree libmm-glib0 shouldn't recommend modem manager. ** Changed in: fwupd (Ubuntu) Status: New =>

[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon

** Changed in: fwupd (Ubuntu) Status: New => Fix Committed -- 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/1969976 Title: DynamicUser=1 doesn't get along with

[Touch-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

Just to correct a few of the targets on this issue. * The reverts mentioned in #30 need to be pulled into linux-firmware for focal. * They're already included in jammy. ** Changed in: amd Status: New => Fix Released ** No longer affects: mesa (Ubuntu) ** Also affects: linux-firmware

[Touch-packages] [Bug 1969976] Re: DynamicUser=1 doesn't get along with services that need dbus-daemon

OK, so upstream here is what we have done (pretty much your suggested W/A). main: https://github.com/fwupd/fwupd/commit/7b0d6bc6e03381544e3fb1836c177d492c9d0bbc https://github.com/fwupd/fwupd/commit/e90b04d7319874db36c06245ab07858589ce8bc8

[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

> The comment at https://github.com/fwupd/fwupd/issues/3037#issuecomment-1100816992 suggests that disabling the DynamicUser= setting makes the service work again. Maybe that's worth a try, in order to get both problems solved? (i.e. shipping an override config for fwupd) > $cat

[Touch-packages] [Bug 1969976] [NEW] DynamicUser=1 doesn't get along with services that need dbus-daemon

Public bug reported: Updating to systemd 245.4-4ubuntu3.16 has caused a regression in Ubuntu 20.04, that fwupd-refresh.service always fails to run. This has been root caused down to the changes in https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1871538 Unfortunately this is an

[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

> https://git.launchpad.net/~ubuntu-core- dev/ubuntu/+source/systemd/commit/?id=e3aacfa26e3fc6df369e6f28e740389ae0020907 This appears to have caused a regression in fwupd in Ubuntu 20.04 with details at https://github.com/fwupd/fwupd/issues/3037 fwupd-refresh.service uses DynamicUser and now

[Touch-packages] [Bug 1960768] Re: fwupd crash on stop

> If fwupd is being backported to previous releases of Ubuntu it seems like libgusb would also need to be backported. Actually the bug was introduced in libgusb 0.3.8, fixed in libgusb 0.3.9. If older releases have older than 0.3.8 they shouldn't need libgusb backport. See comment #3. -- You

[Touch-packages] [Bug 1960768] Re: fwupd crash on stop

** Changed in: fwupd (Ubuntu) Status: Confirmed => Invalid ** Changed in: libusb (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu.

[Touch-packages] [Bug 1960768] Re: fwupd crash on stop

Ah probably was caused by https://github.com/hughsie/libgusb/commit/4b52b0cd27fdadcb29b4518cff293c1c76b872a9 in 0.3.8 and fixed by https://github.com/hughsie/libgusb/commit/24934619a2ad3467b98142dfab2039985afc970d in that case. ** Also affects: libgusb (Ubuntu) Importance: Undecided

[Touch-packages] [Bug 847065] Re: libprotobuf-lite link not created

** Package changed: protobuf-c (Ubuntu) => protobuf (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to protobuf in Ubuntu. https://bugs.launchpad.net/bugs/847065 Title: libprotobuf-lite link not created Status in

[Touch-packages] [Bug 1561643] Re: initramfs-tools ignores the FRAMEBUFFER option

** No longer affects: initramfs-tools (Ubuntu Xenial) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1561643 Title: initramfs-tools ignores the FRAMEBUFFER option

[Touch-packages] [Bug 1945227] Re: drm/amdgpu: Add support for Yellow Carp

Verified on YC with the following combination all from -proposed: # dpkg -l | grep "linux-firmware\|linux-image-5.14.0-1005-oem\|21.0.3-0ubuntu0." ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the EGL API -- Mesa vendor

[Touch-packages] [Bug 1945227] Re: drm/amdgpu: Add support for Yellow Carp

With manually placing firmware in /lib/firmware (since SRU not started for that) and using 5.14 kernel confirmed that mesa looks good. Since we don't have linux-firmware SRU package yet and they are combined on this bug report I will not add "verification-done-focal". # glxinfo | grep "OpenGL

[Touch-packages] [Bug 1835660] Re: initramfs unpacking failed

#134: @xnox, have you re-sent it? It looks like https://lkml.org/lkml/2021/1/14/1091 got no feedback. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title:

[Touch-packages] [Bug 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"

Here's a PPA build with the mesa fix Alex mentioned backported: https://launchpad.net/~superm1/+archive/ubuntu/lp1928393 If you can follow the directions to add that PPA and upgrade to that mesa package you can see if that indeed fixes it. ** Also affects: mesa (Ubuntu) Importance: Undecided

[Touch-packages] [Bug 1865055] [NEW] package libip4tc-dev 1.8.3-2ubuntu5 failed to install/upgrade: trying to overwrite '/usr/include/libiptc/ipt_kernel_headers.h', which is also in package libiptc-de

Public bug reported: Running standard upgrades in focal. Unpacking libip4tc-dev:amd64 (1.8.4-3ubuntu1) over (1.8.3-2ubuntu5) ... dpkg: error processing archive /tmp/apt-dpkg-install-vyGukq/07-libip4tc-dev_1.8.4-3ubuntu1_amd64.deb (--unpack): trying to overwrite

[Touch-packages] [Bug 1861556] Re: g-ir-scanner doesn't work

Upgrading python3-minimal to 3.8.0-3 which has been stuck in proposed fixes this issue, but gobject-introspection doesn't reflect a relationship upon this. # apt show gobject-introspection |grep Dep Depends: libc6 (>= 2.29), libffi7 (>= 3.3~20180313), libgirepository-1.0-1 (= 1.62.0-4ubuntu1),

[Touch-packages] [Bug 1861556] Re: g-ir-scanner doesn't work

It appears to me to be happening because gobject-introspection only ships a python file for python3.8 not python3.7 which is the default in focal. $ python3.7 /usr/bin/g-ir-scanner Traceback (most recent call last): File "/usr/bin/g-ir-scanner", line 99, in from giscanner.scannermain

[Touch-packages] [Bug 1861556] [NEW] g-ir-scanner doesn't work

Public bug reported: Running g-ir-scanner doesn't work anymore after a recent upgrade with a fully up to date focal: Traceback (most recent call last): File "/usr/bin/g-ir-scanner", line 99, in from giscanner.scannermain import scanner_main File

[Touch-packages] [Bug 1814460] Re: systemd-cryptsetup fails during initrd stage of boot

I don't think that anyone should invest effort in sorting dracut unless Ubuntu is actually going to be move to dracut. Clevis 12 has initramfs support, so once that gets uploaded to Debian and syncs from Debian to Ubuntu, you should be able to use that with 20.04 and later. ** Changed in: dracut

[Touch-packages] [Bug 1832108] Re: unmkinitramfs fails with lz4 compressed initrds

@xnox, Could you SRU this to bionic too? It becomes problematic to try to probe at an initramfs file from eoan when you're in bionic otherwise. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.

[Touch-packages] [Bug 1815509] Re: Shutdown hung by firmware update daemon

Thanks for the comment. If it's gone with disco I'll close this. Please anyone who encounters it, turn on fwupd verbose logging so we can figure out what is happening if it's fwupd. It's also possible this is the last visible message but it's some other script running at this time. This will be

[Touch-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0

** Project changed: snappy-hwe-snaps => linux (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1822633 Title: Pairing failure with BLE 4.0 Status in bluez package

[Touch-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0

** Also affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1822633 Title: Pairing failure with BLE 4.0

[Touch-packages] [Bug 1815509] Re: Shutdown hung by firmware update daemon

If it's intermittent at least what evidence points to fwupd? Is it the last thing seen in a log somewhere? Ideally please leave verbose logging turned on in fwipd systemd unit and leave it enabled. When this repros again we can see the logs. -- You received this bug notification because you are

[Touch-packages] [Bug 1815509] Re: Shutdown hung by firmware update daemon

Can you please add the requested stuff from comment 2? -- 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/1815509 Title: Shutdown hung by firmware update daemon Status in

[Touch-packages] [Bug 1815509] Re: Shutdown hung by firmware update daemon

** Changed in: fwupd (Ubuntu) Status: New => Incomplete -- 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/1815509 Title: Shutdown hung by firmware update daemon

[Touch-packages] [Bug 1815509] Re: Shutdown hung by firmware update daemon

Can you please do the following: 1) confirm that masking the service (ur preventing it from starting) fixes the problem? 2) modify the service to start in verbose mode (add --verbose to launch flag) 3) share journal output from an attempt with verbose mode enabled. -- You received this bug

[Touch-packages] [Bug 1811152] Re: Locally installed services can't add dbus configuration

I filed the issue upstream as well. https://gitlab.freedesktop.org/dbus/dbus/issues/253 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1811152 Title: Locally installed

[Touch-packages] [Bug 1811152] Re: Locally installed services can't add dbus configuration

I did not check upstream yet no, thanks for checking. I'll report it upsteam as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1811152 Title: Locally installed

[Touch-packages] [Bug 1811152] [NEW] Locally installed services can't add dbus configuration

Public bug reported: A report was received in upstream fwupd about how the daemon wasn't able to start after the following commands: # meson build # ninja -C build # ninja -C build install This placed everything in /usr/local by default. It also created an

[Touch-packages] [Bug 1631002] Re: fwupd crashed with SIGSEGV in malloc_consolidate()

** Changed in: fwupd (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1631002 Title: fwupd crashed with SIGSEGV in

[Touch-packages] [Bug 1756006] Re: FFe: Support suspend-then-hibernate

Try d-feet as root. I think I recalled seeing this too. -- 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-then-hibernate Status in

[Touch-packages] [Bug 1756006] Re: FFe: Support suspend-then-hibernate

When I did those PR upstream I did it with a swapfile actually on Ubuntu. The key comes down to how initramfs-tools hands off the offsets. It's kinda a jumbled mess though. I started a discussion here https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890950 but it got stalled and I got busy

Re: [Touch-packages] [Bug 1756006] Re: FFe: Support suspend-then-hibernate

s bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1756006 > > Title: > FFe: Support suspend-then-hibernate > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/

[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

On an Dell XPS 9360 with a 3200x1800 display it also defaults to 200% and I reliably reproduce this bug with the 18.04 final image. I can confirm setting the scaling to 100% in the live session resolved the crash. -- You received this bug notification because you are a member of Ubuntu Touch

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

@xnox in order to coordinate the systemd upload in case you have anything in flight, here's a debdiff: ** Patch added: "backported fix from upstream" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1760106/+attachment/5110809/+files/systemd-offsets.debdiff -- You received this bug

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

@Andy, The systemd changes are approved, just waiting for CI to pass and they'll be merged. -- 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/1760106 Title: FFe: Enable

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

regarding klibc upstream is MIA for a long time. There are patches that have been posted before mine, but no activity since: commit 4d19974d7020488f63651244e1f9f51727c3f66c Author: H. Peter Anvin Date: Mon Feb 1 13:26:01 2016 -0800 [klibc] fwrite: fix typo in comment

[Touch-packages] [Bug 1756006] Re: FFe: Support suspend-to-hibernate

The rename is done upstream, it's now suspend-then-hibernate. I'm uploading systemd with these patches. As for G-S-D, I've adjusted it for the rename too but it's still waiting to be merged. ** Changed in: systemd (Ubuntu) Status: New => Fix Committed ** Summary changed: - FFe: Support

[Touch-packages] [Bug 1760106] Re: FFe: Enable configuring resume offset via sysfs

** Summary changed: - Enable configuring resume offset via sysfs + FFe: Enable configuring resume offset via sysfs -- 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/1760106

[Touch-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

** Also affects: klibc (Ubuntu) Importance: Undecided Status: New ** Description changed: In 4.17 a new attribute is introduced to configure the hibernation resume offset. Since Ubuntu enables a swapfile by default this attribute is important to be able to make hibernation work

[Touch-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1760106 Title: Enable configuring resume offset via

[Touch-packages] [Bug 1760106] Re: Enable configuring resume offset via sysfs

** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1760106 Title: Enable configuring resume

Re: [Touch-packages] [Bug 1756006] Re: FFe: Support suspend-to-hibernate

Gsd is pushing for the name change in systemd, so I'm going to get that upstreamed before bringing this into Ubuntu. (Suspend to hibernate to suspend then hibernate). In terms of UI where would it Land? I figure it should be a policy setting on systems that ship with it, but you're probably right

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

Dimitri, I've performed your tasks and can confirm with that PPA applied that it works properly. I've emailed you the packet captures privately to your @ubuntu.com address. I also do note the following in my journal log: Mar 26 12:18:43 test-XPS-13-9350 systemd-resolved[507]: DVE-2018-0001

[Touch-packages] [Bug 1756006] Re: FFe: Support suspend-to-hibernate

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

[Touch-packages] [Bug 1756006] [NEW] FFe: Support suspend-to-hibernate

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

@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

[Touch-packages] [Bug 1644975] Re: Resume from disk (swapfile) fails

** 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)

[Touch-packages] [Bug 1644975] Re: Resume from disk (swapfile) fails

: 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. https://bugs.launchp

[Touch-packages] [Bug 1724604] Re: umockdev 0.9.4-1 causes test suite failures in fwupd

** 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

[Touch-packages] [Bug 1724604] Re: umockdev 0.9.4-1 causes test suite failures in fwupd

** 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

  1   2   >