Bug #7890

Tails Jessie displays "Oh no! Something had gone wrong" instead of the Greeter

Added by alant 2014-09-13 02:51:10 . Updated 2020-04-15 06:05:39 .

Status:
Resolved
Priority:
High
Assignee:
Category:
Target version:
Tails_2.0
Start date:
2014-09-13
Due date:
% Done:

100%

Feature Branch:
feature/jessie
Type of work:
Research
Blueprint:

Starter:
Affected tool:
Welcome Screen
Deliverable for:

Description

A tails jessie build from bc874db on Sept 12, 2014 displays “Oh no! Something had gone wrong” instead of the greeter.

There is a line Fails to give slave programs access to the display. Trying to proceed. in gdm logs.

The same happens if I disable tails-greeter by choosing session-name=gdm-shell in /etc/gdm3/greeter.dconf-defaults and restart gdm.

Subtasks

History

#1 Updated by sajolida 2014-09-13 03:37:57

  • related to Bug #7323: Wheezy's GNOME crashes randomly after Greeter login added

#2 Updated by sajolida 2014-09-13 03:38:23

This error message is the same as in Bug #7323.

#3 Updated by BitingBird 2014-09-13 04:36:49

  • related to deleted (Bug #7323: Wheezy's GNOME crashes randomly after Greeter login)

#4 Updated by BitingBird 2014-09-13 04:36:53

  • is duplicate of Bug #7323: Wheezy's GNOME crashes randomly after Greeter login added

#5 Updated by sajolida 2014-09-13 06:20:40

  • Status changed from New to Resolved
  • Target version deleted (Tails_2.0)
  • Type of work changed from Research to Documentation

Sorry, I posted a comment on the wrong ticket!

#6 Updated by intrigeri 2014-09-13 08:17:47

  • Category set to 165
  • Status changed from Resolved to Confirmed
  • Target version set to Tails_2.0
  • Type of work changed from Documentation to Research

#7 Updated by intrigeri 2014-09-13 08:18:03

  • has duplicate deleted (Bug #7323: Wheezy's GNOME crashes randomly after Greeter login)

#8 Updated by intrigeri 2014-09-13 08:20:28

  • Subject changed from Tails jessie displays "Oh no! Something had gone wrong" instead of the greeter to Tails Jessie displays "Oh no! Something had gone wrong" instead of the Greeter
  • Assignee set to alant

The (very generic) error message is the same, but the root cause isn’t: Bug #7323 occurs rarely when loading the regular GNOME session (on Wheezy), while this one occurs everytime when loading the Greeter’s GNOME session (on Jessie). The fix will likely be entirely different.

#9 Updated by intrigeri 2014-09-13 08:21:02

  • Priority changed from Normal to High
  • Parent task set to Feature #7561

#10 Updated by alant 2014-09-13 10:10:27

The log line Fails to give slave programs access to the display. Trynig to proceed. also appears on a regular debian jessie and doesn’t prevent GDM to work.

It seems that the Something had gone wrong message appears if a component fails to load. Unfortulately even when enabling GDM3 debug logging in /etc/gdm3/daemon.conf I find no error.

#11 Updated by alant 2014-09-13 11:44:26

Same problem with an iso built from commit b68d98e. I’m giving up for today.

#12 Updated by alant 2014-09-14 06:02:42

There seems to be a problem with gnome-session not launching the required components.

GDM process tree in a working jessie system:

        |-gdm3-+-Xorg---2*[{Xorg}]
        |      |-gdm-session-wor-+-gnome-session-+-gnome-settings--+-{dconf worker}
        |      |                 |               |                 |-{gdbus}
        |      |                 |               |                 |-{gmain}
        |      |                 |               |                 `-{pool}
        |      |                 |               |-metacity-+-{dconf worker}
        |      |                 |               |          `-{gdbus}
        |      |                 |               |-tails-greeter---python---{gdbus}
        |      |                 |               |-{dconf worker}
        |      |                 |               |-{gdbus}
        |      |                 |               `-{gmain}
        |      |                 |-{gdbus}
        |      |                 `-{gmain}
        |      |-{gdbus}
        |      |-{gdm SIGUSR1 cat}
        |      `-{gmain}

GDM process tree on an tails ISO:

        |-gdm3-+-Xorg
        |      |-gdm-session-wor-+-gnome-session
        |      |                 |-{gdbus}
        |      |                 `-{gmain}
        |      |-{gdbus}
        |      |-{gdm SIGUSR1 cat}
        |      `-{gmain}

#13 Updated by alant 2014-09-14 07:03:47

  • Status changed from Confirmed to In Progress
  • % Done changed from 0 to 20
  • Feature Branch set to feature/jessie

The logs differ at “gnome-session-is-accelerated: llvmpipe detected” on the working system vs failure to detect 3D acceleration on the failing system. Installing libgl1-mesa-dri solves the issue. On a normal jessie system, this package is pulled by xorg. As I see no reason not to install xorg I added it to config/chroot_local-packageslists/tails-common.list.

#14 Updated by alant 2014-09-14 08:41:30

  • Status changed from In Progress to Resolved
  • % Done changed from 20 to 100

#15 Updated by alant 2014-09-14 08:46:11

  • Assignee deleted (alant)

#16 Updated by intrigeri 2014-09-14 21:37:59

alant wrote:
> Installing libgl1-mesa-dri solves the issue.

Nice catch!

> On a normal jessie system, this package is pulled by xorg. As I see no reason not to install xorg I added it to config/chroot_local-packageslists/tails-common.list.

Agreed. Note that this pulls in a lot of additional packages. We install the vast majority of them on Tails/Wheezy anyway, and I’m pretty sure we’ll run into other issues if we don’t install e.g. xinit and x11-session-utils, so indeed this seems to be the way to go.

#17 Updated by intrigeri 2020-04-15 06:05:39

  • Affected tool changed from Greeter to Welcome Screen