[libkgapi] [Bug 439285] Bad request, Google replied "Contacts API is being deprecated"
https://bugs.kde.org/show_bug.cgi?id=439285 --- Comment #41 from themroc --- After upgrading to 22.04 Google Calendar Sync works again. Contacts are still not synced. -- You are receiving this mail because: You are watching all bug changes.
[kaddressbook] [Bug 443464] New: Kadressbuch does not show any more contacts from google groupware
https://bugs.kde.org/show_bug.cgi?id=443464 Bug ID: 443464 Summary: Kadressbuch does not show any more contacts from google groupware Product: kaddressbook Version: 5.18.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: rauchwe...@gmail.com CC: to...@kde.org Target Milestone: --- After upgrading to Kubuntu 21.10, the Google contacts were displayed once in kadressbook. After another restart, all contacts were gone. Even when you write an email, the contacts are no longer suggested by Google. The following output in akonadictl restart: org.kde.kgapi: Bad request, Google replied ' "Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration."; ' org.kde.pim.google: Got error: KGAPI2::ContactFetchJob(0x555d25884140) "Fehlerhafte Anfrage." org.kde.kgapi: Bad request, Google replied ' "Contacts API is being deprecated. Migrate to People API to retain programmatic access to Google Contacts. See https://developers.google.com/people/contacts-api-migration."; ' org.kde.pim.google: Got error: KGAPI2::ContactFetchJob(0x7f28fc02b210) "Fehlerhafte Anfrage." Operating System: Kubuntu 21.10 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.13.0-16-generic (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 475021] New: The session verification was canceled because the keys are incorrect.
https://bugs.kde.org/show_bug.cgi?id=475021 Bug ID: 475021 Summary: The session verification was canceled because the keys are incorrect. Classification: Applications Product: NeoChat Version: 23.08.1 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: rauchwe...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- SUMMARY When you try to verify Neochat as a new device using emoji verification, you always get the error: "The session verification was canceled because the keys are incorrect." Regardless of whether Neochat or the other device accepts the emojis first. STEPS TO REPRODUCE 1. start verification via emojis via Neochat or on other device 2. click accept in Neochat or on the other device OBSERVED RESULT Message: "The session verification was canceled because the keys are incorrect." No verification is possible. EXPECTED RESULT Neochat can be verified as a device using emojis SOFTWARE/OS VERSIONS Operating System: Kubuntu 23.10 KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Kernel Version: 6.5.0-5-generic (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION libquotient version 0.7.2 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 475021] The session verification was canceled because the keys are incorrect.
https://bugs.kde.org/show_bug.cgi?id=475021 themroc changed: What|Removed |Added CC||rauchwe...@gmail.com -- 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 --- Comment #33 from themroc --- Here the same: Google Groupware is gradually showing no more calendars on my computers. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408563] Provide option for day/night color theme switching
https://bugs.kde.org/show_bug.cgi?id=408563
themroc changed:
What|Removed |Added
CC||rauchwe...@gmail.com
--- Comment #17 from themroc ---
I use this bash script in the startup to automatically change Breeze Light/Dark
and the wallpaper.
It determines the sunrise and sunset for the site via the heliocron program:
#!/bin/bash
if ping -q -c 1 -W 1 8.8.8.8 >/dev/null; then
longitude=$(curl ipinfo.io | jq -c ".loc" | tr -d '"' | awk -F',' '{print
$1}')
latitude=$(curl ipinfo.io | jq -c ".loc" | tr -d '"' | awk -F',' '{print
$2}')
if [ ! -f "/home/user/.location" ]; then
echo "$longitude $latitude" > /home/user/.location
else
read -r longialt latialt < /home/user/.location
if [ 1 != $(awk -v a="$latialt" -v b="$latitude" 'BEGIN{print(a==b)}') ] ||
[ 1 != $(awk -v a="$longialt" -v b="$longitude" 'BEGIN{print(a==b)}') ]; then
cat /home/user/.location > /home/user/.locationalt
echo "$longitude $latitude" > /home/user/.location
fi
fi
elif [ -f "/home/user/.location" ]; then
read -r longitude latitude < /home/user/.location
else
longitude=
latitude=
fi
daystart=$(heliocron -l $longitude -o $latitude report | grep Sunrise | grep -o
'[0-9][0-9]:[0-9][0-9]:[0-9][0-9]')
daystop=$(heliocron -l $longitude -o $latitude report | grep Sunset | grep -o
'[0-9][0-9]:[0-9][0-9]:[0-9][0-9]')
currenttime=$(date +%H:%M:%S)
nextday=$(date --date="next day" +%F)
# thisday=$(date +%F)
if [[ "$currenttime" > "$daystart" ]] && [[ "$currenttime" < "$daystop" ]];
then
lookandfeeltool -a org.kde.breeze.desktop
plasma-apply-wallpaperimage
/home/user/Bilder/Background/Taucher1920x1080.jpg
heliocron -l $longitude -o $latitude wait -e sunset && lookandfeeltool -a
org.kde.breezedark.desktop && plasma-apply-wallpaperimage
/home/user/Bilder/Background/DarkestHour1920x1080.jpg
sleep 2m
heliocron -d $nextday -l $longitude -o $latitude wait -e sunrise &&
lookandfeeltool -a org.kde.breeze.desktop && plasma-apply-wallpaperimage
/home/user/Bilder/Background/Taucher1920x1080.jpg
else
lookandfeeltool -a org.kde.breezedark.desktop
plasma-apply-wallpaperimage
/home/user/Bilder/Background/DarkestHour1920x1080.jpg
if [[ "$currenttime" > "$daystop" ]]; then
heliocron -d $nextday -l $longitude -o $latitude wait -e sunrise &&
lookandfeeltool -a org.kde.breeze.desktop && plasma-apply-wallpaperimage
/home/user/Bilder/Background/Taucher1920x1080.jpg
sleep 2m
heliocron -l $longitude -o $latitude wait -e sunset && lookandfeeltool
-a org.kde.breezedark.desktop && plasma-apply-wallpaperimage
/home/user/Bilder/Background/DarkestHour1920x1080.jpg
else
heliocron -l $longitude -o $latitude wait -e sunrise && lookandfeeltool
-a org.kde.breeze.desktop && plasma-apply-wallpaperimage
/home/user/Bilder/Background/Taucher1920x1080.jpg
sleep 2m
heliocron -l $longitude -o $latitude wait -e sunset && lookandfeeltool
-a org.kde.breezedark.desktop && plasma-apply-wallpaperimage
/home/user/Bilder/Background/DarkestHour1920x1080.jpg
fi
fi
--
You are receiving this mail because:
You are watching all bug changes.
[kate] [Bug 493055] New: After adding an external tool, the standard tools are no longer displayed.
https://bugs.kde.org/show_bug.cgi?id=493055
Bug ID: 493055
Summary: After adding an external tool, the standard tools are
no longer displayed.
Classification: Applications
Product: kate
Version: 23.08.5
Platform: Ubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: application
Assignee: kwrite-bugs-n...@kde.org
Reporter: rauchwe...@gmail.com
Target Milestone: ---
SUMMARY
After adding an external tool in kate, the standard tools are no longer
displayed.
STEPS TO REPRODUCE
1. Configure Kate > External tools > Add tool
2. Create new tool
3. Restart Kate
OBSERVED RESULT
Only the added external tool is displayed.
EXPECTED RESULT
The added and the default external tool should be displayed
SOFTWARE/OS VERSIONS
Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-44-generic (64-bit)
Graphics Platform: X11
Processors: 4 × Unknown Type, 4 × ARM Cortex-A78C
Memory: 15.0 GiB of RAM
Graphics Processor: FD690
Product Name: Lenovo ThinkPad X13s
Manufacturer: LENOVO
Product Name: 21BX001MGE
System Version: ThinkPad X13s Gen 1
ADDITIONAL INFORMATION
My external tool, stored in ~/.config/kate/externaltools/Englisch.ini
[General]
actionName=Englisch
arguments=-t en '%{Document:Text}'
category=Tools
executable=translate
icon=text-x-gettext-translation
name=Englisch
output=AppendToCurrentDocument
reload=false
save=None
trigger=None
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 407111] New: EWS compose Emails with S/MIME signature certificates with wrong Content-Transfer-Encoding: 7Bit instead of base64
https://bugs.kde.org/show_bug.cgi?id=407111 Bug ID: 407111 Summary: EWS compose Emails with S/MIME signature certificates with wrong Content-Transfer-Encoding: 7Bit instead of base64 Product: Akonadi Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: EWS Resource Assignee: kdepim-b...@kde.org Reporter: rauchwe...@gmail.com CC: kri...@op.pl Target Milestone: --- Created attachment 119756 --> https://bugs.kde.org/attachment.cgi?id=119756&action=edit diff between local and server version of sent Email EWS compose/send Mails with S/MIME signature certificates with wrong Content-Transfer-Encoding: 7Bit instead of base64 When I send a signed e-mail with S / MIME signing certificates, the certificate will not be recognized by any other mail client, including Kmail on other machines. An invalid signature is always displayed. Outlook indicates, that the message content was changed after creating the signed mail and therefore the signature can not be verified. In addition, only on the computer from where I have sent the mail in Kmail with the EWS resource in the sent folder the signature is displayed as valid. On another computer with the same EWS resource, the sent mail in the sent folder will be displayed as invalid. This means, however, that Outlook is right and the message content was changed later when it was sent. And indeed, the message source text on both machines in the sent folder is not identical. On the computer from where I sent, will keep the original written e-mail. On the other computer, the sent e-mail is downloaded from the server. Comparing the two different e-mail source texts, there is only one relevant difference: < Content-Transfer-Encoding: 7Bit --- > Content-Transfer-Encoding: base64 The really sent version has this line: > Content-Transfer-Encoding: base64 I then came up with the idea to force kmail to switch to the "Content-Transfer-Encoding: base64" when writing the mail. By adding special characters in the message text I reached it. Then the version sent in Kmail will no longer be different from the version sent to the server. Both have "Content-Transfer-Encoding: base64". And then the signature is displayed as valid in all other mail programs and in kmail on other computers! I have test this on Kubuntu 18.10 and Kubuntu 19.04 E.g for Kubuntu 19.04: Operating System: Kubuntu 19.04 KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 Kernel Version: 5.0.0-13-generic OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 392543] New: bionic package depends on konsole-kpart, which is no longer available
https://bugs.kde.org/show_bug.cgi?id=392543 Bug ID: 392543 Summary: bionic package depends on konsole-kpart, which is no longer available Product: kile Version: 2.9.91 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: michel.lud...@kdemail.net Reporter: rauchwe...@gmail.com Target Milestone: --- Bionic Beaver (Kubuntu 18.04) package depends on konsole-kpart, which is no longer available. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 392543] bionic package depends on konsole4-kpart, which is no longer available
https://bugs.kde.org/show_bug.cgi?id=392543 themroc changed: What|Removed |Added Summary|bionic package depends on |bionic package depends on |konsole-kpart, which is no |konsole4-kpart, which is no |longer available|longer available -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 392543] bionic package depends on konsole4-kpart, which is no longer available
https://bugs.kde.org/show_bug.cgi?id=392543 --- Comment #1 from themroc --- I mean konsole4-kpart instate of konsole-kpart!! -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 385008] [wish] mouse action or shortcut or automatic move to position in source code (latex) if scolling live preview window
https://bugs.kde.org/show_bug.cgi?id=385008 --- Comment #2 from themroc --- I can confirm, that works. -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 385008] New: mouse action or shortcut or automatic move to position in source code (latex) if scolling live preview window
https://bugs.kde.org/show_bug.cgi?id=385008 Bug ID: 385008 Summary: mouse action or shortcut or automatic move to position in source code (latex) if scolling live preview window Product: kile Version: 2.9.91 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: user interface Assignee: michel.lud...@kdemail.net Reporter: rauchwe...@gmail.com Target Milestone: --- It would be an great enhancement, if it would be possible to jump to the actual position in source, if scrolling in live preview window to an other position. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 494230] New: [wayland] wlfreerdp window has wrong size if global global scaling is used
https://bugs.kde.org/show_bug.cgi?id=494230 Bug ID: 494230 Summary: [wayland] wlfreerdp window has wrong size if global global scaling is used Classification: Applications Product: krdc Version: 23.08.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: rauchwe...@gmail.com Target Milestone: --- SUMMARY The wlfreerdp window has wrong size if global global scaling is used. It does not matter whether wlfreerdp is started from kdrc or directly from the terminal. The window size is too large by exactly the global scaling factor. E.g. scaling factor 125 %: On a 1366 x 768 pixel screen, wlfreerdp must be started as follows: wlfreerdp /v: /size:1100x550 to obtain a window of approximately 1366 x 768 pixels. STEPS TO REPRODUCE 1. Start RDP Session from KRDC with e.g. actual size or 2. Start RDP Session from KRDC with any size or 3. Start wlfreerdp directly from command line with any size OBSERVED RESULT 1. wlfreerdp window is too big (the window is as much larger as the scaling factor) 2. same from terminal EXPECTED RESULT kdrc or wlfreerdp take the global scaling of the Plasma Desktop into account when entering the window size. SOFTWARE/OS VERSIONS Operating System: Kubuntu 24.10 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.6.2 Kernel Version: 6.11.0-8-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Pentium® CPU N3710 @ 1.60GHz Memory: 3.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 405 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
