[Touch-packages] [Bug 1382567] Re: Top Crasher: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': free(): invalid pointer: ADD
Thanks for opening the new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1382567 Title: Top Crasher: /usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner:*** Error in `/usr/lib/arm-linux-gnueabihf/unity-scopes/scoperunner': free(): invalid pointer: ADDR *** Status in The Savilerow project: Confirmed Status in unity-scopes-api package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity-scopes-api. This problem was most recently seen with version 0.6.7+14.10.20141010.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/69d0dabacb1ee1cc5be6fba75784a0751c80617d contains more details. Steps to reproduce: 1. Swipe up from bottom of screen and select dashboard 2. Swipe up from bottom of screen and select apps expected result: no crash actual result: crash To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1382567/+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 1455340] Re: package libqt5webkit5 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_6
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1455340 Title: package libqt5webkit5 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux- gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux- gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: I was doing a regular `sudo apt-get update && sudo apt-get dist- upgrade` when it failed for some reason. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libqt5webkit5 (not installed) ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri May 15 08:06:56 2015 DuplicateSignature: package:libqt5webkit5:(not installed):cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2015-04-25 (19 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: qtwebkit-opensource-src Title: package libqt5webkit5 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1455340/+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 1453282] Re: [Neither headphones nor speakers are displayed under "All Settings"->Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all
I'm guessing it isn't spdif because it says it's audio for the HDMI. Something I ended up finding I think is using alsamixer to make sure "auto-mute" is disabled, but that is only so I can have audio from the headphones in the front and back at the same time. However what I just found is resuming from suspend, the audio listing is missing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1453282 Title: [Neither headphones nor speakers are displayed under "All Settings"->Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: Incomplete Bug description: The motherboard speakers and microphone aren't listed under "All Settings"->Sound UNLESS I unplug them and then plug them back in. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 11102 F pulseaudio /dev/snd/pcmC1D0c: username 11102 F...m pulseaudio /dev/snd/controlC1: username 11102 F pulseaudio /dev/snd/timer: username 11102 f pulseaudio CurrentDesktop: Unity Date: Fri May 8 16:09:24 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-07 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., VIA VT1718S, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H55M Pro dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/06/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1453282/+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 1455340] [NEW] package libqt5webkit5 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86
Public bug reported: I was doing a regular `sudo apt-get update && sudo apt-get dist-upgrade` when it failed for some reason. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libqt5webkit5 (not installed) ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri May 15 08:06:56 2015 DuplicateSignature: package:libqt5webkit5:(not installed):cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2015-04-25 (19 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: qtwebkit-opensource-src Title: package libqt5webkit5 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: qtwebkit-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtwebkit-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1455340 Title: package libqt5webkit5 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux- gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux- gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: I was doing a regular `sudo apt-get update && sudo apt-get dist- upgrade` when it failed for some reason. ProblemType: Package DistroRelease: Ubuntu 15.04 Package: libqt5webkit5 (not installed) ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 Date: Fri May 15 08:06:56 2015 DuplicateSignature: package:libqt5webkit5:(not installed):cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream ErrorMessage: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2015-04-25 (19 days ago) InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 (20150422) RelatedPackageVersions: dpkg 1.17.25ubuntu1 apt 1.0.9.7ubuntu4 SourcePackage: qtwebkit-opensource-src Title: package libqt5webkit5 (not installed) failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1' to '/usr/lib/x86_64-linux-gnu/libQt5WebKit.so.5.4.1.dpkg-new': unexpected end of file or stream UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1455340/+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 1316913] Re: wrong keybord layout at system start
Is there any available solution for this keyboard error ? That's really boring to change the keyboard layout in the top bar at each wake up. Please hurry up ! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1316913 Title: wrong keybord layout at system start Status in lightdm package in Ubuntu: Confirmed Bug description: my system is set to german by default (De). When starting thunderbird and writing a new mail my keyboard is in qwerty mode. i must click on the De icon in the task bar to set it to qwertz mode. When updates need to be veriyfied with password i get wrong password - clicking the de icon in task bar sets it to german. thanks! ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1316913/+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 1322925] Re: [SRU] Copy, paste stops working randomly in Ubuntu 14.04 nautilus
I just installed Ubuntu 15.04 RTM, and faced out with multiple problems with the copying files from HDD to USB flash-drive. 1. Not all files copied! You can't be sure that all what you selected is really copied. 2. You can delete folders in USB drive (Directory is not empty). 3. The copied files are corrupted sometimes. 4. You can't even formate the drive. 5. The progress bar of the copying process moves very quickly, but after this window disappears, you have to wait until this process will be really finished (in background), e.g. if you try to unmount/safely remove USB, you'll get the warning, that the drive is still busy or something like that. Non of described above issue doesn't happen with the same USB drive on Windows or on Fedora 21, thus it seems to be an Ubuntu specific case. P.S. I'm in shock that this kind of critical issue is not fixed for during one year and even new releases (14.10 LTS, 15.04) comes with such extremely important bug, when you can't rely on OS in the data copying process. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1322925 Title: [SRU] Copy, paste stops working randomly in Ubuntu 14.04 nautilus Status in Nautilus: Fix Released Status in nautilus package in Ubuntu: Fix Released Status in xorg package in Ubuntu: Confirmed Status in nautilus source package in Trusty: Fix Released Status in xorg source package in Trusty: Confirmed Status in nautilus source package in Utopic: Fix Released Status in xorg source package in Utopic: Confirmed Bug description: The title says it. Since upgrade to 14.04, copy / cut / paste of files among various folders I have write rights on does not work most of the times. Using the terminal to copy / move does work normally. nautilus: Installed: 1:3.10.1-0ubuntu9.1 Candidate: 1:3.10.1-0ubuntu9.1 Version table: *** 1:3.10.1-0ubuntu9.1 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 Packages 100 /var/lib/dpkg/status 1:3.10.1-0ubuntu8 0 500 http://de.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages [Test Case] 1. Open a Nautilus window and switch to List view 2. Go to location with write permission 3. Select a file and try to rename. 4. When prompted to rename (filename becomes a text entry), open new tab. 5. Select a file, try to copy and paste. You will see that file is not copied and pasted. 6. Go back to original tab. If the file that was selected in step 3 is still selected, unselect it. 7. Try to copy and paste. It should work. 8. Try to rename again, and open new tab. 9. Close old tab, and try to copy and paste. It won't work, and there is no way to restore, except opening a new window. [Regression Potential] Already fixed upstream with https://git.gnome.org/browse/nautilus/commit/?id=8032628adc9c8286050716d609c574dc7273dfcb To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1322925/+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 1448180] Re: QGeoSatelliteInfoSource::createDefaultSource() returns NULL on the bq phone
We don't expose satellite visibility information to applications, yet. However, the respective information is certainly used in the service. Please watch this bug and changes to its status for tracking the feature request. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu-sensors in Ubuntu. https://bugs.launchpad.net/bugs/1448180 Title: QGeoSatelliteInfoSource::createDefaultSource() returns NULL on the bq phone Status in location-service package in Ubuntu: Invalid Status in qtubuntu-sensors package in Ubuntu: Confirmed Bug description: Device: bq Aquaris E4.5 Ubuntu Edition Operating System: Ubuntu 14.10 (r21) I am currently trying to build a clone of the "GPS Status" Android app, it displays various details about the built-in GPS receiver. According to the developer documentation at http://developer.ubuntu.com/api/qml/sdk-14.10/QtLocation.location- positioning-cpp/ , a call to QGeoSatelliteInfoSource::createDefaultSource() can be used to get access to the default Satellite positioning source implementation. On my device this call returns NULL. Sample code is located at https://github.com/Sturmflut/ubuntu-touch- simple-gps/tree/3da3dc5f089e698c34765fd18322b84727cb13ae , the call in question is located at backend/modules/Simplegps/gpsdataprovider.cpp . I attached the file and its header for future reference. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1448180/+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 1449045] Re: BQ 4.5 mobile position is wrong on cell radio
Which app do you use to check on your location? Please rely on either Google Maps or the Here app for testing purposes as OSMTouch falls back to geoip-based positioning if it couldn't receive a fix within a timeout period. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1449045 Title: BQ 4.5 mobile position is wrong on cell radio Status in location-service package in Ubuntu: New Bug description: Ubuntuphone bq 4.5 14.10 (r21) For this bug GPS is switched off, so location service have to use other informations. Work pretty well within wlan, so hamburg is hamburg and environment. When i leave the house and congstar radio is used, the locations jumps to schwalmstadt (hesse) what is 500km far away from hamburg. Going back into my wlan the location service is able to switch to hamburg again. Congstar use the t-mobile.de APN, don't know if that is related for this bug. All apps and programs related to the location service jump between hamburg and schwalmstadt. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1449045/+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 1444379] Re: Plain GPS works, GPS with wifi/3g data never uses GPS
** Also affects: location-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1444379 Title: Plain GPS works, GPS with wifi/3g data never uses GPS Status in location-service package in Ubuntu: New Status in phablet-tools package in Ubuntu: Confirmed Bug description: On the BQ Aquaris E4.5 I can use the GPS, but whenever I set the GPS to use wifi/mobile data it only fixes when Wifi is near. Also when I change the setting back to GPS only, I need to reboot before the setting is applied. I am using stock BQ Aquaris E4.5 with Ubuntu 14.10 (all updated) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1444379/+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 1453159] Re: [Ubuntu Phone BQ] GPS disabled after flight mode/restart
** Also affects: location-service Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1453159 Title: [Ubuntu Phone BQ] GPS disabled after flight mode/restart Status in Location Service: New Status in indicator-network package in Ubuntu: New Bug description: Hi! Steps: 1. Enable GPS from the status bar. 2. Change to Flight mode enabled 3. Change to Flight mode disabled > Bug: GPS is disabled It's not happening all the times. I don't know the pattern. The GPS is losing its status a few times with a mobile restart too. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/location-service/+bug/1453159/+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 1455319] [NEW] package linux-image-extra-3.16.0-37-generic 3.16.0-37.51 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
Public bug reported: Errors were encountered while processing: /var/cache/apt/archives/linux-image-3.16.0-33-generic_3.16.0-33.44_amd64.deb /var/cache/apt/archives/linux-image-3.16.0-34-generic_3.16.0-34.47_amd64.deb /var/cache/apt/archives/linux-image-3.16.0-36-generic_3.16.0-36.48_amd64.deb /var/cache/apt/archives/linux-image-3.16.0-37-generic_3.16.0-37.51_amd64.deb /var/cache/apt/archives/linux-image-3.16.0-38-generic_3.16.0-38.52_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) The following packages have unmet dependencies: linux-signed-image-3.16.0-33-generic : Depends: linux-image-3.16.0-33-generic (= 3.16.0-33.44) but 3.16.0-33.44~14.04.1 is installed linux-signed-image-3.16.0-34-generic : Depends: linux-image-3.16.0-34-generic (= 3.16.0-34.47) but 3.16.0-34.47~14.04.1 is installed linux-signed-image-3.16.0-36-generic : Depends: linux-image-3.16.0-36-generic (= 3.16.0-36.48) but 3.16.0-36.48~14.04.1 is installed linux-signed-image-3.16.0-37-generic : Depends: linux-image-3.16.0-37-generic (= 3.16.0-37.51) but 3.16.0-37.51~14.04.1 is installed linux-signed-image-3.16.0-38-generic : Depends: linux-image-3.16.0-38-generic (= 3.16.0-38.52) but 3.16.0-38.52~14.04.1 is installed E: Unmet dependencies. Try using -f. The package system is broken Check if you are using third-party repositories. If so, disable them, because they are a common source of problems. Furthermore, run the following command in a Terminal: apt-get install -f The following packages have unmet dependencies: linux-signed-image-3.16.0-33-generic: Depends: linux-image-3.16.0-33-generic (= 3.16.0-33.44) but 3.16.0-33.44~14.04.1 is installed Depends: linux-image-extra-3.16.0-33-generic (= 3.16.0-33.44) but 3.16.0-33.44 is installed linux-signed-image-3.16.0-34-generic: Depends: linux-image-3.16.0-34-generic (= 3.16.0-34.47) but 3.16.0-34.47~14.04.1 is installed Depends: linux-image-extra-3.16.0-34-generic (= 3.16.0-34.47) but 3.16.0-34.47 is installed linux-signed-image-3.16.0-36-generic: Depends: linux-image-3.16.0-36-generic (= 3.16.0-36.48) but 3.16.0-36.48~14.04.1 is installed Depends: linux-image-extra-3.16.0-36-generic (= 3.16.0-36.48) but 3.16.0-36.48 is installed linux-signed-image-3.16.0-37-generic: Depends: linux-image-3.16.0-37-generic (= 3.16.0-37.51) but 3.16.0-37.51~14.04.1 is installed Depends: linux-image-extra-3.16.0-37-generic (= 3.16.0-37.51) but 3.16.0-37.51 is installed linux-signed-image-3.16.0-38-generic: Depends: linux-image-3.16.0-38-generic (= 3.16.0-38.52) but 3.16.0-38.52~14.04.1 is installed Depends: linux-image-extra-3.16.0-38-generic (= 3.16.0-38.52) but 3.16.0-38.52 is installed ProblemType: Package DistroRelease: Ubuntu 14.10 Package: linux-image-extra-3.16.0-37-generic 3.16.0-37.51 ProcVersionSignature: Ubuntu 3.16.0-38.52~14.04.1-generic 3.16.7-ckt10 Uname: Linux 3.16.0-38-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.7-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: el 4439 F pulseaudio /dev/snd/controlC0: el 4439 F pulseaudio Date: Thu May 14 00:59:26 2015 DuplicateSignature: package:linux-image-extra-3.16.0-37-generic:3.16.0-37.51:run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=33901e26-85c5-4b64-ad1f-ae7940b138d4 InstallationDate: Installed on 2015-03-16 (59 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: Dell Inc. Latitude E6420 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-38-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-extra-3.16.0-37-generic 3.16.0-37.51 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: Upgraded to utopic on 2015-05-14 (0 days ago) dmi.bios.date: 10/18/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: A08 dmi.board.name: 032T9K dmi.board.vendor: Dell Inc. dmi.board.version: A02 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA08:bd10/18/2011:svnDellInc.:pnLatitudeE6420:pvr01:rvnDellInc.:rn032T9K:rvrA02:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6420 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check utopic -
[Touch-packages] [Bug 1201528] Re: [INTEL DP55WG, Realtek ALC889] - Audio Playback Unavailable
** Attachment added: "pulseverbose.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201528/+attachment/4397831/+files/pulseverbose.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201528 Title: [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in alsa-driver source package in Raring: Won't Fix Status in linux source package in Raring: Invalid Status in alsa-driver source package in Saucy: Won't Fix Status in linux source package in Saucy: Won't Fix Status in alsa-driver source package in Vivid: Confirmed Status in linux source package in Vivid: Confirmed Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita 13188 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b InstallationDate: Installed on 2014-05-11 (366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Tags: vivid vivid vivid vivid Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-11 (61 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-4
[Touch-packages] [Bug 1201528] Re: [INTEL DP55WG, Realtek ALC889] - Audio Playback Unavailable
As requested, tested kernel 4.1.0-040100rc3-generic. Audio playback is still lost. See attached verbose output from pulseaudio, including the line that makes all sound go away: (2356.093| 0.000) D: [alsa-sink-ALC889 Analog] protocol-native.c: max_request changed, trying to update from 70272 to 71292. (2356.093| 0.000) D: [alsa-sink-ALC889 Analog] protocol-native.c: Notifying client about increased tlength (2356.093| 0.000) D: [alsa-sink-ALC889 Analog] alsa-sink.c: Latency set to 341.33ms (2356.093| 0.000) D: [alsa-sink-ALC889 Analog] alsa-sink.c: hwbuf_unused=4 (2356.093| 0.000) D: [alsa-sink-ALC889 Analog] alsa-sink.c: setting avail_min=737 (2356.268| 0.175) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Underrun! (2356.268| 0.000) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Increasing wakeup watermark to 331.31 ms (2356.447| 0.178) I: [alsa-sink-ALC889 Analog] alsa-sink.c: Underrun! ** Tags added: kernel-bug-exists-upstream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201528 Title: [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in alsa-driver source package in Raring: Won't Fix Status in linux source package in Raring: Invalid Status in alsa-driver source package in Saucy: Won't Fix Status in linux source package in Saucy: Won't Fix Status in alsa-driver source package in Vivid: Confirmed Status in linux source package in Vivid: Confirmed Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita 13188 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b InstallationDate: Installed on 2014-05-11 (366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersion
[Touch-packages] [Bug 1201528] Re: [INTEL DP55WG, Realtek ALC889] - Audio Playback Unavailable
** Attachment added: "pulseverbose.log.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1201528/+attachment/4397835/+files/pulseverbose.log.gz ** Changed in: alsa-driver (Ubuntu) Status: Expired => Confirmed ** Changed in: alsa-driver (Ubuntu Vivid) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1201528 Title: [INTEL DP55WG,Realtek ALC889] - Audio Playback Unavailable Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in alsa-driver source package in Raring: Won't Fix Status in linux source package in Raring: Invalid Status in alsa-driver source package in Saucy: Won't Fix Status in linux source package in Saucy: Won't Fix Status in alsa-driver source package in Vivid: Confirmed Status in linux source package in Vivid: Confirmed Bug description: This is a fresh upgrade to raring. During the weekend, I updated from precise to quantal, and from there to raring. I did not use sound while the system was in quantal, so no idea if the bug was present there as well. The symptom is: * after some period of sound usage, playback stops working What I mean with sound usage is: I tried having a meeting with: mumble, skype, and google hangout, and in all three cases, audio input/outout will work just fine for ~5 minutes, and the playback just dies (people tell me they keep listening to me, so mic works fine). The only way to solve this is by rebooting. After one of the reboots, I was able to play a 20 minute video with mplayer with no further issue. Then opened skype and after ~3-5 minute talk, audio playback died again. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.8.0-26.38-generic 3.8.13.2 Uname: Linux 3.8.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita2627 F pulseaudio Date: Mon Jul 15 14:40:20 2013 InstallationDate: Installed on 2011-12-20 (572 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (2029.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID failed Symptom_AlsaPlaybackTestStderr: W r i t e e r r o r : - 5 , I n p u t / o u t p u t e r r o r x r u n _ r e c o v e r y f a i l e d : - 5 , I n p u t / o u t p u t e r r o r T r a n s f e r f a i l e d : O p e r a t i o n n o t p e r m i t t e d Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_Type: None of the above Title: [, Realtek ALC889, Green Headphone Out, Front] Playback problem UpgradeStatus: Upgraded to raring on 2013-07-13 (2 days ago) dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.3206.2009.0805.1855:bd08/05/2009:svn:pn:pvr:rvnIntelCorporation:rnDP55WG:rvrAAE57269-404:cvn:ct2:cvr: --- ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nessita 13188 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 15.04 HibernationDevice: RESUME=UUID=bd987ac2-eb4b-43e7-881b-4cf2b5078e4b InstallationDate: Installed on 2014-05-11 (366 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-16-generic root=UUID=e91bd3a4-787b-404b-9f19-aa6dcbe707b0 ro quiet splash ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 RelatedPackageVersions: linux-restricted-modules-3.19.0-16-generic N/A linux-backports-modules-3.19.0-16-generic N/A linux-firmware 1.143 RfKill: Tags: vivid vivid vivid vivid Uname: Linux 3.19.0-16-generic x86_64 UpgradeStatus: Upgraded to vivid on 2015-03-11 (61 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/05/2009 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.3206.2009.0805.1855 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WG dmi.board.vendor: Intel Corporation dmi.board.version: AAE57269-404 dmi
[Touch-packages] [Bug 1204470] Re: [Popover] Positioning doesn't work correctly for rotated items
** Tags added: orientation rotation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1204470 Title: [Popover] Positioning doesn't work correctly for rotated items Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: The Popover's position mechanism does not consider Item's rotation. Check out the attached code example. -> run "qmlscene popovertest.qml" -> long-press the button => The Popover shows up as expected -> close the Popover by clicking somewhere outside -> click the button => The button rotates -> long-press the button again => The Popover shows up hiding the button To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1204470/+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 1439102] Re: Dialogs are rotated incorrectly if root item is not a MainView
** Tags added: orientation rotation -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1439102 Title: Dialogs are rotated incorrectly if root item is not a MainView Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Please test the attached program. When in portrait mode, the dialog will appear with the correct orientation, but when the device is rotated to landscape, the dialog rotates 180 degrees from its original position. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1439102/+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 1332233] Re: [HDA-Intel - HDA Intel PCH, recording] Recording problem
I'm completely lost here, sorry. How can I figure this out, and if I do how does it help? I've tried several headsets, but the one I use most often with everything else is just a set of Samsung earbuds much like these: http://www.samsung.com/us/mobile/cell-phones-accessories/EO-HS1303BEST1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1332233 Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: I opened a thread in the forums first. For reference: http://ubuntuforums.org/showthread.php?t=2230136&p=13052352 The basic issue is that I got a new Asus S400CA laptop. It has a combo jack for headphones/mic (like phones do now). With Windows 8, the headset worked fine (both input and output through the one jack). With Ubuntu 14.04 it works for output, but not for input. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: acampbell F pulseaudio acampbell 23019 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 19 12:05:57 2014 InstallationDate: Installed on 2014-06-14 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S400CA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S400CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS400CA.206:bd11/28/2012:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: S400CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1332233/+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 1452346] Re: please drop build-dependency on g++-4.9
** Branch linked: lp:~michihenning/unity-scopes-api/gcc-version -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1452346 Title: please drop build-dependency on g++-4.9 Status in unity-scopes-api package in Ubuntu: In Progress Bug description: The unity-scopes-api package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1452346/+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 1448834] Re: mouse battery not shown after upgrade
The attachment "[PATCH] rules: support Logitech Unifying in Linux 3.19" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade Status in gnome-power-manager package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the battery level in my wireless logitech mouse. However after upgrading to 15.04 the mouse battery status is not shown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xfce4-power-manager 1.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 26 19:49:19 2015 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1448834/+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 1401141] Re: DHCP server does not work for IPoIB (Infiniband)
** Changed in: isc-dhcp (Ubuntu Trusty) Assignee: (unassigned) => Rafael David Tinoco (inaddy) ** Changed in: isc-dhcp (Ubuntu Utopic) Assignee: (unassigned) => Rafael David Tinoco (inaddy) ** Changed in: isc-dhcp (Ubuntu Vivid) Assignee: (unassigned) => Rafael David Tinoco (inaddy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1401141 Title: DHCP server does not work for IPoIB (Infiniband) Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Confirmed Status in isc-dhcp source package in Utopic: Confirmed Status in isc-dhcp source package in Vivid: Confirmed Bug description: [Impact] * DHCP for InfiniBand IPoIB does not work currently. * After providing missing GPXE patch it had problems (by Mellanox tests). * IPoIB patches from Fedora project (out-of-upstream-tree) were outdated. [Test Case] * To have IPoIB devices (2 if possible) * Try to acquire IP using either DHCPv4 or DHCPv6 [Regression Potential] * DHCP for InfiniBand was not working * Based on already implemented code (Fedora) * Mellanox has tested it [Other Info] Original BUG description: Release: Ubuntu 14.04.1 LTS Version: 4.2.4-7ubuntu12 The current DHCP package in Ubuntu can't handle IPoIB clients. For IB, Mellanox uses IPoIB, which is “Eth emulator” for the control path. DHCP is not working in this mode without a patch for DHCP server. ISC-DHCP-SERVER Missing GPXE patch. After applying GPXE patch only we faced the following problems: After apply 1. dhcp ipoib, does not write in the log on which interface the dhcp work upon when starting the dhcp server using “/etc/init.d/isc-dhcp-server start” we don’t see the line that tells on which interfaces the dhcpd is listening on the /var/log/syslog when running it with “dhcpd –d” command – we do see it. 2. dhcp ipoib ipv6, it did not provide ip6 when we start 2 ib interfaces in a parallel using the following setup: HOST_A: acting as a dhcp server, listening on one of its ipoib (ib0) interfaces. HOST_B: running dhcp clients on two ipoib interfaces (ib1, ib2) ib1 and ib2 are two ports onf the same HCA both interfaces are configured in /etc/interfaces such as: auto ib1 iface ib1 inet6 dhcp both interfaces are configured in /etc/dhcp/dhclient.conf with their dhcp-client-identifier Ib0@HOST_A, Ib1@HOST_B and Ib2@HOST_B are connected to an infiniband switch. We are running on the client (HOST_B) the following: $ ifup ib1 -> ib1 get configured as expected but then when we run on the other interface: $ ifup ib2 -> ib2 get configured, but ib1 is losing its configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141/+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 1350393] Re: Recent accountsservice update causes login window to hang
Right, Derek. Actually, shouldn't the LDAP issue you described be reported as a separate libnss-ldap bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Incomplete Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1452346] Re: please drop build-dependency on g++-4.9
** Changed in: unity-scopes-api (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1452346 Title: please drop build-dependency on g++-4.9 Status in unity-scopes-api package in Ubuntu: In Progress Bug description: The unity-scopes-api package currently has a build-dependency on g++-4.9. This build-dependency is present because of the recommendations on https://wiki.ubuntu.com/cpp-11 about handling of C++11. The C++11 ABI has now stabilized in gcc as of gcc 5; however, before we can switch to gcc 5, we first need to be able to do rebuild tests of the archive against this compiler. To facilitate this, please drop the build-dependency on g++-4.9 from the package in wily. 4.9 will remain the default until all transition issues have been identified, so there is no risk of accidental ABI breakage here anymore. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1452346/+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 1350393] Re: Recent accountsservice update causes login window to hang
@Gunnar, 0.6.35-0ubuntu7.2 may be improve performance in some cases, but it does nothing to avoid the infinite hang that I characterized in comment #4. The fact that it calls user_language_validate() just once in the context of an LDAP user when the LDAP client isn't fully ready will cause accounts-daemon to fail completely. Therefore, your revised patch should make no difference to the failure mode I described. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Incomplete Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1455274] [NEW] no wireless network detected after turning wifi off and on a few times
Public bug reported: This began when I upgraded to Ubuntu 15.04. My workplace is in a place in which the wifi signal from my network is weak. So, sometimes, it loses the signal. A quick solution that sometimes works is turning (either through hardware or gui) the wifi off and back on again. However, it seems that when I do it a couple of times, no network will be detected anymore (not even my neighbor's, which is strong here). Rebooting will turn things back to normal. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 14 20:41:02 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-03-14 (61 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.0.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.12 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-12 (2 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 Net-Virtua-360 d441223d-806f-46ab-b26e-6568883e3580 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- wmx0wimax unmanaged/org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- 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/1455274 Title: no wireless network detected after turning wifi off and on a few times Status in network-manager package in Ubuntu: New Bug description: This began when I upgraded to Ubuntu 15.04. My workplace is in a place in which the wifi signal from my network is weak. So, sometimes, it loses the signal. A quick solution that sometimes works is turning (either through hardware or gui) the wifi off and back on again. However, it seems that when I do it a couple of times, no network will be detected anymore (not even my neighbor's, which is strong here). Rebooting will turn things back to normal. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 14 20:41:02 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2015-03-14 (61 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) IpRoute: default via 192.168.0.1 dev wlan0 proto static metric 1024 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.12 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2015-05-12 (2 days ago) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 Net-Virtua-360 d441223d-806f-46ab-b26e-6568883e3580 /org/freedesktop/NetworkManager/ActiveConnection/0 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManag
[Touch-packages] [Bug 1453282] Re: [Neither headphones nor speakers are displayed under "All Settings"->Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all
Node 0x2d [Pin Complex] wcaps 0x400701: Stereo Digital Control: name="HDMI Phantom Jack", index=0, device=0 Pincap 0x0010: OUT Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI Conn = Digital, Color = Unknown DefAssociation = 0xf, Sequence = 0x0 Pin-ctls: 0x40: OUT Power states: D0 D1 D2 D3 Power: setting=D0, actual=D0 Connection: 1 0x0e is this internal spdif conecctor ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1453282 Title: [Neither headphones nor speakers are displayed under "All Settings"->Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: Incomplete Bug description: The motherboard speakers and microphone aren't listed under "All Settings"->Sound UNLESS I unplug them and then plug them back in. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 11102 F pulseaudio /dev/snd/pcmC1D0c: username 11102 F...m pulseaudio /dev/snd/controlC1: username 11102 F pulseaudio /dev/snd/timer: username 11102 f pulseaudio CurrentDesktop: Unity Date: Fri May 8 16:09:24 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-07 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., VIA VT1718S, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H55M Pro dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/06/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1453282/+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 1401141] Re: DHCP server does not work for IPoIB (Infiniband)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: isc-dhcp (Ubuntu Utopic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1401141 Title: DHCP server does not work for IPoIB (Infiniband) Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Confirmed Status in isc-dhcp source package in Utopic: Confirmed Status in isc-dhcp source package in Vivid: Confirmed Bug description: [Impact] * DHCP for InfiniBand IPoIB does not work currently. * After providing missing GPXE patch it had problems (by Mellanox tests). * IPoIB patches from Fedora project (out-of-upstream-tree) were outdated. [Test Case] * To have IPoIB devices (2 if possible) * Try to acquire IP using either DHCPv4 or DHCPv6 [Regression Potential] * DHCP for InfiniBand was not working * Based on already implemented code (Fedora) * Mellanox has tested it [Other Info] Original BUG description: Release: Ubuntu 14.04.1 LTS Version: 4.2.4-7ubuntu12 The current DHCP package in Ubuntu can't handle IPoIB clients. For IB, Mellanox uses IPoIB, which is “Eth emulator” for the control path. DHCP is not working in this mode without a patch for DHCP server. ISC-DHCP-SERVER Missing GPXE patch. After applying GPXE patch only we faced the following problems: After apply 1. dhcp ipoib, does not write in the log on which interface the dhcp work upon when starting the dhcp server using “/etc/init.d/isc-dhcp-server start” we don’t see the line that tells on which interfaces the dhcpd is listening on the /var/log/syslog when running it with “dhcpd –d” command – we do see it. 2. dhcp ipoib ipv6, it did not provide ip6 when we start 2 ib interfaces in a parallel using the following setup: HOST_A: acting as a dhcp server, listening on one of its ipoib (ib0) interfaces. HOST_B: running dhcp clients on two ipoib interfaces (ib1, ib2) ib1 and ib2 are two ports onf the same HCA both interfaces are configured in /etc/interfaces such as: auto ib1 iface ib1 inet6 dhcp both interfaces are configured in /etc/dhcp/dhclient.conf with their dhcp-client-identifier Ib0@HOST_A, Ib1@HOST_B and Ib2@HOST_B are connected to an infiniband switch. We are running on the client (HOST_B) the following: $ ifup ib1 -> ib1 get configured as expected but then when we run on the other interface: $ ifup ib2 -> ib2 get configured, but ib1 is losing its configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141/+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 1451533] Re: python-docutils fails to build in trusty with python 2.7.9
** Changed in: python2.7 (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1451533 Title: python-docutils fails to build in trusty with python 2.7.9 Status in Python: Fix Released Status in python2.7 package in Ubuntu: Fix Released Status in python2.7 package in Debian: Fix Released Bug description: seen in a test rebuild with python 2.7.9 https://launchpad.net/ubuntu/+archive/test-rebuild-20150317/+build/7080449 == ERROR: test_invalid_raw_xml (test_writers.test_docutils_xml.DocutilsXMLTestCase) -- Traceback (most recent call last): File "/build/buildd/python-docutils-0.11/test/test_writers/test_docutils_xml.py", line 181, in test_invalid_raw_xml result = publish_xml(settings, invalid_raw_xml_source) File "/build/buildd/python-docutils-0.11/test/test_writers/test_docutils_xml.py", line 127, in publish_xml settings_overrides=settings) File "/build/buildd/python-docutils-0.11/build/py2/docutils/core.py", line 414, in publish_string enable_exit_status=enable_exit_status) File "/build/buildd/python-docutils-0.11/build/py2/docutils/core.py", line 662, in publish_programmatically output = pub.publish(enable_exit_status=enable_exit_status) File "/build/buildd/python-docutils-0.11/build/py2/docutils/core.py", line 219, in publish output = self.writer.write(self.document, self.destination) File "/build/buildd/python-docutils-0.11/build/py2/docutils/writers/__init__.py", line 80, in write self.translate() File "/build/buildd/python-docutils-0.11/build/py2/docutils/writers/docutils_xml.py", line 74, in translate self.document.walkabout(visitor) File "/build/buildd/python-docutils-0.11/build/py2/docutils/nodes.py", line 174, in walkabout if child.walkabout(visitor): File "/build/buildd/python-docutils-0.11/build/py2/docutils/nodes.py", line 174, in walkabout if child.walkabout(visitor): File "/build/buildd/python-docutils-0.11/build/py2/docutils/nodes.py", line 166, in walkabout visitor.dispatch_visit(self) File "/build/buildd/python-docutils-0.11/build/py2/docutils/nodes.py", line 1882, in dispatch_visit return method(node) File "/build/buildd/python-docutils-0.11/build/py2/docutils/writers/docutils_xml.py", line 184, in visit_raw col_num, line_num, node.astext()) TypeError: %d format: a number is required, not NoneType -- Ran 1239 tests in 6.543s FAILED (errors=1) Elapsed time: 7.075 seconds make: *** [build-stamp] Error 123 To manage notifications about this bug go to: https://bugs.launchpad.net/python/+bug/1451533/+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 1401141] Re: DHCP server does not work for IPoIB (Infiniband)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: isc-dhcp (Ubuntu Trusty) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1401141 Title: DHCP server does not work for IPoIB (Infiniband) Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Confirmed Status in isc-dhcp source package in Utopic: Confirmed Status in isc-dhcp source package in Vivid: Confirmed Bug description: [Impact] * DHCP for InfiniBand IPoIB does not work currently. * After providing missing GPXE patch it had problems (by Mellanox tests). * IPoIB patches from Fedora project (out-of-upstream-tree) were outdated. [Test Case] * To have IPoIB devices (2 if possible) * Try to acquire IP using either DHCPv4 or DHCPv6 [Regression Potential] * DHCP for InfiniBand was not working * Based on already implemented code (Fedora) * Mellanox has tested it [Other Info] Original BUG description: Release: Ubuntu 14.04.1 LTS Version: 4.2.4-7ubuntu12 The current DHCP package in Ubuntu can't handle IPoIB clients. For IB, Mellanox uses IPoIB, which is “Eth emulator” for the control path. DHCP is not working in this mode without a patch for DHCP server. ISC-DHCP-SERVER Missing GPXE patch. After applying GPXE patch only we faced the following problems: After apply 1. dhcp ipoib, does not write in the log on which interface the dhcp work upon when starting the dhcp server using “/etc/init.d/isc-dhcp-server start” we don’t see the line that tells on which interfaces the dhcpd is listening on the /var/log/syslog when running it with “dhcpd –d” command – we do see it. 2. dhcp ipoib ipv6, it did not provide ip6 when we start 2 ib interfaces in a parallel using the following setup: HOST_A: acting as a dhcp server, listening on one of its ipoib (ib0) interfaces. HOST_B: running dhcp clients on two ipoib interfaces (ib1, ib2) ib1 and ib2 are two ports onf the same HCA both interfaces are configured in /etc/interfaces such as: auto ib1 iface ib1 inet6 dhcp both interfaces are configured in /etc/dhcp/dhclient.conf with their dhcp-client-identifier Ib0@HOST_A, Ib1@HOST_B and Ib2@HOST_B are connected to an infiniband switch. We are running on the client (HOST_B) the following: $ ifup ib1 -> ib1 get configured as expected but then when we run on the other interface: $ ifup ib2 -> ib2 get configured, but ib1 is losing its configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141/+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 1401141] Re: DHCP server does not work for IPoIB (Infiniband)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: isc-dhcp (Ubuntu Vivid) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu. https://bugs.launchpad.net/bugs/1401141 Title: DHCP server does not work for IPoIB (Infiniband) Status in isc-dhcp package in Ubuntu: Fix Released Status in isc-dhcp source package in Trusty: Confirmed Status in isc-dhcp source package in Utopic: Confirmed Status in isc-dhcp source package in Vivid: Confirmed Bug description: [Impact] * DHCP for InfiniBand IPoIB does not work currently. * After providing missing GPXE patch it had problems (by Mellanox tests). * IPoIB patches from Fedora project (out-of-upstream-tree) were outdated. [Test Case] * To have IPoIB devices (2 if possible) * Try to acquire IP using either DHCPv4 or DHCPv6 [Regression Potential] * DHCP for InfiniBand was not working * Based on already implemented code (Fedora) * Mellanox has tested it [Other Info] Original BUG description: Release: Ubuntu 14.04.1 LTS Version: 4.2.4-7ubuntu12 The current DHCP package in Ubuntu can't handle IPoIB clients. For IB, Mellanox uses IPoIB, which is “Eth emulator” for the control path. DHCP is not working in this mode without a patch for DHCP server. ISC-DHCP-SERVER Missing GPXE patch. After applying GPXE patch only we faced the following problems: After apply 1. dhcp ipoib, does not write in the log on which interface the dhcp work upon when starting the dhcp server using “/etc/init.d/isc-dhcp-server start” we don’t see the line that tells on which interfaces the dhcpd is listening on the /var/log/syslog when running it with “dhcpd –d” command – we do see it. 2. dhcp ipoib ipv6, it did not provide ip6 when we start 2 ib interfaces in a parallel using the following setup: HOST_A: acting as a dhcp server, listening on one of its ipoib (ib0) interfaces. HOST_B: running dhcp clients on two ipoib interfaces (ib1, ib2) ib1 and ib2 are two ports onf the same HCA both interfaces are configured in /etc/interfaces such as: auto ib1 iface ib1 inet6 dhcp both interfaces are configured in /etc/dhcp/dhclient.conf with their dhcp-client-identifier Ib0@HOST_A, Ib1@HOST_B and Ib2@HOST_B are connected to an infiniband switch. We are running on the client (HOST_B) the following: $ ifup ib1 -> ib1 get configured as expected but then when we run on the other interface: $ ifup ib2 -> ib2 get configured, but ib1 is losing its configuration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1401141/+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 1350393] Re: Recent accountsservice update causes login window to hang
This may be a duplicate of bug 996791. https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1350393 Title: Recent accountsservice update causes login window to hang Status in Light Display Manager: New Status in accountsservice package in Ubuntu: Incomplete Bug description: Hi, The recent 0.6.35-0ubuntu7.1 update (see https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1290785) seems to have removed the UID_MAX check, which could be used to hide users from the login window. In a large organization where many thousands of users are present on our systems, we relied on the UID_MAX setting in /etc/login.defs to prevent accounts-daemon from trying to frob all our accounts. accounts-daemon's performance is so poor, that not having the UID_MAX check causes lightdm to hang for 5-10mins while accounts-daemon tries to look for something in every users home folder. I've already done things like set the login window to require the user to enter their username and password rather than list all users, but the login window still hangs while accounts-daemon is doing its thing. The behavior I see, is: 1) just after boot, there's a black screen, right after the plymouth splash disappears, for 2-3 minutes before lightdm appears 2) You type a username into the username field and press 'Tab' 3) lightdm appears to hang for 5-10mins before the cursor moves to the password field. During this time, I see an accounts-daemon spawn for each user on the system, sequentially (in alphabetical order). Once the last user's accounts-daemon process finishes, the cursor moves to the password field. This not only happens on first boot, but every time a user logs out and the system returns to the login window. Any chance we can have the UID_MAX check back? Or some equivalent? This is causing a serious problem for us! Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1350393/+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 1453282] Re: [Neither headphones nor speakers are displayed under "All Settings"->Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all
Default sink name: alsa_output.pci-_00_1b.0.hdmi-stereo Default source name: alsa_input.usb-Auvitek_Auvitek_001-01-U0x5e10x400.iec958-stereo ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1453282 Title: [Neither headphones nor speakers are displayed under "All Settings"->Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: Incomplete Bug description: The motherboard speakers and microphone aren't listed under "All Settings"->Sound UNLESS I unplug them and then plug them back in. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 11102 F pulseaudio /dev/snd/pcmC1D0c: username 11102 F...m pulseaudio /dev/snd/controlC1: username 11102 F pulseaudio /dev/snd/timer: username 11102 f pulseaudio CurrentDesktop: Unity Date: Fri May 8 16:09:24 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-07 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., VIA VT1718S, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H55M Pro dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/06/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1453282/+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 996791] Re: Xubuntu 12.04 extremely slow login
I suspect that this bug is a duplicate of https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1350393 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/996791 Title: Xubuntu 12.04 extremely slow login Status in accountsservice package in Ubuntu: Confirmed Bug description: The core issue is that /usr/lib/accountsservice/accounts-daemon doesn't accept dbus messages on boot. The symptom to this problem is that, after successfulling entering your login information, the system takes about 85 seconds to boot. The real issue occuring is that /usr/lib/accountsservice/accounts- daemon isn't being started correctly by ligthdm. The accounts-daemon wont accept dbus requests, and so the dbus timeout is hit during boot. Before I start, here is a run down on my machine/setup: Intel I7. Xubuntu 12.04. Encrypted home drive. Running compiz. Enabling the log files on lightdm, the follow warnings are displayed (Notice the times): [+11.58s] DEBUG: Greeter quit [+36.60s] WARNING: Could not call SetXSession: Timeout was reached [+61.63s] WARNING: Could not call FindUserByName: Timeout was reached [+61.63s] DEBUG: Dropping privileges to uid 1000 [+61.63s] DEBUG: Restoring privileges [+86.65s] WARNING: Could not call FindUserByName: Timeout was reached If the /usr/lib/accountsservices/accounts-daemon is restarted, after the lightdm login screen is displayed, but before a login, then xfce will start immediately. Otherwise boot times take about 87 seconds. Also, it was found that the program d-feet, is unable to retrive valid methods from /usr/lib/accountsservices/accounts-daemon before it is restarted. After the deamon is restarted, all dbus methods are visuable and communicate correctly. For descussion on the problem, and a temporary fix, see the following thread: http://ubuntuforums.org/showthread.php?t=1970326 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/996791/+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 1427264] Re: using ecryptfs, creating frameworks fail to bind mount issues
** Changed in: schroot (Ubuntu) Assignee: (unassigned) => Tyler Hicks (tyhicks) ** Changed in: schroot (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1427264 Title: using ecryptfs, creating frameworks fail to bind mount issues Status in click package in Ubuntu: Triaged Status in schroot package in Ubuntu: In Progress Bug description: Using vivid creating framework fails for ecryptfs users, the issue is similar to bug #769595 The userdir is mounted in a way which makes unmounts fail "E: 10mount: umount: /var/lib/schroot/mount/click-ubuntu-sdk-14.10 -armhf-ec6aaf62-31e0-47e9-b2f8-73f0b038fb4d/home/user: target is busy E: 10mount: (In some cases useful info about processes that E: 10mount: use the device is found by lsof(8) or fuser(1).) " changing the fstab line to be "/home/user /home/user none rw,bind0 0" workarounds the issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1427264/+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 655835] Re: avahi-daemon consumes 100% CPU time after a period of networked Desktop use
I am seeing this in 15.04, fully updated. -- 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/655835 Title: avahi-daemon consumes 100% CPU time after a period of networked Desktop use Status in avahi package in Ubuntu: Confirmed Bug description: On Ubuntu 10.10 Release candidate, after using the machine for some time, the avahi-daemon consistently jumps to 100% CPU usage. It is a networked machine but I haven't made any extensive tests whether this problem also occurs when offline. avahi-daemon: 0.6.27-2ubuntu3 ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: avahi-daemon 0.6.27-2ubuntu3 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic-pae 2.6.35.4 Uname: Linux 2.6.35-22-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Wed Oct 6 12:40:32 2010 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate i386 (20100928) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: avahi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/655835/+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 1332233] Re: [HDA-Intel - HDA Intel PCH, recording] Recording problem
Node 0x1e [Audio Selector] wcaps 0x300501: Stereo Power states: D0 D1 D2 D3 Power: setting=D0, actual=D0 Connection: 5 0x2b 0x2a 0x29 0x21 0x30* -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1332233 Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: I opened a thread in the forums first. For reference: http://ubuntuforums.org/showthread.php?t=2230136&p=13052352 The basic issue is that I got a new Asus S400CA laptop. It has a combo jack for headphones/mic (like phones do now). With Windows 8, the headset worked fine (both input and output through the one jack). With Ubuntu 14.04 it works for output, but not for input. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: acampbell F pulseaudio acampbell 23019 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 19 12:05:57 2014 InstallationDate: Installed on 2014-06-14 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S400CA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S400CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS400CA.206:bd11/28/2012:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: S400CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1332233/+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 1332233] Re: [HDA-Intel - HDA Intel PCH, recording] Recording problem
[4.671751] autoconfig: line_outs=1 (0x24/0x0/0x0/0x0/0x0) type:speaker [4.671756]speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [4.671758]hp_outs=1 (0x25/0x0/0x0/0x0/0x0) [4.671760]mono: mono_out=0x0 [4.671761]inputs: [4.671768] Mic=0x30 sys/class/sound/hwC0D0/init_pin_configs: 0x24 0x90170110 0x25 0x0221401f 0x28 0x422140f0 0x29 0x50a701f0 0x2a 0x418130f0 0x2b 0x41a190f0 0x2d 0x474411f0 0x30 0x90a601f0 0x33 0x501701f0 you need to find out the pin complex of the headset mic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1332233 Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: I opened a thread in the forums first. For reference: http://ubuntuforums.org/showthread.php?t=2230136&p=13052352 The basic issue is that I got a new Asus S400CA laptop. It has a combo jack for headphones/mic (like phones do now). With Windows 8, the headset worked fine (both input and output through the one jack). With Ubuntu 14.04 it works for output, but not for input. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: acampbell F pulseaudio acampbell 23019 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 19 12:05:57 2014 InstallationDate: Installed on 2014-06-14 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S400CA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S400CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS400CA.206:bd11/28/2012:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: S400CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1332233/+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 1404247] Re: Vivid Wallpaper hashed
Wily Werewolf here, updated as of 14 may, boots normally, no Hashing. Reboot to 15.04, screen Hashed as usual. Reboot to Wily Werewolf, boots normally again, no Hashing. Wonder what next updates will do -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1404247 Title: Vivid Wallpaper hashed Status in xorg package in Ubuntu: Incomplete Bug description: After update this week wallpaper hashed. See attachment. Settings Appearance change wallpaper to a different wallpaper O.K., then back to original restores proper image. Reboot, wallpaper hashed again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15-0ubuntu3 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 Date: Fri Dec 19 08:43:46 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkCentre M6258 [17aa:3048] Subsystem: Lenovo Device [17aa:3048] InstallationDate: Installed on 2014-11-25 (23 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20141125) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=285177a7-5498-4980-a3f2-7e3f655ca886 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Dec 19 08:43:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.2.901-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1404247/+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 1455157] Re: Xorg freeze
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1455157 Title: Xorg freeze Status in xorg package in Ubuntu: New Bug description: flashplayar+firefox=crash x.org problem in flashplugin his not stable . ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic i686 NonfreeKernelModules: fglrx .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.10 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: X-Cinnamon Date: Thu May 14 19:59:19 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: fglrx, 14.200, 3.13.0-49-generic, i686: installed fglrx, 14.200, 3.13.0-51-generic, i686: installed fglrx, 14.200, 3.13.0-52-generic, i686: installed ExtraDebuggingInterest: I just need to know a workaround GpuHangFrequency: This is the first time GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde XT [Radeon HD 7770/8760 / R7 250X] [1002:683d] (prog-if 00 [VGA controller]) Subsystem: PC Partner Limited / Sapphire Technology Device [174b:e244] InstallationDate: Installed on 2015-04-12 (31 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=32a7f783-bc9a-43e1-b5a1-22dd6c7c1df5 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/09/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F6 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: F2A88X-D3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF6:bd04/09/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88X-D3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.fglrx-installer: fglrx-installer N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu May 14 19:56:59 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputA4TECH USB DeviceKEYBOARD, id 8 inputA4TECH USB DeviceMOUSE, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.errors: open /dev/dri/card0: No such file or directory AIGLX error: failed to open /usr/X11R6/lib/modules/dri/fglrx_dri.so, error[/usr/X11R6/lib/modules/dri/fglrx_dri.so: cannot open shared object file: No such file or directory] xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: fglrx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1455157/+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 1453282] Re: [Neither headphones nor speakers are displayed under "All Settings"->Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1453282 Title: [Neither headphones nor speakers are displayed under "All Settings"->Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all Status in pulseaudio package in Ubuntu: Confirmed Bug description: The motherboard speakers and microphone aren't listed under "All Settings"->Sound UNLESS I unplug them and then plug them back in. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu6 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: username 11102 F pulseaudio /dev/snd/pcmC1D0c: username 11102 F...m pulseaudio /dev/snd/controlC1: username 11102 F pulseaudio /dev/snd/timer: username 11102 f pulseaudio CurrentDesktop: Unity Date: Fri May 8 16:09:24 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-05-07 (1 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful Symptom_Card: Built-in Audio - HDA Intel MID Symptom_Jack: Green Headphone Out, Front Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [To Be Filled By O.E.M., VIA VT1718S, Green Headphone Out, Front] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P2.20 dmi.board.name: H55M Pro dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/06/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1453282/+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 1450579] Re: Sound muted on login screen at startup
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1450579 Title: Sound muted on login screen at startup Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have recently found that after upgrading from Ubuntu 14.10 to Ubuntu 15.04 that on at the login screen at startup (not on suspend) that the sound appears muted (including the little thing in the notifications area), so I am not able to hear that nice drum thing when Ubuntu gets to the login screen, but once I have successfully signed in, my sound level goes back to what it was before I last shutdown. And as I am not able to change this, and not able then to have any sound before logging in, I thought that I should report this as a bug, although when I first upgraded, this did not happen, but maybe the second or third time I logged in it started, as has been so ever since. --- OS Information: Description: Ubuntu 15.04 Release: 15.04 Package Information: pulseaudio: Installed: 1:6.0-0ubuntu6 Candidate: 1:6.0-0ubuntu6 Version table: *** 1:6.0-0ubuntu6 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1450579/+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 1296425] Update Released
The verification of the Stable Release Update for ubuntu-drivers-common has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1296425 Title: pulseaudio is started twice - effectively making device management impossible. Status in alsa-plugins package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in alsa-plugins source package in Trusty: Invalid Status in ubuntu-drivers-common source package in Trusty: Fix Released Bug description: [Impact] On the current kubuntu 14.04 live-image (and for a 13.10 upgraded system) pulseaudio is running twice. This makes attaching/deattaching of usb-headset and other stuff impossible because the two instances fight over the events. The fix is https://github.com/tseliot/ubuntu-drivers- common/commit/5fe70ce1 [Test Case] To reproduce just boot up the current image and do a "ps -ef | grep pulseaudio" [Regression Potential] Low. This fix has been out for many months in 14.10, and only changes the environment that "aplay -l" gets called with. In the absolutely worst case if this goes totally wrong, ubuntu-drivers would stop to detect sl-modem capable soft-modems. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6 Uname: Linux 3.13.0-19-lowlatency i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sgh2336 F pulseaudio sgh2796 F pulseaudio /dev/snd/controlC0: sgh2336 F pulseaudio sgh2796 F pulseaudio CurrentDesktop: KDE Date: Sun Mar 23 22:36:50 2014 InstallationDate: Installed on 2013-12-24 (89 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+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 1296425] Re: pulseaudio is started twice - effectively making device management impossible.
This bug was fixed in the package ubuntu-drivers-common - 1:0.2.91.9 --- ubuntu-drivers-common (1:0.2.91.9) trusty-proposed; urgency=medium * sl-modem plugin: Keep environment for aplay, just ensure it's using the C locale. This avoids staring pulseaudio twice and causing races for attaching devices to pulseaudio. (LP: #1296425) ubuntu-drivers-common (1:0.2.91.8) trusty-proposed; urgency=medium * gpu-manager.c: - Refine checks for blacklisted modules, so that we don't end up catching false positives (LP: #1376966). Thanks to Pär Lindfors for the patch. -- Martin PittMon, 05 Jan 2015 17:27:53 +0100 ** Changed in: ubuntu-drivers-common (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1296425 Title: pulseaudio is started twice - effectively making device management impossible. Status in alsa-plugins package in Ubuntu: Invalid Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in alsa-plugins source package in Trusty: Invalid Status in ubuntu-drivers-common source package in Trusty: Fix Released Bug description: [Impact] On the current kubuntu 14.04 live-image (and for a 13.10 upgraded system) pulseaudio is running twice. This makes attaching/deattaching of usb-headset and other stuff impossible because the two instances fight over the events. The fix is https://github.com/tseliot/ubuntu-drivers- common/commit/5fe70ce1 [Test Case] To reproduce just boot up the current image and do a "ps -ef | grep pulseaudio" [Regression Potential] Low. This fix has been out for many months in 14.10, and only changes the environment that "aplay -l" gets called with. In the absolutely worst case if this goes totally wrong, ubuntu-drivers would stop to detect sl-modem capable soft-modems. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu10 ProcVersionSignature: Ubuntu 3.13.0-19.39-lowlatency 3.13.6 Uname: Linux 3.13.0-19-lowlatency i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sgh2336 F pulseaudio sgh2796 F pulseaudio /dev/snd/controlC0: sgh2336 F pulseaudio sgh2796 F pulseaudio CurrentDesktop: KDE Date: Sun Mar 23 22:36:50 2014 InstallationDate: Installed on 2013-12-24 (89 days ago) InstallationMedia: Kubuntu 14.04 LTS "Trusty Tahr" - Alpha i386 (20131224) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/02/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G7ET31WW (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 2356GCG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG7ET31WW(1.13):bd07/02/2012:svnLENOVO:pn2356GCG:pvrThinkPadT430s:rvnLENOVO:rn2356GCG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 2356GCG dmi.product.version: ThinkPad T430s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/1296425/+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 1382861] Re: Auto brightness toggle sometimes doesn't appear in power indicator
** Branch linked: lp:~charlesk/indicator-power/lp-1382861-fix-menu- creation-test -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1382861 Title: Auto brightness toggle sometimes doesn't appear in power indicator Status in the base for Ubuntu mobile products: Confirmed Status in indicator-power package in Ubuntu: Confirmed Bug description: On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto brightness toggle is sometimes missing in the power indicator. Sometimes everything is fine and sometimes it's simply not there. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1382861/+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 1451613] Re: Unity/compiz crashes when locking screen
I also have the same problem. ** Also affects: unity Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1451613 Title: Unity/compiz crashes when locking screen Status in Unity: New Status in unity package in Ubuntu: Confirmed Bug description: Since a recent update (around April 29th), sometimes (approximately once a day) when I lock my computer screen (CTRL+L or using system menu) the computer freeze for a while (2 to 30 seconds) before showing the login screen. Then when I try to unlock the screen I need to enter my password twice (with no error message after the first try). Once logged in, all applications are closed. Uptime is still running (since no reboot) and services too (with no interruption). Looking at the apport.log file (see attached) it seems that when I try to lock the screen, compiz crashes. I've attached the compiz crash file too (_usr_bin_compiz.1000.crash) but without the 100Mo data of base64 core dumb… I'm using Ubuntu 14.04 AMD64. Graphics drivers: nvidia-331.113 (tested) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1451613/+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 1332233] Re: [HDA-Intel - HDA Intel PCH, recording] Recording problem
It's been almost a year. I'm now on 15.04, same laptop, same issue. Here is my most current Alsa Info: http://www.alsa- project.org/db/?f=b2d205e49d5a715e4504ec50d5797e1d9659ff10 I'm not sure how to tag this bug as affecting "Vivid" instead of just "trusty" but it's definitely still a problem. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1332233 Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem Status in alsa-driver package in Ubuntu: New Bug description: I opened a thread in the forums first. For reference: http://ubuntuforums.org/showthread.php?t=2230136&p=13052352 The basic issue is that I got a new Asus S400CA laptop. It has a combo jack for headphones/mic (like phones do now). With Windows 8, the headset worked fine (both input and output through the one jack). With Ubuntu 14.04 it works for output, but not for input. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: acampbell F pulseaudio acampbell 23019 F pulseaudio CurrentDesktop: Unity Date: Thu Jun 19 12:05:57 2014 InstallationDate: Installed on 2014-06-14 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Type: Only some of inputs are working Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/28/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: S400CA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: S400CA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrS400CA.206:bd11/28/2012:svnASUSTeKCOMPUTERINC.:pnS400CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnS400CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: S400CA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1332233/+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 1454776] Re: [SRU] New stable release 2.44.1
Hello Iain, or anyone else affected, Accepted glib2.0 into vivid-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.44.1-1ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: glib2.0 (Ubuntu Vivid) Status: In Progress => Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1454776 Title: [SRU] New stable release 2.44.1 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Vivid: Fix Committed Bug description: Upload this stable bugfix release glib2.0 (2.44.1-1) UNRELEASED; urgency=medium * New upstream release 2.44.1 + Improve the default application algorithm + Bump the number of children a GType can have + Various testsuite improvements -- Iain Lane Wed, 13 May 2015 17:27:56 +0100 This is a merge from unstable (wily is taking from experimental). It includes some other testsuite fixes. I think/hope they should be okay to SRU too. [ QA & regression potential ] Under the GNOME MRE, assume the bugs are fixed. Installl the update & use your system as normal. If we don't see any regressions either manually or on errors, we're good. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1454776/+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 1382861] Re: Auto brightness toggle sometimes doesn't appear in power indicator
** Branch linked: lp:~charlesk/indicator-datetime/lp-1382861-fix-menu- creation-test -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1382861 Title: Auto brightness toggle sometimes doesn't appear in power indicator Status in the base for Ubuntu mobile products: Confirmed Status in indicator-power package in Ubuntu: Confirmed Bug description: On build #5 in the ubuntu-touch/ubuntu-rtm/devel channel, the auto brightness toggle is sometimes missing in the power indicator. Sometimes everything is fine and sometimes it's simply not there. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1382861/+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 1437538] Re: Battery Applet appears in English with Gnome in Ubuntu 12.04
Help me please carry with it a month and you have not yet given any -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1437538 Title: Battery Applet appears in English with Gnome in Ubuntu 12.04 Status in indicator-power package in Ubuntu: Incomplete Bug description: Use Ubuntu 12.04 on a Toshiba NB500. I use the Gnome desktop environment, but I found a bug: The battery applet appears in English, but with Unity appears in Spanish, but I still use Gnome !. So I ask you traduzcais battery applet to Spanish. If you ask me I missing some information. a greeting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1437538/+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 1437377] Re: Upowerd eats 100% memory
Fixed in Ubuntu 15.04 Vivid. Ubuntu 14.04 Trusty is not fixed though. ** Changed in: upower (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1437377 Title: Upowerd eats 100% memory Status in upower package in Ubuntu: Fix Released Bug description: I'm having this issue since Ubuntu 14.04. Now I'm on 14.10. Gnome-shell 3.14.3 Kernel 3.16.0-29-generic x86_64 UPower client version 0.99.1 UPower daemon version 0.99.1 Almost every single day I have an issue with upowerd process(es). Suddenly upowerd process(es) eats 100% memory, system freezes due to memory lack. I have a 16GB of RAM and upowerd can eat ANY amount. I think I have seen similar problem reported while ago, unfortunately I cannot find it right now. If you find it please set this topic as duplicate. Anyway - I am looking for a solution. It's a nightmare getting my system freezed every day... Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1437377/+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 1432613] Re: Facebook and MSN messengers shutting down (third-party client access)
This bug was fixed in the package account-plugins - 0.12+14.10.20140924-0ubuntu2 --- account-plugins (0.12+14.10.20140924-0ubuntu2) utopic; urgency=medium [ Alberto Mardegan ] * Add required ResponseType parameter to Facebook plugin, move to 2.0 API. (LP: #1430694) * Remove non working IM services (LP: #1432613) [ Iain Lane ] * Add a NEWS entry. -- Alberto Mardegan Thu, 30 Apr 2015 11:24:02 +0100 ** Changed in: account-plugins (Ubuntu Utopic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1432613 Title: Facebook and MSN messengers shutting down (third-party client access) Status in Online Accounts: Account plugins: In Progress Status in Webapps Team Task Tracking Project: In Progress Status in account-plugins package in Ubuntu: Fix Committed Status in empathy package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in account-plugins source package in Trusty: Fix Released Status in empathy source package in Trusty: Fix Released Status in ubuntu-system-settings-online-accounts source package in Trusty: Won't Fix Status in account-plugins source package in Utopic: Fix Released Status in empathy source package in Utopic: Fix Released Status in ubuntu-system-settings-online-accounts source package in Utopic: Won't Fix Status in account-plugins source package in Vivid: Fix Released Status in empathy source package in Vivid: Fix Released Status in ubuntu-system-settings-online-accounts source package in Vivid: Won't Fix Bug description: [ Description ] Facebook messenger and Windows Live messenger don't work any more because Facebook & Microsoft removed third-party support for them. [ Fix & QA ] Stop supporting IM accounts for these clients. For both creation & continued use. Verify that if you add a WLM or FB account in online accounts, empathy doesn't try to connect to it. account-plugins-windows-live shouldn't be pulled in by default any more (check a trusty daily which is built with proposed). [ Regression potential ] This is a regression, in that we stop supporting some account types. We don't have a choice about this. [ Original description ] The march towards a future of silos carries on. https://developers.facebook.com/docs/chat - the XMPP gateway for Facebook will shut down on April 30. http://ismsndeadyet.com/ - Microsoft are removing MSN endpoints. I guess we need to correspondingly remove IM support for these services & SRU it back. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1432613/+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 1430694] Re: Update Facebook permissions to 2.0 API
This bug was fixed in the package account-plugins - 0.12+14.10.20140924-0ubuntu2 --- account-plugins (0.12+14.10.20140924-0ubuntu2) utopic; urgency=medium [ Alberto Mardegan ] * Add required ResponseType parameter to Facebook plugin, move to 2.0 API. (LP: #1430694) * Remove non working IM services (LP: #1432613) [ Iain Lane ] * Add a NEWS entry. -- Alberto Mardegan Thu, 30 Apr 2015 11:24:02 +0100 ** Changed in: account-plugins (Ubuntu Utopic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1430694 Title: Update Facebook permissions to 2.0 API Status in Online Accounts: Account plugins: In Progress Status in the base for Ubuntu mobile products: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in account-plugins source package in Trusty: Fix Released Status in account-plugins source package in Utopic: Fix Released Status in account-plugins package in Ubuntu RTM: Fix Released Bug description: The 1.0 API is being deprecated on April 30, 2015. [Impact] Depending on how facebook decides to handle the deprecation, there's the possibility that creating facebook accounts from Ubuntu Online Accounts will just stop working, if our OAuth request (which uses deprecated parameters) gets declined. [Test case] Until the deprecation actually takes place, we won't be able to reproduce the bug. According to the Facebook official documentation, the v1.0 API will stop working on April 30th, 2015: https://developers.facebook.com/docs/apps/changelog [Regression potential] Very low: the new Facebook v2.0 API is already active, and we've been using it in Vivid without issues. A quick smoke test (just create a Facebook account from the System Settings -> Online Accounts pane) is anyway advised, to be absolutely sure. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1430694/+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 1444958] Re: STC830:Brazos:br311p06: file(s) are deleted from the /tmp after each reboot on Ubuntu OS
I have the same issue. I would like to keep my tmp files for at least a month. It is a good place for me to save temporary files -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1444958 Title: STC830:Brazos:br311p06: file(s) are deleted from the /tmp after each reboot on Ubuntu OS Status in systemd package in Ubuntu: Triaged Status in systemd package in Debian: Confirmed Bug description: == Comment: #0 - Application Cdeadmin - 2015-04-16 01:55:24 == State: Open by: mpham on 14 April 2015 14:26:40 Problem Description: File(s) are deleted from the /tmp after each reboot on Ubuntu OS. Even after the modification of TMPTIME=-1 or infinite or 60 in /etc/default/rcS. Symtem Info: = ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu Vivid Vervet (development branch) \n \l Kernel Version: 3.19.0-10-generic HTX Version: htxubuntu-331 Host Name: br311p06.site Machine Serial No: IBM,02109D2E7 Machine Type/Model: IBM,9119-MHE System FW Level: FW830.00 (SC830_028) HMC: = brhmc4 (9.3.242.95) Transferring the defect to Linux team for further analysis. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1444958/+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 1455236] Re: AppArmor 2.9.2 fails to load multiple profiles
Just for the records - this is a duplicate of bug 1378095
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1455236
Title:
AppArmor 2.9.2 fails to load multiple profiles
Status in AppArmor Linux application security framework:
Invalid
Status in apparmor package in Ubuntu:
Invalid
Status in apparmor package in Debian:
Invalid
Bug description:
Loading profiles one by one works but this does not:
sudo aa-enforce /etc/apparmor.d/torbrowser.*
Setting /etc/apparmor.d/torbrowser.Browser.firefox to enforce mode.
Traceback (most recent call last):
File "/usr/sbin/aa-enforce", line 30, in
tool.cmd_enforce()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 153, in
cmd_enforce
apparmor.read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2572, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2598, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2853, in
parse_profile_data
store_list_var(filelist[file]['lvar'], list_var, value, var_operation,
file)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3289, in
store_list_var
raise AppArmorException(_('Redefining existing variable %(variable)s:
%(value)s in %(file)s') % { 'variable': list_var, 'value': value, 'file':
filename })
apparmor.common.AppArmorException: 'Redefining existing variable @{LIBVIRT}:
libvirt in /etc/apparmor.d/usr.sbin.libvirtd'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1455236/+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 1455107] Re: Creating and destroying SoundEffects causes crashes
** Also affects: qtmultimedia-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1455107 Title: Creating and destroying SoundEffects causes crashes Status in pulseaudio package in Ubuntu: Confirmed Status in qtmultimedia-opensource-src package in Ubuntu: New Bug description: I keep on receiving bug reports about Machines vs. Machines being crashy on Ubuntu Phones and I tracked it down to the SoundEffect item. When playing without sound effects enabled, the game seems very stable. To get to the bottom of this I created an app that simulates a bit how a game works with sound effects. It's a bit more aggressive than Machines-vs-Machines (still not really far fetched from a real game scenario) and reliably triggers some crashers in less than a minute here. So far I've seen crashes in creating SoundEffects items as well as removing them from the scene. Please find the example here: lp:~mzanetti/+junk/soundcrasher You should be able to run it on any vivid powered device by just opening the .pro file in QtCreator and hit the play button. The logs vary a lot between crashes. Sometimes I get some PulseAudio messages, sometimes it just crashes without any. Probably some raciness. Anyhow, this example app should be give the system a hard time and reveal most of the crashes eventually. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1455107/+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 1455236] Re: AppArmor 2.9.2 fails to load multiple profiles
Actually this was due to the usage of python3-apparmor 2.9.0.
Installing python3-apparmor 2.9.2 fixed the issue.
** Changed in: apparmor (Ubuntu)
Status: New => Invalid
** Changed in: apparmor (Debian)
Status: New => Invalid
** Changed in: apparmor
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1455236
Title:
AppArmor 2.9.2 fails to load multiple profiles
Status in AppArmor Linux application security framework:
Invalid
Status in apparmor package in Ubuntu:
Invalid
Status in apparmor package in Debian:
Invalid
Bug description:
Loading profiles one by one works but this does not:
sudo aa-enforce /etc/apparmor.d/torbrowser.*
Setting /etc/apparmor.d/torbrowser.Browser.firefox to enforce mode.
Traceback (most recent call last):
File "/usr/sbin/aa-enforce", line 30, in
tool.cmd_enforce()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 153, in
cmd_enforce
apparmor.read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2572, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2598, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2853, in
parse_profile_data
store_list_var(filelist[file]['lvar'], list_var, value, var_operation,
file)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3289, in
store_list_var
raise AppArmorException(_('Redefining existing variable %(variable)s:
%(value)s in %(file)s') % { 'variable': list_var, 'value': value, 'file':
filename })
apparmor.common.AppArmorException: 'Redefining existing variable @{LIBVIRT}:
libvirt in /etc/apparmor.d/usr.sbin.libvirtd'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1455236/+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 1442962] Re: Dialer app reports "No network" even though cellular is connected
** Branch linked: lp:~tiagosh/telepathy-ofono/add-ril-mc-plugin -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1442962 Title: Dialer app reports "No network" even though cellular is connected Status in the base for Ubuntu mobile products: New Status in dialer-app package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: New Bug description: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 It happens almost daily to me that the dialer app decides that there's no network available. Indicator says the correct network is connected, and I can even use GSM data, but no telephony apps work. When this happens, my `mc-tool dump` looks somewhere along the lines of (this is modified from memory, will update when happens again): Account: ofono/ofono/account0 Display Name: Nju Enabled: enabled Icon: im-ofono Connects: automatically Service: ofono Presences: Automatic: available (2) "" Current: offline (1) "" Requested: available (2) "online" Changing: yes (string) modem-objpath = /ril_0 Stopping/starting the dialer doesn't help, only thing that does is killing mission-control (or well, restarting lightdm or the phone). Please let me know what else to collect when this happens again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20150330-0ubuntu1 Uname: Linux 3.10.35+ armv7l ApportVersion: 2.17-0ubuntu1 Architecture: armhf Date: Sat Apr 11 22:34:04 2015 InstallationDate: Installed on 2015-04-08 (3 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150408-020203) SourcePackage: dialer-app SystemImageInfo: current build number: 165 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-04-08 05:43:13 version version: 165 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1442962/+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 1455243] [NEW] No memorized passwords
Public bug reported: bq device, r22. The browser neither remembers nor does prompt for remembering the usernames and passwords in websites. This is kind of a basic function nowadays in browser, since almost every page tries to offer a "personalized" experience to the user, and it is pretty annoying to manually reinsert them every time that the session terminates, especially on frequently used websites. ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New ** Description changed: bq device, r22. - The browser does not remember nor does not prompt for remembering the + The browser neither remembers nor does prompt for remembering the usernames and passwords in websites. This is kind of a basic function nowadays in browser, since almost every page tries to offer a "personalized" experience to the user, and it is pretty annoying to manually reinsert them every time that the session terminates, especially on frequently used websites. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1455243 Title: No memorized passwords Status in webbrowser-app package in Ubuntu: New Bug description: bq device, r22. The browser neither remembers nor does prompt for remembering the usernames and passwords in websites. This is kind of a basic function nowadays in browser, since almost every page tries to offer a "personalized" experience to the user, and it is pretty annoying to manually reinsert them every time that the session terminates, especially on frequently used websites. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1455243/+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 1448567] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) no 5 GHz wireless
Installed on a late 2014 Macbook pro, same chip, same issue with 15.04. Worked fine with 14.04 -- 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/1448567 Title: Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) no 5 GHz wireless Status in network-manager package in Ubuntu: Confirmed Bug description: Fresh install of 15.04 on a Macbook Pro 12,1. >Network controller [0280]: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) I copied brcmfmac43602-pcie.bin (https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/plain/brcm/) into /lib/firmware/brcm which enabled the wireless to pick up some SSIDs, but not all (almost positive the only ones seen are 2.4GHz). --- I was referred to this document: https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx Then I ran: $ lspci -vvnn | grep -A 9 Network 03:00.0 Network controller [0280]: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) Subsystem: Apple Inc. Device [106b:0133] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: brcmfmac I find the PCI device ID here: https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211#brcmfmac (Chipset BCM43602, ID: 14e4:43ba) I dropped the relevant firmware files from the repo given a bit further down that page (repo: https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/tree/brcm) into /lib/firmware/brcm/ ...still no 5 GHz. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448567/+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 1455236] Re: AppArmor 2.9.2 fails to load multiple profiles
** Also affects: apparmor (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1455236
Title:
AppArmor 2.9.2 fails to load multiple profiles
Status in AppArmor Linux application security framework:
New
Status in apparmor package in Ubuntu:
New
Status in apparmor package in Debian:
New
Bug description:
Loading profiles one by one works but this does not:
sudo aa-enforce /etc/apparmor.d/torbrowser.*
Setting /etc/apparmor.d/torbrowser.Browser.firefox to enforce mode.
Traceback (most recent call last):
File "/usr/sbin/aa-enforce", line 30, in
tool.cmd_enforce()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 153, in
cmd_enforce
apparmor.read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2572, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2598, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2853, in
parse_profile_data
store_list_var(filelist[file]['lvar'], list_var, value, var_operation,
file)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3289, in
store_list_var
raise AppArmorException(_('Redefining existing variable %(variable)s:
%(value)s in %(file)s') % { 'variable': list_var, 'value': value, 'file':
filename })
apparmor.common.AppArmorException: 'Redefining existing variable @{LIBVIRT}:
libvirt in /etc/apparmor.d/usr.sbin.libvirtd'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1455236/+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 1448567] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) no 5 GHz wireless
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- 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/1448567 Title: Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) no 5 GHz wireless Status in network-manager package in Ubuntu: Confirmed Bug description: Fresh install of 15.04 on a Macbook Pro 12,1. >Network controller [0280]: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) I copied brcmfmac43602-pcie.bin (https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/plain/brcm/) into /lib/firmware/brcm which enabled the wireless to pick up some SSIDs, but not all (almost positive the only ones seen are 2.4GHz). --- I was referred to this document: https://help.ubuntu.com/community/WifiDocs/Driver/bcm43xx Then I ran: $ lspci -vvnn | grep -A 9 Network 03:00.0 Network controller [0280]: Broadcom Corporation BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) Subsystem: Apple Inc. Device [106b:0133] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: brcmfmac I find the PCI device ID here: https://wireless.wiki.kernel.org/en/users/Drivers/brcm80211#brcmfmac (Chipset BCM43602, ID: 14e4:43ba) I dropped the relevant firmware files from the repo given a bit further down that page (repo: https://git.kernel.org/cgit/linux/kernel/git/firmware/linux- firmware.git/tree/brcm) into /lib/firmware/brcm/ ...still no 5 GHz. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1448567/+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 1317305] Re: -Wno-format is not honored
I've reproduced the issue with gcc-4.8 4.8.2-19ubuntu1 in trusty, and
verified that gcc-4.8 4.8.4-2ubuntu1~14.04 from trusty-proposed fixes
the issue. I've also run the test-gcc-security.py script from lp:qa-
regression-testing (which also has a test for this issue) and the
version in trusty-proposed passes all the tests there. Marking
verification-done. Thanks!
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1317305
Title:
-Wno-format is not honored
Status in gcc-4.8 package in Ubuntu:
Fix Released
Status in gcc-4.9 package in Ubuntu:
Fix Released
Bug description:
Due to the way the gcc-default-format-security patch is implemented in
gcc-4.8, disabling format warnings does not work:
$ cat format-extra-args.c
#include
/* printf extra arguments example */
int main(void)
{
printf("%s\n", "argument 1", "argument 2");
return 0;
}
$ gcc -Wall -O2 -o format-off format-extra-args.c -Wno-format
format-extra-args.c: In function 'main':
format-extra-args.c:12:2: warning: too many arguments for format
[-Wformat-extra-args]
printf("%s\n", "argument 1", "argument 2");
^
Earlier versions of gcc allowed disabling warnings correctly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1317305/+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 1103064] Re: power indicator shows Logitech wireless keyboard and mouse batteries with 0%
it seems it looses connection somehow when the message pops up the keyboard is listed as unknown if i turn keyboard / off / on again it works , but these messages still pop up if the keyboard is even switched OFF Done when error is up upower -d Device: /org/freedesktop/UPower/devices/keyboard_0003o046DoC52Bx14F8 native-path: /sys/devices/pci:00/:00:12.0/usb9/9-1/9-1:1.2/0003:046D:C52B.14F7/0003:046D:C52B.14F8 vendor: Logitech, Inc. model:K400 serial: 9E5B1F54 power supply: no updated: Fri 15 May 2015 06:56:54 AEST (60 seconds ago) has history: yes has statistics: no keyboard present: no rechargeable:yes state: unknown percentage: 0% History (charge): 1431637014 0.000 unknown History (rate): 1431637014 0.000 unknown Daemon: daemon-version: 0.9.23 can-suspend: yes can-hibernate: no on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: no is-docked: yes Done after keyboard Switched off and back on as you can see 70% power still upower -d Device: /org/freedesktop/UPower/devices/keyboard_0003o046DoC52Bx1500 native-path: /sys/devices/pci:00/:00:12.0/usb9/9-1/9-1:1.2/0003:046D:C52B.14FF/0003:046D:C52B.1500 vendor: Logitech, Inc. model:K400 serial: 9E5B1F54 power supply: no updated: Fri 15 May 2015 07:00:33 AEST (7 seconds ago) has history: yes has statistics: no keyboard present: yes rechargeable:yes state: discharging percentage: 70% History (charge): 1431637233 70.000 discharging 1431637171 0.000 unknown 1431637166 0.000 unknown History (rate): 1431637171 0.000 unknown 1431637166 0.000 unknown Daemon: daemon-version: 0.9.23 can-suspend: yes can-hibernate: no on-battery: no on-low-battery: no lid-is-closed: no lid-is-present: no is-docked: yes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1103064 Title: power indicator shows Logitech wireless keyboard and mouse batteries with 0% Status in The Power Indicator: Invalid Status in Upower: Fix Released Status in indicator-power package in Ubuntu: Invalid Status in upower package in Ubuntu: Fix Released Status in indicator-power source package in Raring: Invalid Status in upower source package in Raring: Won't Fix Bug description: I updated by raring installation and found that the power indicator now shows my wireless keyboard and mouse as (missing) and with extremely low power. Both the keyboard and mouse work (I'm using them to type this bug) and the low battery light on the respective devices do not show low power. Even switching to brand new batteries don't make the indicator change state. I've attached a screenshot of the indicator and a screen shot of the power setting dialog which seems to be in conflict with the indicator. I've reproduced this behavior with the 3.8.0-0-generic & vmlinuz-3.8.0-1-generic kernels. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: indicator-power 12.10.6daily13.01.18-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-0.4-generic 3.8.0-rc3 Uname: Linux 3.8.0-0-generic x86_64 ApportVersion: 2.8-0ubuntu2 Architecture: amd64 Date: Tue Jan 22 11:39:23 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: indicator-power UpgradeStatus: Upgraded to raring on 2013-01-18 (3 days ago) --- ApportVersion: 2.8-0ubuntu2 Architecture: amd64 DistroRelease: Ubuntu 13.04 EcryptfsInUse: Yes InstallationDate: Installed on 2012-05-08 (259 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120425) MarkForUpload: True Package: upower 0.9.19-1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4 Tags: raring running-unity Uname: Linux 3.8.0-1-generic x86_64 UpgradeStatus: Upgraded to raring on 2013-01-18 (4 days ago) UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1103064/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.n
[Touch-packages] [Bug 1455231] Re: [a11y] accerciser cannot explore Unity's accessibility object hierarchy
Well, this is not needed for the lp:unity/7.2 as it's already correct. Just going to mark the tasks Fix Released then:) ** No longer affects: unity/7.2 ** Changed in: unity Status: New => Fix Released ** Changed in: unity (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1455231 Title: [a11y] accerciser cannot explore Unity's accessibility object hierarchy Status in Unity: Fix Released Status in unity package in Ubuntu: Fix Released Bug description: accerciser cannot explore Unity's accessibility object hierarchy To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1455231/+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 1455236] Re: AppArmor 2.9.2 fails to load multiple profiles
This report is about AppArmor 2.9.2
** Also affects: apparmor
Importance: Undecided
Status: New
** Tags added: aa-tools
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1455236
Title:
AppArmor 2.9.2 fails to load multiple profiles
Status in AppArmor Linux application security framework:
New
Status in apparmor package in Ubuntu:
New
Bug description:
Loading profiles one by one works but this does not:
sudo aa-enforce /etc/apparmor.d/torbrowser.*
Setting /etc/apparmor.d/torbrowser.Browser.firefox to enforce mode.
Traceback (most recent call last):
File "/usr/sbin/aa-enforce", line 30, in
tool.cmd_enforce()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 153, in
cmd_enforce
apparmor.read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2572, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2598, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2853, in
parse_profile_data
store_list_var(filelist[file]['lvar'], list_var, value, var_operation,
file)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3289, in
store_list_var
raise AppArmorException(_('Redefining existing variable %(variable)s:
%(value)s in %(file)s') % { 'variable': list_var, 'value': value, 'file':
filename })
apparmor.common.AppArmorException: 'Redefining existing variable @{LIBVIRT}:
libvirt in /etc/apparmor.d/usr.sbin.libvirtd'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1455236/+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 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
** Changed in: canonical-devices-system-image Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+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 1455236] [NEW] AppArmor 2.9.2 fails to load multiple profiles
Public bug reported:
Loading profiles one by one works but this does not:
sudo aa-enforce /etc/apparmor.d/torbrowser.*
Setting /etc/apparmor.d/torbrowser.Browser.firefox to enforce mode.
Traceback (most recent call last):
File "/usr/sbin/aa-enforce", line 30, in
tool.cmd_enforce()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 153, in
cmd_enforce
apparmor.read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2572, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2598, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2853, in
parse_profile_data
store_list_var(filelist[file]['lvar'], list_var, value, var_operation, file)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3289, in
store_list_var
raise AppArmorException(_('Redefining existing variable %(variable)s:
%(value)s in %(file)s') % { 'variable': list_var, 'value': value, 'file':
filename })
apparmor.common.AppArmorException: 'Redefining existing variable @{LIBVIRT}:
libvirt in /etc/apparmor.d/usr.sbin.libvirtd'
** Affects: apparmor
Importance: Undecided
Status: New
** Affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
** Tags: aa-tools apparmor
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1455236
Title:
AppArmor 2.9.2 fails to load multiple profiles
Status in AppArmor Linux application security framework:
New
Status in apparmor package in Ubuntu:
New
Bug description:
Loading profiles one by one works but this does not:
sudo aa-enforce /etc/apparmor.d/torbrowser.*
Setting /etc/apparmor.d/torbrowser.Browser.firefox to enforce mode.
Traceback (most recent call last):
File "/usr/sbin/aa-enforce", line 30, in
tool.cmd_enforce()
File "/usr/lib/python3/dist-packages/apparmor/tools.py", line 153, in
cmd_enforce
apparmor.read_profiles()
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2572, in
read_profiles
read_profile(profile_dir + '/' + file, True)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2598, in
read_profile
profile_data = parse_profile_data(data, file, 0)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 2853, in
parse_profile_data
store_list_var(filelist[file]['lvar'], list_var, value, var_operation,
file)
File "/usr/lib/python3/dist-packages/apparmor/aa.py", line 3289, in
store_list_var
raise AppArmorException(_('Redefining existing variable %(variable)s:
%(value)s in %(file)s') % { 'variable': list_var, 'value': value, 'file':
filename })
apparmor.common.AppArmorException: 'Redefining existing variable @{LIBVIRT}:
libvirt in /etc/apparmor.d/usr.sbin.libvirtd'
To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1455236/+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 1455231] [NEW] [a11y] accerciser cannot explore Unity's accessibility object hierarchy
Public bug reported: accerciser cannot explore Unity's accessibility object hierarchy ** Affects: unity Importance: Undecided Status: New ** Affects: unity/7.2 Importance: Undecided Status: New ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Also affects: unity Importance: Undecided Status: New ** Also affects: unity/7.2 Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1455231 Title: [a11y] accerciser cannot explore Unity's accessibility object hierarchy Status in Unity: New Status in Unity 7.2 series: New Status in unity package in Ubuntu: New Bug description: accerciser cannot explore Unity's accessibility object hierarchy To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1455231/+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 1448229] Re: Launcher Trash icon: Empty Trash option opens nautilus @ home
*** This bug is a duplicate of bug 1445595 *** https://bugs.launchpad.net/bugs/1445595 Recorded a video of the issue in case there was any question what is happening. https://youtu.be/jpugIadlxz0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1448229 Title: Launcher Trash icon: Empty Trash option opens nautilus @ home Status in unity package in Ubuntu: Confirmed Bug description: Test case: Add a file to trash if none already Right click on Unity launcher trash icon > click on Empty Trash option nautilus open a window @ home folder ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Apr 24 13:11:02 2015 InstallationDate: Installed on 2015-04-24 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448229/+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 1437867] Re: xorg synaptic driver errors
There doesn't seem to be an usage issue in Vivid, but after an uptime of only three days the filesize of Xorg.0.log is already 116MB due to those error messages... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1437867 Title: xorg synaptic driver errors Status in xorg package in Ubuntu: Incomplete Bug description: My touchpad is behaving strangely (As far as I remember it only appeared after some update in Utopic). Using a two or three finger click, it needs several tries till it actually "accepts" the click. Sometimes the mouse pointer jumps to a different location on the screen when clicking with two or the fingers. Whenever the touchpad is used, errors get logged in /var/log/Xorg.0.log which seem to be related to the synaptic driver. Approximately once every week my X server crashes with a segmentation fault. First the screen turns black and after ~30 seconds the login screen appears. In this case the Xorg.0.log ends like this: (EE) BUG: triggered 'if (priv->num_active_touches > priv->num_slots)' (EE) BUG: ../../src/synaptics.c:2991 in UpdateTouchState() (EE) (EE) Backtrace: (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7fbbab374f76] (EE) 1: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7fbba294a000+0x527e) [0x7fbba294f27e] (EE) 2: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7fbba294a000+0x75a2) [0x7fbba29515a2] (EE) 3: /usr/bin/X (0x7fbbab1be000+0x95968) [0x7fbbab253968] (EE) 4: /usr/bin/X (0x7fbbab1be000+0xbfff9) [0x7fbbab27dff9] (EE) 5: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbba8ef3000+0x36eb0) [0x7fbba8f29eb0] (EE) 6: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x33) [0x7fbba8fe4673] (EE) 7: /usr/bin/X (WaitForSomething+0x1b4) [0x7fbbab372314] (EE) 8: /usr/bin/X (0x7fbbab1be000+0x57311) [0x7fbbab215311] (EE) 9: /usr/bin/X (0x7fbbab1be000+0x5b706) [0x7fbbab219706] (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fbba8f14ec5] (EE) 11: /usr/bin/X (0x7fbbab1be000+0x45a8e) [0x7fbbab203a8e] (EE) (EE) [dix] SYN1B7F:01 06CB:2970 UNKNOWN: unable to find touch point 0 (EE) [dix] SYN1B7F:01 06CB:2970 UNKNOWN: unable to find touch point 0 (EE) [dix] SYN1B7F:01 06CB:2970 UNKNOWN: unable to find touch point 0 (EE) [dix] SYN1B7F:01 06CB:2970 UNKNOWN: unable to find touch point 0 (EE) [dix] SYN1B7F:01 06CB:2970 UNKNOWN: unable to find touch point 0 (EE) [dix] SYN1B7F:01 06CB:2970 UNKNOWN: unable to find touch point 0 (EE) [dix] SYN1B7F:01 06CB:2970 UNKNOWN: unable to find touch point 0 (EE) [dix] SYN1B7F:01 06CB:2970 UNKNOWN: unable to find touch point 0 [115313.777] (EE) [115313.777] (EE) Backtrace: [115313.778] (EE) 0: /usr/bin/X (xorg_backtrace+0x56) [0x7fbbab374f76] [115313.779] (EE) 1: /usr/bin/X (0x7fbbab1be000+0x1bb179) [0x7fbbab379179] [115313.779] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fbba8ef3000+0x36eb0) [0x7fbba8f29eb0] [115313.779] (EE) 3: /usr/bin/X (XIGetDeviceProperty+0x40) [0x7fbbab30d8a0] [115313.779] (EE) 4: /usr/bin/X (0x7fbbab1be000+0x14f9f4) [0x7fbbab30d9f4] [115313.779] (EE) 5: /usr/bin/X (0x7fbbab1be000+0x14ff7a) [0x7fbbab30df7a] [115313.779] (EE) 6: /usr/bin/X (0x7fbbab1be000+0x574f7) [0x7fbbab2154f7] [115313.779] (EE) 7: /usr/bin/X (0x7fbbab1be000+0x5b706) [0x7fbbab219706] [115313.780] (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) [0x7fbba8f14ec5] [115313.780] (EE) 9: /usr/bin/X (0x7fbbab1be000+0x45a8e) [0x7fbbab203a8e] [115313.780] (EE) [115313.782] (EE) Segmentation fault at address 0x10018 [115313.782] (EE) Fatal server error: [115313.782] (EE) Caught signal 11 (Segmentation fault). Server aborting [115313.782] (EE) [115313.783] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [115313.783] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [115313.783] (EE) [115313.785] (II) AIGLX: Suspending AIGLX clients for VT switch [115314.987] (EE) Server terminated with error (1). Closing log file. I'm not sure if this a different bug or related to synaptic... ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.2 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: KDE Date: Sun Mar 29 16:04:24 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: kubuntu DkmsStatus: bbswitch, 0.7, 3.16.0-33-generic, x86_64: installed nvidia-304, 304.125, 3.16.0-33-generic, x86_64: installed vboxhost, 4.3.20, 3.16.
[Touch-packages] [Bug 1448834] Re: mouse battery not shown after upgrade
As reported on several places, UPower fails to recognize Unifying devices after an update to kernel >= 3.19. This includes Vivid. Please try the attached patch on /lib/udev/rules.d/95-upower-csr.rules (commit f8104a112eb967cd4c2aaf57b5a59aafe7c4738f upstream). ** Patch added: "[PATCH] rules: support Logitech Unifying in Linux 3.19" https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1448834/+attachment/4397703/+files/0001-rules-support-Logitech-Unifying-in-Linux-3.19.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1448834 Title: mouse battery not shown after upgrade Status in gnome-power-manager package in Ubuntu: Confirmed Status in upower package in Ubuntu: Confirmed Bug description: In Xubuntu 14.04 and 14.10 the power manager dropdown menu showed the battery level in my wireless logitech mouse. However after upgrading to 15.04 the mouse battery status is not shown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xfce4-power-manager 1.4.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Sun Apr 26 19:49:19 2015 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xfce4-power-manager UpgradeStatus: Upgraded to vivid on 2015-04-23 (3 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1448834/+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 1448229] Re: Launcher Trash icon: Empty Trash option opens nautilus @ home
*** This bug is a duplicate of bug 1445595 *** https://bugs.launchpad.net/bugs/1445595 I have the same bug on 2 systems, both fresh installations. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1448229 Title: Launcher Trash icon: Empty Trash option opens nautilus @ home Status in unity package in Ubuntu: Confirmed Bug description: Test case: Add a file to trash if none already Right click on Unity launcher trash icon > click on Empty Trash option nautilus open a window @ home folder ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity 7.3.2+15.04.20150420-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Apr 24 13:11:02 2015 InstallationDate: Installed on 2015-04-24 (0 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1448229/+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 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
Are there any news about this bug? I'm using another distro (elementaryOS) right now and it has the same problem too. I'd say there's a missing driver in the kernel but i'm not an expert... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in alsa-driver package in Ubuntu: Confirmed Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+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 1451462] Re: flite fails to build in trusty
This bug was fixed in the package flite - 1.4-release-8ubuntu0.1 --- flite (1.4-release-8ubuntu0.1) trusty; urgency=medium * debian/patches/CVE-2014-0027_unsafe_temporary_file.patch: - Fix patch format, fixes an FTBFS in trusty (LP: #1451462) -- Luke Yelavich Tue, 05 May 2015 09:05:43 +1000 ** Changed in: flite (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flite in Ubuntu. https://bugs.launchpad.net/bugs/1451462 Title: flite fails to build in trusty Status in flite package in Ubuntu: Fix Released Status in flite source package in Trusty: Fix Released Bug description: Impact: This does not affect the functionality of the package binaries at all. The source package in its current form cannot be unpacked and rebuilt. Test case: Download and attempt to unpack flite from trusty. The error originally given in the bug report will occur. The source package from trusty-proposed should be able to be unpacked properly, and be built. Original report follows: seen in a test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20150317/+build/7074139 dpkg-source: warning: -sn is not a valid option for Dpkg::Source::Package::V3::Quilt gpgv: Signature made Fri Jan 10 14:08:57 2014 UTC using RSA key ID 05BD750A gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./flite_1.4-release-8.dsc dpkg-source: info: extracting flite in flite-1.4-release dpkg-source: info: unpacking flite_1.4-release.orig.tar.gz dpkg-source: info: unpacking flite_1.4-release-8.debian.tar.gz dpkg-source: info: applying flite.texi.patch dpkg-source: info: applying no_rpath.patch dpkg-source: info: applying shlib_deps.patch dpkg-source: error: expected ^--- in line 10 of diff `flite-1.4-release/debian/patches/CVE-2014-0027_unsafe_temporary_file.patch' dpkg-source: info: applying CVE-2014-0027_unsafe_temporary_file.patch dpkg-source: info: fuzz is not allowed when applying patches dpkg-source: info: if patch 'CVE-2014-0027_unsafe_temporary_file.patch' is correctly applied by quilt, use 'quilt refresh' to update it FAILED [dpkg-source died] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flite/+bug/1451462/+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 1451462] Update Released
The verification of the Stable Release Update for flite has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to flite in Ubuntu. https://bugs.launchpad.net/bugs/1451462 Title: flite fails to build in trusty Status in flite package in Ubuntu: Fix Released Status in flite source package in Trusty: Fix Released Bug description: Impact: This does not affect the functionality of the package binaries at all. The source package in its current form cannot be unpacked and rebuilt. Test case: Download and attempt to unpack flite from trusty. The error originally given in the bug report will occur. The source package from trusty-proposed should be able to be unpacked properly, and be built. Original report follows: seen in a test rebuild: https://launchpad.net/ubuntu/+archive/test-rebuild-20150317/+build/7074139 dpkg-source: warning: -sn is not a valid option for Dpkg::Source::Package::V3::Quilt gpgv: Signature made Fri Jan 10 14:08:57 2014 UTC using RSA key ID 05BD750A gpgv: Can't check signature: public key not found dpkg-source: warning: failed to verify signature on ./flite_1.4-release-8.dsc dpkg-source: info: extracting flite in flite-1.4-release dpkg-source: info: unpacking flite_1.4-release.orig.tar.gz dpkg-source: info: unpacking flite_1.4-release-8.debian.tar.gz dpkg-source: info: applying flite.texi.patch dpkg-source: info: applying no_rpath.patch dpkg-source: info: applying shlib_deps.patch dpkg-source: error: expected ^--- in line 10 of diff `flite-1.4-release/debian/patches/CVE-2014-0027_unsafe_temporary_file.patch' dpkg-source: info: applying CVE-2014-0027_unsafe_temporary_file.patch dpkg-source: info: fuzz is not allowed when applying patches dpkg-source: info: if patch 'CVE-2014-0027_unsafe_temporary_file.patch' is correctly applied by quilt, use 'quilt refresh' to update it FAILED [dpkg-source died] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flite/+bug/1451462/+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 1425398] Update Released
The verification of the Stable Release Update for rsyslog has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: In Progress Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Fix Released Bug description: [rsyslog impact] This bug prevents rsyslog from receiving all events from other services on trusty when the utopic-hwe (and newer) kernels are used. The rsyslog SRU adds an additional permission (read access to /dev/log) to the rsyslog apparmor policy to allow this to work. [rsyslog test case] (1) Ensure the rsyslog apparmor policy is set to enforce; it should show up listed in the "XX profiles are in enforce mode." section reported by "sudo aa-status" (if it's disabled, do "sudo aa-enforce rsyslogd"). (2) Install the utopic or newer hwe enablement stack reboot into the kernel. Using the logger(1) utility should generate log messages (e.g. "logger foo") that are recorded in syslog; with this bug, they will be blocked (grep DENIED /var/log/syslog). [rsyslog regression potential] The only change to rsyslog in the SRU is a slight loosening of the rsyslog apparmor policy. The risk of an introduced regression is small. [rsyslog addition info] The qa-regression-testing script is useful for verifying that rsyslog is still functioning properly (http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/head:/scripts/test-rsyslog.py) [Original description] I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4002 comm="sshd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4080 comm="sudo" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/rsyslogd" name="/dev/log" pid=2436 comm="whoopsie" requested_mask="r" denied_mask="r" fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/rsyslogd" name="/dev/log" pid=3762 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-pack
[Touch-packages] [Bug 1425398] Re: Apparmor uses rsyslogd profile for different processes - utopic HWE
This bug was fixed in the package rsyslog - 7.4.4-1ubuntu2.6 --- rsyslog (7.4.4-1ubuntu2.6) trusty-proposed; urgency=medium * debian/usr.sbin.rsyslog: grant read access to /dev/log to cope with behaviorial change of apparmor in utopic HWE kernel (LP: #1425398) -- Steve Beattie Thu, 30 Apr 2015 12:20:51 -0700 ** Changed in: rsyslog (Ubuntu Trusty) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1425398 Title: Apparmor uses rsyslogd profile for different processes - utopic HWE Status in apparmor package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in linux-lts-utopic package in Ubuntu: Invalid Status in rsyslog package in Ubuntu: Fix Released Status in apparmor source package in Trusty: In Progress Status in linux source package in Trusty: Confirmed Status in linux-lts-utopic source package in Trusty: Invalid Status in rsyslog source package in Trusty: Fix Released Bug description: [rsyslog impact] This bug prevents rsyslog from receiving all events from other services on trusty when the utopic-hwe (and newer) kernels are used. The rsyslog SRU adds an additional permission (read access to /dev/log) to the rsyslog apparmor policy to allow this to work. [rsyslog test case] (1) Ensure the rsyslog apparmor policy is set to enforce; it should show up listed in the "XX profiles are in enforce mode." section reported by "sudo aa-status" (if it's disabled, do "sudo aa-enforce rsyslogd"). (2) Install the utopic or newer hwe enablement stack reboot into the kernel. Using the logger(1) utility should generate log messages (e.g. "logger foo") that are recorded in syslog; with this bug, they will be blocked (grep DENIED /var/log/syslog). [rsyslog regression potential] The only change to rsyslog in the SRU is a slight loosening of the rsyslog apparmor policy. The risk of an introduced regression is small. [rsyslog addition info] The qa-regression-testing script is useful for verifying that rsyslog is still functioning properly (http://bazaar.launchpad.net/~ubuntu-bugcontrol/qa-regression-testing/master/view/head:/scripts/test-rsyslog.py) [Original description] I've noticed that apparmor loads /usr/sbin/rsyslogd profile for completely unrelated processes: Feb 25 08:36:19 emma kernel: [ 134.796218] audit: type=1400 audit(1424842579.429:245): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4002 comm="sshd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 08:36:23 emma kernel: [ 139.330989] audit: type=1400 audit(1424842583.965:246): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/rsyslogd" name="/dev/log" pid=4080 comm="sudo" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 Feb 25 08:35:42 emma kernel: [ 97.912402] audit: type=1400 audit(1424842542.565:241): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/rsyslogd" name="/dev/log" pid=2436 comm="whoopsie" requested_mask="r" denied_mask="r" fsuid=103 ouid=0 Feb 25 08:34:43 emma kernel: [ 38.867998] audit: type=1400 audit(1424842483.546:226): apparmor="DENIED" operation="sendmsg" profile="/usr/sbin/rsyslogd" name="/dev/log" pid=3762 comm="ntpd" requested_mask="r" denied_mask="r" fsuid=0 ouid=0 I'm not sure how apparmor decides which profile to use for which task, but is shouldn't load '/usr/sbin/rsyslogd' profile for sshd/ntpd/etc. I'm running: # lsb_release -rd Description: Ubuntu 14.04.2 LTS Release: 14.04 # dpkg -l | grep apparmor ii apparmor2.8.95~2430-0ubuntu5.1 amd64User-space parser utility for AppArmor ii apparmor-profiles 2.8.95~2430-0ubuntu5.1 all Profiles for AppArmor Security policies ii apparmor-utils 2.8.95~2430-0ubuntu5.1 amd64Utilities for controlling AppArmor ii libapparmor-perl2.8.95~2430-0ubuntu5.1 amd64AppArmor library Perl bindings ii libapparmor1:amd64 2.8.95~2430-0ubuntu5.1 amd64changehat AppArmor library ii python3-apparmor2.8.95~2430-0ubuntu5.1 amd64AppArmor Python3 utility library ii python3-libapparmor 2.8.95~2430-0ubuntu5.1 amd64AppArmor library Python3 bindings # uname -a Linux emma 3.16.0-31-generic #41~14.04.1-Ubuntu SMP Wed Feb 11 19:30:13 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1425398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https
[Touch-packages] [Bug 1385689] Re: ubuntu-bug, software-center and update-manager crashing
Seems like an unintended ABI break in APT. ** Package changed: python-apt (Ubuntu) => apt (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1385689 Title: ubuntu-bug, software-center and update-manager crashing Status in apt package in Ubuntu: Confirmed Bug description: Just yesterday I updated from 14.04 to 14.10 and noticed, that the update-manager shows a Stop-sign in the notification bar. Tried to open it via the launcher, no success. Then I tried starting the update-manager via console: dsfsfs@linux:/usr/lib/python3/dist-packages$ update-manager Traceback (most recent call last): File "/usr/bin/update-manager", line 38, in from UpdateManager.UpdateManager import UpdateManager File "/usr/lib/python3/dist-packages/UpdateManager/UpdateManager.py", line 36, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-34m-x86_64-linux-gnu.so: undefined symbol: _ZN13pkgSrcRecords4StepEv dsfsfs@linux:/usr/lib/python3/dist-packages$ Tried the same with software-center: dsfsfs@linux:/usr/lib/python3/dist-packages$ software-center ERROR:root:DebFileApplication import Traceback (most recent call last): File "/usr/share/software-center/softwarecenter/db/__init__.py", line 4, in from debfile import DebFileApplication, DebFileOpenError File "/usr/share/software-center/softwarecenter/db/debfile.py", line 21, in from apt.debfile import DebPackage File "/usr/lib/python2.7/dist-packages/apt/__init__.py", line 23, in import apt_pkg ImportError: /usr/lib/python2.7/dist-packages/apt_pkg.so: undefined symbol: _ZN13pkgSrcRecords4StepEv Speicherzugriffsfehler dsfsfs@linux:/usr/lib/python3/dist-packages$ And, last but not least, after reading the FAQs on how to file in a bug, I tried to run ubuntu-bug, which gave me this: dsfsfs@linux:/usr/lib/python3/dist-packages$ ubuntu-bug Traceback (most recent call last): File "/usr/share/apport/apport-gtk", line 24, in import apport File "/usr/lib/python3/dist-packages/apport/__init__.py", line 5, in from apport.report import Report File "/usr/lib/python3/dist-packages/apport/report.py", line 30, in import apport.fileutils File "/usr/lib/python3/dist-packages/apport/fileutils.py", line 23, in from apport.packaging_impl import impl as packaging File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 20, in import apt File "/usr/lib/python3/dist-packages/apt/__init__.py", line 23, in import apt_pkg ImportError: /usr/lib/python3/dist-packages/apt_pkg.cpython-34m-x86_64-linux-gnu.so: undefined symbol: _ZN13pkgSrcRecords4StepEv dsfsfs@linux:/usr/lib/python3/dist-packages$ Please help. Thanks in advance To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1385689/+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 1455219] [NEW] Cannot connect to PPPoE using NetworkManager: Could not find pppoe binary.
Public bug reported: TL;DR: NetworkManager requires "pppoe" package, which was not installed by default in Lubuntu 15.04. I tried using Network Manager (nm-applet) to configure a PPPoE connection. I can create the connection, but trying to connect to it fails. The erro message that shows up in a dialog is not helpful at all: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/23' failed in libnm- glib. What is helpful is a message buried in /var/log/syslog: NetworkManager[713]: (eth0): PPPoE failed to start: Could not find pppoe binary. Workaround: apt-get install pppoe. Desirable solution: pppoe package being a dependency of another package (lubuntu-desktop seems like a good one). Using Lubuntu 15.04 (upgraded from previous versions). This is the first time configuring a DSL/PPPoE connection in this system. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- 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/1455219 Title: Cannot connect to PPPoE using NetworkManager: Could not find pppoe binary. Status in network-manager package in Ubuntu: New Bug description: TL;DR: NetworkManager requires "pppoe" package, which was not installed by default in Lubuntu 15.04. I tried using Network Manager (nm-applet) to configure a PPPoE connection. I can create the connection, but trying to connect to it fails. The erro message that shows up in a dialog is not helpful at all: (1) Creating object for path '/org/freedesktop/NetworkManager/ActiveConnection/23' failed in libnm- glib. What is helpful is a message buried in /var/log/syslog: NetworkManager[713]: (eth0): PPPoE failed to start: Could not find pppoe binary. Workaround: apt-get install pppoe. Desirable solution: pppoe package being a dependency of another package (lubuntu-desktop seems like a good one). Using Lubuntu 15.04 (upgraded from previous versions). This is the first time configuring a DSL/PPPoE connection in this system. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1455219/+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 841409] Re: GEdit is the only choice as Calendar application in Default Applications dialog
** Changed in: gnome-control-center Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/841409 Title: GEdit is the only choice as Calendar application in Default Applications dialog Status in GNOME Control Center: Confirmed Status in desktop-file-utils package in Ubuntu: Fix Released Status in gtk+3.0 package in Ubuntu: Triaged Status in desktop-file-utils source package in Oneiric: Won't Fix Status in gtk+3.0 source package in Oneiric: Won't Fix Status in desktop-file-utils source package in Precise: Fix Released Status in gtk+3.0 source package in Precise: Triaged Bug description: In Ubuntu Oneiric (11.10) beta1, opening the Default Applications dialog (System Settings -> System Information), GEdit is selected (and only possible choice) for Calendar items. I think this is not expected, since it is not so useful to open calendar data as standard text). In Oneiric Thunderbird is default email client. Currently Thunderbird7 beta is installed, and I noticed the Lightning extension for Calendar is not compatible with it yet. Will Thunderbird/Lightining be possible values for Calendar applications? ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-control-center 1:3.1.90-0ubuntu2 ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4 Uname: Linux 3.0.0-10-generic i686 Architecture: i386 Date: Mon Sep 5 00:56:27 2011 ProcEnviron: PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to oneiric on 2011-09-03 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/841409/+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 543767] Re: ssh logins doesn't show the MOTD when connecting with public key authorisation
Same here, on Ubuntu 14.04: * Selecting 'PrintMotd yes' has no effect if UsePAM is no. Choosing 'UsePAM yes' shows the Motd. IMO, this is is a bug. The MOTD should be controlled solely by PrintMotd. Is there a rationale behind hiding the MOTD if the user logs in with a public key? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/543767 Title: ssh logins doesn't show the MOTD when connecting with public key authorisation Status in Ubuntu Server papercuts: Incomplete Status in openssh package in Ubuntu: Expired Bug description: This is merely a minor annoyance, but nonetheless worth a bug report for the servers papercut team: The method to display a MOTD described in the official Ubuntu server guide, chapter 22 (https://help.ubuntu.com/9.10/serverguide/C/update- motd.html) doesn't work as soon as you connect with public key authorisation. Connecting /w password only shows the MOTD correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/server-papercuts/+bug/543767/+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 1424791] Re: Ubuntu Phone: cellular data did not recover after losing coverage
Hi yesterday I upgraded the device (BQ Aquaris 4.5) to r22. no problem today in switching from 3G to wifi and vice-versa, and recovery celluar data after driving in non covered area. -- 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/1424791 Title: Ubuntu Phone: cellular data did not recover after losing coverage Status in network-manager package in Ubuntu: Incomplete Bug description: Hi! Today I travelled in train and I lost my mobile signal. BUG: After have signal, the cellular data (3G) is not recovering. I have to enter in plane mode and exit from that mode for having 3G again. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1424791/+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 1450642] Re: seccomp missing many new syscalls
Test cases pass with packages in vivid-proposed: * in build testsuite results are same between previous build and this for all archs: PASS * scmp_sys_resolver 1024: PASS * scmp_sys_resolver getrandom: PASS * autopkgtests: PASS * lxc (amd64 and i386 only): PASS * docker framework (snappy/armhf): PASS * snappy hello-world.env (snappy/armhf): PASS As a further data point, this package is source-identical to what is in wily (other than the debian/changelog) and wily's update made it through proposed migration and lxc's tests all passed: https://jenkins.qa.ubuntu.com/job/wily-adt-lxc/lastBuild/ARCH=amd64,label=adt/artifact/results/log https://jenkins.qa.ubuntu.com/job/wily-adt-lxc/lastBuild/ARCH=i386,label=adt/artifact/results/log ** Tags removed: verification-needed ** Tags added: verification-done ** Changed in: snappy-ubuntu Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1450642 Title: seccomp missing many new syscalls Status in Snappy Ubuntu: Fix Committed Status in libseccomp package in Ubuntu: Fix Released Status in libseccomp source package in Vivid: Fix Committed Status in libseccomp source package in Wily: Fix Released Bug description: [Impact] Several syscalls were discovered to be missing when using the launcher on snappy. These should be added so we may properly support seccomp filtering. [Test Case] seccomp itself has a comprehensive testsuite, and while it doesn't fail the build, regressions can be seen by looking at the build log. Eg: Regression Test Summary tests run: 6494 tests skipped: 52 tests passed: 6494 tests failed: 0 tests errored: 0 Furthermore, on a snappy system, perform: $ sudo snappy install hello-world $ hello-world.env It should show the environment. On an arm system with 2.1.1-1 from the archive, this will fail due to a seccomp denial: audit: type=1326 audit(1430766107.122:16): auid=1000 uid=1000 gid=1000 ses=15 pid=1491 comm="env" exe="/bin/bash" sig=31 arch=4028 syscall=983045 compat=0 ip=0xb6fb0bd6 code=0x0 (note, snappy images have a ppa fix for this, see notes below). To test the segfault fix, do: $ scmp_sys_resolver 1024 Segmentation fault It should return: $ scmp_sys_resolver 1024 UNKNOWN For the new 3.19 syscalls: $ scmp_sys_resolver getrandom -1 it should return something like (actual number depends on arch, this is on armhf): $ scmp_sys_resolver getrandom 384 autopkgtests for libseccomp have been added as part of this update to verify that the library recognizes all the syscalls from 3.19 and the private syscalls. These tests can be run like so (assuming you are in the unpacked source and the binaries are in ../binary): $ export REL=vivid $ adt-run `for i in ../binary/*.deb ; do echo -n "-B $i " ; done` --source ../source/*.dsc --log-file /tmp/adt.out --- adt-virt-schroot autopkgtest-$REL-amd64 || echo "** AUTOPKGTESTS FAILED" Alternatively, if you don't have autopkgtest setup, you can do: $ apt-get install dpkg-dev build-essential linux-libc-dev libseccomp-dev seccomp $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-filter ... PASS $ export ADTTMP=/tmp/foo ; mkdir -p "$ADTTMP" ; sh ./debian/tests/test-scmp_sys_resolver ... PASS Lastly, seccomp is used by lxc. lxc can be tested by using the test case as outlined in step 4 of https://wiki.ubuntu.com/Process/Merges/TestPlans/AppArmor#Desktop_only. [Regression Potential] If the above tests, regression potential is considered low. Unknown syscalls will continue to be handled as before. Description of changes: add finit_module: https://github.com/seccomp/libseccomp/commit/64152018ffdf971efefd84466db4a92002bb8b15 sync the syscall table entries - 3.16 https://github.com/seccomp/libseccomp/commit/9186136be7696ed63a8ddc06c9b397057abc5c75 https://github.com/seccomp/libseccomp/commit/3f319a9a5bc2e32f5a3c296fb0476c040b6f46c4 https://github.com/seccomp/libseccomp/commit/689f19e7488535c775c1db415b8d9895905ef8dd https://github.com/seccomp/libseccomp/commit/ac6802b300922ef2ad3e95e2c80f89b575073aeb https://github.com/seccomp/libseccomp/commit/c6205d9600983aa3fa68ca952b7624f2fec86718 https://github.com/seccomp/libseccomp/commit/76739812a3e23182504cde43403ddb9921e0e05a sync the syscall table entries - 3.17 https://github.com/seccomp/libseccomp/commit/6354f8cab5ac82a8d567005e58a9e7ff9dd843a9 sync the syscall table entries - 3.19 https://github.com/seccomp/libseccomp/commit/7b80fb2fb683cafaf5dc9ff7692437ba86e598a3 This should also be applied (fix a segfault for invalid syscall numbers): https://github.com/seccomp/libseccomp/commit/2d09a74c7f04d29ae740db1e2187ff1a1886b2c3 In addition, add-missing-arm-private-syscalls.patch is add to add 5 priv
[Touch-packages] [Bug 1431709] Re: rsync dies with "inflate returned -3"
Just hit the same bug : got the same :"inflate returned -3" while rsync'ing an 8G VM disk .vdi file from a Ubuntu 14.04.2 LTS server to a Ubuntu 12.04.5 LTS one Removed the -z flag sis the trick as well -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsync in Ubuntu. https://bugs.launchpad.net/bugs/1431709 Title: rsync dies with "inflate returned -3" Status in rsync package in Ubuntu: New Bug description: On 12.04.5 64bit server running rsync pulling backups from a 14.04 64bit laptop dies with "inflate returned -3" when using the -z flag on a backup containing a large file (a VM image over 1G). Removing the -z flag works around the issue. See the Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1431709/+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 1311128] Re: Please incorporate gcc 4.8 revision 209515
Thanks, Steve. I forwarded the request internally. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1311128 Title: Please incorporate gcc 4.8 revision 209515 Status in gcc-4.8 package in Ubuntu: Fix Released Status in gccgo-4.9 package in Ubuntu: Invalid Status in gcc-4.8 source package in Trusty: Fix Committed Status in gccgo-4.9 source package in Trusty: Fix Released Status in gcc-4.8 source package in Utopic: Fix Released Status in gccgo-4.9 source package in Utopic: Invalid Bug description: From another, less public, bug: Text by Bill Schmidt: A GCC bug was found in the little endian vector API that affects use of the vec_mergeh and vec_mergel interfaces when VSX is enabled (this is the default for Power8). These interfaces produce the wrong results for 4x32 vector types (vector int of either signedness, vector float). The upstream patch fixes this issue. (bug internally reported by Thierry Fauck; fixed upstream by Bill Schmidt.) SVN revision in FSF 4.8 branch: 209515 http://gcc.gnu.org/viewcvs/gcc?view=revision&revision=209515 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1311128/+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 1454625] Re: Cannot send MMS messages with combined contexts with WiFi connected
** Tags removed: connectiivity
** Tags added: connectivity
--
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/1454625
Title:
Cannot send MMS messages with combined contexts with WiFi connected
Status in the base for Ubuntu mobile products:
Confirmed
Status in network-manager package in Ubuntu:
In Progress
Bug description:
Cannot send MMS messages with combined contexts in case the WiFi is
connected, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've seen the
bug, the data is:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
MessageCenter = http://www.pepephone.com
Name = MMS Pepephone
Username =
Protocol = ip
Preferred = 0
IPv6.Settings = { }
Settings = { }
MessageProxy = 10.138.255.43:8080
Type = internet
AccessPointName = gprs.pepephone.com
Active = 0
Sending an MMS with cellular data and WiFi enabled fails for this
operator when using a combined context. Disabling WiFi I was able to
send the MMS.
The error I see in ~/.cache/upstart/dbus.log is:
E0513 09:55:03.254148 4565 file_upload.cpp:345] Upload ID{
d0e5da6eb7664d908ab49b810ff55e01 } http://www.pepephone.com
ERROR::Network error UnknownNetworkError: an unknown network-related
error was detected
The interface that were up when the failure happened were:
$ ifconfig
rmnet_usb0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.60.155.62 Mask:255.255.255.0
inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
UP RUNNING MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:829 (829.0 B) TX bytes:1052 (1.0 KB)
wlan0 Link encap:Ethernet HWaddr 10:68:3f:7a:92:d5
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355 errors:0 dropped:0 overruns:0 frame:0
TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:51241 (51.2 KB) TX bytes:18951 (18.9 KB)
See attached the tcpdump of the packets sent when this happened. Some
quick analysis shows that the uploader is sending through the WiFi
(192.168.1.40) instead of using 10.60.155.62, so it is clearly a
routing problem. The MMS proxy has private address 10.138.255.43 so it
is not reachable from WiFi.
Reproduced in:
mako vivid-proposed image #195
arale vivid-proposed image #38
krillin vivid-proposed image #205
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1454625/+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 1445134] Re: Network manager never scanning for new access points
** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Milestone: None => ww22-2015 ** Tags added: connectivity -- 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/1445134 Title: Network manager never scanning for new access points Status in the base for Ubuntu mobile products: New Status in network-manager package in Ubuntu: New Bug description: While trying to reproduce another bug related with the last seen value from the access points, I noticed that network manager is never really scanning for new access points on my desktop, not even when not connected. $ sudo nmcli g logging level debug domains wifi_scan Then powered an access point, but was never really able to see it. From syslog, noticed that there is never really a scan, which explains why the ap never goes away and why it is not able to find it in the first place. If I force a scan via cmdline it works as expected (and I noticed a scan also happens when changing connections). Was also able to reproduce this issue on mako, with the following image: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 173 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-16 14:58:58 version version: 173 version ubuntu: 20150416 version device: 20150210 version custom: 20150416 In the mako case, I booted with a known connection in place, it connected successfully but it never really scans for other access points. Scan works fine after disconnecting though. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu14 ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3 Uname: Linux 3.19.0-14-generic x86_64 ApportVersion: 2.17.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 16 14:21:42 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-10-29 (534 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) IpRoute: default via 192.168.1.1 dev wlan0 proto static metric 1024 10.0.3.0/24 dev lxcbr0 proto kernel scope link src 10.0.3.1 169.254.0.0/16 dev lxcbr0 scope link metric 1000 192.168.1.0/24 dev wlan0 proto kernel scope link src 192.168.1.16 SourcePackage: network-manager UpgradeStatus: Upgraded to vivid on 2013-10-31 (532 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-11-04T02:19:36.923463 nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445134/+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 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)
** Changed in: canonical-devices-system-image Milestone: ww21-2015 => ww22-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1425172 Title: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min) Status in the base for Ubuntu mobile products: Confirmed Status in indicator-network package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in network-manager package in Ubuntu RTM: Confirmed Bug description: Summary: Network indicator lists the non-exist AP Steps to reproduce: 1. Boot to system 2. Scroll down the Network indicator 3. It lists about 10 AP (In Taipei office) 4. Go to another place and check network indicator again Expected Result: It should not list non-exist AP and only show available AP Actual Result: It shows about 12 AP on the screen but only two are real AP for connecting, and others 10 are from last list. This is reproducible on mako/krillin on both RTM and vivid. The main issue is that the timeout for the AP to be removed from the known AP list is too big when comparing with other phones. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+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 1445080] Re: Cellular data not activated after exiting flight mode
** Changed in: canonical-devices-system-image Status: Fix Released => Confirmed ** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Milestone: None => ww22-2015 ** Tags added: connectivity -- 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/1445080 Title: Cellular data not activated after exiting flight mode Status in the base for Ubuntu mobile products: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Cellular data is not activated in ~50% of the cases in arale after setting then unsetting flight mode. I obtained the attached log this way: 1. Disabled wifi (to have less noise) and removed syslog (to make smaller the attached one) 2. Reboot 3. See cellular data is on: route is right, I have network access 4. Set flight mode 5. Unset flight mode 6. Data is not restored even after waiting for a few minutes. ccmni0 interface is down. list-modems shows that the modem is data-attached list-contexts output shows that no IP context has been activated Doing usr/share/ofono/scripts/activate-context 1 sudo ip route add default dev ccmni0 ping 8.8.8.8 works and I receive the ping responses. $ system-image-cli -i current build number: 12 device name: arale channel: ubuntu-touch/tangxi-vivid-proposed last update: 2015-04-16 08:06:39 version version: 12 version ubuntu: 20150416.0 version device: a17b9320788e7215ddf123544a3a2b5a4fa61f0d5add83f393866e8c7a9155b0 version custom: 20150416.0 + NetworkManager 0.9.10.0-4ubuntu15~mtrudel1 (silo 29 atm) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1445080/+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 1361864] Re: add "Preferred" property to ConnectionContext interface
** Changed in: canonical-devices-system-image Importance: Undecided => High ** Changed in: canonical-devices-system-image Milestone: None => ww22-2015 ** Tags added: connectivity -- 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/1361864 Title: add "Preferred" property to ConnectionContext interface Status in the base for Ubuntu mobile products: Confirmed Status in libqofono package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: In Progress Status in nuntium package in Ubuntu: In Progress Status in ofono package in Ubuntu: Fix Released Status in ubuntu-system-settings package in Ubuntu: In Progress Status in ubuntu-system-settings source package in Vivid: New Bug description: To implement system-settings APN editor reliably there has to be a Tag field with is an arbitrary non user-visible string that can be set for any Context. We also need org.ofono.ConnectionManager.AddContext which takes a variant map with prepopulated values for the context to be created, so we can have a function in QOfono QOfonoConnectionManager::addContextWithTag(QString tag). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1361864/+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 1432613] Re: Facebook and MSN messengers shutting down (third-party client access)
This bug was fixed in the package empathy - 3.8.6-0ubuntu13.1 --- empathy (3.8.6-0ubuntu13.1) utopic; urgency=medium [ Alberto Mardegan ] * debian/control: - Remove WLM and Facebook plugins from Recommends (LP: #1432613) - Remove WLM and Facebook from package descriptions. [ Iain Lane ] * Update Vcs-Bzr for stable release -- Alberto Mardegan Thu, 30 Apr 2015 10:56:19 +0100 ** Changed in: empathy (Ubuntu Utopic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1432613 Title: Facebook and MSN messengers shutting down (third-party client access) Status in Online Accounts: Account plugins: In Progress Status in Webapps Team Task Tracking Project: In Progress Status in account-plugins package in Ubuntu: Fix Committed Status in empathy package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: New Status in account-plugins source package in Trusty: Fix Released Status in empathy source package in Trusty: Fix Released Status in ubuntu-system-settings-online-accounts source package in Trusty: Won't Fix Status in account-plugins source package in Utopic: Fix Committed Status in empathy source package in Utopic: Fix Released Status in ubuntu-system-settings-online-accounts source package in Utopic: Won't Fix Status in account-plugins source package in Vivid: Fix Released Status in empathy source package in Vivid: Fix Released Status in ubuntu-system-settings-online-accounts source package in Vivid: Won't Fix Bug description: [ Description ] Facebook messenger and Windows Live messenger don't work any more because Facebook & Microsoft removed third-party support for them. [ Fix & QA ] Stop supporting IM accounts for these clients. For both creation & continued use. Verify that if you add a WLM or FB account in online accounts, empathy doesn't try to connect to it. account-plugins-windows-live shouldn't be pulled in by default any more (check a trusty daily which is built with proposed). [ Regression potential ] This is a regression, in that we stop supporting some account types. We don't have a choice about this. [ Original description ] The march towards a future of silos carries on. https://developers.facebook.com/docs/chat - the XMPP gateway for Facebook will shut down on April 30. http://ismsndeadyet.com/ - Microsoft are removing MSN endpoints. I guess we need to correspondingly remove IM support for these services & SRU it back. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1432613/+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 1454625] Re: Cannot send MMS messages with combined contexts with WiFi connected
** Tags added: connectiivity
--
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/1454625
Title:
Cannot send MMS messages with combined contexts with WiFi connected
Status in the base for Ubuntu mobile products:
Confirmed
Status in network-manager package in Ubuntu:
In Progress
Bug description:
Cannot send MMS messages with combined contexts in case the WiFi is
connected, for some operators. Combined contexts are able to handle
internet data and MMS data. For the operator for which I've seen the
bug, the data is:
$ /usr/share/ofono/scripts/list-contexts
[ /ril_0 ]
[ /ril_0/context1 ]
Password =
MessageCenter = http://www.pepephone.com
Name = MMS Pepephone
Username =
Protocol = ip
Preferred = 0
IPv6.Settings = { }
Settings = { }
MessageProxy = 10.138.255.43:8080
Type = internet
AccessPointName = gprs.pepephone.com
Active = 0
Sending an MMS with cellular data and WiFi enabled fails for this
operator when using a combined context. Disabling WiFi I was able to
send the MMS.
The error I see in ~/.cache/upstart/dbus.log is:
E0513 09:55:03.254148 4565 file_upload.cpp:345] Upload ID{
d0e5da6eb7664d908ab49b810ff55e01 } http://www.pepephone.com
ERROR::Network error UnknownNetworkError: an unknown network-related
error was detected
The interface that were up when the failure happened were:
$ ifconfig
rmnet_usb0 Link encap:UNSPEC HWaddr
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:10.60.155.62 Mask:255.255.255.0
inet6 addr: fe80::8159:5668:797f:eed7/64 Scope:Link
UP RUNNING MTU:1500 Metric:1
RX packets:4 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:829 (829.0 B) TX bytes:1052 (1.0 KB)
wlan0 Link encap:Ethernet HWaddr 10:68:3f:7a:92:d5
inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::1268:3fff:fe7a:92d5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:355 errors:0 dropped:0 overruns:0 frame:0
TX packets:186 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:51241 (51.2 KB) TX bytes:18951 (18.9 KB)
See attached the tcpdump of the packets sent when this happened. Some
quick analysis shows that the uploader is sending through the WiFi
(192.168.1.40) instead of using 10.60.155.62, so it is clearly a
routing problem. The MMS proxy has private address 10.138.255.43 so it
is not reachable from WiFi.
Reproduced in:
mako vivid-proposed image #195
arale vivid-proposed image #38
krillin vivid-proposed image #205
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1454625/+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 1450790] Re: Phone with an APN specifying Username/Password, not re-connecting to mobile data until rebooting
** Tags added: connectivity -- 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/1450790 Title: Phone with an APN specifying Username/Password, not re-connecting to mobile data until rebooting Status in the base for Ubuntu mobile products: In Progress Status in network-manager package in Ubuntu: In Progress Status in ofono package in Ubuntu: Invalid Bug description: Whenever I walk out of WiFi range, my phone does not connect to mobile data. Toggling flight mode does not help. I have to reboot the phone. When then I finally manage to connect after rebooting, if the signal strength drops and the phone would want to switch from 3G to 2G, it disconnects and I have to reboot again to get mobile data. $ system-image-cli -i current build number: 200 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-04-30 11:07:21 version version: 200 version ubuntu: 20150429 version device: 20150326-f0c5ba5 version custom: 20150429 Attached you'll find the output of the forensics script To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1450790/+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 1426307] Re: location is inaccurate
With all due respect this bug is a release blocker and I think meets criteria of "Severely affects applications beyond the package responsible for the root cause" as a map cannot get your location which makes it unuseable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1426307 Title: location is inaccurate Status in the base for Ubuntu mobile products: Confirmed Status in location-service package in Ubuntu: Confirmed Status in location-service package in Ubuntu RTM: Confirmed Bug description: current build number: 122 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-02-25 15:06:29 version version: 122 version ubuntu: 20150225 version device: 20150210-95b6a9f version custom: 20150225 Location is inaccurate, it thinks that I'm several kilometres away from my actual location, in the middle of the sea. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: ubuntu-location-service-bin 2.1+15.04.20150126.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Fri Feb 27 11:10:42 2015 InstallationDate: Installed on 2015-02-25 (2 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150225-020204) SourcePackage: location-service UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.ubuntu.location.service.conf: 2015-02-10T21:38:59 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1426307/+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 1455194] [NEW] error booting
Public bug reported: goes to a purpule screen at boot ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8.4 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 Date: Thu May 14 11:52:13 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00b9] InstallationDate: Installed on 2001-01-25 (5222 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Apple Inc. MacBookPro5,5 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP55.88Z.00AC.B03.0906151708 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F2268AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8: dmi.product.name: MacBookPro5,5 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Wed May 13 14:17:50 2015 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.0-1ubuntu1.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 ubuntu utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1455194 Title: error booting Status in xorg package in Ubuntu: New Bug description: goes to a purpule screen at boot ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-33.44-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8.4 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 Date: Thu May 14 11:52:13 2015 DistUpgraded: Fresh install DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Inc. Device [106b:00b9] InstallationDate: Installed on 2001-01-25 (5222 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Apple Inc. MacBookPro5,5 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-33-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP55.88Z.00AC.B03.0906151708 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F2268AC8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F2268AC8 dmi.modalias: dmi:bvnAppleInc.:bvrMBP55.88Z.00AC.B03.0906151708:bd06/15/09:svnAppleInc.:pnMacBookPro5,5:pvr1.0:rvnAppleInc.:rnMac-F2268AC8:rvr:cvnAppleInc.:ct10:cvrMac-F2268AC8: dmi.produ
[Touch-packages] [Bug 1437375] Re: [udev] Adding "Austin" adapter to Ubuntu partition take over system network interface
This bug was fixed in the package systemd - 219-7ubuntu5 --- systemd (219-7ubuntu5) vivid; urgency=medium * Revert upstream commit 743970d which immediately SIGKILLs units during shutdown. This leads to problems like bash not being able to write its history, mosh not saving its state, and similar failed cleanup actions. (LP: #1448259) * ifup@.service: Set IgnoreOnIsolate, so that "systemctl default" does not shut down network interfaces. (LP: #1449380). Add PartOf=network.target, so that stopping network.target also stops network interfaces. * 75-persistent-net-generator.rules: Fix rules for ibmveth (it's a driver, not a subsystem). (LP: #1437375) * debian/tests/unit-config: Add tests for systemctl enable/disable on a SysV-only unit. Reproduces LP #1447807. * Fix systemctl enable for SysV scripts without a native unit. We must not try and enable the nonexisting unit then. (LP: #1447807) -- Martin Pitt Thu, 07 May 2015 07:45:34 +0200 ** Changed in: systemd (Ubuntu Vivid) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1437375 Title: [udev] Adding "Austin" adapter to Ubuntu partition take over system network interface Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Released Status in systemd source package in Wily: Fix Released Bug description: [Impact] This impacts any user of LPARs; upon adding physical network interfaces (or, realistically, any network interface at all, even virtual), the network interface which is used for system access and used to install the system may not appear in the same order after reboot. [Test Case] Requires access to logical partitions. 1) Install system 2) Add an physical network adapter to the partition 3) Reboot. Observed behavior: After reboot, the virtual adapter expected to be used is unavailable, the address is assigned to any other network adapter which may have been detected and used persistent addresses. Expected behavior The system should come up with network interfaces in the same order as before rebooting. [Regression Potential] Added virtual interfaces that should be not persist (because they are locally administered and thus may have their MAC address change) may come up as persistent devices due to the use of the ibmveth driver, and thus fail to work as expected. --- Problem Description: Adding Austin adapter to Ubuntu partition took over system network interface. This caused system to be off network connection. ver 1.5.4.3 - OS, HTX, Firmware and Machine details OS: GNU/Linux OS Version: Ubuntu Vivid Vervet (development branch) \n \l Kernel Version: 3.18.0-13-generic HTX Version: htxubuntu-322 Host Name: br14p08 Machine Serial No: IBM,0210800E7 Machine Type/Model: IBM,9119-MHE System FW Level: FW830.00 (SC830_021) BEFORE adding Austin adapter to br14p08: Before adding austin adapter to br14p05 (vio client), the system network is good. ubuntu@br14p08:~$ lsslot -cpci ubuntu@br14p08:~$ + eth0 U9119.MHE.10800E7-V8-C2-T1 Interpartition Logical LAN root@br14p08:~# lscfg |grep eth + eth0 U9119.MHE.10800E7-V8-C2-T1 root@br14p08:~# ifconfig eth0 Link encap:Ethernet HWaddr 16:59:c0:50:0a:02 inet addr:9.3.21.12 Bcast:9.3.21.255 Mask:255.255.254.0 inet6 addr: fe80::1459:c0ff:fe50:a02/64 Scope:Link inet6 addr: 2002:903:15f:290:1459:c0ff:fe50:a02/64 Scope:Global UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:37366 errors:0 dropped:16 overruns:0 frame:0 TX packets:153 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2472739 (2.4 MB) TX bytes:22596 (22.5 KB) Interrupt:19 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@br14p08:~# ping br14p08 PING br14p08.aus.stglabs.ibm.com (9.3.21.12) 56(84) bytes of data. 64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=1 ttl=64 time=0.008 ms 64 bytes from br14p08.aus.stglabs.ibm.com (9.3.21.12): icmp_seq=2 ttl=64 time=0.004 ms 64 bytes from br14p08.aus.stglab
[Touch-packages] [Bug 1410780] Re: Missing info files
The bug seems to be fixed in binutils-doc 2.24-5ubuntu13, which I just installed from trusty-proposed, i.e. the package you suggested. ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1410780 Title: Missing info files Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Trusty: Fix Committed Bug description: binutils-doc is lacking bfd.info, which is installed when building binutils from source. Arguably, this should go in binutils-dev or the non-existent binutils-dev-doc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1410780/+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 1449380] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1449380 Title: "systemctl default" stops ifup@.service Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Released Status in systemd package in Debian: Fix Released Bug description: Running the display-manager autopkgtest causes eth0 to get shut down: Apr 28 08:30:15 autopkgtest ifdown[3267]: Internet Systems Consortium DHCP Client 4.3.1 Apr 28 08:30:15 autopkgtest ifdown[3267]: Copyright 2004-2014 Internet Systems Consortium. Apr 28 08:30:15 autopkgtest ifdown[3267]: All rights reserved. Apr 28 08:30:15 autopkgtest ifdown[3267]: For info, please visit https://www.isc.org/software/dhcp/ Apr 28 08:30:15 autopkgtest ifdown[3267]: Listening on LPF/eth0/52:54:00:12:34:56 Apr 28 08:30:15 autopkgtest ifdown[3267]: Sending on LPF/eth0/52:54:00:12:34:56 Apr 28 08:30:15 autopkgtest ifdown[3267]: Sending on Socket/fallback Apr 28 08:30:15 autopkgtest dhclient[3301]: DHCPRELEASE on eth0 to 10.0.2.2 port 67 (xid=0x3ca4ea0a) Apr 28 08:30:15 autopkgtest ifdown[3267]: DHCPRELEASE on eth0 to 10.0.2.2 port 67 (xid=0x3ca4ea0a) This breaks the ssh runner. SRU TEST CASE: == - Prepare a system which uses ifupdown (e. g. a standard adt-buildvm-ubuntu-cloud VM) - Start it, run "sudo systemctl default" - With vivid final's systemd, this will stop ifup@eth0.service and hence shut down eth0. ssh and other network connections will stop. - With this fix, ifup@eth0.service and eth0 should stay running/up. Regression potential: Very low: We don't use "systemctl isolate" during regular operation, and more elaborate commands like "systemctl isolate rescue.target" are currently broken on Ubuntu anyway due to our D-Bus shutdown hack. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1449380/+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 1448259] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1448259 Title: Systemd does not send SIGTERM first on shutdown Status in systemd: Unknown Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Vivid: Fix Released Status in systemd package in Debian: Fix Committed Status in systemd package in Fedora: Unknown Bug description: It has been normal that applications first get the SIGTERM signal before SIGKILL on shutdown/reboot in order to successfully finish any pending tasks. Now it seem this logic has been changed to something else, causing problems to mosh and many others: https://bugs.launchpad.net/ubuntu/+source/mosh/+bug/1446982 SIGTERM suggestion can be seen here: http://unixhelp.ed.ac.uk/CGI/man-cgi?shutdown+8 I created this error report to find out the correct way for applications to fix this problem or to create one fix to systemd, bringing back the old "BSD shutdown" functionality. This report is for Ubuntu 15.04. SRU TEST CASE: - Open a terminal, enter some commands, then run "reboot". - After a reboot, chances are very high that your bash history does not contain your most recently typed commands - With the updated package, the bash history should be intact. REGRESSION POTENTIAL: - The original commit was applied because of an inherent race condition with cgroup's release_agent -- in rare corner cases an nspawn container (probably also LXC) can miss them. In that case it's possible that you instead get a 90s timeout on the unit that is shutting down. But this does not mean data loss, just a rare shutdown hang from containers (for the record, I never actually saw that hanging with LXC), so I think it's a good trade-off. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1448259/+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 1447807] Update Released
The verification of the Stable Release Update for systemd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1447807
Title:
systemctl enable shows error on enabling a SysV service
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Vivid:
Fix Released
Status in systemd source package in Wily:
Fix Released
Bug description:
SRU TEST CASE:
--
Trying to enable a SysV init service which does not have a corresponding
systemd unit results in an error:
# systemctl enable pulseaudio
Synchronizing state for pulseaudio.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d pulseaudio defaults
Executing /usr/sbin/update-rc.d pulseaudio enable
Failed to execute operation: No such file or directory
/etc/init.d/pulseaudio actually does get enabled (check
/etc/rc*/*pulse*), but the command fails with code 1 and you get that
error message. With the fix the command succeeds.
SRU Regression potential
Low, the modes for "sysv script + systemd unit" as well as "systemd unit
only" already have automatic tests, and now this scenario ("sysv script only")
has a test too. In the worst case this has the potential of completely breaking
systemctl enable/disable, which can be worked around with changing symlinks
manually, and isn't breaking the boot.
Version details:
Description: Ubuntu 15.04
Release: 15.04
systemd:
Installed: 219-7ubuntu3
Candidate: 219-7ubuntu3
Version table:
*** 219-7ubuntu3 0
500 http://us-west-2.ec2.archive.ubuntu.com/ubuntu/ vivid/main amd64
Packages
100 /var/lib/dpkg/status
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1447807/+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 1410780] Re: Missing info files
Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1410780 Title: Missing info files Status in binutils package in Ubuntu: Fix Released Status in binutils source package in Trusty: Fix Committed Bug description: binutils-doc is lacking bfd.info, which is installed when building binutils from source. Arguably, this should go in binutils-dev or the non-existent binutils-dev-doc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1410780/+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
