be left to expire in approximately 60
> days.
>
> ** Changed in: ubuntu
> Status: Confirmed => Incomplete
>
--
Tim Wetzel
This e-mail may contain confidential or privileged information. If you
are not the intended recipient, please advise by return e-mail and
delete immediately
n.
>
> ** Changed in: gnome-settings-daemon (Ubuntu)
> Status: Confirmed => Won't Fix
>
> ** Changed in: gnome-shell (Ubuntu)
> Status: Confirmed => Won't Fix
>
> ** Changed in: mutter (Ubuntu)
> Status: Confirmed => Won't Fix
&
Two points
-Have not been able to find a combination of logind parameters that avoids this
issue.
-Have also found that this problem is not limited to HDMI connection. It has
also now appeared on a T480 in UltraDock using DP++ connection to external
display. Again, the external display is the pr
Shadrin, I tried that... removed the # from the start of that line so it was
set to ignore. It had no effect.
I notice that there is another parameter LidSwitchIgnoreInhibited. That is set
to yes.
What is the function of that parameter, do you know?
Thanks...
AND I CONCUR: Please correct this bug
New wrinkle: over the weekend on startup (from full shutdown), in dock, lid
down with HDMI monitor and external keyboard and mouse, got to the Ubuntu login
and put in the password. Was waiting for this suspend bug to appear. Instead:
got a Linux error as follows at the point where this bug typic
New wrinkle: today on startup (from full shutdown), in dock, lid down with HDMI
monitor and external keyboard and mouse, got to the Ubuntu login and put in the
password. Was waiting for this suspend bug to appear. Instead: got a Linux
error as follows at the point where this bug typically exhibi
Yes, this is still a problem. Please see post #5 above and /bugs/1897185 where
I posted earlier information. As noted by fchen, this started with Ubuntu
updates and has been a problem ever since, though I started seeing it months
ago.
PLEASE fix this.
Thanks.
--
You received this bug notificat
Just want to remind us that this was NOT AN ISSUE UNTIL after the
September 2020 Ubuntu 20.04 updates that included the updates to
20.04.1. Therefore I have trouble with dismissing it as a known,
unaddressed hardware issue. If so, why did it work fine prior to those
updates? No: there were several
See comment #5 above. Yes, the nVidia driver may appear to be a common
denominator BUT... I've seen the issue trigger apparently due to other
things loading as opposed to nVidia's third party driver, so it may not
be anything in the nVidia driver per se. The occurrences due to other
utilities (like
Agree that this is a serious issue. Like EAB, each of our setups remains
constant: same laptop, dock, display, etc. This issue continues to recur
probably 11 out of 12 startups when docked lid down. Notably, I have
almost never seen it when the laptop is running standalone (out of the
dock).
Note
On our systems, T480 and T570's, this issue continues to occur EVERY
STARTUP when the machine is run in the UltraDock, lid down using and
external HDMI display as primary. Sometimes it is possible to bump the
dock power again to restart it (and then it goes to the desktop WITHOUT
any password promp
Johan and also iMac, thank you...
I was trying to see whether this issue correlated with the type of cable
between the dock and the external display; but obviously not since we're seeing
it with both HDMI and DP.
I'm not suggesting that a particular item such as the Dropbox app,
Logitech USB dr
Johan, is the external monitor connected to the dock with an HDMI cable?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1841826
Title:
Going to sleep instead of logging in while lid closed & external
Update: looks like the return of this problem is being triggered by
Ubuntu Updater of Dec 17 give or take a few days. That update includes
AppIndicator/KStatusNotifierItem support for Gnome Shell, common files
for Gnome desktop apps, crash reporting, input device management and
event handling libra
Ubuntu 20.04.1 just started throwing this error this morning. What gives???
Looks like this was fixed 10 years ago?!?
This is now like the 7th or 8th bug that's recurred since the disastrous mid
September updates to 20.04! C'mon!
--
You received this bug notification because you are a member of
Three additional points:
-This occurs with ONE external HDMI monitor connected to the dock and running
as the primary display. Need not be multi-monitor. All cases I've seen involve
one external monitor.
-I put log information in the notes for 1897185 to show the events that
preceded the suspend
A few things that may help with this, these were noted under bug 1897185. In
looking at logs when this occurred (observed on ThinkPads including T440s,
T570, T480 all docked and running lid-down with external display, keyboard,
etc); this behavior occurred when:
-using a third-party nVidia drive
Another wrinkle since this week's kernel update in 20.04.1 (from
5.4.0.54.57 to 5.4.0.56.59: on every second or third startup in the
UltraDock and with the external HDMI display as primary (which is where
this suspend on login password problem occurs), the system now goes into
never-never land inst
Dimitri, I note your comment #106 about secureboot patches upstream. If
I recall correctly, a linux security update came down through Ubuntu
Updater about the same time or just prior to the LTS 20.04.1 updates in
mid September. A number of issues with LTS 20.04.1 appeared following
two "batches" of
Additional observation: I've tried using Ubuntu LTS 20.04 download
images from July and August, selecting the option to install third party
drivers. These images worked flawlessly at the end of the summer. But
since the mid-September updates, even these earlier iso's of Ubuntu LTS
20.04 Desktop fai
With reference to post #132 above: If this is relevant to this issue
I also am experiencing problems with switching drivers for the device on
my systems that uses (or can use) a Ubuntu third party driver.
Specifically nVidia for the GeForce 940MX. Changing between nVidia
driver versions (all wi
This bug remains, and exhibits with every startup in the T570's
UltraDock. Likewise, this bug has exhibited on every system here (all
ThinkPads) when in their respective UltraDocks. This includes a T480,
which is a current machine based on the i7-8xxx chipset.
--
You received this bug notificatio
Update: this is still acting up, even after the kernel update and Intel
microcode updates of Nov 11 and Nov 12 respectively. Given those
updates, I tested to see whether this bug is still there. Unfortunately,
it is.
This is a ThinkPad T570, docked, using external HDMI display (via the
dock) as pr
Daniel, of course. My point was that I've now seen multiple occurrences
where this suspend on login bug, as it continues to occur on a given
system, causes Ubuntu to become less and less stable over time.
Unfortunately that impact has become predictable at least on the
machines here. So to me, this
This bug is destabilizing the main Ubuntu system here again. Gnome shell has
begun to crash. Latest cold start once again went into suspend as soon as the
login password was entered. Lines immediately before suspending were:
Stopped target Main User Target
A connection to the bus can't be made
Er
Sorry; I thought my post #85 was obvious in being a response to post #84. But
to verify: the plymouth package pulled from proposed was
0.9.4git20200323-0ubuntu6.2
and still so far so good.
All "normal" Ubuntu 20.04.1 Updates were up-to-date prior to pulling this from
proposed.
Thanks,
Tim
--
Y
This may also help:
I'm testing the fix for bug 1872159 (spinning logo hang on startup). It seems
to be working.
So, since the rendering of the nVidia driver is superior to the x.org driver, I
switched for the generic x.org back to nVidia's latest 450 version for the
T570's GeForce 940MX. Well:
Brian and Daniel,
So far so good.
I applied this to 2 affected systems using the gui and selecting just the
plymouth related items from the proposed available modules. There were 5: 2
each in software and base; and a shared library in the software (first) section.
The problem had most reliably ex
Daniel, with reference to post 76 above, yes: all of my configurations
involved with this have one external HDMI display. The laptops run
docked, lid down, with the external display as primary. The dock also
provides external keyboard and mouse. I've seen it with external
displays from less than 19
Another system failed under 20.04.1: A T480 that hadn't been used for a
while, set up dual boot Ubuntu 20.04 and Win 10. Ubuntu had updates
waiting including the 20.04.1 updates from several weeks ago. As soon as
that installed and the system was restarted, malfunctions began. The
system was docked
So my main LTS 20.04.1 system just provided some Ubuntu Updates, mainly
the boot animation plymouth package. But it still shows in dpkg as
0.9.4git20200323 although it incremented to 6.1. Does this address this
issue? I'm new to all this, so trying to make sure I don't test the
wrong thing.
--
Yo
That's what I was afraid of. Guys: please address this. Isn't the whole
point of LTS that stuff like this isn't supposed to happen? All 4 of the
bugs I've been fighting for the past 6 weeks or so have hit LTS 20.04.1
*hard*. The initramfs, the spinning logo hang, then the suspend at login
password.
Brian, my systems pull from focal. I turned on the developer option and
looked at what's available: plymouth isn't there. According to dpkg, the
system still has the 9.4 version from 20200323 installed. Should 9.5 be
available; is it not there yet; or am I looking in the wrong place?
Thanks.
--
Y
Brian, thanks for the heads up and the links to the docs on how to
test... I'll look into this later today then and post back. Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872159
Title:
Bo
Daniel, this seems consistent: so long as I don't load the Dropbox app,
I haven't seen the suspend. I don't know if this is the cause but
regardless the Dropbox app may help in reproducing this issue? Thanks...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Daniel, thanks; looks like there IS something with the Dropbox app going on as
one triggers of this. I changed the Dropbox properties so that Dropbox does not
automatically start; turned off Dropbox sync; and turned off the Dropbox app.
Shut down the system. When I started the system, it did not
Looking through the logs...
Seeing "Suspending" from systemd-logind this morning.
The line immediately before (below) that is
dropbox: load fq extention
'/home/tim/.dropbox-dist/dropbox-lnx.x86_64-108.4.453/psutil._psutil_posi
The lines immediately after (above) the suspending line are (
Posted this detail upstream at Plymouth in hopes it may help:
So I did 3 things yesterday: I applied all Ubuntu Updates; turned the splash
screen back on; and reverted from the third-party nVidia drivers back to the
open source driver. Then rebooted. This was the first time in a month that I
was
Daniel, you're right: it just happened again. Suspended as soon as I put
in the login password. Uh- oh!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897185
Title:
Laptop docked with lid closed, go
NOTE that I'm not seeing this since today's fix for 1872159 (the spinning logo
splash hang on startup). Are these related? Something has changed; but I'm not
sure whether it's truly fixed?
Thanks...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I am seeing much better stability of the Ubuntu distro today. I am
working with a reinstallation from a 20.04.1 image from late August; I
loaded it about a week ago hoping to recover from the 4 bugs I've been
dealing with but still had problems. Today I ran Ubuntu Update AND went
back to the open s
Update as posted upstream at Plymouth:
Daniel, THANK YOU! I have applied Ubuntu Updates to the affected machines here,
and then turned the splash screen back on. Knock on wood, the issue isn't
happening any more.
Also: another bug is gone also, it seems: Ubuntu #1897185 regarding suspend
during
The fix for 1872159 (spinning logo hang on startup) has allowed me to
turn the splash screen back on; and this error is not visible. I do,
though, encourage completion of the fix for it since it rears its head
when the splash screens have to be disabled.
--
You received this bug notification beca
I noted this new comment:
"I am used to having such problems with Nvidia graphics is involved,
but this is not the case on this laptop. It has been happily running
18.04."
In my case, I'm seeing this on machines that have been running *LTS
20.04* just fine UNTIL the updates to 20.04.1 started
Daniel, please see also bug #1897185. Quite similar. And when I searched
for information on the suspend on login password problem, I also found
#1481442, 1589593, and 1626689 which *may* be related. I see this on
Thinkpad T570 in a mechanical dock with external HDMI display and
external USB keyboar
OK: I created a login at Plymouth and added comments to "bump" their bug:
Booting hangs when external monitors are connected
Also noted the seriousness of this and the question of whether it has
corrupted T440s BIOS.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks James. My configuration is different: the laptops in question are
in mechanical docks. The laptop remains closed (lid down); external
display is connected to the dock via HDMI, external keyboard and mouse
are also connected to the dock via USB dongle in the dock. So I can't
start them and th
Well, that answers something I've wondered: this DOES affect the T480
(full Thunderbolt) chipset. I've seen it on T570; I've seen it reported
on T470; and I've also seen it on T440s. Again, this is one of FOUR
serious bugs that I've seen pop up since the Ubuntu updates starting
around September 12
These bugs started with a Ubuntu update just prior to Sept 14 (see post
103 above). By the 14th, there were initramfs problems on startup and
the hang on spinning circle which forced hard power downs.
Then on Sept 24, more updates installed including updates to grub,
*nvidia drivers*, and some oth
Two additional observations on this bug:
-This bug is becoming more persistent on the second machine (the first one is
completely sidelined due to all this; an attempt to reload Ubuntu on it failed
due to bug 1871268).
-I looked back: this problem of going into suspend as soon as the login
passw
Sebastien, I'm new to Ubuntu so I may not be looking in the right
place... but I couldn't find much in the logs. There was no crash, no
error, just... nothing. Only option was a forced power down. I could
find the point where I restarted it in the logs, but nothing else seemed
remarkable. And that
I should add that, in researching old posts on these issues, I gather
that nVidia driver(s) have been a factor; so note that the last Ubuntu
Updater package prior to all this did also include an update to the
nVidia driver package.
--
You received this bug notification because you are a member of
I already used the daily image; and yes I got the (re)installation to
complete without crashing. BUT the freshly (re)installed Ubuntu system
remained unstable and therefore unusable due to other bugs that were
introduced or re-introduced by the two Ubuntu Updater packages pushed
out since mid-Septe
In my experience, the bug occurs when a ThinkPad is in its Ultra Dock
and is run, lid closed, using external display, keyboard, and mouse. Bug
#1888695 refers to a direct connection of an external monitor to the
laptop's own HDMI port. Thus the configuration is not the same. The
cause may be relate
Sorry to say that I tried to install from images from both May and June
of this year, obviously 20.04. Both failed with the same crash. And,
like you, I need nvidia and other specific drivers.
Even if you can get past the crash, other changes that have been made since
mid-September are wreaking h
This morning, this bug affected a second machine here. Updater ran on
Oct 1. This is the same machine that started having ACPI errors after
the boot hanging when docked with an external display (#1872159). These
problems seem to be interrelated: #1872159, 1835660, 1897185. And as
stability deterior
Prior bugs that were similar and may be related to this one include:
1481442
1589593
1626689
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897185
Title:
login triggers suspend after update
To mana
Note that this bug also affects efforts to install older images,
including 20.04 from May and June of this year: those installs crash
also with this same error. This matters, because the bugs introduced by
Updater changes since mid-September have made Ubuntu troublesome and
unstable. Bugs that have
This bug recurred with the last two 20.04 Updater packages, starting
mid-September. The initramfs upacking bug 1835660 recurred about the
same time. Turning off the Ubuntu splash screen seems to avoid the
problem, but when it doesn't (or until you realize that you have to make
that change); the spi
Continues to occur even once the bug 1871268 install crash has been
dealt with (installing from latest daily-live current image). So affects
even a fresh install. Seemed to appear in mid-September updates along
with recurrence of bug 1872159, the dreaded spinning Ubuntu logo hang on
startup. So a f
This bug continues to recur even after a fresh reinstallation of Ubuntu.
After working through the installation crash (bug 1871268) by using the
latest daily image; trying unsuccessfully to get rid of the still
recurring initramfs errors (bug 1835660); and disabling the splash
screen to avoid the d
Additional observations:
1. This bug is interacting with another: where the "short name" of the user
(the Home file name) rather than the full user name is showing up on the login
screen. Usually the short name shows up on this machine when it is docked. When
the laptop is being used by itself,
Public bug reported:
Ubuntu 20.04's software updater just applied quite a few updates
affecting grub and nvidia. The modules should show in the report just
submitted. Also, updates to initramfs had just installed a few days ago.
Kudos in that these updates fixed two login/startup issues: I'd been
63 matches
Mail list logo
