Maybe start by removing the package 'sabily-gdm-themes'
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1972080
Title:
GNOME (non-Ubuntu) login screen mouse cursor is a
The photos in comments #12 and #13 show the Ubuntu Yaru theme is not
being used (missing the logo aside from this cursor bug), so it makes
some sense if whatever theme that is requires more of Adwaita than
regular Ubuntu does.
** Summary changed:
- [mgag200] Mouse cursor is a semi-opaque white
You have been subscribed to a public bug:
Do not think this is hardware dependent, but I'm using an HPE
MicroServer Gen10 Plus.
I installed the server edition of 22.04. Post-Installation, I added
some desktop environments. After logging in, these are working fine.
However on the gdm login
Thanks for the bug report.
This sounds like a hardware problem, most likely just new batteries are
required.
Wired mice or wireless with a dongle use the same code paths so clearly
that's working for some mice. I don't think there's any software bug
here.
** Package changed: xorg (Ubuntu) =>
This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1
---
gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium
* Merge with Debian. Remaining change:
- Lower gnome-control-center dependency to 41
gnome-remote-desktop (42.1.1-2) unstable;
This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1
---
gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium
* Merge with Debian. Remaining change:
- Lower gnome-control-center dependency to 41
gnome-remote-desktop (42.1.1-2) unstable;
This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1
---
gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium
* Merge with Debian. Remaining change:
- Lower gnome-control-center dependency to 41
gnome-remote-desktop (42.1.1-2) unstable;
This bug was fixed in the package gnome-remote-desktop - 42.1.1-2ubuntu1
---
gnome-remote-desktop (42.1.1-2ubuntu1) kinetic; urgency=medium
* Merge with Debian. Remaining change:
- Lower gnome-control-center dependency to 41
gnome-remote-desktop (42.1.1-2) unstable;
*** This bug is a duplicate of bug 1961508 ***
https://bugs.launchpad.net/bugs/1961508
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1961508, so it is being marked as such. Please
Thanks for the bug report.
Screen tearing during mode changes is somewhat normal. Even more normal
and even more visible in VMs. If that's the only problem then this may
not really be a fixable bug. But I am only guessing. Please provide a
video of the issue so we can confirm.
** Package
Nick,
Please look at https://errors.ubuntu.com/user/ID where ID is the content
of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any
links to recent problems on that page? If so then please send the links
to us.
Please also reproduce the bug again and as soon as it happens run:
I would have thought Firefox was using GTK3 still like most non-GNOME
apps(?)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
https://bugs.launchpad.net/bugs/1972984
Title:
Cannot paste filename into File Save dialog
Please try selecting 'Ubuntu on Xorg' on the login screen.
Please also upgrade to Ubuntu 22.04 as soon as you can.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1973143
Title:
Invalid then I suppose.
** Changed in: mutter (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1972749
Title:
Logging into a second Wayland
This bug is closed.
But screen sharing is expected to be broken on Chromium+Wayland due to
bug 1897454.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1950040
Title:
I would mark this as a duplicate of bug 1967488 had you said "black"
instead of "transparent". But I guess they could still both be the same
issue.
** Tags added: jammy nvidia nvidia-wayland wayland wayland-session
--
You received this bug notification because you are a member of Desktop
** Tags added: nvidia nvidia-wayland
** Tags added: jammy
** Tags added: wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1967488
Title:
Chromium stable snap
Please try selecting the Xorg option on the login screen. It will either
be called 'Ubuntu on Xorg' or just 'Ubuntu'.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1970291
Title:
** Package changed: linux (Ubuntu) => joystick (Ubuntu)
** Changed in: joystick (Ubuntu)
Status: Confirmed => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to joystick in Ubuntu.
https://bugs.launchpad.net/bugs/1973216
Title:
You have been subscribed to a public bug:
What I expected to happen:
I plug in Saitek Cyborg Evo Force joystick, run ffmvforce or ffcfstress and can
adjust the force-feedback.
What happenend instead:
No force-feedback at all.
ffcfstress raises error "ERROR: device (or driver) has no constant
We will be manually applying 7836.
** Changed in: freerdp2 (Ubuntu Jammy)
Status: In Progress => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to freerdp2 in Ubuntu.
https://bugs.launchpad.net/bugs/1973229
Title:
Update
To provide some context, when this crash can happen: It can happen, after
attempting to start a remote desktop session, when the screen is locked.
In such case, g-s directly refuses the start request and therefore the lifetime
of the rdpgfx thread in FreeRDP is very short.
The journal message
Please provide a progress report on testing and validation of this
package. Meanwhile, upstream released version 101.0.4951.64 for Linux
(version 101.0.4951.67 was only released for Windows).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Note: 2.7.0 does **NOT** contain https://github.com/FreeRDP/FreeRDP/pull/7836
(which should fix
https://bugs.launchpad.net/ubuntu/+source/gnome-remote-desktop/+bug/1970994),
because 2.7.0 was released before that MR was created and merged.
So you have to either apply
** Description changed:
Impact
==
The cheese app is unusable with color bands showing in the main view.
+ This bug doesn't affect all webcams. It's unknown what percentage of
+ webcams are affected.
+
Test Case
+ On a system that experiences this bug:
Install the
Sure! I'll do it.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to transmission in Ubuntu.
https://bugs.launchpad.net/bugs/1973084
Title:
transmission-daemon high RAM usage
Status in transmission package in Ubuntu:
Incomplete
Bug
I have installed the updated packages and restarted. Evolution and GNOME
Calendar both still work fine.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Tags added: oem-priority
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cheese in Ubuntu.
https://bugs.launchpad.net/bugs/1967843
Title:
cheese display corrupted under Ubuntu 22.04
Status in Cheese:
Unknown
Status in OEM
*** This bug is a duplicate of bug 1967843 ***
https://bugs.launchpad.net/bugs/1967843
** This bug has been marked a duplicate of bug 1967843
cheese display corrupted under Ubuntu 22.04
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Description changed:
- The cheese application produces a corrupted display under Ubuntu 22.04
- with a Logitech C525 webcam. When started from the command line, cheese
- produces repeated warnings of the form...
+ Impact
+ ==
+ The cheese app is unusable with color bands showing in the
** No longer affects: cheese (Ubuntu Jammy)
** Changed in: clutter-gst-3.0 (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: clutter-gst-3.0 (Ubuntu Jammy)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages patched for CVE-2020-35522, CVE-2022-0561, CVE-2022-0562,
CVE-2022-0865 and CVE-2022-0891 are available for Bionic, Focal and
Impish at https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa. (Impish is not affected by
CVE-2020-35522.)
Please patch the other CVEs and
Public bug reported:
What happens:
Wireless mouse shows up under `lsusb` list but doesn't control the
cursor.
Expected behavior:
The mouse controls the cursor.
Background:
I purchased a "Mini 2.4 GHz Wireless Optical Mini Finger Mouse Mice For
Laptop PC Computers"
** Changed in: firefox (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1970989
Title:
missing a tightly integrated deb package without snap
** Changed in: tiff (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to tiff in Ubuntu.
https://bugs.launchpad.net/bugs/1971001
Title:
Multiple vulnerabilities in Trusty, Xenial, Bionic,
** Also affects: xdg-utils (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: xdg-utils (Ubuntu Jammy)
Status: New => Confirmed
** Changed in: xdg-utils (Ubuntu Jammy)
Assignee: (unassigned) => Olivier Tilloy (osomon)
** Changed in: xdg-utils (Ubuntu Jammy)
I am linking to a GTK4 bug. I'm not sure if the GTK4 bug is the same as
the xdg-desktop-portal-gnome issue but the GTK4 bug would need to be
fixed first anyway.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk4 in Ubuntu.
Because this affects more than just Firefox, I am removing the Firefox
task.
I wasn't able to reproduce this bug if I did these steps:
sudo apt uninstall xdg-desktop-portal-gnome
Log out and log back in
Now, snaps will use xdg-desktop-portal-gtk instead.
Therefore, I believe this is a bug in
** Description changed:
Impact
--
+ This is a new stable release in the GNOME 42 series.
- Test Case
- -
+ It has one bugfix: an annoying error message that can be seen in apps like
the Telegram snap when trying to save a file.
+
** Changed in: gnome-remote-desktop (Ubuntu)
Status: Triaged => Fix Committed
** Description changed:
Impact
--
The gnome-remote-desktop systemd user service is always running.
This was a contributing factor for LP: #1971415
Although it's "harmless" for the user
This bug may be mutter/wayland related as the player seems to work in
xorg but not wayland.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to totem in Ubuntu.
https://bugs.launchpad.net/bugs/1969512
Title:
Totem unable to play video:
This bug was fixed in the package xdg-utils - 1.1.3-4.1ubuntu2
---
xdg-utils (1.1.3-4.1ubuntu2) kinetic; urgency=medium
* Cherry-pick an upstream merge request to remove bashisms from xdg-settings
(LP: #1970594)
- debian/source/options
-
Public bug reported:
Impact
--
Ubuntu 22.04 LTS includes basically a git snapshot of freerdp2 as of April 11.
freerdp 2.7.0 was released April 25 with a few more bug fixes.
Also, this includes patches that the upstream gnome-remote-desktop
maintainers believe fix LP: #1970994 I am not
modinfo nvidia-drm
modinfo: ERROR: Module nvidia-drm not found.
modinfo nvidia_drm
modinfo: ERROR: Module nvidia_drm not found.
modinfo nvidia
filename:
/lib/modules/5.4.0-110-generic/kernel/drivers/char/drm/nvidia.ko
inxi -G
Graphics: Device-1: NVIDIA GT218 [GeForce 210] driver:
In our situation home folders are mounted using autofs using NFS v4,
Kerberos is NOT in use.
root@jammy:~# lsb_release -rd
Description:Ubuntu 22.04 LTS
Release:22.04
root@jammy:~# dpkg -l chromium-browser
--snip--
ii chromium-browser 1:85.0.4183.83-0ubuntu2 amd64
Thanks for your report.
This is a design matter and should better be reported upstream:
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues
If you report it there, please post the URL to the upstream issue here
for tracking purposes.
P.S. Good that you figured out how to set it via
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
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
Public bug reported:
I use the same monitor 1440p, keyboard and mouse connected via HDMI to
older MacBook Pro and dual boot Laptop (Ubuntu + Win10) with Hybrid
graphics Intel 630HD and GeForce 1050Ti.
*** This bug is a duplicate of bug 1970291 ***
https://bugs.launchpad.net/bugs/1970291
This is probably a duplicate of:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1970291
** Summary changed:
- NVIDIA: Laggy mouse movement on external monitor
+ Wayland/Hybrid/NVIDIA: Laggy mouse
I can't confirm that the description matches my issue but maybe it is
the same. So here is my own description:
I use the same monitor 1440p, keyboard and mouse connected via HDMI to
older MacBook Pro and dual boot Laptop (Ubuntu + Win10) with Hybrid
graphics Intel 630HD and GeForce 1050Ti.
** Description changed:
Impact
--
There is a new point release in the stable GTK 4.6 series.
https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.3/NEWS
Also, we are cherry-picking a few patches
- Work around infinite loop in box allocation (Closes: #1010547)
- Make it easier to
Public bug reported:
Impact
--
There is a new point release in the stable GTK 4.6 series.
https://gitlab.gnome.org/GNOME/gtk/-/blob/4.6.3/NEWS
Also, we are cherry-picking a few patches
- Work around infinite loop in box allocation (Closes: #1010547)
- Make it easier to select the current
but it doesn't show in your lsmod.
how about `modinfo nvidia_drm`?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: snapd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
Sorry, this is a WONTFIX for Ubuntu 22.04 LTS. Ubuntu 22.04 LTS uses
gnome-control-center 41 which doesn't support setting a theme at all,
except in an Ubuntu-specific patch. If you want the Ubuntu experience,
use the Ubuntu session. If you want the GNOME experience, use the GNOME
session but then
Upstream issue is: https://gitlab.xiph.org/xiph/vorbis/-/issues/1975
and the solution is the commit:
https://gitlab.xiph.org/xiph/vorbis/-/commit/42f2bb2936ea06e3a9a2fc2260988120d6dfc97d
the '--advanced-encode-option disable_coupling' in oggenc is used on
autopkgtests for libvorbis.
so, in
This bug was fixed in the package libvorbis - 1.3.5-3ubuntu0.2+esm1
---
libvorbis (1.3.5-3ubuntu0.2+esm1) xenial-security; urgency=medium
* SECURITY UPDATE: Out-of-bounds access
- debian/patches/CVE-2017-14160_CVE-2018-10393-1.patch: add boundaries
check in
Hi,
I do not remember blacklisting nvidia-drm intentionally, but will check !
Anyway don't you think this line from journalctl:
kernel: [drm] Initialized nvidia-drm 0.0.0 20150116 for :01:00.0 on minor 0
indicates nvidia-drm is fine ?
Running Mint 20.3 still with kernel 5.4 if that matters
update:
no transition plan for nvidia-340.
Then let's see why your nvidia-drm gone.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg]
** Package changed: nautilus (Ubuntu) => gtk4 (Ubuntu)
** Changed in: gtk4 (Ubuntu)
Importance: Low => High
** Changed in: gtk4 (Ubuntu)
Status: Incomplete => Confirmed
** Summary changed:
- File save/download from all browsers fails to save when file name box is not
active.
+
Public bug reported:
The Legacy version is nvidia-390 and will become nvidia-470.
The nvidia-340 is not longer support.
Use this kind of non-support version will likely conflict with newer
design (e.g. from u-d-c, gdm).
Please going to remove it.
** Affects: nvidia-graphics-drivers-340
My Chromium 101.0.4951.54 on 22.04 cannot share screen in Big Blue
Button – the shared image ist just black with the mouse pointer.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu.
Hello Timo, or anyone else affected,
Accepted mesa into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/mesa/22.0.1-1ubuntu2.1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
We should review how the package works but meanwhile the udev rules
change is going to resolve the conflict
** Description changed:
+ * Impact
+
+ The brltty udev rules are claiming generic devices IDs which makes some
+ other devices like Arduino cards not able to interact with the serial
+
Hi,
@Daniel van Vugt (vanvugt), I give you a report.
I have been rebooted my laptop and repeated the problem again, but I
didn't find a file *.crash in /var/crash directory. Apparently, the
problem is not crash (it's my opinion), because Operation System does't
show error messages on my screen,
Thanks Samuel, I've uploaded the changes now.
I also checked a bit the package history since I'm not really familiar
with the package (we used to have Luke working on accessibility but
since he left we mostly carried the status over and don't have anyone
really familiar those changes) and it
ok, I aware the `nvidia-drm` should support in nvidia-340.
Did you blacklist it?
Can you check the nvidia-drm whether presenting in your system?
you could probably found it under
find ... /lib/modules/$(uname -r)/...
--
You received this bug notification because you are a member of Desktop
Hi,
I aware you don't have "nvidia_drm" which is needed for gdm as well.
u-d-c was wait the "nvidia_drm" be probed and your nvidia driver is 340 is
quite old as what I known.
FWIK, the legacy driver should be nvidia-390 and the next is 470.
I wondering why nvidia-340 is not yet be transited to
** Changed in: webkit2gtk (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to webkit2gtk in Ubuntu.
https://bugs.launchpad.net/bugs/1967020
Title:
WebKitWebProcess crashed with SIGSEGV
Still having upload trouble, i'll find a way to get a crash-report
through another means
** Attachment added: "upload failure crash report"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1972812/+attachment/5589244/+files/Screenshot%20from%202022-05-12%2008-47-13.png
--
You
An additional data point; I noted in the linked gitlab bug a couple of
messages noting that "it works with the flatpak". Out of curiosity (as
to whether this might be a well and truly arm64 specific problem), I
tried the flatpak on the pi desktop and: it's got exactly the same
problem (same
*** This bug is a duplicate of bug 1958224 ***
https://bugs.launchpad.net/bugs/1958224
** This bug has been marked a duplicate of bug 1958224
brltty claiming cp210x devices on 22.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
*** This bug is a duplicate of bug 1958224 ***
https://bugs.launchpad.net/bugs/1958224
** This bug has been marked a duplicate of bug 1958224
brltty claiming cp210x devices on 22.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
reopening for snapd since it seems it's not firefox specific and still
an issue
** Changed in: snapd (Ubuntu)
Status: Fix Released => New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
I removed one of the extensions i was using, but still am running into
the issue.
1) I've got a crash report that still fails to upload.
```
-rw-r- 1 addyess whoopsie 94220558 May 12 08:03
_usr_bin_gnome-shell.1000.crash
-rw-rw-r-- 1 addyess whoopsie0 May 12 08:03
for me at least the workaround is working as expected .. But I think it's
something that has to be fixed as soon as possible.. the no use of vaapi gets a
browser that is not smooth and freezes with almost every playback or preview...
firefox is a lot worse since 98 version in my opinion for
Created attachment 9275655
firefox100_crash.log
Hello. Just to add in that this issue at least for my setup (Arch Linux,
Firefox 100) is still current.
The previous comment suggest the problem might lie with the decoder but
no other software on my machine has problem decoding through vaapi at
Public bug reported:
One interesting note is that under system monitor, it shows the process
as having 99 GB of virtual memory.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libwebkit2gtk-4.1-0 2.36.0-2ubuntu1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux
This bug was fixed in the package libreoffice - 1:7.3.3-0ubuntu0.22.04.1
---
libreoffice (1:7.3.3-0ubuntu0.22.04.1) jammy; urgency=medium
* New upstream release (LP: #1971670)
-- Rico Tzschichholz Thu, 05 May 2022 11:06:56
+0200
** Changed in: libreoffice (Ubuntu Jammy)
The verification of the Stable Release Update for libreoffice has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
Public bug reported:
After using the session for a while with a normal workflow like switching
opened windows etc.
Some app windows's dimensions are changed automatically from the left side and
appears behind the dock as shown in the screenshot.
To correct it, the window must be resized and
After further investigation, I found the source of my issue.
Basically the / directory had the wrong ownership. Not sure how I did
that but it seemed to have the side-effect of making systemd-tmpfiles
not create directories as it should.
I saw messages like this in the log that clued me in.
Just checking in again :) The description of this report talks about
Focal, but I only see Jammy in the affected list?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1958673
The unit change mentioned before wasn't the right reference,
http://launchpadlibrarian.net/449200364/rygel_0.38.1-2ubuntu3.1_0.38.1-2ubuntu3.2.diff.gz
is a better example
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Unfortunately we've tried "G_DEBUG=fatal_warnings" before (you suggested
it back in comment:4) but I did manage to figure out a couple of things
since last time:
The crash I originally observed (back in comment:6) only occurs on the
very first run of totem. All subsequent runs (even after a
*** This bug is a duplicate of bug 1971516 ***
https://bugs.launchpad.net/bugs/1971516
** Changed in: nautilus (Ubuntu)
Status: Incomplete => New
** This bug has been marked a duplicate of bug 1971516
File save/download from all browsers fails to save when file name box is not
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1972079
Title:
Switching "High Contrast" on
It's the external monitor which is facing issue.
On Thu, 12 May 2022, 2:05 pm Daniel van Vugt, <1973...@bugs.launchpad.net>
wrote:
> Also which monitor is displaying the wrong resolution?
>
> ** Summary changed:
>
> - monitor resolution issue
> + Wayland session limited to 1024x768
>
> **
Thanks. It kind of looks like the Nvidia driver is directly aware of the
USB-C/Thunderbolt port. So maybe it's not surprising then that the order
of connection matters.
For now that suggests the bug is somewhere between the Nvidia driver and
the kernel.
** Package changed: xorg-server (Ubuntu)
Public bug reported:
This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. The host system specs
are the same as here:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150
At step 24, when I click the "Restart now"
> it's a bit unclear to me which entries there should be considered
'generic USB IDs'?
They are marked "Generic Identifier", that's
0403:6001
10C4:EA60
10C4:EA80
> I also don't understand why those rules are debian specific
See the diff between ./debian/brltty-udeb.udev.rules and
Before reboot I had:
* Laptop internal monitor on
* Samsung 34" external monitor on, with USB-C
* Aces 24" external monitor on, with HDML
Rebooted without changing anything.
* The Samsung 34" / USB-C connected external monitor did _not_ come to life.
* The Acer 24" / HDMI second external
Public bug reported:
This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. I'm using the same
host system specs as in this bug report:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1973150
While running the test, in
@Samuel so I was checking debian/brltty.udev.rules following your
suggestion, but it's a bit unclear to me which entries there should be
considered 'generic USB IDs'?
I also don't understand why those rules are debian specific. How does
upstream handle the devices?
We should stop installing
I've got it working one more time.
* Disconnected the HDMI.
* Rebooted - with USB-C to the monitor connected.
* The external monitor did not register.
In addition to the monitor a Lenovo network adapter (8P8C for
CAT5/CAT6/..) is connected.
I tailed /var/log/syslog and /var/log/kern.log
I kept
Public bug reported:
This bug was discovered while doing an Ubuntu QA test, "Install (entire
disk with lvm and encryption)" for Ubuntu Kinetic. I'm doing this within
a virtual machine - the host OS is Ubuntu Studio 21.10 running on an HP
Z220 SFF Workstation, UEFI, no secure boot, 16 GB of RAM,
Also confirmed. That fixed my problem. I am back to 22.04 Thanks jorge.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-openvpn in Ubuntu.
https://bugs.launchpad.net/bugs/1969274
Title:
openvpn client no longer
If you are using a USB-C dock then please see bug 1970495.
Otherwise if you think the USB-C port might be wired directly to the
Nvidia GPU then please see bug 1960865.
When the bug occurs next please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the
1 - 100 of 118 matches
Mail list logo
