[Desktop-packages] [Bug 1869304] [NEW] Video Card Intel Not being used
Public bug reported: Laptop was draining battery too fast, checked for Video Card Updates, Intel is not being used. Tried Xorg, it says fault packages are being held. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 11:07:15 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1028:078b] InstallationDate: Installed on 2020-03-23 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a05 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15-3567 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=7a4ba4e2-af26-42b5-b4bf-852d8f4e530b ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 0765NJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.10.0:bd05/10/2019:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0765NJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.product.sku: 078B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A 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 N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1869304 Title: Video Card Intel Not being used Status in xorg package in Ubuntu: New Bug description: Laptop was draining battery too fast, checked for Video Card Updates, Intel is not being used. Tried Xorg, it says fault packages are being held. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.3.0-42.34~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.12 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Mar 27 11:07:15 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:078b] Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 M520] [1028:078b] InstallationDate: Installed on 2020-03-23 (3 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 002: ID 0c45:6a05 Microdia Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 15-3567 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-42-generic root=UUID=7a4ba4e2-af26-42b5-b4bf-852d8f4e530b ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.10.0 dmi.board.name: 0765NJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Desktop-packages] [Bug 1867908] Re: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length
** Changed in: wpa (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1867908 Title: Fix RTM NEW/DELLINK IFLA_IFNAME copy for maximum ifname length Status in wpa package in Ubuntu: Triaged Bug description: Some wifi adapters kept asking for a password when MAC address randomization was enabled. I reported this to Realtek, and they gave me a patch for wpa_supplicant, which fixes the issue. I asked Realtek to report this upstream to wpasupplicant, and they did, the commit is: http://w1.fi/cgit/hostap/commit/?id=7546c489a95a033c78331915fcdfa0e6fd74d563 It would be very nice to cherrypick that for Focal. I uploaded it as a merge request below, and I tested that it fixes the issue with adapters based on the following chipsets: ath9k, rtl8812au, rtl88x2bu and rtl8821cu To reproduce this: Ubuntu's network-manager defaults to "MAC randomization disabled", I think as a workaround to this specific issue. This is defined in two places: - wifi.scan-rand-mac-address=no in /etc/NetworkManager/NetworkManager.conf - Some specific drivers in /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. With these, the problem happens in around 10% of the cases. To be able to reproduce it in 100% of the cases, it's best to remove these Ubuntu workarounds. So: - Set "wifi.scan-rand-mac-address=yes" in /etc/NetworkManager/NetworkManager.conf - Remove /usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf. - systemctl stop network-manager - killall wpa_supplicant - systemctl start network-manager Then insert a USB wifi adapter that results in a big name with 15 characters like wlx74ee2ae2436a and try to connect to a wifi network. It will keep asking for a password. Then apply the patch, run the 3 commands above to restart network- manager, and verify that it can now connect properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1867908/+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 1868420] Re: File Operation Progress Display Pauses If Files Is Closed During An Active File Operation
Reported upstream, here's the bug link. Thanks! https://github.com/micheleg/dash-to-dock/issues/1144 ** Bug watch added: github.com/micheleg/dash-to-dock/issues #1144 https://github.com/micheleg/dash-to-dock/issues/1144 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1868420 Title: File Operation Progress Display Pauses If Files Is Closed During An Active File Operation Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: Files (Nautilus) displays progress for things like file transfers/deletions/etc as a small progress bar as part of its icon in the Ubuntu Dock. However, if Files is closed, the progress bar freezes in place rather than tracking the actual file operation, which continues in the background as signaled by GNOME's notification. If you re-open Files during this time, the progress bar will update to the proper position and keep tracking, but stop once the window is closed again. Ubuntu 20.04 (development branch) running GNOME 3.36. An `inxi -Fxzc0` System:Kernel: 5.4.0-18-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.35.91 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x serial: UEFI: American Megatrends v: 5407 date: 12/31/2019 CPU: Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ rev: 2 L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 108792 Speed: 1377 MHz min/max: 1550/3400 MHz Core speeds (MHz): 1: 1374 2: 1378 3: 1372 4: 1378 5: 1360 6: 1360 7: 3365 8: 1359 9: 1375 10: 1375 11: 1360 12: 1360 13: 3398 14: 1360 15: 1377 16: 1378 Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: XFX Pine driver: amdgpu v: kernel bus ID: 0c:00.0 Display: x11 server: X.Org 1.20.7 driver: amdgpu resolution: 3840x1080~144Hz OpenGL: renderer: AMD NAVI10 (DRM 3.35.0 5.4.0-18-generic LLVM 9.0.1) v: 4.6 Mesa 20.0.0 direct render: Yes Audio: Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] driver: snd_hda_intel v: kernel bus ID: 09:00.0 Device-2: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 0c:00.1 Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 0e:00.3 Device-4: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo bus ID: 3-1.3:3 Device-5: C-Media Blue Snowball type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-2:2 Device-6: Kingston HyperX Virtual Surround Sound type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-9:5 Sound Server: ALSA v: k5.4.0-18-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0 IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 6.82 TiB used: 483.31 GiB (6.9%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB size: 232.89 GiB ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB ID-5: /dev/sdd type: USB vendor: Western Digital model: WD easystore 2624 size: 4.55 TiB ID-6: /dev/sde vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB ID-7: /dev/sdf type: USB vendor: SanDisk model: Cruzer Glide 3.0 size: 232.50 GiB Partition: ID-1: / size: 223.52 GiB used: 50.52 GiB (22.6%) fs: btrfs dev: /dev/nvme0n1p3 ID-2: /boot size: 945.6 MiB used: 143.0 MiB (15.1%) fs: ext4 dev: /dev/nvme0n1p2 ID-3: /home size: 223.52 GiB used: 50.52 GiB (22.6%) fs: btrfs dev: /dev/nvme0n1p3 ID-4: swap-1 size: 7.46 GiB used: 4.2 MiB (0.1%) fs: swap dev: /dev/nvme0n1p4 Sensors: System Temperatures: cpu: 30.1 C mobo: N/A gpu: amdgpu temp: 48 C Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 Info: Processes: 511 Uptime: 21h 39m Memory: 31.36 GiB used: 4.79 GiB (15.3%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.16 inxi: 3.0.38 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic
[Desktop-packages] [Bug 1868911] Re: Exiting overview causes windows from other workspaces to be visible
** Summary changed: - Exiting overview on empty workspace causes windows from other workspaces to be visible + Exiting overview causes windows from other workspaces to be visible -- 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/1868911 Title: Exiting overview causes windows from other workspaces to be visible Status in gnome-shell package in Ubuntu: Fix Committed Bug description: $ dpkg-query -W gnome-shell gnome-shell 3.36.0-2ubuntu1 $ lsb_release -rc Release:20.04 Codename: focal $ _ When I toggle in and out of the overview on an empty workspace, windows from other workspaces appear. They are not interactable, so this seems more like a rendering bug than the windows really being teleported to another workspace. Switching back to another workspace that has windows causes the ghost windows to disappear. Opening a window in the empty workspace makes it appear on top of the ghost windows, and I have to switch to another workspace and back again to make only the new window be visible. I am using the vanilla "GNOME" session type. I did not observe this behaviour with gnome-shell 3.35.91-1ubuntu2. As well as the annoyance factor, of course there's a privacy angle to showing random windows at surprising times. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2011-11-06 (3062 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: wayland-session focal third-party-packages Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-25 (29 days ago) UserGroups: adm admin cdrom dialout docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868911/+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 1869296] Re: Windows From Other Workspaces Shown After Triggering Activities Overview
*** This bug is a duplicate of bug 1868911 *** https://bugs.launchpad.net/bugs/1868911 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 1868911, 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 1868911 Exiting overview on empty workspace causes windows from other workspaces to be visible -- 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/1869296 Title: Windows From Other Workspaces Shown After Triggering Activities Overview Status in gnome-shell package in Ubuntu: New Bug description: When Activities Overview is triggered, windows from all workspaces are shown in the current. They cannot be interacted with, but appear under the current window. GNOME 3.36.0 under X and Wayland on Ubuntu 20.04 (development branch) system info: System:Kernel: 5.4.0-18-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.36.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x serial: UEFI: American Megatrends v: 5407 date: 12/31/2019 CPU: Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ rev: 2 L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 108792 Speed: 1375 MHz min/max: 1550/3400 MHz Core speeds (MHz): 1: 1377 2: 1375 3: 1374 4: 1373 5: 1373 6: 1372 7: 1377 8: 1373 9: 1377 10: 1376 11: 1380 12: 1375 13: 1377 14: 1378 15: 1372 16: 1377 Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: XFX Pine driver: amdgpu v: kernel bus ID: 0c:00.0 Display: wayland server: X.Org 1.20.7 driver: amdgpu resolution: 3840x1080~144Hz OpenGL: renderer: AMD NAVI10 (DRM 3.35.0 5.4.0-18-generic LLVM 9.0.1) v: 4.6 Mesa 20.0.2 direct render: Yes Audio: Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] driver: snd_hda_intel v: kernel bus ID: 09:00.0 Device-2: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 0c:00.1 Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 0e:00.3 Device-4: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo bus ID: 3-1.3:3 Device-5: C-Media Blue Snowball type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-2:2 Device-6: Kingston HyperX Virtual Surround Sound type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-9:5 Sound Server: ALSA v: k5.4.0-18-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0 IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 6.60 TiB used: 414.06 GiB (6.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB size: 232.89 GiB ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB ID-5: /dev/sdd type: USB vendor: Western Digital model: WD easystore 2624 size: 4.55 TiB ID-6: /dev/sde vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB Partition: ID-1: / size: 223.52 GiB used: 51.23 GiB (22.9%) fs: btrfs dev: /dev/nvme0n1p3 ID-2: /boot size: 945.6 MiB used: 143.0 MiB (15.1%) fs: ext4 dev: /dev/nvme0n1p2 ID-3: /home size: 223.52 GiB used: 51.23 GiB (22.9%) fs: btrfs dev: /dev/nvme0n1p3 ID-4: swap-1 size: 7.46 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p4 Sensors: System Temperatures: cpu: 27.6 C mobo: N/A gpu: amdgpu temp: 42 C Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 Info: Processes: 471 Uptime: 1h 44m Memory: 31.36 GiB used: 2.38 GiB (7.6%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.16 inxi: 3.0.38 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1869296] [NEW] Windows From Other Workspaces Shown After Triggering Activities Overview
Public bug reported: When Activities Overview is triggered, windows from all workspaces are shown in the current. They cannot be interacted with, but appear under the current window. GNOME 3.36.0 under X and Wayland on Ubuntu 20.04 (development branch) system info: System:Kernel: 5.4.0-18-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.36.0 Distro: Ubuntu 20.04 LTS (Focal Fossa) Machine: Type: Desktop Mobo: ASUSTeK model: PRIME B350-PLUS v: Rev X.0x serial: UEFI: American Megatrends v: 5407 date: 12/31/2019 CPU: Topology: 8-Core model: AMD Ryzen 7 2700 bits: 64 type: MT MCP arch: Zen+ rev: 2 L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 108792 Speed: 1375 MHz min/max: 1550/3400 MHz Core speeds (MHz): 1: 1377 2: 1375 3: 1374 4: 1373 5: 1373 6: 1372 7: 1377 8: 1373 9: 1377 10: 1376 11: 1380 12: 1375 13: 1377 14: 1378 15: 1372 16: 1377 Graphics: Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] vendor: XFX Pine driver: amdgpu v: kernel bus ID: 0c:00.0 Display: wayland server: X.Org 1.20.7 driver: amdgpu resolution: 3840x1080~144Hz OpenGL: renderer: AMD NAVI10 (DRM 3.35.0 5.4.0-18-generic LLVM 9.0.1) v: 4.6 Mesa 20.0.2 direct render: Yes Audio: Device-1: Creative Labs Sound Core3D [Sound Blaster Recon3D / Z-Series] driver: snd_hda_intel v: kernel bus ID: 09:00.0 Device-2: AMD Navi 10 HDMI Audio driver: snd_hda_intel v: kernel bus ID: 0c:00.1 Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel bus ID: 0e:00.3 Device-4: Logitech HD Pro Webcam C920 type: USB driver: snd-usb-audio,uvcvideo bus ID: 3-1.3:3 Device-5: C-Media Blue Snowball type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-2:2 Device-6: Kingston HyperX Virtual Surround Sound type: USB driver: hid-generic,snd-usb-audio,usbhid bus ID: 1-9:5 Sound Server: ALSA v: k5.4.0-18-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASUSTeK driver: r8169 v: kernel port: f000 bus ID: 04:00.0 IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: Drives:Local Storage: total: 6.60 TiB used: 414.06 GiB (6.1%) ID-1: /dev/nvme0n1 vendor: Samsung model: SSD 960 EVO 250GB size: 232.89 GiB ID-2: /dev/sda vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB ID-3: /dev/sdb vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB ID-4: /dev/sdc vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB ID-5: /dev/sdd type: USB vendor: Western Digital model: WD easystore 2624 size: 4.55 TiB ID-6: /dev/sde vendor: Western Digital model: WDS500G2B0A-00SM50 size: 465.76 GiB Partition: ID-1: / size: 223.52 GiB used: 51.23 GiB (22.9%) fs: btrfs dev: /dev/nvme0n1p3 ID-2: /boot size: 945.6 MiB used: 143.0 MiB (15.1%) fs: ext4 dev: /dev/nvme0n1p2 ID-3: /home size: 223.52 GiB used: 51.23 GiB (22.9%) fs: btrfs dev: /dev/nvme0n1p3 ID-4: swap-1 size: 7.46 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/nvme0n1p4 Sensors: System Temperatures: cpu: 27.6 C mobo: N/A gpu: amdgpu temp: 42 C Fan Speeds (RPM): N/A gpu: amdgpu fan: 0 Info: Processes: 471 Uptime: 1h 44m Memory: 31.36 GiB used: 2.38 GiB (7.6%) Init: systemd runlevel: 5 Compilers: gcc: N/A Shell: bash v: 5.0.16 inxi: 3.0.38 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 21:24:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-12 (14 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200309) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Attachment added: "Screen recording of the issue." https://bugs.launchpad.net/bugs/1869296/+attachment/5341984/+files/Screencast%20from%2003-26-2020%2009%3A26%3A59%20PM.webm -- 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/1869296 Title: Windows From Other Workspaces Shown After Triggering Activities
[Desktop-packages] [Bug 1307793] Re: 14.04 rhythmbox freezes when going backwards a song (.m4a).
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1307793 Title: 14.04 rhythmbox freezes when going backwards a song (.m4a). Status in rhythmbox package in Ubuntu: Expired Bug description: I have not been able to replicate this bug on MP3 files, only on m4a audio files I have taken from youtube. a: open Rhythmbox b: play /m4a songs c: press back either by keyboard shortcut, the control under the sound control, or the dialogue on the dash icon. d: Program freezes ~~Also may have caused my dash search to stop working.~~ Edit: I retested; My unity search was not affected when I retested. 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu akiva@Akiva-ThinkPad:~$ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center akiva@Akiva-ThinkPad:~$ apt-cache policy rhythmbox rhythmbox: Installed: 3.0.2-0ubuntu1 Candidate: 3.0.2-0ubuntu1 Version table: *** 3.0.2-0ubuntu1 0 500 http://ca.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen Press backwards to play the previous song 4) What happened instead When backwards was pressed, the program hung, and had to be killed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1307793/+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 1323276] Re: Rhythmbox UI lagging in actually_add_monitor
[Expired for rhythmbox (Ubuntu) because there has been no activity for 60 days.] ** Changed in: rhythmbox (Ubuntu) Status: Incomplete => Expired -- 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/1323276 Title: Rhythmbox UI lagging in actually_add_monitor Status in rhythmbox package in Ubuntu: Expired Bug description: 1. Launch rhythmbox, it works nicely for 15-30 mins 2. At some point RB's UI becomes very sluggish. For example changing song may take 15-30 seconds. This happens every time i run RB so it's easily reproducable. I investigated it a bit, and seems that the UI thread is blocked in actually_add_monitor. Full backtrace follows: (gdb) bt #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:135 #1 0x7fba3586d68d in _L_lock_1082 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x7fba3586d607 in __GI___pthread_mutex_lock (mutex=0x2413480) at ../nptl/pthread_mutex_lock.c:134 #3 0x7fba35b0b991 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fba30a848b0 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #5 0x7fba30a84d47 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7fba30a771b2 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #7 0x7fba36ad36f3 in actually_add_monitor (db=0x1ba2230, directory=0x7fb9a8006b80, error=0x0) at rhythmdb-monitor.c:133 #8 0x7fba36ad37ad in monitor_subdirectory (file=0x7fb9a8006b80, dir=1, db=0x1ba2230) at rhythmdb-monitor.c:154 #9 0x7fba36af4831 in _uri_handle_file (dir=0x7fb9e79b73a0, fileinfo=, handled=0x2a668c0, func=0x7fba36ad3750 , user_data=0x1ba2230, descend=0x7fffae8da6e0) at rb-file-helpers.c:751 #10 0x7fba36af4b44 in _uri_handle_recursively_process_files (src=, result=, ptr=0x24ecec0) at rb-file-helpers.c:897 #11 0x7fba309dd6a7 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #12 0x7fba30a1041b in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #13 0x7fba30a10439 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #14 0x7fba35ac9ce5 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #15 0x7fba35aca048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7fba35aca0ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7fba30a3267c in g_application_run () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #18 0x7fba36a5a812 in rb_application_run (app=0x181e140, argc=argc@entry=1, argv=argv@entry=0x7fffae8daba8) at rb-application.c:659 #19 0x00400d3a in main (argc=1, argv=0x7fffae8daba8) at main.c:89 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: rhythmbox 3.0.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Mon May 26 15:15:46 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-13 (132 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: rhythmbox UpgradeStatus: Upgraded to trusty on 2014-05-15 (11 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1323276/+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 1869288] Re: "Privacy" tab in gnome-control-center is not findable
** Summary changed: - Searching for "Privacy" in Gnome Search returns "Search" tab entry in gnome-control-center + "Privacy" tab in gnome-control-center is not findable ** Description changed: - Searching for "Privacy" returns the "Search" entry in gnome-control- - center, instead of the Privacy tab entry. For all the other tab names of - gnome-control-center it works as expected, including Privacy's sub tabs. - I've tested using EN and PT-BR languages, and it happens in both. + Searching for "Privacy" using gnome-control-center search bar returns + the "Search" tab instead of the "Privacy" tab. The same thing happens + with Gnome Shell Search. - abstract: Privacy tab in gnome-control-center is not searchable. + For all the other tab names of gnome-control-center it works as + expected, including Privacy's sub tabs. I've tested using EN and PT-BR + languages, and it happens in both. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 23:42:26 2020 InstallationDate: Installed on 2020-03-08 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1869288 Title: "Privacy" tab in gnome-control-center is not findable Status in gnome-control-center package in Ubuntu: New Bug description: Searching for "Privacy" using gnome-control-center search bar returns the "Search" tab instead of the "Privacy" tab. The same thing happens with Gnome Shell Search. For all the other tab names of gnome-control-center it works as expected, including Privacy's sub tabs. I've tested using EN and PT-BR languages, and it happens in both. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 23:42:26 2020 InstallationDate: Installed on 2020-03-08 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1869288/+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 1869021] Re: desktop dash search clicking on a snap application leads to error page in software centre
** Attachment added: "search-fail.png" https://bugs.launchpad.net/snap-store/+bug/1869021/+attachment/5341961/+files/search-fail.png ** Changed in: gnome-software (Ubuntu Focal) Assignee: Ken VanDine (ken-vandine) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Eoan) Assignee: Ken VanDine (ken-vandine) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Bionic) Assignee: Ken VanDine (ken-vandine) => Robert Ancell (robert-ancell) ** Changed in: gnome-software (Ubuntu Focal) Status: New => Confirmed ** Changed in: gnome-software (Ubuntu Eoan) Status: New => Confirmed ** Changed in: gnome-software (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869021 Title: desktop dash search clicking on a snap application leads to error page in software centre Status in snap-store: New Status in gnome-software package in Ubuntu: Confirmed Status in gnome-software source package in Bionic: Confirmed Status in gnome-software source package in Eoan: Confirmed Status in gnome-software source package in Focal: Confirmed Bug description: Reproduction Steps: - search for a snap application you don't have installed in the "dash" - click that snap application - You will be led to an errored page in the software center. It looks "blank" for me - From there you can click back and usually click on the first item, and things are fine. What I would have expected to happen: - when I click the application, it takes me to software center to the application directly This is happening on Bionic with the latest updates, and on Focal as of today (2020-03-25) To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1869021/+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 1869261] Re: popups move to top left of window when opened
In the meantime please run this command while no extensions are installed to automatically send fresh system info: apport-collect 1869261 ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1869261 Title: popups move to top left of window when opened Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I open a popup selection menu or a drop-down menu from a legacy menu bar, it behaves oddly. First, it appears in about the right place. Then it jumps to the top- left of the owning window, and the items scroll off. I can navigate it with the keyboard and mouse and it's almost usable. When the popup is closed and I try to open it again, it refuses to appear until I quit the appliation and reopen it. Example 1: * open Settings * select Default Applications * click one of the options to pop up its menu * it may open in the right place, or immediately jump to the top left of the window * if it opened in place, attempts to interact cause it to jump to the top left of the window * close the popup, and it can't be opened again (at least not visibly) * close the app, reopen it, and the process can be repeated Example 2: * some apps with legacy embedded menu bars also behave weirdly, e.g. Quod Libet's menus will jump around similarly quite often, but not entirely consistently I assumed gnome-shell is responsible for positioning and rendering popups, but maybe this is a GTK+3 bug? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 27 09:55:45 2020 DisplayManager: gdm3 InstallationDate: Installed on 2011-11-06 (3063 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-25 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869261/+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 1869261] Re: popups move to top left of window when opened
Thanks. Next please report the issue to the upstream developers here: https://gitlab.gnome.org/GNOME/gnome-shell/issues and then tell us the new bug ID. Although that site is down today so maybe wait a while. -- 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/1869261 Title: popups move to top left of window when opened Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I open a popup selection menu or a drop-down menu from a legacy menu bar, it behaves oddly. First, it appears in about the right place. Then it jumps to the top- left of the owning window, and the items scroll off. I can navigate it with the keyboard and mouse and it's almost usable. When the popup is closed and I try to open it again, it refuses to appear until I quit the appliation and reopen it. Example 1: * open Settings * select Default Applications * click one of the options to pop up its menu * it may open in the right place, or immediately jump to the top left of the window * if it opened in place, attempts to interact cause it to jump to the top left of the window * close the popup, and it can't be opened again (at least not visibly) * close the app, reopen it, and the process can be repeated Example 2: * some apps with legacy embedded menu bars also behave weirdly, e.g. Quod Libet's menus will jump around similarly quite often, but not entirely consistently I assumed gnome-shell is responsible for positioning and rendering popups, but maybe this is a GTK+3 bug? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 27 09:55:45 2020 DisplayManager: gdm3 InstallationDate: Installed on 2011-11-06 (3063 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-25 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869261/+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 1869261] Re: popups move to top left of window when opened
On a second machine also running current focal (it's not convenient to do it on this one right now) I disabled extensions via the Extensions pref panel, deleted my user extensions, and removed gnome-shell- extensions. There were a handful of extensions still on disk whose packages have a lot of reverse dependencies, which I didn't remove. [clammy(~)] gsettings get org.gnome.shell enabled-extensions @as [] [clammy(~)] ls ~/.local/share/gnome-shell/extensions/ [clammy(~)] ls /usr/share/gnome-shell/extensions/ desktop-icons@csoriano ubuntu-appindicat...@ubuntu.com ubuntu-d...@ubuntu.com [clammy(~)] _ Then I rebooted and logged back and and reproduced the problem successfully as per example 1 above. ** Changed in: gnome-shell (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/1869261 Title: popups move to top left of window when opened Status in gnome-shell package in Ubuntu: New Bug description: When I open a popup selection menu or a drop-down menu from a legacy menu bar, it behaves oddly. First, it appears in about the right place. Then it jumps to the top- left of the owning window, and the items scroll off. I can navigate it with the keyboard and mouse and it's almost usable. When the popup is closed and I try to open it again, it refuses to appear until I quit the appliation and reopen it. Example 1: * open Settings * select Default Applications * click one of the options to pop up its menu * it may open in the right place, or immediately jump to the top left of the window * if it opened in place, attempts to interact cause it to jump to the top left of the window * close the popup, and it can't be opened again (at least not visibly) * close the app, reopen it, and the process can be repeated Example 2: * some apps with legacy embedded menu bars also behave weirdly, e.g. Quod Libet's menus will jump around similarly quite often, but not entirely consistently I assumed gnome-shell is responsible for positioning and rendering popups, but maybe this is a GTK+3 bug? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 27 09:55:45 2020 DisplayManager: gdm3 InstallationDate: Installed on 2011-11-06 (3063 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-25 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869261/+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 1869288] [NEW] Searching for "Privacy" in Gnome Search returns "Search" tab entry in gnome-control-center
Public bug reported: Searching for "Privacy" returns the "Search" entry in gnome-control- center, instead of the Privacy tab entry. For all the other tab names of gnome-control-center it works as expected, including Privacy's sub tabs. I've tested using EN and PT-BR languages, and it happens in both. abstract: Privacy tab in gnome-control-center is not searchable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 23:42:26 2020 InstallationDate: Installed on 2020-03-08 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-03-26 21-27-23.png" https://bugs.launchpad.net/bugs/1869288/+attachment/5341953/+files/Screenshot%20from%202020-03-26%2021-27-23.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1869288 Title: Searching for "Privacy" in Gnome Search returns "Search" tab entry in gnome-control-center Status in gnome-control-center package in Ubuntu: New Bug description: Searching for "Privacy" returns the "Search" entry in gnome-control- center, instead of the Privacy tab entry. For all the other tab names of gnome-control-center it works as expected, including Privacy's sub tabs. I've tested using EN and PT-BR languages, and it happens in both. abstract: Privacy tab in gnome-control-center is not searchable. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-20.24-generic 5.4.27 Uname: Linux 5.4.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 23:42:26 2020 InstallationDate: Installed on 2020-03-08 (18 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200304) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1869288/+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 1869274] Re: Entering and exiting overview unminimizes apps, apps are unresponsive until clicked on dash
*** This bug is a duplicate of bug 1868896 *** https://bugs.launchpad.net/bugs/1868896 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 1868896, 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 1868896 Minimized windows reappear when closing the overview -- 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/1869274 Title: Entering and exiting overview unminimizes apps, apps are unresponsive until clicked on dash Status in gnome-shell package in Ubuntu: New Bug description: Apologies for the awful title. Steps to reproduce: * Open an app * Minimize it to the tray * Enter and exit overview (Super key) Result: The minimized app will be unminimized but unresponsive. In fact it is even behind conky in my setup. Clicking on the app icon on the dash brings it to focus and restores the functionality of the app. This is a regression, it wasn't happening a couple of days ago before a series of updates to gnome-shell, mutter and gjs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 19:53:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (762 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 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/1869274/+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 1868780] Re: [virtio] Xubuntu 20.04 - Blank screen after login
Thanks but for some reason that log is truncated and missing most of the boot. Please repeat the steps in comment #9. -- 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/1868780 Title: [virtio] Xubuntu 20.04 - Blank screen after login Status in xorg-server package in Ubuntu: Incomplete Bug description: Both on Xubuntu 20.04 23rd March and 24th March daily build. Using Martin Wimpress QuickEMU setup. Installation part of xubuntu is working fine. But after install and reboot, you get the login box. I type in the password for the user and then just get a black screen and mouse cursor, no other error boxes or gui. Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only on Xubuntu daily builds do I see this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Mar 24 16:40:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] InstallationDate: Installed on 2020-03-24 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=4b1c21e9-1325-435b-9ade-04263b901e6d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+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/xorg-server/+bug/1868780/+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 1869261] Re: popups move to top left of window when opened
Since so many bugs are caused by extensions we first need you to try uninstalling these: 'quitbut...@azathoth92.hotmail.it', 'impatie...@gfxmonk.net', 'launch-new-insta...@gnome-shell-extensions.gcampax.github.com', 'native-window-placem...@gnome-shell-extensions.gcampax.github.com' Then reboot and tell us if the problem persists. Extensions need to be uninstalled completely and not just disabled because a buggy extension can still interfere with the shell while disabled. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1869261 Title: popups move to top left of window when opened Status in gnome-shell package in Ubuntu: Incomplete Bug description: When I open a popup selection menu or a drop-down menu from a legacy menu bar, it behaves oddly. First, it appears in about the right place. Then it jumps to the top- left of the owning window, and the items scroll off. I can navigate it with the keyboard and mouse and it's almost usable. When the popup is closed and I try to open it again, it refuses to appear until I quit the appliation and reopen it. Example 1: * open Settings * select Default Applications * click one of the options to pop up its menu * it may open in the right place, or immediately jump to the top left of the window * if it opened in place, attempts to interact cause it to jump to the top left of the window * close the popup, and it can't be opened again (at least not visibly) * close the app, reopen it, and the process can be repeated Example 2: * some apps with legacy embedded menu bars also behave weirdly, e.g. Quod Libet's menus will jump around similarly quite often, but not entirely consistently I assumed gnome-shell is responsible for positioning and rendering popups, but maybe this is a GTK+3 bug? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 27 09:55:45 2020 DisplayManager: gdm3 InstallationDate: Installed on 2011-11-06 (3063 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-25 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869261/+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 1869272] Re: [Wishlist] Option to remove trash and home folders from desktop
TBH I have no firm opinion on the trade off between Settings and Tweaks (the latter not installed by default in Ubuntu). Just wanted to mention that you don't necessarily need to use terminal commands to do it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1869272 Title: [Wishlist] Option to remove trash and home folders from desktop Status in gnome-control-center package in Ubuntu: New Bug description: Feature proposal: Why do I need to type a command if I want to remove the trash and/or the home folder(s) from the desktop? There should be an option in the Appearance tab: The new interface: _ |Window colors | |_ | |[ ||] | |[ ||] | |[ ||] | |[ ||] | |[Light| Standard |Dark] | || |Dock| || |Auto-hide the dock [x] | |Icon size [===--] | |Position on screen [Left] | || |Desktop | || |Show trash folder [x] | |Show home folder [x] | || || || || I did it with this text editor. You should be able to do it faster than me. I want the feature now! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1869272/+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 1869274] Re: Entering and exiting overview unminimizes apps, apps are unresponsive until clicked on dash
Tested in an other PC, with Nvidia graphics (the bug report is from a Intel laptop) and brand new Ubuntu 20.04 and the bug is there too. -- 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/1869274 Title: Entering and exiting overview unminimizes apps, apps are unresponsive until clicked on dash Status in gnome-shell package in Ubuntu: New Bug description: Apologies for the awful title. Steps to reproduce: * Open an app * Minimize it to the tray * Enter and exit overview (Super key) Result: The minimized app will be unminimized but unresponsive. In fact it is even behind conky in my setup. Clicking on the app icon on the dash brings it to focus and restores the functionality of the app. This is a regression, it wasn't happening a couple of days ago before a series of updates to gnome-shell, mutter and gjs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 19:53:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (762 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 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/1869274/+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 1869102] Re: Minor typo in translatable string in src/remmina_ssh.c
heh that's what I meant to say, cheers ^^ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1869102 Title: Minor typo in translatable string in src/remmina_ssh.c Status in remmina package in Ubuntu: Fix Released Bug description: Entry 210 (https://translations.launchpad.net/ubuntu/focal/+source/remmina/+pots/remmina/en_GB/210/+translate) currently reads: "SSH passphrase is empty, it should not." instead of "SSH passphrase is empty, it should not be." Located in ../src/remmina_ssh.c:255 cheers, Ant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1869102/+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 1869102] Re: Minor typo in translatable string in src/remmina_ssh.c
Upstream approved the MR and updated the POT file. Closing this bug now, even if it will take a while before the change makes it to Ubuntu. ** Changed in: remmina (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1869102 Title: Minor typo in translatable string in src/remmina_ssh.c Status in remmina package in Ubuntu: Fix Released Bug description: Entry 210 (https://translations.launchpad.net/ubuntu/focal/+source/remmina/+pots/remmina/en_GB/210/+translate) currently reads: "SSH passphrase is empty, it should not." instead of "SSH passphrase is empty, it should not be." Located in ../src/remmina_ssh.c:255 cheers, Ant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1869102/+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 1869279] [NEW] zsys clutters up the system and stops system updates.
Public bug reported: Updates of my system stopped, because the boot partition has been cluttered up with snapshots. Note that remedy in the error message is completely wrong! See the annex! >From a programming point of view zsys and zsysctl do work and are an achievement. However from an architectural point of view, they hamper the elegance of zfs. They keep creating snapshots and filling up the partitions without any simple way to control the increase in clutter and size. I now have over 25 snapshots of my system and all snapshots, except say a few are completely useless. The commands of zsysctl use a terminology different from zfs for the same objects and the commands have no added value compared to those of zfs itself. Documentation of the commands are missing and it is completely unclear, which functions will be implemented at which moment in the future. Functions are missing and one of the obvious missing functions is related to new users created after installation. For my 2 main systems (desktop and laptop), both running 20.04, I have purged zsys and zsysctl and I will rely on plain zfs and its grub related adaptions. For the VM I will delete the snapshots and pray for a solution for people with less experience than me. Please if you are serious about zfs: - create a good written architecture specification - create a project plan, about which functions will be implemented when. - collect enough programming capacity to implement those changes according to that plan. I have the feeling, that the current "team" is completely understaffed and lacks the OpenZFS, ZOL and Ubuntu management support, they deserve. Why should you take my warning serious? I have 40 years of experience in software development; have designed an OS; run a software department of more than 100 persons for more than a decade and finished my last 10 working years (2001-2010) as chief architect of Eurocontrol (Say the European FAA, serving ~30 independent countries). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: zsys 0.4.1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 18:51:53 2020 InstallationDate: Installed on 2020-02-01 (54 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200131) SourcePackage: zsys UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: zsys (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Screenshot from 2020-03-26 18-50-42.png" https://bugs.launchpad.net/bugs/1869279/+attachment/5341933/+files/Screenshot%20from%202020-03-26%2018-50-42.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to zsys in Ubuntu. https://bugs.launchpad.net/bugs/1869279 Title: zsys clutters up the system and stops system updates. Status in zsys package in Ubuntu: New Bug description: Updates of my system stopped, because the boot partition has been cluttered up with snapshots. Note that remedy in the error message is completely wrong! See the annex! From a programming point of view zsys and zsysctl do work and are an achievement. However from an architectural point of view, they hamper the elegance of zfs. They keep creating snapshots and filling up the partitions without any simple way to control the increase in clutter and size. I now have over 25 snapshots of my system and all snapshots, except say a few are completely useless. The commands of zsysctl use a terminology different from zfs for the same objects and the commands have no added value compared to those of zfs itself. Documentation of the commands are missing and it is completely unclear, which functions will be implemented at which moment in the future. Functions are missing and one of the obvious missing functions is related to new users created after installation. For my 2 main systems (desktop and laptop), both running 20.04, I have purged zsys and zsysctl and I will rely on plain zfs and its grub related adaptions. For the VM I will delete the snapshots and pray for a solution for people with less experience than me. Please if you are serious about zfs: - create a good written architecture specification - create a project plan, about which functions will be implemented when. - collect enough programming capacity to implement those changes according to that plan. I have the feeling, that the current "team" is completely understaffed and lacks the OpenZFS, ZOL and Ubuntu management support, they deserve. Why should you take my warning serious? I have 40 years of experience in software development; have designed an OS; run a software department of more than 100 persons for more than a decade and finished my last
[Desktop-packages] [Bug 1866146] Re: GNOME Shell 3.35.91 extension's preferences doesn't load
You need to run: sudo apt install gnome-shell-extension-prefs to make extension preferences work in Ubuntu's packaging of gnome-shell. -- 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/1866146 Title: GNOME Shell 3.35.91 extension's preferences doesn't load Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: Using Ubuntu Focal Fossa development with gnome-shell 3.35.91 and preferences for extensions doesn't load. Tried opening using the browser, gnome-tweaks, or the new extensions app. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 12:36:15 2020 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-03 (518 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-12-10 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866146/+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 1866146] Re: GNOME Shell 3.35.91 extension's preferences doesn't load
Not fixed yet in 3.36.0-2ubuntu1 -- 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/1866146 Title: GNOME Shell 3.35.91 extension's preferences doesn't load Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: Using Ubuntu Focal Fossa development with gnome-shell 3.35.91 and preferences for extensions doesn't load. Tried opening using the browser, gnome-tweaks, or the new extensions app. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 12:36:15 2020 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-03 (518 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-12-10 (85 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1866146/+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 1869272] Re: [Wishlist] Option to remove trash and home folders from desktop
Two settings app to configure my system... Which one do I open and when? After spending 10min in one app I should spend 10 other minutes in the other to then spend 30 other mins in the web to the install dconf... I feel like settings app need an update... Don't you think so? -- 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/1869272 Title: [Wishlist] Option to remove trash and home folders from desktop Status in gnome-control-center package in Ubuntu: New Bug description: Feature proposal: Why do I need to type a command if I want to remove the trash and/or the home folder(s) from the desktop? There should be an option in the Appearance tab: The new interface: _ |Window colors | |_ | |[ ||] | |[ ||] | |[ ||] | |[ ||] | |[Light| Standard |Dark] | || |Dock| || |Auto-hide the dock [x] | |Icon size [===--] | |Position on screen [Left] | || |Desktop | || |Show trash folder [x] | |Show home folder [x] | || || || || I did it with this text editor. You should be able to do it faster than me. I want the feature now! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1869272/+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 1869272] Re: [Wishlist] Option to remove trash and home folders from desktop
You don't need to run a command. It can be managed from Extensions -> Desktop icons in Tweaks. -- 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/1869272 Title: [Wishlist] Option to remove trash and home folders from desktop Status in gnome-control-center package in Ubuntu: New Bug description: Feature proposal: Why do I need to type a command if I want to remove the trash and/or the home folder(s) from the desktop? There should be an option in the Appearance tab: The new interface: _ |Window colors | |_ | |[ ||] | |[ ||] | |[ ||] | |[ ||] | |[Light| Standard |Dark] | || |Dock| || |Auto-hide the dock [x] | |Icon size [===--] | |Position on screen [Left] | || |Desktop | || |Show trash folder [x] | |Show home folder [x] | || || || || I did it with this text editor. You should be able to do it faster than me. I want the feature now! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1869272/+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 1869274] [NEW] Entering and exiting overview unminimizes apps, apps are unresponsive until clicked on dash
Public bug reported: Apologies for the awful title. Steps to reproduce: * Open an app * Minimize it to the tray * Enter and exit overview (Super key) Result: The minimized app will be unminimized but unresponsive. In fact it is even behind conky in my setup. Clicking on the app icon on the dash brings it to focus and restores the functionality of the app. This is a regression, it wasn't happening a couple of days ago before a series of updates to gnome-shell, mutter and gjs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 19:53:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (762 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869274 Title: Entering and exiting overview unminimizes apps, apps are unresponsive until clicked on dash Status in gnome-shell package in Ubuntu: New Bug description: Apologies for the awful title. Steps to reproduce: * Open an app * Minimize it to the tray * Enter and exit overview (Super key) Result: The minimized app will be unminimized but unresponsive. In fact it is even behind conky in my setup. Clicking on the app icon on the dash brings it to focus and restores the functionality of the app. This is a regression, it wasn't happening a couple of days ago before a series of updates to gnome-shell, mutter and gjs. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 19:53:37 2020 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-23 (762 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 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/1869274/+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 1869272] Re: [Wishlist] Option to remove trash and home folders from desktop
Click the edit button to see what I draw :D -- 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/1869272 Title: [Wishlist] Option to remove trash and home folders from desktop Status in gnome-control-center package in Ubuntu: New Bug description: Feature proposal: Why do I need to type a command if I want to remove the trash and/or the home folder(s) from the desktop? There should be an option in the Appearance tab: The new interface: _ |Window colors | |_ | |[ ||] | |[ ||] | |[ ||] | |[ ||] | |[Light| Standard |Dark] | || |Dock| || |Auto-hide the dock [x] | |Icon size [===--] | |Position on screen [Left] | || |Desktop | || |Show trash folder [x] | |Show home folder [x] | || || || || I did it with this text editor. You should be able to do it faster than me. I want the feature now! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1869272/+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 1869272] [NEW] [Wishlist] Option to remove trash and home folders from desktop
Public bug reported: Feature proposal: Why do I need to type a command if I want to remove the trash and/or the home folder(s) from the desktop? There should be an option in the Appearance tab: The new interface: _ |Window colors | |_ | |[ ||] | |[ ||] | |[ ||] | |[ ||] | |[Light| Standard |Dark] | || |Dock| || |Auto-hide the dock [x] | |Icon size [===--] | |Position on screen [Left] | || |Desktop | || |Show trash folder [x] | |Show home folder [x] | || || || || I did it with this text editor. You should be able to do it faster than me. I want the feature now! ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1869272 Title: [Wishlist] Option to remove trash and home folders from desktop Status in gnome-control-center package in Ubuntu: New Bug description: Feature proposal: Why do I need to type a command if I want to remove the trash and/or the home folder(s) from the desktop? There should be an option in the Appearance tab: The new interface: _ |Window colors | |_ | |[ ||] | |[ ||] | |[ ||] | |[ ||] | |[Light| Standard |Dark] | || |Dock| || |Auto-hide the dock [x] | |Icon size [===--] | |Position on screen [Left] | || |Desktop | || |Show trash folder [x] | |Show home folder [x] | || || || || I did it with this text editor. You should be able to do it faster than me. I want the feature now! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1869272/+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
Re: [Desktop-packages] [Bug 1868911] Re: Exiting overview on empty workspace causes windows from other workspaces to be visible
joreporter <1868...@bugs.launchpad.net> writes: > Happening to me as well. but with 3.36.0-2ubuntu1. Same here; that's the version this bug report is against. -- 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/1868911 Title: Exiting overview on empty workspace causes windows from other workspaces to be visible Status in gnome-shell package in Ubuntu: Fix Committed Bug description: $ dpkg-query -W gnome-shell gnome-shell 3.36.0-2ubuntu1 $ lsb_release -rc Release:20.04 Codename: focal $ _ When I toggle in and out of the overview on an empty workspace, windows from other workspaces appear. They are not interactable, so this seems more like a rendering bug than the windows really being teleported to another workspace. Switching back to another workspace that has windows causes the ghost windows to disappear. Opening a window in the empty workspace makes it appear on top of the ghost windows, and I have to switch to another workspace and back again to make only the new window be visible. I am using the vanilla "GNOME" session type. I did not observe this behaviour with gnome-shell 3.35.91-1ubuntu2. As well as the annoyance factor, of course there's a privacy angle to showing random windows at surprising times. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2011-11-06 (3062 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: wayland-session focal third-party-packages Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-25 (29 days ago) UserGroups: adm admin cdrom dialout docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868911/+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 1869263] Re: Log-in screen is wrongly themed in vanilla-gnome-desktop mode
The issue is not a gnome-shell one but vanilla-gnome-desktop that needs to be updated, the alternative changed, the alternative is now gdm3-theme.gresource ** Changed in: gnome-shell (Ubuntu) Status: New => Invalid -- 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/1869263 Title: Log-in screen is wrongly themed in vanilla-gnome-desktop mode Status in gnome-shell package in Ubuntu: Invalid Bug description: For several releases now I have been running Ubuntu with the 'vanilla- gnome-desktop' package installed. This changes the start-up, log-in and shutdown screens to dark grey with Ubuntu GNOME logos. Highlighting, underlining and sliders are blue on the log-in screen. Since the update to gnome-shell 3.36 I am seeing the log-in screen as being a purple colour. The log-in box has an orange outline and the indicators in the top bar have an orange underline when clicked. The volume and brightness sliders are also the wrong colour. The colour of the indicator underline and sliders display in blue once logged in. The start-up and shutdown screens display correctly which makes the log-in screen look very out of place. Looking at my Ubuntu 18.04 installation the following files seem to be missing: /etc/alternatives/gdm3.css /usr/share/gnome-shell/theme/gdm3.css So presumably the log-in screen is falling back to the standard Ubuntu theme as it can't find the GDM theme. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 26 21:04:48 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (314 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-11-08 (138 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869263/+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 1868911] Re: Exiting overview on empty workspace causes windows from other workspaces to be visible
Happening to me as well. but with 3.36.0-2ubuntu1. -- 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/1868911 Title: Exiting overview on empty workspace causes windows from other workspaces to be visible Status in gnome-shell package in Ubuntu: Fix Committed Bug description: $ dpkg-query -W gnome-shell gnome-shell 3.36.0-2ubuntu1 $ lsb_release -rc Release:20.04 Codename: focal $ _ When I toggle in and out of the overview on an empty workspace, windows from other workspaces appear. They are not interactable, so this seems more like a rendering bug than the windows really being teleported to another workspace. Switching back to another workspace that has windows causes the ghost windows to disappear. Opening a window in the empty workspace makes it appear on top of the ghost windows, and I have to switch to another workspace and back again to make only the new window be visible. I am using the vanilla "GNOME" session type. I did not observe this behaviour with gnome-shell 3.35.91-1ubuntu2. As well as the annoyance factor, of course there's a privacy angle to showing random windows at surprising times. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2011-11-06 (3062 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: gnome-shell 3.36.0-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Tags: wayland-session focal third-party-packages Uname: Linux 5.4.0-18-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-02-25 (29 days ago) UserGroups: adm admin cdrom dialout docker libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1868911/+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 1869263] Re: Log-in screen is wrong colour in vanilla-gnome-desktop mode
** Description changed: For several releases now I have been running Ubuntu with the 'vanilla- gnome-desktop' package installed. This changes the start-up, log-in and shutdown screens to dark grey with Ubuntu GNOME logos. Highlighting, underlining and sliders are blue on the log-in screen. Since the update to gnome-shell 3.36 I am seeing the log-in screen as being a purple colour. The log-in box has an orange outline and the indicators in the top bar have an orange underline when clicked. The volume and brightness sliders are also the wrong colour. The colour of the indicator underline and sliders display in blue once logged in. The start-up and shutdown screens display correctly which makes the log- in screen look very out of place. + + Looking at my Ubuntu 18.04 installation the following files seem to be missing: + /etc/alternatives/gdm3.css + /usr/share/gnome-shell/theme/gdm3.css + + So presumably the log-in screen is falling back to the standard Ubuntu + theme as it can't find the GDM theme. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 26 21:04:48 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (314 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-11-08 (138 days ago) ** Summary changed: - Log-in screen is wrong colour in vanilla-gnome-desktop mode + Log-in screen is wrongly themed in vanilla-gnome-desktop mode -- 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/1869263 Title: Log-in screen is wrongly themed in vanilla-gnome-desktop mode Status in gnome-shell package in Ubuntu: New Bug description: For several releases now I have been running Ubuntu with the 'vanilla- gnome-desktop' package installed. This changes the start-up, log-in and shutdown screens to dark grey with Ubuntu GNOME logos. Highlighting, underlining and sliders are blue on the log-in screen. Since the update to gnome-shell 3.36 I am seeing the log-in screen as being a purple colour. The log-in box has an orange outline and the indicators in the top bar have an orange underline when clicked. The volume and brightness sliders are also the wrong colour. The colour of the indicator underline and sliders display in blue once logged in. The start-up and shutdown screens display correctly which makes the log-in screen look very out of place. Looking at my Ubuntu 18.04 installation the following files seem to be missing: /etc/alternatives/gdm3.css /usr/share/gnome-shell/theme/gdm3.css So presumably the log-in screen is falling back to the standard Ubuntu theme as it can't find the GDM theme. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 26 21:04:48 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (314 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-11-08 (138 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869263/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Same insue here with a Dell G3 laptop. Microphone, nor any input device its recognized -- 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/1840725 Title: Microphone not working in Ubuntu 18.04.3 LTS on new hp- spectre-x360-convertible-15 laptop Status in alsa-driver package in Ubuntu: Confirmed Bug description: Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp- spectre-x360-convertible-15 laptop. The microphone works perfectly on Windows 10 (present in Dual boot mode). Initially, Internal Microphone was not even detected but installing alsa-tools-gui and overriding pin 0x12 to the Internal Microphone fixed that issue. [Pin 0x13 does not work and causes static in a headphone if it is plugged in.] Microphone is not able to pick up any sound. I changed levels/settings in alsamixer, pavucontrol without any success: In alsamixer: Experimented with levels ranging from very low to very high for Internal Mic, Capture, etc. In pavucontrol: Set the Internal Mic as a fallback device, unlocked the channels for the mic, experimented with reducing the level for one of the channels (reduced right mic level to Silence while keeping the left mic level normal/high and vice versa). alsa-info: http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f arecord -l List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1869263] [NEW] Log-in screen is wrong colour in vanilla-gnome-desktop mode
Public bug reported: For several releases now I have been running Ubuntu with the 'vanilla- gnome-desktop' package installed. This changes the start-up, log-in and shutdown screens to dark grey with Ubuntu GNOME logos. Highlighting, underlining and sliders are blue on the log-in screen. Since the update to gnome-shell 3.36 I am seeing the log-in screen as being a purple colour. The log-in box has an orange outline and the indicators in the top bar have an orange underline when clicked. The volume and brightness sliders are also the wrong colour. The colour of the indicator underline and sliders display in blue once logged in. The start-up and shutdown screens display correctly which makes the log- in screen look very out of place. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 26 21:04:48 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (314 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-11-08 (138 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869263 Title: Log-in screen is wrong colour in vanilla-gnome-desktop mode Status in gnome-shell package in Ubuntu: New Bug description: For several releases now I have been running Ubuntu with the 'vanilla- gnome-desktop' package installed. This changes the start-up, log-in and shutdown screens to dark grey with Ubuntu GNOME logos. Highlighting, underlining and sliders are blue on the log-in screen. Since the update to gnome-shell 3.36 I am seeing the log-in screen as being a purple colour. The log-in box has an orange outline and the indicators in the top bar have an orange underline when clicked. The volume and brightness sliders are also the wrong colour. The colour of the indicator underline and sliders display in blue once logged in. The start-up and shutdown screens display correctly which makes the log-in screen look very out of place. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Mar 26 21:04:48 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (314 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2019-11-08 (138 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869263/+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 1869261] Re: popups move to top left of window when opened
And here's Quod Libet's menu bar acting similarly. ** Attachment added: "Screencast from 27-03-20 10:14:37.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869261/+attachment/5341908/+files/Screencast%20from%2027-03-20%2010%3A14%3A37.webm -- 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/1869261 Title: popups move to top left of window when opened Status in gnome-shell package in Ubuntu: New Bug description: When I open a popup selection menu or a drop-down menu from a legacy menu bar, it behaves oddly. First, it appears in about the right place. Then it jumps to the top- left of the owning window, and the items scroll off. I can navigate it with the keyboard and mouse and it's almost usable. When the popup is closed and I try to open it again, it refuses to appear until I quit the appliation and reopen it. Example 1: * open Settings * select Default Applications * click one of the options to pop up its menu * it may open in the right place, or immediately jump to the top left of the window * if it opened in place, attempts to interact cause it to jump to the top left of the window * close the popup, and it can't be opened again (at least not visibly) * close the app, reopen it, and the process can be repeated Example 2: * some apps with legacy embedded menu bars also behave weirdly, e.g. Quod Libet's menus will jump around similarly quite often, but not entirely consistently I assumed gnome-shell is responsible for positioning and rendering popups, but maybe this is a GTK+3 bug? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 27 09:55:45 2020 DisplayManager: gdm3 InstallationDate: Installed on 2011-11-06 (3063 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-25 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869261/+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 1869261] [NEW] popups move to top left of window when opened
Public bug reported: When I open a popup selection menu or a drop-down menu from a legacy menu bar, it behaves oddly. First, it appears in about the right place. Then it jumps to the top- left of the owning window, and the items scroll off. I can navigate it with the keyboard and mouse and it's almost usable. When the popup is closed and I try to open it again, it refuses to appear until I quit the appliation and reopen it. Example 1: * open Settings * select Default Applications * click one of the options to pop up its menu * it may open in the right place, or immediately jump to the top left of the window * if it opened in place, attempts to interact cause it to jump to the top left of the window * close the popup, and it can't be opened again (at least not visibly) * close the app, reopen it, and the process can be repeated Example 2: * some apps with legacy embedded menu bars also behave weirdly, e.g. Quod Libet's menus will jump around similarly quite often, but not entirely consistently I assumed gnome-shell is responsible for positioning and rendering popups, but maybe this is a GTK+3 bug? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 27 09:55:45 2020 DisplayManager: gdm3 InstallationDate: Installed on 2011-11-06 (3063 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-25 (30 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session -- 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/1869261 Title: popups move to top left of window when opened Status in gnome-shell package in Ubuntu: New Bug description: When I open a popup selection menu or a drop-down menu from a legacy menu bar, it behaves oddly. First, it appears in about the right place. Then it jumps to the top- left of the owning window, and the items scroll off. I can navigate it with the keyboard and mouse and it's almost usable. When the popup is closed and I try to open it again, it refuses to appear until I quit the appliation and reopen it. Example 1: * open Settings * select Default Applications * click one of the options to pop up its menu * it may open in the right place, or immediately jump to the top left of the window * if it opened in place, attempts to interact cause it to jump to the top left of the window * close the popup, and it can't be opened again (at least not visibly) * close the app, reopen it, and the process can be repeated Example 2: * some apps with legacy embedded menu bars also behave weirdly, e.g. Quod Libet's menus will jump around similarly quite often, but not entirely consistently I assumed gnome-shell is responsible for positioning and rendering popups, but maybe this is a GTK+3 bug? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 27 09:55:45 2020 DisplayManager: gdm3 InstallationDate: Installed on 2011-11-06 (3063 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-25 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869261/+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 1869261] Re: popups move to top left of window when opened
Brief screencast showing the problem. ** Attachment added: "Screencast from 27-03-20 10:09:13.webm" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869261/+attachment/5341906/+files/Screencast%20from%2027-03-20%2010%3A09%3A13.webm -- 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/1869261 Title: popups move to top left of window when opened Status in gnome-shell package in Ubuntu: New Bug description: When I open a popup selection menu or a drop-down menu from a legacy menu bar, it behaves oddly. First, it appears in about the right place. Then it jumps to the top- left of the owning window, and the items scroll off. I can navigate it with the keyboard and mouse and it's almost usable. When the popup is closed and I try to open it again, it refuses to appear until I quit the appliation and reopen it. Example 1: * open Settings * select Default Applications * click one of the options to pop up its menu * it may open in the right place, or immediately jump to the top left of the window * if it opened in place, attempts to interact cause it to jump to the top left of the window * close the popup, and it can't be opened again (at least not visibly) * close the app, reopen it, and the process can be repeated Example 2: * some apps with legacy embedded menu bars also behave weirdly, e.g. Quod Libet's menus will jump around similarly quite often, but not entirely consistently I assumed gnome-shell is responsible for positioning and rendering popups, but maybe this is a GTK+3 bug? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Mar 27 09:55:45 2020 DisplayManager: gdm3 InstallationDate: Installed on 2011-11-06 (3063 days ago) InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111011) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-02-25 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869261/+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 1715435] Re: Can't lock screen with keyboard shortcuts when using lightdm
The fix provided by chris-18 worked for me, same issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1715435 Title: Can't lock screen with keyboard shortcuts when using lightdm Status in gnome-shell package in Ubuntu: Confirmed Status in lightdm package in Ubuntu: Confirmed Bug description: Trying to use Super+L or Ctrl+Alt+L, I cannot lock the screen. Additionally, if I wait a very long time the screen does not lock either. Switching from LightDM to GDM3 fixes the issue. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.25.91-0ubuntu3 ProcVersionSignature: Ubuntu 4.12.0-12.13-generic 4.12.8 Uname: Linux 4.12.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 6 09:17:35 2017 DisplayManager: lightdm InstallationDate: Installed on 2016-01-22 (592 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160117) 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/1715435/+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 1868116] Re: QEMU monitor no longer works
Subscribed and Assigned to Ubuntu Desktop to get to 0.60.1 before Focal releases. I'd be happy about an update here that this surely is on your todo list. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works Status in QEMU: New Status in qemu package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Triaged Bug description: Repro: VTE $ meson _build && ninja -C _build && ninja -C _build install qemu: $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user --disable-linux-user --disable-docs --disable-guest-agent --disable-sdl --enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt --disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi --disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir --disable-seccomp --disable-glusterfs --disable-tpm --disable-numa --disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs --disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma --disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock --disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user --disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs --disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat --disable-qed --disable-parallels --disable-sheepdog --disable-avx2 --disable-nettle --disable-gnutls --disable-capstone --disable-tools --disable-libpmem --disable-iconv --disable-cap-ng $ make Test: $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH ./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso - switch to monitor with CTRL+ALT+2 - try to enter something Affects head of both usptream git repos. --- original bug --- It was observed that the QEMU console (normally accessible using Ctrl+Alt+2) accepts no input, so it can't be used. This is being problematic because there are cases where it's required to send commands to the guest, or key combinations that the host would grab (as Ctrl-Alt-F1 or Alt-F4). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu 1:4.2-3ubuntu2 Uname: Linux 5.6.0-rc6+ x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 12:16:31 2020 Dependencies: InstallationDate: Installed on 2017-06-13 (1009 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND qemu-system-x86 Sl+ 1000 1000 34275 25235 29.2 qemu-system-x86_64 -m 4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel kvm -device nec-usb-xhci -serial vc -serial stdio -hda /home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio kvm-nx-lpage-re S0 0 34284 2 0.0 [kvm-nx-lpage-re] kvm-pit/34275 S0 0 34286 2 0.0 [kvm-pit/34275] MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 zswap.enabled=1 zswap.zpool=z3fold resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: qemu UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1868116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1868116] Re: QEMU monitor no longer works
>From IRC: [16:10] cpaelzer, @vte, we should get 0.60.1 for focal, 0.59.91 is a rc1 for 0.60, we are lacking behind merging the stable version from Debian but it's on our backlog (kenvandine was look at that one), the .1 is part of GNOME 3.36.1 which we plan to get before release (I would understand if you would like to backport a patch to help testing rather than waiting though) >From VTE Bug: The standard Ubuntu freeze doesn't apply to GNOME packages. Usually Ubuntu aims to ship latest GNOME x.1. VTE is part of GNOME, VTE 0.60.0 is part of GNOME 3.36.0, VTE 0.60.1 belongs to GNOME 3.36.1 etc. Accordingly, 0.60.0 -> 0.60.1 contains important bugfixes only, no new features. In this particular case, 0.60.1 will bring a trivial shell script fix (quite important for non-VTE users), and hopefully this one. It would be outright ridiculous for an LTS distro to ship an unstable VTE. So, the only reasonable thing for Ubuntu 20.04 is to ship VTE 0.60.1. Anyway, this is not the right place to discuss it. But gladly there now is a commit with a fix: https://gitlab.gnome.org/GNOME/vte/-/commit/277ee003066b3993cf6d55a05606009caac69015 I agree that we need this for 20.04, and therefore will set this up in prio and assign it to the Desktop team. ** Changed in: vte2.91 (Ubuntu) Assignee: (unassigned) => Ubuntu Desktop (ubuntu-desktop) ** Changed in: vte2.91 (Ubuntu) Status: New => Triaged ** Changed in: vte2.91 (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works Status in QEMU: New Status in qemu package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: Triaged Bug description: Repro: VTE $ meson _build && ninja -C _build && ninja -C _build install qemu: $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user --disable-linux-user --disable-docs --disable-guest-agent --disable-sdl --enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt --disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi --disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir --disable-seccomp --disable-glusterfs --disable-tpm --disable-numa --disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs --disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma --disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock --disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user --disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs --disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat --disable-qed --disable-parallels --disable-sheepdog --disable-avx2 --disable-nettle --disable-gnutls --disable-capstone --disable-tools --disable-libpmem --disable-iconv --disable-cap-ng $ make Test: $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH ./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso - switch to monitor with CTRL+ALT+2 - try to enter something Affects head of both usptream git repos. --- original bug --- It was observed that the QEMU console (normally accessible using Ctrl+Alt+2) accepts no input, so it can't be used. This is being problematic because there are cases where it's required to send commands to the guest, or key combinations that the host would grab (as Ctrl-Alt-F1 or Alt-F4). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu 1:4.2-3ubuntu2 Uname: Linux 5.6.0-rc6+ x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 12:16:31 2020 Dependencies: InstallationDate: Installed on 2017-06-13 (1009 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND qemu-system-x86 Sl+ 1000 1000 34275 25235 29.2 qemu-system-x86_64 -m 4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel kvm -device nec-usb-xhci -serial vc -serial stdio -hda /home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio kvm-nx-lpage-re S0 0 34284 2 0.0 [kvm-nx-lpage-re] kvm-pit/34275 S0 0 34286 2 0.0 [kvm-pit/34275] MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 zswap.enabled=1 zswap.zpool=z3fold resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc
[Desktop-packages] [Bug 1857183] Re: No systemtrayicon available
Could you include the output of that command? $ gsettings get org.gnome.shell enabled-extensions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1857183 Title: No systemtrayicon available Status in hplip package in Ubuntu: Confirmed Bug description: HP Linux Imaging and Printing System (ver. 3.19.12) System Tray Status Service ver. 2.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) No systemtrayicon available fabrizio@fabrizio-1TB:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 fabrizio@fabrizio-1TB:~$ apt-cache policy hplip hplip: Installato: 3.17.10+repack0-5 Candidato: 3.17.10+repack0-5 Tabella versione: *** 3.17.10+repack0-5 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1857183/+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 1865170] Re: lid close simply turns off laptop screen
Thanks for opening a bug and testing. Let's mark it fix released. Please re-open if you have found it fails again. ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gnome-session (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1865170 Title: lid close simply turns off laptop screen Status in gnome-session package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: OS: Ubuntu 18.04 LTS (beaver-three-eyed-raven X92.1) ubuntu-session version: 3.28.1-0ubuntu3 Expected behavior: On laptop screen close, system should suspend Actual behavior: On laptop screen close, laptop screen disabled Previously, I triggered 'suspend when laptop lid is closed' in gnome- tweaks. This worked fine until about 2-3 days ago, when I came back to work with a dead laptop (I don't charge overnight, usually, but I do use a dock at work). Now, whenever I close my laptop screen, it doesn't trigger sleep - instead, it simply disables the laptop screen, resulting in my external monitor being used as the only output screen. Once I re-open my laptop, the laptop screen is re-enabled as the primary monitor. This happens regardless of connection to my dock. I tested this by unplugging my laptop, closing it, letting it sit for 3 minutes, then re-opening it. While the laptop was closed, fans still ran. When I re- opened my laptop, the lock screen didn't appear. Links to attempted fixes that didn't work: - https://askubuntu.com/questions/1115572/ubuntu-18-04-dell-xps15-9570-impossible-to-reliably-suspend-hibernate - https://askubuntu.com/questions/1029474/ubuntu-18-04-dell-xps13-9370-no-longer-suspends-on-lid-close - https://www.dell.com/community/Laptops-General-Read-Only/Sleep-Issues-and-Wake-Up-Issues-xps-13/td-p/5018369 - https://askubuntu.com/questions/15520/how-can-i-tell-ubuntu-to-do-nothing-when-i-close-my-laptop-lid Results of attempted fixes: - mem_sleep: no behavior change (files correctly modified) - pm-hibernate: first run, hangs until I kill the process. future runs result in exit code 1. - update bios: already on latest bios - logind.conf: no behavior change - gnome tweaks: no behavior change ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-session 3.28.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 Uname: Linux 4.15.0-1073-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Feb 28 10:23:52 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 InstallationDate: Installed on 2020-01-08 (51 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/zsh SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: colton 4205 F pulseaudio /dev/snd/controlC0: colton 4205 F pulseaudio CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-three-eyed-raven+X92+beaver-three-eyed-raven+X92.1 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-01-08 (53 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. XPS 13 7390 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1073-oem root=UUID=ef2a7f80-1cfd-48d6-a2be-0875e4832f2f ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-1073.83-oem 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-1073-oem N/A linux-backports-modules-4.15.0-1073-oem N/A linux-firmware 1.173.15 Tags: bionic Uname: Linux 4.15.0-1073-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip docker libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.name: 0377MH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10
[Desktop-packages] [Bug 1868409] Re: gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by sna
The desktop team is currently working on changes to update-manager which
would replace snaps with deb packages and this would help people who
installed or upgraded to the development release of Ubuntu early.
https://code.launchpad.net/~marcustomlinson/update-manager/update-
manager/+merge/380060
However, that would not help you out as you are using apt directly.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1868409
Title:
gnome-{calculator,logs,characters} snaps not removed after the
equivalent APT packages are installed on 20.04, and gnome-software APT
package not replaced by snap-store
Status in gnome-calculator package in Ubuntu:
New
Status in ubuntu-meta package in Ubuntu:
Confirmed
Bug description:
I'm trialing the development release of Ubuntu 20.04, installed in
December and kept up-to-date by regularly running apt full-upgrade.
I understand from [1] that 20.04 will ship
gnome-{calculator,logs,characters} as APT packages rather than snap
apps, and gnome-software as a snap app (called snap-store) rather than
an APT package.
Following an apt full-upgrade in late February, I now have:
* both the snap and the APT versions of gnome-{calculator,logs,characters}
* still only the APT version of gnome-software, no snap-store
Is this normal? A user in the #ubuntu+1 IRC channel reports that a
fresh install of the development release:
* only features the APT versions of gnome-{calculator,logs,characters}
* features the snap-store (but also the APT version of gnome-software)
Are users of older installs of the development release supposed to
manually uninstall the snap versions of
gnome-{calculator,logs,characters} and manually install the snap-
store?
[1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
remove-for-snap-snap-store/14542
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1868409/+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 1730612] Re: Enable Remote desktop feature during build
Link in comment #3 also shows an upstream pipewire master https://launchpad.net/~jan-koester/+archive/ubuntu/pipewiremaster Maybe we could get that linked as the upstream? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1730612 Title: Enable Remote desktop feature during build Status in Default settings and artwork for Baltix OS: New Status in mutter package in Ubuntu: Triaged Bug description: Currently there are no way to use Remote Desktop (Desktop sharing) and Screen Recording in Ubuntu 17.10 Wayland (default) session because Remote desktop feature isn't enabled during build :( Please use --enable-remote-desktop during build, see https://wiki.gnome.org/Projects/Mutter/RemoteDesktop Currently in mutter 3.26.1 and 3.26.2 (Artful and Bionic) build log I see this: mutter-3.26.1 [..] Wayland: yes Native (KMS) backend: yes EGLDevice:yes Remote desktop: no To manage notifications about this bug go to: https://bugs.launchpad.net/baltix-default-settings/+bug/1730612/+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 1792085] Re: Regression: MTP not working/very slow
Had the same issue - fixed it today by installing the libmtp 1.1.17 packages from the ubuntu-focal repositories. Seems to work OK now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1792085 Title: Regression: MTP not working/very slow Status in libmtp: New Status in gvfs package in Ubuntu: Incomplete Bug description: Hi, unfortunately (for me) MTP android devices no more work on Ubuntu 18.04. I have used MTP on 16.04 without problems, but on 18.04 it does not work. When I connect my Android devices (Samsung A5 and Samsung J3) and I try to list directories with many files (e.g. /DCIM/Camera) the window hangs until I disconnect the device. Same issue if I try to post the command "ls /var/run/1000/gvfs/". I have installed Ubuntu 18.04 on two different machines - an older HP laptop and a recent DELL laptop - and the issue is present on the all of them. I suspect a defect on the "libmtp". I tried many alternative solutions suggested by the net (e.g. jmtpfs and so on) but anyone worked. That's all! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs-fuse 1.36.1-0ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 12 06:20:07 2018 LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libmtp/+bug/1792085/+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 1868927] Re: FFe: Sync shared-mime-info 1.15-1 (main) from Debian unstable (main)
I wasn't sure whether the updated build dependences require an FFe or not. But yes, the changes are mostly bug fixes and improvements. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1868927 Title: FFe: Sync shared-mime-info 1.15-1 (main) from Debian unstable (main) Status in shared-mime-info package in Ubuntu: New Bug description: Please sync shared-mime-info 1.15-1 (main) from Debian unstable (main) NEWS: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/blob/master/NEWS shared-mime-info 1.15 (2019-30-10) * Add Kindle 8 eBook format * Fix some HTML files being detected as XML shared-mime-info 1.14 (2019-20-09) * Add mime-type for QCOW images * Fix matching SVG files in some circumstances (again) shared-mime-info 1.13.1 (2019-11-09) * Fix matching SVG files in some circumstances shared-mime-info 1.13 (2019-11-09) * Add code of conduct document * Use itstool and gettext to generate translations * Add content-tree type for OSTree USB repositories * Add match for MPEG-4 v1 videos * Adjust a lot of user readable mime-type descriptions * Fix WOFF/WOFF2 mime-types * Prefer text/html to XHTML for *.html files * Better magic for text/html files * Fix SVG magic for files embedded in HTML * Add *.sgd as a glob for Mega Drive ROMs Specification: - Mention that sub-class-of can be aliases Tools: - Enable Large File Support in update-mime-database Test suite: - Make test suite failures fatal - Add test for duplicate mime-types - Fix WarpScript test - Generate the specification in the CI, to avoid it becoming syntactically invalid shared-mime-info 1.12 (2019-17-01) * Fix build from tarball shared-mime-info 1.11 (2019-17-01) * Add mime-type for reStructuredText * Add mime-type for Groovy scripting language * Add mime-type for Gradle build tool * Add mime-type for Maven * Add mime-type for WarpScript source code * Add mime-type for zstd and tar.zst archives * Change the preferred suffix for image/jpeg from .jpeg to .jpg * Assign *.html to XHTML pages * Better detection for *.key files (Apple Keynote vs. GPG keys) * Give weight to one of the appimage patterns Tools: - Link to GitLab for contributions and bug reports - Loads of memory and file descriptor leak fixes Spec: - Clarify the availability of C character escape support Explanation of FeatureFreeze exception: New mime-type's and improvements to the existing ones useful for the life of the new LTS. The current version 1.10 has not been updated since September 2018. Changelog entries since current focal version 1.10-1: shared-mime-info (1.15-1) unstable; urgency=medium * New upstream release. Closes: #954669. * Update watch file for gitlab.freedesktop.org. * Update build-dependencies. * Remove ancient patches changing the magic database. Those should be reported upstream if they're still present. * Switch to debhelper-compat and bump compat to 12. * Don't hardcode full command path in postinst. -- Emilio Pozuelo Monfort Tue, 24 Mar 2020 16:58:21 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1868927/+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 1865845] Re: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers
On 2020-03-26 17:13, Marco Trevisan (Treviño) wrote: > Gunnar, the strings in case will stay in fprind anyways, as we get > them through dbus. Ok, then I misunderstood that part. > However, sure I will notify for the new ones. Good. > Laney, I did sent the message to the documentation list, but my > message is under moderation, so I hope someone would moderate it. It got through - it's because of that message I'm here. :) -- 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/1865845 Title: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: In Progress Bug description: There is no progress information shows to user while enrolling fingerprint if the number of required enrollment steps is greater than 10. It might confuse user thinking it as freeze failure. Also it's not possible to enroll more than one finger. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. And this also introduce some critical issue of step 6 that user page in settings failed forever. However if the enrollment succeeds: 7. If trying to add a new fingerprint, the user is forced to delete its enrolled prints So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. 3. Allow to enroll more fingers As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 There will be few new strings, although most of the action events are already covered by the fprintd translations. UI will change quite a lot, but the current documentation [1] should not be affected by the change, being quite generic, but in case it might be updated to be clearer. [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+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 1706199] Re: Left-handed mouse: tap produces right click
Totally agree. Tapping the touchpad should continue to work normally even after switching the mouse to the left-handed mode. This is a VERY user-unfriendly behavior. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1706199 Title: Left-handed mouse: tap produces right click Status in Xserver Xorg Input Synaptics: Won't Fix Status in xserver-xorg-input-synaptics package in Ubuntu: Confirmed Bug description: First of all I’d like to say that documenting a bug doesn’t justify its existence. The issue I am reporting is documented in `man synaptics`: > If the device is switched to left-handed (an in-server mapping of physical buttons 1, 2, 3 to the logical buttons 3, 2, 1, respectively), both physical and TapButtons are affected. To counteract this, the TapButtons need to be set up in reverse order (TapButton1=3, TapButton2=1). Steps to reproduce: 0) "Tap to click" is activated (by default), your computer has a touchpad 1) Switch mouse and touchpad to the left-handed mode through Settings > Mouse and Touchpad 2) Logout and login for the changes to take effect 3) Tap the touchpad Expected result: a left click event is generated Actual result: right click event is generated, context menu is shown Steps to work around the problem (no sane person will consider this a real solution): 1) Find in `man synaptics` the lines quoted above 2) Find out the syntax of xinput to configure Tap Action (not in the `man xinput` since this particular case is not mentioned there, and not via xorg.conf which ceased to exist) 3) Run this command via an entry in .config/autostart (since putting it in .profile and .xinputrc doesn’t have any effect) These configuration steps MUST NOT (RFC 2119) exist. Tapping the touchpad should continue to work normally even after switching the mouse to the left-handed mode. For the next poor soul trying to figure out the command to run: 1) Run `xinput` and find your touchpad there, remember its ID 2) Run `xinput list-props | grep "Tap Action"`, remember property ID 3) Run `xinput set-prop --type=int --format=8 2 3 0 0 1 3 0` on login by adding it to "Startup applications" To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/1706199/+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 1865845] Re: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers
Gunnar, the strings in case will stay in fprind anyways, as we get them through dbus. However, sure I will notify for the new ones. Laney, I did sent the message to the documentation list, but my message is under moderation, so I hope someone would moderate it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1865845 Title: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: In Progress Bug description: There is no progress information shows to user while enrolling fingerprint if the number of required enrollment steps is greater than 10. It might confuse user thinking it as freeze failure. Also it's not possible to enroll more than one finger. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. And this also introduce some critical issue of step 6 that user page in settings failed forever. However if the enrollment succeeds: 7. If trying to add a new fingerprint, the user is forced to delete its enrolled prints So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. 3. Allow to enroll more fingers As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 There will be few new strings, although most of the action events are already covered by the fprintd translations. UI will change quite a lot, but the current documentation [1] should not be affected by the change, being quite generic, but in case it might be updated to be clearer. [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+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 1869225] [NEW] nm-applet should not attempt to create system-wide WiFi connections for regular users
Public bug reported: When a standard (non-administrator user) selects a WiFi network using the applet, the applet attempts to create a system connection, instead of a user connection, and thus it asks for an administrator user's password. On the other hand, if the same standard user opens the WiFi settings and selects a network there, no admin password is requested, as the connection is created for this user only, not system-wide. This is a workaround I discovered recently (see https://askubuntu.com/a/1163852/375543). This has bitten me several times, as I hand out laptops for new users; when they get home, they try to connect to their network and as I have no other way to help them (before I discovered the workaround), I ended up giving them the administrator password. The applet should not attempt to create a system-wide connection for users that are unable to do it. There is no security implication to implement this, as the users are able to create a connection anyway with the workaround mentioned above. But the improvement in terms of UX would be huge. ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-applet in Ubuntu. https://bugs.launchpad.net/bugs/1869225 Title: nm-applet should not attempt to create system-wide WiFi connections for regular users Status in network-manager-applet package in Ubuntu: New Bug description: When a standard (non-administrator user) selects a WiFi network using the applet, the applet attempts to create a system connection, instead of a user connection, and thus it asks for an administrator user's password. On the other hand, if the same standard user opens the WiFi settings and selects a network there, no admin password is requested, as the connection is created for this user only, not system-wide. This is a workaround I discovered recently (see https://askubuntu.com/a/1163852/375543). This has bitten me several times, as I hand out laptops for new users; when they get home, they try to connect to their network and as I have no other way to help them (before I discovered the workaround), I ended up giving them the administrator password. The applet should not attempt to create a system-wide connection for users that are unable to do it. There is no security implication to implement this, as the users are able to create a connection anyway with the workaround mentioned above. But the improvement in terms of UX would be huge. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1869225/+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 1868780] Re: [virtio] Xubuntu 20.04 - Blank screen after login
See attached: ** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1868780/+attachment/5341849/+files/prevboot.txt -- 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/1868780 Title: [virtio] Xubuntu 20.04 - Blank screen after login Status in xorg-server package in Ubuntu: Incomplete Bug description: Both on Xubuntu 20.04 23rd March and 24th March daily build. Using Martin Wimpress QuickEMU setup. Installation part of xubuntu is working fine. But after install and reboot, you get the login box. I type in the password for the user and then just get a black screen and mouse cursor, no other error boxes or gui. Have tested my QuickEMU setup on ubuntu-mate and do not see this issue, only on Xubuntu daily builds do I see this issue. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' Date: Tue Mar 24 16:40:12 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Red Hat, Inc. Virtio GPU [1af4:1050] (rev 01) (prog-if 00 [VGA controller]) Subsystem: Red Hat, Inc. Virtio GPU [1af4:1100] InstallationDate: Installed on 2020-03-24 (0 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200324) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 480M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 480M MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-18-generic root=UUID=4b1c21e9-1325-435b-9ade-04263b901e6d ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-4.2 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.12.0-59-gc9ba5276e321-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-4.2:cvnQEMU:ct1:cvrpc-q35-4.2: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-4.2 dmi.sys.vendor: QEMU version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-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+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/xorg-server/+bug/1868780/+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 1868409] Re: gnome-{calculator, logs, characters} snaps not removed after the equivalent APT packages are installed on 20.04, and gnome-software APT package not replaced by sna
** Also affects: gnome-calculator (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1868409
Title:
gnome-{calculator,logs,characters} snaps not removed after the
equivalent APT packages are installed on 20.04, and gnome-software APT
package not replaced by snap-store
Status in gnome-calculator package in Ubuntu:
New
Status in ubuntu-meta package in Ubuntu:
Confirmed
Bug description:
I'm trialing the development release of Ubuntu 20.04, installed in
December and kept up-to-date by regularly running apt full-upgrade.
I understand from [1] that 20.04 will ship
gnome-{calculator,logs,characters} as APT packages rather than snap
apps, and gnome-software as a snap app (called snap-store) rather than
an APT package.
Following an apt full-upgrade in late February, I now have:
* both the snap and the APT versions of gnome-{calculator,logs,characters}
* still only the APT version of gnome-software, no snap-store
Is this normal? A user in the #ubuntu+1 IRC channel reports that a
fresh install of the development release:
* only features the APT versions of gnome-{calculator,logs,characters}
* features the snap-store (but also the APT version of gnome-software)
Are users of older installs of the development release supposed to
manually uninstall the snap versions of
gnome-{calculator,logs,characters} and manually install the snap-
store?
[1] https://discourse.ubuntu.com/t/is-ubuntu-software-going-to-be-
remove-for-snap-snap-store/14542
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calculator/+bug/1868409/+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 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment
Thanks, that looks normal. I'm unsure to understand the description now though, 'Opening a pdf file from Zotero in evince' ... what is Zotero in that context? Is that where the file is stored/in a remote location? Can you add a 'journalctl -b 0' log to the bug after triggering the bug? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1869159 Title: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment Status in evince package in Ubuntu: Incomplete Bug description: Opening a pdf file from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment" and the file won't open. When opening the file from its location in Nautilus, that works properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 10:17:17 2020 InstallationDate: Installed on 2019-02-21 (398 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159/+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 1868927] Re: FFe: Sync shared-mime-info 1.15-1 (main) from Debian unstable (main)
You subscribed the release team so I'm going to let them comment but the changes look like mostly bugfixes, unsure there is a new feature/things required a ffe there? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to shared-mime-info in Ubuntu. https://bugs.launchpad.net/bugs/1868927 Title: FFe: Sync shared-mime-info 1.15-1 (main) from Debian unstable (main) Status in shared-mime-info package in Ubuntu: New Bug description: Please sync shared-mime-info 1.15-1 (main) from Debian unstable (main) NEWS: https://gitlab.freedesktop.org/xdg/shared-mime-info/-/blob/master/NEWS shared-mime-info 1.15 (2019-30-10) * Add Kindle 8 eBook format * Fix some HTML files being detected as XML shared-mime-info 1.14 (2019-20-09) * Add mime-type for QCOW images * Fix matching SVG files in some circumstances (again) shared-mime-info 1.13.1 (2019-11-09) * Fix matching SVG files in some circumstances shared-mime-info 1.13 (2019-11-09) * Add code of conduct document * Use itstool and gettext to generate translations * Add content-tree type for OSTree USB repositories * Add match for MPEG-4 v1 videos * Adjust a lot of user readable mime-type descriptions * Fix WOFF/WOFF2 mime-types * Prefer text/html to XHTML for *.html files * Better magic for text/html files * Fix SVG magic for files embedded in HTML * Add *.sgd as a glob for Mega Drive ROMs Specification: - Mention that sub-class-of can be aliases Tools: - Enable Large File Support in update-mime-database Test suite: - Make test suite failures fatal - Add test for duplicate mime-types - Fix WarpScript test - Generate the specification in the CI, to avoid it becoming syntactically invalid shared-mime-info 1.12 (2019-17-01) * Fix build from tarball shared-mime-info 1.11 (2019-17-01) * Add mime-type for reStructuredText * Add mime-type for Groovy scripting language * Add mime-type for Gradle build tool * Add mime-type for Maven * Add mime-type for WarpScript source code * Add mime-type for zstd and tar.zst archives * Change the preferred suffix for image/jpeg from .jpeg to .jpg * Assign *.html to XHTML pages * Better detection for *.key files (Apple Keynote vs. GPG keys) * Give weight to one of the appimage patterns Tools: - Link to GitLab for contributions and bug reports - Loads of memory and file descriptor leak fixes Spec: - Clarify the availability of C character escape support Explanation of FeatureFreeze exception: New mime-type's and improvements to the existing ones useful for the life of the new LTS. The current version 1.10 has not been updated since September 2018. Changelog entries since current focal version 1.10-1: shared-mime-info (1.15-1) unstable; urgency=medium * New upstream release. Closes: #954669. * Update watch file for gitlab.freedesktop.org. * Update build-dependencies. * Remove ancient patches changing the magic database. Those should be reported upstream if they're still present. * Switch to debhelper-compat and bump compat to 12. * Don't hardcode full command path in postinst. -- Emilio Pozuelo Monfort Tue, 24 Mar 2020 16:58:21 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1868927/+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 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment
@seb128 Please find these output: $ dpkg -l | grep evince ii evince 3.36.0-1 amd64Document (PostScript, PDF) viewer ii evince-common 3.36.0-1 all Document (PostScript, PDF) viewer - common files $ dpkg -l | grep nss ii libconfig-model-openssh-perl 2.8.0.1-1 all configuration editor for OpenSsh ii libcurl4-openssl-dev:amd64 7.68.0-1ubuntu1 amd64development files and documentation for libcurl (OpenSSL flavour) ii libevent-openssl-2.1-7:amd64 2.1.11-stable-1 amd64Asynchronous event notification library (openssl) ii libjansson4:amd64 2.12-1build1 amd64C library for encoding, decoding and manipulating JSON data ii libnss-mdns:amd64 0.14.1-1ubuntu1 amd64NSS module for Multicast DNS name resolution ii libnss-myhostname:amd64245.2-1ubuntu2 amd64nss module providing fallback resolution for the current hostname ii libnss-systemd:amd64 245.2-1ubuntu2 amd64nss module providing dynamic user and group name resolution ii libnss3:amd64 2:3.49.1-1ubuntu1 amd64Network Security Service libraries ii libxmlsec1-nss:amd64 1.2.28-2 amd64Nss engine for the XML security library ii openssh-client 1:8.1p1-5 amd64secure shell (SSH) client, for secure access to remote machines ii openssh-server 1:8.1p1-5 amd64secure shell (SSH) server, for secure access from remote machines ii openssh-sftp-server1:8.1p1-5 amd64secure shell (SSH) sftp server module, for SFTP access from remote machines ii openssl1.1.1d-2ubuntu6 amd64Secure Sockets Layer toolkit - cryptographic utility ii perl-openssl-defaults:amd644 amd64version compatibility baseline for Perl OpenSSL packages ii python-openssl 19.0.0-1build1 all Python 2 wrapper around the OpenSSL library And there's no libpdfdocument.sos but I suppose you meant libpdfdocument.so : $ ldd -v /usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.so linux-vdso.so.1 (0x7ffe9ca13000) libevdocument3.so.4 => /usr/lib/x86_64-linux-gnu/libevdocument3.so.4 (0x7fd470424000) libgtk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (0x7fd46fd18000) libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x7fd46fcc9000) libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fd46fca1000) libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7fd46fac1000) libpoppler-glib.so.8 => /usr/lib/x86_64-linux-gnu/libpoppler-glib.so.8 (0x7fd46fa61000) libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7fd46f9ff000) libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7fd46f8d6000) libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x7fd46f71c000) libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x7fd46f5f9000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x7fd46f407000) libsynctex.so.2 => /usr/lib/x86_64-linux-gnu/libsynctex.so.2 (0x7fd46f3e9000) libgdk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 (0x7fd46f2e2000) libgmodule-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x7fd46f2dc000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x7fd46f18d000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x7fd46f16a000) libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7fd46f158000) libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7fd46f01b000) libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7fd46f007000) libXfixes.so.3 => /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x7fd46ee01000) libcairo-gobject.so.2 => /usr/lib/x86_64-linux-gnu/libcairo-gobject.so.2 (0x7fd46edf5000) libatk-1.0.so.0 =>
[Desktop-packages] [Bug 1865845] Re: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers
The applicable doc page is an upstream one. I assume this will make it upstream sooner or later, and that the doc page will be modified if needed, even if the latter step will lag a bit. The proposed change is not important enough to create a temporary Ubuntu specific page. So from a docs POV this is fine. As regards translatable strings: Even if they exist in fprintd, the translations won't automatically move to the gnome-control-center-2.0 translation domain. Therefore, whether it's uploaded before the release or afterwards as an SRU, please notify the translators on the ubuntu- translators list as soon as the new g-c-c strings are available for translation in LP. -- 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/1865845 Title: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: In Progress Bug description: There is no progress information shows to user while enrolling fingerprint if the number of required enrollment steps is greater than 10. It might confuse user thinking it as freeze failure. Also it's not possible to enroll more than one finger. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. And this also introduce some critical issue of step 6 that user page in settings failed forever. However if the enrollment succeeds: 7. If trying to add a new fingerprint, the user is forced to delete its enrolled prints So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. 3. Allow to enroll more fingers As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 There will be few new strings, although most of the action events are already covered by the fprintd translations. UI will change quite a lot, but the current documentation [1] should not be affected by the change, being quite generic, but in case it might be updated to be clearer. [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+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 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
I just tried to reproduce this problem, but couldn't. Installed the ubuntu 20.04 daily built image on my Lenovo X1 Carbon 7th sudo apt dist-upgrade reboot and check the pulesaudio version, it is 1:13.99.1-1ubuntu1 Paring a bluetooth headset (Sony WL-1000X), it connected successfully check the gnome-sound-setting: the output device is Headset - WL-1000X the configuration is High Fidelity Playback (A2DP Sink) Click test Front left and Front right, the sound output to my BT headset choose speaker - Cannon point-LP High Definition...(internal speaker), click test front left and front right,the sound output to internal speaker. Disconnect the BT headset plug a usb audio bar (one headphone and one microphone) the output device is automatically changed to USB Speaker - Audio Adapter (Unitek Y-247A) click the test front left and front right, the sound output to usb headphone manually select internal speaker from gnome-control-center, click front left and front right, the sound output to internal speaker. So looks like everything worked as expected. Didn't reproduce the problem. Also added my testing result to pulseaudio/issues/832. -- 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/1866194 Title: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1868999] Re: Characters in the web browser do not work
@Olivier, This morning it happened again. I had to restart three times. -- 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/1868999 Title: Characters in the web browser do not work Status in firefox package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Invalid Bug description: I updated my ubuntu 20.04 (03-25-2020) and I can't write in Firefox or Chrome. In all other GNOME applications it works fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 74.0+build3-0ubuntu1 Uname: Linux 5.4.27-050427-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1725 F pulseaudio BuildID: 20200309095159 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 10:03:04 2020 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-12-02 (478 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.0.1 dev enx000ec6c82c3f proto dhcp metric 100 169.254.0.0/16 dev enx000ec6c82c3f scope link metric 1000 192.168.0.0/24 dev enx000ec6c82c3f proto kernel scope link src 192.168.0.101 metric 100 Locales: extensions.sqlite corrupt or missing PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:729 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=74.0/20200309095159 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to focal on 2018-12-02 (478 days ago) dmi.bios.date: 11/18/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.35 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.35:bd11/18/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1868999/+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 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
This bug was fixed in the package libmtp - 1.1.17-2ubuntu1 --- libmtp (1.1.17-2ubuntu1) focal; urgency=medium * In 69-libmtp.rules skip all printers, including some weird ones from HP as some test positive on mtp-probe (LP: #1863239). -- Till Kamppeter Sat, 21 Mar 2020 19:05:58 +0100 ** Changed in: libmtp (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: Fix Released Status in libmtp package in Debian: Unknown Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+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 1869022] Re: unity-settings-daemon shipping org.gnome schema
This bug was fixed in the package unity-settings-daemon - 15.04.1+20.04.20200325-0ubuntu1 --- unity-settings-daemon (15.04.1+20.04.20200325-0ubuntu1) focal; urgency=medium [ iain.l...@canonical.com ] * Stop shipping a GNOME schema (LP: #1869022) -- i...@orangesquash.org.uk (i...@orangesquash.org.uk) Wed, 25 Mar 2020 17:16:20 + ** Changed in: unity-settings-daemon (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1869022 Title: unity-settings-daemon shipping org.gnome schema Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: In com.canonical.unity-settings-daemon.peripherals.wacom we have: ["", "", ""] which is squatting on gnome's namespace, and makes g-s-d's own schema get ignored. I think probably a c+p error so I'll just fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1869022/+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 1868260] Re: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement
** Changed in: oem-priority Status: New => Won't Fix -- 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/1868260 Title: Change sleep-inactive-ac-timeout to 1200 to meet eStar 8 requirement Status in OEM Priority Project: Won't Fix Status in gnome-settings-daemon package in Ubuntu: Won't Fix Bug description: Based on Energy Star Computers Specification Version 8.0[1] Table 3: Power Management Requirements (page 10) The energy star spec requests - The machine shall enter Sleep/Alternative Low Power Mode after no more than 30 minutes of user inactivity. (suspend) - The machine shall enter Display Sleep Mode shall be set to activate after no more than 15 minutes of user inactivity. The default settings in focal are - The machine will enter Sleep/Alternative Low Power Mode in 20 minutes with battery[2] - The machine is always on with the AC[2] - Enter Display Sleep Mode in 5 minutes[3] OEM device team suggested to change org.gnome.settings- daemon.plugins.power sleep-inactive-ac-timeout to 1200 (20 minutes) as default to meet the Power Management Requirements of Energy Star Computers Specification Version 8.0. [1] Computers Specification Version 8.0 | | ENERGY STAR - https://www.energystar.gov/products/spec/computers_version_8_0_pd [2] % gsettings list-recursively org.gnome.settings-daemon.plugins.power|grep sleep- org.gnome.settings-daemon.plugins.power sleep-inactive-ac-timeout 0 org.gnome.settings-daemon.plugins.power sleep-inactive-ac-type 'suspend' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-type 'suspend' org.gnome.settings-daemon.plugins.power sleep-inactive-battery-timeout 1200 [3] % gsettings list-recursively org.gnome.desktop.session org.gnome.desktop.session session-name 'ubuntu' org.gnome.desktop.session idle-delay uint32 300 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1868260/+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 1868116] Re: QEMU monitor no longer works
Thank you for investigating this. I would bisect QEMU, but wouldn't investigate its libraries. Consequently, I would never find the cause of this problem. For now, I am using -monitor telnet:127.0.0.1:5,server,nowait to have access to the monitor on QEMU guests. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works Status in QEMU: New Status in qemu package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: New Bug description: Repro: VTE $ meson _build && ninja -C _build && ninja -C _build install qemu: $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user --disable-linux-user --disable-docs --disable-guest-agent --disable-sdl --enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt --disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi --disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir --disable-seccomp --disable-glusterfs --disable-tpm --disable-numa --disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs --disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma --disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock --disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user --disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs --disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat --disable-qed --disable-parallels --disable-sheepdog --disable-avx2 --disable-nettle --disable-gnutls --disable-capstone --disable-tools --disable-libpmem --disable-iconv --disable-cap-ng $ make Test: $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH ./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso - switch to monitor with CTRL+ALT+2 - try to enter something Affects head of both usptream git repos. --- original bug --- It was observed that the QEMU console (normally accessible using Ctrl+Alt+2) accepts no input, so it can't be used. This is being problematic because there are cases where it's required to send commands to the guest, or key combinations that the host would grab (as Ctrl-Alt-F1 or Alt-F4). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu 1:4.2-3ubuntu2 Uname: Linux 5.6.0-rc6+ x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 12:16:31 2020 Dependencies: InstallationDate: Installed on 2017-06-13 (1009 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND qemu-system-x86 Sl+ 1000 1000 34275 25235 29.2 qemu-system-x86_64 -m 4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel kvm -device nec-usb-xhci -serial vc -serial stdio -hda /home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio kvm-nx-lpage-re S0 0 34284 2 0.0 [kvm-nx-lpage-re] kvm-pit/34275 S0 0 34286 2 0.0 [kvm-pit/34275] MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 zswap.enabled=1 zswap.zpool=z3fold resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: qemu UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1868116/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1865845] Re: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers
I'd like to hear from the documentation team now if this has any UIF implications (please mail their list), but I think from the release team POV it's a bit premature to be considering this - the unknown nature of the change (code size) and it not being ready yet means we can't really assess the change based on the current information. I'd say: once this is ready to go, please come back to us again and we can see where we are in the release cycle vs. the risk. It might for example be that this should be SRUed to have additional and explicit verification. -- 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/1865845 Title: [UIFe] No UI indication for fingerprint enrolling progress, no way to enroll multiple fingers Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: In Progress Status in gnome-control-center source package in Focal: In Progress Bug description: There is no progress information shows to user while enrolling fingerprint if the number of required enrollment steps is greater than 10. It might confuse user thinking it as freeze failure. Also it's not possible to enroll more than one finger. steps: 1. enroll fingerprint in gnome-control-center 2. click 'Next' on the enrolling page 3. There is no message tell user that it need at least 12 times touching fingerprint. 4. user press fingerprint for 5 times, there is no way to cancel enrolling. 5. user wait for timeout and get error message for timeout notification. 6. after 5. user page of setting will always failed and show no user found. And this also introduce some critical issue of step 6 that user page in settings failed forever. However if the enrollment succeeds: 7. If trying to add a new fingerprint, the user is forced to delete its enrolled prints So, the suggestion would be: 1. remind user to press 12 times on fingerprint for step 3. 2. show the progress during user pressing fingerprint for step 4. 3. Allow to enroll more fingers As per this, GNOME design has produced some artwork that we want to implement to fix all these issues: - https://gitlab.gnome.org/Teams/Design/settings-mockups/-/issues/18 There will be few new strings, although most of the action events are already covered by the fprintd translations. UI will change quite a lot, but the current documentation [1] should not be affected by the change, being quite generic, but in case it might be updated to be clearer. [1] https://help.ubuntu.com/19.10/ubuntu-help/session-fingerprint.html ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.35.91-0ubuntu2 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 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 3 16:44:13 2020 InstallationDate: Installed on 2020-03-02 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200301)SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1865845/+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 508522] Re: Add automatic switching to HSP/HFP from A2DP when a mic is needed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed -- 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/508522 Title: Add automatic switching to HSP/HFP from A2DP when a mic is needed Status in PulseAudio: New Status in chromium-browser package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Binary package hint: pulseaudio I'm testing a Nokia BH-905i headset (see http://www.wissel.net/blog/d6plinks/SHWL-8AZGGF ) on Ubuntu 10.10. The Bluetooth module correctly identifies the headset and the both audio profiles "HSP/ HFP Telephony duplex" and "A2DP High Fidelity Playback". For music playback only A2DP is suitable (HSP/HFP sounds like listening to music played through an old telephone). A2DP does not have an INPUT mode, so use of the headset for VoiP isn't possible. What would be needed is a separate selection to allow to select A2DP for output and HSP/HFP for input. Smartphones (a lot of them *nix based) phones do that (or they switch on the fly?). Formal structure: 1) Ubuntu 10.10 2) Pulse-Audio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu21.1 consisting og pluseaudio, pulseaudio-esound-compat, pulseaudio-module-bluetooth, pulseaudio-module-gconf, pulseaudio-module-x11, pulseaudio-utils 3) Select high quality audio output and still use the Bluetooth microphone 4) Had to choose: either high quality audio or "telephone quality" with microphone I can change the profile without the Bluetooth connection dropping, but that's ridiculous. E.g. listening to music, a call comes in. Then I would need to switch the profile before answering. Please note that in Windows, Mac OS, iOS, Android, and Windows Mobile it's done automatically. Check out attached screencast. ProblemType: Bug AplayDevices: List of PLAYBACK Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: oivasyuv 2309 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xd850 irq 17' Mixer name : 'Analog Devices AD1984A' Components : 'HDA:11d4194a,103c30e8,00100400' Controls : 22 Simple ctrls : 14 Date: Sat Jan 16 22:31:41 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) Package: pulseaudio 1:0.9.19-0ubuntu4 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-17.54-generic-pae SourcePackage: pulseaudio Uname: Linux 2.6.31-17-generic-pae i686 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/508522/+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 1857183] Re: No systemtrayicon available
fabrizio@fabrizio-1TB:~$ journalctl -b 0 | tail -100 mar 26 12:34:57 fabrizio-1TB gnome-shell[28379]: Failed to load file:///usr/share/gnome-shell/extensions/ubuntu-close-window.svg: Errore nell'aprire il file /usr/share/gnome-shell/extensions/ubuntu-close-window.svg: File o directory non esistente mar 26 12:34:57 fabrizio-1TB gnome-shell[28379]: Failed to load file:///usr/share/gnome-shell/extensions/ubuntu-close-window.svg: Errore nell'aprire il file /usr/share/gnome-shell/extensions/ubuntu-close-window.svg: File o directory non esistente mar 26 12:34:57 fabrizio-1TB gnome-shell[28379]: Failed to load file:///usr/share/gnome-shell/extensions/ubuntu-close-window.svg: Errore nell'aprire il file /usr/share/gnome-shell/extensions/ubuntu-close-window.svg: File o directory non esistente mar 26 12:34:57 fabrizio-1TB gnome-shell[28379]: Failed to load file:///usr/share/gnome-shell/extensions/ubuntu-close-window.svg: Errore nell'aprire il file /usr/share/gnome-shell/extensions/ubuntu-close-window.svg: File o directory non esistente mar 26 12:34:57 fabrizio-1TB gnome-shell[28379]: Failed to load file:///usr/share/gnome-shell/extensions/ubuntu-close-window.svg: Errore nell'aprire il file /usr/share/gnome-shell/extensions/ubuntu-close-window.svg: File o directory non esistente mar 26 12:34:58 fabrizio-1TB gnome-shell[28379]: Failed to load file:///usr/share/gnome-shell/extensions/ubuntu-close-window.svg: Errore nell'aprire il file /usr/share/gnome-shell/extensions/ubuntu-close-window.svg: File o directory non esistente mar 26 12:34:58 fabrizio-1TB gnome-shell[28379]: Failed to load file:///usr/share/gnome-shell/extensions/ubuntu-close-window.svg: Errore nell'aprire il file /usr/share/gnome-shell/extensions/ubuntu-close-window.svg: File o directory non esistente mar 26 12:34:58 fabrizio-1TB gnome-shell[28379]: g_file_get_parent: assertion 'G_IS_FILE (file)' failed mar 26 12:34:58 fabrizio-1TB gnome-shell[28379]: g_file_resolve_relative_path: assertion 'G_IS_FILE (file)' failed mar 26 12:34:58 fabrizio-1TB gnome-shell[28379]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed mar 26 12:34:58 fabrizio-1TB gnome-shell[28379]: g_file_get_parent: assertion 'G_IS_FILE (file)' failed mar 26 12:34:58 fabrizio-1TB gnome-shell[28379]: g_file_resolve_relative_path: assertion 'G_IS_FILE (file)' failed mar 26 12:34:58 fabrizio-1TB gnome-shell[28379]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed mar 26 12:35:22 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:22 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:22 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:22 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:26 fabrizio-1TB nautilus[5926]: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed mar 26 12:35:26 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:26 fabrizio-1TB nautilus[5926]: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed mar 26 12:35:26 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:26 fabrizio-1TB nautilus[5926]: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed mar 26 12:35:26 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:26 fabrizio-1TB nautilus[5926]: gtk_label_set_markup: assertion 'GTK_IS_LABEL (label)' failed mar 26 12:35:26 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:30 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:30 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:30 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:30 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:30 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:30 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:30 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:30 fabrizio-1TB nautilus[5926]: gtk_revealer_set_reveal_child: assertion 'GTK_IS_REVEALER (revealer)' failed mar 26 12:35:45 fabrizio-1TB dbus-daemon[1000]: [system] Activating via systemd: service name='org.freedesktop.hostname1'
[Desktop-packages] [Bug 1857183] Re: No systemtrayicon available
fabrizio@fabrizio-1TB:~$ env | grep DESKTOP_SESSION= DESKTOP_SESSION=ubuntu fabrizio@fabrizio-1TB:~$ ps -A | egrep -i "gnome|kde|mate|cinnamon" 57 ?00:00:00 kdevtmpfs 5319 tty2 01:13:01 gnome-shell 5478 ?00:00:01 gnome-keyring-d 5536 tty2 00:00:00 gnome-session-b 5703 ?00:00:00 gnome-shell-cal 6994 tty2 00:00:56 gnome-software 12716 ?00:00:28 gnome-terminal- -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1857183 Title: No systemtrayicon available Status in hplip package in Ubuntu: Confirmed Bug description: HP Linux Imaging and Printing System (ver. 3.19.12) System Tray Status Service ver. 2.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) No systemtrayicon available fabrizio@fabrizio-1TB:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 fabrizio@fabrizio-1TB:~$ apt-cache policy hplip hplip: Installato: 3.17.10+repack0-5 Candidato: 3.17.10+repack0-5 Tabella versione: *** 3.17.10+repack0-5 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1857183/+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 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
How to inform upstream (where) ? -- 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/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
ok. please notice that https://launchpad.net/~oibaf/+archive/ubuntu /graphics-drivers is working fine -- 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/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
sure, it's there https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #398 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 ** Description changed: + Also created bug on upstream : + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 + + This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: - # This is the distribution channel descriptor for the OEM CDs - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 + # This is the distribution channel descriptor for the OEM CDs + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: - default via 192.168.101.1 dev eno1 proto static metric 100 - 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 - 169.254.0.0/16 dev eno1 scope link metric 1000 - 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 + default via 192.168.101.1 dev eno1 proto static metric 100 + 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 + 169.254.0.0/16 dev eno1 scope link metric 1000 + 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: - Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device - - X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory + Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device + + X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: - NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME - netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection + NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME + netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.22.10 connected starting full enabled disabled disabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.22.10 connected starting full enabled disabled disabled enabled enabled -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu.
[Desktop-packages] [Bug 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
let upstream know that the fix is needed in 20.0.x.. that way focal will get it (and bionic too, when mesa is backported for 18.04.5) -- 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/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1857539] Re: nautilus crashed with SIGSEGV
looks similar to bug #1726129 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: Incomplete Bug description: after turn on pc ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 01:52:06 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-12-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax PC (0x7f3fb437f962) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+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 1857183] Re: No systemtrayicon available
Thank you for your bug report. What desktop environment and session do you use? Could you add your 'journalctl -b 0' log after triggering the issue? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1857183 Title: No systemtrayicon available Status in hplip package in Ubuntu: Confirmed Bug description: HP Linux Imaging and Printing System (ver. 3.19.12) System Tray Status Service ver. 2.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) No systemtrayicon available fabrizio@fabrizio-1TB:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 fabrizio@fabrizio-1TB:~$ apt-cache policy hplip hplip: Installato: 3.17.10+repack0-5 Candidato: 3.17.10+repack0-5 Tabella versione: *** 3.17.10+repack0-5 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1857183/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
@Alex, could you upstream it to https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/ -- 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/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: New Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Bug description: This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+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 1863506] Re: mate-session[1159]: WARNING: Could not parse desktop file /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop: Unrecognized desktop file Version '1.1'
** Changed in: deja-dup (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1863506 Title: mate-session[1159]: WARNING: Could not parse desktop file /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop: Unrecognized desktop file Version '1.1' Status in Déjà Dup: Fix Committed Status in deja-dup package in Ubuntu: Invalid Status in mate-session-manager package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Install Ubuntu MATE 20.04 LTS 2. Remove `~/.xsession-errors` and then login 3. Open `~/.xsession-errors` Expected results: * `~/.xsession-errors` do not have warnings Actual results: * `~/.xsession-errors` have warnings: mate-session[1159]: WARNING: Could not parse desktop file /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop: Unrecognized desktop file Version '1.1' mate-session[1159]: WARNING: could not read /etc/xdg/autostart/org.gnome.DejaDup.Monitor.desktop ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: deja-dup 40.5-1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: MATE Date: Sun Feb 16 21:49:08 2020 InstallationDate: Installed on 2020-02-16 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200216) SourcePackage: deja-dup UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1863506/+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 1869159] Re: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment
Thank you for your bug report, what's the output of those commands $ dpkg -l | grep evince $ dpkg -l | grep nss $ ldd -v /usr/lib/x86_64-linux-gnu/evince/4/backends/libpdfdocument.sos ** Changed in: evince (Ubuntu) Importance: Undecided => Low ** Changed in: evince (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1869159 Title: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment Status in evince package in Ubuntu: Incomplete Bug description: Opening a pdf file from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment" and the file won't open. When opening the file from its location in Nautilus, that works properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 10:17:17 2020 InstallationDate: Installed on 2019-02-21 (398 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159/+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 1868391] Re: /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.peripherals.wacom.gschema.xml:93:1 Error on line 93 char 1:
This should be fixed with https://launchpad.net/ubuntu/+source/unity-settings- daemon/15.04.1+20.04.20200325-0ubuntu1 k_alam has a better solution which we should replace this with though: https://code.launchpad.net/~khurshid-alam/unity-settings- daemon/lp-1868391 ** Changed in: gnome-settings-daemon (Ubuntu) Status: Incomplete => Fix Released -- 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/1868391 Title: /usr/share/glib-2.0/schemas/org.gnome.settings- daemon.peripherals.wacom.gschema.xml:93:1 Error on line 93 char 1: already specified. This entire file has been ignored. Warning: undefined reference to Status in gnome-settings-daemon package in Ubuntu: Fix Released Bug description: Steps to reproduce: 1. Install some package which depends on `gnome-settings-daemon-common` (for example `indicator-session`) with `apt-get` 2. See the output of `apt-get` Expected results: * all packages installed without warnings or errors Actual results: * have warnings or errors during installation ``` ... Processing triggers for libglib2.0-0:amd64 (2.64.1-1) ... /usr/share/glib-2.0/schemas/org.gnome.settings-daemon.peripherals.wacom.gschema.xml:93:1 Error on line 93 char 1: already specified. This entire file has been ignored. Warning: undefined reference to ... ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon-common 3.35.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: MATE Date: Sat Mar 21 18:30:59 2020 InstallationDate: Installed on 2020-03-21 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200321) PackageArchitecture: all SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1868391/+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 1869102] Re: Minor translation fix needed for en_US
Thanks for your report! Not a translation issue; it's the original string which is poorly worded. Submitted an upstream merge request: https://gitlab.com/Remmina/Remmina/-/merge_requests/2024 ** No longer affects: ubuntu-translations ** Summary changed: - Minor translation fix needed for en_US + Minor typo in translatable string in src/remmina_ssh.c ** Changed in: remmina (Ubuntu) Importance: Undecided => Low ** Changed in: remmina (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1869102 Title: Minor typo in translatable string in src/remmina_ssh.c Status in remmina package in Ubuntu: Triaged Bug description: Entry 210 (https://translations.launchpad.net/ubuntu/focal/+source/remmina/+pots/remmina/en_GB/210/+translate) currently reads: "SSH passphrase is empty, it should not." instead of "SSH passphrase is empty, it should not be." Located in ../src/remmina_ssh.c:255 cheers, Ant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1869102/+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 1867188] Re: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264
I've just try Focal fossa with new 20.0.2-1ubuntu1 Same problem, half screen picture for VAAPI - bob -- 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/1867188 Title: Mesa 19.2.8 and VAAPI - bob -> only half screen picture for 1080i H.264 Status in mesa package in Ubuntu: New Bug description: uname -a Linux adiance 4.15.0-88-generic #88-Ubuntu SMP Tue Feb 11 20:11:34 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 18.04.4 LTS Release: 18.04 Codename: bionic inxi -G Graphics: Card: Advanced Micro Devices [AMD/ATI] Oland [Radeon HD 8570 / R7 240/340 OEM] Display Server: x11 (X.Org 1.19.6 ) driver: radeon Resolution: 1920x1080@60.00hz OpenGL: renderer: AMD OLAND (DRM 2.50.0, 4.15.0-88-generic, LLVM 9.0.0) version: 4.5 Mesa 19.2.8 For 1080i H.264 and VAAPI - bob deinterlacing, i have halfscreen (top) compressed image. To solve the default, i have to revert via synaptic the package mesa- va-driver to 19.0.8. Other solution is to take nighty builds as complete mesa package via : https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers that works too and is at mesa 20.1 git Please correct the problem to the official Ubuntu repos. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1867188/+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 1868383] Re: File labels in Nautilus are not properly themed
** Changed in: yaru-theme (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1868383 Title: File labels in Nautilus are not properly themed Status in Yaru Theme: Unknown Status in yaru-theme package in Ubuntu: Fix Released Bug description: Steps to see the bug 1. Open Nautilus and change zoom to default 100% 2. Go to the app settings 3. Select any three labels to show under file icons The labels should be light grey, not black like the file name. See the attached screenshots. Yaru https://user-images.githubusercontent.com/45657128/77167618-a8fd8300-6ab6-11ea-819d-6737c8126493.png Adwaita https://user-images.githubusercontent.com/45657128/77167630-b0249100-6ab6-11ea-899f-2d7df22f8656.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: yaru-theme-gtk 20.04.2 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 21 15:05:30 2020 InstallationDate: Installed on 2020-01-21 (59 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1868383/+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 1869159] [NEW] Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment
Public bug reported: Opening a pdf file from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment" and the file won't open. When opening the file from its location in Nautilus, that works properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 10:17:17 2020 InstallationDate: Installed on 2019-02-21 (398 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug focal ** Attachment added: "screenshot" https://bugs.launchpad.net/bugs/1869159/+attachment/5341792/+files/Capture%20d%E2%80%99%C3%A9cran%20de%202020-03-26%2010-16-46.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1869159 Title: Opening a pdf from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment Status in evince package in Ubuntu: New Bug description: Opening a pdf file from Zotero in evince, I got "failed to load backend for 'application/pdf': libnss3.so: failed to load shared object mapping segment" and the file won't open. When opening the file from its location in Nautilus, that works properly. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 10:17:17 2020 InstallationDate: Installed on 2019-02-21 (398 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1869159/+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
Re: [Desktop-packages] [Bug 1866228] Re: Gnome shell extensions are badly broken
Agreed on the close, the main issue, the disorganisation of the packages to the level of unusability is fixed. A separate report for the missing dependency was filed. I hereby exhort the extension developers to step up their game with the upgrades, but they are not listening and I cant ask anyone to do a favor that's all we can do with this bug :) Regards, tg On Thu, 26 Mar 2020 at 02:31, Daniel van Vugt wrote: > > Thanks for the reply. This sounds somewhat inconclusive, though it does > sound like things are not "badly" broken now. > > I suggest we close this bug and then any additional issues found going > forward should get their own separate new bugs, by running: > > ubuntu-bug gnome-shell > > > ** Changed in: gnome-shell (Ubuntu) >Status: Incomplete => Invalid > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1866228 > > Title: > Gnome shell extensions are badly broken > > Status in gnome-shell package in Ubuntu: > Invalid > > Bug description: > Hi, > > After an upgrade this morning, the following things are not working: > - Earlier the Application key brought up something called "Activities", > which happens now via ApplicationA or SuperA, the microsoft key > - I can not find and search for extensions in the "Software" application. > There are just a few addons/extensions, gstreamer ones, fonts and some input > - any attempt at removing an installed extension results in a "you have no > permission" error, without asking for a password. Apparently gnome-shell is > crashing in the background, i'll attach logs if the tool does not. > - The Tweak app shows a warning triangle next to the "Dash to panel" > extension, by clicking on it the "Extension" thing starts up which shows > nothing. > - If I install the dash-to-panel extension from a package the top bar does > not appears properly, the icons, workplace switcher etc all crumpled into the > top left corne,r overlapping each other, thus being mostly unusable. > > I think that the extensions are not yet upgraded to gnome-shell 3.35, > but I have no way to check it. I also have no trivial way to downgrade > gnome shell to 3.34. > > Please advise. > > Thanks, > > tg > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: gnome-shell 3.35.91-1ubuntu2 > ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 > Uname: Linux 5.4.0-14-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu18 > Architecture: amd64 > CurrentDesktop: ubuntu:GNOME > Date: Thu Mar 5 19:59:26 2020 > DisplayManager: gdm3 > InstallationDate: Installed on 2020-01-19 (46 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > RelatedPackageVersions: mutter-common 3.35.91-1ubuntu1 > SourcePackage: gnome-shell > UpgradeStatus: Upgraded to focal on 2020-02-26 (7 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866228/+subscriptions -- we do what we must because we can -- 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/1866228 Title: Gnome shell extensions are badly broken Status in gnome-shell package in Ubuntu: Invalid Bug description: Hi, After an upgrade this morning, the following things are not working: - Earlier the Application key brought up something called "Activities", which happens now via ApplicationA or SuperA, the microsoft key - I can not find and search for extensions in the "Software" application. There are just a few addons/extensions, gstreamer ones, fonts and some input - any attempt at removing an installed extension results in a "you have no permission" error, without asking for a password. Apparently gnome-shell is crashing in the background, i'll attach logs if the tool does not. - The Tweak app shows a warning triangle next to the "Dash to panel" extension, by clicking on it the "Extension" thing starts up which shows nothing. - If I install the dash-to-panel extension from a package the top bar does not appears properly, the icons, workplace switcher etc all crumpled into the top left corne,r overlapping each other, thus being mostly unusable. I think that the extensions are not yet upgraded to gnome-shell 3.35, but I have no way to check it. I also have no trivial way to downgrade gnome shell to 3.34. Please advise. Thanks, tg ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.35.91-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 19:59:26
[Desktop-packages] [Bug 1857539] Re: nautilus crashed with SIGSEGV
@alexmurray: same pattern for me. It probably happened at shutdown according to timestamp, and Apport popped up just after login with Nautilus crash. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1857539 Title: nautilus crashed with SIGSEGV Status in nautilus package in Ubuntu: Incomplete Bug description: after turn on pc ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 01:52:06 2019 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2019-12-22 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191221) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f3fb437f962:mov0x380(%rax),%rax PC (0x7f3fb437f962) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1857539/+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 1869156] Re: nautilus crashed with SIGSEGV at session startup
*** This bug is a duplicate of bug 1857539 *** https://bugs.launchpad.net/bugs/1857539 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1857539, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1869156/+attachment/5341775/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1869156/+attachment/5341777/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1869156/+attachment/5341780/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1869156/+attachment/5341781/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1869156/+attachment/5341782/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1869156/+attachment/5341783/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1869156/+attachment/5341784/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1857539 nautilus crashed with SIGSEGV ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1869156 Title: nautilus crashed with SIGSEGV at session startup Status in nautilus package in Ubuntu: New Bug description: Using latest Ubuntu Focal, I got this Nautilus crash at session startup. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Mar 25 18:32:02 2020 ExecutablePath: /usr/bin/nautilus ExecutableTimestamp: 1583836867 GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'201' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2019-02-21 (398 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) ProcCmdline: /usr/bin/nautilus --gapplication-service ProcCwd: /home/nicolas ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, user) LANG=fr_FR.UTF-8 SegvAnalysis: Segfault happened at: 0x7f9d92ab0ae2:mov0x380(%rax),%rax PC (0x7f9d92ab0ae2) ok source "0x380(%rax)" (0x0380) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with SIGSEGV UpgradeStatus: Upgraded to focal on 2020-03-20 (5 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo separator: usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1869156/+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 1869102] Re: Minor translation fix needed for en_US
** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to remmina in Ubuntu. https://bugs.launchpad.net/bugs/1869102 Title: Minor translation fix needed for en_US Status in Ubuntu Translations: New Status in remmina package in Ubuntu: New Bug description: Entry 210 (https://translations.launchpad.net/ubuntu/focal/+source/remmina/+pots/remmina/en_GB/210/+translate) currently reads: "SSH passphrase is empty, it should not." instead of "SSH passphrase is empty, it should not be." Located in ../src/remmina_ssh.c:255 cheers, Ant To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1869102/+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 1857183] Re: No systemtrayicon available
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: hplip (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1857183 Title: No systemtrayicon available Status in hplip package in Ubuntu: Confirmed Bug description: HP Linux Imaging and Printing System (ver. 3.19.12) System Tray Status Service ver. 2.0 Copyright (c) 2001-18 HP Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. /usr/lib/python2.7/dist-packages/gtk-2.0/gtk/__init__.py:127: RuntimeWarning: PyOS_InputHook is not available for interactive use of PyGTK set_interactive(1) No systemtrayicon available fabrizio@fabrizio-1TB:~$ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 fabrizio@fabrizio-1TB:~$ apt-cache policy hplip hplip: Installato: 3.17.10+repack0-5 Candidato: 3.17.10+repack0-5 Tabella versione: *** 3.17.10+repack0-5 500 500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1857183/+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 1869141] [NEW] [UIFe] Icon View Captions labels in Nautilus are hard to read when selected
Public bug reported: First reported here: https://github.com/ubuntu/yaru/issues/2110 The "Icon View Captions" label in Nautilus is hard to read when the file is selected. Steps to Reproduce the Problem - open Preferences > View Tab - in the "Icon View Captions" section select at least one "information to be displayed beneath file and folders name" - Go back to Nautilus main window and select Icon View. Below the file name is expected to be a new label with color gray - Select the icon. The caption label keeps the gray color, which is hard to read on an orange background Yaru version - Version 20.04.4 in current Focal daily The fix has a low impact, since it only applies to Yaru's stylesheet part dedicated to Nautilus, and specifically to this caption labels. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Assignee: Carlo Lobrano (c-lobrano) Status: New ** Attachment added: "picture of the caption label when selected" https://bugs.launchpad.net/bugs/1869141/+attachment/5341770/+files/nautilus-caption-before.png ** Changed in: yaru-theme (Ubuntu) Assignee: (unassigned) => Carlo Lobrano (c-lobrano) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1869141 Title: [UIFe] Icon View Captions labels in Nautilus are hard to read when selected Status in yaru-theme package in Ubuntu: New Bug description: First reported here: https://github.com/ubuntu/yaru/issues/2110 The "Icon View Captions" label in Nautilus is hard to read when the file is selected. Steps to Reproduce the Problem - open Preferences > View Tab - in the "Icon View Captions" section select at least one "information to be displayed beneath file and folders name" - Go back to Nautilus main window and select Icon View. Below the file name is expected to be a new label with color gray - Select the icon. The caption label keeps the gray color, which is hard to read on an orange background Yaru version - Version 20.04.4 in current Focal daily The fix has a low impact, since it only applies to Yaru's stylesheet part dedicated to Nautilus, and specifically to this caption labels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1869141/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
** Attachment added: "dmesg.log" https://bugs.launchpad.net/oem-priority/+bug/1868915/+attachment/5341768/+files/dmesg.log -- 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/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: New Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Bug description: This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+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 1868116] Re: QEMU monitor no longer works
I'm not sure how many of you are tracking the Vte bug [1] so here a summary of the latest insight from there. - Short term it seems that new behavior will be reverted in Vte 0.60.1. - Long term the Vte devs might want to deprecate no-pty use cases or at least better understand why apps use it that way. For more details please read [1]. [1]: https://gitlab.gnome.org/GNOME/vte/issues/222 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vte2.91 in Ubuntu. https://bugs.launchpad.net/bugs/1868116 Title: QEMU monitor no longer works Status in QEMU: New Status in qemu package in Ubuntu: Triaged Status in vte2.91 package in Ubuntu: New Bug description: Repro: VTE $ meson _build && ninja -C _build && ninja -C _build install qemu: $ ../configure --python=/usr/bin/python3 --disable-werror --disable-user --disable-linux-user --disable-docs --disable-guest-agent --disable-sdl --enable-gtk --disable-vnc --disable-xen --disable-brlapi --disable-fdt --disable-hax --disable-vde --disable-netmap --disable-rbd --disable-libiscsi --disable-libnfs --disable-smartcard --disable-libusb --disable-usb-redir --disable-seccomp --disable-glusterfs --disable-tpm --disable-numa --disable-opengl --disable-virglrenderer --disable-xfsctl --disable-vxhs --disable-slirp --disable-blobs --target-list=x86_64-softmmu --disable-rdma --disable-pvrdma --disable-attr --disable-vhost-net --disable-vhost-vsock --disable-vhost-scsi --disable-vhost-crypto --disable-vhost-user --disable-spice --disable-qom-cast-debug --disable-vxhs --disable-bochs --disable-cloop --disable-dmg --disable-qcow1 --disable-vdi --disable-vvfat --disable-qed --disable-parallels --disable-sheepdog --disable-avx2 --disable-nettle --disable-gnutls --disable-capstone --disable-tools --disable-libpmem --disable-iconv --disable-cap-ng $ make Test: $ LD_LIBRARY_PATH=/usr/local/lib/x86_64-linux-gnu/:$LD_LIBRARY_PATH ./build/x86_64-softmmu/qemu-system-x86_64 -enable-kvm --drive media=cdrom,file=http://archive.ubuntu.com/ubuntu/dists/bionic/main/installer-amd64/current/images/netboot/mini.iso - switch to monitor with CTRL+ALT+2 - try to enter something Affects head of both usptream git repos. --- original bug --- It was observed that the QEMU console (normally accessible using Ctrl+Alt+2) accepts no input, so it can't be used. This is being problematic because there are cases where it's required to send commands to the guest, or key combinations that the host would grab (as Ctrl-Alt-F1 or Alt-F4). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: qemu 1:4.2-3ubuntu2 Uname: Linux 5.6.0-rc6+ x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 19 12:16:31 2020 Dependencies: InstallationDate: Installed on 2017-06-13 (1009 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) KvmCmdLine: COMMAND STAT EUID RUID PIDPPID %CPU COMMAND qemu-system-x86 Sl+ 1000 1000 34275 25235 29.2 qemu-system-x86_64 -m 4G -cpu Skylake-Client -device virtio-vga,virgl=true,xres=1280,yres=720 -accel kvm -device nec-usb-xhci -serial vc -serial stdio -hda /home/usuario/Sistemas/androidx86.img -display gtk,gl=on -device usb-audio kvm-nx-lpage-re S0 0 34284 2 0.0 [kvm-nx-lpage-re] kvm-pit/34275 S0 0 34286 2 0.0 [kvm-pit/34275] MachineType: LENOVO 80UG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-rc6+ root=UUID=6b4ae5c0-c78c-49a6-a1ba-029192618a7a ro quiet ro kvm.ignore_msrs=1 kvm.report_ignored_msrs=0 kvm.halt_poll_ns=0 kvm.halt_poll_ns_grow=0 i915.enable_gvt=1 i915.fastboot=1 cgroup_enable=memory swapaccount=1 zswap.enabled=1 zswap.zpool=z3fold resume=UUID=a82e38a0-8d20-49dd-9cbd-de7216b589fc log_buf_len=16M usbhid.quirks=0x0079:0x0006:0x10 config_scsi_mq_default=y scsi_mod.use_blk_mq=1 mtrr_gran_size=64M mtrr_chunk_size=64M nbd.nbds_max=2 nbd.max_part=63 SourcePackage: qemu UpgradeStatus: Upgraded to focal on 2019-12-22 (87 days ago) dmi.bios.date: 08/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 0XCN45WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Toronto 4A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40679 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 310-14ISK dmi.modalias: dmi:bvnLENOVO:bvr0XCN45WW:bd08/09/2018:svnLENOVO:pn80UG:pvrLenovoideapad310-14ISK:rvnLENOVO:rnToronto4A2:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad310-14ISK: dmi.product.family: IDEAPAD dmi.product.name: 80UG dmi.product.sku: LENOVO_MT_80UG_BU_idea_FM_Lenovo ideapad 310-14ISK dmi.product.version: Lenovo ideapad 310-14ISK dmi.sys.vendor: LENOVO mtime.conffile..etc.apport.crashdb.conf: 2019-08-29T08:39:36.787240 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1304906] Re: Nautilus does not use umask
Upstream fixed it now with this commit https://gitlab.gnome.org/GNOME/nautilus/-/commit/ee035fe0 ** Changed in: nautilus (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1304906 Title: Nautilus does not use umask Status in nautilus package in Ubuntu: Fix Committed Bug description: Nautilus 3.8.2 in Ubuntu 13.10 (64 bit) does not use umask. I have umask set as 0002. When creating a folder with mkdir, group permissions are correct with read and write permission. When creating a folder with Nautilus/right click/New folder, group permission is "Access files" only. It seems that this bug was present many years ago and have resurfaced now in Nautilus 3.8.2. The bug does not exist on an identical computer with Ubuntu 13.10 (64 bit) which has Nautilus version 3.6.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1304906/+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 1869130] Re: Gnome shell app launcher
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem. We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures. At a minimum, we need: 1. The specific steps or actions you took that caused you to encounter the problem. 2. The behavior you expected. 3. The behavior you actually encountered (in as much detail as possible). Thanks! ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/1869130 Title: Gnome shell app launcher Status in gnome-shell package in Ubuntu: Incomplete Bug description: On focal fossa beta, upgraded from 19.10. Also, Password text box on lock screen stretches when you hit enter ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 01:38:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-15 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-18 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869130/+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 1869135] [NEW] GNOME Shell Activities Overview yields no snaps at all
Public bug reported: When looking for an app in the GNOME Shell Activities Overview, it shows no snaps at all (tried with Slack, Visual Studio Code, 0 AD, Powershell). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 08:08:27 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-09 (107 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-21 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Summary changed: - GNOME Shell Activitites Overview yields no snaps at all + GNOME Shell Activities Overview yields no snaps at all -- 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/1869135 Title: GNOME Shell Activities Overview yields no snaps at all Status in gnome-shell package in Ubuntu: New Bug description: When looking for an app in the GNOME Shell Activities Overview, it shows no snaps at all (tried with Slack, Visual Studio Code, 0 AD, Powershell). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 08:08:27 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-09 (107 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-21 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869135/+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 1866194] Re: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker
** Tags added: rls-ff-incomong ** Tags removed: rls-ff-incomong ** Tags added: rls-ff-incoming -- 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/1866194 Title: [Dell Inspiron 7370] shows up in the sound output options but the sound keeps being emitted from the internal laptop speaker Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: New Bug description: Ubuntu version: focal dev Kernel version: 5.4.0-14-generic #17-Ubuntu SMP Thu Feb 6 22:47:59 UTC 2020 Pulseaudio: 1:13.99.1-1ubuntu1 Device CID: 201704-25503 Steps to reproduce: 1. Connect an audio interface. I tried with BT headphones and speakers as well as a USB microphone/output. 2. Make sure it's the one selected as "Output device" 3. Click "Test" -> the test sound outputs from the internal laptop speakers (NOK) 4. Select "Speakers - Built-in Audio" as Output device and click "Test" -> the test sound outputs from the internal laptop speakers (OK) 5. Try to switch back to the BT device and click Test -> same result as in step 3 Tested with 2 different BT devices (one headset and one speaker) as well as a USB audio interface (Zoom H2N microphone). Attached are btmon logs captured during the procedure described above, and pactl logs capture after step 7. I was previously using 19.04 and 19.10 on this device and never experienced this kind of issue. Up to this morning, it was harder to connect the BT device, but once connected, the sound would output on it as expected. Now, the BT connection seems to work better, but I can't output the sound to the BT device... I tried to reboot the device, and also to suspend/resume, but in each case, the BT device can connect back, but the sound is still output from the internal laptop speakers, even when the BT device is selected in the Sound settings. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 1566 F pulseaudio /dev/snd/pcmC0D0c: pieq 1566 F...m pulseaudio /dev/snd/pcmC0D0p: pieq 1566 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 5 22:15:50 2020 InstallationDate: Installed on 2020-01-17 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200116) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1866194/+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 1869130] [NEW] Gnome shell app launcher
Public bug reported: On focal fossa beta, upgraded from 19.10. Also, Password text box on lock screen stretches when you hit enter ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 01:38:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-15 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-18 (7 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1869130 Title: Gnome shell app launcher Status in gnome-shell package in Ubuntu: New Bug description: On focal fossa beta, upgraded from 19.10. Also, Password text box on lock screen stretches when you hit enter ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24 Uname: Linux 5.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu21 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 26 01:38:40 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-15 (39 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-03-18 (7 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1869130/+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 1863239] Re: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group
** No longer affects: pulseaudio (Ubuntu) ** No longer affects: systemd (Ubuntu) ** No longer affects: udev (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmtp in Ubuntu. https://bugs.launchpad.net/bugs/1863239 Title: /dev/bus/usb/*/* device file of HP multi-function printer assigned to "audio" group Status in libmtp package in Ubuntu: In Progress Status in libmtp package in Debian: Unknown Bug description: When testing HPLIP I found out that CUPS backends can access my printer only when they are running as root, when they are running as the special user lp, as it is usually the case, they cannot access the printer. So I tried to find out why and saw that the /dev/bus/usb/*/* device file for the printer has group ownership "audio" and not "lp": till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ ll /dev/bus/usb/*/* crw-rw-r-- 1 root root189, 0 Feb 11 14:17 /dev/bus/usb/001/001 crw-rw-r-- 1 root root189, 2 Feb 11 14:17 /dev/bus/usb/001/003 crw-rw-r-- 1 root root189, 3 Feb 11 14:17 /dev/bus/usb/001/004 crw-rw-r-- 1 root plugdev 189, 4 Feb 14 12:23 /dev/bus/usb/001/005 crw-rw-r-- 1 root root189, 5 Feb 11 14:17 /dev/bus/usb/001/006 crw-rw+ 1 root audio 189, 62 Feb 14 12:37 /dev/bus/usb/001/063 crw-rw-r-- 1 root root189, 128 Feb 11 14:17 /dev/bus/usb/002/001 crw-rw-r-- 1 root root189, 130 Feb 13 09:38 /dev/bus/usb/002/003 till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ The printer is the device /dev/bus/usb/001/063: till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ lsusb Bus 002 Device 003: ID 0b95:1790 ASIX Electronics Corp. AX88179 Gigabit Ethernet Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0097 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5ce Chicony Electronics Co., Ltd Integrated Camera Bus 001 Device 003: ID 8087:0a2b Intel Corp. Bus 001 Device 006: ID 056a:50b7 Wacom Co., Ltd Pen and multitouch sensor Bus 001 Device 063: ID 03f0:7a12 HP, Inc HP OfficeJet Pro 8730 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub till@till-x1yoga:~/ubuntu/hplip/focal/debian/hplip-3.19.12+dfsg0$ There must be a bug somewhere in the UDEV rules. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/1863239/+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 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
It seems this issue only happens to machine which eth port be renamed as eno1. It can not be reproduced on another machine which eth port be renamed to enp2s0. -- 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/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: New Status in OEM Priority Project: New Status in network-manager package in Ubuntu: New Bug description: This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+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 1778946] Re: No dns resolution after closing a vpn/pptp connection
The problem is still there on Ubuntu 18.04.4 LTS. The workaround from comment #30 works for me. $ apt show ppp Package: ppp Version: 2.4.7-2+4.1ubuntu5 Status: install ok installed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in ppp package in Ubuntu: Fix Released Status in ppp package in Debian: New Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lono wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3aff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1778946/+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
