Bug 438313 - Wayland: Apps launcher is one launch late
Summary: Wayland: Apps launcher is one launch late
Status: RESOLVED FIXED
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (show other bugs)
Version: unspecified
Platform: Neon Linux
: VHI normal
Target Milestone: ---
Assignee: Aleix Pol
URL:
Keywords: regression, wayland
: 438532 438668 438686 438797 438870 439035 439037 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-06-09 09:28 UTC by Edward Oubrayrie
Modified: 2021-06-23 17:37 UTC (History)
25 users (show)

See Also:
Latest Commit: https://invent.kde.org/frameworks/kio/-/commit/3bc92c23dd3456bb18efd44968fabf32dd9c3402
Version Fixed In: 5.83
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Edward Oubrayrie 2021-06-09 09:28:37 UTC 
STEPS TO REPRODUCE
1. Launch a KDE App with launcher or KRunner. eg Dolphin
2. Launch another app. eg Kate
3. and so on. eg launch Okular

OBSERVED RESULT
1. Dolphin does not launch
2. App#1 ie Dolphin, launches (instead of Kate)
3. App#2 ie Kate opens (instead of Okular)


EXPECTED RESULT
Correct app launches on time


SOFTWARE/OS VERSIONS

Linux/KDE Plasma: KDE Neon Testing (based on Ubuntu focal 20.04)
KDE Plasma Version: 5.22.0 (5.22.0+p20.04+tstable+git20210608.1257-0)
KDE Frameworks Version: 5.82.0+p20.04+tunstable+git20210608.0115-0
                       (kInfoCenter say 5.83.0 for some reason)
Qt Version: 5.15.2+p20.04+tunstable+git20210602.0956-0
            (kInfoCenter says 5.15.3 for some reason)
KDE Apps: 21.04.1+p20.04+tstable+git20210608.0108-0

ADDITIONAL INFORMATION

This happens in both:
* the default App Launcher(the new Kickoff named SimpleMenu I think?) and the
* KRunner

It does *not* happen with command-line, even with dbus-launcher / kinit5
It does not happen with all apps, but for sure it does with the kde/wayland ones.

The app is not just hidden, I see eg gwenview/dolphin doing their startup work when I launch the next app.

Works normally on Xorg.
Comment 1 Nate Graham 2021-06-09 22:29:00 UTC 
How long are you waiting? Is it possible that the launch feedback animation not playing is making you think that nothing happened, when in fact it was just being a bit slow?
Comment 2 Edward Oubrayrie 2021-06-10 10:24:05 UTC 
The funny thing is, I am waiting *forever* until I decide to launch something else. It's a FIFO queue of length =1, some component in the launch chain is holding exactly 1 item hostage
Comment 4 Janet Blackquill 2021-06-10 16:59:14 UTC 
Can reproduce. This issue also breaks a lot of other places as well for me, e.g. launching an app to open a URL.
Comment 5 Nate Graham 2021-06-10 17:14:07 UTC 
Aleix, can you investigate?
Comment 6 Nate Graham 2021-06-12 04:53:50 UTC 
Fixed by Aleix Pol Gonzalez with https://invent.kde.org/frameworks/kio/-/commit/3bc92c23dd3456bb18efd44968fabf32dd9c3402
Comment 7 hellofriend 2021-06-15 21:11:26 UTC 
I'm on Wayland with KDE Framework 5.83 and the problem remains.
Comment 8 David Edmundson 2021-06-15 21:14:08 UTC 
Can you confirm the last part of 5.83.X 

(or better yet apt-get source it and look for that patch being applied)

The tarball was made, then released to distros, then respun and released again before the final release. Maybe something has got missed off.
Comment 9 hellofriend 2021-06-15 21:23:18 UTC 
(In reply to David Edmundson from comment #8)
> Can you confirm the last part of 5.83.X 
> 
> (or better yet apt-get source it and look for that patch being applied)
> 
> The tarball was made, then released to distros, then respun and released
> again before the final release. Maybe something has got missed off.

My System Information says this:
Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-55-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics
Memory: 11,1 GiB of RAM
Graphics Processor: AMD RENOIR

apt list --installed says this
plasma-framework/focal,now 5.83.0-0xneon+20.04+focal+release+build36 amd64 [installed,automatic]
Comment 10 hellofriend 2021-06-15 21:26:15 UTC 
(In reply to hellofriend from comment #9)
> (In reply to David Edmundson from comment #8)
> > Can you confirm the last part of 5.83.X 
> > 
> > (or better yet apt-get source it and look for that patch being applied)
> > 
> > The tarball was made, then released to distros, then respun and released
> > again before the final release. Maybe something has got missed off.
> 
> My System Information says this:
> Operating System: KDE neon 5.22
> KDE Plasma Version: 5.22.1
> KDE Frameworks Version: 5.83.0
> Qt Version: 5.15.3
> Kernel Version: 5.8.0-55-generic (64-bit)
> Graphics Platform: Wayland
> Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics
> Memory: 11,1 GiB of RAM
> Graphics Processor: AMD RENOIR
> 
> apt list --installed says this
> plasma-framework/focal,now 5.83.0-0xneon+20.04+focal+release+build36 amd64
> [installed,automatic]

apt-get source plasma-framework
Reading package lists... Done
NOTICE: 'plasma-framework' packaging is maintained in the 'Git' version control system at:
https://invent.kde.org/neon/kde/plasma-framework.git
Please use:
git clone https://invent.kde.org/neon/kde/plasma-framework.git
to retrieve the latest (possibly unreleased) updates to the package.
Need to get 3.160 kB of source archives.
Get:1 http://archive.neon.kde.org/user focal/main plasma-framework 5.83.0-0xneon+20.04+focal+release+build36 (diff) [13,8 kB]
Get:2 http://archive.neon.kde.org/user focal/main plasma-framework 5.83.0-0xneon+20.04+focal+release+build36 (dsc) [3.135 B]
Get:3 http://archive.neon.kde.org/user focal/main plasma-framework 5.83.0-0xneon+20.04+focal+release+build36 (tar) [3.143 kB]
Fetched 3.160 kB in 1s (3.311 kB/s)         
dpkg-source: info: extracting plasma-framework in plasma-framework-5.83.0
dpkg-source: info: unpacking plasma-framework_5.83.0.orig.tar.xz
dpkg-source: info: unpacking plasma-framework_5.83.0-0xneon+20.04+focal+release+build36.debian.tar.x
Comment 11 Nate Graham 2021-06-15 21:42:24 UTC 
*** Bug 438668 has been marked as a duplicate of this bug. ***
Comment 12 Nate Graham 2021-06-15 21:43:19 UTC 
It's working for me on git master, so I wonder if the commit didn't make it into the tarball.
Comment 13 hellofriend 2021-06-15 21:57:14 UTC 
(In reply to Nate Graham from comment #12)
> It's working for me on git master, so I wonder if the commit didn't make it
> into the tarball.

Maybe the package is made from a previous commit.
I hope the fix will be released asap!
Comment 14 Nate Graham 2021-06-15 22:05:38 UTC 
*** Bug 438686 has been marked as a duplicate of this bug. ***
Comment 15 hellofriend 2021-06-15 22:28:54 UTC 
*** Bug 438532 has been marked as a duplicate of this bug. ***
Comment 16 kelnio@yahoo.com 2021-06-16 02:01:11 UTC 
(In reply to hellofriend from comment #13)
> (In reply to Nate Graham from comment #12)
> > It's working for me on git master, so I wonder if the commit didn't make it
> > into the tarball.
> 
> Maybe the package is made from a previous commit.
> I hope the fix will be released asap!

I hope so too. I wouldn't consider this bug critical, as it doesn't cause crashes and data loss. However, it is one of the most annoying non-critical bugs I've encountered so far. Having the wrong application open when you click on an application icon is frustrating!
Comment 17 Fabian Vogt 2021-06-16 09:34:48 UTC 
I can confirm that the referenced commit is in the official kio-5.83.0 tarball.
Considering that all reports about this appear to be from users of a specific distribution, my guess is that this distro ships an outdated tarball.
Comment 18 David Edmundson 2021-06-16 09:44:41 UTC 
Can someone on Neon upgrade and confirm if this is still a problem?
Comment 19 hellofriend 2021-06-16 09:46:52 UTC 
(In reply to David Edmundson from comment #18)
> Can someone on Neon upgrade and confirm if this is still a problem?

sudo pkcon update
Getting updates               [=========================]         
Finished                      [=========================]         
No packages require updating to newer versions.

Operating System: KDE neon 5.22
KDE Plasma Version: 5.22.1
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.3
Kernel Version: 5.8.0-55-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics
Memory: 11,1 GiB of RAM
Graphics Processor: AMD RENOIR
Comment 20 hellofriend 2021-06-16 09:47:16 UTC 
(In reply to hellofriend from comment #19)
> (In reply to David Edmundson from comment #18)
> > Can someone on Neon upgrade and confirm if this is still a problem?
> 
> sudo pkcon update
> Getting updates               [=========================]         
> Finished                      [=========================]         
> No packages require updating to newer versions.
> 
> Operating System: KDE neon 5.22
> KDE Plasma Version: 5.22.1
> KDE Frameworks Version: 5.83.0
> Qt Version: 5.15.3
> Kernel Version: 5.8.0-55-generic (64-bit)
> Graphics Platform: Wayland
> Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics
> Memory: 11,1 GiB of RAM
> Graphics Processor: AMD RENOIR

Stll a problem
Comment 21 David Edmundson 2021-06-16 10:20:22 UTC 
and you restarted plasmashell after upgrading?
Comment 22 hellofriend 2021-06-16 10:48:35 UTC 
(In reply to David Edmundson from comment #21)
> and you restarted plasmashell after upgrading?

Obviously
Comment 23 hellofriend 2021-06-16 10:50:28 UTC 
I have notice that since yesterday evening I have the updates available icon on system tray, but when I open discover or launch pkcon update, it says no update available
Comment 24 hellofriend 2021-06-16 10:55:44 UTC 
On http://archive.neon.kde.org/user the latest version of plasma-framework is this:
plasma-framework_5.83.0-0xneon+20.04+focal+release+build36_amd64.deb

Uploaded on 2021-06-11
Comment 25 kelnio@yahoo.com 2021-06-16 19:18:51 UTC 
(In reply to hellofriend from comment #23)
> I have notice that since yesterday evening I have the updates available icon
> on system tray, but when I open discover or launch pkcon update, it says no
> update available

That's a new bug that was introduced in 5.22.1. A bug report has already been filed.
Comment 26 kelnio@yahoo.com 2021-06-16 19:29:30 UTC 
(In reply to David Edmundson from comment #18)
> Can someone on Neon upgrade and confirm if this is still a problem?

I just checked. No new Plasma related packages are available for Neon. My machine is up to date, I did a reboot, and this is still an issue.
Comment 27 David Edmundson 2021-06-17 11:28:57 UTC 
*** Bug 438797 has been marked as a duplicate of this bug. ***
Comment 28 David Edmundson 2021-06-17 11:31:38 UTC 
Can I confirm everyone here is running "Neon Testing" ?
Comment 29 kelnio@yahoo.com 2021-06-17 12:10:18 UTC 
(In reply to David Edmundson from comment #28)
> Can I confirm everyone here is running "Neon Testing" ?

No, I'm running "Neon User."
Comment 30 hellofriend 2021-06-17 12:57:18 UTC 
(In reply to David Edmundson from comment #28)
> Can I confirm everyone here is running "Neon Testing" ?

I'm also running Neon User
Comment 31 MK 2021-06-17 13:00:55 UTC 
(In reply to David Edmundson from comment #28)
> Can I confirm everyone here is running "Neon Testing" ?

Nope, I'm on user
Comment 32 kelnio@yahoo.com 2021-06-19 06:25:13 UTC 
Is there any update as to when this will be fixed for Neon User Edition?
Comment 33 Paul Worrall 2021-06-19 15:20:38 UTC 
(In reply to kelnio@yahoo.com from comment #32)
> Is there any update as to when this will be fixed for Neon User Edition?

It's fixed in Neon Testing.  Neon User is releasing Plasma 5.22.2 next Tuesday (22 Jun)
Comment 34 kelnio@yahoo.com 2021-06-20 00:47:53 UTC 
(In reply to Paul Worrall from comment #33)
> (In reply to kelnio@yahoo.com from comment #32)
> > Is there any update as to when this will be fixed for Neon User Edition?
> 
> It's fixed in Neon Testing.  Neon User is releasing Plasma 5.22.2 next
> Tuesday (22 Jun)

Will it be incorporated into Plasma 5.22.2 for Neon User? The reason I'm concerned is because it seems that some things that get marked fixed and are in /dev/unstable or /testing don't necessarily make it to /user (like the Maliit keyboard)..
Comment 35 Nate Graham 2021-06-22 03:24:57 UTC 
*** Bug 438870 has been marked as a duplicate of this bug. ***
Comment 36 wulle-h 2021-06-23 12:25:03 UTC 
(In reply to kelnio@yahoo.com from comment #34)
> Will it be incorporated into Plasma 5.22.2 for Neon User? 

Unfortunately it was not. I updated to 5.22.2 today and the problem still occurs
Comment 37 Antonio Rojas 2021-06-23 12:30:05 UTC 
*** Bug 439035 has been marked as a duplicate of this bug. ***
Comment 38 samvo 2021-06-23 14:10:25 UTC 
I confirm this bug in 5.22.2
Comment 39 David Edmundson 2021-06-23 14:19:32 UTC 
We can't reproduce locally, and we tried with a clean VM and couldn't get anything. 

So we are going to need someone who can reproduce to really help out here.

Step one:
Lets get a log with QT_LOGGING_RULES=*.debug=true  and then opening an application

If someone can give steps from a clean image it would also help.
Comment 40 Fabian Vogt 2021-06-23 14:21:25 UTC 
(In reply to David Edmundson from comment #39)
> We can't reproduce locally, and we tried with a clean VM and couldn't get
> anything. 
> 
> So we are going to need someone who can reproduce to really help out here.
> 
> Step one:
> Lets get a log with QT_LOGGING_RULES=*.debug=true  and then opening an
> application
> 
> If someone can give steps from a clean image it would also help.

Was my analysis in comment 17 checked?
Comment 41 hellofriend 2021-06-23 14:22:18 UTC 
(In reply to David Edmundson from comment #39)
> We can't reproduce locally, and we tried with a clean VM and couldn't get
> anything. 
> 
> So we are going to need someone who can reproduce to really help out here.
> 
> Step one:
> Lets get a log with QT_LOGGING_RULES=*.debug=true  and then opening an
> application
> 
> If someone can give steps from a clean image it would also help.

You released only Plasma 5.22.2 and not released Plasma Framework 5.84 (where the fix is present, tried in Neon Testing)
Comment 42 David Edmundson 2021-06-23 14:22:29 UTC 
*** Bug 439037 has been marked as a duplicate of this bug. ***
Comment 43 Rik Mills 2021-06-23 14:42:00 UTC 
(In reply to David Edmundson from comment #8)
> Can you confirm the last part of 5.83.X 
> 
> (or better yet apt-get source it and look for that patch being applied)
> 
> The tarball was made, then released to distros, then respun and released
> again before the final release. Maybe something has got missed off.

It appears that the 5.83 tarball used for the Neon build:

https://archive.neon.kde.org/user/pool/main/k/kio/kio_5.83.0.orig.tar.xz

matches the hashes of the initial spin of the kio tar, and not the respun

This correlates with the date of the build job, which was before the respin:

https://build.neon.kde.org/view/1%20release%20%E2%9B%B0/job/focal_release_kde_kio/41/

So it appears that Neon tar and build is missing:

https://invent.kde.org/frameworks/kio/-/commit/3bc92c23dd3456bb18efd44968fabf32dd9c3402

which I can confirm by doing an manual diff between the Neon repo tar and the release tar from the download sftp
Comment 44 Rik Mills 2021-06-23 15:32:22 UTC 
*** Bug 439037 has been marked as a duplicate of this bug. ***
Comment 45 Rik Mills 2021-06-23 15:34:40 UTC 
A new Neon build of kio 5.83.0 with the fix added is currently under way
Comment 46 Jeffrey Bouter 2021-06-23 17:04:53 UTC 
Seems as though this issue has been resolved indeed. I can no longer reproduce it.
Comment 47 Rik Mills 2021-06-23 17:15:05 UTC 
Kio packages with the fix included should now be in the User Edition repo.
Comment 48 geisserml 2021-06-23 17:37:49 UTC 
Thanks! It now works correctly ;)