[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
** Tags added: rls-ii-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918497] Re: connect to one shared folder error package
[Expired for nautilus (Ubuntu) because there has been no activity for 60 days.] ** Changed in: nautilus (Ubuntu) Status: Incomplete => Expired -- 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/1918497 Title: connect to one shared folder error package Status in nautilus package in Ubuntu: Expired Bug description: when I had upgraded package I can't connect to my folder in my NAS. (All machine have the last ubuntu.) In another computer with old package I can see all file in a shared folder but when I have compiled 'apt upgrade' if I try to open the folder the computer return me a error ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: nautilus 1:3.38.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Mar 10 23:08:05 2021 ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'222' b'org.gnome.nautilus.window-state' b'initial-size' b'(1011, 597)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2021-03-06 (3 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=it_IT.UTF-8 SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince3.38.0-1 file-roller 3.38.0-1 nautilus-extension-gnome-terminal 3.38.0-1ubuntu1.1 nautilus-share0.7.3-2ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1918497/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908930] Re: libwebkit2gtk-4.0-37 missing files break epiphany
[Expired for webkit2gtk (Ubuntu) because there has been no activity for 60 days.] ** Changed in: webkit2gtk (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to webkit2gtk in Ubuntu. https://bugs.launchpad.net/bugs/1908930 Title: libwebkit2gtk-4.0-37 missing files break epiphany Status in webkit2gtk package in Ubuntu: Expired Bug description: libwebkit2gtk-4.0-37 version 2.30.3-0ubuntu0.18.04.1 comes without WebKitPluginProcess (should be under /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0). Similarly /usr/lib/x86_64-linux- gnu/webkit2gtk-4.0/WebKitStorageProcess is missing. If I try to follow a link to a pdf file in epiphany (epiphany-browser 3.28.1-1ubuntu1) it crashes. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webkit2gtk/+bug/1908930/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1928038] [NEW] Multiple memory leaks in libgdiplus
Public bug reported: Multiple memory leaks have been identified in libgdiplus library when the test code provided ibgdiplus/tests/testgdi.c is compiled with ASAN enabled. Memory leaks have been found in multiple components of the library as below : 0x7fce7e31a3d0 in GdipCreatePen1 /home/targets/libgdiplus/src/pen.c:258 0x7fce7e36d4da in GdipCreateSolidFill /home/targets/libgdiplus/src/solidbrush.c:138 Following is the output of the testgdi.c when it is compiled with ASAN. jpg drawn tif drawn gif drawn png drawn bmp drawn XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" after 127 requests (127 known processed) with 0 events remaining. = ==61628==ERROR: LeakSanitizer: detected memory leaks Direct leak of 504 byte(s) in 3 object(s) allocated from: #0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7fce7e31a3d0 in gdip_pen_new /home/targets/libgdiplus/src/pen.c:66 #2 0x7fce7e31a3d0 in GdipCreatePen1 /home/targets/libgdiplus/src/pen.c:258 Direct leak of 256 byte(s) in 1 object(s) allocated from: #0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7fce7bb720b9 (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x1d0b9) Direct leak of 168 byte(s) in 3 object(s) allocated from: #0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7fce7e36d4da in gdip_solidfill_new /home/targets/libgdiplus/src/solidbrush.c:55 #2 0x7fce7e36d4da in GdipCreateSolidFill /home/targets/libgdiplus/src/solidbrush.c:138 Direct leak of 16 byte(s) in 1 object(s) allocated from: #0 0x7fce7e6a2961 in realloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98961) #1 0x7fce7dbf325c (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x5025c) Indirect leak of 168 byte(s) in 3 object(s) allocated from: #0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7fce7e36d4da in gdip_solidfill_new /home/targets/libgdiplus/src/solidbrush.c:55 #2 0x7fce7e36d4da in GdipCreateSolidFill /home/targets/libgdiplus/src/solidbrush.c:138 Indirect leak of 160 byte(s) in 2 object(s) allocated from: #0 0x7fce7e6a279a in __interceptor_calloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x9879a) #1 0x7fce7dbf322e (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x5022e) Indirect leak of 32 byte(s) in 1 object(s) allocated from: #0 0x7fce7e6a279a in __interceptor_calloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x9879a) #1 0x7fce7bb727c8 (/usr/lib/x86_64-linux-gnu/libfontconfig.so.1+0x1d7c8) Indirect leak of 16 byte(s) in 2 object(s) allocated from: #0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7fce7dbf3cb5 (/usr/lib/x86_64-linux-gnu/libX11.so.6+0x50cb5) SUMMARY: AddressSanitizer: 1320 byte(s) leaked in 16 allocation(s) Information requested: # lsb_release -rd Description:Ubuntu 16.04.6 LTS Release:16.04 #apt-cache policy libgdiplus libgdiplus: Installed: 4.2-1ubuntu1 Candidate: 4.2-1ubuntu1 Version table: *** 4.2-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status Expected : No memory leaks while running the test code What happened : Couple of memory leaks in libgdiplus component as indicated in the output. ** Affects: libgdiplus (Ubuntu) Importance: Undecided Status: New ** Attachment added: "This is the ASAN compiled version of testgdi.c" https://bugs.launchpad.net/bugs/1928038/+attachment/5496252/+files/compiled_testgdi -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgdiplus in Ubuntu. https://bugs.launchpad.net/bugs/1928038 Title: Multiple memory leaks in libgdiplus Status in libgdiplus package in Ubuntu: New Bug description: Multiple memory leaks have been identified in libgdiplus library when the test code provided ibgdiplus/tests/testgdi.c is compiled with ASAN enabled. Memory leaks have been found in multiple components of the library as below : 0x7fce7e31a3d0 in GdipCreatePen1 /home/targets/libgdiplus/src/pen.c:258 0x7fce7e36d4da in GdipCreateSolidFill /home/targets/libgdiplus/src/solidbrush.c:138 Following is the output of the testgdi.c when it is compiled with ASAN. jpg drawn tif drawn gif drawn png drawn bmp drawn XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" after 127 requests (127 known processed) with 0 events remaining. = ==61628==ERROR: LeakSanitizer: detected memory leaks Direct leak of 504 byte(s) in 3 object(s) allocated from: #0 0x7fce7e6a2602 in malloc (/usr/lib/x86_64-linux-gnu/libasan.so.2+0x98602) #1 0x7fce7e31a3d0 in gdip_pen_new /home/targets/libgdiplus/src/pen.c:66 #2 0x7fce7e31a3d0
[Desktop-packages] [Bug 1927948] Re: Windows switch monitor after resuming from sleep
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1419 https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 Importance: Unknown Status: Unknown ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2092 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2092 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2092 Importance: Unknown Status: Unknown ** Tags added: multimonitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1927948 Title: Windows switch monitor after resuming from sleep Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in mutter package in Ubuntu: New Bug description: What I expect: Window layout/positioning is identical after resume from sleep. What I observe: After resume from sleep, windows appear on a different monitor than before. I found this possibly relevant GNOME bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 10 13:40:28 2021 InstallationDate: Installed on 2019-12-02 (524 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1927948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926050] Re: [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so)
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: apport-cli YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-ati (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-ati in Ubuntu. https://bugs.launchpad.net/bugs/1926050 Title: [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so) Status in mesa package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Expected behavior: perform the "Basemark Web 3.0" benchmark (Firefox 87 and 88), at most a loss of performance. Real behavior: the benchmark completely crashes the system in one of the initial stages (4). The screen presents graphical distortion (it never happens), intense crashes and sometimes it is solved with the automatic suspension of the computer (which remains on at times). But it doesn't usually come back from the crash. The problem happens with the onboard ATI RADEON 3000 (RS780 driver) and it happens in both xorg and wayland. Ubuntu and kernel duly updated to the present date. Crash moment: WebGL 1.0.2 Test (test 4/20); "Loading scene_uv2.DAE" Benchmark website: https://web.basemark.com/ Motherboard: GA78LMT Ubuntu 20.04.2 LTS Kernel 5.8.0-50-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: poe1860 F pulseaudio /dev/snd/pcmC2D0p: poe1860 F...m pulseaudio /dev/snd/controlC0: poe1860 F pulseaudio /dev/snd/controlC1: poe1860 F pulseaudio BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2021-03-25 15:17:02,784 DEBUG /openCache(), new cache size 67025 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2021-03-04 (51 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Package: xorg-server (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal wayland-session wayland-session ubuntu Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-03-25 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
[Desktop-packages] [Bug 1926050] Re: [radeon] Web benchmark freezing and crashing the system
Thanks for that. Your system log shows it was Xorg crashing in the radeon driver: mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: radeon: The kernel rejected CS, see dmesg for more information (-16). mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) Backtrace: mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 0: /usr/bin/Xwayland (OsLookupColor+0x13c) [0x563171f8122c] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 1: /lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fd7d0f9547f] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (__nss_database_lookup+0x44c4) [0x7fd7d0ef52e4] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 3: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x74483) [0x7fd7cf85bde3] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 4: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x7a00b) [0x7fd7cf866c8b] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 5: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x128cc) [0x7fd7cf7982fc] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 6: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x13efe) [0x7fd7cf79b1fe] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 7: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x19952) [0x7fd7cf7a6592] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 8: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (nouveau_drm_screen_create+0x214793) [0x7fd7cfd68943] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 9: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (nouveau_drm_screen_create+0x21489a) [0x7fd7cfd68c5a] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 10: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (radeon_drm_winsys_create+0x5e6cd) [0x7fd7cf8301dd] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 11: /usr/lib/x86_64-linux-gnu/dri/r600_dri.so (__driDriverGetExtensions_zink+0x3b139) [0x7fd7cf1266c9] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 12: /usr/bin/Xwayland (glamor_get_modifiers+0x76d) [0x563171e27e3d] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 13: /usr/bin/Xwayland (XkbDDXTerminateServer+0x102) [0x563171f325c2] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 14: /usr/bin/Xwayland (XkbDDXTerminateServer+0x12cb) [0x563171f3496b] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 15: /usr/bin/Xwayland (XkbDDXTerminateServer+0x683) [0x563171f33013] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 16: /usr/bin/Xwayland (XkbDDXTerminateServer+0xc16) [0x563171f33b46] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 17: /usr/bin/Xwayland (XkbDDXTerminateServer+0x1f90) [0x563171f362b0] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 18: /usr/bin/Xwayland (SendErrorToClient+0x354) [0x563171f4a5c4] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 19: /usr/bin/Xwayland (InitFonts+0x3b4) [0x563171f4e654] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 20: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf3) [0x7fd7d0daf0b3] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) 21: /usr/bin/Xwayland (_start+0x2e) [0x563171e1c5be] mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) Bus error at address 0x7fd7d07c4000 mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: Fatal server error: mai 10 13:43:01 poe org.gnome.Shell.desktop[8107]: (EE) Caught signal 7 (Bus error). Server aborting ** Summary changed: - [radeon] Web benchmark freezing and crashing the system + [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so) ** Package changed: linux-hwe-5.8 (Ubuntu) => mesa (Ubuntu) ** Also affects: xserver-xorg-video-ati (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1926050 Title: [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so) Status in mesa package in Ubuntu: Incomplete Status in xserver-xorg-video-ati package in Ubuntu: Incomplete Bug description: Expected behavior: perform the "Basemark Web 3.0" benchmark (Firefox 87 and 88), at most a loss of performance. Real behavior: the benchmark completely crashes the system in one of the initial stages (4). The screen presents graphical distortion (it never happens), intense crashes and sometimes it is solved with the automatic suspension of the computer (which remains on at times). But it doesn't usually come back from the crash. The problem
[Desktop-packages] [Bug 1927801] Re: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login
Thanks. I can see lots of crashes and errors from your gnome-shell extensions. Please remove them by: cd /home/grizzlysmit/.local/share/gnome-shell/ rm -rf extensions then log out and in again. And if you experience any problems again after that then just follow the instructions in comment #5 again. -- 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/1927801 Title: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: 1. $ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 2. $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu2 Candidate: 3.38.4-1ubuntu2 Version table: *** 3.38.4-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected it to work like normal. 4. It locked up after 2 to 5 mins. I have tried logging into Xorg, a different account with no plugins I removed the extra monitor All to NO EFFECT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
** No longer affects: sddm (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927993] Re: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
*** This bug is a duplicate of bug 1922353 *** https://bugs.launchpad.net/bugs/1922353 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1922353, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Package changed: wayland (Ubuntu) => gnome-shell (Ubuntu) ** This bug has been marked a duplicate of bug 1922353 Overview sometimes fails to appear or disappear in 21.04 -- 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/1927993 Title: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction Status in gnome-shell package in Ubuntu: New Bug description: This also effects the Ubuntu Dock. Ubuntu 21.04 installed on a Micosoft Surface Go. When invoking the Activities Overview, the overview ceases to be responsive to mouse clicks or to touchscreen interaction. The only interaction to which it responds is the keyboard. Likewise, the Ubuntu Dock also ceases to respond to mouse gestures, clicks or to touchscreen interaction. Meanwhile, apps continue to respond to both Mouse and Touchscreen gestures. I haven't yet found a workaround. That said, I experimented yesterday with limiting myself to touchscreen interaction and the bug, for the period of time that used the system, didn't appear. It's possible that there's some kind of conflict between the mouse, touchscreen and Wayland usage? When used under a Xorg session, this Bug doesn't appear to affect the system. Notes: I chose Wayland as the affected passage but apparently Wayland "does not exist in Ubuntu". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926050] [NEW] [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so)
*** This bug is a security vulnerability *** You have been subscribed to a public security bug: Expected behavior: perform the "Basemark Web 3.0" benchmark (Firefox 87 and 88), at most a loss of performance. Real behavior: the benchmark completely crashes the system in one of the initial stages (4). The screen presents graphical distortion (it never happens), intense crashes and sometimes it is solved with the automatic suspension of the computer (which remains on at times). But it doesn't usually come back from the crash. The problem happens with the onboard ATI RADEON 3000 (RS780 driver) and it happens in both xorg and wayland. Ubuntu and kernel duly updated to the present date. Crash moment: WebGL 1.0.2 Test (test 4/20); "Loading scene_uv2.DAE" Benchmark website: https://web.basemark.com/ Motherboard: GA78LMT Ubuntu 20.04.2 LTS Kernel 5.8.0-50-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: poe1860 F pulseaudio /dev/snd/pcmC2D0p: poe1860 F...m pulseaudio /dev/snd/controlC0: poe1860 F pulseaudio /dev/snd/controlC1: poe1860 F pulseaudio BootLog: Error: [Errno 13] Permissão recusada: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME DistUpgraded: 2021-03-25 15:17:02,784 DEBUG /openCache(), new cache size 67025 DistroCodename: focal DistroRelease: Ubuntu 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd RS780L [Radeon 3000] [1458:d000] InstallationDate: Installed on 2021-03-04 (51 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 Package: xorg-server (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash radeon.audio=1 vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.187.11 Tags: focal wayland-session wayland-session ubuntu Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: Upgraded to focal on 2021-03-25 (30 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare _MarkForUpload: True dmi.bios.date: 11/25/2014 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F2 dmi.board.name: GA-78LMT-USB3 6.0 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: SEx dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd11/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-USB36.0:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-USB36.0:rvrSEx:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-78LMT-USB3 6.0 dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd apport-collected ati basemark benchmark crash focal freeze graphics instability performance radeon rs780 ubuntu wayland-session -- [radeon] Web benchmark freezing and crashing the system (Xorg crashes in Mesa's r600_dri.so) https://bugs.launchpad.net/bugs/1926050 You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa 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 1928017] Re: The Restriced Codecs article recommends an application that was recently discontinued
Thanks for calling our attention to this. It affects both ubuntu-docs and gnome-user-docs, so I submitted an upstream issue as well. ** Also affects: gnome-user-docs (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-user-docs (Ubuntu) Importance: Undecided => Medium ** Changed in: gnome-user-docs (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-docs (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-docs (Ubuntu) Status: New => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/gnome-user-docs/-/issues #123 https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues/123 ** Also affects: gnome-user-docs via https://gitlab.gnome.org/GNOME/gnome-user-docs/-/issues/123 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-user-docs in Ubuntu. https://bugs.launchpad.net/bugs/1928017 Title: The Restriced Codecs article recommends an application that was recently discontinued Status in Gnome Documentation: Unknown Status in gnome-user-docs package in Ubuntu: Confirmed Status in ubuntu-docs package in Ubuntu: Confirmed Bug description: https://help.ubuntu.com/stable/ubuntu-help/video-dvd-restricted.html https://help.ubuntu.com/stable/ubuntu-help/video-dvd.html.en These two help articles both recommend the Fluendo DVD Player for legally playing DVDs. However, Fluendo announced that they would be discontinuing their product as of April 11, 2021, and new licenses don't appear to be available anymore (https://fluendo.com/en/blog/post /oneplay-dvd-player-product-discontinuation/). As such, these instructions are no longer accurate. The AskUbuntu community is currently searching for alternatives (https://askubuntu.com/questions/1337426/legally-playing-dvds-post- april-2021), but, in the mean-time, at least a note saying that the software was discontinued will be helpful. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-user-docs/+bug/1928017/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1863608] Re: version 80 does not start using remote display (X11)
Thanks for the heads up. I upgraded Chromium to 90.0.4430.72-0ubuntu0.16.04.1 and it's working fine here as well. -- 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/1863608 Title: version 80 does not start using remote display (X11) Status in chromium-browser package in Ubuntu: Fix Released Bug description: chromium-browser version 80.0.3987.87-0ubuntu0.16.04.1_amd64 does not work when using remote display; the browser window is a solid pink area without any menu (see picture). Same with the (existing?) command line option "--disable-gpu" Downgrading to chromium-browser_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb chromium-browser-l10n_79.0.3945.130-0ubuntu0.16.04.1_all.deb chromium-codecs-ffmpeg-extra_79.0.3945.130-0ubuntu0.16.04.1_amd64.deb resolve the issue. Description: Ubuntu 16.04.6 LTS All packages are up to date on 2020-02-17 on xenial, xenial-updates and xenial-security To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1863608/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]
** Also affects: sddm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1915870 Title: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so] Status in Mesa: Unknown Status in mesa package in Ubuntu: Fix Released Status in sddm package in Ubuntu: New Status in mesa package in Fedora: Confirmed Bug description: Graphical user interface is not coming up upon start. Only SSH is possible. lsb_release -rd: Description: Ubuntu 20.10 Release: 20.10 dmesg: [ 11.985343] gnome-session-c[1013]: segfault at 0 ip sp 7fff7679ca48 error 14 in gnome-session-check-accelerated-gl-helper[56020e238000+2000] [ 11.985352] Code: Unable to access opcode bytes at RIP 0xffd6. [ 14.216117] gnome-shell[1094]: segfault at 0 ip sp 7ffeddff9f88 error 14 [ 14.216122] Code: Unable to access opcode bytes at RIP 0xffd6. [ 15.316292] gnome-shell[1109]: segfault at 0 ip sp 7ffc70716198 error 14 [ 15.316297] Code: Unable to access opcode bytes at RIP 0xffd6. apt-cache policy: gnome-session: Installed: (none) Candidate: 3.38.0-1ubuntu1 Version table: 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages gnome-session-bin: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 100 /var/lib/dpkg/status gnome-session-common: Installed: 3.38.0-1ubuntu1 Candidate: 3.38.0-1ubuntu1 Version table: *** 3.38.0-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages 100 /var/lib/dpkg/status /var/crash: see attachment To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927998] Re: Jitter/noise in document scan
** Package changed: ubuntu => simple-scan (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan in Ubuntu. https://bugs.launchpad.net/bugs/1927998 Title: Jitter/noise in document scan Status in simple-scan package in Ubuntu: New Bug description: Ubuntu 21.04 Documentscanner 3.38.1 When using the documentscanner about 10 times, without restarting the app, closing the previous scan (delete button), starting a new scan everytime, the background window (white) shows jitter/noise (in black) which will stay there every next scan. It may even become worse. The noise become part of the actual scan too! You will have to stop the app and reconnect the scanner. I've noticed this problem to be reproducable. See attached screen output. Kind regards, Gerard van Drielen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/simple-scan/+bug/1927998/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927998] [NEW] Jitter/noise in document scan
You have been subscribed to a public bug: Ubuntu 21.04 Documentscanner 3.38.1 When using the documentscanner about 10 times, without restarting the app, closing the previous scan (delete button), starting a new scan everytime, the background window (white) shows jitter/noise (in black) which will stay there every next scan. It may even become worse. The noise become part of the actual scan too! You will have to stop the app and reconnect the scanner. I've noticed this problem to be reproducable. See attached screen output. Kind regards, Gerard van Drielen ** Affects: simple-scan (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Jitter/noise in document scan https://bugs.launchpad.net/bugs/1927998 You received this bug notification because you are a member of Desktop Packages, which is subscribed to simple-scan 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 1923479] Re: out of buffer access and Integer overflow in Exiv2
This bug was fixed in the package exiv2 - 0.27.3-3ubuntu0.2 --- exiv2 (0.27.3-3ubuntu0.2) groovy-security; urgency=medium * SECURITY UPDATE: Heap buffer overflow - debian/patches/CVE-2021-3482-*.patch: fix buffer overflow in src/jp2image.cpp and adds tests test/data/poc_1522.jp2, tests/bugfixes/github/test_issue_1522.py. - debian/source/include-binaries: add poc_1522.jp2 entry. - CVE-2021-3482 * SECURITY UPDATE: An out of buffer access - debian/patches/CVE-2021-29457.patch: fix in src/jp2image.cpp (LP: #1923479) - CVE-2021-29457 * SECURITY UPDATE: Integer overflow - debian/patches/CVE-2021-29458.patch: fix in src/crwimage_int.cpp (LP: #1923479) - CVE-2021-29458 * SECURITY UPDATE: Out-of-bounds - debian/patches/CVE-2021-29470-*.patch: Add more bound checks in Jp2Image::encodeJp2Header and add some tests from/for github. - CVE-2021-29470 -- Leonidas Da Silva Barbosa Mon, 12 Apr 2021 15:25:12 -0300 ** Changed in: exiv2 (Ubuntu) Status: In Progress => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-29470 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-3482 ** Changed in: exiv2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: Fix Released Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2
This bug was fixed in the package exiv2 - 0.27.2-8ubuntu2.2 --- exiv2 (0.27.2-8ubuntu2.2) focal-security; urgency=medium * SECURITY UPDATE: Heap buffer overflow - debian/patches/CVE-2021-3482-*.patch: fix buffer overflow in src/jp2image.cpp and adds tests test/data/poc_1522.jp2, tests/bugfixes/github/test_issue_1522.py. - debian/source/include-binaries: add poc_1522.jp2 entry. - CVE-2021-3482 * SECURITY UPDATE: An out of buffer access - debian/patches/CVE-2021-29457.patch: fix in src/jp2image.cpp (LP: #1923479) - CVE-2021-29457 * SECURITY UPDATE: Integer overflow - debian/patches/CVE-2021-29458.patch: fix in src/crwimage_int.cpp (LP: #1923479) - CVE-2021-29458 * SECURITY UPDATE: Out-of-bounds - debian/patches/CVE-2021-29470-*.patch: Add more bound checks in Jp2Image::encodeJp2Header and add some tests from/for github. - CVE-2021-29470 -- Leonidas Da Silva Barbosa Tue, 13 Apr 2021 09:49:39 -0300 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: Fix Released Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923479] Re: out of buffer access and Integer overflow in Exiv2
This bug was fixed in the package exiv2 - 0.27.3-3ubuntu1.1 --- exiv2 (0.27.3-3ubuntu1.1) hirsute-security; urgency=medium * SECURITY UPDATE: Heap buffer overflow - debian/patches/CVE-2021-3482-*.patch: fix buffer overflow in src/jp2image.cpp and adds tests test/data/poc_1522.jp2, tests/bugfixes/github/test_issue_1522.py. - debian/source/include-binaries: add poc_1522.jp2 entry. - CVE-2021-3482 * SECURITY UPDATE: An out of buffer access - debian/patches/CVE-2021-29457.patch: fix in src/jp2image.cpp (LP: #1923479) - CVE-2021-29457 * SECURITY UPDATE: Integer overflow - debian/patches/CVE-2021-29458.patch: fix in src/crwimage_int.cpp (LP: #1923479) - CVE-2021-29458 * SECURITY UPDATE: Out-of-bounds - debian/patches/CVE-2021-29470-*.patch: Add more bound checks in Jp2Image::encodeJp2Header and add some tests from/for github. - CVE-2021-29470 -- Leonidas Da Silva Barbosa Mon, 12 Apr 2021 14:47:29 -0300 ** Changed in: exiv2 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to exiv2 in Ubuntu. https://bugs.launchpad.net/bugs/1923479 Title: out of buffer access and Integer overflow in Exiv2 Status in exiv2 package in Ubuntu: Fix Released Bug description: An out of buffer access: https://github.com/Exiv2/exiv2/commit/13e5a3e02339b746abcaee6408893ca2fd8e289d and a Integer overflow : https://github.com/Exiv2/exiv2/commit/9b7a19f957af53304655ed1efe32253a1b11a8d0 affects Exiv2 in ubuntu releases To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/exiv2/+bug/1923479/+subscriptions -- Mailing list: https://launchpad.net/~desktop-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
I am testing this again (this is supposed to work OOTB now, at least on Intel GPUs), and I'm seeing the following: libva info: VA-API version 1.9.0 libva info: User environment variable requested driver 'i965' libva info: Trying to open /snap/chromium/1568/gnome-platform/usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: va_openDriver() returns -1 even when I explicitly export LIBVA_DRIVERS_PATH=/snap/chromium/current/usr/lib/x86_64-linux-gnu/dri. This is caused by the snapcraft gnome-3-28 extension unconditionally overriding LIBVA_DRIVERS_PATH here: https://github.com/snapcore/snapcraft/blob/master/extensions/desktop/common /desktop-exports#L92 -- 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: News : - Candidate Chromium 83 Snap with vaapi enabled can be installed with : sudo snap install --channel=candidate/vaapi chromium Check that your vidéo is gpu decoded but checking "MojoVideoDecoder" in about:media-internals Widevine DRM streams will have DecryptingVideoDecoder Please report success/failure with - distro version - GPU Hardware used - Codec used --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 1928001] [NEW] [SRU] New stable release 2.68.1
Public bug reported: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: glib2.0 (Ubuntu Hirsute) Importance: Undecided Assignee: Iain Lane (laney) Status: In Progress ** Also affects: glib2.0 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released ** Changed in: glib2.0 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: glib2.0 (Ubuntu Hirsute) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1928001 Title: [SRU] New stable release 2.68.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Hirsute: In Progress Bug description: [ Description ] Take this new upstream stable release. * Fix a crash in `GKeyFile` when parsing a file which contains translations using a `GKeyFile` instance which has loaded another file previously (#2361) * Pin GIO DLL in memory on Windows (!2016) * Bugs fixed: - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to glib-2-68 - !2016 GIO W32: Pin gio DLL - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple lines” to glib-2-68 [ QA ] Upstream release, so QA already performed by maintainers https://wiki.ubuntu.com/StableReleaseUpdates/GNOME This upload will trigger many autopkgtests that we expect to not be regressed by this upload. [ What could go wrong ] This update contains fixes in multiple places so multiple apps could be affected. The consequences of a broken GLib can range from some functions returning bad results sometimes, which have minimal runtime implications, up to the system simply crashing all the time. Pretty much all parts of GNOME use GLib, so test anything in the desktop that you can. If you reboot the machine and can get to the desktop, that's already tested GLib extensively. But also run applications like GNOME terminal, Files and Epiphany. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927993] Re: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
** Package changed: ubuntu => wayland (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1927993 Title: Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction Status in wayland package in Ubuntu: New Bug description: This also effects the Ubuntu Dock. Ubuntu 21.04 installed on a Micosoft Surface Go. When invoking the Activities Overview, the overview ceases to be responsive to mouse clicks or to touchscreen interaction. The only interaction to which it responds is the keyboard. Likewise, the Ubuntu Dock also ceases to respond to mouse gestures, clicks or to touchscreen interaction. Meanwhile, apps continue to respond to both Mouse and Touchscreen gestures. I haven't yet found a workaround. That said, I experimented yesterday with limiting myself to touchscreen interaction and the bug, for the period of time that used the system, didn't appear. It's possible that there's some kind of conflict between the mouse, touchscreen and Wayland usage? When used under a Xorg session, this Bug doesn't appear to affect the system. Notes: I chose Wayland as the affected passage but apparently Wayland "does not exist in Ubuntu". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1927993/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927993] [NEW] Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction
You have been subscribed to a public bug: This also effects the Ubuntu Dock. Ubuntu 21.04 installed on a Micosoft Surface Go. When invoking the Activities Overview, the overview ceases to be responsive to mouse clicks or to touchscreen interaction. The only interaction to which it responds is the keyboard. Likewise, the Ubuntu Dock also ceases to respond to mouse gestures, clicks or to touchscreen interaction. Meanwhile, apps continue to respond to both Mouse and Touchscreen gestures. I haven't yet found a workaround. That said, I experimented yesterday with limiting myself to touchscreen interaction and the bug, for the period of time that used the system, didn't appear. It's possible that there's some kind of conflict between the mouse, touchscreen and Wayland usage? When used under a Xorg session, this Bug doesn't appear to affect the system. Notes: I chose Wayland as the affected passage but apparently Wayland "does not exist in Ubuntu". ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Gnome Activities Overview Unresponsive to Mouse or Touchscreen Interaction https://bugs.launchpad.net/bugs/1927993 You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland 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 1927801] Re: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login
it did it again after many hours ** Attachment added: "this is from running sudo journalctl -b-1 |tee ~/tmp/prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+attachment/5496196/+files/prevboot.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1927801 Title: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: 1. $ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 2. $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu2 Candidate: 3.38.4-1ubuntu2 Version table: *** 3.38.4-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected it to work like normal. 4. It locked up after 2 to 5 mins. I have tried logging into Xorg, a different account with no plugins I removed the extra monitor All to NO EFFECT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927801] Re: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login
** Summary changed: - on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login + on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login -- 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/1927801 Title: on my dual monitor 21.04 system gnome-shell locks up about 2 to 5 mins after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: 1. $ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 2. $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu2 Candidate: 3.38.4-1ubuntu2 Version table: *** 3.38.4-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected it to work like normal. 4. It locked up after 2 to 5 mins. I have tried logging into Xorg, a different account with no plugins I removed the extra monitor All to NO EFFECT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
** No longer affects: libreoffice (Ubuntu) ** Also affects: gtk+3.0 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu Hirsute) Status: New => In Progress ** Changed in: gtk+3.0 (Ubuntu Hirsute) Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 source package in Hirsute: In Progress Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926843] Re: online accounts integration with fb isn't working
But can you confirm: sudo add-apt-repository ppa:folke-schwinning/personal sudo apt-get update sudo apt-get install desktop-facebook sudo apt install npm nodejs-legacy git https://snapcraft.io/install/facebook-webapp/ubuntu Its this safe as worksaground or may is get safety issue? I want replacement for linux, because windows 10 android works with facebook but did no know how becauce is hard to get to works with wine HQ or other software? Because i did not know if APT get or other repo is protected other than wrong repo to old config, because some software may be maded only because developer get money for works with other company that get money on password leaks or other. Not sure if some of apps if safe because it can come software bugs to safety also. Or is snap\apt-get safe with install apps? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927970] [NEW] Maximised gnome-terminal not returning to normal size
Public bug reported: The default terminal size is 80x24 If the terminal is maximised then returned to normal by double clicking on the title bar the terminal ends up being 79x23 the first time, 78x22 the second time and so on. it can be reset by clicking on the burger menu -> advanced -> 80x24 I expect it to return to the same size it started at (80x24) lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 14:37:05 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-09-23 (228 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to focal on 2021-03-16 (54 days ago) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages -- 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/1927970 Title: Maximised gnome-terminal not returning to normal size Status in gnome-terminal package in Ubuntu: New Bug description: The default terminal size is 80x24 If the terminal is maximised then returned to normal by double clicking on the title bar the terminal ends up being 79x23 the first time, 78x22 the second time and so on. it can be reset by clicking on the burger menu -> advanced -> 80x24 I expect it to return to the same size it started at (80x24) lsb_release -rd Description: Ubuntu 20.04.2 LTS Release: 20.04 apt-cache policy gnome-terminal gnome-terminal: Installed: 3.36.2-1ubuntu1~20.04 Candidate: 3.36.2-1ubuntu1~20.04 Version table: *** 3.36.2-1ubuntu1~20.04 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.36.1.1-1ubuntu1 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-terminal 3.36.2-1ubuntu1~20.04 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 14:37:05 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 ExecutablePath: /usr/libexec/gnome-terminal-server InstallationDate: Installed on 2020-09-23 (228 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 ProcEnviron: LANG=en_GB.UTF-8 LANGUAGE=en_GB:en PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: Upgraded to focal on 2021-03-16 (54 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1927970/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927958] [NEW] Switching power source retains tab, even if it does not exist
Public bug reported: When switching from a power source (e.g., "Laptop battery") to another power source (e.g. "AC adapter"), where the latter does not have the tab which was selected in the former, then no information at all is displayed. Ubuntu 21.04, gnome-power-manager 3.32.0-2 Actual behavior === 1. `gnome-power-statistics` starts with "AC adapter" selected left and "Details" tab being shown on the right 2. Click on "Laptop battery" left: Laptop battery "Details" tab is shown on the right 3. Click on "History" or "Statistics" tab: The appropriate information for "Laptop battery" is shown on the right. So far, so good. 4. Click on "AC adapter" left again: Now, *nothing* is shown on the right. This should not happen. Expected behavior = 4. Click on "AC adapter": "Details" tab should be shown. (In general: *Any* tab should be shown, but here, "Details" is the only one available.) This is probably a result from trying to fix https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/766876 ** Affects: gnome-power-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1927958 Title: Switching power source retains tab, even if it does not exist Status in gnome-power-manager package in Ubuntu: New Bug description: When switching from a power source (e.g., "Laptop battery") to another power source (e.g. "AC adapter"), where the latter does not have the tab which was selected in the former, then no information at all is displayed. Ubuntu 21.04, gnome-power-manager 3.32.0-2 Actual behavior === 1. `gnome-power-statistics` starts with "AC adapter" selected left and "Details" tab being shown on the right 2. Click on "Laptop battery" left: Laptop battery "Details" tab is shown on the right 3. Click on "History" or "Statistics" tab: The appropriate information for "Laptop battery" is shown on the right. So far, so good. 4. Click on "AC adapter" left again: Now, *nothing* is shown on the right. This should not happen. Expected behavior = 4. Click on "AC adapter": "Details" tab should be shown. (In general: *Any* tab should be shown, but here, "Details" is the only one available.) This is probably a result from trying to fix https://bugs.launchpad.net/ubuntu/+source/gnome-power- manager/+bug/766876 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1927958/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927334] Re: [SRU] libreoffice 7.1.3 for hirsute
@sil2100 Thank you. 7.1.3~rc2 is identical to the final 7.1.3 -- 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/1927334 Title: [SRU] libreoffice 7.1.3 for hirsute Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice source package in Hirsute: Fix Committed Bug description: [Impact] * LibreOffice 7.1.3 is in its third bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.3_release * Version 7.1.2 is currently released in hirsute. For a list of fixed bugs compared to 7.1.2 see the list of bugs fixed in the release candidates of 7.1.3 (that's a total of 105 bugs): https://wiki.documentfoundation.org/Releases/7.1.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.1.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_linux_gcc_release/88872/console * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/amd64/libr/libreoffice/20210507_025053_79e42@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/arm64/libr/libreoffice/20210507_065558_93940@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/armhf/libr/libreoffice/20210507_020030_1b56f@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/ppc64el/libr/libreoffice/20210507_163628_d1422@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/s390x/libr/libreoffice/20210507_081728_18e2a@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 105 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1927334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926843] Re: online accounts integration with fb isn't working
** Description changed: + * Impact + + The online accounts setting are proposing a facebook item which isn't + working + + * Test case + + Go to settings -> online account, browse the accounts option proposed, + facebook shouldn't be in the list since it doesn't work. + + * Regression potential + + The change is to disable the facebook provider using the upstream + provided build option. Check that facebook isn't listed anymore but that + the other providers still are. Since it's a build option change it could + fail to build so check for that as well on launchpad. + + Since the facebook service currently doesn't consider gnome-online- + accounts as a valid client there should be no user with that provider + configured. Even if there were since the service isn't working they + would see a functional regression. + + --- + Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: * Impact The online accounts setting are proposing a facebook item which isn't working * Test case Go to settings -> online account, browse the accounts option proposed, facebook shouldn't be in the list since it doesn't work. * Regression potential The change is to disable the facebook provider using the upstream provided build option. Check that facebook isn't listed anymore but that the other providers still are. Since it's a build option change it could fail to build so check for that as well on launchpad. Since the facebook service currently doesn't consider gnome-online- accounts as a valid client there should be no user with that provider configured. Even if there were since the service isn't working they would see a functional regression. --- Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927334] Re: [SRU] libreoffice 7.1.3 for hirsute
Hello Rico, or anyone else affected, Accepted libreoffice into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libreoffice/1:7.1.3-0ubuntu0.21.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: libreoffice (Ubuntu) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-hirsute -- 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/1927334 Title: [SRU] libreoffice 7.1.3 for hirsute Status in libreoffice package in Ubuntu: Fix Committed Status in libreoffice source package in Hirsute: Fix Committed Bug description: [Impact] * LibreOffice 7.1.3 is in its third bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.3_release * Version 7.1.2 is currently released in hirsute. For a list of fixed bugs compared to 7.1.2 see the list of bugs fixed in the release candidates of 7.1.3 (that's a total of 105 bugs): https://wiki.documentfoundation.org/Releases/7.1.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.1.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_linux_gcc_release/88872/console * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/amd64/libr/libreoffice/20210507_025053_79e42@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/arm64/libr/libreoffice/20210507_065558_93940@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/armhf/libr/libreoffice/20210507_020030_1b56f@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/ppc64el/libr/libreoffice/20210507_163628_d1422@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/s390x/libr/libreoffice/20210507_081728_18e2a@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 105 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to:
[Desktop-packages] [Bug 1926843] Re: online accounts integration with fb isn't working
> its because facebook did not want to use it on linux or safety issue? no, it's the code in gnome-online-accounts which isn't properly maintained upstream at the moment, they would need to do changes to the code and follow the registration process for the service Ideally that would be fixed and enabled, but until that happens it's less misleading to not propose the option than to have one that isn't working -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1926843 Title: online accounts integration with fb isn't working Status in gnome-online-accounts package in Ubuntu: Fix Released Bug description: Hi i tryed to use gnome-control-center online-accounts to make easy like windows 10 to login to email or add other login so its more easy with ID to use pincode or other ID fingerprint and other. But its look its much issue compared with windows 10 with thunderbird, firefox, and other program. Worst is facebook only little windows with issue with login? ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-online-accounts 3.38.1-1ubuntu1 Uname: Linux 5.12.0-051200-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 1 19:38:03 2021 InstallationDate: Installed on 2019-05-07 (725 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to hirsute on 2021-04-06 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1926843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927954] [NEW] Installing gnome-themes-extra breaks UI color
Public bug reported: I'm using ubuntu 16 I have a need to upgrade Ubuntu 18.04. However after upgrading, the color of UI was changed to white (It should be grey as it is). It tooks me a day to find out the root cause is from gnome-themes-extra. Ubuntu 16 does not have this package, but it is automatically installed when upgrading to 18.04. This white happens not only folder window, but also another app. Please see the image https://ibb.co/swh4g8B Thanks. ** Affects: gnome-themes-extra (Ubuntu) Importance: Undecided Status: New ** Attachment added: "colorbreak.png" https://bugs.launchpad.net/bugs/1927954/+attachment/5496152/+files/colorbreak.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-extra in Ubuntu. https://bugs.launchpad.net/bugs/1927954 Title: Installing gnome-themes-extra breaks UI color Status in gnome-themes-extra package in Ubuntu: New Bug description: I'm using ubuntu 16 I have a need to upgrade Ubuntu 18.04. However after upgrading, the color of UI was changed to white (It should be grey as it is). It tooks me a day to find out the root cause is from gnome-themes-extra. Ubuntu 16 does not have this package, but it is automatically installed when upgrading to 18.04. This white happens not only folder window, but also another app. Please see the image https://ibb.co/swh4g8B Thanks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-themes-extra/+bug/1927954/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927334] Re: [SRU] libreoffice 7.1.3 for hirsute
Please be sure to take a look at the autopkgtests after this is accepted, since the ones attached to the bug seem to be from ~rc2. -- 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/1927334 Title: [SRU] libreoffice 7.1.3 for hirsute Status in libreoffice package in Ubuntu: In Progress Status in libreoffice source package in Hirsute: Fix Committed Bug description: [Impact] * LibreOffice 7.1.3 is in its third bugfix release of the 7.1 line: https://wiki.documentfoundation.org/ReleasePlan/7.1#7.1.3_release * Version 7.1.2 is currently released in hirsute. For a list of fixed bugs compared to 7.1.2 see the list of bugs fixed in the release candidates of 7.1.3 (that's a total of 105 bugs): https://wiki.documentfoundation.org/Releases/7.1.3/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.1.3/RC2#List_of_fixed_bugs * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_linux_gcc_release/88872/console * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/amd64/libr/libreoffice/20210507_025053_79e42@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/arm64/libr/libreoffice/20210507_065558_93940@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/armhf/libr/libreoffice/20210507_020030_1b56f@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/ppc64el/libr/libreoffice/20210507_163628_d1422@/log.gz * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-hirsute-libreoffice-libreoffice-prereleases/hirsute/s390x/libr/libreoffice/20210507_081728_18e2a@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 105 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1927334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted iptables-netflow into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/iptables- netflow/2.4-2ubuntu0.4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security
[Desktop-packages] [Bug 1927948] Re: Windows switch monitor after resuming from sleep
I have a Dell XPS 13 7390 2-in-1 with two external monitors. The first external monitor is connected via USB-C/Thunderbolt, the second one via DP from the first external monitor. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1927948 Title: Windows switch monitor after resuming from sleep Status in mutter package in Ubuntu: New Bug description: What I expect: Window layout/positioning is identical after resume from sleep. What I observe: After resume from sleep, windows appear on a different monitor than before. I found this possibly relevant GNOME bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 10 13:40:28 2021 InstallationDate: Installed on 2019-12-02 (524 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1927948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927948] [NEW] Windows switch monitor after resuming from sleep
Public bug reported: What I expect: Window layout/positioning is identical after resume from sleep. What I observe: After resume from sleep, windows appear on a different monitor than before. I found this possibly relevant GNOME bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 10 13:40:28 2021 InstallationDate: Installed on 2019-12-02 (524 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1927948 Title: Windows switch monitor after resuming from sleep Status in mutter package in Ubuntu: New Bug description: What I expect: Window layout/positioning is identical after resume from sleep. What I observe: After resume from sleep, windows appear on a different monitor than before. I found this possibly relevant GNOME bug: https://gitlab.gnome.org/GNOME/mutter/-/issues/1419 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter 3.38.4-1ubuntu2 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon May 10 13:40:28 2021 InstallationDate: Installed on 2019-12-02 (524 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: mutter UpgradeStatus: Upgraded to hirsute on 2021-05-05 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1927948/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1296085] Re: HP LaserJet 1020 io/hpmud/musb.c 150: unable get_string_descriptor -7: Resource temporarily unavailable
See https://bugs.launchpad.net/hplip/+bug/1922404 for a possible fix. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/1296085 Title: HP LaserJet 1020 io/hpmud/musb.c 150: unable get_string_descriptor -7: Resource temporarily unavailable Status in HPLIP: Triaged Status in hplip package in Ubuntu: Confirmed Status in hplip package in Fedora: Won't Fix Bug description: After upgrading to Ubuntu 14.04 unstable, I can no longer print to my HP LaserJet 1020. This is identical to Fedora bug 1047135: https://bugzilla.redhat.com/show_bug.cgi?id=1047135 `uname -a`: Linux ares 3.13.0-18-generic #38-Ubuntu SMP Mon Mar 17 21:40:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux When I plug in my printer, `tail dmesg` looks like this: [ 4269.639715] usb 2-1.6: new high-speed USB device number 43 using ehci-pci [ 4269.751434] usb 2-1.6: New USB device found, idVendor=03f0, idProduct=2b17 [ 4269.751439] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 4269.751442] usb 2-1.6: Product: HP LaserJet 1020 [ 4269.751445] usb 2-1.6: Manufacturer: Hewlett-Packard [ 4269.751448] usb 2-1.6: SerialNumber: JL0Z6XM [ 4269.754716] usblp 2-1.6:1.0: usblp2: USB Bidirectional printer dev 43 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 [ 4272.980952] usblp2: removed `lsusb` shows the printer: Bus 002 Device 043: ID 03f0:2b17 Hewlett-Packard LaserJet 1020 But then when I run `hp-setup`, it's not found: 12:07:44 adam@ares:~$ hp-setup -g -i '002:043' HP Linux Imaging and Printing System (ver. 3.14.3) Printer/Fax Setup Utility ver. 9.0 Copyright (c) 2001-13 Hewlett-Packard Development Company, LP This software comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to distribute it under certain conditions. See COPYING file for more details. hp-setup[8280]: debug: param=002:043 hp-setup[8280]: debug: selected_device_name=None (Note: Defaults for each question are maked with a '*'. Press to accept the default.) hp-setup[8280]: debug: Trying USB with bus=002 dev=043... hp-setup[8280]: debug: Not found. ... I do see some error messages in syslog: Mar 22 12:07:26 ares kernel: [ 4269.754716] usblp 2-1.6:1.0: usblp2: USB Bidirectional printer dev 43 if 0 alt 0 proto 2 vid 0x03F0 pid 0x2B17 Mar 22 12:07:26 ares logger: loading HP Device 002 043 Mar 22 12:07:29 ares kernel: [ 4272.980952] usblp2: removed Mar 22 12:07:32 ares colord: Device added: sysfs-Hewlett-Packard-HP_LaserJet_1020 Mar 22 12:09:28 ares python: io/hpmud/musb.c 150: unable get_string_descriptor -7: Resource temporarily unavailable Mar 22 12:09:28 ares python: io/hpmud/musb.c 2206: invalid product id string ret=-7 Mar 22 12:09:33 ares python: io/hpmud/musb.c 150: unable get_string_descriptor -7: Resource temporarily unavailable Mar 22 12:09:33 ares python: io/hpmud/musb.c 2211: invalid serial id string ret=-7 Mar 22 12:09:38 ares python: io/hpmud/musb.c 150: unable get_string_descriptor -7: Resource temporarily unavailable Mar 22 12:09:38 ares python: io/hpmud/musb.c 2078: invalid product id string ret=-7 Mar 22 12:09:43 ares python: io/hpmud/musb.c 150: unable get_string_descriptor -7: Resource temporarily unavailable Mar 22 12:09:43 ares python: io/hpmud/musb.c 2083: invalid serial id string ret=-7 Mar 22 12:09:48 ares python: io/hpmud/musb.c 150: unable get_string_descriptor -7: Resource temporarily unavailable Mar 22 12:09:48 ares python: io/hpmud/musb.c 2088: invalid manufacturer string ret=-7 And finally, I can strace an hpmud command to see that it fails. (Attached.) This behavior is consistent with the Fedora bug. It appears like a broken USB connection, but I've tried two working cables on USB ports at the back and front of my computer. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1296085/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927801] Re: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login
it's not happening just now, > 1:20:00 and still nothing bad will see how it goes will do what you asked if it plays up, hmm there have been updates wonder if any of those where dependancies -- 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/1927801 Title: on my dual monitor 21.04 systemm gnome-shell locks up about 2 to 5 mins after login Status in gnome-shell package in Ubuntu: Incomplete Bug description: 1. $ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 2. $ apt-cache policy gnome-shell gnome-shell: Installed: 3.38.4-1ubuntu2 Candidate: 3.38.4-1ubuntu2 Version table: *** 3.38.4-1ubuntu2 500 500 http://au.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status 3. I expected it to work like normal. 4. It locked up after 2 to 5 mins. I have tried logging into Xorg, a different account with no plugins I removed the extra monitor All to NO EFFECT To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1927801/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908082] Re: Ubuntu Firefox is 15% slower than Flatpak Firefox for speedometer benchmark
@Tynach, the symptoms you describe do advocate in favour of the toolchain/optimizations hypothesis. If upstream builds are not affected, wherease Ubuntu builds are, when both are run on the same platform, surely there is a difference in the optimizations used to produce the binary under test. That said I've tested your sample shader in shadertoy on Ubuntu 21.04, and while the framerate is not super constant it does hit 60FPS regularly (chromium is behaving better, also around 60FPS but with a much more constant framerate than firefox). That's with the firefox Ubuntu build, and the chromium snap. -- 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/1908082 Title: Ubuntu Firefox is 15% slower than Flatpak Firefox for speedometer benchmark Status in firefox package in Ubuntu: Incomplete Bug description: Steps to reproduce: I installed Firefox Flatpak (https://flathub.org/apps/details/org.mozilla.firefox) and Chrome. I executed closed all apps and processes and one by one I executed Speedometer test (https://browserbench.org/Speedometer2.0/) in each browser 3 times. I took the max score for reach browser out of the 3 executions of the test. Actual results: Results 100.3 - Firefox Flatpak 85.42 - FIrefox DEB (pre-installd from the store) 100.3 - Google Chrome The preinstalled DEB package Firefox was slower than both Firefox Flatpak and Chrome Expected results: I expected Firefox DEB and Firefox Flatpak to have the same results. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1908082/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927347] Re: Cannot reply to PGP-encrypted email despite OpenPGP being configured for account - thunderbird claims missing signing certificate
This sounds like it might be an upstream bug. Would you mind filing it at https://bugzilla.mozilla.org/enter_bug.cgi#h=dupes%7CThunderbird, and sharing the link here? ** Changed in: thunderbird (Ubuntu) Status: New => Incomplete -- 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/1927347 Title: Cannot reply to PGP-encrypted email despite OpenPGP being configured for account - thunderbird claims missing signing certificate Status in thunderbird package in Ubuntu: Incomplete Bug description: $ lsb_release -rd Description: Ubuntu 21.04 Release: 21.04 $ apt-cache policy thunderbird thunderbird: Installed: 1:78.8.1+build1-0ubuntu1 Candidate: 1:78.8.1+build1-0ubuntu1 Version table: *** 1:78.8.1+build1-0ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages 100 /var/lib/dpkg/status Situation: Both PGP and S/MIME configured for an account, all credentials up to date and configured for the identity of the account. The chosen OpenPGP key has both a sign/certify primary key, and an encryption subkey. What I expect to happen: When receiving an email encrypted with PGP/GPG I expect to be able to respond, encrypted with OpenPGP. What happens: I can decrypt the email, I can hit respond, but then receive the error: "You specified that this message should be digitally signed, but the application either failed to find the signing certificate specified in your Mail & Newsgroup Account Settings, or the certificate has expired." The "Options" -> "Encryption Technology" is set to S/MIME and choosing OpenPGP is not possible (grey). I'm surprised first, that I cannot choose OpenPGP (since the original sender does not have an S/MIME certificate and using OpenPGP is the only option to communicate securely in this case), and that apparently the *signing certificate* was missing. I searched the web a bit, some people suggested to reconfigure the key chosen with the account, but this does not change anything in my case. Sending the same person an email and encrypting it with OpenPGP works like a charm, it only fails when I reply to their emails. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: thunderbird 1:78.8.1+build1-0ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BuildID: 20210304234616 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Thu May 6 12:20:34 2021 InstallationDate: Installed on 2021-04-07 (29 days ago) InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Beta amd64 (20210331.1) SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1927347/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927513] Re: Failure to install chromium-browser/chromium snap
Yes, your symlink is very likely the cause of this error. You weren't seeing the problem in 18.04 because chromium was a a real deb package there, whereas starting with 20.04 it is packaged as a snap. This is not chromium-specific, all snaps would fail to install with such a setup. One possible workaround would be to bind mount /media/galvani/francesco/home to /home instead of using a symlink. -- 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/1927513 Title: Failure to install chromium-browser/chromium snap Status in chromium-browser package in Ubuntu: New Bug description: On an up-to-date Ubuntu 20.04 system, I can't 'sudo apt install chromium-browser': Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: chromium-browser 0 upgraded, 1 newly installed, 0 to remove and 3 not upgraded. Need to get 0 B/48.3 kB of archives. After this operation, 164 kB of additional disk space will be used. Preconfiguring packages ... (Reading database ... 293039 files and directories currently installed.) Preparing to unpack .../chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb ... => Installing the chromium snap ==> Checking connectivity with the snap store ==> Installing the chromium snap Fehler: cannot perform the following tasks: - Den Konfigurationshook von Snap "chromium" ausführen, falls vorhanden (run hook "configure": cannot perform operation: mount --rbind /home /tmp/snap.rootfs_PJbiPg//home: Permission denied) dpkg: error processing archive /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb (--unpack): new chromium-browser package pre-installation script subprocess returned error exit status 1 Errors were encountered while processing: /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu0.20.04.2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Might that 'mount' command have an issue with my '/home -> media/galvani/francesco/home' symlink? (But that has not been a problem in the previous Ubuntu 18.04 installation, where I'm reasonably sure that I did have a snap or two installed, too.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1927513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926194] Re: Web Content consuming too much CPU
It sounds like firefox is not doing hardware-accelerated video decoding. Can you browse to about:support, copy the contents of the page and share them here? Can you also browse to about:config, search for "vaapi" and verify that the two matching options are set to true, then restart firefox (if you had to change the values) and test again? ** 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/1926194 Title: Web Content consuming too much CPU Status in firefox package in Ubuntu: Incomplete Bug description: whenever i use youtube on firefox it starts to lag. when i check the CPU consumption in system moniter Web Content is using a big chunk of it. When i shut firefox the issue dissapears and the system works fine ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.143 Fri Mar 12 07:24:47 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Mon Apr 26 23:02:56 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell 2nd Generation Core Processor Family Integrated Graphics Controller [1028:04ca] NVIDIA Corporation GF108M [GeForce GT 525M] [10de:0df5] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell GF108M [GeForce GT 525M] [1028:04ca] InstallationDate: Installed on 2021-02-28 (57 days ago) InstallationMedia: Ubuntu-Budgie 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210210.1) MachineType: Dell Inc. Inspiron N5110 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=a9722871-3677-4e60-b24d-50d268347ce0 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/30/2011 dmi.bios.release: 0.9 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 0FXK2Y dmi.board.vendor: Dell Inc. dmi.board.version: A09 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.ec.firmware.release: 0.9 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd09/30/2011:br0.9:efr0.9:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn0FXK2Y:rvrA09:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron N5110 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1926194/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927751] Re: Firefox 89 beta for Impish in Mozilla Team Firefox Beta PPA is built without Wayland support
This was caused by the upload of libdrm 2.4.105-2 to the archive, and is now resolved in version 2.4.105-3 (https://launchpad.net/ubuntu/+source/libdrm/2.4.105-3). So the next build in the firefox-next PPA should have Wayland support again. ** Changed in: firefox (Ubuntu) Status: Confirmed => Invalid -- 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/1927751 Title: Firefox 89 beta for Impish in Mozilla Team Firefox Beta PPA is built without Wayland support Status in firefox package in Ubuntu: Invalid Bug description: The Impish build of Firefox 89 beta in the PPA seems to be built without Wayland support. This of course causes it to work only in XWayland mode when running in Wayland, but also breaks VAAPI in both environments due to "DMABUF unavailable by default: Wayland support missing" as reported in about:support. I am reporting this here instead of upstream because the upstream builds are not affected by this issue (they have Wayland and VAAPI working) and also the Hirsute builds in the PPA have both things working properly. It seems limited to the Impish builds. Additionally, if I check the build logs for Impish, the only mention of Wayland seems to be the build dependency packages being installed. If I check the logs for Hirsute, I see a number of references during the compilation itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1927751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927751] Re: Firefox 89 beta for Impish in Mozilla Team Firefox Beta PPA is built without Wayland support
I can confirm this. This line in the build log is relevant: 0:15.05 checking for gtk+-wayland-3.0 >= 3.14 xkbcommon >= 0.4.1 libdrm >= 2.4... no ** Changed in: firefox (Ubuntu) Status: New => Confirmed -- 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/1927751 Title: Firefox 89 beta for Impish in Mozilla Team Firefox Beta PPA is built without Wayland support Status in firefox package in Ubuntu: Confirmed Bug description: The Impish build of Firefox 89 beta in the PPA seems to be built without Wayland support. This of course causes it to work only in XWayland mode when running in Wayland, but also breaks VAAPI in both environments due to "DMABUF unavailable by default: Wayland support missing" as reported in about:support. I am reporting this here instead of upstream because the upstream builds are not affected by this issue (they have Wayland and VAAPI working) and also the Hirsute builds in the PPA have both things working properly. It seems limited to the Impish builds. Additionally, if I check the build logs for Impish, the only mention of Wayland seems to be the build dependency packages being installed. If I check the logs for Hirsute, I see a number of references during the compilation itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1927751/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927940] [NEW] [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all
Public bug reported: It's a notebook with internal audio and HDMI. The sound card cant be used at all. Pulse audio only shows "Dummy Output". Adding "options snd-hda-intel model=generic" to "/etc/modprobe.d/alsa- base.conf" shows at least the HDMI out. But internal analogue output still won't appear. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mia1766 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 11:55:50 2021 InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mia1766 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: HW-13.3-BI-X133GRX210-040-A dmi.board.asset.tag: OEM default string inject dmi.board.name: LINCPLUS dmi.board.vendor: LINCPLUS dmi.board.version: 1.0 dmi.chassis.asset.tag: OEM default string inject dmi.chassis.type: 10 dmi.chassis.vendor: OEM default string inject dmi.chassis.version: OEM default string inject dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrHW-13.3-BI-X133GRX210-040-A:bd01/06/2021:br5.13:svnLINCPLUS:pnLINCPLUSP1:pvrOEMdefaultstringinject:rvnLINCPLUS:rnLINCPLUS:rvr1.0:cvnOEMdefaultstringinject:ct10:cvrOEMdefaultstringinject: dmi.product.family: TVE1315E dmi.product.name: LINCPLUS P1 dmi.product.sku: 1315E20201113001 dmi.product.version: OEM default string inject dmi.sys.vendor: LINCPLUS modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-05-10T11:51:26.728974 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1927940 Title: [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: It's a notebook with internal audio and HDMI. The sound card cant be used at all. Pulse audio only shows "Dummy Output". Adding "options snd-hda-intel model=generic" to "/etc/modprobe.d/alsa- base.conf" shows at least the HDMI out. But internal analogue output still won't appear. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mia1766 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 10 11:55:50 2021 InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Eingebautes Tongerät - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mia1766 F pulseaudio Symptom_Jack: Digital Out, HDMI Symptom_Type: No sound at all Title: [LINCPLUS P1, Intel Geminilake HDMI, Digital Out, HDMI] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/06/2021 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: HW-13.3-BI-X133GRX210-040-A dmi.board.asset.tag: OEM default string inject dmi.board.name: LINCPLUS dmi.board.vendor: LINCPLUS dmi.board.version: 1.0 dmi.chassis.asset.tag: OEM default string inject dmi.chassis.type: 10 dmi.chassis.vendor: OEM default string inject dmi.chassis.version: OEM default string inject dmi.modalias:
[Desktop-packages] [Bug 1927837] Re: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: o subprocesso do pacote chromium-browser, novo script pre-installation retornou
Thank you for the report. Can you run the following command in a terminal, and share the output here? snap list --all ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1927837 Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: o subprocesso do pacote chromium-browser, novo script pre-installation retornou erro do status de saída 1 Status in chromium-browser package in Ubuntu: Incomplete Bug description: Na atualização de versão do Linux Ubuntu, quando o computador pediu para reinicializar o pacote e o computador apresentou diversas falhas dentro do SO e não queria dar boot para inicializar os pacotes. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-72.80-generic 5.4.101 Uname: Linux 5.4.0-72-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat May 8 12:00:01 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32 ErrorMessage: o subprocesso do pacote chromium-browser, novo script pre-installation retornou erro do status de saída 1 InstallationDate: Installed on 2020-07-18 (294 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.5 Snap.Changes: ID Status Spawn Ready Summary 6Error 2021-05-08T11:56:14-03:00 2021-05-08T12:00:00-03:00 Install "chromium" snap 7Error 2021-05-08T12:01:43-03:00 2021-05-08T12:02:06-03:00 Install "chromium" snap 8Error 2021-05-08T12:03:37-03:00 2021-05-08T12:03:59-03:00 Install "chromium" snap 9Error 2021-05-08T12:08:26-03:00 2021-05-08T12:08:43-03:00 Install "chromium" snap Snap.ChromeDriverVersion: Error: command ['snap', 'run', 'chromium.chromedriver', '--version'] failed with exit code 1: error: cannot find current revision for snap chromium: readlink /snap/chromium/current: no such file or directory Snap.ChromiumVersion: Error: command ['snap', 'run', 'chromium', '--version'] failed with exit code 1: error: cannot find current revision for snap chromium: readlink /snap/chromium/current: no such file or directory Snap.Connections: Error: command ['snap', 'connections', 'chromium'] failed with exit code 1: error: snap "chromium" not found SourcePackage: chromium-browser Title: package chromium-browser 1:85.0.4183.83-0ubuntu0.20.04.2 failed to install/upgrade: o subprocesso do pacote chromium-browser, novo script pre-installation retornou erro do status de saída 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1927837/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1918269] Re: moving tabs to a new window no longer works.
So that's an upstream change, not specific to the chromium snap. Can you please file a bug at https://crbug.com/ and share the link here? -- 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/1918269 Title: moving tabs to a new window no longer works. Status in chromium-browser package in Ubuntu: New Bug description: Somewhat similar to bug #999632, but different and quite new. When I have a tab that I want to move to a NEW window, I used to be able to drag the tab and then when releasing it near the tab bar of another chromium window, it would snap into that window's tab list. This still works. But when I release the tab NOT near the tab bar of another window, it used to create a new window. This is convenient: I have multiple screens so when I decide I need to view this tab alongside something in my existing window, I drag the tab to create a new window on the other screen. Workaround: create a new window first then drag the tab there. But this "used to work". It is not necessary to do it like this. I liked it the old way. This changed somewhere in the last week. The behaviour swapped on my home computer yesterday (but it was still normal at work) and today I had to restart chromium (because all new tabs were reporting "aw snap!", reported in another bugreport) and now it's here too. Package: chromium Versions: Reverse Depends: chromium-bsu,chromium 0.9.14 x2gothinclient-minidesktop,chromium webext-ublock-origin,chromium webext-proxy-switcher,chromium webext-privacy-badger,chromium webext-bulk-media-downloader,chromium webext-browserpass,chromium polymake,chromium gnome-core,chromium djview-plugin,chromium cinnamon-desktop-environment,chromium chromium-tt-rss-notifier,chromium chromium-lwn4chrome,chromium chromium-bsu,chromium 0.9.14 chrome-gnome-shell,chromium chrome-gnome-shell,chromium Dependencies: Provides: Reverse Provides: Description:Ubuntu 20.04.2 LTS Release:20.04 % apt-cache policy chromium chromium: Installed: (none) Candidate: (none) Version table: % [] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1918269/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927936] [NEW] My display is flashes
Public bug reported: All my desktop windows are flashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 12:24:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad X240 [17aa:2214] InstallationDate: Installed on 2021-04-10 (29 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20AL00C6MS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2018 dmi.bios.release: 2.44 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AL00C6MS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:br2.44:efr1.17:svnLENOVO:pn20AL00C6MS:pvrThinkPadX240:rvnLENOVO:rn20AL00C6MS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20AL00C6MS dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927936 Title: My display is flashes Status in xorg package in Ubuntu: New Bug description: All my desktop windows are flashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 12:24:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad X240 [17aa:2214] InstallationDate: Installed on 2021-04-10 (29 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20AL00C6MS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2018 dmi.bios.release: 2.44 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AL00C6MS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:br2.44:efr1.17:svnLENOVO:pn20AL00C6MS:pvrThinkPadX240:rvnLENOVO:rn20AL00C6MS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20AL00C6MS dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx
[Desktop-packages] [Bug 1927766] Re: Nautilus - unable to format USB drive
*** This bug is a duplicate of bug 1853784 *** https://bugs.launchpad.net/bugs/1853784 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1853784, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 1853784 Format button has no effect when I right click a USB and select Format -- 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/1927766 Title: Nautilus - unable to format USB drive Status in nautilus package in Ubuntu: New Bug description: Ubuntu 21.04 - Right click on USB drive in Nautilus and selecting format does nothing area51pilot@area51:~$ nautilus Insync Nautilus Plugin [__init__ insync plugin] Nautilus-Share-Message: 12:04:49.633: Called "net usershare info" but it failed: Failed to execute child process “net” (No such file or directory) Cannot parse integer value “3a7” for --xid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1927766/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927936] Re: My display is flashes
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1924624, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1924624 After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge) graphics a lot of glitches render screen unusable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927936 Title: My display is flashes Status in xorg package in Ubuntu: New Bug description: All my desktop windows are flashes. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.17 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 12:24:44 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkPad X240 [17aa:2214] InstallationDate: Installed on 2021-04-10 (29 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20AL00C6MS ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-50-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/20/2018 dmi.bios.release: 2.44 dmi.bios.vendor: LENOVO dmi.bios.version: GIET94WW (2.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20AL00C6MS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.17 dmi.modalias: dmi:bvnLENOVO:bvrGIET94WW(2.44):bd09/20/2018:br2.44:efr1.17:svnLENOVO:pn20AL00C6MS:pvrThinkPadX240:rvnLENOVO:rn20AL00C6MS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X240 dmi.product.name: 20AL00C6MS dmi.product.sku: LENOVO_MT_20AL_BU_Think_FM_ThinkPad X240 dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1927936/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914279] Re: linux from security may force reboots without complete dkms modules
virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (s390x, ppc64el, armhf, arm64) -> is a false negative. virtualbox-hwe is only supported on amd64 i thought. https://autopkgtest.ubuntu.com/packages/v/virtualbox https://autopkgtest.ubuntu.com/packages/v/virtualbox-hwe Suggests that to be the case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1914279 Title: linux from security may force reboots without complete dkms modules Status in acpi-call package in Ubuntu: New Status in apt package in Ubuntu: Invalid Status in backport-iwlwifi-dkms package in Ubuntu: New Status in bcmwl package in Ubuntu: New Status in dahdi-linux package in Ubuntu: New Status in dkms package in Ubuntu: Fix Released Status in dm-writeboost package in Ubuntu: New Status in evdi package in Ubuntu: New Status in gost-crypto package in Ubuntu: New Status in iptables-netflow package in Ubuntu: New Status in liblzf package in Ubuntu: New Status in lime-forensics package in Ubuntu: New Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: Triaged Status in lttng-modules package in Ubuntu: New Status in nvidia-graphics-drivers-340 package in Ubuntu: New Status in openafs package in Ubuntu: New Status in oss4 package in Ubuntu: New Status in r8168 package in Ubuntu: New Status in rtl8812au package in Ubuntu: New Status in sysdig package in Ubuntu: New Status in unattended-upgrades package in Ubuntu: Invalid Status in update-manager package in Ubuntu: Invalid Status in v4l2loopback package in Ubuntu: New Status in virtualbox package in Ubuntu: New Status in virtualbox-hwe package in Ubuntu: New Status in zfs-linux package in Ubuntu: New Status in acpi-call source package in Focal: Fix Committed Status in backport-iwlwifi-dkms source package in Focal: Fix Committed Status in bcmwl source package in Focal: Fix Committed Status in dahdi-linux source package in Focal: Fix Committed Status in dm-writeboost source package in Focal: Fix Committed Status in evdi source package in Focal: Fix Committed Status in gost-crypto source package in Focal: Fix Committed Status in iptables-netflow source package in Focal: Fix Committed Status in liblzf source package in Focal: Fix Committed Status in lime-forensics source package in Focal: Fix Committed Status in lttng-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Fix Committed Status in oss4 source package in Focal: Fix Committed Status in r8168 source package in Focal: Fix Committed Status in rtl8812au source package in Focal: Fix Committed Status in sysdig source package in Focal: Fix Committed Status in v4l2loopback source package in Focal: Fix Committed Status in virtualbox source package in Focal: Fix Committed Status in virtualbox-hwe source package in Focal: Fix Committed Status in zfs-linux source package in Focal: Fix Committed Bug description: Whilst discussing https://discourse.ubuntu.com/t/improvements-for-hardware-support-in- ubuntu-desktop-installation-media/20606 We have noticed a reference to somebody not having working backport- iwlwifi-dkms, whilst SRU of that happened before the v5.4 -> v5.8 switch. However, kernel meta switch was pushed to security pocket, but the dkms modules are all in -updates only. This may result in people automatically installing the new kernel with unatanded upgrades; dkms modules failing to build; and a reboot required flag left on disk. At this point launching update manager will not offer to install dkms modules from updates, and will guide the users to reboot. which will then cause them to boot the new kernel without the dkms modules that might be providing networking for them. Should dkms modules SRUs always getting published into -security pocket, as well as the -updates pocket? Should linux maintainer scripts prevent touching reboot required flag if any dkms modules fail to build? Should apt / unattanded-upgrades / update-manager always update dkms modules with kernels? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/acpi-call/+bug/1914279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925822] Re: [21.04 regression] formatting vfat times out
I installed udisks2 2.9.2-1ubuntu1 from hirsute-proposed, and confirm
that both the manual test case above as well as cockpit's automatic
TestStorageFormat.testFormatTypes now succeed. Thank you Sebastien and
Robie!
** Tags removed: verification-needed verification-needed-hirsute
** Tags added: verification-done verification-done-hirsute
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1925822
Title:
[21.04 regression] formatting vfat times out
Status in udisks2 package in Ubuntu:
Fix Committed
Status in udisks2 source package in Hirsute:
Fix Committed
Bug description:
* Impact
Formatting devices to vfat fails in some cases due to an
incompatibility with the new dosfstools version
* Test case
see comment #5
or
- $ sudo modprobe scsi_debug
- check what device is assigned
- $ sudo busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/DEVNAME org.freedesktop.UDisks2.Block
Format 'sa{sv}' vfat 0
(replace DEVNAME by the actual device name, 'sdc' for example)
the formatting should work which you can verify by
- $ blkid -p /dev/DEVNAME
* Regression potential
The changes is specific to vfat handling so that's the feature to
focus on while testing, make sure than creating, deleting, renaming
vfat partitions from gnome-disks is working.
[racb] An upstream "precautionary" partprobe is being added following
the mkfs for vfat, when it didn't do this before. This is a change in
behaviour that might expose a problem elsewhere.
There is a regression somewhere between udisks, udev, and dosfstools.
Formatting a device with vfat hangs and fails:
# blkid -p /dev/sda
(nothing)
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}' vfat 0
(long pause)
Call failed: Error synchronizing after formatting with type `vfat': Timed out
waiting for object
# blkid -p /dev/sda
/dev/sda: PTUUID="3690494f" PTTYPE="dos"
OTOH, formatting as ext4 works fine:
# wipefs -a /dev/sda; wipefs -a /dev/sda
# busctl call org.freedesktop.UDisks2
/org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format
'sa{sv}' ext4 0
(immediately succeeds)
# blkid -p /dev/sda
/dev/sda: UUID="8bea7475-6af5-4835-86d0-0e5b2cb5500e" VERSION="1.0"
BLOCK_SIZE="4096" TYPE="ext4" USAGE="filesystem"
I tested this to a QEMU emulated disk, but it reproduces equally well
against a `modprobe scsi_debug` device.
Package: udisks2 2.9.2-1
DistroRelease: Ubuntu 21.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1925822/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
The definition of "confirmed" is that "Verified by someone other than the reporter.", hence in case of "gnome-terminal" it was wrong to remove the "confirmed" tag, since someone other than me reported as well that the "gnome-terminal" is affected, and hence it is totally right, that the "gnome-terminal" is non the list named "Affects" with the status of "Confirmed". No one told, that "gnome-terminal" is mainly responsible for the bug, but the title of the list is *not* "The responsible packages", *but* "Affects". And it is "Confirmed" that "gnome-terminal" is "Affected". Henc I ask someone else, especially who removed it, to put back the "Confirmed" status. Since the "opinion" or "invalid" vould be missleading, and simply the opposite of the real truth. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Opinion Status in mutter package in Ubuntu: Opinion Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925732] Re: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal
The bug is clearly stated, reproducible and confirmed by others as well. Hence it can not be ONLY "invalid + opinion + opinion" at 3 packages, and no package is mentioned with "new" or "confirmed". It is acceptable, if someone's opinion is that "mutter is not new but opinion only". But it is not acceptable, if the same person does not mark any other package or the Ubuntu as a whole as "new" or "confirmed", --- since if all the packages mentioned already becomes either "invalid" or "opinion", then the bug report is rejected in fact, what would be a wrong decision since the bug is there confiredly. In fact, if wayland protocol is not advanced enough to provide the original standard facility to handle the positioning of windows, then ALL the packages that wish to use this original standard instead of the new facilities, all of them have the bug, because it is a buggy behaviour to rely on something what is not offerd by the underlying wayland. Therefore the releases 21.04 as a whole has this bug: makes something defuault what brakes the all the packages which wish to position the main window of it's own applications. A disturbing exampe: $ wmctrl -d Cannot get current desktop properties. (_NET_CURRENT_DESKTOP or _WIN_WORKSPACE property) $ wmctrl -l $ wmctrl -d does not "List all desktops managed by the window manager." wmctrl -l does not "List the windows being managed by the window manager." While the same "wmctrl" packages works fine with Xorg. However the "wmctrl" can not be added to the affected packages, since the bugs.launchpad does not accept "wmctrl" as an existing package! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1925732 Title: [wayland] gnome window manager ignores the --geometry location request of the gnome-terminal Status in gnome-terminal package in Ubuntu: Opinion Status in mutter package in Ubuntu: Opinion Status in gnome-terminal package in Fedora: Invalid Bug description: The example "gnome-terminal --geometry=80x24+200+200" from the man page of gnome-terminal, does not work: while the 80x24 part of the geometry request is executed, the location +200+200 is overridden by the automatic positioning of new windows by the "Gnome Shell". "--geometry=GEOMETRY Set the window size as COLSxROWS+X+Y. For example, 80x24 or 80x24+200+200." The "+X+Y" part is ignored since I upgraded from 20.10 to 21.04 yesterday, just 4 hours after the official release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1925732/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1925379] Re: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4
This bug was fixed in the package gtk+3.0 - 3.24.25-1ubuntu6 --- gtk+3.0 (3.24.25-1ubuntu6) impish; urgency=medium * debian/patches/git_imcontext.patch: - cherry pick imcontext fixes until 3.24.29 (LP: #1925379) -- Rico Tzschichholz Sat, 01 May 2021 10:01:31 +0200 ** Changed in: gtk+3.0 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1925379 Title: Auto-Correct in LibreOffice does not work with 3.24.25-1ubuntu4 Status in gtk+3.0 package in Ubuntu: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: I just did a fresh install of Ubuntu 21.04 (smooth as silk), but then discovered that Auto-Correct in LibreOffice does not work. Yesterday, when I was still running 20.04, Auto-Correct worked fine -- same LibreOffice version, same LibreOffice profile, same LibreOffice document, and no changes on my part to my LibreOffice settings since I installed Ubuntu 21.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1925379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
Will try in the evening CET. tg On Mon, 10 May 2021 at 10:05, Daniel van Vugt <1922...@bugs.launchpad.net> wrote: > > Is anyone affected able to build their own gnome-shell? If so then > please try this patch: > > https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1794.patch > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1922353 > > Title: > Overview sometimes fails to appear or disappear in 21.04 > > Status in gnome-shell package in Ubuntu: > Confirmed > Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: > Confirmed > > Bug description: > When I press the "windows" or "options" or "super" key a list of > running applications (like alt-tab) and a text window appears. I can > choose from the running applications or write a command into the text > window. After I chose an application or press ESC all this disappear > and I can do my thing. > > Since trying 21.04 sometimes this > 1. does not appear properly - there is no visible text window > 2. does not disappear - despite what I click on or what keys do I press > this never disappear so I can not use my running applications or start > anything new even from the menu. > > I have to log out and in to break this. > > Disabling my gnome-shell extensions or using xorg instead of wayland > does not helps. > > Since upgrading this morning this happens every time I press Super, > not just occasionally, thus making my desktop unusable. > > ProblemType: Bug > DistroRelease: Ubuntu 21.04 > Package: gnome-shell 3.38.4-1ubuntu1 > ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 > Uname: Linux 5.11.0-13-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu61 > Architecture: amd64 > CasperMD5CheckResult: unknown > CurrentDesktop: ubuntu:GNOME > Date: Fri Apr 2 14:07:39 2021 > DisplayManager: gdm3 > InstallationDate: Installed on 2020-03-19 (378 days ago) > InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) > RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 > SourcePackage: gnome-shell > UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- we do what we must because we can -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04
Is anyone affected able to build their own gnome-shell? If so then please try this patch: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1794.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1922353 Title: Overview sometimes fails to appear or disappear in 21.04 Status in gnome-shell package in Ubuntu: Confirmed Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Confirmed Bug description: When I press the "windows" or "options" or "super" key a list of running applications (like alt-tab) and a text window appears. I can choose from the running applications or write a command into the text window. After I chose an application or press ESC all this disappear and I can do my thing. Since trying 21.04 sometimes this 1. does not appear properly - there is no visible text window 2. does not disappear - despite what I click on or what keys do I press this never disappear so I can not use my running applications or start anything new even from the menu. I have to log out and in to break this. Disabling my gnome-shell extensions or using xorg instead of wayland does not helps. Since upgrading this morning this happens every time I press Super, not just occasionally, thus making my desktop unusable. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 2 14:07:39 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-03-19 (378 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.38.4-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to hirsute on 2021-03-06 (27 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927919] Re: Screen flicker, sections going dark, icons and filenames vanishing, flickering or looking jumbled up
*** This bug is a duplicate of bug 1924624 *** https://bugs.launchpad.net/bugs/1924624 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1924624, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1924624 After upgrade to kernel 5.8.0-49/50 with Intel Gen7 (Haswell/Ivy Bridge) graphics a lot of glitches render screen unusable -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927919 Title: Screen flicker, sections going dark, icons and filenames vanishing, flickering or looking jumbled up Status in xorg package in Ubuntu: New Bug description: Started about 2 weeks ago, tried reinstalling Ubuntu20lts as fix yet issue persists. I can't use terminal because whatever I type, after the third letter things vanish, or become jumbled and impossible to recognise. Attempted updating intel drivers but wasn't successful, I'm not the best at this sort of thing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 09:22:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20B7S0XX0L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=ba39f6c6-e11e-4a3c-abb7-d8d45b02a4a6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2014 dmi.bios.release: 2.22 dmi.bios.vendor: LENOVO dmi.bios.version: GJET72WW (2.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S0XX0L dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET72WW(2.22):bd02/21/2014:br2.22:efr1.9:svnLENOVO:pn20B7S0XX0L:pvrThinkPadT440:rvnLENOVO:rn20B7S0XX0L:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440 dmi.product.name: 20B7S0XX0L dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T440 dmi.product.version: ThinkPad T440 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1927919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1927919] [NEW] Screen flicker, sections going dark, icons and filenames vanishing, flickering or looking jumbled up
Public bug reported: Started about 2 weeks ago, tried reinstalling Ubuntu20lts as fix yet issue persists. I can't use terminal because whatever I type, after the third letter things vanish, or become jumbled and impossible to recognise. Attempted updating intel drivers but wasn't successful, I'm not the best at this sort of thing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 09:22:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20B7S0XX0L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=ba39f6c6-e11e-4a3c-abb7-d8d45b02a4a6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2014 dmi.bios.release: 2.22 dmi.bios.vendor: LENOVO dmi.bios.version: GJET72WW (2.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S0XX0L dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.ec.firmware.release: 1.9 dmi.modalias: dmi:bvnLENOVO:bvrGJET72WW(2.22):bd02/21/2014:br2.22:efr1.9:svnLENOVO:pn20B7S0XX0L:pvrThinkPadT440:rvnLENOVO:rn20B7S0XX0L:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440 dmi.product.name: 20B7S0XX0L dmi.product.sku: LENOVO_MT_20B7_BU_Think_FM_ThinkPad T440 dmi.product.version: ThinkPad T440 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1927919 Title: Screen flicker, sections going dark, icons and filenames vanishing, flickering or looking jumbled up Status in xorg package in Ubuntu: New Bug description: Started about 2 weeks ago, tried reinstalling Ubuntu20lts as fix yet issue persists. I can't use terminal because whatever I type, after the third letter things vanish, or become jumbled and impossible to recognise. Attempted updating intel drivers but wasn't successful, I'm not the best at this sort of thing. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon May 10 09:22:33 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:220c] InstallationDate: Installed on 2021-05-09 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20B7S0XX0L ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=ba39f6c6-e11e-4a3c-abb7-d8d45b02a4a6 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2014 dmi.bios.release: 2.22 dmi.bios.vendor: LENOVO dmi.bios.version: GJET72WW (2.22 ) dmi.board.asset.tag: Not Available dmi.board.name: 20B7S0XX0L dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor:
[Desktop-packages] [Bug 1925344] Re: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth
** Summary changed: - Session not started after reboot (black screen) - requires switching tty back and forth + [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1925344 Title: [nvidia] Session not started after reboot (black screen) - requires switching tty back and forth Status in gdm3 package in Ubuntu: New Status in nvidia-graphics-drivers-460 package in Ubuntu: New Status in nvidia-prime package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: After installation, the first boot works as expected - the system boots into a graphical shell login screen. However all subsequent reboots end up with a black screen with a blinking cursor in the top- left corner of the screen. To get to the login screen, one has to switch to a different tty (like tty2 with ctrl+alt+f2) and then to tty1. Running `prime-select query` shows `nvidia`. Interesting enough, when I change the nvidia-prime settings at least once, like to on-demand via `prime-select on-demand` - then everything starts working as expected. Even when I switch back to `nvidia`. Not sure which package I should fill this under. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xserver-xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 460.67 Thu Mar 11 00:11:45 UTC 2021 GCC version: ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 21 15:20:15 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation CometLake-H GT2 [UHD Graphics] [8086:9bc4] (rev 05) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics [1028:09e1] NVIDIA Corporation TU116M [GeForce GTX 1660 Ti Mobile] [10de:2191] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell TU116M [GeForce GTX 1660 Ti Mobile] [1028:09e1] InstallationDate: Installed on 2021-04-21 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. G3 3500 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=5b38428b-60e8-4741-8b7f-0e60094a80f7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2020 dmi.bios.release: 1.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.1 dmi.board.name: 06ND9G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.1:bd12/04/2020:br1.7:svnDellInc.:pnG33500:pvr:rvnDellInc.:rn06ND9G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: GSeries dmi.product.name: G3 3500 dmi.product.sku: 09E1 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1925344/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1922437] Re: login into desktop is stuttering on wayland
** Bug watch removed: gitlab.gnome.org/GNOME/gnome-shell/-/issues #3571 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3571 -- 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/1922437 Title: login into desktop is stuttering on wayland Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 21.04 devel with kernel 5.11.0-13-generic up to date @ 3/4/2021 Login from gdm till desktop is loaded gives stuttering mousepointer and dock (for 7 seconds) loading until the desktop icons are visible, then the stuttering goes away and the desktop works stable after comparing this on xorg, things get much smoother loading into desktop ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: mutter (not installed) ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7 Uname: Linux 5.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 3 17:07:10 2021 InstallationDate: Installed on 2021-04-03 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210403) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1922437/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1923389] Re: Screenshot different colours
** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3033 Importance: Unknown Status: Unknown ** No longer affects: gnome-shell ** Bug watch removed: gitlab.gnome.org/GNOME/gnome-screenshot/-/issues #113 https://gitlab.gnome.org/GNOME/gnome-screenshot/-/issues/113 -- 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/1923389 Title: Screenshot different colours Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu version 18.04.5 LTS. gnome-screenshot: Installed: 3.25.0-0ubuntu2 Candidate: 3.25.0-0ubuntu2 Version table: *** 3.25.0-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status Expected: Both colors on the image and the web page are the same hex code. Happened instead: Diffent colour hex. Taking a screenshot from a webpage changes the colors slighlty. I have attached a video of what is happening, its a slighlt different colour but still different altogether. From a HTML page it is #11283C but when I place the screenshot on top of a background with that color, its clearly different. On image the hex is #0D253D. I have attached a video of the process To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1923389/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1913672] Re: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width
Zero reports of this crash in hirsute (which is version 3.38.4) so consider it fixed. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released -- 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/1913672 Title: gnome-shell 3.38.2-1ubuntu1~20.10.1 is crashing with assertion failures in st_bin_get_preferred_width Status in gnome-shell package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.38.2-1ubuntu1~20.10.1, the problem page at https://errors.ubuntu.com/problem/4f12318421d8c95c357e2db953aa75b2cdcacdfa contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1913672/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
Yeah I thought so. The problem was obvious a while back but has been gone for a couple of months or so. ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mesa (Ubuntu) Status: Incomplete => Fix Released ** Changed in: mutter (Ubuntu) Status: Incomplete => Fix Released -- 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/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Fix Released Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1872802] Re: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions)
Just upgrade, I just tried Ubuntu again and I didn't get the problem this time. Looks like it's fixed in Ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1872802 Title: Resizing any window will randomly result in graphics corruption for a fraction of a second (in Xorg sessions) Status in gnome-shell package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: When resizing any window in any direction the window can appear glitchy as presented in the screenshot. This glitchy appearance is restored immediately. The issue seems to be seen less often when the CPU is utilized more heavily, as when I recorded the screen with OBS to grab the screenshot. The screenshots shows gnome-system-monitor, but I could trigger it with Firefox, gnome-terminal and others. No such issues were experienced with previously installed Ubuntu Mate or Windows 10. Graphics: Mesa Intel® HD Graphics 620 (KBL GT2) on the Intel® Core™ i5-7200U CPU @ 2.50GHz × 4 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.1-4ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 14 20:45:47 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-14 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) RelatedPackageVersions: mutter-common 3.36.1-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1872802/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
