[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
sorry for my poor english! 非常感谢! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion:
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coiby Xu (coiby) my machine is MSFT0001:00 04F3:3140; i tested the patch on fedora 32 kernel 5.8.11 . the touchpad worked. but the original patch not compile : thread_hid undeclared then i add one line: static struct task_struct *thread_hid = NULL; many thanks to your hard work! i am in in expectation of your final version patch. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias:
[Desktop-packages] [Bug 1887718] Re: Screen freeze
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1887718 Title: Screen freeze Status in gnome-shell package in Ubuntu: Expired Bug description: Freezes randomly without any traceable pattern. Windows become unresponsive while the cursor works. To unfreeze I have to press the OFF button of my HP ProBook and then click on "Cancel" in the shutdown dialogue. That unfreezes the windows. May happen several times per session, may not happen at all. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 15 22:32:43 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 620 [103c:822c] InstallationDate: Installed on 2020-06-19 (26 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 138a:003f Validity Sensors, Inc. VFS495 Fingerprint Reader Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 05c8:03a0 Cheng Uei Precision Industry Co., Ltd (Foxlink) HP HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP ProBook 430 G4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=36191f51-931b-47be-bfdb-1553e0425aad ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/05/2016 dmi.bios.vendor: HP dmi.bios.version: P85 Ver. 01.03 dmi.board.name: 822C dmi.board.vendor: HP dmi.board.version: KBC Version 42.61 dmi.chassis.asset.tag: 5CD7065D4K dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP85Ver.01.03:bd12/05/2016:svnHP:pnHPProBook430G4:pvr:rvnHP:rn822C:rvrKBCVersion42.61:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP ProBook dmi.product.name: HP ProBook 430 G4 dmi.product.sku: Y7Z51EA#ACB dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1887718/+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 1889031] Re: syslog filling up quickly with entries about org.gnome.Shell.desktop
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1889031 Title: syslog filling up quickly with entries about org.gnome.Shell.desktop Status in gnome-shell package in Ubuntu: Expired Bug description: First time to report what I think might be a bug. /var/log/syslog is currently 1.2G, and syslog.1 is 717M. Running tail -n 500 /var/log/syslog | less shows multiple instances of lines like the following: Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: == Stack trace for context 0x55671fd02330 == Jul 27 12:08:45 elmerm-desktop gnome-shell[1913]: Object St.Icon (0x556726741490), has been already deallocated - impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #0 0x7ffc794c6070 b /home/elmerm/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/indi cators/network.js:164 (0x7f6f1acbc3c8 @ 42) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #1 0x7ffc794c60e0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6f706b5de0 @ 71) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #2 0x7ffc794c61b0 b self-hosted:918 (0x7f6f706f12b8 @ 394) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #3 0x556720194290 i /home/elmerm/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/exte nsion.js:225 (0x7f6f1acafef0 @ 64) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #4 0x556720194210 i /home/elmerm/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/exte nsion.js:214 (0x7f6f1acafe68 @ 65) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #5 0x556720194160 i /home/elmerm/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/extension.js:172 (0x7f6f1acafcd0 @ 98) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #6 0x5567201940a8 i /home/elmerm/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/extension.js:110 (0x7f6f1acaf6f8 @ 1421) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #7 0x7ffc794c82c0 b resource:///org/gnome/shell/ui/extensionSystem.js:135 (0x7f6f70259340 @ 509) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #8 0x556720193f78 i resource:///org/gnome/shell/ui/extensionSystem.js:342 (0x7f6f70259c48 @ 13) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #9 0x7ffc794c90c0 b self-hosted:251 (0x7f6f706c4ab0 @ 223) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #10 0x556720193ef8 i resource:///org/gnome/shell/ui/extensionSystem.js:341 (0x7f6f70259bc0 @ 76) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #11 0x556720193e78 i resource:///org/gnome/shell/ui/extensionSystem.js:369 (0x7f6f70259de0 @ 67) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #12 0x7ffc794ca5c0 b resource:///org/gnome/gjs/modules/signals.js:128 (0x7f6f706d2230 @ 386) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #13 0x7ffc794cadd0 b resource:///org/gnome/shell/ui/sessionMode.js:205 (0x7f6f526704d8 @ 254) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #14 0x7ffc794cae30 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6f706b5de0 @ 71) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #15 0x556720193de8 i resource:///org/gnome/shell/ui/sessionMode.js:174 (0x7f6f52670340 @ 100) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #16 0x7ffc794cba10 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6f706b5de0 @ 71) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #17 0x556720193d40 i resource:///org/gnome/shell/ui/screenShield.js:1212 (0x7f6f52653918 @ 159) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #18 0x7ffc794cc5f0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6f706b5de0 @ 71) Jul 27 12:08:45 elmerm-desktop gnome-shell[1913]: clutter_actor_hide: assertion 'CLUTTER_IS_ACTOR (self)' failed Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #19 0x556720193cc0 i resource:///org/gnome/shell/ui/screenShield.js:1198 (0x7f6f52653890 @ 17) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #20 0x556720193c38 i resource:///org/gnome/shell/gdm/authPrompt.js:501 (0x7f6f52681120 @ 61) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]: #21 0x7ffc794cd880 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f6f706b5de0 @ 71) Jul 27 12:08:45 elmerm-desktop org.gnome.Shell.desktop[1913]:
[Desktop-packages] [Bug 1897429] Re: package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
** Tags removed: need-duplicate-check -- 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/1897429 Title: package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in libreoffice package in Ubuntu: New Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 AptOrdering: vpnc-scripts:amd64: Install vpnc:amd64: Install network-manager-vpnc:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 27 09:05:13 2020 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2020-09-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897429/+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 1897429] [NEW] package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Public bug reported: i dont know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 AptOrdering: vpnc-scripts:amd64: Install vpnc:amd64: Install network-manager-vpnc:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 27 09:05:13 2020 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2020-09-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libreoffice (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 libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1897429 Title: package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in libreoffice package in Ubuntu: New Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.4.2-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 AptOrdering: vpnc-scripts:amd64: Install vpnc:amd64: Install network-manager-vpnc:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Sep 27 09:05:13 2020 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2020-09-26 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-common 1:6.4.2-0ubuntu3 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1897429/+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 1828884] Re: [META] Handling Japanese new era "令和 (Reiwa)"
** Changed in: poppler Status: New => Fix Released -- 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/1828884 Title: [META] Handling Japanese new era "令和 (Reiwa)" Status in Poppler: Fix Released Status in fonts-noto-cjk package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Fix Released Status in libreoffice-l10n package in Ubuntu: Fix Released Status in mozc package in Ubuntu: Fix Released Status in openjdk-8 package in Ubuntu: Fix Released Status in libreoffice source package in Xenial: Fix Released Status in libreoffice-l10n source package in Xenial: Fix Released Status in mozc source package in Xenial: Fix Released Status in openjdk-8 source package in Xenial: Fix Released Status in fonts-noto-cjk source package in Bionic: Fix Released Status in libreoffice source package in Bionic: Fix Released Status in libreoffice-l10n source package in Bionic: Fix Released Status in mozc source package in Bionic: Fix Released Status in openjdk-8 source package in Bionic: Fix Released Status in libreoffice source package in Cosmic: Fix Released Status in libreoffice-l10n source package in Cosmic: Fix Released Status in mozc source package in Cosmic: Fix Released Status in fonts-noto-cjk source package in Disco: Fix Released Status in libreoffice source package in Disco: Fix Released Status in libreoffice-l10n source package in Disco: Fix Released Status in mozc source package in Disco: Fix Released Status in openjdk-8 source package in Disco: Fix Released Bug description: [Background] Many packages are affected by the requirement to support the new era "Reiwa" (令和） This is the meta bug to track packages that need fixes; which packages have already been SRUd to previous releases, how to prioritize the work needed, and general test cases for verifying that things are working as expected. [Impact] Users who run Ubuntu in Japanese. [Test cases] == Date conversion == On applications that support writing dates in long form, or with symbols to denote era (either in X00.00.00 format or in GG1G5G1G format (G- glyph; X- character): 1) Enable date formatting in each of the above formats that are supported (long form or symbols) 2) Type in '2019/05/01' to be formatted, verify that it shows as "令和1年5月1日" or "R1.05.01" 3) Type in '2019/04/30' to be formatted, verify that it shows as "平成31年4月30日" or "H31.4.30" == Date output == 1) Set date to 2019/05/01 2) Output date; verify that the year it is displayed as "令和元年" 3) Set date to 2019/04/30 4) Output date; verify that the year is diplayed as "平成31年" === Displaying formatted year for Japanese era with glibc === Run: LC_ALL=ja_JP.utf8 date +%EY -d 20190430 # previous era (should still work as before SRUs) or LC_ALL=ja_JP.utf8 date +%EY -d 20190501 # new era (should now correctly display the new era) == Character maps / font support == 1) Search for character "SQUARE ERA NAME" 2) Verify that the results include at least "SQUARE ERA NAME HEISEI" and "SQUARE ERA NAME REIWA" (there should also be Syouwa, Taisyou and Meizi), and that the glyphs are readable: - SQUARE ERA NAME HEISEI: ㍻ - SQUARE ERA NAME REIWA: 令和 (in a single glyph) Display of the Reiwa square glyph is font-specific; it may show simply as a empty square or a square with hex characters. If that is the case, the unicode data supports the new character, but the selected font does not include the new glyph. == Typing / input methods == 1) Type in 'heisei' 2) Verify that the input method in use gives you an option "平成", and optionally also the square era glyph. 3) Type in 'reiwa' 4) Verify that the input method in use gives you an option that includes "令和", and possibly also the square era glyph (if supported for Heisei) 5) Type in the following strings, and verify that the options are provided in the input method: * "れいわ"(reiwa) => "令和" * "れいわ"(reiwa) => "㋿" * "２０１８ねん"(2018nenn) => "平成三十年" * "２０１９ねん"(2019nenn) => "平成三十一年" * "２０１９ねん"(2019nenn) => "令和元年" * "２０２０ねん"(2020nenn) => "令和二年" /!\ Some fonts, like fonts-noto-cjk, currently have no glyph for U+32FF. [Regression potential] This is a potentially large change as it impacts font display, character sets as well as date conversions. As such, extreme care should be taken to ensure that regressions are avoided, such that dates previous to May 1, 2019 continue to display as before, and dates onward are displayed with the new era symbols. The included test cases account for verifying the continued behavior or previous dates. To manage notifications about this bug go to: https://bugs.launchpad.net/poppler/+bug/1828884/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1607675] Re: Nautilus cann't access AirPort Time Capsule in Ubuntu 16.04
This still exist in Ubuntu 20.04 LTS
** Changed in: nautilus (Ubuntu)
Status: Expired => New
--
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/1607675
Title:
Nautilus cann't access AirPort Time Capsule in Ubuntu 16.04
Status in nautilus package in Ubuntu:
New
Bug description:
When connecting to my Time Capsule, I'll get an error
"kFPAuthContinue" from server.
While I can mount server with `mount.cifs`:
```
sudo mount.cifs \\10.0.1.1\${user_name} /mnt/ -o user=${user_name},sec=ntlm
```
According to `mount.cifs`'s manual, **the default was sec=ntlm in
mainline kernel version prior to v3.8, and has been changed to
sec=ntlmssp in kernel v3.8+**.
Maybe that's the reason why it works in Ubuntu 14.04 and fails in
Ubuntu 16.04.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1607675/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 581770] Re: [Kubuntu][dvipdfmx][Japanese] dvipdfmx can't create PDF by default from DVI file that includes japanese characters.
Not reproducible here on Debian, but the reason is very obvious ...
> Kubuntu 10.04 (i386)
> Virtualbox 3.1.8
> Language Japanese
> texlive-base(dvipdfmx) 2009-7
This is so horribly outdated that there is no way it can work.
platex and friends were introduced into TeX Live starting from 2008 and
and it took 2-3 years to get full support.
So, on a current system, with say TeX Live 2020 (Debian version here),
this is all working.
I think bugs from 2009 should be closed in 2020.
$ file hello.tex
hello.tex: LaTeX 2e document, UTF-8 Unicode text
$ cat hello.tex
\documentclass[a4paper]{jsarticle}
\begin{document}
Hello World ハローワールド 日本語のテスト
\end{document}
$ nkf --overwrite -e hello.tex
$ file hello.tex
hello.tex: LaTeX 2e document, ISO-8859 text # what a mischaracterization!
$ platex -kanji=euc hello.tex
This is e-pTeX, Version 3.14159265-p3.8.3-191112-2.6 (euc) (TeX Live
2020/Debian) (preloaded format=platex)
restricted \write18 enabled.
entering extended mode
(./hello.tex
pLaTeX2e <2020-04-12> (based on LaTeX2e <2020-02-02> patch level 5)
L3 programming layer <2020-07-17>
(/usr/share/texlive/texmf-dist/tex/platex/jsclasses/jsarticle.cls
Document Class: jsarticle 2020/02/02 jsclasses (okumura, texjporg)
(/usr/share/texlive/texmf-dist/tex/platex/jsclasses/jslogo.sty))
(/usr/share/texlive/texmf-dist/tex/latex/l3backend/l3backend-dvips.def)
(./hello.aux) [1] (./hello.aux) )
Output written on hello.dvi (1 page, 344 bytes).
Transcript written on hello.log.
$ dvipdfmx hello.dvi
hello.dvi -> hello.pdf
[1]
2851 bytes written
$
Norbert
--
PREINING Norbert https://www.preining.info
Accelia Inc. + IFMGA ProGuide + TU Wien + JAIST + TeX Live + Debian Dev
GPG: 0x860CDC13 fp: F7D8 A928 26E3 16A1 9FA0 ACF0 6CAC A448 860C DC13
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-base in Ubuntu.
https://bugs.launchpad.net/bugs/581770
Title:
[Kubuntu][dvipdfmx][Japanese] dvipdfmx can't create PDF by default
from DVI file that includes japanese characters.
Status in texlive-base package in Ubuntu:
Confirmed
Bug description:
Binary package hint: texlive-base
I compiled a TeX file (include Japanese character) to DVI file by platex
command.
And I converted a DVI file to PDF by dvipdfmx.
I input a following commands.
[How To reproduce]
$ sudo apt-get install vim # for edit a latex file.
$ sudo apt-get install nkf # for convert a character code.
$ sudo apt-get install texlive "^ptex-*" dvipdfmx gv gs-cjk-resources
"^cmap-adobe-*" okumura-clsfiles
$ sudo jisftconfig add
$ vim hello.tex # edit a tex file.
$ nkf --overwirte -e hello.tex # convert a character code to EUC-JP
$ platex -kanji=euc hello.tex # compile a tex file.
$ nkf -w hello.tex # = cat hello.tex (To convert UTF-8 and output stdout.
hello.tex is EUC-JP)
\documentclass[a4papper]{jsarticle}
\begin{document}
Hello World ハローワールド 日本語のテスト
\end{document}
$ dvipdfmx hello.dvi
[Actual Result]
$ dvipdfmx hello.dvi
hello.dvi -> hello.pdf
** WARNING ** Failed to load AGL file "pdfglyphlist.txt"...
** WARNING ** Failed to load AGL file "glyphlist.txt"...
[1
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 0+555/600 --dpi 555
rml-jis
mktexpk: don't know how to create bitmap font for rml-jis.
kpathsea: Appending font creation commands to missfont.log.
** WARNING ** Could not locate a virtual/physical font for TFM "rml-jis".
** WARNING ** >> There are no valid font mapping entry for this font.
** WARNING ** >> Font file name "rml-jis" was assumed but failed to locate
that font.
** ERROR ** Cannot proceed without .vf or "physical" font for PDF output...
Output file removed.
[Expected Result]
This is a result of Debian GNU/Linux sid.
$ dvipdfmx hello.dvi
./hello.dvi -> hello.pdf
[1]
3274 bytes written
[How To Fix]
This is not perfect. The warning still remains.
$ sudo cp /etc/texmf/dvipdfmx/dvipdfmx.cfg
/etc/texmf/dvipdfmx/dvipdfmx.cfg.orig # backup
$ sudo vim /etc/texmf/dvipdfmx/dvipdfmx.cfg
$ diff -u /etc/texmf/dvipdfmx/dvipdfmx.cfg.orig
/etc/texmf/dvipdfmx/dvipdfmx.cfg
--- /etc/texmf/dvipdfmx/dvipdfmx.cfg.orig 2010-05-18 22:32:20.661200781
+0900
+++ /etc/texmf/dvipdfmx/dvipdfmx.cfg2010-05-18 22:32:58.745196921 +0900
@@ -190,3 +190,4 @@
%% Put additonal fontmap files here (usually for Type0 fonts)
f cid-x.map
+f jis-cjk.map
$ mkdir -p ~/.texmf-var/fonts
$ ln -s /var/lib/defoma/gs.d/dirs/CMap ~/.texmf-var/fonts/cmap
$ dvipdfmx hello.dvi
hello.dvi -> hello.pdf
** WARNING ** Failed to load AGL file "pdfglyphlist.txt"...
** WARNING ** Failed to load AGL file "glyphlist.txt"...
[1]
3191 bytes written
[Environment]
Kubuntu 10.04 (i386)
Virtualbox 3.1.8
Language Japanese
texlive-base(dvipdfmx) 2009-7
result of "dpkg -l": attached (filename: dpkg-l.txt)
To manage
[Desktop-packages] [Bug 581770] Re: [Kubuntu][dvipdfmx][Japanese] dvipdfmx can't create PDF by default from DVI file that includes japanese characters.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: texlive-base (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to texlive-base in Ubuntu.
https://bugs.launchpad.net/bugs/581770
Title:
[Kubuntu][dvipdfmx][Japanese] dvipdfmx can't create PDF by default
from DVI file that includes japanese characters.
Status in texlive-base package in Ubuntu:
Confirmed
Bug description:
Binary package hint: texlive-base
I compiled a TeX file (include Japanese character) to DVI file by platex
command.
And I converted a DVI file to PDF by dvipdfmx.
I input a following commands.
[How To reproduce]
$ sudo apt-get install vim # for edit a latex file.
$ sudo apt-get install nkf # for convert a character code.
$ sudo apt-get install texlive "^ptex-*" dvipdfmx gv gs-cjk-resources
"^cmap-adobe-*" okumura-clsfiles
$ sudo jisftconfig add
$ vim hello.tex # edit a tex file.
$ nkf --overwirte -e hello.tex # convert a character code to EUC-JP
$ platex -kanji=euc hello.tex # compile a tex file.
$ nkf -w hello.tex # = cat hello.tex (To convert UTF-8 and output stdout.
hello.tex is EUC-JP)
\documentclass[a4papper]{jsarticle}
\begin{document}
Hello World ハローワールド 日本語のテスト
\end{document}
$ dvipdfmx hello.dvi
[Actual Result]
$ dvipdfmx hello.dvi
hello.dvi -> hello.pdf
** WARNING ** Failed to load AGL file "pdfglyphlist.txt"...
** WARNING ** Failed to load AGL file "glyphlist.txt"...
[1
kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 0+555/600 --dpi 555
rml-jis
mktexpk: don't know how to create bitmap font for rml-jis.
kpathsea: Appending font creation commands to missfont.log.
** WARNING ** Could not locate a virtual/physical font for TFM "rml-jis".
** WARNING ** >> There are no valid font mapping entry for this font.
** WARNING ** >> Font file name "rml-jis" was assumed but failed to locate
that font.
** ERROR ** Cannot proceed without .vf or "physical" font for PDF output...
Output file removed.
[Expected Result]
This is a result of Debian GNU/Linux sid.
$ dvipdfmx hello.dvi
./hello.dvi -> hello.pdf
[1]
3274 bytes written
[How To Fix]
This is not perfect. The warning still remains.
$ sudo cp /etc/texmf/dvipdfmx/dvipdfmx.cfg
/etc/texmf/dvipdfmx/dvipdfmx.cfg.orig # backup
$ sudo vim /etc/texmf/dvipdfmx/dvipdfmx.cfg
$ diff -u /etc/texmf/dvipdfmx/dvipdfmx.cfg.orig
/etc/texmf/dvipdfmx/dvipdfmx.cfg
--- /etc/texmf/dvipdfmx/dvipdfmx.cfg.orig 2010-05-18 22:32:20.661200781
+0900
+++ /etc/texmf/dvipdfmx/dvipdfmx.cfg2010-05-18 22:32:58.745196921 +0900
@@ -190,3 +190,4 @@
%% Put additonal fontmap files here (usually for Type0 fonts)
f cid-x.map
+f jis-cjk.map
$ mkdir -p ~/.texmf-var/fonts
$ ln -s /var/lib/defoma/gs.d/dirs/CMap ~/.texmf-var/fonts/cmap
$ dvipdfmx hello.dvi
hello.dvi -> hello.pdf
** WARNING ** Failed to load AGL file "pdfglyphlist.txt"...
** WARNING ** Failed to load AGL file "glyphlist.txt"...
[1]
3191 bytes written
[Environment]
Kubuntu 10.04 (i386)
Virtualbox 3.1.8
Language Japanese
texlive-base(dvipdfmx) 2009-7
result of "dpkg -l": attached (filename: dpkg-l.txt)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/texlive-base/+bug/581770/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
It's not working for me using nvidia graphic card. The only way to work around is to use lightdm instead of gdm3, but I can't login automatically. I started using Ubuntu budgie in dual boot until the bug is fixed. I tried Kubuntu and the bug is also in Kubuntu. Envoyé de Mailspring (https://link.getmailspring.com/link/bcb6601f-ac5e-4c6b-b97c-89bccd4fa...@getmailspring.com/0?redirect=https%3A%2F%2Fgetmailspring.com%2F=MTg5MjQ0MEBidWdzLmxhdW5jaHBhZC5uZXQ%3D), la meilleure application de messagerie gratuite pour le travail On sept. 23 2020, at 10:51 am, Sujit Kumar <1892...@bugs.launchpad.net> wrote: > I can confirm this bug is fixed when I updated mutter to > 3.36.1-1ubuntu0.20.04.1. Using NVIDIA Graphics card. > > -- > You received this bug notification because you are subscribed to a > duplicate bug report (1893792). > https://bugs.launchpad.net/bugs/1892440 > > Title: > Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly > on Nvidia) > > Status in mutter package in Ubuntu: > Fix Released > Status in mutter source package in Focal: > Fix Committed > Status in mutter source package in Groovy: > Fix Released > > Bug description: > [ Impact ] > > GNOME Shell starts with a wrong text size > > [ Test case ] > In a terminal run: > - Xephyr :2 > > In another one: > - env DISPLAY=:2 dbus-run-session gnome-shell --x11 > > The shell should run in the embedded window, with the correct text > size, running it again (without closing Xephyr window, but stopping > the shell execution) should not bigger than expected. > > -- Other test case (hw dependant) > - Login, ensure that the Shell text size matches the configured one. > > [ Regression potential ] > Initial UI scaling when fractional scaling is enabled is wrong. > > [ Workaround ] > Run on startup: > - gsettings set org.gnome.desktop.interface scaling-factor \ > $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) > > > --- > See also bug 1892521. > The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 > causes small text in GNOME Shell menu with NVIDIA cards. > > With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem > is after update to the (3.36.4-0ubuntu0.20.04.2). > --- > ProblemType: Bug > ApportVersion: 2.20.11-0ubuntu27.8 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 > InstallationDate: Installed on 2020-08-18 (2 days ago) > InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" > (20200815) > NonfreeKernelModules: nvidia_modeset nvidia > Package: mutter 3.36.4-0ubuntu0.20.04.2 > PackageArchitecture: amd64 > ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 > Tags: focal > Uname: Linux 5.4.0-42-generic x86_64 > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo > _MarkForUpload: True > modified.conffile..etc.default.apport: > # set this to 0 to disable apport, or to 1 to enable it > # you can temporarily override this with > # sudo service apport start force_start=1 > enabled=0 > mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+subscriptions > -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease:
[Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
The attachment "polling_pin_state_touchpad.patch" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias:
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
** Changed in: mutter (Ubuntu Focal) Status: Fix Released => Fix Committed -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
I would like to update that my status update from fix committed to fix released was caused by an accident, and thus should be disregarded Sorry in advance for any confusion caused ** Changed in: mutter (Ubuntu Focal) Status: Fix Committed => Fix Released -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi, I've found out that there is something wrong with the GPIO interrupt controller under Linux. For the details, you can check https://www.spinics.net/lists/linux-input/msg69267.html. While I'm still working on the ultimate solution, you may be interested in the patch as attached which makes the touchpad work by polling HID reports from the touchpad. I've tested the patch for the Synaptics touchpad (MSFT0001:00 06CB:7F28). I guess it will also work for the Elan touchpad (MSFT0001:00 04F3:3140) based on the ACPI DSDT. If not, could you share the following info with me, 1) dsdt.dsl Use the following commands to get dsdt.dsl (you need to install acpica which provides iasl) a) sudo acpidump > acpidata.out b) acpixtract -sSSDT acpidata.out c) acpixtract -sDSDT acpidata.out d) iasl -da dsdt.dat ssdt*.dat 2) dmesg dump when booting kernel with the following command line parameters i2c-designware-core.dyndbg=+p i2c-hid.debug=1 Thank you! ** Patch added: "polling_pin_state_touchpad.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+attachment/5414497/+files/polling_pin_state_touchpad.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic
[Desktop-packages] [Bug 1897396] [NEW] Unable to make chromium-chromedriver work with selenium
Public bug reported: Trying to use chrome web driver instead of firefox driver in selenium gives following error. How to use chromium with selenium now when it is packaged in Snap? Error message: selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /snap/chromium/current/command-chromium.wrapper is no longer running, so ChromeDriver is assuming that Chrome has crashed.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-chromedriver 1:85.0.4183.83-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 26 19:10:59 2020 InstallationDate: Installed on 2019-11-03 (328 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: chromium-browser UpgradeStatus: Upgraded to focal on 2020-03-28 (181 days ago) ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- 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/1897396 Title: Unable to make chromium-chromedriver work with selenium Status in chromium-browser package in Ubuntu: New Bug description: Trying to use chrome web driver instead of firefox driver in selenium gives following error. How to use chromium with selenium now when it is packaged in Snap? Error message: selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally. (unknown error: DevToolsActivePort file doesn't exist) (The process started from chrome location /snap/chromium/current/command-chromium.wrapper is no longer running, so ChromeDriver is assuming that Chrome has crashed.) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: chromium-chromedriver 1:85.0.4183.83-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Sep 26 19:10:59 2020 InstallationDate: Installed on 2019-11-03 (328 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: chromium-browser UpgradeStatus: Upgraded to focal on 2020-03-28 (181 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1897396/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Would it be possible to replace the track-pad with a different one from a supported manufacturer? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05
[Desktop-packages] [Bug 1892440] Re: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia)
@Chistiano Nunes right, I updated and installed it, but but everything like before. So I installed the "temporarily as a workaround" from above again. sudo apt install libmutter-6-0=3.36.1-3ubuntu3 gir1.2-mutter-6=3.36.1-3ubuntu3 sudo apt-mark hold libmutter-6-0 -- 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/1892440 Title: Shell text with wrong size in mutter 3.36.4-0ubuntu0.20.04.2 (mostly on Nvidia) Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Groovy: Fix Released Bug description: [ Impact ] GNOME Shell starts with a wrong text size [ Test case ] In a terminal run: - Xephyr :2 In another one: - env DISPLAY=:2 dbus-run-session gnome-shell --x11 The shell should run in the embedded window, with the correct text size, running it again (without closing Xephyr window, but stopping the shell execution) should not bigger than expected. -- Other test case (hw dependant) - Login, ensure that the Shell text size matches the configured one. [ Regression potential ] Initial UI scaling when fractional scaling is enabled is wrong. [ Workaround ] Run on startup: - gsettings set org.gnome.desktop.interface scaling-factor \ $(gsettings get org.gnome.desktop.interface scaling-factor | cut -d' ' -f2) --- See also bug 1892521. The package mutter version (3.36.4-0ubuntu0.20.04.2) for Ubuntu 20.04 causes small text in GNOME Shell menu with NVIDIA cards. With a previous version (3.36.4-0ubuntu0.20.04.1) all works fine. The problem is after update to the (3.36.4-0ubuntu0.20.04.2). --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOMEDistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-08-18 (2 days ago) InstallationMedia: Ubuntu 20.04.1 2020.08.15 LTS "Custom Focal Fossa" (20200815) NonfreeKernelModules: nvidia_modeset nvidia Package: mutter 3.36.4-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2020-08-15T17:44:36 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1892440/+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 1897281] Re: evince suicides in 20.04 but not in 18.04
> Sebastien Bacher (seb128): > Could you also maybe include an example to the bug? Please go to https://b-ok.cc/book/2611763/45278d "The Cartoons of Cobean" then hit the blue button [Download (cbr, 113.07 MB)] Thanks, siggi2 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1897281 Title: evince suicides in 20.04 but not in 18.04 Status in evince package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Evince does a suicide trip after unsuccessfully trying to open a CBR file. After a while it is killed. Here is my terminal output: $ evince TheCartoons.cbr Killed $ And between the line "$ evince TheCartoons.cbr" and the final "Killed", are passing many minutes. Please note that I started my report in https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1785060 not knowing exactly what "expired" there means. I did "apport-collect 1785060" there, too. Please note also that my error message (see above) is quite different from seb128 in bug 1785060. In fact, there is no error message just the statement "Killed". What gets me is that in 18.04 it is working so smooth and fast and that in 20.04 it is such a mess! P.S. I do not know whether this helps, but with Debian 11 Xfce (Buster sid, testing), evince loads and opens this CBR file correctly, albeit slowly, but okular (installed in Buster sid) yields a similar error message like that of seb128 with evince in bug 1785060: "Could not open file TheCartoons.cbr. The version of unrar on your system is not suitable for opening comicbooks" Inverted world ;-) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1897281/+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 1861280] Re: Desktop icons reshuffle themselves
I updated to 20.04 in July & the problem is still present for me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1861280 Title: Desktop icons reshuffle themselves Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: It may be a bad habit, but for years I have saved temporary files (stuff I don't intend to keep long & some work in progress) to my desktop, where I won't forget them & they are immediately available. For years there was no problem - icons on the desktop stayed where they were. Since 19.10 things have gone crazy (might have started with 19.04 but I can't check that now). Nearly every time a new item is added or removed, some or all of the other items get reshuffled on the desk! I raised this issue on Ubuntu Forum, with details & screenshots (PLEASE LOOK) here: https://ubuntuforums.org/showthread.php?t=2435768 I have run comparison tests, using SHA-verified Live USB stick versions of Ubuntu 18.04.3 & 19.10, which I suppose anybody else can duplicate. My test was to successively "Save-as to desktop" 32 tiny LibO files called 01, 02, 03 etc in that order. With 18.04.3, each item was positioned top-to-bottom in a column at left, then in the next columns to the right after each column was full. Once positioned, no icon moved. With 19.10, icons were positioned clustered top-left but new columns were started before previous columns were full. Nearly every addition caused previous icons to be reshuffled. Frequently the number of columns DIMINISHED when a new icon was added. With 19.10, removing icons causes other items to reshuffle. With 18.04.3, removing icons leaves a gap, which is filled by the next item added. I think the behaviour of 18.04.3 is perfect & the behaviour of 19.10 is an unacceptable regression. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: nautilus 1:3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jan 29 14:03:30 2020 InstallationDate: Installed on 2014-10-23 (1923 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2019-11-04T18:03:11.954726 usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1861280/+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 1891165] Re: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed
Same here. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1891165 Title: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed Status in gsettings-desktop-schemas package in Ubuntu: Confirmed Bug description: I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3 install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is. But i got more errors The following packages have unmet dependencies: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but 3.26.1-2ubuntu1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. sudo ln -sf /usr/bin/python2.7 /usr/bin/python ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 11 20:38:08 2020 InstallationDate: Installed on 2020-02-08 (184 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+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 1872268] Re: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded)
This bug also happens to me. My resolution is 1366 x 768 and is working again after disabling the Ubuntu dock in the extensions app. -- 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/1872268 Title: Gnome Shell completely freezes in Ubuntu 20.04 when clicking outside of app icon folders (when ubuntu-dock is loaded) Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: Description: Ubuntu Focal Fossa (development branch) Release: 20.04 Bug: Gnome shell while opening app drawer, clicking on an app folder and clicking on the blank area freezes gnome shell and it makes the session completely unusable and non recoverable. How to reproduce: 1- Click 9 dots on bottom corner of dash (the app launcher button), wait for the app grid to show up. 2- Click on an app folder to open it. 3- Click on the blank area outside of the opened folder dialog. 4- Gnome shell gets freezes and never come back from this state, on both wayland session and x11 session. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 12 12:00:13 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-11 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200329) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1872268/+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 1882558] Re: desktop - missing templates to create new files
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-flashback (Ubuntu) Status: New => Confirmed -- 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/1882558 Title: desktop - missing templates to create new files Status in GNOME Flashback: Unknown Status in gnome-shell-extension-desktop-icons: Unknown Status in gnome-flashback package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Won't Fix Bug description: Hi, in nautilus i can create new files by templates in (german) directory ~/Vorlagen i miss the option to create files on desktop this way regards Frank To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-flashback/+bug/1882558/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
lenovo release new bios EUCN26WW -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in Pop!_OS: New Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-input-libinput package in Ubuntu: Confirmed Status in linux package in Arch Linux: Confirmed Status in linux package in Fedora: Confirmed Status in linux package in openSUSE: New Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion:
[Desktop-packages] [Bug 1660316] Re: apparmor denial of CUPS
@skliarie, your pasted log message is actually a different issue, and I just reported https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369 for it. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1660316 Title: apparmor denial of CUPS Status in cups package in Ubuntu: Expired Bug description: Printing is enabled when doing sudo aa-complain cupsd Here is an extract of /var/log/syslog: Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929457] audit: type=1400 audit(1485776519.269:37): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.929744] audit: type=1400 audit(1485776519.269:38): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6932 comm="apparmor_parser" Jan 30 12:41:59 dag-TS-P500 kernel: [ 868.945422] audit: type=1400 audit(1485776519.285:39): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6932 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817070] audit: type=1400 audit(1485776530.158:40): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.817342] audit: type=1400 audit(1485776530.158:41): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=6941 comm="apparmor_parser" Jan 30 12:42:10 dag-TS-P500 kernel: [ 879.837254] audit: type=1400 audit(1485776530.178:42): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=6941 comm="apparmor_parser" Jan 30 12:42:16 dag-TS-P500 zeitgeist-datah[3706]: downloads-directory-provider.vala:120: Couldn't process /home/dag/.glvndcEQzqA: Error when getting information for file '/home/dag/.glvndcEQzqA': No such file or directory Jan 30 12:42:23 dag-TS-P500 dbus[996]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' Jan 30 12:42:23 dag-TS-P500 systemd[1]: Starting Hostname Service... Jan 30 12:42:24 dag-TS-P500 dbus[996]: [system] Successfully activated service 'org.freedesktop.hostname1' Jan 30 12:42:24 dag-TS-P500 systemd[1]: Started Hostname Service. Jan 30 12:42:26 dag-TS-P500 kernel: [ 895.746636] audit: type=1400 audit(1485776546.086:43): apparmor="DENIED" operation="capable" profile="/usr/sbin/cupsd" pid=6967 comm="lpd" capability=12 capname="net_admin" Jan 30 12:42:54 dag-TS-P500 systemd[1]: Starting Cleanup of Temporary Directories... Jan 30 12:42:54 dag-TS-P500 systemd-tmpfiles[6973]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring. Jan 30 12:42:54 dag-TS-P500 systemd[1]: Started Cleanup of Temporary Directories. Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.OneConf' Jan 30 12:44:03 dag-TS-P500 com.ubuntu.OneConf[2707]: WARNING:oneconf.hosts:Error in loading other_hosts file: [Errno 2] No such file or directory: '/home/dag/.cache/oneconf/d2fc3bf30c9f4976b441a8f14de53bda/other_hosts' Jan 30 12:44:23 dag-TS-P500 dbus-daemon[2707]: Activating service name='com.ubuntu.sso' Jan 30 12:44:24 dag-TS-P500 dbus-daemon[2707]: Successfully activated service 'com.ubuntu.sso' Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.685842] audit: type=1400 audit(1485776751.028:44): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.686099] audit: type=1400 audit(1485776751.028:45): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=7024 comm="apparmor_parser" Jan 30 12:45:51 dag-TS-P500 kernel: [ 1100.700446] audit: type=1400 audit(1485776751.044:46): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd//third_party" pid=7024 comm="apparmor_parser" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940891] audit: type=1400 audit(1485776757.284:47): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" Jan 30 12:45:57 dag-TS-P500 kernel: [ 1106.940938] audit: type=1400 audit(1485776757.284:48): apparmor="ALLOWED" operation="capable" profile="/usr/sbin/cupsd" pid=7031 comm="lpd" capability=12 capname="net_admin" ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: cups 2.2.0-2 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 NonfreeKernelModules:
[Desktop-packages] [Bug 1873764] Re: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id
*** This bug is a duplicate of bug 1872564 *** https://bugs.launchpad.net/bugs/1872564 The original report contains two issues, where only the second one is fixed in https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1872564. For the first audit messages for `cups-browsed` [ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 comm="cups-browsed" capability=23 capname="sys_nice" I created https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1873764 Title: CUPS Apparmor Error opening /proc/sys/kernel/random/boot_id Status in cups package in Ubuntu: Confirmed Status in cups package in Debian: New Bug description: I noted the following messages on a just installed Ubuntu Focal: $ dmesg | grep cups [ 1769.505132] audit: type=1400 audit(1587372138.575:3011): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15230 comm="cups-browsed" capability=23 capname="sys_nice" [ 1776.623181] audit: type=1400 audit(1587372145.693:3012): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=15510 comm="cups-browsed" capability=23 capname="sys_nice" [ 2040.426033] audit: type=1400 audit(1587372409.494:3013): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426044] audit: type=1400 audit(1587372409.494:3014): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426074] audit: type=1400 audit(1587372409.494:3015): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426092] audit: type=1400 audit(1587372409.494:3016): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2040.426106] audit: type=1400 audit(1587372409.494:3017): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404914] audit: type=1400 audit(1587372410.473:3018): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404920] audit: type=1400 audit(1587372410.473:3019): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404926] audit: type=1400 audit(1587372410.473:3020): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404953] audit: type=1400 audit(1587372410.473:3021): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2041.404963] audit: type=1400 audit(1587372410.473:3022): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925327] audit: type=1400 audit(1587372440.994:3028): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925330] audit: type=1400 audit(1587372440.994:3029): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925337] audit: type=1400 audit(1587372440.994:3030): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925382] audit: type=1400 audit(1587372440.994:3031): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 [ 2071.925391] audit: type=1400 audit(1587372440.994:3032): apparmor="DENIED" operation="open" profile="/usr/sbin/cupsd" name="/proc/sys/kernel/random/boot_id" pid=15508 comm="cupsd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 It happened after installing Brother
[Desktop-packages] [Bug 1897369] [NEW] apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
Public bug reported: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" ** Affects: cups (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) Status in cups package in Ubuntu: New Bug description: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+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 1897369] Re: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE)
>From the manual page capabilities(7): CAP_SYS_NICE * Lower the process nice value (nice(2), setpriority(2)) and change the nice value for arbitrary processes; * set real-time scheduling policies for calling process, and set scheduling policies and priorities for arbitrary processes (sched_setscheduler(2), sched_setparam(2), sched_setattr(2)); * set CPU affinity for arbitrary processes (sched_setaffin‐ ity(2)); * set I/O scheduling class and priority for arbitrary processes (ioprio_set(2)); * apply migrate_pages(2) to arbitrary processes and allow pro‐ cesses to be migrated to arbitrary nodes; * apply move_pages(2) to arbitrary processes; * use the MPOL_MF_MOVE_ALL flag with mbind(2) and move_pages(2) No idea, if cups-browsed should be allowed to change the nice value of *arbitrary* processes. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1897369 Title: apparmor: Allow cups-browsed to change nice value (CAP_SYS_NICE) Status in cups package in Ubuntu: New Bug description: In Ubuntu 20.04.1 with *cups-browsed* 1.27.4-1, apparmor prevents `/usr/sbin/cups-browsed` to change its nice value. $ sudo dmesg | grep apparmor [541870.509461] audit: type=1400 audit(1600898428.089:60): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=62030 comm="cups-browsed" capability=23 capname="sys_nice" [628298.779668] audit: type=1400 audit(1600984854.115:61): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=66850 comm="cups-browsed" capability=23 capname="sys_nice" [714667.424963] audit: type=1400 audit(1601071220.527:62): apparmor="DENIED" operation="capable" profile="/usr/sbin/cups-browsed" pid=76828 comm="cups-browsed" capability=23 capname="sys_nice" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1897369/+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 1798166] Re: “Mouse battery low” notification can't be disabled
Clarification: this bug ist not about wrong battery Level measurements (Nobody reported that), it's about users being unable to disable notifications. The notification is shown even when in DND mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1798166 Title: “Mouse battery low” notification can't be disabled Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in linux package in Ubuntu: Invalid Bug description: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/108 --- I have a wireless mouse powered by non-rechargeable battery. The mouse works absolutely fine even with low battery level. Problem is, Ubuntu gives notifications about the battery level all the time. I have had this issue for almost two months now, and mouse is working perfectly. I had to click away the notification almost every time I moved the mouse. I was then able to make the notifications appear less frequently, but the notification still always appear after some interval, and always after I log in. Here are some specific things I have tried, they have not helped. https://askubuntu.com/questions/1071406/how-to-disable-mouse-battery- low-notification-in-ubuntu-18-04 1) Description: Ubuntu 18.04.1 LTS Release: 18.04 2) I assume the packet in question is notify-osd, not sure. notify-osd: Installed: (none) Candidate: 0.9.35+16.04.20160415-0ubuntu2 Version table: 0.9.35+16.04.20160415-0ubuntu2 500 500 http://fi.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) I expected that no notifications would appear when notifications are set to off 4) Mouse battery low - notification always appears --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ohto 2927 F...m pulseaudio /dev/snd/controlC0: ohto 2927 F pulseaudio /dev/snd/controlC1: ohto 2927 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-07-28 (79 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=a59cc41b-0147-4609-b6c5-75fa912d2396 ro quiet splash vt.handoff=1 ProcVersionSignature: hostname 4.15.0-36.39-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-36-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/15/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F12 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77X-UP5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrF12:bd05/15/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UP5TH-CF:rvrTobefilledbyO.E.M.: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.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1798166/+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
