Description of problem: I have just installed Mageia 5 beta using the DVD-iso for x86_64 and I'm using all the medias except the Testing ones and the kernel that I'm using is 3.18.1-desktop-3.mga5. I haven't made any changes to the standard theme and I'm logged in to KDE 4.14 atm. I get a crash during the time when I'm connecting to the Skype, Google Talk and Facebook-protocols. I'll try to reproduce it in another environment like GNOME or MATE. Here's the output from gdb: [kristoffer@localhost ~]$ gdb pidgin GNU gdb (GDB) 7.8.1-7.mga5 (Mageia release 5) Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-mageia-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from pidgin...Reading symbols from /usr/lib/debug/usr/bin/pidgin.debug...done. done. (gdb) run Starting program: /usr/bin/pidgin [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". Detaching after fork from child process 31589. Detaching after fork from child process 31590. [New Thread 0x7fffeab30700 (LWP 31591)] [New Thread 0x7fffea32f700 (LWP 31592)] [New Thread 0x7fffd6707700 (LWP 31594)] Detaching after fork from child process 31595. Detaching after fork from child process 31596. [New Thread 0x7fffd54d7700 (LWP 31597)] [New Thread 0x7fffd4cd6700 (LWP 31598)] Attempt to unlock mutex that was not locked Program received signal SIGABRT, Aborted. 0x00007ffff495d627 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 55 return INLINE_SYSCALL (tgkill, 3, pid, selftid, sig); (gdb) bt full #0 0x00007ffff495d627 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55 resultvar = 0 pid = 31584 selftid = 31584 #1 0x00007ffff495edba in __GI_abort () at abort.c:89 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0x1d49620, sa_sigaction = 0x1d49620}, sa_mask = {__val = {30700224, 0, 140737351981680, 140737300489984, 44, 140737306852768, 140737297114223, 0, 140737300489984, 44, 140737306852768, 44, 140737297577021, 140737300494896, 140737306852608, 0}}, sa_flags = 44, sa_restorer = 0x7ffff4cd6700 <_IO_2_1_stderr_>} sigs = {__val = {32, 0 <repeats 15 times>}} #2 0x00007ffff52885bd in g_mutex_unlock_slowpath (mutex=<optimized out>, prev=<optimized out>) at gthread-posix.c:1321 #3 0x00007ffff5288fee in g_mutex_unlock (mutex=<optimized out>) at gthread-posix.c:1344 prev = <optimized out> #4 0x00007ffff52891f5 in g_cond_wait_until (cond=0x1d49620, mutex=0x1d472c0, end_time=<optimized out>) at gthread-posix.c:1436 now = {tv_sec = 2283, tv_nsec = 824560029} span = {tv_sec = 9, tv_nsec = 999996971} sampled = 0 res = <optimized out> #5 0x00007fffd831300d in skype_send_message (message_format=0x7fffd831c6e3 "NAME %s") at skype_messaging.c:235 next_message_num = 1 cur_message_num = 0 message = 0x1d57100 "\340o\325\001" return_msg = 0x10 <error: Cannot access memory at address 0x10> args = {{gp_offset = 8, fp_offset = 48, overflow_arg_area = 0x7fffffffb4f0, reg_save_area = 0x7fffffffb430}} condition_result = 0 endtime = {tv_sec = 1420322091, tv_usec = 991320} #6 0x00007fffd8316265 in skype_login_part2 (acct=0x8a1470, acct@entry=<error reading variable: value has been optimized out>) at libskype.c:1701 reply = 0xc46a70 "\300\363", <incomplete sequence \303> gc = 0x1d4be10 #7 0x00007ffff52465d3 in g_timeout_dispatch (source=0x1d573e0, callback=<optimized out>, user_data=<optimized out>) at gmain.c:4520 timeout_source = 0x1d573e0 again = <optimized out> #8 0x00007ffff5245b7d in g_main_context_dispatch (context=0x70a790) at gmain.c:3111 dispatch = 0x7ffff52465c0 <g_timeout_dispatch> prev_source = 0x0 was_in_call = 0 user_data = 0x8a1470 callback = 0x7fffd8316213 <skype_login_part2> cb_funcs = <optimized out> cb_data = 0x1d57450 need_destroy = <optimized out> source = 0x1d573e0 current = 0x746c80 i = 4 #9 0x00007ffff5245b7d in g_main_context_dispatch (context=context@entry=0x70a790) at gmain.c:3710 #10 0x00007ffff5245f18 in g_main_context_iterate (context=0x70a790, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3781 max_priority = 0 timeout = 0 some_ready = 1 nfds = <optimized out> allocated_nfds = 8 fds = 0x1d57480 ---Type <return> to continue, or q <return> to quit--- #11 0x00007ffff5246232 in g_main_loop_run (loop=0x1d57140) at gmain.c:3975 __FUNCTION__ = "g_main_loop_run" #12 0x00007ffff6d5cae7 in IA__gtk_main () at gtkmain.c:1257 tmp_list = 0x0 functions = 0x0 init = <optimized out> loop = 0x1d57140 #13 0x0000000000431b17 in main (argc=1, argv=0x7fffffffda88) at gtkmain.c:937 opt_help = -18672 opt_version = 13350752 opt_config_dir_arg = 0x0 accounts = 0x0 sigset = {__val = {82950, 0 <repeats 15 times>}} errmsg = '\000' <repeats 264 times>... signal_channel = 0x0 signal_status = G_IO_STATUS_ERROR error = 0x0 opt = 0 debug_enabled = 80 active_accounts = 0x0 long_options = {{name = 0x4cae27 "config", has_arg = 1, flag = 0x0, val = 99}, {name = 0x4b93f9 "debug", has_arg = 0, flag = 0x0, val = 100}, {name = 0x4c6eb3 "force-online", has_arg = 0, flag = 0x0, val = 102}, {name = 0x4baf85 "help", has_arg = 0, flag = 0x0, val = 104}, {name = 0x4c6d5d "login", has_arg = 2, flag = 0x0, val = 108}, {name = 0x4c6ec0 "multiple", has_arg = 0, flag = 0x0, val = 109}, {name = 0x4c6ec9 "nologin", has_arg = 0, flag = 0x0, val = 110}, {name = 0x4cae3a "session", has_arg = 1, flag = 0x0, val = 115}, {name = 0x4bd72a "version", has_arg = 0, flag = 0x0, val = 118}, {name = 0x4cae30 "display", has_arg = 1, flag = 0x0, val = 68}, {name = 0x4c79a3 "sync", has_arg = 0, flag = 0x0, val = 83}, {name = 0x0, has_arg = 0, flag = 0x0, val = 0}} Version-Release number of selected component (if applicable): 2.10.11 How reproducible: Many times. Steps to Reproduce: 1. Boot the DVD installation iso for the beta-version of Mageia 5. 2. Use all medias except the Testing ones and update Mageia 5. 3. Install pidgin, skype4pidgin. 4. Run pidgin and set it to log in to Skype (check the box to start Skype automatically if not started already in the tab to the right), Google Talk and Facebook. 5. When you've set that up everything seems fine, but the next time you open Pidgin and connect to all theese protocols Pidgin crashes. Reproducible: Steps to Reproduce:
CC: (none) => kristoffer.grundstrom1983
Created attachment 5782 [details] Here's all the information about my computer
The gdb trace points to code specific to Skype, does it work for Facebook and Google Talk if you remove the Skype account?
CC: (none) => pterjan
Fix should be https://code.google.com/p/skype4pidgin/source/detail?r=665
Source RPM: pidgin => skype4pidgin
I don't even have a chance to disable the Skype account when I start Pidgin so it doesn't help.
Keywords: (none) => TriagedCC: (none) => shlomif
Upgraded to skype4pidgin-0.0-6.svn699.mga5.src.rpm on Cauldron. Please test to see if it fixes the problem for you.
That update seems to do the trick as I get no crash. Can you push it to Release Updates? Closing as RESOLVED FIXED. Should anyone get this problem in the future, please feel free to reopen this bugreport with new information.
Status: NEW => RESOLVEDResolution: (none) => FIXED
(In reply to Kristoffer Grundström from comment #6) > That update seems to do the trick as I get no crash. Can you push it to > Release Updates? Do you mean to the Mageia 4 updates/updates_testing? I can try. It is kind of a package upgrade though. > > Closing as RESOLVED FIXED. Thanks! Regards, -- Shlomi Fish > Should anyone get this problem in the future, please feel free to reopen > this bugreport with new information.
OK, I submited skype4pidgin to the Mageia 4 nonfree/updates_testing , but I also accidentally submitted pidgin there as well: http://pkgsubmit.mageia.org/
Reopening as the update to fix this currently has issues.
Status: RESOLVED => REOPENEDResolution: FIXED => (none)
Blocks: (none) => 15100
This would require an entry in the Errata. Could someone write it? From what I understand the initial issue is fixed but other issues arose?
Keywords: (none) => NEEDINFOWhiteboard: (none) => FOR_ERRATA
(In reply to Samuel VERSCHELDE from comment #10) > This would require an entry in the Errata. Could someone write it? From what > I understand the initial issue is fixed but other issues arose? I'm not aware of any problem for that on Cauldron, but on the other hand, I'm not actively using Skype or skype4pidgin (as I really try to avoid proprietary software). comment #9 is pretty vague and lacks details. Regards, -- Shlomi Fish
Shlomi, comment #9 is related to bug 15100, which was handled back to you due to issues during testing. I suppose comment #9 means the same issues are probably present in cauldron.
Keywords: NEEDINFO => (none)Whiteboard: FOR_ERRATA => MGA5TOO FOR_ERRATA
(In reply to Samuel VERSCHELDE from comment #12) > Shlomi, comment #9 is related to bug 15100, which was handled back to you > due to issues during testing. I suppose comment #9 means the same issues are > probably present in cauldron. I see, well, I don't know if the same issues are present in Cauldron as well. It needs testing.
Keywords: (none) => NEEDINFOWhiteboard: MGA5TOO FOR_ERRATA => (none)
Bump
CC: (none) => nic
(In reply to Nic Baxter from comment #14) > Bump Hi Nic! Shouldn't the fix be present in Mageia 5? Which symptoms are you getting? Mageia 4 was end-of-lifed.
Hi Shlomi I am working through the NEEDINFO bugs with no action for while so wanted to trigger something. I haven't tried to reproduce this but will do now. If it works for me should I close it? Nic
(In reply to Nic Baxter from comment #16) > Hi Shlomi > I am working through the NEEDINFO bugs with no action for while so wanted to > trigger something. I haven't tried to reproduce this but will do now. If it > works for me should I close it? > Nic Hi Nic, yes - please report back and close the bug.
I installed pidgin & skype4pidgin in Mga5. Configured pidgin, closed & reopened. Skype contacts appeared and messaging worked. Closing as fixed.
Status: REOPENED => RESOLVEDResolution: (none) => FIXED