[Touch-packages] [Bug 1886272] [NEW] Request to package webp pixbuf
Public bug reported: It is not currently possible to open a WebP image in any standard application on Ubuntu (except Firefox). There is a now a small extension for gdk-pixbuf to support webp: https://github.com/aruiz/webp-pixbuf- loader Such extension has already been packaged for HEIF (heif-gdk-pixbuf), it'd be nice to have it for WebP too. Once installed, any standard Gnome program can support reading such image, and in particular, eog. An example file: https://www.gstatic.com/webp/gallery/1.webp ** Affects: libwebp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/1886272 Title: Request to package webp pixbuf Status in libwebp package in Ubuntu: New Bug description: It is not currently possible to open a WebP image in any standard application on Ubuntu (except Firefox). There is a now a small extension for gdk-pixbuf to support webp: https://github.com/aruiz /webp-pixbuf-loader Such extension has already been packaged for HEIF (heif-gdk-pixbuf), it'd be nice to have it for WebP too. Once installed, any standard Gnome program can support reading such image, and in particular, eog. An example file: https://www.gstatic.com/webp/gallery/1.webp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/1886272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
@deragon, here, the "$(sleep 10;/sbin/wpa_cli resume)&" doesn't work. Somehow, I wonder if there is some black magic due to systemd, but it doesn't seem that any command after the sleep is ever executed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Interestingly, this "wpa_cli resume" command is precisely what does /lib/systemd/system-sleep/wpasupplicant. I've checked, this script is run at resume, as expected. However, it seems wpa is called too early, and it doesn't have any effect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
As a side-note, as it seems it's been triggered for my laptop by the update to network-manger 1.2.4, one of the few fixes included in 1.2.6 is the following: * Fixed a bug that caused devices to stay unmanaged after resume from sleep. So quite probably, updating network-manager to the latest stable version will help -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
One more thing: contrarily to the title of this bug report, here "sudo wpa_cli scan" doesn't help to get the list of network again. However, "sudo wpa_cli resume" works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Same as comment #52 and #53, while it used to be just once in a while, since a few weeks, it's now _every_ single time that my laptop resumes. There are many similar bugs but with probably different causes. So to be clear here is the symptoms I see much more recently since a few weeks (on 16.04): after resume, only a couple of wifi networks will be listed at most, and never the one I use. This workaround does work (to get nm-applet list all the networks again): sudo service network-manager restart These things do _not_ work: * restarting nm-applet * disabling/enabling the wifi from the hardware key * trying to unblock the wifi in software (via rfkill), it's not even marked as disabled anyway. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1585863 Title: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it. Status in OEM Priority Project: New Status in OEM Priority Project xenial series: New Status in network-manager package in Ubuntu: Confirmed Bug description: Description:Ubuntu Yakkety Yak (development branch) Release:16.10 Packages: libnm-glib-vpn1:amd64 1.2.2-0ubuntu2 libnm-glib4:amd64 1.2.2-0ubuntu2 libnm-util2:amd64 1.2.2-0ubuntu2 libnm0:amd641.2.2-0ubuntu2 network-manager 1.2.2-0ubuntu2 Reproduce steps: 1. Install fwts by `sudo apt-get install fwts`. 2. Run the suspend & resume stress test. sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 --s3-delay-delta=5 Expected result: The WiFi still functioned. Actual result: The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again. P.S. Ubuntu 16.04 also has the same issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373978] Re: Totem:"GStreamer encountered a general stream error." on .flv and .mp4 files
Actually, it seems the same problem as described in bug #1373978. Without gstreamer1.0-vaapi: $ gst-launch-1.0 filesrc location=00072282.jpg ! decodebin ! imagefreeze ! videoconvert ! autovideosink Setting pipeline to PAUSED ... Pipeline is PREROLLING ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock With gstreamer1.0-vaapi: $ gst-launch-1.0 filesrc location=00072282.jpg ! decodebin ! imagefreeze ! videoconvert ! autovideosink Setting pipeline to PAUSED ... libva info: VA-API version 0.37.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_37 libva info: va_openDriver() returns 0 Pipeline is PREROLLING ... ERROR: from element /GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstJpegDec:jpegdec0: No valid frames decoded before end of stream Additional debug info: gstvideodecoder.c(1070): gst_video_decoder_sink_event_default (): /GstPipeline:pipeline0/GstDecodeBin:decodebin0/GstJpegDec:jpegdec0: no valid frames found ERROR: pipeline doesn't want to preroll. Setting pipeline to NULL ... Freeing pipeline ... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1373978 Title: Totem:"GStreamer encountered a general stream error." on .flv and .mp4 files Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: If a .flv or .mp4 file is played with Totem, Totem shows an error saying "GStreamer encountered a general stream error.". Steps to produce: 1- Open a video file, which has an extension .flv or .mp4, with Totem. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgstreamer1.0-0 1.4.2-1 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 25 17:33:36 2014 InstallationDate: Installed on 2014-02-27 (209 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to utopic on 2014-09-08 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1373978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373978] Re: Totem:"GStreamer encountered a general stream error." on .flv and .mp4 files
Sorry, I meant it is similar as bug #1397597. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1373978 Title: Totem:"GStreamer encountered a general stream error." on .flv and .mp4 files Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: If a .flv or .mp4 file is played with Totem, Totem shows an error saying "GStreamer encountered a general stream error.". Steps to produce: 1- Open a video file, which has an extension .flv or .mp4, with Totem. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgstreamer1.0-0 1.4.2-1 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 25 17:33:36 2014 InstallationDate: Installed on 2014-02-27 (209 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to utopic on 2014-09-08 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1373978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373978] Re: Totem:"GStreamer encountered a general stream error." on .flv and .mp4 files
I got the same problem, on Ubuntu 15.04. It seems to be related to filetype: Some filetypes still open fine (eg, .avi), but .mp4 and .mkv fail. It turned out that _removing_ gstreamer1.0-vaapi solved the problem. sudo apt-get remove gstreamer1.0-vaapi Note: my graphic card is a "Intel Corporation Haswell-ULT". -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1373978 Title: Totem:"GStreamer encountered a general stream error." on .flv and .mp4 files Status in gstreamer1.0 package in Ubuntu: Confirmed Bug description: If a .flv or .mp4 file is played with Totem, Totem shows an error saying "GStreamer encountered a general stream error.". Steps to produce: 1- Open a video file, which has an extension .flv or .mp4, with Totem. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgstreamer1.0-0 1.4.2-1 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Sep 25 17:33:36 2014 InstallationDate: Installed on 2014-02-27 (209 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140224) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to utopic on 2014-09-08 (16 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1373978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
