[Touch-packages] [Bug 1397483] Re: Unity restores windows to random workspaces on system resume
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1397483 Title: Unity restores windows to random workspaces on system resume Status in unity package in Ubuntu: Confirmed Bug description: When I suspend and resume my latop, my windows, which were originally all in one workspace, are restored to different workspaces (apparently at random). For windows not in the current workspace after resume, the unity launcher indicates that they are running, but clicking on them has no effect (it doesn't bring the window to the foreground). These windows also do not appear in the task switcher so you can't switch to them. If I have workspaces enabled, this is annoying but can be manually corrected by showing all workspaces and dragging the windows to the current workspace. If I have workspaces disabled, the windows on the disabled workspaces cannot be accessed at all. I would expect the windows to be restored to the same workspace they were in before suspend (especially if workspaces are disabled), and even if this were not the case, clicking on their icon in the launcher should display them as normal. IIRC this is an issue in Ubuntu 14.04 as well as in Ubuntu 14.10. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.18.0-031800rc6-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Nov 29 10:35:31 2014 InstallationDate: Installed on 2014-11-26 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1397483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400575] Re: sed segfaults on L command with long address lengths
Jodie Cunningham, thank you for reporting this bug and helping make Ubuntu better. This is reproducible as per https://bugs.launchpad.net/ubuntu/+source/sed/+bug/1400611 . Hence, the issue you are reporting is an upstream one. Could you please report this problem to them by e-mailing bonz...@gnu.org CC bug-...@gnu.org as per the man page? Thank you for your understanding. ** Changed in: sed (Ubuntu) Importance: Undecided = Medium ** Changed in: sed (Ubuntu) Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sed in Ubuntu. https://bugs.launchpad.net/bugs/1400575 Title: sed segfaults on L command with long address lengths Status in sed package in Ubuntu: Triaged Bug description: To reproduce, run: sed 'L22' d These do not segfault: sed 'L2' d sed 'L2' d I do not have any expected behavior for this as it was just found by the fuzzer AFL. System is AMD64 Distributor ID: Ubuntu Description: Ubuntu 14.04.1 LTS Release: 14.04 Codename: trusty sed: Installed: 4.2.2-4ubuntu1 Candidate: 4.2.2-4ubuntu1 Version table: *** 4.2.2-4ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sed/+bug/1400575/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397483] Re: Unity restores windows to random workspaces on system resume
This was happening to me, so I disabled Workspaces. It has not stopped the issue. Windows still up and move after suspend, only now to get them back I have to enable then disable Workspaces. After re-disabling windows then reappear. -- 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/1397483 Title: Unity restores windows to random workspaces on system resume Status in unity package in Ubuntu: Confirmed Bug description: When I suspend and resume my latop, my windows, which were originally all in one workspace, are restored to different workspaces (apparently at random). For windows not in the current workspace after resume, the unity launcher indicates that they are running, but clicking on them has no effect (it doesn't bring the window to the foreground). These windows also do not appear in the task switcher so you can't switch to them. If I have workspaces enabled, this is annoying but can be manually corrected by showing all workspaces and dragging the windows to the current workspace. If I have workspaces disabled, the windows on the disabled workspaces cannot be accessed at all. I would expect the windows to be restored to the same workspace they were in before suspend (especially if workspaces are disabled), and even if this were not the case, clicking on their icon in the launcher should display them as normal. IIRC this is an issue in Ubuntu 14.04 as well as in Ubuntu 14.10. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 Uname: Linux 3.18.0-031800rc6-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sat Nov 29 10:35:31 2014 InstallationDate: Installed on 2014-11-26 (2 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1397483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1393466] Re: [webapp-container] user agent override param does not work
** Branch linked: lp:ubuntu/vivid-proposed/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/1393466 Title: [webapp-container] user agent override param does not work Status in Web Browser App: In Progress Status in webbrowser-app package in Ubuntu: New Bug description: One can specify using a command line option what the user agent for a given container session is. It does not currently works for the first http request. There is a race in the ubuntu webview component between the time the webcontext is created (with the default UA), the time the URL is set (and picked up by Oxide), and the time the new user agent is pull from the webview override using getUserAgent(), To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1393466/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1362161] Re: Overview needs visual improvements
We don't have dash overview anymore like it is described in this bug. ** Changed in: unity8 (Ubuntu) Status: Triaged = Won't Fix -- 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/1362161 Title: Overview needs visual improvements Status in unity8 package in Ubuntu: Won't Fix Bug description: We got design feedback on the overview, see below with my replies, will post more as I know more: *All Tab* * *Rounded Corners* - The rounded corners of the cards themselves look more like the Ubuntu bezier curve. These should be standard rounded edges. As a point of reference, these appear to be correct on the 'Favourites' tab. That's because they're actually images of the same size as the dash, scaled down, so the radius looks smaller. We'll try changing the radius to small and resolve the scaling issue. * *Aspect Ratio *- This is incorrect. Currently the cards are too tall in this tab. Agreed, we need to override aspect ratio to be that of the dash. * *Shadows *- These cards shouldn't have any inner or drop shadows. Same issue as with corners above. We should be able to disable the shadows though. * *Label Overlay *- For the dark overlays - these should be 15% black. Everywhere? We allowed for scopes to override this explicitly based on the visual designs. * *Text Labels*: The labels should be vertically and horizontally centered in the overlay. We have a fix for the horizontal alignment, vertical, however, is not something that the toolkit allowed. Should we always make them centered in the overlay if there's only the title (across the whole dash, not just in overview)? * *Dimensions / Margins *- The cards also seem very tight on the BQ phone. I guess this is because it's a smaller viewport. Hopefully updating the aspect ratio etc… will help clean this up a little. It's the same 40GU width. We did not, however, apply the latest margins and sizes from the dash redlines you prepared, yet. It's all still as spec'ed out in the dash toolkit spec. *Favourites Tab* * These are a lot more accurate in general :)... * *Overlays* - The overlay should be taller to match the designs (5GU). The overlay is defined to be as high as the maximum header + 1GU padding. Meaning in this case it's two lines of title text + 2GU. Again, that's the case across the dash, if we wanted to change it. * *Text Labels* - Again the text label needs to be centered horizontally and vertically (regardless of whether or not they're one or two lines long). See above. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140825.3-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-10.15-generic 3.16.1 Uname: Linux 3.16.0-10-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.6-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Aug 27 14:46:48 2014 SourcePackage: unity8 SystemImageInfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1362161/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400626] [NEW] Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
Public bug reported:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the documentation
is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
** Affects: libdrm (Ubuntu)
Importance: High
Assignee: Maarten Lankhorst (mlankhorst)
Status: In Progress
** Affects: x11proto-core (Ubuntu)
Importance: Undecided
Status: New
** Affects: x11proto-fonts (Ubuntu)
Importance: Undecided
Status: New
** Affects: xorg (Ubuntu)
Importance: High
Assignee: Maarten Lankhorst (mlankhorst)
Status: In Progress
** Affects: xtrans (Ubuntu)
Importance: High
Assignee: Maarten Lankhorst (mlankhorst)
Status: In Progress
** Affects: libdrm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: x11proto-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: x11proto-fonts (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: xorg (Ubuntu Trusty)
Importance: Undecided
Status: New
** Affects: xtrans (Ubuntu Trusty)
Importance: Undecided
Status: New
** Summary changed:
- Please backport some xorg packages for 14.04.2
+ Please backport xtrans, libdrm, x11proto-{fonts,core} packages for 14.04.2
** Also affects: libdrm (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libdrm (Ubuntu)
Status: New = In Progress
** Changed in: libdrm (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
** Changed in: libdrm (Ubuntu)
Importance: Undecided = High
** Also affects: xtrans (Ubuntu)
Importance: Undecided
Status: New
** Changed in: xtrans (Ubuntu)
Assignee: (unassigned) = Maarten Lankhorst (mlankhorst)
** Changed in: xtrans (Ubuntu)
Importance: Undecided = High
** Changed in: xtrans (Ubuntu)
Status: New = In Progress
** Also affects: x11proto-fonts (Ubuntu)
Importance: Undecided
Status: New
** Also affects: x11proto-core (Ubuntu)
Importance: Undecided
Status: New
** Also affects: xorg (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: libdrm (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: x11proto-core (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: x11proto-fonts (Ubuntu Trusty)
Importance: Undecided
Status: New
** Also affects: xtrans (Ubuntu Trusty)
Importance: Undecided
Status: New
--
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/1400626
Title:
Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
14.04.2
Status in libdrm package in Ubuntu:
In Progress
Status in x11proto-core package in Ubuntu:
New
Status in x11proto-fonts package in Ubuntu:
New
Status in xorg package in Ubuntu:
In Progress
Status in xtrans package in Ubuntu:
In Progress
Status in libdrm source package in Trusty:
New
Status in x11proto-core source package in Trusty:
New
Status in x11proto-fonts source package in Trusty:
New
Status in xorg source package in Trusty:
New
Status in xtrans source package in Trusty:
New
Bug description:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
[Touch-packages] [Bug 1362640] Re: Remove qtwebkit from touch image
** Tags removed: ww51 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1362640 Title: Remove qtwebkit from touch image Status in the base for Ubuntu mobile products: Confirmed Status in Cordova Ubuntu: Triaged Status in Web Browser App: Triaged Status in ubuntu-touch-meta package in Ubuntu: In Progress Bug description: The argument to remove this is based on the following: The qtwebkit webview is deprecated for our sdk and we will not be supporting it long term We are supporting an Oxide/Chromium solution for the Ubuntu.Webview This was done largely for security reasons The qtwebkit package is large and we would like to reduce image and install size We want to discourage app devs from using this api any longer, the review tools have indicated this for several months To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1362640/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319582] Re: emulator: 'Failed to start RenderThread' after opening/closing applications
** Changed in: android (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) ** Changed in: qtubuntu (Ubuntu) Assignee: (unassigned) = Ricardo Mendoza (ricmm) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1319582 Title: emulator: 'Failed to start RenderThread' after opening/closing applications Status in Mir: Triaged Status in android package in Ubuntu: Confirmed Status in qtubuntu package in Ubuntu: New Bug description: Using: ubuntu-emulator 0.2+14.10.20140429.1-0ubuntu1 ubuntu-emulator-runtime 20140501-2310-0ubuntu3 Emulator starts fine, but after a few opening/closing apps in a row (a bunch of times, at least 20), emulator gives the 'Failed to start RenderThread' error. At that point the emulator can't do much more, and you need to abort and run it again. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1319582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397065] Re: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Not sure if this helps but this is the error I get with this problem E: Internal Error, No file name for dbus:amd64 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1397065 Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in dbus package in Ubuntu: Confirmed Bug description: I don't know what it is, my computer said to report the bug and I did it. ProblemType: Package DistroRelease: Ubuntu 14.10 Package: dbus 1.8.8-1ubuntu2.1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Thu Nov 27 18:32:47 2014 DuplicateSignature: package:dbus:1.8.8-1ubuntu2.1:subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2014-03-08 (264 days ago) InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release i386 (20131016.1) SourcePackage: dbus Title: package dbus 1.8.8-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to utopic on 2014-09-27 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1397065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400372] Re: keyboard re-appears in gmail after dismissing
I can reliably reproduce the issue, tentatively confirming for both oxide and ubuntu-keyboard until we investigate and find out where the issue lies. ** Tags added: osk ** Changed in: oxide Status: New = Confirmed ** Changed in: ubuntu-keyboard Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1400372 Title: keyboard re-appears in gmail after dismissing Status in Oxide Webview: Confirmed Status in Ubuntu Keyboard: Confirmed Status in ubuntu-keyboard package in Ubuntu: New Bug description: latest rtm build on krillin: - open gmail webapp - click on search field underneath the Inbox button - type in a search string into the field that will yeild results - press the return key on the keyboard to execute the search - search results are displayed and the keyboard remains visible - now manually swipe the keyboard close in order to scroll through the search results Expected results: - keyboard should stay closed while scrolling Actual results: - keyboard becomes visible when start scrolling and can't get it to disappear Guessing the text field must still have focus and is somehow causing the keyboard to reappear when scrolling, but this shouldn't occur To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1400372/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400393] Re: wrong keyboard layout
localectl has a n/a layout info, looks like systemd is built with --disable-vconsole and #debian-systemd comment suggested that console- common is doing the config ... not sure what change between upstart and systemd boots in that context then? -- 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/1400393 Title: wrong keyboard layout Status in systemd package in Ubuntu: New Bug description: Using systemd as init on current vivid, the keyboard layout doesn't respect the configuration from /etc/default/keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400393/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400449] Re: qmltestrunner crashed with SIGABRT during unity8 tests
** Package changed: qtdeclarative-opensource-src (Ubuntu) = unity8 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1400449 Title: qmltestrunner crashed with SIGABRT during unity8 tests Status in unity8 package in Ubuntu: Triaged Bug description: Running testDash ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-dev-tools 5.3.2-3ubuntu2 Uname: Linux 3.18.0-031800rc4-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Dec 8 14:45:28 2014 Disassembly: = 0x7f84affa5e37: Cannot access memory at address 0x7f84affa5e37 ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmltestrunner LocalLibraries: /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/libs/UbuntuGestures/libUbuntuGestures.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/mocks/Unity/libFakeUnityQml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/utils/modules/Unity/Test/libUnityTestQml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/mocks/Unity/DashCommunicator/libMockDashCommunicator-qml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins/Dash/libDash-qml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins/Ubuntu/Gestures/libUbuntuGesturesQml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins/Utils/libUtils-qml.so ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmltestrunner -input /home/username/Pobrane/unity8-8.02+15.04.20141208/tests/qmltests/Dash/tst_Dash.qml -import /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins -import /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/utils/modules -import /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/mocks -o /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/testDash.xml,xunitxml -o -,txt Signal: 6 SourcePackage: qtdeclarative-opensource-src Stacktrace: #0 0x7f84affa5e37 in ?? () No symbol table info available. #1 0x in ?? () No symbol table info available. StacktraceTop: ?? () ?? () Title: qmltestrunner crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1400449/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400626] Re: Please backport xtrans, libdrm, x11proto-{fonts, core} packages for 14.04.2
** Tags added: lts-utopic trusty
** Description changed:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
- x11proto-core
+ x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
+
+ xorg needs to be slightly updated, to allow xserver-xorg to provide the
+ unrenamed lts-utopic, and to allow xorg to be installed with the renamed
+ xorg-server.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1400626
Title:
Please backport xtrans, libdrm, x11proto-{fonts,core} packages for
14.04.2
Status in libdrm package in Ubuntu:
In Progress
Status in x11proto-core package in Ubuntu:
New
Status in x11proto-fonts package in Ubuntu:
New
Status in xorg package in Ubuntu:
In Progress
Status in xtrans package in Ubuntu:
In Progress
Status in libdrm source package in Trusty:
New
Status in x11proto-core source package in Trusty:
New
Status in x11proto-fonts source package in Trusty:
New
Status in xorg source package in Trusty:
New
Status in xtrans source package in Trusty:
New
Bug description:
In order to upload the new xorg-server we need to backport the following
packages from utopic:
libdrm
x11proto-core
x11proto-fonts
xtrans
libdrm 2.4.52-1-2.4.56-1 seems to have the following changes:
- Hides private symbols from all libdrm libraries
- fixes MSAA on Hawaii (radeon).
- Adds cherryview pci-ids (intel).
- Makes libdrm-nouveau threadsafe with concurrent access to the drm fd.
- Fixes to exynos and freedreno.
- Enables building libdrm-freedreno1 and libdrm-exynos1
x11proto-core's main change appears to be changing from the 'pointer' type to
'void *':
https://launchpadlibrarian.net/173873109/x11proto-core_7.0.24-1_7.0.26-1.diff.gz
x11proto-fonts' main change is the same as x11proto-core, but the
documentation is reformatted too:
https://launchpadlibrarian.net/173873038/x11proto-fonts_2.1.2-1_2.1.3-1.diff.gz
xtrans seems to have 2 minor changes, increase default unix pipe size and add
support for systemd socket activation:
https://launchpadlibrarian.net/173873112/xtrans_1.3.2-1_1.3.4-1.diff.gz
xorg needs to be slightly updated, to allow xserver-xorg to provide
the unrenamed lts-utopic, and to allow xorg to be installed with the
renamed xorg-server.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1400626/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1320990] Re: [xorg-edgers] BOINC can't find CUDA driver with xorg-edgers packages
fix committed in debian anonscm.debian.org/gitweb/?p=pkg- boinc/boinc.git;a=commitdiff;h=be4e9eb will be fixed in boinc in the next few months. But I think this isn't a boinc bug -- 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/1320990 Title: [xorg-edgers] BOINC can't find CUDA driver with xorg-edgers packages Status in xorg package in Ubuntu: Confirmed Bug description: Running Ubuntu 14.04 with Xorg Edgers and a Geforce 750 Ti. Installed nvidia-337,-dev,-uvm, libcuda1-337. With these packages from xorg-edgers everything graphical/game/etc wise runs perfectly, except for CUDA though BOINC. When installed directly from nvidia's website CUDA worked fine in BOINC. Now BOINC just says missing GPU type NVIDIA (generally it looks for CUDA, but OpenCL doesn't appear to work either). I have not had it working on any previous version of xorg-edgers (just got the GPU recently). ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 337.19 Tue Apr 29 19:58:58 PDT 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) ApportVersion: 2.14.1-0ubuntu3.1 Architecture: amd64 CurrentDesktop: Unity Date: Mon May 19 15:08:56 2014 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-337, 337.19, 3.13.0-24-generic, x86_64: installed nvidia-337-uvm, 337.19, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:3751] InstallationDate: Installed on 2014-04-27 (21 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) LightdmGreeterLog: ** (lightdm-gtk-greeter:3637): WARNING **: Failed to load user image: Failed to open file '/home/bryan/.face': No such file or directory (lightdm-gtk-greeter:3637): Gdk-WARNING **: lightdm-gtk-greeter: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. LightdmGreeterLogOld: ** (lightdm-gtk-greeter:2089): WARNING **: Failed to load user image: Failed to open file '/home/bryan/.face': No such file or directory g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting. MachineType: BIOSTAR Group TA890GXE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=a391c643-63e1-42cd-938c-6565a0fad31f ro quiet splash SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/30/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080015 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: TA890GXE dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/30/2011:svnBIOSTARGroup:pnTA890GXE:pvr:rvnBIOSTARGroup:rnTA890GXE:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.name: TA890GXE dmi.sys.vendor: BIOSTAR Group version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.54+git20140505.5126fcb2-0ubuntu0ricotz~trusty version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0~git20140515.67041874-0ubuntu0sarvatt~trusty version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0~git20140515.67041874-0ubuntu0sarvatt~trusty version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.99+git20140505.be1469cc-0ubuntu0ricotz~trusty version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.911+git20140507.18416b51-0ubuntu0ricotz~trusty version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10+git20140220.480f0998-0ubuntu0sarvatt xserver.bootTime: Sat May 17 09:38:52 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1320990/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post
[Touch-packages] [Bug 1400580] Re: Color Inverse on display. Toggle Negative Image
Indeed, we should build accessibility features in as early as possible. I wonder if this should happen in unity8, or maybe this should be a function of Mir itself? ** Changed in: unity8 (Ubuntu) Status: New = Confirmed ** Also affects: mir 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/1400580 Title: Color Inverse on display. Toggle Negative Image Status in Mir: New Status in unity8 package in Ubuntu: Confirmed Bug description: I would like to see a feature that allowed Unity8, to easily inverse the desktop colors. To be able to easily turn on and off a negative (inverse) display of the desktop. For now, it can be done with X (xcalib). It would be nice to see Unity8 do this natively, instead of Ubuntu users needing this feature hoping, X-11 support will always be available. This is a feature I use, due to impaired eye-sight. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1400580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1255403] [NEW] Access Prompt pop-up
You have been subscribed to a public bug: 1) Ubuntu 13.10 2) gnome-keyring 3.2.8-0ubuntu1.1,automatic 3) no pop-up window 4) pop-up window asking for password Since an update about two weeks ago, a window labeled Access Prompt has begun appearing upon login. It requests the password of the account which has just logged on, and has a tick box to save to the keyring. The password is entered, but it reports that it is an invalid password. When cancel is selected, the system seems to work as before. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 27 00:23:48 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-30 (149 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to saucy on 2013-10-19 (38 days ago) ** Affects: gcr (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug saucy -- Access Prompt pop-up https://bugs.launchpad.net/bugs/1255403 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399007] Re: Ringtone doesn't apply to new selected ringtone
This bug was fixed in the package telephony-service - 0.1+15.04.20141205 ~rtm-0ubuntu1 --- telephony-service (0.1+15.04.20141205~rtm-0ubuntu1) 14.09; urgency=low [ Bill Filler ] * fix ringtone change not getting applied until restart (LP: #1399007) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 05 Dec 2014 18:07:11 + ** Changed in: telephony-service (Ubuntu RTM) Status: In Progress = Fix Released -- 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/1399007 Title: Ringtone doesn't apply to new selected ringtone Status in Telephony Service: In Progress Status in telephony-service package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu RTM: Fix Released Bug description: As reported in barajas bug: https://bugs.launchpad.net/barajas/+bug/139 Listed here to track for our project To manage notifications about this bug go to: https://bugs.launchpad.net/telephony-service/+bug/1399007/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388999] Re: gdb is realy slow starting debugging.
** Branch linked: lp:ubuntu/vivid-proposed/gdb -- 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/1388999 Title: gdb is realy slow starting debugging. Status in GNU Debugger: Unknown Status in gdb package in Ubuntu: Triaged Bug description: On binaries with a lot of symbols a massive performance degradation has happened between 14.04 and 14.10 I have bisected the gdb performance degradation to this gdb commit commit 5840bf271c87c3fc14739173fdc91c6a14057130 (refs/bisect/bad) Author: H.J. Lu hjl.to...@gmail.com Date: Wed Jul 16 17:16:24 2014 Properly match PLT entry against .got.plt relocation Relocations against .got.plt section may not be in the same order as entries in PLT section. It is incorrect to assume that the Ith reloction index against .got.plt section always maps to the (I + 1)th entry in PLT section. This patch matches the .got.plt relocation offset/index in PLT entry against the index in .got.plt relocation table. It only checks R_*_JUMP_SLOT and R_*_IRELATIVE relocations. It ignores R_*_TLS_DESC and R_*_TLSDESC relocations since they have different PLT entries. bfd/ PR binutils/17154 * elf32-i386.c (elf_i386_plt_sym_val): Only match R_*_JUMP_SLOT and R_*_IRELATIVE relocation offset with PLT entry. * elf64-x86-64.c (elf_x86_64_plt_sym_val): Likewise. (elf_x86_64_plt_sym_val_offset_plt_bnd): New. (elf_x86_64_get_synthetic_symtab): Use it. ld/testsuite/ PR binutils/17154 * ld-ifunc/pr17154-i386.d: New file. * ld-ifunc/pr17154-x86-64.d: Likewise. * ld-ifunc/pr17154-x86.s: Likewise. * ld-x86-64/bnd-ifunc-2.d: Likewise. * ld-x86-64/bnd-ifunc-2.s: Likewise. * ld-x86-64/mpx.exp: Run bnd-ifunc-2. * ld-x86-64/tlsdesc-nacl.pd: Updated. * ld-x86-64/tlsdesc.pd: Likewise. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: gdb 7.8-1ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-lowlatency 3.16.4 Uname: Linux 3.16.0-24-lowlatency x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: KDE Date: Mon Nov 3 23:27:53 2014 InstallationDate: Installed on 2014-07-11 (115 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) SourcePackage: gdb UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdb/+bug/1388999/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1255403] Re: Access Prompt pop-up
This looks very similar to bug 1044549. ** Package changed: gnome-keyring (Ubuntu) = gcr (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1255403 Title: Access Prompt pop-up Status in gcr package in Ubuntu: New Bug description: 1) Ubuntu 13.10 2) gnome-keyring 3.2.8-0ubuntu1.1,automatic 3) no pop-up window 4) pop-up window asking for password Since an update about two weeks ago, a window labeled Access Prompt has begun appearing upon login. It requests the password of the account which has just logged on, and has a tick box to save to the keyring. The password is entered, but it reports that it is an invalid password. When cancel is selected, the system seems to work as before. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: gnome-keyring 3.8.2-0ubuntu3.1 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Wed Nov 27 00:23:48 2013 EcryptfsInUse: Yes InstallationDate: Installed on 2013-06-30 (149 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-keyring UpgradeStatus: Upgraded to saucy on 2013-10-19 (38 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1255403/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400186] Re: [VGN-A690, Realtek ALC260] No sound at all internal speakers and headphone (Green out)
any reason to change headphone to line out ? you have to send email to the author 8.115834] sound hdaudioC0D0: autoconfig: line_outs=1 (0x10/0x0/0x0/0x0/0x0) type:line [ 18.115842] sound hdaudioC0D0:speaker_outs=1 (0xf/0x0/0x0/0x0/0x0) [ 18.115845] sound hdaudioC0D0:hp_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 18.115848] sound hdaudioC0D0:mono: mono_out=0x0 [ 18.115851] sound hdaudioC0D0:dig-out=0x18/0x0 [ 18.115854] sound hdaudioC0D0:inputs: [ 18.115857] sound hdaudioC0D0: Mic=0x12 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1400186 Title: [VGN-A690, Realtek ALC260] No sound at all internal speakers and headphone (Green out) Status in alsa-driver package in Ubuntu: Incomplete Bug description: I have tried using different options in /etc/modprobe.d/alsa- base.conf. Without probe_mask=1 it also detects a Conexant modem. I just discovered there is sound output from the rear A/V Out port of the laptop, but there is popping whether or not audio is playing. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: beat 1823 F pulseaudio CurrentDesktop: XFCE CurrentDmesg: [ 42.213440] systemd-logind[805]: Failed to start user service: Unknown unit: user@1000.service [ 42.220873] systemd-logind[805]: New session c1 of user beat. [ 42.220901] systemd-logind[805]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. Date: Sun Dec 7 20:10:30 2014 InstallationDate: Installed on 2014-12-06 (1 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: beat 1823 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [VGN-A690, Realtek ALC260, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0080F2 dmi.chassis.asset.tag: 8S4Lf716540bab4851f0 dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0080F2:bd03/14/2005:svnSonyCorporation:pnVGN-A690:pvrC00071GZ:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-A690 dmi.product.version: C00071GZ dmi.sys.vendor: Sony Corporation mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-12-07T18:28:32.827133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1400186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400652] [NEW] Access Prompt inappropriately presented as an app
Public bug reported: gcr 3.10.1-1, Ubuntu 14.04 1. Launch Ubuntu Software Center. 2. Search for access. What you see: Access Prompt appears as an installed app that can be removed. What you should see: Access Prompt should not be shown as an app at all. It's a crypto library. This bug contributed to the confusion that led to http://askubuntu.com/questions/557223/what-legitimate-legal-use-does- the-application-access-prompt-have. ** Affects: gcr (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcr in Ubuntu. https://bugs.launchpad.net/bugs/1400652 Title: Access Prompt inappropriately presented as an app Status in gcr package in Ubuntu: New Bug description: gcr 3.10.1-1, Ubuntu 14.04 1. Launch Ubuntu Software Center. 2. Search for access. What you see: Access Prompt appears as an installed app that can be removed. What you should see: Access Prompt should not be shown as an app at all. It's a crypto library. This bug contributed to the confusion that led to http://askubuntu.com/questions/557223/what-legitimate-legal-use-does- the-application-access-prompt-have. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcr/+bug/1400652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400186] Re: [VGN-A690, Realtek ALC260] No sound at all internal speakers and headphone (Green out)
how about the internal mic ? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1400186 Title: [VGN-A690, Realtek ALC260] No sound at all internal speakers and headphone (Green out) Status in alsa-driver package in Ubuntu: Incomplete Bug description: I have tried using different options in /etc/modprobe.d/alsa- base.conf. Without probe_mask=1 it also detects a Conexant modem. I just discovered there is sound output from the rear A/V Out port of the laptop, but there is popping whether or not audio is playing. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: beat 1823 F pulseaudio CurrentDesktop: XFCE CurrentDmesg: [ 42.213440] systemd-logind[805]: Failed to start user service: Unknown unit: user@1000.service [ 42.220873] systemd-logind[805]: New session c1 of user beat. [ 42.220901] systemd-logind[805]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. Date: Sun Dec 7 20:10:30 2014 InstallationDate: Installed on 2014-12-06 (1 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: beat 1823 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [VGN-A690, Realtek ALC260, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0080F2 dmi.chassis.asset.tag: 8S4Lf716540bab4851f0 dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0080F2:bd03/14/2005:svnSonyCorporation:pnVGN-A690:pvrC00071GZ:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-A690 dmi.product.version: C00071GZ dmi.sys.vendor: Sony Corporation mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-12-07T18:28:32.827133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1400186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355111] Re: newgrp fails with crypt: Invalid argument
** Bug watch added: Red Hat Bugzilla #988184 https://bugzilla.redhat.com/show_bug.cgi?id=988184 ** Also affects: shadow via https://bugzilla.redhat.com/show_bug.cgi?id=988184 Importance: Unknown Status: Unknown -- 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 The Shadow Password File Utilities: 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 1400449] Re: qmltestrunner crashed with SIGABRT during unity8 tests
** Changed in: unity8 (Ubuntu) Status: Triaged = Won't Fix ** Changed in: unity8 (Ubuntu) Status: Won't Fix = 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/1400449 Title: qmltestrunner crashed with SIGABRT during unity8 tests Status in unity8 package in Ubuntu: In Progress Bug description: Running testDash ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-dev-tools 5.3.2-3ubuntu2 Uname: Linux 3.18.0-031800rc4-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Dec 8 14:45:28 2014 Disassembly: = 0x7f84affa5e37: Cannot access memory at address 0x7f84affa5e37 ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmltestrunner LocalLibraries: /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/libs/UbuntuGestures/libUbuntuGestures.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/mocks/Unity/libFakeUnityQml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/utils/modules/Unity/Test/libUnityTestQml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/mocks/Unity/DashCommunicator/libMockDashCommunicator-qml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins/Dash/libDash-qml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins/Ubuntu/Gestures/libUbuntuGesturesQml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins/Utils/libUtils-qml.so ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmltestrunner -input /home/username/Pobrane/unity8-8.02+15.04.20141208/tests/qmltests/Dash/tst_Dash.qml -import /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins -import /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/utils/modules -import /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/mocks -o /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/testDash.xml,xunitxml -o -,txt Signal: 6 SourcePackage: qtdeclarative-opensource-src Stacktrace: #0 0x7f84affa5e37 in ?? () No symbol table info available. #1 0x in ?? () No symbol table info available. StacktraceTop: ?? () ?? () Title: qmltestrunner crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1400449/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390128] Re: [address-book] is stuck on contacts sync dialog becomes unusable
This bug was fixed in the package address-book-app - 0.2+15.04.20141205 ~rtm-0ubuntu1 --- address-book-app (0.2+15.04.20141205~rtm-0ubuntu1) 14.09; urgency=low [ Ubuntu daily release ] * New rebuild forced [ Renato Araujo Oliveira Filho ] * Avoid show online account dialog if the app was called from another app. Close the online account dialog if a new contact get created. (LP: #1390128) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 05 Dec 2014 15:55:11 + ** Changed in: address-book-app (Ubuntu RTM) Status: New = Fix Released -- 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/1390128 Title: [address-book] is stuck on contacts sync dialog becomes unusable Status in Address Book App: Fix Committed Status in the base for Ubuntu mobile products: Confirmed Status in Ubuntu UX bugs: Fix Committed Status in address-book-app package in Ubuntu: Fix Released Status in address-book-app package in Ubuntu RTM: Fix Released Bug description: build 143 To reproduce this bug the address book app has to be launched for the first time. Steps to reproduce 1. wipe your device if necessary 2. launch the address book app and wait until the You have no contacts dialog comes up 3. do not interact with the dialog and navigate away from the app 4. launch the dialer or/and the messaging app 5. open the app spread from the right edge and force close the address book app 6. navigate to dialer (or messaging) app and save a contact from the main view 7. now open the address book again and try to interact with the You have no contacts dialog Expected behaviour: you will either be able to dismiss the dialog or sync contacts Actual behaviour: you won't be able to tap anything or interact with the address book because the dialog is not dismissible. The interesting thing here is that it is possible to access the address book and contacts from the dialer and messaging app but not directly. Marking as Critical because the address book becomes completely unusable even if you restart your device. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1390128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
I've been suffering this bug for months now. Today I noticed some issues with window animations before it happened, and it came to my mind that it might be compiz-related. I killed compiz and the login screen was gone, without losing the unity session. It's the first time that I manage to go back to my session without losing the data. This is a Sony Vaio running Ubuntu 14.04.1 with dual monitor. After that, when the screen lock appeared again, the password field was there. This seems to me a better workaround than unity --replace, if it proves to work consistently. Worth trying it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374082] Re: no API to unlock a specific sim
the attached branches add a capability for the unconfined applications to request unlocking of a specific SIM by name (ofono modem path): $ dbus-send --session --print-reply --dest=com.ubuntu.connectivity1 /com/ubuntu/connectivity1/Private com.ubuntu.connectivity1.Private.UnlockModem string:/ril_0 ** Branch linked: lp:~unity-api-team/indicator-network/unlock- modem-15.04 -- 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/1374082 Title: no API to unlock a specific sim Status in the base for Ubuntu mobile products: Confirmed Status in Network Menu: In Progress Status in indicator-network package in Ubuntu: In Progress Status in indicator-network source package in Utopic: Triaged Status in indicator-network source package in Vivid: In Progress Status in indicator-network package in Ubuntu RTM: In Progress Bug description: In dialer-app on dual sim phones users will be given an option to unlock a specific modem. The current api only supports unlocking all modems at once: UnlockAllModems(). We need a way to invoke the unlock screen to a specific modem, like UnlockModem(objectPath). clients: https://bugs.launchpad.net/messaging-app/+bug/1371661 To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1374082/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399710] Re: no audible warning of high volume level
** Changed in: ubuntu-ux Assignee: (unassigned) = John Lea (johnlea) ** Changed in: ubuntu-ux Assignee: John Lea (johnlea) = (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) = Matthew Paul Thomas (mpt) ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1399710 Title: no audible warning of high volume level Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Incomplete Bug description: Additional to the work done on bug 1373404, I think we need to consider adding an audio warning when the volume crosses the threshold value. The way android works is that the user is asked if they want to allow higher volume levels (they must click ok). Our approach is to just display a visual warning. That's fine (assuming it complies with all legal regs), but it isn't helpful from an accessibility perspective. Obviously folk can hear when levels become painful high, but how about we insert an audible warning when the user crosses the threshold? I'd suggest we do both of the following to indicate an audible warning: 1) Mute (or atleast lower) the currently playing audio streams. 2) Play two beeps in quick succession (at the original volume level prior to mute/lowering). Once the beeps have been played, the volume level will be restored to the appropriate (higher) level. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1399710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355111] Re: newgrp fails with crypt: Invalid argument
Adding tag saucy regarding to reporter observation. ** Tags added: saucy -- 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 The Shadow Password File Utilities: 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 1152692] Re: [SIDESTAGE] no visual hint on sidestage handle to sidestage is draggable
** Changed in: ubuntu-ux Assignee: (unassigned) = Vesa Rautiainen (vesar) -- 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/1152692 Title: [SIDESTAGE] no visual hint on sidestage handle to sidestage is draggable Status in Ubuntu UX bugs: New Status in unity8 package in Ubuntu: Incomplete Bug description: manta #98 sidestage handle should have a visual detail to communicate the draggable affordance. This could be a grab texture, dots or lines similar to window bordered on the desktop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1152692/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1373404] Re: [notification] No warning of high volume level
** Changed in: ubuntu-ux Assignee: (unassigned) = John Lea (johnlea) -- 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/1373404 Title: [notification] No warning of high volume level Status in Ubuntu UX bugs: Fix Committed Status in indicator-sound package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in ubuntu-system-settings package in Ubuntu: Fix Released Status in unity-notifications package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in indicator-sound package in Ubuntu RTM: Fix Released Status in unity-notifications package in Ubuntu RTM: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: The EU has a legal requirement for personal music players to prevent hearing damage. http://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:32009D0490rid=1 Desired resolution: - For RTM the design spec'ed in the following section of the Sound wiki page should be implemented https://wiki.ubuntu.com/Sound#Warnings_.28note:_This_section_should_be_implemented_for_RTM.29 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1373404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398427] Re: Can't use earphone to answer or disconnect a call
** Changed in: ubuntu-ux Assignee: (unassigned) = Matthew Paul Thomas (mpt) ** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: ubuntu-ux Importance: Undecided = High -- 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/1398427 Title: Can't use earphone to answer or disconnect a call Status in the base for Ubuntu mobile products: Confirmed Status in Telephony Service: New Status in Ubuntu UX bugs: Triaged Status in qtmir package in Ubuntu: Fix Released Status in telephony-service package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: New Status in qtmir package in Ubuntu RTM: In Progress Status in telephony-service package in Ubuntu RTM: New Bug description: [Procedures] 1.insert the earphone 2.make a MO call to DUT 3.use the Hook key to answer the call 4.when connected the call use the hook key to disconnect the call [Expect results] earphone hook key can answer and disconnect the call [Actual results] can't answer and disconnect the call [Reproduce] Always To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1398427/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1163412] Re: [gallery app] [visual design] Open albums in album overview tab need visual alignment
Not applicable anymore, project moved on. ** Changed in: ubuntu-ux Assignee: Calum Pringle (calumpringle) = (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) ** Changed in: ubuntu-ux Status: Fix Committed = Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1163412 Title: [gallery app] [visual design] Open albums in album overview tab need visual alignment Status in Ubuntu UX bugs: Won't Fix Status in gallery-app package in Ubuntu: Invalid Bug description: Album overview tab shows uneven margins around photographs in 'open' albums. Margins should be straightened out with transition for launching album. Visual design needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1163412/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372548] Re: Phone field doesn't accept symbols #*()
** Changed in: ubuntu-ux Assignee: (unassigned) = Olga Kemmet (olga-kemmet) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1372548 Title: Phone field doesn't accept symbols #*() Status in Address Book App: Confirmed Status in Ubuntu UX bugs: New Status in address-book-app package in Ubuntu: New Status in ubuntu-keyboard package in Ubuntu: New Status in address-book-app package in Ubuntu RTM: New Status in ubuntu-keyboard package in Ubuntu RTM: New Bug description: The phone field in address book doesn't accept symbols available in the keyboard for phone numbers: #* Test case: - Open Contacts app. - Add a new contact. - Go to Phone number field. - Press + key for 5 seconds and select these symbols: *#() Expected result: - Field accepts symbols as part of a telephone number. Actual result: - Only + symbol is accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1372548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372011] Re: ListItem.Subtitled subText color is too dark with SuruDark
** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1372011 Title: ListItem.Subtitled subText color is too dark with SuruDark Status in Permy: New Status in Ubuntu UX bugs: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: It is hard to read ListItem.Subtitled subText when using the SuruDark theme (or other dark themes). To manage notifications about this bug go to: https://bugs.launchpad.net/permy/+bug/1372011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386208] Re: Purple overflow panel in SuruGradient theme
** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1386208 Title: Purple overflow panel in SuruGradient theme Status in File Manager application for Ubuntu devices: Fix Committed Status in Ubuntu UI Toolkit: Fix Released Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: While testing the new header on trunk, I noticed that the actions on the header are purple. They should be the same colour as the rest of the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1386208/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1398170] Re: [greeter] The greeter and screen rotation
** Changed in: ubuntu-ux Assignee: (unassigned) = John Lea (johnlea) ** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: ubuntu-ux Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1398170 Title: [greeter] The greeter and screen rotation Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: New Bug description: This is basically just a bug to ask a question of the design team: are there plans for rotation support for the greeter? Right now it doesn't really do anything special. I'd guess you don't want it to rotate on a phone factor, but maybe for a tablet. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1398170/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391839] Re: Cannot change boundsBehaviour on Flickable in Expandable
** Changed in: ubuntu-ux Assignee: (unassigned) = Giorgio Venturi (giorgio-venturi) -- 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/1391839 Title: Cannot change boundsBehaviour on Flickable in Expandable Status in Ubuntu UI Toolkit: Incomplete Status in Ubuntu UX bugs: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Right now it's quite unfortunate that some Expandables can be dragged and overshot (Flickable.DragAndOvershootBounds). Could the Expandable expose the boundsBehaviour property or in some other way make this changeable? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1391839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391503] Re: ScrollBar color is not distinctive enough
** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1391503 Title: ScrollBar color is not distinctive enough Status in Ubuntu UX bugs: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Using a MainView with default color, a Flickable and a Scrollbar in it, leaves the scrollbar mostly invisible. You can see it if you look *very* closely, but it's not providing the help/indication it is supposed to. I guess the Scrollbar would need some background color detection and change its color, or, at least provide a color property to allow the developer setting the color. A third option would probably be to expose the ScrollbarStyle in the API so it can be customized to fit the app's design. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1392308] Re: [design] Cannot browse indicators in daylight
** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1392308 Title: [design] Cannot browse indicators in daylight Status in Ubuntu UX bugs: New Status in unity8 package in Ubuntu: New Bug description: While doing GPS tests with the phone in daylight, I found it difficult to open the location indicator, because of the current color scheme. The non-active indicators are too dim to be read. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1392308/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391548] Re: [sdk] + [header]Portuguese words in selection header don't fit
** Changed in: ubuntu-ux Assignee: (unassigned) = Giorgio Venturi (giorgio-venturi) -- 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/1391548 Title: [sdk] + [header]Portuguese words in selection header don't fit Status in Ubuntu UX bugs: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: See http://imgur.com/EZ1lqUI and http://imgur.com/RPRe8Bm Probably this will happen in other languages as well. We need feedback from design to decide how to solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391501] Re: Calendar reminders should mute if phone is muted
** Changed in: ubuntu-ux Assignee: (unassigned) = Giorgio Venturi (giorgio-venturi) -- 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/1391501 Title: Calendar reminders should mute if phone is muted Status in the base for Ubuntu mobile products: New Status in Ubuntu UX bugs: New Status in indicator-datetime package in Ubuntu: New Bug description: Calendar reminders seem to use the alarm role, which means muting your phone does not impact them. It should either use the same role as the ringer, or maybe a completely separate one. This is related to bug #1291458. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: indicator-datetime 13.10.0+15.04.20141103-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 11 13:06:24 2014 SourcePackage: indicator-datetime UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1391501/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391560] Re: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image
** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1391560 Title: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image Status in Ubuntu UX bugs: New Status in unity8 package in Ubuntu: Incomplete Bug description: As discussed with Olga, we need to develop a strategy on keeping the fonts readable when we allow the user to change the background. This is currently the case on the Greeter and the Lockscreens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1397718] Re: Scopes not easily discoverable in the Ubuntu Store
** Changed in: ubuntu-ux Assignee: (unassigned) = James Mulholland (jamesjosephmulholland) ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-click in Ubuntu. https://bugs.launchpad.net/bugs/1397718 Title: Scopes not easily discoverable in the Ubuntu Store Status in Ubuntu UX bugs: Triaged Status in unity-scope-click package in Ubuntu: Confirmed Bug description: It would be nice if there was an easy way to search the Ubuntu Store for scopes. That could either a way to switch between displaying apps and/or scopes results or it could be done by returning a list of all scopes when searching for scope or scopes. For now, scopes need to add scope to their descriptions and/or keywords. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1397718/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1172778] Re: [gallery][visual design]Empty albums
** Changed in: ubuntu-ux Status: Fix Committed = Triaged ** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Assignee: Calum Pringle (calumpringle) = (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1172778 Title: [gallery][visual design]Empty albums Status in Ubuntu UX bugs: Triaged Status in gallery-app package in Ubuntu: Confirmed Bug description: It is possible to end up with an empty album - on launching this album there is a temporary asset with + in it which launches the selector view of photos to add to the album. The asset used could be a duplication of that required for : https://bugs.launchpad.net/goodhope/+bug/1163403 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1172778/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396574] Re: TextField content partially deleted on focus with predictive text on
** Changed in: ubuntu-ux
Assignee: (unassigned) = Giorgio Venturi (giorgio-venturi)
** Changed in: ubuntu-ux
Importance: Undecided = High
** Changed in: ubuntu-ux
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu.
https://bugs.launchpad.net/bugs/1396574
Title:
TextField content partially deleted on focus with predictive text on
Status in Ubuntu Keyboard:
New
Status in Ubuntu UX bugs:
Fix Committed
Status in ubuntu-keyboard package in Ubuntu:
New
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
With the following Textfield:
TextField {
id:editTitle
width:parent.width
text:taskView.tasktoEdit.title
placeholderText: i18n.tr(Add title)
style: TextFieldStyle {
overlaySpacing: 0
frameSpacing: 0
background: Item {}
color: UbuntuColors.lightAubergine
}
}
And with predictive text on in the phone, if you try to click on the
field while it contains text, part of the text where the cursor lands
get deleted.
The work around is to set no predictive text: inputMethodHints:
Qt.ImhNoPredictiveText however this is a problem when predictive text
is required.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-keyboard/+bug/1396574/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394480] Re: Need a mechanism to load more query results
** Changed in: ubuntu-ux Assignee: (unassigned) = James Mulholland (jamesjosephmulholland) ** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: ubuntu-ux Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1394480 Title: Need a mechanism to load more query results Status in Ubuntu UX bugs: Triaged Status in unity-scopes-api package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Many APIs return only partial results to a query, along with a token for requesting further results. There should be a way for scopes to request those results when the user has viewed all of the current results. The obvious trigger would be when the user pulls up at the bottom of the results list. This feels natural, and it would mirror the pull- down-at-top-to-refresh behavior. But this could also happen automatically when the user approaches the bottom of the list, like infinite-scroll webpages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1394480/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400449] Re: qmltestrunner crashed with SIGABRT during unity8 tests
** Branch linked: lp:~aacid/unity8/fix_testDash -- 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/1400449 Title: qmltestrunner crashed with SIGABRT during unity8 tests Status in unity8 package in Ubuntu: In Progress Bug description: Running testDash ProblemType: Crash DistroRelease: Ubuntu 15.04 Package: qtdeclarative5-dev-tools 5.3.2-3ubuntu2 Uname: Linux 3.18.0-031800rc4-generic x86_64 ApportVersion: 2.14.7-0ubuntu10 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Dec 8 14:45:28 2014 Disassembly: = 0x7f84affa5e37: Cannot access memory at address 0x7f84affa5e37 ExecutablePath: /usr/lib/x86_64-linux-gnu/qt5/bin/qmltestrunner LocalLibraries: /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/libs/UbuntuGestures/libUbuntuGestures.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/mocks/Unity/libFakeUnityQml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/utils/modules/Unity/Test/libUnityTestQml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/mocks/Unity/DashCommunicator/libMockDashCommunicator-qml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins/Dash/libDash-qml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins/Ubuntu/Gestures/libUbuntuGesturesQml.so /home/michal/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins/Utils/libUtils-qml.so ProcCmdline: /usr/lib/x86_64-linux-gnu/qt5/bin/qmltestrunner -input /home/username/Pobrane/unity8-8.02+15.04.20141208/tests/qmltests/Dash/tst_Dash.qml -import /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/plugins -import /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/utils/modules -import /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/tests/mocks -o /home/username/Pobrane/unity8-8.02+15.04.20141208/builddir/testDash.xml,xunitxml -o -,txt Signal: 6 SourcePackage: qtdeclarative-opensource-src Stacktrace: #0 0x7f84affa5e37 in ?? () No symbol table info available. #1 0x in ?? () No symbol table info available. StacktraceTop: ?? () ?? () Title: qmltestrunner crashed with SIGABRT UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dip lpadmin plugdev sambashare sbuild sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1400449/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394479] Re: [design] Add ability to place text in emblem position
** Changed in: ubuntu-ux Assignee: (unassigned) = James Mulholland (jamesjosephmulholland) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1394479 Title: [design] Add ability to place text in emblem position Status in Ubuntu UX bugs: New Status in unity-scopes-api package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Category renders will display an image as the emblem at the right end of the title. It should be possible to place text there instead of or in addition to the image. Thus, the emblem should be have like the attributes. Example use case: The Gmail scope displays the time of an email in the emblem position, with the sender as the title. Currently, this is done with an SVG image displaying the text. However, this means the text size and alignment is incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1394479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1396208] Re: Pressing volume key doesn't restore full screen brightness
** Changed in: ubuntu-ux Status: New = Fix Committed ** Changed in: ubuntu-ux Assignee: (unassigned) = Matthew Paul Thomas (mpt) ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Status: Fix Committed = Triaged -- 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/1396208 Title: Pressing volume key doesn't restore full screen brightness Status in Ubuntu UX bugs: Triaged Status in unity-system-compositor package in Ubuntu: New Status in unity8 package in Ubuntu: Invalid Bug description: Steps to reproduce 1. Let device sit idle until the screen dims (not off, just dim) 2. Press a volume up/down button Expected behavior: Screen returns to full brightness Actual Behavior: No change in brightness Reproduced on Nex4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1396208/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1394479] Re: [design] Add ability to place text in emblem position
** Changed in: ubuntu-ux Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-api in Ubuntu. https://bugs.launchpad.net/bugs/1394479 Title: [design] Add ability to place text in emblem position Status in Ubuntu UX bugs: New Status in unity-scopes-api package in Ubuntu: New Status in unity8 package in Ubuntu: New Bug description: Category renders will display an image as the emblem at the right end of the title. It should be possible to place text there instead of or in addition to the image. Thus, the emblem should be have like the attributes. Example use case: The Gmail scope displays the time of an email in the emblem position, with the sender as the title. Currently, this is done with an SVG image displaying the text. However, this means the text size and alignment is incorrect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1394479/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1221172] Re: [Gallery app] Deleted photos displayed as empty squares in 'Photos' tab
** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Status: Fix Committed = Triaged ** Changed in: ubuntu-ux Assignee: Christina Li (christina-li) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1221172 Title: [Gallery app] Deleted photos displayed as empty squares in 'Photos' tab Status in Ubuntu UX bugs: Triaged Status in gallery-app package in Ubuntu: Incomplete Bug description: Current situation: Previously deleted photos still display as empty squares in 'Photos' tab only. Screenshot attached. Desired solution: Deleted photos should not be displayed at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1221172/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305143] Re: [indicators] the ordering of icons of a single indicator should reverse on RTL system
** Changed in: ubuntu-ux Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1305143 Title: [indicators] the ordering of icons of a single indicator should reverse on RTL system Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: New Bug description: Just as the pre-label moves from left to the right on a Right-to-Left system, the multiple icons of an indicator should also change their ordering so that the first (leftmost) icon becomes the rightmost one, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1305143/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317860] Re: [system] the phone should switch itself off before completely draining battery
Not Fix Committed yet because it's not mentioned in the spec. ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Assignee: John Lea (johnlea) = Matthew Paul Thomas (mpt) ** Changed in: ubuntu-ux Status: Fix Committed = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1317860 Title: [system] the phone should switch itself off before completely draining battery Status in The Power Indicator: Confirmed Status in Ubuntu UX bugs: Confirmed Status in indicator-power package in Ubuntu: Confirmed Bug description: the phone should switch itself off at around ~5% remaining battery. This is to preserve a little battery for use cases such as: * turn it back on once or twice for urgent short phone calls * prevent the battery from going into a state where it can't be charged any more * have enough power to turn itself on again and trigger an alarm Desired resolution The following actions should take place as the phone/tablet runs out of battery: at 10% - Notification battery under 10% at 5% - Notification saying battery level is critical, will shutdown soon. at 1-2% - Shell fades out, animation fades in (same as startup animation), phone initiates full shutdown. The notification should be a clickable notification with the tap action mapped to dismiss. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1317860/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1261300] Re: Dash bullet expansion is confusing and difficult to discover
** Changed in: ubuntu-ux Importance: Undecided = Low -- 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/1261300 Title: Dash bullet expansion is confusing and difficult to discover Status in Ubuntu UX bugs: Fix Committed Status in Unity: New Status in The Unity 8 shell: Fix Released Status in unity package in Ubuntu: New Status in unity8 package in Ubuntu: Fix Released Bug description: Section bullets are hard to discover and confusing, in both unity 7 and 8. Unity7+8: A small set of applications/icons are shown under each heading making it look like that heading is already fully expanded. Result: The user never thinks to tap on the heading (like Installed) again to see more apps/icons. Unity 8: Arrows next to headings are misleading: Collapsed: Heading v Expanded: Heading ^ Again, the down arrow suggests the list is already fully expanded so users don't think to tap on it again to further expand the list. Many people will expect the more familiar convention: Collapsed: Heading Expanded: Heading v On a touch image this leads to simple but frustrating problems like the user never finding System Settings. Because it's non-obvious they need to tap on Applications which looks like it's already expanded. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1261300/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1294294] Re: Carousel displays no metadata, making it impossible to identify tracks/videos
** Changed in: ubuntu-ux Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1294294 Title: Carousel displays no metadata, making it impossible to identify tracks/videos Status in Ubuntu UX bugs: Fix Committed Status in unity-scope-mediascanner package in Ubuntu: Triaged Status in unity8 package in Ubuntu: Fix Released Bug description: Put some music and/or videos onto your device via mtp into ~/Music and/or ~/Videos Go to the Music or Video scope Observe music covers or video thumbnails. Note that with multiple tracks from the same album/artist it's impossible to differentiate them as there is no metadata displayed. It's less pronounced on video carousel as you may have decent thumbnails which let you identify one video from another. However if you have multiple episodes of a show, it's not easy to tell which is which. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.84+14.04.20140317.2-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.13.3-0ubuntu1 Architecture: armhf Date: Tue Mar 18 19:05:48 2014 InstallationDate: Installed on 2014-03-18 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140318.1) ProcEnviron: TERM=linux PATH=(custom, no user) XDG_RUNTIME_DIR=set SHELL=/bin/bash SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1294294/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372011] Re: ListItem.Subtitled subText color is too dark with SuruDark
** Changed in: ubuntu-ux Importance: Undecided = High -- 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/1372011 Title: ListItem.Subtitled subText color is too dark with SuruDark Status in Permy: New Status in Ubuntu UX bugs: New Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: It is hard to read ListItem.Subtitled subText when using the SuruDark theme (or other dark themes). To manage notifications about this bug go to: https://bugs.launchpad.net/permy/+bug/1372011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391560] Re: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image
** Changed in: ubuntu-ux Status: New = Triaged ** Changed in: ubuntu-ux Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1391560 Title: [themes] [design] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: As discussed with Olga, we need to develop a strategy on keeping the fonts readable when we allow the user to change the background. This is currently the case on the Greeter and the Lockscreens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391839] Re: Cannot change boundsBehaviour on Flickable in Expandable
I think we should have a good default, then allow developers to change the property. For example, an app developer might not want to have overshoot at all and provide a different hint that the list/area boundaries have been reached. ** Tags added: design-sync ** Changed in: ubuntu-ux Status: New = In Progress ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Importance: Medium = Low -- 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/1391839 Title: Cannot change boundsBehaviour on Flickable in Expandable Status in Ubuntu UI Toolkit: Incomplete Status in Ubuntu UX bugs: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Right now it's quite unfortunate that some Expandables can be dragged and overshot (Flickable.DragAndOvershootBounds). Could the Expandable expose the boundsBehaviour property or in some other way make this changeable? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1391839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382596] Re: [Dash] Launcher home button (BFB) and pinned apps visuals incorrect
** Changed in: ubuntu-ux Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1382596 Title: [Dash] Launcher home button (BFB) and pinned apps visuals incorrect Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: New Bug description: The orange button (home is incorrect (should have rounded corners) and the pinned apps should have a white dot on the top left, they shouldn´t be cut To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1382596/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1338138] Re: [sdk] Time Picker component does not respect user locale
** Changed in: ubuntu-ux
Importance: Undecided = Medium
--
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/1338138
Title:
[sdk] Time Picker component does not respect user locale
Status in Ubuntu UX bugs:
Fix Committed
Status in ubuntu-ui-toolkit package in Ubuntu:
Confirmed
Bug description:
In the new clock app we are using the Date Picker component to allow
the user to choose a time. Hence the mode used was Hours|Minutes.
However the Date Picker seems to always display the time in 24 hour
instead of using the user's locale. So whereever 12-hour time format
is required, the time picker ignores that.
The code below shows the usage in the clock app.
DatePicker {
id: _timePicker
anchors {
left: parent.left
right: parent.right
margins: units.gu(-2)
}
clip: true
mode: Hours|Minutes
}
-- Design solution --
https://docs.google.com/a/canonical.com/document/d/1nFm8xiYhKXXuEO_IvMXoD0lASbYzYXva1BWMVanU3iw/edit#heading=h.tuxva2dtgvpk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1338138/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386208] Re: Purple overflow panel in SuruGradient theme
** Changed in: ubuntu-ux Importance: Undecided = Low -- 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/1386208 Title: Purple overflow panel in SuruGradient theme Status in File Manager application for Ubuntu devices: Fix Committed Status in Ubuntu UI Toolkit: Fix Released Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: New Bug description: While testing the new header on trunk, I noticed that the actions on the header are purple. They should be the same colour as the rest of the app. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-filemanager-app/+bug/1386208/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1231951] Re: [dash] + [scopes] Need a renderer for dash plugins
** Summary changed: - Need a renderer for dash plugins + [dash] + [scopes] Need a renderer for dash plugins ** Changed in: ubuntu-ux Status: Fix Committed = Fix Released ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Assignee: Xi Zhu (xi.zhu) = Estibaliz Landa Torres (estilanda) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-home in Ubuntu. https://bugs.launchpad.net/bugs/1231951 Title: [dash] + [scopes] Need a renderer for dash plugins Status in LibUnity: Fix Released Status in Ubuntu UX bugs: Fix Released Status in Unity Home Scope: Fix Released Status in The Unity 8 shell: Fix Released Status in libunity package in Ubuntu: New Status in unity-scope-home package in Ubuntu: Fix Released Status in unity8 package in Ubuntu: Fix Released Bug description: We need a custom renderer for dash plugins, similar to the weather one (bug #1231948) - no shape around the icon, but also we need to de- colourize the icons when disabled. Should be possible to use the Icon component ¹ for that. Ultimately we'll need an emboss effect or similar, but for now let's just go with a semi-transparent grey/black. ¹ http://developer.ubuntu.com/api/ubuntu-12.10/qml/mobile/qml-ubuntu- components0-icon.html#keyColor-prop desired solution see visual design spec https://docs.google.com/a/canonical.com/presentation/d/1X3_G6reCpcFJxzxn1Xtv9wK5n3-wOW-6z2l0qSZ8-sg/edit#slide=id.g1177c0912_00 To manage notifications about this bug go to: https://bugs.launchpad.net/libunity/+bug/1231951/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1221174] Re: [Gallery app] Timeline displays year '-4714'
** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Status: Fix Committed = Triaged ** Changed in: ubuntu-ux Assignee: Christina Li (christina-li) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1221174 Title: [Gallery app] Timeline displays year '-4714' Status in Ubuntu UX bugs: Triaged Status in gallery-app package in Ubuntu: Incomplete Bug description: Current: Under 'Event's timeline displays year '-4714'. Trigger unknown. Screenshot attached. Desired: Timeline should not display date/years beyond when photos were taken. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1221174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1229663] Re: Unselected tab names too dark in Dark theme
** Changed in: ubuntu-ux Importance: Undecided = High -- 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/1229663 Title: Unselected tab names too dark in Dark theme Status in Ubuntu UI Toolkit: Invalid Status in Ubuntu UX bugs: Fix Committed Status in ubuntu-ui-toolkit package in Ubuntu: Invalid Bug description: Current situation: In the dark theme (for example, in an open indicator screen) if you tap the tabs header to see other available tabs, the ones that are not selected are too dark, hard to see Solution: The unselected tab colour in dark theme should be #f3f3e7, 0.2 opacity To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1229663/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1229652] Re: Home and app scope names are wrong
** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Status: Fix Committed = Triaged ** Changed in: ubuntu-ux Assignee: Jouni Helminen (jounihelminen) = James Mulholland (jamesjosephmulholland) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-home in Ubuntu. https://bugs.launchpad.net/bugs/1229652 Title: Home and app scope names are wrong Status in Ubuntu UX bugs: Triaged Status in Unity Home Scope: Triaged Status in unity-scope-home package in Ubuntu: New Bug description: Current situation: At the moment we have Home Scope and Applications Solution: They should be Home and Apps instead To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1229652/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1221177] Re: [Gallery app] Timeline shouldn't display date with no photos
** Changed in: ubuntu-ux Importance: Undecided = High ** Changed in: ubuntu-ux Status: Fix Committed = Triaged ** Changed in: ubuntu-ux Assignee: Christina Li (christina-li) = Jouni Pentikäinen (jouni) ** Changed in: ubuntu-ux Assignee: Jouni Pentikäinen (jouni) = (unassigned) ** Changed in: ubuntu-ux Assignee: (unassigned) = Jouni Helminen (jounihelminen) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gallery-app in Ubuntu. https://bugs.launchpad.net/bugs/1221177 Title: [Gallery app] Timeline shouldn't display date with no photos Status in Ubuntu UX bugs: Triaged Status in gallery-app package in Ubuntu: Invalid Bug description: Current situation: 'Events' timeline has produced a date when no photos are maintained within that date. Screenshot attached. Desired solution: Date should not be displayed in the timeline when no photos are associated to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1221177/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391503] Re: ScrollBar color is not distinctive enough
I would rather expose the scrollbar color in the API ** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1391503 Title: ScrollBar color is not distinctive enough Status in Ubuntu UX bugs: Triaged Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: Using a MainView with default color, a Flickable and a Scrollbar in it, leaves the scrollbar mostly invisible. You can see it if you look *very* closely, but it's not providing the help/indication it is supposed to. I guess the Scrollbar would need some background color detection and change its color, or, at least provide a color property to allow the developer setting the color. A third option would probably be to expose the ScrollbarStyle in the API so it can be customized to fit the app's design. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391503/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391548] Re: [sdk] + [header]Portuguese words in selection header don't fit
** Changed in: ubuntu-ux Importance: Undecided = High -- 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/1391548 Title: [sdk] + [header]Portuguese words in selection header don't fit Status in Ubuntu UX bugs: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: See http://imgur.com/EZ1lqUI and http://imgur.com/RPRe8Bm Probably this will happen in other languages as well. We need feedback from design to decide how to solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1250861] Re: Long-press on launcher doesn't work when quicklist is on screen
If it's a future consideration, it probably isn't described in a spec yet ... and even if it is, the spec hasn't been linked here. ** Changed in: ubuntu-ux Importance: Undecided = Low ** Changed in: ubuntu-ux Status: Fix Committed = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1250861 Title: Long-press on launcher doesn't work when quicklist is on screen Status in Ubuntu UX bugs: Confirmed Status in unity8 package in Ubuntu: Incomplete Bug description: Steps to reproduce: 1. long-press on a launcher icon 2. release 3. long-press again Expected: 3. you can drag the long-pressed item Current: 3. quicklist closes --- Desired solution: As described in bug reports Expected behaviour. User should be able to enable item reordering even if quick list menu is open. Note that quick list should disappear when item is moved like the case is with the first long press. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1250861/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1238174] Re: [Notifications] notifications / snap decisions over indicators blend into background
** Changed in: ubuntu-ux Importance: Undecided = Medium ** Changed in: ubuntu-ux Status: Fix Committed = Triaged ** Changed in: ubuntu-ux Assignee: James Mulholland (jamesjosephmulholland) = Paty Davila (dizzypaty) -- 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/1238174 Title: [Notifications] notifications / snap decisions over indicators blend into background Status in Ubuntu UX bugs: Triaged Status in unity8 package in Ubuntu: Incomplete Bug description: When a notification or a snap decision is displayed over indicators, it looks really bad, both having the same background. -- New design for notification solve this problem: https://docs.google.com/a/canonical.com/document/d /1ehZGFePGmy8pnyAGsgWYDeBgr45Cc8jE2mTb2Qz- oeM/edit#heading=h.l9277ssjb99w To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1238174/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391548] Re: [sdk] + [header]Portuguese words in selection header don't fit
There are a few different strategies we could use here to mitigate the issue: 1) By default, the action could have a max width at 2x the default width, but the app developer can decide to change that to a custom value 2) By default, I would add a semitransparent gradient like at the end of the browser URL when it exceeds the available width 3) The translator could come up with a different word. See http://goo.gl/qj6Pgi 4) The translator could come up with a shortening eg. compartil. ** Changed in: ubuntu-ux Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1391548 Title: [sdk] + [header]Portuguese words in selection header don't fit Status in Ubuntu UX bugs: In Progress Status in ubuntu-ui-toolkit package in Ubuntu: Incomplete Bug description: See http://imgur.com/EZ1lqUI and http://imgur.com/RPRe8Bm Probably this will happen in other languages as well. We need feedback from design to decide how to solve the issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1399710] Re: no audible warning of high volume level
** Changed in: ubuntu-ux Importance: Undecided = Low -- 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/1399710 Title: no audible warning of high volume level Status in Ubuntu UX bugs: Triaged Status in indicator-sound package in Ubuntu: Incomplete Bug description: Additional to the work done on bug 1373404, I think we need to consider adding an audio warning when the volume crosses the threshold value. The way android works is that the user is asked if they want to allow higher volume levels (they must click ok). Our approach is to just display a visual warning. That's fine (assuming it complies with all legal regs), but it isn't helpful from an accessibility perspective. Obviously folk can hear when levels become painful high, but how about we insert an audible warning when the user crosses the threshold? I'd suggest we do both of the following to indicate an audible warning: 1) Mute (or atleast lower) the currently playing audio streams. 2) Play two beeps in quick succession (at the original volume level prior to mute/lowering). Once the beeps have been played, the volume level will be restored to the appropriate (higher) level. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1399710/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400680] Re: display-manager autopkgtests for systemd
** Patch added: 0001-Add-display-managers-autopkg-tests.patch https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400680/+attachment/4276871/+files/0001-Add-display-managers-autopkg-tests.patch ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1400680 Title: display-manager autopkgtests for systemd Status in systemd package in Ubuntu: New Bug description: See attached patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400680] [NEW] display-manager autopkgtests for systemd
Public bug reported: See attached patch ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Martin Pitt (pitti) Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1400680 Title: display-manager autopkgtests for systemd Status in systemd package in Ubuntu: New Bug description: See attached patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400682] [NEW] Add xdiagnose fallback when display-manager fails to start
Public bug reported: Attached patch ** Affects: systemd (Ubuntu) Importance: Undecided Assignee: Martin Pitt (pitti) Status: New ** Patch added: 0001-Add-xdiagnose-graphical-as-a-fallback-if-display-man.patch https://bugs.launchpad.net/bugs/1400682/+attachment/4276878/+files/0001-Add-xdiagnose-graphical-as-a-fallback-if-display-man.patch ** Changed in: systemd (Ubuntu) Assignee: (unassigned) = Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1400682 Title: Add xdiagnose fallback when display-manager fails to start Status in systemd package in Ubuntu: New Bug description: Attached patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381108] Re: Panel closes immediately after hinting if you don't move touch position
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released ** Changed in: unity8 (Ubuntu RTM) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1381108 Title: Panel closes immediately after hinting if you don't move touch position Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: The panel hint should hold open if you don't move your finger after tapping for hint. This is a regression and there is a new log message if you don't move: [TouchRegistry] Candidate for touch 0 defaulted! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1381108/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381067] Re: left-edge drag over greeter results in jumpy launcher
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Committed ** Changed in: unity8 (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1381067 Title: left-edge drag over greeter results in jumpy launcher Status in unity8 package in Ubuntu: Fix Released Bug description: unity8 version 8.00+14.10.20141013.2-0ubuntu1 Performing a left-edge drag over the greeter results in a jumpy launcher. It jumps back and forth a couple of times before finally moving rightwards to follow the gesture To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1381067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1210199] Re: [Shell] support rotation
** Changed in: unity8 (Ubuntu) Status: Triaged = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1210199 Title: [Shell] support rotation Status in Ubuntu UX bugs: Fix Committed Status in unity8 package in Ubuntu: In Progress Bug description: Example: going to Notes, write a new note so that OSK appears and then switch to landscape mode. The indicators is covered by the OSK rather than the same length of the app. Refer to: https://docs.google.com/a/canonical.com/drawings/d/1P_lCbl7tZ3QTuhvFg2Xl0P5hXm8T46mXl5HYgPQdAgY/edit for proposed solution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1210199/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384730] Re: [notifications] remove combo button from incoming call snap
** Changed in: ubuntu-ux Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1384730 Title: [notifications] remove combo button from incoming call snap Status in Ubuntu UX bugs: Fix Released Status in unity8 package in Ubuntu: Fix Released Status in unity8 package in Ubuntu RTM: Fix Released Bug description: Build r123 The current incoming snap decision has a combo button for additional options, allowing users to reply with a quick message if they are busy/can not take the call. This combo button has two hit areas which caused a lot of confusion with users. One part DECLINES the call the other expands for additional options. Please remove combo button and replace with a toggle button with only one hit area. Hitting that button will reveal an expansion with additional options to users for a quick reply. Remove the CUSTOM option in the quick reply menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1384730/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400682] Re: Add xdiagnose fallback when display-manager fails to start
** Tags added: patch -- 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/1400682 Title: Add xdiagnose fallback when display-manager fails to start Status in systemd package in Ubuntu: New Bug description: Attached patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400680] Re: display-manager autopkgtests for systemd
** Tags added: patch -- 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/1400680 Title: display-manager autopkgtests for systemd Status in systemd package in Ubuntu: New Bug description: See attached patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1400680/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1372548] Re: Phone field doesn't accept symbols #*()
** Branch linked: lp:~renatofilho/telephony-service/fix-1372548-2 ** Branch unlinked: lp:~renatofilho/telephony-service/fix-1372548 -- 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/1372548 Title: Phone field doesn't accept symbols #*() Status in Address Book App: Confirmed Status in Ubuntu UX bugs: New Status in address-book-app package in Ubuntu: New Status in ubuntu-keyboard package in Ubuntu: New Status in address-book-app package in Ubuntu RTM: New Status in ubuntu-keyboard package in Ubuntu RTM: New Bug description: The phone field in address book doesn't accept symbols available in the keyboard for phone numbers: #* Test case: - Open Contacts app. - Add a new contact. - Go to Phone number field. - Press + key for 5 seconds and select these symbols: *#() Expected result: - Field accepts symbols as part of a telephone number. Actual result: - Only + symbol is accepted. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1372548/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384460] Re: Delegate unhandled URL schemes to the system
** Changed in: url-dispatcher (Ubuntu RTM) Assignee: (unassigned) = Ted Gould (ted) ** Changed in: url-dispatcher (Ubuntu) Assignee: (unassigned) = Ted Gould (ted) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1384460 Title: Delegate unhandled URL schemes to the system Status in the base for Ubuntu mobile products: Confirmed Status in Dialer app for Ubuntu Touch: In Progress Status in Oxide Webview: Fix Released Status in Oxide 1.3 series: Fix Released Status in dialer-app package in Ubuntu: Fix Released Status in url-dispatcher package in Ubuntu: New Status in webbrowser-app package in Ubuntu: Fix Released Status in dialer-app package in Ubuntu RTM: In Progress Status in url-dispatcher package in Ubuntu RTM: New Status in webbrowser-app package in Ubuntu RTM: Fix Released Bug description: We currently ignore any URL's with a scheme that is unrecognised. We should be delegating these to the system so that it can try to find a handler for it To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1384460/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1236963] Re: compiz crashed with SIGSEGV in unity::launcher::Launcher::Resize()
** Information type changed from Private to Public ** Changed in: unity Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1236963 Title: compiz crashed with SIGSEGV in unity::launcher::Launcher::Resize() Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: Shut Toshiba laptop lid so display stayed on external monitor only, crashed bamfdaemon and compiz ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.1+13.10.20131004-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-11.17-generic 3.11.3 Uname: Linux 3.11.0-11-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Tue Oct 8 18:13:08 2013 Disassembly: = 0x23fa: Cannot access memory at address 0x23fa ExecutablePath: /usr/bin/compiz MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_GB.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x23fa:Cannot access memory at address 0x23fa PC (0x23fa) not located in a known VMA region (needed executable region)! SegvReason: executing NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () unity::launcher::Launcher::Resize(nux::Point2Dint const, int) () from /usr/lib/compiz/libunityshell.so unity::launcher::Launcher::SetIconSize(int, int) () from /usr/lib/compiz/libunityshell.so unity::launcher::Launcher::UpdateOptions(std::shared_ptrunity::launcher::Options) () from /usr/lib/compiz/libunityshell.so unity::launcher::Launcher::OnOptionChanged() () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in unity::launcher::Launcher::Resize() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1236963/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1165115] Re: Crash after pluging in og htc smartphone
We need a better stacktrace. Can you still reproduce this? ** Changed in: unity Status: New = Incomplete ** Changed in: unity (Ubuntu) Status: New = Incomplete ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1165115 Title: Crash after pluging in og htc smartphone Status in Unity: Incomplete Status in unity package in Ubuntu: Incomplete Bug description: After I connected my htc-smartphone and tried to download Unity completly crashed and restored afterwards so I could continue downloading the files ProblemType: Crash DistroRelease: Ubuntu 13.04 Package: unity 6.12.0daily13.04.01-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4 Uname: Linux 3.8.0-14-generic i686 .tmp.unity.support.test.0: ApportVersion: 2.9.2-0ubuntu5 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri Apr 5 19:02:06 2013 DistUpgraded: 2013-02-23 12:08:06,924 DEBUG enabling apt cron job DistroCodename: raring DistroVariant: ubuntu ExecutablePath: /usr/bin/compiz GraphicsCard: Advanced Micro Devices [AMD] nee ATI RV505 CE [Radeon X1550 64-bit] [1002:715f] (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Device [1043:01ca] Subsystem: ASUSTeK Computer Inc. Device [1043:01cb] InstallationDate: Installed on 2012-09-28 (188 days ago) InstallationMedia: Lubuntu 12.10 Quantal Quetzal - Beta i386 (20120928) LightdmGreeterLog: ** (lightdm-gtk-greeter:1751): WARNING **: Failed to load user background: Datei »/home/tom/.cache/gnome-control-center/backgrounds/f243d139670217fc1301bafa897d894468e713d66a30dca75f1b5a215a4a13bd« konnte nicht geöffnet werden: Keine Berechtigung ** (lightdm-gtk-greeter:1751): WARNING **: Failed to load user image: Datei »/home/tom/.face« konnte nicht geöffnet werden: Keine Berechtigung LightdmGreeterLogOld: ** (lightdm-gtk-greeter:1761): WARNING **: Failed to load user background: Datei »/home/tom/.cache/gnome-control-center/backgrounds/f243d139670217fc1301bafa897d894468e713d66a30dca75f1b5a215a4a13bd« konnte nicht geöffnet werden: Keine Berechtigung ** (lightdm-gtk-greeter:1761): WARNING **: Failed to load user image: Datei »/home/tom/.face« konnte nicht geöffnet werden: Keine Berechtigung MarkForUpload: True ProcCmdline: compiz ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-14-generic root=UUID=84abf351-e93a-448f-9a2f-15142e27f2ef ro quiet splash vt.handoff=7 SegvAnalysis: Skipped: missing required field Disassembly Signal: 11 SourcePackage: unity UpgradeStatus: Upgraded to raring on 2013-02-23 (41 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 02/18/2008 dmi.bios.vendor: Intel Corp. dmi.bios.version: DPP3510J.86A.0407.2008.0218.0923 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP35DP dmi.board.vendor: Intel Corporation dmi.board.version: AAD81073-208 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrDPP3510J.86A.0407.2008.0218.0923:bd02/18/2008:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-208:cvn:ct3:cvr: version.compiz: compiz 1:0.9.9~daily13.03.29-0ubuntu1 version.libdrm2: libdrm2 2.4.43-0ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.0.3-0ubuntu1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.0.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.13.3-0ubuntu4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu2b2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.1.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.21.5-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.7-0ubuntu1 xserver.bootTime: Fri Apr 5 18:19:11 2013 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.13.3-0ubuntu4 xserver.video_driver: radeon To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1165115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1382033] Re: [SIM PIN] 'Incorrect PIN' warning is not cleared from display for SIM2 PIN entry
i-network assumes that unity8 signals that the error has been shown by
activating the error action. This only happens after the timer times
out:
Timer {
id: errorTimer
interval: 4000;
running: false;
repeat: false
onTriggered: {
errorAction.activate();
}
}
I will make the indicator to clear the error message when the snap
decision closes and thus this can be handled on i-network-service alone.
** Changed in: indicator-network (Ubuntu)
Status: Confirmed = Triaged
--
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/1382033
Title:
[SIM PIN] 'Incorrect PIN' warning is not cleared from display for SIM2
PIN entry
Status in indicator-network package in Ubuntu:
Triaged
Status in unity8 package in Ubuntu:
Invalid
Status in unity8 package in Ubuntu RTM:
Invalid
Bug description:
14.09-proposed image #109
STEPS:
1. Ensure 2 SIMs inserted into device with PIN lock enabled
2. Boot up
3. At SIM1 PIN entry insert incorrect PIN once
4. Insert correct SIM1 PIN on second attempt (do this reasonably quickly
before the warning disappears)
EXPECTED RESULT:
SIM2 PIN entry should display with no warning message
ACTUAL RESULT:
The incorrect PIN warning is still displayed for SIM2 PIN entry, when no PIN
has been entered for SIM2.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1382033/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1311316] Re: After locking screen there is no input field to type password for unlock
For infomation : I used Marco Trevisan's unity package since 2014-09-11 without getting this issue. This morning I installed unity (up to date) from Ubuntu repository and I just get this issue. Like David, the first times I get this bug, I noticed some issues with window animations before it happened (windows were moving very slowly). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1311316 Title: After locking screen there is no input field to type password for unlock Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in unity package in Ubuntu: Fix Released Bug description: Sometimes (but not always) after locking the screen there is the situation not having any input field where I can type the password to unlock the session again. The shaded gray area simply does not have the input field. I can't do anything, I have to switch to text console and stop/start lightdm service to cure the problem loosing all of my session :( ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140416-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Apr 22 22:17:57 2014 InstallationDate: Installed on 2012-03-03 (780 days ago) InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2013-10-18 (186 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1297144] Re: Invisible cursor after resume from suspend
Same issue as described in #40 (also X1 Carbon with Ubuntu 14.10). -- 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/1297144 Title: Invisible cursor after resume from suspend Status in light-locker package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: I am using the daily build of Xubuntu 14.04 x64 on a Lenovo Thinkpad x230. If I wake up the computer after it spending some time in the suspend state, the cursor will be invisible. The courser still works (I can click on stuff and hover the invisible cursor over stuff), but the little arrow is not visible. This bug showed up a few days ago after an update. Putting the computer back in suspend state and immediately waking it back up resolves the issue until the next time the computer is put in suspend state for an extended period of time. It is possible that this bug has something to do with Whisker Menu. Sometimes when the courser is invisible it will still show up over Whisker Menu. Most of the time it is invisible there too. Description: Ubuntu Trusty Tahr (development branch) Release: 14.04 xfdesktop version 4.11.4, running on Xfce 4.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/light-locker/+bug/1297144/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1345873] Re: First Use of Workspace Switcher: compiz crashed with SIGSEGV in assign_to_own()
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1345873 Title: First Use of Workspace Switcher: compiz crashed with SIGSEGV in assign_to_own() Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: First click on workspace switcher icon in Launcher after a clean install of the 20 July Utopic daily failed to produce the expected spread of workspaces and instead triggered approx. 30 seconds of disk activity followed by an Apport message that compiz had crashed. On the second the switcher performed as expected. I've seen the same behavior on every Unity release since 12.04. ThinkPad W530, Intel HD4000, 1920x1080. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-4.9-generic 3.16.0-rc5 Uname: Linux 3.16.0-4-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Sun Jul 20 21:11:18 2014 Disassembly: = 0x7f01: Cannot access memory at address 0x7f01 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-07-21 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140720) ProcCmdline: compiz ProcEnviron: PATH=(custom, no user) LANGUAGE=en_US XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7f01:Cannot access memory at address 0x7f01 PC (0x7f01) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () CompAction::initiate() const () from /usr/lib/libcompiz_core.so.ABI-20140123 unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() 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/unity/+bug/1345873/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305773] Re: compiz crashed with SIGSEGV in CompAction::initiate()
*** This bug is a duplicate of bug 1345873 *** https://bugs.launchpad.net/bugs/1345873 ** This bug has been marked a duplicate of bug 1345873 First Use of Workspace Switcher: compiz crashed with SIGSEGV in assign_to_own() -- 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/1305773 Title: compiz crashed with SIGSEGV in CompAction::initiate() Status in Unity: New Status in unity package in Ubuntu: New Bug description: I was playing with CCSM; some options I've put disappear when I come back to the screen; setting them again make unity (???) freeze ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 10 12:46:01 2014 Disassembly: = 0x7f88: Cannot access memory at address 0x7f88 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-05 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcCmdline: compiz SegvAnalysis: Segfault happened at: 0x7f88:Cannot access memory at address 0x7f88 PC (0x7f88) not located in a known VMA region (needed executable region)! SegvReason: executing unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () CompAction::initiate() const () from /usr/lib/libcompiz_core.so.ABI-20140123 unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() 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/unity/+bug/1305773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1302891] Re: compiz crashed with SIGSEGV in assign_to_own()
*** This bug is a duplicate of bug 1345873 *** https://bugs.launchpad.net/bugs/1345873 ** This bug has been marked a duplicate of bug 1345873 First Use of Workspace Switcher: compiz crashed with SIGSEGV in assign_to_own() -- 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/1302891 Title: compiz crashed with SIGSEGV in assign_to_own() Status in Unity: Confirmed Status in unity package in Ubuntu: Confirmed Bug description: on ubuntu 14.04 beta ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140403-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 20:16:26 2014 Disassembly: = 0x0: No se puede acceder a la memoria en la dirección 0x0 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-03-29 (5 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Beta amd64 (20140326) ProcCmdline: compiz ProcEnviron: LANGUAGE=es_AR:es PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=es_AR.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x0: No se puede acceder a la memoria en la dirección 0x0 PC (0x) not located in a known VMA region (needed executable region)! source 0x0 (0x) not located in a known VMA region (needed readable region)! SegvReason: executing NULL VMA reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: ?? () CompAction::initiate() const () from /usr/lib/libcompiz_core.so.ABI-20140123 unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() 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/unity/+bug/1302891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304118] Re: compiz crashed with SIGSEGV in assign_to_own()
*** This bug is a duplicate of bug 1345873 *** https://bugs.launchpad.net/bugs/1345873 ** This bug is no longer a duplicate of bug 1302891 compiz crashed with SIGSEGV in assign_to_own() ** This bug has been marked a duplicate of bug 1345873 First Use of Workspace Switcher: compiz crashed with SIGSEGV in assign_to_own() -- 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/1304118 Title: compiz crashed with SIGSEGV in assign_to_own() Status in unity package in Ubuntu: New Bug description: attempted to set wobbly windows in trusty. ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140404-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Mon Apr 7 21:04:11 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-04-07 (1 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140406) ProcCmdline: compiz ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SegvAnalysis: Failure: invalid literal for int() with base 10: 'bad' Signal: 11 SourcePackage: unity StacktraceTop: ?? () CompAction::initiate() const () from /usr/lib/libcompiz_core.so.ABI-20140123 unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() 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/ubuntu/+source/unity/+bug/1304118/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1400186] Re: [VGN-A690, Realtek ALC260] No sound at all internal speakers and headphone (Green out)
https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/hda_generic.c?id=03ad6a8c93b6df2d65c305b5b5f9474068b45bfb you need to discuss with the author how to assign the playback volume name when you have three outputs internal speaker, headphone and replicator output Node 0x08 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out Control: name=Speaker Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x00 0x00] Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0 Amp-Out vals: [0x40 0x40] Connection: 2 0x02 0x07 Node 0x09 [Audio Mixer] wcaps 0x20010f: Stereo Amp-In Amp-Out Control: name=PCM Playback Volume, index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-In caps: ofs=0x00, nsteps=0x00, stepsize=0x00, mute=1 Amp-In vals: [0x00 0x00] [0x00 0x00] Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0 Amp-Out vals: [0x40 0x40] Connection: 2 0x02 0x07 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1400186 Title: [VGN-A690, Realtek ALC260] No sound at all internal speakers and headphone (Green out) Status in alsa-driver package in Ubuntu: Incomplete Bug description: I have tried using different options in /etc/modprobe.d/alsa- base.conf. Without probe_mask=1 it also detects a Conexant modem. I just discovered there is sound output from the rear A/V Out port of the laptop, but there is popping whether or not audio is playing. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: beat 1823 F pulseaudio CurrentDesktop: XFCE CurrentDmesg: [ 42.213440] systemd-logind[805]: Failed to start user service: Unknown unit: user@1000.service [ 42.220873] systemd-logind[805]: New session c1 of user beat. [ 42.220901] systemd-logind[805]: Linked /tmp/.X11-unix/X0 to /run/user/1000/X11-display. Date: Sun Dec 7 20:10:30 2014 InstallationDate: Installed on 2014-12-06 (1 days ago) InstallationMedia: Xubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: beat 1823 F pulseaudio Symptom_Jack: Green Line Out, Rear Symptom_Type: No sound at all Title: [VGN-A690, Realtek ALC260, Green Line Out, Rear] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2005 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: R0080F2 dmi.chassis.asset.tag: 8S4Lf716540bab4851f0 dmi.chassis.type: 10 dmi.chassis.vendor: Sony Corporation dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrR0080F2:bd03/14/2005:svnSonyCorporation:pnVGN-A690:pvrC00071GZ:cvnSonyCorporation:ct10:cvrN/A: dmi.product.name: VGN-A690 dmi.product.version: C00071GZ dmi.sys.vendor: Sony Corporation mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-12-07T18:28:32.827133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1400186/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1234241] Re: compiz crashed with SIGSEGV in __exchange_and_add()
*** This bug is a duplicate of bug 1110374 *** https://bugs.launchpad.net/bugs/1110374 ** This bug has been marked a duplicate of bug 1110374 compiz crashed with SIGSEGV in assign_to_own() -- 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/1234241 Title: compiz crashed with SIGSEGV in __exchange_and_add() Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: Compiz crashed on startup. As far as I am aware, I did nothing to provoke this error. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130920-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-8.15-generic 3.11.1 Uname: Linux 3.11.0-8-generic x86_64 ApportVersion: 2.12.5-0ubuntu1 Architecture: amd64 Date: Fri Sep 27 09:24:53 2013 ExecutablePath: /usr/bin/compiz ExecutableTimestamp: 1379677419 InstallationDate: Installed on 2012-05-01 (513 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) MarkForUpload: True ProcCmdline: compiz ProcCwd: /home/joey SegvAnalysis: Segfault happened at: 0x7fd3bd06e69d _ZN10CompAction8initiateEv+13: mov0x8(%rdi),%rdx PC (0x7fd3bd06e69d) ok source 0x8(%rdi) (0x0008) not located in a known VMA region (needed readable region)! destination %rdx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: CompAction::initiate() () from /usr/lib/libcompiz_core.so.ABI-20130415 unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateScale(std::string const, int) () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::ScaleWindowGroup(std::vectorunsigned long, std::allocatorunsigned long const, int, bool) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() UpgradeStatus: Upgraded to saucy on 2013-09-23 (3 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1234241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1205888] Re: compiz crashed with SIGSEGV in CompAction::initiate()
*** This bug is a duplicate of bug 1345873 *** https://bugs.launchpad.net/bugs/1345873 ** This bug has been marked a duplicate of bug 1345873 First Use of Workspace Switcher: compiz crashed with SIGSEGV in assign_to_own() -- 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/1205888 Title: compiz crashed with SIGSEGV in CompAction::initiate() Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: .. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.0.2+13.10.20130723.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.10.0-5.15-generic 3.10.2 Uname: Linux 3.10.0-5-generic i686 ApportVersion: 2.11-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Sun Jul 28 23:33:11 2013 ExecutablePath: /usr/bin/compiz MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_IN SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0xb7773174 _ZN10CompAction8initiateEv+20:mov 0x4(%ecx),%edx PC (0xb7773174) ok source 0x4(%ecx) (0x0004) not located in a known VMA region (needed readable region)! destination %edx ok SegvReason: reading NULL VMA Signal: 11 SourcePackage: unity StacktraceTop: CompAction::initiate() () from /usr/lib/libcompiz_core.so.ABI-20130125 unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateExpo() () from /usr/lib/compiz/libunityshell.so unity::launcher::ExpoLauncherIcon::ActivateLauncherIcon(unity::launcher::ActionArg) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() 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/unity/+bug/1205888/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296078] Re: compiz crashed with SIGSEGV in unity::MultiActionList::InitiateAll()
*** This bug is a duplicate of bug 1110374 *** https://bugs.launchpad.net/bugs/1110374 ** This bug has been marked a duplicate of bug 1110374 compiz crashed with SIGSEGV in assign_to_own() -- 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/1296078 Title: compiz crashed with SIGSEGV in unity::MultiActionList::InitiateAll() Status in Unity: New Status in unity package in Ubuntu: New Bug description: When changing effects Compiz, after running 5 windows Nautilus and see the effects of the automatic reload shell Unity. Bug happened in ubuntu 14.04 c latest updates ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140320.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic i686 ApportVersion: 2.13.3-0ubuntu1 Architecture: i386 CurrentDesktop: Unity Date: Sat Mar 22 19:34:55 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-03-22 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Alpha i386 (20140321) ProcCmdline: compiz ProcEnviron: LANGUAGE=ru PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=ru_RU.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x973bff8: add%al,(%eax) PC (0x0973bff8) in non-executable VMA region: 0x08b34000-0x0aae8000 rw-p [heap] source %al ok destination (%eax) (0xbfacf180) ok SegvReason: executing writable VMA [heap] Signal: 11 SourcePackage: unity StacktraceTop: ?? () unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateScale(std::string const, int) () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::ScaleWindowGroup(std::vectorunsigned long, std::allocatorunsigned long const, int, bool) () from /usr/lib/compiz/libunityshell.so unity::launcher::ApplicationLauncherIcon::Spread(bool, int, bool) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in unity::MultiActionList::InitiateAll() 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/unity/+bug/1296078/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1212399] Re: compiz crashed with SIGSEGV in CompAction::initiate()
*** This bug is a duplicate of bug 1110374 *** https://bugs.launchpad.net/bugs/1110374 ** This bug has been marked a duplicate of bug 1110374 compiz crashed with SIGSEGV in assign_to_own() -- 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/1212399 Title: compiz crashed with SIGSEGV in CompAction::initiate() Status in Unity: Triaged Status in unity package in Ubuntu: Triaged Bug description: I clicked the icon for my browser in the bar on the left side to un- minimize one of the two browser windows (the other one was already visible). Nothing seemed to happen, and then Compiz died and was restarted. ProblemType: Crash DistroRelease: Ubuntu 13.10 Package: unity 7.1.0+13.10.20130813.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5 Uname: Linux 3.11.0-2-generic x86_64 ApportVersion: 2.12-0ubuntu3 Architecture: amd64 Date: Wed Aug 14 21:11:37 2013 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2013-06-02 (73 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) MarkForUpload: True ProcCmdline: compiz ProcEnviron: LANGUAGE=nl PATH=(custom, user) XDG_RUNTIME_DIR=set LANG=nl_NL.UTF-8 SHELL=/bin/bash SegvAnalysis: Segfault happened at: 0x7feaf27ba16d _ZN10CompAction8initiateEv+13: mov0x8(%rdi),%rdx PC (0x7feaf27ba16d) ok source 0x8(%rdi) (0x7f09) not located in a known VMA region (needed readable region)! destination %rdx ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: unity StacktraceTop: CompAction::initiate() () from /usr/lib/libcompiz_core.so.ABI-20130125 unity::MultiActionList::Initiate(std::string const, std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::MultiActionList::InitiateAll(std::vectorCompOption, std::allocatorCompOption const, int) const () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::InitiateScale(std::string const, int) () from /usr/lib/compiz/libunityshell.so unity::PluginAdapter::ScaleWindowGroup(std::vectorunsigned long, std::allocatorunsigned long const, int, bool) () from /usr/lib/compiz/libunityshell.so Title: compiz crashed with SIGSEGV in CompAction::initiate() UpgradeStatus: Upgraded to saucy on 2013-06-05 (70 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video wireshark To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1212399/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1370953] Re: layout switch is delayed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: console-setup (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/1370953 Title: layout switch is delayed Status in console-setup package in Ubuntu: Confirmed Bug description: I have two layouts configured En and Ru with Ctrl-Shift as layout switch combo. When I start typing in wrong layout I notice it, hit Ctrl-Shift and type again, but more often than not it is wrong layout again. I repeat the action, but there is no luck. On the third attemt it usually either works OR the first letter is still in wrong layout, but the second is in correct one - i.e. layout switches as I type. The explanation for this is that layout switch takes very unreasonable time - much longer than it is needed to move your fingers from one key to the other. Each time I encounter the error I retry slower so on the third attempt it is slow enough to actually recognize that layout switch is happening, but with a delay. This is extremely annoying and unacceptable. If someone knows how to work around it - please post your suggestions here. It would be nice to have a solution for 3+ layouts setup as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1370953/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1027028] Re: [regression] Drag and drop inside dash is much slower/laggy with unity 6.0
Seems fine in 14.04. ** Changed in: unity Status: Triaged = Invalid ** Changed in: unity/6.0 Status: Triaged = Invalid ** Changed in: unity (Ubuntu) Status: Triaged = Invalid -- 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/1027028 Title: [regression] Drag and drop inside dash is much slower/laggy with unity 6.0 Status in Unity: Invalid Status in Unity 6.0 series: Invalid Status in unity package in Ubuntu: Invalid Bug description: No problem with unity 5.12 and/or 5.14. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1027028/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
