Bug 492904 - Pidgin does displays neither a main window nor running-icon
Pidgin does displays neither a main window nor running-icon
Product: Fedora
Classification: Fedora
Component: pidgin (Show other bugs)
i386 Linux
low Severity high
: ---
: ---
Assigned To: Warren Togami
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-03-30 12:26 EDT by Bill Adams
Modified: 2009-03-30 18:35 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-03-30 18:35:14 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bill Adams 2009-03-30 12:26:55 EDT
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

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: =========
Comment 1 Bill Adams 2009-03-30 18:35:14 EDT
Ugh, I was afraid of this. Waiting seems to have fixed it. Perhaps there were strange network issues on my end.

Note You need to log in before you can comment on or make changes to this bug.