[neon] [Bug 371466] New: Some web links don't work in Neon, throws numerous kde-open5 errors related to Qt
https://bugs.kde.org/show_bug.cgi?id=371466 Bug ID: 371466 Summary: Some web links don't work in Neon, throws numerous kde-open5 errors related to Qt Product: neon Version: unspecified Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Packages User Edition Assignee: neon-b...@kde.org Reporter: arco...@gmail.com CC: j...@jriddell.org, neon-b...@kde.org, sit...@kde.org This happens 100% of the time in Teamspeak. I've seen it occur in one other program but I can't remember which program it was. I do not have any issues opening links in Mint 17 with KDE4, or on any of my other non-KDE linux machines. Which leads me to believe this is strictly a KDE issue, and not a teamspeak bug. Clicking a link in the chat area in Teamspeak will produce the following errors: kde-open5: ./libQt5Widgets.so.5: version `Qt_5' not found (required by kde-open5) kde-open5: ./libQt5Core.so.5: version `Qt_5.7' not found (required by kde-open5) kde-open5: ./libQt5Core.so.5: version `Qt_5' not found (required by kde-open5) kde-open5: ./libQt5Gui.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5) kde-open5: ./libQt5Widgets.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5) kde-open5: ./libQt5Network.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5.7' not found (required by /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5KIOWidgets.so.5) kde-open5: ./libQt5Network.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5.7' not found (required by /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5KIOCore.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5.7' not found (required by /usr/lib/x86_64-linux-gnu/libKF5Service.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5Service.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5.7' not found (required by /usr/lib/x86_64-linux-gnu/libKF5I18n.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5I18n.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5.7' not found (required by /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5CoreAddons.so.5) kde-open5: ./libQt5Gui.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5) kde-open5: ./libQt5Widgets.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5.7' not found (required by /usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5JobWidgets.so.5) kde-open5: ./libQt5Gui.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5Completion.so.5) kde-open5: ./libQt5Widgets.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5Completion.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5.7' not found (required by /usr/lib/x86_64-linux-gnu/libKF5Completion.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5Completion.so.5) kde-open5: ./libQt5Gui.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5) kde-open5: ./libQt5Widgets.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5.7' not found (required by /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5IconThemes.so.5) kde-open5: ./libQt5Widgets.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5) kde-open5: ./libQt5Gui.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5.7' not found (required by /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5) kde-open5: ./libQt5Core.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5WindowSystem.so.5) kde-open5: ./libQt5Gui.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5) kde-open5: ./libQt5Widgets.so.5: version `Qt_5' not found (required by /usr/lib/x86_64-linux-gnu/libKF5ConfigWidgets.so.5) kde
[kdm] [Bug 356524] New: Login username appears outside login dialog for ~10 seconds.. then pops into position. Cant login until it fixes itself.
https://bugs.kde.org/show_bug.cgi?id=356524 Bug ID: 356524 Summary: Login username appears outside login dialog for ~10 seconds.. then pops into position. Cant login until it fixes itself. Product: kdm Version: unspecified Platform: Mint (Ubuntu based) URL: https://www.dropbox.com/s/k6xcrdmkaikwuwb/VID_20151211 _112030.mp4?dl=0 OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdm-bugs-n...@kde.org Reporter: arco...@gmail.com Bug tracker does not let me pick my version, I have v4.14.2 (default in Mint 17.2 x64 KDE). See attached URL for video demo of the issue. This started happening recently, and it happens every time. I can think of no major system changes have been made that may have caused this. The login name appears outside the login dialog for at least 10 seconds.. During this time, all text typed into the login box is in plain text (non-password). In about 10 seconds, the username correctly positions itself and the text box turns into a password box and I am able to log into the system. While I wait, I'm unable to login. Reproducible: Always I am somewhat new to KDE and Linux as a desktop in general, so if you need a different version number for another package, let me know. -- You are receiving this mail because: You are watching all bug changes.
[kdm] [Bug 356524] Login username appears outside login dialog for ~10 seconds.. then pops into position. Cant login until it fixes itself.
https://bugs.kde.org/show_bug.cgi?id=356524 Beer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Beer --- Nevermind I don't think this is related to KDE -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 255306] Slow transfers "TO" mounted cifs shares even on 1Gbps link
https://bugs.kde.org/show_bug.cgi?id=255306 Beer changed: What|Removed |Added CC||arco...@gmail.com --- Comment #28 from Beer --- I'm having the same issue. Copying a large file (2-3GB) to my NAS, my transfer speed is around 4-6MB/s. Files seem to copy fine with cp from terminal -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 254779] kgpg: prevent import of outdated keys
https://bugs.kde.org/show_bug.cgi?id=254779 --- Comment #6 from Rolf Eike Beer --- Put a merged patch (i.e. changes of both patches) into RB, but later commit the separated ones. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 254779] kgpg: prevent import of outdated keys
https://bugs.kde.org/show_bug.cgi?id=254779 Rolf Eike Beer changed: What|Removed |Added Status|CONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kgpg ||/95c6901392c17ef174a6318844 ||7f58d02338aeef Resolution|--- |FIXED --- Comment #8 from Rolf Eike Beer --- Git commit 95c6901392c17ef174a63188447f58d02338aeef by Rolf Eike Beer, on behalf of David Zaslavsky. Committed on 20/08/2016 at 07:07. Pushed by dakon into branch 'frameworks'. Show only valid keys in search results This adds - fields to SearchResult for expiration and revocation status - a proxy model to filter only valid keys from the search results - a checkbox to the keyserver search result dialog to toggle validity filtering REVIEW:128701 M +38 -19 keyservers.cpp M +3-3keyservers.h M +111 -14 model/kgpgsearchresultmodel.cpp M +87 -15 model/kgpgsearchresultmodel.h M +10 -0searchres.ui http://commits.kde.org/kgpg/95c6901392c17ef174a63188447f58d02338aeef -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 367689] kgpg shows fingerprint of subkey not of public key
https://bugs.kde.org/show_bug.cgi?id=367689 --- Comment #1 from Rolf Eike Beer --- Tested with 2.17.40, works fine there. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 367689] kgpg shows fingerprint of subkey not of public key
https://bugs.kde.org/show_bug.cgi?id=367689 --- Comment #4 from Rolf Eike Beer --- Sorry, my fault. My GnuPG shows only one fpr line, so this must work. Will check later on a different machine. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 367689] kgpg shows fingerprint of subkey not of public key
https://bugs.kde.org/show_bug.cgi?id=367689 --- Comment #5 from Rolf Eike Beer --- I see only one fpr line with both GnuPG 2.0 and 2.1. Which version are you using? -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 369274] "expert" button on key generation dialog doesn't bring up Konsole
https://bugs.kde.org/show_bug.cgi?id=369274 Rolf Eike Beer changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #4 from Rolf Eike Beer --- Could be plasma-related, as I can reproduce it on a machine with Plasma 5. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 369274] "expert" button on key generation dialog doesn't bring up Konsole
https://bugs.kde.org/show_bug.cgi?id=369274 Rolf Eike Beer changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||http://commits.kde.org/kgpg ||/af3b40cbb204b69f30b33777b1 ||0606a6814276c6 Status|CONFIRMED |RESOLVED Version Fixed In||16.12.0 --- Comment #5 from Rolf Eike Beer --- Git commit af3b40cbb204b69f30b33777b10606a6814276c6 by Rolf Eike Beer, on behalf of Steven Noonan. Committed on 11/10/2016 at 16:16. Pushed by dakon into branch 'master'. slotGenerateKey: correctly invoke GPG for interactive key generation While at it, use --full-gen-key if the given GnuPG binary is new enough. FIXED-IN:16.12.0 Signed-off-by: Steven Noonan M +10 -3keysmanager.cpp http://commits.kde.org/kgpg/af3b40cbb204b69f30b33777b10606a6814276c6 -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 369609] shows only white and blue for trust levels
https://bugs.kde.org/show_bug.cgi?id=369609 --- Comment #1 from Rolf Eike Beer --- Works for me. Maybe your trustdb is empty, so your private key is the only trusted one? -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 370444] deleting a key does not refresh the list
https://bugs.kde.org/show_bug.cgi?id=370444 --- Comment #1 from Rolf Eike Beer --- Works for me. What versions (KGpg, GnuPG) are you using? What says the debug output? -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 283551] kgpg crashed while reloading keys
https://bugs.kde.org/show_bug.cgi?id=283551 Rolf Eike Beer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Rolf Eike Beer --- Seems fixed. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 342237] kgpg stopped listing keys from keyring
https://bugs.kde.org/show_bug.cgi?id=342237 Rolf Eike Beer changed: What|Removed |Added Status|UNCONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Rolf Eike Beer --- Please check your gpg.conf for any unusual options if this still happens. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 330710] KGPG crashes when trying to mail a signature of a key
https://bugs.kde.org/show_bug.cgi?id=330710 Rolf Eike Beer changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|UNCONFIRMED |RESOLVED --- Comment #3 from Rolf Eike Beer --- Given that it's quite old and not repdroducible I'll close this. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 369609] shows only white and blue for trust levels
https://bugs.kde.org/show_bug.cgi?id=369609 --- Comment #4 from Rolf Eike Beer --- The trust and user trust things are GnuPG details that I can only show, but have no control over their functionality. I've written up something to explain how it works in the documentation: https://docs.kde.org/trunk5/en/kdeutils/kgpg/manage.html I guess you have no keys in your keyring that are signed by your private key. This is why none of them are trusted. I suggest signing one of them, preferably using a local-only signature as it is for testing purposes. Then this key should become trusted, and show a different color. Afterwards the local signature can be deleted again. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 371004] gpg groups using an non-standard id, are not displayed correctly and can not be edited in kgpg
https://bugs.kde.org/show_bug.cgi?id=371004 --- Comment #1 from Rolf Eike Beer --- Git commit f33f8c759a13da6ab663bd9fd1baef17a238836d by Rolf Eike Beer. Committed on 19/10/2016 at 17:37. Pushed by dakon into branch 'master'. tolerate group member ids to begin with 0x M +5-2core/KGpgGroupNode.cpp http://commits.kde.org/kgpg/f33f8c759a13da6ab663bd9fd1baef17a238836d -- You are receiving this mail because: You are watching all bug changes.
[kio] [Bug 162485] KDE 4 SSL Certificate support incomplete
https://bugs.kde.org/show_bug.cgi?id=162485 --- Comment #88 from Rolf Eike Beer --- Even if it is unrelated to that bug: for OpenSUSE you have the possibility to just install the package ca-certificates-cacert and have it in the system store without further work. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 254779] kgpg: prevent import of outdated keys
https://bugs.kde.org/show_bug.cgi?id=254779
--- Comment #2 from Rolf Eike Beer ---
The patch looks good in principle, however I have some nitpicks:
Optional:
-if you have a KDE account I would welcome if you could put the patch into
Reviewboard instead, referencing this bug id
-if at all possible I would like to have this patch rebased on the frameworks
branch as Applications/16.08 is feature and string frozen and I hope we will
get the frameworks branch ready before 16.12, i.e. there will likely be no
further releases from the master branch
Mandatory:
-as you are using git to create the patch, please do a local "git commit" and
"git format-patch -1" to generate the patch, containing your correct author
information as well as a "BUG:254779" and "REVIEW:…" line
-m_expiry is used but not declared
-the initializer list for KGpgSortFilterProxyModel misses some linebreaks, see
e.g. SearchResult for an example
-KGpgSortFilterProxyModel is a bit too general as class name, as this filter is
about search results I would suggest something like
KGpgSearchResultFilterModel
-since this class can only properly work with a KGpgSearchResultModel as input
model I would add this as a required argument in the constructor, so no
invalid state can accidentially happen
-the logic in filterAcceptsRow() should be rewritten to first check the parent
filterAcceptsRow(). If that returns false, just return false, otherwise don't
bother to check it in the rest of the function. Since both branches of the
final "if" end returning the same value move that code out of the if. The
coding style for the else is also wrong, it should be "} else {" in one line,
although the else can go entirely away now that the if-branch became empty.
-I obviously fail the wtf-test with my model design, so I suggest you remove
your comment in this commit and come up with one that has a better code design
Not that mandatory:
-even more, since KGpgSearchResultModel is now never used "alone" I would make
the former model an implementation detail of the proxy model (i.e. private)
and have the new class as KGpgSearchResultModel
--
You are receiving this mail because:
You are watching all bug changes.
[kgpg] [Bug 254779] kgpg: prevent import of outdated keys
https://bugs.kde.org/show_bug.cgi?id=254779 --- Comment #4 from Rolf Eike Beer --- > I didn't change the storage model (the part that fails the "wtf test") > because > I thought it best to limit my changes to those actually necessary to > add the > feature. But since you mentioned it, I will look into changing the > model, and > if it works out, I'll include both changes in the revised patch. Please do that in 2 patches for easier review, in any order that fits your needs. > m_expiry was already declared as a private field of SearchResult; it > was just > never used before. Sorry, I was looking at the frameworks branch, where it got removed for exactly that reason ;) Eike -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 365791] Error when deleting private key with GnuPG 2.1
https://bugs.kde.org/show_bug.cgi?id=365791 Rolf Eike Beer changed: What|Removed |Added Latest Commit||http://commits.kde.org/kgpg ||/b4905e609e8dd44f27c5f8ec3b ||4ef08d7235426a Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from Rolf Eike Beer --- Git commit fd934f1763f33e862dc5385a4f77072e80336faa by Rolf Eike Beer. Committed on 25/07/2016 at 18:12. Pushed by dakon into branch 'Applications/16.08'. ignore PINENTRY_LAUNCHED messages from GnuPG Those seem new in GnuPG 2.1 but are of no interest for KGpg (yet). M +2-0transactions/kgpgtransaction.cpp http://commits.kde.org/kgpg/fd934f1763f33e862dc5385a4f77072e80336faa --- Comment #2 from Rolf Eike Beer --- Git commit b4905e609e8dd44f27c5f8ec3b4ef08d7235426a by Rolf Eike Beer. Committed on 25/07/2016 at 18:15. Pushed by dakon into branch 'Applications/16.08'. do not fail deleting a key if KEY_CONSIDERED message is seen These are new in GnuPG 2.1. For extra sanity check that the given key fingerprint is actually in the list of keys that are about to be deleted. M +18 -1transactions/kgpgdelkey.cpp http://commits.kde.org/kgpg/b4905e609e8dd44f27c5f8ec3b4ef08d7235426a -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 365791] Error when deleting private key with GnuPG 2.1
https://bugs.kde.org/show_bug.cgi?id=365791 Rolf Eike Beer changed: What|Removed |Added Version Fixed In||16.08 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 366245] New: heigt value used in globe projection leads to blurred images
https://bugs.kde.org/show_bug.cgi?id=366245 Bug ID: 366245 Summary: heigt value used in globe projection leads to blurred images Product: marble Version: 1.14 (KDE Applications 16.04) Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: k...@opensource.sf-tec.de The height values on bigger zoom levels differs from globe to merkator projection, so the tiles will get scaled and everything on them becomes blurred. On high zoom levels there is no reason to not use the same height value, the globe effect is so small it should be entirely ignored there. Reproducible: Always Steps to Reproduce: 1. use a map of something like 40x20 kilometers or anything smaller 2. switch between globe and merkator projections 3. observe that the images get blurred in globe 4. zoom in even more, where the same problem will be visible for any other zoom level -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 357362] Provide key expiration notifications
https://bugs.kde.org/show_bug.cgi?id=357362 --- Comment #1 from Rolf Eike Beer --- I wonder if a setting per key is really needed, do you really have that many secret keys that this would have to be set per key? -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 357362] Provide key expiration notifications
https://bugs.kde.org/show_bug.cgi?id=357362 --- Comment #3 from Rolf Eike Beer --- > I think it is needed. > > Personally, I only need notifications for keys I'm responsible for and need > to update or keep track of. For example, I would not care much when another > person's key is about to expire, unless I want to manually update that key > from a keyserver. I was talking about only watching keys where you have the secret key for. > PS: Is kgpg also missing a "refresh all keys" feature? Should I file a > separate bug for this? Ctrl-A, rightclick, refresh. That's fast enough that I will not add a shortcut for this. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 290221] KGpg 2.6.80 fails to start with nonexistant .gnupg directory
https://bugs.kde.org/show_bug.cgi?id=290221 --- Comment #18 from Rolf Eike Beer --- Distros sometimes put their configuration files at different places, so I fear you need do "find /usr /home -name kgpgrc" to find the wrong file. Seems like noone noticed LinuxMint to fix their 3 year old stuff in the last 3 years, so you still get the same bug. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 290221] KGpg 2.6.80 fails to start with nonexistant .gnupg directory
https://bugs.kde.org/show_bug.cgi?id=290221 --- Comment #20 from Rolf Eike Beer --- KGpg will not use the "options" file when not explicitely told to. So this is either still hiding somewhere (try kreadconfig --file kgpgrc --group "GPG Settings" --key "gpg_config_path"), or there is something else going on. Try running kgpg from the command line and see if that prints anything helpful. If not, try running: strace -f -eopen kgpg --nofork > kgpg.log 2>&1 and then attach the logfile. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 290221] KGpg 2.6.80 fails to start with nonexistant .gnupg directory
https://bugs.kde.org/show_bug.cgi?id=290221 --- Comment #23 from Rolf Eike Beer --- > I ran kreadconfig - which correctly told me what I already knew: > @HOME/.gnupg That looks fishy, it should return the name of the configuration _file_, not _directory_. Otherwise it can't work. I get this: $ kreadconfig --file kgpgrc --group "GPG Settings" --key "gpg_config_path" /home/eike/.gnupg/gpg.conf -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 290221] KGpg 2.6.80 fails to start with nonexistant .gnupg directory
https://bugs.kde.org/show_bug.cgi?id=290221 --- Comment #26 from Rolf Eike Beer --- > Aha. Where should I look to fish for a solution? You need to find the kgpgrc that sets the wrong gpg_config_path. Either fix it there or just remove it. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 357746] The document could not been saved, as the selected codec is not supported.
https://bugs.kde.org/show_bug.cgi?id=357746 Rolf Eike Beer changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #1 from Rolf Eike Beer --- The problem is not limited to symmetric encryption, I see it every now and then but have not been able to nail it down. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 321606] Cannot sign messages
https://bugs.kde.org/show_bug.cgi?id=321606 --- Comment #11 from Rolf Eike Beer --- > Any chance it will be resolved fast? What would be an easy turn around > in the > mean time? (except recompiling from source) > It's quite critical function. I still cannot reproduce this. Is your pinentry setup working, e.g. do you get a new window asking for the passphrase e.g. when you sign a key or decrypt a text? -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 340676] KGpg should support GnuPG 2.1
https://bugs.kde.org/show_bug.cgi?id=340676 --- Comment #12 from Rolf Eike Beer --- > Sorry, I meant Kgpg 2.16.1 on KDE 4.14.14, which is what it is > reporting in its > about dialog. It is packaged from KDE Applications 15.08.3 though. Please start kdebugdialog and make sure that section 2100 is enabled. Then quit all running KGpg instances and start a new instance from commandline. There should be output like this: kgpg(19166) GnupgBinary::setBinary: version is "2.1.10" 131338 What is the exact output of your version? -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 340676] KGpg should support GnuPG 2.1
https://bugs.kde.org/show_bug.cgi?id=340676 --- Comment #15 from Rolf Eike Beer --- KGpg will pick gpg2 first if you run the first start wizard. Afterwards it will stick with whatever was found there or what you explicitely set in the settings dialog. If you did never run the first start wizard because your distro shipped a default config file, then it may be a config issue, if gpg2 is actually the default gpg on your distro. > kgpg(5082) GnupgBinary::setBinary: checking version of GnuPG executable > "gpg2" > kgpg(5082) GnupgBinary::setBinary: version is "2.1.9" 131337 Is the warning about the non-running agent now gone? For the 1.4 version it will be actually be right as your agent was probably not started. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 368462] Add support for ECC keys (primary and subkeys)
https://bugs.kde.org/show_bug.cgi?id=368462 Rolf Eike Beer changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |CONFIRMED --- Comment #4 from Rolf Eike Beer --- Your approach looks sane so far. Please post patches to git.reviewboard.kde.org, that is the better suited tool for patch discussion. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 368462] Add support for ECC keys (primary and subkeys)
https://bugs.kde.org/show_bug.cgi?id=368462 --- Comment #5 from Rolf Eike Beer --- And please base any feature patches on the frameworks branch if possible, if not, then use master. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368855] changing files via git (rebase, checkout) causes 100% CPU usage on 2 cores
https://bugs.kde.org/show_bug.cgi?id=368855 Rolf Eike Beer changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #2 from Rolf Eike Beer --- Thread 14 (Thread 0x7fe1a8c3f700 (LWP 10656)): #0 0x7fe203b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe1fe47f86b in () at /usr/lib64/libQt5Script.so.5 #2 0x7fe1fe47f899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7fe209ddc02d in clone () at /lib64/libc.so.6 Thread 13 (Thread 0x7fe1aa5ab700 (LWP 10635)): #0 0x7fe209dd3bfd in poll () at /lib64/libc.so.6 #1 0x7fe202e94e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe202e94f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe20a700d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe20a6a7d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe20a4c961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe20a4ce32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fe209ddc02d in clone () at /lib64/libc.so.6 Thread 12 (Thread 0x7fe18bfff700 (LWP 10528)): #0 0x7fe209dd3bfd in poll () at /lib64/libc.so.6 #1 0x7fe202e94e64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7fe202e94f7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fe20a700d6c in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fe20a6a7d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7fe20a4c961a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7fe20a4ce32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fe209ddc02d in clone () at /lib64/libc.so.6 Thread 11 (Thread 0x7fe1aadac700 (LWP 10515)): #0 0x7fe203b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe20a4cf34b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fe1ff2b465f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fe1ff2b843a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fe1ff2b26cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fe1ff2b6005 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fe20a4ce32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fe209ddc02d in clone () at /lib64/libc.so.6 Thread 10 (Thread 0x7fe1ab5ad700 (LWP 10514)): #0 0x7fe203b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe20a4cf34b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fe1ff2b465f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fe1ff2b843a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fe1ff2b26cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fe1ff2b8481 in () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fe1ff2b26cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #7 0x7fe1ff2b6005 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #8 0x7fe20a4ce32f in () at /usr/lib64/libQt5Core.so.5 #9 0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0 #10 0x7fe209ddc02d in clone () at /lib64/libc.so.6 Thread 9 (Thread 0x7fe1abdae700 (LWP 10513)): #0 0x7fe203b1403f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7fe20a4cf34b in QWaitCondition::wait(QMutex*, unsigned long) () at /usr/lib64/libQt5Core.so.5 #2 0x7fe1ff2b465f in ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*, bool, bool, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #3 0x7fe1ff2b843a in () at /usr/lib64/libKF5ThreadWeaver.so.5 #4 0x7fe1ff2b26cb in ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at /usr/lib64/libKF5ThreadWeaver.so.5 #5 0x7fe1ff2b6005 in ThreadWeaver::Thread::run() () at /usr/lib64/libKF5ThreadWeaver.so.5 #6 0x7fe20a4ce32f in () at /usr/lib64/libQt5Core.so.5 #7 0x7fe203b100a4 in start_thread () at /lib64/libpthread.so.0 #8 0x7fe209ddc02d in clone () at /lib64/libc.so.6 Thread 8 (Thread 0x7fe1ac5af70
[kaddressbook] [Bug 275938] Cannot open multiple addresses in KAddressbook at the same time
https://bugs.kde.org/show_bug.cgi?id=275938 Rolf Eike Beer changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Version|unspecified |5.3.0 Status|NEEDSINFO |CONFIRMED --- Comment #3 from Rolf Eike Beer --- Still in 5.3.0 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 311271] "Open in background tab" opens in foreground tab
https://bugs.kde.org/show_bug.cgi?id=311271 Rolf Eike Beer changed: What|Removed |Added Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #6 from Rolf Eike Beer --- Works in 5.3.0. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 273391] Akregator should not ask to restore session if there is nothing to restore
https://bugs.kde.org/show_bug.cgi?id=273391 Rolf Eike Beer changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Version|1.7.0 |5.3.0 Resolution|WAITINGFORINFO |--- --- Comment #3 from Rolf Eike Beer --- Still happens in 5.3.0 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 332368] Passing a PGP message via KToolInvocation::invokeMailer() it will not show up in the composer
https://bugs.kde.org/show_bug.cgi?id=332368 Rolf Eike Beer changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Ever confirmed|0 |1 Version|4.12.3 |5.3.0 Resolution|WAITINGFORINFO |--- --- Comment #4 from Rolf Eike Beer --- Still in 5.3.0 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 369382] New: Middle mouse click on article title behaves like left mouse button
https://bugs.kde.org/show_bug.cgi?id=369382 Bug ID: 369382 Summary: Middle mouse click on article title behaves like left mouse button Product: akregator Version: 5.3.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: k...@opensource.sf-tec.de When I middle-click on the title of an article in the article view the action of the left mouse is performed, not the one of the middle mouse button. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 207194] UTF-8 is mangled when passed through runner
https://bugs.kde.org/show_bug.cgi?id=207194 Rolf Eike Beer changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from Rolf Eike Beer --- Seems to work in Kontact 5.3.0 and Plasma 5.7.4. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 369434] New: Loop devices never disappear
https://bugs.kde.org/show_bug.cgi?id=369434 Bug ID: 369434 Summary: Loop devices never disappear Product: dolphin Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: k...@opensource.sf-tec.de I use loop devices a lot to write e.g. partitions for embedded devices. When they are created, they also show up in Dolphin. However, if they are destroyed, Dolphin keeps showing them indefinitely. This happens both in KDE4 based and KF5 based Dolphin versions. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 369435] New: Splash screen does not disappear on primary monitor
https://bugs.kde.org/show_bug.cgi?id=369435 Bug ID: 369435 Summary: Splash screen does not disappear on primary monitor Product: kwin Version: 5.7.4 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: k...@opensource.sf-tec.de I have a setup with 2 monitors. If I login the splash screen shows up on both of them. After a few seconds the one on the primary monitor just stalls, while the secondary monitor continues and finally disappears, showing the started programs. I have to call "kwin_x11 --replace" to get the first monitor in a working state. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 369274] "expert" button on key generation dialog doesn't bring up Konsole
https://bugs.kde.org/show_bug.cgi?id=369274 --- Comment #2 from Rolf Eike Beer --- It works for me even without the patch, what is your setup? Konsole version etc.? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 368083] New: Crash when opening link in background browser
https://bugs.kde.org/show_bug.cgi?id=368083 Bug ID: 368083 Summary: Crash when opening link in background browser Product: plasmashell Version: 5.5.5 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: k...@opensource.sf-tec.de CC: bhus...@gmail.com, plasma-b...@kde.org Application: plasmashell (5.5.5) Qt Version: 5.5.1 Operating System: Linux 4.7.2-1.g34ba8d6-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I clicked a link in Kontact (KMail), which was sent to Chromium. This would usually highlight Chromium in the taskbar, instead Plasma crashed. -- Backtrace: Application: Plasma (plasmashell), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2b57f337c0 (LWP 1829))] Thread 8 (Thread 0x7f2a937a5700 (LWP 2035)): #0 0x7f2b5142ebfd in poll () at /lib64/libc.so.6 #1 0x7f2b4db0be64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2b4db0bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2b51d5bd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2b51d02d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2b51b2461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2a94df2cf7 in KCupsConnection::run() () at /usr/lib64/libkcupslib.so #7 0x7f2b51b2932f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f2b50c380a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2b5143702d in clone () at /lib64/libc.so.6 Thread 7 (Thread 0x7f2a9f924700 (LWP 1939)): #0 0x7f2b5142ebfd in poll () at /lib64/libc.so.6 #1 0x7f2b4db0be64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2b4db0bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2b51d5bd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2b51d02d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2b51b2461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2b559d4282 in () at /usr/lib64/libQt5Quick.so.5 #7 0x7f2b51b2932f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f2b50c380a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2b5143702d in clone () at /lib64/libc.so.6 Thread 6 (Thread 0x7f2b266f2700 (LWP 1874)): #0 0x7f2b50c3c03f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0 #1 0x7f2b5760786b in () at /usr/lib64/libQt5Script.so.5 #2 0x7f2b57607899 in () at /usr/lib64/libQt5Script.so.5 #3 0x7f2b50c380a4 in start_thread () at /lib64/libpthread.so.0 #4 0x7f2b5143702d in clone () at /lib64/libc.so.6 Thread 5 (Thread 0x7f2b27fff700 (LWP 1867)): #0 0x7f2b5142ebfd in poll () at /lib64/libc.so.6 #1 0x7f2b4db0be64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2b4db0bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2b51d5bd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2b51d02d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2b51b2461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2b54e38e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f2b51b2932f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f2b50c380a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2b5143702d in clone () at /lib64/libc.so.6 Thread 4 (Thread 0x7f2b2d903700 (LWP 1866)): #0 0x7f2b5142ebfd in poll () at /lib64/libc.so.6 #1 0x7f2b4db0be64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2b4db0bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2b51d5bd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2b51d02d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2b51b2461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2b54e38e18 in () at /usr/lib64/libQt5Qml.so.5 #7 0x7f2b51b2932f in () at /usr/lib64/libQt5Core.so.5 #8 0x7f2b50c380a4 in start_thread () at /lib64/libpthread.so.0 #9 0x7f2b5143702d in clone () at /lib64/libc.so.6 Thread 3 (Thread 0x7f2b3ad4f700 (LWP 1851)): #0 0x7f2b5142ebfd in poll () at /lib64/libc.so.6 #1 0x7f2b4db0be64 in () at /usr/lib64/libglib-2.0.so.0 #2 0x7f2b4db0bf7c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7f2b51d5bd8b in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7f2b51d02d53 in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #5 0x7f2b51b2461a in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #6 0x7f2b54e38e18 in () a
[kgpg] [Bug 367689] kgpg shows fingerprint of subkey not of public key
https://bugs.kde.org/show_bug.cgi?id=367689 Rolf Eike Beer changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED Latest Commit||http://commits.kde.org/kgpg ||/4b01a60a1f43f2e72b082c8156 ||46183593f40ad0 Version Fixed In||16.08.2 --- Comment #9 from Rolf Eike Beer --- Git commit 4b01a60a1f43f2e72b082c815646183593f40ad0 by Rolf Eike Beer. Committed on 09/09/2016 at 14:27. Pushed by dakon into branch 'Applications/16.08'. do not set subkey fingerprint as key fingerprint In case GnuPG has the option "with-subkey-fingerprints" configured by default these will show up also in the normal key listing. In this case currentSNode will never be set, which resulted in these fingerprints overwriting the actual key fingerprint. FIXED-IN:16.08.2 M +1-1kgpginterface.cpp http://commits.kde.org/kgpg/4b01a60a1f43f2e72b082c815646183593f40ad0 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368855] New: changing files via git (rebase, checkout) causes 100% CPU usage on 2 core
https://bugs.kde.org/show_bug.cgi?id=368855 Bug ID: 368855 Summary: changing files via git (rebase, checkout) causes 100% CPU usage on 2 core Product: kdevelop Version: 5.0.0 Platform: openSUSE RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdevelop-bugs-n...@kde.org Reporter: k...@opensource.sf-tec.de I have a 2core+HT system. When I change the files using git from the commandline (git checkout some-other-branch or git rebase) it often happens that the CPU usage on 2 cores goes to 100% (i.e. 50% system load). I can normally quit KDevelop afterwards, everything is fine if I open it again. Reproducible: Sometimes -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 368855] changing files via git (rebase, checkout) causes 100% CPU usage on 2 cores
https://bugs.kde.org/show_bug.cgi?id=368855 Rolf Eike Beer changed: What|Removed |Added Summary|changing files via git |changing files via git |(rebase, checkout) causes |(rebase, checkout) causes |100% CPU usage on 2 core|100% CPU usage on 2 cores -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 359922] QCA: make: error: ‘QIODevice’ has not been declared void update(QIODevice *file);
https://bugs.kde.org/show_bug.cgi?id=359922 Rolf Eike Beer changed: What|Removed |Added CC||k...@opensource.sf-tec.de --- Comment #2 from Rolf Eike Beer --- Which version of qca are you using? It should be fixed in 2.1.1, see https://quickgit.kde.org/?p=qca.git&a=commit&h=66b9754170759d9333d5fc1e348642814d0310dd -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 364352] Shouldn't qca_safetimer.h use Q_SLOTS and Q_SIGNALS?
https://bugs.kde.org/show_bug.cgi?id=364352 Rolf Eike Beer changed: What|Removed |Added CC||k...@opensource.sf-tec.de --- Comment #2 from Rolf Eike Beer --- Which version of qca are you using? It should be fixed in 2.1.1, see https://quickgit.kde.org/?p=qca.git&a=commit&h=66b9754170759d9333d5fc1e348642814d0310dd -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 359922] QCA: make: error: ‘QIODevice’ has not been declared void update(QIODevice *file);
https://bugs.kde.org/show_bug.cgi?id=359922 --- Comment #3 from Rolf Eike Beer --- Wrong link for this bug, this should be the correct one: https://quickgit.kde.org/?p=qca.git&a=commit&h=7207e6285e932044cd66d49d0dc484666cfb0092 -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 359922] QCA: make: error: ‘QIODevice’ has not been declared void update(QIODevice *file);
https://bugs.kde.org/show_bug.cgi?id=359922 Rolf Eike Beer changed: What|Removed |Added Version|unspecified |2.1.0 -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 364495] New: Compilation for ARM fails with Qt 5.7.0 because of narrowing conversion:
https://bugs.kde.org/show_bug.cgi?id=364495
Bug ID: 364495
Summary: Compilation for ARM fails with Qt 5.7.0 because of
narrowing conversion:
Product: qca
Version: 2.1.1
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: dr...@land.ru
Reporter: k...@opensource.sf-tec.de
CC: br...@frogmouth.net, jus...@affinix.com
Using gcc 5.4.0, worked fine with 5.6.1.
[ 35%] Building CXX object
src/CMakeFiles/qca-qt5.dir/botantools/botan/exceptn.cpp.o
cd /tmp/e2/build/build/src && /opt/emlix/test/bin/arm-unknown-linux-gnueabi-g++
--sysroot=/opt/emlix/test/sysroot -DBOTAN_EXT_ALLOC_MMAP -DBOTAN_EXT_MUTEX_QT
-DBOTAN_KARAT_MUL_THRESHOLD=12 -DBOTAN_KARAT_SQR_THRESHOLD=12
-DBOTAN_MINIMAL_BIGINT -DBOTAN_MP_WORD_BITS=32 -DBOTAN_NO_CONF_H
-DBOTAN_NO_INIT_H -DBOTAN_TOOLS_ONLY -DBOTAN_TYPES_QT -DQCA_MAKEDLL
-DQCA_PLUGIN_PATH=\"/opt/emlix/test/sysroot/usr/lib/qt5/plugins\"
-DQCA_SYSTEMSTORE_PATH=\"/tmp/e2/build/qca/certs/rootcerts.pem\" -DQT_CORE_LIB
-DQT_DISABLE_DEPRECATED_BEFORE=0 -DQT_NO_DEBUG -D_BSD_SOURCE
-I/tmp/e2/build/build/src -I/tmp/e2/build/qca/src
-I/tmp/e2/build/qca/include/QtCrypto -I/tmp/e2/build/build
-I/tmp/e2/build/qca/src/support -I/tmp/e2/build/qca/src/botantools/botan
-isystem /opt/emlix/test/sysroot/usr/include/qt5 -isystem
/opt/emlix/test/sysroot/usr/include/qt5/QtCore -isystem
/opt/emlix/test/mkspecs/emlix/linux-arm-g++
-I/opt/emlix/test/sysroot/usr/include/qt5/QtNetwork -Wcast-align
-Wnon-virtual-dtor -Wno-long-long -ansi -Wundef -Wchar-subscripts -Wall -W
-Wpointer-arith -Wwrite-strings -Wformat-security -fno-check-new -fno-common
-fPIC -fPIC -std=gnu++11 -o
CMakeFiles/qca-qt5.dir/botantools/botan/exceptn.cpp.o -c
/tmp/e2/build/qca/src/botantools/botan/exceptn.cpp
In file included from
/opt/emlix/test/sysroot/usr/include/c++/5.4.0/arm-unknown-linux-gnueabi/bits/os_defines.h:39:0,
from
/opt/emlix/test/sysroot/usr/include/c++/5.4.0/arm-unknown-linux-gnueabi/bits/c++config.h:482,
from /opt/emlix/test/sysroot/usr/include/c++/5.4.0/cstddef:44,
from
/opt/emlix/test/sysroot/usr/include/qt5/QtCore/qglobal.h:45,
from
/opt/emlix/test/sysroot/usr/include/qt5/QtCore/QtGlobal:1,
from /tmp/e2/build/qca/src/botantools/botan/botan/types.h:38,
from
/tmp/e2/build/qca/src/botantools/botan/botan/exceptn.h:37,
from /tmp/e2/build/qca/src/botantools/botan/exceptn.cpp:34:
/opt/emlix/test/sysroot/usr/include/features.h:148:3: warning: #warning
"_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE" [-Wcpp]
# warning "_BSD_SOURCE and _SVID_SOURCE are deprecated, use _DEFAULT_SOURCE"
^
/tmp/e2/build/qca/src/qca_textfilter.cpp: In function 'QByteArray
QCA::b64decode(const QByteArray&, bool*)':
/tmp/e2/build/qca/src/qca_textfilter.cpp:314:2: error: narrowing conversion of
'-1' from 'int' to 'char' inside { } [-Wnarrowing]
};
^
Reproducible: Always
--
You are receiving this mail because:
You are watching all bug changes.
[qca] [Bug 364352] Shouldn't qca_safetimer.h use Q_SLOTS and Q_SIGNALS?
https://bugs.kde.org/show_bug.cgi?id=364352 Rolf Eike Beer changed: What|Removed |Added Version|unspecified |2.1.0 Status|UNCONFIRMED |RESOLVED Latest Commit||66b9754170759d9333d5fc1e348 ||642814d0310dd Resolution|--- |FIXED Version Fixed In||2.1.1 -- You are receiving this mail because: You are watching all bug changes.
[qca] [Bug 364495] Compilation for ARM fails with Qt 5.7.0 because of narrowing conversion:
https://bugs.kde.org/show_bug.cgi?id=364495
Rolf Eike Beer changed:
What|Removed |Added
Latest Commit||http://commits.kde.org/qca/
||601fd3a05141c614ae48a3ddac4
||4194d669eaae1
Resolution|--- |FIXED
Status|UNCONFIRMED |RESOLVED
--- Comment #1 from Rolf Eike Beer ---
Git commit 601fd3a05141c614ae48a3ddac44194d669eaae1 by Rolf Eike Beer.
Committed on 27/06/2016 at 16:24.
Pushed by dakon into branch 'master'.
fix base64 decoding on ARM
This code was broken on ARM and other architectures where "char" is unsigned by
default.
First, it breaks with newer compilers with errors like:
.../src/qca_textfilter.cpp:314:2: error: narrowing conversion of '-1' from
'int' to 'char' inside { } [-Wnarrowing]
Second, if the compiler would just allow this conversion then the unsigned char
would hold 255, which would not be sign extended when cast to an int later, so
all the checks "< 0" will never trigger, and so invalid input characters cannot
be detected.
REVIEW:128295
M +1-1src/qca_textfilter.cpp
http://commits.kde.org/qca/601fd3a05141c614ae48a3ddac44194d669eaae1
--
You are receiving this mail because:
You are watching all bug changes.
[kgpg] [Bug 340802] The export option "Sauberer Schlüssel" is not documented
https://bugs.kde.org/show_bug.cgi?id=340802 --- Comment #2 from Rolf Eike Beer --- Not yet. Patches are welcome. -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 340802] The export option "Sauberer Schlüssel" is not documented
https://bugs.kde.org/show_bug.cgi?id=340802 --- Comment #4 from Rolf Eike Beer --- It means that just the key itself is exported including it's subkeys, but excluding all signatures. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 353958] Akregator marks all unread feeds in list as read when set status to unread and click on one of the unread articles
https://bugs.kde.org/show_bug.cgi?id=353958 Rolf Eike Beer changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED CC||k...@opensource.sf-tec.de --- Comment #7 from Rolf Eike Beer --- *** This bug has been marked as a duplicate of bug 350731 *** -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 354746] Click article marks all articles in feed as read
https://bugs.kde.org/show_bug.cgi?id=354746 Rolf Eike Beer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||k...@opensource.sf-tec.de --- Comment #2 from Rolf Eike Beer --- *** This bug has been marked as a duplicate of bug 350731 *** -- 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 Rolf Eike Beer changed: What|Removed |Added CC||d_cork...@rogers.com --- Comment #15 from Rolf Eike Beer --- *** Bug 354746 has been marked as a duplicate of this bug. *** -- 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 Rolf Eike Beer changed: What|Removed |Added CC||k...@opensource.sf-tec.de -- 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 Rolf Eike Beer changed: What|Removed |Added CC||tonym...@gmail.com --- Comment #14 from Rolf Eike Beer --- *** Bug 353958 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 359089] Using your Kgpg to encrypt/decrypt files, unable to PASTE passphrase
https://bugs.kde.org/show_bug.cgi?id=359089 Rolf Eike Beer changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #1 from Rolf Eike Beer --- Sorry, this is the wrong bugtracker for this. Pinentry is a totally separate component, in fact there are multiple versions, they are neither related to KDE nor to KGpg. I've tested it using pinentry-qt on my system, and it works fine. On the other hand, the passphrase for the GnuPG key is a secret itself, having it stored elsewhere and pasted to GnuPG seems strange… -- You are receiving this mail because: You are watching all bug changes.
[kgpg] [Bug 359089] Using your Kgpg to encrypt/decrypt files, unable to PASTE passphrase
https://bugs.kde.org/show_bug.cgi?id=359089 --- Comment #3 from Rolf Eike Beer --- As I said: this is a pinentry problem, which is nothing I can do anything about. Please ask for help there. KGpg does not even trigger this window itself, it is triggered by GnuPG. -- You are receiving this mail because: You are watching all bug changes.
