[Touch-packages] [Bug 1436721] [NEW] bluetooth setting forgot after airplane mode
Public bug reported: BQ phone: Reproduce: 1. turn off bluetooth 2. go to airplane mode 3. turn off airplane mode Desired effect: Bluetooth is still off What I got: Bluetooth is still on ** 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/1436721 Title: bluetooth setting forgot after airplane mode Status in unity8 package in Ubuntu: New Bug description: BQ phone: Reproduce: 1. turn off bluetooth 2. go to airplane mode 3. turn off airplane mode Desired effect: Bluetooth is still off What I got: Bluetooth is still on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436721/+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 1317449]
*** Bug 345402 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 sqlite3 in Ubuntu. https://bugs.launchpad.net/bugs/1317449 Title: sqlite3 version 3.8.2 breaks digikam Status in digiKam - digital photo management: Won't Fix Status in SQLite: Won't Fix Status in digikam package in Ubuntu: Fix Released Status in sqlite3 package in Ubuntu: Fix Released Status in digikam source package in Trusty: Confirmed Status in sqlite3 source package in Trusty: Confirmed Status in digikam source package in Utopic: Fix Released Status in sqlite3 source package in Utopic: Fix Released Bug description: Please update sqlite to a version 3.8.2. According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 3.8.2 causes crashes in digikam (and possibly other software) in various situations. Several reports confirm, that versions 3.8.2 fix the issue. I'm using the 3.8.4.3 package from debian testing right now and can't trigger crashes anymore. Workaround: Install sqlite3 3.8.2, e.g. you can manually install the corresponding deb packages from either utopic or debian. To manage notifications about this bug go to: https://bugs.launchpad.net/digikam/+bug/1317449/+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 1436280] Re: ibus-daemon crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1048161 *** https://bugs.launchpad.net/bugs/1048161 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1048161, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1436280/+attachment/4355433/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1436280/+attachment/4355435/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1436280/+attachment/4355437/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1436280/+attachment/4355438/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1436280/+attachment/4355439/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1436280/+attachment/4355440/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1436280/+attachment/4355441/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1048161 ibus-daemon crashed with SIGABRT in g_assertion_message() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1436280 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() Status in ibus package in Ubuntu: New Bug description: ibus-daemon crashed with SIGABRT in g_assertion_message() ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: ibus 1.5.9-1ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Mar 25 13:12:35 2015 ExecutablePath: /usr/bin/ibus-daemon InstallationDate: Installed on 2014-07-10 (257 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140520) ProcCmdline: /usr/bin/ibus-daemon --daemonize --xim Signal: 6 SourcePackage: ibus StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () ?? () ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 Title: ibus-daemon crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin nopasswdlogin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1436280/+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 1436743] [NEW] [1001PX, Realtek ALC269VB, Speaker, Internal] No sound at all
Public bug reported: Unable to get any sound at all. ASUS eee PC intel Atom N450 101? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phil 1638 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 18:36:30 2015 InstallationDate: Installed on 2015-03-19 (7 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phil 1638 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [1001PX, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd08/12/2010:svnASUSTeKComputerINC.:pn1001PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1436743 Title: [1001PX, Realtek ALC269VB, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: New Bug description: Unable to get any sound at all. ASUS eee PC intel Atom N450 101? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-48.80-generic 3.13.11-ckt16 Uname: Linux 3.13.0-48-generic i686 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phil 1638 F pulseaudio CurrentDesktop: Unity Date: Thu Mar 26 18:36:30 2015 InstallationDate: Installed on 2015-03-19 (7 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140722.2) PackageArchitecture: all ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: phil 1638 F pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [1001PX, Realtek ALC269VB, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/12/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0904 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: 1001PX dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: x.xx dmi.chassis.asset.tag: 0x dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer INC. dmi.chassis.version: x.x dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0904:bd08/12/2010:svnASUSTeKComputerINC.:pn1001PX:pvrx.x:rvnASUSTeKComputerINC.:rn1001PX:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x: dmi.product.name: 1001PX dmi.product.version: x.x dmi.sys.vendor: ASUSTeK Computer INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1436743/+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 1436724] Re: No prompt to unlock sim after airplane mode
@Albert, the bq hardware seems to be a bit special in that it turns off the modem completely in flight mode and loses the unlocked state. Ubuntu touch itself doesn't require to re-enter the sim pin after flight mode. On the nexus 4 for instance, the SIM card stays unlocked. ** Tags added: bq -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1436724 Title: No prompt to unlock sim after airplane mode Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: BQ phone: Steps to reproduce: 1. Turn airplane mode on 2. Turn airplane mode off Desired effect: You get a prompt to unlock your sim cards What I got: You get no connection and no prompt. Only if you open the network panel, you see that your sim is still locked. You should get a prompt to unlock your sim after turning off airplane mode. Otherwise the user does not know the sim card is still locked. The fact that the sim card becomes locked after airplane mode is not something you should have to think about as a user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1436724/+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 1436724] Re: No prompt to unlock sim after airplane mode
** 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 network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1436724 Title: No prompt to unlock sim after airplane mode Status in the base for Ubuntu mobile products: New Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: BQ phone: Steps to reproduce: 1. Turn airplane mode on 2. Turn airplane mode off Desired effect: You get a prompt to unlock your sim cards What I got: You get no connection and no prompt. Only if you open the network panel, you see that your sim is still locked. You should get a prompt to unlock your sim after turning off airplane mode. Otherwise the user does not know the sim card is still locked. The fact that the sim card becomes locked after airplane mode is not something you should have to think about as a user. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436724/+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
Re: [Touch-packages] [Bug 1436724] Re: No prompt to unlock sim after airplane mode
I guess UT should do a check after flight mode? Check if sim is locked, if so; prompt? 2015-03-26 10:21 GMT+01:00 Michael Zanetti michael.zane...@canonical.com: @Albert, the bq hardware seems to be a bit special in that it turns off the modem completely in flight mode and loses the unlocked state. Ubuntu touch itself doesn't require to re-enter the sim pin after flight mode. On the nexus 4 for instance, the SIM card stays unlocked. ** Tags added: bq -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1436724 Title: No prompt to unlock sim after airplane mode Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: BQ phone: Steps to reproduce: 1. Turn airplane mode on 2. Turn airplane mode off Desired effect: You get a prompt to unlock your sim cards What I got: You get no connection and no prompt. Only if you open the network panel, you see that your sim is still locked. You should get a prompt to unlock your sim after turning off airplane mode. Otherwise the user does not know the sim card is still locked. The fact that the sim card becomes locked after airplane mode is not something you should have to think about as a user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1436724/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1436724 Title: No prompt to unlock sim after airplane mode Status in the base for Ubuntu mobile products: New Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: BQ phone: Steps to reproduce: 1. Turn airplane mode on 2. Turn airplane mode off Desired effect: You get a prompt to unlock your sim cards What I got: You get no connection and no prompt. Only if you open the network panel, you see that your sim is still locked. You should get a prompt to unlock your sim after turning off airplane mode. Otherwise the user does not know the sim card is still locked. The fact that the sim card becomes locked after airplane mode is not something you should have to think about as a user. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1436724/+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 1436630] Re: must unlock screen even if it was only off for a few seconds
Daniel, setting the screen to only lock after 10 minutes is not an option. This setting needs to be split up into two: * Turn off screen after ... and * Lock screen after ... ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: ubuntu-ux Status: New = Confirmed ** Changed in: unity8 (Ubuntu) Status: Opinion = Incomplete -- 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/1436630 Title: must unlock screen even if it was only off for a few seconds Status in Ubuntu UX bugs: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: On Ubuntu Touch so far (vivid, mid-March 2015), it is still necessary to unlock the screen after it shuts off, even if the screen was only off for a few seconds. This is inconvenient, and it would be much easier if the lock didn't activate for ~10 seconds after the screen turns itself off. If the user activates the screen-off event by tapping the power button, then it's okay to lock immediately. If the screen times out though, it should probably delay before locking, to give the user a chance to turn the screen back on. Could we add a ~10 second delay between automatic screen shutoff and screen lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436630/+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 1436767] [NEW] No error output if item is used for the Page assignment
Public bug reported:
I have a sample QML application at:
https://gitcafe.com/ubuntu/TabApp2.git
You may use the command:
git clone https://gitcafe.com/ubuntu/TabApp2.git
to get the code.
In the ExternalPage.qml,
import QtQuick 2.0
import Ubuntu.Components 1.1
Item {
anchors.fill: parent
Label {
anchors.centerIn: parent
text: i18n.tr(This is page xxx one)
}
}
I defined it as an Item. However, when I assign it in the following
way:
Tab {
id: externalTab
title: i18n.tr(External)
page: Loader {
id: loader
anchors.fill: parent
source: (tabs.selectedTab === externalTab) ?
Qt.resolvedUrl(ExternalPage.qml) :
onLoaded: {
console.log( loader.source + is loaded)
}
}
}
it does not output any error messages, making it hard to use if a
developer does not know how to define it.
Best regards,
XiaoGuo
** 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/1436767
Title:
No error output if item is used for the Page assignment
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
I have a sample QML application at:
https://gitcafe.com/ubuntu/TabApp2.git
You may use the command:
git clone https://gitcafe.com/ubuntu/TabApp2.git
to get the code.
In the ExternalPage.qml,
import QtQuick 2.0
import Ubuntu.Components 1.1
Item {
anchors.fill: parent
Label {
anchors.centerIn: parent
text: i18n.tr(This is page xxx one)
}
}
I defined it as an Item. However, when I assign it in the following
way:
Tab {
id: externalTab
title: i18n.tr(External)
page: Loader {
id: loader
anchors.fill: parent
source: (tabs.selectedTab === externalTab) ?
Qt.resolvedUrl(ExternalPage.qml) :
onLoaded: {
console.log( loader.source + is loaded)
}
}
}
it does not output any error messages, making it hard to use if a
developer does not know how to define it.
Best regards,
XiaoGuo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1436767/+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 1435836] Re: System detects problem at startup
*** This bug is a duplicate of bug 1432446 *** https://bugs.launchpad.net/bugs/1432446 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1432446, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1435836/+attachment/4354458/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1435836/+attachment/4354460/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1435836/+attachment/4354461/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1435836/+attachment/4354462/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1435836/+attachment/4354463/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1435836/+attachment/4354464/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1435836/+attachment/4354465/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1432446 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1435836 Title: System detects problem at startup Status in indicator-sound package in Ubuntu: New Bug description: No indication of problem origin .. initial boot does not find WIFI .. reboot does but system still indicates a problem. Occasionally both 15.04 and 14.04 will hang. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-sound 12.10.2+15.04.20150311-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-lowlatency 3.19.1 Uname: Linux 3.19.0-9-lowlatency x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Tue Mar 24 07:43:06 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service InstallationDate: Installed on 2015-02-13 (38 days ago) InstallationMedia: Ubuntu-Studio 15.04 Vivid Vervet - Alpha amd64 (20150213) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-sound/indicator-sound-service ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/false Signal: 5 SourcePackage: indicator-sound StacktraceTop: indicator_sound_service_construct () _start () Title: indicator-sound-service crashed with signal 5 in indicator_sound_service_construct() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1435836/+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 1436775] [NEW] pulseaudio crashed with SIGABRT in pa_object_unref()
Public bug reported: Upon log in pulseaudio crashed. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.16.2-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: slickymaster 1983 F pulseaudio CrashCounter: 1 Date: Thu Mar 26 10:04:13 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-07-15 (253 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140506) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/libpulsecore-6.0.so pa_object_unref () from /usr/lib/libpulsecore-6.0.so main () Title: pulseaudio crashed with SIGABRT in pa_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash i386 need-i386-retrace vivid ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436775 Title: pulseaudio crashed with SIGABRT in pa_object_unref() Status in pulseaudio package in Ubuntu: New Bug description: Upon log in pulseaudio crashed. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.16.2-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: slickymaster 1983 F pulseaudio CrashCounter: 1 Date: Thu Mar 26 10:04:13 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-07-15 (253 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140506) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/libpulsecore-6.0.so pa_object_unref () from /usr/lib/libpulsecore-6.0.so main () Title: pulseaudio crashed with SIGABRT in pa_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1436775/+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 1436630] Re: must unlock screen even if it was only off for a few seconds
I for one still believe those settings should be separate... Those are different settings for other phones (probably nor all of them) and also on Ubuntu Desktop. Just because the the screen saver kicks in you don't necessarily require the user to authenticate again. Anyhow, clearly a question for ubuntu-ux. -- 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/1436630 Title: must unlock screen even if it was only off for a few seconds Status in Ubuntu UX bugs: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Incomplete Bug description: On Ubuntu Touch so far (vivid, mid-March 2015), it is still necessary to unlock the screen after it shuts off, even if the screen was only off for a few seconds. This is inconvenient, and it would be much easier if the lock didn't activate for ~10 seconds after the screen turns itself off. If the user activates the screen-off event by tapping the power button, then it's okay to lock immediately. If the screen times out though, it should probably delay before locking, to give the user a chance to turn the screen back on. Could we add a ~10 second delay between automatic screen shutoff and screen lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436630/+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 1436630] Re: must unlock screen even if it was only off for a few seconds
** Attachment added: Security Privacy_060.png https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436630/+attachment/4356680/+files/Security%20%26%20Privacy_060.png -- 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/1436630 Title: must unlock screen even if it was only off for a few seconds Status in Ubuntu UX bugs: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Incomplete Bug description: On Ubuntu Touch so far (vivid, mid-March 2015), it is still necessary to unlock the screen after it shuts off, even if the screen was only off for a few seconds. This is inconvenient, and it would be much easier if the lock didn't activate for ~10 seconds after the screen turns itself off. If the user activates the screen-off event by tapping the power button, then it's okay to lock immediately. If the screen times out though, it should probably delay before locking, to give the user a chance to turn the screen back on. Could we add a ~10 second delay between automatic screen shutoff and screen lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436630/+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 1436735] [NEW] /usr/bin/unity8:11:DisplayWindow::makeCurrent:MirOpenGLContext::makeCurrent:QOpenGLContext::makeCurrent:QSGRenderThread::invalidateOpenGL:QSGRenderThread::event
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.02+15.04.20150320-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/57e495ad9b12ea8e78d0aed997ba70a6e2213dd2 contains more details. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: vivid -- 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/1436735 Title: /usr/bin/unity8:11:DisplayWindow::makeCurrent:MirOpenGLContext::makeCurrent:QOpenGLContext::makeCurrent:QSGRenderThread::invalidateOpenGL:QSGRenderThread::event Status in unity8 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.02+15.04.20150320-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/57e495ad9b12ea8e78d0aed997ba70a6e2213dd2 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436735/+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 1417646] Re: Cannot connect to Eduroam wifi Network
same issue on Aquaris E4.5 Ubuntu Edition -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1417646 Title: Cannot connect to Eduroam wifi Network Status in indicator-network package in Ubuntu: Confirmed Bug description: Eduroam is a wifi Network the uses IEEE 802.1x Authentication technology. It is used in most higher institutuions acrosss Europe and other parts of the world. The network requires a username and password when connecting, instead of just a Wifi key for traditional Wifi networks. Ubuntu desktop can connect to this network, however, Ubuntu touch cannot. I have tried copying the config file for the network from Network Manager on Ubuntu desktop to the same location on the phone using adb push, but this didn't do anything. Here's a video I recorded of what happens when you try to connect. https://www.youtube.com/watch?v=mnbLZ0EmPYc . This affects me because, as I am in the university right now, Eduroam is my only source of internet connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1417646/+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 1421009] Re: unity8 sometimes hangs on boot
I was using mako devel-proposed image #148 with the silo installed. I'll try and reproduce again and get some more info. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in autopilot package in Ubuntu: New Status in libusermetrics package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. Update 2015-03-25: the qtbase dbus update in silo 018 seems to address the boot issue, but causes autopilot to have problems seeing an application start, randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1421009/+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 1436721] Re: bluetooth setting forgot after airplane mode
** Tags added: bq -- 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/1436721 Title: bluetooth setting forgot after airplane mode Status in unity8 package in Ubuntu: New Bug description: BQ phone: Reproduce: 1. turn off bluetooth 2. go to airplane mode 3. turn off airplane mode Desired effect: Bluetooth is still off What I got: Bluetooth is still on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436721/+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 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
** Changed in: wpa (Debian) Status: Unknown = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target Status in network-manager package in Ubuntu: Confirmed Status in wpa package in Ubuntu: Triaged Status in wpa package in Debian: New Bug description: To replicate, perform a manual cifs mount, for example: sudo mount -t cifs -o credentials=,user,rw,uid=1000 //192.168.1.nnn/docs /media/test_mount Then shutdown. When booted with systemd there is a 1 to 2 minute delay before shutdown. In syslog the last shutdown (09:47:11 13th March) showed the effect, though I fear that syslog shuts down too early to see anything. If booted with upstart there is no noticeable delay on shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 09:50:08 2015 InstallationDate: Installed on 2014-10-21 (142 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+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 1429135] Re: webbrowser-app crashed with SIGSEGV in XQueryExtension()
http://bazaar.launchpad.net/~oxide- developers/oxide/oxide.trunk/revision/1021 should fix this ** Changed in: oxide Status: In Progress = Fix Released ** Also affects: oxide/1.5 Importance: Undecided Status: New ** Also affects: oxide/1.6 Importance: Undecided Status: New ** Changed in: oxide/1.5 Importance: Undecided = High ** Changed in: oxide/1.6 Importance: Undecided = High ** Changed in: oxide/1.5 Status: New = Triaged ** Changed in: oxide/1.6 Status: New = Triaged ** Changed in: oxide/1.5 Milestone: None = 1.5.6 ** Changed in: oxide/1.6 Milestone: None = 1.6.1 ** Changed in: oxide/1.5 Assignee: (unassigned) = Chris Coulson (chrisccoulson) ** Changed in: oxide/1.6 Assignee: (unassigned) = Chris Coulson (chrisccoulson) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1429135 Title: webbrowser-app crashed with SIGSEGV in XQueryExtension() Status in Oxide Webview: Fix Released Status in Oxide 1.5 series: Triaged Status in Oxide 1.6 series: Triaged Status in oxide-qt package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: This occurs when starting the webbrowser app in a Unity 8 desktop session. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webbrowser-app 0.23+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Thu Mar 5 10:41:06 2015 ExecutablePath: /usr/bin/webbrowser-app InstallationDate: Installed on 2013-03-18 (717 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcCmdline: webbrowser-app ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: webbrowser-app StacktraceTop: XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XInitExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XextAddDisplay () from /usr/lib/x86_64-linux-gnu/libXext.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 Title: webbrowser-app crashed with SIGSEGV in XQueryExtension() UpgradeStatus: Upgraded to vivid on 2014-10-20 (136 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1429135/+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 1435685] Re: [Asus X751MD] Double mouse cursor
The laptop goes back to the shop. see here (prob touchpad) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1436327 Thanks to all devs! -- 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/1435685 Title: [Asus X751MD] Double mouse cursor Status in xorg package in Ubuntu: Incomplete Bug description: I have a double mouse cursor. WORKAROUND: Installed nvidia driver from Ubuntu repository. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7 Uname: Linux 3.16.0-33-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Tue Mar 24 07:51:42 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation ValleyView Gen7 [8086:0f31] (rev 0e) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:16dd] InstallationDate: Installed on 2015-03-22 (1 days ago) InstallationMedia: Xubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. X751MD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic.efi.signed root=UUID=e919445c-9bea-469f-a036-22c3f5fb6dbb ro splash quiet SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/06/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X751MD.208 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X751MD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX751MD.208:bd02/06/2015:svnASUSTeKCOMPUTERINC.:pnX751MD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX751MD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X751MD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Mar 24 07:49:15 2015 xserver.configfile: default xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) NOUVEAU(G0): [XvMC] Failed to initialize extension. xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5928 vendor CMN xserver.version: 2:1.16.0-1ubuntu1.2~trusty2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1435685/+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 1436162] Re: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21
** Tags added: lt-blocker lt-category-visible -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-good1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1436162 Title: [pulsesink] abort at pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock() with libc 2.21 Status in glibc package in Ubuntu: Fix Committed Status in gst-plugins-good1.0 package in Ubuntu: Invalid Status in pulseaudio package in Ubuntu: Invalid Bug description: current build number: 146 device name: m75 channel: ubuntu-touch/vivid-proposed last update: 2015-03-24 13:57:03 version version: 146 After libc 2.21 landed, pulsesink fails constantly when pausing or seeking the active pipeline. Abort message: Assertion 'pthread_mutex_unlock(m-mutex) == 0' failed at pulsecore/mutex-posix.c:118, function pa_mutex_unlock(). Aborting. This is basically happens when it tries to unlock a mutex that is already unlocked. This issue doesn't happen with libc 2.19. To reproduce the issue: GST_DEBUG=*pulse*:5 gst-launch-1.0 playbin uri=file:///tmp/foobar.mp3 Then when playing, just hit control+c, which will then pause the pipeline, causing the crash. The crash happens with most of the times you pause or seek the pipeline. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1436162/+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 1436269] Re: When you select Analog Output or Speakers as port in Output Devices tab of pavucontrol, headphone levels are raised
As for #2, what do you mean by pulseaudio need to use line out jack to determine the availability instead of unknown? The problem is that headphone volume raises, when you control another port in pavucontrol. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436269 Title: When you select Analog Output or Speakers as port in Output Devices tab of pavucontrol, headphone levels are raised Status in pulseaudio package in Ubuntu: Incomplete Bug description: Please note, that Line out = analog output port is controlled by ALSA mixer track called PCM, whereas there should be a separate mixer track for it; see bug Bug #1433568 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11.1 ProcVersionSignature: Ubuntu 3.13.0-48.80-lowlatency 3.13.11-ckt16 Uname: Linux 3.13.0-48-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Mar 25 12:34:23 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-21 (185 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2011 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.6.6 dmi.board.name: 0RF703 dmi.board.vendor: Dell Inc. dmi.chassis.type: 6 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.6.6:bd06/26/2011:svnDellInc.:pnOptiPlex745:pvr:rvnDellInc.:rn0RF703:rvr:cvnDellInc.:ct6:cvr: dmi.product.name: OptiPlex 745 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1436269/+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 1232734] Re: Multiple AP with same SSID are not grouped
Heh, I love how someone old bugs come out and show how much progress we did in two years :-) Indeed I can't reproduce it anymore, both with mako/vivid and krillin/rtm, but it wasn't happening with all networks, and I haven't anymore the one there is in the screenshot, so I cannot be sure at 100% there isn't anymore, but I'm quite confident it's gone, because I haven't seen it in a while. -- 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/1232734 Title: Multiple AP with same SSID are not grouped Status in network-manager package in Ubuntu: Incomplete Bug description: In Ubuntu Touch on Nexus 4 with image 20130927 (update 67) multiple AP with same SSID are all listed. I think that expect behavior is to grouped them. See attachment. Please let's me know which log can I give you for further information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1232734/+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 1429135] Re: webbrowser-app crashed with SIGSEGV in XQueryExtension()
** Branch linked: lp:oxide -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1429135 Title: webbrowser-app crashed with SIGSEGV in XQueryExtension() Status in Oxide Webview: Fix Released Status in Oxide 1.5 series: Triaged Status in Oxide 1.6 series: Triaged Status in oxide-qt package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu: Invalid Bug description: This occurs when starting the webbrowser app in a Unity 8 desktop session. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: webbrowser-app 0.23+15.04.20150227-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0 Uname: Linux 3.19.0-7-generic x86_64 ApportVersion: 2.16.2-0ubuntu1 Architecture: amd64 Date: Thu Mar 5 10:41:06 2015 ExecutablePath: /usr/bin/webbrowser-app InstallationDate: Installed on 2013-03-18 (717 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) ProcCmdline: webbrowser-app ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash Signal: 11 SourcePackage: webbrowser-app StacktraceTop: XQueryExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XInitExtension () from /usr/lib/x86_64-linux-gnu/libX11.so.6 XextAddDisplay () from /usr/lib/x86_64-linux-gnu/libXext.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libOxideQtCore.so.0 Title: webbrowser-app crashed with SIGSEGV in XQueryExtension() UpgradeStatus: Upgraded to vivid on 2014-10-20 (136 days ago) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sudo vboxusers To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1429135/+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 1436728] [NEW] Cannot open file: avprobe mis-interprets some file names.
Public bug reported: Hello, I am using audio-recorder to produce some audio files of types .ogg, .flac and .mp3. I just discovered that avprobe command cannot open the file names produced by the recorder. Avprobe mis-interprets the file given as argument. An example. $ avprobe -show_format -show_streams -pretty 2015-03-24-21:11:13.mp3 avprobe version 11.2-6:11.2-1, Copyright (c) 2007-2014 the Libav developers built on Jan 18 2015 05:12:33 with gcc 4.9.2 (Ubuntu 4.9.2-10ubuntu2) 2015-03-24-21:11:13.mp3: Protocol not found # avprobe output --- Let's rename 2015-03-24-21:11:13.mp3 to test1.mp3. $ cp 2015-03-24-21:11:13.mp3 test1.mp3 $ avprobe -show_format -show_streams -pretty test1.mp3 avprobe version 11.2-6:11.2-1, Copyright (c) 2007-2014 the Libav developers built on Jan 18 2015 05:12:33 with gcc 4.9.2 (Ubuntu 4.9.2-10ubuntu2) [mp3 @ 0x146ad20] max_analyze_duration 500 reached Input #0, mp3, from 'test1.mp3': Duration: 00:04:41.86, start: 0.00, bitrate: 92 kb/s Stream #0.0: Audio: mp3, 44100 Hz, 2 channels, s16p, 92 kb/s # avprobe output [format] filename=test1.mp3 nb_streams=1 format_name=mp3 format_long_name=MP2/3 (MPEG audio layer 2/3) start_time=0\:00\:00.00 duration=0\:04\:41.861224 size=3.109Mibyte bit_rate=92.536Kbit/s ... start_time=0\:00\:00.00 duration=0\:04\:41.861224 And avprobe opens test1.mp3 fine. - Example 2: $ avprobe -show_format -show_streams -pretty 2015-02-20-22:21:25.ogg avprobe version 11.2-6:11.2-1, Copyright (c) 2007-2014 the Libav developers built on Jan 18 2015 05:12:33 with gcc 4.9.2 (Ubuntu 4.9.2-10ubuntu2) 2015-02-20-22:21:25.ogg: Protocol not found # avprobe output Rename it. $ cp 2015-02-20-22:21:25.ogg test1.ogg And now it works. $ avprobe -show_format -show_streams -pretty test1.ogg avprobe version 11.2-6:11.2-1, Copyright (c) 2007-2014 the Libav developers built on Jan 18 2015 05:12:33 with gcc 4.9.2 (Ubuntu 4.9.2-10ubuntu2) Input #0, ogg, from 'test1.ogg': Duration: 00:00:55.18, start: 0.00, bitrate: 162 kb/s Stream #0.0: Audio: vorbis, 44100 Hz, stereo, fltp, 160 kb/s # avprobe output [format] filename=test1.ogg nb_streams=1 ... time_base=1/44100 start_time=0\:00\:00.00 duration=0\:00\:55.183673 --- Ref: The audio-recorder program. https://launchpad.net/~audio-recorder Version of avprobe: $ avprobe --version avprobe version 11.2-6:11.2-1, Copyright (c) 2007-2014 the Libav developers built on Jan 18 2015 05:12:33 with gcc 4.9.2 (Ubuntu 4.9.2-10ubuntu2) Linux system: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu Vivid Vervet (development branch) Release:15.04 Codename: vivid EOL. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: libav-tools 6:11.2-1 Uname: Linux 3.19.0-999-generic x86_64 ApportVersion: 2.16.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 07:59:16 2015 InstallationDate: Installed on 2015-01-28 (56 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150128) SourcePackage: libav UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libav (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1436728 Title: Cannot open file: avprobe mis-interprets some file names. Status in libav package in Ubuntu: New Bug description: Hello, I am using audio-recorder to produce some audio files of types .ogg, .flac and .mp3. I just discovered that avprobe command cannot open the file names produced by the recorder. Avprobe mis-interprets the file given as argument. An example. $ avprobe -show_format -show_streams -pretty 2015-03-24-21:11:13.mp3 avprobe version 11.2-6:11.2-1, Copyright (c) 2007-2014 the Libav developers built on Jan 18 2015 05:12:33 with gcc 4.9.2 (Ubuntu 4.9.2-10ubuntu2) 2015-03-24-21:11:13.mp3: Protocol not found # avprobe output --- Let's rename 2015-03-24-21:11:13.mp3 to test1.mp3. $ cp 2015-03-24-21:11:13.mp3 test1.mp3 $ avprobe -show_format -show_streams -pretty test1.mp3 avprobe version 11.2-6:11.2-1, Copyright (c) 2007-2014 the Libav developers built on Jan 18 2015 05:12:33 with gcc 4.9.2 (Ubuntu 4.9.2-10ubuntu2) [mp3 @ 0x146ad20] max_analyze_duration 500 reached Input #0, mp3, from 'test1.mp3': Duration: 00:04:41.86, start: 0.00, bitrate: 92 kb/s Stream #0.0: Audio: mp3, 44100 Hz, 2 channels, s16p, 92 kb/s # avprobe output [format] filename=test1.mp3 nb_streams=1 format_name=mp3 format_long_name=MP2/3 (MPEG audio layer 2/3) start_time=0\:00\:00.00 duration=0\:04\:41.861224 size=3.109Mibyte bit_rate=92.536Kbit/s ... start_time=0\:00\:00.00
[Touch-packages] [Bug 1404247] Re: Vivid Wallpaper hashed
done, but i don't know how subscribe you. my report is in: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1436378 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1404247 Title: Vivid Wallpaper hashed Status in xorg package in Ubuntu: Incomplete Bug description: After update this week wallpaper hashed. See attachment. Settings Appearance change wallpaper to a different wallpaper O.K., then back to original restores proper image. Reboot, wallpaper hashed again. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-28.38-generic 3.16.7-ckt1 Uname: Linux 3.16.0-28-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.15-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Dec 19 08:43:46 2014 DistUpgraded: Fresh install DistroCodename: vivid DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo ThinkCentre M6258 [17aa:3048] Subsystem: Lenovo Device [17aa:3048] InstallationDate: Installed on 2014-11-25 (23 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20141125) ProcEnviron: LANGUAGE=en_US TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=285177a7-5498-4980-a3f2-7e3f655ca886 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/10/2011 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT69AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 6234A1U dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12.0+15.04.20141120-0ubuntu3 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58-2 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.2.901-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141119-1~exp1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Dec 19 08:43:04 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.16.2.901-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1404247/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431774] Re: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target
** Also affects: wpa (Ubuntu) Importance: Undecided Status: New ** Changed in: wpa (Ubuntu) Status: New = Triaged ** Bug watch added: Debian Bug tracker #780552 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780552 ** Also affects: wpa (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780552 Importance: Unknown Status: Unknown -- 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/1431774 Title: cifs mount hangs on shutdown - NetworkManager needs to stop after network.target Status in network-manager package in Ubuntu: Confirmed Status in wpa package in Ubuntu: Triaged Status in wpa package in Debian: Unknown Bug description: To replicate, perform a manual cifs mount, for example: sudo mount -t cifs -o credentials=,user,rw,uid=1000 //192.168.1.nnn/docs /media/test_mount Then shutdown. When booted with systemd there is a 1 to 2 minute delay before shutdown. In syslog the last shutdown (09:47:11 13th March) showed the effect, though I fear that syslog shuts down too early to see anything. If booted with upstart there is no noticeable delay on shutdown. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu5 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service] ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 ApportVersion: 2.16.2-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Fri Mar 13 09:50:08 2015 InstallationDate: Installed on 2014-10-21 (142 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20141017) MachineType: FUJITSU LIFEBOOK A544 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic root=UUID=c68c6484-d8d6-44f6-b429-892aa6ef74cf ro SourcePackage: systemd UpgradeStatus: Upgraded to vivid on 2015-02-25 (15 days ago) dmi.bios.date: 12/01/2014 dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd. dmi.bios.version: Version 1.18 dmi.board.name: FJNBB35 dmi.board.vendor: FUJITSU dmi.chassis.type: 10 dmi.chassis.vendor: FUJITSU dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.18:bd12/01/2014:svnFUJITSU:pnLIFEBOOKA544:pvr:rvnFUJITSU:rnFJNBB35:rvr:cvnFUJITSU:ct10:cvr: dmi.product.name: LIFEBOOK A544 dmi.sys.vendor: FUJITSU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1431774/+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 1436325] Re: NetworkManager crashed with SIGABRT in g_assertion_message()
*** This bug is a duplicate of bug 1432262 *** https://bugs.launchpad.net/bugs/1432262 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1432262, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1436325/+attachment/4355519/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1436325/+attachment/4355521/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1436325/+attachment/4355536/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1436325/+attachment/4355537/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1436325/+attachment/4355538/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1436325/+attachment/4355540/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1436325/+attachment/4355541/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1432262 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/1436325 Title: NetworkManager crashed with SIGABRT in g_assertion_message() Status in network-manager package in Ubuntu: New Bug description: Happens on bootstrap or login. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu11 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CrashCounter: 1 Date: Wed Mar 25 08:58:01 2015 ExecutablePath: /usr/sbin/NetworkManager IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-03-01 (388 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1) ProcCmdline: NetworkManager ProcEnviron: LANGUAGE=en_CA:en TERM=linux PATH=(custom, no user) LANG=en_CA.UTF-8 Signal: 6 SourcePackage: network-manager StacktraceTop: g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: NetworkManager crashed with SIGABRT in g_assertion_message() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1436325/+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 1434811] Re: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 1379752 *** https://bugs.launchpad.net/bugs/1379752 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1379752, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1434811/+attachment/4351331/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1434811/+attachment/4351333/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1434811/+attachment/4351334/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1434811/+attachment/4351335/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1434811/+attachment/4351336/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1434811/+attachment/4351337/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1434811/+attachment/4351338/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1379752 indicator-bluetooth-service crashed with SIGSEGV in org_bluez_adapter_set_property() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1434811 Title: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke() Status in indicator-bluetooth package in Ubuntu: New Bug description: bluetooth ne start pas, l'indicateur crash probablement par la fermeture du drivers bluetooth ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: indicator-bluetooth 0.0.6+14.10.20141006-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1 Uname: Linux 3.19.0-9-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 21 13:55:27 2015 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service InstallationDate: Installed on 2015-03-14 (7 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=fr_CH.UTF-8 LANGUAGE=fr_CH:fr XDG_RUNTIME_DIR=set SegvAnalysis: Segfault happened at: 0x40e760: mov(%rbx),%rdi PC (0x0040e760) ok source (%rbx) (0x) not located in a known VMA region (needed readable region)! destination %rdi ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: indicator-bluetooth StacktraceTop: ?? () ?? () ?? () g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: indicator-bluetooth-service crashed with SIGSEGV in g_closure_invoke() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo upstart.indicator-bluetooth.log: ** (process:2154): CRITICAL **: bluez.vala:104: GDBus.Error:org.bluez.Error.NoSuchAdapter: No such adapter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1434811/+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 1430675] Re: fails to set up a bridged network interface
I'll do that. Here's the debug output anyway, which I forgot to attach sooner.. ** Attachment added: debug info https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+attachment/4356510/+files/br0-debug.txt -- 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/1430675 Title: fails to set up a bridged network interface Status in systemd package in Ubuntu: Incomplete Bug description: I have a simple bridge set up in /etc/network/interfaces so that the virtual machines running on that machine can use it and be on the same subnet. But with systemd it's not started on boot. The bridge is configured as follows auto br0 iface br0 inet dhcp bridge_ports eth0 bridge_stp off bridge_maxwait 5 reproduced now on a fresh vm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1430675/+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 1436724] [NEW] No prompt to unlock sim after airplane mode
Public bug reported: BQ phone: Steps to reproduce: 1. Turn airplane mode on 2. Turn airplane mode off Desired effect: You get a prompt to unlock your sim cards What I got: You get no connection and no prompt. Only if you open the network panel, you see that your sim is still locked. You should get a prompt to unlock your sim after turning off airplane mode. Otherwise the user does not know the sim card is still locked. The fact that the sim card becomes locked after airplane mode is not something you should have to think about as a user. ** 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/1436724 Title: No prompt to unlock sim after airplane mode Status in unity8 package in Ubuntu: New Bug description: BQ phone: Steps to reproduce: 1. Turn airplane mode on 2. Turn airplane mode off Desired effect: You get a prompt to unlock your sim cards What I got: You get no connection and no prompt. Only if you open the network panel, you see that your sim is still locked. You should get a prompt to unlock your sim after turning off airplane mode. Otherwise the user does not know the sim card is still locked. The fact that the sim card becomes locked after airplane mode is not something you should have to think about as a user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436724/+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 1436723] [NEW] Regression: Nested LXC is broken on Vivid
Public bug reported: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1436723 Title: Regression: Nested LXC is broken on Vivid Status in lxc package in Ubuntu: New Bug description: The nested LXC functionality seems to be broken on Vivid, at least with the following setup: Vivid (Host) - Trusty (Outer LXC) - Trusty (Inner LXC) What happens: The Inner LXC start command fails when trying to start with: http://pastebin.ubuntu.com/10682639/ ( 631 cgroup error? 100 cgroups with this name already running seems to be the revelant error message). What is expected to happen: The inner LXC start command is expected to succeed and result in a running nested container. Steps to reproduce: - Install vivid server daily, update. - sudo apt-get install lxc - sudo lxc-create -n outer -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo su - echo 'lxc.aa_profile = lxc_container_default_with_nesting' /var/lib/lxc/outer/config - exit - sudo lxc-start -n outer - (SSH to outer) - sudo apt-get update sudo apt-get dist-upgrade - sudo apt-get install lxc - sudo lxc-create -n inner -t ubuntu -- --release trusty --mirror=http://ch.archive.ubuntu.com/ubuntu -b $USER - sudo lxc-start -n inner Fails with: http://pastebin.ubuntu.com/10682639/ Enabling debug logs for this action yields: http://pastebin.ubuntu.com/10682658/ Control: The exact same scenario works on trusty and utopic. Tested by spinning up server installs (from isos) in KVMs and verifying manually. Any further log or information available on request, including KVM images demonstrating the problem. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 26 08:43:56 2015 InstallationDate: Installed on 2015-03-12 (13 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150306) SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1436723/+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 1083084] Re: add option for alt-tab window grouping disable
is there a workaround for ubuntu 14.10 or 15.04 to disable grouping in the switcher? -- 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/1083084 Title: add option for alt-tab window grouping disable Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: Good day, thank you for your wonderful work on Unity, I find it very usable. The only thing that bothers me is the window grouping, as described here: http://ubuntuforums.org/showthread.php?t=1826736 quote: MY Question is if its possible to disable the Grouping part... such as having multiple nautilus windows. Primarily thunderbird is the largest annoyance.. if im writing an email on my laptop and accedentally (touchpad 'palming') off the 'compose message' window; by default and second nature, my brain tells my fingers to alt-tab back into it. unfortunately, this DOES NOT WORK! Basically, I am trying to restore Alt+Tab functionality from Unity 2D. I tried number of other switchers, all have their separate issues. For example, Static Application Switcher does not show minimalized windows (or windows hidden by the show desktop shortcut), etc. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,move,regex,gnomecompat,vpswitch,mousepoll,resize,place,grid,compiztoolbox,snap,imgpng,unitymtgrabhandles,session,animation,workarounds,wall,expo,ezoom,fade,scale,unityshell] Date: Mon Nov 26 10:06:10 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-05-17 (924 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-03 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1083084/+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 1436724] Re: No prompt to unlock sim after airplane mode
Actually, on all the other phones I've used airplane mode doesn't need me to unlock the sim card after disabling it ** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1436724 Title: No prompt to unlock sim after airplane mode Status in indicator-network package in Ubuntu: New Status in network-manager package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: BQ phone: Steps to reproduce: 1. Turn airplane mode on 2. Turn airplane mode off Desired effect: You get a prompt to unlock your sim cards What I got: You get no connection and no prompt. Only if you open the network panel, you see that your sim is still locked. You should get a prompt to unlock your sim after turning off airplane mode. Otherwise the user does not know the sim card is still locked. The fact that the sim card becomes locked after airplane mode is not something you should have to think about as a user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1436724/+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 1083084] Re: add option for alt-tab window grouping disable
confirm! Please add an option to disable grouping in the switcher!!! -- 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/1083084 Title: add option for alt-tab window grouping disable Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: Good day, thank you for your wonderful work on Unity, I find it very usable. The only thing that bothers me is the window grouping, as described here: http://ubuntuforums.org/showthread.php?t=1826736 quote: MY Question is if its possible to disable the Grouping part... such as having multiple nautilus windows. Primarily thunderbird is the largest annoyance.. if im writing an email on my laptop and accedentally (touchpad 'palming') off the 'compose message' window; by default and second nature, my brain tells my fingers to alt-tab back into it. unfortunately, this DOES NOT WORK! Basically, I am trying to restore Alt+Tab functionality from Unity 2D. I tried number of other switchers, all have their separate issues. For example, Static Application Switcher does not show minimalized windows (or windows hidden by the show desktop shortcut), etc. Thanks :) ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: unity 6.10.0-0ubuntu2 ProcVersionSignature: Ubuntu 3.5.0-18.29-generic 3.5.7 Uname: Linux 3.5.0-18-generic i686 ApportVersion: 2.6.1-0ubuntu6 Architecture: i386 CompizPlugins: [core,composite,opengl,decor,move,regex,gnomecompat,vpswitch,mousepoll,resize,place,grid,compiztoolbox,snap,imgpng,unitymtgrabhandles,session,animation,workarounds,wall,expo,ezoom,fade,scale,unityshell] Date: Mon Nov 26 10:06:10 2012 EcryptfsInUse: Yes InstallationDate: Installed on 2010-05-17 (924 days ago) InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: Upgraded to quantal on 2012-10-03 (53 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1083084/+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 1436735] Re: /usr/bin/unity8:11:DisplayWindow::makeCurrent:MirOpenGLContext::makeCurrent:QOpenGLContext::makeCurrent:QSGRenderThread::invalidateOpenGL:QSGRenderThread::event
Assigning to qtmir since there's no unity8 code in that crashing backtrace ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: New = Invalid -- 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/1436735 Title: /usr/bin/unity8:11:DisplayWindow::makeCurrent:MirOpenGLContext::makeCurrent:QOpenGLContext::makeCurrent:QSGRenderThread::invalidateOpenGL:QSGRenderThread::event Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.02+15.04.20150320-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/57e495ad9b12ea8e78d0aed997ba70a6e2213dd2 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1436735/+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 1421009] Re: unity8 sometimes hangs on boot
Richard, which hardware are you using? Can you try reproducing the issue again and then gdb'ing in to the frozen app and posting a backtrace? I've been running it in a loop for minutes and had nothing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in autopilot package in Ubuntu: New Status in libusermetrics package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. Update 2015-03-25: the qtbase dbus update in silo 018 seems to address the boot issue, but causes autopilot to have problems seeing an application start, randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1421009/+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 1436630] Re: must unlock screen even if it was only off for a few seconds
Probably the one in Setting System Battery should only deal with turning off the screen, while the other in security should deal with the interval when the lock code is activated. ** Also affects: ubuntu-system-settings Importance: Undecided Status: New ** Project changed: ubuntu-system-settings = ubuntu-system-settings (Ubuntu) ** Changed in: ubuntu-system-settings (Ubuntu) Status: New = Incomplete -- 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/1436630 Title: must unlock screen even if it was only off for a few seconds Status in Ubuntu UX bugs: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: On Ubuntu Touch so far (vivid, mid-March 2015), it is still necessary to unlock the screen after it shuts off, even if the screen was only off for a few seconds. This is inconvenient, and it would be much easier if the lock didn't activate for ~10 seconds after the screen turns itself off. If the user activates the screen-off event by tapping the power button, then it's okay to lock immediately. If the screen times out though, it should probably delay before locking, to give the user a chance to turn the screen back on. Could we add a ~10 second delay between automatic screen shutoff and screen lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436630/+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 1436694] Re: when the system was opening :systemd-journald crashed with SIGSEGV in __find_specmb()
** Information type changed from Private to Public
--
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/1436694
Title:
when the system was opening :systemd-journald crashed with SIGSEGV in
__find_specmb()
Status in systemd package in Ubuntu:
New
Bug description:
I have opened xubuntu than i have seen 4 windows alert. I have closed
3 of 4 than cliched one of them and report this.
ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: systemd 219-4ubuntu9
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic i686
NonfreeKernelModules: wl
ApportVersion: 2.16.2-0ubuntu4
Architecture: i386
Date: Wed Mar 25 18:12:17 2015
ExecutablePath: /lib/systemd/systemd-journald
InstallationDate: Installed on 2014-12-21 (94 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS Trusty Tahr - Release i386 (20140723)
MachineType: ASUSTeK Computer INC. 1015PW
ProcCmdline: /lib/systemd/systemd-journald
ProcEnviron:
LANG=it_IT.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-9-generic
root=UUID=4d7cab7b-ad63-4fe0-985f-dfb06a812a95 ro quiet splash vt.handoff=7
Signal: 11
SourcePackage: systemd
StacktraceTop:
__find_specmb (format=0xb77a4f69 %s: IO error, rotating.) at
printf-parse.h:108
_IO_vfprintf_internal (s=0xbff08500, format=0xb77a4f69 %s: IO error,
rotating., ap=0xbff08eb8 X\217\351\270\332!x\267\b}{\267\373\377\377\377\t)
at vfprintf.c:1315
___vsnprintf_chk (s=0xbff0863c , maxlen=optimized out, flags=1,
slen=2048, format=0xb77a4f69 %s: IO error, rotating., args=0xbff08eb8
X\217\351\270\332!x\267\b}{\267\373\377\377\377\t) at vsnprintf_chk.c:63
?? ()
?? ()
Title: systemd-journald crashed with SIGSEGV in __find_specmb()
UpgradeStatus: Upgraded to vivid on 2015-03-18 (7 days ago)
UserGroups:
dmi.bios.date: 05/06/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1301
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: 1015PE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.asset.tag: 0x
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.version: x.x
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr1301:bd05/06/2011:svnASUSTeKComputerINC.:pn1015PW:pvrx.x:rvnASUSTeKComputerINC.:rn1015PE:rvrx.xx:cvnASUSTeKComputerINC.:ct10:cvrx.x:
dmi.product.name: 1015PW
dmi.product.version: x.x
dmi.sys.vendor: ASUSTeK Computer INC.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1436694/+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 1436767] Re: No error output if item is used for the Page assignment
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Status: New = Confirmed
--
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/1436767
Title:
No error output if item is used for the Page assignment
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
I have a sample QML application at:
https://gitcafe.com/ubuntu/TabApp2.git
You may use the command:
git clone https://gitcafe.com/ubuntu/TabApp2.git
to get the code.
In the ExternalPage.qml,
import QtQuick 2.0
import Ubuntu.Components 1.1
Item {
anchors.fill: parent
Label {
anchors.centerIn: parent
text: i18n.tr(This is page xxx one)
}
}
I defined it as an Item. However, when I assign it in the following
way:
Tab {
id: externalTab
title: i18n.tr(External)
page: Loader {
id: loader
anchors.fill: parent
source: (tabs.selectedTab === externalTab) ?
Qt.resolvedUrl(ExternalPage.qml) :
onLoaded: {
console.log( loader.source + is loaded)
}
}
}
it does not output any error messages, making it hard to use if a
developer does not know how to define it.
Best regards,
XiaoGuo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1436767/+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 1436767] Re: No error output if item is used for the Page assignment
** Changed in: ubuntu-ui-toolkit (Ubuntu)
Importance: Undecided = Low
--
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/1436767
Title:
No error output if item is used for the Page assignment
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
I have a sample QML application at:
https://gitcafe.com/ubuntu/TabApp2.git
You may use the command:
git clone https://gitcafe.com/ubuntu/TabApp2.git
to get the code.
In the ExternalPage.qml,
import QtQuick 2.0
import Ubuntu.Components 1.1
Item {
anchors.fill: parent
Label {
anchors.centerIn: parent
text: i18n.tr(This is page xxx one)
}
}
I defined it as an Item. However, when I assign it in the following
way:
Tab {
id: externalTab
title: i18n.tr(External)
page: Loader {
id: loader
anchors.fill: parent
source: (tabs.selectedTab === externalTab) ?
Qt.resolvedUrl(ExternalPage.qml) :
onLoaded: {
console.log( loader.source + is loaded)
}
}
}
it does not output any error messages, making it hard to use if a
developer does not know how to define it.
Best regards,
XiaoGuo
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1436767/+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 1436630] Re: must unlock screen even if it was only off for a few seconds
The request seems to be to do what android does, which means that if the screen starts locking on idle, give some time to the user to react and create activity before it's actually locked. It's not really a demand to have different settings for power off and locking... ** Changed in: ubuntu-system-settings (Ubuntu) Importance: Undecided = Low ** Changed in: ubuntu-system-settings (Ubuntu) Status: Incomplete = Invalid -- 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/1436630 Title: must unlock screen even if it was only off for a few seconds Status in Ubuntu UX bugs: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Incomplete Bug description: On Ubuntu Touch so far (vivid, mid-March 2015), it is still necessary to unlock the screen after it shuts off, even if the screen was only off for a few seconds. This is inconvenient, and it would be much easier if the lock didn't activate for ~10 seconds after the screen turns itself off. If the user activates the screen-off event by tapping the power button, then it's okay to lock immediately. If the screen times out though, it should probably delay before locking, to give the user a chance to turn the screen back on. Could we add a ~10 second delay between automatic screen shutoff and screen lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436630/+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 1436458] Re: Restart function is no longer needed
This bug report even suggests to add Reboot to bootloader when the device is in developer mode: https://bugs.launchpad.net/ubuntu- ux/+bug/1434142 -- 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/1436458 Title: Restart function is no longer needed Status in unity8 package in Ubuntu: Incomplete Bug description: 1. Hold down the power button. What you see: Power Off, Restart, and Cancel controls. What you should see: Power Off and Cancel only. The Restart function was always intended to be temporary, to be removed once the phone software was stable. Removing it would be one way of fixing bug 1412780, and would invalidate bug 1377146. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436458/+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 1436458] Re: Restart function is no longer needed
How is this in terms of convergence? Will Ubuntu Desktop not have a restart option any more either? Removing that option from unity8 will also remove it for the desktop - unless we treat it special. But then in theory unity8 shouldn't even care about whether it's a desktop or a phone or a tablet and right now doesn't have that information either. ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- 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/1436458 Title: Restart function is no longer needed Status in unity8 package in Ubuntu: Incomplete Bug description: 1. Hold down the power button. What you see: Power Off, Restart, and Cancel controls. What you should see: Power Off and Cancel only. The Restart function was always intended to be temporary, to be removed once the phone software was stable. Removing it would be one way of fixing bug 1412780, and would invalidate bug 1377146. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1436458/+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 1414930] Re: [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't work
I've put an utopic kernel build here, can be tested on trusty too: http://people.canonical.com/~tjaalton/utopic-fix/ -- 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/1414930 Title: [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't work Status in HWE Next Project: In Progress Status in The Linux Kernel: In Progress Status in libinput package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Status in systemd source package in Trusty: Confirmed Status in xserver-xorg-input-synaptics source package in Trusty: Invalid Status in linux source package in Utopic: Confirmed Status in systemd source package in Utopic: Confirmed Status in xserver-xorg-input-synaptics source package in Utopic: Invalid Bug description: Lenovo X1 3rd Carbon (201411-16196) Steps to reproduce the bug: 1, Log in to system 2, Click left/right/middle buttons of the touchpad Actual result: No response after clicking the buttons Expected results: Buttons work as expected behavirour ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: boot/vmlinuz-3.13.0-45-generic] ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1598 F pulseaudio /dev/snd/controlC0: u 1598 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 27 02:48:23 2015 HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f InstallationDate: Installed on 2015-01-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126) MachineType: LENOVO 20BTZ09ZUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET24W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTZ09ZUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BTZ09ZUS dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414930/+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 1436630] Re: must unlock screen even if it was only off for a few seconds
@Michael, sure, that's a valid request, but it's different/orthogonal from what is asked there. We could have 2 settings implemented but the request from here would still be valid for the locking case (I guess we want to animate the pre-locking to indicate it's going to kick in, and then let a small margin for the user to react) -- 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/1436630 Title: must unlock screen even if it was only off for a few seconds Status in Ubuntu UX bugs: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Incomplete Bug description: On Ubuntu Touch so far (vivid, mid-March 2015), it is still necessary to unlock the screen after it shuts off, even if the screen was only off for a few seconds. This is inconvenient, and it would be much easier if the lock didn't activate for ~10 seconds after the screen turns itself off. If the user activates the screen-off event by tapping the power button, then it's okay to lock immediately. If the screen times out though, it should probably delay before locking, to give the user a chance to turn the screen back on. Could we add a ~10 second delay between automatic screen shutoff and screen lock? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1436630/+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 1380463] Re: [enhancement] Set custom cursors
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.13.0 ** Changed in: mir Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1380463 Title: [enhancement] Set custom cursors Status in Mir: Fix Committed Status in XMir: Confirmed Status in mir package in Ubuntu: Triaged Bug description: We can now set cursors from a fixed set of named cursors. Toolkits expect to be able to create their own cursors - will Mir support this? To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1380463/+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 1339792] Re: Panel network icon - too much latency when network type changes
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1339792 Title: Panel network icon - too much latency when network type changes Status in indicator-network package in Ubuntu: Confirmed Status in indicator-network source package in Utopic: Confirmed Status in indicator-network source package in Vivid: Confirmed Status in indicator-network package in Ubuntu RTM: Confirmed Bug description: Testing image #u122 this morning, I ran into two separate scenarios where the panel network icon didn't always accurately reflect the current network technology due to some kind of latency detecting network changes ( ie. WiFi - 3G - WiFi ). Both scenarios were reproduced on mako. Scenario 1: 3G: online WiFi: enabled; connected to AP 1 - display network menu - tap another secure network - tap cancel when Password dialog is displayed At this point the indicator shows '3G' whereas the network menu still shows the original AP 1 as connected. After some period of time ( 10s - 1m ), the icon will change back to show that WiFi is connected. Scenario 2: 3G: online WiFi: connected to AP 1 - go to System Settings::WiFi - click Previous Networks - select the currently connected AP/network - click Forget Network - go back to WiFi settings The WiFi settings correctly shows the AP is no longer connected, however again the network icon takes some time ( 10s - 1m ) to reflect the change back to 3G. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1339792/+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 1340206] Re: [Network Menu] Enabling flight mode still shows the wifi icon
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1340206 Title: [Network Menu] Enabling flight mode still shows the wifi icon Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: Confirmed Status in indicator-network source package in Utopic: Confirmed Status in indicator-network source package in Vivid: Confirmed Status in Ubuntu RTM: New Bug description: When we enable flight mode the wifi icon is still shown. https://wiki.ubuntu.com/Networking#Title: On the phone ... the title ... should consist of: Flight Mode indication: ✈ the Flight Mode icon, if Flight Mode is on, otherwise nothing at all. ... Finally, Wi- Fi status indication: ... nothing at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1340206/+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 1318533] Re: Inappropriately depends on unity8
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1318533 Title: Inappropriately depends on unity8 Status in indicator-network package in Ubuntu: Triaged Status in unity8 package in Ubuntu: New Bug description: indicator-network 0.5.1+14.04.20140409.1-0ubuntu1, Ubuntu 14.04 1. apt-cache show indicator-network | grep Depends What happens: The result includes unity8. What should happen: The result does not include unity8. This prevents indicator-network from being used in Elementary Pantheon, for example. [Originally reported by Carlin Mangar in https://code.launchpad.net/~voldyman/indicator-network/onlyshowin- add-pantheon/+merge/215570.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1318533/+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 1267407] Re: Warn the user when connecting to an open AP which has been connected before as encrypted
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1267407 Title: Warn the user when connecting to an open AP which has been connected before as encrypted Status in indicator-network package in Ubuntu: New Bug description: scenario: Bob works at an office which provides encrypted wireless for the employees to securely connect to the company network. Somebody outside the office sets up an access point with the same SSID but without encryption hoping that somebody from the company connects to it. Bob does not notice that the AP he sees in his indicator is in fact not encrypted and connects to the open AP thinking he is connected to the company secure AP and now all his sensitive traffic is exposed to the attacker. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1267407/+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 1275761] Re: No standard explanation of why you're offline
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1275761 Title: No standard explanation of why you're offline Status in indicator-network package in Ubuntu: Triaged Bug description: When an Ubuntu Touch app tries to use data, but no data connection is available, there is no user-visible explanation of what is going on or how to fix it. A device might have no data connection because: (a) it is in Flight Mode, or (b) Wi-Fi is otherwise turned off, or (c) there is no cellular data connection, because: - the device has no SIM, or - it is not connected to a carrier, or - cellular data is turned off, or - the carrier is refusing data traffic (for example, because you are over quota), or - it is roaming and data roaming is turned off. (This list is not necessarily complete.) In cases where immediate connectivity is not vital, an app might detect that it is not available, and use queued actions or placeholders. For example, a mail client might store offline messages that you wanted to send, remember which messages you wanted to delete and file, and so on. Similarly, a Dash screen that usually returns online search results might show only offline results, with some sort of indication that you need to go online for online results to appear. But where an action absolutely requires connectivity to be useful, Ubuntu should provide some sort of standard UI explaining why you are offline and, where possible, explaining what to do to go online. If this message is modal, probably it should be limited so that it does not appear more than once before an app is unfocused (whether by focusing a different app, or the phone locking), and so it does not appear more than once every five minutes or so. The design should take into account the Wi-Fi prompt (bug 1287210), so that there aren't two prompts jostling each other. [Originally reported by David Isaacs.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1275761/+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 1361793] Re: VPN support is missing
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1361793 Title: VPN support is missing Status in indicator-network package in Ubuntu: Triaged Bug description: I am building an app for patients, nurses and doctors that is capable of reading a database and interacting with it, i.e.: modifying it, having levels of permission so there is no abuses, having changes recorded as user did this so there's responsibilitiy... In short, making a hospital work with an app that is in phones, tablets and desktops. This would require a secure connection and, in some (not to say many) countries, VPN is needed since HTTPS or other secure protocols are not supported, but VPN is used in hospitals as the secure system. Since there is no VPN support, this app will not be ready to function in a place where only VPN is supported. This is one of the reasons I think VPN support is important, since there are applications that require it to be international and secure, and, without it, this internationalitation would be limited to the country's possibilities. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1361793/+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 1287210] Re: No indication that Wi-Fi is available (Prompt when not connected)
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1287210 Title: No indication that Wi-Fi is available (Prompt when not connected) Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: Ubuntu Trusty r188 0. If you haven't already, connect to a Wi-Fi network. 1. In System Settings Wi-Fi, turn off Wi-Fi. 2. Turn off Auto-join previous networks. 3. Switch from System Settings to anything else. 4. Turn on Wi-Fi. What happens: Nothing. What should happen: You're prompted to join the previously used Wi-Fi network. https://wiki.ubuntu.com/Networking#wifi-connecting-prompted: A prompt should appear, suggesting that you connect to Wi-Fi, if all of these conditions are true... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1287210/+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 1301699] Re: Indicators do not show in Pantheon
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1301699 Title: Indicators do not show in Pantheon Status in elementary OS: Fix Released Status in Application Indicators: New Status in The Date and Time Indicator: New Status in The Session Menu: New Status in Sound Menu: New Status in indicator-datetime package in Ubuntu: Fix Released Status in indicator-network package in Ubuntu: New Status in indicator-sound package in Ubuntu: Fix Released Status in indicator-session source package in Trusty: Fix Released Bug description: [Impact] It looks like OnlyShowIn=Unity;GNOME; has been added to indicator- datetime, indicator-session, and indicator-sound We should provide a patch to add Pantheon to that list. [Test Case] (1) install the Pantheon desktop sesssion (eg. Elementary OS) and log in (2) verify the appropriate indicator (for this case, session indicator) appears (3) install the Unity 7 desktop session and log in (4) verify the indicator still appears [Regression Potential] A typo in the modified .desktop file could cause the indicator to not appear in a Ubuntu session such as Unity 7 or Gnome Flashback. To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1301699/+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 1288365] Re: indicator-secret-agent crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1288365 Title: indicator-secret-agent crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() Status in indicator-network package in Ubuntu: Triaged Bug description: Just logged on and this happened. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: indicator-network 0.5.1+14.04.20140207-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-88.5-mptcp Uname: Linux 3.8.0-88-mptcp x86_64 ApportVersion: 2.13.2-0ubuntu5 Architecture: amd64 Date: Wed Mar 5 18:43:11 2014 ExecutablePath: /usr/lib/x86_64-linux-gnu/indicator-secret-agent InstallationDate: Installed on 2012-03-08 (727 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta amd64 (20120301) ProcCmdline: /usr/lib/x86_64-linux-gnu/indicator-secret-agent Signal: 6 SourcePackage: indicator-network StacktraceTop: __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 __cxa_throw () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 SecretAgent::SecretAgent(QDBusConnection const, QDBusConnection const, QObject*) () SystemImageInfo: Error: [Errno 2] Ingen slik fil eller filkatalog: 'system-image-cli' Title: indicator-secret-agent crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() UpgradeStatus: Upgraded to trusty on 2014-03-04 (0 days ago) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1288365/+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 1339792] Re: Panel network icon - too much latency when network type changes
From Jussi's investigation, this sounds like it might be an issue in ofono ** Tags added: connectivity ** Also affects: ofono (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1339792 Title: Panel network icon - too much latency when network type changes Status in indicator-network package in Ubuntu: Confirmed Status in ofono package in Ubuntu: New Status in indicator-network source package in Utopic: Confirmed Status in ofono source package in Utopic: New Status in indicator-network source package in Vivid: Confirmed Status in ofono source package in Vivid: New Status in indicator-network package in Ubuntu RTM: Confirmed Bug description: Testing image #u122 this morning, I ran into two separate scenarios where the panel network icon didn't always accurately reflect the current network technology due to some kind of latency detecting network changes ( ie. WiFi - 3G - WiFi ). Both scenarios were reproduced on mako. Scenario 1: 3G: online WiFi: enabled; connected to AP 1 - display network menu - tap another secure network - tap cancel when Password dialog is displayed At this point the indicator shows '3G' whereas the network menu still shows the original AP 1 as connected. After some period of time ( 10s - 1m ), the icon will change back to show that WiFi is connected. Scenario 2: 3G: online WiFi: connected to AP 1 - go to System Settings::WiFi - click Previous Networks - select the currently connected AP/network - click Forget Network - go back to WiFi settings The WiFi settings correctly shows the AP is no longer connected, however again the network icon takes some time ( 10s - 1m ) to reflect the change back to 3G. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1339792/+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 1427205] Re: indicator shows (dozens of) out of range access points
** Changed in: indicator-network (Ubuntu) Status: Incomplete = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1427205 Title: indicator shows (dozens of) out of range access points Status in the base for Ubuntu mobile products: In Progress Status in indicator-network package in Ubuntu: Invalid Status in network-manager package in Ubuntu: In Progress Bug description: current build number: 129 device name: krillin channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/vivid-proposed last update: 2015-03-02 07:41:43 version version: 129 version ubuntu: 20150302 version device: 20150210-95b6a9f version custom: 20150302 TEST CASE: 1. Enable Wifi 2. Have a walk with the DUT outside in an area with lot of visible access points. 3. Walk in and out of range of these access points. EXPECTED RESULT: After the walk only the access points that are in range are visible in the indicator ACTUAL RESULT: All the access points the device saw are listed in the indicator (up to several dozens) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-network 0.5.1+15.04.20150217.1-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.16.1-0ubuntu2 Architecture: armhf Date: Mon Mar 2 14:02:40 2015 InstallationDate: Installed on 2015-03-02 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (20150302-020203) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1427205/+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 1436775] Re: pulseaudio crashed with SIGABRT in pa_object_unref()
*** This bug is a duplicate of bug 1430785 *** https://bugs.launchpad.net/bugs/1430785 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1430785, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1436775/+attachment/4356668/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1436775/+attachment/4356671/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1436775/+attachment/4356673/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1436775/+attachment/4356674/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1436775/+attachment/4356675/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1436775/+attachment/4356676/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1436775/+attachment/4356677/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1430785 ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1436775 Title: pulseaudio crashed with SIGABRT in pa_object_unref() Status in pulseaudio package in Ubuntu: New Bug description: Upon log in pulseaudio crashed. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: pulseaudio 1:6.0-0ubuntu4 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic i686 ApportVersion: 2.16.2-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: slickymaster 1983 F pulseaudio CrashCounter: 1 Date: Thu Mar 26 10:04:13 2015 ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2014-07-15 (253 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Alpha i386 (20140506) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Signal: 6 SourcePackage: pulseaudio StacktraceTop: ?? () from /usr/lib/libpulsecore-6.0.so pa_object_unref () from /usr/lib/libpulsecore-6.0.so main () Title: pulseaudio crashed with SIGABRT in pa_object_unref() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1436775/+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 1319728] Re: indicator-network needs to declare a minimal version of unity8 in the package dependencies
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1319728 Title: indicator-network needs to declare a minimal version of unity8 in the package dependencies Status in indicator-network package in Ubuntu: Confirmed Bug description: it recently happened that we had a change of the indicator protocol in unity8. due to indicator-network not declaring a Breaks: unity8 ( $minimal_version) dependency against the first unity8 version that ships the needed protocol, indicator-network was able to migrate alone from the proposed archive pocket to the main archive which caused breakage. to prevent this in the future indicator-network mush add a dependency on the minimal version of unity8 that ships the needed protocol version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1319728/+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 1366014] Re: [indicators] In a Dual SIM phone, There is no way to know which of the two SIMs is being used for cellular data.
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1366014 Title: [indicators] In a Dual SIM phone, There is no way to know which of the two SIMs is being used for cellular data. Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: Fix Released Status in indicator-network source package in Utopic: In Progress Status in indicator-network source package in Vivid: Fix Released Status in indicator-network package in Ubuntu RTM: Fix Released Bug description: Pulled as separate task from bug #1350739, per comment #6: * There is no way to know which of the two SIMs is being used for cellular data. Also, it looks like the displayed indicator mixes data from different slots: when I have a connection on the secondary slot using EDGE, I see an icon with an H some times, and with an E (the right one) some times. The H is probably taking from the technology in the primary slot, which is not attached. Also, related to this one: mobile broadband data connection speed is right now always coming from SIM 1, even if SIM 2 is the one used for mobile broadband. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1366014/+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 1245951] Re: Wrong oFono property used for data technology indication
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1245951 Title: Wrong oFono property used for data technology indication Status in the base for Ubuntu mobile products: New Status in indicator-network package in Ubuntu: Triaged Bug description: Image: Touch #100 ( aka v1.0 ). The current indicator-network code uses the ofono's NetworkRegistration interface's Technology property to determine which mobile data connection icon to display on the status bar. The code currently compares the value of Technology to: - gsm -- this causes 2G ( or a tortoise ) to be displayed - umts -- this causes 3G to be displayed - edge -- this causes E to be displayed - hspa -- this causes H to be displayed - lte -- valid, but currently not supported in the ofono/rilmodem driver ( LTE isn't yet 100% supported ) The code instead should be examining ofono's ConnectionManager interface's Bearer property. This is not currently being set by the ofono/rilmodem code ( see bug #1245954 for more details ). The valid values of the Bearer property ( with associated icons in parentheses ) are: none, gprs ( 2G ), edge ( E ), umts ( 3G ), hsupa/hsdpa/hspa ( H ), and lte ( L ). oFono doesn't currently support reporting HSPA+, whereas RIL does, so if have the need for differentiating between HSPA and HSPA+, then we'll need to patch ofono so that the value hspap is valid for Bearer. - To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1245951/+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 1348265] Re: Wifi networks should be ordered by strength, with connected at top
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1348265 Title: Wifi networks should be ordered by strength, with connected at top Status in indicator-network package in Ubuntu: Triaged Bug description: Order by signal strength Connected network at top. Maximum of 5 connections (in indicators) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1348265/+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 1235120] Re: No icon animation or other indication when establishing a connection
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1235120 Title: No icon animation or other indication when establishing a connection Status in indicator-network package in Ubuntu: Triaged Bug description: On phone I'd expect some kind of indication when device tries to establish a connection. https://wiki.ubuntu.com/Networking#connecting: While Ubuntu for PC is trying to establish any network connection, the title of the network menu should be a spinner. Similarly, while Ubuntu Phone is trying to establish a wi-fi connection, the wi-fi indicator should be an animated wi-fi icon. In both cases, the item for that connection should have a spinner too. If the connection is successful, the latter spinner should be replaced by a radio mark or checkmark as appropriate. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1235120/+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 1091391] Re: [indicators] [network] No Validation of Wi-Fi Key/Passphrases is performed
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1091391 Title: [indicators] [network] No Validation of Wi-Fi Key/Passphrases is performed Status in indicator-network package in Ubuntu: Triaged Bug description: The current network indicator does no checking of Wi-Fi key or passphrases, and thus allows a user to enter an invalid key or passphrase and initiate a connection attempt. For access points using WEP, there are four valid key lengths: * 5 ASCII characters or 10 hex characters * 13 ASCII characters or 26 hex characters For APs using WPA Personal/PSK, a valid passphrase can be between 8 and 63 characters in length. A full 256-bit key can be specified by entering 64 hex characters. Note, the chewie server should also probably do some validation as well. It shouldn't be possible for a new network to be created with a single character key ( see attached file ). Steps to Reproduce: 1. Open the network menu and select an access point known to be using WEP security 2. Enter a 1 character key 3. Click OK Expected Result: The user cannot initiate a connection with an invalid key. Actual Result: The auth dialog is dismissed and the user appears connected ( note, this is another problem ) Build Details: Manhattan/Maguro #160 chewie: 0.2.6~quantal1 indicators-client-plugin-network: 0.20~quantal1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1091391/+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 1159011] Re: Network information should not be considered user private
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1159011 Title: Network information should not be considered user private Status in indicator-network package in Ubuntu: Triaged Bug description: This happens to me each day after I update to the daily image. Steps: 1. Update to daily image 2. Try to swipe from the top of the screen across the wireless symbol to activate wireless Result: Nothing happens Expected: The indicator panel is revealed and I can choose my wireless connection Steps: 3. Swipe from the side to activate the launcher 4. Choose an application, such as facebook 5. Swipe from teh top as in step #2 Result: The indicator panel appears as expected and I can set my wireless https://wiki.ubuntu.com/Networking#Structure: In the login screen, you should still be able to connect to networks so that you can use remote login. Therefore, the indicator and menu should be present as normal, but on the PC, any items that lead to System Settings should be insensitive. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1159011/+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 1435242] Re: Problematic type casting between int/long?
** Changed in: cinder (Ubuntu)
Status: New = Fix Committed
** Changed in: cinder (Ubuntu)
Importance: Undecided = High
** Changed in: cinder (Ubuntu)
Assignee: (unassigned) = James Page (james-page)
--
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/1435242
Title:
Problematic type casting between int/long?
Status in cinder package in Ubuntu:
Fix Committed
Status in python2.7 package in Ubuntu:
New
Bug description:
We're seeing this error with the new kilo-3 milestone:
==
FAIL:
cinder.tests.test_utils.GetBlkdevMajorMinorTestCase.test_get_blkdev_major_minor_file
cinder.tests.test_utils.GetBlkdevMajorMinorTestCase.test_get_blkdev_major_minor_file
--
_StringException: Traceback (most recent call last):
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 721,
in test_get_blkdev_major_minor_file
dev = self._test_get_blkdev_major_minor_file('/dev/made_up_disk1')
File /usr/lib/python2.7/dist-packages/mock.py, line 1210, in patched
return func(*args, **keywargs)
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 712,
in _test_get_blkdev_major_minor_file
dev = utils.get_blkdev_major_minor(test_file)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 656, in
get_blkdev_major_minor
return get_blkdev_major_minor(devpath, False)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 645, in
get_blkdev_major_minor
return '%d:%d' % (os.major(st.st_rdev), os.minor(st.st_rdev))
SystemError: ../Objects/longobject.c:998: bad argument to internal function
Traceback (most recent call last):
_StringException: Empty attachments:
stderr
stdout
Traceback (most recent call last):
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 721,
in test_get_blkdev_major_minor_file
dev = self._test_get_blkdev_major_minor_file('/dev/made_up_disk1')
File /usr/lib/python2.7/dist-packages/mock.py, line 1210, in patched
return func(*args, **keywargs)
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 712,
in _test_get_blkdev_major_minor_file
dev = utils.get_blkdev_major_minor(test_file)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 656, in
get_blkdev_major_minor
return get_blkdev_major_minor(devpath, False)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 645, in
get_blkdev_major_minor
return '%d:%d' % (os.major(st.st_rdev), os.minor(st.st_rdev))
SystemError: ../Objects/longobject.c:998: bad argument to internal function
Traceback (most recent call last):
_StringException: Empty attachments:
stderr
stdout
Traceback (most recent call last):
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 721,
in test_get_blkdev_major_minor_file
dev = self._test_get_blkdev_major_minor_file('/dev/made_up_disk1')
File /usr/lib/python2.7/dist-packages/mock.py, line 1210, in patched
return func(*args, **keywargs)
File /build/buildd/cinder-2015.1~b3/cinder/tests/test_utils.py, line 712,
in _test_get_blkdev_major_minor_file
dev = utils.get_blkdev_major_minor(test_file)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 656, in
get_blkdev_major_minor
return get_blkdev_major_minor(devpath, False)
File /build/buildd/cinder-2015.1~b3/cinder/utils.py, line 645, in
get_blkdev_major_minor
return '%d:%d' % (os.major(st.st_rdev), os.minor(st.st_rdev))
SystemError: ../Objects/longobject.c:998: bad argument to internal function
This is evidently not impacting cinder on 14.04, just 15.04 so I would
suspect some sort of python 2.7.9 issue.
Casting to long appears to workaround this problem.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cinder/+bug/1435242/+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 1349309] Re: Require special menu type for settings menus
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** No longer affects: indicator-network -- 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/1349309 Title: Require special menu type for settings menus Status in Bluetooth Menu: Triaged Status in The Date and Time Indicator: Triaged Status in The Power Indicator: Triaged Status in Sound Menu: New Status in indicator-network package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: The settings menus should have a custom type so that we can specialize them in the UI. com.canonical.indicator.link Attached image to show what design want. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1349309/+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 1378712] Re: extended data for xCanonicalPinPopup should also have xCanonicalPinPopupTitle
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** No longer affects: indicator-network -- 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/1378712 Title: extended data for xCanonicalPinPopup should also have xCanonicalPinPopupTitle Status in indicator-network package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: In order to visually align the SIM entry warning popup with the passcode warning popup, the text would need to be split into title and text. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1378712/+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 1381448] Re: Support network over USB in developer mode
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1381448 Title: Support network over USB in developer mode Status in Ubuntu Connectivity API: Triaged Status in indicator-network package in Ubuntu: Triaged Bug description: Currently the SDK has to use adb forward in order to connect and talk to the devices. However it would be much more reliable if we could create a network over USB and talk directly to it. Probably even run a DHCP server on usb0 so we do not need to setup the interface ourselves and provide a DBUS callback so the SDK can trigger the usbnet to be created over ADB. Quotes from a conversation with Wellark on IRC: zbenjamin Wellark: would be interesting for the SDK zbenjamin Wellark: instead of adb forwarding the ports, which is totally unreliable, we could create a network with the phone and talk to it directly Wellark zbenjamin: well, you file a bug Wellark zbenjamin: then you tell my manager to get me to do the UI zbenjamin Wellark: the idea would be that we setup the initial stuff with adb. And then switch over to usb network which is decoupled from the adb completely Wellark zbenjamin: yep. Wellark adb would only make one call over dbus zbenjamin Wellark: having a dhcp running on the usb interface would make things super easy Wellark com.ubuntu.connectivity.usbnet.Enable() Wellark or something Wellark that would kick up the usbnet Wellark zbenjamin: yep. and zeroconf dns zbenjamin yeah. And we could make ssh only listen on this interface instead of all, and enable wlan only if the user checks a box in the UI Wellark so you don't have to deal with IP's zbenjamin exactly To manage notifications about this bug go to: https://bugs.launchpad.net/connectivity-api/+bug/1381448/+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 1322490] Re: [indicators] Clicking on a connected network's checkbox disconnects re-connects
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings-components in Ubuntu. https://bugs.launchpad.net/bugs/1322490 Title: [indicators] Clicking on a connected network's checkbox disconnects re-connects Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: Triaged Status in ubuntu-settings-components package in Ubuntu: Triaged Bug description: indicator-network 0.5.1+14.10.20140516.2-0ubuntu1, Ubuntu Utopic 1. Unlock the phone 2. Drag down the indicator for networking 3. Select a wifi AP sign into it 4. Drag down the indicator for networking 5. Try to uncheck it. What happens: The network disconnects and reconnects. What should happen: Nothing. https://wiki.ubuntu.com/Networking#wi-fi-menu: 2. If the card is powered on, up to 6 (phone) or 20 (PC) radio items representing known Wi-Fi networks... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1322490/+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 1304500] Re: Indicator Test Plan QA Review
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1304500 Title: Indicator Test Plan QA Review Status in Bluetooth Menu: New Status in The Date and Time Indicator: New Status in Indicator keyboard: New Status in Indicator Location: New Status in The Messaging Menu: New Status in The Power Indicator: New Status in The Session Menu: New Status in Sound Menu: New Status in The Sync Menu: New Status in indicator-bluetooth package in Ubuntu: New Status in indicator-network package in Ubuntu: New Bug description: indicator-bluetooth Additional tests required to ensure indicator status reflects Bluetooth states (enable/disable, scanning, device listing, pairing status etc.) indicator-datetime Additional tests required to ensure indicator menu includes upcoming events indicator-keyboard N/A for unity 8 Expand test cases and ensure menu options and keyboard language can be set and indicator is updated with correct language indicator-location Additional tests to ensure Location and GPS menu items can be enabled/disabled correctly Does indicator status change when a location fix is available? indicator-messages Additional tests to include new messaging items are displayed correctly in indicator status menu indicator-network Additional tests to include Wi-Fi scanning and connection Ensure indicator icon reflects signal strength for Wi-Fi and telephone network indicator-power Additional tests required to ensure indicator status reflects power states (battery level, charging, charged) Display brightness slider is functional indicator-session Is the Session indicator used on Unity8? Ensure test plan is valid. indicator-sound Additional tests to ensure volume slider is functional Indicator changes according to volume level set on slider indicator-sync Is the Sync indicator used on Unity8? Ensure test plan is valid. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1304500/+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 1381516] Re: wifi indicator icon disappears after couple hours using
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1381516 Title: wifi indicator icon disappears after couple hours using Status in indicator-network package in Ubuntu: Incomplete Bug description: had this on krillin ubuntu-rtm r104 and r105; after couple hours of using the phone the network indicator wifi icon disappears even though I am on wifi. I am attaching indicator-network.log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1381516/+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 1411527] Re: should prompt the user when connecting to an insecure network
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1411527 Title: should prompt the user when connecting to an insecure network Status in indicator-network package in Ubuntu: New Bug description: To protect the user, we should inform the user that he is trying to connect to a potentially insecure network (Open, WEP, WPA). [Young Pirate hacker gets top security secrets] http://www.net-security.org/secworld.php?id=17828 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1411527/+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 1420950] Re: Can't connect to Enterprise WIFI with BQ Ubuntu Edition
*** This bug is a duplicate of bug 1283763 *** https://bugs.launchpad.net/bugs/1283763 ** This bug has been marked a duplicate of bug 1283763 Cannot connect to WPA Enterprise networks -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1420950 Title: Can't connect to Enterprise WIFI with BQ Ubuntu Edition Status in indicator-network package in Ubuntu: New Bug description: Unable to connect to a enterprise WIFI. No login screen appears. You have here the parameters: http://thinkonbytes.blogspot.com.es/2014/09/conectar-wifisferatelecable-desde-ubuntu.html Thanks in advance! The mobile is: phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 16 device name: krillin channel: ubuntu-touch/stable/bq-aquaris.en alias: ubuntu-touch/ubuntu-rtm/14.09 last update: 2014-01-01 01:07:56 version version: 16 version ubuntu: 20150129 version device: 20150129-c75dcfb version custom: 20150129-528-26-182 phablet@ubuntu-phablet:~$ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1420950/+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 1340206] Re: [Network Menu] Enabling flight mode still shows the wifi icon
** Tags added: connectivity -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1340206 Title: [Network Menu] Enabling flight mode still shows the wifi icon Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: Confirmed Status in indicator-network source package in Utopic: Confirmed Status in indicator-network source package in Vivid: Confirmed Status in Ubuntu RTM: New Bug description: When we enable flight mode the wifi icon is still shown. https://wiki.ubuntu.com/Networking#Title: On the phone ... the title ... should consist of: Flight Mode indication: ✈ the Flight Mode icon, if Flight Mode is on, otherwise nothing at all. ... Finally, Wi- Fi status indication: ... nothing at all To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1340206/+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 1301429] Re: Available networks: heading is missing
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Changed in: indicator-network (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1301429 Title: Available networks: heading is missing Status in indicator-network package in Ubuntu: Triaged Status in ubuntu-system-settings package in Ubuntu: Confirmed Bug description: Ubuntu Trusty r250 1. In System Settings, navigate to Wi-Fi. 2. Turn on Wi-Fi if it is not on already. What you see: The Wi-Fi switch is immediately followed by the list of available networks. What you should see: The list of available networks has an introductory label, Available networks:. https://wiki.ubuntu.com/Networking#phone-wifi Combined with the poor design and layout of the toolkit's radio buttons, this problem just confused a new colleague, who thought that two networks were selected at once. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1301429/+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 1390136] Re: need a transition state for indicators reflecting laggy backends
** Tags added: connectivity -- 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/1390136 Title: need a transition state for indicators reflecting laggy backends Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Triaged Status in indicator-network source package in Utopic: Confirmed Status in ubuntu-system-settings source package in Utopic: Confirmed Status in indicator-network source package in Vivid: Confirmed Status in ubuntu-system-settings source package in Vivid: Confirmed Status in unity8 source package in Vivid: Triaged Status in indicator-network package in Ubuntu RTM: New Status in ubuntu-system-settings package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: New Bug description: spawned from efforts in bug 1336715 because the user's input toggle for airplane mode is both a reflection of user intent the state of the backendand the backend is unfortunately variable lengthy to change (anywhere from 1 to ~10+ seconds sometimes) we need to have an intermediate/transition statee.g. toggle to airplane mode onthen animate somehow that there's a transition happening, until it either fails/succeeds comment from dizzypaty Between the user’s action of toggling the airplane switcher on and/or off and the backend updating the state, the indicator icon displayed on the statusbar should be the following: network-idle.svg (https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk). Desired resolution Summary: the interface should immediately respond to user input confirming the action, even if the backend takes up to 20 seconds to actually change state. Having the UI and backend out of sync for up to 30 seconds is not a problem, as long as it always goes back into sync after this delay. 1.When the user changes the flight mode toggle switch it should instantly change state. 2.The backend should then be informed of the state change. 3.Up to 30 seconds later the backend completes the state change Note: The cellular connection indicator should always display the backend state, not the current flight mode toggle switch state Variation - user switches the flight mode toggle on and off rapidly. Once a flight mode state change request has been sent to the backend but before a conformation that the state change is complete is received, all further user interactions should be buffered on the client. When the client receives conformation of the state change from the backend it should check to see if the state is in sync with its buffer. If it is in sync nothing happens and the buffer is cleared. If it is not in sync another state change signal is sent to the backend and the buffer is cleared. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390136/+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 1432428] Re: unity-panel-service crashes when clicking onboard indicator
** Also affects: at-spi2-atk (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-atk in Ubuntu. https://bugs.launchpad.net/bugs/1432428 Title: unity-panel-service crashes when clicking onboard indicator Status in at-spi2-atk package in Ubuntu: New Status in onboard package in Ubuntu: New Bug description: When clicking the onboard indicator for the first time (after starting onboard), it can cause a crash of unity-panel-service. I never got crashes of unity-panel-service in connection with other indicators or applications, so I suppose it is something specific to the way how onboard creates its indicator. Apport is regularly collecting the information for this crash, but then it quietly disappears, without telling me whether the crash was automatically reported and to where. Unfortunately I don't have any references / bug report numbers etc. but I have a file _usr_lib_unity_unity-panel-service.1000.crash (13MB) that apport apparently created (I don't which format it is). I was hoping there is a chance someone here could find out more than when I report it to unity, because it happens very specifically when using onboard. How can I get more debug info, or is the crash file of any help? Ubuntu 14.10 64bit onboard 1.1.0+1949-0ppa1~utopic unity 7.3.1+14.10.20141016-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1432428/+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 1436074] Re: tab previews black [arale only]
Is this arale only? Wasn't it that webbrowser-app started using that new-in-Qt-5.4 grabToImage function when Qt 5.4, so would the old method work instead? Although I know the Qt 5.4 function was wanted to be used precisely since it's better/faster. If it's arale only (sorry, my mako is untouchable at the moment), my guess would be the grabToImage uses certain OpenGL ES functionality that may be broken in the arale's graphics driver. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1436074 Title: tab previews black [arale only] Status in Web Browser App: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: running vivid-proposed build 146 on arale When I swipe from bottom edge to reveal tabs, only the most recent tab has a preview. The other tabs are black where the preview should be. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1436074/+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 1318732] Re: [secret-agent] entering a wrong and short pass phrase first hides the dialog, then pops it up again and then closes it after a second or so
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1318732 Title: [secret-agent] entering a wrong and short pass phrase first hides the dialog, then pops it up again and then closes it after a second or so Status in indicator-network package in Ubuntu: Triaged Bug description: see summary. https://wiki.ubuntu.com/Networking#wi-fi-authenticating: When you choose 'Connect', the dialog should remain open to show connection progress ... If authentication fails, a variation of the dialog should appear. If you had just entered authentication details, this dialog should morph from the previous one. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1318732/+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 1351320] Re: Split Connected Available networks into separate sections
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1351320 Title: Split Connected Available networks into separate sections Status in indicator-network package in Ubuntu: Confirmed Bug description: Should be similar to nm-applet where the connected network is under a Connected Network submenu, and the other networks are in a Available Networks submenu. This has been design reviewed and confirmed. https://docs.google.com/a/canonical.com/document/d/1OyHUg_uUfmhDNa- 9UrMc1tZ_eH_99PEU_V2l1YFA1UY/edit#heading=h.en152umx77m2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1351320/+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 1319357] Re: enable tests on powerpc
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1319357 Title: enable tests on powerpc Status in indicator-network package in Ubuntu: Triaged Bug description: some tests are constantly failing on powerpc while passing reliably on all of the other arches. Need to investigate what is the root cause of this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1319357/+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 1351338] Re: Network indicator crashes on desktop suspend/resume
** No longer affects: indicator-network
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1351338
Title:
Network indicator crashes on desktop suspend/resume
Status in indicator-network package in Ubuntu:
Triaged
Bug description:
#0 0x7f8530404117 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 30259
selftid = 30261
#1 0x7f8530405808 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x7fff0ef1d90c,
sa_sigaction = 0x7fff0ef1d90c}, sa_mask = {__val = {140210018233734, 11782904,
86, 4294967295, 140210016872739, 4294967296, 140209968416240, 48005678696,
140209968416160, 140733444118966, 0, 0, 0, 21474836480, 140210051334144,
140210018248880}}, sa_flags = 11782996, sa_restorer = 0xb3d0a0
ActionGroupMerger::removeAction(std::shared_ptrAction)::__PRETTY_FUNCTION__}
sigs = {__val = {32, 0 repeats 15 times}}
#2 0x7f85303fcfc6 in __assert_fail_base (fmt=0x7f853054e8b0 %s%s%s:%u:
%s%sAssertion `%s' failed.\n%n, assertion=assertion@entry=0xb3cb54 count_iter
!= m_count.end(), file=file@entry=0xb3caf8
/home/nick/Work/phablet/unity/indicator-network/network/menumodel-cpp/action-group-merger.h,
line=line@entry=86, function=function@entry=0xb3d0a0
ActionGroupMerger::removeAction(std::shared_ptrAction)::__PRETTY_FUNCTION__
void ActionGroupMerger::removeAction(Action::Ptr)) at assert.c:92
str = 0x7f852005eea0 x
total = 4096
#3 0x7f85303fd072 in __GI___assert_fail (assertion=0xb3cb54 count_iter
!= m_count.end(), file=0xb3caf8
/home/nick/Work/phablet/unity/indicator-network/network/menumodel-cpp/action-group-merger.h,
line=86, function=0xb3d0a0
ActionGroupMerger::removeAction(std::shared_ptrAction)::__PRETTY_FUNCTION__
void ActionGroupMerger::removeAction(Action::Ptr)) at assert.c:101
No locals.
#4 0x00a06453 in
ActionGroupMerger::removeAction(std::shared_ptrAction) ()
No symbol table info available.
#5 0x00b00de2 in
ActionGroupMerger::remove(std::shared_ptrActionGroup) ()
No symbol table info available.
#6 0x00b245f3 in
WwanSection::Private::modemsChanged(std::setstd::shared_ptrModem,
std::lessstd::shared_ptrModem , std::allocatorstd::shared_ptrModem
const) ()
No symbol table info available.
#7 0x00b29236 in void std::_Mem_fnvoid
(WwanSection::Private::*)(std::setstd::shared_ptrModem,
std::lessstd::shared_ptrModem , std::allocatorstd::shared_ptrModem
const)::operator()std::setstd::shared_ptrModem,
std::lessstd::shared_ptrModem , std::allocatorstd::shared_ptrModem ,
void(WwanSection::Private*, std::setstd::shared_ptrModem,
std::lessstd::shared_ptrModem , std::allocatorstd::shared_ptrModem
) const ()
No symbol table info available.
#8 0x00b2899a in void std::_Bindstd::_Mem_fnvoid
(WwanSection::Private::*)(std::setstd::shared_ptrModem,
std::lessstd::shared_ptrModem , std::allocatorstd::shared_ptrModem
const) (WwanSection::Private*, std::_Placeholder1)::__callvoid,
std::setstd::shared_ptrModem, std::lessstd::shared_ptrModem ,
std::allocatorstd::shared_ptrModem , 0ul,
1ul(std::tuplestd::setstd::shared_ptrModem,
std::lessstd::shared_ptrModem , std::allocatorstd::shared_ptrModem
, std::_Index_tuple0ul, 1ul) ()
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1351338/+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 1258496] Re: show wireless encryption type
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1258496 Title: show wireless encryption type Status in indicator-network package in Ubuntu: Confirmed Bug description: Currently the indicator only shows whether or not a wireless network is secured, by showing a padlock. In a situation where we have two accesspoints which both have the same ESSID (name) but different encryption (e.g. WEP vs. WPA) they provide two separate networks. Now the indicator shows two identical items and the user has no way of figuring out which is which. Above scenario is a very rare one, but still completely valid. Neither nm-applet or macosx networking menu bother to deal with this situation, they just show two identical networks, but Android is always showing the encryption scheme beneath the network name. We can either A) do nothing B) always have the encryption type visible somehow C) be smart about it and only show the encryption type when we detect that the name and padlock is not enough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1258496/+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 1349371] Re: Current access point should not change until it is active
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1349371 Title: Current access point should not change until it is active Status in indicator-network package in Ubuntu: Triaged Bug description: When selecting an access point, the current AP changes immediately to the one which was selected selected, even if it is not yet connected. The access point should only change to current when it is connected. Would also be nice to be able to tell if the access point is trying to connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1349371/+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 1351326] Re: Indicator-network crashes when running on desktop
** No longer affects: indicator-network
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-network in
Ubuntu.
https://bugs.launchpad.net/bugs/1351326
Title:
Indicator-network crashes when running on desktop
Status in indicator-network package in Ubuntu:
Triaged
Bug description:
0x00aea885 in RootState::Private::updateNetworkingIcon() ()
(gdb) bt
#0 0x00aea885 in RootState::Private::updateNetworkingIcon() ()
#1 0x00ae9630 in
RootState::Private::Private(std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager) ()
#2 0x00aeb8bc in
RootState::RootState(std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager) ()
#3 0x00a3a269 in void
__gnu_cxx::new_allocatorRootState::constructRootState,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager(RootState*,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager) ()
#4 0x00a395f2 in
std::enable_ifstd::__and_std::allocator_traitsstd::allocatorRootState
::__construct_helperRootState,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager::type::value, void::type
std::allocator_traitsstd::allocatorRootState ::_S_constructRootState,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager(std::allocatorRootState, RootState*,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager) ()
#5 0x00a38cbc in decltype (_S_construct({parm#1}, {parm#2},
(forwardstd::shared_ptrconnectivity::networking::Manager)({parm#3}),
(forwardstd::shared_ptrModemManager)({parm#3})))
std::allocator_traitsstd::allocatorRootState ::constructRootState,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager(std::allocatorRootState, RootState*,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager) ()
#6 0x00a37b60 in std::_Sp_counted_ptr_inplaceRootState,
std::allocatorRootState,
(__gnu_cxx::_Lock_policy)2::_Sp_counted_ptr_inplacestd::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager(std::allocatorRootState,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager) ()
#7 0x00a3617a in void
__gnu_cxx::new_allocatorstd::_Sp_counted_ptr_inplaceRootState,
std::allocatorRootState, (__gnu_cxx::_Lock_policy)2
::constructstd::_Sp_counted_ptr_inplaceRootState, std::allocatorRootState,
(__gnu_cxx::_Lock_policy)2, std::allocatorRootState const,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager(std::_Sp_counted_ptr_inplaceRootState,
std::allocatorRootState, (__gnu_cxx::_Lock_policy)2*,
std::allocatorRootState const,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager) ()
#8 0x00a34518 in
std::enable_ifstd::__and_std::allocator_traitsstd::allocatorstd::_Sp_counted_ptr_inplaceRootState,
std::allocatorRootState, (__gnu_cxx::_Lock_policy)2
::__construct_helperstd::_Sp_counted_ptr_inplaceRootState,
std::allocatorRootState, (__gnu_cxx::_Lock_policy)2,
std::allocatorRootState const,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager::type::value, void::type
std::allocator_traitsstd::allocatorstd::_Sp_counted_ptr_inplaceRootState,
std::allocatorRootState, (__gnu_cxx::_Lock_policy)2
::_S_constructstd::_Sp_counted_ptr_inplaceRootState,
std::allocatorRootState, (__gnu_cxx::_Lock_policy)2,
std::allocatorRootState const,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager(std::allocatorstd::_Sp_counted_ptr_inplaceRootState,
std::allocatorRootState, (__gnu_cxx::_Lock_policy)2 ,
std::_Sp_counted_ptr_inplaceRootState, std::allocatorRootState, (
__gnu_cxx::_Lock_policy)2*, std::allocatorRootState const,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager) ()
#9 0x00a326ec in decltype (_S_construct({parm#1}, {parm#2},
(forwardstd::allocatorRootState const)({parm#3}),
(forwardstd::shared_ptrconnectivity::networking::Manager)({parm#3}),
(forwardstd::shared_ptrModemManager)({parm#3})))
std::allocator_traitsstd::allocatorstd::_Sp_counted_ptr_inplaceRootState,
std::allocatorRootState, (__gnu_cxx::_Lock_policy)2
::constructstd::_Sp_counted_ptr_inplaceRootState, std::allocatorRootState,
(__gnu_cxx::_Lock_policy)2, std::allocatorRootState const,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager(std::allocatorstd::_Sp_counted_ptr_inplaceRootState,
std::allocatorRootState, (__gnu_cxx::_Lock_policy)2 ,
std::_Sp_counted_ptr_inplaceRootState, std::allocatorRootState,
(__gnu_cxx::_Lock_policy)2*, std::allocatorRootState const,
std::shared_ptrconnectivity::networking::Manager,
std::shared_ptrModemManager) ()
#10 0x00a2ecce in
[Touch-packages] [Bug 1255097] Re: No confirmation that wi-fi hardware is turned on/off
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1255097 Title: No confirmation that wi-fi hardware is turned on/off Status in indicator-network package in Ubuntu: Confirmed Bug description: On a PC with a wi-fi or Bluetooth hotkey: 1. Turn off wi-fi or Bluetooth. 2. Turn on wi-fi or Bluetooth. What you see: 1. Nothing. 2. Nothing. What you should see: 1. Some kind of visible confirmation. 2. Some kind of visible confirmation. As described in public bug 404658, this is implemented for a Canonical OEM project in private bug 1213507, using a separate hotkey daemon. https://launchpadlibrarian.net/157232247/MOV_1319.mp4 It is probably better implemented in indicator-network, tracking actual rfkill events rather than hotkeys that might or might not be heeded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1255097/+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 1373463] Re: [indicators] Impossible to disable cellular data from indicator
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1373463 Title: [indicators] Impossible to disable cellular data from indicator Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: Triaged Bug description: I was wondering : Why it isn't possible to disable data from the network indicator ? Probably with a switch button that offer the choice between no data or data activated (with the last data activated state (2g only or 2G,3G,4G). Why this ? Because it's the first setting to change to save battery, and probably one of the most used (I asked around me, everyone agreed they would prefer that over Wi-Fi if only one was possible). I think it's stupid to go to the settings app for the most common action (and very frustrating). Of course, this also apply for the battery setting page (that already contain Wi-Fi, GPS, Bluetooth and brightness settings). I asked that on the phone ML, I've been invited to file a wishlist bug there to help designers with next iteration of network indicator. So here it is ! [1] : mailing list discussion with already some support to this idea : https://lists.launchpad.net/ubuntu-phone/msg09910.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1373463/+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 1283763] Re: Cannot connect to WPA Enterprise networks
** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1283763 Title: Cannot connect to WPA Enterprise networks Status in indicator-network package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Confirmed Bug description: I cannot connect to a wireless network that uses enterprise WPA (which asks not only for a password but also for a username) on a Touch device. It seems like there is just no GUI implemented to handle that, as nothing happens when I ty to connect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1283763/+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 1436799] [NEW] pcsc-lite does not start double free or corruption
Public bug reported: After upggranding in Ubuntu 14.04 i'm getting pcscdaemon.c:240:main() pcscd set to foreground with debug send to stdout 0135 configfile.l:254:DBGetReaderListDir() Parsing conf directory: /etc/reader.conf.d 0026 configfile.l:266:DBGetReaderListDir() Skipping non regular file: .. 0010 configfile.l:266:DBGetReaderListDir() Skipping non regular file: . 0010 configfile.l:307:DBGetReaderList() Parsing conf file: /etc/reader.conf.d/libccidtwin 0122 pcscdaemon.c:545:main() pcsc-lite 1.8.10 daemon ready. 1393 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 0094 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 0083 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x046D, PID: 0xC016, path: /dev/bus/usb/003/002 0099 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001 0099 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/004/001 0075 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/004/001 0196 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x04E6, PID: 0x5116, path: /dev/bus/usb/004/002 0027 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x04E6, PID: 0x5116, path: /dev/bus/usb/004/002 0011 hotplug_libudev.c:321:HPAddDevice() Adding USB device: SCR3310 Smart Card Reader 0050 readerfactory.c:989:RFInitializeReader() Attempting startup of SCR3310 Smart Card Reader [CCID Interface] (21120944218305) 00 00 using /usr/lib/pcsc/drivers/scmccid.bundle/Contents/Linux/libscmccid.so.5.0.27 0217 readerfactory.c:874:RFBindFunctions() Loading IFD Handler 3.0 Loading libscmccid 5.0.27 *** Error in `pcscd': double free or corruption (!prev): 0x09bc8348 *** ** Affects: pcsc-lite (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1436799 Title: pcsc-lite does not start double free or corruption Status in pcsc-lite package in Ubuntu: New Bug description: After upggranding in Ubuntu 14.04 i'm getting pcscdaemon.c:240:main() pcscd set to foreground with debug send to stdout 0135 configfile.l:254:DBGetReaderListDir() Parsing conf directory: /etc/reader.conf.d 0026 configfile.l:266:DBGetReaderListDir() Skipping non regular file: .. 0010 configfile.l:266:DBGetReaderListDir() Skipping non regular file: . 0010 configfile.l:307:DBGetReaderList() Parsing conf file: /etc/reader.conf.d/libccidtwin 0122 pcscdaemon.c:545:main() pcsc-lite 1.8.10 daemon ready. 1393 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 0094 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/003/001 0083 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x046D, PID: 0xC016, path: /dev/bus/usb/003/002 0099 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0002, path: /dev/bus/usb/001/001 0099 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/004/001 0075 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x1D6B, PID: 0x0001, path: /dev/bus/usb/004/001 0196 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x04E6, PID: 0x5116, path: /dev/bus/usb/004/002 0027 hotplug_libudev.c:269:get_driver() Looking for a driver for VID: 0x04E6, PID: 0x5116, path: /dev/bus/usb/004/002 0011 hotplug_libudev.c:321:HPAddDevice() Adding USB device: SCR3310 Smart Card Reader 0050 readerfactory.c:989:RFInitializeReader() Attempting startup of SCR3310 Smart Card Reader [CCID Interface] (21120944218305) 00 00 using /usr/lib/pcsc/drivers/scmccid.bundle/Contents/Linux/libscmccid.so.5.0.27 0217 readerfactory.c:874:RFBindFunctions() Loading IFD Handler 3.0 Loading libscmccid 5.0.27 *** Error in `pcscd': double free or corruption (!prev): 0x09bc8348 *** To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1436799/+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 1427064] Re: Wi-Fi indicator icon does not update when the connected AP's strength changes
** Tags added: connectivity ** Changed in: indicator-network (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1427064 Title: Wi-Fi indicator icon does not update when the connected AP's strength changes Status in indicator-network package in Ubuntu: New Bug description: The top panel Wi-Fi icon always indicates the signal strength of the connected AP at the time of connecting to it. Changes to the signal strength of the connected AP should update this icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1427064/+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 1436801] [NEW] Volume notifications give no audible feedback for volume changes
Public bug reported: On the desktop we have an audible pling sound if you adjust the volume, on the phone this seems to be missing. https://wiki.ubuntu.com/Sound#notification defines it though ... ** Affects: indicator-sound (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Volume notifications ive no audible feedback for volume changes + Volume notifications give no audible feedback for volume changes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1436801 Title: Volume notifications give no audible feedback for volume changes Status in indicator-sound package in Ubuntu: New Bug description: On the desktop we have an audible pling sound if you adjust the volume, on the phone this seems to be missing. https://wiki.ubuntu.com/Sound#notification defines it though ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1436801/+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 1421009] Re: unity8 sometimes hangs on boot
I've reflashed the device so this is with vivid #150 + 018. The MP in #23 (just adjusted for AP 1.5 branch) is now in the 018 PPA. The simplified test case seems fixed for me too, but unfortunately it'd look like running a whole suite like phablet-test-run ubuntuuitoolkit simply hangs at some point - in the sense that test app loads but nothing further happens. Killing the process gets the tests to continue. This ended up with: http://people.canonical.com/~tjyrinki/qt5/fail/qtbase_ubuntu5/ap- 2015_03_26-09_54_27-ubuntuuitoolkit-1-018.tests - potentially less failures (6) than before AP update, but more than before qtbase update. The second UITK run with qtbase + AP seemingly went uninterrupted further, but still with more (7) AP failures compared to before updating qtbase. However, at the end of the run it seemed like the test app was hanging - I tried gdb attaching to it, realized I didn't have debug symbols and detached. After this it seemed the it continued and the testing completed immediately: http://people.canonical.com/~tjyrinki/qt5/fail/qtbase_ubuntu5/ap- 2015_03_26-09_54_27-ubuntuuitoolkit-2-018.tests So it'd seem the AP patch does change behavior and fixes the simple testcase, but is not the real fix. Or it's possible it fixes the AP end but there is some sort hanging issue with the updated Qt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libusermetrics in Ubuntu. https://bugs.launchpad.net/bugs/1421009 Title: unity8 sometimes hangs on boot Status in autopilot package in Ubuntu: New Status in libusermetrics package in Ubuntu: Incomplete Status in qtbase-opensource-src package in Ubuntu: Incomplete Status in unity8 package in Ubuntu: Invalid Bug description: The following gdbus call is failing with a Error: Timeout was reached message: gdbus call --session --dest com.canonical.UnityGreeter --object-path / --method org.freedesktop.DBus.Properties.Get com.canonical.UnityGreeter IsActive This is being seen on krillin devices starting with image 106 from ubuntu-touch/devel-proposed. It doesn't happen every time, so far today, I've seen it 3 times from about 12 tests. On the most recent failure, I grabbed a console and tried repeatedly to run the command from the shell, even after 2 hours the timeout was still being returned (after about 28 seconds). A copy of ~/.cache/upstart/unity8.log is here: http://paste.ubuntu.com/10179482/ I have 3 test cases where the problem was observed: http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-qtchooser/1/console http://d-jenkins.ubuntu-ci:8080/job/vivid-boottest-gsettings-ubuntu-touch-schemas/1/console http://d-jenkins.ubuntu-ci:8080/job/fjg-boottest/3/console In all cases, the test is using adt-run (from autopkgtest) to drive a test on the phone device. adt-run uses the above gdbus call to determine if the desktop is active. In all the examples, the device was freshly flashed. Update 2015-03-25: the qtbase dbus update in silo 018 seems to address the boot issue, but causes autopilot to have problems seeing an application start, randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autopilot/+bug/1421009/+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 1436169] Re: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel()
** Information type changed from Private to Public -- 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/1436169 Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() Status in systemd package in Ubuntu: New Bug description: Crashed over night while recovering Backup. ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: systemd 219-4ubuntu9 ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2 Uname: Linux 3.19.0-10-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.16.2-0ubuntu4 Architecture: amd64 Date: Tue Mar 24 23:48:52 2015 ExecutablePath: /lib/systemd/systemd-logind ExecutableTimestamp: 1427124594 InstallationDate: Installed on 2015-03-23 (1 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) MachineType: Gigabyte Technology Co., Ltd. GA-MA790GP-UD4H ProcCmdline: /lib/systemd/systemd-logind ProcCwd: / ProcEnviron: LANG=de_DE.UTF-8 PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-10-generic root=UUID=45370e47-0377-4e9d-87fc-81889c091532 ro quiet splash Signal: 6 SourcePackage: systemd StacktraceTop: __epoll_wait_nocancel () at ../sysdeps/unix/syscall-template.S:81 ?? () ?? () __libc_start_main (main=0x7fe8459ef730, argc=1, argv=0x7ffd2f676e68, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7ffd2f676e58) at libc-start.c:289 ?? () Title: systemd-logind crashed with SIGABRT in __epoll_wait_nocancel() UpgradeStatus: Upgraded to vivid on 2015-03-24 (0 days ago) UserGroups: dmi.bios.date: 07/08/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F7c dmi.board.name: GA-MA790GP-UD4H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF7c:bd07/08/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA790GP-UD4H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA790GP-UD4H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA790GP-UD4H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1436169/+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 1436691] Re: Essential files are missing
** Description changed: I'm using Ubuntu 15.04 dev and upstart 1.13.2-0ubuntu10 doesn't contain - files like /sbin/init anymore. After upgrading to this package I wasn't - able to reboot/shutdown my system and after a hard reboot it hasn't - fully booted anymore. + files like /sbin/init anymore. This caused that after upgrading to this + package I wasn't able to reboot/shutdown my system and to fully boot it + after a hard reboot. -- 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/1436691 Title: Essential files are missing Status in upstart package in Ubuntu: New Bug description: I'm using Ubuntu 15.04 dev and upstart 1.13.2-0ubuntu10 doesn't contain files like /sbin/init anymore. This caused that after upgrading to this package I wasn't able to reboot/shutdown my system and to fully boot it after a hard reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1436691/+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 1414930] Re: [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't work
It includes the upstream commits plus BDW i915 bugfixes for bug 1434514 -- 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/1414930 Title: [Lenovo ThinkPad X1 Carbon 20BT] Buttons of Synaptics trackpad doesn't work Status in HWE Next Project: In Progress Status in The Linux Kernel: In Progress Status in libinput package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Fix Released Status in xserver-xorg-input-synaptics package in Ubuntu: Invalid Status in linux source package in Trusty: Confirmed Status in systemd source package in Trusty: Confirmed Status in xserver-xorg-input-synaptics source package in Trusty: Invalid Status in linux source package in Utopic: Confirmed Status in systemd source package in Utopic: Confirmed Status in xserver-xorg-input-synaptics source package in Utopic: Invalid Bug description: Lenovo X1 3rd Carbon (201411-16196) Steps to reproduce the bug: 1, Log in to system 2, Click left/right/middle buttons of the touchpad Actual result: No response after clicking the buttons Expected results: Buttons work as expected behavirour ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-45-generic 3.13.0-45.74 [modified: boot/vmlinuz-3.13.0-45-generic] ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: u 1598 F pulseaudio /dev/snd/controlC0: u 1598 F pulseaudio CurrentDesktop: Unity Date: Tue Jan 27 02:48:23 2015 HibernationDevice: RESUME=UUID=c553e9ba-b74b-43ad-8cf2-496531261e0f InstallationDate: Installed on 2015-01-27 (0 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20150126) MachineType: LENOVO 20BTZ09ZUS ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=1d34e685-c98b-41f3-b649-87770517b194 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-45-generic N/A linux-backports-modules-3.13.0-45-generic N/A linux-firmware 1.127.11 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/27/2014 dmi.bios.vendor: LENOVO dmi.bios.version: N14ET24W (1.02 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BTZ09ZUS dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN14ET24W(1.02):bd10/27/2014:svnLENOVO:pn20BTZ09ZUS:pvrThinkPadX1Carbon3rd:rvnLENOVO:rn20BTZ09ZUS:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.name: 20BTZ09ZUS dmi.product.version: ThinkPad X1 Carbon 3rd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414930/+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 1436074] Re: tab previews black [arale only]
...yes it reads in the title that it's arale only. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1436074 Title: tab previews black [arale only] Status in Web Browser App: Invalid Status in qtdeclarative-opensource-src package in Ubuntu: New Bug description: running vivid-proposed build 146 on arale When I swipe from bottom edge to reveal tabs, only the most recent tab has a preview. The other tabs are black where the preview should be. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1436074/+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 1412444] Re: no indication when the cellular network connection is not encrypted
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1412444 Title: no indication when the cellular network connection is not encrypted Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: Triaged Status in indicator-network package in Ubuntu: New Status in ofono package in Ubuntu: Confirmed Bug description: From TS 100 920 - V8.1.0: 3.3.3 Functional Requirements: The ME has to check if the user data confidentiality is switched on using one of the seven algorithms. In the event that the ME detects that this is not the case, or ceases to be the case (e.g. during handover), then an indication is given to the user. This ciphering indicator feature may be disabled by the SIM (see GSM 11.11). In case the SIM does not support the feature that disables the ciphering indicator, then the ciphering indicator feature in the ME shall be enabled by default. My understanding of this is that we should at least show a warning icon and maybe explanatory text inside the i-network and maybe relevant apps like phone-app and messaging-app that the cellular communication channel is not encrypted. Without encryption anyone with sufficient equipment can eavesdrop the voice and data communication between the cell tower and users phone. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1412444/+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 1427064] Re: Wi-Fi indicator icon does not update when the connected AP's strength changes
** Also affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** No longer affects: indicator-network -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1427064 Title: Wi-Fi indicator icon does not update when the connected AP's strength changes Status in indicator-network package in Ubuntu: New Bug description: The top panel Wi-Fi icon always indicates the signal strength of the connected AP at the time of connecting to it. Changes to the signal strength of the connected AP should update this icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1427064/+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
