[Desktop-packages] [Bug 1876516] Re: Mouse cursor lagging (or freezing) when moving over system tray when wayland session
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extension-dash- to-panel (Ubuntu) ** Changed in: gnome-shell-extension-dash-to-panel (Ubuntu) Status: Incomplete => New -- 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/1876516 Title: Mouse cursor lagging (or freezing) when moving over system tray when wayland session Status in gnome-shell-extension-dash-to-panel package in Ubuntu: New Bug description: Cursor lagging when using wayland session. It happens on edge of something new, for example: - between clock menu and keyboard langugge - between app window and left launch panel Xorg session has no mouse lagging over this edges. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libwayland-client0 1.18.0-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Отказано в доступе: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 23:10:15 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.271+bdcom, 5.4.0-28-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 5.4.0-29-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6320] [1002:9806] (prog-if 00 [VGA controller]) Subsystem: Samsung Electronics Co Ltd Wrestler [Radeon HD 6320] [144d:c600] InstallationDate: Installed on 2020-04-26 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: SAMSUNG ELECTRONICS CO., LTD. 305U1A MonitorsUser.xml: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=b242dbf0-fbe1-4cf8-a5a6-57dd5d749833 ro quiet splash vt.handoff=7 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/29/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 03PS.M505.20110929.LEO dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 305U1A/305U1A dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: 03PS dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr03PS.M505.20110929.LEO:bd09/29/2011:svnSAMSUNGELECTRONICSCO.,LTD.:pn305U1A:pvr03PS:rvnSAMSUNGELECTRONICSCO.,LTD.:rn305U1A/305U1A:rvr03PS:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvrN/A: dmi.product.family: To be filled by O.E.M. dmi.product.name: 305U1A dmi.product.sku: To be filled by O.E.M. dmi.product.version: 03PS dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/gnome-shell-extension-dash-to-panel/+bug/1876516/+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 1877850] Re: strange behaviour of shortcuts in ubuntu 20.04
** Package changed: ubuntu => gnome-shell (Ubuntu) -- 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/1877850 Title: strange behaviour of shortcuts in ubuntu 20.04 Status in gnome-shell package in Ubuntu: New Status in udev package in Ubuntu: New Bug description: There are shortcuts like 'Super + P' to change the display mode or 'Super + l' to go to login screen. However, after i upgraded ubuntu 18.04 to 20.04, if i press P or l or any other character which there is a 'super + key' for it, it's does the same thing. It's like the super key is always on! My keyboard works fine in Unity so it's not a hardware problem. GNOME Shell 3.36.1 Ubuntu 20.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877850/+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 1877828] Re: Missing feature: disable one specific wireless device meanwhile another remain switched on
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1877828 Title: Missing feature: disable one specific wireless device meanwhile another remain switched on Status in network-manager package in Ubuntu: New Bug description: When working on laptop, we may need an external wifi adapter in order to catch a remote access point no working well with the built-in wireless card of the laptop. In such case, it would make sense to disable the internal wireless card in order to have just the external on working. However, Ubuntu does not offer a simple way to do so. Moreover, if I click on "Turn off" for the built-in wifi adapter in the top right corner menu (see the screenshot), both wifi adapters are swtiched off, which is not the desired effect. See for example: https://askubuntu.com/questions/168032/how-to- disable-built-in-wifi-and-use-only-usb-wifi-card To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1877828/+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 1877828] [NEW] Missing feature: disable one specific wireless device meanwhile another remain switched on
You have been subscribed to a public bug: When working on laptop, we may need an external wifi adapter in order to catch a remote access point no working well with the built-in wireless card of the laptop. In such case, it would make sense to disable the internal wireless card in order to have just the external on working. However, Ubuntu does not offer a simple way to do so. Moreover, if I click on "Turn off" for the built-in wifi adapter in the top right corner menu (see the screenshot), both wifi adapters are swtiched off, which is not the desired effect. See for example: https://askubuntu.com/questions/168032/how-to-disable- built-in-wifi-and-use-only-usb-wifi-card ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- Missing feature: disable one specific wireless device meanwhile another remain switched on https://bugs.launchpad.net/bugs/1877828 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager 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 1877850] [NEW] strange behaviour of shortcuts in ubuntu 20.04
You have been subscribed to a public bug: There are shortcuts like 'Super + P' to change the display mode or 'Super + l' to go to login screen. However, after i upgraded ubuntu 18.04 to 20.04, if i press P or l or any other character which there is a 'super + key' for it, it's does the same thing. It's like the super key is always on! My keyboard works fine in Unity so it's not a hardware problem. GNOME Shell 3.36.1 Ubuntu 20.04 LTS ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Affects: udev (Ubuntu) Importance: Undecided Status: New ** Tags: 20.04 bot-comment -- strange behaviour of shortcuts in ubuntu 20.04 https://bugs.launchpad.net/bugs/1877850 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell 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 1865896] Re: totem segfaults on ubuntu-mate 18.04
[Expired for totem (Ubuntu) because there has been no activity for 60 days.] ** Changed in: totem (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1865896 Title: totem segfaults on ubuntu-mate 18.04 Status in totem package in Ubuntu: Expired Bug description: Totem crashes on launch along with the desktop/Xorg. BTW I am not using any dm but only managing my desktop with openbox wm. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: totem 3.26.0-0ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: MATE Date: Tue Mar 3 21:43:10 2020 InstallationDate: Installed on 2018-05-11 (661 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1865896/+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 1857122] Re: New Windows are opened below other windows and require extra clicks to acees
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- 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/1857122 Title: New Windows are opened below other windows and require extra clicks to acees Status in gnome-shell package in Ubuntu: Expired Bug description: Sometimes when opening new windows the new window is opened below other windows. This behaviour is not consistent. Sometimes it happens and sometimes it does not happen. This is rather unpredictable and very frustrating. The problem got horribly worde when moving to a fast computer running Ubuntu 19.10 This behaviour causes typing to go to the wrong window so sometimes when I already start typing expected entry just to discover the actual window I am expecting is hidden and the actual typing goes to the wrong place. This can easily lead to revealing of sensitive information therefore IMHO it should be treated as a security issue. I think this is a security issue because this behaviour is in contradiction with Windows/Mac and Ubuntu (sometimes)' so Me ' as a user' is confused and typing to the wrong place can lead to all sorts of errors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1857122/+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 1867001] Re: ibus-x11 crashed with SIGSEGV in __GI___poll()
[Expired for ibus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ibus (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1867001 Title: ibus-x11 crashed with SIGSEGV in __GI___poll() Status in ibus package in Ubuntu: Expired Bug description: the Ubuntu presents an error ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: ibus 1.5.22-1~exp1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Mar 11 08:51:28 2020 ExecutablePath: /usr/lib/ibus/ibus-x11 InstallationDate: Installed on 2020-03-07 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) ProcCmdline: /usr/lib/ibus/ibus-x11 --kill-daemon ProcEnviron: LANG=pt_BR.UTF-8 LANGUAGE=pt_BR:pt:en PATH=(custom, no user) XDG_RUNTIME_DIR= SHELL=/bin/false SegvAnalysis: Segfault happened at: 0x7fab42711b86 <__run_exit_handlers+198>: mov 0x10(%rax),%rdx PC (0x7fab42711b86) ok source "0x10(%rax)" (0xb1ac969e3c4a0) not located in a known VMA region (needed readable region)! destination "%rdx" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: ibus StacktraceTop: __GI___poll (fds=0x7fff598bf188, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 ?? () from /lib/x86_64-linux-gnu/libxcb.so.1 xcb_wait_for_reply64 () from /lib/x86_64-linux-gnu/libxcb.so.1 _XReply () from /lib/x86_64-linux-gnu/libX11.so.6 Title: ibus-x11 crashed with SIGSEGV in __GI___poll() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1867001/+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 1866552] Re: xorg crashed on totem launch on ubuntu-mate-1804
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1866552 Title: xorg crashed on totem launch on ubuntu-mate-1804 Status in xorg-server package in Ubuntu: Expired Bug description: xorg crashed on totem launch on ubuntu-mate-1804. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: MATE Date: Sun Mar 8 21:47:12 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:8694] NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP108 [GeForce GT 1030] [19da:2476] InstallationDate: Installed on 2018-05-11 (666 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard Bus 001 Device 002: ID 09da:c10a A4Tech Co., Ltd. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-91-generic root=UUID=c14b0e5e-bdb0-4d30-87f0-0879253545d0 ro acpi=force iomem=relaxed random.trust_cpu=on initcall_debug console=tty0 console=ttyS0,115200 earlyprintk=ttyS0,115200 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: Default string dmi.board.name: H110M-E/M.2 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd05/28/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-E/M.2:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1866552/+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 1877269] Re: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large)
If the machine is out of memory then please reboot and then run the 'ubuntu-bug' or 'apport-cli' command. -- 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/1877269 Title: Ubuntu crashes multiple time due to pulse audio. (alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large) Status in pulseaudio package in Ubuntu: Incomplete Bug description: Description: Ubuntu 18.04.4 LTS Release: 18.04 pulseaudio: Installé : 1:11.1-1ubuntu7.5 Candidat : 1:11.1-1ubuntu7.5 Table de version : *** 1:11.1-1ubuntu7.5 500 500 http://fr.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:11.1-1ubuntu7 500 500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages The OS freezes when using in normal conditions, usually VS Code, Discord app and Spotify in browser. When it does, I need to hard reboot by holding power button. I checked journalctl to confirm it was due to pulseaudio. alsa-util.c: snd_pcm_delay() returned a value that is exceptionally large The above line is always the last to prompt in the boot journal. It does not freeze instantly, it progressively freezes down, but sometime Mozilla Firefox crashes and it freezes no more. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.5 Uname: Linux 5.1.15-surface-linux-surface x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: saravanane 2071 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu May 7 11:00:37 2020 InstallationDate: Installed on 2019-10-01 (218 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/18/2019 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 108.2706.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr108.2706.768:bd04/18/2019:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B09F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.sku: Surface_Pro_4 dmi.product.version: D:0B:09F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877269/+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 1870640] Re: Does not register as x-www-browser alternative
** Tags added: packaging -- 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/1870640 Title: Does not register as x-www-browser alternative Status in chromium-browser package in Ubuntu: Fix Released Status in chromium-browser source package in Eoan: In Progress Status in chromium-browser source package in Focal: Fix Committed Bug description: [Impact] Low. When installing chromium-browser in eoan/focal (which is a transitional package that installs the chromium snap), update- alternatives cannot be used to set it as x-www-browser or gnome-www- browser. This is a regression compared to the version of chromium- browser in bionic. [Test case] # update-alternatives --set x-www-browser /usr/bin/chromium-browser update-alternatives: error: alternative /usr/bin/chromium-browser for x-www-browser not registered; not setting [Regression potential] This is fixing a regression by adding back a code snippet that was in the package in bionic and previous releases. If the snippet has incorrect syntax, it could possibly prevent installation of the package. If the package installs fine, it's unlikely that anything could have regressed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1870640/+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 1876415] Re: [nvidia+modeset] Fonts in the GNOME shell not shown.
If you would like to make this bug private there is an option to do that at the top-right of this page. -- 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/1876415 Title: [nvidia+modeset] Fonts in the GNOME shell not shown. Status in gnome-shell package in Ubuntu: Incomplete Bug description: GNOME does not show any text in the DE itself. Examples of text that is missing: The activities button on the top left, date and time, text of notifications, authentication dialogs, the telegram icon not displaying the number of unread messages, searches in the search bar. The text however is drawn in applications that are not an integral part of the shell itself, such as the settings application, terminals, Firefox, Rhythmbox, GNOME System montior. The bug appeared seemingly out of nowhere, can be worked around though pretty easily by chainging the fonts of the user interface in the GNOME tweak tool. The problem reappears, if the user interface fonts are changed back to the fonts which were not appearing on the screen originally. Changing the font size does not fix the problem. 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] Ist ein Verzeichnis: '/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) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 2 04:28:41 2020 DistUpgraded: 2020-04-24 10:02:52,848 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-28-generic, x86_64: installed openrazer-driver, 2.7.0, 5.4.0-26-generic, x86_64: installed openrazer-driver, 2.7.0, 5.4.0-28-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] InstallationDate: Installed on 2019-11-07 (176 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. H97-D3H ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/usr/bin/zsh ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=45a49275-be6c-418c-86a5-c57794b70427 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-24 (7 days ago) dmi.bios.date: 09/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F7 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF7:bd09/19/2015:svnGigabyteTechnologyCo.,Ltd.:pnH97-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: H97-D3H dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/gnome-shell/+bug/1876415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe
[Desktop-packages] [Bug 1877279] Re: my wallpaper is changed after computer sleep
*** This bug is a duplicate of bug 1855757 *** https://bugs.launchpad.net/bugs/1855757 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1855757, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1855757 [nvidia] Background image corrupted after standby -- 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/1877279 Title: my wallpaper is changed after computer sleep Status in gnome-shell package in Ubuntu: Incomplete Bug description: when my laptop goes in sleep then when I log in to the ubuntu my wallpaper changes to a bad picture (the bad picture is the white and black horizontal lines and I should change my wallpaper to get it right --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) NonfreeKernelModules: nvidia Package: gnome-shell 3.36.1-5ubuntu1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 Tags: focal third-party-packages Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877279/+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 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable"
** Summary changed: - [XPS L501X, Realtek ALC665, Speaker, Internal] + [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable" -- 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/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] "Analog Stereo" and "Build-in speaker" appears "unplugged/unavailable" Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and "Build-in speaker" appears "unplugged/unavaiable". I can change it in volume control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and sound does play, but after each reboot computer changes to Digital Stereo IEC985 and do not play sound until changed again. I did reinstall of alsa and pulse according to some forums but this didn't work. Before upgrade everything always worked out of the box since 2009 on this computer. I know it's a little old but it works excellent! Please help. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 09:25:27 2020 InstallationDate: Installed on 2020-02-25 (64 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+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 1857335] Re: System volume slider only works between ~90% and 100%.
** Package changed: gnome-control-center (Ubuntu) => pulseaudio (Ubuntu) ** Summary changed: - System volume slider only works between ~90% and 100%. + System volume slider only works between ~90% and 100% with a USB 2.0 speaker -- 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/1857335 Title: System volume slider only works between ~90% and 100% with a USB 2.0 speaker Status in pulseaudio package in Ubuntu: New Bug description: This is only with my USB 2.0 speaker[1] - with other devices, it works fine and the slider's 0% corresponds to silent and 100% full. With my USB 2.0 speaker, with the 'output' set to 'Analogue Output - USB2.0 Device', it only has an effect between about 90% and 100%. I took a video of the problem and uploaded it here: http://davidmaxwaterman.fastmail.co.uk/xfer/ubuntu_volume_problem.mp4 [1] https://www.amazon.co.uk/gp/product/B07W1KN1XD/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8=1 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-control-center 1:3.34.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 23 10:00:17 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-19 (156 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to eoan on 2019-10-28 (56 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1857335/+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 1838227] Re: Bluetooth "Connection switch" snaps back by itself until after many tries
Christopher, please open a new bug for what you experience by running: ubuntu-bug gnome-shell This bug should stay closed while the original reporter hasn't provided the requested info. ** Changed in: bluez (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838227 Title: Bluetooth "Connection switch" snaps back by itself until after many tries Status in bluez package in Ubuntu: Invalid Bug description: Attempting to slide the "Connection" switch in the gui to connect a bluetooth device fails initially -- the switch moves but "snaps back" by itself immediately. Clicking on the switch flashes the "busy" indicator momentarily, but the switch does not move. After a while, connecting succeeds. I don't know if the mouse input is not recognized until the "Nth" attempt, or else the connection was in-progress all along but the gui was not tracking that correctly. Please watch the attached video (use vlc). NOTE: This system is running a non-standard kernel 5.2 in order to circumvent other problems (see bug 1838180). Again, see the video; there is something wrong with how the GUI communicates with the kernel. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bluez 5.50-0ubuntu2 Uname: Linux 5.2.0-050200-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Jul 28 22:46:28 2019 InstallationDate: Installed on 2019-02-06 (173 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) InterestingModules: bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: innotek GmbH VirtualBox ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic root=UUID=75234048-11af-4901-9f89-2c32581f5dd3 ro quiet splash SourcePackage: bluez UpgradeStatus: Upgraded to disco on 2019-06-27 (31 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH hciconfig: rfkill: syslog: Jul 28 22:42:11 V-M-Ubuntu-Experimental NetworkManager[828]: [1564378931.7693] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.16.0/libnm-device-plugin-bluetooth.so) Jul 28 22:42:22 V-M-Ubuntu-Experimental systemd[1]: Condition check resulted in Bluetooth service being skipped. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1838227/+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 1855757] Re: [nvidia] Background image corrupted after standby
** Tags added: 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/1855757 Title: [nvidia] Background image corrupted after standby Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/gnome-shell/+bug/1855757/+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 1877434] Re: Slow Gnome 3.36 overall experience
Was that used by some extension? Can you please detail what "the problem" was, or where you got that info? -- 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/1877434 Title: Slow Gnome 3.36 overall experience Status in gnome-shell package in Ubuntu: Invalid Bug description: After upgrading from ubuntu 19.10 to 20.04 the boot time was very slow and the overall feel of the desktop wasn't as snappy as it was in previous releases. 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: Thu May 7 21:29:12 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877434/+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 1877547] Re: Dead cursor on 125% scaling on x11
*** This bug is a duplicate of bug 1873052 *** https://bugs.launchpad.net/bugs/1873052 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1873052, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1873052 GNOME 3.36 Lands Scaled/Transformed Hardware Cursors Support and keeps another not scaled cursor mid screen -- 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/1877547 Title: Dead cursor on 125% scaling on x11 Status in gnome-shell package in Ubuntu: Confirmed Bug description: Opening a bug for this since all other bugs that reported this have been closed. On an X11 session, a dead secondary mouse is displayed when the scaling for a user session has been set to 125% (fractional scaling). Presumably, the dead cursor is a left-over from the login screen with 100% scaling. I've attached a photo for reference. Screen capturing/print screen functionality does not capture the dead cursor. Going back to 100% after logging in, then reverting to 125% removes the dead cursor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:44:03 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-08 (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/1877547/+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 1877567] Re: Automatic Login
*** This bug is a duplicate of bug 1845801 *** https://bugs.launchpad.net/bugs/1845801 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1845801, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1845801 [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877567 Title: Automatic Login Status in xorg package in Ubuntu: New Bug description: Problem 1. Switched to automatic login option during the fresh install 2. On a start up Login screen is still shown. 3. Typing correct user name and password does not start the system. 4. End up stuck in login loop Solution 1. Restart system 2. Selected Ubuntu Recovery mode 3. Select normal boot 4. System starts 5. Go to to User Settings and disable automatic login 6. Reboot 7. System starts with login screen 8. Type name and password. 9. system starts ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..06.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:06: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: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 08:04:14 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU116 [GeForce GTX 1650 SUPER] [10de:2187] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd TU116 [GeForce GTX 1650 SUPER] [1458:401b] InstallationDate: Installed on 2020-05-04 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=f070f159-e92a-44d2-9c1b-d791f0e697c6 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: A320M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 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.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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/xorg/+bug/1877567/+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 1877894] Re: "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04
** 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/1877894 Title: "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04 Status in alsa-driver package in Ubuntu: New Bug description: I upgraded my Ubuntu installation from 19.10 to 20.04 and I have lost the ability to connect to any kind of Bluetooth "True Wireless" earphones (Apple AirPods, Galaxy Earpods+, etc). Standard Bluetooth headphones connect correctly but all "True Wireless" style headphones briefly connect then disconnect immediately. bluetoothctl output: ``` [bluetooth]# devices Device C0:28:8D:1D:42:90 Jaybird X3 Device 7C:38:AD:4A:C8:F9 Galaxy Buds (C8F9) Device 40:26:19:DC:12:E6 Apple AirPods [bluetooth]# connect C0:28:8D:1D:42:90 Attempting to connect to C0:28:8D:1D:42:90 [CHG] Device C0:28:8D:1D:42:90 Connected: yes Connection successful [Jaybird X3]# connect 7C:38:AD:4A:C8:F9 ttempting to connect to 7C:38:AD:4A:C8:F9 [CHG] Device 7C:38:AD:4A:C8:F9 Connected: yes Failed to connect: org.bluez.Error.Failed Jaybird X3]# connect 40:26:19:DC:12:E6 Attempting to connect to 40:26:19:DC:12:E6 [CHG] Device 40:26:19:DC:12:E6 Connected: yes Failed to connect: org.bluez.Error.Failed [CHG] Device 40:26:19:DC:12:E6 Connected: no [CHG] Device 40:26:19:DC:12:E6 Connected: yes [CHG] Device 40:26:19:DC:12:E6 Connected: no [Jaybird X3]# ``` ``` $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ``` possible packages involved: -pulseaudio -pulseaudio-module-bluetooth -bluez ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: curtis 8167 F pulseaudio /dev/snd/controlC2: curtis 8167 F pulseaudio /dev/snd/pcmC2D0c: curtis 8167 F...m pulseaudio /dev/snd/controlC0: curtis 8167 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 15:52:42 2020 InstallationDate: Installed on 2019-05-24 (352 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to focal on 2020-05-04 (5 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-AR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd06/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877894/+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 1877894] [NEW] "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04
You have been subscribed to a public bug: I upgraded my Ubuntu installation from 19.10 to 20.04 and I have lost the ability to connect to any kind of Bluetooth "True Wireless" earphones (Apple AirPods, Galaxy Earpods+, etc). Standard Bluetooth headphones connect correctly but all "True Wireless" style headphones briefly connect then disconnect immediately. bluetoothctl output: ``` [bluetooth]# devices Device C0:28:8D:1D:42:90 Jaybird X3 Device 7C:38:AD:4A:C8:F9 Galaxy Buds (C8F9) Device 40:26:19:DC:12:E6 Apple AirPods [bluetooth]# connect C0:28:8D:1D:42:90 Attempting to connect to C0:28:8D:1D:42:90 [CHG] Device C0:28:8D:1D:42:90 Connected: yes Connection successful [Jaybird X3]# connect 7C:38:AD:4A:C8:F9 ttempting to connect to 7C:38:AD:4A:C8:F9 [CHG] Device 7C:38:AD:4A:C8:F9 Connected: yes Failed to connect: org.bluez.Error.Failed Jaybird X3]# connect 40:26:19:DC:12:E6 Attempting to connect to 40:26:19:DC:12:E6 [CHG] Device 40:26:19:DC:12:E6 Connected: yes Failed to connect: org.bluez.Error.Failed [CHG] Device 40:26:19:DC:12:E6 Connected: no [CHG] Device 40:26:19:DC:12:E6 Connected: yes [CHG] Device 40:26:19:DC:12:E6 Connected: no [Jaybird X3]# ``` ``` $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 ``` possible packages involved: -pulseaudio -pulseaudio-module-bluetooth -bluez ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: curtis 8167 F pulseaudio /dev/snd/controlC2: curtis 8167 F pulseaudio /dev/snd/pcmC2D0c: curtis 8167 F...m pulseaudio /dev/snd/controlC0: curtis 8167 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 15:52:42 2020 InstallationDate: Installed on 2019-05-24 (352 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to focal on 2020-05-04 (5 days ago) dmi.bios.date: 06/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1204 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-AR dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1204:bd06/20/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-AR:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- "True Wireless" Bluetooth headsets not connecting in Ubuntu 20.04 https://bugs.launchpad.net/bugs/1877894 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 1877547] Re: Dead cursor on 125% scaling on x11
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877547 Title: Dead cursor on 125% scaling on x11 Status in gnome-shell package in Ubuntu: Confirmed Bug description: Opening a bug for this since all other bugs that reported this have been closed. On an X11 session, a dead secondary mouse is displayed when the scaling for a user session has been set to 125% (fractional scaling). Presumably, the dead cursor is a left-over from the login screen with 100% scaling. I've attached a photo for reference. Screen capturing/print screen functionality does not capture the dead cursor. Going back to 100% after logging in, then reverting to 125% removes the dead cursor. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 8 17:44:03 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-05-08 (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/1877547/+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 1877528] Re: Applet does not terminate at end of X desktop session
This bug was reported three years ago in Debian: https://bugs.debian.org/863227 ** Bug watch added: Debian Bug tracker #863227 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863227 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to system-config-printer in Ubuntu. https://bugs.launchpad.net/bugs/1877528 Title: Applet does not terminate at end of X desktop session Status in system-config-printer package in Ubuntu: New Bug description: This concerns system-config-printer 1.5.12-0ubuntu1 in Ubuntu focal. I log into the Xfce desktop, and then logout. The screen returns to the LightDM login screen. A few minutes later, "loginctl list-sessions" shows the following: SESSION UID USERSEAT TTY 90 root c2 1000 skunk seat0 c3 116 lightdm seat0 3 sessions listed. Output from "loginctl session-status c2": c2 - skunk (1000) Since: Fri 2020-05-08 03:09:05 EDT; 9min ago Leader: 2530 Seat: seat0; vc7 Display: :0 Service: lightdm; type x11; class user Desktop: xubuntu State: closing Unit: session-c2.scope └─2856 /usr/bin/python3 /usr/share/system-config-printer/applet.py This process sticks around forever until I kill it, or its parent "systemd --user" process. Only then does the session disappear from list-sessions. When I run "session-status" while I'm logged in, I see a list of nearly 30 desktop-related processes. All of them except this one go away on logout. This one should too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-config-printer/+bug/1877528/+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 1741045] Re: Change the default resample-method to speex-float-N (N > 1) in daemon.conf
** Changed in: pulseaudio Status: Unknown => Fix Released ** Changed in: pulseaudio Importance: Wishlist => Unknown -- 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/1741045 Title: Change the default resample-method to speex-float-N (N > 1) in daemon.conf Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: New Bug description: I suggest changing the default resample-method to speex-float-10, instead of speex-float-1, which is the current default now, in /etc/pulse/daemon.conf. It would look like this in daemon.conf: resample-method = speex-float-10 I have always done that since at least 12.04 LTS. I was not satisfied with the sound quality in Ubuntu compared to Windows, so I changed the resample-method. In my day-to-day usage, it gives better sound quality without sacrificing CPU power. I have not tried other resample methods. Maybe there are better options I don't know about. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13 Uname: Linux 4.13.0-19-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: amr1696 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Jan 3 14:37:25 2018 InstallationDate: Installed on 2017-10-02 (92 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/08/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-S2P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-S2P dmi.sys.vendor: Gigabyte Technology Co., Ltd. modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2017-10-05T12:39:48.718018 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1741045/+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 1877891] Re: Firefox does not play streams
** Summary changed: - Firefox does not play live streams + Firefox does not play streams ** Description changed: - Since I did a fresh install of Ubuntu 20.04 on my laptop livestreams on twitch tv and youtube don't play anymore. This is extra strange because - - It works on 20.04 Kubuntu on my workstation (it has the exact same extension and settings) - - It works in chormium browser - - Normal videos work + Since I did a fresh install of Ubuntu 20.04 on my laptop livestreams on twitch.tv and youtube don't play anymore. Also twitter videos don't seem tp work. + This is extra strange because + - It works on 20.04 Kubuntu on my workstation (it has the exact same extension and settings) + - It works in chormium browser + - Normal videos work I've already tried: - - Reinstalling firefox - - deleting the ~/.mozilla folder and using firefox with a freshly generated one - - using safe-mode + - Reinstalling firefox + - deleting the ~/.mozilla folder and using firefox with a freshly generated one + - using safe-mode None of those changed anything ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 76.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jesko 1080 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jesko 1080 F pulseaudio BuildID: 20200429185419 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 10 21:02:11 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 DefaultProfilePrefSources: prefs.js DefaultProfilePrefs: - extensions.lastAppVersion: "73.0.1" (prefs.js) - security.sandbox.content.tempDirSuffix: "e28738aa-dad9-4b48-b315-6ebeb3ccf3df" (prefs.js) - security.sandbox.plugin.tempDirSuffix: "19210103-39c1-4a97-bef8-a6f4a9e3526e" (prefs.js) + extensions.lastAppVersion: "73.0.1" (prefs.js) + security.sandbox.content.tempDirSuffix: "e28738aa-dad9-4b48-b315-6ebeb3ccf3df" (prefs.js) + security.sandbox.plugin.tempDirSuffix: "19210103-39c1-4a97-bef8-a6f4a9e3526e" (prefs.js) DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: - default via 192.168.178.1 dev wlp0s20f3 proto dhcp metric 600 - 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 - 192.168.178.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.178.107 metric 600 + default via 192.168.178.1 dev wlp0s20f3 proto dhcp metric 600 + 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 + 192.168.178.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.178.107 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: - Profile1 (Default) - LastVersion=75.0/20200403170909 (Out of date) - Profile0 - LastVersion=76.0/20200429185419 (In use) + Profile1 (Default) - LastVersion=75.0/20200403170909 (Out of date) + Profile0 - LastVersion=76.0/20200429185419 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET47W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QFS10B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QFS10B00 dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1877891 Title:
[Desktop-packages] [Bug 1872681] Re: Overview shortcut does not work on non-latin keyboard layout
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 Hi, I found that not only super key not working but also ctrl. You can enable showing pointer on ctrl click and try. These keyes work only for first and 4-th layout(second, third, fifth and other not work properly). It does not matter if layout is latin or not. -- 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/1872681 Title: Overview shortcut does not work on non-latin keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hello, Latest Ubuntu 20.04. After latest upgrade the shortcut key for the Overview (Expose?) function doesn't work on non-latin keyboard layout: 1. Switch current input language to Russian 2. Press Super key. 3. Nothing happens 4. Switch language to English 5. Press Super key 6. Windows overview screen is opened /usr/bin/xev reports the same keyscan for the button, if that matters. Other Super- shortcuts (like Super-`) do work in any keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 13:00:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (124 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872681/+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 1877891] Re: Firefox does not play live streams
** Attachment added: "twitch.tv" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1877891/+attachment/5369601/+files/Screenshot%20from%202020-05-10%2021-32-46.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1877891 Title: Firefox does not play live streams Status in firefox package in Ubuntu: New Bug description: Since I did a fresh install of Ubuntu 20.04 on my laptop livestreams on twitch tv and youtube don't play anymore. This is extra strange because - It works on 20.04 Kubuntu on my workstation (it has the exact same extension and settings) - It works in chormium browser - Normal videos work I've already tried: - Reinstalling firefox - deleting the ~/.mozilla folder and using firefox with a freshly generated one - using safe-mode None of those changed anything ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 76.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jesko 1080 F pulseaudio BuildID: 20200429185419 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 10 21:02:11 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 DefaultProfilePrefSources: prefs.js DefaultProfilePrefs: extensions.lastAppVersion: "73.0.1" (prefs.js) security.sandbox.content.tempDirSuffix: "e28738aa-dad9-4b48-b315-6ebeb3ccf3df" (prefs.js) security.sandbox.plugin.tempDirSuffix: "19210103-39c1-4a97-bef8-a6f4a9e3526e" (prefs.js) DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.178.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.178.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.178.107 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=75.0/20200403170909 (Out of date) Profile0 - LastVersion=76.0/20200429185419 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET47W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QFS10B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QFS10B00 dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1877891/+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 1877875] Re: Pressing Alt+F1 with mouse cursor over the Applcations leads to focus move to Applications, the menus are unusable as result
Caused by some mess with customizations from other flavors. The normally installed Ubuntu MATE is not affected. ** Changed in: gtk+3.0 (Ubuntu) Status: New => Invalid ** Changed in: mate-panel (Ubuntu) Status: New => Incomplete ** Changed in: mate-panel (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877875 Title: Pressing Alt+F1 with mouse cursor over the Applcations leads to focus move to Applications, the menus are unusable as result Status in gtk+3.0 package in Ubuntu: Invalid Status in mate-panel package in Ubuntu: Invalid Bug description: Steps to reproduce: 1. Have Ubuntu MATE 20.04 LTS installed 2. Login to session, choose Traditional desktop layout in MATE Tweak 3. Move move cursor over Applications menu 4. Press + to open Applications menu 5. Press or Expected results: * focus moves with or to corresponding one of the menu items - Applications, Places, System Actual results: * focus is stuck on Applications menu, about which mouse cursor is located (see screencast) ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: mate-panel 1.24.0-2 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30 Uname: Linux 5.4.0-29-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun May 10 18:57:48 2020 InstallationDate: Installed on 2020-04-22 (17 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877875/+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 1877891] Re: Firefox does not play live streams
** Attachment added: "https://www.youtube.com/watch?v=5qap5aO4i9A; https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1877891/+attachment/5369602/+files/Screenshot%20from%202020-05-10%2021-33-32.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1877891 Title: Firefox does not play live streams Status in firefox package in Ubuntu: New Bug description: Since I did a fresh install of Ubuntu 20.04 on my laptop livestreams on twitch tv and youtube don't play anymore. This is extra strange because - It works on 20.04 Kubuntu on my workstation (it has the exact same extension and settings) - It works in chormium browser - Normal videos work I've already tried: - Reinstalling firefox - deleting the ~/.mozilla folder and using firefox with a freshly generated one - using safe-mode None of those changed anything ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 76.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jesko 1080 F pulseaudio BuildID: 20200429185419 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 10 21:02:11 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 DefaultProfilePrefSources: prefs.js DefaultProfilePrefs: extensions.lastAppVersion: "73.0.1" (prefs.js) security.sandbox.content.tempDirSuffix: "e28738aa-dad9-4b48-b315-6ebeb3ccf3df" (prefs.js) security.sandbox.plugin.tempDirSuffix: "19210103-39c1-4a97-bef8-a6f4a9e3526e" (prefs.js) DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.178.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.178.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.178.107 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=75.0/20200403170909 (Out of date) Profile0 - LastVersion=76.0/20200429185419 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET47W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QFS10B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QFS10B00 dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1877891/+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 1877891] [NEW] Firefox does not play live streams
Public bug reported: Since I did a fresh install of Ubuntu 20.04 on my laptop livestreams on twitch tv and youtube don't play anymore. This is extra strange because - It works on 20.04 Kubuntu on my workstation (it has the exact same extension and settings) - It works in chormium browser - Normal videos work I've already tried: - Reinstalling firefox - deleting the ~/.mozilla folder and using firefox with a freshly generated one - using safe-mode None of those changed anything ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 76.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jesko 1080 F pulseaudio BuildID: 20200429185419 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 10 21:02:11 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 DefaultProfilePrefSources: prefs.js DefaultProfilePrefs: extensions.lastAppVersion: "73.0.1" (prefs.js) security.sandbox.content.tempDirSuffix: "e28738aa-dad9-4b48-b315-6ebeb3ccf3df" (prefs.js) security.sandbox.plugin.tempDirSuffix: "19210103-39c1-4a97-bef8-a6f4a9e3526e" (prefs.js) DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2020-05-09 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IpRoute: default via 192.168.178.1 dev wlp0s20f3 proto dhcp metric 600 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 192.168.178.0/24 dev wlp0s20f3 proto kernel scope link src 192.168.178.107 metric 600 Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:738 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=75.0/20200403170909 (Out of date) Profile0 - LastVersion=76.0/20200429185419 (In use) RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET47W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QFS10B00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2HET47W(1.30):bd03/18/2020:svnLENOVO:pn20QFS10B00:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20QFS10B00:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20QFS10B00 dmi.product.sku: LENOVO_MT_20QF_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO ** Affects: firefox (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 firefox in Ubuntu. https://bugs.launchpad.net/bugs/1877891 Title: Firefox does not play live streams Status in firefox package in Ubuntu: New Bug description: Since I did a fresh install of Ubuntu 20.04 on my laptop livestreams on twitch tv and youtube don't play anymore. This is extra strange because - It works on 20.04 Kubuntu on my workstation (it has the exact same extension and settings) - It works in chormium browser - Normal videos work I've already tried: - Reinstalling firefox - deleting the ~/.mozilla folder and using firefox with a freshly generated one - using safe-mode None of those changed anything ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 76.0+build2-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jesko 1080 F pulseaudio BuildID: 20200429185419 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun May 10 21:02:11 2020 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant
[Desktop-packages] [Bug 1872681] Re: Overview shortcut does not work on non-latin keyboard layout
*** This bug is a duplicate of bug 1871913 *** https://bugs.launchpad.net/bugs/1871913 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872681 Title: Overview shortcut does not work on non-latin keyboard layout Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hello, Latest Ubuntu 20.04. After latest upgrade the shortcut key for the Overview (Expose?) function doesn't work on non-latin keyboard layout: 1. Switch current input language to Russian 2. Press Super key. 3. Nothing happens 4. Switch language to English 5. Press Super key 6. Windows overview screen is opened /usr/bin/xev reports the same keyscan for the button, if that matters. Other Super- shortcuts (like Super-`) do work in any keyboard layout. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 13:00:36 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-11 (124 days ago) InstallationMedia: Ubuntu-Server 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 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/1872681/+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 1877887] [NEW] [USB-Audio - Scarlett 2i2 USB, playback] fails after a while
Public bug reported: I am encountering some very bizarre and difficult to reliably replicate issues. I am using a Focusrite Scarlett 2i2 USB audio interface, and am having a number of issues that I did not have in older version of ubuntu (these issues started occuring sometime in 19.04-19.10, can't remember which). I am having three major issues. Number one is, if USB autosuspend is enabled, it will stop working completely until reboot after anywhere from a few minutes to several hours. Reconnecting the device does not fix it and it seems to not power on at all, with dmesg reporting a "usb_set_interface failed -110" error. Sometimes this bug can be recreated by manually disconnecting and reconnecting the device, however I was unable to replicate it in this manner at the time of filing the bug. Another (presumably related) issue I am having is that if I reconnect the device and it doesn't fail, it outputs very crackly audio, as if the bitrate or sample rate were set incorrectly. This persists until a restart of pulseaudio. Previously, I had a similar bug where it would randomly start doing the crackly audio thing until reconnecting the device and in this case a restart of pulse did *not* fix the problem. I am unsure if this issue still happens as it was fairly rare. The third problem is that sometimes when performing a suspend/wake cycle, the interface will power cycle several times, in intervals of 15-30 seconds or so before staying on properly. As previously mentioned, these issues are fairly new and did not occur in older versions of ubuntu. I have confirmed that the audio interface works fine under windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 10 14:09:28 2020 InstallationDate: Installed on 2020-05-08 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB-Audio - microKEY-37 Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Gaming K4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. ** Affects: alsa-driver (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 alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1877887 Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: I am encountering some very bizarre and difficult to reliably replicate issues. I am using a Focusrite Scarlett 2i2 USB audio interface, and am having a number of issues that I did not have in older version of ubuntu (these issues started occuring sometime in 19.04-19.10, can't remember which). I am having three major issues. Number one is, if USB autosuspend is enabled, it will stop working completely until reboot after anywhere from a few minutes to several hours. Reconnecting the device does not fix it and it seems to not power on at all, with dmesg reporting a "usb_set_interface failed -110" error. Sometimes this bug can be recreated by manually disconnecting and reconnecting the device, however I was unable to replicate it in this manner at the time of filing the bug. Another (presumably related) issue I am having is that if I reconnect the device and it doesn't fail, it outputs very crackly audio, as if the bitrate or sample rate were set incorrectly. This persists until a restart of pulseaudio. Previously, I had a similar bug where it would randomly start doing the crackly audio thing until reconnecting the device and in this case a restart of pulse did *not* fix the problem. I am unsure if this issue still happens as it was fairly rare. The third problem is that sometimes when performing a suspend/wake cycle, the interface will power cycle several times, in intervals of 15-30 seconds or so
[Desktop-packages] [Bug 1873764] Re: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id
see comment #3, forgot to add: sudo apparmor_status 4 processes are in enforce mode. /usr/sbin/cups-browsed (188070) /usr/sbin/cupsd (188069) /usr/lib/cups/notifier/dbus (188098) /usr/sbin/cupsd /snap/canonical-livepatch/95/canonical-livepatchd (956) snap.canonical-livepatch.canonical-livepatchd dmesg: [42055.571610] audit: type=1400 audit(1589134509.618:1427): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=188069 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Using: sudo aa-complain usr.sbin.cupsd sudo aa-complain /usr/sbin/cups-browsed removed the error messages. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1873764 Title: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id Status in cups package in Ubuntu: Confirmed Bug description: I noted the following messages on a just installed Ubuntu Focal: $ dmesg | grep cups [ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 comm="cups-browsed" capability=23 capname="sys_nice" [ 1776.623181] audit: type=1400 audit(1587372145.693:3012): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15510 comm="cups-browsed" capability=23 capname="sys_nice" [ 2040.426033] audit: type=1400 audit(1587372409.494:3013): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426044] audit: type=1400 audit(1587372409.494:3014): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426074] audit: type=1400 audit(1587372409.494:3015): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426092] audit: type=1400 audit(1587372409.494:3016): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426106] audit: type=1400 audit(1587372409.494:3017): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404914] audit: type=1400 audit(1587372410.473:3018): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404920] audit: type=1400 audit(1587372410.473:3019): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404926] audit: type=1400 audit(1587372410.473:3020): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404953] audit: type=1400 audit(1587372410.473:3021): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404963] audit: type=1400 audit(1587372410.473:3022): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925327] audit: type=1400 audit(1587372440.994:3028): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925330] audit: type=1400 audit(1587372440.994:3029): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925337] audit: type=1400 audit(1587372440.994:3030): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925382] audit: type=1400 audit(1587372440.994:3031): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925391] audit: type=1400 audit(1587372440.994:3032): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r"
[Desktop-packages] [Bug 704623] Re: Thunderbird renders system unusable / uses 100% CPU while indexing new messages
Launchpad has imported 95 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=493000. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2009-03-31T08:19:08+00:00 redhat wrote: Description of problem: Since upgrading to thunderbird 3 beta my x86_64 WS. is having semi long periods of 100% cpu usage. My i686 laptop with the same setup does not show this. I have two IMAP accounts, both woth several Gigabyte of mail in multiple folders, some with a few hundred thousand messages. Automatich check for new messages is turned OFF for both accounts, and junk filter in thunderbird is disabled. I even tried to rm -Rf the thunderbird profile-folder and set up the accounts from scrath, but the problem persists. As mentioned this only happens on x86_64 and was not an issue with Thunderbird 2 (I downgraded to the latest Thunderbird 2 package to check, and the problem disappeared). Version-Release number of selected component (if applicable): thunderbird-3.0-2.1.beta2.fc11.x86_64 How reproducible: Always Steps to Reproduce: 1. Run thunderbird (v3 beta) 2. 3. Actual results: Every 10-15 minutes thunderbird freezes and cpu usage peaks at 100% for 2-3 minutes. Expected results: Thunderbird should run smooth all the time Additional info: Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/704623/comments/0 On 2009-03-31T11:12:05+00:00 mcepl wrote: Hmm, I am exactly the same configuration here and cannot reproduce it. Is there something more which could help us to reproduce it here. For example, which filesystem you use for your /home directory? Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/704623/comments/1 On 2009-03-31T11:20:13+00:00 redhat wrote: /home is actually on NFS, but that is the same for both the (i686) laptop and the (x86_64) workstation. To be sure NFS is not the problem I have moved the profile from $HOME/.thunderbird/ to a local filesystem and added a symlink: lrwxrwxrwx. 1 olen olen 42 2007-09-17 19:34 .thunderbird/gwagla2i.jobb -> /var/cache/olen/thunderbird/gwagla2i.jobb/ /var/cache is part of / which is LVM with ext3 $ df /var/cache/olen/thunderbird/gwagla2i.jobb/ Filesystem1K-blocks Used Available Use% Mounted on /dev/mapper/VolGroup00-LogVol00 149248172 35944648 105599768 26% / When stracing the process I can't see anything special, but please let me know if there is anything else I can do to debug this. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/704623/comments/2 On 2009-03-31T11:33:36+00:00 mcepl wrote: First of all, could we get output of the command rpm -qa *xulrun* *thunderbird* *mozilla* *flash* *plugin* Please also install thunderbird-debuginfo (debuginfo-install is from yum-utils package). debuginfo-install thunderbird Then run thunderbird and connect to it with gdb by command gdb --pid=$(pidof thunderbird-bin) Then make thunderbird work again with command (gdb) cont and do whatever you did to make thunderbird freeze. When it happens, you should go back to the gdb and run (gdb) thread apply all backtrace This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment. We will review this issue again once you've had a chance to attach this information. Thanks in advance. Reply at: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/704623/comments/3 On 2009-03-31T11:47:12+00:00 redhat wrote: Here is the rpm -qa -output. Attaching gdb-output as soon as I have it: # rpm -qa *xulrun* *thunderbird* *mozilla* *flash* *plugin* PackageKit-yum-plugin-0.4.6-0.3.20090324git.fc11.x86_64 plymouth-plugin-spinfinity-0.7.0-0.2009.03.10.2.fc11.x86_64 gstreamer-plugins-base-0.10.22-2.fc11.x86_64 mozilla-filesystem-1.9-4.fc11.x86_64 nspluginwrapper-1.3.0-5.fc11.x86_64 plymouth-plugin-label-0.7.0-0.2009.03.10.2.fc11.x86_64 alsa-plugins-pulseaudio-1.0.18-3.fc11.x86_64 setroubleshoot-plugins-2.0.14-2.fc11.noarch yum-plugin-refresh-updatesd-1.1.21-2.fc11.noarch gutenprint-plugin-5.2.3-5.fc11.x86_64 xulrunner-1.9.1-0.11.beta3.fc11.x86_64 xfce4-mailwatch-plugin-1.1.0-3.fc11.x86_64 gstreamer-plugins-good-0.10.14-2.fc11.x86_64 gstreamer-plugins-farsight-0.12.10-2.fc11.x86_64 plymouth-plugin-pulser-0.7.0-0.2009.03.10.2.fc11.x86_64 yum-plugin-fastestmirror-1.1.21-2.fc11.noarch
[Desktop-packages] [Bug 1877884] [NEW] OpenVSwitch Support: no package for `nm-openvswitch`
Public bug reported: Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected: Running the following: `nmcli con up ovs-mgmt1` `nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal` Should raise the ovs interface(es) defined. Actual results: `Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable` `Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable` `Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument: As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Description changed: Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. - Expected: - Running the following: - `nmcli con up ovs-mgmt1` - `nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal` - Should raise the ovs interface(es) defined. - + Running the following: + ``` + nmcli con up ovs-mgmt1 + nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal + ``` + Should raise the ovs interface(es) defined. Actual results: - `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable` - `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable` - `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` + `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable` + `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable` + `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised - Argument: - As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. + As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. ** Description changed: Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected: Running the following: ``` nmcli con up ovs-mgmt1 - nmcli connection add type ovs-interface con-name mgmt1 ifname mgmt1 ip4 192.168.16.2/24 gw4 192.168.16.1 master internal + nmcli connection add type ovs-interface \ + con-name mgmt1 ifname mgmt1 \ + ip4 192.168.16.2/24 gw4 192.168.16.1 master internal ``` Should raise the ovs interface(es) defined. Actual results: `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable` `Error: Connection activation failed: NetworkManager plugin for 'ovs-port' unavailable` `Error: Connection activation failed: NetworkManager plugin for 'ovs-bridge' unavailable` *depending on interface type being raised Argument: As of the release of rpm distros {CentOS,RHEL} 8.x there is no standard method to raise OVS interfaces without resorting to depricated ifscripts. deb based releases dropped NetworkManager nm-* support for OVS in favor of networkd. rpm based releases have dropped networkd in favor of NetworkManager. ** Description changed: Ubuntu 20.04 LTS Package Version: NA Issue: Ubuntu NetworkManager packages for Ubuntu 20.04+ lack OVS support. Expected: Running the following: ``` - nmcli con up ovs-mgmt1 nmcli connection add type ovs-interface \ - con-name mgmt1 ifname mgmt1 \ - ip4 192.168.16.2/24 gw4 192.168.16.1 master internal + con-name mgmt1 ifname mgmt1 \ + ip4 192.168.16.2/24 gw4 192.168.16.1 master internal + nmcli con up ovs-mgmt1 ``` Should raise the ovs interface(es) defined. Actual results: `Error: Connection activation failed: NetworkManager plugin for 'ovs-interface' unavailable` `Error: Connection activation failed:
[Desktop-packages] [Bug 1873764] Re: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id
Same happens for HP Laser 107 with driver installed from https://support.hp.com/us-en/drivers/selfservice/hp-laser-100-printer- series/24494339/model/24494342 using cups with cups error "Filter failed" when printing. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1873764 Title: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id Status in cups package in Ubuntu: Confirmed Bug description: I noted the following messages on a just installed Ubuntu Focal: $ dmesg | grep cups [ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 comm="cups-browsed" capability=23 capname="sys_nice" [ 1776.623181] audit: type=1400 audit(1587372145.693:3012): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15510 comm="cups-browsed" capability=23 capname="sys_nice" [ 2040.426033] audit: type=1400 audit(1587372409.494:3013): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426044] audit: type=1400 audit(1587372409.494:3014): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426074] audit: type=1400 audit(1587372409.494:3015): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426092] audit: type=1400 audit(1587372409.494:3016): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426106] audit: type=1400 audit(1587372409.494:3017): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404914] audit: type=1400 audit(1587372410.473:3018): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404920] audit: type=1400 audit(1587372410.473:3019): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404926] audit: type=1400 audit(1587372410.473:3020): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404953] audit: type=1400 audit(1587372410.473:3021): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404963] audit: type=1400 audit(1587372410.473:3022): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925327] audit: type=1400 audit(1587372440.994:3028): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925330] audit: type=1400 audit(1587372440.994:3029): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925337] audit: type=1400 audit(1587372440.994:3030): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925382] audit: type=1400 audit(1587372440.994:3031): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925391] audit: type=1400 audit(1587372440.994:3032): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 It happened after installing Brother DCPL3550CDW Linux drivers. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cups-daemon 2.3.1-9ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-lowlatency 5.4.30 Uname: Linux 5.4.0-25-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME
[Desktop-packages] [Bug 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]
I have a Dell XPS L501X with exactly the same problem. The fix above: > volume control -> configuration to Analog Stereo Duplex (unplugged) I the only thing that has worked for me. I've tried multiple other suggestions on other sites, include renaming .config/pulse folder then reboot, force-reload of alsa, removing the pulse-audio and alsa-base packages from the system, and reinstalling them, and reviewing all settings in alsa mixer. Ubuntu works perfectly on this laptop. I had 19.04 previously, and sound worked fine. An upgrade to 20.04 didn't work as selecting the nVidia video driver nvidia-driver-390 would not let the OS boot into the GUI. What is strange is a complete wipe and reinstall of 20.04 from scratch worked fine, and that video driver was selected automatically. I'm so glad I found this post, as I now have sound again. For now I'm content changing the setting by hand after a 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/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and "Build-in speaker" appears "unplugged/unavaiable". I can change it in volume control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and sound does play, but after each reboot computer changes to Digital Stereo IEC985 and do not play sound until changed again. I did reinstall of alsa and pulse according to some forums but this didn't work. Before upgrade everything always worked out of the box since 2009 on this computer. I know it's a little old but it works excellent! Please help. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 09:25:27 2020 InstallationDate: Installed on 2020-02-25 (64 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+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 1877879] [NEW] segfault in iris_dri.so
Public bug reported: As of Ubuntu 20.04, on intel graphics with intel driver (not modesetting), I got segfault whenever anything tries to use GL. This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One says that it does not happen with modesetting driver. (gdb) run Starting program: /usr/bin/glxgears [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x717cf700 (LWP 97070)] [New Thread 0x7fffebfff700 (LWP 97071)] [New Thread 0x70fce700 (LWP 97072)] [New Thread 0x7fffeb7fe700 (LWP 97073)] Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault. 0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (gdb) where #0 0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #1 0x76c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x76a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x76a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x76099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x711e in ?? () #6 0x6c88 in ?? () #7 0x77ace0b3 in __libc_start_main (main=0x6410, argc=1, argv=0x7fffe698, init=, fini=, rtld_fini=, stack_end=0x7fffe688) at ../csu/libc-start.c:308 #8 0x6f0a in ?? () (gdb) I believe, this is a bug in mesa tracked here: https://gitlab.freedesktop.org/mesa/mesa/issues/1358 packages versions: libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 amd64 xserver-xorg-video-intel 2:2.99.917+git20200226-1amd64 xserver-xorg-core 2:1.20.8-2ubuntu2 amd64 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1877879 Title: segfault in iris_dri.so Status in mesa package in Ubuntu: New Bug description: As of Ubuntu 20.04, on intel graphics with intel driver (not modesetting), I got segfault whenever anything tries to use GL. This happens unless I export MESA_LOADER_DRIVER_OVERRIDE=i965. One says that it does not happen with modesetting driver. (gdb) run Starting program: /usr/bin/glxgears [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [New Thread 0x717cf700 (LWP 97070)] [New Thread 0x7fffebfff700 (LWP 97071)] [New Thread 0x70fce700 (LWP 97072)] [New Thread 0x7fffeb7fe700 (LWP 97073)] Thread 1 "glxgears" received signal SIGSEGV, Segmentation fault. 0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so (gdb) where #0 0x76a7e1d4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #1 0x76c42de4 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #2 0x76a59e5d in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #3 0x76a5aa95 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x76099774 in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x711e in ?? () #6 0x6c88 in ?? () #7 0x77ace0b3 in __libc_start_main (main=0x6410, argc=1, argv=0x7fffe698, init=, fini=, rtld_fini=, stack_end=0x7fffe688) at ../csu/libc-start.c:308 #8 0x6f0a in ?? () (gdb) I believe, this is a bug in mesa tracked here: https://gitlab.freedesktop.org/mesa/mesa/issues/1358 packages versions: libgl1-mesa-dri:amd64 20.0.4-2ubuntu1 amd64 xserver-xorg-video-intel 2:2.99.917+git20200226-1 amd64 xserver-xorg-core 2:1.20.8-2ubuntu2 amd64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1877879/+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 1855757] Re: [nvidia] Background image corrupted after standby
Bug also affects Ubuntu 20.04 -- 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/1855757 Title: [nvidia] Background image corrupted after standby Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Bug description: Looks similar to https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1809407 When the computer goes to standby, the background image becomes corrupted. I am able to fix by "killall Xorg" , change the background image (settings > background) and restart. Haven't tried login logout. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: 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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Dec 9 10:58:35 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 5.3.0-23-generic, x86_64: installed nvidia-340, 340.107, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GT215M [GeForce GTS 360M] [1043:203c] InstallationDate: Installed on 2019-11-29 (10 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: ASUSTek Computer Inc. G60JX ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=65117975-c95f-4406-a7cf-da912cda0e70 ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G60JX dmi.board.vendor: PEGATRON CORPORATION dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: PEGATRON Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd12/25/2009:svnASUSTekComputerInc.:pnG60JX:pvr1.0:rvnPEGATRONCORPORATION:rnG60JX:rvr1.0:cvnPEGATRONComputerInc.:ct10:cvr1.0: dmi.product.family: PEGA Family dmi.product.name: G60JX dmi.product.sku: 0 dmi.product.version: 1.0 dmi.sys.vendor: ASUSTek Computer Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-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+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 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/gnome-shell/+bug/1855757/+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 1877876] Re: white line at gedit with the dark windows skin
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1857191, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1877876 Title: white line at gedit with the dark windows skin Status in gedit package in Ubuntu: New Bug description: With the dark window skin enabled type marker in gedit turns into a white line, so you can't see what your typing. Description: Ubuntu 20.04 LTS Release: 20.04 gedit: Geïnstalleerd: 3.36.1-1 Kandidaat: 3.36.1-1 Versietabel: *** 3.36.1-1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1877876/+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 1877876] [NEW] white line at gedit with the dark windows skin
Public bug reported: With the dark window skin enabled type marker in gedit turns into a white line, so you can't see what your typing. Description:Ubuntu 20.04 LTS Release:20.04 gedit: Geïnstalleerd: 3.36.1-1 Kandidaat: 3.36.1-1 Versietabel: *** 3.36.1-1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Schermafdruk van 2020-05-10 17-08-43.png" https://bugs.launchpad.net/bugs/1877876/+attachment/5369529/+files/Schermafdruk%20van%202020-05-10%2017-08-43.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1877876 Title: white line at gedit with the dark windows skin Status in gedit package in Ubuntu: New Bug description: With the dark window skin enabled type marker in gedit turns into a white line, so you can't see what your typing. Description: Ubuntu 20.04 LTS Release: 20.04 gedit: Geïnstalleerd: 3.36.1-1 Kandidaat: 3.36.1-1 Versietabel: *** 3.36.1-1 500 500 http://nl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1877876/+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 1877875] [NEW] Pressing Alt+F1 with mouse cursor over the Applcations leads to focus move to Applications, the menus are unusable as result
Public bug reported: Steps to reproduce: 1. Have Ubuntu MATE 20.04 LTS installed 2. Login to session, choose Traditional desktop layout in MATE Tweak 3. Move move cursor over Applications menu 4. Press + to open Applications menu 5. Press or Expected results: * focus moves with or to corresponding one of the menu items - Applications, Places, System Actual results: * focus is stuck on Applications menu, about which mouse cursor is located (see screencast) ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: mate-panel 1.24.0-2 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30 Uname: Linux 5.4.0-29-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun May 10 18:57:48 2020 InstallationDate: Installed on 2020-04-22 (17 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Affects: mate-panel (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "menus.gif" https://bugs.launchpad.net/bugs/1877875/+attachment/5369525/+files/menus.gif ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1877875 Title: Pressing Alt+F1 with mouse cursor over the Applcations leads to focus move to Applications, the menus are unusable as result Status in gtk+3.0 package in Ubuntu: New Status in mate-panel package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu MATE 20.04 LTS installed 2. Login to session, choose Traditional desktop layout in MATE Tweak 3. Move move cursor over Applications menu 4. Press + to open Applications menu 5. Press or Expected results: * focus moves with or to corresponding one of the menu items - Applications, Places, System Actual results: * focus is stuck on Applications menu, about which mouse cursor is located (see screencast) ProblemType: Bug DistroRelease: Ubuntu Kylin 20.04 Package: mate-panel 1.24.0-2 [origin: Ubuntu] ProcVersionSignature: Ubuntu 5.4.0-29.33-lowlatency 5.4.30 Uname: Linux 5.4.0-29-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun May 10 18:57:48 2020 InstallationDate: Installed on 2020-04-22 (17 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200422) SourcePackage: mate-panel UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877875/+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 1877857] Re: Black cursor when moving on chromium window in xubuntu
related to bug 1838008 -- 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/1877857 Title: Black cursor when moving on chromium window in xubuntu Status in chromium-browser package in Ubuntu: New Bug description: As identified in the youtube video below, when the mouse cursor moves over the snapped chromium or vlc windows, it turns black. https://youtu.be/xYnzqtPiK7s?t=337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877857/+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 1685754]
This issue was fixed in systemd by https://github.com/systemd/systemd/pull/15318. Debian cherry-picked that change into 245.4-3, so Debian bullseye and buster-backports have the fix, as does Ubuntu 20.04 (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/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: Invalid Status in GNOME Terminal: Confirmed Status in Nautilus: Invalid Status in systemd: Unknown Status in dbus package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Bug description: In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+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 1685754] Re: 'systemd --user' unduly forces umask=0022
** Also affects: systemd via https://github.com/systemd/systemd/issues/6077 Importance: Unknown Status: Unknown -- 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/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: Invalid Status in GNOME Terminal: Confirmed Status in Nautilus: Invalid Status in systemd: Unknown Status in dbus package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Bug description: In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+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 1685754] Re: gnome-terminal unduly forces umask=0022
** Tags removed: focal ** Summary changed: - gnome-terminal unduly forces umask=0022 + 'systemd --user' unduly forces umask=0022 ** Changed in: gnome-terminal (Ubuntu) Status: Confirmed => Invalid ** Changed in: dbus (Ubuntu) Status: Confirmed => Invalid ** Changed in: gnome-session Status: New => Invalid ** Changed in: nautilus Status: Confirmed => Invalid -- 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/1685754 Title: 'systemd --user' unduly forces umask=0022 Status in gedit: Invalid Status in gnome-session: Invalid Status in GNOME Terminal: Confirmed Status in Nautilus: Invalid Status in dbus package in Ubuntu: Invalid Status in gnome-terminal package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Released Bug description: In order to set the default umask of my users to 027 or 007, I followed the instructions provided in 'man pam_umask' : In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or 'umask=007' (for myself). Then, MOST graphical applications systematically run with the correct umask. In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it systematically displays 0007. But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it systematically displays 0022. That is BAD, and is a security issue. Workaround : Inside the newly created '/etc/profile.d/umask.sh', and in each '~/.bashrc', add following content : UMASK="$(grep -o "^$USER:.*,umask=0[0-7]*" /etc/passwd)" if [ "$UMASK" ]; then umask "${UMASK#$USER:*,umask=}" fi In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask unchanged. Thank you in advance for a quick correction. ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: gnome-terminal 3.20.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8 Uname: Linux 4.10.0-19-generic x86_64 ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon Apr 24 08:36:58 2017 InstallationDate: Installed on 2017-03-28 (26 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321) SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gedit/+bug/1685754/+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 1877865] Re: Insufficient privilege to access help files
*** This bug is a duplicate of bug 1869561 *** https://bugs.launchpad.net/bugs/1869561 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1869561, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1869561 Libreoffice Help does not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1877865 Title: Insufficient privilege to access help files Status in libreoffice package in Ubuntu: New Bug description: Following an upgrade from 18.04 to 20.04 the libreoffice help files cannot be accessed due to insufficient user rights. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:04:08 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877865/+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 1877865] [NEW] Insufficient privilege to access help files
*** This bug is a duplicate of bug 1869561 *** https://bugs.launchpad.net/bugs/1869561 Public bug reported: Following an upgrade from 18.04 to 20.04 the libreoffice help files cannot be accessed due to insufficient user rights. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:04:08 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1877865 Title: Insufficient privilege to access help files Status in libreoffice package in Ubuntu: New Bug description: Following an upgrade from 18.04 to 20.04 the libreoffice help files cannot be accessed due to insufficient user rights. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:04:08 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1877865/+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 1876962] Re: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting c
Did you try to contact user support for this? That's clearly some kind of installation error, likely from some interrupted process. Try `sudo dpkg --configure -a` followed by `sudo apt -f install`, if that doesn't work then an `apt install --reinstall libxml2`. If you can't bring it to heel, please ask at user support for directions. ** Changed in: libxml2 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libxml2 in Ubuntu. https://bugs.launchpad.net/bugs/1876962 Title: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libxml2 package in Ubuntu: Incomplete Bug description: Fresh install of Ubuntu 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 Uname: Linux 4.15.0-99-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 AptOrdering: python3-distupgrade:amd64: Install python3-update-manager:amd64: Install update-manager-core:amd64: Install update-manager:amd64: Install NULL: ConfigurePending Architecture: amd64 Date: Tue May 5 17:56:48 2020 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2020-05-05 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Python3Details: /usr/bin/python3.6, Python 3.6.9, python3-minimal, 3.6.7-1~18.04 PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] failed with exit code 1:", unpackaged RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.1 SourcePackage: libxml2 Title: package libxml2:amd64 2.9.4+dfsg1-6.1ubuntu1.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxml2/+bug/1876962/+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 1877866] [NEW] While using nvidia driver the system loops back to login immediately after entering password. Graphical glitches exist in top half of screen. When changing to di
Public bug reported: Graphic adaptor: VGA compatible controller: NVIDIA Corporation GT218M [NVS 3100M] (rev a2) I was using the proprietary nvidia driver package at the time. Using the recovery console I removed the nvidia driver and switched to nouveau. Everything works OK now. I used the nvidia driver for several days on this fresh install with no problems. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal Linux 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Was using nVidia Driver: nVidia binary driver - version 340.108 from nVidia-340. Please feel free to contact me if additional information / logs are needed. I am located in Minnesota, US so please be mindful about what hours you choose to contact me during. jd.qz...@gmail.com Joseph Dighton / 1-763-250-8135 ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New -- 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/1877866 Title: While using nvidia driver the system loops back to login immediately after entering password. Graphical glitches exist in top half of screen. When changing to different tty the log in screen remains displayed, but I am able to login blind to the tty and enter commands. When entering command into the tty, the graphics glitches move around. Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Graphic adaptor: VGA compatible controller: NVIDIA Corporation GT218M [NVS 3100M] (rev a2) I was using the proprietary nvidia driver package at the time. Using the recovery console I removed the nvidia driver and switched to nouveau. Everything works OK now. I used the nvidia driver for several days on this fresh install with no problems. Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal Linux 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Was using nVidia Driver: nVidia binary driver - version 340.108 from nVidia-340. Please feel free to contact me if additional information / logs are needed. I am located in Minnesota, US so please be mindful about what hours you choose to contact me during. jd.qz...@gmail.com Joseph Dighton / 1-763-250-8135 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1877866/+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 1827498] Re: Geoclue 2 very high memory usage
I saw this issue using geoclue-2.0 2.5.3-1ubuntu1 on eoan. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue in Ubuntu. https://bugs.launchpad.net/bugs/1827498 Title: Geoclue 2 very high memory usage Status in geoclue package in Ubuntu: Confirmed Bug description: After geoclue 2 running at high CPU for some minutes I found CPU usage had dropped to zero but geoclue was still hogging a whopping 11GB of memory (the PC has 16GB). I stopped the geoclue service to recover the memory. Kubuntu 18.04 $ apt-cache policy geoclue-2.0 geoclue-2.0: Installed: 2.4.7-1ubuntu1 Candidate: 2.4.7-1ubuntu1 Version table: *** 2.4.7-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Happy to provide other info on request. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue/+bug/1827498/+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 256373] Re: rhythmbox tag editing issue (back button in file property menu becomes inactive)
Further to my comment #13 I can now confirm a slight variation of this bug with rhythmbox 3.4.2 in Ubuntu 18.04. When the song is moved to the end of the list, the forward button should be disabled but it isn't. It seems there are other minor issues in respect of the currently highlighted file once another file is moved after the renaming. ** Tags added: bionic ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/256373 Title: rhythmbox tag editing issue (back button in file property menu becomes inactive) Status in Rhythmbox: New Status in rhythmbox package in Ubuntu: Confirmed Bug description: Binary package hint: rhythmbox Hello all, A strange behaviour of rhythmbox (version 0.11.5, german translation) occured on my laptop: I select a few music files to edit their properties. Right-clicking on one file brings up a menu from which I select 'properties'. Using the 'back' and 'next' buttons I adjust artist, title, album etc. So far things are working fine. When I reach the end of the list of prior selected music files sometimes (rather seldom) the 'back' button turns to grey and becomes inactive. Strangely enough the 'next' button is still active even thought there is no next file in the selection. While the 'back'-button in the properties menu is 'out of order' I have the close that menu and manually choose another music file from the selection. This occures to be rather strange to me. There could be something going on with the GUI of the file property menu. If you need any further description or system output from my laptop please let me know. I am running Ubuntu 8.04 on an IBM T40 laptop. Kind regards, Tobias To manage notifications about this bug go to: https://bugs.launchpad.net/rhythmbox/+bug/256373/+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 1877857] Re: Black cursor when moving on chromium window in xubuntu
Related https://forum.snapcraft.io/t/very-ugly-cursor-for-spotify-and- kde-snaps/17118/2 -- 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/1877857 Title: Black cursor when moving on chromium window in xubuntu Status in chromium-browser package in Ubuntu: New Bug description: As identified in the youtube video below, when the mouse cursor moves over the snapped chromium or vlc windows, it turns black. https://youtu.be/xYnzqtPiK7s?t=337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877857/+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 1877434] Re: Slow Gnome 3.36 overall experience
As it appears the problem persisted. The problem was in the upower service and i managed to fix it by installing the file containing the missing libusbmuxd.so.4 file from http://archive.ubuntu.com/ubuntu/pool/main/libu/libusbmuxd/libusbmuxd4_1.0.10-2_amd64.deb Now everything works as it should -- 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/1877434 Title: Slow Gnome 3.36 overall experience Status in gnome-shell package in Ubuntu: Invalid Bug description: After upgrading from ubuntu 19.10 to 20.04 the boot time was very slow and the overall feel of the desktop wasn't as snappy as it was in previous releases. 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: Thu May 7 21:29:12 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-07 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1877434/+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 1877854] Re: Ubuntu 20.04. Appearance > Dock setting fails with 2 monitors. Shows on both.
*** This bug is a duplicate of bug 1866088 *** https://bugs.launchpad.net/bugs/1866088 Thanks for reporting. However, these problems have already been reported are and in the process of being fixed. I'm marking this as a duplicate of bug 1866088, a fix will be released shortly. Also, bug 1877108 will fix the remaining issue. ** This bug has been marked a duplicate of bug 1866088 Problems with the Dock setting of "Show on" in the Appearance tab -- 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/1877854 Title: Ubuntu 20.04. Appearance > Dock setting fails with 2 monitors. Shows on both. Status in gnome-control-center package in Ubuntu: New Bug description: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 Background -- I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. What I expect to happen --- I expect to have the dock on the monitor I choose. What really happens --- Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows always on both monitors no matter what setting I choose. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1877854/+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 1877857] [NEW] Black cursor when moving on chromium window in xubuntu
Public bug reported: As identified in the youtube video below, when the mouse cursor moves over the snapped chromium or vlc windows, it turns black. https://youtu.be/xYnzqtPiK7s?t=337 ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: 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/1877857 Title: Black cursor when moving on chromium window in xubuntu Status in chromium-browser package in Ubuntu: New Bug description: As identified in the youtube video below, when the mouse cursor moves over the snapped chromium or vlc windows, it turns black. https://youtu.be/xYnzqtPiK7s?t=337 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1877857/+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 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]
So, I've tried. Reinstalling did not help. Also, problem is even worse on kubuntu i've tried. There is no option "Analog Stereo Duplex (unplugged)(unavailable)" to choose and turn on sound. -- 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/1876046 Title: [XPS L501X, Realtek ALC665, Speaker, Internal] Status in pulseaudio package in Ubuntu: Incomplete Bug description: After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and "Build-in speaker" appears "unplugged/unavaiable". I can change it in volume control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and sound does play, but after each reboot computer changes to Digital Stereo IEC985 and do not play sound until changed again. I did reinstall of alsa and pulse according to some forums but this didn't work. Before upgrade everything always worked out of the box since 2009 on this computer. I know it's a little old but it works excellent! Please help. 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 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Apr 30 09:25:27 2020 InstallationDate: Installed on 2020-02-25 (64 days ago) InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kwiatek1472 F pulseaudio /dev/snd/controlC0: kwiatek1472 F pulseaudio /dev/snd/pcmC0D0c: kwiatek1472 F...m pulseaudio /dev/snd/pcmC0D0p: kwiatek1472 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago) dmi.bios.date: 07/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.vendor: Dell Inc. dmi.board.version: A08 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A08 dmi.modalias: dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08: dmi.product.name: XPS L501X dmi.product.version: A08 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+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 1877854] [NEW] Ubuntu 20.04. Appearance > Dock setting fails with 2 monitors. Shows on both.
Public bug reported: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 Background -- I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. What I expect to happen --- I expect to have the dock on the monitor I choose. What really happens --- Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows always on both monitors no matter what setting I choose. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: focal upgrade-software-version ** Tags added: gnome ** Description changed: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 - Background -- I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. What I expect to happen --- I expect to have the dock on the monitor I choose. What really happens --- Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows on both monitors no matter what setting I choose. ** Description changed: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 Background -- - - I upgraded from 18.04 to 20.04 after the official launch date. The dock - also didn't work properly on 18.04 with two monitors. You had to select - the wrong monitor to have the dock on the side you really wanted. + I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. What I expect to happen --- I expect to have the dock on the monitor I choose. What really happens --- Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows on both monitors no matter what setting I choose. ** Description changed: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 Background -- I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. - What I expect to happen --- I expect to have the dock on the monitor I choose. What really happens --- - - Now focusing on 20.04 which is my current version. When I first - installed it, the Dock was showing on one side but after changing the - initial setting just for the sake of testing, the dock shows on both - monitors no matter what setting I choose. + Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows on both monitors no matter what setting I choose. ** Tags added: foc upgrade-software-version ** Tags removed: foc gnome ** Tags added: focal ** Description changed: Environment --- Ubuntu 20.04 LTS package: gnome-shell-extension-ubuntu-dock/focal,focal,now 67ubuntu20.04.5 Number of monitors: 2 Background -- I upgraded from 18.04 to 20.04 after the official launch date. The dock also didn't work properly on 18.04 with two monitors. You had to select the wrong monitor to have the dock on the side you really wanted. What I expect to happen --- I expect to have the dock on the monitor I choose. - What really happens --- - Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the initial setting just for the sake of testing, the dock shows on both monitors no matter what setting I choose. + Now focusing on 20.04 which is my current version. When I first installed it, the Dock was showing on one side but after changing the
[Desktop-packages] [Bug 1877856] [NEW] Display garbled after resume from suspect
Public bug reported: I just upgraded 18.04 -> 20.04. Then after resuming from suspend on my laptop, the display is garbled blocks of random colors. It changes frequently to other random colors. Power cycling the laptop clears the issue, but only until it is suspended again. The VT3 console shows: nouveau :01:00.0: gr: PGRAPH_TLB flush idle timeout fail Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 10 05:53:41 2020 DistUpgraded: 2020-05-09 01:40:08,730 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell GT218M [NVS 3100M] [1028:040a] MachineType: Dell Inc. Latitude E6410 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-05-09 (1 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0K42JR dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Sat May 19 22:08:24 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877856 Title: Display garbled after resume from suspect Status in xorg package in Ubuntu: New Bug description: I just upgraded 18.04 -> 20.04. Then after resuming from suspend on my laptop, the display is garbled blocks of random colors. It changes frequently to other random colors. Power cycling the laptop clears the issue, but only until it is suspended again. The VT3 console shows: nouveau :01:00.0: gr: PGRAPH_TLB flush idle timeout fail Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 10 05:53:41 2020 DistUpgraded: 2020-05-09 01:40:08,730 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT218M [NVS 3100M] [10de:0a6c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Dell GT218M [NVS 3100M] [1028:040a] MachineType: Dell Inc. Latitude E6410 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro SourcePackage: xorg UpgradeStatus: Upgraded to focal on 2020-05-09 (1 days ago) dmi.bios.date: 12/05/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0K42JR dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA16:bd12/05/2013:svnDellInc.:pnLatitudeE6410:pvr0001:rvnDellInc.:rn0K42JR:rvrA03:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6410 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz:
[Desktop-packages] [Bug 1869522] Re: Simple Scan doesn't work
Retasking to the simple-scan package in Ubuntu. ** Package changed: gnome-software (Ubuntu) => simple-scan (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1869522 Title: Simple Scan doesn't work Status in simple-scan package in Ubuntu: Confirmed Bug description: The latest version of Simple Scan released for Ubuntu 18.04 LTS does not work. Version 3.28.0-0ubuntu1 is installed. When I click to launch it nothing happens. I initially reported the bug against Simple Scan, but they said it was a problem with the Ubuntu 18.04 LTS distribution. https://gitlab.gnome.org/GNOME/simple-scan/-/issues/159 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-software 3.28.1-0ubuntu4.18.04.14 ProcVersionSignature: Ubuntu 4.15.0-91.92-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 28 15:29:05 2020 ExecutablePath: /usr/bin/gnome-software InstallationDate: Installed on 2014-08-08 (2059 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.28.1-0ubuntu4.18.04.14 ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash PATH=(custom, no user) LANG=en_US.UTF-8 SourcePackage: gnome-software UpgradeStatus: Upgraded to bionic on 2020-01-05 (82 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1869522/+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 1874219] Re: PC suspends after 20 minutes at the login screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1874219 Title: PC suspends after 20 minutes at the login screen Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: Same as LP: #1759325 in Bionic, but this time affecting Focal. After some update in the last month, my desktop PC now suspends after 20 minutes at the login screen. I was able to override the setting for my user account by adjusting the power settings in gnome-control-center. I see no obvious way of overriding the default for the system. Asking on IRC, I was pointed at LP: #1868260, but got no response there. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1874219/+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 1877847] [NEW] causes freezeups with zsh related to .histfile.LOCK
Public bug reported: This problem only happens to me when I select the Ubuntu WM, not under Cinnamon. I see it in gnome-terminal. After I enter a command, like "ls" or "cd" into gnome-terminal and press Enter, the desktop icons blink out for a split-second, and while they do, the command does not finish. This makes it annoying for me to work in the command-line, since I'm used to most programs responding immediately. >From my experience, it looks like when a program is already running, like Vim, and I ask it to do a disk operation, this "blinking out" and "freezing" does not happen. I'm attaching a video of this happening. I've noticed this line in journalctl -b: Mai 10 13:24:55 agentydragon kernel: mce: CPU3: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU1: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU2: Package temperature/speed normal Mai 10 13:24:55 agentydragon kernel: mce: CPU0: Package temperature/speed normal Mai 10 13:24:56 agentydragon wpa_supplicant[1011]: wlp4s0: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-67 noise= txrate=13 Mai 10 13:25:07 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:10 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:12 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.1' (uid=1000 pid=3139 comm="/usr/libexec/tracker-miner-fs " label="> Mai 10 13:25:14 agentydragon systemd[3110]: Starting Tracker metadata database store and lookup manager... Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Successfully activated service 'org.freedesktop.Tracker1' Mai 10 13:25:14 agentydragon systemd[3110]: Started Tracker metadata database store and lookup manager. Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.1' (uid=1000 pid=3139 comm="/usr/libexec/tracker-mi> Mai 10 13:25:14 agentydragon systemd[3110]: Starting Tracker metadata extractor... Mai 10 13:25:14 agentydragon tracker-extract[49035]: Set scheduler policy to SCHED_IDLE Mai 10 13:25:14 agentydragon tracker-extract[49035]: Setting priority nice level to 19 Mai 10 13:25:14 agentydragon dbus-daemon[3143]: [session uid=1000 pid=3143] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Mai 10 13:25:14 agentydragon systemd[3110]: Started Tracker metadata extractor. Mai 10 13:25:15 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:18 agentydragon gnome-shell[5836]: JS ERROR: TypeError: fileItem is undefined _updateDesktopIfChanged@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:349:17 _monitorDesktopFolder/<@/usr/share/gnome-shell/extensions/desktop-icons@csoriano/desktopManager.js:311:94 Mai 10 13:25:18 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.viminfo.tmp«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:21 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:25 agentydragon systemd[3110]: tracker-extract.service: Succeeded. Mai 10 13:25:25 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:37 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der Informationen für Datei »/home/agentydragon/.histfile.LOCK«: Datei oder Verzeichnis nicht gefunden Mai 10 13:25:48 agentydragon tracker-store[49001]: OK Mai 10 13:25:48 agentydragon systemd[3110]: tracker-store.service: Succeeded. Mai 10 13:25:59 agentydragon gnome-shell[5836]: Error getting desktop unix mode: Gio.IOErrorEnum: Fehler beim Holen der
[Desktop-packages] [Bug 1868660] Re: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_sign
i got this error when hovering with the mouse over the system tray as described in the bug report however Iam using X11 and not wayland i have the following crash files: -rw-r- 1 root root 95M Mai 10 13:15 _usr_bin_gnome-shell.1000.crash -rw-r--r-- 1 root root0 Mai 10 13:15 _usr_bin_gnome-shell.1000.upload -rw--- 1 root root 37 Mai 10 13:15 _usr_bin_gnome-shell.1000.uploaded -rw-r- 1 root root 2,4M Mai 10 13:15 _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.crash -rw-r--r-- 1 root root0 Mai 10 13:15 _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.upload -rw--- 1 root root 37 Mai 10 13:15 _usr_lib_x86_64-linux-gnu_libexec_kdeconnectd.1000.uploaded -- 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/1868660 Title: gnome-shell crashed with SIGSEGV in st_theme_node_get_icon_style() from st_texture_cache_load_gicon() from st_icon_update() from _g_closure_invoke_va() from g_signal_emit_valist() Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.35.91-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/f48b96bcfbbd221faf772da51dae29be310cbd9c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1868660/+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 1877726] Re: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working
[NOTE: Apologies for the paste, but for some reason the answer got deleted from askubuntu (This post is hidden. It was deleted 12 hours ago by fossfreedom♦. ...so much for "freedom" ; ) If someone can tell me why, I would appreciate it. I gave the answer (Rodecaster appears not to be supported) and showed a lot of debugging effort leading to that conclusion.] I have the same issue... I tried many things, but could not get the Rodecaster working. I did learn quite a bit and got the Scarlett 2i2 working though. - lsusb Bus 001 Device 002: ID 19f7:0011 RODE Microphones RODECaster Pro - ls -al /dev/snd/by-id/ lrwxrwxrwx 1 root root 12 May 6 11:44 usb-RODE_Microphones_RODECaster_Pro_001A-01 -> ../controlC2 - cat /proc/asound/cards 2 [Pro]: USB-Audio - RODECaster Pro RODE Microphones RODECaster Pro at usb-:01:00.0-3, high speed - cat /proc/asound/modules 0 snd_usb_audio 1 snd_hda_intel - lsmod | grep snd_usb_audio looks OK - arecord --list-devices does not show it - aplay -L shows usbstream:CARD=GenericHD-Audio GenericUSB Stream Output and a lot of other (normal motherboard) devices but nothing with Rode and nothing else USB - aplay --device=usbstream ALSA lib pcm_usb_stream.c:486:(_snd_pcm_usb_stream_open) Invalid type for card aplay: main:828: audio open error: Invalid argument - cat /proc/asound/pcm does not show it - editing /etc/modprobe.d/alsa-base.conf to add these two lines at the end: options snd-usb-audio index=0 options snd-hda-intel index=1 ...but no change after a reboot. Idea from https://unix.stackexchange.com/questions/220224/alsa-not-detecting-my-soundcard - editing /etc/modprobe.d/alsa-base.conf to add options snd slots=snd-usb-audio,snd-hda-intel did not change anything either - blacklisting snd_hda_intel in /etc/modprobe.d/blacklist-sound.conf by adding blacklist snd_hda_intel to that file (create it if necessary) and rebooting disabled it, but did not help with the USB sound for the Rodecaster - pulseaudio -k && sudo alsa force-reload after the changes (instead of a reboot) doesn't change anything either. Note: pulseaudio restarts itself and does not need to be manually restarted (Is there another way to restart the sound system if pulseaudio/ALSA don't work?) The Answer (as it appears to me at least): - The Rodecaster is recognized as a USB device, but somehow not recognized by Alsa - I grabbed a Scarlett 2i2 gen3 (https://wiki.linuxaudio.org/wiki/hardware_support) - edited /etc/modprobe.d/alsa-base.conf to comment out #options snd-usb-audio index=-2 to allow snd-usb-audio to be the first device - edited /etc/modprobe.d/alsa-base.conf to add options snd slots=snd-usb-audio,snd-hda-intel at the end to have the USB audio before the HDA Intel - pulseaudio -k && sudo alsa force-reload to reload the alsa config Then the Scarlett showed up. Leaving the HDA Intel first did not let the Scarlett show up. Helpful info: - https://www.alsa-project.org/main/index.php/Help_To_Debug ...the alsa-info.sh looks like a fairly complete alsa debugging info summary generator - https://wiki.ubuntu.com/DebuggingSoundProblems - bug filed: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877726 -- 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/1877726 Title: [HDA-Intel - HD-Audio Generic, playback] USB sound with Rodecaster Pro not working Status in alsa-driver package in Ubuntu: New Bug description: Please see https://askubuntu.com/questions/1229085/ubuntu-with-rodecaster-pro-usb-soundcard/1236257#1236257 for most background. tl;dr: - The Rodecaster Pro is a USB audio standard compliant device - lsusb sees it, but alsa cannot use it - trying the exact same setup with a Scarlett 2i2 USB device works (with some caveats, see the mentioned post) Somehow the Rodecaster is ignored by Alsa. I am more than happy to help debug. Alsa info is at http://alsa-project.org/db/?f=94fd609fa23912ab0a39b67676a026fd163f3f3b and also attached. nils@blackbox:~/tmp/soundtest$ aplay -l List of PLAYBACK Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: Generic_1 [HD-Audio Generic], device 1: ALC887-VD Digital [ALC887-VD Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: USB [Scarlett 2i2 USB], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 nils@blackbox:~/tmp/soundtest$ arecord --list-devices List of CAPTURE Hardware Devices card 0: Generic_1 [HD-Audio Generic], device 0: ALC887-VD Analog [ALC887-VD Analog] Subdevices: 1/1
[Desktop-packages] [Bug 1877841] Re: with the dark theme, the active line is highlighted and I cannot see the text I am typing.
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1857191, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1857191 Dark themes don't work well with highlighted current line in gedit -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/1877841 Title: with the dark theme, the active line is highlighted and I cannot see the text I am typing. Status in gedit package in Ubuntu: New Bug description: 1) Release: 20.04 2) Version: 3.36.1-1 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. 4) What happened: Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 17:35:24 2020 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2020-05-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_PH:en LANG=en_PH.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1877841/+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 1877841] [NEW] with the dark theme, the active line is highlighted and I cannot see the text I am typing.
*** This bug is a duplicate of bug 1857191 *** https://bugs.launchpad.net/bugs/1857191 Public bug reported: 1) Release: 20.04 2) Version: 3.36.1-1 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. 4) What happened: Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 17:35:24 2020 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2020-05-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=en_PH:en LANG=en_PH.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gedit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-05-10 17-54-58.png" https://bugs.launchpad.net/bugs/1877841/+attachment/5369386/+files/Screenshot%20from%202020-05-10%2017-54-58.png ** Description changed: 1) Release: 20.04 2) Version: 3.36.1-1 - 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. - 40 Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. + 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. + 4) Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gedit 3.36.1-1 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 17:35:24 2020 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2020-05-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=en_PH:en - LANG=en_PH.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=en_PH:en + LANG=en_PH.UTF-8 SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) ** Description changed: 1) Release: 20.04 2) Version: 3.36.1-1 3) Expected: I have the Dark theme on. On opening Gedit, the active line is all white. When I typed, I expected to see letters. - 4) Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. + 4) What happened: Nothing appeared. I thought it had locked up. I tapped on the Enter key and it went to the next line, revealing the text I had typed on the previously active line. So, it seems like with Dark theme on the text is white and same as the highlight. When I switched back to Standard theme, no problems. The text was black, the blank space is white and the highlight is slightly off-white (beige maybe, not good with the naming of colors). It's perfectly legible. ProblemType: Bug
[Desktop-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rtkit (Ubuntu Focal) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in linux package in Ubuntu: Confirmed Status in rtkit package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in rtkit source package in Focal: Confirmed Bug description: SRU Justification Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the lowlatency kernel since we expected most RT users to use that kernel. However we are getting RT regressions with the generic kernel. Digging deeper into this option, it seems to be pretty specialized and to require quite a bit of workload-specific configuration/tuning to be useful, so it doesn't really seem to make sense for a general-purpose kernel. Fix: Turn this option back off. Test Case: See comment #4. Regression Potential: This was turned on to support some docker functionality, so this functionality will no longer be available. We've had this option off for all releases prior to focal, so this seems acceptable. --- These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+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 1877542] Re: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver
** Summary changed: - Ubuntu 18.04 No sound ALC3253 alsa-driver + Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver -- 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/1877542 Title: Ubuntu 18.04.4 Inspiron 5379 No sound ALC3253 alsa-driver Status in alsa-driver package in Ubuntu: New Bug description: Hello, After last general update sound stops working on all interfaces. speakers, headphones nor HDMI provide any sound output even bluetooth headphones can't be connected. It seems that interface is connected to HDMI aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC3253 Analog [ALC3253 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 10: HDMI 4 [HDMI 4] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1877542/+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 1877717] Re: Sound stop working after wakeup
root@svmk-laptop:/var/log# grep pulseaudio syslog May 10 16:08:31 svmk-laptop pulseaudio[87919]: Error opening PCM device front:0: Нет такого файла или каталога ** Attachment added: "Output of command `pacmd list`" https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877717/+attachment/5369385/+files/pacmd_list.out.txt -- 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/1877717 Title: Sound stop working after wakeup Status in pulseaudio package in Ubuntu: New Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 I don't know how to reproduce this bug. Sometimes after notebook wakup sound stop working. pulseaudio -k fixes this problem. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1925 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 9 15:43:32 2020 InstallationDate: Installed on 2018-04-03 (766 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=ru_RU.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: Upgraded to focal on 2020-04-24 (14 days ago) dmi.bios.date: 06/29/2017 dmi.bios.vendor: Insyde dmi.bios.version: F.21 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83C9 dmi.board.vendor: HP dmi.board.version: 32.59 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.21:bd06/29/2017:svnHP:pnHPEnvy:pvrType1ProductConfigId:rvnHP:rn83C9:rvr32.59:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV NOTEBOOK dmi.product.name: HP Envy dmi.product.sku: 2PQ29EA#ACB dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1877717/+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 1175882]
No lockup here, 32GB RAM. KDE Plasma. Arch Linux 64-bit Version: 7.0.0.0.alpha1+ Build ID: c73418d8d1258ea0a8c77c07672fd182e2b28b26 CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 9 May 2020 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1175882 Title: Hangs while modifying document (after completion of paste from Wep Page with Multiple Images) Status in LibreOffice: New Status in libreoffice package in Ubuntu: Triaged Bug description: Follow these steps to bring LibreOffice writer to a crawl: 1) Allow this page to fully load in firefox (in a new tab): http://www.amorosity.com/SlingBlade/ 2) Click on the page and hit ctrl-a, then ctrl-c (coping the entire page's contents into memory). 3) Open LibreOffice writer, and paste your clipboard into it. I don't mind waiting for all the images to get loaded. The main point here, is that performance is not only slow during the initial paste. After the images get fully loaded into the word processing document, interacting with the document becomes impractical. Everything you try to do makes the application hang for several seconds. I have 4 gigabytes of RAM available for LibreOffice writer to use as it wishes, but it must be using some type of swap file (instead) while I'm modifying this large document. However, I have a really fast solid-state hard drive, so you'd think that even that would be fast on my machine. My machine should have the specs to enable me the ability to handle converting this large web page into a word processing document. Yes there are other ways to achieve what I'm trying to do, but this bug is about how LibreOffice can't handle the job. If it was programmed just right, it would make use of the resources my computer would gladly provide it, and scale up to this rather intensive task. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libreoffice-writer 1:4.0.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8 Uname: Linux 3.8.0-19-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu8 Architecture: amd64 Date: Thu May 2 23:09:24 2013 InstallationDate: Installed on 2013-04-02 (31 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130401) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1175882/+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 1777285]
(In reply to Richard Elkins from comment #0) > Steps to Reproduce: > Linux batch script, starting with an existing text file called "myfile.txt": > > libreoffice --headless --convert-to odt:writer8 myfile.txt > RC=$? > if [ $RC -ne 0 ]; then > echo '*** libreoffice conversion failed for myfile.txt' > exit 86 > fi > cp myfile.odt somewhere-else.odt > > Actual Results: > cp: cannot stat 'myfile.odt': No such file or directory > > Expected Results: > Copy completes as normal because myfile.odt is available. I get the expected result. I guess you should bite the bullet, clone the source and try modifying it. https://wiki.documentfoundation.org/Development/BuildingOnLinux https://wiki.documentfoundation.org/Development/Linux_Build_Dependencies Arch Linux 64-bit Version: 7.0.0.0.alpha1+ Build ID: c73418d8d1258ea0a8c77c07672fd182e2b28b26 CPU threads: 8; OS: Linux 5.6; UI render: default; VCL: kf5; Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 9 May 2020 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1777285 Title: [upstream] Batch libreoffice --convert-to offers no way to wait for document completion Status in LibreOffice: New Status in libreoffice package in Ubuntu: Confirmed Bug description: Command-line: libreoffice --convert-to odt:writer8 myfile.txt The returned status code ($?) is zero. So far, so good. But, when I try to access the ODT file (E.g. copy it), it doesn't yet exist. Adding `sync; sync; sync` right after the libreoffice batch execution did not help. Adding --headless as an option did not help. If I sleep for a few seconds immediately after the libreoffice batch execution, then the file finally gets completed before a subsequent command references the ODT file. Sample script: ### Create somehow a file called myfile.txt rm myfile.odt somewhere-else.odt libreoffice --headless --convert-to odt:writer8 myfile.txt RC=$? if [ $RC -ne 0 ]; then echo '*** libreoffice conversion failed for myfile.txt' exit 86 fi #sleep 3 ls *.odt Result: ls: cannot access '*.odt': No such file or directory If one changes the above script so that the sleep is executed, then the ODT file is available. Observation: It appears that executing libreoffice in batch mode is somehow kicking off a separate process to finish the ODT file. The exit to the shell and the availability of the ODT file should be synchronized. Before 18.04, I never saw this behavior. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Jun 16 17:07:02 2018 InstallationDate: Installed on 2017-10-13 (246 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-05-18 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1777285/+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 1877830] Re: package flashplugin-installer 32.0.0.363ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1877830 Title: package flashplugin-installer 32.0.0.363ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in flashplugin-nonfree package in Ubuntu: New Bug description: my update suddenly got stopped and showing error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: flashplugin-installer 32.0.0.363ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Sun May 10 12:24:13 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2020-03-12 (58 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 32.0.0.363ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2020-05-01 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1877830/+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 1877830] [NEW] package flashplugin-installer 32.0.0.363ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
Public bug reported: my update suddenly got stopped and showing error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: flashplugin-installer 32.0.0.363ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Sun May 10 12:24:13 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2020-03-12 (58 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 32.0.0.363ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2020-05-01 (8 days ago) ** Affects: flashplugin-nonfree (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to flashplugin-nonfree in Ubuntu. https://bugs.launchpad.net/bugs/1877830 Title: package flashplugin-installer 32.0.0.363ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 Status in flashplugin-nonfree package in Ubuntu: New Bug description: my update suddenly got stopped and showing error ProblemType: Package DistroRelease: Ubuntu 16.04 Package: flashplugin-installer 32.0.0.363ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.15.0-91.92~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-91-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 Date: Sun May 10 12:24:13 2020 ErrorMessage: subprocess installed post-installation script returned error exit status 2 InstallationDate: Installed on 2020-03-12 (58 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) RelatedPackageVersions: dpkg 1.18.4ubuntu1.6 apt 1.2.32 SourcePackage: flashplugin-nonfree Title: package flashplugin-installer 32.0.0.363ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 UpgradeStatus: Upgraded to xenial on 2020-05-01 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/1877830/+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 1877829] [NEW] Won't reconnect to shared headphones
Public bug reported: In Ubuntu 19.04, I could use my Sony WH-1000XM3 headphones with both my laptop running Ubuntu, and my Android smartphone. The headphones would pair with both, and I could simply re-enable the connection in Ubuntu or Android to connect to the headphones if the other device had been using the headphones last. In Ubuntu 20.04, Ubuntu now refuses to reconnect to the headphones if my Android phone was using the headphones last. I have to manually unpair the headphones and re-pair them again. This is very inconvenient. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 10 15:44:22 2020 InstallationDate: Installed on 2017-08-16 (997 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-04-12 (27 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET57W (1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20HFCTO1WW dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1WET57W(1.36):bd11/29/2019:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T470s dmi.product.name: 20HFCTO1WW dmi.product.sku: LENOVO_MT_20HF_BU_Think_FM_ThinkPad T470s dmi.product.version: ThinkPad T470s dmi.sys.vendor: LENOVO hciconfig: hci0: Type: Primary Bus: USB BD Address: F8:59:71:8D:1A:16 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:20456 acl:96 sco:0 events:2692 errors:0 TX bytes:604938 acl:84 sco:0 commands:2573 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2019-10-27T23:41:27.085337 ** Affects: bluez (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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1877829 Title: Won't reconnect to shared headphones Status in bluez package in Ubuntu: New Bug description: In Ubuntu 19.04, I could use my Sony WH-1000XM3 headphones with both my laptop running Ubuntu, and my Android smartphone. The headphones would pair with both, and I could simply re-enable the connection in Ubuntu or Android to connect to the headphones if the other device had been using the headphones last. In Ubuntu 20.04, Ubuntu now refuses to reconnect to the headphones if my Android phone was using the headphones last. I have to manually unpair the headphones and re-pair them again. This is very inconvenient. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 10 15:44:22 2020 InstallationDate: Installed on 2017-08-16 (997 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 002: ID 0bda:0316 Realtek Semiconductor Corp. USB3.0-CRW Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 5986:111c Acer, Inc Integrated Camera Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20HFCTO1WW ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=c023de63-612b-4367-874e-b3c987874f56 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to focal on 2020-04-12 (27 days ago) dmi.bios.date: 11/29/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1WET57W (1.36
[Desktop-packages] [Bug 1854676] Re: [snap] Web Midi API doesn't work
Olivier, it's not the webaudio that does not work. It's the webmidi. As in the 2 last examples on the demo list: https://ryoyakawai.github.io/smfplayer/ http://webaudiodemos.appspot.com/MIDIDrums/index.html In my testing the drum machine doesn't ask for permission to use midi. So that might be a bug on the websites part. But when smfplayer loads, this comes up in the teminal: ALSA lib conf.c:3916:(snd_config_update_r) Cannot access file /usr/share/alsa/alsa.conf ALSA lib seq.c:935:(snd_seq_open_noupdate) Unknown SEQ hw Might be usefull :) -- 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/1854676 Title: [snap] Web Midi API doesn't work Status in chromium-browser package in Ubuntu: Confirmed Bug description: With aspirations of creating a web based Midi tool, using Ubuntu 19.10, I'm trying to test out the Web Midi API: https://www.w3.org/TR/webmidi/ Although it is supposed to be supported in Chromium, none of these samples work in Ubuntu 19.10's snap-package installation of Chromium: https://webaudio.github.io/demo-list/ In the meantime, please recommend a work-around of how I can work with the Web Midi API while using Ubuntu Linux as my operating system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1854676/+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