“CRITICAL: We failed, but the fail whale is dead. Sorry…” Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)After coming back from sleep, ubuntu's GUI restartedthe keyboard layout randomly turns off dead keys on boot“FAILED” message on startup, but services running?Nautilus-Share-Message: Called “net usershare info” but it failedWhat is causing (gnome-shell:3120): Clutter-CRITICAL **: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failedGLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed - asked to log in twiceUnable to end session/log out using lightdm (16.04)fail message upon boot up on kubuntu “failed to reset device”After upgrade from 16.04 LTS to 18.04 LTS, display manager fails apparently because of freedesktopIt takes very long for Ubuntu 18.04 to show login screen after a rebootWould Pango-Critical failed error might cause crash
What does it mean that physics no longer uses mechanical models to describe phenomena?
Maximum summed subsequences with non-adjacent items
As a beginner, should I get a Squier Strat with a SSS config or a HSS?
SF book about people trapped in a series of worlds they imagine
What is a fractional matching?
What was the first language to use conditional keywords?
If Windows 7 doesn't support WSL, then what does Linux subsystem option mean?
Crossing US/Canada Border for less than 24 hours
Is grep documentation about ignoring case wrong, since it doesn't ignore case in filenames?
What initially awakened the Balrog?
Denied boarding although I have proper visa and documentation. To whom should I make a complaint?
Performance gap between vector<bool> and array
How were pictures turned from film to a big picture in a picture frame before digital scanning?
Significance of Cersei's obsession with elephants?
Question about debouncing - delay of state change
Why do we need to use the builder design pattern when we can do the same thing with setters?
Is there any word for a place full of confusion?
Is a ledger board required if the side of my house is wood?
Do I really need to have a message in a novel to appeal to readers?
How often does castling occur in grandmaster games?
Can the Great Weapon Master feat's "Power Attack" apply to attacks from the Spiritual Weapon spell?
Is there hard evidence that the grant peer review system performs significantly better than random?
What would you call this weird metallic apparatus that allows you to lift people?
Morning, Afternoon, Night Kanji
“CRITICAL: We failed, but the fail whale is dead. Sorry…”
Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 23, 2019 at 00:00UTC (8:00pm US/Eastern)After coming back from sleep, ubuntu's GUI restartedthe keyboard layout randomly turns off dead keys on boot“FAILED” message on startup, but services running?Nautilus-Share-Message: Called “net usershare info” but it failedWhat is causing (gnome-shell:3120): Clutter-CRITICAL **: clutter_layout_manager_get_child_meta: assertion 'CLUTTER_IS_LAYOUT_MANAGER (manager)' failedGLib-CRITICAL: g_environ_setenv: assertion 'value != NULL' failed - asked to log in twiceUnable to end session/log out using lightdm (16.04)fail message upon boot up on kubuntu “failed to reset device”After upgrade from 16.04 LTS to 18.04 LTS, display manager fails apparently because of freedesktopIt takes very long for Ubuntu 18.04 to show login screen after a rebootWould Pango-Critical failed error might cause crash
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
When I started up my machine today I got some quite bizarre messages in my syslog:
...
Aug 17 18:58:15 Floral-Towel systemd[1349]: Startup finished in 266ms.
Aug 17 18:58:15 Floral-Towel systemd[1349]: Starting Default.
Aug 17 18:58:15 Floral-Towel systemd[1]: Started User Manager for UID 121.
Aug 17 18:58:15 Floral-Towel freshclam[782]: Empty script safebrowsing-43732.cdiff, need to download entire database
Aug 17 18:58:17 Floral-Towel gnome-session[1355]: gnome-session[1355]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 17 18:58:17 Floral-Towel gnome-session[1355]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 17 18:58:17 Floral-Towel gdm[1232]: Child process -1352 was already dead.
Aug 17 18:58:17 Floral-Towel systemd[1]: Stopping User Manager for UID 121...
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopped target Default.
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopping Default.
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopped target Basic System.
...
I included some of the other messages around that time just in case if they might be of help in some way. But to get to the point, who, or what, is "the fail whale"? And why is he/she/it dead? What is the meaning of all this? And what's it doing in my syslog?
I am running Ubuntu Gnome 15.04, with Gnome Shell, and Gnome 3.16.
OS Information:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.04
Release: 15.04
Codename: vivid
Package Information:
gnome-session:
Installed: 3.16.0-0ubuntu1~vivid1
Candidate: 3.16.0-0ubuntu1~vivid1
Version table:
*** 3.16.0-0ubuntu1~vivid1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
3.14.0-2ubuntu5 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages
3.14.0-2ubuntu4 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
3.14.0-2ubuntu4~vivid1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ vivid/main amd64 Packages
gnome startup syslog
add a comment |
When I started up my machine today I got some quite bizarre messages in my syslog:
...
Aug 17 18:58:15 Floral-Towel systemd[1349]: Startup finished in 266ms.
Aug 17 18:58:15 Floral-Towel systemd[1349]: Starting Default.
Aug 17 18:58:15 Floral-Towel systemd[1]: Started User Manager for UID 121.
Aug 17 18:58:15 Floral-Towel freshclam[782]: Empty script safebrowsing-43732.cdiff, need to download entire database
Aug 17 18:58:17 Floral-Towel gnome-session[1355]: gnome-session[1355]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 17 18:58:17 Floral-Towel gnome-session[1355]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 17 18:58:17 Floral-Towel gdm[1232]: Child process -1352 was already dead.
Aug 17 18:58:17 Floral-Towel systemd[1]: Stopping User Manager for UID 121...
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopped target Default.
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopping Default.
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopped target Basic System.
...
I included some of the other messages around that time just in case if they might be of help in some way. But to get to the point, who, or what, is "the fail whale"? And why is he/she/it dead? What is the meaning of all this? And what's it doing in my syslog?
I am running Ubuntu Gnome 15.04, with Gnome Shell, and Gnome 3.16.
OS Information:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.04
Release: 15.04
Codename: vivid
Package Information:
gnome-session:
Installed: 3.16.0-0ubuntu1~vivid1
Candidate: 3.16.0-0ubuntu1~vivid1
Version table:
*** 3.16.0-0ubuntu1~vivid1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
3.14.0-2ubuntu5 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages
3.14.0-2ubuntu4 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
3.14.0-2ubuntu4~vivid1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ vivid/main amd64 Packages
gnome startup syslog
add a comment |
When I started up my machine today I got some quite bizarre messages in my syslog:
...
Aug 17 18:58:15 Floral-Towel systemd[1349]: Startup finished in 266ms.
Aug 17 18:58:15 Floral-Towel systemd[1349]: Starting Default.
Aug 17 18:58:15 Floral-Towel systemd[1]: Started User Manager for UID 121.
Aug 17 18:58:15 Floral-Towel freshclam[782]: Empty script safebrowsing-43732.cdiff, need to download entire database
Aug 17 18:58:17 Floral-Towel gnome-session[1355]: gnome-session[1355]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 17 18:58:17 Floral-Towel gnome-session[1355]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 17 18:58:17 Floral-Towel gdm[1232]: Child process -1352 was already dead.
Aug 17 18:58:17 Floral-Towel systemd[1]: Stopping User Manager for UID 121...
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopped target Default.
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopping Default.
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopped target Basic System.
...
I included some of the other messages around that time just in case if they might be of help in some way. But to get to the point, who, or what, is "the fail whale"? And why is he/she/it dead? What is the meaning of all this? And what's it doing in my syslog?
I am running Ubuntu Gnome 15.04, with Gnome Shell, and Gnome 3.16.
OS Information:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.04
Release: 15.04
Codename: vivid
Package Information:
gnome-session:
Installed: 3.16.0-0ubuntu1~vivid1
Candidate: 3.16.0-0ubuntu1~vivid1
Version table:
*** 3.16.0-0ubuntu1~vivid1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
3.14.0-2ubuntu5 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages
3.14.0-2ubuntu4 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
3.14.0-2ubuntu4~vivid1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ vivid/main amd64 Packages
gnome startup syslog
When I started up my machine today I got some quite bizarre messages in my syslog:
...
Aug 17 18:58:15 Floral-Towel systemd[1349]: Startup finished in 266ms.
Aug 17 18:58:15 Floral-Towel systemd[1349]: Starting Default.
Aug 17 18:58:15 Floral-Towel systemd[1]: Started User Manager for UID 121.
Aug 17 18:58:15 Floral-Towel freshclam[782]: Empty script safebrowsing-43732.cdiff, need to download entire database
Aug 17 18:58:17 Floral-Towel gnome-session[1355]: gnome-session[1355]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 17 18:58:17 Floral-Towel gnome-session[1355]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Aug 17 18:58:17 Floral-Towel gdm[1232]: Child process -1352 was already dead.
Aug 17 18:58:17 Floral-Towel systemd[1]: Stopping User Manager for UID 121...
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopped target Default.
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopping Default.
Aug 17 18:58:17 Floral-Towel systemd[1349]: Stopped target Basic System.
...
I included some of the other messages around that time just in case if they might be of help in some way. But to get to the point, who, or what, is "the fail whale"? And why is he/she/it dead? What is the meaning of all this? And what's it doing in my syslog?
I am running Ubuntu Gnome 15.04, with Gnome Shell, and Gnome 3.16.
OS Information:
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 15.04
Release: 15.04
Codename: vivid
Package Information:
gnome-session:
Installed: 3.16.0-0ubuntu1~vivid1
Candidate: 3.16.0-0ubuntu1~vivid1
Version table:
*** 3.16.0-0ubuntu1~vivid1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
3.14.0-2ubuntu5 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid-updates/main amd64 Packages
3.14.0-2ubuntu4 0
500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
3.14.0-2ubuntu4~vivid1 0
500 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ vivid/main amd64 Packages
gnome startup syslog
gnome startup syslog
edited Aug 18 '15 at 16:24
Braiam
52.7k20138225
52.7k20138225
asked Aug 17 '15 at 19:51
user364819
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
In this case the "fail whale" is an error message logged by GNOME if something went wrong. It's named after a illustration by Yiying Lu used by Twitter to display errors.
If it is dead it means that there's not enough of GNOME running to display the error.
The link to the illustration by Yiying Lu does not work anymore.
– Hans Deragon
Mar 24 at 23:17
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f662678%2fcritical-we-failed-but-the-fail-whale-is-dead-sorry%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
In this case the "fail whale" is an error message logged by GNOME if something went wrong. It's named after a illustration by Yiying Lu used by Twitter to display errors.
If it is dead it means that there's not enough of GNOME running to display the error.
The link to the illustration by Yiying Lu does not work anymore.
– Hans Deragon
Mar 24 at 23:17
add a comment |
In this case the "fail whale" is an error message logged by GNOME if something went wrong. It's named after a illustration by Yiying Lu used by Twitter to display errors.
If it is dead it means that there's not enough of GNOME running to display the error.
The link to the illustration by Yiying Lu does not work anymore.
– Hans Deragon
Mar 24 at 23:17
add a comment |
In this case the "fail whale" is an error message logged by GNOME if something went wrong. It's named after a illustration by Yiying Lu used by Twitter to display errors.
If it is dead it means that there's not enough of GNOME running to display the error.
In this case the "fail whale" is an error message logged by GNOME if something went wrong. It's named after a illustration by Yiying Lu used by Twitter to display errors.
If it is dead it means that there's not enough of GNOME running to display the error.
edited 19 mins ago
NorbiPeti
235
235
answered Aug 17 '15 at 20:17
Florian DieschFlorian Diesch
66.1k16168183
66.1k16168183
The link to the illustration by Yiying Lu does not work anymore.
– Hans Deragon
Mar 24 at 23:17
add a comment |
The link to the illustration by Yiying Lu does not work anymore.
– Hans Deragon
Mar 24 at 23:17
The link to the illustration by Yiying Lu does not work anymore.
– Hans Deragon
Mar 24 at 23:17
The link to the illustration by Yiying Lu does not work anymore.
– Hans Deragon
Mar 24 at 23:17
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f662678%2fcritical-we-failed-but-the-fail-whale-is-dead-sorry%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown