with old pool (missing right modules)
1. offline install "succeeds" but doesn't install any nvidia stuff in
target, no errors otherwise.
2. online install "stalls", generates crashreport pop-up (failing to
install lowlatency).
Possible workarounds:
- fix ubuntu-drivers to detect kernel flavour
@esjrac, you wrote in the duplicate Bug #1874017 that the issue occurs
for you under Wayland as well. Can you repro this also in the tablet
mode of the foldable devices that you mentioned there?
I am asking because for me this occurs under Wayland only if the devices
are laptop mode. In tablet
I have the similar issues with USB detection after upgrade to Ubuntu 20.04 on
my scanners (HP Laser MFP 135a - smfp backend and HP OfficeJet 4630 - hpaio
backend).
WIth
The hpaio scanner is detected on USB, but it is not able to communicate
(xsane, scanimage, simple-scan). Only scanning by
Thanks, indeed it's an usability issue. It's late now to have the fix in the
release but we plan to do a SRU with pending fixes soon and the change should
be included
Marco, I'm assigning to you since you said you were planning to do that SRU
** Changed in: gnome-shell-extension-ubuntu-dock
Thanks, updating the title according. Also keeping at low since it's not
our recommended session
** Summary changed:
- gnome-screenshot takes a screenshot of the wrong screen
+ [wayland] gnome-screenshot takes a screenshot of the wrong screen
--
You received this bug notification because you
IMHO it is hard to decide. The problem remains: the chromium processes are
lurking in the background and there is no control any more. As I stated in my
report there is probably still the system tray icon however there is no control
together with this icon. Also the system tray concept is a
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
*** This bug is a duplicate of bug 1866556 ***
https://bugs.launchpad.net/bugs/1866556
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Hi Hans de Goede,
Thank you very much for your information.
I were able to install OpenSSH server, however I don't know how to do
ssh in while it hangs.
Thank you in advance for your help.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Just to be clear: for that journalctl output, I did put the correct
passwords in because the VPN connection worked. The only problem is
that the network manager failed to save the password for the next time I
tried to use it.
--
You received this bug notification because you are a member of
The issue has been fixed upstream.
Hope it will land in focal.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in
Ubuntu.
https://bugs.launchpad.net/bugs/1873321
Title:
The Show Applications button
OK, I'm totally sure it's a freeze.
Moreover, gnome-shell stack trace looks normal, event loop runs just fine.
I can generate and provide core file if needed.
What I managed to debug so far, is that in case of multiple /dev/dri/cardX
being created
frame_cb in meta-stage-x11.c:296 is not called
Yes, I can confirm the bug happens only on Wayland.
Everything works fine under the standard "Ubuntu" session, or the "Gnome on
Xorg" session.
(I also noticed something strange under the "Ubuntu on Wayland" session,
wich might be related: I can screenshot the left dock and sometimes parts
the dock
Public bug reported:
some sounds are playing over the device (like sound the box makes when i
turn the volume to max)
but chrome sound output does not appear on bluetooth box
this appeard after i upgraded yesterday from 19.10 -> 20.04 via do-
release-upgrade
all pkg's are up to date
tried to
sha256 is now used instead of sha1 - this is probably as important as
the (yet unpublished) CVEs as it is seen as a breaking change by some
colleagues. The change is however only breaking for those that don´t
install trustworthy certificates.
--
You received this bug notification because you are
the log has a
/usr/sbin/vpnc: hash comparison failed: (ISAKMP_N_AUTHENTICATION_FAILED)
unsure if that has to do with the issue
** Changed in: network-manager (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Desktop
Packages, which is
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1860622
Title:
Dependency error installing
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1856691
Title:
libpulse-mainloop-glib0:i386 cannot
Thanks, closing that one, the remaining issue is bug #1870847
** Changed in: gnome-shell (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1861081
Title:
Dependency error installing
** Changed in: pulseaudio (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1858164
Title:
libpulse-dev needs a rebuild for
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Triaged
--
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/1870847
Title:
App grid has too many page dots on right
** Package changed: gtk+3.0 (Ubuntu) => ubuntu
** Changed in: ubuntu
Importance: Undecided => Low
** Changed in: ubuntu
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtk+3.0 in Ubuntu.
Confirmed I'm no longer seeing the tiny-icons thing, but still seeing
the pager issue, fully up to date.
--
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/1869737
Title:
App icons
This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu7.5
---
pulseaudio (1:11.1-1ubuntu7.5) bionic; urgency=medium
* Update snap policy to make access to audio recording conditional on
plugging the "pulseaudio" or "audio-record" interfaces (LP: #1781428):
-
This bug was fixed in the package pulseaudio - 1:8.0-0ubuntu3.11
---
pulseaudio (1:8.0-0ubuntu3.11) xenial; urgency=medium
* Backport the snap policy module to make access to audio recording
conditional on plugging the "pulseaudio" or "audio-record" interfaces
(LP:
hn23,
Can you please reproduce the crash and provide a fresh link to the crash
report you get? I want to see if we land here or on some other bug. If
you're not sure how to do that then some tips are here:
To avoid confusion I have also removed the syslog (Xorg log) from the
top of the bug. This is a crash in the Wayland backend (the login screen
for most people) and any messages from Xorg (Xwayland) are not related
to the original problem.
** Description changed:
[Impact]
gnome-shell
I'm also not sure switching keyboard layouts is related to the crash
that this bug reports. Maybe we have two different bugs confused... The
crash here looks more like it's related to Wayland display mode or
monitor layout changes.
--
You received this bug notification because you are a member
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-meta (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
Thank you for your bug report, it sounds a bit late now to include it
before release but should be a security update to at least fix the CVE
issues
** Changed in: freerdp2 (Ubuntu)
Importance: Undecided => High
** Changed in: freerdp2 (Ubuntu)
Status: New => Confirmed
--
You received
Thanks but it's not going to be for focal now
** Changed in: bubblewrap (Ubuntu)
Importance: Undecided => Wishlist
** Changed in: bubblewrap (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-drivers-common (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-meta in Ubuntu.
This bug was fixed in the package json-glib - 1.4.2-3ubuntu0.18.04.1
---
json-glib (1.4.2-3ubuntu0.18.04.1) bionic; urgency=medium
*
debian/patches/0001-json-gvariant-Stop-string-to-GVariant-conversion-fai.patch:
- Fix JSON to GVariant conversion failing sometimes (LP:
This bug was fixed in the package json-glib - 1.4.4-2ubuntu0.19.10.1
---
json-glib (1.4.4-2ubuntu0.19.10.1) eoan; urgency=medium
*
debian/patches/0001-json-gvariant-Stop-string-to-GVariant-conversion-fai.patch:
- Fix JSON to GVariant conversion failing sometimes (LP: #1871023)
*** This bug is a duplicate of bug 1857191 ***
https://bugs.launchpad.net/bugs/1857191
** Changed in: gedit (Ubuntu)
Importance: Undecided => Low
** This bug has been marked a duplicate of bug 1857191
Dark themes don't work well with highlighted current line in gedit
--
You received
could you ssh in and get a gdb backtrace while it's hanging?
--
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/1870278
Title:
Shell is unresponsive at the lock screen for ~10s after
The verification of the Stable Release Update for json-glib 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
Thanks, it looks right indeed
** Changed in: gnome-control-center (Ubuntu)
Status: New => Triaged
** 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
Thank you for your bug report. Is the issue specific to wayland? does it
work if you try under X?
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Triaged
** Changed in: gnome-screenshot (Ubuntu)
Status: Confirmed => Invalid
** Changed in: gnome-shell (Ubuntu)
This is an expected consequence of removing unity-menubar.patch in 20.04
(https://bazaar.launchpad.net/~mozillateam/thunderbird/thunderbird.focal/revision/528).
** Changed in: thunderbird (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => Triaged
--
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/1873378
Title:
gnome-control-center
Thank you for your bug report. Could you add your 'journalctl -b 0' log
after getting the issue? Is it specific to some wifis? Could you test
under GNOME if you can connect to those?
** Changed in: network-manager (Ubuntu)
Importance: Undecided => Low
** Changed in: network-manager (Ubuntu)
Happened to gnome-calculator on my laptop. Didn't notice any problem
with gedit. Renamed ~/.xinputrc, logout/login, problem solved. This
laptop started with 10.04LTS and has upgraded through all LTS versions
to 18.04LTS. I use gnome-flashback metacity by default...
--
You received this bug
So this is a feature and works as expected, not a bug.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2378 is another report
specific to configurations without a physical keyboard. Could you give
more details on the configuration you are using and test if it works
better under wayland for you?
** Bug watch added:
May I ask, if this is indeed the 'top gnome-shell crash in 18.04' wouldn't it
be good to backport the patch because its still a supported release? The
machine is on the latest patch level for 18.04.
I don't mind too much because I probably upgrade to 20.04 soon. However, this
bug (which only
On second thoughts, the patch doesn't apply in bionic and the issue is
way too deep and nasty to start trying to design a unique fix for bionic
this week.
** Changed in: gnome-shell (Ubuntu Bionic)
Status: In Progress => Triaged
--
You received this bug notification because you are a
Sorry but it's late now for getting changes on the release, fixes are
limited to those impacting the installer or default installation in an
important way. We will get the .2 update as a stable update soon enough
though
** Changed in: eog (Ubuntu)
Status: Triaged => Fix Committed
--
You
** Changed in: gnome-shell (Ubuntu Bionic)
Status: Triaged => In Progress
** Description changed:
+ [Impact]
+
+ gnome-shell crashes a lot on bionic:
https://errors.ubuntu.com/problem/3841a5bc586bc3f532d2313a35f51e511772751f
- ---
+ [Test Case]
+
+ ** Someone who can reproduce the
** Patch added: "libxau_1.0.8-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1559650/+attachment/5357502/+files/libxau_1.0.8-1ubuntu1.debdiff
** Changed in: libxau (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
** Description changed:
+ [Impact]
+
+ gnome-shell crashes a lot. Over 38000 times in bionic so far:
https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7
+
+ [Test Case]
+
+ None known yet. Just keeping an eye on the above link for regressions.
+
+ [Regression
@seb128: The bug was fixed upstream for GNOME 3.36.2. Would it be
possible for you to pull the change into Ubuntu's package so that it's
available for the 20.04 release? It looks like a pretty small change to
me.
--
You received this bug notification because you are a member of Desktop
Packages,
This change was made by a bot.
** Changed in: linux (Ubuntu)
Status: New => Confirmed
--
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/1874010
Title:
[Ice Lake] 2-second black
*** This bug is a duplicate of bug 1866556 ***
https://bugs.launchpad.net/bugs/1866556
I was wrong, sorry. Bug 1866556 is now reopened.
** This bug has been marked a duplicate of bug 1866556
On-screen keyboard (OSK) on touch screen does not seem to work at all under
Xorg in Focal
--
Apparently a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1874020
Title:
Jack clients cannot use real-time
Public bug reported:
With kernels 5.4.0-24-generic and 5.4.0-25-generic Jack client applications can
no longer use real-time scheduling. Kernel 5.4.0-23-generic works.
For example starting guitarix or ardour produces the following logs on stderr:
Cannot use real-time scheduling (RR/5)(1:
Since I got asked by vanwugt to create a new report about this issue,
here you go: https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1874017
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Yes, seems very similar to bug 1873587 with regards boot, but also bug
1873594 regarding post-boot blips.
--
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/1874010
Title:
[Ice Lake]
** This bug is no longer a duplicate of bug 1807276
Cannot open Onscreen Keyboard in Xorg
--
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/1866556
Title:
On-screen keyboard
Public bug reported:
Since GNOME 3.35 packages made their way into the focal repositories, the
on-screen keyboard no longer opens when touching on input fields or swiping
upwards from the bottom edge of the screen. It does not matter if the Wayland
or Xorg session is being used.
To use the
** Changed in: xorg-server (Ubuntu)
Status: Incomplete => New
** Package changed: xorg-server (Ubuntu) => mutter (Ubuntu)
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which
It looks like this was the issue:
https://gitlab.freedesktop.org/xorg/lib/libxau/-/commit/987fee49dc1750082cfe6e24833379233777a13b
** Also affects: libxau (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libxau (Ubuntu Eoan)
Status: New => Fix Released
** Changed in:
I can confirm that auto-login with the kernel parameters "quiet splash
nvidia-drm.modeset=1" works without issues, and that auto-login with
just "quiet splash" is still broken for me. This is with a GTX 1080Ti
now running nvidia-driver-440.
--
You received this bug notification because you are a
Hi Daniel,
In Response:
#2: I see the same problems in wayland and xorg.
#4: Reproducing the bug, results in no new messages.
--
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/1874010
Yes, this is the case. When I turn this off chromium is terminated
correctly.
--
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/1859878
Title:
Chrome does not quit when closing
*** This bug is a duplicate of bug 1807276 ***
https://bugs.launchpad.net/bugs/1807276
Since you are not the original reporter of this bug I suggest logging a
new one:
ubuntu-bug gnome-shell
so we can see more clearly just information from your affected machine.
--
You received this bug
Please also open a Terminal window and run:
dmesg -w
Now reproduce the black screen blips again. Do you see any new messages
in the Terminal window when they occurred?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in
*** This bug is a duplicate of bug 1807276 ***
https://bugs.launchpad.net/bugs/1807276
@esjarc, as the OP of this report I agree and also commented as much in
the other #1807276 already.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
See also bug 1873587.
** Tags added: ice-lake-flicker
--
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/1874010
Title:
[Ice Lake] 2-second black screen blips when using Chrome or
*** This bug is a duplicate of bug 1807276 ***
https://bugs.launchpad.net/bugs/1807276
Apparently there is already an open upstream issue about this problem, which
appeared in GNOME 3.36: https://gitlab.gnome.org/GNOME/gnome-shell/issues/2378
It makes touchscreens with Ubuntu 20.04 very
Please stick with the 'modeset' driver, that's more modern than 'intel'.
Does the problem occur if you select 'Ubuntu on Wayland' from the login
screen?
** Summary changed:
- Xorg freeze
+ [Ice Lake] 2-second black screen blips when using Chrome or gnome-screenshot
** Package changed: xorg
*** This bug is a duplicate of bug 1807276 ***
https://bugs.launchpad.net/bugs/1807276
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
Public bug reported:
Hi,
Im using a HP 14s dq laptop with intel 630 graphics.
I've tried both the mode setting and xserver-xorg-video-intel drivers,
both result in the same 2-second black screen blips. The happens
frequently using chrome, and always when using the gnome screenshot
utility.
*** This bug is a duplicate of bug 1871011 ***
https://bugs.launchpad.net/bugs/1871011
Thanks for the additional info, Robert. Making this bug a duplicate
then.
** This bug has been marked a duplicate of bug 1871011
USB scanning broken on focal --> hpmud and ippusbxd conflict
--
You
I can reliably reproduce the problem with chromium-browser
84.0.4115.5-0ubuntu0.18.04.1 from the dev PPA (ppa:chromium-team/dev).
The relevant error messages are:
[22305:22305:0421/034620.183897:ERROR:CONSOLE(1)] "Uncaught TypeError: Cannot
read property 'Runtime' of undefined", source:
$ xrandr --version
xrandr program version 1.5.0
Server reports RandR version 1.6
--
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/1870736
Title:
[nvidia] Screen scaling 125% gives
101 - 179 of 179 matches
Mail list logo
