[Desktop-packages] [Bug 1767648] Re: Top bar and shell dialogs are not displayed properly when zoom is enabled
This bug was fixed in the package mutter - 3.28.3+git20190124-0ubuntu18.04.2 --- mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium * control: Add Breaks on budgie-desktop verions broken by this upload. budgie-desktop needs a fix in 10.4+git20171031.10.g9f71bb8-1.2ubuntu1.2 for compatibility with this mutter. mutter (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New upstream git snapshot based on 3.28.3 plus commits up to 4af8d9d47 (LP: #1811900) - Fix crash in dual monitor setup and gdm activation (LP: #1790525, LP: #1795774) - Make possible to launch gnome-shell in wayland using nvidia and EGLDevice backend (LP: #1805444) * debian/libmutter-2-0.symbols: Add new symbols * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch, d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch, d/p/monitor-manager-Filter-out-low-screen-resolutions.patch, d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch, d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch, d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch, d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch, d/p/core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch, d/p/renderer-native-Fallback-to-non-planar-API-if-gbm_bo_get_.patch, d/p/clutter-x11-Implement-keycode-lookup-from-keysyms-on-virt.patch, d/p/clutter-Do-not-latch-modifiers-on-modifier-keys.patch: - Removed as applied upstream * d/p/clutter-Fix-offscreen-effect-painting-of-clones.patch: - Fix offscreen-effect painting of clones in zoom mode (LP: #1767648, LP: #1779615) -- Iain Lane Wed, 17 Apr 2019 11:35:51 +0100 ** Changed in: mutter (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1767648 Title: Top bar and shell dialogs are not displayed properly when zoom is enabled Status in Mutter: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] When zoom is enabled, the top bar and some shell dialogs (wireless network selection, shutdown dialog, etc.) are not displayed properly. (See the attached screenshots.) [Test Case] 1. Enable Zoom in Setting > Universal Access 2. (Optional) Set zoom factor to around 3 (or higher) 3. Look at the top bar. You will notice that all texts and icons are now gone. If you move your cursor to the right of the top bar, and then click on the status menu, you will see that only a portion of the menu is shown. 4. For the shell dialogs, go to the Settings app. In the Wifi section, choose one of the secured network available. You will see that the password dialog is not displayed in its entirety. [Regression Potential] Low. The affected code is only used in rendering shell panels and popup menus at the moment. So any potential regression (like the original bug) would be noticed in those places only, and not beyond. Furthermore, the upstream fix has been tested regularly for 8 months already. [Other Info] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.1-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CasperVersion: 1.394 CurrentDesktop: ubuntu:GNOME Date: Sat Apr 28 12:54:24 2018 DisplayManager: gdm3 GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" b'org.gnome.desktop.interface' b'cursor-size' b'96' LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.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/mutter/+bug/1767648/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
No, fix is not released: gnome-shell - 3.28.3+git20190124-0ubuntu18.04.1 - package from bionic- proposed. We are still waiting for it in bionic-updates. -- 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/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826359] Re: Xorg crashed with SIGSEGV in miPointerSetPosition()
*** This bug is a duplicate of bug 1733292 *** https://bugs.launchpad.net/bugs/1733292 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 #1733292, 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/1826359/+attachment/5258898/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1826359/+attachment/5258901/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1826359/+attachment/5258911/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1826359/+attachment/5258913/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1826359/+attachment/5258914/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1826359/+attachment/5258915/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1826359/+attachment/5258916/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1733292 Xorg crashed with SIGSEGV in point_on_screen from miPointerSetPosition from positionSprite from positionSprite from fill_pointer_events ** 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/1826359 Title: Xorg crashed with SIGSEGV in miPointerSetPosition() Status in xorg-server package in Ubuntu: New Bug description: Crashed overnight. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xserver-xorg-core 2:1.19.6-1ubuntu4.2 ProcVersionSignature: Ubuntu 4.15.0-47.50-generic 4.15.18 Uname: Linux 4.15.0-47-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 19:40:14 2019 DistUpgraded: 2018-08-24 16:58:36,112 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process "./xorg_fix_proprietary.py" (No such file or directory) (8)) DistroCodename: bionic DistroVariant: ubuntu ExecutablePath: /usr/lib/xorg/Xorg ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 620 [1028:07a0] InstallationDate: Installed on 2017-03-13 (772 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Dell Inc. Latitude 7480 ProcCmdline: /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 3 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-47-generic root=UUID=38187e08-c728-4202-b73b-d68f5c1c6965 ro quiet splash i915.enable_guc_loading=3 intel_iommu=igfx_off vt.handoff=1 SegvAnalysis: Segfault happened at: 0x562c23591b40:movswl 0x8(%rdi),%ecx PC (0x562c23591b40) ok source "0x8(%rdi)" (0x0008) not located in a known VMA region (needed readable region)! destination "%ecx" ok Stack memory exhausted (SP below stack segment) SegvReason: reading NULL VMA Signal: 11 SourcePackage: xorg-server StacktraceTop: ?? () miPointerSetPosition () ?? () ?? () GetPointerEvents () Title: Xorg crashed with SIGSEGV in miPointerSetPosition() UpgradeStatus: Upgraded to bionic on 2018-08-24 (243 days ago) UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo dmi.bios.date: 11/12/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.13.0 dmi.board.name: 0CXWHP dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.13.0:bd11/12/2018:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn0CXWHP:rvrA01:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7480 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.95-1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev:
[Desktop-packages] [Bug 1825963] Re: Abysmal memory leak on tracker-extract
After removing the folder with those .dds files, the memory leak of tracker-extract doesn't occur. However IMO this can't be regarded as anything as a temporary workaround. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1825963 Title: Abysmal memory leak on tracker-extract Status in tracker package in Ubuntu: New Bug description: After upgrading from 18.10 to 19.04 my Ubuntu desktop started lagging madly. It became very difficult to use and I discovered the problem to be tracker-extract running and very rapidly leaking memory up to 100% and breaching into swap memory. I tried killing it several times but Tracker appears to relaunch it every time, so I deleted it from /usr/lib/tracker entirely. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: tracker 2.1.8-2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Apr 23 13:02:25 2019 InstallationDate: Installed on 2019-03-11 (42 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: tracker UpgradeStatus: Upgraded to disco on 2019-04-23 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1825963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826311] Re: Cannot Login to Google with Advanced Protection Enabled
Thank you for your bug report, could you also report it upstream on https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/ ? They probably have more ideas about the topic that us as distributors do ** Changed in: gnome-online-accounts (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1826311 Title: Cannot Login to Google with Advanced Protection Enabled Status in gnome-online-accounts package in Ubuntu: New Bug description: Description: Ubuntu 19.04 Release: 19.04 gnome-online-accounts: Installed: 3.32.0-1ubuntu1 Candidate: 3.32.0-1ubuntu1 Version table: *** 3.32.0-1ubuntu1 500 500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status 1) Open Online accounts and select google (From settings or during OS setup) 2) enter username and password. What I expect: I get the prompt to plug-in my 2 factor hardware key What actually happens: I get a prompt saying, "You can only use your Security keys with Google Chrome" Not sure if this is actually fixable, I know desktop firefox has hidden settings to allow u2f, but not sure if that extends to the embedded browsers (if gnome-online-accounts even uses an embedded firefox for its browser) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 00:16:27 2019 InstallationDate: Installed on 2019-04-25 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1826311/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK
This bug was fixed in the package gnome-shell - 3.28.3+git20190124-0ubuntu18.04.1 --- gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New git snapshot release up to commit 24cdcc56d (LP: #1811900) - Don't fill journal with osdWindow errors (LP: #1772677) - Fix missing icon in keyboard indicator (LP: #1812266) * d/p/authPrompt-Do-not-enable-sensitivity-if-retries-are-disal.patch, d/p/authPrompt-Unset-preemptiveAnswer-on-reset.patch, d/p/gdm-util-Always-allow-to-retry-login-in-unlock-mode.patch, d/p/ibus-set-content-type-no-holdKeyboard.patch, d/p/popupMenu-Don-t-handle-key-presses-directly-if-there-are-.patch, d/p/st-button-Ignore-pointer-emulated-touch-events.patch, d/p/shell-ignore-invalid-window-monitor-index.patch, d/p/workspace-fix-repositioned-windows-in-activities.patch: - Removed patches applied upstream * d/p/StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch, d/p/js-fix-invalid-access-errors.patch, d/p/js-ui-Choose-some-actors-to-cache-on-the-GPU.patch, d/p/optional-hot-corner.patch, d/p/st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch, d/p/workaround_crasher_fractional_scaling.patch: - Refreshed as per upstream changes * d/p/keyboard-Filter-redundant-FocusTracker-position-changed-s.patch, d/p/keyboard-Listen-to-IbusPanelService-focus-in-out-to-track.patch: - Fix OSK activation on X11 (LP: #1760399) * d/p/power-Label-the-PENDING_CHARGE-state-as-Not-Charging.patch: - Label the PENDING_CHARGE state as "Not Charging" (LP: #1745032) * d/p/debian/patches/volume-Add-back-sound-feedback-on-scroll.patch: - Add missing include (LP: #1811908) -- Marco Trevisan (Treviño) Fri, 25 Jan 2019 18:29:40 + ** Changed in: gnome-shell (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1745032 Title: AC adapter status not detected on Asus ZenBook UX410UAK Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in upower package in Ubuntu: Fix Released Status in gnome-control-center source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in linux source package in Bionic: Fix Released Status in upower source package in Bionic: Fix Released Status in gnome-control-center source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Status in linux source package in Cosmic: Fix Released Status in upower source package in Cosmic: Fix Released Bug description: === SRU Justification === [Impact] Some Asus laptops report "discharging" when the battery is full and AC is plugged [Test] Charge battery to full, the issue appears. Users report with the patch the behaviour is correct. [Fix] The discharge rate is 0 on those machines. Use that to detect the wrong status report. [Regression Potential] Low. The quirk uses strict DMI to match affected systems. === Original Bug Report === The AC adapter status is incorrectly reported when the battery is fully charged. It always shows as if the adapter is not plugged in. If the battery is drained for a while, the adapter status is shown correctly (both connects and disconnects are shown). ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-31-generic 4.13.0-31.34 ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13 Uname: Linux 4.13.0-31-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: abarto 1388 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Jan 23 18:26:18 2018 InstallationDate: Installed on 2018-01-23 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-31-generic N/A linux-backports-modules-4.13.0-31-generic N/A linux-firmware 1.169.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2017 dmi.bios.vendor:
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
I would imagine that the currently shipped API key of "geoclue" is some
kind of universal default. Now that the use of keys is apparently being
monitored and limited, perhaps it would be possible for Ubuntu to
register its own key, and then ship that with this package?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825513] Re: High CPU usage when large document open
Sure. You can mail me at marcus.tomlinson AT canonical.com -- 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/1825513 Title: High CPU usage when large document open Status in LibreOffice: New Status in libreoffice package in Ubuntu: Incomplete Bug description: Description: CPU usage spikes to 110-130% (across 4 cores) when a large document (~260 pages, mainly text) is opened. Steps to reproduce: Open large document Observe CPU spike and fan spin up Close file Observe CPU drop and fan spin down Expected result: Small spike in CPU usage while opening, overall slight increase in CPU usage, total to remain >10% Reproducible: Always User Profile Reset: No. Bug also filed against Libreoffice 6.2.2 installed on Ubuntu 18.10 via PPA. See: https://bugs.documentfoundation.org/show_bug.cgi?id=124346 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice-writer 1:6.2.2-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 22:04:37 2019 InstallationDate: Installed on 2019-02-04 (74 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-19 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1825513/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826266] Re: Nautilus no longer copies file path when a file is marked then copied
Thanks, could you reprort it upstream on https://gitlab.gnome.org/GNOME/nautilus/issues/? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- 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/1826266 Title: Nautilus no longer copies file path when a file is marked then copied Status in nautilus package in Ubuntu: Confirmed Bug description: In previous versions of Ubuntu, copying in nautilus behaved so that it was possible to select a file, Ctrl+C (or just right-click + copy) and the resulting data on the clipboard was a "pasteable" file path that could be used directly in a terminal or by Ctrl+V in an open file dialog box. This was incredibly powerful. Ubuntu 19 behaves differently. If I for example select my .zshrc file in nautilus and past into terminal, the resulting output is: x-special/nautilus-clipboard copy file:///home/trond/.zshrc performing the same on Ubuntu 18 or lower would copy the literal path of the file: /home/trond/.zshrc imho this is a bug as it deteriorates the overall file management experience in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 22:00:17 2019 GsettingsChanges: b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2019-04-20 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772677] Re: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic)
This bug was fixed in the package gnome-shell - 3.28.3+git20190124-0ubuntu18.04.1 --- gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New git snapshot release up to commit 24cdcc56d (LP: #1811900) - Don't fill journal with osdWindow errors (LP: #1772677) - Fix missing icon in keyboard indicator (LP: #1812266) * d/p/authPrompt-Do-not-enable-sensitivity-if-retries-are-disal.patch, d/p/authPrompt-Unset-preemptiveAnswer-on-reset.patch, d/p/gdm-util-Always-allow-to-retry-login-in-unlock-mode.patch, d/p/ibus-set-content-type-no-holdKeyboard.patch, d/p/popupMenu-Don-t-handle-key-presses-directly-if-there-are-.patch, d/p/st-button-Ignore-pointer-emulated-touch-events.patch, d/p/shell-ignore-invalid-window-monitor-index.patch, d/p/workspace-fix-repositioned-windows-in-activities.patch: - Removed patches applied upstream * d/p/StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch, d/p/js-fix-invalid-access-errors.patch, d/p/js-ui-Choose-some-actors-to-cache-on-the-GPU.patch, d/p/optional-hot-corner.patch, d/p/st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch, d/p/workaround_crasher_fractional_scaling.patch: - Refreshed as per upstream changes * d/p/keyboard-Filter-redundant-FocusTracker-position-changed-s.patch, d/p/keyboard-Listen-to-IbusPanelService-focus-in-out-to-track.patch: - Fix OSK activation on X11 (LP: #1760399) * d/p/power-Label-the-PENDING_CHARGE-state-as-Not-Charging.patch: - Label the PENDING_CHARGE state as "Not Charging" (LP: #1745032) * d/p/debian/patches/volume-Add-back-sound-feedback-on-scroll.patch: - Add missing include (LP: #1811908) -- Marco Trevisan (Treviño) Fri, 25 Jan 2019 18:29:40 + ** Changed in: gnome-shell (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] I'm seeing a several gigs (more than 70GB) a day of org.gnome.Shell.desktop log entries. https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 [Test Case] With 2 monitors connected, simply lock the screen and leave it locked for a while. The error messages will be logged into syslog until all the empty space is filled up. More info: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243 [Regression Potential] Low. The fix (https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243) is a minor correction to window destroy logic, written by the main Gnome Shell maintainer. [Original Description] I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042
[Desktop-packages] [Bug 1812266] Re: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver)
This bug was fixed in the package gnome-shell - 3.28.3+git20190124-0ubuntu18.04.1 --- gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New git snapshot release up to commit 24cdcc56d (LP: #1811900) - Don't fill journal with osdWindow errors (LP: #1772677) - Fix missing icon in keyboard indicator (LP: #1812266) * d/p/authPrompt-Do-not-enable-sensitivity-if-retries-are-disal.patch, d/p/authPrompt-Unset-preemptiveAnswer-on-reset.patch, d/p/gdm-util-Always-allow-to-retry-login-in-unlock-mode.patch, d/p/ibus-set-content-type-no-holdKeyboard.patch, d/p/popupMenu-Don-t-handle-key-presses-directly-if-there-are-.patch, d/p/st-button-Ignore-pointer-emulated-touch-events.patch, d/p/shell-ignore-invalid-window-monitor-index.patch, d/p/workspace-fix-repositioned-windows-in-activities.patch: - Removed patches applied upstream * d/p/StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch, d/p/js-fix-invalid-access-errors.patch, d/p/js-ui-Choose-some-actors-to-cache-on-the-GPU.patch, d/p/optional-hot-corner.patch, d/p/st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch, d/p/workaround_crasher_fractional_scaling.patch: - Refreshed as per upstream changes * d/p/keyboard-Filter-redundant-FocusTracker-position-changed-s.patch, d/p/keyboard-Listen-to-IbusPanelService-focus-in-out-to-track.patch: - Fix OSK activation on X11 (LP: #1760399) * d/p/power-Label-the-PENDING_CHARGE-state-as-Not-Charging.patch: - Label the PENDING_CHARGE state as "Not Charging" (LP: #1745032) * d/p/debian/patches/volume-Add-back-sound-feedback-on-scroll.patch: - Add missing include (LP: #1811908) -- Marco Trevisan (Treviño) Fri, 25 Jan 2019 18:29:40 + ** Changed in: gnome-shell (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1812266 Title: Keyboard layout indicator does not indicate current layout (18.04 Bionic beaver) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: Upstream issue: https://gitlab.gnome.org/GNOME/gnome-shell/issues/913 [ Impact ] Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Test case ] 1. Boot 2. Suspend or lock the screen 3. Log again with your user 4. The keyboard indicator should display current layout [ Regression Potential ] Really low, we properly pass a null value instead of an undefined one, without breaking JS. -- Steps to reproduce the bug: 1. After normal boot, suspend or lock. 2. Login again. Result: Keyboard Layout indicator don't display current layout (empty selected drop down box) [ Workarounds ] - Switch with keyboard (Super+space) or mouse. BUT if you then logout on the login screen *when you press the first character* of the password the shown selected keyboard layout resets. - Restart Gnome Shell (Alt+F2 r): https://wiki.gnome.org/Projects/GnomeShell/CheatSheet#Developer_tools - Also asked here https://askubuntu.com/q/1109555/349837 - Similar old bug https://bugs.launchpad.net/gnome-settings-daemon/+bug/531173 $ inxi -SG -! 31 -y80 && cat /etc/default/keyboard && localectl status System:Kernel: 4.15.0-43-generic x86_64 bits: 64 Desktop: Gnome 3.28.3 Distro: Ubuntu 18.04.1 LTS Graphics: Card-1: Intel HD Graphics 520 Card-2: NVIDIA GM108M [GeForce 940M] Display Server: x11 (X.Org 1.19.6 ) drivers: fbdev (unloaded: modesetting,vesa) Resolution: 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) version: 4.5 Mesa 18.0.5 # KEYBOARD CONFIGURATION FILE # Consult the keyboard(5) manual page. XKBMODEL="pc105" XKBLAYOUT="es" XKBVARIANT="en" XKBOPTIONS="terminate:ctrl_alt_bksp" BACKSPACE="guess" System Locale: LANG=en_US.UTF-8 LC_NUMERIC=es_AR.UTF-8 LC_MONETARY=es_AR.UTF-8 LC_PAPER=es_AR.UTF-8 LC_NAME=es_AR.UTF-8 LC_ADDRESS=es_AR.UTF-8 LC_TELEPHONE=es_AR.UTF-8 LC_MEASUREMENT=es_AR.UTF-8 LC_IDENTIFICATION=es_AR.UTF-8 VC Keymap: n/a X11 Layout: es X11 Model: pc105 X11 Variant: en X11 Options: terminate:ctrl_alt_bksp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1812266/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1805444] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1805444 Title: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Bug description: [ Description ] Wayland sessions don't work with the Nvidia driver in 18.04, even after enabling them via the kernel command line 'nvidia- drm.modeset=1'. [ Fix ] See below for the changes from upstream that fix this, which we're uploading to disco-proposed now. [ QA ] Under the GNOME Micro Release Exception, you can believe this is fixed. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It might be a good idea to test an nvidia machine, but it doesn't need explicit verification. [Original description] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due to following missing changes in mutter 3.28.3-2~ubuntu18.04.2 commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84 Author: Miguel A. Vico Date: Thu Jun 7 16:29:44 2018 -0700 renderer/native: Choose first EGL config for non-GBM backends Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only choose EGL configs that match the GBM_FORMAT_XRGB pixel format. However, there won't be any EGL config satisfying such criteria for non-GBM backends, such as EGLDevice. This change will let us choose the first EGL config for the EGLDevice backend, while still forcing GBM_FORMAT_XRGB configs for the GBM one. Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2 commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b Author: Jonas Ådahl Date: Tue Nov 14 16:08:52 2017 +0800 renderer/native: Also wrap flip closures for EGLStreams When using the EGLStream backend, the MetaRendererNative passed a GClosure to KMS when using EGLStreams, but KMS flip callback event handler in meta-gpu-kms.c expected a closure wrapped in a closure container, meaning it'd instead crash when using EGLStreams. Make the flip handler get what it expects also when using EGLStreams by wrapping the flip closure in the container before handing it over to EGL. https://bugzilla.gnome.org/show_bug.cgi?id=790316 apt-cache policy mutter mutter: Installed: 3.28.3-2~ubuntu18.04.2 Candidate: 3.28.3-2~ubuntu18.04.2 Version table: *** 3.28.3-2~ubuntu18.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811900] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811900 Title: SRU 3.28 latest git to bionic Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Released Status in mutter source package in Bionic: Fix Released Status in gnome-shell source package in Disco: Invalid Status in mutter source package in Disco: Invalid Bug description: [ Description ] 3.28 gnome git branch has various upstream approved fixes for many months now, but no release has been done yet, thus we're releasing a git snapshot of the latest approved fixes. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been included in upstream git now, various optimizations to clutter actors could cause drawing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811908] Re: gnome-shell: JS ERROR: ReferenceError: GLib is not defined
This bug was fixed in the package gnome-shell - 3.28.3+git20190124-0ubuntu18.04.1 --- gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New git snapshot release up to commit 24cdcc56d (LP: #1811900) - Don't fill journal with osdWindow errors (LP: #1772677) - Fix missing icon in keyboard indicator (LP: #1812266) * d/p/authPrompt-Do-not-enable-sensitivity-if-retries-are-disal.patch, d/p/authPrompt-Unset-preemptiveAnswer-on-reset.patch, d/p/gdm-util-Always-allow-to-retry-login-in-unlock-mode.patch, d/p/ibus-set-content-type-no-holdKeyboard.patch, d/p/popupMenu-Don-t-handle-key-presses-directly-if-there-are-.patch, d/p/st-button-Ignore-pointer-emulated-touch-events.patch, d/p/shell-ignore-invalid-window-monitor-index.patch, d/p/workspace-fix-repositioned-windows-in-activities.patch: - Removed patches applied upstream * d/p/StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch, d/p/js-fix-invalid-access-errors.patch, d/p/js-ui-Choose-some-actors-to-cache-on-the-GPU.patch, d/p/optional-hot-corner.patch, d/p/st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch, d/p/workaround_crasher_fractional_scaling.patch: - Refreshed as per upstream changes * d/p/keyboard-Filter-redundant-FocusTracker-position-changed-s.patch, d/p/keyboard-Listen-to-IbusPanelService-focus-in-out-to-track.patch: - Fix OSK activation on X11 (LP: #1760399) * d/p/power-Label-the-PENDING_CHARGE-state-as-Not-Charging.patch: - Label the PENDING_CHARGE state as "Not Charging" (LP: #1745032) * d/p/debian/patches/volume-Add-back-sound-feedback-on-scroll.patch: - Add missing include (LP: #1811908) -- Marco Trevisan (Treviño) Fri, 25 Jan 2019 18:29:40 + ** Changed in: gnome-shell (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811908 Title: gnome-shell: JS ERROR: ReferenceError: GLib is not defined Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Bug description: [ Impact ] Gnome-shell in Bionic spams the journal with error such as: giu 05 17:33:24 tricky gnome-shell[4049]: JS ERROR: ReferenceError: GLib is not defined _sliderChanged/this._notifyVolumeChangeId<@resource:///org/gnome/shell/ui/status/volume.js:163:17 When changing the volume scrolling over the volume indicator. [ Test case ] - Run `journalctl -ef -b0 /usr/bin/gnome-shell` - Scroll with the mouse over the volume indicator - No error should be spammed by gnome-shell metnioning a ReferenceError [ Regression potential ] None, a JS include is missing, and adding it can't canuse any trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic
This bug was fixed in the package gnome-shell - 3.28.3+git20190124-0ubuntu18.04.1 --- gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New git snapshot release up to commit 24cdcc56d (LP: #1811900) - Don't fill journal with osdWindow errors (LP: #1772677) - Fix missing icon in keyboard indicator (LP: #1812266) * d/p/authPrompt-Do-not-enable-sensitivity-if-retries-are-disal.patch, d/p/authPrompt-Unset-preemptiveAnswer-on-reset.patch, d/p/gdm-util-Always-allow-to-retry-login-in-unlock-mode.patch, d/p/ibus-set-content-type-no-holdKeyboard.patch, d/p/popupMenu-Don-t-handle-key-presses-directly-if-there-are-.patch, d/p/st-button-Ignore-pointer-emulated-touch-events.patch, d/p/shell-ignore-invalid-window-monitor-index.patch, d/p/workspace-fix-repositioned-windows-in-activities.patch: - Removed patches applied upstream * d/p/StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch, d/p/js-fix-invalid-access-errors.patch, d/p/js-ui-Choose-some-actors-to-cache-on-the-GPU.patch, d/p/optional-hot-corner.patch, d/p/st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch, d/p/workaround_crasher_fractional_scaling.patch: - Refreshed as per upstream changes * d/p/keyboard-Filter-redundant-FocusTracker-position-changed-s.patch, d/p/keyboard-Listen-to-IbusPanelService-focus-in-out-to-track.patch: - Fix OSK activation on X11 (LP: #1760399) * d/p/power-Label-the-PENDING_CHARGE-state-as-Not-Charging.patch: - Label the PENDING_CHARGE state as "Not Charging" (LP: #1745032) * d/p/debian/patches/volume-Add-back-sound-feedback-on-scroll.patch: - Add missing include (LP: #1811908) -- Marco Trevisan (Treviño) Fri, 25 Jan 2019 18:29:40 + ** Changed in: gnome-shell (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811900 Title: SRU 3.28 latest git to bionic Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Released Status in mutter source package in Bionic: Fix Released Status in gnome-shell source package in Disco: Invalid Status in mutter source package in Disco: Invalid Bug description: [ Description ] 3.28 gnome git branch has various upstream approved fixes for many months now, but no release has been done yet, thus we're releasing a git snapshot of the latest approved fixes. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been included in upstream git now, various optimizations to clutter actors could cause drawing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811908] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811908 Title: gnome-shell: JS ERROR: ReferenceError: GLib is not defined Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Bug description: [ Impact ] Gnome-shell in Bionic spams the journal with error such as: giu 05 17:33:24 tricky gnome-shell[4049]: JS ERROR: ReferenceError: GLib is not defined _sliderChanged/this._notifyVolumeChangeId<@resource:///org/gnome/shell/ui/status/volume.js:163:17 When changing the volume scrolling over the volume indicator. [ Test case ] - Run `journalctl -ef -b0 /usr/bin/gnome-shell` - Scroll with the mouse over the volume indicator - No error should be spammed by gnome-shell metnioning a ReferenceError [ Regression potential ] None, a JS include is missing, and adding it can't canuse any trouble. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811908/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779615] Re: Shell text and some icons have sharp edges during zoom
Please always report what package version has been used during verification! But yeah, this time accepting verification even without this info as I trust you have used -proposed as required. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1779615 Title: Shell text and some icons have sharp edges during zoom Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] Shell text and some icons have sharp edges during zoom. Screenshot attached. https://gitlab.gnome.org/GNOME/gnome-shell/issues/387 [Test Case] 1. Settings > Universal Access > Zoom = ON 2. Click on the time/calendar and look closely at the font edges. Expect: the edges should be smooth when zoomed. [Regression Potential] Low potential effect on other parts of Gnome Shell. The code being changed is only used in shell popup menus at the moment. [Other Info] This is not an important bug at all. Its fix is just a happy consequence of fixing the more important bug 1767648, so that's why it is getting SRU'd - for bug 1767648. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1779615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790525] Re: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutt
This bug was fixed in the package mutter - 3.28.3+git20190124-0ubuntu18.04.2 --- mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium * control: Add Breaks on budgie-desktop verions broken by this upload. budgie-desktop needs a fix in 10.4+git20171031.10.g9f71bb8-1.2ubuntu1.2 for compatibility with this mutter. mutter (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New upstream git snapshot based on 3.28.3 plus commits up to 4af8d9d47 (LP: #1811900) - Fix crash in dual monitor setup and gdm activation (LP: #1790525, LP: #1795774) - Make possible to launch gnome-shell in wayland using nvidia and EGLDevice backend (LP: #1805444) * debian/libmutter-2-0.symbols: Add new symbols * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch, d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch, d/p/monitor-manager-Filter-out-low-screen-resolutions.patch, d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch, d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch, d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch, d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch, d/p/core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch, d/p/renderer-native-Fallback-to-non-planar-API-if-gbm_bo_get_.patch, d/p/clutter-x11-Implement-keycode-lookup-from-keysyms-on-virt.patch, d/p/clutter-Do-not-latch-modifiers-on-modifier-keys.patch: - Removed as applied upstream * d/p/clutter-Fix-offscreen-effect-painting-of-clones.patch: - Fix offscreen-effect painting of clones in zoom mode (LP: #1767648, LP: #1779615) -- Iain Lane Wed, 17 Apr 2019 11:35:51 +0100 ** Changed in: mutter (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1790525 Title: gnome-shell assert failure: double free or corruption (fasttop) in g_free() from g_error_free() from cogl_error_free() from cogl_texture_new_with_size() from clutter_offscreen_effect_real_create_texture() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Status in mutter source package in Cosmic: Fix Released Bug description: [ Impact ] Gnome shell crashes on double free Problem is occurring if dual monitor is used. Second monitor is repeatingly blank and activated again. At the bottom it probably contains the upper part of the first monitor. I had the same problem at 18.04 when using gdm3 without wayland during logon. [ Test case ] - Run gnome-shell with multimonitor - No flashing should happen on gdm initialization Also we should monitor crashes in e.u.c [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- ProblemType: CrashDistroRelease: Ubuntu 18.10 Package: gnome-shell 3.29.90-2ubuntu1 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic i686 ApportVersion: 2.20.10-0ubuntu9 Architecture: i386 AssertionMessage: double free or corruption (fasttop) CurrentDesktop: ubuntu:GNOME Date: Mon Sep 3 21:02:58 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'" ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANGUAGE=en_US:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6SourcePackage: gnome-shell StacktraceTop: __libc_signal_restore_set (set=0xbfcd5e9c) at ../sysdeps/unix/sysv/linux/nptl-signals.h:80 __GI_raise (sig=6) at ../sysdeps/unix/sysv/linux/raise.c:48 __GI_abort () at abort.c:79 __libc_message (action=do_abort, fmt=) at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (str=str@entry=0xb6b437e8 "double free or corruption (fasttop)") at malloc.c:5350 Title: gnome-shell assert failure: double free or corruption (fasttop) 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/mutter/+bug/1790525/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend
This bug was fixed in the package mutter - 3.28.3+git20190124-0ubuntu18.04.2 --- mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium * control: Add Breaks on budgie-desktop verions broken by this upload. budgie-desktop needs a fix in 10.4+git20171031.10.g9f71bb8-1.2ubuntu1.2 for compatibility with this mutter. mutter (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New upstream git snapshot based on 3.28.3 plus commits up to 4af8d9d47 (LP: #1811900) - Fix crash in dual monitor setup and gdm activation (LP: #1790525, LP: #1795774) - Make possible to launch gnome-shell in wayland using nvidia and EGLDevice backend (LP: #1805444) * debian/libmutter-2-0.symbols: Add new symbols * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch, d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch, d/p/monitor-manager-Filter-out-low-screen-resolutions.patch, d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch, d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch, d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch, d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch, d/p/core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch, d/p/renderer-native-Fallback-to-non-planar-API-if-gbm_bo_get_.patch, d/p/clutter-x11-Implement-keycode-lookup-from-keysyms-on-virt.patch, d/p/clutter-Do-not-latch-modifiers-on-modifier-keys.patch: - Removed as applied upstream * d/p/clutter-Fix-offscreen-effect-painting-of-clones.patch: - Fix offscreen-effect painting of clones in zoom mode (LP: #1767648, LP: #1779615) -- Iain Lane Wed, 17 Apr 2019 11:35:51 +0100 ** Changed in: mutter (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1805444 Title: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Bug description: [ Description ] Wayland sessions don't work with the Nvidia driver in 18.04, even after enabling them via the kernel command line 'nvidia- drm.modeset=1'. [ Fix ] See below for the changes from upstream that fix this, which we're uploading to disco-proposed now. [ QA ] Under the GNOME Micro Release Exception, you can believe this is fixed. https://wiki.ubuntu.com/StableReleaseUpdates/GNOME It might be a good idea to test an nvidia machine, but it doesn't need explicit verification. [Original description] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due to following missing changes in mutter 3.28.3-2~ubuntu18.04.2 commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84 Author: Miguel A. Vico Date: Thu Jun 7 16:29:44 2018 -0700 renderer/native: Choose first EGL config for non-GBM backends Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only choose EGL configs that match the GBM_FORMAT_XRGB pixel format. However, there won't be any EGL config satisfying such criteria for non-GBM backends, such as EGLDevice. This change will let us choose the first EGL config for the EGLDevice backend, while still forcing GBM_FORMAT_XRGB configs for the GBM one. Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2 commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b Author: Jonas Ådahl Date: Tue Nov 14 16:08:52 2017 +0800 renderer/native: Also wrap flip closures for EGLStreams When using the EGLStream backend, the MetaRendererNative passed a GClosure to KMS when using EGLStreams, but KMS flip callback event handler in meta-gpu-kms.c expected a closure wrapped in a closure container, meaning it'd instead crash when using EGLStreams. Make the flip handler get what it expects also when using EGLStreams by wrapping the flip closure in the container before handing it over to EGL. https://bugzilla.gnome.org/show_bug.cgi?id=790316 apt-cache policy mutter mutter: Installed: 3.28.3-2~ubuntu18.04.2 Candidate: 3.28.3-2~ubuntu18.04.2 Version table: *** 3.28.3-2~ubuntu18.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811900] Re: SRU 3.28 latest git to bionic
This bug was fixed in the package mutter - 3.28.3+git20190124-0ubuntu18.04.2 --- mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium * control: Add Breaks on budgie-desktop verions broken by this upload. budgie-desktop needs a fix in 10.4+git20171031.10.g9f71bb8-1.2ubuntu1.2 for compatibility with this mutter. mutter (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New upstream git snapshot based on 3.28.3 plus commits up to 4af8d9d47 (LP: #1811900) - Fix crash in dual monitor setup and gdm activation (LP: #1790525, LP: #1795774) - Make possible to launch gnome-shell in wayland using nvidia and EGLDevice backend (LP: #1805444) * debian/libmutter-2-0.symbols: Add new symbols * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch, d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch, d/p/monitor-manager-Filter-out-low-screen-resolutions.patch, d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch, d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch, d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch, d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch, d/p/core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch, d/p/renderer-native-Fallback-to-non-planar-API-if-gbm_bo_get_.patch, d/p/clutter-x11-Implement-keycode-lookup-from-keysyms-on-virt.patch, d/p/clutter-Do-not-latch-modifiers-on-modifier-keys.patch: - Removed as applied upstream * d/p/clutter-Fix-offscreen-effect-painting-of-clones.patch: - Fix offscreen-effect painting of clones in zoom mode (LP: #1767648, LP: #1779615) -- Iain Lane Wed, 17 Apr 2019 11:35:51 +0100 ** Changed in: mutter (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811900 Title: SRU 3.28 latest git to bionic Status in gnome-shell package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Status in gnome-shell source package in Bionic: Fix Released Status in mutter source package in Bionic: Fix Released Status in gnome-shell source package in Disco: Invalid Status in mutter source package in Disco: Invalid Bug description: [ Description ] 3.28 gnome git branch has various upstream approved fixes for many months now, but no release has been done yet, thus we're releasing a git snapshot of the latest approved fixes. [ QA ] Run Ubuntu session, expect the shell to work normally with various setups https://wiki.ubuntu.com/StableReleaseUpdates/GNOME [ Regresison potential ] Many patches we were including already have been included in upstream git now, various optimizations to clutter actors could cause drawing issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1795774] Re: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_text
This bug was fixed in the package mutter - 3.28.3+git20190124-0ubuntu18.04.2 --- mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium * control: Add Breaks on budgie-desktop verions broken by this upload. budgie-desktop needs a fix in 10.4+git20171031.10.g9f71bb8-1.2ubuntu1.2 for compatibility with this mutter. mutter (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New upstream git snapshot based on 3.28.3 plus commits up to 4af8d9d47 (LP: #1811900) - Fix crash in dual monitor setup and gdm activation (LP: #1790525, LP: #1795774) - Make possible to launch gnome-shell in wayland using nvidia and EGLDevice backend (LP: #1805444) * debian/libmutter-2-0.symbols: Add new symbols * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch, d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch, d/p/monitor-manager-Filter-out-low-screen-resolutions.patch, d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch, d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch, d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch, d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch, d/p/core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch, d/p/renderer-native-Fallback-to-non-planar-API-if-gbm_bo_get_.patch, d/p/clutter-x11-Implement-keycode-lookup-from-keysyms-on-virt.patch, d/p/clutter-Do-not-latch-modifiers-on-modifier-keys.patch: - Removed as applied upstream * d/p/clutter-Fix-offscreen-effect-painting-of-clones.patch: - Fix offscreen-effect painting of clones in zoom mode (LP: #1767648, LP: #1779615) -- Iain Lane Wed, 17 Apr 2019 11:35:51 +0100 ** Changed in: mutter (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1795774 Title: gnome-shell crashed with SIGSEGV in cogl_texture_get_height(texture=0x0) from clutter_offscreen_effect_real_paint_target() from clutter_offscreen_effect_paint_texture() from clutter_offscreen_effect_paint() from clutter_actor_continue_paint() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Status in mutter source package in Cosmic: Fix Released Bug description: [ Impact ] Gnome shell crashes on cogl_texture_get_height [ Test case ] No clear reproducer is know for such issue, crashes should be monitored in e.u.c checking that this is not happening anymore for the version in proposed. [ Regression potential ] Low, the proposed fix is part of the current stable branch upstream and not changed in further revisions. -- The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 3.30.0-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/e5b2dcb04552882a76f1daa6b9f18ba864269d26 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1795774/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1779615] Re: Shell text and some icons have sharp edges during zoom
This bug was fixed in the package mutter - 3.28.3+git20190124-0ubuntu18.04.2 --- mutter (3.28.3+git20190124-0ubuntu18.04.2) bionic; urgency=medium * control: Add Breaks on budgie-desktop verions broken by this upload. budgie-desktop needs a fix in 10.4+git20171031.10.g9f71bb8-1.2ubuntu1.2 for compatibility with this mutter. mutter (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New upstream git snapshot based on 3.28.3 plus commits up to 4af8d9d47 (LP: #1811900) - Fix crash in dual monitor setup and gdm activation (LP: #1790525, LP: #1795774) - Make possible to launch gnome-shell in wayland using nvidia and EGLDevice backend (LP: #1805444) * debian/libmutter-2-0.symbols: Add new symbols * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch, d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch, d/p/monitor-manager-Filter-out-low-screen-resolutions.patch, d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch, d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch, d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch, d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch, d/p/core-Return-1-if-meta_window_get_monitor-is-called-on-an-.patch, d/p/renderer-native-Fallback-to-non-planar-API-if-gbm_bo_get_.patch, d/p/clutter-x11-Implement-keycode-lookup-from-keysyms-on-virt.patch, d/p/clutter-Do-not-latch-modifiers-on-modifier-keys.patch: - Removed as applied upstream * d/p/clutter-Fix-offscreen-effect-painting-of-clones.patch: - Fix offscreen-effect painting of clones in zoom mode (LP: #1767648, LP: #1779615) -- Iain Lane Wed, 17 Apr 2019 11:35:51 +0100 ** Changed in: mutter (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1779615 Title: Shell text and some icons have sharp edges during zoom Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Bionic: Fix Released Status in mutter source package in Cosmic: Fix Released Bug description: [Impact] Shell text and some icons have sharp edges during zoom. Screenshot attached. https://gitlab.gnome.org/GNOME/gnome-shell/issues/387 [Test Case] 1. Settings > Universal Access > Zoom = ON 2. Click on the time/calendar and look closely at the font edges. Expect: the edges should be smooth when zoomed. [Regression Potential] Low potential effect on other parts of Gnome Shell. The code being changed is only used in shell popup menus at the moment. [Other Info] This is not an important bug at all. Its fix is just a happy consequence of fixing the more important bug 1767648, so that's why it is getting SRU'd - for bug 1767648. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1779615/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 421537] Re: need a way to rotate video playback
Upstream report showing "RESOLVED FIXED" on 2011-08-30 New interface has these controls if appropriate plugin enabled ** Changed in: totem (Ubuntu) Assignee: Ubuntu Desktop Bugs (desktop-bugs) => (unassigned) ** Changed in: totem (Ubuntu) Status: Triaged => Fix Released -- 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/421537 Title: need a way to rotate video playback Status in Totem: Fix Released Status in totem package in Ubuntu: Fix Released Bug description: Binary package hint: totem have problems when viewing mov files from cell phone. the viedo is turned 90 degrees to the left. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/totem-gstreamer Package: totem-gstreamer 2.26.1-0ubuntu5 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem Uname: Linux 2.6.28-15-generic i686 To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/421537/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: geoclue-2.0 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825720] Re: No option to 'star' file in 19.04
go to settings > search. then look for a setting icon on bottom right of the box and click it. Go to other and select those folders where you want the Star to work -- 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/1825720 Title: No option to 'star' file in 19.04 Status in nautilus package in Ubuntu: Invalid Bug description: New feature in 19.04 is not working on my system. As I understand, I should be able to right-click a file/folder and select star. That option is not available though 'Starred' is now a location in places. This option is missing under both Wayland and X. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1825720/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 289063] Re: Totem cant play from iPod
Upstream report closed "RESOLVED FIXED" on 2012-04-18 Tested ok with iPhone and Ubuntu 18.04 so closing ** Changed in: totem (Ubuntu) Status: Triaged => Fix Released -- 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/289063 Title: Totem cant play from iPod Status in Totem: Fix Released Status in totem package in Ubuntu: Fix Released Bug description: Binary package hint: totem When I connect my iPod to my laptop, it asks me if I wont to play it with Rhythmbox, which works great. But if you open totem, in the menu under "Movie" it gives you an option to play your iPod with Totem, but it does not work. This needs to be addressed. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/289063/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826201] Re: MP4 Video playback is broken in Ubuntu 19.04
** Package changed: totem (Ubuntu) => gstreamer-vaapi (Ubuntu) ** Changed in: gstreamer-vaapi (Ubuntu) Status: Incomplete => New -- 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/1826201 Title: MP4 Video playback is broken in Ubuntu 19.04 Status in gstreamer-vaapi package in Ubuntu: New Bug description: MP4 videos cannot be played using the video player (TOTEM). This might be an upgrade problem. VLC and other video players are working fine but i prefer to use totem I have attached a video recording showing the problem in detail. All was working fine before the upgrade. PS : I understand this problem is not related to the package "ubuntu-release-upgrader" but i cannot change it without getting errors( Launchpad and Ubuntu-bug problem ) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: ubuntu-release-upgrader-core 1:19.04.16.1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Wed Apr 24 13:32:53 2019 InstallationDate: Installed on 2018-06-12 (315 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180425.1) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to disco on 2019-04-20 (3 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1826201/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails
Thanks! ** Changed in: gnome-online-accounts (Ubuntu) Status: New => Triaged ** Also affects: gnome-online-accounts via https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/60 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1825580 Title: Gnome Online Accounts fails to sign in Exchange emails Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: Triaged Bug description: After upgrading from 18.10 and/or on fresh install, a known-working Exchange email setup fails to sign in, giving "Error 7: Unexpected response from server". Tested the same settings and credentials on a new install of 18.10 and it worked. I have Evolution and Evolution-ews installed on all instances, working in 18.10, not in 19.04. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-online-accounts 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 16:38:32 2019 InstallationDate: Installed on 2018-03-24 (391 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-online-accounts UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1825580/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 492782] Re: [i945gme] Mouse cursor disappears after restarting screen (xrandr / resume)
As of 2019, using Ubuntu 18.04.2 LTS, this bug is still alive... When I invoke Xrandr the cursor disappears and I have to Alt-Ctrl-F1 and then Alt-Ctrl-F7 to make the cursor re-appear again. I'm using a relatively new BIOSTAR A68N-5600 motherboard newly bought in 2018. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu. https://bugs.launchpad.net/bugs/492782 Title: [i945gme] Mouse cursor disappears after restarting screen (xrandr / resume) Status in xserver-xorg-video-intel package in Ubuntu: Fix Released Bug description: Binary package hint: xorg I use xrandr to activate my external monitor or set the screen size of my Asus Eee 900A PC. However, since the upgrade to Ubuntu Karmic, the mouse cursor disappears after using xrandr. I'm using xorg version 1:7.4+3ubuntu10 and Ubuntu 9.10. The commands I use are: xrandr --output LVDS --mode 800x600 xrandr --output LVDS --off --output VGA --mode 1280x1024 After using these commands, the mouse cursor disappears, but I can still focus and click. Moving the (suspected, but invisible) mouse cursor over a desktop item, highlits it and I can activate it by clicking. One temporarily solution I've found is to switch to the console (CTRL + ALT + F1) and back (CTRL + ALT + F7). This makes the mouse cursor reappear. Using xrandr to reset to the original settings doesn't bring the cursor back. ProblemType: Bug Architecture: i386 Date: Sat Dec 5 10:45:14 2009 DistroRelease: Ubuntu 9.10 Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: ASUSTeK Computer INC. 900A Package: xorg 1:7.4+3ubuntu10 ProcCmdLine: root=UUID=f2d72569-836f-4878-832e-3b9ad0270b07 ro quiet splash ProcEnviron: LANG=de_AT.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.28-12.43-hostname-eeepc RelatedPackageVersions: xserver-xorg 1:7.4+3ubuntu10 libgl1-mesa-glx 7.6.0-1ubuntu4 libdrm2 2.4.14-1ubuntu1 xserver-xorg-video-intel 2:2.9.0-1ubuntu2 xserver-xorg-video-ati 1:6.12.99+git20090929.7968e1fb-0ubuntu1 SourcePackage: xorg Tags: ubuntu-unr Uname: Linux 2.6.28-12-netbook-eeepc i686 XsessionErrors: (gnome-settings-daemon:2545): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:2545): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (nautilus:2568): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (polkit-gnome-authentication-agent-1:2578): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed dmi.bios.date: 10/27/2008 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0703 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 900A dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTek Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/27/2008:svnASUSTeKComputerINC.:pn900A:pvrx.x:rvnASUSTeKComputerINC.:rn900A:rvrx.xx:cvnASUSTekComputerINC.:ct10:cvrx.x: dmi.product.name: 900A dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. fglrx: Not loaded system: distro: Ubuntu architecture: i686kernel: 2.6.28-12-netbook-eeepc [lspci] 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GME Express Integrated Graphics Controller [8086:27ae] (rev 03) Subsystem: ASUSTeK Computer Inc. Device [1043:8340] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/492782/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1772677] Update Released
The verification of the Stable Release Update for gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772677 Title: gnome-shell filling up syslog with thousands/millions of entries with stack traces ending in osdWindow.js (lines 206/207 in bionic, lines 223/224 in cosmic) Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-shell source package in Cosmic: In Progress Bug description: [Impact] I'm seeing a several gigs (more than 70GB) a day of org.gnome.Shell.desktop log entries. https://gitlab.gnome.org/GNOME/gnome-shell/issues/602 [Test Case] With 2 monitors connected, simply lock the screen and leave it locked for a while. The error messages will be logged into syslog until all the empty space is filled up. More info: https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/243 [Regression Potential] Low. The fix (https://gitlab.gnome.org/GNOME/gnome- shell/merge_requests/243) is a minor correction to window destroy logic, written by the main Gnome Shell maintainer. [Original Description] I'm seeing a several gigs (more than 70GB) a day of the following entries on syslog: May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:207 (0x7f31f00c96f8 @ 258) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #6 0x7ffcc6cee1b0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: == Stack trace for context 0x557ebb0a3320 == May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #0 0x7ffcc6cedf80 I resource:///org/gnome/shell/ui/osdWindow.js:206 (0x7f31f00c96f8 @ 231) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #1 0x7ffcc6cedff0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #2 0x7ffcc6cedff0 I self-hosted:915 (0x7f31d4df12b8 @ 367) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #3 0x7ffcc6cee090 I resource:///org/gnome/gjs/modules/signals.js:128 (0x7f31d4dd3230 @ 386) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #4 0x7ffcc6cee140 b resource:///org/gnome/shell/ui/layout.js:531 (0x7f31f00042b8 @ 127) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]: #5 0x7ffcc6cee1b0 I resource:///org/gnome/gjs/modules/_legacy.js:82 (0x7f31d4db5de0 @ 71) May 21 23:54:55 fc553042 org.gnome.Shell.desktop[1469]:
[Desktop-packages] [Bug 1760399] Re: New On-screen keyboard does not appear automatically when selecting some text fields
This bug was fixed in the package gnome-shell - 3.28.3+git20190124-0ubuntu18.04.1 --- gnome-shell (3.28.3+git20190124-0ubuntu18.04.1) bionic; urgency=medium * New git snapshot release up to commit 24cdcc56d (LP: #1811900) - Don't fill journal with osdWindow errors (LP: #1772677) - Fix missing icon in keyboard indicator (LP: #1812266) * d/p/authPrompt-Do-not-enable-sensitivity-if-retries-are-disal.patch, d/p/authPrompt-Unset-preemptiveAnswer-on-reset.patch, d/p/gdm-util-Always-allow-to-retry-login-in-unlock-mode.patch, d/p/ibus-set-content-type-no-holdKeyboard.patch, d/p/popupMenu-Don-t-handle-key-presses-directly-if-there-are-.patch, d/p/st-button-Ignore-pointer-emulated-touch-events.patch, d/p/shell-ignore-invalid-window-monitor-index.patch, d/p/workspace-fix-repositioned-windows-in-activities.patch: - Removed patches applied upstream * d/p/StIcon-only-compute-shadow-pipeline-when-the-texture-is-p.patch, d/p/js-fix-invalid-access-errors.patch, d/p/js-ui-Choose-some-actors-to-cache-on-the-GPU.patch, d/p/optional-hot-corner.patch, d/p/st-texture-cache-Cancel-sliced-image-loading-on-target-ac.patch, d/p/workaround_crasher_fractional_scaling.patch: - Refreshed as per upstream changes * d/p/keyboard-Filter-redundant-FocusTracker-position-changed-s.patch, d/p/keyboard-Listen-to-IbusPanelService-focus-in-out-to-track.patch: - Fix OSK activation on X11 (LP: #1760399) * d/p/power-Label-the-PENDING_CHARGE-state-as-Not-Charging.patch: - Label the PENDING_CHARGE state as "Not Charging" (LP: #1745032) * d/p/debian/patches/volume-Add-back-sound-feedback-on-scroll.patch: - Add missing include (LP: #1811908) -- Marco Trevisan (Treviño) Fri, 25 Jan 2019 18:29:40 + ** Changed in: gnome-shell (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1760399 Title: New On-screen keyboard does not appear automatically when selecting some text fields Status in OEM Priority Project: Fix Released Status in gnome-settings-daemon package in Ubuntu: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-settings-daemon source package in Bionic: Fix Released Status in gnome-shell source package in Bionic: Fix Released Status in gnome-settings-daemon source package in Cosmic: Fix Released Status in gnome-shell source package in Cosmic: Fix Released Bug description: [Impact] on-screen keyboard cannot be reliably opened when running under xorg. [Test Case] 1. Login into an xorg session 1. Open an application with text-entries (e.g. Firefox) 2. Try to enter text in a text entry using the new OSK Expected results: The on-screen keyboard should appear. [Regression Potential] The proposed fix requires a change in the way gnome-settings-daemon decides to enable or disable ibus. Please make sure that ibus correctly works when using a keyboard layout that requires it (e.g. chinese). [Original Report] I have always used an on-screen keyboard as a virtual keyboard for entering text in a different layout than my physical keyboard. This time I cannot, since I cannot manually trigger the new OSK. Steps: 1. Open Firefox 2. Try to enter text in a different layout using the new OSK 3. You cannot make the OSK appear When enabled, the new OSK appears automatically in Activities, but I cannot trigger it outside GNOME apps. You have to enable the new OSK first from Universal Access in Settings. I consider this a regression from 16.04 LTS, where On-board is easily triggered. Workaround: sudo apt install onboard ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10 Uname: Linux 4.15.0-13-generic x86_64 ApportVersion: 2.20.9-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 1 11:31:16 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-10-02 (180 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930) SourcePackage: gnome-shell UpgradeStatus: Upgraded to bionic on 2018-03-27 (4 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1760399/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 662279] Re: Inconsistency in the order of Play, Previous and Next buttons
Upstream report is a duplicate of #551365 which was closed "RESOLVED NOTABUG" on 2008-09-09 In new interface the order of buttons does not change when running Totem full screen so marking this as being fixed. ** Changed in: totem (Ubuntu) Status: Triaged => Fix Released -- 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/662279 Title: Inconsistency in the order of Play, Previous and Next buttons Status in Totem: Invalid Status in totem package in Ubuntu: Fix Released Bug description: Binary package hint: totem System: Ubuntu Maverick 64-bit In the normal view, Totem shows the buttons in the following order: Previous, Play, Next In fullscreen, however, Totem shows the following: Play, Previous, Next For comparison, Rhythmbox shows: Play, Previous, Next Please make the button order consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/totem/+bug/662279/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1633572] Re: video not playing
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 14.04 (trusty) reaches end-of-life today. Do you still see the bug in a later supported release of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: totem (Ubuntu) Status: New => Incomplete -- 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/1633572 Title: video not playing Status in totem package in Ubuntu: Incomplete Bug description: I have faced the problem several times, video not playing, shows read i/o error. Also file copy to usb drive problem. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-98.145-generic 3.13.11-ckt39 Uname: Linux 3.13.0-98-generic i686 ApportVersion: 2.14.1-0ubuntu3.21 Architecture: i386 CurrentDesktop: Unity Date: Fri Oct 14 23:16:58 2016 InstallationDate: Installed on 2016-08-25 (50 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1633572/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704740] Re: [upstream] calc: move cell does not update row sum
** Summary changed: - calc: move cell does not update row sum + [upstream] calc: move cell does not update row sum ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released ** Changed in: libreoffice (Ubuntu) Status: Fix Released => Fix Committed -- 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/1704740 Title: [upstream] calc: move cell does not update row sum Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Committed Bug description: See attached test case. Sum two rows: A1 + B1 = C1; A2 + B2 = C2 where B1 is blank. Cut B2 and paste into B1. Result C2 is decremented correctly by old B2 value; but result C1 is NOT incremented by new B1 value. Formula of C1 remains correct =SUM($Sheet1.A1:B1) as is C2's formula but C1 result is wrong. Saving file, close and re-open does not fix incorrect C1 result. Undo undo to return to initial state results in C2 now having incorrect result. Bug occurs whether drag and drop or control-x/control-v used. This is a data integrity issue as the wrong answer is being displayed. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: libreoffice-calc 1:5.1.6~rc2-0ubuntu1~xenial2 ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70 Uname: Linux 4.4.0-83-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.9 Architecture: amd64 CurrentDesktop: Unity Date: Mon Jul 17 17:33:42 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2016-05-08 (435 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1704740/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826391] [NEW] UI allows dangerous mistakes
Public bug reported: Version: 3.28.3 I managed to format my system drive to NTFS by accident, the UI did nothing to prevent it or even warn me. Last week I was formatting a thumb drive to NTFS. I forgot to select it and my system NVME was selected. I noticed it after I created the NTFS partition but it made no sense since my laptop was running well... I though: it must be a bug in the UI and nothing serious. I'm used to partition programs that allow you to design the partitions and then you click a button to actually write your desired partition map. End result: My system NVME was formatted to NTFS, grub was still present in the drive. I though I had my boot damaged but no: I lost all my data. Can we make the argument: Is the user an idiot? Yes. Does Gnome Disks UI is UX friendly? No. Does it prevents the user from formatting the system partition/drive or mistakes in general? No. I believe Gnome Disks must warn/prevent the user from formatting the system drive. The fact the partition is created right away without a second step makes mistakes very easy. ** Affects: gnome-disk-utility (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-disk-utility in Ubuntu. https://bugs.launchpad.net/bugs/1826391 Title: UI allows dangerous mistakes Status in gnome-disk-utility package in Ubuntu: New Bug description: Version: 3.28.3 I managed to format my system drive to NTFS by accident, the UI did nothing to prevent it or even warn me. Last week I was formatting a thumb drive to NTFS. I forgot to select it and my system NVME was selected. I noticed it after I created the NTFS partition but it made no sense since my laptop was running well... I though: it must be a bug in the UI and nothing serious. I'm used to partition programs that allow you to design the partitions and then you click a button to actually write your desired partition map. End result: My system NVME was formatted to NTFS, grub was still present in the drive. I though I had my boot damaged but no: I lost all my data. Can we make the argument: Is the user an idiot? Yes. Does Gnome Disks UI is UX friendly? No. Does it prevents the user from formatting the system partition/drive or mistakes in general? No. I believe Gnome Disks must warn/prevent the user from formatting the system drive. The fact the partition is created right away without a second step makes mistakes very easy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-disk-utility/+bug/1826391/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819129] Re: No CPU record on Virtualbox
** Also affects: ubuntu-report (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: ubuntu-report (Ubuntu Bionic)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-report in Ubuntu.
https://bugs.launchpad.net/bugs/1819129
Title:
No CPU record on Virtualbox
Status in ubuntu-report package in Ubuntu:
New
Status in ubuntu-report source package in Bionic:
New
Status in ubuntu-report source package in Disco:
New
Bug description:
On a virtualbox guest ubuntu-report doesn't report CPU information.
u@pc:~$ ubuntu-report show
{
"Version": "19.04",
"OEM": {
"Vendor": "innotek GmbH",
"Product": "VirtualBox"
},
"BIOS": {
"Vendor": "innotek GmbH",
"Version": "VirtualBox"
},
"Arch": "amd64",
"GPU": [
{
"Vendor": "15ad",
"Model": "0405"
}
],
"RAM": 2,
"Disks": [
21.5
],
"Partitions": [
20.5
],
"Screens": [
{
"Size": "0mmx0mm",
"Resolution": "800x600",
"Frequency": "60.00"
}
],
"Autologin": true,
"LivePatch": false,
"Session": {
"DE": "ubuntu:GNOME",
"Name": "ubuntu",
"Type": "x11"
},
"Language": "en_US",
"Timezone": "America/New_York",
"Install": {
"Media": "Ubuntu 19.04 \"Disco Dingo\" - Alpha amd64 (20190305.1)",
"Type": "GTK",
"OEM": false,
"PartitionMethod": "use_device",
"DownloadUpdates": true,
"Language": "en",
"Minimal": false,
"RestrictedAddons": false,
"Stages": {
"0": "language",
"2": "language",
"8": "console_setup",
"16": "console_setup",
"20": "prepare",
"24": "partman",
"26": "start_install",
"86": "timezone",
"90": "usersetup",
"97": "user_done",
"582": "done"
}
}
}
@pc:~$ lscpu
Architecture:x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 48 bits physical, 48 bits virtual
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
NUMA node(s):1
Vendor ID: AuthenticAMD
CPU family: 16
Model: 10
Model name: AMD Phenom(tm) II X6 1055T Processor
Stepping:0
CPU MHz: 2812.342
BogoMIPS:5624.68
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache:512K
L3 cache:6144K
NUMA node0 CPU(s): 0
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp
lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid
tsc_known_freq pni monitor cx16 x2apic popcnt hypervisor lahf_lm cr8_legacy abm
sse4a misalignsse 3dnowprefetch vmmcall
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-report 1.4.0
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 8 04:06:58 2019
Dependencies:
gcc-9-base 9-20190220-0ubuntu1
libc6 2.28-0ubuntu1
libgcc1 1:9-20190220-0ubuntu1
libidn2-0 2.0.5-1
libunistring2 0.9.10-1ubuntu1
InstallationDate: Installed on 2019-03-07 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubuntu-report
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-report/+bug/1819129/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
Tested just now (25 April, 10:00 UTC) and a query to the service with
the "geoclue" key returns a valid location. I wonder if someone already
increased the quota for that key and the issue can be considered solved,
or if it's just a lucky coincidence and the daily limit was reset before
I tried.
If the problem persists, there are two possible approaches:
- Ensure the daily limit for the "geoclue" key is high enough
(unlimited?) that it can reasonably sustain all the requests coming from
Ubuntu (and other distros), and check with upstream geoclue that they
are fine with distros using the upstream key
- Request an Ubuntu-specific key (see
https://location.services.mozilla.com/api) and distro-patch geoclue-2.0
to use that key
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826052]
This seems to be a duplicate of bug 123054, which means it's fixed, and the fix will be part of 6.2.4. *** This bug has been marked as a duplicate of bug 123054 *** -- 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/1826052 Title: [upstream] LibreOffice on Ubuntu 19.04 screws up text paragraph styling Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Fix Committed Bug description: After updating Ubuntu to 19.04 documents previously created in LibreOffice had some of their paragraph styling wiped, e.g. a custom heading style was arbitrarily removed in some but not all instances in a document and was replaced with 'Default Style'. LibreOffice Version: 6.2.2.2 Build ID: 1:6.2.2-0ubuntu2 CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1826052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826052] Re: [upstream] LibreOffice on Ubuntu 19.04 screws up text paragraph styling
** Changed in: df-libreoffice Status: New => Invalid -- 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/1826052 Title: [upstream] LibreOffice on Ubuntu 19.04 screws up text paragraph styling Status in LibreOffice: Invalid Status in libreoffice package in Ubuntu: Fix Committed Bug description: After updating Ubuntu to 19.04 documents previously created in LibreOffice had some of their paragraph styling wiped, e.g. a custom heading style was arbitrarily removed in some but not all instances in a document and was replaced with 'Default Style'. LibreOffice Version: 6.2.2.2 Build ID: 1:6.2.2-0ubuntu2 CPU threads: 4; OS: Linux 5.0; UI render: default; VCL: gtk3; Locale: en-GB (en_GB.UTF-8); UI-Language: en-GB Calc: threaded To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1826052/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815239] Re: [snap] Using the Groupedbar Compact user interface and tiling to half the screen, expanding then collapsing grouped bar loses Font group
Testing 6.2.3.2 (released Tuesday) it seems this issue may have been subsequently resolved. Can you confirm Ads2? -- 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/1815239 Title: [snap] Using the Groupedbar Compact user interface and tiling to half the screen, expanding then collapsing grouped bar loses Font group Status in libreoffice package in Ubuntu: New Bug description: Using the Groupedbar Compact user interface and tiling the window to half the screen by moving it to the right, expanding then collapsing grouped bar (by pressing the arrow (->) to the right of the Font group then clicking off the expansion (it should bring up the Paragraph, Insert, References, Review, and View groups)) moves the Font group to the expansion and results in a fair amount of grey space where the Font group was previously. Re-maximizing the window and then re-tiling to half the screen usually corrects this effect. Possible that this is an upstream bug but wanted to file here (partially for Olivier's opinion) before filing upstream. Screen resolution: 1600x900 ``` $ snap info libreoffice tracking: edge refresh-date: yesterday at 14:47 GMT channels: stable:6.1.4.2 2019-01-14 (100) 499MB - candidate: 6.1.4.2 2019-01-24 (102) 499MB - beta: 6.2.0.3 2019-01-31 (103) 505MB - edge: ↑ installed: 6.2.0.3(103) 505MB - $ snap version snap2.37.2+git1136.9d2c80f~ubuntu16.04.1 snapd 2.37.2+git1136.9d2c80f~ubuntu16.04.1 series 16 ubuntu 18.10 kernel 4.18.0-14-generic $ snap info core tracking: edge refresh-date: today at 13:47 GMT channels: stable:16-2.37.1 2019-02-01 (6350) 95MB - candidate: 16-2.37.1 2019-01-31 (6350) 95MB - beta: 16-2.37.2 2019-02-06 (6405) 95MB - edge: 16-2.37.2+git1136.9d2c80f 2019-02-08 (6420) 93MB - installed: 16-2.37.2+git1136.9d2c80f(6420) 93MB core ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1815239/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826395] Re: i tried to print a pdf file using Document viwer and printer prints garbage page
** Attachment added: "pdf" https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826395/+attachment/5259000/+files/0425-0430.pdf -- 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/1826395 Title: i tried to print a pdf file using Document viwer and printer prints garbage page Status in cups package in Ubuntu: New Bug description: 1. Ubuntu 19.04 2. HP Deskjet 400, hpcups 3.19.3 Examine the file obtained in the previous step by running the command ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:52:44 2019 InstallationDate: Installed on 2019-03-20 (35 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for HP: socket://172.16.206.55 MachineType: Micro-Star International Co., Ltd. PL62 7RC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=838b2683-bfe0-4dac-8c5e-d920aa70b420 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-18 (6 days ago) dmi.bios.date: 12/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16JDIMS.10A dmi.board.asset.tag: Default string dmi.board.name: MS-16JD dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16JDIMS.10A:bd12/26/2017:svnMicro-StarInternationalCo.,Ltd.:pnPL627RC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16JD:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: PL dmi.product.name: PL62 7RC dmi.product.sku: 16JD.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1511832] Re: Totem global menu drop down options GUI buggy display
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016 Is this still an issue for anyone in a later Ubuntu release? ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: totem (Ubuntu) Status: Confirmed => Incomplete ** Changed in: totem Status: New => Incomplete -- 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/1511832 Title: Totem global menu drop down options GUI buggy display Status in One Hundred Papercuts: Incomplete Status in Totem: Incomplete Status in totem package in Ubuntu: Incomplete Bug description: When playing videos with single audio track (most videos), if you go to the "View>Languages>" you can see the bug. It does not show empty. Only a thin black horizontal line with shadow appears. The screenshot is attached. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: totem 3.16.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Oct 31 00:59:31 2015 InstallationDate: Installed on 2012-06-22 (1225 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) SourcePackage: totem UpgradeStatus: Upgraded to wily on 2015-10-29 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1511832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1485955] Re: [upstream] EDITING: Background Color button from Table toolbar should change cell background instead of paragraph background
** Changed in: libreoffice (Ubuntu) Status: New => Fix Committed -- 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/1485955 Title: [upstream] EDITING: Background Color button from Table toolbar should change cell background instead of paragraph background Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Fix Committed Bug description: Steps to reproduce: 1. Launch LibreOffice Writer 2. Insert table to the new document (Table -> Insert -> Table) 3. Write some multirow text in table cells 4. Try to change cell background: 4.1. place cursor on desired cell 4.2. select color from palette from "Background Color" drop-down (located on Table toolbar). 4.3. click "Background Color" button on Table toolbar. Expected results: background color of TABLE CELL (where cursor was) is changed to desired color. Actual results: background color of TEXT PARAGRAPH (where cursor was) is changed to desired color. Workaround: There is slow non-intuitive background - select whole cell, select color from palette from "Background Color" drop-down (located on Table toolbar), click "Background Color" button on Table toolbar. Affected versions: LibreOffice 3.5.7.2 Build ID: 350m1(Build:2) = pre-installed Ubuntu 12.04.5 LTS version; LibreOffice 4.2.7.2 Build ID: 420m0(Build:2) = pre-installed Ubuntu 14.04.2 LTS version; LibreOffice 4.4.2.2 Build ID: 40m0(Build:2) = pre-installed Ubuntu 15.04 version. Comment: I can't believe how this bug is possible. It is inherited from OO.org (I saw it on OO.org 3.2 in Ubuntu 10.04.4 LTS too). Microsoft Word 2003 and 2007 of course have normal behaviour with cell background. I attached pdf document with screenshots. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libreoffice 1:3.5.7-0ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-61.100~precise1-generic 3.13.11-ckt22 Uname: Linux 3.13.0-61-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.9 Architecture: amd64 Date: Tue Aug 18 11:45:50 2015 InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429) MarkForUpload: True SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1485955/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1455097] Re: /etc/pm/sleep.d/ is no more processed
This bug was fixed in the package unattended-upgrades - 1.1ubuntu1.18.04.7~16.04.2 --- unattended-upgrades (1.1ubuntu1.18.04.7~16.04.2) xenial; urgency=medium * Don't check blacklist too early and report updates from not allowed origins as kept back. (LP: #1781176) * test/test_blacklisted_wrong_origin.py: Fix and enable test * Filter out progress indicator from dpkg log (LP: #1599646) * Clear cache when autoremoval fails (LP: #1779157) * Find autoremovable kernel packages using the patterns in APT's way (LP: #1815494) unattended-upgrades (1.1ubuntu1.18.04.7~16.04.1) xenial; urgency=medium * Start service after systemd-logind.service to be able to take inhibition lock (LP: #1806487) * Handle gracefully when logind is down (LP: #1806487) unattended-upgrades (1.1ubuntu1.18.04.7~16.04.0) xenial; urgency=medium * Backport to Xenial (LP: #1702793) * Revert to build-depending on debhelper (>= 9~) and dh-systemd * Revert configuration example changes to avoid triggering a debconf question * debian/postinst: Update recovery to be triggered on Xenial's package versions unattended-upgrades (1.1ubuntu1.18.04.7) bionic; urgency=medium * Trigger unattended-upgrade-shutdown actions with PrepareForShutdown() Performing upgrades in service's ExecStop did not work when the upgrades involved restarting services because systemd blocked other stop/start actions making maintainer scripts time out and be killed leaving a broken system behind. Running unattended-upgrades.service before shutdown.target as a oneshot service made it run after unmounting filesystems and scheduling services properly on shutdown is a complex problem and adding more services to the mix make it even more fragile. The solution of monitoring PrepareForShutdown() signal from DBus allows Unattended Upgrade to run _before_ the jobs related to shutdown are queued thus package upgrades can safely restart services without risking causing deadlocks or breaking part of the shutdown actions. Also ask running unattended-upgrades to stop when shutdown starts even in InstallOnShutdown mode and refactor most of unattended-upgrade-shutdown to UnattendedUpgradesShutdown class. (LP: #1778219) * Increase logind's InhibitDelayMaxSec to 30s. (LP: #1778219) This allows more time for unattended-upgrades to shut down gracefully or even install a few packages in InstallOnShutdown mode, but is still a big step back from the 30 minutes allowed for InstallOnShutdown previously. Users enabling InstallOnShutdown node are advised to increase InhibitDelayMaxSec even further possibly to 30 minutes. - Add NEWS entry about increasing InhibitDelayMaxSec and InstallOnShutdown changes * Ignore "W503 line break before binary operator" because it will become the best practice and breaks the build * Stop using ActionGroups, they interfere with apt.Cache.clear() causing all autoremovable packages to be handled as newly autoremovable ones and be removed by default. Dropping ActionGroup usage does not slow down the most frequent case of not having anything to upgrade and when there are packages to upgrade the gain is small compared to the actual package installation. Also collect autoremovable packages before adjusting candidates because that also changed .is_auto_removable attribute of some of them. (LP: #1803749) (Closes: #910874) unattended-upgrades (1.1ubuntu1.18.04.6) bionic; urgency=medium * Unlock for dpkg operations with apt_pkg.pkgsystem_unlock_inner() when it is available. Also stop running when reacquiring the lock fails. Thanks to Julian Andres Klode for original partial patch (LP: #1789637) * Skip rebuilding python-apt in upgrade autopkgtests. Python-apt has a new build dependency making the rebuilding as is failing and the reference handling issue is worked around in unattended-upgrades already. (LP: #1781586) * Stop trying when no adjustment could be made and adjust package candidates only to lower versions (LP: #1785093) * Skip already adjusted packages from being checked for readjusting. This makes it clearer that the recursion ends and can also be a bit quicker. (LP: #1785093) unattended-upgrades (1.1ubuntu1.18.04.5) bionic; urgency=medium * Stop updating the system when reacquiring the dpkg system lock fails. (LP: #1260041) unattended-upgrades (1.1ubuntu1.18.04.4) bionic; urgency=medium * Redirect stderr output in upgrade-between-snapshots, too, otherwise it breaks the test sometimes (LP: #1781446) unattended-upgrades (1.1ubuntu1.18.04.3) bionic; urgency=medium * Redirect stderr output in upgrade-all-security, otherwise it breaks the test (LP: #1781446) unattended-upgrades (1.1ubuntu1.18.04.2) bionic; urgency=medium [ Balint Reczey ] * Clear cache when autoremoval is invalid for a package set marked for removal and
[Desktop-packages] [Bug 1375400] Re: totem gets stuck
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 14.04 (trusty) reaches end-of-life today. Do you still see the bug in a later supported release of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: totem (Ubuntu) Status: New => Incomplete -- 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/1375400 Title: totem gets stuck Status in totem package in Ubuntu: Incomplete Bug description: I run totem and then open a file. It then gets stuck and does not play the file. A lot of the time it works and if it does work, then totem never seems to have a problem with subsequent files. The issue is always with the first file opened it seems ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-34.60-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 29 19:07:25 2014 InstallationDate: Installed on 2011-07-29 (1158 days ago) InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1) SourcePackage: totem UpgradeStatus: Upgraded to trusty on 2014-08-15 (45 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1375400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1729963] Re: chromium-browser crashed in OnConnectionDisconnectedFilter()
It appears the trace has changed slightly, crashes are tracked in a separate report on errors.ubuntu.com: https://errors.ubuntu.com/problem/e0e63ef80dd16f02330b92c6af9e21591b2f47f0 ** Description changed: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 62.0.3202.62-0ubuntu0.17.10.1380, the problem page at https://errors.ubuntu.com/problem/ac572b4fed36983c400b47046ea2445bd14d3884 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/. + + EDIT: new error page: + https://errors.ubuntu.com/problem/e0e63ef80dd16f02330b92c6af9e21591b2f47f0 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1729963 Title: chromium-browser crashed in OnConnectionDisconnectedFilter() Status in chromium-browser package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 62.0.3202.62-0ubuntu0.17.10.1380, the problem page at https://errors.ubuntu.com/problem/ac572b4fed36983c400b47046ea2445bd14d3884 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/. EDIT: new error page: https://errors.ubuntu.com/problem/e0e63ef80dd16f02330b92c6af9e21591b2f47f0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1729963/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826215] Re: /usr/lib/chromium-browser/chromium-browser:5:operator:~LogMessage:OnConnectionDisconnectedFilter:dbus_connection_dispatch:dbus_connection_dispatch
*** This bug is a duplicate of bug 1729963 *** https://bugs.launchpad.net/bugs/1729963 ** This bug has been marked a duplicate of bug 1729963 chromium-browser crashed in OnConnectionDisconnectedFilter() -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1826215 Title: /usr/lib/chromium-browser/chromium- browser:5:operator:~LogMessage:OnConnectionDisconnectedFilter:dbus_connection_dispatch:dbus_connection_dispatch Status in chromium-browser package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding chromium-browser. This problem was most recently seen with package version 73.0.3683.103-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/e0e63ef80dd16f02330b92c6af9e21591b2f47f0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1826215/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
I forwarded the proposed kbd fix upstream: https://lists.altlinux.org/pipermail/kbd/2019-April/000653.html ** Changed in: kbd (Ubuntu Eoan) Status: Confirmed => In Progress -- 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/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: Fix Released Status in kbd package in Ubuntu: In Progress Status in xorg-server package in Ubuntu: Invalid Status in console-setup source package in Bionic: Fix Committed Status in kbd source package in Bionic: Confirmed Status in linux source package in Bionic: Confirmed Status in xorg-server source package in Bionic: Invalid Status in console-setup source package in Cosmic: Fix Committed Status in kbd source package in Cosmic: Confirmed Status in linux source package in Cosmic: Confirmed Status in xorg-server source package in Cosmic: Invalid Status in console-setup source package in Disco: Fix Committed Status in kbd source package in Disco: Confirmed Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Invalid Status in console-setup source package in Eoan: Fix Released Status in kbd source package in Eoan: In Progress Status in linux source package in Eoan: Confirmed Status in xorg-server source package in Eoan: Invalid Bug description: (console-setup) [Impact] * keyboard-configuration's postinst changes keyboard mode breaking X keys. [Test Case] * Ssh to a system or open a terminal and unset DISPLAY $ echo $DISPLAY $ * Check kbd mode, should be raw (set by kbd_mode -s) or unknown: $ sudo kbd_mode The keyboard is in some unknown mode $ sudo kbd_mode The keyboard is in raw (scancode) mode $ On Xenial X runs on VT7 thus the graphical environment is not affected in the default configuration, but the keyboard-configuration postinst maintaner script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode to observe the change: $ sudo kbd_mode -s -C /dev/tty1 $ sudo kbd_mode -C /dev/tty1 The keyboard is in raw (scancode) mode * Install or reinstall kbd-configuration $ sudo apt install --reinstall keyboard-configuration ... Setting up keyboard-configuration (1.178ubuntu11) ... Your console font configuration will be updated the next time your system boots. If you want to update it now, run 'setupcon' from a virtual console. ... * With the fixed package you should see the note above and the kbd mode must stay the same (on Xenial check VT1: sudo kbd_mode -C /dev/tty1): $ sudo kbd_mode The keyboard is in raw (scancode) mode $ * The unfixed package sets the kbd mode to unicode: $ sudo kbd_mode The keyboard is in Unicode (UTF-8) mode $ [Regression Potential] * The change may break debian-installer changing the keyboard mode, this should also be tested. * In general changing the postinst script may make the package unable to install, but this is tested in generic environment and the change to the postinst script is very small. [Original Bug Text] WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
I noticed that the OP had VirtualBox installed, same for me. This taints the kernel ... Are people who posted about going back to the old kernel using VBox? So, re-installing 'VirtualBox' and ubuntu package 'menu' worked for me, and keeping the new kernel Suggest "dmesg | grep vbox" (YMMV) I also noticed that I had installed the .deb as a direct download from Oracle & and not noticed there was an Ubuntu package in the repositories. The Ubuntu package has some extra bits to it. Apport/Whoopsie kept popping up with a crash message shortly after login but when I clicked to see the report everything disappeared. Anyone else get this? Re-install of 'menu' seems to work here. -- 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/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash 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. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1822179] Re: Resuming from sleep breaks desktop and lock screen background in GNOME
Same problem here. Nvidia GeForce 920MX, latest driver installed. -- 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/1822179 Title: Resuming from sleep breaks desktop and lock screen background in GNOME Status in gnome-shell package in Ubuntu: Confirmed Bug description: CPU: AMD Ryzen 5 1600 MOBO: MSI B350M MORTAR GPU: NVIDIA GTX 1060 Ubuntu version: 19.04 Nvidia driver version: 418.56 The system is updated with the latest updates as today, 28 March 2019 As the title says, in Ubuntu 19.04 the GNOME lockscreen gets corrupted, and the GNOME desktop has blank background after resuming from standby/sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826400] [NEW] Event jumps to preceding date after edit
Public bug reported: Full-day events jump a date back if edited and saved, even when no information about date or time is changed. Tested in local and Google calendars, happens in both. To reproduce: 1. Create a full-day event (say on May 5) 2. Click on the event to open event editor 3. Keep the date and time unchanged (full day, May 5) 4. Press "Finish" 5. The event is now registered as a full-day event on the previous date, in this case May 4. Tested on several events in different months, the result is always the same. I reproduced the bug in both month and week view. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-calendar 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 14:17:07 2019 InstallationDate: Installed on 2018-05-09 (350 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to disco on 2019-04-03 (21 days ago) ** Affects: gnome-calendar (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-calendar in Ubuntu. https://bugs.launchpad.net/bugs/1826400 Title: Event jumps to preceding date after edit Status in gnome-calendar package in Ubuntu: New Bug description: Full-day events jump a date back if edited and saved, even when no information about date or time is changed. Tested in local and Google calendars, happens in both. To reproduce: 1. Create a full-day event (say on May 5) 2. Click on the event to open event editor 3. Keep the date and time unchanged (full day, May 5) 4. Press "Finish" 5. The event is now registered as a full-day event on the previous date, in this case May 4. Tested on several events in different months, the result is always the same. I reproduced the bug in both month and week view. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-calendar 3.32.0-1 ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6 Uname: Linux 5.0.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 14:17:07 2019 InstallationDate: Installed on 2018-05-09 (350 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-calendar UpgradeStatus: Upgraded to disco on 2019-04-03 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1826400/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761554] Re: [bionic] Extended characters in GNOME screen keyboard don't get entered
*** This bug is a duplicate of bug 1760399 *** https://bugs.launchpad.net/bugs/1760399 My understanding is that this bug has been taken care of through the fixes of bug #1760399 and bug #1816808. Marking it a duplicate of the former. ** This bug has been marked a duplicate of bug 1760399 New On-screen keyboard does not appear automatically when selecting some text fields -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-config in Ubuntu. https://bugs.launchpad.net/bugs/1761554 Title: [bionic] Extended characters in GNOME screen keyboard don't get entered Status in gnome-shell package in Ubuntu: Triaged Status in gnome-user-docs package in Ubuntu: Confirmed Status in im-config package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Status in gnome-user-docs source package in Bionic: Confirmed Status in im-config source package in Bionic: Triaged Bug description: im-config SRU request = [Impact] When in a Wayland session, accented characters as well as some special characters can't be entered via the screen keyboard. The issue is fixed via the proposed upload of im-config, which has been changed to not set the GTK_IM_MODULE environment variable for IBus on Wayland (previously GTK_IM_MODULE was set to "ibus"). Making this accessibility tool work without issues on Wayland is important enough to justify this SRU. [Test Case] 1. Log in to an Ubuntu on Wayland session 2. Open gedit and enable the screen keyboard (Settings -> Universal Access -> Typing) -> Accented characters via long-press does not work. Example: long-press a and select à from the popup Also, certain keys for special characters result in incorrect characters or nothing. Examples: ~, √, ÷, ×, <, >, ¢ 3. Install im-config from bionic-proposed 4. Relogin and repeat step 2. -> Everything works as expected [Regression Potential] There are reasons to presuppose that GTK_IM_MODULE does not need to be set at all for IBus on a GNOME desktop: * GTK has a mechanism for selecting a built-in IM. * IBus is default in GNOME, and vanilla GNOME (which does not make use of im-config) does not set the GTK_IM_MODULE environment variable. But the change is only made for Wayland sessions, which is not default in 18.04. Given this limitation, the regression risk is deemed to be low. [Original description] I filed this bug upstream last month but it hasn't gotten much attention so I'm filing it here because I think we need to track this issue for the Ubuntu 18.04 release https://gitlab.gnome.org/GNOME/gnome-shell/issues/109 Test Case - 1. Open the Settings app. Click Universal Access. 2. Enable the Screen Keyboard. (Optionally, turn on "Always Show Universal Access Menu" to make turning the Screen Keyboard on and off easier.) 3. Open Text Editor 4. Click the u button on the Screen Keyboard 5. Long-press the u button on the Screen Keyboard for a few seconds. On the popup, click the ü character. What Happens In Step 4, u is entered in the Text Editor document. Nothing is entered in Step 5. This bug affects any of the "extended characters" clicked on from the long-press popup in the Screen Keyboard. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741843] Re: caribou (gnome-shell osk): special characters not working
*** This bug is a duplicate of bug 1760399 *** https://bugs.launchpad.net/bugs/1760399 ** This bug is no longer a duplicate of bug 1761554 [bionic] Extended characters in GNOME screen keyboard don't get entered ** This bug has been marked a duplicate of bug 1760399 New On-screen keyboard does not appear automatically when selecting some text fields -- 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/1741843 Title: caribou (gnome-shell osk): special characters not working Status in Caribou: In Progress Status in caribou package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Bug description: I'm on Ubuntu 17.10 (fully updated, including Gnome-Shell). Hardware is a Lenovo X1 Carbon Laptop with Touchscreen. I've reproduced this issue on both Wayland and XOrg. I've reproduced this issue on the 17.10 live CD (Xorg) and on a fresh 17.10 (Wayland) install in VBox. Bug: Caribou/Gnome-Shell Wayland support for Caribou does not display the vast majority of special characters (the ones that you long press on vowels to get). Nor do the upside down question and exclamation marks work on it either. Nor do the Euro or Sterling signs work. This makes it impossible to use when writing in any other languages than English. 1) lsb_release -rd Description: Ubuntu 17.10 Release: 17.10 2) package version: caribou: Installed: 0.4.21-2 Candidate: 0.4.21-2 Version table: *** 0.4.21-2 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 100 /var/lib/dpkg/status gnome-shell: Installed: 3.26.2-0ubuntu0.1 Candidate: 3.26.2-0ubuntu0.1 Version table: *** 3.26.2-0ubuntu0.1 500 500 http://ca.archive.ubuntu.com/ubuntu artful-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.26.1-0ubuntu4 500 500 http://ca.archive.ubuntu.com/ubuntu artful/main amd64 Packages 3) What do I expect to happen: I expect that when I long press on e and get the popup and select ê, ë that these letter appear 4) they do not. nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/caribou/+bug/1741843/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1494334] Re: tried to open video player but it doesn't open at all no launch error nothing
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. You reported this bug some time ago and there have been many changes in Ubuntu since that time. Ubuntu 14.04 (trusty) reaches end-of-life today. Do you still see the bug in a later supported release of Ubuntu? Please let us know if you do otherwise this report can be left to expire in approximately 60 days time. Thank you for helping make Ubuntu better. Paul White [Ubuntu Bug Squad] ** Changed in: totem (Ubuntu) Status: New => Incomplete -- 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/1494334 Title: tried to open video player but it doesn't open at all no launch error nothing Status in totem package in Ubuntu: Incomplete Bug description: I have tried to play an mp4 video using the default video player . I always prefer defaults over third party but it doesn't open at all . The mouse ticker shows loading but after a few moments nothing loads at all just like I didn't tried to open anything . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: totem 3.10.1-1ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-28.30~14.04.1-generic 3.19.8-ckt5 Uname: Linux 3.19.0-28-generic i686 ApportVersion: 2.14.1-0ubuntu3.13 Architecture: i386 Date: Thu Sep 10 19:50:50 2015 InstallationDate: Installed on 2015-09-08 (1 days ago) InstallationMedia: It SourcePackage: totem SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1494334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807744] Re: Print to File writes to incorrect file
** Also affects: df-libreoffice via https://bugs.documentfoundation.org/show_bug.cgi?id=122075 Importance: Unknown Status: Unknown ** Changed in: libreoffice (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1807744 Title: Print to File writes to incorrect file Status in LibreOffice: Unknown Status in libreoffice package in Ubuntu: Fix Released Bug description: This bug only occurs when using the GTK3 dialogues (libreoffice-gtk3 installed). Under certain conditions print to file over-writes an existing pdf file in the chosen folder which doesn't match the name chosen by the user (and without any warning or confirmation dialog). Steps to reproduce are: 1) Create an empty directory (folder) 2) Put in directory a dummy pdf (e.g. touch sample.pdf) 3) Open libreoffice and create a writer document with a few words 4) Save the libreoffice document to the directory as a regular writer doc (e.g. 'test.odt') 5) Do 'File -> Print' and choose 'Print to File' 6) In the (gtk3) File-chooser dialog: 6a) navigate to the folder created in step 2 6b) select 'Any Type' in the 'types of file shown' selector 6c) click on the file name 'test.odt' 6d) in the 'Name' text field, then edit the name from 'test.odt' to 'test_2.pdf' 6e) then press 'Enter' (or click on 'Select') 7) Observe that in the folder there is no file 'test_2.pdf'. However the dummy file 'sample.pdf' has been over-written and contains the pdf that resulted from the 'print to file' operation -->What should of happened is that the file 'test_2.pdf' should have been created as a pdf of the writer document. -- Some notes: - Occurs in Libreoffice 6.1.2.1 (Build ID: 1:6.1.2-0ubuntu1.1) and older versions - Only occurs using the gtk3 file browser. Native libreoffice is okay (not tested old gtk2 code) - Only occurs if you first click on 'Any Type'. If you simply type a file name without first going to 'Any Type' it doesn't manifest the bug - Only occurs if the file name you type has the '.pdf' extension. If you do a name without it, then it doesn't manifest the bug lsb_release -rd Description: Ubuntu 18.10 Release: 18.10 To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1807744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1808123] Re: [upstream] Fullscreen view lands on another monitor
** Summary changed: - Fullscreen view lands on another monitor + [upstream] Fullscreen view lands on another monitor -- 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/1808123 Title: [upstream] Fullscreen view lands on another monitor Status in LibreOffice: New Status in libreoffice package in Ubuntu: New Bug description: As described above. I work in the classroom with my notebook, to which I have connected a beamer. Sometimes I write things down in the Writer and show it via the beamer. I would like to use the fullscreen mode here. Unfortunately, the fullscreen mode is always displayed on the internal monitor, even if the window with the Writer maximized was previously displayed on the beamer. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 12 10:44:00 2018 InstallationDate: Installed on 2018-11-30 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1808123/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826394] [NEW] IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW
Public bug reported: Have an unusual issue. I have (native) IPv6 on my network. Typically, each connection has two dhclient processes; one for a v4 address, and dhclient with the -6 parameter for the v6 connection. Upon running 'ufw enable' in a console, a firewall is activated. After restarting NetworkManager, only one dhclient process is started by NetworkManager. This was undesirable, so I ran 'ufw disable', and rebooted just to be sure nothing had been left around. All rules gone, but now NetworkManager is point blankly refusing to start a dhclient process for the IPv6 side of networking. I've tried starting NetworkManager with --log-level=DEBUG and watching syslog; nothing seems to indicate that dhclient is even started for IPv6. The only potential indicator of something unusual is 'ipv6.method' being set to 'ignore' periodically, e.g.: Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9076] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9080] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9168] ++ ipv6.method = 'ignore' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9224] ++ ipv6.method = 'ignore' Any clues would be most helpful! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 12:17:43 2019 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco wayland-session -- 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/1826394 Title: IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW Status in network-manager package in Ubuntu: New Bug description: Have an unusual issue. I have (native) IPv6 on my network. Typically, each connection has two dhclient processes; one for a v4 address, and dhclient with the -6 parameter for the v6 connection. Upon running 'ufw enable' in a console, a firewall is activated. After restarting NetworkManager, only one dhclient process is started by NetworkManager. This was undesirable, so I ran 'ufw disable', and rebooted just to be sure nothing had been left around. All rules gone, but now NetworkManager is point blankly refusing to start a dhclient process for the IPv6 side of networking. I've tried starting NetworkManager with --log-level=DEBUG and watching syslog; nothing seems to indicate that dhclient is even started for IPv6. The only potential indicator of something unusual is 'ipv6.method' being set to 'ignore' periodically, e.g.: Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9076] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9080] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9168] ++ ipv6.method = 'ignore' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9224] ++ ipv6.method = 'ignore' Any clues would be most helpful! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 12:17:43 2019 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown NetworkManager.state: [main] NetworkingEnabled=true
[Desktop-packages] [Bug 1826395] [NEW] i tried to print a pdf file using Document viwer and printer prints garbage page
Public bug reported: 1. Ubuntu 19.04 2. HP Deskjet 400, hpcups 3.19.3 Examine the file obtained in the previous step by running the command ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:52:44 2019 InstallationDate: Installed on 2019-03-20 (35 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for HP: socket://172.16.206.55 MachineType: Micro-Star International Co., Ltd. PL62 7RC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=838b2683-bfe0-4dac-8c5e-d920aa70b420 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-18 (6 days ago) dmi.bios.date: 12/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16JDIMS.10A dmi.board.asset.tag: Default string dmi.board.name: MS-16JD dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16JDIMS.10A:bd12/26/2017:svnMicro-StarInternationalCo.,Ltd.:pnPL627RC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16JD:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: PL dmi.product.name: PL62 7RC dmi.product.sku: 16JD.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: cups (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ** Attachment added: "appout" https://bugs.launchpad.net/bugs/1826395/+attachment/5258985/+files/appout -- 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/1826395 Title: i tried to print a pdf file using Document viwer and printer prints garbage page Status in cups package in Ubuntu: New Bug description: 1. Ubuntu 19.04 2. HP Deskjet 400, hpcups 3.19.3 Examine the file obtained in the previous step by running the command ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: cups 2.2.10-4 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:52:44 2019 InstallationDate: Installed on 2019-03-20 (35 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lpstat: device for HP: socket://172.16.206.55 MachineType: Micro-Star International Co., Ltd. PL62 7RC Papersize: a4 PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HP.ppd'] failed with exit code 2: grep: /etc/cups/ppd/HP.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic root=UUID=838b2683-bfe0-4dac-8c5e-d920aa70b420 ro quiet splash vt.handoff=1 SourcePackage: cups UpgradeStatus: Upgraded to disco on 2019-04-18 (6 days ago) dmi.bios.date: 12/26/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16JDIMS.10A dmi.board.asset.tag: Default string dmi.board.name: MS-16JD dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16JDIMS.10A:bd12/26/2017:svnMicro-StarInternationalCo.,Ltd.:pnPL627RC:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16JD:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring: dmi.product.family: PL dmi.product.name: PL62 7RC dmi.product.sku: 16JD.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1826395/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826403] [NEW] Ethernet won't connect when cable is plugged in at boot
Public bug reported: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000 192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-04-25T20:03:28.380204 nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f1 ethernet connectedfull limited /org/freedesktop/NetworkManager/Devices/2 Automatic connection e906293b-df71-435b-8909-7d88ca006540 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0wifi unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled disabled enabled enabled ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1826403 Title: Ethernet won't connect when cable is plugged in at boot Status in network-manager package in Ubuntu: New Bug description: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000
[Desktop-packages] [Bug 1825064] Please test proposed package
Hello Robert, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1825064 Title: Show only reviews from Ubuntu Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Committed Status in gnome-software source package in Disco: Fix Committed Bug description: [Impact] GNOME Software shows all reviews from ODRS, which includes reviews from other distributions. This can be misleading to Ubuntu users, as they may indicate issues or limitations that don't apply in Ubuntu. Solution is to filter reviews to show those reported on Ubuntu only. [Test Case] 1. Open GNOME Software 2. Select an app with reviews Expected result: The reviews should relate to Ubuntu Observed result: Some apps have reviews saying "Failed to start on ", which doesn't occur on Ubuntu. [Regression Potential] A filter was added to check the "distro" field on the review matches the distro GNOME Software is running on. This has a small risk of introducing a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1825064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825064] Please test proposed package
Hello Robert, or anyone else affected, Accepted gnome-software into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.30.2-0ubuntu11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-software (Ubuntu Bionic) Status: Triaged => Fix Committed ** Tags added: verification-needed-bionic -- 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/1825064 Title: Show only reviews from Ubuntu Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Committed Status in gnome-software source package in Disco: Fix Committed Bug description: [Impact] GNOME Software shows all reviews from ODRS, which includes reviews from other distributions. This can be misleading to Ubuntu users, as they may indicate issues or limitations that don't apply in Ubuntu. Solution is to filter reviews to show those reported on Ubuntu only. [Test Case] 1. Open GNOME Software 2. Select an app with reviews Expected result: The reviews should relate to Ubuntu Observed result: Some apps have reviews saying "Failed to start on ", which doesn't occur on Ubuntu. [Regression Potential] A filter was added to check the "distro" field on the review matches the distro GNOME Software is running on. This has a small risk of introducing a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1825064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825064] Re: Show only reviews from Ubuntu
Hello Robert, or anyone else affected, Accepted gnome-software into disco-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.30.6-2ubuntu4 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-disco to verification-done-disco. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-disco. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: gnome-software (Ubuntu Disco) Status: Incomplete => Fix Committed ** Tags added: verification-needed verification-needed-disco ** Changed in: gnome-software (Ubuntu Cosmic) Status: Triaged => Fix Committed ** Tags added: verification-needed-cosmic -- 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/1825064 Title: Show only reviews from Ubuntu Status in gnome-software package in Ubuntu: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in gnome-software source package in Cosmic: Fix Committed Status in gnome-software source package in Disco: Fix Committed Bug description: [Impact] GNOME Software shows all reviews from ODRS, which includes reviews from other distributions. This can be misleading to Ubuntu users, as they may indicate issues or limitations that don't apply in Ubuntu. Solution is to filter reviews to show those reported on Ubuntu only. [Test Case] 1. Open GNOME Software 2. Select an app with reviews Expected result: The reviews should relate to Ubuntu Observed result: Some apps have reviews saying "Failed to start on ", which doesn't occur on Ubuntu. [Regression Potential] A filter was added to check the "distro" field on the review matches the distro GNOME Software is running on. This has a small risk of introducing a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1825064/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799614] Re: Use new media API
Hello Robert, or anyone else affected, Accepted gnome-software into cosmic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.30.2-0ubuntu11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-cosmic to verification-done-cosmic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-cosmic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-cosmic ** Tags added: verification-needed verification-needed-cosmic ** Tags added: verification-needed-bionic -- 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/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Released Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799614] Please test proposed package
Hello Robert, or anyone else affected, Accepted gnome-software into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/gnome- software/3.28.1-0ubuntu4.18.04.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Released Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1798074] Re: LIbreoffice crashes on startup
Sorry for the lack of feedback on that report Stuart. Are you still seeing this startup crash with the latest update for libreoffice on 18.04 (version 1:6.0.7-0ubuntu0.18.04.5)? -- 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/1798074 Title: LIbreoffice crashes on startup Status in libreoffice package in Ubuntu: Confirmed Bug description: On starting up LibreOffice, it crashes. Starting from a terminal with just "libreoffice", I see the "general open a document" libreoffice window and a popup dialog titled "LibreOffice 6.0 Document Recovery", with text "Due to an unexpected error, LibreOffice crashed. All the files you were working on will now be saved. The next time LibreOffice is launched, your files will be recovered automatically. The following files will be recovered:" (and no files to be recovered are listed). Clicking "OK" on this dialog hides it and the general window, and then shows them both again; clicking OK on that dialog exits. LibreOffice does not start. Running "libreoffice --norestore" gives a stack trace: $ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7fa00e2c8568] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3c6)[0x7fa00e2f13c6] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7fa00df02e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7fa00df04801] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5b562)[0x7fa01126a562] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7fa0111f61c2] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d580)[0x7fa01021c580] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cecb6d)[0x7fa0111fbb6d] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7fa00e2cb3b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c28f)[0x7fa00e2f128f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7fa00df02f20] /lib/x86_64-linux-gnu/libc.so.6(+0x18e5a1)[0x7fa00e0525a1] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7fa00c0e7aa4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6972b)[0x7fa01127872b] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9156)[0x7fa00c0dd156] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9398)[0x7fa00c0dd398] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8db66)[0x7fa00c0a1b66] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc0fc2)[0x7fa00c0d4fc2] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d143)[0x7fa00c0a1143] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d179)[0x7fa00c0a1179] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7fa00baf60f5] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c4c0)[0x7fa00baf64c0] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7fa00baf654c] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x414d4)[0x7f9ff8b524d4] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7fa0111f68ce] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7fa0111f8075] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12fa3)[0x7fa010221fa3] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cee756)[0x7fa0111fd756] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7fa0111fd860] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7fa0102430c5] /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x55dd01f4578b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7fa00dee5b97] /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x55dd01f457ca] I have tried entirely removing my profile, ~/.config/libreoffice , but the same problem still exhibits. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libreoffice-common 1:6.0.6-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: MATE Date: Tue Oct 16 12:58:04 2018 InstallationDate: Installed on 2014-04-07 (1653 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: libreoffice UpgradeStatus: Upgraded to bionic on 2018-04-28 (171 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1798074/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819129] Re: No CPU record on Virtualbox
** Description changed:
+ [Impact]
+
+ * Any new report after an installation in a Virtualbox machine won't
+ show up CPU informations.
+
+ [Test Case]
+
+ * Make a new installation in virtualbox
+ * Run "ubuntu-report show".
+ -> you won't have any "CPU" field in the output
+ * Install the new version from proposed
+ * Run "ubuntu-report show"
+ -> note the CPU field is now present.
+
+ [Regression Potential]
+ * The regexp to match lspcu information lines has been relaxed. The
testsuite has been enhanced and existing cases keeps working.
+
+
+
On a virtualbox guest ubuntu-report doesn't report CPU information.
u@pc:~$ ubuntu-report show
{
- "Version": "19.04",
- "OEM": {
- "Vendor": "innotek GmbH",
- "Product": "VirtualBox"
- },
- "BIOS": {
- "Vendor": "innotek GmbH",
- "Version": "VirtualBox"
- },
- "Arch": "amd64",
- "GPU": [
- {
- "Vendor": "15ad",
- "Model": "0405"
- }
- ],
- "RAM": 2,
- "Disks": [
- 21.5
- ],
- "Partitions": [
- 20.5
- ],
- "Screens": [
- {
- "Size": "0mmx0mm",
- "Resolution": "800x600",
- "Frequency": "60.00"
- }
- ],
- "Autologin": true,
- "LivePatch": false,
- "Session": {
- "DE": "ubuntu:GNOME",
- "Name": "ubuntu",
- "Type": "x11"
- },
- "Language": "en_US",
- "Timezone": "America/New_York",
- "Install": {
- "Media": "Ubuntu 19.04 \"Disco Dingo\" - Alpha amd64 (20190305.1)",
- "Type": "GTK",
- "OEM": false,
- "PartitionMethod": "use_device",
- "DownloadUpdates": true,
- "Language": "en",
- "Minimal": false,
- "RestrictedAddons": false,
- "Stages": {
- "0": "language",
- "2": "language",
- "8": "console_setup",
- "16": "console_setup",
- "20": "prepare",
- "24": "partman",
- "26": "start_install",
- "86": "timezone",
- "90": "usersetup",
- "97": "user_done",
- "582": "done"
- }
- }
+ "Version": "19.04",
+ "OEM": {
+ "Vendor": "innotek GmbH",
+ "Product": "VirtualBox"
+ },
+ "BIOS": {
+ "Vendor": "innotek GmbH",
+ "Version": "VirtualBox"
+ },
+ "Arch": "amd64",
+ "GPU": [
+ {
+ "Vendor": "15ad",
+ "Model": "0405"
+ }
+ ],
+ "RAM": 2,
+ "Disks": [
+ 21.5
+ ],
+ "Partitions": [
+ 20.5
+ ],
+ "Screens": [
+ {
+ "Size": "0mmx0mm",
+ "Resolution": "800x600",
+ "Frequency": "60.00"
+ }
+ ],
+ "Autologin": true,
+ "LivePatch": false,
+ "Session": {
+ "DE": "ubuntu:GNOME",
+ "Name": "ubuntu",
+ "Type": "x11"
+ },
+ "Language": "en_US",
+ "Timezone": "America/New_York",
+ "Install": {
+ "Media": "Ubuntu 19.04 \"Disco Dingo\" - Alpha amd64 (20190305.1)",
+ "Type": "GTK",
+ "OEM": false,
+ "PartitionMethod": "use_device",
+ "DownloadUpdates": true,
+ "Language": "en",
+ "Minimal": false,
+ "RestrictedAddons": false,
+ "Stages": {
+ "0": "language",
+ "2": "language",
+ "8": "console_setup",
+ "16": "console_setup",
+ "20": "prepare",
+ "24": "partman",
+ "26": "start_install",
+ "86": "timezone",
+ "90": "usersetup",
+ "97": "user_done",
+ "582": "done"
+ }
+ }
}
-
- @pc:~$ lscpu
+ @pc:~$ lscpu
Architecture:x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 48 bits physical, 48 bits virtual
CPU(s): 1
On-line CPU(s) list: 0
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
NUMA node(s):1
Vendor ID: AuthenticAMD
CPU family: 16
Model: 10
Model name: AMD Phenom(tm) II X6 1055T Processor
Stepping:0
CPU MHz: 2812.342
BogoMIPS:5624.68
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 64K
L1i cache: 64K
L2 cache:512K
L3 cache:6144K
NUMA node0 CPU(s): 0
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt rdtscp
lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid
tsc_known_freq pni monitor cx16 x2apic popcnt hypervisor lahf_lm cr8_legacy abm
sse4a misalignsse 3dnowprefetch vmmcall
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubuntu-report 1.4.0
ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20
Uname: Linux 4.19.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu21
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 8 04:06:58 2019
Dependencies:
- gcc-9-base 9-20190220-0ubuntu1
- libc6 2.28-0ubuntu1
- libgcc1 1:9-20190220-0ubuntu1
- libidn2-0 2.0.5-1
- libunistring2 0.9.10-1ubuntu1
+ gcc-9-base 9-20190220-0ubuntu1
+ libc6 2.28-0ubuntu1
+
[Desktop-packages] [Bug 1737012] Re: Chromium random segfaults: error 4 in libnspr4.so
Thanks for the feedback. Marking fixed per last comment. ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1737012 Title: Chromium random segfaults: error 4 in libnspr4.so Status in chromium-browser package in Ubuntu: Fix Released Bug description: [109127.127307] chromium-browse[15588]: segfault at a1 ip 7f298eb57cc3 sp 7ffc956c8fc0 Just random and seldom crashes. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: chromium-browser 62.0.3202.94-0ubuntu0.17.10.1388 ProcVersionSignature: Ubuntu 4.13.0-18.21-generic 4.13.13 Uname: Linux 4.13.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: XFCE DRM.card0-DVI-D-1: enabled: enabled dpms: On status: connected edid-base64: AP///wBBDAHBomUAAC4aAQOAMx14KtkFpVdRnicPUFS9SwDRwJUAlQ+zAIHAgYCBQAEBAjqAGHE4LUBYLEUA/R4RAAAe/wBVSEIxNjQ2MDI2MDE4/ABQSEwgMjM3RTcKICAg/QA4TB5TEQAKICAgICAgANk= modes: 1920x1080 1680x1050 1280x1024 1280x1024 1440x900 1440x900 1280x960 1280x720 1024x768 1024x768 800x600 800x600 640x480 640x480 640x480 640x480 720x400 DRM.card0-HDMI-A-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: DRM.card0-VGA-1: enabled: disabled dpms: On status: disconnected edid-base64: modes: Date: Thu Dec 7 21:10:33 2017 Desktop-Session: 'xubuntu' '/etc/xdg/xdg-xubuntu:/etc/xdg:/usr/share/kubuntu-default-settings/kf5-settings:/etc/xdg' '/usr/share/xubuntu:/usr/share/xfce4:/home/user/.local/share/flatpak/exports/share:/var/lib/flatpak/exports/share:/usr/local/share:/usr/share:/var/lib/snapd/desktop:/var/lib/snapd/desktop:/usr/share' DetectedPlugins: Env: 'None' 'None' InstallationDate: Installed on 2017-08-28 (101 days ago) InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) Load-Avg-1min: 2.98 Load-Processes-Running-Percent: 0.2% MachineType: ASUS All Series ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.13.0-18-generic.efi.signed root=UUID=355fccdc-c430-43b5-929b-f38e35136c1c ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: chromium-browser UpgradeStatus: Upgraded to artful on 2017-09-16 (81 days ago) dmi.bios.date: 03/10/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0801 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1I-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0801:bd03/10/2016:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnAM1I-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.default.chromium-browser: [deleted] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1737012/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824667] Re: Flash in Chrome does not work
*** This bug is a duplicate of bug 1825497 *** https://bugs.launchpad.net/bugs/1825497 This upstream bug also affects chromium-browser, and is being tracked by bug #1825497. ** This bug has been marked a duplicate of bug 1825497 flash player does not work in chromium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1824667 Title: Flash in Chrome does not work Status in chromium-browser package in Ubuntu: Invalid Bug description: ubuntu 19.04 Flash wbudowany w przeglądarkę Chrome nie działa. Sprawdziłem chromowaną wersję 73 i 74. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1824667/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1514423] Re: package libreoffice-impress 1:4.2.8-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
*** This bug is a duplicate of bug 1824446 *** https://bugs.launchpad.net/bugs/1824446 ** This bug has been marked a duplicate of bug 1824446 package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- 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/1514423 Title: package libreoffice-impress 1:4.2.8-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libreoffice package in Ubuntu: New Bug description: dpkg: error processing package libreoffice-impress (--configure): package is in a very bad inconsistent state; you should reinstall it before attempting configuration Errors were encountered while processing: libreoffice-impress E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libreoffice-impress 1:4.2.8-0ubuntu3 ProcVersionSignature: Ubuntu 3.13.0-66.108-generic 3.13.11-ckt27 Uname: Linux 3.13.0-66-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.18 Architecture: amd64 Date: Mon Nov 9 08:17:04 2015 DuplicateSignature: package:libreoffice-impress:1:4.2.8-0ubuntu3:package is in a very bad inconsistent state; you should reinstall it before attempting configuration ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2015-11-04 (4 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) RelatedPackageVersions: dpkg 1.17.5ubuntu5.4 apt 1.0.1ubuntu2.10 SourcePackage: libreoffice Title: package libreoffice-impress 1:4.2.8-0ubuntu3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1514423/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1593945] Re: package libreoffice-impress 1:5.1.3-0ubuntu1 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten insta
*** This bug is a duplicate of bug 1824446 *** https://bugs.launchpad.net/bugs/1824446 ** This bug has been marked a duplicate of bug 1824446 package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration -- 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/1593945 Title: package libreoffice-impress 1:5.1.3-0ubuntu1 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. Status in libreoffice package in Ubuntu: New Bug description: Update pocedures break up whenever I try to install them. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-impress 1:5.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Jun 17 12:57:59 2016 ErrorMessage: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. InstallationDate: Installed on 2016-05-26 (22 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.10ubuntu1 SourcePackage: libreoffice Title: package libreoffice-impress 1:5.1.3-0ubuntu1 failed to install/upgrade: pakket verkeert in een heel slechte en inconsistente staat; u zou het opnieuw moeten installeren alvorens het te configureren. UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1593945/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825919] Re: Gedit right click context menu stops working
Apr 25 10:17:42 PS006 systemd[1]: snapd.service: Succeeded. Apr 25 10:17:45 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != NULL' failed Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:17:45 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Logs' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.ControlCenter.SearchProvider' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Calculator.SearchProvider' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="u Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Characters.BackgroundService' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.clocks' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.ControlCenter.SearchProvider' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.clocks' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:20 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Characters.BackgroundService' Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.Calculator.SearchProvider' Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: M Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after attribute name “Less-than” of element “:” Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:21 PS006 systemd[1]: Starting Snappy daemon... Apr 25 10:19:21 PS006 snapd[1036]: AppArmor status: apparmor is enabled and all features are available Apr 25 10:19:21 PS006 snapd[1036]: daemon.go:379: started snapd/2.38+19.04 (series 16; classic) ubuntu/19.04 (amd64) linux/5.0.0-13-generic. Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:21 PS006 systemd[1]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1745]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1217]: tmp-sanity\x2dmountpoint\x2d888950326.mount: Succeeded. Apr 25 10:19:21 PS006 systemd[1]: Started Snappy daemon. Apr 25 10:19:21 PS006 gnome-shell[1936]: Failed to set the markup of the actor 'ClutterText': Error on line 1 char 28: Odd character “S”, expected a “=” after attribute name “Less-than” of element “:” Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.seahorse.Application' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconf Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Successfully activated service 'org.gnome.seahorse.Application' Apr 25 10:19:21 PS006 gnome-shell[1936]: Received error from DBus search provider org.gnome.seahorse.Application.desktop during GetResultMetas: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.UnknownMet Apr 25 10:19:21 PS006 gnome-shell[1936]: Wrong number of result metas returned by search provider org.gnome.seahorse.Application.desktop: expected 1 but got 0 Apr 25 10:19:21 PS006 gnome-shell[1936]: g_environ_setenv: assertion 'value != NULL' failed Apr 25 10:19:21 PS006 dbus-daemon[1774]: [session uid=1000 pid=1774] Activating service name='org.gnome.Logs' requested by ':1.15' (uid=1000 pid=1936 comm="/usr/bin/gnome-shell " label="unconfined") Apr 25 10:19:21 PS006
[Desktop-packages] [Bug 1812563] Re: The Chromium window is corrupted only on initial startup.
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Is this issue still happening with the latest version of chromium? Could you please attach additional information to the bug report by running the following command in a terminal: apport-collect 1812563 Thanks in advance! ** Changed in: chromium-browser (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1812563 Title: The Chromium window is corrupted only on initial startup. Status in Ubuntu Manual Tests: Invalid Status in chromium-browser package in Ubuntu: Incomplete Bug description: The Chromium window is corrupted only on it's first launch. Both on VM and acer laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-manual-tests/+bug/1812563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824446] Re: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libreoffice (Ubuntu) Status: New => Confirmed -- 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/1824446 Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libreoffice package in Ubuntu: Confirmed Bug description: it does not get updated with sudo apt-get update and keeps causing problems ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 21:24:06 2019 DpkgHistoryLog: Start-Date: 2019-04-10 21:23:53 Commandline: apt-get -f install Requested-By: vinaya (1000) Upgrade: libreoffice-core:amd64 (1:5.1.6~rc2-0ubuntu1~xenial3, 1:5.1.6~rc2-0ubuntu1~xenial6) DuplicateSignature: package:libreoffice-impress:1:5.1.6~rc2-0ubuntu1~xenial6 Setting up libreoffice-gnome (1:5.1.6~rc2-0ubuntu1~xenial6) ... dpkg: error processing package libreoffice-impress (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-08-27 (592 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.29ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1824446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824446] Re: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before at
Please try running the following command and let us know whether that fixes the problem: sudo apt install --reinstall libreoffice-impress -- 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/1824446 Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in libreoffice package in Ubuntu: Confirmed Bug description: it does not get updated with sudo apt-get update and keeps causing problems ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Wed Apr 10 21:24:06 2019 DpkgHistoryLog: Start-Date: 2019-04-10 21:23:53 Commandline: apt-get -f install Requested-By: vinaya (1000) Upgrade: libreoffice-core:amd64 (1:5.1.6~rc2-0ubuntu1~xenial3, 1:5.1.6~rc2-0ubuntu1~xenial6) DuplicateSignature: package:libreoffice-impress:1:5.1.6~rc2-0ubuntu1~xenial6 Setting up libreoffice-gnome (1:5.1.6~rc2-0ubuntu1~xenial6) ... dpkg: error processing package libreoffice-impress (--configure): package is in a very bad inconsistent state; you should ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2017-08-27 (592 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.29ubuntu0.1 SourcePackage: libreoffice Title: package libreoffice-impress 1:5.1.6~rc2-0ubuntu1~xenial6 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1824446/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1799614] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1799614 Title: Use new media API Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Committed Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Committed Status in snapd-glib source package in Cosmic: Fix Released Bug description: [Impact] snapd now provides 'media' which replaces the old 'screenshots' data. We need to migrate to this as the old screenshot data will be removed in the future. [Test Case] Run gnome-software with updated snapd-glib and confirm that screenshots and promoted snap banners continue to work. [Regression Potential] Possibility of new errors being introduced in updated code paths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1799614/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825919] Re: Gedit right click context menu stops working
It just happened now... When this happened, I had right clicked on a misspelled work in a Firefox text area. I didn't get a popup context menu; I thought it was just Firefox acting up. So, I switched to my open Gedit window, to cut the correctly spelled word from my text document, and the context menu in Gedit wouldn't work either. It didn't work for a while. But as I started to research and copy logs in order to collect information to post here, the right click context menu magically started to work again, after some time. I'll post the journalctl out put here. The issue happened around 10:19 in the logs... -- 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/1825919 Title: Gedit right click context menu stops working Status in gedit package in Ubuntu: Incomplete Bug description: The Gedit text area right-click context menu stops appearing. This bug affects Ubuntu 19.04, but may be a regression of old Bug #1731581 from Ubuntu 17.10. Gedit version: 3.32.0-3 Fresh install of Ubuntu 19.04 gkt-3 version: 3.24.8-1ubuntu1 RECREATING ISSUE When I first log in, the right-click context menus in Gedit works fine. After some time of usage, the right-click context menu no longer appears. SIDE-EFFECT A side-effect of this issue is that the mouse cursor does not revert to a pointer style after doing a right-click. It retains the "I" (Insert) shape even when you hover outside Gedit's text area. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1825919/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826081] Re: Ability to automatically arrange desktop icons gone in 19.04
** Changed in: gnome-shell-extension-desktop-icons Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-desktop-icons in Ubuntu. https://bugs.launchpad.net/bugs/1826081 Title: Ability to automatically arrange desktop icons gone in 19.04 Status in gnome-shell-extension-desktop-icons: Fix Released Status in gnome-shell-extension-desktop-icons package in Ubuntu: Triaged Bug description: Upgraded from Ubuntu 18.10 to Ubuntu 19.04. On the upside, Ubuntu 19.04 now handles my unusual desktop geometry, and displays desktop icons within physical monitor dimensions (I have one landscape, one portrait display). The downside is there's no sort option for desktop icons anymore. Icons are snapped to grid automatically, but all arrangement for now is manual. The restoration of "Sort by name" functionality at the very least, and perhaps the addition of "Sort by type" would be even better. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell-extension-desktop-icons/+bug/1826081/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826420] [NEW] Nautilus disk properties shows black circle
Public bug reported: Ubuntu 19.04 / Nautilus 3.32.0 stable (?) Mounting a disk (which does not show on the desktop may I add here as well) and asking for disk properties gives a black circle. Expected behaviour: different colours for used and unused parts, maybe gray for the unusable meta data. Current behaviour: a black disk telling me nothing. (I have no idea as to why a perfectly working file manager had to get crippled further, but someone managed). I do have a custom theme but it happens with the default theme as well. (Sorry my tone gets harsher every time but I really get tired being an alpha tester). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:48:33 2019 InstallationDate: Installed on 2018-04-30 (360 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-19 (5 days ago) usr_lib_nautilus: ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "So much information" https://bugs.launchpad.net/bugs/1826420/+attachment/5259049/+files/Screenshot%20from%202019-04-25%2016-48-58.png -- 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/1826420 Title: Nautilus disk properties shows black circle Status in nautilus package in Ubuntu: New Bug description: Ubuntu 19.04 / Nautilus 3.32.0 stable (?) Mounting a disk (which does not show on the desktop may I add here as well) and asking for disk properties gives a black circle. Expected behaviour: different colours for used and unused parts, maybe gray for the unusable meta data. Current behaviour: a black disk telling me nothing. (I have no idea as to why a perfectly working file manager had to get crippled further, but someone managed). I do have a custom theme but it happens with the default theme as well. (Sorry my tone gets harsher every time but I really get tired being an alpha tester). ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 16:48:33 2019 InstallationDate: Installed on 2018-04-30 (360 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: nautilus UpgradeStatus: Upgraded to disco on 2019-04-19 (5 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1826420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
Update to 2 hours ago: Started getting segfault problems with libglib. Again re-install fixed that but then I was getting segfaults elsewhere too. I have now reverted to a full system backup of 18.10 that I made earlier && will probably stay on that for a bit longer. -- 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/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash 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. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
I went back to the 4.18 kernel but am not running VirtualBox (running bare metal). Also seeing issues with libglib. gnome-shell won't run due to a trap in libglib-2.0.so: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826025 -- 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/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: New Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: In Progress Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash 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. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792329] Re: Firefox freezes continuously on Ubuntu 16.04
Stefano, can you elaborate on the exact problem you're seeing now? Is there a series of steps that can reliably reproduce the problem? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1792329 Title: Firefox freezes continuously on Ubuntu 16.04 Status in firefox package in Ubuntu: New Bug description: FireFox 62 freezes continuously. (64 bit Ubuntu 16.04.5) Lock mouse and keyboard on Ubuntu, I have to switch off with the On / Off button. Minor defect, but appeared simultaneously, I open a second / third page, do not load, I go back to the previous one and is no longer loaded, you only see the wheel of time. In this case, restart Firefox. glxinfo | grep "OpenGL version" OpenGL version string: 3.0 Mesa 18.0.5 WM_CLASS(STRING) = "Navigator", "Firefox" Description: Ubuntu 16.04.5 LTS Release: 16.04 Intel® Celeron(R) CPU N2840 @ 2.16GHz × 2 Intel® Bay Trail --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stefano1933 F...m pulseaudio /dev/snd/controlC0: stefano1933 F pulseaudio BuildID: 20181023214907 Channel: Unavailable CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-12 (59 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.3 metric 600 Locales: extensions.sqlite corrupt or missing Package: firefox 63.0+build2-0ubuntu0.16.04.2 PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Profiles: Profile0 (Default) - LastVersion=63.0/20181023214907 (In use) RunningIncompatibleAddons: False Tags: xenial Themes: extensions.sqlite corrupt or missing Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1792329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1823363] Re: Running "Junk Mail Controls" does not appear in Activity Manager
Thanks Paul for the upstream report! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1823363 Title: Running "Junk Mail Controls" does not appear in Activity Manager Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: "Running Junk Mail Controls" does not appear in Activity Manager ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jeb3837 F pulseaudio /dev/snd/controlC1: jeb3837 F pulseaudio /dev/snd/controlC0: jeb3837 F pulseaudio BuildID: 20190325141154 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 11:09:14 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-08-17 (231 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src 192.168.86.25 metric 600 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 linkdown Locales: extensions.sqlite corrupt or missing MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 PrefSources: prefs.js ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use) RunningIncompatibleAddons: False SourcePackage: thunderbird SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 Themes: extensions.sqlite corrupt or missing UpgradeStatus: Upgraded to cosmic on 2018-10-19 (168 days ago) dmi.bios.date: 09/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A880G+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A880G+ dmi.product.sku: To Be Filled By O.E.M. dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/thunderbird/+bug/1823363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789336] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1789336 Title: Show publisher display name and verified status Status in gnome-software package in Ubuntu: Fix Released Status in snapd-glib package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Released Status in snapd-glib source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Status in snapd-glib source package in Cosmic: Fix Released Bug description: [Impact] snapd now provides the display name for a snap (e.g. "Skype" instead of the username "skype") and the validation status for the account (used to show a tick against special accounts). This should be shown in GNOME Software. [Test Case] 1. Open GNOME Software 2. Select Skype Expected outcome: Developer is shown as "Skype" and account has tick icon beside it. Observed result: Developer is shown as "skype" and account has no tick icon. [Regression Potential] Chance of new parsing and UI code introducing bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1789336/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1754655] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1754655 Title: Installing snap from command line confuses GNOME Software Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Artful: Won't Fix Status in gnome-software source package in Bionic: Fix Released Bug description: [Impact] Installing snaps from the command line (or any other client) causes the state in GNOME Software to wrongly represented. [Test Case] 1. Ensure you don't have moon-buggy installed $ sudo snap remove moon-buggy 2. Start GNOME Software 3. Install moon-buggy from the command line: $ sudo snap install moon-buggy 4. Search for "moon" in GNOME Software Expected result: Moon Buggy shows in search results as installed Observed result: Moon Buggy not returned in search results. [Regression Potential] Low, we fix a bug where were reading invalid metadata and a check that makes stops unexpected (but valid) state notification from the snap plugin. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1754655/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1790563] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1790563 Title: Many JsonArray critical warnings on command line Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Bug description: [Impact] Running GNOME Software gives many JsonArray warnings on the command line: Json-CRITICAL **: json_object_get_array_member: assertion 'node != NULL' failed Json-CRITICAL **: json_array_get_length: assertion 'array != NULL' failed This is due to the code not handling there being no plugs defined in the interface table (which is valid when it is empty). [Test Case] 1. Run GNOME Software from the command line $ killall gnome-software $ gnome-software Expected result: No JsonArray critical warnings are show. Observed result: Many JsonArray critical warnings are show. [Regression Potential] Risk of additional checks breaking expected behaviour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1790563/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778160] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1778160 Title: /usr/bin/gnome- software:11:g_type_check_instance:g_signal_emit_valist:g_signal_emit:g_closure_invoke:signal_emit_unlocked_R Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Fix Released Bug description: [Impact] Configuring the permissions for a snap that has a plug that can connect to multiple slots causes a crash: https://errors.ubuntu.com/problem/46232e57fbbc469ce3e5f5c0f12bc24f95cd27c6 [Test Case] 1. Open GNOME Software 2. Search for and install TBD snap 3. Open Permissions dialog 4. Toggle TBD permission that uses a combo box Expected result: Permission is changed Observed result: GNOME Software crashes [Regression Potential] Fix is to rename a signal to avoid a name collision, low chance of introducing new bugs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1778160/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1738164] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1738164 Title: [snap] U2F doesn't work with yubikey Status in chromium-browser package in Ubuntu: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Status in gnome-software source package in Bionic: Fix Released Status in gnome-software source package in Cosmic: Confirmed Bug description: [Impact] Installing a snap that requires the u2f-devices interface doesn't show a UI element to enable/disable this in GNOME Software. Initially Chromium didn't have this enabled by default, and thus the feature wouldn't work without going to the command line. It now is enabled by default. [Test Case] 1. Open GNOME Software 2. Install the Chromium snap 3. Click "Permissions" Expected result: A switch is shown to control "Read/write access to U2F devices exposed". Clicking it connects/disconnects the u2f-devices interface. Observed result: No switch is shown for this interface. [Regression Potential] A string for this interface was added to GNOME Software, low risk of introducing a new bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1738164/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1778135] Proposed package upload rejected
An upload of gnome-software to xenial-proposed has been rejected from the upload queue for the following reason: "Since this upload includes the same change for 'new media API' as others, I would feel much safer if we set a minimal version depenency to libsnapd-glib-dev (>= 1.45) - since it seems there was more than one snapd-glib version in xenial.". -- 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/1778135 Title: /usr/bin/gnome- software:11:as_icon_get_name:gs_refine_item_pixbuf:gs_appstream_refine_app:gs_plugin_refine_from_pkgname:gs_plugin_refine_app Status in GNOME Software: Fix Released Status in gnome-software package in Ubuntu: Fix Released Status in gnome-software source package in Xenial: Fix Committed Bug description: [Impact] GNOME Software can crash when failing to get an icon from the cache: https://errors.ubuntu.com/problem/333736cd145e0c8722aba054d9d202310b1447f0 [Test Case] Run updated version on a system that is hitting the problem, observe crash no longer occurs. [Regression Potential] Low, the fix is cherry-picked from a newer branch and fixes and obvious NULL pointer dereference. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-software/+bug/1778135/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1748839] Re: Problem to connect to WPA2/PEAP WIFI - gnome-shell
Nothing helpful in this post but can confirm this issue still exists in 19.04. :( -- 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/1748839 Title: Problem to connect to WPA2/PEAP WIFI - gnome-shell Status in network-manager package in Ubuntu: Confirmed Bug description: This problem is also happened on my desktop. After upgrading OS from Ubuntu 16.04 to Ubuntu 18.04.1 LTS, my PC could not connect and authenticate on WiFi with WPA2/PEAP/MSCHAPv2/no CA certificate/true username and password. I tried to solve the problem following URL link; however, it could not help me also. https://askubuntu.com/questions/279762/how-to-connect-to-wpa2-peap-mschapv2-enterprise-wifi-networks-that-dont-use-a-c My PC is HP Compaq Pro 4300, CPU: Intel® Core™ i3-3220 CPU @ 3.30GHz × 4, OS: Ubuntu 18.04.1 (64-bit). root@joe-UBTPC:/root # lspci 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04) 00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5) 00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5) 00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 3 (rev b5) 00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5) 00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5) 00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5) 00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05) 00:1f.0 ISA bridge: Intel Corporation H61 Express Chipset Family LPC Controller (rev 05) 00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family SATA AHCI Controller (rev 05) 00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05) 03:00.0 Network controller: Ralink corp. RT5392 PCIe Wireless Network Adapter 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1748839/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826415] [NEW] Videos do not play in presentation mode
Public bug reported: It is not possible to play embedded videos in the presentation mode. This affects PDF slides created with the beamer/multimedia latex package. Initially, no controls are shown on the slide with the video. In the normal mode, video controls appear when the video is clicked with the mouse. However, in the presentation mode, evince goes to the next page when one clicks with the mouse so that the controls do not appear and the video can only be played by exiting the presentation mode. Playing videos works fine in presentation mode with the okular PDF- viewer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 Uname: Linux 4.15.0-041500rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 16:15:43 2019 InstallationDate: Installed on 2015-11-05 (1267 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: evince UpgradeStatus: Upgraded to bionic on 2018-05-24 (335 days ago) ** Affects: evince (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug bionic -- 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/1826415 Title: Videos do not play in presentation mode Status in evince package in Ubuntu: New Bug description: It is not possible to play embedded videos in the presentation mode. This affects PDF slides created with the beamer/multimedia latex package. Initially, no controls are shown on the slide with the video. In the normal mode, video controls appear when the video is clicked with the mouse. However, in the presentation mode, evince goes to the next page when one clicks with the mouse so that the controls do not appear and the video can only be played by exiting the presentation mode. Playing videos works fine in presentation mode with the okular PDF-viewer. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: evince 3.28.4-0ubuntu1 Uname: Linux 4.15.0-041500rc6-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 16:15:43 2019 InstallationDate: Installed on 2015-11-05 (1267 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) SourcePackage: evince UpgradeStatus: Upgraded to bionic on 2018-05-24 (335 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1826415/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1823363] Re: Running "Junk Mail Controls" does not appear in Activity Manager
Thank you for thanking me and letting me know! It's greatly appreciated. On Thu, Apr 25, 2019, 9:20 AM Olivier Tilloy wrote: > Thanks Paul for the upstream report! > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1823363 > > Title: > Running "Junk Mail Controls" does not appear in Activity Manager > > Status in Mozilla Thunderbird: > Confirmed > Status in thunderbird package in Ubuntu: > Confirmed > > Bug description: > "Running Junk Mail Controls" does not appear in Activity Manager > > ProblemType: Bug > DistroRelease: Ubuntu 18.10 > Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1 > ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 > Uname: Linux 4.18.0-17-generic x86_64 > AddonCompatCheckDisabled: False > ApportVersion: 2.20.10-0ubuntu13.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC2: jeb3837 F pulseaudio >/dev/snd/controlC1: jeb3837 F pulseaudio >/dev/snd/controlC0: jeb3837 F pulseaudio > BuildID: 20190325141154 > Channel: Unavailable > CurrentDesktop: ubuntu:GNOME > Date: Fri Apr 5 11:09:14 2019 > Extensions: extensions.sqlite corrupt or missing > ForcedLayersAccel: False > IfupdownConfig: ># interfaces(5) file used by ifup(8) and ifdown(8) >auto lo >iface lo inet loopback > IncompatibleExtensions: Unavailable (corrupt or non-existant > compatibility.ini or extensions.sqlite) > InstallationDate: Installed on 2018-08-17 (231 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > IpRoute: >default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 >169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000 >192.168.86.0/24 dev wlx7cdd90a9ad27 proto kernel scope link src > 192.168.86.25 metric 600 >192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 > linkdown > Locales: extensions.sqlite corrupt or missing > MostRecentCrashID: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 > PrefSources: prefs.js > ProcEnviron: >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=en_US.UTF-8 >SHELL=/bin/bash > Profiles: Profile0 (Default) - LastVersion=60.6.1/20190325141154 (In use) > RunningIncompatibleAddons: False > SourcePackage: thunderbird > SubmittedCrashIDs: bp-28d5ae3f-24c9-47bb-9bd3-c0fb10180818 > Themes: extensions.sqlite corrupt or missing > UpgradeStatus: Upgraded to cosmic on 2018-10-19 (168 days ago) > dmi.bios.date: 09/21/2011 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 080016 > dmi.board.asset.tag: To Be Filled By O.E.M. > dmi.board.name: A880G+ > dmi.board.vendor: BIOSTAR Group > dmi.chassis.asset.tag: None > dmi.chassis.type: 3 > dmi.chassis.vendor: BIOSTAR Group > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: > dmi.product.family: To Be Filled By O.E.M. > dmi.product.name: A880G+ > dmi.product.sku: To Be Filled By O.E.M. > dmi.sys.vendor: BIOSTAR Group > > To manage notifications about this bug go to: > https://bugs.launchpad.net/thunderbird/+bug/1823363/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to thunderbird in Ubuntu. https://bugs.launchpad.net/bugs/1823363 Title: Running "Junk Mail Controls" does not appear in Activity Manager Status in Mozilla Thunderbird: Confirmed Status in thunderbird package in Ubuntu: Confirmed Bug description: "Running Junk Mail Controls" does not appear in Activity Manager ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: thunderbird 1:60.6.1+build2-0ubuntu0.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu13.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: jeb3837 F pulseaudio /dev/snd/controlC1: jeb3837 F pulseaudio /dev/snd/controlC0: jeb3837 F pulseaudio BuildID: 20190325141154 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Fri Apr 5 11:09:14 2019 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-08-17 (231 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) IpRoute: default via 192.168.86.1 dev wlx7cdd90a9ad27 proto dhcp metric 600 169.254.0.0/16 dev wlx7cdd90a9ad27 scope link metric 1000
[Desktop-packages] [Bug 1798790] Re: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)
WaylandEnable=false workaround also works for 19.04 Nvidia 340 and 390 drivers still having issues with 19.04 but does not seem to be the cause of the gdm problem. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1798790 Title: Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it) Status in gdm3 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: https://gitlab.gnome.org/GNOME/gdm/issues/435 --- The boot process hangs with the last message being "started bpfilter". There is unusual Network activity during that time. The light of the WiFi adapter is blinking a lot. I am not sure the problem is with the gdm3 package. As a matter of fact, I would remove it and let someone more experienced to set it. I'm afraid I might break something, though. The specific steps or actions you took that caused you to encounter the problem: 1. Boot Ubuntu 18.10 with the Nvidia proprietary drivers installed. The behavior you expected: I expected Ubuntu 18.10 to boot normally. The behavior you actually encountered: The computer gets stuck in a command-like environment with the last message being "started bpfilter". You can't type any commands. I have found that uninstalling the Nvidia proprietary drivers by going into recovery mode fixes the issue. Booting with the earlier kernel doesn't fix the issue. Installing the earlier v.340 driver also doesn't fix the issue. This (https://askubuntu.com/questions/1032639/ubuntu-18-04-stuck-in- boot-after-starting-gnome-display-manager-on-intel-graphic) seems relevant. This is where I found the "solution". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
Same.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}
Hopefully we can get Mozilla to up the limit for the API key.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1787332] Re: Xorg crashed with SIGABRT in OsAbort() from AbortServer() from FatalError("EnterVT failed for screen ...") from xf86VTEnter() from systemd_logind_vtenter()
This bug seems to have stopped for me a couple of months back. Now I get
black screens that have to be toggled off and back on with xrandr before
they display again after undocking/redocking.
That's a minor inconvenience compared to a crashing desktop environment,
so I'm quite happy. It would be good to know if anyone else has seen an
improvement in this behavior.
--
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/1787332
Title:
Xorg crashed with SIGABRT in OsAbort() from AbortServer() from
FatalError("EnterVT failed for screen ...") from xf86VTEnter() from
systemd_logind_vtenter()
Status in xorg-server package in Ubuntu:
Confirmed
Bug description:
.
ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: xserver-xorg-core 2:1.19.6-1ubuntu4
ProcVersionSignature: Ubuntu 4.17.0-6.7-generic 4.17.9
Uname: Linux 4.17.0-6-generic x86_64
ApportVersion: 2.20.10-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for
`/apps/compiz-1/general/screen0/options/active_plugins'
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 16 14:15:46 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExecutablePath: /usr/lib/xorg/Xorg
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA
controller])
Subsystem: Lenovo HD Graphics 630 [17aa:3102]
InstallationDate: Installed on 2018-05-26 (81 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180525)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 17ef:6009 Lenovo ThinkPad Keyboard with TrackPoint
Bus 001 Device 003: ID 045e:0047 Microsoft Corp. IntelliMouse Explorer 3.0
Bus 001 Device 002: ID 8087:0a2b Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 10M7CTO1WW
ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth
/run/user/1000/gdm/Xauthority -background none -noreset -keeptty -verbose 7
-core
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_AU.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-6-generic
root=UUID=d7ecc709-02c2-4413-b7e7-dfce1d2b3703 ro quiet splash vt.handoff=1
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
()
()
()
xf86VTEnter ()
()
Title: Xorg crashed with SIGABRT
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/06/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: M16KT47A
dmi.board.name: 3102
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN 3259627060530
dmi.chassis.type: 3
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias:
dmi:bvnLENOVO:bvrM16KT47A:bd02/06/2018:svnLENOVO:pn10M7CTO1WW:pvrThinkCentreM710s:rvnLENOVO:rn3102:rvrSDK0J40709WIN3259627060530:cvnLENOVO:ct3:cvrNone:
dmi.product.family: ThinkCentre M710s
dmi.product.name: 10M7CTO1WW
dmi.product.version: ThinkCentre M710s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.93-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1787332/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826468] [NEW] Libreoffice Calc cannot export PDF to a network drive
Public bug reported: After upgrading from 18.10 to 19.04 I lost possibility to export a document to PDF, if a document is on a network drive (it's a DAVS network folder in my case). I receive a pop-up windows about general I/O error. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 23:35:20 2019 InstallationDate: Installed on 2018-05-05 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- 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/1826468 Title: Libreoffice Calc cannot export PDF to a network drive Status in libreoffice package in Ubuntu: New Bug description: After upgrading from 18.10 to 19.04 I lost possibility to export a document to PDF, if a document is on a network drive (it's a DAVS network folder in my case). I receive a pop-up windows about general I/O error. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libreoffice (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 23:35:20 2019 InstallationDate: Installed on 2018-05-05 (355 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/usr/bin/fish SourcePackage: libreoffice UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1826468/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826394] Re: IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW
Additional information: I've tried to reproduce this with a virtual machine to no effect - including installing cosmic, enabling firewall, upgrading to disco and seeing if it still occurs. As of yet, I have not managed to reproduce it (save for the fact that this exact problem is affecting two disco installations with very similar software setup). I will continue trying to reproduce and update when I have more information. -- 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/1826394 Title: IPv6 not being brought up on interface after enabling (and subsequently disabling & rebooting) UFW Status in network-manager package in Ubuntu: New Bug description: Have an unusual issue. I have (native) IPv6 on my network. Typically, each connection has two dhclient processes; one for a v4 address, and dhclient with the -6 parameter for the v6 connection. Upon running 'ufw enable' in a console, a firewall is activated. After restarting NetworkManager, only one dhclient process is started by NetworkManager. This was undesirable, so I ran 'ufw disable', and rebooted just to be sure nothing had been left around. All rules gone, but now NetworkManager is point blankly refusing to start a dhclient process for the IPv6 side of networking. I've tried starting NetworkManager with --log-level=DEBUG and watching syslog; nothing seems to indicate that dhclient is even started for IPv6. The only potential indicator of something unusual is 'ipv6.method' being set to 'ignore' periodically, e.g.: Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9076] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9080] ++ ipv6.method = 'auto' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9168] ++ ipv6.method = 'ignore' Apr 25 11:22:57 lpt00258lin-gorgonzola NetworkManager[9238]: [155618.9224] ++ ipv6.method = 'ignore' Any clues would be most helpful! ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Apr 25 12:17:43 2019 IfupdownConfig: # ifupdown has been replaced by netplan(5) on this system. See # /etc/netplan for current configuration. # To re-enable ifupdown on this system, you can run: #sudo apt install ifupdown NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/zsh SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-23 (2 days ago) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1826394/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1826290] Re: geoclue mozilla location api key rate limited
I tried it around 02:00 UTC on 25 April so the daily limit was probably
reset by the time you tested it. I did check around and came across this
issue on geoclue's GitLab
https://gitlab.freedesktop.org/geoclue/geoclue/issues/101
The geoclue key probably has a high daily limit but it's probably being
reached a few hours before the daily limit is reset.
** Bug watch added: gitlab.freedesktop.org/geoclue/geoclue/issues #101
https://gitlab.freedesktop.org/geoclue/geoclue/issues/101
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to geoclue-2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1826290
Title:
geoclue mozilla location api key rate limited
Status in geoclue-2.0 package in Ubuntu:
Confirmed
Bug description:
I am using Ubuntu 19.04
geoclue version: 0.12.99-4ubuntu2
geoclue2 version: 2.5.2-1ubuntu1
The key used by geoclue in ubuntu to access the mozilla location
service appears to be rate limited.
Here's the relevant lines in /etc/geoclue/geoclue.conf
# URL to the wifi geolocation service. The key can currenty be anything, just
# needs to be present but that is likely going to change in future.
url=https://location.services.mozilla.com/v1/geolocate?key=geoclue
The comment is wrong, using an invalid key gives a 400 error.
$ curl https://location.services.mozilla.com/v1/geolocate\?key=random_key
{"error":{"code":400,"message":"Missing or invalid API
key.","errors":[{"domain":"usageLimits","message":"Missing or invalid API
key.","reason":"keyInvalid"}]}}%
Using the current key gives a limit reached error
$ curl https://location.services.mozilla.com/v1/geolocate\?key=geoclue
{"error":{"code":403,"message":"You have exceeded your daily
limit.","errors":[{"domain":"usageLimits","message":"You have exceeded your
daily limit.","reason":"dailyLimitExceeded"}]}}%
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1826290/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1792329] Re: Firefox freezes continuously on Ubuntu 16.04
It happens with more than one open card, especially with Facebook. I have the swap configured, with Ubuntu it can be about 300 Mb in swap. It seems to me that random happens without apparent similarities between the cases, and since February it has never happened again. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1792329 Title: Firefox freezes continuously on Ubuntu 16.04 Status in firefox package in Ubuntu: New Bug description: FireFox 62 freezes continuously. (64 bit Ubuntu 16.04.5) Lock mouse and keyboard on Ubuntu, I have to switch off with the On / Off button. Minor defect, but appeared simultaneously, I open a second / third page, do not load, I go back to the previous one and is no longer loaded, you only see the wheel of time. In this case, restart Firefox. glxinfo | grep "OpenGL version" OpenGL version string: 3.0 Mesa 18.0.5 WM_CLASS(STRING) = "Navigator", "Firefox" Description: Ubuntu 16.04.5 LTS Release: 16.04 Intel® Celeron(R) CPU N2840 @ 2.16GHz × 2 Intel® Bay Trail --- AddonCompatCheckDisabled: False ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: stefano1933 F...m pulseaudio /dev/snd/controlC0: stefano1933 F pulseaudio BuildID: 20181023214907 Channel: Unavailable CurrentDesktop: Unity DistroRelease: Ubuntu 16.04 Extensions: extensions.sqlite corrupt or missing ForcedLayersAccel: False IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IncompatibleExtensions: Unavailable (corrupt or non-existant compatibility.ini or extensions.sqlite) InstallationDate: Installed on 2018-09-12 (59 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IpRoute: default via 192.168.1.1 dev wlp2s0 proto static metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.3 metric 600 Locales: extensions.sqlite corrupt or missing Package: firefox 63.0+build2-0ubuntu0.16.04.2 PackageArchitecture: amd64 Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so PrefSources: prefs.js ProcVersionSignature: Ubuntu 4.15.0-38.41~16.04.1-generic 4.15.18 Profiles: Profile0 (Default) - LastVersion=63.0/20181023214907 (In use) RunningIncompatibleAddons: False Tags: xenial Themes: extensions.sqlite corrupt or missing Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2014 dmi.bios.vendor: LENOVO dmi.bios.version: A7CN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Lancer 5A6 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82993WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-30 dmi.modalias: dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30: dmi.product.family: IDEAPAD dmi.product.name: 80G0 dmi.product.version: Lenovo G50-30 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1792329/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825735] Re: Display is corrupted after waking from sleep
*** This bug is a duplicate of bug 1809407 *** https://bugs.launchpad.net/bugs/1809407 Another thing that I have noticed is that this problem only arises when I click suspend or close the lid. If the laptop naturally goes sleep then this problem doesn't occur. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1825735 Title: Display is corrupted after waking from sleep Status in xorg package in Ubuntu: New Bug description: After I shut the lid of the laptop and turn it back on, I see my open windows for a second and then the lock screen appears. When I log in, my wallpaper is replaced with the image I have attached. This image is also shown in the lock screen. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.116 Sun Jan 27 07:21:36 PST 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Apr 21 13:58:09 2019 DistUpgraded: 2019-04-18 21:28:53,352 DEBUG icon theme changed, re-reading DistroCodename: disco DistroVariant: ubuntu DkmsStatus: nvidia, 390.116, 4.18.0-17-generic, x86_64: installed nvidia, 390.116, 5.0.0-13-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83f9] Subsystem: Hewlett-Packard Company GM108M [GeForce 940MX] [103c:83f9] InstallationDate: Installed on 2019-04-16 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0aa7 Intel Corp. Bus 001 Device 003: ID 05c8:03ab Cheng Uei Precision Industry Co., Ltd (Foxlink) Bus 001 Device 002: ID 275d:0ba6 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Pavilion Laptop 15-cc1xx ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to disco on 2019-04-19 (2 days ago) dmi.bios.date: 01/12/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.26 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 83F9 dmi.board.vendor: HP dmi.board.version: 46.52 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.26:bd01/12/2018:svnHP:pnHPPavilionLaptop15-cc1xx:pvrType1ProductConfigId:rvnHP:rn83F9:rvr46.52:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cc1xx dmi.product.sku: 2SS26UA#ABA dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20180925-2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1825735/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825741] Re: Multiple instances of global menu entries
Yes it still occurs. I'm currently using Ubuntu 19.04 with Unity desktop. I'll test it with my Neon & Kubuntu install when I get the chance. ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/+attachment/5259076/+files/Flameshot19Apr25-130843.png -- 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/1825741 Title: Multiple instances of global menu entries Status in libreoffice package in Ubuntu: Incomplete Bug description: I see 2 instances of each global menu entries. It's cluttering up my top panel. This also happens in Plasma. Build ID: libreoffice-6.2.2.2-snap1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1825741/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
