[Desktop-packages] [Bug 1844132] Re: FFe: Mesa 19.2.0
Mmkay, based on the above, I say go for it. It'll miss beta (unless we have reason to respin, I guess), but such is life. -- 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/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+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 1222602]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/727. -- 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/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Unknown Status in Nux: Fix Released Status in Release Notes for Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+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 1222602] Re: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers
** Changed in: mesa Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #727 https://gitlab.freedesktop.org/mesa/mesa/issues/727 -- 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/1222602 Title: [regression] [gen3] Mesa 9.2 makes Unity unusable on Atom class hardware and 943/945 graphics controllers Status in Mesa: Unknown Status in Nux: Fix Released Status in Release Notes for Ubuntu: Invalid Status in mesa package in Ubuntu: Fix Released Status in nux package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Bug description: After the upgrade to Mesa 9.2.0 unity is barely usable. Dash, Alt+Tab switcher and Alt+F2 command line shows in more than 1 minute, using 100% cpu. A downgrade to mesa 9.1.6-2ubuntu2 restores full performance. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgl1-mesa-glx 9.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-5.11-generic 3.11.0 Uname: Linux 3.11.0-5-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.12.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Mon Sep 9 01:51:45 2013 DistUpgraded: 2013-09-08 20:36:47,811 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Mobile 945GSE Express Integrated Graphics Controller [8086:27ae] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] Subsystem: Micro-Star International Co., Ltd. Device [1462:0110] InstallationDate: Installed on 2013-09-07 (1 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424) MachineType: MICRO-STAR INTERNATIONAL CO., LTD U90/U100 MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-5-generic root=UUID=674329c8-d0a6-4954-89c0-72821cfa0ba8 ro quiet splash vt.handoff=7 SourcePackage: mesa UpgradeStatus: Upgraded to saucy on 2013-09-08 (0 days ago) dmi.bios.date: 12/01/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4.6.3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: U90/U100 dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.board.version: Ver.001 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: MICRO-STAR INTERNATIONAL CO., LTD dmi.chassis.version: Ver.001 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4.6.3:bd12/01/2009:svnMICRO-STARINTERNATIONALCO.,LTD:pnU90/U100:pvrVer.001:rvnMICRO-STARINTERNATIONALCO.,LTD:rnU90/U100:rvrVer.001:cvnMICRO-STARINTERNATIONALCO.,LTD:ct10:cvrVer.001: dmi.product.name: U90/U100 dmi.product.version: Ver.001 dmi.sys.vendor: MICRO-STAR INTERNATIONAL CO., LTD version.compiz: compiz 1:0.9.10+13.10.20130828.2-0ubuntu1 version.libdrm2: libdrm2 2.4.46-1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.14.2.901-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu6 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.14-4ubuntu3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Mon Sep 9 01:46:55 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1001 vendor HSD xserver.version: 2:1.14.2.901-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1222602/+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 1275042] Re: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC
** No longer affects: mesa (Ubuntu) ** Project changed: mesa => mesa (Ubuntu) ** Changed in: mesa (Ubuntu) Status: Unknown => New ** Changed in: mesa (Ubuntu) Remote watch: freedesktop.org Bugzilla #72877 => None ** Changed in: mesa (Ubuntu) Status: New => Triaged ** Description changed: - Hi all, + Upstream report: + https://gitlab.freedesktop.org/mesa/mesa/issues/477 I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code but IBM pSeries machines without graphics cards need this code. This code translates the colors in a wrong way for Radeon graphics cards. I removed this code and after compiling Mesa again, the colors are displayed correctly. I released some unofficial Mesa versions with this patch. Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib- unofficial.html Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM XFX Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian --- ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107] Package: libgl1-mesa-dri 11.1.2-1ubuntu1 PackageArchitecture: powerpc ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash ProcModules: kvm_pr 91899 0 - Live 0x Tags: xenial ubuntu Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 -- 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/1275042 Title: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC Status in mesa package in Ubuntu: Triaged Bug description: Upstream report: https://gitlab.freedesktop.org/mesa/mesa/issues/477 I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code
[Desktop-packages] [Bug 880952] Re: Evince prints gdk critical failings on console output
[Expired for evince (Ubuntu) because there has been no activity for 60 days.] ** Changed in: evince (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/880952 Title: Evince prints gdk critical failings on console output Status in evince package in Ubuntu: Expired Bug description: Evince is printing a bunch of gdk critical warnings when running from the console to open any kind of pdf file. Example: $ evince template.pdf (evince:2750): GLib-GObject-WARNING **: g_object_set_valist: construct property "enable-gestures" for object `EvView' can't be set after construction (evince:2750): Gdk-CRITICAL **: gdk_window_get_pointer: assertion `GDK_IS_WINDOW (window)' failed ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: evince 3.2.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4 Uname: Linux 3.0.0-12-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: i386 Date: Mon Oct 24 14:17:51 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: PATH=(custom, no user) LANG=en_US.ISO-8859-1 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/880952/+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 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: This is a fresh installation of 18.04. After entering the password and pressing enter, it takes 5 seconds for the lock screen to disappear. This problem didn't happen on the same machine with 16.04 or 14.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 15:31:48 2018 InstallationDate: Installed on 2018-05-04 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+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 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
[Expired for gdm3 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gdm3 (Ubuntu) Status: Incomplete => Expired -- 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/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: This is a fresh installation of 18.04. After entering the password and pressing enter, it takes 5 seconds for the lock screen to disappear. This problem didn't happen on the same machine with 16.04 or 14.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 15:31:48 2018 InstallationDate: Installed on 2018-05-04 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+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 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: This is a fresh installation of 18.04. After entering the password and pressing enter, it takes 5 seconds for the lock screen to disappear. This problem didn't happen on the same machine with 16.04 or 14.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 15:31:48 2018 InstallationDate: Installed on 2018-05-04 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+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 1774188] Re: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions)
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1774188 Title: Unlocking the screen takes 5 seconds in Xorg sessions (not so much in Wayland sessions) Status in gdm3 package in Ubuntu: Expired Status in gnome-shell package in Ubuntu: Expired Status in mutter package in Ubuntu: Expired Status in xorg-server package in Ubuntu: Expired Bug description: This is a fresh installation of 18.04. After entering the password and pressing enter, it takes 5 seconds for the lock screen to disappear. This problem didn't happen on the same machine with 16.04 or 14.04. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.28.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17 Uname: Linux 4.15.0-22-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed May 30 15:31:48 2018 InstallationDate: Installed on 2018-05-04 (25 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1774188/+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 1837902] Re: Ubuntu Software doesn't show any update description
[Expired for gnome-software (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-software (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1837902 Title: Ubuntu Software doesn't show any update description Status in gnome-software package in Ubuntu: Expired Bug description: When Ubuntu releases an update the only information I get in Ubuntu Software is the one shown in the attached screenshot: no list of updates packages at all. Similarly, after clicking on the Update button, only a tiny progress bar is shown, it's never clear what is being done. I remember having used gnome-software in Fedora and the update process was more informative. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1837902/+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 1275042] [NEW] Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC
You have been subscribed to a public bug: Hi all, I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code but IBM pSeries machines without graphics cards need this code. This code translates the colors in a wrong way for Radeon graphics cards. I removed this code and after compiling Mesa again, the colors are displayed correctly. I released some unofficial Mesa versions with this patch. Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib- unofficial.html Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM XFX Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian --- ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107] Package: libgl1-mesa-dri 11.1.2-1ubuntu1 PackageArchitecture: powerpc ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash ProcModules: kvm_pr 91899 0 - Live 0x Tags: xenial ubuntu Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected regression-release saucy trusty ubuntu xenial -- Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC https://bugs.launchpad.net/bugs/1275042 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 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
Hi team, Please let us know if this is as-designed or not, Ubuntu desktop version was using /etc/network/interfaces to configure static IP address and etc... Best regards, Pengpeng -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Confirmed Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+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 1843044]
[Bugbug](https://github.com/mozilla/bugbug/) thinks this bug should belong to this component, but please revert this change in case of error. -- 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/1843044 Title: firefox crashes on a FIPS enabled machine Status in Mozilla Firefox: New Status in firefox package in Ubuntu: New Bug description: [IMPACT] firefox is not a FIPS certified library. firefox uses bundled nss and on a machine running FIPS enabled kernel, nss by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. This is an untested configuration and since firefox with bundled nss is not a certified library we propose disabling reading the 'fips_enabled' flag and therefore switching the library automatically into FIPS mode. A FIPS customer reported firefox crash on a FIPS enabled system and strace showed it was repeatedly trying to read the fips_enabled flag from the bundled nss before crashing. The proposed patch disables reading the /proc/sys/crypto/fips_enabled flag. The users of the library however can force nss into FIPS mode via an environment variable. We plan to leave it as is so as not to regress existing users who may be using it. The issue impacts firefox versions in eoan, disco, bionic and xenial. lsb_release -rd Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 Version: 2:3.45-1ubuntu1 lsb_release -rd Description: Ubuntu Disco Dingo Release: 19.04 Version: 2:3.42-1ubuntu2 lsb_release -rd Description: Ubuntu Bionic Beaver Release: 18.04 Version: 2:3.35-2ubuntu2.3 lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 Version: 2:3.28.4-0ubuntu0.16.04 [FIX] This fix proposes to disable bundled nss in firefox reading proc/sys/crypto/fips_enabled. We only want fips certified modules reading this file and running in fips mode. firefox is not one of our fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. Users who do want to run the library in FIPS mode can do so by using the environment variable "NSS_FIPS". We propose to leave it as is so as not to regress anyone using this. The user who is using this option should be doing so with the awareness. [TEST] Tested on a xenial and bionic desktop ISO running FIPS enabled kernel and in FIPS mode. With the patch fix no crashes were observed when launching firefox browser. Without the patch fix, firefox crashes. Tested on a xenial and bionic desktop ISO running non-FIPS generic kernel. With the patch fix, firefox worked as expected and no changes were observed. [REGRESSION POTENTIAL] The regression potential for this is small. A FIPS kernel is required to create /proc/sys/crypto/fips_enabled and it is not available in the standard Ubuntu archive. For users forcing FIPS through environment variable, nothing has changed. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1843044/+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 1275042] Re: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC
** Changed in: mesa Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/issues #477 https://gitlab.freedesktop.org/mesa/mesa/issues/477 -- 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/1275042 Title: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Bug description: Hi all, I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code but IBM pSeries machines without graphics cards need this code. This code translates the colors in a wrong way for Radeon graphics cards. I removed this code and after compiling Mesa again, the colors are displayed correctly. I released some unofficial Mesa versions with this patch. Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib- unofficial.html Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM XFX Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian --- ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107] Package: libgl1-mesa-dri 11.1.2-1ubuntu1 PackageArchitecture: powerpc ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash ProcModules: kvm_pr 91899 0 - Live 0x Tags: xenial ubuntu Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1275042/+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 1275042]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/477. -- 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/1275042 Title: Wrong colors with Mesa 11.1.2-1 on ubuntu MATE 16.04 PowerPC Status in Mesa: Unknown Status in mesa package in Ubuntu: Triaged Bug description: Hi all, I've tried Mesa 9.2.2-1 and 10.0.1 on Debian Sid, Lubuntu 13.10, and on Lubuntu 14.04. Unfortunately all have issued false colors in games. They appear to be ABGR instead of RGBA, thus blue becomes green, red becomes alpha etc. This issue affects sdl2 applications either. The Mesa version 11.1.2-1 doesn't work either on ubuntu MATE 16.04 PowerPC. Mesa 8.0.5-4 and Mesa 9.1.6 have no color problem. The transitional solution is to install the old Mesa 8.0.X with "Force Version" with the Synaptic package manager on new distributions. In my point of view, the problem is in the source file p_format.h in the directory src/gallium/include/pipe/. There is some code for translating colors for big-endian machines. The problem is, this code is only for the CPU. I mean for LLVMpipe for the CPU. The Radeon graphics cards don't need this translating code but IBM pSeries machines without graphics cards need this code. This code translates the colors in a wrong way for Radeon graphics cards. I removed this code and after compiling Mesa again, the colors are displayed correctly. I released some unofficial Mesa versions with this patch. Downloads: http://www.supertuxkart-amiga.de/amiga/mesalib- unofficial.html Hardware: AmigaOne X1000 (Nemo) PA Semi Dual-core PA6T-1682M, 1.8GHz PowerISA™ v2.04+ CPU "Xena" 500MHz XMOS XS1-L2 124 8GB DDR2 SDRAM XFX Radeon HD 6870, 1 GB RAM OCZ600MXSP 600 Switching power supply RTL 8139/8139C/8139C+ network card TSSTcorp CDDVDW SH-224BB dvd drive ATA ST2000DM001-9YN1 SEAGATE HD ATA ESA 3SF1240GB HD More information: http://en.wikipedia.org/wiki/AmigaOne_X1000 http://www.supertuxkart-amiga.de/amiga/x1000.html Rgds, Christian --- ApportVersion: 2.20-0ubuntu3 Architecture: powerpc CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: MATE DistUpgraded: Fresh install DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Barts XT [Radeon HD 6870] [1002:6738] (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Barts XT [Radeon HD 6870] [1682:3107] Package: libgl1-mesa-dri 11.1.2-1ubuntu1 PackageArchitecture: powerpc ProcKernelCmdLine: root=/dev/sdb1 quiet ro splash ProcModules: kvm_pr 91899 0 - Live 0x Tags: xenial ubuntu Uname: Linux 4.5.0-rc6_A-EON_AmigaONE_X1000_Nemo ppc64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.67-1 version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1 To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1275042/+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 1845102] [NEW] Video tearing in Celluloid with new Yaru theme
Public bug reported: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 My specs: Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz Latest version of Celluloid (0.17) obtained by PPA: https://launchpad.net/~xuzhen666/+archive/ubuntu/gnome-mpv When I use the new Ubuntu 19.10 dev theme (all gray Yaru), video playback starts to tear in Celluloid (I wasn't able to capture it with SimpleScreenRecorder, sorry, the tearing does not appear in the capture). Really similar tearing occurs with Adwaita as the enabled theme. It however does NOT occur at all with the older Yaru theme (which I copied from my Ubuntu 19.04 install). There is no tearing with any of the themes enabled in Wayland. Tearing is scant and impossible to appreciate in VLC. These issues occur only in X, and in Celluloid. The reason I'm reporting this to you is because it coincides with the theme change. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1845102 Title: Video tearing in Celluloid with new Yaru theme Status in yaru-theme package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 My specs: Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz Latest version of Celluloid (0.17) obtained by PPA: https://launchpad.net/~xuzhen666/+archive/ubuntu/gnome-mpv When I use the new Ubuntu 19.10 dev theme (all gray Yaru), video playback starts to tear in Celluloid (I wasn't able to capture it with SimpleScreenRecorder, sorry, the tearing does not appear in the capture). Really similar tearing occurs with Adwaita as the enabled theme. It however does NOT occur at all with the older Yaru theme (which I copied from my Ubuntu 19.04 install). There is no tearing with any of the themes enabled in Wayland. Tearing is scant and impossible to appreciate in VLC. These issues occur only in X, and in Celluloid. The reason I'm reporting this to you is because it coincides with the theme change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1845102/+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 1845103] [NEW] Video tearing in Celluloid with new Yaru theme
Public bug reported: Description:Ubuntu Eoan Ermine (development branch) Release:19.10 My specs: Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz Latest version of Celluloid (0.17) obtained by PPA: https://launchpad.net/~xuzhen666/+archive/ubuntu/gnome-mpv When I use the new Ubuntu 19.10 dev theme (all gray Yaru), video playback starts to tear in Celluloid (I wasn't able to capture it with SimpleScreenRecorder, sorry, the tearing does not appear in the capture). Really similar tearing occurs with Adwaita as the enabled theme. It however does NOT occur at all with the older Yaru theme (which I copied from my Ubuntu 19.04 install). There is no tearing with any of the themes enabled in Wayland. Tearing is scant and impossible to appreciate in VLC. These issues occur only in X, and in Celluloid. The reason I'm reporting this to you is because it coincides with the theme change. ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1845103 Title: Video tearing in Celluloid with new Yaru theme Status in yaru-theme package in Ubuntu: New Bug description: Description: Ubuntu Eoan Ermine (development branch) Release: 19.10 My specs: Advanced Micro Devices, Inc. [AMD/ATI] Caicos PRO [Radeon HD 7450] Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz Latest version of Celluloid (0.17) obtained by PPA: https://launchpad.net/~xuzhen666/+archive/ubuntu/gnome-mpv When I use the new Ubuntu 19.10 dev theme (all gray Yaru), video playback starts to tear in Celluloid (I wasn't able to capture it with SimpleScreenRecorder, sorry, the tearing does not appear in the capture). Really similar tearing occurs with Adwaita as the enabled theme. It however does NOT occur at all with the older Yaru theme (which I copied from my Ubuntu 19.04 install). There is no tearing with any of the themes enabled in Wayland. Tearing is scant and impossible to appreciate in VLC. These issues occur only in X, and in Celluloid. The reason I'm reporting this to you is because it coincides with the theme change. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1845103/+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 1065126]
*** Bug 1582927 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1065126 Title: "Always do this from now on" does not work Status in Mozilla Firefox: Confirmed Status in One Hundred Papercuts: New Status in firefox package in Ubuntu: Confirmed Bug description: Downloading an unknown file type in Firefox displays a dialog for choosing which application to use for opening the file. The dialog contains a check box labelled "Always do this action from now on". Checking this option does not work: When I download a file of the same type next time, the same dialog is displayed again. This feature is broken for as long as I can remember (> 10 years). It's time it was fixed (or removed). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: firefox 15.0.1+build1-0ubuntu0.12.04.1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic x86_64 NonfreeKernelModules: nvidia AddonCompatCheckDisabled: False AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu13 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ruediger 2536 F pulseaudio BuildID: 20120907231657 Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe22 irq 49' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20bb,00100400' Controls : 32 Simple ctrls : 20 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7KHT24WW-1.08' Mixer name : 'ThinkPad EC 7KHT24WW-1.08' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Channel: Unavailable Date: Wed Oct 10 18:17:44 2012 EcryptfsInUse: Yes ForcedLayersAccel: False IfupdownConfig: auto lo iface lo inet loopback InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) IpRoute: default via 172.31.0.1 dev wlan0 proto static 169.254.0.0/16 dev wlan0 scope link metric 1000 172.31.0.0/20 dev wlan0 proto kernel scope link src 172.31.9.26 metric 2 MostRecentCrashID: bp-7716491c-74b4-4213-bbf0-37b512110505 PrefSources: prefs.js Profiles: Profile0 (Default) - LastVersion=15.0.1/20120907231657 (In use) RelatedPackageVersions: rhythmbox-mozilla 2.96-0ubuntu4.2 totem-mozilla 3.0.1-0ubuntu21.1 icedtea-6-plugin 1.2-2ubuntu1.2 RunningIncompatibleAddons: False SourcePackage: firefox UpgradeStatus: Upgraded to precise on 2012-04-28 (165 days ago) dmi.bios.date: 03/18/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 7LETC9WW (2.29 ) dmi.board.name: 6457BBG dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7LETC9WW(2.29):bd03/18/2011:svnLENOVO:pn6457BBG:pvrThinkPadT61:rvnLENOVO:rn6457BBG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 6457BBG dmi.product.version: ThinkPad T61 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1065126/+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 1804568] Re: click position is flipped to cursor position when in tent mode
I don't think it's a Linux kernel bug. ** Package changed: linux (Ubuntu) => gnome-shell (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1804568 Title: click position is flipped to cursor position when in tent mode Status in gnome-shell package in Ubuntu: Confirmed Bug description: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1950 F pulseaudio /dev/snd/controlC1: imi1950 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.60 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1333 F pulseaudio /dev/snd/controlC1: imi1333 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP To manage notifications about this bug go to:
[Desktop-packages] [Bug 1804568] [NEW] click position is flipped to cursor position when in tent mode
You have been subscribed to a public bug: Hello, same bug is present 18.04 and 18.10: after I log in in tent mode the screen goes upside down, and after xrandr --output eDP-1 --rotate normal it goes back to normal however now the cursor is upside down, and click position and cursor position isnt the same, they are flipped thank you for the fix in advance ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: coreutils 8.28-1ubuntu2 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Nov 22 04:28:21 2018 ExecutablePath: /bin/sleep InstallationDate: Installed on 2018-11-22 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: LANG=hu_HU.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) SourcePackage: coreutils UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1950 F pulseaudio /dev/snd/controlC1: imi1950 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.04 InstallationDate: Installed on 2019-03-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190329) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-8-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 RelatedPackageVersions: linux-restricted-modules-5.0.0-8-generic N/A linux-backports-modules-5.0.0-8-generic N/A linux-firmware 1.178 Tags: disco Uname: Linux 5.0.0-8-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.31 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.60 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.31:bd04/27/2017:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.60:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: imi1333 F pulseaudio /dev/snd/controlC1: imi1333 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-23 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917) MachineType: HP HP Spectre x360 Convertible 13-w0XX Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 RelatedPackageVersions: linux-restricted-modules-5.3.0-10-generic N/A linux-backports-modules-5.3.0-10-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/03/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.49 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 827E dmi.board.vendor: HP dmi.board.version: 94.71 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.49:bd05/03/2019:svnHP:pnHPSpectrex360Convertible13-w0XX:pvr:rvnHP:rn827E:rvr94.71:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=SPT dmi.product.name: HP Spectre x360 Convertible 13-w0XX dmi.product.sku: Z9E46EA#ABV dmi.sys.vendor: HP ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug apport-collected cosmic disco eoan -- click position is flipped to cursor position when in tent mode https://bugs.launchpad.net/bugs/1804568 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1844575] Re: Pixelated fonts sometimes
agree that mutter#804 is the upstream issue -- 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/1844575 Title: Pixelated fonts sometimes Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: New Status in mutter package in Ubuntu: New Bug description: Running under wayland, with fractional scaling enabled and set to 175% on laptop screen, 100% on external screen, sometimes windows like nautilus or the file chooser get pixelated fonts (see screenshot). Seen this mostly on the 100% external screen, and it goes away if maximizing the window or moving the window back and forth between screens a few times. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Sep 18 12:59:50 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-08-17 (32 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) RelatedPackageVersions: mutter-common 3.34.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1844575/+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 1845076] [NEW] Gnome shell/Xorg freeze after remote connection with monitor unplugged
Public bug reported: I was trying to have a remote connection on a Ubuntu 18.04 pc with nomachine (but the behavior with Anydesk is the same) AFTER I unplugged the monitor form that pc. Once connected the output on the client freeze by just opening the Activities panel. If I plug the monitor back in on the server, the gnome shell is glitched and the only way to gain back control is by doing ALT F2 and then r. If I keep the monitor plugged in but turned off everything will work as it should. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 24 00:24:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP107 [GeForce GTX 1050 Ti] [19da:2454] InstallationDate: Installed on 2019-07-16 (69 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=dfa66545-9ac3-41fa-817b-433d8a61bd78 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) 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: x.x 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:rvrx.x: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.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic false-gpu-hang freeze ubuntu ** Summary changed: - Gnome shell freeze after remote connection with monitor unplugged + Gnome shell/Xorg freeze after remote connection with monitor unplugged -- 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/1845076 Title: Gnome shell/Xorg freeze after remote connection with monitor unplugged Status in xorg package in Ubuntu: New Bug description: I was trying to have a remote connection on a Ubuntu 18.04 pc with nomachine (but the behavior with Anydesk is the same) AFTER I unplugged the monitor form that pc. Once connected the output on the client freeze by just opening the Activities panel. If I plug the monitor back in on the server, the gnome shell is glitched and the only way to gain back control is by doing ALT F2 and then r. If I keep the monitor plugged in but turned off everything will work as it should. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Sep 24 00:24:03 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: I just need to know a workaround GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ZOTAC International (MCO) Ltd. GP107 [GeForce GTX 1050 Ti] [19da:2454] InstallationDate: Installed on 2019-07-16 (69 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: Gigabyte Technology Co., Ltd. GA-78LMT-USB3 6.0 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic root=UUID=dfa66545-9ac3-41fa-817b-433d8a61bd78 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg
[Desktop-packages] [Bug 1736176]
Please, make this option configurable, because as for now after so many years i can't use LibreOffice :( I have HP ZBook laptop and on Windows 10 I can not turn on ScrollLock. After research I managed to turn on ScrollLock using onscreen keyboard, and now I can move cell selection by arrow keys only up and down, but left and right arrows move a sheet itself, instead of cell selection. That's very pity and make the navigation to be very hard, I can't work in LO like this, sorry. LO 6.3.1.2 (64 bit), Windows 10 Pro, HP ZBook 15. -- 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/1736176 Title: Can't jump between cells when non-english input layout is active Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: Confirmed Bug description: Can't jump between LibreOffice Calc cells by arrow keys when non- english input layout is active. It's because Ubuntu is using Scroll Lock indicator (LED) to show state of layout switch, but in LibreOffice Scroll Lock state is used to switch between page's scrolling and jumping on cells. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 4 17:25:29 2017 InstallationDate: Installed on 2017-10-19 (45 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1736176/+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 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo
@Maxim Smih: Why did you subscribe all those teams and individuals? If you don't have a good reason (I doubt you have) it's bad manners. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, when I turn off the computer, it hangs on the logo. I can not turn off the computer using alt + SysRq + REISUO. The light on the system unit continues to light, and the fan runs. This is a problem with kernel 5.0, 5.3 Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq https://ibb.co/4JMGwvC sudo dmesg|grep ACPI|less - https://pastebin.com/PZxRGNyJ ProblemType: Bug DistroRelease: Ubuntu 18.04 Пакет: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Архитектура: amd64 CurrentDesktop: XFCE Дата: Четверг 5 09:44:35 2019 Дата установки: установлено в 2019-08 -09 (26 дней назад) InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 (20190210) ProcEnviron: LANGUAGE = ru_UA: ru PATH = (пользовательский, нет пользователя) XDG_RUNTIME_ DIR = LANG = ru_UA.UTF -8 SHELL = / bin / bash SourcePackage: gvfs UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) --- Тип проблемы: ошибка ApportVersion: 2.20.9-0ubuntu7.7 Архитектура: amd64 AudioDevicesInUse: КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID / dev / snd / controlC0: макс. 1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Установлен 2019-08-09 (37 дней назад) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 (20190210) IwConfig: enp0s25 без беспроводных расширений. enp7s4 нет беспроводных расширений. нет никаких беспроводных расширений. Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower Пакет: Linux (не установлен) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень = UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1 ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18 RelatedPackageV ersions: linux- restricted- modules- 4.15.0- 62-родовое N / A linux- backports- modules- 4.15.0 - 62-типовой N / A linux-прошивка 1.173.9 RfKill: Теги: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: нет журнала обновления (возможно, новая установка) Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 26.10.2015 dmi. bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board. asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis. asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: rn2820h: rvr: cvnHewlett- Packard: ct6: cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dvtwelet dv00 от компании HP : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842865/+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 1844132] Re: FFe: Mesa 19.2.0
1) yes, the upstream schedule slip has meant that .0 (which should be released tomorrow/the day after) is better than the usual .0 release 2) there will be a point release every two weeks, so the first one should arrive roughly around Oct 9th -- 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/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+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 1839716] Re: There is infinite loop in address bar
** Bug watch added: Red Hat Bugzilla #1740095 https://bugzilla.redhat.com/show_bug.cgi?id=1740095 -- 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/1839716 Title: There is infinite loop in address bar Status in chromium-browser package in Ubuntu: Invalid Status in chromium package in Fedora: Invalid Bug description: There seems to be infinite loop in the address bar if you fill it with letter f https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug then scrolling and page loading becomes faster. :)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716/+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 1844132] Re: FFe: Mesa 19.2.0
Just tested 19.2 RC4 from the ppa on a Radeon RX 570. Everything works fine, desktop and games (I've tested Witcher 3, CS:GO, HoN). -- 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/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+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 1839716]
two spaces https://bugzilla.redhat.com/show_bug.cgi?id=1740095#c31 -- 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/1839716 Title: There is infinite loop in address bar Status in chromium-browser package in Ubuntu: Invalid Status in chromium package in Fedora: Invalid Bug description: There seems to be infinite loop in the address bar if you fill it with letter f https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug then scrolling and page loading becomes faster. :)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716/+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 1839716]
*** This bug has been marked as a duplicate of bug 1754300 *** -- 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/1839716 Title: There is infinite loop in address bar Status in chromium-browser package in Ubuntu: Invalid Status in chromium package in Fedora: Invalid Bug description: There seems to be infinite loop in the address bar if you fill it with letter f https://bugs.launchpad.net/ubuntu/+source/nautilus/+filebug then scrolling and page loading becomes faster. :)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1839716/+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 1845046] [NEW] [WH-1000XM3, playback] Hearing input and output audio until disconnecting and reconnecting
Public bug reported: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1845046 Title: [WH-1000XM3, playback] Hearing input and output audio until disconnecting and reconnecting Status in pulseaudio package in Ubuntu: New Bug description: Whenever I turn on my headphones theyll connect to my computer but im able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: litleck1398 F pulseaudio /dev/snd/controlC0: litleck1398 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:07:59 2019 InstallationDate: Installed on 2019-09-22 (0 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: WH-1000XM3 Symptom_Type: High background noise, or volume is too low Title: [WH-1000XM3, playback] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2019 dmi.bios.vendor: Alienware dmi.bios.version: 1.0.19 dmi.board.name: 01NYPT dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 3 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.0.19:bd02/12/2019:svnAlienware:pnAlienwareAuroraR5:pvr1.0.19:rvnAlienware:rn01NYPT:rvrA00:cvnAlienware:ct3:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware Aurora R5 dmi.product.sku: 0729 dmi.product.version: 1.0.19 dmi.sys.vendor: Alienware To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845046/+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 684982]
Well, crowed too soon. 69.0 messed it all up again. Neither desktop not window position are remembered correctly across sessions. Sad, sad, sad. -- 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/684982 Title: Firefox windows don't restore on correct workspaces Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Confirmed Bug description: Binary package hint: firefox Create two workspaces Open one firefox window on the first workspace, second on the second one. Quit (or crash) firefox, specifying "Yes, remember my windows" Expected behavior: second window shows up on second workspace Actual behavior: Both windows appear on the current workspace To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/684982/+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 1813471]
We'll release TB 70 beta 2 early next week. -- 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/1813471 Title: Thunderbird crashes with GTK_USE_PORTAL environment variable. Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Triaged Bug description: Crash happens at startup, even for a new profile, as long as any e-mail accounts are configured. In profile creation mode, the crash happens as soon as an e-mail account is added. If all e-mail accounts are removed from prefs.js, then Thunderbird doesn't crash. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vectro 2619 F pulseaudio /dev/snd/controlC0: vectro 2619 F pulseaudio BuildID: 20190116085154 Channel: Unavailable CurrentDesktop: KDE Date: Sun Jan 27 06:55:37 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-23 (309 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) IpRoute: default via 172.20.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600 MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefSources: prefs.js Profile1Prefs: extensions.lastAppVersion: "60.4.0" (prefs.js) network.cookie.prefsMigrated: true (prefs.js) places.history.expiration.transient_current_max_pages: 104858 (prefs.js) Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=60.4.0/20190116085154 Profile1 - LastVersion=60.4.0/20190116085154 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L78 Ver. 01.43 dmi.board.name: 2101 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 640 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1813471/+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 1813471]
I am having this issue with the latest version 70.0b1 but I don't see any release for 70.0b2 so basically I cannot use thunderbird. I can confirm that using the nightly there are no problems. -- 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/1813471 Title: Thunderbird crashes with GTK_USE_PORTAL environment variable. Status in Mozilla Thunderbird: Fix Released Status in thunderbird package in Ubuntu: Triaged Bug description: Crash happens at startup, even for a new profile, as long as any e-mail accounts are configured. In profile creation mode, the crash happens as soon as an e-mail account is added. If all e-mail accounts are removed from prefs.js, then Thunderbird doesn't crash. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: thunderbird 1:60.4.0+build2-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: vectro 2619 F pulseaudio /dev/snd/controlC0: vectro 2619 F pulseaudio BuildID: 20190116085154 Channel: Unavailable CurrentDesktop: KDE Date: Sun Jan 27 06:55:37 2019 DefaultProfileExtensions: extensions.sqlite corrupt or missing DefaultProfileIncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) DefaultProfileLocales: extensions.sqlite corrupt or missing DefaultProfilePrefSources: prefs.js DefaultProfileThemes: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2018-03-23 (309 days ago) InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180306.1) IpRoute: default via 172.20.0.1 dev wlo1 proto dhcp metric 600 169.254.0.0/16 dev wlo1 scope link metric 1000 172.20.0.0/20 dev wlo1 proto kernel scope link src 172.20.2.18 metric 600 MostRecentCrashID: bp-d74e2e85-8327-42af-bce7-559720190127 Profile1Extensions: extensions.sqlite corrupt or missing Profile1IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) Profile1Locales: extensions.sqlite corrupt or missing Profile1PrefSources: prefs.js Profile1Prefs: extensions.lastAppVersion: "60.4.0" (prefs.js) network.cookie.prefsMigrated: true (prefs.js) places.history.expiration.transient_current_max_pages: 104858 (prefs.js) Profile1Themes: extensions.sqlite corrupt or missing Profiles: Profile0 (Default) - LastVersion=60.4.0/20190116085154 Profile1 - LastVersion=60.4.0/20190116085154 RunningIncompatibleAddons: False SourcePackage: thunderbird UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/25/2018 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L78 Ver. 01.43 dmi.board.name: 2101 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 16.3C dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO dmi.product.name: HP ProBook 640 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1813471/+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 1707884] Re: GTK3 tooltips are corrupted after latest update
Launchpad has imported 23 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=102013. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-08-02T10:08:47+00:00 Amr Ibrahim wrote: Created attachment 133192 GTK3 tooltips are corrupted After updating to Radeon 7.9.0 in Ubuntu 16.04.3, I noticed that all GTK3 tooltips are corrupted. See the attached screencast. Other tooltips are not affected. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/10 On 2017-08-02T10:14:58+00:00 Amr Ibrahim wrote: Created attachment 133193 Xorg log Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/11 On 2017-08-02T14:09:14+00:00 Michel Dänzer wrote: Does Option "AccelMethod" "EXA" in /etc/X11/xorg.conf avoid the problem? If not, please attach the corresponding Xorg log file. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/12 On 2017-08-02T15:26:42+00:00 Amr Ibrahim wrote: I don't have this file /etc/X11/xorg.conf. Please tell me what the content of it would be so I can create a new one. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/13 On 2017-08-02T22:13:50+00:00 Amr Ibrahim wrote: Michel, yes, adding that option fixes the tooltips problem. It also fixes another bug about artefacts when resizing windows. I attached a screencast. Downstream https://launchpad.net/bugs/1707893 Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/14 On 2017-08-02T22:16:44+00:00 Amr Ibrahim wrote: Created attachment 133215 Xorg log after Option "AccelMethod" "EXA" Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/15 On 2017-08-02T22:27:49+00:00 Amr Ibrahim wrote: Created attachment 133217 Resizing windows artefacts before Option "AccelMethod" "EXA" This screencast is before the Option "AccelMethod" "EXA". After applying the option, the artefacts are gone. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/16 On 2017-08-03T01:07:03+00:00 Michel Dänzer wrote: Please try Driver "modesetting" in xorg.conf and attach the corresponding Xorg log file. Does either of these problems happen in that case as well? Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/17 On 2017-08-03T08:27:25+00:00 Amr Ibrahim wrote: Adding Driver "modesetting" made the two problems disappear by making compiz (unity7) go into low graphics mode. Effects and animations are gone. Compiz was using 50% CPU. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/18 On 2017-08-03T08:28:44+00:00 Amr Ibrahim wrote: Created attachment 133224 Xorg log after Driver "modesetting" Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/19 On 2017-08-03T08:42:28+00:00 Amr Ibrahim wrote: The whole desktop is much slower after Driver "modesetting". Playing small videos in Totem is slow. Playing big videos crashes the session and brings me back to the login screen. Compiz and Totem together use 100% CPU for switching, moving windows and playing videos. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/20 On 2017-08-03T09:24:31+00:00 Michel Dänzer wrote: Ah, you also need to comment out Option "AccelMethod" for testing the modesetting driver. Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/21 On 2017-08-03T09:41:55+00:00 Amr Ibrahim wrote: Created attachment 133225 Xorg log after Driver "modesetting" and without Option "AccelMethod" Reply at: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1707884/comments/22 On 2017-08-03T09:43:02+00:00 Amr Ibrahim wrote: OK, the driver modesetting brings back the two problems.
[Desktop-packages] [Bug 1845041] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1751508 ***
https://bugs.launchpad.net/bugs/1751508
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1751508, so 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. Please continue to report any other bugs you may
find.
** Attachment removed: "CoreDump.gz"
https://bugs.launchpad.net/bugs/1845041/+attachment/5290752/+files/CoreDump.gz
** Attachment removed: "Disassembly.txt"
https://bugs.launchpad.net/bugs/1845041/+attachment/5290755/+files/Disassembly.txt
** Attachment removed: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/1845041/+attachment/5290764/+files/ProcMaps.txt
** Attachment removed: "ProcStatus.txt"
https://bugs.launchpad.net/bugs/1845041/+attachment/5290766/+files/ProcStatus.txt
** Attachment removed: "Registers.txt"
https://bugs.launchpad.net/bugs/1845041/+attachment/5290767/+files/Registers.txt
** Attachment removed: "Stacktrace.txt"
https://bugs.launchpad.net/bugs/1845041/+attachment/5290768/+files/Stacktrace.txt
** Attachment removed: "ThreadStacktrace.txt"
https://bugs.launchpad.net/bugs/1845041/+attachment/5290769/+files/ThreadStacktrace.txt
** This bug has been marked a duplicate of bug 1751508
Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("Couldn't add screen\n") from InitOutput()
** Information type changed from Private to Public
** Tags removed: need-amd64-retrace
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
https://bugs.launchpad.net/bugs/1845041
Title:
Xwayland crashed with SIGABRT in OsAbort()
Status in xorg-server package in Ubuntu:
New
Bug description:
Xwayland crashed
ProblemType: Crash
DistroRelease: Ubuntu 19.10
Package: xwayland 2:1.20.5+git20190820-0ubuntu3
ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0
Uname: Linux 5.3.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME-Greeter:GNOME
Date: Mon Sep 23 23:04:32 2019
DistUpgraded: 2019-09-20 01:36:18,618 DEBUG /openCache(), new cache size 95614
DistroCodename: eoan
DistroVariant: ubuntu
DkmsStatus: virtualbox, 6.0.12, 5.3.0-12-generic, x86_64: installed
ExecutablePath: /usr/bin/Xwayland
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA
controller])
Subsystem: Dell UHD Graphics 620 [1028:0810]
InstallationDate: Installed on 2013-12-27 (2095 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64
(20131016.1)
MachineType: Dell Inc. Inspiron 5570
ProcCmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth
/run/user/121/.mutter-Xwaylandauth.69QM8Z -listen 4 -listen 5 -displayfd 6
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=it_IT.UTF-8
SHELL=/bin/false
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-12-generic
root=UUID=392cca54-560c-4712-be6b-586150b9b6ad ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
OsAbort ()
?? ()
FatalError ()
InitOutput ()
?? ()
Title: Xwayland crashed with SIGABRT in OsAbort()
UpgradeStatus: Upgraded to eoan on 2019-09-19 (3 days ago)
UserGroups:
dmi.bios.date: 05/15/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.2.3
dmi.board.name: 0D65FD
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.2.3:bd05/15/2019:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0D65FD:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 5570
dmi.product.sku: 0810
dmi.sys.vendor: Dell Inc.
separator:
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
version.libdrm2: libdrm2 2.4.99-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.1.6-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20190815-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
To manage notifications about this bug go to:
[Desktop-packages] [Bug 1845040] Re: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject()
*** This bug is a duplicate of bug 1841794 *** https://bugs.launchpad.net/bugs/1841794 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1841794, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1845040/+attachment/5290738/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1845040/+attachment/5290740/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1845040/+attachment/5290744/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1845040/+attachment/5290745/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1845040/+attachment/5290746/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1845040/+attachment/5290748/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1845040/+attachment/5290749/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1841794 gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1845040 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() Status in gnome-shell package in Ubuntu: New Bug description: GNOME Shell crashed ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 17:12:47 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2013-12-27 (2095 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=it_IT.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::disassociate_js_gobject() () at /usr/lib/libgjs.so.0 ObjectInstance::remove_wrapped_gobjects_if(std::function const&, std::function const&) () at /usr/lib/libgjs.so.0 ObjectInstance::update_heap_wrapper_weak_pointers(JSContext*, JSCompartment*, void*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::disassociate_js_gobject() UpgradeStatus: Upgraded to eoan on 2019-09-19 (3 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845040/+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 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo
** Description changed: - When I turn off the computer, it hangs on the logo. The light on the - system unit continues to light. Does not respond to the keyboard. Kernel - version 5.0.0-27. Here is the error: + Sometimes, when I turn off the computer, it hangs on the logo. I can not + turn off the computer using alt + SysRq + REISUO. This is a problem with + kernel 5.0, 5.3 + Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message - https://ibb.co/PcYvDLq + https: / /ibb.co/ PcYvDLq + https://ibb.co/4JMGwvC - ProblemType: Bug - DistroRelease: Ubuntu 18.04 - Package: gvfs 1.36.1-0ubuntu1.3.3 - ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21 - Uname: Linux 5.0.0-27-generic x86_64 - ApportVersion: 2.20.9-0ubuntu7.7 - Architecture: amd64 - CurrentDesktop: XFCE - Date: Thu Sep 5 09:44:35 2019 - InstallationDate: Installed on 2019-08-09 (26 days ago) - InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) - ProcEnviron: - LANGUAGE=ru_UA:ru - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=ru_UA.UTF-8 - SHELL=/bin/bash + sudo dmesg|grep ACPI|less - https://pastebin.com/PZxRGNyJ + + + ProblemType: Bug + DistroRelease: Ubuntu 18.04 + Пакет: gvfs 1.36.1-0ubuntu1.3.3 + ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21 + Uname: Linux 5.0.0-27-generic x86_64 + ApportVersion: 2.20.9-0ubuntu7.7 + Архитектура: amd64 + CurrentDesktop: XFCE + Дата: Четверг 5 09:44:35 2019 Дата + установки: установлено в 2019-08 -09 (26 дней назад) + InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 (20190210) + ProcEnviron: + LANGUAGE = ru_UA: ru + PATH = (пользовательский, нет пользователя) + XDG_RUNTIME_ DIR = + LANG = ru_UA.UTF -8 + SHELL = / bin / bash SourcePackage: gvfs - UpgradeStatus: No upgrade log present (probably fresh install) + UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) --- - ProblemType: Bug - ApportVersion: 2.20.9-0ubuntu7.7 - Architecture: amd64 - AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: max1055 F pulseaudio - CurrentDesktop: XFCE - DistroRelease: Ubuntu 18.04 - InstallationDate: Installed on 2019-08-09 (37 days ago) - InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) - IwConfig: - enp0s25 no wireless extensions. - - enp7s4no wireless extensions. - - lono wireless extensions. - MachineType: Hewlett-Packard HP Compaq dc5800 Microtower - Package: linux (not installed) - ProcFB: 0 inteldrmfb - ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1 - ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18 - RelatedPackageVersions: - linux-restricted-modules-4.15.0-62-generic N/A - linux-backports-modules-4.15.0-62-generic N/A - linux-firmware 1.173.9 + Тип проблемы: ошибка + ApportVersion: 2.20.9-0ubuntu7.7 + Архитектура: amd64 + AudioDevicesInUse: + КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID + / dev / snd / controlC0: макс. 1055 F pulseaudio + CurrentDesktop: XFCE + DistroRelease: Ubuntu 18.04 + InstallationDate: Установлен 2019-08-09 (37 дней назад) + InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 (20190210) + IwConfig: + enp0s25 без беспроводных расширений. + + enp7s4 нет беспроводных расширений. + + нет никаких беспроводных расширений. + Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower + Пакет: Linux (не установлен) + ProcFB: 0 inteldrmfb + ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень = UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1 + ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18 + RelatedPackageV ersions: + linux- restricted- modules- 4.15.0- 62-родовое N / A + linux- backports- modules- 4.15.0 - 62-типовой N / A + linux-прошивка 1.173.9 RfKill: - - Tags: bionic - Uname: Linux 4.15.0-62-generic x86_64 - UpgradeStatus: No upgrade log present (probably fresh install) - UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo - _MarkForUpload: True - dmi.bios.date: 10/26/2015 - dmi.bios.vendor: Hewlett-Packard - dmi.bios.version: 786F2 v01.60 - dmi.board.asset.tag: CZC8107S1Y - dmi.board.name: 2820h - dmi.board.vendor: Hewlett-Packard - dmi.chassis.asset.tag: CZC8107S1Y - dmi.chassis.type: 6 - dmi.chassis.vendor: Hewlett-Packard - dmi.modalias: dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr: - dmi.product.family: 103C_53307F - dmi.product.name: HP Compaq dc5800 Microtower - dmi.sys.vendor: Hewlett-Packard + + Теги: bionic + Uname: Linux
[Desktop-packages] [Bug 1845031] [NEW] gnome not remembering numlock state in eoan
Public bug reported: in 3.34, gnome-settings-daemon has removed its handling of numlock state persistence, claiming that mutter should be handling that now (https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/710a4c4e7828828cb35ea14333882354ae73264f). However, numlock is always off when I start a session, and does not get remembered when I turn it on, log out, and log back in. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 23 11:15:27 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan 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/1845031 Title: gnome not remembering numlock state in eoan Status in mutter package in Ubuntu: New Bug description: in 3.34, gnome-settings-daemon has removed its handling of numlock state persistence, claiming that mutter should be handling that now (https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/710a4c4e7828828cb35ea14333882354ae73264f). However, numlock is always off when I start a session, and does not get remembered when I turn it on, log out, and log back in. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: mutter 3.34.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18 Uname: Linux 5.0.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Sep 23 11:15:27 2019 InstallationDate: Installed on 2019-08-17 (37 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) SourcePackage: mutter UpgradeStatus: Upgraded to eoan on 2019-09-18 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1845031/+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 1842865] Re: Xubuntu 18.04 sometimes freezes when turned on on logo
Kai-Heng Feng (kaihengfeng), with kernel 5.3 the same problem. I can not turn off the computer using alt+SysRq+R E I S O -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1842865 Title: Xubuntu 18.04 sometimes freezes when turned on on logo Status in linux package in Ubuntu: Confirmed Bug description: Sometimes, when I turn off the computer, it hangs on the logo. I can not turn off the computer using alt + SysRq + REISUO. The light on the system unit continues to light, and the fan runs. This is a problem with kernel 5.0, 5.3 Here is the error: info: task systemd shutdown:1 blocked for more than 120 seconds Not tainted 5.0.0-20-generic #21-Ubuntu «echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message https://ibb.co/PcYvDLq https://ibb.co/4JMGwvC sudo dmesg|grep ACPI|less - https://pastebin.com/PZxRGNyJ ProblemType: Bug DistroRelease: Ubuntu 18.04 Пакет: gvfs 1.36.1-0ubuntu1.3.3 ProcVersionSign ature: Ubuntu 5.0.0-27. 28 ~ 18,04. 1-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Архитектура: amd64 CurrentDesktop: XFCE Дата: Четверг 5 09:44:35 2019 Дата установки: установлено в 2019-08 -09 (26 дней назад) InstallationMedia: Xubuntu 18.04.2 LTS «Бионический бобр» - выпуск amd64 (20190210) ProcEnviron: LANGUAGE = ru_UA: ru PATH = (пользовательский, нет пользователя) XDG_RUNTIME_ DIR = LANG = ru_UA.UTF -8 SHELL = / bin / bash SourcePackage: gvfs UpgradeStatus: журнал обновления отсутствует (возможно, новая установка) --- Тип проблемы: ошибка ApportVersion: 2.20.9-0ubuntu7.7 Архитектура: amd64 AudioDevicesInUse: КОМАНДА ДОСТУПА ПОЛЬЗОВАТЕЛЯ PID / dev / snd / controlC0: макс. 1055 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 InstallationDate: Установлен 2019-08-09 (37 дней назад) InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Выпуск amd64 (20190210) IwConfig: enp0s25 без беспроводных расширений. enp7s4 нет беспроводных расширений. нет никаких беспроводных расширений. Тип машины: Hewlett-Packard HP Compaq dc5800 Microtower Пакет: Linux (не установлен) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE = / загрузки / vmlinuz- 4.15.0- 62-общий корень = UUID = 8c77fe78- d1d9-4452- aca0-eb1f844041 22 ро тихий всплеск vt.handoff = 1 ProcVersionSign ature: Ubuntu 4.15.0- 62,69-родовое 4.15.18 RelatedPackageV ersions: linux- restricted- modules- 4.15.0- 62-родовое N / A linux- backports- modules- 4.15.0 - 62-типовой N / A linux-прошивка 1.173.9 RfKill: Теги: bionic Uname: Linux 4.15.0-62-generic x86_64 UpgradeStatus: нет журнала обновления (возможно, новая установка) Группы пользователей: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 26.10.2015 dmi. bios.vendor: Hewlett-Packard dmi.bios.version: 786F2 v01.60 dmi.board. asset.tag: CZC8107S1Y dmi.board.name: 2820h dmi.board.vendor: Hewlett-Packard dmi.chassis. asset.tag: CZC8107S1Y dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi: bvnHewlett- Packard: bvr786F2v01. 60: bd10 / 26/2015: svnHewlett- Packard:pnHPCompaqdc580 0Microtower: pvr: rvnHewlett- Packard: rn2820h: rvr: cvnHewlett- Packard: ct6: cvr: dmi.product.family: 103C_53307F dmi.product.name: HP Compaq dvtwelet dv00 от компании HP : To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842865/+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 330833] Re: NetworkManager always overwrites default route when connecting to OpenVPN network
it's 2019 and the same bug still exists. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/330833 Title: NetworkManager always overwrites default route when connecting to OpenVPN network Status in NetworkManager-OpenVPN: Invalid Status in network-manager package in Ubuntu: Invalid Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager package in Debian: New Status in network-manager package in Fedora: Invalid Bug description: Binary package hint: network-manager My office VPN has IMAP, (forwarding) DNS services and not much else. It doesn't forward client traffic to the Internet. This means I can't use the VPN server as a default gateway. Every time I connect to the VPN using NetworkManager/OpenVPN, my routing table gets a default route to the VPN. I've tried everything to avoid this in both the Intrepid package and the version from the network manager PPA with no success. Even telling NetworkManager to ignore routes from the server doesn't work. As it is right now, I have to connect to the VPN, delete the default route, and re-add my wireless router as the default gateway before I can have both email and web access. See attached routing table details. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 8.10 NonfreeKernelModules: nvidia Package: network-manager 0.7-0ubuntu1~nm1~intrepid1 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_CA.UTF-8 SHELL=/bin/bash SourcePackage: network-manager Uname: Linux 2.6.27-11-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager-openvpn/+bug/330833/+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 1845000] Re: evince assert failure: double free or corruption (!prev)
** Changed in: evince Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1845000 Title: evince assert failure: double free or corruption (!prev) Status in Evince: New Status in evince package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/evince/issues/1259 --- I'm working with .pdf ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evince 3.32.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: double free or corruption (!prev) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 09:20:00 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (294 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evince assert failure: double free or corruption (!prev) UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1845000/+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 1845017] Re: Desktop hard lockup in 19.10
It's hard to reproduce. I've had it twice today though. Once when I was doing a "snap refresh" and one when using lxd. -- 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/1845017 Title: Desktop hard lockup in 19.10 Status in gnome-shell package in Ubuntu: New Bug description: Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris). Had a few desktop shell lockups. Pattern seems to be when running snap refresh, but this time happened when running snapcraft --use-lxd. Feels like something related to mounting / unmounting devices. Got this from the journal. Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: dock._settings is undefined _showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1 _enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 23 16:52:06 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (595 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+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 1845017] Re: Desktop hard lockup in 19.10
It's possible that this is related to the Mutter fix from last week which manifests itself via changes to the launcher. However, this should have been fixed on Friday. Can you add some steps to reproduce? ** Tags removed: rls-ee-incoming -- 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/1845017 Title: Desktop hard lockup in 19.10 Status in gnome-shell package in Ubuntu: New Bug description: Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris). Had a few desktop shell lockups. Pattern seems to be when running snap refresh, but this time happened when running snapcraft --use-lxd. Feels like something related to mounting / unmounting devices. Got this from the journal. Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: dock._settings is undefined _showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1 _enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 23 16:52:06 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (595 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+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 1845017] Re: Desktop hard lockup in 19.10
** Tags added: rls-ee-incoming -- 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/1845017 Title: Desktop hard lockup in 19.10 Status in gnome-shell package in Ubuntu: New Bug description: Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris). Had a few desktop shell lockups. Pattern seems to be when running snap refresh, but this time happened when running snapcraft --use-lxd. Feels like something related to mounting / unmounting devices. Got this from the journal. Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: dock._settings is undefined _showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1 _enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 23 16:52:06 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (595 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+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 1845017] [NEW] Desktop hard lockup in 19.10
Public bug reported: Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris). Had a few desktop shell lockups. Pattern seems to be when running snap refresh, but this time happened when running snapcraft --use-lxd. Feels like something related to mounting / unmounting devices. Got this from the journal. Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: dock._settings is undefined _showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1 _enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 23 16:52:06 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (595 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan rls-ee-incoming -- 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/1845017 Title: Desktop hard lockup in 19.10 Status in gnome-shell package in Ubuntu: New Bug description: Upgraded from 18.04 to 19.04 (then 19.10 last week in Paris). Had a few desktop shell lockups. Pattern seems to be when running snap refresh, but this time happened when running snapcraft --use-lxd. Feels like something related to mounting / unmounting devices. Got this from the journal. Sep 23 16:40:48 KinkPad-K450 gnome-shell[18382]: JS ERROR: TypeError: dock._settings is undefined _showOverlay@/usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com/docking.js:1438:1 _enableHotKeys/http://paste.ubuntu.com/p/txsGG5dTQw/ ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Mon Sep 23 16:52:06 2019 DisplayManager: gdm3 InstallationDate: Installed on 2018-02-04 (595 days ago) InstallationMedia: neon userlts "Xenial" - Build amd64 LIVE Binary 20180202-11:07 RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to eoan on 2019-09-19 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845017/+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 1844126] Re: Update NVIDIA the 430 series and introduce the 435 series
Please update nvidia-settings in Bionic as well, so that users can adjust settings of the new features in the 430 / 435 drivers. e.g. G-SYNC ** Also affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-430 in Ubuntu. https://bugs.launchpad.net/bugs/1844126 Title: Update NVIDIA the 430 series and introduce the 435 series Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-435 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: New Status in nvidia-graphics-drivers-430 source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-435 source package in Bionic: In Progress Status in nvidia-settings source package in Bionic: New Bug description: Update NVIDIA the 430 series and introduce the 435 series from 19.10. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 430.50: * New upstream release (LP: #1844126): - Fixed display color range handling on pre-Turing GPUs, such that when limited color range is selected through the display controls page in nvidia-settings, output pixel values will be correctly clamped to Consumer Technology Association (CTA) range. 435.21: * New upstream release: - Fixed a bug that caused the X server to crash when using HardDPMS with an NVIDIA-driven GPU Screen. - Fixed a bug which caused the kernel to panic when exiting a single X server when multiple X servers were active and in an SLI configuration. - Fixed a regression introduced in the 430.* series of releases that caused a segmentation fault in libnvcuvid.so while using Video Codec SDK APIs on certain graphics boards. - Added initial experimental support for runtime D3 (RTD3) power management on Turing notebook GPUs. - Improved nvidia-bug-report.sh to collect runtime D3 (RTD3) power management information. - Improved nvidia-bug-report.sh to collect ACPI tables when the acpidump tool is available. - Added Vulkan and OpenGL+GLX support for PRIME render offload. Please see the PRIME Render Offload chapter in the README for system requirements and configuration details. - Added support for changing Digital Vibrance in the display controls section of nvidia-settings on Turing hardware. - Fixed the cuvidParseVideoData API in the NVCUVID driver to correctly propagate errors returned by the PFNVIDSEQUENCECALLBACK callback function to the application. - Fixed a bug that caused the NVIDIA X driver to behave incorrectly or crash when a client queried Xinerama information on X servers with a non-NVIDIA X screen as screen 0. - Fixed the "Image Settings" options in the "OpenGL Settings" page of nvidia-settings for Quadro GPUs. Previously, OpenGL rendering on Quadro would behave as if the "High Quality" option were selected regardless of the selection. Now, the setting will default to "High Quality" for Quadro but selecting a lower option will affect rendering accordingly. (Other GPUs are unchanged: the default remains "Quality", but other options can be selected if desired.) - Fixed a bug that could cause Vulkan applications to generate spurious warning messages about a missing NV-GLX extension. - Fixed a bug that prevented nvidia-drm from marking preferred modes properly when reporting display information via the DRM- KMS API. - Fixed the NvEncodeAPI driver to correctly reject the encoding of sequences with resolutions smaller than what the NVENC supports. - Fixed display color range handling on pre-Turing GPUs, such that when limited color range is selected through the display controls page in nvidia-settings, output pixel values will be correctly clamped to Consumer Technology
[Desktop-packages] [Bug 1839846] Re: Please sync librsync 2 from Debian
It's in eoan now https://launchpad.net/ubuntu/+source/librsync ** Changed in: librsync (Ubuntu) Importance: Undecided => Low ** Changed in: librsync (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsync in Ubuntu. https://bugs.launchpad.net/bugs/1839846 Title: Please sync librsync 2 from Debian Status in librsync package in Ubuntu: Fix Released Bug description: Ubuntu has delta from Debian that was never upstreamed. Please drop the delta and sync librsync 2.0.2 from Debian so Ubuntu would not lag behind. See https://tracker.debian.org/pkg/librsync for details To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsync/+bug/1839846/+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 1845000] Re: evince assert failure: double free or corruption (!prev)
https://gitlab.gnome.org/GNOME/evince/issues/1259 ** Bug watch added: gitlab.gnome.org/GNOME/evince/issues #1259 https://gitlab.gnome.org/GNOME/evince/issues/1259 ** Also affects: evince via https://gitlab.gnome.org/GNOME/evince/issues/1259 Importance: Unknown Status: Unknown ** Description changed: + https://gitlab.gnome.org/GNOME/evince/issues/1259 + + --- + I'm working with .pdf ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evince 3.32.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: double free or corruption (!prev) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 09:20:00 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (294 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcEnviron: - SHELL=/bin/bash - XDG_RUNTIME_DIR= - PATH=(custom, no user) - LANGUAGE=es_CL:es - LANG=es_CL.UTF-8 + SHELL=/bin/bash + XDG_RUNTIME_DIR= + PATH=(custom, no user) + LANGUAGE=es_CL:es + LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: - __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 - malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 - _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 - g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 - () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 + __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 + malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 + _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 + g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 + () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evince assert failure: double free or corruption (!prev) UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1845000 Title: evince assert failure: double free or corruption (!prev) Status in Evince: Unknown Status in evince package in Ubuntu: New Bug description: https://gitlab.gnome.org/GNOME/evince/issues/1259 --- I'm working with .pdf ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evince 3.32.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: double free or corruption (!prev) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 09:20:00 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (294 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evince assert failure: double free or corruption (!prev) UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1845000/+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 1844132] Re: FFe: Mesa 19.2.0
1) Are you confident that you'll get enough testing to find any meaningful regressions, and have enough time to fix them before release? 2) Is there an upstream point release planned by October, or does their slip mean we'll see .1 as an SRU a month post-release? I'm a tentative +1 on this anyway just for the Ice Lake and Navi support, which we'll also want for the next bionic point release, but better answers to the above would help me be sure. -- 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/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+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 1845000] Re: evince assert failure: double free or corruption (!prev)
** Information type changed from Private to Public ** Attachment added: "valgrind.log" https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1845000/+attachment/5290711/+files/valgrind.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1845000 Title: evince assert failure: double free or corruption (!prev) Status in evince package in Ubuntu: New Bug description: I'm working with .pdf ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: evince 3.32.0-1ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-12.13-generic 5.3.0 Uname: Linux 5.3.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AssertionMessage: double free or corruption (!prev) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 09:20:00 2019 ExecutablePath: /usr/bin/evince InstallationDate: Installed on 2018-12-02 (294 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-5.3.0-12-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANGUAGE=es_CL:es LANG=es_CL.UTF-8 Signal: 6 SourcePackage: evince StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f16dd7e73a5 "%s\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0x7f16dd7e90c0 "double free or corruption (!prev)") at malloc.c:5332 _int_free (av=0x7f16dd818b80 , p=0x560e3a72c2c0, have_lock=) at malloc.c:4317 g_datalist_clear () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 Title: evince assert failure: double free or corruption (!prev) UpgradeStatus: Upgraded to eoan on 2018-12-02 (294 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1845000/+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 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1022.24 --- linux-oem-osp1 (5.0.0-1022.24) bionic; urgency=medium [ Ubuntu: 5.0.0-29.31 ] * powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction (CVE-2019-15030) (LP: #1843533) // CVE-2019-15031 - powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction - powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts * CVE-2019-14835 - vhost: fix dirty log buffer overflow * Packaging resync (LP: #1786013) - [Packaging] resync getabis -- Stefan Bader Thu, 12 Sep 2019 20:27:12 +0200 ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14835 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-15030 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-15031 ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Fix Released -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Fix Released Status in HWE Next: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Invalid Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
[Desktop-packages] [Bug 1714178] Re: Triple 4K monitor display failed (modesetting driver limited to 8192x8192)
This bug was fixed in the package linux-oem-osp1 - 5.0.0-1022.24 --- linux-oem-osp1 (5.0.0-1022.24) bionic; urgency=medium [ Ubuntu: 5.0.0-29.31 ] * powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts (CVE-2019-15031) / powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction (CVE-2019-15030) (LP: #1843533) // CVE-2019-15031 - powerpc/tm: Fix FP/VMX unavailable exceptions inside a transaction - powerpc/tm: Fix restoring FP/VMX facility incorrectly on interrupts * CVE-2019-14835 - vhost: fix dirty log buffer overflow * Packaging resync (LP: #1786013) - [Packaging] resync getabis -- Stefan Bader Thu, 12 Sep 2019 20:27:12 +0200 -- 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/1714178 Title: Triple 4K monitor display failed (modesetting driver limited to 8192x8192) Status in DRI: Fix Released Status in HWE Next: New Status in X.Org X server: Unknown Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in xorg-server package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: Fix Released Status in mesa source package in Bionic: Fix Released Status in xorg-server source package in Bionic: Invalid Bug description: Title: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Summary: Triple monitor display failed with Dell Dock (HiDPI) (modesetting) Steps: 1. a laptop with Built-in 4K LCD 2. Cold boot system with Dell Dock connected 3. Connect a 4K monitor to Dock 4. Connect 2nd 4K monitor to Dock 5. Go to [All Settings]=>[Displays] to have the following configuration. Resolution: 4kx2k@60Hz (one Built-in LCD + two external monitors) Mirror displays: disable Expected results: Triple monitor display should works without issues Actual results: Triple monitor display failed with Dell Dock Additional information: 1. Linux distribution: Ubuntu 16.04+modesetting, 16.04.3, and 17.04 2. Laptop: Dell Precision 5520 3. Dell Business Thunderbolt Dock - TB16 https://goo.gl/vFDjpi WORKAROUND (UBUNTU 18.04+): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: Fresh install DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-20160624-2 DistroCodename: xenial DistroRelease: Ubuntu 16.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591d] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07bf] Subsystem: Dell Device [1028:07bf] InstallationDate: Installed on 2017-08-29 (2 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20160624-10:47 MachineType: Dell Inc. Precision 5520 Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-14-generic.efi.signed root=UUID=b79ae801-0652-4785-beaf-e8387d798948 ro acpi_rev_override quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.11.0-14.20~16.04.1-generic 4.11.12 Tags: xenial ubuntu compiz-0.9 Uname: Linux 4.11.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd05/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.name: Precision 5520 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2
[Desktop-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade
** Bug watch added: Debian Bug tracker #941018 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941018 ** Also affects: ibus (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941018 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Fix Released Status in ibus package in Debian: Unknown Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+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 1844853] Re: IBus no longer works in Qt applications after upgrade
This bug was fixed in the package ibus - 1.5.19-1ubuntu2.2 --- ibus (1.5.19-1ubuntu2.2) disco-security; urgency=medium * SECURITY UPDATE: ibus regression in Qt applications (LP: #1844853) - debian/patches/CVE-2019-14822.patch: disabled pending further investigation. -- Marc Deslauriers Mon, 23 Sep 2019 13:29:28 +0200 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Fix Released Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+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 1844853] Re: IBus no longer works in Qt applications after upgrade
This bug was fixed in the package ibus - 1.5.11-1ubuntu2.3 --- ibus (1.5.11-1ubuntu2.3) xenial-security; urgency=medium * SECURITY UPDATE: ibus regression in Qt applications (LP: #1844853) - debian/patches/CVE-2019-14822.patch: disabled pending further investigation. -- Marc Deslauriers Mon, 23 Sep 2019 13:31:22 +0200 ** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-14822 ** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Fix Released Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+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 1844853] Re: IBus no longer works in Qt applications after upgrade
This bug was fixed in the package ibus - 1.5.17-3ubuntu5.2 --- ibus (1.5.17-3ubuntu5.2) bionic-security; urgency=medium * SECURITY UPDATE: ibus regression in Qt applications (LP: #1844853) - debian/patches/CVE-2019-14822.patch: disabled pending further investigation. -- Marc Deslauriers Mon, 23 Sep 2019 13:30:51 +0200 ** Changed in: ibus (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in ibus: New Status in ibus package in Ubuntu: Fix Released Bug description: Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ibus/+bug/1844853/+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 1845004] [NEW] Unable to set static route on eno1
Public bug reported: Install recent version of 19.10 daily build. All is well but can't set a static route for my wired ethernet. Going to Settings-Network-Wired tried to fill in IP Address/NetMask/Route and although all appears to be correct the Apply button is never activated to set the static environment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 08:43:48 2019 InstallationDate: Installed on 2019-09-20 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917) IpRoute: default via 192.168.1.1 dev wlp5s0 proto static metric 600 169.254.0.0/16 dev wlp5s0 scope link metric 1000 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.201 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.2 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1845004 Title: Unable to set static route on eno1 Status in network-manager package in Ubuntu: New Bug description: Install recent version of 19.10 daily build. All is well but can't set a static route for my wired ethernet. Going to Settings-Network- Wired tried to fill in IP Address/NetMask/Route and although all appears to be correct the Apply button is never activated to set the static environment. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: network-manager 1.20.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 08:43:48 2019 InstallationDate: Installed on 2019-09-20 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190917) IpRoute: default via 192.168.1.1 dev wlp5s0 proto static metric 600 169.254.0.0/16 dev wlp5s0 scope link metric 1000 192.168.1.0/24 dev wlp5s0 proto kernel scope link src 192.168.1.201 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.20.2 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1845004/+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 1845001] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1731261 *** https://bugs.launchpad.net/bugs/1731261 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1731261, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1845001/+attachment/5290674/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1845001/+attachment/5290677/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1845001/+attachment/5290685/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1845001/+attachment/5290687/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1845001/+attachment/5290688/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1845001/+attachment/5290689/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1845001/+attachment/5290690/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1731261 Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_log_handler(msg="Error sending request: Broken pipe\n...") ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1845001 Title: Xwayland crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: New Bug description: Booted the machine and left it standing for 10 mins. Opened GNOME Software and xwayland crashed. I am not in the wayland session though. Suspect this was a greeter crash? ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20190820-0ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Sep 23 13:36:36 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0613] InstallationDate: Installed on 2019-09-05 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830) MachineType: Dell Inc. Inspiron 3137 ProcCmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/123/.mutter-Xwaylandauth.0D5P8Z -listen 4 -listen 5 -displayfd 6 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=ff1caa1b-3c45-413d-9fa5-ba1772317cae ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0PRDX0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 3137 dmi.product.sku: 0613 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.0~rc4-1ubuntu1~ppa1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1845001/+subscriptions --
[Desktop-packages] [Bug 1845001] [NEW] Xwayland crashed with SIGABRT in OsAbort()
Public bug reported: Booted the machine and left it standing for 10 mins. Opened GNOME Software and xwayland crashed. I am not in the wayland session though. Suspect this was a greeter crash? ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20190820-0ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Sep 23 13:36:36 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0613] InstallationDate: Installed on 2019-09-05 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830) MachineType: Dell Inc. Inspiron 3137 ProcCmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/123/.mutter-Xwaylandauth.0D5P8Z -listen 4 -listen 5 -displayfd 6 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=ff1caa1b-3c45-413d-9fa5-ba1772317cae ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/25/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0PRDX0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd12/25/2013:svnDellInc.:pnInspiron3137:pvr:rvnDellInc.:rn0PRDX0:rvrA00:cvnDellInc.:ct8:cvr0.1: dmi.product.family: Shark Bay ULT dmi.product.name: Inspiron 3137 dmi.product.sku: 0613 dmi.sys.vendor: Dell Inc. separator: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.0~rc4-1ubuntu1~ppa1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash eoan need-amd64-retrace single-occurrence third-party-packages ubuntu ** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1845001 Title: Xwayland crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: New Bug description: Booted the machine and left it standing for 10 mins. Opened GNOME Software and xwayland crashed. I am not in the wayland session though. Suspect this was a greeter crash? ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: xwayland 2:1.20.5+git20190820-0ubuntu3 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CompositorRunning: None CurrentDesktop: GNOME-Greeter:GNOME Date: Mon Sep 23 13:36:36 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a06] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0613] InstallationDate: Installed on 2019-09-05 (18 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190830) MachineType: Dell Inc. Inspiron 3137 ProcCmdline: /usr/bin/Xwayland :1024 -rootless -noreset -accessx -core -auth /run/user/123/.mutter-Xwaylandauth.0D5P8Z -listen 4 -listen 5 -displayfd 6 ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/false ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-10-generic root=UUID=ff1caa1b-3c45-413d-9fa5-ba1772317cae ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () from /lib/x86_64-linux-gnu/libwayland-client.so.0 Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: No upgrade log present (probably
[Desktop-packages] [Bug 1841605] Re: freerdp2-x11 Remoteapp no response from application in Ubuntu 18.04
ADDITION: Hello everyone again, after testing out some stuff, i found out, that the problem lies with the ubuntu default window manager. I tried using freerdp (the nightly version) with some different window manager (e.g. IceWM) and its works fine with these. The only one, which doesn't work with all the different Window manager i tried, is the default one in ubuntu 18.04. But i want to open the remoteapp in the default ubuntu window manager, since i don#t want to work in a completly different enviroment. Maybe there is someone with a solution for this problem. Either a fix for running the remoteapp in the default window manager or open the remoteapp WITH another window manager, while still in the default one? Kind regards. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to freerdp2 in Ubuntu. https://bugs.launchpad.net/bugs/1841605 Title: freerdp2-x11 Remoteapp no response from application in Ubuntu 18.04 Status in freerdp2 package in Ubuntu: New Bug description: Hello, i installed the freerdp2-x11 package from the bionic sources (my current ubuntu is 18.04.3 LTS) and tried running a certain application called "Sfirm" on a Windows Server 2016 Essentials. At the beginning it loads normaly, but as soon as i get to the login window, after a few seconds, the window reloads and doesn't respond anymore (no response), so i can't login (can#t type anything in the prompts) and only close the window and with that the application. I also tried running the freerdp nightly version, but it doesn't work there as well in this ubuntu version. So i used virtual box to see, if it works on an older ubuntu version (ubuntu 16.04) and somehow it works without the application not responding as soon as i get to the login window! So something changed from 16.04 to 18.04, which causes this problem and i really need some help or fixes in this regard. Here the outputs from different commands: "lsb_release -rd" Description: Ubuntu 18.04.3 LTS Release: 18.04 "apt-cache policy freerdp2-x11" freerdp2-x11: Installiert: 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 Installationskandidat: 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 Versionstabelle: *** 2.0.0~git20170725.1.1648deb+dfsg1-7ubuntu0.1 500 500 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 100 /var/lib/dpkg/status 2.0.0~git20170725.1.1648deb+dfsg1-7 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages My command looks like this: "xfreerdp /app:"||SFirm" /u: /v: or with the rdp-file: "xfreerdp /u:" Output from "xfreerdp /buildconfig" from ubuntu 16.04 where it DOES work: This is FreeRDP version 2.0.0-dev5 (a298a3d8d) Build configuration: BUILD_TESTING=OFF BUILTIN_CHANNELS=ON HAVE_AIO_H=1 HAVE_EXECINFO_H=1 HAVE_FCNTL_H=1 HAVE_INTTYPES_H=1 HAVE_MATH_C99_LONG_DOUBLE=1 HAVE_POLL_H=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK=ON HAVE_PTHREAD_MUTEX_TIMEDLOCK_LIB=1 HAVE_PTHREAD_MUTEX_TIMEDLOCK_SYMBOL= HAVE_SYSLOG_H=1 HAVE_SYS_EVENTFD_H=1 HAVE_SYS_FILIO_H= HAVE_SYS_MODEM_H= HAVE_SYS_SELECT_H=1 HAVE_SYS_SOCKIO_H= HAVE_SYS_STRTIO_H= HAVE_SYS_TIMERFD_H=1 HAVE_TM_GMTOFF=1 HAVE_UNISTD_H=1 HAVE_XI_TOUCH_CLASS=1 WITH_ALSA=ON WITH_CAIRO=ON WITH_CCACHE=ON WITH_CHANNELS=ON WITH_CLANG_FORMAT=ON WITH_CLIENT=ON WITH_CLIENT_AVAILABLE=1 WITH_CLIENT_CHANNELS=ON WITH_CLIENT_CHANNELS_AVAILABLE=1 WITH_CLIENT_COMMON=ON WITH_CLIENT_INTERFACE=OFF WITH_CUPS=ON WITH_DEBUG_ALL=OFF WITH_DEBUG_CAPABILITIES=OFF WITH_DEBUG_CERTIFICATE=OFF WITH_DEBUG_CHANNELS=OFF WITH_DEBUG_CLIPRDR=OFF WITH_DEBUG_DVC=OFF WITH_DEBUG_KBD=OFF WITH_DEBUG_LICENSE=OFF WITH_DEBUG_MUTEX=OFF WITH_DEBUG_NEGO=OFF WITH_DEBUG_NLA=OFF WITH_DEBUG_NTLM=OFF WITH_DEBUG_RAIL=OFF WITH_DEBUG_RDP=OFF WITH_DEBUG_RDPDR=OFF WITH_DEBUG_RDPEI=OFF WITH_DEBUG_RDPGFX=OFF WITH_DEBUG_REDIR=OFF WITH_DEBUG_RFX=OFF WITH_DEBUG_RINGBUFFER=OFF WITH_DEBUG_SCARD=OFF WITH_DEBUG_SND=OFF WITH_DEBUG_SVC=OFF WITH_DEBUG_SYMBOLS=OFF WITH_DEBUG_THREADS=OFF WITH_DEBUG_TIMEZONE=OFF WITH_DEBUG_TRANSPORT=OFF WITH_DEBUG_TSG=OFF WITH_DEBUG_TSMF=OFF WITH_DEBUG_WND=OFF WITH_DEBUG_X11=OFF WITH_DEBUG_X11_CLIPRDR=OFF WITH_DEBUG_X11_LOCAL_MOVESIZE=OFF WITH_DEBUG_XV=OFF WITH_DSP_EXPERIMENTAL=OFF WITH_DSP_FFMPEG=OFF WITH_DSP_FFMPEG=OFF WITH_EVENTFD_READ_WRITE=1 WITH_FAAC=OFF WITH_FAAD2=OFF WITH_FFMPEG=TRUE WITH_FFMPEG=TRUE WITH_GFX_H264=ON WITH_GPROF=OFF WITH_GSM=OFF WITH_GSSAPI=OFF WITH_GSTREAMER_0_10=ON WITH_GSTREAMER_1_0=ON WITH_ICU=OFF WITH_IPP=OFF WITH_JPEG=OFF WITH_LAME=OFF WITH_LIBRARY_VERSIONING=ON WITH_LIBSYSTEMD=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO=OFF WITH_MACAUDIO_AVAILABLE=0 WITH_MANPAGES=ON WITH_MBEDTLS=OFF WITH_OPENH264=OFF WITH_OPENSLES=OFF WITH_OPENSSL=ON WITH_OSS=ON WITH_PAM=ON WITH_PCSC=ON WITH_PROFILER=OFF WITH_PULSE=ON
[Desktop-packages] [Bug 1844815] Re: appindicators for startup applications missing from top bar upon login
>Also affects 18.04 Strange, I never saw it on 19.04. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1844815 Title: appindicators for startup applications missing from top bar upon login Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have two startup applications configured, flameshot and yubioath- desktop. After upgrading this morning from 19.04 to 19.10, these two applications are being started when I log in, but their appindicator icons are not showing up in the top bar. Restarting gnome-shell with Alt-F2 r does not help. To make the icons show up I have to kill and restart the two applications. This is a regression from 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 11:33:31 2019 InstallationDate: Installed on 2019-09-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1844815/+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 1844815] Re: appindicators for startup applications missing from top bar upon login
Also affects 18.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1844815 Title: appindicators for startup applications missing from top bar upon login Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have two startup applications configured, flameshot and yubioath- desktop. After upgrading this morning from 19.04 to 19.10, these two applications are being started when I log in, but their appindicator icons are not showing up in the top bar. Restarting gnome-shell with Alt-F2 r does not help. To make the icons show up I have to kill and restart the two applications. This is a regression from 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 11:33:31 2019 InstallationDate: Installed on 2019-09-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1844815/+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 1844815] Re: appindicators for startup applications missing from top bar upon login
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-appindicator (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-appindicator in Ubuntu. https://bugs.launchpad.net/bugs/1844815 Title: appindicators for startup applications missing from top bar upon login Status in gnome-shell-extension-appindicator package in Ubuntu: Confirmed Bug description: I have two startup applications configured, flameshot and yubioath- desktop. After upgrading this morning from 19.04 to 19.10, these two applications are being started when I log in, but their appindicator icons are not showing up in the top bar. Restarting gnome-shell with Alt-F2 r does not help. To make the icons show up I have to kill and restart the two applications. This is a regression from 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell-extension-appindicator 30-1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 20 11:33:31 2019 InstallationDate: Installed on 2019-09-12 (7 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) PackageArchitecture: all SourcePackage: gnome-shell-extension-appindicator UpgradeStatus: Upgraded to eoan on 2019-09-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1844815/+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 1844643] Re: [UIFe] Change default theme to Yaru Ambience variant
This bug was fixed in the package yaru-theme - 19.10.3 --- yaru-theme (19.10.3) eoan; urgency=medium [ Didier Roche ] * Only install light, default, dark with symlinks. (LP: #1844643) * Fix debian/copyright CC-By-SA missing copyright content. [ Feichtmeier ] * Fix selection mode's titlebuttons * Organize _tweaks.scss * Use ubuntu-colors in colors sass * Use transparent active color for dock apps * Basic unity support * Fix window border, add comments * Update README.md * Revert "Ubuntu dock permanent transparency" [ Carlo Lobrano ] * Revert "Terminal additions" [ ubuntujaggers ] * fixing battery icons which have an incorrect xml class on the fill (LP: #1844137) -- Carlo Lobrano Fri, 20 Sep 2019 22:11:00 +0100 ** Changed in: yaru-theme (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1844643 Title: [UIFe] Change default theme to Yaru Ambience variant Status in yaru-theme package in Ubuntu: Fix Released Bug description: We've made a decision to ship the new Yaru themes light and dark as options in EE, not as the default. The default will actually be "Yaru Ambience" which is a very similar visual style to the traditional dark window header bars as in Disco. This will preserve the traditional look of the Ubuntu desktop for 19.10. There is a minor bug in Yaru Ambience which is being worked on right now (limited to GNOME Boxes and Videos) but I am filing this bug now in order to try and land the new changes as soon as that bug is fixed. The upshot of this change is that screenshots made since UI freeze could now look wrong when using the default theme. However, screenshots from previous Ubuntu releases will look more similar to 19.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1844643/+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 1844137] Re: Battery icon in top bar looks "red" when battery is not low
This bug was fixed in the package yaru-theme - 19.10.3 --- yaru-theme (19.10.3) eoan; urgency=medium [ Didier Roche ] * Only install light, default, dark with symlinks. (LP: #1844643) * Fix debian/copyright CC-By-SA missing copyright content. [ Feichtmeier ] * Fix selection mode's titlebuttons * Organize _tweaks.scss * Use ubuntu-colors in colors sass * Use transparent active color for dock apps * Basic unity support * Fix window border, add comments * Update README.md * Revert "Ubuntu dock permanent transparency" [ Carlo Lobrano ] * Revert "Terminal additions" [ ubuntujaggers ] * fixing battery icons which have an incorrect xml class on the fill (LP: #1844137) -- Carlo Lobrano Fri, 20 Sep 2019 22:11:00 +0100 ** Changed in: yaru-theme (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1844137 Title: Battery icon in top bar looks "red" when battery is not low Status in Yaru Theme: Fix Released Status in yaru-theme package in Ubuntu: Fix Released Status in yaru-theme source package in Eoan: Fix Released Bug description: In Ubuntu 19.10 the battery icon in the top bar looks red (actually it's orange rgb(245,121,62)) even when the battery is full, e.g. 99%. The orange colour makes it look like a warning that the battery is low. Logged upstream: https://github.com/ubuntu/yaru/issues/1531 To manage notifications about this bug go to: https://bugs.launchpad.net/yaru/+bug/1844137/+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 1844992] [NEW] Update to 1.18.0 not this cycle
Public bug reported: The new version has new features and it's late for this cycle ** Affects: v4l-utils (Ubuntu) Importance: Wishlist Status: New ** Tags: upgrade-software-version version-blocked-ff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to v4l-utils in Ubuntu. https://bugs.launchpad.net/bugs/1844992 Title: Update to 1.18.0 not this cycle Status in v4l-utils package in Ubuntu: New Bug description: The new version has new features and it's late for this cycle To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/v4l-utils/+bug/1844992/+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 1842643] Re: [ffe] Update to 1.44.6
We failed to have consensus in Paris and I feel like it's getting late now and we have enough other work to do to wrap the cycle so would prefer to delay to next cycle now. Iain, what do you think? (you opened the FFe but so you should be the one deciding if we withdraw the request) ** Changed in: pango1.0 (Ubuntu) Importance: Undecided => Wishlist ** Changed in: pango1.0 (Ubuntu) Status: New => Triaged ** Tags added: version-blocked-ff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pango1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1842643 Title: [ffe] Update to 1.44.6 Status in pango1.0 package in Ubuntu: Triaged Bug description: There are a lot of changes in pango1.0 since the version we currently have in eoan. We held off updating because there was a test failure. This has been resolved in the latest release, so we'd like to go for the update now. Overview of changes in 1.44.6 = - docs: Fix symbol indices - Fix Thai line breaking - Re-add symbols needed by some bindings - Don't insert hyphens for some languages - Fix a crash with hyphenation Overview of changes in 1.44.5 = - Revert a broken change (causing crashes on OS X) Overview of changes in 1.44.4 = - Add an insert-hyphens attribute - Reinstate the return type of pango_fc_font_lock_face - Fix a problem with ellipses getting the wrong font - fc: Improve filtering by font format - Re-add PangoFcFont to public headers - Install PangoFc and PangoOT introspection files - Fix ink rectangles to have positive height - Fix mark positioning - Switch to using harfbuzz for metrics Overview of changes in 1.44.3 = - Install pango-ot headers - Make subpixel positioning optional - fc: Ignore fonts with unsupported formats Overview of changes in 1.44.2 = - Disable ligatures when letterspacing - Set design coords on hb_font_t - Expose more font options in pango-view - OS X: Make 'system-ui' font work - Keep deprecated pango-fc apis in headers - Make hex boxes work, always - introspection: Various build fixes - introspection: Add PangoPT, PangoFT2 namespaces - layout: Make the new line-spacing opt-in Overview of changes in 1.44.1 = - Fix a crash with allow_break attributes - Fix Emoji spacing - Fix up includes and pkg-config requires - Correct some cases for hyphen insertion Overview of changes in 1.44.0 = - Use harfbuzz for shaping on all platforms - Stop using freetype for font loading; this drops support for type1 and bitmap fonts - Add a getter for hb_font_t - Make PangoCoverage a GObject - Add a pango_tailor_break api - font metrics: Add line height - layout: Support line spacing - layout: Draw hyphens for line breaks - Add an attribute to suppress line breaking - cairo: Don't render hex boxes for space - Add an attribute to show invisible characters - Stop quantizing glyph positions - Add tests for itemization and line breaking - Remove language and shape engine remnants - Rename meson options: gtk_doc, introspection - Require GLib 2.59.2 - Require Harfbuzz 2.0 Overview of changes in 1.43.0 = - Drop autotools - Drop Visual Studio build - Build with meson everywhere - Update Emoji tables for Unicode 11 - Update test data for Unicode 11 - Fix a crash with Thai breaking - Fix a crash with font variations - Deprecate bidi apis in favor of fribidi - Add a variable font family api - Improve font fallback handling on win32 And see posts from upstream https://blogs.gnome.org/mclasen/2019/07/19/pango-updates/ https://blogs.gnome.org/mclasen/2019/07/27/more-text-rendering-updates/ https://blogs.gnome.org/mclasen/2019/08/07/pango-1-44-wrap-up/ for the new features. We'd like to update to it, if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1842643/+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 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa
This bug was fixed in the package mesa - 19.0.8-0ubuntu0~18.04.2 --- mesa (19.0.8-0ubuntu0~18.04.2) bionic; urgency=medium * i965-revert-enabling-softpin.diff: Dropped, unnecessary by now and broke Ice Lake which needs softpin. (LP: #1815172) * rules: Force -DNDEBUG, meson < 0.47 is buggy and doesn't set it even if we have b_ndebug=true. (LP: #1841412) -- Timo Aaltonen Tue, 27 Aug 2019 09:42:44 +0300 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1815172 Title: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa Status in Mesa: Fix Released Status in linux package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Released Status in linux source package in Cosmic: Won't Fix Status in mesa source package in Cosmic: Fix Released Bug description: [Impact] Several schools reported black screens after normally updating their Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1. Downgrading mesa fixes the problem. lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:8694]Kernel modules: i915 Unfortunately I can't find a lot of useful information, here are some bits: * systemctl --failed says "gpu-manager" and "lightdm" have failed * Xorg.log is clean: https://termbin.com/6l2b * dmesg too: https://termbin.com/ip4e * It happens on lightdm/MATE, I don't know about Ubuntu GNOME. * If one runs `xinit` from ssh, it fails with: i965: Failed to submit batchbuffer: Invalid argument This is caused by mesa assuming that soft-pinning on GEN8+ is working since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT sizes/pin flags, but that's left for future. [Test case] install fixed mesa or kernel, check that the regression is fixed [Regression potential] mesa: shouldn't be any, it just reverts the change to always soft-pin (TODO kernel: adds commits from upstream stable, which have been well tested upstream by now) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1815172/+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 1841412] Re: Build with NDEBUG again
This bug was fixed in the package mesa - 19.0.8-0ubuntu0~18.04.2 --- mesa (19.0.8-0ubuntu0~18.04.2) bionic; urgency=medium * i965-revert-enabling-softpin.diff: Dropped, unnecessary by now and broke Ice Lake which needs softpin. (LP: #1815172) * rules: Force -DNDEBUG, meson < 0.47 is buggy and doesn't set it even if we have b_ndebug=true. (LP: #1841412) -- Timo Aaltonen Tue, 27 Aug 2019 09:42:44 +0300 ** Changed in: mesa (Ubuntu Bionic) Status: Fix Committed => Fix Released -- 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/1841412 Title: Build with NDEBUG again Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Released Bug description: [Impact] Mesa is now built with meson, and it turns out that meson < 0.47.0 (commit 7c4736d27f4c5d7 to be exact) doesn't handle command line options properly which means that -Db_ndebug=true didn't have any effect when mesa is built on bionic. This means that some asserts are enabled, and at least nouveau is affected. [Test case] chech the build log that -DNDEBUG is passed [Regression potential] none really, it just adds a build flag which should've been there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1841412/+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 1841412] Update Released
The verification of the Stable Release Update for mesa has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1841412 Title: Build with NDEBUG again Status in mesa package in Ubuntu: Invalid Status in mesa source package in Bionic: Fix Released Bug description: [Impact] Mesa is now built with meson, and it turns out that meson < 0.47.0 (commit 7c4736d27f4c5d7 to be exact) doesn't handle command line options properly which means that -Db_ndebug=true didn't have any effect when mesa is built on bionic. This means that some asserts are enabled, and at least nouveau is affected. [Test case] chech the build log that -DNDEBUG is passed [Regression potential] none really, it just adds a build flag which should've been there To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1841412/+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 1844977] [NEW] uses too much cpu in case of inactivity
Public bug reported: open any page after few minute fan make noise and between 15 -30% cpu used by chromium browser ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 76.0.3809.100-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-LVDS-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAw5NgCAAAWAQOAHBB46ohVmVtVjyYdUFQBAQEBAQEBAQEBAQEBAQEBYB1W2FAAGDAwQEcAFZwQAAAb/gBMRyBEaXNwbGF5CiAg/gBMUDEyNVdIMi1TTEIzAFk= modes: 1366x768 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAmzQ5hHgkAACEXAQNoNB14KirFpFZPnigPUFS/7wDRwIGAlQCzAIFAcU+VDwEBAjqAGHE4LUBYLEUACSUhAAAe/QA3TBhTEQAKICAgICAg/wAxMTE4N1YzODAyMzM0/ABQTDI0ODFICiAgICAgAIk= modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 800x600 800x600 640x480 640x480 640x480 640x480 720x400 Date: Mon Sep 23 10:29:16 2019 Desktop-Session: 'ubuntu' '/etc/xdg/xdg-ubuntu:/etc/xdg' '/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2018-10-24 (333 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Load-Avg-1min: 1.01 Load-Processes-Running-Percent: 0.1% MachineType: LENOVO 23259S9 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-64-generic root=UUID=68f6aa88-4dcb-4bb8-ab84-312e7bd2b5ba ro quiet splash vt.handoff=1 SourcePackage: chromium-browser UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/20/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET90WW (2.50 ) dmi.board.asset.tag: Not Available dmi.board.name: 23259S9 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET90WW(2.50):bd12/20/2012:svnLENOVO:pn23259S9:pvrThinkPadX230:rvnLENOVO:rn23259S9:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad X230 dmi.product.name: 23259S9 dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO modified.conffile..etc.default.chromium-browser: [deleted] ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- 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/1844977 Title: uses too much cpu in case of inactivity Status in chromium-browser package in Ubuntu: New Bug description: open any page after few minute fan make noise and between 15 -30% cpu used by chromium browser ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: chromium-browser 76.0.3809.100-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DRM.card0-DP-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-DP-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-1: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-2: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-HDMI-A-3: enabled: disabled dpms: Off status: disconnected edid-base64: modes: DRM.card0-LVDS-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAw5NgCAAAWAQOAHBB46ohVmVtVjyYdUFQBAQEBAQEBAQEBAQEBAQEBYB1W2FAAGDAwQEcAFZwQAAAb/gBMRyBEaXNwbGF5CiAg/gBMUDEyNVdIMi1TTEIzAFk= modes: 1366x768 DRM.card0-VGA-1: enabled: enabled dpms: On status: connected edid-base64: AP///wAmzQ5hHgkAACEXAQNoNB14KirFpFZPnigPUFS/7wDRwIGAlQCzAIFAcU+VDwEBAjqAGHE4LUBYLEUACSUhAAAe/QA3TBhTEQAKICAgICAg/wAxMTE4N1YzODAyMzM0/ABQTDI0ODFICiAgICAgAIk=
[Desktop-packages] [Bug 1844132] Re: FFe: Mesa 19.2.0
** Description changed: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: + Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) -- 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/1844132 Title: FFe: Mesa 19.2.0 Status in mesa package in Ubuntu: Confirmed Status in mesa source package in Eoan: Confirmed Bug description: It would be great to get 19.2.0 in eoan, though it's release cycle has slipped. It's working fine on a typical desktop use here on i915 (Kaby Lake). It would also migrate to llvm-9. It is currently at rc3, and final version is expected to arrive next week (week 39). New features: Full support for Intel Ice Lake Support for AMD Navi GL_ARB_post_depth_coverage on radeonsi (Navi) GL_ARB_seamless_cubemap_per_texture on etnaviv (if GPU supports SEAMLESS_CUBE_MAP) GL_EXT_shader_image_load_store on radeonsi (with LLVM >= 10) GL_EXT_shader_samples_identical on iris and radeonsi (if using NIR) GL_EXT_texture_shadow_lod on i965, iris EGL_EXT_platform_device VK_AMD_buffer_marker on radv VK_EXT_index_type_uint8 on radv VK_EXT_post_depth_coverage on radv VK_EXT_queue_family_foreign on radv VK_EXT_sample_locations on radv VK_EXT_shader_demote_to_helper_invocation on Intel. VK_KHR_depth_stencil_resolve on radv VK_KHR_imageless_framebuffer on radv VK_KHR_shader_atomic_int64 on radv VK_KHR_uniform_buffer_standard_layout on radv (note: iris is the new DRI driver for newer Intel, not enabled by default yet) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1844132/+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 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
** Package changed: ubuntu => network-manager (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1844763 Title: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso Status in network-manager package in Ubuntu: Confirmed Bug description: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+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 1841794] Re: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed ob
** Tags added: bugpattern-needed -- 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/1841794 Title: gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] Status in GNOME Shell: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Eoan: Fix Released Bug description: https://errors.ubuntu.com/problem/10051642bda6e2a9a27fe0b0d5f84f8b1f29438f ubuntu-bug crash report for bug reported in LP: #1841680 On Eoan, gnome-shell (3.33.91-1ubuntu1) crashes and restarts when opening up applications from the dock. ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.33.91-1ubuntu1 ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8 Uname: Linux 5.2.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 27 10:42:41 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-02-19 (554 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to eoan on 2019-08-27 (0 days ago) UserGroups: adm cdrom dip docker kvm libvirt lpadmin lxd plugdev sambashare sbuild sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1841794/+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 1844973] Re: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance()
*** This bug is a duplicate of bug 1841794 *** https://bugs.launchpad.net/bugs/1841794 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1841794, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1844973/+attachment/5290592/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1844973/+attachment/5290594/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1844973/+attachment/5290599/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1844973/+attachment/5290600/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1844973/+attachment/5290601/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1844973/+attachment/5290603/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1844973/+attachment/5290604/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1841794 gnome-shell crashed with SIGTRAP in g_log_default_handler() ... from ObjectInstance::~ObjectInstance() [usually logging "Finalizing wrapper for an already freed object of type: Clutter.PropertyTransition"] ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1844973 Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance() Status in gnome-shell package in Ubuntu: New Bug description: gnome shell crash periodically closing almost all applications. (terminator terminator(1.91-4 )tipically survive) ProblemType: Crash DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Mon Sep 23 09:05:04 2019 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2018-03-05 (566 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180305) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 3.34.0-3ubuntu1 Signal: 5 SourcePackage: gnome-shell StacktraceTop: ObjectInstance::~ObjectInstance() () at /usr/lib/libgjs.so.0 GIWrapperBase::finalize(JSFreeOp*, JSObject*) () at /usr/lib/libgjs.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 () at /usr/lib/x86_64-linux-gnu/libmozjs-60.so.0 Title: gnome-shell crashed with signal 5 in ObjectInstance::~ObjectInstance() UpgradeStatus: Upgraded to eoan on 2019-09-01 (21 days ago) UserGroups: adm cdrom dip jenkins lpadmin plugdev sambashare sudo tomcat wildfly wireshark separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844973/+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 1844763] [NEW] file /etc/network/interfaces is missing in eoan-desktop-amd64.iso
You have been subscribed to a public bug: The file /etc/network/interfaces is missing after install guestOS with eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi. This issue cause a failure for VMware Guest OS Customization ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: bot-comment -- file /etc/network/interfaces is missing in eoan-desktop-amd64.iso https://bugs.launchpad.net/bugs/1844763 You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager 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 1840699] Re: Caps-lock doesn't work correctly in Old Hungarian layout
Thank you Gunnar Hjalmarsson! I tested this package on bionic, and it works. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1840699 Title: Caps-lock doesn't work correctly in Old Hungarian layout Status in xkeyboard-config: Fix Released Status in xkeyboard-config package in Ubuntu: Fix Released Bug description: Xkeyboard-config's version 2.27 resolves this problem To manage notifications about this bug go to: https://bugs.launchpad.net/xkeyboard-config/+bug/1840699/+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 1800794] Re: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE
Currently I doesn't have access to hardware. I will try to check /run/usb_modeswitch/current_cfg content with latest build from PPA this Friday, or next week. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to usb-modeswitch in Ubuntu. https://bugs.launchpad.net/bugs/1800794 Title: usb-modeswitch can't apply Configuration=0 to Snapdragon X12 LTE Status in usb-modeswitch package in Ubuntu: In Progress Bug description: Please refer to post of usb-modeswitch developer http://www.draisberghof.de/usb_modeswitch/bb/viewtopic.php?f=4=2827 for complete issue description. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-modeswitch/+bug/1800794/+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 1350527] Re: Custom keyboard shortcuts using Esc key do not work
Ubuntu 18.04 - Can use Escape for shortcuts! Using ctrl-shift-esc to open system monitor so I have the same(ish) command across my dual-boot. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1350527 Title: Custom keyboard shortcuts using Esc key do not work Status in gnome-settings-daemon package in Ubuntu: Confirmed Bug description: I have just upgraded to 14.04 and found an issue with custom keyboard shortcuts. In 12.04 I used to have Shift + Ctrl + Esc as a custom shortcut to suspend my machine, upon upgrading I have found that any combination use Esc key will not run the command. It appears to be a regression from 13.10 as another user is reporting the same issue in askubuntu: http://askubuntu.com/q/489418/8570 Using any alternative such as Shift + Ctrl + F1 works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1350527/+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
