April 2024 - openSUSE Bugs - openSUSE Mailing Lists

[Bug 1218422] New: Can't build hyprland plugins due to improper header locations
by bugzilla_noreply＠suse.com 11 May '24

11 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1218422 Bug ID: 1218422 Summary: Can't build hyprland plugins due to improper header locations Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Development Assignee: screening-team-bugs(a)suse.de Reporter: johndoe1352460(a)outlook.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- I cannot build the plugins for Hyprland due to the improper locations of headers. When building hyprbars for hyprland it expects <wlr/util/transform.h> but the full path of the file is /usr/include/hyprland/wlroots. I'm guessing it expects it to be /usr/include/hyprland/wlr with the pkgconfig parameter inclduing -I/usr/include/hyprland What I did to fix this issue is create a symlink /usr/include/hyprland/wlr that points to /usr/include/hyprland/wlroots and add -I${includedir}/hyprland to the cflags in /usr/share/pkgconfig/hyprland.pc After I do that the hyprbars plugin builds just fine. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222202] New: Ignition config always causes initramfs sosreport to be generated.
by bugzilla_noreply＠suse.com 10 May '24

10 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222202 Bug ID: 1222202 Summary: Ignition config always causes initramfs sosreport to be generated. Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: MicroOS Assignee: forgotten_u0-bnvADNc(a)user.net Reporter: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 873966 --> https://bugzilla.suse.com/attachment.cgi?id=873966&action=edit sosreport The following ignition contents will always crash on first boot: { "ignition": { "version": "3.2.0" }, "passwd": { "users": [ { "name": "root", "sshAuthorizedKeys": [ "ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBCiRcelfygo9beT4sZS8qXsyZg0zgBl7bBsfk5w3k8RubhkCmC7yCYu+4JPGgyiL5gP3brx6u+veXQtUf62X8wA= william@piv" ] }, { "name": "root" } ] }, "storage": { "files": [ { "path": "/etc/hostname", "mode": 420, "overwrite": true, "contents": { "source": "data:,hostname.domain.local" } } ] } } Install CLI virt-install --connect=qemu:///system -n microtest.suse.firstyear.id.au --import --boot uefi --osinfo opensusetumbleweed --virt-type kvm --hvm --machine q35 --cpu host-passthrough --serial pty --console pty,target_type=virtio --autoconsole text --network=bridge=net_20,model=virtio --rng /dev/urandom --tpm backend.type=emulator,backend.version=2.0,model=tpm-tis --vcpu 2 --memory 2048 --security type=dynamic --sysinfo type=fwcfg,entry0.name=opt/com.coreos/config,entry0.file=/var/lib/libvirt/qemu/ignition/default.ign --disk path=/mnt/libvirt/nvme/microtest.suse.firstyear.id.au.qcow2,bus=virtio,cache=none,sparse=no -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1217488] New: pynfs CID* tests fails: OP_SETCLIENTID should return NFS4_OK, instead got NFS4ERR_DELAY
by bugzilla_noreply＠suse.com 10 May '24

10 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217488 Bug ID: 1217488 Summary: pynfs CID* tests fails: OP_SETCLIENTID should return NFS4_OK, instead got NFS4ERR_DELAY Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Filesystems Assignee: nfbrown(a)suse.com Reporter: petr.vorel(a)suse.com QA Contact: petr.vorel(a)suse.com Target Milestone: --- Found By: --- Blocker: --- Although we start due #1217128 testing via cdmackay/pynfs.git, which has fix for "nfs4lib.BadCompoundRes: operation OP_SETCLIENTID should return NFS4_OK [1], instead got NFS4ERR_DELAY", we still get 9 tests failing with this error on Tumbleweed. Any idea what could be wrong now? O I can ask Calum Mackay on linux-nfs if you're busy with more important stuff. [1] https://git.linux-nfs.org/?p=cdmackay/pynfs.git;a=commit;h=0d4d3fd0bb7a6386… -- You are receiving this mail because: You are on the CC list for the bug.

1 6

[Bug 1220524] New: Files in virtualbox shared folder (on the guest) show wrong timestamp
by bugzilla_noreply＠suse.com 09 May '24

09 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1220524 Bug ID: 1220524 Summary: Files in virtualbox shared folder (on the guest) show wrong timestamp Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs(a)suse.de Reporter: suse.junky(a)t-online.de QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- On my openSUSE Tumbleweed system (bare metal) Operating System: openSUSE Tumbleweed 20240225 KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.12 Kernel Version: 6.7.6-1-default (64-bit) Graphics Platform: X11 I use virtualbox # zypper se -si virtual* Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------------------------+---------+-----------------------+--------+------------------ i | virtualbox | package | 7.0.14-3.1 | x86_64 | (System Packages) i+ | virtualbox-kmp-default | package | 7.0.14_k6.7.6_1-3.2 | x86_64 | (System Packages) i+ | virtualbox-qt | package | 7.0.14-3.1 | x86_64 | (System Packages) # One guest is an openSUSE Tumbleweed 20240225 system with # zypper se -si virtualbox* Loading repository data... Reading installed packages... S | Name | Type | Version | Arch | Repository ---+------------------------+---------+---------------------+--------+------------------ i+ | virtualbox-guest-tools | package | 7.0.14-3.1 | x86_64 | (System Packages) i+ | virtualbox-kmp-default | package | 7.0.14_k6.7.6_1-3.2 | x86_64 | (System Packages) # The host shares a directory (/mnt/Lokal/VM_share) with the guest. On the host system I have (in my home directory) a file > ls -la *.jpg -rw-r--r-- 1 A users 40749 Mar 3 2023 Opensuse_beer_label.jpg when I copy this file to the shared directory > cp -a Opensuse_beer_label.jpg /mnt/Lokal/VM_share/ everything looks fine (on the host) > ls -la /mnt/Lokal/VM_share/ total 64 drwxr-xr-x 3 A users 4096 Feb 27 09:51 . drwxr-xr-x 7 root root 4096 Jan 3 2022 .. -rw-r--r-- 1 A users 40749 Mar 3 2023 Opensuse_beer_label.jpg > but on the guest system I see in the shared folder > ls -la total 64 drwxrwx--- 1 root vboxsf 4096 Jan 1 1970 . dr-xr-xr-x 5 root root 4096 Feb 27 09:40 .. -rwxrwx--- 1 root vboxsf 40749 Feb 27 09:44 Opensuse_beer_label.jpg > The timestamps in the share of the VM don’t make sense to me. This happens to all files copied to the share. Even when I copy files in the guest to the share their timestamps are changed (in the share) to the current date . However when I look at those files on the host they do have the correct date; i.e. the date of the original file in the guest. On MS Windows 11 (bare metal) with virtualbox 7.0.14 and openSUSE Tumbleweed 20240225 as guest I see the same behaviour. Kubuntu (as guest) does not show this behaviour although it uses VBoxGuestAdditions_7.0.14 as well. I discussed this already here: https://forums.opensuse.org/t/files-in-the-virtualbox-share-show-wrong-time… and a third user could very this behaviour in its setup as well. -- You are receiving this mail because: You are on the CC list for the bug.

1 7

[Bug 1217824] New: longterm kernel: figure out how to build KMPs
by bugzilla_noreply＠suse.com 09 May '24

09 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217824 Bug ID: 1217824 Summary: longterm kernel: figure out how to build KMPs Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Security Assignee: rfrohl(a)suse.com Reporter: rfrohl(a)suse.com QA Contact: qa-bugs(a)suse.de CC: tiwai(a)suse.com Target Milestone: --- Found By: --- Blocker: --- One of the major open questions, before introducing the longterm kernel to Factory, is how KPMs can be build. This issue is supposed to server as a reminder, that this likely blocks the addition to Factory until it is resolved. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1216042] New: Kernels fail to build in Kernel:stable:Backport
by bugzilla_noreply＠suse.com 09 May '24

09 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1216042 Bug ID: 1216042 Summary: Kernels fail to build in Kernel:stable:Backport Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: manfred.h(a)gmx.net QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The recently updated binutils in openSUSE_Leap_15.4 generate new DT_ tags which dwarves does not know about: [ 1122s] Unsupported DW_TAG_unspecified_type(0x3b) [ 1122s] Encountered error while encoding BTF. osc branch --nodevelproject openSUSE:Factory dwarves Kernel:stable:Backport would probably solve this issue. -- You are receiving this mail because: You are on the CC list for the bug.

1 4

[Bug 1221869] New: error after installing package "powdertoy"
by bugzilla_noreply＠suse.com 09 May '24

09 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1221869 Bug ID: 1221869 Summary: error after installing package "powdertoy" Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: comes(a)naic.edu QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The packages powdertoy once installed causes problem. The content of a file that it installs is not valid. The file in question is: /usr/share/mime/packages/powdertoy-save.xml and the issue is due to the following extract: <mime-type type="application/vnd.powdertoy.save"> <comment>Powder Toy save</comment> <glob pattern=*.cps/> <glob pattern=*.stm/> </mime-type>" Note the single double quote at the end of </mime-type> and *.cps *.stm not being surrounded by quotes When installed this error is printed: # /usr/share/mime/packages/powdertoy-save.xml:5: parser error : AttValue: " or ' expected # <glob pattern=*.cps/> # ^ # /usr/share/mime/packages/powdertoy-save.xml:5: parser error : attributes construct error # <glob pattern=*.cps/> # ^ # /usr/share/mime/packages/powdertoy-save.xml:5: parser error : Couldn't find end of Start Tag glob line 5 # <glob pattern=*.cps/> # ^ # /usr/share/mime/packages/powdertoy-save.xml:6: parser error : AttValue: " or ' expected # <glob pattern=*.stm/> # ^ # /usr/share/mime/packages/powdertoy-save.xml:6: parser error : attributes construct error # <glob pattern=*.stm/> # ^ # /usr/share/mime/packages/powdertoy-save.xml:6: parser error : Couldn't find end of Start Tag glob line 6 # <glob pattern=*.stm/> # ^ # Failed to parse '/usr/share/mime/packages/powdertoy-save.xml' Such error message is repeated also later when other packages are installed. There are two simple ways to fix the problem: 1) add a patch with a content like: --- The-Powder-Toy-93.3/resources/powdertoy-save.xml.ori 2024-03-05 21:16:59.051478441 -0400 +++ The-Powder-Toy-93.3/resources/powdertoy-save.xml 2024-03-05 21:17:15.887478820 -0400 @@ -2,7 +2,7 @@ <mime-info xmlns='http://www.freedesktop.org/standards/shared-mime-info'> <mime-type type="application/vnd.powdertoy.save"> <comment>Powder Toy save</comment> - <glob pattern=*.cps/> - <glob pattern=*.stm/> - </mime-type>" + <glob pattern="*.cps"/> + <glob pattern="*.stm"/> + </mime-type> </mime-info> or 2) add in the spec file: %prep %setup -q -n The-Powder-Toy-%{version} +sed -i '/\/mime-type/s@"@@;/pattern=/{s@=@="@;s@/@"/@}' resources/powdertoy-save.xml %build Which one to use is a matter of taste. The problem is present in Leap 15.5 and 15.6. The package in the games project is not affected as upstream has already fixed the issue in the more recent version present there. -- You are receiving this mail because: You are on the CC list for the bug.

1 1

[Bug 1217232] New: bees does not build on Leap 15.6
by bugzilla_noreply＠suse.com 09 May '24

09 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1217232 Bug ID: 1217232 Summary: bees does not build on Leap 15.6 Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.6 Hardware: Other OS: Other Status: NEW Severity: Major Priority: P5 - None Component: Other Assignee: screening-team-bugs(a)suse.de Reporter: lubos.kocman(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- Hello bees does not build on Leap 15.6 this should be fixed before Beta (Feb 2023) https://en.opensuse.org/openSUSE:Roadmap#Schedule_for_openSUSE_Leap_15.6 Build log from Leap 15.6 https://build.opensuse.org/package/live_build_log/openSUSE:Backports:SLE-15… [ 23s] /usr/include/linux/btrfs.h:667:43: error: flexible array member 'btrfs_ioctl_same_args::info' not at end of 'struct crucible::BtrfsExtentSame' [ 23s] struct btrfs_ioctl_same_extent_info info[]; [ 23s] ^ [ 23s] In file included from extentwalker.cc:5:0: [ 23s] ../include/crucible/fs.h:40:7: note: next member 'int crucible::BtrfsExtentSame::m_fd' declared here [ 23s] int m_fd; [ 23s] ^~~~ [ 23s] ../include/crucible/fs.h:34:9: note: in the definition of 'struct crucible::BtrfsExtentSame' [ 23s] struct BtrfsExtentSame : public btrfs_ioctl_same_args { [ 23s] ^~~~~~~~~~~~~~~ [ 23s] In file included from ../include/crucible/btrfs.h:17:0, [ 23s] from ../include/crucible/fs.h:11, [ 23s] from extentwalker.cc:5: [ 23s] /usr/include/linux/btrfs.h:687:12: error: flexible array member 'btrfs_data_container::val' not at end of 'struct crucible::BtrfsDataContainer' [ 23s] __u64 val[]; /* out */ [ 23s] ^ [ 23s] In file included from extentwalker.cc:5:0: [ 23s] ../include/crucible/fs.h:66:19: note: next member 'std::vector<unsigned char> crucible::BtrfsDataContainer::m_data' declared here [ 23s] vector<uint8_t> m_data; [ 23s] ^~~~~~ [ 23s] ../include/crucible/fs.h:56:9: note: in the definition of 'struct crucible::BtrfsDataContainer' [ 23s] struct BtrfsDataContainer : public btrfs_data_container { [ 23s] ^~~~~~~~~~~~~~~~~~ [ 23s] In file included from ../include/crucible/fs.h:14:0, [ 23s] from extentwalker.cc:5: [ 23s] /usr/include/linux/fiemap.h:37:34: error: flexible array member 'fiemap::fm_extents' not at end of 'struct crucible::Fiemap' [ 23s] struct fiemap_extent fm_extents[]; /* array of mapped extents (out) */ [ 23s] ^ [ 23s] In file included from extentwalker.cc:5:0: [ 23s] ../include/crucible/fs.h:155:24: note: next member 'std::vector<crucible::FiemapExtent> crucible::Fiemap::m_extents' declared here [ 23s] vector<FiemapExtent> m_extents; [ 23s] ^~~~~~~~~ [ 23s] ../include/crucible/fs.h:144:9: note: in the definition of 'struct crucible::Fiemap' [ 23s] struct Fiemap : public fiemap { [ 23s] ^~~~~~ [ 23s] make[1]: *** [Makefile:48: extentwalker.o] Error 1 [ 23s] make[1]: *** Waiting for unfinished jobs.... [ 23s] In file included from ../include/crucible/btrfs.h:17:0, [ 23s] from ../include/crucible/fs.h:11, [ 23s] from fs.cc:1: [ 23s] /usr/include/linux/btrfs.h:667:43: error: flexible array member 'btrfs_ioctl_same_args::info' not at end of 'struct crucible::BtrfsExtentSame' [ 23s] struct btrfs_ioctl_same_extent_info info[]; [ 23s] ^ [ 23s] In file included from fs.cc:1:0: [ 23s] ../include/crucible/fs.h:40:7: note: next member 'int crucible::BtrfsExtentSame::m_fd' declared here [ 23s] int m_fd; [ 23s] ^~~~ [ 23s] ../include/crucible/fs.h:34:9: note: in the definition of 'struct crucible::BtrfsExtentSame' [ 23s] struct BtrfsExtentSame : public btrfs_ioctl_same_args { [ 23s] ^~~~~~~~~~~~~~~ [ 23s] In file included from ../include/crucible/btrfs.h:17:0, [ 23s] from ../include/crucible/fs.h:11, [ 23s] from fs.cc:1: [ 23s] /usr/include/linux/btrfs.h:687:12: error: flexible array member 'btrfs_data_container::val' not at end of 'struct crucible::BtrfsDataContainer' [ 23s] __u64 val[]; /* out */ [ 23s] ^ [ 23s] In file included from fs.cc:1:0: [ 23s] ../include/crucible/fs.h:66:19: note: next member 'std::vector<unsigned char> crucible::BtrfsDataContainer::m_data' declared here [ 23s] vector<uint8_t> m_data; [ 23s] ^~~~~~ [ 23s] ../include/crucible/fs.h:56:9: note: in the definition of 'struct crucible::BtrfsDataContainer' [ 23s] struct BtrfsDataContainer : public btrfs_data_container { [ 23s] ^~~~~~~~~~~~~~~~~~ [ 23s] In file included from ../include/crucible/fs.h:14:0, [ 23s] from fs.cc:1: [ 23s] /usr/include/linux/fiemap.h:37:34: error: flexible array member 'fiemap::fm_extents' not at end of 'struct crucible::Fiemap' [ 23s] struct fiemap_extent fm_extents[]; /* array of mapped extents (out) */ [ 23s] ^ [ 23s] In file included from fs.cc:1:0: [ 23s] ../include/crucible/fs.h:155:24: note: next member 'std::vector<crucible::FiemapExtent> crucible::Fiemap::m_extents' declared here [ 23s] vector<FiemapExtent> m_extents; [ 23s] ^~~~~~~~~ [ 23s] ../include/crucible/fs.h:144:9: note: in the definition of 'struct crucible::Fiemap' [ 23s] struct Fiemap : public fiemap { [ 23s] ^~~~~~ [ 23s] make[1]: *** [Makefile:48: fs.o] Error 1 [ 24s] make[1]: Leaving directory '/home/abuild/rpmbuild/BUILD/bees-0.7/lib' [ 24s] make: *** [Makefile:34: lib] Error 2 [ 24s] error: Bad exit status from /var/tmp/rpm-tmp.rcToPR (%build) -- You are receiving this mail because: You are on the CC list for the bug.

1 2

[Bug 1222963] New: btrfs option --delete-qgroup unreliable
by bugzilla_noreply＠suse.com 09 May '24

09 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222963 Bug ID: 1222963 Summary: btrfs option --delete-qgroup unreliable Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem Assignee: screening-team-bugs(a)suse.de Reporter: aschnell(a)suse.com QA Contact: qa-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- The btrfs option --delete-qgroup when deleting subvolumes is unreliable: # btrfs subvolume create /test1/yls Create subvolume '/test1/yls' # btrfs quota rescan --wait /test1 quota rescan started # btrfs subvolume delete --delete-qgroup /test1/yls Delete subvolume 4804 (no-commit): '/test1/yls' WARNING: unable to delete qgroup 0/0: Device or resource busy Note: The qgroup in the warning is also wrong. -- You are receiving this mail because: You are on the CC list for the bug.

1 8

[Bug 1222412] New: [Tumbleweed20240405]chrome and slack crash on Haswell platform
by bugzilla_noreply＠suse.com 09 May '24

09 May '24

https://bugzilla.suse.com/show_bug.cgi?id=1222412 Bug ID: 1222412 Summary: [Tumbleweed20240405]chrome and slack crash on Haswell platform Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: X.Org Assignee: gfx-bugs(a)suse.de Reporter: dawei.pang(a)suse.com QA Contact: gfx-bugs(a)suse.de Target Milestone: --- Found By: --- Blocker: --- A desktop computer with Haswell platform CPU running KDE plasma6, two monitors connected to internal builtin Intel GPU, all are good on Tumbleweed March version. Mar 19 16:59:46 localhost.localdomain kwin_x11[2175]: OpenGL version string: 4.6 (Compatibility Profile) Mesa 23.3.6 Mar 19 16:59:46 localhost.localdomain kwin_x11[2175]: OpenGL shading language version string: 4.60 Mar 19 16:59:46 localhost.localdomain kwin_x11[2175]: Driver: Intel Mar 19 16:59:46 localhost.localdomain kwin_x11[2175]: GPU class: Haswell Mar 19 16:59:46 localhost.localdomain kwin_x11[2175]: OpenGL version: 4.6 Mar 19 16:59:46 localhost.localdomain kwin_x11[2175]: GLSL version: 4.60 Mar 19 16:59:46 localhost.localdomain kwin_x11[2175]: Mesa version: 23.3.6 Mar 19 16:59:46 localhost.localdomain kwin_x11[2175]: Requires strict binding: yes Mar 19 16:59:46 localhost.localdomain kwin_x11[2175]: Virtual Machine: no Mar 19 16:59:46 localhost.localdomain kwin_x11[2175]: Timer query support: yes When upgrading April version, slack and google chrome crash. Current Meas version is Mesa-24.0.3-372.1.x86_64 For google chrome: /opt/google/chrome/chrome [0408/095746.240039:WARNING:chrome_main_linux.cc(80)] Read channel stable from /opt/google/chrome/CHROME_VERSION_EXTRA MESA-INTEL: warning: Haswell Vulkan support is incomplete [4069:4069:0408/095746.825577:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139 MESA-INTEL: warning: Haswell Vulkan support is incomplete [4069:4069:0408/095747.256290:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139 MESA-INTEL: warning: Haswell Vulkan support is incomplete [4069:4089:0408/095747.361327:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.DBus.StartServiceByName: object_path= /org/freedesktop/DBus: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [4069:4069:0408/095747.677306:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139 MESA-INTEL: warning: Haswell Vulkan support is incomplete [4069:4069:0408/095748.114228:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139 MESA-INTEL: warning: Haswell Vulkan support is incomplete [4069:4069:0408/095748.555254:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139 MESA-INTEL: warning: Haswell Vulkan support is incomplete [4069:4069:0408/095748.978560:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139 [4069:4069:0408/095749.309510:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139 INFO: Created TensorFlow Lite XNNPACK delegate for CPU. [4069:4069:0408/095749.639428:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139 [4069:4069:0408/095749.977947:ERROR:gpu_process_host.cc(1002)] GPU process exited unexpectedly: exit_code=139 [4069:4069:0408/095749.977970:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye. [0408/095749.983418:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0408/095749.983488:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0408/095749.983521:ERROR:elf_dynamic_array_reader.h(64)] tag not found [0408/095749.983586:ERROR:elf_dynamic_array_reader.h(64)] tag not found Trace/breakpoint trap (core dumped) For slack: [4636:0408/095840.634615:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_code=139 MESA-INTEL: warning: Haswell Vulkan support is incomplete [4636:0408/095841.000845:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_code=139 MESA-INTEL: warning: Haswell Vulkan support is incomplete [4636:0408/095841.422391:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_code=139 MESA-INTEL: warning: Haswell Vulkan support is incomplete [4636:0408/095841.828327:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_code=139 MESA-INTEL: warning: Haswell Vulkan support is incomplete [4636:0408/095842.247934:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_code=139 [4636:0408/095842.604062:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_code=139 [4636:0408/095842.903471:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_code=139 [4636:0408/095843.305441:ERROR:gpu_process_host.cc(993)] GPU process exited unexpectedly: exit_code=139 [4636:0408/095843.305489:FATAL:gpu_data_manager_impl_private.cc(448)] GPU process isn't usable. Goodbye. Trace/breakpoint trap (core dumped) -- You are receiving this mail because: You are on the CC list for the bug.

1 11