[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    force it into 3.1? (Re: [RFC+PATCH] xp-like fast switching)
From:       Oswald Buddenhagen <ossi () kde ! org>
Date:       2002-10-01 13:17:04
[Download RAW message or body]

On Tue, Sep 24, 2002 at 08:09:32PM +0200, Allan Sandfeld Jensen wrote:
> This is what is needed right now for KDE 3.1. I would consider it a
> bug-fix.
> Take a look at how it has worked for the last month or so:
> 1. You go to lunch and therefore click on lock desktop.
> 2. You come back and find a kdm login-screen, and you think to
> yourself: WTF??
> 3. You lock in again and for the rest of the day wonder why your
> desktop is so damn slow all of a sudden.
> 4. At the end of the day you log out and find your old locked session
> and again you think to yourself: WFT??
> Atleast this is what I did the first time I discovered this hidden
> feature. We need to be able to see locked sessions in kdm, or this has
> to be disabled (atleast by default) for KDE 3.1. I naivly thought that
> was the plan all along.
>
... and attached is the other side. :)

so now i'm wondering, if we should not consider my patch a bugfix and
simply put it into 3.1. it is part of suse 8.1 (which is kde 3.0.3 based,
btw), so they seem to consider it stable - except for the kdesktop_lock
part it's only a few LOC anyway. the one problem we have is one new
string in kdesktop, one in kicker and two in kdesktop_lock and a missing
icon (although suse simply reused some icon called "start" or something
(a rocket)).
should we?

greetings

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.


Return-Path: <anonymous@ktown.kde.org>
Delivered-To: ossi@master.kde.org
Received: (qmail 29222 invoked by uid 1055); 1 Oct 2002 07:35:14 -0000
Delivered-To: kde.org-ossi@kde.org
Received: (qmail 29218 invoked by uid 30); 1 Oct 2002 07:35:14 -0000
Date: 1 Oct 2002 07:35:14 -0000
Message-ID: <20021001073514.29217.qmail@ktown.kde.org>
From: Paulo Dias <pcd@ieg.com.br>
To: ossi@kde.org
Sender: owner@bugs.kde.org
Reply-To: bugmail@bugs.kde.org
Subject: [Bug 48537] New: kdm isn't appearing when i do a lock screen         
X-Bugzilla-URL: http://bugs.kde.org/ 
X-Bugzilla-Reason: AssignedTo     
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=iso-8859-1

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=48537     
           Summary: kdm isn't appearing when i do a lock screen
           Product: kdm
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: ossi@kde.org
        ReportedBy: pcd@ieg.com.br


Version:            (using KDE Devel)
Installed from:    Compiled sources
Compiler:          gcc 2.95.3 
OS:          Linux

I'm running kde 3.1 beta 2 (3.0.8 cvs version date 29/9/2002 -although this behaviour \
is current for almost a month now) compiled by hand in slackware 8.1. The problem: \
when i click on the lock button, kdesktop_lock is properly called with the \
--forcelock option but instead of locking my area, running kscreensaver and opening a \
second X with the KDM logon, which is the standard procedure, only the kscreensaver \
is called. No second X, no nothing. I've runned genkdmconf --no-old to toss the old \
scripts and create the news ones which appear to be fine in \
/opt/kde3/share/config/kdm, but still no new X (running Xfree86 4.2.1 BTW). This was \
working till past month, now it appears to be broken. i've runned out of ideas. \
Calling kdesktop_lock via dcop also doesn't open a second KDM.



[prev in list] [next in list] [prev in thread] [next in thread]