[Desktop-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd
** Description changed: [Impact] lrmd daemon with upstart resource has memory leak in Trusty affected to pacemaker 1.1.10. - affected to glib2.0 2.40.2-0ubuntu1 + affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [3] Please note that patch for pacemaker is created myself. [Test Case] - 1. deploy 3 trusty instance. - 2. install corosync, pacemaker, mysql. - 3. setting with below info - 3.1 corosync.conf, proper setting for 3 node - 3.2 crm configure < setup.crm ( which has upstart:mysql setting ) - 3.3 monitor lrmd daemon's memory usage + https://pastebin.ubuntu.com/p/fqK6Cx3SKK/ + you can check memory leak with this script [Regression] - Restarting daemon after upgrading this pkg will be needed. this patch added NULL check for several parts. prior commit[1] changed file structure. and This change makes user changes usage of upstart:mysql to lsb:mysql. So I added free function myself. This might affect to system. - For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building it. + Restarting daemon after upgrading this pkg will be needed. this patch adds free for non-freed dynamic allocated memory. so it solves memory leak. [Others] - Related commits. + this patch is from my self with testing. - [1] commit a7b61e276120184c7586a3217ed3571a982f5017 - Author: Andrew Beekhof- Date: Fri Aug 23 16:25:35 2013 +1000 - - Refactor: attrd: Move to its own directory and create a stub for - attrd-ng - - -- - $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0 - Pacemaker-1.1.11-rc3 - - $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017 - Pacemaker-1.1.11-rc1~168 - - $ rmadison pacemaker - pacemaker | 1.1.10+git20130802-1ubuntu2 | trusty - pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security - pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates - - pacemaker | 1.1.14-2ubuntu1 | xenial - pacemaker | 1.1.14-2ubuntu1.3 | xenial-security - pacemaker | 1.1.14-2ubuntu1.3 | xenial-update - pacemaker | 1.1.16-1ubuntu1 | zesty - pacemaker | 1.1.16-1ubuntu1 | artful - pacemaker | 1.1.18~rc3-1ubuntu1 | bionic - -- - - For glib - [1] https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c - [2] https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663 - [3] https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4 - [4] https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a + Please review carefully if it is ok. [Original Description] I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy (13.10) and have encountered a memory leak in lrmd. The details of the bug are covered here in this thread (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html) but to summarise, the Pacemaker developers believe the leak is caused by the g_dbus API, the use of which was removed in Pacemaker 1.11. I've also attached the Valgrind output from the run that exposed the issue. Given that this issue affects production stability (a periodic restart of Pacemaker is required), will a version of 1.11 be released for Trusty? (I'm happy to upgrade the OS to Trusty to get it). If not, can you advise which version of the OS will be the first to take 1.11 please? ** Description changed: [Impact] lrmd daemon with upstart resource has memory leak in Trusty affected to pacemaker 1.1.10. - affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [3] + affected to glib2.0 2.40.2-0ubuntu1 >> for glib2.0 created new lp [1] Please note that patch for pacemaker is created myself. [Test Case] https://pastebin.ubuntu.com/p/fqK6Cx3SKK/ you can check memory leak with this script [Regression] - Restarting daemon after upgrading this pkg will be needed. this patch adds free for non-freed dynamic allocated memory. so it solves memory leak. + Restarting daemon after upgrading this pkg will be needed. this patch adds free for non-freed dynamic allocated memory. so it solves memory leak. [Others] this patch is from my self with testing. Please review carefully if it is ok. + + [1] https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741 [Original Description] I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy (13.10) and have encountered a memory leak in lrmd. The details of the bug are covered here in this thread (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html) but to summarise, the Pacemaker developers believe the leak is caused by the g_dbus API, the use of which was removed in Pacemaker 1.11. I've also attached the Valgrind
[Desktop-packages] [Bug 1750741] Re: Memory leak in g_dbus_proxy_new_for_bus_sync()
** Patch added: "lp1750741_trusty_glib2.0.debdiff" https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+attachment/5059468/+files/lp1750741_trusty_glib2.0.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1750741 Title: Memory leak in g_dbus_proxy_new_for_bus_sync() Status in glib2.0 package in Ubuntu: Fix Released Bug description: [Impact] This issue is found while debugging pacemaker lrmd memory leak glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1] said this is affected to Trusty [Test Case] https://pastebin.ubuntu.com/p/fqK6Cx3SKK/ you can check memory leak with this script [Regression] This patch is affected to library pkg. so related daemon should be restarted after patching. patch itself is very simple and old. it seems verified for few years. [Others] original commit https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+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 1750741] [NEW] Memory leak in g_dbus_proxy_new_for_bus_sync()
Public bug reported: [Impact] This issue is found while debugging pacemaker lrmd memory leak glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1] said this is affected to Trusty [Test Case] https://pastebin.ubuntu.com/p/fqK6Cx3SKK/ you can check memory leak with this script [Regression] This patch is affected to library pkg. so related daemon should be restarted after patching. patch itself is very simple and old. it seems verified for few years. [Others] original commit https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c ** Affects: glib2.0 (Ubuntu) Importance: Undecided Status: Fix Released ** Tags: sts sts-sru-needed ** Tags added: sts sts-sru-needed ** Also affects: glib2.0 (Ubuntu) Importance: Undecided Status: New ** No longer affects: pacemaker (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1750741 Title: Memory leak in g_dbus_proxy_new_for_bus_sync() Status in glib2.0 package in Ubuntu: Fix Released Bug description: [Impact] This issue is found while debugging pacemaker lrmd memory leak glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1] said this is affected to Trusty [Test Case] https://pastebin.ubuntu.com/p/fqK6Cx3SKK/ you can check memory leak with this script [Regression] This patch is affected to library pkg. so related daemon should be restarted after patching. patch itself is very simple and old. it seems verified for few years. [Others] original commit https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade
Although a month has passed since 17 Jan 2018, this compiz segfault surface up today on 21 February 12:20 pm GMT +8 on my lenovo T400. I am sorry if i have necroposted now, but this bug is annoying and i seek all of your kind assistance. Details are: $sudo lshw -c video *-display description: VGA compatible controller product: RV620/M82 [Mobility Radeon HD 3450/3470] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 32 bits clock: 33MHz capabilities: pm pciexpress msi vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:30 memory:d000-dfff ioport:2000(size=256) memory:cfff-cfff memory:cff0-cff1 $lsb_release -a LSB Version: core-9.20160110ubuntu0.2-amd64:core-9.20160110ubuntu0.2-noarch:security-9.20160110ubuntu0.2-amd64:security-9.20160110ubuntu0.2-noarch Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial $apt policy xserver-xorg-core xserver-xorg-core: Installed: 2:1.18.4-0ubuntu0.7 Candidate: 2:1.18.4-0ubuntu0.7 Version table: *** 2:1.18.4-0ubuntu0.7 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 2:1.18.3-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages $apt policy libgl1-mesa-dri libgl1-mesa-dri: Installed: 17.2.8-0ubuntu0~16.04.1 Candidate: 17.2.8-0ubuntu0~16.04.1 Version table: *** 17.2.8-0ubuntu0~16.04.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 100 /var/lib/dpkg/status 11.2.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages $dmesg | grep compiz compiz: segfault at 38 ip 7f98dd4ac240 sp 7ffc01ba0410 error 4 in libmove.so[7f98dd4a1000+15000] >From what i have read above about ppa purge and adding ppa/proposed, does it still apply to my system? -- 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/1735594 Title: [regression] compiz crashes after Mesa upgrade Status in mesa package in Ubuntu: Fix Committed Status in mesa source package in Xenial: Fix Released Status in mesa source package in Artful: Fix Released Bug description: [Impact] When I use the Unity session I automatically get logged out under these conditions: When I hover with my mouse over any icon of the sidebar. When I press the alt key. When I press the super key. running dmesg after this unwanted logout happens I get following information: compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0 error 4 in i965_dri.so[7fbca2af6000+7e4000] This is caused by a mesa upgrade, which added a patch for bug #1727401. The crasher is reproduced on: - gen4 / gen5 Intel - if using modesetting X driver, like when xserver-xorg-video-intel is not installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults to modesetting) [Test case] Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash. [Regression potential] The backported patches need to be tested, here for regressions and on 1727401 that they fix the original bug (again). Best to test on a wide array of Intel HW: gen4 (965GM/GM45/G45) gen5 (Ironlake) gen6 (Sandy Bridge) gen7 (Bay Trail, Ivy Bridge, Haswell) gen8 (Braswell, Broadwell) gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1711936] Re: Severe graphical corruption in gnome-shell with nouveau [Nvidia GeForce 8400M GS]
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1711936 Title: Severe graphical corruption in gnome-shell with nouveau [Nvidia GeForce 8400M GS] Status in gnome-shell package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: When running gnome-shell on Ubuntu 17.10, text is visible only as white blocks (or sometimes not visible at all), and some graphics, such as the icons on the launcher menu, are corrupt. Only objects drawn by the gnome-shell and related programs seem to be affected. Software which is not part of the gnome-shell, such as LibreOffice, calculator, terminal, etc displays without corruption. --- ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple' InstallationDate: Installed on 2017-08-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Tags: artful wayland-session Uname: Linux 4.12.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1711936/+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 1732704] Re: Window opened with shortcut custom global shortcut does not get focus
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1732704 Title: Window opened with shortcut custom global shortcut does not get focus Status in gnome-shell package in Ubuntu: Expired Bug description: I have a custom shortcut set to open google translate in firefox. If I'm using firefox already, this key combination will open a new firefox window with translate, yet it will not have focus. This is problematic in that I must then type to focus the window. Steps: 1. create a custom shortcut to the command "/usr/bin/firefox --browser --new-window translate.google.com" 2. open a firefox window. 3. type the shortcut. 4. see that the window does not have focus (even if it may appear in front!) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1732704/+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 1731872] Re: gnome shell crashed when searching for 're'
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1731872 Title: gnome shell crashed when searching for 're' Status in gnome-shell package in Ubuntu: Expired Bug description: When searching after pressing the super key, gnome shell restarts/hangs as soon as the search term becomes 're'. I can search for 'r' without issues. In this case I was trying to bring up remmina. The issues replicates in both nvidia and intel modes on Asus UX550VE. I will try on my PC later on, to see if I can reproduce it there as well. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 Uname: Linux 4.14.0-041400-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3.2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Nov 13 10:53:57 2017 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (41 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20171002) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1731872/+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 1735127] Re: Ubuntu AA (gnome) - panel and dock transparency animation crashes Gnome shell
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1735127 Title: Ubuntu AA (gnome) - panel and dock transparency animation crashes Gnome shell Status in gnome-shell package in Ubuntu: Expired Bug description: I believe this is caused by the panel and dock transparency animations on the Ubuntu session (not the vanilla Gnome session). This is best replicated on a multi-monitor set up. Scenario 1: - Open some app, make full screen on monitor with panel and dock - panels are now opaque - Open some other app unmaximized - Rapidly drag back and forth between monitors - Everything's good Scenario 2: - Ensure no app is making the panel / dock opaque - Open some app unmaximized - Rapidly drag back and forth between monitors - Crash Now this happens both on X (where Gnome restarts) and Wayland (where we get kicked out to the login screen). Just before the crash, CPU usage spikes and frame rate drops dramatically. Ubuntu 17.10, Wayland and X, intel graphics. I can't find no gnome logs anywhere, but a 270MB binary file appears at ~/core, do you need this? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1735127/+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 1711936] Re: Severe graphical corruption in gnome-shell with nouveau [Nvidia GeForce 8400M GS]
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1711936 Title: Severe graphical corruption in gnome-shell with nouveau [Nvidia GeForce 8400M GS] Status in gnome-shell package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Bug description: When running gnome-shell on Ubuntu 17.10, text is visible only as white blocks (or sometimes not visible at all), and some graphics, such as the icons on the launcher menu, are corrupt. Only objects drawn by the gnome-shell and related programs seem to be affected. Software which is not part of the gnome-shell, such as LibreOffice, calculator, terminal, etc displays without corruption. --- ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 17.10 GsettingsChanges: org.gnome.desktop.interface gtk-im-module 'gtk-im-context-simple' InstallationDate: Installed on 2017-08-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818) Package: linux PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Tags: artful wayland-session Uname: Linux 4.12.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1711936/+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 1736820] Re: Laptop doesn't suspend on lid close
[Expired for gnome-shell (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1736820 Title: Laptop doesn't suspend on lid close Status in gnome-shell package in Ubuntu: Expired Bug description: Laptop is Thinkpad T450. On previous releases of Ubuntu I would close the lid to suspend it. 17.10 doesn't suspend on lid close, which has caused my laptop to overheat in my bag a couple of times. I have installed tweak tool and made sure the power section toggle switch is on. But it makes no difference. I have also tried rebooting, flipping the toggle back and forth, and still nothing. Should I see a key change somewhere in dconf-editor once I flip the switch? Does suspend work for others, on the T450? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 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: Wed Dec 6 23:25:07 2017 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.shell' b'command-history' b"['xkill', 'goxel']" b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true' b'org.gnome.shell' b'app-picker-view' b'uint32 1' b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'org.gnome.Software.desktop', 'google-chrome.desktop', 'chrome-hebeiaianhihkafkbopcfpkgloimgagb-Default.desktop', 'discord.desktop', 'chrome-flidaonfhnkbealpaagddgffpppelhhb-Profile_1.desktop', 'chrome-celnaknmndcdcjcagffhbhciignkeokb-Default.desktop', 'chrome-dcdbodpaldbchkfinnjphocleggfceip-Default.desktop', 'chrome-ddiddklncfgbfaaahngklemobghhjkim-Default.desktop', 'chrome-fimghoffjcofmboofohmacdeabiimdeg-Profile_1.desktop', 'irccloud-desktop_irccloud-desktop.desktop', 'telegramdesktop.desktop', 'org.gnome.Terminal.desktop', 'code.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" InstallationDate: Installed on 2017-08-02 (126 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170712) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1736820/+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 1750352] Re: gnome-shell freeze on key press while high CPU load
Thanks. Your system log is full of error messages about 'extensions' that I have never seen before. Like: févr. 20 11:55:15 hostname nautilus[2460]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x55d6331da690 févr. 20 11:55:15 hostname nautilus[2460]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x55d6334b7770 févr. 20 11:55:15 hostname nautilus[2460]: Unexpected plugin response. This probably indicates a bug in a Nautilus extension: handle=0x55d63425e160 and févr. 20 12:43:51 hostname gnome-shell[2029]: JS ERROR: ReferenceError: NM80211ApFlags is not defined WirelessList<._getApSecurityType@/home/username/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/indicators/network.js:448:1 wrapper@resource:///org/gnome/gjs/modules/_legacy.js:82:22 WirelessList<._accessPointAdded@/home/username/.local/share/gnome-shell/extensions/extend-panel-menu@julio641742/indicators/network.js:567:27 Please try disabling/uninstalling all gnome-shell extensions other than the Ubuntu default ones (gnome-shell-extension-appindicator, gnome- shell-extension-ubuntu-dock), and tell us if the bug persists. If that fixes it then please try to figure out which extension was causing the bug, by reintroducing them one-by-one. -- 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/1750352 Title: gnome-shell freeze on key press while high CPU load Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug happens randomly (once an hour), on keyboard input in different apps, ex Firefox address bar, Alfred launcher or Gnome Overview. I could not find steps to reproduce (tried reducing keyboard interval and repeated keypress following STRs from #1731420 but it did not freeze, though CPU use increased). System is completely frozen, cannot switch to TTY, but music continues to play. Sometimes it logs out but most of the time I have to force reboot by long pressing the shutdown key. syslog show message : "Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!" multiple times. Looks similar to bug https://bugzilla.gnome.org/show_bug.cgi?id=777693 Ubuntu 17.10 with Gnome session on wayland. Gnome-Shell 3.26.2-0ubuntu0.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: lightdm DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-28 (83 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip i2c input libvirt lpadmin plugdev sambashare sudo wireshark www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750352/+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 1750171] Re: Applications' extension bug - Activity menu vanished in the abyss
This is technically not an Ubuntu bug, since the problem originated from code acquired outside of Ubuntu. However rather than mark it as invalid, we might be able to suggest a fix. Please: 1. Clarify what you mean by "Activity menu". "Activities" is a button, not a menu. And the menu beside that button is the application menu. Which one do you mean? 2. Try: Install 'gnome-tweak-tool' and check that Tweaks > Top Bar > Application Menu = ON ** Changed in: gnome-desktop (Ubuntu) Importance: Undecided => Low ** Changed in: gnome-desktop (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1750171 Title: Applications' extension bug - Activity menu vanished in the abyss Status in gnome-desktop package in Ubuntu: Incomplete Bug description: Hi, So I downloaded the applications' extension from gnome shell extensions website. The application menu appears on the left side of the top bar but an "error" notification appears beside the extension, plus the menu doesn't work : it is just stuck there and THE MAIN PROBLEM is that I can't bring back the activity button even if I delete the extension, reboot, etc. Anyone experienced the same issue ? I run Ubuntu 17.10 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2509 F pulseaudio ph0enix3059 F pulseaudio /dev/snd/controlC0: gdm2509 F pulseaudio ph0enix3059 F pulseaudio DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2018-02-16 (1 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20180108.1) MachineType: Dell Inc. Inspiron 5737 Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: kvm libvirt _MarkForUpload: True dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 02TKW1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn02TKW1:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.family: 00 dmi.product.name: Inspiron 5737 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1750171/+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 1750707] [NEW] LibreOffice says permission was denied to open a file in a NTFS partition, even with it having permission
Public bug reported: I'm trying to open a spreadsheet file located in a NTFS partition, but LibreOffice gives an error saying the permission is denied. I am sure I have permission to edit that file and that partition because I could edit it with Gedit (it does not show Read-Only on the bar) and I copied and created new files (not with LibreOffice) in the same directory the spreadsheet is. The NTFS partition is mounted at boot time using the following on /etc/fstab (redacted): UUID= /mnt/W10 ntfs-3g defaults,windows_names 0 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:5.4.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Feb 20 23:16:05 2018 InstallationDate: Installed on 2017-06-13 (252 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2017-10-20 (124 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- 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/1750707 Title: LibreOffice says permission was denied to open a file in a NTFS partition, even with it having permission Status in libreoffice package in Ubuntu: New Bug description: I'm trying to open a spreadsheet file located in a NTFS partition, but LibreOffice gives an error saying the permission is denied. I am sure I have permission to edit that file and that partition because I could edit it with Gedit (it does not show Read-Only on the bar) and I copied and created new files (not with LibreOffice) in the same directory the spreadsheet is. The NTFS partition is mounted at boot time using the following on /etc/fstab (redacted): UUID= /mnt/W10 ntfs-3g defaults,windows_names 0 0 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice 1:5.4.4-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Feb 20 23:16:05 2018 InstallationDate: Installed on 2017-06-13 (252 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2017-10-20 (124 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1750707/+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 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox
OK, thanks. I don't know why that happens. It never fails like that for me but other people have reported the problem you describe. Next we try an alternative approach: 1. kill -ABRT `pidof -s gnome-shell` 2. Look in /var/crash for a new crash file (may take a little while to be written) 3. ubuntu-bug /var/crash/YOURFILE.crash 4. Tell us the new bug ID created. -- 5. If #3-4 failed then set this bug to Private (top right of the page) and attach the crash file here. -- 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/1749779 Title: System freeze when going back and forth fullscreen mode with Firefox Status in gnome-shell package in Ubuntu: Incomplete Bug description: Use Ubuntu 17.10 Open a Wayland session Start Firefox Press F11 repeatedly --> The System freezes ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 20:09:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749779/+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 1721248] Re: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos
Starting in Ubuntu 17.10, totem (and some other apps like gnome-maps) use Wayland subsurfaces by default. This means the video (or maps) rectangle are able to redraw without redrawing the window decorations and saves a lot of CPU. A side-effect of this is that screenshots didn't seem to work any more. However I believe that's just going to be a bug in gnome-shell/mutter, for not being able to screenshot its own Wayland subsurfaces. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Changed in: mutter (Ubuntu) Importance: Undecided => Low ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed ** Changed in: gnome-shell (Ubuntu) Importance: Undecided => Low ** Tags added: wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1721248 Title: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: I try to get a screenshot from my video and totem shows a message saying it could not get a screenshot of the video and suggesting to open a bug. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 14:54:16 2017 InstallationDate: Installed on 2017-09-29 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1721248/+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 1750702] Re: gegl build failure on armhf
** Changed in: gegl Status: Unknown => Confirmed ** Changed in: gegl Importance: Unknown => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gegl in Ubuntu. https://bugs.launchpad.net/bugs/1750702 Title: gegl build failure on armhf Status in GEGL: Confirmed Status in gegl package in Ubuntu: Confirmed Bug description: Reported upstream who requests more debugging info. To manage notifications about this bug go to: https://bugs.launchpad.net/gegl/+bug/1750702/+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 1731420] Re: gnome-shell hangs (goes into key repeat runaway) when key repeat is used on chromium-browser's address bar
** Information type changed from Public Security to Public -- 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/1731420 Title: gnome-shell hangs (goes into key repeat runaway) when key repeat is used on chromium-browser's address bar Status in GNOME Shell: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: GNOME Shell running in Wayland completely hangs when the key repeat rate is sufficiently high and used inside Chromium and/or Google Chrome. Then GNOME Shell, at-spi's dbus-daemon, ibus-daemon, and chromium-browser all get stuck at 100% CPU. GNOME Shell's RSS also quickly increases to >2GB and continues climbing. Attempting to kill chromium-browser in a separate TTY either causes one of two things: - gnome-shell, dbus-daemon and ibus-daemon remain at 100% CPU and stuck; or - gnome-shell temporarily recovers, then crashes, taking the entire session with it and returning to the login screen. Steps to reproduce: 1. Set key repeat rates to a high value (these are my actual settings): $ gsettings set org.gnome.desktop.peripherals.keyboard repeat-interval 3 $ gsettings set org.gnome.desktop.peripherals.keyboard repeat true $ gsettings set org.gnome.desktop.peripherals.keyboard delay 180 2. Start chromium-browser 3. Focus the location bar in chromium-browser 4. Press and hold a key (e.g. a) for a few seconds (~10 should do) 5. Observe that gnome-shell probably has hung by this point. If it hasn't, proceed to step 6. 6. Press and hold the backspace button until the location bar has cleared, then continue for another few seconds (~10 seconds should do) This also affected GNOME Shell 3.24, but I was able to reduce the chances of it happening by renicing my chromium processes to +10, thereby giving GNOME Shell a greater chance at the CPU. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.1-0ubuntu5 Uname: Linux 4.13.4-hyper2+ x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Nov 10 16:50:13 2017 DisplayManager: gdm3 SourcePackage: gnome-shell UpgradeStatus: Upgraded to artful on 2017-11-04 (5 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1731420/+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 1750702] [NEW] gegl build failure on armhf
Public bug reported: Reported upstream who requests more debugging info. ** Affects: gegl Importance: Unknown Status: Unknown ** Affects: gegl (Ubuntu) Importance: High Status: Confirmed ** Tags: ftbfs ** Bug watch added: GNOME Bug Tracker #793682 https://bugzilla.gnome.org/show_bug.cgi?id=793682 ** Also affects: gegl via https://bugzilla.gnome.org/show_bug.cgi?id=793682 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gegl in Ubuntu. https://bugs.launchpad.net/bugs/1750702 Title: gegl build failure on armhf Status in GEGL: Unknown Status in gegl package in Ubuntu: Confirmed Bug description: Reported upstream who requests more debugging info. To manage notifications about this bug go to: https://bugs.launchpad.net/gegl/+bug/1750702/+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 1749678] Re: in wayland and ()and swicth to xorg proprem again black video
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 ** Information type changed from Public Security to Public -- 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/1749678 Title: in wayland and ()and swicth to xorg proprem again black video Status in gnome-shell package in Ubuntu: New Bug description: happen when I connect my telefone huawei p10 lite WASLX1A ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 Uname: Linux 4.15.3-041503-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Wed Feb 14 21:37:34 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-02-07 (7 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180126) ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749678/+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 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications
block-proposed still belongs for mesa, having it blocked for other reasons isn't good enough because this bug will break the Kubuntu and Lubuntu Next desktops. ** No longer affects: qtbase-opensource-src (Ubuntu Bionic) ** No longer affects: qtbase-opensource-src (Ubuntu) ** Tags added: block-proposed -- 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/1749472 Title: mesa 18.0.0 will cause rendering errors in Qt applications Status in mesa package in Ubuntu: New Status in mesa source package in Bionic: New Bug description: From: https://bugreports.qt.io/browse/QTBUG-66348 ** extract ** The `QOpenGLShaderProgram` class in Qt can be used to compile and link OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is available, it can cache those shaders on disk (~/.cache/qtshadercache). The i965 driver in Mesa supports this extension since version 18.0.0. When the shader is loaded using the `glProgramBinary` function, OpenGL can refuse it if for example some hardware or software component changed. Mesa refuses binaries that were created by any other build of Mesa (using among other things the build_id of the library). If the shader is refused, Qt should fallback to compiling it from sources, but it incorrectly calls glLinkProgram first. The glLinkProgram succeeds, because it actually links 0 shaders together. That is allowed in OpenGL compatibility profile and the resulting program works as a fixed pipeline. Which of course does not render as expected. This causes rendering errors in Qt applications every time Mesa is updated since version 18.0.0. For example white screen in sddm. This issue was originally reported in openSUSE (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578). ** end extract ** As this potentially effects Qt applications, and could even render display manager login unusable, this should be a blocking bug in mesa and Qt until Qt mitigations patches pass codereview and can be included in Qtbase for 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+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 1734545] Re: Translations not updated from upstream
I was wrong in comment #10 - checked apparently the wrong files. All the stuff from the -proposed build is in the tarball. https://launchpad.net/ubuntu/bionic/+upload/17626717/+files/gnome- sudoku_3.27.3-1build1_amd64_translations.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1734545 Title: Translations not updated from upstream Status in gnome-sudoku package in Ubuntu: Confirmed Bug description: The Danish translation of gnome-sudoku lacks many strings as it has not been synchronized with upstream for years: https://translations.launchpad.net/ubuntu/+source/gnome-sudoku Meanwhile gnome-sudoku is and has always been completely translated upstream. Indeed it has been fully translated for every release of GNOME ever since it forked out of gnome-games. Take for example current master: https://l10n.gnome.org/vertimus/gnome-sudoku/master/po/da It seems there are rather grave problems with translation imports in Launchpad. I reported a similar issue recently for util-linux: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1730793 Who knows how many other packages are affected, and in what languages. I think Launchpad translations should be disabled entirely for all source packages - the translations belong upstream, with the project. Thanks to scootergrisen for making me aware of this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1734545/+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 1748838] Re: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1726156 *** https://bugs.launchpad.net/bugs/1726156 ** Information type changed from Public Security to Public -- 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/1748838 Title: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() Status in gnome-shell package in Ubuntu: New Bug description: so what is the reason ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 12 12:10:38 2018 DisplayManager: gdm3 ExecutablePath: /usr/lib/gnome-shell/gnome-shell-portal-helper GsettingsChanges: b'org.gnome.shell' b'favorite-apps' b"['org.gnome.Nautilus.desktop', 'firefox.desktop', 'libreoffice-writer.desktop', 'libreoffice-calc.desktop', 'libreoffice-impress.desktop', 'org.gnome.Software.desktop', 'gnome-control-center.desktop', 'libreoffice-startcenter.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'clock-format' b"'12h'" InstallationDate: Installed on 2018-01-29 (13 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: /usr/lib/gnome-shell/gnome-shell-portal-helper ProcEnviron: XDG_RUNTIME_DIR= SHELL=/bin/bash LD_PRELOAD= PATH=(custom, no user) LANG=en_US.UTF-8 Signal: 6 SourcePackage: gnome-shell StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell-portal-helper crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1748838/+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 1750687] Re: gedit crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 1570938 *** https://bugs.launchpad.net/bugs/1570938 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 #1570938, 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/1750687/+attachment/5059277/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1750687/+attachment/5059279/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1750687/+attachment/5059283/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1750687/+attachment/5059284/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1750687/+attachment/5059285/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1750687/+attachment/5059286/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1750687/+attachment/5059287/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1570938 ** 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 gedit in Ubuntu. https://bugs.launchpad.net/bugs/1750687 Title: gedit crashed with SIGSEGV in g_closure_invoke() Status in gedit package in Ubuntu: New Bug description: i don't have more information ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gedit 3.22.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 21 02:05:23 2018 ExecutablePath: /usr/bin/gedit InstallationDate: Installed on 2017-09-07 (166 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcCmdline: gedit /home/username/Downloads/6a3337e2-b3b4-4fe3-a102-0d7ff63690b6.xml SegvAnalysis: Segfault happened at: 0x7f68d427cee6:mov0xc8(%rax),%rbp PC (0x7f68d427cee6) ok source "0xc8(%rax)" (0x00f8) not located in a known VMA region (needed readable region)! destination "%rbp" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gedit StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/gedit/libgedit.so g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gedit crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: Upgraded to artful on 2017-10-27 (115 days ago) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1750687/+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 1750682] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1750682/+attachment/5059246/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1750682/+attachment/5059248/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1750682/+attachment/5059252/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1750682/+attachment/5059253/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1750682/+attachment/5059254/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1750682/+attachment/5059255/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1750682/+attachment/5059256/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1750682 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: this was a debootstrap install of ubuntu 18 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Feb 20 23:12:23 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750682/+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 1542471] Re: Playing mp3 files causes: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer.
(had this tab open in a really old browser session ... doing some clean up ...) retested on Fedora 26, it works! (bug no longer present) {{{ $ sudo zfs list | grep music zstorage/music 7.40G 84.9G 7.40G /zstorage/music }}} rhythmbox opens, music library on that pool, music plays {{{ 4.14.14-200.fc26.x86_64, zfs-0.7.5-1.fc26.x86_64, rhythmbox-3.4.1-3.fc26.x86_64 }}} ** Attachment added: "rbox_zfs_pool_source.png" https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1542471/+attachment/5059243/+files/rbox_zfs_pool_source.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1542471 Title: Playing mp3 files causes: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer. Status in gstreamer1.0 package in Ubuntu: Confirmed Status in rhythmbox package in Ubuntu: Confirmed Bug description: I get the following error in the console when trying to play a mp3 file using Rhythmbox: (21:23:27) [0x832a60] [rb_shell_player_error] rb-shell-player.c:2443: playback error while playing: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer. I don't get the same error while trying to play the same file using 'Video's. I installed the required codec using the 'Video's application as it told me to install a codec. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libgstreamer1.0-0 1.7.1-1 ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0 Uname: Linux 4.4.0-2-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia zfs zunicode zcommon znvpair zavl ApportVersion: 2.19.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri Feb 5 21:24:05 2016 ExecutablePath: /usr/bin/rhythmbox SourcePackage: gstreamer1.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1542471/+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 1728467] Re: All files on ntfs partitions are marked executable
** Tags removed: zesty ** Tags added: bionic ** Tags removed: bb-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1728467 Title: All files on ntfs partitions are marked executable Status in udisks2 package in Ubuntu: Confirmed Bug description: This did not happen in 14.04 but somewhere since then udisks2 sets any & all files on ntfs partitions as executable. Additionally if file is copied over to user's ext4 partion the bit remains set. Can't see why this would be intentional?? In 14.04 udisks2 - :static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077", "fmask=0177", NULL }; In 16.04, 17.04, 17.10,18.04 udisks2 - :static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL }; ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: udisks2 2.1.7-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 CurrentDesktop: Unity CustomUdevRuleFiles: 70-snap.core.rules Date: Sun Oct 29 21:20:19 2017 InstallationDate: Installed on 2017-09-16 (43 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7 SourcePackage: udisks2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1728467/+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 1749779] Re: System freeze when going back and forth fullscreen mode with Firefox
I applied the workaround and ran again the command. It seems that nothing happens when I try to send the report: hadrien@c18:~$ apport-cli --hanging -P `pidof -s gnome-shell` *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (170.3 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s hadrien@c18:~$ I also tried "V" to view the report and I get the same kind of report I attached previously. -- 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/1749779 Title: System freeze when going back and forth fullscreen mode with Firefox Status in gnome-shell package in Ubuntu: Incomplete Bug description: Use Ubuntu 17.10 Open a Wayland session Start Firefox Press F11 repeatedly --> The System freezes ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Feb 15 20:09:27 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (135 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1749779/+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 1433774] Re: When double clicking an executable bash script in file manager, it opens in gedit rather than executing
And Ubuntu 17.10 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1433774 Title: When double clicking an executable bash script in file manager, it opens in gedit rather than executing Status in nautilus package in Ubuntu: Confirmed Bug description: Download https://www.torproject.org/dist/torbrowser/4.0.4/tor-browser- linux64-4.0.4_en-US.tar.xz and extract it to a folder. Navigate to that folder in the GNOME file manager. Double click "start-tor-browser". Expected result: The script executes and launches the browser. Actual result: The script opens in gedit. Even when right clicking it, "Run" is not listed as an option anywhere. It's not even an option under "Open With... -> Other Application". The only way to run it is from a terminal. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: nautilus 1:3.10.1-0ubuntu9.7 ProcVersionSignature: Ubuntu 3.16.0-31.43~14.04.1-generic 3.16.7-ckt5 Uname: Linux 3.16.0-31-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 18 16:00:48 2015 GsettingsChanges: InstallationDate: Installed on 2015-03-06 (12 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1433774/+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 1750030] Re: Report fwupd version in user agent
Confirmed with upstream, this fix is already in bionic (3.26.6, currently 3.27.90 in proposed). -- 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/1750030 Title: Report fwupd version in user agent Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Bug description: [Impact] Some firmware updates fail require a recent version of fwupd to work. Upstream has requested we update the user agent sent in HTTP requests so that they can stop sending firmware to clients that may not work. [Test Case] Check with the fwupd server that the correct user agent is being sent. [Regression Potential] Low. The fix is simply to add to the user-agent string used in HTTP requests. There are some situations that LVFS shouldn't be offering firmware to certain machines. Upstream is going to use the user agent for filtering these firmware offerings and it would be good if gnome-software can report the user agent. The following has been added to the gnome 3.20 tree: https://gitlab.gnome.org/GNOME/gnome-software/commit/9bf4ecef4daa2d31827810d672458768c3c2a2b3 Can this please be backported to xenial? Bionic can already report this as part of 3.26 gnome-software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750030/+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 1750098] Re: Ubuntu software shows snaps as installed even if it failed to install
What version of GNOME Software is this? -- 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/1750098 Title: Ubuntu software shows snaps as installed even if it failed to install Status in gnome-software package in Ubuntu: New Bug description: As stated on https://forum.snapcraft.io/t/ubuntu-software-shows-snaps- as-installed-even-if-it-failed-to-install/4054 When a snap fails to install, Software center still shows the download as completed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750098/+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 1734586] Re: Merge NetworkManager with Debian 1.10.0-1
the python-dbusmock fix has been commited upstream, now the n-m one needs to be resolved -- 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/1734586 Title: Merge NetworkManager with Debian 1.10.0-1 Status in network-manager package in Ubuntu: Fix Committed Bug description: Debian has packaged the latest major release of NetworkManager, 1.10. We should update to this version for Ubuntu 18.04 "bionic". I have prepared the merge at https://git.launchpad.net/network-manager?h=bionic The only thing missing is that this patch needs to be rebased or dropped: https://git.launchpad.net/network-manager/tree/debian/patches/dns-manager-don-t-merge-split-DNS-search-domains.patch?h=bionic Otherwise, the build will fail: src/.libs/libNetworkManagerTest.a(src_libNetworkManager_la-nm-dns-manager.o): In function `merge_one_ip_config_data': ./src/dns/nm-dns-manager.c:417: undefined reference to `nm_ip4_config_get_never_default' ./src/dns/nm-dns-manager.c:419: undefined reference to `nm_ip4_config_get_never_default' There's been a lot of refactoring, but this commit looks important: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=5c29945 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1734586/+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 1580168] Re: Tab descriptions are unreadable, black text on black background
It doesn't affect Firefox 58.0.1 on Kubuntu 16.04.3, Plasma 5.8.8. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1580168 Title: Tab descriptions are unreadable, black text on black background Status in firefox package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: When I hover the mouse button on top of the Firefox tabs, the tab descriptions are unreadable, black text on black background. This also happens on some other web sites which pop up a description box, e.g. on portal.azure.com when hovering over your username in the top right corner in the browser. This probably started happening when Firefox was first compiled against gtk3. My gtk3 theme is oxygen-gtk. 1) The Kubuntu release is 14.04.4 2) The version of Firefox is 46.0+build5-0ubuntu0.14.04.2 3) I expect to be able to read the tab descriptions 4) The tab descriptions are black text on black background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580168/+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 1739537] Re: mtp volume is not removed when unplugging
This bug was fixed in the package gvfs - 1.35.91-1ubuntu1 --- gvfs (1.35.91-1ubuntu1) bionic; urgency=medium * Sync with Debian. Remaining change: - Don't build the NFS backend since the required library is in universe. See bug 1746598. gvfs (1.35.91-1) experimental; urgency=medium * New upstream development release * Drop no longer needed Files-Excluded * Add workaround for Ubuntu translations issue * Drop 0008-test-Make-etc-init-optional.patch: Applied in new release gvfs (1.35.90-1) experimental; urgency=medium [ Jeremy Bicha ] * New upstream development release - Fixes "MTP volume not removed after disconnecting" (Closes: #882353) (LP: #1739537) * debian/copyright: Use Files-Excluded to avoid non-free RFCs. * Update Vcs fields for migration to https://salsa.debian.org/ * Drop obsolete Build-Depends on libudev-dev * Build with meson * Don't build the Blu-ray backend on Ubuntu since the required library is in universe. See bug 1746629. * Cherry-pick 0008-test-Make-etc-init-optional.patch: - Fix tests when /etc/init/ doesn't exist (on minimal systems) [ Martin Pitt ] * Run autopkgtests through sudo starting as normal user, so that it can find a non-root user. -- Jeremy BichaMon, 19 Feb 2018 16:56:37 -0500 ** Changed in: gvfs (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1739537 Title: mtp volume is not removed when unplugging Status in gvfs: Fix Released Status in gvfs package in Ubuntu: Fix Released Bug description: as in the title ... was pointed at this for nautilus https://gitlab.gnome.org/GNOME/nautilus/issues/154 see the same in thunar ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gvfs 1.34.1-1ubuntu4 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Dec 21 05:26:33 2017 InstallationDate: Installed on 2017-09-02 (109 days ago) InstallationMedia: Xubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170902) SourcePackage: gvfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gvfs/+bug/1739537/+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 1750651] [NEW] man page does not include options specific to eog
Public bug reported: The manpage includes config for X and GTK, but not the specific EOG stuff mentioned here: https://help.gnome.org/users/eog/stable/commandline.html.en I was specifically looking for --fullscreen and --disable-gallery which are not mentioned. ** Affects: eog (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1750651 Title: man page does not include options specific to eog Status in eog package in Ubuntu: New Bug description: The manpage includes config for X and GTK, but not the specific EOG stuff mentioned here: https://help.gnome.org/users/eog/stable/commandline.html.en I was specifically looking for --fullscreen and --disable-gallery which are not mentioned. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1750651/+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 1580168] Re: Tab descriptions are unreadable, black text on black background
I can confirm that this is no longer problem with Ubuntu Gnome 18.04 with Firefox 58, Nautilus 3.26, Chromium 64 and Google Chrome 64 firefox: Installed: 58.0+build6-0ubuntu0.17.10.1 Candidate: 58.0+build6-0ubuntu0.17.10.1 Version table: *** 58.0+build6-0ubuntu0.17.10.1 100 100 /var/lib/dpkg/status 57.0.1+build2-0ubuntu1 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages nautilus: Installed: 1:3.26.0-0ubuntu1 Candidate: 1:3.26.0-0ubuntu1 Version table: *** 1:3.26.0-0ubuntu1 500 500 http://za.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status chromium-browser: Installed: 64.0.3282.167-0ubuntu1 Candidate: 64.0.3282.167-0ubuntu1 Version table: *** 64.0.3282.167-0ubuntu1 500 500 http://za.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status google-chrome-stable: Installed: 64.0.3282.167-1 Candidate: 64.0.3282.167-1 Version table: *** 64.0.3282.167-1 100 100 /var/lib/dpkg/status Users on the KDE side will need to confirm if it is fixed or not. ** No longer affects: ubuntu-gnome -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1580168 Title: Tab descriptions are unreadable, black text on black background Status in firefox package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: When I hover the mouse button on top of the Firefox tabs, the tab descriptions are unreadable, black text on black background. This also happens on some other web sites which pop up a description box, e.g. on portal.azure.com when hovering over your username in the top right corner in the browser. This probably started happening when Firefox was first compiled against gtk3. My gtk3 theme is oxygen-gtk. 1) The Kubuntu release is 14.04.4 2) The version of Firefox is 46.0+build5-0ubuntu0.14.04.2 3) I expect to be able to read the tab descriptions 4) The tab descriptions are black text on black background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1580168/+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 1580168] Re: Tab descriptions are unreadable, black text on black background
Should this be closed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1580168 Title: Tab descriptions are unreadable, black text on black background Status in Ubuntu GNOME: Confirmed Status in firefox package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: When I hover the mouse button on top of the Firefox tabs, the tab descriptions are unreadable, black text on black background. This also happens on some other web sites which pop up a description box, e.g. on portal.azure.com when hovering over your username in the top right corner in the browser. This probably started happening when Firefox was first compiled against gtk3. My gtk3 theme is oxygen-gtk. 1) The Kubuntu release is 14.04.4 2) The version of Firefox is 46.0+build5-0ubuntu0.14.04.2 3) I expect to be able to read the tab descriptions 4) The tab descriptions are black text on black background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1580168/+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 1750638] Re: Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite WICD working and native kernel support
Marked as confirmed based on several other reports on the internet: https://askubuntu.com/questions/929027/qualcomm-atheros-qca6174-802 -11ac-wireless-network-adapter-168c003e-rev-32 https://ubuntuforums.org/showthread.php?t=2323812 etc Fun update: Bluetooth from the same card works perfectly fine once airplane mode is disabled. -- 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/1750638 Title: Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite WICD working and native kernel support Status in network-manager package in Ubuntu: Confirmed Bug description: This fails in a similar manner from 16.04 to 18.04, in both gnome and unity where applicable. Details of failure in 18.04: System always boots in airplane mode, no matter what. When you disable it and go to turn the wifi on in system settings, it hangs while doing so, but sometimes works and shows wifi, though it usually doesn't. I can't reproduce the cause of success of failure, but the wifi settings menu does immediately stop updating new networks after this point no matter what. The wifi menu in the top right never works at all. How I know it's not a hardware issue: It works in windows It works in WICD People say it works in other distros It shows up under lshw -C network as expected How I know it's not a firmware issue: It works in other distros It works in WICD How I know it's not a driver issue: It's natively supported in the kernel after an open source driver that worked for everyone was merged (which no one could get properly with Ubuntu's network manager) It shows up under lshw -C network as expected It works with WICD This is the default wifi card for a ton of new Lenovo laptops, so this is actually a serious issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1750638/+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 1750638] [NEW] Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite WICD working and native kernel support
Public bug reported: This fails in a similar manner from 16.04 to 18.04, in both gnome and unity where applicable. Details of failure in 18.04: System always boots in airplane mode, no matter what. When you disable it and go to turn the wifi on in system settings, it hangs while doing so, but sometimes works and shows wifi, though it usually doesn't. I can't reproduce the cause of success of failure, but the wifi settings menu does immediately stop updating new networks after this point no matter what. The wifi menu in the top right never works at all. How I know it's not a hardware issue: It works in windows It works in WICD People say it works in other distros It shows up under lshw -C network as expected How I know it's not a firmware issue: It works in other distros It works in WICD How I know it's not a driver issue: It's natively supported in the kernel after an open source driver that worked for everyone was merged (which no one could get properly with Ubuntu's network manager) It shows up under lshw -C network as expected It works with WICD This is the default wifi card for a ton of new Lenovo laptops, so this is actually a serious issue. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Confirmed ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1750638 Title: Network Manager Can't Interact With Qualcomm Atheros QCA6174 despite WICD working and native kernel support Status in network-manager package in Ubuntu: Confirmed Bug description: This fails in a similar manner from 16.04 to 18.04, in both gnome and unity where applicable. Details of failure in 18.04: System always boots in airplane mode, no matter what. When you disable it and go to turn the wifi on in system settings, it hangs while doing so, but sometimes works and shows wifi, though it usually doesn't. I can't reproduce the cause of success of failure, but the wifi settings menu does immediately stop updating new networks after this point no matter what. The wifi menu in the top right never works at all. How I know it's not a hardware issue: It works in windows It works in WICD People say it works in other distros It shows up under lshw -C network as expected How I know it's not a firmware issue: It works in other distros It works in WICD How I know it's not a driver issue: It's natively supported in the kernel after an open source driver that worked for everyone was merged (which no one could get properly with Ubuntu's network manager) It shows up under lshw -C network as expected It works with WICD This is the default wifi card for a ton of new Lenovo laptops, so this is actually a serious issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1750638/+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 1750628] Re: "Insert Emoji" menu is untranslated
** Attachment added: "emoji1.png" https://bugs.launchpad.net/ubuntu-translations/+bug/1750628/+attachment/5059136/+files/emoji1.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1750628 Title: "Insert Emoji" menu is untranslated Status in Ubuntu Translations: New Status in gnome-characters package in Ubuntu: New Bug description: If you try to use the "Insert Emoji" menu from another application, it's untranslated on non-English Ubuntu 18.04 system. See the attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1750628/+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 1750379] Re: Distortion Realtek ALC887
This started affecting me with the kernel update to 4.4.0-112-generic on xenial. I booted the old kernel and the issue went away. Tried a few times back and forth and the 4.4.0-112 kernel consistently has the sound dropouts, while 4.4.0-108 does not. Also tested with 3 different audio cards (by varying manufacturers), same result on each. -- 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/1750379 Title: Distortion Realtek ALC887 Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Incomplete Bug description: Sounds can distort even when not amplified. Amplification worked well for years before recent PulseAudio update. The audio is Realtek ALC887 under an IntelG41 Chipset with GA-G41M-Combo main board; Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 I am seeking to engage upstream for April LTS release. Windows have abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user going! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu6 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fleamour 1049 F pulseaudio /dev/snd/controlC2: fleamour 1049 F pulseaudio /dev/snd/controlC0: fleamour 1049 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 13:54:33 2018 InstallationDate: Installed on 2018-02-19 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/25/2012 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: FB dmi.board.name: G41M-Combo 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.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: G41M-Combo dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750379/+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 1576420] Re: [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts or crackling sound
This started affecting me with the kernel update to 4.4.0-112-generic on xenial. I booted the old kernel and the issue went away. Tried a few times back and forth and the 4.4.0-112 kernel consistently has the sound dropouts, while 4.4.0-108 does not. Also tested with 3 different audio cards (by varying manufacturers), same result on each. -- 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/1576420 Title: [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts or crackling sound Status in pulseaudio package in Ubuntu: New Bug description: crackling and noisy audio out of only LH speaker. Only recently started on upgrade to 16.04. Previous versions worked correctly with no changes. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic i686 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: tron 1912 F pulseaudio /dev/snd/controlC0: tron 1912 F pulseaudio CurrentDesktop: Unity Date: Fri Apr 29 07:17:59 2016 InstallationDate: Installed on 2016-04-24 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Line Out, Rear Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [H55M-D2H, Realtek ALC887, Green Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/04/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F1 dmi.board.name: H55M-D2H 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.:bvrF1:bd05/04/2010:svnGigabyteTechnologyCo.,Ltd.:pnH55M-D2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH55M-D2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: H55M-D2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1576420/+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 1750628] Re: "Insert Emoji" menu is untranslated
** Attachment added: "emoji2.png" https://bugs.launchpad.net/ubuntu-translations/+bug/1750628/+attachment/5059137/+files/emoji2.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1750628 Title: "Insert Emoji" menu is untranslated Status in Ubuntu Translations: New Status in gnome-characters package in Ubuntu: New Bug description: If you try to use the "Insert Emoji" menu from another application, it's untranslated on non-English Ubuntu 18.04 system. See the attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1750628/+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 1750628] [NEW] "Insert Emoji" menu is untranslated
Public bug reported: If you try to use the "Insert Emoji" menu from another application, it's untranslated on non-English Ubuntu 18.04 system. See the attached screenshots. ** Affects: ubuntu-translations Importance: Undecided Status: New ** Affects: gnome-characters (Ubuntu) Importance: Undecided Status: New ** Tags: bionic l10n ** Also affects: ubuntu-translations Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-characters in Ubuntu. https://bugs.launchpad.net/bugs/1750628 Title: "Insert Emoji" menu is untranslated Status in Ubuntu Translations: New Status in gnome-characters package in Ubuntu: New Bug description: If you try to use the "Insert Emoji" menu from another application, it's untranslated on non-English Ubuntu 18.04 system. See the attached screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1750628/+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 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1707451 Title: udisksd crashed with SIGSEGV in g_mutex_lock() Status in udisks: New Status in glib package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Triaged Bug description: Showed up after login ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udisks2 2.6.5-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sun Jul 30 00:35:31 2017 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2017-06-22 (37 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170622) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/lib/udisks2/udisksd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f4900fb5c65: lock xadd %eax,(%rdi) PC (0x7f4900fb5c65) ok source "%eax" ok destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 main () Title: udisksd crashed with SIGSEGV in g_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: Z87 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1707451/+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 1707451] Re: udisksd crashed with SIGSEGV in g_mutex_lock()
As a github comment suggest a possible glibc relationship, a new version has been upgraded recently (2 days ago) glib2.0 (2.55.2-1ubuntu1) bionic; urgency=medium ** Also affects: glib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1707451 Title: udisksd crashed with SIGSEGV in g_mutex_lock() Status in udisks: New Status in glib package in Ubuntu: Confirmed Status in udisks2 package in Ubuntu: Triaged Bug description: Showed up after login ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: udisks2 2.6.5-2ubuntu1 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.6-0ubuntu4 Architecture: amd64 Date: Sun Jul 30 00:35:31 2017 ExecutablePath: /usr/lib/udisks2/udisksd InstallationDate: Installed on 2017-06-22 (37 days ago) InstallationMedia: Ubuntu-GNOME 17.10 "Artful Aardvark" - Alpha amd64 (20170622) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/lib/udisks2/udisksd ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.11.0-10-generic.efi.signed root=UUID=44b31662-d2ab-443b-9546-86d022d8de0d ro quiet splash vt.handoff=7 SegvAnalysis: Segfault happened at: 0x7f4900fb5c65: lock xadd %eax,(%rdi) PC (0x7f4900fb5c65) ok source "%eax" ok destination "(%rdi)" (0x3a9d80e262617474) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 main () Title: udisksd crashed with SIGSEGV in g_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 04/12/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.40 dmi.board.name: Z87 Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.40:bd04/12/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnZ87Extreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/1707451/+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 1750624] Re: udisksd crashed with SIGSEGV in g_mutex_lock()
*** This bug is a duplicate of bug 1707451 *** https://bugs.launchpad.net/bugs/1707451 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 #1707451, 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/1750624/+attachment/5059110/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1750624/+attachment/5059113/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1750624/+attachment/5059120/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1750624/+attachment/5059122/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1750624/+attachment/5059123/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1750624/+attachment/5059124/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1750624/+attachment/5059125/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1707451 udisksd crashed with SIGSEGV in g_mutex_lock() ** 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 udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1750624 Title: udisksd crashed with SIGSEGV in g_mutex_lock() Status in udisks2 package in Ubuntu: New Bug description: Have installed the required r8168-dkms package, and rebooted then. Got that crash at the session opening. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: udisks2 2.6.5-2ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Tue Feb 20 18:45:51 2018 ExecutablePath: /usr/lib/udisks2/udisksd Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse] Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcCmdline: /usr/lib/udisks2/udisksd ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=2f22752a-ca0f-4cff-b5d7-9754e6154d56 ro SegvAnalysis: Segfault happened at: 0x7fd519359be5: lock xadd %eax,(%rdi) PC (0x7fd519359be5) ok source "%eax" ok destination "(%rdi)" (0x75736f6e2c777220) not located in a known VMA region (needed writable region)! SegvReason: writing unknown VMA Signal: 11 SourcePackage: udisks2 StacktraceTop: g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 main () Title: udisksd crashed with SIGSEGV in g_mutex_lock() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/07/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P7.00 dmi.board.name: B150M-HDV dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP7.00:bd10/07/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-HDV:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1750624/+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 1721248] Re: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos
I have again the same problem on Ubuntu 18.04. as before problem disappears removing gstreamer1.0-vaapi corrado@corrado-p8-bb:~$ inxi -SCGx System:Host: corrado-p8-bb Kernel: 4.15.0-10-generic x86_64 bits: 64 gcc: 7.3.0 Desktop: Gnome 3.26.2 (Gtk 3.22.28-1ubuntu1) Distro: Ubuntu Bionic Beaver (development branch) CPU: Dual core Intel Core i3-7100 (-MT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 800 MHz 2: 800 MHz 3: 800 MHz 4: 800 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.6 ) driver: i915 Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 18.0.0-rc4 Direct Render: Yes corrado@corrado-p8-bb:~$ apt policy gstreamer1.0-vaapi gstreamer1.0-vaapi: Installed: 1.12.4-1ubuntu1 Candidate: 1.12.4-1ubuntu1 Version table: *** 1.12.4-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p8-bb:~$ apt policy totem totem: Installed: 3.26.0-0ubuntu5 Candidate: 3.26.0-0ubuntu5 Version table: *** 3.26.0-0ubuntu5 500 500 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.26.0-0ubuntu3 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages corrado@corrado-p8-bb:~$ -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1721248 Title: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos Status in totem package in Ubuntu: Confirmed Bug description: I try to get a screenshot from my video and totem shows a message saying it could not get a screenshot of the video and suggesting to open a bug. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 14:54:16 2017 InstallationDate: Installed on 2017-09-29 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/+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 1737053] Re: [MIR] brotli
** Changed in: brotli (Ubuntu) Assignee: Canonical Security Team (canonical-security) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brotli in Ubuntu. https://bugs.launchpad.net/bugs/1737053 Title: [MIR] brotli Status in brotli package in Ubuntu: New Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = brotli is a file compression format and library developed and maintained by Google. brotli is required by the WOFF 2.0 format for compressed web fonts. brotli and woff2 are libraries that are technically already in main because they are bundled in Firefox and webkit2gtk. The next major stable release of webkit2gtk, 2.20, will be released in March. It drops those 2 bundled libraries. I think our options are basically 1) Bundle those libraries anyway, or 2) Approve this MIR, or 3) Drop support for the WOFF2 format in webkit2gtk Security brotli is a security-sensitive library. There was one security bug fixed recently for xenial (LP: #1737364) https://security-tracker.debian.org/tracker/source-package/brotli https://launchpad.net/ubuntu/+source/brotli/+cve Quality assurance = - Ubuntu Desktop Bugs is subscribed. - dh_auto_test runs upstream build tests. Test failure would fail the build. - New autopkgtests pass on all arches: http://autopkgtest.ubuntu.com/packages/b/brotli https://ci.debian.net/packages/b/brotli/ https://bugs.launchpad.net/ubuntu/+source/brotli https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=brotli https://github.com/google/brotli/issues Dependencies No universe binary dependencies Standards compliance 4.1.1, debhelper compat 10, dh7 simple rules Maintenance === Actively maintained: https://github.com/google/brotli Not team maintained in Debian. https://tracker.debian.org/pkg/brotli Other Info == webkit2gtk is managed similar to Firefox and Chromium. So far, new releases are pushed to Ubuntu 16.04 LTS and newer as security updates, but the Ubuntu Security Team does not guarantee security support for webkit2gtk. The woff2 MIR is LP: #1742743 We are going to need to backport brotli and woff2 into main as security updates for 16.04 LTS and 17.10. The new version of brotli adds new binary packages (in particular, the C library needed by woff2 and webkit2gtk). brotli has no reverse dependencies in 16.04 and 17.10. (fonttools is a reverse-dependency in 18.04.) brotli has a bizarre build system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brotli/+bug/1737053/+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 1742743] Re: [MIR] woff2
** Changed in: woff2 (Ubuntu) Assignee: (unassigned) => Ubuntu Security Team (ubuntu-security) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to woff2 in Ubuntu. https://bugs.launchpad.net/bugs/1742743 Title: [MIR] woff2 Status in woff2 package in Ubuntu: New Bug description: Availability Built for all supported architectures. In sync with Debian. Rationale = woff2 is a library maintained by Google to convert fonts from TTF to the woff2 format and decompress from woff2 to TTF. The WOFF 2.0 format uses the Brotli compression algorithm to compress fonts suitable for use in CSS @font-face rules. WOFF 2.0 is a W3C Candidate Recommendation. See the brotli MIR at LP: #1737053. brotli and woff2 are libraries that are technically already in main because they are bundled in Firefox and webkit2gtk. The next major stable release of webkit2gtk, 2.20, will be released in March. It drops those 2 bundled libraries. I think our options are basically 1) Bundle those libraries anyway, or 2) Approve this MIR, or 3) Drop support for the WOFF2 format in webkit2gtk Security I assume we want a security review here. https://security-tracker.debian.org/tracker/source-package/woff2 https://launchpad.net/ubuntu/+source/woff2/+cve Quality assurance = - Ubuntu Desktop Bugs is subscribed. - No test suite - No autopkgtests https://bugs.launchpad.net/ubuntu/+source/woff2 https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=woff2 https://github.com/google/woff2/issues Dependencies Only universe binary dependency is brotli (LP: #1737053) Standards compliance 4.1.2, debhelper compat 10, dh7 simple rules Maintenance === Actively maintained: https://github.com/google/woff2 Maintained by the Debian Fonts Team in Debian. It's a small team so it may need co-maintenance help from the Ubuntu Desktop team. Other Info == woff2 was only packaged in Debian and Ubuntu very recently. webkit2gtk is managed similar to Firefox and Chromium. So far, new releases are pushed to Ubuntu 16.04 LTS and newer as security updates, but the Ubuntu Security Team does not guarantee security support for webkit2gtk. We are going to need to backport brotli and woff2 into main as security updates for 16.04 LTS and 17.10. Packaging is at https://salsa.debian.org/fonts-team/woff2/tree/debian/unstable/debian To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/woff2/+bug/1742743/+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 1750030] Re: Report fwupd version in user agent
Thanks Robert. I guess please re-upload for xenial then. ** Changed in: gnome-software (Ubuntu) Status: Triaged => Fix Released -- 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/1750030 Title: Report fwupd version in user agent Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Bug description: [Impact] Some firmware updates fail require a recent version of fwupd to work. Upstream has requested we update the user agent sent in HTTP requests so that they can stop sending firmware to clients that may not work. [Test Case] Check with the fwupd server that the correct user agent is being sent. [Regression Potential] Low. The fix is simply to add to the user-agent string used in HTTP requests. There are some situations that LVFS shouldn't be offering firmware to certain machines. Upstream is going to use the user agent for filtering these firmware offerings and it would be good if gnome-software can report the user agent. The following has been added to the gnome 3.20 tree: https://gitlab.gnome.org/GNOME/gnome-software/commit/9bf4ecef4daa2d31827810d672458768c3c2a2b3 Can this please be backported to xenial? Bionic can already report this as part of 3.26 gnome-software. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750030/+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 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications
mesa is blocked, in addition to this bug, by other issues, and qtbase is unrelated (e.g. migrating qtbase will not regress this further, nor fix this issue). Thus removing block-proposed tag to migrate qtbase update. ** Tags removed: block-proposed -- 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/1749472 Title: mesa 18.0.0 will cause rendering errors in Qt applications Status in mesa package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Status in mesa source package in Bionic: New Status in qtbase-opensource-src source package in Bionic: New Bug description: From: https://bugreports.qt.io/browse/QTBUG-66348 ** extract ** The `QOpenGLShaderProgram` class in Qt can be used to compile and link OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is available, it can cache those shaders on disk (~/.cache/qtshadercache). The i965 driver in Mesa supports this extension since version 18.0.0. When the shader is loaded using the `glProgramBinary` function, OpenGL can refuse it if for example some hardware or software component changed. Mesa refuses binaries that were created by any other build of Mesa (using among other things the build_id of the library). If the shader is refused, Qt should fallback to compiling it from sources, but it incorrectly calls glLinkProgram first. The glLinkProgram succeeds, because it actually links 0 shaders together. That is allowed in OpenGL compatibility profile and the resulting program works as a fixed pipeline. Which of course does not render as expected. This causes rendering errors in Qt applications every time Mesa is updated since version 18.0.0. For example white screen in sddm. This issue was originally reported in openSUSE (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578). ** end extract ** As this potentially effects Qt applications, and could even render display manager login unusable, this should be a blocking bug in mesa and Qt until Qt mitigations patches pass codereview and can be included in Qtbase for 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+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 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications
why is this filed with "block-proposed" tag? Do you intend to prevent mesa from migrating or qt? At the moment this bug is blocking qtbase migration, which is a rebuild against openssl1.1 and I do not see how that change can be related to this bug report. -- 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/1749472 Title: mesa 18.0.0 will cause rendering errors in Qt applications Status in mesa package in Ubuntu: New Status in qtbase-opensource-src package in Ubuntu: New Status in mesa source package in Bionic: New Status in qtbase-opensource-src source package in Bionic: New Bug description: From: https://bugreports.qt.io/browse/QTBUG-66348 ** extract ** The `QOpenGLShaderProgram` class in Qt can be used to compile and link OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is available, it can cache those shaders on disk (~/.cache/qtshadercache). The i965 driver in Mesa supports this extension since version 18.0.0. When the shader is loaded using the `glProgramBinary` function, OpenGL can refuse it if for example some hardware or software component changed. Mesa refuses binaries that were created by any other build of Mesa (using among other things the build_id of the library). If the shader is refused, Qt should fallback to compiling it from sources, but it incorrectly calls glLinkProgram first. The glLinkProgram succeeds, because it actually links 0 shaders together. That is allowed in OpenGL compatibility profile and the resulting program works as a fixed pipeline. Which of course does not render as expected. This causes rendering errors in Qt applications every time Mesa is updated since version 18.0.0. For example white screen in sddm. This issue was originally reported in openSUSE (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578). ** end extract ** As this potentially effects Qt applications, and could even render display manager login unusable, this should be a blocking bug in mesa and Qt until Qt mitigations patches pass codereview and can be included in Qtbase for 18.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+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 1750171] Re: Applications' extension bug - Activity menu vanished in the abyss
** Package changed: linux (Ubuntu) => gnome-desktop (Ubuntu) ** Changed in: gnome-desktop (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1750171 Title: Applications' extension bug - Activity menu vanished in the abyss Status in gnome-desktop package in Ubuntu: New Bug description: Hi, So I downloaded the applications' extension from gnome shell extensions website. The application menu appears on the left side of the top bar but an "error" notification appears beside the extension, plus the menu doesn't work : it is just stuck there and THE MAIN PROBLEM is that I can't bring back the activity button even if I delete the extension, reboot, etc. Anyone experienced the same issue ? I run Ubuntu 17.10 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2509 F pulseaudio ph0enix3059 F pulseaudio /dev/snd/controlC0: gdm2509 F pulseaudio ph0enix3059 F pulseaudio DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2018-02-16 (1 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20180108.1) MachineType: Dell Inc. Inspiron 5737 Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: kvm libvirt _MarkForUpload: True dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 02TKW1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn02TKW1:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.family: 00 dmi.product.name: Inspiron 5737 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-desktop/+bug/1750171/+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 743176] Re: Pink layer on taken screenshots (gnome-screenshot)
Issue present on my system : Ubuntu 17.10 64-bit GNOME Shell 3.26.1 Linux Kernel 4.13.0-32-generic I noticed something interesting and that might resonate with comment #31 above (https://bugs.launchpad.net/ubuntu/+source/gnome- utils/+bug/743176/comments/31). I have two screens, and the problem occurs on only one of my screen. Furthermore, on the screen where the problem occurs, depending if I quickly take the screenshot or not, the pink area will either fully cover the screenshot or for example only 90% of the area if I click-drag and release mouse button quickly... I can provide more information if needed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/743176 Title: Pink layer on taken screenshots (gnome-screenshot) Status in gnome-flashback package in Ubuntu: Confirmed Status in gnome-screenshot package in Ubuntu: Confirmed Status in gnome-utils package in Ubuntu: Fix Released Bug description: Binary package hint: gnome-utils After having taken a screenshot of a part of my screen (gnome- screenshot) which is marked/shown by a pink layer, this pink layer can be seen on the screenshot itself. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-screenshot 2.32.0-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 Date: Sat Mar 26 16:19:48 2011 EcryptfsInUse: Yes InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110316) ProcEnviron: LANGUAGE=de_DE:en LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: gnome-utils UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-flashback/+bug/743176/+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 1750171] [NEW] Applications' extension bug - Activity menu vanished in the abyss
You have been subscribed to a public bug: Hi, So I downloaded the applications' extension from gnome shell extensions website. The application menu appears on the left side of the top bar but an "error" notification appears beside the extension, plus the menu doesn't work : it is just stuck there and THE MAIN PROBLEM is that I can't bring back the activity button even if I delete the extension, reboot, etc. Anyone experienced the same issue ? I run Ubuntu 17.10 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gdm2509 F pulseaudio ph0enix3059 F pulseaudio /dev/snd/controlC0: gdm2509 F pulseaudio ph0enix3059 F pulseaudio DistroRelease: Ubuntu 17.10 EcryptfsInUse: Yes HibernationDevice: RESUME=/dev/mapper/ubuntu--vg-swap_1 InstallationDate: Installed on 2018-02-16 (1 days ago) InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Release amd64 (20180108.1) MachineType: Dell Inc. Inspiron 5737 Package: linux (not installed) ProcEnviron: LANGUAGE=en_CA:en TERM=xterm-256color PATH=(custom, no user) LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=/dev/mapper/hostname--vg-root ro ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.13.0-32-generic N/A linux-backports-modules-4.13.0-32-generic N/A linux-firmware 1.169.3 Tags: artful Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: kvm libvirt _MarkForUpload: True dmi.bios.date: 08/25/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 02TKW1 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A09 dmi.modalias: dmi:bvnDellInc.:bvrA09:bd08/25/2016:svnDellInc.:pnInspiron5737:pvrA09:rvnDellInc.:rn02TKW1:rvrA00:cvnDellInc.:ct8:cvrA09: dmi.product.family: 00 dmi.product.name: Inspiron 5737 dmi.product.version: A09 dmi.sys.vendor: Dell Inc. ** Affects: gnome-desktop (Ubuntu) Importance: Undecided Status: New ** Tags: 17.10 applications apport-collected artful extension ubuntu -- Applications' extension bug - Activity menu vanished in the abyss https://bugs.launchpad.net/bugs/1750171 You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-desktop 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 1734545] Re: Translations not updated from upstream
** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1734545 Title: Translations not updated from upstream Status in gnome-sudoku package in Ubuntu: Confirmed Bug description: The Danish translation of gnome-sudoku lacks many strings as it has not been synchronized with upstream for years: https://translations.launchpad.net/ubuntu/+source/gnome-sudoku Meanwhile gnome-sudoku is and has always been completely translated upstream. Indeed it has been fully translated for every release of GNOME ever since it forked out of gnome-games. Take for example current master: https://l10n.gnome.org/vertimus/gnome-sudoku/master/po/da It seems there are rather grave problems with translation imports in Launchpad. I reported a similar issue recently for util-linux: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1730793 Who knows how many other packages are affected, and in what languages. I think Launchpad translations should be disabled entirely for all source packages - the translations belong upstream, with the project. Thanks to scootergrisen for making me aware of this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1734545/+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 1750610] Re: cupsd crashed with SIGSEGV in ippCopyAttribute()
*** This bug is a duplicate of bug 1750603 *** https://bugs.launchpad.net/bugs/1750603 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 #1750603, 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/1750610/+attachment/5059065/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1750610/+attachment/5059068/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1750610/+attachment/5059077/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1750610/+attachment/5059079/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1750610/+attachment/5059080/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1750610/+attachment/5059081/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1750610/+attachment/5059082/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1750603 ** 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 cups in Ubuntu. https://bugs.launchpad.net/bugs/1750610 Title: cupsd crashed with SIGSEGV in ippCopyAttribute() Status in cups package in Ubuntu: New Bug description: Logged in after desktop being idle for more than 8 hours with crash report ready to send. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: cups-daemon 2.2.6-5 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CupsErrorLog: E [20/Feb/2018:00:09:49 +0200] Filter \"brftopagedbrf\" not found. E [20/Feb/2018:00:09:49 +0200] Filter \"brftopagedbrf\" not found. Date: Tue Feb 20 10:10:43 2018 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2016-10-25 (482 days ago) InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160720) KernLog: Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: Bad file descriptor MachineType: MSI MS-7850 Papersize: a4 PpdFiles: HP-LaserJet-400-MFP-M425dn: HP LaserJet 400 MFP M425 Postscript (recommended) HP_LaserJet_400_MFP_M425dn_195BDA_: HP LaserJet 400 MFP M425dn, driverless, cups-filters 1.20.0 HP_Color_LaserJet_M452dn_B587F1_: Color LaserJet M452dn ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=de66cbe2-16ea-4c60-9081-ed9a0306f7af ro quiet splash vt.handoff=1 ProcEnviron: LANG=en_ZA.UTF-8 LANGUAGE=en_ZA:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed root=UUID=de66cbe2-16ea-4c60-9081-ed9a0306f7af ro quiet splash vt.handoff=1 SegvAnalysis: Segfault happened at: 0x7fe80e9a1db3: addl $0x1,0x38(%rdx) PC (0x7fe80e9a1db3) ok source "$0x1" ok destination "0x38(%rdx)" (0x0038) not located in a known VMA region (needed writable region)! SegvReason: writing NULL VMA Signal: 11 SourcePackage: cups StacktraceTop: ippCopyAttribute () from /usr/lib/x86_64-linux-gnu/libcups.so.2 ?? () ?? () ?? () ?? () Title: cupsd crashed with SIGSEGV in ippCopyAttribute() UpgradeStatus: Upgraded to bionic on 2018-01-24 (26 days ago) UserGroups: dmi.bios.date: 02/16/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V5.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H97 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV5.9:bd02/16/2016:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnH97PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7850 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1750610/+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 1316970] Re: g_dbus memory leak in lrmd
Seyeong, can you check this updated debdiff to verify it still fixes the mem leak? I reverted the free->g_free changes that I previously suggested, as you were correct - the existing code uses chars and normal free() so we should stick with that, i was wrong to suggest using g_free(). Also I removed one of the free() that did not seem correct per the docs. ** Patch added: "lp1316970_trusty_pacemaker_v4.debdiff" https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1316970/+attachment/5059064/+files/lp1316970_trusty_pacemaker_v4.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1316970 Title: g_dbus memory leak in lrmd Status in glib2.0 package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in glib2.0 source package in Trusty: New Status in pacemaker source package in Trusty: In Progress Bug description: [Impact] lrmd daemon with upstart resource has memory leak in Trusty affected to pacemaker 1.1.10. affected to glib2.0 2.40.2-0ubuntu1 Please note that patch for pacemaker is created myself. [Test Case] 1. deploy 3 trusty instance. 2. install corosync, pacemaker, mysql. 3. setting with below info 3.1 corosync.conf, proper setting for 3 node 3.2 crm configure < setup.crm ( which has upstart:mysql setting ) 3.3 monitor lrmd daemon's memory usage [Regression] Restarting daemon after upgrading this pkg will be needed. this patch added NULL check for several parts. prior commit[1] changed file structure. and This change makes user changes usage of upstart:mysql to lsb:mysql. So I added free function myself. This might affect to system. For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building it. [Others] Related commits. [1] commit a7b61e276120184c7586a3217ed3571a982f5017 Author: Andrew BeekhofDate: Fri Aug 23 16:25:35 2013 +1000 Refactor: attrd: Move to its own directory and create a stub for attrd-ng -- $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0 Pacemaker-1.1.11-rc3 $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017 Pacemaker-1.1.11-rc1~168 $ rmadison pacemaker pacemaker | 1.1.10+git20130802-1ubuntu2 | trusty pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates pacemaker | 1.1.14-2ubuntu1 | xenial pacemaker | 1.1.14-2ubuntu1.3 | xenial-security pacemaker | 1.1.14-2ubuntu1.3 | xenial-update pacemaker | 1.1.16-1ubuntu1 | zesty pacemaker | 1.1.16-1ubuntu1 | artful pacemaker | 1.1.18~rc3-1ubuntu1 | bionic -- For glib [1] https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c [2] https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663 [3] https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4 [4] https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a [Original Description] I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy (13.10) and have encountered a memory leak in lrmd. The details of the bug are covered here in this thread (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html) but to summarise, the Pacemaker developers believe the leak is caused by the g_dbus API, the use of which was removed in Pacemaker 1.11. I've also attached the Valgrind output from the run that exposed the issue. Given that this issue affects production stability (a periodic restart of Pacemaker is required), will a version of 1.11 be released for Trusty? (I'm happy to upgrade the OS to Trusty to get it). If not, can you advise which version of the OS will be the first to take 1.11 please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+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 1750570] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
*** This bug is a duplicate of bug 1724439 *** https://bugs.launchpad.net/bugs/1724439 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1750570 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() Status in gnome-shell package in Ubuntu: Confirmed Bug description: I get this when switching off the screen and then back on, when image come back my session has crashed. I try to disable all extensions from gnome-tweak-tool (top bar button in Extensions section) but it did not help. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 20 13:49:04 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1510175942 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.shell' b'favorite-apps' b"['gnome-system-monitor.desktop', 'firefox.desktop', 'google-chrome.desktop', 'filezilla.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'steam.desktop', 'rhythmbox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' InstallationDate: Installed on 2016-10-22 (485 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/media SegvAnalysis: Segfault happened at: 0x7fb7d7d282d4:mov 0x18(%rax),%eax PC (0x7fb7d7d282d4) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() UpgradeStatus: Upgraded to artful on 2018-02-18 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750570/+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 1750601] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1750601/+attachment/5059024/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1750601/+attachment/5059026/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1750601/+attachment/5059029/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1750601/+attachment/5059030/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1750601/+attachment/5059031/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1750601/+attachment/5059032/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1750601/+attachment/5059033/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1750601 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: Release:18.04 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Feb 20 10:45:55 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2018-02-20 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180220) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750601/+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 1750523] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 共有されている '/lib/udev/hwdb.d/20-sane.hwdb' を上書きしようとしています。これはパッケージ libsane1:i386 の他の実体と異なりま
*** This bug is a duplicate of bug 1725928 *** https://bugs.launchpad.net/bugs/1725928 ** This bug has been marked a duplicate of bug 1725928 package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files '/lib/udev/hwdb.d/20-sane.hwdb' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1750523 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 共有されている '/lib/udev/hwdb.d/20-sane.hwdb' を上書きしようとしています。これはパッケージ libsane1:i386 の他の実体と異なります Status in sane-backends package in Ubuntu: New Bug description: abc ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Wed Feb 14 18:57:24 2018 ErrorMessage: 共有されている '/lib/udev/hwdb.d/20-sane.hwdb' を上書きしようとしています。これはパッケージ libsane1:i386 の他の実体と異なります InstallationDate: Installed on 2018-01-30 (21 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64(20171024.1) Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: 共有されている '/lib/udev/hwdb.d/20-sane.hwdb' を上書きしようとしています。これはパッケージ libsane1:i386 の他の実体と異なります UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1750523/+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 1750579] Re: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches
*** This bug is a duplicate of bug 1725928 *** https://bugs.launchpad.net/bugs/1725928 ** This bug has been marked a duplicate of bug 1725928 package libsane1 1.0.27-1~experimental2ubuntu1: multiarch packages with differing files '/lib/udev/hwdb.d/20-sane.hwdb' -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1750579 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Status in sane-backends package in Ubuntu: New Bug description: Vormals nicht ausgewähltes Paket libsane1:i386 wird gewählt. Vorbereitung zum Entpacken von .../133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb ... Entpacken von libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-IODlGE/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist dpkg-deb: Fehler: Unterprozess einfügen wurde durch Signal (Datenübergabe unterbrochen (broken pipe)) getötet Fehler traten auf beim Bearbeiten von: /tmp/apt-dpkg-install-IODlGE/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) frank@NoteB1:~$ sudo apt-get install -f ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Feb 20 15:21:02 2018 ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1750579/+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 1750593] [NEW] Misspelled word in description-en for unity-scopes-runner
Public bug reported: For package "unity-scopes-runner", version "7.1.4+16.04.20180209.1-0ubuntu1", the "Description-en" value is: ``` Description-en: desktop runner for misceallenous scopes The scope runner is a handy tool for wrapping on a desktop the various scoped installed on the system. ``` "misceallenous" should be spelled "miscellaneous". ** Affects: libunity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libunity in Ubuntu. Matching subscriptions: dp-libunity https://bugs.launchpad.net/bugs/1750593 Title: Misspelled word in description-en for unity-scopes-runner Status in libunity package in Ubuntu: New Bug description: For package "unity-scopes-runner", version "7.1.4+16.04.20180209.1-0ubuntu1", the "Description-en" value is: ``` Description-en: desktop runner for misceallenous scopes The scope runner is a handy tool for wrapping on a desktop the various scoped installed on the system. ``` "misceallenous" should be spelled "miscellaneous". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libunity/+bug/1750593/+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 162111]
Oops, copying the microsoft file does not fix the fonts. Sorry for the spam! -- 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/162111 Title: Evince displays math equations incorrectly Status in Evince: Confirmed Status in Wine: New Status in evince package in Ubuntu: Invalid Status in wine1.2 package in Ubuntu: Fix Released Bug description: Binary package hint: evince I am using Evince to view a TexLive compilation of an Optics Express paper that I am trying to submit in DVI format. The paper displays correctly in xdvi, but not in Evince. Evince is much better in general than xdvi, so I would prefer to use it. Evince does not display many parts of my math equations correctly. It seems to be some kind of font issue, but I cannot figure out how to fix it. To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/162111/+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 789479]
Oops, copying the microsoft file does not fix the fonts. Sorry for the spam! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to poppler in Ubuntu. https://bugs.launchpad.net/bugs/789479 Title: Improper encoding of the "Symbol" font Status in Wine: New Status in poppler package in Ubuntu: Invalid Status in wine1.2 package in Ubuntu: Fix Released Status in wine1.3 package in Ubuntu: Fix Released Bug description: The characters 'm' and 'p' are mapped to wrong glphys in the base-14 font "Symbol". This problem has not occurred in maverick. I'm attaching a pdf-file that uses all base-14 fonts without embedding them, and screenshots from maverick and natty. Note the differences in the 5th word in the "Symbol" line. The screenshots were made in TeXworks which is based on poppler-qt4 (evince in natty gives the same result as TeXworks, but I don't have a maverick-screenshot of it at hand). $ lsb_release -rd Description: Ubuntu 11.04 Release: 11.04 $apt-cache policy libpoppler-qt4-3 libpoppler-qt4-3: Installed: 0.16.4-0ubuntu1.1 Candidate: 0.16.4-0ubuntu1.1 Version table: *** 0.16.4-0ubuntu1.1 0 500 http://gd.tuwien.ac.at/opsys/linux/ubuntu/archive/ natty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.16.4-0ubuntu1 0 500 http://gd.tuwien.ac.at/opsys/linux/ubuntu/archive/ natty/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/wine/+bug/789479/+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 1316970] Re: g_dbus memory leak in lrmd
Ok, in that case, can you open a separate lp bug for the glib2.0 memory leak? I think it will be easier to track just fixing the pacemaker mem leaks in this bug, and track fixing the glib2.0 mem leak in a separate bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1316970 Title: g_dbus memory leak in lrmd Status in glib2.0 package in Ubuntu: New Status in pacemaker package in Ubuntu: Fix Released Status in glib2.0 source package in Trusty: New Status in pacemaker source package in Trusty: In Progress Bug description: [Impact] lrmd daemon with upstart resource has memory leak in Trusty affected to pacemaker 1.1.10. affected to glib2.0 2.40.2-0ubuntu1 Please note that patch for pacemaker is created myself. [Test Case] 1. deploy 3 trusty instance. 2. install corosync, pacemaker, mysql. 3. setting with below info 3.1 corosync.conf, proper setting for 3 node 3.2 crm configure < setup.crm ( which has upstart:mysql setting ) 3.3 monitor lrmd daemon's memory usage [Regression] Restarting daemon after upgrading this pkg will be needed. this patch added NULL check for several parts. prior commit[1] changed file structure. and This change makes user changes usage of upstart:mysql to lsb:mysql. So I added free function myself. This might affect to system. For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building it. [Others] Related commits. [1] commit a7b61e276120184c7586a3217ed3571a982f5017 Author: Andrew BeekhofDate: Fri Aug 23 16:25:35 2013 +1000 Refactor: attrd: Move to its own directory and create a stub for attrd-ng -- $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0 Pacemaker-1.1.11-rc3 $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017 Pacemaker-1.1.11-rc1~168 $ rmadison pacemaker pacemaker | 1.1.10+git20130802-1ubuntu2 | trusty pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates pacemaker | 1.1.14-2ubuntu1 | xenial pacemaker | 1.1.14-2ubuntu1.3 | xenial-security pacemaker | 1.1.14-2ubuntu1.3 | xenial-update pacemaker | 1.1.16-1ubuntu1 | zesty pacemaker | 1.1.16-1ubuntu1 | artful pacemaker | 1.1.18~rc3-1ubuntu1 | bionic -- For glib [1] https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c [2] https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663 [3] https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4 [4] https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a [Original Description] I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy (13.10) and have encountered a memory leak in lrmd. The details of the bug are covered here in this thread (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html) but to summarise, the Pacemaker developers believe the leak is caused by the g_dbus API, the use of which was removed in Pacemaker 1.11. I've also attached the Valgrind output from the run that exposed the issue. Given that this issue affects production stability (a periodic restart of Pacemaker is required), will a version of 1.11 be released for Trusty? (I'm happy to upgrade the OS to Trusty to get it). If not, can you advise which version of the OS will be the first to take 1.11 please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+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 1750579] [NEW] package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welche
Public bug reported: Vormals nicht ausgewähltes Paket libsane1:i386 wird gewählt. Vorbereitung zum Entpacken von .../133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb ... Entpacken von libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-IODlGE/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist dpkg-deb: Fehler: Unterprozess einfügen wurde durch Signal (Datenübergabe unterbrochen (broken pipe)) getötet Fehler traten auf beim Bearbeiten von: /tmp/apt-dpkg-install-IODlGE/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) frank@NoteB1:~$ sudo apt-get install -f ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Feb 20 15:21:02 2018 ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: sane-backends (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package artful -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to sane-backends in Ubuntu. https://bugs.launchpad.net/bugs/1750579 Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Status in sane-backends package in Ubuntu: New Bug description: Vormals nicht ausgewähltes Paket libsane1:i386 wird gewählt. Vorbereitung zum Entpacken von .../133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb ... Entpacken von libsane1:i386 (1.0.27-1~experimental2ubuntu2.1) ... dpkg: Fehler beim Bearbeiten des Archivs /tmp/apt-dpkg-install-IODlGE/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb (--unpack): Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist dpkg-deb: Fehler: Unterprozess einfügen wurde durch Signal (Datenübergabe unterbrochen (broken pipe)) getötet Fehler traten auf beim Bearbeiten von: /tmp/apt-dpkg-install-IODlGE/133-libsane1_1.0.27-1~experimental2ubuntu2.1_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) frank@NoteB1:~$ sudo apt-get install -f ProblemType: Package DistroRelease: Ubuntu 17.10 Package: libsane1 1.0.27-1~experimental2ubuntu2.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Tue Feb 20 15:21:02 2018 ErrorMessage: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 3.6.3-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 2.7.14-2ubuntu1 RelatedPackageVersions: dpkg 1.18.24ubuntu1 apt 1.5.1 SourcePackage: sane-backends Title: package libsane1 1.0.27-1~experimental2ubuntu2.1 failed to install/upgrade: Versuch, gemeinsam benutztes »/lib/udev/hwdb.d/20-sane.hwdb« zu überschreiben, welches verschieden von anderen Instanzen des Paketes libsane1:i386 ist UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1750579/+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 1750403] Re: Live Session - Increased memory usage with preinstalled snap (fails to start with - gnome-session timeout)
I noticed that core 3887 is on the image while 4017 is published to stable, a theory is that the refresh to stable happens during boot and consumes lot of resources leading to memory starvation or timeouts. ** Changed in: gnome-session (Ubuntu) Importance: Medium => High ** Package changed: gnome-session (Ubuntu) => casper (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1750403 Title: Live Session - Increased memory usage with preinstalled snap (fails to start with - gnome-session timeout) Status in casper package in Ubuntu: Confirmed Bug description: Ubuntu Desktop Bionic 20180219 on VM The session fails to start. There is the following message in the journal: Feb 19 16:01:54 ubuntu gnome-session[1469]: gnome-session-binary[1469]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Feb 19 16:01:54 ubuntu gnome-session-binary[1469]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Feb 19 16:01:54 ubuntu gnome-session-binary[1469]: Unrecoverable failure in required component org.gnome.Shell.desktop Feb 19 16:01:54 ubuntu gnome-session[1469]: gnome-session-binary[1469]: CRITICAL: We failed, but the fail whale is dead. Sorry Feb 19 16:01:54 ubuntu gnome-session-binary[1469]: CRITICAL: We failed, but the fail whale is dead. Sorry Feb 19 16:01:54 ubuntu at-spi-bus-launcher[1582]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Feb 19 16:01:54 ubuntu at-spi-bus-launcher[1582]: after 21 requests (21 known processed) with 0 events remaining. On hardware boot time is slow but there is no timeout. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 17:04:42 2018 InstallationDate: Installed on 2013-09-03 (1629 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-01-26 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1750403/+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 1734545] Re: Translations not updated from upstream
Many of the .po files are huge, since they include strings from gnome- games, and many of them have not been merged with the template for years. So one idea is to upload with .po files which are consistent with po/gnome-sudoku.pot. Attached please find a patch which could be used for the purpose. ** Patch added: "merge-po-files.patch.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1734545/+attachment/5058929/+files/merge-po-files.patch.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1734545 Title: Translations not updated from upstream Status in gnome-sudoku package in Ubuntu: Confirmed Bug description: The Danish translation of gnome-sudoku lacks many strings as it has not been synchronized with upstream for years: https://translations.launchpad.net/ubuntu/+source/gnome-sudoku Meanwhile gnome-sudoku is and has always been completely translated upstream. Indeed it has been fully translated for every release of GNOME ever since it forked out of gnome-games. Take for example current master: https://l10n.gnome.org/vertimus/gnome-sudoku/master/po/da It seems there are rather grave problems with translation imports in Launchpad. I reported a similar issue recently for util-linux: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1730793 Who knows how many other packages are affected, and in what languages. I think Launchpad translations should be disabled entirely for all source packages - the translations belong upstream, with the project. Thanks to scootergrisen for making me aware of this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1734545/+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 1675705] Re: unknown file system type zfs_member
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: udisks2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/1675705 Title: unknown file system type zfs_member Status in udisks2 package in Ubuntu: Confirmed Bug description: Hi, I'm happy to see that there is some progress about automounting removable devices with zfs, but when I plug in a pendrive with zfs, I still get the error message Error mounting /dev/dm-2 at /media/danisch/sync2: Command-line `mount -t "zfs_member" -o "uhelper=udisks2,nodev,nosuid" "/dev/dm-2" "/media/danisch/sync2"' exited with non-zero exit status 32: mount: unknown filesystem type 'zfs_member' ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: mount 2.28.2-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 24 10:20:03 2017 InstallationDate: Installed on 2016-04-22 (335 days ago) InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420) SourcePackage: util-linux UpgradeStatus: Upgraded to yakkety on 2016-10-17 (158 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1675705/+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 1750558] Re: gnome-software crashed with SIGSEGV in __strlen_avx2()
Thanks for your report. Are you able to reproduce this crash and could you provide the steps to do it? Thanks. ** Changed in: gnome-software (Ubuntu) Status: New => Incomplete -- 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/1750558 Title: gnome-software crashed with SIGSEGV in __strlen_avx2() Status in gnome-software package in Ubuntu: Incomplete Bug description: from lxqt? ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.27.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Date: Tue Feb 20 12:54:36 2018 ExecutablePath: /usr/bin/gnome-software InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.27.90-1ubuntu1 ProcCmdline: /usr/bin/gnome-software --local-filename=/tmp/mozilla_frank0/gdm3setup-20141021-1.deb ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=de_DE.UTF-8 LANGUAGE= SegvAnalysis: Segfault happened at: 0x7f43bc20c191 <__strlen_avx2+17>: vpcmpeqb (%rdi),%ymm0,%ymm1 PC (0x7f43bc20c191) ok source "(%rdi)" (0x0004) not located in a known VMA region (needed readable region)! destination "%ymm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:62 _IO_vfprintf_internal (s=s@entry=0x7ffe9de6e2f0, format=format@entry=0x7f43bfd21211 , ap=ap@entry=0x7ffe9de6e460) at vfprintf.c:1643 __GI___vasprintf_chk (result_ptr=0x7ffe9de6e440, flags=1, format=0x7f43bfd21211 , args=0x7ffe9de6e460) at vasprintf_chk.c:66 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-software crashed with SIGSEGV in __strlen_avx2() UpgradeStatus: Upgraded to bionic on 2017-12-04 (78 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750558/+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 1750558] Re: gnome-software crashed with SIGSEGV in __strlen_avx2()
** Information type changed from Private to Public -- 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/1750558 Title: gnome-software crashed with SIGSEGV in __strlen_avx2() Status in gnome-software package in Ubuntu: New Bug description: from lxqt? ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-software 3.27.90-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: Date: Tue Feb 20 12:54:36 2018 ExecutablePath: /usr/bin/gnome-software InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.27.90-1ubuntu1 ProcCmdline: /usr/bin/gnome-software --local-filename=/tmp/mozilla_frank0/gdm3setup-20141021-1.deb ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=de_DE.UTF-8 LANGUAGE= SegvAnalysis: Segfault happened at: 0x7f43bc20c191 <__strlen_avx2+17>: vpcmpeqb (%rdi),%ymm0,%ymm1 PC (0x7f43bc20c191) ok source "(%rdi)" (0x0004) not located in a known VMA region (needed readable region)! destination "%ymm0" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-software StacktraceTop: __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:62 _IO_vfprintf_internal (s=s@entry=0x7ffe9de6e2f0, format=format@entry=0x7f43bfd21211 , ap=ap@entry=0x7ffe9de6e460) at vfprintf.c:1643 __GI___vasprintf_chk (result_ptr=0x7ffe9de6e440, flags=1, format=0x7f43bfd21211 , args=0x7ffe9de6e460) at vasprintf_chk.c:66 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-software crashed with SIGSEGV in __strlen_avx2() UpgradeStatus: Upgraded to bionic on 2017-12-04 (78 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750558/+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 1734545] Re: Translations not updated from upstream
** Changed in: gnome-sudoku (Ubuntu) Status: Fix Released => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-sudoku in Ubuntu. https://bugs.launchpad.net/bugs/1734545 Title: Translations not updated from upstream Status in gnome-sudoku package in Ubuntu: Confirmed Bug description: The Danish translation of gnome-sudoku lacks many strings as it has not been synchronized with upstream for years: https://translations.launchpad.net/ubuntu/+source/gnome-sudoku Meanwhile gnome-sudoku is and has always been completely translated upstream. Indeed it has been fully translated for every release of GNOME ever since it forked out of gnome-games. Take for example current master: https://l10n.gnome.org/vertimus/gnome-sudoku/master/po/da It seems there are rather grave problems with translation imports in Launchpad. I reported a similar issue recently for util-linux: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1730793 Who knows how many other packages are affected, and in what languages. I think Launchpad translations should be disabled entirely for all source packages - the translations belong upstream, with the project. Thanks to scootergrisen for making me aware of this problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-sudoku/+bug/1734545/+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 1750570] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
*** This bug is a duplicate of bug 1724439 *** https://bugs.launchpad.net/bugs/1724439 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 #1724439, 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/1750570/+attachment/5058893/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1750570/+attachment/5058895/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1750570/+attachment/5058899/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1750570/+attachment/5058900/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1750570/+attachment/5058901/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1750570/+attachment/5058902/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1750570/+attachment/5058903/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1724439 gnome-shell crashed with SIGSEGV in meta_window_get_monitor() from ffi_call_unix64() from ffi_call() from gjs_invoke_c_function() from function_call() ** 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/1750570 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() Status in gnome-shell package in Ubuntu: New Bug description: I get this when switching off the screen and then back on, when image come back my session has crashed. I try to disable all extensions from gnome-tweak-tool (top bar button in Extensions section) but it did not help. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.26.2-0ubuntu0.1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 20 13:49:04 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell ExecutableTimestamp: 1510175942 GsettingsChanges: b'org.gnome.shell' b'disable-user-extensions' b'true' b'org.gnome.shell' b'favorite-apps' b"['gnome-system-monitor.desktop', 'firefox.desktop', 'google-chrome.desktop', 'filezilla.desktop', 'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 'steam.desktop', 'rhythmbox.desktop']" b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'text-scaling-factor' b'1.25' InstallationDate: Installed on 2016-10-22 (485 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcCmdline: /usr/bin/gnome-shell ProcCwd: /home/media SegvAnalysis: Segfault happened at: 0x7fb7d7d282d4:mov 0x18(%rax),%eax PC (0x7fb7d7d282d4) ok source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: meta_window_get_monitor () from /usr/lib/x86_64-linux-gnu/libmutter-1.so.0 ffi_call_unix64 () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ffi_call () from /usr/lib/x86_64-linux-gnu/libffi.so.6 ?? () from /usr/lib/libgjs.so.0 ?? () from /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() UpgradeStatus: Upgraded to artful on 2018-02-18 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750570/+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 1750572] Re: Xwayland crashed with SIGABRT in OsAbort()
*** This bug is a duplicate of bug 1731911 *** https://bugs.launchpad.net/bugs/1731911 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 #1731911, 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/1750572/+attachment/5058905/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1750572/+attachment/5058908/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1750572/+attachment/5058917/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1750572/+attachment/5058919/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1750572/+attachment/5058920/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1750572/+attachment/5058921/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1750572/+attachment/5058922/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1731911 Xwayland crashed with SIGABRT in OsAbort() from AbortServer() from FatalError() from xwl_read_events() from ospoll_wait() ** 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/1750572 Title: Xwayland crashed with SIGABRT in OsAbort() Status in xorg-server package in Ubuntu: New Bug description: I get this when switching off the screen and then back on, when image come back my session has crashed. I try to disable all extensions from gnome-tweak-tool (top bar button in Extensions section) but it did not help. ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: xwayland 2:1.19.5-0ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Feb 20 13:49:54 2018 DistUpgraded: 2018-02-18 19:38:05,474 DEBUG icon theme changed, re-reading DistroCodename: artful DistroVariant: ubuntu ExecutablePath: /usr/bin/Xwayland ExecutableTimestamp: 1508068793 GraphicsCard: Intel Corporation Device [8086:5a85] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:2067] InstallationDate: Installed on 2016-10-22 (485 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) Lsusb: Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc. ASM1051E SATA 6Gb/s bridge, ASM1053E SATA 6Gb/s bridge, ASM1153 SATA 3Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0aa7 Intel Corp. Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd 6 ProcCwd: /home/media ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=6da0fb62-a60c-4a4d-8f9a-e26a760520c9 ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: xorg-server StacktraceTop: OsAbort () ?? () FatalError () ?? () ?? () Title: Xwayland crashed with SIGABRT in OsAbort() UpgradeStatus: Upgraded to artful on 2018-02-18 (1 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 03/10/2017 dmi.bios.vendor: Intel Corp. dmi.bios.version: AYAPLCEL.86A.0038.2017.0310.1633 dmi.board.name: NUC6CAYB dmi.board.vendor: Intel Corporation dmi.board.version: J23203-403 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrAYAPLCEL.86A.0038.2017.0310.1633:bd03/10/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC6CAYB:rvrJ23203-403:cvn:ct3:cvr: version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1 version.libdrm2: libdrm2 2.4.83-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
[Desktop-packages] [Bug 1721428] Re: Artful (17.10) Session logout after screen turned off
I reproduce the same thing with a pretty standard Ubuntu 17.10 (but upgraded from 17.04) in which I did not installed any extension (which mean I only have the system Ubuntu ones: "Ubuntu AppIndicators" and "Ubuntu Dock"). I wanted to try to disable those extension to check but it does not seems to be possible (at least not from https://extensions.gnome.org/local/). My system is a Nuc Arches Canyon Nuc6cayh. -- 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/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in Nouveau Xorg driver: New Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1747802] Re: Snapped applications launched from command line aren't properly matched
@3v1n0 can you also test the artful version? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bamf in Ubuntu. https://bugs.launchpad.net/bugs/1747802 Title: Snapped applications launched from command line aren't properly matched Status in BAMF: Fix Committed Status in bamf package in Ubuntu: Fix Released Status in bamf source package in Xenial: Fix Committed Status in bamf source package in Artful: Fix Committed Bug description: [Impact] Snapped applications non launched from their desktop file aren't properly matched by BAMF. [Test case] From terminal: 1. snap install qml-hello-world 2. qml-hello-world The application should start and the icon in the unity launcher should contain a Qt logo. [Regression Potential] Application with security profile might get a wrong desktop file. To manage notifications about this bug go to: https://bugs.launchpad.net/bamf/+bug/1747802/+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 1750352] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1750352/+attachment/5058892/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1750352 Title: gnome-shell freeze on key press while high CPU load Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug happens randomly (once an hour), on keyboard input in different apps, ex Firefox address bar, Alfred launcher or Gnome Overview. I could not find steps to reproduce (tried reducing keyboard interval and repeated keypress following STRs from #1731420 but it did not freeze, though CPU use increased). System is completely frozen, cannot switch to TTY, but music continues to play. Sometimes it logs out but most of the time I have to force reboot by long pressing the shutdown key. syslog show message : "Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!" multiple times. Looks similar to bug https://bugzilla.gnome.org/show_bug.cgi?id=777693 Ubuntu 17.10 with Gnome session on wayland. Gnome-Shell 3.26.2-0ubuntu0.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: lightdm DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-28 (83 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip i2c input libvirt lpadmin plugdev sambashare sudo wireshark www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750352/+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 1750352] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1750352/+attachment/5058891/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1750352 Title: gnome-shell freeze on key press while high CPU load Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug happens randomly (once an hour), on keyboard input in different apps, ex Firefox address bar, Alfred launcher or Gnome Overview. I could not find steps to reproduce (tried reducing keyboard interval and repeated keypress following STRs from #1731420 but it did not freeze, though CPU use increased). System is completely frozen, cannot switch to TTY, but music continues to play. Sometimes it logs out but most of the time I have to force reboot by long pressing the shutdown key. syslog show message : "Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!" multiple times. Looks similar to bug https://bugzilla.gnome.org/show_bug.cgi?id=777693 Ubuntu 17.10 with Gnome session on wayland. Gnome-Shell 3.26.2-0ubuntu0.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: lightdm DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-28 (83 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip i2c input libvirt lpadmin plugdev sambashare sudo wireshark www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750352/+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 1721428] Re: Artful (17.10) Session logout after screen turned off
Here are the reported issues (thanks @jrstravino for the apport fix to send them to the right place): * https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750570 * https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1750572 -- 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/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in Nouveau Xorg driver: New Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1552792] Re: gnome software leaves dependencies installed
I don't have the ETH anymore, but I will send $600 via PayPal to the one who fixes this issue. -- 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/1552792 Title: gnome software leaves dependencies installed Status in GNOME Software: Invalid Status in Release Notes for Ubuntu: Fix Released Status in aptdaemon package in Ubuntu: New Status in gnome-software package in Ubuntu: Triaged Status in packagekit package in Ubuntu: New Bug description: Using gnome software (or another PackageKit or aptdaemon based UI) to install an application - removal of that package leaves behind dependencies Installing an application with ubuntu software centre only leaves behind config files (seen in synaptic labelled for complete removal). After installing and then removing alarm clock with USC - sudo apt-get autoremove [sudo] password for wolf: Reading package lists... Done Building dependency tree Reading state information... Done 0 to upgrade, 0 to newly install, 0 to remove and 1 not to upgrade. After cleaning up and then reinstalling with gnome software, followed by the removal sudo apt-get autoremove Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED libappindicator1 libindicator7 0 to upgrade, 0 to newly install, 2 to remove and 1 not to upgrade. After this operation, 184 kB disk space will be freed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: gnome-software 3.19.92~git20160303.26a927d-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3 Uname: Linux 4.4.0-10-generic x86_64 ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: XFCE Date: Thu Mar 3 16:23:45 2016 InstallationDate: Installed on 2015-10-29 (126 days ago) InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151029) SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1552792/+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 1741027] Re: screen sharing panels abort using an unexistant vino gsettings key
That sounds a better solution indeed, closing the vino part of the bug ** Changed in: vino (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: screen sharing panels abort using an unexistant vino gsettings key Status in unity-control-center package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Status in vino package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20171225-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Specifically, the error report "Settings schema 'org.gnome.Vino' does not contain a key named 'enabled' " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+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 1721428] Re: Artful (17.10) Session logout after screen turned off
I used ubuntu-bug but no idea what issue has been created from it since it's not indicating anything. I just got new .upload and uploaded files added to /var/crash/. -- 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/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in Nouveau Xorg driver: New Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1750403] Re: Live Session - Increased memory usage with preinstalled snap (fails to start with - gnome-session timeout)
Increasing the memory of the guest to 2GB fixes the problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1750403 Title: Live Session - Increased memory usage with preinstalled snap (fails to start with - gnome-session timeout) Status in gnome-session package in Ubuntu: Confirmed Bug description: Ubuntu Desktop Bionic 20180219 on VM The session fails to start. There is the following message in the journal: Feb 19 16:01:54 ubuntu gnome-session[1469]: gnome-session-binary[1469]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Feb 19 16:01:54 ubuntu gnome-session-binary[1469]: WARNING: Application 'org.gnome.Shell.desktop' failed to register before timeout Feb 19 16:01:54 ubuntu gnome-session-binary[1469]: Unrecoverable failure in required component org.gnome.Shell.desktop Feb 19 16:01:54 ubuntu gnome-session[1469]: gnome-session-binary[1469]: CRITICAL: We failed, but the fail whale is dead. Sorry Feb 19 16:01:54 ubuntu gnome-session-binary[1469]: CRITICAL: We failed, but the fail whale is dead. Sorry Feb 19 16:01:54 ubuntu at-spi-bus-launcher[1582]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0" Feb 19 16:01:54 ubuntu at-spi-bus-launcher[1582]: after 21 requests (21 known processed) with 0 events remaining. On hardware boot time is slow but there is no timeout. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-session (not installed) ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 19 17:04:42 2018 InstallationDate: Installed on 2013-09-03 (1629 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902) ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: Upgraded to bionic on 2018-01-26 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1750403/+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 1750352] Re: gnome-shell freeze on key press while high CPU load
apport information ** Tags added: apport-collected artful wayland-session ** Description changed: This bug happens randomly (once an hour), on keyboard input in different apps, ex Firefox address bar, Alfred launcher or Gnome Overview. I could not find steps to reproduce (tried reducing keyboard interval and repeated keypress following STRs from #1731420 but it did not freeze, though CPU use increased). System is completely frozen, cannot switch to TTY, but music continues to play. Sometimes it logs out but most of the time I have to force reboot by long pressing the shutdown key. syslog show message : "Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!" multiple times. Looks similar to bug https://bugzilla.gnome.org/show_bug.cgi?id=777693 Ubuntu 17.10 with Gnome session on wayland. Gnome-Shell 3.26.2-0ubuntu0.1 + --- + ApportVersion: 2.20.7-0ubuntu3.7 + Architecture: amd64 + CurrentDesktop: GNOME + DisplayManager: lightdm + DistroRelease: Ubuntu 17.10 + InstallationDate: Installed on 2017-11-28 (83 days ago) + InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) + Package: gnome-shell 3.26.2-0ubuntu0.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 + Tags: artful wayland-session + Uname: Linux 4.13.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip i2c input libvirt lpadmin plugdev sambashare sudo wireshark www-data + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1750352/+attachment/505/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1750352 Title: gnome-shell freeze on key press while high CPU load Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug happens randomly (once an hour), on keyboard input in different apps, ex Firefox address bar, Alfred launcher or Gnome Overview. I could not find steps to reproduce (tried reducing keyboard interval and repeated keypress following STRs from #1731420 but it did not freeze, though CPU use increased). System is completely frozen, cannot switch to TTY, but music continues to play. Sometimes it logs out but most of the time I have to force reboot by long pressing the shutdown key. syslog show message : "Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!" multiple times. Looks similar to bug https://bugzilla.gnome.org/show_bug.cgi?id=777693 Ubuntu 17.10 with Gnome session on wayland. Gnome-Shell 3.26.2-0ubuntu0.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: lightdm DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-28 (83 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip i2c input libvirt lpadmin plugdev sambashare sudo wireshark www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750352/+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 1750352] JournalErrors.txt
apport information ** Attachment added: "JournalErrors.txt" https://bugs.launchpad.net/bugs/1750352/+attachment/5058890/+files/JournalErrors.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1750352 Title: gnome-shell freeze on key press while high CPU load Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug happens randomly (once an hour), on keyboard input in different apps, ex Firefox address bar, Alfred launcher or Gnome Overview. I could not find steps to reproduce (tried reducing keyboard interval and repeated keypress following STRs from #1731420 but it did not freeze, though CPU use increased). System is completely frozen, cannot switch to TTY, but music continues to play. Sometimes it logs out but most of the time I have to force reboot by long pressing the shutdown key. syslog show message : "Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!" multiple times. Looks similar to bug https://bugzilla.gnome.org/show_bug.cgi?id=777693 Ubuntu 17.10 with Gnome session on wayland. Gnome-Shell 3.26.2-0ubuntu0.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: lightdm DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-28 (83 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip i2c input libvirt lpadmin plugdev sambashare sudo wireshark www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750352/+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 1750352] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1750352/+attachment/5058889/+files/GsettingsChanges.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1750352 Title: gnome-shell freeze on key press while high CPU load Status in gnome-shell package in Ubuntu: Incomplete Bug description: This bug happens randomly (once an hour), on keyboard input in different apps, ex Firefox address bar, Alfred launcher or Gnome Overview. I could not find steps to reproduce (tried reducing keyboard interval and repeated keypress following STRs from #1731420 but it did not freeze, though CPU use increased). System is completely frozen, cannot switch to TTY, but music continues to play. Sometimes it logs out but most of the time I have to force reboot by long pressing the shutdown key. syslog show message : "Key repeat discarded, Wayland compositor doesn't seem to be processing events fast enough!" multiple times. Looks similar to bug https://bugzilla.gnome.org/show_bug.cgi?id=777693 Ubuntu 17.10 with Gnome session on wayland. Gnome-Shell 3.26.2-0ubuntu0.1 --- ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: GNOME DisplayManager: lightdm DistroRelease: Ubuntu 17.10 InstallationDate: Installed on 2017-11-28 (83 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Package: gnome-shell 3.26.2-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Tags: artful wayland-session Uname: Linux 4.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip i2c input libvirt lpadmin plugdev sambashare sudo wireshark www-data _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750352/+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 1741027] Re: screen sharing panels abort using an unexistant vino gsettings key
No. Patching vino is not a good idea. I am porting sharing-panel from g-c-c. ** Also affects: unity-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-control-center (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) ** Changed in: unity-settings-daemon (Ubuntu) Assignee: (unassigned) => Khurshid Alam (khurshid-alam) ** Changed in: vino (Ubuntu) Assignee: Khurshid Alam (khurshid-alam) => (unassigned) ** Changed in: unity-settings-daemon (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/1741027 Title: screen sharing panels abort using an unexistant vino gsettings key Status in unity-control-center package in Ubuntu: Confirmed Status in unity-settings-daemon package in Ubuntu: Confirmed Status in vino package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-control-center. This problem was most recently seen with package version 15.04.0+17.10.20171225-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/be6d095e2145d77c79a6e47e17c94dfe70bcaa0a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. Specifically, the error report "Settings schema 'org.gnome.Vino' does not contain a key named 'enabled' " To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1741027/+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 1721428] Re: Artful (17.10) Session logout after screen turned off
OK so it's actually a bit random actually. Even with all extensions disabled in gnome-tweak-tool the session sometimes crash and sometimes stay. -- 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/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in Nouveau Xorg driver: New Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1721428] Re: Artful (17.10) Session logout after screen turned off
For some weird reason gnome-tweak-tool is telling me that Ubuntu extensions are not enabled but I guess it's a visual bug since I don't have the problem anymore if I use the top bar button to disable all extensions at once. So it definitely seems to be in one of the Ubuntu extensions but no idea which once since I can't disable them separately. -- 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/1721428 Title: Artful (17.10) Session logout after screen turned off Status in GNOME Shell: Unknown Status in Nouveau Xorg driver: New Status in gnome-shell package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: Whenever I turn off my screen, the computer (a desktop PC) logs me out of my session. Here is a discussion thread with users of similar issue: https://ubuntuforums.org/showthread.php?t=2372388=13694312=1#post13694312 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1721428/+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 1750559] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
*** This bug is a duplicate of bug 1748450 *** https://bugs.launchpad.net/bugs/1748450 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 #1748450, 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/1750559/+attachment/5058865/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1750559/+attachment/5058867/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1750559/+attachment/5058870/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1750559/+attachment/5058871/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1750559/+attachment/5058872/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1750559/+attachment/5058873/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1750559/+attachment/5058874/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1748450 gnome-shell crashed with SIGTRAP in _g_log_abort() from g_log_default_handler() from default_log_handler(message="Connection to xwayland lost") from g_logv() from g_log() from ** 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/1750559 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: New Bug description: In lxqt? ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME-Greeter:GNOME Date: Tue Feb 20 12:24:56 2018 DisplayManager: sddm ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: ProcCmdline: /usr/bin/gnome-shell ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: gnome-shell StacktraceTop: ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log () from /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 bionic on 2017-12-04 (78 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1750559/+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 1630860] Re: [HDA-Intel - HDA Intel PCH, playback] Playback problem
same here ubuntu 16.04 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1630860 Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Debian: New Bug description: Lenovo Thinkpad P50 with docking station Issues: Headphone jack on station not detected; no sound (works without docking station) Issues: Sound via HDMI on station not detected; no sound (works without docking station) Since all outputs are routed via the Thunderbolt chip, my guess is that it's related to the pin setup (lenovo-dock) in Alsa. Without the dock, everything works, headphone/mic jack on the P50 itself is hotplug (switches from speaker to headphones right away). Screenshots (with and without docking station) attached. Thanks and LG, Wolfgang ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-38.57~14.04.1-generic 4.4.19 Uname: Linux 4.4.0-38-generic x86_64 NonfreeKernelModules: symap_custom_dkms_x86_64 nvidia ApportVersion: 2.14.1-0ubuntu3.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wjl2943 F pulseaudio /dev/snd/controlC0: wjl2943 F pulseaudio CurrentDesktop: Unity Date: Wed Oct 5 14:14:02 2016 InstallationDate: Installed on 2016-09-10 (24 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: HDA NVidia - HDA NVidia Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/10/2016 dmi.bios.vendor: LENOVO dmi.bios.version: N1EET52W (1.26 ) dmi.board.asset.tag: Not Available dmi.board.name: 20EQS1EH0B dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1EET52W(1.26):bd05/10/2016:svnLENOVO:pn20EQS1EH0B:pvrThinkPadP50:rvnLENOVO:rn20EQS1EH0B:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20EQS1EH0B dmi.product.version: ThinkPad P50 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa.base.conf: 2016-10-04T12:48:36.270399 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1630860/+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 1733557] Re: Login screen showing Authentication Failure Switch to greeter...
Appears on 16.04.3 after updating Unity to latest packages. Also on 17.10 with installed unity-session. For me, this issue appears after switching to another user. Steps to reproduce (must be more than one local users on system, eg. "bob", "alice"): 1. Login under bob. 2. Via upper-right menu switch to "alice". 3. On greeter screen setect "alice", login under alice. 4. Logout, return to greeter screen. 5. Select bob (already logged in). Enter password. 6. Lock screen. Issue appeared. Issue appeared on every screen lock. Messages in syslog: Jan 6 17:15:33 eugene-Lenovo-Flex-2-14 systemd[1411]: Stopped Backing Service for the Unity Panel in Lockscreen mode. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 1 time. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 2 time. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Starting Backing Service for the Unity Panel in Lockscreen mode... Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.glib.dbus.proxy GLibDBusProxy.cpp:487 Calling method "EmitEvent" on object path: "/com/ubuntu/Upstart" failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name com.canonical.Unity.Test.Upstart was not provided by any .service files Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd-prestart-check[3804]: grep: /usr/share/gnome-session/sessions/ubuntu.session: Нет такого файла или каталога Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Started Backing Service for the Unity Panel in Lockscreen mode. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 systemd[1411]: Reached target A target that, when running, represents the screen being locked. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 3 time. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 4 time. Jan 6 17:15:42 eugene-Lenovo-Flex-2-14 compiz[1877]: WARN 2018-01-06 17:15:42 unity.lockscreen UserPromptView.cpp:500 Failed to start the authentication process. Retrying for 5 time. ** Summary changed: - Login screen showing Authentication Failed Switch to greeter... + Login screen showing Authentication Failure Switch to greeter... ** Package changed: lightdm (Ubuntu) => unity (Ubuntu) ** Tags added: 16.04 17.10 unity xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1733557 Title: Login screen showing Authentication Failure Switch to greeter... Status in unity package in Ubuntu: Confirmed Bug description: When I lock my machine, the login screen shows my current user with the message: "Authentication Failed" ..and in the position when the password normally exists, the option "Switch to greeter..." ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-control-center 1:3.26.1-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Nov 21 10:28:47 2017 InstallationDate: Installed on 2017-04-17 (217 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to artful on 2017-10-23 (29 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1733557/+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 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial
We have made efforts to improve Bluetooth audio support over the past year, but most of the fixes are in Ubuntu 17.10 and 18.04 only. We've backported some to 16.04 but unfortunately can't backport everything. Please try 17.10/18.04 and if you have any ongoing issues then open a new bug. -- 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/1549163 Title: Bluetooth headset HSP/HFP mode not working in Xenial Status in HWE Next: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: Using the 2/14 Xenial daily build, paired bluetooth headsets' do not work in HSP/HFP mode. [Steps to reproduce] 1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build 2. In the laptop, go to sound settings > output tab > try switching mode to HSP/HFP mode 3. Press the "test sound" button and try playing sound 4. Go to the input tab and check if bluetooth headset mic is listed [Expected result] After step 3, a window for mono audio test should pop up After step 4, the input tab should list a bluetooth headset mic device [Actual result] After step 3, the window that pops up is for stereo (A2DP) audio test After step 4, the input tab does not list any bluetooth headset mic [Details] BT wireless module: * Intel 3160 BT headset: * Jabra CLI Xenial: 2/14 daily build: * Kernel: 4.4.0-6 * bluez: 5.36-0ubuntu1 * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1 * pulseaudio: 1:8.0-0ubuntu2 * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2 [Note] Also double checked with same set of hardware, but with 15.10 installed. Bluetooth headset HSP/HFP mode worked correctly in 15.10. 15.10 details: * kernel: 4.2.0-19 * bluez: 5.35-0ubuntu2 * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1 * pulseaudio: 1:6.0-0ubuntu13 * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1549163/+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 1750548] [NEW] Need some way to show multiple banners
Public bug reported: While GNOME Software allows one banner to be shown, it would be great to have multiple banners in rotation. Having multiple banners would enable us to rotate around a bunch of promoted applications rather than have one application stuck there for a while. A discussion was had on the forum. https://forum.snapcraft.io/t /supporting-multiple-featured-snaps-in-gnome-software/3124/7 ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New -- 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/1750548 Title: Need some way to show multiple banners Status in gnome-software package in Ubuntu: New Bug description: While GNOME Software allows one banner to be shown, it would be great to have multiple banners in rotation. Having multiple banners would enable us to rotate around a bunch of promoted applications rather than have one application stuck there for a while. A discussion was had on the forum. https://forum.snapcraft.io/t /supporting-multiple-featured-snaps-in-gnome-software/3124/7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750548/+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 1750098] Re: Ubuntu software shows snaps as installed even if it failed to install
** Description changed: - As statet on https://forum.snapcraft.io/t/ubuntu-software-shows-snaps- + As stated on https://forum.snapcraft.io/t/ubuntu-software-shows-snaps- as-installed-even-if-it-failed-to-install/4054 When a snap fails to install, Software center still shows the download as completed -- 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/1750098 Title: Ubuntu software shows snaps as installed even if it failed to install Status in gnome-software package in Ubuntu: New Bug description: As stated on https://forum.snapcraft.io/t/ubuntu-software-shows-snaps- as-installed-even-if-it-failed-to-install/4054 When a snap fails to install, Software center still shows the download as completed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1750098/+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 1644662] Re: Icons missing when appearance setting is "high contrast"
I have just verified this in my env earlier used to reproduce the issue. Results: artful - 3.22.3-1ubuntu2 - verified xenial - 3.18.0-2ubuntu2 - verified ** Tags removed: verification-needed verification-needed-artful verification-needed-xenial ** Tags added: verification-done verification-done-artful verification-done-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-themes-standard in Ubuntu. https://bugs.launchpad.net/bugs/1644662 Title: Icons missing when appearance setting is "high contrast" Status in gnome-themes-standard package in Ubuntu: Fix Released Status in gnome-themes-standard source package in Xenial: Fix Committed Status in gnome-themes-standard source package in Artful: Fix Committed Bug description: [Impact] * Switching to HighContrast theme in System Settings/Appearance results in missing icons for some of the panels in System Settings. * Only Xenial is affected of the currently supported releases. * Current development release is not affected. [Test Case] * Open System Settings, select Appearance. * Choose the "High Contrast" theme. * Go back by selecting "All Settings". Expected result: there are icons to all items in the Settings window. Actual result: some items are missing icons. [Regression Potential] * There might be different icons used in some places depending on the fact that for Xenial HighContrast used Adwaita themes. Possibly icons may be missing in different places. [Other Info] * For some reason Trusty was using HighContrast icons and the change was made somewhere in between Trusty - Xenial. * Original bug description: To reproduce this: Open System Settings. Click Appearance Theme: High Contrast. Click All Settings tab: Many icons are missing. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity-control-center 15.04.0+16.04.20160705-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24 Uname: Linux 4.4.0-47-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Nov 24 14:45:30 2016 ExecutablePath: /usr/bin/unity-control-center InstallationDate: Installed on 2015-06-06 (537 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcEnviron: PATH=(custom, user) SHELL=/bin/bash LANG=en_CA.UTF-8 LANGUAGE=en_CA:en XDG_RUNTIME_DIR= SourcePackage: unity-control-center UpgradeStatus: Upgraded to xenial on 2016-08-28 (88 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/1644662/+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 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
** Changed in: lightdm-gtk-greeter Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: Fix Released Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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 1670933] Re: [PATCH] Accessibility partly broken due to X root window being kept from login session.
** Changed in: lightdm-gtk-greeter Milestone: None => 2.0.4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-greeter in Ubuntu. https://bugs.launchpad.net/bugs/1670933 Title: [PATCH] Accessibility partly broken due to X root window being kept from login session. Status in LightDM GTK+ Greeter: Fix Committed Status in unity-greeter package in Ubuntu: Confirmed Bug description: affects lightdm Lightdm version 1.21.5, in 17.04. Some components of the Unity and Mate desktops are currently not accessible when logging in using lightdm. So far I've tested and reproduced this problem with both unity-greeter, and lightdm-gtk-greeter, so I suspect it is what I mentioned in the title, i.e the X root window is kept around. At-spi gets loaded in the greeter for use with Orca. At-spi ads a property atom, AT_SPI_BUS, to the root X window to allow software to be able to find the accessibility bus. If my understanding is correct, this root window is kept around for the user login session. What then happens is software either using Qt or Gtk loads its accessibility support code, which in turn looks for the AT_SPI_BUS property. Normally on session load, this property is not present, at which point the support code then connects to org.a11y.bus, which in turn via systemd loads the at-spi bus launcher and registry to respond to the bus activation/request. At-spi adds the AT_SPI_BUS property to the X root window at load. However the AT_SPI_BUS property is hanging around from the greeter session, which is confusing software. At-spi only then gets loaded from /etc/xdg/autostart/at-spi-dbus-bus.desktop by the mate or gnome session binaries, but this happens after unity-panel-service and mate- panel are loaded. As such they are inaccessible for the session, or until the user kills them and they get reloaded. To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm-gtk-greeter/+bug/1670933/+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 1745188] Re: gnome-calculator crashed with SIGABRT in mpfr_assert_fail → mpfr_init2 → mpc_init3 → mpc_pow_usi_naive → mpc_pow_usi
<< reposting my previous comment in the aligned format as there seems to be no option to edit it >> Hello, I encountered this abort/crash with gnome-calculator and finally got rid of it as under. I manually built and installed the latest mpfr/mpfc/gmp source code and binaries for building gcc-7.3 which turned out to be extremely frustrating and energy-draining. So, after installing those hand-built mpfr/mpfc/gmp binaries, I happened to launch the calculator(gnome- calculator) from the quick launch side-bar(yes, I still have Unity on 17.10!) and its icon was animating as usual for few seconds and nothing was happening after that. So, I tried to launch it from terminal - it showed the abort/crash error that this bug reports : "../../src/init2.c:52: MPFR assertion failed: p >= 2 && p <= ((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1))". After searching for the above error, I stumbled upon this bug report, and I tried to downgrade back to the default Ubuntu-repo version via "apt install" - that didn't solve the issue. I tried to build and install mpfr-4.0.0 version - didn't change the crash behavior. Tried building and installing mpfr-3.1.6/5 - didn't work. Manually removed the installed libraries(libmpfr*) from /usr/lib/* and /usr/local /lib/* and redid the installation - both "apt install" and build-install method from source for the reported mpfr-3.1.6 - didn't help. I had also tried to modify mpfr-4.0.1's source code to use precision 2 instead of 1 and also bunch of the other assert-macros logic for disabling the assertion(abort) - didn't help. Downgraded mpc* as well as gmp* to older versions by building from their sources and installing them - didn't help. So, basically, I tried to put my system back to the previous state before I started meddling with the mpfr/gmp/mpc all for building gcc-7.3 from its source - huge cost paid! Tried the extreme cases out though not relevant as I could already figure out but did them anyway to get back the "calculator" : reinstalled the kernel(I know kernel has nothing to do with mpfr!), rebooted the PC, and so on - didn't help. Finally, I paid close attention to the error stating that this assertion was from "init2.c:52", so I located this 52nd source code line inside mpfr-3.1.6/src/init2.c and *disabled* the assertion by commenting it out as my last attempt to get back the system to successfully launch gnome -calculator, rebuilt and installed it - boom! I got the gnome-calculator back. Below is what I commented out. I thought this was not necessary as MPFR_PREC_MIN was already 2 and not 1 as mentioned here in this proposed bug report/fix. Anyway. /* p=1 is not allowed since the rounding to nearest even rule requires at least two bits of mantissa: the neighbours of 3/2 are 1*2^0 and 1*2^1, which both have an odd mantissa */ //MPFR_ASSERTN(p >= MPFR_PREC_MIN && p <= MPFR_PREC_MAX); I confirmed that MPFR_PREC_MIN was 2 as told in here in this bug report and not 1 as in 4.0.1. But, even then the above assertion was failing causing abort/crash for gnome-calculator. Below is what I have in mpfr-3.1.6/src/mpfr.h(unchanged). /* Definition of precision limits without needing */ /* Note: the casts allows the expression to yield the wanted behavior for _MPFR_PREC_FORMAT == 1 (due to integer promotion rules). */ #define MPFR_PREC_MIN 2 #define MPFR_PREC_MAX ((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1)) Hope my above change help those banging their head to fix this super -annoying crash, until it's fixed in the mpfr* codebase/release as needed. Cheers, Raghavan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calculator in Ubuntu. https://bugs.launchpad.net/bugs/1745188 Title: gnome-calculator crashed with SIGABRT in mpfr_assert_fail → mpfr_init2 → mpc_init3 → mpc_pow_usi_naive → mpc_pow_usi Status in gnome-calculator package in Ubuntu: Triaged Status in mpclib3 package in Ubuntu: Triaged Bug description: I cannot launch gnome-calculator because of the following: ``` ../../src/init2.c:52: MPFR assertion failed: p >= 2 && p <= ((mpfr_prec_t)((mpfr_uprec_t)(~(mpfr_uprec_t)0)>>1)) Aborted (core dumped) ``` errors.u.c: https://errors.ubuntu.com/problem/40a6712b7f663d518c85d34a30891ff7629f9041 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-calculator 1:3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 ApportVersion: 2.20.8-0ubuntu6 Architecture: amd64 CurrentDesktop: GNOME Date: Wed Jan 24 19:13:49 2018 ExecutablePath: /usr/bin/gnome-calculator InstallationDate: Installed on 2017-08-21 (156 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170820) ProcCmdline: gnome-calculator Signal: 6 SourcePackage: gnome-calculator StacktraceTop: mpfr_assert_fail () at /usr/lib/x86_64-linux-gnu/libmpfr.so.4