Bug 438042 - pidgin crashes after upgrade to fc8
Summary: pidgin crashes after upgrade to fc8
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: pidgin
Version: 8
Hardware: i686
OS: Linux
low
high
Target Milestone: ---
Assignee: Warren Togami
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-03-18 19:36 UTC by Jes Sorensen
Modified: 2008-03-19 06:58 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-03-19 06:58:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Jes Sorensen 2008-03-18 19:36:43 UTC
Description of problem:
Pidgin fails to start after upgrade to FC8

Version-Release number of selected component (if applicable):
pidgin-2.4.0-1.fc8

How reproducible:
Every time

Steps to Reproduce:
1. Start pidgin
2.
3.
  
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 19:48:52 UTC
That error message is harmless, simply indicating that NetworkManager is not
running.

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 06:58:09 UTC
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.

Thanks,
Jes



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