[Touch-packages] [Bug 1389028] Re: u1 account crashes and gets removed when installing app
Sure, here they are: export UOA_LOGGING_LEVEL=2 export UOA_DAEMON_TIMEOUT= online-accounts-service the last command won't return; it will print its output on the console (or you can capture it into a file if you append a " > file.log" to the last command), and you can kill it with Ctrl+C after you are done creating the U1 account. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-system-settings- online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1389028 Title: u1 account crashes and gets removed when installing app Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Incomplete Bug description: platform: Ubuntu touch image: rtm #6 device: Mako after updating to rtm #6 today, I tried installing an app from the store. The app in question is the new Grooveshark app by Grooveshark (NOT the one by Adnane Belmadiaf) When I hit the install button, I get an error: Login Error Please log in to your Ubuntu One account Sure enough, my U1 is gone fron the registered online accounts. I can re-add my U1 account and try again to add the app but the same thing happens every time. Even after a device reboot. Note that it has something to do with this app. Other apps install normally. (Needless to say i have not tried every app or scope in the store so there might be others that trigger this as well.) Cheers, Mat To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings-online-accounts/+bug/1389028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 401823] Re: Gdk-WARNING **: XID collision, trouble ahead
Can someone please close this bug? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/401823 Title: Gdk-WARNING **: XID collision, trouble ahead Status in Chromium Browser: New Status in The Mozilla Firefox Browser: Invalid Status in GTK+ GUI Toolkit: Expired Status in Modular X11 Libraries: Confirmed Status in “firefox” package in Ubuntu: Fix Released Status in “firefox-3.5” package in Ubuntu: Invalid Status in “gtk+2.0” package in Ubuntu: Fix Released Status in “firefox” source package in Lucid: Invalid Status in “firefox-3.5” source package in Lucid: Invalid Status in “gtk+2.0” source package in Lucid: Invalid Status in “firefox” source package in Karmic: Invalid Status in “firefox-3.5” source package in Karmic: Won't Fix Status in “gtk+2.0” source package in Karmic: Fix Released Bug description: karmic testing in .xsession-errors: (firefox:24993): Gdk-WARNING **: XID collision, trouble ahead previously, have had this one: (nautilus:3572): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (bug report 401822) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/401823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388582] Re: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks
you need early patching or hda jack retask to change node 0x1a to [jack] hp and node from [jack] line out to [fixed] speaker at int ** Bug watch added: Linux Kernel Bug Tracker #67481 http://bugzilla.kernel.org/show_bug.cgi?id=67481 -- 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/1388582 Title: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have a fresh install of KUbuntu 14.10 with this problem and i come of a KUbuntu 13.10 without problems. I don't have any sound from speakers or headphone, i think the driver isn't loaded, but the microphone works, it records. The sound playback works too, but the sound doesn't go through speakers or headphones. I was testing with a lot of LiveCD KUbuntu when the problem comes. With LiveCDs KUbuntu 12.04.5 LTS, 12.10, 13.04 the sound works, they configs the sound system as "HDA Intel AD198x". Since LiveCDs 13.10, 14.04.1 LTS and, of course, 14.10 Live CD and my install, i have this problem, because the sound system is now "AD1986A". I will attach the alsa-info output for all this systems in my computer. But with HDA_Analyzer http://www.alsa- project.org/main/index.php/HDA_Analyzer i found the details of the problem: i can create a python script to brought back the sound working in a basic mode, like as previously. The details are activating EAPD in Card 0, Codec 0, Node 0x1b PIN (In my computer, it could be different in another) what brought back the sound to the speakers, and unmuting "Output Amplifier" in Card 0, Codec 0, Node 0x1a VAL[0] and VAL[1] to brought back sound to the headphones when they are plugged. I will attach too the output of this diff and the python script created by HDA_Analyzer for my system. At least, the basic working state should be back, because with a untoching fresh install there isn't any sound. There are related bugs here and other post in internet, but i collected all information i found and can give more if it's necessary. For additional information: Searching the solution, i tested too all the models availables for HDA Intel AD1986A (editing /etc/modprobe.d /alsa-base.conf with AD1986A models /usr/share/doc/alsa-base/driver /HD-Audio-Models.txt.gz) and i found the default one doesn't fit my system and anothers are better, but have problems of no sound too and i don't found how to fix these problem. When this bug is corrected, i want to help to found a better model for my computer, i don't know how now, but first it brought back the sound. Also, i test with snd-hda- tools https://launchpad.net/~diwic/+archive/ubuntu/hda and with hda- jack-sense-test the Green Line Out sense doesn't work (always NO present) but the Pink Mic sense works without problems. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thywalls 2380 F pulseaudio CurrentDesktop: KDE Date: Sun Nov 2 16:24:36 2014 InstallationDate: Installed on 2014-10-30 (3 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T12JNC.206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EasyNote_MX65 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12JNC.206:bd09/28/2006:svnPackardBellBV:pnEasyNote_MX65:pvrPB63E03104:rvnPackardBellBV:rnEasyNote_MX65:rvr1.0:cvnPackardBellBV:ct10:cvr: dmi.product.name: EasyNote_MX65 dmi.product.version: PB63E03104 dmi.sys.vendor: Packard Bell BV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1388582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Asser
** Changed in: dbus-cpp (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1382595 Title: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator- network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Assertion `mutex->__data.__owner == 0' failed. Status in DBus C++: Fix Released Status in “dbus-cpp” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu: Invalid Status in “location-service” package in Ubuntu: Invalid Status in “dbus-cpp” package in Ubuntu RTM: Fix Released Status in “indicator-network” package in Ubuntu RTM: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20141015-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988 contains more details. steps to reproduce: (need to trigger race condition) 1. pull down network indicator 2. toggle flight mode on and off quickly a few times 3. click sim card 1 and 2 4. toggle flight mode 5. swipe up close indicators 6. repeat steps 1-5 until crash occurs expected results: no crash happens actual results: Bluetooth indicator blinks (appear and disappear) in indicator bar at top of screen, and network indicator crashes. additional info: eventually the bluetooth indicator appears stable in the indicators at the top of the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388582] Re: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks
https://bugzilla.kernel.org/show_bug.cgi?id=67481 -- 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/1388582 Title: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have a fresh install of KUbuntu 14.10 with this problem and i come of a KUbuntu 13.10 without problems. I don't have any sound from speakers or headphone, i think the driver isn't loaded, but the microphone works, it records. The sound playback works too, but the sound doesn't go through speakers or headphones. I was testing with a lot of LiveCD KUbuntu when the problem comes. With LiveCDs KUbuntu 12.04.5 LTS, 12.10, 13.04 the sound works, they configs the sound system as "HDA Intel AD198x". Since LiveCDs 13.10, 14.04.1 LTS and, of course, 14.10 Live CD and my install, i have this problem, because the sound system is now "AD1986A". I will attach the alsa-info output for all this systems in my computer. But with HDA_Analyzer http://www.alsa- project.org/main/index.php/HDA_Analyzer i found the details of the problem: i can create a python script to brought back the sound working in a basic mode, like as previously. The details are activating EAPD in Card 0, Codec 0, Node 0x1b PIN (In my computer, it could be different in another) what brought back the sound to the speakers, and unmuting "Output Amplifier" in Card 0, Codec 0, Node 0x1a VAL[0] and VAL[1] to brought back sound to the headphones when they are plugged. I will attach too the output of this diff and the python script created by HDA_Analyzer for my system. At least, the basic working state should be back, because with a untoching fresh install there isn't any sound. There are related bugs here and other post in internet, but i collected all information i found and can give more if it's necessary. For additional information: Searching the solution, i tested too all the models availables for HDA Intel AD1986A (editing /etc/modprobe.d /alsa-base.conf with AD1986A models /usr/share/doc/alsa-base/driver /HD-Audio-Models.txt.gz) and i found the default one doesn't fit my system and anothers are better, but have problems of no sound too and i don't found how to fix these problem. When this bug is corrected, i want to help to found a better model for my computer, i don't know how now, but first it brought back the sound. Also, i test with snd-hda- tools https://launchpad.net/~diwic/+archive/ubuntu/hda and with hda- jack-sense-test the Green Line Out sense doesn't work (always NO present) but the Pink Mic sense works without problems. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thywalls 2380 F pulseaudio CurrentDesktop: KDE Date: Sun Nov 2 16:24:36 2014 InstallationDate: Installed on 2014-10-30 (3 days ago) InstallationMedia: Kubuntu 14.10 "Utopic Unicorn" - Release i386 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T12JNC.206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EasyNote_MX65 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12JNC.206:bd09/28/2006:svnPackardBellBV:pnEasyNote_MX65:pvrPB63E03104:rvnPackardBellBV:rnEasyNote_MX65:rvr1.0:cvnPackardBellBV:ct10:cvr: dmi.product.name: EasyNote_MX65 dmi.product.version: PB63E03104 dmi.sys.vendor: Packard Bell BV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1388582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387959] Re: [TOPBLOCKER] unity8 crash in image krillin rtm 139
** Changed in: qtubuntu-media (Ubuntu) Importance: Undecided => Critical ** Changed in: qtubuntu-media (Ubuntu) Status: New => In Progress ** Changed in: qtubuntu-media (Ubuntu) Assignee: (unassigned) => Thomas Voß (thomas-voss) -- 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/1387959 Title: [TOPBLOCKER] unity8 crash in image krillin rtm 139 Status in “media-hub” package in Ubuntu: In Progress Status in “qtubuntu-media” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Status in “media-hub” package in Ubuntu RTM: In Progress Bug description: Earlier today, a few QA folks tested image krillin rtm 138 plus silo 13, and found that it fixed the unity8 crash from bug 1382595. Silo 13 plus silo 10 landed in image 139. Now, in image 139, unity8 is crashy again. Olli mentioned getting two crashes within a few minutes, and I got a unity8 crash while trying to accept an incoming call. I'm not sure if it's the same crash as before, or if it's a new one. Attached is the crash dump I got just after hitting 'accept' for an incoming call. I tried to pre-process it in apport-cli, but it failed with "Sorry, the program "unity8" closed unexpectedly // Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1387959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380736] Re: showing notification right after boot causes unity8 crash
*** This bug is a duplicate of bug 1387959 *** https://bugs.launchpad.net/bugs/1387959 ** This bug has been marked a duplicate of bug 1387959 [TOPBLOCKER] unity8 crash in image krillin rtm 139 -- 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/1380736 Title: showing notification right after boot causes unity8 crash Status in Network Menu: Invalid Status in “dbus-cpp” package in Ubuntu: Invalid Status in “media-hub” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Status in “qtubuntu-media” package in Ubuntu RTM: Fix Released Bug description: STEPS: 1. Install a new image (Apparently it works with just re-running the wizard) 2. While the dash is empty drag down the network indicator 3. Click on the first unlock sim button 4. Type in the unlock code and hit the tick 5. System locks up EXPECTED: I expect the lock you unlock the sim and change back to the indicator ACTUAL: The system hard locks nothing works. In the end you are forced to hard shutdown the phone by pressing and holding the power button till the phone powers down. Booting the Phone back up after this and everthing works as expected. Also waiting on the dash to fully load and fill with apps and then unlocking works. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1380736/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383357] Re: enabling flight mode shows airplane + 2g icon
Possibly related to bug 1388473? The symptoms seem similar at least. -- 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/1383357 Title: enabling flight mode shows airplane + 2g icon Status in “indicator-network” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Incomplete Status in “indicator-network” source package in Utopic: Confirmed Status in “network-manager” source package in Utopic: Confirmed Status in “indicator-network” source package in Vivid: Confirmed Status in “network-manager” source package in Vivid: Incomplete Status in “indicator-network” package in Ubuntu RTM: Confirmed Bug description: I see this when I toggle the indicator in the indicator-network.logs void core::dbus::Property::handle_changed(const core::dbus::types::Variant&) [with PropertyType = org::freedesktop::URfkill::Interface::Killswitch::Property::State]: org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist There is nothing crashing according to /var/crash Modem seems to be offline: phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems [ /ril_1 ] Features = Manufacturer = Fake Manufacturer Lockdown = 0 Powered = 1 Online = 0 Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime Serial = 354142060406982 Type = hardware Emergency = 0 Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 Model = Fake Modem Model [ org.ofono.CallVolume ] SpeakerVolume = 0 Muted = 0 MicrophoneVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 08 000 999 110 112 911 118 119 [ org.ofono.NetworkTime ] [ /ril_0 ] Features = Manufacturer = Fake Manufacturer Lockdown = 0 Powered = 1 Online = 0 Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime Serial = 354142060126986 Type = hardware Emergency = 0 Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 Model = Fake Modem Model [ org.ofono.CallVolume ] SpeakerVolume = 0 Muted = 0 MicrophoneVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 112 911 [ org.ofono.NetworkTime ] phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/flight-mode flight-mode is: 1 phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/enumerate /org/freedesktop/URfkill/devices/0 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/0 Printing props for Kernel device: /org/freedesktop/URfkill/devices/0 type: 2 hard: 0 index: 0 urftype: org.freedesktop.URfkill.Device.Kernel name: hci0 platform: 0 soft: 1 /org/freedesktop/URfkill/devices/200 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/200 Printing props for Hybris device: /org/freedesktop/URfkill/devices/200 type: 1 index: 200 urftype: org.freedesktop.URfkill.Device.Hybris name: hybris_wifi platform: 0 soft: 1 /org/freedesktop/URfkill/devices/100 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100 Printing props for Ofono device: /org/freedesktop/URfkill/devices/100 type: 5 index: 100 urftype: org.freedesktop.URfkill.Device.Ofono name: Fake Manufacturer Fake Modem Model platform: 0 soft: 1 /org/freedesktop/URfkill/devices/101 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/101 Printing props for Ofono device: /org/freedesktop/URfkill/devices/101 type: 5 index: 101 urftype: org.freedesktop.URfkill.Device.Ofono name: Fake Manufacturer Fake Modem Model platform: 0 soft: 1 phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 117 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-19 08:18:48 version version: 117 version ubuntu: 20141019 version device: 20141015-32e0f27 version custom: 1413412663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1383357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354092] Re: Location service needs internationalization
** Changed in: ubuntu-translations Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1354092 Title: Location service needs internationalization Status in Ubuntu Translations: Fix Released Status in “location-service” package in Ubuntu: Fix Released Bug description: The location dialog is displayed untranslated. Test case. - Switch the phone to Spanish. - Open webbrowser-app. - Go to maps.google.com - Accept to use location in the app. - Dialog appears. Expected result. - The dialog should be displayed in Spanish. Actual result. - The dialog appears untranslated: "unconfined: An unconfined application wants to access your current location. Deny, Allow". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1354092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387708] Re: [TOPBLOCKER] Location services not getting location
Please note that we only managed to reproduce this issue on phones that have been exposed to multiple OTA updates. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387708 Title: [TOPBLOCKER] Location services not getting location Status in Location Service: New Status in “location-service” package in Ubuntu: Confirmed Status in “location-service” package in Ubuntu RTM: Confirmed Status in “location-service” source package in 14.09: Confirmed Bug description: Failing to get location fix from application. Neither network based nor gps location works. Bug has now been seen on 3 phones with and without SIM installed. HERE service seems to be running, but no reasonable location is reported. GPS is failing to get fix, tested with phone placed for 2 hours outside. On two of those phones location was working fine, but with OTA update to ~135 stopped working. hard to guess working image but somewhere around 129~131 Problem is now reproducible on RTM release 137 To manage notifications about this bug go to: https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389516] Re: new camera videos not shown in scope until after reboot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-scope-mediascanner (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1389516 Title: new camera videos not shown in scope until after reboot Status in “unity-scope-mediascanner” package in Ubuntu: Confirmed Bug description: After recording some videos with the camera app, they don't show up in the Videos scope until after a reboot. Performing a search or using pull-to-refresh does not cause them to show up, but rebooting does. Not sure if this is caused by the scope itself or if it's an underlying issue with mediascanner. This was seen in krillin rtm image 142. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1389516/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387754] Re: applicationName ignored in pure QML apps importing Ubuntu.Web
** Changed in: webbrowser-app Status: In Progress => Fix Released -- 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/1387754 Title: applicationName ignored in pure QML apps importing Ubuntu.Web Status in Web Browser App: Fix Released Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: The dataPath for webviews is set in the plugin’s initializeEngine() method, like so: QDir dataLocation(QStandardPaths::writableLocation(QStandardPaths::DataLocation)); engine->rootContext()->setContextProperty("dataLocation", dataLocation.absolutePath()); This works well if the application has a C++ wrapper that sets the application name before loading any QML, but it doesn’t work so well for pure QML applications that import Ubuntu.Web: at the point in time when they import the module, the app name most likely hasn’t been set yet, and as a result the generic name set by qmlscene is used, resulting in a dataPath that looks like "~/.local/share/Qt Project/QtQmlViewer". We don’t want to force applications to ship a thin C++ wrapper just to work around this issue, so we will need to figure out a way to delay the setting of dataLocation until the webview is actually instantiated. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1387754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
I'm getting for example empty music lens with the ~test5 packages. Next up I'm simply trying getting the networkmanager bearer directory from 5.4 git with cherrypicked property cache patch, and use that on top of 5.3.0. There does not seem to be anything preventing that looking at the git logs, and if it just builds it should be a saner way to match all the recent changes. I'll keep also the generic plugin disabling patch, the Reset QNAM patch and the linux_common ofono move related changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351167] Re: Multi-select mode in history view
** Changed in: webbrowser-app Status: In Progress => Fix Released -- 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/1351167 Title: Multi-select mode in history view Status in Ubuntu UX bugs: Fix Committed Status in Web Browser App: Fix Released Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: Per design specification, when in the history view a long press on any domain should activate multi-select mode, where the user can select various domains to delete from the history database. UX: https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g1df4ec952_017 VD: https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354125fb9_0110 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351167/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379766] Re: --fullscreen command-line switch doesn’t work
** Changed in: webbrowser-app Status: In Progress => Fix Released -- 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/1379766 Title: --fullscreen command-line switch doesn’t work Status in Web Browser App: Fix Released Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: Both webbrowser-app and webapp-container advertise a "--fullscreen" command-line switch to allow running applications fullscreen. However this doesn’t work: the window is briefly shown fullscreen, and then restored to its normal state. This is most likely because of this code snippet in webbrowser-app.qml (and its counterpart in webapp- container.qml): visibility: browser.currentWebview && browser.currentWebview.fullscreen ? Window.FullScreen : Window.AutomaticVisibility The value for 'visibility' needs to take into account the --fullscreen command-line switch. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1379766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384460] Re: Delegate unhandled URL schemes to the system
** Branch linked: lp:~osomon/webbrowser-app/rtm-14.09-no-htpp ** Branch linked: lp:~osomon/webbrowser-app/no-htpp ** Changed in: webbrowser-app (Ubuntu RTM) Status: New => Confirmed -- 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/1384460 Title: Delegate unhandled URL schemes to the system Status in Oxide Webview: Fix Released Status in Oxide 1.3 series: Fix Committed Status in “webbrowser-app” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu RTM: Confirmed Bug description: We currently ignore any URL's with a scheme that is unrecognised. We should be delegating these to the system so that it can try to find a handler for it To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1384460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu
The public API between 5.3 and 5.4 has not changed, so using the 5.4 backend code in 5.3 will work. It's how I am testing/developing it. Sorry if this is a mess, the nm backend code was basically never totally finished and untouched for a long time, except for the port to qt5 (which I had nothing to do with), which broke more of it. There are still a few bugs left, but at least it's not totally broken now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: [TOPBLOCKER] QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389357] Re: whoopsie reuses CRASH_DB_IDENTIFIER on next run
This will mean that tests in CI will negligibly skew the results, but I think we can live with that for now. I agree that this is low priority. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1389357 Title: whoopsie reuses CRASH_DB_IDENTIFIER on next run Status in “whoopsie” package in Ubuntu: New Bug description: On Vivid, Ubuntu 15.04, I observed the following behavior. bdmurray@blacklightning:~/Downloads$ sudo stop whoopsie [sudo] password for bdmurray: whoopsie stop/waiting bdmurray@blacklightning:~/Downloads$ sudo CRASH_DB_URL=https://daisy.staging.ubuntu.com CRASH_DB_IDENTIFIER=deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd APPORT_REPORT_DIR=/var/crash/ whoopsie -f [11:07:17] Using lock path: /var/crash/whoopsie_lock [11:07:18] The default IPv4 route is: /org/freedesktop/NetworkManager/ActiveConnection/39 [11:07:18] Not a paid data plan: /org/freedesktop/NetworkManager/ActiveConnection/39 [11:07:18] Found usable connection: /org/freedesktop/NetworkManager/ActiveConnection/39 [11:07:18] online bdmurray@blacklightning:~/Downloads$ sudo cat /var/lib/whoopsie/whoopsie-id deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd bdmurray@blacklightning:~/Downloads$ sudo start whoopsie whoopsie start/running, process 9083 bdmurray@blacklightning:~/Downloads$ sudo cat /var/lib/whoopsie/whoopsie-id deadbeefbd89cc5da1f045978a550ad4b38782c1390ccd8c265c5ddc803be1d8bc0d0d5657350ce06c611975d77dac5a28db5e78921476be5430e0b6c1a44dfd Notice, how the same CRASH_DB_IDENTIFIER was used by whoopsie when starting up, rather than calculating the system identifier. This may lead to crashes being reported under the wrong system-identifier if people switch from setting the environmental variable to just running whoopsie. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1389357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 401823] Re: Gdk-WARNING **: XID collision, trouble ahead
** Changed in: chromium-browser Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/401823 Title: Gdk-WARNING **: XID collision, trouble ahead Status in Chromium Browser: Invalid Status in The Mozilla Firefox Browser: Invalid Status in GTK+ GUI Toolkit: Expired Status in Modular X11 Libraries: Confirmed Status in “firefox” package in Ubuntu: Fix Released Status in “firefox-3.5” package in Ubuntu: Invalid Status in “gtk+2.0” package in Ubuntu: Fix Released Status in “firefox” source package in Lucid: Invalid Status in “firefox-3.5” source package in Lucid: Invalid Status in “gtk+2.0” source package in Lucid: Invalid Status in “firefox” source package in Karmic: Invalid Status in “firefox-3.5” source package in Karmic: Won't Fix Status in “gtk+2.0” source package in Karmic: Fix Released Bug description: karmic testing in .xsession-errors: (firefox:24993): Gdk-WARNING **: XID collision, trouble ahead previously, have had this one: (nautilus:3572): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (bug report 401822) To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/401823/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385630] Re: systemd 215 hangs during boot
SysRQ My keyboard does not apparently have that button. http://www.logitech.com/en-gb/product/illuminated-keyboard-k740 So, at least trying Alt+Print Screen R+E+I+S+U+B does nothing, even after a successful boot. The hang Yes, I now have only this in kernel line: quiet init=/lib/systemd/systemd So, no splash there. And yes, it boots fine without quiet, but much slower, because of the text being printed onto screen. Additional questions 1) Why doesn't my setup boot at all, if I remove the kernel line init=/lib/systemd/systemd ? 2) Why doesn't my setup boot at all, if I use /bin/systemd in the kernel line instead? I do have that link file though. All I get is kernel panic. -- 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/1385630 Title: systemd 215 hangs during boot Status in “systemd” package in Ubuntu: Incomplete Bug description: I just installed (for testing) the newest systemd from Vivid proposed repositories. Yes, that is only a proposed package. The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8). After the installation I found that every now and then booting or rebooting fails. It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing. After each failure the next booting is successful, however. My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu. The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD. This may also be some sort of race situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387959] Re: [TOPBLOCKER] unity8 crash in image krillin rtm 139
** Also affects: qtubuntu-media (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: qtubuntu-media (Ubuntu RTM) Status: New => In Progress ** Changed in: qtubuntu-media (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: qtubuntu-media (Ubuntu RTM) Assignee: (unassigned) => Thomas Voß (thomas-voss) -- 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/1387959 Title: [TOPBLOCKER] unity8 crash in image krillin rtm 139 Status in “media-hub” package in Ubuntu: In Progress Status in “qtubuntu-media” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu: Invalid Status in “media-hub” package in Ubuntu RTM: In Progress Status in “qtubuntu-media” package in Ubuntu RTM: In Progress Bug description: Earlier today, a few QA folks tested image krillin rtm 138 plus silo 13, and found that it fixed the unity8 crash from bug 1382595. Silo 13 plus silo 10 landed in image 139. Now, in image 139, unity8 is crashy again. Olli mentioned getting two crashes within a few minutes, and I got a unity8 crash while trying to accept an incoming call. I'm not sure if it's the same crash as before, or if it's a new one. Attached is the crash dump I got just after hitting 'accept' for an incoming call. I tried to pre-process it in apport-cli, but it failed with "Sorry, the program "unity8" closed unexpectedly // Your computer does not have enough free memory to automatically analyze the problem and send a report to the developers." To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1387959/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 974480] Re: Notification area whitelist is obsolete
@paddy-landau, i'm aware of that ppa but no package for utopic yet. unity version on utopic up to now is 7.3.1+14.10.20141016-0ubuntu1. fyi, the patch on https://github.com/chenxiaolong/Unity-for- Arch/tree/master/unity works :D -- 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/974480 Title: Notification area whitelist is obsolete Status in Ayatana Design: Fix Released Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: Mark has asked us to consider retiring the notification area whitelist for 12.10. The application indicator system has been in place for two years now, which should be long enough for applications to adopt it. If the whitelist was retired, Java and Wine would be hard-coded as the only software still able to use the menu bar as if it was a notification area, because their developers don't necessarily know that Ubuntu even exists. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/974480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389234] Re: Message actions not translated ("Reply", "Call back")
** Also affects: ubuntu-settings-components (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: telephony-service (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: telephony-service (Ubuntu RTM) Importance: Undecided => High ** Changed in: telephony-service Status: New => In Progress ** Changed in: telephony-service Assignee: (unassigned) => Tiago Salem Herrmann (tiagosh) ** Changed in: ubuntu-settings-components (Ubuntu RTM) Importance: Undecided => High -- 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/1389234 Title: Message actions not translated ("Reply", "Call back") Status in Telephony Service: In Progress Status in “ubuntu-settings-components” package in Ubuntu: In Progress Status in “telephony-service” package in Ubuntu RTM: New Status in “ubuntu-settings-components” package in Ubuntu RTM: New Bug description: Message actions appear untranslated. Test case. - Switch the phone to Spanish. - Receive a missing call. - Receive a text message. - Open the messaging indicator. - Click on the missing call message. - Click on the text message. Expected results. - "Reply", "Call back", etc, strings must be displayed translated to Spanish. Actual result. - These strings appear in English. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1389234/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383357] Re: enabling flight mode shows airplane + 2g icon
@kalikiana: yes. it's the same bug. marking as duplicate. Rest assured, it's only UI. ** Summary changed: - enabling flight mode shows airplane + 2g icon + enabling flight mode shows airplane + [2g|3g] icon -- 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/1383357 Title: enabling flight mode shows airplane + [2g|3g] icon Status in “indicator-network” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Incomplete Status in “indicator-network” source package in Utopic: Confirmed Status in “network-manager” source package in Utopic: Confirmed Status in “indicator-network” source package in Vivid: Confirmed Status in “network-manager” source package in Vivid: Incomplete Status in “indicator-network” package in Ubuntu RTM: Confirmed Bug description: I see this when I toggle the indicator in the indicator-network.logs void core::dbus::Property::handle_changed(const core::dbus::types::Variant&) [with PropertyType = org::freedesktop::URfkill::Interface::Killswitch::Property::State]: org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist There is nothing crashing according to /var/crash Modem seems to be offline: phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems [ /ril_1 ] Features = Manufacturer = Fake Manufacturer Lockdown = 0 Powered = 1 Online = 0 Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime Serial = 354142060406982 Type = hardware Emergency = 0 Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 Model = Fake Modem Model [ org.ofono.CallVolume ] SpeakerVolume = 0 Muted = 0 MicrophoneVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 08 000 999 110 112 911 118 119 [ org.ofono.NetworkTime ] [ /ril_0 ] Features = Manufacturer = Fake Manufacturer Lockdown = 0 Powered = 1 Online = 0 Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime Serial = 354142060126986 Type = hardware Emergency = 0 Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 Model = Fake Modem Model [ org.ofono.CallVolume ] SpeakerVolume = 0 Muted = 0 MicrophoneVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 112 911 [ org.ofono.NetworkTime ] phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/flight-mode flight-mode is: 1 phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/enumerate /org/freedesktop/URfkill/devices/0 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/0 Printing props for Kernel device: /org/freedesktop/URfkill/devices/0 type: 2 hard: 0 index: 0 urftype: org.freedesktop.URfkill.Device.Kernel name: hci0 platform: 0 soft: 1 /org/freedesktop/URfkill/devices/200 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/200 Printing props for Hybris device: /org/freedesktop/URfkill/devices/200 type: 1 index: 200 urftype: org.freedesktop.URfkill.Device.Hybris name: hybris_wifi platform: 0 soft: 1 /org/freedesktop/URfkill/devices/100 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100 Printing props for Ofono device: /org/freedesktop/URfkill/devices/100 type: 5 index: 100 urftype: org.freedesktop.URfkill.Device.Ofono name: Fake Manufacturer Fake Modem Model platform: 0 soft: 1 /org/freedesktop/URfkill/devices/101 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/101 Printing props for Ofono device: /org/freedesktop/URfkill/devices/101 type: 5 index: 101 urftype: org.freedesktop.URfkill.Device.Ofono name: Fake Manufacturer Fake Modem Model platform: 0 soft: 1 phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 117 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-19 08:18:48 version version: 117 version ubuntu: 20141019 version device: 20141015-32e0f27 version custom: 1413412663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1383357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299054] Re: resizing loop on high-dpi screen
This does still occurs frequently in Ubuntu 14.10 official release with Unity 7.3.1+14.10.20141016-0ubuntu1. Some application windows freeze and "shrink" slowly for 10-30 seconds while turning the cpu up to 100%. When these windows have reached the smallest possible size, they remain unusable. When trying to resize them to a usable size, they continue freezing and shrinking. -- 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/1299054 Title: resizing loop on high-dpi screen Status in Unity: New Status in “unity” package in Ubuntu: New Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388473] Re: 3G active even though data is disabled
*** This bug is a duplicate of bug 1383357 *** https://bugs.launchpad.net/bugs/1383357 ** This bug has been marked a duplicate of bug 1383357 enabling flight mode shows airplane + 2g icon -- 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/1388473 Title: 3G active even though data is disabled Status in “indicator-network” package in Ubuntu: New Bug description: I have data disabled. Despite that, as soon as wireless is disabled, I see a 3G symbol. Being used to Android I assume that this means that it is in fact using data and potentially draining my credit! Hard to tell if it's "only" a UI difference but in that case it would still mean I have no way to tell which is almost equally problematic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1388473/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379817] Re: When importing 7 digital albums music-app sometimes displays "Imported files not found" when all files have been imported
** Also affects: mediascanner2 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: mediascanner2 (Ubuntu) Importance: Undecided => High ** Changed in: mediascanner2 Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1379817 Title: When importing 7 digital albums music-app sometimes displays "Imported files not found" when all files have been imported Status in Media Scanner v2: Fix Released Status in Music application for Ubuntu devices: Invalid Status in “mediascanner2” package in Ubuntu: Fix Released Status in “mediascanner2” package in Ubuntu RTM: New Bug description: Occasionally music-app displays a message stating "Imported file not found" after importing albums from 7 digital (currently in testing in silo 8, hopefully landing soon). However all the files are present in the ~/Music/Imported directory and are shown in the music app after dismissing the error. The log reports: qml: File(s) were not found ["/home/phablet/Music/Imported/2014/10/10/135211-Anais Mitchell & Rachel Ries - Come September.mp3","/home/phablet/Music/Im ported/2014/10/10/135211-Anais Mitchell & Rachel Ries - Grace the Day.mp3","/home/phablet/Music/Imported/2014/10/10/135211-Anais Mitchell & Rachel Ries - MGD.mp3","/home/phablet/Music/Imported/2014/10/10/135211-Anais Mitchell & Rachel Ries - O My Star.mp3","/home/phablet/Music/Imported/2014/10/10/1352 11-Anais Mitchell & Rachel Ries - When you fall.mp3"] However all the files have log entries prior to that along the lines of: qml: MusicStore model from lookup {"objectName":"","filename":"/home/phablet/Music/Imported/2014/10/10/135211-Anais Mitchell & Rachel Ries - O My Star. mp3","uri":"file:///home/phablet/Music/Imported/2014/10/10/135211-Anais%20Mitchell%20&%20Rachel%20Ries%20-%20O%20My%20Star.mp3","contentType":"audio/mp eg","eTag":"1412952556:0","title":"O My Star","author":"Anais Mitchell & Rachel Ries","album":"Country EP","albumArtist":"Anais Mitchell & Rachel Ries" ,"date":"2008","genre":"Folk/Bluegrass","discNumber":1,"trackNumber":1,"duration":182,"width":0,"height":0,"latitude":0,"longitude":0,"hasThumbnail":tr ue,"art":"image://thumbnailer/file:///home/phablet/Music/Imported/2014/10/10/135211-Anais%20Mitchell%20&%20Rachel%20Ries%20-%20O%20My%20Star.mp3"} So appear to have been processed successfully. To manage notifications about this bug go to: https://bugs.launchpad.net/mediascanner2/+bug/1379817/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389510] Re: SD card and contents listed several times
I can't reproduce this here - are you sure your version of gmtp isn't buggy? I'm on Utopic and running 1.3.7-1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mtp in Ubuntu. https://bugs.launchpad.net/bugs/1389510 Title: SD card and contents listed several times Status in “mtp” package in Ubuntu: New Bug description: When connecting to a krillin running rtm image 142, I see the SD card device listed several times. If I connect to that device and list its contents, each file and directory is listed several times too. The exact number is consistent during a session, but varies per boot. If I then add a new file, disconnect, and reconnect, that file is listed just once while everything else is listed several times. The mtp client I'm using to test this is gmtp. Results may appear different with Nautilus, because I think it ignores duplicates. Screenshots demonstrating what I see are attached. This issue isn't new, but it seems to happen every time now instead of just once in a while. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1389510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389234] Re: Message actions not translated ("Reply", "Call back")
** Branch linked: lp:ubuntu/vivid-proposed/ubuntu-settings-components -- 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/1389234 Title: Message actions not translated ("Reply", "Call back") Status in Telephony Service: In Progress Status in “ubuntu-settings-components” package in Ubuntu: In Progress Status in “telephony-service” package in Ubuntu RTM: New Status in “ubuntu-settings-components” package in Ubuntu RTM: New Bug description: Message actions appear untranslated. Test case. - Switch the phone to Spanish. - Receive a missing call. - Receive a text message. - Open the messaging indicator. - Click on the missing call message. - Click on the text message. Expected results. - "Reply", "Call back", etc, strings must be displayed translated to Spanish. Actual result. - These strings appear in English. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1389234/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383357] Re: enabling flight mode shows airplane + [2g|3g] icon
The reason this is happening is that NetworkManager is not sending the proper signal. In the log we should find a signal sent with value 20. This is not there. If you do 'nmcli nm' when your phone is in this state, it will get fixed (nm reinitializes its state and sends the signal it should have sent earlier). This makes this bug a duplicate of #1386109. However please do NOT mark this bug as a duplicate of that bug. The reason being that if you do, it will vanish from bug searches and people will keep refiling this one again and again. -- 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/1383357 Title: enabling flight mode shows airplane + [2g|3g] icon Status in “indicator-network” package in Ubuntu: Confirmed Status in “network-manager” package in Ubuntu: Incomplete Status in “indicator-network” source package in Utopic: Confirmed Status in “network-manager” source package in Utopic: Confirmed Status in “indicator-network” source package in Vivid: Confirmed Status in “network-manager” source package in Vivid: Incomplete Status in “indicator-network” package in Ubuntu RTM: Confirmed Bug description: I see this when I toggle the indicator in the indicator-network.logs void core::dbus::Property::handle_changed(const core::dbus::types::Variant&) [with PropertyType = org::freedesktop::URfkill::Interface::Killswitch::Property::State]: org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist There is nothing crashing according to /var/crash Modem seems to be offline: phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems [ /ril_1 ] Features = Manufacturer = Fake Manufacturer Lockdown = 0 Powered = 1 Online = 0 Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime Serial = 354142060406982 Type = hardware Emergency = 0 Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 Model = Fake Modem Model [ org.ofono.CallVolume ] SpeakerVolume = 0 Muted = 0 MicrophoneVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 08 000 999 110 112 911 118 119 [ org.ofono.NetworkTime ] [ /ril_0 ] Features = Manufacturer = Fake Manufacturer Lockdown = 0 Powered = 1 Online = 0 Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime Serial = 354142060126986 Type = hardware Emergency = 0 Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 Model = Fake Modem Model [ org.ofono.CallVolume ] SpeakerVolume = 0 Muted = 0 MicrophoneVolume = 0 [ org.ofono.VoiceCallManager ] EmergencyNumbers = 112 911 [ org.ofono.NetworkTime ] phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/flight-mode flight-mode is: 1 phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/enumerate /org/freedesktop/URfkill/devices/0 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/0 Printing props for Kernel device: /org/freedesktop/URfkill/devices/0 type: 2 hard: 0 index: 0 urftype: org.freedesktop.URfkill.Device.Kernel name: hci0 platform: 0 soft: 1 /org/freedesktop/URfkill/devices/200 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/200 Printing props for Hybris device: /org/freedesktop/URfkill/devices/200 type: 1 index: 200 urftype: org.freedesktop.URfkill.Device.Hybris name: hybris_wifi platform: 0 soft: 1 /org/freedesktop/URfkill/devices/100 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100 Printing props for Ofono device: /org/freedesktop/URfkill/devices/100 type: 5 index: 100 urftype: org.freedesktop.URfkill.Device.Ofono name: Fake Manufacturer Fake Modem Model platform: 0 soft: 1 /org/freedesktop/URfkill/devices/101 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/101 Printing props for Ofono device: /org/freedesktop/URfkill/devices/101 type: 5 index: 101 urftype: org.freedesktop.URfkill.Device.Ofono name: Fake Manufacturer Fake Modem Model platform: 0 soft: 1 phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 117 device name: krillin channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2014-10-19 08:18:48 version version: 117 version ubuntu: 20141019 version device: 20141015-32e0f27 version custom: 1413412663 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1383357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpa
[Touch-packages] [Bug 1389234] Re: Message actions not translated ("Reply", "Call back")
This bug was fixed in the package ubuntu-settings-components - 0.4+15.04.20141105-0ubuntu1 --- ubuntu-settings-components (0.4+15.04.20141105-0ubuntu1) vivid; urgency=low [ Sebastien Bacher ] * Get the string translation from telephony-service, that's a workaround but ubuntu-settings-components is not currently setup for translations (LP: #1389234) -- Ubuntu daily releaseWed, 05 Nov 2014 08:45:40 + ** Changed in: ubuntu-settings-components (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings-components in Ubuntu. https://bugs.launchpad.net/bugs/1389234 Title: Message actions not translated ("Reply", "Call back") Status in Telephony Service: In Progress Status in “ubuntu-settings-components” package in Ubuntu: Fix Released Status in “telephony-service” package in Ubuntu RTM: New Status in “ubuntu-settings-components” package in Ubuntu RTM: New Bug description: Message actions appear untranslated. Test case. - Switch the phone to Spanish. - Receive a missing call. - Receive a text message. - Open the messaging indicator. - Click on the missing call message. - Click on the text message. Expected results. - "Reply", "Call back", etc, strings must be displayed translated to Spanish. Actual result. - These strings appear in English. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1389234/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389617] Re: Inconsistant dialogs between camera and gallery
In that one the buttons are yes/no style ** Attachment added: "screenshot of the gallery dialog" https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1389617/+attachment/4253601/+files/gallerydialog.jpg ** Package changed: camera-app (Ubuntu) => camera-app ** Also affects: gallery-app Importance: Undecided Status: New ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1389617 Title: Inconsistant dialogs between camera and gallery Status in Camera App: New Status in Gallery App: New Status in Ubuntu UX bugs: New Bug description: Using rtm 142, camera and gallery have similar photo browsing views, yet their dialogs to delete photos has different label/buttons, it would be nice if those would be the same To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1389617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389617] Re: Inconsistant dialogs between camera and gallery
There the buttons use action labels ** Attachment added: "screenshot of the camera dialog" https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1389617/+attachment/4253599/+files/cameradialog.jpg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1389617 Title: Inconsistant dialogs between camera and gallery Status in Camera App: New Status in Gallery App: New Status in Ubuntu UX bugs: New Bug description: Using rtm 142, camera and gallery have similar photo browsing views, yet their dialogs to delete photos has different label/buttons, it would be nice if those would be the same To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1389617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389617] [NEW] Inconsistant dialogs between camera and gallery
Public bug reported: Using rtm 142, camera and gallery have similar photo browsing views, yet their dialogs to delete photos has different label/buttons, it would be nice if those would be the same ** Affects: camera-app Importance: Undecided Status: New ** Affects: gallery-app Importance: Undecided Status: New ** Affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1389617 Title: Inconsistant dialogs between camera and gallery Status in Camera App: New Status in Gallery App: New Status in Ubuntu UX bugs: New Bug description: Using rtm 142, camera and gallery have similar photo browsing views, yet their dialogs to delete photos has different label/buttons, it would be nice if those would be the same To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1389617/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389622] [NEW] n
Public bug reported: n ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.46 Wed Sep 24 14:23:40 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Nov 5 11:34:09 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 3.13.0-39-generic, x86_64: installed nvidia-340, 340.46, 3.13.0-39-generic, x86_64: installed nvidia-340-uvm, 340.46, 3.13.0-39-generic, x86_64: installed oem-touchpad-alps-synaptics, 0.1: added virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0653] Subsystem: Dell Device [1028:0653] InstallationDate: Installed on 2014-10-31 (4 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Inspiron 3542 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=165c9d39-e014-4a55-8635-516d325d9549 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A03 dmi.board.name: 0WW73H dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0WW73H:rvrA03:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3542 dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.58+git20141006.00847fa4-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.4.0~git20141103.799106d3-0ubuntu0ricotz~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.4.0~git20141103.799106d3-0ubuntu0ricotz~trusty version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.916+git20141101.cc3b8a54-0ubuntu0sarvatt~trusty version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2 xserver.bootTime: Wed Nov 5 11:32:56 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: intel: Failed to load module "dri3" (module does not exist, 0) intel: Failed to load module "present" (module does not exist, 0) NVIDIA(0): Failed to initiate mode change. NVIDIA(0): Failed to complete mode change xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id1110 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1389622 Title: n Status in “xorg” package in Ubuntu: New Bug description: n ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.46 Wed Sep 24 14:23:40 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 Date: Wed Nov 5 11:34:09 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 3.13.0-39-generic, x86_64: installed nvidia-340, 340.46, 3.13.0-39-generic, x86_64: installed nvidia-340-uvm, 340.46, 3.13.0-39-generic, x86_64: installed oem-touchpad-alps-synaptics, 0.1: added virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0653] Subsystem: Dell Device [1028:0653] InstallationDate: Installed on 2014-10-31 (4 days ago) In
[Touch-packages] [Bug 1312917] Re: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/sys/timerfd.h', which is also in package libc6-dev-amd64 2.19-0ub
May be same problem occure to me but with overwriting /gnu/ rude@Marla:/etc/apt/apt.conf.d$ sudo apt-get -f install Reading package lists... Done Building dependency tree Reading state information... Done Correcting dependencies... Done The following extra packages will be installed: libc6-dev-i386 The following NEW packages will be installed libc6-dev-i386 0 to upgrade, 1 to newly install, 0 to remove and 62 not to upgrade. 5 not fully installed or removed. Need to get 0 B/1,148 kB of archives. After this operation, 6,335 kB of additional disk space will be used. Do you want to continue? [Y/n] y (Reading database ... 256685 files and directories currently installed.) Preparing to unpack .../libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb ... Unpacking libc6-dev-i386 (2.19-0ubuntu6.3) ... dpkg: error processing archive /var/cache/apt/archives/libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb (--unpack): trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3 Errors were encountered while processing: /var/cache/apt/archives/libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1312917 Title: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/sys/timerfd.h', which is also in package libc6-dev-amd64 2.19-0ubuntu6, ncurse Status in “eglibc” package in Ubuntu: Confirmed Bug description: I was trying to install ncurse library from synpatic when this error occured. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libc6-dev-i386 (not installed) ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 Date: Fri Apr 25 13:43:53 2014 DuplicateSignature: package:libc6-dev-i386:(not installed):trying to overwrite '/usr/include/sys/timerfd.h', which is also in package libc6-dev-amd64 2.19-0ubuntu6 ErrorMessage: trying to overwrite '/usr/include/sys/timerfd.h', which is also in package libc6-dev-amd64 2.19-0ubuntu6 InstallationDate: Installed on 2014-04-25 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) SourcePackage: eglibc Title: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/sys/timerfd.h', which is also in package libc6-dev-amd64 2.19-0ubuntu6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1312917/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386109] Re: [TOPBLOCKER] com.ubuntu.connectivity1.NetworkingStatus.Status is always online
inheriting priority from bug #1383357 ** Description changed: qdbus com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status always returns "online" on the phone, no matter if i'm connected to wifi or not or in Flight mode or not. + + known duplicate with different end result: bug #1383357 ** Changed in: network-manager (Ubuntu) Importance: Medium => Critical -- 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/1386109 Title: [TOPBLOCKER] com.ubuntu.connectivity1.NetworkingStatus.Status is always online Status in dekko: Confirmed Status in Network Menu: Invalid Status in Libqtelegram - a qt library to access telegram.: Confirmed Status in “network-manager” package in Ubuntu: In Progress Bug description: qdbus com.ubuntu.connectivity1 /com/ubuntu/connectivity1/NetworkingStatus com.ubuntu.connectivity1.NetworkingStatus.Status always returns "online" on the phone, no matter if i'm connected to wifi or not or in Flight mode or not. known duplicate with different end result: bug #1383357 To manage notifications about this bug go to: https://bugs.launchpad.net/dekko/+bug/1386109/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383357] Re: enabling flight mode shows airplane + [2g|3g] icon
yes, so indeed this is a duplicate of bug #1386109, but let's keep this open for making it easier for people to find it and having less duplicates filed. ** Changed in: indicator-network (Ubuntu RTM) Status: Confirmed => Invalid ** Changed in: indicator-network (Ubuntu Utopic) Status: Confirmed => Invalid ** Changed in: indicator-network (Ubuntu Vivid) Status: Confirmed => Invalid ** Changed in: network-manager (Ubuntu Vivid) Importance: Medium => Critical ** Changed in: network-manager (Ubuntu Vivid) Status: Incomplete => Triaged ** Changed in: network-manager (Ubuntu Vivid) Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl) ** Description changed: - I see this when I toggle the indicator in the indicator-network.logs - void core::dbus::Property::handle_changed(const - core::dbus::types::Variant&) [with PropertyType = - org::freedesktop::URfkill::Interface::Killswitch::Property::State]: - org.freedesktop.DBus.Error.UnknownMethod: Method "Get" with signature - "ss" on interface "org.freedesktop.DBus.Properties" doesn't exist + known duplicate with different end result: bug #1386109 - There is nothing crashing according to /var/crash + - - Modem seems to be offline: - phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-modems - [ /ril_1 ] - Features = - Manufacturer = Fake Manufacturer - Lockdown = 0 - Powered = 1 - Online = 0 - Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime - Serial = 354142060406982 - Type = hardware - Emergency = 0 - Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 - Model = Fake Modem Model - [ org.ofono.CallVolume ] - SpeakerVolume = 0 - Muted = 0 - MicrophoneVolume = 0 - [ org.ofono.VoiceCallManager ] - EmergencyNumbers = 08 000 999 110 112 911 118 119 - [ org.ofono.NetworkTime ] - - [ /ril_0 ] - Features = - Manufacturer = Fake Manufacturer - Lockdown = 0 - Powered = 1 - Online = 0 - Interfaces = org.ofono.CallVolume org.ofono.VoiceCallManager org.ofono.NetworkTime - Serial = 354142060126986 - Type = hardware - Emergency = 0 - Revision = MOLY.WR8.W1315.MD.WG.MP.V37.P5, 2014/05/15 11:49 - Model = Fake Modem Model - [ org.ofono.CallVolume ] - SpeakerVolume = 0 - Muted = 0 - MicrophoneVolume = 0 - [ org.ofono.VoiceCallManager ] - EmergencyNumbers = 112 911 - [ org.ofono.NetworkTime ] - - - phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/flight-mode - flight-mode is: 1 - - phablet@ubuntu-phablet:~$ /usr/share/urfkill/scripts/enumerate - /org/freedesktop/URfkill/devices/0 - Printing props for unspecialized device: /org/freedesktop/URfkill/devices/0 - Printing props for Kernel device: /org/freedesktop/URfkill/devices/0 - type: 2 - hard: 0 - index: 0 - urftype: org.freedesktop.URfkill.Device.Kernel - name: hci0 - platform: 0 - soft: 1 - - /org/freedesktop/URfkill/devices/200 - Printing props for unspecialized device: /org/freedesktop/URfkill/devices/200 - Printing props for Hybris device: /org/freedesktop/URfkill/devices/200 - type: 1 - index: 200 - urftype: org.freedesktop.URfkill.Device.Hybris - name: hybris_wifi - platform: 0 - soft: 1 - - /org/freedesktop/URfkill/devices/100 - Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100 - Printing props for Ofono device: /org/freedesktop/URfkill/devices/100 - type: 5 - index: 100 - urftype: org.freedesktop.URfkill.Device.Ofono - name: Fake Manufacturer Fake Modem Model - platform: 0 - soft: 1 - - /org/freedesktop/URfkill/devices/101 - Printing props for unspecialized device: /org/freedesktop/URfkill/devices/101 - Printing props for Ofono device: /org/freedesktop/URfkill/devices/101 - type: 5 - index: 101 - urftype: org.freedesktop.URfkill.Device.Ofono - name: Fake Manufacturer Fake Modem Model - platform: 0 - soft: 1 - - - phablet@ubuntu-phablet:~$ system-image-cli -i - current build number: 117 - device name: krillin - channel: ubuntu-touch/ubuntu-rtm/14.09-proposed - last update: 2014-10-19 08:18:48 - version version: 117 - version ubuntu: 20141019 - version device: 20141015-32e0f27 - version custom: 1413412663 + NM fails to send a proper networking status updated signal. -- 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/1383357 Title: enabling flight mode shows airplane + [2g|3g] icon Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Triaged Status in “indicator-network” source package in Utopic: Invalid Status in “network-manager” source package in Utopic: Confirmed Status in “indicator-network” source package in Vivid: Invalid Status in “network-manager” source package in Vivid: Triaged Status in “in
[Touch-packages] [Bug 1383357] Re: enabling flight mode shows airplane + [2g|3g] icon
** Tags removed: ota-1 ** Tags added: 2014-11-06 -- 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/1383357 Title: enabling flight mode shows airplane + [2g|3g] icon Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Triaged Status in “indicator-network” source package in Utopic: Invalid Status in “network-manager” source package in Utopic: Confirmed Status in “indicator-network” source package in Vivid: Invalid Status in “network-manager” source package in Vivid: Triaged Status in “indicator-network” package in Ubuntu RTM: Invalid Bug description: known duplicate with different end result: bug #1386109 NM fails to send a proper networking status updated signal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1383357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389639] [NEW] Plantroncs Audio 628USB Headset does not function
Public bug reported: Plantronics Audio 628USB Headset mute, hold , volume up o& volume down does not work. It is disply the follwing. How copuld i troubleshoot this problem. $lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 047f:c012 Plantronics, Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 003 Device 002: ID 0461:4e35 Primax Electronics, Ltd Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed Nov 5 14:31:46 2014 DistUpgraded: 2014-11-04 09:15:25,099 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:3397] InstallationDate: Installed on 2014-10-22 (14 days ago) InstallationMedia: Custom Live CD - Release i386 MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=abc345eb-1d60-491c-a74b-bf5165d4084e ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-11-04 (1 days ago) dmi.bios.date: 07/16/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.90 dmi.board.asset.tag: 6CR4126DL0 dmi.board.name: 3397 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 6CR4126DL0 dmi.chassis.type: 4 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr: dmi.product.name: HP Compaq Elite 8300 SFF dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.2 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.2 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Nov 5 14:20:17 2014 xserver.configfile: /etc/X11/xorg.conf xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPixArt USB Optical Mouse MOUSE, id 8 inputCHICONY HP Basic USB Keyboard KEYBOARD, id 9 inputHP WMI hotkeys KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2.1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug compiz-0.9 i386 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1389639 Title: Plantroncs Audio 628USB Headset does not function Status in “xorg” package in Ubuntu: New Bug description: Plantronics Audio 628USB Headset mute, hold , volume up o& volume down does not work. It is disply the follwing. How copuld i troubleshoot this problem. $lsusb Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 047f:c012 Plantronics, Inc. Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 003: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard Bus 003 Device 002: ID 0461
[Touch-packages] [Bug 1351646] Re: SRU: gdb 7.7.1 for trusty
the testsuite results look ok, and the original ARM issue was checked by pitti in https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1233185/comments/17 ** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/1351646 Title: SRU: gdb 7.7.1 for trusty Status in “gdb” package in Ubuntu: Fix Released Status in “gdb” source package in Trusty: Fix Committed Bug description: SRU: gdb 7.7.1 for trusty The SRU supersedes #1328503, building the gdb-doc package now from the gdb source, with the gdb man page in the gdb package, and updates to the 7.7.1 release. 7.7.1 is a bug fix release (https://sourceware.org/gdb/news/), fixing the following issues: PR win32/14018 (pc register not available error on Windows) PR python/16547 (GDB crashing on gdb.python/py-linetable.exp) PR build/16550 (64-bit GDB doesn't build on Solaris) PR gdb/16626 (auto-load regression: gdb uses wrong file to test safeness) PR breakpoints/16292 (GDB oversteps a range in some cases.) PR gdb/16575 (stale breakpoint instructions in the code cache) PR gdb/16696 (AIX 32-bit cores, high section addresses) PR gdb/16721 (Erroneous backtrace on AVR) PR gdb/16832 (Erroneous backtrace on avrxmega architectures) PR build/16873 (GDB 7.7 does not build with GCC 4.9) The gdb package was built in the ubuntu-toolchain-r/ppa PPA, and doesn't show regressions in the gdb testsuite. SRU Justification: [Impact] Some crashes and misbehaviour. [Test Case] Run the gdb testsuite and check that the added testcases pass [Regression Potential] The gdb 7.7.1 was available in 14.10 until replaced by 7.8, and didn't show any issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1351646/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385630] Re: systemd 215 hangs during boot
> 1) Why doesn't my setup boot at all, if I remove the kernel line init=/lib/systemd/systemd ? That's a good question, if you have systemd-sysv installed it should work without it (that's how I boot my system). $ ls -l /sbin/init lrwxrwxrwx 1 root root 20 Nov 3 07:41 /sbin/init -> /lib/systemd/systemd Does that look any different for you? > 2) Why doesn't my setup boot at all, if I use /bin/systemd in the kernel line instead? That should also work indeed, I do that all the time. This was fixed a while ago in utopic: https://launchpad.net/ubuntu/+source/initramfs- tools/0.103ubuntu8. What's your version of initramfs-tools? Also, did you perhaps somehow damage your initramfs? Can you please attach your /boot/grub/grub.cfg ? -- 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/1385630 Title: systemd 215 hangs during boot Status in “systemd” package in Ubuntu: Incomplete Bug description: I just installed (for testing) the newest systemd from Vivid proposed repositories. Yes, that is only a proposed package. The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8). After the installation I found that every now and then booting or rebooting fails. It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing. After each failure the next booting is successful, however. My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu. The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD. This may also be some sort of race situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299054] Re: resizing loop on high-dpi screen
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New => Confirmed -- 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/1299054 Title: resizing loop on high-dpi screen Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299054] Re: resizing loop on high-dpi screen
Oh, and my scaling is set to 1.88, so it's not related to the GTK scaling >= 2 problems. -- 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/1299054 Title: resizing loop on high-dpi screen Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299054] Re: resizing loop on high-dpi screen
I get this every time I click on the "show details" button of the "application has crashed" dialog that pops up when I log in. If you need an example. -- 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/1299054 Title: resizing loop on high-dpi screen Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: When the global scaling factor is set to 2, some dialogs occasionally start changing their window size causing very high CPU activity. This occurs for example in dconf-editor while searching: It appears dconf-editor tries to adjust the window dimensions to the size of the content and reduces the window size until it is unusable. This causes very high CPU activity and freezes the window content. It also happens when (then) resizing the window width (→) or height (↓) afterwards, it tries to revert to the previous window size. However, the only way to resize the window back so that it doesn't reduce its size is by dragging the window corner (↓→). This issue happens also in other applications, for example in apport- dialogs when expanding the collapsed details view. This does not happen when the global scaling factor is set to 1. It could be related to the new window resizing method that updates the window content. org.gnome.desktop.interface.scaling-factor = 2 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140321-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-17.37-generic 3.13.6 Uname: Linux 3.13.0-17-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Fri Mar 28 16:07:47 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-02-02 (53 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1299054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371206] Re: [TOPBLOCKER] [SDK] Text selection - can't drag the handle
Fix is ready but blocked on https://bugs.launchpad.net/ubuntu-ui- toolkit/+bug/1389654 -- 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/1371206 Title: [TOPBLOCKER] [SDK] Text selection - can't drag the handle Status in Ubuntu UI Toolkit: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: When in insert mode, I can't drag the handle in a new position UX Spec https://docs.google.com/a/canonical.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#bookmark=kix.x877v0jqsn42 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1371206/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389659] [NEW] spread should allow dragging windows to other monitor
Public bug reported: It would be a nice feature if in the "Spread" of windows, you can drag windows to other monitor. It would be good for people who need to drag multiple windows to other monitor at a time. ** Affects: unity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1389659 Title: spread should allow dragging windows to other monitor Status in “unity” package in Ubuntu: New Bug description: It would be a nice feature if in the "Spread" of windows, you can drag windows to other monitor. It would be good for people who need to drag multiple windows to other monitor at a time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1389659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389657] [NEW] Libpixman segfaults when searching
Public bug reported: [ 2810.133252] pool[8519]: segfault at bc ip 7f966bdabb71 sp 7f962bfed040 error 4 in libpixman-1.so.0.32.4[7f966bd55000+a3000] Compiz crashed and I saw the above line in the dmesg output. Happens EVERY time I pressed "d" on the ubuntu button for file search (dash, icon on top in the sidebar). Furthermore .xsession-errors has logged this as well: upstart: unity7 main process (1925) killed by SEGV signal upstart: unity7 main process ended, respawning Pretty serious I'd say ... ** Affects: pixman (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pixman in Ubuntu. https://bugs.launchpad.net/bugs/1389657 Title: Libpixman segfaults when searching Status in “pixman” package in Ubuntu: New Bug description: [ 2810.133252] pool[8519]: segfault at bc ip 7f966bdabb71 sp 7f962bfed040 error 4 in libpixman-1.so.0.32.4[7f966bd55000+a3000] Compiz crashed and I saw the above line in the dmesg output. Happens EVERY time I pressed "d" on the ubuntu button for file search (dash, icon on top in the sidebar). Furthermore .xsession-errors has logged this as well: upstart: unity7 main process (1925) killed by SEGV signal upstart: unity7 main process ended, respawning Pretty serious I'd say ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pixman/+bug/1389657/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.
No, it does fit. Only when workspaces are enabled it does not work. Take a look at this screenshot; my screen @ 1024*768: https://www.dropbox.com/s/rcg2z7c3sz7engi/Screenshot%20from%202014-11-05%2013%3A07%3A55.png?dl=0 I tested this in a fresh install of 14.10, same problem. -- 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/1243233 Title: Holding Super key doesn't bring up shortcut overlay. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: After upgrading from 13.04 to 13.10, holding Super no longer brings up the help overlay. Holding Super worked before upgrading. Tapping the Super key still brings up the HUD, and holding it down still brings up the Launcher and after a second or so shows the numbers on the applications. In Compiz Config Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> General, Enable Shortcut Hints Overlay is checked. This is also known to affect 14.04 (without compiz) when workspaces are enabled and screen resolution is 1024x768. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330410] Re: All keyboard types in "Keyboard layout" are not localized during installation
** Attachment added: "config from utopic package" https://bugs.launchpad.net/ubuntukylin/+bug/1330410/+attachment/4253709/+files/config-utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1330410 Title: All keyboard types in "Keyboard layout" are not localized during installation Status in Ubuntu Kylin: Triaged Status in “console-setup” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: New Bug description: 系统:UK 14.10 dailybuild 32 位 6-15 机器型号:vritualbox 现象: 安装过程中键盘布局页面所有的键盘布局类型没有汉化 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1330410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330410] Re: All keyboard types in "Keyboard layout" are not localized during installation
Unlike the trusty package, DEBIAN/config in the utopic package lacks all the translated strings. I rebuilt lp:ubuntu/console-setup in a vivid chroot, and found that the DEBIAN/config file is properly localized. Perhaps there's something wrong during the package build of the utopic package. For reference, I am attaching the DEBIAN/config files of the utopic package and the package I built. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1330410 Title: All keyboard types in "Keyboard layout" are not localized during installation Status in Ubuntu Kylin: Triaged Status in “console-setup” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: New Bug description: 系统:UK 14.10 dailybuild 32 位 6-15 机器型号:vritualbox 现象: 安装过程中键盘布局页面所有的键盘布局类型没有汉化 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1330410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330410] Re: All keyboard types in "Keyboard layout" are not localized during installation
** Attachment added: "config from package I built" https://bugs.launchpad.net/ubuntukylin/+bug/1330410/+attachment/4253712/+files/config-vivid ** Changed in: ubuntukylin Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1330410 Title: All keyboard types in "Keyboard layout" are not localized during installation Status in Ubuntu Kylin: Triaged Status in “console-setup” package in Ubuntu: New Status in “ubiquity” package in Ubuntu: New Bug description: 系统:UK 14.10 dailybuild 32 位 6-15 机器型号:vritualbox 现象: 安装过程中键盘布局页面所有的键盘布局类型没有汉化 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntukylin/+bug/1330410/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.
Like I said, the horizontal size of the overlay does depend on the current language. In Portuguese (my native language), the texts are longer and the overlay doesn't fit (even with workspaces disabled), but in English it fits. I think 1024x768 should be the minimum supported resolution by the overlay (in English, at least). Maybe you should report a new bug (asking the overlay to be made smaller horizontally)? -- 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/1243233 Title: Holding Super key doesn't bring up shortcut overlay. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: After upgrading from 13.04 to 13.10, holding Super no longer brings up the help overlay. Holding Super worked before upgrading. Tapping the Super key still brings up the HUD, and holding it down still brings up the Launcher and after a second or so shows the numbers on the applications. In Compiz Config Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> General, Enable Shortcut Hints Overlay is checked. This is also known to affect 14.04 (without compiz) when workspaces are enabled and screen resolution is 1024x768. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 598308] Re: Volume at login set to Maximum
Sorry for adding a comment to a 'fix released' bug, but, is there a plan for the updated pulseaudio package to get backported to 14.04? I just checked and it's on 1:4.0-0ubuntu11 with nothing in the updates repository. It would be nice to have this fix available for LTS. -- 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/598308 Title: Volume at login set to Maximum Status in “pulseaudio” package in Ubuntu: Fix Released Bug description: Release: Ubuntu 10.04 64-bit Desktop Edition What You Expected to Happen: System volume to remain as set before reboot and as shown in volume panel applet What Happened Instead: After reboot/shutdown at and after login system volume is set to maximum Extended Description: Intel HD Audio Chipset using S/PDIF coax out to speakers and system audio set to digital output After either rebooting or shutting down my system at the next login the system volume will be set to maximum. Once the panel loads I can click on the system volume applet and if I move the volume slider in any direction the volume will immediately be set to the correct level. Here is how the process goes: 1. (logged in system running)slide volume to 75% using system volume applet on panel 2. reboot 3. Login, 4. login soundbite plays at 100% volume 5. open rhythmbox play audio track system volume at 100% 6. click on system volume panel applet, do not click slider, slider shows volume set at 75% as before reboot < This is the odd part 7. click on volume slider and adjust in either direction system volume abruptly adjusts to match the volume level indicated by the slider. If any more information is needed please let me know. Thank you **MORE INFO 6/25/10** This also affects the system alert volume in the same fashion as above. Adjusting the slider for the alert value via the panel applet reset the volume to the correct level. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/598308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1379235] Re: Creates "Phone Calls" and "SMS" entries in indicator-messages on desktop systems
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: telephony-service (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1379235 Title: Creates "Phone Calls" and "SMS" entries in indicator-messages on desktop systems Status in “telephony-service” package in Ubuntu: Confirmed Bug description: telephony-service integrates with indicator-messages even on systems which don't have telephony capabilities, such as desktops (I'm guessing that ubuntu-system-settings caused telephony-service to be ran by D-Bus activation). It shouldn't do this - I now have Phone Calls and SMS on my indicator even though this system can't make those. Perhaps the solution is to gracefully exit if you detect the system doesn't have telephony capabilities, but I don't know if that makes sense given your API, so I would be happy enough if you just avoid registering with indicator-messages in this case. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: telephony-service 0.1+14.10.20140918.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Oct 9 09:55:52 2014 InstallationDate: Installed on 2012-10-07 (731 days ago) InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007) SourcePackage: telephony-service UpgradeStatus: Upgraded to utopic on 2013-05-07 (520 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1379235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389676] [NEW] unity-launcher opens new nautilus instead of bring up existing window
Public bug reported: I have one nautilus window open but in background. I want to get this window back up to top through clicking on the launcher-icon that has the little arrow next to it, indicating, that there is an open window for nautilus somewhere. Then an new nautilus window pops up, starting in my homedir, the old one stays in background. $ lsb_release -rdDescription: Ubuntu 14.10 Release:14.10 $ apt-cache policy unity8 unity8: Installiert: (keine) Installationskandidat: 8.00+14.10.20141013.2-0ubuntu1 Versionstabelle: 8.00+14.10.20141013.2-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Nov 5 13:35:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-25 (375 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-28 (8 days ago) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- 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/1389676 Title: unity-launcher opens new nautilus instead of bring up existing window Status in “unity” package in Ubuntu: New Bug description: I have one nautilus window open but in background. I want to get this window back up to top through clicking on the launcher-icon that has the little arrow next to it, indicating, that there is an open window for nautilus somewhere. Then an new nautilus window pops up, starting in my homedir, the old one stays in background. $ lsb_release -rdDescription: Ubuntu 14.10 Release: 14.10 $ apt-cache policy unity8 unity8: Installiert: (keine) Installationskandidat: 8.00+14.10.20141013.2-0ubuntu1 Versionstabelle: 8.00+14.10.20141013.2-0ubuntu1 0 500 http://de.archive.ubuntu.com/ubuntu/ utopic/universe amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Wed Nov 5 13:35:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-25 (375 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-10-28 (8 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1389676/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.
Yes, please file a new bug about the shortcuts screen not displaying on localized installations due to display size limitations. -- 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/1243233 Title: Holding Super key doesn't bring up shortcut overlay. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: After upgrading from 13.04 to 13.10, holding Super no longer brings up the help overlay. Holding Super worked before upgrading. Tapping the Super key still brings up the HUD, and holding it down still brings up the Launcher and after a second or so shows the numbers on the applications. In Compiz Config Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> General, Enable Shortcut Hints Overlay is checked. This is also known to affect 14.04 (without compiz) when workspaces are enabled and screen resolution is 1024x768. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354092] Re: Location service needs internationalization
Still display untranslated buttons in image rtm-proposed #142. ** Attachment added: "location-service-here.png" https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1354092/+attachment/4253761/+files/location-service-here.png ** Also affects: trust-store (Ubuntu) Importance: Undecided Status: New ** Changed in: trust-store (Ubuntu) Assignee: (unassigned) => Thomas Voß (thomas-voss) ** Changed in: trust-store (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1354092 Title: Location service needs internationalization Status in Ubuntu Translations: Fix Released Status in “location-service” package in Ubuntu: Fix Released Status in “trust-store” package in Ubuntu: New Bug description: The location dialog is displayed untranslated. Test case. - Switch the phone to Spanish. - Open webbrowser-app. - Go to maps.google.com - Accept to use location in the app. - Dialog appears. Expected result. - The dialog should be displayed in Spanish. Actual result. - The dialog appears untranslated: "unconfined: An unconfined application wants to access your current location. Deny, Allow". To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1354092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384289] Re: mesa 10.3.1 required for mir
** Changed in: mesa (Ubuntu Utopic) Assignee: (unassigned) => Maarten Lankhorst (mlankhorst) ** Changed in: mesa (Ubuntu Utopic) Importance: Undecided => Critical ** Changed in: mesa (Ubuntu Utopic) Importance: Critical => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1384289 Title: mesa 10.3.1 required for mir Status in “mesa” package in Ubuntu: Fix Released Status in “mesa” source package in Utopic: New Bug description: There is a bugfix in 10.3.1 that will fix dma-buf handling in i915. So we would like to see the newest minor release of mesa, which is 10.3.1 This will fix: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1275398 and basically enable i915 devices to run mir. [Impact] * The bug leads to crashes in unity8 on i915 and to crashes or 'black buffers' on mir clients. * This is not a request for back porting but a request to pick the next minor bugfix release of mesa. [Test Case] * Install mir-demos on a intel atom netbook or a pentium d system * sudo mir_demo_server_basic --vt 2 --file /tmp/mir_socket * sudo chmod 666 /tmp/mir_socket * mir_demo_client_egltriangle -m /tmp/mir_socket * then vt switch to vt 1 Expected: Animation Observed: Crashing or just showing a black buffer [Regression Potential] * Instead of immediately crashing unity8s desktop session it will make the primary client of unity8: unity8-dash fail to start due to insufficient GL support on the mesa driver - but that is a different error. * 10.3.1 introduces the bespoke i915 bug fix, and further driver local fixes to nouveau for the kepler ir, shutdown leak fixes for radeon and a division by zero fix for llvmpipe. A fix to glsl that first manifested in i965. Apart from that build system cleanups for building mesa for android and detecting LLVM. * the fix to glsl has impact on i965 * fixes for intel are local to i915 and will not cause regression * fixes to radeon should only touch shutdown code * fixes to nouveau should be local to kepler gpus [Other Info] * The switch to this mesa release will not enable mir. But it will not enable unity8 on pentium D and atom, but it will be a step towards that To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1384289/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1358717] Re: nautilus crashed with signal 5 in wl_display_connect()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: wayland (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wayland in Ubuntu. https://bugs.launchpad.net/bugs/1358717 Title: nautilus crashed with signal 5 in wl_display_connect() Status in “wayland” package in Ubuntu: Confirmed Bug description: Nautilus crashes just after login. Autologin and desktop icons are enabled. Manual execution of nautilus is not affected. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: nautilus 1:3.10.1-0ubuntu12 ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1 Uname: Linux 3.16.0-8-generic x86_64 ApportVersion: 2.14.6-0ubuntu1 Architecture: amd64 Date: Sun Aug 17 11:01:07 2014 ExecutablePath: /usr/bin/nautilus GsettingsChanges: InstallationDate: Installed on 2014-08-11 (7 days ago) InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Alpha amd64 (20140811) ProcCmdline: /usr/bin/nautilus Signal: 5 SourcePackage: nautilus StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 wl_display_connect () from /usr/lib/x86_64-linux-gnu/libwayland-client.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gdk_display_manager_open_display () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 gtk_init_check () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 Title: nautilus crashed with signal 5 in wl_display_connect() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wayland/+bug/1358717/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1243233] Re: Holding Super key doesn't bring up shortcut overlay.
@Stephen, it also affects English when workspaces are enabled (and horizontal resolution is 1024). But yes, I think a new bug should be filed (the size problem in other languages could also be mentioned there). -- 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/1243233 Title: Holding Super key doesn't bring up shortcut overlay. Status in Unity: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: After upgrading from 13.04 to 13.10, holding Super no longer brings up the help overlay. Holding Super worked before upgrading. Tapping the Super key still brings up the HUD, and holding it down still brings up the Launcher and after a second or so shows the numbers on the applications. In Compiz Config Manager, under Ubuntu Unity Plugin -> Launcher, the Key to show the Dash, Launcher and Help Overlay is set to Super. Under Ubuntu Unity Plugin -> General, Enable Shortcut Hints Overlay is checked. This is also known to affect 14.04 (without compiz) when workspaces are enabled and screen resolution is 1024x768. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1243233/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389698] [NEW] unity8-dash can't load scopes
Public bug reported: Unity8 on mako rtm #6 won't load any scope installed in the system. Sometimes it stays on the loading screen with the activity indicator spinning, or it may also end up with the white/grey background, but no scopes are loaded. I can't use the phone right now, since I can't launch apps from the app scope. The left panel works, though. This all started after I played a bit with QtCreator because I'm developing a scope for the contest. I don't know exactly which files to attach, meanwhile there's ~/.cache/upstart/scope-register.log. Tell me if you need more information. Thanks in advance for the help, Giulio ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "scope-registry.log" https://bugs.launchpad.net/bugs/1389698/+attachment/4253806/+files/scope-registry.log -- 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/1389698 Title: unity8-dash can't load scopes Status in “unity8” package in Ubuntu: New Bug description: Unity8 on mako rtm #6 won't load any scope installed in the system. Sometimes it stays on the loading screen with the activity indicator spinning, or it may also end up with the white/grey background, but no scopes are loaded. I can't use the phone right now, since I can't launch apps from the app scope. The left panel works, though. This all started after I played a bit with QtCreator because I'm developing a scope for the contest. I don't know exactly which files to attach, meanwhile there's ~/.cache/upstart/scope-register.log. Tell me if you need more information. Thanks in advance for the help, Giulio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385302] Re: Recorded videos don't show up in Videos scope
** Summary changed: - File handles for recorded videos are left open until the camera app exits + Recorded videos don't show up in Videos scope ** Description changed: - This means they don't get detected by mediascanner (which waits for the - file to finish being written) until you close the camera app, and - presumably the operating system just closes all the handles. + File handles for recorded videos are left open until the camera app exits. + This means they don't get detected by mediascanner (which waits for the file to finish being written) until you close the camera app, and presumably the operating system just closes all the handles. The impact is that your recorded videos won't show up anywhere that uses mediascanner (specifically the Videos scope). ** Also affects: unity-scope-mediascanner (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-scope-mediascanner (Ubuntu) Status: New => Invalid ** Also affects: mediascanner2 (Ubuntu) Importance: Undecided Status: New ** Changed in: mediascanner2 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1385302 Title: Recorded videos don't show up in Videos scope Status in Camera App: New Status in libhybris: New Status in “mediascanner2” package in Ubuntu: Invalid Status in “unity-scope-mediascanner” package in Ubuntu: Invalid Bug description: File handles for recorded videos are left open until the camera app exits. This means they don't get detected by mediascanner (which waits for the file to finish being written) until you close the camera app, and presumably the operating system just closes all the handles. The impact is that your recorded videos won't show up anywhere that uses mediascanner (specifically the Videos scope). To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1385302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370146] Re: Adjust header behaviour & UI in multi select mode
** Also affects: address-book-app (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1370146 Title: Adjust header behaviour & UI in multi select mode Status in Address Book App: Confirmed Status in Dialer app for Ubuntu Touch: Confirmed Status in Messaging App: Confirmed Status in Clock application for Ubuntu devices: Fix Released Status in Ubuntu UI Toolkit: Fix Released Status in Ubuntu UX bugs: Fix Released Status in “address-book-app” package in Ubuntu: Confirmed Status in “dialer-app” package in Ubuntu: Confirmed Status in “messaging-app” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Status in “address-book-app” package in Ubuntu RTM: New Bug description: Steps to reproduce: 1. Open Messaging app (or Address Book app, Phone app), make sure you have a list in your messages view 2. Long press on any of the list items Actual Result: 3. Header is changing and shows an X button on the left hand side and two action buttons on the right hand side. Selection checkboxes appear from the left hand side. Expected result - desired solution: - The header should display a BACK button instead of the "X" on the left hand side, same as we have in all other headers - Remove the change in the background colour when a list item is selected, change in the colour of the checkbox is enough - Add labels for all visible actions in this mode in the header, except for 'BACK' - Tapping on the BACK in this mode, cancels the multi-select mode and does NOT navigate back to the previous view - There is no title in this header Please see attached wireframe for reference. This change applies across all apps which use a multi select in their list views. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1370146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388436] Re: ga-z97-d3h motherboard, no sound using line out
*** This bug is a duplicate of bug 1357723 *** https://bugs.launchpad.net/bugs/1357723 ** Bug watch added: Linux Kernel Bug Tracker #87771 http://bugzilla.kernel.org/show_bug.cgi?id=87771 ** Also affects: alsa-driver via http://bugzilla.kernel.org/show_bug.cgi?id=87771 Importance: Unknown Status: Unknown -- 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/1388436 Title: ga-z97-d3h motherboard, no sound using line out Status in ALSA driver: Unknown Status in “alsa-driver” package in Ubuntu: New Bug description: Problems with the sound (chipset z97). I've got the sound in Windows - so it is a software bug. Freshly installed default system. First time this was Kubuntu 14.04 then it was upgraded to 14.10 for a fresh kernel. No effect to the problem. Found the similar problems here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421, but none of the workarounds helped me. Upgrading to the 3.17 kernel dind't help. UPD: It is the same bug as described in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1357723 Please merge them or close this one. Fully confirmed. meklon@meklon-desktop:~$ lsb_release -rd Description:Ubuntu 14.10 Release:14.10 meklon@meklon-desktop:~$ uname -a Linux meklon-desktop 3.16.0-24-generic #32-Ubuntu SMP Tue Oct 28 13:07:32 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Expecting: sound output from the rear panel. What happened: no sound at all. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D3p: meklon 3589 F...m pulseaudio /dev/snd/controlC1: meklon 3589 F pulseaudio /dev/snd/controlC0: meklon 3589 F pulseaudio CurrentDesktop: KDE Date: Sat Nov 1 22:45:33 2014 InstallationDate: Installed on 2014-10-31 (1 days ago) InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed Symptom_Card: Cayman/Antilles HDMI Audio [Radeon HD 6900 Series] - HDA ATI HDMI Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [Z97-D3H, ATI R6xx HDMI, Digital Out, HDMI] Playback problem UpgradeStatus: Upgraded to utopic on 2014-11-01 (0 days ago) dmi.bios.date: 04/25/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-D3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF4:bd04/25/2014:svnGigabyteTechnologyCo.,Ltd.:pnZ97-D3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-D3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z97-D3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1388436/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389705] Re: missing location eula checkbox prompt after second flash
nevermind, i screwed up and accidently thot I was flashing rtm when it was vivid ** Changed in: location-service (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1389705 Title: missing location eula checkbox prompt after second flash Status in “location-service” package in Ubuntu: Invalid Bug description: so i flashed the latest RTM on krillin using --wipe, the device just had vivid installed upon boot i saw the eula prompt for gps in the welcome wizard did some testing, needed to reflash, again to RTM using --wipe this time, there was no prompt in the welcome wizard for the eula I believe after --wipe it should have re-prompted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389698] Re: unity8-dash can't load scopes
Can you please paste the output from the command below, ran on the phone: $ system-image-cli -i Also, if you could please attach ~/.cache/upstart/unity8-dash.log -- 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/1389698 Title: unity8-dash can't load scopes Status in “unity8” package in Ubuntu: New Bug description: Unity8 on mako rtm #6 won't load any scope installed in the system. Sometimes it stays on the loading screen with the activity indicator spinning, or it may also end up with the white/grey background, but no scopes are loaded. I can't use the phone right now, since I can't launch apps from the app scope. The left panel works, though. This all started after I played a bit with QtCreator because I'm developing a scope for the contest. I don't know exactly which files to attach, meanwhile there's ~/.cache/upstart/scope-register.log. Tell me if you need more information. Thanks in advance for the help, Giulio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389705] [NEW] missing location eula checkbox prompt after second flash
Public bug reported: so i flashed the latest RTM on krillin using --wipe, the device just had vivid installed upon boot i saw the eula prompt for gps in the welcome wizard did some testing, needed to reflash, again to RTM using --wipe this time, there was no prompt in the welcome wizard for the eula I believe after --wipe it should have re-prompted ** Affects: location-service (Ubuntu) Importance: Undecided Status: Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1389705 Title: missing location eula checkbox prompt after second flash Status in “location-service” package in Ubuntu: Invalid Bug description: so i flashed the latest RTM on krillin using --wipe, the device just had vivid installed upon boot i saw the eula prompt for gps in the welcome wizard did some testing, needed to reflash, again to RTM using --wipe this time, there was no prompt in the welcome wizard for the eula I believe after --wipe it should have re-prompted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389705/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361221] Re: Manage Dash does not notice when the phone comes online
** Also affects: unity-scope-scopes (Ubuntu RTM) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1361221 Title: Manage Dash does not notice when the phone comes online Status in “unity-scope-scopes” package in Ubuntu: Invalid Status in “unity-scopes-api” package in Ubuntu: In Progress Status in “unity-scopes-shell” package in Ubuntu: In Progress Status in “unity-scope-scopes” package in Ubuntu RTM: New Bug description: Steps: 1. Start the phone with no Internet (i.e. no wireless or 2g/3g/4g) 2. From the Dash, swipe from the bottom to get to Manage Dash 3. Click "All" 4. Note there are no internet based scopes available (which makes sense since you are not online) 5. Click Done to go back to the dash 6. Use the network indicator to get online 7. After getting online, go back to Manage Dash Observed: The online scopes are still hidden Expected: After getting online you can see the online scopes Note that after a reboot and being online, the online scopes are visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-scopes/+bug/1361221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384776] Re: Occasional hang in unity 8 dash on the phone
The patches have been merged upstream. Timo can you have a look at merging them in our packages? ** Also affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu) Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki) ** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1384776 Title: Occasional hang in unity 8 dash on the phone Status in “network-manager” package in Ubuntu: In Progress Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity8” package in Ubuntu: Triaged Bug description: The dash is sometimes hanging on the phone. See the attached backtrace. The issue is as follows: we are maintaining a client-side tree of all NetworkManager devices. When we see that a new device has been added, we query its properties in order to build our local proxy. Doing this means that we are making QtDBus calls from a signal handler. Due to a bug in QtDBus this is not safe. libdbus-1 has a recursive lock on its DBusConnection. When the signal arrives, the lock is acquired and the sginal handler is run. The signal handler can make DBus calls (which also require the lock) because the lock is recursive. QtDBus also has a lock that is always acquired before the libdbus-1 connection lock is acquired. Unfortuntaely, the QtDBus lock is not acquired in the case of the incoming call from DBus -- only the DBus lock is. If another thread tries to do an unrelated DBus call meanwhile, it will acquire the QtDBus lock first and then the DBus lock (which is held because of the signal that arrived). Once the signal handler gets to the point of wanting to make a DBus call (in order to query the properties of the just-added network device) it will attempt to acquire the QtDBus lock. This is a lock-inversion deadlock. There are at least three bugs here: 1) QtDBus should be fixed in order to avoid this sort of lock inversion problem. Even if we fix this one situation, it seems quite likely that issues like this will arise again. 2) QNetworkManager should avoid the issue in QtDBus until such a time as it is fixed. This could be done by dispatching to a worker thread on receipt of signals so that the queries are done in a fresh call stack (without the libdbus-1 lock held). 3) Apparently the only reason we are using NetworkManager at all is in order to know if we are on a 3G connection or not (in order to avoid too much data charges). This would be much easier to do if NetworkManager provided a property that we could watch directly instead of bringing up an entire tree of objects in order to answer a very simple question. To that end I've filed https://bugzilla.gnome.org/show_bug.cgi?id=739080 which we can hopefully get addressed relatively quickly. I consider 3) to be the real fix as far as we are concerned, but we should probably ensure that the Qt people know about 1) and 2). Either of those could function as a workaround for us in the meantime, but the idea that we are creating this complex object tree to answer a simple question is ridiculous, so we should really fix that directly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1384776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367341] Re: proximity sensor blanks screen when dialer is not active app
marked invalid per comment #2 ** Changed in: unity-system-compositor (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1367341 Title: proximity sensor blanks screen when dialer is not active app Status in PowerD: Fix Released Status in Telepathy Ofono: Fix Released Status in “dialer-app” package in Ubuntu: Invalid Status in “unity-system-compositor” package in Ubuntu: Invalid Bug description: Steps: 1. Make a phone call with BT so that you are not holding the phone to hear and talk 2. Push the power button to blank the screen 3. Push the power button again, observe that you are at the welcome screen 4. Wave a finger over the proximity sensor Effect: The screen blanks while finger is over the sensor Expected: The sensor only blanks the screen while the dialer app is being used this is kirllin r23 To manage notifications about this bug go to: https://bugs.launchpad.net/powerd/+bug/1367341/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389698] Re: unity8-dash can't load scopes
$ system-image-cli -i current build number: 6 device name: mako channel: ubuntu-touch/ubuntu-rtm/14.09 last update: 2014-11-04 00:06:16 version version: 6 version ubuntu: 20141031.1 version device: 20141017.2 version custom: mako-1.1 Thanks, Giulio ** Attachment added: "unity8-dash.log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389698/+attachment/4253841/+files/unity8-dash.log -- 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/1389698 Title: unity8-dash can't load scopes Status in “unity8” package in Ubuntu: New Bug description: Unity8 on mako rtm #6 won't load any scope installed in the system. Sometimes it stays on the loading screen with the activity indicator spinning, or it may also end up with the white/grey background, but no scopes are loaded. I can't use the phone right now, since I can't launch apps from the app scope. The left panel works, though. This all started after I played a bit with QtCreator because I'm developing a scope for the contest. I don't know exactly which files to attach, meanwhile there's ~/.cache/upstart/scope-register.log. Tell me if you need more information. Thanks in advance for the help, Giulio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387708] Re: [TOPBLOCKER] Location services not getting location
** Attachment added: "attaching various log files as requested" https://bugs.launchpad.net/location-service/+bug/1387708/+attachment/4253842/+files/location-logs.tar.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387708 Title: [TOPBLOCKER] Location services not getting location Status in Location Service: New Status in “location-service” package in Ubuntu: Confirmed Status in “location-service” package in Ubuntu RTM: Confirmed Status in “location-service” source package in 14.09: Confirmed Bug description: Failing to get location fix from application. Neither network based nor gps location works. Bug has now been seen on 3 phones with and without SIM installed. HERE service seems to be running, but no reasonable location is reported. GPS is failing to get fix, tested with phone placed for 2 hours outside. On two of those phones location was working fine, but with OTA update to ~135 stopped working. hard to guess working image but somewhere around 129~131 Problem is now reproducible on RTM release 137 To manage notifications about this bug go to: https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389718] [NEW] krillin 142 frozen on welcome screen when unlocking
Public bug reported: On a couple of occasions now my krillin has frozen at the partly drawn welcome screen when I press the power button to wake it. The display doesn't update and touching the screen does nothing. Pressing the power button again blanks the screen and wakes again on next press, but the phone is no longer usable. No crash files are made. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 5 13:49:54 2014 InstallationDate: Installed on 2014-11-04 (1 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141104-030206) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: apport-bug armhf utopic ** Attachment added: "device-2014-11-05-134936.png" https://bugs.launchpad.net/bugs/1389718/+attachment/4253848/+files/device-2014-11-05-134936.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/1389718 Title: krillin 142 frozen on welcome screen when unlocking Status in “unity8” package in Ubuntu: Confirmed Bug description: On a couple of occasions now my krillin has frozen at the partly drawn welcome screen when I press the power button to wake it. The display doesn't update and touching the screen does nothing. Pressing the power button again blanks the screen and wakes again on next press, but the phone is no longer usable. No crash files are made. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 5 13:49:54 2014 InstallationDate: Installed on 2014-11-04 (1 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141104-030206) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376644] Re: Some qtpim tests start failing when built against Qt 5.3.2
Renato's analysis was at the end that it works locally, if just the qtpim packages are installed system wide before running the tests. This is a change in behavior from when qtpim was built against Qt 5.3.0, where such a requirement did not exist. This bug should remain open as the core issue should be fixed, but as tests pass locally it could be ok to temporarily disable those additional tests in qtpim. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1376644 Title: Some qtpim tests start failing when built against Qt 5.3.2 Status in “qtpim-opensource-src” package in Ubuntu: New Bug description: Some qtpim tests start failing when built against Qt 5.3.2: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-015/+sourcepub/4451482/+listing- archive-extra We shouldn't be disabling additional tests, so the root causes should be found. All seem to have the following thing in common: "ASSERT failure in QTest::fetchData(): "Test data requested, but no testdata available.", file qtestcase.cpp, line 2047" You can test the Qt 5.3.2 yourself by following the instructions at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtpim-opensource-src/+bug/1376644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389718] Re: krillin 142 frozen on welcome screen when unlocking
To be clear, it's not cpu bound as I can connect over usb and see nothing going on... top - 14:24:54 up 17:00, 2 users, load average: 0.00, 0.01, 0.05 -- 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/1389718 Title: krillin 142 frozen on welcome screen when unlocking Status in “unity8” package in Ubuntu: Confirmed Bug description: On a couple of occasions now my krillin has frozen at the partly drawn welcome screen when I press the power button to wake it. The display doesn't update and touching the screen does nothing. Pressing the power button again blanks the screen and wakes again on next press, but the phone is no longer usable. No crash files are made. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 5 13:49:54 2014 InstallationDate: Installed on 2014-11-04 (1 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141104-030206) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1276186] Re: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu
I also experienced this issue when using the composer in Geary 0.8.1 under 14.10 x64. Disabling IBus worked for me. If someone ever gets assigned to this bug, feel free to contact me for help testing. -- 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/1276186 Title: System becomes unresponsive, ibus-ui-daemon takes ~150 % cpu Status in “ibus” package in Ubuntu: Confirmed Bug description: As stated the graphical desktop became unresponsive. Dropping to CTRL + ALT + F1 terminal and `top`showed ibus-ui-daemon taking around 150 % cpu time and ibus-ui-gtk3 taking around 50 % cpu time. (names may contain minor errors) Tried to kill processes, rebooted. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ibus 1.5.3-6ubuntu2.1 ProcVersionSignature: Ubuntu 3.11.0-15.25-generic 3.11.10 Uname: Linux 3.11.0-15-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 Date: Tue Feb 4 16:41:03 2014 InstallationDate: Installed on 2013-09-10 (147 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: ibus UpgradeStatus: Upgraded to saucy on 2013-10-23 (104 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1276186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389718] Re: krillin 142 frozen on welcome screen when unlocking
i see this since the 130's from time to time but have not reported it yet due to insufficient data ** Changed in: unity8 (Ubuntu) Status: New => Confirmed -- 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/1389718 Title: krillin 142 frozen on welcome screen when unlocking Status in “unity8” package in Ubuntu: Confirmed Bug description: On a couple of occasions now my krillin has frozen at the partly drawn welcome screen when I press the power button to wake it. The display doesn't update and touching the screen does nothing. Pressing the power button again blanks the screen and wakes again on next press, but the phone is no longer usable. No crash files are made. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: unity8 8.01+15.04.20141030~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Wed Nov 5 13:49:54 2014 InstallationDate: Installed on 2014-11-04 (1 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141104-030206) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1218228] Re: Please update to openjpeg-2.0.0
** Also affects: pillow (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openjpeg in Ubuntu. https://bugs.launchpad.net/bugs/1218228 Title: Please update to openjpeg-2.0.0 Status in “darktable” package in Ubuntu: Confirmed Status in “gimp” package in Ubuntu: Confirmed Status in “openjpeg” package in Ubuntu: Confirmed Status in “pillow” package in Ubuntu: New Bug description: openjpeg-2.0.0 is already released in November 2012 (last year) https://code.google.com/p/openjpeg/ Please update ubuntu package to openjpeg-2.0.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/darktable/+bug/1218228/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389715] [NEW] [messaging-app] + [indicators] No message is either sent or stored in the messaging app when replying a message from the ‘quick reply’ on the notifications indicat
Public bug reported: Built: r141 Steps to reproduce: 1. New incoming message. Go to the notifications indicator menu. 2. Tap on the list item to write a quick reply. 3. Send your reply. Actual behaviour: The message I've just sent is not stored in the messageing app, neither received by the contact. Expected behaviour: Messages sent through the 'quick reply' feature on the indicators menu shoud be stored in the messageing app and received by the recipient. ** Affects: indicators-client (Ubuntu) Importance: Undecided Status: New ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New ** Tags: avengers ** Also affects: indicators-client (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1389715 Title: [messaging-app] + [indicators] No message is either sent or stored in the messaging app when replying a message from the ‘quick reply’ on the notifications indicator menu. Status in “indicators-client” package in Ubuntu: New Status in “messaging-app” package in Ubuntu: New Bug description: Built: r141 Steps to reproduce: 1. New incoming message. Go to the notifications indicator menu. 2. Tap on the list item to write a quick reply. 3. Send your reply. Actual behaviour: The message I've just sent is not stored in the messageing app, neither received by the contact. Expected behaviour: Messages sent through the 'quick reply' feature on the indicators menu shoud be stored in the messageing app and received by the recipient. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicators-client/+bug/1389715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342031] Re: Rename QML modules to follow qml-module-foo naming
** Branch linked: lp:~online-accounts/accounts-qml-module/packaging -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1342031 Title: Rename QML modules to follow qml-module-foo naming Status in “accounts-qml-module” package in Ubuntu: New Status in “address-book-app” package in Ubuntu: New Status in “bacon2d” package in Ubuntu: Triaged Status in “clickmanager-plugin” package in Ubuntu: New Status in “content-hub” package in Ubuntu: New Status in “cordova-ubuntu” package in Ubuntu: New Status in “dee-qt” package in Ubuntu: New Status in “gsettings-qt” package in Ubuntu: New Status in “history-service” package in Ubuntu: New Status in “libhud-qt” package in Ubuntu: Won't Fix Status in “libqofono” package in Ubuntu: New Status in “libusermetrics” package in Ubuntu: New Status in “mediascanner2” package in Ubuntu: New Status in “poppler-qml-plugin” package in Ubuntu: New Status in “qml-box2d” package in Ubuntu: New Status in “qml-friends” package in Ubuntu: New Status in “qt3d-opensource-src” package in Ubuntu: New Status in “qtconnectivity-opensource-src” package in Ubuntu: Fix Released Status in “qtdeclarative-opensource-src” package in Ubuntu: Fix Released Status in “qtgrilo” package in Ubuntu: New Status in “qtlocation-opensource-src” package in Ubuntu: New Status in “qtmultimedia-opensource-src” package in Ubuntu: Fix Released Status in “qtpim-opensource-src” package in Ubuntu: Fix Released Status in “qtquickcontrols-opensource-src” package in Ubuntu: Fix Released Status in “qtsensors-opensource-src” package in Ubuntu: Fix Released Status in “qtsystems-opensource-src” package in Ubuntu: Fix Released Status in “reminders-app” package in Ubuntu: New Status in “solid” package in Ubuntu: New Status in “sync-monitor” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: Triaged Status in “thumbnailer” package in Ubuntu: New Status in “u1db-qt” package in Ubuntu: New Status in “ubuntu-download-manager” package in Ubuntu: New Status in “ubuntu-keyboard” package in Ubuntu: New Status in “ubuntu-settings-components” package in Ubuntu: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Fix Released Status in “ubuntu-ui-extras” package in Ubuntu: New Status in “ubuntu-ui-toolkit” package in Ubuntu: New Status in “ubuntuone-credentials” package in Ubuntu: New Status in “unity-action-api” package in Ubuntu: Triaged Status in “unity-notifications” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu: Confirmed Bug description: The package names of QML modules should be of the format qml- module-{$modulename}[version], a transition that was started during Qt 5.3 preparation in Ubuntu. For example this could be qml-module- qtquick-localstorage or qml-module-qtsysteminfo for non versioned modules, and qml-module-ubuntu-webthing0.3 for versioned/co- installable modules. Further details in Debian e-mail: http://lists.alioth.debian.org/pipermail/pkg-kde- talk/2014-March/001889.html For Ubuntu, transitional packages should be put in place for smooth distribution upgrades, since we're shipping with the old names in previous Ubuntus. An example of that is at http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31 - in other words: - Make the old package a transitional oldlibs package that depends on the new package - Add Breaks/Replaces to the new package for the old non-transitional packages (be careful about the version number specification) - Keep Multi-Arch: same and Architecture: any for the transitional package - Write "QML module" instead of "QML plugin" - Rename also the *.install files --- One more example on naming: For example, the "test" (qtdeclarative5-test-plugin) in the old qtdeclarative5-style package naming became "qttest" (qml-module- qttest) in the new naming since the path is actually under /usr/lib/*/qt5/qml/QtTest/ qml-module-qtquick-xmllistmodel has path /usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an example if you have more than one subdir. /usr/lib/*/qt5/qml/Ubuntu/Connectivity/ would be qml-module-ubuntu-connectivity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accounts-qml-module/+bug/1342031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389721] [NEW] API versioning broken in some cases
Public bug reported: With Oxide 1.2 being the version that's shipping in the RTM image, I want to start correctly versioning new API's so that we can upgrade Oxide OTA safely without breaking existing applications. I'm testing the attached patch for Oxide to add a revision to API's that were added in 1.3, but running the test suite results in the following failure: Output: -- file:///home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11:11: ".allowedExtraUrlSchemes" is not available due to component versioning. context.allowedExtraUrlSchemes: [ "test", "bar" ] ^ * Start testing of qml-core-test * Config: Using QtTest library 5.3.0, Qt 5.3.0 QWARN : qml-core-test::tst_CustomURLSchemes::compile() /home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml produced 1 error(s): /home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11,11: ".allowedExtraUrlSchemes" is not available due to component versioning. Working directory: /home/chr1s/src/oxide/oxide/objdir/qt/tests/qmltests View: QQuickView, import paths: '/home/chr1s/src/oxide/oxide/objdir/out/bin' '/home/chr1s/src/oxide/oxide/objdir/out/imports' '/usr/lib/x86_64-linux-gnu/qt5/qml' Plugin paths: '.' FAIL! : qml-core-test::tst_CustomURLSchemes::compile() ".allowedExtraUrlSchemes" is not available due to component versioning. Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml(11)] After scratching my head for a while, I can't see what I'm doing wrong here. If I run the following simple QML app, I can access the property correctly: - test.qml: import QtQuick 2.0 import com.canonical.Oxide 1.3 WebView { focus: true width: 960 height: 540 url: "https://www.google.com"; context: WebContext { allowedExtraUrlSchemes: [] } } However, if I run this simple app instead, then it fails with the same message I see in the unit tests: - test.qml: import QtQuick 2.0 import com.canonical.Oxide 1.3 TestWebView { focus: true width: 960 height: 540 url: "https://www.google.com"; context.allowedExtraUrlSchemes: [] } - TestWebView.qml import QtQuick 2.0 import com.canonical.Oxide 1.3 WebView { context: WebContext {} } I consider this to be a blocker for being able to update Oxide OTA, as we're not able to version new API's with this bug ** Affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Oxide patch to version new API's in 1.3" https://bugs.launchpad.net/bugs/1389721/+attachment/4253859/+files/diff -- 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/1389721 Title: API versioning broken in some cases Status in “qtdeclarative-opensource-src” package in Ubuntu: New Bug description: With Oxide 1.2 being the version that's shipping in the RTM image, I want to start correctly versioning new API's so that we can upgrade Oxide OTA safely without breaking existing applications. I'm testing the attached patch for Oxide to add a revision to API's that were added in 1.3, but running the test suite results in the following failure: Output: -- file:///home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11:11: ".allowedExtraUrlSchemes" is not available due to component versioning. context.allowedExtraUrlSchemes: [ "test", "bar" ] ^ * Start testing of qml-core-test * Config: Using QtTest library 5.3.0, Qt 5.3.0 QWARN : qml-core-test::tst_CustomURLSchemes::compile() /home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml produced 1 error(s): /home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11,11: ".allowedExtraUrlSchemes" is not available due to component versioning. Working directory: /home/chr1s/src/oxide/oxide/objdir/qt/tests/qmltests View: QQuickView, import paths: '/home/chr1s/src/oxide/oxide/objdir/out/bin' '/home/chr1s/src/oxide/oxide/objdir/out/imports' '/usr/lib/x86_64-linux-gnu/qt5/qml' Plugin paths: '.' FAIL! : qml-core-test::tst_CustomURLSchemes::compile() ".allowedExtraUrlSchemes" is not available due to component versioning. Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml(11)] After scratching my head for a while, I can't see what I'm doing wrong here. If I run the following simple QML app, I can access the property correctly: - test.qml: import QtQuick 2.0 import com.canonical.Oxide 1.3 WebView { focus: true width: 960 height: 540 url: "https://www.google.com"; conte
[Touch-packages] [Bug 1389721] Re: API versioning broken in some cases
This sounds similar to https://bugreports.qt- project.org/browse/QTBUG-40043 ** Description changed: With Oxide 1.2 being the version that's shipping in the RTM image, I want to start correctly versioning new API's so that we can upgrade Oxide OTA safely without breaking existing applications. I'm testing the attached patch for Oxide to add a revision to API's that were added in 1.3, but running the test suite results in the following failure: Output: -- - file:///home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11:11: ".allowedExtraUrlSchemes" is not available due to component versioning. -context.allowedExtraUrlSchemes: [ "test", "bar" ] -^ + file:///home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11:11: ".allowedExtraUrlSchemes" is not available due to component versioning. + context.allowedExtraUrlSchemes: [ "test", "bar" ] + ^ * Start testing of qml-core-test * Config: Using QtTest library 5.3.0, Qt 5.3.0 - QWARN : qml-core-test::tst_CustomURLSchemes::compile() - /home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml produced 1 error(s): - /home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11,11: ".allowedExtraUrlSchemes" is not available due to component versioning. - Working directory: /home/chr1s/src/oxide/oxide/objdir/qt/tests/qmltests - View: QQuickView, import paths: - '/home/chr1s/src/oxide/oxide/objdir/out/bin' - '/home/chr1s/src/oxide/oxide/objdir/out/imports' - '/usr/lib/x86_64-linux-gnu/qt5/qml' - Plugin paths: - '.' + QWARN : qml-core-test::tst_CustomURLSchemes::compile() + /home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml produced 1 error(s): + /home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11,11: ".allowedExtraUrlSchemes" is not available due to component versioning. + Working directory: /home/chr1s/src/oxide/oxide/objdir/qt/tests/qmltests + View: QQuickView, import paths: + '/home/chr1s/src/oxide/oxide/objdir/out/bin' + '/home/chr1s/src/oxide/oxide/objdir/out/imports' + '/usr/lib/x86_64-linux-gnu/qt5/qml' + Plugin paths: + '.' FAIL! : qml-core-test::tst_CustomURLSchemes::compile() ".allowedExtraUrlSchemes" is not available due to component versioning. -Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml(11)] + Loc: [/home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml(11)] After scratching my head for a while, I can't see what I'm doing wrong here. If I run the following simple QML app, I can access the property correctly: - test.qml: import QtQuick 2.0 import com.canonical.Oxide 1.3 WebView { - focus: true - width: 960 - height: 540 + focus: true + width: 960 + height: 540 - url: "https://www.google.com"; + url: "https://www.google.com"; - context: WebContext { - allowedExtraUrlSchemes: [] - } + context: WebContext { + allowedExtraUrlSchemes: [] + } } However, if I run this simple app instead, then it fails with the same message I see in the unit tests: - test.qml: import QtQuick 2.0 import com.canonical.Oxide 1.3 TestWebView { - focus: true - width: 960 - height: 540 + focus: true + width: 960 + height: 540 - url: "https://www.google.com"; + url: "https://www.google.com"; - context.allowedExtraUrlSchemes: [] + context.allowedExtraUrlSchemes: [] } - TestWebView.qml import QtQuick 2.0 import com.canonical.Oxide 1.3 WebView { - context: WebContext {} + context: WebContext {} } + + I consider this to be a blocker for being able to update Oxide OTA, as + we're not able to version new API's with this bug -- 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/1389721 Title: API versioning broken in some cases Status in “qtdeclarative-opensource-src” package in Ubuntu: New Bug description: With Oxide 1.2 being the version that's shipping in the RTM image, I want to start correctly versioning new API's so that we can upgrade Oxide OTA safely without breaking existing applications. I'm testing the attached patch for Oxide to add a revision to API's that were added in 1.3, but running the test suite results in the following failure: Output: -- file:///home/chr1s/src/oxide/oxide/qt/tests/qmltests/core/tst_CustomURLSchemes.qml:11:11: ".allowedExtraUrlSchemes" is not available due to component versioning. context.allowedExtraUrlSchemes: [ "test", "bar" ] ^ * Start testing o
[Touch-packages] [Bug 1389725] [NEW] g_app_info warning on start (utouch)
Public bug reported: Using rtm 143, indicator-messages displays warnings on start backtrace of one of those #0 g_log (log_domain=0xb6f87914 "GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=0xb6e247d4 "%s: assertion '%s' failed") at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1075 #1 0xb6dedd62 in g_return_if_fail_warning (log_domain=, pretty_function=, expression=) at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1088 #2 0xb6ef610c in g_app_info_equal (appinfo1=0x4e088, appinfo2=0x0) at /build/buildd/glib2.0-2.41.5/./gio/gappinfo.c:132 #3 0x000170d2 in g_app_info_is_default_for_uri_scheme ( uri_scheme=0x1d63c "mailto", info=0x4e088) at im-desktop-menu.c:87 #4 im_desktop_menu_app_added (applist=, app_id=0x50b80 "telephony-service-call", app_info=0x4e088, user_data=0x3fe40) at im-desktop-menu.c:176 #5 0x000173ee in im_desktop_menu_constructed (object=0x3fe40) at im-desktop-menu.c:380 #6 0xb6e96fae in g_object_new_internal (class=class@entry=0x0, params=params@entry=0xbefff354, n_params=n_params@entry=1) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1814 #7 0xb6e98650 in g_object_new_valist (object_type=object_type@entry=346680, first_property_name=first_property_name@entry=0x1d054 "application-list", var_args=..., var_args@entry=...) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:2034 #8 0xb6e987ec in g_object_new (object_type=346680, first_property_name=0x1d054 "application-list") at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1617 #9 0x00017510 in im_desktop_menu_new (applist=) at im-desktop-menu.c:427 #10 0x00014d16 in main (argc=, argv=) at messages-service.c:277 ** Affects: indicator-messages (Ubuntu) Importance: Low Assignee: Lars Uebernickel (larsu) Status: New ** Changed in: indicator-messages (Ubuntu) Importance: Undecided => Low ** Changed in: indicator-messages (Ubuntu) Assignee: (unassigned) => Lars Uebernickel (larsu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1389725 Title: g_app_info warning on start (utouch) Status in “indicator-messages” package in Ubuntu: New Bug description: Using rtm 143, indicator-messages displays warnings on start backtrace of one of those #0 g_log (log_domain=0xb6f87914 "GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=0xb6e247d4 "%s: assertion '%s' failed") at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1075 #1 0xb6dedd62 in g_return_if_fail_warning (log_domain=, pretty_function=, expression=) at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1088 #2 0xb6ef610c in g_app_info_equal (appinfo1=0x4e088, appinfo2=0x0) at /build/buildd/glib2.0-2.41.5/./gio/gappinfo.c:132 #3 0x000170d2 in g_app_info_is_default_for_uri_scheme ( uri_scheme=0x1d63c "mailto", info=0x4e088) at im-desktop-menu.c:87 #4 im_desktop_menu_app_added (applist=, app_id=0x50b80 "telephony-service-call", app_info=0x4e088, user_data=0x3fe40) at im-desktop-menu.c:176 #5 0x000173ee in im_desktop_menu_constructed (object=0x3fe40) at im-desktop-menu.c:380 #6 0xb6e96fae in g_object_new_internal (class=class@entry=0x0, params=params@entry=0xbefff354, n_params=n_params@entry=1) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1814 #7 0xb6e98650 in g_object_new_valist (object_type=object_type@entry=346680, first_property_name=first_property_name@entry=0x1d054 "application-list", var_args=..., var_args@entry=...) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:2034 #8 0xb6e987ec in g_object_new (object_type=346680, first_property_name=0x1d054 "application-list") at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1617 #9 0x00017510 in im_desktop_menu_new (applist=) at im-desktop-menu.c:427 #10 0x00014d16 in main (argc=, argv=) at messages-service.c:277 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1389725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384460] Re: Delegate unhandled URL schemes to the system
** Tags removed: touch-2014-10-30 ** Tags added: ota-1 -- 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/1384460 Title: Delegate unhandled URL schemes to the system Status in Oxide Webview: Fix Released Status in Oxide 1.3 series: Fix Committed Status in “webbrowser-app” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu RTM: Confirmed Bug description: We currently ignore any URL's with a scheme that is unrecognised. We should be delegating these to the system so that it can try to find a handler for it To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1384460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389725] Re: g_app_info warning on start (utouch)
other warning following, likely the same issue #1 0xb6dedd62 in g_return_if_fail_warning (log_domain=, pretty_function=, expression=) at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1088 #2 0x000170dc in g_app_info_is_default_for_uri_scheme ( uri_scheme=0x1d63c "mailto", info=) at im-desktop-menu.c:89 #3 im_desktop_menu_app_added (applist=, app_id=0x4daa8 "telephony-service-call", app_info=0x4b088, user_data=0x3fe40) at im-desktop-menu.c:176 #4 0x000173ee in im_desktop_menu_constructed (object=0x3fe40) at im-desktop-menu.c:380 #5 0xb6e96fae in g_object_new_internal (class=class@entry=0x0, params=params@entry=0xbefff354, n_params=n_params@entry=1) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1814 #6 0xb6e98650 in g_object_new_valist (object_type=object_type@entry=348264, first_property_name=first_property_name@entry=0x1d054 "application-list", var_args=..., var_args@entry=...) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:2034 #7 0xb6e987ec in g_object_new (object_type=348264, first_property_name=0x1d054 "application-list") at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1617 #8 0x00017510 in im_desktop_menu_new (applist=) at im-desktop-menu.c:427 #9 0x00014d16 in main (argc=, argv=) at messages-service.c:277 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1389725 Title: g_app_info warning on start (utouch) Status in “indicator-messages” package in Ubuntu: New Bug description: Using rtm 143, indicator-messages displays warnings on start backtrace of one of those #0 g_log (log_domain=0xb6f87914 "GLib-GIO", log_level=log_level@entry=G_LOG_LEVEL_CRITICAL, format=0xb6e247d4 "%s: assertion '%s' failed") at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1075 #1 0xb6dedd62 in g_return_if_fail_warning (log_domain=, pretty_function=, expression=) at /build/buildd/glib2.0-2.41.5/./glib/gmessages.c:1088 #2 0xb6ef610c in g_app_info_equal (appinfo1=0x4e088, appinfo2=0x0) at /build/buildd/glib2.0-2.41.5/./gio/gappinfo.c:132 #3 0x000170d2 in g_app_info_is_default_for_uri_scheme ( uri_scheme=0x1d63c "mailto", info=0x4e088) at im-desktop-menu.c:87 #4 im_desktop_menu_app_added (applist=, app_id=0x50b80 "telephony-service-call", app_info=0x4e088, user_data=0x3fe40) at im-desktop-menu.c:176 #5 0x000173ee in im_desktop_menu_constructed (object=0x3fe40) at im-desktop-menu.c:380 #6 0xb6e96fae in g_object_new_internal (class=class@entry=0x0, params=params@entry=0xbefff354, n_params=n_params@entry=1) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1814 #7 0xb6e98650 in g_object_new_valist (object_type=object_type@entry=346680, first_property_name=first_property_name@entry=0x1d054 "application-list", var_args=..., var_args@entry=...) at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:2034 #8 0xb6e987ec in g_object_new (object_type=346680, first_property_name=0x1d054 "application-list") at /build/buildd/glib2.0-2.41.5/./gobject/gobject.c:1617 #9 0x00017510 in im_desktop_menu_new (applist=) at im-desktop-menu.c:427 #10 0x00014d16 in main (argc=, argv=) at messages-service.c:277 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1389725/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342031] Re: Rename QML modules to follow qml-module-foo naming
** Changed in: accounts-qml-module (Ubuntu) Status: New => In Progress ** Changed in: accounts-qml-module (Ubuntu) Assignee: (unassigned) => Alberto Mardegan (mardy) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1342031 Title: Rename QML modules to follow qml-module-foo naming Status in “accounts-qml-module” package in Ubuntu: In Progress Status in “address-book-app” package in Ubuntu: New Status in “bacon2d” package in Ubuntu: Triaged Status in “clickmanager-plugin” package in Ubuntu: New Status in “content-hub” package in Ubuntu: New Status in “cordova-ubuntu” package in Ubuntu: New Status in “dee-qt” package in Ubuntu: New Status in “gsettings-qt” package in Ubuntu: New Status in “history-service” package in Ubuntu: New Status in “libhud-qt” package in Ubuntu: Won't Fix Status in “libqofono” package in Ubuntu: New Status in “libusermetrics” package in Ubuntu: New Status in “mediascanner2” package in Ubuntu: New Status in “poppler-qml-plugin” package in Ubuntu: New Status in “qml-box2d” package in Ubuntu: New Status in “qml-friends” package in Ubuntu: New Status in “qt3d-opensource-src” package in Ubuntu: New Status in “qtconnectivity-opensource-src” package in Ubuntu: Fix Released Status in “qtdeclarative-opensource-src” package in Ubuntu: Fix Released Status in “qtgrilo” package in Ubuntu: New Status in “qtlocation-opensource-src” package in Ubuntu: New Status in “qtmultimedia-opensource-src” package in Ubuntu: Fix Released Status in “qtpim-opensource-src” package in Ubuntu: Fix Released Status in “qtquickcontrols-opensource-src” package in Ubuntu: Fix Released Status in “qtsensors-opensource-src” package in Ubuntu: Fix Released Status in “qtsystems-opensource-src” package in Ubuntu: Fix Released Status in “reminders-app” package in Ubuntu: New Status in “solid” package in Ubuntu: New Status in “sync-monitor” package in Ubuntu: New Status in “telephony-service” package in Ubuntu: Triaged Status in “thumbnailer” package in Ubuntu: New Status in “u1db-qt” package in Ubuntu: New Status in “ubuntu-download-manager” package in Ubuntu: New Status in “ubuntu-keyboard” package in Ubuntu: New Status in “ubuntu-settings-components” package in Ubuntu: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Fix Released Status in “ubuntu-ui-extras” package in Ubuntu: New Status in “ubuntu-ui-toolkit” package in Ubuntu: New Status in “ubuntuone-credentials” package in Ubuntu: New Status in “unity-action-api” package in Ubuntu: Triaged Status in “unity-notifications” package in Ubuntu: New Status in “webbrowser-app” package in Ubuntu: Confirmed Bug description: The package names of QML modules should be of the format qml- module-{$modulename}[version], a transition that was started during Qt 5.3 preparation in Ubuntu. For example this could be qml-module- qtquick-localstorage or qml-module-qtsysteminfo for non versioned modules, and qml-module-ubuntu-webthing0.3 for versioned/co- installable modules. Further details in Debian e-mail: http://lists.alioth.debian.org/pipermail/pkg-kde- talk/2014-March/001889.html For Ubuntu, transitional packages should be put in place for smooth distribution upgrades, since we're shipping with the old names in previous Ubuntus. An example of that is at http://bazaar.launchpad.net/~kubuntu-packagers/kubuntu-packaging/qtsystems-opensource-src/revision/31 - in other words: - Make the old package a transitional oldlibs package that depends on the new package - Add Breaks/Replaces to the new package for the old non-transitional packages (be careful about the version number specification) - Keep Multi-Arch: same and Architecture: any for the transitional package - Write "QML module" instead of "QML plugin" - Rename also the *.install files --- One more example on naming: For example, the "test" (qtdeclarative5-test-plugin) in the old qtdeclarative5-style package naming became "qttest" (qml-module- qttest) in the new naming since the path is actually under /usr/lib/*/qt5/qml/QtTest/ qml-module-qtquick-xmllistmodel has path /usr/lib/*/qt5/qml/QtQuick/XmlListModel, as an example if you have more than one subdir. /usr/lib/*/qt5/qml/Ubuntu/Connectivity/ would be qml-module-ubuntu-connectivity. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accounts-qml-module/+bug/1342031/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270245] Re: Backward frame jumps on mali (Nexus 10 & krillin)
Not much info in the kernel log but here it is. ** Attachment added: "kernel.log" https://bugs.launchpad.net/mir/+bug/1270245/+attachment/4253871/+files/kernel.log -- 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/1270245 Title: Backward frame jumps on mali (Nexus 10 & krillin) Status in Mir: Confirmed Status in “mir” package in Ubuntu: Confirmed Bug description: Alexandros, Andreas, and I have noted at different points that we see frame skips on the nexus 10. The frames look like they move in a 1,3,2 pattern, particularly when unlocking the device. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1270245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270245] Re: Backward frame jumps on mali (Nexus 10 & krillin)
Logcat log for krillin ** Attachment added: "logcat.log" https://bugs.launchpad.net/mir/+bug/1270245/+attachment/4253872/+files/logcat.log -- 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/1270245 Title: Backward frame jumps on mali (Nexus 10 & krillin) Status in Mir: Confirmed Status in “mir” package in Ubuntu: Confirmed Bug description: Alexandros, Andreas, and I have noted at different points that we see frame skips on the nexus 10. The frames look like they move in a 1,3,2 pattern, particularly when unlocking the device. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1270245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389727] [NEW] Can't run any application using PositionSource on desktop
Public bug reported: Using this example code: import QtQuick 2.2 import QtPositioning 5.1 Item { height: 500; width: 500 PositionSource {} } -- crashes when started on desktop with the message: Ubuntu Platform API: Unable to find module configuration file -- Aborting Aborted (core dumped) This affects all phone applications using Positioning. They can't be tested on the desktop atm. ** Affects: location-service (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1389727 Title: Can't run any application using PositionSource on desktop Status in “location-service” package in Ubuntu: New Bug description: Using this example code: import QtQuick 2.2 import QtPositioning 5.1 Item { height: 500; width: 500 PositionSource {} } -- crashes when started on desktop with the message: Ubuntu Platform API: Unable to find module configuration file -- Aborting Aborted (core dumped) This affects all phone applications using Positioning. They can't be tested on the desktop atm. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1389727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384460] Re: Delegate unhandled URL schemes to the system
marking ota, this will release mid nov -- 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/1384460 Title: Delegate unhandled URL schemes to the system Status in Oxide Webview: Fix Released Status in Oxide 1.3 series: Fix Committed Status in “webbrowser-app” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu RTM: Confirmed Bug description: We currently ignore any URL's with a scheme that is unrecognised. We should be delegating these to the system so that it can try to find a handler for it To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1384460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389730] [NEW] [call] audible feedback after ended call not working in silent mode
Public bug reported: This bug is related to this one https://bugs.launchpad.net/ubuntu- ux/+bug/1372973 which is marked as "fixed-released". The issue is that the beep tone doesn't happen when the phone is in silent mode. Build: r143 Steps to reproduce: 1. switch your device on loud/turn up the sound 2. call your device and hand up the phone you called from 3. you hear a beep when the call is ended 4. now put your device on silent 5. call your device again and hang up Expected result: you hear the beep Actual result: not a sound The beep sound should be played in whatever output the call is performed, internal, speaker, headphones, etc. If user switches the output lets say from speaker to internal, the sound should follow. ** Affects: telephony-service Importance: Undecided Status: New ** Affects: ubuntu-ux Importance: High Assignee: Olga Kemmet (olga-kemmet) Status: Triaged ** Affects: powerd (Ubuntu) Importance: Undecided Status: New ** Tags: rtm14 ** Also affects: telephony-service Importance: Undecided Status: New ** Also affects: powerd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1389730 Title: [call] audible feedback after ended call not working in silent mode Status in Telephony Service: New Status in Ubuntu UX bugs: Triaged Status in “powerd” package in Ubuntu: New Bug description: This bug is related to this one https://bugs.launchpad.net/ubuntu- ux/+bug/1372973 which is marked as "fixed-released". The issue is that the beep tone doesn't happen when the phone is in silent mode. Build: r143 Steps to reproduce: 1. switch your device on loud/turn up the sound 2. call your device and hand up the phone you called from 3. you hear a beep when the call is ended 4. now put your device on silent 5. call your device again and hang up Expected result: you hear the beep Actual result: not a sound The beep sound should be played in whatever output the call is performed, internal, speaker, headphones, etc. If user switches the output lets say from speaker to internal, the sound should follow. To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1389730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1057834]
Created attachment 108963 detailed interface description -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1057834 Title: Haier CE81B is not detected on 12.04 Status in ModemManager (with NetworkManager support): In Progress Status in “modemmanager” package in Ubuntu: Triaged Bug description: I have reported this bug under https://bugzilla.gnome.org/show_bug.cgi?id=685011 However, I'm not sure to report only to gnome people. I hope this problem will be fixed on upcoming 12.10. Problem: Modem Haier CE81B EVDO is not working. ModemManager failed to scan the right TTYUSB. Solution: 1. Add udev blacklist for modem manager rule (attached) 2. Type command: sudo modprobe usbserial vendor=0x201e product=0x10f8 To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1057834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389732] [NEW] The computer freeze randomly
Public bug reported: The freeze problem actually started when I was using 12.04 LTS. Every time when I was login to the desktop (after the computer is completely shut down) , the screen glitches and freezes. However, when I restart the computer, the problem went away. Everything is normal again. This happened in every desktop environment that I have used (Gnome, Unity, Xfce). The problem getting worst after few days where I need to restart the computer twice (sometime 3 times) in order to make the system calm down. So, I think it was the driver problem, and I changed the VGA driver to its propriety Nvidia driver, but no avail. In fact, it getting worst. Then, I thought maybe the system not stable, so I upgrade the system to 14.04. But the problem still persist. Again, I installed the Nvdia driver again, it seem to work but eventually it also no avail. The problem seem more serious under Nvdia driver. And I revert back to the opensource driver. It works, but only in xfce environment. It also freeze if I using other environment. It's okay for me to use xfce, but the thing is when I try to play the "Nibbles" (which I think it is preinstalled in 14.04), not long I played, it freeze again. I also thought this might be the hardware problem, maybe it is the onboard vga card got something wrong with it. After All, I have been using this computer for 5 years. But, when i using Window 7 (using dual boot), it's never be the problem. Everything is working fine in Window 7. So, the hardware issue, ruled out. Hope you can help. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Wed Nov 5 22:43:33 2014 DistUpgraded: 2014-11-05 02:41:27,689 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: virtualbox, 4.3.10, 3.13.0-39-generic, x86_64: installed virtualbox, 4.3.10, 3.5.0-54-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:83a4] InstallationDate: Installed on 2013-03-23 (592 days ago) InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130213) Lsusb: Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 003: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse Bus 002 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=9faca4c5-9082-45a6-aa69-00dec6f3c30b ro plymouth:debug drm.debug=0xe no=1 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-11-04 (0 days ago) dmi.bios.date: 04/08/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0701 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M2N68-AM Plus dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0701:bd04/08/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N68-AMPlus:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Wed Nov 5 22:42:17 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 04f3:0103KEYBOARD, id 8 inputHID 04f3:0103KEYBOARD, id 9 inputUSB Optical MouseMOUSE, id 10 xserver.errors: Failed to load module "nv
[Touch-packages] [Bug 1355095] Re: mediaplayer hangs on fast-forward
** Tags added: ubuntu-rtm -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediaplayer-app in Ubuntu. https://bugs.launchpad.net/bugs/1355095 Title: mediaplayer hangs on fast-forward Status in Media Hub: In Progress Status in “mediaplayer-app” package in Ubuntu: Invalid Bug description: mako build #183 last known good build: ? TEST CASE: 1. Download http://trailers.divx.com/divx_prod/divx_plus_hd_showcase/AmosTV_10min_HT.divx 2. Play it in the mediaplayer 3. Once the video starts playing, if the control bar is not displayed tap the screen to display it 4. Tap the slider to fast-forward to the middle of the video EXPECTED RESULT The video continues playing from the middle of the track ACTUAL RESULT The player hangs ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mediaplayer-app 0.20.5+14.10.20140718.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Mon Aug 11 11:35:22 2014 InstallationDate: Installed on 2014-08-11 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140811-020205) SourcePackage: mediaplayer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/media-hub/+bug/1355095/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380683] Re: Web app requiring account, and "Online Accounts" account screen, disappear without explanation
** Tags removed: touch-2014-10-30 ** Tags added: touch-2014-11-13 ** Also affects: qtbase-opensource-src (Ubuntu RTM) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings-online-accounts (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu RTM) Importance: Undecided => High ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu RTM) Importance: Undecided => High ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu RTM) Assignee: (unassigned) => Alberto Mardegan (mardy) ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu RTM) Status: New => Confirmed ** Changed in: ubuntu-system-settings-online-accounts (Ubuntu RTM) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1380683 Title: Web app requiring account, and "Online Accounts" account screen, disappear without explanation Status in “qtbase-opensource-src” package in Ubuntu: Incomplete Status in “ubuntu-system-settings-online-accounts” package in Ubuntu: Confirmed Status in “qtbase-opensource-src” package in Ubuntu RTM: New Status in “ubuntu-system-settings-online-accounts” package in Ubuntu RTM: Triaged Bug description: Ubuntu 14.10 r279 1. Launch a Web app that requires an online account, e.g. Twitter or Facebook. 2. Launch System Settings, and choose an account type. What happens: 1. The app opens, shows an Online Accounts prompt with a spinner for a few seconds, then disappears. 2. An account screen appears for a few seconds, then you're returned to Online Accounts. What should happen: 1. You see the sign-in page. 2. You see the sign-in page. [Originally reported by Patricia Davila.] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1380683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376644] Re: Some qtpim tests start failing when built against Qt 5.3.2
A log of a successful run of tests locally without disabling extra tests, when qtpim libraries and the QML modules are already installed. (a cmake related test was skipped, since that succeeds on the builders but not if using the build directory, a path parsing upstream problem) ** Attachment added: "successful_qtpim_makecheck_local_qt532.txt" https://bugs.launchpad.net/ubuntu/+source/qtpim-opensource-src/+bug/1376644/+attachment/4253899/+files/successful_qtpim_makecheck_local_qt532.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtpim-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1376644 Title: Some qtpim tests start failing when built against Qt 5.3.2 Status in “qtpim-opensource-src” package in Ubuntu: New Bug description: Some qtpim tests start failing when built against Qt 5.3.2: https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-015/+sourcepub/4451482/+listing- archive-extra We shouldn't be disabling additional tests, so the root causes should be found. All seem to have the following thing in common: "ASSERT failure in QTest::fetchData(): "Test data requested, but no testdata available.", file qtestcase.cpp, line 2047" You can test the Qt 5.3.2 yourself by following the instructions at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtpim-opensource-src/+bug/1376644/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372948] Re: Keyboard doesn't auto-capitalize 'I'
** Changed in: ubuntu-keyboard Status: Confirmed => In Progress ** Changed in: ubuntu-keyboard (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1372948 Title: Keyboard doesn't auto-capitalize 'I' Status in Ubuntu Keyboard: In Progress Status in “ubuntu-keyboard” package in Ubuntu: In Progress Bug description: In English 'I' is not auto-capitalized. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-keyboard 0.99.trunk.phablet2+14.10.20140910~rtm-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Tue Sep 23 15:44:57 2014 InstallationDate: Installed on 2014-09-16 (7 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-030205) SourcePackage: ubuntu-keyboard UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1372948/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330262] Re: HUAWEI E3531 not connected on Ubuntu 14.04
** Changed in: network-manager Importance: Unknown => Critical -- 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/1330262 Title: HUAWEI E3531 not connected on Ubuntu 14.04 Status in NetworkManager: Unknown Status in “network-manager” package in Ubuntu: Triaged Bug description: PC: Dell 3721 OS:Ubuntu 14.04 i386 DE: KDE Kernel: 3.13.0-29 and 3.15.0 (Stable) usb-modeswitch 2.2.0 (Debian Unstable)/2.1.1 A connection is defined and a modem in the system, but an error while connecting: "Connection deactivated". Upgrading to kernel 3.15 (stable) and usb-modeswitch (2.2.0) not solve the problem. LOGS: dmesg [ 84.302769] usb 3-4: new high-speed USB device number 3 using xhci_hcd [ 84.431625] usb 3-4: New USB device found, idVendor=12d1, idProduct=1506 [ 84.431632] usb 3-4: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 84.431635] usb 3-4: Product: Mobile Connect [ 84.431638] usb 3-4: Manufacturer: .. [ 84.731329] usbcore: registered new interface driver usbserial [ 84.731348] usbcore: registered new interface driver usbserial_generic [ 84.731362] usbserial: USB Serial support registered for generic [ 84.762404] usbcore: registered new interface driver option [ 84.762424] usbserial: USB Serial support registered for GSM modem (1-port) [ 84.762598] option 3-4:1.0: GSM modem (1-port) converter detected [ 84.762763] usb 3-4: GSM modem (1-port) converter now attached to ttyUSB0 [ 84.762820] option 3-4:1.1: GSM modem (1-port) converter detected [ 84.762947] usb 3-4: GSM modem (1-port) converter now attached to ttyUSB1 To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1330262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307535] Re: Installing apps manually does not refresh the scope
This is causing frequent issues when distributing development packages for testing. I'd vote for increasing priority. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1307535 Title: Installing apps manually does not refresh the scope Status in “unity-scope-click” package in Ubuntu: Triaged Bug description: When installing apps from the command line, the scope is not refreshed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1307535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp