FS#52684 - [amule] new gtk3 build is very unstable

Attached to Project: Arch Linux
Opened by François Guerraz (kubrick) - Monday, 23 January 2017, 11:03 GMT
Last edited by Antonio Rojas (arojas) - Monday, 23 January 2017, 11:48 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I tried this new build and I couldn't use it for more than a few minutes without a crash.
See the github issue below. I also had a variety of infinite loops leading to amule being killed by OOM killer

Additional info:
* package version 10984
* see https://github.com/amule-project/amule/issues/89

Steps to reproduce:
Just launch it and search for something, or wait for your downloads to start, or anything really.

I think we should revert to the GTK2 version for now, as sad as it is...
This task depends upon

Closed by  Antonio Rojas (arojas)
Monday, 23 January 2017, 11:48 GMT
Reason for closing:  Fixed
Additional comments about closing:  amule 10983-2
Comment by Sebastiaan Lokhorst (lonaowna) - Monday, 23 January 2017, 11:24 GMT
I think you mean the switch to wxGTK 3 (from 2.8), which it still uses GTK+2. We cannot easily switch back to wxGTK 2.8, as that has now been dropped from the repositories.

See  FS#51584  for more info. Some people there already mentioned that it was unstable (I didn't notice it myself), but it seems like the switch was made anyway.
Comment by François Guerraz (kubrick) - Monday, 23 January 2017, 11:30 GMT
Building with the following PKGBUILD seems to fix the issue with sockets.
   PKGBUILD (1.6 KiB)

Loading...