[Touch-packages] [Bug 1492129] [NEW] FFE: integrate networkd with /etc/network/if-*.d/ scripts and resolvconf
Public bug reported: In https://blueprints.launchpad.net/ubuntu/+spec/foundations-w-networkd- vs-ifupdown we want to provide networkd as a viable option for Ubuntu, in particular server/cloud land. This requires some integration with existing packages, in particular calling the /etc/network/if-up.d/ and if-post-down.d/ scripts, similar to what NetworkManager does. I would like to land this in wily still, so that people can experiment it and we still have some time to tweak it for 16.04 LTS: http://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?id=27f7cc9f9f32 As we don't currently use (or even advertise) networkd in Ubuntu, the risk of this is very low IMHO. The main regression risk is if that would somehow influence/break interfaces managed by ifupdown or NetworkManager, but the above changes test if the interface is managed by networkd. We also want to provide integration with "resolvconf". This does not exist yet, but FFE wise it would be very similar; so perhaps this could get some pre-approval to avoid some paperwork? ** Affects: systemd (Ubuntu) Importance: Wishlist Status: New ** Changed in: systemd (Ubuntu) Importance: Undecided => Wishlist ** Description changed: In https://blueprints.launchpad.net/ubuntu/+spec/foundations-w-networkd- vs-ifupdown we want to provide networkd as a viable option for Ubuntu, in particular server/cloud land. This requires some integration with existing packages, in particular calling the /etc/network/if-up.d/ and if-post-down.d/ scripts, similar to what NetworkManager does. I would like to land this in wily still, so that people can experiment it and we still have some time to tweak it for 16.04 LTS: - http://anonscm.debian.org/cgit/pkg- + http://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?id=27f7cc9f9f32 As we don't currently use (or even advertise) networkd in Ubuntu, the risk of this is very low IMHO. The main regression risk is if that would somehow influence/break interfaces managed by ifupdown or NetworkManager, but the above changes test if the interface is managed by networkd. + + We also want to provide integration with "resolvconf". This does not + exist yet, but FFE wise it would be very similar; so perhaps this could + get some pre-approval to avoid some paperwork? ** Summary changed: - FFE: integrate networkd with /etc/network/if-*.d/ scripts + FFE: integrate networkd with /etc/network/if-*.d/ scripts and resolvconf -- 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/1492129 Title: FFE: integrate networkd with /etc/network/if-*.d/ scripts and resolvconf Status in systemd package in Ubuntu: New Bug description: In https://blueprints.launchpad.net/ubuntu/+spec/foundations-w -networkd-vs-ifupdown we want to provide networkd as a viable option for Ubuntu, in particular server/cloud land. This requires some integration with existing packages, in particular calling the /etc/network/if-up.d/ and if-post-down.d/ scripts, similar to what NetworkManager does. I would like to land this in wily still, so that people can experiment it and we still have some time to tweak it for 16.04 LTS: http://anonscm.debian.org/cgit/pkg- systemd/systemd.git/commit/?id=27f7cc9f9f32 As we don't currently use (or even advertise) networkd in Ubuntu, the risk of this is very low IMHO. The main regression risk is if that would somehow influence/break interfaces managed by ifupdown or NetworkManager, but the above changes test if the interface is managed by networkd. We also want to provide integration with "resolvconf". This does not exist yet, but FFE wise it would be very similar; so perhaps this could get some pre-approval to avoid some paperwork? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1492129/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1489309] Re: Names in Favorite Contacts are cut at the bottom
@Ethan, thanks! -- 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/1489309 Title: Names in Favorite Contacts are cut at the bottom Status in Today Scope: Fix Committed Status in unity8 package in Ubuntu: In Progress Bug description: bq 4.5 Ubuntu Edition with OTA-5, Today Scope version 1.9.1. Please see the attached screenshot. The name should read 'Some Gorge' but 'g' in 'Gorge' is not fully visible. To manage notifications about this bug go to: https://bugs.launchpad.net/today-scope/+bug/1489309/+subscriptions -- Mailing list: https://launchpad.net/~touch-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: [edge interaction] Left swipe/BFB should reset search string
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- 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: [edge interaction] Left swipe/BFB should reset search string Status in Canonical System Image: Fix Released Status in Ubuntu UX: Fix Released Status in unity8 package in Ubuntu: Fix Released 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 -- Desired design solution: Long left edge swipe or BFB click on the launcher takes user back to apps scope (or leftmost scope in the dash). It also resets the search query and positions the list in the beginning. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+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 1492126]
StacktraceTop:
g_variant_iter_loop (iter=0x0, format_string=0xb424daba "(&oa{sv})") at
/build/glib2.0-M4BESt/glib2.0-2.45.6/./glib/gvariant.c:5616
ofono_enumerate_devices_done (proxy=0x8c91760, res=0x8cbf810,
user_data=0x8caa708) at nm-modem-manager.c:329
g_task_return_now (task=task@entry=0x8cbf810) at
/build/glib2.0-M4BESt/glib2.0-2.45.6/./gio/gtask.c:1104
g_task_return (task=0x8cbf810, type=) at
/build/glib2.0-M4BESt/glib2.0-2.45.6/./gio/gtask.c:1162
reply_cb (connection=0x8c9c818, res=0x8cbf888, user_data=0x8cbf810) at
/build/glib2.0-M4BESt/glib2.0-2.45.6/./gio/gdbusproxy.c:2569
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1492126
Title:
[wily-proposed only] NetworkManager crashed with SIGSEGV in
g_variant_iter_loop()
Status in network-manager package in Ubuntu:
New
Bug description:
This can be trivially reproduced by installing the wily-proposed
network-manager on i386 and rebooting. This is also spotted by
systemd's autopkgtest
(http://autopkgtest.ubuntu.com/packages/s/systemd/wily/i386/).
In the journal I see
Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718):
GLib-GObject-WARNING **:
/build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal
'ModemAdded' is invalid for instance '0x997d760' of type 'GDBusProxy'
Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718):
GLib-GObject-WARNING **:
/build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal
'ModemRemoved' is invalid for instance '0x997d760' of type 'GDBusProxy'
Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718):
GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed
Sep 04 08:32:15 autopkgtest systemd[1]: NetworkManager.service: Main process
exited, code=dumped, status=11/SEGV
I suppose the g_critical is not the thing it fails on, as that would
be a SIGABRT.
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0
Uname: Linux 4.2.0-7-generic i686
ApportVersion: 2.18-0ubuntu9
Architecture: i386
Date: Fri Sep 4 08:40:19 2015
ExecutablePath: /usr/sbin/NetworkManager
ExecutableTimestamp: 1440792479
IpRoute:
default via 10.0.2.2 dev eth0
10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
ProcCmdline: /usr/sbin/NetworkManager --no-daemon
ProcCwd: /
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
SegvAnalysis:
Segfault happened at: 0xb701f259 : mov
0xc(%esi),%edi
PC (0xb701f259) ok
source "0xc(%esi)" (0x000c) not located in a known VMA region (needed
readable region)!
destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: network-manager
StacktraceTop:
g_variant_iter_loop () from /lib/i386-linux-gnu/libglib-2.0.so.0
?? () from /usr/lib/i386-linux-gnu/NetworkManager/libnm-wwan.so
?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0
Title: NetworkManager crashed with SIGSEGV in g_variant_iter_loop()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code
8: Error: NetworkManager is not running.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code
8: Error: NetworkManager is not running.
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code
2: Error: Object 'nm' is unknown, try 'nmcli help'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1492126/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492126] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1492126/+attachment/4457131/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1492126 Title: [wily-proposed only] NetworkManager crashed with SIGSEGV in g_variant_iter_loop() Status in network-manager package in Ubuntu: New Bug description: This can be trivially reproduced by installing the wily-proposed network-manager on i386 and rebooting. This is also spotted by systemd's autopkgtest (http://autopkgtest.ubuntu.com/packages/s/systemd/wily/i386/). In the journal I see Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemAdded' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemRemoved' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Sep 04 08:32:15 autopkgtest systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV I suppose the g_critical is not the thing it fails on, as that would be a SIGABRT. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 ApportVersion: 2.18-0ubuntu9 Architecture: i386 Date: Fri Sep 4 08:40:19 2015 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1440792479 IpRoute: default via 10.0.2.2 dev eth0 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SegvAnalysis: Segfault happened at: 0xb701f259 : mov 0xc(%esi),%edi PC (0xb701f259) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: g_variant_iter_loop () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/NetworkManager/libnm-wwan.so ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in g_variant_iter_loop() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1492126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492137] [NEW] Brightness keys (fn+f5/f6) not working, UX305FA
Public bug reported: Brightness keys does not change screen brightness. Manually editing the brightness in system settings does work however. Using xev, neither of the brightness function keys are detected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.12 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 Sep 4 08:59:14 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:181d] InstallationDate: Installed on 2015-09-02 (1 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9700 Suyin Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305FA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic.efi.signed root=UUID=dc0d1e93-b3f9-4b94-9fd9-4c91317f91f7 ro quiet splash acpi_osi=Linux vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/19/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305FA.210 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305FA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305FA.210:bd05/19/2015:svnASUSTeKCOMPUTERINC.:pnUX305FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: UX305FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Fri Sep 4 08:03:23 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3~trusty1 xserver.video_driver: intel ** 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/1492137 Title: Brightness keys (fn+f5/f6) not working, UX305FA Status in xorg package in Ubuntu: New Bug description: Brightness keys does not change screen brightness. Manually editing the brightness in system settings does work however. Using xev, neither of the brightness function keys are detected. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.12 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 Sep 4 08:59:14 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Broadwell-U Integrated Graphics [8086:161e] (rev 08) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:181d] InstallationDate: Installed on 2015-09-02 (1 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 064e:9700 Suyin Corp. Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305FA
[Touch-packages] [Bug 1492126] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1492126/+attachment/4457132/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1492126 Title: [wily-proposed only] NetworkManager crashed with SIGSEGV in g_variant_iter_loop() Status in network-manager package in Ubuntu: New Bug description: This can be trivially reproduced by installing the wily-proposed network-manager on i386 and rebooting. This is also spotted by systemd's autopkgtest (http://autopkgtest.ubuntu.com/packages/s/systemd/wily/i386/). In the journal I see Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemAdded' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemRemoved' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Sep 04 08:32:15 autopkgtest systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV I suppose the g_critical is not the thing it fails on, as that would be a SIGABRT. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 ApportVersion: 2.18-0ubuntu9 Architecture: i386 Date: Fri Sep 4 08:40:19 2015 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1440792479 IpRoute: default via 10.0.2.2 dev eth0 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SegvAnalysis: Segfault happened at: 0xb701f259 : mov 0xc(%esi),%edi PC (0xb701f259) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: g_variant_iter_loop () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/NetworkManager/libnm-wwan.so ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in g_variant_iter_loop() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1492126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492126] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1492126/+attachment/4457133/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1492126/+attachment/4457112/+files/CoreDump.gz ** Tags removed: need-i386-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1492126 Title: [wily-proposed only] NetworkManager crashed with SIGSEGV in g_variant_iter_loop() Status in network-manager package in Ubuntu: New Bug description: This can be trivially reproduced by installing the wily-proposed network-manager on i386 and rebooting. This is also spotted by systemd's autopkgtest (http://autopkgtest.ubuntu.com/packages/s/systemd/wily/i386/). In the journal I see Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemAdded' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemRemoved' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Sep 04 08:32:15 autopkgtest systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV I suppose the g_critical is not the thing it fails on, as that would be a SIGABRT. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 ApportVersion: 2.18-0ubuntu9 Architecture: i386 Date: Fri Sep 4 08:40:19 2015 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1440792479 IpRoute: default via 10.0.2.2 dev eth0 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SegvAnalysis: Segfault happened at: 0xb701f259 : mov 0xc(%esi),%edi PC (0xb701f259) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: g_variant_iter_loop () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/NetworkManager/libnm-wwan.so ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in g_variant_iter_loop() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1492126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491566] Re: Greeter and edges not responsive after an incoming SMS
Indeed, we need to track where is the input lost. When you experience it again, can you please check if volume buttons still work? Unity8 isn't stuck altogether because you can see notifications and indicators updating, so somehow no input reaches unity8. I wonder if unity-system-compositor could be involved. ** Also affects: unity-system-compositor (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/1491566 Title: Greeter and edges not responsive after an incoming SMS Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: New Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: Confirmed Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491802] Re: A disabled label cannot be visually differantiated from enabled labels
Currently developers are faking disabled labels by setting opacity. So
if/when toolkit visual designers decide that they should be styled
another way (even just a different opacity level), the longer this bug
goes unfixed, the more lines of code will need finding and changing.
--
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/1491802
Title:
A disabled label cannot be visually differantiated from enabled labels
Status in Ubuntu UX:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
New
Bug description:
Reproduce:
Label {
text: "Example text"
enabled: false
}
Label {
text: "Example text"
enabled: true
}
What happens:
The two labels are visually equal.
What should have happened:
The disabled label should somehow indicate a disabled state.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1491802/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492126] Re: [wily-proposed only] NetworkManager crashed with SIGSEGV in ofono_enumerate_devices_done()
Adjusting bug title to make this more obvious. Apparently ofono_enumerate_devices_done() calls g_variant_iter_loop() on a NULL iterator. ** Summary changed: - [wily-proposed only] NetworkManager crashed with SIGSEGV in g_variant_iter_loop() + [wily-proposed only] NetworkManager crashed with SIGSEGV in ofono_enumerate_devices_done() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1492126 Title: [wily-proposed only] NetworkManager crashed with SIGSEGV in ofono_enumerate_devices_done() Status in network-manager package in Ubuntu: New Bug description: This can be trivially reproduced by installing the wily-proposed network-manager on i386 and rebooting. This is also spotted by systemd's autopkgtest (http://autopkgtest.ubuntu.com/packages/s/systemd/wily/i386/). In the journal I see Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemAdded' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemRemoved' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Sep 04 08:32:15 autopkgtest systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV I suppose the g_critical is not the thing it fails on, as that would be a SIGABRT. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 ApportVersion: 2.18-0ubuntu9 Architecture: i386 Date: Fri Sep 4 08:40:19 2015 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1440792479 IpRoute: default via 10.0.2.2 dev eth0 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SegvAnalysis: Segfault happened at: 0xb701f259 : mov 0xc(%esi),%edi PC (0xb701f259) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: g_variant_iter_loop () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/NetworkManager/libnm-wwan.so ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in g_variant_iter_loop() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1492126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480815] Re: CMCC receive MMS will auto change into group chat
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: messaging-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1480815 Title: Receiving MMS will auto change into group chat for some operators Status in messaging-app package in Ubuntu: Confirmed Bug description: system-image-cli -i current build number: 80 device name: arale channel: ubuntu-touch/devel-proposed/meizu.en last update: 2015-08-03 15:23:15 version version: 80 version ubuntu: 20150802 version device: 20150709-8965e37 version custom: 20150716-819-8-42 reproduce steps: 1.there is a CMCC SIM card inserted in the DUT device. 2.there is no contact in the device and the MMS group chat option was disabled 3.other device send one MMS just to the DUT 4.the DUT received the MMS 5.launch the message app check the received MMS expect result: (5) the MMS display in the dialog panel and show the the number of the sender and the word content actual result: the dialog panel of the message change to group chat auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1480815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492126] Re: [wily-proposed only] NetworkManager crashed with SIGSEGV in ofono_enumerate_devices_done()
also a show stopper: not all the network-manager packages have been upgraded to 1.0.4-0ubuntu2, some are still 0.9.10 reported as lp:1489154 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1492126 Title: [wily-proposed only] NetworkManager crashed with SIGSEGV in ofono_enumerate_devices_done() Status in network-manager package in Ubuntu: Confirmed Bug description: This can be trivially reproduced by installing the wily-proposed network-manager on i386 and rebooting. This is also spotted by systemd's autopkgtest (http://autopkgtest.ubuntu.com/packages/s/systemd/wily/i386/). In the journal I see Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemAdded' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemRemoved' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Sep 04 08:32:15 autopkgtest systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV I suppose the g_critical is not the thing it fails on, as that would be a SIGABRT. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 ApportVersion: 2.18-0ubuntu9 Architecture: i386 Date: Fri Sep 4 08:40:19 2015 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1440792479 IpRoute: default via 10.0.2.2 dev eth0 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SegvAnalysis: Segfault happened at: 0xb701f259 : mov 0xc(%esi),%edi PC (0xb701f259) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: g_variant_iter_loop () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/NetworkManager/libnm-wwan.so ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in g_variant_iter_loop() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1492126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437192] Re: FTBFS with Qt 5.5: "cannot find -linput"
** Branch linked: lp:ubuntu/wily-proposed/appmenu-qt5 -- 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/1437192 Title: FTBFS with Qt 5.5: "cannot find -linput" Status in appmenu-qt5 package in Ubuntu: New Status in qtubuntu package in Ubuntu: Fix Released Bug description: There seems to be some sort of new dependency, even though none were added in Qt 5.5's own build dependencies: --- g++ -std=c++11 -Wl,-no-undefined -Wl,-Bsymbolic-functions -Wl,-z,relro -shared -o libqpa-ubuntumirclient.so backingstore.o clipboard.o glcontext.o input.o integration.o nativeinterface.o platformservices.o plugin.o screen.o theme.o window.o moc_clipboard.o moc_input.o moc_plugin.o moc_screen.o moc_window.o -lmirclient -lmircommon -lubuntu_application_api -lQt5PlatformSupport -lfontconfig -lfreetype -lgthread-2.0 -pthread -lglib-2.0 -linput -lxkbcommon -ludev -lmtdev -lEGL -lQt5Gui -lQt5Sensors -lQt5DBus -lQt5Core -lGLESv2 -lpthread /usr/bin/ld: cannot find -linput --- That is, qtubuntu and appmenu-qt5 should apparently have a build dependency on 'libinput-dev': https://launchpad.net/ubuntu/+source/libinput More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting appmenu-qt5: https://launchpadlibrarian.net/202748418/buildlog_ubuntu-vivid-amd64.appmenu-qt5_0.3.0%2B15.04.20150121-0ubuntu4~vivid1~test1~qt550alpha1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1437192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480815] Re: CMCC receive MMS will auto change into group chat
I am seeing this also with Spanish operators when receiving a MMS from Ubuntu phone to Ubuntu phone: a chat group is automatically created. ** Summary changed: - CMCC receive MMS will auto change into group chat + Receiving MMS will auto change into group chat for some operators -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1480815 Title: Receiving MMS will auto change into group chat for some operators Status in messaging-app package in Ubuntu: Confirmed Bug description: system-image-cli -i current build number: 80 device name: arale channel: ubuntu-touch/devel-proposed/meizu.en last update: 2015-08-03 15:23:15 version version: 80 version ubuntu: 20150802 version device: 20150709-8965e37 version custom: 20150716-819-8-42 reproduce steps: 1.there is a CMCC SIM card inserted in the DUT device. 2.there is no contact in the device and the MMS group chat option was disabled 3.other device send one MMS just to the DUT 4.the DUT received the MMS 5.launch the message app check the received MMS expect result: (5) the MMS display in the dialog panel and show the the number of the sender and the word content actual result: the dialog panel of the message change to group chat auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1480815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370376] Re: Can't receive MMS despite ability to send on Tele2
@Tomas, thanks for your testing. I think you are seeing bug #1480815 . Could you please add a comment there? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1370376 Title: Can't receive MMS despite ability to send on Tele2 Status in network-manager package in Ubuntu: Invalid Status in nuntium package in Ubuntu: Confirmed Bug description: I can send MMS (and they actually come through to the recipient), but I can't receive MMS. I am not sure if this is an APN settings issue, but I would have thought it either worked both ways or not at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1370376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492126] Re: [wily-proposed only] NetworkManager crashed with SIGSEGV in ofono_enumerate_devices_done()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1492126 Title: [wily-proposed only] NetworkManager crashed with SIGSEGV in ofono_enumerate_devices_done() Status in network-manager package in Ubuntu: Confirmed Bug description: This can be trivially reproduced by installing the wily-proposed network-manager on i386 and rebooting. This is also spotted by systemd's autopkgtest (http://autopkgtest.ubuntu.com/packages/s/systemd/wily/i386/). In the journal I see Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemAdded' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemRemoved' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Sep 04 08:32:15 autopkgtest systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV I suppose the g_critical is not the thing it fails on, as that would be a SIGABRT. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 ApportVersion: 2.18-0ubuntu9 Architecture: i386 Date: Fri Sep 4 08:40:19 2015 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1440792479 IpRoute: default via 10.0.2.2 dev eth0 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SegvAnalysis: Segfault happened at: 0xb701f259 : mov 0xc(%esi),%edi PC (0xb701f259) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: g_variant_iter_loop () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/NetworkManager/libnm-wwan.so ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in g_variant_iter_loop() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1492126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474313] Re: Needs to b-d on libqt5xcbqpa5 to be able to run tests under xvfb
Agreed, merging that change too, thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1474313 Title: Needs to b-d on libqt5xcbqpa5 to be able to run tests under xvfb Status in camera-app package in Ubuntu: Invalid Status in messaging-app package in Ubuntu: Invalid Status in qtbase-opensource-src package in Ubuntu: New Status in signon-ui package in Ubuntu: Invalid Status in ubuntu-keyboard package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Status in ubuntu-system-settings-online-accounts package in Ubuntu: Invalid Status in webbrowser-app package in Ubuntu: Invalid Bug description: UPDATE: qtbase will be changed to Recommend libqt5xcbqpa5 instead. Qt 5.5 packaging currently introduces a new package libqt5xcbqpa5, which is required to be installed during build time for being able to run tests under X(vfb). The change cannot be landed other than together with Qt 5.5, or after it for packages that do not require a rebuild. So, there are no actions except for preparing the branch. Another possibility would probably be to switch to Mir's mirvfb. Packages that need to be fixed together with Qt 5.5: webbrowser-app Packages that can be fixed afterwards (but it'd be useful to run the tests before to see if they actually pass): camera-app messaging-app signon-ui ubuntu-system-settings ubuntu-system-settings-online- accounts Information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting Test rebuilds against landing-012 have been made at https://launchpad.net/~canonical- qt5-edgers/+archive/ubuntu/qt5-beta2/+packages?field.name_filter=&field.status_filter=published&field.series_filter=wily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1474313/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492144] [NEW] wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch()
Public bug reported: This happens when running the NetworkManager autopkgtests ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: wpasupplicant 2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Fri Sep 4 09:00:38 2015 ExecutablePath: /sbin/wpa_supplicant ExecutableTimestamp: 1439920046 ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1 PC (0x7f66fb181cc6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-crash need-amd64-retrace wily ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1492144 Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() Status in wpa package in Ubuntu: New Bug description: This happens when running the NetworkManager autopkgtests ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: wpasupplicant 2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Fri Sep 4 09:00:38 2015 ExecutablePath: /sbin/wpa_supplicant ExecutableTimestamp: 1439920046 ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1 PC (0x7f66fb181cc6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1492144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1409356] Re: drop usage of :sys:started/stopped/starting/stopping events
Missing bug ref in the changelog, closing manually: https://launchpad.net/ubuntu/+source/nuntium/1.4+15.10.20150902-0ubuntu1 Thanks Dimitri and Alfonso! ** Changed in: nuntium (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1409356 Title: drop usage of :sys:started/stopped/starting/stopping events Status in location-service package in Ubuntu: New Status in nuntium package in Ubuntu: Fix Released Bug description: When system upstart goes away, :sys:started/stopped/starting/stopping events will go away. One option is to introduce a user session event bridge which will relay similar events from systemd. I have a working prototype for that, however incomplete information is exposed by systemd at the moment. Another option is to key onto approximately equivalent events which are already available. This is a master bug to track all users and port them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1409356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471577] Re: Left launcher should show what apps are open
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- 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/1471577 Title: Left launcher should show what apps are open Status in Canonical System Image: New Status in Ubuntu UX: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: Hello, I think that will be good if left launcher shows us somehow what app is in opened. For now, when we start new app, its icon 'lands' in left launcher. But we don't know if that app is pinned there and it is all the time, or only because it's opened. I think that in Desktop version that issue is solved, but for now can't check it now. Desired solution--- Launcher should indicate running apps in the launcher with a mark on the left side of the app icon. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1471577/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492144]
StacktraceTop: ?? () ?? () ?? () from /tmp/apport_sandbox_3HEGxn/lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /tmp/apport_sandbox_3HEGxn/lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1492144 Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() Status in wpa package in Ubuntu: Invalid Bug description: This happens when running the NetworkManager autopkgtests ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: wpasupplicant 2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Fri Sep 4 09:00:38 2015 ExecutablePath: /sbin/wpa_supplicant ExecutableTimestamp: 1439920046 ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1 PC (0x7f66fb181cc6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1492144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492144] Stacktrace.txt
** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1492144/+attachment/4457171/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1492144 Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() Status in wpa package in Ubuntu: Invalid Bug description: This happens when running the NetworkManager autopkgtests ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: wpasupplicant 2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Fri Sep 4 09:00:38 2015 ExecutablePath: /sbin/wpa_supplicant ExecutableTimestamp: 1439920046 ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1 PC (0x7f66fb181cc6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1492144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492144] Crash report cannot be processed
Thank you for your report! However, processing it in order to get sufficient information for the developers failed (it does not generate a useful symbolic stack trace). This might be caused by some outdated packages which were installed on your system at the time of the report: no debug symbol package found for libdbus-1-3 no debug symbol package found for libgpg-error0 no debug symbol package found for liblzma5 no debug symbol package found for libnl-genl-3-200 no debug symbol package found for wpasupplicant Please upgrade your system to the latest package versions. If you still encounter the crash, please file a new report. Thank you for your understanding, and sorry for the inconvenience! ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1492144/+attachment/4457159/+files/CoreDump.gz ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1492144 Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() Status in wpa package in Ubuntu: Invalid Bug description: This happens when running the NetworkManager autopkgtests ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: wpasupplicant 2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Fri Sep 4 09:00:38 2015 ExecutablePath: /sbin/wpa_supplicant ExecutableTimestamp: 1439920046 ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1 PC (0x7f66fb181cc6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1492144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492144] ThreadStacktrace.txt
** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1492144/+attachment/4457173/+files/ThreadStacktrace.txt ** Changed in: wpa (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1492144 Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() Status in wpa package in Ubuntu: Invalid Bug description: This happens when running the NetworkManager autopkgtests ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: wpasupplicant 2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Fri Sep 4 09:00:38 2015 ExecutablePath: /sbin/wpa_supplicant ExecutableTimestamp: 1439920046 ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1 PC (0x7f66fb181cc6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1492144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492144] StacktraceSource.txt
** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/1492144/+attachment/4457172/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1492144 Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() Status in wpa package in Ubuntu: Invalid Bug description: This happens when running the NetworkManager autopkgtests ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: wpasupplicant 2.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic x86_64 ApportVersion: 2.18-0ubuntu9 Architecture: amd64 Date: Fri Sep 4 09:00:38 2015 ExecutablePath: /sbin/wpa_supplicant ExecutableTimestamp: 1439920046 ProcCmdline: /sbin/wpa_supplicant -u -s -O /run/wpa_supplicant ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SegvAnalysis: Segfault happened at: 0x7f66fb181cc6 <__strcmp_sse2+22>: movlpd (%rdi),%xmm1 PC (0x7f66fb181cc6) ok source "(%rdi)" (0x) not located in a known VMA region (needed readable region)! destination "%xmm1" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: wpa StacktraceTop: ?? () ?? () ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3 ?? () Title: wpa_supplicant crashed with SIGSEGV in dbus_connection_dispatch() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1492144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437192] Re: FTBFS with Qt 5.5: "cannot find -linput"
This bug was fixed in the package appmenu-qt5 - 0.3.0+15.10.20150903-0ubuntu1 --- appmenu-qt5 (0.3.0+15.10.20150903-0ubuntu1) wily; urgency=medium [ Timo Jyrinki ] * Build dep on libinput-dev for Qt 5.5. (LP: #1437192) -- CI Train Bot Thu, 03 Sep 2015 10:15:35 + ** Changed in: appmenu-qt5 (Ubuntu) Status: New => Fix Released -- 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/1437192 Title: FTBFS with Qt 5.5: "cannot find -linput" Status in appmenu-qt5 package in Ubuntu: Fix Released Status in qtubuntu package in Ubuntu: Fix Released Bug description: There seems to be some sort of new dependency, even though none were added in Qt 5.5's own build dependencies: --- g++ -std=c++11 -Wl,-no-undefined -Wl,-Bsymbolic-functions -Wl,-z,relro -shared -o libqpa-ubuntumirclient.so backingstore.o clipboard.o glcontext.o input.o integration.o nativeinterface.o platformservices.o plugin.o screen.o theme.o window.o moc_clipboard.o moc_input.o moc_plugin.o moc_screen.o moc_window.o -lmirclient -lmircommon -lubuntu_application_api -lQt5PlatformSupport -lfontconfig -lfreetype -lgthread-2.0 -pthread -lglib-2.0 -linput -lxkbcommon -ludev -lmtdev -lEGL -lQt5Gui -lQt5Sensors -lQt5DBus -lQt5Core -lGLESv2 -lpthread /usr/bin/ld: cannot find -linput --- That is, qtubuntu and appmenu-qt5 should apparently have a build dependency on 'libinput-dev': https://launchpad.net/ubuntu/+source/libinput More information about Qt 5.5 at https://wiki.ubuntu.com/Touch/QtTesting appmenu-qt5: https://launchpadlibrarian.net/202748418/buildlog_ubuntu-vivid-amd64.appmenu-qt5_0.3.0%2B15.04.20150121-0ubuntu4~vivid1~test1~qt550alpha1_BUILDING.txt.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appmenu-qt5/+bug/1437192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1415023] Re: [Dialog] if keyboard is present, buttons and derivatives have to be pressed twice
** No longer affects: ubuntu-system-settings (Ubuntu) -- 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/1415023 Title: [Dialog] if keyboard is present, buttons and derivatives have to be pressed twice Status in ubuntu-ui-toolkit package in Ubuntu: Confirmed Bug description: STEPS: Setup: 1 phone + one locked sim 1. Open system settings 2. Goto Security 3. Goto Sim Pin 4. Tap on unlock 5. Type in the pin 6. Tap the green confirm button EXPECTED: I expect the dialog to be dismissed and the keyboard and sim be unlocked ACTUAL: The keyboard is dismissed but the dialog box remains. A recent change has effected this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1415023/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1431328] Re: build.sh --setup doesn't install build dependencies
I've fixed the page so that it says --setup now, wordpress was being too smart for its own good -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1431328 Title: build.sh --setup doesn't install build dependencies Status in unity8 package in Ubuntu: Incomplete Bug description: DISTRO Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 EXPECTED after "build.sh -s" completes I am able to build unity8 with "build.sh" ACTUAL "build.sh -s" doesn't install libsystemsettings-dev so the compilation afterwards fails with -- Could NOT find Lcov (missing: LCOV_EXECUTABLE GENHTML_EXECUTABLE) -- Could NOT find gcovr (missing: GCOVR_EXECUTABLE) Package SystemSettings was not found in the pkg-config search path. Perhaps you should add the directory containing `SystemSettings.pc' to the PKG_CONFIG_PATH environment variable No package 'SystemSettings' found CMake Error at CMakeLists.txt:67 (message): Could not determine USS private plugin installation dir. MORE INFORMATION You can find the "build.sh -s" output at http://pastebin.ubuntu.com/10585178/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1431328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492157] [NEW] ibus-ui-gtk3 crashed with SIGSEGV in g_variant_type_new_tuple()
Public bug reported: This happened with a Wily gnome-shell session: - open nautilus - click on its top bar to get 'Move To Workspace Down' and got a cascade of crashes, ending to the session crashing: - first crash: tracker-miner-fs - then ibus-ui-gtk3 - and finally gnome-shell when i right click on the crashed files, apport simply ignore to send the rapoort. So i join the files here. Strangely 'ubuntu-bug ibus-ui-gtk3' warns that this package does not exist. Effectively there is no such package into the archive. Note: that happen also without installed/activated 'extensions' from gnome.org ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ibus 1.5.10-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu9 Architecture: i386 CurrentDesktop: GNOME Date: Fri Sep 4 10:18:08 2015 SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 wily ** Attachment added: "_usr_lib_ibus_ibus-ui-gtk3.1000.crash" https://bugs.launchpad.net/bugs/1492157/+attachment/4457187/+files/_usr_lib_ibus_ibus-ui-gtk3.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1492157 Title: ibus-ui-gtk3 crashed with SIGSEGV in g_variant_type_new_tuple() Status in ibus package in Ubuntu: New Bug description: This happened with a Wily gnome-shell session: - open nautilus - click on its top bar to get 'Move To Workspace Down' and got a cascade of crashes, ending to the session crashing: - first crash: tracker-miner-fs - then ibus-ui-gtk3 - and finally gnome-shell when i right click on the crashed files, apport simply ignore to send the rapoort. So i join the files here. Strangely 'ubuntu-bug ibus-ui-gtk3' warns that this package does not exist. Effectively there is no such package into the archive. Note: that happen also without installed/activated 'extensions' from gnome.org ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ibus 1.5.10-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu9 Architecture: i386 CurrentDesktop: GNOME Date: Fri Sep 4 10:18:08 2015 SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1492157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492157] Re: ibus-ui-gtk3 crashed with SIGSEGV in g_variant_type_new_tuple()
** Attachment added: "tracker-miner-fs crash" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1492157/+attachment/4457191/+files/_usr_lib_tracker_tracker-miner-fs.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1492157 Title: ibus-ui-gtk3 crashed with SIGSEGV in g_variant_type_new_tuple() Status in ibus package in Ubuntu: New Bug description: This happened with a Wily gnome-shell session: - open nautilus - click on its top bar to get 'Move To Workspace Down' and got a cascade of crashes, ending to the session crashing: - first crash: tracker-miner-fs - then ibus-ui-gtk3 - and finally gnome-shell when i right click on the crashed files, apport simply ignore to send the rapoort. So i join the files here. Strangely 'ubuntu-bug ibus-ui-gtk3' warns that this package does not exist. Effectively there is no such package into the archive. Note: that happen also without installed/activated 'extensions' from gnome.org ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ibus 1.5.10-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu9 Architecture: i386 CurrentDesktop: GNOME Date: Fri Sep 4 10:18:08 2015 SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1492157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488920] Re: should display hotplug be the only trigger for going in and out of windowed mode
** Description changed: Currently on nexus4 vivid+o + silo0 we have 2 triggers for going in and out of windowed mode use 1) BT mouse 2) hotplug slimport Should we continue with this? or limit the windowed mode to only hotplug of the hdmi ? certainly the windowed mode feels odd when on the local phone screen( as in the case of BT mouse only) using the local screen for windowed mode causes issues like bug 1438465 & bug 1473572 & bug 1488852 + + UX Solution: + 1. If a monitor and a mouse is connected then windowed mode should be enabled. + 2. If a pointer device (a mouse) is connected then windowed mode should be enabled. + 3. If a monitor is connected with no pointer device connected then windowed mode should not be enabled as a user will not be able to do much without a pointer device. ** Changed in: ubuntu-ux Status: New => 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/1488920 Title: should display hotplug be the only trigger for going in and out of windowed mode Status in canonical-pocket-desktop: New Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: New Bug description: Currently on nexus4 vivid+o + silo0 we have 2 triggers for going in and out of windowed mode use 1) BT mouse 2) hotplug slimport Should we continue with this? or limit the windowed mode to only hotplug of the hdmi ? certainly the windowed mode feels odd when on the local phone screen( as in the case of BT mouse only) using the local screen for windowed mode causes issues like bug 1438465 & bug 1473572 & bug 1488852 UX Solution: 1. If a monitor and a mouse is connected then windowed mode should be enabled. 2. If a pointer device (a mouse) is connected then windowed mode should be enabled. 3. If a monitor is connected with no pointer device connected then windowed mode should not be enabled as a user will not be able to do much without a pointer device. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1488920/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1473586] Re: [Navigation] Launcher, Status bar and app switcher reveals too easy for Full Screen applications
I acknowledge that Ubuntu touch operating system is likely not the best one for gaming. Especially when it comes to swipe interaction games like cut the rope. The solution described here is absolutely on the right track in my opinion. Thank you for the suggestion. I just think that the "edge gesture restriction mode" should not be on by default for all the fullscreen apps. For example our Ubuntu Gallery app is fullscreen but as it doesn't really have gesture heavy UI, making shell edge gestures more difficult doesn't make sense in this case. Instead I would provide apps an API that they could use to enable the mode. Let's see if this would fit to our product plans and schedules. ** Changed in: ubuntu-ux Status: Triaged => In Progress ** Changed in: ubuntu-ux Importance: High => 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/1473586 Title: [Navigation] Launcher, Status bar and app switcher reveals too easy for Full Screen applications Status in Ubuntu UX: In Progress Status in unity8 package in Ubuntu: Incomplete Bug description: I love playing games. One of my favourite game is "Cut the Rope". It is full screen game. Unfortunately during playing when I swiping left/right/top edge, then launcher/status bar/app switcher are revealed (see attached screen shots). I would like to propose improvement: For full screen application, enable double edge swiping. Use cases: Status bar - top edge: 1. Run full screen game eg. Cut the Rope (there is no status bar) 2. First top edge swipe. Result: - Status bar appears. - Game is not interrupted. - Pressing/swiping any part of screen, except top edge swipe, hide status bar. - Pressing status bar hide it. - Only second top edge swipe reveal settings. - Every press and swipe, except top edge swipe, is transferred to the game, and status bar is hiding 3. Second top edge swipe. Result: The settings are revealed. as for standard (non full-screen) mode. Launcher - left edge: 1. Run full screen game eg. Cut the Rope 2. First left edge siwpe. Result: - Only half of launcher appears. - There is no dim. - No application changing. - Game is not interrupted. - Pressing/swiping any part of screen, except left edge swipe, hide launcher. - Pressing on launcher hide it. - Only second left edge swipe reveal launcher. - Every press and swipe, except left edge swipe, is transferred to the game and launcher is hiding. 3. Second left edge swipe. Result: The launcher are revealed and it dim application. As for standard (non full-screen) mode. App switcher -right edge: 1. Run full screen game eg. Cut the Rope 2. First right edge swipe. Result: - Small bar appear on right side. - There is no dim. - There is no screen transformation - No application changing. - Game is not interrupted. - Pressing/swiping any part of screen, except right edge swipe, hide App switcher and app switcher is hiding. - Pressing on bar hide it. - Only second right edge swipe reveal App switcher. - Every press and swipe, except right edge swipe, is transferred to the game. 3. Second right edge swipe. Result: Reveal an application switcher that shows all your recent apps and lets you choose between them. As for standard (non full-screen) mode. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1473586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480815] Re: Receiving MMS will auto change into group chat for some operators
I am seeing the same behaviour with Tele2 in Sweden. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1480815 Title: Receiving MMS will auto change into group chat for some operators Status in messaging-app package in Ubuntu: Confirmed Bug description: system-image-cli -i current build number: 80 device name: arale channel: ubuntu-touch/devel-proposed/meizu.en last update: 2015-08-03 15:23:15 version version: 80 version ubuntu: 20150802 version device: 20150709-8965e37 version custom: 20150716-819-8-42 reproduce steps: 1.there is a CMCC SIM card inserted in the DUT device. 2.there is no contact in the device and the MMS group chat option was disabled 3.other device send one MMS just to the DUT 4.the DUT received the MMS 5.launch the message app check the received MMS expect result: (5) the MMS display in the dialog panel and show the the number of the sender and the word content actual result: the dialog panel of the message change to group chat auto. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1480815/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351157] Re: [browser] Update visual design of the new tab page
** Description changed: The visual design of the new tab page doesn’t fully match the visual spec: - the "see more" / "see less" actions for bookmarks should be in the section header - the layout should be different when in landscape mode --- --- --- --- UX Comment 1: Fix Released Partial - Correct UX/visuals for portrait working as per spec, but same UX/visuals also present in landscape mode (landscape has different UX & visuals): https://docs.google.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354ad9a19_026 (Page 14 of visual spec) --- --- --- --- UX Comment 2: - "Update visual design of the new tab page" - Visual designers have been overhauling style - Updated visual design for tabs can be seen here: - https://docs.google.com/presentation/d/1P6A7ZsI03sPfuI9vzPeC0VcUfIgugxnU4QyObH6UNTs/edit#slide=id.ga3305968b_0_0 + Correct UX/Visuals are currently WIP by engineers. ** Description changed: The visual design of the new tab page doesn’t fully match the visual spec: - the "see more" / "see less" actions for bookmarks should be in the section header - the layout should be different when in landscape mode --- --- --- --- UX Comment 1: Fix Released Partial - Correct UX/visuals for portrait working as per spec, but same UX/visuals also present in landscape mode (landscape has different UX & visuals): https://docs.google.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354ad9a19_026 (Page 14 of visual spec) --- --- --- --- UX Comment 2: - Correct UX/Visuals are currently WIP by engineers. + Correct Landscape UX/Visuals are currently WIP by engineers. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1351157 Title: [browser] Update visual design of the new tab page Status in Ubuntu UX: Fix Committed Status in webbrowser-app: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Status in webbrowser-app package in Ubuntu RTM: Fix Released Bug description: The visual design of the new tab page doesn’t fully match the visual spec: - the "see more" / "see less" actions for bookmarks should be in the section header - the layout should be different when in landscape mode --- --- --- --- UX Comment 1: Fix Released Partial - Correct UX/visuals for portrait working as per spec, but same UX/visuals also present in landscape mode (landscape has different UX & visuals): https://docs.google.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit#slide=id.g354ad9a19_026 (Page 14 of visual spec) --- --- --- --- UX Comment 2: Correct Landscape UX/Visuals are currently WIP by engineers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492157] Re: ibus-ui-gtk3 crashed with SIGSEGV in g_variant_type_new_tuple()
Here is the cascading crashes; maybe due to the gcc5 & libstdc++6 transition still not complete. This issue is only one of the many affected users reporting multiple crashes like lp:1484380 and others ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1492157/+attachment/4457193/+files/_usr_bin_gnome-shell.1000.crash -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1492157 Title: ibus-ui-gtk3 crashed with SIGSEGV in g_variant_type_new_tuple() Status in ibus package in Ubuntu: New Bug description: This happened with a Wily gnome-shell session: - open nautilus - click on its top bar to get 'Move To Workspace Down' and got a cascade of crashes, ending to the session crashing: - first crash: tracker-miner-fs - then ibus-ui-gtk3 - and finally gnome-shell when i right click on the crashed files, apport simply ignore to send the rapoort. So i join the files here. Strangely 'ubuntu-bug ibus-ui-gtk3' warns that this package does not exist. Effectively there is no such package into the archive. Note: that happen also without installed/activated 'extensions' from gnome.org ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ibus 1.5.10-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu9 Architecture: i386 CurrentDesktop: GNOME Date: Fri Sep 4 10:18:08 2015 SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1492157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1484383] Re: [Edge education] Tutorial doesn't teach you about the long swipe from left
We are redesigning the Edge Education and this bug will be covered by the new design. ** Changed in: ubuntu-ux Status: Triaged => In Progress -- 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/1484383 Title: [Edge education] Tutorial doesn't teach you about the long swipe from left Status in Ubuntu UX: In Progress Status in unity8 package in Ubuntu: Incomplete Bug description: I've only just discovered the long swipe from the left to get to the apps scope. I feel like an idiot but it turns out it's quite hard to find out about or discover accidentally. Even the Unity8 tutorial fails to show this feature to the user. You can (in fact, must) get through the tutorial using only a short swipe from the left to show the launcher. The long swipe remains a somewhat hidden feature. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1484383/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312260] Re: [browser] There is no search in page option in webbrowser-app (like ctrl+F)
** Description changed: Users will be able to find text in page (partial&exact match) - Function will be available in the Action Drawer - UX Spec here + --- --- --- --- --- + + UX Comment: + Spec here https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g187f4edfe_50 ** Changed in: ubuntu-ux Importance: Low => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1312260 Title: [browser] There is no search in page option in webbrowser-app (like ctrl+F) Status in Oxide: Fix Released Status in Ubuntu UX: Fix Committed Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Users will be able to find text in page (partial&exact match) - Function will be available in the Action Drawer --- --- --- --- --- UX Comment: Spec here https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g187f4edfe_50 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1312260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492161] [NEW] Messaging app sluggish after OTA-6
Public bug reported: Since OTA-6 on Bq Aquaris 4.5, the new messaging app is just unbearably slow. The app is very unresponsive and everything seems to take very long. Opening the app takes about 5 seconds, displaying contact names instead of numbers another 5 secs, opening a chat >=5 secs, sending message after pressing button some 3 seconds etc. Sometimes the app sort of pauses while typing, then after a few seconds showing the characters that have been entered. Unfortunately, the latency in the app is so bad it is almost unusable. ** Affects: messaging-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1492161 Title: Messaging app sluggish after OTA-6 Status in messaging-app package in Ubuntu: New Bug description: Since OTA-6 on Bq Aquaris 4.5, the new messaging app is just unbearably slow. The app is very unresponsive and everything seems to take very long. Opening the app takes about 5 seconds, displaying contact names instead of numbers another 5 secs, opening a chat >=5 secs, sending message after pressing button some 3 seconds etc. Sometimes the app sort of pauses while typing, then after a few seconds showing the characters that have been entered. Unfortunately, the latency in the app is so bad it is almost unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1492161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491566] Re: Greeter and edges not responsive after an incoming SMS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity-system-compositor (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1491566 Title: Greeter and edges not responsive after an incoming SMS Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491566] Re: Greeter and edges not responsive after an incoming SMS
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: qtmir (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1491566 Title: Greeter and edges not responsive after an incoming SMS Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492126] Re: [wily-proposed only] NetworkManager crashed with SIGSEGV in ofono_enumerate_devices_done()
Also from journalctl on Wily with nm 0.9.10: NetworkManager[806]: SCPlugin-Ofono: file doesn't exist: /var/lib/ofono ofono is not installed on that desktop which does not need it anyway -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1492126 Title: [wily-proposed only] NetworkManager crashed with SIGSEGV in ofono_enumerate_devices_done() Status in network-manager package in Ubuntu: Confirmed Bug description: This can be trivially reproduced by installing the wily-proposed network-manager on i386 and rebooting. This is also spotted by systemd's autopkgtest (http://autopkgtest.ubuntu.com/packages/s/systemd/wily/i386/). In the journal I see Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemAdded' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:2506: signal 'ModemRemoved' is invalid for instance '0x997d760' of type 'GDBusProxy' Sep 04 08:32:15 autopkgtest NetworkManager[718]: (NetworkManager:718): GLib-CRITICAL **: g_variant_get_va: assertion 'value != NULL' failed Sep 04 08:32:15 autopkgtest systemd[1]: NetworkManager.service: Main process exited, code=dumped, status=11/SEGV I suppose the g_critical is not the thing it fails on, as that would be a SIGABRT. ProblemType: Crash DistroRelease: Ubuntu 15.10 Package: network-manager 1.0.4-0ubuntu2 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 ApportVersion: 2.18-0ubuntu9 Architecture: i386 Date: Fri Sep 4 08:40:19 2015 ExecutablePath: /usr/sbin/NetworkManager ExecutableTimestamp: 1440792479 IpRoute: default via 10.0.2.2 dev eth0 10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true ProcCmdline: /usr/sbin/NetworkManager --no-daemon ProcCwd: / ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SegvAnalysis: Segfault happened at: 0xb701f259 : mov 0xc(%esi),%edi PC (0xb701f259) ok source "0xc(%esi)" (0x000c) not located in a known VMA region (needed readable region)! destination "%edi" ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: network-manager StacktraceTop: g_variant_iter_loop () from /lib/i386-linux-gnu/libglib-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/NetworkManager/libnm-wwan.so ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 ?? () from /usr/lib/i386-linux-gnu/libgio-2.0.so.0 Title: NetworkManager crashed with SIGSEGV in g_variant_iter_loop() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 8: Error: NetworkManager is not running. nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 8: Error: NetworkManager is not running. nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1492126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328119] Re: [sdk] Scrollbars are too thin and transparent to be useful
there is a new scrollbar design under way ** Changed in: ubuntu-ux Assignee: Jamie Young (jamiedawsonyoung) => Jouni Helminen (jounihelminen) ** Changed in: ubuntu-ux Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1328119 Title: [sdk] Scrollbars are too thin and transparent to be useful Status in Ubuntu UI Toolkit: Triaged Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Triaged Bug description: Using the code from this branch https://code.launchpad.net/~kalikiana/ubuntu-ui-toolkit/interactiveThumb/+merge/218307 which is practically being merged into trunk now. The scrollbars are too thin and too transparent. They blend with the background and with the content, and are too hard to see to be useful for anything. Please make them more noticeable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1328119/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481798] Re: package:modemmanager:1.4.10-1:subprocess installed post-installation script returned error exit status 100
I had this ame error last night when attempting to update xubuntu 15.04 to 15.10.. left system unusable -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1481798 Title: package:modemmanager:1.4.10-1:subprocess installed post-installation script returned error exit status 100 Status in modemmanager package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding modemmanager. This problem was most recently seen with version 1.4.10-1, the problem page at https://errors.ubuntu.com/problem/abc807de9d9c87d965fea31c865192edb30b6738 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1481798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383454] Re: [design] Indicator menu separators look bad
My understanding is that the extra lines are caused by an empty list items that has only the separator but no content. Why there are any such items in the menus is another question. Anyway the extra lines make the UI look broken and should be removed. ** Description changed: The indicator style changed recently. And the new style for the separators between sections of an indicator look like two lines separated by some space. It doesn't look great to my eye. Screenshot attached. I asked Nick about it and he said that we don't have visual designs for that yet. + + + Desired solution: + + Remove the extra lines. They just look wrong. ** Changed in: ubuntu-ux Status: Triaged => 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/1383454 Title: [design] Indicator menu separators look bad Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: Incomplete Bug description: The indicator style changed recently. And the new style for the separators between sections of an indicator look like two lines separated by some space. It doesn't look great to my eye. Screenshot attached. I asked Nick about it and he said that we don't have visual designs for that yet. Desired solution: Remove the extra lines. They just look wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1383454/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492168] [NEW] [wily-proposed] --config option not respected any more (causes test failures)
Public bug reported: Pretty much all NM integration tests fail on the wily-proposed version (1.0.4), as NM tears down the (fake) "remote" side of the hwsim wifi and veth interfaces. Turns out this is due to not respecting the local --config option any more, which blacklists these devices to avoid NM tearing them down at startup: $ NetworkManager --log-level=debug --debug --config=/tmp/tmpyehdrfvu/NetworkManager.conf NetworkManager-Message: No config file found or given; using /etc/NetworkManager/NetworkManager.conf NetworkManager[5227]: Read config: /etc/NetworkManager/NetworkManager.conf [...] In the Ubuntu packaging bzr I reverted most of the disabling of tests, and also tuned the timeouts back down to reasonable values. On top of that, if you change --- debian/tests/nm 2015-09-04 09:06:44 + +++ debian/tests/nm 2015-09-04 09:07:05 + @@ -75,7 +75,8 @@ blacklist += ';' blacklist += 'mac:%s' % f.read().strip() -conf = os.path.join(self.workdir, 'NetworkManager.conf') +#conf = os.path.join(self.workdir, 'NetworkManager.conf') +conf = '/etc/NetworkManager/NetworkManager.conf' extra_main = '' if not auto_connect: extra_main += 'no-auto-default=*\n' to work around this bug, all the tests succeed again, at least on amd64. On i386 they still fail because NM crashes right away (bug 1492126). ** Affects: network-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1492168 Title: [wily-proposed] --config option not respected any more (causes test failures) Status in network-manager package in Ubuntu: New Bug description: Pretty much all NM integration tests fail on the wily-proposed version (1.0.4), as NM tears down the (fake) "remote" side of the hwsim wifi and veth interfaces. Turns out this is due to not respecting the local --config option any more, which blacklists these devices to avoid NM tearing them down at startup: $ NetworkManager --log-level=debug --debug --config=/tmp/tmpyehdrfvu/NetworkManager.conf NetworkManager-Message: No config file found or given; using /etc/NetworkManager/NetworkManager.conf NetworkManager[5227]: Read config: /etc/NetworkManager/NetworkManager.conf [...] In the Ubuntu packaging bzr I reverted most of the disabling of tests, and also tuned the timeouts back down to reasonable values. On top of that, if you change --- debian/tests/nm 2015-09-04 09:06:44 + +++ debian/tests/nm 2015-09-04 09:07:05 + @@ -75,7 +75,8 @@ blacklist += ';' blacklist += 'mac:%s' % f.read().strip() -conf = os.path.join(self.workdir, 'NetworkManager.conf') +#conf = os.path.join(self.workdir, 'NetworkManager.conf') +conf = '/etc/NetworkManager/NetworkManager.conf' extra_main = '' if not auto_connect: extra_main += 'no-auto-default=*\n' to work around this bug, all the tests succeed again, at least on amd64. On i386 they still fail because NM crashes right away (bug 1492126). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1492168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1462664] Re: [Ubuntu Phone] With WIFI = ON the GPS stops
is there any news about this bug? it was raised to Critical more than 2 months ago :) -- 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/1462664 Title: [Ubuntu Phone] With WIFI = ON the GPS stops Status in Canonical System Image: Confirmed Status in Oxide: New Status in ubuntu-system-settings: New Status in location-service package in Ubuntu: Confirmed Bug description: Hi! Steps: 1. Enable WIFI = ON on phone. 2. Run one of these apps: GPS Navigation, HERE maps, Sensor Status. 3. Drive. 4. When you'll be into a WIFI area as a town or city, I'm thinking the WIFI will try to search WIFIs and then the GPS will stop, the GPS apps will not receive more new positions from the GPS. Extra info1: If you had GPS Navigation & Sensor running, both of them will not receive new GPS positions from the device. If you restart for example GPS Navigation, GPS Navigation will receive new positions, but Sensor Status not, until you restart it too. Extra info2: When the GPS stops the icon in the status disappears, but it you kill and relaunch the app, the icon will appear again. Thanks in advance! To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462664/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350806] Re: [switcher] Apps in spread should have icon to help distinguish between them
** Changed in: ubuntu-ux Status: Triaged => In Progress -- 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/1350806 Title: [switcher] Apps in spread should have icon to help distinguish between them Status in Ubuntu UX: In Progress Status in unity8 package in Ubuntu: Incomplete Status in unity8 package in Ubuntu RTM: Incomplete Bug description: As summary, it is hard in spread browse between apps, many apps look the same at first glance, adding an app icon may help Desired design: Add white overlay bar on top of the spread items. Anchored at the bottom of an item. Height 8 gu. Opacity 0.85. Add button at the bottom left of the spread items above the white overlay bar. Icon height 6 gu. Left margin 1 gu. Vertically centered to the the white overlay. UbuntuShape radius medium. BorderSource: "none". See Right edge documentation: https://docs.google.com/a/canonical.com/document/d/1FC_- 5yz5kPy_ZvTphaqxOgI5BPnALFbxRAO4eJkzlf8/edit#heading=h.rutyq59eqmc1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1350806/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492161] Re: Messaging app sluggish after OTA-6
Actually, after restarting the phone, displaying contact names took even longer, this time 15 seconds! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1492161 Title: Messaging app sluggish after OTA-6 Status in messaging-app package in Ubuntu: New Bug description: Since OTA-6 on Bq Aquaris 4.5, the new messaging app is just unbearably slow. The app is very unresponsive and everything seems to take very long. Opening the app takes about 5 seconds, displaying contact names instead of numbers another 5 secs, opening a chat >=5 secs, sending message after pressing button some 3 seconds etc. Sometimes the app sort of pauses while typing, then after a few seconds showing the characters that have been entered. Unfortunately, the latency in the app is so bad it is almost unusable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1492161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432171] Re: [udev] Shows "starting version 219" boot message even with "quiet"
happening on kubuntu 15.04, installed with some problems. since it's cosmetic I wait for next upgrade... -- 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/1432171 Title: [udev] Shows "starting version 219" boot message even with "quiet" Status in systemd package in Ubuntu: Fix Released Bug description: Everytime the system is booted up I get a "Starting version 219" which it seems is the version number for systemd. udev version: 219-4ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1432171/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457874] Re: [scopes] nearby: "Expected the recommendations to be arranged based on distance, or to have filters to allow users to define "
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1457874 Title: [scopes] nearby: "Expected the recommendations to be arranged based on distance, or to have filters to allow users to define " Status in Ubuntu UX: In Progress Status in unity8 package in Ubuntu: New Bug description: "The recommendation should be based on distance" -- UX Comment -- This is part of a bigger redesign project (Scopes filters) and it can't be fixed as a single bug. The desired resolution and specs will be updated as soon as they are available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1457874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371846] Re: [SDK] no way to disable PageHeadState actions highlighting
We have a new palette structure which should help. Finished the light theme, dark theme to be done next ** Changed in: ubuntu-ux Assignee: Jouni Helminen (jounihelminen) => (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) => Jamie Young (jamiedawsonyoung) -- 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/1371846 Title: [SDK] no way to disable PageHeadState actions highlighting Status in Ubuntu UX: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: On applications with a dark theme (eg, Authenticator, Blabble, Utudu) the highlight color of the PageHeadState actions is very noticeable. This is easily seen by simply pressing one of the actions. When using a light theme, the effect is much more subtle. It would be nice to be able to disable the highlight or to set the highlight to a custom color. Setting as rtm14 with High priority since as an application writer it is very frustrating not being able to adjust this when using dark colors for the theme. On a possibly related note-- perhaps this is all configurable via Theme, but I've tried several times to figure out to do it. There appears to be no documentation on it (and I've mentioned this at least 3 times to people that we need it). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1371846/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492168] Re: [wily-proposed] --config option not respected any more (causes test failures)
** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1492168 Title: [wily-proposed] --config option not respected any more (causes test failures) Status in network-manager package in Ubuntu: New Bug description: Pretty much all NM integration tests fail on the wily-proposed version (1.0.4), as NM tears down the (fake) "remote" side of the hwsim wifi and veth interfaces. Turns out this is due to not respecting the local --config option any more, which blacklists these devices to avoid NM tearing them down at startup: $ NetworkManager --log-level=debug --debug --config=/tmp/tmpyehdrfvu/NetworkManager.conf NetworkManager-Message: No config file found or given; using /etc/NetworkManager/NetworkManager.conf NetworkManager[5227]: Read config: /etc/NetworkManager/NetworkManager.conf [...] In the Ubuntu packaging bzr I reverted most of the disabling of tests, and also tuned the timeouts back down to reasonable values. On top of that, if you change --- debian/tests/nm 2015-09-04 09:06:44 + +++ debian/tests/nm 2015-09-04 09:07:05 + @@ -75,7 +75,8 @@ blacklist += ';' blacklist += 'mac:%s' % f.read().strip() -conf = os.path.join(self.workdir, 'NetworkManager.conf') +#conf = os.path.join(self.workdir, 'NetworkManager.conf') +conf = '/etc/NetworkManager/NetworkManager.conf' extra_main = '' if not auto_connect: extra_main += 'no-auto-default=*\n' to work around this bug, all the tests succeed again, at least on amd64. On i386 they still fail because NM crashes right away (bug 1492126). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1492168/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492157] Re: ibus-ui-gtk3 crashed with SIGSEGV in g_variant_type_new_tuple()
This is what is logged when the crashes have happened: (gnome-shell:1570): GLib-GObject-WARNING **: /build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gclosure.c:721: unable to remove uninstalled invalidation notifier: 0xb642c490 (0x8f42450) gnome-session[1522]: ** gnome-session[1522]: GLib-GObject:ERROR:/build/glib2.0-M4BESt/glib2.0-2.45.6/./gobject/gsignal.c:684:handler_unref_R: assertion failed: (hlist->tail_after == handler) gnome-session[1522]: WARNING: Application 'gnome-shell.desktop' killed by signal 6 polkitd(authority=local)[818]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.71, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus) gnome-session[1522]: gnome-session[1522]: WARNING: Application 'gnome-shell.desktop' killed by signal 6 gnome-session[1522]: current session already has an ibus-daemon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1492157 Title: ibus-ui-gtk3 crashed with SIGSEGV in g_variant_type_new_tuple() Status in ibus package in Ubuntu: New Bug description: This happened with a Wily gnome-shell session: - open nautilus - click on its top bar to get 'Move To Workspace Down' and got a cascade of crashes, ending to the session crashing: - first crash: tracker-miner-fs - then ibus-ui-gtk3 - and finally gnome-shell when i right click on the crashed files, apport simply ignore to send the rapoort. So i join the files here. Strangely 'ubuntu-bug ibus-ui-gtk3' warns that this package does not exist. Effectively there is no such package into the archive. Note: that happen also without installed/activated 'extensions' from gnome.org ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ibus 1.5.10-1ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-7.7-generic 4.2.0 Uname: Linux 4.2.0-7-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu9 Architecture: i386 CurrentDesktop: GNOME Date: Fri Sep 4 10:18:08 2015 SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1492157/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1430694] Re: Update Facebook permissions to 2.0 API
** Changed in: account-plugins Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1430694 Title: Update Facebook permissions to 2.0 API Status in Online Accounts: Account plugins: Fix Released Status in Canonical System Image: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in account-plugins source package in Trusty: Fix Released Status in account-plugins source package in Utopic: Fix Released Status in account-plugins package in Ubuntu RTM: Fix Released Bug description: The 1.0 API is being deprecated on April 30, 2015. [Impact] Depending on how facebook decides to handle the deprecation, there's the possibility that creating facebook accounts from Ubuntu Online Accounts will just stop working, if our OAuth request (which uses deprecated parameters) gets declined. [Test case] Until the deprecation actually takes place, we won't be able to reproduce the bug. According to the Facebook official documentation, the v1.0 API will stop working on April 30th, 2015: https://developers.facebook.com/docs/apps/changelog [Regression potential] Very low: the new Facebook v2.0 API is already active, and we've been using it in Vivid without issues. A quick smoke test (just create a Facebook account from the System Settings -> Online Accounts pane) is anyway advised, to be absolutely sure. To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1430694/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1159795] Re: foursquare plugin fails with redirect_uri_mismatch
** Changed in: account-plugins Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1159795 Title: foursquare plugin fails with redirect_uri_mismatch Status in Online Accounts: Account plugins: Fix Released Status in account-plugins package in Ubuntu: Fix Released Status in account-plugins source package in Raring: Won't Fix Bug description: When trying to add a new foursquare account, the signon-ui webview loads a page with the following content: Connecting failed Ubuntu has a configuration problem and was unable to connect to your foursquare account Cause of error: redirect_uri_mismatch To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1159795/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449628] Re: [Icons] X-Ubuntu-Splash-Color=#ffffff yields #f5f5f5
default background colour changed to white with Tim Peeters ** Changed in: ubuntu-ux Status: Triaged => Fix Released -- 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/1449628 Title: [Icons] X-Ubuntu-Splash-Color=#ff yields #f5f5f5 Status in Ubuntu UX: Fix Released Status in unity8 package in Ubuntu: Incomplete Bug description: I tried using a white-background app icon with a white-background splash color, but they didn't render the same. I took a screenshot and discovered that unity8 was rendering a white splash (#ff) as #f5f5f5. Switching my app icon to use that same off white as its background fixed the visual glitch. But why does unity8 do that? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1449628/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1486008] Re: leading actions width is too small making it very difficult to press
** Summary changed:
- leading actions width is too small making it very difficult to press on Nexus
4 (mako)
+ leading actions width is too small making it very difficult to press
--
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/1486008
Title:
leading actions width is too small making it very difficult to press
Status in Ubuntu UX:
Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
Since a recent update to the ListItem leading actions in
Ubuntu.Components 1.2, where the width of the action was clamped, the
width is too small to press comfortably on a phone resulting in it
missing 9 out of 10 tries. It affects the usability of the action and
may be become a release blocker for apps that have recently switched
over to the new list items.
Sample App
import QtQuick 2.4
import Ubuntu.Components 1.2
MainView {
applicationName: "testdelete.nik90"
width: units.gu(100)
height: units.gu(75)
Page {
title: "Swipe to Delete"
ListItem {
id: listItem
anchors.top: parent.top
Label {
text: "Swipe me right to delete this listitem"
wrapMode: Text.WordWrap
anchors { left: parent.left; leftMargin: units.gu(2); right:
parent.right; verticalCenter: parent.verticalCenter }
}
leadingActions: ListItemActions {
actions: [
Action {
iconName: "delete"
onTriggered: listItem.destroy()
}
]
}
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1486008/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1457874] Re: [scopes] nearby: "Expected the recommendations to be arranged based on distance, or to have filters to allow users to define "
** Description changed: "The recommendation should be based on distance" - -- UX Comment -- - This is part of a bigger redesign project (Scopes filters) and it can't - be fixed as a single bug. The desired resolution and specs will be - updated as soon as they are available. + We are currently working on the implementation of filter widgets for + scopes. Every scope author will be able to choose what filters to use + for each scope based on the available list of widgets. For this + particular use case, we recommend to use a combination of "Location + widget" (with current lcoation as its default) and "One way slider + widget' displaying distance range in miles (within 1 miles, within 3 + miles, within 5 miles, within 10 miles). Also, we could consider + offering a 'sort by' filter with the following values: 'relevance', + 'distance', 'rating'. + + For further information, please see the Filter widgets in Scopes + specification: + https://docs.google.com/document/d/1xWNpO3UUdmVak0NZ63yaDTF8Il0P_UF96Y2eOiBVBz0/edit ** 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/1457874 Title: [scopes] nearby: "Expected the recommendations to be arranged based on distance, or to have filters to allow users to define " Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: New Bug description: "The recommendation should be based on distance" -- UX Comment -- We are currently working on the implementation of filter widgets for scopes. Every scope author will be able to choose what filters to use for each scope based on the available list of widgets. For this particular use case, we recommend to use a combination of "Location widget" (with current lcoation as its default) and "One way slider widget' displaying distance range in miles (within 1 miles, within 3 miles, within 5 miles, within 10 miles). Also, we could consider offering a 'sort by' filter with the following values: 'relevance', 'distance', 'rating'. For further information, please see the Filter widgets in Scopes specification: https://docs.google.com/document/d/1xWNpO3UUdmVak0NZ63yaDTF8Il0P_UF96Y2eOiBVBz0/edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1457874/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1245381] Re: Add e-mail scopes to Windows Live plugin
** Changed in: account-plugins Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1245381 Title: Add e-mail scopes to Windows Live plugin Status in Online Accounts: Account plugins: Fix Released Status in account-plugins package in Ubuntu: Fix Released Bug description: Now that Outlook.com provides IMAP access and EDS supports it, we need to extend the Windows Live plugin and request these OAuth scopes: wl.imap wl.offline_access To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1245381/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1041744] Re: Can't log in to flickr account that's linked to a Google login
** Changed in: account-plugins Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1041744 Title: Can't log in to flickr account that's linked to a Google login Status in Online Accounts: Account plugins: Fix Released Status in account-plugins package in Ubuntu: Fix Released Bug description: When I try to add my Flickr account in the "Online accounts" preferences screen, the link to log in using Google/Facebook are "dead". Clicking them does nothing. This means I can't add my account. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: account-plugin-flickr 0.5-0ubuntu3 ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1 Uname: Linux 3.5.0-10-generic x86_64 ApportVersion: 2.5.1-0ubuntu2 Architecture: amd64 Date: Sun Aug 26 07:55:00 2012 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=nl_NL.UTF-8 SHELL=/bin/bash SourcePackage: account-plugins UpgradeStatus: Upgraded to quantal on 2011-12-03 (266 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/account-plugins/+bug/1041744/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1477146] Re: [inconsistency] Contacts list opened from the Dialer shows "+ Create New" on the first place
Marked as Fix Committed from UX side because the correct specification is provided already ** Changed in: ubuntu-ux Status: New => Fix Committed ** Changed in: ubuntu-ux Importance: Undecided => Medium ** Changed in: ubuntu-ux Assignee: (unassigned) => Olga Kemmet (olga-kemmet) ** Description changed: When You open Contacts from the Dialer, a "+ Create New" item is shown as the first in the list. This takes too much space and is pretty obtrusive, especially in the "Favourites" tab, which is supposed to contain already existing contacts only. The solution could be to change this item to a draggable " + " in the bottom of the screen, the same way as it works in the stand-alone Contacts app already. Version: 0.1+15.04.20150415.2-0ubuntu1 + + - UX comment --- + + The telephony suit specifications already have a solution for this + problem. The behaviour of contacts within the dialer app will be aligned + with the behaviour in the AB app. + + Please refer to the latest UX spec: + https://docs.google.com/document/d/1BRy9 + -DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit#heading=h.u6f263x6045p ** Also affects: dialer-app (Ubuntu) Importance: Undecided Status: New -- 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/1477146 Title: [inconsistency] Contacts list opened from the Dialer shows "+ Create New" on the first place Status in Ubuntu UX: Fix Committed Status in address-book-app package in Ubuntu: New Status in dialer-app package in Ubuntu: New Bug description: When You open Contacts from the Dialer, a "+ Create New" item is shown as the first in the list. This takes too much space and is pretty obtrusive, especially in the "Favourites" tab, which is supposed to contain already existing contacts only. The solution could be to change this item to a draggable " + " in the bottom of the screen, the same way as it works in the stand-alone Contacts app already. Version: 0.1+15.04.20150415.2-0ubuntu1 - UX comment --- The telephony suit specifications already have a solution for this problem. The behaviour of contacts within the dialer app will be aligned with the behaviour in the AB app. Please refer to the latest UX spec: https://docs.google.com/document/d/1BRy9 -DEXr3A1D7PHkJaXmjbe7xbRmxKkzANXuu-F6lc/edit#heading=h.u6f263x6045p To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1477146/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346126] Re: [Dash] Departments look wrong on wider screens
Attached screen shot from current implementation looks solved and done! ** Attachment added: "IMG_2015-09-04 10:29:23.jpg" https://bugs.launchpad.net/ubuntu-ux/+bug/1346126/+attachment/4457226/+files/IMG_2015-09-04%2010%3A29%3A23.jpg -- 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/1346126 Title: [Dash] Departments look wrong on wider screens Status in Ubuntu UX: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: Just flashed image 141 to my Nexus7. All departments dropdown not full screen width and anchored to the right See screenshot = Relevant spec: https://sites.google.com/a/canonical.com/unity8dash/toolkit/2-navigation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1346126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1458235] Re: [scopes] Allow users to set arbitrary location for scopes.
** Description changed: Currently I can't set my location manually for any scope. They get it somehow automatically, most of the time wrongly. It would be nice if a user could somehow select the location he/she wants. + + -- UX Comment -- + + This will be soon possible with the 'Location filter widget' - currently + under development. For further information please refer to the Filter + wisgets in Scopes design specification: + https://docs.google.com/document/d/1xWNpO3UUdmVak0NZ63yaDTF8Il0P_UF96Y2eOiBVBz0/edit ** 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/1458235 Title: [scopes] Allow users to set arbitrary location for scopes. Status in Ubuntu UX: Fix Committed Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Bug description: Currently I can't set my location manually for any scope. They get it somehow automatically, most of the time wrongly. It would be nice if a user could somehow select the location he/she wants. -- UX Comment -- This will be soon possible with the 'Location filter widget' - currently under development. For further information please refer to the Filter wisgets in Scopes design specification: https://docs.google.com/document/d/1xWNpO3UUdmVak0NZ63yaDTF8Il0P_UF96Y2eOiBVBz0/edit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1458235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492180] [NEW] iwconfig reports wrong bitrate (6 Mb/s)
Public bug reported: Upgraded to Wily. iwconfig now says the Bitrate is 6 Mb/s when 'iw dev wlan0 link' seems to report the correct bitrate. Firmware iwlwifi-7260-13.ucode ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: wireless-tools 30~pre9-8ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 4 12:43:52 2015 Dependencies: gcc-5-base 5.2.1-15ubuntu5 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-15ubuntu5 libiw30 30~pre9-8ubuntu1 multiarch-support 2.21-0ubuntu4 InstallationDate: Installed on 2011-11-11 (1393 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: wireless-tools UpgradeStatus: Upgraded to wily on 2015-09-04 (0 days ago) ** Affects: wireless-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wireless-tools in Ubuntu. https://bugs.launchpad.net/bugs/1492180 Title: iwconfig reports wrong bitrate (6 Mb/s) Status in wireless-tools package in Ubuntu: New Bug description: Upgraded to Wily. iwconfig now says the Bitrate is 6 Mb/s when 'iw dev wlan0 link' seems to report the correct bitrate. Firmware iwlwifi-7260-13.ucode ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: wireless-tools 30~pre9-8ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.18-0ubuntu9 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Sep 4 12:43:52 2015 Dependencies: gcc-5-base 5.2.1-15ubuntu5 libc6 2.21-0ubuntu4 libgcc1 1:5.2.1-15ubuntu5 libiw30 30~pre9-8ubuntu1 multiarch-support 2.21-0ubuntu4 InstallationDate: Installed on 2011-11-11 (1393 days ago) InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) SourcePackage: wireless-tools UpgradeStatus: Upgraded to wily on 2015-09-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wireless-tools/+bug/1492180/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482251] Re: Transfer idicator should use a different label "Files" is not generic enough
** Changed in: ubuntu-ux Status: Triaged => Opinion -- 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/1482251 Title: Transfer idicator should use a different label "Files" is not generic enough Status in Ubuntu UX: Opinion Status in indicator-transfer package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: Now that we are integrating syncing (contacts,calendar, etc..) into the transfer indicator, the title of the indicator should be different from "files" . Today it show "files" if you expand the panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1482251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1453580] Re: package libgsm1:amd64 1.0.13-4 failed to install/upgrade: package libgsm1:amd64 is already installed and configured
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libgsm (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libgsm in Ubuntu. https://bugs.launchpad.net/bugs/1453580 Title: package libgsm1:amd64 1.0.13-4 failed to install/upgrade: package libgsm1:amd64 is already installed and configured Status in libgsm package in Ubuntu: Confirmed Bug description: when starting computer there is message in desktop ProblemType: Package DistroRelease: Ubuntu 14.04 Package: libgsm1:amd64 1.0.13-4 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.10 AptdaemonVersion: 1.1.1-1ubuntu5.1 Architecture: amd64 Date: Sun May 3 19:00:39 2015 Dependencies: gcc-4.9-base 4.9.1-0ubuntu1 libc6 2.19-0ubuntu6.6 libgcc1 1:4.9.1-0ubuntu1 multiarch-support 2.19-0ubuntu6.6 DuplicateSignature: package:libgsm1:amd64:1.0.13-4:package libgsm1:amd64 is already installed and configured ErrorMessage: package libgsm1:amd64 is already installed and configured InstallationDate: Installed on 2015-05-01 (8 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) SourcePackage: libgsm Title: package libgsm1:amd64 1.0.13-4 failed to install/upgrade: package libgsm1:amd64 is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgsm/+bug/1453580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346126] Re: [Dash] Departments look wrong on wider screens
** Description changed: Just flashed image 141 to my Nexus7. All departments dropdown not full screen width and anchored to the right See screenshot = Relevant spec: https://sites.google.com/a/canonical.com/unity8dash/toolkit/2-navigation + + + Desired resolution: Attached below screen shot from current + implementation looks solved and done! ** Changed in: ubuntu-ux Status: Triaged => In Progress ** 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/1346126 Title: [Dash] Departments look wrong on wider screens Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: Incomplete Bug description: Just flashed image 141 to my Nexus7. All departments dropdown not full screen width and anchored to the right See screenshot = Relevant spec: https://sites.google.com/a/canonical.com/unity8dash/toolkit/2-navigation Desired resolution: Attached below screen shot from current implementation looks solved and done! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1346126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492185] Re: unity8 crashes when running ubuntu keyboard test
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492185/+attachment/4457236/+files/syslog ** Description changed: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 + (extact same failure on mako, same rc-proposed image) + Reproduce: - phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess + phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash -- 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/1492185 Title: unity8 crashes when running ubuntu keyboard test Status in unity8 package in Ubuntu: New Bug description: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 (extact same failure on mako, same rc-proposed image) Reproduce: phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492185] [NEW] unity8 crashes when running ubuntu keyboard test
Public bug reported: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 (extact same failure on mako, same rc-proposed image) Reproduce: phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Attachment added: "unit8 log" https://bugs.launchpad.net/bugs/1492185/+attachment/4457234/+files/unity8.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1492185 Title: unity8 crashes when running ubuntu keyboard test Status in unity8 package in Ubuntu: New Bug description: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 (extact same failure on mako, same rc-proposed image) Reproduce: phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492185] Re: unity8 crashes when running ubuntu keyboard test
** Attachment added: "maliit-server log" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492185/+attachment/4457235/+files/maliit-server.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1492185 Title: unity8 crashes when running ubuntu keyboard test Status in unity8 package in Ubuntu: New Bug description: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 (extact same failure on mako, same rc-proposed image) Reproduce: phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492185] Re: unity8 crashes when running ubuntu keyboard test
The actual trigger appears to be when maliit restarts (which the tests do to enable extra introspection), so this can be reproduced by simply running "restart maliit-server" -- 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/1492185 Title: unity8 crashes when running ubuntu keyboard test Status in unity8 package in Ubuntu: New Bug description: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 (extact same failure on mako, same rc-proposed image) Reproduce: phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346126] Re: [Dash] Departments look wrong on wider screens
** Description changed: Just flashed image 141 to my Nexus7. All departments dropdown not full screen width and anchored to the right See screenshot = Relevant spec: https://sites.google.com/a/canonical.com/unity8dash/toolkit/2-navigation - - - Desired resolution: Attached below screen shot from current - implementation looks solved and done! -- 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/1346126 Title: [Dash] Departments look wrong on wider screens Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: Incomplete Bug description: Just flashed image 141 to my Nexus7. All departments dropdown not full screen width and anchored to the right See screenshot = Relevant spec: https://sites.google.com/a/canonical.com/unity8dash/toolkit/2-navigation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1346126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1486008] Re: leading actions width is too small making it very difficult to press
After OTA-6 and latest clock update I also have this issue with deleting
alarms.
--
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/1486008
Title:
leading actions width is too small making it very difficult to press
Status in Ubuntu UX:
Confirmed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
Since a recent update to the ListItem leading actions in
Ubuntu.Components 1.2, where the width of the action was clamped, the
width is too small to press comfortably on a phone resulting in it
missing 9 out of 10 tries. It affects the usability of the action and
may be become a release blocker for apps that have recently switched
over to the new list items.
Sample App
import QtQuick 2.4
import Ubuntu.Components 1.2
MainView {
applicationName: "testdelete.nik90"
width: units.gu(100)
height: units.gu(75)
Page {
title: "Swipe to Delete"
ListItem {
id: listItem
anchors.top: parent.top
Label {
text: "Swipe me right to delete this listitem"
wrapMode: Text.WordWrap
anchors { left: parent.left; leftMargin: units.gu(2); right:
parent.right; verticalCenter: parent.verticalCenter }
}
leadingActions: ListItemActions {
actions: [
Action {
iconName: "delete"
onTriggered: listItem.destroy()
}
]
}
}
}
}
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1486008/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312260] Re: [browser] There is no search in page option in webbrowser-app (like ctrl+F)
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1312260 Title: [browser] There is no search in page option in webbrowser-app (like ctrl+F) Status in Oxide: Fix Released Status in Ubuntu UX: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: Users will be able to find text in page (partial&exact match) - Function will be available in the Action Drawer --- --- --- --- --- UX Comment: Spec here https://docs.google.com/a/canonical.com/presentation/d/1Qrd4Flfs3EH-fI79IfrYgLdAx2nce-L7ve8NKLCX324/edit#slide=id.g187f4edfe_50 To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1312260/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492185] Re: unity8 crashes when running ubuntu keyboard test
I assigned you Daniel as I recall we had this same issue last week with the welcome wizard -- 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/1492185 Title: unity8 crashes when running ubuntu keyboard test Status in QtMir: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 (extact same failure on mako, same rc-proposed image) Reproduce: phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1492185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351660] Re: [wizard] After the wi-fi is authenticated, it doesn't open the next page automatically
** Changed in: ubuntu-ux Assignee: Olga Kemmet (olga-kemmet) => (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) => Andreea Pirvu (andreea-pirvu) -- 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/1351660 Title: [wizard] After the wi-fi is authenticated, it doesn't open the next page automatically Status in Ubuntu UX: Opinion Status in unity8 package in Ubuntu: Opinion Bug description: This is how android does it: Touch on the name of the network, and enter the password. The network will try to authenticate and if it's successfull, the wizard will advance automatically to the next step. On ubuntu, after we are connected we still have to click the continue button to advance to the next page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1351660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492185] Re: unity8 crashes when running ubuntu keyboard test
Seems to be crashing in the scene graph renderer? #0 0xb68c53ec in QSGOpaqueTextureMaterial::compare (this=0x23b9b00, o=0x23bf1d8) at scenegraph/util/qsgtexturematerial.cpp:295 #1 0xb68b3566 in QSGBatchRenderer::Renderer::prepareAlphaBatches (this=this@entry=0x15b8fd8) at scenegraph/coreapi/qsgbatchrenderer.cpp:1594 #2 0xb68baac4 in QSGBatchRenderer::Renderer::render (this=0x15b8fd8) at scenegraph/coreapi/qsgbatchrenderer.cpp:2544 #3 0xb68c1560 in QSGRenderer::renderScene (this=0x15b8fd8, bindable=...) at scenegraph/coreapi/qsgrenderer.cpp:206 #4 0xb68c18e8 in QSGRenderer::renderScene (this=, fboId=0) at scenegraph/coreapi/qsgrenderer.cpp:168 #5 0xb68cc2b4 in QSGRenderContext::renderNextFrame (this=0x1234498, renderer=0x15b8fd8, fboId=) at scenegraph/qsgcontext.cpp:554 #6 0xb68feab8 in QQuickWindowPrivate::renderSceneGraph (this=this@entry=0x12351b8, size=...) at items/qquickwindow.cpp:379 #7 0xb68df738 in QSGRenderThread::syncAndRender (this=this@entry=0x14f68a0) at scenegraph/qsgthreadedrenderloop.cpp:582 #8 0xb68e0908 in QSGRenderThread::run (this=0x14f68a0) at scenegraph/qsgthreadedrenderloop.cpp:663 #9 0xb63cf496 in ?? () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 #10 0xb6055490 in start_thread () from /lib/arm-linux-gnueabihf/libpthread.so.0 #11 0xb6216c4c in ?? () from /lib/arm-linux-gnueabihf/libc.so.6 -- 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/1492185 Title: unity8 crashes when running ubuntu keyboard test Status in QtMir: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 (extact same failure on mako, same rc-proposed image) Reproduce: phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1492185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492185] Re: unity8 crashes when running ubuntu keyboard test
Shell rejecting OSK's re-connection attempts, which is wrong. It shouldn't also crash... ** Changed in: unity8 (Ubuntu) Importance: Undecided => Critical ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) => Daniel d'Andrada (dandrader) ** Changed in: unity8 (Ubuntu) Status: New => Triaged ** Also affects: qtmir Importance: Undecided Status: New ** Changed in: qtmir Status: New => Triaged ** Changed in: qtmir Importance: Undecided => Critical ** Changed in: qtmir Assignee: (unassigned) => Daniel d'Andrada (dandrader) -- 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/1492185 Title: unity8 crashes when running ubuntu keyboard test Status in QtMir: Triaged Status in unity8 package in Ubuntu: Triaged Bug description: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 (extact same failure on mako, same rc-proposed image) Reproduce: phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1492185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488852] Re: dialer app window feels funny on windowed mode
** Description changed: while trying out simulated phone calls on nexus4 vivid+o+silo0 the dialer app has the big green dial/hangup button floating over the numbers if not sized to the expected phone formfactor (specifically sized smaller) so maybe this is a design question - should the dialer app have a fixed minimum? should the dialer app window even be allowed to resize ? and what to do if that minimum doesn't fit on screen well ? + + + - UX comment - + + The dialer app should have a set minimum window size on the desktop so that all functionalities are always visible and accessible. Ideally the window should not be resized for the time being. + If it is unavoidable to increase the window size then the additional GU can simply be filled with white space/the same background the dialer is using. + + For a greater user experience a longer term solution is to make the + dialer convergent, meaning it would use the multi column layout similar + to the AB and messaging apps. ** Changed in: ubuntu-ux Status: New => Fix Committed ** Summary changed: - dialer app window feels funny on windowed mode + [pocket desktop] + [dialer app] window feels funny on windowed mode -- 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/1488852 Title: [pocket desktop] + [dialer app] window feels funny on windowed mode Status in canonical-pocket-desktop: New Status in Ubuntu UX: Fix Committed Status in dialer-app package in Ubuntu: New Bug description: while trying out simulated phone calls on nexus4 vivid+o+silo0 the dialer app has the big green dial/hangup button floating over the numbers if not sized to the expected phone formfactor (specifically sized smaller) so maybe this is a design question - should the dialer app have a fixed minimum? should the dialer app window even be allowed to resize ? and what to do if that minimum doesn't fit on screen well ? - UX comment - The dialer app should have a set minimum window size on the desktop so that all functionalities are always visible and accessible. Ideally the window should not be resized for the time being. If it is unavoidable to increase the window size then the additional GU can simply be filled with white space/the same background the dialer is using. For a greater user experience a longer term solution is to make the dialer convergent, meaning it would use the multi column layout similar to the AB and messaging apps. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1488852/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492185] Re: unity8 crashes when running ubuntu keyboard test
** Attachment added: "_usr_bin_unity8.32011.crash" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492185/+attachment/4457239/+files/_usr_bin_unity8.32011.crash -- 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/1492185 Title: unity8 crashes when running ubuntu keyboard test Status in unity8 package in Ubuntu: New Bug description: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 (extact same failure on mako, same rc-proposed image) Reproduce: phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492185] Re: unity8 crashes when running ubuntu keyboard test
** Attachment added: "crash files" https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492185/+attachment/4457240/+files/1492185-crashes.zip -- 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/1492185 Title: unity8 crashes when running ubuntu keyboard test Status in unity8 package in Ubuntu: New Bug description: current build number: 105 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en last update: 2015-09-04 11:06:40 version version: 105 version ubuntu: 20150904 version device: 20150818-0b38025 version custom: 20150814-887-8-46 (extact same failure on mako, same rc-proposed image) Reproduce: phablet-test-run -v ubuntu_keyboard.tests.test_keyboard.UbuntuKeyboardTestsAccess What happens: unity8 crashes What should happen: unity8 should not crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1482251] Re: Transfer idicator should use a different label "Files" is not generic enough
Afak Files indicator is meant to dissapear from the phone. ** Description changed: Now that we are integrating syncing (contacts,calendar, etc..) into the transfer indicator, the title of the indicator should be different from "files" . Today it show "files" if you expand the panel. + + --- + + Afak Files indicator is meant to dissapear from the phone. -- 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/1482251 Title: Transfer idicator should use a different label "Files" is not generic enough Status in Ubuntu UX: Opinion Status in indicator-transfer package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: Now that we are integrating syncing (contacts,calendar, etc..) into the transfer indicator, the title of the indicator should be different from "files" . Today it show "files" if you expand the panel. --- Afak Files indicator is meant to dissapear from the phone. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1482251/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346126] Re: [Dash] Departments look wrong on wider screens
** Changed in: ubuntu-ux Assignee: Alex Milazzo (digitalalex) => Paty Davila (dizzypaty) ** Changed in: ubuntu-ux Status: Fix Committed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1346126 Title: [Dash] Departments look wrong on wider screens Status in Ubuntu UX: Incomplete Status in unity8 package in Ubuntu: Incomplete Bug description: Just flashed image 141 to my Nexus7. All departments dropdown not full screen width and anchored to the right See screenshot = Relevant spec: https://sites.google.com/a/canonical.com/unity8dash/toolkit/2-navigation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1346126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374996] Re: [sdk] Instead of an overflow in the header, pull down more to reveal more options
** Changed in: ubuntu-ux Assignee: Giorgio Venturi (giorgio-venturi) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: Opinion => Won't Fix -- 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/1374996 Title: [sdk] Instead of an overflow in the header, pull down more to reveal more options Status in Ubuntu UX: Won't Fix Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: Instead of having buttons to open an overflow that shows tabs or additional actions, what if we let the user pull down more after the header was revealed, and the header extends (contents is dragged more down revealing more just under the header) to reveal the additional options? So you get a second (and third, ...?) row under the header that shows more buttons? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1374996/+subscriptions -- Mailing list: https://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 1491566] Re: Greeter and edges not responsive after an incoming SMS
Actually, I tried buttons, there was no visible reaction on the presses: * volume buttons (even attempted to get a screenshot, but it is not present on the phone, so it did not work) * power button. could not even reboot the phone (or maybe have not waited long enough? pressed on it for about a minute), had to do reboot via shell The only part that still was updating on the screen - notification area. Noticed, because charging was indicated upon connection of the phone to the PC. On Fri, Sep 4, 2015 at 10:59 AM, Launchpad Bug Tracker < 1491...@bugs.launchpad.net> wrote: > Status changed to 'Confirmed' because the bug affects multiple users. > > ** Changed in: unity-system-compositor (Ubuntu) >Status: New => Confirmed > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1491566 > > Title: > Greeter and edges not responsive after an incoming SMS > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1491566 Title: Greeter and edges not responsive after an incoming SMS Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1420748] Re: Always reserve space for three actions in header
** Changed in: ubuntu-ux Assignee: Giorgio Venturi (giorgio-venturi) => Olga Kemmet (olga-kemmet) ** Changed in: ubuntu-ux Status: Opinion => Won't Fix ** Summary changed: - Always reserve space for three actions in header + [sdk] Always reserve space for three actions in header -- 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/1420748 Title: [sdk] Always reserve space for three actions in header Status in Ubuntu UX: Won't Fix Status in ubuntu-ui-toolkit package in Ubuntu: Won't Fix Bug description: Currently there is room for 3 actions directly in the header, including a back/cancel button or tabs button on the left side. So without a button on the left, there is room for 3 actions on the right, but when there is an action on the left, only 2 actions are allowed on the right side. I think this is confusing for the users (some times you have 3 buttons, and some times 1 normal button plus an overflow button with two actions in the overflow) and not really necessary. I propose to (on a phone) always reserve space for 3 actions on the right side in the header, even if there is an action in the left of the header. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1420748/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1437006] Re: [browser] bottom edge gesture graphic should have a numeric representation of the number of open tabs
** Changed in: ubuntu-ux Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1437006 Title: [browser] bottom edge gesture graphic should have a numeric representation of the number of open tabs Status in Ubuntu UX: Fix Released Status in webbrowser-app: Fix Released Status in webbrowser-app package in Ubuntu: Fix Released Bug description: This is a UX issue. Currently, the bottom edge graphic is a squat caret. Aside from the caret, it would be nice to have a numeric display of the number of open tabs. Today while trying to use a website, my actions resulted in the opening of multiple tabs, but there was no change in the browser that would suggest any tabs were opened. UX resolution-the phone visual spec is updated to include the bottom edge hint with numerical display, page 23 https://docs.google.com/a/canonical.com/presentation/d/1woHjO8K4iqyVZZlfQ4BXL0DhYbwkEmZ7wvcUhYzHDRk/edit?pli=1#slide=id.g986756eaf_6_0 A new asset for the bottom edge tab has been sent to Olivier To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1437006/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323691] Re: [Scopes] "back" button behaves unpredictably from selected search results
** Description changed: Steps to reproduce: 1. Open scopes scope 2. Search for "redd" => you will get some scopes including reddit 3. Click on the reddit scope 4. Click back button You will be taken to the scopes scope, instead of to the search results. Desired solution Back button should take you back to the search results page [UX Comment] Updating this bug as search is partially fixed/scopes-scope no longer present. Steps to reproduce: 1. Open today scope 2. Search for "dino" 3. Click on a result 4. Click back button 5. Today Scope shown Correct behaviour: 1. Open news scope 2. Search for "a" 3. Click on a result from a child scope (e.g. weather) 4. Click back button 5. Search results are shown + + + -- UX Comment -- + (updated 4/09/2015) + + The desaired solution for this bug is specified in the Filter widgets in + Scopes specification: "Searching and filtering journeys" --> + https://docs.google.com/document/d/1xWNpO3UUdmVak0NZ63yaDTF8Il0P_UF96Y2eOiBVBz0/edit#heading=h.7mxnfoxz2x47 -- 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/1323691 Title: [Scopes] "back" button behaves unpredictably from selected search results Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: 1. Open scopes scope 2. Search for "redd" => you will get some scopes including reddit 3. Click on the reddit scope 4. Click back button You will be taken to the scopes scope, instead of to the search results. Desired solution Back button should take you back to the search results page [UX Comment] Updating this bug as search is partially fixed/scopes-scope no longer present. Steps to reproduce: 1. Open today scope 2. Search for "dino" 3. Click on a result 4. Click back button 5. Today Scope shown Correct behaviour: 1. Open news scope 2. Search for "a" 3. Click on a result from a child scope (e.g. weather) 4. Click back button 5. Search results are shown -- UX Comment -- (updated 4/09/2015) The desaired solution for this bug is specified in the Filter widgets in Scopes specification: "Searching and filtering journeys" --> https://docs.google.com/document/d/1xWNpO3UUdmVak0NZ63yaDTF8Il0P_UF96Y2eOiBVBz0/edit#heading=h.7mxnfoxz2x47 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1323691/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491484] Re: Anker keyboard doesn't send key events to krillin
After some more analysis the BT HID stack in the krillin kernel seems to be horrible broken. We will not going to fix but replace this pretty soon with a complete new bluetooth stack which will be based on an recent upstream kernel (4.2). We have to wait until this is done until we have a solution for this bug. However just conencting a keyboard should be possible once the mentioned kernel fix is merged and published, it will just not allow you to enter anything. -- 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/1491484 Title: Anker keyboard doesn't send key events to krillin Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: In Progress Bug description: I have an Anker BT keyboard which seems to work fine on the Nexus 4 with Android, but when I use it with Krillin and Ubuntu it doesn't seem to receive keypresses. In fact I have used a hack boot.img to get it to even connect. The exact model is : http://www.amazon.co.uk /Compact-Wireless-Bluetooth-Keyboard- Rechargeable/dp/B00PIMRCFG/ref=sr_1_2?ie=UTF8&qid=1441209196&sr=8-2&keywords=anker+bluetooth+keyboard phablet@ubuntu-phablet:~$ system-image-cli -i current build number: 114 device name: krillin channel: ubuntu-touch/rc-proposed/bq-aquaris.en last update: 2015-09-02 08:01:15 version version: 114 version ubuntu: 20150902 version device: 20150821-736d127 version custom: 20150821-887-33-32-vivid To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491484/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480785] Re: ofono does not start after upgrade (initclt stalls when sending an event)
Got it again, the android event seems stalled too and maybe that's stopping other things: root@ubuntu-phablet:/home/phablet# ps -ef|grep initctl root 749 562 0 12:38 ?00:00:01 initctl emit android root 1852 753 0 12:38 ?00:00:00 initctl emit rild-ready OFONO_RIL_DEVICE=mtk OFONO_RIL_NUM_SIM_SLOTS=1 root 3798 3769 0 12:42 pts/900:00:00 grep --color=auto initctl root@ubuntu-phablet:/home/phablet# ps awx|grep mountall 3786 pts/9S+ 0:00 grep --color=auto mountall root@ubuntu-phablet:/home/phablet# initctl list mountnfs-bootclean.sh start/running rsyslog start/running, process 697 udev start/running, process 884 upstart-udev-bridge start/running, process 777 whoopsie start/running, process 1554 mountall-net stop/waiting mtp-state stop/waiting passwd stop/waiting rc stop/waiting tty4 stop/waiting ureadahead-other stop/waiting apport start/running rild start/running, process 753 bluetooth-touch-grouper stop/waiting click-system-hooks stop/waiting console-setup stop/waiting hwclock-save stop/waiting plymouth-log stop/waiting tty5 stop/waiting zram-touch stop/waiting mountall.sh start/running urfkill start/running, process 895 procps-instance stop/waiting rfkill-store stop/waiting set.pretty-hostname stop/waiting tethering stop/waiting ubuntu-location-provider-here-posclientd stop/waiting failsafe stop/waiting dbus start/running, process 729 lxc-android-config start/post-start, process 561 post-start process 562 resolvconf start/running alsa-utils stop/waiting bluetooth-touch-flo stop/waiting lxc-android-boot stop/waiting mounted-var stop/waiting plymouth-shutdown stop/waiting plymouth stop/waiting system-watchdog stop/waiting udev-fallback-graphics stop/waiting ssh start/running, process 1796 checkroot.sh start/running lxc start/running network-manager start/running, process 1288 ubuntu-location-service start/running, process 1853 bluetooth-touch stop/waiting control-alt-delete stop/waiting factory-wipe stop/waiting hwclock stop/waiting mounted-proc stop/waiting alsa-store stop/waiting setvtrgb stop/waiting shutdown stop/waiting cron start/running, process 1502 lightdm start/running, process 1887 mountkernfs.sh start/running upstart-local-bridge start/running, process 560 alsa-restore stop/waiting apport-noui stop/waiting mountall stop/waiting mounted-debugfs stop/waiting ubuntu-location-provider-here-after-wizard stop/waiting hostname.sh start/running android-usb-state stop/waiting console stop/waiting mounted-run stop/waiting ofono stop/waiting bluetooth start/running, process 739 checkfs.sh start/running checkroot-bootclean.sh start/running mountnfs.sh start/running plymouth-stop start/running ufw start/running kmod stop/waiting rcS stop/waiting ssh-keygen stop/waiting ubuntu-location-provider-here-slpgwd stop/waiting wait-for-state stop/waiting bootmisc.sh start/running android-tools-adbd start/running, process 2379 bluetooth-touch-maguro stop/waiting flush-early-job-log stop/waiting lxc-instance stop/waiting rc-sysinit stop/waiting enable-cpu-hotplugging stop/waiting powerd start/running, process 758 upstart-socket-bridge start/running, process 1438 cgproxy stop/waiting force-mtp stop/waiting ssh-property-watcher stop/waiting apparmor stop/waiting mountdevsubfs.sh start/running upstart-file-bridge start/running, process 743 tty2 stop/waiting udevtrigger stop/waiting mtab.sh start/running udev-finish start/running boot-hooks/extrausers stop/waiting container-detect stop/waiting custom-apparmor-cache stop/waiting device-hacks stop/waiting force-adb stop/waiting mounted-dev stop/waiting tty3 stop/waiting cgmanager start/running, process 533 hwclock.sh start/running adbd-emergency-shell stop/waiting alsa-state stop/waiting bluetooth-touch-mako stop/waiting boot-hooks/ensure-logdir-owner stop/waiting hostname stop/waiting lxc-net stop/waiting mountall-reboot stop/waiting no-cpu-hotplug stop/waiting network-interface (sit0) start/running network-interface (ccmni1) start/running network-interface (ccmni0) start/running network-interface (ccmni2) start/running network-interface (tunl0) start/running network-interface (lo) start/running network-interface (ip6tnl0) start/running network-interface (ifb0) start/running network-interface (ifb1) start/running network-interface (wlan0) start/running boot-hooks/wipe-qml-cache stop/waiting mountall-shell stop/waiting mounted-tmp stop/waiting plymouth-ready stop/waiting plymouth-splash stop/waiting plymouth-upstart-bridge stop/waiting tty1 stop/waiting ubuntu-espoo-service stop/waiting udevmonitor stop/waiting mountall-bootclean.sh start/running network-interface-security (network-interface/ip6tnl0) start/running network-interface-security (network-interface/tunl0) start/running network-interface-security (network-manager) start/running network-interface-security (network-interface/wlan0) start/running network-interface-security (network-interface/sit0) start/running network-interface-security (network-interfac
[Touch-packages] [Bug 1491532] Re: ssh-keygen invocation difficult to copy-paste
** Changed in: openssh (Ubuntu) Importance: Undecided => Low ** Changed in: openssh (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1491532 Title: ssh-keygen invocation difficult to copy-paste Status in openssh package in Ubuntu: Triaged Bug description: When connecting to a host whose host keys have changed (e.g. when connecting to a new instance in a cloud), something like the below message is displayed. The ssh-keygen invocation is harder to copy- paste than it could be if it were on a separate line. @@@ @WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that a host key has just been changed. The fingerprint for the ECDSA key sent by the remote host is . Please contact your system administrator. Add correct host key in /home//.ssh/known_hosts to get rid of this message. Offending ECDSA key in /home//.ssh/known_hosts:408 remove with: ssh-keygen -f "/home//.ssh/known_hosts" -R ECDSA host key for has changed and you have requested strict checking. Host key verification failed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1491532/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373421] Re: [Notifications] Notifications centre item unclear
UX comment- We've added in the latest specification for Notifications in the Notification Centre the ability to launch the originating app by tapping on any part of the body of a notification list item. Link to the spec: https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.2kihdtv7as7e -- 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/1373421 Title: [Notifications] Notifications centre item unclear Status in Ubuntu UX: Fix Committed Status in unity-notifications: New Status in unity-notifications package in Ubuntu: New Bug description: When in notification centre, tapping on an item will expand it to show further information. However, if you want to go to the app that generated the notification, users need to tap on a tiny icon at the right. We suggest a different experience should be provided, making the access to the app easier. UX comment- We've added in the latest specification for Notifications in the Notification Centre the ability to launch the originating app by tapping on any part of the body of a notification list item. Link to the spec: https://docs.google.com/a/canonical.com/document/d/1xDSZ_dnAMAlhgFnnyjJEibaITXjVLp1_pnj_tATNm9I/edit#heading=h.2kihdtv7as7e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1373421/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1449295] Re: [Icons] Inconsistent tranparent app icon handling
** Changed in: ubuntu-ux Status: Triaged => 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/1449295 Title: [Icons] Inconsistent tranparent app icon handling Status in Ubuntu UX: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: I uploaded an app with an icon that had a transparent background. The Ubuntu Store scope renders it with a white background. The dash renders it transparent. The launcher renders it transparent. I think the Store is doing the right thing. But any solution is fine, as long as it is consistent. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1449295/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492214] [NEW] All preview comments are created at the same time
Public bug reported: All the preview comments are created at the same time which can produce considerable delays when the creation happens. How to reproduce: * Be on the apps scope * Long press on telegram to get to the preview * Scroll down until the place comments have to appear * Notice the 3 or 4 seconds delay while all the comments are being created One solution is to use a listview + displayMargin settings so that only the items actually in viewport + a few more for precaching are created and not the whole lot. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1492214 Title: All preview comments are created at the same time Status in unity8 package in Ubuntu: New Bug description: All the preview comments are created at the same time which can produce considerable delays when the creation happens. How to reproduce: * Be on the apps scope * Long press on telegram to get to the preview * Scroll down until the place comments have to appear * Notice the 3 or 4 seconds delay while all the comments are being created One solution is to use a listview + displayMargin settings so that only the items actually in viewport + a few more for precaching are created and not the whole lot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1492214/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1491566] Re: Shell not responsive after an incoming SMS
** Summary changed: - Greeter and edges not responsive after an incoming SMS + Shell not responsive after an incoming SMS -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1491566 Title: Shell not responsive after an incoming SMS Status in Canonical System Image: Confirmed Status in qtmir package in Ubuntu: Confirmed Status in unity-system-compositor package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: RC proposed MX4 r100 This happened twice in the last two days Receive an incoming text Screen turns on and notification is shown notification goes away try to interact with the phone and nothing works another text message is received and the notification is displayed To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1491566/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
Not totally fixed : the "intermediate" state of mouse cursor is wrong - while holding left click during dragging. ** Attachment added: "photo of screen, not screenshot" https://bugs.launchpad.net/ubuntu/+source/xorg-lts-utopic/+bug/1390625/+attachment/4457252/+files/DSC_0062.jpg -- 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/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Fix Released Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when drag&dropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a drag&drop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] 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 Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO 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 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 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1434124] Re: [dash] + [scopes] Uninstallation confirmation screen inconsistent with other dialogs
** Changed in: ubuntu-ux Assignee: Paty Davila (dizzypaty) => Grazina (boroskograzina) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1434124 Title: [dash] + [scopes] Uninstallation confirmation screen inconsistent with other dialogs Status in Ubuntu UX: In Progress Status in unity-scope-click package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: On current rtm trying to uninstall a click from the dash you get a confirmation screen with a "confirm" button on the left and an orange "cancel" one on the right, that seems inconsistant with the guideline/what other part of the system are doing - why is "cancel" in orange? https://design.ubuntu.com/apps/building-blocks/buttons states that the color is for negative actions - unsure that "confirm" is conveying what the button does, could it be "uninstall" or "confirm uninstallation"? it feels like that the left button should be the red one and have something in its label stating what you are confirming (since the rational is that users tend to not read the text description, so the button should summarize the action they are doing) -- UX Comment -- We are currently working on the redesign of scopes previews and design patterns for the use of buttons (types, colour, position, behaviour). (Page 133: https://docs.google.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#heading=h.pl3n70ucwqtp). The desired resolution and specs will be updated as soon as they are available. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1434124/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1450255] Re: SIM names should default to carrier names
** Changed in: ubuntu-ux Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to messaging-app in Ubuntu. https://bugs.launchpad.net/bugs/1450255 Title: SIM names should default to carrier names Status in telepathy-ofono: New Status in Ubuntu UX: Invalid Status in address-book-app package in Ubuntu: Invalid Status in dialer-app package in Ubuntu: Invalid Status in messaging-app package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Invalid Bug description: Right now whenever I need to pick a SIM card somewhere it says "SIM 1" and "SIM 2". That means I need to look up what the respective cards are on a regular basis to be sure which is which - there's no way I will remember this, not to mention when traveling I change cards and it's paramount for me to know what card is in there and not accidentally use the wrong one. SIM switchers should display the names of the carriers rather than mere numbers. To manage notifications about this bug go to: https://bugs.launchpad.net/telepathy-ofono/+bug/1450255/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1492218] [NEW] {Gallery app} when multi-selecting photos it uses a different style of checkbox
Public bug reported:
When multi-selecting photos in the Gallery app, it uses a big orange
tick box. Shouldn't we be using our standard checkboxes here for
consistency?
Image attached.
** Affects: gallery-app (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "Gallery app selection"
https://bugs.launchpad.net/bugs/1492218/+attachment/4457257/+files/gallery%20app%20selection.png
** Summary changed:
- {Gallery app} when multi-selecting photos it doesn't use a checkbox
+ {Gallery app} when multi-selecting photos it uses a different style of
checkbox
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gallery-app in Ubuntu.
https://bugs.launchpad.net/bugs/1492218
Title:
{Gallery app} when multi-selecting photos it uses a different style of
checkbox
Status in gallery-app package in Ubuntu:
New
Bug description:
When multi-selecting photos in the Gallery app, it uses a big orange
tick box. Shouldn't we be using our standard checkboxes here for
consistency?
Image attached.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gallery-app/+bug/1492218/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
