Thanks for your response. I can confirm that the problem does not happen
with Ubuntu 24.04. It does happen with 23.10.1 and below.
I'm not sure about filing a bug report with Mozilla. I think they'll
blame it on the Ubuntu modifications because the bug doesn't happen on
any version of Debian,
I've been testing all these packages since last Monday, and this morning
night light was stuck again when I unlocked my screen. So I'm afraid
this doesn't fix the issue.
I also haven't seen any activity in the upstream ticket of people
actually confirming the issue was fixed.
** Tags removed:
Public bug reported:
I'm trying to clone an EXT4 partition on a Linux software RAID
I'm using the command line
partclone.ext4 --clone --source=/dev/md1p1 --output=testout
when the relevant part of 'lsblk' output is
sda 8:00 16.4T 0 disk
└─md1 9:10 32.8T 0
The oracular archives already contain gnome-calculator 46.1 as a .deb
package. I've installed that on noble without issues, and I can confirm
that also fixes this issue.
So if that package is copied to the noble archives, this bug will be
fixed.
--
You received this bug notification because you
Upstream says this is fixed in gnome-calculator 46.1. I've just tested
the Flatpak of that version, and can confirm that it indeed is fixed in
the next point release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
A new upstream version (1.5.0) was released on 2021-10-28:
https://github.com/zevv/bucklespring/releases
** Affects: bucklespring (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
)
Status: New => In Progress
** Changed in: linux (Ubuntu Noble)
Assignee: (unassigned) => Kevin Becker (kevinbecker)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2033007
Title:
I have installed the mutter package from noble-proposed and rebooted, so
I'll be testing it from now on.
kevin@arcadia:~$ mutter --version
mutter 46.2
Sadly I don't know of any way to manually trigger this bug. Sometimes it
doesn't happen for days, and then all of a sudden the colour temperature
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2072370
Title:
URL for home page and privacy policy point to a dead site
To
@Dave, I didn't see anything displayed on the monitor with core20.
Only see there is a fixed pattern on ACT LED, 4 long flashes first, followed by
7 short flashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Dave, the current focal server image originally can boot on the rev 1.4
rpi3b+, but core20(https://cdimage.ubuntu.com/ubuntu-
core/20/stable/current/) can't, so how do I verify the new firmware
works?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "journal log"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2070319/+attachment/5792126/+files/journal.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2070319
Title:
Public bug reported:
I'm conducting the nvidia driver SRU testing, during test this version
on Focal, I found one of laptop can't perform auto-login after
installing this driver.
[Reproduce]
1. Install ubuntu 20.04
2. Run dist-upgrade to update all the packages.
3. Enable proposed pocket
4.
** Attachment added: "lspci.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2069550/+attachment/5790121/+files/lspci.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069550
Title:
Public bug reported:
During the SRU testing for 5.15.0-112 kernel on Focal, I found 2 AMD laptops
displayed a black screen.
After some investigation, the impacted laptops both with Picasso/Raven
2(1002:15d8) GPU.
Output for lscpi and journalctl are attached.
If you need more detail, please let
** Changed in: linux (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2069400
Title:
Some DUTs can't boot up after installing the hwe kernel in the
Public bug reported:
During the SRU testing for 5.15.0-112 kernel, I found some machines freeze at
very early stage of booting process.
The last messages displayed on the screen are:
Loading Linux 5.15.0-112-generic...
Loading initial ramdisk...
It looks like it's very similar to this bug.
Hi Colin, I've consistently reproduced this issue in QEMU VMs on arm64
realtime (6.8.1.1002-realtime). However, it also occurs with the generic
kernel (6.8.0-35-generic) on arm64. I couldn't get it to happen with
amd64.
Here's the dmesg output on 6.8.0-35-generic after the modprobe gets
stuck:
[
To be clear, so far I've only been able to get the following hardware
configurations to fail reliably:
- QEMU VM amd64, linux-realtime 6.8.1-1002-realtime
- QEMU VM amd64, linux (generic) 6.8.0-35-generic
I once got each of the following to fail, but haven't been able to
reproduce it
Hi Colin, I've been able to reproduce this issue in QEMU VMs on amd64
consistently and I got it to happen once in arm64, however, I haven't
been able to reproduce the kernel oops again. I can't get it to happen
on bare metal or in an LXD VM (multipass). I've also found that this
doesn't just
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2059259
Title:
ubuntu_ltp
** Package changed: linux (Ubuntu) => ubuntu-realtime
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2068615
Title:
kernel oops in pick_next_task_fair in 6.8.1-1002-realtime kernel
To manage
/report.BUG_ID linux
If apport can't be run:
1) uname -a > uname-a.log
2) dmesg > dmesg.log
3) sudo lspci -vvnn > lspci-vvnn.log
4) cat /proc/version_signature > version.log
Thanks,
Kevin
** Changed in: linux-realtime (Ubuntu)
Status: New => Triaged
** Changed in: linux-r
Public bug reported:
```
GNU Image Manipulation Program version 2.10.36
git-describe: GIMP_2_10_36
Build: unknown rev 0 for linux
# C compiler #
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-linux-gnu/13/lto-wrapper
Public bug reported:
Unable to calculate upgrade use ppa-purge - removed ppa file from other
software then tried to upgrade again ans till get unable to calculate
upgrade and to report the bug in the summary - have submitted bug report
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package:
Public bug reported:
Since installing Ubuntu 24.04, every now and then Night Light gets stuck
when my screen is locked at night and I unlock it in the morning. The
screen is then very orange (more so than normally is the case with Night
Light), and disabling it with the button in in the top bar
This happens with nl_NL.UTF-8 for me as well. The period is no longer
converted to a comma, as it used to be in older gnome-calculator
releases.
This seems to be the upstream bug: https://gitlab.gnome.org/GNOME/gnome-
calculator/-/issues/403
** Bug watch added:
Further research indicates that `webkit2gtk-4.0` is legacy and removed
on purpose, which I fully understand, and bringing it back might not be
a practical operation.
My project (GlobalProtect-openconnect) uses Tauri 1.x, which depends on
`webkit2gtk-4.0`. Tauri started to use `webkit2gtk-4.1` in
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
1 - 100 of 9459 matches
Mail list logo