Knotes always remembers the note's original desktop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdepim (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: kdepim
I checked off the "Remember Desktop" box in Knotes. However, when I enter a new note, it still seems to stick it on the one desktop that it was entered on originally.
For example, if I am on desktop 1, and add a note, then right click on KNotes, click "Hide all notes", switch to desktop 2, right click on KNotes and click "Show all notes", the note I just added does not show. If I switch back to desktop 1 I can see it opened there. I expected all notes to open on my current desktop, desktop 2.
Another example: if I close the note, switch to desktop 2, left click on the KNotes icon, and select the note I just added, the system switches to desktop 1 automatically, where the note is open (I would expect it to open on the current desktop, desktop 2, instead).
I checked the note's file itself (libcal-nnnnn under .kde4/share/
[Display]
RememberDesktop
bgcolor=255,255,189
[General]
version=3.9
[WindowDisplay]
desktop=1
position=54,271
My system's version data is below.
Description: Ubuntu 9.10
Release: 9.10
kdepim:
Installed: 4:4.3.2-0ubuntu6
Candidate: 4:4.3.2-0ubuntu6
Version table:
*** 4:4.3.2-0ubuntu6 0
500 http://
100 /var/lib/
ProblemType: Bug
Architecture: amd64
Date: Mon Nov 30 11:39:42 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/knotes
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelMo
Package: knotes 4:4.3.2-0ubuntu6
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: kdepim
Uname: Linux 2.6.31-14-generic x86_64
Hi there!
Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https:/ /bugs.kde. org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.
Thanks!