Description of problem: I had a crash when using the official skype4pidgin-package in mga2 & I rebuilt the same version from the nonfree-repo using the src.rpm & skype4pidgin no longer crashes. Version-Release number of selected component (if applicable): 0.0-svn628
Created attachment 3026 [details] Here's the crash-output using gdb
CC: (none) => kristoffer.grundstrom1983
Should be fixed in skype4pidgin-0.0-2.svn639.1.mga2 , which should arrive in updates_testing. Please test. Assigning to QA. Regards, -- Shlomi Fish
CC: (none) => shlomifAssignee: bugsquad => qa-bugs
Kristoffer can you test this corrects your crash please. Thanks.
Summary: Backport skype4pidgin to mga2 => skype4pidgin crash mga2
More info on this here: http://eion.robbmob.com/README.txt It needs a running copy of skype (install get-skype)
I was running get-skype. Forgot to mention that. Now tested the new update of skype4pidgin & problem seems to be gone. Closing as RESOLVED FIXED.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED
Hardware: All => x86_64
Severity: major => normal
a package in testing is useless
Hardware: x86_64 => AllComponent: Backports => RPM PackagesWhiteboard: (none) => MGA2-64-OK
(sorry)
Resolution: FIXED => (none)Status: RESOLVED => REOPENED
Are you able to test i586 too Kristoffer? Once it's been tested on both arch's then we can validate and ask sysadmin to push to updates.
Yes, but it'd take some time. ;)
There is no rush for this.
Any progress Kristoffer please?
According to http://www.ubuntugeek.com/how-to-install-skype-api-plugin-for-pidgin-in-ubuntu.html once skype4pidgin is installed, each buddy should have the skype icon added in the pidgin dialog, but that doesn't seem to be happening. I'm not clear on what else needs to be done to be able to use skype from within pidgin.
CC: (none) => davidwhodgins
I just tested on MGA 2, i586. I could not reproduce the bug, works like a charm for me. Unfortunately I could not test the package in Updates_Testing, as I could not find it - it seems my mirror is not up to date. Dave: You need to add a new "account" for your Skype contacts (where you would also add a Jabber/IRC/MSN account). There should be an option "Skype (d-bus)", all you need to do is enter your Skype user name there (note that Skype must be running!). Then Skype will ask you if you want to let Pidgin use it - confirm (and make sure you check "remember this setting", otherwise you get asked over and over again) and your Skype contacts should appear in Pidgin.
CC: (none) => wassi
(In reply to comment #13) > I just tested on MGA 2, i586. I could not reproduce the bug, works like a charm > for me. Unfortunately I could not test the package in Updates_Testing, as I > could not find it - it seems my mirror is not up to date. > Please switch to a different mirror because you should install the upcoming updates and using such outdated mirror is risky. Regards, -- Shlomi Fish
Thanks for pointing this out to me, I am aware of the risks and suspended testing until I have an up-to-date system again. However, I'd rather like the mirror to update, as I imagine many more Mageia users are using it, possibly without even being aware of the fact it's outdated. So far I found out that ftp://ftp.fi.muni.cz/pub/linux/mageia/distrib/2/i586 is to blame, but didn't find a way to contact the server administrators yet - any ideas how I could do that? Note that I did not pick the mirror by hand, it was picked by rpmdrake out of $MIRRORLIST.
testing on MGA2-64
CC: (none) => stblack
user7, Thanks for the answer in comment 13. Testing complete on Mageia 2 i586. Could someone from the sysadmin team push the srpm skype4pidgin-0.0-2.svn639.1.mga2.nonfree.src.rpm from Mageia 2 Nonfree Updates Testing to Nonfree Updates. Advisory: This bugfix update for skype4pidgin fixes a segfault when using the plugin with pidgin and skype. https://bugs.mageia.org/show_bug.cgi?id=7955
Keywords: (none) => validated_updateCC: (none) => sysadmin-bugsWhiteboard: MGA2-64-OK => MGA2-64-OK MGA2-32-OK
Update pushed: https://wiki.mageia.org/en/Support/Advisories/MGAA-2012-0239
Status: REOPENED => RESOLVEDCC: (none) => tmbResolution: (none) => FIXED