[Touch-packages] [Bug 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
refine previous comment: kill -9 $(pidof unity8) $(pidof unity8-dash) might make it once on my PC, but after that, I try many time and never success any more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in unity8 package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I kill -9 unity8 unity8-dash. But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1394850] Re: package cups 1.7.5-3ubuntu2 failed to install/upgrade: triggers looping, abandoned
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: cups (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1394850 Title: package cups 1.7.5-3ubuntu2 failed to install/upgrade: triggers looping, abandoned Status in cups package in Ubuntu: Confirmed Bug description: error happened during dist-upgrade ProblemType: Package DistroRelease: Ubuntu 15.04 Package: cups 1.7.5-3ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CupsErrorLog: W [20/Nov/2014:18:06:53 -0500] CreateProfile failed: org.freedesktop.ColorManager.AlreadyExists:profile id 'HP-LaserJet-4200-Gray..' already exists Date: Thu Nov 20 18:06:54 2014 DuplicateSignature: package:cups:1.7.5-3ubuntu2:triggers looping, abandoned ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2014-10-30 (21 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141028) Lpstat: device for HP-LaserJet-4200: socket://10.120.192.107:9100 MachineType: LENOVO 232036U Papersize: letter PpdFiles: HP-LaserJet-4200: HP LaserJet 4200 Series Postscript (recommended) ProcCmdline: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-24-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: cups Title: package cups 1.7.5-3ubuntu2 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2012 dmi.bios.vendor: LENOVO dmi.bios.version: G2ET32WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 232036U dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrG2ET32WW(1.12):bd05/30/2012:svnLENOVO:pn232036U:pvrThinkPadX230:rvnLENOVO:rn232036U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 232036U dmi.product.version: ThinkPad X230 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1394850/+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 1390919] Re: Scope template cannot be running for devel emulator
** Changed in: click (Ubuntu) Status: Incomplete = Invalid -- 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/1390919 Title: Scope template cannot be running for devel emulator Status in click package in Ubuntu: Invalid Bug description: Some libs are missing in the chroot, and the scope cannot be running for emulator (devel i386). Attached please find the captured screen. -- package 'process-cpp' not found -- package 'net-cpp=1.1.0' not found -- package 'net-cpp=1.1.0' not found -- The CXX compiler identification is GNU 4.9.1 -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++ -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found PkgConfig: /usr/bin/pkg-config (found version 0.28) -- Boost version: 1.55.0 -- checking for modules 'libunity-scopes=0.6.0;net-cpp=1.1.0' -- package 'net-cpp=1.1.0' not found CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 (_pkg_check_modules_internal) CMakeLists.txt:34 (pkg_check_modules) -- Found Gettext: /usr/bin/msgmerge (found version 0.19.2) -- Found XGettext: /usr/bin/xgettext (found version 0.19.2) CMake Error at cmake/FindGMock.cmake:6 (add_subdirectory): add_subdirectory given source /usr/src/gmock which is not an existing directory. Call Stack (most recent call first): tests/CMakeLists.txt:3 (include) -- checking for module 'process-cpp' -- package 'process-cpp' not found -- Configuring incomplete, errors occurred! See also /home/liuxg/release/build-scopetest1-UbuntuSDK_for_i386_GCC_ubuntu_sdk_14_10_utopic-Default/CMakeFiles/CMakeOutput.log. CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 (_pkg_check_modules_internal) tests/CMakeLists.txt:6 (pkg_check_modules) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1390919/+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 1391877] Re: Please implement missing 'Other Vibrations' System setting
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/serviceproperties- component -- 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/1391877 Title: Please implement missing 'Other Vibrations' System setting Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Button vibration should be driven thru the OtherVibrate settings. UITK must get the value from AccountsSettings. See bug #1358610 for further info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1391877/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
refine previous comment again, sorry: On my PC with visualization off in the bios: kill -9 $(pidof unity8) $(pidof unity8-dash) might make it once. After that, I try many time after that and never success any more. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in unity8 package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I kill -9 unity8 unity8-dash. But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1391877] Re: Please implement missing 'Other Vibrations' System setting
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/haptics-feedback- singleton-staging -- 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/1391877 Title: Please implement missing 'Other Vibrations' System setting Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Button vibration should be driven thru the OtherVibrate settings. UITK must get the value from AccountsSettings. See bug #1358610 for further info. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1391877/+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 1390919] Re: Scope template cannot be running for devel emulator
@XiaoGuo, please report your rtm version by output of command: system- image-cli -i -- 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/1390919 Title: Scope template cannot be running for devel emulator Status in click package in Ubuntu: Invalid Bug description: Some libs are missing in the chroot, and the scope cannot be running for emulator (devel i386). Attached please find the captured screen. -- package 'process-cpp' not found -- package 'net-cpp=1.1.0' not found -- package 'net-cpp=1.1.0' not found -- The CXX compiler identification is GNU 4.9.1 -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++ -- Check for working CXX compiler: /usr/bin/i686-linux-gnu-g++ -- works -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Found PkgConfig: /usr/bin/pkg-config (found version 0.28) -- Boost version: 1.55.0 -- checking for modules 'libunity-scopes=0.6.0;net-cpp=1.1.0' -- package 'net-cpp=1.1.0' not found CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 (_pkg_check_modules_internal) CMakeLists.txt:34 (pkg_check_modules) -- Found Gettext: /usr/bin/msgmerge (found version 0.19.2) -- Found XGettext: /usr/bin/xgettext (found version 0.19.2) CMake Error at cmake/FindGMock.cmake:6 (add_subdirectory): add_subdirectory given source /usr/src/gmock which is not an existing directory. Call Stack (most recent call first): tests/CMakeLists.txt:3 (include) -- checking for module 'process-cpp' -- package 'process-cpp' not found -- Configuring incomplete, errors occurred! See also /home/liuxg/release/build-scopetest1-UbuntuSDK_for_i386_GCC_ubuntu_sdk_14_10_utopic-Default/CMakeFiles/CMakeOutput.log. CMake Error at /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:283 (message): A required package was not found Call Stack (most recent call first): /usr/share/cmake-2.8/Modules/FindPkgConfig.cmake:337 (_pkg_check_modules_internal) tests/CMakeLists.txt:6 (pkg_check_modules) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1390919/+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 1397236] [NEW] After opening qpaeq, python gets stuck on 100% of CPU
Public bug reported: qpaeq is an equalizer for pulseaudio written in python. I've installed it and loaded all the required modules, but on Ubuntu 14.10 launching qpaeq from terminal does nothing; after launching it top shows that python's CPU usage is very high, with a percentage between 97 and 112. The only way to stop python from running is sudo killall python. qpaeq used to work fine on Saucy and Trusty. I think that this would happen with any python program, but I'm not sure. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Package changed: gnome-shell (Ubuntu) = python2.7 (Ubuntu) -- 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/1397236 Title: After opening qpaeq, python gets stuck on 100% of CPU Status in python2.7 package in Ubuntu: New Bug description: qpaeq is an equalizer for pulseaudio written in python. I've installed it and loaded all the required modules, but on Ubuntu 14.10 launching qpaeq from terminal does nothing; after launching it top shows that python's CPU usage is very high, with a percentage between 97 and 112. The only way to stop python from running is sudo killall python. qpaeq used to work fine on Saucy and Trusty. I think that this would happen with any python program, but I'm not sure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1397236/+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 1395862] Re: there is no media playback in vivid
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-touch-meta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1395862 Title: there is no media playback in vivid Status in Oxide Webview: Invalid Status in ubuntu-touch-meta package in Ubuntu: Confirmed Bug description: STEPS: 1. Open the Music scope in vivid 2. Click on any track in groove shark 3. select play in grooveshark 4. Browser opens with a warning 5. try and play music EXPECTED: the song plays ACTUAL nothing happens Vivid 31 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1395862/+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 1397236] Re: After opening qpaeq, python gets stuck on 100% of CPU
By mistake I reported this bug as a gnome-shell bug. Now I've corrected the description. -- 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/1397236 Title: After opening qpaeq, python gets stuck on 100% of CPU Status in python2.7 package in Ubuntu: New Bug description: qpaeq is an equalizer for pulseaudio written in python. I've installed it and loaded all the required modules, but on Ubuntu 14.10 launching qpaeq from terminal does nothing; after launching it top shows that python's CPU usage is very high, with a percentage between 97 and 112. The only way to stop python from running is sudo killall python. qpaeq used to work fine on Saucy and Trusty. I think that this would happen with any python program, but I'm not sure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1397236/+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 1370669] Re: Implement top priority features from roadmap
** Description changed: Color effects - Display image properties + Image properties (sharpness, contrast, etc.) Self timer Adjust jpeg quality Gridlines Use SD card storage Set video quality -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1370669 Title: Implement top priority features from roadmap Status in Camera App: Confirmed Status in camera-app package in Ubuntu: Confirmed Bug description: Color effects Image properties (sharpness, contrast, etc.) Self timer Adjust jpeg quality Gridlines Use SD card storage Set video quality To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1370669/+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 1213043] Re: Binding loop detected when changing backgroundColor of MainView dynamically
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/app-theming-staging -- 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/1213043 Title: Binding loop detected when changing backgroundColor of MainView dynamically Status in Sudoku game for Ubuntu Touch: Triaged Status in Weather application for Ubuntu devices: Fix Released Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: When changing the backgroundColor of MainView programmatically, a binding loop occurs: file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property style file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property style file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property target file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property style file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property target file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property target file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property style file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property style file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property target file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:192:5: QML StyledItem: Binding loop detected for property style file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property target file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:62:5: QML Binding: Binding loop detected for property target To manage notifications about this bug go to: https://bugs.launchpad.net/sudoku-app/+bug/1213043/+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 1356779] Re: MainView.backgroundColor is not usable any more
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/app-theming-staging -- 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/1356779 Title: MainView.backgroundColor is not usable any more Status in Ubuntu UX bugs: New Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: Since the latest SDK updates, MainView.backgroundColor is not usable any more. It completely messes up the whole theming: For example setting a dark background causes: * Text in Dialogs to be unreadable * Header Popovers (the new ones) to turn purple(!) * Active ListItem's text color to be unreadable And the situation seems to get worse with each uitk update... Maybe the *color properties of the MainView should just be removed? If you think that should be kept but all the places that break should be fixed instead to make it work again, please let me know and I'll do my best to collect all the places it broke. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1356779/+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 1277647] Re: Changing theme from Ambiance to SuruDark or SuruGradient in MainView's completion causes binding loops.
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/app-theming-staging
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to address-book-app in
Ubuntu.
https://bugs.launchpad.net/bugs/1277647
Title:
Changing theme from Ambiance to SuruDark or SuruGradient in MainView's
completion causes binding loops.
Status in Address Book App:
Fix Released
Status in address-book-app package in Ubuntu:
Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
In Progress
Bug description:
The following code snippet reproduces the error:
import QtQuick 2.0
import Ubuntu.Components 0.1
MainView {
width: units.gu(40)
height: units.gu(71)
Component.onCompleted: Theme.name = Ubuntu.Components.Themes.SuruDark
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/address-book-app/+bug/1277647/+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 1389792] Re: theme not found when using a user-defined theme
** Branch linked: lp:~zsombi/ubuntu-ui-toolkit/app-theming-staging -- 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/1389792 Title: theme not found when using a user-defined theme Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu RTM: In Progress Bug description: This bugs makes it so that developers cannot update the theming, which can be pretty important for some people and also important for working around color scheme issues in the theming (I've filed other bugs on this). Attached is a very simple application that tries to define the Foo theme which is derived from the SuruDark theme. $ tar -zxvf ./theme-test.tar.gz ./theme-test/ ./theme-test/themes/ ./theme-test/themes/Foo/ ./theme-test/themes/Foo/parent_theme ./theme-test/themes/Foo/Palette.qml ./theme-test/themes/Foo/MainViewStyle.qml ./theme-test/main.qml $ cd theme-test/ $ qmlscene ./main.qml Theme not found: themes.Foo QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:330:9: QML AppHeader: Warning: Style PageHeadStyle.qml not found in theme themes.Foo file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/MainView.qml:202:5: QML StyledItem: Warning: Style MainViewStyle.qml not found in theme themes.Foo QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready QQmlComponent: Component is not ready file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/Themes/Ambiance/MainViewStyle.qml:70:5: QML Binding: Binding loop detected for property target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1389792/+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 1395862] Re: there is no media playback in vivid
This bug was fixed in the package ubuntu-touch-meta - 1.201 --- ubuntu-touch-meta (1.201) vivid; urgency=medium * Refreshed dependencies * Moved oxideqt-codecs-extra to sdk-libs (LP: #1395862) -- Michael Vogt m...@ubuntu.com Fri, 28 Nov 2014 09:25:48 +0100 ** Changed in: ubuntu-touch-meta (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1395862 Title: there is no media playback in vivid Status in Oxide Webview: Invalid Status in ubuntu-touch-meta package in Ubuntu: Fix Released Bug description: STEPS: 1. Open the Music scope in vivid 2. Click on any track in groove shark 3. select play in grooveshark 4. Browser opens with a warning 5. try and play music EXPECTED: the song plays ACTUAL nothing happens Vivid 31 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1395862/+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 1397236] Re: After opening qpaeq, python gets stuck on 100% of CPU
** Summary changed: - After opening qpaeq, python gets stuck on 100% of CPU + After launching a python app, python gets stuck on 100% CPU usage -- 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/1397236 Title: After launching a python app, python gets stuck on 100% CPU usage Status in python2.7 package in Ubuntu: New Bug description: qpaeq is an equalizer for pulseaudio written in python. I've installed it and loaded all the required modules, but on Ubuntu 14.10 launching qpaeq from terminal does nothing; after launching it top shows that python's CPU usage is very high, with a percentage between 97 and 112. The only way to stop python from running is sudo killall python. qpaeq used to work fine on Saucy and Trusty. I think that this would happen with any python program, but I'm not sure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1397236/+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 1349011] Re: nm-l2tp-service needs exception in ppp ip-up/down scripts
undesirable behavior: all DNS queries go to the VPN nameservers
That is in most cases the *desired* behavior
On today's systems, I don't think so. [...] Ubuntu run a dnsmasq instance...
Rather than overwrite this...
You are right in saying that when there is a local forwarding nameserver
then it should be used (i.e., its address should be listed in
resolv.conf) instead of external nameservers.
Resolvconf is designed to implement this. If a nameserver address is
127.* or ::1 then resolvconf doesn't list any more addresses (provided
the value of the environment variable
TRUNCATE_NAMESERVER_LIST_AFTER_LOOPBACK_ADDRESS is 'y'). And if the
interface configurer follows resolvconf conventions and registers the
address using the pattern lo.CONFIGURER then resolvconf's interface
prioritization will cause a 127.* address to be listed first, and thus
listed exclusively.
Unfortunately, in Ubuntu, network-manager does not follow resolvconf
conventions. NetworkManager starts a local forwarding nameserver and
registers its listening address 127.0.1.1 under the record name
NetworkManager instead of the correct lo.NetworkManager.
Consequently NetworkManager's record has a low priority as defined by
/etc/resolvconf/interface-order instead of a high priority. Consequently
nameserver addresses registered by other interface configurers can pre-
empt NetworkManager's local forwarding nameserver address. This is a
longstanding bug in NetworkManager.
Well, if you work at home and connect to an employer's VPN,
what earthly reason is there to send them all your Internet
DNS lookups?
The only reason is that the most commonly used resolver libraries can't
route DNS traffic according to the name looked up; such a library
connects to a single nameserver which is expected to answer all queries.
The idea that the local system should know about multiple nameservers
having different information is foreign to DNS. So in general you want
to configure the resolver to contact the nameserver with the most
complete information.
Having said that, I grant that in the special case where you have a
private network with its own nameservers which have information about a
private (sub)namespace and you have a local forwarding nameserver
capable of routing DNS queries to the appropriate servers based on the
domain then there may be speed and privacy benefits to doing such
routing.
There has to be a better way of handling this than excluding every one
specifically...
If the aforementioned bug were fixed then, in the case where
NetworkManager runs a local forwarding nameserver, it wouldn't do any
harm for PPP to register nameserver addresses with resolvconf because
those addresses would have lower priority than the loopback address in
lo.NetworkManager and wouldn't end up appearing in resolv.conf.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1349011
Title:
nm-l2tp-service needs exception in ppp ip-up/down scripts
Status in resolvconf package in Ubuntu:
Confirmed
Bug description:
There is an actively maintained NetworkManager L2TP VPN plugin,
available as an Ubuntu package here: https://launchpad.net/~seriy-
pr/+archive/ubuntu/network-manager-l2tp. Hopefully it will be a part
of Ubuntu soon.
Like nm-pptp-service, it needs an exception in
/etc/ppp/ip-{up,down}.d/000resolvconf (part of the resolvconf package)
as follows:
% diff /etc/ppp/ip-up.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-up
16c16
nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
Since that's how it works for the PPTP plugin, could we add the L2TP
one as well so that it can work out of the box on Ubuntu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+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 1377332] Re: [TOPBLOCKER] UI randomly freezes
after testing the packages serge offered above from https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu- rtm/landing-003 for a day i mustr say that the device feels generally a lot more stable. except some webapp crashes that i suspect are unrelated to cgmanager the phone was stable, did not expose any hangs, lock-ups or session restarts yet. i will go on testing this over the weekend but the first impression is really good. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377332 Title: [TOPBLOCKER] UI randomly freezes Status in cgmanager package in Ubuntu: Confirmed Status in ubuntu-app-launch package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Opinion Status in ubuntu-app-launch package in Ubuntu RTM: Fix Released Status in unity8 package in Ubuntu RTM: Opinion Bug description: Summary UI randomly freezes steps: 1. unlock greeter 2. open app 3. pull down random indicator 4. close indicator 5. open app 6. swipe to view all open apps 7. open launcher 8. close some open apps 9. repeat until ui freezes device info: [service] base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/ubuntu-rtm/14.09-proposed device: krillin build_number: 79 version_detail: ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1377332/+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 1349011] Re: nm-l2tp-service needs exception in ppp ip-up/down scripts
Returning to the main issue...
Could this fix be considered for trusty-updates?
The patch is very simple and applying it involves little risk, so I'd
say yes.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1349011
Title:
nm-l2tp-service needs exception in ppp ip-up/down scripts
Status in resolvconf package in Ubuntu:
Confirmed
Bug description:
There is an actively maintained NetworkManager L2TP VPN plugin,
available as an Ubuntu package here: https://launchpad.net/~seriy-
pr/+archive/ubuntu/network-manager-l2tp. Hopefully it will be a part
of Ubuntu soon.
Like nm-pptp-service, it needs an exception in
/etc/ppp/ip-{up,down}.d/000resolvconf (part of the resolvconf package)
as follows:
% diff /etc/ppp/ip-up.d/000resolvconf
/tmp/resolvconf-1.69ubuntu1.1/debian/resolvconf.000resolvconf.ppp.ip-up
16c16
nm-l2tp-service-*|nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
---
nm-pptp-service-*|/org/freedesktop/NetworkManager/PPP/*)
Since that's how it works for the PPTP plugin, could we add the L2TP
one as well so that it can work out of the box on Ubuntu?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1349011/+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 1380914] Re: OnlineAccountsClient::Setup::exec() should execute a signon auth session
** Branch linked: lp:~mardy/ubuntu-system-settings-online-accounts/rtm- fixes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1380914 Title: OnlineAccountsClient::Setup::exec() should execute a signon auth session Status in the base for Ubuntu mobile products: Confirmed Status in Online Accounts setup for Ubuntu Touch: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu RTM: New Bug description: There is a fix to unity8 coming up that will soon be hiding the OA splash screen. Hiding the splash screen is great for 50% of the situations that it pops up, but there is a point where its actually nice to see that something is happening. With scopes, after the OnlineAccountsClient::Setup class returns from exec(), the shell then calls signon_auth_session_process_async() to request an access token. Thats when seeing the splash screen is useful as the user can see that something is still happening. With that slash screen hidden, the focus will be returned to the scope without any indication that the sign on process is still busy. Could we have the OnlineAccountsClient::Setup::exec() method execute the auth session itself before returning / sending the “finished” signal? That way you'll stay on the setup screen until the oauth token has been granted, hence returning to the scope when all is ready to go. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1380914/+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 1392380] Re: OA gives out all tokens to any app
** Branch linked: lp:~mardy/signon/rtm-fixes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1392380 Title: OA gives out all tokens to any app Status in signon package in Ubuntu: Fix Released Status in signon source package in Utopic: Confirmed Status in signon source package in Vivid: Fix Released Status in signon package in Ubuntu RTM: In Progress Bug description: The attached app will steal all your tokens. All it takes is the accounts permission in the apparmor file. Here's the code: https://pastebin.canonical.com/120398/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1392380/+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 1392380] Re: OA gives out all tokens to any app
** Changed in: signon (Ubuntu Vivid) Status: Confirmed = Fix Released ** Changed in: signon (Ubuntu RTM) Assignee: (unassigned) = Alberto Mardegan (mardy) ** Changed in: signon (Ubuntu RTM) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1392380 Title: OA gives out all tokens to any app Status in signon package in Ubuntu: Fix Released Status in signon source package in Utopic: Confirmed Status in signon source package in Vivid: Fix Released Status in signon package in Ubuntu RTM: In Progress Bug description: The attached app will steal all your tokens. All it takes is the accounts permission in the apparmor file. Here's the code: https://pastebin.canonical.com/120398/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1392380/+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 1391034] Re: SortFilterModel sorting is A-Z followed by a-z so it is not case insensitive
I'm not sure that it should be the default. Though mentioning it in the docs seems like a good idea. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Incomplete = Confirmed ** Summary changed: - SortFilterModel sorting is A-Z followed by a-z so it is not case insensitive + case insensitive SortFilterModel sorting undocumented -- 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/1391034 Title: case insensitive SortFilterModel sorting undocumented Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: In the model provided by SortFilterModel the sorting is handled such that lower case letters are after any and all items that start with an upper case letter. This produces ordering such as the following when sorting by Qt.AscendingOrder: Awesome Cool Excellent Wonderful abysmal bad wrong It would ideal if the result was a case insensitive ordering. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1391034/+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 1391034] Re: case insensitive SortFilterModel sorting undocumented
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/caseInsensitiveSort -- 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/1391034 Title: case insensitive SortFilterModel sorting undocumented Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: In the model provided by SortFilterModel the sorting is handled such that lower case letters are after any and all items that start with an upper case letter. This produces ordering such as the following when sorting by Qt.AscendingOrder: Awesome Cool Excellent Wonderful abysmal bad wrong It would ideal if the result was a case insensitive ordering. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1391034/+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 1391034] Re: case insensitive SortFilterModel sorting undocumented
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = In Progress -- 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/1391034 Title: case insensitive SortFilterModel sorting undocumented Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Bug description: In the model provided by SortFilterModel the sorting is handled such that lower case letters are after any and all items that start with an upper case letter. This produces ordering such as the following when sorting by Qt.AscendingOrder: Awesome Cool Excellent Wonderful abysmal bad wrong It would ideal if the result was a case insensitive ordering. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1391034/+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 1397319] [NEW] two sequential login windows after resuming from sleep
Public bug reported: After resuming from sleep, I sometimes (about 50%) get a first (unusual, ugly) login screen, then a short (1 sec) flash showing my desktop, then the 'normal' login screen First login window: http://oi59.tinypic.com/ws5uo9.jpg Second login window: http://oi57.tinypic.com/24xnx4w.jpg I tried the 4 sudo commands from http://ubuntuforums.org/showthread.php?t=1867733p=11626298#post11626298, but that did not update anything, so I expect that to change nothing. Then, based on http://ubuntuforums.org/showthread.php?t=1867733page=3p=12566826#post12566826, I installed and selected gdm instead of lightdm. I'll post back the results after a few days of usage. TBC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 28 14:03:32 2014 InstallationDate: Installed on 2013-09-01 (452 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-03-17 (255 days ago) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- 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/1397319 Title: two sequential login windows after resuming from sleep Status in lightdm package in Ubuntu: New Bug description: After resuming from sleep, I sometimes (about 50%) get a first (unusual, ugly) login screen, then a short (1 sec) flash showing my desktop, then the 'normal' login screen First login window: http://oi59.tinypic.com/ws5uo9.jpg Second login window: http://oi57.tinypic.com/24xnx4w.jpg I tried the 4 sudo commands from http://ubuntuforums.org/showthread.php?t=1867733p=11626298#post11626298, but that did not update anything, so I expect that to change nothing. Then, based on http://ubuntuforums.org/showthread.php?t=1867733page=3p=12566826#post12566826, I installed and selected gdm instead of lightdm. I'll post back the results after a few days of usage. TBC ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lightdm 1.10.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 28 14:03:32 2014 InstallationDate: Installed on 2013-09-01 (452 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) LightdmConfig: [SeatDefaults] user-session=ubuntu greeter-session=unity-greeter SourcePackage: lightdm UpgradeStatus: Upgraded to trusty on 2014-03-17 (255 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1397319/+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 1397316] Re: GObject signal functions make python apps crash
** Attachment removed: The backtrace from gdb https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1397316/+attachment/4270121/+files/backtrace ** Attachment added: The backtrace from gdb https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1397316/+attachment/4270130/+files/backtrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1397316 Title: GObject signal functions make python apps crash Status in Python bindings for GObject: Unknown Status in pygobject package in Ubuntu: New Bug description: Calling GObject signal functions (signal_handlers_block_matched, signal_handlers_unblock_matched and others) in a python app makes it crash. This bug has been fixed upstream for some newer versions of pygobject, but the older version (3.2.2-1~precise) in Ubuntu 12.04 is still affected. The test app (which crashes in Ubuntu 12.04) is in the attachment. Please fix it. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1397316/+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 1395011] Re: UITK Docs don't build with Qt 5.4 beta
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui- toolkit/boldLinkingforQt5.4 -- 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/1395011 Title: UITK Docs don't build with Qt 5.4 beta Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: There is some sort of error with the documentation building when building latest UITK release against Qt 5.4 beta: https://launchpadlibrarian.net/190833195/buildlog_ubuntu-vivid-amd64 .ubuntu-ui- toolkit_1.1.1311%2B15.04.2014-0ubuntu2~beta~test2_FAILEDTOBUILD.txt.gz More information about Qt test builds at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1395011/+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 1395661] Re: Qt Webkit fails to build against Qt 5.4.0 on amd64
Also with the Release Candidate: https://launchpad.net/~canonical-qt5-edgers/+archive/ubuntu/qt5-beta2/+build/6602907 ** Summary changed: - Qt Webkit fails to build against Qt 5.4.0 beta on amd64 + Qt Webkit fails to build against Qt 5.4.0 on amd64 -- 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/1395661 Title: Qt Webkit fails to build against Qt 5.4.0 on amd64 Status in qtwebkit-opensource-src package in Ubuntu: New Bug description: There's a problem with Qt WebKit (5.4.0 beta) failing to build against Qt 5.4.0 beta on amd64: https://launchpadlibrarian.net/190809157 /buildlog_ubuntu-vivid-amd64.qtwebkit-opensource-src_5.4.0~beta- 0ubuntu1~vivid1~test1_FAILEDTOBUILD.txt.gz It seems to be related to pre-compiled headers. Qttools requires qtwebkit for the documentation. In the test PPA I've disabled qttools' qtwebkit requirement in order to have more amd64 builds done in general. More information about Qt testing at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1395661/+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 1397327] [NEW] Notify OSD to dailer app on locked phone happens in slow motion on mako vivid
Public bug reported: STEPS: 1. Flash the latest Vivid image on mako 2. Let the phone sleep or tap the power button 3. Call the phone 4. The phone wakes pretty fast 5. The you swipe the notify osd to the right the answer the call 6. watch what happens next 7. Hang up 8. Close the dailer app 9. Unlock the device 10. Now with the device unlocked call it again 11. watch what happens again EXPECTED: I expected the app to open on the locked phone as smoothly and promptly as it does on the unlock phone ACTUAL: On the locked device the animations of swiping and revealing the dialer are really slow. ** Affects: dialer-app Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1397327 Title: Notify OSD to dailer app on locked phone happens in slow motion on mako vivid Status in Dialer app for Ubuntu Touch: New Status in unity8 package in Ubuntu: New Bug description: STEPS: 1. Flash the latest Vivid image on mako 2. Let the phone sleep or tap the power button 3. Call the phone 4. The phone wakes pretty fast 5. The you swipe the notify osd to the right the answer the call 6. watch what happens next 7. Hang up 8. Close the dailer app 9. Unlock the device 10. Now with the device unlocked call it again 11. watch what happens again EXPECTED: I expected the app to open on the locked phone as smoothly and promptly as it does on the unlock phone ACTUAL: On the locked device the animations of swiping and revealing the dialer are really slow. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1397327/+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 1397316] Re: GObject signal functions make python apps crash
** Changed in: pygobject Status: Unknown = Fix Released ** Changed in: pygobject Importance: Unknown = Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1397316 Title: GObject signal functions make python apps crash Status in Python bindings for GObject: Fix Released Status in pygobject package in Ubuntu: New Bug description: Calling GObject signal functions (signal_handlers_block_matched, signal_handlers_unblock_matched and others) in a python app makes it crash. This bug has been fixed upstream for some newer versions of pygobject, but the older version (3.2.2-1~precise) in Ubuntu 12.04 is still affected. The test app (which crashes in Ubuntu 12.04) is in the attachment. Please fix it. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1397316/+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 1385425] Re: add AppArmor change profile support
*** This bug is a duplicate of bug 1396270 *** https://bugs.launchpad.net/bugs/1396270 Profile changing in units works quite well now in current vivid (bug 1396270). So unless there is further information about what's still missing I'm considering this a duplicate. ** This bug has been marked a duplicate of bug 1396270 specifying AppArmorProfile doesn't result in processes launched under the named profile -- 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/1385425 Title: add AppArmor change profile support Status in systemd package in Ubuntu: Triaged Bug description: This is work to support bug #1379535 and a subtask of phase 1. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385425/+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 1179113] Re: unity crashes with Bus Error when I enable my second monitor.
Can you still reproduce the bug? Can you provide a stacktrace? ** Changed in: unity Status: Triaged = Incomplete ** Changed in: unity (Ubuntu) Status: Triaged = Incomplete -- 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/1179113 Title: unity crashes with Bus Error when I enable my second monitor. Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: My Setup: Version: Ubuntu 13.10 Video Card: ATI Radeon 2600XT on Open Source Drivers (fglrx is unavailable for this card on 13.10) Montor #1@1920x1080 Monitor #2:@1440x900 on left of Monitor #1 How to reproduce: Open Displays from the dash. Select the secondary monitor. Turn the secondary monitor off (in the settings, not the physical button on the monitor), and click Apply. Close Displays. Reopen it. Select the secondary monitor. Turn the secondary monitor on (in the settings; not on the monitor, itself.) Put the secondary monitor to the left of the primary monitor. Click Apply Expected Results: Secondary Display turns on, and I am prompted to keep my settings or revert. Actual Results: Brief screen garbage, followed by unity crashing. Whenever I try to resurrect Unity from a either VT or a terminal emulator running in X, I see Bus Error (core dumped). This continues until I end my session. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.0.0daily13.04.18~13.04-0ubuntu1 ProcVersionSignature: Ubuntu 3.9.0-1.5-generic 3.9.1 Uname: Linux 3.9.0-1-generic x86_64 ApportVersion: 2.10-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,compiztoolbox,grid,mousepoll,place,imgpng,gnomecompat,session,move,resize,regex,vpswitch,unitymtgrabhandles,animation,wall,wobbly,workarounds,fade,expo,scale,ezoom,unityshell,dbus] Date: Sat May 11 18:20:31 2013 InstallationDate: Installed on 2013-02-28 (72 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130225) MarkForUpload: True SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2013-05-05 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1179113/+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 1247564] Re: Initial window size slightly too small causing scaling+smoothing on image
Was this bug really fixed in Ubuntu? As Øyvind Stegard wrote the same bug is still present in Ubuntu 14.04. With the default theme (Ambiance, and Radiance too) the window height is 2 pixels smaller than necessary for the correct pixel to pixel display. When the theme is changed to High Contrast or the toolbar in EOG is disabled the bug does not show. 14.04 contains GTK+ 3.10.8 and the resolution from https://bugzilla.gnome.org/show_bug.cgi?id=719595 was released with GTK+ 3.10.6. In the source I see that the change from the patch is still there. Should this bug be re-opened? How to mark that the problem is not resolved in 14.04? There is also a new bug report specific to 14.04: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1296487 Should it be marked as a duplicate of this one? ** Bug watch added: GNOME Bug Tracker #719595 https://bugzilla.gnome.org/show_bug.cgi?id=719595 -- 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/1247564 Title: Initial window size slightly too small causing scaling+smoothing on image Status in Eye of GNOME: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: When opening an image that is medium sized, but still much smaller than screen resolution, eog sizes its window initially slightly too small, causing scaling and consequently smoothing to be applied to the image. This makes crisp images like figures, diagrams etc. look unnecessarily blurred (and bad) at first sight. Increasing eog window size a little fixes it so that the image is displayed 1:1 (pixel perfect). Pressing Ctrl+0 also fixes the initial sizing of the image. I see no way to turn off Best fit option by default in prefs. That would probably fix it for smaller images, but is unpractical for larger ones, where scaling is desireable. Attached source image and screenshot of initial eog window (untouched) shows the problem. My screen resolution is 1920x1200 and the source image is 640x480, so it should not have been scaled by eog on first display. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eog 3.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 3 11:47:00 2013 InstallationDate: Installed on 2013-11-01 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1247564/+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 1396244] Re: Unlocking the phone over dialer is very slow
An easy but not necessarily pretty fix is to revert the commit that
added greeter-fullscreen switching to the dialer [1]. It will leave us
with a black bar where the panel is, but that's probably better than a
jittering experience.
Of course a real fix would be better. Either make this change quicker
(do we think it's actually a complicated operation or just poorly
performant?), or only have it make the change when needed (i.e. we
actually expose the greeter) instead of every time the greeter shows.
Or both.
For the latter, we'd probably need some way to signal what's happening.
Maybe an exposed DBus property much like Active but named something
like Shown to indicate if the greeter itself is visible.
[1] http://bazaar.launchpad.net/~phablet-team/dialer-
app/trunk/revision/321
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1396244
Title:
Unlocking the phone over dialer is very slow
Status in unity8 package in Ubuntu:
Triaged
Bug description:
Steps to repro:
* have a pass{code,word}-protected phone
* start dialer
* lock the phone
* unlock the phone
Expected:
* nothing much, stuff unlocks fluently and all
Current:
* fade out of the lockscreen takes like 2-3s, dialer and panel seem to fight
over fullscreen vs. maximized surface size
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: unity8 8.01+15.04.20141117-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu10
Architecture: armhf
Date: Tue Nov 25 17:46:27 2014
InstallationDate: Installed on 2014-11-25 (0 days ago)
InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf
(20141125-020205)
SourcePackage: unity8
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396244/+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 1397327] Re: Notify OSD to dailer app on locked phone happens in slow motion on mako vivid
*** This bug is a duplicate of bug 1396244 *** https://bugs.launchpad.net/bugs/1396244 ** This bug has been marked a duplicate of bug 1396244 Unlocking the phone over dialer is very slow -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1397327 Title: Notify OSD to dailer app on locked phone happens in slow motion on mako vivid Status in Dialer app for Ubuntu Touch: New Status in unity8 package in Ubuntu: New Bug description: STEPS: 1. Flash the latest Vivid image on mako 2. Let the phone sleep or tap the power button 3. Call the phone 4. The phone wakes pretty fast 5. The you swipe the notify osd to the right the answer the call 6. watch what happens next 7. Hang up 8. Close the dailer app 9. Unlock the device 10. Now with the device unlocked call it again 11. watch what happens again EXPECTED: I expected the app to open on the locked phone as smoothly and promptly as it does on the unlock phone ACTUAL: On the locked device the animations of swiping and revealing the dialer are really slow. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1397327/+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 1397316] Re: GObject signal functions make python apps crash
** Also affects: pygobject (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: pygobject (Ubuntu) Status: New = Fix Released ** Changed in: pygobject (Ubuntu Precise) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1397316 Title: GObject signal functions make python apps crash Status in Python bindings for GObject: Fix Released Status in pygobject package in Ubuntu: Fix Released Status in pygobject source package in Precise: Triaged Bug description: Calling GObject signal functions (signal_handlers_block_matched, signal_handlers_unblock_matched and others) in a python app makes it crash. This bug has been fixed upstream for some newer versions of pygobject, but the older version (3.2.2-1~precise) in Ubuntu 12.04 is still affected. The test app (which crashes in Ubuntu 12.04) is in the attachment. Please fix it. Thanks in advance. To manage notifications about this bug go to: https://bugs.launchpad.net/pygobject/+bug/1397316/+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 1247564] Re: Initial window size slightly too small causing scaling+smoothing on image
There is also an old resolved bug #231385 from 2008 with a similar effect but probably a different cause. -- 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/1247564 Title: Initial window size slightly too small causing scaling+smoothing on image Status in Eye of GNOME: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: When opening an image that is medium sized, but still much smaller than screen resolution, eog sizes its window initially slightly too small, causing scaling and consequently smoothing to be applied to the image. This makes crisp images like figures, diagrams etc. look unnecessarily blurred (and bad) at first sight. Increasing eog window size a little fixes it so that the image is displayed 1:1 (pixel perfect). Pressing Ctrl+0 also fixes the initial sizing of the image. I see no way to turn off Best fit option by default in prefs. That would probably fix it for smaller images, but is unpractical for larger ones, where scaling is desireable. Attached source image and screenshot of initial eog window (untouched) shows the problem. My screen resolution is 1920x1200 and the source image is 640x480, so it should not have been scaled by eog on first display. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: eog 3.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 3 11:47:00 2013 InstallationDate: Installed on 2013-11-01 (1 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) MarkForUpload: True SourcePackage: eog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/eog/+bug/1247564/+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 1140716]
*** Bug 86765 has been marked as a duplicate of this bug. *** -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1140716 Title: [regression] 3.5.0-26-generic and 3.2.0-39-generic GPU hangs on Sandybridge Status in Direct Rendering Infrastructure: In Progress Status in The Linux Kernel: Invalid Status in linux package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in mesa package in Ubuntu: Triaged Status in linux source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in mesa source package in Precise: Triaged Status in linux source package in Quantal: Invalid Status in linux-lts-quantal source package in Quantal: Invalid Status in linux source package in Raring: Invalid Status in linux-lts-quantal source package in Raring: Invalid Status in linux package in Debian: New Status in linux package in Fedora: Unknown Bug description: I'm getting errors about GPU hangs every minute or so (usually only when using FF and scrolling a webpage or something). I also get an annoying ubuntu dialog saying there is a system error. This didn't happen with 3.5.0-24-generic. Here is the dmesg: [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26285.658405] [ cut here ] [26285.658472] WARNING: at /build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 gen6_enable_rps+0x706/0x710 [i915]() [26285.658474] Hardware name: SATELLITE Z830 [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc lp parport e1000e ahci libahci [last unloaded: sdhci] [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic #40-Ubuntu [26285.658539] Call Trace: [26285.658549] [81051bef] warn_slowpath_common+0x7f/0xc0 [26285.658553] [81051c4a] warn_slowpath_null+0x1a/0x20 [26285.658569] [a02d32e6] gen6_enable_rps+0x706/0x710 [i915] [26285.658584] [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915] [26285.658595] [a02954b4] i915_reset+0x1a4/0x6e0 [i915] [26285.658601] [8101257b] ? __switch_to+0x12b/0x420 [26285.658612] [a029a943] i915_error_work_func+0xc3/0x110 [i915] [26285.658618] [8107097a] process_one_work+0x12a/0x420 [26285.658629] [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915] [26285.658632] [8107152e] worker_thread+0x12e/0x2f0 [26285.658636] [81071400] ? manage_workers.isra.26+0x200/0x200 [26285.658640] [81076023] kthread+0x93/0xa0 [26285.658644] [8168a3e4] kernel_thread_helper+0x4/0x10 [26285.658649] [81075f90] ? kthread_freezable_should_stop+0x70/0x70 [26285.658652] [8168a3e0] ? gs_change+0x13/0x13 [26285.658654] ---[ end trace 59c6162fdfcbffee ]--- [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
[Touch-packages] [Bug 1397065] Re: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: dbus (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1397065 Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in dbus package in Ubuntu: Confirmed Bug description: I don't know what it is, my computer said to report the bug and I did it. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: dbus 1.8.8-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Thu Nov 27 18:32:47 2014 DuplicateSignature: package:dbus:1.8.8-1ubuntu2.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-03-08 (264 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: dbus Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-09-27 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1397065/+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 1397065] Re: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
(synaptic:14598): GLib-CRITICAL **: g_child_watch_add_full: assertion 'pid 0' failed Selecting previously unselected package gir1.2-nautilus-3.0. (Reading database ... 377668 files and directories currently installed.) Preparing to unpack .../gir1.2-nautilus-3.0_1%3a3.10.1-0ubuntu15_amd64.deb ... Unpacking gir1.2-nautilus-3.0 (1:3.10.1-0ubuntu15) ... Selecting previously unselected package python-nautilus. Preparing to unpack .../python-nautilus_1.1-4_amd64.deb ... Unpacking python-nautilus (1.1-4) ... Selecting previously unselected package clamtk-nautilus. Preparing to unpack .../clamtk-nautilus_5.10-1_all.deb ... Unpacking clamtk-nautilus (5.10-1) ... Setting up dbus (1.8.8-1ubuntu2.1) ... insserv: warning: script 'K20.depend.stop' missing LSB tags and overrides insserv: warning: script 'K20.depend.boot' missing LSB tags and overrides insserv: warning: script 'K20.depend.start' missing LSB tags and overrides insserv: There is a loop at service rc.local if started insserv: There is a loop between service rc.local and urandom if started insserv: loop involving service urandom at depth 4 insserv: loop involving service hwclock at depth 3 insserv: There is a loop between service .depend.stop and udev if started insserv: loop involving service udev at depth 1 insserv: There is a loop between service .depend.stop and rc.local if started insserv: loop involving service rc.local at depth 2 insserv: loop involving service .depend.stop at depth 1 insserv: loop involving service rsyslog at depth 1 insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.boot depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.start depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.boot depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.start depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.boot depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.start depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.boot depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.start depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.boot depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.start depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.boot depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.start depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.boot depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.start depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.boot depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.start depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.boot depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.start depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.stop depends on rc.local and therefore on system facility `$all' which can not be true! insserv: Starting .depend.boot depends on rc.local and therefore on system facility `$all' which can not be true! insserv:
[Touch-packages] [Bug 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
this looks like something to add to developer docs -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1396919 Title: unity8 display blank in emulator, host utopic, rtm-14.09 instance. Status in unity8 package in Ubuntu: Confirmed Bug description: As run emulator, device screen is blank. Step to reproduce: 1. install utopic. 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 3. sudo apt-get install ubuntu-sdk 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 5. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I kill -9 unity8 unity8-dash. But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1396919/+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 1397340] [NEW] Integer overflow when processing giant field values
Public bug reported: Ubuntu release: 12.04 Package version: 0.1.33 When parsing fields in a crash report file, whoopsie will reallocate the value buffer when appending continuation lines. The current length of the buffer is computed by pointer arithmetic and the result stored in a signed integer. If the field value length reaches 2GB, then this value will overflow, and become negative. This will then cause whoopsie itself to abort, as it tries to allocate a huge amount of memory. I would expect whoopsie to cope with such large input (which may be generated as the result of a memory-hungry process crashing and creating a very large compressed+base64-encoded CoreDump). By inspection, I see that this issue is still present in current development versions: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/vivid/whoopsie/vivid/view/head:/src/whoopsie.c#L402 I've attached a patch (created against the 0.1.33 sources, but should apply with minimal issues against later versions), that resolves the immediate issue. There's a more general question about the sanity of loading the entire crash file into memory, too (particularly as the CoreDump is never used unless the server requests it). ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Patch added: whoopsie.patch https://bugs.launchpad.net/bugs/1397340/+attachment/4270149/+files/whoopsie.patch -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1397340 Title: Integer overflow when processing giant field values Status in whoopsie package in Ubuntu: New Bug description: Ubuntu release: 12.04 Package version: 0.1.33 When parsing fields in a crash report file, whoopsie will reallocate the value buffer when appending continuation lines. The current length of the buffer is computed by pointer arithmetic and the result stored in a signed integer. If the field value length reaches 2GB, then this value will overflow, and become negative. This will then cause whoopsie itself to abort, as it tries to allocate a huge amount of memory. I would expect whoopsie to cope with such large input (which may be generated as the result of a memory-hungry process crashing and creating a very large compressed+base64-encoded CoreDump). By inspection, I see that this issue is still present in current development versions: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/vivid/whoopsie/vivid/view/head:/src/whoopsie.c#L402 I've attached a patch (created against the 0.1.33 sources, but should apply with minimal issues against later versions), that resolves the immediate issue. There's a more general question about the sanity of loading the entire crash file into memory, too (particularly as the CoreDump is never used unless the server requests it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1397340/+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 1377332] Re: [TOPBLOCKER] UI randomly freezes
13:14 ogra_ stgraber, soo ... that gcmanager fix from hallyn looks reallly good, the phone seems a lot more stable ... we are wondering what the implications are if we would use the 0.32 cgmmanager in rtm though ... would there be any drawbacks with the old lxc version we use ? 13:15 sil2100 stgraber: hey! We've been wondering, would everything be ok to use the new cgmanager (from utopic) in rtm? 15:15 stgraber ogra_, sil2100: I don't expect any problem with current LXC and new cgmanager 15:15 stgraber the only time where lxc talks to cgmanager on the phone is at container startup and you've tested that a few times already. LXC itself does cgmanager API version detection at runtime so there's also no need to rebuild it or anything 15:15 ogra_ stgraber, oh, thats awesome, could you note that in the bug ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377332 Title: [TOPBLOCKER] UI randomly freezes Status in cgmanager package in Ubuntu: Confirmed Status in ubuntu-app-launch package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Opinion Status in ubuntu-app-launch package in Ubuntu RTM: Fix Released Status in unity8 package in Ubuntu RTM: Opinion Bug description: Summary UI randomly freezes steps: 1. unlock greeter 2. open app 3. pull down random indicator 4. close indicator 5. open app 6. swipe to view all open apps 7. open launcher 8. close some open apps 9. repeat until ui freezes device info: [service] base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/ubuntu-rtm/14.09-proposed device: krillin build_number: 79 version_detail: ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cgmanager/+bug/1377332/+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 1397344] [NEW] Give 217 some more testing
Public bug reported: I don't have the guts to upload 217 on a Friday evening and let it propagate, so let's hold it in -proposed over the weekend. It should also be tested on Ubuntu Touch first. I tested it in Qemu and on my laptop. ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Martin Pitt (pitti) Status: In Progress ** Tags: block-proposed ** Changed in: systemd (Ubuntu) Status: New = In Progress ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) ** Tags added: block-proposed -- 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/1397344 Title: Give 217 some more testing Status in systemd package in Ubuntu: In Progress Bug description: I don't have the guts to upload 217 on a Friday evening and let it propagate, so let's hold it in -proposed over the weekend. It should also be tested on Ubuntu Touch first. I tested it in Qemu and on my laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397344/+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 1397348] [NEW] GT215 crash PGRAPH TLB flush idle timeout fail
Public bug reported: I'm using ubuntu 14.04 LTS, as well as tried to load 15.04 dev build downloaded today. Display showing black and white rectangles with some color noise. When in switch to text i see errors from nouveau driver telling PGRAPH TLB flush idle timeout fail. And i see it is happening in infinite loop. the only way to me to boot into X is to use nomodeset. I dont want install nvidia proprietary drivers, since i will need to use Xen later and it won't work with them. Description:Ubuntu 14.04.1 LTS Release:14.04 xserver-xorg-video-nouveau: Installed: 1:1.0.10-1ubuntu2 Candidate: 1:1.0.10-1ubuntu2 Version table: *** 1:1.0.10-1ubuntu2 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.5 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 CurrentDmesg: [ 32.027037] init: plymouth-upstart-bridge main process ended, respawning [ 60.120737] audit_printk_skb: 132 callbacks suppressed [ 60.120740] type=1400 audit(1417187362.092:62): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2358 comm=apparmor_parser [ 60.120747] type=1400 audit(1417187362.092:63): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2358 comm=apparmor_parser [ 60.121191] type=1400 audit(1417187362.092:64): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2358 comm=apparmor_parser Date: Fri Nov 28 18:11:23 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff50] InstallationDate: Installed on 2014-11-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA Qosmio X505 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=UUID=fc1ea7a5-ebe4-412b-a55a-6e47c007c4ec ro nomodeset vga=795 quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.90 dmi.board.name: Qosmio X505 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.90:bd12/10/2010:svnTOSHIBA:pnQosmioX505:pvrPQX33U-01J00H:rvnTOSHIBA:rnQosmioX505:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Qosmio X505 dmi.product.version: PQX33U-01J00H dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Nov 28 18:08:52 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- 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/1397348 Title: GT215 crash PGRAPH TLB flush idle timeout fail Status in xorg package in Ubuntu: New Bug description: I'm using ubuntu 14.04 LTS, as well as tried to load 15.04 dev build downloaded today. Display showing black and white rectangles with some color noise. When in switch to text i see errors from nouveau driver telling PGRAPH TLB flush idle timeout fail. And i see it is happening in infinite loop. the only way to me to boot into X is to use nomodeset. I dont want install nvidia proprietary drivers, since i will need to use Xen later and it won't work with them. Description: Ubuntu 14.04.1 LTS Release: 14.04
[Touch-packages] [Bug 1392380] Re: OA gives out all tokens to any app
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1392380 Title: OA gives out all tokens to any app Status in the base for Ubuntu mobile products: New Status in signon package in Ubuntu: Fix Released Status in signon source package in Utopic: Confirmed Status in signon source package in Vivid: Fix Released Status in signon package in Ubuntu RTM: In Progress Bug description: The attached app will steal all your tokens. All it takes is the accounts permission in the apparmor file. Here's the code: https://pastebin.canonical.com/120398/ To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1392380/+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 1396471] Re: glibc vulnerability CVE-2014-7817
** Also affects: eglibc (Ubuntu Vivid) Importance: Undecided Status: Confirmed ** Also affects: eglibc (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: glibc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1396471 Title: glibc vulnerability CVE-2014-7817 Status in eglibc package in Ubuntu: Confirmed Status in glibc package in Ubuntu: New Status in eglibc source package in Lucid: New Status in glibc source package in Lucid: New Status in eglibc source package in Precise: New Status in glibc source package in Precise: New Status in eglibc source package in Trusty: New Status in glibc source package in Trusty: New Status in eglibc source package in Utopic: New Status in glibc source package in Utopic: New Status in eglibc source package in Vivid: Confirmed Status in glibc source package in Vivid: New Bug description: http://www.cvedetails.com/cve-details.php?t=1cve_id=CVE-2014-7817 https://security-tracker.debian.org/tracker/CVE-2014-7817 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1396471/+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 1376445] Re: Addition of signon-apparmor-extension causes token lookup problems
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1376445 Title: Addition of signon-apparmor-extension causes token lookup problems Status in the base for Ubuntu mobile products: New Status in go-onlineaccounts: Incomplete Status in The Savilerow project: Invalid Status in ACL for signond, AppArmor backend: Fix Released Status in Online Accounts setup for Ubuntu Touch: In Progress Status in ubuntu-system-settings-online-accounts package in Ubuntu: In Progress Status in ubuntuone-credentials package in Ubuntu: Confirmed Status in signon-apparmor-extension package in Ubuntu RTM: Triaged Status in ubuntu-system-settings-online-accounts package in Ubuntu RTM: New Status in ubuntuone-credentials package in Ubuntu RTM: Confirmed Bug description: As of image ~264 of ubuntu-touch, the signon-apparmor-extension package is included. As a result, apps like pay-ui cannot find the token any longer, and are not being notified that they are not allowed to access the token. The following error appears in the payui log file: 2014-10-01 19:15:51,550 - DEBUG - ../../../../lib/SignOn/authsessionimpl.cpp 184 errorSlot QDBusError(com.google.code.AccountsSSO.SingleSignOn.Error.PermissionDenied, Client has insuficient permissions to access the service.Method:getAuthSessionObjectPath) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1376445/+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 1397361] [NEW] Failed to try-restart systemd-resolved.service:
Public bug reported: This bug is filed against the latest systemd (217-1ubuntu1) in the Vivid branch. When upgrading to this version, this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1397361 Title: Failed to try-restart systemd-resolved.service: Status in systemd package in Ubuntu: New Bug description: This bug is filed against the latest systemd (217-1ubuntu1) in the Vivid branch. When upgrading to this version, this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+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 1397361] Re: Failed to try-restart systemd-resolved.service:
More info on my setup: I only use systemd booting with init=/lib/systemd/systemd kernel booting line. I have upstart, cgmanager and systemd-shim purged. -- 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/1397361 Title: Failed to try-restart systemd-resolved.service: Status in systemd package in Ubuntu: New Bug description: This bug is filed against the latest systemd (217-1ubuntu1) in the Vivid branch. When upgrading to this version, this is the warning message I get: Failed to try-restart systemd-resolved.service: Unit systemd-resolved.service failed to load: No such file or directory. However, the systemd (217) works itself fine with no issues, it is only this installation message the bug is about. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1397361/+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 1236749] Re: Gnome shell extensions disabled at every startup
I tried Comments #12 and #57 but they didnt work . Can we add this extensions to startup applications ? Unfortunately i cant use startup on tweak tool because it doesnt work (i think it must be broken). Ubuntu 14.10 Gnome 3.14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1236749 Title: Gnome shell extensions disabled at every startup Status in Ubuntu GNOME: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in upstart package in Ubuntu: Confirmed Bug description: Since gnome-shell 3.10, my extensions are disabled by default at every boot. I need to launch Tweak Tool to enable theme by hand every time. Both pre-installed extensions ( AlternateTab) and user-installed ones (top-icons) Step to reproduce : Enable an extension in Tweak Tool ( Alternate Tab for example) reboot computer, open Tweak Tool : Alternate tab is disabled. Running on Ubuntu 13.10 GNOME Shell 3.10.0.1 gnome-tweak-tool 3.10..0-0ubuntu1-saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1236749/+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 1397340] Re: Integer overflow when processing giant field values
The attachment whoopsie.patch 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 whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1397340 Title: Integer overflow when processing giant field values Status in whoopsie package in Ubuntu: New Bug description: Ubuntu release: 12.04 Package version: 0.1.33 When parsing fields in a crash report file, whoopsie will reallocate the value buffer when appending continuation lines. The current length of the buffer is computed by pointer arithmetic and the result stored in a signed integer. If the field value length reaches 2GB, then this value will overflow, and become negative. This will then cause whoopsie itself to abort, as it tries to allocate a huge amount of memory. I would expect whoopsie to cope with such large input (which may be generated as the result of a memory-hungry process crashing and creating a very large compressed+base64-encoded CoreDump). By inspection, I see that this issue is still present in current development versions: http://bazaar.launchpad.net/~ubuntu- branches/ubuntu/vivid/whoopsie/vivid/view/head:/src/whoopsie.c#L402 I've attached a patch (created against the 0.1.33 sources, but should apply with minimal issues against later versions), that resolves the immediate issue. There's a more general question about the sanity of loading the entire crash file into memory, too (particularly as the CoreDump is never used unless the server requests it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1397340/+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 1396471] Re: glibc vulnerability CVE-2014-7817
** Changed in: eglibc (Ubuntu Lucid) Importance: Undecided = Medium ** Changed in: eglibc (Ubuntu Lucid) Status: New = Confirmed ** Changed in: eglibc (Ubuntu Lucid) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) ** Changed in: eglibc (Ubuntu Precise) Importance: Undecided = Medium ** Changed in: eglibc (Ubuntu Precise) Status: New = Confirmed ** Changed in: eglibc (Ubuntu Precise) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) ** Changed in: eglibc (Ubuntu Trusty) Importance: Undecided = Medium ** Changed in: eglibc (Ubuntu Trusty) Status: New = Confirmed ** Changed in: eglibc (Ubuntu Trusty) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) ** Changed in: eglibc (Ubuntu Utopic) Status: New = Invalid ** Changed in: eglibc (Ubuntu Vivid) Status: Confirmed = Invalid ** Changed in: glibc (Ubuntu Lucid) Status: New = Invalid ** Changed in: glibc (Ubuntu Precise) Status: New = Invalid ** Changed in: glibc (Ubuntu Trusty) Status: New = Invalid ** Changed in: glibc (Ubuntu Utopic) Importance: Undecided = Medium ** Changed in: glibc (Ubuntu Utopic) Status: New = Confirmed ** Changed in: glibc (Ubuntu Utopic) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) ** Changed in: glibc (Ubuntu Vivid) Importance: Undecided = Medium ** Changed in: glibc (Ubuntu Vivid) Status: New = Confirmed ** Changed in: glibc (Ubuntu Vivid) Assignee: (unassigned) = adicarlo (adam) ** Changed in: glibc (Ubuntu Vivid) Assignee: adicarlo (adam) = Adam Conrad (adconrad) ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2014-7817 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1396471 Title: glibc vulnerability CVE-2014-7817 Status in eglibc package in Ubuntu: Invalid Status in glibc package in Ubuntu: Confirmed Status in eglibc source package in Lucid: Confirmed Status in glibc source package in Lucid: Invalid Status in eglibc source package in Precise: Confirmed Status in glibc source package in Precise: Invalid Status in eglibc source package in Trusty: Confirmed Status in glibc source package in Trusty: Invalid Status in eglibc source package in Utopic: Invalid Status in glibc source package in Utopic: Confirmed Status in eglibc source package in Vivid: Invalid Status in glibc source package in Vivid: Confirmed Bug description: http://www.cvedetails.com/cve-details.php?t=1cve_id=CVE-2014-7817 https://security-tracker.debian.org/tracker/CVE-2014-7817 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1396471/+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 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
FWIW, the package in utopic-proposed fixes the issue for me. I'm not marking as verification-done, as I would really like for someone else who is affected by this bug to test it also. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in nfs-utils package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Confirmed Status in nfs-utils source package in Utopic: Fix Committed Status in upstart source package in Utopic: Confirmed Status in nfs-utils source package in Vivid: Fix Released Status in upstart source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+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 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
@Ricardo, I'm added copious amounts of debug into the kernel and a shim on umount too and I can't see /dev/mmcblk023 being unmounted anywhere. Can you inform me where to expect this umount is actioned on shutdown. I just can't see it. With full journaling on I'd expect this to cope with a non-umount as it can replay the journaled data and metadata and so we don't get errors, however, with the data=ordered option I could expect to see metadata being perhaps sane where as the file data being not written back and hence we see old data and possibly the reason for this corruption. So, I'd really like to have some idea where the umount actually occurs. The debug shows me: boot -- initrd -- mount /dev/mmcpblk023 onto /tmpmnt and then [5.142499] mount: /root/userdata [5.142591] do_mount: /tmpmnt - /root/userdata [null] [5.143811] do_mount return - 0 But for the life of me, I can't see this being unmounted. So that's my concern, it may not be umounted and hence the root cause of the data corruption. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in android package in Ubuntu: Fix Released Status in android-tools package in Ubuntu: In Progress Status in initramfs-tools-ubuntu-touch package in Ubuntu: Fix Released Status in linux-mako package in Ubuntu: Confirmed Status in android package in Ubuntu RTM: Fix Released Status in android-tools package in Ubuntu RTM: In Progress Status in initramfs-tools-ubuntu-touch package in Ubuntu RTM: Fix Released Status in linux-mako package in Ubuntu RTM: Confirmed Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet
[Touch-packages] [Bug 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
I agree we'll need to look into this, but can we lower the priority now that we know enabling virtualization (which most even remotely modern CPUs have) makes it go away? ** Also affects: goget-ubuntu-touch (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1396919 Title: unity8 display blank in emulator when virtualization disabled Status in goget-ubuntu-touch package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: Emulator screen remains blank when virtualization is disabled. Step to reproduce: 1. disable virtualization support in your BIOS 2. install utopic. 3. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 4. sudo apt-get install ubuntu-sdk 5. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 6. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I kill -9 unity8 unity8-dash. But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1396919/+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 1396919] Re: unity8 display blank in emulator when virtualization disabled
Oh and btw, instead of forcefully killing unity8, you can just `restart unity8` it (unity8-dash will get restarted with it). Or to restart the whole session, `sudo restart lightdm`. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1396919 Title: unity8 display blank in emulator when virtualization disabled Status in goget-ubuntu-touch package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: Emulator screen remains blank when virtualization is disabled. Step to reproduce: 1. disable virtualization support in your BIOS 2. install utopic. 3. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 4. sudo apt-get install ubuntu-sdk 5. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 6. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I kill -9 unity8 unity8-dash. But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1396919/+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 1396919] Re: unity8 display blank in emulator, host utopic, rtm-14.09 instance.
Adding ubuntu-emulator task, it's still not clear what actually prevents the rendering. And maybe emulator should warn about missing virtualization caps? ** Summary changed: - unity8 display blank in emulator, host utopic, rtm-14.09 instance. + unity8 display blank in emulator when virtualization disabled ** Description changed: - As run emulator, device screen is blank. + Emulator screen remains blank when virtualization is disabled. Step to reproduce: - 1. install utopic. - 2. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa - 3. sudo apt-get install ubuntu-sdk - 4. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 - 5. create device instance i386 / rtm-14.09 and launch it. + 1. disable virtualization support in your BIOS + 2. install utopic. + 3. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa + 4. sudo apt-get install ubuntu-sdk + 5. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 + 6. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I kill -9 unity8 unity8-dash. But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1396919 Title: unity8 display blank in emulator when virtualization disabled Status in goget-ubuntu-touch package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: Emulator screen remains blank when virtualization is disabled. Step to reproduce: 1. disable virtualization support in your BIOS 2. install utopic. 3. sudo add-apt-repository ppa:ubuntu-sdk-team/ppa 4. sudo apt-get install ubuntu-sdk 5. launch ubuntu-sdk and install chroot:click-ubuntu-sdk-14.10-armhf, and chroot:click-ubuntu-sdk-14.10-i386 6. create device instance i386 / rtm-14.09 and launch it. Expected result: See ubuntu phone UI there. Current result: Emulator screen is black. Extra Note: 1. On the pc, in the first run of the instance, I can see phone interface on first boot after I kill -9 unity8 unity8-dash. But this work around failed as I stop the instance and run again. I even create the same instance with the other name and try this work around, still can't see anything on the screen. 2. I can run test_glesv2 and see the result on the screen of the display correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/goget-ubuntu-touch/+bug/1396919/+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 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
So just to re-iterate: 1. I believe the file system is not being cleanly umounted. 2. data=journal saved us from disaster because it works so well. My recommendation is to keep data=journal because a user can power off the device (battery death, pulling out battery, random kernel reboot, etc) and data=journal has conclusively shown it the only RELIABLE way to ensure data and metadata are sane. I really would like to warn against fixing this bug by doing the umount and changing back to the faster but definitely less rugged data=ordered option. I think that would really be too risky IMHO. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in android package in Ubuntu: Fix Released Status in android-tools package in Ubuntu: In Progress Status in initramfs-tools-ubuntu-touch package in Ubuntu: Fix Released Status in linux-mako package in Ubuntu: Confirmed Status in android package in Ubuntu RTM: Fix Released Status in android-tools package in Ubuntu RTM: In Progress Status in initramfs-tools-ubuntu-touch package in Ubuntu RTM: Fix Released Status in linux-mako package in Ubuntu RTM: Confirmed Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh #testscript=/home/bug/test-with-true.sh The kernel team has verified the above reproducer
[Touch-packages] [Bug 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
The fix in proposed fixed this problem on two separate boxes for me. Would be great to see this in the main repository. thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in nfs-utils package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Confirmed Status in nfs-utils source package in Utopic: Fix Committed Status in upstart source package in Utopic: Confirmed Status in nfs-utils source package in Vivid: Fix Released Status in upstart source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+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 1391296] Re: 14.10: NFS drives in fstab not mounted automatically
** 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 upstart in Ubuntu. https://bugs.launchpad.net/bugs/1391296 Title: 14.10: NFS drives in fstab not mounted automatically Status in nfs-utils package in Ubuntu: Fix Released Status in upstart package in Ubuntu: Confirmed Status in nfs-utils source package in Utopic: Fix Committed Status in upstart source package in Utopic: Confirmed Status in nfs-utils source package in Vivid: Fix Released Status in upstart source package in Vivid: Confirmed Bug description: [SRU Request] Due to a change in Upstart behaviour, the statd daemon no longer starts automatically at boot, resulting in nfs mounts not being mounted at boot. This has been corrected by modifying the statd upstart job to wait for the rpcbind job to start, instead of waiting for the compatibility portmap event. [Test Case] 1- set up an NFS mount in /etc/fstab 2- Reboot, notice the directory didn't get mounted 3- Install update 4- Reboot, notice the directory is mounted [Regression Potential] The upstart jobs to get the proper daemons started up at boot have complex relationships, and have suffered from race conditions in the past. Although this change is small, it may slightly change previous behaviour. Of course, not having it work at all is worse than having a possible race condition, so this fix is unlikely to be any worse than the broken behaviour. Original description: After upgrading to 14.10 (fresh install) my NFS drive does no longer mounts automatically at boot when the network is up and running. Manually running mount -a mounts the drive as expected and hacking a mount -a command into mountall-net.conf makes my system function normally again. Trying to manually to killall -USR1 mountall does not work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mountall 2.54build1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 10 20:37:39 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-11-09 (1 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic root=UUID=e1197618-b55d-40d3-9b81-df2dcb847c1f ro quiet splash vt.handoff=7 SourcePackage: mountall UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.init.mountall.net.conf: 2014-11-10T20:26:00.795161 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1391296/+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 1387214] Re: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem
I don't thing we're seeing many writes to that partition, most of it's probably data pages being flushed out in the background so it's not going to bite too hard. We do have tools to figure out how much is being written if it needs some analysis. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools-ubuntu- touch in Ubuntu. https://bugs.launchpad.net/bugs/1387214 Title: [TOPBLOCKER] file corruption on touch images in rw portions of the filesystem Status in android package in Ubuntu: Fix Released Status in android-tools package in Ubuntu: In Progress Status in initramfs-tools-ubuntu-touch package in Ubuntu: Fix Released Status in linux-mako package in Ubuntu: Confirmed Status in android package in Ubuntu RTM: Fix Released Status in android-tools package in Ubuntu RTM: In Progress Status in initramfs-tools-ubuntu-touch package in Ubuntu RTM: Fix Released Status in linux-mako package in Ubuntu RTM: Confirmed Bug description: Symptoms are that cache files in /var/cache/apparmor and profiles in /var/lib/apparmor/profiles are sometimes corrupted after a reboot. We've already fixed several bugs in the apparmor and click-apparmor and made both more robust in the face of corruption and we've reduced the impact when there is a corrupted profile, but we've still not found the cause of the corruption. This corruption can still affect real-world devices: if a profile in /var/lib/apparmor/profiles is corrupted and the cache file is out of date, then the profile won't compile and that app/scope won't start. Workaround: remove the affected profile and then run 'sudo aa- clickhook'. This obviously is not viable on an end-user device. The investigation is ongoing and this may not be a problem with the kernel at all, so this bug may be retargeted to another project. The security team and the kernel team have discussed this a lot and Colin King is currently looking at this. This bug is just so it can be tracked. Here is an excerpt from my latest email to Colin: I believe I have conclusively ruled out apparmor_parser and aa- clickhook by creating a new 'home/bug/test-with-true.sh'. Here is the test output: http://paste.ubuntu.com/8648109/ Specifically, home/bug/test-with-true.sh changes the interesting parts of the algorithm to: 1. wait for unity8 to start (this ensures the apparmor upstart job is finished) 2. restore apparmor_parser and aa-clickhook, if needed 3. if /home/bug/profiles... exists, perform a diff -Naur /home/bug/profiles... /var/lib/apparmor/profiles and fail if differences (note, apparmor_parser and aa-clickhook were /bin/true during boot so they could not have changed /var/lib/apparmor/profiles) 4. verify the profiles, exit with error if they do not 5. alternately upgrade/downgrade the packages 6. verify the profiles, exit with error if they do not 7. copy the known good profiles in the previous step to /home/bug/profiles... 8. have apparmor_parser and aa-clickhook point to /bin/true 9. reboot 10. go to step 1 In the paste you'll notice that in step 6 the profiles were successfully created by the installation of the packages, then verified, then copied aside, then apparmor_parser and aa-clickhook diverted, then rebooted, only to have the profiles in /var/lib/apparmor/profiles be different than what was copied aside. It would be nice to verify on your device as well (I reproduced several times here) and verify the reproducer algorithm. I think this suggests this is a kernel issue and not userspace. IMPORTANT: you will want to update the reproducer and refollow all of these steps (ie, I updated the scripts, the debs, the sudoers file, etc): $ wget http://people.canonical.com/~jamie/cking/aa-corruption.tar.gz $ tar -zxvf ./aa-corruption.tar.gz ... $ adb push ./aa-corruption.tar.gz /tmp $ adb shell phablet@ubuntu-phablet:~$ cd /tmp phablet@ubuntu-phablet:~$ tar -zxvf ./aa-corruption.tar.gz phablet@ubuntu-phablet:~$ sudo mount -o remount,rw / phablet@ubuntu-phablet:~$ sudo cp ./aa-corruption/etc/sudoers.d/phablet /etc/sudoers.d/ phablet@ubuntu-phablet:~$ sudo mount -o remount,ro / phablet@ubuntu-phablet:~$ sudo cp -a ./aa-corruption/home/bug /home phablet@ubuntu-phablet:~$ exit $ cd ./aa-corruption $ ./test-from-host.sh ... The old script is still in place. Simply adjust ./test-from-host.sh to have: testscript=/home/bug/test.sh #testscript=/home/bug/test-with-true.sh The kernel team has verified the above reproducer and symptoms. Related bugs: * bug 1371771 * bug 1371765 * bug 1377338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1387214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe :
[Touch-packages] [Bug 1397410] [NEW] TextField isn't rendering correctly ubuntu-rtm
Public bug reported: At some point in the development cycle, TextFields stopped rendering correctly on actual devices and in the emulator. Attached are two screenshots: desktop.png is what the textfield look like on the desktop, and emulator.png is what they look like on the emulator. Code to display those textfields is here: http://bazaar.launchpad.net/~mdeslaur/tipcalc/trunk/view/head:/tipcalc.qml#L203 ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- 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/1397410 Title: TextField isn't rendering correctly ubuntu-rtm Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: At some point in the development cycle, TextFields stopped rendering correctly on actual devices and in the emulator. Attached are two screenshots: desktop.png is what the textfield look like on the desktop, and emulator.png is what they look like on the emulator. Code to display those textfields is here: http://bazaar.launchpad.net/~mdeslaur/tipcalc/trunk/view/head:/tipcalc.qml#L203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1397410/+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 1397410] Re: TextField isn't rendering correctly ubuntu-rtm
** Attachment added: desktop.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1397410/+attachment/4270296/+files/desktop.png -- 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/1397410 Title: TextField isn't rendering correctly ubuntu-rtm Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: At some point in the development cycle, TextFields stopped rendering correctly on actual devices and in the emulator. Attached are two screenshots: desktop.png is what the textfield look like on the desktop, and emulator.png is what they look like on the emulator. Code to display those textfields is here: http://bazaar.launchpad.net/~mdeslaur/tipcalc/trunk/view/head:/tipcalc.qml#L203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1397410/+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 1397410] Re: TextField isn't rendering correctly ubuntu-rtm
** Attachment added: emulator.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1397410/+attachment/4270297/+files/emulator.png -- 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/1397410 Title: TextField isn't rendering correctly ubuntu-rtm Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: At some point in the development cycle, TextFields stopped rendering correctly on actual devices and in the emulator. Attached are two screenshots: desktop.png is what the textfield look like on the desktop, and emulator.png is what they look like on the emulator. Code to display those textfields is here: http://bazaar.launchpad.net/~mdeslaur/tipcalc/trunk/view/head:/tipcalc.qml#L203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1397410/+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 1397410] Re: TextField isn't rendering correctly ubuntu-rtm
This issue exists both in the emulator, and on a nexus 4. -- 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/1397410 Title: TextField isn't rendering correctly ubuntu-rtm Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: At some point in the development cycle, TextFields stopped rendering correctly on actual devices and in the emulator. Attached are two screenshots: desktop.png is what the textfield look like on the desktop, and emulator.png is what they look like on the emulator. Code to display those textfields is here: http://bazaar.launchpad.net/~mdeslaur/tipcalc/trunk/view/head:/tipcalc.qml#L203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1397410/+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 1397410] Re: TextField isn't rendering correctly ubuntu-rtm
FYI, I can confirm the device and emulator matched the style of textfields on the desktop last time I uploaded the app, which was on August 13th, so something changed since then. -- 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/1397410 Title: TextField isn't rendering correctly ubuntu-rtm Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: At some point in the development cycle, TextFields stopped rendering correctly on actual devices and in the emulator. Attached are two screenshots: desktop.png is what the textfield look like on the desktop, and emulator.png is what they look like on the emulator. Code to display those textfields is here: http://bazaar.launchpad.net/~mdeslaur/tipcalc/trunk/view/head:/tipcalc.qml#L203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1397410/+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 1397415] [NEW] App icons remain in Dash after uninstallation, or total inability to run app from Dash.
Public bug reported: I have two icons which remain after unistalling the application. This also happened on my previous 32bit Utopic with Skype creating two icons: one which worked, and one which was like the screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Nov 28 19:20:53 2014 InstallationDate: Installed on 2014-11-14 (14 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: This is a screenshot of an application's icon remaining after an uninstall with purge, restart, and even manual menu remove using tool. https://bugs.launchpad.net/bugs/1397415/+attachment/4270302/+files/Screenshot%20from%202014-11-28%2012%3A51%3A18.png -- 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/1397415 Title: App icons remain in Dash after uninstallation, or total inability to run app from Dash. Status in unity package in Ubuntu: New Bug description: I have two icons which remain after unistalling the application. This also happened on my previous 32bit Utopic with Skype creating two icons: one which worked, and one which was like the screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-26.34-generic 3.16.7-ckt1 Uname: Linux 3.16.0-26-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Nov 28 19:20:53 2014 InstallationDate: Installed on 2014-11-14 (14 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) 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/1397415/+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 1372665] Re: apport reports suspend/resume failure twice on boot (apportcheckresume)
With apport 2.14.1-0ubuntu3.5, I get two error dialogues on boot but one crash file in /var/crash/. With 2.14.1-0ubuntu3.6 in trusty-proposed, I get one dialogue and one crash file. I think this is the same problem as in this bug, and the proposed package fixes it for me. ** 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 apport in Ubuntu. https://bugs.launchpad.net/bugs/1372665 Title: apport reports suspend/resume failure twice on boot (apportcheckresume) Status in apport package in Ubuntu: Fix Released Status in apport source package in Trusty: Fix Committed Bug description: Test Case - 1) sudo touch /var/lib/pm-utils/status 2) reboot 3) observe two susres named crash reports in /var/crash/ With the version of apport from trusty-proposed you will only have one crash report in /var/crash. Something has regressed to cause my laptop to not resume from suspend. But in addition, this has exposed a bug in apportcheckresume, which is reporting the resume failure twice in a row. $ ls -l /var/crash/susres.2014-09-22_15\:00\:53.7*.crash -rw-r- 1 root whoopsie 1314658 Sep 22 15:02 /var/crash/susres.2014-09-22_15:00:53.767701.crash -rw-r- 1 root whoopsie 1314630 Sep 22 15:01 /var/crash/susres.2014-09-22_15:00:53.780433.crash $ As I certainly did not have two resume failures within a second of one another, I think this is an apportcheckresume bug. ProblemType: BugDistroRelease: Ubuntu 14.10 Package: apport 2.14.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 ApportLog: ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Mon Sep 22 15:15:14 2014 InstallationDate: Installed on 2010-09-24 (1459 days ago)InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) PackageArchitecture: allSourcePackage: apport UpgradeStatus: Upgraded to utopic on 2014-05-23 (122 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1372665/+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 1397348] Re: GT215 crash PGRAPH TLB flush idle timeout fail
** Tags added: latest-bios-2.90 ** Summary changed: - GT215 crash PGRAPH TLB flush idle timeout fail + [Toshiba Qosmio X505-Q880] GT215 crash PGRAPH TLB flush idle timeout fail -- 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/1397348 Title: [Toshiba Qosmio X505-Q880] GT215 crash PGRAPH TLB flush idle timeout fail Status in xorg package in Ubuntu: New Bug description: I'm using ubuntu 14.04 LTS, as well as tried to load 15.04 dev build downloaded today. Display showing black and white rectangles with some color noise. When in switch to text i see errors from nouveau driver telling PGRAPH TLB flush idle timeout fail. And i see it is happening in infinite loop. the only way to me to boot into X is to use nomodeset. I dont want install nvidia proprietary drivers, since i will need to use Xen later and it won't work with them. Description: Ubuntu 14.04.1 LTS Release: 14.04 xserver-xorg-video-nouveau: Installed: 1:1.0.10-1ubuntu2 Candidate: 1:1.0.10-1ubuntu2 Version table: *** 1:1.0.10-1ubuntu2 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.5 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 CurrentDmesg: [ 32.027037] init: plymouth-upstart-bridge main process ended, respawning [ 60.120737] audit_printk_skb: 132 callbacks suppressed [ 60.120740] type=1400 audit(1417187362.092:62): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2358 comm=apparmor_parser [ 60.120747] type=1400 audit(1417187362.092:63): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2358 comm=apparmor_parser [ 60.121191] type=1400 audit(1417187362.092:64): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2358 comm=apparmor_parser Date: Fri Nov 28 18:11:23 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff50] InstallationDate: Installed on 2014-11-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA Qosmio X505 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=UUID=fc1ea7a5-ebe4-412b-a55a-6e47c007c4ec ro nomodeset vga=795 quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.90 dmi.board.name: Qosmio X505 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias: dmi:bvnTOSHIBA:bvrV2.90:bd12/10/2010:svnTOSHIBA:pnQosmioX505:pvrPQX33U-01J00H:rvnTOSHIBA:rnQosmioX505:rvrNotApplicable:cvnTOSHIBA:ct10:cvrN/A: dmi.product.name: Qosmio X505 dmi.product.version: PQX33U-01J00H dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Nov 28 18:08:52 2014 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1397348/+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 1367883] [udev/precise] possible regression found
As a part of the Stable Release Updates quality process a search for Launchpad bug reports using the version of udev from precise-proposed was performed and bug 1397221 was found. Please investigate this bug report to ensure that a regression will not be created by this SRU. In the event that this is not a regression remove the verification-failed tag from this bug report and tag 1397221 bot-stop-nagging. Thanks! ** Tags added: verification-failed -- 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/1367883 Title: [SRU] Add Microsoft-owned MAC address to 75-persistent-net- generator.rules Status in systemd package in Ubuntu: Fix Released Status in udev package in Ubuntu: Invalid Status in udev source package in Precise: Fix Committed Status in systemd source package in Trusty: Fix Released Bug description: Impact: As Microsoft expands its public cloud offering it may need to utilize additional MAC address prefixes. If a user launches a Cloud instance when the MAC address is from a Microsoft-owned MAC address that is not in the exclusion list, eth0 is persistently named for the first NIC seen. If a user rebundles, or the machines has its MAC address changed (e.g. VM resize or VM is moved to another host), it will lose network connectivity. Fix: Please add the following Microsoft-owned MAC address to the 75 -persistent-net-generator.rules file: 00:25:ae Microsoft Corporation Test Case : - Launch Hyper-V VM with MAC address with prefix 00:25:ae - Install updated Udev/systemd - Delete any existing udev rule - Reboot and confirm that no new UDEV rule was added To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1367883/+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 1397410] Re: TextField isn't rendering correctly ubuntu-rtm
Those textfields are read-only. I think it is intentional (as requested by design), that these textfields don't look like textfields any more. It was done to fix this bug https://bugs.launchpad.net/ubuntu/+source /ubuntu-ui-toolkit/+bug/1370571 -- 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/1397410 Title: TextField isn't rendering correctly ubuntu-rtm Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: At some point in the development cycle, TextFields stopped rendering correctly on actual devices and in the emulator. Attached are two screenshots: desktop.png is what the textfield look like on the desktop, and emulator.png is what they look like on the emulator. Code to display those textfields is here: http://bazaar.launchpad.net/~mdeslaur/tipcalc/trunk/view/head:/tipcalc.qml#L203 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1397410/+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 1397348] Re: [Toshiba Qosmio X505-Q880] GT215 crash PGRAPH TLB flush idle timeout fail
Anton Viktorov, thank you for reporting this and helping make Ubuntu better. Could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags: kernel-fixed-upstream kernel-fixed-upstream-VERSION-NUMBER where VERSION-NUMBER is the version number of the kernel you tested exactly shown as: kernel-fixed-upstream-3.18-rc6 This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. If the mainline kernel does not fix this bug, please add the following tags: kernel-bug-exists-upstream kernel-bug-exists-upstream-VERSION-NUMBER Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding. ** Tags added: vivid ** Package changed: xorg (Ubuntu) = linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided = Low ** Changed in: linux (Ubuntu) Status: New = Incomplete -- 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/1397348 Title: [Toshiba Qosmio X505-Q880] GT215 crash PGRAPH TLB flush idle timeout fail Status in linux package in Ubuntu: Incomplete Bug description: I'm using ubuntu 14.04 LTS, as well as tried to load 15.04 dev build downloaded today. Display showing black and white rectangles with some color noise. When in switch to text i see errors from nouveau driver telling PGRAPH TLB flush idle timeout fail. And i see it is happening in infinite loop. the only way to me to boot into X is to use nomodeset. I dont want install nvidia proprietary drivers, since i will need to use Xen later and it won't work with them. Description: Ubuntu 14.04.1 LTS Release: 14.04 xserver-xorg-video-nouveau: Installed: 1:1.0.10-1ubuntu2 Candidate: 1:1.0.10-1ubuntu2 Version table: *** 1:1.0.10-1ubuntu2 0 500 http://ru.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.5 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 CurrentDmesg: [ 32.027037] init: plymouth-upstart-bridge main process ended, respawning [ 60.120737] audit_printk_skb: 132 callbacks suppressed [ 60.120740] type=1400 audit(1417187362.092:62): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/lib/cups/backend/cups-pdf pid=2358 comm=apparmor_parser [ 60.120747] type=1400 audit(1417187362.092:63): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2358 comm=apparmor_parser [ 60.121191] type=1400 audit(1417187362.092:64): apparmor=STATUS operation=profile_replace profile=unconfined name=/usr/sbin/cupsd pid=2358 comm=apparmor_parser Date: Fri Nov 28 18:11:23 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215M [GeForce GTS 360M] [10de:0cb1] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:ff50] InstallationDate: Installed on 2014-11-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: TOSHIBA Qosmio X505 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=UUID=fc1ea7a5-ebe4-412b-a55a-6e47c007c4ec ro nomodeset vga=795 quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/10/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: V2.90 dmi.board.name: Qosmio X505 dmi.board.vendor: TOSHIBA dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: N/A dmi.modalias:
[Touch-packages] [Bug 1397433] [NEW] Statistics test fails on PowerPC
Public bug reported: The stats test fails on PowerPC due to non-normal distribution. Looks like there are outliers in the distribution. ** Affects: unity-scopes-api (Ubuntu) Importance: Undecided Status: New ** Attachment added: failed-test.gz https://bugs.launchpad.net/bugs/1397433/+attachment/4270336/+files/failed-test.gz -- 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/1397433 Title: Statistics test fails on PowerPC Status in unity-scopes-api package in Ubuntu: New Bug description: The stats test fails on PowerPC due to non-normal distribution. Looks like there are outliers in the distribution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1397433/+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 1397435] [NEW] Running apport on a server terminal using lynx fails the SSO with a 403 after machine authorization
Public bug reported: I was asked to run apport-collect to report a bug on one of my servers. That server has lynx installed as the default web browser. The SSO process failed after the step where I authorize this server to send information on my behalf (I chose to allow for a week); submitting that form took me to a 403 page. This might be an SSO bug. ** Affects: apport (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1397435 Title: Running apport on a server terminal using lynx fails the SSO with a 403 after machine authorization Status in apport package in Ubuntu: New Bug description: I was asked to run apport-collect to report a bug on one of my servers. That server has lynx installed as the default web browser. The SSO process failed after the step where I authorize this server to send information on my behalf (I chose to allow for a week); submitting that form took me to a 403 page. This might be an SSO bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1397435/+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 1397435] Re: Running apport on a server terminal using lynx fails the SSO with a 403 after machine authorization
I should have noted I have 2FA in place. The page it's posting to and getting a 403 is https://launchpad.net /+authorize-token The actual error page reads: No REFERER Header Launchpad requires a REFERER header to perform this action. There is no REFERER header present. This can be caused by configuring your browser to block REFERER headers. Unblock REFERER headers for launchpad.net and try again, or see the FAQ Why does Launchpad require a REFERER header? for more information. You can also join the #launchpad IRC support channel on chat.freenode.net for further assistance. Launchpad • Take the tour • Read the guide Search Launchpad © 2004-2014 Canonical Ltd. • Terms of use • Contact Launchpad Support • Blog • Careers • System status • r17267 (Get the code!) IFRAME: javascript:void(0); -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1397435 Title: Running apport on a server terminal using lynx fails the SSO with a 403 after machine authorization Status in apport package in Ubuntu: New Bug description: I was asked to run apport-collect to report a bug on one of my servers. That server has lynx installed as the default web browser. The SSO process failed after the step where I authorize this server to send information on my behalf (I chose to allow for a week); submitting that form took me to a 403 page. This might be an SSO bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1397435/+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 1397444] [NEW] Ubuntu secondary screen is not working properly (screenshot attached)
Public bug reported: I am running two screens for my Ubuntu: External Screen is main screen and Laptop (smaller) screen is secondary screen. I am using NVIDIA drivers. Screenshot attached. Please doctors do anything you can because the patient is losing its one eye :) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 28 23:22:08 2014 DistUpgraded: 2014-06-20 20:04:19,980 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:181d] NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:181d] InstallationDate: Installed on 2013-10-01 (423 days ago) InstallationMedia: Ubuntu-Server 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.2) MachineType: Hewlett-Packard HP ENVY dv7 Notebook PC ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-40-generic root=/dev/mapper/hostname--vg-root ro SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to trusty on 2014-06-20 (161 days ago) dmi.bios.date: 09/03/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 181D dmi.board.vendor: Hewlett-Packard dmi.board.version: 52.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd09/03/2012:svnHewlett-Packard:pnHPENVYdv7NotebookPC:pvr088A1130592620100:rvnHewlett-Packard:rn181D:rvr52.23:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.name: HP ENVY dv7 Notebook PC dmi.product.version: 088A1130592620100 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Nov 28 13:51:04 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 882 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 corruption trusty ubuntu ** Attachment added: Resolution in secondary screen is messed up https://bugs.launchpad.net/bugs/1397444/+attachment/4270359/+files/Screenshot%20from%202014-11-28%2023%3A20%3A43.png -- 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/1397444 Title: Ubuntu secondary screen is not working properly (screenshot attached) Status in xorg package in Ubuntu: New Bug description: I am running two screens for my Ubuntu: External Screen is main screen and Laptop (smaller) screen is secondary screen. I am using NVIDIA drivers. Screenshot attached. Please doctors do anything you can because the patient is losing its one eye :) ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-40.69-generic 3.13.11.10 Uname: Linux 3.13.0-40-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error:
[Touch-packages] [Bug 1383468] Re: Windows in non-focused workspaces have not decorations in expo
This bug was fixed in the package unity - 7.3.1+15.04.20141128-0ubuntu1 --- unity (7.3.1+15.04.20141128-0ubuntu1) vivid; urgency=low [ Andrea Azzarone ] * Unmap all windows during shutdown. (LP: #1370017, #1375271) * Make sure GetScreenGeometry returns the correct value. (LP: #1374785) [ Marco Trevisan (Treviño) ] * Decorated Window: still paint decorations if on transformated windows in different workspaces (LP: #1383468) * DecoratedWindow: make sure we always set a _NET_FRAME_EXTENTS for windows that requested it * UnityScreen: when filtering out windows in spread, make sure we unscale them (LP: #1316265) * PanelMenuView: ensure that proper window tiles and buttons are shown at the right place (LP: #1384958, #1384910, #1385285) * PanelService: inject special key events back to the root window when a menu is opened * PanelService: use gdbus to notfy upstart of service start/stop -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 28 Nov 2014 12:56:28 + ** Changed in: unity (Ubuntu) Status: In Progress = 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/1383468 Title: Windows in non-focused workspaces have not decorations in expo Status in Unity: In Progress Status in unity package in Ubuntu: Fix Released Bug description: 1. Open multiple windows and put them in different workspaces 2. Hit Super+S to open the expo 3. Notice that windows that are not in the focused workspaces have no decorations To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1383468/+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 1375271] Re: desktop or other past screen contents visible before lockscreen on resume
This bug was fixed in the package unity - 7.3.1+15.04.20141128-0ubuntu1 --- unity (7.3.1+15.04.20141128-0ubuntu1) vivid; urgency=low [ Andrea Azzarone ] * Unmap all windows during shutdown. (LP: #1370017, #1375271) * Make sure GetScreenGeometry returns the correct value. (LP: #1374785) [ Marco Trevisan (Treviño) ] * Decorated Window: still paint decorations if on transformated windows in different workspaces (LP: #1383468) * DecoratedWindow: make sure we always set a _NET_FRAME_EXTENTS for windows that requested it * UnityScreen: when filtering out windows in spread, make sure we unscale them (LP: #1316265) * PanelMenuView: ensure that proper window tiles and buttons are shown at the right place (LP: #1384958, #1384910, #1385285) * PanelService: inject special key events back to the root window when a menu is opened * PanelService: use gdbus to notfy upstart of service start/stop -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 28 Nov 2014 12:56:28 + ** Changed in: unity (Ubuntu) Status: In Progress = 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/1375271 Title: desktop or other past screen contents visible before lockscreen on resume Status in GNOME Screensaver: New Status in Unity: In Progress Status in unity package in Ubuntu: Fix Released Bug description: This appears to be a regression in 14.10 sometime in September 2014. The behavior appears similar to this bug from 2011: https://bugs.launchpad.net/unity-2d/+bug/830348 On resume from suspend, screen contents are displayed for a brief time (perhaps 0.5 to 1 sec) before the lock dialog appears. These screen contents are not always the desktop or open application beneath the lock screen. On at least one occasion, the screen showed content from a full-screen video that had been playing in Firefox some time before the computer had been suspended: neither the video nor its underlying tab were open anymore, so the image(s) was likely part of a buffer somewhere. (Needless to say, if the wrong full-screen video had been watched, depending on the setting, this could be a quite serious issue for some users). I have not exhaustively tested conditions in which this appears. However, just now, the bug did not appear when keeping the lid open, suspending, and then resuming with the power button. But when suspending from menu, closing the lid, then opening the lid and moving the mouse, the screen displayed contents before showing the lock dialog. The image displayed was of the desktop (with this bug reporting window) and showed the suspend item in the power menu being highlighted/clicked. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20140915-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon Sep 29 08:38:57 2014 InstallationDate: Installed on 2014-08-10 (50 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-08-10 (50 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/1375271/+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 1384910] Re: Switching maximized windows using the spread might lead to wrong title and positioning
This bug was fixed in the package unity - 7.3.1+15.04.20141128-0ubuntu1 --- unity (7.3.1+15.04.20141128-0ubuntu1) vivid; urgency=low [ Andrea Azzarone ] * Unmap all windows during shutdown. (LP: #1370017, #1375271) * Make sure GetScreenGeometry returns the correct value. (LP: #1374785) [ Marco Trevisan (Treviño) ] * Decorated Window: still paint decorations if on transformated windows in different workspaces (LP: #1383468) * DecoratedWindow: make sure we always set a _NET_FRAME_EXTENTS for windows that requested it * UnityScreen: when filtering out windows in spread, make sure we unscale them (LP: #1316265) * PanelMenuView: ensure that proper window tiles and buttons are shown at the right place (LP: #1384958, #1384910, #1385285) * PanelService: inject special key events back to the root window when a menu is opened * PanelService: use gdbus to notfy upstart of service start/stop -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 28 Nov 2014 12:56:28 + ** Changed in: unity (Ubuntu) Status: In Progress = 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/1384910 Title: Switching maximized windows using the spread might lead to wrong title and positioning Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: 1. Open at least two maximized windows 2. Select one of the windows (last opened seems better) 3. Hit Super + W 4. Start writing to select the other(s) window opened 5. Select it, hitting enter. The title will be wrong (the one of the previous title) while the window buttons will be in the wrong position (see attached sreenshot, in LIM mode, or empty panel otherwise). To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1384910/+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 1384958] Re: Ubuntu Desktop title is moved right as the window buttons were there
This bug was fixed in the package unity - 7.3.1+15.04.20141128-0ubuntu1 --- unity (7.3.1+15.04.20141128-0ubuntu1) vivid; urgency=low [ Andrea Azzarone ] * Unmap all windows during shutdown. (LP: #1370017, #1375271) * Make sure GetScreenGeometry returns the correct value. (LP: #1374785) [ Marco Trevisan (Treviño) ] * Decorated Window: still paint decorations if on transformated windows in different workspaces (LP: #1383468) * DecoratedWindow: make sure we always set a _NET_FRAME_EXTENTS for windows that requested it * UnityScreen: when filtering out windows in spread, make sure we unscale them (LP: #1316265) * PanelMenuView: ensure that proper window tiles and buttons are shown at the right place (LP: #1384958, #1384910, #1385285) * PanelService: inject special key events back to the root window when a menu is opened * PanelService: use gdbus to notfy upstart of service start/stop -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 28 Nov 2014 12:56:28 + ** Changed in: unity (Ubuntu) Status: In Progress = 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/1384958 Title: Ubuntu Desktop title is moved right as the window buttons were there Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: 1. Open a maximized window 2. Hit Super+s 3. The Ubuntu Desktop title is moved some pixels to the right, as shown in the attached screenshot To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1384958/+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 1374785] Re: Screen-saver fade-to-black does not cover entire screen on HiDPI
This bug was fixed in the package unity - 7.3.1+15.04.20141128-0ubuntu1 --- unity (7.3.1+15.04.20141128-0ubuntu1) vivid; urgency=low [ Andrea Azzarone ] * Unmap all windows during shutdown. (LP: #1370017, #1375271) * Make sure GetScreenGeometry returns the correct value. (LP: #1374785) [ Marco Trevisan (Treviño) ] * Decorated Window: still paint decorations if on transformated windows in different workspaces (LP: #1383468) * DecoratedWindow: make sure we always set a _NET_FRAME_EXTENTS for windows that requested it * UnityScreen: when filtering out windows in spread, make sure we unscale them (LP: #1316265) * PanelMenuView: ensure that proper window tiles and buttons are shown at the right place (LP: #1384958, #1384910, #1385285) * PanelService: inject special key events back to the root window when a menu is opened * PanelService: use gdbus to notfy upstart of service start/stop -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 28 Nov 2014 12:56:28 + ** Changed in: unity (Ubuntu) Status: In Progress = 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/1374785 Title: Screen-saver fade-to-black does not cover entire screen on HiDPI Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: Display summary: 3840x2160 display with 2x UI scaling The fade-to-black which occurs prior to the screen shutting off only covers the top left quarter of the screen. When scaling is set to 1x, the entire screen fades to black. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.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 CurrentDesktop: Unity Date: Sat Sep 27 11:37:13 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-35-generic, x86_64: installed bbswitch, 0.7, 3.13.0-36-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-35-generic, x86_64: installed nvidia-331-updates, 331.38, 3.13.0-36-generic, x86_64: installed EcryptfsInUse: Yes GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-09-19 (7 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: LENOVO 20378 ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-3.13.0-36-generic.efi.signed root=UUID=f869a790-cf94-4a68-a435-9ebdc95b4166 ro rootflags=subvol=@ quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/16/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ECN30WW(V1.13) dmi.board.asset.tag: 31900058WIN dmi.board.name: Lenovo Y50-70 dmi.board.vendor: LENOVO dmi.board.version: 31900058WIN dmi.chassis.asset.tag: 31900058WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Y50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ECN30WW(V1.13):bd07/16/2014:svnLENOVO:pn20378:pvrLenovoY50-70:rvnLENOVO:rnLenovoY50-70:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoY50-70: dmi.product.name: 20378 dmi.product.version: Lenovo Y50-70 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 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.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Sat Sep 27 10:15:35 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 18514 vendor SDC xserver.version: 2:1.15.1-0ubuntu2.1 To manage notifications about this bug go to:
[Touch-packages] [Bug 1316265] Re: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering
This bug was fixed in the package unity - 7.3.1+15.04.20141128-0ubuntu1 --- unity (7.3.1+15.04.20141128-0ubuntu1) vivid; urgency=low [ Andrea Azzarone ] * Unmap all windows during shutdown. (LP: #1370017, #1375271) * Make sure GetScreenGeometry returns the correct value. (LP: #1374785) [ Marco Trevisan (Treviño) ] * Decorated Window: still paint decorations if on transformated windows in different workspaces (LP: #1383468) * DecoratedWindow: make sure we always set a _NET_FRAME_EXTENTS for windows that requested it * UnityScreen: when filtering out windows in spread, make sure we unscale them (LP: #1316265) * PanelMenuView: ensure that proper window tiles and buttons are shown at the right place (LP: #1384958, #1384910, #1385285) * PanelService: inject special key events back to the root window when a menu is opened * PanelService: use gdbus to notfy upstart of service start/stop -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 28 Nov 2014 12:56:28 + ** Changed in: unity (Ubuntu) Status: In Progress = 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/1316265 Title: Maximized Window's Title Bar Does Not Merge into Menu Bar after Performing Super+W (window spread) filtering Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: A maximized application's title bar does not merge into the menu bar once a user has performed Super + W (window slide). Note that if one does not do Super+E, then the bars to merge together. However, once Super+E has been performed, this bug persists for the lifetime of the windowed application. If the application is restarted after doing Super+E, then the bug is gone. Thus, it seems like Super+E introduces this bug for the lifetime of the windowed application. Expected behavior: Maximized window's title bar is merged into menu bar. Observed: Does not occur after Super+W is performed. Try this out using Terminal. ProblemType: BugDistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Mon May 5 14:48:01 2014 InstallationDate: Installed on 2013-09-08 (239 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424)SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1316265/+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 1397374] [NEW] Adding repository via PackageKit D-Bus interface does not work
You have been subscribed to a public bug: I am on Ubuntu Utopic (14.10) and want to do the following, preferably with a Python script. I want to install a printer driver package from Epson (which is available as both DEB and RPM) through its apt or yum repository so that future updates get installed automatically through the distro's update mechanism. I also want to assure by means of a key fingerprint that repository and package are really from Epson. The package name for example is epson-inkjet-printer-escpr The key fingerprint is E5220FB7014D0FBDA50DFC2BE5E86C008AA65D56 and the Debian package repository is deb http://download.ebz.epson.net/dsc/op/stable/debian/ lsb3.2 main This data is polled from OpenPrinting: https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL :EP-801A%20Series;DES:EPSON%20EP-801A%20Series;CLS:PRINTER; You can replace the packagesystem=deb in the URL by packagesystem=rpm for RPM-based distros. Now I run a script of system-config-printer, /usr/share/system-config-printer/install-printerdriver.py via the command install-printerdriver 'epson-inkjet-printer-escpr' 'deb http://download.ebz.epson.net/dsc/op/stable/debian/ lsb3.2 main' 'E5220FB7014D0FBDA50DFC2BE5E86C008AA65D56' Or by pasting the commands at the python prompt: till@till-twist:~/ubuntu/system-config-printer/test$ python3 Python 3.4.2 (default, Oct 8 2014, 13:08:17) [GCC 4.9.1] on linux Type help, copyright, credits or license for more information. from gi.repository import GLib, PackageKitGlib import sys def progress(progress, type, user_data): ... pass ... pk = PackageKitGlib.Client() repo = 'deb http://download.ebz.epson.net/dsc/op/stable/debian/ lsb3.2 main' res = pk.repo_enable(repo, True, None, progress, None) And I get Could not found the repositorie And if I do pkcon repo-enable 'deb http://download.ebz.epson.net/dsc/op/stable/debian/ lsb3.2 main' I get the same error. I tried also with other repositories, even ones which are already added to the system and always get this error. How do I add a repository with PackageKit? till@till-twist:~/ubuntu/system-config-printer/test$ pkcon backend-details Name: aptcc Description:APTcc Author: Daniel Nicoletti dantt...@gmail.com till@till-twist:~/ubuntu/system-config-printer/test$ Another problem is installing the signature. Formerly repo_gpg_id = E5220FB7014D0FBDA50DFC2BE5E86C008AA65D56 res = pk.install_signature(PackageKitGlib.SigTypeEnum.GPG, repo_gpg_id, '', None, progress, None) worked (note the empty string for the package ID). Now a package ID is required, and to obtain it I have to add the repository, but is it not a security problem to already add the repository if the signature is not yet installed? This all still worked on Trusty (14.04). Is there a problem with the Python bindings of the client (perhaps due to Python3)? Or is perhaps the D-Bus service (aptdaemon on Ubuntu) at fault? ** Affects: packagekit (Ubuntu) Importance: Low Status: New -- Adding repository via PackageKit D-Bus interface does not work https://bugs.launchpad.net/bugs/1397374 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. -- 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 1397374] Re: Adding repository via PackageKit D-Bus interface does not work
Sorry, on my system there was for some reason, perhaps some experiments several months ago, installed the original PackageKit D-Bus service (packagekit binary package) and not the Ubuntu standard PackageKit D-Bus service emulation using aptdaemon (python3-aptdaemon.pkcompat binary package). aptdaemon was installed, giving me the impression that it was used. This caused the bug to occur and after returning to the standard setup with python3-aptdaemon.pkcompat the bug went away. So the bug is most probably in the packagekit package and most users are stillhaving automatic printer driver installation working, so moving to packagekit and lowering importance ... ** Changed in: aptdaemon (Ubuntu) Importance: High = Low ** Package changed: aptdaemon (Ubuntu) = packagekit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1397374 Title: Adding repository via PackageKit D-Bus interface does not work Status in packagekit package in Ubuntu: New Bug description: I am on Ubuntu Utopic (14.10) and want to do the following, preferably with a Python script. I want to install a printer driver package from Epson (which is available as both DEB and RPM) through its apt or yum repository so that future updates get installed automatically through the distro's update mechanism. I also want to assure by means of a key fingerprint that repository and package are really from Epson. The package name for example is epson-inkjet-printer-escpr The key fingerprint is E5220FB7014D0FBDA50DFC2BE5E86C008AA65D56 and the Debian package repository is deb http://download.ebz.epson.net/dsc/op/stable/debian/ lsb3.2 main This data is polled from OpenPrinting: https://www.openprinting.org/query.cgi?moreinfo=1showprinterid=1onlynewestdriverpackages=0architectures=amd64noobsoletes=1onlyfree=0onlymanufacturer=0onlydownload=1packagesystem=debonlysigneddriverpackages=0format=xmltype=driversprinter=MFG:EPSON;MDL :EP-801A%20Series;DES:EPSON%20EP-801A%20Series;CLS:PRINTER; You can replace the packagesystem=deb in the URL by packagesystem=rpm for RPM-based distros. Now I run a script of system-config-printer, /usr/share/system-config-printer/install-printerdriver.py via the command install-printerdriver 'epson-inkjet-printer-escpr' 'deb http://download.ebz.epson.net/dsc/op/stable/debian/ lsb3.2 main' 'E5220FB7014D0FBDA50DFC2BE5E86C008AA65D56' Or by pasting the commands at the python prompt: till@till-twist:~/ubuntu/system-config-printer/test$ python3 Python 3.4.2 (default, Oct 8 2014, 13:08:17) [GCC 4.9.1] on linux Type help, copyright, credits or license for more information. from gi.repository import GLib, PackageKitGlib import sys def progress(progress, type, user_data): ... pass ... pk = PackageKitGlib.Client() repo = 'deb http://download.ebz.epson.net/dsc/op/stable/debian/ lsb3.2 main' res = pk.repo_enable(repo, True, None, progress, None) And I get Could not found the repositorie And if I do pkcon repo-enable 'deb http://download.ebz.epson.net/dsc/op/stable/debian/ lsb3.2 main' I get the same error. I tried also with other repositories, even ones which are already added to the system and always get this error. How do I add a repository with PackageKit? till@till-twist:~/ubuntu/system-config-printer/test$ pkcon backend-details Name: aptcc Description: APTcc Author: Daniel Nicoletti dantt...@gmail.com till@till-twist:~/ubuntu/system-config-printer/test$ Another problem is installing the signature. Formerly repo_gpg_id = E5220FB7014D0FBDA50DFC2BE5E86C008AA65D56 res = pk.install_signature(PackageKitGlib.SigTypeEnum.GPG, repo_gpg_id, '', None, progress, None) worked (note the empty string for the package ID). Now a package ID is required, and to obtain it I have to add the repository, but is it not a security problem to already add the repository if the signature is not yet installed? This all still worked on Trusty (14.04). Is there a problem with the Python bindings of the client (perhaps due to Python3)? Or is perhaps the D-Bus service (aptdaemon on Ubuntu) at fault? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1397374/+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 1340830] Re: Regression: Cannot install signatures in Utopic any more
Sorry, on my system there was for some reason, perhaps some experiments several months ago, installed the original PackageKit D-Bus service (packagekit binary package) and not the Ubuntu standard PackageKit D-Bus service emulation using aptdaemon (python3-aptdaemon.pkcompat binary package). aptdaemon was installed, giving me the impression that it was used. This caused the bug to occur and after returning to the standard setup with python3-aptdaemon.pkcompat the bug went away. So the bug is most probably in the packagekit package and most users are still having automatic printer driver installation working, so closing aptdaemon task ... ** Changed in: aptdaemon (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to packagekit in Ubuntu. https://bugs.launchpad.net/bugs/1340830 Title: Regression: Cannot install signatures in Utopic any more Status in aptdaemon package in Ubuntu: Invalid Status in packagekit package in Ubuntu: New Bug description: In the script /usr/share/system-config-printer/install- printerdriver.py I use package kit to add a repository to install printer driver packages, install the signature for te repository and finally install the driver package from the repository, to get a secure installation and the system's update facility also updating my printer driver package if an update gets available. Under Trusty this works correctly, but under Utopic it stopped working. Under Utopic I get the following if I run the Python statements of the script one by one at the Python prompt: -- till@till-twist:~$ python Python 2.7.7 (default, Jun 4 2014, 05:21:28) [GCC 4.8.3] on linux2 Type help, copyright, credits or license for more information. from gi.repository import GLib, PackageKitGlib import sys def progress(progress, type, user_data): ... pass ... repo_gpg_id = E5220FB7014D0FBDA50DFC2BE5E86C008AA65D56 pk = PackageKitGlib.Client() res = pk.install_signature(PackageKitGlib.SigTypeEnum.GPG, repo_gpg_id, '', None, progress, None) Traceback (most recent call last): File stdin, line 1, in module GLib.Error: g-dbus-error-quark: Error calling StartServiceByName for org.freedesktop.PackageKit: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Launch helper exited with unknown return code 1 (25) -- The signature key is from Epson. I also tried with the key F8897B6F00075648E248B7EC24CBF5474CFD1E2F from OpenPrinting and got the same result. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1340830/+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 1347009] Re: apport-retrace occassionally creates a retraced report without a stacktrace
** Changed in: apport (Ubuntu) Importance: Undecided = Low ** Changed in: apport (Ubuntu) Status: Confirmed = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1347009 Title: apport-retrace occassionally creates a retraced report without a stacktrace Status in Ubuntu error tracker backend (daisy): Triaged Status in apport package in Ubuntu: Triaged Bug description: On the Ubuntu Error Tracker retracers I've noticed that apport occasionally will retrace a crash and that the retraced crash report will contain no Stacktrace in it. Here a couple of examples of the retraced reports, unfortunately without the CoreDump. https://pastebin.canonical.com/113960/ https://pastebin.canonical.com/113959/ I've seen this with both crashes on i386 and armhf, so it doesn't seem to be armhf specific although it may be related to using gdb- multiarch. I've created statsd counters for this (retrace.missing.stacktrace) and so far (after 96 hours) it has only occurred 12 times. Subsequently, it seems like a rather low priority but it is still curious. To manage notifications about this bug go to: https://bugs.launchpad.net/daisy/+bug/1347009/+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 1341598] Re: Typo in app-install-data-ubuntu
** Changed in: unity-webapps-qml (Ubuntu) Importance: Undecided = Medium ** Also affects: hundredpapercuts Importance: Undecided Status: New ** Changed in: hundredpapercuts Status: New = Confirmed ** Changed in: hundredpapercuts Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-webapps-qml in Ubuntu. https://bugs.launchpad.net/bugs/1341598 Title: Typo in app-install-data-ubuntu Status in One Hundred Papercuts: Confirmed Status in unity-webapps-qml package in Ubuntu: Confirmed Bug description: Hi, In string #5167: Unity WebApp QML Comonent - Example of WebApps Applications Model Comonent should be replaced by Component. Link: https://translations.launchpad.net/ubuntu/utopic/+source/app- install-data-ubuntu/+pots/app-install-data/fr/5167/+translate To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1341598/+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 1360222] Re: notification for voicemail that was dismissed re notified constantly
** Changed in: telephony-service (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1360222 Title: notification for voicemail that was dismissed re notified constantly Status in telephony-service package in Ubuntu: Confirmed Bug description: I have a recurring voicemail notification from a voicemail I don't want to listen to. Here's the scenario: - Receive voicemail - Receive notification - Dismiss it Expected result: - voicemail doesn't show up again during the running session. I don't mind it showing up after a reboot; but the way it currently is, I am forced to listen to the voicemail to get rid of the false positive of a new notification when it actually isn't, it's a dismissed one. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: telephony-service 0.1+14.10.20140820-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Fri Aug 22 11:53:37 2014 InstallationDate: Installed on 2014-08-22 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140822-020204) SourcePackage: telephony-service UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1360222/+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 1370008] Re: url-dispatcher-bad-url
** Changed in: gallery-app (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1370008 Title: url-dispatcher-bad-url Status in gallery-app package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gallery-app. This problem was most recently seen with version 13.10.0+14.10.20140908.1-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b1f16000af092461aeb85b5c7edfd3dc3f1271c8 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1370008/+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 1370014] Re: Remmina Launching Remote Sessions Larger than Workspace
** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: remmina (Ubuntu) Importance: Undecided = Medium -- 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/1370014 Title: Remmina Launching Remote Sessions Larger than Workspace Status in Unity: New Status in remmina package in Ubuntu: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Please view this video of the bug I'm reporting: http://youtu.be/wKGLff7HhS8 Essentially, when using the Unity desktop in a Multiple Monitor setup (using workspaces), Remmina is launching remote sessions into a window larger than the workspace to which I'm launching it. Another thing to note about my set up, is that I do use Ubuntu's scaling feature to make things about 10% larger than the default size (to accommodate my otherwise straining eyes). Some times I use large text too. These facts may be totally unrelated to the bug, but I thought I would at least mention them. I'm using a fully update Ubuntu 14.04 Desktop 64bit. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1370014/+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 1371859] Re: can't update loaders.cache: permission denied
** Changed in: gdk-pixbuf (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdk-pixbuf in Ubuntu. https://bugs.launchpad.net/bugs/1371859 Title: can't update loaders.cache: permission denied Status in gdk-pixbuf package in Ubuntu: Confirmed Bug description: upgrading that fresh Utopic 64 bits installation, i'm seeing that error into the dialog box: Processing triggers for hicolor-icon-theme (0.13-1) ... (gtk-update-icon-cache-3.0:3098): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': No such file or directory This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. The terminal output is: oem@u64:~$ gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission denied oem@u64:~$ sudo gdk-pixbuf-query-loaders /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache bash: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache: Permission denied ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgdk-pixbuf2.0-0 2.30.8-1 ProcVersionSignature: Ubuntu 3.16.0-16.22-generic 3.16.2 Uname: Linux 3.16.0-16-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Sat Sep 20 08:00:57 2014 SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1371859/+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 1380480] Re: network disabled after suspend - resume
** Changed in: network-manager (Ubuntu) Importance: Undecided = High -- 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/1380480 Title: network disabled after suspend - resume Status in network-manager package in Ubuntu: Confirmed Bug description: Background: this started to happen after the upgrade to Utopic Beta 1 3) When I close the laptop's lid and open, the wifi should reconnect 4) Wifi does not reconnect. It says Wi-Fi networks - disconnected when I left-click on NM icon in notif area. However the context menu (right-click) has items Enable networking and Enable Wi-Fi both with checkmarks. Workarounds: switch off - on the physical switch on laptop OR two times go and select Enable networking in the NM context menu (after first time it removes checkmark and the Enable Wi-Fi item - visual feedback of being disabled). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu27 ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4 Uname: Linux 3.16.0-21-generic x86_64 ApportVersion: 2.14.7-0ubuntu5 Architecture: amd64 CurrentDesktop: XFCE Date: Sat Oct 11 22:33:06 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-07-21 (447 days ago) InstallationMedia: Xubuntu 13.04 Raring Ringtail - Release amd64 (20130423.1) IpRoute: default via 192.168.10.1 dev wlan0 proto static 10.9.9.0/24 dev vboxnet0 proto kernel scope link src 10.9.9.1 192.168.10.0/24 dev wlan0 proto kernel scope link src 192.168.10.239 metric 9 SourcePackage: network-manager UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2014-07-19T15:03:44.847279 nmcli-dev: DEVICE TYPE STATE DBUS-PATH eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/1 wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1380480/+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 1385803] Re: package lightdm 1.12.1-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1
** Changed in: lightdm (Ubuntu) Importance: Undecided = Critical -- 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/1385803 Title: package lightdm 1.12.1-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 Status in lightdm package in Ubuntu: Confirmed Bug description: encrypted home directory broken as well ProblemType: Package DistroRelease: Ubuntu 14.10 Package: lightdm 1.12.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4 Uname: Linux 3.16.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Sun Oct 19 12:43:51 2014 DuplicateSignature: package:lightdm:1.12.1-0ubuntu1:subprocess installed post-removal script returned error exit status 1 ErrorMessage: subprocess installed post-removal script returned error exit status 1 InstallationDate: Installed on 2014-10-18 (7 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) SourcePackage: lightdm Title: package lightdm 1.12.1-0ubuntu1 failed to install/upgrade: subprocess installed post-removal script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.pam.d.lightdm: 2014-10-19T13:04:22.965443 mtime.conffile..etc.pam.d.lightdm.greeter: 2014-10-19T13:03:27.617443 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1385803/+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 1386852] Re: package whoopsie 0.2.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
** Changed in: whoopsie (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1386852 Title: package whoopsie 0.2.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 Status in whoopsie package in Ubuntu: Confirmed Bug description: loading Ubuntu 14.10 on chromebook - whoopsie fails to install in script and then also reports error on startup ProblemType: Package DistroRelease: Ubuntu 14.10 Package: whoopsie 0.2.39 Uname: Linux 3.4.0 x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Tue Oct 28 19:02:43 2014 Df: DuplicateSignature: package:whoopsie:0.2.39:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.39 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1386852/+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 1397472] [NEW] movies
Public bug reported: my downloaded movies are fine when started but then they start doing a slow motion thing ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 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 Nov 28 16:28:04 2014 DistUpgraded: 2014-05-31 01:55:39,671 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0410] InstallationDate: Installed on 2014-05-04 (208 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E4310 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-41-generic root=UUID=b5a4cdc1-a48b-4260-b10f-8d10301a5dbf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-31 (181 days ago) dmi.bios.date: 11/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 03HH35 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/20/2010:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn03HH35:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.2 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.3 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Nov 28 15:20:29 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 21569 vendor SEC xserver.version: 2:1.15.1-0ubuntu2.2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- 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/1397472 Title: movies Status in xorg package in Ubuntu: New Bug description: my downloaded movies are fine when started but then they start doing a slow motion thing ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-41.70-generic 3.13.11.11 Uname: Linux 3.13.0-41-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 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 Nov 28 16:28:04 2014 DistUpgraded: 2014-05-31 01:55:39,671 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0410] InstallationDate: Installed on 2014-05-04 (208 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release i386 (20121017.2) MachineType: Dell Inc. Latitude E4310 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-41-generic root=UUID=b5a4cdc1-a48b-4260-b10f-8d10301a5dbf ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-05-31 (181 days ago) dmi.bios.date: 11/20/2010 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 03HH35 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA05:bd11/20/2010:svnDellInc.:pnLatitudeE4310:pvr0001:rvnDellInc.:rn03HH35:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E4310 dmi.product.version: 0001 dmi.sys.vendor:
[Touch-packages] [Bug 1387422] Re: package keyboard-configuration 1.70ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Changed in: console-setup (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1387422 Title: package keyboard-configuration 1.70ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in console-setup package in Ubuntu: Confirmed Bug description: during upgrade to 14.10 possibly a cascading error from another install-failure ProblemType: Package DistroRelease: Ubuntu 14.10 Package: keyboard-configuration 1.70ubuntu9 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Tue Oct 28 14:22:41 2014 DuplicateSignature: package:keyboard-configuration:1.70ubuntu9:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2013-10-05 (389 days ago) InstallationMedia: Ubuntu-Server 13.04 Raring Ringtail - Release amd64 (20130423.1) PackageArchitecture: all SourcePackage: console-setup Title: package keyboard-configuration 1.70ubuntu9 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1387422/+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 1387163] Re: 'Show Desktop' on launcher crashes compiz for any Gtk-Headerbar app when using any third party Gtk(3.12) theme (Utopic/Vivid)
** Changed in: unity (Ubuntu) Importance: Undecided = Critical -- 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/1387163 Title: 'Show Desktop' on launcher crashes compiz for any Gtk-Headerbar app when using any third party Gtk(3.12) theme (Utopic/Vivid) Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: This is happening for any gtk-3.12 theme which has proper support for gtk-headerbar. How to reproduce on Utopic: 1. sudo apt-get install Numix 2. sudo apt-get install gnome-tweak-tool 3. change Gtk theme to Numix 4. Open any app with Gtk-Headerbar ( NOT directly patched by Ubuntu) like gnome-tweak-tool, gnome-system-log 2. enable show-desktop on unity launcher 3. Click on show-desktop first time. it will show desktop. 4. Click on it again, it crashes compiz sometimes does not recover from it. Users have to fallback to TTY force restart lightdm. The problem also occurs for any headerbar app from Gnom3 ppa (for example gnome-contacts, baobab, gnome-maps). Attached crash file from /var/crash/compiz. Note: Compiz on other desktop shell/session works relatively well. For example in Gnome-Flashback-Compiz session it doesn't happen. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1387163/+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
