[Bug 2061324] Re: Error when re-building package from source
Right, thanks @racb, this issue does not affect the development release, I put it to Invalid ** Changed in: intel-gpu-tools (Ubuntu) Status: In Progress => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[jira] [Commented] (KAFKA-16223) Replace EasyMock and PowerMock with Mockito for KafkaConfigBackingStoreTest
[ https://issues.apache.org/jira/browse/KAFKA-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17842717#comment-17842717 ] Hector Geraldino commented on KAFKA-16223: -- Thanks [~chia7712] [~cmukka20] for following up on this. As you've already noticed, the strategy I took was to create a separate [KafkaConfigBackingStoreMockitoTest|https://github.com/apache/kafka/blob/trunk/connect/runtime/src/test/java/org/apache/kafka/connect/storage/KafkaConfigBackingStoreMockitoTest.java] and migrate the tests in batches to facilitate reviews. My original plan was to do this in 3 separate batches, the [first batch|https://github.com/apache/kafka/pull/15520] was merged a few weeks ago, and I have another set of tests already migrated and plan to open the second PR soon. If you guys want to pick up the remaining that's fine by me. I haven't had enough time these past weeks to work on this, but I'd love to see this completed (and the migration to JUnit5 started) before 3.8 > Replace EasyMock and PowerMock with Mockito for KafkaConfigBackingStoreTest > --- > > Key: KAFKA-16223 > URL: https://issues.apache.org/jira/browse/KAFKA-16223 > Project: Kafka > Issue Type: Sub-task > Components: connect > Reporter: Hector Geraldino >Assignee: Hector Geraldino >Priority: Minor > Fix For: 3.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: [Launchpad-reviewers] [Merge] ~tchavadar/launchpad-buildd:use-ubuntu-images-deb into launchpad-buildd:master
The unmerged commits list seems strange, perhaps is it work to rebase properly on https://code.launchpad.net/~launchpad/launchpad-buildd/+git/launchpad-buildd/+ref/master ? -- https://code.launchpad.net/~tchavadar/launchpad-buildd/+git/launchpad-buildd/+merge/464761 Your team Launchpad code reviewers is requested to review the proposed merge of ~tchavadar/launchpad-buildd:use-ubuntu-images-deb into launchpad-buildd:master. ___ Mailing list: https://launchpad.net/~launchpad-reviewers Post to : launchpad-reviewers@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-reviewers More help : https://help.launchpad.net/ListHelp
[Bug 2062164] Re: test binary in share doc folder
** Changed in: qatzip (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062164 Title: test binary in share doc folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qatzip/+bug/2062164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062164] Re: test binary in share doc folder
The fix is uploaded here : https://launchpad.net/~hectorcao/+archive/ubuntu/lp-2062164 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062164 Title: test binary in share doc folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qatzip/+bug/2062164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2062164] [NEW] test binary in share doc folder
Public bug reported: The qzip-test binary is installed in /usr/share/doc/qatzip. Per consequence, it will be compressed and marked as not executable. Usually the sample, test binaries of a package should be installed in /usr/share/ ** Affects: qatzip (Ubuntu) Importance: Undecided Assignee: Hector CAO (hectorcao) Status: In Progress ** Changed in: qatzip (Ubuntu) Status: New => In Progress ** Changed in: qatzip (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2062164 Title: test binary in share doc folder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qatzip/+bug/2062164/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): - tools/intel_gpu_top: Fix clients header width when no clients - tools/intel_gpu_top: Fix client layout on first sample period - tools/intel_gpu_top: Optimise interactive display a bit - tools/intel_gpu_top: Handle narrow terminals more gracefully + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully + + NOTES: + For Noble, all the 4 patches will be backported + For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): - tools/intel_gpu_top: Fix clients header width when no clients - tools/intel_gpu_top: Fix client layout on first sample period - tools/intel_gpu_top: Optimise interactive display a bit - tools/intel_gpu_top: Handle narrow terminals more gracefully + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully + + NOTES: + For Noble, all the 4 patches will be backported + For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: In Progress Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully NOTES: For Noble, all the 4 patches will be backported For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it
[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source
build fix is usually not accepted in SRU, this fix will be part of https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314 ** Changed in: intel-gpu-tools (Ubuntu Jammy) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Jammy) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061324] Re: Error when re-building package from source
build fix is usually not accepted in SRU, this fix will be part of
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314
** Changed in: intel-gpu-tools (Ubuntu Jammy)
Status: New => In Progress
** Changed in: intel-gpu-tools (Ubuntu Jammy)
Assignee: (unassigned) => Hector CAO (hectorcao)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Status in intel-gpu-tools source package in Jammy:
In Progress
Bug description:
[ Impact ]
Impossible to build the package from source on Ubuntu 22.04, users will get
this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The problem comes from the bad call to meson function underscorify in
lib/meson.build
This problem has been fixed upstream:
963917a3565466832a3b2fc22e9285d34a0bf944
lib/meson.build: Fix underscorify call
f.underscorify() is correct, f.underscorify(f) is an error that later
meson versions don't like at all.
The proposed fix for Ubuntu consists of backporting this patch.
[ Test Plan ]
Build the package from source on Ubuntu 22.04
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
[ Where problems could occur ]
The problem occurs only at build process
[ Other Info ]
This issue only happens at build and has been fixed upstream.
It is safe to have it in SRU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): - tools/intel_gpu_top: Fix clients header width when no clients - tools/intel_gpu_top: Fix client layout on first sample period - tools/intel_gpu_top: Optimise interactive display a bit - tools/intel_gpu_top: Handle narrow terminals more gracefully + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully + + NOTES: + For Noble, all the 4 patches will be backported + For Mantic, Jammy, only "tools/intel_gpu_top: Handle narrow terminals more gracefully" will be backported because the others are not applicable to Jammy/Mantic (related to refactoring that happened after Mantic release) [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2061324] Re: Error when re-building package from source
build fix is usually not accepted in SRU, this fix will be part of https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314 ** Changed in: intel-gpu-tools (Ubuntu Jammy) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Jammy) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: In Progress Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re:[ANNOUNCE] New Kafka PMC Member: Greg Harris
Congrats! Well deserved From: dev@kafka.apache.org At: 04/13/24 14:42:22 UTC-4:00To: dev@kafka.apache.org Subject: [ANNOUNCE] New Kafka PMC Member: Greg Harris Hi all, Greg Harris has been a Kafka committer since July 2023. He has remained very active and instructive in the community since becoming a committer. It's my pleasure to announce that Greg is now a member of Kafka PMC. Congratulations, Greg! Chris, on behalf of the Apache Kafka PMC
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu Mantic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: In Progress Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for noble ** Attachment removed: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz ** Attachment added: "intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765627/+files/intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for noble ** Attachment removed: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz ** Attachment added: "intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765627/+files/intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for noble ** Attachment removed: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz ** Attachment added: "intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765627/+files/intel-gpu-tools_1.28-1ubuntu0.1_1.28-1ubuntu2.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: Fix Released Status in intel-gpu-tools source package in Noble: Fix Released Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for Noble ** Attachment added: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for Noble ** Attachment added: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
The fixed is available for Noble at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp-1949314 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
debdiff for Noble ** Attachment added: "intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765600/+files/intel-gpu-tools_1.28-1build2_1.28-1ubuntu0.1.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
The fixed is available for Noble at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp-1949314 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu releases (Jammy, Mantic and Noble) Tvrtko Ursulin (4): tools/intel_gpu_top: Fix clients header width when no clients tools/intel_gpu_top: Fix client layout on first sample period tools/intel_gpu_top: Optimise interactive display a bit tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
The fixed is available for Noble at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp-1949314 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 - The proposed fix consists of backporting this fix to affected ubuntu + The fix has been part of a serie of fixes that improve intel_gpu_top UI + behavior for some corner cases : + https://patchwork.freedesktop.org/series/124890/ + + The proposed fix consists of backporting these fixes to affected Ubuntu releases : Jammy, Mantic and Noble [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu - releases : Jammy, Mantic and Noble + releases (Jammy, Mantic and Noble) + + Tvrtko Ursulin (4): + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 - The proposed fix consists of backporting this fix to affected ubuntu + The fix has been part of a serie of fixes that improve intel_gpu_top UI + behavior for some corner cases : + https://patchwork.freedesktop.org/series/124890/ + + The proposed fix consists of backporting these fixes to affected Ubuntu releases : Jammy, Mantic and Noble [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu - releases : Jammy, Mantic and Noble + releases (Jammy, Mantic and Noble) + + Tvrtko Ursulin (4): + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Status in intel-gpu-tools source package in Noble: In Progress Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is:
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 - The proposed fix consists of backporting this fix to affected ubuntu + The fix has been part of a serie of fixes that improve intel_gpu_top UI + behavior for some corner cases : + https://patchwork.freedesktop.org/series/124890/ + + The proposed fix consists of backporting these fixes to affected Ubuntu releases : Jammy, Mantic and Noble [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Description changed: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The fix has been part of a serie of fixes that improve intel_gpu_top UI behavior for some corner cases : https://patchwork.freedesktop.org/series/124890/ The proposed fix consists of backporting these fixes to affected Ubuntu - releases : Jammy, Mantic and Noble + releases (Jammy, Mantic and Noble) + + Tvrtko Ursulin (4): + tools/intel_gpu_top: Fix clients header width when no clients + tools/intel_gpu_top: Fix client layout on first sample period + tools/intel_gpu_top: Optimise interactive display a bit + tools/intel_gpu_top: Handle narrow terminals more gracefully [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] - When resizing the terminal window, intel_gpu_top may crash if the window + When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: - intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion + intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. + The fix has been reported and fixed upstream recently : + https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 - The proposed fix consists of removing the assert() function and only skip drawing. + The proposed fix consists of backporting this fix to affected ubuntu + releases : Jammy, Mantic and Noble [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] - When resizing the terminal window, intel_gpu_top may crash if the window + When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: - intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion + intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. + The fix has been reported and fixed upstream recently : + https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 - The proposed fix consists of removing the assert() function and only skip drawing. + The proposed fix consists of backporting this fix to affected ubuntu + releases : Jammy, Mantic and Noble [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The fix has been reported and fixed upstream recently : https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 The proposed fix consists of backporting this fix to affected ubuntu releases : Jammy, Mantic and Noble [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: [ Impact ] - When resizing the terminal window, intel_gpu_top may crash if the window + When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: - intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion + intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. + The fix has been reported and fixed upstream recently : + https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/issues/143 - The proposed fix consists of removing the assert() function and only skip drawing. + The proposed fix consists of backporting this fix to affected ubuntu + releases : Jammy, Mantic and Noble [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: + [ Impact ] + + When resizing the terminal window, intel_gpu_top may crash if the window + becomes small enough. The output when it crashes is: + + intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion + `max_len > 0' failed. + + + The proposed fix consists of removing the assert() function and only skip drawing. + + [ Test Plan ] + + Run intel_gpu_top inside a console + Resize the console with the mouse to it smallest size + + [ Where problems could occur ] + + The problem occurs when intel_gpu_top try to draw information on the + console + + [ Other Info ] + + This fix should not cause regression on any other feature. + + + When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Changed in: intel-gpu-tools (Ubuntu Jammy) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Jammy) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Jammy: In Progress Status in intel-gpu-tools source package in Mantic: New Bug description: [ Impact ] When resizing the terminal window, intel_gpu_top may crash if the window becomes small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. The proposed fix consists of removing the assert() function and only skip drawing. [ Test Plan ] Run intel_gpu_top inside a console Resize the console with the mouse to it smallest size [ Where problems could occur ] The problem occurs when intel_gpu_top try to draw information on the console [ Other Info ] This fix should not cause regression on any other feature. When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: + [ Impact ] + + When resizing the terminal window, intel_gpu_top may crash if the window + becomes small enough. The output when it crashes is: + + intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion + `max_len > 0' failed. + + + The proposed fix consists of removing the assert() function and only skip drawing. + + [ Test Plan ] + + Run intel_gpu_top inside a console + Resize the console with the mouse to it smallest size + + [ Where problems could occur ] + + The problem occurs when intel_gpu_top try to draw information on the + console + + [ Other Info ] + + This fix should not cause regression on any other feature. + + + When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Changed in: intel-gpu-tools (Ubuntu Jammy) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Jammy) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Description changed: + [ Impact ] + + When resizing the terminal window, intel_gpu_top may crash if the window + becomes small enough. The output when it crashes is: + + intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion + `max_len > 0' failed. + + + The proposed fix consists of removing the assert() function and only skip drawing. + + [ Test Plan ] + + Run intel_gpu_top inside a console + Resize the console with the mouse to it smallest size + + [ Where problems could occur ] + + The problem occurs when intel_gpu_top try to draw information on the + console + + [ Other Info ] + + This fix should not cause regression on any other feature. + + + When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] ** Changed in: intel-gpu-tools (Ubuntu Jammy) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Jammy) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source
** Description changed:
- When I try to build package from source in Ubuntu Jammy 22.04, i run
- into this error:
+ [ Impact ]
+
+ Impossible to build the package from source on Ubuntu 22.04, users will get
+ this error:
```
int main(void) {
- void *a = (void*) _create;
- long long b = (long long) a;
- return (int) b;
- }
+ void *a = (void*) _create;
+ long long b = (long long) a;
+ return (int) b;
+ }
Compiler stdout:
-
+
Compiler stderr:
-
- Checking for function "memfd_create" : YES
+
+ Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
- The build command is : dpkg-buildpackage -us -uc -b
- Ubuntu release : Jammy 22.04
- Meson version : 0.61.2
+ The problem comes from the bad call to meson function underscorify in
+ lib/meson.build
+
+ This problem has been fixed upstream:
+
+ 963917a3565466832a3b2fc22e9285d34a0bf944
+ lib/meson.build: Fix underscorify call
+ f.underscorify() is correct, f.underscorify(f) is an error that later
+ meson versions don't like at all.
+
+ The proposed fix for Ubuntu consists of backporting this patch.
+
+ [ Test Plan ]
+
+ Build the package from source on Ubuntu 22.04
+
+ The build command is : dpkg-buildpackage -us -uc -b
+ Ubuntu release : Jammy 22.04
+ Meson version : 0.61.2
+
+ [ Where problems could occur ]
+
+ The problem occurs only at build process
+
+ [ Other Info ]
+
+ This issue only happens at build and has been fixed upstream.
+ It is safe to have it in SRU
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Bug 2061324] Re: Error when re-building package from source
** Description changed:
- When I try to build package from source in Ubuntu Jammy 22.04, i run
- into this error:
+ [ Impact ]
+
+ Impossible to build the package from source on Ubuntu 22.04, users will get
+ this error:
```
int main(void) {
- void *a = (void*) _create;
- long long b = (long long) a;
- return (int) b;
- }
+ void *a = (void*) _create;
+ long long b = (long long) a;
+ return (int) b;
+ }
Compiler stdout:
-
+
Compiler stderr:
-
- Checking for function "memfd_create" : YES
+
+ Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
- The build command is : dpkg-buildpackage -us -uc -b
- Ubuntu release : Jammy 22.04
- Meson version : 0.61.2
+ The problem comes from the bad call to meson function underscorify in
+ lib/meson.build
+
+ This problem has been fixed upstream:
+
+ 963917a3565466832a3b2fc22e9285d34a0bf944
+ lib/meson.build: Fix underscorify call
+ f.underscorify() is correct, f.underscorify(f) is an error that later
+ meson versions don't like at all.
+
+ The proposed fix for Ubuntu consists of backporting this patch.
+
+ [ Test Plan ]
+
+ Build the package from source on Ubuntu 22.04
+
+ The build command is : dpkg-buildpackage -us -uc -b
+ Ubuntu release : Jammy 22.04
+ Meson version : 0.61.2
+
+ [ Where problems could occur ]
+
+ The problem occurs only at build process
+
+ [ Other Info ]
+
+ This issue only happens at build and has been fixed upstream.
+ It is safe to have it in SRU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2061324] Re: Error when re-building package from source
** Description changed:
- When I try to build package from source in Ubuntu Jammy 22.04, i run
- into this error:
+ [ Impact ]
+
+ Impossible to build the package from source on Ubuntu 22.04, users will get
+ this error:
```
int main(void) {
- void *a = (void*) _create;
- long long b = (long long) a;
- return (int) b;
- }
+ void *a = (void*) _create;
+ long long b = (long long) a;
+ return (int) b;
+ }
Compiler stdout:
-
+
Compiler stderr:
-
- Checking for function "memfd_create" : YES
+
+ Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
- The build command is : dpkg-buildpackage -us -uc -b
- Ubuntu release : Jammy 22.04
- Meson version : 0.61.2
+ The problem comes from the bad call to meson function underscorify in
+ lib/meson.build
+
+ This problem has been fixed upstream:
+
+ 963917a3565466832a3b2fc22e9285d34a0bf944
+ lib/meson.build: Fix underscorify call
+ f.underscorify() is correct, f.underscorify(f) is an error that later
+ meson versions don't like at all.
+
+ The proposed fix for Ubuntu consists of backporting this patch.
+
+ [ Test Plan ]
+
+ Build the package from source on Ubuntu 22.04
+
+ The build command is : dpkg-buildpackage -us -uc -b
+ Ubuntu release : Jammy 22.04
+ Meson version : 0.61.2
+
+ [ Where problems could occur ]
+
+ The problem occurs only at build process
+
+ [ Other Info ]
+
+ This issue only happens at build and has been fixed upstream.
+ It is safe to have it in SRU
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Status in intel-gpu-tools source package in Jammy:
New
Bug description:
[ Impact ]
Impossible to build the package from source on Ubuntu 22.04, users will get
this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The problem comes from the bad call to meson function underscorify in
lib/meson.build
This problem has been fixed upstream:
963917a3565466832a3b2fc22e9285d34a0bf944
lib/meson.build: Fix underscorify call
f.underscorify() is correct, f.underscorify(f) is an error that later
meson versions don't like at all.
The proposed fix for Ubuntu consists of backporting this patch.
[ Test Plan ]
Build the package from source on Ubuntu 22.04
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
[ Where problems could occur ]
The problem occurs only at build process
[ Other Info ]
This issue only happens at build and has been fixed upstream.
It is safe to have it in SRU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1852916] Re: GPU problem, screen flikers a lot on start and log off. Unable to see anything black out.
@punisher01 : I think this bug has been reported for the wrong component, ** Changed in: intel-gpu-tools (Ubuntu) Status: New => Invalid ** Changed in: intel-gpu-tools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1852916 Title: GPU problem, screen flikers a lot on start and log off. Unable to see anything black out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1852916/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852916] Re: GPU problem, screen flikers a lot on start and log off. Unable to see anything black out.
@punisher01 : I think this bug has been reported for the wrong component, ** Changed in: intel-gpu-tools (Ubuntu) Status: New => Invalid ** Changed in: intel-gpu-tools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1852916 Title: GPU problem, screen flikers a lot on start and log off. Unable to see anything black out. Status in intel-gpu-tools package in Ubuntu: Invalid Bug description: I am using Dell Vostro 15 3568 runing on Ubuntu 19.04 with Graphics : Intel® HD Graphics 620 (Kaby Lake GT2) and Amd Radeon on it. But lately have some problem with something either the GPU, GRUB or kernel. The I uninstalled the driver for Amd Radeon after reading articles over internet but it did not help. Also tried to add "GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nomodeset" in GRUB but did not work. I do not know what is the problem I have tried almost everything available but it does not fix. Please help me in fixing the problem. It so irritating, while restarting of siging in it takes ages. This problem was encountred after some package update while I was using Ubuntu 18.04 LTE, so later I upgraded to Ubuntu 19.04 in hope of solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1852916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 1852916] Re: GPU problem, screen flikers a lot on start and log off. Unable to see anything black out.
@punisher01 : I think this bug has been reported for the wrong component, ** Changed in: intel-gpu-tools (Ubuntu) Status: New => Invalid ** Changed in: intel-gpu-tools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1852916 Title: GPU problem, screen flikers a lot on start and log off. Unable to see anything black out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1852916/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Here is the debdiff for the proposed fix ** Attachment added: "intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765384/+files/intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Bug description: When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Here is the debdiff for the proposed fix ** Attachment added: "intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765384/+files/intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
Here is the debdiff for the proposed fix ** Attachment added: "intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+attachment/5765384/+files/intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: intel-gpu-tools (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: intel-gpu-tools (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: In Progress Bug description: When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
** Changed in: intel-gpu-tools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: intel-gpu-tools (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source
here is the debdiff of the fix ** Attachment added: "intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+attachment/5765373/+files/intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 2061324] Re: Error when re-building package from source
here is the debdiff of the fix ** Attachment added: "intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+attachment/5765373/+files/intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2061324] Re: Error when re-building package from source
here is the debdiff of the fix
** Attachment added: "intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz"
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+attachment/5765373/+files/intel-gpu-tools_1.26-2_1.26-2ubuntu1.diff.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Bug description:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
I was able to reproduce this problen on 22.04 ** Changed in: intel-gpu-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
I was able to reproduce this problen on 22.04 ** Changed in: intel-gpu-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Status in intel-gpu-tools package in Ubuntu: Confirmed Bug description: When resizing the terminal window, intel_gpu_top may crash if the window become small enough. The output when it crashes is: intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. Abortado I was able to reproduce this crash with tilix and xterm. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: intel-gpu-tools 1.26-2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: XFCE Date: Sun Oct 31 21:06:01 2021 InstallationDate: Installed on 2017-06-13 (1601 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to jammy on 2019-12-22 (679 days ago) modified.conffile..etc.cron.daily.apport: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1949314] Re: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed.
I was able to reproduce this problen on 22.04 ** Changed in: intel-gpu-tools (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1949314 Title: intel_gpu_top crashes with intel_gpu_top: ../tools/intel_gpu_top.c:1202: print_percentage_bar: Assertion `max_len > 0' failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1949314/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source
The package with proposed fixed for Jammy can be found at: https://launchpad.net/~hectorcao/+archive/ubuntu/lp2061324 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 2061324] Re: Error when re-building package from source
The package with proposed fixed for Jammy can be found at: https://launchpad.net/~hectorcao/+archive/ubuntu/lp2061324 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2061324] Re: Error when re-building package from source
The package with proposed fixed for Jammy can be found at:
https://launchpad.net/~hectorcao/+archive/ubuntu/lp2061324
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Bug description:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Bug 2061324] Re: Error when re-building package from source
This problem has been fixed upstream: 963917a3565466832a3b2fc22e9285d34a0bf944 lib/meson.build: Fix underscorify call f.underscorify() is correct, f.underscorify(f) is an error that later meson versions don't like at all. Closes: #107 Fixes: 588555f7 See : https://gitlab.freedesktop.org/drm/igt-gpu- tools/-/commit/963917a3565466832a3b2fc22e9285d34a0bf944 I propose to backport this patch ** Changed in: intel-gpu-tools (Ubuntu) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2061324] Re: Error when re-building package from source
This problem has been fixed upstream:
963917a3565466832a3b2fc22e9285d34a0bf944
lib/meson.build: Fix underscorify call
f.underscorify() is correct, f.underscorify(f) is an error that later
meson versions don't like at all.
Closes: #107
Fixes: 588555f7
See : https://gitlab.freedesktop.org/drm/igt-gpu-
tools/-/commit/963917a3565466832a3b2fc22e9285d34a0bf944
I propose to backport this patch
** Changed in: intel-gpu-tools (Ubuntu)
Status: New => In Progress
** Changed in: intel-gpu-tools (Ubuntu)
Assignee: (unassigned) => Hector CAO (hectorcao)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
In Progress
Bug description:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2061324] Re: Error when re-building package from source
This problem has been fixed upstream: 963917a3565466832a3b2fc22e9285d34a0bf944 lib/meson.build: Fix underscorify call f.underscorify() is correct, f.underscorify(f) is an error that later meson versions don't like at all. Closes: #107 Fixes: 588555f7 See : https://gitlab.freedesktop.org/drm/igt-gpu- tools/-/commit/963917a3565466832a3b2fc22e9285d34a0bf944 I propose to backport this patch ** Changed in: intel-gpu-tools (Ubuntu) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2061324 Title: Error when re-building package from source To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2061324] [NEW] Error when re-building package from source
Public bug reported:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
** Affects: intel-gpu-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2061324] [NEW] Error when re-building package from source
Public bug reported:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
** Affects: intel-gpu-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to intel-gpu-tools in Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
Status in intel-gpu-tools package in Ubuntu:
New
Bug description:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Bug 2061324] [NEW] Error when re-building package from source
Public bug reported:
When I try to build package from source in Ubuntu Jammy 22.04, i run
into this error:
```
int main(void) {
void *a = (void*) _create;
long long b = (long long) a;
return (int) b;
}
Compiler stdout:
Compiler stderr:
Checking for function "memfd_create" : YES
Configuring config.h using configuration
../lib/meson.build:155:4: ERROR: Function does not take positional arguments.
dh_auto_configure: error: cd build && LC_ALL=C.UTF-8 meson ..
--wrap-mode=nodownload --buildtype=plain --prefix=/usr --sysconfdir=/etc
--localstatedir=/var --libdir=lib/x86_64-linux-gnu -Dtests=disabled returned
exit code 1
make[1]: *** [debian/rules:19: override_dh_auto_configure] Error 255
make[1]: Leaving directory '/home/ubuntu/hector/intel-gpu-tools-1.26'
make: *** [debian/rules:39: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
```
The build command is : dpkg-buildpackage -us -uc -b
Ubuntu release : Jammy 22.04
Meson version : 0.61.2
** Affects: intel-gpu-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061324
Title:
Error when re-building package from source
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/2061324/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
@dongwonk : i see that you are probably testing on jammy, that is the wrong release, the package to be tested is for 24.04 (you can install it with the daily build ISO). regarding the networking problem, that is probably proxy problem, a work-around is to download the debian package at https://ppa.launchpadcontent.net/hectorcao/lp2049714/ubuntu/pool/main/i/intel- gpu-tools/intel-gpu-tools_1.28-1ubuntu1_amd64.deb , and install it with dpkg let me know if you have any further question -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
@dongwonk : i see that you are probably testing on jammy, that is the wrong release, the package to be tested is for 24.04 (you can install it with the daily build ISO). regarding the networking problem, that is probably proxy problem, a work-around is to download the debian package at https://ppa.launchpadcontent.net/hectorcao/lp2049714/ubuntu/pool/main/i/intel- gpu-tools/intel-gpu-tools_1.28-1ubuntu1_amd64.deb , and install it with dpkg let me know if you have any further question -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Kernel-packages] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
@dongwonk : i see that you are probably testing on jammy, that is the wrong release, the package to be tested is for 24.04 (you can install it with the daily build ISO). regarding the networking problem, that is probably proxy problem, a work-around is to download the debian package at https://ppa.launchpadcontent.net/hectorcao/lp2049714/ubuntu/pool/main/i/intel- gpu-tools/intel-gpu-tools_1.28-1ubuntu1_amd64.deb , and install it with dpkg let me know if you have any further question -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Noble: In Progress Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
Hi @dongwonk, @chaoqin, I uploaded a package for Ubuntu 24.04 with the fix at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp2049714 Could you please take a look and validate it on appropriate hardware ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
Hi @dongwonk, @chaoqin, I uploaded a package for Ubuntu 24.04 with the fix at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp2049714 Could you please take a look and validate it on appropriate hardware ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Noble: In Progress Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
Hi @dongwonk, @chaoqin, I uploaded a package for Ubuntu 24.04 with the fix at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp2049714 Could you please take a look and validate it on appropriate hardware ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [dmarc-ietf] There is no pony, Overall last-call comments on DMARC
My overall assessment as an early adopter and implementation: DMARC SHOULD NOT be declared a Standard Track document. We still have the potential to develop a sound 1st, 3rd party DKIM Policy model. Declaring DMARCBis a STD will only hamper future development. Keep it experimental or informational. DMARC/Bis has represented a big IETF “Elephant In The Room” change in allowing External 3rd Party Organizations to put barriers of entry to correct the IETF protocol development.. Change is needed. DMARCBis is not it. Is there is an Update Document minus the subjectives considerations. It has been a fair process but a very high hurdle to correct a serious IETF protocol problem. All the best, Hector Santos > On Apr 4, 2024, at 4:47 PM, Jim Fenton wrote: > > On 4 Apr 2024, at 13:31, John R. Levine wrote: > >>> I don’t think it’s scope creep at all. The WG charter puts “Review and >>> refinement of the DMARC specification” in phase III, after “Specification >>> of DMARC improvements to support indirect mail flows”. It seems clear to me >>> that standards-track DMARC needs to incorporate those improvements. >>> >>> IESG accepted ARC as an improvement to support indirect mail flows, and I >>> think a complete solution needs to incorporate that. I wish there were >>> better data to support advancing ARC to standards track, and not just from >>> Google (it has to work for smaller players as well). >>> >>> But I am troubled by the possibility that ARC might require domain >>> reputation to avoid ARC header fields supporting From address spoofing. One >>> reason it might work for Google is because they’re big enough to derive >>> their own domain reputation. We’ve not had success with domain reputation >>> at internet scale. >> >> No might about it -- ARC is only useful with domain reputation. Of course, >> DKIM is only useful with domain reputation, as were Domainkeys and IIM, so I >> don't see why it's a problem now. > > Much of the objective of DomainKeys/IIM/DKIM was to provide a reliable domain > identifier that could be used by a reputation system. They avoided saying > that they were doing anything about spam and phishing. OTOH, DMARC is > explicitly saying that it’s there to do something about phishing. > >> We've been going around and around for years now. DMARC works pretty well >> for direct mail flows, so-so for simple indirect flows (forwarders) and >> really badly for mediated indirect flows (mailing lists.) There is nothing >> better than ARC to mitigate those problems and this WG certainly isn't going >> to invent anything now. I agree that at this point we don't have enough >> evidence to advance ARC, so we can punt the question of what or when to do >> with it to MAILMAINT or something. >> >> Our choices are to say here's what DMARC does, it has these problems, here's >> how to use it for the situations where it works, here's how to sort of >> mitigate the ones where it doesn't. Or we can stamp our feet and say DMARC >> is BAD and we will not endorse it and NOBODY should use it, and the rest of >> the mail world will say isn't that cute, the IETF is having a tantrum. > > Or we can say that it’s not ready for standards track yet. The only time I > can think of in this space that we have stamped our feet and said something > is BAD was with ADSP. But I am troubled by the mandatory requirements imposed > by organizations citing an informational RFC, RFC 7489. It makes it seem like > standards track doesn’t mean as much as it should. > > -Jim > > ___ > dmarc mailing list > dmarc@ietf.org > https://www.ietf.org/mailman/listinfo/dmarc ___ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
Re: [Ietf-dkim] Testing a DKIM implementation
On 3/22/2024 8:25 AM, David Harris wrote: My thanks to Murray S. Kucherawy, who was most helpful in answering my previous questions about specifics of RFC6376.. I now have my implementation complete: I was wondering if there is a recommended way of testing it - for instance, a reference site that allows you to send messages and then replies with information about the correctness of your implementation, or an application that can generate signatures for data you supply, showing its work product (the various hashes and canonicalized forms) so you can compare it with your own. Any pointers would be appreciated. Thanks in advance for any assistance. There are number of verifiers. One such address is dkim-autoresp...@isdg.net will verify your DKIM signatures and apply DKIM Policies such as ADSP (deprecated), DMARC and report the result. -- Hector Santos, https://santronics.com https://winserver.com ___ Ietf-dkim mailing list Ietf-dkim@ietf.org https://www.ietf.org/mailman/listinfo/ietf-dkim
[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Noble) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Noble) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Noble: In Progress Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Information type changed from Private to Public ** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement Status in intel: Fix Released Status in The Kobuk project: In Progress Status in intel-gpu-tools package in Ubuntu: In Progress Status in intel-gpu-tools source package in Noble: In Progress Bug description: [Description] igt-gpu-tool enabling for Raptor Lake-P [Hardware Information] Architecture: Intel Platform(s): Raptor Lake-P Date HW is expected at Canonical: Component(s): itg-gpu-tool [Software Information] Target Version: 22.04 Target Kernel: Commit IDs / External Links: https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/commit/1b32bcdb2d9965090234739aba891a90743e01c4 [Business Justification] [Testing guidance] [External ID] To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Information type changed from Private to Public ** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Changed in: intel-gpu-tools (Ubuntu Noble) Status: New => In Progress ** Changed in: intel-gpu-tools (Ubuntu Noble) Assignee: (unassigned) => Hector CAO (hectorcao) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2049714] Re: [RPL-P] igt-gpu-tool enablement
** Information type changed from Private to Public ** Changed in: intel Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2049714 Title: [RPL-P] igt-gpu-tool enablement To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/2049714/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: Please recommend postgresql.conf improvements for osm2pgsql loading Europe
On Sat, 30 Mar 2024, 10:04 Alexander Farber, wrote: > Thank you, Justin - > > On Sat, Mar 30, 2024 at 4:33 AM Justin Clift > wrote: > >> On 2024-03-30 05:53, Alexander Farber wrote: >> > I use the following postgresql.conf in my Dockerfile >> > ( the full version at https://stackoverflow.com/a/78243530/165071 ), >> > when loading a 28 GByte large europe-latest.osm.pbf >> >> Not specific conf file improvements, but for an initial data load >> have you done things like turning off fsync(), deferring index >> creating until after the data load finishes, and that kind of thing? >> > > I will try the following commands in my Dockerfile then > and later report back on any improvements: > > RUN set -eux && \ > pg_ctl init && \ > echo "shared_buffers = 1GB">> $PGDATA/postgresql.conf > && \ > echo "work_mem = 50MB" >> $PGDATA/postgresql.conf > && \ > echo "maintenance_work_mem = 10GB" >> $PGDATA/postgresql.conf > && \ > echo "autovacuum_work_mem = 2GB" >> $PGDATA/postgresql.conf > && \ > echo "wal_level = minimal" >> $PGDATA/postgresql.conf > && \ > echo "checkpoint_timeout = 60min" >> $PGDATA/postgresql.conf > && \ > echo "max_wal_size = 10GB" >> $PGDATA/postgresql.conf > && \ > echo "checkpoint_completion_target = 0.9" >> $PGDATA/postgresql.conf > && \ > echo "max_wal_senders = 0" >> $PGDATA/postgresql.conf > && \ > echo "random_page_cost = 1.0" >> $PGDATA/postgresql.conf > && \ > echo "password_encryption = scram-sha-256" >> $PGDATA/postgresql.conf > && \ > echo "fsync = off">> > $PGDATA/postgresql.conf && \ > pg_ctl start && \ > createuser --username=postgres $PGUSER && \ > createdb --username=postgres --encoding=UTF8 --owner=$PGUSER > $PGDATABASE && \ > psql --username=postgres $PGDATABASE --command="ALTER USER $PGUSER > WITH PASSWORD '$PGPASSWORD';" && \ > psql --username=postgres $PGDATABASE --command='CREATE EXTENSION IF > NOT EXISTS postgis;' && \ > psql --username=postgres $PGDATABASE --command='CREATE EXTENSION IF > NOT EXISTS hstore;' && \ > osm2pgsql --username=$PGUSER --database=$PGDATABASE --create > --cache=6 --hstore --latlong /data/map.osm.pbf && \ > rm -f /data/map.osm.pbf && \ > pg_ctl stop && \ > echo "fsync = on">> > $PGDATA/postgresql.conf && \ > echo '# TYPE DATABASE USER ADDRESS METHOD'> > $PGDATA/pg_hba.conf && \ > echo "local all postgres peer" >> > $PGDATA/pg_hba.conf && \ > echo "local $PGDATABASE $PGUSER scram-sha-256" >> > $PGDATA/pg_hba.conf && \ > echo "host $PGDATABASE $PGUSER 0.0.0.0/0 scram-sha-256" >> > $PGDATA/pg_hba.conf > > The later fsync = on will override the former, right? > > Best regards > Alex > > > 2hrs sounds reasonable for Europe, it's a big place in terms of osm data and osm2pgsql is doing processing to convert to geometry objects prior to doing anything on the Postgresql side. If you examine the --log--sql output for a small test country you can see what it does in terms of the postgresql. osm2pgsql gives options to trim the output to only what you need (so if you don't want waterways, traffic features, parking places or places of worship etc.. why load them) Hopefully you have found the excellent geofabrik https://download.geofabrik.de/ source for osm data. Rather than load this data afresh each update cycle you would be better off simply loading the changes so the .osc files or ... osm osmosis will create the equivalent of a diff file for you Looks like you are already using osm2psql's recommended postgresql.config settings, I'd be surprised if this was way off. Getting as close to tin rather than virtual machines and containers will also help, lots of io going on here. If you are only interested in the geography you might consider geofabrik's shapefile available for many countries, they have already done some of the work for you. Apologies if you are already a long way down this route & just asking about the final stage of loading the osm2pgsql output to Postgresql but however well you do here I would only expect small marginal gains.
Re:[DISCUSS] KIP-1028: Docker Official Image for Apache Kafka
Hi, What is the difference between this KIP and KIP-975: Docker Image for Apache Kafka? From: dev@kafka.apache.org At: 03/21/24 07:30:07 UTC-4:00To: dev@kafka.apache.org Subject: [DISCUSS] KIP-1028: Docker Official Image for Apache Kafka Hi everyone, I would like to start the discussion on https://cwiki.apache.org/confluence/display/KAFKA/KIP-1028%3A+Docker+Official+Im age+for+Apache+Kafka . This KIP aims to introduce JVM based Docker Official Image (DOI) for Apache Kafka. Regards, Krish.
[sumo-user] background map resolution
Dear sumo community, I am using the tileGet.py script to pull a map from an ARCGIS service but I would like to avoid the bad stitching of tiles that looks less than professional when I give presentations in large screens. I tried pulling only one tile but the resolution is very blurry eventhough I don't get the bad stitching. Would you recommend changing the code in the tileGet.py to give me a better resolution of the background map when I zoom in to look a vehicles in the network? If so, where would you recommend I do it to avoid braking the script? Thanks, Hector A. Martinez, P.E. Group Leader, N253 - CENTCOM, SOUTHCOM and Joint Staff Ops MITRE | National Security Engineering Center<https://www.mitre.org/centers/national-security-and-engineering-center/who-we-are> 813.207.5365 ___ sumo-user mailing list sumo-user@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/sumo-user
Re: [dmarc-ietf] DMARC exceptions
Doug, since of dawn of electronic messaging, a system local policy always prevails. When implementing the new SMTP filters such as SPF, the more powerful policy was one of detecting failure. The PASS meant nothing since it may not pre-empt any other checking. For us, wcSPF was the exception in the wcSMTP suites of filters out of the box: - Low Code Reject/Access rules - DNS-RBL - SPF - CBV SPF would pre-empt the final CBV check for a matching source (pass). An SPF Hard Fail is an immediate 550 rejection response. A unknown continues with the CBV check. When it comes to DKIM, we calculate all the valid signatures. When it comes to a DKIM Policy Model - well, we have DMARC. We apply the protocol rules without exceptions. If a Local System does not honor the results for any reason, that is ok. But I don’t think it can define a consistent Local Policy OverRide and expect systems to use same local overrides. Again, my Philosophy has been Failure Detection as the key filtering strength for all the DKIM Policies explored. A PASS or worst unknown/neutral means nothing because good and bad can both apply. Another “Trust” Layer is considered at the local level. All the best, Hector Santos > On Mar 15, 2024, at 1:46 AM, Douglas Foster > wrote: > > DMARC is an imperfect tool, as evidenced by the mailing list problem, among > others. DMARCbis has failed to integrate RFC7489 with RFC 7960, because it > provides no discussion of the circumstances where an evaluator should > override the DMARC result. I believe DMARCbis needs a discussion about the > appropriate scope and characteristics of local policy. I have developed an > initial draft of proposed language for that section, which appears below > > Doug Foster > > > x. Exceptions / Local Policy > > A DMARC disposition policy communicates the domain owner’s recommendation for > handling of messages which fail to authenticate. By definition, this > recommendation cannot take into consideration the local interest of specific > receivers, or the specific flow path of any specific message. As a result, > evaluators should anticipate the need to implement local policy exceptions > that override the DMARC recommended disposition when appropriate. These > exceptions can be considered in two groups: policy overrides and > authentication overrides. This section discusses some expected override > scenarios, without intending to be comprehensive, so that product > implementers can create appropriate exception structures for these and > similar possible situations. > > x.1 Policy Overrides > > x.1.1 Override p=none > > A disposition policy of “none” indicates that the domain owner suspects that > some evaluators may receive some legitimate and wanted messages which lack > authentication when received. The evaluator may reasonably conclude that > its risk of allowing a message which maliciously impersonates the domain is > much greater than the risk of hindering a legitimate-but-unauthenticated > message from the domain. In such cases, the local policy will override > p=none and handle the domain with p=quarantine or p=reject. > > x.1.2 Override missing PSL=Y > > Some PSDs have implemented DMARC policies in accordance with RFC 9901, > without a PSL tag because that RFC assumed that organizational domain > determination would be provided by the PSL. Particularly during the early > rollout of this specification, evaluators should use the PSL to identify > DMARC policies which are intended to be treated as PSL=Y even though the > PSD’s policy has not yet been updated to include the PSD=Y tag. > > x.1.3 Override strict alignment > > A domain may publish aspf=s or adkim=s incorrectly, which the evaluator will > detect when legitimate and wanted messages produce a DMARC Fail result, even > though they would produce Pass using relaxed alignment. In this case, the > evaluator overrides the strict alignment rules in the published policy and > applies a local policy of relaxed alignment. > > x.2 Authentication Overrides > > An Authentication Override provides alternate authentication when a message > is acceptable but the DMARC algorithm produces a result of Fail. To ensure > that the exception does not create a vulnerability, the rule should include > at least one verified identifier with a value that indicates the trusted > message source, often coupled with unverified identifiers with specific > values the further narrow scope of the rule. > > x.2.1 Mailing List messages > > Mailing Lists typically add content to the Subject or Body, and replace the > Mail From address, while forwarding a message. As a result, the > RFC5322.From address of the author can no
Re: [dmarc-ietf] DMARCbis WGLC Issue 132 - 5.5.1 and 5.5.2 SHOULD vs MUST (was Another point for SPF advice)
> On Mar 14, 2024, at 4:02 PM, Todd Herr > wrote: > > On Thu, Mar 14, 2024 at 3:25 PM Hector Santos > mailto:40isdg@dmarc.ietf.org>> wrote: >>> On Mar 14, 2024, at 10:09 AM, Todd Herr >>> >> <mailto:40valimail@dmarc.ietf.org>> wrote: >>> To configure SPF for DMARC, the Domain Owner MUST choose a domain to use as >>> the RFC5321.MailFrom domain (i.e., the Return-Path domain) for its mail >>> that aligns with the Author Domain, and then publish an SPF policy in DNS >>> for that domain. The SPF record MUST be constructed at a minimum to ensure >>> an SPF pass verdict for all known sources of mail for the RFC5321.MailFrom >>> domain. >> >> A major consideration, Todd, is receivers will process SPF for SPF without >> DMARC (payload) considerations. IOW, if SPF is a hardfail, we have SMTP >> processors who will not continue to transmit a payload (DATA). >> >> DMARCBis is making a major design presumption receivers will only use SPF as >> a data point for a final DMARC evaluation where a potentially high overhead >> payload was transmitted only to be rejected anyway, > > I don't necessarily think your assertion is true here, or at least I'd submit > that DMARCbis and RFC 7489 aren't approaching this subject any differently. > > Section 10.1 from RFC 7489, titled "Issues Specific to SPF" had two > paragraphs, the second of which reads: > >Some receiver architectures might implement SPF in advance of any >DMARC operations. This means that a "-" prefix on a sender's SPF >mechanism, such as "-all", could cause that rejection to go into >effect early in handling, causing message rejection before any DMARC >processing takes place. Operators choosing to use "-all" should be >aware of this. Yes, I agree. I am only reminding the community SPF can preempt DMARC with a restrictive hardfail policy. Does DMARCBis integrate the tag to delay SPF failures? > > DMARCbis contains the same two paragraphs with no change to the text, other > than the section is now numbered 8.1. > >> >>> In the ticket, I propose the following new text: >>> >>> == >>> To configure DKIM for DMARC, the Domain Owner MUST choose a DKIM-Signing >>> domain (i.e., the d= domain in the DKIM-Signature header) that aligns with >>> the Author Domain. >>> == >> >> In order to maximize security, the Domain Owner is REQUIRED to choose a ….. >> >> Is REQUIRED the same as MUST? I think SHOULD or MUST is fine as long as we >> specify the reason it is required, > > I'm not understanding the comment you're making here, as I don't see the word > "REQUIRED" in anything I wrote. For any protocol, there are “Protocol Requirements,” A MUST or SHOULD is a “Requirement” for proper support, So I just wanted to just note that it can stated another way. Developers need a Requirements Section that allow us to code the logic, Its getting pretty confusing for implementors. — HLS ___ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
Re: [dmarc-ietf] DMARCbis WGLC Issue 132 - 5.5.1 and 5.5.2 SHOULD vs MUST (was Another point for SPF advice)
> On Mar 14, 2024, at 10:09 AM, Todd Herr > wrote: > > > In the ticket, I propose the following replacement text: > > == > Because DMARC relies on SPF [[RFC7208]] and DKIM [[RFC6376], in order to take > full advantage of DMARC, a Domain Owner MUST first ensure that either SPF or > DKIM authentication are properly configured, and SHOULD ensure that both are. +1 > > To configure SPF for DMARC, the Domain Owner MUST choose a domain to use as > the RFC5321.MailFrom domain (i.e., the Return-Path domain) for its mail that > aligns with the Author Domain, and then publish an SPF policy in DNS for that > domain. The SPF record MUST be constructed at a minimum to ensure an SPF pass > verdict for all known sources of mail for the RFC5321.MailFrom domain. A major consideration, Todd, is receivers will process SPF for SPF without DMARC (payload) considerations. IOW, if SPF is a hardfail, we have SMTP processors who will not continue to transmit a payload (DATA). DMARCBis is making a major design presumption receivers will only use SPF as a data point for a final DMARC evaluation where a potentially high overhead payload was transmitted only to be rejected anyway, > In the ticket, I propose the following new text: > > == > To configure DKIM for DMARC, the Domain Owner MUST choose a DKIM-Signing > domain (i.e., the d= domain in the DKIM-Signature header) that aligns with > the Author Domain. > == In order to maximize security, the Domain Owner is REQUIRED to choose a ….. Is REQUIRED the same as MUST? I think SHOULD or MUST is fine as long as we specify the reason it is required, — HLS___ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
Re: [dmarc-ietf] A.5 Issues with ADSP in Operation
> On Mar 9, 2024, at 10:05 AM, Alessandro Vesely wrote: > > Hi, > > as ADSP is historical, perhaps we can strike A5 entirely. If not, we should > at least eliminate bullet 5: > > 5. ADSP has no support for a slow rollout, i.e., no way to configure > a percentage of email on which the Mail Receiver should apply the > policy. This is important for large-volume senders. > > (Alternatively, we could think back about pct=...?) > > If anything, DMARCBis should assist (provide guidance) with ADSP to DMARC migration considerations. There are still folks who don’t believe in DMARC and continue to have an ADSP. ADSP has two basic policies: DISCARDABLE and ALL. ALL means lways signed by anyone. DISCARDABLE means always signed by the Author Domain, DMARCbis continues to use the term “Super ADSP” in section A5. We may be beyond justifications of why DMARC replaced ADSP. Help with migration would be useful. While an ADSP DISCARD policy may translate to a DMARC p=reject, an ADSP ALL policy may not have any DMARC equivalent unless non-alignment was a defined policy (in DMARC) - I don’t there is. All the best, Hector Santos ___ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
Re: [dmarc-ietf] Inconsistencies in DMARC Aggregate Report XML Schema
> On Mar 11, 2024, at 10:33 PM, Neil Anuskiewicz > wrote: > > Wow, the stat on how many domain operators move to enforcing reject policy > sans aggregate reports shocked me. Trust the force, Luke. It should not be a surprise the client/server protocol concept of “email reporting” was always and I still believe is considered a taboo as it can be a form of abuse when not negotiated, requested or solicited. It is an 100% optional feature to provide a reporting address. With DMARC policy publishing, for exploratory reasons only, I have reports sent to an email to newsgroup forum where I can privately review and so far, it has not provided any benefit beyond what is expected. I have advocated for a straight text report but I probably have to write a translator. The current format expects JSON/XML readers. Our wcDMARC verification processor does not have built-in support for reporting. All the best, Hector Santos ___ dmarc mailing list dmarc@ietf.org https://www.ietf.org/mailman/listinfo/dmarc
[jira] [Reopened] (KAFKA-16223) Replace EasyMock and PowerMock with Mockito for KafkaConfigBackingStoreTest
[ https://issues.apache.org/jira/browse/KAFKA-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hector Geraldino reopened KAFKA-16223: -- > Replace EasyMock and PowerMock with Mockito for KafkaConfigBackingStoreTest > --- > > Key: KAFKA-16223 > URL: https://issues.apache.org/jira/browse/KAFKA-16223 > Project: Kafka > Issue Type: Sub-task > Components: connect > Reporter: Hector Geraldino >Assignee: Hector Geraldino >Priority: Minor > Fix For: 3.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (KAFKA-14683) Replace EasyMock and PowerMock with Mockito in WorkerSinkTaskTest
[ https://issues.apache.org/jira/browse/KAFKA-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hector Geraldino resolved KAFKA-14683. -- Reviewer: Greg Harris Resolution: Fixed > Replace EasyMock and PowerMock with Mockito in WorkerSinkTaskTest > - > > Key: KAFKA-14683 > URL: https://issues.apache.org/jira/browse/KAFKA-14683 > Project: Kafka > Issue Type: Sub-task > Components: connect > Reporter: Hector Geraldino >Assignee: Hector Geraldino >Priority: Minor > Fix For: 3.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (KAFKA-14683) Replace EasyMock and PowerMock with Mockito in WorkerSinkTaskTest
[ https://issues.apache.org/jira/browse/KAFKA-14683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hector Geraldino resolved KAFKA-14683. -- Reviewer: Greg Harris Resolution: Fixed > Replace EasyMock and PowerMock with Mockito in WorkerSinkTaskTest > - > > Key: KAFKA-14683 > URL: https://issues.apache.org/jira/browse/KAFKA-14683 > Project: Kafka > Issue Type: Sub-task > Components: connect > Reporter: Hector Geraldino >Assignee: Hector Geraldino >Priority: Minor > Fix For: 3.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Reopened] (KAFKA-16223) Replace EasyMock and PowerMock with Mockito for KafkaConfigBackingStoreTest
[ https://issues.apache.org/jira/browse/KAFKA-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hector Geraldino reopened KAFKA-16223: -- > Replace EasyMock and PowerMock with Mockito for KafkaConfigBackingStoreTest > --- > > Key: KAFKA-16223 > URL: https://issues.apache.org/jira/browse/KAFKA-16223 > Project: Kafka > Issue Type: Sub-task > Components: connect > Reporter: Hector Geraldino >Assignee: Hector Geraldino >Priority: Minor > Fix For: 3.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (KAFKA-16223) Replace EasyMock and PowerMock with Mockito for KafkaConfigBackingStoreTest
[ https://issues.apache.org/jira/browse/KAFKA-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hector Geraldino resolved KAFKA-16223. -- Fix Version/s: 3.8.0 Reviewer: Greg Harris Resolution: Fixed > Replace EasyMock and PowerMock with Mockito for KafkaConfigBackingStoreTest > --- > > Key: KAFKA-16223 > URL: https://issues.apache.org/jira/browse/KAFKA-16223 > Project: Kafka > Issue Type: Sub-task > Components: connect > Reporter: Hector Geraldino >Assignee: Hector Geraldino >Priority: Minor > Fix For: 3.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (KAFKA-16223) Replace EasyMock and PowerMock with Mockito for KafkaConfigBackingStoreTest
[ https://issues.apache.org/jira/browse/KAFKA-16223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hector Geraldino resolved KAFKA-16223. -- Fix Version/s: 3.8.0 Reviewer: Greg Harris Resolution: Fixed > Replace EasyMock and PowerMock with Mockito for KafkaConfigBackingStoreTest > --- > > Key: KAFKA-16223 > URL: https://issues.apache.org/jira/browse/KAFKA-16223 > Project: Kafka > Issue Type: Sub-task > Components: connect > Reporter: Hector Geraldino >Assignee: Hector Geraldino >Priority: Minor > Fix For: 3.8.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
Re: Insert with Jsonb column hangs
On Sat, Mar 9, 2024 at 4:10 PM Adrian Klaver
wrote:
> On 3/9/24 08:00, kuldeep singh wrote:
> > Copy may not work in our scenario since we need to join data from
> > multiple tables & then convert it to json using row_to_json . This
> > json data eventually needs to be stored in a target table .
>
> Per:
>
> https://www.postgresql.org/docs/current/sql-copy.html
>
> "
> COPY { table_name [ ( column_name [, ...] ) ] | ( query ) }
>
> <...>
>
> query
>
> A SELECT, VALUES, INSERT, UPDATE, or DELETE command whose results
> are to be copied. Note that parentheses are required around the query.
>
> For INSERT, UPDATE and DELETE queries a RETURNING clause must be
> provided, and the target relation must not have a conditional rule, nor
> an ALSO rule, nor an INSTEAD rule that expands to multiple statements.
> "
>
> >
> > Will it be better if we break the process into batches of like 10,000
> > rows & insert the data in its individual transactions? Or any other
> > better solution available ?
> >
> > On Sat, Mar 9, 2024 at 9:01 PM hector vass > <mailto:hector.v...@gmail.com>> wrote:
> >
> >
> >
> > On Sat, Mar 9, 2024 at 3:02 PM kuldeep singh
> > mailto:kuldeeparor...@gmail.com>> wrote:
> >
> > Hi,
> >
> > We are inserting data close to 1M record & having a single Jsonb
> > column but query is getting stuck.
> >
> > We are using insert into select * .. , so all the operations are
> > within the DB.
> >
> > If we are running select query individually then it is returning
> > the data in 40 sec for all rows but with insert it is getting
> stuck.
> >
> > PG Version - 15.
> >
> > What could be the problem here ?
> >
> > Regards,
> > KD
> >
> >
> > insert 1M rows especially JSON that can be large, variable in size
> > and stored as blobs and indexed is not perhaps the correct way to do
> > this
> > insert performance will also depend on your tuning. Supporting
> > transactions, users or bulk processing are 3x sides of a compromise.
> > you should perhaps consider that insert is for inserting a few rows
> > into live tables ... you might be better using copy or \copy,
> > pg_dump if you are just trying to replicate a large table
> >
>
> --
> Adrian Klaver
> adrian.kla...@aklaver.com
What Adrian Klaver said ^
discovered even this works...
create view myview as (select row_to_json from mytable);
create table newtable as select * from myview where 1=0;
copy myview to program 'psql mydb postgres -c ''copy newtable from stdin'' '
;
Re: Insert with Jsonb column hangs
copy syntax can include any valid select statement COPY (any valid select statement joining tables and converting it row_to_json) TO 'some_dump_file' or can copy a view CREATE VIEW myview (any valid select statement joining tables and converting it row_to_json); COPY myview TO 'some_dump_file' Regards Hector Vass 07773 352559 On Sat, Mar 9, 2024 at 4:01 PM kuldeep singh wrote: > Copy may not work in our scenario since we need to join data from multiple > tables & then convert it to json using row_to_json . This json data > eventually needs to be stored in a target table . > > Will it be better if we break the process into batches of like 10,000 rows > & insert the data in its individual transactions? Or any other better > solution available ? > > On Sat, Mar 9, 2024 at 9:01 PM hector vass wrote: > >> >> >> On Sat, Mar 9, 2024 at 3:02 PM kuldeep singh >> wrote: >> >>> Hi, >>> >>> We are inserting data close to 1M record & having a single Jsonb column >>> but query is getting stuck. >>> >>> We are using insert into select * .. , so all the operations are within >>> the DB. >>> >>> If we are running select query individually then it is returning the >>> data in 40 sec for all rows but with insert it is getting stuck. >>> >>> PG Version - 15. >>> >>> What could be the problem here ? >>> >>> Regards, >>> KD >>> >> >> insert 1M rows especially JSON that can be large, variable in size and >> stored as blobs and indexed is not perhaps the correct way to do this >> insert performance will also depend on your tuning. Supporting >> transactions, users or bulk processing are 3x sides of a compromise. >> you should perhaps consider that insert is for inserting a few rows into >> live tables ... you might be better using copy or \copy, pg_dump if you are >> just trying to replicate a large table >> >>
Re: Insert with Jsonb column hangs
On Sat, Mar 9, 2024 at 3:02 PM kuldeep singh wrote: > Hi, > > We are inserting data close to 1M record & having a single Jsonb column > but query is getting stuck. > > We are using insert into select * .. , so all the operations are within > the DB. > > If we are running select query individually then it is returning the data > in 40 sec for all rows but with insert it is getting stuck. > > PG Version - 15. > > What could be the problem here ? > > Regards, > KD > insert 1M rows especially JSON that can be large, variable in size and stored as blobs and indexed is not perhaps the correct way to do this insert performance will also depend on your tuning. Supporting transactions, users or bulk processing are 3x sides of a compromise. you should perhaps consider that insert is for inserting a few rows into live tables ... you might be better using copy or \copy, pg_dump if you are just trying to replicate a large table
Fwd: Getting error while upgrading
On Sat, Mar 9, 2024 at 12:18 PM omkar narkar wrote: > Hello Team, > > I am trying to upgrade my edb 10.5 community version to postgres 15.6 > version and while doing this i am getting error regarding OIDS are not > stable across Postgresql version (sys.callback_queue_table.user_data). > Kindly help me to get the solution of this issue. > > Thanks and regards, > Omkar Narkar > Usually get this error if there are composite data types or data types that cannot be translated between 10.5 and 15.6. The clue may be in the error message just before it says 'OIDS are not stable across Postgresql version' You state edb 10.5 community guessing you are using pg_upgrade and going from windows to linux ? I am impressed if you can do that, would you not end up with collation issues? If you are using pg_upgrade what does pg_upgrade --check say I would dump the schema to a sql file pg_dump -s >dumped.sql Then run the sql one command at a time to track down where you are going to have a problem.
Re: creating a subset DB efficiently ?
On Fri, Mar 8, 2024 at 4:22 PM David Gauthier wrote: > Here's the situation > > - The DB contains data for several projects. > - The tables of the DB contain data for all projects (data is not > partitioned on project name or anything like that) > - The "project" identifier (table column) exists in a few "parent" tables > with many child... grandchild,... tables under them connected with foreign > keys defined with "on delete cascade". So if a record in one of the parent > table records is deleted, all of its underlying, dependent records get > deleted too. > - New projects come in, and old ones need to be removed and "archived" in > DBs of their own. So there's a DB called "active_projects" and there's a > DB called "project_a_archive" (identical metadata). > - The idea is to copy the data for project "a" that's in "active_projects" > to the "project_a_arhchive" DB AND delete the project a data out of > "active_projects". > - Leave "project_a_archive" up and running if someone needs to attach to > that and get some old/archived data. > > The brute-force method I've been using is... > 1) pg_dump "active_projects" to a (huge) file then populate > "project_a_archive" using that (I don't have the privs to create database, > IT creates an empty one for me, so this is how I do it). > 2) go into the "project_a_archive" DB and run... "delete from par_tbl_1 > where project <> 'a' ", "delete from par_tbl_2 where project <> 'a' ", > etc... leaving only project "a" data in the DB. > 3) go into the "active_projects" DB and "delete from par_tbl_1 where > project = 'a' ", etc... removing project "a" from the "active_projects DB. > > Ya, not very elegant, it takes a long time and it takes a lot of > resources. So I'm looking for ideas on how to do this better. > > Related question... > The "delete from par_tbl_a where project <> 'a' " is taking forever. I > fear it's because it's trying to journal everything in case I want to > rollback. But this is just in the archive DB and I don't mind taking the > risk if I can speed this up outside of a transaction. How can I run a > delete command like this without the rollback recovery overhead ? > >(I don't have the privs to create database, IT creates an empty one for me, so this is how I do it). That's a shame. You can do something similar with tablespaces Template your existing schema to create a new schema for the project (pg_dump -s) Create tablespace for this new project and schema You can then move the physical tablespace to cheaper disk and use symbolic links or... archive and/or back it up at the schema level with pg_dump -n ...as long as you don't put anything in the public schema all you are really sharing is roles otherwise a bit like a separate database
