[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU

2023-04-18 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=468635 --- Comment #7 from HD Scania --- Created attachment 158203 --> https://bugs.kde.org/attachment.cgi?id=158203=edit My SDDM logs up to 18 April simplified with only Wayland related, warnings, and errors -- You are receiving this mail because:

[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU

2023-04-18 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=468635 HD Scania changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |hd-sca...@users.sf.net --- Comment #6 from HD

[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU

2023-04-18 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=468635 HD Scania changed: What|Removed |Added Assignee|hd-sca...@users.sf.net |kwin-bugs-n...@kde.org --- Comment #5 from HD

[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU

2023-04-18 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=468635 HD Scania changed: What|Removed |Added Assignee|kwin-bugs-n...@kde.org |hd-sca...@users.sf.net CC

[kwin] [Bug 468635] Plasma/Wayland always goes frozen on an AMD APU

2023-04-17 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=468635 --- Comment #2 from HD Scania --- Where to get logs for Wayland-related issues? And will going frozen then having to reboot even be loggable? I'm quite unsure -- You are receiving this mail because: You are watching all bug changes.

[plasma-wayland-protocols] [Bug 468635] New: Plasma/Wayland always goes frozen on an AMD APU

2023-04-17 Thread HD Scania
Status: REPORTED Severity: major Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hd-sca...@users.sf.net CC: aleix...@kde.org Target Milestone: --- SUMMARY *** AMD APU Zen2 Lucienne-G R4750G

[digikam] [Bug 467505] When launching the latest version of digiKam, the old internal MySql database cannot be started.

2023-03-17 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=467505 --- Comment #4 from Hackintosh HD --- Sorry for my screenshot and comment after Gilles explanation of the problem - as you may notice from our comments' timestamps, we commented pretty much simultaneously, so I didn't have any knowledge about

[digikam] [Bug 467505] When launching the latest version of digiKam, the old internal MySql database cannot be started.

2023-03-17 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=467505 --- Comment #3 from Hackintosh HD --- Same here on a MacBook Pro mid-2012 (MacBookPro9,1) with Ventura 13.2.1 after an upgrade of digikam 7.9/internal mysql to digikam 7.10, cf. attached screenshot. -- You are receiving this mail because: You

[digikam] [Bug 467505] When launching the latest version of digiKam, the old internal MySql database cannot be started.

2023-03-17 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=467505 Hackintosh HD changed: What|Removed |Added CC||hackintos...@posteo.eu --- Comment #2 from

[kup] [Bug 453919] Buckups won't run, no errors given.

2022-10-29 Thread HD
https://bugs.kde.org/show_bug.cgi?id=453919 HD changed: What|Removed |Added CC||hdomingu...@gmail.com --- Comment #6 from HD --- I had

[Powerdevil] [Bug 442954] Laptop going to sleep even when external monitor is plugged-in (Wayland only)

2021-09-26 Thread Adarsha HD
https://bugs.kde.org/show_bug.cgi?id=442954 Adarsha HD changed: What|Removed |Added CC||m...@adarshahd.com -- You are receiving

[digikam] [Bug 434714] digiKam-7.2.0-20210320T221224 breaks digiKam launch on macOS 10.14.6 Mojave

2021-03-21 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=434714 --- Comment #3 from Hackintosh HD --- That's really good news, thank you very much. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 434714] New: digiKam-7.2.0-20210320T221224 breaks digiKam launch on macOS 10.14.6 Mojave

2021-03-21 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=434714 Bug ID: 434714 Summary: digiKam-7.2.0-20210320T221224 breaks digiKam launch on macOS 10.14.6 Mojave Product: digikam Version: 7.2.0 Platform: macOS (DMG) OS:

[digikam] [Bug 432650] macOS: digikam Finder menu not localizable

2021-02-09 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=432650 --- Comment #18 from Hackintosh HD --- (In reply to Hackintosh HD from comment #17) … and a Qt-based application with at least a _partly_ localized macOS Finder menu item: MuseScore, https://musescore.org/. Source available from https://github.com

[digikam] [Bug 432650] macOS: digikam Finder menu not localizable

2021-02-09 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=432650 --- Comment #17 from Hackintosh HD --- I've just gone through https://en.wikipedia.org/wiki/Category:Software_that_uses_Qt and have now found an application that, at the same time, … 1. … is built on Qt, 2. … is free open source software, 3. … has

[digikam] [Bug 432650] macOS: digikam Finder menu not localizable

2021-02-09 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=432650 --- Comment #16 from Hackintosh HD --- (In reply to caulier.gilles from comment #12) > Clementine Audio player has also a macOS version. It fully based on Qt. Thank you, Gilles! - Clementine 1.3.1 is unfortunately suffering from a startup cr

[digikam] [Bug 432650] macOS: digikam Finder menu not localizable

2021-02-09 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=432650 --- Comment #11 from Hackintosh HD --- I've also opened a bug report for Krita, as it is showing the same problem: https://bugs.kde.org/show_bug.cgi?id=432685. -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 432685] New: macOS: Krita Finder menu item not localized/localizable despite non-English system locale

2021-02-09 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=432685 Bug ID: 432685 Summary: macOS: Krita Finder menu item not localized/localizable despite non-English system locale Product: krita Version: 4.4.2 Platform:

[digikam] [Bug 432650] macOS: digikam Finder menu not localizable

2021-02-09 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=432650 --- Comment #10 from Hackintosh HD --- If there are other QT-based, localized applications with a macOS build that I could test, feel free to let me know, -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 432650] macOS: digikam Finder menu not localizable

2021-02-09 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=432650 --- Comment #9 from Hackintosh HD --- (In reply to caulier.gilles from comment #8) > To HickitoshHD : Can you try to see if Kate or Krita installed on your Mac > has also the same i18n menu problem ? > > GilleS Caulier No problem, in

[digikam] [Bug 432650] macOS: digikam Finder menu not localizable

2021-02-08 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=432650 --- Comment #5 from Hackintosh HD --- (In reply to caulier.gilles from comment #3) My system locale however is AFAIK set to German: ~ $ locale LANG="de_DE.UTF-8" LC_COLLATE="de_DE.UTF-8" LC_CTYPE="de_DE.UTF-8" LC_MESS

[digikam] [Bug 432650] macOS: digikam Finder menu not localizable

2021-02-08 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=432650 --- Comment #1 from Hackintosh HD --- ... in case somebody would like to add the strings if that becomes possible: About digikam - Über digikam Preferences… - Einstellungen … (with a space) Services - Dienste Hide digikam - digikam ausblenden Hide

[digikam] [Bug 432650] New: macOS: digikam Finder menu not localizable

2021-02-08 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=432650 Bug ID: 432650 Summary: macOS: digikam Finder menu not localizable Product: digikam Version: 7.2.0 Platform: Other OS: macOS Status: REPORTED Severity: minor

[kwin] [Bug 420160] Session crashes when monitor goes into standby

2021-01-11 Thread Adarsha HD
https://bugs.kde.org/show_bug.cgi?id=420160 Adarsha HD changed: What|Removed |Added CC||m...@adarshahd.com -- You are receiving

[digikam] [Bug 426997] Automatic upgrading

2021-01-06 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=426997 --- Comment #11 from Hackintosh HD --- (In reply to caulier.gilles from comment #3) Just as a question, doesn't Clementine use the Sparkle Framework on macOS, https://sparkle-project.org/ ? To me, from a user's perspective, the Sparkle Framwork

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-06 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #36 from Hackintosh HD --- That sounds promising, I really like your approach of "polishing" the macOS release continuously bit by bit! :) An auto-update option is definitely something I would have proposed myself as a feature, s

[digikam] [Bug 426997] Automatic upgrading

2021-01-06 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=426997 Hackintosh HD changed: What|Removed |Added CC||hackintos...@posteo.eu -- You are receiving

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-06 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #34 from Hackintosh HD --- Great! I can confirm today's macOS build https://files.kde.org/digikam/digiKam-7.2.0-rc-20210106T133431-MacOS-x86-64.pkg fixes the problem, the hi-res icons from the .icns resources are now permanently used

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-05 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #28 from Hackintosh HD --- Created attachment 134563 --> https://bugs.kde.org/attachment.cgi?id=134563=edit 20200105_digiKam_macOS_dock_icon_after_launch_with_artefacts_in_top_left_corner.

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-05 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #27 from Hackintosh HD --- I've just tested https://files.kde.org/digikam/digiKam-7.2.0-rc-20210105T085952-MacOS-x86-64.pkg. Unfortunately, there's no improvement for digiKam's macOS dock icon, it's still heavily pixelated after changing

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-04 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #25 from Hackintosh HD --- I've tested https://files.kde.org/digikam/digiKam-7.2.0-rc-20210104T180304-MacOS-x86-64.pkg and unfortunately there's no change at all in the app icons' dock appearance, i.e. the final icons are still heavily

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-04 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #22 from Hackintosh HD --- (In reply to caulier.gilles from comment #20) Salut Gilles, voilà un archive ZIP avec au moins deux versions en 1024 px et en 512 px pour chaque application crées dans Inkscape. -- You are receiving this mail

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-04 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #21 from Hackintosh HD --- Created attachment 134533 --> https://bugs.kde.org/attachment.cgi?id=134533=edit archive with resized SVG app icons digikam-showfoto-svgs.zip containing: - digikam_1024_x_1024_px.svg (digiKam app i

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-04 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #19 from Hackintosh HD --- (In reply to caulier.gilles from comment #18) Hi Gilles, I chose 1024 x 1024 px after checking https://developer.apple.com/design/human-interface-guidelines/macos/icons-and-images/app-icon, which states

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-03 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #17 from Hackintosh HD --- Created attachment 134523 --> https://bugs.kde.org/attachment.cgi?id=134523=edit digikam.svg Test with document properties = 1024 x 1024 px -- You are receiving this mail because: You are watching all

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-03 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #16 from Hackintosh HD --- (In reply to caulier.gilles from comment #15) Thank you for the explanations, Gilles, I'm not sure if I understand the mechanism how both the digiKam and showfoto SVG resources for the applications' icons

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2021-01-03 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #51 from Hackintosh HD --- (In reply to caulier.gilles from comment #49) > Please confirm if bug #431003 is fixed or not. For me yes it is... Sorry, I'm a bit confused which bug is meant - this one here (#430949) or indeed the

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2021-01-03 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #50 from Hackintosh HD --- I just wondered if that GUI dialog was intentional as my digiKam instance already was under the /Applications/digiKam.org/digikam.app… -structure before executing the PKG installer. But if it is intented

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-03 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #11 from Hackintosh HD --- Just FYI, because attachment handling doesn't seem to work with the two screenshots (at least not in my browser): They are PNG files. -- You are receiving this mail because: You are watching all bug changes.

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-03 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #10 from Hackintosh HD --- Created attachment 134501 --> https://bugs.kde.org/attachment.cgi?id=134501=edit digiKam 7.2.0-todays-build launched in macOS dock Screenshot: digiKam 7.2.0-todays-build launched in macOS dock --

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-03 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #9 from Hackintosh HD --- Created attachment 134500 --> https://bugs.kde.org/attachment.cgi?id=134500=edit digiKam 7.2.0-todays-build in macOS dock, not launched Screenshot: digiKam 7.2.0-todays-build in macOS dock, not launched --

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-03 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 --- Comment #8 from Hackintosh HD --- Tested this morning's macOS build https://files.kde.org/digikam/digiKam-7.2.0-rc-20210103T072125-MacOS-x86-64.pkg with the following result: 1. digiKam now launches as one icon instance, there are in other words

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2021-01-03 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #48 from Hackintosh HD --- Addendum: After confirming the location of the MariaDB binaries, however, everything seems to be okay (digiKam launches, database is populated with expected RAW images). -- You are receiving this mail because

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2021-01-03 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 Hackintosh HD changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED

[digikam] [Bug 431003] Running status of digikam not reflected in MacOS task bar

2021-01-02 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=431003 Hackintosh HD changed: What|Removed |Added CC||hackintos...@posteo.eu -- You are receiving

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2021-01-02 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #44 from Hackintosh HD --- (In reply to Hackintosh HD from comment #43) > Confirmation: digiKam-7.2.0-rc-20210101T154336-MacOS-x86-64.pkg with Maik's > patch from comment #41 now also fixes MonitorProfileFile[$e] and > WorkProfi

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2021-01-02 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #43 from Hackintosh HD --- (In reply to caulier.gilles from comment #42) Confirmation: digiKam-7.2.0-rc-20210101T154336-MacOS-x86-64.pkg with Maik's patch from comment #41 now also fixes MonitorProfileFile[$e] and WorkProfileFile[$e] of my

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2021-01-01 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #37 from Hackintosh HD --- Confirmation: https://files.kde.org/digikam/digiKam-7.2.0-rc-20210101T154336-MacOS-x86-64.pkg indeed fixes the problem. REMAINING PROBLEM The PKG installer still did *not* update MonitorProfileFile[$e

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2021-01-01 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #36 from Hackintosh HD --- (In reply to caulier.gilles from comment #35) Oops, you're right, sorry. I did not consider that I was going through a PKG installer and not just dragging the two app bundles from a DMG to my /Application folder

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2021-01-01 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #34 from Hackintosh HD --- Another scenario that would break the app is an installation to /Users/$USERNAME/Applications, which according to Apple's guidelines is an entirely valid install location for macOS applications. Wouldn't

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2021-01-01 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #33 from Hackintosh HD --- Encore une fois merci, Gilles. Si la solution est si simple, tant mieux! :) (In reply to caulier.gilles from comment #31) > Here, we need to pass -b > /Applications/digiKam.org/digikam.app/Conten

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2020-12-31 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #30 from Hackintosh HD --- (In reply to Hackintosh HD from comment #29) Problem partly solved by a workaround: I did a ~ $ sudo mkdir -p /opt/digikam.org/share/mariadb/ && sudo cp -p /Applications/digiKam.org/digikam.app/Cont

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2020-12-31 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #29 from Hackintosh HD --- (In reply to caulier.gilles from comment #28) Merci beaucoup, Gilles, I've downloaded and installed digiKam-7.2.0-rc-20201231T170945-MacOS-x86-64.pkg now. Unfortunately, the error dialog still appears

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2020-12-31 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #27 from Hackintosh HD --- (In reply to Maik Qualmann from comment #20) Thank you, Maik, I'll try to collect relevant MariaDB debug info then. I'm afraid I also should check how the integrated MariaDB binaries of digiKam 7.2.0-beta2 were

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2020-12-31 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #16 from Hackintosh HD --- (In reply to Maik Qualmann from comment #15) > I think the cause is the wrong directory too > > /Users/$MYUSERNAME/Library/Application Support/digikam/digikam/mysql.conf > > The double digika

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2020-12-31 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #12 from Hackintosh HD --- ADDITIONAL COMMENTS Please feel free to let me know if I can provide further logging / debugging info. And just an idea, but if possible, wouldn't it be helpful to reference the MariaDB binaries

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2020-12-31 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #11 from Hackintosh HD --- Tested this morning's https://files.kde.org/digikam/digiKam-7.2.0-rc-20201231T095642-MacOS-x86-64.pkg: OBSERVATIONS 1. As expected, digiKam displays a dialog after launch that the MySQL binaries were not found

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2020-12-30 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #8 from Hackintosh HD --- (In reply to caulier.gilles from comment #3) > Hi, > > Yes, the new relocatable PKG for MAcOS remove older place to install digiKam > : /opt/digikam. No need to use 800Mb for nothing. > > Now b

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2020-12-29 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 --- Comment #2 from Hackintosh HD --- To elaborate this further: As far as I can see, versions of digiKam prior to 7.2.0-beta2 have installed MySQL / MariaDB binaries to /opt/digikam/lib/mariadb and have referenced the corresponding paths at least

[digikam] [Bug 430949] digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2020-12-29 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 Hackintosh HD changed: What|Removed |Added Component|Setup-Misc |Database-Mysql --- Comment #1 from Hackintosh

[digikam] [Bug 430949] New: digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade

2020-12-29 Thread Hackintosh HD
https://bugs.kde.org/show_bug.cgi?id=430949 Bug ID: 430949 Summary: digiKam-7.2.0-beta2 (macOS (DMG)) breaks existing local MySQL/MariaDB instances on upgrade Product: digikam Version: 7.2.0 Platform: macOS (DMG)

[plasmashell] [Bug 429631] SDDM crash after hardening

2020-11-25 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=429631 HD Scania changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|UPSTREAM

[plasmashell] [Bug 429631] SDDM crash after hardening

2020-11-25 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=429631 HD Scania changed: What|Removed |Added Assignee|plasma-b...@kde.org |hd-sca...@users.sf.net -- You are receiving

[plasmashell] [Bug 429631] SDDM crash after hardening

2020-11-25 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=429631 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net -- You are receiving

[plasmashell] [Bug 429631] SDDM crash after hardening

2020-11-25 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=429631 --- Comment #3 from HD Scania --- Created attachment 133637 --> https://bugs.kde.org/attachment.cgi?id=133637=edit My last known working sysctl.conf from a backup on an USB SSD -- You are receiving this mail because: You are watching all

[plasmashell] [Bug 429631] SDDM crash after hardening

2020-11-25 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=429631 --- Comment #2 from HD Scania --- Created attachment 133636 --> https://bugs.kde.org/attachment.cgi?id=133636=edit My current sysctl.conf with NO hardenings left, but SDDM is still being dead; see my first logfile that is the most recent SDDM sta

[plasmashell] [Bug 429631] SDDM crash after hardening

2020-11-25 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=429631 --- Comment #1 from HD Scania --- Created attachment 133635 --> https://bugs.kde.org/attachment.cgi?id=133635=edit The Lynis entries for kernel hardening, as of upgraing your scores for Lynis system auditing -- You are receiving this mail beca

[plasmashell] [Bug 429631] New: SDDM crash after hardening

2020-11-25 Thread HD Scania
Priority: NOR Component: generic-crash Assignee: plasma-b...@kde.org Reporter: hd-sca...@users.sf.net Target Milestone: 1.0 Created attachment 133634 --> https://bugs.kde.org/attachment.cgi?id=133634=edit My /var/log/sddm.log SUMMARY SDDM is being cras

[plasmashell] [Bug 419492] Plasma crashed immediately after login to Wayland session with an external monitor connected to hdmi port and mult-monitor mode set to "Switch to external screen"

2020-09-30 Thread Adarsha HD
https://bugs.kde.org/show_bug.cgi?id=419492 Adarsha HD changed: What|Removed |Added CC||m...@adarshahd.com -- You are receiving

[plasmashell] [Bug 426947] Global Plsama theme changes are crashing the shell

2020-09-25 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=426947 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net Assignee|plasma-b

[plasmashell] [Bug 426947] New: Global Plsama theme changes are crashing the shell

2020-09-25 Thread HD Scania
Severity: crash Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: hd-sca...@users.sf.net Target Milestone: 1.0 SUMMARY https://invent.kde.org/plasma/plasma-desktop/-/issues/10 STEPS TO REPRODUCE 1. Download new Plasma themes

[kdeconnect] [Bug 389010] devices cannot see eachother

2020-05-31 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=389010 HD Scania changed: What|Removed |Added OS|Linux |FreeBSD Version|1.2

[kdeconnect] [Bug 389010] devices cannot see eachother

2020-05-31 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=389010 --- Comment #10 from HD Scania --- I’m on HardenedBSD 13-CURRENT and has the same bugs there below, > https://git-01.md.hardenedbsd.org/HardenedBSD/hardenedbsd-ports/issues/5#issuecomment-107 And Mr. dSP, how is your ‘‘pcapng’’ file looked like? Ple

[kdeconnect] [Bug 389010] devices cannot see eachother

2020-05-31 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=389010 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net Assignee|albertv

[frameworks-plasma] [Bug 417530] PlasmaShell crashes due to "invalid metadata" at libs

2020-05-20 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=417530 HD Scania changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED

[plasmashell] [Bug 416491] Backgrounds, wallpapers, panels are locked at all, which are kept from getting done setting up.

2020-05-20 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=416491 HD Scania changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[kdeconnect] [Bug 421815] KDE Connect on HardenedBSD 13-CURRENT is unseen to my Android device, Samsung J7-2015 over KDE Connect

2020-05-20 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=421815 --- Comment #1 from HD Scania --- Created attachment 128630 --> https://bugs.kde.org/attachment.cgi?id=128630=edit This is how my HardenedBSD’s KDE Connect is looked like, which my Android device ‘‘j7eltexx’’ doesn’t show there -- You are receiv

[kdeconnect] [Bug 421814] The frontends, Plasmoids, modules were messed up

2020-05-20 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=421814 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net Assignee|albertv

[kdeconnect] [Bug 421815] KDE Connect on HardenedBSD 13-CURRENT is unseen to my Android device, Samsung J7-2015 over KDE Connect

2020-05-20 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=421815 HD Scania changed: What|Removed |Added Assignee|albertv...@gmail.com|hd-sca...@users.sf.net CC

[kdeconnect] [Bug 421815] New: KDE Connect on HardenedBSD 13-CURRENT is unseen to my Android device, Samsung J7-2015 over KDE Connect

2020-05-20 Thread HD Scania
Ports OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: hd-sca...@users.sf.net Target Milestone: --- Created attachment 128629 --> ht

[kdeconnect] [Bug 373327] KDE Connect cannot see laptop on the android app and can't see android on laptop

2020-05-20 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=373327 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net -- You are receiving

[kdeconnect] [Bug 421814] New: The frontends, Plasmoids, modules were messed up

2020-05-20 Thread HD Scania
: critical Priority: NOR Component: plasmoid Assignee: albertv...@gmail.com Reporter: hd-sca...@users.sf.net Target Milestone: --- Created attachment 128628 --> https://bugs.kde.org/attachment.cgi?id=128628=edit As which my final step of your reproduct

[frameworks-plasma] [Bug 417530] PlasmaShell crashes due to "invalid metadata" at libs

2020-02-12 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=417530 --- Comment #1 from HD Scania --- Created attachment 125922 --> https://bugs.kde.org/attachment.cgi?id=125922=edit What are libs metadata issue is looked like -- You are receiving this mail because: You are watching all bug changes.

[frameworks-plasma] [Bug 417530] PlasmaShell crashes due to "invalid metadata" at libs

2020-02-12 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=417530 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net Assignee|notm

[frameworks-plasma] [Bug 417530] New: PlasmaShell crashes due to "invalid metadata" at libs

2020-02-12 Thread HD Scania
Status: REPORTED Severity: crash Priority: NOR Component: libplasma Assignee: notm...@gmail.com Reporter: hd-sca...@users.sf.net CC: plasma-b...@kde.org Target Milestone: --- Created attachment 125921 --> https://bugs.kde.org/a

[Active Window Control] [Bug 416491] Backgrounds, wallpapers, panels are locked at all, which are kept from getting done setting up.

2020-01-24 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=416491 HD Scania changed: What|Removed |Added Assignee|zrenf...@gmail.com |hd-sca...@users.sf.net -- You are receiving

[Active Window Control] [Bug 416491] Backgrounds, wallpapers, panels are locked at all, which are kept from getting done setting up.

2020-01-20 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=416491 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net -- You are receiving

[Active Window Control] [Bug 416491] New: Backgrounds, wallpapers, panels are locked at all, which are kept from getting done setting up.

2020-01-20 Thread HD Scania
Platform: Netrunner Rolling OS: Linux Status: REPORTED Severity: major Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: hd-sca...@users.sf.net CC: plasma-b...@kde.org Target Milestone

[plasmashell] [Bug 416243] Plasma not ‎‎‘‘finishing customizing’’ panels

2020-01-14 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=416243 HD Scania changed: What|Removed |Added Assignee|k...@davidedmundson.co.uk|hd-sca...@users.sf.net -- You are receiving

[plasmashell] [Bug 416243] Plasma not ‎‎‘‘finishing customizing’’ panels

2020-01-14 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=416243 HD Scania changed: What|Removed |Added CC||hd-sca...@users.sf.net -- You are receiving

[plasmashell] [Bug 416243] Plasma not ‎‎‘‘finishing customizing’’ panels

2020-01-14 Thread HD Scania
https://bugs.kde.org/show_bug.cgi?id=416243 HD Scania changed: What|Removed |Added Component|general |Panel -- You are receiving this mail because: You

[plasma-integration] [Bug 416243] New: Plasma not ‎‎‘‘finishing customizing’’ panels

2020-01-14 Thread HD Scania
Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: hd-sca...@users.sf.net Target Milestone: --- Created attachment 125116 --> https://bugs.kde.org/attachment.cgi?id=125116=edit It never really ‘‘finis

[plasmashell] [Bug 414833] New: Plasma Crash When applying Global theme [Wayland]

2019-12-04 Thread Adarsha HD
https://bugs.kde.org/show_bug.cgi?id=414833 Bug ID: 414833 Summary: Plasma Crash When applying Global theme [Wayland] Product: plasmashell Version: 5.17.4 Platform: Fedora RPMs OS: Linux Status: REPORTED

[kfile] [Bug 373352] file open / save / save as dialog is slow if automounted filesystems are not available (nfs, smb, etc )

2017-11-11 Thread HD
https://bugs.kde.org/show_bug.cgi?id=373352 HD <haako...@ifi.uio.no> changed: What|Removed |Added CC||haako...@ifi.uio.no --- Comm

[okular] [Bug 383396] Okular doesn't remember window size

2017-08-13 Thread HD
https://bugs.kde.org/show_bug.cgi?id=383396 --- Comment #5 from HD <haako...@ifi.uio.no> --- Hi again, I've tried it on another computer also running debian stable and there size and position remembering works, so I agree, you can close this bug. Sorry I took your time and thanks for the h

[okular] [Bug 383396] Okular doesn't remember window size

2017-08-11 Thread HD
https://bugs.kde.org/show_bug.cgi?id=383396 --- Comment #3 from HD <haako...@ifi.uio.no> --- Thank you for replying! I removed the first few "garbage" entries, but that made no difference. What did make a difference was removing the various Height= and Width= entries. Now, t

[okular] [Bug 383396] New: Okular doesn't remember window size

2017-08-11 Thread HD
les data removed. Thanks for reading, HD -- You are receiving this mail because: You are watching all bug changes.

[kscreenlocker] [Bug 383327] New: Screen not locking on resume from suspend

2017-08-09 Thread HD
https://bugs.kde.org/show_bug.cgi?id=383327 Bug ID: 383327 Summary: Screen not locking on resume from suspend Product: kscreenlocker Version: 5.8.7 Platform: Debian stable OS: Linux Status: UNCONFIRMED

[systemsettings] [Bug 354962] login on rotated monitor is not rotated (works good after login)

2017-06-22 Thread HD
https://bugs.kde.org/show_bug.cgi?id=354962 HD <haako...@ifi.uio.no> changed: What|Removed |Added CC||haako...@ifi.uio.no --- Comm

[plasmashell] [Bug 381552] Multi-monitor setup, all monitors right of the rotated monitor overlap with that of their left neighbor

2017-06-22 Thread HD
https://bugs.kde.org/show_bug.cgi?id=381552 --- Comment #2 from HD <haako...@ifi.uio.no> --- Created attachment 106252 --> https://bugs.kde.org/attachment.cgi?id=106252=edit xrandr output -- You are receiving this mail because: You are watching all bug changes.

  1   2   >