[Desktop-packages] [Bug 1873725] [NEW] Folder under applications menu doesn't show text below last line of icons.
Public bug reported: Under the applications menu the "Utilities" folder does not show the last line of text below the icons. If you launch one of the applications on the last line ie terminal then it will reveal the text below the icon. Description:Ubuntu 20.04 LTS Release:20.04 nautilus: Installed: 1:3.36.1.1-1ubuntu2 Candidate: 1:3.36.1.1-1ubuntu2 Version table: *** 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 22:46:39 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "photo_2020-04-19_22-39-08.jpg" https://bugs.launchpad.net/bugs/1873725/+attachment/5356975/+files/photo_2020-04-19_22-39-08.jpg -- 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/1873725 Title: Folder under applications menu doesn't show text below last line of icons. Status in nautilus package in Ubuntu: New Bug description: Under the applications menu the "Utilities" folder does not show the last line of text below the icons. If you launch one of the applications on the last line ie terminal then it will reveal the text below the icon. Description: Ubuntu 20.04 LTS Release: 20.04 nautilus: Installed: 1:3.36.1.1-1ubuntu2 Candidate: 1:3.36.1.1-1ubuntu2 Version table: *** 1:3.36.1.1-1ubuntu2 500 500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.1.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 22:46:39 2020 GsettingsChanges: InstallationDate: Installed on 2020-04-20 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1873725/+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 1872527] Re: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests)
There's a surprising number of clipboard fixes already landed upstream and waiting to be released in mutter 3.36.2 -- we should probably wait and see if they help. Most of them don't have associated bug reports :/ Also, in case you haven't already please try both 'Ubuntu' and 'Ubuntu on Wayland'. In case one works better than the other. It looks like some upstream fixes are specific to one or the other. -- 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/1872527 Title: Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) Status in mutter package in Ubuntu: Confirmed Status in virt-manager package in Ubuntu: Invalid Bug description: I'm testing Ubuntu 20.04 LTS (Focal Fossa) Beta. I installed Kubuntu 20.04 and virt-manager as I did many times on Ubuntu 18.04. Unfortunatelly when I run a VM (QEMU-KVM, libvirt, libspice-server1 and spice-vdagent) with another Kubuntu 20.04 guest or with Ubuntu 20.04 guest then clipboard doesn't work right. To test it, please install Kubuntu 20.04 and then install Kubuntu / Ubuntu 20.04 as VM (guest). Open some simple text editor and start Ctrl + C and Ctrl + V plain text. 90% of time it will work and 10% of time it won't. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: virt-manager 1:2.2.1-3ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Mon Apr 13 15:02:22 2020 InstallationDate: Installed on 2020-04-09 (4 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) PackageArchitecture: all SourcePackage: virt-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1872527/+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 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
*** This bug is a duplicate of bug 1872527 *** https://bugs.launchpad.net/bugs/1872527 Actually this sounds related to bug 1872527. Maybe we should just use that for now. ** This bug has been marked a duplicate of bug 1872527 Clipboard doesn't work 100% of the time in Ubuntu 20.04 (in KVM guests) -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM Status in gnome-shell package in Ubuntu: Incomplete Bug description: Could you please try install: - Kubuntu 20.04 Focal desktop on bare metal (laptop) - Upgrade all packages - Install virtualization as usually (qemu-kvm, libvirt, virt-manager) - Install Ubuntu 20.04 inside a VM - upgrade all packages in the VM - Start copying (CTRL+X, CTRL+V) plain text between the Kubuntu on laptop and Ubuntu inside VM? Doesn't take too long - doesn't need to much testing. After a couple of trials, the clipboard will hang and you loose the text in clipboard... I don't remember such issues in past. Copying worked fine when I used virt-manager a couple of years ago. Thank you all great people in Canonical for Ubuntu. Ian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 04:43:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu2 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/1873413/+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 1873266] Re: [nvidia] cannot change main monitor after setting scaling for monitors
Can you please look in Settings > Screen Display and tell us if 'Fractional Scaling' is enabled? ** Changed in: mutter (Ubuntu) Status: New => Incomplete -- 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/1873266 Title: [nvidia] cannot change main monitor after setting scaling for monitors Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: After booting with nvidia drivers, if I change which monitor is the main one first, then change the scaling from 100% to 200%, it works. But doing this in the inverse direction, by first setting the scaling and then changing the main monitor, it fails and the screens go black. Oddly enough, it also fails to revert this setting and I have to hard- reboot (though I could probably try switching ttys, etc). This is with focal and focal-proposed enabled. I also have the proprietary 440 nvidia drivers enabled, and I'm using default gnome with x11. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-05 (287 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: nvidia-graphics-drivers-440 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Tags: focal package-from-proposed Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+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 1872971] Re: Xorg crash
*** This bug is a duplicate of bug 1868519 *** https://bugs.launchpad.net/bugs/1868519 ** This bug has been marked a duplicate of private bug 1873195 ** This bug is no longer a duplicate of private bug 1873195 ** This bug has been marked a duplicate of bug 1868519 [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() -- 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/1872971 Title: Xorg crash Status in xorg-server package in Ubuntu: Incomplete Bug description: lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status I was running the game Into the Breach (https://store.steampowered.com/app/590380/Into_the_Breach/) through Steam Play (Proton 5.0-5). When I continue my game and mouse over a character which has been placed on the play field, my session crashes and I am returned to the login screen. This consistently happens every time I load my game and perform the mouseover. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.82 Wed Apr 1 20:04:33 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu1) ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: XFCE Date: Wed Apr 15 13:38:42 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.82, 5.4.0-21-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0819] Subsystem: Dell GM108M [GeForce MX130] [1028:0819] InstallationDate: Installed on 2020-04-09 (6 days ago) InstallationMedia: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) MachineType: Dell Inc. Latitude 5591 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=595cdefb-5445-4df8-99e9-6a60485a8c97 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.1 dmi.board.name: 0DVVG1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.1:bd01/11/2019:svnDellInc.:pnLatitude5591:pvr:rvnDellInc.:rn0DVVG1:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5591 dmi.product.sku: 0819 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+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/1872971/+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 1868519] Re: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite()
** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed ** Tags removed: cosmic disco -- 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/1868519 Title: [nvidia] Xorg crashed with SIGSEGV in xf86ScreenMoveCursor() from xf86MoveCursor() from miPointerMoveNoEvent() from miPointerSetPosition() from positionSprite() Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-graphics-drivers. This problem was most recently seen with package version 2:1.20.7-2ubuntu2, the problem page at https://errors.ubuntu.com/problem/5a9ed7ea32a1d20e4222dbe8712aa9640b42a73c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1868519/+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 1873266] Re: cannot change main monitor after setting scaling for monitors w/nvidia drivers
"screens go black" reminds me of bug 1873403 which might be somehow related. ** Summary changed: - cannot change main monitor after setting scaling for monitors w/nvidia drivers + [nvidia] cannot change main monitor after setting scaling for monitors -- 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/1873266 Title: [nvidia] cannot change main monitor after setting scaling for monitors Status in gnome-control-center package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-440 package in Ubuntu: Incomplete Bug description: After booting with nvidia drivers, if I change which monitor is the main one first, then change the scaling from 100% to 200%, it works. But doing this in the inverse direction, by first setting the scaling and then changing the main monitor, it fails and the screens go black. Oddly enough, it also fails to revert this setting and I have to hard- reboot (though I could probably try switching ttys, etc). This is with focal and focal-proposed enabled. I also have the proprietary 440 nvidia drivers enabled, and I'm using default gnome with x11. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-07-05 (287 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia Package: nvidia-graphics-drivers-440 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Tags: focal package-from-proposed Uname: Linux 5.4.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873266/+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 1873718] Re: CSR8510 based BTA-402 Bluetooth device cannot be started
Sounds like this might be a kernel bug, or a hardware problem. I am skeptical of CSR Bluetooth dongles since they seem to be consistently unreliable, at least on Linux. Please try a newer (or older) kernel version and tell us if that makes any difference: https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D Or more simply just try live booting Ubuntu 20.04 from USB and tell us if that has the same bug: http://cdimage.ubuntu.com/daily-live/current/ Ubuntu 20.04 is due for release at the end of this week. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: bluez (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1873718/+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 1873719] Re: Relatar
Please explain in more detail what kind of problem you are having. ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1873719 Title: Relatar Status in Ubuntu: Incomplete Bug description: Relatar erro na execução Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Apr 19 23:33:32 2020 DistUpgraded: 2020-04-18 10:05:27,584 DEBUG icon theme changed, re-reading DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: intel-hid, 3.1, 4.4.0-177-generic, x86_64: installed oem-wifi-ath9k-msi, 1, 4.4.0-177-generic, x86_64: installed oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1, 4.4.0-177-generic, x86_64: installed radeon-si, 1a, 4.4.0-38-generic, x86_64: built ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:078c] InstallationDate: Installed on 2019-08-18 (246 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=10e0a602-865d-4c14-bc06-438dbffafffc ro locale=pt_BR alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-04-18 (1 days ago) dmi.bios.date: 07/17/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.0 dmi.board.name: 06J0HF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.0:bd07/17/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn06J0HF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Apr 18 01:24:06 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 29164 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1873719/+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 1873719] [NEW] Relatar
Public bug reported: Relatar erro na execução Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Apr 19 23:33:32 2020 DistUpgraded: 2020-04-18 10:05:27,584 DEBUG icon theme changed, re-reading DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: intel-hid, 3.1, 4.4.0-177-generic, x86_64: installed oem-wifi-ath9k-msi, 1, 4.4.0-177-generic, x86_64: installed oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1, 4.4.0-177-generic, x86_64: installed radeon-si, 1a, 4.4.0-38-generic, x86_64: built ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:078c] InstallationDate: Installed on 2019-08-18 (246 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron 15-3567 ProcEnviron: LANGUAGE=pt_BR: PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=10e0a602-865d-4c14-bc06-438dbffafffc ro locale=pt_BR alx.enable_wol=1 mem_sleep_default=deep alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2020-04-18 (1 days ago) dmi.bios.date: 07/17/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.0 dmi.board.name: 06J0HF dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.0:bd07/17/2018:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn06J0HF:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 15-3567 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sat Apr 18 01:24:06 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 29164 vendor AUO xserver.version: 2:1.18.4-0ubuntu0.8 ** 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/1873719 Title: Relatar Status in xorg package in Ubuntu: New Bug description: Relatar erro na execução Linux ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Sun Apr 19 23:33:32 2020 DistUpgraded: 2020-04-18 10:05:27,584 DEBUG icon theme changed, re-reading DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: intel-hid, 3.1, 4.4.0-177-generic, x86_64: installed oem-wifi-ath9k-msi, 1, 4.4.0-177-generic, x86_64: installed oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1, 4.4.0-177-generic, x86_64: installed radeon-si, 1a, 4.4.0-38-generic, x86_64: built ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:078c] InstallationDate: Installed on 2019-08-18 (246 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Inspiron
[Desktop-packages] [Bug 1873718] [NEW] CSR8510 based BTA-402 Bluetooth device cannot be started
Public bug reported: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0: Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1873718 Title: CSR8510 based BTA-402 Bluetooth device cannot be started Status in bluez package in Ubuntu: New Bug description: In the GUI, I can go to the Bluetooth settings and it shows BT to be off. I turn on the little switch at the top but nothing else changes. If I navigate away from this page and then back, the switch is off again. If I try to reset the device on the command line I get: seb@eragon:~$ sudo hciconfig hci0 reset Can't init device hci0: Connection timed out (110) ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu5.1 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 20 14:39:55 2020 EcryptfsInUse: Yes InterestingModules: bnep btusb bluetooth MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_NZ.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-46-generic root=/dev/mapper/vg0-root rw rootflags=errors=remount-ro quiet splash vt.handoff=1 pti=off SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/23/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FA dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 990FXA-UD3 dmi.board.vendor: AMD Corporation dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFA:bd10/23/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnAMDCorporation:rn990FXA-UD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 DOWN RX bytes:0 acl:0 sco:0 events:0 errors:0 TX bytes:0 acl:0 sco:0 commands:1 errors:1 rfkill: 0: hci0:
[Desktop-packages] [Bug 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags added: bionic -- 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/1423773 Title: Gnome-Shell don't free ram when I change a wallpaper Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Sorry for my bad english, here is the link to see the error by yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+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 1423773] Re: Gnome-Shell don't free ram when I change a wallpaper
** Tags added: leak ** Tags added: 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/1423773 Title: Gnome-Shell don't free ram when I change a wallpaper Status in gnome-shell package in Ubuntu: Confirmed Bug description: Sorry for my bad english, here is the link to see the error by yourself: https://www.youtube.com/watch?v=O53tt-6v81Y=youtu.be To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1423773/+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 1873700] Re: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
Thanks for the clarification. Can you please report that second "real" issue as a new bug by running: ubuntu-bug linux ** 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/1873700 Title: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands Status in gnome-shell package in Ubuntu: Invalid Bug description: I lost ability to rotate the display upon upgrade to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 15:04:26 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873700/+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 1873625] Re: Mouse moves at the bottom right of the screen at log-in
This is a "feature" but efforts are underway upstream to change it: https://gitlab.gnome.org/GNOME/mutter/-/issues/651 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #651 https://gitlab.gnome.org/GNOME/mutter/-/issues/651 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/651 Importance: Unknown Status: Unknown ** Summary changed: - Mouse moves at the bottom right of the screen at log-in + Center the mouse cursor at startup ** Changed in: mutter (Ubuntu) Importance: Undecided => Wishlist ** Changed in: mutter (Ubuntu) Status: New => Triaged -- 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/1873625 Title: Center the mouse cursor at startup Status in Mutter: Unknown Status in mutter package in Ubuntu: Triaged Bug description: When I open a session, the mouse cursor moves at the bottom-right of the screen, at a fixed position. The coordinates are about (x:1730, y:970) on a 1920x1080 screen. When I close the session, the mouse goes again to this position. I am not sure if the issue really comes from mutter, or gdm, or other component. This behavior is specially annoying because your first action after log-in will probably consist in launching an application by clicking its icon at opposite position of the screen, in the top-left part of the launch bar. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 09:03:01 2020 InstallationDate: Installed on 2018-04-07 (742 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-04 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1873625/+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 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Using GNOME in the guest isn't removing it from the equation, it's only changing the equation. Actually this could equally be a problem with virt-manager. What happens if both the host and guest are not GNOME? -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM Status in gnome-shell package in Ubuntu: Incomplete Bug description: Could you please try install: - Kubuntu 20.04 Focal desktop on bare metal (laptop) - Upgrade all packages - Install virtualization as usually (qemu-kvm, libvirt, virt-manager) - Install Ubuntu 20.04 inside a VM - upgrade all packages in the VM - Start copying (CTRL+X, CTRL+V) plain text between the Kubuntu on laptop and Ubuntu inside VM? Doesn't take too long - doesn't need to much testing. After a couple of trials, the clipboard will hang and you loose the text in clipboard... I don't remember such issues in past. Copying worked fine when I used virt-manager a couple of years ago. Thank you all great people in Canonical for Ubuntu. Ian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 04:43:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu2 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/1873413/+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 1873630] Re: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting.
** Changed in: pulseaudio (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1873630 Title: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa- ucm.c:2158, function device_add_hw_mute_jack(). Aborting. Status in pulseaudio package in Ubuntu: Fix Released Bug description: I have a Gigabyte motherboard that gives pulseaudio fits in Ubuntu 20.04 beta. (It worked fine in 18.04.4 LTS.) It produced pulseaudio crashes with bug #1870833 until a proposed fix was brought in from upstream: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu2 However, that did not actually make pulseaudio work; now it throws this error and aborts: Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. It was suggested in the previous bug that I should open a new bug for this. Here you are! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 00:25:26 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
And yes nvidia-drm.modeset=1 will give you back the missing boot animation, but that discussion should stay in bug 1868240. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help :
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Note that we don't recommend use of nvidia-drm.modeset=1 for most users because it still results in some bugs: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset And I'm not sure that's even a complete list. So you should be aware of what you're getting into. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1873700] Re: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
Sorry - not a total noob here, but enough to embarrass myself... I had to boot with "nomodeset" in order to get my machine to boot. That caused the situation I described here. When I blacklisted the nouveau video driver, I got my functionality back. For those who know better how to fix these things - the real problem is that the nouveau driver didn't work on my XPS 13 9365, causing it to hang while trying to boot. -- 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/1873700 Title: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands Status in gnome-shell package in Ubuntu: New Bug description: I lost ability to rotate the display upon upgrade to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 15:04:26 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873700/+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 1873692] Re: Do Not Disturb setting does not persist across login sessions
I have a feeling you are right that it may not be gnome-control-center doing this as setting the default value of show-banners in /usr/share/glib2.0/schemas to false ends up being ignored at login. It is unclear to me what the desired behaviour is from those discussions, but my expectation is that an exposed user setting will stay set until I unset 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/1873692 Title: Do Not Disturb setting does not persist across login sessions Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Selecting do not disturb from settings does not persist across login sessions. What I did - Set Do Not Disturb in settings or from top bar to prevent pop-up notification banners from appearing, which it does. - logout and log back in - expect pop-up notifications to continue to be blocked and only displayed in the top bar What happens: - Do Not Disturb is reset to disabled on each new login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 14:42:49 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-24 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873692/+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 1873700] Re: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
** Package changed: ubuntu => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1873700 Title: Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands Status in gnome-shell package in Ubuntu: New Bug description: I lost ability to rotate the display upon upgrade to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 15:04:26 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-18 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873700/+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 1873700] [NEW] Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands
You have been subscribed to a public bug: I lost ability to rotate the display upon upgrade to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 15:04:26 2020 DisplayManager: gdm3 RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-18 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Display won't rotate, rotate lock/unlock button missing, can't rotate screen with xrandr commands https://bugs.launchpad.net/bugs/1873700 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873104] Re: Defaults to USB audio after every reboot
I agree. I don't see this as an upstream issue because I have tried it on other distros - they worked as expected. USB hotplugging updates the audio device. However, a reboot simply restores whatever was last in use. For some reason, only on Ubuntu, it treats a reboot as plugging a new USB device. And this occurs on every flavor I tested - Ubuntu, Mate, Kubuntu and Xubuntu. In Kubuntu it can be slightly mitigated because you can set the default from the tray. -- 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/1873104 Title: Defaults to USB audio after every reboot Status in alsa-driver package in Ubuntu: Confirmed Bug description: I manually set my audio output to the Line Out. Every reboot this settings is lost and the system defaults back to the USB output. I have several other distros to test - Ubuntu and its flavors are the only ones that have this problem. Something changed in 19.04 or 19.10 that broke this, and it continues to be an issue in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: caleb 1778 F pulseaudio /dev/snd/controlC3: caleb 1778 F pulseaudio /dev/snd/controlC1: caleb 1778 F pulseaudio /dev/snd/controlC0: caleb 1778 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 15 19:32:36 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.name: 8437 dmi.board.vendor: HP dmi.board.version: 1.3 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Desktop PC 880-p1xx dmi.product.sku: 2TB61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1873104/+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
As mentioned in comment #37 the internal mic works well with Ubuntu 20.04 live mode. I haven't tried installing Ubuntu 20.04 though, as some report the mic doesn't work once installed. I wish I knew more and had the time to understand the difference (beyond kernel) between Ubuntu 20.04 live mode and non-live mode. I'm currently running Ubuntu 19.10. Let me know if there is something I can test to understand why Ubuntu 20.04 live mode works. Thanks -- 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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop
Sorry to post so much - I wish I could consolidate or edit all these posts. The next day I came back and it didn't work in Zoom. I tried a bunch of things listed on the following web page, starting with simplest first, from https://support.system76.com/articles/audio/ until finally I did sudo apt install --reinstall alsa-base alsa-utils pulseaudio linux- sound-base libasound2 then I rebooted and sudo alsa force-reload and it worked. Which is weird, I think, because I just did this reinstall of these modules 3 days ago. I don't think the versions of these modules changed. I don't know what's going on. My guess is that it breaks because something changes a configuration file. And then I guess it's fixed when the configuration file is re-initialized by re- installing these modules. I wish I could pinpoint it. -- 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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages from focal: xserver-xorg-video-geode 2.11.20-1 in focal Comment: obsolete source package, only builds xserver for i386 which is not supported as a host arch; LP: #1772588 1 package successfully removed. ** Changed in: xserver-xorg-video-geode (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-trident 1:1.3.8-1build2 in focal xserver-xorg-video-trident 1:1.3.8-1build2 in focal amd64 xserver-xorg-video-trident 1:1.3.8-1build2 in focal arm64 xserver-xorg-video-trident 1:1.3.8-1build2 in focal armhf xserver-xorg-video-trident 1:1.3.8-1build2 in focal ppc64el xserver-xorg-video-trident 1:1.3.8-1build2 in focal riscv64 xserver-xorg-video-trident 1:1.3.8-1build2 in focal s390x xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal amd64 xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal arm64 xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal armhf xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal ppc64el xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal riscv64 xserver-xorg-video-trident-dbgsym 1:1.3.8-1build2 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-trident (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-tdfx 1:1.5.0-2 in focal xserver-xorg-video-tdfx 1:1.5.0-2 in focal amd64 xserver-xorg-video-tdfx 1:1.5.0-2 in focal arm64 xserver-xorg-video-tdfx 1:1.5.0-2 in focal armhf xserver-xorg-video-tdfx 1:1.5.0-2 in focal ppc64el xserver-xorg-video-tdfx 1:1.5.0-2 in focal riscv64 xserver-xorg-video-tdfx 1:1.5.0-2 in focal s390x xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal amd64 xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal arm64 xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal armhf xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal ppc64el xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal riscv64 xserver-xorg-video-tdfx-dbgsym 1:1.5.0-2 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-tdfx (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-ast 1.1.5-1.1build1 in focal xserver-xorg-video-ast 1.1.5-1.1build1 in focal amd64 xserver-xorg-video-ast 1.1.5-1.1build1 in focal arm64 xserver-xorg-video-ast 1.1.5-1.1build1 in focal armhf xserver-xorg-video-ast 1.1.5-1.1build1 in focal ppc64el xserver-xorg-video-ast 1.1.5-1.1build1 in focal riscv64 xserver-xorg-video-ast 1.1.5-1.1build1 in focal s390x xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal amd64 xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal arm64 xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal armhf xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal ppc64el xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal riscv64 xserver-xorg-video-ast-dbgsym 1.1.5-1.1build1 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-ast (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-mach64 6.9.6-1build1 in focal xserver-xorg-video-mach64 6.9.6-1build1 in focal amd64 xserver-xorg-video-mach64 6.9.6-1build1 in focal arm64 xserver-xorg-video-mach64 6.9.6-1build1 in focal armhf xserver-xorg-video-mach64 6.9.6-1build1 in focal ppc64el xserver-xorg-video-mach64 6.9.6-1build1 in focal riscv64 xserver-xorg-video-mach64 6.9.6-1build1 in focal s390x xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal amd64 xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal arm64 xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal armhf xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal ppc64el xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal riscv64 xserver-xorg-video-mach64-dbgsym 6.9.6-1build1 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-mach64 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal amd64 xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal arm64 xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal armhf xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal ppc64el xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal riscv64 xserver-xorg-video-savage 1:2.3.9-2ubuntu1 in focal s390x xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal amd64 xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal arm64 xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal armhf xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal ppc64el xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal riscv64 xserver-xorg-video-savage-dbgsym 1:2.3.9-2ubuntu1 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-savage (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal amd64 xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal arm64 xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal armhf xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal ppc64el xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal riscv64 xserver-xorg-video-siliconmotion 1:1.7.9-2ubuntu2 in focal s390x xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal amd64 xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal arm64 xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal armhf xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal ppc64el xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal riscv64 xserver-xorg-video-siliconmotion-dbgsym 1:1.7.9-2ubuntu2 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-siliconmotion (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-input-elographics 1:1.4.1-1build6 in focal xserver-xorg-input-elographics 1:1.4.1-1build6 in focal amd64 xserver-xorg-input-elographics 1:1.4.1-1build6 in focal arm64 xserver-xorg-input-elographics 1:1.4.1-1build6 in focal armhf xserver-xorg-input-elographics 1:1.4.1-1build6 in focal ppc64el xserver-xorg-input-elographics 1:1.4.1-1build6 in focal riscv64 xserver-xorg-input-elographics 1:1.4.1-1build6 in focal s390x xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal amd64 xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal arm64 xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal armhf xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal ppc64el xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal riscv64 xserver-xorg-input-elographics-dbgsym 1:1.4.1-1build6 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-input-elographics (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal amd64 xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal arm64 xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal armhf xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal ppc64el xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal riscv64 xserver-xorg-video-sisusb 1:0.9.7-1build2 in focal s390x xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal amd64 xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal arm64 xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal armhf xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal ppc64el xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal riscv64 xserver-xorg-video-sisusb-dbgsym 1:0.9.7-1build2 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-sisusb (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-neomagic 1:1.3.0-1 in focal xserver-xorg-video-neomagic 1:1.3.0-1 in focal amd64 xserver-xorg-video-neomagic 1:1.3.0-1 in focal arm64 xserver-xorg-video-neomagic 1:1.3.0-1 in focal armhf xserver-xorg-video-neomagic 1:1.3.0-1 in focal ppc64el xserver-xorg-video-neomagic 1:1.3.0-1 in focal riscv64 xserver-xorg-video-neomagic 1:1.3.0-1 in focal s390x xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal amd64 xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal arm64 xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal armhf xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal ppc64el xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal riscv64 xserver-xorg-video-neomagic-dbgsym 1:1.3.0-1 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-neomagic (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-video-r128 6.12.0-1 in focal xserver-xorg-video-r128 6.12.0-1 in focal amd64 xserver-xorg-video-r128 6.12.0-1 in focal arm64 xserver-xorg-video-r128 6.12.0-1 in focal armhf xserver-xorg-video-r128 6.12.0-1 in focal ppc64el xserver-xorg-video-r128 6.12.0-1 in focal riscv64 xserver-xorg-video-r128 6.12.0-1 in focal s390x xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal amd64 xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal arm64 xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal armhf xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal ppc64el xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal riscv64 xserver-xorg-video-r128-dbgsym 6.12.0-1 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-video-r128 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal amd64 xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal arm64 xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal armhf xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal ppc64el xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal riscv64 xserver-xorg-input-mutouch 1:1.3.0-1build9 in focal s390x xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal amd64 xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal arm64 xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal armhf xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal ppc64el xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal riscv64 xserver-xorg-input-mutouch-dbgsym 1:1.3.0-1build9 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-input-mutouch (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1772588] Re: Remove obsolete X11 drivers from the archive
Removing packages: xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal amd64 xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal arm64 xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal armhf xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal ppc64el xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal riscv64 xserver-xorg-input-aiptek 1:1.4.1-2build1 in focal s390x xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal amd64 xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal arm64 xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal armhf xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal ppc64el xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal riscv64 xserver-xorg-input-aiptek-dbgsym 1:1.4.1-2build1 in focal s390x Comment: (From Debian) ROM; unmaintained, obsolete, or both; Debian bug #955603 Remove [y|N]? y ** Changed in: xserver-xorg-input-aiptek (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1772588 Title: Remove obsolete X11 drivers from the archive Status in xf86-input-mtrack package in Ubuntu: Confirmed Status in xf86-input-xwiimote package in Ubuntu: New Status in xserver-xorg-input-aiptek package in Ubuntu: Fix Released Status in xserver-xorg-input-elographics package in Ubuntu: Fix Released Status in xserver-xorg-input-evdev package in Ubuntu: Invalid Status in xserver-xorg-input-keyboard package in Ubuntu: New Status in xserver-xorg-input-mouse package in Ubuntu: New Status in xserver-xorg-input-mutouch package in Ubuntu: Fix Released Status in xserver-xorg-input-void package in Ubuntu: New Status in xserver-xorg-video-ast package in Ubuntu: Fix Released Status in xserver-xorg-video-geode package in Ubuntu: Fix Released Status in xserver-xorg-video-mach64 package in Ubuntu: Fix Released Status in xserver-xorg-video-neomagic package in Ubuntu: Fix Released Status in xserver-xorg-video-r128 package in Ubuntu: Fix Released Status in xserver-xorg-video-savage package in Ubuntu: Fix Released Status in xserver-xorg-video-siliconmotion package in Ubuntu: Fix Released Status in xserver-xorg-video-sisusb package in Ubuntu: Fix Released Status in xserver-xorg-video-tdfx package in Ubuntu: Fix Released Status in xserver-xorg-video-trident package in Ubuntu: Fix Released Status in Debian: Fix Released Bug description: xserver-xorg-video-all has not depended on these drivers for quite some time now, meaning that installation images didn't have them either nor installed them on the system. Now would be the time to drop them from the archive before next LTS & HWE-18.04 stack and in preparation for xserver 1.20. Some rationale in detail for future reference: input: -aiptek: no upstream release in 7 years -elographics: no upstream release in 6 years -evdev: replaced by -libinput (not entirely, see comment #1) -keyboard: replaced by -libinput -mtrack: no upstream release in 3 years, should be replaceable by -libinput by now -mouse: replaced by -libinput -mutouch: no upstream release in 7 years -void: xserver can start without an input driver these days -xwiimote: no upstream release in 5 years video: -ast: no upstream release in 3 years, no KMS support -geode: i386 only, no kernel support since moving to i586 (or i686?) -mach64: no KMS support -neomagic: no upstream release in 3 years, no KMS support -r128: no KMS support -savage: no KMS support -siliconmotion: no KMS suppport -sisusb: no KMS support -tdfx: no KMS support -trident: no KMS support Fedora dropped drivers without KMS (kernel modesetting) support five years ago: https://lists.fedoraproject.org/pipermail/devel/2013-August/188429.html one exception to this is -openchrome, which we'll keep since it has some users and might even get KMS support before next LTS. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+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 1553685] Re: Lenovo Y700-17ISK subwoofer doesn't work
This is the most heated bug on this site. Can someone please get this fixed? -- 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/1553685 Title: Lenovo Y700-17ISK subwoofer doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: Lenovo Y700-17ISK (Intel Core i7-6700HQ/RAM 16GB/SSD 512GB/Nvidia GTX960M 4GB) Operating system: Ubuntu 16.04 (xenial-desktop-amd64.iso 04-Mar-2016, kernel 4.4.0-10-generic, nvidia 361.28) Problem: Notebook subwoofer doesn't work. Judging from alsa-info.sh output, there is no pin declared for the bass output by BIOS. Please find a zip file attached: 'alsa-info_hdajackretask-unconnected-pins' ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-10-generic 4.4.0-10.25 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: aljosa 1776 F pulseaudio CurrentDesktop: Unity Date: Sun Mar 6 11:02:21 2016 HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125 InstallationDate: Installed on 2016-03-05 (0 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304) MachineType: LENOVO 80Q0 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.4.0-10-generic N/A linux-backports-modules-4.4.0-10-generic N/A linux-firmware1.156 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2016 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN30WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 7A dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-17ISK dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK: dmi.product.name: 80Q0 dmi.product.version: Lenovo ideapad Y700-17ISK dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1553685/+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 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus
There's a patch in #71. Unfortunately, I don't know how to properly submit the patch. -- 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/1244090 Title: Pressing any global keyboard shortcut causes temporary loss of focus Status in Mutter: Confirmed Status in compiz package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-shell package in Fedora: Confirmed Status in gnome package in openSUSE: Unknown Bug description: When pressing any global keyboard shourtcut (configurable via System settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout, volume up/down), focus temporary switches from active text input to something else, then restores back shortly. Maybe even active window loses focus, but window frame does not shows this (window header remains to look active). For example: when I press ctrl+shift here to switch keyboard layout, when writing this description, yellow frame disappears from text input box, text caret disappears too; they appear again when releasing ctrl+shift. The same occurs in all other programs, i.e. terminal. It causes serious annoyance, for example in Twitter when losing focus in Reply text box, reply rolls up and I have to click it again with mouse and set caret to correct place each time I switch keyboard layouts. Other key combinations, not only ctrl+shift, also cause this. It is especially annoying when using keyboard layout switch shortcut handled by the same subsystem (media-keys plugin): case SWITCH_INPUT_SOURCE_KEY: case SWITCH_INPUT_SOURCE_BACKWARD_KEY: do_switch_input_source_action (manager, type); break; (Original gnome-settings-daemon, from which unity-settings-daemon was forked, does not use media-keys plugin to switch keyboard layout). -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session 3.9.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 24 11:42:19 2013 InstallationDate: Installed on 2013-10-23 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1244090/+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 1873692] Re: Do Not Disturb setting does not persist across login sessions
Thanks for your report! I can confirm it. When "Do Not Disturb" is enabled, this dconf value is set: $ gsettings get org.gnome.desktop.notifications show-banners false But something always sets it to "true" at login. (That something is reasonably not gnome-control-center, btw, since it's not launched automatically at login.) The feature was preceded by long discussions: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/56 https://gitlab.gnome.org/GNOME/gnome-shell/issues/239 I have a feeling that the behavior is intentional, even if I didn't find any explicit statement in that direction. ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #56 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/56 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #239 https://gitlab.gnome.org/GNOME/gnome-shell/issues/239 ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1873692 Title: Do Not Disturb setting does not persist across login sessions Status in gnome-control-center package in Ubuntu: Confirmed Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Selecting do not disturb from settings does not persist across login sessions. What I did - Set Do Not Disturb in settings or from top bar to prevent pop-up notification banners from appearing, which it does. - logout and log back in - expect pop-up notifications to continue to be blocked and only displayed in the top bar What happens: - Do Not Disturb is reset to disabled on each new login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 14:42:49 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-24 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873692/+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 1244090] Re: Pressing any global keyboard shortcut causes temporary loss of focus
Also loses focus on Microsoft To-Do app. Hope that is enough to change the status from Undecided to actual real bug. -- 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/1244090 Title: Pressing any global keyboard shortcut causes temporary loss of focus Status in Mutter: Confirmed Status in compiz package in Ubuntu: Confirmed Status in gnome-settings-daemon package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Triaged Status in gnome-settings-daemon package in ALT Linux: Unknown Status in gnome-shell package in Fedora: Confirmed Status in gnome package in openSUSE: Unknown Bug description: When pressing any global keyboard shourtcut (configurable via System settings -> Keyboard -> Shortcuts; i.e. for switching keyboard layout, volume up/down), focus temporary switches from active text input to something else, then restores back shortly. Maybe even active window loses focus, but window frame does not shows this (window header remains to look active). For example: when I press ctrl+shift here to switch keyboard layout, when writing this description, yellow frame disappears from text input box, text caret disappears too; they appear again when releasing ctrl+shift. The same occurs in all other programs, i.e. terminal. It causes serious annoyance, for example in Twitter when losing focus in Reply text box, reply rolls up and I have to click it again with mouse and set caret to correct place each time I switch keyboard layouts. Other key combinations, not only ctrl+shift, also cause this. It is especially annoying when using keyboard layout switch shortcut handled by the same subsystem (media-keys plugin): case SWITCH_INPUT_SOURCE_KEY: case SWITCH_INPUT_SOURCE_BACKWARD_KEY: do_switch_input_source_action (manager, type); break; (Original gnome-settings-daemon, from which unity-settings-daemon was forked, does not use media-keys plugin to switch keyboard layout). -- For other layout switching problems introduced in Ubuntu 13.10 you can see bug 1218322. -- ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-session 3.9.90-0ubuntu3 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Thu Oct 24 11:42:19 2013 InstallationDate: Installed on 2013-10-23 (0 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) MarkForUpload: True PackageArchitecture: all SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1244090/+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 130213] Re: rhythmbox doesn't play the next song after first song finished
I have had this (or a similar) problem for the last month or so, Rhythmbox is stuck in shuffle mode. I'm using Ubuntu 16:04, which I've had installed for close to four years now, but this problem suddenly popped up very recently. I've uninstalled and reinstalled, but no luck. Doesn't matter if I try to activate repeat before starting to play the first song in a list or before selecting all or while I'm playing a song, it is completely stuck in shuffle mode. Also, the sign that is supposed to say it's in repeat or shuffle mode is very faint, just a very narrow band around that button. Wouldn't it be better to make this clearer? Im attaching the output to stderr when I run rhythmbox --debug. ** Attachment added: "stderr.log" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/130213/+attachment/5356887/+files/stderr.log -- 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/130213 Title: rhythmbox doesn't play the next song after first song finished Status in rhythmbox package in Ubuntu: Fix Released Bug description: Binary package hint: rhythmbox (I'm not English... I'll try to write as well as I can) Hi Community! The problem starts today, no updates, no strange happening... nothing. Often Rhytmbox stop playing after the song finished. It doesn't play the next song... I'm using the shuffle mode. After restarting rb it seems to work correctly... maybe a one-time error Bye bye _LameMind ProblemType: Bug Architecture: i386 Date: Fri Aug 3 17:49:26 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/rhythmbox Package: rhythmbox 0.11.1-0ubuntu2~pollycoke1 PackageArchitecture: i386 ProcCmdline: rhythmbox ProcCwd: /home/lamemind ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux WrkSt@t 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux UnreportableReason: Questo non è un pacchetto Ubuntu genuino To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/130213/+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 130213] Re: rhythmbox doesn't play the next song after first song finished
I have had this (or a similar) problem for the last month or so, Rhythmbox is stuck in shuffle mode. I'm using Ubuntu 16:04, which I've had installed for close to four years now, but this problem suddenly popped up very recently. I've uninstalled and reinstalled, but no luck. Doesn't matter if I try to activate repeat before starting to play the first song in a list or before selecting all or while I'm playing a song, it is completely stuck in shuffle mode. Also, the sign that is supposed to say it's in repeat or shuffle mode is very faint, just a very narrow band around that button. Wouldn't it be better to make this clearer? Im attaching the output to stderr when I run rhythmbox --debug. ** Attachment added: "stderr.log" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/130213/+attachment/5356888/+files/stderr.log -- 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/130213 Title: rhythmbox doesn't play the next song after first song finished Status in rhythmbox package in Ubuntu: Fix Released Bug description: Binary package hint: rhythmbox (I'm not English... I'll try to write as well as I can) Hi Community! The problem starts today, no updates, no strange happening... nothing. Often Rhytmbox stop playing after the song finished. It doesn't play the next song... I'm using the shuffle mode. After restarting rb it seems to work correctly... maybe a one-time error Bye bye _LameMind ProblemType: Bug Architecture: i386 Date: Fri Aug 3 17:49:26 2007 DistroRelease: Ubuntu 7.04 ExecutablePath: /usr/bin/rhythmbox Package: rhythmbox 0.11.1-0ubuntu2~pollycoke1 PackageArchitecture: i386 ProcCmdline: rhythmbox ProcCwd: /home/lamemind ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: rhythmbox Uname: Linux WrkSt@t 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux UnreportableReason: Questo non è un pacchetto Ubuntu genuino To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/130213/+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 1872844] Re: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
Chrome and VLC have it though -- 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/1872844 Title: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: Confirmed Status in vlc package in Ubuntu: New Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1872844/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
@Rajat Pandita: awesome, thanks for sharing! I came here to report that I too was experiencing this bug: GTX 1060, up-to-date Focal Fossa beta, NVidia 440 driver series, 5.4.0-24 kernel. Couldn't log in. Removing `splash` from grub's kernel parameters solved the issue, but adding `nvidia-drm.modeset=1` is a much better solution since it leaves the splash screen unaffected (so you get a nice-looking boot). Besides, I remember from using KDE on Archlinux that `nvidia-drm.modeset=1` is required to get decent performance from NVidia drivers on KDE (though on Ubuntu I'm using Gnome). The driver install script should really edit and update grub configuration accordingly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1872844] Re: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions)
Well, it works when you change theme from Dark to White, but doesn't work when you switch from Standard to White. This doesn't look like a problem with the software for me. >I guess you've turned off integrated titlebars I didn't turn off anything, it's freshly installed ubuntu 20. For me firefox on wayland doesn't have this title bar at all. -- 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/1872844 Title: Changing theme Light<->Standard preserves theme for Firefox title bar (in Xorg sessions) Status in chromium-browser package in Ubuntu: New Status in firefox package in Ubuntu: Confirmed Status in vlc package in Ubuntu: New Bug description: This is Ubuntu 20.04 beta. Start a program that has title bar. Try Firefox or whatever. Then navigate to settings->appearance. Now set the theme to Standard, then Light - Firefox will now have white theme with dark titlebar. Setting to Dark resets the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1872844/+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 1868872] Re: Nautilus Cant open files in shared folders
Great, thanks for confrming, closing the bug! ** Changed in: nautilus (Ubuntu) Status: Incomplete => Fix Released -- 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/1868872 Title: Nautilus Cant open files in shared folders Status in nautilus package in Ubuntu: Fix Released Bug description: When i go to a shared folder and try to open a .doc file i received a notification saying that no app cant open the file. Please see the pictures ProblemType: Bug 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: Tue Mar 24 20:13:33 2020 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1868872/+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 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
Great, thanks for testing, closing the bug! ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+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 1523100] Re: Alsa not detecting internal microphone [ALC255] (Realtek)
I had a problem with a *missing* internal microphone today (well, I spotted it today - probably been like this for ages...). Note that this was PulseAudio saying that there were no input devices. The problem (as I eventually spotted) was that I'd set the Profile to be Analgue Stereo Output (under Configuration in PA Volume Control). Setting this to Analogue Stereo Duplex made the internal mic show up. Might not be the problem for most people, but you never know. I did notice that if I plugged in an *external* mic the Profile switched to Duplex automatically. -- 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/1523100 Title: Alsa not detecting internal microphone [ALC255] (Realtek) Status in alsa-driver package in Ubuntu: Confirmed Bug description: I've just installed Ubuntu 16.04 alongside Windows 10 on a 64bit Acer Aspire VN7-792G and noticed, that the internal microphone doesn't work. The computer has been released a couple of months ago and it's Intel Skylake -based with a Sunrise Point -based motherboard. INFO: The problem exists in Ubuntu 15.10 too, only microphone jack detected. Currently using Ubuntu 16.04 for proper hardware support. Alsa reports the audio device to be: Card: HDA Intel PCH Chip: Intel Skylake HDMI The speakers are working fine, but both alsamixer and pavucontrol (Pulseaudio Volume Control) raport the unplugged external microphone connector as the only sound input. I have tried many of the alsa model configurations (options snd-hda- intel model=something) without success, alsa finds only the microphone jack, which works fine when I plug an external microphone in it. Here's some info: lspci | grep -I audio: 00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-H HD Audio (rev 31) cat /proc/asound/cards: 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x8432 irq 128 And a clip from dmesg | grep snd: [3.019164] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [3.047505] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC255: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker [3.047508] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [3.047510] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 (0x21/0x0/0x0/0x0/0x0) [3.047511] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:dig-out=0x1e/0x0 [3.047512] snd_hda_codec_realtek hdaudioC0D0:inputs: [3.047514] snd_hda_codec_realtek hdaudioC0D0: Mic=0x1a One problem is that I can't find any model options (options snd-hda- intel model=something) or other parameters for the card's model (ALC255), I suppose this issue is relatively new. /Dennis --- ApportVersion: 2.19.2-0ubuntu6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dennis 1180 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2015-11-11 (23 days ago) InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151110) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Tags: xenial Uname: Linux 4.2.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/25/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.02 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire VN7-792G dmi.board.vendor: Acer dmi.board.version: V1.02 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.02 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.02:bd09/25/2015:svnAcer:pnAspireVN7-792G:pvrV1.02:rvnAcer:rnAspireVN7-792G:rvrV1.02:cvnAcer:ct10:cvrV1.02: dmi.product.name: Aspire VN7-792G dmi.product.version: V1.02 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1523100/+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 1861408] Re: firefox apparmor messages
to
"
i added w to
owner @{HOME}/.{,cache/}fontconfig/** mrl,
"
:
cboltz said in apparmor irc channel:
I'd recommend _not_ to allow writing to ~/.cache/fontconfig/ because apps could
in theory poison that cache
actually we recently (intentionally) removed write permissions in
abstractions/fonts
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1861408
Title:
firefox apparmor messages
Status in apparmor package in Ubuntu:
New
Status in firefox package in Ubuntu:
New
Bug description:
firefox version 72.0.1 64 bit, 72.0.1+linuxmint1+tricia , linux mint
19.3.
i see there is newer ubuntu version in
https://www.ubuntuupdates.org/package/ubuntu_mozilla_security/bionic/main/base/firefox
, 72.0.2+build1-0ubuntu0.18.04.1 , but its changes are not for
apparmor.
i have not found a page for firefox bugs in linux mint sites, so i
belive i should report here. but i have also asked about that in linux
mint's irc and then github.
i have enabled apparmor for firefox and see these types of messages in
syslog:
Jan 28 18:43:33 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.111' (uid=1000
pid=1922 comm="/usr/lib/firefox/firefox " label="unconfined")
Jan 28 18:44:36 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5525.077960] audit: type=1400 audit(1580226276.440:27):
apparmor="DENIED" operation="capable"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}" pid=15948
comm="firefox" capability=21 capname="sys_admin"
Jan 28 18:44:37 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5526.471731] audit: type=1107 audit(1580226277.832:28): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/RealtimeKit1"
interface="org.freedesktop.DBus.Properties" member="Get" mask="send"
name="org.freedesktop.RealtimeKit1" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1320
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/Daemon" interface="org.gtk.vfs.Daemon"
member="ListMonitorImplementations" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/Private/RemoteVolumeMonitor"
interface="org.gtk.Private.RemoteVolumeMonitor" member="IsSupported"
mask="send" name=":1.35" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1385
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="ListMounts2" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:47 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/org/gtk/vfs/mounttracker" interface="org.gtk.vfs.MountTracker"
member="LookupMount" mask="send" name=":1.10" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1262
peer_label="unconfined"
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[735]:
[system] Activating via systemd: service
name='org.freedesktop.hostname1' unit='dbus-
org.freedesktop.hostname1.service' requested by ':1.119' (uid=1000
pid=15948 comm="/usr/lib/firefox/firefox "
label="/usr/lib/firefox/firefox{,*[^s][^h]} (enforce)")
Jan 28 18:44:48 dinar-HP-Pavilion-g7-Notebook-PC kernel: [
5536.783313] audit: type=1107 audit(1580226288.143:34): pid=735
uid=103 auid=4294967295 ses=4294967295 msg='apparmor="DENIED"
operation="dbus_method_call" bus="system"
path="/org/freedesktop/hostname1"
interface="org.freedesktop.DBus.Properties" member="GetAll"
mask="send" name=":1.120" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=16177
peer_label="unconfined"
Jan 28 18:45:02 dinar-HP-Pavilion-g7-Notebook-PC dbus-daemon[1181]:
apparmor="DENIED" operation="dbus_method_call" bus="session"
path="/ca/desrt/dconf/Writer/user" interface="ca.desrt.dconf.Writer"
member="Change" mask="send" name="ca.desrt.dconf" pid=15948
label="/usr/lib/firefox/firefox{,*[^s][^h]}" peer_pid=1370
peer_label="unconfined"
Jan 28 21:51:30 dinar-HP-Pavilion-g7-Notebook-PC kernel:
[10131.880788] audit: type=1400 audit(1580237490.777:123):
apparmor="DENIED" operation="open"
profile="/usr/lib/firefox/firefox{,*[^s][^h]}"
[Desktop-packages] [Bug 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
It seems that the issue is connected with Sane backend (pixma). Please check on bug list, if the issue was already reported: https://gitlab.com/sane-project/backends/-/issues You could also report the issue to mailing list: https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/sane-devel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1759889 Title: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw Status in simple-scan package in Ubuntu: Incomplete Bug description: Hello, When scanning multiple pages from a Canon mf244dw via the LAN I only get the first page scanned, then an error message. Running "simple-scan -d" and looking at the output I see the following: [+123.87s] DEBUG: scanner.vala:1321: sane_read (7651) -> (SANE_STATUS_CANCELLED, 0) [+123.87s] WARNING: scanner.vala:1337: Unable to read frame from device: Operation was cancelled [+123.87s] DEBUG: scanner.vala:768: sane_cancel () [+123.87s] DEBUG: scanner.vala:771: sane_close () I do notice that the scanner is already feeding in the second page before the first page has completely rendered on screen - perhaps it's going too fast? Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1759889/+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 1873686] Re: cut action fails to save content to clipboard or fails to use in in paste
** Package changed: ubuntu => libreoffice (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1873686 Title: cut action fails to save content to clipboard or fails to use in in paste Status in libreoffice package in Ubuntu: New Bug description: I tried to report the bug as Libreoffice bug, but they seem to ignore it as of problem in ubuntu. I was advised to report this for ubuntu beta 20.04. Bugzilla Bug 132213 shows what I was able to describe at the time. I dis some 50 cut and paste actions while working with LibreOffice calc document. 3 times cut operation succeeded but paste result was what was cut and already pasted during previous cut and paste sequence. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1873686/+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 1873686] [NEW] cut action fails to save content to clipboard or fails to use in in paste
You have been subscribed to a public bug: I tried to report the bug as Libreoffice bug, but they seem to ignore it as of problem in ubuntu. I was advised to report this for ubuntu beta 20.04. Bugzilla Bug 132213 shows what I was able to describe at the time. I dis some 50 cut and paste actions while working with LibreOffice calc document. 3 times cut operation succeeded but paste result was what was cut and already pasted during previous cut and paste sequence. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New -- cut action fails to save content to clipboard or fails to use in in paste https://bugs.launchpad.net/bugs/1873686 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1873692] [NEW] Do Not Disturb setting does not persist across login sessions
Public bug reported: Description:Ubuntu 20.04 LTS Release:20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Selecting do not disturb from settings does not persist across login sessions. What I did - Set Do Not Disturb in settings or from top bar to prevent pop-up notification banners from appearing, which it does. - logout and log back in - expect pop-up notifications to continue to be blocked and only displayed in the top bar What happens: - Do Not Disturb is reset to disabled on each new login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 14:42:49 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-24 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago) ** Affects: gnome-control-center (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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1873692 Title: Do Not Disturb setting does not persist across login sessions Status in gnome-control-center package in Ubuntu: New Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.1-1ubuntu5 Candidate: 1:3.36.1-1ubuntu5 Version table: *** 1:3.36.1-1ubuntu5 500 500 http://ca.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Selecting do not disturb from settings does not persist across login sessions. What I did - Set Do Not Disturb in settings or from top bar to prevent pop-up notification banners from appearing, which it does. - logout and log back in - expect pop-up notifications to continue to be blocked and only displayed in the top bar What happens: - Do Not Disturb is reset to disabled on each new login ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 14:42:49 2020 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2019-07-24 (270 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to focal on 2020-03-19 (30 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873692/+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 1873638] Re: Weird close button in settings
On 2020-04-19 19:28, Dragosh wrote: > From my point on view the version of gnome-control-center can be > determined from the screenshot, That shows the upstream version of some of the many GNOME packages (don't know which one). Besides, there are several non-trivial gnome- control-center patches in Ubuntu, so what does this command output: dpkg-query -W gnome-control-center With desktop environment I meant to ask if you possibly are on one of the Ubuntu flavors. I think Ubuntu Budgie uses gnome-control-center by default. Yes, knowing how to reproduce is always useful, of course. (But I still can't reproduce it.) You seem to be using some other theme but the default Yaru one. Wondering if it may be a theme issue. -- 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/1873638 Title: Weird close button in settings Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Unexpected button location on settings. Check image as screenshot attachment . OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question show be how to reproduce? To switch button on the left side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+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 1873685] Re: Wallpaper not updated to 20.04 default after upgrade
Attached is the apport.lubuntu-artwork file ** Attachment added: "apport.lubuntu-artwork.dnc1a_x_.apport" https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1873685/+attachment/5356851/+files/apport.lubuntu-artwork.dnc1a_x_.apport -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1873685 Title: Wallpaper not updated to 20.04 default after upgrade Status in Lubuntu Artwork: New Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Wallpaper not updated to 20.04 default after upgrade. After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04 the desktop still showing the 19.10 default wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-wallpapers-focal (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Apr 19 17:44:01 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) SourcePackage: ubuntu-wallpapers UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-artwork/+bug/1873685/+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 1873685] Re: Wallpaper not updated to 20.04 default after upgrade
** Also affects: lubuntu-artwork Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1873685 Title: Wallpaper not updated to 20.04 default after upgrade Status in Lubuntu Artwork: New Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Wallpaper not updated to 20.04 default after upgrade. After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04 the desktop still showing the 19.10 default wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-wallpapers-focal (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Apr 19 17:44:01 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) SourcePackage: ubuntu-wallpapers UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/lubuntu-artwork/+bug/1873685/+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 1873685] Re: Wallpaper not updated to 20.04 default after upgrade
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1873685 ** Tags added: iso-testing -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1873685 Title: Wallpaper not updated to 20.04 default after upgrade Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Wallpaper not updated to 20.04 default after upgrade. After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04 the desktop still showing the 19.10 default wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-wallpapers-focal (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Apr 19 17:44:01 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) SourcePackage: ubuntu-wallpapers UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1873685/+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 1873685] [NEW] Wallpaper not updated to 20.04 default after upgrade
Public bug reported: Wallpaper not updated to 20.04 default after upgrade. After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04 the desktop still showing the 19.10 default wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-wallpapers-focal (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Apr 19 17:44:01 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) SourcePackage: ubuntu-wallpapers UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago) ** Affects: ubuntu-wallpapers (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 ubuntu-wallpapers in Ubuntu. https://bugs.launchpad.net/bugs/1873685 Title: Wallpaper not updated to 20.04 default after upgrade Status in ubuntu-wallpapers package in Ubuntu: New Bug description: Wallpaper not updated to 20.04 default after upgrade. After GUI upgrade from Lubuntu version 19.10 to Lubuntu Focal 20.04 the desktop still showing the 19.10 default wallpaper. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-wallpapers-focal (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: LXQt Date: Sun Apr 19 17:44:01 2020 InstallationDate: Installed on 2020-04-19 (0 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) SourcePackage: ubuntu-wallpapers UpgradeStatus: Upgraded to focal on 2020-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1873685/+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 1873638] Re: Weird close button in settings
>From my point on view the version of gnome-control-center can be determined from the screenshot, the gnome-control-center 3.36.1 as the version of gnome / the screenshot from is settings and we OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question show be how to reproduce? To switch button on the left side. -- 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/1873638 Title: Weird close button in settings Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Unexpected button location on settings. Check image as screenshot attachment . OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question show be how to reproduce? To switch button on the left side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+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 1873638] Re: Weird close button in settings
OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question show be how to reproduce? To switch button on the left side. ** Description changed: Unexpected button location on settings. Check image as screenshot attachment . + + OS: Ubuntu 20.04 + OS Type: 64-bit + Gnome: 3.36.1 + Windows System: X11 / Xorg + + May the question show be how to reproduce? To switch button on the left + side. -- 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/1873638 Title: Weird close button in settings Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Unexpected button location on settings. Check image as screenshot attachment . OS: Ubuntu 20.04 OS Type: 64-bit Gnome: 3.36.1 Windows System: X11 / Xorg May the question show be how to reproduce? To switch button on the left side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
Did a Fresh Install today, and Selected the option to automatically install proprietary drivers, Something changed and my Installation Failed, I got a message saying that there was already a bug for that, I followed along and updated my situation in that bug report, because why not, It is just a 2 Minute Job. So this time around I changed the kernel parameters before installing Nvidia Drivers using the ubuntu-drivers autoinstall command. I edited by /etc/default/grub and I added nvidia-drm.modeset=1, Did not remove splash or any other parameters. I then ran sudo ubuntu-drivers autoinstall and waited for that to finish, Once done, I ran sudo update-grub. Then rebooted. This way I now have the flicker free boot/Animation and I can get into the desktop without any issues, GDM autologin works absolutely fine. I rebooted again just to be sure, and things stayed good. I wanted to update here so others can benefit while the bug is addressed. This is a working solution for me. I have a GTX 1070 CPU. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. Status in gdm3 package in Ubuntu: Confirmed Status in gnome-session package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-390 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Incomplete Status in gdm3 source package in Eoan: Confirmed Status in gnome-session source package in Eoan: Confirmed Status in nvidia-graphics-drivers-435 source package in Eoan: Confirmed Bug description: I just updated to the Ubuntu 19.10 beta. After boot, I'm shown the GDM login screen (which I shouldn't; I have auto login enabled), and logging in just takes me back to the same user selection screen even though the password is correct. If I switch to a TTY and run `sudo pkill gnome-session-binary`, logging in through GDM starts working again. I should add that the do-release-upgrade was rocky; I did it in a terminal from within gnome, went away for a while, and when I returned, I just saw an Ubuntu 19.10 in a TTY. I was able to do `sudo dpkg --configure -a` and complete the upgrade, but I don't know if something's still messed up due to that. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1) ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Sep 28 19:55:42 2019 DistUpgraded: 2019-09-28 18:35:15,142 INFO cache.commit() DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP102 [GeForce GTX 1080 Ti] [10de:1b06] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP102 [GeForce GTX 1080 Ti] [1043:85e4] InstallationDate: Installed on 2019-09-14 (13 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: MSI MS-7A67 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=04974c80-e732-49b6-8148-c3dce7c02a25 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to eoan on 2019-09-28 (0 days ago) dmi.bios.date: 01/25/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.60 dmi.board.asset.tag: Default string dmi.board.name: H270I GAMING PRO AC (MS-7A67) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.60:bd01/25/2018:svnMSI:pnMS-7A67:pvr1.0:rvnMSI:rnH270IGAMINGPROAC(MS-7A67):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A67 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A
[Desktop-packages] [Bug 1873676] [NEW] Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory
Public bug reported: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install xscreensaver package 3. Launch `xscreensaver-demo` Expected results: * no warnings Actual results: * there are warnings: ``` $ xscreensaver-demo (xscreensaver-demo:6824): libglade-WARNING **: 19:47:51.804: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory xscreensaver-demo: 19:47:52: XScreenSaver-debug: Name com.canonical.AppMenu.Registrar does not exist on the session bus ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xscreensaver 5.42+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Apr 19 19:49:14 2020 InstallationDate: Installed on 2020-04-12 (6 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200412) SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libgnomeui (Ubuntu) Importance: Undecided Status: New ** Affects: xscreensaver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Also affects: libgnomeui (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgnomeui in Ubuntu. https://bugs.launchpad.net/bugs/1873676 Title: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory Status in libgnomeui package in Ubuntu: New Status in xscreensaver package in Ubuntu: New Bug description: Steps to reproduce: 1. Have Ubuntu 20.04 LTS installed 2. Install xscreensaver package 3. Launch `xscreensaver-demo` Expected results: * no warnings Actual results: * there are warnings: ``` $ xscreensaver-demo (xscreensaver-demo:6824): libglade-WARNING **: 19:47:51.804: Could not load support for `gnome': libgnome.so: cannot open shared object file: No such file or directory xscreensaver-demo: 19:47:52: XScreenSaver-debug: Name com.canonical.AppMenu.Registrar does not exist on the session bus ``` ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xscreensaver 5.42+dfsg1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Sun Apr 19 19:49:14 2020 InstallationDate: Installed on 2020-04-12 (6 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Beta amd64 (20200412) SourcePackage: xscreensaver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnomeui/+bug/1873676/+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 1759889] Re: Simple scan multiple page issue - Unable to read frame from device - Canon mf244dw
Very similar failure observed - the 1st page scans, but the 2nd fails. Errors in logs are different however: $ SANE_DEBUG_PIXMA=3 xsane [sanei_debug] Setting debug level of pixma to 3. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.37 [pixma] Scanner model found: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_find_scanners() found 1 devices (xsane:6919): Gdk-CRITICAL **: 12:08:35.630: IA__gdk_drawable_unref: assertion 'GDK_IS_DRAWABLE (drawable)' failed (xsane:6919): Gdk-CRITICAL **: 12:08:35.630: IA__gdk_drawable_unref: assertion 'GDK_IS_DRAWABLE (drawable)' failed [pixma] Scanner model found: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_open(): Canon i-SENSYS MF240 Series [pixma] *iclass_open* This is a generation 2 scanner. * [pixma] Trying to clear the interrupt buffer... [pixma] no packets in buffer [xsane] ERROR: xsane-startimage not found. Looks like xsane is not installed correct. [pixma] Reader task started [pixma] Reader task id=140132160792320 (threaded) [pixma] [pixma] pixma_scan(): start [pixma] line_size=7680 image_size=32256000 channels=3 depth=8 [pixma] dpi=300x300 offset=(0,0) dimension=2560x4200 [pixma] gamma_table=0x55deb339ae38 source=1 [pixma] threshold=127 threshold_curve=0 [pixma] adf-wait=0 [pixma] ADF page count: 0 [pixma] Setting non-blocking mode [pixma] raw_width = 2560 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_scan* start scanning * [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_finish_scan* wait for next page from ADF * [pixma] WARNING:image size mismatches [pixma] 32256000 expected (4200 lines) but 25489920 received (3319 lines) [pixma] pixma_read_image(): completed (underrun detected) [pixma] Reader task terminated [pixma] pixma_close(): Canon i-SENSYS MF240 Series vs $ SANE_DEBUG_PIXMA=3 simple-scan [sanei_debug] Setting debug level of pixma to 3. [pixma] pixma is compiled with pthread support. [pixma] pixma version 0.17.37 [pixma] Scanner model found: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_find_scanners() found 1 devices [pixma] Scanner model found: Name MF240(Canon i-SENSYS MF240 Series) matches Canon MF240 Series [pixma] pixma_collect_devices() found Canon i-SENSYS MF240 Series at mfnp://canon-mfc.lan:8610/timeout=1000 [pixma] pixma_open(): Canon i-SENSYS MF240 Series [pixma] *iclass_open* This is a generation 2 scanner. * [pixma] Trying to clear the interrupt buffer... [pixma] no packets in buffer [pixma] Reader task started [pixma] Reader task id=140424282892032 (threaded) [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] [pixma] pixma_scan(): start [pixma] line_size=1280 image_size=2112000 channels=1 depth=8 [pixma] dpi=150x150 offset=(0,0) dimension=1275x1650 [pixma] gamma_table=0x7fb6fc28db88 source=1 [pixma] threshold=127 threshold_curve=0 [pixma] adf-wait=0 [pixma] ADF page count: 0 [pixma] raw_width = 1280 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_scan* start scanning * [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] *sane_read* Warning: padding may cause incomplete scan results [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] Current status: paper=0x00 cal=1 lamp=0 [pixma] *iclass_finish_scan* wait for next page from ADF * [pixma] pixma_read_image():completed [pixma] Reader task
[Desktop-packages] [Bug 1660121] Re: LightDM can't use the user background on Mate
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1660121 Title: LightDM can't use the user background on Mate Status in Ubuntu MATE: New Status in lightdm package in Ubuntu: Confirmed Bug description: Using Ubuntu Mate 16.10 (the issue appears too on 16.04 and 17.04 alpha 2). On Mate, the LightDM Gtk Greeter can't use the user background. It works fine on other DEs like Xfce. From what I understand, LightDM and/or the Gkt greeter (not sure which one handles the background) gets the background path from Gsettings, so I assume it can't find the one from Mate, which stores it in "org.mate.background picture-filename". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1660121/+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 1873413] Re: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM
Hi Daniel, > Since your setup only uses gnome-shell in the host and not the guest it Host is KDE Plasma, guest is GNOME => I have problems with clipboard when I close virt-manager or shutdown the guest => no problems So if I remove GNOME from the equation, then it's OK. -- 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/1873413 Title: hanging clipboard when CTRL+X / CTRL+V text between two Ubuntu Focal VMs or between laptop and VM Status in gnome-shell package in Ubuntu: Incomplete Bug description: Could you please try install: - Kubuntu 20.04 Focal desktop on bare metal (laptop) - Upgrade all packages - Install virtualization as usually (qemu-kvm, libvirt, virt-manager) - Install Ubuntu 20.04 inside a VM - upgrade all packages in the VM - Start copying (CTRL+X, CTRL+V) plain text between the Kubuntu on laptop and Ubuntu inside VM? Doesn't take too long - doesn't need to much testing. After a couple of trials, the clipboard will hang and you loose the text in clipboard... I don't remember such issues in past. Copying worked fine when I used virt-manager a couple of years ago. Thank you all great people in Canonical for Ubuntu. Ian ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 17 04:43:59 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-16 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200315) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu2 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/1873413/+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 1849787] Re: The dock is shown in front of full screen windows since 19.10
seems to be fixed for me with xscreensaver shows fullscreen again and does not fight with the dock anymore on 19/4/2020 -- 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/1849787 Title: The dock is shown in front of full screen windows since 19.10 Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: See attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1849787/+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
I have the same Problem on Ubuntu 19.10 with a Samsung Galaxy S10 (SM- G973F) Kernel: 5.3.0-46-generic x86_64 Architecture: arm64 Desktop: Gnome 3.34.2 gvfs: amd64 1.42.1-1ubuntu1 -- 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 1873263] Re: Users home directory isn’t created or modified on useradd/adduser/usermod/g-c-c
This bug was fixed in the package adduser - 3.118ubuntu2 --- adduser (3.118ubuntu2) focal; urgency=medium * Add support for ZFS home directories: - Home directories are created as ZFS dataset if zsysctl is installed. If the command is not installed or fails, the user will be created as usual without a dedicated dataset (LP: #1873263) -- Jean-Baptiste Lallement Thu, 16 Apr 2020 16:12:53 +0200 ** Changed in: adduser (Ubuntu) Status: Confirmed => Fix Released -- 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/1873263 Title: Users home directory isn’t created or modified on useradd/adduser/usermod/g-c-c Status in adduser package in Ubuntu: Fix Released Status in shadow package in Ubuntu: Fix Released Status in zsys package in Ubuntu: Fix Released Bug description: There is no more zsys integration for this part of the stack. Fix regression from disco due to useradd merge with debian. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1873263/+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 1873638] Re: Weird close button in settings
That's weird. For me the close button is in the top right corner as expected. Which version of gnome-control-center are you using? Which desktop environment? ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- 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/1873638 Title: Weird close button in settings Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Unexpected button location on settings. Check image as screenshot attachment . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+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 1871019] Re: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work)
Sebastien, I can confirm that the updated package fixes the problem. Thanks for your work! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1871019 Title: Nextcloud account added to Online Accounts does not populate Calendar apps (WebDAV file sharing does work) Status in gnome-online-accounts: Unknown Status in evolution-data-server package in Ubuntu: Fix Released Bug description: My Nextcloud server was working fine with previous versions of Ubuntu, but on the 20.04 daily when I add my Nextcloud account it does not populate my Calendars or todo lists. It does give me file access via WebDAV. Server is working fine as far as I'm aware. Going to Settings -> Administration - Overview shows me any configuration issues it can detect, currently the only error there is related to background job execution (which is only relevant to the News app if I'm not mistaken). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-online-accounts 3.36.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 5 23:59:55 2020 InstallationDate: Installed on 2020-04-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1871019/+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 1873321] Re: The Show Applications button should be clickable in the corner and along its bottom edge
** Changed in: dash-to-dock Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1873321 Title: The Show Applications button should be clickable in the corner and along its bottom edge Status in Dash to dock: New Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: After one of the recent updates, clicking the Show Applications button in the very corner of the screen and at its bottom edge doesn't work. This bug applies in the cases of left and right positions of the dock and there is no this bug in the case of bottom position. This issue is very annoying since the mouse pointer runs at the very corner of the screen in vast majority of cases as you intent to press the Show Apps button. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 67ubuntu20.04.3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 20:34:32 2020 InstallationDate: Installed on 2019-04-25 (356 days ago) InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190425) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1873321/+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 1873650] [NEW] package nvidia-340 (not installed) failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/71-nvidia.rules », qui appartient aussi au paquet
Public bug reported: I applied modification in xserver nvidia panel: video settings: quality to high performances. I saved new configuration. .conf file has been updated after reboot no connexion with Xserver, graphical issue. I booted in recovery mode : connect to internet network, used root way to replace video drivers nvidia by video drivers xserver-xorg-driver-nouveau Graphical Ubuntu mode is back now. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Apr 19 03:48:29 2020 ErrorMessage: tentative de remplacement de « /lib/udev/rules.d/71-nvidia.rules », qui appartient aussi au paquet nvidia-kernel-common-390 390.132-0ubuntu2 InstallationDate: Installed on 2018-11-16 (519 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/71-nvidia.rules », qui appartient aussi au paquet nvidia-kernel-common-390 390.132-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1873650 Title: package nvidia-340 (not installed) failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/71-nvidia.rules », qui appartient aussi au paquet nvidia-kernel-common-390 390.132-0ubuntu2 Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: I applied modification in xserver nvidia panel: video settings: quality to high performances. I saved new configuration. .conf file has been updated after reboot no connexion with Xserver, graphical issue. I booted in recovery mode : connect to internet network, used root way to replace video drivers nvidia by video drivers xserver-xorg-driver-nouveau Graphical Ubuntu mode is back now. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 (not installed) ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Apr 19 03:48:29 2020 ErrorMessage: tentative de remplacement de « /lib/udev/rules.d/71-nvidia.rules », qui appartient aussi au paquet nvidia-kernel-common-390 390.132-0ubuntu2 InstallationDate: Installed on 2018-11-16 (519 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: nvidia-graphics-drivers-340 Title: package nvidia-340 (not installed) failed to install/upgrade: tentative de remplacement de « /lib/udev/rules.d/71-nvidia.rules », qui appartient aussi au paquet nvidia-kernel-common-390 390.132-0ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1873650/+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 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
The GNOME issue is completely separate from the problem of "triggering layout change on press", as GNOME does not use the kxb behavior at all - it actually disables any options set using setxkbmap - instead it listens to keyboard events and implements its own custom behavior that mimics Mac OS. Note that with the current release (19.10, but also tested 20.04) on Kubuntu with xserver 1.20 that *does not* include the patch from freedesktop.org bug 865, layout switching works on release - as requested. I'm not sure what introduced this behavior and whether it is in X.org or in KDE. -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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
It's half fixed, but NOT for my bug posting (I am on Ubuntu 18.04 and compilation for it is MISSING) -- 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: Fix Released 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 36812] Re: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts
I am running ubuntu 19.10 with recent gnome 3 and did not find any working solution to switch layout on Ctrl +Shift shortcuts key release. Eventualy i wrote a dirty workoround to fit my needs. https://gitlab.com/softkot/gnome3_xinput_layout_switch -- 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/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts Status in gnome-control-center: Unknown Status in X.Org X server: New Status in gnome-control-center package in Ubuntu: Invalid Status in xorg-server package in Ubuntu: Confirmed Bug description: This is a bug about shortcuts mapped to combinations which include each other. For example, if we have Ctrl+Shift (for keyboard layout) and Ctrl+Shift+N (to open a new terminal), then we are practically unable to use the second shortcut; this is what happens: Ctrl press (nothing happens) Shift press (keyboard layout change) N (a simple N appears, since a shortcut has already fired) The expected behavior is to fire shortcuts on the release (not on press) of the special keys (ctrl,shift,alt, etc) which is also how Windows behave. This is a serious problem for bilingual layouts, typically using Alt+Shift or Ctrl+Shift for keyboard layout change. For users being affected by this problem, the easiest solution for now is to add this PPA in your repositories: https://launchpad.net/~oded-geek/+archive/xorg-patches Practical summary of this bug for ubuntu developers (since reading 120 comments is impractical for most): This problem is a really old (since 2004) issue of the xkb part of xorg; the main discussion was made upstream in freedesktop-bugs #865. There has been a patch from Ilya Murav'jov for upstream (#55), and attached here (#61). Upstream xorg has refused to apply the patch, mainly because it "explicitly contradicts the (xkb) spec" (#84, #91). This patch has been reported to work for many people without any problems, and there is also a PPA by Oded Arbel (#95) where he maintains a patched version of the ubuntu xorg. The proper resolution of this bug would be to apply this patch to the upstream xorg, or at minimum to the official ubuntu xorg package. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+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 571229] Re: Menus are not shown when accessed by keys in full screen mode, but they work
** Bug watch added: Mozilla Bugzilla #648504 https://bugzilla.mozilla.org/show_bug.cgi?id=648504 ** Bug watch added: Mozilla Bugzilla #1192655 https://bugzilla.mozilla.org/show_bug.cgi?id=1192655 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/571229 Title: Menus are not shown when accessed by keys in full screen mode, but they work Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in firefox-3.5 package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 marcingo@idevele:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 9.10 Release: 9.10 Codename: karmic marcingo@idevele:~$ apt-cache policy firefox firefox: Installed: 3.5.9+nobinonly-0ubuntu0.9.10.1 Candidate: 3.5.9+nobinonly-0ubuntu0.9.10.1 Version table: *** 3.5.9+nobinonly-0ubuntu0.9.10.1 0 500 http://hu.archive.ubuntu.com karmic-updates/main Packages 500 http://security.ubuntu.com karmic-security/main Packages 100 /var/lib/dpkg/status 3.5.3+build1+nobinonly-0ubuntu6 0 500 http://hu.archive.ubuntu.com karmic/main Packages Ubuntu Netbook Remix Normal mode: I press Alt-F. The File menu appears. I can see that the key for print preview is V as it is underlined. I press V. The print preview appears. Fullscreen mode: I press Alt-F. The File menu does NOT appear. I press V just in case. The print preview appears. Always reproducible. Expected Results: The menu should be displayed upon the corresponding keypress in fullscreen mode as well. It is worst with the Bookmarks, because they change and by the time one memorizes a keystroke combination, a new bookmark or submenu will likely make it invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/571229/+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 571229]
I'd suggest this should be closed as a duplicate of bug 1192655. However, there is another bug blocked on this one and I don't really know what the status of that is, so I'm not closing this myself. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/571229 Title: Menus are not shown when accessed by keys in full screen mode, but they work Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in firefox-3.5 package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 marcingo@idevele:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 9.10 Release: 9.10 Codename: karmic marcingo@idevele:~$ apt-cache policy firefox firefox: Installed: 3.5.9+nobinonly-0ubuntu0.9.10.1 Candidate: 3.5.9+nobinonly-0ubuntu0.9.10.1 Version table: *** 3.5.9+nobinonly-0ubuntu0.9.10.1 0 500 http://hu.archive.ubuntu.com karmic-updates/main Packages 500 http://security.ubuntu.com karmic-security/main Packages 100 /var/lib/dpkg/status 3.5.3+build1+nobinonly-0ubuntu6 0 500 http://hu.archive.ubuntu.com karmic/main Packages Ubuntu Netbook Remix Normal mode: I press Alt-F. The File menu appears. I can see that the key for print preview is V as it is underlined. I press V. The print preview appears. Fullscreen mode: I press Alt-F. The File menu does NOT appear. I press V just in case. The print preview appears. Always reproducible. Expected Results: The menu should be displayed upon the corresponding keypress in fullscreen mode as well. It is worst with the Bookmarks, because they change and by the time one memorizes a keystroke combination, a new bookmark or submenu will likely make it invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/571229/+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 571229]
So, in fact this bug has been fixed by the fix for https://bugzilla.mozilla.org/show_bug.cgi?id=1192655 -- pressing Alt plus a letter when in fullscreen mode no longer opens hidden menus, and thus pressing F11 to get out of fullscreen mode will always work. The desire of the other bug report (https://bugzilla.mozilla.org/show_bug.cgi?id=648504) is that Alt+letter should open the requested menu *visibly*, so that the menus can be used even when the menu bar itself is hidden. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/571229 Title: Menus are not shown when accessed by keys in full screen mode, but they work Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in firefox-3.5 package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 marcingo@idevele:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 9.10 Release: 9.10 Codename: karmic marcingo@idevele:~$ apt-cache policy firefox firefox: Installed: 3.5.9+nobinonly-0ubuntu0.9.10.1 Candidate: 3.5.9+nobinonly-0ubuntu0.9.10.1 Version table: *** 3.5.9+nobinonly-0ubuntu0.9.10.1 0 500 http://hu.archive.ubuntu.com karmic-updates/main Packages 500 http://security.ubuntu.com karmic-security/main Packages 100 /var/lib/dpkg/status 3.5.3+build1+nobinonly-0ubuntu6 0 500 http://hu.archive.ubuntu.com karmic/main Packages Ubuntu Netbook Remix Normal mode: I press Alt-F. The File menu appears. I can see that the key for print preview is V as it is underlined. I press V. The print preview appears. Fullscreen mode: I press Alt-F. The File menu does NOT appear. I press V just in case. The print preview appears. Always reproducible. Expected Results: The menu should be displayed upon the corresponding keypress in fullscreen mode as well. It is worst with the Bookmarks, because they change and by the time one memorizes a keystroke combination, a new bookmark or submenu will likely make it invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/571229/+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 571229]
Related/duplicate of https://bugzilla.mozilla.org/show_bug.cgi?id=648504 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/571229 Title: Menus are not shown when accessed by keys in full screen mode, but they work Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Status in firefox-3.5 package in Ubuntu: Triaged Bug description: Binary package hint: firefox-3.0 marcingo@idevele:~$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 9.10 Release: 9.10 Codename: karmic marcingo@idevele:~$ apt-cache policy firefox firefox: Installed: 3.5.9+nobinonly-0ubuntu0.9.10.1 Candidate: 3.5.9+nobinonly-0ubuntu0.9.10.1 Version table: *** 3.5.9+nobinonly-0ubuntu0.9.10.1 0 500 http://hu.archive.ubuntu.com karmic-updates/main Packages 500 http://security.ubuntu.com karmic-security/main Packages 100 /var/lib/dpkg/status 3.5.3+build1+nobinonly-0ubuntu6 0 500 http://hu.archive.ubuntu.com karmic/main Packages Ubuntu Netbook Remix Normal mode: I press Alt-F. The File menu appears. I can see that the key for print preview is V as it is underlined. I press V. The print preview appears. Fullscreen mode: I press Alt-F. The File menu does NOT appear. I press V just in case. The print preview appears. Always reproducible. Expected Results: The menu should be displayed upon the corresponding keypress in fullscreen mode as well. It is worst with the Bookmarks, because they change and by the time one memorizes a keystroke combination, a new bookmark or submenu will likely make it invalid. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/571229/+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 1873642] Re: F1 help NOT working
*** This bug is a duplicate of bug 1869561 *** https://bugs.launchpad.net/bugs/1869561 I can confirm this on both Kubuntu and Ubuntu (20.04). ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed ** Tags added: focal ** This bug has been marked a duplicate of bug 1869561 Libreoffice Help does not work -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1873642 Title: F1 help NOT working Status in libreoffice package in Ubuntu: Confirmed Bug description: Hi developers, I'm using Kubuntu 20.04 beta with default installation and updates till today April 19. I have to report a bug about F1 help key when pressed or help voice in menu. I receive the error "Object not accessible. The object cannot be accessed due to insufficient user rights." I tried both as user and root with the same result. Hope you solve this bug soon. Thanks and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1873642/+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 1873642] [NEW] F1 help NOT working
Public bug reported: Hi developers, I'm using Kubuntu 20.04 beta with default installation and updates till today April 19. I have to report a bug about F1 help key when pressed or help voice in menu. I receive the error "Object not accessible. The object cannot be accessed due to insufficient user rights." I tried both as user and root with the same result. Hope you solve this bug soon. Thanks and have a nice day. ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Screenshot_20200418_031928.jpg" https://bugs.launchpad.net/bugs/1873642/+attachment/5356710/+files/Screenshot_20200418_031928.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1873642 Title: F1 help NOT working Status in libreoffice package in Ubuntu: New Bug description: Hi developers, I'm using Kubuntu 20.04 beta with default installation and updates till today April 19. I have to report a bug about F1 help key when pressed or help voice in menu. I receive the error "Object not accessible. The object cannot be accessed due to insufficient user rights." I tried both as user and root with the same result. Hope you solve this bug soon. Thanks and have a nice day. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1873642/+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 1873638] Re: Weird close button in settings
** Package changed: ubuntu => gnome-control-center (Ubuntu) ** Tags added: focal -- 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/1873638 Title: Weird close button in settings Status in gnome-control-center package in Ubuntu: New Bug description: Unexpected button location on settings. Check image as screenshot attachment . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1873638/+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 1873638] [NEW] Weird close button in settings
You have been subscribed to a public bug: Unexpected button location on settings. Check image as screenshot attachment . ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Tags: settings -- Weird close button in settings https://bugs.launchpad.net/bugs/1873638 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
I ran the software updater and noticed that it installed a new pulseaudio: pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 After rebooting the system, I'm running this version. You will be happy to learn that pulseaudio doesn't crash with this version, and it shows sound devices in Settings -> Sound, and the speaker test actually plays (once I picked Line Out rather than the default which was Speaker -- my chassis doesn't have a speaker). I am even able to play mp3 and flac music in Totem. I think it's fixed! Thank you! -- 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/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+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 1873630] Re: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting.
I ran the software updater and noticed that it installed a new pulseaudio: pulseaudio: Installed: 1:13.99.1-1ubuntu3 Candidate: 1:13.99.1-1ubuntu3 After rebooting the system, I'm running this version. You will be happy to learn that pulseaudio doesn't crash with this version, and it shows sound devices in Settings -> Sound, and the speaker test actually plays (once I picked Line Out rather than the default which was Speaker -- my chassis doesn't have a speaker). I am even able to play mp3 and flac music in Totem. I think it's fixed! Thank you! -- 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/1873630 Title: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa- ucm.c:2158, function device_add_hw_mute_jack(). Aborting. Status in pulseaudio package in Ubuntu: New Bug description: I have a Gigabyte motherboard that gives pulseaudio fits in Ubuntu 20.04 beta. (It worked fine in 18.04.4 LTS.) It produced pulseaudio crashes with bug #1870833 until a proposed fix was brought in from upstream: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu2 However, that did not actually make pulseaudio work; now it throws this error and aborts: Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. It was suggested in the previous bug that I should open a new bug for this. Here you are! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 00:25:26 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1873630/+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 1873038] Re: Merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main)
This bug was fixed in the package gtk+3.0 - 3.24.18-1ubuntu1 --- gtk+3.0 (3.24.18-1ubuntu1) focal; urgency=medium * Update to the current stable version (based on Debian) (lp: #1873038) -- Sebastien Bacher Thu, 16 Apr 2020 11:23:10 +0200 ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1873038 Title: Merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main) Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Please merge gtk+3.0 3.24.18-1 (main) from Debian unstable (main) Sorry, I can't work on this merge myself. It fixes bugs in Wayland. https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS Overview of Changes in GTK+ 3.24.18 === * Wayland: - Fix more sizing regressions in Epiphany and LibreOffice menus, and popups in general * Build: - Make resource build reproducible * Translation updates Basque Latvian Explanation of the Ubuntu delta: * Update to the current stable version (based on Debian) Changelog entries since current focal version 3.24.17-3ubuntu1: gtk+3.0 (3.24.18-1) unstable; urgency=medium * Team upload * New upstream release - Fix remaining XInclude failure in documentation (Closes: #672369) * d/copyright: Update * d/patches: Drop patches that came from upstream -- Simon McVittie Fri, 10 Apr 2020 15:47:07 +0100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1873038/+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 1750087] Re: [libreoffice-kde4] LO crashes when trying to save
I can confirm that this issue is still present in 1:6.0.7-0ubuntu0.18.04.10. the command $ sudo apparmor_parser -R /etc/apparmor.d/usr.lib.libreoffice.program.* still works though. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1750087 Title: [libreoffice-kde4] LO crashes when trying to save Status in libreoffice package in Ubuntu: Fix Released Bug description: To reproduce type hello world into a libreoffice document. Then press the save icon. libreoffice crashes. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 to try to save and then try it crashes. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXQt Date: Fri Feb 16 16:19:38 2018 InstallationDate: Installed on 2017-06-20 (241 days ago) InstallationMedia: Lubuntu-Next 17.10 "Artful Aardvark" - Alpha amd64 (20170619) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-02-02 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750087/+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 1871913] Re: super key does not work with secondary keyboard layout
Obviously this is an upstream bug reported to gnome / mutter developers a while ago. As usual, they responded by being arrogant and refusing to acknowledge the problem. We will have to wait for them to open their eyes. -- 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/1871913 Title: super key does not work with secondary keyboard layout Status in budgie-desktop package in Ubuntu: New Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: New Bug description: When keyboard layout is set on Persian, pressing Super does not open Activities overview. It just works when the input is set on English. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 00:02:55 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-11-01 (159 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1871913/+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 1870833] Re: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init()
OK, that's bug #1873630. We don't actually know that this current crasher bug is correctly solved by the above patch, since pulseaudio is not yet working. Perhaps the new bug was there all along, but perhaps it was introduced by this patch being an incomplete fix. -- 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/1870833 Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() from module_alsa_card_LTX_pa__init() Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Incomplete Bug description: https://errors.ubuntu.com/problem/468f63163a916557999ec0a7aac3459fa638a2d1 --- gigabyte X370 Gaming 5 main board, Ryzen 1600 16gb ram. I get a black screen on boot of clean install of the Beta 20.04. realised however it has booted, hitting enter then Password then Enter and desktop loads.. Get error concerning Pulse audio crashing. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CrashCounter: 1 Date: Sat Apr 4 20:13:21 2020 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2020-04-04 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/pulseaudio --daemonize=no ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_alsa_ucm_add_profile_set () from /usr/lib/pulse-13.99.1/modules/libalsa-util.so module_alsa_card_LTX_pa__init () from /usr/lib/pulse-13.99.1/modules/module-alsa-card.so pa_module_load () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-13.99.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so ?? () from /usr/lib/pulse-13.99.1/modules/module-udev-detect.so Title: pulseaudio crashed with SIGABRT in pa_alsa_ucm_add_profile_set() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo dmi.bios.date: 08/01/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F42b dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF42b:bd08/01/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. separator: To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1870833/+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 1873630] [NEW] [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting.
Public bug reported: I have a Gigabyte motherboard that gives pulseaudio fits in Ubuntu 20.04 beta. (It worked fine in 18.04.4 LTS.) It produced pulseaudio crashes with bug #1870833 until a proposed fix was brought in from upstream: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu2 However, that did not actually make pulseaudio work; now it throws this error and aborts: Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. It was suggested in the previous bug that I should open a new bug for this. Here you are! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 00:25:26 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F25 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming 5 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF25:bd01/16/2019:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming5:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming5:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming 5 dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1873630 Title: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa- ucm.c:2158, function device_add_hw_mute_jack(). Aborting. Status in pulseaudio package in Ubuntu: New Bug description: I have a Gigabyte motherboard that gives pulseaudio fits in Ubuntu 20.04 beta. (It worked fine in 18.04.4 LTS.) It produced pulseaudio crashes with bug #1870833 until a proposed fix was brought in from upstream: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu2 However, that did not actually make pulseaudio work; now it throws this error and aborts: Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion 'jack' failed at modules/alsa/alsa-ucm.c:2158, function device_add_hw_mute_jack(). Aborting. It was suggested in the previous bug that I should open a new bug for this. Here you are! ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D4c', '/dev/snd/pcmC1D4p', '/dev/snd/pcmC1D2c', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 00:25:26 2020 InstallationDate: Installed on 2020-04-17 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably
[Desktop-packages] [Bug 1873625] [NEW] Mouse moves at the bottom right of the screen at log-in
Public bug reported: When I open a session, the mouse cursor moves at the bottom-right of the screen, at a fixed position. The coordinates are about (x:1730, y:970) on a 1920x1080 screen. When I close the session, the mouse goes again to this position. I am not sure if the issue really comes from mutter, or gdm, or other component. This behavior is specially annoying because your first action after log- in will probably consist in launching an application by clicking its icon at opposite position of the screen, in the top-left part of the launch bar. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 09:03:01 2020 InstallationDate: Installed on 2018-04-07 (742 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-04 (14 days ago) ** Affects: mutter (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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1873625 Title: Mouse moves at the bottom right of the screen at log-in Status in mutter package in Ubuntu: New Bug description: When I open a session, the mouse cursor moves at the bottom-right of the screen, at a fixed position. The coordinates are about (x:1730, y:970) on a 1920x1080 screen. When I close the session, the mouse goes again to this position. I am not sure if the issue really comes from mutter, or gdm, or other component. This behavior is specially annoying because your first action after log-in will probably consist in launching an application by clicking its icon at opposite position of the screen, in the top-left part of the launch bar. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.1-3ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 09:03:01 2020 InstallationDate: Installed on 2018-04-07 (742 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180403) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-04 (14 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1873625/+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 1873578] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1873578 Title: [WinBook TW102] Autorotation works but is backwards Status in iio-sensor-proxy package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: when docked into the keyboard dock, orientation is accurate on this tablet. However, when I rotate the tablet 90 degrees, the display will rotate the opposite direction, resulting in an upside down screen when in portrait mode. rotating either direction back into a landscape orientation results in a right-side up image. I can provide more information and maybe additional troubleshooting, if someone can give me instructions to follow. This issue persists in every release of since Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.0-050500-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 13:02:41 2020 DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-01-22 (86 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0603:0002 Novatek Microelectronics Corp. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub 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/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: MicroElectronics TW102 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-01-26 (82 days ago) dmi.bios.date: 03/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: H8811C dmi.board.vendor: EMDOOR dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: EMDOOR dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1: dmi.product.family: WinBook dmi.product.name: TW102 dmi.product.sku: 585497 dmi.product.version: 1 dmi.sys.vendor: MicroElectronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1873578/+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 1873578] Re: [WinBook TW102] Autorotation works but is backwards
** Summary changed: - Autorotation works but is backwards + [WinBook TW102] Autorotation works but is backwards ** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Also affects: iio-sensor-proxy (Ubuntu) Importance: Undecided Status: New -- 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/1873578 Title: [WinBook TW102] Autorotation works but is backwards Status in iio-sensor-proxy package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: when docked into the keyboard dock, orientation is accurate on this tablet. However, when I rotate the tablet 90 degrees, the display will rotate the opposite direction, resulting in an upside down screen when in portrait mode. rotating either direction back into a landscape orientation results in a right-side up image. I can provide more information and maybe additional troubleshooting, if someone can give me instructions to follow. This issue persists in every release of since Ubuntu 18.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 Uname: Linux 5.5.0-050500-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Apr 18 13:02:41 2020 DistUpgraded: 2020-01-26 15:24:00,462 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:7270] InstallationDate: Installed on 2020-01-22 (86 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0603:0002 Novatek Microelectronics Corp. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub 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/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/7p, 480M |__ Port 4: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M |__ Port 2: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M MachineType: MicroElectronics TW102 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.5.0-050500-generic root=UUID=20dd837f-ba9a-469c-bba4-45bb6e2370db ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-01-26 (82 days ago) dmi.bios.date: 03/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 8.17 dmi.board.asset.tag: Default string dmi.board.name: H8811C dmi.board.vendor: EMDOOR dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: EMDOOR dmi.chassis.version: 1 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr8.17:bd03/22/2018:svnMicroElectronics:pnTW102:pvr1:rvnEMDOOR:rnH8811C:rvr1.0:cvnEMDOOR:ct17:cvr1: dmi.product.family: WinBook dmi.product.name: TW102 dmi.product.sku: 585497 dmi.product.version: 1 dmi.sys.vendor: MicroElectronics version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/iio-sensor-proxy/+bug/1873578/+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 1873622] Re: Gnome shell 3.36 leaks, eats more memory than 3.34
Also I am going to make this bug private to avoid getting unrelated and misleading comments from anyone else, as "leak" bugs often attract. You will still be able to add comments yourself. ** Information type changed from Public to Private ** 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/1873622 Title: Gnome shell 3.36 leaks, eats more memory than 3.34 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Before Beta release and in 3.34 my gnome-shell used 177 MB of memory in maximum load, currently it begins from 190 MB to 500 MB without reducing after stop of heavy applications. It seems some plugins or gnome-shell still are memory hog ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 08:47:37 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873622/+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 1873622] Re: Gnome shell 3.36 leaks, eats more memory than 3.34
Please try using gnome-shell for some time without some or all of these extensions: 'gamem...@christian.kellner.me', 'freon@Veske', 'nvidiatemp@baco', 'desktop-icons@csoriano', 'ubuntu-appindicat...@ubuntu.com', 'ubuntu-d...@ubuntu.com']" because only if the leak occurs with zero extensions should this bug be assigned to the 'gnome-shell package'. ** Tags added: leak ** Tags added: nvidia -- 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/1873622 Title: Gnome shell 3.36 leaks, eats more memory than 3.34 Status in gnome-shell package in Ubuntu: Incomplete Bug description: Before Beta release and in 3.34 my gnome-shell used 177 MB of memory in maximum load, currently it begins from 190 MB to 500 MB without reducing after stop of heavy applications. It seems some plugins or gnome-shell still are memory hog ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-25.29-generic 5.4.30 Uname: Linux 5.4.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 19 08:47:37 2020 DisplayManager: gdm3 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.1-3ubuntu3 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1873622/+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 1810636] Re: [Qualcomm Atheros QCA6174] Bluetooth audio choppiness
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- 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/1810636 Title: [Qualcomm Atheros QCA6174] Bluetooth audio choppiness Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm running Linux 4.20.0-042000-generic #201812232030 x64 on a Dell XPS 9570 with QCA6174 chipset, and have had the problem with Bluetooth audio choppiness ever since I have owned this laptop. This problem has persisted for me with previous kernels. If I disable wifi and use media on machine locally, the problem doesn't occur. Note: I've reverted back v4.18.0-13-generic and reproduced the problem for the apport-collect report. It started with Ubuntu 18.04 and continues with 18.10. It's particularly noticeable when the when saturating the WLAN connection with throughput, i.e. copying a large file sequentially across from a samba share, but also streaming video online results in the audio progressively delaying over-time. Re-establishing the Bluetooth audio sync restores the sync, but slowly creeps out again. I've upgraded my linux-firmware package to disco 176 to match v4.20 kernel drivers ref: https://launchpad.net/ubuntu/+source/linux- firmware/1.176 The ath10k_core driver that supports this device has a reference for btcoex: ref https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c?h=v4.20#n2598 It's possible that the Bluetooth component firmware is not supporting or communicating btcoex compatibility, but this is starting to reach the edge of my ability to diagnose the problem. This btcoex support in ath9k has resolved/improved the Bluetooth bandwidth problem for older Qualcomm chipsets as shown in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164 As a troubleshooting step, I've also tried the very latest firmware-6 file from, but I'm continuing to experience the problem ref: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berg 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-07-02 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=c825a7b0-a5ac-41de-bd57-7663fef8a1f1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.176 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (79 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07GHH0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810636/+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 1810636] Re: [Qualcomm Atheros QCA6174] Bluetooth audio choppiness
** Tags added: a2dp a2dp-skip ** Tags removed: cosmic ** Tags added: bionic -- 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/1810636 Title: [Qualcomm Atheros QCA6174] Bluetooth audio choppiness Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I'm running Linux 4.20.0-042000-generic #201812232030 x64 on a Dell XPS 9570 with QCA6174 chipset, and have had the problem with Bluetooth audio choppiness ever since I have owned this laptop. This problem has persisted for me with previous kernels. If I disable wifi and use media on machine locally, the problem doesn't occur. Note: I've reverted back v4.18.0-13-generic and reproduced the problem for the apport-collect report. It started with Ubuntu 18.04 and continues with 18.10. It's particularly noticeable when the when saturating the WLAN connection with throughput, i.e. copying a large file sequentially across from a samba share, but also streaming video online results in the audio progressively delaying over-time. Re-establishing the Bluetooth audio sync restores the sync, but slowly creeps out again. I've upgraded my linux-firmware package to disco 176 to match v4.20 kernel drivers ref: https://launchpad.net/ubuntu/+source/linux- firmware/1.176 The ath10k_core driver that supports this device has a reference for btcoex: ref https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/wireless/ath/ath10k/core.c?h=v4.20#n2598 It's possible that the Bluetooth component firmware is not supporting or communicating btcoex compatibility, but this is starting to reach the edge of my ability to diagnose the problem. This btcoex support in ath9k has resolved/improved the Bluetooth bandwidth problem for older Qualcomm chipsets as shown in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1746164 As a troubleshooting step, I've also tried the very latest firmware-6 file from, but I'm continuing to experience the problem ref: https://github.com/kvalo/ath10k-firmware/tree/master/QCA6174/hw3.0/4.4.1 --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: berg 2871 F pulseaudio CurrentDesktop: GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-07-02 (187 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. XPS 15 9570 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=c825a7b0-a5ac-41de-bd57-7663fef8a1f1 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.176 Tags: cosmic Uname: Linux 4.18.0-13-generic x86_64 UpgradeStatus: Upgraded to cosmic on 2018-10-18 (79 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/02/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 07GHH0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd11/02/2018:svnDellInc.:pnXPS159570:pvr:rvnDellInc.:rn07GHH0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9570 dmi.product.sku: 087C dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810636/+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
