[Touch-packages] [Bug 1377239] Re: cups-pdf 2.6.1-9 not able to lookup domain user because apparmor profile
Okay, step by step: cups-pdf policy has: #include abstractions/nameservice yes /etc/apparmor.d/abstractions/nameservice has: #include abstractions/winbind yes /etc/apparmor.d/abstractions/winbind has: /var/{lib,run}/samba/winbindd_privileged/pipe rw, yes I am using ubuntu defaults. All apparmor files are unchanged, but it only works when I add following to cups-pdf policy: /run/samba/winbindd/pipe rw, Eventually it's because /var/run/samba/winbindd_privileged/pipe is not available, but /var/lib/samba/winbindd_privileged/pipe is. The permissions on both pipes are the same: 0 srwxrwxrwx 1 root root 0 Okt 3 15:13 /var/lib/samba/winbindd_privileged/pipe 0 srwxrwxrwx 1 root root 0 Okt 3 15:13 /run/samba/winbindd/pipe -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1377239 Title: cups-pdf 2.6.1-9 not able to lookup domain user because apparmor profile Status in “cups” package in Ubuntu: Incomplete Bug description: I use cups-pdf for years now. But now it's no longer able to lookup users from domain. lookup user by getent passwd works fine. lookup user by wbinfo works fine. Login with domain user works fine. kinit username works, too. But cups-pdf with log level 7 tells: unknown user (admin) It's regardless of wether I use UserPrefix MYDOMAIN\ or leave it blank. Just the output of the log file differs to: unknown user (MYDOMAIN\admin) After long time of searching around in all log files I tried to set apparmor profile use.sbin.cupsd to complain mode. That fixes my problem. But what I have to change in apparmor profile to switch back to enforce mode? I don't get any logging by complain, enforce or audit mode in /var/log/syslog. It looks like getpwnam or another method used in cups-pdf.c is restricted by apparmor in Ubuntu 14.04.1 LTS. I use the default cups-pdf.conf and default usr.sbin.cupsd apparmor profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1377239/+subscriptions -- Mailing list: https://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 1377973] [NEW] lxc-destroy/lxc-stop gets stuck
Looks like the lxc-start command got stuck, after killing the process everything went back to normal. root@ares:~# netstat -x | grep lxc unix 2 [ ] STREAM CONNECTING0 @/var/lib/lxc/myvm/command unix 2 [ ] STREAM CONNECTING0 @/var/lib/lxc/myvm/command unix 2 [ ] STREAM CONNECTING0 @/var/lib/lxc/myvm/command unix 2 [ ] STREAM CONNECTING0 @/var/lib/lxc/myvm/command unix 2 [ ] STREAM CONNECTING0 @/var/lib/lxc/myvm/command unix 2 [ ] STREAM CONNECTING0 @/var/lib/lxc/myvm/command root@ares:~# ps -ef | grep lxc root 1697 1250 0 Okt06 ?00:00:00 strace lxc-start -n myvm -f myvm.conf --logfile=vm.log --logpriority=NOTICE root 1704 1697 0 Okt06 ?00:00:00 lxc-start -n myvm -f myvm.conf --logfile=vm.log --logpriority=NOTICE lxc-dns+ 13856 1 0 Okt05 ?00:00:00 dnsmasq -u lxc-dnsmasq --strict-order --bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --conf-file= --listen-address 10.0.3.1 --dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override --except-interface=lo --interface=lxcbr0 --dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative root@ares:~# ps -ef | grep 1697 root 1697 1250 0 Okt06 ?00:00:00 strace lxc-start -n myvm -f myvm.conf --logfile=vm.log --logpriority=NOTICE root 1704 1697 0 Okt06 ?00:00:00 lxc-start -n myvm -f myvm.conf --logfile=vm.log --logpriority=NOTICE root 15861 21116 0 08:12 pts/16 00:00:00 grep --color=auto 1697 root@ares:~# kill -3 1697 root@ares:~# ps -ef | grep lxc-start root 15870 21116 0 08:13 pts/16 00:00:00 grep --color=auto lxc-start root@ares:~# lxc-ls --fancy NAME STATE IPV4 IPV6 AUTOSTART -- root@ares:~# lxc-destroy -n myvm Container is not defined still, I find it a bit strange that not even lxc-ls was working properly On Mon, Oct 6, 2014 at 4:57 PM, Serge Hallyn 1377...@bugs.launchpad.net wrote: thanks for reporting this bug. Could you please show: 1. The result of 'netstat -x | grep lxc' 2. ps -ef | grep lxc status: incomplete ** Changed in: lxc (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1377973 Title: lxc-destroy/lxc-stop gets stuck Status in “lxc” package in Ubuntu: Incomplete Bug description: On ubuntu 14.04 I ran lxc-start with a custom built container and interrupted the setup before it could finish. Now lxc-ls --fancy, lxc- destroy -n container or lxc-stop -n container are getting stuck. LXC package version is 1.0.5-0ubuntu0.1 Output from strace: # strace lxc-destroy -n myvm mkdir(/, 0755)= -1 EEXIST (File exists) mkdir(/run/, 0755)= -1 EEXIST (File exists) mkdir(/run/lock/, 0755) = -1 EEXIST (File exists) mkdir(/run/lock/lxc//, 0755) = -1 EEXIST (File exists) mkdir(/run/lock/lxc//var/, 0755) = -1 EEXIST (File exists) mkdir(/run/lock/lxc//var/lib/, 0755) = -1 EEXIST (File exists) mkdir(/run/lock/lxc//var/lib/lxc, 0755) = -1 EEXIST (File exists) stat(/var/lib/lxc/myvm/config, 0x7fff06d64f50) = -1 ENOENT (No such file or directory) stat(/var/lib/lxc/myvm/partial, 0x7fff06d64e80) = -1 ENOENT (No such file or directory) socket(PF_LOCAL, SOCK_STREAM, 0)= 3 connect(3, {sa_family=AF_LOCAL, sun_path=@/var/lib/lxc/myvm/command}, 28) = 0 getuid()= 0 getgid()= 0 sendmsg(3, {msg_name(0)=NULL, msg_iov(1)=[{\4\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 16}], msg_controllen=32, {cmsg_len=28, cmsg_level=SOL_SOCKET, cmsg_type=SCM_CREDENTIALS{pid=2028, uid=0, gid=0}}, msg_flags=0}, MSG_NOSIGNAL) = 16 recvmsg(3, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1377973/+subscriptions -- Pozdrav / Regards, Nikola Krzalic. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1377973 Title: lxc-destroy/lxc-stop gets stuck Status in “lxc” package in Ubuntu: Incomplete Bug description: On ubuntu 14.04 I ran lxc-start with a custom built container and interrupted the setup before it could finish. Now lxc-ls --fancy, lxc- destroy -n container or lxc-stop -n container are getting stuck. LXC package version is 1.0.5-0ubuntu0.1 Output from strace: # strace lxc-destroy -n myvm mkdir(/, 0755)= -1 EEXIST (File exists) mkdir(/run/, 0755)= -1 EEXIST (File exists) mkdir(/run/lock/, 0755) = -1 EEXIST (File exists) mkdir(/run/lock/lxc//, 0755) = -1 EEXIST (File exists)
[Touch-packages] [Bug 1103961] Re: nux::IOpenGLShaderProgram::Begin crashes on nVidia 10de:00fd
I've upgraded the OS on the affected computer to trusty and found that the problem is still present in trusty's version of nux. Same symptoms, and my patch still applies. ** Tags added: precise trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1103961 Title: nux::IOpenGLShaderProgram::Begin crashes on nVidia 10de:00fd Status in “nux” package in Ubuntu: New Bug description: After upgrading to precise and activating nvidia-173 (173.14.35) on a machine with the following graphics card: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV37GL [Quadro PCI-E Series] [10de:00fd] (rev a2) /usr/bin/compiz started to crash with the exact same symptoms as in bug #768178. (I'm filing a new bug since that one is marked as a duplicate of a quite different bug that is itself marked as invalid.) This isn't too surprising since the graphics card is a close relative of the GeForce FX series, various flavours of which are already blacklisted in nux. Forcing Unity 2D works around the problem, so I've applied the attached patch on top of nux 2.14.1-0ubuntu1. Maybe one could set _use_glsl_shaders = false in NuxGraphics/GraphicsEngine.cpp instead but I don't have the time to test this conjecture. glGetString(GL_RENDERER) returns Quadro PCI-E Series/PCI/SSE2 for this card and driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1103961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376054] Re: Scope Registry fails when aggregating an aggregator
Looking into this in more detail, there seems to be some issues with the scopes that the dashboard scope aggregates: 1. If I have no favourited contacts on my phone, when the scope gets to pushing favourite contact results it just seems to close and stop pushing any further results (no results from other aggregated scopes are returned thereafter). 2. Upcoming events seems to get stuck in the query run() method (loading bar moves back and forth for a while), then after some time the events scope crashes: RegistryObject::ScopeProcess: Scope: com.canonical.scopes.events_events closed unexpectedly. Either the process crashed or was killed forcefully. 3. Without a FitBit account (Note: adding a FitBit account via settings doesn't even work for me), the FitBit scope gets stuck in the scope's start() method, then after 4s the scopes runtime gives up and logs a timeout: 2014/10/07 06:35:50 Starting fitbit scope ScopeBase::run(): unity::scopes::TimeoutException: Request timed out after 5000 milliseconds So, the best I can do is favourite a contact, then disable both Display upcoming events and Display your FitBit stats, then the scope works just fine. In fact, the scope works this way even without the changes in the linked branch. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1376054 Title: Scope Registry fails when aggregating an aggregator Status in “unity-scopes-api” package in Ubuntu: In Progress Bug description: When trying to aggregate and aggreagator scope. many many queries are fired off at once, which seems to cause the scope registry to hang. To reproduce: 1) Install krillin rtm image 2) Install attached dashboard.click 3) Note scope registry seems to hang when adding News to the Dashboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1376054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378198] Re: powerd crashed with SIGABRT in ua_sensors_proximity_new()
*** This bug is a duplicate of bug 1351314 *** https://bugs.launchpad.net/bugs/1351314 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1351314, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1378198/+attachment/4227207/+files/CoreDump.gz ** Attachment removed: Disassembly.txt https://bugs.launchpad.net/bugs/1378198/+attachment/4227209/+files/Disassembly.txt ** Attachment removed: ProcMaps.txt https://bugs.launchpad.net/bugs/1378198/+attachment/4227210/+files/ProcMaps.txt ** Attachment removed: ProcStatus.txt https://bugs.launchpad.net/bugs/1378198/+attachment/4227211/+files/ProcStatus.txt ** Attachment removed: Registers.txt https://bugs.launchpad.net/bugs/1378198/+attachment/4227212/+files/Registers.txt ** Attachment removed: Stacktrace.txt https://bugs.launchpad.net/bugs/1378198/+attachment/4227213/+files/Stacktrace.txt ** Attachment removed: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1378198/+attachment/4227214/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of bug 1351314 powerd crashed with SIGABRT in internal::ToBackend::exit_module() ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to powerd in Ubuntu. https://bugs.launchpad.net/bugs/1378198 Title: powerd crashed with SIGABRT in ua_sensors_proximity_new() Status in “powerd” package in Ubuntu: New Bug description: Happened just after a system start ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: powerd 0.16+14.10.20140903-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 Date: Tue Oct 7 08:29:07 2014 ExecutablePath: /usr/bin/powerd InstallationDate: Installed on 2014-10-01 (5 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) ProcCmdline: /usr/bin/powerd ProcEnviron: PATH=(custom, no user) TERM=linux Signal: 6 SourcePackage: powerd StacktraceTop: ?? () ?? () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 ua_sensors_proximity_new () from /usr/lib/x86_64-linux-gnu/libubuntu_application_api.so.2 powerd_sensors_init() () main () Title: powerd crashed with SIGABRT in ua_sensors_proximity_new() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powerd/+bug/1378198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376054] Re: Scope Registry fails when aggregating an aggregator
I'm testing on RTM image 75. phablet@ubuntu-phablet:~$ click list com.account.plugin.fitbit 0.2 com.canonical.cincodias 0.2 com.canonical.elpais0.6 com.canonical.los40 0.1 com.canonical.scopes.bbc1.02 com.canonical.scopes.bbc-sport 1.0.2 com.canonical.scopes.calls 0.17 com.canonical.scopes.cnet 0.2 com.canonical.scopes.contacts 0.4 com.canonical.scopes.dashboard 0.9 com.canonical.scopes.engadget 0.5 com.canonical.scopes.etsy 1.0.23 com.canonical.scopes.euronews 0.4 com.canonical.scopes.events 0.4 com.canonical.scopes.fbphotos 1.17 com.canonical.scopes.fitbit 1.0.12 com.canonical.scopes.flickr 1.0.19 com.canonical.scopes.holidays 0.04 com.canonical.scopes.inrix 1.0.21 com.canonical.scopes.news 2.0 com.canonical.scopes.openmotion 1.12 com.canonical.scopes.photos 1.07 com.canonical.scopes.photos-local 1.17 com.canonical.scopes.poi1.0.7 com.canonical.scopes.shopping 1.2 com.canonical.scopes.songkick 1.0.7 com.canonical.scopes.tasks 0.6 com.canonical.scopes.texts 0.6 com.canonical.scopes.timeout0.4.10 com.canonical.scopes.tmdb 1.0.3 com.canonical.scopes.transport-alerts 1.05 com.canonical.scopes.twittertrending1.0.3 com.canonical.scopes.wikinear 1.0.5 com.canonical.scopes.xataka 0.5 com.canonical.unity-scope-nearby0.8.4 com.nokia.heremaps 1.0.1 com.ubuntu.developer.knitzsche.i18n 1.07 com.ubuntu.developer.mzanetti.tagger0.5.1.0 com.ubuntu.telegram 0.6.0.57 com.ubuntu.yelp 1.0.26 com.canonical.payui 0.4.0 com.ubuntu.calculator 1.3.329 com.ubuntu.camera 3.0.0.400 com.ubuntu.clock3.1.125 com.ubuntu.developer.webapps.webapp-amazon 1.0.10 com.ubuntu.developer.webapps.webapp-ebay1.0.12 com.ubuntu.developer.webapps.webapp-facebook1.0.24 com.ubuntu.developer.webapps.webapp-gmail 1.0.18 com.ubuntu.developer.webapps.webapp-twitter 1.0.18 com.ubuntu.dropping-letters 0.1.2.2.66 com.ubuntu.filemanager 0.3.288 com.ubuntu.gallery 2.9.1.1084 com.ubuntu.music1.3.638 com.ubuntu.reminders0.5.262 com.ubuntu.scopes.youtube 1.0.13 com.ubuntu.shorts 0.2.330 com.ubuntu.sudoku 1.1.292 com.ubuntu.terminal 0.5.155 com.ubuntu.weather 1.1.374 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1376054 Title: Scope Registry fails when aggregating an aggregator Status in “unity-scopes-api” package in Ubuntu: In Progress Bug description: When trying to aggregate and aggreagator scope. many many queries are fired off at once, which seems to cause the scope registry to hang. To reproduce: 1) Install krillin rtm image 2) Install attached dashboard.click 3) Note scope registry seems to hang when adding News to the Dashboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1376054/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377698] Re: /etc/default/rcS: UTC=no is being ignored
This is a regression in the util-linux package in 14.10. When built with the current debhelper, /etc/init.d/hwclock.sh is installed alongside /etc/init/hwclock.conf, and is not masked out by the system; and this init script has broken handling of the $UTC setting entirely. This is courtesy of an ill-conceived change in Debian to move the UTC setting into /etc/adjtime, which we *DO NOT NEED AT ALL* and should not have in Ubuntu. ** Package changed: sysvinit (Ubuntu) = util-linux (Ubuntu) ** Changed in: util-linux (Ubuntu) Importance: Undecided = High ** Changed in: util-linux (Ubuntu) Status: Confirmed = Triaged ** Changed in: util-linux (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1377698 Title: /etc/default/rcS: UTC=no is being ignored Status in “util-linux” package in Ubuntu: Triaged Bug description: This causes the greeter time to display utc sets system time to utc Affects users who are in a different timezone Also affects users who dual boot with windows, their time will be off by amount different from utc to their time zone ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: initscripts 2.88dsf-41ubuntu18 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 5 14:16:48 2014 InstallationDate: Installed on 2014-10-05 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140923) SourcePackage: sysvinit UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.rcS: 2014-10-05T10:58:21.042693 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1377698/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1289804] Re: Foreground app consuming lots of memory
** Changed in: music-app Status: Triaged = 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/1289804 Title: Foreground app consuming lots of memory Status in Music application for Ubuntu devices: Incomplete Status in “unity8” package in Ubuntu: New Bug description: Started music app and other apps about 20 hours ago. Phone has been sat on my desk, locked, not used for that time. Now I find it's sluggish and seems lots of RAM/SWAP has been consumed:- top - 15:49:44 up 22:55, 1 user, load average: 5.10, 2.41, 2.73 Tasks: 234 total, 1 running, 233 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.7 us, 7.1 sy, 0.0 ni, 87.9 id, 1.2 wa, 0.0 hi, 0.0 si, 0.0 st KiB Mem: 1878632 total, 1834880 used,43752 free, 384 buffers KiB Swap: 524284 total, 524284 used,0 free.22260 cached Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 65 root 20 0 0 0 0 D 37.4 0.0 4:08.99 kswapd0 24543 root 20 02548 1100712 R 10.7 0.1 0:00.06 top 969 20 0 10904284144 S 5.3 0.0 121:04.11 sensors.qc+ 981 root 20 0 10360268 40 S 5.3 0.0 102:52.46 Binder_2 6834 phablet 20 0 2047948 1.266g 6848 S 5.3 70.6 137:51.83 qmlscene 16085 root 20 0 0 0 0 S 5.3 0.0 0:26.14 kworker/0:4 24298 message+ 20 02976 1144708 S 5.3 0.1 0:00.15 dbus-daemon 1 root 20 04060 1880576 S 0.0 0.1 1:23.34 init 2 root -2 0 0 0 0 S 0.0 0.0 0:04.24 kthreadd 3 root 20 0 0 0 0 S 0.0 0.0 0:01.33 ksoftirqd/0 6 root rt 0 0 0 0 S 0.0 0.0 0:00.00 migration/0 16 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 khelper 17 root 20 0 0 0 0 S 0.0 0.0 0:00.03 kdevtmpfs 18 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 netns 19 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 suspend_sy+ 20 root 0 -20 0 0 0 S 0.0 0.0 0:00.00 suspend 22 root -51 0 0 0 0 S 0.0 0.0 0:00.00 irq/203-ms+ phablet 6834 10.1 70.7 2003920 1329976 ? Ssl Mar07 138:04 /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene music-app.qml --file= -I ./plugins To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1289804/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1273625] Re: Mediascanner2 should provide a QML interface that satisfies the needs of music-app
** Changed in: music-app Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1273625 Title: Mediascanner2 should provide a QML interface that satisfies the needs of music-app Status in Media Scanner v2: Fix Released Status in Music application for Ubuntu devices: Fix Released Status in “mediascanner2” package in Ubuntu: Fix Released Bug description: The current version of music-app uses QtGrilo to snarf the entire media index into a private database on startup. We haven't yet implemented a Grilo plugin for the new media scanner, and it would be preferable for music-app to drive itself directly from the media scanner index. To achieve this, we want to provide a QML interface that provides the necessary functionality. The initial work is in this merge proposal, but it does little more than show that it is possible to perform queries from QML: https://code.launchpad.net/~jamesh/mediascanner2/qml- plugin/+merge/201754 We most likely need to add some QAbstractListModel classes that let you iterate over songs, albums and artists. What is less clear is what filters would be needed to work with those models. This e-mail is also relevant: https://lists.launchpad.net/ubuntu-touch-coreapps/msg00666.html To manage notifications about this bug go to: https://bugs.launchpad.net/mediascanner2/+bug/1273625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1035324] Re: [desktop] Desktop Scrollbars
Lowering the importance for Music, as at least until RTM, the focus is the phone. ** Changed in: music-app Importance: Medium = Low -- 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/1035324 Title: [desktop] Desktop Scrollbars Status in Gallery App: In Progress Status in Music application for Ubuntu devices: Triaged Status in “gallery-app” package in Ubuntu: In Progress Bug description: On the desktop, we should use unity scrollbars. To manage notifications about this bug go to: https://bugs.launchpad.net/gallery-app/+bug/1035324/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized
Hmm, are you unable to change the Wifi name? -- 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/366780 Title: Please provide a mechanism whereby Wi-Fi networks can be prioritized Status in NetworkManager: In Progress Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager I've got few wifi network profiles. NM connects to 1st available network in alphabetical order. But at my home NM connects to slow and unstable free network and I want to connect to my own wifi router. I suggest to add some priorities to different networks to set the order which network to connect to. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/366780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1223050] Re: [PageStack] Calling positionViewAtIndex cause the page header misbehave
** Changed in: music-app Status: New = Triaged ** Changed in: music-app Importance: Undecided = Low -- 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/1223050 Title: [PageStack] Calling positionViewAtIndex cause the page header misbehave Status in Address Book App: Confirmed Status in Music application for Ubuntu devices: Triaged Status in Ubuntu UI Toolkit: Confirmed Status in “address-book-app” package in Ubuntu: Confirmed Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Status in “address-book-app” source package in Trusty: Confirmed Status in “ubuntu-ui-toolkit” source package in Trusty: Confirmed Bug description: Using a ListView inside of a PageStack causes the ListView header misbehave after calling positionViewAtIndex: How to reproduce (using the example attached): 1- run: qmlscene main.qml 2- click in the button click me 3- scroll the list 4- click in the button click me again Expected behavior: The section header should be fully visible at the top Current behavior: The page header overlaps the listview and the section header To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1223050/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1246172] Re: Tracks don't sort by disc number
I understand this has been fixed in the Music app by it being fixed on mediascanner. Please feel free to undo the bug status change if incorrect. ** Changed in: qtgrilo Status: Triaged = Won't Fix ** Changed in: music-app Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1246172 Title: Tracks don't sort by disc number Status in Media Scanner v2: Fix Released Status in Music application for Ubuntu devices: Fix Released Status in QtDeclarative bindings for the Grilo media scanner: Won't Fix Status in “mediascanner2” package in Ubuntu: Fix Released Bug description: I have an album with two discs and the songs play in the following order: Disc2, Track1 Disc1, Track1 Disc2, Track2 Disc1, Track2 (and so on...) I would expect that they be played: Disc1, Track1 Disc1, Track2 ... Disc1, TrackN Disc2, Track1 Disc2, Track2 ... Disc2, TrackM Some investigation into this shows that disc number is not being tracked in the music app, there are no QtGrilo bindings for it or even a field for it in the grilo library. To manage notifications about this bug go to: https://bugs.launchpad.net/mediascanner2/+bug/1246172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1288552] Re: [indicators] menus cancel current scope activity
** Changed in: unity8 (Ubuntu) Status: Confirmed = 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/1288552 Title: [indicators] menus cancel current scope activity Status in Ubuntu UX bugs: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: If I pull down an indicator menu, whatever my current scope is doing gets cancelled. For example, if I'm playing (or previewing) music in the music scope and I pull down the sound indicator to change the volume, the music stops and goes back to the default music scope state. If I'm in the Applications scope looking through click app search results, then I grab the messaging indicator to double-check what a friend told me (or use the network indicator to switch to a faster connection, or otherwise use an indicator), my current app search results disappear and the scope resets to its default state. This is annoying, especially when using a slow connection. It can take a while to get back to where I was before touching the indicators. Could we make the indicator menus not kill the state of other things the user might be doing? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1288552/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378126] Re: Passcode screen misses keypresses
I can confirm this, and I don't think this has anything to do with the keyboard. ** Changed in: unity8 (Ubuntu) Status: New = Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided = Medium ** Changed in: unity8 (Ubuntu) Assignee: (unassigned) = Michael Zanetti (mzanetti) ** Changed in: ubuntu-keyboard Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378126 Title: Passcode screen misses keypresses Status in Ubuntu Keyboard: Incomplete Status in “unity8” package in Ubuntu: Triaged Bug description: For some reason the passcode entry screen / lock screen feels very laggy when entering my passcode. It frequently misses my keypresses, so i end up typing insufficient characters. I don't know if the hit area for the numbers is too small and I'm mis-hitting or if there is a lag/delay. I'm not typing stupendously fast, but pretty quick. Any slower and it feels very deliberate, like I'm typing a PIN into an ATM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1378126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367916] Re: Phone freezes when trying to active the dialer app from the messaging menu
I can confirm the fact that it launches in emergency mode instead of showing the lockscreen, will file a separate bug as this one is fixed now. ** Changed in: unity8 (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1367916 Title: Phone freezes when trying to active the dialer app from the messaging menu Status in The Messaging Menu: Invalid Status in “indicator-messages” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Bug description: How to reproduce == 1 - Make sure that you have a missing call/voice message in your messaging indicator 2 - Launch the dialer app 3 - Lock your phone 4 - From the lock screen open the messaging menu 5 - Click to expand the message 6 - Click on the icon in the top right Expected == The dialer app appears with the phone pre-populated Current === The phone freezes and stop to accept any input. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1367916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1357321] Re: QNetworkAccessManager doesn't support roaming on Ubuntu
I have no way to test this currently, but this change may also help. The NM backend was missing some mobile connection functionality. https://codereview.qt-project.org/#/c/96501/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1253627] Re: Needs to provide emulators for Python3
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- 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/1253627 Title: Needs to provide emulators for Python3 Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: A lot of other tests (dialer, messaging, gallery, webbrowser, notes, keyboard) depend on ubuntu-ui-toolkit-autopilot for the emulators. To unblock these from being ported to Python 3, the package should ship a Python 3 module of ubuntuuitoolkit.emulators. The module itself should already work fine for Python 3, 2to3 has no output at all, and a quick visual inspection also shows no oddities (string vs. bytes and the usual traps). The package already violates the python policy anyway, so I guess as a first step it could just ship the python3 module in the same package. A cleaner approach would be to split out python3-ubuntuuitoolkit- emulators, but that might be a bit much for this one file which is relevant for testing only. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1253627/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1274434] Re: Possible environment dependency in tst_MainView::testLocalStorage()
Is this still relevant? ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1274434 Title: Possible environment dependency in tst_MainView::testLocalStorage() Status in “ubuntu-ui-toolkit” package in Ubuntu: Incomplete Bug description: For some reason, tst_MainView::testLocalStorage() fails in local sbuild/chrorot builds on amd64 but seem to succeed on the buildds (PPAs in particular). I have not yet verified whether local armhf chroot builds are also affected, since the build segfaults locally on armhf. Here is an excerpt of the local build failure (entirely reproducible): QWARN : tst_MainView::testLocalStorage() unity::action::ActionManager::ActionManager(QObject*): Could not get session bus. Actions will not be available through D-Bus. Reason: Could not connect: Connection refused QWARN : tst_MainView::testLocalStorage() unity::action::ActionManager::ActionManager(QObject*): Could not determine application identifier. HUD will not work properly. Provide your application identifier in $APP_ID environment variable. QWARN : tst_MainView::testLocalStorage() QSqlQuery::prepare: database not open QWARN : tst_MainView::testLocalStorage() file:///«BUILDDIR»/ubuntu-ui-toolkit-0.1.46+14.04.20131216/tests/unit/tst_mainview/LocalStorage.qml:27: Error: ** (process:61722): CRITICAL **: Unable to get session bus: Operation was cancelled FAIL! : tst_MainView::testLocalStorage() 'QFile::exists(databaseFolder)' returned FALSE. () Loc: [tst_mainview.cpp(140)] However, as you can see here, the build on PPA succeeds: https://launchpad.net/~barry/+archive/experimental/+build/5535025 What's missing or different in the local build environment? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1274434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1255364] Re: Not able to horizontally scroll on a single line textarea field, e.g. can't edit long browser url
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- 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/1255364 Title: Not able to horizontally scroll on a single line textarea field, e.g. can't edit long browser url Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: There's no horizontal scroll in a single line textarea field. I was trying to edit the browser URL to workaround bug 1253703 but noticed it's impossible to do, I can't move the text to edit parts that aren't visible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1255364/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378185] Re: Sometimes, header and departments combobox disappear
Could you please grab and attach scope-registry.log and unity8-dash.log when it happens? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1378185 Title: Sometimes, header and departments combobox disappear Status in “unity-scopes-shell” package in Ubuntu: New Bug description: This has happened to me twice on krillin #87 while testing silo 18 with unity-plugin-scopes 0.5.4+14.10.20141002.1-0ubuntu1 http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtmq=landing-018 See the attached screenshot. What I did in this case was to install 2ubuntu. Then got back to the home screen clicking the back button on the header. The header appears again if I swipe down the dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1378185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1200553] Re: two mouse pointers
This doesn't sound like something the UITK could affect, mouse pointers are drawn by X11 or equivalent. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Invalid -- 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/1200553 Title: two mouse pointers Status in “ubuntu-ui-toolkit” package in Ubuntu: Invalid Bug description: after this update i have two mouse pointers, one white, and one black ubuntu-ui-toolkit (0.1.46+13.10.20130712-0ubuntu1) saucy; urgency=low [ Kaleo ] * Removed unused artwork. * Added experimental dark gradient themes. * Reverted standard easings to Quad because it seems QEasingCurve::BezierSpline does not ensure the target value is always reached. (LP: #1199662) [ Loïc Molinari ] * [UbuntuShape] Prevented dangling nodes in the scene graph. (LP: #1180794) [ Ubuntu daily release ] * Automatic snapshot from revision 618 -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 12 Jul 2013 04:02:24 + tried to take a screenshot but only one pointer shows in it ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-ui-toolkit-theme 0.1.46+13.10.20130712-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-2.10-generic 3.10.0 Uname: Linux 3.10.0-2-generic x86_64 ApportVersion: 2.10.2-0ubuntu4 Architecture: amd64 Date: Fri Jul 12 10:30:20 2013 InstallationDate: Installed on 2012-06-10 (396 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Alpha amd64 (20120606.2) MarkForUpload: True SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1200553/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378186] Re: When the only app of a selected department is uninstalled, the empty department remains selected
** Changed in: unity-scopes-shell (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1378186 Title: When the only app of a selected department is uninstalled, the empty department remains selected Status in “unity-scopes-shell” package in Ubuntu: Confirmed Bug description: I found this on on krillin #87 while testing silo 18 with unity-plugin-scopes 0.5.4+14.10.20141002.1-0ubuntu1 http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtmq=landing-018 I haven't tested it without the silo. Steps to reproduce: Install an app that will add a new department to the list of installed apps. I installed 2ubuntu. Go back to the home. Select the newly added department. In my case, Books Comics. Long press on the newly installed app. Uninstall it. The dash is refreshed and the app disappears, but the empty department remains selected. See the attachment. I think that if the dash is refreshed and the selected department is empty, we should be back to All the apps. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1378186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1326037] Re: click_action_button() is not working
*** This bug is a duplicate of bug 1324556 *** https://bugs.launchpad.net/bugs/1324556 ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- 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/1326037 Title: click_action_button() is not working Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: click_action_button() uitoolkit emulator is not working. it was working fine in the previous release but the latest version broke it. I get Loading tests from: /home/om26er/code/canonical/address-book- app/staging.working/tests/autopilot Tests running... class 'Xlib.protocol.request.QueryExtension' Running from: ../../src/app/address-book-app == ERROR: address_book_app.tests.test_edit_contact.TestEditContact.test_remove_email -- Empty attachments: process-stdout (../../src/app/address-book-app) /var/log/syslog: {{{Jun 3 21:17:21 inspiron kernel: [20275.979414] input: autopilot-finger as /devices/virtual/input/input25}}} process-return-code (../../src/app/address-book-app): {{{-15}}} process-stderr (../../src/app/address-book-app): {{{ Using contact manager: memory Testability driver loaded. Wire protocol version is 1.4. unity::action::ActionManager::ActionManager(QObject*): Could not determine application identifier. HUD will not work properly. Provide your application identifier in $APP_ID environment variable. UCUriHandler: Empty APP_ID environment variable, ignoring. Fail to connect with sync monitor: QDBusError(org.freedesktop.DBus.Error.ServiceUnknown, The name com.canonical.SyncMonitor was not provided by any .service files) QObject::connect: No such signal QDBusAbstractInterface::stateChanged() QObject::connect: No such signal QDBusAbstractInterface::enabledServicesChanged() WARNING! Do not put Page/Tabs/PageStack inside another Page because that causes confusion which is the active page that sets the title and actions. ** (address-book-app:27029): WARNING **: Unable to register app: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid application ID WARNING! Do not put Page/Tabs/PageStack inside another Page because that causes confusion which is the active page that sets the title and actions. Unknown : [19] [-1] Unknown : [19] [-1] Unknown : [19] [0] Unknown : [19] [4] Unknown : [19] [5] }}} Traceback (most recent call last): File /home/om26er/code/canonical/address-book-app/staging.working/tests/autopilot/address_book_app/tests/test_edit_contact.py, line 115, in test_remove_email self.add_contact(Fulano, de Tal, None, [ful...@email.com]) File /home/om26er/code/canonical/address-book-app/staging.working/tests/autopilot/address_book_app/tests/__init__.py, line 295, in add_contact self.main_window.save() File /home/om26er/code/canonical/address-book-app/staging.working/tests/autopilot/address_book_app/emulators/main_window.py, line 131, in save self.click_action_button(save) File /usr/lib/python3/dist-packages/autopilot/logging.py, line 46, in inner return f(instance, *args, **kwargs) File /usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_mainview.py, line 196, in click_action_button header = self.open_header() File /home/om26er/code/canonical/address-book-app/staging.working/tests/autopilot/address_book_app/emulators/main_window.py, line 100, in open_header header = self.get_header() File /usr/lib/python3/dist-packages/ubuntuuitoolkit/_custom_proxy_objects/_mainview.py, line 46, in get_header raise _common.ToolkitException('The main view has no header.') ubuntuuitoolkit._custom_proxy_objects._common.ToolkitException: The main view has no header. Ran 1 test in 26.622s FAILED (failures=1) ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-ui-toolkit-autopilot 0.1.46+14.10.20140527-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-1.5-generic 3.15.0-rc5 Uname: Linux 3.15.0-1-generic x86_64 ApportVersion: 2.14.2-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 3 21:09:51 2014 InstallationDate: Installed on 2014-04-21 (43 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: ubuntu-ui-toolkit UpgradeStatus: Upgraded to utopic on 2014-05-19 (15 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1326037/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1240529] Re: Wi-Fi password field is nearly invisible
** Package changed: ubuntu-ui-toolkit (Ubuntu) = indicator-network (Ubuntu) ** Changed in: indicator-network (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1240529 Title: Wi-Fi password field is nearly invisible Status in “indicator-network” package in Ubuntu: Fix Released Bug description: Unknown build, flashed 2013-10-16 1. Choose a closed wi-fi network that you have not connected to since flashing the phone. What happens: A 'Connect to network name' dialog appears, with a near-invisible password field. What happens: A 'Connect to network name' dialog appears, with an easy-to-see password field. This is similar to a mistake Facebook made in January, with a dark blue search field on a dark blue background. http://www.fastcodesign.com/1673209/how-facebook-fixed-the-biggest- design-flaw-in-graph-search#1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1240529/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1290201] Re: haptic feedback / vibration audible during calls
If this is still a concern I gather a fix has to come from dialer/ usensord at this point. The vibrations are so subtle that, if they can still be heard, they'll have to be globally disabled during calls, but the UITK can't provide that. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- 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/1290201 Title: haptic feedback / vibration audible during calls Status in Dialer app for Ubuntu Touch: Triaged Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: If I press any of the call control buttons during a call, the phone vibrates. This vibration is audible to the person on the other end of the call. This means people can hear when I toggle mute/pause/speaker, which can be considered rude or at least distracting. The dialer app seems to ignore audio for a while after each button press, but the mic starts working again before the vibration stops. Could we make the vibration shorter? This was on a nexus 4 (mako), image 228 (observed on older images too). To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1290201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1287701] Re: anchorToKeyboard doesn't work properly when device is held in landscape
How do you reproduce this? Without an example I'm not sure how to evaluate the problem. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1287701 Title: anchorToKeyboard doesn't work properly when device is held in landscape Status in “ubuntu-ui-toolkit” package in Ubuntu: Incomplete Bug description: I recently discovered that specifying 'anchorToKeyboard: true' will resize things like lists when the keyboard appears such that there is a small space between the keyboard and the bottom of the list. This is great! However, if I turn the phone sideways (landscape), the resizing doesn't appear to happen. This can be seen by using 'utudu' from the store, add a few items to the list and then turn sideways. Maybe it is actually resizing, but there isn't enough room to show the resized elements (I can't verify that cause I can't see under the keyboard). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1287701/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 366780] Re: Please provide a mechanism whereby Wi-Fi networks can be prioritized
@Marius I have exactly the same problem with the University network and the global EDUROAM network. And no, I can't change the name of any of them; I just want NM to connect to my local University network whenever available, even if last time I manually connected to the global EDUROAM --- because I was in another university campus. Let me explain exactly the problem: - I have a wifi account on my university network, let call it UNIWIFI. When I am connected to this network I can print (and more, but use that as an example). - I have an account on EDUROAM, which is broadcast on hundreds of universities, included mine. When I am connected with EDUROAM, I cannot print. Now I move between my campus and other campuses. So the last connection could well be EDUROAM, because I was, say, attending a meeting. Or because I entered the elevator in my campus and the UNIWIFI was lost and by chance exiting the elevator NM was trying to connect to EDUROAM, and succeeded. Summary: I would like to have a way to say that if UNIWIFI is available, NM should switch to it even if the EDUROAM is available and was automatically connected (with automatically I mean after a connection loss or reboot or wake-up). I really think that just one bit of priority is all that is needed. Now I have to check and sometime change manually my connection every time I have to do a privileged (like printing) operation... BTW, this is not a criticism of NM in general. NM is a really outstanding tool and works perfectly, out of the box, with no help from the user 98% of the time --- which is almost magical. Simply there are cases where the heuristic of connection does not work; it would be really nice if the UNIWIFI AP could send a this network supersedes EDUROAM info in the broadcast, but... -- 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/366780 Title: Please provide a mechanism whereby Wi-Fi networks can be prioritized Status in NetworkManager: In Progress Status in “network-manager” package in Ubuntu: Confirmed Bug description: Binary package hint: network-manager I've got few wifi network profiles. NM connects to 1st available network in alphabetical order. But at my home NM connects to slow and unstable free network and I want to connect to my own wifi router. I suggest to add some priorities to different networks to set the order which network to connect to. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/366780/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378218] [NEW] Calling back from notification center opens an emergency-mode dialer
Public bug reported: This is extracted out of bug #1367916: Steps to reproduce: 1) make sure you have a passcode lock setup on phone 2) make sure you have indicator allows to show on lock screen (default) 3) lock the phone 4) call the phone and hang up before answering it, then wait till phone turns off after 1 minute 5) turn on screen but don't unlock 6) pull down the messaging menu, and click on the Missed Call to expand it, then tap in right corner to launch the app Expected Results: The passcode unlock screen should be shown Actual Results: The dialer gets launched in step 6 and is visible but it's in Emergency calling mode (because the phone is locked) so the call can't be made. The correct thing to do in both cases is to display the passcode unlock screen. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20141006-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu3 Architecture: armhf Date: Tue Oct 7 09:39:25 2014 InstallationDate: Installed on 2014-10-07 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141007-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Critical Assignee: Michael Terry (mterry) Status: Triaged ** Tags: apport-bug armhf utopic -- 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/1378218 Title: Calling back from notification center opens an emergency-mode dialer Status in “unity8” package in Ubuntu: Triaged Bug description: This is extracted out of bug #1367916: Steps to reproduce: 1) make sure you have a passcode lock setup on phone 2) make sure you have indicator allows to show on lock screen (default) 3) lock the phone 4) call the phone and hang up before answering it, then wait till phone turns off after 1 minute 5) turn on screen but don't unlock 6) pull down the messaging menu, and click on the Missed Call to expand it, then tap in right corner to launch the app Expected Results: The passcode unlock screen should be shown Actual Results: The dialer gets launched in step 6 and is visible but it's in Emergency calling mode (because the phone is locked) so the call can't be made. The correct thing to do in both cases is to display the passcode unlock screen. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20141006-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu3 Architecture: armhf Date: Tue Oct 7 09:39:25 2014 InstallationDate: Installed on 2014-10-07 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141007-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1378218/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1356866] Re: [UbuntuShape] strokeColor border scales badly
** Summary changed: - Button with strokeColor's border looks wrong + [UbuntuShape] strokeColor border scales badly ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1356866 Title: [UbuntuShape] strokeColor border scales badly Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: Given the attached test file you can see how badly the border is scaled for different sizes of the stroked button. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1181+14.10.20140806-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-7.12-generic 3.16.0 Uname: Linux 3.16.0-7-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Thu Aug 14 14:59:48 2014 SourcePackage: ubuntu-ui-toolkit SystemImageInfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1356866/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367916] Re: Phone freezes when trying to active the dialer app from the messaging menu
Filed as bug #1378218 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1367916 Title: Phone freezes when trying to active the dialer app from the messaging menu Status in The Messaging Menu: Invalid Status in “indicator-messages” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Bug description: How to reproduce == 1 - Make sure that you have a missing call/voice message in your messaging indicator 2 - Launch the dialer app 3 - Lock your phone 4 - From the lock screen open the messaging menu 5 - Click to expand the message 6 - Click on the icon in the top right Expected == The dialer app appears with the phone pre-populated Current === The phone freezes and stop to accept any input. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-messages/+bug/1367916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377010] Re: lenovo g555 battery design capacity 4400 mAh, last full capacity 2390 mAh = 54%
*** This bug is a duplicate of bug 1377011 *** https://bugs.launchpad.net/bugs/1377011 i was not sure if its related to acpi or upower, thats why it seems as duplicate of bug #1377011 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1377010 Title: lenovo g555 battery design capacity 4400 mAh, last full capacity 2390 mAh = 54% Status in “upower” package in Ubuntu: New Bug description: $ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge 00:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (int gfx) 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 0) 00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 1) 00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (PCIE port 2) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c) 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 08:00.0 Network controller: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter (rev 01) 09:00.0 Ethernet controller: Qualcomm Atheros AR8132 Fast Ethernet (rev c0) $ lsb_release -rd Description: Ubuntu 12.04.5 LTS Release: 12.04 $ apt-cache policy upower upower: Installiert: 0.9.15-3git1ubuntu0.1 Kandidat:0.9.15-3git1ubuntu0.1 Versionstabelle: *** 0.9.15-3git1ubuntu0.1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.9.15-3git1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1d/ACPI0003:00/power_supply/AC power supply: yes updated: Fr 03 Okt 2014 07:08:53 CEST (18 seconds ago) has history: no has statistics: no line-power online: yes Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1d/PNP0C0A:00/power_supply/BAT0 vendor: LENOVO model:BCL3100LiON power supply: yes updated: Fr 03 Okt 2014 07:08:59 CEST (12 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: charging energy: 24,9417 Wh energy-empty:0 Wh #! here is the problem energy-full: 26,529 Wh energy-full-design: 48,84 Wh energy-rate: 16,5168 W voltage: 12,393 V time to full:5,8 minutes percentage: 94,0167% #! here is the problem capacity:54,3182% technology: lithium-ion History (charge): 141231291294,017 discharging 141231287295,021 charging History (rate): 141231293316,517 charging 141231291216,040 discharging 141231288116,495 discharging Daemon: daemon-version: 0.9.15 can-suspend:
[Touch-packages] [Bug 1371846] Re: no way to disable PageHeadState actions highlighting
Can you provide an example that shows this? ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1371846 Title: no way to disable PageHeadState actions highlighting 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/+source/ubuntu-ui-toolkit/+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 1377100] Re: [Launcher] Change favourite application indication
** Branch linked: lp:~cimi/unity8/redesign-pinned-apps -- 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/1377100 Title: [Launcher] Change favourite application indication Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: In Progress Bug description: Current corner cut to indicate user's favourite applications is not understood by the user and we've gotten feedback that is not either visually very much liked. -- Desired design: White dot at the top left corner of an icon. Can be done in code with white rect and radius and no asset needed. Parameters: color: white width = height = 1 gu anchors top left corner with -2dp top margin See the attached visual for reference. Don't pay attention to other details in the attached image but just to the pin indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1377100/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308007] Re: QML DatePicker allows selecting dates in the past when 'minimum' is today
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed ** Summary changed: - QML DatePicker allows selecting dates in the past when 'minimum' is today + DatePicker allows selecting days before minimum -- 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/1308007 Title: DatePicker allows selecting days before minimum Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: API says: The default values are the current date for the minimum But even if I use minimum: new Date() it's still possible to select a date in the past. Just years selector look affected it maximum is not set. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 0.1.46+14.04.20140408.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: KDE Date: Tue Apr 15 14:17:22 2014 SourcePackage: ubuntu-ui-toolkit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1308007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1221510] Re: When changing ~/.config/ubuntu-ui-toolkit/theme.ini to SuruDark, ProgressBars no longer show up
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- 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/1221510 Title: When changing ~/.config/ubuntu-ui-toolkit/theme.ini to SuruDark, ProgressBars no longer show up Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: When setting a different default theme (that's not Ambiance), some elements don't show up, specifically Buttons and ProgressBars. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: ubuntu-ui-toolkit-theme 0.1.46+13.10.20130903.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7 Uname: Linux 3.11.0-4-generic x86_64 ApportVersion: 2.12.1-0ubuntu3 Architecture: amd64 Date: Thu Sep 5 23:06:23 2013 InstallationDate: Installed on 2013-07-26 (41 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: ubuntu-ui-toolkit UpgradeStatus: Upgraded to saucy on 2013-08-15 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1221510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377010] Re: lenovo g555 battery design capacity 4400 mAh, last full capacity 2390 mAh = 54%
*** This bug is a duplicate of bug 1377011 *** https://bugs.launchpad.net/bugs/1377011 not sure if its related to ubuntu 12.04.1 64bit version but some i got some changes after installing ubuntu 12.04.1 32bit and recalibrating the battery by running the laptop after ubuntu auto shutdown due to critical battery power level in bios till it shuts down, then recharging $ lsb_release -rd Description:Ubuntu 12.04.5 LTS Release:12.04 $ apt-cache policy upower upower: Installiert: 0.9.15-3git1ubuntu0.1 Kandidat:0.9.15-3git1ubuntu0.1 Versionstabelle: *** 0.9.15-3git1ubuntu0.1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages 100 /var/lib/dpkg/status 0.9.15-3git1 0 500 http://de.archive.ubuntu.com/ubuntu/ precise/main i386 Packages $ upower -d Device: /org/freedesktop/UPower/devices/line_power_AC native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1d/ACPI0003:00/power_supply/AC power supply: yes updated: Di 07 Okt 2014 09:39:13 CEST (1921 seconds ago) has history: no has statistics: no line-power online: no Device: /org/freedesktop/UPower/devices/battery_BAT0 native-path: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:1d/PNP0C0A:00/power_supply/BAT0 vendor: LENOVO model:BCL3100LiON power supply: yes updated: Di 07 Okt 2014 10:10:48 CEST (26 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: discharging energy: 19,7136 Wh energy-empty:0 Wh # changes energy-full: 41,07 Wh energy-full-design: 48,84 Wh energy-rate: 19,5915 W voltage: 10,832 V time to empty: 1,0 hours percentage: 48% # changes capacity:84,0909% technology: lithium-ion History (charge): 1412669418 48,000 discharging History (rate): 1412669448 19,591 discharging 1412669418 18,537 discharging 1412669388 18,937 discharging Daemon: daemon-version: 0.9.15 can-suspend: yes can-hibernateno on-battery: yes on-low-battery: no lid-is-closed: no lid-is-present: yes is-docked: no -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1377010 Title: lenovo g555 battery design capacity 4400 mAh, last full capacity 2390 mAh = 54% Status in “upower” package in Ubuntu: New Bug description: $ lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] RS880 Host Bridge 00:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (int gfx) 00:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 0) 00:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780/RS880 PCI to PCI bridge (PCIE port 1) 00:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] RS780 PCI to PCI bridge (PCIE port 2) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:12.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB OHCI0 Controller 00:13.1 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0 USB OHCI1 Controller 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 USB EHCI Controller 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 SMBus Controller (rev 3c) 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 LPC host controller 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 PCI to PCI Bridge 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 01:05.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RS880M [Mobility Radeon HD 4225/4250] 08:00.0 Network controller: Broadcom Corporation BCM4313
[Touch-packages] [Bug 1377338] Re: apparmor may fail to load some profiles if one is corrupted
The cause of the corruption is believed to be an interaction between the click-system-hooks and the apparmor upstart jobs. click-apparmor will be adjusted to use a blocking lockfile to avoid the corruption. As such, the apparmor task priority can be reduced. After discussing with the apparmor team, fixing the parser bug can (and should be done) but it more involved that the cache bug and we can't fix it in time for rtm. If the lockfile doesn't fully address this issue, we can go back to using '-n1' with xargs unconditionally in /lib/apparmor/functions. ** Also affects: click-apparmor (Ubuntu) Importance: Undecided Status: New ** Changed in: click-apparmor (Ubuntu) Status: New = In Progress ** Changed in: click-apparmor (Ubuntu) Importance: Undecided = Critical ** Changed in: click-apparmor (Ubuntu) Assignee: (unassigned) = Jamie Strandboge (jdstrand) ** Also affects: click-apparmor (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: click-apparmor (Ubuntu RTM) Status: New = In Progress ** Changed in: click-apparmor (Ubuntu RTM) Importance: Undecided = Critical ** Changed in: click-apparmor (Ubuntu RTM) Assignee: (unassigned) = Jamie Strandboge (jdstrand) ** Changed in: apparmor (Ubuntu RTM) Importance: Critical = Medium ** Changed in: apparmor (Ubuntu) Importance: Critical = Medium ** Changed in: apparmor (Ubuntu RTM) Status: In Progress = Triaged ** Changed in: apparmor (Ubuntu) Status: In Progress = Triaged ** No longer affects: apparmor (Ubuntu RTM) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1377338 Title: apparmor may fail to load some profiles if one is corrupted Status in “apparmor” package in Ubuntu: Triaged Status in “click-apparmor” package in Ubuntu: In Progress Status in “click-apparmor” package in Ubuntu RTM: In Progress Bug description: Steps to reproduce (on the emulator): 1. sudo sh -c 'echo foo /var/lib/apparmor/profiles/click_com.ubuntu.music_music_1.3.638' 2. sudo start apparmor ACTION=teardown 3. sudo start apparmor start: Job failed to start 4. sudo aa-status|egrep '^ '|grep -v '('| sort -u /tmp/aa-status.music_bad 5. sudo rm -f /var/lib/apparmor/profiles/click_com.ubuntu.music_music_1.3.638 6. sudo aa-clickhook # regenerates the missing profile to had a good one 7. sudo start apparmor ACTION=teardown 8. sudo start apparmor 9. sudo aa-status|egrep '^ '|grep -v '('| sort -u /tmp/aa-status.music_good 10. diff -Naur /tmp/aa-status.music_bad /tmp/aa-status.music_good --- /tmp/aa-status.music_bad 2014-10-03 22:47:52.890906744 + +++ /tmp/aa-status.music_good 2014-10-03 22:49:54.372739381 + @@ -13,6 +13,10 @@ com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter_1.0.18//oxide_helper com.ubuntu.developer.webapps.webapp-twitter_webapp-twitter-helper_1.0.18 com.ubuntu.dropping-letters_dropping-letters_0.1.2.2.66 + com.ubuntu.music_music_1.3.638 + com.ubuntu.shorts_shorts_0.2.330 + com.ubuntu.sudoku_sudoku_1.1.292 + com.ubuntu.weather_weather_1.1.374 lxc-container-default lxc-container-default-with-mounting lxc-container-default-with-nesting Expected results: only com.ubuntu.music_music_1.3.638 should be missing. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1377338/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374750] Re: Cannot create chroot in 14.04
What version of click are you using? I believe I fixed this in 0.4.23, although that was after trusty. You might want to use the backport in the ubuntu-sdk-team PPA. ** Changed in: click (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1374750 Title: Cannot create chroot in 14.04 Status in “click” package in Ubuntu: Incomplete Bug description: In Trusty, on an amd64 system, running sudo click chroot -a amd64 -f ubuntu-sdk-14.04 create terminates with: Reading state information... Done Note, selecting 'libc6-dev' instead of 'libc-dev' E: Unable to locate package g++-x86_64-linux-gnu E: Couldn't find any package by regex 'g++-x86_64-linux-gnu' E: Unable to locate package pkg-config-x86_64-linux-gnu Command returned 100: schroot -u root -c source:click-ubuntu-sdk-14.04-amd64 -- /finish.sh I'm adding the full logs as an attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1374750/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1367821] Re: [Dash] Apps that are downloaded/installed should show on launcher and dash with a being-filled animation
** Tags added: ota-future -- 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/1367821 Title: [Dash] Apps that are downloaded/installed should show on launcher and dash with a being-filled animation Status in Ubuntu UX bugs: Triaged Status in “ubuntu-download-manager” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: Triaged Bug description: When a user taps to install an app, the app icon should be instantly placed into all locations it will appear when the download is complete, and the icon should display the 'downloading animation' (filling with colour) until the download is complete. Relevant spec: https://sites.google.com/a/canonical.com/unity8dash/scopes/store/3-previews To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1367821/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348557] Re: Make scrolling speed resolution independent
** Tags removed: rtm14 ** Tags added: ota-future rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1348557 Title: Make scrolling speed resolution independent Status in QT Ubuntu: Invalid Status in Ubuntu UI Toolkit: Confirmed Status in “qtbase-opensource-src” package in Ubuntu: New Status in “qtdeclarative-opensource-src” package in Ubuntu: New Bug description: Following https://bugreports.qt-project.org/browse/QTBUG-35608 the default speed of scrollable components (components inheriting from flickable basically) is not resolution independent. The result is that scrolling speed on our high dpi touch screens is slow. We could workaround this in the SDK until the bug is fixed upstream (I bet it won't happen in time for our releases), by simply adding components named as Flickable, Listview, Gridview etc etc in the Ubuntu.Components, where each of them sets the speed to be resolution independent following our GU guidelines To manage notifications about this bug go to: https://bugs.launchpad.net/qtubuntu/+bug/1348557/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371835] Re: highlighting selected item displays incorrectly with OptionSelector and ItemSelector
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1371835 Title: highlighting selected item displays incorrectly with OptionSelector and ItemSelector Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. open the Ubuntu SDK 2. Tools/Ubuntu/Showcase Gallery 3. click Styles on the left 4. select the SuruDark theme Notice after selecting the dark theme that there is a light gray rectangle for the selected item. This light gray box expands outside the rounded corners of the OptionSelector and looks wrong. If you look very carefully at the Ambiance theme, the same thing happens there with the selected item-- it is just that the highlight color is much closer to the background color. I have an application that is affected by this and it makes it look horrible. I think two things should be fixed to address this bug: 1. the highlight color should fill within the rounded corners but not outside) 2. you should be able to disable highlighting or make the color configurable, since not all users of OptionSelector will want to have the default highlight color (I do not in my application). Adding rtm14 tag and marking as Critical because many applications use OptionSelector and this bug makes these applications look bad. I just noticed the same thing happens with ItemSelector. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1371835/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240134] Re: Several system app dash icons are too low res in Applications scope
*** This bug is a duplicate of bug 1271158 *** https://bugs.launchpad.net/bugs/1271158 ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Invalid -- 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/1240134 Title: Several system app dash icons are too low res in Applications scope Status in Ubuntu UI Toolkit: New Status in Ubuntu UX bugs: Fix Committed Status in The Unity 8 shell: Incomplete Status in “ubuntu-ui-toolkit” package in Ubuntu: Invalid Bug description: current situation: Several system app icons are too low res (blurry/pixelated) in Applications scope. The same icons appear fine in Home scope however affected icons: -gallery -messaging -facebook -twitter -contacts -dialer -browser -gmail -ubuntu one -amazon Solution: Mathieu has uploaded high res system app icons to ubuntu-themes - please use those instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1240134/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361825] Re: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
Looks more like python3-gi being hosed for some reason ... ** Package changed: click (Ubuntu) = pygobject (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1361825 Title: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in “pygobject” package in Ubuntu: New Bug description: Got this when I started an xubuntu session on utopic. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: click-apparmor 0.2.9 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 Date: Mon Aug 25 11:20:50 2014 DuplicateSignature: package:click-apparmor:0.2.9:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-05-31 (452 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: click-apparmor SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-02-18 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1361825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1286269] Re: Over-long header text disappears off the screen edge
The header ends in an ellipsis these days. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Fix Released -- 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/1286269 Title: Over-long header text disappears off the screen edge Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: Ubuntu Trusty r188 1. In System Settings, navigate to About this phone Software licenses. 2. Select a component with a long name, for example account-plugin-facebook or accountsservice-ubuntu-touch-schemas. What happens: a. There is no way to read all of the header text. b. The header text just disappears off the screen edge. If the screen edge happens to be at a character boundary, then apart from any incomplete word, there's no hint that more text even exists. What should happen: a. All the header text is readable. b. If the header text is not fully on screen all the time, there should be an obvious hint of this. There are several ways this might be solved. For example: a1. The header might wrap to multiple lines. a2. The header font size might be reduced just enough for all the text to be shown, at least down to a reasonable minimum. a3. The text might be scrollable by swiping it left and right. b1. The text might end in an ellipsis. b2. The last visible character or two might fade out into transparency. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1286269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1371032] Re: Cannot send MMS from Yoigo
The requested logs me trying to send mms to my Z10 phone, was never received (i've never received any mms there so tbh may be a Z10 fault) ** Attachment added: network-test-session_10-07-2014_09:00:09.tar.gz https://bugs.launchpad.net/ubuntu/+source/nuntium/+bug/1371032/+attachment/4227326/+files/network-test-session_10-07-2014_09%3A00%3A09.tar.gz -- 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/1371032 Title: Cannot send MMS from Yoigo Status in “messaging-app” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Incomplete Status in “nuntium” package in Ubuntu: Fix Released Status in “ofono” package in Ubuntu: Invalid Status in “nuntium” package in Ubuntu RTM: Fix Released Bug description: phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts [ /ril_1 ] [ /ril_0 ] [ /ril_0/context1 ] AccessPointName = internet Name = Yoigo Internet Password = Protocol = ip IPv6.Settings = { } Type = internet Active = 1 Username = Settings = { DomainNameServers=217.168.13.34,46.6.113.2, Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31 Interface=ccmni0 } [ /ril_0/context2 ] AccessPointName = mms MessageCenter = http://mmss/ Name = Yoigo MMS Password = Protocol = ip MessageProxy = 193.209.134.141:80 IPv6.Settings = { } Type = mms Active = 0 Username = Settings = { } phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2 Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not attached phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 1 Additional info: - I didn't see any error in the messaging app. - Couldn't send nor receive MMS. - 3G connection is activated, but usually after a reboot. After a while, it looses it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1371032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1366049] Re: Distinguish between click build failing and click build succeeding, but validation failing
** Changed in: click (Ubuntu) Status: New = Triaged ** Changed in: click (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1366049 Title: Distinguish between click build failing and click build succeeding, but validation failing Status in Qt Creator plugins for Ubuntu: New Status in “click” package in Ubuntu: Triaged Bug description: click build is soon going to run click-review as part of the build to notify developers who are using click build manually of possible validation issues. Currently qtcreator-plugin-ubuntu relies on the return code of click build being 0. If we want to distinguish between - build of click file failed - click file successfully built, validation failed - click build + validation successful we need to define a return codes for these cases. To manage notifications about this bug go to: https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1366049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377147] Re: OnlineAccountClient hangs on construction
** Changed in: unity-scopes-api (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1377147 Title: OnlineAccountClient hangs on construction Status in “unity-scopes-api” package in Ubuntu: In Progress Bug description: If an application has instantiated a main loop (E.g. In a Qt app via new QCoreApplication()) but does not actually run that main loop, instantiating an OnlineAccountClient hangs. This was picked up when OnlineAccountClient was used from a scope that instantiated a QCoreApplication in order to execute QEventLoops elsewhere in the code, but did not actually use the application event loop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-api/+bug/1377147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372559] Re: [system-settings] Settings application section headlines
*** This bug is a duplicate of bug 1242666 *** https://bugs.launchpad.net/bugs/1242666 ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1372559 Title: [system-settings] Settings application section headlines Status in Ubuntu UX bugs: New Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: In Settings application. For example go to SecurityPrivacy view. Headlines for Security and Privacy are confusing. - they appear to be clickable, but without any response. - they are lacking any visual differentiation from actual settings items. Possible solution: - increase spacing from the top, to break it from previous section - use different font, or at least bolt font, to highlight it as section headline - when clicked, do not highlight the line/row to give impression it's clickable Same problem is all over the Settings application To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1372559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363015] Re: App icons require shaping at every callsite
Do we have some code examples? Where do app icons come from? I don't know how consistent the path is… doing magic on arbitrary path names may or may not make it even more confusing when the outcome changes depending on the image. ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1363015 Title: App icons require shaping at every callsite Status in “notify-osd” package in Ubuntu: New Status in “ubuntu-ui-toolkit” package in Ubuntu: Incomplete Bug description: In list items, showing an app icon in the correct Ubuntu shape requires shaping it when you are using it: ListItem.Standard{IconFrame: True}. http://developer.ubuntu.com/api/devel/ubuntu-13.04/qml/ui-toolkit/qml-ubuntu-components-listitems0-standard.html That property is set to True by default, but it's not obvious why it should be, and list items aren't the only place that app icons get used. The result is that several times now, app updates have ended up without the appropriate frame: - in the System Settings Updates list (bug 1354478) - in the Notifications screen - in the Launcher the frame is unintentionally different (bug 1332119). Conversely, non-app icons have ended up *with* the frame by mistake: - Display language (bug 1288866) - Orientation Lock (bug 1365450) - Ubuntu updates (bug 1367136). In notification bubbles, the opposite applies -- you have to set a hint to use an *unshaped* icon: notify_notification_set_hint_string(m_notification, x-canonical-non-shaped-icon, true). https://wiki.ubuntu.com/Touch/Notifications#Elements_of_a_Notification Predictably, this has resulted in cases of icons having frames when they shouldn't: - Wi-Fi network authentication (bug 1346904) - alarms (bug 1346925) - Remove Account (bug 1350282). On the API design quality scale, both of these are roughly Read the implementation and you'll get it right. http://sweng.the- davies.net/Home/rustys-api-design-manifesto Worse, they have opposite defaults. I suggest that the toolkit move all the way up to It's impossible to get wrong, by always shaping an icon when it is an app icon, and never otherwise. Whether an icon is an app icon could (I assume) be detected by its path. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/1363015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376763] Re: Dialog doesn't take the contents size into consideration
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = 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/1376763 Title: Dialog doesn't take the contents size into consideration Status in Ubuntu UI Toolkit: In Progress Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: In Progress Bug description: A dialog doesn't scroll if the text (as in the code example) or its contents exceeds the viewport size. This can be reproduced in e.g. ubuntu-system-settings: (Make sure you're running the very latest from proposed or a USS from October 2014 – debs[1]). 1. Open Ubuntu System Settings 2. Go to the Wi-Fi panel 3. Click Connect to hidden network… 4. Choose any security scheme other that None 4. Resize the viewport/use landscape on a device What I expect to happen: I can scroll inside the Dialog to access all fields and buttons What happened instead: The content not visible becomes inaccessible Example code: http://paste.ubuntu.com/8479468/ [1] https://launchpad.net/ubuntu-system-settings/+packages UX Solution: Make sure content can scroll vertically if exceeding the maximum height of the dialog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1376763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377812] Re: Pull down indicator menu not working properly
** Package changed: ubuntu-ui-toolkit (Ubuntu) = indicator-network (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1377812 Title: Pull down indicator menu not working properly Status in “indicator-network” package in Ubuntu: New Bug description: Mako rtm r72 I am not sure where to post this bug, so I post it here. Feel free to move it elsewhere if this is not the correct place to post it. In the last two images for mako (171 172) it is not working properly. Either I can't pull the menu down more than 10-15 mm or it flickers while being pulled down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1377812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361074] Re: Dual-SIM support for PIN unlock dialog
** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1361074 Title: Dual-SIM support for PIN unlock dialog Status in “indicator-network” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: In Progress Status in “indicator-network” package in Ubuntu RTM: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: On dual-SIM devices with both SIM cards protected by a PIN code, the PIN code prompt doesn't say which SIM card the PIN code is for. It should indicate the slot. cf screenshot attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140822-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.6-0ubuntu2 Architecture: armhf Date: Mon Aug 25 09:29:26 2014 InstallationDate: Installed on 2014-08-25 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140825-020205) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1361074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368702] Re: [SDK] HEADER ISSUE: Back arrow needs to be moved further to the right and also have a larger invisible touch target
What's the consensus then? ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1368702 Title: [SDK] HEADER ISSUE: Back arrow needs to be moved further to the right and also have a larger invisible touch target Status in Ubuntu UX bugs: Fix Committed Status in “ubuntu-ui-toolkit” package in Ubuntu: Incomplete Bug description: - SDK HEADER ISSUE: Back arrow needs to be moved further to the right and also have a larger invisible touch target To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368702/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359226] Re: Black screen with text on top left when wrong SIM PIN
** Changed in: unity8 (Ubuntu) Status: New = 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/1359226 Title: Black screen with text on top left when wrong SIM PIN Status in “unity8” package in Ubuntu: In Progress Bug description: See https://chinstrap.canonical.com/~aacid/sim.mp4 Once every 5 or 6 times i write the wrong SIM PIN i end up with a black screen with white text on the top left Feels pretty weird. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1359226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377352] Re: Touchpad hotkey does not work on ASUS P81IJ
Fixed in upstream git. ** Changed in: systemd (Ubuntu) Status: New = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1377352 Title: Touchpad hotkey does not work on ASUS P81IJ Status in “systemd” package in Ubuntu: Fix Committed Bug description: $ sudo evtest [...] Select the device event number [0-10]: 6 Input driver version is 1.0.1 Input device ID: bus 0x19 vendor 0x0 product 0x0 version 0x0 Input device name: Asus Laptop extra buttons [...] Testing ... (interrupt to exit) Event: time 1412379709.628840, type 4 (EV_MSC), code 4 (MSC_SCAN), value 6b Event: time 1412379709.628840, type 1 (EV_KEY), code 530 (KEY_TOUCHPAD_TOGGLE), value 1 Event: time 1412379709.628840, -- SYN_REPORT Event: time 1412379709.628856, type 1 (EV_KEY), code 530 (KEY_TOUCHPAD_TOGGLE), value 0 Event: time 1412379709.628856, -- SYN_REPORT Event: time 1412379717.081469, type 4 (EV_MSC), code 4 (MSC_SCAN), value 6b Event: time 1412379717.081469, type 1 (EV_KEY), code 530 (KEY_TOUCHPAD_TOGGLE), value 1 Event: time 1412379717.081469, -- SYN_REPORT Event: time 1412379717.081488, type 1 (EV_KEY), code 530 (KEY_TOUCHPAD_TOGGLE), value 0 Event: time 1412379717.081488, -- SYN_REPORT ^C Above is the result I got after two (Fn + F9) strokes on my ASUS P81IJ laptop. The hotkey does not toggle the touchpad as intended. Additional informations: $ lsb_release -rd Description: Ubuntu 14.04.1 LTS Release: 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.7 ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6 Uname: Linux 3.13.0-36-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CurrentDesktop: Unity CurrentDmesg: [ 310.062530] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 1511.112582] init: acpid main process ended, respawning [ 1513.124409] init: acpid main process (2696) killed by KILL signal [ 1513.124438] init: acpid main process ended, respawning [ 1932.872956] perf samples too long (2510 2500), lowering kernel.perf_event_max_sample_rate to 5 Date: Sat Oct 4 06:42:59 2014 InstallationDate: Installed on 2011-10-18 (1081 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012) MachineType: ASUSTeK Computer Inc. P81IJ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-36-generic root=UUID=00ab2e2c-ccf1-4f9d-a430-a4623ac322f4 ro quiet splash acpi_osi=Linux acpi_backlight=vendor vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to trusty on 2014-04-20 (166 days ago) dmi.bios.date: 02/14/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: P81IJ dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd02/14/2011:svnASUSTeKComputerInc.:pnP81IJ:pvr1.0:rvnASUSTeKComputerInc.:rnP81IJ:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: P81IJ dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1377352/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370571] Re: Read-only text field doesn't look read-only
** Changed in: ubuntu-ui-toolkit (Ubuntu) Assignee: (unassigned) = Christian Dywan (kalikiana) ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1370571 Title: Read-only text field doesn't look read-only Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: Ubuntu 14.10 r244 1. Connect the phone to a Wi-Fi network if it isn't already. 2. Navigate to System Settings Wi-Fi the chevron next to the current network. 3. Tap in the IP address field. What you see: 2. The field is grey. 3. The field is white. What you should see: Since the field is read-only, it should look exactly the same when it isn't focused as when it is. (The use of a read-only text field is a workaround for bug 1286282.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1370571/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377294] Re: Indicator order change on the phone
This bug was fixed in the package indicator-bluetooth - 0.0.6+14.10.20141006-0ubuntu1 --- indicator-bluetooth (0.0.6+14.10.20141006-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Move the position of this indicator on the panel. (LP: #1377294) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 06 Oct 2014 17:22:41 + ** Branch linked: lp:ubuntu/utopic-proposed/indicator-bluetooth ** Branch linked: lp:ubuntu/utopic-proposed/indicator-power ** Branch linked: lp:ubuntu/utopic-proposed/indicator-network ** Changed in: indicator-bluetooth (Ubuntu) Status: New = Fix Released ** Changed in: indicator-power (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1377294 Title: Indicator order change on the phone Status in Bluetooth Menu: In Progress Status in The Date and Time Indicator: Invalid Status in Display Indicator: Invalid Status in Indicator Location: In Progress Status in The Messaging Menu: In Progress Status in Network Menu: In Progress Status in The Power Indicator: In Progress Status in Sound Menu: Invalid Status in Transfer Indicator: In Progress Status in “indicator-bluetooth” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-transfer” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: Design change: Panel items should be, from right to left: Time Alarm Power Volume Wifi Cellular Bluetooth Location Transfer Rotation Messages Which should translate into these ordering values: Datetime: 20 Power: 25 Sound: 30 Network: 35 Bluetooth: 36 Location: 60 Transfer: 71 Rotation: 90 Messages: 100 Documented: https://wiki.ubuntu.com/SystemComponents#Phone To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1377294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377294] Re: Indicator order change on the phone
This bug was fixed in the package indicator-power - 12.10.6+14.10.20141006-0ubuntu1 --- indicator-power (12.10.6+14.10.20141006-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Move the position of this indicator on the panel. (LP: #1377294) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 06 Oct 2014 17:31:07 + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1377294 Title: Indicator order change on the phone Status in Bluetooth Menu: In Progress Status in The Date and Time Indicator: Invalid Status in Display Indicator: Invalid Status in Indicator Location: In Progress Status in The Messaging Menu: In Progress Status in Network Menu: In Progress Status in The Power Indicator: In Progress Status in Sound Menu: Invalid Status in Transfer Indicator: In Progress Status in “indicator-bluetooth” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-transfer” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: Design change: Panel items should be, from right to left: Time Alarm Power Volume Wifi Cellular Bluetooth Location Transfer Rotation Messages Which should translate into these ordering values: Datetime: 20 Power: 25 Sound: 30 Network: 35 Bluetooth: 36 Location: 60 Transfer: 71 Rotation: 90 Messages: 100 Documented: https://wiki.ubuntu.com/SystemComponents#Phone To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1377294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377294] Re: Indicator order change on the phone
This bug was fixed in the package indicator-messages - 13.10.1+14.10.20141006-0ubuntu1 --- indicator-messages (13.10.1+14.10.20141006-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Move the position of this indicator on the panel. (LP: #1377294) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 06 Oct 2014 17:25:02 + ** Changed in: indicator-messages (Ubuntu) Status: New = Fix Released ** Changed in: indicator-network (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1377294 Title: Indicator order change on the phone Status in Bluetooth Menu: In Progress Status in The Date and Time Indicator: Invalid Status in Display Indicator: Invalid Status in Indicator Location: In Progress Status in The Messaging Menu: In Progress Status in Network Menu: In Progress Status in The Power Indicator: In Progress Status in Sound Menu: Invalid Status in Transfer Indicator: In Progress Status in “indicator-bluetooth” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-transfer” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: Design change: Panel items should be, from right to left: Time Alarm Power Volume Wifi Cellular Bluetooth Location Transfer Rotation Messages Which should translate into these ordering values: Datetime: 20 Power: 25 Sound: 30 Network: 35 Bluetooth: 36 Location: 60 Transfer: 71 Rotation: 90 Messages: 100 Documented: https://wiki.ubuntu.com/SystemComponents#Phone To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1377294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377294] Re: Indicator order change on the phone
This bug was fixed in the package indicator-network - 0.5.1+14.10.20141006-0ubuntu1 --- indicator-network (0.5.1+14.10.20141006-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Move the position of this indicator on the panel. (LP: #1377294) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 06 Oct 2014 17:27:23 + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1377294 Title: Indicator order change on the phone Status in Bluetooth Menu: In Progress Status in The Date and Time Indicator: Invalid Status in Display Indicator: Invalid Status in Indicator Location: In Progress Status in The Messaging Menu: In Progress Status in Network Menu: In Progress Status in The Power Indicator: In Progress Status in Sound Menu: Invalid Status in Transfer Indicator: In Progress Status in “indicator-bluetooth” package in Ubuntu: Fix Released Status in “indicator-location” package in Ubuntu: Fix Released Status in “indicator-messages” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-power” package in Ubuntu: Fix Released Status in “indicator-transfer” package in Ubuntu: Fix Released Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: Design change: Panel items should be, from right to left: Time Alarm Power Volume Wifi Cellular Bluetooth Location Transfer Rotation Messages Which should translate into these ordering values: Datetime: 20 Power: 25 Sound: 30 Network: 35 Bluetooth: 36 Location: 60 Transfer: 71 Rotation: 90 Messages: 100 Documented: https://wiki.ubuntu.com/SystemComponents#Phone To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1377294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377853] Re: Nested Mir server crashes on exit (corrupted double-linked list) since Mesa 10.3
** Changed in: mesa (Ubuntu) Milestone: None = ubuntu-14.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377853 Title: Nested Mir server crashes on exit (corrupted double-linked list) since Mesa 10.3 Status in Mir: In Progress Status in “mesa” package in Ubuntu: In Progress Bug description: Nested Mir server crashes on exit: 1. bin/mir_demo_server_minimal -f /tmp/outer sleep 1 ; bin/mir_demo_server_shell --host-socket /tmp/outer -f /tmp/inner 2. Ctrl+C 3. *** Error in `bin/mir_demo_server_shell': corrupted double-linked list: 0x0074e970 *** To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1377853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377727] Re: Desktop permissions (e.g shutdown, network, users) broken for all accounts after upgrade to 14.10
7. Running dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop from the terminal results in the error: Error org.freedesktop.ConsoleKit.Manager.NotPrivileged: Not Authorized That won't work indeed, as ConsoleKit has been dead since Ubuntu 13.10. There the change to logind and libpam_systemd happened, so if it worked under 14.04 I presume that libpam-systemd got configured correctly in /etc/pam.d/common-session. It should have a line like session optional pam_systemd.so. If not, that's the problem, can you confirm? Do you have the policykit-desktop-privileges package installed? ** Changed in: systemd (Ubuntu) Status: New = Incomplete -- 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/1377727 Title: Desktop permissions (e.g shutdown, network, users) broken for all accounts after upgrade to 14.10 Status in “systemd” package in Ubuntu: Incomplete Bug description: I reported this bug before as Bug #1372187 but it has been brought to my attention that Ubuntu switched from console-kit to logind after the 13.10 release. 1. System worked without any problems under 14.04 2. Upgrade to 14.10 3. Upgrade went without any problems 4. Notice that standby has disappeared from the gears menu 5. notice that I cannot disconnect or change the network connection (exact error is: (32) Not authorized to control networking.) 6. I can't see, change or unlock setting under Settings User accounts 7. Running dbus-send --system --print-reply --dest=org.freedesktop.ConsoleKit /org/freedesktop/ConsoleKit/Manager org.freedesktop.ConsoleKit.Manager.Stop from the terminal results in the error: Error org.freedesktop.ConsoleKit.Manager.NotPrivileged: Not Authorized 8. Running sudo pam-auth-update --force doesn't solve any errors 9. Creating a new user account (sudo adduser) and switching to the account results in the same permission problems. Output of: laurens@laurens-desktop:~$ loginctl list-sessions SESSION UID USER SEAT c1 110 lightdm seat0 c2 1000 laurens seat0 2 sessions listed. Sudo works as expected so I can help to further debug this problem and provide relevant information. Unfortunately I have very limited experience with Logind and PAM so I hope I have reported this to the right package. If someone could point me in the right direction (wiki, man page, tutorial) I would be more than happy to see if I can see what went wrong and if I can debug this myself. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libpam-systemd 208-8ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-17.23-generic 3.16.3 Uname: Linux 3.16.0-17-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Oct 5 22:34:02 2014 InstallationDate: Installed on 2013-04-21 (531 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130421) SourcePackage: systemd UpgradeStatus: Upgraded to utopic on 2014-09-14 (21 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1377727/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328798] Re: Setting default printer does not work
The bug also affects me with CUPS 1.5.3 and Ubuntu 12.04 LTS. Workaround posted by Phil works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cups in Ubuntu. https://bugs.launchpad.net/bugs/1328798 Title: Setting default printer does not work Status in “cups” package in Ubuntu: Confirmed Bug description: Setting default printer does not work. This is a nagging bug because it's affecting a commonly used, basic function. This bug persisted for a long time already. Upgrading from 13.10 to 14.04 did not help. In my system, there are three configured printers: 1) a locally connected one (which can be absent or not at boot) - 2) the same printer accessed over the network at another computer - 3) another network printer. Printer 3 should be the default printer, e.g. the one which is preselected when opening any print dialogue. One can set a default printer in system settings - printer. I did this many times. The check box is set (and is still set when re-entering the dialogue later or another time), but each time a print dialogue is accessed in any program, another printer is preselected and not printer 3. One can also set a default printer in the cups admin dialogue. This did not change the behavior. The desired printer is marked as default printer in the cups admin interface, but each time a print dialogue is accessed in e.g. okular, another printer is preselected. So one has to select each time the desired printer. Not having to do that each time is what the setting default printer (by whatever dialogue) is for, but it simply does not work. One thing I noticed is that in the /etc/cups/printers.conf, the desired printer (3) is marked as DefaultPrinter Kyocera, but the closing tag in this file is not named /DefaultPrinter as one would expect but just /Printer. Maybe there is a conflict between two different systems for setting a default printer (cups vs. system settings)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1328798/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378258] [NEW] /usr/bin/unity8:6:__assert_fail_base:__GI___assert_fail:__GI___pthread_mutex_lock:__gthread_mutex_lock:std::mutex::lock
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.00+14.10.20141006-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6edea87015728b4d954e6bfab317afe987a0c636 contains more details. ** Affects: dbus-cpp (Ubuntu) Importance: Undecided Status: New ** Tags: utopic -- 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/1378258 Title: /usr/bin/unity8:6:__assert_fail_base:__GI___assert_fail:__GI___pthread_mutex_lock:__gthread_mutex_lock:std::mutex::lock Status in “dbus-cpp” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.00+14.10.20141006-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6edea87015728b4d954e6bfab317afe987a0c636 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1378258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378258] Re: /usr/bin/unity8:6:__assert_fail_base:__GI___assert_fail:__GI___pthread_mutex_lock:__gthread_mutex_lock:std::mutex::lock
This is the most common unity8 crash these days. ** Package changed: unity8 (Ubuntu) = dbus-cpp (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1378258 Title: /usr/bin/unity8:6:__assert_fail_base:__GI___assert_fail:__GI___pthread_mutex_lock:__gthread_mutex_lock:std::mutex::lock Status in “dbus-cpp” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding unity8. This problem was most recently seen with version 8.00+14.10.20141006-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/6edea87015728b4d954e6bfab317afe987a0c636 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1378258/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1275398] Re: i915 driver/i945 hardware: Mir GL clients are rendered as black or transparent windows when using i945 graphics
It is in the 10.3. branch but a few commits after the 10.3 tags. So it will be in 10.3.1. Or we cherry pick that into 10.3? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1275398 Title: i915 driver/i945 hardware: Mir GL clients are rendered as black or transparent windows when using i945 graphics Status in Mir: Confirmed Status in “linux” package in Ubuntu: Invalid Status in “mesa” package in Ubuntu: In Progress Bug description: Running Mir on a Pentium D system with integrated i945 graphics, appears to work at first. The server starts and software clients are rendered correctly. However hardware (GL) clients are rendered as all black or transparent windows, despite logging to stdout that they think they are rendering: $ sudo bin/mir_demo_client_egltriangle Current active output is 1920x1200 +0+0 Server supports 2 of 6 surface pixel formats. Using format: 4 libEGL warning: unsupported platform (null) 1 FPS 33 FPS 60 FPS 60 FPS 60 FPS 60 FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1275398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378185] Re: Sometimes, header and departments combobox disappear
Please also attach unity8-dash.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1378185 Title: Sometimes, header and departments combobox disappear Status in “unity-scopes-shell” package in Ubuntu: New Bug description: This has happened to me twice on krillin #87 while testing silo 18 with unity-plugin-scopes 0.5.4+14.10.20141002.1-0ubuntu1 http://people.canonical.com/~platform/citrain_dashboard/#?distro=ubuntu-rtmq=landing-018 See the attached screenshot. What I did in this case was to install 2ubuntu. Then got back to the home screen clicking the back button on the header. The header appears again if I swipe down the dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scopes-shell/+bug/1378185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1240198] Re: Wrong keyboard layout active after booting into desktop
I noticed on a 12.04 system that something had created in the user home directory a directory called .xinput.d/ which contained the file (symbolic link) en_US - /etc/X11/xinit/xinput.d/ibus. I wonder what created this? Ibus? Why is it en_US despite the user keyboard locale in setxkb and other places was 'fi'? -- 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/1240198 Title: Wrong keyboard layout active after booting into desktop Status in “ibus” package in Ubuntu: Triaged Status in “indicator-keyboard” package in Ubuntu: Triaged Bug description: I upgraded from raring to saucy. After booting into the desktop (unity), the english keyboard layout is active, although everything on the system is set to be german (keyboard layout, language...) Switching to a virtual terminal (ctrl+alt+f1) fixes the problem and changes the layout to the german layout. all the time, the new input settings indicator says the german layout is active. locale says: LANG=de_DE.UTF-8 LANGUAGE=de_DE LC_CTYPE=de_DE.UTF-8 LC_NUMERIC=de_DE.UTF-8 LC_TIME=de_DE.UTF-8 LC_COLLATE=de_DE.UTF-8 LC_MONETARY=de_DE.UTF-8 LC_MESSAGES=de_DE.UTF-8 LC_PAPER=de_DE.UTF-8 LC_NAME=de_DE.UTF-8 LC_ADDRESS=de_DE.UTF-8 LC_TELEPHONE=de_DE.UTF-8 LC_MEASUREMENT=de_DE.UTF-8 LC_IDENTIFICATION=de_DE.UTF-8 LC_ALL= /etc/default/keyboard says: # Check /usr/share/doc/keyboard-configuration/README.Debian for # documentation on what to do after having modified this file. # The following variables describe your keyboard and can have the same # values as the XkbModel, XkbLayout, XkbVariant and XkbOptions options # in /etc/X11/xorg.conf. XKBMODEL=pc105 XKBLAYOUT=de XKBVARIANT= XKBOPTIONS= # If you don't want to use the XKB layout on the console, you can # specify an alternative keymap. Make sure it will be accessible # before /usr is mounted. # KMAP=/etc/console-setup/defkeymap.kmap.gz ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: indicator-keyboard 0.0.0+13.10.20131010.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 ApportVersion: 2.12.5-0ubuntu2 Architecture: amd64 Date: Tue Oct 15 20:49:03 2013 InstallationDate: Installed on 2013-04-26 (171 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True SourcePackage: indicator-keyboard UpgradeStatus: Upgraded to saucy on 2013-10-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1240198/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378265] [NEW] Icon position is inconsistent on the scopes
Public bug reported: Go to the dash, swiping scopes. In the Music scope I can see the search icon, the settings icon and the favourites icon. When I swipe to the next scope: my music scope, the search icon is in a different position. I was expecting to see the icons in the same position. ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: avengers ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378265 Title: Icon position is inconsistent on the scopes Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: New Bug description: Go to the dash, swiping scopes. In the Music scope I can see the search icon, the settings icon and the favourites icon. When I swipe to the next scope: my music scope, the search icon is in a different position. I was expecting to see the icons in the same position. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1378265/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1361825] Re: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1
For being sure that we get the full output, can you please run this python3 -c 'from gi.repository import Click' and copypaste the whole output? This looks like your glib is out of date (2.41.3-1), can you please upgrade to the current 14.10 version and check if it works then? If so, I'll bump the dependency in gobject- introspection. Thanks! ** Changed in: pygobject (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pygobject in Ubuntu. https://bugs.launchpad.net/bugs/1361825 Title: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 Status in “pygobject” package in Ubuntu: Incomplete Bug description: Got this when I started an xubuntu session on utopic. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: click-apparmor 0.2.9 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 Date: Mon Aug 25 11:20:50 2014 DuplicateSignature: package:click-apparmor:0.2.9:subprocess new pre-removal script returned error exit status 1 ErrorMessage: subprocess new pre-removal script returned error exit status 1 InstallationDate: Installed on 2013-05-31 (452 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) SourcePackage: click-apparmor SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: package click-apparmor 0.2.9 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-02-18 (189 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pygobject/+bug/1361825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374249] Re: Scrolling works erratically when sound center balance is off-center
This bug was fixed in the package indicator-sound - 12.10.2+14.10.20141007-0ubuntu1 --- indicator-sound (12.10.2+14.10.20141007-0ubuntu1) utopic; urgency=low [ Ted Gould ] * Merge trunk into older branches to resolve conflicts. [ Nick Dedekind ] * Use label for Volume sliders. [ Mirco Müller ] * Merge trunk into older branches to resolve conflicts. [ CI bot ] * Added use of synchronous notifications for volume-changes. (LP: #1232633) * Volume control: properly scale channels when setting the volume (LP: #1374249) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 07 Oct 2014 02:51:42 + ** Changed in: indicator-sound (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1374249 Title: Scrolling works erratically when sound center balance is off-center Status in “indicator-sound” package in Ubuntu: Fix Released Status in “unity-control-center” package in Ubuntu: Triaged Bug description: When the center balance is adjusted to the right, scrolling on the volume icon in the panel produces erratic results. The same thing happens when trying to adjust the volume in the sound menu. The volume buttons still function correctly though. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1374249/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1232633] Re: [system] Changing volume doesn't show feedback on the phone
This bug was fixed in the package indicator-sound - 12.10.2+14.10.20141007-0ubuntu1 --- indicator-sound (12.10.2+14.10.20141007-0ubuntu1) utopic; urgency=low [ Ted Gould ] * Merge trunk into older branches to resolve conflicts. [ Nick Dedekind ] * Use label for Volume sliders. [ Mirco Müller ] * Merge trunk into older branches to resolve conflicts. [ CI bot ] * Added use of synchronous notifications for volume-changes. (LP: #1232633) * Volume control: properly scale channels when setting the volume (LP: #1374249) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 07 Oct 2014 02:51:42 + ** Changed in: indicator-sound (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1232633 Title: [system] Changing volume doesn't show feedback on the phone Status in Ubuntu UX bugs: Fix Committed Status in “indicator-sound” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: In Progress Bug description: Not an indicator of volume status when it makes adjusting volume (Nexus 4) https://wiki.ubuntu.com/Sound#volume-keys: In addition, any of those keys/buttons should play a subtle noise for you to gauge the volume, and display a confirmation bubble with the icon of the primary sound output at the current volume, a volume bar, and accessible text “Sound muted” or “Volume {X}%” (for example, “Volume 75%”). **Update** For EU regulations: When listening to music/audio sources and the volume is raised above a certain threshold a warning must be displayed to user. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1232633/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374215] Re: Can't invoke UnlockAllModems() twice via dbus
** Branch unlinked: lp:~unity-api-team/indicator- network/dual_sim_pin_unlock -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374215 Title: Can't invoke UnlockAllModems() twice via dbus Status in Network Menu: Triaged Status in “indicator-network” package in Ubuntu: Triaged Bug description: Dialer-app now calls UnlockAllModems() when needed via dbus, but it only works for the first time. If I call the method once and then cancel the sim unlock screen, I can't call it again. The method just returns and the sim unlock screen never appears. Also, I noticed that after that sometimes the contents of the network indicator simply disappears as if the service was not running, but it in fact is. No crashes are observed. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1374215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378267] Re: Suspended app screenshots are blurry
And we should desaturate the screenshot while it's launching and show a spinner after a timeout if the app didn't come up yet. ** Changed in: unity8 (Ubuntu) Status: New = Triaged ** Changed in: unity8 (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378267 Title: Suspended app screenshots are blurry Status in “unity8” package in Ubuntu: Triaged Bug description: It's really obvious that an app has been suspended when I switch to it and the screengrab is really blurry. Would be really nice if it wasn't blurry. See screenshots. One shows blurry clock that I switched to, and then the non-blurry real clock a few seconds later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1378267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378267] Re: Suspended app screenshots are blurry
** Attachment added: device-2014-10-07-105914.png https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1378267/+attachment/4227360/+files/device-2014-10-07-105914.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378267 Title: Suspended app screenshots are blurry Status in “unity8” package in Ubuntu: Triaged Bug description: It's really obvious that an app has been suspended when I switch to it and the screengrab is really blurry. Would be really nice if it wasn't blurry. See screenshots. One shows blurry clock that I switched to, and then the non-blurry real clock a few seconds later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1378267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378267] [NEW] Suspended app screenshots are blurry
Public bug reported: It's really obvious that an app has been suspended when I switch to it and the screengrab is really blurry. Would be really nice if it wasn't blurry. See screenshots. One shows blurry clock that I switched to, and then the non-blurry real clock a few seconds later. ** Affects: unity8 (Ubuntu) Importance: High Status: Triaged ** Attachment added: device-2014-10-07-105904.png https://bugs.launchpad.net/bugs/1378267/+attachment/4227359/+files/device-2014-10-07-105904.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378267 Title: Suspended app screenshots are blurry Status in “unity8” package in Ubuntu: Triaged Bug description: It's really obvious that an app has been suspended when I switch to it and the screengrab is really blurry. Would be really nice if it wasn't blurry. See screenshots. One shows blurry clock that I switched to, and then the non-blurry real clock a few seconds later. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1378267/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376701] Re: invalid key/value pair in file /lib/udev/rules.d/
This isn't an udev bug, but bugs in the udev rules that various packages install. Creating tasks accordingly. /lib/udev/rules.d/40-libgphoto2-6.rules is indeed broken: SUBSYSTEM!=usb, GOTO=libgphoto2_usb_end That label doesn't exist. ** Package changed: systemd (Ubuntu) = libgphoto2 (Ubuntu) ** Changed in: libgphoto2 (Ubuntu) Importance: Undecided = Low ** Changed in: libgphoto2 (Ubuntu) Status: New = Triaged ** Changed in: libgphoto2 (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) ** Also affects: libmtp (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1376701 Title: invalid key/value pair in file /lib/udev/rules.d/ Status in “libgphoto2” package in Ubuntu: Triaged Status in “libmtp” package in Ubuntu: Triaged Bug description: from a fully updated Utopic (proposed enabled),(booting with systemd- boot), the syslog file shown these errors: (following that linux-boot-prober: debug: running /usr/lib/linux- boot-probes/50mounted-tests) Oct 2 08:36:16 u32 systemd-udevd[241]: GOTO 'libgphoto2_usb_end' has no matching label in: '/lib/udev/rules.d/40-libgphoto2-6.rules' Oct 2 08:36:16 u32 systemd-udevd[241]: invalid key/value pair in file /lib/udev/rules.d/40-usb-media-players.rules on line 26,starting at character 25 ('m') Oct 2 08:36:16 u32 systemd-udevd[241]: invalid key/value pair in file /lib/udev/rules.d/69-libmtp.rules on line 1,starting at character 1 ('n') That has happened while upgrading some packages from synaptic: purging an old kernel, installing a newest one Then later, after grub2 processes ended, get these errors: linux-boot-prober: debug: linux detected by /usr/lib/linux-boot-probes/50mounted-tests Oct 2 08:43:15 u32 systemd[1]: Reloading. Oct 2 08:43:15 u32 systemd[1]: [/lib/systemd/system/friendly-recovery.service:14] Executable path is not absolute, ignoring: dmesg --console-off Oct 2 08:43:15 u32 systemd[1]: [/lib/systemd/system/rtkit-daemon.service:32] Unknown lvalue 'ControlGroup' in section 'Service' Oct 2 08:43:15 u32 systemd[1]: Cannot add dependency job for unit systemd-vconsole-setup.service, ignoring: Unit systemd-vconsole-setup.service failed to load: No such file or directory. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: systemd 208-8ubuntu7 ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3 Uname: Linux 3.16.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu2 Architecture: i386 CurrentDesktop: GNOME Date: Thu Oct 2 14:10:08 2014 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgphoto2/+bug/1376701/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349281] Re: The exposed open windows are displayed in the correct order
** Branch linked: lp:~hikiko/unity/unity.1349281 -- 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/1349281 Title: The exposed open windows are displayed in the correct order Status in Unity: Confirmed Status in “unity” package in Ubuntu: New Bug description: When multiple non-maximised windows of the same program are open and one clicks on the icon of the program in the launcher, they are all shown one next to each other but in the wrong order: windows that are in the top-left corner can be shown in the right bottom position or on the top bottom corner. This makes very hard to switch between similarly looking windows like terminals. How to reproduce: * launch four or so terminal windows; * write something different on each of them to be able to tell them apart; * move each window to a different corner, possibly using the auto-resizing feature of Unity; * click on the terminal icon in the launcher; * many terminal windows are displayed; * choose the thumbnail in the right-top corner; * very likely a window that was in another corner has been selected; * try again various time and realize how confusing this all is. The thing that is more strange is that you have to move the mouse pointer to a certain point (let's say right-top), then you see the window has appeared far away (let's say bottom-left) so you have to move your mouse again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378278] [NEW] Inconsistent artwork between scope and app
Public bug reported: I have only one Bruno Mars and one Daft Punk album on my device. In the Music Scope initial view they show with one set of artwork. In the Music app and the expanded Music Scope they show different artwork. Should these not be consistent? Scope:- http://imgur.com/yKR0hof Scope, expanded:- http://imgur.com/GqtRI5a Further example:- http://imgur.com/cL3E0Ni I don't have a screenshot from the Music App, but it shows the same as the scope expanded view. ** Affects: music-app Importance: Undecided Status: New ** Affects: unity-scope-mediascanner (Ubuntu) Importance: Undecided Status: New ** Also affects: unity-scope-mediascanner (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1378278 Title: Inconsistent artwork between scope and app Status in Music application for Ubuntu devices: New Status in “unity-scope-mediascanner” package in Ubuntu: New Bug description: I have only one Bruno Mars and one Daft Punk album on my device. In the Music Scope initial view they show with one set of artwork. In the Music app and the expanded Music Scope they show different artwork. Should these not be consistent? Scope:- http://imgur.com/yKR0hof Scope, expanded:- http://imgur.com/GqtRI5a Further example:- http://imgur.com/cL3E0Ni I don't have a screenshot from the Music App, but it shows the same as the scope expanded view. To manage notifications about this bug go to: https://bugs.launchpad.net/music-app/+bug/1378278/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1349281] Re: The exposed open windows are displayed in the correct order
** Changed in: unity Status: Confirmed = In Progress -- 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/1349281 Title: The exposed open windows are displayed in the correct order Status in Unity: In Progress Status in “unity” package in Ubuntu: New Bug description: When multiple non-maximised windows of the same program are open and one clicks on the icon of the program in the launcher, they are all shown one next to each other but in the wrong order: windows that are in the top-left corner can be shown in the right bottom position or on the top bottom corner. This makes very hard to switch between similarly looking windows like terminals. How to reproduce: * launch four or so terminal windows; * write something different on each of them to be able to tell them apart; * move each window to a different corner, possibly using the auto-resizing feature of Unity; * click on the terminal icon in the launcher; * many terminal windows are displayed; * choose the thumbnail in the right-top corner; * very likely a window that was in another corner has been selected; * try again various time and realize how confusing this all is. The thing that is more strange is that you have to move the mouse pointer to a certain point (let's say right-top), then you see the window has appeared far away (let's say bottom-left) so you have to move your mouse again. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1349281/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377812] Re: Pull down indicator menu not working properly
** Package changed: indicator-network (Ubuntu) = unity8 (Ubuntu) -- 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/1377812 Title: Pull down indicator menu not working properly Status in “unity8” package in Ubuntu: New Bug description: Mako rtm r72 I am not sure where to post this bug, so I post it here. Feel free to move it elsewhere if this is not the correct place to post it. In the last two images for mako (171 172) it is not working properly. Either I can't pull the menu down more than 10-15 mm or it flickers while being pulled down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372563] Re: [system-settings] Checkbox missing haptic response
** Description changed: utopic-proposed-krillin r40 Ubuntu 14.10 r257 1. Go to System Settings Sound, a screen that contains both switches and checkboxes. 2. Tap on a switch or checkbox. 3. Tap on the label next to a switch or checkbox. What happens: 2. Tapping on the switch or checkbox gives haptic feedback. 3. Tapping on the label similarly toggles the control, but with no haptic feedback. What should happen: Tapping on the label behaves exactly the same as tapping on the control itself. One way of fixing this bug would be to add haptic feedback to the labels. Another would be to remove haptic feedback for taps altogether (bug 1267592). + + Code example: + + ListItem.Standard { + control: CheckBox { + objectName: callVibrate + checked: true + } + text: i18n.tr(Vibrate when ringing) + } ** Summary changed: - [system-settings] Checkbox missing haptic response + Checkbox in ListItem missing haptic response ** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1372563 Title: Checkbox in ListItem missing haptic response Status in Ubuntu UX bugs: New Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: utopic-proposed-krillin r40 Ubuntu 14.10 r257 1. Go to System Settings Sound, a screen that contains both switches and checkboxes. 2. Tap on a switch or checkbox. 3. Tap on the label next to a switch or checkbox. What happens: 2. Tapping on the switch or checkbox gives haptic feedback. 3. Tapping on the label similarly toggles the control, but with no haptic feedback. What should happen: Tapping on the label behaves exactly the same as tapping on the control itself. One way of fixing this bug would be to add haptic feedback to the labels. Another would be to remove haptic feedback for taps altogether (bug 1267592). Code example: ListItem.Standard { control: CheckBox { objectName: callVibrate checked: true } text: i18n.tr(Vibrate when ringing) } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1372563/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1286620] Re: created header elemnt not added to parent in setHeader in list.js
** Package changed: ubuntu-ui-toolkit (Ubuntu) = cordova-ubuntu (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cordova-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1286620 Title: created header elemnt not added to parent in setHeader in list.js Status in “cordova-ubuntu” package in Ubuntu: New Bug description: file ubuntu-html5-ui-toolkit/js/list.js If the header element doesn't exist in the function setHeader a new one is created but it isn't added to the parent (line 97) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cordova-ubuntu/+bug/1286620/+subscriptions -- Mailing list: https://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 1371032] Re: Cannot send MMS from Yoigo
On Tuesday, October 7, 2014, Víctor R. Ruiz 1371...@bugs.launchpad.net wrote: I received the MMS to Yoigo, but couldn't send from it (at least the message didn't arrive to my other phone). Oh, that is not the fault of nuntium or our stack. The carrier replied an OK for the send request. Does it take long when sent from a different OS? Delivery in any case depends on many things. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1371032 Title: Cannot send MMS from Yoigo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1371032/+subscriptions -- 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/1371032 Title: Cannot send MMS from Yoigo Status in “messaging-app” package in Ubuntu: Incomplete Status in “network-manager” package in Ubuntu: Incomplete Status in “nuntium” package in Ubuntu: Fix Released Status in “ofono” package in Ubuntu: Invalid Status in “nuntium” package in Ubuntu RTM: Fix Released Bug description: phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/list-contexts [ /ril_1 ] [ /ril_0 ] [ /ril_0/context1 ] AccessPointName = internet Name = Yoigo Internet Password = Protocol = ip IPv6.Settings = { } Type = internet Active = 1 Username = Settings = { DomainNameServers=217.168.13.34,46.6.113.2, Address=10.192.132.31 Method=static Netmask=255.255.255.0 Gateway=10.192.132.31 Interface=ccmni0 } [ /ril_0/context2 ] AccessPointName = mms MessageCenter = http://mmss/ Name = Yoigo MMS Password = Protocol = ip MessageProxy = 193.209.134.141:80 IPv6.Settings = { } Type = mms Active = 0 Username = Settings = { } phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 2 Error activating /ril_0/context2: org.ofono.Error.NotAttached: GPRS is not attached phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/activate-context /ril_0 1 Additional info: - I didn't see any error in the messaging app. - Couldn't send nor receive MMS. - 3G connection is activated, but usually after a reboot. After a while, it looses it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/messaging-app/+bug/1371032/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377812] Re: Pull down indicator menu not working properly
Image 171/172? Or rtm 71/72? Could you please record a video of the broken behaviour, I can't reproduce here? ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1377812 Title: Pull down indicator menu not working properly Status in “unity8” package in Ubuntu: Incomplete Bug description: Mako rtm r72 I am not sure where to post this bug, so I post it here. Feel free to move it elsewhere if this is not the correct place to post it. In the last two images for mako (171 172) it is not working properly. Either I can't pull the menu down more than 10-15 mm or it flickers while being pulled down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1103961] Re: nux::IOpenGLShaderProgram::Begin crashes on nVidia 10de:00fd
tag -patch done * Sergio Gelato [2014-10-07 06:27:49 +]: I've upgraded the OS on the affected computer to trusty and found that the problem is still present in trusty's version of nux. Same symptoms, and my patch still applies. I'll take that back: the patch still applies but is no longer useful since it no longer results in compiz-2d being invoked. compiz starts anyway, the LIBGL_ALWAYS_SOFTWARE setting is not applicable because I'm using nVidia's proprietary OpenGL libraries rather than Mesa, and so I get a crash. That means one needs to fix the actual cause of the crash. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1103961 Title: nux::IOpenGLShaderProgram::Begin crashes on nVidia 10de:00fd Status in “nux” package in Ubuntu: New Bug description: After upgrading to precise and activating nvidia-173 (173.14.35) on a machine with the following graphics card: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation NV37GL [Quadro PCI-E Series] [10de:00fd] (rev a2) /usr/bin/compiz started to crash with the exact same symptoms as in bug #768178. (I'm filing a new bug since that one is marked as a duplicate of a quite different bug that is itself marked as invalid.) This isn't too surprising since the graphics card is a close relative of the GeForce FX series, various flavours of which are already blacklisted in nux. Forcing Unity 2D works around the problem, so I've applied the attached patch on top of nux 2.14.1-0ubuntu1. Maybe one could set _use_glsl_shaders = false in NuxGraphics/GraphicsEngine.cpp instead but I don't have the time to test this conjecture. glGetString(GL_RENDERER) returns Quadro PCI-E Series/PCI/SSE2 for this card and driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nux/+bug/1103961/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377853] Re: Nested Mir server crashes on exit (corrupted double-linked list) since Mesa 10.3
** Patch added: mesa-10.3-egl-platform-update.debdiff https://bugs.launchpad.net/mir/+bug/1377853/+attachment/4227409/+files/mesa-10.3-egl-platform-update.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377853 Title: Nested Mir server crashes on exit (corrupted double-linked list) since Mesa 10.3 Status in Mir: In Progress Status in “mesa” package in Ubuntu: In Progress Bug description: Nested Mir server crashes on exit: 1. bin/mir_demo_server_minimal -f /tmp/outer sleep 1 ; bin/mir_demo_server_shell --host-socket /tmp/outer -f /tmp/inner 2. Ctrl+C 3. *** Error in `bin/mir_demo_server_shell': corrupted double-linked list: 0x0074e970 *** To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1377853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372563] Re: Checkbox in ListItem missing haptic response
** Branch linked: lp:~ubuntu-sdk-team/ubuntu-ui-toolkit/pullTheTrigger -- 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/1372563 Title: Checkbox in ListItem missing haptic response Status in Ubuntu UX bugs: New Status in “ubuntu-ui-toolkit” package in Ubuntu: Confirmed Bug description: utopic-proposed-krillin r40 Ubuntu 14.10 r257 1. Go to System Settings Sound, a screen that contains both switches and checkboxes. 2. Tap on a switch or checkbox. 3. Tap on the label next to a switch or checkbox. What happens: 2. Tapping on the switch or checkbox gives haptic feedback. 3. Tapping on the label similarly toggles the control, but with no haptic feedback. What should happen: Tapping on the label behaves exactly the same as tapping on the control itself. One way of fixing this bug would be to add haptic feedback to the labels. Another would be to remove haptic feedback for taps altogether (bug 1267592). Code example: ListItem.Standard { control: CheckBox { objectName: callVibrate checked: true } text: i18n.tr(Vibrate when ringing) } To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1372563/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1359831] Re: Apps incorrectly perform a chmod on XDG_RUNTIME_DIR
I can confirm that the warning caused by QStandardDialogs::writableLocation(RuntimeLocation) doesn't chmod anymore, no warning log is shown anymore on camera app logs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1359831 Title: Apps incorrectly perform a chmod on XDG_RUNTIME_DIR Status in Camera App: Confirmed Status in Ubuntu Reminders app: Invalid Status in Sudoku game for Ubuntu Touch: Invalid Status in “qtbase-opensource-src” package in Ubuntu: Incomplete Bug description: From bug #1351041: [Thu Jul 31 21:04:20 2014] type=1400 audit(1406837062.464:97): apparmor=DENIED operation=chmod profile=com.ubuntu.reminders_reminders_0.5.203 name=/run/user/32011/ pid=12954 comm=reminders requested_mask=w denied_mask=w fsuid=32011 ouid=32011 From irc: Aug 21 15:47:20 ubuntu-phablet kernel: [ 251.843308] type=1400 audit(1408636040.346:137): apparmor=DENIED operation=chmod profile=com.ubuntu.camera_camera_3.0.0.355 name=/run/user/32011/ pid=4172 comm=camera-app requested_mask=w denied_mask=w fsuid=32011 ouid=32011 AppArmor policy is correct on this denial-- apps should not be able to change the permissions on the /run/user/32011/ (XDG_RUNTIME_DIR) directory. I filed this against camera-app and reminders, but my guess is this is an underlying library that is causing this. I don't know if the denial is causing errors with the app, but it is causing confusion for users and developers who see the denial. To manage notifications about this bug go to: https://bugs.launchpad.net/camera-app/+bug/1359831/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373462] Re: [background] Preview/Background is black for some images
This impacts also the photo scope, does the unity8 fix applies to scopes? -- 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/1373462 Title: [background] Preview/Background is black for some images Status in Libqtelegram - a qt library to access telegram.: Fix Committed Status in Messaging App: New Status in “messaging-app” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “messaging-app” package in Ubuntu RTM: New Bug description: With some images the preview and the background is black but the image is fine in the gallery app. For example picture attached looks correct, but preview and background are black. TEST CASE: 1. Upload the attached picture to the phone with mtp 2. Go to system-settings / background 3. Tap 'Add an image' 4. Select this image - Verify that the preview is correct 5. Validate your choice, 6. Press the power button twice to show the greeter - Verify that the background is correct ACTUAL RESULT Background and preview are black. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140913-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Sep 24 16:34:18 2014 InstallationDate: Installed on 2014-09-16 (8 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-030205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1373462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373462] Re: [background] Preview/Background is black for some images
** Branch linked: lp:~unity-team/unity8/croppedImageMinimumSourceSize -- 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/1373462 Title: [background] Preview/Background is black for some images Status in Libqtelegram - a qt library to access telegram.: Fix Committed Status in Messaging App: New Status in “messaging-app” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “messaging-app” package in Ubuntu RTM: New Bug description: With some images the preview and the background is black but the image is fine in the gallery app. For example picture attached looks correct, but preview and background are black. TEST CASE: 1. Upload the attached picture to the phone with mtp 2. Go to system-settings / background 3. Tap 'Add an image' 4. Select this image - Verify that the preview is correct 5. Validate your choice, 6. Press the power button twice to show the greeter - Verify that the background is correct ACTUAL RESULT Background and preview are black. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140913-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Sep 24 16:34:18 2014 InstallationDate: Installed on 2014-09-16 (8 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-030205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1373462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1270579] Re: Ubuntu should have an init script for saving/restoring backlight level on laptops
Right, if you boot 14.10 with systemd this should already work. But that job doesn't run under upstart. So either we wait until systemd becomes the init in Ubuntu, or we write a corresponding upstart job that calls /lib/systemd/systemd-backlight. ** Changed in: sysvinit (Ubuntu) Importance: Medium = Wishlist ** Changed in: sysvinit (Ubuntu) Status: Confirmed = Triaged ** Changed in: sysvinit (Ubuntu) Status: Triaged = Invalid ** Changed in: systemd (Ubuntu) Importance: Undecided = Wishlist ** Changed in: systemd (Ubuntu) Status: New = Triaged ** Summary changed: - Ubuntu should have an init script for saving/restoring backlight level on laptops + Ubuntu should have an upstart job for saving/restoring backlight level on laptops -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1270579 Title: Ubuntu should have an upstart job for saving/restoring backlight level on laptops Status in elementary OS: New Status in One Hundred Papercuts: Confirmed Status in Ubuntu MATE: Opinion Status in “systemd” package in Ubuntu: Triaged Status in “sysvinit” package in Ubuntu: Invalid Status in “sysvinit” package in Debian: New Bug description: I have tested many distros - Arch, OpenSuSe 13.1, Fedora 20, ALT Linux p7, Sabayon, Mageia 4. Many of them are based on systemd. It does not matter what init system they use, but all of them have very usefull script (or binary program, I don't know) for saving and restoring backlight level on laptop. In these distros there is a script for save and restore backlight levels for two video-cards (acpi_video0 and acpi_video1). During system boot it is indicated as follows: [ OK ] Started Load/Save Screen Backlight Brightness of acpi_video1. [ OK ] Started Load/Save Screen Backlight Brightness of acpi_video0. . I have a draft version, which works normally on my VAIO F13Z1R laptop with Ubuntu 12.04.4. It is in attachment. You can use it unmodified or modify it for compatibility or something. I made symlinks for it: ln -s /etc/init.d/brightness /etc/rc0.d/S25backlight ln -s /etc/init.d/brightness /etc/rcS.d/S25backlight ln -s /etc/init.d/brightness /etc/rc6.d/S25backlight For details you can read my comment on askubuntu (http://askubuntu.com/a/227553/66509). I think that having a script for saving and restoring backlight level is very useful for laptop Ubuntu users. So, please, add such init script to default Ubuntu installation. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: initscripts 2.88dsf-41ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-4.19-generic 3.13.0-rc8 Uname: Linux 3.13.0-4-generic i686 ApportVersion: 2.13.1-0ubuntu1 Architecture: i386 CurrentDesktop: GNOME Date: Sun Jan 19 17:20:26 2014 InstallationDate: Installed on 2013-10-20 (91 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: sysvinit UpgradeStatus: Upgraded to trusty on 2013-11-19 (61 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1270579/+subscriptions -- Mailing list: https://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 1376849] Re: em28xx audio device no sound (Pinnacle Dazzle DVC100, Terratec Grabby)
The devices both appear in pulseaudio settings, but there is no audio input whatsoever. Both devices have been tested on other OSs, so I can rule out any external problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1376849 Title: em28xx audio device no sound (Pinnacle Dazzle DVC100, Terratec Grabby) Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I'm getting no input signal at all with these devices. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-36.63-lowlatency 3.13.11.6 Uname: Linux 3.13.0-36-lowlatency x86_64 ApportVersion: 2.14.1-0ubuntu3.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: zequence 1679 F pulseaudio /dev/snd/controlC0: zequence 1679 F pulseaudio CurrentDesktop: XFCE Date: Thu Oct 2 19:02:28 2014 InstallationDate: Installed on 2014-10-02 (0 days ago) InstallationMedia: Ubuntu-Studio 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.1) PackageArchitecture: all SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/08/2008 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: R2111Q0 dmi.board.asset.tag: N/A dmi.board.name: VAIO dmi.board.vendor: Sony Corporation dmi.board.version: N/A dmi.chassis.asset.tag: N/A dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR2111Q0:bd09/08/2008:svnSonyCorporation:pnVGN-CR31Z_R:pvr01:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-CR31Z_R dmi.product.version: 01 dmi.sys.vendor: Sony Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1376849/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377853] Re: Nested Mir server crashes on exit (corrupted double-linked list) since Mesa 10.3
** Patch removed: mesa-10.3-egl-platform-update.debdiff https://bugs.launchpad.net/mir/+bug/1377853/+attachment/4227409/+files/mesa-10.3-egl-platform-update.debdiff ** Patch added: mesa-10.3-egl-platform-update.debdiff https://bugs.launchpad.net/mir/+bug/1377853/+attachment/4227413/+files/mesa-10.3-egl-platform-update.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1377853 Title: Nested Mir server crashes on exit (corrupted double-linked list) since Mesa 10.3 Status in Mir: In Progress Status in “mesa” package in Ubuntu: In Progress Bug description: Nested Mir server crashes on exit: 1. bin/mir_demo_server_minimal -f /tmp/outer sleep 1 ; bin/mir_demo_server_shell --host-socket /tmp/outer -f /tmp/inner 2. Ctrl+C 3. *** Error in `bin/mir_demo_server_shell': corrupted double-linked list: 0x0074e970 *** To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1377853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373462] Re: [background] Preview/Background is black for some images
The branch I just attached (lp:~unity- team/unity8/croppedImageMinimumSourceSize) fixes this for scope results. If you still find this problem somewhere, please file a separate bug against unity8. -- 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/1373462 Title: [background] Preview/Background is black for some images Status in Libqtelegram - a qt library to access telegram.: Fix Committed Status in Messaging App: New Status in “messaging-app” package in Ubuntu: Confirmed Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “messaging-app” package in Ubuntu RTM: New Bug description: With some images the preview and the background is black but the image is fine in the gallery app. For example picture attached looks correct, but preview and background are black. TEST CASE: 1. Upload the attached picture to the phone with mtp 2. Go to system-settings / background 3. Tap 'Add an image' 4. Select this image - Verify that the preview is correct 5. Validate your choice, 6. Press the power button twice to show the greeter - Verify that the background is correct ACTUAL RESULT Background and preview are black. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-system-settings 0.3+14.10.20140913-0ubuntu1 [origin: Ubuntu RTM] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf Date: Wed Sep 24 16:34:18 2014 InstallationDate: Installed on 2014-09-16 (8 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140916-030205) SourcePackage: ubuntu-system-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/libqtelegram/+bug/1373462/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1376302] Re: indicator-network is frequently logging to /home/phablet/.cache/upstart/indicator-network.log
** Branch linked: lp:~jpakkane/indicator-network/tracetoggle -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1376302 Title: indicator-network is frequently logging to /home/phablet/.cache/upstart/indicator-network.log Status in “indicator-network” package in Ubuntu: Triaged Bug description: I was trying to figure out where excessive file system writes were coming from (to try to reduce flash writes and hence reduce power consumption) and I spotted that /home/phablet/.cache/upstart /indicator-network.log is being written to rather often (every minute or so) (tail -f the log and see what I mean). On my phone it the log seems to be being filled with the same 3 types of messages over and over: void org::ofono::Interface::NetworkRegistration::_updateProperty(std::string, core::dbus::types::Variant): unhandled property change: MobileCountryCode void org::ofono::Interface::NetworkRegistration::_updateProperty(std::string, core::dbus::types::Variant): unhandled property change: MobileNetworkCode void org::ofono::Interface::NetworkRegistration::_updateProperty(std::string, core::dbus::types::Variant): unhandled property change: CellId I guess these look like some kind of error message from ofono. In the period of an hour I see ~28K of messages being written, which although isn't huge, it is extra work for the system to write and I think the messages may need looking into and investigating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1376302/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1245951] Re: Wrong oFono property used for data technology indication
OK, now an actual real world case from asac where the technology and bearer don't match: https://pastebin.canonical.com/118313/ Would still keep this as Medium, as the worst case scenario is that the user actually sees 3G instead of 2G. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1245951 Title: Wrong oFono property used for data technology indication Status in Network Menu: Triaged Status in “indicator-network” package in Ubuntu: Triaged Bug description: Image: Touch #100 ( aka v1.0 ). The current indicator-network code uses the ofono's NetworkRegistration interface's Technology property to determine which mobile data connection icon to display on the status bar. The code currently compares the value of Technology to: - gsm -- this causes 2G ( or a tortoise ) to be displayed - umts -- this causes 3G to be displayed - edge -- this causes E to be displayed - hspa -- this causes H to be displayed - lte -- valid, but currently not supported in the ofono/rilmodem driver ( LTE isn't yet 100% supported ) The code instead should be examining ofono's ConnectionManager interface's Bearer property. This is not currently being set by the ofono/rilmodem code ( see bug #1245954 for more details ). The valid values of the Bearer property ( with associated icons in parentheses ) are: none, gprs ( 2G ), edge ( E ), umts ( 3G ), hsupa/hsdpa/hspa ( H ), and lte ( L ). oFono doesn't currently support reporting HSPA+, whereas RIL does, so if have the need for differentiating between HSPA and HSPA+, then we'll need to patch ofono so that the value hspap is valid for Bearer. - To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1245951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378177] Re: Turn screen off when invactive timeout doesn't work
*** This bug is a duplicate of bug 1377847 *** https://bugs.launchpad.net/bugs/1377847 ** This bug has been marked a duplicate of bug 1377847 unity screen saver no longer blanks nor locks automatically -- 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/1378177 Title: Turn screen off when invactive timeout doesn't work Status in “unity” package in Ubuntu: New Bug description: I left my laptop open and running tonight when away. When I returned 1.5 hours later, my screen was still on, all black except for a white mouse pointer. I locked the screen with the windows+L combo and walked away when the lock screen displayed properly. The Brightness Lock section of the control panel shows Turn screen off when inactive for: 5 minutes. Lock is turned on, Lock screen after: 5 minutes, and Require my password when waking from suspend. I didn't suspend, and I manually locked before leaving. Thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.2+14.04.20140714-0ubuntu1.1 ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6 Uname: Linux 3.13.0-35-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: Unity Date: Mon Oct 6 21:42:24 2014 InstallationDate: Installed on 2012-10-18 (718 days ago) InstallationMedia: Ubuntu 12.04.1 LTS Precise Pangolin - Release amd64 (20120823.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-04-12 (178 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1378177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339883] Re: unity8-dash on the phone has unreasonable CPU usage when system is idle with screen off
** Changed in: qtmir Status: In Progress = 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/1339883 Title: unity8-dash on the phone has unreasonable CPU usage when system is idle with screen off Status in Qt integration with the Mir display server: Fix Released Status in The Ubuntu Power Consumption Project: New Status in “unity8” package in Ubuntu: Fix Released Bug description: I am attaching tty recordings of htop running on N4 with the latest image. This is with screen off, no apps running, system has settled after boot. Three recordings of the major CPU usage offenders are included: unity8 smartscopesproxy mpdecision (probably not directly related to unity8 but adding for completeness, please point me to a better place to report this if you know) To replay the tty recordings use ttyplay file.tty (from ubuntu package ttyrec) To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1339883/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp