[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
Just FTR, note that the change in NM upstream was needed so the network- manager snap was able to correctly detect if udevd is running. We currently build the snap from the source package + some patches including this one. But, the long term target is to be able to create the snap by simply staging the network-manager debs. So, please keep this in mind and try to put back this change as soon as is feasible again, so we do not need to remove the change in the deb and then put it back in the snap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1910235] Re: The mouse stops working after trying to take an area screenshot in some apps on Xorg
** Description changed: - Steps to reproduce this bug: + [ Impact ] + + Mouse stops working after taking an area screenshot + + [ Test case ] 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen - 5. Try to switch between applications using the panel and check the operation of the mouse in other applications besides browser (in my case Slack) - --- + 5. Try to switch between applications using the panel and check the operation of the mousein other applications besides browser (in my case Slack) + + [ Regression potential ] + + Grab events don't happen or pointer isn't ungrabbed when required. + + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME - DisplayManager: gdm3 - DistroRelease: Ubuntu 20.04 + DisplayManager: gdm3DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True -- 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/1910235 Title: The mouse stops working after trying to take an area screenshot in some apps on Xorg Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Released Bug description: [ Impact ] Mouse stops working after taking an area screenshot [ Test case ] 1. Open Chromium browser. 2. Go to the page with the form in which there is a standard browser drop-down menu (form select) 3. Open it 4. Try to take a screenshot with the keyboard shortcut: Ctrl+Shift+PrintScreen 5. Try to switch between applications using the panel and check the operation of the mousein other applications besides browser (in my case Slack) [ Regression potential ] Grab events don't happen or pointer isn't ungrabbed when required. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-10-26 (71 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-58.64-generic 5.4.73 RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2 Tags: focal Uname: Linux 5.4.0-58-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1910235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support
** Changed in: gnome-shell (Ubuntu) Status: In Progress => Fix Committed -- 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/1915570 Title: Login screen password entry not working on systems with fingerprint support Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Fix Committed Bug description: This bug is for the login package. This only affects users of the development release and does not affect stable users. The bug in the password entry causes either the password to be entered only for the login to hang, or when attempting to enter the password, the computer quickly deletes any characters entered as if backspace was being held therefore preventing a user from being able to log in. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-02-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Tags: hirsute Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => In Progress -- 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/1915570 Title: Login screen password entry not working on systems with fingerprint support Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: In Progress Bug description: This bug is for the login package. This only affects users of the development release and does not affect stable users. The bug in the password entry causes either the password to be entered only for the login to hang, or when attempting to enter the password, the computer quickly deletes any characters entered as if backspace was being held therefore preventing a user from being able to log in. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-02-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Tags: hirsute Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915674] Re: Sharing folder in Files: "net usershare" returned error 255
Reassigning this to samba, this can't be fixed in nautilus-share ** Package changed: nautilus-share (Ubuntu) => samba (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1915674 Title: Sharing folder in Files: "net usershare" returned error 255 Status in samba package in Ubuntu: New Bug description: I'm just guessing package name since I can't simply read my way to that information in the GUI... I'm trying to share my games folder on the network by right clicking and selecting the Share on local network option. I tick Share this folder, and confirm. I expected the folder to be shared, but instead I get the message: "net usershare" returned error 255: net usershare add: share name games is already a valid system user name Ubuntu 20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 02:05:28 2021 InstallationDate: Installed on 2020-10-30 (107 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1915674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support
Ok it's handled in https://gitlab.gnome.org/GNOME/gnome- shell/-/merge_requests/1683 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3734 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3734 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3734 Importance: Unknown Status: Unknown -- 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/1915570 Title: Login screen password entry not working on systems with fingerprint support Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Bug description: This bug is for the login package. This only affects users of the development release and does not affect stable users. The bug in the password entry causes either the password to be entered only for the login to hang, or when attempting to enter the password, the computer quickly deletes any characters entered as if backspace was being held therefore preventing a user from being able to log in. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-02-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Tags: hirsute Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1915570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915771] [NEW] Thunderbird randomly inserts string
Public bug reported: How ik happens I don't know, because I notice this only later, but some string gets inserted at seemingly random place. Ctrl-Z undoes it. See attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.10.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: humphrey 2229 F pulseaudio /dev/snd/pcmC0D0p: humphrey 2229 F...m pulseaudio BuildID: 20200629235513 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Feb 16 14:14:35 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1138 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/thunderbird/thunderbird ForcedLayersAccel: False InstallationDate: Installed on 2021-01-14 (33 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.0.1 dev eno1 proto dhcp metric 100 default via 192.168.1.1 dev wlx001325ad55e1 proto dhcp metric 600 169.254.0.0/16 dev wlx001325ad55e1 scope link metric 1000 192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.10 metric 100 192.168.1.0/24 dev wlx001325ad55e1 proto kernel scope link src 192.168.1.103 metric 600 MostRecentCrashID: bp-d8ee9043-ef35-483e-8c89-c1b0d0181224 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1138 Profile1PrefSources: prefs.js Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile1 - LastVersion=68.10.0/20200629235513 Profile0 (Default) - LastVersion=68.10.0/20200629235513 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/14/2020 dmi.bios.release: 2.48 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.48 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.39 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.ec.firmware.release: 5.57 dmi.modalias: dmi:bvnHP:bvrN01Ver.02.48:bd07/14/2020:br2.48:efr5.57:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.39:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: L1G76AV dmi.sys.vendor: HP ** Affects: thunderbird (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "Re: Een repliek..html" https://bugs.launchpad.net/bugs/1915771/+attachment/5464006/+files/Re%3A%20Een%20repliek..html -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1915771 Title: Thunderbird randomly inserts string Status in thunderbird package in Ubuntu: New Bug description: How ik happens I don't know, because I notice this only later, but some string gets inserted at seemingly random place. Ctrl-Z undoes it. See attached. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: thunderbird 1:68.10.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: humphrey 2229 F pulseaudio /dev/snd/pcmC0D0p: humphrey 2229 F...m pulseaudio BuildID: 20200629235513 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Tue Feb 16 14:14:35 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/thunderbird/omni.ja:greprefs.js:1138 DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ExecutablePath: /usr/lib/thunderbird/thunderbird ForcedLayersAccel: False InstallationDate: Installed on 2021-01-14 (33 days ago) InstallationMedia: Ubuntu
Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi Maton,
On Mon, Feb 15, 2021 at 08:46:57AM -, Maton Danko wrote:
>I've checked the 5.11.0-rc7 and the touchpad still doesn't work
>properly, on the left and right bottom side the same primary action is
>being taken instead of secondary on the right and primary on the left!
>
5.11.0-rc7 is expected to fix your touchpad. Could you paste the output of
"sudo cat /sys/kernel/debug/gpio|grep pin130 -A1" and also the output of
"sudo evest" when you lick the left bottom and right bottom button?
>--
>You received this bug notification because you are subscribed to the bug
>report.
>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:
> Fix Committed
>Status in linux package in Fedora:
> Confirmed
>Status in linux package in openSUSE:
> New
>
>Bug description:
> Update (based on #296)
> =
>
> The latest kernel tree
> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
> has the complete solution to fix this bug. So we can expect kernel
> v5.11 to fix this issue without any additional work.
>
> Before the release of v5.11, you are suggested to use #189 to save your
> touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
> driver is built into the initramfs. So you have to rebuild the initramfs
> after replacing the old module with new one.
> On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
> -u`.
>
> The complete solution is three patches,
> - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
> filter setting in IRQ type setting")
> - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect
> way to disable debounce filter")
> - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
> account debounce settings")
>
> The first two patches has reached the stable tree. If the last one is
> also backported to LTS kernel, you won't need to install kernel 5.11.
> But I don't know when this will happen.
>
> Original bug report
> ===
>
> 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 Mouseid=16 [slave pointer
> (2)]
> ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Control id=12 [slave
> pointer (2)]
> ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
> (2)]
> ⎣ Virtual core keyboard id=3[master keyboard (2)]
> ↳ Virtual core XTEST keyboardid=5[slave
> keyboard (3)]
> ↳ Ideapad extra buttons id=15 [slave
> keyboard (3)]
> ↳ Power Button id=6[slave
> keyboard (3)]
> ↳ Integrated Camera: Integrated Cid=10 [slave
> keyboard (3)]
> ↳ Video Bus id=7[slave
> keyboard (3)]
> ↳ ITE Tech. Inc. ITE Device(8910) Consumer Control id=19 [slave
> keyboard (3)]
> ↳ Power Button id=9[slave
> keyboard (3)]
> ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
> keyboard (3)]
> ↳ ITE Tech. Inc. ITE Device(8910) Keyboard id=14 [slave
> keyboard (3)]
> ↳ AT Translated Set 2 keyboard id=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:
> USER
Re: [Desktop-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hi resolve,
On Sun, Feb 14, 2021 at 04:09:09PM -, roselove wrote:
>Hi, I think I personally tried everything from bbs.archlinux.org,
>forum.manjaro.org, reddit, https://github.com/coiby/standalone_i2c_hid,
>bugzilla, bugs.launchpad.net, etc...
>
>I tried Coiby solution this very day (2021-02-14).
>
>Nothing ever worked since I updated to 9.7 kernel (coiby solution was
>nice before that ^^)
>
>Here is my lenovo model :
>https://psref.lenovo.com/Detail/Legion/Lenovo_Legion_5_15ARH05?M=82B50015FR
>
>Here is my touchpad model :
>```
>Input device ID: bus 0x18 vendor 0x6cb product 0x7f28 version 0x100
>Input device name: "MSFT0001:00 06CB:7F28 Touchpad"
>```
>
>evtest gives that btw :
>```
>Testing ... (interrupt to exit)
>expected 24 bytes, got -1
>
>evtest: error reading: No such device
>```
>
Did the above error happens when using
https://github.com/coiby/standalone_i2c_hid?
Have you tried what's suggested in the bug description?
>Now I'm running on `Kernel: 5.10.15-1-MANJARO`, I never managed to make
>touchpad OR brightness work \o/, I guess I'll need to reinstall
>everything someday but if anyone have any clue I guess I'll take it :D
>
As for the brightness issue, https://github.com/Askannz/optimus-manager/
works for me.
>--
>You received this bug notification because you are subscribed to the bug
>report.
>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:
> Fix Committed
>Status in linux package in Fedora:
> Confirmed
>Status in linux package in openSUSE:
> New
>
>Bug description:
> Update (based on #296)
> =
>
> The latest kernel tree
> (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
> has the complete solution to fix this bug. So we can expect kernel
> v5.11 to fix this issue without any additional work.
>
> Before the release of v5.11, you are suggested to use #189 to save your
> touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
> driver is built into the initramfs. So you have to rebuild the initramfs
> after replacing the old module with new one.
> On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
> -u`.
>
> The complete solution is three patches,
> - 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
> filter setting in IRQ type setting")
> - 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect
> way to disable debounce filter")
> - 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
> account debounce settings")
>
> The first two patches has reached the stable tree. If the last one is
> also backported to LTS kernel, you won't need to install kernel 5.11.
> But I don't know when this will happen.
>
> Original bug report
> ===
>
> 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 Mouseid=16 [slave pointer
> (2)]
> ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Control id=12 [slave
> pointer (2)]
> ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer
> (2)]
> ⎣ Virtual core keyboard id=3[master keyboard (2)]
> ↳ Virtual core XTEST keyboardid=5[slave
> keyboard (3)]
> ↳ Ideapad extra buttons id=15 [slave
> keyboard (3)]
> ↳ Power Button id=6[slave
> keyboard (3)]
> ↳ Integrated Camera: Integrated Cid=10 [slave
> keyboard (3)]
> ↳ Video Bus id=7[slave
> keyboard (3)]
> ↳ ITE Tech. Inc. ITE Device(8910) Consumer Control id=19 [slave
> keyboard (3)]
> ↳ Power Button id=9[slave
> keyboard (3)]
> ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave
> keyboard (3)]
> ↳ ITE Tech. Inc. ITE
[Desktop-packages] [Bug 1915674] Re: Sharing folder in Files: "net usershare" returned error 255
Thanks for the suggestion for a workaround. If true, sounds like an unreasonable limitation and implementation detail worthy of someone's attention, considering it is entirely reasonable to create a share called "games". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1915674 Title: Sharing folder in Files: "net usershare" returned error 255 Status in nautilus-share package in Ubuntu: New Bug description: I'm just guessing package name since I can't simply read my way to that information in the GUI... I'm trying to share my games folder on the network by right clicking and selecting the Share on local network option. I tick Share this folder, and confirm. I expected the folder to be shared, but instead I get the message: "net usershare" returned error 255: net usershare add: share name games is already a valid system user name Ubuntu 20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 02:05:28 2021 InstallationDate: Installed on 2020-10-30 (107 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1915674/+subscriptions -- Mailing list: https://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 1915674] [NEW] Sharing folder in Files: "net usershare" returned error 255
On Mon, Feb 15, 2021 at 04:21:02PM -, Launchpad Bug Tracker wrote: > You have been subscribed to a public bug: > > I'm just guessing package name since I can't simply read my way to that > information in the GUI... > > I'm trying to share my games folder on the network by right clicking and > selecting the Share on local network option. > > I tick Share this folder, and confirm. I expected the folder to be > shared, but instead I get the message: > > "net usershare" returned error 255: net usershare add: share name games > is already a valid system user name Well it sounds like you can't have a share with the same name as a username, and there's a `games` user in Ubuntu by default. Pick another share name perhaps? -- Kind regards, Loong Jin -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1915674 Title: Sharing folder in Files: "net usershare" returned error 255 Status in nautilus-share package in Ubuntu: New Bug description: I'm just guessing package name since I can't simply read my way to that information in the GUI... I'm trying to share my games folder on the network by right clicking and selecting the Share on local network option. I tick Share this folder, and confirm. I expected the folder to be shared, but instead I get the message: "net usershare" returned error 255: net usershare add: share name games is already a valid system user name Ubuntu 20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 02:05:28 2021 InstallationDate: Installed on 2020-10-30 (107 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1915674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908502] Re: [MIR] libdeflate
** No longer affects: tiff (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tiff in Ubuntu. https://bugs.launchpad.net/bugs/1908502 Title: [MIR] libdeflate Status in libdeflate package in Ubuntu: New Status in libdeflate source package in Hirsute: New Bug description: * Availability In sync with Debian, built on all architectures https://launchpad.net/ubuntu/+source/libdeflate/1.7-1 * Rationale It's a new depends of libtiff * Security There is no known security issues https://security-tracker.debian.org/tracker/source-package/libdeflate https://people.canonical.com/~ubuntu-security/cve/pkg/libdeflate.html https://cve.mitre.org/cgi-bin/cvekey.cgi?keyword=libdeflate * Quality assurance The desktop team is going to subscribe to the package https://launchpad.net/ubuntu/+source/libdeflate/+bugs https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=libdeflate No open reports The package enables upstream tests during the build and ships basic autopkgtests * Dependencies No universe binary dependencies * Standards compliance current 4.5.1 standards-version, debhelper compat 13, dh style simple rules * Maintenance Upstream is active, the package is maintained in Debian and in sync for Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdeflate/+bug/1908502/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1874120] Re: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error e
Atualizei o sistema Operacional do meu notebook e quando tentei abrir um arquivo ele não abriu e não consegui restaura-lo -- 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/1874120 Title: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 Status in chromium-browser package in Ubuntu: Expired Bug description: error appeared when opening chrome ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 DRM.card0-HDMI-A-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEaTDjAQEBAQkXAQOAMBt47umEpVVImyYSUFQBAQEBAQEBAQEBAQEBAQEBAjqAGHE4LUBYLEUA3w0RAAAe/QAwTBhkCgAKICAgICAg/ABFVDIyMjFJCiAgICAg/wBBU1VTMjAxMzAzMDEKAEI= modes: 1920x1080 DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: Date: Tue Apr 21 23:33:33 2020 Desktop-Session: 'None' 'None' 'None' Env: 'None' 'None' ErrorMessage: new chromium-browser package pre-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-03-28 (1851 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Load-Avg-1min: 3.38 Load-Processes-Running-Percent: 0.2% MachineType: ASUSTeK COMPUTER INC. ET2221I-B85 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-96-generic root=UUID=e54296a0-874c-412b-9fc6-092c89bdfa74 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 80.0.3987.163-0ubuntu0.18.04.1 failed to install/upgrade: new chromium-browser package pre-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-04-21 (0 days ago) dmi.bios.date: 11/05/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: ET2221I-B85 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd11/05/2013:svnASUSTeKCOMPUTERINC.:pnET2221I-B85:pvr0503:rvnASUSTeKCOMPUTERINC.:rnET2221I-B85:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: All-In-One dmi.product.name: ET2221I-B85 dmi.product.version: 0503 dmi.sys.vendor: ASUSTeK COMPUTER INC. modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874120/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915605] Re: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5
The best way to find this bug is. 1) Start firefox 2) Move your cursor to the top of the screen on place with date and time or other place on the top of the screen (on the left or the right from the date and time place). 3) Now you can noticed that your cursor is "busy" but only when you have your cursor on the top of the screen. When you move cursor to the centre of the screen outside top of the screen cursor return to normal animation. Sorry for my English but I hope that you now understand me. P.S. I noticed also that if I will start firefox for the first time from the boot my system this bug is not affected but I think that firefox start longer than when I run this for the second and next times so maybe I can't see this bug. On Ubuntu 20.04 I don't have this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1915605 Title: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5 Status in firefox package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I have problem with Firefox on Ubuntu 18.04.5 system. When I run firefox this loading too long (circle spinning - animation of my cursor). I noticed this bug also on Xubuntu 18.04.4 on another computer. On Lubuntu 18.04.5 system on another computer I don't have these kind of bug so it is problem with Ubuntu and Xubuntu system. On Ubuntu 20.04 and Ubuntu 20.04.1 I don't have these bug. Of course I have updated system. I noticed also that if I will run firefox for the first time after booting my system this bug is not exist. I have this bug for the second run of the firefox and next. I have this problem also booting my computer with live USB with clear system image with Ubuntu 18.04.5. Like I earlier said this is problem with the system. When I use Ubuntu 20.04 I don't have this problem. My system is clean this is fresh install. I don't know what is problem but I am sure that everyone with Ubuntu 18.04.5 have this problem. Firefox is the newest 85.0.1 version. On older vesion I also had this problem in Ubuntu 18.04.5. Firefox start with no errors. No errors is a shown in terminal. Problem is with spinning with the cursor. When I run firefox cursor is spinning but firefox normally works. This cursor spinning only when I move this cursor on GNOME environment (top of the screen I don't know what is the name of this. This is graphic bar? When I run firefox in this "graphic bar" are shown name of the program (in my case firefox). On Ubuntu 20.04 my cursor doesn't spinning. Like I said this is problem only with Ubuntu 18.04.5 and Xubuntu 18.04.4 system. So this is the problem with bionic family but on Lubuntu 18.04.4 and 18.04.5 and doesn't have this problem too. I tried reinstall firefox but this doesn't help. I also deleted files for firex in /home but this also doesn't help. I think that this problem is more complicated. Can you fix it? I am sure that everyone have this problem. Some output from terminal: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1915605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915605] Re: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5
The best way to way to find this bug is. 1) Start firefox 2) Move your cursor to the top of the screen near place with date and time. 3) Now you can noticed that your cursor is "busy" Sorry for my English but I hope that you understand me. P.S. I noticed also that if I will start firefox for the first time from the boot my system this bug is not affected but I think that firefox start longer than when I run this for the second and next times so maybe I can't see this bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1915605 Title: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5 Status in firefox package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I have problem with Firefox on Ubuntu 18.04.5 system. When I run firefox this loading too long (circle spinning - animation of my cursor). I noticed this bug also on Xubuntu 18.04.4 on another computer. On Lubuntu 18.04.5 system on another computer I don't have these kind of bug so it is problem with Ubuntu and Xubuntu system. On Ubuntu 20.04 and Ubuntu 20.04.1 I don't have these bug. Of course I have updated system. I noticed also that if I will run firefox for the first time after booting my system this bug is not exist. I have this bug for the second run of the firefox and next. I have this problem also booting my computer with live USB with clear system image with Ubuntu 18.04.5. Like I earlier said this is problem with the system. When I use Ubuntu 20.04 I don't have this problem. My system is clean this is fresh install. I don't know what is problem but I am sure that everyone with Ubuntu 18.04.5 have this problem. Firefox is the newest 85.0.1 version. On older vesion I also had this problem in Ubuntu 18.04.5. Firefox start with no errors. No errors is a shown in terminal. Problem is with spinning with the cursor. When I run firefox cursor is spinning but firefox normally works. This cursor spinning only when I move this cursor on GNOME environment (top of the screen I don't know what is the name of this. This is graphic bar? When I run firefox in this "graphic bar" are shown name of the program (in my case firefox). On Ubuntu 20.04 my cursor doesn't spinning. Like I said this is problem only with Ubuntu 18.04.5 and Xubuntu 18.04.4 system. So this is the problem with bionic family but on Lubuntu 18.04.4 and 18.04.5 and doesn't have this problem too. I tried reinstall firefox but this doesn't help. I also deleted files for firex in /home but this also doesn't help. I think that this problem is more complicated. Can you fix it? I am sure that everyone have this problem. Some output from terminal: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1915605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915605] Re: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5
Hi Olivier, I know of other users who are observing the same problem. Like I earlier said on other machine I noticed this same bug also. This is my father machine with Xubuntu 18.04.4. This bug was frustrating my father so I decided to install Lubuntu 18.04.4 and this problem not exist on Lubuntu system. Firefox start normally. This start in a reasonable time frame but "busy" cursor remains on even after app has started. So like you said. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1915605 Title: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5 Status in firefox package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I have problem with Firefox on Ubuntu 18.04.5 system. When I run firefox this loading too long (circle spinning - animation of my cursor). I noticed this bug also on Xubuntu 18.04.4 on another computer. On Lubuntu 18.04.5 system on another computer I don't have these kind of bug so it is problem with Ubuntu and Xubuntu system. On Ubuntu 20.04 and Ubuntu 20.04.1 I don't have these bug. Of course I have updated system. I noticed also that if I will run firefox for the first time after booting my system this bug is not exist. I have this bug for the second run of the firefox and next. I have this problem also booting my computer with live USB with clear system image with Ubuntu 18.04.5. Like I earlier said this is problem with the system. When I use Ubuntu 20.04 I don't have this problem. My system is clean this is fresh install. I don't know what is problem but I am sure that everyone with Ubuntu 18.04.5 have this problem. Firefox is the newest 85.0.1 version. On older vesion I also had this problem in Ubuntu 18.04.5. Firefox start with no errors. No errors is a shown in terminal. Problem is with spinning with the cursor. When I run firefox cursor is spinning but firefox normally works. This cursor spinning only when I move this cursor on GNOME environment (top of the screen I don't know what is the name of this. This is graphic bar? When I run firefox in this "graphic bar" are shown name of the program (in my case firefox). On Ubuntu 20.04 my cursor doesn't spinning. Like I said this is problem only with Ubuntu 18.04.5 and Xubuntu 18.04.4 system. So this is the problem with bionic family but on Lubuntu 18.04.4 and 18.04.5 and doesn't have this problem too. I tried reinstall firefox but this doesn't help. I also deleted files for firex in /home but this also doesn't help. I think that this problem is more complicated. Can you fix it? I am sure that everyone have this problem. Some output from terminal: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1915605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854371] Re: Input lag with Razer Naga Trinity mouse
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg-server (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854371 Title: Input lag with Razer Naga Trinity mouse Status in xorg-server package in Ubuntu: Confirmed Bug description: When pressing multiple keys on my keyboard (Roccat isku FX) and pressing repetitively the buttons on the "numpad" (side buttons) of my mouse (Razer Naga Trinity) at the same time, the system freeze while doing this. All become normal again when I stop doing this. While freezing, I can see the Xorg process going up to 60/70% of the CPU. Not sure if it is a Xorg or driver related problem, or anything else. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 28 15:25:50 2019 DistUpgraded: 2019-10-25 11:21:07,314 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-22-generic, x86_64: installed nvidia, 435.21, 5.3.0-23-generic, x86_64: installed openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-22-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] [19da:1385] MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=eabe8e30-c27a-4b40-8af2-38ffd8bcbcc9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-25 (34 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd02/28/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854371] Re: Input lag with Razer Naga Trinity mouse
I have the exact same issue described here on Ubuntu 20.04/10. Any solution to this? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1854371 Title: Input lag with Razer Naga Trinity mouse Status in xorg-server package in Ubuntu: Confirmed Bug description: When pressing multiple keys on my keyboard (Roccat isku FX) and pressing repetitively the buttons on the "numpad" (side buttons) of my mouse (Razer Naga Trinity) at the same time, the system freeze while doing this. All become normal again when I stop doing this. While freezing, I can see the Xorg process going up to 60/70% of the CPU. Not sure if it is a Xorg or driver related problem, or anything else. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 28 15:25:50 2019 DistUpgraded: 2019-10-25 11:21:07,314 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: L’exécution du processus fils « ./xorg_fix_proprietary.py » a échoué (Aucun fichier ou dossier de ce type) (8)) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-22-generic, x86_64: installed nvidia, 435.21, 5.3.0-23-generic, x86_64: installed openrazer-driver, 2.6.0, 5.3.0-23-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-22-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-23-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GM206 [GeForce GTX 960] [10de:1401] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GM206 [GeForce GTX 960] [19da:1385] MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=eabe8e30-c27a-4b40-8af2-38ffd8bcbcc9 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to eoan on 2019-10-25 (34 days ago) dmi.bios.date: 02/28/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1801:bd02/28/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1854371/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915750] Re: with wifi on, bluetooth speaker output sound is stuttering / garbled / jittery
** Package changed: ubuntu => bluez (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1915750 Title: with wifi on, bluetooth speaker output sound is stuttering / garbled / jittery Status in bluez package in Ubuntu: New Bug description: That seems to be the oldest unresolved bug around here (https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 Uname: Linux 5.3.18-050318-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 19:53:07 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2019-04-10 (677 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.18-050318-generic root=UUID=8cd56bb5-4fcb-4c5b-a4ba-f5dd560e9f9c ro elevator=noop alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-20 (117 days ago) dmi.bios.date: 03/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 00FK8Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd03/06/2019:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn00FK8Y:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 0885 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:39:1F:29 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:538991 acl:390 sco:2748 events:51466 errors:0 TX bytes:24976655 acl:37033 sco:2712 commands:14348 errors:0 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.bluetooth.main.conf: 2019-05-01T23:43:26.699874 mtime.conffile..etc.default.apport: 2019-04-24T22:54:58.031610 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1915750/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915750] [NEW] with wifi on, bluetooth speaker output sound is stuttering / garbled / jittery
You have been subscribed to a public bug: That seems to be the oldest unresolved bug around here (https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/424215) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1.1 Uname: Linux 5.3.18-050318-generic x86_64 NonfreeKernelModules: wl nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 19:53:07 2021 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 InstallationDate: Installed on 2019-04-10 (677 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.18-050318-generic root=UUID=8cd56bb5-4fcb-4c5b-a4ba-f5dd560e9f9c ro elevator=noop alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to groovy on 2020-10-20 (117 days ago) dmi.bios.date: 03/06/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.8.1 dmi.board.name: 00FK8Y dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.8.1:bd03/06/2019:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn00FK8Y:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 0885 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: Primary Bus: USB BD Address: 98:2C:BC:39:1F:29 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:538991 acl:390 sco:2748 events:51466 errors:0 TX bytes:24976655 acl:37033 sco:2712 commands:14348 errors:0 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.bluetooth.main.conf: 2019-05-01T23:43:26.699874 mtime.conffile..etc.default.apport: 2019-04-24T22:54:58.031610 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- with wifi on, bluetooth speaker output sound is stuttering / garbled / jittery https://bugs.launchpad.net/bugs/1915750 You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support
No need for further testing, this seems to happen when a fingerprint reader is in the system but no prints are enrolled for the user. So I'm working upstream to fix this to handle the unavailable-service case in shell. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915570 Title: Login screen password entry not working on systems with fingerprint support Status in gnome-shell package in Ubuntu: Confirmed Bug description: This bug is for the login package. This only affects users of the development release and does not affect stable users. The bug in the password entry causes either the password to be entered only for the login to hang, or when attempting to enter the password, the computer quickly deletes any characters entered as if backspace was being held therefore preventing a user from being able to log in. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-02-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Tags: hirsute Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915751] [NEW] Sharing is enabled out of the box
Public bug reported: Apologies if this is the wrong package. Using Ubuntu Budgie I note that GNOME Settings - Sharing is enabled by default and that "Remote Login" is ticked to be on. This could be construed as a security issue. I would have expected a user to enable if sharing should be possible - certainly "Remote Login" shouldnt be enabled by default out-of-the-box. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-settings-daemon 3.38.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Mon Feb 15 19:01:17 2021 InstallationDate: Installed on 2021-02-08 (6 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210208) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute third-party-packages -- 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/1915751 Title: Sharing is enabled out of the box Status in gnome-settings-daemon package in Ubuntu: New Bug description: Apologies if this is the wrong package. Using Ubuntu Budgie I note that GNOME Settings - Sharing is enabled by default and that "Remote Login" is ticked to be on. This could be construed as a security issue. I would have expected a user to enable if sharing should be possible - certainly "Remote Login" shouldnt be enabled by default out-of-the- box. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-settings-daemon 3.38.1-3ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18 Uname: Linux 5.8.0-36-generic x86_64 ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: Budgie:GNOME Date: Mon Feb 15 19:01:17 2021 InstallationDate: Installed on 2021-02-08 (6 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Alpha amd64 (20210208) SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1915751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915744] Re: System settings power saving section has misleading wording
** Description changed: The power saving section of system settings has the title "Power saving" (all GUI text is translated to English in this report, but I suspect the wording is similar enough in the English localization of the UI that the points still stand). There are some problems with that title in combination with the actual options in that section: - Screen backlight level - Automatic backlight level - Keyboard backlight level - Dim screen when inactive - Empty screen (after interval) - Automatic suspend - Wireless network: The wireless network can be turned off to save power. - Bluetooth: Bluetooth can be turned off to save power. 1. Let's start with the problem with the two bottommost controls (wireless network, and bluetooth). Their subtitles in combination with the section title "Power saving" gives a very clear impression that these settings enable/disable *the ability for these components to be automatically turned off in order to save power*, but that's not what they do at all. They're just switches to turn off the components manually, as though the focus of this section weren't to automate power saving but to offer manual controls that are already available not only in their own respective setions of system settings, but readily available at any time in the global system menu in the top right corner of the desktop. There's no good reason to believe that the Power saving switches are just triply redundant instances of these already highly available switches, since no one is actually that interested in manually managing their power saving from a buried panel in system settings every time they decide to go battery powered or are critically low on battery. What's expected in this section are settings unique to power saving, like automating it during battery power, as opposed to just general preferences about whether you need wifi or bluetooth. It doesn't hurt to suggest turning the transmitters off in the power saving section, but doing it this way is misleading. I mistakenly turned off the Bluetooth transmitter in this way in an attempt to prevent the system from automatically power it off, during my efforts to troubleshoot Bluetooth. Needless to say, that didn't help, and I was later surprised to discover that Bluetooth was off. 2. The other problem in the Power saving section is that many of the settings aren't really about power saving strategies -- they're just general preferences that would have to be adjusted manually every single time you want to save power: - Screen backlight level - Keyboard backlight level - Wireless network: The wireless network can be turned off to save power. - Bluetooth: Bluetooth can be turned off to save power. Sure, they technically have the potential to save power, but then they would have to be micromanaged all the time, i.e. not very useful in practice if you're using battery power on a daily basis. You would have to be extremely proactive for these settings to be preventative of needlessly draining your battery, and they're instead very likely going to be used when it's "too late" and you're already low on battery. Here are the ones actually concerned with power saving strategies, i.e. preventing battery from draining prematurely: - Automatic backlight level - Dim screen when inactive - Empty screen (after interval) - Automatic suspend Notice how you don't have to babysit these settings every time you decide to use battery power, and how they're actually focused on the problem of conserving power before it's too late. To alleviate these issues, the easiest quick fix would be to: 1. either remove or change the subtitles of the two bottommost to something like "WiFi/Bluetooth can consume a lot of power" which succinctly explains why these switches are here while at the same time not misleading the reader to think the switches control something else. 2. Move the "micromanagement settings" to their own section to clearly separate the more relevant "power conservation strategies" from the - "general user preferences for devices with potential for high power + "general user preferences for components with potential for high power consumption that can be manually adjusted here if you're in a pinch and are critically low on battery". The less easy fix would of course be to offer automatic keyboard backlight levels instead of manual controls, and to offer actual automatic wifi and bluetooth power saving (if that's a thing). Not to mention a general "power saving" mode, which is the reasonable level at which regular power saving could be expected to be managed manually. Ubuntu 20.10 gnome-control-center 3.38.3 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu.
[Desktop-packages] [Bug 1915744] [NEW] System settings power saving section has misleading wording
Public bug reported: The power saving section of system settings has the title "Power saving" (all GUI text is translated to English in this report, but I suspect the wording is similar enough in the English localization of the UI that the points still stand). There are some problems with that title in combination with the actual options in that section: - Screen backlight level - Automatic backlight level - Keyboard backlight level - Dim screen when inactive - Empty screen (after interval) - Automatic suspend - Wireless network: The wireless network can be turned off to save power. - Bluetooth: Bluetooth can be turned off to save power. 1. Let's start with the problem with the two bottommost controls (wireless network, and bluetooth). Their subtitles in combination with the section title "Power saving" gives a very clear impression that these settings enable/disable *the ability for these components to be automatically turned off in order to save power*, but that's not what they do at all. They're just switches to turn off the components manually, as though the focus of this section weren't to automate power saving but to offer manual controls that are already available not only in their own respective setions of system settings, but readily available at any time in the global system menu in the top right corner of the desktop. There's no good reason to believe that the Power saving switches are just triply redundant instances of these already highly available switches, since no one is actually that interested in manually managing their power saving from a buried panel in system settings every time they decide to go battery powered or are critically low on battery. What's expected in this section are settings unique to power saving, like automating it during battery power, as opposed to just general preferences about whether you need wifi or bluetooth. It doesn't hurt to suggest turning the transmitters off in the power saving section, but doing it this way is misleading. I mistakenly turned off the Bluetooth transmitter in this way in an attempt to prevent the system from automatically power it off, during my efforts to troubleshoot Bluetooth. Needless to say, that didn't help, and I was later surprised to discover that Bluetooth was off. 2. The other problem in the Power saving section is that many of the settings aren't really about power saving strategies -- they're just general preferences that would have to be adjusted manually every single time you want to save power: - Screen backlight level - Keyboard backlight level - Wireless network: The wireless network can be turned off to save power. - Bluetooth: Bluetooth can be turned off to save power. Sure, they technically have the potential to save power, but then they would have to be micromanaged all the time, i.e. not very useful in practice if you're using battery power on a daily basis. You would have to be extremely proactive for these settings to be preventative of needlessly draining your battery, and they're instead very likely going to be used when it's "too late" and you're already low on battery. Here are the ones actually concerned with power saving strategies, i.e. preventing battery from draining prematurely: - Automatic backlight level - Dim screen when inactive - Empty screen (after interval) - Automatic suspend Notice how you don't have to babysit these settings every time you decide to use battery power, and how they're actually focused on the problem of conserving power before it's too late. To alleviate these issues, the easiest quick fix would be to: 1. either remove or change the subtitles of the two bottommost to something like "WiFi/Bluetooth can consume a lot of power" which succinctly explains why these switches are here while at the same time not misleading the reader to think the switches control something else. 2. Move the "micromanagement settings" to their own section to clearly separate the more relevant "power conservation strategies" from the "general user preferences for devices with potential for high power consumption that can be manually adjusted here if you're in a pinch and are critically low on battery". The less easy fix would of course be to offer automatic keyboard backlight levels instead of manual controls, and to offer actual automatic wifi and bluetooth power saving (if that's a thing). Not to mention a general "power saving" mode, which is the reasonable level at which regular power saving could be expected to be managed manually. Ubuntu 20.10 gnome-control-center 3.38.3 ** Affects: nautilus-share (Ubuntu) Importance: Undecided Status: New ** Description changed: The power saving section of system settings has the title "Power saving" (all GUI text is translated to English in this report, but I suspect the wording is similar enough in the English localization of the UI that the points still stand). There are some problems with that title in combination with
[Desktop-packages] [Bug 1908049] Re: Firefox cannot open pdf with viewer (evince)
Sorry this bug shouldn't have expired as the required information was provided. Manfred, in your handlers.json the action for application/pdf is 2, which corresponds to "Always Ask". Is it not what happens when you open a PDF file from within firefox? Or is it that the behaviour differs when it is a local file vs a distant resource? ** Changed in: firefox (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1908049 Title: Firefox cannot open pdf with viewer (evince) Status in firefox package in Ubuntu: New Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 Package: firefox 83.0+build2-0ubuntu0.20.04.1 firefox: Installiert: 83.0+build2-0ubuntu0.20.04.1 Installationskandidat: 83.0+build2-0ubuntu0.20.04.1 Versionstabelle: *** 83.0+build2-0ubuntu0.20.04.1 500 500 http://at.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 75.0+build3-0ubuntu1 500 500 http://at.archive.ubuntu.com/ubuntu focal/main amd64 Packages Expecting: Changing the Firefox PDF setting from "Open in Firefox" to "Use system default application" leads to opening pdf resources with evince. What happend instead: pdf resources are opend inside firefox with internal viewer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1908049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915641] Re: I was wathing youtube and the ubuntu froze. i'm runing ubuntu 20.04.2 64-bit on a ZOTAC ZBOX with 15.6 Gb mem, INTEL I5-7500T CPU, GeForce GTX1070, 250GB Disk, GNO
Does that happen everytime you watch a video (or that particular video) on youtube? Can you elaborate on what happened? I understand that the system froze, did you have to force a reboot to recover a working state? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1915641 Title: I was wathing youtube and the ubuntu froze. i'm runing ubuntu 20.04.2 64-bit on a ZOTAC ZBOX with 15.6 Gb mem, INTEL I5-7500T CPU, GeForce GTX1070, 250GB Disk, GNOME 3.36.8 Status in firefox package in Ubuntu: Incomplete Bug description: ubuntu system crashes with the keyboard and mouse not working. restart necessary. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 85.0.1+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: stephan1409 F pulseaudio /dev/snd/controlC1: stephan1409 F pulseaudio BuildID: 20210204182252 CasperMD5CheckResult: skip Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Feb 14 11:47:45 2021 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:353 DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False InstallationDate: Installed on 2021-01-27 (17 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IpRoute: default via 192.168.1.1 dev enp2s0 proto dhcp metric 100 169.254.0.0/16 dev enp2s0 scope link metric 1000 192.168.1.0/24 dev enp2s0 proto kernel scope link src 192.168.1.36 metric 100 ProcEnviron: LANGUAGE=en_BW:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_BW.UTF-8 SHELL=/bin/bash Profile0Extensions: extensions.sqlite corrupt or missing Profile0IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile0Locales: extensions.sqlite corrupt or missing Profile0PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/firefox/omni.ja:greprefs.js:353 Profile0PrefSources: prefs.js Profile0Themes: extensions.sqlite corrupt or missing Profiles: Profile1 (Default) - LastVersion=None/None (Out of date) Profile0 - LastVersion=85.0.1/20210204182252 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2018 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: NA dmi.board.name: ZBOX-EN1070/1060,EN1070K/1060K dmi.board.vendor: ZOTAC dmi.board.version: XX dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd05/10/2018:br5.12:svnZOTAC:pnZBOX-EN1070/1060,EN1070K/1060K:pvrXX:rvnZOTAC:rnZBOX-EN1070/1060,EN1070K/1060K:rvrXX:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: NA dmi.product.name: ZBOX-EN1070/1060,EN1070K/1060K dmi.product.sku: NA dmi.product.version: XX dmi.sys.vendor: ZOTAC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1915641/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support
Can you please modify your `/etc/pam.d/gdm-fingerprint` so that it will use: authrequiredpam_fprintd.so debug And then provide me output from: - grep fingerprint /var/log/auth.log It may be useful also enable debugging for gdm into your /etc/gdm3/daemon.conf (and provide journal) ** Changed in: gnome-shell (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1915570 Title: Login screen password entry not working on systems with fingerprint support Status in gnome-shell package in Ubuntu: Confirmed Bug description: This bug is for the login package. This only affects users of the development release and does not affect stable users. The bug in the password entry causes either the password to be entered only for the login to hang, or when attempting to enter the password, the computer quickly deletes any characters entered as if backspace was being held therefore preventing a user from being able to log in. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-02-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Tags: hirsute Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915742] [NEW] gvfsd-google used too much memory
Public bug reported: Problem with `gvfs-google` Description:Ubuntu 20.10 Release:20.10 Package already exist on machine. I want to copy a large file form google drive to my another drive. So i logged it my drive in account. This give me access to dive in nautilus. Now when i copy files between drive to some local drive. Then it should run smooth. And consume normal RAM. When you copy big files like 1-2 files total of 9 GB. Then this package `gvfsd-google` consume enough memory that causes the system to freeze. I have 8 GB of Ram. And it consume all then I have to open tty3, When I used `top` command then I got that it uses enough memory to crash my system. Then i killed it. To regain my responsiveness to my system. This doesn't happened earlier. But it starts happening when i copy large file. It also consume some memory in my 8 GB swapfile. I have added a screenshot of it. ** Affects: gvfs (Ubuntu) Importance: Undecided Status: New ** Tags: gvfsd ** Attachment added: "Live usage report." https://bugs.launchpad.net/bugs/1915742/+attachment/5463853/+files/Screenshot%20from%202021-02-15%2022-47-04.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1915742 Title: gvfsd-google used too much memory Status in gvfs package in Ubuntu: New Bug description: Problem with `gvfs-google` Description: Ubuntu 20.10 Release: 20.10 Package already exist on machine. I want to copy a large file form google drive to my another drive. So i logged it my drive in account. This give me access to dive in nautilus. Now when i copy files between drive to some local drive. Then it should run smooth. And consume normal RAM. When you copy big files like 1-2 files total of 9 GB. Then this package `gvfsd-google` consume enough memory that causes the system to freeze. I have 8 GB of Ram. And it consume all then I have to open tty3, When I used `top` command then I got that it uses enough memory to crash my system. Then i killed it. To regain my responsiveness to my system. This doesn't happened earlier. But it starts happening when i copy large file. It also consume some memory in my 8 GB swapfile. I have added a screenshot of it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1915742/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915712] Re: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected
I'd recommend running what Ian suggested first, before attempting the reinstall that I suggested. This might give valuable information as to what the problem is. -- 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/1915712 Title: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected Status in chromium-browser package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Bug description: happened on do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcmOt9h4RchURAQMIJh546JrlplhJmSMRUFS/7wABAQEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/QA4Sx5TDgAKICAgICAg/wBMNzgwQzA1NDQwNDQK/ABBTDE5MTYKICAgICAgAGE= modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Feb 15 13:26:20 2021 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-27 (1328 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) InstalledPlugins: Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Hewlett-Packard HP Pro3500 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic root=UUID=093e88ea-7b5e-4e39-b56c-03b28ad06dd2 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.17 dmi.board.name: 2ABF dmi.board.vendor: Foxconn dmi.board.version: 3.20 dmi.chassis.asset.tag: CZC34935PY dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.17:bd10/25/2013:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.20:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Pro3500 Series dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1915712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772426] Re: /usr/lib/gvfs/gvfsd-google:11:unregister_mount_callback:g_simple_async_result_complete:complete_in_idle_cb:g_main_dispatch:g_main_context_dispatch
When u copy a large file from google drive it. It takes huge sapace in ram. May be the size of file. Like when u copy 6 gb file or more your device will be freeze. unitll you kill it. ** Attachment added: "Screenshot from 2021-02-15 22-47-04.png" https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1772426/+attachment/5463852/+files/Screenshot%20from%202021-02-15%2022-47-04.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1772426 Title: /usr/lib/gvfs/gvfsd- google:11:unregister_mount_callback:g_simple_async_result_complete:complete_in_idle_cb:g_main_dispatch:g_main_context_dispatch Status in gvfs package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gvfs. This problem was most recently seen with package version 1.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/540d649b23c4ddfe5ab631bf54c5d1a248ed78f9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1772426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772426] Re: /usr/lib/gvfs/gvfsd-google:11:unregister_mount_callback:g_simple_async_result_complete:complete_in_idle_cb:g_main_dispatch:g_main_context_dispatch
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gvfs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1772426 Title: /usr/lib/gvfs/gvfsd- google:11:unregister_mount_callback:g_simple_async_result_complete:complete_in_idle_cb:g_main_dispatch:g_main_context_dispatch Status in gvfs package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gvfs. This problem was most recently seen with package version 1.34.1-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/540d649b23c4ddfe5ab631bf54c5d1a248ed78f9 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1772426/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915605] Re: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5
Hi Piotr, and thanks for the report. Fortunately, this bug/regression hasn't been reported separately, so it's unlikely that it affects everyone as you claim. Do you have actual data to back your claim (i.e. do you know of other users who are observing the same problem?). This is still something that we need to look into, of course. >From your description, it's unclear to me whether the problem is that firefox takes a long time to start up, or whether it starts in a reasonable time frame, but the "busy" cursor remains on even after the app has started? ** Changed in: firefox (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1915605 Title: Firefox (circle spinning while run program) problem on Ubuntu bionic family - 18.04.5 Status in firefox package in Ubuntu: Incomplete Bug description: Dear Launchpad Team, I have problem with Firefox on Ubuntu 18.04.5 system. When I run firefox this loading too long (circle spinning - animation of my cursor). I noticed this bug also on Xubuntu 18.04.4 on another computer. On Lubuntu 18.04.5 system on another computer I don't have these kind of bug so it is problem with Ubuntu and Xubuntu system. On Ubuntu 20.04 and Ubuntu 20.04.1 I don't have these bug. Of course I have updated system. I noticed also that if I will run firefox for the first time after booting my system this bug is not exist. I have this bug for the second run of the firefox and next. I have this problem also booting my computer with live USB with clear system image with Ubuntu 18.04.5. Like I earlier said this is problem with the system. When I use Ubuntu 20.04 I don't have this problem. My system is clean this is fresh install. I don't know what is problem but I am sure that everyone with Ubuntu 18.04.5 have this problem. Firefox is the newest 85.0.1 version. On older vesion I also had this problem in Ubuntu 18.04.5. Firefox start with no errors. No errors is a shown in terminal. Problem is with spinning with the cursor. When I run firefox cursor is spinning but firefox normally works. This cursor spinning only when I move this cursor on GNOME environment (top of the screen I don't know what is the name of this. This is graphic bar? When I run firefox in this "graphic bar" are shown name of the program (in my case firefox). On Ubuntu 20.04 my cursor doesn't spinning. Like I said this is problem only with Ubuntu 18.04.5 and Xubuntu 18.04.4 system. So this is the problem with bionic family but on Lubuntu 18.04.4 and 18.04.5 and doesn't have this problem too. I tried reinstall firefox but this doesn't help. I also deleted files for firex in /home but this also doesn't help. I think that this problem is more complicated. Can you fix it? I am sure that everyone have this problem. Some output from terminal: uname -a 5.4.0-65-generic #73~18.04.1-Ubuntu SMP Tue Jan 19 09:02:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux lsb_release -crid Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1915605/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915712] Re: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected
Hi, @jl-o, on your system can you run in a terminal and share the
output:
journalctl --no-pager -u snapd
snap changes
for err in $(snap changes | grep Error | awk '{print $1}'); do snap tasks $err;
done
Thanks
** Changed in: snapd (Ubuntu)
Status: New => Incomplete
--
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/1915712
Title:
[snap] configure hook fails because the gnome-3-28-1804 platform snap
isn't connected
Status in chromium-browser package in Ubuntu:
Incomplete
Status in snapd package in Ubuntu:
Incomplete
Bug description:
happened on do-release-upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1
ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18
Uname: Linux 4.15.0-135-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
DRM.card0-DP-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-HDMI-A-1:
enabled: disabled
dpms: Off
status: disconnected
edid-base64:
modes:
DRM.card0-VGA-1:
enabled: enabled
dpms: On
status: connected
edid-base64:
AP///wAEcmOt9h4RchURAQMIJh546JrlplhJmSMRUFS/7wABAQEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/QA4Sx5TDgAKICAgICAg/wBMNzgwQzA1NDQwNDQK/ABBTDE5MTYKICAgICAgAGE=
modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 832x624 800x600
800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400
Date: Mon Feb 15 13:26:20 2021
Desktop-Session:
'None'
'None'
'/usr/local/share:/usr/share:/var/lib/snapd/desktop'
Env:
'None'
'None'
ErrorMessage: »neues chromium-browser-Skript des Paketes
pre-installation«-Unterprozess gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2017-06-27 (1328 days ago)
InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215)
InstalledPlugins:
Load-Avg-1min: 0.61
Load-Processes-Running-Percent: 0.2%
MachineType: Hewlett-Packard HP Pro3500 Series
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic
root=UUID=093e88ea-7b5e-4e39-b56c-03b28ad06dd2 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
SourcePackage: chromium-browser
Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to
install/upgrade: »neues chromium-browser-Skript des Paketes
pre-installation«-Unterprozess gab den Fehlerwert 1 zurück
UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: AMI
dmi.bios.version: 8.17
dmi.board.name: 2ABF
dmi.board.vendor: Foxconn
dmi.board.version: 3.20
dmi.chassis.asset.tag: CZC34935PY
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias:
dmi:bvnAMI:bvr8.17:bd10/25/2013:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.20:cvnHewlett-Packard:ct3:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Pro3500 Series
dmi.sys.vendor: Hewlett-Packard
modified.conffile..etc.default.chromium-browser: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1915712/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915712] Re: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected
I added a snapd task, in case there's a potential for race conditions regarding when configure hooks are run. -- 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/1915712 Title: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected Status in chromium-browser package in Ubuntu: Incomplete Status in snapd package in Ubuntu: New Bug description: happened on do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcmOt9h4RchURAQMIJh546JrlplhJmSMRUFS/7wABAQEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/QA4Sx5TDgAKICAgICAg/wBMNzgwQzA1NDQwNDQK/ABBTDE5MTYKICAgICAgAGE= modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Feb 15 13:26:20 2021 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-27 (1328 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) InstalledPlugins: Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Hewlett-Packard HP Pro3500 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic root=UUID=093e88ea-7b5e-4e39-b56c-03b28ad06dd2 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.17 dmi.board.name: 2ABF dmi.board.vendor: Foxconn dmi.board.version: 3.20 dmi.chassis.asset.tag: CZC34935PY dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.17:bd10/25/2013:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.20:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Pro3500 Series dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1915712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880405] Re: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
** Description changed: - O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. - Installiert: 3.36.1-5ubuntu2 - Installationskandidat: 3.36.2-1ubuntu1~20.04.1 - Versionstabelle: - 3.36.2-1ubuntu1~20.04.1 500 - 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages - *** 3.36.1-5ubuntu2 100 - 100 /var/lib/dpkg/status - 3.36.1-5ubuntu1 500 - 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages + [ Impact ] - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + Shell becomes slow and unresponsive flooding journal with JS errors + + [ Test case ] + + 1. Resize the terminal to use half the screen (using CMD+LEFT) + 2. switch it to fullscreen (F11) and back (F11) + 3. Repeat this some number of times ensure we don't end up in a loop with +100% CPU usage. + 4. Ensure that it's still possible to get window focus and the UI is responsive. + + [ Regression potential ] + + Events are ignored for windows which are still visible. + + --- + + O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. + Installiert: 3.36.1-5ubuntu2 + Installationskandidat: 3.36.2-1ubuntu1~20.04.1 + Versionstabelle: + 3.36.2-1ubuntu1~20.04.1 500 + 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages + *** 3.36.1-5ubuntu2 100 + 100 /var/lib/dpkg/status + 3.36.1-5ubuntu1 500 + 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages + + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) - RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 - SourcePackage: gnome-shell + RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) -- 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/1880405 Title: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: [ Impact ] Shell becomes slow and unresponsive flooding journal with JS errors [ Test case ] 1. Resize the terminal to use half the screen (using CMD+LEFT) 2. switch it to fullscreen (F11) and back (F11) 3. Repeat this some number of times ensure we don't end up in a loop with 100% CPU usage. 4. Ensure that it's still possible to get window focus and the UI is responsive. [ Regression potential ] Events are ignored for windows which are still visible. --- O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net
[Desktop-packages] [Bug 1915712] Re: migrating to chromium snap broken 18.04->20.04
Relevant error from DpkgTerminalLog.txt: Fehler: cannot perform the following tasks: - Den Konfigurationshook von Snap "chromium" ausführen, falls vorhanden (run hook "configure": /snap/chromium/1479/snap/command-chain/hooks-configure-desktop: line 43: /snap/chromium/1479/gnome-platform/usr/bin/fc-cache: No such file or directory) This suggests that the gnome-3-28-1804 platform snap wasn't installed/connected at the time the configure hook was run. Can you try running the following command, and let us know how this goes (share the output here if it goes awry): sudo apt reinstall chromium-browser ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete ** Tags added: snap ** Summary changed: - migrating to chromium snap broken 18.04->20.04 + [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1915712 Title: [snap] configure hook fails because the gnome-3-28-1804 platform snap isn't connected Status in chromium-browser package in Ubuntu: Incomplete Status in snapd package in Ubuntu: New Bug description: happened on do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcmOt9h4RchURAQMIJh546JrlplhJmSMRUFS/7wABAQEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/QA4Sx5TDgAKICAgICAg/wBMNzgwQzA1NDQwNDQK/ABBTDE5MTYKICAgICAgAGE= modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Feb 15 13:26:20 2021 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-27 (1328 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) InstalledPlugins: Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Hewlett-Packard HP Pro3500 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic root=UUID=093e88ea-7b5e-4e39-b56c-03b28ad06dd2 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.17 dmi.board.name: 2ABF dmi.board.vendor: Foxconn dmi.board.version: 3.20 dmi.chassis.asset.tag: CZC34935PY dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.17:bd10/25/2013:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.20:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Pro3500 Series dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1915712/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915674] Re: Sharing folder in Files: "net usershare" returned error 255
** Package changed: nautilus (Ubuntu) => nautilus-share (Ubuntu) ** Changed in: nautilus-share (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus-share in Ubuntu. https://bugs.launchpad.net/bugs/1915674 Title: Sharing folder in Files: "net usershare" returned error 255 Status in nautilus-share package in Ubuntu: New Bug description: I'm just guessing package name since I can't simply read my way to that information in the GUI... I'm trying to share my games folder on the network by right clicking and selecting the Share on local network option. I tick Share this folder, and confirm. I expected the folder to be shared, but instead I get the message: "net usershare" returned error 255: net usershare add: share name games is already a valid system user name Ubuntu 20.10 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 15 02:05:28 2021 InstallationDate: Installed on 2020-10-30 (107 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-share/+bug/1915674/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
> @seb128 could you please patch network-manager 1.28 to behave in LXC like it did in 1.26 to let it migrate and not fail in LXC with systemd 247 until the udevd behaviour is fixed in LXC? alright, I can temporarily revert the commit that made it use udev under lxc -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915175] Re: wifi network stops working and shows a green wifi icon
** Package changed: network-manager (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1915175 Title: wifi network stops working and shows a green wifi icon Status in linux package in Ubuntu: New Bug description: I recently started using ubuntu 20.04, I connected it to my 2.4ghz Wi-Fi, at first the wifi worked fine, but suddenly the wifi stopped connecting, and after a few seconds it said "unable to activate network". I checked the "additional drivers tab" and it showed my wifi adapter, but it said "this device is using an alternate driver". right now I'm using my 5ghz Wi-Fi network, but sometimes it happens that it stops working, usually after suspend. UPDATE #1: Apparently it's working now, I suppose it's from an update. Anyways I guess it's fixed. UPDATE #2: it's broken again UPDATE #3: after checking the error a long time I've realized that this error happens when I leave it suspended it for a long time, it is fixed by doing about 3-4 restarts. I'm going to try to use a code that restarts the network-service after suspend, I'll see if it works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 12:09:28 2021 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.8 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2021-02-08T22:50:26.196692 nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 Betancur 5G cda009c8-c845-4366-8436-8e9c44da2cbf /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915175/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915014] Re: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot
I downgraded to 20.04 kernel (5.4.x) and I am still getting the black flashes. BTW, the journal seems to expose the username, so you should warn about that before requesting it. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1915014/+attachment/5463815/+files/journal.txt -- 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/1915014 Title: [amdgpu] [wayland] Screen goes occasionally black after taking a screenshot Status in mutter package in Ubuntu: Incomplete Bug description: Weird issue which has come to my system via updates - possibly the Linux kernel 5.8? Steps to repro: - Take a screenshot (prt scr) - Continue using the computer After I have taken a screenshot, my display gets quick black flashes when using other applications. Manipulating the screenshot with Pinta, opening web browser, etc.. Screen goes black for a second and then resumes normal operation. This does not happen before taking the screenshot, so it obviously triggers something. The system works and is usable, but the black flashes are pretty odd and distracting. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Feb 8 14:39:47 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Subsystem: Acer Incorporated [ALI] Baffin [Radeon RX 460/560D / Pro 450/455/460/555/555X/560/560X] [1025:1367] Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev c2) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Picasso [1025:1366] InstallationDate: Installed on 2020-05-16 (268 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Nitro AN515-43 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-41-generic root=UUID=675bb42c-4c3c-461b-bce1-53e34e786eaa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/24/2019 dmi.bios.release: 1.8 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.08 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Octavia_PKS dmi.board.vendor: PK dmi.board.version: V1.08 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.08 dmi.ec.firmware.release: 1.5 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.08:bd12/24/2019:br1.8:efr1.5:svnAcer:pnNitroAN515-43:pvrV1.08:rvnPK:rnOctavia_PKS:rvrV1.08:cvnAcer:ct10:cvrV1.08: dmi.product.family: Nitro 5 dmi.product.name: Nitro AN515-43 dmi.product.sku: dmi.product.version: V1.08 dmi.sys.vendor: Acer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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/mutter/+bug/1915014/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915659] Re: MSI computer desktop linux kernel 5.8 bug jammed and freeze all programs
** Package changed: ubuntu-meta (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1915659 Title: MSI computer desktop linux kernel 5.8 bug jammed and freeze all programs Status in linux package in Ubuntu: Incomplete Bug description: MSI computer desktop linux kernel 5.8 bug jammed and freeze all programs i am removed linux kernel 5.8 my MSI computer desktop because when same is trying install again ubuntu 20.04.2 LTS is jammed and nothing happen my MSI desktop computer only MSI desktop linux kernel 5.4 is working only my MSI computer MSI desktop linux kernel 5.8 dont working only jammed and freeze all programs this my intel graphic card information my MSI computer *-display description: VGA compatible controller product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 06 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:32 memory:f780-f7bf memory:e000-efff ioport:f000(size=64) memory:c-d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1915659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906671] Re: [MIR] usrmerge
letting just the dep update of ubuntu-meta through. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1906671 Title: [MIR] usrmerge Status in debootstrap package in Ubuntu: New Status in ubuntu-meta package in Ubuntu: New Status in usrmerge package in Ubuntu: Fix Released Bug description: [Availability] In universe. [Rationale] Since Disco, Ubuntu has defaulted to merged usr systems, specifically that /lib is a symlink to /usr/lib. However, we have not yet completed this transition for systems that were installed pre-disco. This package performs such transition using maintainer scripts. It has been tested and improved thoroughly and has managed to work with all sorts of packages that happened to be installed on the system. For systems that were installed post disco, this package is effectively a no-op. Systems that use nfs mounting with split /usr care must be taken to ensure that initrd mounts nfs-backed /usr. The package aborts configuration if such rare configuration is detected to avoid potentially bracking reboot. For all other systems, we always provide a fallback initrd which has been mounting both / and /usr whenever possible. [Security] The package ships two perl scripts, which are executed by root from maintainer scripts. [Quality assurance] There is debconf question one can preseed to prevent the migration, there is README.Debian explaining what it does and how. It is a one- way / one-time migration, removing the package will not undo the migration. [Dependencies] Perl, and many documented conflicts to ensure that usrmerge compatible packages are on disk prior to migration. [Standards compliance] Adheres to Debian Policy. [Maintenance] Maintained in Debian, merged and supported by Foundations, foundations-bugs is subscribed. [Background information] This will complete usrmerge migration, and will allow to switch buildds to build packages with merged-usr by default. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debootstrap/+bug/1906671/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870822] Re: gnome-shell crashed with assertion failure window.c:1552:meta_window_unmanage: assertion failed: (window->display->focus_window != window)
Hello! Please update the description to include the necessary SRU information [1]. Thank you! [1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template -- 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/1870822 Title: gnome-shell crashed with assertion failure window.c:1552:meta_window_unmanage: assertion failed: (window->display->focus_window != window) Status in Mutter: Unknown Status in mutter package in Ubuntu: Fix Committed Bug description: just what I said in the title, the gnome user interface hung for a minute or so, after pressing 'x' to close a terminal window... been having other issues with the gnome-shell, in this ubuntu beta, this is new. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 4 18:40:19 2020 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2020-04-03 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-6.so.0 () at /lib/x86_64-linux-gnu/libmutter-6.so.0 () at /lib/x86_64-linux-gnu/libmutter-6.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1870822/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1880405] Re: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9
Hello! Please update the description to include the necessary SRU information [1]. Thank you! [1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template -- 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/1880405 Title: Unresponsive GUI and journal flooded with: JS ERROR: TypeError: null has no properties _onFocusChanged@resource:///org/gnome/shell/ui/closeDialog.js:135:9 Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Fix Committed Bug description: O.k. it is an old Lenovo thinkpad T410. However, in 18.04, 19.04 and 19.10 I did face these problems. The sometimes I have to wait 10 seconds to see if a window reacts or not. It is hard to use. Installiert: 3.36.1-5ubuntu2 Installationskandidat: 3.36.2-1ubuntu1~20.04.1 Versionstabelle: 3.36.2-1ubuntu1~20.04.1 500 500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 3.36.1-5ubuntu2 100 100 /var/lib/dpkg/status 3.36.1-5ubuntu1 500 500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-5ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME-Classic:GNOME Date: Sun May 24 15:43:34 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-02-05 (109 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-05-08 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1880405/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841774] Re: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js)
Hello! Please update the description to include the necessary SRU information [1]. Thank you! [1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template -- 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/1841774 Title: gnome-shell freezes and continuously logs "JS ERROR: TypeError: null has no properties" in _addWindowEffect from vfunc_show (both in closeDialog.js) Status in mutter package in Ubuntu: In Progress Bug description: I was closing the dialog of the "software and updates" tools (I was checking the repositories and ppa), but the entire desktop went into freeze, no mouse movement, at the click no action, I pressed the keys "ctrl + alt + f3 "and I went into a tty session, from there I recorded the logs via:" journalctl -f> log ", and I restarted. This is one part of the log, but it seems to repeat itself, I have attached a file with a longer log. -- Logs begin at Tue 2019-02-19 00:29:40 CET. -- ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ago 28 13:41:35 emanuc gnome-shell[2747]: JS ERROR: TypeError: null has no properties _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:74:13 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:145:9 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Aug 28 14:51:01 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-02-18 (190 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190130) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 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/mutter/+bug/1841774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1911921] Re: auto-move-windows extension crashes gnome-shell with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_
Hello! Please update the description to include the necessary SRU information [1]. Thank you! [1] https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template -- 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/1911921 Title: auto-move-windows extension crashes gnome-shell with SIGABRT in src/core/workspace.c:375:meta_workspace_add_window: assertion failed: (g_list_find (workspace->mru_list, window) == NULL) Status in Mutter: Unknown Status in gnome-shell-extensions package in Ubuntu: Fix Committed Status in mutter package in Ubuntu: Fix Committed Bug description: https://gitlab.gnome.org/GNOME/gnome-shell-extensions/-/issues/97 https://gitlab.gnome.org/GNOME/mutter/-/issues/992 --- As in bug 1864052, putting a Chrome video into PiP mode crashes gnome- shell, although this time, in a different location. ProblemType: Crash DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.10.0-12.13-generic 5.10.6 Uname: Linux 5.10.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu55 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Jan 15 16:04:30 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-03-14 (1037 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180313) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.38.2-1ubuntu1 Signal: 6 SourcePackage: gnome-shell StacktraceTop: () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 () at /lib/x86_64-linux-gnu/libmutter-7.so.0 meta_window_stick () at /lib/x86_64-linux-gnu/libmutter-7.so.0 Title: gnome-shell crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip fax input kvm lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1911921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1902290] Re: Sync libraw 0.20.2-1 (main) from Debian unstable (main)
This bug was fixed in the package libraw - 0.20.2-1 Sponsored for Hans Joachim Desserud (hjd) --- libraw (0.20.2-1) unstable; urgency=medium * New upstream release -- Matteo F. Vescovi Mon, 19 Oct 2020 23:00:12 +0200 libraw (0.20.0-4) unstable; urgency=medium * Upload to unstable * debian/libraw20.symbols: drop duplicates and restrict to 64 bits -- Matteo F. Vescovi Tue, 18 Aug 2020 15:45:30 +0200 libraw (0.20.0-3) experimental; urgency=medium * debian/libraw20.symbols: drop MISSING and update others -- Matteo F. Vescovi Tue, 04 Aug 2020 23:43:02 +0200 libraw (0.20.0-2) experimental; urgency=medium * debian/libraw20.symbols: file updated -- Matteo F. Vescovi Tue, 04 Aug 2020 21:11:25 +0200 libraw (0.20.0-1) experimental; urgency=medium [ Matteo F. Vescovi ] * New upstream release This release fixes CVE-2020-15503: | LibRaw before 0.20-RC1 lacks a thumbnail size range check. | This affects decoders/unpack_thumb.cpp, | postprocessing/mem_image.cpp, and utils/thumb_utils.cpp. | For example, | malloc(sizeof(libraw_processed_image_t)+T.tlength) occurs | without validating T.tlength. * debian/: SONAME bump 19 -> 20 * debian/control: - debhelper bump 12 -> 13 - S-V bump 4.4.0 -> 4.5.0 (no changes needed) - RRR set * debian/tests/smoketest: path adapted * debian/copyright: entries for unused files and licenses removed * debian/rules: drop useless files installation * debian/libraw20.symbols: missing and new symbols added [ Sebastien Bacher ] * debian/tests/build: use the correct compiler for autopkgtest cross-testing. (Closes: #954886) -- Matteo F. Vescovi Thu, 30 Jul 2020 00:09:36 +0200 ** Changed in: libraw (Ubuntu) Status: Confirmed => Fix Committed ** Changed in: libraw (Ubuntu) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2020-15503 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libraw in Ubuntu. https://bugs.launchpad.net/bugs/1902290 Title: Sync libraw 0.20.2-1 (main) from Debian unstable (main) Status in libraw package in Ubuntu: Fix Released Bug description: Please sync libraw 0.20.2-1 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: * debian/tests/build: - Use the correct compiler for proposed autopkgtest cross-testing support. * debian/tests/build: - Use the correct compiler for proposed autopkgtest cross-testing support. * debian/tests/build: - Use the correct compiler for proposed autopkgtest cross-testing support. The compiler changes in the autopkgtest for cross-testing has been included in the Debian package. Changelog entries since current hirsute version 0.19.5-1ubuntu1: libraw (0.20.2-1) unstable; urgency=medium * New upstream release -- Matteo F. Vescovi Mon, 19 Oct 2020 23:00:12 +0200 libraw (0.20.0-4) unstable; urgency=medium * Upload to unstable * debian/libraw20.symbols: drop duplicates and restrict to 64 bits -- Matteo F. Vescovi Tue, 18 Aug 2020 15:45:30 +0200 libraw (0.20.0-3) experimental; urgency=medium * debian/libraw20.symbols: drop MISSING and update others -- Matteo F. Vescovi Tue, 04 Aug 2020 23:43:02 +0200 libraw (0.20.0-2) experimental; urgency=medium * debian/libraw20.symbols: file updated -- Matteo F. Vescovi Tue, 04 Aug 2020 21:11:25 +0200 libraw (0.20.0-1) experimental; urgency=medium [ Matteo F. Vescovi ] * New upstream release This release fixes CVE-2020-15503: | LibRaw before 0.20-RC1 lacks a thumbnail size range check. | This affects decoders/unpack_thumb.cpp, | postprocessing/mem_image.cpp, and utils/thumb_utils.cpp. | For example, | malloc(sizeof(libraw_processed_image_t)+T.tlength) occurs | without validating T.tlength. * debian/: SONAME bump 19 -> 20 * debian/control: - debhelper bump 12 -> 13 - S-V bump 4.4.0 -> 4.5.0 (no changes needed) - RRR set * debian/tests/smoketest: path adapted * debian/copyright: entries for unused files and licenses removed * debian/rules: drop useless files installation * debian/libraw20.symbols: missing and new symbols added [ Sebastien Bacher ] * debian/tests/build: use the correct compiler for autopkgtest cross-testing. (Closes: #954886) -- Matteo F. Vescovi Thu, 30 Jul 2020 00:09:36 +0200 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libraw/+bug/1902290/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914918] Re: The snap being updated in the background causes both old and new tabs to die to SIGTRAP
I've seen no problems for last 5 days, while before, I had to restart browser every couple hours. -- 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/1914918 Title: The snap being updated in the background causes both old and new tabs to die to SIGTRAP Status in chromium-browser package in Ubuntu: Confirmed Status in snapd package in Ubuntu: Confirmed Bug description: The last few background updates of chromium have made some old tabs suddenly crash with SIGTRAP and it also makes it impossible to open new tabs, those die instantly with a SIGTRAP as well. This is incredibly destructive to whatever might be the dying tabs' unsaved state and there's no warning about it. Yet again a snap- related change rolled out to users with absolutely amateur-tier testing. Ubuntu: 20.04.2 Snap: 2.48+20.04 Chromium: 88.0.4324.150 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1914918/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914403] Re: Simple Scan UI freezes while scanning from second page on
** Changed in: simple-scan (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1914403 Title: Simple Scan UI freezes while scanning from second page on Status in simple-scan package in Ubuntu: New Bug description: In Kubuntu 20.04 Simple Scan application shows the following behaviour on my system. While scanning the first page, all works fine: the UI is responsive and the live preview of the page being scanned is shown. Starting from the second page on, while the page scanning is in progress the UI is completely frozen and hence no live preview is shown. Trying to click on the application window shows the UI is completely unresponsive. This lasts until around 10 seconds after the page scanning has been completed (and the scanner light has returned to the "home" position). Apart from this, the application works, but this slows down multi-page scanning process and hurts user experience. My scanner is a Canon LiDE 110, a flatbed one. Simple Scan was working perfectly fine in Ubuntu 16.04 and Ubuntu 14.04 on the same system (after upgrading SANE drivers, but for a completely different reason) and was not showing this behaviour. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: simple-scan 3.36.3-0ubuntu0.20.04.0 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Wed Feb 3 13:04:50 2021 InstallationDate: Installed on 2020-10-05 (120 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: Hewlett-Packard HP ProBook 450 G1 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-65-generic root=/dev/mapper/vgkubuntu-root ro quiet splash zswap.enabled=1 zswap.compressor=lz4 vt.handoff=7 SimpleScanLog: [+0,00s] DEBUG: simple-scan.vala:1720: Starting /usr/bin/simple-scan 3.36.3, PID=56452 SourcePackage: simple-scan UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/18/2020 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L74 Ver. 01.50 dmi.board.name: 1942 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 12.F4 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL74Ver.01.50:bd02/18/2020:svnHewlett-Packard:pnHPProBook450G1:pvrA3009DD10303:rvnHewlett-Packard:rn1942:rvrKBCVersion12.F4:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 450 G1 dmi.product.sku: E9Y21EA#ABZ dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1914403/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1899833] Re: [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1899833 Title: [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while Status in alsa-driver package in Ubuntu: Confirmed Bug description: the sound is good for while , then get noisi + lower to nothing, 2 time ago it get solved by turning on secure boot and turning of fast boot ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: matinzare 1615 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Oct 14 23:05:07 2020 InstallationDate: Installed on 2020-08-11 (64 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Speaker, Internal Symptom_PulseAudioLog: اوْکتوْبر 14 19:54:29 matinzare-ZenBook-UX434FLC dbus-daemon[913]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.31' (uid=125 pid=1100 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") اوْکتوْبر 14 19:54:29 matinzare-ZenBook-UX434FLC pulseaudio[1100]: No UCM verb is valid for hw:0 اوْکتوْبر 14 19:54:42 matinzare-ZenBook-UX434FLC systemd[1090]: pulseaudio.service: Succeeded. اوْکتوْبر 14 19:54:52 matinzare-ZenBook-UX434FLC systemd[1090]: pulseaudio.socket: Succeeded. Symptom_Type: Sound works for a while, then breaks Title: [ZenBook UX434FLC_UX434FL, Realtek ALC294, Speaker, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/18/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434FLC.303 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434FLC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX434FLC.303:bd12/18/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX434FLC_UX434FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX434FLC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX434FLC_UX434FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-08-11T18:28:56.120214 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1899833/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915481] Re: gnome crashes after running `apt upgrade`
I believe the crash happened at roughly Feb 11 19:42:41. -- 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/1915481 Title: gnome crashes after running `apt upgrade` Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is the second time this week this has happened, and perhaps the tenth time in the past few months. This time the packages it was updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1) When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2) When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't. Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK. I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 20:27:58 2021 InstallationDate: Installed on 2016-12-27 (1507 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915712] [NEW] migrating to chromium snap broken 18.04->20.04
Public bug reported: happened on do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcmOt9h4RchURAQMIJh546JrlplhJmSMRUFS/7wABAQEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/QA4Sx5TDgAKICAgICAg/wBMNzgwQzA1NDQwNDQK/ABBTDE5MTYKICAgICAgAGE= modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Feb 15 13:26:20 2021 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-27 (1328 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) InstalledPlugins: Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Hewlett-Packard HP Pro3500 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic root=UUID=093e88ea-7b5e-4e39-b56c-03b28ad06dd2 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to focal on 2021-02-15 (0 days ago) dmi.bios.date: 10/25/2013 dmi.bios.vendor: AMI dmi.bios.version: 8.17 dmi.board.name: 2ABF dmi.board.vendor: Foxconn dmi.board.version: 3.20 dmi.chassis.asset.tag: CZC34935PY dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAMI:bvr8.17:bd10/25/2013:svnHewlett-Packard:pnHPPro3500Series:pvr:rvnFoxconn:rn2ABF:rvr3.20:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Pro3500 Series dmi.sys.vendor: Hewlett-Packard modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (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 chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1915712 Title: migrating to chromium snap broken 18.04->20.04 Status in chromium-browser package in Ubuntu: New Bug description: happened on do-release-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-135.139-generic 4.15.18 Uname: Linux 4.15.0-135-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAEcmOt9h4RchURAQMIJh546JrlplhJmSMRUFS/7wABAQEBAQEBAQEBAQEBAQEBMCoAmFEAKkAwcBMAeC0RAAAe/QA4Sx5TDgAKICAgICAg/wBMNzgwQzA1NDQwNDQK/ABBTDE5MTYKICAgICAgAGE= modes: 1280x1024 1280x1024 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Feb 15 13:26:20 2021 Desktop-Session: 'None' 'None' '/usr/local/share:/usr/share:/var/lib/snapd/desktop' Env: 'None' 'None' ErrorMessage: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück InstallationDate: Installed on 2017-06-27 (1328 days ago) InstallationMedia: Kubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215) InstalledPlugins: Load-Avg-1min: 0.61 Load-Processes-Running-Percent: 0.2% MachineType: Hewlett-Packard HP Pro3500 Series ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-135-generic root=UUID=093e88ea-7b5e-4e39-b56c-03b28ad06dd2 ro quiet splash vt.handoff=1 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 SourcePackage: chromium-browser Title: package chromium-browser 87.0.4280.66-0ubuntu0.18.04.1 failed to install/upgrade: »neues chromium-browser-Skript des Paketes pre-installation«-Unterprozess gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to
[Desktop-packages] [Bug 1915481] Re: gnome crashes after running `apt upgrade`
Out from running journalctl -b-1 > prevjournal.txt ** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+attachment/5463784/+files/prevjournal.txt -- 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/1915481 Title: gnome crashes after running `apt upgrade` Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is the second time this week this has happened, and perhaps the tenth time in the past few months. This time the packages it was updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1) When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2) When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't. Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK. I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 20:27:58 2021 InstallationDate: Installed on 2016-12-27 (1507 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915481] Re: gnome crashes after running `apt upgrade`
Reproducing the crash exactly is basically impossible -- I have no idea what I was doing to trigger it on January 6. The crashes I've been experiencing happen seemingly at random while running `apt update`. It may well happen again in the future, but based on past experiences it will be with a different set of packages than the last time. Also gnome-shell was updated on January 20, and the crashes have continued to happen since then. But the last time I rebooted was after a crash, so I just ran `journalctl -b-1 > prevjournal.txt` and I've attached the results. -- 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/1915481 Title: gnome crashes after running `apt upgrade` Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is the second time this week this has happened, and perhaps the tenth time in the past few months. This time the packages it was updating were: libsqlite3-dev:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-gtk-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), libsqlite3-0:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), sqlite3:amd64 (3.33.0-1, 3.33.0-1ubuntu0.1), libgnome-autoar-0-0:amd64 (0.2.4-2, 0.2.4-2ubuntu0.1), wpasupplicant:amd64 (2:2.9-1ubuntu8, 2:2.9-1ubuntu8.1) When it happened on Tuesday, the packages that were upgraded were: friendly-recovery:amd64 (0.2.41, 0.2.41ubuntu0.20.10.1), snapd:amd64 (2.48+20.10, 2.48.3+20.10), snap-confine:amd64 (2.48+20.10, 2.48.3+20.10), openjdk-11-jre-headless:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), openjdk-11-jre:amd64 (11.0.9.1+1-0ubuntu1~20.10, 11.0.10+9-0ubuntu1~20.10), ubuntu-core-launcher:amd64 (2.48+20.10, 2.48.3+20.10), plexmediaserver:amd64 (1.21.3.4014-58bd20c02, 1.21.3.4021-5a0a3e4b2) When it happens the screen goes blank, and in about 10-15 seconds I'm back at a gnome login prompt. Sometimes it kills my tmux session, but this time it didn't. Also about 24 hours after it happens I will suddenly start experiencing network issues. I'll need to restart NetworkManager and then it will be OK. I created a gist with the contents of /var/log/syslog when it happened at https://gist.github.com/waltman/8a6166e270d99b98e86b641ccc0a9006 ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.14 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu Feb 11 20:27:58 2021 InstallationDate: Installed on 2016-12-27 (1507 days ago) InstallationMedia: Ubuntu-Server 16.10 "Yakkety Yak" - Release amd64 (20161012.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-10-25 (109 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915481/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914062] Re: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC
@stgraber Thank you for assisting with aligning udevs's behaviour with LXD. I've added the tests-in-lxd autopkgtests to ensure catching issues in LXD earlier. I'd be happy to add more tests in systemd's autopkgtest to not let udevd regress in LXD. @xnox I don't like to idea of letting services be failed in default installs in LXD because this would result bad user experience. @seb128 could you please patch network-manager 1.28 to behave in LXC like it did in 1.26 to let it migrate and not fail in LXC with systemd 247 until the udevd behaviour is fixed in LXC? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1914062 Title: NetworkManager-wait-online.service in 1.28.0-2ubuntu1 fails to start in LXC Status in lxd package in Ubuntu: Won't Fix Status in network-manager package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: This regresses systemd's autopkgtest because it expects the system in the container to reach running state, but the system ends up in degraded state due to the service failing. https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-hirsute/hirsute/amd64/s/systemd/20210112_185712_ff570@/log.gz ... == FAIL: test_no_failed (__main__.ServicesTest) No failed units -- Traceback (most recent call last): File "/tmp/autopkgtest.fFC3Lw/build.xLc/real-tree/debian/tests/boot-and-services", line 68, in test_no_failed self.assertEqual(failed, []) AssertionError: Lists differ: ['● NetworkManager-wait-online.service loa[42 chars]ine'] != [] First list contains 1 additional elements. First extra element 0: '● NetworkManager-wait-online.service loaded failed failed Network Manager Wait Online' + [] - ['● NetworkManager-wait-online.service loaded failed failed Network Manager ' - 'Wait Online'] -- Ran 23 tests in 4.435s ... Reproducible locally by installing n-m from -proposed, then restarting the system in the LXC container. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1914062/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
This is the verification work I did from a package management perspective, to verify correctness and consistency in a variety of scenarii: 1) In a fully up-to-date focal VM with enigmail, jsunit and tinyjsd installed, I enabled focal-proposed and updated: - from a terminal with `apt dist-upgrade`, debconf ncurses dialogs were displayed to notify of the removal of tinyjsd and jsunit from the archive - from the GUI (update-manager), debconf GTK dialogs were displayed 2) In a fully up-to-date groovy VM with enigmail installed, I enable groovy-proposed: - if jsunit and tinyjsd had been manually installed from focal-proposed (i.e. they are empty packages), they are not removed - if jsunit and tinyjsd had been manually installed from focal (release), they are removed with the upgrade 3) In a focal chroot without focal-updates, with enigmail, jsunit and tinyjsd installed, I hand-edited /etc/apt/sources.list to upgrade to groovy with groovy-updates and groovy-proposed and verified that jsunit and tinyjsd were being removed as expected. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in jsunit source package in Bionic: New Status in thunderbird source package in Bionic: Triaged Status in jsunit source package in Focal: Fix Committed Status in thunderbird source package in Focal: Fix Committed Status in tinyjsd source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Committed Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915704] [NEW] Specific pointing device disappear/disconnect when standby
Public bug reported: Ubuntu 20.10 groovy (x86-64) Cinnamon 4.6.7 Kernel 5.8.0-43-generic I installed Ubuntu while using a Microsft mise. This one works great with no problem. The buttons are old and used out, so I changed it with a Trust with RGB. The Trust mouse seems disconnected when going to standby (need keyboard, since mouse seems disconnected to show password prompt). The only way to get the mouse back to work, is to disconnect and reconnect it. What's narrow in this, is that I've tried again with the old pointing device (from Microsoft), and this one still is recognised in standby, and I'm able to click to open the password prompt. I've read this repport: https://bugs.launchpad.net/ubuntu/+bug/1573454 But it seems not totaly the same, since I've the problem with a pointer and not the other one. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.32.03 Sun Dec 27 19:00:34 UTC 2020 GCC version: gcc version 10.2.0 (Ubuntu 10.2.0-13ubuntu1) ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Mon Feb 15 12:07:10 2021 DistUpgraded: Fresh install DistroCodename: groovy DistroVariant: ubuntu DkmsStatus: nvidia, 460.32.03, 5.8.0-43-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK107 [GeForce GTX 650] [10de:0fc6] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GK107 [GeForce GTX 650] [19da:1288] MachineType: ASUS System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=1768f602-2494-474b-970a-2f71d61fca4b ro quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/21/2020 dmi.bios.release: 14.3 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1403 dmi.board.asset.tag: Default string dmi.board.name: PRIME B460-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1403:bd07/21/2020:br14.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB460-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.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-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1915704 Title: Specific pointing device disappear/disconnect when standby Status in xorg package in Ubuntu: New Bug description: Ubuntu 20.10 groovy (x86-64) Cinnamon 4.6.7 Kernel 5.8.0-43-generic I installed Ubuntu while using a Microsft mise. This one works great with no problem. The buttons are old and used out, so I changed it with a Trust with RGB. The Trust mouse seems disconnected when going to standby (need keyboard, since mouse seems disconnected to show password prompt). The only way to get the mouse back to work, is to disconnect and reconnect it. What's narrow in this, is that I've tried again with the old pointing device (from Microsoft), and this one still is recognised in standby, and I'm able to click to open the password prompt. I've read this repport:
[Desktop-packages] [Bug 1897224] Re: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display)
this was also addressed in snapd in https://github.com/snapcore/snapd/pull/9530 in 2.48 ** Changed in: snapd Status: In Progress => Won't Fix ** Changed in: snapd Status: Won't Fix => Fix Committed ** Changed in: snapd 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/1897224 Title: Graphical snaps can't run in Gnome 3.38 Wayland sessions (can't open X display) Status in Mutter: Unknown Status in snapd: Fix Released Status in mutter package in Ubuntu: Fix Released Status in snapd package in Ubuntu: Won't Fix Status in mutter source package in Groovy: Fix Released Status in snapd source package in Groovy: Won't Fix Status in mutter source package in Hirsute: Fix Released Status in snapd source package in Hirsute: Won't Fix Bug description: [Impact] * Users who select the Wayland session on Ubuntu 20.10 cannot run snap confined X11 applications, due to gnome-shell no longer listening on an abstract socket for connections. * The fix, which has been accepted into upstream's gnome-3-38 branch reverts the change removing the abstract socket, and fixes the bug that prompted it's removal: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1508 [Test Case] * Start with a stock Ubuntu 20.10 desktop install. * At the GDM login screen, after selecting your user account use the gear icon to select the "Ubuntu on Wayland" session, and log in. * Ensure Chromium is installed by running "sudo snap install chromium". * Try to run "chromium" from the terminal. Without the fix, it will fail with the error "Unable to open X display". With the fix applied, it will launch as normal. [Regression Potential] * The patch modifies the logic gnome-shell uses to launch Xwayland. So there is a potential that the change could break X11 application support on the Wayland session. * The default configuration for gnome-shell is to launch Xwayland on session start, so it should be immediately obvious if there are problems. * In addition to checking snapped X11 apps like Chromium, verify that a few classic X11 apps still launch correctly (e.g. xterm, xeyes, etc). [Other Info] * Running "ss -xlp | grep Xwayland" should show that it is listening on both "/tmp/.X11-unix/X0" (the regular unix domain socket) and "@/tmp/.X11-unix/X0" (the abstract socket). --- I'm trying to run chromium installed via snap in Ubuntu 20.10 when running Ubuntu Wayland session. Unfortunately, chromium wouldn't start: > chromium [49244:49244:0925/094607.732169:ERROR:browser_main_loop.cc(1417)] Unable to open X display. I am able to run Firefox just fine (assuming that Firefox still runs on xwayland) and also Intellij snap works fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8 Uname: Linux 5.8.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu47 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Sep 25 09:45:16 2020 InstallationDate: Installed on 2016-09-05 (1480 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Snap: chromium 85.0.4183.121 (latest/stable) SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1897224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working on systems with fingerprint support
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915570 Title: Login screen password entry not working on systems with fingerprint support Status in gnome-shell package in Ubuntu: Confirmed Bug description: This bug is for the login package. This only affects users of the development release and does not affect stable users. The bug in the password entry causes either the password to be entered only for the login to hang, or when attempting to enter the password, the computer quickly deletes any characters entered as if backspace was being held therefore preventing a user from being able to log in. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-02-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Tags: hirsute Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
Still present on nvidia-driver-460 (460.39-0ubuntu0.20.04.1). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs Status in nvidia-graphics-drivers-340 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Bug description: To replicate: 1. Start a video playing, for example in vlc. 'avcodec decoder: Using NVIDIA VDPAU Driver Shared Library 418.56 Fri Mar 15 12:31:51 CDT 2019 for hardware decoding' 2. Optionally pause it. 3. Switch to another user. The original user's ~/.xsession-errors will rapidly fill up with errors along the lines of "vdpau_chroma filter error". At the same time, errors are put in /var/log/syslog as well: [7f9d604810a0] vdpau_chroma filter error: video mixer features failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer attributes failure: An invalid handle value was provided. [7f9d604810a0] vdpau_chroma filter error: video mixer rendering failure: An invalid handle value was provided. (repeat ad nauseum) At least one of the two will rapidly fill up its partition and problems will arise. With AMD video hardware and driver, the video continues playing - you can hear the sound despite being in the other user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1846374/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1906243] Re: Audio comes out through system speakers when headset autoconnects
I am facing with similar problem. I have Thinkpad T14 with COWIN bluetooth headphones. When I turn ON the headphones,it automatically connects. However the sound still comes out of internal speaker. When I go to output devices the headphone is not in the list. I have to disconnect and reconnect again to get the audio to the headphones. I tried the suggested solution from #1866194 i.e. deleting ~/.config/pulse and restarting. Also I have pulseaudio v13.99.1. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1906243 Title: Audio comes out through system speakers when headset autoconnects Status in pulseaudio package in Ubuntu: New Bug description: When I turn on my Bluetooth headset, Ubuntu 20.04 connects to it automatically (Or at least it appears to be connected to it). It says connected and the switch is in the ON position in Bluetooth settings, however the audio still comes out of the speakers, the icon next to the volume bar in the top-right menu shows the speaker icon instead of the headphone icon. I have to disconnect the headset and re-connect it from Bluetooth settings for the audio to go to the headset. It doesn't work only when it connects automatically. Always works when I connect it manually. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.13 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sujit 1394 F pulseaudio /dev/snd/controlC0: sujit 1394 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-28 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: pulseaudio 1:13.99.1-1ubuntu3.8 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65 Tags: focal Uname: Linux 5.4.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.name: 0JKRPT dmi.board.vendor: Dell Inc. dmi.board.version: A07 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA07:bd07/13/2015:svnDellInc.:pnVostro3446:pvrNotSpecified:rvnDellInc.:rn0JKRPT:rvrA07:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Vostro 3446 dmi.product.sku: 0662 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1906243/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working
I still can't reproduce this on my hirsute desktop, fully updated. Please check if the problem is unique to: * Some special characters in your password; or * Other authentication methods being available, like fingerprint. ** No longer affects: gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915570 Title: Login screen password entry not working on systems with fingerprint support Status in gdm3 package in Ubuntu: Confirmed Bug description: This bug is for the login package. This only affects users of the development release and does not affect stable users. The bug in the password entry causes either the password to be entered only for the login to hang, or when attempting to enter the password, the computer quickly deletes any characters entered as if backspace was being held therefore preventing a user from being able to log in. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-02-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Tags: hirsute Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working
I’m getting a lot of pam failures due to fingerprints in my logs: févr. 12 08:21:51 casanier gdm-password][6277]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:51 casanier gdm-fingerprint][6278]: gkr-pam: no password is available for user févr. 12 08:21:51 casanier gdm-password][6283]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:51 casanier gdm-fingerprint][6284]: gkr-pam: no password is available for user févr. 12 08:21:52 casanier gdm-password][6289]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:52 casanier gdm-fingerprint][6290]: gkr-pam: no password is available for user févr. 12 08:21:52 casanier gdm-password][6360]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:52 casanier gdm-fingerprint][6361]: gkr-pam: no password is available for user févr. 12 08:21:52 casanier gdm-password][6366]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:52 casanier gdm-fingerprint][6367]: gkr-pam: no password is available for user févr. 12 08:21:52 casanier gdm-password][6372]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:52 casanier gdm-fingerprint][6373]: gkr-pam: no password is available for user févr. 12 08:21:52 casanier gdm-password][6378]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:52 casanier gdm-fingerprint][6379]: gkr-pam: no password is available for user févr. 12 08:21:53 casanier gdm-password][6384]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:53 casanier gdm-fingerprint][6385]: gkr-pam: no password is available for user févr. 12 08:21:53 casanier gdm-password][6390]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:53 casanier gdm-fingerprint][6391]: gkr-pam: no password is available for user févr. 12 08:21:53 casanier gdm-password][6396]: pam_unix(gdm-password:auth): Couldn't open /etc/securetty: Aucun fichier ou dossier de ce type févr. 12 08:21:53 casanier gdm-fingerprint][6397]: gkr-pam: no password is available for user Before getting into that state, I got very few in my logs, and after reverting my system globally, I don’t have those when logging in. I think this is the cause of the password prompt emptying. -- 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/1915570 Title: Login screen password entry not working on systems with fingerprint support Status in gdm3 package in Ubuntu: Confirmed Bug description: This bug is for the login package. This only affects users of the development release and does not affect stable users. The bug in the password entry causes either the password to be entered only for the login to hang, or when attempting to enter the password, the computer quickly deletes any characters entered as if backspace was being held therefore preventing a user from being able to log in. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-02-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Tags: hirsute Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I've checked the 5.11.0-rc7 and the touchpad still doesn't work
properly, on the left and right bottom side the same primary action is
being taken instead of secondary on the right and primary on the left!
--
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:
Fix Committed
Status in linux package in Fedora:
Confirmed
Status in linux package in openSUSE:
New
Bug description:
Update (based on #296)
=
The latest kernel tree
(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git)
has the complete solution to fix this bug. So we can expect kernel
v5.11 to fix this issue without any additional work.
Before the release of v5.11, you are suggested to use #189 to save your
touchpad. Note that for distributions like Ubuntu and Fedora, the pinctrl-amd
driver is built into the initramfs. So you have to rebuild the initramfs after
replacing the old module with new one.
On Fedora, run `sudo dracut --force`; On ubuntu, run `sudo update-initramfs
-u`.
The complete solution is three patches,
- 47a0001436352c9853d72bf2071e85b316d688a2 ("pinctrl: amd: remove debounce
filter setting in IRQ type setting")
- 06abe8291bc31839950f7d0362d9979edc88a666 ("pinctrl: amd: fix incorrect way
to disable debounce filter")
- 8dcb7a15a585b6d0fee15751ce11d7a68cfedd56 ("gpiolib: acpi: Take into
account debounce settings")
The first two patches has reached the stable tree. If the last one is
also backported to LTS kernel, you won't need to install kernel 5.11.
But I don't know when this will happen.
Original bug report
===
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:
[Desktop-packages] [Bug 1915570] Re: Login screen password entry not working
Is the password box misinterpreting some special character that's causing this? ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gdm3 (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1915570 Title: Login screen password entry not working Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: This bug is for the login package. This only affects users of the development release and does not affect stable users. The bug in the password entry causes either the password to be entered only for the login to hang, or when attempting to enter the password, the computer quickly deletes any characters entered as if backspace was being held therefore preventing a user from being able to log in. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu57 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-02-12 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210212) NonfreeKernelModules: nvidia_modeset nvidia Package: gdm3 3.38.1-2ubuntu1.1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 Tags: hirsute Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True mtime.conffile..etc.gdm3.custom.conf: 2021-02-12T13:25:57.150125 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1915570/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914230] Re: On-screen keyboard for Japanese doesn't display Japanese characters, only English
@vanvugt i'll fix that myself ^_^ -- 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/1914230 Title: On-screen keyboard for Japanese doesn't display Japanese characters, only English Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Triaged Bug description: This is about touch keyboard. Screen keyboard doesn't display other languages characters, only english characters. I noticed many users concern about that on forums To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1914230/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895643] Re: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS
** Changed in: jsunit (Ubuntu Focal) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: tinyjsd (Ubuntu Focal) Assignee: (unassigned) => Olivier Tilloy (osomon) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1895643 Title: Backport Thunderbird 78 to 20.04 LTS and 18.04 LTS Status in thunderbird package in Ubuntu: Fix Released Status in jsunit source package in Bionic: New Status in thunderbird source package in Bionic: Triaged Status in jsunit source package in Focal: Fix Committed Status in thunderbird source package in Focal: Fix Committed Status in tinyjsd source package in Focal: Fix Committed Status in thunderbird source package in Groovy: Fix Committed Bug description: Upstream Thunderbird version 78.2.2 should be a candidate for backporting to stable Ubuntu releases. I've successfully built 78.2.1 against both with forcing nodejs version (20.04, 18.04) and disabling AV1 support due to too old nasm (18.04). Attaching debdiffs here. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1895643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1905623] Re: df: /run/user/1000/doc: Operation not permitted
Daniel, thank you for submitting the patch upstream! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal in Ubuntu. https://bugs.launchpad.net/bugs/1905623 Title: df: /run/user/1000/doc: Operation not permitted Status in coreutils package in Ubuntu: Fix Released Status in xdg-desktop-portal package in Ubuntu: Triaged Bug description: /run/user/1000/doc is a fuse.portal mount point, but statfs() return EPERM, hence df produces an error message. Maybe statfs() is not implemented, but it would be good to quieten this down (df even does not allow me to ignore it, probably because it looks at statfs to find out fs type, so my fs type ignoring doesn't work). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1905623/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
