I'm experiencing the same issue. Will we be adding these packages back?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2061914
Title:
libjavascriptcoregtk-4.0-18 seems to be missing on the latest
** Description changed:
During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at
very early stage of booting process.
- The last messages displayed on the screen are:
+ The last messages displayed on the screen are:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID
Public bug reported:
During the SRU testing for 6.5.0.33 kernel, I found some machines freeze at
very early stage of booting process.
The last messages displayed on the screen are:
EFI stub: Loaded initrd from LINUX_EFI_INITRD_MEDIA_GUID device path
EFI stub: Measured initrd data into PCR 9
That did the trick, thank you! I can confirm that after updating via apt
on noble beta, VisualVM now launches successfully with the default JRE
(21)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
You're experiencing LDAP authentication issues while migrating from
Ubuntu 10.04 with Apache 2.2 to Ubuntu 14.04 with Apache 2.4 and
Subversion 1.8. The problem stems from changes in Apache versions. To
address this, apply the patch provided in the Apache bug report
Public bug reported:
Installing VisualVM via the apt on noble beta automatically installs
java 21, but the packaged version of VisualVM (2.1.6) only supports Java
20 and below. When you try to launch it, you get a pop up message
stating:
"You are running VisualVM using an unsupported Java
** Changed in: linux-aws (Ubuntu Jammy)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043811
Title:
AWS: arm64: pauth: don't sign leaf functions
To
Confirmed as working by Amazon.
** Tags removed: verification-needed-jammy-linux-aws
** Tags added: verification-done-jammy-linux-aws
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2043811
Title:
** Also affects: linux-intel-iotg-5.15 (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/2056383
Title:
Audio turned to dummy output from
@Francis
I've confirmed that the DUT has already used the latest ubuntu-drivers from
proposed.
Setting up ubuntu-drivers-common (1:0.9.0~0.20.04.8) ...
But it doesn't seem to solve the issue. Please check following messages.
+ _run sudo ubuntu-drivers devices
+ ssh -t -o
** Summary changed:
- NetworkManager 1.36.6 orders IPv6 addresses incorrectly
+ NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Situation:
- My network has both DHCPv6 and SLAAC for IPv6. From a privacy
+ My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over
** Description changed:
Situation:
My network has both DHCPv6 and SLAAC for IPv6. From a privacy
perspective, for readability reasons and for network management
policies, DHCPv6 should *always* be preferred over SLAAC addresses when
available. And according to RFC 6724, the smaller
** Description changed:
- My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
- perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available. And according to RFC 6724 the
- smaller /128 scope of the DHCPv6 address should be chosen
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available. And according to RFC 6724 the
smaller /128 scope of the DHCPv6 address should be chosen
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
- over SLAAC addresses when available.
+ over SLAAC addresses when available. And according to RFC 6724 the
+ smaller /128 scope
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
** Tags added: regression-update
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977619
Title:
NetworkManager 1.36.6 orders IPv6 addresses incorrectly
To manage notifications about this bug go to:
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
-
@seb128 I have created a new bug report with links to the upstream
commits. The core of the issue is that IPv6 addresses are now being
added in the wrong order, so the kernel prefers SLAAC addresses over
DHCPv6 addresses, which should be the other way around.
As this is a breaking change in
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
** Tags added: jammy
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply
I guess these commits are relevant:
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/c631aa48f034ade2b5cb97ccc4462d56d80174e7
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/257221d1986b56cbb2e329fcc74a2daca145b7aa
Bottom line: addresses are now being
Comparing the output of `ip -6 a`, you can see that the dynamic
addresses are no longer at the top of the list, where they should be.
Before (network-manager 1.36.4):
2: eno0: mtu 1500 state UP qlen 1000
inet6 2a10:3781:::bd0/128 scope global dynamic noprefixroute
valid_lft
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
Looking at the changelog of 1.38.0:
* Fix bug setting priority for IP addresses.
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-38/NEWS
So it looks like Ubuntu just introduced that bug by upgrading to 1.36.6.
Please either backport it from 1.38.0 or revert to 1.36.4.
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974428
Title:
Update to the current 1.36 stable version
To manage
** Description changed:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
Public bug reported:
My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
perspective and readability reasons, DHCPv6 should *always* be preferred
over SLAAC addresses when available.
NetworkManager has always been able to adhere to that by simply setting
ip6.privacy=0 for the
All of a sudden SLAAC addresses are preferred over DHCPv6 addresses,
which should not be happening. Setting ip6.privacy=0 no longer helps,
nor does setting net.ipv6.conf.all.use_tempaddr = 0 with sysctl.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Output of dmesg attached.
** Attachment added: "output dmesg"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5593690/+files/dmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is greatly exasperated because systemd until v251 is using MemFree
and not MemAvailable to decide how much memory is remaining. Since Linux
aggressively uses MemFree for caching, this will result in systemd-oomd
excessively killing applications.
There's a fix in upstream
Please find output of cat /proc/iomem attached.
** Attachment added: "output cat /proc/iomem"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956177/+attachment/5593426/+files/iomem.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATL'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATL
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATL returned object 09af25b3,
external buffer length 18
[Integer] =
$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATH'
Evaluating
Yes - Disabling Secureboot worked in order to get acpidbg working
(killed my touchpad mouse however that is another topic).
Output from both commands here:
$ sudo acpidbg -b 'ex \_SB_.PCI0.LPCB.EC0_.BATD'
Evaluating \_SB_.PCI0.LPCB.EC0_.BATD
Evaluation of \_SB_.PCI0.LPCB.EC0_.BATD returned
Unfortunately I get an "Operation not permitted" error when running sudo
acpidbg -b 'ex \_SB_.BAT1._STA' as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177
Title:
battery not detected
Hi,
I left the PC at the office. Will try the new command on Friday when I will be
there again. Thanks!
Br. Kevin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177
Title:
battery not detected
Unfortunately I get an "Operation not permitted" error when I try to run
acpidbg here. Is above command exactly as it should be entered? Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956177
ations
This will give you a dsdt.aml that should work.
I did that with: sudo iasl -ta dsdt.dsl and got the aml file just with
warnings.
11) Proceed as above
sudo cp dsdt.aml /boot/
sudo cp 01_acpi /etc/grub.d/
chmod 755 01_acpi
sudo update-grub
reboot
Still just the same :/
Can anyone point me in
This bug is back in ubuntu 22.04, somehow. In the previous ubuntu version I was
using it was possible to add workarounds via xinput rules, but the clickpad
parameter seems to be absent from libinput quirks, instead it uses this kernel
parameter?
all three mouse buttons misbehave in various
** Also affects: wine via
https://bugs.winehq.org/show_bug.cgi?id=52770
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971901
Title:
dlltool uses
Linking binutils package and subscribing Mattias Klose since
https://launchpad.net/ubuntu/+source/binutils/2.38-4ubuntu1 mentions
"Update from the binutils 2.38 branch: Fix PR 28885" and so a rebuild
based on binutils-source_2.38-4ubuntu1 would fix this issue.
--
You received this bug
** Bug watch added: Sourceware.org Bugzilla #28885
https://sourceware.org/bugzilla/show_bug.cgi?id=28885
** Also affects: binutils via
https://sourceware.org/bugzilla/show_bug.cgi?id=28885
Importance: Unknown
Status: Unknown
** Also affects: binutils (Ubuntu)
Importance:
Thanks for the reply! Reported upstream here:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1860
And patch submitted here: https://gitlab.gnome.org/GNOME/gnome-control-
center/-/merge_requests/1328
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1860
Public bug reported:
In Ubuntu 20.04, I was able to set Left Ctrl as my Compose key using
gnome-tweaks. I just upgraded to 22.04, where the Compose key settings
have been removed from gnome-tweaks and moved into control-center, but
Left Ctrl is not in the list of options for Compose.
I was able
/kubelet/pki
total 16
drwxr-xr-x 2 root root 4096 May 11 05:09 .
drwxr-xr-x 3 root root 4096 May 11 05:09 ..
-rw-r--r-- 1 root root 2291 May 11 05:02 kubelet.crt
-rw--- 1 root root 1675 May 11 05:02 kubelet.key```
If the files are there, then it's vulnerable.
Thanks,
Kevi
Public bug reported:
`man java` shows a man page for some build of JDK 8 in 2015, not the
`java` included in this package with documentation appropriate for the
included JVM.
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: openjdk-11-jre-headless 11.0.15+10-0ubuntu0.21.10.1
Missed a link, https://bugs.winehq.org/show_bug.cgi?id=52770 shows
others on jammy hitting the same (and confirms this upstream patch fixes
it)
** Bug watch added: Wine Bugzilla #52770
https://bugs.winehq.org/show_bug.cgi?id=52770
--
You received this bug notification because you are a
Public bug reported:
Installation of qgis 3.22.4 fails in post install configure on jammy.
The qgis-providers package seems to be the problem. The only meaningful
info I got was an error from synaptic claiming a name was missing from a
package file. apt only gave a generic 127 error.
Don't be
Public bug reported:
Description:Ubuntu 22.04 LTS
Release:22.04
binutils-mingw-w64-x86-64 2.38-3ubuntu1+9build1
/usr/bin/x86_64-w64-mingw32-dlltool now encounters errors like
tools/winebuild/winebuild -b x86_64-w64-mingw32 -w --implib -o
dlls/winmm/libwinmm.delay.a --export \
Isn't this a release blocker? It most definitely should be in my
opinion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243
Title:
gdm 42.0-1ubuntu4 no longer shows Wayland option
To manage
You can just remove 61-gdm.rules yes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243
Title:
gdm 42.0-1ubuntu4 no longer shows Wayland option
To manage notifications about this bug go to:
42.0-1ubuntu4 seems to block Wayland on *every* GPU, so it's not really
a good way to test NVIDIA support I would say.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969197
Title:
42.0-1ubuntu4
*** This bug is a duplicate of bug 1969243 ***
https://bugs.launchpad.net/bugs/1969243
** This bug has been marked a duplicate of bug 1969243
gdm 42.0-1ubuntu4 no longer shows Wayland option
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
*** This bug is a duplicate of bug 1969243 ***
https://bugs.launchpad.net/bugs/1969243
** This bug has been marked a duplicate of bug 1969243
gdm 42.0-1ubuntu4 no longer shows Wayland option
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
When I outright delete /lib/udev/rules.d/61-gdm.rules it also works
normally again with 42.0-1ubuntu4, so the problem is with one of the
udev rules.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For me, gdm3 42.0-1ubuntu4 breaks Wayland entirely. There is no option
to select a session left when logging in, and when I enter my password
and press enter I'm left in an X11 session.
I only have machines with Intel graphics.
Reverting to 42.0-1ubuntu2 makes it work normally again (defaults to
For me 42.0-1ubuntu4 breaks Wayland as well on all my (Intel-only)
machines.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968929
Title:
No Wayland support on my NVIDA laptop
To manage
** Tags added: jammy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969243
Title:
gdm 42.0-1ubuntu4 no longer shows Wayland option
To manage notifications about this bug go to:
Public bug reported:
After updating gdm3 from 42.0-1ubuntu2 to 42.0-1ubuntu4 in jammy, it no
longer shows any sessions in the bottom-right corner. When I log in, I
am dropped into an X11 session, with no way to switch to Wayland.
Downgrading the gdm3, gir1.2-gdm-1.0 and libgdm1 packages to
Public bug reported:
The 'Cheese' application states "no device found". This problem has
happened before. It seems like sometimes system updates fix the issue;
however, the most recent update seems to have re-broken the webcam.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: webcam (not
*** This bug is a duplicate of bug 1966418 ***
https://bugs.launchpad.net/bugs/1966418
Public bug reported:
When I navigate to Settings / Online accounts and try to add a Google,
Microsoft or Flickr-account the pop-up screens remains blank. Other
accounts are fine.
I'm using IUbuntu 22.04
For someone who is still struggling with this,
https://forum.snapcraft.io/t/experimental-flag-for-hiding-snap/28509 may help.
It seems that
sudo snap set system experimental.hidden-snap-folder=true
works and puts data in ~/.snap/data, but snap still creates an empty ~/snap on
app startups.
--
Test results for 510 are available at
https://docs.google.com/spreadsheets/d/1VjZ1Jx9vuQPFtmTU-r9hJYDWlrA5dyopHQfQ9LWitlg/edit?usp=sharing
Test results for 390 are available at
https://docs.google.com/spreadsheets/d/1hZrugw1J2oNKFf4ZZzhBE5wmE1HWjZGSOqk6Llt_0ZM/edit?usp=sharing
No regression
You don't consider a lack of documentation of how to connect to a basic
hotel WiFi that every other operating system can connect to a short-coming
in your documentation or product? I have been programming for fun and
profit since 1979. I built BSD Unix systems from source in the 1980's. I
am
Copy/paste works for me, but drag/drop does not. I can't even rearrange
tabs or bookmarks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1947210
Title:
Firefox Snap can't copy or drag in Wayland
** Description changed:
[Reproduce step]
1. install ubuntu-22.04 beta.
2. run "apt update" and "ubuntu-driver install"
3. reboot the system.
[Expected result]
system should boot into desktop.
[Actual result]
system stuck in boot stage and monitor keeps blinking.
** Description changed:
[Reproduce step]
1. install ubuntu-22.04 beta.
2. run "apt update" and "ubuntu-driver install"
3. reboot the system.
[Expected result]
system should boot into desktop.
[Actual result]
system stuck in boot stage and monitor keeps blinking.
Public bug reported:
[Reproduce step]
1. install ubuntu-22.04 beta.
2. run "apt update" and "ubuntu-driver install"
3. reboot the system.
[Expected result]
system should boot into desktop.
[Actual result]
system stuck in boot stage and monitor keeps blinking.
please see the attachment.
Public bug reported:
I am at a Marriott Hotel and cannot connect to the open WiFi on
Ubuntu20. The re-direct url they are using is complicated and the usual
tricks (which one does not have to use to connect using Windows, Macs or
Android) including http://, etc. do not work.
The redirect looks
I tried glxgear before, it will use nvidia-driver, I can see it by nvidia-smi.
Since we define our test scope using firefox to check, so I report this bug.
Or should I add firefox as impacted package and remove linux package.
--
You received this bug notification because you are a member of
** Summary changed:
- Jammy didn't use nvidia driver whne executing firefox
+ Jammy didn't use nvidia driver when executing firefox
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967456
Title:
Public bug reported:
[Reproduce step]
1. Install Jammy beta.
2. Install Nvidia driver by ubuntu-driver install.
3. Connect monitor to dGPU output port.
4. Run firefox, type "about:support" in url, and check column "GPU #1"
[Expected result]
should see nvidia driver info.
[Actual result]
** Also affects: gnome-shell
Importance: Undecided
Status: New
** No longer affects: gnome-shell
** Also affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
This video shows that what I observed.
** Attachment added: "IMG_6015.mp4"
https://bugs.launchpad.net/ubuntu/+source/xwayland/+bug/1967452/+attachment/5575459/+files/IMG_6015.mp4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
[Reproduce steps]
1. Install jammy beta.
2. Install nvidia-driver by ubuntu-driver install
3. Suspend the system by clicking the button at the upper right corner.
[Expected result]
Should re-enter to desktop.
[Actual result]
Screen keep blinking and don't show the
Public bug reported:
i turned my computer on and the touchpad wasnt working. It doesnt recognize any
input.
hp pavilion x360 convertible model 14dy-0022ns
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.13.0-35-generic 5.13.0-35.40~20.04.1
ProcVersionSignature: Ubuntu
Public bug reported:
When I enable the web service in Kodi and open it in a browser, it
fails:
Loading failed for the
Please find test results at
https://docs.google.com/spreadsheets/d/1VtJNgxFU4sO8foPgzP2Q-g-flo2sSELecOJnS9pGKXM/edit?usp=sharing.
No regressions were found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks for the solution. I removed "nomodeset" from grub config and now
it detects external monitor.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1961596
Title:
Ubuntu 20.04 with kernel version
Public bug reported:
Graphics option in About pane shows "llvmpipe (LLVM 12.0.0, 256 bits)"
$ lspci | grep -E 'VGA|Display'
00:02.0 VGA compatible controller: Intel Corporation UHD Graphics (rev 05)
$ glxinfo -B
name of display: :1
display: :1 screen: 0
direct rendering: Yes
Extended renderer
According to test result at
https://certification.canonical.com/hardware/202002-27718/submission/245770/test-results/pass/?term=media.
This problem has been solved.
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because
Also same issue with Asus PN50 Ryzen 5 4500U Bios 0623 (latest Bios) and
Mint version 20.3
Everything fine using version 5.11.0.46 but can't shut down/restart with
5.13.0.25 (even after waiting over ten minutes). sudo shutdown -h now
also doesn't work. Seems to reach (message) [OK] Reached Target
** Also affects: stress-ng (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/1929788
Title:
Some machines failed in stress-ng test on hirsute
To
@Alex
an update for this issue:
I just tested running fwts with --s3-sleep-type=s3, it can resume normally,
and I heard from Kent Lin and SWE member, dell's laptop don't support s3 for
now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
@Alex, @Ivan
There are some systems' default sleep mode is deep.
Maybe I can ask @sylvain comment on this issue, for the fix is
appropriate to land in checkbox or not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Ivan,
I just asked KC, he said if default sleep type is s2idle, it should test
with s2idle.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956914
Title:
Can't resume from suspend on some specific
That means if I don't use --s3-sleep-type=s2idle, fwts will test with
s3.
What I can see is most of systems can wake from s3, only 4 systems can't
for now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Alex,
I use dell system(202001-27665) to test your step.
1.default sleep type is [s2idle] deep
2.use rtcwake to trigger a sleep, and dmesg shows the message ""PM:
suspend entry (s2idle)"
3.if force fwts use s2idle, system can wake.
there is additional information, if I use fwts-21.09 on
Public bug reported:
Asking to burn from a browser fails.
Invoking as root: xfburn -i reports a seg fault (core dumped) but I don't see a
dump
I'm attaching the output of strace on the above command
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xfburn 0.6.2-1
ProcVersionSignature:
** Changed in: fwts (Ubuntu)
Assignee: (unassigned) => Alex Hung (alexhung)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1956914
Title:
Can't resume from suspend on some specific systems
** Changed in: fwts
Status: New => Confirmed
** Also affects: fwts (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/1956914
Title:
Can't
Public bug reported:
g++ 9.3.0-17ubuntu1~20.04 miscompiles the following example for x86
(bar_stdcall should pop 4 bytes fewer than an bar_cdecl, as stdcall is
callee-cleanup for the argument). To see it in this minimized example
one must use `-O0` as it will otherwise be inlined and the calling-
Test results for 495 are available at
https://docs.google.com/spreadsheets/d/14Kc4yMyGIqUr6oMGzqddlVcMMoY4qpq99crILaH58Os/edit?usp=sharing
Test results for 470 are available at
https://docs.google.com/spreadsheets/d/1kAo_Y8LFIDYY6skpkPGDCrNErG8-rN_ziQ0eJwmYDZ4/edit?usp=sharing
No regression were
Public bug reported:
I installed Ubuntu 21.10 on my laptop (Lenovo Yoga Slim 14 ARE 05 - AMD
Ryzen 4700 - 1ยง GB RAM - 512 GB SSD). Every time I close the lid or let
the laptop go to suspend the system doesn't resume. Clicking the mouse
or pushing the keys doesn't resume the OS.
The only way to
Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1745098
Likely caused by this change:
https://bugzilla.mozilla.org/show_bug.cgi?id=1737068
** Bug watch added: Mozilla Bugzilla #1745098
https://bugzilla.mozilla.org/show_bug.cgi?id=1745098
** Bug watch added: Mozilla Bugzilla
** Description changed:
I have a couple of ThinkPads with old Intel GMA X4500 graphics. Since
- the update to Firefox 95, it's been verry laggy; especially noticeable
+ the update to Firefox 95, it's been very laggy; especially noticeable
while scrolling, for instance on about:support.
I have also tested the tarball releases from
https://www.mozilla.org/firefox/
The problems are identical with those releases. I tested 94.0.2, 95.0,
96.0b2 and 97.0a1.
I ran all of them with `MOZ_ENABLE_WAYLAND=1`.
94.0.2 works perfectly fine, and all the other releases show lag while
1 - 100 of 9194 matches
Mail list logo
