Bug 438042 - pidgin crashes after upgrade to fc8
pidgin crashes after upgrade to fc8
Product: Fedora
Classification: Fedora
Component: pidgin (Show other bugs)
i686 Linux
low Severity high
: ---
: ---
Assigned To: Warren Togami
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-03-18 15:36 EDT by Jes Sorensen
Modified: 2008-03-19 02:58 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-19 02:58:09 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 Jes Sorensen 2008-03-18 15:36:43 EDT
Description of problem:
Pidgin fails to start after upgrade to FC8

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

How reproducible:
Every time

Steps to Reproduce:
1. Start pidgin
Actual results:
[jes@mini ~]$ pidgin
libnm_glib_nm_state_cb: dbus returned an error.
  (org.freedesktop.DBus.Error.ServiceUnknown) The name
org.freedesktop.NetworkManager was not provided by any .service files

Expected results:

Additional info:
After upgrading my Mac Mini from Fedora Core 7 to Fedora Core 8, I am now
getting the above strage error message when I try to launch pidgin.

I do not run Network Manager on this box as it is assigned a static IP address
and I am unable to get that working with NM. NM itself crashes when I try to add
a new connection as a regular user. However it's beyond me why pidgin cares
about network manager in the first place.
Comment 1 Stu Tomlinson 2008-03-18 15:48:52 EDT
That error message is harmless, simply indicating that NetworkManager is not

Please install the debuginfo packages (with "debuginfo-install pidgin") and get
a backtrace as described on http://fedoraproject.org/wiki/StackTraces
Comment 2 Jes Sorensen 2008-03-19 02:58:09 EDT
Ok, this is the weirdest I've seen.

After installing the 250MB of debuginfo packages, I am suddenly able to start
pidgin again. No idea whats changned, but I'll close this one for now, and
reopen if this happens again.


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