[Akonadi] [Bug 485426] Google Groupware agent stops syncing after a while
https://bugs.kde.org/show_bug.cgi?id=485426 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 485222] KMail Mail Display shows wrong date (just cutoff from the plain header, not regarding timezone information)
https://bugs.kde.org/show_bug.cgi?id=485222 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467186] Rectangular Region toolbar backgrounds are too transparent
https://bugs.kde.org/show_bug.cgi?id=467186 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 470832] New: If clazy-standalone fails for one file no fixes are written
https://bugs.kde.org/show_bug.cgi?id=470832 Bug ID: 470832 Summary: If clazy-standalone fails for one file no fixes are written Classification: Developer tools Product: clazy Version: unspecified Platform: openSUSE OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: woebbek...@kde.org CC: smart...@kde.org Target Milestone: --- Hi, I'm running clazy 1.11 and I use find . -name "*cpp" | xargs clazy-standalone --checks=old-style-connect --export-fixes=fixes.yaml -p compile_commands.json to convert old style connects to new syntax. If clazy-standalone fails for one CPP (because it isn't in the JSON file) no fixes.yaml is written. I've to delete the non contained CPP and run clazy-standalone again. Please write the fixes in every case. Cheers, André -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 392795] Support QOverload<>::of in fix-old-style-connect
https://bugs.kde.org/show_bug.cgi?id=392795 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org --- Comment #2 from Andre Woebbeking --- Would be really nice to have. -- You are receiving this mail because: You are watching all bug changes.
[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 448630] Google account is removed after being added and configured
https://bugs.kde.org/show_bug.cgi?id=448630 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 434118] Graphical artifacts since updating to 5.21.1
https://bugs.kde.org/show_bug.cgi?id=434118 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org --- Comment #11 from Andre Woebbeking --- I had similar artifacts after upgrading to 5.23. Finally I had a look at ~/.config/kwinrc and found: [Compositing] AnimationSpeed[$d] Backend=OpenGL Enabled=true GLColorCorrection=false GLCore=true GLPlatformInterface=egl GLTextureFilter=2 HiddenPreviews=5 OpenGLIsUnsafe=false UnredirectFullscreen=false XRenderSmoothScale=false after I removed GLPlatformInterface=egl GLTextureFilter=2 all work fine again. I also have Intel HD Graphics and running a X11 session. One last note: I only had artifacts in Qt programmes. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443953] Black screen with GLES compositing on LLVMpipe
https://bugs.kde.org/show_bug.cgi?id=443953 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org --- Comment #3 from Andre Woebbeking --- I wonder if I've the same problem. When I login (plasma_x11) I see SUSE's light bulb forever. I've to kill KWin, disable compositing and restart KWin. Then I can work again but get many graphical artefacts. This is on Tumbleweed, Plasma 5.23 with Intel UHD Graphics. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 424790] Dolphin never stores the SAMBA domain in authentication dialog
https://bugs.kde.org/show_bug.cgi?id=424790 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 419465] Wallet failed to get opened by PAM, error code is -9
https://bugs.kde.org/show_bug.cgi?id=419465 --- Comment #9 from Andre Woebbeking --- (In reply to Albert Astals Cid from comment #8) > @Andre how does your encrypfs setup works? > > It gets un-encrypted after you put the password using pam? I think so. It was an option while installing Kubuntu. > I wonder how this may work at all with 5.18.3 since your user dir is still > encrypted and thus it can not read from it. > > Is it possible that there's a .local/share/kwalletd/kdewallet.salt in your > home "outside" the encrypted data? > > I've no idea how encrypfs works, but if it works by mounting something on > top of your existing home dir, i can envision the fact that there's a > /home/youruser/.local/share/kwalletd/kdewallet.salt "outside" your encrypted > data and then another one inside. > > Can you try that? e.g. by logging as root or as another user and checking if > the file is there? It's, also one in ~/.kde/share/apps/kwalled. > If that's the case, that's unfortunately a bug of how kwallet-pam used to > work, that file should be *inside* your encrypted data and not outside, so a > way to fix this would be copying that file from outside your encrypted data > to the inside (keep copy of the old one just in case). First I moved them away, and got error code -9 with 5.18.3 and 5.18.4 at first and second login. Then I moved them inside and 5.18.4 works as expected, first and second login :-) > Am i making sense? Well, you fixed my problem :-) Thank you very much! Not sure whether kwallet could warn about my problem otherwise this should be documented somewhere. -- You are receiving this mail because: You are watching all bug changes.
[kwallet-pam] [Bug 419465] Wallet failed to get opened by PAM, error code is -9
https://bugs.kde.org/show_bug.cgi?id=419465 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org --- Comment #7 from Andre Woebbeking --- I've this problem after updating Kubuntu 18.04 to 20.04. I also get error code -9. My home folder is encrypted with encrypfs and libpam-wallet* is version 5.18.4. After reading this I also downgraded libpam-wallet* to 5.18.3 (from eoan updates) and it works. But only when I login the first time after booting. When I logout and relogin I get error code -9 again. So I tried 5.18.4 again but that seems to be broken first and second login (I rebooted after upgrading). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 408897] crash on start
https://bugs.kde.org/show_bug.cgi?id=408897 Andre Woebbeking changed: What|Removed |Added CC||woebbek...@kde.org --- Comment #2 from Andre Woebbeking --- I've have the same crash for some weeks, also on Tumbleweed. It happens when I login to Plasma or when I restart akonadiserver. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 408871] New: False positive with -Wclazy-qstring-left
https://bugs.kde.org/show_bug.cgi?id=408871 Bug ID: 408871 Summary: False positive with -Wclazy-qstring-left Product: clazy Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: woebbek...@kde.org CC: smart...@kde.org Target Milestone: --- Hi, the following code QString text; QStringList list; list.append(text.left(1)); gives me "warning: Use QString::at(0) instead of QString::left(1) to avoid temporary allocations". But append() needs a QString so there is no way to avoid the temporary. I'm using clazy 1.5. Cheers, André -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 400308] New: Please add a test to validate old style connects
https://bugs.kde.org/show_bug.cgi?id=400308 Bug ID: 400308 Summary: Please add a test to validate old style connects Product: clazy Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: woebbek...@kde.org CC: smart...@kde.org Target Milestone: --- As we only have runtime checks for old style connects it would be nice to get errors already at compile time: 1) does the signal text match the method text 2) test whether signal and slot are members 3) test whether signal and slot are really signals and slots I think it's necessary to separate 2) and 3) to make 3) configurable to avoid false positives when compiling with icecream (preprocessed file). Thanks in advance! Cheers, André -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370969] Desktop pager missing under Wayland
https://bugs.kde.org/show_bug.cgi?id=370969 Andre Woebbeking <woebbek...@kde.org> changed: What|Removed |Added Resolution|--- |INVALID Status|REOPENED|RESOLVED --- Comment #3 from Andre Woebbeking <woebbek...@kde.org> --- OK, I just found https://community.kde.org/Plasma/Wayland_Showstoppers#Plasma . -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370969] Desktop pager missing under Wayland
https://bugs.kde.org/show_bug.cgi?id=370969 Andre Woebbeking <woebbek...@kde.org> changed: What|Removed |Added Resolution|INVALID |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED CC||woebbek...@kde.org --- Comment #2 from Andre Woebbeking <woebbek...@kde.org> --- I just tried uptodate tumbleweed (Plasma 5.11.4, Qt 5.9.3) and had no (visible) pager. If I unlock the panel and presss the panel's menu button the pager becomes visible, but only showing one desktop instead of n. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 362281] Kontact and kmail share New mail shortcut
https://bugs.kde.org/show_bug.cgi?id=362281 --- Comment #3 from Andre Woebbeking <woebbek...@kde.org> --- Daniel you made my day :-) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380904] Increase the word wrap column limit
https://bugs.kde.org/show_bug.cgi?id=380904 --- Comment #2 from Andre Woebbeking <woebbek...@kde.org> --- Well, it's from 1999 (and says "SHOULD be shorter than 80 characters." or "any paragraph longer than 79 characters in total length COULD be wrapped") and even 1999 people had more than 80-column screens. I'd be also fine with a warning like "Guy, this is not standard, it's your own risk" ;-) You probably know more mail readers than me. If you really think that nowadays it's still a problem to increase the limit I'll cancel this wish. The only alternative would be to use HTML mails to work around this limitation but I try to avoid them. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 380904] New: Increase the word wrap column limit
https://bugs.kde.org/show_bug.cgi?id=380904 Bug ID: 380904 Summary: Increase the word wrap column limit Product: kmail2 Version: 5.5.1 Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: composer Assignee: kdepim-b...@kde.org Reporter: woebbek...@kde.org Target Milestone: --- Hi, today the limit is 78. This is probably a good default (as it's standard?). But why I'm not allowed to enter higher values? VT100 terminals with 80 chars per row were yesterday, today we've displays with up to 8K. Cheers, André -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 374870] new-check: warn about broken QLatin1String
https://bugs.kde.org/show_bug.cgi?id=374870 --- Comment #2 from Andre Woebbeking <woebbek...@kde.org> --- Well, if you can distinguish non-latin1 from non-ascii. But given that most sources should be in UTF-8 nowadays I'm fine with non-ascii. -- You are receiving this mail because: You are watching all bug changes.
[clazy] [Bug 374870] New: new-check: warn about broken QLatin1String
https://bugs.kde.org/show_bug.cgi?id=374870 Bug ID: 374870 Summary: new-check: warn about broken QLatin1String Product: clazy Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: woebbek...@kde.org CC: smart...@kde.org Target Milestone: --- Hi, please add warning for QLatin1String used with non ASCII text. Thanks in advance! Cheers, André -- You are receiving this mail because: You are watching all bug changes.
