[ISSUE] Bug in glib update 2.74.0 (part II)

[ISSUE] Bug in glib update 2.74.0 (part II)

[biopsin]

[-- Attachment #1: Type: text/plain, Size: 912 bytes --]

New issue by biopsin on void-packages repository

https://github.com/void-linux/void-packages/issues/39523

Description:
### Is this a new report?

Yes

### System Info

Linux voidx 5.10.145_1 #1 SMP Sat Sep 24 09:55:29 UTC 2022 x86_64 GNU/Linux

### Package(s) Affected

Any GTK3+ (firefox-esr, scite)

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

Unknown

### Expected behaviour

no issues

### Actual behaviour

After a reboot upgrading kernel from 5.4 -> 5.10 and also a update to glib-2.74.0 trying to launch any gtk3 applications (firefox-esr, scite) ends up in a Trace/breakpoint trap.
However I have spacefm (gtk2) and it has no issues.

Downgrading to glibc-2.72. resolves my issue, but I will further do a rebuild of GTK3+ as there seems to be more oddities going on after update.

### Steps to reproduce

launch any gtk3 application from terminal

Re: Bug in glib update 2.74.0 (part II)

[biopsin]

[-- Attachment #1: Type: text/plain, Size: 339 bytes --]

New comment by biopsin on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1261977681

Comment:
Upsidupsi a local issue : 
since I run GTK3-classic on this spesific machine, applying https://github.com/lah7/gtk3-classic/commit/8e6176c5eb8a3c45e78be0a9190db44d798bb0f6 should fix my problem.

Re: [ISSUE] [CLOSED] Bug in glib update 2.74.0 (part II)

[biopsin]

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

Closed issue by biopsin on void-packages repository

https://github.com/void-linux/void-packages/issues/39523

Description:
### Is this a new report?

Yes

### System Info

Linux voidx 5.10.145_1 #1 SMP Sat Sep 24 09:55:29 UTC 2022 x86_64 GNU/Linux

### Package(s) Affected

Any GTK3+ (firefox-esr, scite)

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

Unknown

### Expected behaviour

no issues

### Actual behaviour

After a reboot upgrading kernel from 5.4 -> 5.10 and also a update to glib-2.74.0 trying to launch any gtk3 applications (firefox-esr, scite) ends up in a Trace/breakpoint trap.
However I have spacefm (gtk2) and it has no issues.

Downgrading to glibc-2.72. resolves my issue, but I will further do a rebuild of GTK3+ as there seems to be more oddities going on after update.

### Steps to reproduce

launch any gtk3 application from terminal

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 213 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1262648629

Comment:
Not a Void bug, but I wonder if @bugcrazy is also using that project.

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 302 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1262648629

Comment:
Not a Void bug, but I wonder if @bugcrazy is also using that project.

This seems to be the same as https://github.com/void-linux/void-packages/issues/39390

Re: [ISSUE] [CLOSED] Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 915 bytes --]

Closed issue by biopsin on void-packages repository

https://github.com/void-linux/void-packages/issues/39523

Description:
### Is this a new report?

Yes

### System Info

Linux voidx 5.10.145_1 #1 SMP Sat Sep 24 09:55:29 UTC 2022 x86_64 GNU/Linux

### Package(s) Affected

Any GTK3+ (firefox-esr, scite)

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

Unknown

### Expected behaviour

no issues

### Actual behaviour

After a reboot upgrading kernel from 5.4 -> 5.10 and also a update to glib-2.74.0 trying to launch any gtk3 applications (firefox-esr, scite) ends up in a Trace/breakpoint trap.
However I have spacefm (gtk2) and it has no issues.

Downgrading to glibc-2.72. resolves my issue, but I will further do a rebuild of GTK3+ as there seems to be more oddities going on after update.

### Steps to reproduce

launch any gtk3 application from terminal

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 333 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1262648629

Comment:
Not a Void bug, but I wonder if @bugcrazy is also using that project or just an old version of gtk3.

This seems to be the same as https://github.com/void-linux/void-packages/issues/39390

Re: Bug in glib update 2.74.0 (part II)

[bugcrazy]

[-- Attachment #1: Type: text/plain, Size: 387 bytes --]

New comment by bugcrazy on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1264499953

Comment:
> Not a Void bug, but I wonder if @bugcrazy is also using that project or just an old version of gtk3.
> 
> This seems to be the same as #39390

I use gtk3-classic and gtk3, the bug is in the glib 2.74 version, the blame of the glib devs.

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 187 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1264508967

Comment:
That's not how this works, update your gtk.

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 291 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1264508967

Comment:
That's not how this works, update your gtk.
You shouldn't be able to reproduce this with a regular, not pached, up to date, official gtk+3 package.

Re: Bug in glib update 2.74.0 (part II)

[bugcrazy]

[-- Attachment #1: Type: text/plain, Size: 419 bytes --]

New comment by bugcrazy on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1264806624

Comment:
> That's not how this works, update your gtk.
> You shouldn't be able to reproduce this with a regular, not pached, up to date, official gtk+3 package.

I solved my problem, using the glib 2.72 version, I won't update for version 2.74, there are many problems and bugs.

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 336 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1265031869

Comment:
We do not support that and as more packages get updated, they will rely on glib 2.74 features. Please fix the underlying problem in your setup, most likely by updating GTK that you downgraded.

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 316 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1265104235

Comment:
And if there are any bugs in a normal void setup, not a highly customized one, they should be reported and fixed. So far only the gimp text tool bug was reported and fixed.

Re: Bug in glib update 2.74.0 (part II)

[q66]

[-- Attachment #1: Type: text/plain, Size: 199 bytes --]

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1265150391

Comment:
i for one sincerely hope that @bugcrazy's setup gets broken

Re: Bug in glib update 2.74.0 (part II)

[bugcrazy]

[-- Attachment #1: Type: text/plain, Size: 479 bytes --]

New comment by bugcrazy on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1265957697

Comment:
> We do not support that and as more packages get updated, they will rely on glib 2.74 features. Please fix the underlying problem in your setup, most likely by updating GTK that you downgraded.

I'll test Debian patches or wait for a really stable release of version 2.74.

https://launchpad.net/debian/+source/glib2.0/+changelog

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 309 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1265989233

Comment:
I will ask one last time, can you reproduce this with an unmodified Void system (especially with the official gtk+3 package) or is it an issue in your modifications?

Re: Bug in glib update 2.74.0 (part II)

[bugcrazy]

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

New comment by bugcrazy on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1266038091

Comment:
> And if there are any bugs in a normal void setup, not a highly customized one, they should be reported and fixed. So far only the gimp text tool bug was reported and fixed.

There was another user who told me, who had problems with glib 2.74 in thunar with android-tools. There are problems with glib update in distro:

https://forum.endeavouros.com/t/timeshift-issue/10391/9

Re: Bug in glib update 2.74.0 (part II)

[bugcrazy]

[-- Attachment #1: Type: text/plain, Size: 270 bytes --]

New comment by bugcrazy on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1266041513

Comment:
> i for one sincerely hope that @bugcrazy's setup gets broken

I don't have broken setup, it only happens with glib update.

Re: Bug in glib update 2.74.0 (part II)

[bugcrazy]

[-- Attachment #1: Type: text/plain, Size: 591 bytes --]

New comment by bugcrazy on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1266058599

Comment:
> I will ask one last time, can you reproduce this with an unmodified Void system (especially with the official gtk+3 package) or is it an issue in your modifications?

I have another machine, I use it as a server, no modifications to the packages, I just update, so far I haven't found any errors in glib. If the update problem was just mine, it would be an isolated case, but there are reports in other distros, so  it's not an isolated case.

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 946 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1266070369

Comment:
As I already said, if there are issues, they should be reported and fixed. I don't see any indication this (all gtk applications not starting) is an issue and you keep avoiding my question whether you can reproduce this with a official unmodified gtk+3 package. 
It would be nice if users could report bugs to us and not you, I can reproduce the issue with timeshift. Could the user who reported it to you or you open an issue about it?

> If the update problem was just mine, it would be an isolated case, but there are reports in other distros, so it's not an isolated case.

Could you link an issue in another distribution where all gtk applications don't start?

android-tools doesn't even depend on glib, so I am not sure how that would be an issue and I can not reproduce the Thunar issue.

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1266070369

Comment:
As I already said, if there are issues, they should be reported and fixed. I don't see any indication this (all gtk applications not starting) is an issue and you keep avoiding my question whether you can reproduce this with a official unmodified gtk+3 package. 
It would be nice if users could report bugs to us and not you, ~~I can reproduce the issue with timeshift~~. Could the user who reported it to you or you open an issue about it if they are also not using a heavily modified system?

correction: I can not reproduce a crash with glib 2.74, but I see some failed assertions and there are reports upstream

> If the update problem was just mine, it would be an isolated case, but there are reports in other distros, so it's not an isolated case.

Could you link an issue in another distribution where all gtk applications don't start?

android-tools doesn't even depend on glib, so I am not sure how that would be an issue and I can not reproduce the Thunar issue.

Re: Bug in glib update 2.74.0 (part II)

[bugcrazy]

[-- Attachment #1: Type: text/plain, Size: 1545 bytes --]

New comment by bugcrazy on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1267932816

Comment:
> As I already said, if there are issues, they should be reported and fixed. I don't see any indication this (all gtk applications not starting) is an issue and you keep avoiding my question whether you can reproduce this with a official unmodified gtk+3 package. It would be nice if users could report bugs to us and not you, ~I can reproduce the issue with timeshift~. Could the user who reported it to you or you open an issue about it if they are also not using a heavily modified system?
> 
> correction: I can not reproduce a crash with glib 2.74, but I see some failed assertions and there are reports upstream
> 
> > If the update problem was just mine, it would be an isolated case, but there are reports in other distros, so it's not an isolated case.
> 
> Could you link an issue in another distribution where all gtk applications don't start?
> 
> android-tools doesn't even depend on glib, so I am not sure how that would be an issue and I can not reproduce the Thunar issue.

I will only use glib 2.74, when they release a glib version 2.74.1 or higher, which really fixes the problems, as there are no test tools on the glib if it had no bug in the gimp.

Problems in other distros are similar.

Already question of the thunar, would be a problem of stamp data/team, when copies android files to Void. Because user, it didn't open Issue in github, that's a matter of him.

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 1405 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1268081658

Comment:
> I will only use glib 2.74, when they release a glib version 2.74.1 or higher, which really fixes the problems

"the problems"? You refuse to test this with the official gtk package and none of your reports make sense. Which problems do you have that are not caused by your modifications?

> as there are no test tools on the glib if it had no bug in the gimp.

glib has a test suite, I am not sure what your point is here.

> Problems in other distros are similar.

Problems with which programs that we also have? Links? Can you reproduce the issues? If there are none that you are experiencing, we don't care.

> Already question of the thunar, would be a problem of stamp data/team, when copies android files to Void. Because user, it didn't open Issue in github, that's a matter of him.

I don't really understand the first sentence, but if there isn't an open issue, we will probably ignore it.

You are not trying to be helpful. You just decided that glib 2.74 is bad, you complain in 3 (1 unrelated) threads, ignore me when I ask you to test something and then continue with complaining. This is not Telegram, this is a bug tracker and you are expected to cooperate in order for us to figure out how to solve the issues if there are any.

Re: Bug in glib update 2.74.0 (part II)

[bugcrazy]

[-- Attachment #1: Type: text/plain, Size: 2593 bytes --]

New comment by bugcrazy on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1269016917

Comment:
> > I will only use glib 2.74, when they release a glib version 2.74.1 or higher, which really fixes the problems
> 
> "the problems"? You refuse to test this with the official gtk package and none of your reports make sense. Which problems do you have that are not caused by your modifications?
> 
> > as there are no test tools on the glib if it had no bug in the gimp.
> 
> glib has a test suite, I am not sure what your point is here.
> 
> > Problems in other distros are similar.
> 
> Problems with which programs that we also have? Links? Can you reproduce the issues? If there are none that you are experiencing, we don't care.
> 
> > Already question of the thunar, would be a problem of stamp data/team, when copies android files to Void. Because user, it didn't open Issue in github, that's a matter of him.
> 
> I don't really understand the first sentence, but if there isn't an open issue, we will probably ignore it.
> 
> You are not trying to be helpful. You just decided that glib 2.74 is bad, you complain in 3 (1 unrelated) threads, ignore me when I ask you to test something and then continue with complaining. This is not Telegram, this is a bug tracker and you are expected to cooperate in order for us to figure out how to solve the issues if there are any.

I opened a issue here, as the problem was not reproduced, it was closed, so the problem was gimp, I said on the gimp ticket, what a bug was on the glib, you said the problem was at gimp, that glib 2.74 had shown this bug in gimp, then you posted what problem was really glib and hid the posts on the gimp ticket because they were off-tropics. I also opened glib's gitlab ticket, was closed and had poorly answered answers, I started accompanying gitlab glib tickets, has many problems related to glib 2.73, which has a 2.74 code and problems at 2.74, are simply closed and not fixed , they release a version with bugs and misplaced, the gimp is proof of this, because it is a brother project, they create patches later and is like this, just like Debian package full of patches.

If there really is glib testsuite, it does not work, as they would easily detect errors before, the problem with gimp would not exist.

The user who reported a problem with thunar knows how to create Issue here, because he didn't open it, I don't know.

If my needs, they require specific things, glib 2.74 problems cannot be reproduced, how would this help Void?

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 1784 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1269065962

Comment:
> I opened a issue here, as the problem was not reproduced, it was closed, so the problem was gimp

no, your issue was about all gtk programs not working, someone had a similar issue in this issue, figured out it's because of their custom gtk3 and even provided a link to a patch for you.

> I said on the gimp ticket, what a bug was on the glib, you said the problem was at gimp, that glib 2.74 had shown this bug in gimp, then you posted what problem was really glib and hid the posts on the gimp ticket because they were off-tropics.

You went to an unrelated issue about a gimp with glib 2.74 bug, posted your unrelated issue in the gnome repository which confused me because I thought it was about that issue. I am sorry about that, I shouln't have blindly trusted that you won't post random links, sorry about that. When I realised this discussion was irrelevant, I marked it off topic.


> I also opened glib's gitlab ticket, was closed and had poorly answered answers

If you are talking about the one about chromium not starting (probavly because of your custom gtk3), I found the answer understandable.
 
> If there really is glib testsuite, it does not work, as they would easily detect errors before, the problem with gimp would not exist.

I think you don't understand how tests work. They can not catch all issues.

> If my needs, they require specific things, glib 2.74 problems cannot be reproduced, how would this help Void?

You wouldn't spam irrelevant things and you would probably fix your system if you just updated your gtk3 like I suggested multiple times. This is not going anywhere, so let's lock this discussion.

Re: Bug in glib update 2.74.0 (part II)

[paper42]

[-- Attachment #1: Type: text/plain, Size: 1810 bytes --]

New comment by paper42 on void-packages repository

https://github.com/void-linux/void-packages/issues/39523#issuecomment-1269065962

Comment:
> I opened a issue here, as the problem was not reproduced, it was closed, so the problem was gimp

No, your issue was about all gtk programs not working. Someone had a similar problem in this issue, figured out it's because of their custom gtk3 and even provided a link to a patch for you.

> I said on the gimp ticket, what a bug was on the glib, you said the problem was at gimp, that glib 2.74 had shown this bug in gimp, then you posted what problem was really glib and hid the posts on the gimp ticket because they were off-tropics.

You went to an unrelated issue about a gimp with glib 2.74 bug, posted your unrelated issue in the glib repository which confused me because I thought it was about that issue. I am sorry about that, I shouln't have blindly trusted that you won't post random links and read it more closely, sorry about that. When I realised this discussion was irrelevant, I marked it off topic.


> I also opened glib's gitlab ticket, was closed and had poorly answered answers

If you are talking about the one about chromium not starting (probavly because of your custom gtk3), I found the answer understandable.
 
> If there really is glib testsuite, it does not work, as they would easily detect errors before, the problem with gimp would not exist.

I think you don't understand how tests work. They can not catch all issues.

> If my needs, they require specific things, glib 2.74 problems cannot be reproduced, how would this help Void?

You wouldn't spam irrelevant things and you would probably fix your system if you just updated your gtk3 like I suggested multiple times. This is not going anywhere, so let's lock this discussion.