[frameworks-kirigami] [Bug 443146] New: Anchor setting issue in AboutPage.qml
https://bugs.kde.org/show_bug.cgi?id=443146 Bug ID: 443146 Summary: Anchor setting issue in AboutPage.qml Product: frameworks-kirigami Version: Master Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: snehit...@protonmail.com Target Milestone: Not decided SUMMARY This line contains a typo in "parent" https://invent.kde.org/frameworks/kirigami/-/blob/master/src/controls/AboutPage.qml#L56 However, "anchors.fill: parent" doesn't seem to be the correct property, as it left aligns the about page, whereas we want it to be center aligned. Removing the line produces the desired result. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS (available in About System) KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.13.2 -- You are receiving this mail because: You are watching all bug changes.
[LabPlot2] [Bug 451623] New: Tag 2.8.2 missing on GitLab repository
https://bugs.kde.org/show_bug.cgi?id=451623 Bug ID: 451623 Summary: Tag 2.8.2 missing on GitLab repository Product: LabPlot2 Version: unspecified Platform: unspecified OS: Unspecified Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: snehit...@protonmail.com Target Milestone: --- SUMMARY Git repository tags https://invent.kde.org/education/labplot/-/tags don't have 2.8.2. The version is available on https://download.kde.org/stable/labplot/ STEPS TO REPRODUCE 1. Visit https://invent.kde.org/education/labplot/-/tags OBSERVED RESULT Tag for version 2.8.2 not shown. EXPECTED RESULT Tag for version 2.8.2 should be shown, as that version does exist. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 443146] Anchor setting issue in AboutPage.qml
https://bugs.kde.org/show_bug.cgi?id=443146 --- Comment #2 from Snehit Sah --- (In reply to Nate Graham from comment #1) > Good catch. In fact the problem is that "parent" is misspelled; it says > "parnet" instead! Wanna fix it? You can submit a merge request here: > https://invent.kde.org/frameworks/kirigami/-/merge_requests/ Thanks! I have created a merge request : https://invent.kde.org/frameworks/kirigami/-/merge_requests/384 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 435874] Ark should warn about closing its window while an extraction is in progress
https://bugs.kde.org/show_bug.cgi?id=435874 Snehit Sah changed: What|Removed |Added CC||flyingcake...@gmail.com --- Comment #1 from Snehit Sah --- I would like to submit a patch for this. I have already added an exit confirmation dialog, but am stuck because I can't seem to figure out how to detect if an extraction or compression job is in progress. Some help on this and I'll have a an MR ready. Thanks -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 435874] Ark should warn about closing its window while an extraction is in progress
https://bugs.kde.org/show_bug.cgi?id=435874 Snehit Sah changed: What|Removed |Added CC||snehit...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 448719] New: Install process does not respect prefix
https://bugs.kde.org/show_bug.cgi?id=448719 Bug ID: 448719 Summary: Install process does not respect prefix Product: kalarm Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: snehit...@protonmail.com Target Milestone: --- Created attachment 145617 --> https://bugs.kde.org/attachment.cgi?id=145617&action=edit build_log.txt : output of flatpak's build process including only the log from installing/building kalarm SUMMARY When installing KAlarm from source, it does not respect prefix for all install directives, and hence fails trying to access /usr/lib when installing to a user directory. I am trying to package KAlarm for Flathub which requires installing it to a user folder and packaging. The above mentioned issue is preventing me from doing so. STEPS TO REPRODUCE Install KAlarm in a user directory without superuser privileges. OBSERVED RESULT Install fails with following message ``` -- Installing: /usr/lib/x86_64-linux-gnu/libexec/kauth/kalarm_helper CMake Error at src/cmake_install.cmake:119 (file): file INSTALL cannot copy file "/run/build/kalarm/bin/kalarm_helper" to "/usr/lib/x86_64-linux-gnu/libexec/kauth/kalarm_helper": Read-only file system. Call Stack (most recent call first): cmake_install.cmake:47 (include) FAILED: CMakeFiles/install.util cd /run/build/kalarm && /usr/bin/cmake -P cmake_install.cmake ninja: build stopped: subcommand failed. Error: module kalarm: Child process exited with code 1 ``` EXPECTED RESULT KAlarm should install to user directory without accessing root ADDITIONAL INFORMATION Source tarball obtained from : https://download.kde.org/stable/release-service/21.12.1/src/kalarm-21.12.1.tar.xz Build log attached with bug report. -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 448764] New: KDF should not rely on having Dolphin in runtime
https://bugs.kde.org/show_bug.cgi?id=448764 Bug ID: 448764 Summary: KDF should not rely on having Dolphin in runtime Product: kdf Version: 21.12.1 Platform: Compiled Sources OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: snehit...@protonmail.com Target Milestone: --- SUMMARY KDF currently relies on having Dolphin installed to be able to open a disk in file explorer. The choice seems to be hardcoded in source code https://invent.kde.org/utilities/kdf/-/blob/master/src/stdoption.cpp#L16 A better way to open local paths might be to use QUrl::fromLocalFile and pass it to QDesktopServices::openUrl This will ensure that disk is opened in whichever file manager is available on user's system, rather than assuming that Dolphin is always available. STEPS TO REPRODUCE Install KDF on a system without Dolphin. In KDF, right click on a disk and select "Open in File Manager". OBSERVED RESULT Nothing happens EXPECTED RESULT Disk should open in whichever file manager is available on user's system. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 438530] ./kdesrc-build --initial-setup adds invalid `complete` command to .zshrc
https://bugs.kde.org/show_bug.cgi?id=438530 Snehit Sah changed: What|Removed |Added CC||snehit...@protonmail.com --- Comment #2 from Snehit Sah --- Adding `autoload -U +X bashcompinit && bashcompinit` before the call to `complete` removed the error for me. -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 438530] ./kdesrc-build --initial-setup adds invalid `complete` command to .zshrc
https://bugs.kde.org/show_bug.cgi?id=438530 --- Comment #3 from Snehit Sah --- I have added a tiny note on wiki page : https://community.kde.org/index.php?title=Get_Involved/development&diff=prev&oldid=93638 -- You are receiving this mail because: You are watching all bug changes.
[kdf] [Bug 448764] KDF should not rely on having Dolphin in runtime
https://bugs.kde.org/show_bug.cgi?id=448764 --- Comment #3 from Snehit Sah --- Thanks for the acknowledgement about opening default file manager. I'll send a merge request soon. -- You are receiving this mail because: You are watching all bug changes.
