Bug 23785 - probs running konqueror inside gnome session
Summary: probs running konqueror inside gnome session
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: kdebase
Version: 7.1
Hardware: i386
OS: Linux
low
low
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: David Lawrence
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-01-11 11:02 UTC by Tim Waugh
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-02-22 13:18:07 UTC
Embargoed:

Attachments (Terms of Use)

Description Tim Waugh 2001-01-11 11:02:09 UTC 
When running konqueror from inside a GNOME session I get warning dialogs about 'did not respond to saveyourself'.  Clicking on 'Remove program' makes them go away, and doesn't stop konqueror or anything.

(Why I'm doing this: I like GNOME's ability to launch applications from key combinations [can't KDE do this??], but konqueror is a lot faster than mozilla right now.)
Comment 1 David Mason 2001-01-11 15:49:41 UTC 
hp, problem with conflicting session management?
Comment 2 Havoc Pennington 2001-01-11 16:32:24 UTC 
The error means what it says - Konqueror connects to the session manager, then
gets a SaveYourself message from the session manager and doesn't respond.
Konqueror bug. It should either not connect to the SM or respond to requests to
save.
Comment 3 Bernhard Rosenkraenzer 2001-01-12 11:32:36 UTC 
Bug (and feature request about keyboard shortcuts) forwarded to
submit.org.

From a quick look at the code, Konqueror *does* respond to SaveYourself, but
apparently in a different way from what GNOME expects.
Comment 4 Tim Waugh 2001-02-09 11:28:10 UTC 
I think this may have been fixed by a recent gnome-core changes.  I'll update
when I retest.
Comment 5 Bernhard Rosenkraenzer 2002-02-21 13:33:17 UTC 
Any news on this?
Comment 6 Tim Waugh 2002-02-22 13:18:02 UTC 
Sorry, no.  Feel free to close it.
Note You need to log in before you can comment on or make changes to this bug.