[krdc] [Bug 488656] New: KRDC going fullscreen will always place the application on the leftmost screen
https://bugs.kde.org/show_bug.cgi?id=488656 Bug ID: 488656 Summary: KRDC going fullscreen will always place the application on the leftmost screen Classification: Applications Product: krdc Version: 24.05.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: ker...@ag.de1.cc Target Milestone: --- SUMMARY KRDC going fullscreen will always place the application on the leftmost screen STEPS TO REPRODUCE Prequisite: Have multiple screens. 1. Start KRDC and have the window on a different screen that the leftmost one. 2. Connect to an RDP client or switch active windowed connection to fullscreen OBSERVED RESULT The RDP window goes fullscreen on the leftmost screen. EXPECTED RESULT The RDP window goes fullscreen on the same screen the window was. (possible Alternative: Screen that best matches the Resolution configured in KRDC's client settings) SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Graphics Platform: Wayland ADDITIONAL INFORMATION Tested with krdc-window on central screen (1920×1200), which is also set up as primary. Client settings also specify a resolution of 1920×1200. Left screen is 1024×1280. -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 488655] New: Tab key not working in RDP session
https://bugs.kde.org/show_bug.cgi?id=488655 Bug ID: 488655 Summary: Tab key not working in RDP session Classification: Applications Product: krdc Version: 24.05.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: ker...@ag.de1.cc Target Milestone: --- SUMMARY Pressing the Tab key in a RDP session does not register in the client. Furthermore, after pressing it no other keyboard input works until I click into the window. STEPS TO REPRODUCE 1. Connect to a remote machine via RDP 2. Open some Application that should react to Tab (e.g. Notepad) 3. Press Tab key OBSERVED RESULT No Tab inserted; And no keyboard input after this. EXPECTED RESULT Tab inserted. SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Graphics Platform: Wayland ADDITIONAL INFORMATION * Tried this on 2 Clients with same result. * Not happening with Remmina. * My first idea was that Tab changes Focus to some invisible UI Element, but Shift-Tab / repeated presses of Tab do not fix the situation. * This beeing RDP-specific is only a guess - I don't have any clients available to test other protocols. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 482499] KWalletmanager not quitting correctly (crash/hang)
https://bugs.kde.org/show_bug.cgi?id=482499 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc Product|kde |kwalletmanager Assignee|unassigned-b...@kde.org |va...@kde.org Component|general |general Version|unspecified |24.02.0 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 482499] New: KWalletmanager not quitting correctly (crash/hang)
https://bugs.kde.org/show_bug.cgi?id=482499 Bug ID: 482499 Summary: KWalletmanager not quitting correctly (crash/hang) Classification: I don't know Product: kde Version: unspecified Platform: Neon OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: ker...@ag.de1.cc Target Milestone: --- Application: kwalletmanager5 (24.02.0) Qt Version: 6.6.2 Frameworks Version: 6.0.0 Operating System: Linux 6.5.0-21-generic x86_64 Windowing System: Wayland Distribution: KDE neon 6.0 DrKonqi: 6.0.0 [KCrashBackend] -- Information about the crash: Whenever I close kwalletmanager (File -> Quit or Window close does not seem to matter), one of 2 things happens (chosen randomly) 1. it crashes (see backtrace) 2. no crash, window is gone, but the process continues running and can only be ended through the System Monitor / killall / similiar program. This is reproducable by simply starting, then quitting the application. The only special configuration I can think of is that I have 3 wallets configured. The crash can be reproduced sometimes. -- Backtrace: Application: Wallet Manager (kwalletmanager5), signal: Aborted [KCrash Handler] #4 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140596258077376) at ./nptl/pthread_kill.c:44 #5 __pthread_kill_internal (signo=6, threadid=140596258077376) at ./nptl/pthread_kill.c:78 #6 __GI___pthread_kill (threadid=140596258077376, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #7 0x7fdf21d48476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #8 0x7fdf21d2e7f3 in __GI_abort () at ./stdlib/abort.c:79 #9 0x7fdf21d8f676 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fdf21ee1b77 "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #10 0x7fdf21da6cfc in malloc_printerr (str=str@entry=0x7fdf21ee4210 "munmap_chunk(): invalid pointer") at ./malloc/malloc.c:5664 #11 0x7fdf21da6fdc in munmap_chunk (p=) at ./malloc/malloc.c:3060 #12 0x7fdf21dab49a in __GI___libc_free (mem=) at ./malloc/malloc.c:3381 #13 0x7fdf22524353 in QObject::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #14 0x7fdf241b665d in KXmlGuiWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libKF6XmlGui.so.6 #15 0x7fdf235e00eb in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt6Widgets.so.6 #16 0x7fdf225bee18 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #17 0x7fdf225bf530 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #18 0x7fdf225c2c99 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt6Core.so.6 #19 0x55abe460ca4c in ?? () #20 0x7fdf21d2fd90 in __libc_start_call_main (main=main@entry=0x55abe460bdc0, argc=argc@entry=1, argv=argv@entry=0x7ffd51263208) at ../sysdeps/nptl/libc_start_call_main.h:58 #21 0x7fdf21d2fe40 in __libc_start_main_impl (main=0x55abe460bdc0, argc=1, argv=0x7ffd51263208, init=, fini=, rtld_fini=, stack_end=0x7ffd512631f8) at ../csu/libc-start.c:392 #22 0x55abe460cb45 in ?? () [Inferior 1 (process 10293) detached] Reported using DrKonqi This report was filed against 'kde' because the product 'kwalletmanager5' 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.
[systemsettings] [Bug 479193] With Qt 6.7, user is prompted to apply changes without changing any settings
https://bugs.kde.org/show_bug.cgi?id=479193 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #7 from Arek Guzinski --- Happening to me on current neon (plasma/kf 6.0.0, qt 6.6.2, wayland) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 475128] akregator / kmail : can't restore / reduce to tray
https://bugs.kde.org/show_bug.cgi?id=475128 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #1 from Arek Guzinski --- Same thing here on current neon -- but only with akregator. Works fine in kmail. Maybe it's fixed there and that fix can be applied to akregator? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 474246] Yakuake monitor assignment is not stable
https://bugs.kde.org/show_bug.cgi?id=474246 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #1 from Arek Guzinski --- It might not be the exactly same bug as the conditions are different, but the effect is similiar enough: I never had that problem on plasma 5 + X11. It started after the switch to wayland and plasma 6. I have 3 monitors and their order seems to be randomized in yakuake after each system restart (or possibly plasma login?). The left and right monitor are the same model, but I once had yakuake wrongly appear on the middle one, too. I checked the priority order in display settings. It currently matches the order in yakuake, but did not do this last session. (Display settings remain stable) So in effect I have yakuake starting on a random monitor each session. In addition, I used to change the current monitor via shortcut (move window to screen) in X11. This only partially works now: moving yakuake to another screen will result in a gap between the top window border and the top of the screen (middle monitor starts lower than the others, so than might have something to do with it - but also happens when moving from right to left). Also that change is not remembered - when I close and reopen yakuake, it's on the screen set inside the application. Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15,5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482050] kile did not start
https://bugs.kde.org/show_bug.cgi?id=482050 --- Comment #3 from Arek Guzinski --- Sorry, I was maybe a bit unclear about that idea... What I mean is that the developers might change the code, so that the okular-part is not necessary to start kile, so that we might use it until kile is properly ported to kf6. I also tried if I could quickly do this myself by removing all okular-related stuff from the source and fix a few things until it compiles again... but as expected, it wasn't that easy :/. Settings can be changed without the UI by editing ~/.config/kilerc, but that is not enough to make kile start again (otherwise I would not even have noticed this problem). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482297] New: Mouse marks sometimes unintentionally drawn when moving windows via shortcut
https://bugs.kde.org/show_bug.cgi?id=482297 Bug ID: 482297 Summary: Mouse marks sometimes unintentionally drawn when moving windows via shortcut Classification: Plasma Product: kwin Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: effects-various Assignee: kwin-bugs-n...@kde.org Reporter: ker...@ag.de1.cc Target Milestone: --- SUMMARY Occasionally, when I move a window to a different screen or virtual desktop using a keyboard shortcut, a red line (mouse mark) is drawn from a position where the mouse cursor recently rested to it's current position. The shortcuts I use have the same modifiers (Meta+Shift) that are configured for drawing a line. After changing the modifiers for mouse marks, no lines are drawn. STEPS TO REPRODUCE 1. Activate mouse marks and set free draw modifiers to Meta + Shift 2. Set shortcut for "Window to Next Desktop" to Meta + Shift + V (or other key) 3. Focus any window 4. Move mouse somewhere 5. Stop moving mouse 6. Press the shortcut set in 2 7. If no mouse mark created yet, repeat from step 4 OBSERVED RESULT At some point a Line is drawn EXPECTED RESULT No line drawn SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15,5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482225] Task switcher ignores windows on 1 screen (of 3)
https://bugs.kde.org/show_bug.cgi?id=482225 --- Comment #4 from Arek Guzinski --- Oh.. you're right, disabling Screens fixed it for me. Thanks :) But now that I'm reading this correctly and know what it does, I still see a problem here: "All other screens" means "All screens except the one with the mouse cursor on it". If I remember correctly, there was a decision to define the current screen like this, which might make sense in many situations... In this case though, because I'm navigating windows by keyboard, I would expect the current screen to be the one with the currently focussed window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482225] Task switcher ignores windows on 1 screen (of 3)
https://bugs.kde.org/show_bug.cgi?id=482225 --- Comment #2 from Arek Guzinski --- forgot this: SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15,5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482225] Task switcher ignores windows on 1 screen (of 3)
https://bugs.kde.org/show_bug.cgi?id=482225 --- Comment #1 from Arek Guzinski --- Created attachment 166301 --> https://bugs.kde.org/attachment.cgi?id=166301=edit Display settings -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482225] New: Task switcher ignores windows on 1 screen (of 3)
https://bugs.kde.org/show_bug.cgi?id=482225 Bug ID: 482225 Summary: Task switcher ignores windows on 1 screen (of 3) Classification: Plasma Product: kwin Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: ker...@ag.de1.cc Target Milestone: --- Created attachment 166300 --> https://bugs.kde.org/attachment.cgi?id=166300=edit Task switcher settings SUMMARY When using Tab Switcher to switch between applications, those on one of my screens are completely ignored (not visible/selectable). Which of my screens is ignored, may change after switching virtual desktops. I have 3 screens, 2 of which are identical (EIZO L568). But the other one is affected as well. STEPS TO REPRODUCE 1. Open a bunch of windows across several screens. 2. Press Meta+Tab to switch window. OBSERVED RESULT Only windows on 2 of my 3 screens are selectable. Can't switch to the others via this shortcut. EXPECTED RESULT Can switch to any window on the current virtual desktop. SOFTWARE/OS VERSIONS ADDITIONAL INFORMATION Switching via other shortcuts like "Switch to Window to the Right" works across all screens (although I can't use it to switch to any completely covered windows :( ). Relevant settings attached. Switching to a different visualization (e.g. Cover switch) does not help (tried them all). -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 482050] kile did not start
https://bugs.kde.org/show_bug.cgi?id=482050 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #1 from Arek Guzinski --- Same problem for me. I also tried installing libokular5core9 and libokular5core11 to fix it, but that didn't help. I assume this is due to the inline viewer, which never worked for me anyway (because I use xelatex and it only seems to work with pdflatex). Maybe making that component optional could work as a quick workaround? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 482182] Breeze is mixes up light & dark
https://bugs.kde.org/show_bug.cgi?id=482182 --- Comment #3 from Arek Guzinski --- Just updating did not fix the issue (though it did fix 2 other problems that I hadn't reported yet). So I installed a fresh neon user edition into a vm and compared my installed packages to those on the vm. The culprit was plasma-integration, which was still at version 5.15. Upgrading it to 6.0 solved the problem :). I think the root of the issue is that plasma-desktop depends on any version of plasma-intergation. Instead it should depend on >= 6.0. I also noticed that I had a package named plasma-integration5 (version 6.0) installed, which is not present on the vm. Is this for integrating qt5 based applications? Should it be on the fresh install as well? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 482182] New: Breeze is mixes up light & dark
https://bugs.kde.org/show_bug.cgi?id=482182 Bug ID: 482182 Summary: Breeze is mixes up light & dark Classification: Plasma Product: Breeze Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Color scheme Assignee: plasma-b...@kde.org Reporter: ker...@ag.de1.cc Target Milestone: --- Created attachment 166269 --> https://bugs.kde.org/attachment.cgi?id=166269=edit system settings and system monitor with breeze dark SUMMARY After upgrading to plasma 6, the breeze themes are broken in a way that mixes elements from the light & dark themes. How bad it is, depends on the application and there are much more mixups with breeze dark than breeze light. Barely usable with breeze dark: system settings, kgetnewhotstuff, system monitor Minor problems: gwenview, dolphin, kate.. kmail partially uses icons from breeze light, but seems unaffected otherwise STEPS TO REPRODUCE 1. upgrade system 2. start system settings OBSERVED RESULT see screenshot EXPECTED RESULT a beautiful application with well readable text - just like in plasma 5 SOFTWARE/OS VERSIONS Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15,5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 482137] New: Regression: Filesystem/Clipboard not shared anymore
https://bugs.kde.org/show_bug.cgi?id=482137 Bug ID: 482137 Summary: Regression: Filesystem/Clipboard not shared anymore Classification: Applications Product: krdc Version: 24.02.0 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: RDP Assignee: uwol...@kde.org Reporter: ker...@ag.de1.cc CC: aa...@kde.org Target Milestone: --- SUMMARY after upgrading to 24.02, clipboard and filesystem are not shared anymore. Downgrading back to 23.08.5 fixes it. STEPS TO REPRODUCE 1. connect to a windows machine via rdp 2. try to copy/paste text 3. access network drive //tsclient to copy files OBSERVED RESULT clipboard is not shared between machines - both sides only paste their own last copied text. //tsclient exists but has no directories to copy files to/from EXPECTED RESULT text copied on host or server can be pasted in either machine. //tsclient on windows contains a directory that maps to a path on my linux machine SOFTWARE/OS VERSIONS Windows: 10 Operating System: KDE neon 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-21-generic (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15,5 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 ADDITIONAL INFORMATION I'm also missing the extra options text field in the host configuration window, but that's not critical (for me) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 343635] No way to set cursor blink rate / cursorFlashTime
https://bugs.kde.org/show_bug.cgi?id=343635 --- Comment #6 from Arek Guzinski --- > Hi, is it possible to review this? CursorBlinkRate=0 in the KDE section of > .config/kdeglobals does not have any effect anymore. You had me scared there! But I can't confirm this. It still works for me on current Neon. I also installed Neon unstable (with Plasma 6.1dev) in a VM and disabling the blinking cursor worked there, too. Would be nice if we could configure this in system settings... -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 463603] Cannot install Wine because of Sane
https://bugs.kde.org/show_bug.cgi?id=463603 Arek Guzinski changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||ker...@ag.de1.cc Ever confirmed|0 |1 --- Comment #1 from Arek Guzinski --- Bump! I can confirm that this is still a problem (using User Edition). It should be noted that this only affects the 32-bit version of wine, but I can't think of any software that I might want to run in wine and is actually providing 64-bit binaries (it's sad, considering that 64-bit has been around for so long). So wine:i386 is the important one. Simply providing a 32-bit package of libpoppler-glib8 in the neon sources might fix the problem. I tried to build one via apt-get (source|build-dep) and dpkg-buildpackage --target-arch=i386, but that failed. A workaround that I have seen recomended is to downgrade libpoppler to the ubuntu-jammy version, but I'm not sure if this will break anything. (versions of this package can not have different versions per arch) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472492] New: opening krunner or the compositor-kcm freezes kwin_x11
https://bugs.kde.org/show_bug.cgi?id=472492 Bug ID: 472492 Summary: opening krunner or the compositor-kcm freezes kwin_x11 Classification: Plasma Product: kwin Version: 5.27.6 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: ker...@ag.de1.cc Target Milestone: --- Created attachment 160441 --> https://bugs.kde.org/attachment.cgi?id=160441=edit Backtrace of frozen kwin_x11 SUMMARY Starting krunner causes kwin to freeze on X11. STEPS TO REPRODUCE 1a. start krunner - (tried per shortcut or konsole; makes no difference) or 1b. start systemsettings and navigate to "Display and Monitor" -> Compositor OBSERVED RESULT Everything visible except the mouse cursor freezes. (Sound is not affected) The mouse cursor also continues to change depending on item in the background. Waiting cursor is still animated. After kwin restarts (by switching to text console; then back to X11 and wait a few seconds): krunner works normal the compositor kcm is a black rectangle and stays that way even if compositing is disabled. Both work fine if compositing is disabled before start. Problem does not occurr in wayland-session. EXPECTED RESULT No freeze SOFTWARE/OS VERSIONS Linux Distro: KDE Neon KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION GPU: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 NVidia driver: 535.54.03 Kernel: 6.1.0-1016-oem (happens with 6.1.0-1015-oem as well) MORE DETAILS: This started after upgrading some packages (not sure which, but I assume kwin_x11 was among them) a few days ago. At first I thought this might be related to #338355, but there are too many differences in the freeze description: Also true here: > - Entire desktop image is frozen > - Pointer still works > - Does not happen if compositing is disabled > - Does not happen on Wayland (But too many other things don't work for me) NOT true here: > - Pointer still operates on desktop under frozen image (more on that below) > - If during the freeze, I tried to operate on any windows with pointer, > they now show up in updated positions/sizes, etc. > - Does not happen on kernels older than 6.1.9 > - Does not happen if compositing is toggled off then on after logging in > - Does not happen a 2nd time if kwin is killed and restarted In case of the kernel version, that is assuming ubuntu kernel versioning matches upstream. I followed the steps mentioned in #338355 to produce a backtrace which indicates a different cause. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 433171] Yakuake Opens, but does not close under wayland
https://bugs.kde.org/show_bug.cgi?id=433171 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465041] Resizing the header and moving the mouse above the window causes the header to snap back to maximized state
https://bugs.kde.org/show_bug.cgi?id=465041 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #2 from Arek Guzinski --- I can reproduce this sometimes... Whether it happens at all and to what size it snaps back to, seems to be related to the initial size (when elisa was started). Will investigate further in the next days. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 436504] Sleep/suspend is broken on KDE Neon Testing Edition
https://bugs.kde.org/show_bug.cgi?id=436504 --- Comment #21 from Arek Guzinski --- I'm still getting logged out instead of putting the computer to sleep. But at least my workaround is working.. Current setup: Operating System: KDE neon 5.25 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.97.0 Qt Version: 5.15.5 Kernel Version: 5.15.0-46-generic (64-bit) Graphics Platform: X11 systemd: 245.4-4ubuntu3.17 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 436504] Sleep/suspend is broken on KDE Neon Testing Edition
https://bugs.kde.org/show_bug.cgi?id=436504 --- Comment #17 from Arek Guzinski --- Does anyone who is *not* on neon experience this bug? If so, what Distro are you on? Is it Ubuntu-based? I still think, this is more likely an issue with systemd (or at least it's ubuntu-packages), but I can't find anything on their bugtrackers :/ Btw: here is a workaround for the Sleep-shortcut, that might work for some people. I did work for me before, but not now, because every time the system wakes up again, some fan decides to spin and not stop until I reboot :( - this did not happen the last time. In the shell: $ sudo -i $ echo "echo mem > /sys/power/state" > /usr/local/sbin/sleep $ chmod +x /usr/local/sbin/sleep $ visudo This will open /etc/sudoers in vim (do NOT do this manually). Add the following line somewhere near the bottom (I put it right above the #includedir statement), replacing USER and HOSTNAME with your user name and whatever is in /etc/hostname: USER HOSTNAME = (root) NOPASSWD: /usr/local/sbin/sleep close with ESC ZZ then open systemsettings and navigate to Shortcuts -> Custom Shortcuts Right Click on some group (or create one) and create a new shortcut (New -> Global Shortcut -> Command/URL) Set Trigger to your prefered Sleep shortcut Set Action to sudo /usr/local/sbin/sleep -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 436504] Sleep/suspend is broken on KDE Neon Testing Edition
https://bugs.kde.org/show_bug.cgi?id=436504 --- Comment #15 from Arek Guzinski --- Upgraded the system, and now that issue is back again - great... not! systemd is now 245.4-4ubuntu3.14 The rest: Operating System: KDE neon 5.23 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-46-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15,6 GiB of RAM Graphics Processor: NV136 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 436504] Sleep/suspend is broken on KDE Neon Testing Edition
https://bugs.kde.org/show_bug.cgi?id=436504 --- Comment #14 from Arek Guzinski --- I Completely forgot about this bug... It works fine for me now on Plasma 5.23.0 Frameworks 5.87.0 Kernel 5.11.0-37-generic systemd 245.4-4ubuntu3 and has so for a few weeks now. I also never had any networking issues because of this. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 436971] Wrong color with dark theme
https://bugs.kde.org/show_bug.cgi?id=436971 Arek Guzinski changed: What|Removed |Added Status|REPORTED|RESOLVED CC||ker...@ag.de1.cc Resolution|--- |DUPLICATE --- Comment #1 from Arek Guzinski --- *** This bug has been marked as a duplicate of bug 374426 *** -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 374426] HTML email is unreadable with dark theme
https://bugs.kde.org/show_bug.cgi?id=374426 Arek Guzinski changed: What|Removed |Added CC||med.medin.2...@gmail.com --- Comment #2 from Arek Guzinski --- *** Bug 436971 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401772] [Wayland] Screen cannot be rotated
https://bugs.kde.org/show_bug.cgi?id=401772 Arek Guzinski changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #11 from Arek Guzinski --- Ok, now it works for me, too :) Versions that changed since my last post: KDE Plasma Version: 5.22.5 -> 5.23.0 KDE Frameworks Version: 5.85.0 -> 5.87.0 Kernel Version: 5.11.0-34 -> 5.11.0-37 libnvidia-egl-wayland1 and libwayland.* versions are still the same. Closing this, as I don't see any recent me-toos -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 432062] Nvidia Wayland - KRunner never renders search results
https://bugs.kde.org/show_bug.cgi?id=432062 --- Comment #14 from Arek Guzinski --- I still have a small problem with accepting the bug as resolved ... When logging in as "tmp" - a testing user with it's home on a tmpfs, so I get the default config, the workaround works. But when I logged in as myself, it did not. With a status of resolved, I would expect either an automatic activation, or a dialog on login, that offers me to apply the workaround (you can't expect a non-technical user to fix this any other way!), but nothing like that happens. Then again, you mention qtquicksettings - which I was able to start via krunner in an X11-session (but NOT via systemsettings! - another bug?) and will try the wayland session again after writing this. For the record: Rendering Backend was set to OpenGL, but Render Loop was Automatic. I'll leave it up to you plasma-devs if you want to reopen the bug because of this or not. -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441013] yakuake-21.08 highlight terminals when moving focus -> highlighting does not correctly disappear
https://bugs.kde.org/show_bug.cgi?id=441013 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #4 from Arek Guzinski --- For the record, it's also happening with Yakuake 21.08.1 with the following configuration: Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-36-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Can somebody test if this happens on non-Nvidia cards, too? -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 441067] Yakuake is no longer available in the task switcher list
https://bugs.kde.org/show_bug.cgi?id=441067 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #4 from Arek Guzinski --- Can't wait for the fix to be available in neon packages :) - this is really annoying. Also, I believe this is probably a duplicate of #435544 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 440801] Crash after search or during typing of search criterea [CollectionTreeItem::row()]
https://bugs.kde.org/show_bug.cgi?id=440801 --- Comment #4 from Arek Guzinski --- Created attachment 141757 --> https://bugs.kde.org/attachment.cgi?id=141757=edit New crash information added by DrKonqi amarok (2.9.71) using Qt 5.15.3 - What I was doing when the application crashed: typing text into the search field I had this occurr on occasion before, but the new thing is that for the past week or so, it happens every single time I try searching, which makes Amarok quite useless :(. The package itself has not been updated for longer than that. Package version is 2:2.9.71+1SNAPSHOT20210626150430+0200-0ubuntu1ppa1~ubuntu20.04.1 from http://ppa.launchpad.net/pgomes/amarok/ubuntu - the only neon-compatible package source for amarok that I know of... -- Backtrace (Reduced): #4 0x7ff304bea0e4 in CollectionTreeItem::row() const () at /usr/lib/x86_64-linux-gnu/libamaroklib.so.1 #5 0x7ff304bf0054 in CollectionTreeItemModelBase::itemIndex(CollectionTreeItem*) const () at /usr/lib/x86_64-linux-gnu/libamaroklib.so.1 #6 0x7ff304bf00e4 in CollectionTreeItemModelBase::parent(QModelIndex const&) const () at /usr/lib/x86_64-linux-gnu/libamaroklib.so.1 #7 0x7ff3036b26f9 in QModelIndex::parent() const (this=0x555c526c4790) at ../../include/QtCore/../../src/corelib/itemmodels/qabstractitemmodel.h:443 #8 QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) (this=0x555c504edf60, source_top_left=..., source_bottom_right=..., roles=...) at itemmodels/qsortfilterproxymodel.cpp:1433 -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 440801] Crash after search or during typing of search criterea [CollectionTreeItem::row()]
https://bugs.kde.org/show_bug.cgi?id=440801 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401772] [Wayland] Screen cannot be rotated
https://bugs.kde.org/show_bug.cgi?id=401772 Arek Guzinski changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|WORKSFORME |--- --- Comment #9 from Arek Guzinski --- @Germano Massullo > I am no longer experiencing this problem Interesting.. on current KDE neon I'm still affected by it. What version of libwayland do you have installed? Maybe that is the problem.. @everyone Is there any way to obtain error messages for rotating via systemsettings? Starting it via Konsole did not provide anything related. Should I change platform and version accordingly, or should it be kept to it's original value for reference? Not sure what the policy here is... My system: Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.3 Kernel Version: 5.11.0-34-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 (driver = 470.63.01) Other library versions that might be important: libnvidia-egl-wayland1 1:1.1.3-1ubuntu1 libwayland.* 1.18.0-1 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 436504] Sleep/suspend is broken on KDE Neon Testing Edition
https://bugs.kde.org/show_bug.cgi?id=436504 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #12 from Arek Guzinski --- I think this might be an issue with some lower level. Maybe systemd? I'm on KDE neon with Plasma 5.22.4 and have this problem. However the same (=logout) happens using $ systemctl suspend while $ echo -n mem > /sys/power/state puts the computer to sleep like expected -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 432062] Nvidia Wayland - KRunner never renders search results
https://bugs.kde.org/show_bug.cgi?id=432062 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #5 from Arek Guzinski --- (In reply to Andreas Hartmann from comment #2) > Should say additionally, that krunner hangs and must be killed. I'm having the issue as originally described, too. But I don't have to kill krunner. I suspect the original description is a duplicate of #427921, but yours could be a different bug. For reference, my system is: Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-63-generic (64-bit) Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 (Driver: 470.57.02) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431851] Automatic screen rotation should rotate all built-in pointing devices.
https://bugs.kde.org/show_bug.cgi?id=431851 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 430826] Unable to rotate screen
https://bugs.kde.org/show_bug.cgi?id=430826 Arek Guzinski changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||ker...@ag.de1.cc --- Comment #2 from Arek Guzinski --- *** This bug has been marked as a duplicate of bug 401772 *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401772] [Wayland] Screen cannot be rotated
https://bugs.kde.org/show_bug.cgi?id=401772 Arek Guzinski changed: What|Removed |Added CC||pingo-po...@hotmail.fr --- Comment #5 from Arek Guzinski --- *** Bug 430826 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 401772] [Wayland] Screen cannot be rotated
https://bugs.kde.org/show_bug.cgi?id=401772 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #4 from Arek Guzinski --- A little bump: this bug still exists (at least for me) I'm on: Operating System: KDE neon 5.22 KDE Plasma Version: 5.22.4 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 Kernel Version: 5.8.0-63-generic (64-bit) Processors: 4 × Intel® Core™ i5-6500 CPU @ 3.20GHz Memory: 15,6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1060 6GB/PCIe/SSE2 Nvidia driver version: 470.57.02 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 437361] New: Description in the status bar susceptible to the character "RIGHT-TO-LEFT OVERRIDE"
https://bugs.kde.org/show_bug.cgi?id=437361 Bug ID: 437361 Summary: Description in the status bar susceptible to the character "RIGHT-TO-LEFT OVERRIDE" Product: dolphin Version: 21.04.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: status Assignee: dolphin-bugs-n...@kde.org Reporter: domk...@wp.pl CC: kfm-de...@kde.org Target Milestone: --- Created attachment 138560 --> https://bugs.kde.org/attachment.cgi?id=138560=edit Dolphin reversed statusbar description SUMMARY The description in the status bar is vulnerable to the U+202E (https://www.fileformat.info/info/unicode/char/202e/index.htm) character. Other KDE applications may also be affected. STEPS TO REPRODUCE 1. Open Konsole and type: fname=$(echo -e "test.txt\u202e") 2. Make new file with U202e char: echo "Some text" > $fname 3. Move the cursor over the created file with Dolphin and check the description on the status bar. OBSERVED RESULT The description content from the status bar is reversed back, while elsewhere it is displayed normally. EXPECTED RESULT Ignore U+202E and display the description correctly. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.4-arch1-2 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 980/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417457] entry of an app that is not playing audio has sound icon while another app plays audio
https://bugs.kde.org/show_bug.cgi?id=417457 Arek changed: What|Removed |Added CC||domk...@wp.pl --- Comment #25 from Arek --- Created attachment 137529 --> https://bugs.kde.org/attachment.cgi?id=137529=edit Taskbar bug I'm facing the same bug and it applies to Dophin and other apps. Operating System: Arch Linux KDE Plasma Version: 5.21.4 KDE Frameworks Version: 5.81.0 Qt Version: 5.15.2 Kernel Version: 5.11.13-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 980/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 434455] New: kinit doesn't terminate "file.so" and the partition cannot be unmounted.
https://bugs.kde.org/show_bug.cgi?id=434455 Bug ID: 434455 Summary: kinit doesn't terminate "file.so" and the partition cannot be unmounted. Product: frameworks-kinit Version: 5.80.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: fa...@kde.org Reporter: domk...@wp.pl CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY If I mount a partition manually using "mount" on a mount point, then after visiting the location with Dolphin and opening any file, then shuting down both. The partition is busy. STEPS TO REPRODUCE 1. sudo mount /dev/sdc1 /mnt 2. run Dolphin, go to /mnt and open any file (e.g. text file in Kate) 3. close file, close Dolphin 4. sudo umount /dev/sdc1 OBSERVED RESULT umount: /mnt: target is busy. lsof /mnt COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME file.so 6403 me5r REG 8,33 190 1448 /mnt/Clonezilla-Live-Version EXPECTED RESULT Successful unmounting. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 Kernel Version: 5.11.6-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 980/PCIe/SSE2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 338361] After swapping Esc and Caps Lock and assigning new action to shortcut which includes Esc, it doesn't work.
https://bugs.kde.org/show_bug.cgi?id=338361 --- Comment #5 from Arek Guzinski --- I'm on current neon now (see below) and it works. However I do remember this bug switching on and off between updates, but don't think it happened since 2019 or so. There is also the question how well this works on wayland... Operating System: KDE neon 5.21 KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 Kernel Version: 5.8.0-43-generic OS Type: 64-bit Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 428022] ksmserver-logout-greeter crashing on logout
https://bugs.kde.org/show_bug.cgi?id=428022 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #6 from Arek Guzinski --- Another confirmation on KDE neon. Now on upgrade to 5.21.1. This happens pretty much every time I do a bigger plasma upgrade, and has been happening for at least a year now. I'll attach the stack trace as well as the last part of aptitudes output (should include all the packeges that have been upgraded). Stack Application: ksmserver-logout-greeter (ksmserver-logout-greeter), signal: Aborted [New LWP 43340] [New LWP 43341] [New LWP 43342] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7ff13c4a0aff in __GI___poll (fds=0x7ffdcf978868, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7ff1388e0580 (LWP 43339))] Thread 4 (Thread 0x7ff135225700 (LWP 43342)): #0 __GI___libc_read (nbytes=16, buf=0x7ff135224ab0, fd=12) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=12, buf=0x7ff135224ab0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7ff13b39289f in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff13b349cde in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff13b34a132 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff13b34a2c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7ff13ca6bfbb in QEventDispatcherGlib::processEvents (this=0x7ff124000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #7 0x7ff13ca101ab in QEventLoop::exec (this=this@entry=0x7ff135224cc0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #8 0x7ff13c82aa12 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #9 0x7ff13df4dfa9 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #10 0x7ff13c82bbac in QThreadPrivate::start (arg=0x55ba43b37bf0) at thread/qthread_unix.cpp:329 #11 0x7ff13bcbb609 in start_thread (arg=) at pthread_create.c:477 #12 0x7ff13c4ad293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7ff1369e5700 (LWP 43341)): #0 0x7ff13b34670d in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7ff13b348165 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff13b349adf in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff13b34a132 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff13b34a2c3 in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff13ca6bfbb in QEventDispatcherGlib::processEvents (this=0x7ff128000b60, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7ff13ca101ab in QEventLoop::exec (this=this@entry=0x7ff1369e4cb0, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:141 #7 0x7ff13c82aa12 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #8 0x7ff13d393f4b in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7ff13c82bbac in QThreadPrivate::start (arg=0x7ff13d417d80) at thread/qthread_unix.cpp:329 #10 0x7ff13bcbb609 in start_thread (arg=) at pthread_create.c:477 #11 0x7ff13c4ad293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7ff137cc5700 (LWP 43340)): #0 0x7ff13c4a0aff in __GI___poll (fds=0x7ff137cc4be8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7ff13c27ac1a in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7ff13c27c90a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7ff1381ded58 in QXcbEventQueue::run (this=0x55ba43922b60) at qxcbeventqueue.cpp:228 #4 0x7ff13c82bbac in QThreadPrivate::start (arg=0x55ba43922b60) at thread/qthread_unix.cpp:329 #5 0x7ff13bcbb609 in start_thread (arg=) at pthread_create.c:477 #6 0x7ff13c4ad293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7ff1388e0580 (LWP 43339)): [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50 #5 0x7ff13c3b0859 in __GI_abort () at abort.c:79 #6 0x7ff13c7f0be7 in qt_message_fatal (context=..., message=...) at global/qlogging.cpp:1914 #7 QMessageLogger::fatal (this=this@entry=0x7ffdcf9794d0, msg=msg@entry=0x7ff13e51f816 "%s") at global/qlogging.cpp:893 #8 0x7ff13e2d441e in QSGRenderLoop::handleContextCreationFailure (this=this@entry=0x7ff1300078b0, window=0x55ba43ae0240) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:208 #9 0x7ff13e2d5b72 in QSGGuiThreadRenderLoop::renderWindow
[okteta] [Bug 336607] cursor is blinking (flashing) at insane rate
https://bugs.kde.org/show_bug.cgi?id=336607 --- Comment #18 from Arek Guzinski --- And back again ^^ - had a lot of distraction lately... >> * Directly after switching between insert and overwrite mode, the cursor is >> not drawn at all until you move it. I believe this is because drawing the >> cursor is so tightly coupled to the blinking timer. I haven't found them >> yet, but can imagine that there are other cases where this happens. > Any chance that happened due to some patches you have? Because I > cannotreproduce that, and the code logic should actually ensure that after > any change the initial blink cursor state is visible/on. Well... probably... I tried it with the current package in neon and can't reproduce it either :) One more thing I noticed (which might be intended?): If the keyboard focus is anywhere except the editing part or the decoding table, the cursor is invisible. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 336607] cursor is blinking (flashing) at insane rate
https://bugs.kde.org/show_bug.cgi?id=336607 --- Comment #15 from Arek Guzinski --- Created attachment 134566 --> https://bugs.kde.org/attachment.cgi?id=134566=edit the above, with cursor slightly more to the left -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 336607] cursor is blinking (flashing) at insane rate
https://bugs.kde.org/show_bug.cgi?id=336607 --- Comment #14 from Arek Guzinski --- Created attachment 134565 --> https://bugs.kde.org/attachment.cgi?id=134565=edit possible solution for insertion cursor problem -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 336607] cursor is blinking (flashing) at insane rate
https://bugs.kde.org/show_bug.cgi?id=336607 --- Comment #13 from Arek Guzinski --- And a happy new year to you! I'm glad my work got this rolling :) As far as the insertion mode is concerned... I comletely forgot about it, but on a second look, I see what you mean. From my point of view, "difficult to distinguish in a rarely used mode" is a major improvement from "practicaly unusable". I gave the insertion mode problem some consideration, and can think of 2 possible solutions (although none of them feels perfect). One would be to draw a 2 pixel in fg-color, 2 pixel bg-color alternating line around the block (I'll attach a mockup). The other might be to highlight the line in the active subview (like the active line in kate). I also noticed 2 related minor problems: * the insertion cursor overlaps with the value a bit too much - I think it would be better to draw it a pixel more to the left (see second mockup for comparison).. maybe even 2 pixels. * Directly after switching between insert and overwrite mode, the cursor is not drawn at all until you move it. I believe this is because drawing the cursor is so tightly coupled to the blinking timer. I haven't found them yet, but can imagine that there are other cases where this happens. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 411326] krunner hangs on first start
https://bugs.kde.org/show_bug.cgi?id=411326 --- Comment #19 from Arek Guzinski --- With the following versions... Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.4 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 ... I can't reproduce the Bug anymore :) (yep, I switched Instant Messeging plugin back on) - I assume, this includes the mentioned commit -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 429889] New: triyng to set up connection on unmanageble device should trigger error message
https://bugs.kde.org/show_bug.cgi?id=429889 Bug ID: 429889 Summary: triyng to set up connection on unmanageble device should trigger error message Product: systemsettings Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_networkmanagement Assignee: jgrul...@redhat.com Reporter: ker...@ag.de1.cc CC: plasma-b...@kde.org Target Milestone: --- SUMMARY If trying to set up a wired Ethernet connection, Connections module will create the connection (as "In User Inf, but it is impossible to get it to actually connect. No hint as to what the Reason may be is given. STEPS TO REPRODUCE 1. make sure /usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf contains [keyfile] unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma 2. Try to set up a Wired connection and connect it OBSERVED RESULT There is no connection visible in plasma-nm and nothing happens EXPECTED RESULT Tell the user that the systemwide setting for network-manager prohibits configuring the interface SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.8.0-23-generic OS Type: 64-bit ADDITIONAL INFORMATION nmtui-connect displays a helpful error message in same situation -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 429885] New: not having network-manager managing connections causes major problems in several kde applications
https://bugs.kde.org/show_bug.cgi?id=429885
Bug ID: 429885
Summary: not having network-manager managing connections causes
major problems in several kde applications
Product: frameworks-kded
Version: 5.76.0
Platform: Neon Packages
OS: Linux
Status: REPORTED
Severity: grave
Priority: NOR
Component: general
Assignee: fa...@kde.org
Reporter: ker...@ag.de1.cc
CC: kdelibs-b...@kde.org
Target Milestone: ---
note:
I report this to kded because the problem seems to be related to the way kde
applications find out about network connection state and I can't find out how
exactly this happens.
kded seems to provide this information through dbus, so I chose it as "closest
match".
SUMMARY
After several days of kmail not working, I noticed that akregator can't fetch
feeds either.
This along with Bug #424245 and several hours of triyng stuff led to the
following summary:
Applications not beeing able to get data from Network (with the "quality" of
"Error Messages"):
Akonadi (KMail, KOrganizer) - "Connection established - Offline"
Akregator "Networking is not available" - the only useful :)
Konqueror (http(s) only - sftp still worked) something like "File not found"
(yes! "file"!)
qdbus showed: back then (not working) | now after workaround (working)
$ qdbus org.kde.kded5 /modules/networkstatus
org.kde.Solid.Networking.Client.status
0 | 4
$ qdbus org.kde.kded5 /modules/networkstatus
org.kde.Solid.Networking.Service.networks
{} | SolidNetwork
Configuration:
I was using ifupdown | netplan.io (now that I uninstalled netplan, I'm not sure
the system was actually using it...)
Workaround that fixed everything:
1. uninstall netplan.io
2. install network-manager & plasma-nm
3. make network-manager manage wired connections
4. configure wired connection in plasma-nm
the whole problem started only recently (probably after updating to 5.76.0)
... I don't want network-manager, because there is only one
dhcp-wired-connection and no need to ever change network configuration
STEPS TO REPRODUCE
1. uninstall network-manager
OBSERVED RESULT
no http for kde-apps
EXPECTED RESULT
no problems
SOFTWARE/OS VERSIONS
Distro: KDE Neon (focal)
KDE Plasma Version: 5.20.3
KDE Frameworks Version: 5.76.0
Qt Version: 5.15.1
ADDITIONAL INFORMATION
This is related to #322602 and (at least my version of) #424245
Non-KDE software was not affected (tested with vivaldi and the qt http example)
It is not a user configuration problem - I had the same problems with a fresh
user
--
You are receiving this mail because:
You are watching all bug changes.
[Akonadi] [Bug 424245] Agent says "Connection established" without having any connection
https://bugs.kde.org/show_bug.cgi?id=424245 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #1 from Arek Guzinski --- Same problem here with 5.15.3 on KDE neon (20.04 based) in akonadiconsole: Akonadi Server Self-Test shows no errors. IMAP agent: Status: Offline, Idle Status Message: Connection established lsof -n -p `pgrep -f akonadi_imap_resource_1` | grep -v 'mem' shows no IP file descriptors (this is on my main computer - it does show them on my laptop, where akonadi is working fine) But: bearer plugins are enabled (or am i missing one?) # ls -la /usr/lib/x86_64-linux-gnu/qt5/plugins/bearer total 612 drwxr-xr-x 2 root root 4096 Nov 20 10:29 . drwxr-xr-x 73 root root 53248 Nov 28 23:14 .. -rw-r--r-- 1 root root 233536 Nov 10 18:12 libqconnmanbearer.so -rw-r--r-- 1 root root 81224 Nov 10 18:12 libqgenericbearer.so -rw-r--r-- 1 root root 254096 Nov 10 18:12 libqnmbearer.so There are no helpful messeges of any kind - clicking on "Check Mail" in kmail does absolutely nothing. I also tried resetting akonadi by following the steps at https://wiki.ubuntuusers.de/Akonadi/#Akonadi-zuruecksetzen (in german) and reconfiguring the IMAP agent. This did *not* fix the problem... So currently I can't check my mails on my main computer. Help! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 429699] New: No "Home" in location bar after open standard directories (Music, Documents etc.)
https://bugs.kde.org/show_bug.cgi?id=429699 Bug ID: 429699 Summary: No "Home" in location bar after open standard directories (Music, Documents etc.) Product: dolphin Version: 20.08.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: domk...@wp.pl CC: kfm-de...@kde.org Target Milestone: --- Created attachment 133676 --> https://bugs.kde.org/attachment.cgi?id=133676=edit On the left "New folder" on the right standard directory SUMMARY The navigation/location bar behaves differently for standard directories and different for user-created directories. STEPS TO REPRODUCE 1. Run Dolphin 2. Open e.g. Music directory or 1. Run Dolphin 2. Open a different directory than the default "home" directories OBSERVED RESULT If You open e.g Music directory on location bar You see only ">Music" (No "home") EXPECTED RESULT It should show like for user-created directories: ">Home>Music" SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.2 Kernel Version: 5.9.10-arch1-1 OS Type: 64-bit ADDITIONAL INFORMATION You can see this bug in the attachment. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 359351] skanlite should display a progress bar when uploading firmware (Usability bug)
https://bugs.kde.org/show_bug.cgi?id=359351 --- Comment #4 from Arek Guzinski --- Nice to see the old bugs still get attention... Unfortunately I cannot test this, as I don't have a scanner anymore. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423421] Plasmashell occasionally 'forgets' to load widgets and wallpaper
https://bugs.kde.org/show_bug.cgi?id=423421 --- Comment #10 from Arek Guzinski --- Created attachment 132905 --> https://bugs.kde.org/attachment.cgi?id=132905=edit xsession-errors for 3 display setup -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423421] Plasmashell occasionally 'forgets' to load widgets and wallpaper
https://bugs.kde.org/show_bug.cgi?id=423421 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #9 from Arek Guzinski --- Same thing happens to me on current KDE Neon with Plasma 5.20.1 (and a few versions before). Things that might be useful to know: it's a 3 display setup and when it happens, it's per screen - meaning it usually affects one or two of them. activity switcher shows only "New Activity" on all screens - "Desktop" (the other configured one) is not shown. I'll attach my xsession-errors, too. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 425896] Kate toolbars appear and disappear
https://bugs.kde.org/show_bug.cgi?id=425896 --- Comment #3 from Arek --- Created attachment 131632 --> https://bugs.kde.org/attachment.cgi?id=131632=edit Kate no save option after open and close new tab This bug still exists. I added an attachment showing the essence of the problem. Kate version: 20.08.1 Operating System: Arch Linux KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.1 Kernel Version: 5.8.8-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 980/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 425896] Kate toolbars appear and disappear
https://bugs.kde.org/show_bug.cgi?id=425896 Arek changed: What|Removed |Added CC||domk...@wp.pl --- Comment #1 from Arek --- This bug also occurs with Arch Linux and is annoying. I use the Kate editor quite often, and in addition to the disappearing buttons on the toolbar, the context menu is also deactivated. Operating System: Arch Linux KDE Plasma Version: 5.19.4 KDE Frameworks Version: 5.73.0 Qt Version: 5.15.0 Kernel Version: 5.8.5-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15.6 GiB of RAM Graphics Processor: GeForce GTX 980/PCIe/SSE2 -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 411326] krunner hangs on first start
https://bugs.kde.org/show_bug.cgi?id=411326 --- Comment #14 from Arek Guzinski --- Created attachment 130310 --> https://bugs.kde.org/attachment.cgi?id=130310=edit krunner 5.19.3 on neon -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 411326] krunner hangs on first start
https://bugs.kde.org/show_bug.cgi?id=411326 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #13 from Arek Guzinski --- I got this bug since i upgraded to 5.19.3 (nope - did not have that before...) on KDE neon. Disabling the telepathy plugin fixed it (not sure why it was enabled anyway - I don't need it). The behavior was a little different though: * krunner would krash after some time of hanging - I measured ~15 and ~45 seconds. * it's not usable even an hour after login. I'll attach a strace dump. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422844] Stuttering Plasma effects after the composer's resumption
https://bugs.kde.org/show_bug.cgi?id=422844 --- Comment #2 from Arek --- Note/Tip: This bug occurs when there is even one minimized application on the taskbar. If no application window was minimized while pausing and resuming the composer, the error does not appear. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422844] Stuttering Plasma effects after the composer's resumption
https://bugs.kde.org/show_bug.cgi?id=422844 --- Comment #1 from Arek --- This bug is also revealed when switching the scaling methods or display engine in the composer's settings window. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422844] New: Stuttering Plasma effects after the composer's resumption
https://bugs.kde.org/show_bug.cgi?id=422844 Bug ID: 422844 Summary: Stuttering Plasma effects after the composer's resumption Product: kwin Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: domk...@wp.pl Target Milestone: --- SUMMARY For example, when the MPV player is started in full-screen mode, the composer are suspended. After the player returns to window mode, the composer are resumed. After that, all Plasma effects get stuttering. If all opened app windows are maximized and again minimized, then Plasma effects work smoothly again. STEPS TO REPRODUCE 1. Run MPV video in window mode (Plasma effects work smoothly) 2. Switch MPV to full screen mode and back to window mode (after compositing resume all animations stuttering) 3. (Optional) Maximize and again minimize all opened application windows - Plasma effects work smoothly again ---OR--- 1. Open few random apps 2. Press Alt+Shift+F12 to suspend compositions 3. Press Alt+Shift+F12 to resume compositions - now all Plasma effect stuttering (especially visible at the desktop cube) 4.(Optional) Maximize and again minimize all open application windows - Plasma effects work smoothly again. OBSERVED RESULT Animations of Plasma effects stuttering after pausing and resuming the composition. EXPECTED RESULT All animations work smoothly as before pausing and resuming the composition. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.7.2-arch1-1 OS Type: 64-bity Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15,6 GiB RAM-u Graphics Processor: GeForce GTX 980/PCIe/SSE2 Graphics drivers: nvidia 440.82-21 (proprietary drivers) ADDITIONAL INFORMATION The bug faced since the last update of KDE Plasma to version 5.19.0 and previously, the bug didn't occur with the same graphics drivers and the older KDE Plasma 5.18.5. (and older kwin) For Intel iGPU's, this problem doesn't occur. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 422840] New: Can't open Window management settings
https://bugs.kde.org/show_bug.cgi?id=422840 Bug ID: 422840 Summary: Can't open Window management settings Product: systemsettings Version: 5.19.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcmshell Assignee: plasma-b...@kde.org Reporter: domk...@wp.pl Target Milestone: --- Created attachment 129240 --> https://bugs.kde.org/attachment.cgi?id=129240=edit Window management settings bug "More actions" > "Window management settings" option doesn't work. It also doesn't work when started via the KDE kickoff menu or krunner. STEPS TO REPRODUCE 1. Right click on the title bar of any application, e.g. kate 2. More actions 3. Window management settings OBSERVED RESULT No any settings window appears. EXPECTED RESULT "Window management settings" window. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.19.0 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 Kernel Version: 5.6.15-arch1-1 OS Type: 64-bity Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz Memory: 15,6 GiB RAM-u Graphics Processor: GeForce GTX 980/PCIe/SSE2 ADDITIONAL INFORMATION $kcmshell5 kwinadvanced Couldn't load plugin "kcms/kcm_kwinoptions" : "The shared library was not found." -- falling back to old-style loading from desktop file Violation of memory protection (memory dump) -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414003] Systemsettings crashes when I'm trying to open any icon but second time.
https://bugs.kde.org/show_bug.cgi?id=414003 --- Comment #8 from Arek --- Comment on attachment 123877 --> https://bugs.kde.org/attachment.cgi?id=123877 Call the "systemsettings5" error Operating System: Arch Linux KDE Plasma Version: 5.17.3 KDE Frameworks Version: 5.64.0 Qt Version: 5.13.2 Kernel Version: 5.3.10-arch1-1 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414003] Systemsettings crashes when I'm trying to open any icon but second time.
https://bugs.kde.org/show_bug.cgi?id=414003 --- Comment #5 from Arek --- Created attachment 123877 --> https://bugs.kde.org/attachment.cgi?id=123877=edit Call the "systemsettings5" error -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414003] Systemsettings crashes when I'm trying to open any icon but second time.
https://bugs.kde.org/show_bug.cgi?id=414003 Arek changed: What|Removed |Added CC||domk...@wp.pl --- Comment #4 from Arek --- I have the same bug. It is easier to cause this bug when "Icon View" is set. 1) Set "Icon View" in systemsettings5 2) Close systemsettings5 (very important) 3) Run systemsettings5 4) Select "Global appearance" and return to all settings 5) Select e.g. "Fonts" and return to all settings 6) Do that until at some point an error. If it is started via the terminal after calling the error you can see: "Memory protection violation" -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 200776] Switching from krdc via alt-tab sends "alt key" to the remote desktop
https://bugs.kde.org/show_bug.cgi?id=200776
--- Comment #17 from Arek Guzinski ---
Ok... so i looked at the code, played around and realized 2 things:
The bad:
I don't think this problem can be fixed in krdc alone.
The solution Sektor van Skijlen proposed is how I'd try to solve it - but this
can't be done because embedding another X application blocks most focus events
from krdc.
Possible workarounds:
a) having kwin (or a kwinscript) notify krdc if the window changes via dbus.
Contra: would depend on using a window manager that can do that - AFAIK
this means kwin or xmonad.
b) Monitoring xfreerdp for messages that hint at a focus change.
Contra: might need modifiyng freerdp.
c) Fixing whatever causes the lost focus events (possibly Qt - more likely X.
And there is no way I'm touching Xorg code!)
Has anyone tested this on wayland? if so: whats the situation there?
The good:
the above isn't really necessary, as freerdp has already (mostly) fixed this :)
In my tests with the current version from git (2.0.0-dev4) keys are almost
always properly released. Beeing a development version, of course, it has some
quirks (like sometimes randomly grabbing all keys until you press right ctrl).
But I found using it more pleasant than having to deal with unreleased keys.
In short: workaround = upgrade to current freerdp from git.
If anyone really can't use the git version I might be persuaded to implement
a). Otherwise I'll consider it "almost resolved upstream". (is this enough to
change status to resolved ?)
also: @Christoph Feck thanks for the links :). However this wasn't enough, as
krdc would still load both versions of the plugin - and always use the wrong
one :/.
I worked around it by placing these 2 lines at the start of
MainWindow::loadAllPlugins()
const QString badpath =
QString::fromUtf8("/usr/lib/x86_64-linux-gnu/qt5/plugins");
QCoreApplication::removeLibraryPath(badpath);
--
You are receiving this mail because:
You are watching all bug changes.
[krdc] [Bug 200776] Switching from krdc via alt-tab sends "alt key" to the remote desktop
https://bugs.kde.org/show_bug.cgi?id=200776 --- Comment #15 from Arek Guzinski --- I tried to fix it but pretty much hit a wall with plugin loading. this might be slightly off topic for a bug report, but... when i try to debug krdc (per gdb or qCDebug) this only works for parts of it. The problem is that the plugins (libkrdc_rdpplugin.so in this case) or always loaded from the system-installed krdc. Of course I could to something like link from there to my compiled plugins, but I'd prefer not to pollute my system... So... @developers: how do you set everything up for KRDC development? -- You are receiving this mail because: You are watching all bug changes.
[krdc] [Bug 200776] Switching from krdc via alt-tab sends "alt key" to the remote desktop
https://bugs.kde.org/show_bug.cgi?id=200776 Arek Guzinski changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #14 from Arek Guzinski --- bump! this is still a problem (IMO the most annoying bug in KRDC) in 2018 (using current Neon). If I find the time, I'll try to fix this myself next week or so. But since I don't know the source (yet), any hints on where to start and what problems this might cause are welcome. Also... is this a bug in krdc at all, or is it maybe an issue in xfreerdp? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 391609] autostart script is not executed, log claims it is
https://bugs.kde.org/show_bug.cgi?id=391609 --- Comment #5 from Arek Guzinski --- > Maybe there are some particularities in the script that are causing the > problem? damn it! yes, actually there was something.. after some more experimenting, i found that the "Session Autostart Manager Control Panel Module" -> "Add Script" was adding the "#!/bin/sh " header to every script, which seems to be mandatory now... since my script was from the old days, it did not have that header. adding it, fixed this problem :) would be nice if kde would have told me, my script can't start because of that. maybe "Session Autostart Manager Control Panel Module" could make a quick check when it's opened? the multiple execution issue with scripts that run "Before session start-up" still remains. should i open another bug for that? @Alexander Mentyu: thanks for motivating me to look closer! @francisco_t: many of the things xmodmap does, would be overwritten when kde sets the keyboard layout. are you sure that's not happening? (i don't think it should, but.. maybe..) as a workaround, you could try a script with the line (sleep 5; xmodmap ~/.xmodmaprc)& -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 391609] autostart script is not executed, log claims it is
https://bugs.kde.org/show_bug.cgi?id=391609 --- Comment #3 from Arek Guzinski --- okay... I just tried this with KUbuntu 18.04 LTS in VirtualBox and autostart works fine there. So maybe this will be fixed when Neon finally switches to 18.04. Upgrading to 5.13 on Neon at least, did not change anything... :( The question is: do i want to wait that long? It's really annoying to start all the stuff manually on login. Are there any known workarounds? If not, is there a guide on how to run ksmserver in gdb? I imagine it's not simple, as it should start a clean X/Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.
https://bugs.kde.org/show_bug.cgi?id=391805 --- Comment #5 from Arek Guzinski <ker...@ag.de1.cc> --- Bug no longer occurs in 5.12.5 :) As for formalaties: should I set the status to closed, or should that be done by the assignee/maintainer/whoever after some investigation into what might have fixed it? Are there any guidelines? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-frameworkintegration] [Bug 343635] No way to set cursor blink rate / cursorFlashTime
https://bugs.kde.org/show_bug.cgi?id=343635 Arek Guzinski <ker...@ag.de1.cc> changed: What|Removed |Added CC||ker...@ag.de1.cc -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 391609] autostart script is not executed, log claims it is
https://bugs.kde.org/show_bug.cgi?id=391609 --- Comment #1 from Arek Guzinski <ker...@ag.de1.cc> --- i experimented with running myxinit.sh from noblink.sh as a workaround and discovered that noblink.sh is executed twice at login and once at logout (i expected it to run only once at login). Is this wanted behaviour or another (possibly related) bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.
https://bugs.kde.org/show_bug.cgi?id=391805 Arek Guzinski <ker...@ag.de1.cc> changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |UNCONFIRMED --- Comment #4 from Arek Guzinski <ker...@ag.de1.cc> --- just saw your comment about the status.. interpreting it as "set now".. I noticed one strange thing (althought my guess is it's probably unrelated): when i log in as myself, the rotating thingie below the plasma-icon disappers after ~8 sec. For the new user, it keeps rotating the full 30 sec until the end. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 391805] Splashscreen always visible for 30 seconds. Plasma is ready much earlier.
https://bugs.kde.org/show_bug.cgi?id=391805 --- Comment #3 from Arek Guzinski <ker...@ag.de1.cc> --- > Can you include output of ~/.local/share/sddm/xorg-session.log after logging > in. I would, if there was something to include. $ ls -l ~/.local/share/sddm/xorg-session.log -rw--- 1 arek arek 0 Mär 13 14:29 /home/arek/.local/share/sddm/xorg-session.log same on my laptop btw. (where it's working properly) are there any other logs that could help? -- You are receiving this mail because: You are watching all bug changes.
[ksplash] [Bug 391805] New: Splashscreen always visible for 30 seconds. Plasma is ready much earlier.
https://bugs.kde.org/show_bug.cgi?id=391805 Bug ID: 391805 Summary: Splashscreen always visible for 30 seconds. Plasma is ready much earlier. Product: ksplash Version: 5.12.3 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: ker...@ag.de1.cc Target Milestone: --- Every time i log in to plasma, the splash screen is visible for exactly 30 seconds (i assume thats the timeout). However plasma is ready after a few seconds. $ top -b > log shows that there is barely any CPU activity after 8 seconds. $ when i log in via ssh and killall ksplashqml prematurely, plasma looks perfectly ready. I created a new user and logged in: same problem. On another (much slower) Computer with the same package versions, ksplashqml disappears after about 15 seconds, likely because plasma is ready... https://bugs.kde.org/show_bug.cgi?id=380495 sounded like it might be related, so i tried the patch: no change This has been going on for a while now.. perhaps since 5.12.0 Now i'm out of ideas where to look :/ What would, under normal circumstances, tell ksplashqml to quit? -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 391609] New: autostart script is not executed, log claims it is
https://bugs.kde.org/show_bug.cgi?id=391609 Bug ID: 391609 Summary: autostart script is not executed, log claims it is Product: ksmserver Version: 5.12.2 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: l.lu...@kde.org Reporter: ker...@ag.de1.cc Target Milestone: --- I have an autostart script configured in KDE. In "System Settings" -> Startup and Shutdown" -> "Autostart" Name Command Status Run On Script File | myxinit.sh myxinit.shEnabledStartup | noblink.sh noblink.shEnabledBefore session start-up .xsession-errors has the line ksmserver: Starting autostart script "/home/arek/.config/autostart-scripts/myxinit.sh" but nothing about noblink.sh however myxinit.sh is not executed (tested by putting "touch /tmp/yes" at the beginning. The file is not created) the code in noblink.sh is executed as expected -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 380223] Volume settings not in sync with Pulseaudio settings
https://bugs.kde.org/show_bug.cgi?id=380223 --- Comment #8 from Arek Guzinski <ker...@ag.de1.cc> --- After my last comment, it seemed to work fine... then it went to sometimes volume is ok, sometimes it's 0. About 3 weeks ago i tried switching phonon to gstreamer backend - and that seemed to fix it :) I had to delete all config files after that though - otherwise amarok would constantly stop playing when after each track. In other words: it seems to be a problem with the vlc phonon backend. -- You are receiving this mail because: You are watching all bug changes.
[trojita] [Bug 383045] New: Message box does not resize to window size
https://bugs.kde.org/show_bug.cgi?id=383045 Bug ID: 383045 Summary: Message box does not resize to window size Product: trojita Version: unspecified Platform: Manjaro OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Core Assignee: trojita-b...@kde.org Reporter: domk...@wp.pl Target Milestone: --- Created attachment 107039 --> https://bugs.kde.org/attachment.cgi?id=107039=edit Opened message in normal (plain) text mode Message plain text doesn't resize to window size. In HTML mode is OK. Look at attachment. Trojita 0.7 KDE: 5.10.4 KDE Framework: 5.36.0 Qt: 5.9.1 Kernel: 4.12.3-1 (64-bit) -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 368118] Bluetooth headset doesn't output voice after disconnected and reconnected
https://bugs.kde.org/show_bug.cgi?id=368118 Arek Marud <a.ma...@post.pl> changed: What|Removed |Added CC||a.ma...@post.pl --- Comment #3 from Arek Marud <a.ma...@post.pl> --- Confirm. Looks like the problem is specific to Bluedio headsets. I have also Philips bluetooth headset, and it is working fine. -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 380223] Volume settings not in sync with Pulseaudio settings
https://bugs.kde.org/show_bug.cgi?id=380223 --- Comment #4 from Arek Guzinski <ker...@ag.de1.cc> --- sounds like (as a worst case) a rewrite of the PA stack might be in order :( As for my situation: changing "Master Volume" to 50 seemed to fix the issue, but after a few days it returned, and now amarok starts muted again :/. Even though it doesn't sound like a pure config issue anymore, i'd like to try moving all my config files and setting amarok up again. In case that solves the issue, i'll send a diff. I am currently aware of the following config files: ~/.kde/share/config/amarok-appletsrc ~/.kde/share/config/amarok-appletsrcGx4859.new ~/.kde/share/config/amarok_homerc ~/.kde/share/config/amarokrc are there any other files i should move? Is there any reason i should rebuild the database as well? If so, which files would i have to move and how can i transfer my ratings? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 380223] Volume is set to 0% at startup
https://bugs.kde.org/show_bug.cgi?id=380223 --- Comment #2 from Arek Guzinski <ker...@ag.de1.cc> --- Ok... so i found ~/.kde/share/config/amarokrc In there was that part: [Phonon::AudioOutput] Amarok_Volume=0.79 [Playback] FadeoutOnPause=false Master Volume=0 Then i changed "Master Volume" to 50, which seems to have fixed the issue. After playing around for a bit, i found that "Amarok_Volume" is the last volume set via amarok's volume control, while "Master Volume" is what i set via any pulsaudio-aware volume control. Changing volume via amarok, also changes pa volume for it, but not vica versa (it does actually change the volume, but that is not reflected inside amarok). So, (only) if i set volume via amarok first and then in pa, those two values differ... and the second one is loaded @startup. (note: this is *not* what i did every time before) While this explains part of it, i still don't understand why amarok did not correctly save the "Master Volume" before, nor why it does now. (meaning: i am unable to reproduce the problem now) In any case you were right in that there must have been something wrong with the config. But: shouldn't those two volume values always be the same? What is the point of this information beeing saved twice? And most important: is amarok not syncing to changes via pa a bug? -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 380223] New: Volume is set to 0% at startup
https://bugs.kde.org/show_bug.cgi?id=380223 Bug ID: 380223 Summary: Volume is set to 0% at startup Product: amarok Version: 2.8.0 Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: amarok-bugs-d...@kde.org Reporter: ker...@ag.de1.cc Target Milestone: 2.9 Every time i start Amarok, volume is set to 0% Note: i am using KDE Neon, but selected "Kubuntu Packages" since the package version is 2:2.8.0-0ubuntu9 (no neon) Also: is Amarok dead? will there ever be a KF5 based Amarok? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 372881] Plasmashell crashes when adding default panel
https://bugs.kde.org/show_bug.cgi?id=372881 Arek Guzinski <ker...@ag.de1.cc> changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #4 from Arek Guzinski <ker...@ag.de1.cc> --- same problem here with plasme 5.8.5 on KDE-Neon. Also the new panel is added on the wrong screen (i want a panel on my secondary screen - it appears on the primary one) It also crashes with default settings (after removing plasma-org.kde.plasma.desktop-appletsrc and plasmashellrc). last line of output (appears 5 times): file:///usr/lib/x86_64-linux-gnu/qt5/qml/QtQuick/Controls/Styles/Base/SliderStyle.qml:224:13: QML Loader: Binding loop detected for property "x" backtrace: Thread 1 "plasmashell" received signal SIGSEGV, Segmentation fault. 0x7efcd4cd0637 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 (gdb) bt #0 0x7efcd4cd0637 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #1 0x7efcd4cd0716 in QQmlVMEMetaObject::metaCall(QObject*, QMetaObject::Call, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #2 0x7efcd4cb0aa1 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #3 0x7efcd4cb17da in QV4::QObjectWrapper::getProperty(QV4::ExecutionEngine*, QObject*, QQmlPropertyData*, bool) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #4 0x7efcd4cb21ba in QV4::QObjectWrapper::getQmlProperty(QQmlContextData*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*, bool) const () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #5 0x7efcd4cb247f in QV4::QObjectWrapper::getQmlProperty(QV4::ExecutionEngine*, QQmlContextData*, QObject*, QV4::String*, QV4::QObjectWrapper::RevisionMode, bool*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #6 0x7efcd4d55567 in QV4::QmlContextWrapper::get(QV4::Managed const*, QV4::String*, bool*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7efcd4c3bc1e in QV4::ExecutionContext::getProperty(QV4::String*) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #8 0x7efcd4cc4170 in QV4::Runtime::getActivationProperty(QV4::ExecutionEngine*, int) () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5 #9 0x7efc18055479 in ?? () #10 0x0078 in ?? () #11 0x458201c4ab9b5c00 in ?? () #12 0x0008 in ?? () #13 0x010a84d0 in ?? () #14 0x010a84d0 in ?? () #15 0x7efcb959a698 in ?? () #16 0x in ?? () -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 336607] cursor is blinking (flashing) at insane rate
https://bugs.kde.org/show_bug.cgi?id=336607 --- Comment #8 from Arek Guzinski <ker...@ag.de1.cc> --- Bump! 2 Years later and still not fixed :( While there is still no way to easily turn off blinking in qt5 on linux (shame on that!), it can be done with qt5noblink (https://github.com/igogo/qt5noblink). While this works for other applications, okteta (0.17.0 here) still blinks insanely. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 361589] New: Plasma crash after turn off / on amplituner (connected via HDMI)
https://bugs.kde.org/show_bug.cgi?id=361589 Bug ID: 361589 Summary: Plasma crash after turn off / on amplituner (connected via HDMI) Product: plasmashell Version: 5.6.1 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: crash Priority: NOR Component: Desktop Containment Assignee: se...@kde.org Reporter: domk...@wp.pl Any times if i turn on/off my A/V amplituner (Yamaha RX-A840 - AVENTAGE) or switch video/audio input from HDMI2 (PC) to AV4 (SmartTV) (and back to HDMI2) or turn off => on TV - plasma always be crashed. (i have connected pc to my home theater: PC =>A/V Amplituner =>LG 4k SmartTV) If any window is not minimalized after crash borders and window title bar disappear. Reproducible: Always Steps to Reproduce: 1. Turn OFF A/V amplituner or turn OFF TV. 2. Turn ON A/V amplituner or turn OFF TV. Actual Results: Plasma crash and automaticaly restart. Expected Results: Return to the previous state. PC configuration: Processor: Intel i7 4790k (4GHz@4.4GHz) GPU: Gigabyte GeForce GTX 980 G1 Motherboard: Asus Maximus VII Ranger RAM: 16GB (2400MHz) HyperX Savage SSD's: Samsung Evo 850 250GB and Samsung Evo 850 500GB Monitor: no monitor (connected via HDMI to A/V amplituner and LG 4k SmartTV) System: Linux Manjaro 15.02 /KDE (5.6.1) / kernel 4.4.6-1-MANJARO (dual boot with windows 8.1) GPU drivers version: Nvidia 361.42 Resolution: 1920x1080 @60Hz -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355528] Multiple monitor support is erratic
https://bugs.kde.org/show_bug.cgi?id=355528 --- Comment #18 from Arek Guzinski <ker...@ag.de1.cc> --- Created attachment 97232 --> https://bugs.kde.org/attachment.cgi?id=97232=edit logfiles for the three cases -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 355528] Multiple monitor support is erratic
https://bugs.kde.org/show_bug.cgi?id=355528 Arek Guzinski <ker...@ag.de1.cc> changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #17 from Arek Guzinski <ker...@ag.de1.cc> --- I also have issues with multi-monitor support, however this is on a desktop system, where both screens are always connected. The setup is (as taken from xrandr output) DFP1 connected primary 1920x1200+1024+0 DFP2 connected 1024x1280+0+0 (rotated to the) right The panel *should* appear on DFP1, but even if i change the config, it lasts at most for one start of plasma and appears on DFP2 the next time. when plasmashell is started, randomly one of 3 things happen: 1. (sometimes on login, mostly on manual restart) Everything except the panel beeing on the wrong screen is fine 2. (sometimes on login, maybe 30% of the time on manual restart) Background is visible, but no panel or other widgets 3. (most likely on login) Plasma is pretty messed up, meaning: the Plasma root window on DFP2 has the dimensions, as if the screen was not rotated, leaving black space at the bottom and overflowing to DFP1. if i click the root of DFP1, its root goes to front, hiding that part of DFP2's plasma. https://bugs.kde.org/show_bug.cgi?id=337590 is probably related to this. When i maximize windows, instead of the screens height, their height is set to 1074 pixels (on both screens). Width is ok. -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 359351] New: skanlite should display a progress bar when uploading firmware (Usability bug)
https://bugs.kde.org/show_bug.cgi?id=359351 Bug ID: 359351 Summary: skanlite should display a progress bar when uploading firmware (Usability bug) Product: Skanlite Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kare.s...@iki.fi Reporter: ker...@ag.de1.cc I have an Epson Perfection 660 scanner, which needs its firmware uploaded every time before scanning. When i start skanlite, a window pops up for maybe 0.5 seconds, then vanishes. After that nothing visible happens for a minute or two. Then the Skanlite window appears and everything works. Now i know, the firware is being uploaded and i just need to wait a bit, but a new user would think that the application crashed. Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[Skanlite] [Bug 359351] skanlite should display a progress bar when uploading firmware (Usability bug)
https://bugs.kde.org/show_bug.cgi?id=359351 --- Comment #2 from Arek Guzinski <ker...@ag.de1.cc> --- Well, lets see... xsane: same as skanlite :/ what i didn't notice before is that all three applications print the following 2 lines to stderr (which also answers the question how scanimage handles this): [snapscan] Scanner warming up - waiting 31 seconds. [snapscan] Scanner warming up - waiting 31 seconds. well, maybe i was wrong after all and the firmware isn't the reason - does not change the UI-issue though. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdelibs4support] [Bug 359320] New: formatDateTime(..., KLocale::FancyShortDate, ... ) should take LC_TIME into account
https://bugs.kde.org/show_bug.cgi?id=359320 Bug ID: 359320 Summary: formatDateTime(..., KLocale::FancyShortDate, ... ) should take LC_TIME into account Product: frameworks-kdelibs4support Version: unspecified Platform: Kubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: ker...@ag.de1.cc This is related to my bugreport for akregator https://bugs.kde.org/show_bug.cgi?id=359191 (theres a screenshot too), which turned out to belong to a frameworks component. I hope this is the correct component (probably not...), but after trying to find out which component exactly this belongs to for about 40 minutes, i had enough and took my best guess with the following env... LANGUAGE=en_US:de LC_TIME=de_DE.UTF-8 akregator shows the time as "MM/DD/ hh:mm AM/PM", as opposed to "DD.MM. hh:mm", which is what i would expect with LC_TIME=de_DE.UTF-8. What i would expect , vs what i get is (examples) Expected | What i get Yesterday 14:35 | Yesterday 02:35 PM 29.01.2016 19:20 | 01/29/2016 07:20 PM so in my opinion the function should translate the words based on LANGUAGE (as it does), but the numeric part based on LC_TIME, as this would be consistent with the Interface language being english and the date/time format being german as a workaround, LANGUAGE=en_GB:de makes things a bit better for me Reproducible: Always -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 340420] Make it easier to file issue reports
https://bugs.kde.org/show_bug.cgi?id=340420 Arek Guzinski <ker...@ag.de1.cc> changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #9 from Arek Guzinski <ker...@ag.de1.cc> --- While i agree that finding the product works well for a specific application, it does not for bugs that appear in multiple applications (aka bugs in the frameworks). This is made even worse by having kde 4&5 stuff mixed together. I propose the following changes: add a checkbox "show deprecated products" and/or add columns to the table, which show in which version of kde it is used add the Line "If you are unsure, choose kde" at the bottom of the table. This way it will be visible, after trying to find the right product, but not encourage people to use it every time. I remember that i did not file at least one bug in the past, because i could not find the right product and did not see the "kde" category. If you click the "search" link from https://bugs.kde.org/enter_bug.cgi?product=productname , the product should be preselected. sometimes i knew which api call causes a problem (through debug output, stack trace, alook into the applications source code, etc..). However, finding to which part of frameworks it belongs, is not that easy. it would be great if you could search for an api call. Or simply find the product name in the api reference. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 359191] aKregator does not honor LC_TIME / date and time in wrong format
https://bugs.kde.org/show_bug.cgi?id=359191 --- Comment #4 from Arek Guzinski <ker...@ag.de1.cc> --- ok, i see the problem now... > I saw in your screenshot that all is in english so it's the problem. yes, it is. and it should be, because, for several reasons, i prefer english as my interface language. However, i really really hate the US/UK date format, which is why i set my time to de_DE (btw: yes, i live in germany) i had a quick look at the dolphin source code, where QLocale is used, which displays the date the way i want it (dd.mm.). But QLocale does not support anything like KLocale::FancyShortDate. As FancyShortDate uses words, it seems to get its locale settings from the LANGUAGE variable, instead of LC_TIME. i think the correct way to handle this would be to use LANGUAGE for the words and LC_TIME for the rest (as, i believe, it was in kde 4) which is, of course, an issue for the kf5 libraries and not a bug in akregator. I'll file a report there. -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 359191] New: aKregator does not honor LC_TIME / date and time in wrong format
https://bugs.kde.org/show_bug.cgi?id=359191 Bug ID: 359191 Summary: aKregator does not honor LC_TIME / date and time in wrong format Product: akregator Version: unspecified Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: ker...@ag.de1.cc Version: 5.0.3 the date and time are displayed in US format (mm/dd/yy hh:mm AM/PM) instead of german format (dd.mm.yy HH:mm). output of $ env | ack-grep '^L[AC]' | sort LANG=en_US.UTF-8 LANGUAGE=en_US.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_NUMERIC=C LC_PAPER=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 Reproducible: Always date and time are correctly displayed in other applications ( tested with dolphin(15.08.03), konqueror (4.14.13), kmail(5.0.3) ) -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 335748] Information in date columns unclear, no controls to clarify
https://bugs.kde.org/show_bug.cgi?id=335748 Arek Guzinski <ker...@ag.de1.cc> changed: What|Removed |Added CC||ker...@ag.de1.cc --- Comment #2 from Arek Guzinski <ker...@ag.de1.cc> --- Created attachment 97110 --> https://bugs.kde.org/attachment.cgi?id=97110=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 335748] Information in date columns unclear, no controls to clarify
https://bugs.kde.org/show_bug.cgi?id=335748 --- Comment #3 from Arek Guzinski <ker...@ag.de1.cc> --- Damn it - sorry, the screenshot should go to another bugreport - can someone delete it? -- You are receiving this mail because: You are watching all bug changes.
