Description of problem: [Desktop Entry] Name=SpringLobby Comment=Play real-time strategy games using the Spring engine Exec=/usr/games/springlobby Icon=springlobby Terminal=false Type=Application Categories=Game;StrategyGame; X-SuSE-translate=false X-Desktop-File-Install-Version=0.20 If you launch it by the menu it will not work as /usr/games/springlobby does not exist 'whereis springlobby' give '/bin/springlobby /usr/bin/springlobby' and 'springlobby' in a terminal works fine.
Assignee: bugsquad => nanardon
Depends on: (none) => 8201
Depends on: 8201 => (none)
Bug still valid and trivial to fix. Resetting assignee field since the package has no maintainer anymore.
Keywords: (none) => Junior_job, TriagedAssignee: nanardon => bugsquad
Summary: springlobby.desktop use a non existent launcher => springlobby.desktop uses a non existent launcher
Uploaded patched package for Mageia 5. The application should start now, please test. Advisory: ======================== springlobby would not start in some desktop environments due to a wrong executable path in desktop file. This update fixes it. ======================== Updated packages in core/updates_testing: ======================== springlobby-0.180-4.1.mga5.i586.rpm springlobby-0.180-4.1.mga5.x86_64.rpm From source RPMs: springlobby-0.180-4.1.mga5.src.rpm
Assignee: bugsquad => qa-bugsCC: (none) => yann.cantinWhiteboard: (none) => advisory
Created attachment 6914 [details] Failure of springlobby to launch This is the full terminal output
This comment was lost somehow: Testing on mga-5-64 (KDE) urpmi springlobby Confirmed that the application does not launch from the menu but does in a terminal Installed the testing package: urpmi --search-media "Core Updates Testing" springlobby ftp://192.168.0.2//pub/mirror/Mageia/distrib/5/x86_64/media/core/updates_testing/springlobby-0.180-4.1.mga5.x86_64.rpm installing springlobby-0.180-4.1.mga5.x86_64.rpm from /var/cache/urpmi/rpms Preparing... ################################################################################# 1/1: springlobby ################################################################################# 1/1: removing springlobby-0.180-4.mga5.x86_64 Attempting to launch from the menu, the icon appears briefly in the panel, but the application does not launch In a terminal it does not launch either; *** Error in `springlobby': free(): invalid size: 0x00007ffff9237c60 *** The full terminal output is attached per comment#3
Version: Cauldron => 5
Whiteboard: advisory => advisory feedback
see mga#16397 : wxgtk update (currently in testing), if not installed, cause the segfault.
Depends on: (none) => 16560
Uploaded patched package for Mageia 5. Along with the updated wxgtk packages (Bug 16560), the application should start from the menu, please test. New advisory: ======================== springlobby would not start in some desktop environments due to a wrong executable path in desktop file. This update fixes it. ======================== Updated packages in core/updates_testing: ======================== springlobby-0.180-4.4.mga5.i586.rpm springlobby-0.180-4.4.mga5.x86_64.rpm From source RPMs: springlobby-0.180-4.4.mga5.src.rpm
On mga-5-64 I installed springlobby wxgtk lib64wxgtku3.0_0 from updates_testing springlobby now launches from the menu or in a terminal. I did no further testing, but this update resolves the reported bug.
Whiteboard: advisory feedback => advisory feedback MGA5-64-OK
Whiteboard: advisory feedback MGA5-64-OK => advisory MGA5-64-OK
On mga-5-32 I installed springlobby wxgtk libwxgtku3.0_0 from testing springlobby now launches from the menu or in a terminal I did no further testing but this update fixes the reported bug.
Whiteboard: advisory MGA5-64-OK => advisory MGA5-64-OK MGA5-32-OK
Before I validate this update, could a QA committer confirm that the revised advisory has been uploaded to SVN. There is no comment to that effect.
(In reply to James Kerr from comment #9) > Before I validate this update, could a QA committer confirm that the revised > advisory has been uploaded to SVN. There is no comment to that effect. Actually I think it was not uploaded at all, Yann added the whiteboard tag when he wrote the initial advisory, but I think it was just that he misunderstood its meaning.
Whiteboard: advisory MGA5-64-OK MGA5-32-OK => MGA5-64-OK MGA5-32-OK
I had suspected that. I've validated the update. A QA-committer needs to upload the advisory.
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugs
I should have noted the revised advisory is in comment #6 This update should not be pushed until the updates in Bug 16560 are pushed.
Advisory uploaded. Please ensure bug 16560 is pushed before or at the same time as this one. Thanks
Whiteboard: MGA5-64-OK MGA5-32-OK => advisory MGA5-64-OK MGA5-32-OK
An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGAA-2015-0111.html
Status: NEW => RESOLVEDResolution: (none) => FIXED