Opened 11 years ago

Closed 11 years ago

#6247 closed defect

Pidgin Crashing on start-up using both desktop icon & from terminal.

Reported by: trennor Owned by:
Milestone: Component: pidgin (gtk)
Version: Keywords: crash, startup


I try to start Pidgin - which has worked very well for me for the past 10 months or so - and last night, after a terminal reset - I started experiencing problems:

I did an -strace; which yielded this message:

--- SIGSEGV (Segmentation fault) @ 0 (0) --- write(2, "Pidgin has segfaulted and attempted to dump a core file.\nThis is a bug in the software and has happened through\nno fault of your own.\n\nIf you can reproduce the crash, please notify the Pidgin\ndevelopers by reporting a bug at\n\n\nPlease make sure to specify what you were doing at the time\nand post the backtrace from the core file. If you do not know\nhow to get the backtrace, please read the instructions at\n\n\nIf you need further assistance, please IM either SeanEgn? or \nLSchiere (via AIM). Contact information for Sean and Luke \non other protocols is at\n\n", 637Pidgin 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.

rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0 tgkill(26779, 26779, SIGABRT) = 0 --- SIGABRT (Aborted) @ 0 (0) --- +++ killed by SIGABRT +++ Process 26779 detached

It goes on to ask me to report this to you. I'm running this version of pidgin on an FC7 linux.

Change History (2)

comment:1 Changed 11 years ago by QuLogic

  • pending changed from 0 to 1

But you missed the part where it said to get a backtrace.

comment:2 Changed 11 years ago by trac-robot

  • pending changed from 1 to 0
  • Status changed from new 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!