[plasmashell] [Bug 428394] huge memory leak
https://bugs.kde.org/show_bug.cgi?id=428394 Gabor Szita changed: What|Removed |Added CC||gaborszit...@gmail.com --- Comment #25 from Gabor Szita --- I'm having the same issue. I just came to realize that it's with wayland as it started appearing when I switched to wayland from X11. This has become almost a daily problem for me that I have to force-shut-down my computer and reboot it because it just freezes. The mouse starts lagging more and more and after about 20 seconds my whole computer just freezes. It usually happens to me when I'm using chrome, vs code, and I'm switching fast through tabs, windows, and open files. Since chrome and vs code are both based on the chromium engine, wouldn't this suggest a problem with the integration between the chromium engine and wayland? I'm on Arch Linux. KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 Kernel version: 6.1.1-arch1-1 (64-bit) Graphics Platform: Wayland CPU: Intel Core i5-6300U @ 2.40 GHz Memory: 15.5 GiB Product: PORTEGE Z30t-C -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 433253] Folder list shows unread messages but filter doesn't
https://bugs.kde.org/show_bug.cgi?id=433253 Gabor Körber changed: What|Removed |Added CC||g...@g4b.org --- Comment #1 from Gabor Körber --- Created attachment 143616 --> https://bugs.kde.org/attachment.cgi?id=143616&action=edit Similar issue, 3 messages reported as unread, but all are read I have probably the same or a similar issue; the 3 messages shown in the folder box cannot be found; I have refreshed the folder by now several times. Problem is already at least 6 months old. Akonadi was configured with postgres, mail account is office365 IMAP. If I knew how to debug it better, I would. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 445574] New: DBus Access to Refresh Button in KDE Connect
https://bugs.kde.org/show_bug.cgi?id=445574 Bug ID: 445574 Summary: DBus Access to Refresh Button in KDE Connect Product: kdeconnect Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: g...@g4b.org Target Milestone: --- Flags: corner_case+ SUMMARY *** KDE Connect sometimes loses connection over the network; I tracked it down to most likely being due to packet loss, which is induced by our WiFi situation (overlapping networks) which we can't change. Finding devices again sometimes takes several minutes, once the connection breaks. However, pressing "Refresh" in the KDE Connect Settings below the list of devices on the host usually fixes this problem instantly. However unfortunately, pressing the refresh button cannot be automated easily. I ask to simply expose this refresh Action via DBUS, if possible. This would allow a script that checks our usecase of using KDE Connect on a keyboard-less kiosk system to poll refresh, if no phone is connected every x sec, so we can at least reduce the outage time of network errors. *** STEPS TO REPRODUCE 1. Set up KDE Connect by adding IP Adress 2. Have bad WiFi Connection 3. Wait until connection is re-established SOFTWARE/OS VERSIONS Linux/KDE Plasma: latest Neon, however this issue persists since 3 years. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 373440] konsole --new-tab opens window instead
https://bugs.kde.org/show_bug.cgi?id=373440 Gabor changed: What|Removed |Added CC||ga...@splitter.hu --- Comment #44 from Gabor --- I am on manjaro XFCE konsole 21.04.3. In this version if "run all Konsole with single process" checked and first instance started with --new-tab, then another --new-tab works. This is an acceptable workaround. With this combination the dbus address is org.kde.konsole In other cases dbus-send --dest=$KONSOLE_DBUS_SERVICE --print-reply=literal --type=method_call /Windows/1 org.kde.konsole.Window.newSession works. and also works with --dest=org.kde.konsole-$KPID where $KPID is the pid of the konsole. Maybe the problem is that the dbus service is not the standard org.kde.konsole -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 431446] Blinking panels and window contents not refreshing
https://bugs.kde.org/show_bug.cgi?id=431446 Gabor changed: What|Removed |Added CC||ga...@splitter.hu --- Comment #12 from Gabor --- I have the same issue (chrome hw accel suspicious) I dont know if it is related, but I almost always have to switch fromo tty1 and back to tty1 because the whole screen freezes when laptop locked. intel i5 4210U -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429525] mouse wheel activate application if not grouped
https://bugs.kde.org/show_bug.cgi?id=429525 --- Comment #1 from Gabor --- I found this: https://bugs.kde.org/show_bug.cgi?id=327276 So it is "fixed" now:( Please add an option to work like as I described. -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 327276] Task Manager: grouped tasks not cyclic switchable by mouse wheel anymore
https://bugs.kde.org/show_bug.cgi?id=327276 Gabor changed: What|Removed |Added CC||ga...@splitter.hu --- Comment #7 from Gabor --- https://bugs.kde.org/show_bug.cgi?id=429525 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 429525] New: mouse wheel activate application if not grouped
https://bugs.kde.org/show_bug.cgi?id=429525 Bug ID: 429525 Summary: mouse wheel activate application if not grouped Product: plasmashell Version: 5.20.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: ga...@splitter.hu CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I am glad that finally in icons only task manager, if I use mouse wheel on grouped application, it is cycling trough only the instances of that application. My feature request is this option: If I use the mouse wheel on a non grouped application icon, than just activate that application. and don't cycle trough all applications. I think it makes a more consistent behavior. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 298775] Add search for tab functionality
https://bugs.kde.org/show_bug.cgi?id=298775 --- Comment #8 from Gabor --- Works with exact match, and I have not tried it more than about 10 tab. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 298775] Add search for tab functionality
https://bugs.kde.org/show_bug.cgi?id=298775 --- Comment #7 from Gabor --- (In reply to Nicolas Girard from comment #6) > (In reply to Gabor from comment #5) > > > > > I filed that bug when I wanted to achieve the same thing. Currently I have > > an awful workaround which activates the tabs one by one and gets the current > > title while it founds the searched tab. > > Yeah, I saw someone else getting that dirty here: > https://debianforum.de/forum/viewtopic.php?t=178041 and didn't feel like > trying. > > How bad does it feel with a few tens of tabs ? > I might give it a try after all, if you don't mind pasting your code. Here you have it: https://pastebin.com/7HFThb5a activates the tab if found else exits 0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 298775] Add search for tab functionality
https://bugs.kde.org/show_bug.cgi?id=298775 Gabor changed: What|Removed |Added CC||ga...@splitter.hu --- Comment #5 from Gabor --- (In reply to Nicolas Girard from comment #4) > > The only missing piece here is the ability to switch to the tab associated > > with a session number via D-bus. > > This would be achieved by fixing bug 422262. I filed that bug when I wanted to achieve the same thing. Currently I have an awful workaround which activates the tabs one by one and gets the current title while it founds the searched tab. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 Gabor changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #13 from Gabor --- I was thinking it will affect more user after that upgrade, but it is obvious now, it was only me. I was not able to reproduce it either, with a new user with the same custom panel settings, so I went to my .config dir as you suggested searching for broken config. And I found it. It turned out, kwinrulesrc had two rules, which I added as a workaround, to achive that newly opened window always open on the primary display. (one rule for all window, and the other for systray panels) I use a laptop so my display settings changes frequently between dual and single display and I use the external as primary when connected. The workaround worked well before that upgrade. I hope new kde version handle newly opened window placement better in my case :) Thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 --- Comment #10 from Gabor --- Created attachment 130866 --> https://bugs.kde.org/attachment.cgi?id=130866&action=edit systray panel opens in wrong corner -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 425335] New: Crash after re-enabling locked tab
https://bugs.kde.org/show_bug.cgi?id=425335 Bug ID: 425335 Summary: Crash after re-enabling locked tab Product: yakuake Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: h...@kde.org Reporter: g...@g4b.org Target Milestone: --- Application: yakuake (3.0.5+) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 4.15.0-101-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: I had an SSH session open in a tab (which was probably stale to an internet change) that tab was marked as "do not close" and "keyboard input disabled" I deactivated those flags and tried to write into the tab, whole yakuake crashed. -- Backtrace: Application: Yakuake (yakuake), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f84bd86e300 (LWP 1541))] Thread 4 (Thread 0x7f84977ce700 (LWP 1631)): #0 0x7f84b37919f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x56352eedd8e8) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x56352eedd898, cond=0x56352eedd8c0) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x56352eedd8c0, mutex=0x56352eedd898) at pthread_cond_wait.c:655 #3 0x7f849cd07ecb in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f849cd07ac7 in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f84b378b6db in start_thread (arg=0x7f84977ce700) at pthread_create.c:463 #6 0x7f84b7bd8a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f84a4b14700 (LWP 1607)): #0 0x7f84b7bc71c4 in __GI___libc_read (fd=7, buf=0x7f84a4b13b60, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7f84b19d82b0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f84b19930b7 in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f84b1993570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f84b19936dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7f84b85327cb in QEventDispatcherGlib::processEvents (this=0x7f8498000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #6 0x7f84b84d1d2a in QEventLoop::exec (this=this@entry=0x7f84a4b13d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #7 0x7f84b82e2757 in QThread::exec (this=) at thread/qthread.cpp:536 #8 0x7f84b9aea555 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7f84b82e3c2c in QThreadPrivate::start (arg=0x7f84b9d62da0) at thread/qthread_unix.cpp:342 #10 0x7f84b378b6db in start_thread (arg=0x7f84a4b14700) at pthread_create.c:463 #11 0x7f84b7bd8a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 2 (Thread 0x7f84a8444700 (LWP 1589)): #0 0x7f84b7bcbcf9 in __GI___poll (fds=0x7f84a8443ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f84b5ca8747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #2 0x7f84b5caa36a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1 #3 0x7f84ab019fd0 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #4 0x7f84b82e3c2c in QThreadPrivate::start (arg=0x56352ed47610) at thread/qthread_unix.cpp:342 #5 0x7f84b378b6db in start_thread (arg=0x7f84a8444700) at pthread_create.c:463 #6 0x7f84b7bd8a3f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 1 (Thread 0x7f84bd86e300 (LWP 1541)): [KCrash Handler] #4 QtPrivate::indexOf (from=0, u=@0x7ffd21303de8: 0x56352f3b9b60, list=...) at ../../include/QtCore/../../src/corelib/tools/qlist.h:1025 #5 QList::indexOf (from=0, t=@0x7ffd21303de8: 0x56352f3b9b60, this=0x7f84b7ea3288 ) at ../../include/QtCore/../../src/corelib/tools/qlist.h:1009 #6 QList::removeAll (this=0x7f84b7ea3288 , _t=@0x7ffd21303de8: 0x56352f3b9b60) at ../../include/QtCore/../../src/corelib/tools/qlist.h:919 #7 0x7f84b93fa527 in QWidget::removeAction (this=0x56352f399a20, action=) at kernel/qwidget.cpp:3175 #8 0x7f84bc213549 in KActionCollection::removeAssociatedWidget(QWidget*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #9 0x7f84bc25c96b in KXMLGUIClient::prepareXMLUnplug(QWidget*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #10 0x7f84bc261101 in KXMLGUIFactory::removeClient(KXMLGUIClient*) () from /usr/lib/x86_64-linux-gnu/libKF5XmlGui.so.5 #11 0x7f848e5661c4 in Konsole::SessionController::~SessionController() () from /usr/lib/x86_64-linux-gnu/libkonsoleprivate.so.20 #12 0x7f848e566379 in Konsole::SessionController::~SessionController() () from /usr/lib/
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 --- Comment #8 from Gabor --- (In reply to Gabor from comment #7) > I just noticed, that my calendar widget (org.kde.plasma.calendar.wl) also > opens the calendar on the left, while the clock widget opens on the right > place on the right. And now it's not. My widgets are in vertical order but it seems the opening panels try to go from left to right. And I can't reproduce the state when the clock opened in right. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 --- Comment #7 from Gabor --- I just noticed, that my calendar widget (org.kde.plasma.calendar.wl) also opens the calendar on the left, while the clock widget opens on the right place on the right. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 --- Comment #6 from Gabor --- Created attachment 130377 --> https://bugs.kde.org/attachment.cgi?id=130377&action=edit click on kde connect opens in top left -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 --- Comment #4 from Gabor --- Can you please delete the attachment, I accidentally left my ip on the screenshot, and I can't delete it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 --- Comment #3 from Gabor --- Created attachment 130360 --> https://bugs.kde.org/attachment.cgi?id=130360&action=edit systray wrong corner Maybe the problem is, that I have two panels at the top, I switched from my custom theme so you can see the line on the task switcher's left. The screenshot was taken on dual monitor, but the issue is the same on one display setup (I cropped the left display later because of the attach size limit). Tried to move the left one, stretch the right to full width, the result is the same. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424489] New: systray panels open in wrong corner
https://bugs.kde.org/show_bug.cgi?id=424489 Bug ID: 424489 Summary: systray panels open in wrong corner Product: plasmashell Version: 5.19.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: ga...@splitter.hu Target Milestone: 1.0 SUMMARY After latest upgrade: I have my systray on the top right corner. When i click on network or bluetooth or anything the panel opens in the top left, when I click other icon it comes to the right place (where it should open) to the right. So it gets to the right place only when switching and it always opens left. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.19.3 KDE Frameworks Version: 5.72 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 423262] copy-paste not working in konsole
https://bugs.kde.org/show_bug.cgi?id=423262 Gabor changed: What|Removed |Added CC||ga...@splitter.hu --- Comment #1 from Gabor --- did you try a support forum before posted here? how do you try to paste? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423102] New: mouse cursor loads before display layout at start causing some flickering on multi monitor
https://bugs.kde.org/show_bug.cgi?id=423102 Bug ID: 423102 Summary: mouse cursor loads before display layout at start causing some flickering on multi monitor Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ga...@splitter.hu CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY I have an extend to right display setup. The sddm is mirroring displays which is ok. When logging in plasma loads the cursor theme then loads the display setup, so first i have two mouse pointer, than some flickering and one comes back STEPS TO REPRODUCE 1. use extended display setup 2. login 3. EXPECTED RESULT set the display setup, than display mouse cursor. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70 Qt Version: 5.15 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 423064] "Win" instead of "Meta" in keyboard settings
https://bugs.kde.org/show_bug.cgi?id=423064 Gabor changed: What|Removed |Added CC||ga...@splitter.hu --- Comment #1 from Gabor --- I don't think it's a bug. I don't really understand this Meta/Win/Super concept, just know it always means my Win key. But on this advanced tab if you open the "Alt and Win behavior" you can see for example "Meta is mapped to Win" option. So I think they use "Win" here not as a mistake. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 423092] New: auto lockscreen with allow unlocking for X sec behavior useless when other tty used
https://bugs.kde.org/show_bug.cgi?id=423092 Bug ID: 423092 Summary: auto lockscreen with allow unlocking for X sec behavior useless when other tty used Product: kscreenlocker Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: ga...@splitter.hu CC: bhus...@gmail.com Target Milestone: --- SUMMARY I have set lockscreen auto after 1min and allow unlocking without password for 4sec. Now If I am on an other tty for more than one min, after I switch back, I can see the desktop, then it locks itself, and I can unlock it easily within the 4sec without password (even after 2min). STEPS TO REPRODUCE 1. set lockscreen auto after 1min and allow unlocking without password for 4sec 2. switch to other tty for example ctrl+alt+F2 3. wait at least 1 min and switch back for example alt+f1 OBSERVED RESULT plasma just locks and unlocks EXPECTED RESULT lock in the background not when it's activated, or at least don't automatically unlock if 60+4 sec already spent. SOFTWARE/OS VERSIONS. KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.15.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423074] Mouse cursor theme partially changes
https://bugs.kde.org/show_bug.cgi?id=423074 --- Comment #1 from Gabor --- I changed theme 2 times, just noticed the lock screen theme is also different. So I currently have 3 themes at the same time. And plasmashell --replca doesn't resolves it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 423074] New: Mouse cursor theme partially changes
https://bugs.kde.org/show_bug.cgi?id=423074 Bug ID: 423074 Summary: Mouse cursor theme partially changes Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: ga...@splitter.hu CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY After changing mouse theme it doesn't work if the mouse over some elements for example logout screen, desktop and somewhere in the panel. Doesn't matter how many times you change theme, on the mentioned elements the cursor remains the same, as it was when plasma was started. plasmashell --replace, resolves it. STEPS TO REPRODUCE 1. Change Cursor theme under Settings -> Cursor 2. examine the cursor over desktop, logout screen OBSERVED RESULT cursor switches back to the theme which was set at start SOFTWARE/OS VERSIONS KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70 Qt Version: 5.15 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 421371] UX: Disable WIFI and Airplane Mode Need Explanation
https://bugs.kde.org/show_bug.cgi?id=421371 Gabor changed: What|Removed |Added CC||ga...@splitter.hu --- Comment #2 from Gabor --- I felt this confusion first, but only the first time. I just opened it now, and it's fine. Maybe the airplane mode checkbox is too close to the Wifi, would be better in the center. And as this is affect bluetooth too, I think the bluetooth panel is missing the airplane mode switch -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421436] Cannot logout of plasma
https://bugs.kde.org/show_bug.cgi?id=421436 Gabor changed: What|Removed |Added CC||ga...@splitter.hu --- Comment #1 from Gabor --- I experienced it, not for first try but if I am testing and login/out a few times have to kill kwin with -9. STEPS TO REPRODUCE 1. Log in 2. Log out 3. Goto 1 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422663] lock screen flickers on unlock
https://bugs.kde.org/show_bug.cgi?id=422663 --- Comment #2 from Gabor --- *** Bug 419364 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 419364] lockscreen backflashes after unlocking
https://bugs.kde.org/show_bug.cgi?id=419364 Gabor changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Gabor --- *** This bug has been marked as a duplicate of bug 422663 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422663] New: lock screen flickers on unluck
https://bugs.kde.org/show_bug.cgi?id=422663 Bug ID: 422663 Summary: lock screen flickers on unluck Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: ga...@splitter.hu CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY After unlocking: the lock screen disappears and the desktop appears immediately, than the lockscreen covers it with some opacity, and fades out. This causes a flickering on unlocking. You can see it if you set the Animation Speed to the minimum in plasma settings under Workspace Behavior. STEPS TO REPRODUCE 1. set the Animation Speed to the minimum in plasma settings under Workspace Behavior. 2. lock the screen 3. unlock EXPECTED RESULT even would be better without animation. SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 422262] New: dbus /Windows/1 org.kde.konsole.Window.setCurrentSession doesn't changes session
https://bugs.kde.org/show_bug.cgi?id=422262 Bug ID: 422262 Summary: dbus /Windows/1 org.kde.konsole.Window.setCurrentSession doesn't changes session Product: konsole Version: 20.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: ga...@splitter.hu Target Milestone: --- SUMMARY Maybe I am wrong and in this case I am sorry. Trying to change the active Session in Konsole by Session id with: dbus-send --dest=org.kde.konsole --type=method_call /Windows/1 org.kde.konsole.Window.setCurrentSession int32:2 simply doesn't work, just the current session lost it's focus. however the following works: dbus-send --dest=org.kde.konsole --type=method_call --print-reply=literal /Windows/1 org.kde.konsole.Window.nextSession STEPS TO REPRODUCE 1. open konsole with at least two tabs 2. select other than second 3. try to move to the second tab with the above (first) command OBSERVED RESULT active session doesn't changes just current session lost it's focus (outlined cursor) EXPECTED RESULT change the session SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 419609] New: previously exported openvpn.conf importing fails on tls-auth key direction
https://bugs.kde.org/show_bug.cgi?id=419609 Bug ID: 419609 Summary: previously exported openvpn.conf importing fails on tls-auth key direction Product: plasma-nm Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: ga...@splitter.hu Target Milestone: --- STEPS TO REPRODUCE 1. export an openvpn connection which have this line: "tls-auth some.key 1" 2. rename the file 3. import it 4. try to connect OBSERVED RESULT in the log: NetworkManager[69064]: Options error: Unknown key direction ' 1' -- must be '0' or '1' in the settings it shows 1 after set to 0 and back to 1 it started working -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419364] New: lockscreen backflashes after unlocking
https://bugs.kde.org/show_bug.cgi?id=419364 Bug ID: 419364 Summary: lockscreen backflashes after unlocking Product: plasmashell Version: 5.18.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: ga...@splitter.hu CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY After enter the password on lockscreen, my desktop comes in but the lockscreen flickers back for a split second STEPS TO REPRODUCE 1. lock screen 2. unlock the screen SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.18.3 KDE Frameworks Version: 5.68.0 Qt Version: 5.14.1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 416900] New: akonadi crash when try to move imap folder
https://bugs.kde.org/show_bug.cgi?id=416900 Bug ID: 416900 Summary: akonadi crash when try to move imap folder Product: Akonadi Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: g...@g4b.org Target Milestone: --- Application: akonadiserver (5.13.1 (19.12.1)) Qt Version: 5.13.2 Frameworks Version: 5.65.0 Operating System: Linux 4.15.0-74-generic x86_64 Distribution: KDE neon User Edition 5.17 -- Information about the crash: - What I was doing when the application crashed: I was moving a folder into a newly created subfolder on Office365 imap account. The folder had a lot of messages (Sentry logs) I also clicked on the other folder while the action was underway (so it might be unrelated to the move-action) -- Backtrace (Reduced): #6 0x7f19d4cbf368 in qHash(QString const&, unsigned int) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x560e186d665b in QHash::findNode (this=this@entry=0x560e193a3528, akey=..., ahp=ahp@entry=0x0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:934 #8 0x560e186d6a9a in QHash::remove (this=this@entry=0x560e193a3528, akey=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qhash.h:806 #9 0x560e186d3e3f in Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x560e193a34f0, request=0x7f1968021470, errorMsg=...) at ./src/server/storage/itemretrievalmanager.cpp:192 [...] #11 0x560e187242f4 in Akonadi::Server::AbstractItemRetrievalJob::requestCompleted (this=this@entry=0x7f19a8006c00, _t1=, _t2=...) at ./obj-x86_64-linux-gnu/src/server/libakonadiserver_autogen/5XLNPBDXWK/moc_itemretrievaljob.cpp:136 Possible duplicates by query: bug 416379, bug 416113, bug 415634, bug 414966, bug 414229. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwindowsystem] [Bug 412995] New: Custom Shortcut Group condition doesn't notice title change
https://bugs.kde.org/show_bug.cgi?id=412995 Bug ID: 412995 Summary: Custom Shortcut Group condition doesn't notice title change Product: frameworks-kwindowsystem Version: 5.15.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdelibs-b...@kde.org Reporter: ga...@splitter.hu Target Milestone: --- SUMMARY Not sure it's a bug, maybe it is a feature request. I would like to use mouse gestures in browser except on one tab. But the custom shortcut group condition didn't respect title changes. STEPS TO REPRODUCE 1. In Settings -> Shortcuts -> Custom Shortcuts Create a group, add coniditon with a "window class contain" and a "title doesn't contain" rule to match you borswer class and title on a specific site. 2. add some shortcut to the group 3. try the shortcuts while changing tab (so the title changes) in browser OBSERVED RESULT The match decided when I hit the apply button on settings, so the gestures working on every tab if I was not on that site, and don't work on any tab if the site was active, even when I switch to other tab and the title changes. EXPECTED RESULT If I add a title related condition, it should monitor the title changes, so the shortcut group activates/deactivates on title changes. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: kubuntu 19.04 (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56 Qt Version: 5.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412823] New: Please add a refresh function.
https://bugs.kde.org/show_bug.cgi?id=412823 Bug ID: 412823 Summary: Please add a refresh function. Product: kdeconnect Version: unspecified Platform: Other OS: Android 9.x Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: g...@g4b.org Target Milestone: --- SUMMARY If your device is not found, closing and reopening the app, lately even force stop does not work. I have to use another phone to connect. Or restart my phone. Would be awesome if there was a refresh button which manually starts to search for the currently opened device E.g. if I open KDE connect from another room and walk into the area I could connect -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 Gabor Körber changed: What|Removed |Added CC|g...@g4b.org | -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #88 from Gabor Körber --- I can also confirm, that Rik's packages fix the issue for me in 5.14.5 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981
--- Comment #79 from Gabor Körber ---
I had no problems with installing the packages, however, as András, my main
issue was that it got stuck at kdesrc-build --initial-setup and also at
kdesrc-build discover --include-dependencies:
Unescaped left brace in regex is illegal here in regex; marked by <-- HERE in
m/(\${ <-- HERE MODULE})|(\$MODULE\b)/ at /usr/bin/kdesrc-build line 4759.
which leads to ~/kde/src not existing, so i can't continue.
Nate, did your step-by-step guide include ignoring that one commit? as i do not
really see that in particular.
I am happy to test this otherwise, i will try to restrain myself from upgrading
apt too frequently, so I have some packages in the queue. Otherwise I AM a bit
puzzled the release policies do not allow bugfix releases to be included into
an older release branch, but I am also pretty sure, the deb folks can do their
own hotfix packages, given the fix is in some branch / diff / sth.
--
You are receiving this mail because:
You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 --- Comment #67 from Gabor Körber --- I do not have that file either, only the ones for gtk3 and gtk2 themes. Thank you very much Nate, and all helpers, for the good news however, I suppose I personally can wait until next release. As for the "non tech user" basic functionality like upgrades are theoretically quite crucial, even if it might look like a minor feat, so it is unfortunate it can't be fixed upstream; however, since that user would not be able to install the upgrade anyway, as his button does not work, I guess it makes little difference :) Will confirm once the fix takes effect. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 399981] Both "check for updates" and "update all" buttons are disabled even when updates are available
https://bugs.kde.org/show_bug.cgi?id=399981 Gabor Guzmics changed: What|Removed |Added CC||g...@g4b.org --- Comment #47 from Gabor Guzmics --- I have this bug since last year November. It never resolved. Updating through apt or other means works fine. I kinda find it disgusting. The software updater should be top priority, folks. SOFTWARE VERSIONS Operating System: KDE Neon, updated daily. KDE Framework Version: 5.54.0 Qt: 5.11.2 Discover: 5.14.5 -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 398092] Comic Strip causes plasmashell CPU spike, does not load comic
https://bugs.kde.org/show_bug.cgi?id=398092 --- Comment #1 from Gabor Guzmics --- Although to be honest, plasmashell tends to go nuts with cpu in many cases, so in the end maybe it is finally time to overwork how it handles widget authority. It's nuts one malfunctioning widget or an animation with too many redraws can cause it to go full cpu usage. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 398092] New: Comic Strip causes plasmashell CPU spike, does not load comic
https://bugs.kde.org/show_bug.cgi?id=398092 Bug ID: 398092 Summary: Comic Strip causes plasmashell CPU spike, does not load comic Product: kdeplasma-addons Version: 5.13.4 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Comic Applet Assignee: notm...@gmail.com Reporter: g...@g4b.org Target Milestone: --- For me, after resuming from standby in the morning this happens most often. The comic strip starts to show it is busy, obviously trying to update to the new comics. However, it just gets stuck in that update phase, causing plasmashell to go mental with CPU usage. It never resolves from this, and it never fetches new comics. Switching the comic or going back one strip can solve the issue, since that cancels the retrieval. There is sadly no "reload strip now" functionality for manually running the reload. It feels like a loop is getting stuck with endless errors, immediately retrying something, without sleeps, and no abort counter. I have no idea how to log this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370003] Performance issues (laggy animations, stuttering keyboard input handling, severe frame drops in videos) after using plasmashell for a few days
https://bugs.kde.org/show_bug.cgi?id=370003 --- Comment #12 from Gabor Guzmics --- Joan, since you mention this, are you sure it is only plasmashell in your case that is slowing the system? One of my two machines I work with and mentioned, having this plasmashell bug, had 4GB RAM and showed symptoms of kswapd0 starting to completely freak out even if there was still RAM and swap space left, with short spikes in top - but it was not swapping. I fixed that issue with upgrading to 8GB, and assume its something that came up in the kernel in 2018 (for me as neon user, its ubuntu), as the issue started after an upgrade. Since both things could happen at the same time, I also first blamed the plasmashell issue. However the other laptop has 16GB RAM; far from being filled. The issue of plasmashell eating CPU happens even then. Even further, when plasmashell eats CPU, as it's an 8th gen i7, I actually only realize it through Cpu meters. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 370003] Performance issues (laggy animations, stuttering keyboard input handling, severe frame drops in videos) after using plasmashell for a few days
https://bugs.kde.org/show_bug.cgi?id=370003 Gabor Guzmics changed: What|Removed |Added CC||g...@g4b.org --- Comment #10 from Gabor Guzmics --- I have the same issues with kde under neon (up2date), and I had it in ubuntu before, on two laptops, one lenovo x1 and one dell latitude. By now I am very sure by now, the issue is triggered by suspending and waking the system. As it is not immediately showing up every time, one might suspect other causes first, especially since usually it comes up after leaving the machine on for long times (where one might forget the suspends inbetween) I did patch the BusyIndicator entry in NotificationIcon.qml in the past on one of those laptops, as it is one of the circulating proposed fixes for plasmashell cpu usage, and one of my laptops does neither use dual screen nor any animated plasmoids. The only animated thing is the icon of sparkleshare for me. turning it off did not help however. suspending and resuming almost always triggers the cpu spike. it totally blocks at least one core for me, resulting in plasmashell eating up to 128% cpu. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388510] shell crash
https://bugs.kde.org/show_bug.cgi?id=388510 --- Comment #1 from gabor --- cairo-dock was involved -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 388510] New: shell crash
https://bugs.kde.org/show_bug.cgi?id=388510 Bug ID: 388510 Summary: shell crash Product: plasmashell Version: 5.8.8 Platform: Neon Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: dynamicsi...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 109657 --> https://bugs.kde.org/attachment.cgi?id=109657&action=edit dragging from the kicker app launcher menu just submitting, because i think plasma is the future so anything to help -- You are receiving this mail because: You are watching all bug changes.
[plasma4] [Bug 345293] KDE Shell (plasma shell) Crashes when moving System Info widget from one monitor to another.
https://bugs.kde.org/show_bug.cgi?id=345293 gabor changed: What|Removed |Added CC||dynamicsi...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 388467] New: failed to migrate from schema 7 to 8
https://bugs.kde.org/show_bug.cgi?id=388467 Bug ID: 388467 Summary: failed to migrate from schema 7 to 8 Product: digikam Version: 5.5.0 Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Database-Schema Assignee: digikam-bugs-n...@kde.org Reporter: orrm...@gmail.com Target Milestone: --- QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-orrmany' digikam.general: AlbumWatch use QFileSystemWatcher digikam.general: Database Parameters: Type: "QMYSQL" DB Core Name: "digikam" DB Thumbs Name: "thumbnails-digikam" DB Face Name: "" Connect Options: "" Host Name:"localhost" Host port:3306 Internal Server: false Internal Server Path: "/home/orrmany/.local/share/digikam/" Internal Server Serv Cmd: "mysqld" Internal Server Init Cmd: "mysql_install_db" Username: "digikam" Password: "X" digikam.dbengine: Loading SQL code from config file "/usr/share/digikam/database/dbconfig.xml" digikam.dbengine: Checking XML version ID => expected: 3 found: 3 digikam.coredb: Core database: running schema update digikam.coredb: Core database: have a structure version 7 digikam.coredb: Core database: makeUpdates 7 to 8 digikam.dbengine: Failure executing query: "" Error messages: "QMYSQL: A lekérdezés nem hajtható végre" "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IF EXISTS identifier' at line 2" 1064 2 Bound values: () digikam.dbengine: Error while executing DBAction [ "UpdateSchemaFromV7ToV8" ] Statement [ "ALTER TABLE AlbumRoots\n DROP INDEX IF EXISTS identifier;" ] digikam.coredb: Core database: schema update to V 8 failed! digikam.coredb: Core database: cannot process schema initialization -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 330676] PIcture download
https://bugs.kde.org/show_bug.cgi?id=330676 Gabor Fekete changed: What|Removed |Added CC||gabor.fek...@flamma.eu -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 330676] PIcture download
https://bugs.kde.org/show_bug.cgi?id=330676 --- Comment #11 from Gabor Fekete --- Created attachment 96300 --> https://bugs.kde.org/attachment.cgi?id=96300&action=edit New crash information added by DrKonqi digikam (4.0.0) on KDE Platform 4.14.2 using Qt 4.8.6 - What I was doing when the application crashed: The program crashed each time I tried to download pictures from Nikon D3200 -- Backtrace (Reduced): #6 Digikam::Album::globalID (this=0x0) at /build/buildd/digikam-4.0.0/core/digikam/album/album.cpp:227 #7 0x007d3d43 in Digikam::ImportUI::slotDownload (this=0x423e040, onlySelected=, deleteAfter=, album=0x0) at /build/buildd/digikam-4.0.0/core/utilities/importui/main/importui.cpp:1475 #8 0x007d4d26 in slotDownloadSelected (this=) at /build/buildd/digikam-4.0.0/core/utilities/importui/main/importui.cpp:1395 #9 Digikam::ImportUI::qt_static_metacall (_o=0x423e040, _c=69889032, _id=0, _a=0x10) at /build/buildd/digikam-4.0.0/obj-x86_64-linux-gnu/core/utilities/importui/importui.moc:199 [...] #11 0x7f5bec5b7a62 in QAction::triggered (this=this@entry=0x5a81b40, _t1=false) at .moc/release-shared/moc_qaction.cpp:276 -- You are receiving this mail because: You are watching all bug changes.
