[gwenview] [Bug 471029] Gwenview crashes immediately when i specifically try to open these images
https://bugs.kde.org/show_bug.cgi?id=471029 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 392798] Power button actions should be handled from lock screen
https://bugs.kde.org/show_bug.cgi?id=392798 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #25 from Rewarp --- I would like to chime in with a particular setup that makes the lack of an easy access to the shutdown procedure from the power button from the lock screen dangerously insecure. I am setting up servers for schools running openSUSE with docker containers containing various services, with the Plasma interface. They are designed to be as easy to use as possible since we are talking about primary and secondary schools. No one expects any teacher there to be a moonlighting sysadmin. To shutdown the server properly in such a scenario would be too much of a hassle for them, so I used the system settings for power management to trigger a shutdown when the power button is pressed. However, the power button doesn't work if the screenlock is on. The screenlock should ideally be on so that teachers and trusted students can access the desktop interface for whatever reason. The only protection therefore for such a unit thus far in an exposed environment is the lack of a KVM. I can imagine that's not going to be much of a barrier for kids determined to do mischief. So my hope is there will be a user toggle option that allows the power button to shutdown the system safely should it be necessary from the lockscreen. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 460186] New: Timezone not synced correctly for daylight savings in country without DST
https://bugs.kde.org/show_bug.cgi?id=460186 Bug ID: 460186 Summary: Timezone not synced correctly for daylight savings in country without DST Classification: Applications Product: korganizer Version: 5.21.1 Platform: OpenSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: timezones Assignee: kdepim-b...@kde.org Reporter: rew...@thestrayworld.com Target Milestone: --- Created attachment 152677 --> https://bugs.kde.org/attachment.cgi?id=152677&action=edit Screenshot showing the incorrect meeting time being displayed, and discrepancy versus the month view. SUMMARY I missed a company meeting because Korganizer did not show me the correct time for New Zealand while I am based in Malaysia. Checking my online calendar hosted at Fastmail does however show the correct time. To test that it is a problem with the app and not a service provider, I requested my invitation to the meeting to be resent, and it still shows the incorrect time. Upon closer observation of what is written versus what is shown in the monthly view however, it seems the time is placed correctly, but not in writing. Please check the attached screenshot to see that in writing, it is the incorrect time that does not account for DST, and the month view that does. STEPS TO REPRODUCE 1. Receive invitation from country with DST to a country without DST OBSERVED RESULT Time not correctly synced in the written out view. On closer observation, discrepancy can be seen in the month view on the right. EXPECTED RESULT Time to be correctly synced across all calendars. CalDav host (Fastmail in this case) shows the correct time. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20221006 (available in About System) KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #26 from Rewarp --- Quick update. Emails now sent from Fastmail following port number change, but about half an hour after they were supposed to be sent. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #25 from Rewarp --- Changing the port for Fastmail to 587 fails to get smtp working. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 --- Comment #21 from Rewarp --- I restarted akonadi and see this error too: org.kde.pim.ksmtp: Socket error: 2 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 387926] Release version 17.12: Sending a mail with SMTP fails with: org.kde.pim.ksmtp: Socket error: 1
https://bugs.kde.org/show_bug.cgi?id=387926 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #20 from Rewarp --- OS: openSUSE TUmbleweed Version: 5.7 I can confirm all my smtp settings are correct for Fastmail and Office365 and yet only my Google SMTP sends my messages. smtp.office365.com TLS; 587;LOGIN smtp.fastmail.com TLS; 465; PLAIN smtp.googlemail.com TLS; 25; LOGIN -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 262271] Akregator fetched feeds with incorrect content (overlapping with each other) with dates in future.
https://bugs.kde.org/show_bug.cgi?id=262271 --- Comment #12 from Rewarp --- I noticed another funny behaviour. The wrong dates often appear on new feed items without dates, when akregator is restarted. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 262271] Akregator fetched feeds with incorrect content (overlapping with each other) with dates in future.
https://bugs.kde.org/show_bug.cgi?id=262271 --- Comment #11 from Rewarp --- The problem has gotten much worse for me on openSUSE Tumbleweed. Nearly half of my feed is now populated by wrongly dated feeds (all dated to 0702/2106 14:38), and they are usually new items. This would be a minor inconvenience if it were not for the fact every time I am highlighting one of those items it bounces the article to the bottom of the feed of 2106, which means I have to scroll even more to get to the next newest item. I can back up the feed, so I am okay with just resetting akregator. How do I do so? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358501] New Message shortcut not working correctly
https://bugs.kde.org/show_bug.cgi?id=358501 Rewarp changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 371203] ktorrent immediately crashes
https://bugs.kde.org/show_bug.cgi?id=371203 Rewarp changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kiten] [Bug 347273] Kiten search bar does not allow Fcitx input of Japanese characters.
https://bugs.kde.org/show_bug.cgi?id=347273 Rewarp changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 377122] kwallet cannot ask for GPG password on wayland
https://bugs.kde.org/show_bug.cgi?id=377122 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #2 from Rewarp --- Just dropping by to say that as of openSUSE Tumbleweed build 20170602, kwallet with GPG still does not work. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 350731] [4.81 beta1] akregator in kontact: read messages are removed from unread filter immediately
https://bugs.kde.org/show_bug.cgi?id=350731 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 262271] Akregator fetched feeds with incorrect content (overlapping with each other) with dates in future.
https://bugs.kde.org/show_bug.cgi?id=262271 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #9 from Rewarp --- I have feeds being pulled from the year 2106! http://i.imgur.com/6CGI1VV.png Here the feed for the podcast The Bugle from which the problem originates, though knowing the host, they will probably find this to be the basis of a pun run. URL of the episode to confirm that it is indeed, not from the future: http://bugle.prx.org/2013/12/bugle-253-lenin-in-a-dress/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+thebuglefeed+%28The+Bugle%29 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 374676] The Akonadi personal information management service is not operational
https://bugs.kde.org/show_bug.cgi?id=374676 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #1 from Rewarp --- Akonadi is also not working for me correctly with the same error message in Kontact. Attempts to start it lead to the following: rewarp@ganymede:~> akonadictl start Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) rewarp@ganymede:~> org.kde.pim.akonadiserver: Failed to connect to database! org.kde.pim.akonadiserver: Database error: "Can't connect to local MySQL server through socket '/tmp/akonadi-rewarp.eMZXmm/mysql.socket' (111 \"Connection refused\") QMYSQL: Unable to connect" /usr/bin/mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/tmp/akonadi-rewarp.eMZXmm/mysql.socket' (111 "Connection refused")' Check that mysqld is running and that the socket: '/tmp/akonadi-rewarp.eMZXmm/mysql.socket' exists! org.kde.pim.akonadiserver: Failed to remove runtime connection config file org.kde.pim.akonadicontrol: Application 'akonadiserver' exited normally... -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 373443] Mail Dispatcher Agent spins at 100% CPU after upgrade from 4:16.08.2+p16.04+git20161117.2322-0 to 4:16.08.3+p16.04+git20161207.0319-0
https://bugs.kde.org/show_bug.cgi?id=373443 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #6 from Rewarp --- I can confirm Tomasz's solution fixes the problem on openSUSE Tumbleweed. I only noticed the problem when KMail failed to send my messages in my outbox, presumably because of the saturation of the CPU processes. Thanks for the suggestion. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 373989] Kmail 5.4 / akonadi agents hogging cpu cores
https://bugs.kde.org/show_bug.cgi?id=373989 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #2 from Rewarp --- Possible duplicate of https://bugs.kde.org/show_bug.cgi?id=373443 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 346118] Plasmashell crash when disconnecting/reconnecting my WiFi connection after changing MTU
https://bugs.kde.org/show_bug.cgi?id=346118 Rewarp changed: What|Removed |Added CC|rew...@thestrayworld.com| -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 347916] Search does not work when performed from $HOMEDIR/$USER
https://bugs.kde.org/show_bug.cgi?id=347916 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #8 from Rewarp --- (In reply to Bron Mach from comment #4) > Going to: System Settings > Search > File Search, and unselecting "Enable > file search" let Dolphin find files in my home directory and subdirectories. > > Otherwise with "Enable file search" selected, the behaviour was the same as > described by Edward: no files found unless searching outside of my home > directory. > > Dolphin 15.08.2 on Kubuntu 15.10 with updates from backports PPA I can confirm this behavior in openSUSE Tumbleweed. I have tried resetting Baloo for reindexing many times, but oddly, the Search settings automatically exclude my secondary hard drives containing my user files from being indexed. I have tried forcing the reindexing by deleting the baloo config files via: balooctl stop rm ~/.config/baloo* rm -rf ~/.local/share/baloo baloo start However, when I check the Search settings, my external drives are once again excluded from being indexed. It is very ironic that unselecting Enable File Search allows me to search for files. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 360448] Visual artefact appearing in Akregator
https://bugs.kde.org/show_bug.cgi?id=360448 Rewarp changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #3 from Rewarp --- I don't see this issue anymore in Kontact 5.3, so I presume it has been properly fixed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 350059] Filters in kmail no longer functional
https://bugs.kde.org/show_bug.cgi?id=350059 Rewarp changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED --- Comment #7 from Rewarp --- Since this issue is no longer occurring, I am closing this report. Thanks for all the help! -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 371203] New: ktorrent immediately crashes
https://bugs.kde.org/show_bug.cgi?id=371203 Bug ID: 371203 Summary: ktorrent immediately crashes Product: ktorrent Version: unspecified Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: joris.guis...@gmail.com Reporter: rew...@thestrayworld.com Application: ktorrent (5.0.1) Qt Version: 5.7.0 Frameworks Version: 5.26.0 Operating System: Linux 4.7.6-1-default x86_64 Distribution: "openSUSE Tumbleweed" -- Information about the crash: ktorrent fails to properly launch and crashes as soon as it loads up. This behavior occurs whether it is launched on its own, or when used to open torrent links. The crash can be reproduced every time. -- Backtrace: Application: KTorrent (ktorrent), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fab968f2940 (LWP 22295))] Thread 6 (Thread 0x7fab4f41b700 (LWP 22315)): #0 0x7fab909aeb39 in syscall () from /lib64/libc.so.6 #1 0x7fab915b86c5 in QBasicMutex::lockInternal() () from /usr/lib64/libQt5Core.so.5 #2 0x7fab915b8782 in QMutex::lock() () from /usr/lib64/libQt5Core.so.5 #3 0x7fab9615cba9 in net::SocketMonitor::lock (this=) at /usr/src/debug/libktorrent-2.0.1/src/net/socketmonitor.cpp:108 #4 0x7fab9615db8c in net::UploadThread::update (this=0x224a180) at /usr/src/debug/libktorrent-2.0.1/src/net/uploadthread.cpp:49 #5 0x7fab9615e3d9 in net::NetworkThread::run (this=0x224a180) at /usr/src/debug/libktorrent-2.0.1/src/net/networkthread.cpp:48 #6 0x7fab915c1558 in ?? () from /usr/lib64/libQt5Core.so.5 #7 0x7fab8c40e454 in start_thread () from /lib64/libpthread.so.0 #8 0x7fab909b33ff in clone () from /lib64/libc.so.6 Thread 5 (Thread 0x7fab4fc1c700 (LWP 22314)): [KCrash Handler] #6 0x7fab9164a52c in QString::indexOf(QChar, int, Qt::CaseSensitivity) const () from /usr/lib64/libQt5Core.so.5 #7 0x7fab96199036 in HttpResponseHeader::parseLine (this=this@entry=0x7fab4fc1b9b0, line=..., number=number@entry=14) at /usr/src/debug/libktorrent-2.0.1/src/download/httpresponseheader.cpp:27 #8 0x7fab96199af2 in HttpResponseHeader::parse (this=this@entry=0x7fab4fc1b9b0, str=...) at /usr/src/debug/libktorrent-2.0.1/src/download/httpresponseheader.cpp:88 #9 0x7fab96197911 in HttpResponseHeader::HttpResponseHeader (str=..., this=0x7fab4fc1b9b0) at /usr/src/debug/libktorrent-2.0.1/src/download/httpresponseheader.h:27 #10 bt::HttpConnection::HttpGet::onDataReady (this=0x2c0f600, buf=buf@entry=0x7fab9648dba0 "HTTP/1.1 302 Found\r\nCache-Control: no-cache, no-store, must-revalidate\r\nPragma: no-cache\r\nContent-Type: text/html; charset=utf-8\r\nExpires: -1\r\nLocation: http://201406.jb-dl.cdn.scaleengine.net/las/201";..., size=size@entry=665) at /usr/src/debug/libktorrent-2.0.1/src/download/httpconnection.cpp:386 #11 0x7fab961984fb in bt::HttpConnection::onDataReady (this=0x2c0e270, buf=0x7fab9648dba0 "HTTP/1.1 302 Found\r\nCache-Control: no-cache, no-store, must-revalidate\r\nPragma: no-cache\r\nContent-Type: text/html; charset=utf-8\r\nExpires: -1\r\nLocation: http://201406.jb-dl.cdn.scaleengine.net/las/201";..., size=665) at /usr/src/debug/libktorrent-2.0.1/src/download/httpconnection.cpp:158 #12 0x7fab9616269f in net::TrafficShapedSocket::read (this=0x2bfce80, max_bytes_to_read=106230, now=1476859486396) at /usr/src/debug/libktorrent-2.0.1/src/net/trafficshapedsocket.cpp:142 #13 0x7fab9615f4e3 in net::SocketGroup::processLimited (this=0x224a0d0, up=false, now=1476859486396, allowance=@0x7fab4fc1bbb4: 106230) at /usr/src/debug/libktorrent-2.0.1/src/net/socketgroup.cpp:79 #14 0x7fab9615f750 in net::SocketGroup::process (this=0x224a0d0, up=, now=, global_allowance=@0x7fab4fc1bbb4: 106230) at /usr/src/debug/libktorrent-2.0.1/src/net/socketgroup.cpp:188 #15 0x7fab9615e627 in net::NetworkThread::doGroupsLimited (this=this@entry=0x2249e50, num_ready=num_ready@entry=1, now=now@entry=1476859486396, allowance=@0x7fab4fc1bc10: 106230) at /usr/src/debug/libktorrent-2.0.1/src/net/networkthread.cpp:111 #16 0x7fab9615e921 in net::NetworkThread::doGroups (this=this@entry=0x2249e50, num_ready=num_ready@entry=1, now=now@entry=1476859486396, limit=) at /usr/src/debug/libktorrent-2.0.1/src/net/networkthread.cpp:190 #17 0x7fab9615e396 in net::DownloadThread::update (this=0x2249e50) at /usr/src/debug/libktorrent-2.0.1/src/net/downloadthread.cpp:83 #18 0x7fab9615e3d9 in net::NetworkThread::run (this=0x2249e50) at /usr/src/debug/libktorrent-2.0.1/src/net/networkthread.cpp:48 #19 0x7fab915c1558 in ?? () from /usr/lib64/libQt5Core.so.5 #20 0x7fab8c40e454 in start_thread () from /lib64/libpthread.so.0 #21 0x7fab909b33ff in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7fab5f6ab700 (LWP 22302)): #0 0x7fab8c41410f
[kmail2] [Bug 339360] offline accounts should try to reconnect automatically
https://bugs.kde.org/show_bug.cgi?id=339360 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #2 from Rewarp --- I am experiencing this error with KMail 5.3.0. nd in prior versions. When I login, I have a cryptographic key setup to unlock kwallet, which means there is a delay in the credentials for signing onto the available networks. This delay means autoconnect usually fails unless I unlock my wallet fast enough. The failure to connect stops KMail from retrieving new messages. After connecting, KMail fails to detect the change in the network status, and will remain so until I manually restart the IMAP connection. Prior to noticing this issue, I went for days without receiving or responding to emails, simply because I was trying to connect to networks requiring authentication. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 366040] libkf5wallet5: timeout when using GPG and gpg-agent
https://bugs.kde.org/show_bug.cgi?id=366040 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #1 from Rewarp --- I would like to add, that my gpg-protected kwallet does not provide ample time to type in my passphrase before proceeding with authentication procedures after logging in. This causes two major issues which are: 1. Connection to an encrypted WiFI network fails as the saved password is not provided because kwallet has yet to be unlocked immediately after logging in. I have to manually cancel the password dialogue box after unlocking kwallet before attempting to connect. 2. Failure to connect to the WiFi network always results in KMail failing to connect to my email servers, whose status will remain unchanged unless I manually restart the connection to my email servers. I am running kwallet 5.24 on opensuse Tumbleweed. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 347740] Encrypted message not detected as encrypted message
https://bugs.kde.org/show_bug.cgi?id=347740 --- Comment #13 from Rewarp --- Created attachment 99662 --> https://bugs.kde.org/attachment.cgi?id=99662&action=edit Message as plain text By full message, I assume you mean the entire source view of the message. I have included it in this attachment, and would also like to confirm that this correspondence also uses Apple Mail, as mentioned in the bug report you attached. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 347740] Encrypted message not detected as encrypted message
https://bugs.kde.org/show_bug.cgi?id=347740 --- Comment #11 from Rewarp --- I have confirmed that messages sent with the attachment above are still not being decrypted. I am at a loss as what is wrong here. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 345992] Keyboard shortcut assigned to "archive mail" works once, unconfigures itself
https://bugs.kde.org/show_bug.cgi?id=345992 Rewarp changed: What|Removed |Added CC||rew...@thestrayworld.com --- Comment #4 from Rewarp --- Since this is a keyboard shortcut issue, I am adding my own custom shortcut problem here as well. I have assigned the "Right" and "Left" key to Next and Previous message respectively. For some odd reason, The shortcut for "Focus on Next Message" is not the default Alt+Right, but is Right. This conflicts with my custom key for "Next Message". After changing "Focus on Next Message" to the default Alt+Right, the Right key works once to move to the next message, but on the second tap is suddenly reassigned to "Focus on Next Message again" Steps to reproduce: 1. Reassign shortcut for "Focus on Next Message" to default Alt+Right 2. Assign shortcut for "Next Message" to Right. 3. Press Right. Expected: The next email message should be selected. Instead: 1. The next message is selected. 2. The custom shortcut fails and is reassigned to "Focus on Next Message". -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 347740] Encrypted message not detected as encrypted message
https://bugs.kde.org/show_bug.cgi?id=347740 --- Comment #10 from Rewarp --- (In reply to tomaggio from comment #8) > Hi; > With kmail 5.1.3 it works again. So for me, this Bug is solved. Thanks. I will wait and see if it works on 5.1.3. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 347740] Encrypted message not detected as encrypted message
https://bugs.kde.org/show_bug.cgi?id=347740 --- Comment #7 from Rewarp --- I am now running KMail 5.1.2, and the workaround method no longer works. I am back to downloading the message separately before I am able to decrypt the message. Here's a screenshot as proof. https://imgur.com/sY3XrQl -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 360448] New: Visual artefact appearing in Akregator
https://bugs.kde.org/show_bug.cgi?id=360448 Bug ID: 360448 Summary: Visual artefact appearing in Akregator Product: akregator Version: unspecified Platform: Other URL: http://imgur.com/OWAZySV OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: rew...@thestrayworld.com A short period after I launch Kontact, visual artefacts with seemingly random snippets of whatever has been on the screen previously will cover up a portion of Akregator in Kontact. A screenshot illustrating the problem is included. Reproducible: Always Steps to Reproduce: 1. Launch Kontact 2. Switch to Akregator Actual Results: Visual artifact blocking part of the screen. Expected Results: Visual artefact should not be there. Problem disappears after restarting Kontact in the same session. But will reoccur. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 358501] New: New Message shortcut not working correctly
https://bugs.kde.org/show_bug.cgi?id=358501 Bug ID: 358501 Summary: New Message shortcut not working correctly Product: kmail2 Version: 5.1 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: commands and actions Assignee: kdepim-b...@kde.org Reporter: rew...@thestrayworld.com After successfully moving my KMail4 to KMail5, I discovered the Ctrl+N shortcut threw up an error. "The key sequence 'Ctrl+N' is ambiguous. Use 'Configure Shortcuts' from the 'Settings' menu to solve the ambiguity. No action will be triggered." The shortcut settings had not been changed from the default setting and no other application was in conflict with it. After assigning nothing to the custom shortcut to New Message, the actual shortcut for New Message worked again. Attempts to reassign the shortcut back to the default setting threw up this error: "The 'Ctrl+N' key combination is already used by the New Message... action. Please select a different one." It is possible that remnants of the shortcuts in KMail4 are still being run, hence resulting in a conflict. Reproducible: Always Steps to Reproduce: 1. Tries to use (default setting) Ctrl+N in KMail5 after upgrading from KMail4 Actual Results: Error message given. Expected Results: New message window should have launched. The computer is running openSUSE Tumbleweed with subscriptions to the Frameworks, Applications, and Extras repositories taking priority over stock repositories. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 357482] New: Plasma5 crashes when initially switching VPN servers.
https://bugs.kde.org/show_bug.cgi?id=357482 Bug ID: 357482 Summary: Plasma5 crashes when initially switching VPN servers. Product: plasmashell Version: 5.4.3 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: rew...@thestrayworld.com CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.4.3) Qt Version: 5.5.1 Operating System: Linux 4.3.3-2-default x86_64 Distribution: "openSUSE Tumbleweed (20151229) (x86_64)" -- Information about the crash: The crash appears to be a direct result of the KDE Wallet request for its password from the initial switching off of the VPN connection. 1. After disabling the VPN connection, KDE Wallet pops up and requests the password. 2. Connection to a new VPN is initiated which results in a momentary crash of Plasma 5. 3. Connection is however, successfully established after automated restart of Plasma 5. 4. Subsequent request for switching VPN servers are establiushed without issue. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd4f64138c0 (LWP 2837))] Thread 9 (Thread 0x7fd4df97f700 (LWP 2845)): #0 0x7fd4ef9a124d in poll () at /lib64/libc.so.6 #1 0x7fd4f4873432 in () at /usr/lib64/libxcb.so.1 #2 0x7fd4f4875007 in xcb_wait_for_event () at /usr/lib64/libxcb.so.1 #3 0x7fd4e1acee29 in () at /usr/lib64/libQt5XcbQpa.so.5 #4 0x7fd4f009294f in () at /usr/lib64/libQt5Core.so.5 #5 0x7fd4ef1a84a4 in start_thread () at /lib64/libpthread.so.0 #6 0x7fd4ef9a9bdd in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fd4dcb2d700 (LWP 2891)): #0 0x7fd4ef9a124d in poll () at /lib64/libc.so.6 #1 0x7fd4ec096264 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd4ec09636c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd4f02b752b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd4f026163a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd4f008db1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fd4f335a9a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fd4f009294f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fd4ef1a84a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fd4ef9a9bdd in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7fd4cae49700 (LWP 2918)): #0 0x7fd4ef1ae07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd4d59bbd6a in () at /usr/lib64/dri/radeonsi_dri.so #2 0x7fd4d59bb597 in () at /usr/lib64/dri/radeonsi_dri.so #3 0x7fd4ef1a84a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fd4ef9a9bdd in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7fd4c4fb1700 (LWP 2922)): #0 0x7fd4ec095a80 in g_main_context_query () at /usr/lib64/libglib-2.0.so.0 #1 0x7fd4ec0961df in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fd4ec09636c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd4f02b752b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fd4f026163a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fd4f008db1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fd4f335a9a5 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7fd4f009294f in () at /usr/lib64/libQt5Core.so.5 #8 0x7fd4ef1a84a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7fd4ef9a9bdd in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7fd4bf43a700 (LWP 2924)): #0 0x7fd4f008ad1a in QMutex::lock() () at /usr/lib64/libQt5Core.so.5 #1 0x7fd4f02b6aeb in () at /usr/lib64/libQt5Core.so.5 #2 0x7fd4ec09588d in g_main_context_prepare () at /usr/lib64/libglib-2.0.so.0 #3 0x7fd4ec096193 in () at /usr/lib64/libglib-2.0.so.0 #4 0x7fd4ec09636c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fd4f02b752b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fd4f026163a in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x7fd4f008db1c in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #8 0x7fd4f335a9a5 in () at /usr/lib64/libQt5Qml.so.5 #9 0x7fd4f009294f in () at /usr/lib64/libQt5Core.so.5 #10 0x7fd4ef1a84a4 in start_thread () at /lib64/libpthread.so.0 #11 0x7fd4ef9a9bdd in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7fd4bdbb9700 (LWP 2927)): #0 0x7fd4ef1ae07f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fd4f5b01a84 in () at /usr/lib64/libQt5Script.so.5 #2 0x7fd4f5b01ac9 in () at /usr/lib64/libQt5Scr
