[plasmashell] [Bug 365602] Multi screen issues: black screen, wrong panel positions, plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=365602 --- Comment #6 from Tim Eberhardt --- I could not reproduce it the same way with the live image like in my normal setup. Could be fixed but I'm not sure. In what plasmashell version this fix will be in? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365602] Multi screen issues: black screen, wrong panel positions, plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=365602 --- Comment #5 from Tim Eberhardt --- I will test it with the krypton live image the next days. I tried to upgrade my KDE install to the latest unstable but that would brake a lot of stuff in my current install. I'm already on factory for KDE but the step to unstable seems a bit more complicated. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 366403] KScreenlocker not unlockable when there are multiple sessions on NFS home
https://bugs.kde.org/show_bug.cgi?id=366403 --- Comment #6 from Tim Eberhardt --- I now tested with XDG_CACHE_HOME set to somewhere under /var/tmp which gets then populated with some stuff, but brings no difference to this problem. All settings should remain in the users home. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 366403] KScreenlocker not unlockable when there are multiple sessions on NFS home
https://bugs.kde.org/show_bug.cgi?id=366403 --- Comment #4 from Tim Eberhardt --- I don't know what else could be adjusted but the socket, cache and tmp links under ~/.kde4 point to /run/..., /var/tmp/... and /tmp/... respectively. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 366403] KScreenlocker not unlockable when there are multiple sessions on NFS home
https://bugs.kde.org/show_bug.cgi?id=366403 --- Comment #2 from Tim Eberhardt --- Unfortunately kscreenlocker_greet is working perfectly when I run it in gdb or in a pure shell with or without --testing option. Only if I wait for the set timeout or hit the shortcut to lock the screen I get the error described above. Additionally I have observed that the second session has not to be locked to crash kscreenlocker on the first session. It begins to happen as soon as there is a newer session then the one running. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 366403] New: KScreenlocker not unlockable when there are multiple sessions on NFS home
https://bugs.kde.org/show_bug.cgi?id=366403 Bug ID: 366403 Summary: KScreenlocker not unlockable when there are multiple sessions on NFS home Product: kscreenlocker Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tim.eberha...@tu-bs.de CC: bhus...@gmail.com, mgraess...@kde.org We have many openSUSE Leap clients with NFS homes. When we leave a client running and go (eg. for presentation purposes in a conference room) to another client, log in there and the sessions gets locked, the first session isn't unlockable anymore. You can only see a message which advises you to use "loginctl unlock-sessions" to remove the lock. But for normal users this isn't possible. Reproducible: Always Steps to Reproduce: 1. On machine A lock your session 2. Go to machine B and log in 3. Lock session on machine B, too 4. Try to unlock session on machine A Actual Results: Session on machine A can not be unlocked over kscreenlocker. Only root with "loginctl unlock-sessions" can unlock it. Expected Results: Session should be unlockable over kscreenlocker. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 360792] akonadi_davgroupware_resource crashes constandly
https://bugs.kde.org/show_bug.cgi?id=360792 --- Comment #5 from Tim Eberhardt --- Created attachment 100094 --> https://bugs.kde.org/attachment.cgi?id=100094&action=edit new crash dump with frameworks 5.24 and apps 16.04.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365602] Multi screen issues: black screen, wrong panel positions, plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=365602 --- Comment #3 from Tim Eberhardt --- Created attachment 100061 --> https://bugs.kde.org/attachment.cgi?id=100061&action=edit plasmashell debug info -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365602] Multi screen issues: black screen, wrong panel positions, plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=365602 --- Comment #2 from Tim Eberhardt --- Created attachment 100060 --> https://bugs.kde.org/attachment.cgi?id=100060&action=edit xsessions-errors of office #2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365602] Multi screen issues: black screen, wrong panel positions, plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=365602 --- Comment #1 from Tim Eberhardt --- Created attachment 100059 --> https://bugs.kde.org/attachment.cgi?id=100059&action=edit xsessions-errors of office #1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365602] New: Multi screen issues: black screen, wrong panel positions, plasmashell segfaults
https://bugs.kde.org/show_bug.cgi?id=365602 Bug ID: 365602 Summary: Multi screen issues: black screen, wrong panel positions, plasmashell segfaults Product: plasmashell Version: 5.7.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: tim.eberha...@tu-bs.de CC: plasma-b...@kde.org I have a laptop for my work which I use at two different offices. On office #1 I have a single 1600x900 monitor connected via DVI to a dock. On office #2 I have 2x 1920x1200 monitors connected via DP to a dock. On both offices when I log in to KDE the external monitors are black. I can drag the mouse over and see the cursor (so the screens are active) but no desktop, wallpaper or widgets. I then have to go to the screen settings, disable the external monitors, click apply (which always can be clicked twice), wait some seconds, re-enable the screens, eventually resize to correct resolution, click apply again (twice). After this and a short wait the desktops are showing on the other screens. In office #2 I always have to drag all my panels from the internal screen to the two other screens, as they are all on screen 1 on top of each other. Additionally plasmashell is crashing in office #2 right after applying the final changes in kscreen with a segfault. Reproducible: Always Steps to Reproduce: 1. start laptop on dock 2. log in to plasma Actual Results: black external screens Expected Results: desktops with all panels and widgets on their place on all screens Specs of laptop: ThinkPad L440, Intel i5-4200M, 8GB RAM, UltraDock docks System specs: openSUSE Tumbleweed with KDE from Factory repos (plasma 5.7.1, frameworks 5.24.0, applications 16.04.3, Qt 5.6.1, kernel 4.6.4) I'm attaching some files for debugging: xsession-errors1: .xsessions-errors from office #1 xsession-errors2: .xsessions-errors from office #2 plasmashell-20160713-090550.kcrash.txt: crash info from office #2 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 360792] akonadi_davgroupware_resource crashes constandly
https://bugs.kde.org/show_bug.cgi?id=360792 --- Comment #4 from Tim Eberhardt --- Created attachment 99035 --> https://bugs.kde.org/attachment.cgi?id=99035&action=edit crash dump -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 360792] akonadi_davgroupware_resource crashes constandly
https://bugs.kde.org/show_bug.cgi?id=360792 Tim Eberhardt changed: What|Removed |Added CC||tim.eberha...@tu-bs.de --- Comment #3 from Tim Eberhardt --- Can confirm this. openSUSE Tumbleweed, KDE from Factory repository Applications 16.04 Frameworks 5.22 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 349581] Akonadi DAV Resource does not sync all calendars (at least on Communigate or ownCloud)
https://bugs.kde.org/show_bug.cgi?id=349581 --- Comment #18 from Tim Eberhardt --- Just to inform those that may be interested in the Communigate issue. The bug was reported by me to Stalker Software and fixed in v6.1.7 of CommunigatePro. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 354908] Recurring events are missing on a caldav resource (Zimbra)
https://bugs.kde.org/show_bug.cgi?id=354908 Tim Eberhardt changed: What|Removed |Added CC||tim.eberha...@tu-bs.de --- Comment #1 from Tim Eberhardt --- I can confirm this Bug with version 5.0.3 (Gentoo) -- You are receiving this mail because: You are watching all bug changes.
