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

List:       kwrite-devel
Subject:    [Bug 101855] kate: two of each window restored with session
From:       Peter <i.vanderheijden1 () chello ! nl>
Date:       2005-05-26 11:44:30
Message-ID: 20050526114430.484.qmail () ktown ! kde ! org
[Download RAW message or body]

------- 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=101855         




------- Additional Comments From i.vanderheijden1 chello nl  2005-05-26 13:44 -------
I have the same bug, using KDE 3.4 (upgraded from 3.3.2) and Slackware-Current (the \
install started out with 10.1). I'm using the official Slackware packages. I couldn't \
find much info for this bug on google though, so I suppose it's not \
Slackware-specific. I've had the same bug happening with two different situations, \
both regarding starting kate at session-start/-restore. The first is with kate \
opening a text-file in my ~/.kde/Autostart dir. I never started kate with this file \
open so it must have started itself (which, afaik, is the whole point of Autostart \
;)). However, if I remember correctly, it opened this file with 2 instances of kate \
the even first time it got opened. I closed both instances every time my session \
started, and it reapeared (with 2 kate's) the next time I started a KDE session (it \
took me some time to figure out it was because the file was in Autostart). Both \
instances got started in whatever desktop was in front of me at the moment

With the normally saved kate sessions (where kate was open when I logged out, I use \
'restore previous session on login' option), the first instance of kate that gets \
started, starts in the desktop that it was in when I logged out. The second instance \
starts in whatever desktop that is in front of me at the moment.

I don't know how to get debugging info from a program that starts when starting the \
KDE session (I do, however, start X by using 'startx' from a terminal, don't know if \
it helps if I log it's output). If anyone could explain to me how to do it, I'd be \
glad to post the debugging output. 

As far as I can remember, it happened every time I restore a session with kate in it \
since I use KDE 3.4. It might have happened in older KDE versions, but I'm not sure.

I tried it with moving the ~/.kde/share/config/katerc file. The first startup after \
the moving only showed on instance of kate. However, when shutting down this session \
and starting a new one, kate appeared with twice again, opening the same file (where \
it should be once), using the katerc generated in the last session (the one after \
moving the katerc (to katerc.old)). So my guess is it happens whenever there's an \
existing katerc (since it happend to me with two different katerc's).

I just checked for any differences between the first opened kate window (in the right \
desktop, the one where it was when the session ended) and the second (opened in \
whatever desktop was in front of me). The only difference I saw, was that the first \
window had a split-window (split horizontally) view, showing two different files \
(just as it was when I closed the session). The second one, however, only shows the \
file displayed in the lower frame of the first one (this frame is way bigger then the \
above one).

When I do a "ps aux | grep kate" (only tried it once, after the last start (with the \
new katerc)), I only see ONE instance of kate running (kate [kdeinit] kate -session \
10b7d9c965000111707566000000050080058_1117114578_701800).

If more info is needed, please contact me or reply to this bug report.

Hope this helps ;).
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel


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