[Bug 1593645] Re: manpage does not document "-reduce" parameter
-s (silent) is also undocumented. There's a confusing distinction between it and -q (quiet), where the latter isn't quiet in the usual sense; -s is needed to silence non-error output entirely. There's useless output even when called entirely without options: $ pngcrush CPU time decode 0.00, encode 0.00, other 0.00, total 0.02 sec $ pngcrush -q CPU time decode 0.00, encode 0.00, other 0.00, total 0.02 sec $ pngcrush -s $ This is pngcrush 1.8.13-0.1 on focal. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593645 Title: manpage does not document "-reduce" parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pngcrush/+bug/1593645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798973] Re: Crashes with "double free" or "invalid chunk size" with some mp4 files
Seems to be fixed in VLC 3.0.9.2-1 (Ubuntu 20.04); at least I haven't been able to reproduce it anymore. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798973 Title: Crashes with "double free" or "invalid chunk size" with some mp4 files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1798973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1894968] Re: vlc assert failure: double free or corruption (!prev) when taking screenshot the second time on same time position
Same "double free or corruption (!prev)" reproducible here too (VLC 3.0.9.2-1, Ubuntu 20.04), even more easily: the position doesn't matter, and the first attempt to screenshot is already enough to trigger the issue. I came across this when trying to screenshot a Superman cartoon I downloaded from Internet Archive [1]. * [1] https://archive.org/download/dom-6746superman- episode7-theundergroundworld512kb/dom-6746superman- episode7-theundergroundworld512kb.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1894968 Title: vlc assert failure: double free or corruption (!prev) when taking screenshot the second time on same time position To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1894968/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940417]
I tested 95.0a1 (Nightly), and opening the hamburger menu (using the steps I outlined above) works now. Closing it is still partly broken though, as clicking on the menu button doesn't close the menu; I think that is [bug 1694514](https://bugzilla.mozilla.org/show_bug.cgi?id=1694514). For a workaround, clicking outside the menu (and the menu button) does close the menu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940417 Title: On Wayland toolbar menus are sometimes invisible/flickering To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1940417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940417]
Also, I tested the 94.0a1 nightly now, and the issue is still present. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940417 Title: On Wayland toolbar menus are sometimes invisible/flickering To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1940417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940417]
I ran mozregression like this (twice, to be sure): MOZ_ENABLE_WAYLAND=1 mozregression --profile /home/jani/.mozilla/firefox/fyaus28k.LP1940417 --bad 91 --good 89 --profile-persistence clone-first Here's the result (it was the same for both bisects): 5:25.73 INFO: No more integration revisions, bisection finished. 5:25.73 INFO: Last good revision: 9f0fbb1431721c9eae68a3c94ae49a4d33fdb1f8 5:25.73 INFO: First bad revision: 7b82d177a6b979036f180329be6b029d690d9e0c 5:25.73 INFO: Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9f0fbb1431721c9eae68a3c94ae49a4d33fdb1f8=7b82d177a6b979036f180329be6b029d690d9e0c According to [that log](https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=9f0fbb1431721c9eae68a3c94ae49a4d33fdb1f8=7b82d177a6b979036f180329be6b029d690d9e0c), this [changeset](https://hg.mozilla.org/integration/autoland/rev/7b82d177a6b979036f180329be6b029d690d9e0c) was introduced to address [#1661516](https://bugzilla.mozilla.org/show_bug.cgi?id=1661516). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940417 Title: On Wayland toolbar menus are sometimes invisible/flickering To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1940417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1940417]
I can't speak for Jeroen, but I played around with the upstream builds (both 92 and 91) and my faulty profile a bit and managed to isolate the trigger combination for this: `MOZ_ENABLE_WAYLAND=1` and setting `layout.css.devPixelsPerPx` to my preferred value of `1.2`; either resetting `layout.css.devPixelsPerPx` to its default (`-1.0`), or running Firefox without `MOZ_ENABLE_WAYLAND=1` will make the toolbar items work again. [Here's the graphics portion of my `about:support`](https://pastebin.mozilla.org/OdgM9Oox). **So my steps to reproduce this are:** 1. start Firefox with `MOZ_ENABLE_WAYLAND=1` 2. set `layout.css.devPixelsPerPx` to `1.2` 3. click on the hamburger menu button **What I expect to happen:** For the hamburger menu content to show. **What happens instead:** The hamburger menu content flickers or doesn't show at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940417 Title: On Wayland toolbar menus are sometimes invisible/flickering To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1940417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
There's no gnome-shell-extension-dashtodock package for focal [1], but I did try with Dash to Dock from extensions.gnome.org, and could not reproduce the issue with it. I tried with the default settings, as well as after recreating the look & feel of Ubuntu Dock as much as possible. Dash to Dock has customizable action for the scroll (to either switch workspaces or windows, or to do nothing), and all of those also worked just as expected. I also noticed that using the two finger scroll function of the touchpad on my laptop does *not* trigger this (whereas using the mouse on it does). * [1] https://packages.ubuntu.com/search?keywords=gnome-shell-extension-dashtodock -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
Do you want another log for that? Because (as I already mentioned above), this also reproduces when using a newly-created user, so that means no unsupported extensions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
** Attachment added: "prevboot.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5502426/+files/prevboot.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
I can reproduce the crash at will with the steps I listed above, so I don't have to wait for it to happen. It also doesn't forcibly log me out, so I can enter those commands by just having a terminal window present when I trigger the issue. But I logged out here (after triggering) anyway since you instructed me to log in, in case it matters. Also, there's lots of noise in these from Boinc, thanks to #1876313. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5502425/+files/journal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
1. There's nothing in /var/crash 2. There are no reports on the page for this computer. 3. Done, still nothing in /var/crash. I don't know if this means it's not a true crash, although visually all the indications are there. I also verified that this reproduces when using a newly-created user (with the only change from defaults for it being switching to Wayland), and also on another computer (also running 20.04). I am limited to using the one mouse that I have, so that all testing so far has been with the same mouse. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930304] Re: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
** Attachment added: "syslog Stack trace" https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+attachment/5501476/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1930304] [NEW] Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze
Public bug reported: # Steps to reproduce 0. have a mouse with horizontal scrolling functionality (mine is a Microsoft Comfort Mouse 4500 with a tilting action for horizontal scroll) 1. move mouse pointer over the dock 2. use the mouse scroller to scroll horizontally # What I expect to happen Nothing # What happens Mouse pointer and everything on screen freezes. After a few seconds it unfreezes, but all the icons from the dock are missing. I have to log out and back in to restore the dock. # Other info Slightly similar to LP #1875106, but I'm not using imwheel. I am using Wayland. Syslog seems to always point to this one function: "The offending callback was get_preferred_height(), a vfunc". I'll attach the relevant part from one crash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:35:37 2021 InstallationDate: Installed on 2020-11-30 (182 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084 ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Description changed: # Steps to reproduce 0. have a mouse with horizontal scrolling functionality (mine is a Microsoft Comfort Mouse 4500 with a tilting action for horizontal scroll) 1. move mouse pointer over the dock 2. use the mouse scroller to scroll horizontally # What I expect to happen Nothing # What happens Mouse pointer and everything on screen freezes. After a few seconds it unfreezes, but all the icons from the dock are missing. I have to log out and back in to restore the dock. # Other info - Slightly similar to #1875106, but I'm not using imwheel. + Slightly similar to LP #1875106, but I'm not using imwheel. I am using Wayland. Syslog seems to always point to this one function: "The offending callback was get_preferred_height(), a vfunc". I'll attach the relevant part from one crash. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell-extension-ubuntu-dock 68ubuntu1~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-53.60~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-53-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon May 31 20:35:37 2021 InstallationDate: Installed on 2020-11-30 (182 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) PackageArchitecture: all SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1930304 Title: Horizontal scroll over dock causes it to crash and disappear, and a temporary GUI freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1930304/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874808]
### Steps to reproduce 1. Open about:config 2. Search for autoplay in the settings 3. Set `media.autoplay.default` to `1` ("Block Audio", which is the default) 4. Set `media.autoplay.blocking_policy` to `2` 5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033 6. Try to unmute the video (either by clicking Twitch player's speaker control button, or by dragging the accompanying volume slider) ### What I expect to happen For the audio to be unmuted. ### What happens instead The audio remains muted, and the volume control/indicator remains in the muted position. --- I'm unmotivated to report this to Twitch, as I'm unsure about the precise meaning of `media.autoplay.blocking_policy`, and I currently don't use the non-working value for it myself. Feel free to downprioritize this as you see fit, unless the original reporter is still affected. Here's [my downstream report over at Launchpad](https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1874808) though, just for reference. (I'll update it too.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874808 Title: Twitch video can not be unmuted when media.autoplay.blocking_policy=2, media.autoplay.default=1 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1874808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874808]
Hi Alex! It does not appear to have been fully fixed by Firefox 88 for me at least, although the conditions have changed slightly, and the remaining broken behavior is now slightly different too. First, to update my note above: `media.autoplay.enabled.user-gestures- needed` has been superseded by `media.autoplay.blocking_policy`, and setting the latter to `2` is now required to trigger the issue (as it manifests presently); with the setting at either `0` or `1` I haven't been able to reproduce any variation of the issue. Now, the video doesn't get paused anymore, but the unmuting also does not work: clicking the muted indicator just always resets it back to muted, instead of actually unmuting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874808 Title: Twitch video can not be unmuted when media.autoplay.blocking_policy=2, media.autoplay.default=1 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1874808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874808] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1874808/+attachment/5493044/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874808 Title: Twitch video can not be unmuted when media.autoplay.blocking_policy=2, media.autoplay.default=1 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1874808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874808] HookError_source_firefox.txt
apport information ** Attachment added: "HookError_source_firefox.txt" https://bugs.launchpad.net/bugs/1874808/+attachment/5493042/+files/HookError_source_firefox.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874808 Title: Twitch video can not be unmuted when media.autoplay.blocking_policy=2, media.autoplay.default=1 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1874808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874808] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1874808/+attachment/5493045/+files/ProcEnviron.txt ** Attachment removed: "HookError_source_firefox.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1874808/+attachment/5493042/+files/HookError_source_firefox.txt ** Description changed: With `media.autoplay.blocking_policy` set to 2 and `media.autoplay.default` set to 1 (block audio, which is the default), a Twitch video can not be unmuted. == Steps to reproduce == 1. Open about:config 2. Search for autoplay in the settings 3. Set media.autoplay.default to 1 ("Block Audio", which is the default) 4. Set media.autoplay.blocking_policy to 2 5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033 6. Try to unmute the video (either by clicking Twitch player's speaker control button, or by dragging the accompanying volume slider) == What I expect to happen == For the audio to be unmuted. == What happens instead == The audio remains muted, and the volume control/indicator remains in the muted position. + + == Other info == + This is present in Firefox 88. I tried to update the versions info below using apport-collect, but it failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BuildID: 20200403170909 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 16:33:46 2020 InstallationDate: Installed on 2016-10-13 (1289 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BuildID: 20210415204500 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-11-30 (148 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: firefox 88.0+build2-0ubuntu0.20.04.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Tags: focal wayland-session Uname: Linux 5.8.0-50-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare ssh sudo vboxusers _MarkForUpload: True modified.conffile..etc.default.apport: [modified] mtime.conffile..etc.default.apport: 2020-11-30T20:24:48.587084 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874808 Title: Twitch video can not be unmuted when media.autoplay.blocking_policy=2, media.autoplay.default=1 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1874808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874808] Re: Unmuting Twitch video pauses playback, when media.autoplay.enabled.user-gestures-needed=false, media.autoplay.default=1
apport information ** Description changed: - With `media.autoplay.enabled.user-gestures-needed` set to false and - `media.autoplay.default` set to 1 (block audio), which is the default - (and other autoplay-related settings in their defaults as well), a - Twitch video can only be either paused or playing muted; unmuting the - video pauses it and vice versa. + With `media.autoplay.blocking_policy` set to 2 and + `media.autoplay.default` set to 1 (block audio, which is the default), a + Twitch video can not be unmuted. == Steps to reproduce == + 1. Open about:config 2. Search for autoplay in the settings - 3. Set media.autoplay.enabled.user-gestures-needed to false - 4. Set media.autoplay.default to 1 + 3. Set media.autoplay.default to 1 ("Block Audio", which is the default) + 4. Set media.autoplay.blocking_policy to 2 5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033 - 6. Try to unmute the video - - == What happens == - The video is unmuted, but also paused + 6. Try to unmute the video (either by clicking Twitch player's speaker control button, or by dragging the accompanying volume slider) == What I expect to happen == - For the video to continue playing, unmuted + For the audio to be unmuted. + + == What happens instead == + The audio remains muted, and the volume control/indicator remains in the muted position. + ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BuildID: 20200403170909 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 16:33:46 2020 InstallationDate: Installed on 2016-10-13 (1289 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fi_FI.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fi_FI.UTF-8 + SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - Unmuting Twitch video pauses playback, when media.autoplay.enabled.user-gestures-needed=false, media.autoplay.default=1 + Twitch video can not be unmuted when media.autoplay.blocking_policy=2, media.autoplay.default=1 ** Tags added: apport-collected ** Description changed: With `media.autoplay.blocking_policy` set to 2 and `media.autoplay.default` set to 1 (block audio, which is the default), a Twitch video can not be unmuted. == Steps to reproduce == 1. Open about:config 2. Search for autoplay in the settings 3. Set media.autoplay.default to 1 ("Block Audio", which is the default) 4. Set media.autoplay.blocking_policy to 2 5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033 6. Try to unmute the video (either by clicking Twitch player's speaker control button, or by dragging the accompanying volume slider) == What I expect to happen == For the audio to be unmuted. == What happens instead == The audio remains muted, and the volume control/indicator remains in the muted position. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BuildID: 20200403170909 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 16:33:46 2020 InstallationDate: Installed on 2016-10-13 (1289 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.16 + Architecture: amd64 + BuildID: 20210415204500 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-11-30 (148 days ago) + InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) + NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair + Package: firefox 88.0+build2-0ubuntu0.20.04.1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 + Tags: focal wayland-session + Uname: Linux 5.8.0-50-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare ssh sudo vboxusers + _MarkForUpload: True + modified.conffile..etc.default.apport: [modified]
[Bug 1092099] Re: inconsistent behavior for linked target directory
No, I haven't (and wouldn't know how). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092099 Title: inconsistent behavior for linked target directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pdf/+bug/1092099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092099] Re: inconsistent behavior for linked target directory
Yes, this is still present in 20.04 with printer-driver-cups-pdf 3.0.1-6, limited to original reporter's case of having the symlink point to another filesystem; if I point ~/PDF to, say ~/tmp/PDF (without crossing filesystem borders), the PDF is created without issue, whereas having ~/PDF linked to /media/$USER/$USB_THUMBDRIVE/PDF/ does still cause it to fail: [...] Sat Dec 26 16:48:07 2020 [DEBUG] output filename created: /home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for...ry_342_200_-job_8.pdf Sat Dec 26 16:48:07 2020 [DEBUG] ghostscript commandline built: /usr/bin/gs -q -dCompatibilityLevel=1.2 -dNOPAUSE -dBATCH -dSAFER -sDEVICE=pdfwrite -sOutputFile="/home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for...ry_342_200_-job_8.pdf" -dAutoRotatePages=/PageByPage -dAutoFilterColorImages=false -dColorImageFilter=/FlateEncode -dPDFSETTINGS=/prepress -c .setpdfwrite -f /var/spool/cups-pdf/SPOOL/cups2pdf-233705 Sat Dec 26 16:48:07 2020 [DEBUG] output file unlinked: /home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for...ry_342_200_-job_8.pdf Sat Dec 26 16:48:07 2020 [DEBUG] TMPDIR set for GhostScript: /var/tmp Sat Dec 26 16:48:07 2020 [DEBUG] waiting for child to exit Sat Dec 26 16:48:07 2020 [DEBUG] entering child process Sat Dec 26 16:48:07 2020 [DEBUG] GID set for current user Sat Dec 26 16:48:07 2020 [DEBUG] supplementary groups set for current user Sat Dec 26 16:48:07 2020 [DEBUG] UID set for current user: jani Sat Dec 26 16:48:07 2020 [DEBUG] ghostscript has finished: 256 Sat Dec 26 16:48:07 2020 [ERROR] failed to set file mode for PDF file: /home/jani/PDF/Bug__1092099__342_200_234inconsistent_behavior_for...ry_342_200_-job_8.pdf (non fatal) Sat Dec 26 16:48:07 2020 [DEBUG] ERRNO: 2 (No such file or directory) Sat Dec 26 16:48:07 2020 [DEBUG] no postprocessing Sat Dec 26 16:48:07 2020 [DEBUG] spoolfile unlinked: /var/spool/cups-pdf/SPOOL/cups2pdf-233705 Sat Dec 26 16:48:07 2020 [DEBUG] all memory has been freed Sat Dec 26 16:48:07 2020 [STATUS] PDF creation successfully finished for jani jani@latimeria:~$ ls -l PDF lrwxrwxrwx 1 jani jani 27 joulu 26 16:47 PDF -> /media/jani/KINGSTON_1G/PDF jani@latimeria:~$ ls PDF/ jani@latimeria:~$ ls /media/jani/KINGSTON_1G/PDF/ jani@latimeria:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092099 Title: inconsistent behavior for linked target directory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-pdf/+bug/1092099/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860769] Re: should record changes after snap transactions
Sorry, tried to link this with LP #1723881 but failed, because LP #1334 ** Also affects: snappy (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860769 Title: should record changes after snap transactions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/etckeeper/+bug/1860769/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889784] Re: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland)
** Changed in: firefox (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874272] Re: Stage "searching for obsolete software" takes a very long time (30 minutes)
Currently experiencing this. `lsof /var/lib/dpkg/lock` shows only "focal" as holding the lock. The same "focal" process is also eating up all of the CPU. No dpkg or apt processes are listed by `ps` either. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874272 Title: Stage "searching for obsolete software" takes a very long time (30 minutes) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1874272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1889784] [NEW] Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland)
Public bug reported: After updating Firefox from 78 to 79, hardware-accelerated video decoding no longer works properly in Wayland: streaming video gets cut off with an error message from the service. == Steps to reproduce == 1. Follow the steps in [1] to enable VA-API. 2. Open a Youtube/Twitch video (for instance https://www.twitch.tv/rifftrax), press play == What I expect to happen == For the video be played without issues (as it did with Firefox 78). == What happens == After playing for a while (anything from just a few seconds to a couple of minutes), the video stops and is replaced by a service-specific error message, such as error #3000 (in case of Twitch). Even when playing, the video also flickers green. After reloading the tab, the video again plays for a few seconds before the error message reappears. == Other info == A fix is apparently already in the works upstream [2]. * [1] https://mastransky.wordpress.com/2020/06/03/firefox-on-fedora-finally-gets-va-api-on-wayland/ * [2] https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 79.0+build1-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BuildID: 20200720193547 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 17:07:50 2020 InstallationDate: Installed on 2016-10-13 (1387 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-11T14:52:22.308877 ** Affects: firefox Importance: Unknown Status: Unknown ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Bug watch added: Mozilla Bugzilla #1645671 https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1645671 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1889784 Title: Hardware-accelerated video decoding (VA-API) broken in Firefox 79 (Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1889784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871868] Re: Shell dialog text is truncated and ellipsized
I can confirm that 3.36.4-1ubuntu1~20.04.1 from -proposed fixed the issue (in Boxes) for me, i.e. the dialog text is now wrapped and hence entirely legible. ** Attachment added: "Fully visible text after installing package from -proposed" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871868/+attachment/5396556/+files/20200728_163529.jpg ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871868 Title: Shell dialog text is truncated and ellipsized To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1871868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1704159] Re: a bug in dhcp exit hook script of ddclient
A fix has recently been committed upstream: https://salsa.debian.org/debian/ddclient/-/commit/82d99d1dfb0fb002a15e081fdc7ccf8f96215dc6 ** Bug watch added: Debian Bug tracker #729960 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729960 ** Also affects: ddclient (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=729960 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1704159 Title: a bug in dhcp exit hook script of ddclient To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddclient/+bug/1704159/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1883980] Re: Upgrade corrupted due to "sh: 1: pager: not found"
*** This bug is a duplicate of bug 1874953 *** https://bugs.launchpad.net/bugs/1874953 ** This bug has been marked a duplicate of bug 1874953 dpkg: conffile difference visualizer subprocess returned error exit status 127 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1883980 Title: Upgrade corrupted due to "sh: 1: pager: not found" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1883980/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
After doing manual dconf cleanup, I've been unable to reproduce the issue. That's since posting the previous comment, so a few days now. So I think I'll hold off on reporting this upstream for the time being, but I'll go ahead and do that if the problem still manifests itself. Thanks again, Daniel. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1877568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
I removed all but Desktop Icons, Ubuntu AppIndicators and Ubuntu Dock, rebooted and then reproduced the issue. Luckily I've found one way to reproduce this, albeit somewhat convoluted and still a bit unreliable, involving Synaptic and window tiling. And as it doesn't seem to trigger the issue when using another account, I'm now working through settings differences between the two in hopes of finding something crucial. While doing so, I did discover that dconf-editor is similarly affected: touko 12 16:09:32 saegusa gnome-shell[8208]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client. touko 12 16:09:32 saegusa gnome-shell[8208]: WL: error in client communication (pid 12364) touko 12 16:09:32 saegusa dconf-editor[12364]: Error reading events from display: Katkennut putki touko 12 16:09:32 saegusa boinc[2098]: No protocol specified touko 12 16:09:32 saegusa boinc[2098]: No protocol specified touko 12 16:09:33 saegusa boinc[2098]: No protocol specified touko 12 16:09:33 saegusa boinc[2098]: No protocol specified touko 12 16:09:34 saegusa gnome-shell[8208]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client. touko 12 16:09:34 saegusa boinc[2098]: No protocol specified touko 12 16:09:34 saegusa boinc[2098]: No protocol specified touko 12 16:09:34 saegusa gnome-shell[8208]: WL: error in client communication (pid 12796) touko 12 16:09:34 saegusa gnome-terminal-[12796]: Error reading events from display: Katkennut putki touko 12 16:09:34 saegusa systemd[3569]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE touko 12 16:09:34 saegusa systemd[3569]: gnome-terminal-server.service: Failed with result 'exit-code'. touko 12 16:09:34 saegusa systemd[3569]: vte-spawn-da1941e8-60e5-48e5-868b-7348dd1158c7.scope: Succeeded. touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null touko 12 16:09:34 saegusa gnome-shell[8208]: Error adding children to desktop: this.layout.get_child_at(...) is null Looks like dconf-editor did not exit with FAILURE, but the dconf-editor window did disappear just as Gnome terminal's did. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1877568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
Happened again: May 11 17:05:50 saegusa gnome-shell[3619]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client. May 11 17:05:50 saegusa gnome-shell[3619]: WL: error in client communication (pid 5170) May 11 17:05:50 saegusa gnome-terminal-[5170]: Error reading events from display: Katkennut putki May 11 17:05:50 saegusa systemd[3544]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE May 11 17:05:50 saegusa systemd[3544]: gnome-terminal-server.service: Failed with result 'exit-code'. May 11 17:05:50 saegusa systemd[3544]: vte-spawn-b269c64d-5376-49ec-83fc-9f4806ac4b30.scope: Succeeded. May 11 17:05:50 saegusa systemd[3544]: vte-spawn-3294a176-7b32-4995-a11b-fe0fea8b07bc.scope: Succeeded. May 11 17:05:50 saegusa systemd[3544]: vte-spawn-0b59afd0-1aed-4081-a7d1-801e7c405399.scope: Succeeded. May 11 17:05:51 saegusa systemd[3544]: Started Application launched by gnome-shell. But there's still nothing in /var/crash, nor on the Error Tracker (aside from the aforementioned, unrelated crash from last week). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1877568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
** Attachment added: "syslog.5-excerpt.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877568/+attachment/5369829/+files/syslog.5-excerpt.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1877568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
Turns out the online service was just a little slow to update, and there are in fact reports sent. But the only one post-20.04-upgrade is [1] from last week, which is a gnome-shell crash and IIRC, unrelated to the terminal issue here. It seemed to be triggered by something related to media files and Nautilus, and the logs from the time are different; I'm attaching them here. (I had separated gnome-shell logs out from the main syslog, but I've since reverted back to having everything in syslog.) * [1] https://errors.ubuntu.com/oops/26828e26-8fc9-11ea- acd0-fa163e983629 ** Attachment added: "gnome-shell.log" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1877568/+attachment/5369828/+files/gnome-shell.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1877568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877568] Re: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
Thanks for the instructions, Daniel! I found no crash files either locally or online, so I've implemented the workaround now, and will try to trigger the crash again. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877568 Title: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1877568/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877568] [NEW] WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client (resulting in Gnome terminal crashing)
Public bug reported: Since upgrading to 20.04 and switching to Wayland, Gnome terminal occasionally crashes. I interpret the corresponding logs to mean that it's actually Wayland that fails to do something in the background, which then takes down Gnome terminal: touko 08 11:35:16 saegusa gnome-shell[4227]: WL: compositor bug: The compositor tried to use an object from one client in a 'wl_pointer.enter' for a different client. touko 08 11:35:16 saegusa gnome-shell[4227]: WL: error in client communication (pid 11639) touko 08 11:35:16 saegusa gnome-terminal-[11639]: Error reading events from display: Katkennut putki touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-bbca1723-5987-4ccf-98cb-3389ad05641e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: vte-spawn-fbe02208-95df-4cf4-bfbe-fffc71d6bc7e.scope: Succeeded. touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FAILURE touko 08 11:35:16 saegusa systemd[4153]: gnome-terminal-server.service: Failed with result 'exit-code'. I have yet to nail down the precise circumstances, as this has (so far) been somewhat rare, having occurred perhaps once or twice a week. Since the log mentions pointer, I should perhaps mention that I've set `org.gnome.desktop.wm.preferences` > `focus-mode` to `mouse`. Gnome terminal also exhibits other misbehaviour wrt. to this, occasionally refusing to get focus, or alternatively losing the focus, despite mouse cursor being over the terminal window. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xwayland 2:1.20.8-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,gnomecompat,snap,imgpng,unitymtgrabhandles,move,place,grid,resize,mousepoll,vpswitch,regex,winrules,wall,session,animation,workarounds,expo,ezoom,fade,scale,unityshell] CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 8 15:22:28 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: fwts-efi-runtime-dkms, 20.03.00, 5.4.0-29-generic, x86_64: installed (WARNING! Diff between built and installed module!) fwts-efi-runtime-dkms, 20.03.00, 5.4.0-30-generic, x86_64: installed (WARNING! Diff between built and installed module!) xtables-addons, 3.8, 5.4.0-29-generic, x86_64: installed xtables-addons, 3.8, 5.4.0-30-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0162] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:84ca] InstallationDate: Installed on 2016-10-13 (1302 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: System manufacturer System Product Name ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7 SourcePackage: xorg-server UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1505 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8H77-M PRO 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.:bvr1505:bd10/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8H77-MPRO:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Tue Mar 20 15:09:56 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Tags:
[Bug 1876313] [NEW] Constantly logging "No protocol specified"
Public bug reported: Boinc-client logs "No protocol specified" incessantly, twice every second on my setup. -- Logs begin at Wed 2020-03-25 14:45:19 EET, end at Fri 2020-05-01 17:14:34 EEST. -- touko 01 00:00:00 saegusa boinc[2083]: No protocol specified touko 01 00:00:00 saegusa boinc[2083]: No protocol specified touko 01 00:00:01 saegusa boinc[2083]: No protocol specified touko 01 00:00:01 saegusa boinc[2083]: No protocol specified touko 01 00:00:02 saegusa boinc[2083]: No protocol specified touko 01 00:00:02 saegusa boinc[2083]: No protocol specified touko 01 00:00:03 saegusa boinc[2083]: No protocol specified touko 01 00:00:03 saegusa boinc[2083]: No protocol specified touko 01 00:00:04 saegusa boinc[2083]: No protocol specified touko 01 00:00:04 saegusa boinc[2083]: No protocol specified touko 01 00:00:05 saegusa boinc[2083]: No protocol specified touko 01 00:00:05 saegusa boinc[2083]: No protocol specified touko 01 00:00:06 saegusa boinc[2083]: No protocol specified ...and on and on... touko 01 17:14:54 saegusa boinc[2083]: No protocol specified touko 01 17:14:55 saegusa boinc[2083]: No protocol specified touko 01 17:14:55 saegusa boinc[2083]: No protocol specified touko 01 17:14:56 saegusa boinc[2083]: No protocol specified touko 01 17:14:56 saegusa boinc[2083]: No protocol specified touko 01 17:14:57 saegusa boinc[2083]: No protocol specified touko 01 17:14:57 saegusa boinc[2083]: No protocol specified touko 01 17:14:58 saegusa boinc[2083]: No protocol specified touko 01 17:14:58 saegusa boinc[2083]: No protocol specified touko 01 17:14:59 saegusa boinc[2083]: No protocol specified touko 01 17:14:59 saegusa boinc[2083]: No protocol specified touko 01 17:15:00 saegusa boinc[2083]: No protocol specified touko 01 17:15:00 saegusa boinc[2083]: No protocol specified touko 01 17:15:01 saegusa boinc[2083]: No protocol specified touko 01 17:15:01 saegusa boinc[2083]: No protocol specified touko 01 17:15:02 saegusa boinc[2083]: No protocol specified touko 01 17:15:02 saegusa boinc[2083]: No protocol specified ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: boinc-client 7.16.6+dfsg-1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri May 1 17:16:46 2020 InstallationDate: Installed on 2016-10-13 (1296 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: boinc UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.boinc-client.gui_rpc_auth.cfg: [inaccessible: [Errno 13] Lupa evätty: '/etc/boinc-client/gui_rpc_auth.cfg'] mtime.conffile..etc.boinc-client.cc_config.xml: 2020-04-03T18:39:31.411167 mtime.conffile..etc.boinc-client.global_prefs_override.xml: 2020-04-03T15:47:12.178284 ** Affects: boinc Importance: Unknown Status: Unknown ** Affects: boinc (Ubuntu) Importance: Undecided Status: New ** Affects: boinc (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug focal wayland-session ** Bug watch added: Debian Bug tracker #813728 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813728 ** Also affects: boinc (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813728 Importance: Unknown Status: Unknown ** Bug watch added: github.com/BOINC/boinc/issues #2256 https://github.com/BOINC/boinc/issues/2256 ** Also affects: boinc via https://github.com/BOINC/boinc/issues/2256 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1876313 Title: Constantly logging "No protocol specified" To manage notifications about this bug go to: https://bugs.launchpad.net/boinc/+bug/1876313/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1874808] [NEW] Unmuting Twitch video pauses playback, when media.autoplay.enabled.user-gestures-needed=false, media.autoplay.default=1
Public bug reported: With `media.autoplay.enabled.user-gestures-needed` set to false and `media.autoplay.default` set to 1 (block audio), which is the default (and other autoplay-related settings in their defaults as well), a Twitch video can only be either paused or playing muted; unmuting the video pauses it and vice versa. == Steps to reproduce == 1. Open about:config 2. Search for autoplay in the settings 3. Set media.autoplay.enabled.user-gestures-needed to false 4. Set media.autoplay.default to 1 5. Open a Twitch VOD, for instance https://www.twitch.tv/videos/280106033 6. Try to unmute the video == What happens == The video is unmuted, but also paused == What I expect to happen == For the video to continue playing, unmuted ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: firefox 75.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BuildID: 20200403170909 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 16:33:46 2020 InstallationDate: Installed on 2016-10-13 (1289 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox Importance: Unknown Status: Unknown ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session ** Bug watch added: Mozilla Bugzilla #1631642 https://bugzilla.mozilla.org/show_bug.cgi?id=1631642 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1631642 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1874808 Title: Unmuting Twitch video pauses playback, when media.autoplay.enabled .user-gestures-needed=false, media.autoplay.default=1 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1874808/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819543] Re: Does not exit correctly, have to "kill -9
Still present in 20.04 (Focal) with vlc 3.0.9.2-1, though here at least it seems to only affect some URLs, not all. When I view a stream from my local webcam, vlc -vvv in the terminal shows main playlist debug: incoming request - stopping current input as the final message, and does not exit (after closing the window; Ctrl-Q still works). But when streaming from Wowza's RTSP test stream [1], vlc exits just fine after closing the window. Debian bug 916595 [2] and related VLC ticket [3] mention disabling hardware acceleration as a workaround, but even so I was unable to make it work (i.e. exit properly). Possibly related: Ubuntu bug #1847162. There's also been discussion about the issue over on Manjaro forums [4]. * [1] rtsp://wowzaec2demo.streamlock.net/vod/mp4:BigBuckBunny_115k.mov * [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916595 * [3] https://trac.videolan.org/vlc/ticket/20627 * [4] https://forum.manjaro.org/t/vlc-not-closing/69965/2 ** Bug watch added: VLC Trac #20627 http://trac.videolan.org/vlc/ticket/20627 ** Also affects: vlc via http://trac.videolan.org/vlc/ticket/20627 Importance: Unknown Status: Unknown ** Bug watch added: Debian Bug tracker #916595 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916595 ** Also affects: vlc (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916595 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819543 Title: Does not exit correctly, have to "kill -9 To manage notifications about this bug go to: https://bugs.launchpad.net/vlc/+bug/1819543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871868] Re: Keyboard shortcut restoring shortcut cut short when localized
Done. Thanks, Sebastien! ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #2616 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2616 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/2616 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871868 Title: Keyboard shortcut restoring shortcut cut short when localized To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1871868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1872056] [NEW] luksFormat without root results in "Not compatible PBKDF options"
Public bug reported: When trying without root: $ dd if=/dev/zero bs=16M count=1 of=test.img 1+0 records in 1+0 records out 16777216 bytes (17 MB, 16 MiB) copied, 0.0326881 s, 513 MB/s $ echo foo | cryptsetup luksFormat test.img - Not compatible PBKDF options. Whereas for root it still works: # dd if=/dev/zero bs=16M count=1 of=test.img Please touch the device. 1+0 records in 1+0 records out 16777216 bytes (17 MB, 16 MiB) copied, 0.0183403 s, 915 MB/s # echo foo | sudo cryptsetup luksFormat test.img - # For a workaround (from upstream report) with non-root, specify --type luks1: $ dd if=/dev/zero bs=16M count=1 of=test.img 1+0 records in 1+0 records out 16777216 bytes (17 MB, 16 MiB) copied, 0.0138972 s, 1.2 GB/s $ echo foo | cryptsetup luksFormat --type luks1 test.img - $ ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cryptsetup 2:2.2.2-3ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 14:02:28 2020 InstallationDate: Installed on 2016-10-13 (1274 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: cryptsetup UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago) cmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-23-generic root=UUID=45ed9550-28e7-4af4-a625-9f31663dce9b ro quiet splash vt.handoff=7 crypttab: # siilo0 /home/jani/.Backup/siilo/luks/siilo0/root/.ssh/id_rsa noauto,luks,nofail,timeout=10s modified.conffile..etc.cryptsetup-initramfs.conf-hook: [modified] mtime.conffile..etc.cryptsetup-initramfs.conf-hook: 2020-04-05T16:38:44.442060 ** Affects: cryptsetup (Ubuntu) Importance: Undecided Status: New ** Affects: cryptsetup (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug focal wayland-session ** Bug watch added: Debian Bug tracker #923513 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923513 ** Also affects: cryptsetup (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923513 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1872056 Title: luksFormat without root results in "Not compatible PBKDF options" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1872056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871868] Re: Keyboard shortcut restoring shortcut cut short when localized
Oh and I'm using Wayland, in case it matters here. Haven't yet tried whether Xorg is similarly affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871868 Title: Keyboard shortcut restoring shortcut cut short when localized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871868] [NEW] Keyboard shortcut restoring shortcut cut short when localized
Public bug reported: When trying to start a virtual machine with Gnome Boxes, I get a prompt about keyboard shortcuts. The prompt text is localized, but translated back to English (I think, based on [1]) it says: Boxes wants to inhibit shortcuts You can restore shortcuts by pressing Super+Escape. In my locale (Finnish), it says Sovellus Boksit haluaa rajoittaa pikanäppäinten toimintaa. Voit palauttaa pikanäppäinten toiminnan painamalla Super... (sic; see attached photo) So the actual key combination is truncated, defeating the point of that part of the text. This isn't a localization error (AFAICT; see [2]). It's caused by the text being forced to fit on a single line of an arbitrarily fixed width, instead of wrapping to span as many lines as needed. (I'm reporting this against gnome-shell as opposed gnome-boxes based on [3]. Feel free to reassign as necessary.) * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874526#28 * [2] https://translations.launchpad.net/ubuntu/focal/+source/gnome-shell/+pots/gnome-shell/fi/+translate?batch=10show=allsearch=pikan%C3%A4pp%C3%A4inten * [3] https://bugzilla.redhat.com/show_bug.cgi?id=1668036 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.0-2ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-23.27-generic 5.4.29 Uname: Linux 5.4.0-23-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 9 18:29:14 2020 DisplayManager: gdm3 InstallationDate: Installed on 2016-10-13 (1274 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.36.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to focal on 2020-04-05 (4 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Attachment added: "Localized prompt about keyboard shortcuts being inhibited" https://bugs.launchpad.net/bugs/1871868/+attachment/5350374/+files/20200409_180221.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871868 Title: Keyboard shortcut restoring shortcut cut short when localized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871868/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754125] Re: Rhythmbox stays running in the background after quit
For some of the depressing history of this, see bug #875002 (which has been incorrectly marked as fixed by someone without a clue) from way back in 2011. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754125 Title: Rhythmbox stays running in the background after quit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1754125/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1871107] [NEW] Popup menu jumps to top left window corner when focus follows mouse (in Wayland)
Public bug reported: I'm using 20.04 and a Wayland session. My preferred focus mode is to have it follow the mouse cursor: $ gsettings get org.gnome.desktop.wm.preferences focus-mode 'mouse' Unfortunately this causes GTK apps' popup (RMB) menu to jump to the app window corner when opened. I'm attaching a screencast, where I demonstrate the bug first, then reset focus-mode to 'click' to demonstrate the bug no longer manifesting. (Please excuse the flashing. It's just a video artefact caused by Gnome's built in screen recorder, which was the only one that at least somewhat worked.) This has been reported upstream, where a fix was recently merged: https://gitlab.gnome.org/GNOME/mutter/issues/1103 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.36.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 16:02:37 2020 InstallationDate: Installed on 2016-10-13 (1270 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: Upgraded to focal on 2020-04-05 (0 days ago) ** Affects: mutter Importance: Unknown Status: Unknown ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal third-party-packages wayland-session ** Attachment added: "testi.webm" https://bugs.launchpad.net/bugs/1871107/+attachment/5347736/+files/testi.webm ** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #1103 https://gitlab.gnome.org/GNOME/mutter/issues/1103 ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/issues/1103 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871107 Title: Popup menu jumps to top left window corner when focus follows mouse (in Wayland) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1871107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798074] Re: LIbreoffice crashes on startup
Happy to report that the proposed packages did fix the issue for me also. Thanks everyone! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798074 Title: LIbreoffice crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798074] Re: LIbreoffice crashes on startup
@Marcus: yup, that seems to be it: jani@saegusa:~$ dpkg -l 'libcpd*' 'cpdb*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Nimi VersioArkkitehtuuri Kuvaus +++--=-=-== ii cpdb-backend-gcp 1.0.0-0ubuntu2amd64 Common Print Dialog Backends - Google Cloud Print Back ii libcpdb-libs-common0:amd 1.1.1-0ubuntu1amd64 Common Print Dialog Backends - Interface Library for B jani@saegusa:~$ SAL_DISABLE_CPD=true libreoffice --norestore func=xmlSecCheckVersionExt:file=xmlsec.c:line=188:obj=unknown:subj=unknown:error=19:invalid version:mode=abi compatible;expected minor version=2;real minor version=2;expected subminor version=25;real subminor version=26 That is, no stack trace nor other apparent problems when starting LO with SAL_DISABLE_CPD=true. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798074 Title: LIbreoffice crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1798074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798074] Re: LIbreoffice crashes on startup
Can't speak for Stuart, but I'm the other one affected, and still so: jani@saegusa:~$ apt-cache policy libreoffice libreoffice: Asennettu: 1:6.0.7-0ubuntu0.18.04.5 Ehdokas: 1:6.0.7-0ubuntu0.18.04.5 Versiotaulukko: *** 1:6.0.7-0ubuntu0.18.04.5 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu bionic-security/universe amd64 Packages 100 /var/lib/dpkg/status 1:6.0.3-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/universe amd64 Packages jani@saegusa:~$ libreoffice --norestore Application Error Fatal exception: Signal 6 Stack: /usr/lib/libreoffice/program/libuno_sal.so.3(+0x13568)[0x7f5cb050b568] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c3a6)[0x7f5cb05343a6] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f5cb0145f20] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7)[0x7f5cb0145e97] /lib/x86_64-linux-gnu/libc.so.6(abort+0x141)[0x7f5cb0147801] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d5c882)[0x7f5cb34ae882] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5AbortERKN3rtl8OUStringE+0xa2)[0x7f5cb343a2b2] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d0d470)[0x7f5cb245f470] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cedc5d)[0x7f5cb343fc5d] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x163b2)[0x7f5cb050e3b2] /usr/lib/libreoffice/program/libuno_sal.so.3(+0x3c26f)[0x7f5cb053426f] /lib/x86_64-linux-gnu/libc.so.6(+0x3ef20)[0x7f5cb0145f20] /lib/x86_64-linux-gnu/libc.so.6(+0xb1646)[0x7f5cb01b8646] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(g_dbus_node_info_new_for_xml+0x124)[0x7f5cae74dce4] /usr/lib/libreoffice/program/libmergedlo.so(+0x2d6aa3b)[0x7f5cb34bca3b] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc92d6)[0x7f5cae7432d6] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc9518)[0x7f5cae743518] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d1a3)[0x7f5cae7071a3] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8dbc6)[0x7f5cae707bc6] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0xc1082)[0x7f5cae73b082] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d1a3)[0x7f5cae7071a3] /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0(+0x8d1d9)[0x7f5cae7071d9] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x155)[0x7f5cae15b285] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x4c650)[0x7f5cae15b650] /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c)[0x7f5cae15b6dc] /usr/lib/libreoffice/program/libvclplug_gtk3lo.so(+0x41444)[0x7f5c9ac63444] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application5YieldEv+0x2e)[0x7f5cb343a9be] /usr/lib/libreoffice/program/libmergedlo.so(_ZN11Application7ExecuteEv+0x45)[0x7f5cb343c165] /usr/lib/libreoffice/program/libmergedlo.so(+0x1d12e93)[0x7f5cb2464e93] /usr/lib/libreoffice/program/libmergedlo.so(+0x2cef846)[0x7f5cb3441846] /usr/lib/libreoffice/program/libmergedlo.so(_Z6SVMainv+0x30)[0x7f5cb3441950] /usr/lib/libreoffice/program/libmergedlo.so(soffice_main+0x115)[0x7f5cb2485fb5] /usr/lib/libreoffice/program/soffice.bin(+0x78b)[0x557ff5eff78b] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7)[0x7f5cb0128b97] /usr/lib/libreoffice/program/soffice.bin(+0x7ca)[0x557ff5eff7ca] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798074 Title: LIbreoffice crashes on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1798074/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739836] Re: dependency failed for pNFS block layout mapping daemon
** Package changed: ubuntu-release-upgrader (Ubuntu) => nfs-utils (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739836 Title: dependency failed for pNFS block layout mapping daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1739836/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1819478] Re: xtables-addons package V 3.0 not compatible to new Maxmind Data format - Update to V 3.3 needed
*** This bug is a duplicate of bug 1810920 *** https://bugs.launchpad.net/bugs/1810920 ** This bug has been marked a duplicate of bug 1810920 GeoLite2-Country-CSV support for Ubuntu 16.04/18.04 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1819478 Title: xtables-addons package V 3.0 not compatible to new Maxmind Data format - Update to V 3.3 needed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1819478/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1811029] Re: Package installation fails when attempting to download GeoIP database files
The Debian BTS has a related report [1] which suggests to me this issue should have been fixed way back in v1.11. But even if installing wasn't broken, with the legacy databases discontinued, it's not much use in the long term. Geoip-database-contrib has already been removed from Debian entirely [2] due to deprecation by upstream, apparently in favor of geoipupdate [3]. (I'm not affiliated with either package and have no solutions; I'm just documenting the connections here.) * [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666063 * [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900400 * [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885441 ** Bug watch added: Debian Bug tracker #666063 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666063 ** Bug watch added: Debian Bug tracker #900400 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900400 ** Bug watch added: Debian Bug tracker #885441 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885441 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1811029 Title: Package installation fails when attempting to download GeoIP database files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoip-database-contrib/+bug/1811029/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820514] Re: Saving a web page from Tom's Hardware forums fails
Yep, retrying does work. I've now reported this to Mozilla and linked to it. Thanks, Olivier! ** Bug watch added: Mozilla Bugzilla #1536530 https://bugzilla.mozilla.org/show_bug.cgi?id=1536530 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1536530 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820514 Title: Saving a web page from Tom's Hardware forums fails To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1820514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820514] Re: Saving a web page from Tom's Hardware forums fails
Tested all combinations of both (Ctrl-s/context menu in safe mode and normal mode), all with the same results. Could this be locale-dependent? The UI is in English in safe mode though, so I'm guessing safe mode should be locale-independent, as I'm on fi_FI.UTF-8 otherwise. And just to clarify: my testing of Bionic was on real hardware as well, and I ran these latest tests on Cosmic on another computer (real hardware). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820514 Title: Saving a web page from Tom's Hardware forums fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820514] [NEW] Saving a web page from Tom's Hardware forums fails
Public bug reported: == Steps to reproduce == 1. Open https://forums.tomshardware.com/threads/what-is-the-actually-difference-between-udimm-and-dimm.1575984/ 2. Right-click and select 'Save page as'. Point the dialog to your directory of choice. == What I expect to happen == For the directory to contain a downloaded copy of the page. == What happens == There's no copy of the page in the target directory. Going to about:downloads reveals that the download has failed, without further details. == Other info == I'm reporting this from up-to-date Disco, albeit with a 4.* kernel (as gdm currently fails to start in my VirtualBox VM with 5.*) but it's equally reproducible in Bionic. Any page under https://forums.tomshardware.com/ seems to trigger this, but I have yet to come across other sites that do. Pages can even be saved from the main Tom's Hardware domain (https://www.tomshardware.com/) without issues. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 66.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8 Uname: Linux 4.19.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jani 1324 F pulseaudio BuildID: 20190315094614 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 15:37:04 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-09-30 (167 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=66.0/20190315094614 (In use) RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) 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 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820514 Title: Saving a web page from Tom's Hardware forums fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1820514/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1593645] Re: manpage does not document "-reduce" parameter
Another option missing from the man page is -ow (for overwriting the input file in-place), available since version 1.7.22. $ pngcrush 2>&1 | grep -- -ow pngcrush -ow [other options] file.png [tempfile.png] -ow (Overwrite) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1593645 Title: manpage does not document "-reduce" parameter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pngcrush/+bug/1593645/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1589717] Re: bc cannot handle "comma" instead of "dot" in floating point operations
** Bug watch added: Debian Bug tracker #696762 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696762 ** Also affects: bc via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696762 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1589717 Title: bc cannot handle "comma" instead of "dot" in floating point operations To manage notifications about this bug go to: https://bugs.launchpad.net/bc/+bug/1589717/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1814403] Re: Latest update causes 30 sec. menu delay timeout
Fixed for me by the latest -proposed package. I'm running Bionic, non- EFI, and was affected by the issue with the earlier package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1814403 Title: Latest update causes 30 sec. menu delay timeout To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1814403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
A new log; still nothing useful from colord AFAICT, despite the --verbose. ** Attachment added: "Unrecoverable failure with gsd-color --verbose" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+attachment/5236695/+files/joured.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
...except that --debug isn't one of gsd-color's recognized parameters, and adding it caused GDM to fail to start. I changed it to --verbose which is available. 10.08 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color --help-all Usage: gsd-color [OPTION?] color Help Options: -h, --help Show help options --help-all Show all help options --help-gtk Show GTK+ Options GTK+ Options --class=CLASSProgram class as used by the window manager --name=NAME Program name as used by the window manager --gdk-debug=FLAGSGDK debugging flags to set --gdk-no-debug=FLAGS GDK debugging flags to unset --gtk-module=MODULES Load additional GTK+ modules --g-fatal-warnings Make all warnings fatal --gtk-debug=FLAGSGTK+ debugging flags to set --gtk-no-debug=FLAGS GTK+ debugging flags to unset Application Options: --exit-time Exit after n seconds time --dummy-name Name when using the dummy daemon -v, --verboseVerbose --display=DISPLAYX display to use There's also --gtk-debug and --gdk-debug, but I could do with a little help for what to select for those, as just giving 'all' seems a little counterproductive (for instance, "touchscreen" and "interactive" don't seem very useful here). 10.03 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color --gtk-debug help Supported debug values: misc plugsocket text tree updates keybindings multihead modules geometry icontheme printing builder size-request no-css-cache baselines pixel-cache no-pixel-cache interactive touchscreen actions resize layout all help 10.04 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color --gdk-debug help Supported debug values: events misc dnd xim nograbs input cursor multihead xinerama draw eventloop frames settings opengl all help Error parsing option --gdk-debug (Looks like --gdk-debug reports an error with 'help', despite having just listed it as one of the options.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Sure, I've now set it up thus and will post the results once I hit this again (it seems pretty unpredictable, so could be anything from days to weeks). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764417] Re: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Here you go. Had this occur twice in a row just now, so my original theory of the second login never failing was false. ** Attachment added: "journalctl from a boot with two dead whales" https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+attachment/5231688/+files/joured.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1808690] Re: Page content slightly transparent, reveals content from another window below
** Attachment added: "Same screenshot with added hints about see-through content" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1808690/+attachment/5222692/+files/spectral-highlights.png ** Description changed: Under some circumstances, content from another Firefox window hidden - behind another leaks onto the top one. Reproducible in both Bionic and - Disco, reporting this from Disco. + behind another leaks onto the top one. Reproducible in both Bionic (with + Intel graphics) and Disco (in a VirtualBox VM), reporting this from + Disco. == Steps to reproduce == 1. Open one Firefox window, drag it to the right side of screen to fill the right half, and navigate to https://www.twitch.tv/rifftrax 2. Open another Firefox window, maximize it on top of the first one, and use this topmost window to open https://www.youtube.com/watch?v=P5dxd-ocaE8 == What happens == White parts of content in Firefox window #1 cast a spectral shadow on the black parts of content in Firefox window #2. It's quite subtle, but luckily can be caught in screenshots: see attachments below. Pausing the Youtube video seems to make the effect to go away (the transparency disappears). == What I'd expect to happen == For the topmost window to be completely opaque, i.e. not to see anything from behind the topmost window. == Other info == Though I don't think this is tied the two sites I've used as an example, they're the first and only ones I've happened to encounter this with. I've yet to find other reports this, apart from one /r/Fedora thread mentioning something similar: https://www.reddit.com/r/Fedora/comments/7m9m4h/youtube_videos_are_transparent_kind_of_in_firefox/ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 64.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8 Uname: Linux 4.19.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: jani 1748 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: jani 1748 F pulseaudio BuildID: 20181207223303 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Dec 16 15:30:58 2018 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 + # 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-30 (76 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930) IpRoute: - default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 - 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 - 169.254.0.0/16 dev enp0s3 scope link metric 1000 + default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 + 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 + 169.254.0.0/16 dev enp0s3 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fi_FI.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fi_FI.UTF-8 + SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=64.0/20181207223303 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) 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 ** Description changed: Under some circumstances, content from another Firefox window hidden behind another leaks onto the top one. Reproducible in both Bionic (with Intel graphics) and Disco (in a VirtualBox VM), reporting this from Disco. == Steps to reproduce == 1. Open one Firefox window, drag it to the right side of screen to fill the right half, and navigate to https://www.twitch.tv/rifftrax - 2. Open another Firefox window, maximize it on top of the first one, and use this topmost window to open https://www.youtube.com/watch?v=P5dxd-ocaE8 + 2. Open another Firefox window, maximize it on top of the first one, and use this topmost window to open
[Bug 1808690] [NEW] Page content slightly transparent, reveals content from another window below
Public bug reported: Under some circumstances, content from one Firefox window hidden behind another leaks onto the top one. Reproducible in both Bionic (with Intel graphics) and Disco (in a VirtualBox VM), reporting this from Disco. == Steps to reproduce == 1. Open one Firefox window, drag it to the right side of screen to fill the right half, and navigate to https://www.twitch.tv/rifftrax 2. Open another Firefox window, maximize it on top of the first one, and use this topmost window to open https://www.youtube.com/watch?v=P5dxd-ocaE8 and expand the Youtube view to 'theatre' mode == What happens == White parts of content in Firefox window #1 cast a spectral shadow on the black parts of content in Firefox window #2. It's quite subtle, but luckily can be caught in screenshots: see attachments below. Pausing the Youtube video seems to make the effect to go away (the transparency disappears). == What I'd expect to happen == For the topmost window to be completely opaque, i.e. not to see anything from behind the topmost window whether the video is playing or not. == Other info == Though I don't think this is tied the two sites I've used as an example, they're the first and only ones I've happened to encounter this with. I've yet to find other reports about this, apart from one /r/Fedora thread mentioning something similar: https://www.reddit.com/r/Fedora/comments/7m9m4h/youtube_videos_are_transparent_kind_of_in_firefox/ ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: firefox 64.0+build3-0ubuntu1 ProcVersionSignature: Ubuntu 4.19.0-9.10-generic 4.19.8 Uname: Linux 4.19.0-9-generic x86_64 AddonCompatCheckDisabled: False ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jani 1748 F pulseaudio BuildID: 20181207223303 Channel: Unavailable CurrentDesktop: ubuntu:GNOME Date: Sun Dec 16 15:30:58 2018 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-30 (76 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930) IpRoute: default via 10.0.2.2 dev enp0s3 proto dhcp metric 100 10.0.2.0/24 dev enp0s3 proto kernel scope link src 10.0.2.15 metric 100 169.254.0.0/16 dev enp0s3 scope link metric 1000 Locales: extensions.sqlite corrupt or missing PrefSources: prefs.js ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash Profiles: Profile0 (Default) - LastVersion=64.0/20181207223303 RunningIncompatibleAddons: False SourcePackage: firefox Themes: extensions.sqlite corrupt or missing UpgradeStatus: No upgrade log present (probably fresh install) 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 ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Untouched screenshot of top window revealing content from another window below" https://bugs.launchpad.net/bugs/1808690/+attachment/5222682/+files/Kuvakaappaus%20-%202018-12-16%2015-05-24.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1808690 Title: Page content slightly transparent, reveals content from another window below To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1808690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803534] Re: Backport uuid based cache file naming scheme
I've hit an issue, which I believe I've now isolated to have come from upgrading fontconfig (and related packages) from 2.12.6-0ubuntu2 to 2.12.6-0ubuntu2.3 from -proposed: if I start Firefox and afterwards start Gparted or Synaptic, Firefox starts eating up all of my CPU. Eventually all letters in the Gparted/Synaptic UI turn into boxes. Syslog typically then says something like below: Dec 4 13:41:50 saegusa synaptic.desktop[30027]: (synaptic:30028): Pango-WARNING **: 13:41:50.995: failed to create cairo scaled font, expect ugly output. the offending font is 'DejaVu Sans 11' Dec 4 13:41:50 saegusa synaptic.desktop[30027]: (synaptic:30028): Pango-WARNING **: 13:41:50.995: font_face status is: out of memory Dec 4 13:41:50 saegusa synaptic.desktop[30027]: (synaptic:30028): Pango-WARNING **: 13:41:50.995: scaled_font status is: out of memory Dec 4 13:41:50 saegusa synaptic.desktop[30027]: (synaptic:30028): Pango-WARNING **: 13:41:50.995: shaping failure, expect ugly output. shape-engine='PangoFcShapeEngine', font='DejaVu Sans 11', text='Päivitä' Dec 4 13:41:51 saegusa synaptic.desktop[30027]: (synaptic:30028): Pango-WARNING **: 13:41:51.007: failed to create cairo scaled font, expect ugly output. the offending font is 'DejaVu Sans 11' Dec 4 13:41:51 saegusa synaptic.desktop[30027]: (synaptic:30028): Pango-WARNING **: 13:41:51.007: font_face status is: out of memory Dec 4 13:41:51 saegusa synaptic.desktop[30027]: (synaptic:30028): Pango-WARNING **: 13:41:51.007: scaled_font status is: out of memory The computer has 32 GB of memory and there's plenty still usable when this occurs, so the OOM seems incorrect to me. To be sure, I rolled back entirely from -proposed (which caused the issue to go away), then re-enabled -proposed and upgraded just fontconfig, and the issue reappeared. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1803534 Title: Backport uuid based cache file naming scheme To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1803534/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798103] Re: Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2
Thanks Olivier, I've now added the link to my upstream report. ** Bug watch added: Mozilla Bugzilla #1508043 https://bugzilla.mozilla.org/show_bug.cgi?id=1508043 ** Also affects: firefox via https://bugzilla.mozilla.org/show_bug.cgi?id=1508043 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798103 Title: Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1798103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1793861] Re: libreoffice crashes when libvclplug_gtk3lo is installed
LO 1:6.0.6-0ubuntu0.18.04.1 in Bionic is likewise affected, and the workaround also works here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1793861 Title: libreoffice crashes when libvclplug_gtk3lo is installed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1793861/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1778422] Re: evince responds to mouse location when it does not have focus. Scrolls wildly up or down.
This happens in 18.04 too. Bug #1650076 does also, and I'm not 100 % sure if these are two different issues or the same. I was able to reproduce #1650076 with the steps listed there, but just before that I had Evince following my scroll wheel despite being unfocussed, and I had not selected anything in the PDF before that (at least not knowingly). I haven't found the steps to reproduce this without the selection though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1778422 Title: evince responds to mouse location when it does not have focus. Scrolls wildly up or down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1778422/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1800330] [NEW] Doesn't know about acpica-tools (acpidump, acpixtract)
Public bug reported: When acpica-tools is not installed, running acpidump or acpixtract produces no suggestions (in either Bionic or Cosmic): $ acpixtract acpixtract: command not found $ apt-cache policy acpitools-ca N: Unable to locate package acpitools-ca $ apt-cache policy acpica-tools acpica-tools: Installed: (none) Candidate: 20180629-1 Version table: 20180629-1 500 500 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages $ sudo apt install acpica-tools [sudo] password for jani: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: linux-headers-4.18.0-8 linux-headers-4.18.0-8-generic linux-image-4.18.0-8-generic linux-modules-4.18.0-8-generic linux-modules-extra-4.18.0-8-generic Use 'sudo apt autoremove' to remove them. The following NEW packages will be installed: acpica-tools 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 851 kB of archives. After this operation, 2782 kB of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu cosmic/universe amd64 acpica-tools amd64 20180629-1 [851 kB] Fetched 851 kB in 1s (1622 kB/s) Selecting previously unselected package acpica-tools. (Reading database ... 207563 files and directories currently installed.) Preparing to unpack .../acpica-tools_20180629-1_amd64.deb ... Unpacking acpica-tools (20180629-1) ... Setting up acpica-tools (20180629-1) ... update-alternatives: using /usr/bin/acpixtract-acpica to provide /usr/bin/acpixtract (acpixtract) in auto mode update-alternatives: warning: skip creation of /usr/share/man/man1/acpixtract.1.gz because associated file /usr/share/man/man1/acpixtract-acpica.1 (of link group acpixtract) doesn't exist update-alternatives: using /usr/bin/acpidump-acpica to provide /usr/bin/acpidump (acpidump) in auto mode update-alternatives: warning: skip creation of /usr/share/man/man1/acpidump.1.gz because associated file /usr/share/man/man1/acpidump-acpica.1 (of link group acpidump) doesn't exist Processing triggers for man-db (2.8.4-2) ... $ acpidump Could not open table file: /sys/firmware/acpi/tables/SSDT Could not get ACPI tables, AE_ACCESS $ acpixtract Intel ACPI Component Architecture ACPI Binary Table Extraction Utility version 20180629 Copyright (c) 2000 - 2018 Intel Corporation Usage: acpixtract [option] Options: -a Extract all tables, not just DSDT/SSDT -f Force extraction, even if there are errors -l List table summaries, do not extract -m Extract multiple DSDT/SSDTs to a single file -s Extract all tables with -v Display version information -vd Display build date and time Extract binary ACPI tables from text acpidump output Default invocation extracts the DSDT and all SSDTs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: command-not-found 18.10.0~pre1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 28 09:31:57 2018 InstallationDate: Installed on 2018-09-30 (27 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180930) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: command-not-found UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: command-not-found (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1800330 Title: Doesn't know about acpica-tools (acpidump, acpixtract) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/command-not-found/+bug/1800330/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798973] Re: Crashes with "double free" or "invalid chunk size" with some mp4 files
** Attachment added: "vlc -vvv output ending in "double free or corruption (fasttop)"" https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1798973/+attachment/5203362/+files/vlc-double-free.log -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798973 Title: Crashes with "double free" or "invalid chunk size" with some mp4 files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1798973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798973] Re: Crashes with "double free" or "invalid chunk size" with some mp4 files
** Attachment added: "vlc -vvv output ending in "malloc_consolidate(): invalid chunk size"" https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1798973/+attachment/5203363/+files/vlc-malloc.log ** Description changed: I'm seeing memory-related crashes when playing videos sliced (with ffmpeg -c copy) from mp4 streams (downloaded with youtube-dl). I'm attaching a sample clip which, granted, is pretty useless for a video, but which produces these crashes with 100% certainty for me; I just edited it down to a reasonable size and non-infringing content. The errors reported just before core is dumped are (mostly) "double free or corruption (fasttop)" or (less often) "malloc_consolidate(): invalid chunk size". - To be clear, my expectation here is not for the problematic clips have - useful content, or even to play back; just that vlc didn't crash. (Totem - for instance does not seem to crash with the same files.) + To be clear, my expectation here is not for the problematic clips to + have useful content, or even to play back; just that vlc didn't crash. + (Totem for instance does not seem to crash with the same files.) I'll attach logs for both the double free and malloc_consolidate cases (which I'm producing by running LC_ALL=C vlc -vvv out.mp4 in a loop). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vlc 3.0.3-1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 18:14:25 2018 InstallationDate: Installed on 2016-10-13 (737 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fi_FI.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fi_FI.UTF-8 + SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798973 Title: Crashes with "double free" or "invalid chunk size" with some mp4 files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1798973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798973] [NEW] Crashes with "double free" or "invalid chunk size" with some mp4 files
Public bug reported: I'm seeing memory-related crashes when playing videos sliced (with ffmpeg -c copy) from mp4 streams (downloaded with youtube-dl). I'm attaching a sample clip which, granted, is pretty useless for a video, but which produces these crashes with 100% certainty for me; I just edited it down to a reasonable size and non-infringing content. The errors reported just before core is dumped are (mostly) "double free or corruption (fasttop)" or (less often) "malloc_consolidate(): invalid chunk size". To be clear, my expectation here is not for the problematic clips to have useful content, or even to play back; just that vlc didn't crash. (Totem for instance does not seem to crash with the same files.) I'll attach logs for both the double free and malloc_consolidate cases (which I'm producing by running LC_ALL=C vlc -vvv out.mp4 in a loop). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: vlc 3.0.3-1-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Oct 20 18:14:25 2018 InstallationDate: Installed on 2016-10-13 (737 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: vlc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: vlc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "short example mp4 file to reproduce the crash" https://bugs.launchpad.net/bugs/1798973/+attachment/5203358/+files/out.mp4 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798973 Title: Crashes with "double free" or "invalid chunk size" with some mp4 files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vlc/+bug/1798973/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798103] Re: Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2
** Attachment added: "pasted text is not even close to what you've selected to copy" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798103/+attachment/5201768/+files/screenshot-2.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798103 Title: Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1798103] [NEW] Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2
Public bug reported: == The issue == Search and text selection highlighting visuals get mismatched with the actual selection in view-source when the value of `layout.css.devPixelsPerPx` is 1.2 or larger. == Steps to reproduce == * Open `about:config`, find `layout.css.devPixelsPerPx` and change the value from default (-1.0) to 1.2. * Open a view-source view with long lines: `view-source:https://www.youtube.com/user/10asti10` * hit Ctrl+f, search for rss * using the LMB, try selecting some text, then copy and paste it somewhere == What happens == Screenshot 1: the highlighted text on the page is not ”rss”. The highlight doesn’t even adhere to letter widths. Screenshot 2: the pasted text is not even close to what you’ve selected to copy. == What I expect to happen == For the search to hightlight an occurence of ”rss”, and for the pasted text to correspond to what I’ve selected from the view-source view. == Other info == * In my testing, a devPixelsPerPx value of 1.1 seems to not trigger this, whereas 1.2 and anything above does. * In addition to 18.04 (whence the attached info is from) I’ve reproduced this in a VM running up-to-date 18.10. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: firefox 62.0.3+build1-0ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BuildID: 20181002130007 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 16 16:59:28 2018 InstallationDate: Installed on 2016-10-13 (733 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: firefox UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "highlighted text on the page is not ”rss”" https://bugs.launchpad.net/bugs/1798103/+attachment/5201764/+files/screenshot-1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1798103 Title: Text highlight mismatch in view-source when layout.css.devPixelsPerPx is >= 1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1798103/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1402183] Re: Unimportant update notifications are sent to root from cron script
Needless verbosity is the problem here, IMO. I'd expect to receive output from the installer only when the download or install fails for some reason, not when it succeeds. (Also, to me the culprit here seems to be flashplugin-installer and not update-notifier, as plenty of other packages also report their installation progress, but only flashplugin's seems to get forwarded to root's mail even when nothing abnormal occurs.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1402183 Title: Unimportant update notifications are sent to root from cron script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1402183/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu
All right. Thanks, Jeremy! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747171 Title: "New Tab" disappeared from the GNOME Terminal menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu
Okay, did it! https://gitlab.gnome.org/GNOME/gnome-terminal/issues/30 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747171 Title: "New Tab" disappeared from the GNOME Terminal menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu
Jeremy: If this is indeed the popular choice then I fully respect that. I just wanted to voice my disgruntlement, since I feel the way this was set by upstream is much simpler. Sorry for being late with it, didn't realize this was getting overridden before the change already came into effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747171 Title: "New Tab" disappeared from the GNOME Terminal menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747171] Re: "New Tab" disappeared from the GNOME Terminal menu
Urgh, I'd argue that changing this back *is* a regression. The merged menu item has been the default since (at least) 16.04, and now the cognitive load of opening a new tab has suddenly increased: instead of "new terminal" I now again have to pick the one I want (which is always tabs for me) from two options each time, instead of just the one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747171 Title: "New Tab" disappeared from the GNOME Terminal menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1747171/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767806] Re: Position of left-tiled windows not restored correctly when another left-tiled window present
Thanks, I've now reported this at: https://gitlab.gnome.org/GNOME/gnome- shell/issues/287 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767806 Title: Position of left-tiled windows not restored correctly when another left-tiled window present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1767806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1747891] Re: gsd-color[1032]: failed to set screen _ICC_PROFILE
** Bug watch added: GNOME Bug Tracker #749338 https://bugzilla.gnome.org/show_bug.cgi?id=749338 ** Also affects: gnome-settings-daemon via https://bugzilla.gnome.org/show_bug.cgi?id=749338 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1747891 Title: gsd-color[1032]: failed to set screen _ICC_PROFILE To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1747891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767806] Re: Position of left-tiled windows not restored correctly when another left-tiled window present
** Attachment added: "Expected: Firefox tiled to the left (when Nautilus floating)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1767806/+attachment/5130159/+files/expected.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767806 Title: Position of left-tiled windows not restored correctly when another left-tiled window present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1767806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767806] [NEW] Position of left-tiled windows not restored correctly when another left-tiled window present
Public bug reported: When another window is maximized or tiled to the left side of the screen, re-opening an application whose window was previously tiled to the left side does not restore that windows' previous position. Instead such windows open at varying distances from the dock, untiled. = Steps to reproduce *expected* behavior (with a newly created user) = 1. open Firefox, drag the window to the left edge of the screen to tile it there (filling up the left half of horizontal screen space) 2. close Firefox 3. open Nautilus, make sure that the window floats (i.e. is unmaximized and not tiled to either side of screen) 4. open Firefox == What happens == As expected, Firefox's window is tiled to the left edge of screen, immediately to the right side of the dock. = Steps to reproduce *unexpected* behavior (with a newly created user) = 1. open Firefox, drag the window to the left edge of the screen to tile it there (filling up the left half of horizontal screen space) 2. close Firefox 3. open Nautilus, *maximize its window* 4. open Firefox == What happens == Firefox's window opens slightly to the right off the right edge of the dock (with a gap between the dock and the window). == What I expect to happen == I expect Firefox's window to be tiled to the left edge of screen, immediately to the right side of the dock, just as it did following the first recipe above. = Further information = Either maximizing or tiling Nautilus' window to the left edge of the screen (at step #3) triggers the issue. Tiling it to the *right* edge of the screen does not. Using Gnome Terminal instead of Nautilus triggers the issue just as well, I suspect any other application will though I've only systematically tested these two so far. >From battling with this in my daily use I also know that the distance of incorrectly restored windows from the dock varies: different applications open at different distances. The precise mechanics of this still elude me, though the distances do appear to be multiples of 25 pixels. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: mutter 3.28.1-1ubuntu1 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 CurrentDesktop: ubuntu:GNOME Date: Sun Apr 29 16:32:37 2018 InstallationDate: Installed on 2016-10-13 (562 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767806 Title: Position of left-tiled windows not restored correctly when another left-tiled window present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1767806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1767806] Re: Position of left-tiled windows not restored correctly when another left-tiled window present
** Attachment added: "Unexpected: Firefox not properly tiled to the left (with Nautilus maximized)" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1767806/+attachment/5130163/+files/unexpected-1.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1767806 Title: Position of left-tiled windows not restored correctly when another left-tiled window present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1767806/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1749728] Re: GDebi doesn't handle Firefox "open with"
** Description changed: - GDebi doesn't handle Firefox "open with" option instead of "save file". - It will open GDebi but when presing to install the pachage it will close. + When launched from Firefox with the "open with" function, GDebi is + unable to complete installing the package. The GDebi window does open, + but after selecting to "install" the package the window closes and the + package is left uninstalled. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdebi 0.9.5.7+nmu2 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: MATE Date: Thu Feb 15 17:08:31 2018 InstallationDate: Installed on 2018-02-15 (0 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180215) PackageArchitecture: all SourcePackage: gdebi UpgradeStatus: No upgrade log present (probably fresh install) ** Summary changed: - GDebi doesn't handle Firefox "open with" + Installing packages fails when launched via Firefox ("open with") -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1749728 Title: Installing packages fails when launched via Firefox ("open with") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1749728/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 135063] Re: wget --quiet --background leaves a wget.log file
** Summary changed: - wget --quite --background leaves a wget.log file + wget --quiet --background leaves a wget.log file ** Description changed: Binary package hint: wget - wget --quite --background leaves a 0 byte wget.log file + wget --quiet --background leaves a 0 byte wget.log file it is no supposed once the quiet parameter is entered. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/135063 Title: wget --quiet --background leaves a wget.log file To manage notifications about this bug go to: https://bugs.launchpad.net/wget/+bug/135063/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765690] [NEW] wget-log file created despite -q when run in background with
Public bug reported: == Steps to reproduce == `wget -q https://www.google.com/ &` == What happens == wget says it's "Redirecting output to 'wget-log'" and creates an empty wget-log file in the current directory. == What I expect to happen == No wget-log file to be created. == Details == Wget has a -b (--background) option, for which the man page says: "If no output file is specified via the -o, output is redirected to wget-log." There's also the -q (--quiet) option, for which the man page says: "Turn off Wget's output." When both are given, wget goes to background, and no wget-log gets created, as expected. When only -b is given, wget goes to background, and creates wget-log, also as expected. When only -q is given, wget runs in the foreground, and no wget-log is created, still as expected. When only -q is given, but & is added to the end of the command line, wget goes to background, but also creates wget-log, which I find unexpected (and inconsistent). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: wget 1.19.4-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 20 14:56:17 2018 InstallationDate: Installed on 2016-10-13 (553 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: wget UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wget (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Bug watch added: Red Hat Bugzilla #1484411 https://bugzilla.redhat.com/show_bug.cgi?id=1484411 ** Bug watch added: Debian Bug tracker #888691 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888691 ** Bug watch added: Debian Bug tracker #874590 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874590 ** Bug watch added: GNU Savannah Bug Tracker #51181 http://savannah.gnu.org/bugs/?51181 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765690 Title: wget-log file created despite -q when run in background with & To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1765690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1765690] Re: wget-log file created despite -q when run in background with
Red Hat issue: https://bugzilla.redhat.com/show_bug.cgi?id=1484411 "Running wget with -O and -q in the background yields a file wget-log" Related but (FWICT) not precisely the same issues upstream: * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888691 "wget -b produces empty wget-log file" * https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874590 "wget: creates log file when run in the background", forwarded to https://savannah.gnu.org/bugs/?51181 "Unexpected "Redirecting output to 'wget-log'."" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1765690 Title: wget-log file created despite -q when run in background with & To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1765690/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1764417] [NEW] Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Public bug reported: I've had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I'm thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact), and for now I have no better steps to reproduce this other than "boot, log in". Bug #1663839 (reported against 17.04) seems similar, as does bug #1731428 (reported against 17.10). journalctl output during the issue: Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-settings-daemon 3.28.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Apr 16 17:07:14 2018 InstallationDate: Installed on 2016-10-13 (550 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1764417 Title: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1764417/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1754284] Re: Totem is tearing when fullscreen in Xorg sessions
In addition to Totem, Firefox also exhibits this with fullscreen HTML5 video. Here's a good test: https://www.youtube.com/watch?v=5xkNy9gfKOg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1754284 Title: Totem is tearing when fullscreen in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1754284/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1734891] Re: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file()
My bug #1762400 got marked as a duplicate for this one, but I don't have Dropbox installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1734891 Title: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1734891/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1762400] Re: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file() when trying to open a password-protected 7z archive
*** This bug is a duplicate of bug 1734891 *** https://bugs.launchpad.net/bugs/1734891 Possible duplicates with bug #1607919 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1762400 Title: nautilus crashed with SIGSEGV in nautilus_list_model_get_all_iters_for_file() when trying to open a password-protected 7z archive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1762400/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1733908] Re: In Firefox 57 (Quantum), HTML links' context menu appears in the wrong place
Haven't seen this since upgrading to 18.04, and can't reproduce it following the instructions anymore either, so it appears to be fixed. ** Changed in: firefox (Ubuntu) Status: New => Fix Released ** Summary changed: - In Firefox 57 (Quantum), HTML links' context menu appears in the wrong place + HTML links' context menu appears in the wrong place (since Firefox 57 Quantum) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1733908 Title: HTML links' context menu appears in the wrong place (since Firefox 57 Quantum) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1733908/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1664054] Re: issues when saving image (different from #1064332)
This is currently still present in Bionic's Shotwell 0.28.1-0ubuntu1. ** Also affects: shotwell via https://bugzilla.gnome.org/show_bug.cgi?id=738486 Importance: Unknown Status: Unknown ** Summary changed: - issues when saving image (different from #1064332) + After saving image, Shotwell still thinks image is unsaved -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1664054 Title: After saving image, Shotwell still thinks image is unsaved To manage notifications about this bug go to: https://bugs.launchpad.net/shotwell/+bug/1664054/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1760056] Re: gnome-shell crashed with SIGSEGV in meta_window_get_monitor()
*** This bug is a duplicate of bug 1724439 *** https://bugs.launchpad.net/bugs/1724439 ** Description changed: Had been AFK for a couple of hours with the display turned off, came back and turned it on when this occurred. - I've redirected Gnome shell related log etries away from my syslog so + I've redirected Gnome Shell related log entries away from my syslog so I'm attaching the separate log here. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.28.0-0ubuntu1 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 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 30 12:02:25 2018 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2016-10-13 (532 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - PATH=(custom, user) - XDG_RUNTIME_DIR= - LANG=fi_FI.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + XDG_RUNTIME_DIR= + LANG=fi_FI.UTF-8 + SHELL=/bin/bash SegvAnalysis: - Segfault happened at: 0x7ff6e1385c24:mov 0x18(%rax),%eax - PC (0x7ff6e1385c24) ok - source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! - destination "%eax" ok + Segfault happened at: 0x7ff6e1385c24 :mov 0x18(%rax),%eax + PC (0x7ff6e1385c24) ok + source "0x18(%rax)" (0x0018) not located in a known VMA region (needed readable region)! + destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-shell StacktraceTop: - meta_window_get_monitor () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 - ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 - ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 - () at /usr/lib/libgjs.so.0 - () at /usr/lib/libgjs.so.0 + meta_window_get_monitor () at /usr/lib/x86_64-linux-gnu/libmutter-2.so.0 + ffi_call_unix64 () at /usr/lib/x86_64-linux-gnu/libffi.so.6 + ffi_call () at /usr/lib/x86_64-linux-gnu/libffi.so.6 + () at /usr/lib/libgjs.so.0 + () at /usr/lib/libgjs.so.0 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom debian-transmission dip lp lpadmin lxd plugdev sambashare ssh sudo vboxusers -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1760056 Title: gnome-shell crashed with SIGSEGV in meta_window_get_monitor() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1760056/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758907] [NEW] mp3cut makes output file executable
Public bug reported: == Steps to reproduce == $ wget -q 'https://upload.wikimedia.org/wikipedia/commons/a/a5/Uncle_Josh_and_the_Insurance_Company_-_Cal_Stewart.mp3' && mp3cut -o test.mp3 Uncle_Josh_and_the_Insurance_Company_-_Cal_Stewart.mp3 &>/dev/null && ls -l test.mp3 == Expected result == -rw-r--r-- 1 jani jani 2433848 maali 26 15:45 test.mp3 == Actual result == -rwxr--r-- 1 jani jani 2433848 maali 26 15:45 test.mp3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: poc-streamer 0.4.2-4build1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Mar 26 15:49:22 2018 Dependencies: gcc-8-base 8-20180321-1ubuntu1 libc6 2.27-0ubuntu2 libgcc1 1:8-20180321-1ubuntu1 InstallationDate: Installed on 2016-10-13 (528 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: poc-streamer UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: poc-streamer (Ubuntu) Importance: Undecided Status: New ** Affects: poc-streamer (Debian) Importance: Unknown Status: Unknown ** Tags: amd64 apport-bug bionic ** Bug watch added: Debian Bug tracker #785100 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785100 ** Also affects: poc-streamer (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=785100 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758907 Title: mp3cut makes output file executable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/poc-streamer/+bug/1758907/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot
Looks like you can still enter 'Print' in dconf-editor for a custom action (/org/gnome/settings-daemon/plugins/media-keys/custom- keybindings/customN/binding), so at least there's that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742443 Title: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1742443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1742443] Re: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot
It seems that PrintScreen is now bound to Gnome Settings Daemon, which is used to take screenshots instead of gnome-screenshot. Keyboard settings (in Gnome settings) still has a screenshot shortcuts section in the keyboard shortcut settings, but those too now only trigger Gnome Settings Daemon's screenshot feature, not gnome-screenshot. What's worse, disabling those shortcuts does not allow for remapping PrintScreen back to gnome-screenshot using a custom shortcut, as pressing PrintScreen in the shortcut selector window still just triggers the GSD 'blink' instead of registering PrintScreen as the new shortcut key for the custom command. Only the screenshot section's pre-defined actions allow for PrintScreen to be grabbed. (At least that's what it does here.) When the screenshot shortcuts are disabled, nothing is apparently saved anywhere despite the blink effect. The "Save a screenshot to Pictures" shortcut has to be defined for the screenshots to actually get saved, and then they will be unconditionally saved to $XDG_PICTURES_DIR: https://bugzilla.gnome.org/show_bug.cgi?id=699642 ** Bug watch added: GNOME Bug Tracker #699642 https://bugzilla.gnome.org/show_bug.cgi?id=699642 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1742443 Title: Ubuntu 18.04: PrtSc doesn't trigger gnome-screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-screenshot/+bug/1742443/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758332] [NEW] Flood of "peer a.b.c.d:port is not from a LAN" in syslog
Public bug reported: After upgrading from Xenial to Bionic, my syslog is being spammed by minissdpd. From today's syslog going back three hours: 15.05 jani@saegusa:~$ grep "is not from a LAN" /var/log/syslog | tail Mar 23 15:03:30 saegusa minissdpd[1990]: peer 192.168.1.4:39280 is not from a LAN Mar 23 15:03:33 saegusa minissdpd[1990]: message repeated 3 times: [ peer 192.168.1.4:39280 is not from a LAN] Mar 23 15:03:36 saegusa minissdpd[1990]: peer 192.168.1.10:13206 is not from a LAN Mar 23 15:03:36 saegusa minissdpd[1990]: peer 192.168.1.10:13206 is not from a LAN Mar 23 15:03:51 saegusa minissdpd[1990]: peer 192.168.1.1:32769 is not from a LAN Mar 23 15:04:21 saegusa minissdpd[1990]: message repeated 39 times: [ peer 192.168.1.1:32769 is not from a LAN] Mar 23 15:04:29 saegusa minissdpd[1990]: peer 192.168.1.10:13206 is not from a LAN Mar 23 15:04:29 saegusa minissdpd[1990]: peer 192.168.1.10:13206 is not from a LAN Mar 23 15:04:50 saegusa minissdpd[1990]: peer 192.168.1.1:32769 is not from a LAN Mar 23 15:04:51 saegusa minissdpd[1990]: message repeated 19 times: [ peer 192.168.1.1:32769 is not from a LAN] 15.05 jani@saegusa:~$ grep -c "is not from a LAN" /var/log/syslog 1623 192.168.1.0 is my LAN. According to the upstream report [1], specifying an interface should get rid of the "not from a LAN" messages, and I can confirm that adding "-i eth1" to the value of MiniSSDPd_OTHER_OPTIONS in /etc/default/minissdpd does just that. I don't know how good a solution adding a fixed interface is though, I'd imagine switching to (e.g.) a wifi interface on a system with multiple interfaces would cause the message flood to reappear. *[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890584 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: minissdpd 1.5.20161216-2 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Mar 23 15:25:25 2018 InstallationDate: Installed on 2016-10-13 (525 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: minissdpd UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: minissdpd Importance: Unknown Status: Unknown ** Affects: minissdpd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Bug watch added: Debian Bug tracker #890584 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890584 ** Also affects: minissdpd via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890584 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758332 Title: Flood of "peer a.b.c.d:port is not from a LAN" in syslog To manage notifications about this bug go to: https://bugs.launchpad.net/minissdpd/+bug/1758332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758071] Re: Graphical prompt (pinentry-gnome3) invoked even when connected via ssh
Possible upstream issues: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=842015 -> https://dev.gnupg.org/T2818 (-> https://dev.gnupg.org/T2843#) ** Bug watch added: Debian Bug tracker #842015 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=842015 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758071 Title: Graphical prompt (pinentry-gnome3) invoked even when connected via ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1758071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1758071] [NEW] Graphical prompt (pinentry-gnome3) invoked even when connected via ssh
Public bug reported: When I'm connected to my desktop computer via ssh, with the desktop computer's desktop environment running and unlocked, trying to decrypt a gpg-encrypted file causes gpg-agent to invoke pinentry-gnome3 on the desktop. Assuming I'm physically elsewhere, I'm obviously unable to use the prompt on the desktop to enter the passphrase. This happens despite both pinentry-tty and pinentry-curses being present on the desktop (in addition to pinentry-gnome3), and having GPG_TTY point to the correct tty (export GPG_TTY=$(tty)). Under these circumstances I'd expect gpg-agent to gracefully fall back to non- graphical alternatives. Granted, I've so far only simulated being physically elsewhere by first ssh'ing out of the desktop, then back in again from the other end. If gpg-agent is using some kind of magic to detect that in reality I'm still physically on the desktop, then this report is invalid (although I'd still feel uneasy about such magic). == Steps to reproduce == 1. log in to desktop computer A 2. use another computer B to ssh in to the desktop computer 3. still physically on B, invoke `gpg -d encrypted.gpg` on A (over ssh) == What happens == Graphical passphrase prompt pops up on A, while your ssh terminal on B waits == What I expect to happen == For a non-graphical passphrase prompt (such as pinentry-tty or pinentry-curses) to appear on B's ssh terminal ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gpg-agent 2.2.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Thu Mar 22 16:04:09 2018 InstallationDate: Installed on 2016-10-13 (525 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash SourcePackage: gnupg2 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnupg2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1758071 Title: Graphical prompt (pinentry-gnome3) invoked even when connected via ssh To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg2/+bug/1758071/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs