[Touch-packages] [Bug 1001738] Re: Totem no longer play rtsp stream : black video-no sound
broken on 15.04 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1001738 Title: Totem no longer play rtsp stream : black video-no sound Status in gstreamer0.10 package in Ubuntu: Confirmed Bug description: In oneiric I was able to play my freebox (adsl provider) tv stream with this : totem http://mafreebox.freebox.fr/freeboxtv/playlist.m3u With precise upgrade, i can see the list of stream, but I can't play them : black video and no sound. A example of content of this file : #EXTINF:0,2 - France 2 HD rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1=201=hd #EXTINF:0,2 - France 2 rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1=201=sd #EXTINF:0,2 - France 2 (bas débit) rtsp://mafreebox.freebox.fr/fbxtv_pub/stream?namespace=1=201=ld ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgstreamer0.10-0 0.10.36-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14 Uname: Linux 3.2.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu7 Architecture: i386 Date: Sat May 19 20:11:15 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer0.10 UpgradeStatus: Upgraded to precise on 2012-04-27 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1001738/+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 987212] Re: Wireless printer Processing - Unable to locate printer.
Also effects utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/987212 Title: Wireless printer Processing - Unable to locate printer. Status in avahi package in Ubuntu: Confirmed Status in avahi source package in Precise: Confirmed Status in avahi source package in Quantal: Won't Fix Status in avahi source package in Raring: Won't Fix Bug description: Description: Ubuntu 12.04 LTS (Precise Pangolin) Beta 2 Release: 12.04 Beta 2 The printer is a Lexmark X734de printer connected over a wireless network that can be found, but will not print. The print job stays in the queue forever. Wireless Printer Processing - Unable to locate printer. Network/Local Printers found but cannot print - Unable to get printer status and says it's Processing. I'm shure we want avoid this for the Ubuntu 12.04 LTS (Precise Pangolin) release, when the final has been released. I'm using Ubuntu 12.04 LTS (Precise Pangolin) Beta 2 with latest update as of today. CUPS log: /var/log/cups/error_log W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-Gray..' already exists W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-CMYK..' already exists W [23/Apr/2012:11:48:05 +0200] failed to CreateDevice: org.freedesktop.ColorManager.AlreadyExists:device id 'cups-Lexmark-X734de' already exists W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-Gray..' already exists W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-CMYK..' already exists W [23/Apr/2012:11:48:05 +0200] failed to CreateDevice: org.freedesktop.ColorManager.AlreadyExists:device id 'cups-Lexmark-X734de' already exists W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-Gray..' already exists W [23/Apr/2012:11:48:05 +0200] failed to CreateProfile: org.freedesktop.ColorManager.AlreadyExists:profile id 'Lexmark-X734de-CMYK..' already exists W [23/Apr/2012:11:48:05 +0200] failed to CreateDevice: org.freedesktop.ColorManager.AlreadyExists:device id 'cups-Lexmark-X734de' already exists E [23/Apr/2012:11:50:58 +0200] [Job 2] Unable to find printer. E [23/Apr/2012:11:51:13 +0200] [Job 2] Unable to find printer. E [23/Apr/2012:11:51:28 +0200] [Job 2] Unable to find printer. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: system-config-printer-gnome 1.3.8+20120201-0ubuntu8 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12 Uname: Linux 3.2.0-20-generic-pae i686 ApportVersion: 2.0.1-0ubuntu5 Architecture: i386 CheckboxSubmission: e28f23d40ba6960d2759044b1acbd380 CheckboxSystem: c69722ecac764861be52925fa50b4dcc Date: Mon Apr 23 11:58:03 2012 ExecutablePath: /usr/share/system-config-printer/system-config-printer.py InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) InterpreterPath: /usr/bin/python2.7 Lpstat: device for Canon-MP190-series: usb://Canon/MP190%20series?serial=E14D77interface=1 device for Lexmark-X734de: dnssd://Lexmark%20X734de._pdl-datastream._tcp.local/ MachineType: Acer AOA150 PackageArchitecture: all Papersize: a4 PpdFiles: Lexmark-X734de: Lexmark X734de Canon-MP190-series: Canon PIXMA MP190 - CUPS+Gutenprint v5.2.8-pre1 ProcEnviron: LANGUAGE=se_NO:nb_NO:nb:no_NO:no:nn_NO:nn:da:sv:en LANG=se_NO SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic-pae root=UUID=6448F9C148F991D2 loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7 SourcePackage: system-config-printer UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/09/2008 dmi.bios.vendor: Acer dmi.bios.version: v0.3305 dmi.board.asset.tag: Base Board Asset Tag 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:bvnAcer:bvrv0.3305:bd05/09/2008:svnAcer:pnAOA150:pvr1:rvnAcer:rn:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion: dmi.product.name: AOA150 dmi.product.version: 1 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/987212/+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 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
@r0lf this is still happening in 14.10/Utopic should it be reopened there? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in systemd-shim package in Ubuntu: Confirmed Status in systemd-shim source package in Saucy: Won't Fix Status in systemd-shim source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+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
