Bug 492904

Summary:	Pidgin does displays neither a main window nor running-icon
Product:	[Fedora] Fedora	Reporter:	Bill Adams <badams>
Component:	pidgin	Assignee:	Warren Togami <wtogami>
Status:	CLOSED NOTABUG	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	10	CC:	stu, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-03-30 22:35:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bill Adams 2009-03-30 16:26:55 UTC

Description of problem:

After running yum update this morning and rebooting (twice), pidgin will start but the main window never displays. If I kill the program (or SIGINT from the command line) it flashes the window and exits.

The icon never appears in the menu-bar either.

I removed mugshot, renamed .purple and none of those things helped. When I renamed .purple I did get the dialog asking to set up a new account. Pressing Cancel did the same thing: no main window and only a flash of it when I pressed CTRL+c. 



Version-Release number of selected component (if applicable):

pidgin.i386 0:2.5.5-1.fc10


How reproducible:

Every time.


Steps to Reproduce:
1. yum -y update
2. pidgin
3.
  

Actual results:

No main window nor icon.


Expected results:

Main window / Icon


Additional info:

Running as root: No window, SIGINT causes segfault:


[root@xxxx bill]# pidgin 

(pidgin:4790): GStreamer-CRITICAL **: gst_caps_copy: assertion `GST_IS_CAPS (caps)' failed

(pidgin:4790): GStreamer-CRITICAL **: gst_caps_do_simplify: assertion `caps != NULL' failed

(pidgin:4790): GStreamer-CRITICAL **: gst_caps_unref: assertion `caps != NULL' failed
^C*** glibc detected *** pidgin: free(): invalid pointer: 0x09a2ec10 ***
======= Backtrace: =========
[snip]

Comment 1 Bill Adams 2009-03-30 22:35:14 UTC

Ugh, I was afraid of this. Waiting seems to have fixed it. Perhaps there were strange network issues on my end.