[Desktop-packages] [Bug 1895941] Re: Screen lock after some minutes while playing vidoes from mpv player.
Well someone requested so here, self explanatory on ppa page, patch in /debian/patches folder.. https://launchpad.net/~mc3man/+archive/ubuntu/mutterpatch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1895941 Title: Screen lock after some minutes while playing vidoes from mpv player. Status in Mutter: Unknown Status in mpv package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I installed mpv player from APT repository. It was working fine but from last week I have been experiencing this issue. The issue is: Screen gets locked while watching video. Normally, this should not have happened. But something has gone wrong. Video continue to play in background but to watch it I need to unlock the screen.I was using wayland when this problem started.. Something is triggering to lock the screen while playing any movies/videos, which is very weird. Let me know if you need more output to resolve this issue. suraj@surtoshwi ~> mpv --version mpv 0.32.0 Copyright © 2000-2020 mpv/MPlayer/mplayer2 projects built on UNKNOWN ffmpeg library versions: libavutil 56.31.100 libavcodec 58.54.100 libavformat 58.29.100 libswscale 5.5.100 libavfilter 7.57.100 libswresample 3.5.100 ffmpeg version: 4.2.4-1ubuntu0.1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mpv 0.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-47.51-generic 5.4.55 Uname: Linux 5.4.0-47-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Sep 17 13:18:02 2020 InstallationDate: Installed on 2020-04-24 (145 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1895941/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870184] Re: Snap store not showing ubuntu repository apt apps inthe store
20200403.d6b9c02 (345) 50MB is the only one that works, some users could revert back to it, most can't.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1870184 Title: Snap store not showing ubuntu repository apt apps inthe store Status in snap-store: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: Invalid Bug description: OS : Ubuntu 20.04 (20200401) Problem : repository (apt) apps are not showing Problem Simulation: Install ubuntu 20.04 current daily build > open Snap Store> Search gnome tweak (or anyother apt apps) > no results Expected Solution: The Snap store should show repository apps or the gnome software should have installed by default. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1870184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870184] Re: Snap store not showing ubuntu repository apt apps inthe store
Still working fine on both my 20.04 installs. $ snap info snap-store name:snap-store summary: Snap Store is a graphical desktop application for discovering, installing and managing snaps on Linux. publisher: Canonical✓ store-url: https://snapcraft.io/snap-store contact: https://bugs.launchpad.net/snap-store/ license: unset description: | Snap Store showcases featured and popular applications with useful descriptions, ratings, reviews and screenshots. Applications can be found either through browsing categories or by searching. Snap Store can also be used to switch channels, view and alter snap permissions and view and submit reviews and ratings. Snap Store is based on GNOME Software, optimized for the Snap experience. commands: - snap-store - snap-store.ubuntu-software snap-id: gjf3IPXoRiipCu9K0kVu52f0H56fIksg tracking: latest/stable/ubuntu-20.04 refresh-date: yesterday at 09:46 EDT channels: latest/stable:20191114.a9948d5 2019-11-14 (209) 44MB - latest/candidate: 20191126.6a93891 2019-11-26 (214) 45MB - latest/beta: 20200403.d6b9c02 2020-04-03 (345) 50MB - latest/edge: 20200403.55a2b6b 2020-04-03 (344) 52MB - installed: 20200403.d6b9c02(345) 50MB - -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1870184 Title: Snap store not showing ubuntu repository apt apps inthe store Status in snap-store: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: Invalid Bug description: OS : Ubuntu 20.04 (20200401) Problem : repository (apt) apps are not showing Problem Simulation: Install ubuntu 20.04 current daily build > open Snap Store> Search gnome tweak (or anyother apt apps) > no results Expected Solution: The Snap store should show repository apps or the gnome software should have installed by default. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1870184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870184] Re: Snap store not showing ubuntu repository apt apps inthe store
Don't see it as hit or miss, the version on the Ubuntu beta image only shows snaps. On an older install it has snap-store 20200401.4cde4f1 which shows both snaps and .deb's Refreshing the beta image install's snap-store from latest/stable: 20191114.a9948d5 to latest/beta: 20200403.d6b9c02 then allows the snap-store to show both snaps and .deb's. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1870184 Title: Snap store not showing ubuntu repository apt apps inthe store Status in snap-store: Confirmed Status in gnome-desktop package in Ubuntu: Invalid Status in gnome-software package in Ubuntu: Invalid Status in gnome-tweaks package in Ubuntu: Invalid Bug description: OS : Ubuntu 20.04 (20200401) Problem : repository (apt) apps are not showing Problem Simulation: Install ubuntu 20.04 current daily build > open Snap Store> Search gnome tweak (or anyother apt apps) > no results Expected Solution: The Snap store should show repository apps or the gnome software should have installed by default. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store/+bug/1870184/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
List of some mpv issues with gnome wayland, the window deco is somewhat mitigated by the new osc overlay that will, by default show in the absence of window deco. https://github.com/mpv-player/mpv/wiki/FAQ#i-use-gnome-wayland-and-i-have-xyz-problem -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Fix Released Status in Mutter: New Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
On 2/11/20 11:16 AM, Imre Péntek wrote: > as far as I can tell this bug is not present in 19.10 (fixed) > No, clearly never fixed and still an issue in 20.04. Only way around is for user from cli to use gnome-session-inhibit mpv /path/to/file -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Fix Released Status in Mutter: New Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856927] Re: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to grilo in Ubuntu. https://bugs.launchpad.net/bugs/1856927 Title: totem crashed with SIGSEGV in build_flavored_key() from insert_key_mapping() Status in grilo package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034 --- Test case: Fresh 20.04 install, updated Open totem What happens: segfault Installing grilo-plugins-0.3-extra allows totem to open fine. ProblemType: Crash DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 19:51:40 2019 ExecutablePath: /usr/bin/totem ExecutableTimestamp: 1570435741 InstallationDate: Installed on 2019-12-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) ProcCmdline: /usr/bin/totem --gapplication-service ProcCwd: /home/doug ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f76b92f6dd6:movzbl (%rax),%eax PC (0x7f76b92f6dd6) ok source "(%rax)" (0x) not located in a known VMA region (needed readable region)! destination "%eax" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: totem StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so grl_tracker_setup_key_mappings () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so ?? () from /lib/x86_64-linux-gnu/libtracker-sparql-2.0.so.0 Title: totem crashed with SIGSEGV in grl_tracker_setup_key_mappings() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo/+bug/1856927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856915] Re: Totem segfaults without grilo-plugins-0.3-extra (i.e some or all of it's deps) installed
*** This bug is a duplicate of bug 1856927 *** https://bugs.launchpad.net/bugs/1856927 Didn't see much that I could do apport-collect probably wouldn't be specific The backtrace I got was sparse. So edited the .conf so report was upload to launchpad, marked this as a dupe.. ** This bug has been marked a duplicate of private bug 1856927 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1856915 Title: Totem segfaults without grilo-plugins-0.3-extra (i.e some or all of it's deps) installed Status in totem package in Ubuntu: New Bug description: Test case: A fresh 20.04 install, updated Open totem in a terminal. What happens: segfaults with 0x7fffe14f3dd6 in () at /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so Installing grilo-plugins-0.3-extra allows totem to open fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 21:16:59 2019 InstallationDate: Installed on 2019-12-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1856915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1856915] [NEW] Totem segfaults without grilo-plugins-0.3-extra (i.e some or all of it's deps) installed
Public bug reported: Test case: A fresh 20.04 install, updated Open totem in a terminal. What happens: segfaults with 0x7fffe14f3dd6 in () at /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so Installing grilo-plugins-0.3-extra allows totem to open fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 21:16:59 2019 InstallationDate: Installed on 2019-12-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' ** Affects: totem (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1856915 Title: Totem segfaults without grilo-plugins-0.3-extra (i.e some or all of it's deps) installed Status in totem package in Ubuntu: New Bug description: Test case: A fresh 20.04 install, updated Open totem in a terminal. What happens: segfaults with 0x7fffe14f3dd6 in () at /usr/lib/x86_64-linux-gnu/grilo-0.3/libgrltracker.so Installing grilo-plugins-0.3-extra allows totem to open fine. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: totem 3.34.1-2ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Dec 18 21:16:59 2019 InstallationDate: Installed on 2019-12-19 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191217) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1856915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824282] Re: Add a mode that load nvidia.ko only so that we display on intel and do cuda deep learning in NV GPU
New bug https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1851416 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1824282 Title: Add a mode that load nvidia.ko only so that we display on intel and do cuda deep learning in NV GPU Status in nvidia-prime package in Ubuntu: Fix Released Bug description: Per current NV and intel GPU driver, if we load nvidia.ko only, we can do display on intel GPU and leave the NV to deep learning for a graphic workstation. I proposed to add a mode might call "intel+nv_cuda" for this mode. Test procedure: 1. install the new package on a platform with both intel and NV graphic card. 2. $ sudo prime-select intel+nv_cuda; sudo reboot 3. $ nvidia-smi # it will show the nvidia GPU status and we will found that no GUI process use any NV GPU memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1824282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1824282] Re: Add a mode that load nvidia.ko only so that we display on intel and do cuda deep learning in NV GPU
I think this was poorly implemented. If any of the concerned parties wish to discuss here, great. Otherwise I'll file a bug on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1824282 Title: Add a mode that load nvidia.ko only so that we display on intel and do cuda deep learning in NV GPU Status in nvidia-prime package in Ubuntu: Fix Released Bug description: Per current NV and intel GPU driver, if we load nvidia.ko only, we can do display on intel GPU and leave the NV to deep learning for a graphic workstation. I proposed to add a mode might call "intel+nv_cuda" for this mode. Test procedure: 1. install the new package on a platform with both intel and NV graphic card. 2. $ sudo prime-select intel+nv_cuda; sudo reboot 3. $ nvidia-smi # it will show the nvidia GPU status and we will found that no GUI process use any NV GPU memory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1824282/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1841696] Re: Upgrade of g-c-c from 1:3.32.2-1ubuntu4 to 1:3.33.90-1ubuntu2 installs media libraries
** Description changed: - Ex. - + Ex. + $ sudo apt -s install gnome-control-center - [sudo] password for doug: + [sudo] password for doug: Reading package lists... Done - Building dependency tree + Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: - libebook-contacts-1.2-2 libip4tc0 libip6tc0 libmysqlclient20 libvpx5 + libebook-contacts-1.2-2 libip4tc0 libip6tc0 libmysqlclient20 libvpx5 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: - gnome-control-center-data gstreamer1.0-libav i965-va-driver - intel-media-va-driver libaacs0 libaom0 libass9 libavcodec58 libavfilter7 - libavformat58 libavutil56 libbdplus0 libbluray2 libbs2b0 libchromaprint1 - libcodec2-0.8.1 libfftw3-double3 libflite1 libgme0 libgsm1 libgssdp-1.2-0 - libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libigdgmm9 liblilv-0-0 - libmysofa0 libnorm1 libopenjp2-7 libopenmpt0 libpgm-5.2-0 libpostproc55 - librubberband2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 - librygel-server-2.6-2 libserd-0-0 libshine3 libsnappy1v5 libsord-0-0 - libsratom-0-0 libssh-gcrypt-4 libswresample3 libswscale5 libva-drm2 - libva-x11-2 libva2 libvdpau1 libvidstab1.1 libx264-155 libx265-176 - libxvidcore4 libzmq5 libzvbi-common libzvbi0 mesa-va-drivers - mesa-vdpau-drivers rygel va-driver-all vdpau-driver-all + gnome-control-center-data gstreamer1.0-libav i965-va-driver + intel-media-va-driver libaacs0 libaom0 libass9 libavcodec58 libavfilter7 + libavformat58 libavutil56 libbdplus0 libbluray2 libbs2b0 libchromaprint1 + libcodec2-0.8.1 libfftw3-double3 libflite1 libgme0 libgsm1 libgssdp-1.2-0 + libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libigdgmm9 liblilv-0-0 + libmysofa0 libnorm1 libopenjp2-7 libopenmpt0 libpgm-5.2-0 libpostproc55 + librubberband2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 + librygel-server-2.6-2 libserd-0-0 libshine3 libsnappy1v5 libsord-0-0 + libsratom-0-0 libssh-gcrypt-4 libswresample3 libswscale5 libva-drm2 + libva-x11-2 libva2 libvdpau1 libvidstab1.1 libx264-155 libx265-176 + libxvidcore4 libzmq5 libzvbi-common libzvbi0 mesa-va-drivers + mesa-vdpau-drivers rygel va-driver-all vdpau-driver-all Suggested packages: - gnome-user-share realmd libcanberra-gtk-module i965-va-driver-shaders - libbluray-bdj libfftw3-bin libfftw3-dev serdi sordi rygel-playbin - rygel-preferences rygel-ruih rygel-tracker tumbler gstreamer1.0-plugins-ugly - libvdpau-va-gl1 nvidia-vdpau-driver nvidia-legacy-340xx-vdpau-driver - nvidia-legacy-304xx-vdpau-driver + gnome-user-share realmd libcanberra-gtk-module i965-va-driver-shaders + libbluray-bdj libfftw3-bin libfftw3-dev serdi sordi rygel-playbin + rygel-preferences rygel-ruih rygel-tracker tumbler gstreamer1.0-plugins-ugly + libvdpau-va-gl1 nvidia-vdpau-driver nvidia-legacy-340xx-vdpau-driver + nvidia-legacy-304xx-vdpau-driver The following NEW packages will be installed: - gstreamer1.0-libav i965-va-driver intel-media-va-driver libaacs0 libaom0 - libass9 libavcodec58 libavfilter7 libavformat58 libavutil56 libbdplus0 - libbluray2 libbs2b0 libchromaprint1 libcodec2-0.8.1 libfftw3-double3 - libflite1 libgme0 libgsm1 libgssdp-1.2-0 libgupnp-1.2-0 libgupnp-av-1.0-2 - libgupnp-dlna-2.0-3 libigdgmm9 liblilv-0-0 libmysofa0 libnorm1 libopenjp2-7 - libopenmpt0 libpgm-5.2-0 libpostproc55 librubberband2 librygel-core-2.6-2 - librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libserd-0-0 - libshine3 libsnappy1v5 libsord-0-0 libsratom-0-0 libssh-gcrypt-4 - libswresample3 libswscale5 libva-drm2 libva-x11-2 libva2 libvdpau1 - libvidstab1.1 libx264-155 libx265-176 libxvidcore4 libzmq5 libzvbi-common - libzvbi0 mesa-va-drivers mesa-vdpau-drivers rygel va-driver-all - vdpau-driver-all + gstreamer1.0-libav i965-va-driver intel-media-va-driver libaacs0 libaom0 + libass9 libavcodec58 libavfilter7 libavformat58 libavutil56 libbdplus0 + libbluray2 libbs2b0 libchromaprint1 libcodec2-0.8.1 libfftw3-double3 + libflite1 libgme0 libgsm1 libgssdp-1.2-0 libgupnp-1.2-0 libgupnp-av-1.0-2 + libgupnp-dlna-2.0-3 libigdgmm9 liblilv-0-0 libmysofa0 libnorm1 libopenjp2-7 + libopenmpt0 libpgm-5.2-0 libpostproc55 librubberband2 librygel-core-2.6-2 + librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libserd-0-0 + libshine3 libsnappy1v5 libsord-0-0 libsratom-0-0 libssh-gcrypt-4 + libswresample3 libswscale5 libva-drm2 libva-x11-2 libva2 libvdpau1 + libvidstab1.1 libx264-155 libx265-176 libxvidcore4 libzmq5 libzvbi-common + libzvbi0 mesa-va-drivers mesa-vdpau-drivers rygel va-driver-all + vdpau-driver-all The following packages will be upgraded: - gnome-control-center gnome-control-center-data + gnome-control-center gnome-control-center-data 2 upgraded, 60 newly installed, 0 to remove and 14 not
[Desktop-packages] [Bug 1841696] [NEW] Upgrade of g-c-c from 1:3.32.2-1ubuntu4 to 1:3.33.90-1ubuntu2 installs media libraries
Public bug reported: Ex. $ sudo apt -s install gnome-control-center [sudo] password for doug: Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: libebook-contacts-1.2-2 libip4tc0 libip6tc0 libmysqlclient20 libvpx5 Use 'sudo apt autoremove' to remove them. The following additional packages will be installed: gnome-control-center-data gstreamer1.0-libav i965-va-driver intel-media-va-driver libaacs0 libaom0 libass9 libavcodec58 libavfilter7 libavformat58 libavutil56 libbdplus0 libbluray2 libbs2b0 libchromaprint1 libcodec2-0.8.1 libfftw3-double3 libflite1 libgme0 libgsm1 libgssdp-1.2-0 libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libigdgmm9 liblilv-0-0 libmysofa0 libnorm1 libopenjp2-7 libopenmpt0 libpgm-5.2-0 libpostproc55 librubberband2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libserd-0-0 libshine3 libsnappy1v5 libsord-0-0 libsratom-0-0 libssh-gcrypt-4 libswresample3 libswscale5 libva-drm2 libva-x11-2 libva2 libvdpau1 libvidstab1.1 libx264-155 libx265-176 libxvidcore4 libzmq5 libzvbi-common libzvbi0 mesa-va-drivers mesa-vdpau-drivers rygel va-driver-all vdpau-driver-all Suggested packages: gnome-user-share realmd libcanberra-gtk-module i965-va-driver-shaders libbluray-bdj libfftw3-bin libfftw3-dev serdi sordi rygel-playbin rygel-preferences rygel-ruih rygel-tracker tumbler gstreamer1.0-plugins-ugly libvdpau-va-gl1 nvidia-vdpau-driver nvidia-legacy-340xx-vdpau-driver nvidia-legacy-304xx-vdpau-driver The following NEW packages will be installed: gstreamer1.0-libav i965-va-driver intel-media-va-driver libaacs0 libaom0 libass9 libavcodec58 libavfilter7 libavformat58 libavutil56 libbdplus0 libbluray2 libbs2b0 libchromaprint1 libcodec2-0.8.1 libfftw3-double3 libflite1 libgme0 libgsm1 libgssdp-1.2-0 libgupnp-1.2-0 libgupnp-av-1.0-2 libgupnp-dlna-2.0-3 libigdgmm9 liblilv-0-0 libmysofa0 libnorm1 libopenjp2-7 libopenmpt0 libpgm-5.2-0 libpostproc55 librubberband2 librygel-core-2.6-2 librygel-db-2.6-2 librygel-renderer-2.6-2 librygel-server-2.6-2 libserd-0-0 libshine3 libsnappy1v5 libsord-0-0 libsratom-0-0 libssh-gcrypt-4 libswresample3 libswscale5 libva-drm2 libva-x11-2 libva2 libvdpau1 libvidstab1.1 libx264-155 libx265-176 libxvidcore4 libzmq5 libzvbi-common libzvbi0 mesa-va-drivers mesa-vdpau-drivers rygel va-driver-all vdpau-driver-all The following packages will be upgraded: gnome-control-center gnome-control-center-data 2 upgraded, 60 newly installed, 0 to remove and 14 not upgraded. Inst gnome-control-center [1:3.32.2-1ubuntu4] (1:3.33.90-1ubuntu2 Ubuntu:19.10/eoan [amd64]) [] Inst gnome-control-center-data [1:3.32.2-1ubuntu4] (1:3.33.90-1ubuntu2 Ubuntu:19.10/eoan [all]) Inst libaom0 (1.0.0-3 Ubuntu:19.10/eoan [amd64]) Inst libva2 (2.5.0-1 Ubuntu:19.10/eoan [amd64]) Inst libva-drm2 (2.5.0-1 Ubuntu:19.10/eoan [amd64]) Inst libva-x11-2 (2.5.0-1 Ubuntu:19.10/eoan [amd64]) Inst libvdpau1 (1.2-1ubuntu1 Ubuntu:19.10/eoan [amd64]) Inst libavutil56 (7:4.1.4-1build2 Ubuntu:19.10/eoan [amd64]) Inst libcodec2-0.8.1 (0.8.1-2 Ubuntu:19.10/eoan [amd64]) Inst libgsm1 (1.0.18-2 Ubuntu:19.10/eoan [amd64]) Inst libopenjp2-7 (2.3.0-2 Ubuntu:19.10/eoan [amd64]) Inst libshine3 (3.1.1-2 Ubuntu:19.10/eoan [amd64]) Inst libsnappy1v5 (1.1.7-1 Ubuntu:19.10/eoan [amd64]) Inst libswresample3 (7:4.1.4-1build2 Ubuntu:19.10/eoan [amd64]) Inst libx264-155 (2:0.155.2917+git0a84d98-2 Ubuntu:19.10/eoan [amd64]) Inst libx265-176 (3.1.1-2 Ubuntu:19.10/eoan [amd64]) Inst libxvidcore4 (2:1.3.5-1 Ubuntu:19.10/eoan [amd64]) Inst libzvbi-common (0.2.35-16 Ubuntu:19.10/eoan [all]) Inst libzvbi0 (0.2.35-16 Ubuntu:19.10/eoan [amd64]) Inst libavcodec58 (7:4.1.4-1build2 Ubuntu:19.10/eoan [amd64]) Inst libass9 (1:0.14.0-2 Ubuntu:19.10/eoan [amd64]) Inst libbluray2 (1:1.1.2-2 Ubuntu:19.10/eoan [amd64]) Inst libchromaprint1 (1.4.3-3 Ubuntu:19.10/eoan [amd64]) Inst libgme0 (0.6.2-1 Ubuntu:19.10/eoan [amd64]) Inst libopenmpt0 (0.4.6-1 Ubuntu:19.10/eoan [amd64]) Inst libssh-gcrypt-4 (0.9.0-1 Ubuntu:19.10/eoan [amd64]) Inst libavformat58 (7:4.1.4-1build2 Ubuntu:19.10/eoan [amd64]) Inst libbs2b0 (3.1.0+dfsg-2.2 Ubuntu:19.10/eoan [amd64]) Inst libflite1 (2.1-release-3 Ubuntu:19.10/eoan [amd64]) Inst libserd-0-0 (0.28.0~dfsg0-1 Ubuntu:19.10/eoan [amd64]) Inst libsord-0-0 (0.16.0~dfsg0-1 Ubuntu:19.10/eoan [amd64]) Inst libsratom-0-0 (0.6.0~dfsg0-1 Ubuntu:19.10/eoan [amd64]) Inst liblilv-0-0 (0.24.4~dfsg0-1 Ubuntu:19.10/eoan [amd64]) Inst libmysofa0 (0.7~dfsg0-1 Ubuntu:19.10/eoan [amd64]) Inst libpostproc55 (7:4.1.4-1build2 Ubuntu:19.10/eoan [amd64]) Inst libfftw3-double3 (3.3.8-2 Ubuntu:19.10/eoan [amd64]) Inst librubberband2 (1.8.1-7ubuntu2 Ubuntu:19.10/eoan [amd64]) Inst libswscale5 (7:4.1.4-1build2 Ubuntu:19.10/eoan [amd64]) Inst libvidstab1.1 (1.1.0-2 Ubuntu:19.10/eoan [amd64]) Inst libnorm1 (1.5.8+dfsg2-1 Ubuntu:19.10/eoan
[Desktop-packages] [Bug 1835625] Re: Shows old snap edge version of thunderbird
** Attachment added: "screenshot of search result" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1835625/+attachment/5275407/+files/Screenshot%20from%202019-07-06%2015-02-08.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1835625 Title: Shows old snap edge version of thunderbird Status in gnome-software package in Ubuntu: New Bug description: Test case: Open ubuntu-software, search thunderbird Version returned is an old edge version of thunderbird not meant to be used. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-software 3.30.6-2ubuntu8 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 6 14:57:47 2019 InstallationDate: Installed on 2019-07-03 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190703) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu8 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1835625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1835625] [NEW] Shows old snap edge version of thunderbird
Public bug reported: Test case: Open ubuntu-software, search thunderbird Version returned is an old edge version of thunderbird not meant to be used. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-software 3.30.6-2ubuntu8 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 6 14:57:47 2019 InstallationDate: Installed on 2019-07-03 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190703) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu8 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan third-party-packages -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1835625 Title: Shows old snap edge version of thunderbird Status in gnome-software package in Ubuntu: New Bug description: Test case: Open ubuntu-software, search thunderbird Version returned is an old edge version of thunderbird not meant to be used. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-software 3.30.6-2ubuntu8 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jul 6 14:57:47 2019 InstallationDate: Installed on 2019-07-03 (2 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190703) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.30.6-2ubuntu8 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1835625/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833832] Re: NVIDIA kernel module fails with KMS on optimus hardware
Fixed with latest gdm3 package, i.e 3.32.0-1ubuntu2 ** This bug is no longer a duplicate of bug 1716857 nvidia-drm.modeset=1 results in no monitors detected by Xorg ** Changed in: gdm3 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1833832 Title: NVIDIA kernel module fails with KMS on optimus hardware Status in gdm3 package in Ubuntu: Fix Released Bug description: Test case; An optimus laptop fresh 19.10 install, updated. Install nvidia-driver-430 Enable nvidia-drm.modeset ( done here thru a .conf /etc/modprobe.d Reboot What happens: Boots to login screen, all attempts to log into a ubuntu session loop back to log in screen Attached log from journalctl ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 22 21:13:04 2019 InstallationDate: Installed on 2019-06-22 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2019-06-22T20:52:09.277952 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1833832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1833832] [NEW] NVIDIA kernel module fails with KMS on optimus hardware
Public bug reported: Test case; An optimus laptop fresh 19.10 install, updated. Install nvidia-driver-430 Enable nvidia-drm.modeset ( done here thru a .conf /etc/modprobe.d Reboot What happens: Boots to login screen, all attempts to log into a ubuntu session loop back to log in screen Attached log from journalctl ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 22 21:13:04 2019 InstallationDate: Installed on 2019-06-22 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2019-06-22T20:52:09.277952 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan nvidia-drm.modeset ** Attachment added: "journalctl on attempted login" https://bugs.launchpad.net/bugs/1833832/+attachment/5272427/+files/1.log ** Summary changed: - NVIDIA kernel module fails with KMs on optimus hardware + NVIDIA kernel module fails with KMS on optimus hardware -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1833832 Title: NVIDIA kernel module fails with KMS on optimus hardware Status in gdm3 package in Ubuntu: New Bug description: Test case; An optimus laptop fresh 19.10 install, updated. Install nvidia-driver-430 Enable nvidia-drm.modeset ( done here thru a .conf /etc/modprobe.d Reboot What happens: Boots to login screen, all attempts to log into a ubuntu session loop back to log in screen Attached log from journalctl ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gdm3 3.32.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-17.18-generic 5.0.8 Uname: Linux 5.0.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu3 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jun 22 21:13:04 2019 InstallationDate: Installed on 2019-06-22 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190606) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.gdm3.custom.conf: [modified] mtime.conffile..etc.gdm3.custom.conf: 2019-06-22T20:52:09.277952 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1833832/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820542] Re: In a wayland session opening text file in gedit causes busy cursor
What also happens is if you move a window the busy cursor halts. But this is just temporary, opening a new window causes it to start up again. So only way to really stop is too log out. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1820542 Title: In a wayland session opening text file in gedit causes busy cursor Status in GNOME Shell: Unknown Status in gnome-shell package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1820542/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1820542] [NEW] In a wayland session opening text file in gedit causes busy cursor
Public bug reported: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.sku: LENOVO_BI_IDEAPAD dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.97-1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: wayland (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco regression reproducible single-occurrence ubuntu wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1820542 Title: In a wayland session opening text file in gedit causes busy cursor Status in wayland package in Ubuntu: New Bug description: Test case: Fresh 19.04 daily current image, updated Log in to a wayland session, open a single tesxt file in gedit Move cursor out of gedit window or close gedit What happens: get busy cursor forever. Only way to stop is to either logout or open 2 files (tabs) in gedit ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: libwayland-cursor0 1.16.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Mar 17 16:55:31 2019 DistUpgraded: Fresh install DistroCodename: disco DistroVariant: ubuntu GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2019-03-17 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) MachineType: LENOVO 20217 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic root=UUID=347ed652-bf05-4fe8-a58a-3788f704faf4 ro quiet splash vt.handoff=1 SourcePackage: wayland UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version:
[Desktop-packages] [Bug 1819795] Re: Launcher & panel are solid so..
A g-s update made panel solid so at least on same page. The override file needs editing.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1819795 Title: Launcher & panel are solid so.. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: See this - sudo glib-compile-schemas /usr/share/glib-2.0/schemas [sudo] password for doug: override for key “transparency-mode” in schema “org.gnome.shell.extensions.dash-to-dock” in override file “/usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override” is not in the list of valid choices; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 19:50:54 2019 InstallationDate: Installed on 2019-03-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1819795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819795] [NEW] Launcher & panel are solid so..
Public bug reported: See this - sudo glib-compile-schemas /usr/share/glib-2.0/schemas [sudo] password for doug: override for key “transparency-mode” in schema “org.gnome.shell.extensions.dash-to-dock” in override file “/usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override” is not in the list of valid choices; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 19:50:54 2019 InstallationDate: Installed on 2019-03-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell-extension-ubuntu-dock (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Summary changed: - Launcher is solid color, panel is transparent + Launcher is solid color, panel is translucent ** Summary changed: - Launcher is solid color, panel is translucent + Launcher & panel are solid so.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1819795 Title: Launcher & panel are solid so.. Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: New Bug description: See this - sudo glib-compile-schemas /usr/share/glib-2.0/schemas [sudo] password for doug: override for key “transparency-mode” in schema “org.gnome.shell.extensions.dash-to-dock” in override file “/usr/share/glib-2.0/schemas/10_ubuntu-dock.gschema.override” is not in the list of valid choices; ignoring override for this key. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: gnome-shell-extension-ubuntu-dock 64ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0 Uname: Linux 5.0.0-7-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Mar 12 19:50:54 2019 InstallationDate: Installed on 2019-03-12 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190312) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-shell-extension-ubuntu-dock UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1819795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1819368] Re: unity-control-center crashed with SIGSEGV in free()
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to unity-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1819368 Title: unity-control-center crashed with SIGSEGV in free() Status in unity-control-center package in Ubuntu: New Bug description: Happens when trying to open the info (details) panel ProblemType: Crash DistroRelease: Ubuntu 19.04 Package: unity-control-center 15.04.0+19.04.20190209-0ubuntu2 ProcVersionSignature: Ubuntu 4.19.0-13.14-generic 4.19.20 Uname: Linux 4.19.0-13-generic x86_64 ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Mar 10 15:09:20 2019 ExecutablePath: /usr/bin/unity-control-center ExecutableTimestamp: 1551456572 InstallationDate: Installed on 2019-03-09 (1 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1) ProcCmdline: unity-control-center info --verbose ProcCwd: /home/doug SegvAnalysis: Segfault happened at: 0x7f17f1c1f25d <__GI___libc_free+29>: mov -0x8(%rdi),%rax PC (0x7f17f1c1f25d) ok source "-0x8(%rdi)" (0xfff8) not located in a known VMA region (needed readable region)! destination "%rax" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity-control-center StacktraceTop: __GI___libc_free (mem=0x1) at malloc.c:3109 g_unix_mount_free () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so () at /usr/lib/x86_64-linux-gnu/unity-control-center-1/panels/libinfo.so g_type_create_instance () at /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: unity-control-center crashed with SIGSEGV in __GI___libc_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1819368/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740771] Re: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1)
** Tags added: disco -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1740771 Title: the screen keeps locking while I watch video (missing support for Wayland's idle_inhibit_unstable_v1) Status in MPV: Unknown Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/20 --- Reproducibility: 100% reproducible steps to reproduce: 1. $ mpv -fv anyvideo_long_enough.anyformat 2. now please refrain from any mouse/keyboard activity, wait for the screensaver to activate 3. screensaver activates problem: the screensaver activates desired behaviour: the screensaver shouldn't activate long description: Hello, the screen keeps locking while I watch video with mpv. Basically the screensaver gets activated. but according to man mpv: --heartbeat-cmd= WARNING: This option is redundant with Lua scripting. Further, it shouldn't be needed for disabling screensaver anyway, since mpv will call xdg-screensaver when using X11 backend. As a consequence this option has been deprecated with no direct replacement. ... That all said as the screen getting locked contradicts the manpage, I consider this a bug. Thank you for the fix in advance. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: mpv 0.26.0-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 1 19:10:42 2018 InstallationDate: Installed on 2017-12-25 (7 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=hu_HU.UTF-8 SHELL=/bin/bash SourcePackage: mpv UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mpv/+bug/1740771/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815775] Re: libnautilus-fileroller.so fails on .deb archives
I tracked it down, seems an interesting nautilus extension I was testing (3rd party provided) somehow caused this even though it worked fine and there were no apparent bad effects other than this. (- a mediainfo extension exposed thru properties menu. The journalctl -f message at point of 'hang' was g_file_resolve_relative_path: assertion 'relative_path != NULL' failed So marking invalid, sorry about that.. ** Changed in: nautilus (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1815775 Title: libnautilus-fileroller.so fails on .deb archives Status in nautilus package in Ubuntu: Invalid Bug description: Test Case: Place any .deb file in a user folder ( ex. Documents Right click on > Extract here This works ok, a folder using the.deb named is created. Inside will be 3 files. Right click on either of the archives inside that folder > extract here or extract to What happens: An extracted folder is created with nothing in it. Nautilus's file operations hangs on "Preparing" > Verifying destination. Cancelling the operation has no effect, nautilus is perpetually in that operation till nautilus is quit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: file-roller 3.31.90-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 10:10:07 2019 InstallationDate: Installed on 2019-02-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1815775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1815775] [NEW] libnautilus-fileroller.so fails on .deb archives
Public bug reported: Test Case: Place any .deb file in a user folder ( ex. Documents Right click on > Extract here This works ok, a folder using the.deb named is created. Inside will be 3 files. Right click on either of the archives inside that folder > extract here or extract to What happens: An extracted folder is created with nothing in it. Nautilus's file operations hangs on "Preparing" > Verifying destination. Cancelling the operation has no effect, nautilus is perpetually in that operation till nautilus is quit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: file-roller 3.31.90-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 10:10:07 2019 InstallationDate: Installed on 2019-02-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: file-roller (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco third-party-packages ** Attachment added: "nautilus hang on extracting control.tar.xz" https://bugs.launchpad.net/bugs/1815775/+attachment/5238368/+files/Screenshot%20from%202019-02-13%2010-26-41.png ** Description changed: Test Case: Place any .deb file in a user folder ( ex. Documents Right click on > Extract here This works ok, a folder using the.deb named is created. Inside will be 3 files. Right click on either of the archives inside that folder > extract here or extract to What happens: An extracted folder is created with nothing in it. Nautilus's file operations hangs on "Preparing" > Verifying destination. - Cancelling the has no effect, nautilus is perpetually in that operation till nautilus is quit. + Cancelling the operation has no effect, nautilus is perpetually in that operation till nautilus is quit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: file-roller 3.31.90-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 10:10:07 2019 InstallationDate: Installed on 2019-02-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1815775 Title: libnautilus-fileroller.so fails on .deb archives Status in file-roller package in Ubuntu: New Bug description: Test Case: Place any .deb file in a user folder ( ex. Documents Right click on > Extract here This works ok, a folder using the.deb named is created. Inside will be 3 files. Right click on either of the archives inside that folder > extract here or extract to What happens: An extracted folder is created with nothing in it. Nautilus's file operations hangs on "Preparing" > Verifying destination. Cancelling the operation has no effect, nautilus is perpetually in that operation till nautilus is quit. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: file-roller 3.31.90-1 ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18 Uname: Linux 4.19.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu20 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 13 10:10:07 2019 InstallationDate: Installed on 2019-02-08 (4 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1815775/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend
Maybe I'm missing the point of this bug, if so sorry about that. The bug seems to be basically about being able to log into a wayland session while using nvidia drivers. Though the description has changed a time or two. So question could be simply rephrased - Does the fix released imply that nvidia should be working on 19.04 on all nvidia devices? It's stated above that - "mutter 3.30.2 in 18.10 & 19.04: * EGLDevice compiled and working * EGLStreams' new build deps are missing so not configured, but compiled in anyway by accident because the new build deps were weak, and it's working**" "** EGLStreams working means Wayland clients get full Nvidia acceleration but I thought it was broken for a while because that also includes 100% CPU use by [kworker/u16:3+events_unbound]. Possible driver bug? " What I mentioned is that no m series nvidia i've tested gets nvidia support in a wayland session. (- when logging into wayland one is automatically switched to Intel -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1805444 Title: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend Status in mutter package in Ubuntu: Fix Released Bug description: Wayland sessions don't work with the Nvidia driver in 18.04, even after enabling them via the kernel command line 'nvidia- drm.modeset=1'. [Original description] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due to following missing changes in mutter 3.28.3-2~ubuntu18.04.2 commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84 Author: Miguel A. Vico Date: Thu Jun 7 16:29:44 2018 -0700 renderer/native: Choose first EGL config for non-GBM backends Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only choose EGL configs that match the GBM_FORMAT_XRGB pixel format. However, there won't be any EGL config satisfying such criteria for non-GBM backends, such as EGLDevice. This change will let us choose the first EGL config for the EGLDevice backend, while still forcing GBM_FORMAT_XRGB configs for the GBM one. Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2 commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b Author: Jonas Ådahl Date: Tue Nov 14 16:08:52 2017 +0800 renderer/native: Also wrap flip closures for EGLStreams When using the EGLStream backend, the MetaRendererNative passed a GClosure to KMS when using EGLStreams, but KMS flip callback event handler in meta-gpu-kms.c expected a closure wrapped in a closure container, meaning it'd instead crash when using EGLStreams. Make the flip handler get what it expects also when using EGLStreams by wrapping the flip closure in the container before handing it over to EGL. https://bugzilla.gnome.org/show_bug.cgi?id=790316 apt-cache policy mutter mutter: Installed: 3.28.3-2~ubuntu18.04.2 Candidate: 3.28.3-2~ubuntu18.04.2 Version table: *** 3.28.3-2~ubuntu18.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1720624] Re: Ubuntu 17.10 blank CD or audio CD not detected
On 1/17/19 3:13 PM, corrado venturini wrote: > I have again the same/similar problem with Ubuntu 18.04, 18.10 and 19.04. > should i open a new bug? > I would suspect so as this is fix released & personally see no current issues in 18.04 . If seeing this on a laptop you should confirm it's not a drive issue as cd/dvd drives in laptops are generally low quality and fail in different ways quite often. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1720624 Title: Ubuntu 17.10 blank CD or audio CD not detected Status in lshw package in Ubuntu: Invalid Status in nautilus package in Ubuntu: Invalid Status in udisks2 package in Ubuntu: Fix Released Status in lshw source package in Artful: Invalid Status in nautilus source package in Artful: Invalid Status in udisks2 source package in Artful: Fix Released Bug description: Audio CD are not detected while data CD and data DVD are detected. When I insert a data CD or DVD I have a notification and I see the CD in files. With audio CD nothing happens. Also empty CD and DVD are not detected. No problem on same PC, different partition with Ubuntu 16.04. I have the same problem on 3 different PC running Ubuntu 17.10. I opened a question about this problem: https://answers.launchpad.net/ubuntu/+question/658807 and I was invited to open a bug. In Ubuntu 16.04 when I insert a blank CD I see a box with a message 'You have just inserted a blank CD. Choose what application ...' when I insert an audio CD I see a box with a message 'You have just inserted a Audio CD. Choose what application ...' In Ubuntu 17.10 when I insert a blank CD or an Audio CD nothing happens so I can't access the CD. when I insert a data CD od DVD I see a notification at the top of the screen and I can see the inserted CD in files. In attachment: screenshot of messages from Ubuntu 16.04 messages from 'sudo lshw -c disk' in Ubuntu 16.04 messages from 'sudo lshw -c disk' in Ubuntu 17.10 corrado@corrado-0926:~$ inxi -Fx System:Host: corrado-0926 Kernel: 4.13.0-12-generic x86_64 bits: 64 gcc: 7.2.0 Desktop: Gnome 3.26.0 (Gtk 3.22.21-0ubuntu1) Distro: Ubuntu Artful Aardvark (development branch) Machine: Device: desktop Mobo: ASRock model: H110M-G/M.2 serial: N/A UEFI: American Megatrends v: P1.10 date: 05/11/2017 CPU: Dual core Intel Core i3-7100 (-HT-MCP-) arch: Skylake rev.9 cache: 3072 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648 clock speeds: max: 3900 MHz 1: 3900 MHz 2: 3900 MHz 3: 3900 MHz 4: 3900 MHz Graphics: Card: Intel HD Graphics 630 bus-ID: 00:02.0 Display Server: x11 (X.Org 1.19.3 ) driver: i915 Resolution: 1680x1050@59.88hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) version: 4.5 Mesa 17.2.1 Direct Render: Yes Audio: Card Intel Sunrise Point-H HD Audio driver: snd_hda_intel bus-ID: 00:1f.3 Sound: Advanced Linux Sound Architecture v: k4.13.0-12-generic Network: Card: Intel Ethernet Connection (2) I219-V driver: e1000e v: 3.2.6-k bus-ID: 00:1f.6 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 70:85:c2:44:7b:86 Drives:HDD Total Size: 1000.2GB (6.2% used) ID-1: /dev/sda model: TOSHIBA_DT01ACA1 size: 1000.2GB Partition: ID-1: / size: 32G used: 6.0G (20%) fs: ext4 dev: /dev/sda3 ID-2: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2 RAID: No RAID devices: /proc/mdstat, md_mod kernel module present Sensors: System Temperatures: cpu: 37.5C mobo: N/A Fan Speeds (in rpm): cpu: N/A Info: Processes: 239 Uptime: 3 min Memory: 782.8/7684.1MB Init: systemd runlevel: 5 Gcc sys: N/A Client: Shell (bash 4.4.121) inxi: 2.3.37 corrado@corrado-0926:~$ ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: lshw 02.18-0.1ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Oct 1 12:50:48 2017 InstallationDate: Installed on 2017-09-29 (2 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: lshw UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1720624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend
Additionally what about the newer 10XX mobile devices? (- I've none to try. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1805444 Title: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend Status in mutter package in Ubuntu: Fix Released Bug description: Wayland sessions don't work with the Nvidia driver in 18.04, even after enabling them via the kernel command line 'nvidia- drm.modeset=1'. [Original description] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due to following missing changes in mutter 3.28.3-2~ubuntu18.04.2 commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84 Author: Miguel A. Vico Date: Thu Jun 7 16:29:44 2018 -0700 renderer/native: Choose first EGL config for non-GBM backends Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only choose EGL configs that match the GBM_FORMAT_XRGB pixel format. However, there won't be any EGL config satisfying such criteria for non-GBM backends, such as EGLDevice. This change will let us choose the first EGL config for the EGLDevice backend, while still forcing GBM_FORMAT_XRGB configs for the GBM one. Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2 commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b Author: Jonas Ådahl Date: Tue Nov 14 16:08:52 2017 +0800 renderer/native: Also wrap flip closures for EGLStreams When using the EGLStream backend, the MetaRendererNative passed a GClosure to KMS when using EGLStreams, but KMS flip callback event handler in meta-gpu-kms.c expected a closure wrapped in a closure container, meaning it'd instead crash when using EGLStreams. Make the flip handler get what it expects also when using EGLStreams by wrapping the flip closure in the container before handing it over to EGL. https://bugzilla.gnome.org/show_bug.cgi?id=790316 apt-cache policy mutter mutter: Installed: 3.28.3-2~ubuntu18.04.2 Candidate: 3.28.3-2~ubuntu18.04.2 Version table: *** 3.28.3-2~ubuntu18.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1805444] Re: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend
In regard to caveats above: There is no mention of specific Nvidia series, is it presumed that XXXm devices should work now in 18.10 & 19.04? (- I've never seem any Nvidia m series work in wayland.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1805444 Title: [nvidia] Fail to launch gnome-shell (Wayland) on Ubuntu with EGLDevice backend Status in mutter package in Ubuntu: Fix Released Bug description: Wayland sessions don't work with the Nvidia driver in 18.04, even after enabling them via the kernel command line 'nvidia- drm.modeset=1'. [Original description] Fail to launch gnome-wayland-shell on Ubuntu-18.04 with EGLDevice backend due to following missing changes in mutter 3.28.3-2~ubuntu18.04.2 commit 1bf2eb95b502ed0419b0fe8979c022cacaf79e84 Author: Miguel A. Vico Date: Thu Jun 7 16:29:44 2018 -0700 renderer/native: Choose first EGL config for non-GBM backends Commit 712ec30cd9be1f180c3789e7e6a042c5f7b5781d added the logic to only choose EGL configs that match the GBM_FORMAT_XRGB pixel format. However, there won't be any EGL config satisfying such criteria for non-GBM backends, such as EGLDevice. This change will let us choose the first EGL config for the EGLDevice backend, while still forcing GBM_FORMAT_XRGB configs for the GBM one. Related to: https://gitlab.gnome.org/GNOME/mutter/issues/2 commit 8ee14a7cb7e8f072d2731d59c7dc735f83a9bb0b Author: Jonas Ådahl Date: Tue Nov 14 16:08:52 2017 +0800 renderer/native: Also wrap flip closures for EGLStreams When using the EGLStream backend, the MetaRendererNative passed a GClosure to KMS when using EGLStreams, but KMS flip callback event handler in meta-gpu-kms.c expected a closure wrapped in a closure container, meaning it'd instead crash when using EGLStreams. Make the flip handler get what it expects also when using EGLStreams by wrapping the flip closure in the container before handing it over to EGL. https://bugzilla.gnome.org/show_bug.cgi?id=790316 apt-cache policy mutter mutter: Installed: 3.28.3-2~ubuntu18.04.2 Candidate: 3.28.3-2~ubuntu18.04.2 Version table: *** 3.28.3-2~ubuntu18.04.2 500 500 http://ports.ubuntu.com/ubuntu-ports bionic-updates/main arm64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports bionic/main arm64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1805444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1811717] Re: Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop disappear
Testing the latest git of desktop icons (git-d1027f8 from 20190114) the issue seems resolved. When using the current package in disco saw the same as been reported, -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1811717 Title: Changing Dock icon size (Settings-Dock-Icon size) the icons on desktop disappear Status in gnome-shell-extension-desktop-icons package in Ubuntu: Confirmed Bug description: I have some icons on desktop (applications folders and files) Changing Dock Icon size (Settings-Dock-Icon size) the icons on desktop disappear, they reappear creating a file or a folder in the desktop or in /Home/Desktop sometimes they reappear also changing Icon size again. Problem happen both with x11 and wayland session. corrado@corrado-p6-dd-1227:~$ inxi -SCGx System: Host: corrado-p6-dd-1227 Kernel: 4.18.0-11-generic x86_64 bits: 64 compiler: gcc v: 8.2.0 Desktop: Gnome 3.30.2 Distro: Ubuntu 19.04 (Disco Dingo) CPU: Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31296 Speed: 800 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 Graphics: Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 Display: x11 server: X.Org 1.20.3 driver: i915 resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 4.5 Mesa 18.2.6 direct render: Yes corrado@corrado-p6-dd-1227:~$ corrado@corrado-p6-dd-1227:~$ apt policy nautilus nautilus: Installed: 1:3.30.4-1ubuntu1 Candidate: 1:3.30.4-1ubuntu1 Version table: *** 1:3.30.4-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 100 /var/lib/dpkg/status corrado@corrado-p6-dd-1227:~$ gnome-shell-extension-desktop-icons: Installed: 18.11~rc+git20181217-1 Candidate: 18.11~rc+git20181217-1 Version table: *** 18.11~rc+git20181217-1 500 500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu disco/main i386 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.30.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu18 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 14 20:10:16 2019 GsettingsChanges: b'org.gnome.nautilus.window-state' b'initial-size' b'(1252, 581)' b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" InstallationDate: Installed on 2018-12-27 (18 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181227) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1811717/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1809659] [NEW] Nautilus breadcrumbs aren't visible till hovered
Public bug reported: The breadcrumb is dark grey with no text visible until hovered over with default yaru theming ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: yaru-theme-gnome-shell 18.10.6 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 24 09:14:09 2018 Dependencies: InstallationDate: Installed on 2018-12-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181217) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: yaru-theme (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug disco ** Attachment added: "Screenshot from 2018-12-24 09-18-01.png" https://bugs.launchpad.net/bugs/1809659/+attachment/5224645/+files/Screenshot%20from%202018-12-24%2009-18-01.png ** Summary changed: - Nautilus breadcrumbs are visible till hovered + Nautilus breadcrumbs aren't visible till hovered -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to yaru-theme in Ubuntu. https://bugs.launchpad.net/bugs/1809659 Title: Nautilus breadcrumbs aren't visible till hovered Status in yaru-theme package in Ubuntu: New Bug description: The breadcrumb is dark grey with no text visible until hovered over with default yaru theming ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: yaru-theme-gnome-shell 18.10.6 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 24 09:14:09 2018 Dependencies: InstallationDate: Installed on 2018-12-24 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181217) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: yaru-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/yaru-theme/+bug/1809659/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1807761] Re: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi
It would appear the issue is that a gdebi instance opened from the context menu on a desktop item is unable to do any action on any .deb file located anywhere. In other words it's doomed to fail upon simply opening. Can be easily seen by opening gdebi-gtk as described but then switching to another .deb somewhere else from gdebi's open menu item. This will also fail. gdebi-gtk opened from app menu has no issues acting on a .deb from anywhere inc. the desktop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1807761 Title: Unable to install deb-file stored on Desktop (which is controlled by nautilus-desktop) with GDebi Status in gdebi package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu 18.04 LTS or Ubuntu 18.10 2. Download some deb-file to the desktop - for with help of terminal: cd ~/Desktop apt-get download meld 3. Install GDebi package installer with sudo apt install gdebi 4. Select deb-file on desktop, make right click on it, select *Open With Other Application* select *GDebi Package Installer*, click *Select*, in opened window select *Install Package* Expected results: * GDebi asks user (sudo-able) password and installs the package Actual results: * GDebi do not ask user for password and do not install the package Notes: * first seen on AskUbuntu ( https://askubuntu.com/q/1099387/66509 ) * you can view my screencast to get first person view :) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: nautilus 1:3.26.4-0ubuntu7 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 10 23:14:16 2018 GsettingsChanges: SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdebi/+bug/1807761/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1800359] [NEW] libosmesa6 is not installable in 18.04
Public bug reported: currently at version 18.0.0~rc5-1ubuntu1 but libglapi-mesa is at version 18.0.5-0ubuntu0~18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libosmesa6 (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Oct 28 10:55:42 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2018-10-13 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=e8def74e-6e50-4d6e-9adb-07d2b230cb55 ro quiet splash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1.1~ppa version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1800359 Title: libosmesa6 is not installable in 18.04 Status in mesa package in Ubuntu: New Bug description: currently at version 18.0.0~rc5-1ubuntu1 but libglapi-mesa is at version 18.0.5-0ubuntu0~18.04.1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libosmesa6 (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Oct 28 10:55:42 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2018-10-13 (14 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=e8def74e-6e50-4d6e-9adb-07d2b230cb55 ro quiet splash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias:
[Desktop-packages] [Bug 1794649] [NEW] Closing ubuntu-software on an app page then prevents returning to main (all) page
Public bug reported: Test Case: Open ubuntu-software, open page for any app. Close ubuntu-software from that page. Re-open ubuntu-software, it will open on the app page you closed on. Click the back button, nothing happens. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 26 23:49:40 2018 InstallationDate: Installed on 2018-08-24 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.0-0ubuntu1 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic ** Summary changed: - Closing ubuntu-software on an app page then prevents returnining to main (all) page + Closing ubuntu-software on an app page then prevents returning to main (all) page -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1794649 Title: Closing ubuntu-software on an app page then prevents returning to main (all) page Status in gnome-software package in Ubuntu: New Bug description: Test Case: Open ubuntu-software, open page for any app. Close ubuntu-software from that page. Re-open ubuntu-software, it will open on the app page you closed on. Click the back button, nothing happens. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: ubuntu-software 3.30.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7 Uname: Linux 4.18.0-8-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 26 23:49:40 2018 InstallationDate: Installed on 2018-08-24 (33 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-limba N/A gnome-software-plugin-snap3.30.0-0ubuntu1 PackageArchitecture: all SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1794649/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1672297] Re: gnome-shell uses lots of memory, and grows over time
@ Nick Timkovich
The 'fix released' for 18.04 (1.52.1-1ubuntu1) is to the extent as seen in
comment 78 which may not be as developed as the 'fix released' for 18.10 , i.e
comment 96
The bionic task for gjs as shown at top still says 'In progress' which *may*
mean there are further gjs patches under consideration for 18.04..
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1672297
Title:
gnome-shell uses lots of memory, and grows over time
Status in GNOME Shell:
Confirmed
Status in gjs package in Ubuntu:
Fix Released
Status in gjs source package in Bionic:
In Progress
Bug description:
Upstream:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/64
---
gnome-shell's RSS is growing by 1 MiB every few minutes, and is now at
almost 2 GiB.
user 3039 1.8 16.1 4302340 1968476 tty2 Sl+ Mar09 120:17
/usr/bin/gnome-shell
strace output is voluminous; here is a representative sample:
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\231\n\10\0\n\0
\0\0\0\0\0\0\0\0\0\0\0\0\0\1\0\0\0\0\0\0\0\0\0\0\0", 32}], 1) = 32
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0{\224\0\0\0\0H\0\0\0\0\23\266\32\0\0\0\0\201\242\204\0\0\0\0\0\261.\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\5\4\0a\2228\0y\3\5\0%\3\27\4\231\6\5\0\n\0
\0a\2228\0\0\0\0\0"..., 36}, {NULL, 0}, {"", 0}], 3) = 36
poll([{fd=5, events=POLLIN}], 1, -1)= 1 ([{fd=5, revents=POLLIN}])
recvmsg(5, {msg_name(0)=NULL,
msg_iov(1)=[{"\1\0}\224\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
4096}], msg_controllen=0, msg_flags=0}, 0) = 32
recvmsg(5, 0x7fff60efac90, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=5, events=POLLIN|POLLOUT}], 1, -1) = 1 ([{fd=5, revents=POLLOUT}])
writev(5, [{"\212\n\2\0a\2228\0", 8}, {NULL, 0}, {"", 0}], 3) = 8
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 0) = 0
(Timeout)
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
open("/proc/self/stat", O_RDONLY) = 36
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
fcntl(36, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE)
fstat(36, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
read(36, "3039 (gnome-shell) R 2930 2917 2"..., 4096) = 354
read(36, "", 3072) = 0
close(36) = 0
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, 0x7fff60efb000, 0) = -1 EAGAIN (Resource temporarily
unavailable)
poll([{fd=4, events=POLLIN}, {fd=5, events=POLLIN}, {fd=11, events=POLLIN},
{fd=12, events=POLLIN}, {fd=14, events=POLLIN}, {fd=16, events=POLLIN}, {fd=26,
events=POLLIN}, {fd=29, events=POLLIN}, {fd=32, events=POLLIN}, {fd=34,
events=POLLIN}, {fd=37, events=POLLIN}, {fd=38, events=POLLIN}, {fd=40,
events=POLLIN}, {fd=42, events=POLLIN}, {fd=43, events=POLLIN}], 15, 117885) =
1 ([{fd=4, revents=POLLIN}])
read(4, "\1\0\0\0\0\0\0\0", 16) = 8
recvmsg(5, 0x7fff60efb040, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(5, 0x7fff60efb020, 0) = -1 EAGAIN (Resource temporarily
unavailable)
recvmsg(12, {msg_name(0)=NULL,
msg_iov(1)=[{"[\2\327\0@\0i\0@\0(nu\22\n\0I\0\336\2\232\1\265\0038\2\362\2\355\1",
4096}], msg_controllen=0,
Re: [Desktop-packages] [Bug 927952] Re: When I press the Print Screen button, it will not appear in "Save Screenshot" window.
Just use ctrl+PrtSc to send to clipboard On Jun 10, 2018 10:04 PM, "Kris" wrote: Just recently upgraded to bionic, and after using it for a while I mostly got used to it, but the one feature that keeps bothering me painfully is the lack of the printscreen dialog. I understand the initiative to adopt gnome standards, but this is introducing a big inconvenience in comparison to how it was functional in the Unity desktop. It is not just about being able to save printscreens to an arbitrary location under an arbitrary name. It is even more importantly being able to copy a printscreen into a clipboard without saving it to a file on a disk. I used to be able to just copy a printscreen and Ctrl+V it into a IM window, a email client or any webapp. Now I have to take additional steps to open file manager, navigate to the Pictures folder, locate the one printscreen file I need among other ones, and drag it to where I need it, then, delete it. The functionality and user experience has decreased significantly for me, and on top of that I get constantly annoyed by it. I wish Canonical shipped the previous user experience with the new gnome-desktop based Ubuntu. Even as an opt-in! -- You received this bug notification because you are subscribed to a duplicate bug report (928364). https://bugs.launchpad.net/bugs/927952 Title: When I press the Print Screen button, it will not appear in "Save Screenshot" window. Status in Ayatana Design: Fix Released Status in Gnome Screenshot: Expired Status in gnome-screenshot package in Ubuntu: Fix Released Status in gnome-screenshot source package in Precise: Fix Released Status in gnome-screenshot package in Debian: Confirmed Bug description: When taking a screenshot with Print Screen or Alt+Print Screen a dialog box asking you what and where to save the file no longer appears. So while you hear a camera sound you have no other confirmation that a screenshot was really taken. Additionally, there is no way of knowing where the screenshot went. I'd imagine this will be particularly problematic for new users of Ubuntu. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-screenshot 3.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3 Uname: Linux 3.2.0-14-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 6 23:54:17 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1)SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to precise on 2012-01-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/927952/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screenshot in Ubuntu. https://bugs.launchpad.net/bugs/927952 Title: When I press the Print Screen button, it will not appear in "Save Screenshot" window. Status in Ayatana Design: Fix Released Status in Gnome Screenshot: Expired Status in gnome-screenshot package in Ubuntu: Fix Released Status in gnome-screenshot source package in Precise: Fix Released Status in gnome-screenshot package in Debian: Confirmed Bug description: When taking a screenshot with Print Screen or Alt+Print Screen a dialog box asking you what and where to save the file no longer appears. So while you hear a camera sound you have no other confirmation that a screenshot was really taken. Additionally, there is no way of knowing where the screenshot went. I'd imagine this will be particularly problematic for new users of Ubuntu. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: gnome-screenshot 3.3.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-14.23-generic 3.2.3 Uname: Linux 3.2.0-14-generic x86_64 ApportVersion: 1.91-0ubuntu1 Architecture: amd64 Date: Mon Feb 6 23:54:17 2012 InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1)SourcePackage: gnome-screenshot UpgradeStatus: Upgraded to precise on 2012-01-27 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/927952/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758689] Re: No microcode option present
So in 16.04 linux-image-generic (4.4.0.125.131) & linux-image-generic-hwe-16.04
(4.13.0.42.61) & linux-image-generic-hwe-16.04-edge (4.15.0.21.43 all now have
a dep on both intel & amd microcode packages.
Doesn't seem to have happened yet in 18.04, why not?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1758689
Title:
No microcode option present
Status in ubuntu-drivers-common package in Ubuntu:
Confirmed
Bug description:
Appears to have been removed based on
" - Remove the cpu-microcode.py detection plugin (LP: #1738259).
Kernel metapackages are going to have a hard dependency on the
{intel,amd64}-microcode packages to ensure that all bare-metal installs
benefit from microcode updates"
However that appears to have never occured in bionic for 4.15.x & to have
been reverted in all other linux-meta packages, ex. xenial -
* Miscellaneous upstream changes
- Revert "UBUNTU: Make kernel image packages depend on cpu microcode
updates"
-- Marcelo Henrique Cerri Fri, 12 Jan
2018 16:34:13 -0200
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-drivers-common 1:0.5
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: Unity:Unity7:ubuntu
Date: Sun Mar 25 11:36:27 2018
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1758689/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1761593] Re: Uninstall left nouveau blacklisted
As stated in duped bug removing nvidia drivers (nvidia-390 here) via software-properties only removes the driver meta package so actually nothing is removed. (- and of course /etc/modprobe.d/nvidia-graphics-drivers.conf will still be there .. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1761593 Title: Uninstall left nouveau blacklisted Status in nvidia-graphics-drivers-340 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-390 package in Ubuntu: Triaged Status in software-properties package in Ubuntu: Confirmed Bug description: Following a successful install and subsequent use of nvidia-340 - uninstallation of nvidia via Additional Drivers led to a reboot to a desktop at 640x480 px. Investigation found an nvidia created file left on the system blacklisting nouveau, deleted file and rebooted to normal desktop. Didn't think about ubuntu-reporting this - can try and replicate and apport-collect if it's of any use. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1761593/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728467] Re: All files on ntfs partitions are marked executable
Not sure what the heck you all are recently taking about.
Most linux users of a ntfs partition are using to store files for use on any Os
or store files without any permission nonsense.
Those that actually place .exe files & want to then execute them from an Ubuntu
session would likely be using something like wine.
In that case the .exe does not need to be "executable" to be run.
The prior settings for ntfs defaults was best for the vast majority of
users, period.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs partitions are marked executable
Status in ntfs-3g package in Ubuntu:
New
Status in udisks2 package in Ubuntu:
Invalid
Bug description:
This did not happen in 14.04 but somewhere since then udisks2 sets any & all
files on ntfs partitions as executable.
Additionally if file is copied over to user's ext4 partion the bit remains
set.
Can't see why this would be intentional??
In 14.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077",
"fmask=0177", NULL };
In 16.04, 17.04, 17.10,18.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udisks2 2.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 70-snap.core.rules
Date: Sun Oct 29 21:20:19 2017
InstallationDate: Installed on 2017-09-16 (43 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN44WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias:
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntfs-3g/+bug/1728467/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1704781] Re: With gdm3 a restart is needed when switching prime profiles
Last year this may have mattered. (17.10 Now in 18.04 a restart is required anyway so marking invalid. ** Changed in: nvidia-prime (Ubuntu) Status: Confirmed => Invalid ** Changed in: gdm3 (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1704781 Title: With gdm3 a restart is needed when switching prime profiles Status in gdm3 package in Ubuntu: Invalid Status in nvidia-prime package in Ubuntu: Invalid Bug description: Test case: Install nvidia drivers ,restart. Open nvidia-settings, switch prime profile. Will be prompted to log out/in, do so What happens: user goes into a log in loop To actually get back to the ubuntu-session one must restart. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: nvidia-prime 0.8.4 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 17 07:57:24 2017 InstallationDate: Installed on 2017-07-15 (1 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170708) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1704781/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
(- off topic slightly. It would be good it the gnome gitlab issue tracker could be added to launchpad as a valid 'location' to track upstream gnome bugs rather than the current of just bugzilla.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Fix Committed Bug description: Test Case = Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) Regression Potential This commit fixes the bug and was applied upstream. https://gitlab.gnome.org/GNOME/gnome-shell/commit/0327069e83b Other Info == https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1: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-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760444] Re: Snap core version 16-2.31.2 fails to open chromium window with nvidia drivers
Fixed with upgrade of snap core version. ** Changed in: snapd (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1760444 Title: Snap core version 16-2.31.2 fails to open chromium window with nvidia drivers Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: Fix Released Bug description: name: chromium summary: Chromium web browser, open-source version of Chrome publisher: canonical contact: https://forum.snapcraft.io/ license: unknown description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refreshed: 2018-03-29T11:56:58-04:00 installed: 65.0.3325.181 (270) 144MB - channels: stable:65.0.3325.181 (266) 138MB - candidate: 65.0.3325.181 (270) 144MB - beta: ↑ edge: ↑ Happens with all versions. Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416 Card-2: NVIDIA GK107M [GeForce GT 755M] driver: nvidia v: 390.42 bus ID: 01:00.0 chip ID: 10de:0fcd Display Server: x11 (X.Org 1.19.6) driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: GeForce GT 755M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.42 direct render: Yes doug@doug-Lenovo-IdeaPad-Y510P:~$ snap run chromium Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: Failed to load module "canberra-gtk-module" Gkr-Message: secret service operation failed: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.93" (uid=1000 pid=6866 comm="/snap/chromium/270/usr/lib/chromium-browser/chromi" label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus.Peer" member="Ping" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=5817 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined") ATTENTION: default value of option force_s3tc_enable overridden by environment. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast [7175:7175:0401/105124.319419:ERROR:gl_context_glx.cc(227)] Couldn't make context current with X drawable. [7175:7175:0401/105124.319444:ERROR:gpu_info_collector.cc(62)] gl::GLContext::MakeCurrent() failed Gkr-Message: secret service operation failed: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.93" (uid=1000 pid=6866 comm="/snap/chromium/270/usr/lib/chromium-browser/chromi" label="snap.chromium.chromium (enforce)") interface="org.freedesktop.Secret.Service" member="SearchItems" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=5817 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined") screenshot attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1760444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Invalid Status in gnome-shell package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 --- Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1: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-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
Fix in gnome-shell should be committed shortly, as seen here in merge request https://gitlab.gnome.org/GNOME/gnome-shell/merge_requests/85 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 --- Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1: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-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
** Changed in: gnome-shell (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Fix Committed Bug description: https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 --- Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1: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-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
Started report here https://gitlab.gnome.org/GNOME/gnome-shell/issues/221 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 --- Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1: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-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
I have to go out, guess could file upstream bug tonight if no one does.. Seems best place is gitlab? https://gitlab.gnome.org/GNOME/gnome-shell/issues The commit allowing this seems to be, https://github.com/GNOME/gnome-shell/commit/cb4252e888c651c5a11fa0cb4c330e9351d61f1b (- confirmed here by reverting that commit to latest ubuntu gnome-shell source -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 --- Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1: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-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
Ok but then you'd need to add/address gnome-software, software- properties-gtk, synaptic, gnome-disk-utility, ect. as any & all of them will cause/experience the same issue, sans a segfault. As soon as 1 app that calls a pkexec auth dialog is canceled then no other app can use pkexec auth until gnome-shell is restarted. As mentioned this does not happen in prior version of gnome-shell. None of the other apps 'crash', they can however get an unresponsive window or in the case of gnome-software (ubuntu-software) it'll just endlessly show installing. There's half a dozen test cases to see this that don't involve g-c-c at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 --- Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1: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-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765353] Re: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete()
Not sure why gnome-shell was removed as clearly that's were the issue is. G-c-c may be the only apt actually crashing but this affects any apt that calls a pkexec Auth dialog. Easy examples are software & updates > change something, cancel the auth dialog or synaptic > cancel on the auth. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV in acquire_cb() from g_simple_async_result_complete() Status in gnome-control-center package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/55b54d35f8bfd6319edbf1e24d53587020b16273 --- Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1: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-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1765353] Re: gnome-control-center crashed with SIGSEGV
To note; this behavior affects all apps that call pkexec, if the auth dialogue is cancelled then issue occurs. After occurring pkexec cannot be used until gnome-shell is restarted. Does not occur with gnome-shell (3.28.0-0ubuntu5) ** Also affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1765353 Title: gnome-control-center crashed with SIGSEGV Status in gnome-control-center package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: New Bug description: Being discussed on the forums - https://ubuntuforums.org/showthread.php?t=2389622 Open "Settings" and navigate to "Users". Click on "Unlock" and cancel dialog without inputting a password. "Unlock" becomes unresponsive and Settings will eventually crash. If started from a terminal I see the following output: (gnome-control-center:24951): GLib-GIO-CRITICAL **: 10:26:38.402: g_permission_acquire_finish: assertion 'G_IS_PERMISSION (permission)' failed fish: “gnome-control-center” terminated by signal SIGSEGV (Address boundary error) ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1: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-0ubuntu5 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 19 10:25:11 2018 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2017-11-07 (163 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcCmdline: gnome-control-center --overview ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f7e2de3b845:pushq 0x8(%rax) PC (0x7f7e2de3b845) ok source "0x8(%rax)" (0x0008) not located in a known VMA region (needed readable region)! SegvReason: reading NULL VMA Signal: 11 SourcePackage: gnome-control-center StacktraceTop: () at /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 g_simple_async_result_complete () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 () at /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 Title: gnome-control-center crashed with SIGSEGV UpgradeStatus: Upgraded to bionic on 2018-02-21 (56 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1765353/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1481049] Re: list view defines .iso as unknown types
If Ubuntu wanted to add this to 3.26 it's rather trivial ** Patch added: "details_full.patch" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1481049/+attachment/5111429/+files/details_full.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1481049 Title: list view defines .iso as unknown types Status in nautilus package in Ubuntu: Confirmed Bug description: the file manager does not have iin order "type" the .iso file, as shown in the picture you see that I enclose, the files with the extension .iso not respect the line and are scattered around the window To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1481049/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760444] Re: Snap core version 16-2.31.2 fails to open window with nvidia drivers
ok, setting bug to snapd, fix is update current snap core to beta or better. ** Also affects: snapd (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Snap core version 16-2.31.2 fails to open window with nvidia drivers + Snap core version 16-2.31.2 fails to open chromium window with nvidia drivers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1760444 Title: Snap core version 16-2.31.2 fails to open chromium window with nvidia drivers Status in chromium-browser package in Ubuntu: Invalid Status in snapd package in Ubuntu: New Bug description: name: chromium summary: Chromium web browser, open-source version of Chrome publisher: canonical contact: https://forum.snapcraft.io/ license: unknown description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refreshed: 2018-03-29T11:56:58-04:00 installed: 65.0.3325.181 (270) 144MB - channels: stable:65.0.3325.181 (266) 138MB - candidate: 65.0.3325.181 (270) 144MB - beta: ↑ edge: ↑ Happens with all versions. Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416 Card-2: NVIDIA GK107M [GeForce GT 755M] driver: nvidia v: 390.42 bus ID: 01:00.0 chip ID: 10de:0fcd Display Server: x11 (X.Org 1.19.6) driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: GeForce GT 755M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.42 direct render: Yes doug@doug-Lenovo-IdeaPad-Y510P:~$ snap run chromium Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: Failed to load module "canberra-gtk-module" Gkr-Message: secret service operation failed: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.93" (uid=1000 pid=6866 comm="/snap/chromium/270/usr/lib/chromium-browser/chromi" label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus.Peer" member="Ping" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=5817 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined") ATTENTION: default value of option force_s3tc_enable overridden by environment. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast [7175:7175:0401/105124.319419:ERROR:gl_context_glx.cc(227)] Couldn't make context current with X drawable. [7175:7175:0401/105124.319444:ERROR:gpu_info_collector.cc(62)] gl::GLContext::MakeCurrent() failed Gkr-Message: secret service operation failed: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.93" (uid=1000 pid=6866 comm="/snap/chromium/270/usr/lib/chromium-browser/chromi" label="snap.chromium.chromium (enforce)") interface="org.freedesktop.Secret.Service" member="SearchItems" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=5817 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined") screenshot attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1760444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760444] Re: Snap version fails to open window with nvidia drivers
Yes, this is on 18.04. The beta core, (16-2.32.2) does fix the problem. ** Tags added: bionic ** Changed in: chromium-browser (Ubuntu) Status: Incomplete => New ** Summary changed: - Snap version fails to open window with nvidia drivers + Snap core version 16-2.31.2 fails to open window with nvidia drivers ** Summary changed: - Snap core version 16-2.31.2 fails to open window with nvidia drivers + Snap fails to open window with nvidia drivers ** Summary changed: - Snap fails to open window with nvidia drivers + Snap core version 16-2.31.2 fails to open window with nvidia drivers -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1760444 Title: Snap core version 16-2.31.2 fails to open window with nvidia drivers Status in chromium-browser package in Ubuntu: New Bug description: name: chromium summary: Chromium web browser, open-source version of Chrome publisher: canonical contact: https://forum.snapcraft.io/ license: unknown description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refreshed: 2018-03-29T11:56:58-04:00 installed: 65.0.3325.181 (270) 144MB - channels: stable:65.0.3325.181 (266) 138MB - candidate: 65.0.3325.181 (270) 144MB - beta: ↑ edge: ↑ Happens with all versions. Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416 Card-2: NVIDIA GK107M [GeForce GT 755M] driver: nvidia v: 390.42 bus ID: 01:00.0 chip ID: 10de:0fcd Display Server: x11 (X.Org 1.19.6) driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: GeForce GT 755M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.42 direct render: Yes doug@doug-Lenovo-IdeaPad-Y510P:~$ snap run chromium Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: Failed to load module "canberra-gtk-module" Gkr-Message: secret service operation failed: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.93" (uid=1000 pid=6866 comm="/snap/chromium/270/usr/lib/chromium-browser/chromi" label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus.Peer" member="Ping" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=5817 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined") ATTENTION: default value of option force_s3tc_enable overridden by environment. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast [7175:7175:0401/105124.319419:ERROR:gl_context_glx.cc(227)] Couldn't make context current with X drawable. [7175:7175:0401/105124.319444:ERROR:gpu_info_collector.cc(62)] gl::GLContext::MakeCurrent() failed Gkr-Message: secret service operation failed: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.93" (uid=1000 pid=6866 comm="/snap/chromium/270/usr/lib/chromium-browser/chromi" label="snap.chromium.chromium (enforce)") interface="org.freedesktop.Secret.Service" member="SearchItems" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=5817 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined") screenshot attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1760444/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1760444] [NEW] Snap version fails to open window with nvidia drivers
Public bug reported: name: chromium summary: Chromium web browser, open-source version of Chrome publisher: canonical contact: https://forum.snapcraft.io/ license: unknown description: | An open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. commands: - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refreshed: 2018-03-29T11:56:58-04:00 installed: 65.0.3325.181 (270) 144MB - channels: stable:65.0.3325.181 (266) 138MB - candidate: 65.0.3325.181 (270) 144MB - beta: ↑ edge: ↑ Happens with all versions. Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:0416 Card-2: NVIDIA GK107M [GeForce GT 755M] driver: nvidia v: 390.42 bus ID: 01:00.0 chip ID: 10de:0fcd Display Server: x11 (X.Org 1.19.6) driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: GeForce GT 755M/PCIe/SSE2 v: 4.6.0 NVIDIA 390.42 direct render: Yes doug@doug-Lenovo-IdeaPad-Y510P:~$ snap run chromium Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: Failed to load module "canberra-gtk-module" Gkr-Message: secret service operation failed: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.93" (uid=1000 pid=6866 comm="/snap/chromium/270/usr/lib/chromium-browser/chromi" label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus.Peer" member="Ping" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=5817 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined") ATTENTION: default value of option force_s3tc_enable overridden by environment. libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast [7175:7175:0401/105124.319419:ERROR:gl_context_glx.cc(227)] Couldn't make context current with X drawable. [7175:7175:0401/105124.319444:ERROR:gpu_info_collector.cc(62)] gl::GLContext::MakeCurrent() failed Gkr-Message: secret service operation failed: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.93" (uid=1000 pid=6866 comm="/snap/chromium/270/usr/lib/chromium-browser/chromi" label="snap.chromium.chromium (enforce)") interface="org.freedesktop.Secret.Service" member="SearchItems" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=5817 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined") screenshot attached ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: snap ** Attachment added: "Screenshot from 2018-04-01 10-52-10.png" https://bugs.launchpad.net/bugs/1760444/+attachment/5097987/+files/Screenshot%20from%202018-04-01%2010-52-10.png ** Tags added: snap ** Description changed: name: chromium summary: Chromium web browser, open-source version of Chrome publisher: canonical contact: https://forum.snapcraft.io/ license: unknown description: | - An open-source browser project that aims to build a safer, faster, and more - stable way for all Internet users to experience the web. + An open-source browser project that aims to build a safer, faster, and more + stable way for all Internet users to experience the web. commands: - - chromium + - chromium snap-id: XKEcBqPM06H1Z7zGOdG5fbICuf8NWK5R tracking: beta refreshed: 2018-03-29T11:56:58-04:00 installed: 65.0.3325.181 (270) 144MB - - channels: - stable:65.0.3325.181 (266) 138MB - - candidate: 65.0.3325.181 (270) 144MB - - beta: ↑ - edge: ↑ + channels: + stable:65.0.3325.181 (266) 138MB - + candidate: 65.0.3325.181 (270) 144MB - + beta: ↑ + edge: ↑ - Happens with all version. + Happens with all versions. doug@doug-Lenovo-IdeaPad-Y510P:~$ snap run chromium Gtk-Message: Failed to load module "canberra-gtk-module" Gtk-Message: Failed to load module "canberra-gtk-module" Gkr-Message: secret service operation failed: An AppArmor policy prevents this sender from sending this message to this recipient; type="method_call", sender=":1.93" (uid=1000 pid=6866 comm="/snap/chromium/270/usr/lib/chromium-browser/chromi" label="snap.chromium.chromium (enforce)") interface="org.freedesktop.DBus.Peer" member="Ping" error name="(unset)" requested_reply="0" destination="org.freedesktop.secrets" (uid=1000 pid=5817 comm="/usr/bin/gnome-keyring-daemon --daemonize --login " label="unconfined") ATTENTION: default value of option force_s3tc_enable overridden by environment. libGL error: No matching fbConfigs or visuals found libGL error: failed to load
[Desktop-packages] [Bug 1758689] [NEW] No microcode option present
Public bug reported:
Appears to have been removed based on
" - Remove the cpu-microcode.py detection plugin (LP: #1738259).
Kernel metapackages are going to have a hard dependency on the
{intel,amd64}-microcode packages to ensure that all bare-metal installs
benefit from microcode updates"
However that appears to have never occured in bionic for 4.15.x & to have been
reverted in all other linux-meta packages, ex. xenial -
* Miscellaneous upstream changes
- Revert "UBUNTU: Make kernel image packages depend on cpu microcode
updates"
-- Marcelo Henrique Cerri Fri, 12 Jan
2018 16:34:13 -0200
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-drivers-common 1:0.5
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: Unity:Unity7:ubuntu
Date: Sun Mar 25 11:36:27 2018
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: ubuntu-drivers-common (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1758689
Title:
No microcode option present
Status in ubuntu-drivers-common package in Ubuntu:
New
Bug description:
Appears to have been removed based on
" - Remove the cpu-microcode.py detection plugin (LP: #1738259).
Kernel metapackages are going to have a hard dependency on the
{intel,amd64}-microcode packages to ensure that all bare-metal installs
benefit from microcode updates"
However that appears to have never occured in bionic for 4.15.x & to have
been reverted in all other linux-meta packages, ex. xenial -
* Miscellaneous upstream changes
- Revert "UBUNTU: Make kernel image packages depend on cpu microcode
updates"
-- Marcelo Henrique Cerri Fri, 12 Jan
2018 16:34:13 -0200
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-drivers-common 1:0.5
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: Unity:Unity7:ubuntu
Date: Sun Mar 25 11:36:27 2018
SourcePackage: ubuntu-drivers-common
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1758689/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758214] Re: The prime-select window becomes unresponsive during switch process
Example of unresponsive window ** Attachment added: "Screenshot from 2018-03-22 21-31-00.png" https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1758214/+attachment/5087667/+files/Screenshot%20from%202018-03-22%2021-31-00.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1758214 Title: The prime-select window becomes unresponsive during switch process Status in nvidia-prime package in Ubuntu: New Bug description: When using the prime profile window to switch profiles the window becomes unresponsive during that process. This may take 10 -15 seconds or so to complete. If the user wonders what's going on & happens to click on the launcher icon a pop up appears stating window is unresponsive & offers to force quit it.. Doing so may leave the user's install in an inconsistent state & unable to subsequently boot up. An example in screen where profile was switched to intel but prime-profile quit before the nvidia-blacklist.conf was created. In this case prime-select intel won;t work & prime-select nvividia won't work either. Only way out is to either remove nvidia* or put a blacklist file in /etc/modeprobe.d/ During this new, extended switching process the user should be given some indication the process is ongoing.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.6 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: Unity:Unity7:ubuntu Date: Thu Mar 22 21:36:27 2018 Dependencies: PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1758214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1758214] [NEW] The prime-select window becomes unresponsive during switch process
Public bug reported: When using the prime profile window to switch profiles the window becomes unresponsive during that process. This may take 10 -15 seconds or so to complete. If the user wonders what's going on & happens to click on the launcher icon a pop up appears stating window is unresponsive & offers to force quit it.. Doing so may leave the user's install in an inconsistent state & unable to subsequently boot up. An example in screen where profile was switched to intel but prime-profile quit before the nvidia-blacklist.conf was created. In this case prime-select intel won;t work & prime-select nvividia won't work either. Only way out is to either remove nvidia* or put a blacklist file in /etc/modeprobe.d/ During this new, extended switching process the user should be given some indication the process is ongoing.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.6 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: Unity:Unity7:ubuntu Date: Thu Mar 22 21:36:27 2018 Dependencies: PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-prime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Screenshot from 2018-03-22 21-15-01.png" https://bugs.launchpad.net/bugs/1758214/+attachment/5087663/+files/Screenshot%20from%202018-03-22%2021-15-01.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1758214 Title: The prime-select window becomes unresponsive during switch process Status in nvidia-prime package in Ubuntu: New Bug description: When using the prime profile window to switch profiles the window becomes unresponsive during that process. This may take 10 -15 seconds or so to complete. If the user wonders what's going on & happens to click on the launcher icon a pop up appears stating window is unresponsive & offers to force quit it.. Doing so may leave the user's install in an inconsistent state & unable to subsequently boot up. An example in screen where profile was switched to intel but prime-profile quit before the nvidia-blacklist.conf was created. In this case prime-select intel won;t work & prime-select nvividia won't work either. Only way out is to either remove nvidia* or put a blacklist file in /etc/modeprobe.d/ During this new, extended switching process the user should be given some indication the process is ongoing.. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nvidia-prime 0.8.6 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: Unity:Unity7:ubuntu Date: Thu Mar 22 21:36:27 2018 Dependencies: PackageArchitecture: all SourcePackage: nvidia-prime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1758214/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1757180] Re: nvidia-prime can't switch off the discrete GPU
Re: nvidia-setting previously with alternatives lightdm could affect switch on a og out/in, however gdm3 needed a reboot. The message was never changed to reflect this, now that apparently a reboot is required no matter what dm it would be a good time to edit it. Old bug - https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1704781 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1757180 Title: nvidia-prime can't switch off the discrete GPU Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in ubuntu-drivers-common package in Ubuntu: In Progress Bug description: nvidia-prime used to be able to switch off and on NVIDIA dGPU. Now, a change in the nvidia packaging, and a change of behaviour in logind, broke this feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1757180/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***
Fixed with latest libcdio 1.0.0-2ubuntu1 ** Changed in: libcdio (Ubuntu) Status: Confirmed => Fix Released ** Changed in: gvfs (Ubuntu) Status: Confirmed => Invalid ** Changed in: audacious (Ubuntu) Status: Confirmed => Invalid ** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid ** Changed in: rhythmbox (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1740644 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** Status in audacious package in Ubuntu: Invalid Status in gvfs package in Ubuntu: Invalid Status in libcdio package in Ubuntu: Fix Released Status in nautilus package in Ubuntu: Invalid Status in rhythmbox package in Ubuntu: Invalid Bug description: While trying to play an audio cd, likely a gvfs or libcdio17 issue ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: audacious 3.9-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 21:02:57 2017 ExecutablePath: /usr/bin/audacious InstallationDate: Installed on 2017-12-17 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126) ProcCmdline: audacious ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: audacious StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7eff83be4870 "double free or corruption (out)", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7eff83e16c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1740644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1756380] Re: vaapi VP9 hardware decoding not working anymore in bionic
18.04 should really get the new driver, whether it's easier to do before or after release I don't know but it should be done. For some reason Debian hasn't added it yet but that shouldn't stop Ubuntu from doing so. In addition to bug symptoms there are other advantages to going to 2.1. For example there is a new interface for EGL interop, vaAcquireSurfaceHandle() in libva 2.1 but you need the 2.1 driver to implement. So while the 2.1.x driver will certainly be available via ppa's before too long Ubuntu should plan on providing in 18.04 as best achieved. ** Changed in: libva (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libva in Ubuntu. https://bugs.launchpad.net/bugs/1756380 Title: vaapi VP9 hardware decoding not working anymore in bionic Status in intel-vaapi-driver package in Ubuntu: Confirmed Status in libva package in Ubuntu: Invalid Bug description: Hardware: Dell XPS13 9365, i7-7Y75 System: Ubuntu Bionic Beaver (development branch) vainfo output on bionic is: libva info: VA-API version 1.1.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.1 (libva 2.1.0) vainfo: Driver version: Intel i965 driver for Intel(R) Kaby Lake - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointEncSliceLP VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264Main : VAEntrypointEncSliceLP VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264High : VAEntrypointEncSliceLP VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD VAProfileJPEGBaseline : VAEntrypointEncPicture VAProfileVP8Version0_3 : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointVLD VAProfileHEVCMain : VAEntrypointEncSlice VAProfileHEVCMain10 : VAEntrypointVLD VAProfileHEVCMain10 : VAEntrypointEncSlice As you can see, VP9 entrypoints are missing. vainfo output on 17.10 was: libva info: VA-API version 0.40.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_0_40 libva info: va_openDriver() returns 0 vainfo: VA-API version: 0.40 (libva ) vainfo: Driver version: Intel i965 driver for Intel(R) Kabylake - 1.8.3 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple:VAEntrypointVLD VAProfileMPEG2Simple:VAEntrypointEncSlice VAProfileMPEG2Main :VAEntrypointVLD VAProfileMPEG2Main :VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointVLD VAProfileH264ConstrainedBaseline:VAEntrypointEncSlice VAProfileH264ConstrainedBaseline:VAEntrypointEncSliceLP VAProfileH264Main :VAEntrypointVLD VAProfileH264Main :VAEntrypointEncSlice VAProfileH264Main :VAEntrypointEncSliceLP VAProfileH264High :VAEntrypointVLD VAProfileH264High :VAEntrypointEncSlice VAProfileH264High :VAEntrypointEncSliceLP VAProfileH264MultiviewHigh :VAEntrypointVLD VAProfileH264MultiviewHigh :VAEntrypointEncSlice VAProfileH264StereoHigh :VAEntrypointVLD VAProfileH264StereoHigh :VAEntrypointEncSlice
[Desktop-packages] [Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2
What i should of said is a new package for cd-paranoia, can't see ubuntu doing that for 18.04.. ** Attachment removed: "cd-paranoia.install" https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1750264/+attachment/5074358/+files/cd-paranoia.install -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1750264 Title: program 'cd-paranoia' is missing from package in 1.0.0-2 Status in libcdio package in Ubuntu: Invalid Status in libcdio-paranoia package in Ubuntu: Confirmed Bug description: apt show libcdio-utils: Description: sample applications based on the CDIO libraries This package contains a collection of small libcdio-based tools: * cd-drive show CD-ROM drive characteristics * cd-info show information about a CD or CD-image * cd-paranoia an audio CD ripper * cd-read read information from a CD or CD-image * cdda-player a simple curses-based audio CD player * iso-info show information about an ISO 9660 image * iso-read read portions of an ISO 9660 image * mmc-tool issue low-level commands to a CD drive cd-paranoia is missing from package. This breaks abcde 'optional' functionality which is in fact the most common used, since the original cdparanoia (separate program) is abandoned since 10 years. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 libcdio-utils: Installiert: 1.0.0-2 Installationskandidat: 1.0.0-2 Versionstabelle: *** 1.0.0-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcdio-utils 1.0.0-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Feb 18 18:18:55 2018 ProcEnviron: TERM=qterminal PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libcdio UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1750264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2
looking at deb multimedia there they decided to create a new file ** Attachment added: "cd-paranoia.install" https://bugs.launchpad.net/ubuntu/+source/libcdio-paranoia/+bug/1750264/+attachment/5074358/+files/cd-paranoia.install -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1750264 Title: program 'cd-paranoia' is missing from package in 1.0.0-2 Status in libcdio package in Ubuntu: Invalid Status in libcdio-paranoia package in Ubuntu: Confirmed Bug description: apt show libcdio-utils: Description: sample applications based on the CDIO libraries This package contains a collection of small libcdio-based tools: * cd-drive show CD-ROM drive characteristics * cd-info show information about a CD or CD-image * cd-paranoia an audio CD ripper * cd-read read information from a CD or CD-image * cdda-player a simple curses-based audio CD player * iso-info show information about an ISO 9660 image * iso-read read portions of an ISO 9660 image * mmc-tool issue low-level commands to a CD drive cd-paranoia is missing from package. This breaks abcde 'optional' functionality which is in fact the most common used, since the original cdparanoia (separate program) is abandoned since 10 years. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 libcdio-utils: Installiert: 1.0.0-2 Installationskandidat: 1.0.0-2 Versionstabelle: *** 1.0.0-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcdio-utils 1.0.0-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Feb 18 18:18:55 2018 ProcEnviron: TERM=qterminal PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libcdio UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1750264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2
Actually quite simple, no one set the binary to be installed in libcdio-paranoia2.install file i.e. usr/lib/*/libcdio_paranoia.so.* usr/bin/* ** Also affects: libcdio-paranoia (Ubuntu) Importance: Undecided Status: New ** Changed in: libcdio-paranoia (Ubuntu) Status: New => Confirmed ** Changed in: libcdio (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1750264 Title: program 'cd-paranoia' is missing from package in 1.0.0-2 Status in libcdio package in Ubuntu: Invalid Status in libcdio-paranoia package in Ubuntu: Confirmed Bug description: apt show libcdio-utils: Description: sample applications based on the CDIO libraries This package contains a collection of small libcdio-based tools: * cd-drive show CD-ROM drive characteristics * cd-info show information about a CD or CD-image * cd-paranoia an audio CD ripper * cd-read read information from a CD or CD-image * cdda-player a simple curses-based audio CD player * iso-info show information about an ISO 9660 image * iso-read read portions of an ISO 9660 image * mmc-tool issue low-level commands to a CD drive cd-paranoia is missing from package. This breaks abcde 'optional' functionality which is in fact the most common used, since the original cdparanoia (separate program) is abandoned since 10 years. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 libcdio-utils: Installiert: 1.0.0-2 Installationskandidat: 1.0.0-2 Versionstabelle: *** 1.0.0-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcdio-utils 1.0.0-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Feb 18 18:18:55 2018 ProcEnviron: TERM=qterminal PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libcdio UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1750264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2
Actually quite simple, no one set the binary to be installed in libcdio-paranoia2.install file i.e. usr/lib/*/libcdio_paranoia.so.* usr/bin/* -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1750264 Title: program 'cd-paranoia' is missing from package in 1.0.0-2 Status in libcdio package in Ubuntu: Invalid Status in libcdio-paranoia package in Ubuntu: Confirmed Bug description: apt show libcdio-utils: Description: sample applications based on the CDIO libraries This package contains a collection of small libcdio-based tools: * cd-drive show CD-ROM drive characteristics * cd-info show information about a CD or CD-image * cd-paranoia an audio CD ripper * cd-read read information from a CD or CD-image * cdda-player a simple curses-based audio CD player * iso-info show information about an ISO 9660 image * iso-read read portions of an ISO 9660 image * mmc-tool issue low-level commands to a CD drive cd-paranoia is missing from package. This breaks abcde 'optional' functionality which is in fact the most common used, since the original cdparanoia (separate program) is abandoned since 10 years. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 libcdio-utils: Installiert: 1.0.0-2 Installationskandidat: 1.0.0-2 Versionstabelle: *** 1.0.0-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcdio-utils 1.0.0-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Feb 18 18:18:55 2018 ProcEnviron: TERM=qterminal PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libcdio UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1750264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2
so libcdio17 is broken on audio cd's (- https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1740644 And now the cd-paranoia binary is missing. What's going on?? ** Changed in: libcdio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1750264 Title: program 'cd-paranoia' is missing from package in 1.0.0-2 Status in libcdio package in Ubuntu: Confirmed Bug description: apt show libcdio-utils: Description: sample applications based on the CDIO libraries This package contains a collection of small libcdio-based tools: * cd-drive show CD-ROM drive characteristics * cd-info show information about a CD or CD-image * cd-paranoia an audio CD ripper * cd-read read information from a CD or CD-image * cdda-player a simple curses-based audio CD player * iso-info show information about an ISO 9660 image * iso-read read portions of an ISO 9660 image * mmc-tool issue low-level commands to a CD drive cd-paranoia is missing from package. This breaks abcde 'optional' functionality which is in fact the most common used, since the original cdparanoia (separate program) is abandoned since 10 years. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 libcdio-utils: Installiert: 1.0.0-2 Installationskandidat: 1.0.0-2 Versionstabelle: *** 1.0.0-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcdio-utils 1.0.0-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Feb 18 18:18:55 2018 ProcEnviron: TERM=qterminal PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libcdio UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1750264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1750264] Re: program 'cd-paranoia' is missing from package in 1.0.0-2
Well it appears it's been moved out of libcdio & the binary is no longer built https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888053 ** Bug watch added: Debian Bug tracker #888053 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888053 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libcdio in Ubuntu. https://bugs.launchpad.net/bugs/1750264 Title: program 'cd-paranoia' is missing from package in 1.0.0-2 Status in libcdio package in Ubuntu: Confirmed Bug description: apt show libcdio-utils: Description: sample applications based on the CDIO libraries This package contains a collection of small libcdio-based tools: * cd-drive show CD-ROM drive characteristics * cd-info show information about a CD or CD-image * cd-paranoia an audio CD ripper * cd-read read information from a CD or CD-image * cdda-player a simple curses-based audio CD player * iso-info show information about an ISO 9660 image * iso-read read portions of an ISO 9660 image * mmc-tool issue low-level commands to a CD drive cd-paranoia is missing from package. This breaks abcde 'optional' functionality which is in fact the most common used, since the original cdparanoia (separate program) is abandoned since 10 years. Description:Ubuntu Bionic Beaver (development branch) Release:18.04 libcdio-utils: Installiert: 1.0.0-2 Installationskandidat: 1.0.0-2 Versionstabelle: *** 1.0.0-2 500 500 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libcdio-utils 1.0.0-2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXQt Date: Sun Feb 18 18:18:55 2018 ProcEnviron: TERM=qterminal PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: libcdio UpgradeStatus: Upgraded to bionic on 2017-06-03 (260 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1750264/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
On 03/05/2018 09:02 PM, Daniel van Vugt wrote: > Doug, > > Ideally it will be automatically installed, or at least gets installed > with ubuntu-restricted-addons. See: > https://wiki.ubuntu.com/IntelQuickSyncVideo > Good to know about the add-ons package, been quite awhile here that I've used it. Generally on new install I'm just trying to play media & looking to see if the gst-packagekit > ubuntu-software reacts properly, ect. (- which it's doing a decent job atm, always some room for improvement.. I'd think many users also follow that path, i.e add or access media then follow the pop up if support isn't already available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: New Status in Mutter: Fix Released Status in Totem: Expired Status in VLC media player: New Status in chromium-browser package in Ubuntu: Confirmed Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Committed Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in libva package in Ubuntu: Triaged Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Status in steam package in Ubuntu: Confirmed Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1698287] Re: VA-API fails to initialize in a Gnome Shell Wayland session
This seems fixed as of today's updates but does beg the question of how would most users even know to install the gstreamer1.0-vaapi package? It doesn't show up here in ubuntu software no matter what I search.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gst-plugins-base1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698287 Title: VA-API fails to initialize in a Gnome Shell Wayland session Status in Libva: New Status in Mutter: Fix Released Status in Totem: Expired Status in VLC media player: New Status in chromium-browser package in Ubuntu: Confirmed Status in gst-plugins-bad1.0 package in Ubuntu: Fix Released Status in gst-plugins-base1.0 package in Ubuntu: Fix Committed Status in gstreamer-vaapi package in Ubuntu: Won't Fix Status in libva package in Ubuntu: Triaged Status in mpv package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Status in steam package in Ubuntu: Confirmed Bug description: The Intel i965 VA-API driver works well in Xorg sessions (Unity7 and Gnome Shell). But it refuses to load when in a Wayland session: $ totem bbb_sunflower_1080p_60fps_normal.mp4 libva error: va_getDriverName() failed with unknown libva error,driver_name=(null) $ env LIBVA_DRIVER_NAME=i965 totem bbb_sunflower_1080p_60fps_normal.mp4 totem: intel_driver.c:112: intel_driver_init: Assertion `VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI1) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_DRI2) || VA_CHECK_DRM_AUTH_TYPE(ctx, VA_DRM_AUTH_CUSTOM)' failed. Aborted (core dumped) $ gst-play-1.0 bbb_sunflower_1080p_60fps_normal.mp4 Press 'k' to see a list of keyboard shortcuts. Now playing /home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 Redistribute latency... Redistribute latency... ERROR Internal error: could not render surface for file:///home/dan/Videos/bbb_sunflower_1080p_60fps_normal.mp4 ERROR debug information: ../../../gst/vaapi/gstvaapisink.c(1482): gst_vaapisink_show_frame_unlocked (): /GstPlayBin:playbin/GstPlaySink:playsink/GstBin:vbin/GstVaapiSink:vaapisink0 WORKAROUNDS: * Use weston instead of gnome-shell; or * $ env -uDISPLAY totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland totem ... # but creates corruption -> bug 1701463 * $ env GST_GL_WINDOW=wayland gst-play-1.0 --videosink glimagesink ... * $ env -uDISPLAY mpv --hwdec --opengl-backend=wayland ... ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: i965-va-driver 1.8.1-1 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Fri Jun 16 13:40:38 2017 InstallationDate: Installed on 2017-05-03 (44 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: intel-vaapi-driver UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libva/+bug/1698287/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728467] Re: All files on ntfs partitions are marked executable
** Tags removed: zesty
** Tags added: bionic
** Tags removed: bb-incoming
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs partitions are marked executable
Status in udisks2 package in Ubuntu:
Confirmed
Bug description:
This did not happen in 14.04 but somewhere since then udisks2 sets any & all
files on ntfs partitions as executable.
Additionally if file is copied over to user's ext4 partion the bit remains
set.
Can't see why this would be intentional??
In 14.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077",
"fmask=0177", NULL };
In 16.04, 17.04, 17.10,18.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udisks2 2.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 70-snap.core.rules
Date: Sun Oct 29 21:20:19 2017
InstallationDate: Installed on 2017-09-16 (43 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN44WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias:
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1728467/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***
** Patch added: "0001-Remove-duplicate-free.patch" https://bugs.launchpad.net/ubuntu/+source/libcdio/+bug/1740644/+attachment/5056951/+files/0001-Remove-duplicate-free.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1740644 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** Status in audacious package in Ubuntu: New Status in gvfs package in Ubuntu: New Status in libcdio package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: New Status in rhythmbox package in Ubuntu: New Bug description: While trying to play an audio cd, likely a gvfs or libcdio17 issue ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: audacious 3.9-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 21:02:57 2017 ExecutablePath: /usr/bin/audacious InstallationDate: Installed on 2017-12-17 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126) ProcCmdline: audacious ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: audacious StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7eff83be4870 "double free or corruption (out)", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7eff83e16c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1740644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***
Also pretty well ignored in Debian, i.e. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887640 ** Bug watch added: Debian Bug tracker #887640 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887640 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1740644 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** Status in audacious package in Ubuntu: New Status in gvfs package in Ubuntu: New Status in libcdio package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: New Status in rhythmbox package in Ubuntu: New Bug description: While trying to play an audio cd, likely a gvfs or libcdio17 issue ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: audacious 3.9-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 21:02:57 2017 ExecutablePath: /usr/bin/audacious InstallationDate: Installed on 2017-12-17 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126) ProcCmdline: audacious ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: audacious StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7eff83be4870 "double free or corruption (out)", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7eff83e16c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1740644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***
So let's add some more 'affected', maybe someone will take some notice.. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1740644 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** Status in audacious package in Ubuntu: New Status in gvfs package in Ubuntu: New Status in libcdio package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: New Status in rhythmbox package in Ubuntu: New Bug description: While trying to play an audio cd, likely a gvfs or libcdio17 issue ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: audacious 3.9-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 21:02:57 2017 ExecutablePath: /usr/bin/audacious InstallationDate: Installed on 2017-12-17 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126) ProcCmdline: audacious ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: audacious StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7eff83be4870 "double free or corruption (out)", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7eff83e16c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1740644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***
There is a crash report on this that is probably at least 3 months old, never triaged, remains private. https://bugs.launchpad.net/bugs/1737701 ** Also affects: rhythmbox (Ubuntu) Importance: Undecided Status: New ** Also affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1740644 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** Status in audacious package in Ubuntu: New Status in gvfs package in Ubuntu: New Status in libcdio package in Ubuntu: Confirmed Status in nautilus package in Ubuntu: New Status in rhythmbox package in Ubuntu: New Bug description: While trying to play an audio cd, likely a gvfs or libcdio17 issue ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: audacious 3.9-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 21:02:57 2017 ExecutablePath: /usr/bin/audacious InstallationDate: Installed on 2017-12-17 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126) ProcCmdline: audacious ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: audacious StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7eff83be4870 "double free or corruption (out)", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7eff83e16c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1740644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11
Downgrading mesa to 17.10 proposed again then upgrading in smallest groups possible (libegl1-mesa, libgl1-mesa-dri & deps first) it's this final 3 group that starts the corruption Upgraded the following packages: libgl1-mesa-glx (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 libglapi-mesa (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 libgles2-mesa (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1747744 Title: [regression] Video playback in totem is corrupted in X11 Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Test case Log inti xorg session Install gstreamer1.0-vaapi plugin Play a supported video (- h.264/avc in .mp4, .mkv or .mov would suffice Expected: hardware decoded playback What happens: totally corrupted screen, see screenshots Does work ok in a wayland session $ vainfo libva info: VA-API version 1.0.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.0 (libva 2.0.0) vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 14:43:57 2018 InstallationDate: Installed on 2018-02-06 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer-vaapi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1747744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11
Going the other way, i.e. 17.10 updated, then slowly upgraded to bionic found this. Updating totem, the eventually all of gstreamer inc. the vaapi plugin, installing libva2 packages produced no issues & did provide vaapi in totem once libva was fully on bionic versions. (restarts after all changes.. Updating libdrm2 caused no issues. However as soon as this group was updated & a reboot corruption in totem occurred Upgraded the following packages: libdrm-amdgpu1 (2.4.83-1) to 2.4.89-1 libegl1-mesa (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 libgbm1 (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 libgl1-mesa-dri (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 libgl1-mesa-glx (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 libglapi-mesa (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 libgles2-mesa (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 libmirclient9 (0.28.0+17.10.20171011.1-0ubuntu1) to 0.29.0-0ubuntu1 libmircommon7 (0.28.0+17.10.20171011.1-0ubuntu1) to 0.29.0-0ubuntu1 libmircore1 (0.28.0+17.10.20171011.1-0ubuntu1) to 0.29.0-0ubuntu1 libmirprotobuf3 (0.28.0+17.10.20171011.1-0ubuntu1) to 0.29.0-0ubuntu1 libwayland-egl1-mesa (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 mesa-va-drivers (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 mesa-vdpau-drivers (17.2.8-0ubuntu0~17.10.1) to 17.3.3-0ubuntu1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1747744 Title: [regression] Video playback in totem is corrupted in X11 Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Test case Log inti xorg session Install gstreamer1.0-vaapi plugin Play a supported video (- h.264/avc in .mp4, .mkv or .mov would suffice Expected: hardware decoded playback What happens: totally corrupted screen, see screenshots Does work ok in a wayland session $ vainfo libva info: VA-API version 1.0.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.0 (libva 2.0.0) vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 14:43:57 2018 InstallationDate: Installed on 2018-02-06 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer-vaapi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1747744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11
It's possible that this broke on the switch to libva2 which would be somewhat hard to test on a current 18.04 image.(not impossible just hard due to extensive amount of packages involved.. To note: parole works fine with the gst-vaapi plugin. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1747744 Title: [regression] Video playback in totem is corrupted in X11 Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: Confirmed Bug description: Test case Log inti xorg session Install gstreamer1.0-vaapi plugin Play a supported video (- h.264/avc in .mp4, .mkv or .mov would suffice Expected: hardware decoded playback What happens: totally corrupted screen, see screenshots Does work ok in a wayland session $ vainfo libva info: VA-API version 1.0.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.0 (libva 2.0.0) vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 14:43:57 2018 InstallationDate: Installed on 2018-02-06 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer-vaapi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1747744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747744] Re: Video playback in totem is corrupted in X11
Seems I can play a vid directly with gstreamer so maybe issue is with totem? ex. ~$ gst-launch-1.0 playbin uri=file:///home/doug/Desktop/amostviolentyear-nowplaying_h1080p.mkv Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Got context from element 'vaapisink0': gst.vaapi.Display=context, gst.vaapi.Display=(GstVaapiDisplay)"\(GstVaapiDisplayGLX\)\ vaapidisplayglx1"; Redistribute latency... Got context from element 'playsink': gst.vaapi.Display=context, gst.vaapi.Display=(GstVaapiDisplay)"\(GstVaapiDisplayGLX\)\ vaapidisplayglx1"; Redistribute latency... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstPulseSinkClock ... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1747744 Title: Video playback in totem is corrupted in X11 Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: New Bug description: Test case Log inti xorg session Install gstreamer1.0-vaapi plugin Play a supported video (- h.264/avc in .mp4, .mkv or .mov would suffice Expected: hardware decoded playback What happens: totally corrupted screen, see screenshots Does work ok in a wayland session $ vainfo libva info: VA-API version 1.0.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.0 (libva 2.0.0) vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 14:43:57 2018 InstallationDate: Installed on 2018-02-06 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer-vaapi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1747744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1747744] Re: Video playback in totem is corrupted in X11
** Also affects: totem (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1747744 Title: Video playback in totem is corrupted in X11 Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in totem package in Ubuntu: New Bug description: Test case Log inti xorg session Install gstreamer1.0-vaapi plugin Play a supported video (- h.264/avc in .mp4, .mkv or .mov would suffice Expected: hardware decoded playback What happens: totally corrupted screen, see screenshots Does work ok in a wayland session $ vainfo libva info: VA-API version 1.0.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.0 (libva 2.0.0) vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 14:43:57 2018 InstallationDate: Installed on 2018-02-06 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer-vaapi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1747744/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1719004] Re: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed.
How about fixing this in 18.04? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1719004 Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Status in CUPS: Fix Released Status in cups package in Ubuntu: Invalid Status in glibc package in Ubuntu: Confirmed Bug description: 1. Error: Package/cups-daemon2.2.4-7 (mutilated) 2. compiz-core/tmp/apport_core_q_vnqis (corrupted) ProblemType: Crash DistroRelease: Ubuntu 17.10 Package: cups-daemon 2.2.4-7 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AssertionMessage: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. Date: Fri Sep 22 22:16:18 2017 ExecutablePath: /usr/sbin/cupsd InstallationDate: Installed on 2017-05-27 (118 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20161008) Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No destinations added. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name Papersize: a4 ProcAttrCurrent: /usr/sbin/cupsd (enforce) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcEnviron: LANG=el_GR.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-11-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 Signal: 6 SourcePackage: cups Title: cupsd assert failure: cupsd: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 10/23/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0503 dmi.board.asset.tag: Default string dmi.board.name: H110M-K D3 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0503:bd10/23/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnH110M-KD3:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1719004/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: In Progress Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Committed Status in gnome-shell package in Debian: Confirmed Status in gnome-shell package in Fedora: In Progress Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
fine now in unity 7.4.5+16.04.20171201.3 ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1532508 Title: Screen contents revealed briefly on resume, before even unlocking Status in GNOME Shell: In Progress Status in Ubuntu GNOME: Confirmed Status in gdm3 package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Fix Released Status in unity source package in Xenial: Fix Committed Status in gnome-shell package in Debian: Confirmed Status in gnome-shell package in Fedora: In Progress Bug description: [Impact] When lock is enabled, the screen doesn't get blank/covered by lockscreen before suspending, thus on early resume the content might be shown. Video showing the bug: https://youtu.be/dDOgtK1MldI Reproduced on Ubuntu 2015.10, Ubuntu 2014.04 [Test case] 1. Work on highly secret files 2. Close the lid of your laptop and go have a break 3. Anyone who opens the lid of the laptop can see the secret files for a half second before the lock screen appears [Possible Regression] Content on screen isn't painted anymore and screen stays black. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1742912] Re: Please confine guest sessions again
** Changed in: lightdm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1742912 Title: Please confine guest sessions again Status in lightdm package in Ubuntu: Confirmed Bug description: This is a continuation of LP: #1663157 where as a workaround for the guest session not being confined the session got disabled. This bug tracks the fix for proper confinement. Original bug report text: Processes launched under a lightdm guest session are not confined by the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu 16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The processes are unconfined. The simple test case is to log into a guest session, launch a terminal with ctrl-alt-t, and run the following command: $ cat /proc/self/attr/current Expected output, as seen in Ubuntu 16.04 LTS, is: /usr/lib/lightdm/lightdm-guest-session (enforce) Running the command inside of an Ubuntu 16.10 and newer guest session results in: unconfined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1742912/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04
Not affected at all here with Haswell, i.e. CPU: Quad core Intel Core i7-4700MQ (-HT-MCP-) cache: 6144 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 19155 clock speeds: max: 3400 MHz 1: 2394 MHz 2: 2394 MHz 3: 2394 MHz 4: 2394 MHz 5: 2394 MHz 6: 2394 MHz 7: 2394 MHz 8: 2394 MHz Graphics: Card-1: Intel 4th Gen Core Processor Integrated Graphics Controller bus-ID: 00:02.0 Card-2: NVIDIA GK107M [GeForce GT 755M] bus-ID: 01:00.0 Display Server: X.Org 1.19.5 drivers: (unloaded: fbdev,vesa) FAILED: nouveau Resolution: 1920x1080@59.91hz GLX Renderer: Mesa DRI Intel Haswell Mobile GLX Version: 3.0 Mesa 17.2.4 Direct Rendering: Yes libgl1-mesa-dri: Installed: 17.2.4-0ubuntu1~16.04.2 ect. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1741447 Title: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04 Status in mesa package in Ubuntu: Confirmed Bug description: GUI is constantly crashing, can't start desktop Jan 5 11:21:29 1810 kernel: [ 806.368754] compiz[10824]: segfault at 0 ip 7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000] Jan 5 11:21:40 1810 kernel: [ 817.279740] compiz[1]: segfault at 0 ip 7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000] Jan 5 11:22:30 1810 kernel: [ 867.445137] compiz[11271]: segfault at 0 ip 7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000] Jan 5 11:22:46 1810 kernel: [ 883.319195] compiz[11458]: segfault at 0 ip 7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000] Jan 5 11:23:01 1810 kernel: [ 898.587610] compiz[11516]: segfault at 0 ip 7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000] In /var/crash: _usr_bin_compiz.999.crash Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not really usable. - dash not working - no window switching - sometimes all windows disappear for a few seconds So effectively my laptop is not usable after latest updates. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: unity 7.4.0+16.04.20160906-0ubuntu1 ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17 Uname: Linux 4.10.0-42-generic x86_64 .tmp.unity_support_test.0: .tmp.unity_support_test.1: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Jan 5 11:16:53 2018 DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading DistroCodename: xenial DistroVariant: ubuntu GraphicsCard: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated Graphics Controller [1025:029b] InstallationDate: Installed on 2014-04-18 (1357 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Acer Aspire 1810TZ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago) dmi.bios.date: 08/31/2010 dmi.bios.vendor: INSYDE dmi.bios.version: v1.3314 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JM11-MS dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 1 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: Aspire 1810TZ dmi.product.version: v1.3314 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***
On 01/03/2018 05:58 AM, Henning Meyer wrote: > there was a bugfix on 2017-12-22 for a double free in the function > get_cdtext_generic in the attached stack trace > > http://git.savannah.gnu.org/cgit/libcdio.git/commit/?id=f6f9c48fb40b8a1e8218799724b0b61a7161eb1d > > the latest upstream release (version 2.0.0) contains the bug fix > Can confirm that commit f6f9c48fb40b8a1e8218799724b0b61a7161eb1d does solve this and related issues, i.e. access from fie manager, gvfs, ect. ** Changed in: libcdio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1740644 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** Status in audacious package in Ubuntu: New Status in gvfs package in Ubuntu: New Status in libcdio package in Ubuntu: Confirmed Bug description: While trying to play an audio cd, likely a gvfs or libcdio17 issue ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: audacious 3.9-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 21:02:57 2017 ExecutablePath: /usr/bin/audacious InstallationDate: Installed on 2017-12-17 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126) ProcCmdline: audacious ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: audacious StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7eff83be4870 "double free or corruption (out)", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7eff83e16c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1740644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***
audacious doesn't appear to use gvfs-backends so to test removed the backends package & replaced current libcdio packages with these 3, then it (audacious) works fine libcdio16_0.94-0ubuntu1_amd64.deb libcdio-cdda2_10.2+0.94+2-2_amd64.deb libcdio-paranoia2_10.2+0.94+2-2_amd64.deb So issue seems to be with libcdio17 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1740644 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** Status in audacious package in Ubuntu: New Status in gvfs package in Ubuntu: New Status in libcdio package in Ubuntu: New Bug description: While trying to play an audio cd, likely a gvfs or libcdio17 issue ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: audacious 3.9-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 21:02:57 2017 ExecutablePath: /usr/bin/audacious InstallationDate: Installed on 2017-12-17 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126) ProcCmdline: audacious ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: audacious StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7eff83be4870 "double free or corruption (out)", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7eff83e16c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1740644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740644] Re: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x00007eff44005b70 ***
** Information type changed from Private to Public -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gvfs in Ubuntu. https://bugs.launchpad.net/bugs/1740644 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** Status in audacious package in Ubuntu: New Status in gvfs package in Ubuntu: New Status in libcdio package in Ubuntu: New Bug description: While trying to play an audio cd, likely a gvfs or libcdio17 issue ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: audacious 3.9-2 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 AssertionMessage: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** CurrentDesktop: ubuntu:GNOME Date: Sat Dec 30 21:02:57 2017 ExecutablePath: /usr/bin/audacious InstallationDate: Installed on 2017-12-17 (13 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171126) ProcCmdline: audacious ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 6 SourcePackage: audacious StacktraceTop: __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7eff83be44e8 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:181 malloc_printerr (action=, str=0x7eff83be4870 "double free or corruption (out)", ptr=, ar_ptr=) at malloc.c:5425 _int_free (av=0x7eff83e16c20 , p=, have_lock=0) at malloc.c:4174 __GI___libc_free (mem=) at malloc.c:3144 ?? () from /usr/lib/x86_64-linux-gnu/libcdio.so.17 Title: audacious assert failure: *** Error in `audacious': double free or corruption (out): 0x7eff44005b70 *** UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/audacious/+bug/1740644/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1630218] Re: gnome-shell crashed with signal 5 in g_log_default_handler()
** Tags removed: yakkety ** Tags added: bionic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1630218 Title: gnome-shell crashed with signal 5 in g_log_default_handler() Status in gnome-shell package in Ubuntu: Confirmed Bug description: The system is reporting this issue when I get logged into GNOME X11 session and I can't speak for if it is same using the Wayland session. ProblemType: Crash DistroRelease: Ubuntu 16.10 Package: gnome-shell 3.20.3-1ubuntu2 Uname: Linux 4.8.0-17-generic x86_64 ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 CurrentDesktop: GNOME-Greeter:GNOME Date: Sat Oct 1 18:55:43 2016 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell GsettingsChanges: InstallationDate: Installed on 2015-10-26 (344 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20151017.1) LocalLibraries: /usr/local/lib/libfreetype.so.6.12.2 ProcCmdline: /usr/bin/gnome-shell Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libmutter.so.0 ?? () ?? () g_log_writer_journald () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_default_handler() UpgradeStatus: Upgraded to yakkety on 2016-10-01 (2 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1630218/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1740183] [NEW] Consider removing libmir* from mesa
Public bug reported: Linking to libmir* seems to be of no value & is a roadblock to some things, ex. chromecast support in vlc. Myself see no change when mesa is not patched for mir, if there is no value anymore then please remove from build. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libegl1-mesa 17.2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Dec 26 17:24:41 2017 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-17-generic, x86_64: installed bbswitch, 0.8, 4.14.0-13-generic, x86_64: installed nvidia-381, 381.22, 4.13.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2017-11-09 (47 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171108) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-13-generic.efi.signed root=UUID=ca35bdd1-3efc-4356-aa79-7226240b6d57 ro quiet splash SourcePackage: mesa UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/18/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN44WW(V3.05) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.13.1+18.04.20171116-0ubuntu1+ppa version.libdrm2: libdrm2 2.4.89-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu2 version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu2 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-0ubuntu0~ppa0~18.04.0 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20170309-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: mesa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic compiz-0.9 single-occurrence third-party-packages ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1740183 Title: Consider removing libmir* from mesa Status in mesa package in Ubuntu: New Bug description: Linking to libmir* seems to be of no value & is a roadblock to some things, ex. chromecast support in vlc. Myself see no change when mesa is not patched for mir, if there is no value anymore then please remove from build. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libegl1-mesa 17.2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7 Uname: Linux 4.14.0-13-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu5 Architecture: amd64 CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Tue Dec 26 17:24:41 2017 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.13.0-17-generic, x86_64: installed bbswitch, 0.8, 4.14.0-13-generic, x86_64: installed nvidia-381, 381.22, 4.13.0-17-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2017-11-09 (47 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171108) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-13-generic.efi.signed
[Desktop-packages] [Bug 1728467] Re: All files on ntfs partitions are marked executable
@ Matt -
here for my personal builds (16.04/18.04) i've altered source in this manner &
it does what's best for me -
-static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };
+static const gchar *ntfs_defaults[] = { "uid=", "gid=", "fmask=0111", NULL };
If you'd like to try such builds use launchpad email & i'll point to pa's where
they are.
(- those particular ppa's are not for general use but one could dl & use any
particular package source.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs partitions are marked executable
Status in udisks2 package in Ubuntu:
Confirmed
Bug description:
This did not happen in 14.04 but somewhere since then udisks2 sets any & all
files on ntfs partitions as executable.
Additionally if file is copied over to user's ext4 partion the bit remains
set.
Can't see why this would be intentional??
In 14.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077",
"fmask=0177", NULL };
In 16.04, 17.04, 17.10,18.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udisks2 2.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 70-snap.core.rules
Date: Sun Oct 29 21:20:19 2017
InstallationDate: Installed on 2017-09-16 (43 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN44WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias:
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1728467/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1728467] Re: All files on ntfs partitions are marked executable
If the intention of the changes was to make all files executable then
that was a poor decision (it does not appear that was the focus of the
whatsoever...
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
https://bugs.launchpad.net/bugs/1728467
Title:
All files on ntfs partitions are marked executable
Status in udisks2 package in Ubuntu:
Invalid
Bug description:
This did not happen in 14.04 but somewhere since then udisks2 sets any & all
files on ntfs partitions as executable.
Additionally if file is copied over to user's ext4 partion the bit remains
set.
Can't see why this would be intentional??
In 14.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", "dmask=0077",
"fmask=0177", NULL };
In 16.04, 17.04, 17.10,18.04 udisks2 -
:static const gchar *ntfs_defaults[] = { "uid=", "gid=", NULL };
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: udisks2 2.1.7-1ubuntu1
ProcVersionSignature: Ubuntu 4.13.0-16.19~16.04.3-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CurrentDesktop: Unity
CustomUdevRuleFiles: 70-snap.core.rules
Date: Sun Oct 29 21:20:19 2017
InstallationDate: Installed on 2017-09-16 (43 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
MachineType: LENOVO 20217
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic
root=UUID=b5ef3f68-8479-4c90-8c07-7fc4c165c5e9 ro quiet splash vt.handoff=7
SourcePackage: udisks2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 74CN44WW(V3.05)
dmi.board.asset.tag: No Asset Tag
dmi.board.name: VIQY0Y1
dmi.board.vendor: LENOVO
dmi.board.version: 31900058STD
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad Y510P
dmi.modalias:
dmi:bvnLENOVO:bvr74CN44WW(V3.05):bd09/18/2013:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P:
dmi.product.family: IDEAPAD
dmi.product.name: 20217
dmi.product.version: Lenovo IdeaPad Y510P
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/udisks2/+bug/1728467/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732204] Re: Totem could not get a screenshot of the video
*** This bug is a duplicate of bug 1721248 *** https://bugs.launchpad.net/bugs/1721248 ** This bug has been marked a duplicate of bug 1721248 Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1732204 Title: Totem could not get a screenshot of the video Status in totem package in Ubuntu: Confirmed Bug description: 1) Ubuntu 17.10 2) totem 3.26.0-0ubuntu1 3) I have selected 'Take screenshot' option and I expected to get a screenshot of the video in the pictures folder 4) I got an error message, a pop-up showing 'Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report.' and no screenshot available in 'Pictures' folder ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 15:46:44 2017 InstallationDate: Installed on 2017-10-22 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1721248] Re: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos
** Summary changed: - Totem could not get a screenshot of the video + Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1721248 Title: Totem could not get a screenshot of the video when using gstreamer1.0-vaapi plugin on supported videos Status in totem package in Ubuntu: Confirmed Bug description: I try to get a screenshot from my video and totem shows a message saying it could not get a screenshot of the video and suggesting to open a bug. See attached screenshot. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.25.90.1-0ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Oct 4 14:54:16 2017 InstallationDate: Installed on 2017-09-29 (5 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1732204] Re: Totem could not get a screenshot of the video
This isn't news, the reason is likely described here & due to the use of gstreamer1.0-vaapi plugin https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1721248/comments/3 (- videos not supported by the gst vaapi plugin will get screenshots -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1732204 Title: Totem could not get a screenshot of the video Status in totem package in Ubuntu: Confirmed Bug description: 1) Ubuntu 17.10 2) totem 3.26.0-0ubuntu1 3) I have selected 'Take screenshot' option and I expected to get a screenshot of the video in the pictures folder 4) I got an error message, a pop-up showing 'Totem could not get a screenshot of the video. This is not supposed to happen; please file a bug report.' and no screenshot available in 'Pictures' folder ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: totem 3.26.0-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Nov 14 15:46:44 2017 InstallationDate: Installed on 2017-10-22 (22 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1732204/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734577] Re: Only returns snap packages in current 18.04 image installs
After several restarts seems to clear up. ** Changed in: gnome-software (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1734577 Title: Only returns snap packages in current 18.04 image installs Status in gnome-software package in Ubuntu: Invalid Bug description: Daily image of 18.04 (11/26 Fresh install, sources updated When opening Ubuntu Software (or Gnome Software in Xubuntu) only Editors picks is shown Searching for apps only returns snap version or nothing if no snap available Test case: Fresh install of current 18.04 image Boot up, log in, update sources Open Ubuntu Software, notice main screen Search for an app, ex. in screens below What happens: Only snap versions are found (if they exist To fix (user side): Remove the gnome-software snap plugin package re-open Software, all is as expected. Re-install the snap plugin, all remains as expected.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734577] Re: Only returns snap packages
** Attachment added: "searhing mpv, only old snap shown" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734577/+attachment/5014991/+files/Screenshot%20from%202017-11-26%2017-46-37.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1734577 Title: Only returns snap packages in current 18.04 image installs Status in gnome-software package in Ubuntu: New Bug description: Daily image of 18.04 (11/26 Fresh install, sources updated When opening Ubuntu Software (or Gnome Software in Xubuntu) only Editors picks is shown Searching for apps only returns snap version or nothing if no snap available Test case: Fresh install of current 18.04 image Boot up, log in, update sources Open Ubuntu Software, notice main screen Search for an app, ex. in screens below What happens: Only snap versions are found (if they exist To fix (user side): Remove the gnome-software snap plugin package re-open Software, all is as expected. Re-install the snap plugin, all remains as expected.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734577] Re: Only returns snap packages
** Attachment added: "searching vlc, only snap version shown" https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734577/+attachment/5014992/+files/Screenshot%20from%202017-11-26%2017-47-20.png ** Summary changed: - Only returns snap packages + Only returns snap packages in current 18.04 image installs -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1734577 Title: Only returns snap packages in current 18.04 image installs Status in gnome-software package in Ubuntu: New Bug description: Daily image of 18.04 (11/26 Fresh install, sources updated When opening Ubuntu Software (or Gnome Software in Xubuntu) only Editors picks is shown Searching for apps only returns snap version or nothing if no snap available Test case: Fresh install of current 18.04 image Boot up, log in, update sources Open Ubuntu Software, notice main screen Search for an app, ex. in screens below What happens: Only snap versions are found (if they exist To fix (user side): Remove the gnome-software snap plugin package re-open Software, all is as expected. Re-install the snap plugin, all remains as expected.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1734577] [NEW] Only returns snap packages in current 18.04 image installs
Public bug reported: Daily image of 18.04 (11/26 Fresh install, sources updated When opening Ubuntu Software (or Gnome Software in Xubuntu) only Editors picks is shown Searching for apps only returns snap version or nothing if no snap available Test case: Fresh install of current 18.04 image Boot up, log in, update sources Open Ubuntu Software, notice main screen Search for an app, ex. in screens below What happens: Only snap versions are found (if they exist To fix (user side): Remove the gnome-software snap plugin package re-open Software, all is as expected. Re-install the snap plugin, all remains as expected.. ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: bionic ** Attachment added: "Main window" https://bugs.launchpad.net/bugs/1734577/+attachment/5014990/+files/Screenshot%20from%202017-11-26%2017-46-10.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1734577 Title: Only returns snap packages in current 18.04 image installs Status in gnome-software package in Ubuntu: New Bug description: Daily image of 18.04 (11/26 Fresh install, sources updated When opening Ubuntu Software (or Gnome Software in Xubuntu) only Editors picks is shown Searching for apps only returns snap version or nothing if no snap available Test case: Fresh install of current 18.04 image Boot up, log in, update sources Open Ubuntu Software, notice main screen Search for an app, ex. in screens below What happens: Only snap versions are found (if they exist To fix (user side): Remove the gnome-software snap plugin package re-open Software, all is as expected. Re-install the snap plugin, all remains as expected.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1734577/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1716203] Re: Backport packages for 16.04.4 HWE stack
RE: llvm-toolchain-5.0 Works fine here in 16.04.x, no issues, would be great to see it leave proposed asap. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1716203 Title: Backport packages for 16.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-5.0 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in wayland-protocols package in Ubuntu: Invalid Status in xorg-hwe-16.04 package in Ubuntu: Invalid Status in xorg-server-hwe-16.04 package in Ubuntu: Invalid Status in libclc source package in Xenial: Fix Committed Status in libdrm source package in Xenial: Fix Committed Status in llvm-toolchain-5.0 source package in Xenial: Fix Committed Status in mesa source package in Xenial: New Status in wayland-protocols source package in Xenial: Fix Committed Status in xorg-hwe-16.04 source package in Xenial: New Status in xorg-server-hwe-16.04 source package in Xenial: New Bug description: [Impact] *** hwe-16.04 refresh for 16.04.4 *** A minor update, only some driver updates plus a newer Mesa. Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols updates. [Test case] upgrade from/to stock & old hwe stack, test desktop usage [Regression potential] libdrm: Slim to none, changes from 2.4.76 to 2.4.83 - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests - intel: new pci-ids - drm: leak fixes, manpage updates - exynos, etnaviv, freedreno, android: fixes, new stuff wayland-protocols: None, just adds a few protocol definitions (xml files) llvm-toolchain-5.0: None, a new package libclc: I'd say none, very little has changed, added support for llvm-5 is the main reason for this slightly newer snapshot xorg-server: Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include: - security fixes - backported bugfixes to glamor, modesetting driver, xwayland etc mesa: New major release plus a few bugfix updates after that. Regressions at this point are less likely. Upstream is tested by Intel CI system for instance. And we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for the bugfix release (xenial & artful) is bug 1727390 [Other information] build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc, xorg-server], mesa To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1586516] Re: Rb sets all mp3's extracted from an audiocd to 31kbps
** Changed in: rhythmbox (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1586516 Title: Rb sets all mp3's extracted from an audiocd to 31kbps Status in rhythmbox package in Ubuntu: Invalid Bug description: Test case: Insert an audio cd Open Rb > Edit > Preferences > Music > pick any mp3 option Extract a track, when done ck. the file properties No matter what mp3 setting all are *reported* at 31kbps So it's setting an improper/incorrect bitrate index in frame headers ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: rhythmbox 3.3-1ubuntu7 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Fri May 27 15:28:21 2016 InstallationDate: Installed on 2016-04-26 (31 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) SourcePackage: rhythmbox UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1586516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1711964] Re: Breaks Firefox if logging out or restating with firefox open
No longer issue ** Changed in: firefox (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1711964 Title: Breaks Firefox if logging out or restating with firefox open Status in firefox package in Ubuntu: Invalid Bug description: Test case: open firefox, go to any page Only open 1 instance of firefox restart or log out/in without closing firefox What happens: when opening firefox in new login it opens to default startpage & is unresponsive What should happen: should either open to page on before or offer to reload that page, also should be usable This behavior not seen in ubuntu-web-launchers (17.10.10) package version ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: ubuntu-web-launchers 17.10.12 ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5 Uname: Linux 4.12.0-11-generic x86_64 ApportVersion: 2.20.6-0ubuntu6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sun Aug 20 19:20:33 2017 InstallationDate: Installed on 2017-08-20 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170818) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1711964/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
