[Desktop-packages] [Bug 1996267] [NEW] Insecure passwort storage in Chromium (Snap)
Public bug reported: In the Snap package of Chromium, Chromium is not protecting passwords with gnome-keyring (or KWallet). As a result, copying the Chromium profile directory from the snap directory gives access to all stored passwords. This is a HIGH security risk. Regular users who are used to storing their passwords in browsers are probably unaware of this. Note that Chromium is started with the command line option “--password- store=basic”. This hack should never have been released to the public. The Chromium documentation states: > --password-store=basic (to use the plain text store) https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1996267 Title: Insecure passwort storage in Chromium (Snap) Status in chromium-browser package in Ubuntu: New Bug description: In the Snap package of Chromium, Chromium is not protecting passwords with gnome-keyring (or KWallet). As a result, copying the Chromium profile directory from the snap directory gives access to all stored passwords. This is a HIGH security risk. Regular users who are used to storing their passwords in browsers are probably unaware of this. Note that Chromium is started with the command line option “--password-store=basic”. This hack should never have been released to the public. The Chromium documentation states: > --password-store=basic (to use the plain text store) https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993064] Re: Please update to 102.3.x so that tbSync can work again!
Thunderbird 102.4.2 is distributed: https://packages.ubuntu.com/search?keywords=thunderbird On Ubuntu 22.04, my update worked fine, tbSync works again. Thank you very much to the developers. -- 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/1993064 Title: Please update to 102.3.x so that tbSync can work again! Status in thunderbird package in Ubuntu: In Progress Bug description: Currently it is impossible to use Thunderbird effectively with Office365 servers, due to a bug in TB 102.2.2, as noted here, which affects calendar syncing. https://github.com/jobisoft/TbSync/issues/617 Please could we get the 102.3.x version released for Ubuntu 18.04 and later? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1993064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967632] Re: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication
I was able to load the module libaetpkss from version 3.7.0 (instead of the latest 3.8.0) to Snap Firefox just copying the shared library to my home dir (where Firefox has access). It has to be the version 3.7.0 that needs the legacy package libssl1.1 -- 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/1967632 Title: [snap] apparmor denied when trying to load pkcs11 module for smart card authentication Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: I use a smart card to access government sites. I have that working in firefox and chrome on ubuntu impish, and gave jammy a try, but there firefox won't load the library, giving me a generic error. dmesg, however, shows this apparmor denied message: [sáb abr 2 17:32:27 2022] audit: type=1400 audit(1648931547.646:115): apparmor="DENIED" operation="file_mmap" profile="snap.firefox.firefox" name="/run/user/1000/doc/e0bac853/libaetpkss.so.3.5.4112" pid=3680 comm="firefox" requested_mask="m" denied_mask="m" fsuid=1000 ouid=0 Note also the path, that's not what I typed into the firefox dialog box. I have the .so copied to /usr/lib/x86_64-linux-gnu/libaetpkss.so.3.5.4112, and that's what I typed in when prompted for its path by firefox. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Apr 2 17:34:09 2022 InstallationDate: Installed on 2022-03-20 (13 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220319) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1967632/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956637] Re: I have disabled the touchpad through settings, but that has no effect
The 'Settings' application is not ubuntu-settings but gnome-control- center. Ubuntu 21.10 (impish) reached end-of-life on July 14, 2022. Do you still see the problem which you reported while using a currently supported release of Ubuntu? If so, please tell us which one otherwise this bug report can be left to expire in due course. ** Package changed: ubuntu-settings (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1956637 Title: I have disabled the touchpad through settings, but that has no effect Status in Ubuntu: Incomplete Bug description: I'm running Ubuntu 21.10 on a laptop Ubuntu-settings is V 21.10.4 Disabling the touchpad on my new laptop has no effect. The only way to disable the touchpad was to install Touchpad-indicator ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: ubuntu-settings 21.10.4 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 7 12:05:10 2022 InstallationDate: Installed on 2021-12-31 (6 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1956637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956090] [NEW] Not possible to choose which admin should enter password
You have been subscribed to a public bug: Environment Ubuntu 20.04 fully upgraded. Pretty low likelihood but if a system has more than one admin, when a user (admin or not) needs to perform an action that require administration permission a pop up cames on and require a password for a specific admin user, usually the first historically created, and it's not possible to choose another admin, a couple of examples. 1 - I would like to create a new admin and get rid of the old one, see attachment I downloaded a pre-cooked ubuntu version to test it - as osboxes.org I created user Luca (admin) - logout and login as Luca - open settings and get rid of osboxes.org Expected: the window should ask password for my user, since I'm admin, or should let me choose which admin should enter the password to confirm Actual: the window ask me for osboxes.org password, no chance to change user 2 - Use case see in office - A computer has 1 normal account and 2 admins account This person have not admin priviledges so that to make some actions is require to enter admin password. Two admins are me (Luca) and an other one (Ale) Sometimes happens that if system ask for a specific user, and user is not in the office is not possible to proceed this way. Of course no issue in acting via command line for every action, but it's a bad UX and somtimes could happen in a worst situation. ** Affects: policykit-1 (Ubuntu) Importance: Undecided Status: New ** Tags: administrator gnome password settings ux -- Not possible to choose which admin should enter password https://bugs.launchpad.net/bugs/1956090 You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 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 1956090] Re: Not possible to choose which admin should enter password
** Package changed: ubuntu => policykit-1 (Ubuntu) ** Tags added: focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1956090 Title: Not possible to choose which admin should enter password Status in policykit-1 package in Ubuntu: New Bug description: Environment Ubuntu 20.04 fully upgraded. Pretty low likelihood but if a system has more than one admin, when a user (admin or not) needs to perform an action that require administration permission a pop up cames on and require a password for a specific admin user, usually the first historically created, and it's not possible to choose another admin, a couple of examples. 1 - I would like to create a new admin and get rid of the old one, see attachment I downloaded a pre-cooked ubuntu version to test it - as osboxes.org I created user Luca (admin) - logout and login as Luca - open settings and get rid of osboxes.org Expected: the window should ask password for my user, since I'm admin, or should let me choose which admin should enter the password to confirm Actual: the window ask me for osboxes.org password, no chance to change user 2 - Use case see in office - A computer has 1 normal account and 2 admins account This person have not admin priviledges so that to make some actions is require to enter admin password. Two admins are me (Luca) and an other one (Ale) Sometimes happens that if system ask for a specific user, and user is not in the office is not possible to proceed this way. Of course no issue in acting via command line for every action, but it's a bad UX and somtimes could happen in a worst situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1956090/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1570129] Re: Xorg crashed with SIGABRT
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Changed in: xorg-server (Ubuntu) Status: Confirmed => Incomplete -- 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/1570129 Title: Xorg crashed with SIGABRT Status in xorg-server package in Ubuntu: Incomplete Bug description: After the last update and after of reboot system the error appeared. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 364.15 Sat Apr 2 21:30:33 PDT 2016 GCC version: gcc version 5.3.1 20160407 (Ubuntu 5.3.1-13ubuntu6) ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Wed Apr 13 19:42:54 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed bbswitch, 0.8, 4.4.0-18-generic, x86_64: installed nvidia-364, 364.15, 4.4.0-18-generic, x86_64: installed vboxhost, 5.0.16, 4.4.0-17-generic, x86_64: installed vboxhost, 5.0.16, 4.4.0-18-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0616] Subsystem: Dell GK208M [GeForce GT 740M] [1028:0616] InstallationDate: Installed on 2016-03-19 (25 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: Dell Inc. Vostro 5470 ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=c1651082-fabc-4b0c-b328-6c708e33f208 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F7NWH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/21/2015:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn0F7NWH:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1570129/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1568904] Re: Xorg crashed with SIGABRT
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1568904 Title: Xorg crashed with SIGABRT Status in xorg-server package in Ubuntu: Incomplete Bug description: After of exit of game, "Snow" of Steam, the error appeared. I had to end the session because the system crashed. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6 Uname: Linux 4.4.0-18-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 364.15 Sat Apr 2 21:30:33 PDT 2016 GCC version: gcc version 5.3.1 20160407 (Ubuntu 5.3.1-13ubuntu6) ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 Date: Mon Apr 11 11:51:06 2016 Disassembly: => 0x7f8ff3e40518: Não é possível acessar a memória no endereço 0x7f8ff3e40518 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed bbswitch, 0.8, 4.4.0-18-generic, x86_64: installed nvidia-364, 364.15, 4.4.0-18-generic, x86_64: installed vboxhost, 5.0.16, 4.4.0-17-generic, x86_64: installed vboxhost, 5.0.16, 4.4.0-18-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0616] Subsystem: Dell GK208M [GeForce GT 740M] [1028:0616] InstallationDate: Installed on 2016-03-19 (23 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: Dell Inc. Vostro 5470 ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-18-generic.efi.signed root=UUID=c1651082-fabc-4b0c-b328-6c708e33f208 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server Stacktrace: #0 0x7f8ff3e40518 in ?? () No symbol table info available. Backtrace stopped: Não é possível acessar a memória no endereço 0x7ffd30b6b768 StacktraceTop: ?? () ThreadStacktrace: . Thread 1 (LWP 1360): #0 0x7f8ff3e40518 in ?? () No symbol table info available. Backtrace stopped: Não é possível acessar a memória no endereço 0x7ffd30b6b768 Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F7NWH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/21/2015:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn0F7NWH:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1568904/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1567700] Re: Xorg crashed with SIGABRT
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1567700 Title: Xorg crashed with SIGABRT Status in xorg-server package in Ubuntu: Incomplete Bug description: After the update of xorg package and after system rebooting, the error is appearing after logged system. ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: xserver-xorg-core 2:1.18.3-1ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6 Uname: Linux 4.4.0-17-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 364.15 Sat Apr 2 21:30:33 PDT 2016 GCC version: gcc version 5.3.1 20160405 (Ubuntu 5.3.1-13ubuntu4) ApportVersion: 2.20.1-0ubuntu1 Architecture: amd64 Date: Thu Apr 7 20:15:23 2016 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.4.0-16-generic, x86_64: installed bbswitch, 0.8, 4.4.0-17-generic, x86_64: installed nvidia-364, 364.15, 4.4.0-17-generic, x86_64: installed vboxhost, 5.0.16, 4.4.0-16-generic, x86_64: installed vboxhost, 5.0.16, 4.4.0-17-generic, x86_64: installed ExecutablePath: /usr/lib/xorg/Xorg GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0616] Subsystem: Dell GK208M [GeForce GT 740M] [1028:0616] InstallationDate: Installed on 2016-03-19 (19 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307) MachineType: Dell Inc. Vostro 5470 ProcCmdline: /usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch ProcEnviron: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-17-generic.efi.signed root=UUID=c1651082-fabc-4b0c-b328-6c708e33f208 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so ?? () Title: Xorg crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 01/21/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A11 dmi.board.name: 0F7NWH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA11:bd01/21/2015:svnDellInc.:pnVostro5470:pvr:rvnDellInc.:rn0F7NWH:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.name: Vostro 5470 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160331-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1567700/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800555] Re: Computer slow. Error reports appear.
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1800555 Title: Computer slow. Error reports appear. Status in xorg-server package in Ubuntu: Incomplete Bug description: Computer slow. Error reports appear. Says system is running on low graphics sometimes. Makes me log in most of the time. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155 Uname: Linux 4.4.0-138-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 BootLog: [[0;32m OK [0m] Stopped WPA supplicant. [[0;32m OK [0m] Started Show Plymouth Boot Screen. Starting Hold until boot process finishes up... CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Oct 29 17:37:27 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1] InstallationDate: Installed on 2016-09-11 (778 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Hewlett-Packard p6710f ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 6.07 dmi.board.name: 2AB1 dmi.board.vendor: FOXCONN dmi.board.version: 1.00 dmi.chassis.asset.tag: 4CE0480TV4 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr: dmi.product.name: p6710f dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Oct 29 17:32:25 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8 inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9 inputLogitech USB Optical Mouse MOUSE, id 10 xserver.errors: /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1800555/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1631643] Re: 1920x1080 HDMI output is corrupted in 16.04
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1631643 Title: 1920x1080 HDMI output is corrupted in 16.04 Status in xorg-server package in Ubuntu: Incomplete Bug description: Ever since upgrading to 16.04 from 14.04 on my Lenovo x230 the HDMI output to a Benq W1070 is corrupted if run at 1920x1080 (native resolution). At 1280x720 the display looks fine. Looking at similar reports for other graphics cards it seems similar to cases when the frequency is too low. I've tested that the projector still works fine with the same cable and another computer. I've attached a photo of the kind of corruption that shows up on screen. It's mostly green/magenta pixels sprinkled across the screen. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sat Oct 8 19:38:39 2016 DistUpgraded: 2016-08-07 01:11:54,340 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu DkmsStatus: virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed virtualbox, 5.0.24, 4.4.0-38-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fa] InstallationDate: Installed on 2014-05-03 (889 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: LENOVO 23252QG ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-38-generic root=UUID=9018e190-86bb-4fbf-a348-d47ea769640f ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to xenial on 2016-08-07 (62 days ago) dmi.bios.date: 05/24/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET31WW (1.11 ) dmi.board.asset.tag: Not Available dmi.board.name: 23252QG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET31WW(1.11):bd05/24/2012:svnLENOVO:pn23252QG:pvrThinkPadX230:rvnLENOVO:rn23252QG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 23252QG dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Wed Oct 5 10:26:16 2016 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 728 vendor LGD xserver.version: 2:1.18.3-1ubuntu2.3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1631643/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790519] Re: package xserver-common 2:1.18.4-0ubuntu0.8 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** Changed in: xorg-server (Ubuntu) Status: New => Incomplete -- 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/1790519 Title: package xserver-common 2:1.18.4-0ubuntu0.8 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato Status in xorg-server package in Ubuntu: Incomplete Bug description: pc blocked and needs hard power off or reboot more than two times. Every time I power on pc I see messages with "There is a problem..." ProblemType: Package DistroRelease: Ubuntu 16.04 Package: xserver-common 2:1.18.4-0ubuntu0.8 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 3 20:08:50 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ErrorMessage: problemi con le dipendenze - lasciato non configurato ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology RV610 [Radeon HD 2400 PRO] [174b:e370] MachineType: CdcPointSpa MS-7255 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic root=UUID=0ce495b0-d61b-494b-bde1-68981ac3b3ca ro quiet splash vt.handoff=7 RelatedPackageVersions: dpkg 1.18.4ubuntu1.4 apt 1.2.27 SourcePackage: xorg-server Title: package xserver-common 2:1.18.4-0ubuntu0.8 failed to install/upgrade: problemi con le dipendenze - lasciato non configurato UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/15/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V5.6C dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: MS-7255 dmi.board.vendor: Micro-Star dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV5.6C:bd11/15/2007:svnCdcPointSpa:pnMS-7255:pvr2.0:rvnMicro-Star:rnMS-7255:rvr2.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: MS-7255 dmi.product.version: 2.0 dmi.sys.vendor: CdcPointSpa version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Mon Sep 3 20:07:34 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputSleep Button KEYBOARD, id 8 inputMicrosoft Microsoft Wheel Mouse Optical® MOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1790519/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996286] [NEW] screencast recording should also record audio
Public bug reported: The gnome-shell built-in screencast recorder doesn't currently (43.0-1ubuntu2/lunar) record audio. According to this comment: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5524#note_1465711 enabling audio recording only requires changing a parameter via dbus. If the change is not invasive I believe it should be done by default in Ubuntu. Note that Kazam is not functional on Wayland, which means that >= Jammy currently lacks a well integrated audio+video screencast recording tool. ** Affects: gnome-shell Importance: Unknown Status: Unknown ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #5524 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5524 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5524 Importance: Unknown Status: Unknown ** Description changed: The gnome-shell built-in screencast recorder doesn't currently (43.0-1ubuntu2/lunar) record audio. According to this comment: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5524#note_1481502 enabling audio recording only requires changing a parameter via dbus. If the change is not invasive I believe it should be done by default in Ubuntu. Note that Kazam is not functional on Wayland, which means that >= Jammy - lacks a well integrated audio+video screencast recording tool. + currently lacks a well integrated audio+video screencast recording tool. ** Description changed: The gnome-shell built-in screencast recorder doesn't currently (43.0-1ubuntu2/lunar) record audio. According to this comment: - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5524#note_1481502 + https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5524#note_1465711 enabling audio recording only requires changing a parameter via dbus. If the change is not invasive I believe it should be done by default in Ubuntu. Note that Kazam is not functional on Wayland, which means that >= Jammy currently lacks a well integrated audio+video screencast recording tool. -- 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/1996286 Title: screencast recording should also record audio Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: New Bug description: The gnome-shell built-in screencast recorder doesn't currently (43.0-1ubuntu2/lunar) record audio. According to this comment: https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/5524#note_1465711 enabling audio recording only requires changing a parameter via dbus. If the change is not invasive I believe it should be done by default in Ubuntu. Note that Kazam is not functional on Wayland, which means that >= Jammy currently lacks a well integrated audio+video screencast recording tool. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1996286/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1059928] Re: Lightdm [Kubuntu) not displaying user thumbnail photos
** Changed in: accountsservice (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: lightdm (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1059928 Title: Lightdm [Kubuntu) not displaying user thumbnail photos Status in accountsservice package in Ubuntu: Won't Fix Status in lightdm package in Ubuntu: Won't Fix Bug description: On the Kubuntu login screen (I'm assuming lightdm?), there are just generic pictures for users. I expected it to display my photo along with my user name, as I configured in System Settings -> Account Details -> Change your image. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lightdm 1.3.3-0ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-16.25-generic 3.5.4 Uname: Linux 3.5.0-16-generic x86_64 ApportVersion: 2.6.1-0ubuntu1 Architecture: amd64 Date: Mon Oct 1 21:53:35 2012 EcryptfsInUse: Yes InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20120928) ProcEnviron: LANGUAGE= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1059928/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1377497] Re: Unable to unlock guest seesion in Kubuntu 14.04
** Changed in: lightdm (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1377497 Title: Unable to unlock guest seesion in Kubuntu 14.04 Status in lightdm package in Ubuntu: Won't Fix Bug description: OS: Kubuntu 14.04 Desktop: KDE Applidation: KDE Screen Lock (sorry, don't know the exact package name) Symptom: After being left alone, Kubutnu will lock the guest user's session. It is then not possible to resume (blank passwords or obvious possibles like "password", "guest" are no accepted) and the computer needs to be rebooted to gain access (losing any files and data that the guest might have in-use). Expected behaviour: Either the screen does not lock, or the guest account is informed of the password to use during log-in I have read bug 1059625 but that appears to applyt to Gnome (or possibly Unity) whereas this affects Kubuntu/KDE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1377497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 380312] Re: SVG thumbnails are pixelated
Upstream issue was closed 2018-01-02 as "RESOLVED OBSOLETE" Launchpad bug did not expire due to bug watch Initial report was against a release that was 'end-of-life' in 2010 No reply to comment #5 after almost four years so closing. ** Changed in: nautilus (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/380312 Title: SVG thumbnails are pixelated Status in Nautilus: Expired Status in nautilus package in Ubuntu: Invalid Bug description: Binary package hint: nautilus I don't remember this as a problem in Intrepid, but thumbnails for SVG files in Jaunty are pixelated, like they were created at low resolution and then blown up. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/380312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996267] Re: Insecure passwort storage in Chromium (Snap)
Hello Erlenmayr, thanks for your report. > In the Snap package of Chromium, Chromium is not protecting passwords > with gnome-keyring (or KWallet). You can connect the corresponding interface for that: snap connect chromium:password-manager-service > As a result, copying the Chromium profile directory from the snap > directory gives access to all stored passwords. Please note those passwords are not stored in the clear, though they can be discovered by going into Chromium's Settings > Passwords. ** Tags added: snap ** Summary changed: - Insecure passwort storage in Chromium (Snap) + [snap] Insecure password storage -- 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/1996267 Title: [snap] Insecure password storage Status in chromium-browser package in Ubuntu: New Bug description: In the Snap package of Chromium, Chromium is not protecting passwords with gnome-keyring (or KWallet). As a result, copying the Chromium profile directory from the snap directory gives access to all stored passwords. This is a HIGH security risk. Regular users who are used to storing their passwords in browsers are probably unaware of this. Note that Chromium is started with the command line option “--password-store=basic”. This hack should never have been released to the public. The Chromium documentation states: > --password-store=basic (to use the plain text store) https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 400966] Re: gnome terminal should highlight user entered text for easy parsing
gnome-terminal task has been 'Incomplete' since 2009 so closing. ** Changed in: gnome-terminal (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) ** Changed in: gnome-terminal (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/400966 Title: gnome terminal should highlight user entered text for easy parsing Status in gnome-terminal package in Ubuntu: Invalid Status in vte package in Ubuntu: Expired Bug description: Binary package hint: gnome-terminal It's often hard to find an entered command in the text of a terminal. A simple solution to this would be to annotate the text entered by a user (or pasted perhaps) with a colour, or underline, or similar. njh@flobber:~$ lsb_release -rd Description: Ubuntu 8.10 Release: 8.10 njh@flobber:~$ apt-cache policy gnome-terminal gnome-terminal: Installed: 2.24.1.1-0ubuntu1 Candidate: 2.24.1.1-0ubuntu1 Version table: *** 2.24.1.1-0ubuntu1 0 500 http://us.archive.ubuntu.com intrepid-updates/main Packages 100 /var/lib/dpkg/status 2.24.1-0ubuntu1 0 500 http://us.archive.ubuntu.com intrepid/main Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/400966/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 660272] Re: Two instances of mutter at start-up
Bug report did not expire due to bug watch. Upstream issue was closed "RESOLVED FIXED" on 2010-11-10 so no doubt included in Ubuntu shortly after that date. ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/660272 Title: Two instances of mutter at start-up Status in gnome-session package in Ubuntu: Fix Released Bug description: Binary package hint: mutter I installed gnome-shell and gnome3-session in Maverick. When I enter the GNOME 3 session, I have two mutter processes. gnome-shell doesn't start untill i kill on of the two mutter instances. ProblemType: Bug DistroRelease: Ubuntu 10.10 mutter 2.31.5-0ubuntu9 gnome3-session 2.32.0-0ubuntu1 gnome-shell 2.31.5-2ubuntu2 I also installed gnome-shell 2.91 from git, no changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/660272/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 538964] Re: Window manager not started after login
Bug report did not expire due to assignment. No activity for over 12 years and bug report refers to GNOME 2. Closing as 'Invalid' as no recent reports, no indication of bug being fixed and an EOL GNOME version being referred to. ** Changed in: gnome-session (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/538964 Title: Window manager not started after login Status in gnome-session package in Ubuntu: Invalid Bug description: Binary package hint: gnome-session When I log in to ubuntu, my window manager compiz is not started, and I have to use the Appearance dialog to manually start it. However, when I switch to guest session, the window manager is started by default. I cannot report by apport, which generates an Internet connection error. If further information is needed, I would like to help providing it. Using 2.28.0-0ubuntu5 under Ubuntu 9.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/538964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 344428] Re: Screen freezes after gdm login
Bug report did not expire due to assignment. Last comment was 13 years ago and will have referred to GNOME 2 which is now EOL so closing as 'Invalid'. ** Changed in: gnome-session (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/344428 Title: Screen freezes after gdm login Status in gnome-session package in Ubuntu: Invalid Bug description: I just upgraded from intrepid to jaunty, and after logging in to GDM, I get a blank screen with a non-spinning cursor. It never finishes logging in. This is on a version 2 MacBook. I upgraded to the most recent jaunty packages (as of 3-17-2009), and that did not make a difference. Here is my xsession-errors output: /etc/gdm/Xsession: Beginning session setup... Setting IM through im-switch for locale=en_US. Start IM through /etc/X11/xinit/xinput.d/all_ALL linked to /etc/X11/xinit/xinput.d/default. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. I: caps.c: Dropping root privileges. I: caps.c: Limited capabilities successfully to CAP_SYS_NICE. GNOME_KEYRING_SOCKET=/tmp/keyring-GOc19F/socket SSH_AUTH_SOCK=/tmp/keyring-GOc19F/socket.ssh Checking for Xgl: not present. xset q doesn't reveal the location of the log file. Using fallback /var/log/Xorg.0.log Detected PCI ID for VGA: Checking for texture_from_pixmap: not present. Trying again with indirect rendering: Checking for texture_from_pixmap: present. Checking for non power of two support: present. Checking for Composite extension: present. Checking screen 1Comparing resolution (1280x800) to maximum 3D texture size (2048): Passed. Checking for Software Rasterizer: Not present. Checking for nVidia: not present. Checking for FBConfig: present. Checking for Xgl: not present. x-session-manager[3916]: WARNING: Application 'gnome-panel.desktop' failed to register before timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/344428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
** Description changed:
To test the snap with VA-API changes,
1. Install the Chromium snap,
- sudo snap install --channel beta/hwacc chromium
+ sudo snap install --channel stable/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-media-
samples.
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) and note what the page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
- Currently it seems to work for all reporters on Xorg, but not for all
- reporters on Wayland.
+ Currently it seems to work for all reporters on Xorg.
- Just to situate ourselves, beta/hwacc is [1] and I plan to merge it in
- the main snap via [2]. Comments before #176 refer to [3] and _should_ be
- roughly equivalent to [1], but I wouldn't be surprised if it turned out
- not to be.
+ The version in stable/hwacc is fixed.
- [1]:
https://launchpad.net/~nteodosio/+snap/chromium-browser-dev/+build/1875127
- [2]:
https://code.launchpad.net/~nteodosio/chromium-browser/+git/chromium-browser/+merge/428038
- [3]:
https://launchpad.net/~nteodosio/+snap/chromium-browser-hwacc/+build/1838168
+ Versions in other channels (edge/hwacc, beta/hwacc, candidate/hwacc)
+ follow the Chromium release cycle (dev, beta and stable channels as in
+ https://omahaproxy.appspot.com/all.json?os=linux).
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel stable/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples.
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) and note what the page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
Currently it seems to work for all reporters on Xorg.
The version in stable/hwacc is fixed.
Versions in other channels (edge/hwacc, beta/hwacc, candidate/hwacc)
follow the Chromium release cycle (dev, beta and stable channels as in
https://omahaproxy.appspot.com/all.json?os=linux).
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile
[Desktop-packages] [Bug 341344] Re: session crashing randomly - may be power management issue
Report did not expire due to assignment. GNOME 2 is so very EOL seven years after the last comment. Further to comment #9 will close as 'Invalid' although it seems the problem may never have been fixed in that GNOME version. ** Changed in: gnome-session (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/341344 Title: session crashing randomly - may be power management issue Status in gnome-session package in Ubuntu: Invalid Bug description: Binary package hint: gnome-session Likely gnome-session session crashes - closing X session and logging out - randomly (somewhat). Sometimes happens in lid close. Sometimes happen in resume (from suspend) Sometimes happens when screensaver activates Sometimes just happens (I don't see anything - all of a sudden everything closes and I'm sent back to login) suspect power management problem. Might also be gnome-screensaver. Note: Intel 965 video chipset on Dell hardware, not well supported - opengl fails a lot of the time - may also be related. This is a severe bug. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: gnome-session 2.25.92-0ubuntu2 ProcEnviron: PATH=(custom, user) LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session Uname: Linux 2.6.28-9-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/341344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 267909] Re: Error messages when starting X Sessions may not fully adhere to language requests
Bug report did not expire due to assignment. Comment #6 seems to imply that the issue was fixed many years ago in any case the reporter will have been using GNOME 2 which has been EOL for some time now. ** Changed in: gnome-session (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) ** Changed in: gnome-session (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/267909 Title: Error messages when starting X Sessions may not fully adhere to language requests Status in gnome-session package in Ubuntu: Fix Released Bug description: Binary package hint: gdm On Ubuntu 8.04.1, if one language is the system default, the user chooses a different language at the GDM login prompt, and the X Session encounters a problem, the error message that appears will show the error message in the language selected, but the "OK"/"Accept" button will still be in the system default language, rather than both the message and button being in the user's chosen language. For an example of what this looks like, see the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/267909/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 81817] Re: window screenshot crashes (using openbox)
Issue did not expire due to the bug watch. Upstream report was closed 2012-01-26 "RESOLVED OBSOLETE" as the issue had not been reproducible for some time. With no reports here for over 12 years I'm closing this as being fixed, probably many many years ago, see comment #4. ** Changed in: gnome-screenshot (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/81817 Title: window screenshot crashes (using openbox) Status in gnome-utils: Expired Status in gnome-screenshot package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-utils In Feisty x86 gnome-screenshot crashes if I want to take a screenshot of a window, with gnome-screenshot -w Full-screen gnome-screenshot works perfectly. This only happens in openbox (not in metacity). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-utils/+bug/81817/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
The latest Nvidia BETA driver (https://www.nvidia.com/Download/driverResults.aspx/194278/en-us/): Linux X64 (AMD64/EM64T) Display Driver Version:525.53 BETA Release Date: 2022.11.10 Operating System: Linux 64-bit Language: English (US) File Size: 394.19 MB includes: Fixed a regression in 515.76 that caused blank screens and hangs when starting an X server on RTX 30 series GPUs in some configurations where the boot display is connected via HDMI. and this did indeed fix this issue for me. Alternatively, keep an eye on https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa and when updated with version 525 do sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt update and then install the Ubuntu packaged driver for your series. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: New Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Status in xserver-xorg-video-intel source package in Jammy: New Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInter
[Desktop-packages] [Bug 1392053] Re: gnome-screenshot sometimes hangs leaving a transparent white square over the screen
Bug report did not expire due to bug watch Debian issue was closed 2016-03-26 as no longer reproducible. Comment #9 implies no longer an issue in Ubuntu in 2017. With no comments confirming the problem for over five years I'm closing this as being fixed. If anyone still sees an issue then please open a new bug report by issuing the following command in a terminal ubuntu-bug gnome-screenshot so that your installation settings can be captured, thank you. ** Changed in: gnome-screenshot (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/1392053 Title: gnome-screenshot sometimes hangs leaving a transparent white square over the screen Status in gnome-screenshot package in Ubuntu: Fix Released Bug description: Sometimes after taking some screenshots gnome-screenshots hangs and leaves a transparent white filled zone over my screen. The PrintScreen key does not work anymore in that situation. If I kill the gnome-screenshot process the white zone disappears and the PrintScreen key becomes functional again. I am using Ubuntu 14.10 with Unity. It comes with gnome-screenshot 3.10.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1392053/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1996267] Re: [snap] Insecure password storage
** Changed in: chromium-browser (Ubuntu) Status: New => Confirmed ** Summary changed: - [snap] Insecure password storage + [snap] Doesn't encrypt stored password unless password-manager-service is connected ** Summary changed: - [snap] Doesn't encrypt stored password unless password-manager-service is connected + [snap] Doesn't encrypt stored passwords unless interface is connected ** Summary changed: - [snap] Doesn't encrypt stored passwords unless interface is connected + [snap] Doesn't store encrypted passwords unless interface is connected -- 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/1996267 Title: [snap] Doesn't store encrypted passwords unless interface is connected Status in chromium-browser package in Ubuntu: Confirmed Bug description: In the Snap package of Chromium, Chromium is not protecting passwords with gnome-keyring (or KWallet). As a result, copying the Chromium profile directory from the snap directory gives access to all stored passwords. This is a HIGH security risk. Regular users who are used to storing their passwords in browsers are probably unaware of this. Note that Chromium is started with the command line option “--password-store=basic”. This hack should never have been released to the public. The Chromium documentation states: > --password-store=basic (to use the plain text store) https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1996267/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1692149] Re: Firefox thinks w3.css is a domain
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Firefox since that time. I'm unsure of what was expected when this bug report was raised as the screenshot is no loner available. In both Firefox and Chrome I see a Google list of suggested web sites when "w3.css" is input into the search box and that is what I would expect. When enabling the Firefox "Search" box I see the same Google suggestion list. Has this issue been fixed or am I misunderstanding the problem that you reported? ** 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/1692149 Title: Firefox thinks w3.css is a domain Status in firefox package in Ubuntu: Incomplete Bug description: When I type in w3.css in the url bar it gives this: https://s9.postimg.org/4f15c6ndb/Screenshot_from_2017-05-19_21-28-10.png Even though I should not be doing searches in the url bar I'm accustomed to chrome's omnibox ProblemType: Bug DistroRelease: Ubuntu 17.04 Package: firefox 53.0.2+build1-0ubuntu0.17.04.2 ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11 Uname: Linux 4.10.0-21-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: alexios2049 F...m pulseaudio /dev/snd/controlC0: alexios2049 F pulseaudio BuildID: 20170509205512 Channel: Unavailable CurrentDesktop: Unity:Unity7 Date: Fri May 19 21:25:03 2017 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2017-05-19 (0 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp9s0 proto static metric 600 169.254.0.0/16 dev wlp9s0 scope link metric 1000 192.168.1.0/24 dev wlp9s0 proto kernel scope link src 192.168.1.252 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=53.0.2/20170509205512 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to zesty on 2017-05-20 (0 days ago) dmi.bios.date: 10/05/2012 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V2.07 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: MA40_HX dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV2.07:bd10/05/2012:svnAcer:pnAspireM5-481PT:pvrV2.07:rvnAcer:rnMA40_HX:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire M5-481PT dmi.product.version: V2.07 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1692149/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1762336] Re: when viewing ads in youtube, the screen lock is turned on
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Do you still see a problem related to the one that you reported when using a currently supported version of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. ** 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/1762336 Title: when viewing ads in youtube, the screen lock is turned on Status in firefox package in Ubuntu: Incomplete Bug description: 1. Expect that video playback will be continuous throughout the entire video. 2. It turned out that when advertising in the video is enabled lock screen. This prevents you from watching the video. 3. I open the browser, I start video on youtube after long viewing advertising video hosting is started and with it the screen lock is started. --- 1. Ожидаю что режим просмотра видео будет непрерывен на протяжении всего видео. 2. Оказалось что при появлении рекламы в видео включается блокировка экрана. Это мешает просмотру видео. 3. Открываю браузер, запускаю видео на youtube после длительного просмотра запускается реклама видеохостинга и с ней запускается блокировка экрана. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: firefox 59.0.2+build1-0ubuntu0.16.04.3 ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-38-generic x86_64 NonfreeKernelModules: wl AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: alexandr 1788 F...m pulseaudio /dev/snd/controlC0: alexandr 1788 F pulseaudio BuildID: 20180404120016 Channel: Unavailable CurrentDesktop: Unity Date: Mon Apr 9 13:24:47 2018 ExecutablePath: /usr/lib/firefox/firefox Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-02-01 (66 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) IpRoute: default via 192.168.0.1 dev wlp4s0 proto static metric 600 169.254.0.0/16 dev wlp4s0 scope link metric 1000 192.168.0.0/24 dev wlp4s0 proto kernel scope link src 192.168.0.14 metric 600 Locales: extensions.sqlite corrupt or missing Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcEnviron: LANGUAGE=ru PATH=(custom, user) XDG_RUNTIME_DIR= LANG=ru_RU.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=59.0.2/20180404120016 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/27/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.17 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.17 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.17 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.17:bd02/27/2013:svnAcer:pnAspireV5-571G:pvrV2.17:rvnAcer:rnAspireV5-571G:rvrV2.17:cvnAcer:ct9:cvrV2.17: dmi.product.family: Aspire V5-571G dmi.product.name: Aspire V5-571G dmi.product.version: V2.17 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1762336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1705981] Re: Chromium doesn't follow flash deprecation guidelines
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu and Chromium since that time. This bug report is over five years old and the contents of the URL in the description have undoubtedly changed as today I see a message (when using Google Chrome) which includes the text: We have retired Flash. Support for Flash ended on December 31, 2020. Chromium, now a snap, give me an "Access denied" error. I'm closing this bug report as it is no longer valid. ** Changed in: chromium-browser (Ubuntu) Status: New => Invalid -- 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/1705981 Title: Chromium doesn't follow flash deprecation guidelines Status in chromium-browser package in Ubuntu: Invalid Bug description: Chrome has set the global policy for flash to "ask first" for a while. Yet, chromium will always play flash content without user consent if the adobe-flashplugin package is installed on the system. Test: Visit http://get.adobe.com/flashplayer/about/ on chrome and chromium. Per default policy, chrome will ask for user consent. Chromium will not. Expected Behaviour: Chromium should also ask the user first. Version: Chromium 59.0.3071.109 Built on Ubuntu , running on Ubuntu 16.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1705981/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1987631] Re: Screencast only records one second
Following up on my earlier comment (#9), is it worth trying to apply patch https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2928 to gstreamer1.0 and gst-plugins-base1.0? I was able to confirm the patch picks cleanly and gstreamer still compiles when applied to the current jammy refs: https://git.launchpad.net/ubuntu/+source/gstreamer1.0/log/?h=ubuntu%2Fjammy and https://git.launchpad.net/ubuntu/+source/gst-plugins- base1.0/log/?h=ubuntu%2Fjammy . Original patch file: https://gitlab.freedesktop.org/gstreamer/gstreamer/-/merge_requests/2928.patch Patch file broken into... gstreamer1.0: https://gist.github.com/mdmower/a758ec83b525ce8b1a59774782ec8abd gst-plugins-base1.0: https://gist.github.com/mdmower/de7245603f12c3ef413c0beba1f02628 I haven't created Ubuntu packages before and I'm wary of trying to overwrite gstreamer on my computer; sorry, I haven't gone beyond verifying it compiles. -- 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/1987631 Title: Screencast only records one second Status in GNOME Shell: Fix Released Status in OEM Priority Project: In Progress Status in gnome-shell package in Ubuntu: Fix Released Status in pipewire package in Ubuntu: Fix Released Status in gnome-shell source package in Jammy: Fix Released Status in pipewire source package in Jammy: New Bug description: When recording a screencast with gnome on kinetic the resulting video will play for one second and then freeze. It looks like the same bug was discussed upstream at https://gitlab.gnome.org/GNOME/gnome- shell/-/issues/5585 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1987631/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1832913] Re: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
*** This bug is a duplicate of bug 1800196 *** https://bugs.launchpad.net/bugs/1800196 I am getting this error in my log, Ubuntu 18.04: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1832913 Title: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 Status in gnome-session package in Ubuntu: Confirmed Bug description: I am getting this error in my log, Ubuntu 18.04: Cannot access vdagent virtio channel /dev/virtio- ports/com.redhat.spice.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1832913/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
For these description items:
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
Do you mean?
- Distro version (`grep VERSION= /etc/os-release`);
- GPU (`lsgpu`);
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel stable/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples.
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) and note what the page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
Currently it seems to work for all reporters on Xorg.
The version in stable/hwacc is fixed.
Versions in other channels (edge/hwacc, beta/hwacc, candidate/hwacc)
follow the Chromium release cycle (dev, beta and stable channels as in
https://omahaproxy.appspot.com/all.json?os=linux).
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1816497] Re: [snap] vaapi chromium no video hardware decoding
Hardware decode on stable/hwacc worked out of the box for me, thanks!
- VDAVideoDecoder
- Xorg
- VERSION="21 (Vanessa)"
- Intel Kabylake (Gen9)
- Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
--
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/1816497
Title:
[snap] vaapi chromium no video hardware decoding
Status in chromium-browser package in Ubuntu:
In Progress
Bug description:
To test the snap with VA-API changes,
1. Install the Chromium snap,
sudo snap install --channel stable/hwacc chromium
2. Start Chromium,
snap run chromium
3. Open a video, e.g. one from https://github.com/chthomos/video-
media-samples.
4. Enter about:media-internals in the address bar, click the
corresponding box (if the video is playing, it will have the "(kPlay)"
identifier) and note what the page says for kVideoDecoderName.
Please report
- The value for kVideoDecoderName from step 4. Success is typically
{Vaapi,VDA,Mojo}VideoDecoder while failure is {FFMpeg,Vpx,Dav1d}VideoDecoder;
- Xorg or Wayland (`echo $WAYLAND_DISPLAY`);
- Distro version (`grep VERSION= /etc/os_release`);
- GPU (`lscpu`);
- CPU generation (`lscpu`).
Currently it seems to work for all reporters on Xorg.
The version in stable/hwacc is fixed.
Versions in other channels (edge/hwacc, beta/hwacc, candidate/hwacc)
follow the Chromium release cycle (dev, beta and stable channels as in
https://omahaproxy.appspot.com/all.json?os=linux).
--Original Bug report -
Libva is no longer working for snap installed chromium 72.0.3626.109
(Official Build) snap (64-bit)
I followed this instruction
sudo snap install --channel=candidate/vaapi chromium
My amdgpu can use libva
`vainfo: Driver version: Mesa Gallium driver 18.3.3 for AMD STONEY (DRM
3.27.0, 4.20.0-10.1-liquorix-amd64, LLVM 7.0.1)
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple: VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main: VAEntrypointVLD
VAProfileVC1Advanced: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileHEVCMain : VAEntrypointVLD
VAProfileHEVCMain10 : VAEntrypointVLD
VAProfileJPEGBaseline : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc`
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1816497/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985137] Re: Millions of syslog messages about: Creating shared memory in /dev/shm/.org.chromium.Chromium failed: Too many open files (24)
[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.] ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Expired -- 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/1985137 Title: Millions of syslog messages about: Creating shared memory in /dev/shm/.org.chromium.Chromium failed: Too many open files (24) Status in chromium-browser package in Ubuntu: Expired Bug description: My /var/log/syslog file is 35 GB in size. 96234480/192463600 (50%) lines contain something like that: Aug 8 15:45:34 compiz[8153]: [8153:0100/00.390316:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.wRKl7F failed: Too many open files (24) Aug 8 15:45:34 compiz[8153]: [8153:0100/00.390320:ERROR:command_buffer_proxy_impl.cc(93)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed Aug 8 15:45:34 compiz[8153]: [8153:0100/00.390338:ERROR:platform_shared_memory_region_posix.cc(250)] Creating shared memory in /dev/shm/.org.chromium.Chromium.SRkCeH failed: Too many open files (24) Aug 8 15:45:34 compiz[8153]: [8153:0100/00.390342:ERROR:command_buffer_proxy_impl.cc(93)] ContextResult::kFatalFailure: AllocateAndMapSharedMemory failed ProblemType: Bug DistroRelease: Ubuntu 22.04 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu82.2ppa8 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Unity:Unity7:ubuntu Date: Thu Aug 11 18:09:15 2022 InstallationDate: Installed on 2022-03-20 (144 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) RebootRequiredPkgs: Error: path contained symlinks. Snap: chromium 104.0.5112.79 (latest/stable) Snap.Changes: keine Änderungen gefunden SnapSource: ubuntu/+source/chromium-browser UpgradeStatus: Upgraded to jammy on 2022-04-14 (119 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1985137/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779432] Re: [upstream] Libre Writer doesn't do duplex printing
Thank you very much for your help with this post. Keep up the good job and continue to provide such excellent results. I appreciate you sharing this data. It has a lot of value. https://atdoorstep.ae/dubai/handyman";>handyman services near me -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1779432 Title: [upstream] Libre Writer doesn't do duplex printing Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: The Libre Writer print settings are set to two side printing, but program only prints single side. Is not HP Linux driver because both FireFox and Chrome print both sides. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-core 1:6.0.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: ufsd ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: MATE Date: Fri Jun 29 22:17:38 2018 ExecutablePath: /usr/lib/libreoffice/program/soffice.bin InstallationDate: Installed on 2018-06-15 (14 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1779432/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
