[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
Or as one user posted, the official AMDGPU Pro package, which also enables 10bpc. -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
This bug can only occur if 10bpc is enabled. There is no other possibility. It is clearly a colorspace mismatch between VAAPI and the decode target surface. If disabling 10bpc happens in Ubuntu Mesa packages, then it is clearly someone using unofficial package builds of Mesa which have 10bpc enabled on supporting hardware. -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
As already stated above, the correct workaround, for now, is to configure a drirc (probably in a conf.d directory, so it doesn't clash with other settings files) so as to disable 10 bit per channel support for Totem. The same had to be done with Chromium-vaapi, as it also happens with that solution. -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1720630] Re: Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1
I wouldn’t exactly consider Google Drive “friendly”, but I guess most users don’t have 10+TB of data stored on premises. That much runs for a minimum of $99/mo on Google One. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to deja-dup in Ubuntu. https://bugs.launchpad.net/bugs/1720630 Title: Amazon S3 storage location missing from Deja Dup 36.1-0ubuntu1 Status in Déjà Dup: Invalid Status in deja-dup package in Ubuntu: Invalid Bug description: I am currently testing out Ubuntu 17.10 and I noticed that Deja Dup (version 36.1-0ubuntu1) no longer supports S3 backups. I have already installed the packages python-boto python-cloudfiles but the "Amazon S3" option is missing from the Storage location tab. Using dconfig editor, I can see the S3 records created under /org/gnome/deja-dup/s3. The same installation works fine on Ubuntu 16.04. Any thoughts? lsb_release -d Description: Ubuntu Artful Aardvark (development branch) dpkg-query -W deja-dup duplicity deja-dup 36.1-0ubuntu1 duplicity gsettings list-recursively org.gnome.DejaDup org.gnome.DejaDup last-restore '' org.gnome.DejaDup periodic false org.gnome.DejaDup periodic-period 7 org.gnome.DejaDup full-backup-period 90 org.gnome.DejaDup backend 'remote' org.gnome.DejaDup last-run '' org.gnome.DejaDup nag-check '' org.gnome.DejaDup prompt-check '2017-10-01T10:29:53.542958Z' org.gnome.DejaDup root-prompt true org.gnome.DejaDup include-list ['$HOME'] org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD'] org.gnome.DejaDup last-backup '' org.gnome.DejaDup allow-metered false org.gnome.DejaDup delete-after 0 org.gnome.DejaDup.Rackspace username '' org.gnome.DejaDup.Rackspace container 'ubuntu' org.gnome.DejaDup.S3 id '' org.gnome.DejaDup.S3 bucket '' org.gnome.DejaDup.S3 folder 'ubuntu' org.gnome.DejaDup.OpenStack authurl '' org.gnome.DejaDup.OpenStack tenant '' org.gnome.DejaDup.OpenStack username '' org.gnome.DejaDup.OpenStack container 'ubuntu' org.gnome.DejaDup.GCS id '' org.gnome.DejaDup.GCS bucket '' org.gnome.DejaDup.GCS folder 'ubuntu' org.gnome.DejaDup.Local folder 'ubuntu' org.gnome.DejaDup.Remote uri '' org.gnome.DejaDup.Remote folder 'ubuntu' org.gnome.DejaDup.Drive uuid '' org.gnome.DejaDup.Drive icon '' org.gnome.DejaDup.Drive folder '$HOSTNAME' org.gnome.DejaDup.Drive name '' org.gnome.DejaDup.GOA id '' org.gnome.DejaDup.GOA folder 'ubuntu' org.gnome.DejaDup.GOA type 'owncloud' org.gnome.DejaDup.File short-name '' org.gnome.DejaDup.File type 'normal' org.gnome.DejaDup.File migrated true org.gnome.DejaDup.File name '' org.gnome.DejaDup.File path '' org.gnome.DejaDup.File uuid '' org.gnome.DejaDup.File icon '' org.gnome.DejaDup.File relpath @ay [] To manage notifications about this bug go to: https://bugs.launchpad.net/deja-dup/+bug/1720630/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789523] Re: The ssh-agent launcher script fails to relaunch ssh-agent
It appears it's still there, but only accessible to project members. Which also excludes me. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1789523 Title: The ssh-agent launcher script fails to relaunch ssh-agent Status in xorg package in Ubuntu: Confirmed Bug description: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-GD65 (MS-7751) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7751 dmi.product.version: 2.0 dmi.sys.vendor: MSI mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 2018-08-28T17:23:14.025376 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:18.3~git180816191500.b618d7e~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:18.3~git180816191500.b618d7e~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.99+git1808290006.cba8fe4~b~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1806121919.3d39506~b~padoka0 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1789523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
Adding a comment to indicate that this is a problem with the 10bpc support which is enabled in Radeon graphics. I am unsure if it is enabled in Intel's drivers, so that would explain why it does not occur there. Either VA-API is outputting wrong, the client library is outputting wrong, or all the player applications are wrong. Something appears to be matching the buffers to each other without a conversion, simply because both RGBA32 and RGBA10-10-10-2 have the same number of bytes per pixel, but clearly completely different structure. A workaround is to add the following to the //driconf/device section of /etc/drirc: Clearly, this workaround should not be the only way, since someone in the processing chain clearly wants 10bpc support, and some applications can benefit from it, somehow. -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1623666] Re: iOS device contents not displayed in Ubuntu
Yes, but this does not grant transparent access to the Documents folders of installed applications. Pairing and libimobiledevice are still needed for that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1623666 Title: iOS device contents not displayed in Ubuntu Status in Libimobiledevice: Fix Released Status in gnutls28 package in Ubuntu: Confirmed Status in libimobiledevice package in Ubuntu: Confirmed Bug description: Plug in iOS device, and it doesn't show the documents on it. Please package the recent fix in libimobiledevice*: Vauge discussion that mentions using the latest git HEAD*: https://github.com/libimobiledevice/libimobiledevice/issues/327 *This discussion is quite vague. One comment points out "iOS 10 devices don't allow SSLv3 anymore but require at least TLSv1", but not how or if that has been fixed in libimobiledevice git HEAD. This ppa packages the git version and may resolve the issue: https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages There are several other upstream reports related to this problem. Partial success patch (idevicepair only) trying to keep GnuTLS: https://github.com/libimobiledevice/libimobiledevice/issues/413 Failure with GnuTLS, Success with OpenSSL: https://gitlab.com/gnutls/gnutls/issues/145 Ubuntu packages libimobiledevice with "--disable-openssl": https://github.com/libimobiledevice/ifuse/issues/32 Duplicate bug 1638177 suggests to repackage libimobiledevice using OpenSSL to avoid this problem, as per comment 27 below. To manage notifications about this bug go to: https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
I only thought to mention the PPA to indicate that the bug still occurs even in fairly bleeding edge Mesa code. I also still think it's either something wrong with gstreamer-vaapi, or something that gstreamer-vaapi is doing different from what mpv does for the same exact video. It should probably be reported to upstream Mesa, just in case it really is their bug. -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789523] Re: The ssh-agent launcher script fails to relaunch ssh-agent
Freedesktop tells me it's a downstream Debian script file. https://gitlab.freedesktop.org/xorg/meta/issues/6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1789523 Title: The ssh-agent launcher script fails to relaunch ssh-agent Status in xorg package in Ubuntu: Incomplete Bug description: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-GD65 (MS-7751) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7751 dmi.product.version: 2.0 dmi.sys.vendor: MSI mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 2018-08-28T17:23:14.025376 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:18.3~git180816191500.b618d7e~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:18.3~git180816191500.b618d7e~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.99+git1808290006.cba8fe4~b~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1806121919.3d39506~b~padoka0 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1789523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
** Attachment added: "And here's a screen shot of mpv with vaapi, also playing correctly." https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5181988/+files/Screenshot_20180828_204952.png -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
** Attachment added: "For reference, the same video in Totem." https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5181989/+files/Screenshot_20180828_205430.png -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos
I have tested on my Radeon RX480, also AMDGPU drivers, git snapshot from 20180829 from Padoka PPA, and this bug occurs with Totem as well. It should also be noted that the bug does not occur with mpv, either with vdpau or vaapi. ** Attachment added: "Screen shot of mpv plus vdpau and terminal output" https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+attachment/5181987/+files/Screenshot_20180828_204917.png -- 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/1767312 Title: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos Status in gstreamer-vaapi package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian stable, debian testing) aren't affected). When i try to reproduce a video that use h264 codec, i've wrong colors. I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6 WORKAROUND: sudo apt remove gstreamer1.0-vaapi or sudo apt remove mesa-va-drivers See also bug 1720820. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1789523] [NEW] The ssh-agent launcher script fails to relaunch ssh-agent
Public bug reported: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-GD65 (MS-7751) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7751 dmi.product.version: 2.0 dmi.sys.vendor: MSI mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 2018-08-28T17:23:14.025376 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:18.3~git180816191500.b618d7e~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:18.3~git180816191500.b618d7e~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.99+git1808290006.cba8fe4~b~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1806121919.3d39506~b~padoka0 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1789523 Title: The ssh-agent launcher script fails to relaunch ssh-agent Status in xorg package in Ubuntu: New Bug description: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no
[Desktop-packages] [Bug 1789523] Re: The ssh-agent launcher script fails to relaunch ssh-agent
** Patch added: "Patch to fix ssh-agent startup script" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1789523/+attachment/5181938/+files/90x11-common_ssh-agent.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1789523 Title: The ssh-agent launcher script fails to relaunch ssh-agent Status in xorg package in Ubuntu: New Bug description: There is an issue with the Xsession, in which logging out and logging back in again does not clear environment variables, so the ssh-agent script thinks that the agent is already running, and thus does not bother to start it again. I have altered the script, albeit in not the most pretty way, to detect if the agent is already running, and if not, force a restart. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: x11-common 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Tue Aug 28 17:33:34 2018 Dependencies: lsb-base 9.20170808ubuntu1 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: anbox, 1, 4.15.0-32-generic, x86_64: installed anbox, 1, 4.15.0-33-generic, x86_64: installed nvidia, 396.54, 4.15.0-33-generic, x86_64: installed GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] [1002:67df] (rev c7) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb] InstallationDate: Installed on 2018-08-04 (24 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: MSI MS-7751 PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z77A-GD65 (MS-7751) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7751 dmi.product.version: 2.0 dmi.sys.vendor: MSI mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 2018-08-28T17:23:14.025376 version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0 version.libgl1-mesa-dri: libgl1-mesa-dri 1:18.3~git180816191500.b618d7e~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 1:18.3~git180816191500.b618d7e~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.99+git1808290006.cba8fe4~b~padoka0 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git1806121919.3d39506~b~padoka0 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1789523/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1726262] Re: 17.10 - flickering overlay patterns in gnome-terminal
Confirming that this issue does occur with Ubuntu 18.04.1, i7 3770, with AMD Radeon RX 480, using AMDGPU. I'm also using the kernel ppa 4.17 from June 4th, so I can keep AMDGPU DC enabled and use my primary monitor's DVI-D dual link connection to support 120Hz refresh rate. I can also confirm that unchecking "Use transparency from system theme", checking "Use transparent background", and re-checking "Use transparency from system theme", results in a stable background. Perhaps "Use transparent background" should check itself if the system theme employs transparency? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1726262 Title: 17.10 - flickering overlay patterns in gnome-terminal Status in gnome-terminal package in Ubuntu: Confirmed Bug description: Clean install of Ubuntu 17.10. For gnome-terminal select color-scheme "black on light yellow". Overlay partly with e.g. Chrome (Browser) or Geany (editor). Then the border shadow of the e.g. Geany produces flickering extended shadows in the gnome-terminal. Foto with the extended shadows is attached. This bug was introduced with 17.10. This flickering didn't appear in 17.04, 16.10, 16.04... Working as a developer with several open terminal windows on the desktop, this produces a disturbing desktop environment and mitigated by covering not used terminal windows complete with other apps. Haven't reproduced with other apps than gnome-terminal. Hardware Lenovo Thinkpad e330, cpu : Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz gpu Builtin : HD 4000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1726262/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
