Bug 1822651

Summary:	dash-to-dock not working after
Product:	Red Hat Enterprise Linux 7	Reporter:	Pablo Greco <pablo>
Component:	gnome-shell-extensions	Assignee:	Florian Müllner <fmuellner>
Status:	CLOSED DUPLICATE	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.8	CC:	jadahl, mboisver, tpelka
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-05-26 15:06:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pablo Greco 2020-04-09 14:19:41 UTC

Description of problem:
After bug 1720286, dash-to-dock no longer works in classic mode, it shows a warning in the extension list.

Version-Release number of selected component (if applicable):
gnome-shell-extensions-3.28.1-11


How reproducible:
Always


Steps to Reproduce:
1. Install gnome-shell-extensions-dash-to-doc
2.
3.

Actual results:
Nothing


Expected results:
Working dash-to-dock

Additional info:
Looks like this patch is what solved this problem upstream https://github.com/micheleg/dash-to-dock/commit/5658b5c2217ab3b7a036d51b62b357ea99e8fedc

Comment 2 Pablo Greco 2020-04-09 14:22:23 UTC

This seems to be the same as bug 1805929, but for 7

Comment 3 Tomas Pelka 2020-04-09 14:32:27 UTC

Overview in gnome-classic was changed in order to look and behave more like gnome2. Can you please check non-classic session?

Comment 4 Pablo Greco 2020-04-09 15:05:28 UTC

(In reply to Tomas Pelka from comment #3)
> Overview in gnome-classic was changed in order to look and behave more like
> gnome2. Can you please check non-classic session?

Yes, it works on non-classic mode.
Either way, I've already fixed if for myself by reverting part of bug 1720286

Comment 5 Florian Müllner 2020-05-26 15:06:26 UTC


*** This bug has been marked as a duplicate of bug 1805920 ***