Bug #10842

GNOME Shell sometimes disables the Classic mode extensions

Added by intrigeri 2016-01-03 16:11:08 . Updated 2016-01-27 13:33:26 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2016-01-03
Due date:
% Done:

100%

Feature Branch:
bugfix/update-gnome-shell-extensions-list
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

I’ve seen it once (after at least one hour of letting a Tails system running), anonym has seen something similar on Bug #9012#note-16, and I suspect this problem might share a root cause or two with Bug #10807.

I think it happens too rarely and randomly to be a credible 2.0 release blocker, but I’ll at least give it a good try (and document on the known issues page how to bring the desktop back to its expected state).


Subtasks


History

#1 Updated by intrigeri 2016-01-03 16:21:14

  • Status changed from Confirmed to In Progress

#2 Updated by intrigeri 2016-01-03 16:48:23

  • Subject changed from GNOME Shell sometimes leaves Classic mode to GNOME Shell sometimes disables the Classic mode extensions

To clarify: when I saw this problem, the top bar was always light gray, so GNOME Shell didn’t really fully leave classic mode, it “just” disabled 2 extensions (apps-menu and window-list). Same when anonym saw it (Bug #9012#note-16). Retitling accordingly.

#3 Updated by intrigeri 2016-01-03 19:59:07

  • Assignee changed from intrigeri to anonym
  • % Done changed from 0 to 10
  • QA Check set to Ready for QA
  • Feature Branch set to bugfix/update-gnome-shell-extensions-list

Let’s see if that’s enough.

#4 Updated by anonym 2016-01-05 19:17:53

  • Status changed from In Progress to Fix committed
  • % Done changed from 10 to 100

Applied in changeset commit:b99b83cb4e91297240720844f9d575b1238ae863.

#5 Updated by anonym 2016-01-05 19:22:02

  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

intrigeri, I couldn’t reproduce the bug I told you about (clicking the GNOME Application menu button doesn’t open the menu until I opened the activities overlay) so I’m writing it off as a coincidence or whatever. So “no regressions”. Any way, let’s reopen this bug if your branch indeed didn’t fix the problem.

#6 Updated by anonym 2016-01-27 13:33:26

  • Status changed from Fix committed to Resolved