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 Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1841826
Title:
Going to sleep instead of logging
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
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
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:
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
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 Desktop
Packages, wh
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 Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1897185
Title:
Laptop docked
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 Desktop
Packages, which is sub
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
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
30 matches
Mail list logo
