Public bug reported:
After updating from wily to xenial (beta 1 and following updates) the
screen freezes at login as soon as the lightdm splash comes up.
Switching to the console and logging in, I was able to capture the dmesg
output, which shows an OOPS in the drm module.
This happens with
Is there any way I could debug the issue with 4.13?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1697450
Title:
Gnome Shell hangs at startup
Status in gdm3 package in Ubuntu:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1697450/+attachment/4966437/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1697450/+attachment/4966435/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected wayland-session
** Description changed:
I'm trying to install from the daily Artful desktop image (20170612).
After boot, the gnome session hangs at startup, while the "zoom"
animation is being shown.
I have an intel card:
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1697450/+attachment/4966436/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
If I run gnome-shell from the terminal with the latest (4.13.0-12.13)
kernel, the system freezes.
Running apport-collect while running the 4.8 kernel segfaults:
$ sudo apport-collect 1697450
Invalid MIT-MAGIC-COOKIE-1 keyUnable to init server: Could not connect:
Connection refused
Invalid
To test the issue, I booted in text mode (multi-user.target), logged in
and then started gnome-shell.
Nothing happens (the session doesn't start and the console seems hang).
Via ssh, I ran the killall, saved the .crash file and uploaded to the
following bug:
FTR this still happens with gnome-shell 3.26.1-0ubuntu4 and kernel
4.13.0-16-generic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1697450
Title:
Gnome Shell hangs at startup
Status
*** This bug is a duplicate of bug 1748450 ***
https://bugs.launchpad.net/bugs/1748450
@Daniel
I see #1748450 is marked as fix released now, but I still see this behavior
(including Xwayland core dumps in my home) with latest bionic packages.
Should I open a new bug or unduplicate this one?
yes, Zesty has the same issue, and apparently bionic too.
FTR I've tried the v4.14.12 one from the mainline PPA and it behaves the same.
I'll give v4.9 a try too.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
@Daniel no, the whole system freezes, even if I ssh before the UI starts
(which requires exact timing), then the machine freezes.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1697450
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1697450
Title:
Whole machine freezes at startup using kernels after
How can I collect logs?
I'm currently using kernel 4.8.0-59.64 from yakkety, anything newer
makes the machine freeze at gdm login, or as a soon as I press enter at
login screen
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
No, everything is frozen, if I ssh in the machine before starting the
session, ssh is frozen too
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1697450
Title:
Whole machine freezes at
So, it seems that changing a bios setting for the (builtin) video card
frequency to "Auto" fixed the issue. it was previously set to match the RAM
freq (as the video memory is shared).
I can now run 4.13 fine.
Maybe something changed in the intel driver in 4.9 that makes it freeze when a
fixed
I tested the 4.9.0-040900-generic (4.9.0-040900.201612111631) kernel
from the mainline PPA, same issue.
Looking at the boot output the last message I see is about gdm.service starting.
The machine freezes at the boot output as soon as the mouse cursor appears.
--
You received this bug
I'm still seeing a similar issue with daily images of Bionic.
At boot, the machine hangs at splash screen.
If I boot without "splash quiet", I can see the last message is about starting
login session.
I'm not sure this is actually a duplicate of #1505409.
How can I help fixing this? It makes it
@Daniel I can't really follow those steps exactly, as the machine hangs
as soon as either GDM or gnome-shell is started
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1697450
Title:
I haven't seen any crash after latest updates, but I still have the
issue with screen freezing when coming out of the lock/blank screen.
Is there anything else I can do to track down the issue?
--
You received this bug notification because you are a member of Kernel
Packages, which is
Not when the system freezes for some time as described above. I'll see
if I get a crashdump when the session actually crashes
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1756092
Title:
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
This seems to have gotten worse after latest updates. Now if I leave the
PC for a while and the screen blanks, when I get and wake up the screen,
I find the login screen (and the previous session has creashed).
--
You received this bug notification because you are a member of Kernel
Packages,
I just reproduced a crash, uploaded the crash files to
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1759849 and
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1759850
** Changed in: gdm3 (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
After leaving my PC alone for a few minutes I found it at the login
window and the session crashed.
Attached is the crash log
** Attachment added: "_usr_bin_Xwayland.1000.crash"
After leaving my PC alone for a few minutes I found it at the login
window and the session crashed.
Attached is the crash log. If it can be useful, I also have a 145Mb
Xwayland core dump from the same crash
** Attachment added: "_usr_bin_Xwayland.1000.crash"
Attached a dmesg right after the issue occurred
** Attachment added: "dmesg"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5086281/+files/dmesg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I attached the previous dmesg without apparmor errors (although I don't
see much useful in there)
** Attachment added: "kernel.txt"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5087121/+files/kernel.txt
--
You received this bug notification because you are a
Done. Is there any more info I can provide on the original machine?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1756092
Title:
Screen freeze for some time when unlocking
Status in
** Attachment added: "kernel.log"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5087994/+files/kernel.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Attachment added: "journalctl.log.gz"
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1756092/+attachment/5088004/+files/journalctl.log.gz
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Uploaded the dmesg and journalctl log as requested
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1756092
Title:
Screen freeze for some time when unlocking
Status in gdm3 package in
Yes, the latter attachments are from my laptop, which shows the same issue.
Note that the issue happens on resume from screen standby, not resume from
machine standby
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Daniel,
I'll take a look at what that device is (I don't have access to that
computer today) but it's not a printer.
But as said, this behavior also happens on my laptop (also a fresh
bionic install). I've attached log from it right after the issue
occurred.
** Changed in: gdm3 (Ubuntu)
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1756092/+attachment/5083754/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
When trying to unlock the machine, sometimes the screen freezes entirely
(including mouse and keyboard input) for a long time either right away or after
submitting the password.
The freeze lasts for 10-20s, and
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1756092/+attachment/5083755/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1756092/+attachment/5083756/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
On a fresh 19.10 install, I get repeated (every ~10s) kernel backtraces
when wifi is enabled
This is an example of the trace:
[ 3963.367576] iwlwifi :04:00.0: Failed to get geographic profile info -5
[ 3963.367591] [ cut here ]
[ 3963.367660]
*** This bug is a duplicate of bug 1846016 ***
https://bugs.launchpad.net/bugs/1846016
Indeed, it does seem to be a duplicate.
With mainline kernel seems to be working fine.
Thanks!
** This bug has been marked a duplicate of bug 1846016
Intel Wireless AC 3168 on Eoan complaints FW error
Setting this to incomplete for maas as weel, since we couldn't reproduce
the issue with maas 2.7.
Please reopen if it happens again, with steps on how to reproduce
** Changed in: maas
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of
** Changed in: maas
Milestone: 2.8.0 => 2.9.0b1
** Changed in: maas
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881821
Title:
MAAS does
** Changed in: maas/2.8
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881821
Title:
MAAS does not properly detect max interface speed for
** Changed in: maas
Milestone: 2.8.0rc1 => 2.8.0
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881821
Title:
MAAS does not properly detect max interface speed for interfaces which
** Changed in: maas/2.7
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881821
Title:
MAAS does not properly detect max interface speed for
** Summary changed:
- [maas][focal]unable to deploy 20.04(focal) w/ default kernel for sut after
images update on Oct 5
+ unable to deploy 20.04(focal) w/ default kernel for sut after images update
on Oct 5
--
You received this bug notification because you are a member of Kernel
Packages,
Hi, is this system deployed by MAAS?
if so, could you please attach the output from the
50-maas-01-commissioning script from commissioning?
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is
Public bug reported:
After moving to Impish, my bluetooth headset doesn't automatically
connect when I power it on (it was working fine on hirsute).
When I go to the bluetooth settings, select it and click connect, the first
time it disconnects immediately and I see this line in bluetoothd
** Tags added: champagne rls-ii-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1949075
Title:
Bluetooth headset not autoconnecting on power-on on 21.10
Status in bluez package
This still happens on a clean 22.04 install (with 5.15.0-23-generic).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1949075
Title:
[Sony WI-C310] [Intel Wireless 8260] Bluetooth
Public bug reported:
On a clean 22.04 install, the screen randomly blanks once in a while for
a couple of seconds, then comes back.
I see the following message in dmesg when it happens:
[ 6614.338572] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun
ProblemType: Bug
DistroRelease:
Public bug reported:
On a Lenovo Thinkpad X260 with 22.04 and 5.15.0-23-generic kernel, after
suspending the laptop, it's never possible to wake it up.
Neither keyboard nor power button work, only way is to long-press to
force poweroff and restart.
This did not happen with 21.10.
ProblemType:
>From what I see, this could be indeed an issue with missing driver for
the specific network card in the initrd.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: maas
Status: Incomplete => Triaged
** Changed in: maas
Importance: Undecided =>
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967721
Title:
Laptop never resuming from standby
Status in linux package in Ubuntu:
Confirmed
Bug
** Tags added: rls-jj-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967727
Title:
Random screen blanks with "CPU pipe B FIFO underrun" error
Status in linux package in
Also, probably related, after the system has entered standby (the power
led pulsates slowly), the fan keeps running for a while. I've never seen
this behavior before with previous releases.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
After force-rebooting the machine and looking at the previous boot dmesg
(journalctl -k -b -1) I noticed this:
Apr 03 23:10:55 arrakis kernel: wlp4s0: deauthenticating from 1e:e8:29:9b:9e:c5
by local choice (Reason: 3=DEAUTH_LEAVING)
Apr 03 23:10:56 arrakis kernel: PM: suspend entry (deep)
Apr
I tested by installing the kernel from impish (linux-
image-5.13.0-40-generic) on jammy, suspend works correctly with that
one.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967721
On my laptop
5.13 -> always suspends/resume correctly (battery and power)
5.15 -> always fails to resume (battery and power)
fwupdate doesn't report any update available.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've also tested more recent versions than 5.15 from the mainline PPA
(5.16 and 5.17), they all fail to resume.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967721
Title:
Laptop
Daniel,
yes I'm using an external monitor via DP. This is the same setup I've
been using for a long time with no issue. I've reverted to the Impish
kernel (mainly because of an other kernel issue preventing
suspend/resume) and that makes the issue disappear.
** Changed in: linux (Ubuntu)
** Summary changed:
- [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on
power-on on 21.10
+ [Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not autoconnecting on
power-on on 22.04
--
You received this bug notification because you are a member of Kernel
From the comments above, it seems the generic kernel does not work on
this machine, and the xgene-uboot is required?
** Changed in: maas
Status: New => Incomplete
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Tags added: bug-council
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1922910
Title:
Unable to deploy HWE kernel with sub-arch set to xgene-uboot
Status in MAAS:
New
Status in
Confirmed that on a Thinkpad X260 with 5.15.0-46 suspend works fine.
Thanks
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1967721
Title:
Laptop never resuming from standby
Status in
Tested with 6.0.0 drm-tip kernel as well and still reproducible, filed
https://gitlab.freedesktop.org/drm/intel/-/issues/6793 upstream.
** Bug watch added: gitlab.freedesktop.org/drm/intel/-/issues #6793
https://gitlab.freedesktop.org/drm/intel/-/issues/6793
--
You received this bug
** Summary changed:
- Lenovo T14 G3 HDMI not working
+ Lenovo Thinkpad T14 G3 HDMI not working
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1989253
Title:
Lenovo Thinkpad T14 G3 HDMI
Public bug reported:
On 22.10 with 5.19.0-15-generic on a ThinkPad T14 gen3 (intel-based),
the HDMI port is not working, screen is not detected (both in xorg and
wayland).
Also tested with older 5.15.0-27-generic kernel, same result.
I see the following traceback in dmesg:
[3.510605]
** Tags added: rls-kk-incoming
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1989253
Title:
Lenovo T14 G3 HDMI not working
Status in linux package in Ubuntu:
Confirmed
Bug
This seems related: https://forums.lenovo.com/t5/Other-Linux-
Discussions/Thinkpad-T14-Gen-3-has-no-available-HDMI-ports-under-
Linux/m-p/5147202?page=1
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Following the suggestion on https://forums.lenovo.com/t5/Other-Linux-
Discussions/Thinkpad-T14-Gen-3-has-no-available-HDMI-ports-under-
Linux/m-p/5147202?page=8#5745003 I've tried setting
i915.enable_psr2_sel_fetch=0, which does seem to avoid the traceback.
--
You received this bug notification
Public bug reported:
When connecting display via USB-C, I get the following traceback in dmesg.
The display still work, though.
[ 62.598637] usb 3-5: new full-speed USB device number 11 using xhci_hcd
[ 62.761540] usb 3-5: not running at top speed; connect to
@Timo I'm not sure if the traceback in the log is related to HDMI not
being available.
I get the same error at every boot, even when w/o HDMI connected, or
when using an external monitor via USB-C (which works).
Should I open a separate bug for this traceback or repurpose this one?
--
You
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616833/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616834/+files/IwConfig.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Tags added: apport-collected wayland-session
** Description changed:
when running the "refresh" command I get the following message
$ sudo fwupdtool refresh
Loading… [**
]07:43:19:0893 FuBiosSettings
apport information
** Attachment added: "AudioDevicesInUse.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616832/+files/AudioDevicesInUse.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616847/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616841/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616842/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616846/+files/UdevDb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616844/+files/ProcModules.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616843/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616848/+files/acpidump.txt
** Changed in: linux (Ubuntu)
Status: Triaged => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616835/+files/Lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990052
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616839/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616840/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616838/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616836/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616837/+files/Lsusb.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990052
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1990052/+attachment/5616845/+files/RfKill.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Also, possibly related to driver issues, sometimes after (builtin)
screen blank due to inactivity, it's not possible to bring it back
anymore.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
FWIW I get the same error with the 5.19.0-16 package from -proposed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1989253
Title:
Lenovo Thinkpad T14 G3 HDMI not working
Status in
FTR this is still happening on 22.10
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1949075
Title:
[Sony WI-C310] [Intel Wireless 8260] Bluetooth headset not
autoconnecting on
** Changed in: maas
Milestone: 3.4.0 => 3.4.0-beta2
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2016908
Title:
udev fails to make prctl() syscall with apparmor=0 (as used by maas
95 matches
Mail list logo
