Bug 442228

Summary:	Latte-dock causes Microsoft Edge to crash
Product:	[Unmaintained] lattedock	Reporter:	Pango Gillespi <pango>
Component:	application	Assignee:	Michail Vourlakos <mvourlakos>
Status:	RESOLVED WORKSFORME
Severity:	grave	CC:	aleksejs.baksa
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Pango Gillespi 2021-09-09 14:30:03 UTC

SUMMARY

When latte-dock is running with an active latte-tasks widget, Microsoft Edge is unable to start. Quitting Latte allows the browser to run normally, but if Latte is started while Edge is running, the browser immediately crashes.

This behavior is observed on Ubuntu (latte-dock 0.10.0), Arch (latte-dock 0.10.1), and Manjaro (latte-dock 0.10.1) with Microsoft Edge - both Dev (95.0.997.1) and Beta (94.0.992.14).

STEPS TO REPRODUCE

1. Run Latte-Dock
2. Open MS Edge

Alternatively,
1. With latte-dock closed, run MS Edge
2. With Edge open, run latte-dock

OBSERVED RESULT
In both cases, MS Edge immediately crashes.

EXPECTED RESULT
Both Edge and Latte can run at the same time.

SOFTWARE/OS VERSIONS

KDE Plasma Version: 5.22.5 (Arch/Manjaro) AND 5.22.4 (Ubuntu)
KDE Frameworks Version: 5.85.0
Qt Version: 5.15.2
Latte-dock: 0.10.1 (Arch/Manjaro) AND 0.10.0 (Ubuntu)
MS Edge: 94.0.992.14 AND 95.0.997.1

ADDITIONAL INFORMATION

Granted, this is likely an issue in MS-Edge, but I'm hoping a change to Latte can address this incompatibility since this project is more likely to process a bug specific to Edge's interaction with Latte than Microsoft is.

MS Edge dump:

Gtk-Message: 10:28:25.803: Failed to load module "appmenu-gtk-module"
[0909/102825.997282:ERROR:elf_dynamic_array_reader.h(61)] tag not found
[0909/102825.997442:ERROR:elf_dynamic_array_reader.h(61)] tag not found
[0909/102825.997709:ERROR:elf_dynamic_array_reader.h(61)] tag not found
[0909/102825.999107:WARNING:minidump_to_upload_parameters.cc(36)] duplicate key guid, discarding value a3364902609e446fad2cb5a2d3099a59
[0909/102826.579041:WARNING:minidump_to_upload_parameters.cc(36)] duplicate key guid, discarding value a3364902609e446fad2cb5a2d3099a59
[1486119:1486131:0909/102827.863451:ERROR:ssl_client_socket_impl.cc(1136)] handshake failed; returned -1, SSL error code 1, net_error -3
[1486118:1486118:0100/000000.804960:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
fish: Job 1, 'microsoft-edge-beta' terminated by signal SIGTRAP (Trace or breakpoint trap)

Comment 1 Michail Vourlakos 2021-09-09 15:05:19 UTC

1. https://userbase.kde.org/LatteDock/HowToReportCrashes
2. If you close Latte and you use a plasma panel with a plasma taskmanager isnt plasmashell crashing also?

Comment 2 Pango Gillespi 2021-09-09 15:19:08 UTC

When a latte-tasks widget is added to a standard plasma panel (with no other widgets), Edge is able to run normally. So the issue must be with some other part of latte-dock, not the latte-tasks widget specifically.

a trace of latte-dock doesn't produce any useful information as it's edge that crashes, not latte-dock.

Comment 3 Michail Vourlakos 2021-09-09 17:23:55 UTC

Are you using layte default layout?

Comment 4 Pango Gillespi 2021-09-09 19:20:08 UTC

I normally don't use the default layout, but for troubleshooting on this I did test with the default layout and that has the same issue.

Comment 5 Pango Gillespi 2021-09-10 22:14:32 UTC

informational only: today's Edge-dev release (95.0.1000.0-1) continues to have the same problem

Comment 6 abaksa 2021-09-19 06:01:33 UTC

I found out MS Edge conflicts with various top-edge snapped panels.
Standard KDE maia panel snapped to top edge also causing Edge is unable to start.
Moving panel to side edge prevents this from happening.

Comment 7 Bug Janitor Service 2021-10-04 04:35:58 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 8 Bug Janitor Service 2021-10-19 04:35:51 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!