Opened 11 years ago

Closed 11 years ago

#7057 closed defect

Pidgin doesn't start after an update (x86_64)

Reported by: dux Owned by: lschiere
Milestone: Component: unclassified
Version: 2.5.1 Keywords: doesn't start update 2.5.1.1
Cc:

Description (last modified by dux)

Pidgin doesn't start after updating on my machine (fedora 9):

"Pidgin 2.5.1-1.fc9 has segfaulted and attempted to dump a core file. This is a bug in the software and has happened through no fault of your own."

No older version is working anymore.

  • Solution: Removal of ./purple
  • Still having the problem, that I can't add any typ of protocol. No error appears besides the above.

Change History (11)

comment:1 Changed 11 years ago by dux

  • Description modified (diff)

comment:2 Changed 11 years ago by dux

  • Description modified (diff)

comment:3 Changed 11 years ago by dux

  • Description modified (diff)

comment:4 Changed 11 years ago by QuLogic

  • Status changed from new to pending

Please follow the instructions to get a backtrace and attach it to this ticket.

comment:5 Changed 11 years ago by fcorneli

I'm experiencing the same problem. A backtrace gives me:

#16 0x00bc1ecf in ?? () from /usr/lib/purple-2/libjabber.so.0
No symbol table info available.
#17 0x00bc4a04 in jabber_login () from /usr/lib/purple-2/libjabber.so.0
No symbol table info available.
#18 0x002b6b42 in purple_connection_new () from /usr/lib/libpurple.so.0
No symbol table info available.
#19 0x0029d116 in purple_account_connect () from /usr/lib/libpurple.so.0
No symbol table info available.
#20 0x0029d281 in purple_accounts_restore_current_statuses ()
   from /usr/lib/libpurple.so.0

comment:6 Changed 11 years ago by fcorneli

When I remove the .purple directory and I try to add a new account I also get a core dump:

*** glibc detected *** pidgin: malloc(): memory corruption (fast): 0x0a006735 ***
======= Backtrace: =========
/lib/libc.so.6[0x63cc874]
/lib/libc.so.6[0x63cf8d6]
/lib/libc.so.6(__libc_malloc+0x95)[0x63d0ce5]
/lib/libglib-2.0.so.0(g_realloc+0x3a)[0x27eb3da]
/lib/libglib-2.0.so.0[0x280635f]
/lib/libglib-2.0.so.0(g_string_sized_new+0x3d)[0x280753d]
/lib/libglib-2.0.so.0(g_shell_unquote+0x3c)[0x27ff41c]
/lib/libglib-2.0.so.0(g_shell_parse_argv+0x281)[0x27ffb61]
/lib/libglib-2.0.so.0(g_spawn_command_line_sync+0x4c)[0x281c05c]
/usr/lib/libpurple.so.0(purple_proxy_get_setup+0x2f6)[0x2deb36]
/usr/lib/libpurple.so.0(purple_proxy_connect+0xa4)[0x2df094]
/usr/lib/purple-2/libmsn.so(msn_servconn_connect+0x126)[0xf47336]
/usr/lib/purple-2/libmsn.so(msn_notification_connect+0x6b)[0xf43cfb]
/usr/lib/purple-2/libmsn.so(msn_session_connect+0x62)[0xf488c2]
/usr/lib/purple-2/libmsn.so[0xf3de65]
/usr/lib/libpurple.so.0(purple_connection_new+0x192)[0x2b6b42]
/usr/lib/libpurple.so.0(purple_account_connect+0xc6)[0x29d116]
/usr/lib/libpurple.so.0(purple_account_set_enabled+0x12a)[0x29d3fa]
pidgin[0x8071988]

comment:7 Changed 11 years ago by fcorneli

The issue seems to be related to the Proxy Options one chooses. When you set the proxy type to "Use GNOME proxy settings", then pidgin crashes.

comment:8 Changed 11 years ago by Jaus

How do I change the proxy settings in Pidgin? If I remove the ~/.pruple directory it still doesn't start. But you are right - I also changed the Proxy settings before that problem appeared. But where the hell do I need to edit this option so I can start Pidgin again?

comment:9 Changed 11 years ago by fcorneli

Removing the ~/.purple directory should do the trick. Are you sure you removed the correct directory? You've got a typo: pruple instead of purple.

comment:10 Changed 11 years ago by Jaus

I solved the problem. I had to change the Gnome Proxy settings, because Pidgin uses the standard Gnome Proxy settings. On Fedora you can find these settings in System -> Preferences -> Internet and Network -> Network Proxy

There you have to change the Proxy settings to 'Direct Internet connection'. If you are using a Proxy you will have to use the proxy.c fix or just wait for version 2.5.2

comment:11 Changed 11 years ago by trac-robot

  • Status changed from pending to closed

This ticket was closed automatically by the system. It was previously set to a Pending status and hasn't been updated within 14 days.

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!