Bug 152256 - Switching wireless networks causes kdeinit to fail
Summary: Switching wireless networks causes kdeinit to fail
Status: RESOLVED FIXED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-13 17:32 UTC by Carlos Castillo
Modified: 2011-01-06 00:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Castillo 2007-11-13 17:32:02 UTC 
Version:            (using KDE KDE 3.5.8)
Installed from:    Gentoo Packages
Compiler:          gcc-4.2.2 
OS:                Linux

When switching wireless networks inside a KDE session (eg: when using knetworkmanager), if the hostname is changed, all KDE-apps will fail to launch with a message like "KDEInit could not launch 'konsole'", "KLauncher could not be reached via DCOP.", or simply fail to start up at all.

A similar bug was filed in 2001, where the user was warned to not change the hostname since it would break IPC. This is most likely the same problem, however now it is no longer the user's fault for the hostname change.
Comment 1 Samuel Brack 2011-01-05 15:57:07 UTC 
Is this still a valid bug and can someone confirm this?
Comment 2 Samuel Brack 2011-01-06 00:49:12 UTC 
Closing this bug report because of the use of DBUS in KDE now.