Bug#1051355: Processed: your mail

[Leandro Cunha]

On Mon, Sep 11, 2023 at 4:10 PM Andres Salomon  wrote:
>
>
>
> On Mon, Sep 11 2023 at 03:27:30 PM -03:00:00, Leandro Cunha 
>  wrote:
>
> On Mon, Sep 11, 2023 at 4:07 AM Andres Salomon  wrote:
>
> So apparently it's already fixed in sid and trixie: 
> https://tracker.debian.org/news/1454349/accepted-llvm-toolchain-16-11606-11-source-into-unstable/
>  Bug didn't get closed because of the missing "(closes: " in that changelog 
> entry. I'll push the clang-16 stuff to git so you can give it a test build on 
> ppc. On Mon, Sep 11 2023 at 12:37:39 AM -05:00:00, Timothy Pearson 
>  wrote: For 16 to work we'll need the Debian 
> clang team to include this patchset: https://reviews.llvm.org/D158066 Any 
> chance of that happening? - Original Message - From: "Andres Salomon" 
>  To: "Leandro Cunha" , 
> 1051...@bugs.debian.org Cc: "Timothy Pearson" 
>  Sent: Sunday, September 10, 2023 11:43:18 PM 
> Subject: Re: Bug#1051355: Processed: your mail Alright, I built 117 w/ 
> clang-16 on sid and it doesn't segfault. Same exact build but with clang-14 
> segfaults. Timothy, did you ever get the ppc64 issues with clang >= 15 
> squared away? It's looking like I'm going to need to upload a build with 
> clang-16. On Sun, Sep 10 2023 at 03:07:29 PM -03:00:00, Leandro Cunha 
>  wrote: Hi, Em dom., 10 de set. de 2023 15:01, 
> Andres Salomon mailto:dilin...@queued.net>> escreveu: 
> Unfortunately 117 *also* segfaults on sid. I'm tempted to try a newer clang, 
> but probably not 15 since debian's planning to remove it. 16, I guess? Arch 
> is already with Clang 16 and I tested Chromium 117 in a vm that I installed 
> here and it was working normally.
>
> So we already have this version on unstable? I saw it in experimental. 
> https://metadata.ftp-master.debian.org/changelogs//main/l/llvm-defaults/llvm-defaults_0.57~exp4_changelog
>
>
> That's just the defaults package, which we don't really care about. Because 
> we're dealing with different compilers across different distributions, we're 
> hardcoding the specific clang version for each distribution's build.

Ah yes, I see, there is a user on GitHub who compiles Chromium for
Ubuntu, Debian and Windows operating systems with Clang/LLVM. I also
tested the .deb package it offers in version 117 and it worked. But of
course I had to delete the package distributed by Debian. And I also
didn't find any segmentation fault bug reports in version 116 in my
search. In this sense, research was carried out on other distributions
and their bug tracker. But I noticed that this problem sometimes
occurs considering the links inserted here.

https://groups.google.com/a/chromium.org/g/chromium-bugs/search?q=segmentation%20fault
https://bugs.chromium.org/p/chromium/issues/detail?id=48168
https://bbs.archlinux.org/viewtopic.php?id=151904
https://bugs.chromium.org/p/chromium/issues/list?q=segmentation%20fault=2
https://groups.google.com/a/chromium.org/g/chromium-bugs/c/wolJA_Ma4ZE
https://github.com/RobRich999/Chromium_Clang

-- 
Cheers,
Leandro Cunha

Bug#1051355: Processed: your mail

[Andres Salomon]

On Mon, Sep 11 2023 at 03:27:30 PM -03:00:00, Leandro Cunha 
 wrote:
On Mon, Sep 11, 2023 at 4:07 AM Andres Salomon <mailto:dilin...@queued.net>> wrote:


 So apparently it's already fixed in sid and trixie:

 
<https://tracker.debian.org/news/1454349/accepted-llvm-toolchain-16-11606-11-source-into-unstable/>


 Bug didn't get closed because of the missing "(closes: " in that 
changelog entry. I'll push the clang-16 stuff to git so you can give 
it a test build on ppc.


 On Mon, Sep 11 2023 at 12:37:39 AM -05:00:00, Timothy Pearson 
<mailto:tpear...@raptorengineering.com>> wrote:


 For 16 to work we'll need the Debian clang team to include this 
patchset: <https://reviews.llvm.org/D158066> Any chance of that 
happening? - Original Message -


 From: "Andres Salomon" <mailto:dilin...@queued.net>> To: "Leandro Cunha" 
mailto:leandrocunha...@gmail.com>>, 
1051...@bugs.debian.org <mailto:1051...@bugs.debian.org> Cc: 
"Timothy Pearson" <mailto:tpear...@raptorengineering.com>> Sent: Sunday, September 10, 
2023 11:43:18 PM Subject: Re: Bug#1051355: Processed: your mail


 Alright, I built 117 w/ clang-16 on sid and it doesn't segfault. 
Same exact build but with clang-14 segfaults. Timothy, did you ever 
get the ppc64 issues with clang >= 15 squared away? It's looking 
like I'm going to need to upload a build with clang-16. On Sun, Sep 
10 2023 at 03:07:29 PM -03:00:00, Leandro Cunha 
mailto:leandrocunha...@gmail.com>> wrote:


 Hi, Em dom., 10 de set. de 2023 15:01, Andres Salomon 
mailto:dilin...@queued.net> 
<<mailto:dilin...@queued.net>>> escreveu:


 Unfortunately 117 *also* segfaults on sid. I'm tempted to try a 
newer clang, but probably not 15 since debian's planning to remove 
it. 16, I guess?


 Arch is already with Clang 16 and I tested Chromium 117 in a vm 
that I installed here and it was working normally.


So we already have this version on unstable? I saw it in experimental.
<https://metadata.ftp-master.debian.org/changelogs//main/l/llvm-defaults/llvm-defaults_0.57~exp4_changelog>



That's just the defaults package, which we don't really care about. 
Because we're dealing with different compilers across different 
distributions, we're hardcoding the specific clang version for each 
distribution's build.

Bug#1051355: Processed: your mail

[Leandro Cunha]

On Mon, Sep 11, 2023 at 4:07 AM Andres Salomon  wrote:
>
> So apparently it's already fixed in sid and trixie:
>
> https://tracker.debian.org/news/1454349/accepted-llvm-toolchain-16-11606-11-source-into-unstable/
>
> Bug didn't get closed because of the missing "(closes: " in that changelog 
> entry. I'll push the clang-16 stuff to git so you can give it a test build on 
> ppc.
>
> On Mon, Sep 11 2023 at 12:37:39 AM -05:00:00, Timothy Pearson 
>  wrote:
>
> For 16 to work we'll need the Debian clang team to include this patchset: 
> https://reviews.llvm.org/D158066 Any chance of that happening? - Original 
> Message -
>
> From: "Andres Salomon"  To: "Leandro Cunha" 
> , 1051...@bugs.debian.org Cc: "Timothy Pearson" 
>  Sent: Sunday, September 10, 2023 11:43:18 PM 
> Subject: Re: Bug#1051355: Processed: your mail
>
> Alright, I built 117 w/ clang-16 on sid and it doesn't segfault. Same exact 
> build but with clang-14 segfaults. Timothy, did you ever get the ppc64 issues 
> with clang >= 15 squared away? It's looking like I'm going to need to upload 
> a build with clang-16. On Sun, Sep 10 2023 at 03:07:29 PM -03:00:00, Leandro 
> Cunha  wrote:
>
> Hi, Em dom., 10 de set. de 2023 15:01, Andres Salomon  <mailto:dilin...@queued.net>> escreveu:
>
> Unfortunately 117 *also* segfaults on sid. I'm tempted to try a newer clang, 
> but probably not 15 since debian's planning to remove it. 16, I guess?
>
> Arch is already with Clang 16 and I tested Chromium 117 in a vm that I 
> installed here and it was working normally.

So we already have this version on unstable? I saw it in experimental.
https://metadata.ftp-master.debian.org/changelogs//main/l/llvm-defaults/llvm-defaults_0.57~exp4_changelog

-- 
Cheers,
Leandro Cunha

Bug#1051355: Processed: your mail

[Andres Salomon]

So apparently it's already fixed in sid and trixie:

<https://tracker.debian.org/news/1454349/accepted-llvm-toolchain-16-11606-11-source-into-unstable/>

Bug didn't get closed because of the missing "(closes: " in that 
changelog entry. I'll push the clang-16 stuff to git so you can give it 
a test build on ppc.


On Mon, Sep 11 2023 at 12:37:39 AM -05:00:00, Timothy Pearson 
 wrote:
For 16 to work we'll need the Debian clang team to include this 
patchset:


<https://reviews.llvm.org/D158066>

Any chance of that happening?

- Original Message -
 From: "Andres Salomon" <mailto:dilin...@queued.net>>
 To: "Leandro Cunha" <mailto:leandrocunha...@gmail.com>>, 1051...@bugs.debian.org 
<mailto:1051...@bugs.debian.org>
 Cc: "Timothy Pearson" <mailto:tpear...@raptorengineering.com>>

 Sent: Sunday, September 10, 2023 11:43:18 PM
 Subject: Re: Bug#1051355: Processed: your mail


 Alright, I built 117 w/ clang-16 on sid and it doesn't segfault. 
Same

 exact build but with clang-14 segfaults.

 Timothy, did you ever get the ppc64 issues with clang >= 15 squared
 away? It's looking like I'm going to need to upload a build with
 clang-16.

 On Sun, Sep 10 2023 at 03:07:29 PM -03:00:00, Leandro Cunha
 mailto:leandrocunha...@gmail.com>> 
wrote:

 Hi,

 Em dom., 10 de set. de 2023 15:01, Andres Salomon
 mailto:dilin...@queued.net> 
<<mailto:dilin...@queued.net>>> escreveu:

 Unfortunately 117 *also* segfaults on sid.

 I'm tempted to try a newer clang, but probably not 15 since 
debian's

 planning to remove it. 16, I guess?


 Arch is already with Clang 16 and I tested Chromium 117 in a vm 
that

 I installed here and it was working normally.

Bug#1051355: Processed: your mail

[Leandro Cunha]

On Mon, Sep 11, 2023 at 2:37 AM Timothy Pearson
 wrote:
>
> For 16 to work we'll need the Debian clang team to include this patchset:
>
> https://reviews.llvm.org/D158066
>
> Any chance of that happening?
>
> - Original Message -
> > From: "Andres Salomon" 
> > To: "Leandro Cunha" , 1051...@bugs.debian.org
> > Cc: "Timothy Pearson" 
> > Sent: Sunday, September 10, 2023 11:43:18 PM
> > Subject: Re: Bug#1051355: Processed: your mail
>
> > Alright, I built 117 w/ clang-16 on sid and it doesn't segfault. Same
> > exact build but with clang-14 segfaults.
> >
> > Timothy, did you ever get the ppc64 issues with clang >= 15 squared
> > away? It's looking like I'm going to need to upload a build with
> > clang-16.
> >
> > On Sun, Sep 10 2023 at 03:07:29 PM -03:00:00, Leandro Cunha
> >  wrote:
> >> Hi,
> >>
> >> Em dom., 10 de set. de 2023 15:01, Andres Salomon
> >> mailto:dilin...@queued.net>> escreveu:
> >>> Unfortunately 117 *also* segfaults on sid.
> >>>
> >>> I'm tempted to try a newer clang, but probably not 15 since debian's
> >>> planning to remove it. 16, I guess?
> >>
> >> Arch is already with Clang 16 and I tested Chromium 117 in a vm that
> >> I installed here and it was working normally.

Clang migration will have to go through a transition, as it may still
break some packages and this requires care.
Which could still delay the release of new versions of Chromium.

Example: https://lists.debian.org/debian-release/2019/12/msg00402.html

-- 
Cheers,
Leandro Cunha

Bug#1051355: Processed: your mail

[Timothy Pearson]

For 16 to work we'll need the Debian clang team to include this patchset:

https://reviews.llvm.org/D158066

Any chance of that happening?

- Original Message -
> From: "Andres Salomon" 
> To: "Leandro Cunha" , 1051...@bugs.debian.org
> Cc: "Timothy Pearson" 
> Sent: Sunday, September 10, 2023 11:43:18 PM
> Subject: Re: Bug#1051355: Processed: your mail

> Alright, I built 117 w/ clang-16 on sid and it doesn't segfault. Same
> exact build but with clang-14 segfaults.
> 
> Timothy, did you ever get the ppc64 issues with clang >= 15 squared
> away? It's looking like I'm going to need to upload a build with
> clang-16.
> 
> On Sun, Sep 10 2023 at 03:07:29 PM -03:00:00, Leandro Cunha
>  wrote:
>> Hi,
>> 
>> Em dom., 10 de set. de 2023 15:01, Andres Salomon
>> mailto:dilin...@queued.net>> escreveu:
>>> Unfortunately 117 *also* segfaults on sid.
>>> 
>>> I'm tempted to try a newer clang, but probably not 15 since debian's
>>> planning to remove it. 16, I guess?
>> 
>> Arch is already with Clang 16 and I tested Chromium 117 in a vm that
>> I installed here and it was working normally.

Bug#1051355: Processed: your mail

[Andres Salomon]

Alright, I built 117 w/ clang-16 on sid and it doesn't segfault. Same 
exact build but with clang-14 segfaults.


Timothy, did you ever get the ppc64 issues with clang >= 15 squared 
away? It's looking like I'm going to need to upload a build with 
clang-16.


On Sun, Sep 10 2023 at 03:07:29 PM -03:00:00, Leandro Cunha 
 wrote:

Hi,

Em dom., 10 de set. de 2023 15:01, Andres Salomon 
mailto:dilin...@queued.net>> escreveu:

Unfortunately 117 *also* segfaults on sid.

I'm tempted to try a newer clang, but probably not 15 since debian's 
planning to remove it. 16, I guess?


Arch is already with Clang 16 and I tested Chromium 117 in a vm that 
I installed here and it was working normally.

Bug#1051355: Processed: your mail

[Leandro Cunha]

Hi,

Em dom., 10 de set. de 2023 15:01, Andres Salomon 
escreveu:

> Unfortunately 117 *also* segfaults on sid.
>
> I'm tempted to try a newer clang, but probably not 15 since debian's
> planning to remove it. 16, I guess?
>

Arch is already with Clang 16 and I tested Chromium 117 in a vm that I
installed here and it was working normally.

>

Bug#1051355: Processed: your mail

[Andres Salomon]

Unfortunately 117 *also* segfaults on sid.

I'm tempted to try a newer clang, but probably not 15 since debian's 
planning to remove it. 16, I guess?


On Fri, Sep 8 2023 at 05:36:17 PM -03:00:00, Leandro Cunha 
 wrote:

Hi,

On Fri, Sep 8, 2023 at 4:39 PM Andres Salomon > wrote:




 On Fri, Sep 8 2023 at 03:31:37 PM -03:00:00, Leandro Cunha 
mailto:leandrocunha...@gmail.com>> wrote:


 Hi, On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System 
mailto:ow...@bugs.debian.org>> wrote:


 Processing commands for cont...@bugs.debian.org 
: > affects 1051355 phpsysinfo 
phpldapadmin jquery-timepicker Bug #1051355 [chromium] chromium: 
Segmentation fault Added indication that 1051355 affects phpsysinfo, 
phpldapadmin, and jquery-timepicker > stop Stopping processing here. 
Please contact me if you need assistance. -- 1051355: 
 Debian 
Bug Tracking System Contact ow...@bugs.debian.org 
 with problems


 Apparently this should have been fixed in version 117.0.5938.48-1, 
if you want to release this version in beta stage as a distro they 
are making which is Arch and we can test it on Debian. 
 


 --
 Cheers, Leandro Cunha



 Do you have a crbug or commit or something that fixes it? I haven't 
started on 117 yet, and I also haven't really had time to debug this 
sid-specific 116 crash (other than building with downgraded packages 
from 9/1 and still getting the crash). This was a bad week for 
finding free time.


 Tim, I don't suppose you've looked at 117 yet? There's an early 
release out.





This version is expected to be released on September 12th and we can
wait. I believe it must have also been compiled for Linux with the
current changes.


--
Cheers,
Leandro Cunha

Bug#1051355: Processed: your mail

[Leandro Cunha]

Hi,

On Fri, Sep 8, 2023 at 4:39 PM Andres Salomon  wrote:
>
>
>
> On Fri, Sep 8 2023 at 03:31:37 PM -03:00:00, Leandro Cunha 
>  wrote:
>
> Hi, On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System 
>  wrote:
>
> Processing commands for cont...@bugs.debian.org: > affects 1051355 phpsysinfo 
> phpldapadmin jquery-timepicker Bug #1051355 [chromium] chromium: Segmentation 
> fault Added indication that 1051355 affects phpsysinfo, phpldapadmin, and 
> jquery-timepicker > stop Stopping processing here. Please contact me if you 
> need assistance. -- 1051355: 
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051355 Debian Bug Tracking 
> System Contact ow...@bugs.debian.org with problems
>
> Apparently this should have been fixed in version 117.0.5938.48-1, if you 
> want to release this version in beta stage as a distro they are making which 
> is Arch and we can test it on Debian. 
> https://archlinux.org/packages/extra/x86_64/chromium/ 
> https://repology.org/project/chromium/versions
> --
> Cheers, Leandro Cunha
>
>
>
> Do you have a crbug or commit or something that fixes it? I haven't started 
> on 117 yet, and I also haven't really had time to debug this sid-specific 116 
> crash (other than building with downgraded packages from 9/1 and still 
> getting the crash). This was a bad week for finding free time.
>
> Tim, I don't suppose you've looked at 117 yet? There's an early release out.
>
>

This version is expected to be released on September 12th and we can
wait. I believe it must have also been compiled for Linux with the
current changes.
https://chromiumdash.appspot.com/schedule

-- 
Cheers,
Leandro Cunha

Bug#1051355: Processed: your mail

[Andres Salomon]

On Fri, Sep 8 2023 at 03:31:37 PM -03:00:00, Leandro Cunha 
 wrote:

Hi,

On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System
mailto:ow...@bugs.debian.org>> wrote:


 Processing commands for cont...@bugs.debian.org 
:


 > affects 1051355 phpsysinfo phpldapadmin jquery-timepicker
 Bug #1051355 [chromium] chromium: Segmentation fault
 Added indication that 1051355 affects phpsysinfo, phpldapadmin, and 
jquery-timepicker

 > stop
 Stopping processing here.

 Please contact me if you need assistance.
 --
 1051355: 
 Debian Bug Tracking System
 Contact ow...@bugs.debian.org  with 
problems


Apparently this should have been fixed in version 117.0.5938.48-1, if
you want to release this version in beta stage as a distro they are
making which is Arch and we can test it on Debian.



--
Cheers,
Leandro Cunha



Do you have a crbug or commit or something that fixes it?  I haven't 
started on 117 yet, and I also haven't really had time to debug this 
sid-specific 116 crash (other than building with downgraded packages 
from 9/1 and still getting the crash). This was a bad week for finding 
free time.


Tim, I don't suppose you've looked at 117 yet? There's an early release 
out.

Bug#1051355: Processed: your mail

[Leandro Cunha]

Hi,

On Fri, Sep 8, 2023 at 10:03 AM Debian Bug Tracking System
 wrote:
>
> Processing commands for cont...@bugs.debian.org:
>
> > affects 1051355 phpsysinfo phpldapadmin jquery-timepicker
> Bug #1051355 [chromium] chromium: Segmentation fault
> Added indication that 1051355 affects phpsysinfo, phpldapadmin, and 
> jquery-timepicker
> > stop
> Stopping processing here.
>
> Please contact me if you need assistance.
> --
> 1051355: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1051355
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems

Apparently this should have been fixed in version 117.0.5938.48-1, if
you want to release this version in beta stage as a distro they are
making which is Arch and we can test it on Debian.
https://archlinux.org/packages/extra/x86_64/chromium/
https://repology.org/project/chromium/versions

-- 
Cheers,
Leandro Cunha