[kwin] [Bug 492933] New: Level 5 symbol on key having ISO_Level5_Latch on level 1 is ignored
https://bugs.kde.org/show_bug.cgi?id=492933 Bug ID: 492933 Summary: Level 5 symbol on key having ISO_Level5_Latch on level 1 is ignored Classification: Plasma Product: kwin Version: 6.1.4 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: input Assignee: kwin-bugs-n...@kde.org Reporter: aldo-pub...@laposte.net Target Milestone: --- Reproduction : 1. Set keyboard layout Ergo-L (for instance), assuming you have a recent xkb 2. focus a text input in a Wayland window 3. press key [O] (supposed to be the level5 latch in Ergo-L) 4. press a second time (level 5 of [O] is dead diaeresis in Ergo-L) 5. press key [D] (character "e" in Ergo-L) Expected: 4. should display an indicator that dead diaeresis is active 5. should output character "ë" Observed: 4. nothing 5. character "e" (without diacritics) is output This has been happening at least since plasma 6.1.4. It does not affect: - X11 apps - level 5 symbols on other keys - symbols on other levels than 5 on the key havingy ISO_Level5_Latch on level 1 More data : I checked the changelog of version 6.1.4 and noticed some work concerning level latches. Could it be related ? Suspected change: https://invent.kde.org/plasma/kwin/-/commit/0374acb1d82e827c254eeb1444cb0ce15aee635c#1a71db6ed299b894bf188ebe6a7a4cc093278abf_1030_1030 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472657] Battery widget shows charging icon, and computer will not sleep, even though AC is disconnected
https://bugs.kde.org/show_bug.cgi?id=472657 --- Comment #13 from Aldoo --- And indeed, it is upower who loops through AC devices to guess whether we are on battery. The code is here : https://gitlab.freedesktop.org/upower/upower/-/blob/master/src/up-daemon.c#L359 So, if I am right, the suggestion to make "on battery" status more robust by only checking the online status of "/org/freedesktop/UPower/devices/line_power_AC" instead of checking all devices should be made upstream (also why the other device wrongly returns "online" is another issue). -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472657] Battery widget shows charging icon, and computer will not sleep, even though AC is disconnected
https://bugs.kde.org/show_bug.cgi?id=472657 --- Comment #12 from Aldoo --- One more observation: like OP, the output "upower -d" also ends with: Daemon: daemon-version: 0.99.17 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep where we can see that "on-battery" is "no" even when the laptop is unplugged. This is already suspicious, even before powerdevil or dbus is involved. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472657] Battery widget shows charging icon, and computer will not sleep, even though AC is disconnected
https://bugs.kde.org/show_bug.cgi?id=472657 --- Comment #11 from Aldoo --- The DBUS property "OnBattery" from "/org/freedesktop/UPower" also happens to wrongly report "false" when my laptop is unplugged. I am not sure I understand exactly how powerdevil works, but it seems likely that it uses this property. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 472657] Battery widget shows charging icon, and computer will not sleep, even though AC is disconnected
https://bugs.kde.org/show_bug.cgi?id=472657 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #10 from Aldoo --- Dell Latitude 5410, Kernel 6.5.0-25-generic with plasma 6.0.4. I can reproduce previous comment's output: when unplugged, the psy line power, wrongly, reports online, while the main line power correctly reports offline. The widget icon says the power is connected (wrong) while discharging. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 428675] Missing keyboard layout button on SDDM login screen
https://bugs.kde.org/show_bug.cgi?id=428675 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #8 from Aldoo --- So it was fixed upstream in 2022. But is it supposed to work in 2024 plasma 6? (on my installation it is still missing. Should I open a new issue?) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #54 from Aldoo --- Any news on this issue? The fix seems to be known but Neon still has this faulty behavior as of today. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 460433] "Replica of" feature doesn't appear on Wayland
https://bugs.kde.org/show_bug.cgi?id=460433 --- Comment #2 from Aldoo --- Also the other way around: if a screen is already a replica of another screen, this cannot be changed with current UI. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 475284] Cannot toggle screen mirroring in display settings (in systemsettings)
https://bugs.kde.org/show_bug.cgi?id=475284 --- Comment #2 from Aldoo --- This workaround works provided a separate screen appears that you can drag around. My problem is that the screen I want to change the behavior of, only appears as an icon in the upper right corner of the representation of my laptop screen (which it is cloning). I cannot drag and drop and move this icon out of the laptop screen, for instance. So, so far there is no workaround I can think of. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 475284] New: Cannot toggle screen mirroring in display settings (in systemsettings)
https://bugs.kde.org/show_bug.cgi?id=475284 Bug ID: 475284 Summary: Cannot toggle screen mirroring in display settings (in systemsettings) Classification: Plasma Product: KScreen Version: 5.27.8 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: aldo-pub...@laposte.net Target Milestone: --- This used to be completely configurable in the kscreen KCM, but it seems it disappeared somewhere along the way (maybe when I switched from X11 to Wayland?): the ability to select whether a monitor should extend the display area or mirror another monitor (and which one). Most of the time I do not really care, since I use only 2 monitors and they just make an extended display by default. I only use systemsettings to change relative positioning and fractional scale and voilà. But I also give a lecture in an amphitheater having 2 side-by-side video projectors and I would like the 2 projectors to display the same thing (as I used to do last year, but maybe under X11 plasma)... which seems to be impossible: kscreen decides that the third screen should just mirror my laptop integrated panel, with no apparent way to change this. Is this setting hidden somewhere or did this feature just disappear? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 432818] Use libxkbregistry to parse the rules files
https://bugs.kde.org/show_bug.cgi?id=432818 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #18 from Aldoo --- Also, relying on environment variables is not really convenient, since you need to restart the session to take changes into account. So not only it is just user unfriendly, but also it is much less flexible than setxkbmap used to be. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460221] The "start menu" is in the center of the screen now not on the left.
https://bugs.kde.org/show_bug.cgi?id=460221 --- Comment #2 from Aldoo --- I just updated to plasma 5.26 (Neon packages), this issue is still here. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 460221] The "start menu" is in the center of the screen now not on the left.
https://bugs.kde.org/show_bug.cgi?id=460221 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #1 from Aldoo --- I have the same issue with up to date Neon. The problem is very recent. I just wanted to add that this menu is not the only one concerned by the problem of wrongly appearing at screen center since this update. Also concerned: - krunner - "drawers" opened from system tray icons (for instance the one opened by "more" button from the system tray, or the one from the notification icon) - the activity list Not affected: - context menus from non-plasma apps in the system tray - menus from the task manager plasma widget Other drawers or menus (like the one from the window list plasma widget) appear at the wrong place since the same update, but since their location is not at the center of the screen, it's probably off-topic. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 458924] Clarify respective responsibilities of activities and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=458924 --- Comment #2 from Aldoo --- I did not know there was another bug tracker! It is reassuring to know that plasma "VIPs" also agree with some of this diagnosis. Anyway, in this case, the TL;DR will suffice as my humble contribution, if it isn't redundant with something already said (obviously I haven't caught up with the discussion yet... ). -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 458924] New: Clarify respective responsibilities of activities and virtual desktops
https://bugs.kde.org/show_bug.cgi?id=458924 Bug ID: 458924 Summary: Clarify respective responsibilities of activities and virtual desktops Product: kactivitymanagerd Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: aldo-pub...@laposte.net CC: plasma-b...@kde.org Target Milestone: --- TL;DR: Plasma does not need both virtual desktops and activities (as a more evolved alternative). Instead both concepts should have clearly defined and separate roles: desktops for window management and activities for semantic desktop (only). In this setting, it should be possible to semantically associate a virtual desktop to an activity (as you would associate a document). First, I would like to apologize, as I do not know whether here is the place to make such an elaborate suggestion, but I do not really know where to start either... (probably I should directly discuss with whichever developer is currently interested in this part of plasma, but I am not familiar enough with the project... ). Also maybe this issue should not be reported to kactivitymanagerd component, as it is a transversal one (please feel free to move it to wherever it should be discussed!). So I believe current situation with respect to activities and virtual desktop is less than ideal (anyway I am not very satisfied!). On one side, we have virtual desktops: - old concept, shared by many X11 (and now Wayland) window managers - each window has, in its properties, the desktop number it belongs to - various apps from different desktop environments are desktop-aware in a compatible way - they are well supported in plasma/kwin, with nice switching effect and convenient integration (window title bar context menu, task manager and virtual desktop plamoid) - but overall they are quite poor in features On the other side, there are the plasma activities: - like virtual desktops, they can contain windows... - ... but they also contain associated documents and various stuff. Power management is also activity aware. - newer concept (although not that new now!) - kde plasma-centric. Non-plasma apps are totally oblivious to the concept (when you restore your firefox windows after it crashed or after you rebooted, they all appear in current activity disregarding where the windows used to be before, for instance). - even kde stuff does not fully support activities everywhere it makes sense (various reported issues) - features similar to virtual desktops, needs to get re-implemented separately (for instance the activity manager plasmoid, analogous to the desktop manager plasmoid)... sadly often it is done in a less polished way (many kwin animations for desktop switching, none for activity switching) or not at all (kwin has many shortcuts for navigating desktops or presenting windows from current desktop, but not their counterpart for activities). While it appears activities were initially meant to replace virtual desktops, after all these years, we are not yet at a stage where they can efficiently do so. Even if many issues could be fixed, given some love, there would still remain the main standing issue with the non-kde world. As a consequence, if you want everything (full support and semantic desktop features), currently you need to use both activities and virtual concepts. Unfortunately, doing so does not resolve everything and it adds a useless layer of complexity, which is hard to mentally adapt to. Also this adds constraints that do not make sense semantically (such as being forced to use the same number of desktops in each activity; or, if we look at it with the opposite mental model, being forced to have the same activities on each desktop!). Moreover as long as plasma uses both concepts, many features need to be duplicated which wastes a lot of developer time. At this point, wouldn't the only reasonable thing to totally drop window management from activities and only keep the semantic stuff? What I have in mind is that an activity should not be a kind of virtual desktop on steroids, but just container for : - as it is already the case: documents, files, folders, tasks and some relevant settings (e.g. power management settings)... and not windows! - but also a set of virtual desktops (so that every virtual desktop is associated to some activity) When you switch to a desktop, you also automatically switch to the activity it belongs to, hence: - all the activity switching and window management features can be removed (activity manager plasmoid, keyboard shortcuts) so that their (often more polished) virtual desktop counterparts can be used instead; - non-kde apps who know how to deal with virtual desktops (remembering where they belong, for instance), also work smoothly with activit
[kwin] [Bug 444235] New: Keyboard shortcut for appmenu in kwin decoration
https://bugs.kde.org/show_bug.cgi?id=444235 Bug ID: 444235 Summary: Keyboard shortcut for appmenu in kwin decoration Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: appmenu Assignee: kwin-bugs-n...@kde.org Reporter: aldo-pub...@laposte.net Target Milestone: --- It seems there is currently no way to add a keyboard shortcut to open the application "global" menu integrated in the decoration. This implies that application features that are only reachable through the menu bar require the mouse to be activated (unless an alternative menu bar implementation is used, such as the application native menu or the global menu plasma widget). Could this be added? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376727] Can't navigate between menu entries using arrow keys
https://bugs.kde.org/show_bug.cgi?id=376727 --- Comment #8 from Aldoo --- And the keyboard navigability issue when invoked from a shortcut seems to be also known: Bug 441990. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418574] Global Menu widget renders 2 varying menus when activated via keyboard shortcut.
https://bugs.kde.org/show_bug.cgi?id=418574 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Aldoo --- It looks like it is a duplicate of Bug #379242. *** This bug has been marked as a duplicate of bug 379242 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379242] Global Menu widget calls menu twice when using hotkey on single button mod
https://bugs.kde.org/show_bug.cgi?id=379242 Aldoo changed: What|Removed |Added CC||dawnprai...@gmail.com --- Comment #4 from Aldoo --- *** Bug 418574 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376727] Can't navigate between menu entries using arrow keys
https://bugs.kde.org/show_bug.cgi?id=376727 --- Comment #7 from Aldoo --- I wanted to add I just found out that the problem of different appearance when single button menu is invoked by keyboard was already reported: see Bug #379242. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379242] Global Menu widget calls menu twice when using hotkey on single button mod
https://bugs.kde.org/show_bug.cgi?id=379242 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #3 from Aldoo --- Additional observation: when this happens, the menu is not navigable by keyboard. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 376727] Can't navigate between menu entries using arrow keys
https://bugs.kde.org/show_bug.cgi?id=376727 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #6 from Aldoo --- (In reply to Felipe Kinoshita from comment #5) > Not a problem anymore, can anyone confirm? For me (current KDE Neon packages): - everything works ok when the widget is a proper menu bar - still works fine when the widget is a single button... but only provided it was first opened by clicking the button with the mouse. There is still something weird: some submenus can be exited using left arrow, while some require using escape key... - no keyboard navigation at all when the widget is a single button and it was first opened using a keyboard shortcut (even the visual appearance is different actually... ). This is quite embarrassing: typically you use the keyboard shortcut when you don't want your hands to leave the keyboard. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 412527] KScreenlocker gets confused when changin displays
https://bugs.kde.org/show_bug.cgi?id=412527 --- Comment #8 from Aldoo --- Also, is there something Is can do to help with the resolution of this bug? (I would rather use my time for helping than losing it uselessly several times a day, every time I switch to a VT to kill kscreenlocker!) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 412527] KScreenlocker gets confused when changin displays
https://bugs.kde.org/show_bug.cgi?id=412527 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #7 from Aldoo --- Likely duplicates: Bug #440639 and Bug #436590 (different manifestations of what looks like the inability of kscreenlocker to realize that display configuration has changed). Also the bug is still present (at least on my computer, running Plasma 5.22.5 on KDE Neon). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440639] Black screen with cursor when resuming from sleep with a different display configuration
https://bugs.kde.org/show_bug.cgi?id=440639 --- Comment #4 from Aldoo --- Ah and Bug #412527 is also almost the same problem. The three bugs are probable duplicates or symptoms of the same bug. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 436590] Lock screen does not resize with display resolution change
https://bugs.kde.org/show_bug.cgi?id=436590 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #1 from Aldoo --- Also probably related to Bug #440639 (about greeter screen becoming black after unplugging external monitor, which probably share the same root cause, i.e. : kscreenlocker is not aware of the change or does not react to it). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440639] Black screen with cursor when resuming from sleep with a different display configuration
https://bugs.kde.org/show_bug.cgi?id=440639 --- Comment #3 from Aldoo --- Also probably related to Bug #436590 (about greeter not resizing on display configuration change: which probably share the same root cause, i.e. kscreenlocker is not aware of the change or does not react to it). -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 440639] Black screen with cursor when resuming from sleep with a different display configuration
https://bugs.kde.org/show_bug.cgi?id=440639 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #2 from Aldoo --- I am pretty sure I have this bug since way longer than a couple of months (much like several years, I think). Also, there is the "reverse" reproduction: use your laptop unplugged, put it to sleep, plug it to an external monitor while asleep, then wake it up. In this case, often (not always), one of the screens will be black. Also there are focusing issues, making the password hard to enter (not going more into details, as this deserves a separate bug report). Since this is an old ongoing bug, I assume the resolution is probably difficult, and probably hardware dependent (by the way, like the opener, I use an Intel integrated GPU: Mesa Intel(R) UHD Graphics (CML GT2) (0x9bca)). Maybe, until there is a proper fix, a workaround could be provided, making it easy to restart kscreenclocker when it is not usable? (I don't know, maybe a "panic" key combo of some sort, that does not require to switch to some other virtual terminal) Also, is there no way for kscreenlocker to detect that the screen is currently black? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 429177] wayland: krunner position no longer follows window rules and can't be set to "under mouse"
https://bugs.kde.org/show_bug.cgi?id=429177 --- Comment #6 from Aldoo --- By the way, this focus issue also affects Yakuake. -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 429177] wayland: krunner position no longer follows window rules and can't be set to "under mouse"
https://bugs.kde.org/show_bug.cgi?id=429177 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #5 from Aldoo --- Another side effect of this bug: when exiting krunner, the focus doesn't necessarily go back to the window that previously had it. Instead it goes to the active window of the left screen, which is particularly frustrating when the screen you use as primary is on the right hand side. This behavior probably deserves its own bug. This bug was invisible when krunner used to correctly appear on current screen. But even if #429177 is fixed, the focus bug could come back when screen placement options will be implemented in krunner. -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 442580] Control panel's checkbox legend to access UEFI on next startup is unclear in French
https://bugs.kde.org/show_bug.cgi?id=442580 --- Comment #1 from Aldoo --- Also I would like to add that this checkbox has little to do with desktop sessions anyway, so this does not help understanding what it is meant to do. But moving the checkbox to another tab should be a separate bug to submit to "systemsettings" product, shouldn't it? -- You are receiving this mail because: You are watching all bug changes.
[i18n] [Bug 442580] New: Control panel's checkbox legend to access UEFI on next startup is unclear in French
https://bugs.kde.org/show_bug.cgi?id=442580 Bug ID: 442580 Summary: Control panel's checkbox legend to access UEFI on next startup is unclear in French Product: i18n Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: fr Assignee: kde-francoph...@kde.org Reporter: aldo-pub...@laposte.net Target Milestone: --- In plasma system settings, in the desktop session management tab, there is a checkbox labelled "Saisir l'écran de configuration du micro-programme au prochain redémarrage". In my opinion this is a very puzzling description of what this is meant to do. After researching a bit (looking for the original English label), I finally understood this was meant to enter UEFI setup on next computer boot. In this regard, the translation does not work at all: - "saisir" means for a human to input some data into the computer. How is this related to what the checkbox does? - "micro-programme" can be understood, although it is very uncommon, compared to the English word "firmware" (I understand there is some ideology here, trying to push French equivalents when it is possible). Anyway, there are a lot of micro-programmes (or firmwares). How is the user supposed to guess this is about UEFI? Suggested replacement: "Entrer dans l'écran de configuration du micro-programme UEFI au prochain démarrage". -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430098] Alt + Resize or Move and window focus
https://bugs.kde.org/show_bug.cgi?id=430098 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #1 from Aldoo --- I would like to add that current behavior disrupts a very classical workflow: 1. you work on window1, maximized on your main screen (or just taking a lot of room on your only screen, if you are in a single monitor setup) 2. you want to switch to another task (window2), currently on your secondary screen (or maybe a small window on your main screen) 3. so you alt-grab window2 and move it to the most comfortable place (i.e. maximized on the main screen), most of the time reaching for the screen top edge so that window2 is maximized in the process. So you expect to have a readily usable full screen window for the new active task, but instead, the window of the task you want to switch to is hidden behind the window of your previous task. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 391038] Weird little widget that shows the desktop wallpaper shown over the mail window
https://bugs.kde.org/show_bug.cgi?id=391038 --- Comment #11 from Aldoo --- It's still here for me. Except it is now white instead of showing the wallpaper as it previously used to. (Currently using version 4:20.08.3-0xneon+20.04+focal+build23 of kdepim packages, with version 4:5.20.3-0xneon+20.04+focal+build20 of plasma packages.) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 428885] New: Open dolphin in current activity folder by default
https://bugs.kde.org/show_bug.cgi?id=428885 Bug ID: 428885 Summary: Open dolphin in current activity folder by default Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: aldo-pub...@laposte.net CC: kfm-de...@kde.org Target Milestone: --- In dolphin (and in the KIO ecosystem) the URL "activities:/current" points to a virtual folder where you can find all stuff tagged for current activity. This is typically the files I want to quickly access to when I open dolphin, so I wanted to set up the startup URL as "activities:/current". Alas, the configuration dialog won't let me do this. It pops up an error dialog instead: "The location of personal folder is invalid or does not exist. It will not be applied." (not sure about the exact message: my UI is in French). Could this be fixed so that dolphin accepts that sort of URL? (same for any other KIO compatible URL, by the way, as it seems the problem is more general: so far, according to what I tried, only local file system locations seem to work) -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 428760] New: Remap touchscreen to laptop integrated panel on display configuration change
https://bugs.kde.org/show_bug.cgi?id=428760 Bug ID: 428760 Summary: Remap touchscreen to laptop integrated panel on display configuration change Product: KScreen Version: 5.20.2 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kded Assignee: kscreen-bugs-n...@kde.org Reporter: aldo-pub...@laposte.net Target Milestone: --- I have a laptop with a touchscreen. When using it alone (without an external monitor), the touchscreen works as expected. But when I plug an external monitor and do multi-monitor, then the touchscreen area is mapped to the whole visual area (not just limited to laptop integrated panel), which is awkward since the user expects that the pixel being interacted with is the one under the finger. Please, make it so the touchscreen input is always mapped to the laptop panel, whatever happens ! For information I use X11 Plasma. Also it seems that the command "xinput --map-to-output " works for fixing the touchscreen manually, so it would be enough if kded would run this command on every display change (maybe the user would have to declare what screen is the laptop panel and what pointing device is the touchscreen, if this cannot be automated?). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428719] New: Kwin rules will not let you select several activities for a given window or application
https://bugs.kde.org/show_bug.cgi?id=428719 Bug ID: 428719 Summary: Kwin rules will not let you select several activities for a given window or application Product: kwin Version: 5.20.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: rules Assignee: kwin-bugs-n...@kde.org Reporter: aldo-pub...@laposte.net CC: isma...@gmail.com Target Milestone: --- The applications I use are typically used in the context of a some subset of the set of activities I defined. This subset often is a strict subset (not *all* activities) and not a singleton (I need this application in *several* activities). I would like kwin to be able to automatically set the activities where the application or window should be shown when the application starts or the window appears. Currently, kwin rules settings (for either windows or apps) will only let me create such a rule for one single activity: a rule of the form "initially, set activity to SOME_ACTIVITY". What would like instead is the ability to define a rule of the form "initially, set activities to SOME_ACTIVITY_1, SOME_ACTIVITY_2, ... SOME_ACTIVITY_N". This rule format would be more consistent with what you can do from the window decoration context menu, where you can actually choose an arbitrary set of activities where the window should be shown. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 419499] Switch activity shortcut order
https://bugs.kde.org/show_bug.cgi?id=419499 --- Comment #5 from Aldoo --- I believe Adam got it right: the order is updated when merely "switching over". This is different from what happens when you alt-tab from one window to another one: in this case, the order is updated only when the alt key is released, and definitely not every time you hit tab (while alt is still pressed). -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 283678] Distinct session sets per desktop activity
https://bugs.kde.org/show_bug.cgi?id=283678 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #8 from Aldoo --- Why not implement this by using several instances of the konsole kpart instead of expecting a single konsole instance to manage activity membership of tabs? Yakuake would then have one (different) window in each activity, and each window would contain a different instance of the kpart. Doing so would not require any modification of the konsole kpart, or would it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 406806] Folder View widget is not an icon on vertical panels
https://bugs.kde.org/show_bug.cgi?id=406806 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #3 from Aldoo --- There is clearly some issue with automatic choice of mode between icon and list. Notwithstanding, adding a simple checkbox, in the widget settings, to let the user choose would solve many problems. Even in cases where there is room for a list view, some users may prefer a simple icon anyway. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 419499] New: Switch activity shortcut order
https://bugs.kde.org/show_bug.cgi?id=419499 Bug ID: 419499 Summary: Switch activity shortcut order Product: kactivitymanagerd Version: 5.18.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ivan.cu...@kde.org Reporter: aldo-pub...@laposte.net CC: plasma-b...@kde.org Target Milestone: --- Currently, it is possible to set up shortcuts to navigate activities (direct and reverse orders). In my setup, I chose meta+tab and meta+shift+tab, to mimic the famous alt+tab and alt+shift+tab window navigating shortcuts. Alas, the analogy stops here, as the activity order is static, whereas alt+tab will always switch to previously active window (and alt+tab+tab will switch to the window that was active before that). In other words, for alt+tab, windows are sorted in last apparition order, and this order is updated every time the focus changes. A similar behaviour for activities would play very nicely for my workflow (where I typically switch between 2 or at most 3 active tasks, and I don't want less relevant activities to pop up unless I specifically look for them). Would it be possible to implement the "most recent order switching" behaviour for activities? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412272] New: Gyroscope/accelerometer support in presenter or control plugin
https://bugs.kde.org/show_bug.cgi?id=412272 Bug ID: 412272 Summary: Gyroscope/accelerometer support in presenter or control plugin Product: kdeconnect Version: unspecified Platform: Android OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: aldo-pub...@laposte.net Target Milestone: --- It would be useful if either (or both) the presenter or the controller plugin would support the gyroscope/accelerometer embedded in the phone. - in presenter plugin: the purpose would be laser pointer emulation (so device orientation would be interpreted as absolute coordinates for the mouse pointer) - in controller plugin: both the "absolute mode" (already described) and a "relative mode" (the device orientation would only control the pointer speed, as if it was a joystick) could be interesting. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 391038] Weird little widget that shows the desktop wallpaper shown over the mail window
https://bugs.kde.org/show_bug.cgi?id=391038 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #2 from Aldoo --- I also have this bug. Some additional observations : - mouse cursor change aside, there is no possible interaction with the rectangle - the rectangle prevents clicking on elements it hides - the rectangle's position is fixed relatively to the kmail window (resizing the subpanels of kmail main window will not move it) - restarting kmail will not make it go away (I assume, as long as whatever condition causes the bug is still met; and I know it is not always met, as this rectangle does not always appear). -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405682] akonadi_imap_resource and akonadiserver crashe every couple of minutes
https://bugs.kde.org/show_bug.cgi?id=405682 --- Comment #3 from Aldoo --- I do not know if it is a duplicate: my crashes did not happen on logout, but any time akonadi checked for new mail. Anyway, after deleting all configuration files and starting from fresh ones, the crashes are gone. Note that deleting the cached database was not enough (I had already tried that before I reported this bug). -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 283678] Distinct session sets per desktop activity
https://bugs.kde.org/show_bug.cgi?id=283678 Aldoo changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #7 from Aldoo --- *** This bug has been confirmed by popular vote. *** -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405682] akonadi_imap_resource and akonadiserver crashe every couple of minutes
https://bugs.kde.org/show_bug.cgi?id=405682 --- Comment #1 from Aldoo --- Created attachment 118932 --> https://bugs.kde.org/attachment.cgi?id=118932&action=edit akonadiserver crash log -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 405682] New: akonadi_imap_resource and akonadiserver crashe every couple of minutes
https://bugs.kde.org/show_bug.cgi?id=405682 Bug ID: 405682 Summary: akonadi_imap_resource and akonadiserver crashe every couple of minutes Product: Akonadi Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: IMAP resource Assignee: kdepim-b...@kde.org Reporter: aldo-pub...@laposte.net Target Milestone: --- Created attachment 118931 --> https://bugs.kde.org/attachment.cgi?id=118931&action=edit akonadi_imap_resource crash log akonadi_imap_resource and akonadiserver crashe every couple of minutes. There is nothing much to make it happen. It seems it happens only when synchronizing my IMAP mailboxes, but I am not sure of this. There is a load of associated bugs in my kmail/akonadi, which may or not be related to these crashes: - following one of the crashes, one of my IMAP accounts has mails in its root folder (which is supposed to be unpopulated; of course I cannot delete these mails). - sometimes, after a crashe, the whole mailbox needs to be downloaded again (this means a couple of gigabytes to download!) - kmail status bar frequently reports errors (sorry I do not have examples now, I will try to copy one and add it to this report as soon as I can) - one of my IMAP accounts frequently loses its name and receives a generic name instead (such as "Compte IMAP 6", sorry the locale is French). - in kmail status bar, the agent filtering agent seems stuck forever at 0% - synchronization seems to often restart several times for a given folder. Sometimes the progress bar goes back a few %, then progresses again. - synchronization of big folders is always very slow (although IMAP protocol should allow for just downloading the delta, should it not?) - when I mark a message as spam (which should move it to spam folder), the message comes back at the next synchronization - spam seems never to be filter out anyway (although the bogosity field is correctly set up in every received message) All in all, kmail has become almost unusable for me in the last weeks. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE neon 5.15 KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.0 ADDITIONAL INFORMATION My setup of kmail/akonadi consists in - a local mail folder - 3 IMAP accounts with local cache - a couple of calendars and address books (probably unrelated to this bug) Morover, the antispam (bogofilter) filters are set up. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kcrash] [Bug 404230] Can not submit a bug report: Login button is disabled
https://bugs.kde.org/show_bug.cgi?id=404230 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #6 from Aldoo --- I just had this bug (for a crash in akonadiserver), so it's still there. Sorry this does not help much since I do not know a reliable way to make it happen (although akonadiserver crashes every couple of minutes in my case... ). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kded] [Bug 404244] New: Select primary display from display switch window
https://bugs.kde.org/show_bug.cgi?id=404244 Bug ID: 404244 Summary: Select primary display from display switch window Product: frameworks-kded Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: fa...@kde.org Reporter: aldo-pub...@laposte.net CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Plasma recently added a convenient display switch window which can automatically pop up when a new monitor was plugged, or just triggered with a shortcut. While this new feature is convenient, it is still insufficient because it gives no option to select what monitor will become the primary display after you choose to extend current display to some direction. Why this is important (at least to me): I usually plug a new monitor during one the following two scenarii: - scenario 1: when I come to my desk and plug my laptop onto its base station, to which a 24" monitor is connected. In this scenario, I obviously want the big external monitor to become the primary display, while the integrated screen of the laptop will play a secondary role. - scenario 2: I need to give a lecture or make a presentation. In this scenario, I will plug a videoprojector to my laptop, but I want all my windows (including my panels) to stay on the laptop integrated monitor. Only the slides will be deported to the new display, which *must not* become primary. PROPOSED NEW FEATURE Add a checkbox (or any other UI control with similar functionality) on the display switch window to select whether the new monitor should become the primary display. ALTERNATIVE I believe I remember that in some previous version of Plasma, the display settings allowed to save current display configuration, and restore it when the same monitors are plugged again (similarly to the CLI tool autorandr). Putting this feature back would be an even better solution for half my daily routine (i.e.: loading the configuration for the 24" monitor on my desk for scenario 1), but would not be sufficient for scenario 2 (because I can often make presentations on new, unknown, videoprojectors). -- You are receiving this mail because: You are watching all bug changes.
[print-manager] [Bug 399707] New: Move page properties to the the main printing dialogue
https://bugs.kde.org/show_bug.cgi?id=399707 Bug ID: 399707 Summary: Move page properties to the the main printing dialogue Product: print-manager Version: 18.04 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dantt...@gmail.com Reporter: aldo-pub...@laposte.net Target Milestone: --- In old versions of KDE (was it 4.x?), it was easy to select, for instance, printing several pages per sheet directly from the main window of the printing assistant. Now you need to open the printer properties first, then "Page" tab. In my opinion, the whole "Page" tab has little to do with printer properties (except for margins, you may want to set these options independently from the actual printer you will use) and a lot to do with what you actually want to print. Hence, it should be moved to the main dialogue. It could be just another tab next to "Copies", "Options", and "PDF options". Probably, it should actually be merged with "Options", as double-sided printing options are the same kind of settings (i.e.: this is all about how pages are being laid out on sheets in order to produce the printable document). Then the tab could be renamed "Page options". -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 305095] mouse wheel scrolling problems with dynamic word wrap activated
https://bugs.kde.org/show_bug.cgi?id=305095 --- Comment #6 from Aldoo --- Sorry for the noise. There is already an open ticket: this is Bug 256561 (created in 2010 though... ) -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 305095] mouse wheel scrolling problems with dynamic word wrap activated
https://bugs.kde.org/show_bug.cgi?id=305095 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #5 from Aldoo --- Maybe the bug is back, but current version of Kate (17.12.2, Neon packages) has this problem. I have been experiencing this for a few months, but I don't remember having had this issue ever before (in particular not in 2012, with KDE 4). Should this bug be reopened, or should a brand new ticket be created ? -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 382331] Kontact/ Kmail crashes every time
https://bugs.kde.org/show_bug.cgi?id=382331 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #4 from Aldoo --- I am in the same situation, but libqt5webengine5 cannot be updated. After some inquiry, it happens that it (indirectly) depends on libharfbuzz0b, which, for some reason, will not automatically be installed (you need to explicitly ask to install it, which will in turn uninstall some stuff, in my case: libgraphite2-dev libharfbuzz-dev libharfbuzz-gobject0 libharfbuzz-icu0). After this, I can just run "apt update" and libqt5webengine5 and some bunch of other libs can finally be updated. Once this is done, I can finally run kmail ! Thank you Christoph Feck for the clue! Seems like the actual issue is that there is something wrong with dependencies and conflicts in Neon packages: all the steps I had to take by hand should have been automatically figured out by apt. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 375238] calligra-l10n-de tries to overwrite data from calligra-data
https://bugs.kde.org/show_bug.cgi?id=375238 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net --- Comment #3 from Aldoo --- Related to this bug : when calligra-l10n-xx is not installed, every time KDE starts, there is a notification asking the user to authenticate in order to finish installing language support. Of course, When you do so, it tries to install calligra-l10n-xx, which is wrong. KDE Neon should also override the settings of whatever component checks whether l10n packages are missing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Aldoo changed: What|Removed |Added CC|aldo-pub...@laposte.net | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 365989] Default desktop layout is not loaded properly from template
https://bugs.kde.org/show_bug.cgi?id=365989 Aldoo changed: What|Removed |Added CC||aldo-pub...@laposte.net -- You are receiving this mail because: You are watching all bug changes.
