[Desktop-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Hi, thanks to everyone, especially Daniel for unpacking this issue. I have had a very similar issue, where gnome shell fails to run my external 4K/UHD display at 60HZ and I see the following failure loop triggered in `journalctl -b -p warning _COMM=gnome-shell`: May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to flip: Device or resource busy May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to blit shared framebuffer: EGL failed to allocate resources for the requested operation. May 02 20:39:38 JNBA434499PLL gnome-shell[1957]: Failed to set CRTC mode 3840x2160: No such file or directory ... While not sure it's exactly the same, it should still inform the overall discussion about dealing with GDM3 + Mutter + proprietary Nvidia drivers modeset problems. To summarise and share my experience of it on a Lenovo P53 and some quirks/workarounds: - `sudo ubuntu-drivers autoinstall` got Nvidia 440.59 drivers installed. - However, Nvidia modeset was not enabled as yet. $ sudo cat /sys/module/nvidia_drm/parameters/modeset N - - Using prime-select - For laptops like mine, seems the external port is connected to the Nvidia GPU. - Using the proprietary Nvidia drivers seems to then bump into a ** Attachment added: "gnome-shell_journal_warnings_egl_resource_failed.txt" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5365716/+files/gnome-shell_journal_warnings_egl_resource_failed.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1852183] Re: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04
I see this happening very frequently with screenshots...they seem to get lost. E.g: I use Ctrl+Prt Sc to get a screenshot of my entire display into my clipboard, and moments later I cannot paste it into Discord because somehow it got 'lost'. It takes several tries before the screenshot can finally be pasted into Discord. Also, one other thing I have noticed is that while taking the screenshot, if I can hear the screenshot 'click' sound, it will almost certainly fail, whereas if I don't hear the 'click' sound, it copies it successfully into the clipboard. I have seen this happening on Ubuntu 19.10 and 20.04 (currently on 20.04, seems worse than on 19.10) -- 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/1852183 Title: [X11] copy/paste (clipboard) is broken in Ubuntu 19.10 & 20.04 Status in LibreOffice: Won't Fix Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter source package in Eoan: Triaged Status in mutter source package in Focal: Fix Committed Bug description: I'm running LibreOffice 6.3.2.2 on Ubuntu 19.10. In this environment, copy/cut/paste often fails. Specifically, the paste command sometimes does not paste the text that was cut/copied most recently. Instead, it pastes text that was cut/copied at some prior time. I use LibreOffice Writer a lot, and I now see this problem very often, i.e. many times every day. There is some discussion of the problem here: https://ask.libreoffice.org/en/question/213510/copypaste-issues- libreoffice-calc/ Several posters there say that they are also using Ubuntu 19.10. Ubuntu 19.10 includes Mutter 3.34, which has a new clipboard manager: https://www.phoronix.com/scan.php?page=news_item=GNOME-3.34 -Clipboard-Manager It seems like that could be related. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1852183/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
more test on 20.04: 100%-->125% auto200% and larger desktop area than screen disable fractional scale--> 100% and not responding at all ctrl+alt+f1 -->login screen/login --> 200% and larger desktop area than screen, responding trying again 200%-->100% black screen ctrl+alt+f1 -->login screen/login --> black screen again ctrl+alt+f1 -->login screen/login -->200% and larger desktop area than screen, responding reboot--> 200%, normal desktop area 200%-->100% ok - On ubuntu 19.10, every fractional scale value is ok exept from video playing. Apps tested fail on full screen: videos on youtube through firefox, smplayer, vlc: normal window->ok, maximize->ok, full screen->black ps. If there is anything I can test, as far as I understand how to do it, I'll be glad to do it. -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875989] Re: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card
Reply to #12. Lenovo ThinkPad T400 has an internal sound card. So unplugging it sounds a bit challenging. Removed all the music software installations AND I CAN HEAR MUSIC! CASE SOLVED! Thanks!! === sudo apt-get remove lmms sudo apt-get remove ardour sudo apt-get remove qsynth sudo apt-get remove guitarix sudo apt-get remove timidity sudo apt-get update sudo apt-get upgrade sudo apt-get dist-update sudo apt-get autoremove reboot === -- 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/1875989 Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card Status in pulseaudio package in Ubuntu: Incomplete Bug description: No sound from internal or external soundjack since upgrading from Ubuntu 18.04 LTS to Ubuntu 20.04 LTS. 1) 'lsb_release -rd' Description: Ubuntu 20.04 LTS Release: 20.04 2) 'apt-cache policy pulseaudio' pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 Version table: *** 1:13.99.1-1ubuntu3 500 500 http://fi.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Hear sound 4) What happened instead No sound 5) 'lspci -v | grep -A7 -i "audio"' 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T400 Flags: bus master, fast devsel, latency 0, IRQ 33 Memory at fc22 (64-bit, non-prefetchable) [size=16K] Capabilities: Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/by-id', '/dev/snd/controlC0', '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/midiC1D0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 30 00:46:33 2020 InstallationDate: Installed on 2017-05-29 (1066 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HDA Intel Symptom_Jack: Speaker, Internal Title: [276812G, Conexant CX20561 (Hermosa), Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: Upgraded to focal on 2020-04-24 (5 days ago) dmi.bios.date: 10/17/2012 dmi.bios.vendor: LENOVO dmi.bios.version: 7UET94WW (3.24 ) dmi.board.name: 276812G dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7UET94WW(3.24):bd10/17/2012:svnLENOVO:pn276812G:pvrThinkPadT400:rvnLENOVO:rn276812G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T400 dmi.product.name: 276812G dmi.product.version: ThinkPad T400 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1875989/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875326] Re: Can't double click items in icon view
It seems that on clicking an item the focus is temporarily set to a different item further up the page before setting it to the selected item. This can cause the page to scroll up to display the temporarily focused item before scrolling down to show the selected item. Hence the jump. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1875326 Title: Can't double click items in icon view Status in nautilus package in Ubuntu: New Bug description: Ubuntu: 20.04LTS Nautilus: 1:3.36.1.1-1ubuntu2 Double clicking an item in Nautilus should open the item but this doesn't happen in all cases because the display is scrolled. When items are displayed in icon view (as opposed to list view) and there are more items than can be displayed in the window, clicking an item can cause the display to scroll so that the item is no longer under the cursor and so double-clicking is impossible. This only seems to happen if the display has been scrolled down somewhat and clicking the item then causes it to be scrolled to the bottom of the window. In list view the item can be double-clicked without a problem so this is a workaround. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Apr 27 10:44:48 2020 ExecutablePath: /usr/bin/nautilus InstallationDate: Installed on 2015-12-19 (1590 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SourcePackage: nautilus UpgradeStatus: Upgraded to focal on 2020-04-25 (1 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1875326/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876534] Re: ThinkPad P72 - Very serious issues with external monitors on Thunderbolt dock
** Description changed: I'm running Ubuntu 20.04 LTS on a ThinkPad P72 with a Quadro P5200. I recently purchased the ThinkPad Workstation Dock Gen2 and have been having issues with external displays on it. There are a multitude of issues with this. Sometimes you can plug in displays and both will show up fine after running xrandr --auto. Sometimes only one will appear and the other will stay black. There is a chance for any of these things to happen after making a display configuration change: - Nothing (displays work fine) - One display stays black - All displays including laptop internal display freeze, which is recoverable only by physically disconnecting the displays from the dock - Displays flicker on and off rapidly before every one goes dark including the laptop's internal display, requiring a hard reset. I have tried: - Upgrading to a newer kernel version (5.6.7) via mainline - Upgrading all system firmware, including dock, to latest via Lenovo Vantage in Windows dual boot - Downgrading the dock firmware from 3166 to 3164 - despite suggestions by people in this thread in the Lenovo community https://forums.lenovo.com/t5/Ubuntu/Thinkpad-P1-Gen2-amp-Thunderbolt-3-Workstation-Dock-amp-Linux-Ubuntu-Monitor-s-black/m-p/4575709?page=3 - this did not work - Downgrading the NVIDIA driver version to both 435 and 390 - neither worked + Downgrading to an older kernel (4.19) appears to work, but it still has + some issues with locking up while repositioning displays using xrandr. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: - NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 - GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) + NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 + GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun May 3 00:37:27 2020 DistUpgraded: 2020-03-04 19:48:20,592 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: - acpi-call, 1.1.0, 5.4.0-28-generic, x86_64: installed - nvidia, 440.64, 5.4.0-28-generic, x86_64: installed - v4l2loopback, 0.12.3, 5.4.0-28-generic, x86_64: installed - wireguard, 1.0.20200413, 5.4.0-28-generic, x86_64: installed (WARNING! Diff between built and installed module!) + acpi-call, 1.1.0, 5.4.0-28-generic, x86_64: installed + nvidia, 440.64, 5.4.0-28-generic, x86_64: installed + v4l2loopback, 0.12.3, 5.4.0-28-generic, x86_64: installed + wireguard, 1.0.20200413, 5.4.0-28-generic, x86_64: installed (WARNING! Diff between built and installed module!) ExtraDebuggingInterest: Yes, including running git bisection searches GpuHangFrequency: This is the first time GraphicsCard: - Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) -Subsystem: Lenovo Device [17aa:2269] - NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) -Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] + Intel Corporation Device [8086:3e94] (prog-if 00 [VGA controller]) + Subsystem: Lenovo Device [17aa:2269] + NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) (prog-if 00 [VGA controller]) + Subsystem: Lenovo GP104GLM [Quadro P5200 Mobile] [17aa:2269] InstallationDate: Installed on 2019-10-19 (196 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20MCS08200 ProcEnviron: - LANGUAGE=en_GB:en - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_GB.UTF-8 - SHELL=/bin/bash + LANGUAGE=en_GB:en + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_GB.UTF-8 + SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash intel_iommu=on default_hugepagesz=1G hugepagesz=1G hugepages=32 transparent_hugepage=never vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-03-04 (59 days ago) dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2CET50W (1.33 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MCS08200
[Desktop-packages] [Bug 864369] Re: Hibernate option missing from gnome-shell session menu
@vanvugt: What would be your proposed way to fix this in Ubuntu if upstream doesn't change their mind? A new extension? Adding a patch to the package? -- 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/864369 Title: Hibernate option missing from gnome-shell session menu Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Status in Baltix: New Bug description: I upgraded to Oneiric recently and installed gnome-shell because unity still has some pretty serious functionality problems, but discovered that the gnome-shell session menu doesn't have a Hibernate option, just Suspend. I never use suspend, but use hibernate at least twice a day, so this regression in functionality is a pain. The alternative-status-menu shell extension (http://live.gnome.org/GnomeShell/Extensions) for gnome-shell adds the Hibernate option back, but it apparently isn't packaged for Ubuntu yet. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/864369/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876569] [NEW] Dock settings do not apply correctly
Public bug reported: I went to try out the different dock settings such as use on all displays and the position on the displays and tried use on all displays, but when I tried to switch back to showing the dock on only one display, upon clicking the display I wanted it to show up on, the dock persisted on both displays and the dropdown menu showed all displays again. No matter what I choose, it shows the dock on both displays. Sometimes the dropdown menu will have the display chosen, but will still have the dock on both displays. More often then not it will have all displays shown as selected in the dropdown menu and have the dock on both screens. Some things of note are that I have identical monitors and the problem persists after a restart. Basically 1. I opened the settings app. 2. I navigated to appearance and selected all monitors for where to display the dock. 3. I tried to switch back to my main display, and it did not work. Required info: Source: /usr/bin/gnome-control-center Release Info: Description:Ubuntu 20.04 LTS Release:20.04 Version: gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 05:29:00 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot of example of issue." https://bugs.launchpad.net/bugs/1876569/+attachment/5365633/+files/Screenshot%20from%202020-05-03%2005-52-58.png -- 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/1876569 Title: Dock settings do not apply correctly Status in gnome-control-center package in Ubuntu: New Bug description: I went to try out the different dock settings such as use on all displays and the position on the displays and tried use on all displays, but when I tried to switch back to showing the dock on only one display, upon clicking the display I wanted it to show up on, the dock persisted on both displays and the dropdown menu showed all displays again. No matter what I choose, it shows the dock on both displays. Sometimes the dropdown menu will have the display chosen, but will still have the dock on both displays. More often then not it will have all displays shown as selected in the dropdown menu and have the dock on both screens. Some things of note are that I have identical monitors and the problem persists after a restart. Basically 1. I opened the settings app. 2. I navigated to appearance and selected all monitors for where to display the dock. 3. I tried to switch back to my main display, and it did not work. Required info: Source: /usr/bin/gnome-control-center Release Info: Description: Ubuntu 20.04 LTS Release: 20.04 Version: gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 05:29:00 2020 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876569/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1876566] [NEW] Two Mouse pointers one big and stuck
Public bug reported: After login a big mouse pointer is stuck in the middle of the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 12:32:29 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Pointer" https://bugs.launchpad.net/bugs/1876566/+attachment/5365624/+files/Screenshot%20from%202020-05-03%2012-35-21.png -- 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/1876566 Title: Two Mouse pointers one big and stuck Status in gnome-shell package in Ubuntu: New Bug description: After login a big mouse pointer is stuck in the middle of the screen. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 12:32:29 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876532] Re: Badly positioned icons in the app grid
Correction: It's not about where the cursor is placed when the animation ends, it's about whether the cursor is moving or not. Keep the cursor still, as I said previously, and the bug doesn't happen. Keep the cursor moving while the sliding animation is running, and the problem is nearly always reproducible. -- 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/1876532 Title: Badly positioned icons in the app grid Status in gnome-shell package in Ubuntu: New Bug description: This bug is best explained with images. I've attached two screenshots showing what the app grid looks like right after it's opened. A gif has also been recorded to show a glitch in the animation as the icons slide in. This is not reproducible in Fedora 32 with GNOME 3.36 on the same machine. I will be testing the Wayland session shortly and report back. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 2 19:51:09 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-02 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876532/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765363] Re: prime-select intel is not powering off the nvidia card
I confirm the issue on Ubuntu 18.04 base with kernel 4.15.0-88, NVidia
drivers 435.21 and 440.59 make no difference in the behavior. After
'prime-select intel' the nvidia driver is not loaded at all and intel
graphcs are active, but according to PowerTop the NVIDIA chip still
consumes the power. Acer laptop, NVidia 1050 Ti, Intel i5-7300HQ.
(TLDR: see SOLUTION at the end of the comment!)
Good thing is: as reported in comment #61 above by Vincente, command
from PowerTop Tunables tab (Runtime PM for PCI device NVIDIA Corporation
GP107M) actually helps to power off the NVidia chip and power
consumption goes down by a ~10W. Unfortunately, that does not persist
after system restart.
After checking the relevant NVidia driver manual
http://us.download.nvidia.com/XFree86/Linux-x86_64/440.59/README/dynamicpowermanagement.html
I have found that same command to enable the runtime power management which
PowerTop uses:
echo auto > /sys/bus/pci/devices/\:01\:00.0/power/control
or a variant with proper privileges:
sudo sh -c 'echo auto > /sys/bus/pci/devices/:01:00.0/power/control'
That does the trick as well, so PowerTop is not needed to enable it.
GREAT THING AND THE SOLUTION: after reading the 'Automated Setup'
section in the nvidia manual above, I have found a way to automate that.
No bbswitch, no tlp tools, no extra scripts/services! Just create a file
named 80-nvidia-poweroff.rules in /lib/udev/rules.d/ directory with the
following content:
# Enable runtime PM for NVIDIA VGA/3D controller devices by default (if the
driver is not / will not be bound)
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de",
ATTR{class}=="0x03", DRIVER=="", TEST=="power/control",
ATTR{power/control}="auto"
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de",
ATTR{class}=="0x030200", DRIVER=="", TEST=="power/control",
ATTR{power/control}="auto"
Save and reboot the system. Done! The nvidia chip will be in power off
mode already when you open the PowerTop to check that. And that will
work only when the intel is selected as an active controller by prime-
select tool, so should be safe when nvidia is set as active instead.
P.S. I wish this to be done automatically when installing the nvidia
driver... No magic for installer to create that file.
--
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/1765363
Title:
prime-select intel is not powering off the nvidia card
Status in nvidia-prime package in Ubuntu:
Confirmed
Bug description:
Right now, it seems that prime-select intel makes sure the nvidia driver is
not loaded, as nvidia-settings reports.
But my power consumption is > 20W.
cat /proc/acpi/bbswitch reports the card is still on.
If bbswitch and powertop are reliable, then the nvidia card is still powered.
This is a thinkpad w520 in Optimus mode.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: nvidia-prime 0.8.7
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 19 19:56:21 2018
Dependencies:
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-12-14 (125 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
SourcePackage: nvidia-prime
UpgradeStatus: Upgraded to bionic on 2018-03-09 (41 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1765363/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876471] Re: Trash desktop icon is not translated
Apparently this isn't only a problem of the desktop icons package after all. In Files "Trash" is translated as expected, with the exception of the breadcrumb item (see the attached screenshot). Should I assign this bug report to another package? If so, what package should it be assigned to? ** Attachment added: ""Trash" is translated to "Prullenbak" (in Dutch) except on the desktop and in the breadcrumb (Files)." https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1876471/+attachment/5365620/+files/Schermafdruk%20van%202020-05-03%2011-19-33.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1876471 Title: Trash desktop icon is not translated Status in gnome-shell-extension-desktop-icons package in Ubuntu: New Bug description: 1) Release: Ubuntu 20.04 2) Package version: gnome-shell-extension-desktop-icons 20.04.0-1 3) Expected behaviour The name of the trash icon should be in the language of the current user. 4) Actual behaviour The trash icon on the desktop is always named "Trash". It would be better if the name of this icon were translated, using the same name as elsewhere (e.g. inside Gnome Files). For example: "Corbeille" if the current user's language is French, "Prullenbak" if the language is Dutch... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1876471/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox
For me in 20.04, bug is definitely still present. I have earlyoom active, and 32 gb a few seconds of "freeze" (which is not really a freeze) earlyoom activates and nukes a few things, including Firefox, which brings back interactive response. It also killed Chrome and Remmina, which was irritating, but that's what earlyoom is there to do; better than minutes of no keyboard response. Alt F2 seem to work after a few seconds too, which allows restart of the gnome shell. I will comment on the upstream bug. -- 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/1749779 Title: System freeze when going back and forth fullscreen mode with Firefox Status in Mozilla Firefox: Confirmed Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell/issues/71 --- Use Ubuntu 17.10 Open a Wayland session Start Firefox Press F11 repeatedly --> The System freezes ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 20:09:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1749779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876561] [NEW] Launching terminal or typing commands in it makes the desktop "refresh"
Public bug reported: By refresh i mean that every icons disappear before reappearing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 10:15:55 2020 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-04-28 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1876561 Title: Launching terminal or typing commands in it makes the desktop "refresh" Status in gnome-terminal package in Ubuntu: New Bug description: By refresh i mean that every icons disappear before reappearing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.1.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 10:15:55 2020 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-04-28 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/usr/bin/zsh XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1876561/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876460] Re: No users appear in settings
I have a user with uid 1001 that doesn't show up in the gnome-control- center. Is this not a bug? -- 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/1876460 Title: No users appear in settings Status in gnome-control-center package in Ubuntu: Invalid Bug description: 1. Open the gnome control center 2. Click on "users" 3. See that there are no users (see attached screenshot). The message says "No Ussers Found", "Unlock to add a user account." There is no button to unlock. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat May 2 15:27:03 2020 SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876555] Re: Apps cannot retrieve internal mic input
Some additional info for bug report: $ ls /lib/modules/5.3.0-51-generic/kernel/sound/drivers mpu401 snd-aloop.ko snd-mts64.ko snd-virmidi.ko opl3snd-dummy.ko snd-portman2x4.ko vx pcspsnd-mtpav.ko snd-serial-u16550.ko ~$ ls /lib/firmware/cs46xx/ ba1 cwc4630 cwcasync cwcbinhack cwcdma cwcsnoop ~$ modinfo snd-cs46xx filename: /lib/modules/5.3.0-51-generic/kernel/sound/pci/cs46xx/snd-cs46xx.ko license:GPL description:Cirrus Logic Sound Fusion CS46XX author: Jaroslav Kysela firmware: cs46xx/cwcdma firmware: cs46xx/cwcbinhack firmware: cs46xx/cwcsnoop firmware: cs46xx/cwcasync firmware: cs46xx/cwc4630 srcversion: 11FF4360F4C97088F132FB1 alias: pci:v1013d6004sv*sd*bc*sc*i* alias: pci:v1013d6003sv*sd*bc*sc*i* alias: pci:v1013d6001sv*sd*bc*sc*i* depends:snd-pcm,snd-ac97-codec,snd,snd-rawmidi,gameport retpoline: Y intree: Y name: snd_cs46xx vermagic: 5.3.0-51-generic SMP mod_unload signat: PKCS#7 signer: sig_key: sig_hashalgo: md4 parm: index:Index value for the CS46xx soundcard. (array of int) parm: id:ID string for the CS46xx soundcard. (array of charp) parm: enable:Enable CS46xx soundcard. (array of bool) parm: external_amp:Force to enable external amplifier. (array of bool) parm: thinkpad:Force to enable Thinkpad's CLKRUN control. (array of bool) parm: mmap_valid:Support OSS mmap. (array of bool) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876555 Title: Apps cannot retrieve internal mic input Status in alsa-driver package in Ubuntu: New Bug description: Could be pulseaudio, alsa-driver, or ~$ /usr/bin/gnome-control-center sound input Dell Vostro 2520 dual-boot laptop Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 2- Cirrus Logic High Definition Audio, model CS4213 Ubuntu 18.04.4 LTS Windows 10 Home, v. 1903, bld 18362.778 Skype 8.59 (Ubu & Win) Zoom (cloud meetings) 5.0.3x (Ubu), 5.0.1x (Win) pulseaudio 1:11.1-1ubuntu7.5 alsa-driver -- package could not be found: ~$ apt-cache policy alsa-driver N: Unable to locate package alsa-driver Does this help? /lib/modules/5.3.0-51-generic/kernel/sound/drivers In Settings > Sound > Input, the On/Off [unmute/mute] setting *appearance* is preserved over reboots and awakenings from sleep, but the mic input sound is always muted despite the control still being set to On (unmute). Clicking mute (Off), then unmute (On) restores mic input, as shown by the level meter tracking input sounds. However, Skype 8.59x and Zoom 5.0.3x cannot receive sound inputs *despite* their sound level meters (in their respective sound settings) registering changing input levels. The Skype test call does not work. I opened a Zoom meeting with my wife on her Win 10 computer. I could see and hear her, and she could see but not hear me. On this dual-boot laptop, Skype 8.59x fails the test call under Windows 10 Home. The Sound Recorder app can successfully record mic input and play it back. pavucontrol shows input on its level meter. Notes: + ~$ /usr/bin/gnome-control-center sound input (gnome-control-center:17284): sound-cc-panel-WARNING **: 16:48:28.795: Couldn't find a stream from the active input + Many days searching the internet and AskUbuntu have not produced a solution that works. (For what it is worth, many posters have reported that sound became dysfunctional after upgrading to 18.04 or 18.04.4.) + I have added the snd-cs46xx kernel module and firmware to get around driver licensing issues following the instructions at https://wiki.debian.org/snd-cs46xx, Debian 8. + I have added these lines to /etc/modprobe.d/alsa-base.conf : options snd-hda-intel model=dell-vostro-2520 options snd-hda-intel dmic_detect=0 + In PulseAudio Volume Control I have set the following: Input Devices Port: Internal Microphone Output Devices Port: Speakers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hfinger4047 F pulseaudio /dev/snd/pcmC0D0c: hfinger4047 F...m pulseaudio /dev/snd/pcmC0D0p: hfinger4047 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 16:52:35 2020 InstallationDate: Installed on 2020-04-15 (17 days ago) InstallationMedia:
[Desktop-packages] [Bug 1876555] Re: Apps cannot retrieve internal mic input
Did the internal mic work before? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876555 Title: Apps cannot retrieve internal mic input Status in alsa-driver package in Ubuntu: New Bug description: Could be pulseaudio, alsa-driver, or ~$ /usr/bin/gnome-control-center sound input Dell Vostro 2520 dual-boot laptop Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 2- Cirrus Logic High Definition Audio, model CS4213 Ubuntu 18.04.4 LTS Windows 10 Home, v. 1903, bld 18362.778 Skype 8.59 (Ubu & Win) Zoom (cloud meetings) 5.0.3x (Ubu), 5.0.1x (Win) pulseaudio 1:11.1-1ubuntu7.5 alsa-driver -- package could not be found: ~$ apt-cache policy alsa-driver N: Unable to locate package alsa-driver Does this help? /lib/modules/5.3.0-51-generic/kernel/sound/drivers In Settings > Sound > Input, the On/Off [unmute/mute] setting *appearance* is preserved over reboots and awakenings from sleep, but the mic input sound is always muted despite the control still being set to On (unmute). Clicking mute (Off), then unmute (On) restores mic input, as shown by the level meter tracking input sounds. However, Skype 8.59x and Zoom 5.0.3x cannot receive sound inputs *despite* their sound level meters (in their respective sound settings) registering changing input levels. The Skype test call does not work. I opened a Zoom meeting with my wife on her Win 10 computer. I could see and hear her, and she could see but not hear me. On this dual-boot laptop, Skype 8.59x fails the test call under Windows 10 Home. The Sound Recorder app can successfully record mic input and play it back. pavucontrol shows input on its level meter. Notes: + ~$ /usr/bin/gnome-control-center sound input (gnome-control-center:17284): sound-cc-panel-WARNING **: 16:48:28.795: Couldn't find a stream from the active input + Many days searching the internet and AskUbuntu have not produced a solution that works. (For what it is worth, many posters have reported that sound became dysfunctional after upgrading to 18.04 or 18.04.4.) + I have added the snd-cs46xx kernel module and firmware to get around driver licensing issues following the instructions at https://wiki.debian.org/snd-cs46xx, Debian 8. + I have added these lines to /etc/modprobe.d/alsa-base.conf : options snd-hda-intel model=dell-vostro-2520 options snd-hda-intel dmic_detect=0 + In PulseAudio Volume Control I have set the following: Input Devices Port: Internal Microphone Output Devices Port: Speakers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hfinger4047 F pulseaudio /dev/snd/pcmC0D0c: hfinger4047 F...m pulseaudio /dev/snd/pcmC0D0p: hfinger4047 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 16:52:35 2020 InstallationDate: Installed on 2020-04-15 (17 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [Vostro 2520, Cirrus Logic CS4213, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0FWKV7 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd01/25/2013:svnDellInc.:pnVostro2520:pvrNotSpecified:rvnDellInc.:rn0FWKV7:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 2520 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-01T13:58:36.978996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876555] Re: Apps cannot retrieve internal mic input
** Package changed: ubuntu => alsa-driver (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1876555 Title: Apps cannot retrieve internal mic input Status in alsa-driver package in Ubuntu: New Bug description: Could be pulseaudio, alsa-driver, or ~$ /usr/bin/gnome-control-center sound input Dell Vostro 2520 dual-boot laptop Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 2- Cirrus Logic High Definition Audio, model CS4213 Ubuntu 18.04.4 LTS Windows 10 Home, v. 1903, bld 18362.778 Skype 8.59 (Ubu & Win) Zoom (cloud meetings) 5.0.3x (Ubu), 5.0.1x (Win) pulseaudio 1:11.1-1ubuntu7.5 alsa-driver -- package could not be found: ~$ apt-cache policy alsa-driver N: Unable to locate package alsa-driver Does this help? /lib/modules/5.3.0-51-generic/kernel/sound/drivers In Settings > Sound > Input, the On/Off [unmute/mute] setting *appearance* is preserved over reboots and awakenings from sleep, but the mic input sound is always muted despite the control still being set to On (unmute). Clicking mute (Off), then unmute (On) restores mic input, as shown by the level meter tracking input sounds. However, Skype 8.59x and Zoom 5.0.3x cannot receive sound inputs *despite* their sound level meters (in their respective sound settings) registering changing input levels. The Skype test call does not work. I opened a Zoom meeting with my wife on her Win 10 computer. I could see and hear her, and she could see but not hear me. On this dual-boot laptop, Skype 8.59x fails the test call under Windows 10 Home. The Sound Recorder app can successfully record mic input and play it back. pavucontrol shows input on its level meter. Notes: + ~$ /usr/bin/gnome-control-center sound input (gnome-control-center:17284): sound-cc-panel-WARNING **: 16:48:28.795: Couldn't find a stream from the active input + Many days searching the internet and AskUbuntu have not produced a solution that works. (For what it is worth, many posters have reported that sound became dysfunctional after upgrading to 18.04 or 18.04.4.) + I have added the snd-cs46xx kernel module and firmware to get around driver licensing issues following the instructions at https://wiki.debian.org/snd-cs46xx, Debian 8. + I have added these lines to /etc/modprobe.d/alsa-base.conf : options snd-hda-intel model=dell-vostro-2520 options snd-hda-intel dmic_detect=0 + In PulseAudio Volume Control I have set the following: Input Devices Port: Internal Microphone Output Devices Port: Speakers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hfinger4047 F pulseaudio /dev/snd/pcmC0D0c: hfinger4047 F...m pulseaudio /dev/snd/pcmC0D0p: hfinger4047 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 16:52:35 2020 InstallationDate: Installed on 2020-04-15 (17 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [Vostro 2520, Cirrus Logic CS4213, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0FWKV7 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd01/25/2013:svnDellInc.:pnVostro2520:pvrNotSpecified:rvnDellInc.:rn0FWKV7:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 2520 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-01T13:58:36.978996 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1876555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876555] [NEW] Apps cannot retrieve internal mic input
You have been subscribed to a public bug: Could be pulseaudio, alsa-driver, or ~$ /usr/bin/gnome-control-center sound input Dell Vostro 2520 dual-boot laptop Intel Corporation 7 Series/C216 Chipset Family High Definition Audio Controller (rev 04) 2- Cirrus Logic High Definition Audio, model CS4213 Ubuntu 18.04.4 LTS Windows 10 Home, v. 1903, bld 18362.778 Skype 8.59 (Ubu & Win) Zoom (cloud meetings) 5.0.3x (Ubu), 5.0.1x (Win) pulseaudio 1:11.1-1ubuntu7.5 alsa-driver -- package could not be found: ~$ apt-cache policy alsa-driver N: Unable to locate package alsa-driver Does this help? /lib/modules/5.3.0-51-generic/kernel/sound/drivers In Settings > Sound > Input, the On/Off [unmute/mute] setting *appearance* is preserved over reboots and awakenings from sleep, but the mic input sound is always muted despite the control still being set to On (unmute). Clicking mute (Off), then unmute (On) restores mic input, as shown by the level meter tracking input sounds. However, Skype 8.59x and Zoom 5.0.3x cannot receive sound inputs *despite* their sound level meters (in their respective sound settings) registering changing input levels. The Skype test call does not work. I opened a Zoom meeting with my wife on her Win 10 computer. I could see and hear her, and she could see but not hear me. On this dual-boot laptop, Skype 8.59x fails the test call under Windows 10 Home. The Sound Recorder app can successfully record mic input and play it back. pavucontrol shows input on its level meter. Notes: + ~$ /usr/bin/gnome-control-center sound input (gnome-control-center:17284): sound-cc-panel-WARNING **: 16:48:28.795: Couldn't find a stream from the active input + Many days searching the internet and AskUbuntu have not produced a solution that works. (For what it is worth, many posters have reported that sound became dysfunctional after upgrading to 18.04 or 18.04.4.) + I have added the snd-cs46xx kernel module and firmware to get around driver licensing issues following the instructions at https://wiki.debian.org/snd-cs46xx, Debian 8. + I have added these lines to /etc/modprobe.d/alsa-base.conf : options snd-hda-intel model=dell-vostro-2520 options snd-hda-intel dmic_detect=0 + In PulseAudio Volume Control I have set the following: Input Devices Port: Internal Microphone Output Devices Port: Speakers ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hfinger4047 F pulseaudio /dev/snd/pcmC0D0c: hfinger4047 F...m pulseaudio /dev/snd/pcmC0D0p: hfinger4047 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun May 3 16:52:35 2020 InstallationDate: Installed on 2020-04-15 (17 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Mic, Internal Symptom_Type: None of the above Title: [Vostro 2520, Cirrus Logic CS4213, Mic, Internal] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0FWKV7 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd01/25/2013:svnDellInc.:pnVostro2520:pvrNotSpecified:rvnDellInc.:rn0FWKV7:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 2520 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-05-01T13:58:36.978996 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa amd64 apport-bug bionic internal-microphone pulseaudio sound -- Apps cannot retrieve internal mic input https://bugs.launchpad.net/bugs/1876555 You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
Affected as well: Ubuntu 20.04 LTS GeForce 1080 nvidia-driver-440 -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% Status in gnome-control-center package in Ubuntu: Confirmed Status in mutter package in Ubuntu: In Progress Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: Procedure used: 1. Fully updated system via apt update && apt upgrade 2. Select the screen setup in gnome control center 3. Click the "Fractional scaling" toggle 4. Select 125% and click the green "use" button top right (it says "Anvend" in dansih) 5. Observe that the window has grown a lot, click the "use new settings" button 6. The window tells me, I am at 200% scaling. The "200%" option is now highlighted. 7. Switch back to 100% and file this bug. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.16 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 09:42:34 2020 InstallationDate: Installed on 2018-01-14 (810 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=da_DK.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: Upgraded to focal on 2020-04-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Confirmed here with Ubuntu 20.04 and GTX 1060. As already suggested I used the fix: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to GRUB_CMDLINE_LINUX_DEFAULT="quiet" in the file: sudo nano /etc/default/grub and after: sudo update-grub which worked for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1874217] Re: Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors
Seems they've closed that bug, blaming it on the nvidia driver? -- 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/1874217 Title: Dual monitor setup with secondary monitor in portrait-right mode cause tiled windows to occupy 1.5 monitors Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I will provide below a screen capture. I think this bug is related to this one : https://bugs.launchpad.net/dash-to-dock/+bug/1869571 I'm on Ubuntu 20.04 AMD64 fully up to date and freshly rebooted. I use dual screen : the main screen is on the left side (32"), the secondary screen (19") is at right and in portrait mode (rotated right). The window are improperly growed : they extend from full main screen to half the "witdh" of the secondary screen. Additionnally, the « pop-up » menus (eg. from settings) do not appear at the right place (see screen capture in comment). The problem disappears if I revert the orientation of secondary screen from « portrait turned right » to « landscape ». I do have gnome-shell-extension-ubuntu-dock in version 67ubuntu20.04.5, but still got the problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Apr 22 11:11:25 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-19 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1874217/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876551] Re: Upgrading from 19.10 to 20.04, gnome no longer allows setting display to portrait orientation
Likely to be related to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1874217 ... which Gnome upstream closed as being related to nvidia driver... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1876551 Title: Upgrading from 19.10 to 20.04, gnome no longer allows setting display to portrait orientation Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Upgraded from 19.10 to 20.04. Running: * NVIDIA Corporation G92 [GeForce GTS 250] (rev a2) * Gigabyte P55A-UD4 * Intel Core i7 860 * 2x DELL U2413 1920x1200 * One connected via DVI in landscape * Detected as #2 * Positioned on the left * Configured to be screen with dock/launcher * One connected via HDMI in portrait * Detected as 1 * Positioned on the right Upon logging into my normal gnome session, the right display (detected as display 1) was no longer rotated to portrait orientation. Attempting to do this through the normal Gnome settings panel appears to disable monitor 1 which I want to rotate, and increase the virtual desktop size on monitor 2. Without rotation, both monitors are functioning. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 15:52:13 2020 InstallationDate: Installed on 2016-01-21 (1563 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) mtime.conffile..etc.apport.crashdb.conf: 2018-11-10T13:06:57.396750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1876551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876551] [NEW] Upgrading from 19.10 to 20.04, gnome no longer allows setting display to portrait orientation
Public bug reported: Upgraded from 19.10 to 20.04. Running: * NVIDIA Corporation G92 [GeForce GTS 250] (rev a2) * Gigabyte P55A-UD4 * Intel Core i7 860 * 2x DELL U2413 1920x1200 * One connected via DVI in landscape * Detected as #2 * Positioned on the left * Configured to be screen with dock/launcher * One connected via HDMI in portrait * Detected as 1 * Positioned on the right Upon logging into my normal gnome session, the right display (detected as display 1) was no longer rotated to portrait orientation. Attempting to do this through the normal Gnome settings panel appears to disable monitor 1 which I want to rotate, and increase the virtual desktop size on monitor 2. Without rotation, both monitors are functioning. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 15:52:13 2020 InstallationDate: Installed on 2016-01-21 (1563 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) mtime.conffile..etc.apport.crashdb.conf: 2018-11-10T13:06:57.396750 ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1876551 Title: Upgrading from 19.10 to 20.04, gnome no longer allows setting display to portrait orientation Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Upgraded from 19.10 to 20.04. Running: * NVIDIA Corporation G92 [GeForce GTS 250] (rev a2) * Gigabyte P55A-UD4 * Intel Core i7 860 * 2x DELL U2413 1920x1200 * One connected via DVI in landscape * Detected as #2 * Positioned on the left * Configured to be screen with dock/launcher * One connected via HDMI in portrait * Detected as 1 * Positioned on the right Upon logging into my normal gnome session, the right display (detected as display 1) was no longer rotated to portrait orientation. Attempting to do this through the normal Gnome settings panel appears to disable monitor 1 which I want to rotate, and increase the virtual desktop size on monitor 2. Without rotation, both monitors are functioning. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 15:52:13 2020 InstallationDate: Installed on 2016-01-21 (1563 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: nvidia-graphics-drivers-340 UpgradeStatus: Upgraded to focal on 2020-05-03 (0 days ago) mtime.conffile..etc.apport.crashdb.conf: 2018-11-10T13:06:57.396750 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1876551/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876552] [NEW] PC freezes when F11 is pressed
Public bug reported: When pressed F11 the computer freezes. The problem is stated in this post: https://www.omgubuntu.co.uk/2020/05/ubuntu-freeze-f11-bug ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 07:41:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-07 (25 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-07 (25 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal package-from-proposed -- 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/1876552 Title: PC freezes when F11 is pressed Status in gnome-shell package in Ubuntu: New Bug description: When pressed F11 the computer freezes. The problem is stated in this post: https://www.omgubuntu.co.uk/2020/05/ubuntu-freeze-f11-bug ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 3 07:41:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-07 (25 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-07 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1876552/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
