[Touch-packages] [Bug 1383297] Re: [oobe] Edge tutorial's redesign: new gestures
** Changed in: ubuntu-ux Status: In Progress = Fix Committed -- 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/1383297 Title: [oobe] Edge tutorial's redesign: new gestures Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: New Bug description: The first-boot edge tutorial should cover a wider range of gestures than it currently does. Things like right edge swipe, bottom edge swipe, and long vs short swipes. Visual designs (not entirely finished yet): https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383297/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I have the same bug as described on my fresh install of Ubuntu 14.04, however I'm with a newer kernel because of problems with my wifi drivers in previous versions, which were fixed: Linux 3.17.3-031703-generic #201411141335 SMP Fri Nov 14 18:36:40 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 14.04.1 LTS 14.04 trusty The problem is reproducible multiple times. After closing the laptop lid and going in suspend for a longer period, when opened the laptop displays the welcome screen with my wallpaper, but does not have any field to enter password. Clicking any sound/lang icons on the menu bar does not help, but waiting for a bit of time does. Diagnostics so far: So I dig a bit myself and looked at the log of lightdm, with the problem occurring here: [+0.28s] DEBUG: Session pid=1224: Running command /usr/lib/lightdm/lightdm-greeter-session /usr/sbin/unity-greeter [+0.28s] DEBUG: Creating shared data directory /var/lib/lightdm-data/lightdm [+0.28s] DEBUG: Session pid=1224: Logging to /var/log/lightdm/x-0-greeter.log [+0.33s] DEBUG: Activating VT 7 [+0.33s] DEBUG: Activating login1 session c1 [+0.45s] DEBUG: Session pid=1224: Greeter connected version=1.10.3 [+0.60s] DEBUG: Session pid=1224: Greeter start authentication for alex [+0.60s] DEBUG: Session pid=1283: Started with service 'lightdm', username 'alex' [+1.67s] DEBUG: Session pid=1283: Got 1 message(s) from PAM [+1.67s] DEBUG: Session pid=1224: Prompt greeter with 1 message(s) [+3.49s] DEBUG: Session pid=1283: Authentication complete with return value 0: Success As can be seen the period 0.60-1.67 is just waiting for the PAM service to respond (1 minute wait). I typed my password asap as it was available, so my guess is it is connected with the PAM service. I will look into it, but if someone has an idea why would be great. The /var/log/auth.log does not contain any useful information for the why the problem is occurring. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421556] Re: systemd[1]: [/lib/systemd/system/ifup@.service:14] Trailing garbage, ignoring.
Eek, how embarassing. Fixed in git, thanks! ** Changed in: systemd (Ubuntu) Status: New = Fix Committed ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- 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/1421556 Title: systemd[1]: [/lib/systemd/system/ifup@.service:14] Trailing garbage, ignoring. Status in systemd package in Ubuntu: Fix Committed Bug description: Seen into syslog, on a desktop booted with systemd-sysv: systemd[1]: [/lib/systemd/system/ifup@.service:14] Trailing garbage, ignoring. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-8ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0 Uname: Linux 3.19.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Fri Feb 13 09:02:54 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-5-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1421556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421574] [NEW] Mouse partially not working
Public bug reported: Mouse isn't working properly. From time to time, I can only move it but I'm unable to click or scroll, nor does the cursor change it appearance when it should (e.g. when hovering over text it stays an arrow and does not switch to a bar). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Feb 13 09:52:38 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-45-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GF114 [GeForce GTX 560] [10de:1201] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Gigabyte Technology Co., Ltd Device [1458:3527] InstallationDate: Installed on 2015-02-11 (1 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic.efi.signed root=UUID=3d772cca-63e3-40b0-a9a8-a33fdfb88fce ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Ua5 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z68AP-D3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: To be filled by O.E.M. 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.:bvrUa5:bd06/13/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ68AP-D3:rvrTobefilledbyO.E.M.:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 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.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Feb 13 09:46:07 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Unifying Device. Wireless PID:4004 KEYBOARD, id 8 inputSaitek Cyborg R.A.T.3 Mouse MOUSE, id 9 inputSaitek Cyborg R.A.T.3 Mouse MOUSE, id 9 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.15.1-0ubuntu2.6 xserver.video_driver: nouveau ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1421574 Title: Mouse partially not working Status in xorg package in Ubuntu: New Bug description: Mouse isn't working properly. From time to time, I can only move it but I'm unable to click or scroll, nor does the cursor change it appearance when it should (e.g. when hovering over text it stays an arrow and does not switch to a bar). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Feb 13 09:52:38 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7,
[Touch-packages] [Bug 1416048] Re: Expected to be able to pause a video by tapping on anywhere of the video
** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- 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/1416048 Title: Expected to be able to pause a video by tapping on anywhere of the video Status in Media Player App: Confirmed Status in Ubuntu UX bugs: New Status in mediaplayer-app package in Ubuntu: New Bug description: Tapping anywhere on the video that is playing should pause it and vice versa. To manage notifications about this bug go to: https://bugs.launchpad.net/mediaplayer-app/+bug/1416048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421399] Re: [dialer] increase touch area for in call controls
** Summary changed: - increase touch area for in call controls + [dialer] increase touch area for in call controls ** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Assignee: (unassigned) = Olga Kemmet (olga-kemmet) -- 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/1421399 Title: [dialer] increase touch area for in call controls Status in Dialer app for Ubuntu Touch: New Status in Ubuntu UX bugs: Triaged Status in dialer-app package in Ubuntu: New Status in dialer-app package in Ubuntu RTM: New Bug description: from usability tests: Buttons (eg. mute icon, hang up button) are a bit small therefore demanded high gesture precision. Guidance from design is Make invisible touch targets larger To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1421399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421560] Re: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service'
** Package changed: systemd (Ubuntu) = rtkit (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1421560 Title: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' Status in rtkit package in Ubuntu: New Bug description: booted with systemd-sysv seen into syslog: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-8ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0 Uname: Linux 3.19.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Fri Feb 13 09:19:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-5-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1421560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 932834] Re: Enable equalizer
Hello, as suggested by Pascal de Bruijn (pmjdebruijn), I filed a feature request against unity-control-center, see: https://bugs.launchpad.net/ubuntu/+source/unity-control- center/+bug/1421581 Regards -- 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/932834 Title: Enable equalizer Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Precise: Won't Fix Status in pulseaudio source package in Quantal: Won't Fix Status in pulseaudio source package in Raring: Won't Fix Bug description: pulseaudio has support for built in equalizer, but ubuntu does not have enabled it. pulseudio provides module module-equalizer-sink which needs to be enabled at compile time. In src/Makefile.am is this code: if HAVE_DBUS if HAVE_FFTW modlibexec_LTLIBRARIES += \ module-equalizer-sink.la bin_SCRIPTS += utils/qpaeq endif endif So for equalizer module is needed package fftw-dev. Please add needed fftw packages to pulseaudio build depends for equalizer support. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/932834/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1331346] Re: No access to contacts on SIM
** Changed in: ubuntu-ux Importance: Undecided = High ** Summary changed: - No access to contacts on SIM + [address book] No access to contacts on SIM ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1331346 Title: [address book] No access to contacts on SIM Status in Address Book App: New Status in Ubuntu UX bugs: Triaged Status in address-book-app package in Ubuntu: In Progress Status in ofono package in Ubuntu: Fix Committed Bug description: Hi, There are no option to sync contact for a human being form the Contacts apps, from SIM. Steps : * Launch contacts * no option to sync, import/export contact are found on the interface (only a search option and a + option) * swipe from down to access the + menu, users might expect to add manually contact here, no more option like importing SIM contact. * To be sure I checked in the system settings, no import option found there User should be able to add contact from his SIM card (no one want to import hundreds of contacts manually) To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1331346/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421598] [NEW] DisplayPasskey() entered number wrong on some devices
Public bug reported: Using vivid on the n7, the number of entered digit is random/wrong, it should start at 0 and increase to 6 as you type, but on that device it returns random value (i.e 75, 92, etc) ** Affects: bluez (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1421598 Title: DisplayPasskey() entered number wrong on some devices Status in bluez package in Ubuntu: New Bug description: Using vivid on the n7, the number of entered digit is random/wrong, it should start at 0 and increase to 6 as you type, but on that device it returns random value (i.e 75, 92, etc) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1421598/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
Also if you could answer the question in #108 this could help us a lot to further debug if necessary the PAM module. And to add, I'm also using a finger print reader (fprintd) as an authentication before the password, but there are some interesting facts about it(before anyone jump and point fingers there): It has a timeout of 10s, the wait for the password text area is ~1 min If I suspend the laptop manually and wake it it uses the fingerprint reader normally. If I close the lid and open it - the finger print reader authentication is not available and the bug occurs. Conclusion: Possibly the fprintd.so library is not loaded for some reason on lid open, or the PAM module encounters some problems, after which it falls back (somehow) to the unix password. Again if you answer #108 would be most appreciated. -- 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/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: Fix Released Bug description: *** IMPORTANT ** *** The fix is not included in TRUSTY. Will be included with next SRU. *** If you can reproduce this bug please be sure to provide the following info: 1. Do you use a multi-head setup? If yes, using just one monitor fixes the issue? 2. Can you reproduce all the time? 3. Do you use ldap? If yes, using gnome-screensaver fix the issue (see comment #115) can you still reproduce that? 4. Please consider posting /var/log/auth.log (at least part of it, should not contain sensitive information) 5. Please specify the unity version *** END IMPORTANT ** Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420601] Re: Systemd_218-6ubuntu1 and later cannot connect to network except via USB
It's actually very likely that this is due to bug 1421556. I'm going to fix that soon; can you please test the next version as soon as I upload it, and complain here if it still doesn't work? If you want, you can also test this right away already, by replacing /lib/systemd/system/ifup@.service with the attached file. Thanks! ** Attachment added: fixed /lib/systemd/system/ifup@.service https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1420601/+attachment/4318743/+files/ifup%40.service -- 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/1420601 Title: Systemd_218-6ubuntu1 and later cannot connect to network except via USB Status in systemd package in Ubuntu: Incomplete Bug description: systemd_218-6ubuntu1_amd64.deb and later work ONLY with USB networking devices when booted from Dracut. Dracut network module is NOT in use, and binaries needed to connect to the network do not appear in my initramfs, yet systemd version loaded from it determines whether or not network can be connected. With an AMD Athlon II x4 machined and a Gigabyte AMD motherboard (785 series I think), I get the systemd networking unit entering a failed state, and the wired network cannot be turned on. On an Intel Atom Pine Trail netbook the wireless attempt to connect to the network but hangs on requesting an IP address from the router, never completing. Rolling back systemd to systemd_218-5ubuntu2_amd64.deb always fixes this and brings back normal network connectivity. Finally, an AMD bulldozer machine connected by a USB wifi device has no trouble at all with the newer builds of systemd. systemd_218-5ubuntu2_amd64.deb , which came out Jan 23, seems to be the last good version. Same upstream version of systemd, apparently just build-time changes caused this. I'm not sure if this bug will appear with a normal Ubuntu initramfs- tools initramfs (I use Dracut with systemd in the initramfs), but I bring this up because my /boot partition is not normally mounted (so as not to corrupt a monitored hash value) and which version of systemd is in the initramfs, not the version on disk, determines whether or not networking functions on my machines. I do understand my setup has diverged a lot from normal Ubuntu, someone should see if this problem exists in a normal Ubuntu install. If not I will need to find out what changed(possibly a udev rule?) and revert it myself in all later versions. I've been using systemd with dracut/systemd in the initramfs since last May, I now rely on it to run a parallelized version of my multi- encrypted disk unlocking program and am not about to revert it. Initramfs-tools seems to be unable to cope with multiple asynchrounous instances of cryptsetup, while dracut/systemd handles it just fine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1420601/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415256] Re: Errors entering single-user mode; hang going back to multiuser
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upstart (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1415256 Title: Errors entering single-user mode; hang going back to multiuser Status in upstart package in Ubuntu: Confirmed Bug description: Several wrong-looking messages appear when entering single-user mode, and when ^D is typed to exit the single-user shell, the system hangs trying to resume multi-user mode (the graphical login never apperas, nor does the virtual-terminal login prompt). I observed this testing with virtualbox. Haven't tried bare metal. I will attach two screenshots, one showing the entry into single-user mode, the second showing the attempted exit. But the bits which seemed relevant are reproduced below; STEPS TO REPRODUCE: 1. Log in as root from a virtual console (in virtualbox: host-F1 and log in) 2. $ shutdown now # documented to enter single-user mode /lib/init/init-d-script: 2: /etc/default/whoopsie: [General]: not found ... ModemManager ... Caught signal, shutting down... ModemManager ... Could not acquire the 'org.freedesktop.Modemmanger1' service name 3. When prompted, enter root password ... 4. ^D (or type 'exit') ... /lib/init/init-d-script: 2: /etc/default/shoopsie: [General]: not found systemd-logind: Failed to start user service: Unknown unit: user@108.service systemd-logind: Failed to start user service: Unknown unit: user@0.service systemd-logind: Failed to start user service: Unknown unit: user@1000.service * Starting shoopsie shoopsie[fail] (HANGS) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 27 15:46:46 2015 InstallationDate: Installed on 2015-01-02 (25 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150102) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic root=UUID=96d674cd-12fb-4ad1-8d76-cffb545e6256 ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1415256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386268] Re: [oobe] Edge tutorial's redesign: new look
** Changed in: ubuntu-ux Status: In Progress = Fix Committed -- 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/1386268 Title: [oobe] Edge tutorial's redesign: new look Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: New Bug description: This is a breakout from bug 1383297 (which now just covers new gestures). This bug is just about implementing the new look and feel as well as dropping the first greeter screen, which is no longer in the tutorial designs. I'm making a separate bug because they will likely be given different priorities and implemented at different times. You can see the new visuals in this folder: https://drive.google.com/a/canonical.com/folderview?id=0B8I8ZVKH- 8SsM1QyMmhWbkpRLTg And the flow in general here: https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1386268/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 49521] Re: Screen locks up black on laptop lid close.
snurfle, it would help immensely if you filed a new report via a terminal: ubuntu-bug linux Please feel free to subscribe me to it. -- 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/49521 Title: Screen locks up black on laptop lid close. Status in xorg package in Ubuntu: Incomplete Bug description: Binary package hint: acpi On my Dell 640C laptop, my screen locks up black whenever I close the lid. Doesn't matter if I have it set to sleep/suspend, blank screen, or just no event. Whenever I close the lid, it locks up black and nothing short of restarting Gnome or rebooting can get my screen back. Thanks for any fixes/suggestions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/49521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393008] Re: Horizontal cards with summary don't get backgrounds
This is intertwined with bug #1411748.
** Also affects: canonical-devices-system-image
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1393008
Title:
Horizontal cards with summary don't get backgrounds
Status in the base for Ubuntu mobile products:
New
Status in Ubuntu App Developer site:
Invalid
Status in unity8 package in Ubuntu:
Fix Released
Status in unity8 package in Ubuntu RTM:
New
Bug description:
If I change the WEATHER_TEMPLATE in the scopes example to:
const static string WEATHER_TEMPLATE =
R(
{
schema-version: 1,
template: {
category-layout: carousel,
card-layout: horizontal,
card-size: small,
card-background:color:///#0F0F0F
},
components: {
title: title,
art : {
field: art
},
subtitle: subtitle,
summary: summary
}
}
);
The cards are placed in carousel style, but the background color is
simply omitted, the color of the card stays black.
If the card-layout is changed from horizontal to vertical, the
color is there, and the cards in a carousel style, but the bottom 10%
of the cards seem to be clipped. (Screenshot attached)
This is my first bug report ever, so please let me know what else I
should add, or if I am at the right place at all.
Reported from: http://developer.ubuntu.com/scopes/cookbook/
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1393008/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393447] Re: Launcher over greeter should remain on screen if the left edge gesture did not swipe the greeter away
** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Michał Sawicz (saviq) -- 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/1393447 Title: Launcher over greeter should remain on screen if the left edge gesture did not swipe the greeter away Status in the base for Ubuntu mobile products: In Progress Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Triaged Bug description: Preconditions: * Have the screen lock method configured to use a PIN code Steps: * swipe from the left edge so that the welcome screen (Greeter) is moved, but springs back into place Expected: * launcher remains on screen Current: * launcher hides ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.01+15.04.20141107.2-0ubuntu2 Uname: Linux 3.18.0-031800rc4-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 17 16:01:43 2014 SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1393447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1401635] Re: NVIDIA driver makes internet very slow
Adrians Netlis, could you please run the apport-collect from http://cdimage.ubuntu.com/daily-live/current/ and advise if this is reproducible? As well, is this reproducible without installing the Nvidia drivers? ** Tags removed: 331 drivers graphics internet nvidia r8168 r8169 ** Tags added: latest-bios-1.90 ** Changed in: xorg (Ubuntu) Importance: Low = High ** Changed in: xorg (Ubuntu) Status: Expired = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1401635 Title: NVIDIA driver makes internet very slow Status in xorg package in Ubuntu: Incomplete Bug description: Here is information about bug: I am not a good computer spec, so I could not find reason of it, but, when I installed NVIDIA bin-331.89 driver from additional drivers, it appeared a bug so my internet became very slow. I use Realtek RTL8111/RTL8168... ethernet adapter. I have r8169 kernel driver in use(I am not allowed to modify internet stuff in this computer, cause this is actually my parent's PC). Wehn I installed NVIDIA driver, internet appeared to work very, very slow. After getting rid of it, it became nice again. Could you, please, look trought this and find something to fix this. Maybe you could gimme full tutorial on how to do it if I have: 01:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce GT 610] (rev a1) 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) --- .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity DistUpgraded: 2014-12-01 17:54:03,868 DEBUG enabling apt cron job DistroCodename: utopic DistroRelease: Ubuntu 14.10 DistroVariant: ubuntu GraphicsCard: NVIDIA Corporation GF119 [GeForce GT 610] [10de:104a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: CardExpert Technology Gainward GeForce GT 610 [10b0:104a] InstallationDate: Installed on 2014-11-26 (17 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: xorg 1:7.7+7ubuntu2 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic root=UUID=2e2221b2-b6c7-4553-815f-67afdc924a98 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.16.0-28.37-generic 3.16.7-ckt1 Tags: utopic ubuntu compiz-0.9 Uname: Linux 3.16.0-28-generic x86_64 UpgradeStatus: Upgraded to utopic on 2014-12-01 (11 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/11/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.90 dmi.board.name: H61M-VG3 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.90:bd07/11/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-VG3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Dec 13 10:47:27 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputPIXART USB OPTICAL MOUSE MOUSE, id 8 inputUSB USB Keykoard KEYBOARD, id 9 inputUSB USB Keykoard KEYBOARD, id 10 xserver.errors: Failed to load module nvidia (module does not exist, 0) Failed to load module nvidia (module does not exist, 0) xserver.logfile:
[Touch-packages] [Bug 1355422] Re: [notifications] Can't dismiss notification bubbles
** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Michał Sawicz (saviq) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1355422 Title: [notifications] Can't dismiss notification bubbles Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in Server and client library for desktop notifications in Unity: New Status in unity-notifications package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Triaged Bug description: On a phone with accounts setup for twitter, facebook and 2x google accounts I get a fair number of notifications. Often times these notifications appear while I'm actually using the phone. This presents issues in multiple areas:- * If I'm in the dash I am blocked from using the search function because a notification covers the search button * If I'm in the dash and already searching, having typed something, I'm blocked from seeing what I'm typing by the notification * In apps I can't go back because the notification blocks the button You get the idea. Basically notifications slow me down, because I have to wait for them to disappear. I'd like to be able to dismiss them. On iOS you swipe up which is indicated with a horizontal bar to grab and swipe away. --- Desired solution We've added in the latest specification for notifications bubbles (or clickable notifications) the ability to dismiss a notification via swiping left to right. Link to the spec: https://docs.google.com/a/canonical.com/document/d /1ehZGFePGmy8pnyAGsgWYDeBgr45Cc8jE2mTb2Qz-oeM/edit# To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1355422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350891] Re: [Dash] Suru Background should scroll
** Changed in: unity8 (Ubuntu RTM) Milestone: 14.09-release = 14.09-ota-1 ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Michał Sawicz (saviq) -- 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/1350891 Title: [Dash] Suru Background should scroll Status in the base for Ubuntu mobile products: Confirmed Status in Clock application for Ubuntu devices: Triaged Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: Triaged Bug description: On the dash, the Suru paper folds stays fixed at the bottom, while it should rather scroll away. We should also 'tile' the background, so the paper fold is displayed again after scrolling a certain amount of vertical space. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1350891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418060] Re: QML compilation cache patch needs adaptation for Qt 5.4
** Changed in: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided = Critical ** Changed in: qtdeclarative-opensource-src (Ubuntu) Status: New = Triaged -- 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/1418060 Title: QML compilation cache patch needs adaptation for Qt 5.4 Status in qtdeclarative-opensource-src package in Ubuntu: Triaged Bug description: The environment variable controlled new functionality provided by QML compilation cache patch (being landed for Qt 5.3.2) needs adaptation for Qt 5.4, as it does not currently apply. Attachment shows a summary of the problems. More information about Qt 5.4 at https://wiki.ubuntu.com/Touch/QtTesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1418060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421562] [NEW] Not to visualize
Public bug reported: Hi, I'm not to see in first tab, only send. Tks! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Feb 13 06:16:17 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:035a] InstallationDate: Installed on 2015-02-08 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Acer Aspire 5745 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 15/10/2010 dmi.bios.vendor: INSYDE dmi.bios.version: V1.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV51_CP dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDE:bvrV1.18:bd15/10/2010:svnAcer:pnAspire5745:pvrV1.18:rvnAcer:rnJV51_CP:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.name: Aspire 5745 dmi.product.version: V1.18 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.11.3+14.04.20141104-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1~ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.3 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.6 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.4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Thu Feb 12 23:29:59 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 528 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.6 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu ** Summary changed: - Not to see + Not to visualize -- 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/1421562 Title: Not to visualize Status in xorg package in Ubuntu: New Bug description: Hi, I'm not to see in first tab, only send. Tks! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Feb 13 06:16:17 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 18) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:035a] InstallationDate: Installed on 2015-02-08 (5 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) MachineType: Acer Aspire 5745 ProcEnviron: LANGUAGE=pt_BR:pt:en PATH=(custom, no user) LANG=pt_BR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-45-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 15/10/2010 dmi.bios.vendor: INSYDE dmi.bios.version: V1.18 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JV51_CP dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias:
[Touch-packages] [Bug 1421559] [NEW] Should be able to silence alarm using power button
Public bug reported: Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, swipe, enter pin, press OK on alarm What should have happened: I should be able to silence the alarm using the power button—like on iOS. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class. Removing the phone from my pocket, swiping, unlocking and dismissing the alarm, always takes about 3-4 rings. People are starting to notice. Related to bug 1340329. ** Affects: ubuntu-clock-app Importance: Undecided Status: New ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Description changed: (Maybe this should affect indicator-datetime, or whatever is responsible for creating/dismissing alarms?) Reproduce: 1. Set alarm - 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface + 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, swipe, enter pin, press OK on alarm What should have happened: I should be able to silence the alarm using the power button—like on iOS. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class, when the phone is in my trouser pocket. I can never get the screen unlocked in time, so the alarm will ring 4 times, drawing a lot of attention. I really need to be able to stop the alarm quickly pressing the power button. ** Description changed: (Maybe this should affect indicator-datetime, or whatever is responsible for creating/dismissing alarms?) Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, swipe, enter pin, press OK on alarm What should have happened: I should be able to silence the alarm using the power button—like on iOS. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off - during class, when the phone is in my trouser pocket. I can never get - the screen unlocked in time, so the alarm will ring 4 times, drawing a - lot of attention. I really need to be able to stop the alarm quickly - pressing the power button. + during class. Removing the phone from my pocket, swiping, unlocking and + dismissing the alarm, always takes about 3-4 rings. People are starting + to notice. ** Also affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Description changed: - (Maybe this should affect indicator-datetime, or whatever is responsible - for creating/dismissing alarms?) - Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, swipe, enter pin, press OK on alarm What should have happened: I should be able to silence the alarm using the power button—like on iOS. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class. Removing the phone from my pocket, swiping, unlocking and dismissing the alarm, always takes about 3-4 rings. People are starting to notice. + + Related 1340329 ** Description changed: Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, swipe, enter pin, press OK on alarm What should have happened: I should be able to silence the alarm using the power button—like on iOS. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class. Removing the phone from my pocket, swiping, unlocking and dismissing the alarm, always takes about 3-4 rings. People are starting to notice. - Related 1340329 + Related bug 1340329. ** Description changed: Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, swipe, enter pin, press OK on alarm What should have happened: I should be able to silence the alarm using the power button—like on iOS.
[Touch-packages] [Bug 1421556] [NEW] systemd[1]: [/lib/systemd/system/ifup@.service:14] Trailing garbage, ignoring.
Public bug reported: Seen into syslog, on a desktop booted with systemd-sysv: systemd[1]: [/lib/systemd/system/ifup@.service:14] Trailing garbage, ignoring. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-8ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0 Uname: Linux 3.19.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Fri Feb 13 09:02:54 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-5-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid ** Attachment added: ifup@.service https://bugs.launchpad.net/bugs/1421556/+attachment/4318584/+files/ifup%40.service -- 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/1421556 Title: systemd[1]: [/lib/systemd/system/ifup@.service:14] Trailing garbage, ignoring. Status in systemd package in Ubuntu: New Bug description: Seen into syslog, on a desktop booted with systemd-sysv: systemd[1]: [/lib/systemd/system/ifup@.service:14] Trailing garbage, ignoring. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-8ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0 Uname: Linux 3.19.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Fri Feb 13 09:02:54 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-5-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1421556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421560] [NEW] [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service'
Public bug reported: booted with systemd-sysv seen into syslog: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-8ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0 Uname: Linux 3.19.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Fri Feb 13 09:19:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-5-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 vivid ** Attachment added: rtkit-daemon.service https://bugs.launchpad.net/bugs/1421560/+attachment/4318596/+files/rtkit-daemon.service -- 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/1421560 Title: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' Status in systemd package in Ubuntu: New Bug description: booted with systemd-sysv seen into syslog: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-8ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0 Uname: Linux 3.19.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Fri Feb 13 09:19:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-5-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1421560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all
@Raymond Thanks for your information. I will find time to give it a try. -- 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/1414706 Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all Status in HWE Next Project: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: During this test, an error dialog was thrown, reading: The following mixer control(s) might be incorrectly set: Mic is at 0.0% Mic is muted Please try to fix that (e g by running alsamixer -D hw:PCH in a terminal) and see if that solves the problem. Would you like to continue troubleshooting anyway? However, the System Settings... - Sound UI shows the mic as not muted. When I tried running the alsamixer command, I saw mic and mic- boost were both showing 0; I cranked them up to 100, but it made no difference. I also tried re-running this command with the mic/mic- boost still set to 100 and it threw the same error. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 26 16:20:49 2015 InstallationDate: Installed on 2014-09-10 (138 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 1 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio Symptom_Jack: Black Mic, Left Symptom_Type: No sound at all Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET75WW (2.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ALCTO1WW dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394731] Re: [MIR] grilo-plugins
From discussions on IRC -base will have: bookmarks filesystem local-metadata metadata-store appletrailers bliptv filesystem gravatar jamendo lastfm-albumart optical-media raitv shoutcast tracker youtube vimeo -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grilo-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1394731 Title: [MIR] grilo-plugins Status in grilo-plugins package in Ubuntu: Incomplete Bug description: Availability: In universe, builds on all archs Rational: grilo-plugins is now a dependency of totem and is hard to patch out. See lp:1393067 Security: No known CVEs Quality Assurance: No bugs in debian or ubuntu, most upstream bugs are feature requests. Active debian maintainer. Has watch file. Tests are run during build. UI standards: The package is translated upstream. Dependencies: All deps in main Standards compliance: No issues Maintenance: Actively maintained in debian. ubuntu-gnome team will subscribe in ubuntu. Background info: Grilo is a framework focused on making media discovery and browsing easy for application developers. This package contains it's plugins, including the tracker one, which is now needed by totem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grilo-plugins/+bug/1394731/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414706] Re: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all
This seems to be a tricky one. I was wondering if we can also make a coef dump. To do that, please do the following: 1) revert any changes done with hdajackretask or /etc/modprobe.d/alsa-base.conf 2) on top of 14.04, install the latest daily dkms package (from the alsa-daily PPA) 3) reboot 4) (as root) echo 1 /sys/module/snd_hda_codec/parameters/dump_coef 5) start recording to headset mic and confirm that the bug is present (records buzzing noise instead of clear sound) 6) while recording is active, dump alsa-info 7) attach alsa-info (or a link to it) here Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1414706 Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left][Lenovo ThinkPad X240] external mic has no sound at all Status in HWE Next Project: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: During this test, an error dialog was thrown, reading: The following mixer control(s) might be incorrectly set: Mic is at 0.0% Mic is muted Please try to fix that (e g by running alsamixer -D hw:PCH in a terminal) and see if that solves the problem. Would you like to continue troubleshooting anyway? However, the System Settings... - Sound UI shows the mic as not muted. When I tried running the alsamixer command, I saw mic and mic- boost were both showing 0; I cranked them up to 100, but it made no difference. I also tried re-running this command with the mic/mic- boost still set to 100 and it threw the same error. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13 Uname: Linux 3.13.0-45-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio CurrentDesktop: Unity Date: Mon Jan 26 16:20:49 2015 InstallationDate: Installed on 2014-09-10 (138 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_AlsaRecordingTestStderr: a r e c o r d : p c m _ r e a d : 2 0 3 1 : r e a d e r r o r : I n p u t / o u t p u t e r r o r Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: doctorow 2636 F pulseaudio /dev/snd/pcmC1D0c: doctorow 2636 F...m pulseaudio /dev/snd/pcmC1D0p: doctorow 2636 F...m pulseaudio /dev/snd/controlC0: doctorow 2636 F pulseaudio Symptom_Jack: Black Mic, Left Symptom_Type: No sound at all Title: [20ALCTO1WW, Realtek ALC292, Black Mic, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/24/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GIET75WW (2.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ALCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98401 PRO dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGIET75WW(2.25):bd06/24/2014:svnLENOVO:pn20ALCTO1WW:pvrThinkPadX240:rvnLENOVO:rn20ALCTO1WW:rvr0B98401PRO:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 20ALCTO1WW dmi.product.version: ThinkPad X240 dmi.sys.vendor: LENOVO mtime.conffile..etc.modprobe.d.alsa.base.conf: 2015-01-22T13:36:22.741441 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1414706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1291455] Re: Screen and input should be disabled with proximity sensor when on greeter
IIRC it's telepathy-ofono that wakes the screen up for this still (I know, not the greatest architecture...), and powerd/u-s-c are responsible for actually turning it on and off based on proximity. So, as long as the screen is kept on with proximity enabled by telepathy- ofono, u-s-c and powerd should do the right thing and check proximity before turning the display on. ** Also affects: powerd (Ubuntu) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: Triaged = Incomplete -- 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/1291455 Title: Screen and input should be disabled with proximity sensor when on greeter Status in the base for Ubuntu mobile products: Confirmed Status in powerd package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: Steps to reproduce: * suspend your device * cover the proximity sensor (top left on mako) * call the phone Expecte result: * screen does not light up until you uncover the proximity sensor Current result: * screen lights up and you can answer the call This results in butt/pocket calls... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.84+14.04.20140306-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Wed Mar 12 13:14:37 2014 InstallationDate: Installed on 2014-03-12 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140312) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1291455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390136] Re: need a transition state for indicators reflecting laggy backends
Since we don't have a clear idea for fixing this yet, I'd say this should be dropped off the RTM list. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1390136 Title: need a transition state for indicators reflecting laggy backends Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Triaged Status in indicator-network source package in Utopic: Confirmed Status in ubuntu-system-settings source package in Utopic: Confirmed Status in indicator-network source package in Vivid: Confirmed Status in ubuntu-system-settings source package in Vivid: Confirmed Status in unity8 source package in Vivid: Triaged Status in indicator-network package in Ubuntu RTM: New Status in ubuntu-system-settings package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: New Bug description: spawned from efforts in bug 1336715 because the user's input toggle for airplane mode is both a reflection of user intent the state of the backendand the backend is unfortunately variable lengthy to change (anywhere from 1 to ~10+ seconds sometimes) we need to have an intermediate/transition statee.g. toggle to airplane mode onthen animate somehow that there's a transition happening, until it either fails/succeeds comment from dizzypaty Between the user’s action of toggling the airplane switcher on and/or off and the backend updating the state, the indicator icon displayed on the statusbar should be the following: network-idle.svg (https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk). Desired resolution Summary: the interface should immediately respond to user input confirming the action, even if the backend takes up to 20 seconds to actually change state. Having the UI and backend out of sync for up to 30 seconds is not a problem, as long as it always goes back into sync after this delay. 1.When the user changes the flight mode toggle switch it should instantly change state. 2.The backend should then be informed of the state change. 3.Up to 30 seconds later the backend completes the state change Note: The cellular connection indicator should always display the backend state, not the current flight mode toggle switch state Variation - user switches the flight mode toggle on and off rapidly. Once a flight mode state change request has been sent to the backend but before a conformation that the state change is complete is received, all further user interactions should be buffered on the client. When the client receives conformation of the state change from the backend it should check to see if the state is in sync with its buffer. If it is in sync nothing happens and the buffer is cleared. If it is not in sync another state change signal is sent to the backend and the buffer is cleared. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418460] Re: libconnectivity-qt1-dev un-installable in click chroot
How did you install the package? What was the exact command? So for example for an armhf chroot it would be: apt-get install libconnectivity-qt1-dev:armhf Notice the :armhf suffix, without it apt would try to install a x86 package which would conflict with other already installed armhf packages. ** Changed in: qtcreator-plugin-ubuntu (Ubuntu) Status: Confirmed = Incomplete -- 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/1418460 Title: libconnectivity-qt1-dev un-installable in click chroot Status in qtcreator-plugin-ubuntu package in Ubuntu: Incomplete Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: I am unable to install libconnectivity-qt1-dev in a click chroot. It hits dependency errors starting with qtbase5-dev. The following packages have unmet dependencies: libconnectivity-qt1-dev : Depends: qtbase5-dev E: Unable to correct problems, you have held broken packages. I would have thought this package would be already installed as it's a part of the SDK connectivity api. Both Dekko and Shorts app need access to this API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1418460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411751] Re: Attribute in news section of today scope has wrong aspect ratio depending on grid size
** Also affects: unity8 (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu RTM) Status: New = Triaged ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = High ** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Michał Sawicz (saviq) ** Changed in: unity8 (Ubuntu RTM) Milestone: None = 14.09-ota-1 -- 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/1411751 Title: Attribute in news section of today scope has wrong aspect ratio depending on grid size Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: Triaged Bug description: Open the Today scope in Arale Go to News section BBC attribute aspect ratio is not correct. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384374] Re: Dash pauses/stutters during scope switching left/right
We don't have immediate improvements in store for this I'm afraid. It will require further, deep, analysis on what's the blocking part in this situation. It also depends on the design direction we'll go for wrt dash/home. ** Changed in: canonical-devices-system-image Status: Confirmed = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1384374 Title: Dash pauses/stutters during scope switching left/right Status in the base for Ubuntu mobile products: New Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: New Bug description: Dash pauses/stutters during scope switching left/right. Watching the log: tail -f ~/.cache/upstart/unity8-dash.log I can see error messages flood out whenever the dash pauses/stutters during left/right swipes: file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1384374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352251] Re: Reverse trust prompt hosting
We discussed this with tvoss in Brussels, there's an improvement on the architecture of this that we want to happen, but AFAIU it's not critical to any user experience at the moment. IMO this should be pulled off the RTM list. ** Changed in: canonical-devices-system-image Status: Confirmed = New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1352251 Title: Reverse trust prompt hosting Status in the base for Ubuntu mobile products: New Status in Qt integration with the Mir display server: Triaged Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: Triaged Bug description: In order to keep continuity, keeping this original bug rather than spawning a new one. new description: currently non ui process are asking for trust prompts from related focused ui's, example scopes ask for dash to host a prompt. however, it needs to be the other way around, with the ui process having a list of pid's that it can host for. original description: On the phone, a splash screen is shown as soon as QGuiApplication is instantiated; however, a QWindow might be created much later, or not be created at all. We have for example a D-Bus service (ubuntu-system-settings-online-accounts) which is a QGuiApplication, but creates QWindows only as client requests arrive. In the common case, this works fine because the service is generally started when a window needs to be displayed, but we are now preparing for implementing trust session support, and that would require either this bug to be fixed, or a deeper refactoring of our code. see below, that the original description was simply incorrectly using the default socket, instead of the trust socket. the default socket causes the splash screen, whereas the trust socket won't To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1352251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384374] Re: Dash pauses/stutters during scope switching left/right
Right, IMO this should be pulled off the RTM list for now. -- 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/1384374 Title: Dash pauses/stutters during scope switching left/right Status in the base for Ubuntu mobile products: New Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: New Bug description: Dash pauses/stutters during scope switching left/right. Watching the log: tail -f ~/.cache/upstart/unity8-dash.log I can see error messages flood out whenever the dash pauses/stutters during left/right swipes: file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1384374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411748] Re: [Arale] News aggregator scope has a white scope background in cards
Importance of this can be reduced since it's not actually affecting RTM without the fix for the other bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1411748 Title: [Arale] News aggregator scope has a white scope background in cards Status in the base for Ubuntu mobile products: In Progress Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Triaged Bug description: Open the news aggregator in Arale. Go to the section national news A white card background appears This seems to be only impacting vertical-jounal cards. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420544] Re: Ubuntu instances on GCE should use NOOP scheduler
@Ben Howard: I'll upload that to trusty as soon as the current SRU gets verified and into trusty-updates. ** Changed in: systemd (Ubuntu Trusty) Assignee: (unassigned) = Martin Pitt (pitti) ** Changed in: systemd (Ubuntu Trusty) Importance: Undecided = Medium -- 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/1420544 Title: Ubuntu instances on GCE should use NOOP scheduler Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Incomplete Status in systemd source package in Trusty: Triaged Bug description: Per Google's request, Ubuntu instances should use NOOP as the default scheduler. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1420544/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1364973] Re: [sdk] Overflow page header actions' labels truncated
Wrapping is tricky, since a single action may then end up using a lot of lines, giving less space for the other items. Is that what we want? Alternatively, we can also have proper truncation (showing ... at the end of the truncated word). -- 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/1364973 Title: [sdk] Overflow page header actions' labels truncated Status in Ubuntu UX bugs: Triaged Status in The Unity 8 shell: Opinion Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: The overflowing page header action labels have very little space, and are not wrapped, which results in truncating the labels. I think we need to add wrapping in those labels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1364973/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1352251] Re: Reverse trust prompt hosting
Agreed. I thought this could solve focus issues we're experiencing with trust prompts But Saviq confirmed this is unrelated. So I agree that all system clients that would benefit from that have otherwise found ways around this and there is no user experience broken by the absence of this I can think of. On Fri, Feb 13, 2015 at 12:20 PM, Michał Sawicz michal.saw...@canonical.com wrote: We discussed this with tvoss in Brussels, there's an improvement on the architecture of this that we want to happen, but AFAIU it's not critical to any user experience at the moment. IMO this should be pulled off the RTM list. ** Changed in: canonical-devices-system-image Status: Confirmed = New -- You received this bug notification because you are a bug assignee. https://bugs.launchpad.net/bugs/1352251 Title: Reverse trust prompt hosting To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1352251/+subscriptions -- 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/1352251 Title: Reverse trust prompt hosting Status in the base for Ubuntu mobile products: New Status in Qt integration with the Mir display server: Triaged Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: Triaged Bug description: In order to keep continuity, keeping this original bug rather than spawning a new one. new description: currently non ui process are asking for trust prompts from related focused ui's, example scopes ask for dash to host a prompt. however, it needs to be the other way around, with the ui process having a list of pid's that it can host for. original description: On the phone, a splash screen is shown as soon as QGuiApplication is instantiated; however, a QWindow might be created much later, or not be created at all. We have for example a D-Bus service (ubuntu-system-settings-online-accounts) which is a QGuiApplication, but creates QWindows only as client requests arrive. In the common case, this works fine because the service is generally started when a window needs to be displayed, but we are now preparing for implementing trust session support, and that would require either this bug to be fixed, or a deeper refactoring of our code. see below, that the original description was simply incorrectly using the default socket, instead of the trust socket. the default socket causes the splash screen, whereas the trust socket won't To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1352251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372061] Re: SMS notification: time format not translatable
The required API was not accepted into UITK yet, ww09 seems like an impossible target for this. ** Changed in: unity8 (Ubuntu RTM) Milestone: 14.09-release = 14.09-ota-1 -- 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/1372061 Title: SMS notification: time format not translatable Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu Translations: Triaged Status in telephony-service package in Ubuntu: Invalid Status in ubuntu-settings-components package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in ubuntu-settings-components package in Ubuntu RTM: Triaged Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: Triaged Bug description: See the attached screenshot. The time for the notification seems to be hardcoded to hh:mm - mm, d. This works well for the US, but it's not a format that is used in all other countries. In Spain, for example, the date would rather be d mm. The time format needs to be marked for translation. Not sure from which project the notifications come from, for some reason I seem to remember they were moved to u-s-s, but if it's the wrong project/package, please reassign. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1372061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1365673] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal: UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPl
This bug consistently evades me. I've spent much time trying to reproduce this to no avail. This fail will occur if mir client process are *not* launched via ubuntu-app-launch - as unity8 will not accept mir connections it doesn't expect, causing the client to crash with this error. The obvious possibility is a race where unity8 is informed of a client launch only after client tries to connect - but the logs don't indicate this. There could be a bug somewhere in the stack causing a client to be launched twice, the first will be accepted, the second rejected and crashing. The logs do seem to indicate this possibility, but I cannot pinpoint where. Logs from ubuntu-app-launch upstart might help shed light. Any suggestions on increasing the odds of reproducing this would be appreciated. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1365673 Title: /usr/lib/arm-linux- gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal: UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration Status in the base for Ubuntu mobile products: Confirmed Status in Qt integration with the Mir display server: Triaged Status in QT Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Status in qtmir package in Ubuntu RTM: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding qtdeclarative-opensource-src. This problem was most recently seen with version 5.3.0-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/4618cad07e610ca3c59a3e07c582e963d4780359 contains more details. steps to reproduce: run the lrt switch test 1. open a bunch of apps 2. swipe the screen to show the app selector 3. pick an app at random 4. swipe the screen again to show the app selector 5. pick an app at random 6. repeat steps 2-5 until crash shows in /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1365673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390393] Re: It's too easy to trigger a volume notification when taking a screenshot
** Changed in: unity8 (Ubuntu RTM) Milestone: 14.09-release = 14.09-ota-1 -- 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/1390393 Title: It's too easy to trigger a volume notification when taking a screenshot Status in the base for Ubuntu mobile products: In Progress Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: In Progress Bug description: On Mako, I'm unable to take a screenshot (Vol up + Vol down) without changing the volume, which causes a notification to appear on the screenshot, and changes the volume when taking a screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393485] Re: [SDK] Need a standard way to make an Icon look disabled
Disabled icons in the standard list items currently have an opacity of 0.5. Do you want to change that to 0.3 as well? -- 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/1393485 Title: [SDK] Need a standard way to make an Icon look disabled Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Right now if one wants to use an Icon inside a ListItem.Empty or any other AbstractButton derived class, and disable the item, there is no standard way to make the Icon look disabled without directly affecting its opacity and/or colorization. Haviing a standard way to do this would help promoting consistency in the UI. --- UX Solution --- Agreed. Disabled icons should have 30% opacity by default, but that can be changed by the App developer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1393485/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1369939] Re: Default value for MainView.useDeprecatedToolbar will change to false in 1.2
Implemented in this MR https://code.launchpad.net/~tpeeters/ubuntu-ui- toolkit/10-mv12/+merge/247230 by disabling the toolbar and removing the useDeprecatedToolbar property in 1.2. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: Confirmed = Fix Committed -- 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/1369939 Title: Default value for MainView.useDeprecatedToolbar will change to false in 1.2 Status in ubuntu-ui-toolkit package in Ubuntu: Fix Committed Bug description: This was announced on the mailing lists To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1369939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421308] Re: Deadlock in Unity8
Please read previous comments before re-assigning affected project. Unity8's main loop is blocked, which will cause qtmir to block mir when mir is asking if a session should be authorized or not - as that decision made in unity8's main loop. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: qtmir (Ubuntu) Status: New = Invalid ** Changed in: qtmir Status: New = Invalid ** Changed in: unity8 (Ubuntu) Importance: Undecided = Critical -- 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/1421308 Title: Deadlock in Unity8 Status in Qt integration with the Mir display server: Invalid Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: New Bug description: Got a lockup on boot, here's a another gdb t a a bt. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1421308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334855] Re: [design] Can't use toolbar while notifications on screen
** Changed in: canonical-devices-system-image Importance: Undecided = Medium ** Changed in: canonical-devices-system-image Status: New = In Progress ** Changed in: canonical-devices-system-image Milestone: None = ww09-2015 -- 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/1334855 Title: [design] Can't use toolbar while notifications on screen Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: New Bug description: With notifications on the screen, they're overlayed on top of the top toolbar, as such I can't tap the back button. To replicate. Open system settings - accounts Sign in to twitter Wait while tweet notifications come in Navigate anywhere in system settings, such as updates. Note you can't go back while the notifications are on screen. See screenshot, back button obscured. --- Desired resolution: - All types of notifications should be dismissable To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1334855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1419854] Re: contact export does not work correctly when multiple contacts selected
** Branch linked: lp:~renatofilho/address-book-app/fix-1419854 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1419854 Title: contact export does not work correctly when multiple contacts selected Status in Address Book App: In Progress Status in the base for Ubuntu mobile products: In Progress Status in address-book-app package in Ubuntu: New Status in address-book-service package in Ubuntu: New Status in address-book-app package in Ubuntu RTM: New Bug description: In Telegram application, when trying to import a big list of contacts from Contacts application using the ContentHub there is a weird behaviour: The generated file in path: ~/.cache/com.ubuntu.telegram/HubIncoming/number/ubuntu_contacts.vcf usually has not the requested contacts. Instead it has a different small number of them. The format of the file is valid but doesn't contains the N requested contacts to be imported in Telegram. After doing a lot of tests, i have realized that: - If I select X contacts to import so that X 25, those X contacts are included in ubuntu_contacts.vcf (Ok) - If I select 25 contacts to import, all the contacts in agenda are included in ubuntu_contacts.vcf (578 elements) - If i select Y contacts so that Y % 25 == Z, then Z contacts are included in ubuntu_contacts.vcf To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1419854/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390136] Re: need a transition state for indicators reflecting laggy backends
track on later milestone as this experience needs a solution ** Changed in: canonical-devices-system-image Milestone: ww09-2015 = ww13-2015 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1390136 Title: need a transition state for indicators reflecting laggy backends Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in indicator-network package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Triaged Status in indicator-network source package in Utopic: Confirmed Status in ubuntu-system-settings source package in Utopic: Confirmed Status in indicator-network source package in Vivid: Confirmed Status in ubuntu-system-settings source package in Vivid: Confirmed Status in unity8 source package in Vivid: Triaged Status in indicator-network package in Ubuntu RTM: New Status in ubuntu-system-settings package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: New Bug description: spawned from efforts in bug 1336715 because the user's input toggle for airplane mode is both a reflection of user intent the state of the backendand the backend is unfortunately variable lengthy to change (anywhere from 1 to ~10+ seconds sometimes) we need to have an intermediate/transition statee.g. toggle to airplane mode onthen animate somehow that there's a transition happening, until it either fails/succeeds comment from dizzypaty Between the user’s action of toggling the airplane switcher on and/or off and the backend updating the state, the indicator icon displayed on the statusbar should be the following: network-idle.svg (https://drive.google.com/drive/#folders/0BzbnWoHmYF3aZTA4WHNPYW1jeUE/0BzbnWoHmYF3aS2pVejVicktrdm8/0BzbnWoHmYF3ablBITVByRnpzdEk). Desired resolution Summary: the interface should immediately respond to user input confirming the action, even if the backend takes up to 20 seconds to actually change state. Having the UI and backend out of sync for up to 30 seconds is not a problem, as long as it always goes back into sync after this delay. 1.When the user changes the flight mode toggle switch it should instantly change state. 2.The backend should then be informed of the state change. 3.Up to 30 seconds later the backend completes the state change Note: The cellular connection indicator should always display the backend state, not the current flight mode toggle switch state Variation - user switches the flight mode toggle on and off rapidly. Once a flight mode state change request has been sent to the backend but before a conformation that the state change is complete is received, all further user interactions should be buffered on the client. When the client receives conformation of the state change from the backend it should check to see if the state is in sync with its buffer. If it is in sync nothing happens and the buffer is cleared. If it is not in sync another state change signal is sent to the backend and the buffer is cleared. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1390136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393008] Re: Horizontal cards with summary don't get backgrounds
** Changed in: canonical-devices-system-image
Importance: Undecided = High
** Changed in: canonical-devices-system-image
Status: New = In Progress
** Changed in: canonical-devices-system-image
Milestone: None = ww09-2015
--
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/1393008
Title:
Horizontal cards with summary don't get backgrounds
Status in the base for Ubuntu mobile products:
In Progress
Status in Ubuntu App Developer site:
Invalid
Status in unity8 package in Ubuntu:
Fix Released
Status in unity8 package in Ubuntu RTM:
New
Bug description:
If I change the WEATHER_TEMPLATE in the scopes example to:
const static string WEATHER_TEMPLATE =
R(
{
schema-version: 1,
template: {
category-layout: carousel,
card-layout: horizontal,
card-size: small,
card-background:color:///#0F0F0F
},
components: {
title: title,
art : {
field: art
},
subtitle: subtitle,
summary: summary
}
}
);
The cards are placed in carousel style, but the background color is
simply omitted, the color of the card stays black.
If the card-layout is changed from horizontal to vertical, the
color is there, and the cards in a carousel style, but the bottom 10%
of the cards seem to be clipped. (Screenshot attached)
This is my first bug report ever, so please let me know what else I
should add, or if I am at the right place at all.
Reported from: http://developer.ubuntu.com/scopes/cookbook/
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1393008/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408263] Re: Edge gestures still get lost
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: android (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/1408263 Title: Edge gestures still get lost Status in android package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: There are still cases where edge gestures are lost. Over the christmas holidays It happened about 5 times to me (in 2 weeks). Only way to recover is to reboot the phone. It always happened while the phone was in my pocket. When pulling it out of the pocket the edge gestures (launcher and right edge) were gone. This is most likely related to random taps on the screen, maybe in combination with the display toggling on/off. Haven't found a way yet to manually trigger it. Will keep on trying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1408263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421656] [NEW] package libllvm3.4 1:3.4.2-10ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1' to '/usr/lib/x86_64-li
Public bug reported: I have no idea what happened. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libllvm3.4 1:3.4.2-10ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 AptOrdering: libllvm3.4: Install libllvm3.4: Configure Architecture: amd64 Date: Fri Feb 13 19:10:43 2015 ErrorMessage: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1' to '/usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2014-12-27 (47 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: llvm-toolchain-3.4 Title: package libllvm3.4 1:3.4.2-10ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1' to '/usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1.dpkg-new': unexpected end of file or stream UpgradeStatus: Upgraded to utopic on 2015-01-19 (25 days ago) ** Affects: llvm-toolchain-3.4 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to llvm-toolchain-3.4 in Ubuntu. https://bugs.launchpad.net/bugs/1421656 Title: package libllvm3.4 1:3.4.2-10ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1' to '/usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1.dpkg-new': unexpected end of file or stream Status in llvm-toolchain-3.4 package in Ubuntu: New Bug description: I have no idea what happened. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: libllvm3.4 1:3.4.2-10ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-30.40-generic 3.16.7-ckt3 Uname: Linux 3.16.0-30-generic x86_64 ApportVersion: 2.14.7-0ubuntu8.1 AptOrdering: libllvm3.4: Install libllvm3.4: Configure Architecture: amd64 Date: Fri Feb 13 19:10:43 2015 ErrorMessage: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1' to '/usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1.dpkg-new': unexpected end of file or stream InstallationDate: Installed on 2014-12-27 (47 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: llvm-toolchain-3.4 Title: package libllvm3.4 1:3.4.2-10ubuntu1 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1' to '/usr/lib/x86_64-linux-gnu/libLLVM-3.4.so.1.dpkg-new': unexpected end of file or stream UpgradeStatus: Upgraded to utopic on 2015-01-19 (25 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.4/+bug/1421656/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421662] [NEW] system goes into hanging state
Public bug reported: after login the system is go into hang state and mouse also not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Feb 13 20:18:18 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu 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 2015-02-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lsusb: Bus 001 Device 002: ID 04a9:2737 Canon, Inc. MF4410 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c535 Logitech, Inc. Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=232289ef-c909-4c42-8d3e-be728694ea7d ro recovery nomodeset Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) XorgLogOld: dmi.bios.date: 09/11/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0804 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.:bvr0804:bd09/11/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+14.04.20140409-0ubuntu1 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 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 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Fri Feb 13 20:16:45 2015 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Dell Wireless Mouse WM123 MOUSE, id 8 inputLogitech Dell Wireless Mouse WM123 KEYBOARD, id 9 inputAT Translated Set 2 keyboard KEYBOARD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 ** 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/1421662 Title: system goes into hanging state Status in xorg package in Ubuntu: New Bug description: after login the system is go into hang state and mouse also not working ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Feb 13 20:18:18 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu 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 2015-02-13 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release i386 (20140417) Lsusb: Bus 001 Device 002: ID 04a9:2737 Canon, Inc. MF4410 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 046d:c535 Logitech, Inc. Bus 002 Device 001: ID 1d6b:0001
[Touch-packages] [Bug 1365673] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal: UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPl
** No longer affects: canonical-devices-system-image -- 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/1365673 Title: /usr/lib/arm-linux- gnueabihf/qt5/bin/qmlscene:6:qt_message_fatal:QMessageLogger::fatal: UbuntuClientIntegration::UbuntuClientIntegration:UbuntuMirClientIntegrationPlugin::create:loadIntegration Status in Qt integration with the Mir display server: Triaged Status in QT Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Incomplete Status in qtmir package in Ubuntu RTM: Triaged Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding qtdeclarative-opensource-src. This problem was most recently seen with version 5.3.0-3ubuntu10, the problem page at https://errors.ubuntu.com/problem/4618cad07e610ca3c59a3e07c582e963d4780359 contains more details. steps to reproduce: run the lrt switch test 1. open a bunch of apps 2. swipe the screen to show the app selector 3. pick an app at random 4. swipe the screen again to show the app selector 5. pick an app at random 6. repeat steps 2-5 until crash shows in /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1365673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421560] Re: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service'
** Bug watch added: Debian Bug tracker #747568 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747568 ** Also affects: rtkit (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747568 Importance: Unknown Status: Unknown ** Changed in: rtkit (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1421560 Title: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' Status in rtkit package in Ubuntu: Triaged Status in rtkit package in Debian: Unknown Bug description: booted with systemd-sysv seen into syslog: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-8ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0 Uname: Linux 3.19.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Fri Feb 13 09:19:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-5-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1421560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352251] Re: Reverse trust prompt hosting
Explaining per kgunn's request: What we have currently is: whatever initiates a trusted session provides a PID of the process it wants to open the prompt on. The problem there is that trusted helpers need not necessarily know what that PID should be, because the request might come from a scope, which has no UI. Currently the helpers just cheat by going `pidof unity8-dash` and open the session with that. In the general case it's fine because apps interact with trusted helpers directly, so the helpers can identify the connecting PID (with the exception that upcoming multi-surface support will somewhat break this, as the helper has no way to uniquely identify the surface to relate the session to). What we need is for the trusted broker, that scope-registry is, to be able to create a non-spoofable relation between whatever surface displays the data for a particular scope, and pass it down to the scope, which will then pass it to trusted helpers. The exact solution is not clear yet. In addition, somewhat off-topic, we want to add an optional type and metadata or geometry arguments for a trusted prompt, to allow per- type transitions (immediate use case - media player as trusted prompt should grow from a thumbnail to fullscreen). -- 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/1352251 Title: Reverse trust prompt hosting Status in Qt integration with the Mir display server: Triaged Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: Triaged Bug description: In order to keep continuity, keeping this original bug rather than spawning a new one. new description: currently non ui process are asking for trust prompts from related focused ui's, example scopes ask for dash to host a prompt. however, it needs to be the other way around, with the ui process having a list of pid's that it can host for. original description: On the phone, a splash screen is shown as soon as QGuiApplication is instantiated; however, a QWindow might be created much later, or not be created at all. We have for example a D-Bus service (ubuntu-system-settings-online-accounts) which is a QGuiApplication, but creates QWindows only as client requests arrive. In the common case, this works fine because the service is generally started when a window needs to be displayed, but we are now preparing for implementing trust session support, and that would require either this bug to be fixed, or a deeper refactoring of our code. see below, that the original description was simply incorrectly using the default socket, instead of the trust socket. the default socket causes the splash screen, whereas the trust socket won't To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1352251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421661] Re: The applicationName documentation doesn't state that it define the gettext domain
** Branch linked: lp:~seb128/ubuntu-ui-toolkit/gettext-application-name -- 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/1421661 Title: The applicationName documentation doesn't state that it define the gettext domain Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: That's an useful information and should probably be mentioned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421661] [NEW] The applicationName documentation doesn't state that it define the gettext domain
Public bug reported: That's an useful information and should probably be mentioned ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1421661 Title: The applicationName documentation doesn't state that it define the gettext domain Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: That's an useful information and should probably be mentioned To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421661/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1211274] Re: xcb_wait_for_reply deadlock
Thanks for your bug report. Is this still an issue? Have you tried it in a later Ubuntu release / with a more recent version of libxcb (the report was against 1.8.1-2ubuntu2.1)? ** Changed in: libxcb (Ubuntu) Status: New = Incomplete ** Changed in: libxcb (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1211274 Title: xcb_wait_for_reply deadlock Status in libxcb package in Ubuntu: Incomplete Bug description: I have a Qt application which hangs in startup. Stack trace: (gdb) bt #0 0xb77b5424 in __kernel_vsyscall () #1 0xb3d2084b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0xb2a1337b in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1 #3 0xb2a14b40 in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1 #4 0xb2a14e07 in xcb_wait_for_reply () from /usr/lib/i386-linux-gnu/libxcb.so.1 #5 0xb2a3bd0b in xcb_glx_query_version_reply () from /usr/lib/i386-linux-gnu/libxcb-glx.so.0 #6 0xa08a5740 in ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so #7 0xa08a8b9a in ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so #8 0xa08aa2f9 in ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so #9 0xa08bb1f9 in ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so #10 0xb41f57f9 in ?? () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5 #11 0xb41fccf4 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5 #12 0xb41fd704 in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5 #13 0xb482bd4b in QApplicationPrivate::createEventDispatcher() () from /usr/lib/i386-linux-gnu/libQt5Widgets.so.5 #14 0xb3f46972 in QCoreApplication::init() () from /usr/lib/i386-linux-gnu/libQt5Core.so.5 #15 0xb3f469f9 in QCoreApplication::QCoreApplication(QCoreApplicationPrivate) () from /usr/lib/i386-linux-gnu/libQt5Core.so.5 #16 0xb41fe12a in QGuiApplication::QGuiApplication(QGuiApplicationPrivate) () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5 #17 0xb47d8de8 in QApplication::QApplication(int, char**, int) () from /usr/lib/i386-linux-gnu/libQt5Widgets.so.5 Google shows other reports about xcb_wait_for_reply deadlocking. This happens when starting the application from .xsession file using nodm display manager. Starting the app from an x terminal works so i believe this is some kind of timing issue / race condition. The app in question is properietary so i cannot supply it to reproduce the issue, sorry. Ubuntu version is Ubuntu 13.04 x86_32 with updates installed. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libxcb1 1.8.1-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 Uname: Linux 3.8.0-28-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.88 Wed Mar 27 14:31:12 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 CheckboxSubmission: 5411b7083f2413511daec522a712c016 CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: None Date: Mon Aug 12 14:09:50 2013 DistUpgraded: 2013-05-22 13:40:23,672 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GT216M [NVS 5100M] [10de:0a2c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2011-06-14 (790 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) JockeyStatus: kmod:nvidia_310_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_313_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304 - nvidia_304 (Proprietary, Enabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_310 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: Hewlett-Packard HP EliteBook 8540p MarkForUpload: True PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia
[Touch-packages] [Bug 1291455] Re: Screen and input should be disabled with proximity sensor when on greeter
** Changed in: canonical-devices-system-image Assignee: Kevin Gunn (kgunn) = Bill Filler (bfiller) -- 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/1291455 Title: Screen and input should be disabled with proximity sensor when on greeter Status in the base for Ubuntu mobile products: Confirmed Status in powerd package in Ubuntu: New Status in telepathy-ofono package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: Steps to reproduce: * suspend your device * cover the proximity sensor (top left on mako) * call the phone Expecte result: * screen does not light up until you uncover the proximity sensor Current result: * screen lights up and you can answer the call This results in butt/pocket calls... ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.84+14.04.20140306-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Wed Mar 12 13:14:37 2014 InstallationDate: Installed on 2014-03-12 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140312) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1291455/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384374] Re: Dash pauses/stutters during scope switching left/right
while we may not have a solution this remains a critical issue I am surprised there is no way to speed at least the perception of the scope loading or offload to other threads as discussed ** Changed in: canonical-devices-system-image Milestone: ww09-2015 = None -- 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/1384374 Title: Dash pauses/stutters during scope switching left/right Status in the base for Ubuntu mobile products: New Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: New Bug description: Dash pauses/stutters during scope switching left/right. Watching the log: tail -f ~/.cache/upstart/unity8-dash.log I can see error messages flood out whenever the dash pauses/stutters during left/right swipes: file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1384374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421653] Re: Changing ItemSelector model sets currentIndex to 0
** Description changed: Repro: 1. Have expanded ItemSelector 2. Set currentIndex to something other than 0 by tapping the second or third item in an ItemSelector What happens: currentIndex is sat to 0, i.e. the selected item is changed What should have happened: currentIndex should have remained Example: http://pastebin.ubuntu.com/10205382/ + + Might be invalid/unfixable, and that's ok, but it might deserve a note + in the docs? -- 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/1421653 Title: Changing ItemSelector model sets currentIndex to 0 Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Repro: 1. Have expanded ItemSelector 2. Set currentIndex to something other than 0 by tapping the second or third item in an ItemSelector What happens: currentIndex is sat to 0, i.e. the selected item is changed What should have happened: currentIndex should have remained Example: http://pastebin.ubuntu.com/10205382/ Might be invalid/unfixable, and that's ok, but it might deserve a note in the docs? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420002] [NEW] Sync fails with no way to recover after token expires
You have been subscribed to a public bug: I have two accounts on my krillin which I sync to google. Opened calendar and hit 'sync' button. Navigated around a bit in the app, it died (will file separate bug for that) and I restarted it. Tried syncing again. Got a sync fail popup. ubuntu-touch/ubuntu-rtm/14.09-proposed 231. ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: sync-monitor 0.1+15.04.20150127~rtm-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Feb 9 21:11:51 2015 InstallationDate: Installed on 2015-02-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150209-030204) SourcePackage: sync-monitor UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: canonical-devices-system-image Importance: High Assignee: Bill Filler (bfiller) Status: In Progress ** Affects: sync-monitor Importance: High Status: In Progress ** Affects: signon-plugin-oauth2 (Ubuntu) Importance: High Assignee: Alberto Mardegan (mardy) Status: In Progress ** Affects: sync-monitor (Ubuntu) Importance: High Assignee: Renato Araujo Oliveira Filho (renatofilho) Status: New ** Affects: sync-monitor (Ubuntu RTM) Importance: High Status: New ** Tags: apport-bug armhf calendar utopic ww09 -- Sync fails with no way to recover after token expires https://bugs.launchpad.net/bugs/1420002 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon-plugin-oauth2 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1020210] Re: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption
Chris, please find the updated debdiff. ** Patch removed: precise_eglibc_2.15-0ubuntu10.11.debdiff https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1020210/+attachment/4317996/+files/precise_eglibc_2.15-0ubuntu10.11.debdiff ** Patch added: precise_eglibc_2.15-0ubuntu10.11.debdiff https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1020210/+attachment/4318758/+files/precise_eglibc_2.15-0ubuntu10.11.debdiff -- 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/1020210 Title: Race condition using ATOMIC_FASTBINS in _int_free causes crash or heap corruption Status in Embedded GLIBC: Fix Released Status in eglibc package in Ubuntu: Fix Released Status in eglibc source package in Precise: In Progress Bug description: [Impact] * This bug is likely to cause a crash with a SEGV in multithreading applications doing many memory deallocations with ATOMIC_FASTBINS feature enabled. [Test Case] * Since this is a race condition issue there is no simple path of reproducing it, however one could try to follow the instructions in the upstream bug (https://www.sourceware.org/bugzilla/show_bug.cgi?id=15073): https://www.sourceware.org/bugzilla/attachment.cgi?id=7331 [Regression Potential] * This issue has been merged upstream with no further issues reported. [Other Info] * Original bug description: We have an application which makes heavy allocation and de-allocation demands from multiple threads. We run this application continuously on many servers, and once every several CPU months or years, we were getting a crash in _int_free that did not look like vanilla heap corruption. I believe I have narrowed it down to a race condition in _int_free due to the ATOMIC_FASTBINS feature. Basically, in the lockless FASTBIN _int_free path, a chunk is pulled into a local variable with the intent to add it to the fastbins list. However, the heap consolidation/trim code can race with this, and can coalesce the entire block and/or give it back to the OS before _int_free has a chance to try and store it into the fastbins list. The problem is very challenging to reproduce in situ, but using gdb I have a recipe which demonstrates the crash 100% of the time on my 12.04 x64 system running eglibc 2.15. It relies on malloc_trim, although in our in situ data, the consolidation is triggered as a result of a normal free. malloc_trim is just easier to control. While I am not a glibc developer, I could not see any easy ways to fix the situation shy of disabling ATOMIC_FASTBINS. I am attaching the reproduction source. Other pertinent information follows: jpieper@calculon:~/downloads$ lsb_release -rd Description:Ubuntu 12.04 LTS Release:12.04 jpieper@calculon:~/downloads$ apt-cache policy libc6 libc6: Installed: 2.15-0ubuntu10 Candidate: 2.15-0ubuntu10 Version table: *** 2.15-0ubuntu10 0 500 http://us.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages 100 /var/lib/dpkg/status What I expect: I expect the attached application, when run using the gdb script in the comments, to complete with no failures. What happened: A SIGSEGV after the final continue. To manage notifications about this bug go to: https://bugs.launchpad.net/eglibc/+bug/1020210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415256] Re: Errors entering single-user mode; hang going back to multiuser
** Changed in: upstart (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1415256 Title: Errors entering single-user mode; hang going back to multiuser Status in upstart package in Ubuntu: Confirmed Bug description: Several wrong-looking messages appear when entering single-user mode, and when ^D is typed to exit the single-user shell, the system hangs trying to resume multi-user mode (the graphical login never apperas, nor does the virtual-terminal login prompt). I observed this testing with virtualbox. Haven't tried bare metal. I will attach two screenshots, one showing the entry into single-user mode, the second showing the attempted exit. But the bits which seemed relevant are reproduced below; STEPS TO REPRODUCE: 1. Log in as root from a virtual console (in virtualbox: host-F1 and log in) 2. $ shutdown now # documented to enter single-user mode /lib/init/init-d-script: 2: /etc/default/whoopsie: [General]: not found ... ModemManager ... Caught signal, shutting down... ModemManager ... Could not acquire the 'org.freedesktop.Modemmanger1' service name 3. When prompted, enter root password ... 4. ^D (or type 'exit') ... /lib/init/init-d-script: 2: /etc/default/shoopsie: [General]: not found systemd-logind: Failed to start user service: Unknown unit: user@108.service systemd-logind: Failed to start user service: Unknown unit: user@0.service systemd-logind: Failed to start user service: Unknown unit: user@1000.service * Starting shoopsie shoopsie[fail] (HANGS) ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: upstart 1.13.2-0ubuntu7 ProcVersionSignature: Ubuntu 3.18.0-11.12-generic 3.18.3 Uname: Linux 3.18.0-11-generic x86_64 ApportVersion: 2.15.1-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 27 15:46:46 2015 InstallationDate: Installed on 2015-01-02 (25 days ago) InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150102) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.18.0-11-generic root=UUID=96d674cd-12fb-4ad1-8d76-cffb545e6256 ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: No upgrade log present (probably fresh install) UpstartBugCategory: System UpstartRunningSessionVersion: upstart 1.13.2 UpstartRunningSystemVersion: init (upstart 1.13.2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1415256/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421653] [NEW] Changing ItemSelector model sets currentIndex to 0
Public bug reported: Repro: 1. Have expanded ItemSelector 2. Set currentIndex to something other than 0 by tapping the second or third item in an ItemSelector What happens: currentIndex is sat to 0, i.e. the selected item is changed What should have happened: currentIndex should have remained Example: http://pastebin.ubuntu.com/10205382/ ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1421653 Title: Changing ItemSelector model sets currentIndex to 0 Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: Repro: 1. Have expanded ItemSelector 2. Set currentIndex to something other than 0 by tapping the second or third item in an ItemSelector What happens: currentIndex is sat to 0, i.e. the selected item is changed What should have happened: currentIndex should have remained Example: http://pastebin.ubuntu.com/10205382/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421653/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411748] Re: [Arale] News aggregator scope has a white scope background in cards
** Changed in: unity8 (Ubuntu RTM) Milestone: 14.09-ota-1 = None ** Changed in: unity8 (Ubuntu RTM) Assignee: Michał Sawicz (saviq) = (unassigned) -- 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/1411748 Title: [Arale] News aggregator scope has a white scope background in cards Status in the base for Ubuntu mobile products: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Invalid Bug description: Open the news aggregator in Arale. Go to the section national news A white card background appears This seems to be only impacting vertical-jounal cards. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393008] Re: Horizontal cards with summary don't get backgrounds
** Changed in: unity8 (Ubuntu RTM)
Milestone: None = 14.09-ota-1
** Changed in: unity8 (Ubuntu RTM)
Status: New = Triaged
** Changed in: unity8 (Ubuntu RTM)
Importance: Undecided = High
--
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/1393008
Title:
Horizontal cards with summary don't get backgrounds
Status in the base for Ubuntu mobile products:
In Progress
Status in Ubuntu App Developer site:
Invalid
Status in unity8 package in Ubuntu:
Fix Released
Status in unity8 package in Ubuntu RTM:
Triaged
Bug description:
If I change the WEATHER_TEMPLATE in the scopes example to:
const static string WEATHER_TEMPLATE =
R(
{
schema-version: 1,
template: {
category-layout: carousel,
card-layout: horizontal,
card-size: small,
card-background:color:///#0F0F0F
},
components: {
title: title,
art : {
field: art
},
subtitle: subtitle,
summary: summary
}
}
);
The cards are placed in carousel style, but the background color is
simply omitted, the color of the card stays black.
If the card-layout is changed from horizontal to vertical, the
color is there, and the cards in a carousel style, but the bottom 10%
of the cards seem to be clipped. (Screenshot attached)
This is my first bug report ever, so please let me know what else I
should add, or if I am at the right place at all.
Reported from: http://developer.ubuntu.com/scopes/cookbook/
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1393008/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421664] [NEW] Shouldn't run on desktop configurations
Public bug reported: Currently the upstart job tries to run mtp on desktop/configurations without mtp support, that's wrong (especially that the server hits an abort on the missing device which spins apport and lead to slow systems) ** Affects: mtp (Ubuntu) Importance: High Status: New ** Tags: unity8-desktop ** Changed in: mtp (Ubuntu) Importance: Undecided = High ** Tags added: unity8-desktop -- 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/1421664 Title: Shouldn't run on desktop configurations Status in mtp package in Ubuntu: New Bug description: Currently the upstart job tries to run mtp on desktop/configurations without mtp support, that's wrong (especially that the server hits an abort on the missing device which spins apport and lead to slow systems) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1421664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408263] Re: Edge gestures still get lost
I saw this recently where I lost left and right edge gestures, but top and bottom seemed to work. It was as the reporter described-- happened after being in my pocket. Only recourse was to reboot. -- 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/1408263 Title: Edge gestures still get lost Status in android package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: There are still cases where edge gestures are lost. Over the christmas holidays It happened about 5 times to me (in 2 weeks). Only way to recover is to reboot the phone. It always happened while the phone was in my pocket. When pulling it out of the pocket the edge gestures (launcher and right edge) were gone. This is most likely related to random taps on the screen, maybe in combination with the display toggling on/off. Haven't found a way yet to manually trigger it. Will keep on trying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1408263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421671] [NEW] Implement wifi hotspot status
Public bug reported: Implement the wifi hotspot status in the indicator per the [1] spec 1. https://wiki.ubuntu.com/Networking#hotspot ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1421671 Title: Implement wifi hotspot status Status in indicator-network package in Ubuntu: New Bug description: Implement the wifi hotspot status in the indicator per the [1] spec 1. https://wiki.ubuntu.com/Networking#hotspot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1421671/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1416048] Re: Expected to be able to pause a video by tapping on anywhere of the video
It's up to the design team to decide on the desired functionality here. -- 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/1416048 Title: Expected to be able to pause a video by tapping on anywhere of the video Status in Media Player App: Confirmed Status in Ubuntu UX bugs: New Status in mediaplayer-app package in Ubuntu: New Bug description: Tapping anywhere on the video that is playing should pause it and vice versa. To manage notifications about this bug go to: https://bugs.launchpad.net/mediaplayer-app/+bug/1416048/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421559] Re: Should be able to silence alarm using power button
** Description changed: Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: - You need to turn on screen, swipe, enter pin, press OK on alarm + You need to turn on screen, press OK on alarm What should have happened: I should be able to silence the alarm using the power button—like on iOS. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class. Removing the phone from my pocket, swiping, unlocking and - dismissing the alarm, always takes about 3-4 rings. People are starting - to notice. + dismissing the alarm, always takes about 3-4 rings. Related to bug 1340329. ** Description changed: + krillin @rtm #16 + Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, press OK on alarm What should have happened: I should be able to silence the alarm using the power button—like on iOS. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class. Removing the phone from my pocket, swiping, unlocking and dismissing the alarm, always takes about 3-4 rings. Related to bug 1340329. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1421559 Title: Should be able to silence alarm using power button Status in Clock application for Ubuntu devices: New Status in indicator-datetime package in Ubuntu: New Bug description: krillin @rtm #16 Reproduce: 1. Set alarm 2. Let alarm go off, but do not turn it off immediately—do not touch the phone surface, wait until the screen goes black 3. Try to disable alarm What happens: You need to turn on screen, press OK on alarm What should have happened: I should be able to silence the alarm using the power button—like on iOS. Rationale: I set two alarms on weekdays, one at 07:07 and one at 09:07. When I wake up at 07:07 and go to school, the 09:07 alarm goes off during class. Removing the phone from my pocket, swiping, unlocking and dismissing the alarm, always takes about 3-4 rings. Related to bug 1340329. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1421559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418460] Re: libconnectivity-qt1-dev un-installable in click chroot
@Dan Is it stable enough to install vivid chroot to build apps ( for store /end-user ) ? -- 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/1418460 Title: libconnectivity-qt1-dev un-installable in click chroot Status in qtcreator-plugin-ubuntu package in Ubuntu: Incomplete Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: I am unable to install libconnectivity-qt1-dev in a click chroot. It hits dependency errors starting with qtbase5-dev. The following packages have unmet dependencies: libconnectivity-qt1-dev : Depends: qtbase5-dev E: Unable to correct problems, you have held broken packages. I would have thought this package would be already installed as it's a part of the SDK connectivity api. Both Dekko and Shorts app need access to this API To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtcreator-plugin-ubuntu/+bug/1418460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372061] Re: SMS notification: time format not translatable
** Changed in: canonical-devices-system-image Milestone: ww09-2015 = ww13-2015 ** Changed in: canonical-devices-system-image Assignee: Kevin Gunn (kgunn) = Zoltan Balogh (bzoltan) -- 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/1372061 Title: SMS notification: time format not translatable Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu Translations: Triaged Status in telephony-service package in Ubuntu: Invalid Status in ubuntu-settings-components package in Ubuntu: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: In Progress Status in unity8 package in Ubuntu: In Progress Status in ubuntu-settings-components package in Ubuntu RTM: Triaged Status in ubuntu-ui-toolkit package in Ubuntu RTM: New Status in unity8 package in Ubuntu RTM: Triaged Bug description: See the attached screenshot. The time for the notification seems to be hardcoded to hh:mm - mm, d. This works well for the US, but it's not a format that is used in all other countries. In Spain, for example, the date would rather be d mm. The time format needs to be marked for translation. Not sure from which project the notifications come from, for some reason I seem to remember they were moved to u-s-s, but if it's the wrong project/package, please reassign. Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1372061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411748] Re: [Arale] News aggregator scope has a white scope background in cards
fixed in vivid ** Changed in: unity8 (Ubuntu RTM) Status: Triaged = Invalid ** Changed in: canonical-devices-system-image Status: In Progress = Fix Released ** Changed in: canonical-devices-system-image Milestone: ww09-2015 = None -- 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/1411748 Title: [Arale] News aggregator scope has a white scope background in cards Status in the base for Ubuntu mobile products: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Invalid Bug description: Open the news aggregator in Arale. Go to the section national news A white card background appears This seems to be only impacting vertical-jounal cards. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352251] Re: Reverse trust prompt hosting
** No longer affects: canonical-devices-system-image -- 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/1352251 Title: Reverse trust prompt hosting Status in Qt integration with the Mir display server: Triaged Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: Triaged Bug description: In order to keep continuity, keeping this original bug rather than spawning a new one. new description: currently non ui process are asking for trust prompts from related focused ui's, example scopes ask for dash to host a prompt. however, it needs to be the other way around, with the ui process having a list of pid's that it can host for. original description: On the phone, a splash screen is shown as soon as QGuiApplication is instantiated; however, a QWindow might be created much later, or not be created at all. We have for example a D-Bus service (ubuntu-system-settings-online-accounts) which is a QGuiApplication, but creates QWindows only as client requests arrive. In the common case, this works fine because the service is generally started when a window needs to be displayed, but we are now preparing for implementing trust session support, and that would require either this bug to be fixed, or a deeper refactoring of our code. see below, that the original description was simply incorrectly using the default socket, instead of the trust socket. the default socket causes the splash screen, whereas the trust socket won't To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1352251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418033] Re: Location service should stop updates for sessions that have been identified as stale (sigstop'd)
** Branch linked: lp:~thomas-voss/location-service/fix-1418033 -- 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/1418033 Title: Location service should stop updates for sessions that have been identified as stale (sigstop'd) Status in the base for Ubuntu mobile products: Confirmed Status in location-service package in Ubuntu: Confirmed Bug description: The heuristic might be as simple as: If providing updates to clients fails more than 10 times, stop all updates. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1418033/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421623] Re: Welcome wizard claims GPS is less accurate than wifi based location
When the Here service is enabled we also use GPS so the users choice is not Here or GPS. The message should be somehow that using Here gives a better experience. But agreed that Use GPS Only should drop the (less accurate) ** Also affects: ubuntu-system-settings (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1421623 Title: Welcome wizard claims GPS is less accurate than wifi based location Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: New Status in ubuntu-system-settings package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: First boot welcome wizard in location sections claims GPS is less accurate than network based location service from HERE. While this can be theoretically true in some insane corner case, in normal life GPS is far more accurate. To help form correct text here are main differences. GPS - more accurate, but slow to acquire fix, does not work indoors, drains battery more, no need for internet connection, does not send any data out. Network based location - almost instant to get coarse location, works indoors, accuracy depends on network coverage in the area, more power efficient, requires internet connection. To get location data about visible GSM network and wifi networks needs to be send to 3rd party server. tested on krillin vivid-proposed r107 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1421623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1384374] Re: Dash pauses/stutters during scope switching left/right
while we may not have a solution this remains a critical issue I am surprised there is no way to speed at least the perception of the scope loading or offload to other threads as discussed We've already offloaded everything we could identify, which improved the situation a lot. We now need to spend more time finding which bits still add to the UI getting blocked when scopes are queried. Just never had the time yet, so no immediate solution. -- 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/1384374 Title: Dash pauses/stutters during scope switching left/right Status in the base for Ubuntu mobile products: New Status in unity8 package in Ubuntu: Triaged Status in unity8 package in Ubuntu RTM: New Bug description: Dash pauses/stutters during scope switching left/right. Watching the log: tail -f ~/.cache/upstart/unity8-dash.log I can see error messages flood out whenever the dash pauses/stutters during left/right swipes: file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height file:///usr/lib/arm-linux-gnueabihf/unity8/qml/Dash/createCardComponent:120:1: QML Label: Binding loop detected for property height To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1384374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420002] Re: Sync fails with no way to recover after token expires
I've been debugging the issue here, according to the steps (and the
logs) which Renato provided me with.
So, a problem arises if the access token has expires and the refresh
token (which can be used to request a new access token without UI
interactions) is still valid, but the client application has been
revoked access from https://myaccount.google.com/ (section Connected
apps and services). In that case, here's the logs:
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: oauth2plugin.cpp 111
OAuth2Plugin :
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: oauth2plugin.cpp 206
respondWithStoredToken : Stored token is expired
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: oauth2plugin.cpp 586
refreshOAuth2Token : 1/
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: oauth2plugin.cpp 598
sendOAuth2PostRequest :
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: oauth2plugin.cpp 623
sendOAuth2PostRequest : Query string = QUrl(
?grant_type=refresh_tokenrefresh_token=1/client_id=759250720802-4sii0me9963n9fdqdmi7cepn6ub8luoh.apps.googleusercontent.comclient_secret=juFngKUcuhB7IRQqHtSLavqJ
)
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: base-plugin.cpp 112
postRequest : Posting request: QUrl(
https://accounts.google.com/o/oauth2/token; )
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]:
../../../../src/remotepluginprocess/remotepluginprocess.cpp 496 startTask
operation is completed
Feb 13 15:02:16 ubuntu-phablet signonpluginprocess[13128]: base-plugin.cpp 152
handleNetworkError : error signal received: 302
Feb 13 15:02:16 ubuntu-phablet signonpluginprocess[13128]: base-plugin.cpp 167
handleNetworkError : Contents: {#012 error : invalid_grant,#012
error_description : Token has been revoked.#012}
So, this is a but in signon-plugin-oauth2, which should discard the
refresh token and try the authentication again if some error happens
while using the refresh token.
** Project changed: ubuntu-system-settings-online-accounts = signon-
plugin-oauth2 (Ubuntu)
** Changed in: signon-plugin-oauth2 (Ubuntu)
Status: New = In Progress
** Changed in: signon-plugin-oauth2 (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 signon-plugin-oauth2 in
Ubuntu.
https://bugs.launchpad.net/bugs/1420002
Title:
Sync fails with no way to recover after token expires
Status in the base for Ubuntu mobile products:
In Progress
Status in Sync monitor for Ubuntu Touch:
In Progress
Status in signon-plugin-oauth2 package in Ubuntu:
In Progress
Status in sync-monitor package in Ubuntu:
New
Status in sync-monitor package in Ubuntu RTM:
New
Bug description:
I have two accounts on my krillin which I sync to google.
Opened calendar and hit 'sync' button. Navigated around a bit in the app, it
died (will file separate bug for that) and I restarted it. Tried syncing again.
Got a sync fail popup.
ubuntu-touch/ubuntu-rtm/14.09-proposed 231.
ProblemType: Bug
DistroRelease: Ubuntu RTM 14.09
Package: sync-monitor 0.1+15.04.20150127~rtm-0ubuntu1
Uname: Linux 3.4.67 armv7l
ApportVersion: 2.14.7-0ubuntu8
Architecture: armhf
Date: Mon Feb 9 21:11:51 2015
InstallationDate: Installed on 2015-02-09 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf
(20150209-030204)
SourcePackage: sync-monitor
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420002/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388107] Re: Add Catalan layout
** Description changed: The keyboard should support a dedicated layout and predictive input for - Catalan. + Catalan as one of the target languages for the first phones. + + The layout is already available on vivid, but would need to be added to + RTM. -- 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/1388107 Title: Add Catalan layout Status in the base for Ubuntu mobile products: Fix Released Status in Ubuntu Keyboard: Fix Released Status in ubuntu-keyboard package in Ubuntu: Fix Released Status in ubuntu-keyboard package in Ubuntu RTM: Fix Released Bug description: The keyboard should support a dedicated layout and predictive input for Catalan as one of the target languages for the first phones. The layout is already available on vivid, but would need to be added to RTM. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1388107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334855] Re: [design] Can't use toolbar while notifications on screen
** Changed in: unity8 (Ubuntu RTM) Status: New = Triaged ** Changed in: unity8 (Ubuntu RTM) Milestone: None = 14.09-ota-1 ** Changed in: unity8 (Ubuntu RTM) Importance: Undecided = Medium -- 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/1334855 Title: [design] Can't use toolbar while notifications on screen Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Triaged Bug description: With notifications on the screen, they're overlayed on top of the top toolbar, as such I can't tap the back button. To replicate. Open system settings - accounts Sign in to twitter Wait while tweet notifications come in Navigate anywhere in system settings, such as updates. Note you can't go back while the notifications are on screen. See screenshot, back button obscured. --- Desired resolution: - All types of notifications should be dismissable To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1334855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316796] Re: systemd-fsck lacks integration for fsck progress output to plymouth, the way mountall handled it
I merged Didier's patches into our package now, as they won't make it into 219 any more (bug fixes only), and the 219 release itself is still some weeks out, so that won't make it into our feature freeze either. Great work, thanks Didier! I noticed that Control-C doesn't work to interrupt the check, but the aggregation and plymouth feedback works very nice now. ** Changed in: systemd (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1316796 Title: systemd-fsck lacks integration for fsck progress output to plymouth, the way mountall handled it Status in systemd package in Ubuntu: Fix Committed Bug description: in 14.04 LTS mountall has excellent integration of fsck progress output for both ubuntu-logo and details plugins. systemd-fsck doesn't appear to have such integration. =( shame To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1316796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420934] Re: [online-accounts] re-authenticating an account does not work
I've been debugging the issue here, according to the steps (and the
logs) which Renato provided me with.
So, a problem arises if the access token has expires and the refresh
token (which can be used to request a new access token without UI
interactions) is still valid, but the client application has been
revoked access from https://myaccount.google.com/ (section Connected
apps and services). In that case, here's the logs:
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: oauth2plugin.cpp 111
OAuth2Plugin :
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: oauth2plugin.cpp 206
respondWithStoredToken : Stored token is expired
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: oauth2plugin.cpp 586
refreshOAuth2Token : 1/
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: oauth2plugin.cpp 598
sendOAuth2PostRequest :
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: oauth2plugin.cpp 623
sendOAuth2PostRequest : Query string = QUrl(
?grant_type=refresh_tokenrefresh_token=1/client_id=759250720802-4sii0me9963n9fdqdmi7cepn6ub8luoh.apps.googleusercontent.comclient_secret=juFngKUcuhB7IRQqHtSLavqJ
)
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]: base-plugin.cpp 112
postRequest : Posting request: QUrl(
https://accounts.google.com/o/oauth2/token; )
Feb 13 15:02:15 ubuntu-phablet signonpluginprocess[13128]:
../../../../src/remotepluginprocess/remotepluginprocess.cpp 496 startTask
operation is completed
Feb 13 15:02:16 ubuntu-phablet signonpluginprocess[13128]: base-plugin.cpp 152
handleNetworkError : error signal received: 302
Feb 13 15:02:16 ubuntu-phablet signonpluginprocess[13128]: base-plugin.cpp 167
handleNetworkError : Contents: {#012 error : invalid_grant,#012
error_description : Token has been revoked.#012}
So, this is a but in signon-plugin-oauth2, which should discard the
refresh token and try the authentication again if some error happens
while using the refresh token.
** Package changed: ubuntu-system-settings-online-accounts (Ubuntu) =
signon-plugin-oauth2 (Ubuntu)
** Changed in: signon-plugin-oauth2 (Ubuntu)
Assignee: (unassigned) = Alberto Mardegan (mardy)
** No longer affects: ubuntu-system-settings-online-accounts
** Changed in: signon-plugin-oauth2 (Ubuntu)
Status: New = In Progress
** Package changed: ubuntu-system-settings-online-accounts (Ubuntu RTM)
= signon-plugin-oauth2 (Ubuntu RTM)
** Changed in: signon-plugin-oauth2 (Ubuntu RTM)
Status: New = Confirmed
** Changed in: signon-plugin-oauth2 (Ubuntu RTM)
Assignee: (unassigned) = Alberto Mardegan (mardy)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to signon-plugin-oauth2 in
Ubuntu.
https://bugs.launchpad.net/bugs/1420934
Title:
[online-accounts] re-authenticating an account does not work
Status in the base for Ubuntu mobile products:
Confirmed
Status in signon-plugin-oauth2 package in Ubuntu:
In Progress
Status in signon-plugin-oauth2 package in Ubuntu RTM:
Confirmed
Bug description:
After a online account token became invalid we should use the function
AccountService.authenticate to re-validate the account. But is is
not working for google accounts.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1420934/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421672] [NEW] Overwrite the gettext to MainView.applicationName if already set
Public bug reported: That leaded to issue in ubuntu-system-settings. Our code calls textdomain() directly, the domain was then changed to another wrong value because MainView's overwrites it to be applicationName. The main reason why we did the call ourself was because the MainView documentation doesn't document that it's doing it for you (opened bug #1421661 about that), but still if some code decide to write a specific value it should probably be respected and not overwrited. Suggested change, set the textdomain only if that has not been done yet ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1421672 Title: Overwrite the gettext to MainView.applicationName if already set Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: That leaded to issue in ubuntu-system-settings. Our code calls textdomain() directly, the domain was then changed to another wrong value because MainView's overwrites it to be applicationName. The main reason why we did the call ourself was because the MainView documentation doesn't document that it's doing it for you (opened bug #1421661 about that), but still if some code decide to write a specific value it should probably be respected and not overwrited. Suggested change, set the textdomain only if that has not been done yet To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1421672/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1211274] Re: xcb_wait_for_reply deadlock
This bug is 1.5 years old. I don't even remember what i was doing back then. I suppose it can be closed if no-one still suffers from it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libxcb in Ubuntu. https://bugs.launchpad.net/bugs/1211274 Title: xcb_wait_for_reply deadlock Status in libxcb package in Ubuntu: Incomplete Bug description: I have a Qt application which hangs in startup. Stack trace: (gdb) bt #0 0xb77b5424 in __kernel_vsyscall () #1 0xb3d2084b in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/i386-linux-gnu/libpthread.so.0 #2 0xb2a1337b in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1 #3 0xb2a14b40 in ?? () from /usr/lib/i386-linux-gnu/libxcb.so.1 #4 0xb2a14e07 in xcb_wait_for_reply () from /usr/lib/i386-linux-gnu/libxcb.so.1 #5 0xb2a3bd0b in xcb_glx_query_version_reply () from /usr/lib/i386-linux-gnu/libxcb-glx.so.0 #6 0xa08a5740 in ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so #7 0xa08a8b9a in ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so #8 0xa08aa2f9 in ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so #9 0xa08bb1f9 in ?? () from /usr/lib/i386-linux-gnu/qt5/plugins/platforms/libqxcb.so #10 0xb41f57f9 in ?? () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5 #11 0xb41fccf4 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5 #12 0xb41fd704 in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5 #13 0xb482bd4b in QApplicationPrivate::createEventDispatcher() () from /usr/lib/i386-linux-gnu/libQt5Widgets.so.5 #14 0xb3f46972 in QCoreApplication::init() () from /usr/lib/i386-linux-gnu/libQt5Core.so.5 #15 0xb3f469f9 in QCoreApplication::QCoreApplication(QCoreApplicationPrivate) () from /usr/lib/i386-linux-gnu/libQt5Core.so.5 #16 0xb41fe12a in QGuiApplication::QGuiApplication(QGuiApplicationPrivate) () from /usr/lib/i386-linux-gnu/libQt5Gui.so.5 #17 0xb47d8de8 in QApplication::QApplication(int, char**, int) () from /usr/lib/i386-linux-gnu/libQt5Widgets.so.5 Google shows other reports about xcb_wait_for_reply deadlocking. This happens when starting the application from .xsession file using nodm display manager. Starting the app from an x terminal works so i believe this is some kind of timing issue / race condition. The app in question is properietary so i cannot supply it to reproduce the issue, sorry. Ubuntu version is Ubuntu 13.04 x86_32 with updates installed. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: libxcb1 1.8.1-2ubuntu2.1 ProcVersionSignature: Ubuntu 3.8.0-28.41-generic 3.8.13.5 Uname: Linux 3.8.0-28-generic i686 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86 Kernel Module 304.88 Wed Mar 27 14:31:12 PDT 2013 GCC version: gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu8.3 Architecture: i386 CheckboxSubmission: 5411b7083f2413511daec522a712c016 CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,workarounds,scale,expo,ezoom] CompositorRunning: None Date: Mon Aug 12 14:09:50 2013 DistUpgraded: 2013-05-22 13:40:23,672 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: NVIDIA Corporation GT216M [NVS 5100M] [10de:0a2c] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2011-06-14 (790 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) JockeyStatus: kmod:nvidia_310_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_313_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_304 - nvidia_304 (Proprietary, Enabled, Not in use) kmod:nvidia_304_updates - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) kmod:nvidia_310 - NVIDIA binary Xorg driver, kernel module and VDPAU library (Proprietary, Disabled, Not in use) MachineType: Hewlett-Packard HP EliteBook 8540p MarkForUpload: True PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-28-generic root=UUID=debfbf8b-faee-4fef-887f-aaa61947d6d2 ro crashkernel=384M-2G:64M,2G-:128M quiet splash SourcePackage: libxcb
[Touch-packages] [Bug 1408263] Re: Edge gestures still get lost
I might also note-- in both cases recently I needed to make a call; thankfully it was not an emergency. -- 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/1408263 Title: Edge gestures still get lost Status in android package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: There are still cases where edge gestures are lost. Over the christmas holidays It happened about 5 times to me (in 2 weeks). Only way to recover is to reboot the phone. It always happened while the phone was in my pocket. When pulling it out of the pocket the edge gestures (launcher and right edge) were gone. This is most likely related to random taps on the screen, maybe in combination with the display toggling on/off. Haven't found a way yet to manually trigger it. Will keep on trying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1408263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408263] Re: Edge gestures still get lost
I should've mentioned: $ system-image-cli -i current build number: 194 device name: mako channel: ubuntu-touch/ubuntu-rtm/14.09-proposed last update: 2015-02-11 15:34:27 version version: 194 version ubuntu: 20150211.1 version device: 20150116 version custom: mako-1.1 I too don't have a consistent reproducer, but can keep trying to find one. -- 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/1408263 Title: Edge gestures still get lost Status in android package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Invalid Bug description: There are still cases where edge gestures are lost. Over the christmas holidays It happened about 5 times to me (in 2 weeks). Only way to recover is to reboot the phone. It always happened while the phone was in my pocket. When pulling it out of the pocket the edge gestures (launcher and right edge) were gone. This is most likely related to random taps on the screen, maybe in combination with the display toggling on/off. Haven't found a way yet to manually trigger it. Will keep on trying. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/android/+bug/1408263/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421560] Re: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service'
** Changed in: rtkit (Ubuntu) Status: Triaged = Fix Committed ** Changed in: rtkit (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) ** Changed in: rtkit (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1421560 Title: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' Status in rtkit package in Ubuntu: Fix Committed Status in rtkit package in Debian: Unknown Bug description: booted with systemd-sysv seen into syslog: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-8ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0 Uname: Linux 3.19.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Fri Feb 13 09:19:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-5-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1421560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413791] Re: Left swipe/BFB should reset search string
Ubuntu UX guys: ping? -- 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/1413791 Title: Left swipe/BFB should reset search string Status in Ubuntu UX bugs: New Status in unity8 package in Ubuntu: Triaged Bug description: device nexus 4 mako os Ubuntu 15.04 (r73) I love the left swipe, being able to go back to the main menu by doing a full swipe to the left is great. However my list of apps has considerably increased \o/ and i usually search them via the search button and this is where the problem lies. A full left swipe does not bring me back to the main menu but to the last searched app if i opened my app through the search menu As an example Step 1 go to apps scope on main menu step 2 search music app via the search button ( type music) step 3 open music app step 4 do a full left swippe I should expect to being brought back to app scope. == Full left swipe brings me back to results of step 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1413791/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421664] Re: Shouldn't run on desktop configurations
** Branch linked: lp:~mathieu-tl/mtp/lp1421664 -- 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/1421664 Title: Shouldn't run on desktop configurations Status in mtp package in Ubuntu: New Bug description: Currently the upstart job tries to run mtp on desktop/configurations without mtp support, that's wrong (especially that the server hits an abort on the missing device which spins apport and lead to slow systems) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mtp/+bug/1421664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388235] Re: [indicators] Battery icon turns red at 30%
** Branch linked: lp:~charlesk/indicator-power/lp-1388235-use-new- battery-icons-rtm-14.09 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1388235 Title: [indicators] Battery icon turns red at 30% Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Triaged Status in indicator-power package in Ubuntu: Fix Released Status in ubuntu-themes package in Ubuntu: Fix Released Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1388235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421320] Re: Keyboard text input: letters get swapped/garbled while running on video hangout
Please run apport-collect. Also which browser are you using? Can you try with another browser? ** Also affects: unity (Ubuntu) Importance: Undecided Status: New ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1421320 Title: Keyboard text input: letters get swapped/garbled while running on video hangout Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: This happens on Vivid on My MacBookPro. Happens when I am on a video hangout with 6-7 people and I try to take notes into a Google Doc in another window. The letters I hit seem to be swapped. E.g. 'specific' -- 'specifci' 'review' -- 'erview' 'installed' -- 'nistalled' etc. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1421320/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393008] Re: Horizontal cards with summary don't get backgrounds
** Branch linked: lp:~unity-team/unity8/rtm-20150213
--
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/1393008
Title:
Horizontal cards with summary don't get backgrounds
Status in the base for Ubuntu mobile products:
In Progress
Status in Ubuntu App Developer site:
Invalid
Status in unity8 package in Ubuntu:
Fix Released
Status in unity8 package in Ubuntu RTM:
In Progress
Bug description:
If I change the WEATHER_TEMPLATE in the scopes example to:
const static string WEATHER_TEMPLATE =
R(
{
schema-version: 1,
template: {
category-layout: carousel,
card-layout: horizontal,
card-size: small,
card-background:color:///#0F0F0F
},
components: {
title: title,
art : {
field: art
},
subtitle: subtitle,
summary: summary
}
}
);
The cards are placed in carousel style, but the background color is
simply omitted, the color of the card stays black.
If the card-layout is changed from horizontal to vertical, the
color is there, and the cards in a carousel style, but the bottom 10%
of the cards seem to be clipped. (Screenshot attached)
This is my first bug report ever, so please let me know what else I
should add, or if I am at the right place at all.
Reported from: http://developer.ubuntu.com/scopes/cookbook/
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1393008/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393447] Re: Launcher over greeter should remain on screen if the left edge gesture did not swipe the greeter away
** Branch linked: lp:~unity-team/unity8/rtm-20150213 -- 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/1393447 Title: Launcher over greeter should remain on screen if the left edge gesture did not swipe the greeter away Status in the base for Ubuntu mobile products: In Progress Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: In Progress Bug description: Preconditions: * Have the screen lock method configured to use a PIN code Steps: * swipe from the left edge so that the welcome screen (Greeter) is moved, but springs back into place Expected: * launcher remains on screen Current: * launcher hides ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: unity8 8.01+15.04.20141107.2-0ubuntu2 Uname: Linux 3.18.0-031800rc4-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Mon Nov 17 16:01:43 2014 SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1393447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1411751] Re: Attribute in news section of today scope has wrong aspect ratio depending on grid size
** Branch linked: lp:~unity-team/unity8/rtm-20150213 -- 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/1411751 Title: Attribute in news section of today scope has wrong aspect ratio depending on grid size Status in the base for Ubuntu mobile products: Confirmed Status in unity8 package in Ubuntu: In Progress Status in unity8 package in Ubuntu RTM: In Progress Bug description: Open the Today scope in Arale Go to News section BBC attribute aspect ratio is not correct. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1411751/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1334855] Re: [design] Can't use toolbar while notifications on screen
** Branch linked: lp:~unity-team/unity8/rtm-20150213 -- 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/1334855 Title: [design] Can't use toolbar while notifications on screen Status in the base for Ubuntu mobile products: In Progress Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: In Progress Bug description: With notifications on the screen, they're overlayed on top of the top toolbar, as such I can't tap the back button. To replicate. Open system settings - accounts Sign in to twitter Wait while tweet notifications come in Navigate anywhere in system settings, such as updates. Note you can't go back while the notifications are on screen. See screenshot, back button obscured. --- Desired resolution: - All types of notifications should be dismissable To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1334855/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1418939] Re: unity actively overrides system-wide gsettings as current user, making some vendor overrides ineffective
** Changed in: unity
Status: New = Confirmed
** 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/1418939
Title:
unity actively overrides system-wide gsettings as current user, making
some vendor overrides ineffective
Status in Unity:
Confirmed
Status in unity package in Ubuntu:
Confirmed
Bug description:
How to reproduce:
as root execute
# echo -e [org.gnome.desktop.input-sources]\nsources=[('xkb', 'us'), ('xkb',
'hu')]\n\n /usr/share/glib-2.0/schemas/99_my.gschema.override
# echo -e [org.compiz.unityshell]\nlauncher-minimize-window=true\n\n
/usr/share/glib-2.0/schemas/99_my.gschema.override
# glib-compile-schemas /usr/share/glib-2.0/schemas
and, either remove contents of home directory or create a new user,
and, reboot and log in as the appropriate user.
Result is that launcher-minimize-window settings=true as expected and
launcher behaves accordingly, however input sources is just [('xkb',
'us')], where as it should be [('xkb', 'us'), ('xkb', 'hu')].
The launcher-minimize-window is just a random example. For most
settings the vendor override method works.
But for a few, like org.gnome.desktop.input-sources sources, they
will not take effect, as some process, related to Unity, will override
them for the current user after login.
Proof of this, is that running `gsettings reset org.gnome.desktop
.input-sources sources` will result in [('xkb', 'us'), ('xkb', 'hu')],
and the panel offering both layouts. Hence the vendor-override-method
of setting system-wide defaults does work, but Unity ruins it for a
few settings.
The proof that this bug is in Unity is that, installing another
desktop environment, like gnome-shell, and logging into it, leaves all
the system-wide defaults effective.
This bug makes vendor overrides, that should affect all fresh user
accounts, ineffective.
The appropriate behaviour would be that a new user, or one that has
its home directory cleared, to have the system-wide default gsettings
in effect for their unity session.
Original problem statement: http://askubuntu.com/questions/582083
/what-is-overriding-the-systemwide-keyboard-layout-settings
To get a more comprehensive but still incomplete listing of the settings that
Unity overrides, log in into a fresh Unity session,
$ gsettings list-recursively /tmp/01
$ gsettings list-schemas | xargs -n 1 gsettings reset-recursively
$ gsettings list-recursively /tmp/02
$ diff /tmp/0* | less
This listing is incomplete, because it only lists non-relocatable schemas,
and also because your system-wide defaults may match those of what Unity sets
the users settings to. For example, not changing the layout setting to
[('xkb', 'us'), ('xkb', 'hu')] with a vendor override, would cause it not to
be listed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/unity/+bug/1418939/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355422] Re: [notifications] Can't dismiss notification bubbles
** Branch linked: lp:~unity-team/unity8/rtm-20150213 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-notifications in Ubuntu. https://bugs.launchpad.net/bugs/1355422 Title: [notifications] Can't dismiss notification bubbles Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in Server and client library for desktop notifications in Unity: New Status in unity-notifications package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: In Progress Bug description: On a phone with accounts setup for twitter, facebook and 2x google accounts I get a fair number of notifications. Often times these notifications appear while I'm actually using the phone. This presents issues in multiple areas:- * If I'm in the dash I am blocked from using the search function because a notification covers the search button * If I'm in the dash and already searching, having typed something, I'm blocked from seeing what I'm typing by the notification * In apps I can't go back because the notification blocks the button You get the idea. Basically notifications slow me down, because I have to wait for them to disappear. I'd like to be able to dismiss them. On iOS you swipe up which is indicated with a horizontal bar to grab and swipe away. --- Desired solution We've added in the latest specification for notifications bubbles (or clickable notifications) the ability to dismiss a notification via swiping left to right. Link to the spec: https://docs.google.com/a/canonical.com/document/d /1ehZGFePGmy8pnyAGsgWYDeBgr45Cc8jE2mTb2Qz-oeM/edit# To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1355422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1421560] Re: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service'
** Changed in: rtkit (Debian) Status: Unknown = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rtkit in Ubuntu. https://bugs.launchpad.net/bugs/1421560 Title: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' Status in rtkit package in Ubuntu: Fix Released Status in rtkit package in Debian: Fix Released Bug description: booted with systemd-sysv seen into syslog: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: systemd 218-8ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-5.5-generic 3.19.0 Uname: Linux 3.19.0-5-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.16.1-0ubuntu2 Architecture: i386 BootDmesg: (Nothing has been logged yet.) CurrentDesktop: GNOME Date: Fri Feb 13 09:19:58 2015 Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002: ID 046d:c50e Logitech, Inc. Cordless Mouse Receiver Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-5-generic root=UUID=7b1f4a51-558f-468f-85e0-f815d2f791e1 ro SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/22/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3002 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5W DH Deluxe dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3002:bd07/22/2010:svnASUSTEKCOMPUTERINC:pnP5WDHDeluxe:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5WDHDeluxe:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: P5W DH Deluxe dmi.product.version: System Version dmi.sys.vendor: ASUSTEK COMPUTER INC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rtkit/+bug/1421560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
