I had the same issue, having updated my Ubuntu partition to 18.04, ASUS K501UQ.
I added "dis_ucode_ldr" after "quiet splash" and it worked, both when
temporarily added using 'e' with GRUB, and permanently added by gediting
/etc/default/grub.
I would like to thank everybody on this thread, you
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
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 &
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
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
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
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
Public bug reported:
On attempted upgrade from 18.04LTS to 20LTS
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: wireguard-dkms 1.0.20201112-1~20.04.1
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Yeah it's a pretty ridiculous bug to have in an LTS release. Disk
encryption is a must these days, and other OSes like Windows support it
by default
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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"
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
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
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
a sound... for
which it doesn't have the codec, etc.
1. ALL notifications should name the PROGRAM and DATA KEY+VALUE involved:
kaccess is requesting additional codecs to play notification-sound
/home/tim/sound/broken_audio_file.ogg'
2. Notifications should be RATE LIMITED, and/or have a 'dismiss
I just installed Ubuntu 20.10 on a machine that was running Pop!os 20.04
and 20.10 (a fairly new AMD Ryzen desktop system, different to the
machine I had the problem on earlier, which was a laptop). Not 24 hours
later, this problem again. I thought there was something wrong with Team
app ('bloody
This is my first post here so I apologize if this is not appropriate.
On Nov 22, 2020 I upgraded from 18.04 LTS to 20.04 LTS over the wire (no
physical media). During the upgrade I received the following error
message in a dialog box:
"Could not install initramfs-tools"
"The upgrade will
This is my first post here so I apologize if this is not appropriate.
On Nov 22, 2020 I upgraded from 18.04 LTS to 20.04 LTS over the wire (no
physical media). During the upgrade I received the following error
message in a dialog box:
"Could not install initramfs-tools"
"The upgrade will
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818260
Title:
forget cluster node failed during cluster-relation-changed hook
To
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
Anyone know how to finish the installation?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903421
Title:
crash at end of installation procedure
To manage notifications about this bug go to:
Public bug reported:
The ubiquity installer, including both the text version on the Ubuntu
Server live CD and its GUI version does not support using existing LUKS
encrypted partitions. That means out of the box it wants to completely
wipe all existing partitions, this is a serious failure for
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,
Error while sending AddMatch () message: The connection is closed
Stopping Tracker file system data miner...
OK
systemd-hotnamed.service: Succeeded.
Delay lock is active (UID 1000/tim, PID 1690/gnome-shell) but inhibitor timeout
is reached.
Starting Suspend...
Suspending system...
PM: suspend entry
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.
T
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:
is docked, lid down, as before). Knock on wood, no issues...
I'll keep watching and report if any issues occur.
Thanks,
Tim
--
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:
Boot animation
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
Public bug reported:
Go to Settings > Mouse & Trackpad
* Turn off Natural Scrolling and Click "Test Your Settings"
* Moving scroll wheel "up" moves content down
* Turn on Natural Scrolling and Click "Test Your Settings"
* Scroll wheel behavior is unchanged
ProblemType: Bug
DistroRelease: Ubuntu
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
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.
--
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
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.
--
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:
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
This would be nice to have working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828842
Title:
mate-panel workspace switcher does not loop with repeatedly pressed
keyboard shortcuts on
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
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 suspe
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
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,
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
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
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
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
This is still present with Ubuntu 20.04 and the latest XFCE & LightDM.
This is a major pain almost to the point of me wanting to switch back to
GDM & Gnome.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
I want to add that in my case it's not related to WLAN. I'm not using
WLAN on the Pi and also totally disabled it in the config ( I was hoping
that helped, but it didn't ). So the issue is related to the ETH0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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,
I'm having the exact same issue on my RPi 3. I've been using the Pi for
a very long time now and never had an issue. But since last week I
updated the OS to the latest Raspberry OS and the Pi is now running as a
K3s master node. Since then the Pi keeps crashing like this. I've having
a lot of
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
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
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
Hmm. This upstream issue looks relevant:
"Correct PID but incorrect victim name"
https://github.com/rfjakob/earlyoom/issues/194
** Bug watch added: github.com/rfjakob/earlyoom/issues #194
https://github.com/rfjakob/earlyoom/issues/194
--
You received this bug notification because you are
To clarify, I have not confirmed the exact claim here - that "earlyoom
reports _wrong_ killed process name" (my emphasis) - so maybe I should
not have said it affects me.
But, I have confirmed that earlyoom is killing a process and either not
reporting it, or reporting it incorrectly, as this bug
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
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
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
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
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
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
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
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
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
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
3.36.6-1 tested on my focal system using focal-proposed. All seems OK
thus far.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879968
Title:
Copy/paste still sometimes fails in LibreOffice and Wine
Hi. My mistake. I had, some time ago, needed to install one package
from focal-proposed, and to do this had turned off letting synaptic etc
from showing all proposed updates by adding a file in
/etc/apt/preference.d. I'd forgotten about this.
sudo aptitude -t focal-proposed
showed that mutter
Marco - as I said, that is what I have done, but I do not see the focal-
proposed updates for mutter. In fact I see no proposed updates at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1896332
I am on focal, with the 'developer options' pre-release option ticked
(and repos re-reloaded). I'm not seeing any proposed updates. Is it
available to the public or not?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Tested again from focal-proposed (mutter 3.36.6-1ubuntu0.20.04.2). Can
confirm it still fixes the problem! (Intel HD Graphics).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell
Indeed, the PPA seems to be working without issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892440
Title:
Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly
on Nvidia)
To
This happens to me too. Note: when X is NOT running, the kernel still
locks up. This appears to be a kernel driver issue and not an X issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
Any chance this will get into focal soon? It's still making a mess of
my spreadsheets.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879968
Title:
copy/paste still sometimes fails in LibreOffice
OK after digging further through the logs, it seems that at some point
NetworkManager lost the vpn "HMAC Authentication" Cipher setting.
not sure if this was caused during the Dist upgrade or switching to IWD.
I will report further on this once I upgrade second laptop to Groovy.
--
You received
** Description changed:
Since upgrading to groovy my openvpn connection out to our corporate is
not working.
I was testing Iwd but have now reverted to wpa_supplicant.
- Connection to the vpn succeeds and routing table gets setup no traffic
- is flowing over the connection and I get
Public bug reported:
Since upgrading to groovy my openvpn connection out to our corporate is
not working.
I was testing Iwd but have now reverted to wpa_supplicant.
Connection to the vpn succeeds and routing table gets setup no traffic
is flowing over the connection and I get the following
We've been using 5.9rc since release, now on rc4. The problem is fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1878279
Title:
MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not
I relayed to Neil, he'll follow the guidance above and let you know
results.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892422
Title:
Pci passthrough interface not showing up in Ubuntu 20.04
My sound control panel reports three speech-dispatcher entries in Volume
Levels. I don't know why.
My session is about two days old and I haven't had any instance of
distortion, so the workaround referred to in my previous comment, a
config change, may be a good idea for package maintainers to
Sophos for linux detected this (as above), starting on 24th August 2020,
and now detects it every day in my daily on-demand scan.
I'm on 20.04, fully up to date.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If you want to test this, force YouTube to serve H264, which your card
supports judging by the vainfo results. A 4k 60fps YouTube video won't
be in a codec your hardware can handle, I guess. There are 'h264ify'
extensions for Chromium.
--
You received this bug notification because you are a
I should add, I don't have an NVIDIA card - intel integrated HD
graphics. As it stands, GNOME is a mess with differential scaling
everywhere some parts are smaller, some are larger (notably the menu
bar).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Also struggling since the latest mutter and/or gnome-shell update
(3.36.4). Font scaling is mismatched throughout the entire GUI. It's
larger than normal in the menu-bar, while it's smaller/squished in
terminal. This makes it difficult to fix. If I scale down to 0.9 to fix
the menu bar, text
Christian I work with Neil, the setup is in a qemu VM. so the host OS
is Ubuntu 18.04 in both cases, its just within the Guest VM that the os
changes from 18.04 to 20.04 with the exact same parameters. it is
automated, so the setup is exact comparison with the only difference
being the OS
Public bug reported:
I did a fresh install and can't connect from Windows 10 to Ubuntu 20.04
even though the smb.conf claims it is clean and the server launches and
says ready for connections.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: samba-common-bin 2:4.11.6+dfsg-0ubuntu1.4
I will try this workaround/config change:
https://github.com/brailcom/speechd/issues/198#issuecomment-619605269
** Bug watch added: github.com/brailcom/speechd/issues #198
https://github.com/brailcom/speechd/issues/198
--
You received this bug notification because you are a member of Ubuntu
This bug started affecting me in the past week although I've been on
20.04 since launch. I have removed the packages including orca.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736222
Title:
I just did a right click copy and paste in writer and it works the 1st
time, 2nd time it uses the 1st copy not the 2nd. And so on. All said to
be fixed in the next version - at this rate in a month or 2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Sadly, ubuntu 20.04 has just released 3.36.4, which doesn't fix the
problem.
It'd be good if 3.36.5 was at least available in developer options.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879968
kernel: iwlwifi :02:00.0: Microcode SW error detected. Restarting
0x200.
kernel: iwlwifi :02:00.0: Start IWL Error Log Dump:
kernel: iwlwifi :02:00.0: Status: 0x0040, count: 6
kernel: iwlwifi :02:00.0: Loaded firmware version: 36.79ff3ccf.0
8265-36.ucode
kernel:
Same here. I don't think this bug has been fixed. Can we please reopen
it?
Machine: ThinkPad Carbon X1 6th gen (same as in this issue's description)
Linux: 5.6.14-2
firmware-iwlwifi: 20200619-1
$ modinfo iwlwifi | grep 7260
firmware: iwlwifi-7260-17.ucode
This issue is specifically
Comment #28 seems to offer some good insights about the best path
forward here, also supporting that this bug should be reopened. Note
that with a Google Wifi router, there is no capability to reconfigure
the router to work around this issue, as the poster mentions.
--
You received this bug
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1888237
Title:
nova-next job fails as novnc service fails with TypeError:
*** This bug is a duplicate of bug 1643911 ***
https://bugs.launchpad.net/bugs/1643911
** Also affects: ubuntu
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
device is an IdeaPad 5 14 (14ARE05) with a Ryzen 5 4600
Now on kernel 5.8
observation is that the touchpad sometimes doesn't work. So far,
shutdown and remove AC then restart fixes it every time. This was true
on 5.7 too.
Something goes wrong with hardware initialisation?
--
You received this
Too late, I am already at 20.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832754
Title:
"shutdown[1]: Failed to wait for process: Protocol error" at shutdown
or reboot and hangs.
To manage
901 - 1000 of 22042 matches
Mail list logo
