Summary: | Session management: wrong windows positions | ||
---|---|---|---|
Product: | [Unmaintained] knotes | Reporter: | PCB <bugreports> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | kevin.kofler, kwin-bugs-null, notmart, s2, scott+kde, the.warl0ck.1989 |
Priority: | NOR | ||
Version: | 4.9.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Bug Depends on: | |||
Bug Blocks: | 209936 |
Description
PCB
2009-07-22 11:34:31 UTC
don't think it has anything to do with plasma, more with the session manager itself what is the component? When choosing the application from the application list while entering the bug it was not clear to me where the responisbility for session management lies. Does that belong to kwin? And... how do I find out what the component is? kwin stores and reloads geometries across sessions. session vars are stored in ~/.kde/share/config/session/ (might be ~/.kde4/...) look for the knotes_* files. in particular if there're write protected entries, all expected entries and (if the solution isn't obvious from that) you can compare them against the notes from ~/.kde/share/apps/knotes/notes/. You can also attach both for inspection. Seeing the same thing on Kubuntu 10.04 with KNotes 3.9 / KDE 4.4.2. On a fresh login, all the notes I had open across several desktops will usually reappear stacked on top of each on a single desktop. So in my case the size/position of the notes is affected as well as the desktop. Worked around by: 1. Excluding "knotes" and "/usr/bin/knotes" from session management 2. Starting knotes explicitly at login using an Autostart job Now all my notes reappear where I left them. Its 2011. Bug still exists. Anyone recommend a replacement for knotes? Still valid in KDE 4.9.0, setting status to confirmed. *** Bug 254944 has been marked as a duplicate of this bug. *** Not reproducible with KDE 4.10 *** This bug has been marked as a duplicate of bug 196977 *** |