KDE CI: Frameworks » kcalendarcore » kf5-qt5 WindowsMSVCQt5.15 - Build # 32 - Fixed!

2021-01-31 Thread CI System 
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20WindowsMSVCQt5.15/32/
 Project:
kf5-qt5 WindowsMSVCQt5.15
 Date of build:
Mon, 01 Feb 2021 01:37:03 +
 Build duration:
1 hr 16 min and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 493 test(s), Skipped: 0 test(s), Total: 493 test(s)

KDE CI: Frameworks » kcalendarcore » kf5-qt5 SUSEQt5.15 - Build # 52 - Fixed!

2021-01-31 Thread CI System 
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20SUSEQt5.15/52/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Mon, 01 Feb 2021 02:32:59 +
 Build duration:
16 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5CalendarCore-5.79.0.xmlcompat_reports/KF5CalendarCore_compat_report.htmllogs/KF5CalendarCore/5.79.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 494 test(s), Skipped: 0 test(s), Total: 494 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(2/2)95%
(88/93)95%
(88/93)71%
(9707/13696)50%
(4534/9049)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(40/40)100%
(40/40)96%
(3090/3213)52%
(944/1818)src91%
(48/53)91%
(48/53)63%
(6617/10483)50%
(3590/7231)

KDE CI: Frameworks » kservice » kf5-qt5 SUSEQt5.15 - Build # 97 - Still Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kservice/job/kf5-qt5%20SUSEQt5.15/97/
 Project:
kf5-qt5 SUSEQt5.15
 Date of build:
Mon, 01 Feb 2021 02:32:57 +
 Build duration:
13 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5Service-5.79.0.xmlcompat_reports/KF5Service_compat_report.htmllogs/KF5Service/5.79.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.ksycocathreadtestName: projectroot.tests Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report88%
(7/8)84%
(78/93)84%
(78/93)69%
(5883/8484)47%
(2556/5392)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests93%
(14/15)93%
(14/15)87%
(1570/1801)46%
(660/1441)src.kbuildsycoca100%
(1/1)100%
(1/1)91%
(51/56)38%
(3/8)src.kdeinit67%
(2/3)67%
(2/3)6%
(22/356)8%
(18/237)src.plugin67%
(2/3)67%
(2/3)50%
(49/98)38%
(29/77)src.services94%
(32/34)94%
(32/34)63%
(1978/3164)42%
(784/1860)src.sycoca83%
(24/29)83%
(24/29)76%
(2110/2777)61%
(1046/1711)tests0%
(0/5)0%
(0/5)0%
(0/117)0%
(0/34)tests.pluginlocator100%
(3/3)100%
(3/3)90%
(103/115)67%
(16/24)

KDE CI: Frameworks » ktexteditor » kf5-qt5 SUSEQt5.14 - Build # 121 - Fixed!

2021-01-31 Thread CI System 
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/ktexteditor/job/kf5-qt5%20SUSEQt5.14/121/
 Project:
kf5-qt5 SUSEQt5.14
 Date of build:
Mon, 01 Feb 2021 01:46:24 +
 Build duration:
34 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5TextEditor-5.79.0.xmlcompat_reports/KF5TextEditor_compat_report.htmllogs/KF5TextEditor/5.79.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 63 test(s), Skipped: 0 test(s), Total: 63 test(s)Name: projectroot.autotests.src Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report75%
(21/28)85%
(259/303)85%
(259/303)67%
(33411/49723)49%
(14971/30338)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests.src100%
(39/39)100%
(39/39)94%
(5095/5407)49%
(1899/3844)autotests.src.benchmarks0%
(0/1)0%
(0/1)0%
(0/32)0%
(0/6)autotests.src.vimode100%
(9/9)100%
(9/9)99%
(5551/5594)58%
(984/1708)src.buffer88%
(15/17)88%
(15/17)89%
(1703/1921)73%
(1080/1472)src.completion100%
(11/11)100%
(11/11)57%
(1798/3148)42%
(1009/2425)src.completion.expandingtree100%
(3/3)100%
(3/3)40%
(182/458)21%
(73/340)src.dialogs0%
(0/4)0%
(0/4)0%
(0/869)0%
(0/188)src.document100%
(4/4)100%
(4/4)61%
(1958/3208)48%
(1419/2955)src.export0%
(0/4)0%
(0/4)0%
(0/137)0%
(0/158)src.include.ktexteditor79%
(15/19)79%
(15/19)85%
(226/267)57%
(136/240)src.inputmode100%
(8/8)100%
(8/8)67%
(204/306)56%
(43/77)src.mode88%
(7/8)88%
(7/8)36%
(379/1067)16%
(146/891)src.part0%
(0/1)0%
(0/1)0%
(0/7)100%
(0/0)src.printing0%
(0/4)0%
(0/4)0%
(0/862)0%
(0/282)src.render100%
(8/8)100%
(8/8)76%
(918/1214)66%
(600/914)src.script94%
(16/17)94%
(16/17)66%
(693/1057)51%
(207/409)src.search100%
(5/5)100%

KDE CI: Frameworks » kcalendarcore » kf5-qt5 SUSEQt5.14 - Build # 20 - Fixed!

2021-01-31 Thread CI System 
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20SUSEQt5.14/20/
 Project:
kf5-qt5 SUSEQt5.14
 Date of build:
Mon, 01 Feb 2021 01:46:27 +
 Build duration:
27 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5CalendarCore-5.79.0.xmlcompat_reports/KF5CalendarCore_compat_report.htmllogs/KF5CalendarCore/5.79.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 494 test(s), Skipped: 0 test(s), Total: 494 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report100%
(2/2)95%
(88/93)95%
(88/93)71%
(9706/13696)50%
(4533/9049)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests100%
(40/40)100%
(40/40)96%
(3090/3213)52%
(944/1818)src91%
(48/53)91%
(48/53)63%
(6616/10483)50%
(3589/7231)

KDE CI: Frameworks » kservice » kf5-qt5 SUSEQt5.14 - Build # 34 - Still Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kservice/job/kf5-qt5%20SUSEQt5.14/34/
 Project:
kf5-qt5 SUSEQt5.14
 Date of build:
Mon, 01 Feb 2021 01:46:25 +
 Build duration:
23 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5Service-5.79.0.xmlcompat_reports/KF5Service_compat_report.htmllogs/KF5Service/5.79.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.ksycocathreadtestName: projectroot.tests Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report88%
(7/8)84%
(78/93)84%
(78/93)69%
(5882/8484)47%
(2554/5392)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests93%
(14/15)93%
(14/15)87%
(1570/1801)46%
(660/1441)src.kbuildsycoca100%
(1/1)100%
(1/1)91%
(51/56)38%
(3/8)src.kdeinit67%
(2/3)67%
(2/3)6%
(22/356)8%
(18/237)src.plugin67%
(2/3)67%
(2/3)50%
(49/98)38%
(29/77)src.services94%
(32/34)94%
(32/34)62%
(1977/3164)42%
(782/1860)src.sycoca83%
(24/29)83%
(24/29)76%
(2110/2777)61%
(1046/1711)tests0%
(0/5)0%
(0/5)0%
(0/117)0%
(0/34)tests.pluginlocator100%
(3/3)100%
(3/3)90%
(103/115)67%
(16/24)

KDE CI: Frameworks » frameworkintegration » kf5-qt5 WindowsMSVCQt5.15 - Build # 26 - Fixed!

2021-01-31 Thread CI System 
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/frameworkintegration/job/kf5-qt5%20WindowsMSVCQt5.15/26/
 Project:
kf5-qt5 WindowsMSVCQt5.15
 Date of build:
Mon, 01 Feb 2021 01:36:59 +
 Build duration:
32 min and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)

KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 563 - Still Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/563/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Mon, 01 Feb 2021 01:31:21 +
 Build duration:
31 min and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 53 test(s), Skipped: 0 test(s), Total: 55 test(s)Failed: projectroot.autotests.kiofilewidgets_kfilecustomdialogtestFailed: projectroot.autotests.kiofilewidgets_kfilewidgettestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)

KDE CI: Frameworks » kwayland » kf5-qt5 FreeBSDQt5.15 - Build # 48 - Still Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kwayland/job/kf5-qt5%20FreeBSDQt5.15/48/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Mon, 01 Feb 2021 01:31:18 +
 Build duration:
28 min and counting
   JUnit Tests
  Name: projectroot.autotests Failed: 13 test(s), Passed: 30 test(s), Skipped: 0 test(s), Total: 43 test(s)Failed: projectroot.autotests.client.kwayland_testCompositorFailed: projectroot.autotests.client.kwayland_testDataDeviceFailed: projectroot.autotests.client.kwayland_testDataSourceFailed: projectroot.autotests.client.kwayland_testRegionFailed: projectroot.autotests.client.kwayland_testShmPoolFailed: projectroot.autotests.client.kwayland_testSubCompositorFailed: projectroot.autotests.client.kwayland_testSubSurfaceFailed: projectroot.autotests.client.kwayland_testWaylandConnectionThreadFailed: projectroot.autotests.client.kwayland_testWaylandRegistryFailed: projectroot.autotests.client.kwayland_testWaylandShellFailed: projectroot.autotests.client.kwayland_testWaylandSurfaceFailed: projectroot.autotests.server.kwayland_testQtSurfaceExtensionFailed: projectroot.autotests.server.kwayland_testWaylandServerDisplay

KDE CI: Frameworks » knewstuff » kf5-qt5 FreeBSDQt5.15 - Build # 195 - Fixed!

2021-01-31 Thread CI System 
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/knewstuff/job/kf5-qt5%20FreeBSDQt5.15/195/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Mon, 01 Feb 2021 01:31:23 +
 Build duration:
23 min and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 2 test(s), Skipped: 0 test(s), Total: 2 test(s)Name: projectroot.autotests Failed: 0 test(s), Passed: 3 test(s), Skipped: 0 test(s), Total: 3 test(s)

KDE CI: Frameworks » ktexteditor » kf5-qt5 FreeBSDQt5.15 - Build # 217 - Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/ktexteditor/job/kf5-qt5%20FreeBSDQt5.15/217/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Mon, 01 Feb 2021 01:31:18 +
 Build duration:
20 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 62 test(s), Skipped: 0 test(s), Total: 63 test(s)Failed: projectroot.autotests.kateindenttest_testCstyleName: projectroot.autotests.src Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)

KDE CI: Frameworks » kbookmarks » kf5-qt5 WindowsMSVCQt5.15 - Build # 21 - Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kbookmarks/job/kf5-qt5%20WindowsMSVCQt5.15/21/
 Project:
kf5-qt5 WindowsMSVCQt5.15
 Date of build:
Mon, 01 Feb 2021 01:37:04 +
 Build duration:
14 min and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 2 test(s)Failed: projectroot.autotests.kbookmarktest

KDE CI: Frameworks » kcalendarcore » kf5-qt5 FreeBSDQt5.15 - Build # 49 - Fixed!

2021-01-31 Thread CI System 
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kcalendarcore/job/kf5-qt5%20FreeBSDQt5.15/49/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Mon, 01 Feb 2021 01:31:22 +
 Build duration:
17 min and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 494 test(s), Skipped: 0 test(s), Total: 494 test(s)

KDE CI: Frameworks » kservice » kf5-qt5 FreeBSDQt5.15 - Build # 88 - Still Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kservice/job/kf5-qt5%20FreeBSDQt5.15/88/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Mon, 01 Feb 2021 01:31:18 +
 Build duration:
8 min 49 sec and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 10 test(s), Skipped: 0 test(s), Total: 11 test(s)Failed: projectroot.autotests.ksycocathreadtestName: projectroot.tests Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)

KDE CI: Frameworks » kcoreaddons » kf5-qt5 FreeBSDQt5.15 - Build # 158 - Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kcoreaddons/job/kf5-qt5%20FreeBSDQt5.15/158/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Mon, 01 Feb 2021 01:31:23 +
 Build duration:
4 min 14 sec and counting
   JUnit Tests
  Name: projectroot Failed: 1 test(s), Passed: 26 test(s), Skipped: 0 test(s), Total: 27 test(s)Failed: projectroot.autotests.kdirwatch_inotify_unittest

KDE CI: Frameworks » kdav » kf5-qt5 FreeBSDQt5.15 - Build # 38 - Fixed!

2021-01-31 Thread CI System 
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/kdav/job/kf5-qt5%20FreeBSDQt5.15/38/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Mon, 01 Feb 2021 01:31:21 +
 Build duration:
1 min 32 sec and counting
   JUnit Tests
  Name: projectroot Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)

Re: KDE Frameworks 6 - Virtual Sprint setup

2021-01-31 Thread Aleix Pol 
On Fri, Jan 29, 2021 at 5:24 PM Adam Szopa  wrote:
>
> Hello,
>
> I've been talking with David Faure about setting up a Sprint focused on KF6  
> work. Some of the topics would include:
>
> - Reviewing the KF6 board (https://phabricator.kde.org/project/board/310/[1]):
>
> -- Clean up
>
> -- Tagging Junior Jobs
>
> - Working out a structure/process for handling:
>
> -- "Stuck" tasks
>
> -- Unit test regressions
>
> - Decide the 5.15 minimum requirement bump timeline
>
> - Decide on a 6 branching strategy and timeline
>
> - Decide if/how ECM should support multiple Qt versions
>
>
> That's just an example list - the wiki should include the up to date and 
> detailed topics.
>
>
> The Sprint will use the KDE BBB instance - same tech that powered last years  
> Akademy; I'll coordinate that with our sysadmins to have it available.
>
>
> As for the date and length, usually Virtual Sprints are a weekend thing. I'd
>
> love to hear from you if that sounds OK, and which weekend would be workable
>
> for you (how soon can we get this started) and your preferred availability
>
> hours. I'll set up a poll later to pinpoint the final timing.
>
>
> Thanks,
>
> - Adam

+1! :)

KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 562 - Still Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/562/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sun, 31 Jan 2021 20:17:58 +
 Build duration:
3 min 17 sec and counting
   JUnit Tests
  Name: projectroot Failed: 2 test(s), Passed: 53 test(s), Skipped: 0 test(s), Total: 55 test(s)Failed: projectroot.autotests.kiofilewidgets_kfilecustomdialogtestFailed: projectroot.autotests.kiofilewidgets_kfilewidgettestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)

KDE CI: Frameworks » kio » kf5-qt5 FreeBSDQt5.15 - Build # 561 - Still Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/kio/job/kf5-qt5%20FreeBSDQt5.15/561/
 Project:
kf5-qt5 FreeBSDQt5.15
 Date of build:
Sun, 31 Jan 2021 20:08:41 +
 Build duration:
9 min 14 sec and counting
   JUnit Tests
  Name: projectroot Failed: 3 test(s), Passed: 52 test(s), Skipped: 0 test(s), Total: 55 test(s)Failed: projectroot.autotests.commandlauncherjob_scopetestFailed: projectroot.autotests.kiofilewidgets_kfilecustomdialogtestFailed: projectroot.autotests.kiofilewidgets_kfilewidgettestName: projectroot.autotests Failed: 0 test(s), Passed: 6 test(s), Skipped: 0 test(s), Total: 6 test(s)Name: projectroot.src.ioslaves.trash Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot.src.kpasswdserver Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)

Re: RFC: relative executables in desktop files

2021-01-31 Thread David Faure 
On dimanche 10 mai 2020 19:17:01 CET Aleix Pol wrote:
> On Sun, Apr 26, 2020 at 1:36 PM David Faure  wrote:
> > During the review of https://phabricator.kde.org/D29170 the following
> > question surfaced again: should it be possible for a desktop file to
> > refer to an executable that is in the "current directory", for some
> > definition of that term. At least, outside of $PATH.
> > 
> > In my opinion, in a GUI program started graphically, the notion of
> > "current dir" (QDir::currentPath()) has no meaning. The user can't see it
> > and can't change it. When starting the program from the command line it
> > does serve a purpose for command line arguments, but IMHO not after that
> > (e.g. if you navigate to another dir in dolphin, QDir::currentPath()
> > still points to the directory you started dolphin from).
> > 
> > There is however another "current directory" that might make more sense
> > when starting a desktop file: the directory of the desktop file itself.
> > 
> > There are actual use cases for that, see this very old request on the XDG
> > mailing-list:
> > https://lists.freedesktop.org/archives/xdg/2011-April/011883.html
> > 
> > AFAICS this discussion has 3 possible outcomes:
> > 
> > * We do not support starting executables that are not in $PATH, end of
> > story. That was actually what I had in mind when writing the code
> > initially, any use of API that also looked in the current directory (like
> > QFileInfo::exists) was accidental. Unless I'm mistaken, this is how it's
> > been until now. It's also what the XDG spec [1] says.
> > 
> > * We support launching executables relative to the desktop file,
> > transparently. In the same directory, put a copy of dolphin called
> > dolphin2, and a copy of org.kde.dolphin.desktop modified to say
> > Exec=dolphin2, and clicking on the desktop file starts dolphin2. That's
> > what my current revision of D29170 does. I'm wondering if this is the
> > right thing to do though.
> > After all, on the command line "foo" doesn't start a local executable
> > called foo, only ./foo does that. Except for people who add "." to $PATH,
> > but that's generally not recommended (security, accidental use of wrong
> > binary).
> > 
> > * We could also adopt the above proposal from the xdg list, which is that
> > Exec=foo only looks in $PATH, while Exec=./foo only looks in the
> > directory of the desktop file.
> > 
> > (I'm purposefully excluding the 4th option, resolving relative to
> > QDir::currentPath() which as explained at the top, would be nonsense
> > IMHO)
> > 
> > Thoughts?
> 
> One thing to note, which is probably easy to support: at the moment in
> kwin we're relying on certain apps to be defined in absolute paths for
> some security measures.
> 
> Just supporting $PATH makes most sense to me, there's increasingly
> other ways to distribute software that abstract XDG out (e.g. snap,
> appimage and flatpak). Weird custom uses should become increasingly
> more rare over time.

Hi Aleix,
There's some interest in reviving this discussion, about the usefulness of 
relative paths (for the Exec field of desktop files) even in the case of 
AppImages. See 
https://gitlab.freedesktop.org/xdg/xdg-specs/-/issues/71

I would be very interested in getting your feedback (you and anyone else of 
course) in that issue (not here please).

-- 
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5

Re: KDE Frameworks 6 - Virtual Sprint setup

2021-01-31 Thread Christoph Cullmann 

On 2021-01-30 12:14, Volker Krause wrote:

On Freitag, 29. Januar 2021 15:57:59 CET Adam Szopa wrote:

Hello,
I've been talking with David Faure about setting up a Sprint focused 
on KF6

work. Some of the topics would include:
- Reviewing the KF6 board
(https://phabricator.kde.org/project/board/310/[1]): -- Clean up
-- Tagging Junior Jobs
- Working out a structure/process for handling:
-- "Stuck" tasks
-- Unit test regressions
- Decide the 5.15 minimum requirement bump timeline
- Decide on a 6 branching strategy and timeline
- Decide if/how ECM should support multiple Qt versions

That's just an example list - the wiki[1] should include the up to 
date and

detailed topics.

The Sprint will use the KDE BBB instance - same tech that powered last 
years
 Akademy; I'll coordinate that with our sysadmins to have it 
available.


As for the date and length, usually Virtual Sprints are a weekend 
thing. I'd

love to hear from you if that sounds OK, and which weekend would be
workable for you (how soon can we get this started) and your preferred
availability hours. I'll set up a poll later to pinpoint the final 
timing.


Thanks for driving this, I'm in! European hours preferred, any weekend
starting from w6 should be possible.

Count me in, too ;=)
European hours preferred.

Greetings
Christoph

--
Ignorance is bliss...
https://cullmann.io | https://kate-editor.org

KDE CI: Frameworks » ktexteditor » kf5-qt5 SUSEQt5.14 - Build # 120 - Unstable!

2021-01-31 Thread CI System 
BUILD UNSTABLE
 Build URL
https://build.kde.org/job/Frameworks/job/ktexteditor/job/kf5-qt5%20SUSEQt5.14/120/
 Project:
kf5-qt5 SUSEQt5.14
 Date of build:
Sun, 31 Jan 2021 14:07:53 +
 Build duration:
16 min and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5TextEditor-5.79.0.xmlcompat_reports/KF5TextEditor_compat_report.htmllogs/KF5TextEditor/5.79.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 1 test(s), Passed: 62 test(s), Skipped: 0 test(s), Total: 63 test(s)Failed: projectroot.autotests.kateindenttest_testCstyleName: projectroot.autotests.src Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report75%
(21/28)85%
(259/303)85%
(259/303)67%
(33341/49715)49%
(14941/30338)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests.src100%
(39/39)100%
(39/39)94%
(5065/5404)49%
(1892/3844)autotests.src.benchmarks0%
(0/1)0%
(0/1)0%
(0/32)0%
(0/6)autotests.src.vimode100%
(9/9)100%
(9/9)99%
(5551/5594)58%
(984/1708)src.buffer88%
(15/17)88%
(15/17)89%
(1702/1921)73%
(1079/1472)src.completion100%
(11/11)100%
(11/11)57%
(1798/3148)42%
(1009/2425)src.completion.expandingtree100%
(3/3)100%
(3/3)40%
(182/458)21%
(73/340)src.dialogs0%
(0/4)0%
(0/4)0%
(0/869)0%
(0/188)src.document100%
(4/4)100%
(4/4)61%
(1954/3208)48%
(1411/2955)src.export0%
(0/4)0%
(0/4)0%
(0/137)0%
(0/158)src.include.ktexteditor79%
(15/19)79%
(15/19)85%
(226/267)57%
(136/240)src.inputmode100%
(8/8)100%
(8/8)67%
(204/306)56%
(43/77)src.mode88%
(7/8)88%
(7/8)36%
(379/1067)16%
(146/891)src.part0%
(0/1)0%
(0/1)0%
(0/7)100%
(0/0)src.printing0%
(0/4)0%
(0/4)0%
(0/862)0%
(0/282)src.render100%
(8/8)100%
(8/8)76%
(918/1214)66%
(600/914)src.script94%
(16/17)94%
(16/17)64%
(671/1054)48%

KDE CI: Frameworks » ktexteditor » kf5-qt5 SUSEQt5.14 - Build # 119 - Fixed!

2021-01-31 Thread CI System 
BUILD SUCCESS
 Build URL
https://build.kde.org/job/Frameworks/job/ktexteditor/job/kf5-qt5%20SUSEQt5.14/119/
 Project:
kf5-qt5 SUSEQt5.14
 Date of build:
Sun, 31 Jan 2021 13:58:07 +
 Build duration:
9 min 46 sec and counting
   BUILD ARTIFACTS
  abi-compatibility-results.yamlacc/KF5TextEditor-5.79.0.xmlcompat_reports/KF5TextEditor_compat_report.htmllogs/KF5TextEditor/5.79.0/log.txt
   JUnit Tests
  Name: (root) Failed: 0 test(s), Passed: 1 test(s), Skipped: 0 test(s), Total: 1 test(s)Name: projectroot Failed: 0 test(s), Passed: 63 test(s), Skipped: 0 test(s), Total: 63 test(s)Name: projectroot.autotests.src Failed: 0 test(s), Passed: 5 test(s), Skipped: 0 test(s), Total: 5 test(s)
   Cobertura Report
  
   Project Coverage Summary
  
   Name
  PackagesFilesClassesLinesConditionalsCobertura Coverage Report75%
(21/28)85%
(259/303)85%
(259/303)67%
(33437/49723)49%
(14985/30338)Coverage Breakdown by Package
Name
   FilesClassesLinesConditionalsautotests.src100%
(39/39)100%
(39/39)94%
(5095/5407)49%
(1899/3844)autotests.src.benchmarks0%
(0/1)0%
(0/1)0%
(0/32)0%
(0/6)autotests.src.vimode100%
(9/9)100%
(9/9)99%
(5551/5594)58%
(984/1708)src.buffer88%
(15/17)88%
(15/17)89%
(1703/1921)73%
(1080/1472)src.completion100%
(11/11)100%
(11/11)57%
(1798/3148)42%
(1009/2425)src.completion.expandingtree100%
(3/3)100%
(3/3)40%
(182/458)21%
(73/340)src.dialogs0%
(0/4)0%
(0/4)0%
(0/869)0%
(0/188)src.document100%
(4/4)100%
(4/4)61%
(1958/3208)48%
(1419/2955)src.export0%
(0/4)0%
(0/4)0%
(0/137)0%
(0/158)src.include.ktexteditor79%
(15/19)79%
(15/19)85%
(226/267)57%
(136/240)src.inputmode100%
(8/8)100%
(8/8)67%
(204/306)56%
(43/77)src.mode88%
(7/8)88%
(7/8)36%
(379/1067)16%
(146/891)src.part0%
(0/1)0%
(0/1)0%
(0/7)100%
(0/0)src.printing0%
(0/4)0%
(0/4)0%
(0/862)0%
(0/282)src.render100%
(8/8)100%
(8/8)77%
(940/1214)67%
(612/914)src.script94%
(16/17)94%
(16/17)66%
(693/1057)51%
(207/409)src.search100%

D27224: add Kongress icon

2021-01-31 Thread Ahmad Samir 
ahmadsamir added a comment.


  Hello. FWIW, I would also close/abandon this diff :) (nice icon BTW).

REPOSITORY
  R266 Breeze Icons

REVISION DETAIL
  https://phabricator.kde.org/D27224

To: mbruchert, dkardarakos, #vdg, ndavis
Cc: ahmadsamir, ndavis, kde-frameworks-devel, LeGast00n, cblack, michaelh, 
ngraham, bruns

D27224: add Kongress icon

2021-01-31 Thread Dimitris Kardarakos 
dkardarakos added a comment.


  Created this MR 
  to 
continue the review on invent.

REPOSITORY
  R266 Breeze Icons

REVISION DETAIL
  https://phabricator.kde.org/D27224

To: mbruchert, dkardarakos, #vdg, ndavis
Cc: ndavis, kde-frameworks-devel, LeGast00n, cblack, michaelh, ngraham, bruns

Re: Need xcb/xkb help for severe kglobalaccel_x11 issue

2021-01-31 Thread David Faure 
On dimanche 31 janvier 2021 00:30:14 CET Fabian Vogt wrote:
> I suspect that something else is triggering keyboard layout reloads or
> similar in a loop. The keyboard kded module listens for new keyboards and
> mouse events and configures them, which is likely to be called on resume
> when devices get reenumerated. You could try to disable that before
> suspend/resume.

Well spotted. After
qdbus org.kde.kded5 /kded unloadModule keyboard
and suspend/resume, I got only one call to KGlobalAccelImpl::x11MappingNotify

This is amazing. Suddenly it manages to reconnect to wifi instantly, too,
and my global shortcuts work instantly.
Previously, kded kept everyone so busy that everything crawled for about a 
minute, and wifi timed out...
 
> If I run "xmodmap .Xmodmap" here with "xev" open, I get quite a high count
> of mapping change events, presumably for every assignment in the file. If
> the kded calls xmodmap with many assignments, that would be enough to
> explain the issue. Maybe xmodmap could be optimized to upload everything at
> once, like setxkbmap.

I debugged what happens in plasma-desktop/kcms/keyboard
and when resuming from suspend, XInputEventNotifier::processOtherEvents()
emits newKeyboardDevice() many many times.
Each time, the slot KeyboardDaemon::configureKeyboard() does all this

KeyboardConfig::load configuring layouts true configuring options true
X11Helper::getGroupNames Fetched keyboard model from X server: "pc101"
XkbHelper::runConfigLayoutCommand Executed successfully in  137 ms 
"/usr/bin/setxkbmap -layout us,fr -option -option compose:caps"
XkbHelper::runConfigLayoutCommandand with xmodmap 137 ms
X11Helper::getGroupNames Fetched layout groups from X server:   layouts: 
("us", "fr")   variants: ("", "")
KeyboardLayoutActionCollection::loadLayoutShortcuts Skipping empty shortcut for 
"us"
KeyboardLayoutActionCollection::loadLayoutShortcuts Skipping empty shortcut for 
"fr"
KeyboardLayoutActionCollection::loadLayoutShortcuts Cleaning component 
shortcuts on load true

Going back up, the reason why processOtherEvents() thinks there's a new device 
is this:

XInputEventNotifier::getNewDeviceEventType New device id: 15
XInputEventNotifier::getNewDeviceEventType id: 2 name: Virtual core pointer 
used as: 0
XInputEventNotifier::getNewDeviceEventType id: 3 name: Virtual core keyboard 
used as: 1
XInputEventNotifier::getNewDeviceEventType id: 4 name: Virtual core XTEST 
pointer used as: 4
XInputEventNotifier::getNewDeviceEventType id: 5 name: Virtual core XTEST 
keyboard used as: 3
XInputEventNotifier::getNewDeviceEventType id: 6 name: Power Button used as: 3
XInputEventNotifier::getNewDeviceEventType id: 7 name: Video Bus used as: 3
XInputEventNotifier::getNewDeviceEventType id: 8 name: Sleep Button used as: 3
XInputEventNotifier::getNewDeviceEventType id: 9 name: Logitech Craft used as: 4
XInputEventNotifier::getNewDeviceEventType id: 10 name: Logitech MX Master 2S 
used as: 4
XInputEventNotifier::getNewDeviceEventType id: 11 name: Logitech MX Master used 
as: 4
XInputEventNotifier::getNewDeviceEventType id: 12 name: Integrated Camera: 
Integrated C used as: 3
XInputEventNotifier::getNewDeviceEventType id: 13 name: Integrated Camera: 
Integrated I used as: 3
XInputEventNotifier::getNewDeviceEventType id: 14 name: AT Translated Set 2 
keyboard used as: 3
XInputEventNotifier::getNewDeviceEventType id: 15 name: SynPS/2 Synaptics 
TouchPad used as: 4
XInputEventNotifier::getNewDeviceEventType new pointer device, id: 15 name: 
SynPS/2 Synaptics TouchPad used as: 

Before that, it got notified of new device 6, 7, 8, and so on.
It's like X is re-enabling the devices one after the other, and we react to 
each one immediately.

This misdetects the device types though:
   new keyboard device, id: 13 name: Integrated Camera: Integrated I used as: 3
No, my webcam doesn't have keys...

And for some reason, even mouse devices trigger keyboard processing, see the 
arghh comment:

bool XInputEventNotifier::processOtherEvents(xcb_generic_event_t* event)
{
int newDeviceType = getNewDeviceEventType(event);
if( newDeviceType == DEVICE_KEYBOARD ) {
emit(newKeyboardDevice());
}
else if( newDeviceType == DEVICE_POINTER ) {
emit(newPointerDevice());
emit(newKeyboardDevice());  // arghhh, looks like X resets xkb map even 
when only pointer device is connected
}
return true;
}

> I actually had the issue that calling xmodmap here basically froze the whole
> session for a while, which was probably caused by that behaviour.
> Agreed. If those events are caused by something we can't fix, then this
> might turn out to be the best option though.

Now I'm thinking maybe the compression should happen in the keyboard module... ?
That wouldn't fix the xmodmap issue though.
Maybe we're seeing a N devices * M keys multiplication issue, i.e. it would be 
good to compress at both levels.

-- 
David Faure, fa...@kde.org, http://www.davidfaure.fr
Working on KDE Frameworks 5