Bug#1069679: Debian Bugs information: logs for Bug#1069679
Hello Mike, On Fri, 24 May 2024 at 08:57, Mike Gabriel wrote: > If noone plans to fix Ofono in Debian within the next 1-2 weeks, I'd > like to do a team upload. In that case, could any of you give me > access to > https://salsa.debian.org/telepathy-team (or just the ofono repo in there). I tried but I do not have enough permissions to add you. You'll need Emilio or Laurent for that. Regards -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
Bug#1069679: Debian Bugs information: logs for Bug#1069679
Hello Mike, On Fri, 24 May 2024 at 08:57, Mike Gabriel wrote: > If noone plans to fix Ofono in Debian within the next 1-2 weeks, I'd > like to do a team upload. In that case, could any of you give me > access to > https://salsa.debian.org/telepathy-team (or just the ofono repo in there). I tried but I do not have enough permissions to add you. You'll need Emilio or Laurent for that. Regards -- Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.
[plasma-pa] [Bug 442379] When using Natural Scrolling, scrolling direction to change volume is inverted
https://bugs.kde.org/show_bug.cgi?id=442379 --- Comment #13 from Hector Martin --- > I find the new behaviour quite unnatural after using it the way it was for so > long. That sounds like "I got used to the old way even though it didn't make sense", which isn't a terribly good reason not to fix it. :) > Also since the sliders are perpendicular to the direction of motion, I don't > believe there really is a "correct" way for them to respond. Other systems > have likely preferred to keep their audio sliders vertical for this same > reason. If you're implying that for a vertical volume slider then "scroll up" on a trackpad should in fact be volume up (i.e. the current behavior after this bug was fixed) *then* it stands to reason that the same should be true for a horizontal slider as, despite there being no "correct" spatial mapping due to the axis being different, the "volume up" metaphor still holds. Indeed, this same rationale applies to non-spatial cases like the Plasma system tray volume icon itself, which simply displays a varying number of "waves". In general, non-scrollbar linear widgets on desktop environments (and, indeed, largely so in the physical world) have always used the "positive right / up" convention, so it stands to reason that they would be mapped this way. That said, I just noticed that horizontal sliders and indeed the tray icon itself *also* respond to horizontal trackpad movement, which is also excellent as it matches the direction of the slider. As I said in my earlier comment, the only reason we ended up in this mess to begin with is because scroll wheels were *specifically* intended for the use case of viewport scrolling first (which is inverted vs. the content), then widgets have always tried to use "natural scrolling" by inverting the scroll direction at the widget level, and then finally "natural scrolling" for trackpads was originally implemented as a hack that inverted all scrolling regardless of scroll target, making the widgets move backwards unintentionally. People might have gotten used to that, but I really doubt there is a strong argument to be made that this behavior is, in any way, intuitive. -- You are receiving this mail because: You are watching all bug changes.
[jira] [Updated] (HUDI-7782) Task not serializable due to DynamoDBBasedLockProvider and HiveMetastoreBasedLockProvider in clean action
[ https://issues.apache.org/jira/browse/HUDI-7782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] hector updated HUDI-7782: - Description: Caused by: java.io.NotSerializableException: org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider Serialization stack: - object not serializable (class: org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider, value: org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider@1355d2ca) like HUDI-3638, only fixed the issue of ZookeeperbasedLockProvider. was: Caused by: java.io.NotSerializableException: org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider Serialization stack: - object not serializable (class: org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider, value: org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider@1355d2ca) > Task not serializable due to DynamoDBBasedLockProvider and > HiveMetastoreBasedLockProvider in clean action > - > > Key: HUDI-7782 > URL: https://issues.apache.org/jira/browse/HUDI-7782 > Project: Apache Hudi > Issue Type: Bug > Reporter: hector >Priority: Major > > Caused by: java.io.NotSerializableException: > org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider > Serialization stack: > - object not serializable (class: > org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider, value: > org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider@1355d2ca) > > like HUDI-3638, only fixed the issue of ZookeeperbasedLockProvider. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (HUDI-7782) Task not serializable due to DynamoDBBasedLockProvider and HiveMetastoreBasedLockProvider in clean action
hector created HUDI-7782: Summary: Task not serializable due to DynamoDBBasedLockProvider and HiveMetastoreBasedLockProvider in clean action Key: HUDI-7782 URL: https://issues.apache.org/jira/browse/HUDI-7782 Project: Apache Hudi Issue Type: Bug Reporter: hector Caused by: java.io.NotSerializableException: org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider Serialization stack: - object not serializable (class: org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider, value: org.apache.hudi.hive.transaction.lock.HiveMetastoreBasedLockProvider@1355d2ca) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[Bug 2066061] Re: Please merge paramiko 3.4.0-1 into Oracular
The folowing Ubuntu changes are dropped: - SECURITY UPDATE: Prefix truncation attack on BPP - debian/patches/CVE-2023-48795-*.patch: implement strict key exchange. - CVE-2023-48795 These changes are backports from upstream and the new debian version contains these commits. Per consequence, no need anymore to apply them - debian/patches/remove_six.patch This patch is dropped since it is in upstream - debian/patches/fix_test_on_armhf.patch This patch is dropped because the file tests/test_transport.py is changed in the new version and this patch is not application neither necessary ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-48795 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066061 Title: Please merge paramiko 3.4.0-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2066061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066061] Re: Please merge paramiko 3.4.0-1 into Oracular
The merge request : https://code.launchpad.net/~hectorcao/ubuntu/+source/paramiko/+git/paramiko/+merge/466111 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2066061 Title: Please merge paramiko 3.4.0-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2066061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066061] Re: Please merge paramiko 3.4.0-1 into Oracular
** Changed in: paramiko (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: paramiko (Ubuntu) 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/2066061 Title: Please merge paramiko 3.4.0-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2066061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2066061] [NEW] Please merge paramiko 3.4.0-1 into Oracular
Public bug reported: paramiko Fri May 3 21:50:49 2024 Below now follows the report of the automated merge of the Ubuntu changes to the paramiko source package against the new Debian version. Here are the particulars of the three versions of paramiko that were chosen for the merge. The base is the newest version that is a common ancestor of both the Ubuntu and Debian packages. It may be of a different upstream version, but that's not usually a problem. The files are the source package itself, and the patch from the common base to that version. base: 2.12.0-2 paramiko_2.12.0-2.dsc paramiko_2.12.0.orig.tar.xz paramiko_2.12.0-2.debian.tar.xz ubuntu: 2.12.0-2ubuntu4 paramiko_2.12.0-2ubuntu4.dsc paramiko_2.12.0.orig.tar.xz paramiko_2.12.0-2ubuntu4.debian.tar.xz base -> ubuntu paramiko_2.12.0-2ubuntu4.patch debian: 3.4.0-1 paramiko_3.4.0-1.dsc paramiko_3.4.0.orig.tar.xz paramiko_3.4.0-1.debian.tar.xz base -> debian paramiko_3.4.0-1.patch Generated Result Due to conflict or error, it was not possible to automatically create a source package. Instead the result of the merge has been placed into the following tar file which you will need to turn into a source package once the problems have been resolved. paramiko_3.4.0-1ubuntu1.src.tar.gz Conflicts = In one or more cases, there were different changes made in both Ubuntu and Debian to the same file; these are known as conflicts. It is not possible for these to be automatically resolved, so this source needs human attention. Those files marked with 'C ' contain diff3 conflict markers, which can be resolved using the text editor of your choice. Those marked with 'C*' could not be merged that way, so you will find .UBUNTU and .DEBIAN files instead and should choose one of them or a combination of both, moving it to the real filename and deleting the other. C debian/patches/series ** Affects: paramiko (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/2066061 Title: Please merge paramiko 3.4.0-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/paramiko/+bug/2066061/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065883] Re: Please merge wget 1.24.5-1 into Oracular
The merge request : https://code.launchpad.net/~hectorcao/ubuntu/+source/wget/+git/wget/+merge/466063 The new package has been built and available at : https://launchpad.net/~hectorcao/+archive/ubuntu/lp2065883 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065883 Title: Please merge wget 1.24.5-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2065883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065883] Re: Please merge wget 1.24.5-1 into Oracular
** Changed in: wget (Ubuntu) Assignee: (unassigned) => Hector CAO (hectorcao) ** Changed in: wget (Ubuntu) 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/2065883 Title: Please merge wget 1.24.5-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2065883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2065883] [NEW] Please merge wget 1.24.5-1 into Oracular
Public bug reported: Debian has new release of wget at version 1.24.5-1 Merge this new release to Oracular ** Affects: wget (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/2065883 Title: Please merge wget 1.24.5-1 into Oracular To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2065883/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[jira] [Comment Edited] (FLINK-35331) Download links for binary releases are displayed as source releases on website
[
https://issues.apache.org/jira/browse/FLINK-35331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846933#comment-17846933
]
Hector Sanchez edited comment on FLINK-35331 at 5/16/24 12:22 PM:
--
Added [PR#742|https://github.com/apache/flink-web/pull/742] with fix.
The shortcode {{flink_download}} used to create the download links had the
property {{source_release_url}} mandatory. I just added a conditional so no
need to have that property anymore. This way we can have only the
{{binary_release_url}} for those binary only downloads.
I have updated the
`[additional_components.yml|https://github.com/apache/flink-web/pull/742/files#diff-45fd031d774cda3e995f0ebe71de328688f561f75000a4d0a234fccd72bd2151]`
file update the hadoop links. I haven't found any other download links with
binary only. Please report if there is any other missing
was (Author: JIRAUSER305463):
Added [PR#742|https://github.com/apache/flink-web/pull/742] with fix.
The shortcode `flink_download` used to create the download links had the
property `source_release_url` mandatory. I just added a conditional so no need
to have that property anymore. This way we can have only the
`binary_release_url` for those binary only downloads.
I have updated the
`[additional_components.yml|https://github.com/apache/flink-web/pull/742/files#diff-45fd031d774cda3e995f0ebe71de328688f561f75000a4d0a234fccd72bd2151]`
file update the hadoop links. I haven't found any other download links with
binary only. Please report if there is any other missing
> Download links for binary releases are displayed as source releases on website
> --
>
> Key: FLINK-35331
> URL: https://issues.apache.org/jira/browse/FLINK-35331
> Project: Flink
> Issue Type: Bug
> Components: Project Website
>Reporter: Xintong Song
>Priority: Major
> Labels: pull-request-available
>
> Take Pre-bundled Hadoop as examples. The content for downloading are binary
> releases, while the link is displayed as "Pre-bundled Hadoop 2.x.y Source
> Release (asc, sha512)". The problem is caused by misusing
> `source_release_[url|asc_url|sha512_url]` for binary contents in the
> corresponding [yaml
> file.|https://github.com/apache/flink-web/blob/asf-site/docs/data/additional_components.yml]
> There are many similar cases in the webpage.
> And a relevant issues is that, some source releases are displayed as "XXX
> Source Release Source Release", due to including "Source Release" in the
> `name` field of the corresponding yaml file.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (FLINK-35331) Download links for binary releases are displayed as source releases on website
[ https://issues.apache.org/jira/browse/FLINK-35331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17846933#comment-17846933 ] Hector Sanchez commented on FLINK-35331: Added [PR#742|https://github.com/apache/flink-web/pull/742] with fix. The shortcode `flink_download` used to create the download links had the property `source_release_url` mandatory. I just added a conditional so no need to have that property anymore. This way we can have only the `binary_release_url` for those binary only downloads. I have updated the `[additional_components.yml|https://github.com/apache/flink-web/pull/742/files#diff-45fd031d774cda3e995f0ebe71de328688f561f75000a4d0a234fccd72bd2151]` file update the hadoop links. I haven't found any other download links with binary only. Please report if there is any other missing > Download links for binary releases are displayed as source releases on website > -- > > Key: FLINK-35331 > URL: https://issues.apache.org/jira/browse/FLINK-35331 > Project: Flink > Issue Type: Bug > Components: Project Website >Reporter: Xintong Song >Priority: Major > Labels: pull-request-available > > Take Pre-bundled Hadoop as examples. The content for downloading are binary > releases, while the link is displayed as "Pre-bundled Hadoop 2.x.y Source > Release (asc, sha512)". The problem is caused by misusing > `source_release_[url|asc_url|sha512_url]` for binary contents in the > corresponding [yaml > file.|https://github.com/apache/flink-web/blob/asf-site/docs/data/additional_components.yml] > There are many similar cases in the webpage. > And a relevant issues is that, some source releases are displayed as "XXX > Source Release Source Release", due to including "Source Release" in the > `name` field of the corresponding yaml file. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[Ietf-dkim] Re: [Dcrup] [standards] [Editorial Errata Reported] RFC8463 (7930)
> > |Because that's not actually accurate, due to the inclusion of the digest > |OID in the signature payload in the "single" primitive. > > ...but the above says "two hashes". But despite that. > An Ed25519 sign operation alone creates three SHA-512 digests > which are incorporated into several further calculations. Whereas > for RSA it is, to the best of my knowledge, crucial to let it pass > over as few bytes as possible (for encryption as such i think > OpenSSL will refuse to do so after a certain limit), for EC with > its embedded digests it may be more expensive but even beneficial > to push more data rounds onto the embedded digests. > So maybe, and in hindsight to the RFC that i would try to publish > in fall if i am allowed to and if the email giants still have not > moved towards this RFC 8463, it might make sense to adjust the > data-hash in that it may come from hash-alg or be included via > sig-alg. > > --steffen I don’t wish to oversimplify here, but I wonder if the confusion is with the idea that in order to support RFC8463, a complaint implementation would have to sign two DKIM signatures for backward compatibility. One DKIM signature using SHA256 and a second signature using Ed25519. No one will support exclusively Ed25519 unless dealing with highly direct 1 to 1 comm I/O with a permission-based system. In other words, supporting this crypto enhancement requires a high overhead of two signatures, The ignorant RFC8463 system (the majority) is not ready for this. One SHA256 signature is sufficient, I would not Ed25519 provides smaller keys that are more supportive by DNS Zone Managers. All the best, Hector Santos ___ Ietf-dkim mailing list -- ietf-dkim@ietf.org To unsubscribe send an email to ietf-dkim-le...@ietf.org
Re:[VOTE] KIP-1028: Docker Official Image for Apache Kafka
+1 (non-binding) Thanks Vedarth! From: dev@kafka.apache.org At: 05/14/24 12:13:14 UTC-4:00To: dev@kafka.apache.org Subject: [VOTE] KIP-1028: Docker Official Image for Apache Kafka Hi everyone, I'd like to call a vote on KIP-1028 which aims to introduce a JVM based Docker Official Image (DOI) for Apache Kafka. KIP - https://cwiki.apache.org/confluence/display/KAFKA/KIP-1028%3A+Docker+Official+Im age+for+Apache+Kafka Discussion thread - https://lists.apache.org/thread/6vvwx173jcbgj6vqoq6bo8c0k0ntym0w Thanks and regards, Vedarth
[dmarc-ietf] Re: WG Action: Formed Mail Maintenance (mailmaint)
Thanks. I am subscribed. Based on the written charter, is re-introducing then ESMTP add-on, https://datatracker.ietf.org/doc/html/draft-santos-smtpgrey-02 Reasonable? Many years of operation, the ultimate two questions are: 1) Do greylistng servers support responses to drive greylisted clients? and 2) Do rermote clients honor the advanced response for Retry Times? The above is an example only. Another is ATPS re-introduction for a DMARC-based world. All the best, Hector Santos > On May 10, 2024, at 1:53 PM, Murray S. Kucherawy wrote: > > FYI > > -- Forwarded message - > From: IESG Secretary <mailto:iesg-secret...@ietf.org>> > Date: Thu, May 9, 2024 at 1:01 PM > Subject: WG Action: Formed Mail Maintenance (mailmaint) > To: IETF Announcement List <mailto:ietf-annou...@ietf.org>> > Cc: mailto:i...@ietf.org>>, <mailto:mailmaint-cha...@ietf.org>>, <mailto:mailma...@ietf.org>> > > > A new IETF WG has been formed in the Applications and Real-Time Area. For > additional information, please contact the Area Directors or the WG Chair. > > Mail Maintenance (mailmaint) > --- > Current status: Proposed WG > > Chairs: > Kenneth Murchison mailto:mu...@fastmail.com>> > > Assigned Area Director: > Murray Kucherawy mailto:superu...@gmail.com>> > > Applications and Real-Time Area Directors: > Murray Kucherawy mailto:superu...@gmail.com>> > Orie Steele > > Mailing list: > Address: mailma...@ietf.org <mailto:mailma...@ietf.org> > To subscribe: https://www.ietf.org/mailman/listinfo/mailmaint > Archive: https://mailarchive.ietf.org/arch/browse/mailmaint/ > > Group page: https://datatracker.ietf.org/group/mailmaint/ > > Charter: https://datatracker.ietf.org/doc/charter-ietf-mailmaint/ > > Internet Messaging (“email”) is one of the oldest applications still > supported by the IETF. It consists of numerous layers and extensions that > support the robust construction, transport, retrieval, and interpretation of > messages. > > (For the purposes of this charter, “email” starts in RFC 5321 which covers > transport and RFC 5322 which covers message format, and extends into > specifications based on those documents and their antecedents. It also > includes related protocols such as IMAP [RFC 9051] and JMAP [RFC 8620, et > seq].) > > >From time to time, new work in the email space is brought to the IETF for > consideration and development. Where there is enough critical mass to create > a working group to develop and publish the work, this is the preferred case. > More often, however, a proposal is brought that lacks enough critical mass to > independently support chartering of a working group, but would still be > useful to publish as a standard. Such projects must then either seek the > assent of an Area Director willing to sponsor it as a standards track > document, or support via the Independent Stream Editor (ISE) without > standards track status. > > The MAILMAINT (“Mail Maintenance”) working group will consider projects in > the email space that are too small to warrant construction of a dedicated > working group. This will take advantage of a common community to consider > these proposals rather than forming a series of disparate but related > communities. > > Work proposed for MAILMAINT may arrive via direct proposals, or it may be > referred via one or more DISPATCH-style working groups. Recorded Calls for > Adoption are required for all work proposals. > > Proponents of work that is not taken up within the IETF may, of course, > decide to bring their proposal to the Independent Stream. The working group > should discuss such proposals with the ISE and share the results of the > working group’s consideration. > > Further, MAILMAINT will observe the following constraints when considering > the adoption of new work directly: > > * Prior to accepting any Standards Track document for development, there must > be a commitment to implement the resulting proposed standard from at least > two independent parties, as recorded on a related IETF mailing list. > > * When deciding to send any Standards Track work to the IESG, there must > first be produced a report documenting at least two (preferably more) > independent implementations with at least partial interoperation based on the > developed specification. > > * The above constraints do not apply to documents that are not intended for > the Standards Track. > > * Chartering of a dedicated working group with a custom charter is strongly > preferred when engaging any work that updates any base email do
[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.
