Worked for me:
cat /etc/NetworkManager/conf.d/tl-wn722n.conf
[device]
match-device=wlx18a6f719681b
wifi.scan-rand-mac-address=0
Thanks for starting this thread.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in
Public bug reported:
Surprisingly, when I launched meld as a difftool and later suspended it
my session got frozen: my mouse was moving but clicks and keyboard
presses did not have any effect, there was an empty rectangle on my
screen on top of one of the windows. The only thing I could do was to
Public bug reported:
On-boot message in the log:
окт 15 01:50:32 blade gnome-shell[6314]: Some code accessed the property
'discreteGpuAvailable' on the module 'appDisplay'. That property was
defined with 'let' or 'const' inside the module. This was previously
supported, but is not correct
Public bug reported:
Attached screenshots for "before applying" and after.
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-shell 3.26.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm
** Attachment added: "After"
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1722000/+attachment/4964664/+files/after.png
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
This used to work before recent a update of several distro packages.
Currently settings are not applied and everything falls back to "Join
displays" instead of "Single Display"
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell
This used to work before recent a update of several distro packages.
Currently settings are not applied and everything falls back to "Join
displays" instead of "Single Display".
---
After debugging that a little bit more I can see that the bug is not
triggered if I do not change scaling from
Public bug reported:
Symptom: hotkeys do not work at all. It seems to only affect letters
themselves while Ctrl, Shift or Alt are interpreted (as shown in a bar
at the bottom of the UI).
➜ ~ echo $XDG_SESSION_DESKTOP
ubuntu-xorg
I do have two keyboard layouts
Alright, it seems that the problem was in "layout: ru,us,us". When I
switched to "layout: us" my gnome settings stopped affecting input so I
switched it to the following:
➜ ~ sudo setxkbmap -option grp:alt_shift_toggle us,ru
➜ ~ setxkbmap -query
rules:
Chris, out of curiosity, do you have a dual-monitor setup?
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1726538
For me it works fine with a laptop monitor disabled + single monitor as
a primary.
--
You received this bug notification because you are a member of Desktop
Packages,
I can confirm that the package version from bionic-proposed solves the
problem.
During an installation I used Dell 2715Q with settings as in the
screenshot attached (single monitor mode, 200% scaling).
# the updated package
apt policy ubiquity
ubiquity:
Installed: 18.04.14.1
Candidate:
A bit odd that I cannot reproduce this on a fresh 18.04 installation on
the same system.
https://paste.ubuntu.com/p/PqYBPfvvKr/
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Also, the setup in comment #7 was tested with 4.17-rc4 and 4.17-rc5.
--
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/1764137
Title:
[bionic][beta][nvidia] gnome-shell high CPU
Hmm, for my installation upgraded from 17.04 it got fixed - I no longer
experience the issue.
--
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/1716341
Title:
Settings for external
Public bug reported:
Scenario: a server is available via LAN from which content is played
back via SFTP (ssh, gvfs).
After some time (could be an hour) rhythmbox hangs and a window comes up
suggesting that you can either wait or terminate rhythmbox.
There are no network interruptions that would
Public bug reported:
I am experiencing 60% - 200% CPU utilization after an upgrade from
ubuntu artful to bionic.
Pretty much any drawing results in a sluggish behavior due to high CPU
utilization.
The same combination of kernel/drivers did not result in the issue on
17.10 so gnome-shell seems a
apport information
** Tags added: apport-collected
** Description changed:
I am experiencing 60% - 200% CPU utilization after an upgrade from
ubuntu artful to bionic.
Pretty much any drawing results in a sluggish behavior due to high CPU
utilization.
The same combination of
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1764137/+attachment/5116801/+files/ProcEnviron.txt
** Description changed:
I am experiencing 60% - 200% CPU utilization after an upgrade from
ubuntu artful to bionic.
Pretty much any drawing
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1764137/+attachment/5116800/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
nvidia-xconfig -generated xorg.conf looked like this
https://paste.ubuntu.com/p/4hRVzHmbJV/
--
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/1785964
Title:
Unable to unlock the
Had this with nvidia graphics drivers after installing and then removing
proprietary drivers downloaded from nvidia website. I could not log in
at all at first boot.
If you see nvidia modules loaded, make sure that you select an xorg
session on the login screen (not wayland) if you this control
On 19.04 I can see the following (correct) behavior.
With VPN (turned on via NetworkManager):
# note: no "global" DNS servers have been configured by hand through
systemd-resolved conf using "DNS=" directive
systemd-resolved --status
# ...
Link 15 (tun0)
Current Scopes: DNS
DefaultRoute
Public bug reported:
Unable to switch an input method from English in chromium by changing it
via ibus.
➜ ~ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 19.10
Release:19.10
Codename: eoan
➜ ~ snap list chromium
Name Version
Tried rev 951 now and I cannot reproduce the same behavior anymore.
➜ ~ snap refresh chromium --beta
Download snap "chromium" (951) from channel "beta"
77%
251kBDownloadchromium (beta)
English (US) to Russian: en -> ru.
** Changed in: chromium-browser (Ubuntu)
Status: Incomplete => New
--
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/1853420
Title:
updateinitramfs used to be run previously, however, this was removed at
some point (introduced into the distro in Cosmic/18.10):
https://github.com/tseliot/nvidia-
prime/commit/7595f47b84f713dc969440e31d0e53708fddd71f
https://git.launchpad.net/~usd-import-team/ubuntu/+source/nvidia-
Managed to reproduce it:
1) switched to nvidia;
2) worked for a while with it for a while with 5.3.0-19-generic;
3) got a kernel update to 5.3.0-23-generic;
4) switched to intel;
5) reproduced the problem.
What I found is:
1) /lib/modprobe.d/blacklist-nvidia.conf gets created if you switch to
I had the same problem (the system got upgraded from 19.04 to 19.10,
nvidia-430 driver).
I noticed that nvidia drivers were loaded in the rescue mode - so they
were likely not blacklisted properly.
When I did not enter the rescue mode I had the following message displayed:
"A start job is
If anybody still has a reproducer, it would be useful to set a trace
point like this:
sudo vim /usr/bin/prime-select
# ...
import pdb
pdb.set_trace()
if profile == 'nvidia':
# Always allow enabling nvidia
# (No need to check if nvidia is
Public bug reported:
I observed the following on Eoan as well with nvidia drivers older than
440.
1) a windows 10 VM running in a qemu-kvm VM: pc-q35-3.1 machine type,
QXL + SPICE:
2) When a host is booted with `prime-select intel` observing
Hi Daniel,
I submitted a new crash dump via `ubuntu-bug`:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1863142
I'm going to set the status for this one to "New" as I provided the info
but maybe it should be duplicated to the new bug.
** Changed in: xorg-server (Ubuntu)
** Tags added: champagne
--
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/1838151
Title:
Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing
wide band speech
I'm on focal now, just got the updated packages.
I will give it a try soon.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with
Happened to me when using virt-viewer and connecting to an Ubuntu 18.04
VM via SPICE as well so this isn't specific to a guest VM it seems.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
Thanks, will help you with testing for sure.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-select does not
albertomilone, looks good to me.
I tried switching from nvidia to intel and back rebooting on each
attempt and haven't managed to reproduce the issue. Looks like
reordering udev rules and/or adding another device class in your change
helped (thanks a lot!).
I don't see an nvidia device in lspci
Based on a discussion with ~albertomilone, powering down the NVIDIA GPU
while keeping the modules loaded is the way to go long-term as opposed
to blacklisting the modules.
The power management feature is described here (requires Turing GPUs and above):
Public bug reported:
A Wayland session present at /usr/share/wayland-sessions/ubuntu-
wayland.desktop is not displayed at the login screen when a system has
an iGPU (Intel) and dGPU (Nvidia) and Intel iGPU is used:
prime-select query
intel
Only sessions at /usr/share/xsessions are present.
➜
** Tags added: champagne
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1848326
Title:
[cosmic+] error booting with prime-select intel: prime-select does not
update initramfs
Hi Daniel, thank you for the quick response and prior work.
I think the upstream check for the nvidia driver in 61-gdm.rules is too
broad to be useful as the nvidia driver might be loaded for other
reasons (e.g. CUDA usage or hw accelerated video encoding/decoding while
nvidia-drm.ko is
I see, thanks for the clarification.
I will need to read through other cases as well.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1862531
Title:
[focal] Wayland session is
I no longer get that issue with latest updates for Focal so something
must have fixed it.
Setting to incomplete.
** Changed in: nvidia-graphics-drivers (Ubuntu)
Status: Confirmed => Incomplete
** Changed in: nvidia-graphics-drivers-440 (Ubuntu)
Status: Confirmed => Incomplete
**
Found another way to trigger this problem by opening up various
documents in libreoffice and using zoom back and forth (also happens
sometimes when comments are created).
https://errors.ubuntu.com/oops/a906d424-6cc2-11ea-aa90-fa163e983629
--
You received this bug notification because you are a
Public bug reported:
Gnome shell crashed while I was doing web browsing.
A crash report was also submitted via apport. This is a fresh install of
Ubuntu 22.10.
~$ uname -r
5.19.0-23-generic
HW: 21D4000HUS with integrated graphics in Ryzen 7 PRO 6850H and AMD
Radeon RX 6500M discrete card (AMD
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5627851/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5627853/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5627854/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5627850/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1995207/+attachment/5627852/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
Public bug reported:
When using a Wayland session with kernel 5.15.0-53-generic gnome-shell
may sometimes crash and restart. This happened to me when using a
chromium-based browser (Brave).
➜ ~ uname -r
5.15.0-53-generic
➜ ~ printenv XDG_SESSION_TYPE
wayland
The issue does not happen on the
apport information
** Attachment added: "GsettingsChanges.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631550/+files/GsettingsChanges.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631549/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631551/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631552/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "ShellJournal.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631553/+files/ShellJournal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
apport information
** Attachment added: "monitors.xml.txt"
https://bugs.launchpad.net/bugs/1997142/+attachment/5631554/+files/monitors.xml.txt
** Description changed:
When using a Wayland session with kernel 5.15.0-53-generic gnome-shell
may sometimes crash and restart. This happened to
56 matches
Mail list logo
