[kdeconnect] [Bug 480209] New: KDE Connect Crash
https://bugs.kde.org/show_bug.cgi?id=480209 Bug ID: 480209 Summary: KDE Connect Crash Classification: Applications Product: kdeconnect Version: 23.08.4 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: con...@fdcs.co.za CC: andrew.g.r.hol...@gmail.com Target Milestone: --- Application: kdeconnectd (23.08.4) Qt Version: 5.15.12 Frameworks Version: 5.114.0 Operating System: Linux 6.5.0-14-generic x86_64 Windowing System: X11 Distribution: KDE neon 5.27 DrKonqi: 5.27.10 [KCrashBackend] -- Information about the crash: After Lattes kde framework update to 5.114.0 kde connect open and closes the hole tine tested on wayland and x11 The crash can be reproduced every time. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault [KCrash Handler] #4 0x7f4d72daf87e in Device::reloadPlugins() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #5 0x7f4d72dafaa1 in Device::pairingHandler_pairingSuccessful() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #6 0x7f4d716f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7f4d72da0519 in PairingHandler::acceptPairing() () from /lib/x86_64-linux-gnu/libkdeconnectcore.so.23 #8 0x7f4d716f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7f4d72d3a350 in KNotification::activate(unsigned int) () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #10 0x7f4d72d3cfc9 in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #11 0x7f4d716f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7f4d72d40b83 in KNotificationPlugin::actionInvoked(int, int) () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #13 0x7f4d72d4f54b in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #14 0x7f4d716f4db4 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7f4d72d59f15 in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #16 0x7f4d72d5aa03 in ?? () from /lib/x86_64-linux-gnu/libKF5Notifications.so.5 #17 0x7f4d729d5feb in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #18 0x7f4d716ea85e in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7f4d7236c783 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Widgets.so.5 #20 0x7f4d716bd30a in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7f4d716c0407 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7f4d717171a7 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #23 0x7f4d70120d3b in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #24 0x7f4d70176258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f4d7011e3e3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f4d717167f8 in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #27 0x7f4d716bbc2b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #28 0x7f4d716c41d4 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x562f7abac001 in ?? () #30 0x7f4d70c29d90 in __libc_start_call_main (main=main@entry=0x562f7ababbd0, argc=argc@entry=1, argv=argv@entry=0x7fffe3cd4d78) at ../sysdeps/nptl/libc_start_call_main.h:58 #31 0x7f4d70c29e40 in __libc_start_main_impl (main=0x562f7ababbd0, argc=1, argv=0x7fffe3cd4d78, init=, fini=, rtld_fini=, stack_end=0x7fffe3cd4d68) at ../csu/libc-start.c:392 #32 0x562f7abac285 in ?? () [Inferior 1 (process 8525) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] New: neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 Bug ID: 447337 Summary: neo2 layout stuck on keyboard layer 4 on wayland Product: systemsettings Version: 5.23.4 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keyboard Assignee: plasma-b...@kde.org Reporter: conrad_bugtrac...@linuxfreaks.info CC: butir...@gmail.com Target Milestone: --- SUMMARY On plasma/wayland when configuring the German keyboard layout Neo2 the layout is permanently stuck on layer 4 and therefor completely unusable. (the layer maps most numpad functions to the main keyboard section) STEPS TO REPRODUCE 1. set layout "German (Neo 2)" in Keyboard System Settings 2. try to type anything OBSERVED RESULT Layout permanently stuck on layer 4. Need to switch to a standard layout. SOFTWARE/OS VERSIONS System: Gentoo Linux (linux 5.10.76 64bit x86) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 Graphics Platform: Wayland ADDITIONAL INFORMATION I have had problems with Neo2 on Plasma/Wayland for years but things fully broke after updating from plasma 5.22.5 to 5.23.4. In previous versions the layout would be stuck on layer 4 on login but reset after changing any setting in the keyboard configuration menu and pressing the "apply" button. This workaround does no longer work in 5.23.4 and the layout is now permanently stuck on layer 4. On another system with Plasma/X11 I have no issues. I have restored the keyboard default settings but that did not cause any change in behavior. As a side note, when newly configuring keyboard layouts now, the Neo 2 layout shows "Map: de" (same as German standard layout) instead of "Map: neo". Don't know if this is relevant. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 Conrad changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED --- Comment #2 from Conrad --- This bug is a duplicate of 432436. It is not about layout changing at all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #3 from Conrad --- Unfortunate typo: This bug is *not* a duplicate of 432436. It is not about layout changing at all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #5 from Conrad --- As far as I can tell there is no difference no matter what settings I set or how many layouts I configure. ~/.config/kxkbrc [$Version] update_info=kxkb_variants.upd:split-variants [Layout] DisplayNames= LayoutList=de LayoutLoopCount=-1 Model=pc105 Options=grp:alt_space_toggle ResetOldOptions=true ShowFlag=false ShowLabel=true ShowLayoutIndicator=true ShowSingle=true SwitchMode=Global Use=true VariantList=neo -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #7 from Conrad --- I have tried with "XKB_DEFAULT_LAYOUT=de XKB_DEFAULT_VARIANT=neo sway" and this worked as intended. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #9 from Conrad --- No, sway is its own wayland compositor. "etc." sounded like that was what you were asking for. Any way to test this without having to install the whole gnome suite on my system? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #11 from Conrad --- Thanks for your help so far! I tested with a newly created user just now and the problem does not occur there. Any idea where I could start looking to narrow down the cause? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #12 from Conrad --- Figured out the problem. It was caused by ~/.config/kcminputrc and more precisely by these lines: [Keyboard] KeyRepeat=repeat NumLock=0 RepeatDelay=600 RepeatRate=25 It must have been created by some older version of kde/plasma. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #14 from Conrad --- The culprit is "NumLock=0". Removing the line or changing it to "NumLock=1" resolves the problem. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #16 from Conrad --- I can't tell. My numlock is always off and I can't enable it. Probably some other problem with legacy config files. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #18 from Conrad --- turn on sets it to 0, turn off sets it to 1. The problem indeed only appears when numlock is enabled. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #20 from Conrad --- Yes, verified multiple times. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #22 from Conrad --- They do. They are written to the file like this as soon as I click the "apply" button in the system settings. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #24 from Conrad --- Yes, that could be what is happening here. It does however not explain why neo2 layout would become unusable if numlock is on. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #26 from Conrad --- I can confirm your suspicions. sway shows the same broken behavior as soon as numlock is turned on. So very likely an upstream problem. Regarding the 0/1 status in the config, this has been for years., so probably working as intended. I found this thread from 2009 that references the same settings: https://forums.gentoo.org/viewtopic-t-805441-start-0.html -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #28 from Conrad --- Thank you for your help so far! Upstream bug has been reported here: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/-/issues/300 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 447337] neo2 layout stuck on keyboard layer 4 on wayland
https://bugs.kde.org/show_bug.cgi?id=447337 --- Comment #30 from Conrad --- sure, sounds good -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 497041] Very high memory usage while using external monitor connected directly to the laptop
https://bugs.kde.org/show_bug.cgi?id=497041 Conrad changed: What|Removed |Added CC||ctestagros...@gmail.com --- Comment #1 from Conrad --- I am also seeing the same thing on a Lenovo Legion 7i with an Nvidia RTX 3060 running Archlinux with KDE Plasma. htop shows 76% memory usage from kwin_wayland after a zoom call when plugged into an external monitor. Probably the third time this has happened and is only resolved after a reboot. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414185] New: PREVIOUS TABS NOT OPENED AUTOMATICALLY UPON START-UP
https://bugs.kde.org/show_bug.cgi?id=414185 Bug ID: 414185 Summary: PREVIOUS TABS NOT OPENED AUTOMATICALLY UPON START-UP Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: alan.con...@t-online.de Target Milestone: --- SUMMARY After starting Okular none of the previous tabs are opened automatically. They have to be opened again manually. It would be a great advantage if it were possible to set the preferences so that the previous tabs are saved upon shut-down and then re-opened automatically upon the next start-up. STEPS TO REPRODUCE 1. Using a Raspberry 4 and Raspbian, open Okular, open a number of PDF files in different tabs. 2. Shut-down Okular. 3. Start Okular, none of the previous tabs are opened automatically. OBSERVED RESULT None of the previous tabs are opened automatically. EXPECTED RESULT Previous tabs should be re-opened automatically upon start-up. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Raspbian OS. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 330950] Setup wizard: Warning "Password is empty" stays visible after switching back from "Classic, blowfish encrypted file" to "Use GPG encryption"
https://bugs.kde.org/show_bug.cgi?id=330950 --- Comment #3 from Claus Conrad --- Hi Andrew, I can no longer reproduce this in version 18.08.3. Please close it. -- You are receiving this mail because: You are watching all bug changes.
