Updating wxgtk3.1 from the "Core Release" repo to version(wxgtk3.1-3.1.5-1.mga8) from "Core Updates Testing" breaks PlayOnLinux. The irony being that playonlinux is only in the "Core Updates Testing" repo. Version-Release number of selected component (if applicable): wxgtk3.1-3.1.5-1.mga8.x86_64.rpm playonlinux-4.4-1.mga8.x86_64.rpm How reproducible: Always. Steps to Reproduce: 1. Enable "Core Updates Testing" repo and update wxgtk3.1 packages. 2. run playonlinux from terminal to at least see the segmentation fault error. $ playonlinux Looking for python3... 3.8.11 - selected 1.0 [main] Message: PlayOnLinux (4.4) is starting [clean_tmp] Message: Cleaning temp directory [Check_OpenGL] Message: 64bits direct rendering is enabled [Check_OpenGL] Message: 64bits direct rendering is enabled [POL_System_CheckFS] Message: Checking filesystem for /home/aurelian/.PlayOnLinux/ [main] Message: Filesystem is compatible [install_plugins] Message: Checking plugin: Capture... [install_plugins] Message: Checking plugin: ScreenCap... [install_plugins] Message: Checking plugin: PlayOnLinux Vault... [update_check] Message: List is up to date Registered PID: 2432223 (Present) Registered PID: 2432257 (Missing) The workaround, if someone had that testing repo enabled and used playonlinux, is to downgrade wxgtk to the release version. $ urpmi --downgrade --media "Core Release" wxgtk3.1 It looks like POL depends on python3-wxpython4 which depends on wxgtk3.1.
Yeah. This needs to be rebuilt. Assigning. Adding committer about wxgtk3.1 playonlinux was restored on: r1716015 | daviddavid | 2021-04-16 16:52:06 +0200 (ven. 16 avril 2021) | 3 lignes
Source RPM: wxgtk-3.1.5-1.mga8.src.rpm => SRPMS/core/updates_testing/playonlinux-4.4-1.mga8.src.rpmCC: (none) => jani.valimaa, ouaurelienAssignee: bugsquad => geiger.david68210
wxgtk3.1 update is in c33+ of Bug 28352 Affects several packages. For Playonlinux Bug 28717 - Reintroduce: PlayonLinux works on Mageia 8
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=28352, https://bugs.mageia.org/show_bug.cgi?id=28717CC: (none) => fri
Hi, Yesterday, I rebuilt python3-wxpython4. In my tests (with a game I wrote: http://yapysudoku.sf.net), with python-wxpython4-4.1.1-1.1.mga8 from core/updates_testing, the segmentation fault does not occur anymore. Best regards, Nico.
CC: (none) => nicolas.salguero
Created attachment 12952 [details] Screenshot that show the issue with Playonlinux installing a programm This screenshot show as Playonlinux crash in Plasma environment to install a programm. Appears windows in Plasma panel, but I can't open these windows for continue with the installation.
CC: (none) => joselpddj
Now, Playonlinux opens, but don't work fine. Crash when I have tried install a programm.
(In reply to Nicolas Salguero from comment #3) > Yesterday, I rebuilt python3-wxpython4. In my tests (with a game I wrote: > http://yapysudoku.sf.net), with python-wxpython4-4.1.1-1.1.mga8 from > core/updates_testing, the segmentation fault does not occur anymore. I can confirm that the reported bug is no more with python-wxpython4-4.1.1-1.1.mga8 . Managed to run an old already installed windows app and to install and to run your linked game in a new POL instance. I had to do a clean reinstall POL as I had my own hacked rpm packages. These are the rpms installed for POL from 'Core Updates Testing' media/repo used for mentioned tests: $ rpm -qa --last python3-wxpython4-4.1.1-1.1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 playonlinux-4.4-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_gtk3u_xrc3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_gtk3u_stc3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_gtk3u_richtext3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_gtk3u_ribbon3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_gtk3u_propgrid3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_gtk3u_html3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_gtk3u_gl3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_gtk3u_core3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_gtk3u_aui3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_baseu_xml3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 lib64wx_baseu_net3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:53 +0300 wxgtk3.1-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:52 +0300 lib64wx_baseu3.1_5-3.1.5-1.mga8.x86_64 Vi 15 oct 2021 12:23:52 +0300 So, for me, this bug is solved as it stands now and it should be closed as fixed. Thank you.
Update: in https://bugs.mageia.org/show_bug.cgi?id=28717#c24, Jose told PlayOnLinux works now - thanks. This bug have apparently transformed into python3-wxpython4 update if i get this correct? Calling in Lewis and Andrews for what is next step / test about this. A possibly complicating issue is the stuck update of wxgtk-3.1.5-1.mga8 sitting in core/updates_testing waiting for decision https://bugs.mageia.org/show_bug.cgi?id=28352#c39 For PlayOnLinux separately, lets move on to Bug 28717 - Reintroduce: PlayonLinux works on Mageia 8
Assignee: geiger.david68210 => qa-bugsCC: ouaurelien => andrewsfarm, lewyssmithSummary: playonlinux: Segmentation fault(core dumped) with wxgtk-3.1.5-1 packages => PlayOnLinux segmentation fault with wxgtk-3.1.5-1, python3-wxpython4 update fix thisSource RPM: SRPMS/core/updates_testing/playonlinux-4.4-1.mga8.src.rpm => python3-wxpython4Status comment: (none) => wxgtk-3.1.5-1.mga8 in bug 28352#c39, POL in 28717
Thes two bugs 28717 & 29291 are intimate; resolved by python-wxpython4-4.1.1-1 (already pushed) in addition to 'new' playonlinux. https://bugs.mageia.org/show_bug.cgi?id=28717#c22 https://bugs.mageia.org/show_bug.cgi?id=28717#c24 https://bugs.mageia.org/show_bug.cgi?id=29291#c3 https://bugs.mageia.org/show_bug.cgi?id=29291#c6 These are all about playonlinux being re-introduced. I cannot see its current Mageia version anywhere. It needs to be (if not already) in Backports. Can it be clarified that - with the now current 'python-wxpython4-4.1.1-1' - the last 'playonlinux' basically works, heeding Morgan's wiki notes. BUT note: https://bugs.mageia.org/show_bug.cgi?id=28717#c19 "just pop up to say we should not bother to reintroduce PoL4 on Mageia8. PoL4 seems to be dead, and even the git https://github.com/PlayOnLinux/POL-POM-4 mentioned : Note: Phoenicis PlayOnLinux ... is currently under development. Please clone Phoenicis PlayOnLinux ... repository if you want to contribute. Phoenicis is the designated successor of PlayOnLinux" Perhaps we should do that for Mageia 9.
CC: (none) => arusanu, geiger.david68210Blocks: (none) => 28717
Replied in https://bugs.mageia.org/show_bug.cgi?id=28717#c27
I cannot send this along as an update, whether playonlinux works or not, because of the included wxgtk packages. They're going to break too many other things. An example: Bug 28352 concerns the guayadeque music player. It requires the above wxgtk packages. As it is, the player loads and appears to work in 64-bit, but not in 32-bits. That is the reason for the bug, and I can confirm it. But, after using quarepo to download the package list at http://madb.mageia.org/tools/listRpmsForQaBug/bugnum/29291/application/0 and getting updates before even attempting to install playonlinux, guayadeque crashes with a segfault even on 64-bits. This indicates that if this goes forward, and users update the included wxgtk packages, any or all of the apps on the long list in https://bugs.mageia.org/show_bug.cgi?id=28352#c39 will probably suffer the same fate. This needs to be re-assigned, but I don't know who should be the assignee. Oh, and I believe that new assignee should be looking into Bug 28352 as well.
Depends on: (none) => 29848
I think we could close this bug both because it was raised against a package not yet officially in our repos; and is 'fixed' in its context (comment 6), with: - playonlinux-4.4-1.mga8.x86_64 - python3-wxpython4-4.1.1-1.1.mga8.x86_64 - wxgtk3.1-3.1.5-1.mga8.x86_64 (to be confirmed by Jose on 28717) but we do not know that the exact version of wxgtk3.1 matters. It should, I think, be in Backports/testing anyway. It does not need to go to QA because as yet the application is on hold for pushing public over wxgtk3.1, and that will be done via the other Bug 28717 which is more explicit: please re-introduce POL. What say others?
I'm fine with that. I wondered from the beginning why it wasn't in backports, but decided that was outside my jurisdiction.
Maybe in updates so that upgrade from mga7 works? I am also for closing this.
Thanks. (In reply to Thomas Andrews from comment #12) > was outside my jurisdiction. Just shout! A packager affair, really; but for M8 this was a 'new package' because we do not currently offer it. Re upgrades, if this was just in Core for M9, would it not be picked up from there? Do not upgrades only use 'updates' where a post-issue (M9) update exists?
Status: NEW => RESOLVEDResolution: (none) => FIXED
I assume users upgrading *from mga7 to mga8* need this update, and backports repo is not usually enabled.
After reading Bug 28717 Comment 29 I see why it was reintroduced as an update, rather than put into backports. However, we did not need two bugs for this, so closing this one should not be a problem. But, I don't see it as "fixed" just yet. That won't happen until Bug 28717 is fixed, which can't happen until Bug 29848 is done.
Trying to tidy up relationships... Bug 29848 references this bug for the wxpython update. It is probably good to make it really be that. To close when wxpython is released, after/with wxgtk3.1
Resolution: FIXED => (none)Summary: PlayOnLinux segmentation fault with wxgtk-3.1.5-1, python3-wxpython4 update fix this => python3-wxpython4 update, for PlayOnLinux, depending on wxgtk3.1Status: RESOLVED => REOPENEDStatus comment: wxgtk-3.1.5-1.mga8 in bug 28352#c39, POL in 28717 => wxgtk-3.1.5-1.mga8 in 29848, from 28352#c39, POL in 28717
My mistake, confused by all those 1s! I thought the update in this bug was already out, apparently not, so agree with you. Current issued: python3-wxpython4-4.1.1-1 This update: python3-wxpython4-4.1.1-1.1 Thanks for all your work on the ongoing inter-related bug minefield.
Blocks: (none) => 28352See Also: https://bugs.mageia.org/show_bug.cgi?id=28352 => (none)
See Also: https://bugs.mageia.org/show_bug.cgi?id=28717 => (none)
Validating; This seem to work with the package updates it concern.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
CC: lewyssmith => (none)
Keywords: (none) => advisoryCC: (none) => davidwhodgins
Tried in Mga Vbox x84_64, Playonlinux works fine, no installation issues. Greetings!!
CC: (none) => lewyssmith
Whiteboard: (none) => MGA8-64-OK
An update for this issue has been pushed to the Mageia Updates repository. https://advisories.mageia.org/MGAA-2022-0015.html
Status: REOPENED => RESOLVEDResolution: (none) => FIXED
Blocks: (none) => 29959
Blocks: 29959 => (none)