[Touch-packages] [Bug 1355111] Re: newgrp fails with "crypt: Invalid argument"
I was getting this issue on ubuntu 15.04 (Vivid Vervet) too... However I've found a workaround, running 'grpconv' as root fixed the problem for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1355111 Title: newgrp fails with "crypt: Invalid argument" Status in Shadow: Unknown Status in shadow package in Ubuntu: Confirmed Bug description: entry from /etc/passwd: user:x:1000:1000:User,,,:/home/user:/bin/bash entry from /etc/group: dummy:x:200:user entry from /etc/gshadow: dummy:*:: logged on as user the command "newgrp dummy" asks for a password and fails with "crypt: Invalid argument" after removing the line for dummy from gshadow newgrp works A similar bug was reported on the redhat tracker: https://bugzilla.redhat.com/show_bug.cgi?id=988184 cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION="Ubuntu 14.04 LTS" To manage notifications about this bug go to: https://bugs.launchpad.net/shadow/+bug/1355111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467740] Re: Lots of thumbnail requests with invalid size
I think this is actually on the Unity8 side rather than unity-scopes- shell. The result cards are generated by CardCreator.js, which uses a CroppedImageMinimumSourceSize component to display the result art: http://bazaar.launchpad.net/~unity- team/unity8/trunk/view/head:/plugins/Dash/CardCreator.js#L101 This component is implemented in QML but delegates finding the size of the image to the C++ component CroppedImageSizer http://bazaar.launchpad.net/~unity- team/unity8/trunk/view/head:/plugins/Dash/CroppedImageMinimumSourceSize.qml That class uses QNetworkAccessManager to try and get the file contents and uses a helper class to manage the response: http://bazaar.launchpad.net/~unity- team/unity8/trunk/view/head:/plugins/Dash/croppedimagesizer.cpp#L102 That helper tries to read the returned data via QImageReader and passes the image size back to CroppedImageSizer: http://bazaar.launchpad.net/~unity- team/unity8/trunk/view/head:/plugins/Dash/croppedimagesizerasyncworker.cpp#L58 If the worker provides a non-empty size, CroppedImageSizer then uses that size information to pick a sourceSize value that will result in the image being loaded at the correct size so it only has to be cropped in at most one dimension to fit. If an empty (or invalid) size is provided, it sets sourceSize to (0, 0): http://bazaar.launchpad.net/~unity- team/unity8/trunk/view/head:/plugins/Dash/croppedimagesizer.cpp#L118 This causes a problem for the thumbnailer because QNetworkAccessManager has no idea how to deal with image:// URIs, so we get an invalid QSize from the worker and use a sourceSize of (0, 0). Perhaps it should just use the requested dimensions in this case instead. It doesn't look like there is a way to handle this crop mode properly with QQuickImageProvider. ** Package changed: unity-scopes-shell (Ubuntu) => unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1467740 Title: Lots of thumbnail requests with invalid size Status in thumbnailer package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When using scopes, the thumbnailer gets loads of requests with QSize(-1,-1) from the shell. For example, with a bunch of videos recorded, run up the video scope and go to "My Videos". The shell asks for a thumbnail at QSize(-1,-1) for the tiny thumbnail that appears to the left of each list entry. The problem with this is that the thumbnailer interprets this to mean "give me the largest size you can (limited to a 1920x1920 bounding box). That's very expensive, especially in terms of disk space, because that 1920 "thumbnail" ends up going into the cache, needlessly hogging space. We are about to add a qWarning message to the QML side that reports invalid QSize requests. For now, we are going to retain the old behavior, but this will turn into an error soon. The most effective way to use the thumbnailer is to simply ask for an image in the desired size, with neither width nor height of -1. The thumbnailer will efficiently produce a thumbnail for that. (We do lots of internal caching to avoid extracting or downloading a thumbnail unnecessarily.) The thumbnailer may deliver a thumbnail that is smaller than what was asked for (because it never up-scales) so, if asked for a thumbnail of size 256, it's guaranteed not to be larger, but might be smaller (if the original image is smaller than what was asked for). Could you please adjust the shell behavior to ask for specific, valid sizes only? Running a tail -f on ~/.cache/upstart/dbus.log allows you to see the requests as they are made. Each request shows the size that was asked for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1467740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1464053] Re: ubuntu-bug is broken (only) within Mate, because of gvfs-open.
I can't reproduce this in Ubuntu MATE 15.04 or Ubuntu MATE 15.10. ** Changed in: ubuntu-mate Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1464053 Title: ubuntu-bug is broken (only) within Mate, because of gvfs-open. Status in ubuntu-mate: Incomplete Status in apport package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Bug description: The ubuntu bug reporting system is rather badly broken, because when I run ubuntu-bug/apport-bug, it gathers data, then opens a new blank firefox window, but does not connect to launchpad! The root cause is this one: https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1427144 which basically means that apport needs to invoke firefox with a different set of options. This should be trivial to fix, but I think it's rather important, especially given how hard it is to get a direct report into Launchpad, and all the redirects that emphasise using the ubuntu-bug tool: https://help.ubuntu.com/community/ReportingBugs (I'm reporting this from Ubuntu Wily, though I think I recall seeing it in Vivid) Apport version is: 2.17.3-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1464053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488391] [NEW] Double buffering is only smooth while you're touching it
*** This bug is a duplicate of bug 1488386 *** https://bugs.launchpad.net/bugs/1488386 Public bug reported: On some devices (mako at least) it's possible to force double buffering and it will often keep up: restart unity8 QML_NO_TOUCH_COMPRESSION=1 MIR_SERVER_NBUFFERS=2 Curiously however it only keeps up smoothly (eg. during a dash scroll) while you're touching the screen. If you lift off or fling the dash then it immediately stutters, quite badly. So the issue is not that the device can't keep up with double buffering. It seems more like we're not keeping the kernel sufficiently awake and it's clocking down prematurely, as soon as we're not touching it. Certainly adjusting the variables in: /sys/devices/system/cpu/cpu0/cpufreq it is possible to raise the performance and minimum frequency to make double buffering smooth. The challenge of this bug is to find a way in Mir/QtMir to keep the kernel more awake so it doesn't clock down when we need smooth animations and we're not touching the screen. ** Affects: mir Importance: Undecided Assignee: Daniel van Vugt (vanvugt) Status: New ** Affects: qtmir Importance: Undecided Status: New ** Affects: mir (Ubuntu) Importance: Undecided Status: New ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Tags: performance ** Also affects: qtmir Importance: Undecided Status: New ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Also affects: mir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488391 Title: Double buffering is only smooth while you're touching it Status in Mir: New Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Bug description: On some devices (mako at least) it's possible to force double buffering and it will often keep up: restart unity8 QML_NO_TOUCH_COMPRESSION=1 MIR_SERVER_NBUFFERS=2 Curiously however it only keeps up smoothly (eg. during a dash scroll) while you're touching the screen. If you lift off or fling the dash then it immediately stutters, quite badly. So the issue is not that the device can't keep up with double buffering. It seems more like we're not keeping the kernel sufficiently awake and it's clocking down prematurely, as soon as we're not touching it. Certainly adjusting the variables in: /sys/devices/system/cpu/cpu0/cpufreq it is possible to raise the performance and minimum frequency to make double buffering smooth. The challenge of this bug is to find a way in Mir/QtMir to keep the kernel more awake so it doesn't clock down when we need smooth animations and we're not touching the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1488391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488391] Re: Double buffering is only smooth while you're touching it
*** This bug is a duplicate of bug 1488386 *** https://bugs.launchpad.net/bugs/1488386 Could be a simple matter of increasing our concurrency. If that's not kept high enough then the delay between context switches likely becomes unacceptably high. And each frame requires at least 4 context switches (USC -> Unity8 -> app -> Unity8 -> USC). ** This bug has been marked a duplicate of bug 1488386 Double buffering is only smooth while you're touching it -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488391 Title: Double buffering is only smooth while you're touching it Status in Mir: New Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Bug description: On some devices (mako at least) it's possible to force double buffering and it will often keep up: restart unity8 QML_NO_TOUCH_COMPRESSION=1 MIR_SERVER_NBUFFERS=2 Curiously however it only keeps up smoothly (eg. during a dash scroll) while you're touching the screen. If you lift off or fling the dash then it immediately stutters, quite badly. So the issue is not that the device can't keep up with double buffering. It seems more like we're not keeping the kernel sufficiently awake and it's clocking down prematurely, as soon as we're not touching it. Certainly adjusting the variables in: /sys/devices/system/cpu/cpu0/cpufreq it is possible to raise the performance and minimum frequency to make double buffering smooth. The challenge of this bug is to find a way in Mir/QtMir to keep the kernel more awake so it doesn't clock down when we need smooth animations and we're not touching the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1488391/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1476201] Re: Dynamic double buffering fails to detect inertial dash scrolling as slow; and stutters instead of scaling up to triple buffers.
The above issue has been moved into bug 1488391. Ideally that would be resolved before we're sure this bug is. ** Tags added: performance -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1476201 Title: Dynamic double buffering fails to detect inertial dash scrolling as slow; and stutters instead of scaling up to triple buffers. Status in Mir: In Progress Status in QtMir: Opinion Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Opinion Bug description: Dynamic double buffering fails to detect inertial dash scrolling as slow; and stutters... [1437388267.960199] perf: Scopes: 37.69 FPS, render time 17.79ms, buffer lag 34.87ms (2 buffers) [1437388268.985012] perf: Scopes: 30.27 FPS, render time 25.22ms, buffer lag 40.29ms (2 buffers) [1437388269.993894] perf: Scopes: 31.74 FPS, render time 23.42ms, buffer lag 40.46ms (2 buffers) [1437388271.002470] perf: Scopes: 36.70 FPS, render time 19.13ms, buffer lag 35.59ms (2 buffers) [1437388272.021942] perf: Scopes: 44.16 FPS, render time 15.96ms, buffer lag 29.12ms (2 buffers) [1437388273.043734] perf: Scopes: 40.15 FPS, render time 17.85ms, buffer lag 31.90ms (2 buffers) whereas forcing triple buffers it runs more smoothly: [1437389981.872839] perf: Scopes: 57.71 FPS, render time 13.86ms, buffer lag 38.31ms (3 buffers) [1437389982.877556] perf: Scopes: 56.77 FPS, render time 15.72ms, buffer lag 37.31ms (3 buffers) [1437389983.887702] perf: Scopes: 57.42 FPS, render time 13.53ms, buffer lag 38.76ms (3 buffers) [1437389984.894372] perf: Scopes: 55.66 FPS, render time 16.02ms, buffer lag 38.12ms (3 buffers) [1437389985.912328] perf: Scopes: 60.96 FPS, render time 13.72ms, buffer lag 34.99ms (3 buffers) [1437389986.929857] perf: Scopes: 59.98 FPS, render time 14.49ms, buffer lag 35.67ms (3 buffers) You can see that unity8-dash is right on the edge here. Surprisingly the problem is not detectable if you keep your finger on the screen. Then the dash actually renders faster. The problem only seems to happen with inertial scrolling; when you fling the surface and lift your finger off. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1476201/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
several other machines are affected by this bug in our workplace. not sure if it's worth to mention but one machine NOT displaying this behavior is a 32b system, while the rest are 64b. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in hud package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/li
[Touch-packages] [Bug 1488386] Re: Double buffering is only smooth while you're touching it
** Also affects: qtmir Importance: Undecided Status: New ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488386 Title: Double buffering is only smooth while you're touching it Status in Mir: New Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Bug description: On some devices (mako at least) it's possible to force double buffering and it will often keep up: restart unity8 QML_NO_TOUCH_COMPRESSION=1 MIR_SERVER_NBUFFERS=2 Curiously however it only keeps up smoothly (eg. during a dash scroll) while you're touching the screen. If you lift off or fling the dash then it immediately stutters, quite badly. So the issue is not that the device can't keep up with double buffering. It seems more like we're not keeping the kernel sufficiently awake and it's clocking down prematurely, as soon as we're not touching it. Certainly adjusting the variables in: /sys/devices/system/cpu/cpu0/cpufreq it is possible to raise the performance and minimum frequency to make double buffering smooth. The challenge of this bug is to find a way in Mir/QtMir to keep the kernel more awake so it doesn't clock down when we need smooth animations and we're not touching the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1488386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487889] Re: After disconnnecting from car bluetooth, audio is still routed to bluetooth
I tried to reproduce this under similar conditions with a headset as I don't have access to any carkit at the moment but didn't had success. There are two possible reasons for this: * the device doesn't get disconnect any stays connected as device for bluez * the device disconnects properly but the upper stack (telepathy-ofono, telephony-service, pulseaudio) doesn't recognize this correctly I will try to get this reproduced next week with my own carkit at home. Tiago also mentioned there was a major rework of the code part in telepathy-ofono recently (ota6?) handling these things. He will attach a package without this rework included to let us verify if this is the reason for the behavior we see here or not. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1487889 Title: After disconnnecting from car bluetooth, audio is still routed to bluetooth Status in Canonical System Image: Confirmed Status in telephony-service package in Ubuntu: New Bug description: MX4 r96 This has been happening fro a few weeks Phone automatically connects to the car, you don't have to make or receive a call Leave the car and disconnect Place a call The audio starts out using the phone as expected, after a few seconds the audio switches to bluetooth You can manually change the audio in the UI This happens until you reboot To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487889/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488403] [NEW] Apps killed by lowmemorykiller leave a shadow window in the spread
*** This bug is a duplicate of bug 1474319 *** https://bugs.launchpad.net/bugs/1474319 Public bug reported: current build number: 96 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en Test Case: 1. Open several apps, enough to run out of memory 2. Switch between apps and monitor syslog until you notice OOM starts killing processes. Open more apps if necessary. 3. Once OM triggered, open the spread view to switch between apps Actual Result There is a shadow window for killed apps instead of a screenshot. When the shadow is selected, the screen is black until the app is reloaded. Expected Behaviour It shows a screenshot. ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - Apps killed by OOM leave a shadow window in the spread + Apps killed by lowmemorykiller leave a shadow window in the spread -- 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/1488403 Title: Apps killed by lowmemorykiller leave a shadow window in the spread Status in unity8 package in Ubuntu: New Bug description: current build number: 96 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en Test Case: 1. Open several apps, enough to run out of memory 2. Switch between apps and monitor syslog until you notice OOM starts killing processes. Open more apps if necessary. 3. Once OM triggered, open the spread view to switch between apps Actual Result There is a shadow window for killed apps instead of a screenshot. When the shadow is selected, the screen is black until the app is reloaded. Expected Behaviour It shows a screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1488403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488403] Re: Apps killed by lowmemorykiller leave a shadow window in the spread
*** This bug is a duplicate of bug 1474319 *** https://bugs.launchpad.net/bugs/1474319 ** This bug has been marked a duplicate of bug 1474319 app spread only shows shadows of apps, no content -- 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/1488403 Title: Apps killed by lowmemorykiller leave a shadow window in the spread Status in unity8 package in Ubuntu: New Bug description: current build number: 96 device name: arale channel: ubuntu-touch/rc-proposed/meizu.en Test Case: 1. Open several apps, enough to run out of memory 2. Switch between apps and monitor syslog until you notice OOM starts killing processes. Open more apps if necessary. 3. Once OM triggered, open the spread view to switch between apps Actual Result There is a shadow window for killed apps instead of a screenshot. When the shadow is selected, the screen is black until the app is reloaded. Expected Behaviour It shows a screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1488403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378345] Re: [address-book-app] Should open email app from contacts
** No longer affects: dekko -- 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/1378345 Title: [address-book-app] Should open email app from contacts Status in address-book-app: Fix Released Status in Canonical System Image: Fix Released Status in Ubuntu UX: Fix Released Status in unity-webapps-qml: New Status in address-book-app package in Ubuntu: Fix Released Status in address-book-app source package in Vivid: Confirmed Bug description: Steps: * add a contact with an email * open the contact Expected: * I can tap on the email address to open an email app composing an email to that contact (via a mailto: URL probably) Current: * email is not displayed at all ---UX comment--- The best solution for now would be to invoke the content hub and give user the option to select an app to send an email. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1378345/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1480952] Re: Enable journal-remote
** Changed in: systemd (Debian) Status: Unknown => 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/1480952 Title: Enable journal-remote Status in systemd package in Ubuntu: Triaged Status in systemd package in Debian: New Bug description: Right now there's nothing like systemd-journal-remote and systemd- journal-upload available in Ubuntu's repo. Would be great to have this packaged and installable in one command (or better yet - by default) to get modern remote logging to/from ubuntu as quickly and pain-free for users as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1480952/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487839] Re: Crash when closing window
@Marius: I can not reproduce this issue using that same image, do you have any custom scope or something special you did to your phone you think could be causing this crash? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1487839 Title: Crash when closing window Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Every time I close a window by sliding it up, Ubuntu Touch crashes and restarts. Device : BQ Aquaris E5 HD OS : Ubuntu 15.04 - armhf (20150713-202300) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1487839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488413] [NEW] connected BT mouse should unblank screen (windowed mode)
Public bug reported: when switching into windowed mode && a BT mouse is connected && screen is blanked (from time out or pwr key press) the BT mouse motion should unblank the screen this may effect multiple projects so sort of shotgunning the effected project list ** Affects: mir Importance: Undecided Status: New ** Affects: qtmir (Ubuntu) Importance: Undecided Status: Opinion ** Affects: unity-system-compositor (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: pd ** Also affects: unity-system-compositor (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Changed in: qtmir (Ubuntu) Status: New => Opinion ** Also affects: mir Importance: Undecided Status: New ** Description changed: when switching into windowed mode && a BT mouse is connected && screen is blanked (from time out or pwr key press) the BT mouse motion should unblank the screen + + this may effect multiple projects so sort of shotgunning the effected + project list ** Tags added: pd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1488413 Title: connected BT mouse should unblank screen (windowed mode) Status in Mir: New Status in qtmir package in Ubuntu: Opinion Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: when switching into windowed mode && a BT mouse is connected && screen is blanked (from time out or pwr key press) the BT mouse motion should unblank the screen this may effect multiple projects so sort of shotgunning the effected project list To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1488413/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488417] [NEW] nexus4 window mode mouse motion bounded incorrectly
Public bug reported: when connecting a monitor to the Nexus4 during windowed mode, the device is put into landscape mode. the mouse motion appears to not have followed the orientation and is bounded by roughly portrait width instead of landscape width ** Affects: mir (Ubuntu) Importance: Undecided Status: New ** Affects: qtmir (Ubuntu) Importance: Undecided Status: Opinion ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: pd ** Also affects: mir (Ubuntu) Importance: Undecided Status: New ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags added: pd ** Changed in: qtmir (Ubuntu) Status: New => Opinion -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488417 Title: nexus4 window mode mouse motion bounded incorrectly Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: Opinion Status in unity8 package in Ubuntu: New Bug description: when connecting a monitor to the Nexus4 during windowed mode, the device is put into landscape mode. the mouse motion appears to not have followed the orientation and is bounded by roughly portrait width instead of landscape width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488386] Re: Double buffering is only smooth while you're touching it
Further evidence: mirping gets better results while you're touching the screen: $ mirping /var/run/mir_socket Connected to server: /var/run/mir_socket --- Not touching the screen --- Round-trip time: 0.854571 milliseconds Round-trip time: 1.373416 milliseconds Round-trip time: 1.556539 milliseconds Round-trip time: 1.617580 milliseconds Round-trip time: 1.434458 milliseconds Round-trip time: 1.556539 milliseconds Round-trip time: 1.342896 milliseconds Round-trip time: 1.373417 milliseconds Round-trip time: 1.403937 milliseconds Round-trip time: 1.464978 milliseconds Round-trip time: 1.526019 milliseconds --- Now touching the screen a lot --- Round-trip time: 0.457805 milliseconds Round-trip time: 0.427285 milliseconds Round-trip time: 0.579887 milliseconds Round-trip time: 0.427285 milliseconds Round-trip time: 0.579887 milliseconds Round-trip time: 0.518847 milliseconds Round-trip time: 0.457805 milliseconds Round-trip time: 0.457805 milliseconds Round-trip time: 0.518846 milliseconds -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488386 Title: Double buffering is only smooth while you're touching it Status in Mir: New Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Bug description: On some devices (mako at least) it's possible to force double buffering and it will often keep up: restart unity8 QML_NO_TOUCH_COMPRESSION=1 MIR_SERVER_NBUFFERS=2 Curiously however it only keeps up smoothly (eg. during a dash scroll) while you're touching the screen. If you lift off or fling the dash then it immediately stutters, quite badly. So the issue is not that the device can't keep up with double buffering. It seems more like we're not keeping the kernel sufficiently awake and it's clocking down prematurely, as soon as we're not touching it. Certainly adjusting the variables in: /sys/devices/system/cpu/cpu0/cpufreq it is possible to raise the performance and minimum frequency to make double buffering smooth. The challenge of this bug is to find a way in Mir/QtMir to keep the kernel more awake so it doesn't clock down when we need smooth animations and we're not touching the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1488386/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487839] Re: Crash when closing window
@Daniel: the channel for that image is ubuntu-touch/stable/bq-aquaris.en -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1487839 Title: Crash when closing window Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Every time I close a window by sliding it up, Ubuntu Touch crashes and restarts. Device : BQ Aquaris E5 HD OS : Ubuntu 15.04 - armhf (20150713-202300) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1487839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488417] Re: nexus4 window mode mouse motion bounded incorrectly
Might be bug 1313610, or closely related. ** Tags added: cursor -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488417 Title: nexus4 window mode mouse motion bounded incorrectly Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: Opinion Status in unity8 package in Ubuntu: New Bug description: when connecting a monitor to the Nexus4 during windowed mode, the device is put into landscape mode. the mouse motion appears to not have followed the orientation and is bounded by roughly portrait width instead of landscape width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488424] [NEW] Sometimes after a window is maximized it is not possible to unmaximize it
Public bug reported: Steps to reproduce: 1. Open any app in windowed mode 2. Click the maximize button in its window title bar 3. Click the unmaximize button in its window title bar which is now merged with the top unity panel Sometimes after step 3 the window is still maximized. ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: pd -- 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/1488424 Title: Sometimes after a window is maximized it is not possible to unmaximize it Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: 1. Open any app in windowed mode 2. Click the maximize button in its window title bar 3. Click the unmaximize button in its window title bar which is now merged with the top unity panel Sometimes after step 3 the window is still maximized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1488424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438465] Re: It's possible to put a window under the top panel
** Changed in: unity8 (Ubuntu) Importance: Medium => 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/1438465 Title: It's possible to put a window under the top panel Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: so many times,when i drag the window to the top, the max-min-button will be overlaied by panel,so i can not drag this window back and i can not see these buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1438465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
touching this bug as on our unity8 windowed mode i see this as 1. go to system settings 2. select connect device 3. select mouse detected 4. select connect (put user back to bt first view) expected: to be connected result: have to go back to the mouse bt page and hit "connect" again. this is really obvious, b/c the mouse presence is being used for converting into window mode ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: qtmir (Ubuntu) Status: New => Opinion ** Tags added: pd -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in bluez package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Opinion Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481136] Re: Bluetooth mouse fails to reconnect after suspend + resume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1481136 Title: Bluetooth mouse fails to reconnect after suspend + resume Status in bluez package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Opinion Bug description: I can connect the bluetooth mouse (Logitech M557) using the GUI and the device works properly. However, after suspend and resume the mouse fails to reconnect. It does "attempt" to reconnect, in that I see the padlock flashes momentarily onto the bluetooth icon on the toolbar applet. Similarly, if the Bluetooth Settings dialog is open the devices flashes momentarily bold as if connected. Both effects happen whenever the mouse is used (movement or mouse click) but the device does not connect. I have a workaround, which is to remove the device and pair it using the command line as follows: sudo bluez-test-device remove 00:1F:20:EF:B1:00 sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 remove sudo bluez-simple-agent hci0 00:1F:20:EF:B1:00 sudo bluez-test-device trusted 00:1F:20:EF:B1:00 yes sudo bluez-test-input connect 00:1F:20:EF:B1:00 Once paired manually in this manner the devices appears in the Bluetooth Settings as normal an successfully reconnects when resuming. I'm submitted a new bug as this is similar but not the same as other bugs reported. In particular the workarounds presented in other bugs do not work for me and the workaround I'm using was not suggested in other cases. Thanks. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: bluez 4.101-0ubuntu25 ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 ApportVersion: 2.17.2-0ubuntu1.1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 4 09:53:18 2015 InstallationDate: Installed on 2014-01-23 (557 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: rfcomm bnep btusb bluetooth MachineType: TOSHIBA KIRA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic.efi.signed root=UUID=a0fdb0ee-bbeb-4872-8e79-1a785c304e91 ro libata.force=noncq vesafb.invalid=1 splash quiet nopat vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/15/2013 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.30 dmi.board.asset.tag: 00 dmi.board.name: KIRA dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 00 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.30:bd02/15/2013:svnTOSHIBA:pnKIRA:pvrPSU7FA-00T00K:rvnTOSHIBA:rnKIRA:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: KIRA dmi.product.version: PSU7FA-00T00K dmi.sys.vendor: TOSHIBA hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: B4:B6:76:C4:A2:88 ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN RX bytes:587136 acl:36542 sco:0 events:271 errors:0 TX bytes:2913 acl:109 sco:0 commands:81 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2015-08-01T14:24:23.630880 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1481136/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488425] [NEW] [MIR] ubuntu-download-manager
Public bug reported: webbrowser-app (in main) currently has a non-explicit runtime dependency on ubuntu-download-manager, which is in universe. This has been working until now because the desktop version of the app doesn’t make use of the QML API for the download manager, only the version for touch devices does (and ubuntu-download-manager is part of the touch seed). With convergence in mind, the desktop version needs to start using that QML API, so the runtime dependency needs to be made explicit. Hence the need for ubuntu-download-manager to be included in main. It is likely that other applications will have the same kind of requirements in the near future too. ubuntu-download-manager is actively being developed and maintained, upstream tracks their bugs at https://bugs.launchpad.net/ubuntu/+source /ubuntu-download-manager/. All its build and runtime dependencies are already in main. ** Affects: ubuntu-download-manager (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1488425 Title: [MIR] ubuntu-download-manager Status in ubuntu-download-manager package in Ubuntu: New Bug description: webbrowser-app (in main) currently has a non-explicit runtime dependency on ubuntu-download-manager, which is in universe. This has been working until now because the desktop version of the app doesn’t make use of the QML API for the download manager, only the version for touch devices does (and ubuntu-download-manager is part of the touch seed). With convergence in mind, the desktop version needs to start using that QML API, so the runtime dependency needs to be made explicit. Hence the need for ubuntu-download-manager to be included in main. It is likely that other applications will have the same kind of requirements in the near future too. ubuntu-download-manager is actively being developed and maintained, upstream tracks their bugs at https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/. All its build and runtime dependencies are already in main. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1488425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488424] Re: Sometimes after a window is maximized it is not possible to unmaximize it
** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Tags added: pd -- 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/1488424 Title: Sometimes after a window is maximized it is not possible to unmaximize it Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Steps to reproduce: 1. Open any app in windowed mode 2. Click the maximize button in its window title bar 3. Click the unmaximize button in its window title bar which is now merged with the top unity panel Sometimes after step 3 the window is still maximized. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1488424/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1380084] Re: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0
*** This bug is a duplicate of bug 201786 *** https://bugs.launchpad.net/bugs/201786 ** This bug has been marked a duplicate of bug 201786 ssh Agent admitted failure to sign using the key on big endian machines -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1380084 Title: SSH client requires SSH_AUTH_SOCK=0 will not work without it, can't use key auth without SSH_AUTH_SOCK=0 Status in openssh package in Ubuntu: Confirmed Bug description: I expect that when using key based authentication I do $ssh user@0.0.0.0 I expect to be asked for the key password. Instead I get Agent admitted failure to sign using the key. Permission denied (publickey). Using SSH_AUTH_SOCK=0 solves the problem allowing me to be asked for the key password. What should happen is that I should not have to specify SSH_AUTH_SOCK=0 on the CLI, I should only have to type $ user@0.0.0.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: openssh-client 1:6.6p1-2ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7 Uname: Linux 3.13.0-37-generic i686 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 CurrentDesktop: Unity Date: Sat Oct 11 07:19:08 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2) ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: ssh-askpass N/A libpam-sshN/A keychain N/A ssh-askpass-gnome 1:6.6p1-2ubuntu2 SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014 SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1380084/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 201786] Re: ssh Agent admitted failure to sign using the key on big endian machines
** Tags added: 14.04 ** Tags added: 14.10 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/201786 Title: ssh Agent admitted failure to sign using the key on big endian machines Status in seahorse: Fix Released Status in gnome-keyring package in Ubuntu: Triaged Status in openssh package in Ubuntu: Confirmed Bug description: on hardy (preserved home folder from feisty) i get the following when i try to ssh Agent admitted failure to sign using the key. Permission denied (publickey). or with verbose on sam@titania:~$ ssh -v oberon OpenSSH_4.7p1 Debian-4ubuntu1, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /home/sam/.ssh/config debug1: Applying options for oberon debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to ## [##] port ##. debug1: Connection established. debug1: identity file /home/sam/.ssh/identity type -1 debug1: identity file /home/sam/.ssh/id_rsa type 1 debug1: identity file /home/sam/.ssh/id_dsa type -1 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.6p1 Debian-5ubuntu0.1 debug1: match: OpenSSH_4.6p1 Debian-5ubuntu0.1 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-4ubuntu1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: using hostkeyalias: oberon debug1: Host 'oberon' is known and matches the RSA host key. debug1: Found key in /home/sam/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey debug1: Next authentication method: publickey debug1: Offering public key: /home/sam/.ssh/id_rsa debug1: Server accepts key: pkalg ssh-rsa blen 277 Agent admitted failure to sign using the key. debug1: Trying private key: /home/sam/.ssh/identity debug1: Trying private key: /home/sam/.ssh/id_dsa debug1: No more authentication methods to try. Permission denied (publickey). I tried generating a new key. this worked for a few logons, but then i get back to this error. I think it is to do with the local key agent. i found that SSH_AUTH_SOCK=0 ssh oberon works fine. To manage notifications about this bug go to: https://bugs.launchpad.net/seahorse/+bug/201786/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1438465] Re: It's possible to put a window under the top panel
** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Tags added: pd -- 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/1438465 Title: It's possible to put a window under the top panel Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: Triaged Bug description: so many times,when i drag the window to the top, the max-min-button will be overlaied by panel,so i can not drag this window back and i can not see these buttons To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1438465/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488427] [NEW] nexus4 windowed mode greeter password text box hidden by osk
Public bug reported: on nexus4 windowed mode greeter password text box hidden by osk mainly annoying as if you mistype, you cannot see it ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: pd ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Tags added: pd -- 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/1488427 Title: nexus4 windowed mode greeter password text box hidden by osk Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: on nexus4 windowed mode greeter password text box hidden by osk mainly annoying as if you mistype, you cannot see it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1488427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487754] Re: Local storage not working properly
Can you share your code (the one that uses a WebView? On which device are you testing this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1487754 Title: Local storage not working properly Status in Oxide: New Status in webbrowser-app package in Ubuntu: Invalid Bug description: Hi, I noticed some days ago now, that local storage (and may be other web storage) not persist data randomly. It's pretty easy to show the issue with a website which use local storage. To reproduce this issue : - With a phone or emulator, go to http://todomvc.com/examples/angularjs/ - Create a simple todo list - Close the browser - Open the browser - And go back to http://todomvc.com/examples/angularjs/ - If data are correctly restored, reproduce all the step and you will see, sometimes, it not restore the last local storage. So the issue is present in Browser. I also noticed, it happens in webview, for example in my application : https://uappexplorer.com/app/yaoswa.inglebard So the problem exist in Webview too. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1487754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487837] Re: Live webcam feeds don't work on the browser
*** This bug is a duplicate of bug 1408760 *** https://bugs.launchpad.net/bugs/1408760 There’s unfortunately no way to make this bug a child of the other one, it’s either a duplicate or nothing. I’ll tentatively mark this one a duplicate of the other one, and I’ll add the information in this bug report to the other one to make sure we review this use case when fixing streaming. ** This bug has been marked a duplicate of bug 1408760 Streaming video does not work -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1487837 Title: Live webcam feeds don't work on the browser Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Visiting live webcam feeds like this one [1] don't work on the phone. They just display an updated thumbnail on refresh. It works on every other device I've tried (desktop, iOS Safari). 1: http://zoo.sandiegozoo.org/cams/koala-cam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1487837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488431] [NEW] Clients fail to create surfaces when using Mir server in compositor mode
Public bug reported: When trying to run the Unity 8 session on an up to date wily laptop (using the unity8-desktop-session-mir package) I'm only seeing a black screen. Digging down, it appears when running a Mir server in compositor mode the Mir clients are unable to create surfaces. To reproduce: 1. Switch to VT1 2. Run a Mir server in compositor mode: $ sudo mir_demo_server --window-manager system-compositor --arw-file 3. Switch to VT2 4. Run a Mir client: $ MIR_SOCKET=/tmp/mir_socket mir_demo_client_basic 5. Switch to VT1 6. Switch to VT2 Expected result: The client runs successfully Observed result: The client hits an assertion that the surface is not valid. Using a modified client to see the error message (see lp:~robert- ancell/mir/basic-client-print-surface-error) it gives: Error processing request: Failed to place surface in requested output Internal error details: /build/mir-QIEYOz/mir-0.15.0+15.10.20150818/src/server/shell/graphics_display_layout.cpp(91): Throw in function virtual void mir::shell::GraphicsDisplayLayout::place_in_output(mir::graphics::DisplayConfigurationOutputId, mir::geometry::Rectangle&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to place surface in requested output The above steps work file if the --window-manager system-compositor flag is removed. This used to work before and appears to work on some up to date wily systems. ** Affects: mir (Ubuntu) Importance: Critical Status: Confirmed ** Changed in: mir (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488431 Title: Clients fail to create surfaces when using Mir server in compositor mode Status in mir package in Ubuntu: Confirmed Bug description: When trying to run the Unity 8 session on an up to date wily laptop (using the unity8-desktop-session-mir package) I'm only seeing a black screen. Digging down, it appears when running a Mir server in compositor mode the Mir clients are unable to create surfaces. To reproduce: 1. Switch to VT1 2. Run a Mir server in compositor mode: $ sudo mir_demo_server --window-manager system-compositor --arw-file 3. Switch to VT2 4. Run a Mir client: $ MIR_SOCKET=/tmp/mir_socket mir_demo_client_basic 5. Switch to VT1 6. Switch to VT2 Expected result: The client runs successfully Observed result: The client hits an assertion that the surface is not valid. Using a modified client to see the error message (see lp:~robert- ancell/mir/basic-client-print-surface-error) it gives: Error processing request: Failed to place surface in requested output Internal error details: /build/mir-QIEYOz/mir-0.15.0+15.10.20150818/src/server/shell/graphics_display_layout.cpp(91): Throw in function virtual void mir::shell::GraphicsDisplayLayout::place_in_output(mir::graphics::DisplayConfigurationOutputId, mir::geometry::Rectangle&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to place surface in requested output The above steps work file if the --window-manager system-compositor flag is removed. This used to work before and appears to work on some up to date wily systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488431] Re: Clients fail to create surfaces when using Mir server in compositor mode
I downgraded mesa from 10.6.3 to 10.5.9 in case that had caused it but it made no difference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488431 Title: Clients fail to create surfaces when using Mir server in compositor mode Status in mir package in Ubuntu: Confirmed Bug description: When trying to run the Unity 8 session on an up to date wily laptop (using the unity8-desktop-session-mir package) I'm only seeing a black screen. Digging down, it appears when running a Mir server in compositor mode the Mir clients are unable to create surfaces. To reproduce: 1. Switch to VT1 2. Run a Mir server in compositor mode: $ sudo mir_demo_server --window-manager system-compositor --arw-file 3. Switch to VT2 4. Run a Mir client: $ MIR_SOCKET=/tmp/mir_socket mir_demo_client_basic 5. Switch to VT1 6. Switch to VT2 Expected result: The client runs successfully Observed result: The client hits an assertion that the surface is not valid. Using a modified client to see the error message (see lp:~robert- ancell/mir/basic-client-print-surface-error) it gives: Error processing request: Failed to place surface in requested output Internal error details: /build/mir-QIEYOz/mir-0.15.0+15.10.20150818/src/server/shell/graphics_display_layout.cpp(91): Throw in function virtual void mir::shell::GraphicsDisplayLayout::place_in_output(mir::graphics::DisplayConfigurationOutputId, mir::geometry::Rectangle&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to place surface in requested output The above steps work file if the --window-manager system-compositor flag is removed. This used to work before and appears to work on some up to date wily systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487839] Re: Crash when closing window
I ran the following commands from the phone's terminal sudo mount -o remount,rw / sudo apt-get update sudo apt-get upgrade I had an error for the powerd package, it wouldn't install. Yesterday I reset the phone using the recovery boot and I'm having the same problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1487839 Title: Crash when closing window Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Every time I close a window by sliding it up, Ubuntu Touch crashes and restarts. Device : BQ Aquaris E5 HD OS : Ubuntu 15.04 - armhf (20150713-202300) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1487839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1408760] Re: Streaming video does not work
>From a duplicate bug report: http://zoo.sandiegozoo.org/cams/koala-cam doesn’t work on devices either, it’s very likely that it’s the same issue. ** No longer affects: webbrowser-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1408760 Title: Streaming video does not work Status in webbrowser-app package in Ubuntu: Confirmed Status in webbrowser-app package in Ubuntu RTM: Confirmed Bug description: Try going to a https://twitch.tv and open any live stream. Hopefully you should be redirected to https://twitch.tv/:streamer-slug/mobile, where there's a video being streamed over HLS. Clicking on the play button makes the video look like it's initializing for a second, and then nothing happens. Just in case there was something funky with that particular implementation, I also tried it at https://hitbox.tv, but had the same thing happen. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1408760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487839] Re: Crash when closing window
By doing that you basically put yourself in the "we can't help you territory". don't run apt-get on the phone unless you *really* know what you're doing. Which command did you use to reflash your phone? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1487839 Title: Crash when closing window Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Every time I close a window by sliding it up, Ubuntu Touch crashes and restarts. Device : BQ Aquaris E5 HD OS : Ubuntu 15.04 - armhf (20150713-202300) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1487839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488431] Re: Clients fail to create surfaces when using Mir server in compositor mode
confirmed on an inspiron 3138 config on wily ** Changed in: mir (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488431 Title: Clients fail to create surfaces when using Mir server in compositor mode Status in mir package in Ubuntu: Confirmed Bug description: When trying to run the Unity 8 session on an up to date wily laptop (using the unity8-desktop-session-mir package) I'm only seeing a black screen. Digging down, it appears when running a Mir server in compositor mode the Mir clients are unable to create surfaces. To reproduce: 1. Switch to VT1 2. Run a Mir server in compositor mode: $ sudo mir_demo_server --window-manager system-compositor --arw-file 3. Switch to VT2 4. Run a Mir client: $ MIR_SOCKET=/tmp/mir_socket mir_demo_client_basic 5. Switch to VT1 6. Switch to VT2 Expected result: The client runs successfully Observed result: The client hits an assertion that the surface is not valid. Using a modified client to see the error message (see lp:~robert- ancell/mir/basic-client-print-surface-error) it gives: Error processing request: Failed to place surface in requested output Internal error details: /build/mir-QIEYOz/mir-0.15.0+15.10.20150818/src/server/shell/graphics_display_layout.cpp(91): Throw in function virtual void mir::shell::GraphicsDisplayLayout::place_in_output(mir::graphics::DisplayConfigurationOutputId, mir::geometry::Rectangle&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to place surface in requested output The above steps work file if the --window-manager system-compositor flag is removed. This used to work before and appears to work on some up to date wily systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488425] Re: [MIR] ubuntu-download-manager
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-download-manager (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1488425 Title: [MIR] ubuntu-download-manager Status in ubuntu-download-manager package in Ubuntu: Confirmed Bug description: webbrowser-app (in main) currently has a non-explicit runtime dependency on ubuntu-download-manager, which is in universe. This has been working until now because the desktop version of the app doesn’t make use of the QML API for the download manager, only the version for touch devices does (and ubuntu-download-manager is part of the touch seed). With convergence in mind, the desktop version needs to start using that QML API, so the runtime dependency needs to be made explicit. Hence the need for ubuntu-download-manager to be included in main. It is likely that other applications will have the same kind of requirements in the near future too. ubuntu-download-manager is actively being developed and maintained, upstream tracks their bugs at https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/. All its build and runtime dependencies are already in main. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1488425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488425] Re: [MIR] ubuntu-download-manager
** Changed in: ubuntu-download-manager (Ubuntu) Importance: Undecided => Medium ** Changed in: ubuntu-download-manager (Ubuntu) Assignee: (unassigned) => Manuel de la Peña (mandel) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1488425 Title: [MIR] ubuntu-download-manager Status in ubuntu-download-manager package in Ubuntu: Confirmed Bug description: webbrowser-app (in main) currently has a non-explicit runtime dependency on ubuntu-download-manager, which is in universe. This has been working until now because the desktop version of the app doesn’t make use of the QML API for the download manager, only the version for touch devices does (and ubuntu-download-manager is part of the touch seed). With convergence in mind, the desktop version needs to start using that QML API, so the runtime dependency needs to be made explicit. Hence the need for ubuntu-download-manager to be included in main. It is likely that other applications will have the same kind of requirements in the near future too. ubuntu-download-manager is actively being developed and maintained, upstream tracks their bugs at https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/. All its build and runtime dependencies are already in main. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-download-manager/+bug/1488425/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488431] Re: Clients fail to create surfaces when using Mir server in compositor mode
Downgrading mir from 0.15.0+15.10.20150818-0ubuntu1 to 0.14.0+15.10.20150723.1-0ubuntu2~ppa2 made no difference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488431 Title: Clients fail to create surfaces when using Mir server in compositor mode Status in mir package in Ubuntu: Confirmed Bug description: When trying to run the Unity 8 session on an up to date wily laptop (using the unity8-desktop-session-mir package) I'm only seeing a black screen. Digging down, it appears when running a Mir server in compositor mode the Mir clients are unable to create surfaces. To reproduce: 1. Switch to VT1 2. Run a Mir server in compositor mode: $ sudo mir_demo_server --window-manager system-compositor --arw-file 3. Switch to VT2 4. Run a Mir client: $ MIR_SOCKET=/tmp/mir_socket mir_demo_client_basic 5. Switch to VT1 6. Switch to VT2 Expected result: The client runs successfully Observed result: The client hits an assertion that the surface is not valid. Using a modified client to see the error message (see lp:~robert- ancell/mir/basic-client-print-surface-error) it gives: Error processing request: Failed to place surface in requested output Internal error details: /build/mir-QIEYOz/mir-0.15.0+15.10.20150818/src/server/shell/graphics_display_layout.cpp(91): Throw in function virtual void mir::shell::GraphicsDisplayLayout::place_in_output(mir::graphics::DisplayConfigurationOutputId, mir::geometry::Rectangle&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to place surface in requested output The above steps work file if the --window-manager system-compositor flag is removed. This used to work before and appears to work on some up to date wily systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488417] Re: nexus4 window mode mouse motion bounded incorrectly
*** This bug is a duplicate of bug 1313610 *** https://bugs.launchpad.net/bugs/1313610 Yeah pretty sure it's the same as bug 1313610. We've never updated our cursor bounds correctly on rotation... ** This bug has been marked a duplicate of bug 1313610 Cursor gets stranded and can't move between non-contiguous monitors (especially after rotation) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488417 Title: nexus4 window mode mouse motion bounded incorrectly Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: Opinion Status in unity8 package in Ubuntu: New Bug description: when connecting a monitor to the Nexus4 during windowed mode, the device is put into landscape mode. the mouse motion appears to not have followed the orientation and is bounded by roughly portrait width instead of landscape width To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488417/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390625] Re: mouse cursor gets corrupted
Same here on both Travelmate B115-M and old MacBook 2007 (GMA 950). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1390625 Title: mouse cursor gets corrupted Status in elementary OS: Fix Committed Status in Mesa: New Status in Unity: Invalid Status in unity package in Ubuntu: Invalid Status in xorg-lts-utopic package in Ubuntu: Confirmed Bug description: In Ubuntu 14.10, the mouse cursor graphic gets corrupted under certain occasions. It then looks flipped, sheared or shows fragments of a previous cursor. * when switching the cursor them forth and back in Gnome Tweak Tool * when drag&dropping a document icon Maybe related, the cursor does not always show the correct image scale on a high-dpi display (this was working right in 14.04). For example after login, or when hovering specific areas, or on mouse down to start a drag&drop, the cursor appears 1/4 the expected size. Attached is a photo of a corrupted cursor (whereas a screenshot with Gimp showed the uncorrupted cursor). ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 BootLog: * Setting up X socket directories... [400G [394G[ OK ] CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Fri Nov 7 22:12:52 2014 DistUpgraded: 2014-11-04 18:35:56,188 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu EcryptfsInUse: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3978] InstallationDate: Installed on 2014-02-02 (278 days ago) InstallationMedia: Ubuntu-GNOME 14.04 "Trusty Tahr" - Alpha amd64 (20140201) MachineType: LENOVO 20266 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-24-generic.efi.signed root=UUID=4bfb3686-b9f7-487d-81f6-eceb41097ad9 ro quiet splash acpi_backlight=vendor SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2014-11-04 (3 days ago) dmi.bios.date: 10/31/2013 dmi.bios.vendor: LENOVO dmi.bios.version: 76CN31WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Yoga2 dmi.board.vendor: LENOVO dmi.board.version: 31900058STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga 2 Pro dmi.modalias: dmi:bvnLENOVO:bvr76CN31WW:bd10/31/2013:svnLENOVO:pn20266:pvrLenovoYoga2Pro:rvnLENOVO:rnYoga2:rvr31900058STD:cvnLENOVO:ct10:cvrLenovoYoga2Pro: dmi.product.name: 20266 dmi.product.version: Lenovo Yoga 2 Pro dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Fri Nov 7 14:54:59 2014 xserver.configfile: /etc/X11/xorg.conf xserver.errors: [dix] ELAN Touchscreen: unable to find touch point 1 xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 16970 vendor SDC xserver.version: 2:1.16.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/elementaryos/+bug/1390625/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1435040] Re: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth
I can confirm this issue in a Ford Fiesta. After the device detection and introducing the pin for connection nothing happens, the connection is not established. Can someone please update the debugging instructions on: (a) best way to use the command line in the phone (installing terminal? developer mode on?), it might be useful for some users (b) how to revert the verbose logging and leave the phone as it was before? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1435040 Title: Ubuntu Phone (BQ E4.5) does not connect to car-bluetooth Status in Canonical System Image: Confirmed Status in bluez package in Ubuntu: Confirmed Status in ubuntu-system-settings package in Ubuntu: Incomplete Bug description: With my FORD Focus Car, pairing does not work. The bluetooth system in the car searches for devices and shows "Aquaris E4.5 Ubuntu Edition" and then prompts me to connect with a 4-digit pin code, but the Ubuntu phone doesn't react at all and after a while the car system says that it failed to connect. image: 20150310-3201c0a KRILIN01A-S15A_BQ_L100EN_2020_150312 OS Build 20 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1435040/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488431] Re: Clients fail to create surfaces when using Mir server in compositor mode
This exception is thrown by the system-compositor window manager when the surface spec to create a surface does not use an output id that matches one of the available output ids and the requested size does not match. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488431 Title: Clients fail to create surfaces when using Mir server in compositor mode Status in mir package in Ubuntu: Confirmed Bug description: When trying to run the Unity 8 session on an up to date wily laptop (using the unity8-desktop-session-mir package) I'm only seeing a black screen. Digging down, it appears when running a Mir server in compositor mode the Mir clients are unable to create surfaces. To reproduce: 1. Switch to VT1 2. Run a Mir server in compositor mode: $ sudo mir_demo_server --window-manager system-compositor --arw-file 3. Switch to VT2 4. Run a Mir client: $ MIR_SOCKET=/tmp/mir_socket mir_demo_client_basic 5. Switch to VT1 6. Switch to VT2 Expected result: The client runs successfully Observed result: The client hits an assertion that the surface is not valid. Using a modified client to see the error message (see lp:~robert- ancell/mir/basic-client-print-surface-error) it gives: Error processing request: Failed to place surface in requested output Internal error details: /build/mir-QIEYOz/mir-0.15.0+15.10.20150818/src/server/shell/graphics_display_layout.cpp(91): Throw in function virtual void mir::shell::GraphicsDisplayLayout::place_in_output(mir::graphics::DisplayConfigurationOutputId, mir::geometry::Rectangle&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to place surface in requested output The above steps work file if the --window-manager system-compositor flag is removed. This used to work before and appears to work on some up to date wily systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1464053] Re: ubuntu-bug is broken (only) within Mate, because of gvfs-open.
I just tested this again in my Ubuntu Mate system (Wily, fully updated as of today). Running the command "gvfs-open http://www.bbc.co.uk"; still results in the same problem - namely a new firefox window that is open at the homepage, not the URL required. The gvfs-open command does what it should when the running-desktop is KDE or Unity - but not when it is Mate. How else can I help debug this? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1464053 Title: ubuntu-bug is broken (only) within Mate, because of gvfs-open. Status in ubuntu-mate: Incomplete Status in apport package in Ubuntu: Invalid Status in gvfs package in Ubuntu: New Bug description: The ubuntu bug reporting system is rather badly broken, because when I run ubuntu-bug/apport-bug, it gathers data, then opens a new blank firefox window, but does not connect to launchpad! The root cause is this one: https://bugs.launchpad.net/ubuntu/+source/exo/+bug/1427144 which basically means that apport needs to invoke firefox with a different set of options. This should be trivial to fix, but I think it's rather important, especially given how hard it is to get a direct report into Launchpad, and all the redirects that emphasise using the ubuntu-bug tool: https://help.ubuntu.com/community/ReportingBugs (I'm reporting this from Ubuntu Wily, though I think I recall seeing it in Vivid) Apport version is: 2.17.3-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1464053/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1316913] Re: wrong keybord layout at system start
** Also affects: lightdm Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1316913 Title: wrong keybord layout at system start Status in Light Display Manager: New Status in lightdm package in Ubuntu: Confirmed Bug description: my system is set to german by default (De). When starting thunderbird and writing a new mail my keyboard is in qwerty mode. i must click on the De icon in the task bar to set it to qwertz mode. When updates need to be veriyfied with password i get wrong password - clicking the de icon in task bar sets it to german. thanks! ubuntu 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/1316913/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467740] Re: Lots of thumbnail requests with invalid size
I don't understand why you guys consider an undefined size to be invalid, the documentation of Qt is quite clear in that it is a valid size sourceSize can be cleared to the natural size of the image by setting sourceSize to undefined. So yes I want the natural size of the image if i can't find out what's the aspect ratio of the image. Besides it's weird because you complain for undefined but for 0x0 you give me a thumbnail just fine. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1467740 Title: Lots of thumbnail requests with invalid size Status in thumbnailer package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When using scopes, the thumbnailer gets loads of requests with QSize(-1,-1) from the shell. For example, with a bunch of videos recorded, run up the video scope and go to "My Videos". The shell asks for a thumbnail at QSize(-1,-1) for the tiny thumbnail that appears to the left of each list entry. The problem with this is that the thumbnailer interprets this to mean "give me the largest size you can (limited to a 1920x1920 bounding box). That's very expensive, especially in terms of disk space, because that 1920 "thumbnail" ends up going into the cache, needlessly hogging space. We are about to add a qWarning message to the QML side that reports invalid QSize requests. For now, we are going to retain the old behavior, but this will turn into an error soon. The most effective way to use the thumbnailer is to simply ask for an image in the desired size, with neither width nor height of -1. The thumbnailer will efficiently produce a thumbnail for that. (We do lots of internal caching to avoid extracting or downloading a thumbnail unnecessarily.) The thumbnailer may deliver a thumbnail that is smaller than what was asked for (because it never up-scales) so, if asked for a thumbnail of size 256, it's guaranteed not to be larger, but might be smaller (if the original image is smaller than what was asked for). Could you please adjust the shell behavior to ask for specific, valid sizes only? Running a tail -f on ~/.cache/upstart/dbus.log allows you to see the requests as they are made. Each request shows the size that was asked for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1467740/+subscriptions -- Mailing list: https://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 1487837] Re: Live webcam feeds don't work on the browser
*** This bug is a duplicate of bug 1408760 *** https://bugs.launchpad.net/bugs/1408760 Thanks so much Oliver On Tue, Aug 25, 2015 at 10:11 AM, Olivier Tilloy < olivier.til...@canonical.com> wrote: > *** This bug is a duplicate of bug 1408760 *** > https://bugs.launchpad.net/bugs/1408760 > > There’s unfortunately no way to make this bug a child of the other one, > it’s either a duplicate or nothing. I’ll tentatively mark this one a > duplicate of the other one, and I’ll add the information in this bug > report to the other one to make sure we review this use case when fixing > streaming. > > ** This bug has been marked a duplicate of bug 1408760 >Streaming video does not work > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1487837 > > Title: > Live webcam feeds don't work on the browser > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1487837/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1487837 Title: Live webcam feeds don't work on the browser Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Visiting live webcam feeds like this one [1] don't work on the phone. They just display an updated thumbnail on refresh. It works on every other device I've tried (desktop, iOS Safari). 1: http://zoo.sandiegozoo.org/cams/koala-cam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1487837/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481673] Re: No mechanism for displaying internal downloads in transfer indicator
I confirmed this is still an issue, even with silo 24 installed ** Changed in: indicator-transfer (Ubuntu) Assignee: (unassigned) => Charles Kerr (charlesk) ** Also affects: canonical-devices-system-image Importance: Undecided Status: New ** Changed in: canonical-devices-system-image Milestone: None => ww40-2015 ** Changed in: indicator-transfer (Ubuntu) Importance: Undecided => High ** Changed in: indicator-transfer (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1481673 Title: No mechanism for displaying internal downloads in transfer indicator Status in Canonical System Image: New Status in indicator-transfer package in Ubuntu: Confirmed Status in ubuntu-download-manager package in Ubuntu: New Bug description: We're currently adding support to the webbrowser-app to allow it download files internally in addition to sending them to other applications, currently download manager has a metadata property titled "showInIndicator", however this doesn't appear to have any effect when the transfer is happening inside an application without content-hub involvement. This results in an inconsistent experience for the user, as some downloads from the browser show up in the indicator (those opened immediately with other apps) and some don't (those downloaded for later use). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488470] Re: Ctrl+W shortcut non functional on blank tab after closing a blank tab
** Changed in: webbrowser-app (Ubuntu) Assignee: (unassigned) => Ugo Riboni (uriboni) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1488470 Title: Ctrl+W shortcut non functional on blank tab after closing a blank tab Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Steps to reproduce (on a desktop): - launch the browser - press Ctrl+T twice in a row to open two new blank tabs - press Ctrl+W, this closes the second blank tab - press Ctrl+W again Expected result: this closes the first blank tab Current result: nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1488470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488470] Re: Ctrl+W shortcut non functional on blank tab after closing a blank tab
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: webbrowser-app (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1488470 Title: Ctrl+W shortcut non functional on blank tab after closing a blank tab Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Steps to reproduce (on a desktop): - launch the browser - press Ctrl+T twice in a row to open two new blank tabs - press Ctrl+W, this closes the second blank tab - press Ctrl+W again Expected result: this closes the first blank tab Current result: nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1488470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488470] [NEW] Ctrl+W shortcut non functional on blank tab after closing a blank tab
Public bug reported: Steps to reproduce (on a desktop): - launch the browser - press Ctrl+T twice in a row to open two new blank tabs - press Ctrl+W, this closes the second blank tab - press Ctrl+W again Expected result: this closes the first blank tab Current result: nothing happens ** Affects: webbrowser-app (Ubuntu) Importance: Medium Assignee: Ugo Riboni (uriboni) Status: Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1488470 Title: Ctrl+W shortcut non functional on blank tab after closing a blank tab Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Steps to reproduce (on a desktop): - launch the browser - press Ctrl+T twice in a row to open two new blank tabs - press Ctrl+W, this closes the second blank tab - press Ctrl+W again Expected result: this closes the first blank tab Current result: nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1488470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1474319] Re: app spread only shows shadows of apps, no content
** Also affects: canonical-devices-system-image Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1474319 Title: app spread only shows shadows of apps, no content Status in Canonical System Image: New Status in QtMir: Invalid Status in qtmir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: In Progress Bug description: on arale rc-proposed i'm hitting a bug in the spread since a while where apps do not have any content in the spread overview anymore but only show their shadow ... the image at http://i.imgur.com/r7tnyym.png shows the issue, as you can see the two front apps do not have any content but show only their shadow ... tapping on such an app to foreground it restarts it properly and the content is visible in the spread again. i do not see this behavior on krillin.. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1474319/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467740] Re: Lots of thumbnail requests with invalid size
Well, consider the cost of scaling down from a full-size photo to a thumbnail. It takes a quarter of a second on a Nexus 4. Surely, it's not too much to ask the caller what size thumbnail it wants? If we are not told what size the caller needs, we can either deliver the full-size image, which is really expensive and eats a lot of disk space, or we can deliver some thumbnail that is arbitrarily smaller and ends up getting scaled up and looking bad. Either the battery loses or the user experience loses. The meaning of (0, 0) is "give me the best thumbnail available". We'll faithfully do that. We ask that callers use this feature judiciously because it is expensive. The meaning of (-1, -1) is "I don't know what I need, just give me something." I don't think that's a good idea, and we should never have supported that feature in the first place. If the caller doesn't know what size image it needs, there is a problem with the caller, I think. If the caller doesn't mind scaling up and the loss of image quality, it is free to ask for (256, 256) or whatever, and we'll provide that. The point here is that the thumbnailer has no business setting policy. The policy is up to the caller. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1467740 Title: Lots of thumbnail requests with invalid size Status in thumbnailer package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When using scopes, the thumbnailer gets loads of requests with QSize(-1,-1) from the shell. For example, with a bunch of videos recorded, run up the video scope and go to "My Videos". The shell asks for a thumbnail at QSize(-1,-1) for the tiny thumbnail that appears to the left of each list entry. The problem with this is that the thumbnailer interprets this to mean "give me the largest size you can (limited to a 1920x1920 bounding box). That's very expensive, especially in terms of disk space, because that 1920 "thumbnail" ends up going into the cache, needlessly hogging space. We are about to add a qWarning message to the QML side that reports invalid QSize requests. For now, we are going to retain the old behavior, but this will turn into an error soon. The most effective way to use the thumbnailer is to simply ask for an image in the desired size, with neither width nor height of -1. The thumbnailer will efficiently produce a thumbnail for that. (We do lots of internal caching to avoid extracting or downloading a thumbnail unnecessarily.) The thumbnailer may deliver a thumbnail that is smaller than what was asked for (because it never up-scales) so, if asked for a thumbnail of size 256, it's guaranteed not to be larger, but might be smaller (if the original image is smaller than what was asked for). Could you please adjust the shell behavior to ask for specific, valid sizes only? Running a tail -f on ~/.cache/upstart/dbus.log allows you to see the requests as they are made. Each request shows the size that was asked for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1467740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1413710] Re: Xorg crash - Fullscreen causing crash
Jullian Gafar, it will help immensely if you filed a new crash report following https://help.ubuntu.com/community/ReportingBugs . Please feel free to subscribe me to it. ** Attachment removed: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1413710/+attachment/4449393/+files/dmesg.txt ** Attachment removed: "lspci.txt" https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1413710/+attachment/4449390/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1413710 Title: Xorg crash - Fullscreen causing crash Status in X.Org X server: Invalid Status in xorg package in Ubuntu: Incomplete Bug description: I was listening to this YouTube video: http://www.infinitelooper.com/?v=-tJYN-eG1zk&p=n When I decided to make it full screen, but it didn't want to go, so I very quickly double-clicked on it twice, and then the entire screen went black. And no matter what I did, it go away. Although I could still hear the music from the video. As I couldn't do anything really about it I had to hold down my power button and force it to shutdown. And when it started up the screen was fine. It is a laptop so I don't think that the monitor just turned off or something. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: xorg 1:7.7+7ubuntu2 ProcVersionSignature: Ubuntu 3.16.0-29.39-generic 3.16.7-ckt2 Uname: Linux 3.16.0-29-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.7-0ubuntu8.1 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Jan 22 19:26:26 2015 DistUpgraded: 2014-12-13 16:39:34,851 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:5002] InstallationDate: Installed on 2014-12-06 (47 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: LENOVO 62742SG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-29-generic root=UUID=3883b8c8-34cb-4ec2-8834-fe85bbd10f52 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: Upgraded to utopic on 2014-12-13 (40 days ago) dmi.bios.date: 11/15/2012 dmi.bios.vendor: LENOVO dmi.bios.version: H5ET69WW (1.12 ) dmi.board.asset.tag: Not Available dmi.board.name: 62742SG dmi.board.vendor: LENOVO dmi.board.version: Win8 Pro DPK IPG dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrH5ET69WW(1.12):bd11/15/2012:svnLENOVO:pn62742SG:pvrLenovoB590:rvnLENOVO:rn62742SG:rvrWin8ProDPKIPG:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 62742SG dmi.product.version: Lenovo B590 dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.56-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Thu Jan 22 19:19:28 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 827 vendor LGD xserver.version: 2:1.16.0-1ubuntu1.2 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/1413710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1294732] Re: [OOBE] "phone" string in tablet oobe; oobe should have "tablet" or generic term
** Changed in: unity8 (Ubuntu) Status: Confirmed => 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/1294732 Title: [OOBE] "phone" string in tablet oobe; oobe should have "tablet" or generic term Status in Ubuntu UX: Fix Committed Status in unity8 package in Ubuntu: In Progress Bug description: build r237 the oobe on the tablet (nexus 7) refers to a "phone" it should refer to a "tablet" or a generic like "your device" See also bug 1258211. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1294732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487839] Re: Crash when closing window
I know that now. I reset the phone using the "factory settings" option in "About your phone". I just finished flashing the phone using BQ's flash utility and everything's back to normal. I'll close the bug report. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1487839 Title: Crash when closing window Status in Mir: New Status in mir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Every time I close a window by sliding it up, Ubuntu Touch crashes and restarts. Device : BQ Aquaris E5 HD OS : Ubuntu 15.04 - armhf (20150713-202300) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1487839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487754] Re: Local storage not working properly
Hi, The full code is accessible here : https://github.com/Inglebard/YAOSWA/ I am working in master-dev branch. The concerned file where local storage is present is "app.js" in "js" folder inside "www". Maybe, there are other issue but don't pay attention. I attach you an armf click package where the issue is present. I am testing on BQ Aquaris E4.5. I also noticed the local storage issue seems less present in emulator but i'm not totally sure. ** Attachment added: "yaoswa.inglebard_1.2.0_armhf.click" https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1487754/+attachment/4452070/+files/yaoswa.inglebard_1.2.0_armhf.click -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1487754 Title: Local storage not working properly Status in Oxide: New Status in webbrowser-app package in Ubuntu: Invalid Bug description: Hi, I noticed some days ago now, that local storage (and may be other web storage) not persist data randomly. It's pretty easy to show the issue with a website which use local storage. To reproduce this issue : - With a phone or emulator, go to http://todomvc.com/examples/angularjs/ - Create a simple todo list - Close the browser - Open the browser - And go back to http://todomvc.com/examples/angularjs/ - If data are correctly restored, reproduce all the step and you will see, sometimes, it not restore the last local storage. So the issue is present in Browser. I also noticed, it happens in webview, for example in my application : https://uappexplorer.com/app/yaoswa.inglebard So the problem exist in Webview too. To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1487754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488431] Re: Clients fail to create surfaces when using Mir server in compositor mode
The system-compositor window manager expects clients to create fullscreen windows associated with outputs. For example: VT1: sudo bin/mir_demo_server --window-manager system-compositor --arw-file VT2: bin/mir_demo_server --host /tmp/mir_socket VT3: bin/mir_demo_client_eglplasma Which works for me. You can also, for example, connect the USC "spinner" directly: bin/unity-system-compositor-spinner -m /tmp/mir_socket Hmm. That last one doesn't work today. (But, oddly, fails to get a connection - not create a surface.) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488431 Title: Clients fail to create surfaces when using Mir server in compositor mode Status in mir package in Ubuntu: Confirmed Bug description: When trying to run the Unity 8 session on an up to date wily laptop (using the unity8-desktop-session-mir package) I'm only seeing a black screen. Digging down, it appears when running a Mir server in compositor mode the Mir clients are unable to create surfaces. To reproduce: 1. Switch to VT1 2. Run a Mir server in compositor mode: $ sudo mir_demo_server --window-manager system-compositor --arw-file 3. Switch to VT2 4. Run a Mir client: $ MIR_SOCKET=/tmp/mir_socket mir_demo_client_basic 5. Switch to VT1 6. Switch to VT2 Expected result: The client runs successfully Observed result: The client hits an assertion that the surface is not valid. Using a modified client to see the error message (see lp:~robert- ancell/mir/basic-client-print-surface-error) it gives: Error processing request: Failed to place surface in requested output Internal error details: /build/mir-QIEYOz/mir-0.15.0+15.10.20150818/src/server/shell/graphics_display_layout.cpp(91): Throw in function virtual void mir::shell::GraphicsDisplayLayout::place_in_output(mir::graphics::DisplayConfigurationOutputId, mir::geometry::Rectangle&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to place surface in requested output The above steps work file if the --window-manager system-compositor flag is removed. This used to work before and appears to work on some up to date wily systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 374807] Re: grep does not work for UTF-16 files
This is not surprising since 'grep' is a standard POSIX utility. It uses POSIX locales (http://pubs.opengroup.org/onlinepubs/9699919799/utilities/grep.html#tag_20_55_08). So if you read the POSIX standard carefully, then you are going to find out the following: UTF-16 and UTF-32 cannot be supported in POSIX locales because these encoding forms imply using 2-byte and 4-byte code-units respectively making the encoding of '/' and '.' nonconforming. Quoting http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap06.html: "Conforming implementations shall support one or more coded character sets. Each supported locale shall include the portable character set, which is the set of symbolic names for characters in Portable Character Set. ... POSIX.1-2008 places only the following requirements on the encoded values of the characters in the portable character set: ... The encoded values associated with and shall be invariant across all locales supported by the implementation. The encoded values associated with the members of the portable character set are each represented in a single byte. Moreover, if the value is stored in an object of C-language type char, it is guaranteed to be positive (except the NUL, which is always zero)." Another issue is that sizeof(wchar_t) is implementation defined. My tests on Ubuntu show that sizeof(wchar_t) returns 4 (bytes) and you need some other data type to store UTF-16 code units in a portable way. I would say that this should not be fixed: you should use iconv in a pipeline to do the appropriate grepping with UTF-8 (though this might be resource-intensive for large XML files). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to grep in Ubuntu. https://bugs.launchpad.net/bugs/374807 Title: grep does not work for UTF-16 files Status in grep package in Ubuntu: Confirmed Bug description: Binary package hint: grep Release: Description:Ubuntu 9.04 Release:9.04 Package: grep: Installed: 2.5.3~dfsg-6ubuntu1 Candidate: 2.5.3~dfsg-6ubuntu1 Version table: *** 2.5.3~dfsg-6ubuntu1 0 500 http://gb.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status When grep-ing a UTF-16 file, I expected results for the search pattern I was using. However, no matches were found (using grep without options and 'grep -hi'). I am not sure what program initially created the file as I received them via email from a Windows user. I have attached part of the file for testing (I have gzipped the file to reduce any risk of the browser mangling it). 'file' returns the filetype as 'Little-endian UTF-16 Unicode character data, with CRLF, CR line terminators'. I have attached a gzip extract of the file (just the first ten lines returned from 'head'). Other text utilities such as cat, less, head, tail and vim have no problem dealing with the file. So far as I have found, only grep cannot handle the file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grep/+bug/374807/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488484] [NEW] "Quit" launcher app menu item not translated
Public bug reported:
Test case.
- Flash the phone.
- Switch to Spanish.
- Complete the installation wizard and gesture tutorial.
- Open the Launcher.
- Long tap on an app.
Expected result.
- All items in the menu should be translated.
Actual result.
- "Quit" is not translated.
String is marked for translation, but it is not available in Launchpad.
52:launcheritem.cpp m_quitAction.setText(gettext("Quit"));
** Affects: unity8 (Ubuntu)
Importance: Undecided
Status: New
** Tags: touch-l10n
--
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/1488484
Title:
"Quit" launcher app menu item not translated
Status in unity8 package in Ubuntu:
New
Bug description:
Test case.
- Flash the phone.
- Switch to Spanish.
- Complete the installation wizard and gesture tutorial.
- Open the Launcher.
- Long tap on an app.
Expected result.
- All items in the menu should be translated.
Actual result.
- "Quit" is not translated.
String is marked for translation, but it is not available in
Launchpad.
52:launcheritem.cpp m_quitAction.setText(gettext("Quit"));
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1488484/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370245] Re: wpa_supplicant version 2.2 available
just wanted to note that 2.4 seems broken, at least in Fedora for some setups of wireless networks: https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1473088 a fix in 14.04 seems reasonable, maybe by upgrading to 2.3 if possible. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1370245 Title: wpa_supplicant version 2.2 available Status in wpa package in Ubuntu: Fix Released Status in wpasupplicant package in Ubuntu: Won't Fix Bug description: Currently version 2.1 is still the version slated to be shipped with utopic. It seems from http://w1.fi/wpa_supplicant/ that wpa_supplicant version 2.2 was released in 2014-06. Is it possible for 2.2 to be packaged? Thanks! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1370245/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340481] Re: lrt test found crash file _usr_lib_arm-linux-gnueabihf_unity-scopes_scoperunner.32011.crash
It is not working in my pc. I am using Ubuntu for my oficial purpose http://mriduladutt.in Please suggest me some alternate code. -- 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/1340481 Title: lrt test found crash file _usr_lib_arm-linux-gnueabihf_unity- scopes_scoperunner.32011.crash Status in unity-scope-click package in Ubuntu: New Bug description: Summary: Crash file _usr_lib_arm-linux-gnueabihf_unity-scopes_scoperunner.32011.crash was found Steps to reproduce: 1. Run lrt test in lp:lrt Expected result: No crashes happen Actual result: A crash happened System info: base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/utopic-proposed build_number: 124 version_detail: ubuntu=20140710.1,device=20140709,version=124 Device=mako To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1340481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1485659] Re: Date/time indicator doesn't update after changing time zone
I think it's a glib GFileMonitor problem - it works again if I build 2.44 and run with that. The code here is watching /etc/timezone to know when it changes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1485659 Title: Date/time indicator doesn't update after changing time zone Status in indicator-datetime package in Ubuntu: Confirmed Bug description: After changing the timezone the time displayed in the date/time indicator is still in my old time zone. I sent a signal to the indicator-datetime-service process, and after it restarted the correct time was displayed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu2~gcc5.1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 17 08:51:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-19 (178 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to wily on 2015-07-01 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1485659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488431] Re: Clients fail to create surfaces when using Mir server in compositor mode
Ah! MIR_CLIENT_PLATFORM_PATH=/home/alan/local/lib/mir/client-platform bin /unity-system-compositor-spinner -m /tmp/mir_socket works. (But spinner eats the helpful error message.) ** Changed in: mir (Ubuntu) Status: Confirmed => Invalid ** Changed in: mir (Ubuntu) Importance: Critical => Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1488431 Title: Clients fail to create surfaces when using Mir server in compositor mode Status in mir package in Ubuntu: Invalid Bug description: When trying to run the Unity 8 session on an up to date wily laptop (using the unity8-desktop-session-mir package) I'm only seeing a black screen. Digging down, it appears when running a Mir server in compositor mode the Mir clients are unable to create surfaces. To reproduce: 1. Switch to VT1 2. Run a Mir server in compositor mode: $ sudo mir_demo_server --window-manager system-compositor --arw-file 3. Switch to VT2 4. Run a Mir client: $ MIR_SOCKET=/tmp/mir_socket mir_demo_client_basic 5. Switch to VT1 6. Switch to VT2 Expected result: The client runs successfully Observed result: The client hits an assertion that the surface is not valid. Using a modified client to see the error message (see lp:~robert- ancell/mir/basic-client-print-surface-error) it gives: Error processing request: Failed to place surface in requested output Internal error details: /build/mir-QIEYOz/mir-0.15.0+15.10.20150818/src/server/shell/graphics_display_layout.cpp(91): Throw in function virtual void mir::shell::GraphicsDisplayLayout::place_in_output(mir::graphics::DisplayConfigurationOutputId, mir::geometry::Rectangle&) Dynamic exception type: boost::exception_detail::clone_impl > std::exception::what: Failed to place surface in requested output The above steps work file if the --window-manager system-compositor flag is removed. This used to work before and appears to work on some up to date wily systems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mir/+bug/1488431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487839] Re: Crash when closing window
** Changed in: mir Status: New => Invalid ** Changed in: mir (Ubuntu) Status: New => Invalid ** Changed in: unity8 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1487839 Title: Crash when closing window Status in Mir: Invalid Status in mir package in Ubuntu: Invalid Status in unity8 package in Ubuntu: Invalid Bug description: Every time I close a window by sliding it up, Ubuntu Touch crashes and restarts. Device : BQ Aquaris E5 HD OS : Ubuntu 15.04 - armhf (20150713-202300) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1487839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488484] Re: "Quit" launcher app menu item not translated
** Changed in: unity8 (Ubuntu)
Status: New => Triaged
** Changed in: unity8 (Ubuntu)
Assignee: Lukáš Tinkl (lukas-kde) => Albert Astals Cid (aacid)
** Changed in: unity8 (Ubuntu)
Importance: Undecided => High
** Changed in: unity8 (Ubuntu)
Status: Triaged => In Progress
** Branch linked: lp:~aacid/unity8/make_pot_file
--
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/1488484
Title:
"Quit" launcher app menu item not translated
Status in unity8 package in Ubuntu:
In Progress
Bug description:
Test case.
- Flash the phone.
- Switch to Spanish.
- Complete the installation wizard and gesture tutorial.
- Open the Launcher.
- Long tap on an app.
Expected result.
- All items in the menu should be translated.
Actual result.
- "Quit" is not translated.
String is marked for translation, but it is not available in
Launchpad.
52:launcheritem.cpp m_quitAction.setText(gettext("Quit"));
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1488484/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488484] Re: "Quit" launcher app menu item not translated
** Changed in: unity8 (Ubuntu)
Assignee: (unassigned) => Lukáš Tinkl (lukas-kde)
--
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/1488484
Title:
"Quit" launcher app menu item not translated
Status in unity8 package in Ubuntu:
In Progress
Bug description:
Test case.
- Flash the phone.
- Switch to Spanish.
- Complete the installation wizard and gesture tutorial.
- Open the Launcher.
- Long tap on an app.
Expected result.
- All items in the menu should be translated.
Actual result.
- "Quit" is not translated.
String is marked for translation, but it is not available in
Launchpad.
52:launcheritem.cpp m_quitAction.setText(gettext("Quit"));
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1488484/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1485659] Re: Date/time indicator doesn't update after changing time zone
We should instead watch timedated's Timezone property ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => In Progress ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) => Iain Lane (laney) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1485659 Title: Date/time indicator doesn't update after changing time zone Status in indicator-datetime package in Ubuntu: In Progress Bug description: After changing the timezone the time displayed in the date/time indicator is still in my old time zone. I sent a signal to the indicator-datetime-service process, and after it restarted the correct time was displayed. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: indicator-datetime 13.10.0+15.10.20150728-0ubuntu2~gcc5.1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 ApportVersion: 2.18-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Mon Aug 17 08:51:44 2015 EcryptfsInUse: Yes InstallationDate: Installed on 2015-02-19 (178 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Alpha amd64 (20150110) SourcePackage: indicator-datetime UpgradeStatus: Upgraded to wily on 2015-07-01 (46 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1485659/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396700] Re: Indicator needs to be updated to bluez5
This bug was fixed in the package indicator-bluetooth - 0.0.6+15.10.20150813-0ubuntu1 --- indicator-bluetooth (0.0.6+15.10.20150813-0ubuntu1) wily; urgency=medium [ Robert Ancell ] * Support Bluez 5 (LP: #1396700) -- CI Train Bot Thu, 13 Aug 2015 15:42:34 + ** Changed in: indicator-bluetooth (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/1396700 Title: Indicator needs to be updated to bluez5 Status in Canonical System Image: Confirmed Status in indicator-bluetooth package in Ubuntu: Fix Released Bug description: See https://blueprints.launchpad.net/ubuntu/+spec/desktop-v-bluez5 for details To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1396700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1478222] Re: Ubuntu Touch forgets WiFi settings after first connection. EDUROAM network WPA & WPA2 Enterprise
Thanks Enrique for the work-around. In fact, doing what you describe allows me to tick the "remember password". Otherwise, one can never tick the field, because it is covered by the keyboard. This means: Anyone who fills the form from the top to the bottom (like everyone usually does it) will not succeed! Point (1) is a bug. Your point (2) is also a bug. The correct password is not accepted if "remember password" was not ticked before. -- 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/1478222 Title: Ubuntu Touch forgets WiFi settings after first connection. EDUROAM network WPA & WPA2 Enterprise Status in indicator-network package in Ubuntu: New Bug description: Using WPA & WPA2 Enterprise I connected to the EDUROAM WiFi network with Ubuntu Touch. This works fine. However, when leaving the WiFi range and coming back, Ubuntu Touch will not be able to connect again. It asks again for the password, but the correct password does not work anymore. The only (annoying) workaround is to delete "EDUROAM" network from "previous networks" in the WiFi setting and then apply all setting again. The WiFi access will work then until one leaves the WiFi range again. Additional info: The EDUROAM WiFi network is a unified WiFi network to get access almost any European University. Default set-up is described here: http://www.urz.uni-heidelberg.de/zugang/eduroam/linux_ubuntu.html System: Ubuntu Touch 15.04(r24). Device-Built: KRILIN01A-S15A_BQ_L100EN_2024_150713 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1478222/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488506] [NEW] Trying to run 2 external displays on my Laptop
Public bug reported: I'm attempting to run two external monitors using my laptop, in addition to it's built-in display. The machine I'm using is a HP Elitebook 8570p, and based on everything that I've read, the machine id physically capable of doing what I want, but the drivers don't seem to be able to allow it. I can have either my monitor on the display port -OR- the monitor on the VGA port active, but I can seem to get both to work at the same time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: kwin Date: Tue Aug 25 15:21:05 2015 DistUpgraded: 2014-04-25 08:04:56,411 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:17a7] InstallationDate: Installed on 1980-01-01 (13020 days ago) InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120820.1) LightdmGreeterLog: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession LightdmGreeterLogOld: QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such file or directory QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus Bus::open: Can not get ibus-daemon's address. IBusInputContext::createInputContext: no connection to ibus-daemon file:///usr/share/kde4/apps/lightdm-kde-greeter/themes/userbar/main.qml:135: Unable to assign [undefined] to QString usersession MachineType: Hewlett-Packard HP EliteBook 8570p ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=d4fb8295-a504-4c69-a799-fca503b14e99 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-25 (487 days ago) dmi.bios.date: 01/31/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68ICF Ver. F.40 dmi.board.name: 17A7 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 42.32 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68ICFVer.F.40:bd01/31/2013:svnHewlett-Packard:pnHPEliteBook8570p:pvrA1029D1103:rvnHewlett-Packard:rn17A7:rvrKBCVersion42.32:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8570p dmi.product.version: A1029D1103 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz N/A version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jan 1 02:00:41 1980 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 600 vendor LGD xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1488506 Title: Trying to run 2 external displays on my Laptop Status in xorg package in Ubuntu: New Bug description: I'm attempting to run two external monitors using my laptop, in addition to it's built-in display. The machine I'm using is a HP Elitebook 8570p, and based on everything that I've read, the machine id physically capable of doing what I want, but the drivers don't seem to be able to allow it. I can have either my monitor on the display port -OR- the monitor on the VGA port active, but I can seem to get both to work at the same time. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg (not installed) ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.12 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/g
[Touch-packages] [Bug 952999] Re: gdb crashed with ImportError in /usr/lib/debug/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16-gdb.py: No module named libstdcxx.v6.printers
That issue came back either with the updates of the last month, up to Feb. 2015 it was possible to use gdb without any hazzle: output snippet from today: ... Reading symbols from /lib/x86_64-linux-gnu/libdbus-1.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/x86_64-linux-gnu/libdbus-1.so.3 0x7f06702a882d in read () at ../sysdeps/unix/syscall-template.S:81 81 ../sysdeps/unix/syscall-template.S: Datei oder Verzeichnis nicht gefunden. Traceback (most recent call last): File "/usr/share/gdb/auto-load/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.19-gdb.py", line 63, in from libstdcxx.v6.printers import register_libstdcxx_printers ImportError: No module named 'libstdcxx' ... ||/ Name VersionArchitektur Beschreibung +++-==-==-==-= ii gdb7.7.1-0ubuntu5~14. amd64 GNU Debugger ii libstdc++6:amd64 4.8.4-2ubuntu1~14. amd64 GNU Standard C++ Library v3 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gdb in Ubuntu. https://bugs.launchpad.net/bugs/952999 Title: gdb crashed with ImportError in /usr/lib/debug/usr/lib/i386-linux- gnu/libstdc++.so.6.0.16-gdb.py: No module named libstdcxx.v6.printers Status in gdb package in Ubuntu: Fix Released Bug description: it just popped up to say that there was an error. ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gdb 7.4-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-18.29-generic 3.2.9 Uname: Linux 3.2.0-18-generic i686 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 CrashCounter: 1 Date: Mon Mar 12 12:12:49 2012 ExecutablePath: /usr/bin/gdb InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007) ProcCmdline: gdb --batch --ex file\ /usr/bin/synergyc --ex core-file\ /tmp/tmp5M47_D --ex set\ backtrace\ limit\ 2000 --ex p\ -99 --ex bt\ full --ex p\ -99 --ex thread\ apply\ all\ bt\ full --ex p\ -99 --ex info\ registers --ex p\ -99 --ex x/16i\ $pc --ex p\ -99 --ex print\ __abort_msg->msg SourcePackage: gdb Title: gdb crashed with ImportError in /usr/lib/debug/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16-gdb.py: No module named libstdcxx.v6.printers Traceback: Traceback (most recent call last): File "/usr/lib/debug/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16-gdb.py", line 62, in from libstdcxx.v6.printers import register_libstdcxx_printers ImportError: No module named libstdcxx.v6.printers UpgradeStatus: Upgraded to precise on 2012-03-05 (6 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/952999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 631870] Re: Laptop goes back to hibernate twice upon resume after battery discharged and cable plugged
This version has expired ** Changed in: upower (Ubuntu) Status: New => Invalid -- 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/631870 Title: Laptop goes back to hibernate twice upon resume after battery discharged and cable plugged Status in upower package in Ubuntu: Invalid Bug description: Binary package hint: upower Observed on Dell Vostro 1015 with Ubuntu Lucid (10.04.1), kernel = 2.6.32-24-generic, upower 0.9.1-1. Scenario: let battery discharge, laptop goes to hibernation, plug the cable and close the lid. Open the lid and power on. The first resume brings up the last screen with ~10 warning windows of battery low. Then the hibernation kicks in again. On the second resume, it brings me to my password screen (locked). Once again, the hibernation kicks in. On the 3rd resume, I'm back to the password screen, but I can enter my password, close the battery low warning windows and continue normally. I have saved my kernel log, but I'm not sure which part is relevant. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/631870/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1481673] Re: No mechanism for displaying internal downloads in transfer indicator
** Changed in: ubuntu-download-manager (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-download-manager (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-download-manager (Ubuntu) Assignee: (unassigned) => Manuel de la Peña (mandel) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-download-manager in Ubuntu. https://bugs.launchpad.net/bugs/1481673 Title: No mechanism for displaying internal downloads in transfer indicator Status in Canonical System Image: New Status in indicator-transfer package in Ubuntu: Confirmed Status in ubuntu-download-manager package in Ubuntu: Confirmed Bug description: We're currently adding support to the webbrowser-app to allow it download files internally in addition to sending them to other applications, currently download manager has a metadata property titled "showInIndicator", however this doesn't appear to have any effect when the transfer is happening inside an application without content-hub involvement. This results in an inconsistent experience for the user, as some downloads from the browser show up in the indicator (those opened immediately with other apps) and some don't (those downloaded for later use). To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1481673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1467740] Re: Lots of thumbnail requests with invalid size
> Well, consider the cost of scaling down from a full-size photo to a > thumbnail. It takes a quarter of a second on a Nexus 4. Yes, that should be done as few times as possible. > Surely, it's not too much to ask the caller what size thumbnail it wants? It actually is, i have no idea of the image i want unless you tell me the aspect ratio and since i can't know the aspect ratio i need the full image. > The meaning of (-1, -1) is "I don't know what I need, just give me something. You're making this up, the API documentation explicitly says "sourceSize can be cleared to the natural size of the image by setting sourceSize to undefined." > The point here is that the thumbnailer has no business setting policy. You say you have no business setting the policy but then go and set a policy that says "i'm not accepting undefined sizes even if the API says i should", please do not do that. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1467740 Title: Lots of thumbnail requests with invalid size Status in thumbnailer package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: When using scopes, the thumbnailer gets loads of requests with QSize(-1,-1) from the shell. For example, with a bunch of videos recorded, run up the video scope and go to "My Videos". The shell asks for a thumbnail at QSize(-1,-1) for the tiny thumbnail that appears to the left of each list entry. The problem with this is that the thumbnailer interprets this to mean "give me the largest size you can (limited to a 1920x1920 bounding box). That's very expensive, especially in terms of disk space, because that 1920 "thumbnail" ends up going into the cache, needlessly hogging space. We are about to add a qWarning message to the QML side that reports invalid QSize requests. For now, we are going to retain the old behavior, but this will turn into an error soon. The most effective way to use the thumbnailer is to simply ask for an image in the desired size, with neither width nor height of -1. The thumbnailer will efficiently produce a thumbnail for that. (We do lots of internal caching to avoid extracting or downloading a thumbnail unnecessarily.) The thumbnailer may deliver a thumbnail that is smaller than what was asked for (because it never up-scales) so, if asked for a thumbnail of size 256, it's guaranteed not to be larger, but might be smaller (if the original image is smaller than what was asked for). Could you please adjust the shell behavior to ask for specific, valid sizes only? Running a tail -f on ~/.cache/upstart/dbus.log allows you to see the requests as they are made. Each request shows the size that was asked for. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1467740/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1456328] Re: Need a development framework on Vivid overlay
Actually landed now ** Changed in: canonical-devices-system-image Status: In Progress => Fix Released -- 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/1456328 Title: Need a development framework on Vivid overlay Status in Canonical System Image: Fix Released Status in click package in Ubuntu: In Progress Bug description: While we continue to develop on top of 15.04 using the overlay, we will need to add new APIs. Normally this would occur in the new release, like Wily, but as Wily is moving to snap it probably does not make sense there. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1456328/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487620] Re: wireless treats driver failure as network security refusal
The "being pushed onto the nearest open network" is the security risk part of the bug. -- 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/1487620 Title: wireless treats driver failure as network security refusal Status in network-manager package in Ubuntu: New Bug description: I've a Lenovo 585 with Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter - this combination leads to frequent driver failures (sudden component shutdowns) with sound and network hardware being the most likely to temporarily abort. (this isn't the first laptop I've seen this problem on either) Every time the hardware crashes and resets, network-manager treats this as a security abort and asks (erroneously) for network credentials. a: this disrupts all running program and puts up a modal dialogue b: this is unnecessary, because above. c: this is a security risk because it will try (under normal circumstances) to hop networks until it finds an open one, and this can put the unit into a secure vulnerable state. I'm happy to help provide more info - this bug hits me anywhere up to several times an hour. recommend : this is a security risk / serious / blocking (fix asap) bug. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: KDE Date: Fri Aug 21 14:20:55 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-28 (692 days ago) InstallationMedia: Linux Mint 15 "Olivia" - Release amd64 (20130520) IpRoute: default via 10.253.0.1 dev wlan0 proto static metric 1024 1.1.1.1 via 10.253.0.1 dev wlan0 proto dhcp metric 10 10.253.0.0/16 dev wlan0 proto kernel scope link src 10.253.0.20 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 IUGO_STAFF 25f36dd0-8cfa-4336-91a4-2ac49e7c3b4d /org/freedesktop/NetworkManager/ActiveConnection/7 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- virbr0-nic tap unmanaged/org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1487620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487620] Re: wireless treats driver failure as network security refusal
Open networks are a direct security risk, at least in some locations. And that does include the neighbours of my office.It's not "immediately obvious" one has been put into a security risk situation if one is busy working. There's also no obvious way to mark a network (even if it's visibly a honey pot for harvesting passwords) as unhealthy/bad, because the above bug will mean the system automatically connects. -- 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/1487620 Title: wireless treats driver failure as network security refusal Status in network-manager package in Ubuntu: New Bug description: I've a Lenovo 585 with Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter - this combination leads to frequent driver failures (sudden component shutdowns) with sound and network hardware being the most likely to temporarily abort. (this isn't the first laptop I've seen this problem on either) Every time the hardware crashes and resets, network-manager treats this as a security abort and asks (erroneously) for network credentials. a: this disrupts all running program and puts up a modal dialogue b: this is unnecessary, because above. c: this is a security risk because it will try (under normal circumstances) to hop networks until it finds an open one, and this can put the unit into a secure vulnerable state. I'm happy to help provide more info - this bug hits me anywhere up to several times an hour. recommend : this is a security risk / serious / blocking (fix asap) bug. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: KDE Date: Fri Aug 21 14:20:55 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-28 (692 days ago) InstallationMedia: Linux Mint 15 "Olivia" - Release amd64 (20130520) IpRoute: default via 10.253.0.1 dev wlan0 proto static metric 1024 1.1.1.1 via 10.253.0.1 dev wlan0 proto dhcp metric 10 10.253.0.0/16 dev wlan0 proto kernel scope link src 10.253.0.20 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 IUGO_STAFF 25f36dd0-8cfa-4336-91a4-2ac49e7c3b4d /org/freedesktop/NetworkManager/ActiveConnection/7 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- virbr0-nic tap unmanaged/org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1487620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487620] Re: wireless treats driver failure as network security refusal
However, it blacklisting the active and VALID network because of a driver fault - that's not a security risk, that's just an ongoing nightmare. After it goes through the entire group of valid networks, that's when it starts hopping onto honeypots, and I can usually catch it before then. -- 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/1487620 Title: wireless treats driver failure as network security refusal Status in network-manager package in Ubuntu: New Bug description: I've a Lenovo 585 with Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter - this combination leads to frequent driver failures (sudden component shutdowns) with sound and network hardware being the most likely to temporarily abort. (this isn't the first laptop I've seen this problem on either) Every time the hardware crashes and resets, network-manager treats this as a security abort and asks (erroneously) for network credentials. a: this disrupts all running program and puts up a modal dialogue b: this is unnecessary, because above. c: this is a security risk because it will try (under normal circumstances) to hop networks until it finds an open one, and this can put the unit into a secure vulnerable state. I'm happy to help provide more info - this bug hits me anywhere up to several times an hour. recommend : this is a security risk / serious / blocking (fix asap) bug. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: KDE Date: Fri Aug 21 14:20:55 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-28 (692 days ago) InstallationMedia: Linux Mint 15 "Olivia" - Release amd64 (20130520) IpRoute: default via 10.253.0.1 dev wlan0 proto static metric 1024 1.1.1.1 via 10.253.0.1 dev wlan0 proto dhcp metric 10 10.253.0.0/16 dev wlan0 proto kernel scope link src 10.253.0.20 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 IUGO_STAFF 25f36dd0-8cfa-4336-91a4-2ac49e7c3b4d /org/freedesktop/NetworkManager/ActiveConnection/7 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- virbr0-nic tap unmanaged/org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1487620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 711061] Re: [MIR] openjpeg
Note also that there is actually no alternative for openjpeg. It is the only actively developed JPEG2000 library. If it turns out that it is still a high security risk and it is important to have the Ghostscript upstream developers as an extra security instance to integrate it into Ghostscript for us and not let app developers freely use it and not trust Debian who have it in Main, we have to keep Ghostscript different from Debian, using the Ghostscript-embedded openjpeg. I think we never can do completely away with JPEG2000, as this makes several PDFs not displaying/printing and me receiving a lot of bug reports. As JPEG2000 is not used standalone but only in PDF we can continue using Ghostscript with embedded openjpeg, my main intentions to use openjpeg as separate library are: - Syncing GS with Debian and so ease maintainership - Getting MuPDF into Main which probably also uses openjpeg -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openjpeg in Ubuntu. https://bugs.launchpad.net/bugs/711061 Title: [MIR] openjpeg Status in openjpeg package in Ubuntu: New Bug description: libopenjpeg should be included in main because compiling poppler with --enable-openjpeg in debian/rules gives poppler greater functionality (please see bug 710412). Since this change to /debian/rules adds libopenjpeg as a build-dep to poppler, which is in main, libopenjpeg must also be in main. Main inclusion requirements: 1. It is already in the universe. 2. The package is a new build-dep, and has a large user base (think evince). 3. Searching http://secunia.com/advisories/search/ for libopenjpeg gave zero results. 4. Libopenjpeg has no current Ubuntu bugs (https://bugs.launchpad.net/ubuntu/maverick/+source/openjpeg) in the Debian bug tracking system libopenjpeg has 1 open bug (http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=libopenjpeg2), this is an encoding bug, but the main use for this package will be decoding. Libopenjpeg does not require any configuration or debconf questions. 5. N/A 6. All build-deps are already included in main. 7. I am afraid that this is a bit over my head, hopefully someone else could ensure that this package meets the requirments here. Based on its long inclusion in Debian and Ubuntu I think that it should be alright here. 8.This is a fairly simple program not needed too much maintenance, as shown by the bug reports. 9. The package title and description seem to be in order. My only final comments are that I am sorry this may not be quite the normal MIR, but I am just a member of bug control, not a dev. Also, any help and advise along the way would be much appreciated. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjpeg/+bug/711061/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488072] Re: Headset loud warning issues when the screen is blank
** Changed in: indicator-sound (Ubuntu) Assignee: (unassigned) => Xavi Garcia (xavi-garcia-mena) -- 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/1488072 Title: Headset loud warning issues when the screen is blank Status in indicator-sound package in Ubuntu: New Bug description: STEPS: This is a behavioural bug and may require input from design. 1. Install the latest rc-proposed image 2. Plug in a wired headset 3. Play some music 4. Tap on cancel the the volume is dropped below the acceptable level 5. Blank the screen 6. Tap the volume up button EXPECTED: I expect something to tell me I need to wake the phone to accept the policy so the volume raises above the 50% level ACTUAL: The popup appear but gives no indication that it is there so you have no idea why the volume isn't increasing. POSSIBLE SOLUTIONS: 1. An audible ping so you know that this volume up is doing something different 2. Wake the screen so the information is visible, only issue here is that the cancel or accept button might be pressed so then there is no idea why it didn't work 3. Flash the led like you do for messages to get the users attention. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1488072/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487680] Re: package python-psutil 1.2.1-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-psutil in Ubuntu. https://bugs.launchpad.net/bugs/1487680 Title: package python-psutil 1.2.1-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-psutil package in Ubuntu: New Bug description: idk ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-psutil 1.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Sat Aug 22 13:37:03 2015 DuplicateSignature: package:python-psutil:1.2.1-1ubuntu2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-22 (0 days ago) InstallationMedia: It SourcePackage: python-psutil Title: package python-psutil 1.2.1-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-psutil/+bug/1487680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471909] Re: MultiThreadedCompositor::destroy_compositing_threads hangs/deadlocks on shutdown or display reconfiguration
** Changed in: mir/0.14 Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1471909 Title: MultiThreadedCompositor::destroy_compositing_threads hangs/deadlocks on shutdown or display reconfiguration Status in Mir: Fix Released Status in Mir 0.13 series: Won't Fix Status in Mir 0.14 series: Won't Fix Status in mir package in Ubuntu: Fix Released Bug description: Try revision 211 of lp:~unity-team/unity-system-compositor/toggle- cursor2/ The desire was to resize all surfaces to the size of the smallest attached display. usc::WindowManager implements the mir::shell::WindowManagement interface. I thought it logical to implement this resizing in add_display. However it causes a deadlock when plugging in a second display, while the compositor is stopping, see this backtrace: http://pastebin.ubuntu.com/11831907/ I suspect Threads 8 and Thread 1 are blocking eachother. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1471909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1471858] Re: Android: rotated display config not applied when an external monitor is hot-plugged
** Changed in: mir/0.14 Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1471858 Title: Android: rotated display config not applied when an external monitor is hot-plugged Status in Mir: Fix Released Status in Mir 0.13 series: Won't Fix Status in Mir 0.14 series: Won't Fix Status in mir package in Ubuntu: Fix Released Bug description: Hardware: Android (Nexus 7), using slimport cable to drive external monitor. Using Mir 0.13 The intention is to configure USC to clone the contents of the internal display to the external display (id=1), but with those contents rotated 90 degrees. Check out revision 220 of lp:~unity-team/unity-system-compositor /toggle-cursor2/ I am implementing a DisplayConfigurationPolicy like this: http://pastebin.ubuntu.com/11830210/ I've got some print statements in there too. On testing this, there are 2 cases: 1. Slimport cable connected at server startup Here, the external monitor comes up rotated correctly. I see the debug statements print. 2. Slimport cable *not* connected at server startup First off, I do not see my debug statement print at server start. Secondly, when I do plug in the slimport cable, while I see my debug prints, the external monitor does not get rotated. You can explicitly tell USC to rotate the external display with dbus (install qdbus-qt5 first): qdbus --system com.canonical.Unity.Screen / com.canonical.Unity.Screen.overrideOrientation 1 90 so rotation does work. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1471858/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351890] Re: Changing external screen resolution with dual monitors
The fix for Trusty is still in that queue - did something wrong happened? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1351890 Title: Changing external screen resolution with dual monitors Status in GTK+: Fix Released Status in ubuntu-mate: Fix Released Status in gtk+2.0 package in Ubuntu: Fix Released Status in mate-control-center package in Ubuntu: Fix Released Status in gtk+2.0 source package in Precise: Fix Committed Status in gtk+2.0 source package in Trusty: In Progress Status in gtk+2.0 package in Debian: Fix Released Bug description: [Impact] Due to a bug in GTK+2, mate-display-properties crashes when the screen resolution is changed *outside* of it (e.g. by changing the resolution not via that app, but somewhere else). The attached patches fix the issue in GTK+2 and prevent crashing of m-d-p. Since this issue caused much inconvenience for users, the fix should be backported to all current stable releases of Ubuntu. [Test Case] The easiest way to reproduce it is via Virtualbox: 1. Run mate-display-properties in the VM. 2. Make the VM go full-screen. 3. See m-d-p crash. [Regression Potential] After several months of testing the patched version of GTK+2 in Debian Jessie, I found no regressions. I consider the regression risk very low here. There were originally some bugs with a few applications (notably Spotify) crashing. We think we've backported patches to fix that - some refcounting issues - but please check a few apps to see they still work. [ Original report ] Changing extrnal screen resolution with dual mon ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: mate-control-center 1.8.1+dfsg1-4 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic i686 ApportVersion: 2.14.5-0ubuntu3 Architecture: i386 CrashCounter: 1 Date: Sun Aug 3 07:09:21 2014 ExecutablePath: /usr/bin/mate-display-properties InstallationDate: Installed on 2014-08-03 (0 days ago) InstallationMedia: Ubuntu MATE 14.10 "Utopic Unicorn" - Alpha i386 (20140731) ProcCmdline: mate-display-properties SegvAnalysis: Skipped: missing required field "Disassembly" Signal: 11 SourcePackage: mate-control-center UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1351890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487910] Re: choppy video
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1487910 Title: choppy video Status in xorg package in Ubuntu: New Bug description: The video streaming and playing is choppy. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 3.19.0-26.28~14.04.1-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic i686 NonfreeKernelModules: wl .tmp.unity.support.test.1: ApportVersion: 2.14.1-0ubuntu3.12 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Aug 23 21:58:39 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.248+bdcom, 3.19.0-25-generic, i686: installed bcmwl, 6.30.223.248+bdcom, 3.19.0-26-generic, i686: installed fglrx-core, 15.200, 3.19.0-26-generic, i686: installed nvidia-304, 304.125: added ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation System Controller Hub (SCH Poulsbo) Graphics Controller [8086:8108] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:02c6] InstallationDate: Installed on 2015-08-22 (1 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805) MachineType: Dell Inc. Inspiron 1010 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-26-generic root=UUID=b8d3b232-5918-4769-9c28-7fc3417b5249 ro mem=900mb quiet splash vt.handoff=7 Renderer: Software SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2009 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 0R990K dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.asset.tag: ** dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A05 dmi.modalias: dmi:bvnDellInc.:bvrA05:bd05/20/2009:svnDellInc.:pnInspiron1010:pvrA05:rvnDellInc.:rn0R990K:rvrA05:cvnDellInc.:ct8:cvrA05: dmi.product.name: Inspiron 1010 dmi.product.version: A05 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Sun Aug 23 21:43:11 2015 xserver.configfile: default xserver.devices: inputVideo BusKEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputIntegrated WebcamKEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputETPS/2 Elantech Touchpad TOUCHPAD, id 10 xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.17.1-0ubuntu3~trusty1 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1487910/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487680] Re: package python-psutil 1.2.1-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-psutil in Ubuntu. https://bugs.launchpad.net/bugs/1487680 Title: package python-psutil 1.2.1-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-psutil package in Ubuntu: New Bug description: idk ProblemType: Package DistroRelease: Ubuntu 14.04 Package: python-psutil 1.2.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2 Uname: Linux 3.19.0-25-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 Date: Sat Aug 22 13:37:03 2015 DuplicateSignature: package:python-psutil:1.2.1-1ubuntu2:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-08-22 (0 days ago) InstallationMedia: It SourcePackage: python-psutil Title: package python-psutil 1.2.1-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-psutil/+bug/1487680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487826] Re: upgrade 14.04 to 14.10 audio is not working
** Information type changed from Private Security to Public -- 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/1487826 Title: upgrade 14.04 to 14.10 audio is not working Status in unity package in Ubuntu: New Bug description: after upgrade 14.04 to 14.10 audio is not working. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20 Uname: Linux 3.13.0-55-generic i686 .tmp.unity.support.test.0: .tmp.unity.support.test.1: ApportVersion: 2.14.7-0ubuntu8.5 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Sun Aug 23 15:41:46 2015 DistUpgraded: 2015-08-23 13:16:21,465 DEBUG enabling apt cron job DistroCodename: utopic DistroVariant: ubuntu GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:167e] InstallationDate: Installed on 2015-03-28 (147 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417) MachineType: Hewlett-Packard HP ProBook 4330s ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic root=UUID=c2636dfe-fdea-4d8d-a089-f8cea5545150 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to utopic on 2015-08-23 (0 days ago) dmi.bios.date: 03/09/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SRR Ver. F.23 dmi.board.name: 167E dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 22.21 dmi.chassis.asset.tag: CNU220206K dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SRRVer.F.23:bd03/09/2012:svnHewlett-Packard:pnHPProBook4330s:pvrA0001D02:rvnHewlett-Packard:rn167E:rvrKBCVersion22.21:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 4330s dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1 version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.2-0ubuntu0.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.2-0ubuntu0.1 version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.914-1~exp1ubuntu4.5 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2 xserver.bootTime: Sat Aug 22 19:42:57 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 13653 vendor SEC xserver.version: 2:1.15.1-0ubuntu2.7 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1487826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 891210] Re: Dash - dash search should catch keyboard events immediately, not after UI is loaded and displayed
Mh, I can't reproduce this anymore, but I guess it might still happen on low powered machine... Any feedback? -- 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/891210 Title: Dash - dash search should catch keyboard events immediately, not after UI is loaded and displayed Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: Once we become expert at using our machines, the delay between tapping the Super key and starting to type results is short, and the computer lags behind. I can hit Super, and start typing the name of a program, and the first few keys are lost because the search field in the Dash didn't appear until after I started typing. That ruins the search, and I must start over. I haven't seen the source code, but surely the the UI isn't cheap to load, and even beginning to do that should be a step after starting to catch key events in a buffer to be replayed after the UI is up. The UI having been displayed must not be a prerequisite for catching the letters of the thing I'm searching for. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/891210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1066963] Re: Dash - Update the Dash to use the Ubuntu medium font weight
** Changed in: unity Milestone: None => 7.3.4 -- 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/1066963 Title: Dash - Update the Dash to use the Ubuntu medium font weight Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: The 12.10 Dash designs specified that the Ubuntu Medium font weight should be used for Category Headers and search filter Category headers (see designs in https://chinstrap.canonical.com/~sabdfl/12_10/desktop_and_netbook/Dash/ ) Unfortunately the Ubuntu Medium font did not land in time to be used in the Dash in 12.10. This change request is the use the Ubuntu Medium font as intended in the 13.04 Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/1066963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 591189] Re: Manage the fullscreen application case
** No longer affects: appmenu-gtk (Ubuntu) ** No longer affects: appmenu-gtk -- 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/591189 Title: Manage the fullscreen application case Status in Application Menu Indicator: Invalid Status in Unity: In Progress Status in Unity 7.2 series: In Progress Status in unity package in Ubuntu: In Progress Bug description: See https://wiki.ubuntu.com/MenuBar#Full-screen%20windows To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/591189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487946] Re: Unity8 always crashes on second restart
There seems to be an issue with restart since for example if i do while [ true ]; do start unity8; sleep 10; stop unity8; sleep 10; done It works fine for a long time (i got bored after 40 min) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1487946 Title: Unity8 always crashes on second restart Status in Mir: New Status in QtMir: New Status in mir package in Ubuntu: New Status in qtmir package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Unity8 always crashes on second restart. Using the "restart unity8" command is very handy for applying environment variables and trying things out. The trouble is that it only ever works once. On the second use, Untiy8/Mir fails to start and in some cases the whole phone reboots (arale). On krillin: restart unity8 restart unity8 # Now the phone never restarts... $ tail ~/.cache/upstart/unity8.log [1440384396.950594] Platform Loader: Selected driver: android (version 0.11.0) Exiting Mir! Reason: Nested Mir and Host Mir cannot use the same socket file to accept connections! ERROR: QMirServer - Mir failed to start terminate called after throwing an instance of 'boost::exception_detail::clone_impl >' what(): Cannot use configuration before apply_settings() call On mako: $ system-image-cli -i current build number: 284 device name: mako channel: ubuntu-touch/devel-proposed/ubuntu last update: 2015-08-19 04:19:23 version version: 284 version ubuntu: 20150819 version device: 20150812 version custom: 20150819 $ restart unity8 $ restart unity8 $ tail -f ~/.cache/upstart/unity8.log [1440385259.474381] mirserver: Starting [1440385259.474899] mircommon: Loading modules from: /usr/lib/arm-linux-gnueabihf/mir/server-platform [1440385259.475083] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-dummy.so [1440385259.477799] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/input-stub.so [1440385259.479172] mircommon: Loading module: /usr/lib/arm-linux-gnueabihf/mir/server-platform/graphics-android.so.3 [1440385259.479355] mirplatform: Found graphics driver: dummy [1440385259.480485] mirplatform: Found graphics driver: android [1440385259.480851] mirserver: Selected driver: android (version 0.14.0) Exiting Mir! Reason: Nested Mir and Host Mir cannot use the same socket file to accept connections! ERROR: QMirServer - Mir failed to start To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1487946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1432871] Re: `df` shows bind mounts instead of real mounts.
I have a new fix for this that I will attempt to upstream. I will submit it again once it gets accepted upstream. ** Changed in: coreutils (Ubuntu) Status: Won't Fix => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1432871 Title: `df` shows bind mounts instead of real mounts. Status in coreutils package in Ubuntu: Incomplete Bug description: [Impact] * df displays bind mounts instead of "real" mounts if the bind mount is mounted to a shorter directory. * justification - This is a change of behavior from precise * Explanation - This patch checks to see if the source directory of a mount is contains the destination directory of the mount it's replacing *(check if it's bind mount from the original directory). [Test Case] * $ mount 192.168.1.2:/raid on /raid type nfs /dev/sdc5 on /data type ext4 (rw) /data/a on /a type none (rw,bind) /raid/temp on /b type none (rw,bind) $df Filesystem 1K-blocks Used Available Use% Mounted on /data/a 449830616 229975284 196982196 54% /a /raid/temp 7752072192 5581343744 1780023296 76% /b I'd expect to see the real mount prioritized over the bind mount. Like so. $df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdc5449830616 229975284 196982196 54% /data 192.168.1.2:/raid 7752072192 5581438976 1779929088 76% /raid [Regression Potential] * Patch is not upstream, and will not be upstreamed *(see other info) * df command could stop working if I wrote the patch poorly. df might not process mounts correctly. [Other Info] * The behavior of df, mount and similar number of other commands has changed going forward. Previously these commands all processed /etc/mtab which was maintained by the mount command. Going forward they still process /etc/mtab, but this is simply a symlink to /proc/mounts now which is maintained by the kernel and likely significantly more accurate. Unlike the mount command, the kernel makes no distinction between bind mounts and normal mounts. This is evident by the fact that you can mount a device, bind mount from that device, and then unmount the original mount. The default behavior of df in this case is to simply pick the mounted directory for a device that is the shortest since it has no other information to go on from /proc/mounts. * Theoretically df, mount and a number of other commands could be modified to run ioctl commands to determine if the mount is from a root inode of the mounted filesystem to determine preference, but that is really more of an upstream exercise. Original bug. Depending on mount path length df sometimes prioritizes showing bind mounts over real mounts for example. $ mount 192.168.1.2:/raid on /raid type nfs (rw,nosuid,nodev,noexec,vers=4,addr=192.168.1.2,clientaddr=192.168.1.3) /dev/sdc5 on /data type ext4 (rw) /data/a on /a type none (rw,bind) /raid/temp on /b type none (rw,bind) $df Filesystem 1K-blocks Used Available Use% Mounted on /data/a 449830616 229975284 196982196 54% /a /raid/temp 7752072192 5581343744 1780023296 76% /b I'd expect to see the real mount prioritized over the bind mount. Like so. $df Filesystem 1K-blocks Used Available Use% Mounted on /dev/sdc5449830616 229975284 196982196 54% /data 192.168.1.2:/raid 7752072192 5581438976 1779929088 76% /raid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1432871/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 749767] Re: Menu bar - Ugly global menu behaviour with fullscreen window
*** This bug is a duplicate of bug 591189 *** https://bugs.launchpad.net/bugs/591189 ** This bug has been marked a duplicate of bug 591189 Manage the fullscreen application case -- 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/749767 Title: Menu bar - Ugly global menu behaviour with fullscreen window Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in indicator-appmenu package in Ubuntu: Triaged Status in unity package in Ubuntu: Triaged Bug description: Binary package hint: unity Make a window fullscreen (so that it covers the menu bar) and press F10. It is possible to use and navigate the menu bar using the keyboard, but because the menu bar itself is hidden all you see are floating menus with no titles to tell you where they come from. Desired Resolution: - Opening the app menus when in full screen mode (either by pressing ALT or F10) should cause the top bar to temporally slide down over the top of the full screen application. - After the user selects a action from any of the menus, the top bar and associated menus should slide back off the screen. - Pressing ALT or F10 a second time should close the menu, and also cause the top bar to slide back off the screen. - Pressing ESC should close the menu, and also cause the top bar to slide back off the screen. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/749767/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488540] [NEW] Right clicks go through popovers
Public bug reported: When displaying e.g. an ActionSelectionPopover (but this is valid for generic Popovers too), clicking anywhere outside of the popover will dismiss it by default. A left-click inside the popover will typically trigger the action under the cursor. But a right-click is not intercepted and goes through the popover, to be processed by whatever is below it. I would tend to think that this is unwanted behaviour in the general case. ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1488540 Title: Right clicks go through popovers Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: When displaying e.g. an ActionSelectionPopover (but this is valid for generic Popovers too), clicking anywhere outside of the popover will dismiss it by default. A left-click inside the popover will typically trigger the action under the cursor. But a right-click is not intercepted and goes through the popover, to be processed by whatever is below it. I would tend to think that this is unwanted behaviour in the general case. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1488540/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1487620] Re: wireless treats driver failure as network security refusal
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public ** Tags added: vivid -- 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/1487620 Title: wireless treats driver failure as network security refusal Status in network-manager package in Ubuntu: New Bug description: I've a Lenovo 585 with Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter - this combination leads to frequent driver failures (sudden component shutdowns) with sound and network hardware being the most likely to temporarily abort. (this isn't the first laptop I've seen this problem on either) Every time the hardware crashes and resets, network-manager treats this as a security abort and asks (erroneously) for network credentials. a: this disrupts all running program and puts up a modal dialogue b: this is unnecessary, because above. c: this is a security risk because it will try (under normal circumstances) to hop networks until it finds an open one, and this can put the unit into a secure vulnerable state. I'm happy to help provide more info - this bug hits me anywhere up to several times an hour. recommend : this is a security risk / serious / blocking (fix asap) bug. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: network-manager 0.9.10.0-4ubuntu15.1 ProcVersionSignature: Ubuntu 3.19.0-26.28-generic 3.19.8-ckt4 Uname: Linux 3.19.0-26-generic x86_64 NonfreeKernelModules: fglrx wl ApportVersion: 2.17.2-0ubuntu1.3 Architecture: amd64 CurrentDesktop: KDE Date: Fri Aug 21 14:20:55 2015 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2013-09-28 (692 days ago) InstallationMedia: Linux Mint 15 "Olivia" - Release amd64 (20130520) IpRoute: default via 10.253.0.1 dev wlan0 proto static metric 1024 1.1.1.1 via 10.253.0.1 dev wlan0 proto dhcp metric 10 10.253.0.0/16 dev wlan0 proto kernel scope link src 10.253.0.20 169.254.0.0/16 dev wlan0 scope link metric 1000 192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATEDBUS-PATH CONNECTION CON-UUID CON-PATH wlan0 wifi connected/org/freedesktop/NetworkManager/Devices/2 IUGO_STAFF 25f36dd0-8cfa-4336-91a4-2ac49e7c3b4d /org/freedesktop/NetworkManager/ActiveConnection/7 eth0ethernet unavailable /org/freedesktop/NetworkManager/Devices/1 -- ---- lo loopback unmanaged/org/freedesktop/NetworkManager/Devices/0 -- ---- virbr0-nic tap unmanaged/org/freedesktop/NetworkManager/Devices/3 -- ---- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1487620/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488470] Re: Ctrl+W shortcut non functional on blank tab after closing a blank tab
** Branch linked: lp:~uriboni/webbrowser-app/reset-focus-tab-change -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1488470 Title: Ctrl+W shortcut non functional on blank tab after closing a blank tab Status in webbrowser-app package in Ubuntu: Confirmed Bug description: Steps to reproduce (on a desktop): - launch the browser - press Ctrl+T twice in a row to open two new blank tabs - press Ctrl+W, this closes the second blank tab - press Ctrl+W again Expected result: this closes the first blank tab Current result: nothing happens To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1488470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1488555] [NEW] Xorg crash
Public bug reported: Xorg crashes and sends me back to the login screen when using Alt+tab to switch between windows. This doesn't happen every time I do it, but quite often (once or twice a day). Details of my system follow: Ubuntu 14.04.3 LTS compiz: Installed: 1:0.9.11.3+14.04.20150313-0ubuntu1 Candidate: 1:0.9.11.3+14.04.20150313-0ubuntu1 Version table: *** 1:0.9.11.3+14.04.20150313-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.11+14.04.20140409-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 Uname: Linux 3.17.0-031700-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 25 10:03:12 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:054d] InstallationDate: Installed on 2014-05-08 (473 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) MachineType: Dell Inc. XPS L421X ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.17.0-031700-generic root=UUID=727c-f0ea-4ee7-afd9-626e5597fb5d ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/07/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 0X86WT dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A13 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd12/07/2012:svnDellInc.:pnXPSL421X:pvrA13:rvnDellInc.:rn0X86WT:rvrA00:cvnDellInc.:ct8:cvrA13: dmi.product.name: XPS L421X dmi.product.version: A13 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Aug 25 10:02:08 2015 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id4158 vendor AUO xserver.version: 2:1.15.1-0ubuntu2.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 crash trusty ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1488555 Title: Xorg crash Status in xorg package in Ubuntu: New Bug description: Xorg crashes and sends me back to the login screen when using Alt+tab to switch between windows. This doesn't happen every time I do it, but quite often (once or twice a day). Details of my system follow: Ubuntu 14.04.3 LTS compiz: Installed: 1:0.9.11.3+14.04.20150313-0ubuntu1 Candidate: 1:0.9.11.3+14.04.20150313-0ubuntu1 Version table: *** 1:0.9.11.3+14.04.20150313-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:0.9.11+14.04.20140409-0ubuntu1 0 500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 Uname: Linux 3.17.0-031700-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue Aug 25 10:03:12 2015 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller]) Subsys
Re: [Touch-packages] [Bug 891210] Re: Dash - dash search should catch keyboard events immediately, not after UI is loaded and displayed
I can't reproduce now. -- 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/891210 Title: Dash - dash search should catch keyboard events immediately, not after UI is loaded and displayed Status in Ayatana Design: Fix Committed Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: Once we become expert at using our machines, the delay between tapping the Super key and starting to type results is short, and the computer lags behind. I can hit Super, and start typing the name of a program, and the first few keys are lost because the search field in the Dash didn't appear until after I started typing. That ruins the search, and I must start over. I haven't seen the source code, but surely the the UI isn't cheap to load, and even beginning to do that should be a step after starting to catch key events in a buffer to be replayed after the UI is up. The UI having been displayed must not be a prerequisite for catching the letters of the thing I'm searching for. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/891210/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
