[Akonadi] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 --- Comment #39 from a.key --- (In reply to B. Scheichl from comment #36) > Created attachment 146964 [details] > attachment-10630-0.html > > Same experience - several updates over the last weeks (Tumbleweed), still > not working. Very annoying, as it had worked until January. > > B. Scheichl (TU Wien). From my mobile. > > Von: bugzilla_nore...@kde.org > Gesendet: Sonntag, 20. Februar 2022 07:50 > An: Scheichl, Bernhard > Betreff: [Akonadi] [Bug 449024] Unable to fetch google calendar events > > https://bugs.kde.org/show_bug.cgi?id=449024 > > --- Comment #35 from siauder...@hotmail.com --- > (In reply to siauderman from comment #33) > > (In reply to a.key from comment #32) > > > The patch does work on Fedora 35 KDE. > > > > Hi, does anyone know how to apply the patch on Kubuntu? Would like to use > > KDE PIM Events plugin. Thanks. > > I just did a plasma update today and it still doesn't work. Version 5.19.2 > (21.12.2). > > -- > You are receiving this mail because: > You are on the CC list for the bug. Yeah, I meant that a package with the patch applied does fix this on Fedora. The version of kdepim-runtime from marcdeop/plasma copr is unpatched hence I had to apply the patch manually and recompile. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 483334] Different font rendering after plasma 6 update
https://bugs.kde.org/show_bug.cgi?id=483334 a.key changed: What|Removed |Added CC||a@moronet.pl --- Comment #7 from a.key --- Created attachment 168866 --> https://bugs.kde.org/attachment.cgi?id=168866&action=edit blurry Monospace konsole font rendering Blurry Monospace font rendering in plasma 6.0.3 (konsole) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 483334] Different font rendering after plasma 6 update
https://bugs.kde.org/show_bug.cgi?id=483334 a.key changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|LATER |--- Assignee|konsole-de...@kde.org |a@moronet.pl Ever confirmed|0 |1 --- Comment #8 from a.key --- Created attachment 168868 --> https://bugs.kde.org/attachment.cgi?id=168868&action=edit Bolded items in lists have too wide spacing There's also a weird widened spacing in bolded items in lists. Here a list of konsole profiles with the default one bolded which is too thick. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 483334] Different font rendering after plasma 6 update
https://bugs.kde.org/show_bug.cgi?id=483334 --- Comment #9 from a.key --- Created attachment 168869 --> https://bugs.kde.org/attachment.cgi?id=168869&action=edit kontact email folder list with bolded items too spaced out Here in kontact the email folder list with items bolded show that the spacing is too wide too. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 483334] Different font rendering after plasma 6 update
https://bugs.kde.org/show_bug.cgi?id=483334 --- Comment #10 from a.key --- Created attachment 168870 --> https://bugs.kde.org/attachment.cgi?id=168870&action=edit message list in kontact shows new emails (bolded) with too wide spacing Finally the worst of all... I have my new/unread emails set as bold (very old school/thunderbird behaviour) in this example shows my spam emails and the ones that are set as unread are shown here as too spaced out. This was not like it in the last plasma 5.x.x. It looked a lot better. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483334] Different font rendering after plasma 6 update
https://bugs.kde.org/show_bug.cgi?id=483334 a.key changed: What|Removed |Added Product|konsole |kde Component|font|general Version|24.02.0 |unspecified -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 483334] Different font rendering after plasma 6 update
https://bugs.kde.org/show_bug.cgi?id=483334 --- Comment #11 from a.key --- It's actually hard to say what it is... it seems like it's too spaced out but also that bold is kind of "too bold". -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 444411] New: Akonadi resource crashed at system startup
https://bugs.kde.org/show_bug.cgi?id=11 Bug ID: 11 Summary: Akonadi resource crashed at system startup Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: a@moronet.pl Target Milestone: --- Application: akonadi_google_resource (5.16.2 (20.12.2)) Qt Version: 5.15.2 Frameworks Version: 5.85.0 Operating System: Linux 5.14.13-200.fc34.x86_64 x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: "Fedora release 34 (Thirty Four)" -- Information about the crash: - What I was doing when the application crashed: Waiting for the desktop to load after reboot. Bunch of these: Oct 26 08:24:48 darkstar akonadiserver[4746]: org.kde.pim.akonadiserver: Handler exception when handling command FetchItems on connection plasmashell-297544688 (0x558b5d58f830) : Operations based on remote identifiers require a resource or collection context Oct 26 08:24:48 darkstar akonadi_google_resource[4888]: ASSERT failure in Akonadi::ResourceBase::retrieveItem(): "The base implementation of retrieveItem() must never be reached. You must implement either retrieveItem() or retrieveItems(Akonadi::Item::List, QSet) overload to handle item retrieval requests.", file /builddir/build/BUILD/akonadi-20.1 2.2/src/agentbase/resourcebase.cpp, line 1462 ...and eventually: Oct 26 08:24:48 darkstar korgac[4888]: KCrash: Application 'akonadi_google_resource' crashing... The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Google Groupware (a.key1...@gmail.com) (akonadi_google_resource), signal: Aborted [KCrash Handler] #4 0x7ffac8aa12a2 in raise () at /lib64/libc.so.6 #5 0x7ffac8a8a8a4 in abort () at /lib64/libc.so.6 #6 0x7ffac8f2045b in qt_message_output(QtMsgType, QMessageLogContext const&, QString const&) [clone .cold] () at /lib64/libQt5Core.so.5 #7 0x7ffac8f1f8be in qgetenv(char const*) [clone .cold] () at /lib64/libQt5Core.so.5 #8 0x7ffacaa6c1ee in QMapNode::copy(QMapData*) const [clone .cold] () at /lib64/libKF5AkonadiAgentBase.so.5 #9 0x7ffacaa86082 in Akonadi::ResourceBasePrivate::slotPrepareItemRetrievalResult(KJob*) () at /lib64/libKF5AkonadiAgentBase.so.5 #10 0x7ffac91493a9 in void doActivate(QObject*, int, void**) () at /lib64/libQt5Core.so.5 #11 0x7ffaca3eacf0 in KJob::result(KJob*, KJob::QPrivateSignal) () at /lib64/libKF5CoreAddons.so.5 #12 0x7ffaca3ef5cb in KJob::finishJob(bool) () at /lib64/libKF5CoreAddons.so.5 #13 0x7ffac913ff09 in QObject::event(QEvent*) () at /lib64/libQt5Core.so.5 #14 0x7ffac9ce0443 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /lib64/libQt5Widgets.so.5 #15 0x7ffac9115798 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /lib64/libQt5Core.so.5 #16 0x7ffac9118d06 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /lib64/libQt5Core.so.5 #17 0x7ffac91670d7 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /lib64/libQt5Core.so.5 #18 0x7ffac72de4cf in g_main_context_dispatch () at /lib64/libglib-2.0.so.0 #19 0x7ffac73324f8 in g_main_context_iterate.constprop () at /lib64/libglib-2.0.so.0 #20 0x7ffac72dbc03 in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #21 0x7ffac9166b78 in QEventDispatcherGlib::processEvents(QFlags) () at /lib64/libQt5Core.so.5 #22 0x7ffac91141a2 in QEventLoop::exec(QFlags) () at /lib64/libQt5Core.so.5 #23 0x7ffac911c6e4 in QCoreApplication::exec() () at /lib64/libQt5Core.so.5 #24 0x556da88dc1b7 in int Akonadi::ResourceBase::init(int, char**) () #25 0x7ffac8a8bb75 in __libc_start_main () at /lib64/libc.so.6 #26 0x556da88d293e in _start () [Inferior 1 (process 4888) detached] Possible duplicates by query: bug 444002, bug 443954, bug 443935, bug 443784, bug 443771. Reported using DrKonqi This report was filed against 'kde' because the product 'akonadi_google_resource' could not be located in Bugzilla. Add it to drkonqi's mappings file! -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 444411] Akonadi resource crashed at system startup
https://bugs.kde.org/show_bug.cgi?id=11 --- Comment #1 from a.key --- Then I had another crash for the same resource with this message in journal: Oct 26 08:37:13 darkstar akonadiserver[7971]: org.kde.pim.akonadiserver.search: Executing search "kontact-97546946-SearchSession" Oct 26 08:37:13 darkstar akonadiserver[7971]: org.kde.pim.akonadiserver.search: Search "kontact-97546946-SearchSession" done (without remote search) Oct 26 08:37:13 darkstar akonadi_google_resource[8013]: ASSERT failure in Akonadi::ResourceBase::retrieveItem(): "The base implementation of retrieveItem() must never be reached. You must implement either retrieveItem() or retrieveItems(Akonadi::Item::List, QSet) overload to handle item retrieval requests.", file /builddir/build/BUILD/akonadi-20.12.2/src/agentbase/resourcebase.cpp, line 1462 Oct 26 08:37:13 darkstar plasmashell[8013]: KCrash: Application 'akonadi_google_resource' crashing... -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 420280] Can't add Google account: authentication process gets stuck
https://bugs.kde.org/show_bug.cgi?id=420280 a.key changed: What|Removed |Added CC||a@moronet.pl --- Comment #74 from a.key --- I can confirm that the signon-ui from hazel-bunny:ports fixes the issue of not getting to the password prompt after entering the email address for gmail but as @Bernie Innocenti mentioned it still wont let you complete the setup if 2FA is enabled on the account. It just hangs and waits on the waiting to use your pass key step but the prompt or option to choose what pass key or what other 2FA method to use is never displayed. A temp workaround is to disable 2FA for the time being of setting up the account in KDE and re-enabling straight after! -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 a.key changed: What|Removed |Added CC||a@moronet.pl --- Comment #11 from a.key --- Same problem here. I have a ThinkPad X1 Carbon connected to a Thundrebolt 3 dock to which there are 2 Apple Cinema HD screens connected: Configuring the screens in extended mode sets up the external monitors with incorrect resolutions and everything looks really bad. You cannot click on anything because the display is set to incorrect resolution but the the Plasma thinks it's correct. Attached screenshots from kscreen and drm_info when both external monitors are enabled but with incorrect resolution. $ kscreen-doctor -o Output: 1 unknown eDP-1-unknown enabled connected Panel Modes: 0:1920x1080@48 1:1920x1080@60*! Geometry: 0,0 1920x1080 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic Output: 2 Apple Computer Inc Cinema HD /CY73902UXMP enabled connected Unknown Modes: 0:1280x800@60 1:2560x1600@60*! Geometry: 1920,0 2560x1600 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic Output: 3 Apple Computer Inc Cinema HD /CY7231DVXMP enabled connected primary Unknown Modes: 0:1280x800@60 1:2560x1600@60*! Geometry: 4480,0 2560x1600 Scale: 1 Rotation: 1 Overscan: 0 Vrr: incapable RgbRange: Automatic primary -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 --- Comment #12 from a.key --- Created attachment 145354 --> https://bugs.kde.org/attachment.cgi?id=145354&action=edit xrandr output with external monitors enabled xrandr "thinks" the resolution is set to 2560x1600 but in reality it's 1280x800. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 --- Comment #13 from a.key --- Created attachment 145355 --> https://bugs.kde.org/attachment.cgi?id=145355&action=edit drm_info output with external monitors enabled -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 --- Comment #14 from a.key --- Created attachment 145356 --> https://bugs.kde.org/attachment.cgi?id=145356&action=edit kscreen screenshot -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 445253] Unable to set maximum resolution on HiDPI after suspend, goes back to lower resolution (Wayland, after suspend, persists after several reboots)
https://bugs.kde.org/show_bug.cgi?id=445253 --- Comment #15 from a.key --- It maybe useful to know that: The problem of incorrect resolution doesn't appear when: Laptop is rebooted without the docking station plugged in. In this situation I reboot the laptop, go through the SDDM login and get straight to Plasma Wayland session. Then I plug my docking station and the monitors light up with correct resolution. Please note that plasma completely crashes when I then unplug the docking station and plug it back in. It simply goes black, crashes and goes back to SDDM. It may also be useful that my SDDM as well as TTY get incorrect resolution as well. This means that if I boot the laptop (Fedora 35) to runlevel 3 with not X, the laptop built in display will be in it's correct resolution but the two external ones will be at the incorrect ones. When changing runlevel to X where sddm would get started, SDDM also shows incorrect resolution for external displays and depending how well the SDDM theme can handle multiple screen resolutions the login screen can look better or worse. This is of lesser importance. Logging in to Plasma X11 session is working OK. All screens get their correct resolution but logging into Plasma Wayland is bad as described previously. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 449024] Unable to fetch google calendar events
https://bugs.kde.org/show_bug.cgi?id=449024 a.key changed: What|Removed |Added CC||a@moronet.pl --- Comment #32 from a.key --- The patch does work on Fedora 35 KDE. -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 378436] Instance create job emits result too early
https://bugs.kde.org/show_bug.cgi?id=378436 a.key changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED CC||a@moronet.pl Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- --- Comment #3 from a.key --- Yes, Just happened to me when I attempted to add another account from g-suite (custom domain). plasma version: 5.19.5 framework version: 5.70.0 qt version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431200] New: Unable to set double click for right click in touchpad settings
https://bugs.kde.org/show_bug.cgi?id=431200 Bug ID: 431200 Summary: Unable to set double click for right click in touchpad settings Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_touchpad Assignee: plasma-b...@kde.org Reporter: a@moronet.pl Target Milestone: --- Created attachment 134597 --> https://bugs.kde.org/attachment.cgi?id=134597&action=edit kcm_touchpad X11 KCM Touchpad settings don't allow setting up "clickfinger" Click method also known as "Press anywhere with two fingers" option for right click. Tested this on 2 Thinkpads: T450s and ThinkPad X1 Carbon Gen 8 Under X the option is displayed but is disabled and cannot be enabled. Under wayland this option is completely missing. Under wayland libinput list-devices properly shows the properties are available: Device: Synaptics TM3053-004 Kernel: /dev/input/event17 Group:8 Seat: seat0, default Size: 97x53mm Capabilities: pointer gesture Tap-to-click: disabled Tap-and-drag: enabled Tap drag lock:disabled Left-handed: disabled Nat.scrolling:disabled Middle emulation: disabled Calibration: n/a Scroll methods: *two-finger edge Click methods:*button-areas clickfinger Disable-w-typing: enabled Accel profiles: flat *adaptive Rotation: n/a It's possible to manually enable the method via dbus: qdbus org.kde.KWin /org/kde/KWin/InputDevice/event17 org.kde.KWin.InputDevice.clickMethodClickfinger true STEPS TO REPRODUCE 1. Open System settings 2. Click on Input Devices category 3. Click on Touchpad Input Devices OBSERVED RESULT Depending if under X11 or wayland the option is disabled or completely missing EXPECTED RESULT Option "Right click" is available and possible to choose via a radio option type with the following choices available: - Press bottom-right corner - Press anywhere with two fingers SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 33 (available in About System) KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 431200] Unable to set double click for right click in touchpad settings
https://bugs.kde.org/show_bug.cgi?id=431200 --- Comment #1 from a.key --- Created attachment 134598 --> https://bugs.kde.org/attachment.cgi?id=134598&action=edit kcm_touchpad wayland -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 379285] Akonadi IMAP doesn't refresh connections after sleep or network change
https://bugs.kde.org/show_bug.cgi?id=379285 a.key changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #3 from a.key --- This has been resolved long time ago. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 399704] kate crashes when printing to a google cloud printer
https://bugs.kde.org/show_bug.cgi?id=399704 a.key changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #2 from a.key --- This was environmental caused. Closing this ticket as it's not an issue anymore. -- You are receiving this mail because: You are watching all bug changes.
