[kmail2] [Bug 401760] New: RFE: Support enigmail style subject encryption
https://bugs.kde.org/show_bug.cgi?id=401760 Bug ID: 401760 Summary: RFE: Support enigmail style subject encryption Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: net...@crc.id.au Target Milestone: --- As per the enigmail documentation, it would be great to have this feature compatible within kmail. https://www.enigmail.net/index.php/en/user-manual/handbook-faq#How_can_I_encrypt_the_Subject.3F -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #105 from Steven Haigh --- Probably the same issue. Its been around for ever and I'm not sure anyone cares... -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #98 from Steven Haigh <net...@crc.id.au> --- Thanks for the link. @Daniel Vrátil - Can you please advise on the thoughts to resolve this? Seems to be a long standing / high impact issue with no progress. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #96 from Steven Haigh <net...@crc.id.au> --- Thanks for the additional info - would it be too much to ask to find the previous patch? I guess the idea was along the lines of a LIMIT 1 in scenarios where more than one result would kill the world. Ideally, this could be a runtime fix - and the fsck ability of akondactl could remove duplicate entries. I still use this code in the SQL tab of akonadiconsole: DELETE FROM pimitemtable WHERE pimitemtable.id in ( SELECT id FROM ( SELECT id FROM pimitemtable LEFT OUTER JOIN ( SELECT MIN(pimitemtable.id) as RowId, pimitemtable.remoteId, pimitemtable.collectionId FROM pimitemtable GROUP by pimitemtable.remoteId, pimitemtable.collectionId ) as KeepRows ON pimitemtable.id = KeepRows.RowId WHERE KeepRows.RowId IS NULL ) AS foo ) Source: https://wiki.meurisse.org/wiki/Workarounds#Kmail:_Multiple_merge_candidates.2C_aborting This seems to resurrect things until it occurs again. Still annoying and really needs to be fixed. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #94 from Steven Haigh <net...@crc.id.au> --- Interestingly, I disabled the local filters on my gmail account today from within Kmail and haven't had to restart akonadi all day. Maybe there is something within the local filters that causes things to die? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #93 from Steven Haigh <net...@crc.id.au> --- I use kmail with Dovecot + Sieve at home - and I never seem to have an issue. I use kmail with Gmail at work with local filters, and it dies multiple times a day. Every time it requires the documented (in this report anyway) SQL query to fix and a restart of the akonadi services via akonadictl restart. Same distro, same kmail / framework versions. I'm in the middle of setting up a local set of folders and syncing the gmail account with offlineimap to see if that suffers the same problem - but I think this is going to be the only workaround that is somewhat reliable... -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #90 from Steven Haigh <net...@crc.id.au> --- So as we're now looking at nearly 4 years on with this issue, are we any closer to looking for a final resolution? I see new commits on the kmail git repo, but it looks like there's only one person looking after it? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #89 from Steven Haigh <net...@crc.id.au> --- Well, me being a sucker for punishment - with a new laptop - I set up kmail on a fresh install of Fedora 27. Sync'ed my gmail account to it. The very next day, hit by this problem. >From the console: org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Unknown error." org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Unknown error." org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Unknown error." org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Unknown error." org.kde.pim.akonadicore: Creating/updating items from the akonadi database failed: "Multiple merge candidates, aborting" So yeah - this is still an issue. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #87 from Steven Haigh <net...@crc.id.au> --- I never had problems sending - only receiving... I've often wondered if the 'IMAP' connection to gmail goes away unexpectedly that it causes this problem - but have had no real way to prove this. Just leaving kmail open for a couple of hours with the auto-check for every 10-15 minutes is enough to cause the problem. It seems to get worse when using mail filters - as I have quite a few. In fact, thinking out loud, I wonder if the mail filters have any contribution to this? -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #85 from Steven Haigh <net...@crc.id.au> --- That is interesting. I am currently using Fedora 27 - which includes dovecot 2.2.33 without issues. In fact, I'm not sure I have ever seen this issue with dovecot as the IMAP server. My problems are purely with the gmail integration. I was assuming that this problem only affects gmail. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #83 from Steven Haigh <net...@crc.id.au> --- Heh - funny you should mention this - I've recently had to do the same for my work gmail based mail. Thunderbird is s slow by comparison - kmail is clearly better - but having mail break a dozen times a day isn't usable. I still use kmail for my home dovecot IMAP mail - and its perfect - but akonadi really doesn't like gmail at all. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 --- Comment #80 from Steven Haigh <net...@crc.id.au> --- Just to give this a nudge, I still see this with 17.12 on Fedora 27. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 388005] Impossible to send emails : "Connection to server interrupted".
https://bugs.kde.org/show_bug.cgi?id=388005 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added CC||net...@crc.id.au --- Comment #1 from Steven Haigh <net...@crc.id.au> --- On a similar note, using Fedora 27 + 17.12 kmail, I get the following error with smtp.gmail.com: "Failed to transport message. Server error" I can't find any way to display what the error actually is - but this was working prior to the 17.12 update. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 384201] SMB3 is broken in Dolphin
https://bugs.kde.org/show_bug.cgi?id=384201 --- Comment #4 from Steven Haigh <net...@crc.id.au> --- Oh - and I'm not quite sure if it is related, but I do not have anything configured for 'max protocol' on either the client or server side. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 384201] SMB3 is broken in Dolphin
https://bugs.kde.org/show_bug.cgi?id=384201 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added CC||net...@crc.id.au --- Comment #3 from Steven Haigh <net...@crc.id.au> --- I also see this with Fedora 27. I can list the shares on a samba server, but can't access any content on them. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381180] UI is horrible over ssh + X-Forward connection
https://bugs.kde.org/show_bug.cgi?id=381180 --- Comment #5 from Steven Haigh <net...@crc.id.au> --- On the laptop I ssh into to run kmail: # dnf list mesa* Last metadata expiration check: 0:38:08 ago on Wed 04 Oct 2017 12:56:14 AEDT. Installed Packages mesa-dri-drivers.x86_64 17.2.1-1.fc27 @updates-testing mesa-filesystem.x86_64 17.2.1-1.fc27 @updates-testing mesa-libEGL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libGL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libGLU.x86_64 9.0.0-13.fc27 @fedora mesa-libOpenCL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libgbm.x86_64 17.2.1-1.fc27 @updates-testing mesa-libglapi.x86_64 17.2.1-1.fc27 @updates-testing mesa-libwayland-egl.x86_64 17.2.1-1.fc27 @updates-testing mesa-libxatracker.x86_64 17.2.1-1.fc27 @updates-testing On the machine I'm SSH'ing FROM: # dnf list mesa* Last metadata expiration check: 0:22:26 ago on Wed 04 Oct 2017 13:11:39 AEDT. Installed Packages mesa-dri-drivers.i686 17.2.1-1.fc27 @updates-testing mesa-dri-drivers.x86_64 17.2.1-1.fc27 @updates-testing mesa-filesystem.i686 17.2.1-1.fc27 @updates-testing mesa-filesystem.x86_64 17.2.1-1.fc27 @updates-testing mesa-libEGL.i686 17.2.1-1.fc27 @updates-testing mesa-libEGL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libGL.i686 17.2.1-1.fc27 @updates-testing mesa-libGL.x86_64 17.2.1-1.fc27 @updates-testing mesa-libGLU.x86_64 9.0.0-13.fc27 @fedora mesa-libOpenCL.
[kmail2] [Bug 381180] UI is horrible over ssh + X-Forward connection
https://bugs.kde.org/show_bug.cgi?id=381180 --- Comment #3 from Steven Haigh <net...@crc.id.au> --- Output from the shell: $ dbus-launch kmail libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast Could not initialize GLX KCrash: Application 'kmail' crashing... KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit sock_file=/run/user/1000/kdeinit5_localhost_10 kf5.kwidgetsaddons: Invalid pixmap specified. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast No XVisualInfo for format QSurfaceFormat(version 2.0, options QFlags(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(SingleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile)) Falling back to using screens root_visual. [1]+ Stopped dbus-launch kmail -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381180] UI is horrible over ssh + X-Forward connection
https://bugs.kde.org/show_bug.cgi?id=381180 --- Comment #2 from Steven Haigh <net...@crc.id.au> --- I also note that with the latest kmail, I get the following crash when trying to start kmail and forward its UI to my desktop via SSH: Application: kmail (kmail), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #4 0x7f28cc5766bb in raise () from /lib64/libc.so.6 #5 0x7f28cc578447 in abort () from /lib64/libc.so.6 #6 0x7f28cd2a5941 in QMessageLogger::fatal(char const*, ...) const () from /lib64/libQt5Core.so.5 #7 0x7f289e540004 in QGLXContext::init(QXcbScreen*, QPlatformOpenGLContext*) () from /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #8 0x7f289e53dd87 in QXcbGlxIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from /usr/lib64/qt5/plugins/xcbglintegrations/libqxcb-glx-integration.so #9 0x7f28a0e49971 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from /lib64/libQt5XcbQpa.so.5 #10 0x7f28cd9d08bf in QOpenGLContext::create() () from /lib64/libQt5Gui.so.5 #11 0x7f28c3425b44 in QtWebEngineCore::initialize() () from /lib64/libQt5WebEngineCore.so.5 #12 0x7f28cd457f8f in QCoreApplicationPrivate::init() () from /lib64/libQt5Core.so.5 #13 0x7f28cd995e6c in QGuiApplicationPrivate::init() () from /lib64/libQt5Gui.so.5 #14 0x7f28ce09c8a9 in QApplicationPrivate::init() () from /lib64/libQt5Widgets.so.5 #15 0x7f28d291e9a4 in KontactInterface::PimUniqueApplication::PimUniqueApplication(int&, char***) () from /lib64/libKF5KontactInterface.so.5 #16 0x558b7a3e1a42 in main () -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 378315] KMail crash on logout
https://bugs.kde.org/show_bug.cgi?id=378315 --- Comment #10 from Steven Haigh <net...@crc.id.au> --- I can confirm that this still occurs with: $ rpm -qa | grep qtwebengine qt5-qtwebengine-5.9.0-4.fc26.x86_64 $ rpm -qa | grep kmail | sort kf5-kmailtransport-17.04.1-1.fc26.x86_64 kf5-kmailtransport-akonadi-17.04.1-1.fc26.x86_64 kmail-17.04.1-3.fc26.x86_64 kmail-account-wizard-17.04.1-1.fc26.x86_64 kmail-libs-17.04.1-3.fc26.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 338658] GMail, Novell Groupwise, other IMAP: "Multiple merge candidates, aborting"
https://bugs.kde.org/show_bug.cgi?id=338658 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added CC||net...@crc.id.au --- Comment #76 from Steven Haigh <net...@crc.id.au> --- For what its worth, I still see this with Fedora 26. rpm -qa | grep kmail | sort kf5-kmailtransport-17.04.1-1.fc26.x86_64 kf5-kmailtransport-akonadi-17.04.1-1.fc26.x86_64 kmail-17.04.1-3.fc26.x86_64 kmail-account-wizard-17.04.1-1.fc26.x86_64 kmail-libs-17.04.1-3.fc26.x86_64 $ rpm -qa | grep akonadi | sort akonadi-calendar-tools-17.04.1-1.fc26.x86_64 akonadiconsole-17.04.1-1.fc26.x86_64 akonadi-import-wizard-17.04.1-1.fc26.x86_64 kf5-akonadi-calendar-17.04.1-1.fc26.x86_64 kf5-akonadi-contacts-17.04.1-1.fc26.x86_64 kf5-akonadi-mime-17.04.1-1.fc26.x86_64 kf5-akonadi-notes-17.04.1-1.fc26.x86_64 kf5-akonadi-search-17.04.1-1.fc26.x86_64 kf5-akonadi-server-17.04.1-3.fc26.x86_64 kf5-akonadi-server-mysql-17.04.1-3.fc26.x86_64 kf5-kmailtransport-akonadi-17.04.1-1.fc26.x86_64 kf5-libkdepim-akonadi-17.04.1-1.fc26.x86_64 kf5-mailimporter-akonadi-17.04.1-1.fc26.x86_64 kf5-pimcommon-akonadi-17.04.1-1.fc26.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 378010] Generic High CPU Usage Rendering
https://bugs.kde.org/show_bug.cgi?id=378010 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added CC||net...@crc.id.au --- Comment #30 from Steven Haigh <net...@crc.id.au> --- I wonder if my report from re kwin_x11 belongs here too? https://bugs.kde.org/show_bug.cgi?id=378010 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381181] akonadiserver is launched every time kmail starts via SSH X-Forwarding.
https://bugs.kde.org/show_bug.cgi?id=381181 --- Comment #2 from Steven Haigh <net...@crc.id.au> --- I should mention that I connect to my laptop via: I connect to my laptop via: $ ssh -C -Y username@ Then launch kmail via: $ dbus-launch kmail -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381181] akonadiserver is launched every time kmail starts via SSH X-Forwarding.
https://bugs.kde.org/show_bug.cgi?id=381181 --- Comment #1 from Steven Haigh <net...@crc.id.au> --- May also be related to: https://bugs.kde.org/show_bug.cgi?id=381180 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381181] New: akonadiserver is launched every time kmail starts via SSH X-Forwarding.
https://bugs.kde.org/show_bug.cgi?id=381181 Bug ID: 381181 Summary: akonadiserver is launched every time kmail starts via SSH X-Forwarding. Product: kmail2 Version: 5.5.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: net...@crc.id.au Target Milestone: --- Created attachment 106093 --> https://bugs.kde.org/attachment.cgi?id=106093=edit Output of ps after multiple remote kmail launches. When launching kmail over SSH with X-Forwarding enabled, I notice that an instance of akonadiserver starts for every time kmail is launched - but it doesn't quit after quitting kmail. This leads to multiple akonadiserver processes running. Have attached the output of a ps due to anti-spam rules. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381180] UI is horrible over ssh + X-Forward connection
https://bugs.kde.org/show_bug.cgi?id=381180 --- Comment #1 from Steven Haigh <net...@crc.id.au> --- On a possibly related issue, I notice I have issues marking messages as read when using kmail via this method. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381180] New: UI is horrible over ssh + X-Forward connection
https://bugs.kde.org/show_bug.cgi?id=381180 Bug ID: 381180 Summary: UI is horrible over ssh + X-Forward connection Product: kmail2 Version: 5.5.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: net...@crc.id.au Target Milestone: --- I run kmail over SSH at times when I have a desktop system available. I connect to my laptop via: $ ssh -C -Y username@ When I log in, I currently have to issue 'akonadictl stop' from the laptop keyboard. At this point, I can usually launch kmail via SSH: $ dbus-launch kmail akonadi.collectionattributetable OK akonadi.collectionmimetyperelation OK akonadi.collectionpimitemrelation OK akonadi.collectiontableOK akonadi.flagtable OK akonadi.mimetypetable OK akonadi.parttable OK akonadi.parttypetable OK akonadi.pimitemflagrelationOK akonadi.pimitemtable OK akonadi.pimitemtagrelation OK akonadi.relationtable OK akonadi.relationtypetable OK akonadi.resourcetable OK akonadi.schemaversiontable OK akonadi.tagattributetable OK akonadi.tagremoteidresourcerelationtable OK akonadi.tagtable OK akonadi.tagtypetable OK org.kde.pim.webengineviewer: It's not necessary to check database now QSystemTrayIcon::setVisible: No Icon set this does not work on a KActionCollection containing actions! QDBusConnection: name 'org.kde.kwalletd5' had owner '' but we thought it was ':1.3' QPainter::begin: Paint device returned engine == 0, type: 3 QPainter::setCompositionMode: Painter not active QPainter::end: Painter not active, aborted It seems that when I do this, there are no icons or any type of theme applied to the UI. Text labels are visible, but no icons. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380855] kmail crashes with signal 11 on logout
https://bugs.kde.org/show_bug.cgi?id=380855 --- Comment #2 from Steven Haigh <net...@crc.id.au> --- Correct - to be a pain in the backside, this *only* crashes when I log out. I can open and close kmail as many times as I like within the session and am unable to trigger the crash. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380855] New: kmail crashes with signal 11 on logout
https://bugs.kde.org/show_bug.cgi?id=380855 Bug ID: 380855 Summary: kmail crashes with signal 11 on logout Product: kmail2 Version: 5.5.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: net...@crc.id.au Target Milestone: --- After using kmail for a while, when I log out of my KDE session, kmail will trigger the crash handler for a signal 11 quit. I have not been able to grab any additional information about the crash - as the crash handler is terminated as part of the logout before any useful information is retrieved. I am currently using the Fedora 26 packages with updates-testing enabled. More than happy to try and debug this if suggestions can be made on how to capture the crash details. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380800] High CPU usage with 'Destkop Effects' enabled
https://bugs.kde.org/show_bug.cgi?id=380800 --- Comment #2 from Steven Haigh <net...@crc.id.au> --- The following output is from an i7 laptop with only an intel GPU. I was doing nothing but moving the mouse around in circles over the 'systemsettings5' window. top - 12:12:45 up 1:24, 3 users, load average: 0.74, 0.33, 0.20 Tasks: 223 total, 1 running, 222 sleeping, 0 stopped, 0 zombie %Cpu(s): 13.8 us, 2.7 sy, 0.0 ni, 82.5 id, 0.3 wa, 0.4 hi, 0.3 si, 0.0 st KiB Mem : 8077024 total, 5125184 free, 1464352 used, 1487488 buff/cache KiB Swap: 8125436 total, 8125436 free,0 used. 5987760 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3748 shaigh20 0 744544 67684 56812 S 46.5 0.8 0:07.06 systemsettings5 1076 root 20 0 368044 101532 69928 S 11.6 1.3 1:23.75 Xorg 1271 shaigh20 0 3239840 85740 61076 S 7.6 1.1 2:01.79 kwin_x11 1281 shaigh20 0 3932612 280104 110536 S 0.7 3.5 0:51.55 plasmashell 2035 shaigh20 0 1431656 267336 135888 S 0.7 3.3 2:41.00 chrome 125 root 20 0 0 0 0 S 0.3 0.0 0:03.57 kworker/u8:4 812 root -51 0 0 0 0 S 0.3 0.0 0:21.02 irq/30-iwlwifi 2218 shaigh20 0 1048804 118212 68972 S 0.3 1.5 0:08.65 chrome 3298 root 20 0 0 0 0 S 0.3 0.0 0:01.18 kworker/u8:2 3709 shaigh20 0 1002728 122836 68264 S 0.3 1.5 0:17.03 chrome 3747 shaigh20 0 157036 4252 3680 R 0.3 0.1 0:00.11 top -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380800] High CPU usage with 'Destkop Effects' enabled
https://bugs.kde.org/show_bug.cgi?id=380800 --- Comment #1 from Steven Haigh <net...@crc.id.au> --- For the record, I have managed to get systemsettings5 to show the same level of CPU usage on a laptop with an intel GPU. Another point - on the first system with the nvidia card, if I have the compositor enabled, I have observed kwin_x11 use up to 160% CPU (average of 140%) while playing a DVB-T stream within VLC. Disabling the compositor or using Alt-Shift-F12 causes the problem to disappear completely. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 380800] New: High CPU usage with 'Destkop Effects' enabled
https://bugs.kde.org/show_bug.cgi?id=380800 Bug ID: 380800 Summary: High CPU usage with 'Destkop Effects' enabled Product: kwin Version: 5.9.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: net...@crc.id.au Target Milestone: --- This output of 'top' is grabbed from just moving the mouse around over the top of the system settings dialog. top - 12:28:24 up 2 min, 2 users, load average: 0.67, 0.28, 0.10 Tasks: 287 total, 2 running, 284 sleeping, 0 stopped, 1 zombie %Cpu(s): 9.7 us, 3.0 sy, 0.0 ni, 87.0 id, 0.0 wa, 0.2 hi, 0.2 si, 0.0 st KiB Mem : 10228404 total, 8320700 free, 1099032 used, 808672 buff/cache KiB Swap: 5181436 total, 5181436 free,0 used. 8807936 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1861 netwiz20 0 988516 154128 92760 R 49.2 1.5 0:16.39 systemsettings5 988 root 20 0 291872 70384 44240 S 23.3 0.7 0:15.02 Xorg 1318 netwiz20 0 3365896 141000 87728 S 10.0 1.4 0:15.30 kwin_x11 1333 netwiz20 0 4571460 420064 159660 S 4.3 4.1 0:12.64 plasmashell 1024 root -51 0 0 0 0 S 1.0 0.0 0:00.64 irq/40-nvidia 8 root 20 0 0 0 0 S 0.3 0.0 0:00.05 rcu_sched 492 root 20 0 0 0 0 S 0.3 0.0 0:00.05 btrfs-transacti 887 root 20 0 789412 18016 15060 S 0.3 0.2 0:00.19 NetworkManager 1885 netwiz20 0 756992 68836 58156 S 0.3 0.7 0:00.49 konsole Disabling the desktop effects via "Alt-Shift-F12" will cause this behaviour to stop immediately. # rpm -qa | grep kwin | sort kf5-kwindowsystem-5.34.0-1.fc26.x86_64 kwin-5.9.5-2.fc26.x86_64 kwin-common-5.9.5-2.fc26.x86_64 kwin-libs-5.9.5-2.fc26.x86_64 # rpm -qa | grep nvidia | sort akmod-nvidia-381.22-2.fc26.x86_64 kmod-nvidia-4.11.3-300.fc26.x86_64-381.22-2.fc26.x86_64 nvidia-driver-381.22-6.fc26.x86_64 nvidia-driver-cuda-libs-381.22-6.fc26.x86_64 nvidia-driver-libs-381.22-6.fc26.x86_64 nvidia-libXNVCtrl-381.22-1.fc26.x86_64 nvidia-settings-381.22-1.fc26.x86_64 Am more than happy to do more debug as required. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380381] New: RFE: "When entering a folder" option request
https://bugs.kde.org/show_bug.cgi?id=380381 Bug ID: 380381 Summary: RFE: "When entering a folder" option request Product: kmail2 Version: 5.5.1 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: net...@crc.id.au Target Milestone: --- Its always been a long standing annoyance that if I select the option "Jump to First Unread Message", and then navigate to a folder that has no unread messages, you just see the first message in the list - ie it goes nowhere. It almost seems like a useful option would be "First unread message (if there is one), otherwise the newest message". This would allow the user to click into a folder, go from the first unread message, read what is required, then go on to the next folder - and essentially come back to where he was before moving off to another folder. This may include another mixture of "First unread message, else last selected message". I would be happy with either of the above options - or maybe both - or maybe even a rethink of this paradigm. Posting as an RFE for discussion. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 283020] Store Kmail Tags in IMAP flags, like Thunderbird
https://bugs.kde.org/show_bug.cgi?id=283020 --- Comment #23 from Steven Haigh <net...@crc.id.au> --- I've just gotten around to toying with kmail again in Fedora 26 Alpha. I like it as a general client - but glaring shortcomings such as shared labels / tags are just about deal breakers. Right now, I use roundcube mail when I'm out and about, k-9 Mail on android, and currently thunderbird on desktops (which I really want to replace with kmail) - and these 3 have no problems with the basic, well agreed tags / labels. I have hope that one day I can check this off the list of annoyances with kmail :) -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 380292] akonadi_imap_resource crash trying to modify IMAP account in kmail
https://bugs.kde.org/show_bug.cgi?id=380292 --- Comment #1 from Steven Haigh <net...@crc.id.au> --- This may actually be a duplicate of 379155 - but I will let someone more knowledgeable than me make that call. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 380292] New: akonadi_imap_resource crash trying to modify IMAP account in kmail
https://bugs.kde.org/show_bug.cgi?id=380292 Bug ID: 380292 Summary: akonadi_imap_resource crash trying to modify IMAP account in kmail Product: Akonadi Version: 5.5.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: IMAP resource Assignee: chrig...@fastmail.fm Reporter: net...@crc.id.au CC: kdepim-b...@kde.org, vkra...@kde.org Target Milestone: --- When trying to modify an IMAP account via kmail Settings -> Configure Kmail -> Accounts Then try to click 'Modify...' on 'IMAP Account 4' (the only imap mail account), nothing happens. In the system journal, I can see that akonadi_imap_resource has crashed. Dump below. $ rpm -qa | grep -i Akonadi | sort akonadi-1.13.0-103.fc26.x86_64 akonadi-import-wizard-17.04.1-1.fc26.x86_64 kf5-akonadi-calendar-17.04.1-1.fc26.x86_64 kf5-akonadi-contacts-17.04.1-1.fc26.x86_64 kf5-akonadi-mime-17.04.1-1.fc26.x86_64 kf5-akonadi-notes-17.04.1-1.fc26.x86_64 kf5-akonadi-search-17.04.1-1.fc26.x86_64 kf5-akonadi-server-17.04.1-3.fc26.x86_64 kf5-akonadi-server-mysql-17.04.1-3.fc26.x86_64 kf5-kmailtransport-akonadi-17.04.1-1.fc26.x86_64 kf5-libkdepim-akonadi-17.04.1-1.fc26.x86_64 kf5-mailimporter-akonadi-17.04.1-1.fc26.x86_64 kf5-pimcommon-akonadi-17.04.1-1.fc26.x86_64 $ rpm -qa | grep -i kmail | sort kf5-kmailtransport-17.04.1-1.fc26.x86_64 kf5-kmailtransport-akonadi-17.04.1-1.fc26.x86_64 kmail-17.04.1-1.fc26.x86_64 kmail-account-wizard-17.04.1-1.fc26.x86_64 kmail-libs-17.04.1-1.fc26.x86_64 akonadi_control[1868]: org.kde.pim.akonadicontrol: ProcessControl: Application "/usr/bin/akonadi_imap_resource" stopped unexpectedly ( "Process crashed" ) akonadi_control[1868]: org.kde.pim.akonadicontrol: Application '/usr/bin/ akonadi_imap_resource' crashed. No restart! systemd-coredump[2857]: Process 2620 (akonadi_imap_re) of user 5000 dumped core. Stack trace of thread 2620: #0 0x7f8dfbaa0801 _ZNK13MailTransport10ServerTest15normalProtocolsEv (libKF5MailTransport.so.5) #1 0x5583292df625 _ZN11SetupServer17slotSafetyChangedEv (akonadi_imap_resource) #2 0x7f8df73a84b7 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #3 0x7f8df7e74012 _ZN9QLineEdit11textChangedERK7QString (libQt5Widgets.so.5) #4 0x7f8df7e7a7d1 _ZN9QLineEdit18qt_static_metacallEP7QObjectN11QMetaObject4CallEiPPv (libQt5Widgets.so.5) #5 0x7f8df73a8383 _ZN11QMetaObject8activateEP7QObjectiiPPv (libQt5Core.so.5) #6 0x7f8df7f03bf5 _ZN18QWidgetLineControl11textChangedERK7QString (libQt5Widgets.so.5) #7 0x7f8df7f06ec6 _ZN18QWidgetLineControl12finishChangeEibb (libQt5Widgets.so.5) #8 0x7f8df7f071de _ZN18QWidgetLineControl15internalSetTextERK7QStringib (libQt5Widgets.so.5) #9 0x7f8df7e75d9c _ZN9QLineEdit7setTextERK7QString (libQt5Widgets.so.5) #10 0x5583292de251 _ZN11SetupServer12readSettingsEv (akonadi_imap_resource) #11 0x5583292e139c _ZN11SetupServerC1EP16ImapResourceBasey (akonadi_imap_resource) #12 0x5583292d917d _ZN12ImapResource21createConfigureDialogEy (akonadi_imap_resource) #13 0x5583292eca6d _ZN16ImapResourceBase9configureEy (akonadi_imap_resource) #14 0x7f8dfa5a48c3 _ZN23Akonadi__ControlAdaptor11qt_metacallEN11QMetaObject4CallEiPPv (libKF5AkonadiAgentBase.so.5) #15 0x7f8dfc711458 _ZN22QDBusConnectionPrivate11deliverCallEP7QObjectiRK12QDBusMessageRK7QVectorIiEi (/usr/lib64/libQt5DBus.so.5.7.1) #16 0x7f8dfc716425 _ZN22QDBusConnectionPrivate12activateCallEP7QObjectiRK12QDBusMessage.part.147 (/usr/lib64/libQt5DBus.so.5.7.1) #17 0x7f8dfc716d3d _ZN22QDBusConnectionPrivate14activateObjectERNS_14ObjectTreeNodeERK12QDBusMessagei (/usr/lib64/libQt5DBus.so.5.7.1) #18 0x7f8dfc71949e _ZN24QDBusActivateObjectEvent13placeMetaCallEP7QObject (/usr/lib64/libQt5DBus.so.5.7.1) #19 0x7f8df73a9199 _ZN7QObject5eventEP6QEvent (libQt5Core.so.5) #20 0x7f8df7d37d9c _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5) #21 0x7f8df7d3f3d4 _ZN12QApplication6notifyEP7QObjectP6QEvent (libQt5Widgets.so.5) #22 0x7f8df7380b8b _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5) #23 0x7f8df7382d6b _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt5Core.so.5) #24 0x7f8df73cfc73 _ZL23postEventSourceDispatchP8_GSourcePFiPvES1_ (libQt5Core.so.5) #25 0x7f8de8eb3277 g_main_context_dispatch (libglib-2.0.so.0) #26 0x7f8de8eb3618 g_main_context_iterate.isra.25 (libglib-2.0.so.0) #27 0x7f8de8eb36ac g_main_context_iteration (libglib-2.0.so.0) #28 0x7f8df73cfcef _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5) #29 0x7f8df737fb8a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5) #30 0x7f8df73877dc _ZN16QCoreApplication4execEv
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added Version Fixed In||5.8.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #13 from Steven Haigh <net...@crc.id.au> --- Ok - so after messing around with this (docked/undocked/etc), the screen config came good. I'm happy to mark this as FIXED for version 5.8.4. New installations will probably work out of the box - and I haven't had to restart plasmashell to fix up a screen problem in a while now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 --- Comment #12 from Steven Haigh <net...@crc.id.au> --- Updated to 5.8.4 (thanks Rex!) $ rpm -qa | grep plasma | sort kdeplasma-addons-5.8.4-1.fc25.x86_64 kde-settings-plasma-25-2.fc25.noarch kf5-plasma-5.27.0-1.fc25.x86_64 plasma-breeze-5.8.4-1.fc25.x86_64 plasma-breeze-common-5.8.4-1.fc25.noarch plasma-desktop-5.8.4-1.fc25.x86_64 plasma-desktop-doc-5.8.4-1.fc25.noarch plasma-discover-5.8.4-2.fc25.x86_64 plasma-discover-libs-5.8.4-2.fc25.x86_64 plasma-integration-5.8.4-1.fc25.x86_64 plasma-lookandfeel-fedora-5.8.4-1.fc25.noarch plasma-milou-5.8.4-1.fc25.x86_64 plasma-nm-5.8.4-1.fc25.x86_64 plasma-nm-l2tp-5.8.4-1.fc25.x86_64 plasma-nm-openconnect-5.8.4-1.fc25.x86_64 plasma-nm-openswan-5.8.4-1.fc25.x86_64 plasma-nm-openvpn-5.8.4-1.fc25.x86_64 plasma-nm-pptp-5.8.4-1.fc25.x86_64 plasma-nm-vpnc-5.8.4-1.fc25.x86_64 plasma-pa-5.8.4-1.fc25.x86_64 plasma-pk-updates-0.2-9.20160307git7b484b0.fc25.x86_64 plasma-systemsettings-5.8.4-1.fc25.x86_64 plasma-user-manager-5.8.4-1.fc25.x86_64 plasma-workspace-5.8.4-1.fc25.x86_64 plasma-workspace-common-5.8.4-1.fc25.x86_64 plasma-workspace-drkonqi-5.8.4-1.fc25.x86_64 plasma-workspace-geolocation-5.8.4-1.fc25.x86_64 plasma-workspace-geolocation-libs-5.8.4-1.fc25.x86_64 plasma-workspace-libs-5.8.4-1.fc25.x86_64 While the login works correctly now, I am unable to change the properties of the desktop that was always reset - ie change from Folder View to Desktop. Hopefully some helpful info: $ kscreen-doctor -o Output: 67 LVDS1 disabled connected Panel Modes: 243:1920x1080@40 244:1400x1050@60 245:1600x900@60 246:1280x1024@60 247:1280x960@60 248:1368x768@60 249:1280x720@60 250:1024x768@60 251:1024x576@60 252:960x540@60 253:800x600@60 254:800x600@56 255:864x486@60 256:640x480@60 257:720x405@60 258:640x360@60 77:1920x1080@60! Geometry: 0,0 0x0 Output: 68 DP1 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Output: 69 DP2 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Output: 70 DP3 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Output: 71 HDMI1 disabled disconnected HDMI Modes: Geometry: 0,0 0x0 Output: 72 HDMI2 enabled connected primary HDMI Modes: 246:1280x1024@60 250:1024x768@60 253:800x600@60 256:640x480@60 259:1600x900@60 260:1280x1024@75 261:1152x864@75 262:1024x768@75 263:800x600@75 264:640x480@75 265:720x400@70 78:1920x1080@60*! Geometry: 0,0 1920x1080 Output: 73 HDMI3 enabled connected HDMI Modes: 246:1280x1024@60 250:1024x768@60 253:800x600@60 256:640x480@60 259:1600x900@60 260:1280x1024@75 261:1152x864@75 262:1024x768@75 263:800x600@75 264:640x480@75 265:720x400@70 78:1920x1080@60*! Geometry: 1920,0 1920x1080 Output: 74 VGA1 disabled disconnected VGA Modes: Geometry: 0,0 0x0 Output: 75 VIRTUAL1 disabled disconnected Unknown Modes: Geometry: 0,0 0x0 $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 LVDS1 connected (normal left inverted right x axis y axis) 1920x1080 60.01 + 40.01 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1280x960 60.00 1368x768 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm 1920x1080 60.00*+ 1600x900 60.00 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 720x400 70.08 HDMI3 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 480mm x 270mm 1920x1080 60.00*+ 1600x900 60.00 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 720x400 70.08 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) Any suggestions on how to debug or troubleshoot this? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added Version|5.8.3 |5.8.4 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added Version|5.8.0 |5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 --- Comment #10 from Steven Haigh <net...@crc.id.au> --- For what its worth, this still occurs on F25 + 5.8.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 --- Comment #8 from Steven Haigh <net...@crc.id.au> --- I can confirm this problem still exists in 5.8.1 - with an added regression that I can no longer change the second screen from Folder View -> Desktop. The primary screen can be changed at will, yet the secondary screen does not apply the changes when either clicking OK or Apply. $ rpm -qa | grep plasma | sort kdeplasma-addons-5.8.1-0.1.fc25.x86_64 kde-settings-plasma-25-2.fc25.noarch kf5-plasma-5.27.0-1.fc25.x86_64 plasma-breeze-5.8.1-0.1.fc25.x86_64 plasma-breeze-common-5.8.1-0.1.fc25.noarch plasma-desktop-5.8.1-0.1.fc25.x86_64 plasma-desktop-doc-5.8.1-0.1.fc25.noarch plasma-discover-5.8.1-0.1.fc25.x86_64 plasma-discover-libs-5.8.1-0.1.fc25.x86_64 plasma-integration-5.8.1-0.1.fc25.x86_64 plasma-lookandfeel-fedora-5.8.1-0.1.fc25.noarch plasma-milou-5.8.1-0.1.fc25.x86_64 plasma-nm-5.8.1-0.1.fc25.x86_64 plasma-nm-l2tp-5.8.1-0.1.fc25.x86_64 plasma-nm-openconnect-5.8.1-0.1.fc25.x86_64 plasma-nm-openswan-5.8.1-0.1.fc25.x86_64 plasma-nm-openvpn-5.8.1-0.1.fc25.x86_64 plasma-nm-pptp-5.8.1-0.1.fc25.x86_64 plasma-nm-vpnc-5.8.1-0.1.fc25.x86_64 plasma-pa-5.8.0-1.fc25.x86_64 plasma-pk-updates-0.2-9.20160307git7b484b0.fc25.x86_64 plasma-systemsettings-5.8.1-0.1.fc25.x86_64 plasma-user-manager-5.8.1-0.1.fc25.x86_64 plasma-workspace-5.8.1-0.1.fc25.x86_64 plasma-workspace-common-5.8.1-0.1.fc25.x86_64 plasma-workspace-drkonqi-5.8.1-0.1.fc25.x86_64 plasma-workspace-geolocation-5.8.1-0.1.fc25.x86_64 plasma-workspace-geolocation-libs-5.8.1-0.1.fc25.x86_64 plasma-workspace-libs-5.8.1-0.1.fc25.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 --- Comment #4 from Steven Haigh <net...@crc.id.au> --- Created attachment 101517 --> https://bugs.kde.org/attachment.cgi?id=101517=edit ~/.config/plasmashellrc as requested. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 --- Comment #5 from Steven Haigh <net...@crc.id.au> --- Created attachment 101518 --> https://bugs.kde.org/attachment.cgi?id=101518=edit ~/.config/plasma-org.kde.plasma.desktop-appletsrc as requested. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 --- Comment #2 from Steven Haigh <net...@crc.id.au> --- Just like to confirm that this also occurs on a F25 Beta install with KDE 5.8 from COPR. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 --- Comment #1 from Steven Haigh <net...@crc.id.au> --- Installation on Fedora 24 from the 5.8 unstable COPR: $ rpm -qa | grep plasma-desktop | sort plasma-desktop-5.8.0-0.4.fc24.x86_64 plasma-desktop-doc-5.8.0-0.4.fc24.noarc -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370388] New: No panel on login / second screen settings not saved.
https://bugs.kde.org/show_bug.cgi?id=370388 Bug ID: 370388 Summary: No panel on login / second screen settings not saved. Product: plasmashell Version: 5.8.0 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: major Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: net...@crc.id.au CC: plasma-b...@kde.org This has been fixed in one of my other systems - but in this hardware configuration, it seems that maybe having another screen connected but disabled may break some logic. Hardware: * Dell Lattitude E5530 with 2 x DVI screens on docking station. * Laptop lid / screen closed. * Graphics: Intel Corporation 3rd Gen Core processor Graphics Controller (rev 09) Reproducible: Always Steps to Reproduce: On login, I do not get *ANY* panel. Both screens are at default settings. Upon running 'killall plasmashell && plasmashell &', I get the primary screen with panel + saved settings, whereas screen 1 is either blank or at defaults. $ kscreen-doctor -o Output: 67 LVDS1 disabled connected Panel Modes: 243:1920x1080@40 244:1400x1050@60 245:1600x900@60 246:1280x1024@60 247:1280x960@60 248:1368x768@60 249:1280x720@60 250:1024x768@60 251:1024x576@60 252:960x540@60 253:800x600@60 254:800x600@56 255:864x486@60 256:640x480@60 257:720x405@60 258:640x360@60 77:1920x1080@60! Geometry: 0,0 0x0 Output: 68 DP1 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Output: 69 DP2 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Output: 70 DP3 disabled disconnected DisplayPort Modes: Geometry: 0,0 0x0 Output: 71 HDMI1 disabled disconnected HDMI Modes: Geometry: 0,0 0x0 Output: 72 HDMI2 enabled connected primary HDMI Modes: 246:1280x1024@60 250:1024x768@60 253:800x600@60 256:640x480@60 259:1600x900@60 260:1280x1024@75 261:1152x864@75 262:1024x768@75 263:800x600@75 264:640x480@75 265:720x400@70 78:1920x1080@60*! Geometry: 0,0 1920x1080 Output: 73 HDMI3 enabled connected HDMI Modes: 246:1280x1024@60 250:1024x768@60 253:800x600@60 256:640x480@60 259:1600x900@60 260:1280x1024@75 261:1152x864@75 262:1024x768@75 263:800x600@75 264:640x480@75 265:720x400@70 78:1920x1080@60*! Geometry: 1920,0 1920x1080 Output: 74 VGA1 disabled disconnected VGA Modes: Geometry: 0,0 0x0 Output: 75 VIRTUAL1 disabled disconnected Unknown Modes: Geometry: 0,0 0x0 $ xrandr Screen 0: minimum 8 x 8, current 3840 x 1080, maximum 32767 x 32767 LVDS1 connected (normal left inverted right x axis y axis) 1920x1080 60.01 + 40.01 1400x1050 59.98 1600x900 60.00 1280x1024 60.02 1280x960 60.00 1368x768 60.00 1280x720 60.00 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.3256.25 864x486 60.00 640x480 59.94 720x405 60.00 640x360 60.00 DP1 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm 1920x1080 60.00*+ 1600x900 60.00 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 720x400 70.08 HDMI3 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 480mm x 270mm 1920x1080 60.00*+ 1600x900 60.00 1280x1024 75.0260.02 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.32 640x480 75.0059.94 720x400 70.08 VGA1 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367917] Primary desktop settings are not saved
https://bugs.kde.org/show_bug.cgi?id=367917 --- Comment #6 from Steven Haigh <net...@crc.id.au> --- For the record, this is fixed in the Fedora COPR versions: $ rpm -qa | grep plasma-desktop | sort plasma-desktop-5.8.0-0.4.fc24.x86_64 plasma-desktop-doc-5.8.0-0.4.fc24.noarch -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 327024] Migrate to libssh 0.6 API (add support for ECDSA keys)
https://bugs.kde.org/show_bug.cgi?id=327024 --- Comment #4 from Steven Haigh <net...@crc.id.au> --- Also: debug1: Server host key: ecdsa-sha2-nistp256 -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 327024] Migrate to libssh 0.6 API (add support for ECDSA keys)
https://bugs.kde.org/show_bug.cgi?id=327024 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added CC||net...@crc.id.au --- Comment #3 from Steven Haigh <net...@crc.id.au> --- I'm not sure this is currently working with KDE 5.7 / 5.8. I'm trying via Dolphin to use SFTP to a system I am also SSH'ed into and I *always* get an "Authentication Failed" message. The host logs don't show any connection attempt being made. Using the FISH:// method, all is fine. Bits from the connect using -vv via SSH: debug1: Local version string SSH-2.0-OpenSSH_7.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.3 ... debug2: peer server KEXINIT proposal debug2: KEX algorithms: curve25519-sha...@libssh.org,ecdh-sha2-nistp256,ecdh-sha2-nistp384,ecdh-sha2-nistp521,diffie-hellman-group-exchange-sha256,diffie-hellman-group16-sha512,diffie-hellman-group18-sha512,diffie-hellman-group14-sha256,diffie-hellman-group14-sha1 debug2: host key algorithms: ssh-rsa,rsa-sha2-512,rsa-sha2-256,ecdsa-sha2-nistp256,ssh-ed25519 debug2: ciphers ctos: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com debug2: ciphers stoc: chacha20-poly1...@openssh.com,aes128-ctr,aes192-ctr,aes256-ctr,aes128-...@openssh.com,aes256-...@openssh.com debug2: MACs ctos: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: MACs stoc: umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-sha1-...@openssh.com,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-sha1 debug2: compression ctos: none,z...@openssh.com debug2: compression stoc: none,z...@openssh.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367917] Primary desktop settings are not saved
https://bugs.kde.org/show_bug.cgi?id=367917 --- Comment #4 from Steven Haigh <net...@crc.id.au> --- To assist with debugging, I started again today with a fresh user account. I configured the screen on DVI-D port to be Folder View (the default) with columns instead of rows. I then set up the Left side screen (DP-1) to Desktop mode. Then the right side screen (DP-5) to Desktop mode. Rebooted, then logged back in again. DP-1 & DP-5 are now back to the default Folder View with Rows. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367917] Primary desktop settings are not saved
https://bugs.kde.org/show_bug.cgi?id=367917 --- Comment #3 from Steven Haigh <net...@crc.id.au> --- For reference, packages obtained from this repo: https://copr.fedorainfracloud.org/coprs/g/kdesig/plasma-5-unstable/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367917] Primary desktop settings are not saved
https://bugs.kde.org/show_bug.cgi?id=367917 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added Version|5.7.3 |5.8.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367917] Primary desktop settings are not saved
https://bugs.kde.org/show_bug.cgi?id=367917 Steven Haigh <net...@crc.id.au> changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|UNCONFIRMED --- Comment #2 from Steven Haigh <net...@crc.id.au> --- Still seeing this with: $ rpm -qa | grep plasma | sort kdeplasma-addons-5.8.0-0.1.fc24.x86_64 kde-settings-plasma-24-7.fc24.noarch kf5-plasma-5.26.0-1.fc24.x86_64 plasma-breeze-5.8.0-0.2.fc24.x86_64 plasma-breeze-common-5.8.0-0.2.fc24.noarch plasma-desktop-5.8.0-0.1.fc24.x86_64 plasma-desktop-doc-5.8.0-0.1.fc24.noarch plasma-discover-5.8.0-0.1.fc24.x86_64 plasma-discover-libs-5.8.0-0.1.fc24.x86_64 plasma-integration-5.8.0-0.1.fc24.x86_64 plasma-milou-5.8.0-0.1.fc24.x86_64 plasma-nm-5.8.0-0.1.fc24.x86_64 plasma-nm-l2tp-5.8.0-0.1.fc24.x86_64 plasma-nm-openconnect-5.8.0-0.1.fc24.x86_64 plasma-nm-openswan-5.8.0-0.1.fc24.x86_64 plasma-nm-openvpn-5.8.0-0.1.fc24.x86_64 plasma-nm-pptp-5.8.0-0.1.fc24.x86_64 plasma-nm-vpnc-5.8.0-0.1.fc24.x86_64 plasma-pa-5.8.0-0.1.fc24.x86_64 plasma-pk-updates-0.2-9.20160307git7b484b0.fc24.x86_64 plasma-systemsettings-5.8.0-0.1.fc24.x86_64 plasma-user-manager-5.8.0-0.1.fc24.x86_64 plasma-workspace-5.8.0-0.1.fc24.x86_64 plasma-workspace-common-5.8.0-0.1.fc24.x86_64 plasma-workspace-drkonqi-5.8.0-0.1.fc24.x86_64 plasma-workspace-geolocation-5.8.0-0.1.fc24.x86_64 plasma-workspace-geolocation-libs-5.8.0-0.1.fc24.x86_64 plasma-workspace-libs-5.8.0-0.1.fc24.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 367917] New: Primary desktop settings are not saved
https://bugs.kde.org/show_bug.cgi?id=367917 Bug ID: 367917 Summary: Primary desktop settings are not saved Product: plasmashell Version: 5.7.3 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Multi-screen support Assignee: aleix...@kde.org Reporter: net...@crc.id.au CC: plasma-b...@kde.org I have a tri-monitor setup hooked up to an nVidia 1060 card. 1 x DVI-D, 2 x DP. I set the centre screen as the main screen, and have configured screens from left to right as: 1) Desktop mode 2) Folder View 3) Desktop mode. When I reboot / log out and return, the following config is applied: 1) Folder View 2) Desktop mode 3) Desktop mode If I change the settings around again, save my session and reboot, I always get the same settings back. Reproducible: Always Steps to Reproduce: See details. $ rpm -qa | grep plasma | sort kdeplasma-addons-5.7.3-1.fc24.x86_64 kde-settings-plasma-24-7.fc24.noarch kf5-plasma-5.25.0-2.fc24.x86_64 plasma-breeze-5.7.3-1.fc24.x86_64 plasma-breeze-common-5.7.3-1.fc24.noarch plasma-desktop-5.7.3-1.fc24.x86_64 plasma-desktop-doc-5.7.3-1.fc24.noarch plasma-discover-5.7.3-1.fc24.x86_64 plasma-discover-libs-5.7.3-1.fc24.x86_64 plasma-integration-5.7.3-1.fc24.x86_64 plasma-milou-5.7.3-1.fc24.x86_64 plasma-nm-5.7.3-2.fc24.x86_64 plasma-nm-l2tp-5.7.3-2.fc24.x86_64 plasma-nm-openconnect-5.7.3-2.fc24.x86_64 plasma-nm-openswan-5.7.3-2.fc24.x86_64 plasma-nm-openvpn-5.7.3-2.fc24.x86_64 plasma-nm-pptp-5.7.3-2.fc24.x86_64 plasma-nm-vpnc-5.7.3-2.fc24.x86_64 plasma-pa-5.7.3-1.fc24.x86_64 plasma-pk-updates-0.2-9.20160307git7b484b0.fc24.x86_64 plasma-systemsettings-5.7.3-1.fc24.x86_64 plasma-user-manager-5.7.3-1.fc24.x86_64 plasma-workspace-5.7.3-2.fc24.x86_64 plasma-workspace-common-5.7.3-2.fc24.x86_64 plasma-workspace-drkonqi-5.7.3-2.fc24.x86_64 plasma-workspace-libs-5.7.3-2.fc24.x86_64 03:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device 3716 Flags: bus master, fast devsel, latency 0, IRQ 40 Memory at fa00 (32-bit, non-prefetchable) [size=16M] Memory at d000 (64-bit, prefetchable) [size=256M] Memory at ce00 (64-bit, prefetchable) [size=32M] I/O ports at dc00 [size=128] [virtual] Expansion ROM at 000c [disabled] [size=128K] Capabilities: Kernel driver in use: nvidia Kernel modules: nouveau, nvidia_drm, nvidia $ xrandr --current Screen 0: minimum 8 x 8, current 5760 x 1080, maximum 32767 x 32767 DVI-D-0 connected primary 1920x1080+1920+0 (normal left inverted right x axis y axis) 510mm x 290mm 1920x1080 60.00*+ 1680x1050 59.95 1280x1024 75.0260.02 1280x960 60.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.3256.25 640x480 75.0059.94 HDMI-0 disconnected (normal left inverted right x axis y axis) DP-0 disconnected (normal left inverted right x axis y axis) DP-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 510mm x 290mm 1920x1080 60.00*+ 1680x1050 59.95 1280x1024 75.0260.02 1280x960 60.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.3256.25 640x480 75.0059.94 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) DP-4 disconnected (normal left inverted right x axis y axis) DP-5 connected 1920x1080+3840+0 (normal left inverted right x axis y axis) 510mm x 290mm 1920x1080 60.00*+ 1680x1050 59.95 1280x1024 75.0260.02 1280x960 60.00 1152x864 75.00 1024x768 75.0360.00 800x600 75.0060.3256.25 640x480 75.0059.94 -- You are receiving this mail because: You are watching all bug changes.
