[konsole] [Bug 474848] Toolbar items sometimes move to weird places when creating split view
https://bugs.kde.org/show_bug.cgi?id=474848 --- Comment #4 from Alfonso Murolo --- Hi, I have started a merge request to solve the two aforementioned strange behaviours. https://invent.kde.org/utilities/konsole/-/merge_requests/981 Since one of my changes removes a detail of the signal that handles the change of the active view, I'd be happy to get some feedback if I need to study an alternative approach to this one. Cheers Alfonso -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 474848] Toolbar items sometimes move to weird places when creating split view
https://bugs.kde.org/show_bug.cgi?id=474848 Alfonso Murolo changed: What|Removed |Added CC||almur@gmail.com --- Comment #1 from Alfonso Murolo --- Hi Alois, Yeah I can replicate it. The whole thing seems kinda weird to me in other cases too, such as when the hamburger icon sometimes seems to disappear: 1. Open Konsole, hamburger icon is visible top right 2. Split vertically. Split right is preselected, hamburger icon is gone. 3. Focus the split left (original). Hamburger icon is back. 4. Split vertically again. 5. Now new preselected tab is the first of three. Hamburger icon is gone. 6. Focus center split. 7. Hamburger icon is back. 8. Close center split. 9. No split offers a hamburger icon any longer. Does this behaviour seem erratic only to me? Or is there some kind of logic behind it? If it needs to be reworked/fixed, I'd be happy to look into it. Cheers Alfonso -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 476051] Invisible splitter (black on black) when using Dark Theme
https://bugs.kde.org/show_bug.cgi?id=476051 Alfonso Murolo changed: What|Removed |Added CC||almur@gmail.com --- Comment #5 from Alfonso Murolo --- Hey Andrew, does this persist for you in KDE6 with Breeze Dark? For me it is definitely visible now. Cheers Alfonso -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 426276] Split view: change view shortcuts
https://bugs.kde.org/show_bug.cgi?id=426276 --- Comment #5 from Alfonso Murolo --- (In reply to Bernd Steinhauser from comment #4) > That's remappable, it's called "Focus Above/Below/Left/Right Terminal". > > What at least I meant was something like "Cycle Through Terminals in Current > View". > That's of course less specific than the one with arrows, where you can > specify the direction, but I rarely split a view into more than two > terminals, so it'd be a better fit for me. Interesting, is that also supported in tmux? (I do not have a lot of experience with it). What I am currently unsure about your formulation, is that your concept implies a linearization and a consequent sorting of the splitted views, in order to cycle through them in a predictable manner. If this feature is already implemented somewhere in a manner which is generally accepted, that would be good to know to take it as reference. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 426276] Split view: change view shortcuts
https://bugs.kde.org/show_bug.cgi?id=426276 Alfonso Murolo changed: What|Removed |Added CC||almur@gmail.com --- Comment #3 from Alfonso Murolo --- Hello sacha and Bernd, if I have not misunderstood your request, after having a look at the source code of the Konsole ViewManager, I believe this feature exists already. You can try by creating an arbitrarily complex split view and move with the default hotkeys: CTRL + SHIFT + Arrow [Up, Down, Left, Right] I am currently unsure if there is a possibility to remap this key combination. Please let me know if that differs from what you expected. Cheers Alfonso -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 469249] Cannot create a new tab and split view when current tab has used SSH
https://bugs.kde.org/show_bug.cgi?id=469249 Alfonso Murolo changed: What|Removed |Added CC||almur@gmail.com --- Comment #2 from Alfonso Murolo --- Is /usr/bin/zsh the shell on your OpenBSD box by any chance? I have tried to replicate this on my Arch box, but failed to succeed for now. Admittedly though i only tried to ssh to myself for these first tests. I may set up a more complex test environment in the next days though. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469271] Double click on folder from desktop opens not only that folder but also random unrelated ones
https://bugs.kde.org/show_bug.cgi?id=469271 Alfonso Murolo changed: What|Removed |Added CC||almur@gmail.com --- Comment #1 from Alfonso Murolo --- I could reproduce this on Arch. It is, to my eyes, kind-of intended since in the settings of Dolphin there is one which seems to control exactly this. I am wondering however what is the rationale behind a *default* of reopening the tabs of the last process.. can anybody shed some light? I admit I find this behaviour slightly odd too. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463302] "New tab" in Konsole opens a new window
https://bugs.kde.org/show_bug.cgi?id=463302 --- Comment #5 from Alfonso Murolo --- I took the liberty of markng it as duplicate directly. Please let me know if that is somehow inappropriate for the process. -- 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 Alfonso Murolo changed: What|Removed |Added CC||enric...@hotmail.com --- Comment #51 from Alfonso Murolo --- *** Bug 463302 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463302] "New tab" in Konsole opens a new window
https://bugs.kde.org/show_bug.cgi?id=463302 Alfonso Murolo changed: What|Removed |Added Resolution|--- |DUPLICATE Status|CONFIRMED |RESOLVED --- Comment #4 from Alfonso Murolo --- *** This bug has been marked as a duplicate of bug 373440 *** -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463302] "New tab" in Konsole opens a new window
https://bugs.kde.org/show_bug.cgi?id=463302 Alfonso Murolo changed: What|Removed |Added CC||almur@gmail.com --- Comment #3 from Alfonso Murolo --- Seems to me a duplicate of https://bugs.kde.org/show_bug.cgi?id=373440 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468745] Konsole Context Menu: Open File Manager Option Fails to Open
https://bugs.kde.org/show_bug.cgi?id=468745 Alfonso Murolo changed: What|Removed |Added CC||almur@gmail.com --- Comment #3 from Alfonso Murolo --- Hi - I have attempted to replicate this bug in Arch Linux ARM with wayland. I could not reproduce it. Did you by any chance miss to install kde applications? Is dolphin installed? Do you have another file manager? The following output could be replicated on my machine and seems to be unrelated to the reported behaviour; in my case, file manager opens normally. kf.service.services: KApplicationTrader: mimeType "x-scheme-handler/file" not found -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 457059] New: KDE Discover crashes when opening com.discordapp.Discord.flatpakref from Flathub
https://bugs.kde.org/show_bug.cgi?id=457059 Bug ID: 457059 Summary: KDE Discover crashes when opening com.discordapp.Discord.flatpakref from Flathub Product: Discover Version: 5.24.4 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: alfonsojon1...@gmail.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.24.4) Qt Version: 5.15.2 Frameworks Version: 5.90.0 Operating System: Linux 5.14.21-150400.24.11-default x86_64 Windowing System: X11 Distribution: "openSUSE Leap 15.4" DrKonqi: 5.24.4 [KCrashBackend] -- Information about the crash: - What I was doing when the application crashed: Trying to install Discord from Flathub. I was successful in installing Discord through the terminal; I only had issues when opening the .flatpakref file from Flathub. After installing Discord through the terminal using the command line flatpak command, the .flatpakref file opens properly with KDE Discover. I am unable to reproduce this issue once this was performed. My system was a fresh installation of OpenSUSE Leap 15.4 before this change. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Segmentation fault [KCrash Handler] #4 g_type_check_instance_is_fundamentally_a (type_instance=type_instance@entry=0x7faf608729b0, fundamental_type=fundamental_type@entry=80) at ../gobject/gtype.c:4093 #5 0x7fafd7cad633 in g_object_ref (_object=0x7faf608729b0) at ../gobject/gobject.c:3443 #6 0x7faf93dd5e29 in FlatpakResource::FlatpakResource (this=0x55bcfdba4e00, component=..., installation=0x7faf80012210, parent=) at /usr/src/debug/discover-5.24.4-bp154.1.44.x86_64/libdiscover/backends/FlatpakBackend/FlatpakResource.cpp:52 #7 0x7faf93de253b in FlatpakBackend::addAppFromFlatpakRef (this=0x55bcf5121e90, url=..., stream=0x55bcf517c4f0) at /usr/src/debug/discover-5.24.4-bp154.1.44.x86_64/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:730 #8 0x7faf93dea9b2 in FlatpakFetchRemoteResourceJob::processFile (this=0x55bcf517c740, fileUrl=...) at /usr/src/debug/discover-5.24.4-bp154.1.44.x86_64/libdiscover/backends/FlatpakBackend/FlatpakBackend.cpp:297 #9 0x7fafde0c8cfb in QObject::event (this=0x55bcf517c4f0, e=0x55bcf517cf20) at kernel/qobject.cpp:1314 #10 0x7fafe05093ac in QApplicationPrivate::notify_helper (this=this@entry=0x55bcf4813400, receiver=receiver@entry=0x55bcf517c4f0, e=e@entry=0x55bcf517cf20) at kernel/qapplication.cpp:3632 #11 0x7fafe05101a0 in QApplication::notify (this=0x7ffefd9b6e50, receiver=0x55bcf517c4f0, e=0x55bcf517cf20) at kernel/qapplication.cpp:3156 #12 0x7fafde094ac3 in QCoreApplication::notifyInternal2 (receiver=0x55bcf517c4f0, event=0x55bcf517cf20) at kernel/qcoreapplication.cpp:1064 #13 0x7fafde094c9e in QCoreApplication::sendEvent (receiver=receiver@entry=0x55bcf517c4f0, event=event@entry=0x55bcf517cf20) at kernel/qcoreapplication.cpp:1462 #14 0x7fafde0974e1 in QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x55bcf481f580) at kernel/qcoreapplication.cpp:1821 #15 0x7fafde097a68 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1680 #16 0x7fafde0f7a33 in postEventSourceDispatch (s=0x55bcf48e6610) at kernel/qeventdispatcher_glib.cpp:277 #17 0x7fafd89ab7fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #18 0x7fafd89abba0 in ?? () from /usr/lib64/libglib-2.0.so.0 #19 0x7fafd89abc2c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #20 0x7fafde0f70dc in QEventDispatcherGlib::processEvents (this=0x55bcf48ea0c0, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #21 0x7fafde09333a in QEventLoop::exec (this=this@entry=0x7ffefd9b6d70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:232 #22 0x7fafde09cb37 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1375 #23 0x55bcf4016c89 in main (argc=, argv=) at /usr/src/debug/discover-5.24.4-bp154.1.44.x86_64/discover/main.cpp:217 [Inferior 1 (process 17176) detached] The reporter indicates this bug may be a duplicate of or related to bug 442709. Possible duplicates by query: bug 449277, bug 442709, bug 440877. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456803] Plasma crashes after screen inactivity
https://bugs.kde.org/show_bug.cgi?id=456803 --- Comment #5 from Alfonso Murolo --- Created attachment 150748 --> https://bugs.kde.org/attachment.cgi?id=150748=edit journalctl log In this workflow, I locked the computer manually and turned off both screens myself. Then waited for some seconds, and turned them back on at the same time. Plasma was gone, wallpaper was gone, and it seems it found itself in timeout, killed itself and restarted - in a total of almost 1 minute downtime. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456803] Plasma crashes after screen inactivity
https://bugs.kde.org/show_bug.cgi?id=456803 Alfonso Murolo changed: What|Removed |Added Resolution|WAITINGFORINFO |BACKTRACE --- Comment #4 from Alfonso Murolo --- (In reply to Nate Graham from comment #3) > If it's not crashing, what is it doing? I'd say it's a good question :-) I will try to replicate the crash behaviour where I get the crash dialog too. In that case, the hard reset is not necessary and I am able to get back to the desktop with a crashed plasmashell and a crash dialog welcoming me. Plasma is gone, but will eventually restart and so the session is recovered. In this other case which just happened, the logs in journalctl are all I am able to find for now of what is happening. Is there some other log which is plasma specific which I could browse? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456803] Plasma crashes after screen inactivity
https://bugs.kde.org/show_bug.cgi?id=456803 --- Comment #2 from Alfonso Murolo --- Hi Nate, thanks for the instructions. It just happened again (I could also replicate it by let it lock for inactivity and turn off the screens directly) and I had prepared my distro to get a dump with debug symbols. Sadly, it seems that it is not just "crashing" - plasmashell is still alive, printing those errors to journalctl until I hard reset. Exactly the same ones i wrote before. Is there a way I can provide more info even if plasmashell does not exactly 'crash' all the time such as in this case? Other times, I am able to see the actual crash if I manage to log back in and plasmashell is gone - I see the crash dialog and so on. As soon as I manage to replicate that, I will look to retrieve a trace with coredumpctl (I have a whole bunch of those in the list from the recent past, but I am not sure anymore if they are from an event I am describing in this issue or something else). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456803] New: Plasma crashes after screen inactivity
https://bugs.kde.org/show_bug.cgi?id=456803 Bug ID: 456803 Summary: Plasma crashes after screen inactivity Product: plasmashell Version: 5.25.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: almur@gmail.com Target Milestone: 1.0 SUMMARY Turning screens on after the screens turned themselves off for inactivity makes plasmashell crash. Once they are off STEPS TO REPRODUCE 1. Using Wayland with two Displayport screens, let KDE be without interacting until the two screens turn themselves off for inactivity. 2. Once they are off, come back to the computer and move the mouse to wake the screens up 3. Observe at least plasma crashing, if not failing to wake screens up at all (in which case, a hard reset is required) 4. If the screens were to come back up correctly, logging in with the password shows the unlock button and it does not continue the login procedure, hanging there, since plasma crashed behind the scenes. OBSERVED RESULT Plasma crashes and sometimes fails to wake up screens. journalctl shows multiple instances of: plasmashell[1473]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() and multiple instances of: plasmashell[1473]: requesting unexisting screen 3 EXPECTED RESULT The screens should wake up normally and plasma should not crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.18.10-arch1-1 KDE Plasma Version: 5.25.3 KDE Frameworks Version: 5.96.0 Qt Version: 5.15.5 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449563] System Settings Quick Settings page shows same "Most Used" item twice
https://bugs.kde.org/show_bug.cgi?id=449563 --- Comment #12 from Alfonso Murolo --- (In reply to Ivan Čukić from comment #10) > Hi Schlaefer, > > Can you post the output of the following here (as two attachments). > > sqlite3 ~/.local/share/kactivitymanagerd/resources/database 'select * from > ResourceScoreCache where initiatingAgent = "org.kde.systemsettings";' > > and > > sqlite3 ~/.local/share/kactivitymanagerd/resources/database 'select * from > ResourceEvent where initiatingAgent = "org.kde.systemsettings";' > > I see two possible causes of this -- plasma changed how it reports KCM URLs > (but the kcm: prefix wasn't added in 5.24) or, as you said, some other > component reporting this the wrong way. > > This is not something that KActivities can handle, but we can prune the > invalid ones easily when they are loaded in system settings. The second command instead produces the following output (I used pastebin since it is very long): https://pastebin.com/QxW41TRB -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449563] System Settings Quick Settings page shows same "Most Used" item twice
https://bugs.kde.org/show_bug.cgi?id=449563 --- Comment #11 from Alfonso Murolo --- (In reply to Ivan Čukić from comment #10) > Hi Schlaefer, > > Can you post the output of the following here (as two attachments). > > sqlite3 ~/.local/share/kactivitymanagerd/resources/database 'select * from > ResourceScoreCache where initiatingAgent = "org.kde.systemsettings";' > > and > > sqlite3 ~/.local/share/kactivitymanagerd/resources/database 'select * from > ResourceEvent where initiatingAgent = "org.kde.systemsettings";' > > I see two possible causes of this -- plasma changed how it reports KCM URLs > (but the kcm: prefix wasn't added in 5.24) or, as you said, some other > component reporting this the wrong way. > > This is not something that KActivities can handle, but we can prune the > invalid ones easily when they are loaded in system settings. Hi Ivan, for what it's worth, I am sending you my output in the VM where I have been replicating it. Currently, I get duplicate output for "File Search" if I open systemsettings. > 0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:about-distro.desktop|0|3.0|1639847651|1648997945 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_baloofile.desktop|0|14.0|1639847870|1648998547 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_lookandfeel.desktop|0|26.0|1639864711|1648998245 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kwinoptions.desktop|0|0.0|1648996660|1648996660 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:screenlocker.desktop|0|0.0|1648996674|1648996674 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_translations.desktop|0|0.0|1648996682|1648996682 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_notifications.desktop|0|2.0|1648998038|1648998075 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:fontinst.desktop|0|0.0|1648998040|1648998040 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_workspace.desktop|0|0.0|1648998042|1648998042 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_kup.desktop|0|1.0|1648998067|1648998069 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_style.desktop|0|6.0|1648998225|1648998246 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_plasmasearch.desktop|0|7.0|1648998521|1648998547 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_lookandfeel|0|11.5568568269966|1649108250|1649600255 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_plasmasearch|0|20.412484512923|1649176526|1649529146 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_baloofile|0|8.96923323447635|1649177402|1649598590 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_style|0|1.0|1649179696|1649194468 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_updates|0|0.0|1649194308|1649194308 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_desktoptheme|0|0.0|1649194468|1649194468 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_kwindecoration|0|0.0|1649194473|1649194473 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_fonts|0|0.0|1649194473|1649194473 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_icons|0|0.0|1649194475|1649194475 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_translations|0|0.0|1649194599|1649194599 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_kscreen|0|0.0|1649509984|1649509984 > f0963528-319c-4763-a86b-580f3e27e664|org.kde.systemsettings|kcm:kcm_sddm|0|0.0|1649600261|1649600261 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449563] System Settings Quick Settings page shows same "Most Used" item twice
https://bugs.kde.org/show_bug.cgi?id=449563 --- Comment #7 from Alfonso Murolo --- (In reply to Schlaefer from comment #0) > Created attachment 146230 [details] > System Settings most used shows same module twice > > SUMMARY > > The "Most Used Settings" shows same item twice. > > STEPS TO REPRODUCE > > 1. Open System Settings > 2. Have my setup and System Settings usage behavior > > OBSERVED RESULT > > "Display Configuration" is shown twice for me. > > See attached video. > > EXPECTED RESULT > > Display Configuration module should only be displayed once. > > SOFTWARE/OS VERSIONS > Operating System: EndeavourOS > KDE Plasma Version: 5.24.80 > KDE Frameworks Version: 5.91.0 > Qt Version: 5.15.2 > Kernel Version: 5.16.4-242-tkg-cacule (64-bit) > Graphics Platform: Wayland > Processors: 12 × 11th Gen Intel® Core™ i5-11400 @ 2.60GHz > Memory: 31,2 GiB of RAM > Graphics Processor: AMD Radeon RX 5500 XT (In reply to Alfonso Murolo from comment #6) > (In reply to Nate Graham from comment #3) > > Looks like the model data comes from KActivitiesStats; the duplicate data > > should probably ne filtered out there, not not even added in the first > > place. > > Hi Nate, I am trying to investigate this behavior. The duplicate data comes > indeed from there. However, i believe the issue comes at insertion time. > Apparently, when the notification to KActivitiesStats happens, it happens in > such a way that the module ID sent is different. When accessing the last 20 > characters of such module IDs from the statistics, I manage to get two > different results for the same item (plasmasearch): > kf.activitiesstats: Item: ⊥ 26 "" 1648998245 "_lookandfeel.desktop" > kf.activitiesstats: Item: ⊥ 14 "" 1648998547 "cm_baloofile.desktop" > kf.activitiesstats: Item: ⊥ 11.4125 "" 1649527799 "kcm:kcm_plasmasearch" > kf.activitiesstats: Item: ⊥ 7 "" 1648998547 "plasmasearch.desktop" > kf.activitiesstats: Item: ⊥ 6 "" 1648998246 "cm:kcm_style.desktop" > > Specifically, it seems sometimes the kcm_pasmasearch.desktop item is sent > without the .desktop extension, and some others with the extension. However, > now that I am trying to purposefully spawn something which notifies it with > the extension, I don´t seem to be able to. Any ideas what could be causing > it? Maybe some other project is notifying access to this KCM file > incorrectly? I still can´t put my finger on this, but I am under the impression that this phenomenon is the result of the KActivities-stats database being notified differently over different KDE versions. @Schlaefer: did you update your KDE version before noticing this bug, by any chance? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 449563] System Settings Quick Settings page shows same "Most Used" item twice
https://bugs.kde.org/show_bug.cgi?id=449563 Alfonso Murolo changed: What|Removed |Added CC||almur@gmail.com --- Comment #6 from Alfonso Murolo --- (In reply to Nate Graham from comment #3) > Looks like the model data comes from KActivitiesStats; the duplicate data > should probably ne filtered out there, not not even added in the first place. Hi Nate, I am trying to investigate this behavior. The duplicate data comes indeed from there. However, i believe the issue comes at insertion time. Apparently, when the notification to KActivitiesStats happens, it happens in such a way that the module ID sent is different. When accessing the last 20 characters of such module IDs from the statistics, I manage to get two different results for the same item (plasmasearch): kf.activitiesstats: Item: ⊥ 26 "" 1648998245 "_lookandfeel.desktop" kf.activitiesstats: Item: ⊥ 14 "" 1648998547 "cm_baloofile.desktop" kf.activitiesstats: Item: ⊥ 11.4125 "" 1649527799 "kcm:kcm_plasmasearch" kf.activitiesstats: Item: ⊥ 7 "" 1648998547 "plasmasearch.desktop" kf.activitiesstats: Item: ⊥ 6 "" 1648998246 "cm:kcm_style.desktop" Specifically, it seems sometimes the kcm_pasmasearch.desktop item is sent without the .desktop extension, and some others with the extension. However, now that I am trying to purposefully spawn something which notifies it with the extension, I don´t seem to be able to. Any ideas what could be causing it? Maybe some other project is notifying access to this KCM file incorrectly? -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 435029] Do not display maximize button when only one splitter is active
https://bugs.kde.org/show_bug.cgi?id=435029 Alfonso Murolo changed: What|Removed |Added CC||almur@gmail.com --- Comment #2 from Alfonso Murolo --- Hi, I thought I could provide a way to fix this. I have started the MR at https://invent.kde.org/utilities/konsole/-/merge_requests/571 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447074] Split-view creates uneven views
https://bugs.kde.org/show_bug.cgi?id=447074 --- Comment #7 from Alfonso Murolo --- (In reply to tcanabrava from comment #4) > Created attachment 144677 [details] > attachment-4483-0.html > > you are correct, there is a bug there, I have never realized it. > Do you want to try to solve it? code *should* not be complex. > if not, I can try later on. > > > On Sun, Dec 19, 2021 at 10:39 AM Alfonso Murolo > wrote: > > > https://bugs.kde.org/show_bug.cgi?id=447074 > > > > --- Comment #3 from Alfonso Murolo --- > > (In reply to tcanabrava from comment #2) > > > Created attachment 144670 [details] > > > attachment-25446-0.html > > > > > > Subsequent commands splits the *current* container in exactly half. > > > I understand the request but I think it would be complex to implement > > > considering that the old behavior you could do only vertical *or* > > > horizontal splits, not combine them. (so it was easy to just reorganize > > the > > > screen dividing the width by the number of splits) > > > > > > Now we can combine splits, horizontal and vertical, so resizing all > > panels > > > is not so straightforward. > > > > > > > > > Le dim. 19 déc. 2021 à 09:51, Alfonso Murolo > > a > > > écrit : > > > > > > > https://bugs.kde.org/show_bug.cgi?id=447074 > > > > > > > > Alfonso Murolo changed: > > > > > > > >What|Removed |Added > > > > > > > > > > > > > > CC||almur@gmail.com > > > > > > > > --- Comment #1 from Alfonso Murolo --- > > > > I can confirm this, I have tried it on my personal machine (Konsole > > 21.12 > > > > on > > > > Archlinux) and on Konsole master (22.03.70). I am looking into why this > > > > happens. At a certain point I started thinking that maybe this could be > > > > intended, but the fact that the first command spilits in exactly half, > > and > > > > subsequent commands don´t, is to me giving away that something is odd. > > > > > > > > -- > > > > You are receiving this mail because: > > > > You are the assignee for the bug. > > > > As I am not very familiar with the code of the ViewSplitter, and I chose > > this > > issue as the first one ever to look at (:D), please take my words with a > > grain > > of salt: it seems from the behaviour however that the sizes of the current > > container are incorrectly referenced to. > > > > This results in a failure: > > 1. Split the views in half top/bottom. Views will be split correctly > > 2. Kill the bottom view. Now only one view exists, exactly identical to the > > first > > 3. Split the view in half top/bottom again. Current container should, > > intuitively, be exactly the same size of the original container, to be > > split in > > half. Observe the failure in splitting in half a second time. > > > > -- > > You are receiving this mail because: > > You are the assignee for the bug. I should have now correctly issued the merge request. Should I also take the assignment of this bug ticket? How is the workflow exactly? Any further guidance about this is welcome! -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447074] Split-view creates uneven views
https://bugs.kde.org/show_bug.cgi?id=447074 --- Comment #5 from Alfonso Murolo --- (In reply to tcanabrava from comment #4) > Created attachment 144677 [details] > attachment-4483-0.html > > you are correct, there is a bug there, I have never realized it. > Do you want to try to solve it? code *should* not be complex. > if not, I can try later on. > > > On Sun, Dec 19, 2021 at 10:39 AM Alfonso Murolo > wrote: > > > https://bugs.kde.org/show_bug.cgi?id=447074 > > > > --- Comment #3 from Alfonso Murolo --- > > (In reply to tcanabrava from comment #2) > > > Created attachment 144670 [details] > > > attachment-25446-0.html > > > > > > Subsequent commands splits the *current* container in exactly half. > > > I understand the request but I think it would be complex to implement > > > considering that the old behavior you could do only vertical *or* > > > horizontal splits, not combine them. (so it was easy to just reorganize > > the > > > screen dividing the width by the number of splits) > > > > > > Now we can combine splits, horizontal and vertical, so resizing all > > panels > > > is not so straightforward. > > > > > > > > > Le dim. 19 déc. 2021 à 09:51, Alfonso Murolo > > a > > > écrit : > > > > > > > https://bugs.kde.org/show_bug.cgi?id=447074 > > > > > > > > Alfonso Murolo changed: > > > > > > > >What|Removed |Added > > > > > > > > > > > > > > CC||almur@gmail.com > > > > > > > > --- Comment #1 from Alfonso Murolo --- > > > > I can confirm this, I have tried it on my personal machine (Konsole > > 21.12 > > > > on > > > > Archlinux) and on Konsole master (22.03.70). I am looking into why this > > > > happens. At a certain point I started thinking that maybe this could be > > > > intended, but the fact that the first command spilits in exactly half, > > and > > > > subsequent commands don´t, is to me giving away that something is odd. > > > > > > > > -- > > > > You are receiving this mail because: > > > > You are the assignee for the bug. > > > > As I am not very familiar with the code of the ViewSplitter, and I chose > > this > > issue as the first one ever to look at (:D), please take my words with a > > grain > > of salt: it seems from the behaviour however that the sizes of the current > > container are incorrectly referenced to. > > > > This results in a failure: > > 1. Split the views in half top/bottom. Views will be split correctly > > 2. Kill the bottom view. Now only one view exists, exactly identical to the > > first > > 3. Split the view in half top/bottom again. Current container should, > > intuitively, be exactly the same size of the original container, to be > > split in > > half. Observe the failure in splitting in half a second time. > > > > -- > > You are receiving this mail because: > > You are the assignee for the bug. I´d like to try to fix it. As it is my first issue, it will probably take me a while to figure out how the entire splitter works, but hopefully it shouldn´t be too hard :-) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447074] Split-view creates uneven views
https://bugs.kde.org/show_bug.cgi?id=447074 --- Comment #3 from Alfonso Murolo --- (In reply to tcanabrava from comment #2) > Created attachment 144670 [details] > attachment-25446-0.html > > Subsequent commands splits the *current* container in exactly half. > I understand the request but I think it would be complex to implement > considering that the old behavior you could do only vertical *or* > horizontal splits, not combine them. (so it was easy to just reorganize the > screen dividing the width by the number of splits) > > Now we can combine splits, horizontal and vertical, so resizing all panels > is not so straightforward. > > > Le dim. 19 déc. 2021 à 09:51, Alfonso Murolo a > écrit : > > > https://bugs.kde.org/show_bug.cgi?id=447074 > > > > Alfonso Murolo changed: > > > >What|Removed |Added > > > > > > CC||almur@gmail.com > > > > --- Comment #1 from Alfonso Murolo --- > > I can confirm this, I have tried it on my personal machine (Konsole 21.12 > > on > > Archlinux) and on Konsole master (22.03.70). I am looking into why this > > happens. At a certain point I started thinking that maybe this could be > > intended, but the fact that the first command spilits in exactly half, and > > subsequent commands don´t, is to me giving away that something is odd. > > > > -- > > You are receiving this mail because: > > You are the assignee for the bug. As I am not very familiar with the code of the ViewSplitter, and I chose this issue as the first one ever to look at (:D), please take my words with a grain of salt: it seems from the behaviour however that the sizes of the current container are incorrectly referenced to. This results in a failure: 1. Split the views in half top/bottom. Views will be split correctly 2. Kill the bottom view. Now only one view exists, exactly identical to the first 3. Split the view in half top/bottom again. Current container should, intuitively, be exactly the same size of the original container, to be split in half. Observe the failure in splitting in half a second time. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 447074] Split-view creates uneven views
https://bugs.kde.org/show_bug.cgi?id=447074 Alfonso Murolo changed: What|Removed |Added CC||almur@gmail.com --- Comment #1 from Alfonso Murolo --- I can confirm this, I have tried it on my personal machine (Konsole 21.12 on Archlinux) and on Konsole master (22.03.70). I am looking into why this happens. At a certain point I started thinking that maybe this could be intended, but the fact that the first command spilits in exactly half, and subsequent commands don´t, is to me giving away that something is odd. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 438993] Plotting using ggplot2 makes R crash in RKWard
https://bugs.kde.org/show_bug.cgi?id=438993 --- Comment #7 from Alfonso --- Thanks for the Fix!!! It is working as: Versión 0.7.2z+0.7.3+devel1 -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 438993] Plotting using ggplot2 makes R crash in RKWard
https://bugs.kde.org/show_bug.cgi?id=438993 --- Comment #3 from Alfonso --- Hi, Would you recommend to rebuild RKWard against R base 4.1 with the: >Quick workaround: >https://invent.kde.org/education/rkward/-/commit/3ea95cb816e7388b9d0e4c8bb2092b29054243bb ? Or wait for it to be included in a future release? (right now the server is down, so I'll have to wait till tomorrow) Thanks a lot for your answers and fixes!!! -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 439162] "Error in RK() : Graphics API version mismatch" R 4.1
https://bugs.kde.org/show_bug.cgi?id=439162 --- Comment #1 from Alfonso --- The bug is reproducible with nativie R 4.1 previews dialogs. -- You are receiving this mail because: You are watching all bug changes.
[rkward] [Bug 439162] New: "Error in RK() : Graphics API version mismatch" R 4.1
https://bugs.kde.org/show_bug.cgi?id=439162 Bug ID: 439162 Summary: "Error in RK() : Graphics API version mismatch" R 4.1 Product: rkward Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: rkward-de...@kde.org Reporter: alfonsociol...@gmail.com Target Milestone: --- SUMMARY Error in RK() : Graphics API version mismatch" when using RKWard native device to plot with ggplot2 with R 4.1. STEPS TO REPRODUCE 1. Updated with deb "https://cloud.r-project.org/bin/linux/ubuntu focal-cran40/" and "https://launchpad.net/~c2d4u.team/+archive/ubuntu/c2d4u4.0+ " to R 4.1.0, 2. plotting using ggplot2. 3. Error in RK() : Graphics API version mismatch" when using RKWard native device. 4. But is capable of producing the graph when submited. OBSERVED RESULT Native device shows error: (In Spanish) "Error in RK() : Versión API gráfica incompatible" EXPECTED RESULT Graph preview. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux Mint 20.1 (available in About System) KDE Plasma Version: 5.68 KDE Frameworks Version: 5.68 Qt Version: Qt5 5.12.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting
https://bugs.kde.org/show_bug.cgi?id=385880 Alfonso Castro changed: What|Removed |Added CC||fons...@gmail.com --- Comment #9 from Alfonso Castro --- This problem still happens in OpenSuSE Leap 15. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 375529] New: Indentation broken if automatic brackets is used
https://bugs.kde.org/show_bug.cgi?id=375529
Bug ID: 375529
Summary: Indentation broken if automatic brackets is used
Product: kate
Version: 16.04
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: indentation
Assignee: kwrite-bugs-n...@kde.org
Reporter: naker...@nakerium.com
Target Milestone: ---
In c++, with automatic brackets on, indentation set to "C style" and using
tabs, when I write something that uses brackets (for example the body of an
if-case), the brackets go to wrong positions and the indentation is all bad.
For example ( means tab, . means space, | is the caret position):
I have something like this:
int main()
{
while(true)|
}
I press and go to the next line (as expected with the one extra
indentation more than the while line). Then, pressing the '{' key results in
this:
int main()
{
while(true)
.{|}
}
Notice that the indentation is wrong and using a single space instead of a tab.
The cursor is inside the brackets, as expected.
If I press once again, I get this:
int main()
{
while(true)
.{
.|
}
}
That is: the first bracket has an space instead of a tab; the body part (where
the caret is) has a tab, as expected, but then a single space (instead of a
second tab); and the second bracket has no indentation at all.
I'm using kubuntu 16.04 but with a ppa to get stable kde backports and another
for kdevelop.
Kate says that it is version 16.04.3, using KDE Frameworks 5.28.0, Qt 5.6.1
(built against 5.6.1), and the xcb windowing system.
KDE Plasma Version is 5.8.5.
Qt Version is 5.6.1.
--
You are receiving this mail because:
You are watching all bug changes.
