Bug 57003 - Gnome segmentation fault after using KDE desktop switching tool
Summary: Gnome segmentation fault after using KDE desktop switching tool
Keywords:
Status: CLOSED DUPLICATE of bug 55119
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: gnome-core
Version: 7.2
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-12-03 00:46 UTC by Art Fore
Modified: 2007-04-18 16:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2001-12-04 15:35:10 UTC
Embargoed:


Attachments (Terms of Use)

Description Art Fore 2001-12-03 00:46:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; DigExt)

Description of problem:
Was using KDE GUI, used the desktop switching tool to switch to GNOME, 
upon rebooting, it came up with segmentation fault and no control pane. 
Start here, etc is on display, can go into programs with Nautilus, but no 
control panel

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


How reproducible:
Couldn't Reproduce

Steps to Reproduce:
1.Cannot reproduce since I cannot get back to KDE.
2.
3.
	

Actual Results:  Cannot reproduce since I cannot get back to KDE

Expected Results:  Switch to Gnome without segmentation fault

Additional info:

Upgraded to 2.4.9-13 kernel, has Nvidia 1.0-2313 Video drivers on 1Ghz 
Dell Inspiron with 512 meg ram.

Comment 1 Art Fore 2001-12-03 23:57:05 UTC
Finally got switched back to KDE using switchdesk in mode 3. Still have 
problems with Konquerer, reinstalled Galeon and it now works in KDE. Am 
presently inprocess of installing Ximian Gnome desktop tomorrow morning when I 
get to work with high speed internet connection. Hopefully this will fix Gnome 
and I will get rid of KDE.



Comment 2 Havoc Pennington 2002-02-25 23:09:32 UTC

*** This bug has been marked as a duplicate of 55119 ***


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