[Plasma SDK] [Bug 465893] Lookandfeelexplorer incorporates background image but in a not-working way
https://bugs.kde.org/show_bug.cgi?id=465893 Frank changed: What|Removed |Added CC||frankeba...@gmail.com --- Comment #1 from Frank --- I support this. We have identified the same issue since 5.27 has been released, although it was not present in kde-git before 5.27. -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 465893] Lookandfeelexplorer incorporates background image but in a not-working way
https://bugs.kde.org/show_bug.cgi?id=465893 Frank changed: What|Removed |Added Version|5.26.90 |5.27.0 -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 465893] Lookandfeelexplorer incorporates background image but in a not-working way
https://bugs.kde.org/show_bug.cgi?id=465893 --- Comment #2 from Frank --- The scripting we are using is: var allDesktops = desktops(); print (allDesktops); for (i=0;i
[Spectacle] [Bug 466444] New: Rectangle selection blanks out monitors.
https://bugs.kde.org/show_bug.cgi?id=466444 Bug ID: 466444 Summary: Rectangle selection blanks out monitors. Classification: Applications Product: Spectacle Version: 22.08.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: frank.so...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY When in multi-monitor if scale set to 125% or if one monitor is scaled differntly than the others when using rectangular region all sceens will blank out. You can select an image you just cannot see what you are doing. If all set to any scale other than 125% it works as normal. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. There are two ways to reproduce this bug either set all monitors to 125% scale or have one of three monitors set to a different scale than the rest of the monitors. 2. When you press the shorcut for rectange selection all thre monitors blank out. 3. This only happens at 125% or if all screens are not set to the same scale OBSERVED RESULT All screens blank out, you can select an image but you cannot see what you are doing. EXPECTED RESULT Normal screen grab selection operation SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 22.10 x86_64 / Plasma 5.27.0 (available in About System) KDE Plasma Version: Plasma 5.27.0 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 466357] Flickering in systray for apps that change tooltip or on mouse hover
https://bugs.kde.org/show_bug.cgi?id=466357 Frank changed: What|Removed |Added CC||frankeba...@gmail.com --- Comment #5 from Frank --- Thank you for fixing this! I have this issue with qbittorrent and MEGASync icons, both are black and white. My qbittorrent icon is a different one than the one on the original screenshot but it's the same flickering behavior. Happy to see it part of the list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470555] Left-clicking app icon in system tray does not consistently open apps, instead it activates the right-click context menu
https://bugs.kde.org/show_bug.cgi?id=470555 Frank changed: What|Removed |Added CC||glub...@yahoo.co.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470554] Left-clicking app icon in system tray does not consistently open apps, instead it activates the right-click context menu
https://bugs.kde.org/show_bug.cgi?id=470554 --- Comment #3 from Frank --- It is a bug actually, but not with Plasma directly. Seems to be an issue with Electron-based apps. More discussion of it here: https://github.com/electron/electron/issues/14941 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470554] Left-clicking app icon in system tray does not consistently open apps, instead it activates the right-click context menu
https://bugs.kde.org/show_bug.cgi?id=470554 --- Comment #4 from Frank --- More info, looks like an open bug: https://github.com/electron/electron/issues/37112 -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 460149] New: Czech language keyboard layout not working properly
https://bugs.kde.org/show_bug.cgi?id=460149 Bug ID: 460149 Summary: Czech language keyboard layout not working properly Classification: Applications Product: khelpcenter Version: 5.7.6.21123 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: fsd...@gmail.com Target Milestone: --- SUMMARY *** Uppercase letters with caron (i.e. Ď, Ň, Ř, Š, Ť, Ž cannot be reached). Further on ť and ď are missing. German umlaut which is present on Czech typewriters (ä, ö, ü, Ä, Ö, Ü) does not work neither. It works in Firefox (I typed the characters here but no other app I tried works i.e kwrite, Libreoffice) I set the layout switcher shortcut to both Ctrl and switching policy to system wide. Whenever I change the focus to another app the layout switches back to US. *** STEPS TO REPRODUCE 1. Add Czech Layout in Keyboard Settings 2. Try all Variants 3. Try typing mentioned characters OBSERVED RESULT Works in Firefox only, does not work in no other app EXPECTED RESULT The Keyboard settings should work in all applications the same way. The keyboard layout should be independent on regional settings i.e. time format, currency ... ADDITIONAL INFORMATION I checked the "Possible Duplicates" below. Du to the fact that all of them are "RESOLVED" and the problem resides I guess I have another problem here. There is a work around: Open some web page with an input box, type there and copy the text to the required application. This is VERY ugly tough. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 489005] New: Switching out of the "Spell Check" module says we've made changes
https://bugs.kde.org/show_bug.cgi?id=489005 Bug ID: 489005 Summary: Switching out of the "Spell Check" module says we've made changes Classification: Applications Product: systemsettings Version: 6.1.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_spellchecking Assignee: plasma-b...@kde.org Reporter: franciscofabiangutier...@gmail.com Target Milestone: --- First time using plasma and it is a pleasant experience. Haven't tried a new non-minimal-wm in a long time. I like going through the settings and configurations to see what features are available. When I came across the spell check I didn't see anything that caught my eye and moved to another module, but the warning that it has been edited pops up. It pops up again and again every time I visit that module. Not the other modules though STEPS TO REPRODUCE 1. Open up settings 2. Editted a setting somewhere else 3. Click on the Spell Check Module 4. Click on another module (Like the Region & Language) Observed: "The settings of the current module have changed" pop up message. Nothing unusual about the pop up, just that it appears. EXPECTED RESULT No pop up at all. SOFTWARE/OS VERSIONS Linux: Arch KDE Plasma Version: Qt Version: 6 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 478489] New: Plasma 6 Panel - Unable to set property "Length" through API Scripting
https://bugs.kde.org/show_bug.cgi?id=478489
Bug ID: 478489
Summary: Plasma 6 Panel - Unable to set property "Length"
through API Scripting
Classification: Plasma
Product: plasma-integration
Version: 5.90.0
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: frankeba...@gmail.com
Target Milestone: ---
Created attachment 164151
--> https://bugs.kde.org/attachment.cgi?id=164151&action=edit
How to from GUI
SUMMARY
***
In Plasma 6 with new very much improved Panel, I am unable to set property
"Length" through API Scripting.
I am also unable to find documentation on all of the Plasma 6 Panel's
properties that can be used through API Scripting.
Tried the following documentation:
https://userbase.kde.org/Plasma/Create_a_Global_Theme_Package
https://userbase.kde.org/Plasma/How_to_create_a_Unity-like_look_and_feel_theme_using_Plasma%E2%80%99s_Desktop_Scripting_API
https://develop.kde.org/docs/plasma/
***
STEPS TO REPRODUCE
1. Use org.kde.plasma.desktop-layout.js to create a Global Theme, which
creates, among other things, a bottom Panel ("Floating Dock" to be more
precise).
2. From the following section:
// Create bottom panel (Dock)
const dock = new Panel
// Basic Dock Geometry
dock.alignment = “center”
dock.height = Math.round(gridUnit * 2.8);
dock.hiding = “windowscover”
dock.location = “bottom”
dock.panelLength = 1
dock.maximumLenth = 1000
dock.minimumLength = 250
Try various possibilities for the line "dock.panelLength = 1" (panelLengthMode,
length, lengthMode, etc…).
3. Remove the Max and Min length lines (last 2) from the script above and try
step 2 again.
OBSERVED RESULT
The Panel does not Fit Content and remain "Fill Width" in all 8 tries.
EXPECTED RESULT
File ~/.config/plasmashellrc should have a line with "panelLengthMode = 1"
under [PlasmaViews][Panel nnn] section, where "nnn" is a number.
See attached screenshot for what I am trying to achieve, which is extremely
easy through GUI, but I need to set it through API.
Thank you very much for your guidance!
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Yes, it's the best!
KDE Plasma Version: 5.90.90
KDE Frameworks Version: 5.247.0
Qt Version: 6.6.1
ADDITIONAL INFORMATION
I don't believe there is a bug here, at least not at this moment judging how
not far I went with it. :)
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 478489] Plasma 6 Panel - Ability to set lengthMode through API Scripting
https://bugs.kde.org/show_bug.cgi?id=478489
--- Comment #4 from Frank ---
(In reply to fanzhuyifan from comment #3)
> As a work around, just do `panel.setConfig("panelLengthMode", 1)` for
> setting fit.
Thanks for the suggestion.
I'm missing something. Here's one of the 5 or 6 versions I tried following
re-reading this documentation
https://develop.kde.org/docs/plasma/scripting/api/#applets-containments-and-widgets
var plasma = getApiVersion(1)
-
// Create bottom panel (Dock) //
const dock = new Panel
// Basic Dock Geometry
dock.alignment = "center"
dock.height = Math.round(gridUnit * 2.8);
dock.hiding = "windowscover"
dock.location = "bottom"
//dock.maximumLenth = 1000
//dock.minimumLength = 250
// Icons-Only Task Manager
var tasks = dock.addWidget("org.kde.plasma.icontasks")
tasks.currentConfigGroup = ["General"]
tasks.writeConfig("fill", false)
tasks.writeConfig("iconSpacing", 2)
tasks.writeConfig("launchers",
"applications:garuda-welcome.desktop,applications:org.kde.konsole.desktop,preferred://browser,preferred://filemanager,applications:org.kde.plasma-systemmonitor.desktop,applications:snapper-tools.desktop,applications:systemsettings.desktop,applications:octopi.desktop")
tasks.writeConfig("maxStripes", 1)
tasks.writeConfig("showOnlyCurrentDesktop", false)
tasks.writeConfig("showOnlyCurrentScreen", false)
const panel = ConfigFile('plasmashellrc')
panel.group = 'PlasmaViews'
panel.setConfig("panelLenghtMode", 1)
// End of Dock creation //
-
Nothing is written in plasmashellrc.
However if I use instead panel.writeEntry("panelLenghtMode", 1), I do get the
following section written in plasmashellrc:
[PlasmaViews]
panelLenghtMode=1
It's alone in its own section, not associated to a Panel.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 478489] Plasma 6 Panel - Ability to set lengthMode through API Scripting
https://bugs.kde.org/show_bug.cgi?id=478489 --- Comment #6 from Frank --- (In reply to fanzhuyifan from comment #5) > Sorry I meant `writeConfig`, not `setConfig`. Tried it part of my tests with same result, therefore plz read below: > Also for support please use the KDE forums or the matrix channels. The > bugzilla is only for reporting bugs. That's true, sorry about that. This is the correct Forum? https://discuss.kde.org/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478576] New: Plasma 6 System Tray Applet - Ability to set scaleIconsToFit through API Scripting
https://bugs.kde.org/show_bug.cgi?id=478576 Bug ID: 478576 Summary: Plasma 6 System Tray Applet - Ability to set scaleIconsToFit through API Scripting Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: frankeba...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 Created attachment 164209 --> https://bugs.kde.org/attachment.cgi?id=164209&action=edit Scale Icons SUMMARY *** We use Plasma API Scripting for our distro’s Global Theme and setting the property "scaleIconToFit" in the systray is becoming more important with time. There are use cases where this is interesting, because it keeps a consistent size along with other icons like Task Manager. There is a vast array of screen resolutions used nowadays, therefore building a Theme for say 1920x1080 resolution doesn't make this aspect transient seamlessly for someone using it in a say 3840x2160 resolution, because the systray icons are set to Small no matter the Y pixel resolution. It it is also very handy for those who often switch from say a big 2160 external monitor to a lower 1080 laptop monitor. I have read many documentations like https://develop.kde.org/docs/plasma/scripting/api/#applets-containments-and-widgets but no matter what I try to code in layout.js it does not apply that setting. STEPS TO REPRODUCE 1. Use code in script following documentation above 2. Apply the Theme OBSERVED RESULT In ~/.config/plasma-org.kde.plasma.desktop-appletsrc the config is written in a different group/subgroup, with "Applets", so it doesn't set the property. === [Containments][1][Applets][9][Configuration] === EXPECTED RESULT The second to last line should be written in the below Group: === [Containments][10][General] extraItems=org.kde.kdeconnect,org.kde.kscreen,org.kde.plasma.battery,org.kde.plasma.bluetooth,org.kde.plasma.clipboard,org.kde.plasma.devicenotifier,org.kde.plasma.keyboardindicator,org.kde.plasma.keyboardlayout,org.kde.plasma.manage-inputmethod,org.kde.plasma.mediacontroller,org.kde.plasma.networkmanagement,org.kde.plasma.nightcolorcontrol,org.kde.plasma.notifications,org.kde.plasma.volume knownItems=org.kde.kdeconnect,org.kde.kscreen,org.kde.plasma.battery,org.kde.plasma.bluetooth,org.kde.plasma.clipboard,org.kde.plasma.devicenotifier,org.kde.plasma.keyboardindicator,org.kde.plasma.keyboardlayout,org.kde.plasma.manage-inputmethod,org.kde.plasma.mediacontroller,org.kde.plasma.networkmanagement,org.kde.plasma.nightcolorcontrol,org.kde.plasma.notifications,org.kde.plasma.volume scaleIconsToFit=true shownItems=org.kde.plasma.volume,org.kde.plasma.battery === SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478576] Plasma 6 System Tray Applet - Ability to set scaleIconsToFit through API Scripting
https://bugs.kde.org/show_bug.cgi?id=478576 Frank changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478582] New: Plasma 6 Folder Applet - Ability to set Contextual Menu Plugins through API scripting
https://bugs.kde.org/show_bug.cgi?id=478582 Bug ID: 478582 Summary: Plasma 6 Folder Applet - Ability to set Contextual Menu Plugins through API scripting Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Folder Assignee: plasma-b...@kde.org Reporter: frankeba...@gmail.com CC: h...@kde.org Target Milestone: 1.0 Created attachment 164212 --> https://bugs.kde.org/attachment.cgi?id=164212&action=edit Contextual Menu Plugins SUMMARY *** We use Plasma API Scripting for our distro’s Global Theme and setting specific Contextual Menu Plugins allows more flexibility for the UX and better overall experience of the Theme. Mainly the plugin LEAVE, accessible when right-clicking the mouse anywhere on the desktop wallpaper to call the context menu (mouse actions/right-button). Currently Plasma allows to access the "Leave" actions through the Application Launcher. This requires to drag the mouse to the App Launcher and click on the desired action. It's a 3-click operation, 4 if you want to Lock, Logout or Switch User. I am proposing a faster alternative (without removing the default one) that doesn't take user space and that is a 3-click-no-mouse-draggin operation for all actions. This is possible by including the "Leave" action when right-clicking on the desktop. I believe this makes the user's workflow faster and smoother. Same goes with the action "Lock Screen", which would then be accessible faster. I think it would be interesting to have Plasma default to these, but if it doesn't, at least to have the ability to set those actions through API would help increase the UX for the Global Themes in which it fits well to have these features included. I have read many documentations like https://develop.kde.org/docs/plasma/scripting/api/#applets-containments-and-widgets but no matter what I try to code in layout.js it does not apply that setting. I cannot seem to write in the group [ActionPlugins][0][RightButton;NoModifier]. STEPS TO REPRODUCE 1. Use code in script following documentation above 2. Apply the Theme OBSERVED RESULT In ~/.config/plasma-org.kde.plasma.desktop-appletsrc the config is written in a different group/subgroup than required. The closest I could get is: === [Containments][2][ActionPlugins] _logout=true === EXPECTED RESULT It should look like this, in the below groups, in ~/.config/plasma-org.kde.plasma.desktop-appletsrc: === [ActionPlugins][0][RightButton;NoModifier] _add panel=true _context=true _display_settings=true _lock_screen=false _logout=true _open_terminal=false _run_command=false _sep1=true _sep2=true _sep3=true _wallpaper=true add widgets=true configure=true configure shortcuts=false edit mode=true manage activities=true remove=true === SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247 Qt Version: 6.6.1 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478582] Plasma 6 Folder Applet - Ability to set Contextual Menu Plugins through API scripting
https://bugs.kde.org/show_bug.cgi?id=478582 Frank changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483022] New: Icons-Only Task Manager scaling misbehavior/inconsistency on Side Position Panel
https://bugs.kde.org/show_bug.cgi?id=483022 Bug ID: 483022 Summary: Icons-Only Task Manager scaling misbehavior/inconsistency on Side Position Panel Classification: Plasma Product: plasmashell Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: frankeba...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 166817 --> https://bugs.kde.org/attachment.cgi?id=166817&action=edit Machine1-Plasma6-bottom SUMMARY, Observed result and Expected result Since Plasma 6, IOTM scales almost perfectly with the Panel size. However this causes some issues and inconsistencies and has a limiting factor. 1- The icons are too big for the Panel size, unless you use small Panel size, which is small enough so that it's less enjoyable for UX perspective. At a certain smaller size, the icons shrink more relative to the Panel size, which frees up space inside the Panel, but that size is too small. When you increase size from that point, icons increase more than Panel to take all the space and from there they scale 1-1 relative to Panel size. On one machine, for example, in Plasma 5 I was using 100px for a Panel, but on Plasma 6 I need to reduce to 66 in order to free up space around the icons. Obviously those got smaller too! This limits the use of custom Themes because it removes a lot of space around the icons. I could not find a way to change IOTM size relative to Panel size. 2- When moving the Panel to the either side (compared to bottom or top), they take even more space on either side of the icons, which again limits even more than issue #1 because almost anything you try to draw on the sides of the icons is drawn under the face of the icons. No matter where the Panel is located, icons should have the same amount of space all around to keep consistency. That amount of space should be sufficient to allow drawing indicators around the icons, like SVG elements "focus-bottom, focus-right, focus-left, focus-top", etc.. Screen resolution does not seem to affect this, the same behaviors are observed. Plasma Style (Breeze or other ported to Plasma 6) does not seem to affect this either, the same behaviors are observed. The following files will be attached: Machine1-Plasma6-bottom.png Machine1-Plasma6-side.png Machine2-Plasma5-side.png Machine2-Plasma5-side-Scaleddown.png Machine2-Plasma6-side.png SOFTWARE/OS VERSIONS Windows: Not at all macOS: Not either Linux/KDE Plasma: 6.0.1 (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483022] Icons-Only Task Manager scaling misbehavior/inconsistency on Side Position Panel
https://bugs.kde.org/show_bug.cgi?id=483022 --- Comment #1 from Frank --- Created attachment 166818 --> https://bugs.kde.org/attachment.cgi?id=166818&action=edit Machine1-Plasma6-side -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483022] Icons-Only Task Manager scaling misbehavior/inconsistency on Side Position Panel
https://bugs.kde.org/show_bug.cgi?id=483022 --- Comment #2 from Frank --- Created attachment 166819 --> https://bugs.kde.org/attachment.cgi?id=166819&action=edit Machine2-Plasma5-side -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483022] Icons-Only Task Manager scaling misbehavior/inconsistency on Side Position Panel
https://bugs.kde.org/show_bug.cgi?id=483022 --- Comment #3 from Frank --- Created attachment 166820 --> https://bugs.kde.org/attachment.cgi?id=166820&action=edit Machine2-Plasma6-side-Scaleddown -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483022] Icons-Only Task Manager scaling misbehavior/inconsistency on Side Position Panel
https://bugs.kde.org/show_bug.cgi?id=483022 --- Comment #4 from Frank --- Created attachment 166821 --> https://bugs.kde.org/attachment.cgi?id=166821&action=edit Machine2-Plasma6-side -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483172] New: Free Disk Space button margin too wide and cuts off fonts
https://bugs.kde.org/show_bug.cgi?id=483172 Bug ID: 483172 Summary: Free Disk Space button margin too wide and cuts off fonts Classification: Applications Product: dolphin Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: status Assignee: dolphin-bugs-n...@kde.org Reporter: frankeba...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY *** Depending on the Application Theme used (many of the popular kvantum themes have the issue), the area where Dolphin indicates Free Disk Space is cut off. Possible regression in QT6.6. *** STEPS TO REPRODUCE 1. Update to Plasma 6.0.1 with QT6.6 2. Use various kvantum themes OBSERVED RESULT Area of free disk space cut off slightly or almost completely, depending on the theme used. EXPECTED RESULT Area should be fully visible no matter the theme used. SOFTWARE/OS VERSIONS Windows: Nope macOS: Nope Linux/KDE Plasma: Yes! (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Plz refer to these bug reports directly at kvantum for some detailed information with screenshots. https://github.com/tsujan/Kvantum/issues/945 https://github.com/tsujan/Kvantum/issues/951 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 483172] Free Disk Space button margin too wide and cuts off fonts
https://bugs.kde.org/show_bug.cgi?id=483172 --- Comment #1 from Frank --- For quick information, this comment might explain the difference between Dolphin 23.08.5 and 24.02.0. https://github.com/tsujan/Kvantum/issues/951#issuecomment-1987391211 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 488061] New: the tool Image Mosaic Wall will crashes
https://bugs.kde.org/show_bug.cgi?id=488061 Bug ID: 488061 Summary: the tool Image Mosaic Wall will crashes Classification: Applications Product: digikam Version: 8.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: ImageEditor-Plugins Assignee: digikam-bugs-n...@kde.org Reporter: fwi...@web.de Target Milestone: --- Hello, I would like to create a mosaic image using the Image Mosaic Wall... tool (Extras/Image Mosaic Wall..), which works well with the standard grid settings of 100 x 100. However, if I change the grid settings, e.g. 150 x 150, and then click on "Create Mosaic", the entire digikam program usually crashes without an error message. Sometimes you also get an error message that the read operation could not be carried out in the memory. Perhaps you can fix the problem in a future version. Many thanks and best regards Frank STEPS TO REPRODUCE 1. open the Tool Image Mosaic Wall 2. create a mosaic with the default settings 3. change the default settings (for example grid settings 150 x150) 4. click the button "Create Mosaic" the program will crashes immediately OBSERVED RESULT - the program crashes immediately EXPECTED RESULT - creation of the mosaic SOFTWARE/OS VERSIONS Windows: 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 481545] New: by assign name to face application will close
https://bugs.kde.org/show_bug.cgi?id=481545 Bug ID: 481545 Summary: by assign name to face application will close Classification: Applications Product: digikam Version: 8.2.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Faces-Recognition Assignee: digikam-bugs-n...@kde.org Reporter: fwi...@web.de Target Milestone: --- Hello everyone, for me, digiKam crashes when I try to assign the name of a photo to a recognized face using the keyboard (i.e. write). However, if I use the selection function, digiKam does not crash. Am I doing something wrong or is there an error in the program? Thank you and best regards Frank STEPS TO REPRODUCE 1. open image 2. right click -> search for faces 3. right click -> Recognize faces 4. Assign name to face -> enter names using the keyboard -> Application closes OBSERVED RESULT - The application will close EXPECTED RESULT - Name is assigned SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478489] Plasma 6 Panel - Ability to set lengthMode through API Scripting
https://bugs.kde.org/show_bug.cgi?id=478489 --- Comment #8 from Frank --- Tested and working. Thank you so much! This saves our Theming so it can be automatically applied correctly. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483022] Icons-Only Task Manager scaling misbehavior/inconsistency on Side Position Panel
https://bugs.kde.org/show_bug.cgi?id=483022 --- Comment #6 from Frank --- > 3. Edit your preferred theme to have larger margins Thanks, this is my preferred option. Changing the hint-[direction]-margin in panel-background.svgz does change the margins on pretty much all widgets (App Launcher, Sys Tray, Digital Clock), but does not affect IOTM. Is IOTM working differently than other widgets in that manner? -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 451373] New: have not been able to do system update for over 30 days
https://bugs.kde.org/show_bug.cgi?id=451373 Bug ID: 451373 Summary: have not been able to do system update for over 30 days Product: khelpcenter Version: 5.7.6.21122 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-doc-engl...@kde.org Reporter: frankscomput...@gmail.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** have not been able to do system update for over 30 days STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 451373] WindowsFX 11_ have not been able to do system update for over 30 days
https://bugs.kde.org/show_bug.cgi?id=451373 Frank changed: What|Removed |Added Summary|have not been able to do|WindowsFX 11_ have not been |system update for over 30 |able to do system update |days|for over 30 days -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 451373] WindowsFX 11_ have not been able to do system update for over 30 days
https://bugs.kde.org/show_bug.cgi?id=451373 --- Comment #1 from Frank --- Windows11FX_have not been able to do system update for over 30 days -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 451373] WindowsFX 11_ have not been able to do system update for over 30 days
https://bugs.kde.org/show_bug.cgi?id=451373 --- Comment #3 from Frank --- [image: image.png] this is the screen when I try to update. still will not update. here is system info. please help!! Thanks, Frank On Thu, Mar 10, 2022 at 10:10 PM Felipe Kinoshita wrote: > https://bugs.kde.org/show_bug.cgi?id=451373 > > Felipe Kinoshita changed: > >What|Removed |Added > > > Resolution|--- |DOWNSTREAM > Status|REPORTED|RESOLVED > CC||kinof...@gmail.com > > --- Comment #2 from Felipe Kinoshita --- > Please refer to their website: https://windowsfx.org/ > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[khelpcenter] [Bug 451373] WindowsFX 11_ have not been able to do system update for over 30 days
https://bugs.kde.org/show_bug.cgi?id=451373 --- Comment #5 from Frank --- Thanks, I'll check it out. sorry to bother you!! On Sat, Mar 12, 2022 at 1:15 PM Jack wrote: > https://bugs.kde.org/show_bug.cgi?id=451373 > > --- Comment #4 from Jack --- > This is a problem with windowsfx, not with khelpcenter, which is what you > filed > the bug against. If you want help, you need to follow the advice in > Comment #2 > and seek help there. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 451676] New: file saving window
https://bugs.kde.org/show_bug.cgi?id=451676 Bug ID: 451676 Summary: file saving window Product: kolourpaint Version: 20.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kolourpaint-supp...@lists.sourceforge.net Reporter: frab...@gmail.com Target Milestone: --- Version 20.12.0 could not be selected but it works very well on my laptop with Q4OS. One problem: if I want to save my work the window to select an output file becomes very wide, about twice the size of my screen. Dragging the side of the window does not work. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433311] New: New or modified root album folders are always placed into local collections (= Type No 1 in table album roots)
https://bugs.kde.org/show_bug.cgi?id=433311 Bug ID: 433311 Summary: New or modified root album folders are always placed into local collections (= Type No 1 in table album roots) Product: digikam Version: 7.2.0 Platform: Compiled Sources OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Setup-Collections Assignee: digikam-bugs-n...@kde.org Reporter: re...@web.de Target Milestone: --- SUMMARY It seems this https://bugs.kde.org/show_bug.cgi?id=347937 problem is back. STEPS TO REPRODUCE 1. Place an album to network share or removable media 2. Click Ok 3. Reenter the dialog OBSERVED RESULT All folders are placed under local collection EXPECTED RESULT The folders should stay where they were created SOFTWARE/OS VERSIONS Windows: 10 (incl. all updates until Feb. 19th) macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.78.ß Qt Version: 5.15.2 ADDITIONAL INFORMATION When chanaging the type in the table "AlbumRoots" manually from 1 to 2 or 3 and do not touch it in digikam it stays where it is. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433311] New or modified root album folders are always placed into local collections (= Type No 1 in table album roots)
https://bugs.kde.org/show_bug.cgi?id=433311 --- Comment #1 from Frank --- Created attachment 135955 --> https://bugs.kde.org/attachment.cgi?id=135955&action=edit Screenshot from SQL Database -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433311] New or modified root album folders are always placed into local collections (= Type No 1 in table album roots)
https://bugs.kde.org/show_bug.cgi?id=433311 --- Comment #4 from Frank --- (In reply to Maik Qualmann from comment #2) > I don't know what you are doing You shouldn't change the database directly. > Only when you know what you are doing. You can change the collection type in > the digiKam settings in the collection setup via the refresh symbol next to > the trash icon. > > Maik Yes, that was what I tried. But the system do not care and re-placed it back into local collections always. I tried to find out what ist the problem by looking directly into the database and found the behaviour as described. For me it looks as if the dialog always writes a No 1 = local drive into the database on clicking the OK button - independend of the input values -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 433311] New or modified root album folders are always placed into local collections (= Type No 1 in table album roots)
https://bugs.kde.org/show_bug.cgi?id=433311 Frank changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #7 from Frank --- Thanks Maik! I checked the weekly from yesterday: Problem Solved! It works as expected. Best Regards Frank -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447865] Crashing program report | Issue: Fill borders effects.
https://bugs.kde.org/show_bug.cgi?id=447865 --- Comment #3 from Frank --- Fixed, thanks On Sun, Oct 1, 2023, 8:57 AM emohr wrote: > https://bugs.kde.org/show_bug.cgi?id=447865 > > emohr changed: > >What|Removed |Added > > > Status|REPORTED|RESOLVED > Resolution|--- |FIXED > > --- Comment #2 from emohr --- > With version 23.08.1 the crash doesn't happen anymore. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 447110] New: Samba-share / Network-share preview does not work
https://bugs.kde.org/show_bug.cgi?id=447110 Bug ID: 447110 Summary: Samba-share / Network-share preview does not work Product: dolphin Version: 21.12.0 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: f.nat...@sherart.com CC: kfm-de...@kde.org Target Milestone: --- The preview function of Dolpin works fine on the local file system on my Neon dist. But it does not work on remote filesystems, like samba or webdav. Samba attachments were via Dolpin, webdav via system and the remote file size set to 50MB or higher. I rebooted after setting this values, and/or created a new user both show the same result. Looks like Dolpin is ignoring the preview on remote filesystems. *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Enable preview for remote files in the config menu by increasing the file size. Press Ok or confirm 2. Nothing changes by viewing remote folders. 3. OBSERVED RESULT EXPECTED RESULT See preview SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: NEON 5-23 (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.89.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 447865] New: Crashing program report | Issue: Fill borders effects.
https://bugs.kde.org/show_bug.cgi?id=447865 Bug ID: 447865 Summary: Crashing program report | Issue: Fill borders effects. Product: kdenlive Version: 21.12.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: crash Priority: NOR Component: Effects & Transitions Assignee: vpi...@kde.org Reporter: jfg...@gmail.com Target Milestone: --- Fill borders crashes program when manipulating "Right" levels. SOFTWARE/OS VERSIONS Windows: 10 pro 64 | Version 21H2 AMD FX 8350 8 core -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 432110] Dragging icons/launchers from within dock no longer possible
https://bugs.kde.org/show_bug.cgi?id=432110 Frank changed: What|Removed |Added Summary|Draggin icons/launchers |Dragging icons/launchers |from within dock no longer |from within dock no longer |possible|possible -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 432110] Dragging icons/launchers from within dock no longer possible
https://bugs.kde.org/show_bug.cgi?id=432110 --- Comment #2 from Frank --- I confirm the fix with latest git version. Thank you! :) Who should close the ticket? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 424023] New: Portions of plasma randomly reports a crash at startup
https://bugs.kde.org/show_bug.cgi?id=424023 Bug ID: 424023 Summary: Portions of plasma randomly reports a crash at startup Product: plasmashell Version: 5.19.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: frank.herb...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.19.2) Qt Version: 5.15.0 Frameworks Version: 5.71.0 Operating System: Linux 5.7.7-1-default x86_64 Windowing system: X11 Distribution: "openSUSE Tumbleweed" -- Information about the crash: - What I was doing when the application crashed: Plasma randomly shows me crash reports at startup and exhibits some odd behavior - Unusual behavior I noticed: One of my screens shows a black background and the right click menu will not appear, at random. Often restarting the session will fix it. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x in () #5 0x7f99cb3f2ca4 in Plasma::DataEngineManager::unloadEngine(QString const&) (name=..., this=0x7f99cb447710 ) at /usr/src/debug/plasma-framework-5.71.0-3.1.x86_64/src/plasma/private/dataenginemanager.cpp:153 #6 0x7f99cb3f2ca4 in Plasma::DataEngineConsumer::~DataEngineConsumer() (this=, this=) at /usr/src/debug/plasma-framework-5.71.0-3.1.x86_64/src/plasma/dataengineconsumer.cpp:84 #7 0x7f994c045744 in WeatherEngine::~WeatherEngine() (this=0x562f4309fce0, this=) at /usr/src/debug/plasma5-workspace-5.19.2-2.1.x86_64/dataengines/weather/weatherengine.cpp:54 #8 0x7f994c045779 in WeatherEngine::~WeatherEngine() (this=0x562f4309fce0, this=) at /usr/src/debug/plasma5-workspace-5.19.2-2.1.x86_64/dataengines/weather/weatherengine.cpp:56 #9 0x7f99cb3ee797 in Plasma::DataEngineManagerPrivate::~DataEngineManagerPrivate() (this=0x562f4180c540, this=) at /usr/src/debug/plasma-framework-5.71.0-3.1.x86_64/src/plasma/private/dataenginemanager.cpp:62 #10 0x7f99cb3ee797 in Plasma::DataEngineManager::~DataEngineManager() (this=0x7f99cb447710 , this=) at /usr/src/debug/plasma-framework-5.71.0-3.1.x86_64/src/plasma/private/dataenginemanager.cpp:102 #11 0x7f99cb3ee879 in Plasma::(anonymous namespace)::Q_QGS_privateDataEngineManagerSelf::innerFunction()::Holder::~Holder() () at /usr/src/debug/plasma-framework-5.71.0-3.1.x86_64/src/plasma/private/dataenginemanager.cpp:87 #12 0x7f99c8f17d67 in __run_exit_handlers () at /lib64/libc.so.6 #13 0x7f99c8f17f0c in () at /lib64/libc.so.6 #14 0x7f99c8dd96df in _XDefaultIOError (dpy=0x562f40f4e980) at XlibInt.c:1310 #15 0x7f99c8ddcede in _XIOError (dpy=dpy@entry=0x562f40f4e980) at XlibInt.c:1526 #16 0x7f99c8de1aec in _XReply (dpy=0x562f40f4e980, rep=0x7f9974ff70e0, extra=0, discard=0) at xcb_io.c:716 #17 0x7f99bd8779b8 in () at /usr/lib64/libGLX_nvidia.so.0 #18 0x7f99bd80c40c in () at /usr/lib64/libGLX_nvidia.so.0 #19 0x7f99bd863611 in () at /usr/lib64/libGLX_nvidia.so.0 #20 0x7f99bd863f28 in () at /usr/lib64/libGLX_nvidia.so.0 #21 0x7f99b7220d87 in () at /usr/lib64/libnvidia-glcore.so.390.138 #22 0x7f99b722100b in () at /usr/lib64/libnvidia-glcore.so.390.138 #23 0x7f99b7221099 in () at /usr/lib64/libnvidia-glcore.so.390.138 #24 0x7f99b6fe034b in () at /usr/lib64/libnvidia-glcore.so.390.138 #25 0x7f99b6fe0483 in () at /usr/lib64/libnvidia-glcore.so.390.138 #26 0x7f99b7109e5c in () at /usr/lib64/libnvidia-glcore.so.390.138 #27 0x7f99b7399d70 in () at /usr/lib64/libnvidia-glcore.so.390.138 #28 0x7f99b6e8241c in () at /usr/lib64/libnvidia-glcore.so.390.138 #29 0x7f99caffb017 in QSGBatchRenderer::Renderer::renderBatches() (this=this@entry=0x7f9958144ce0) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/include/QtQuick/5.15.0/QtQuick/private/../../../../../src/quick/scenegraph/coreapi/qsgrenderer_p.h:131 #30 0x7f99caffb922 in QSGBatchRenderer::Renderer::render() (this=) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/scenegraph/coreapi/qsgbatchrenderer.cpp:4324 #31 0x7f99cafe4220 in QSGRenderer::renderScene(QSGBindable const&) (bindable=..., this=0x7f9958144ce0) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:264 #32 0x7f99cafe4220 in QSGRenderer::renderScene(QSGBindable const&) (this=0x7f9958144ce0, bindable=...) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:220 #33 0x7f99cafe46f3 in QSGRenderer::renderScene(unsigned int) (this=, fboId=) at /usr/src/debug/libqt5-qtdeclarative-5.15.0-1.1.x86_64/src/quick/scenegraph/coreapi/qsgrenderer.cpp:212 #34 0x7f99cb043603 in QSGDefaultRenderContext::renderNextFrame(QSGRende
[Akonadi] [Bug 449433] New: Akonadi crashes after disabling standby mode
https://bugs.kde.org/show_bug.cgi?id=449433 Bug ID: 449433 Summary: Akonadi crashes after disabling standby mode Product: Akonadi Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: SendLaterAgent Assignee: mon...@kde.org Reporter: sche...@opensourcemedia.de CC: kdepim-b...@kde.org Target Milestone: --- Created attachment 146117 --> https://bugs.kde.org/attachment.cgi?id=146117&action=edit Developer Information KDE Crash Handling STEPS TO REPRODUCE Don't know exactly either. Had my Linux switched to stand by mode and am a 3 hours back to the computer.After the computer was awake Akonadi crashed and gave out lots of crash messages Operating System: openSUSE Tumbleweed 20220128 KDE Plasma Version: 5.23.5 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.16.2-1-default (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 2700 Eight-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 422413] Browser Identification doesn't work with WebEngine browser engine
https://bugs.kde.org/show_bug.cgi?id=422413 frank changed: What|Removed |Added CC||sk...@legalise.it -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 406821] Dark UI color theme breaks default LightTheme
https://bugs.kde.org/show_bug.cgi?id=406821 --- Comment #18 from Frank --- That's interesting. I run the following: KDE Plasma 5.21.5 KDE Framework 5.82.0 QT 5.15.2 Dolphin 21.04.1 I do not have the issue anymore even when I was on older versions of all 4 above. Maybe there is something specific to Kubuntu? Or maybe the fix was pushed forward into a newer version that you don't have yet. I am not actually sure which of the above 4 really fixes the issue. :( I would need someone with more expertise to clarify this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462222] New: Plasma panel Icons-Only Task Manager widget resizes by a huge number of px at a time
https://bugs.kde.org/show_bug.cgi?id=46 Bug ID: 46 Summary: Plasma panel Icons-Only Task Manager widget resizes by a huge number of px at a time Classification: Plasma Product: plasmashell Version: 5.26.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: frankeba...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 154008 --> https://bugs.kde.org/attachment.cgi?id=154008&action=edit 72px SUMMARY The Icons-Only Task Manager widget does not scale pixel by pixel when changing the size of the panel. Instead you have to increase the size say from 72px to 136 until the icons grow and they then do it by that huge 64px step. On the other way, down from 70px you have to hit 56px for the icons to shrink. This limits a lot the icon size choices for the user. In between two px marks (say 72 and 136 excluded), the icons only space out from themselves rather than scale their size. The exact px number varies, not sure on what, maybe the plasma theme or some chosen configurations, sometimes the 136px mark has been 132px that I have seen, but the behavior is the same: you need to change the panel size by a large number in order to get the icons to scale. Tested in a real machine and tested in a VM with exact same behavior. STEPS TO REPRODUCE 1. Use any Plasma Style (try with Breeze Dark) 2. Create a panel (either floating or not, both have the same behavior) 3. Add Icons-Only Task Manager widget 4. Enter EDIT MODE 5. Change the size of the panel both sides (up and down) OBSERVED RESULT The icons space out (or space in) from themselves until you hit a certain px mark and then they change a lot in size EXPECTED RESULT The icons should scale their size on every px step you change, or at least something a lot smaller than 50px. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Attached screenshots -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462222] Plasma panel Icons-Only Task Manager widget resizes by a huge number of px at a time
https://bugs.kde.org/show_bug.cgi?id=46 --- Comment #1 from Frank --- Created attachment 154009 --> https://bugs.kde.org/attachment.cgi?id=154009&action=edit 134px -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462222] Plasma panel Icons-Only Task Manager widget resizes by a huge number of px at a time
https://bugs.kde.org/show_bug.cgi?id=46 --- Comment #2 from Frank --- Created attachment 154010 --> https://bugs.kde.org/attachment.cgi?id=154010&action=edit 136px -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462222] Plasma panel Icons-Only Task Manager widget resizes by a huge number of px at a time
https://bugs.kde.org/show_bug.cgi?id=46 --- Comment #4 from Frank --- Hi Nicco! I knew you'd respond, I follow all your youtube videos, you are awesome, tnx for your work and clear explanations (both in videos and here)! I understand your explanation about scaling. That's how it is, ok. You know I spent a lot of time finding something about this and no documentation or forum threads gave me any detail, which is why I ended up here. Sorry for reporting something that was intentional in the 1st place. I will just point out that Latte-Dock does scale perfectly the icons without getting blurry. I guess the framwork/architecture behing Latte is much different than Plasma Panel, but if in Plasma 6 this can evolve, I'm sure you will remember. :) Thanks again! :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462253] New: Icons-Only Task Manager "glow icons on mouse hover for closed applications" alternatives
https://bugs.kde.org/show_bug.cgi?id=462253 Bug ID: 462253 Summary: Icons-Only Task Manager "glow icons on mouse hover for closed applications" alternatives Classification: Plasma Product: plasmashell Version: 5.26.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: frankeba...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 154036 --> https://bugs.kde.org/attachment.cgi?id=154036&action=edit Before mouse hover SUMMARY Hello, This is a feature request, or wishlist. Currently when you hover the mouse pointer on an icon (launcher) part of Icons-Only Task Manager widget, it just very faintly glows. Trying over 15 different Plasma Styles and the result is always "glowing icons". Searched in many configuration files, forums, etc. but couldn't find anything to change this. I am not a developer. Since the glow is extremely faint, depending on the icons color, wallpaper, pointer size/type/color, etc., it can take more time for the user's eye to see the visual change and therefore more brain processing time to make sure the pointer is pointing at the right icon. I have personally clicked the wrong icon a couple times already. Also for some users it is not visually appealing to have such a very faint glow. Within Dolphin, or applications, that's fine. But when using a panel as a dock with launchers, something more obvious is required as more efficiency is wanted. It would be interesting to have the ability to change that (very faint) glowing behavior for something else. As an example, Latte-Dock and Cairo-Dock can grow in size (zoom) the icons. Other alternatives could be implemented, like overlaying a solid color with user variable blurriness and opacity, much like an SVG form, which is used say for normal, hover, focused, etc. However it is used only when the application is running/opened. Not asking for anything fancy, but for something efficient. "Efficieny" is the key here, in this wishlist/feature request. STEPS TO REPRODUCE 1. Use Plasma Panel (floating or not) 2. Add Icons-Only Task Manager widget 3. Add at least 1 application launcher in the widget 4. Do not click or open the icon/application, simply hover the mouse pointer on the icon. OBSERVED RESULT Very faint glow. EXPECTED RESULT Other visual alternatives in order to make this feature efficient for the user and improve user's work. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Attached screenshots before and after mouse hover. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462253] Icons-Only Task Manager "glow icons on mouse hover for closed applications" alternatives
https://bugs.kde.org/show_bug.cgi?id=462253 --- Comment #1 from Frank --- Created attachment 154037 --> https://bugs.kde.org/attachment.cgi?id=154037&action=edit After mouse hover -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462253] Icons-Only Task Manager "glow icons on mouse hover for closed applications" alternatives
https://bugs.kde.org/show_bug.cgi?id=462253 --- Comment #3 from Frank --- Yes, merge request 1265 seems to be in the same area. I think I will contact Niccolo on one his platform just to make sure it covers pretty much the same idea. Thanks for pointing out the merge request! :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462253] Icons-Only Task Manager "glow icons on mouse hover for closed applications" alternatives
https://bugs.kde.org/show_bug.cgi?id=462253 --- Comment #5 from Frank --- (In reply to veggero from comment #4) > (In reply to Frank from comment #3) > > Yes, merge request 1265 seems to be in the same area. I think I will contact > > Niccolo on one his platform just to make sure it covers pretty much the same > > idea. > > > > Thanks for pointing out the merge request! :) > > Hey, just FYI, "Bug Janitor Service" is a bot :P It automatically links MRs > in bug reports when such MRs have the bug report id in the description. I've > made the MR after seeing this merge request :) Oh god I must be dumb, I'm blushing right now. loll Not familiar with reporting bugs and feature requests, I usually always find ways to do things on my machine. :) But for the Panel it's different, it needs you. :) Ok so then I understand there is a merge request already for my feature suggestion? I must contribute to your work, seriously, you are extremely efficient and transparent. Thank you very much! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462253] Icons-Only Task Manager "glow icons on mouse hover for closed applications" alternatives
https://bugs.kde.org/show_bug.cgi?id=462253
--- Comment #7 from Frank ---
(In reply to veggero from comment #6)
> be able to add an element
> called "launcher-hover-*" (where * is top, topright, etc) similarly to the
> existing "hover-*" elements in the tasks.svg file of the plasma theme that I
> think you already saw ("much like an SVG form, which is used say for normal,
> hover, focused, etc"). This will allow you to set some kind of more visible
> background, with whatever look you prefer. (Unluckily, blur is not something
> that our SVG viewer supports).
>
> This doesn't change Breeze *by default*, so it does require changing the
> Plasma Theme; however I'm not against adding some more hover feedback for
> launchers as well, it's something that could be discussed with the community.
>
> The other solution - making the icons bigger, similar to Latte Dock - is
> much more complex to implement, especially if we had to draw the icons
> outside of the panel area, as Latte does; I would prefer to keep that
> complexity in Latte, to maintain Plasma Panels as simple (and bug-free) as
> possible.
Amazing! Here's the instruction manual just there. :) Yes that MR will do (the
code change seemed pretty simple too!), blur and growing icons were examples to
better understand what I meant by "alternatives to the faint icon glow". I
customized my panel to leverage the icon backgrounds in various states so I
will want to keep consistency in my theme here as well. Having, maybe one day,
more hover feedbacks as you point out, would provide more alternatives to the
user, I personally like the idea.
I'll follow this closely, thank you!
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 462411] New: Feature request to decouple Plasma Panel from Application Windows in terms of theming or some particular effects.
https://bugs.kde.org/show_bug.cgi?id=462411 Bug ID: 462411 Summary: Feature request to decouple Plasma Panel from Application Windows in terms of theming or some particular effects. Classification: Plasma Product: plasmashell Version: 5.26.4 Platform: Archlinux OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: frankeba...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 SUMMARY Feature request to decouple Plasma Panel from Application Windows in terms of theming or some particular effects. See "Additional Information" below for more details. STEPS TO REPRODUCE 1. Make your Panel translucent using its integrated feature (EDIT MODE > Configure Panel > Opacity > Translucent) OR change opacity of panel-background.svg to 0 2. Apply System Settings > Workspace Behavior > Desktop Effect = Blur OBSERVED RESULT The Panel blurs just like all the other application Windows. EXPECTED RESULT The Panel should have the ability to remain fully translucent and therefore not being entangled to what is applied to the rest of the Plasma Desktop/Workspace. The Panel should have the ability to control its look (colors, effects, etc.) independently to the Desktop/Workspace/Application Windows. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.26.4 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100 Qt Version: 5.15.7 ADDITIONAL INFORMATION This feature request focuses on the user experience. Plasma is all about customization. As many believe, the Panel is not really considered like a Window from a user's perspective, it's a tool to manage applications, launchers, window menus, system trays, etc. Many users like to have a different look and feel for the Panel vs the rest of the windows, which is also why Plasma Panel alternatives are quite popular (but they are not native to Plasma). In fact it's already possible in certain scenarios to have the Plasma Panel change its color independently than the Plasma Windows. This should also apply to Desktop Effects, like Blur for instance. Currently, Blur acts as an opacity variable to the Panel. As seen, it's possible to change the opacity of the panel-background.svg to 0, but when applying Blur Effect, it blurs what should not exist (0 opacity means there shouldn't be anything there, otherwise if there is something, it defeats the purpose of using 0% opacity, from a user's point of view of course). :) Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462411] Don't apply blur to panel when it's marked as translucent
https://bugs.kde.org/show_bug.cgi?id=462411 --- Comment #3 from Frank --- (In reply to veggero from comment #2) > [BlurBehindEffect] > enabled=false OMG! It's working! No need for 3rd party widget altering the Panel which can break at anytime or stop being maintained. :D Thanks (yet again) Nicco! -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 341784] K3b Version 2.0.2
https://bugs.kde.org/show_bug.cgi?id=341784 Frank changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 400495] New: no timeline resize or get a white background
https://bugs.kde.org/show_bug.cgi?id=400495 Bug ID: 400495 Summary: no timeline resize or get a white background Product: kdenlive Version: 18.08.2 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: frk...@gmail.com Target Milestone: --- SUMMARY i cant believe you dont know about this, if so juat ignore. i downloaded kdenlive 18.08.2 appimage from your website. the first time i run kdenlive appimage it has a dark background and i cannot change the height of the timeline window, it just snaps back. if i exit and run it a second time, it comes up with a white background and i can resize the timeline height. if i remove the kdenlive-appimagerc file then when i run it, it gives me the dark background again but no timeline resize. i prefer the dark background with the ability to resize the timeline. i downloaded kdenlive 18.04.1 appimage and it does not have the timeline resize problem. however it changes to a white background on all runs after the first. STEPS TO REPRODUCE 1. download appimage, run, resize timeline, exit, run, resize timeline 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE VERSIONS i think all these versions are in the appimage (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION os is ubuntu 18.04.1 with the default gui. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408277] New: plasma5 volume applet (System panel) is not working correctly
https://bugs.kde.org/show_bug.cgi?id=408277 Bug ID: 408277 Summary: plasma5 volume applet (System panel) is not working correctly Product: frameworks-plasma Version: 5.58.0 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: libplasmaquick Assignee: notm...@gmail.com Reporter: sche...@opensourcemedia.de Target Milestone: --- Created attachment 120548 --> https://bugs.kde.org/attachment.cgi?id=120548&action=edit status of the applet after killall pulseaudio SUMMARY STEPS TO REPRODUCE 1. start Browser (Firefox) 2. start Kmail 3. start any internet video in firefox 4. the sound of the video is disturbed OBSERVED RESULT Before my last update i "solved" it in this way: 1. bash killall pulseaudio 2. the volume applet start again 3. It ran again, I got clear sound OBSERVED RESULT Since the last tumbleweed update a few days ago (Plasma 5.15.5) the bug still the same but now i can't solve it. I'm doing the same thing I did before. 1. bash killall pulseaudio 2. now the applet doesn't work anymore. The settings/connection of the applet is lost (I have added two screenshots) EXPECTED RESULT the plasma volume control should work System: openSUSE Tumbleweed 20190601 KDE-Plasma-Version: 5.15.5 KDE-Frameworks-Version: 5.58.0 Qt-Version: 5.12.3 Kernel-Version: 5.1.5-1-default Art des Betriebssystems: 64-bit Prozessoren: 16 × AMD Ryzen 7 2700 Eight-Core Processor RAM: 15,7 GiB Arbeitsspeicher openSUSE tumbleweed 20190601 ADDITIONAL INFORMATION I've had the bug since my first installation of tumbleweed in December 2018 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408277] plasma5 volume applet (System panel) is not working correctly
https://bugs.kde.org/show_bug.cgi?id=408277 --- Comment #1 from Frank --- Created attachment 120550 --> https://bugs.kde.org/attachment.cgi?id=120550&action=edit the empty settings view of the applet -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 408277] plasma5 volume applet (System panel) is not working correctly
https://bugs.kde.org/show_bug.cgi?id=408277 --- Comment #2 from Frank --- I must add the following STEPS TO REPRODUCE 1. start Browser (Firefox) 2. start Kontact/Kmail !! when I don't start Kontact and watch videos in the browser the sound remains clear!! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406430] New: korganizer chrashes
https://bugs.kde.org/show_bug.cgi?id=406430 Bug ID: 406430 Summary: korganizer chrashes Product: korganizer Version: 5.10.3 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sche...@opensourcemedia.de Target Milestone: --- SUMMARY OBSERVED RESULT Korganizer (Version 18.12.3-1.2) crashes from start SOFTWARE/OS VERSIONS Linux opensSUSE Tumbleweed 20190408 Linux/KDE Plasma: KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION korgac PID: 3092 Signal: Segmentation fault (11) Datum: 11.04.19 11:46:14 Application: KOrganizer-Erinnerungsmodul (korgac), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fa61a4d4940 (LWP 3092))] Thread 24 (Thread 0x7fa5c1ffb700 (LWP 4485)): #0 0x7fa61cd7f03c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa607975e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa607975b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa61cd78fab in start_thread () from /lib64/libpthread.so.0 #4 0x7fa61e2ff6af in clone () from /lib64/libc.so.6 Thread 23 (Thread 0x7fa5c27fc700 (LWP 4484)): #0 0x7fa61cd7f03c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa607975e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa607975b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa61cd78fab in start_thread () from /lib64/libpthread.so.0 #4 0x7fa61e2ff6af in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7fa5c2ffd700 (LWP 4483)): #0 0x7fa61cd7f03c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa607975e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa607975b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa61cd78fab in start_thread () from /lib64/libpthread.so.0 #4 0x7fa61e2ff6af in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7fa5c37fe700 (LWP 4482)): #0 0x7fa61cd7f03c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa607975e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa607975b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa61cd78fab in start_thread () from /lib64/libpthread.so.0 #4 0x7fa61e2ff6af in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7fa5c3fff700 (LWP 4481)): #0 0x7fa61cd7f03c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa607975e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa607975b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa61cd78fab in start_thread () from /lib64/libpthread.so.0 #4 0x7fa61e2ff6af in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7fa5e4ff9700 (LWP 4480)): #0 0x7fa61cd7f03c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa607975e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa607975b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa61cd78fab in start_thread () from /lib64/libpthread.so.0 #4 0x7fa61e2ff6af in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7fa5e57fa700 (LWP 4479)): #0 0x7fa61cd7f03c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa607975e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa607975b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa61cd78fab in start_thread () from /lib64/libpthread.so.0 #4 0x7fa61e2ff6af in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7fa5e5ffb700 (LWP 4478)): #0 0x7fa61cd7f03c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa607975e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa607975b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa61cd78fab in start_thread () from /lib64/libpthread.so.0 #4 0x7fa61e2ff6af in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7fa5e67fc700 (LWP 4477)): #0 0x7fa61cd7f03c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa607975e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa607975b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa61cd78fab in start_thread () from /lib64/libpthread.so.0 #4 0x7fa61e2ff6af in clone () from /lib64/libc.so.6 Thread 15 (Thread 0x7fa5e6ffd700 (LWP 4476)): #0 0x7fa61cd7f03c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7fa607975e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7fa607975b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7fa61cd78fab in start_thread () from /lib64/libpthread.so.0 #4 0x7fa61e2ff6af in clone () from /lib64/libc.so.6 Thread 14 (Thread 0x7fa5e77fe700 (LWP
[korganizer] [Bug 406430] korganizer chrashes
https://bugs.kde.org/show_bug.cgi?id=406430 --- Comment #2 from Frank --- (In reply to Wolfgang Bauer from comment #1) > Seems to be the same as bug#406411... Yes, looks like it. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 Frank changed: What|Removed |Added CC||sche...@opensourcemedia.de --- Comment #6 from Frank --- I just reportet a bug seems to be the same issue. Bug 406430 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 386674] kdeinit5 crash
https://bugs.kde.org/show_bug.cgi?id=386674 Frank changed: What|Removed |Added CC||sche...@opensourcemedia.de -- You are receiving this mail because: You are watching all bug changes.
[bugs.kde.org] [Bug 406463] New: kdeinit5 chrashes
https://bugs.kde.org/show_bug.cgi?id=406463 Bug ID: 406463 Summary: kdeinit5 chrashes Product: bugs.kde.org Version: unspecified Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: sysad...@kde.org Reporter: sche...@opensourcemedia.de CC: she...@kde.org Target Milestone: --- SUMMARY kdeinit5 PID: 16374 Signal: Floating point exception (8) Datum: 12.04.19 12:14:13 STEPS TO REPRODUCE dont't know. There is only Kmail, dolphin and Firefox open at that time it chrashes suddenly OBSERVED RESULT kdeinit5 chrashes EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/ OPensuse tumbleweed Kernel 5.06.-1 default KDE Plasma: (available in About System) KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.56.0 Qt Version: 5.12.2 ADDITIONAL INFORMATION Application: kdeinit5 (kdeinit5), signal: Floating point exception Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f21382d1900 (LWP 16374))] Thread 23 (Thread 0x7f20d77fe700 (LWP 16409)): #0 0x7f2139bd26c4 in read () from /lib64/libc.so.6 #1 0x7f21387d3880 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x7f213878c90f in g_main_context_check () from /usr/lib64/libglib-2.0.so.0 #3 0x7f213878cde0 in ?? () from /usr/lib64/libglib-2.0.so.0 #4 0x7f213878cf5c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #5 0x7f2139f79e7b in QEventDispatcherGlib::processEvents (this=0x7f20c4000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #6 0x7f2139f253cb in QEventLoop::exec (this=this@entry=0x7f20d77fdc70, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:140 #7 0x7f2139d70016 in QThread::exec (this=) at ../../include/QtCore/../../src/corelib/global/qflags.h:120 #8 0x7f213601d565 in ?? () from /usr/lib64/libQt5DBus.so.5 #9 0x7f2139d71362 in QThreadPrivate::start (arg=0x7f213609dd80) at thread/qthread_unix.cpp:361 #10 0x7f213920dfab in start_thread () from /lib64/libpthread.so.0 #11 0x7f2139be16af in clone () from /lib64/libc.so.6 Thread 22 (Thread 0x7f20d7fff700 (LWP 16408)): #0 0x7f213921403c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f212ee95e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f212ee95b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f213920dfab in start_thread () from /lib64/libpthread.so.0 #4 0x7f2139be16af in clone () from /lib64/libc.so.6 Thread 21 (Thread 0x7f20f4ff9700 (LWP 16407)): #0 0x7f213921403c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f212ee95e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f212ee95b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f213920dfab in start_thread () from /lib64/libpthread.so.0 #4 0x7f2139be16af in clone () from /lib64/libc.so.6 Thread 20 (Thread 0x7f20f57fa700 (LWP 16406)): #0 0x7f213921403c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f212ee95e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f212ee95b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f213920dfab in start_thread () from /lib64/libpthread.so.0 #4 0x7f2139be16af in clone () from /lib64/libc.so.6 Thread 19 (Thread 0x7f20f5ffb700 (LWP 16405)): #0 0x7f213921403c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f212ee95e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f212ee95b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f213920dfab in start_thread () from /lib64/libpthread.so.0 #4 0x7f2139be16af in clone () from /lib64/libc.so.6 Thread 18 (Thread 0x7f20f67fc700 (LWP 16404)): #0 0x7f213921403c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f212ee95e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f212ee95b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f213920dfab in start_thread () from /lib64/libpthread.so.0 #4 0x7f2139be16af in clone () from /lib64/libc.so.6 Thread 17 (Thread 0x7f20f6ffd700 (LWP 16403)): #0 0x7f213921403c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f212ee95e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f212ee95b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f213920dfab in start_thread () from /lib64/libpthread.so.0 #4 0x7f2139be16af in clone () from /lib64/libc.so.6 Thread 16 (Thread 0x7f20f77fe700 (LWP 16402)): #0 0x7f213921403c in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x7f212ee95e13 in ?? () from /usr/lib64/dri/radeonsi_dri.so #2 0x7f212ee95b67 in ?? () from /usr/lib64/dri/radeonsi_dri.so #3 0x7f213920dfab in start_thread () from /lib64/libpthread.so.0 #4 0x7f
[kio-extras] [Bug 406463] kdeinit5 chrashes
https://bugs.kde.org/show_bug.cgi?id=406463 --- Comment #2 from Frank --- (In reply to Christoph Feck from comment #1) > Could you find the Postscript or PDF file which causes GhostScript to crash? I'm not sure. I may have opened an e-mail attachment when it happened. i can't trace the trigger at the moment -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 406411] Korganizer daemon closes when plasma starts
https://bugs.kde.org/show_bug.cgi?id=406411 --- Comment #15 from Frank --- I can agree with the observation. The same applies to me. the bug seems to be fixed. Many thanks for your work!!! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 410254] Clipboard from platform to OS doesn't work 100% of the time
https://bugs.kde.org/show_bug.cgi?id=410254 Frank changed: What|Removed |Added CC||alteahandle-...@yahoo.ca Version|unspecified |1.3.2 --- Comment #5 from Frank --- Same here Pixel 2 after Android 10 Copy on KDE Neon desktop, phone receives and makes pastable. Copy on the phone and desktop receives nothing. Very frustrating when someone sends you a link. -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 388082] ktp-text-ui does not scroll automatically
https://bugs.kde.org/show_bug.cgi?id=388082 frank changed: What|Removed |Added CC|sk...@legalise.it | -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 387898] high cpu usage on QtWebEngineProcess when using akregator's internal browser
https://bugs.kde.org/show_bug.cgi?id=387898 frank changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from frank --- not true anymore with akregator 5.10.2 -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 202370] closing tab sets focus to search instead of content
https://bugs.kde.org/show_bug.cgi?id=202370 --- Comment #17 from frank --- seems fixed to me (v5.10.2) -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 360126] Account not selected when using "Previous Conversations"
https://bugs.kde.org/show_bug.cgi?id=360126 frank changed: What|Removed |Added CC||sk...@legalise.it -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 411609] New: I can receive email but cannot send it. Kontact mail reports an error when determining the D-Bus interface of mailfilteragent.
https://bugs.kde.org/show_bug.cgi?id=411609 Bug ID: 411609 Summary: I can receive email but cannot send it. Kontact mail reports an error when determining the D-Bus interface of mailfilteragent. Product: kontact Version: 5.12.0 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: sche...@opensourcemedia.de Target Milestone: --- SUMMARY I can receive email but cannot send it. This happens "Kontact mail reports an error when determining the D-Bus interface of mailfilteragent." This happened on 04.09.19. I installed a system update once on 04.09 and then again on 05.09.19 In both updates akonadi was also involved. Maybe this is the reason? STEPS TO REPRODUCE 0. The following message appears in the taskbar shortly after system startup, of course: "Kontact mail reports an error when determining the D-Bus interface of mailfilteragent." 1. start Kontact 2. click E-Mail OBSERVED RESULT E-mails are not sent EXPECTED RESULT E-mails should be sent SOFTWARE/OS VERSIONS OpenSuSe Tumbleweed Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.16.4 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.0 Kernel: 5.2.11-1 default -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 193673] article scrollbar should reset at feed-change
https://bugs.kde.org/show_bug.cgi?id=193673 frank changed: What|Removed |Added CC||sk...@legalise.it -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 341785] Application: K3b
https://bugs.kde.org/show_bug.cgi?id=341785 Frank changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #2 from Frank --- I can't tell you because I haven't been on Ubuntu for two years. I switched to Debian and the Synaptic version is 2.0.3. Right now I don't have any problems with that. But on the other hand there is also another one that makes that when you erase a DVD -RW in fast the disc stops during the operation or that after the operation K3B says that an error has occurred and consequently the disc becomes unusable. It's a problem I had with Ubuntu as well. So it's also an old problem to solve. But right now, I can't tell you if that's still the case, because I haven't tried it again for at least a year and a half, and it's mostly because I lost a lot of DVD-RWs by doing tests. So I've been using full formatting for over 2 years and I have no problems with it that way. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 400495] no timeline resize or get a white background
https://bugs.kde.org/show_bug.cgi?id=400495 --- Comment #1 from frank --- settings -> themes -> breeze-dark will fix the problems but i have to do it every time i run kdenlive, it does not remember. this should be changed to minor in importance. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421849] Unable to create proxy clips
https://bugs.kde.org/show_bug.cgi?id=421849 Frank changed: What|Removed |Added CC||frankrb...@gmail.com --- Comment #2 from Frank --- I have the exact same issue when trying to create proxy clips from .mov files in version 20.4.1 and above. My work around at the moment is opening the project in version 19.12.3, creating the required proxies, save the project and reopen in 20.04.1. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421849] Unable to create proxy clips
https://bugs.kde.org/show_bug.cgi?id=421849 --- Comment #9 from Frank --- (SOLVED) Mark solved? In the 'Proxy' tab from 'Project settings' I changed the 'Encoding profile' to x264. Now all clips are perfectly converted to proxy clips. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 417217] New: Umlauts are not displayed correctly
https://bugs.kde.org/show_bug.cgi?id=417217 Bug ID: 417217 Summary: Umlauts are not displayed correctly Product: kmail2 Version: 5.13.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: sche...@opensourcemedia.de Target Milestone: --- SUMMARY Hello since a system update about 3 weeks ago about 30% of my incoming mails with umlauts are not displayed correctly. If I use the webmail access of my hoster the mails are displayed correctly Nothing has been changed in the settings of Kontact/Kmail. The coding is set to "automatic". It has worked perfectly since the first system installation over a year ago STEPS TO REPRODUCE Requesting mails from the mail server OBSERVED RESULT umlauts are not displayed correctly EXPECTED RESULT The umlauts should be displayed correctly SOFTWARE/OS VERSIONS Betriebssystem: openSUSE Tumbleweed 20200201 KDE-Plasma-Version: 5.17.5 KDE-Frameworks-Version: 5.66.0 Qt-Version: 5.14.1 Kernel-Version: 5.4.14-2-default Art des Betriebssystems: 64-bit Prozessoren: 16 × AMD Ryzen 7 2700 Eight-Core Processor Speicher: 15,5 GiB Arbeitsspeicher -- You are receiving this mail because: You are watching all bug changes.
[telepathy] [Bug 388082] ktp-text-ui does not scroll automatically
https://bugs.kde.org/show_bug.cgi?id=388082 frank changed: What|Removed |Added CC||sk...@legalise.it -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 387897] New: akregator supressing power management on specific website
https://bugs.kde.org/show_bug.cgi?id=387897 Bug ID: 387897 Summary: akregator supressing power management on specific website Product: akregator Version: 5.6.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: sk...@legalise.it Target Milestone: --- Created attachment 109371 --> https://bugs.kde.org/attachment.cgi?id=109371&action=edit energy saving snapshot after opening http://punto-informatico.it/ with akregator, power management doesn't work anymore with the snapshotted message, while opening the same site with any other browser (tried qupzilla, firefox and chromium) doesn't lead to the same result... -- You are receiving this mail because: You are watching all bug changes.
[akregator] [Bug 387898] New: high cpu usage on QtWebEngineProcess when using akregator's internal browser
https://bugs.kde.org/show_bug.cgi?id=387898 Bug ID: 387898 Summary: high cpu usage on QtWebEngineProcess when using akregator's internal browser Product: akregator Version: 5.6.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: internal browser Assignee: kdepim-b...@kde.org Reporter: sk...@legalise.it Target Milestone: --- when opening any webpage (however the issue is more visible with heavy js pages) with akregator's internal browser the spawned QtWebEngineProcess is using a relative high cpu usage, while opening the same page with qupzilla the QtWebEngineProcess cpu usage if way lower: skunk@morpheus ~ $ ps -eo pcpu,pid,args --sort=-pcpu|grep "QtWebEngineProcess --type=renderer" 62.9 16923 /usr/lib64/qt5/libexec/QtWebEngineProcess --type=renderer --disable-accelerated-video-decode --disable-gpu-memory-buffer-video-fram 4.2 16961 /usr/lib64/qt5/libexec/QtWebEngineProcess --type=renderer --disable-accelerated-video-decode --disable-gpu-memory-buffer-video-frames --enable-threaded-compositing --use-gl=desktop --primordial-pipe-token=8F7668716F60475AFA8305A4CD049921 --lang=en-US --enable-pinch --num-raster-threads=2 --enable-main-frame-before-activation --content-image-texture-target=0,0,3553;0,1,3553;0,2,3553;0,3,3553;0,4,3553;0,5,3553;0,6,3553;0,7,3553;0,8,3553;0,9,3553;0,10,3553;0,11,3553;0,12,3553;0,13,3553;0,14,3553;0,15,3553;1,0,3553;1,1,3553;1,2,3553;1,3,3553;1,4,3553;1,5,3553;1,6,3553;1,7,3553;1,8,3553;1,9,3553;1,10,3553;1,11,3553;1,12,3553;1,13,3553;1,14,3553;1,15,3553;2,0,3553;2,1,3553;2,2,3553;2,3,3553;2,4,3553;2,5,3553;2,6,3553;2,7,3553;2,8,3553;2,9,3553;2,10,3553;2,11,3553;2,12,3553;2,13,3553;2,14,3553;2,15,3553;3,0,3553;3,1,3553;3,2,3553;3,3,3553;3,4,3553;3,5,3553;3,6,3553;3,7,3553;3,8,3553;3,9,3553;3,10,3553;3,11,3553;3,12,3553;3,13,3553;3,14,3553;3,15,3553 --service-request-channel-token=8F7668716F60475AFA8305A4CD049921 --renderer-client-id=5 0.2 16798 /usr/lib64/qt5/libexec/QtWebEngineProcess --type=renderer --disable-accelerated-video-decode --disable-gpu-memory-buffer-video-fram -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 388022] New: An error occurred: Kleopatra: Could not open file "E:\Buffalotech\ISO\electrum-3.0.3-portable.exe" for reading: Input/output error (218136625)
https://bugs.kde.org/show_bug.cgi?id=388022 Bug ID: 388022 Summary: An error occurred: Kleopatra: Could not open file "E:\Buffalotech\ISO\electrum-3.0.3-portable.exe" for reading: Input/output error (218136625) Product: kleopatra Version: 3.0.1 Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: critical Priority: NOR Component: general Assignee: aheine...@intevation.de Reporter: ffalcon...@gmail.com CC: kdepim-b...@kde.org, m...@kde.org Target Milestone: --- Created attachment 109444 --> https://bugs.kde.org/attachment.cgi?id=109444&action=edit Screen capture of error Error when trying to Decrypt / Verify the electrum-3.0.3-portable.exe.asc file -- You are receiving this mail because: You are watching all bug changes.
[ksmserver] [Bug 354097] Session management broken when using several virtual desktops
https://bugs.kde.org/show_bug.cgi?id=354097 Frank changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #10 from Frank --- Just to pick up on this after some time: After about 8 months I retried whether this problem has vanished in the meantime and indeed in version 5.37 all seems fixed. -- You are receiving this mail because: You are watching all bug changes.
[kleopatra] [Bug 354098] Does not ask for password and only works with empty password keys
https://bugs.kde.org/show_bug.cgi?id=354098 Frank changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #4 from Frank --- Also here, after retrying after 8 months the bug seems to be gone now. Must have been fixed together with other general bugfixes. -- You are receiving this mail because: You are watching all bug changes.
[libkface] [Bug 387077] New: libkface vs opencv incompatibility: compile error
https://bugs.kde.org/show_bug.cgi?id=387077
Bug ID: 387077
Summary: libkface vs opencv incompatibility: compile error
Product: libkface
Version: unspecified
Platform: Gentoo Packages
OS: Linux
Status: UNCONFIRMED
Severity: critical
Priority: NOR
Component: General
Assignee: imaging-bugs-n...@kde.org
Reporter: fhe...@inbox.lv
Target Milestone: ---
Relevant System: Gentoo, opencv-3.3.0-r4, libkface-17.08.3
The package fails to compile with the following error:
[ 54%] Building CXX object
src/CMakeFiles/KF5KFace.dir/database/core/databasecorebackend.cpp.o
cd /var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3_build/src
&& /usr/bin/x86_64-pc-linux-gnu-g++ -DKF5KFace_EXPORTS -DQT_CORE_LIB
-DQT_GUI_LIB -DQT_NO_CAST_FROM_ASCII -DQT_NO_CAST_FROM_BYTEARRAY
-DQT_NO_CAST_TO_ASCII -DQT_NO_DEBUG -DQT_NO_SIGNALS_SLOTS_KEYWORDS
-DQT_NO_URL_CAST_FROM_STRING -DQT_SQL_LIB -DQT_USE_FAST_OPERATOR_PLUS
-DQT_USE_QSTRINGBUILDER -DQT_WIDGETS_LIB -DQT_XML_LIB -D_GNU_SOURCE
-D_LARGEFILE64_SOURCE
-I/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3_build/src
-I/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src
-I/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3_build/src/KF5KFace_autogen/include
-I/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3_build/src/..
-I/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/database
-I/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/database/core
-I/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/detection
-I/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/recognition-opencv-lbph
-I/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/alignment-congealing
-isystem /usr/include/opencv -isystem /usr/include/qt5 -isystem
/usr/include/qt5/QtGui -isystem /usr/include/qt5/QtCore -isystem
/usr/lib64/qt5/mkspecs/linux-g++ -isystem /usr/include/qt5/QtXml -isystem
/usr/include/qt5/QtSql -isystem /usr/include/qt5/QtWidgets -DQT_NO_DEBUG
-DNDEBUG -O2 -march=native -fomit-frame-pointer -pipe -std=c++0x
-fno-operator-names -Wall -Wextra -Wcast-align -Wchar-subscripts
-Wformat-security -Wno-long-long -Wpointer-arith -Wundef -Wnon-virtual-dtor
-Woverloaded-virtual -Werror=return-type -Wvla -Wdate-time -pedantic
-Wsuggest-override -fexceptions -fPIC -fvisibility=hidden
-fvisibility-inlines-hidden -fPIC -std=gnu++11 -o
CMakeFiles/KF5KFace.dir/database/core/databasecorebackend.cpp.o -c
/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/database/core/databasecorebackend.cpp
In file included from
/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/recognition-opencv-lbph/facerec_borrowed.cpp:41:0:
/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/recognition-opencv-lbph/facerec_borrowed.h:120:10:
warning: ‘virtual void
KFaceIface::LBPHFaceRecognizer::train(cv::InputArrayOfArrays, cv::InputArray)’
can be marked override [-Wsuggest-override]
void train(cv::InputArrayOfArrays src, cv::InputArray labels);
^
/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/recognition-opencv-lbph/facerec_borrowed.h:126:10:
warning: ‘virtual void
KFaceIface::LBPHFaceRecognizer::update(cv::InputArrayOfArrays, cv::InputArray)’
can be marked override [-Wsuggest-override]
void update(cv::InputArrayOfArrays src, cv::InputArray labels);
^
/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/recognition-opencv-lbph/facerec_borrowed.h:184:12:
warning: ‘virtual double KFaceIface::LBPHFaceRecognizer::getThreshold() const’
can be marked override [-Wsuggest-override]
double getThreshold() const { return m_threshold;
}
^
/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/recognition-opencv-lbph/facerec_borrowed.h:185:10:
warning: ‘virtual void KFaceIface::LBPHFaceRecognizer::setThreshold(double)’
can be marked override [-Wsuggest-override]
void setThreshold(double _threshold) { m_threshold =
_threshold; }
^
/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/recognition-opencv-lbph/facerec_borrowed.cpp:
In static member function ‘static cv::Ptr
KFaceIface::LBPHFaceRecognizer::create(int, int, int, int, double,
KFaceIface::LBPHFaceRecognizer::PredictionStatistics)’:
/var/tmp/portage/kde-apps/libkface-17.08.3/work/libkface-17.08.3/src/recognition-opencv-lbph/facerec_borrowed.cpp:553:115:
error: invalid new-expression of abstract class type
‘KFaceIface::LBPHFaceRecognizer’
LBPHFaceRecognizer* const fr = new LBPHFaceRecognizer(radius, neighbors,
grid_x, grid_y, threshold, statistics);
-
Looks to me like it is related to an incompatibility with opencv.
--
You are receiving this mail because:
You are wa
[kontact] [Bug 374333] New: Kontact crashes on vcard import
https://bugs.kde.org/show_bug.cgi?id=374333 Bug ID: 374333 Summary: Kontact crashes on vcard import Product: kontact Version: 5.2.3 Platform: Mint (Ubuntu based) OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: fhe...@inbox.lv Target Milestone: --- Application: kontact (5.2.3) Qt Version: 5.6.1 Frameworks Version: 5.28.0 Operating System: Linux 4.8.0-30-generic i686 Distribution: Linux Mint 18 Sarah -- Information about the crash: Vcard import to addressbook. The same vcard works flawless (import/export) on a different 64bit gentoo-linux kde-plasma5 installation. A version or 32/64 bit incompatibility is suspected as the reason. Please debug and remove this serious bug. It keeps crashing kontact whenever the kaddressbook plugin is opened and required deletion of the whole akonadi databse to fix. The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0xadde7ac0 (LWP 4787))] Thread 25 (Thread 0x9862fb40 (LWP 4839)): #0 0xb770ece5 in __kernel_vsyscall () #1 0xb5efdd0f in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0xb24e1b10 in g_poll (__timeout=-1, __nfds=1, __fds=0xad088820) at /usr/include/i386-linux-gnu/bits/poll2.h:46 #3 0xb24e1b10 in g_poll (fds=0xad088820, nfds=1, timeout=-1) at /build/glib2.0-8EA4QF/glib2.0-2.48.1/./glib/gpoll.c:124 #4 0xb24d310c in g_main_context_iterate (priority=2147483647, n_fds=1, fds=0xad088820, timeout=, context=0x9d2897c0) at /build/glib2.0-8EA4QF/glib2.0-2.48.1/./glib/gmain.c:4135 #5 0xb24d310c in g_main_context_iterate (context=context@entry=0x9d2897c0, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-8EA4QF/glib2.0-2.48.1/./glib/gmain.c:3835 #6 0xb24d3244 in g_main_context_iteration (context=0x9d2897c0, may_block=1) at /build/glib2.0-8EA4QF/glib2.0-2.48.1/./glib/gmain.c:3901 #7 0xb644 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #8 0xb63c82a6 in QEventLoop::processEvents(QFlags) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #9 0xb63c86da in QEventLoop::exec(QFlags) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #10 0xb61f982d in QThread::exec() () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb61f9908 in QThread::run() () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #12 0xb61fead2 in () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #13 0xb266f295 in start_thread (arg=0x9862fb40) at pthread_create.c:333 #14 0xb5f07eee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 24 (Thread 0x98e30b40 (LWP 4837)): #0 0xb770ece5 in __kernel_vsyscall () #1 0xb770e979 in __vdso_clock_gettime () #2 0xb5f15142 in __GI___clock_gettime (clock_id=1, tp=0x98e2fee4) at ../sysdeps/unix/clock_gettime.c:115 #3 0xb6297b48 in () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #4 0xb641fcc2 in QTimerInfoList::updateCurrentTime() () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #5 0xb64201e4 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #6 0xb6421739 in () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #7 0xb24d25cb in g_main_context_prepare (context=0xabf17cd8, priority=0x98e30054) at /build/glib2.0-8EA4QF/glib2.0-2.48.1/./glib/gmain.c:3442 #8 0xb24d3014 in g_main_context_iterate (context=context@entry=0xabf17cd8, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /build/glib2.0-8EA4QF/glib2.0-2.48.1/./glib/gmain.c:3820 #9 0xb24d3244 in g_main_context_iteration (context=0xabf17cd8, may_block=1) at /build/glib2.0-8EA4QF/glib2.0-2.48.1/./glib/gmain.c:3901 #10 0xb644 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #11 0xb63c82a6 in QEventLoop::processEvents(QFlags) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #12 0xb63c86da in QEventLoop::exec(QFlags) () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #13 0xb61f982d in QThread::exec() () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #14 0xb61f9908 in QThread::run() () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #15 0xb61fead2 in () at /usr/lib/i386-linux-gnu/sse2/libQt5Core.so.5 #16 0xb266f295 in start_thread (arg=0x98e30b40) at pthread_create.c:333 #17 0xb5f07eee in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:114 Thread 23 (Thread 0x99631b40 (LWP 4835)): #0 0xb770ece5 in __kernel_vsyscall () #1 0xb5efdd0f in poll () at ../sysdeps/unix/syscall-template.S:84 #2 0xb24e1b10 in g_poll (__timeout=-1, __nfds=1, __fds=0xa9b34878) at /usr/include/i386-linux-gnu/bits/poll2.h:46 #3 0xb24e1b10 in g_poll (fds=0xa9b34878, nfds=1, timeout=-1) at /build/glib2.0-8EA4QF/glib2.0-2.48.1/./glib/gpoll.c:
[kmymoney4] [Bug 379355] New: Reports do not print in colour.
https://bugs.kde.org/show_bug.cgi?id=379355 Bug ID: 379355 Summary: Reports do not print in colour. Product: kmymoney4 Version: 4.8.0 Platform: Ubuntu Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: kmymoney-de...@kde.org Reporter: morris.fran...@gmail.com Target Milestone: --- Reports displayed on the screen are in colour. When they are printed though, they are only printed in greyscale. I have tried with the system printer (Brother MFC-J615W) as well as printing to a PDF. The system defaults for the printer is full colour and, the printer dialogue in KMyMoney is also set to full colour. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 379377] New: KDE Desktop crash - no reason
https://bugs.kde.org/show_bug.cgi?id=379377 Bug ID: 379377 Summary: KDE Desktop crash - no reason Product: plasmashell Version: 5.9.4 Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: fr...@werkstatt.ovh CC: bhus...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.9.4) Qt Version: 5.8.0 Frameworks Version: 5.33.0 Operating System: Linux 4.10.9-1 x86_64 Distribution: "KaOS" -- Information about the crash: - What I was doing when the application crashed: I just started the, after login and changing the position of the panel, the wallpaper disapeared and the panel crashed and restarted. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7fe020b49cc0 (LWP 444))] Thread 8 (Thread 0x7fdf58ca1700 (LWP 550)): #0 0x7fe014da75c6 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #1 0x7fe014da7a68 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fe014da7b0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #3 0x7fe01bd32ebb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #4 0x7fe01bce0bba in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #5 0x7fe01bb15d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5 #6 0x7fdf5b86d347 in KCupsConnection::run() () at /usr/lib/libkcupslib.so #7 0x7fe01bb1a6e9 in () at /usr/lib/libQt5Core.so.5 #8 0x7fe01a9e1494 in start_thread () at /lib/libpthread.so.0 #9 0x7fe01b4386ff in clone () at /lib/libc.so.6 Thread 7 (Thread 0x7fdf6bd7c700 (LWP 545)): #0 0x7fe01b42af7d in read () at /lib/libc.so.6 #1 0x7fe014deb1c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fe014da750e in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fe014da79a8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fe014da7b0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fe01bd32ebb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fe01bce0bba in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fe01bb15d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fe01eaf21b2 in () at /usr/lib/libQt5Quick.so.5 #9 0x7fe01bb1a6e9 in () at /usr/lib/libQt5Core.so.5 #10 0x7fe01a9e1494 in start_thread () at /lib/libpthread.so.0 #11 0x7fe01b4386ff in clone () at /lib/libc.so.6 Thread 6 (Thread 0x7fdff95d9700 (LWP 539)): #0 0x7fe01a9e75cf in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/libpthread.so.0 #1 0x7fe0205ac934 in () at /usr/lib/libQt5Script.so.5 #2 0x7fe0205ac979 in () at /usr/lib/libQt5Script.so.5 #3 0x7fe01a9e1494 in start_thread () at /lib/libpthread.so.0 #4 0x7fe01b4386ff in clone () at /lib/libc.so.6 Thread 5 (Thread 0x7fdffb17a700 (LWP 536)): #0 0x7ffc9761eafb in clock_gettime () #1 0x7fe01b445696 in clock_gettime () at /lib/libc.so.6 #2 0x7fe01bd32151 in () at /usr/lib/libQt5Core.so.5 #3 0x7fe01bd309d9 in QTimerInfoList::updateCurrentTime() () at /usr/lib/libQt5Core.so.5 #4 0x7fe01bd30f05 in QTimerInfoList::timerWait(timespec&) () at /usr/lib/libQt5Core.so.5 #5 0x7fe01bd324ee in () at /usr/lib/libQt5Core.so.5 #6 0x7fe014da6fbd in g_main_context_prepare () at /usr/lib/libglib-2.0.so.0 #7 0x7fe014da7933 in () at /usr/lib/libglib-2.0.so.0 #8 0x7fe014da7b0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #9 0x7fe01bd32ebb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #10 0x7fe01bce0bba in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #11 0x7fe01bb15d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5 #12 0x7fe01e1483a5 in () at /usr/lib/libQt5Qml.so.5 #13 0x7fe01bb1a6e9 in () at /usr/lib/libQt5Core.so.5 #14 0x7fe01a9e1494 in start_thread () at /lib/libpthread.so.0 #15 0x7fe01b4386ff in clone () at /lib/libc.so.6 Thread 4 (Thread 0x7fe00116d700 (LWP 533)): #0 0x7fe01b42af7d in read () at /lib/libc.so.6 #1 0x7fe014deb1c0 in () at /usr/lib/libglib-2.0.so.0 #2 0x7fe014da750e in g_main_context_check () at /usr/lib/libglib-2.0.so.0 #3 0x7fe014da79a8 in () at /usr/lib/libglib-2.0.so.0 #4 0x7fe014da7b0c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #5 0x7fe01bd32ebb in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #6 0x7fe01bce0bba in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #7 0x7fe01bb15d7c in QThread::exec() () at /usr/lib/libQt5Core.so.5 #8 0x7fe01e1483a5 in () at /usr/lib/libQt5Qml.so.5 #9 0x7fe01bb1a6e9 in () at
[plasmashell] [Bug 475864] Error on switch from yandex browser to desktop
https://bugs.kde.org/show_bug.cgi?id=475864 --- Comment #22 from Frank --- Created attachment 175096 --> https://bugs.kde.org/attachment.cgi?id=175096&action=edit New crash information added by DrKonqi plasmashell (5.27.5) using Qt 5.15.8 Crash happens when resuming from sleep with Firefox running and sometimes other windows (email, file browser etc). Firefox is from Mozilla DEB repositories, not official Debian. -- Backtrace (Reduced): #4 0x7f96d7fbe3d0 in QSGAreaAllocator::deallocateInNode(QPoint const&, QSGAreaAllocatorNode*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7f96d7fbe446 in QSGAreaAllocator::deallocate(QRect const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #10 0x7f96d8067c09 in QQuickWindowPrivate::runAndClearJobs(QList*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 [...] #9 0x7f96d60d1a6b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 [...] #11 0x7f96d8076e20 in QQuickWindow::event(QEvent*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 475864] Error on switch from yandex browser to desktop
https://bugs.kde.org/show_bug.cgi?id=475864 Frank changed: What|Removed |Added CC||cont...@qza.io -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 498175] Desktop goes black and panels disappear when changing the global theme with "Desktop and window layout selected", until plasmashell is restarted
https://bugs.kde.org/show_bug.cgi?id=498175 Frank changed: What|Removed |Added CC||frankeba...@gmail.com --- Comment #13 from Frank --- Hello, I also experience this issue on all my machines (metals+VMs) every time I apply a Global Theme. Using Garuda Linux on Arch Wayland Plasma 6.2.5 QT 6.8.2-2 Frameworks 6.10.0-1 Kernel 6.13.2 Many of our users also report that same issue. So far the workaround was CTRL-ALT-DEL followed by either LOGOUT or REBOOT and wait a while for Plasma to execute the task, but I appreciate the systemctl command as another workaround. Thank you -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 486871] Can't fetch caldav or carddav from Nextcloud in Fedora 40, driver error
https://bugs.kde.org/show_bug.cgi?id=486871 Frank changed: What|Removed |Added CC||fhe...@inbox.lv --- Comment #7 from Frank --- Exactly the same problem on Nextcloud 30.0.6.2 Operating System: Manjaro Linux KDE Plasma Version: 6.3.2 KDE Frameworks Version: 6.11.0 Qt Version: 6.8.2 Kernel Version: 6.13.0-3-rt5-MANJARO (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7Y54 CPU @ 1.20GHz Memory: 15.5 GiB of RAM Graphics Processor: Intel® HD Graphics 615 Manufacturer: TUXEDO Computers Product Name: TUXEDO InfinityBook 14v1 Synopsis: DavX on Android works. On this box it does not matter how I try to add the dav resource, via kontacts, via akonadiconsole, as manual dav resource, merkuro, all same errors as described in this bugreport. It was working before I tried to reinstall the calendar, so the incompatibility is in the detection likely and it seems an akonadi incompatibility. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372047] New: Migration fails: collection path contains %2F instead of /
https://bugs.kde.org/show_bug.cgi?id=372047 Bug ID: 372047 Summary: Migration fails: collection path contains %2F instead of / Product: digikam Version: 5.2.0 Platform: Gentoo Packages OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Database-Migration Assignee: digikam-de...@kde.org Reporter: war...@gmx.de Target Milestone: --- I’m a user of Digikam 4.14 and trying out a freshly built 5.2.0 on my Gentoo system with Plasma 5.8.3, frameworks 5.26.0. After going through the conversion wizard, I see the root entry of the collection I am trying to migrate in the album tree, but after a short moment it vanishes and I see a progress popup at 100 %. The tag tree is still there. The timeline also shows how many images I have for a given month. But this one is cleared once I closed and reopened Digikam. I found out that in Digikam’s Settings→Collections I see the collection that I tried to migrate, but its path is written as "%2Fhome%2Ffrank%2Fbilder". So I delete that, add a new collection with the proper path, click OK and then the collection is correctly imported. Quickly glancing over it, all tags and so on seem to be there. After a while of processing, the timeline is also populated again. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 369051] Too low similarity threshold in fuzzy/duplicate search bloats the results with potentially unwished high-similarity results [patch]
https://bugs.kde.org/show_bug.cgi?id=369051 --- Comment #3 from Mario Frank --- Hey Gilles, those are good news. I agree with you concerning the improved usability by ordering the, as I understand, list of results in the left pane where the reference image and count of similar images is shown. But introducing an order here means changing the signature of the functions in haariface. Since QMap automatically has a sorting on the keys, we could use this to introduce an order to the result set. One quite easy way would be to wrap the QMap> as value of a avg-similarity-map. This would surely increase the memory consumption during search. But the automatic ordering by the similarity would circumvent a signifficant increase of runtime. After a small glimpse at the source code with grep, I found no possible conflicts with other files concerning the definition of the result set. Changing the return value types in haariface should be most likely safe. Should I propose another patch for this issue? -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372217] New: The results of the Duplicates are currently sorted by the image id and sortable by name and count if similars. But it should be sortable by the similarity of the duplicates
https://bugs.kde.org/show_bug.cgi?id=372217 Bug ID: 372217 Summary: The results of the Duplicates are currently sorted by the image id and sortable by name and count if similars. But it should be sortable by the similarity of the duplicates, too. [patch] Product: digikam Version: 5.3.0 Platform: Compiled Sources OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: Searches-Fuzzy Assignee: digikam-de...@kde.org Reporter: mario.fr...@uni-potsdam.de Target Milestone: --- Created attachment 102120 --> https://bugs.kde.org/attachment.cgi?id=102120&action=edit The first patch. When searching for duplicates, the result set is a table with the thumbnail and the count of similar pictures (including the original one). It is possible to sort the rows by either the reference picture (either name or id, I'm not sure here) or the count of entries in this virtual album. Sadly, it is not possible to sort the result by similarity. This patch introduces this functionality. For each reference image, the average similarity (in percent) is calculated for the potential duplicates, excluding the reference image. This way, it is possible to sort the virtual albums by the average similarities of the duplicates in both ascending and descending order. There is still one glitch in the sorting. Since the sorting of the items is done by lexicographic order, the ordering of was not correct if the length of the average similarity string differs. This problem was fixed with another patch that introduces arithmetic ordering for this column explicitly. The second patch will be submitted as comment. The complete commit messages: " [PATCH] Extended the duplicates search list view. Now, the average similarity of the found duplicates (excluding the original image) is shown as table column. Sorting the result set by the average similarity is thus possible. To implement this feature, the haariface had to be modified. It returns a map of average similarities to a map of image ids to the set of similar images instead of the map of image ids to the set of similar images. Communicating the average similarity to the search list view was not possible via slots and signals and this would have lead to sending a map of image ids to average similarities and then distributing the appropriate average similarity to the correct FindDuplicateAlbumItem. Instead, the average similarity is communicated via the SearchXml-query as a field of the group. This way, the correct item gets the correct similarity automatically. The evaluation of the new field by an SQL query is surpressed by the introduction of noEffect fields which need to have a prefix "noeffect_". So, the log is not polluted by unnecessary debug information. " and " [PATCH] The items in the FindDuplicatesAlbum were sorted by lexicographic order which does not make sense for the average similarity column (e.g. 100.00 is not correctly sorted). Thus, the less than operator was adopted such that for the average similarity column, arithmetic order is used. To make the code more stable against regressions due to reordering the columns, an enum was introduced. " -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 372217] The results of the Duplicates are currently sorted by the image id and sortable by name and count if similars. But it should be sortable by the similarity of the duplicates, too
https://bugs.kde.org/show_bug.cgi?id=372217 Mario Frank changed: What|Removed |Added CC||mario.fr...@uni-potsdam.de -- You are receiving this mail because: You are watching all bug changes.
