Public bug reported:
I would like to request that this AMD fix be backported to OEM kernels
https://github.com/torvalds/linux/commit/4f26c95ffc21a91281429ed60180619bae19ae92
the 6.11 OEM kernel currently leaves display backlight at maximum
brightness in conjunction with power-profiles-daemon v0.
I just built it from source for 24.04 and it fixes the problem, yay.
chatgtp gave me step by step instructions on how to do this, after I provided
the link to the source page, and it worked first time.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
t;
> Title:
> Plymouth's hidden console contains squares instead of bold text on
> live session shutdown
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2056526/+subscriptions
>
>
--
Tim Richardson
I have this problem on Asus ProArt Creator X670E AM5 (AMD), after a BIOS update
and CPU upgrade.
Disabling plymouth (SPLASH) and the TPP hardware makes no difference.
The 6.8, 6.11 OEM kernel and latest liquorix 6.11 all show this problem.
Occasionally it will reboot or shutdown, maybe 5% of the
There might be a race condition.
The modified script below allows the bold fonts to display:
The difference is the
ExecStart=- /bin/sleep 1
A value of 0.1 means the bold fonts do not render
a long delay (say 5s) changes in a bad way the shutdown process. The
messages stop with complaints about
Upstream can reproduce it (with a kubuntu live boot) , they say it is
"weird" and guess: "On shutdown, label-pango is always loaded before
switching the file system, but the font is loaded only when you hit the
Esc key. Once the root file system is unmounted, label-pango no longer
able to access sy
In
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/152
which relates to https://bugs.launchpad.net/bugs/1942987 reference
above, there was a comment from upstream:
"we ship a script plymouth-populate-initrd upstream that copies all the
necessary files if you can hook into that."
I men
PS on this same install, I also see this very recently, but I assumed it was
related to a BIOS update in preparation for CPU upgrade:
[this is pasted from http://iso.qa.ubuntu.com/qatracker/reports/bugs/2056526]
Boxes that ended with black screen & cursor/underscore (static/not-blinking)
- dell
I am seeing this in Ubuntu 24.04.1, in an actual install on a
workstation with amd graphics and four monitors, but not on another
installs.
The problem occurs:
a) only in shutdown messages
b) only in the default bgrt theme
c) does not happen in other themes I have tried: spinner, ubuntu-gnome-logo
Could be
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/233 [Closed]
** Bug watch added: gitlab.freedesktop.org/plymouth/plymouth/-/issues #233
https://gitlab.freedesktop.org/plymouth/plymouth/-/issues/233
--
You received this bug notification because you are a member of Ubuntu
Public bug reported:
On shutdown, user can escape splash screen and view console logs with the ESC
key.
With the default Ubntu plymouth theme, this breaks rendering of systemd
messages, making them unreadable. Other console messages are not affected.
I will upload a screen shot.
This is repor
Screen shot of console when using default plymouth theme and ESC to view
messages
** Attachment added: "image of shutdown screen"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/2084952/+attachment/5829661/+files/PXL_20241018_231733721.jpg
--
You received this bug notification becaus
this is not a bug. It's telling you to undo packages added by a ppa before the
upgrade.
ppas can introduce versions and dependencies not expected by the upgrader, so
it's warning you now rather than risking a broken update.
the ppa-purge command will do that for you and most of the time it work
a
> duplicate bug report (2065288).
> https://bugs.launchpad.net/bugs/2061687
>
> Title:
> Snapshot doesn't work until camera is unplugged and plugged back in
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/oem-priority/+bug/2061687/+subscrip
thanks this works for me, thanks for this. Probably an example for all
the other snaps and appimages out there with the same problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2045820
Title:
fi
might be more
> appropriate for such code (which now is much easier to understand).
>
> @JJ - how should we guard correctly in apparmor to allow usage of for
> anonymous via memfd_create as allocation backend files?
>
> ** Also affects: apparmor (Ubuntu)
>Importa
after enabling audit.log I get this message when the profile is in
enforce mode
type=AVC msg=audit(1721533808.319:1238): apparmor="DENIED" operation="truncate"
class="file" profile="libvirt-465a6629-3167-43fc-93da-4c7ef837d863" name="/"
pid=37291 comm="qemu-system-x86" requested_mask="w" denied
One workaround is to do
aa-complain /etc/apparmor.d/libvirt/libvirt-
You may need to
touch /etc/apparmor.d/libvirt/libvirt-.files
because the .files may not be present, it is created and removed
dynamically by libvirt
Another workaround is to (accidentally) break the apparmor profile so it
can
(earlier I had disabled apparmor while investigating another problem but
I forgot that I did this, sorry)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073214
Title:
hugepages causes permissions er
I want to reopen this. I think there is an apparmor problem.
Here is how to reproduce:
I made a new Ubuntu 24.04 desktop to an external drive on my AMD laptop.
I did all suggested updates, set up virt-manager and installed hugeadm
Then I download the image for the 24.04 server and installed it
** Changed in: libvirt (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073214
Title:
hugepages causes permissions error [invalid, page pool too small]
To manag
I can't work out the process owning the reserved pages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2073214
Title:
hugepages causes permissions error [invalid, page pool too small]
To manage noti
1:36 black dnsmasq[9079]: read /etc/hosts - 8 names
Jul 18 20:31:36 black dnsmasq[9079]: read
/var/lib/libvirt/dnsmasq/default.addnhosts - 0 names
Jul 18 20:31:36 black dnsmasq-dhcp[9079]: read
/var/lib/libvirt/dnsmasq/default.hostsfile
On Thu, 18 Jul 2024 at 20:27, Tim Richardson
wrote:
> T
m/mailman/listinfo/libvir-list
>
> P.S. @Sergio who usually looks at these - sorry for stealing those
> interesting cases in my morning, bad timezone luck for you :-P. Do not
> be concerned, you might deal with is long enough down the road :-)
>
> ** Bug watch added: github.com/sy
Public bug reported:
After upgrading from 22.04 to 24.04, a VM set to autostart is no longer
starting.
service status indicates the problem is /dev/dri not existing.
tim@black:~$ systemctl status libvirtd
○ libvirtd.service - libvirt legacy monolithic daemon
Loaded: loaded (/usr/lib/system
** Changed in: libvirt (Ubuntu)
Status: Incomplete => Invalid
** Summary changed:
- hugepages causes permissions error
+ hugepages causes permissions error [invalid, page pool too small]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
r full guest-config in regard to memory
> - hugeadm --list-all-mounts
> - journalctl -f while starting the guest
> - grep -i huge /proc/meminfo
>
> ** Changed in: libvirt (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because
When I reboot I see a directory libvirt and then libvert/qemu
tim@black:/dev/hugepages$ tree -pug
[drwxrwx--t root hugetlb ] .
└── [drwxr-xr-x root root] libvirt
└── [drwxr-xr-x root root] qemu
3 directories, 0 files
--
You received this bug notification because you a
** Description changed:
Today I upgraded from 22.04 to 24.04
+
+ 10.0.0-2ubuntu8.2
+
I have a VM with 16GB of hugepages allocated to it.
This no longer works.
I can not defeat the virtual machine start up error (from virtual
manager):
Error starting domain: internal error
Public bug reported:
Today I upgraded from 22.04 to 24.04
10.0.0-2ubuntu8.2
I have a VM with 16GB of hugepages allocated to it.
This no longer works.
I can not defeat the virtual machine start up error (from virtual
manager):
Error starting domain: internal error: QEMU unexpectedly closed th
Public bug reported:
I upgraded 22.04 to 24.04 today on a workstation PC which runs VMs
managed by virtual-manager
VMs using the "hardware device" filesystem did not start.
The package virtiofsd needed to be installed.
Has this been split into a separate package from some other package in
24.04
** Description changed:
I have hardware decoding working with mpv, evidence is nvtop. Hardware is AMD
7840U igpu.
- test file is a vp9 encoding.
+ test file is a vp9 encoding.
- vlc .deb does not show VA-API has a decoding option
+ vlc .deb does not show VA-API as a decoding option
- How
Public bug reported:
I have hardware decoding working with mpv, evidence is nvtop. Hardware is AMD
7840U igpu.
test file is a vp9 encoding.
vlc .deb does not show VA-API has a decoding option
However, the flatpak package works.
The snap package does not work.
Ubuntu 24.04
This was reported
the rendering problem is identical when using virt-manager with the
virtio video driver with open gl 3D accel enabled. persists even in
latest kisak fresh mesa.
workaround is
export GSK_RENDERER=gl
in ~/.profile or where ever you set your environment variables.
--
You received this bug notific
Please note that for virtio/virt-manager, setting this envionment
variable in ~/.profile may be a workaround.
export GSK_RENDERER=gl
this at least fixes Files
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.n
This affects qemu/kvm too. On vanilla 22.04 host, gtk4 apps (e.g. Files)
from 24.04 do not render properly (with 3D/openGL enabled)
via virt-manager
mesa in the 24.04 guest is 24.0.5-1
Fedora 40 guest with all updates has the same problem (open files apps and view
files in list view, for examp
the issues in Comment #10 appear to be closed, and they are not mentioned
anyway on
https://discourse.ubuntu.com/t/noble-numbat-24-04-release-status-tracking/44043
so it is confusing.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For me the fix included the new version of pipewire (now released in
24.04) AND adding my user to the video group
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061687
Title:
Snapshot doesn't work
I confirm the findings of @corradoventu : fixing this requires both
pipewire1.0.5-1 AND adding my user to group video.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060390
Title:
Snapshot No Camera
*** This bug is a duplicate of bug 2061687 ***
https://bugs.launchpad.net/bugs/2061687
** This bug has been marked a duplicate of bug 2061687
Snapshot doesn't work until camera is unplugged and plugged back in
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Package changed: ubuntu => pipewire (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2065288
Title:
gnome 46 camera app requires systemctl --user restart pipewire
To manage notifications a
Public bug reported:
In ubuntu 24.40 the camera app will not see my laptop camera until I do
this:
systemctl --user restart pipewire
this is required in every log in.
The camera problem also affects other usage, such as using the laptop camera in
google meet via firefox.
It is probably a pipe
@sbeattie I tested the package you built for 22.04 and it fixes the
problem for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060354
Title:
Segfaults and assertion failures in Xorg's render/gly
@sbeattie It's broken in mantic too. In xwayland, the window dies. in
xorg, the session crashes, badly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2060354
Title:
Segfaults and assertion failures
Yeah, for me it crashed 100% of the time with no changes, and removing a
configuration file (which among other things removed my non-default
preference for grayscale antialias) completely stopped the crashing.
This is in a kvm/qemu VM. So from my perspective, and from a few others
users, it looks l
for what it's worth, JetBrains bug reports find that the problem is
triggered by requesting grayscale anti-aliasing.
https://youtrack.jetbrains.com/issue/IDEA-350864/Idea.sh-abort-X-window
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
I use the wayland session. I sort of have this bug. The screens do power
off, but then the backlights resume. It is still a blank screen
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971434
Title:
Public bug reported:
Ubuntu now defaults to systemd oom handling.
Is there a way to warn an upgrade user who has earlyoom installed that the two
are in conflict (assuming that they are).
** Affects: earlyoom (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug not
I see this in the xorg session in the flatpak firefox save downloads
dialog, for instance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971112
Title:
File picker gets bigger more and more each tim
see also https://bugzilla.redhat.com/show_bug.cgi?id=2072070 for lengthy
discussion.
** Bug watch added: Red Hat Bugzilla #2072070
https://bugzilla.redhat.com/show_bug.cgi?id=2072070
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, out of habit I installed the snap. The .deb works fine, so I am
using that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967437
Title:
does not detect battery discharge 22.04 beta thinkpad
Ubuntu 22.04.
I still have this problem
intel-media-va-driver 22.3.0
tigerlake laptop
$ apt-cache show intel-media-va-driver
Package: intel-media-va-driver
Architecture: amd64
Version: 22.3.0+dfsg1-1
tim@ochre:~$ vainfo
libva info: VA-API version 1.14.0
libva info: Trying to open /usr/lib/x86_
Public bug reported:
On Tigerlake Thinkpad X1, ubuntu 22.04 beta
powerstat -d 0
reports
Device is not discharging, cannon measure power usage.
this worked previously, including with the snap installed on Fedora 35
kernel is 5.15.0-23-generic
** Affects: powerstat (Ubuntu)
Importance: Und
** Tags removed: verification-needed-impish
** Tags added: verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google Contacts API Deprecated
To manage notificatio
(... Ubuntu 21.10)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google Contacts API Deprecated
To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-dat
I used proposed-updates today to get the latest evolution, and contact sync
works again.
So 3.40.4-1ubuntu2 works. (amd64 arch)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1952107
Title:
Google
I have this laptop. Bug happens on S3 suspend, much better on modern
standby (once it took two minutes or so for the touchpad to resume,
every other time it has worked).
Modern suspend does not use much battery. Mine slept for 8:20h last night and
the battery percentage declined from 96% to 94%.
It doesn't corrupt boots. It's inconvenient.
On Wed, 1 Sept 2021, 15:31 martin, <1396...@bugs.launchpad.net> wrote:
> This sounds like a massive, GIGANTIC bug which is corrupting people's
> boot setups. It's a wonder that it hasn't been fixed after SEVEN YEARS.
>
> --
> You received this bug noti
No data available from (1) or (2) and the problem has not reoccurred.
I have commented line 23 of crashdb.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1927767
Title:
All apps crashed in my X11
Public bug reported:
The reboot failed with many services that could not stop. I think there
may have been a crash in the network stack.
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-16-generic 5.11.0-16.17
ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
Uname
The flathub version is fixed too.
Please see upstream bug report
https://github.com/pdfarranger/pdfarranger/issues/478
which is closed as fixed in new release.
** Bug watch added: github.com/pdfarranger/pdfarranger/issues #478
https://github.com/pdfarranger/pdfarranger/issues/478
--
You recei
Update. I had zram-tools installed as well. Or at least, I have it after the
upgrade to 21.04
I removed it and zram-config, and reinstalled zram-config, and it works fine.
However, this still doesn't make much sense: if they were both installed
previously, why did it stop working?
I stepped thr
Public bug reported:
Under 20.10, my machine of 64GB had 8 zram devices of 2GB each.
After the 21.04 upgrade, zram was still configured, but now with one 1 device
of 256MB.
dpkg-reconfigure did not fix this
purge and reinstall did not fix this.
$ cat /proc/swaps
Filename
otherwise
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
//bugs.launchpad.net/bugs/1816497
>
> Title:
> [snap] vaapi chromium no video hardware decoding
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
>
--
Tim Richardson
--
You received this
t; To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1396379/+subscriptions
>
--
Tim Richardson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
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 m
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 imp
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 membe
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
B
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:
spee
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 b
@olepet I have 14ARE05 too, same symptoms. It seems the hardware is different,
we need a new bug.
I see no elan modules loaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1881319
Title:
Touchpad
I tested this today, and with HDMI connection, I no longer have the
problem.
--
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:
booting with splash hangs when external monitors are connect
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159
** This bug is no longer a duplicate of bug 1874194
Ubuntu 20.04 HDMI connected, no boot
** This bug has been marked a duplicate of bug 1872159
booting with splash hangs when external monitors are conn
*** This bug is a duplicate of bug 1872159 ***
https://bugs.launchpad.net/bugs/1872159
** This bug has been marked a duplicate of bug 1872159
booting with splash hangs when external monitors are connected (pure intel
8th gen laptop)
--
You received this bug notification because you are a
I experience this in 20.04 as well: remote session with Workstation,
after termination the greeter on this host does not respond to the
mouse. The keyboard allows access to virtual terminals and ctrl-alt-
delete reboots.
Hopefully nomachine has an answer.
--
You received this bug notification be
You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1396379
>
> Title:
> installer uses first EFI system partition found even when directed
> otherwise
>
> To manage notifications about this bug go to:
>
>
@vasyl: thanks, good comment. It pays to RTFM, apparently.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765363
Title:
prime-select intel is not powering off the nvidia card
To manage notification
For me in 20.04, bug is definitely still present. I have earlyoom active, and
32 gb a few seconds of "freeze" (which is not really a freeze) earlyoom
activates and nukes a few things, including Firefox, which brings back
interactive response. It also killed Chrome and Remmina, which was irritat
PS there is no text at all, the process gets as far as the spinning icon
and stops. I don't see the fsck check start.
--
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:
booting with splash
Hi Sebastien,
my most recent attachment #11 is from a failed boot.
When it gets stuck, I get no keyboard response from Esc, ctrl-C. I don't think
it is possible to log in to virtual terminals at this point in the boot, but if
I try, I can get to a blank screen, which after a few seconds jumps bac
I have been trying to work out how to log a failed session with plymouth debug
messages. I finally succeeded, it is attached.
Note that at the end of log file, it goes into suspend. That was me trying to
power off the machine, and not holding the button long enough. It actually
suspends and resu
I have been investigating other bug reports. I can't find anything that
helps my very much, but I did note references to timing. It is very
puzzling why I don't have problems when booting from the installation to
an external drive. That drive is actually a USB stick (ext4 formatted).
My internal ss
I installed 20.04 beta on a usb drive on the same machine, and reinstalled
packages to resemble my main install as closely as possible. The bug does not
occur when booting from the usb drive.
The most significant difference I can think of is that the main install is on
an lvm partition (unencry
** Attachment added: "boot messages with plymouth debugging messages"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5352286/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
** Summary changed:
- booting with splash hangs when external monitors are connected (pure intel
laptop)
+ booting with splash hangs when external monitors are connected (pure intel
8th gen laptop)
** Description changed:
+ I think this is a problem with the splash boot loader. This problem is
** Summary changed:
- booting with splash hangs when external monitors are connected
+ booting with splash hangs when external monitors are connected (pure intel
laptop)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
** Attachment added: "journalctl -b-1 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1872159/+attachment/5351782/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
** Attachment added: "journalctl -b0 > journal.txt"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1872159/+attachment/5351769/+files/journal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
What happens if you edit
/etc/default/grub
to remove splash as a setting (that is, boot without plymouth).
I was having similar problems to you, also with log message saying job was on
hold. I did not wait beyond 3 minutes. In my case, this only happens if an
external monitor is connected at boo
** Also affects: plymouth (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/1872159
Title:
booting with splash hangs when external monitors are conne
boot.log could not be attached by the report tool, I added it manualy
--
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:
booting with splash hangs when external monitors are connected
To
Public bug reported:
I think this is a problem with the splash boot loader.
I have installed 20.04 to this laptop. Clean install, not an upgrade.
When booting from the install, the greeter screen is never reached if external
monitors are connected at startup.
I get the spinning ubuntu logo, and
@Alberto, couldn't prime-select do this when going into hybrid or
Optimus mode? Only users with nvidia hybrid graphics would go down this
logic path, and they are only ones who need the fix (but only if they
are using gdm3, sddm and lightdm continue to be unaffected by this)
The set of users who "
not 'a fix', the intel maintainer's 5.4 patch has been applied by the
ubuntu devs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856653
Title:
CVE-2019-0154 caused major power problem, pls backport
Confirming that a fix has been backported to 20.04, currently in the
proposed kernel. I'm testing it, the power usage is great.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856653
Title:
CVE-2019-
This bug persists in 20.04 daily.
The one-line Pop!OS solution
(https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/comments/26)
works, just logout and login.
Pop!OS has used this for several releases now, just saying.
** Summary changed:
- nvidia-drm.modeset=1, gdm3 and optimus lap
Also, please note the upstream bug discussion also includes patches for 5.4
It seems that 5.4 is destined for 20.04. So far 5.4 upstream is still using the
first release of this patch, which means 5.4 has the i915 RC6 bug. 5.4 is a LTS
kernel bug so it strange to me, but please, I hope you can co
Yes, that little patch applies cleanly to every 5.3 hwe build I've done (about
five I'd say)
To be clear:
diff --git a/drivers/gpu/drm/i915/gt/intel_lrc.c
b/drivers/gpu/drm/i915/gt/intel_lrc.c
index 82b7ace62d97..b18f281d5d12 100644
--- a/drivers/gpu/drm/i915/gt/intel_lrc.c
+++ b/drivers/gpu/drm
1 - 100 of 392 matches
Mail list logo
