[frameworks-kconfig] [Bug 422529] Put config files inside a kde subdirectory in ~/.config, ~/.local/share, and ~/.cache
https://bugs.kde.org/show_bug.cgi?id=422529 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #14 from Matthias Mueller --- Just wanted to add that this indeed is something that kind of bothered me with KDE forever. Nothing dealbreaking for me, but it would be nice to have more order in the configs for easier backup/restore. I don't even think it has to be done forcefully - just transition every piece of software when it's developer has time. So maybe more a change of the guidelines than a real change in the framework? -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458865] After an update to qt5-base the dolphin file picker dialog used in GTK applications via GTK_USE_PORTAL=1 ignores theming
https://bugs.kde.org/show_bug.cgi?id=458865 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #18 from Matthias Mueller --- (In reply to Moritz from comment #13) > since I added `XDG_CURRENT_DESKTOP=KDE` as > a workaround to `/etc/environment/` I don't have this issue anymore Does this work for anyone else? I still have to restart plasma-xdg-desktop-portal-kde to get the dark theme applied. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 458865] After an update to qt5-base the dolphin file picker dialog used in GTK applications via GTK_USE_PORTAL=1 ignores theming
https://bugs.kde.org/show_bug.cgi?id=458865 --- Comment #29 from Matthias Mueller --- Thanks for the Fix, Harald! I can confirm it works on my side too, despite the workaround not having an effect here. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464322] Make Kwin capable of using one animation for opening windows and a different one for closing
https://bugs.kde.org/show_bug.cgi?id=464322 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #5 from Matthias Mueller --- I wholeheartedly support this wish! i also think it would be better to directly have two sections in the settings. Or - if it's not too complicated in regards to implementation - maybe have the current selection for both opening and closing by default and a checkbox that splits that section into two? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 474196] The blur effect does not work in Konsole when moving a window if the "Wobbly Window" effect is enabled
https://bugs.kde.org/show_bug.cgi?id=474196 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #2 from Matthias Mueller --- Can confirm this (minus the flickering). Plasma 6.0.3 KF 6.0.0 QT 6.7.0 ArchLinux on AMDGPU -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #30 from Matthias Mueller --- (In reply to David Redondo from comment #29) > To clarify we do not skip any sensors for gpus anymore, all GPU sensors are > exposed under GPU, closing this because of that. > As this bug is about GPU I am closing it, please file another bug for other > actionable problems. > > If you want to take a look yourself the relevant code is not in libksysguard > but ksystemstats repo i can't confirm that gpu power is exposed - could you elaborate? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 445917] New: GPU-Power and CPU-Tctl and Tccd missing from filtered sensors
https://bugs.kde.org/show_bug.cgi?id=445917 Bug ID: 445917 Summary: GPU-Power and CPU-Tctl and Tccd missing from filtered sensors Product: plasma-systemmonitor Version: 5.23.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: mat.muel...@mailbox.org CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Follow-Up to https://bugs.kde.org/show_bug.cgi?id=438318 as that apparently is fixed. (see https://bugs.kde.org/show_bug.cgi?id=438318#c31) Unfortunately, GPU Power and CPU-Temperature for the whole CPU and all sensors for the mainboard are still missing/being filtered out while being displayed by 'sensors' At least on my hardware (Ryzen 3800x and 6900xt on Asrock x470 Taichi) I still strongly believe that filtering out sensors is the wrong approach, at least without the option to expose the "raw" data or a config file to change which sensors are filtered. Every time new sensors are added by new or obscure hardware, those filters have to be changed in the codebase - and hardcoded filterlists imho are pretty bad practice... -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #32 from Matthias Mueller --- (In reply to David Redondo from comment #31) > The power1 sensor in the outputs? Let's create a new issue anyways since > were we can collect relevant info since it's slightly different that it > should be now there but isn't. I don't really see why it should be a new/differnt issue, but i've created https://bugs.kde.org/show_bug.cgi?id=445917 to follow up. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 445920] GPU power sensors missing
https://bugs.kde.org/show_bug.cgi?id=445920 --- Comment #2 from Matthias Mueller --- (In reply to David Redondo from comment #1) > Matthias, could you please attach sensors -u output? Sure: [termy@Wunderland] ➜ ~ sensors -u amdgpu-pci-1000 Adapter: PCI adapter vddgfx: in0_input: 0.768 fan1: fan1_input: 0.000 fan1_min: 0.000 fan1_max: 3300.000 edge: temp1_input: 57.000 temp1_crit: 100.000 temp1_crit_hyst: -273.150 temp1_emergency: 105.000 junction: temp2_input: 60.000 temp2_crit: 110.000 temp2_crit_hyst: -273.150 temp2_emergency: 115.000 mem: temp3_input: 58.000 temp3_crit: 100.000 temp3_crit_hyst: -273.150 temp3_emergency: 105.000 power1: power1_average: 43.000 power1_cap: 255.000 -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 445917] CPU-Tctl and Tccd missing from filtered sensors
https://bugs.kde.org/show_bug.cgi?id=445917 --- Comment #2 from Matthias Mueller --- (In reply to David Redondo from comment #1) > Thanks, as I said there is not intentional filtering going on on the gpu > sensors. There is though for CPU sensors, let's have this one for cpu > sensors I will create a new issue for gpu sensors (done: 445920) Alright... i personally don't use the cpu sensors currently with systemmonitor as there is the thermal monitor plasmoid, but here's the sensors -u output for k10temp, just in case ;) k10temp-pci-00c3 Adapter: PCI adapter Tctl: temp1_input: 53.625 Tccd1: temp3_input: 49.000 I just noticed that i don't have my mainboard-sensors in lm-sensors on this install (and don't want to search for sensors due to https://gitlab.freedesktop.org/drm/amd/-/issues/1470 for the time being), so the part about the mainboard sensors might be obsolete. I think i recall them missing, too, but i'm not 100% sure and it was still 5.22 i think. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #43 from Matthias Mueller --- (In reply to David Redondo from comment #42) > Because the bug report was about amd gpu sensors missing which was fixed > with the commit mentioned in comment #16 It's not fixed for amdgpu either, as "power" still isn't available again... And this confusion is an excellent example why i believe hardcoded black-/whitelisting isn't ideal, to put it diplomatic. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 Matthias Mueller changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0 |1 Resolution|FIXED |--- --- Comment #23 from Matthias Mueller --- Yeah i'd say it is definetely not resolved/fixed - there is still no sensor for gpu power and cpu temp. We have things like GPU mem clock or usage (that i think weren't there in the past), voltage and fan speed are re-added, but still not have the other sensors the bugreport was initially created for. I heavily agree with shmerl that this filtering-approach isn't really a good idea, at least not as the only option... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444424] New: Kickoff no longer inverted when in top panel
https://bugs.kde.org/show_bug.cgi?id=24 Bug ID: 24 Summary: Kickoff no longer inverted when in top panel Product: plasmashell Version: 5.23.1 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: mat.muel...@mailbox.org CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 In the past, the new Kickoff used to be "inverted" when located in a top-panel or in the upper area of a side-panel so that the "Application/Places/Session-Management" area is on top and the search-bar on the bottom of the window. With 5.23 this behavior was removed and it opens the same way as it does in a bottom-panel. As i use kickoff mainly for session management (as krunner is as awesome as it is ;) ), i find this change unfortunate, as the session management is no longer right next to the icon i click but more halfway down the screeen. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 443409] New: "add property" in "Configure Special Window Settings" only visible after resize when accessed via titlebar
https://bugs.kde.org/show_bug.cgi?id=443409 Bug ID: 443409 Summary: "add property" in "Configure Special Window Settings" only visible after resize when accessed via titlebar Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: mat.muel...@mailbox.org Target Milestone: Not decided STEPS TO REPRODUCE 1. Right click on the TitleBar -> More Actions -> Configure Special Window Settings 2. see "add property" and "identify window property" is missing (compare to window rules accessed via ksystemsettings where this issue doesn't occur) 3. resize window downwards 4. "add property" and "identify window property" appear OBSERVED RESULT "add property" and "identify window property" is missing EXPECTED RESULT "add property" and "identify window property" to be visible from the start SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro KDE KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION worked fine in the past, haven't had the need to use it in a while though, so i'm not sure when this bug/regression was introduced -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 443409] "add property" in "Configure Special Window Settings" only visible after resize when accessed via titlebar
https://bugs.kde.org/show_bug.cgi?id=443409 --- Comment #2 from Matthias Mueller --- Ah, very good - didn't find that bug report, thanks! :) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433246] New: Pipewire missing "module-gsettings"
https://bugs.kde.org/show_bug.cgi?id=433246 Bug ID: 433246 Summary: Pipewire missing "module-gsettings" Product: plasma-pa Version: 5.20.90 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: now...@gmail.com Reporter: mat.muel...@mailbox.org CC: plasma-b...@kde.org Target Milestone: --- After switching to pipewire to replace pulse i have one annoying issue: I can no longer set "Automatically switch all running streams when a new output becomes available" in the KDE sound settings - it’s greyed out with the message "needs the pulse-audio module "module-gsettings" " According to https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/771 module-gsettings is not implemented in pipewire (yet). I've not found any other reports of this issue, so i thought it wouldn't hurt to inform you, too, in case anybody else encounters this - or maybe it even is easy to remove the dependency to this module? KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433246] Pipewire missing "module-gsettings"
https://bugs.kde.org/show_bug.cgi?id=433246 --- Comment #2 from Matthias Mueller --- Absolutely - i'm just not sure if/when the pipewire folks will implement that and as pipewire is destined to be the new standard some time i guess this should at least be documented :) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433246] Pipewire missing "module-gsettings"
https://bugs.kde.org/show_bug.cgi?id=433246 --- Comment #4 from Matthias Mueller --- Yeah the question is still open at the linked gitlab, i'll report back here as soon as i've got info when/if gsettings will be implemented or if there is an alternative way! -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433246] Pipewire is missing pulseaudio modules
https://bugs.kde.org/show_bug.cgi?id=433246 --- Comment #7 from Matthias Mueller --- Regarding the "automatically switch ..." function: Quote from P V (Contributor): "There's a setting streams-follow-default in media-session.conf that moves streams when default changes, and it's usually on by default, so streams follow default unless they have been previously manually fixed to a specific device (see pw-dump | grep target.node). The default session manager doesn't support toggling features at runtime, or have the combine sink. Pipewire itself can do all this since you can link nodes freely (eg. with Jack apps + pw-jack), but the session manager doesn't have the same link autoconfiguration features as pulseaudio right now." It seems KDE is fixing the streams to devices, even if they are not manually changed in plasma-pa? So i guess one solution (that would make the option "automatically switch ..." kind of obsolete, at least for my usecase) would be to only fix streams that have been manually set to another device and let the switching be handled by the pipewire session manager? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426496] Multiple monitor assignment is wrong after update to Qt 5.15.1
https://bugs.kde.org/show_bug.cgi?id=426496 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #23 from Matthias Mueller --- i can confirm the issue on my side - desktop PC with two different size screens. For me, the wallpaper second screen is shifted upwards and the taskmanager doesn't display the windows on that screen. And KRunner launces somewhere in the "middle" of both screens (i'd guess the middle of the combined horizontal resolution). Shifting the position of the second screen in system settings/display does fix the issues, so maybe it's related to screen positioning somehow? There are also a lot of people reporting it in the latest manjaro-testing update thread ( https://forum.manjaro.org/t/testing-update-2020-09-15-kernels-pamac-gamemode-qt-5-15-1-systemd-amdvlk-wine/25346 ) Let me know if any logs from my side could be helpful :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426496] Multiple monitor assignment is wrong after update to Qt 5.15.1
https://bugs.kde.org/show_bug.cgi?id=426496 --- Comment #31 from Matthias Mueller --- plasmashell --replace doesn't work for me, i HAVE to move the secondary screen around in system settings in order to fix it -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #8 from Matthias Mueller --- My usecase is/was monitoring the GPU-Power - i guess the mentioned mapping of PCI-adresses is nothing that can be done in userspace but has to be patched in? Or am i missing something? -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 --- Comment #15 from Matthias Mueller --- i agree that filtered choice as the only option isn't the best way to go - maybe add a checkbox "display raw sensor data" or something to still have the filtered few for less confusion for not-so-tech-savvy users. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 438318] Some AMD gpu (lm-sensors-based?) sensors no longer available
https://bugs.kde.org/show_bug.cgi?id=438318 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #3 from Matthias Mueller --- I can confirm this after updating to 5.22.1 (manjaro testing) -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 430862] Kde5init crashes in ThumbnailProtocol::get() every time I take a screenshot or start the computer
https://bugs.kde.org/show_bug.cgi?id=430862 --- Comment #73 from Matthias Mueller --- I can't reproduce the issue on my side (kio-extras 21.04.0-1, manjaro testing) anymore - i only encountered it when taking a screenshot that shows the thumbnail in a notification though. Are you sure your issues are related to this bug? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426496] Multiple monitor assignment is wrong after update to Qt 5.15.1
https://bugs.kde.org/show_bug.cgi?id=426496 --- Comment #66 from Matthias Mueller --- i only had a black wallpaper on the second monitor once since it was "fixed". (Manjaro testing here, so currently qt5-base 5.15.1-3 and plasma-desktop 5.20.2-1 ) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381257] KMail does not remember window size or position
https://bugs.kde.org/show_bug.cgi?id=381257 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #2 from Matthias Mueller --- I can confirm this, too - Manjaro testing with 5.15.3 currently -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 429134] New: Kmail doesn't remember window position after session restore
https://bugs.kde.org/show_bug.cgi?id=429134 Bug ID: 429134 Summary: Kmail doesn't remember window position after session restore Product: kmail2 Version: 5.15.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: UI Assignee: kdepim-b...@kde.org Reporter: mat.muel...@mailbox.org Target Milestone: --- SUMMARY I use session restore on reboot and usually have kmail on the right half of my second monitor. After boot, kmail is opened in the top left corner of the main screen. Exiting Kmail and starting it (or closing the window and opening it from tray) works fine, the issue only occurs on boot. I'm not sure if its a kmail or kwin/plasma issue, but i only observed this behaviour on kmail yet. To make matters worse, window rules don't work properly for kmail (i tried "apply on initialization" for position and size) - reported in https://bugs.kde.org/show_bug.cgi?id=381257 STEPS TO REPRODUCE 1. position kmail main window to your hearts content 2. reboot with option "restore session" active 3. observe wrong placement of kmail main window OBSERVED RESULT Kmail is positioned in the top left corner of the main screen EXPECTED RESULT Kmail should be where it was on shutdown SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro testing KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 429134] Kmail doesn't remember window position after session restore
https://bugs.kde.org/show_bug.cgi?id=429134 --- Comment #1 from Matthias Mueller --- I have to add to that report - it seems that Kmail now remembers the position it had when exiting kmail through the tray. So that might be a workaround if someone encounters the same problem :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 464459] New: Input-settings in xorg .conf files are overwritten by plasma
https://bugs.kde.org/show_bug.cgi?id=464459 Bug ID: 464459 Summary: Input-settings in xorg .conf files are overwritten by plasma Classification: Plasma Product: plasmashell Version: 5.26.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Startup process Assignee: plasma-b...@kde.org Reporter: mat.muel...@mailbox.org CC: k...@davidedmundson.co.uk Target Milestone: 1.0 SUMMARY I've tried setting a different mouse sensitivity for the touchpad (is treated as a mouse though) on my wireless couch-keyboard. Works like a charm with "xinput set-prop", but won't work when put into a xorg .conf file. In the xorg-log, it seems to be applied, but when doing a 'xinput list-props xx", it is back to the old value. When trying "startx /usr/bin/xterm", it gets applied properly and is correctly listed in list-props. So it seems that plasma is doing something that overwrites these settings after they are applied by X11. Options that are affected from my experiments are at least "AccelProfile" and "AccelSpeed", i haven't really tested other ones though. I guess the options are applied according to what is set in the mouse section of system settings - in there, there is no possibility to set separate values for different mice though. It seems there are a few other inactive bugreports that share the same origin: https://bugs.kde.org/show_bug.cgi?id=435247 https://bugs.kde.org/show_bug.cgi?id=357194 https://bugs.kde.org/show_bug.cgi?id=339743 STEPS TO REPRODUCE 1. create .conf file in "/etc/X11/xorg.conf.d" 2. Specify InputClass with AccelSpeed Option - my example: Section "InputClass" Identifier "touchpad-sens" MatchDriver "libinput" MatchIsPointer "true" MatchProduct "2.4G Receiver" Option "AccelProfile" "flat" Option "AccelSpeed" "0.3" EndSection 3. Reboot and see options not applied properly although reported as set in xorg log SOFTWARE/OS VERSIONS Linux/KDE Plasma: Archlinux Kernel 6.1.6 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION Don't know if it matters, but i use SDDM and X11 session, haven't tried on plasma-wayland yet though. Also, i'm not sure if this is a plasmashell but or maybe kwin? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464459] Input-settings in xorg .conf files ignored by plasma
https://bugs.kde.org/show_bug.cgi?id=464459 --- Comment #2 from Matthias Mueller --- (In reply to Nate Graham from comment #1) > Does it not offer the settings you need? I guess you could say so, yes. ^^ Changing the mouse-settings in ksystemsettings affects all attached mice equally/offers no option to change them individually. Maybe i should have clarified that i want to change the sensitivity of the couch-keyboard only, while leaving the sens of the desktop mouse as is - sorry for that confusion. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 464459] Input-settings in xorg .conf files ignored by Plasma on X11
https://bugs.kde.org/show_bug.cgi?id=464459 --- Comment #4 from Matthias Mueller --- I knew i should have checked on wayland, too! It's not possible on X11 though. Well, if it is already implemented in wayland i guess the main question is how much effort it would be to port it over (i don't know how similar the codepaths for wayland and X11 are in that regard?). If it's a lot of work and already implemented in the futureproof version, i'd almost say it's too much of a niche usecase to put too much effort into it, isn't it? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433138] Since update to 5.21, system tray icons on a very thin panel are smaller
https://bugs.kde.org/show_bug.cgi?id=433138 --- Comment #29 from Matthias Mueller --- I'm now on 5.21.5 and still got the same issue - see my earlier screenshot - i somehow can't believe THAT should be intentional?! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437549] New: Icons too big on vertical panel
https://bugs.kde.org/show_bug.cgi?id=437549 Bug ID: 437549 Summary: Icons too big on vertical panel Product: plasmashell Version: 5.21.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: mat.muel...@mailbox.org CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 138706 --> https://bugs.kde.org/attachment.cgi?id=138706&action=edit Panel with "fit to width" and "small icons" in comparison For a while now (i think since 5.21?), the icons in the system tray applet are way too big on a vertical panel, if option "fit to width" is used (and much too small if "small icons" is used ;) ). It's like the icon-size is calculated without any padding (well seen at the anydesk or element-icons in my screenshot) I initially thought this was related to https://bugs.kde.org/show_bug.cgi?id=433138 , but that assumption was wrong it seems. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437549] Icons too big on vertical panel
https://bugs.kde.org/show_bug.cgi?id=437549 --- Comment #1 from Matthias Mueller --- Created attachment 138707 --> https://bugs.kde.org/attachment.cgi?id=138707&action=edit Comparison vertical/horizontal panel Both panels have "fit to width"/"fit to height" active and a panel height of 50 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437549] Icons too big on vertical panel
https://bugs.kde.org/show_bug.cgi?id=437549 --- Comment #4 from Matthias Mueller --- If fit to width would be working correctly, then fit to height wouldn't. and as the icons are way bigger than anything else (see task manager for example), i think my first explanation makes more sense ^^ And i specifically removed the margin separator on the horizontal default-panel to show the same state (as margin separator doesn't work on vertical panels, but that's an other bug i guess). What exactly would you want to see in edit mode? I just tried to take a screenshot and noticed it looks exactly as without editing (i guess you want to make sure no margin separator is present?) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 381257] KMail does not remember window size or position
https://bugs.kde.org/show_bug.cgi?id=381257 --- Comment #4 from Matthias Mueller --- it's gotten much more rare for me that it doesn't remember the correct size and position, that much i can confirm. I'd say the instances where it is launched in the wrong place are mostly after crashes or forced reboots or the like, but i'm not 100% positive. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 437549] Icons too big on vertical panel
https://bugs.kde.org/show_bug.cgi?id=437549 --- Comment #6 from Matthias Mueller --- A known and fixed bug is the best bug! Thanks for the heads up :) -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 437908] New: Kmail doesn't move messages on server
https://bugs.kde.org/show_bug.cgi?id=437908 Bug ID: 437908 Summary: Kmail doesn't move messages on server Product: kmailtransport Version: 5.17.1 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mat.muel...@mailbox.org Target Milestone: --- SUMMARY Kmail sometimes doesn't move (move to other folder or delete with trash set to the trash folder on the imap server) messages. So when i delete a message, the next time i look for mails it pops up as unread again. Same goes for moving a message to another folder - on the server it still resides in the old folder, in kmail it's displayed in the new AND the old folder after i hit "look for mails". Seems to me as if the communication with the server is uni-directional and kmail doesn't send actions to the server? It happens with all three providers i've got set up (mailbox.org, web.de and gmx.net) - but only occasionally. If it happens, there is no error message. I couldn't find any kmail logs, so if there is more information i could provide, please tell me. I'm also not sure if kmailtransport or kmail2 is the right place - kmail2 doesn't offer the 5.17.1 version though ;) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 KMail Version: 5.17.1 (21.04.1) -- You are receiving this mail because: You are watching all bug changes.
[kmailtransport] [Bug 437908] Kmail doesn't move messages on server
https://bugs.kde.org/show_bug.cgi?id=437908 --- Comment #1 from Matthias Mueller --- Just tried to get more info out of akonadi console, but if i move a message there, the same issue arises -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 434478] New: kdeinit5 crashes when spectacle shows a notification
https://bugs.kde.org/show_bug.cgi?id=434478 Bug ID: 434478 Summary: kdeinit5 crashes when spectacle shows a notification Product: kio-extras Version: 20.12.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Thumbnails and previews Assignee: plasma-b...@kde.org Reporter: mat.muel...@mailbox.org Target Milestone: --- Created attachment 136725 --> https://bugs.kde.org/attachment.cgi?id=136725&action=edit crashlog of kdeinit5 SUMMARY kdeinit5 segfaults when taking a screenshot with spectacle since update from Framework 5.79 to 5.80 STEPS TO REPRODUCE 1. take a screenshot with spectacle that causes a notification popup with a preview (for example super+printscreen for the active window) 2. see the notification pop up with the thumbnail 3. see kdeinit5 crash dialogue OBSERVED RESULT kdeinit5 crashes EXPECTED RESULT no crash ;) This happens after the last Manjaro Update, i guess because of framework 5.79->5.80. I can upload a detailed update log if needed. KDE Plasma Version: 5.21.2 KDE Frameworks Version: 5.80.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION First reported by another user in the update thread - so unlikely to be a local issue. I found https://bugs.kde.org/show_bug.cgi?id=430862 that might be related? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 413111] Create a "Breeze Light" theme to mirror "Breeze Dark", allowing people to force all GTK apps to be light or dark rather than following the KDE color scheme
https://bugs.kde.org/show_bug.cgi?id=413111 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #16 from Matthias Mueller --- I'd like to add to the wish for "forced" dark or light breeze GTK. I use Breeze Dark as a main theme and when i use Breeze for GTK, applications that have a darkmode-switch (like for example lutris) use the Breeze-Dark colorset. If the application does not have a darkmode-switch (like for example prusaslicer), it uses the light Breeze colorset. So i would wish for distinct Breeze-Light-GTK and Breeze-Dark-GTK themes :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433138] Since update to 5.21, system tray icons on a very thin panel are smaller
https://bugs.kde.org/show_bug.cgi?id=433138 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #8 from Matthias Mueller --- Created attachment 136142 --> https://bugs.kde.org/attachment.cgi?id=136142&action=edit Icon Sizes in 5.21 Tray i can also confirm an undesirable change in the icon size. I've got a vertical panel and after updating to 5.21 the icons with the setting "fit to panel size" are way bigger than before, "small" icons are (i think?) even smaller than before. Ideally the icons with setting "fit to size" should be the same size as in the taskbar for the running programs imho. In 5.20, that was (at least roughly) the case when using "fit to size" (at least with my panel width 50) -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433246] Pipewire is missing pulseaudio modules
https://bugs.kde.org/show_bug.cgi?id=433246 --- Comment #8 from Matthias Mueller --- I've just updated to 5.21.1 and it seems now the behaviour is almost like "Automatically switch all running streams when a new output becomes available" was active (but it's still greyed out). So all streams on the current default-sink are switched when changing the default, but any stream that was on another sink stays there. So for me, this issue is kind of resolved, but for people who DON'T want that behaviour or need/want the combined output it might still be relevant. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433138] Since update to 5.21, system tray icons on a very thin panel are smaller
https://bugs.kde.org/show_bug.cgi?id=433138 --- Comment #14 from Matthias Mueller --- The i guess we shouldn't mark this report as resolved fixed as it originally is about the size and not the blurriness? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 433138] Since update to 5.21, system tray icons on a very thin panel are smaller
https://bugs.kde.org/show_bug.cgi?id=433138 --- Comment #16 from Matthias Mueller --- I don't know if resolved is even the right category - even if it is intentionally, it still looked way better before imho. Or are suggestions/requests tracked elsewhere that i don't know of yet? -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 433715] New: krunner crashes when input contains a quote
https://bugs.kde.org/show_bug.cgi?id=433715 Bug ID: 433715 Summary: krunner crashes when input contains a quote Product: krunner Version: 5.21.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: mat.muel...@mailbox.org CC: plasma-b...@kde.org Target Milestone: --- SUMMARY krunner crashes when you type a quotation mark into it. Was observed by me and another manjaro-user in an update-thread. STEPS TO REPRODUCE 1. type a single ( ' ) or double quote ( " ) in krunner 2. observe crash ;) SOFTWARE/OS VERSIONS KDE Plasma Version: 5.21.1 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION here are three core dumps from said other user: Stack trace of thread 22637: #0 0x7f465480bc92 _ZN6KShell11tildeExpandERK7QString (libKF5CoreAddons.so.5 + 0x62c92) #1 0x7f463808a74b n/a (krunner_locations.so + 0x374b) #2 0x7f464c136ca8 _ZN6Plasma14AbstractRunner12performMatchERNS_13RunnerContextE (libKF5Runner.so.5 + 0xfca8) #3 0x7f464c141095 n/a (libKF5Runner.so.5 + 0x1a095) #4 0x7f464c114709 _ZN12ThreadWeaver8Executor3runERK14QSharedPointerINS_12JobInterfaceEEPNS_6ThreadE (libKF5ThreadWeaver.so.5 + 0x1a709) #5 0x7f464c113722 _ZN12ThreadWeaver3Job7executeERK14QSharedPointerINS_12JobInterfaceEEPNS_6ThreadE (libKF5ThreadWeaver.so.5 + 0x19722) #6 0x7f464c112fb1 _ZN12ThreadWeaver6Thread3runEv (libKF5ThreadWeaver.so.5 + 0x18fb1) #7 0x7f4653c51eff n/a (libQt5Core.so.5 + 0xcdeff) #8 0x7f46531e4299 start_thread (libpthread.so.0 + 0x9299) #9 0x7f46538d9053 __clone (libc.so.6 + 0xff053) Stack trace of thread 22640: #0 0x7f46531f09ba __futex_abstimed_wait_common64 (libpthread.so.0 + 0x159ba) #1 0x7f46531ea260 pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0 + 0xf260) #2 0x7f4653c580c4 _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd40c4) #3 0x7f46548a8095 n/a (libQt5DBus.so.5 + 0x65095) #4 0x7f46548a8762 _ZN23QDBusPendingCallWatcher15waitForFinishedEv (libQt5DBus.so.5 + 0x65762) #5 0x7f464c13c40d n/a (libKF5Runner.so.5 + 0x1540d) #6 0x7f464c136ca8 _ZN6Plasma14AbstractRunner12performMatchERNS_13RunnerContextE (libKF5Runner.so.5 + 0xfca8) #7 0x7f464c141095 n/a (libKF5Runner.so.5 + 0x1a095) #8 0x7f464c114709 _ZN12ThreadWeaver8Executor3runERK14QSharedPointerINS_12JobInterfaceEEPNS_6ThreadE (libKF5ThreadWeaver.so.5 + 0x1a709) #9 0x7f464c113722 _ZN12ThreadWeaver3Job7executeERK14QSharedPointerINS_12JobInterfaceEEPNS_6ThreadE (libKF5ThreadWeaver.so.5 + 0x19722) #10 0x7f464c112fb1 _ZN12ThreadWeaver6Thread3runEv (libKF5ThreadWeaver.so.5 + 0x18fb1) #11 0x7f4653c51eff n/a (libQt5Core.so.5 + 0xcdeff) #12 0x7f46531e4299 start_thread (libpthread.so.0 + 0x9299) #13 0x7f46538d9053 __clone (libc.so.6 + 0xff053) Stack trace of thread 22636: #0 0x7f46538d3a9d syscall (libc.so.6 + 0xf9a9d) #1 0x7f4653c52256 _ZN11QBasicMutex12lockInternalEv (libQt5Core.so.5 + 0xce256) #2 0x7f4653c5808f _ZN14QWaitCondition4waitEP6QMutex14QDeadlineTimer (libQt5Core.so.5 + 0xd408f) #3 0x7f464c1117c1 _ZN12ThreadWeaver6Weaver36takeFirstAvailableJobOrSuspendOrWaitEPNS_6ThreadEbbb (libKF5ThreadWeaver.so.5 +
[krunner] [Bug 433715] krunner crashes when input contains a quote
https://bugs.kde.org/show_bug.cgi?id=433715 --- Comment #2 from Matthias Mueller --- Fixed even before the bug report, excellent! :D -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 433246] Pipewire is missing pulseaudio modules
https://bugs.kde.org/show_bug.cgi?id=433246 --- Comment #9 from Matthias Mueller --- Sadly, the first impression was wrong. While it sometimes works that way, it doesn't switch running streams over always, i haven't yet figured out when it happens or not. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 402693] Error "This device is already mounted at /media/user/XXXX" when mounting encrypted LUKS partitions
https://bugs.kde.org/show_bug.cgi?id=402693 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #1 from Matthias Mueller --- It seems the decrypted drive is mounted according to crypttab/fstab, but expected to be mounted in /dev/dm-x -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 412851] New: Mounting external encrypted LUKS partition ignores keyfile
https://bugs.kde.org/show_bug.cgi?id=412851 Bug ID: 412851 Summary: Mounting external encrypted LUKS partition ignores keyfile Product: dolphin Version: 19.08.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: panels: places Assignee: dolphin-bugs-n...@kde.org Reporter: mat.muel...@mailbox.org CC: kfm-de...@kde.org Target Milestone: --- I've setup my external drives in crypttab with a specified keyfile. But when decrypting/mounting these drives via dolphin, i get the password dialoge. Everything else (mapping, mountpoint) in crypttab and fstab seems to be respected (besides https://bugs.kde.org/show_bug.cgi?id=402693 ), so i would assume that a keyfile-entry should work, too? My syntax should be OK - my internal drives are decrypted and mounted properly on boot, only difference is the "noauto"-option. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro 5.3 (available in About System) KDE Plasma Version: 19.08 KDE Frameworks Version: 5.62 Qt Version: 5.13.1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410934] Preview of Textfiles in Information Panel unreadable with dark theme
https://bugs.kde.org/show_bug.cgi?id=410934 --- Comment #3 from Matthias Mueller --- Framework is 5.61.0, QT is at 5.13.0. While verifying that the issue still persists i noticed that some "generic" textfiles do come color-coded (.bashrc and .bash_profile for example) - but this doesn't seem to be caused by the file-content, as when i copy .bashrc to .bashrc1, the new file is white again. But going with .(1).bashrc yields colorcoded - so it seems it's dependent on file extension? After all i would assume that the file extension is parsed to view files like .py, .yml, .sh with colorcoded text? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410934] Preview of Textfiles in Information Panel unreadable with dark theme
https://bugs.kde.org/show_bug.cgi?id=410934 --- Comment #4 from Matthias Mueller --- I just noticed that a PKGBUILD file is also colored without any extension, so it's not just that. -- You are receiving this mail because: You are watching all bug changes.
[plasma-browser-integration] [Bug 394126] Blacklist site from integrating with Media Player
https://bugs.kde.org/show_bug.cgi?id=394126 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #7 from Matthias Mueller --- I'm adding my vote for a blacklisting-option - in my case it's mainly 9gag thats showing up all the time once a single video is played until the tab is closed. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 410493] New: Mouse configuration options missing when using libinput
https://bugs.kde.org/show_bug.cgi?id=410493 Bug ID: 410493 Summary: Mouse configuration options missing when using libinput Product: systemsettings Version: 5.16.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_mouse Assignee: unassigned-b...@kde.org Reporter: saldo...@mailbox.org CC: unassigned-b...@kde.org Target Milestone: --- When using libinput, the mouse configuration is pretty limited compared to the evdev mouse KCM. My personal main issue is the missing "drag start distance" and "drag start time", but there are several other reports about scroll speed: https://bugs.kde.org/show_bug.cgi?id=403843 https://bugs.kde.org/show_bug.cgi?id=403842 There have been other related reports: https://bugs.kde.org/show_bug.cgi?id=398610 https://bugs.kde.org/show_bug.cgi?id=374311 And a corresponding report over at QT: https://bugreports.qt.io/browse/QTBUG-57849 As it sounded like it was not possible to access this configurations with libinput, i filed a report there, in which nate corrected me: https://gitlab.freedesktop.org/libinput/libinput/issues/333 So i'm creating this one as a kind of "collect all" report ;) -- You are receiving this mail because: You are watching all bug changes.
[Touchpad-KCM] [Bug 403843] Libinput touchpad KCM needs a scroll speed setting
https://bugs.kde.org/show_bug.cgi?id=403843 Matthias Mueller changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=410493 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 410493] Mouse configuration options missing when using libinput
https://bugs.kde.org/show_bug.cgi?id=410493 Matthias Mueller changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=403842, ||https://bugs.kde.org/show_b ||ug.cgi?id=403843 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 403842] Libinput mouse KCM lost the scroll speed setting that was present in the evdev version
https://bugs.kde.org/show_bug.cgi?id=403842 Matthias Mueller changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=410493 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 410493] "Drag start distance" configuration option missing when using Libinput
https://bugs.kde.org/show_bug.cgi?id=410493 --- Comment #6 from Matthias Mueller --- As this won't be too many configuration options (if i understood correct?), i see no issue in adding them to workspace behaviour. One thing to consider might be hiding these options in workspace behaviour when evdev is used though. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 410934] New: Preview of Textfiles in Information Panel unreadable with dark theme
https://bugs.kde.org/show_bug.cgi?id=410934 Bug ID: 410934 Summary: Preview of Textfiles in Information Panel unreadable with dark theme Product: dolphin Version: 19.04.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: panels: information Assignee: dolphin-bugs-n...@kde.org Reporter: saldo...@mailbox.org Target Milestone: --- I'm using breeze dark and noticed that when i view textfiles in dolphins information panel, the text there has the default color (white-ish), but also a white background and is thus not readable. I don't think this is a theming issue as i didn't find any way to set the test color for the preview. Setting the background of the preview to something other than white could lead to new issues with theming, so i think it would be best to simply default to black text on white ground for the preview? -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 411196] gwenview very slow to launch
https://bugs.kde.org/show_bug.cgi?id=411196 Matthias Mueller changed: What|Removed |Added CC||mat.muel...@mailbox.org --- Comment #11 from Matthias Mueller --- I can confirm that clearing the clipboard yielded a fast start again. Gwenview 19.12.1 Betriebssystem: Manjaro Linux KDE-Plasma-Version: 5.17.5 KDE-Frameworks-Version: 5.66.0 Qt-Version: 5.14.0 Kernel-Version: 5.4.13-2-MANJARO -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 Matthias Mueller changed: What|Removed |Added CC||saldo...@mailbox.org --- Comment #3 from Matthias Mueller --- can confirm behaviour (CalDAV and CardDAV) on a Mailbox.org server with KAddressBook/KOrganizer Version 5.10.1 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 380012] CalDAV-sync not working with Communigate
https://bugs.kde.org/show_bug.cgi?id=380012 --- Comment #4 from Matthias Mueller --- just found seemingly related: https://phabricator.kde.org/D8843 -- You are receiving this mail because: You are watching all bug changes.
