[Touch-packages] [Bug 1389891] Re: error during upgrade: cannot create /dev/shm: file exists
** Branch linked: lp:ubuntu/sysvinit -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1389891 Title: error during upgrade: cannot create /dev/shm: file exists Status in “sysvinit” package in Ubuntu: Fix Committed Bug description: Setting up initscripts (2.88dsf-53.2ubuntu1) ... mkdir: cannot create directory '/dev/shm': File exists dpkg: error processing package initscripts (--configure): subprocess installed post-installation script returned error exit status 1 Perhaps missing the -p option to exit without error if the directory already exists? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: initscripts 2.88dsf-53.2ubuntu1 Uname: Linux 3.16-3-686-pae i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Thu Nov 6 00:28:02 2014 ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, user) LANG=fi_FI.UTF-8 LANGUAGE=fi:en SourcePackage: sysvinit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1389891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389891] Re: error during upgrade: cannot create /dev/shm: file exists
** Changed in: sysvinit (Ubuntu) Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sysvinit in Ubuntu. https://bugs.launchpad.net/bugs/1389891 Title: error during upgrade: cannot create /dev/shm: file exists Status in “sysvinit” package in Ubuntu: Fix Committed Bug description: Setting up initscripts (2.88dsf-53.2ubuntu1) ... mkdir: cannot create directory '/dev/shm': File exists dpkg: error processing package initscripts (--configure): subprocess installed post-installation script returned error exit status 1 Perhaps missing the -p option to exit without error if the directory already exists? ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: initscripts 2.88dsf-53.2ubuntu1 Uname: Linux 3.16-3-686-pae i686 ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 Date: Thu Nov 6 00:28:02 2014 ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, user) LANG=fi_FI.UTF-8 LANGUAGE=fi:en SourcePackage: sysvinit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/1389891/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351977] Re: New upstream release 0.9.10.0
I see WIP: https://code.launchpad.net/~mathieu-tl/network- manager/0.9.10.0 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1351977 Title: New upstream release 0.9.10.0 Status in Ubuntu GNOME: New Status in “network-manager” package in Ubuntu: Confirmed Status in “network-manager” package in Debian: Fix Released Bug description: Please update package in Utopic to 0.9.10.0. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-gnome/+bug/1351977/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391415] [NEW] totem does not play H264 any more
Public bug reported: Totem does not play H264 videos any more. It used to play them one or two weeks ago. Container does not matter, .mp4 and .mkv both don't work. AAC audio-only files do work (.m4a or .mkv containers.) If started from terminal, totem does show exactly the same messages when launched with MP4 like with WebM. But MP4 does not play, while WebM just works. Ubuntu version: 14.10 Video card: 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) ubuntu-restriced-extras is installed. I tried to reinstall all gestreamer, totem and xorg-video-* packages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgstreamer1.0-0 1.4.3-1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 11 09:32:41 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago) ** Affects: gstreamer1.0 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1391415 Title: totem does not play H264 any more Status in “gstreamer1.0” package in Ubuntu: New Bug description: Totem does not play H264 videos any more. It used to play them one or two weeks ago. Container does not matter, .mp4 and .mkv both don't work. AAC audio-only files do work (.m4a or .mkv containers.) If started from terminal, totem does show exactly the same messages when launched with MP4 like with WebM. But MP4 does not play, while WebM just works. Ubuntu version: 14.10 Video card: 00:02.0 VGA compatible controller: Intel Corporation Device 0a2e (rev 09) ubuntu-restriced-extras is installed. I tried to reinstall all gestreamer, totem and xorg-video-* packages. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: libgstreamer1.0-0 1.4.3-1 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CurrentDesktop: Unity Date: Tue Nov 11 09:32:41 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-10-08 (33 days ago) InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.2) SourcePackage: gstreamer1.0 UpgradeStatus: Upgraded to utopic on 2014-10-17 (24 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1391415/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363226] Re: /usr/bin/ubuntu-location-serviced:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_bad_function_c
** Changed in: location-service (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1363226 Title: /usr/bin/ubuntu-location- serviced:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_bad_function_call Status in “location-service” package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding location-service. This problem was most recently seen with version 2.0.1+14.10.20140825-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/dbd77e211013a84dc9db0bdaf1afe6a51c06a8f9 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1363226/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351559] Re: Apps in spread are not anti-aliased
** Branch unlinked: lp:~unity-team/unity8/rtm-14.09-staging ** Changed in: qtmir (Ubuntu RTM) Status: In Progress = Triaged ** Changed in: unity8 (Ubuntu RTM) Status: In Progress = Triaged -- 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/1351559 Title: Apps in spread are not anti-aliased Status in Qt integration with the Mir display server: Fix Released Status in “qtmir” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “qtmir” package in Ubuntu RTM: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: With qtcomp enabled, smoothing in the spread was disabled. This is unfortunately very visible on lower density devices, causing sharp edges on all diagonal lines. We need to investigate how to enable anti-aliasing with as little performance hit as possible. To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1351559/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336715] Re: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings
** Changed in: ubuntu-system-settings (Ubuntu RTM) Assignee: Michał Sawicz (saviq) = Ken VanDine (ken-vandine) -- 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/1336715 Title: [TOPBLOCKER] switch-items in indicators sometimes get out of sync with system-settings Status in Display Indicator: Invalid Status in Indicator Location: Invalid Status in Network Menu: Invalid Status in Sound Menu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Fix Released Status in “ubuntu-system-settings” package in Ubuntu RTM: In Progress Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: I noticed when testing flightmode with indicator-network that the switch items sometimes get out of sync from what GActions states on dbus are and stop updating their states when action states on dbus change. This seems to happen randomly and I have no procedure to reproduce reliably. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-display/+bug/1336715/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1368660] Re: [launcher] implement the updated visual design whereby the quicklist is positioned above the user's fingers
** Changed in: unity8 (Ubuntu RTM) Assignee: (unassigned) = Michał Sawicz (saviq) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1368660 Title: [launcher] implement the updated visual design whereby the quicklist is positioned above the user's fingers Status in Ubuntu UX bugs: Triaged Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: Triaged Bug description: - implement the updated visual design whereby the quicklist is positioned above the user's fingers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1368660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1342103] [NEW] [QtComp] Camera doesn't often work
You have been subscribed to a public bug: With QtComp ppa camera stops working only after first instance. 0. reboot phone 1. start camera, take a picture 2. close the app 3. start it again What happens: A black screen is shown with 'capture' button greyed out ** Affects: unity8 (Ubuntu) Importance: High Assignee: Gerry Boland (gerboland) Status: Fix Released ** Tags: qtcomp -- [QtComp] Camera doesn't often work https://bugs.launchpad.net/bugs/1342103 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 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 1342103] Re: [QtComp] Camera doesn't often work
** Project changed: unity8 = 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/1342103 Title: [QtComp] Camera doesn't often work Status in “unity8” package in Ubuntu: Fix Released Bug description: With QtComp ppa camera stops working only after first instance. 0. reboot phone 1. start camera, take a picture 2. close the app 3. start it again What happens: A black screen is shown with 'capture' button greyed out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1342103/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1134491] Re: [indicators] improve the indicator selection
** Changed in: unity8 (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1134491 Title: [indicators] improve the indicator selection Status in Ubuntu UX bugs: Fix Committed Status in “unity8” package in Ubuntu: Fix Released Bug description: Still not refined enough Blank bar has caused some confusion. http://www.infoworld.com/d/mobile-technology/hands-the-ubuntu-touch- linux-smartphone-213277?page=0,0: The icons are small and closely spaced, so it's easy to open a different tray than expected. See also duplicate blueprint https://blueprints.launchpad.net/ubuntu/+spec/client-1303-unity-ui- improve-indicator-selection. -- Desired solution: prototype screencast : https://drive.google.com/a/canonical.com/#folders/0B8eY_FZZ1z7IOE5uZFRJV1RVTlU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1134491/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1384357] Re: Current composition is not canceled when a text input field is cleared programmatically
I can’t observe the bug with the steps described in the original description, however I can see the text being restored when swiping from the right to show the app previews. In any case that’s most likely a bug in oxide, not in webbrowser-app. ** Changed in: webbrowser-app Status: New = Invalid -- 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/1384357 Title: Current composition is not canceled when a text input field is cleared programmatically Status in Oxide Webview: Confirmed Status in Ubuntu Keyboard: Invalid Status in Web Browser App: Invalid Status in “webbrowser-app” package in Ubuntu: Invalid Bug description: Using rtm 122 - start the webbrowser - go on google.com - type ubuntu in the google page text entry - tap the x symbol at the right of the entry - the entry is cleared and then the text is restored once you hit that issue, you can also hit another bug - type the delete key until emptying the entry, then another time - the text is restored and the delete key loop over the content To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1384357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387708] Re: [TOPBLOCKER] Location services not getting location
** Changed in: location-service (Ubuntu) Assignee: (unassigned) = Thomas Voß (thomas-voss) ** Changed in: location-service (Ubuntu) Status: Confirmed = In Progress ** Changed in: location-service (Ubuntu-rtm 14.09) Status: Confirmed = In Progress ** Branch linked: lp:~thomas-voss/location-service/fix-nm-race -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1387708 Title: [TOPBLOCKER] Location services not getting location Status in Location Service: New Status in “location-service” package in Ubuntu: In Progress Status in “location-service” package in Ubuntu RTM: In Progress Status in “location-service” source package in 14.09: In Progress Bug description: Failing to get location fix from application. Neither network based nor gps location works. Bug has now been seen on 3 phones with and without SIM installed. HERE service seems to be running, but no reasonable location is reported. GPS is failing to get fix, tested with phone placed for 2 hours outside. On two of those phones location was working fine, but with OTA update to ~135 stopped working. hard to guess working image but somewhere around 129~131 Problem is now reproducible on RTM release 137 To manage notifications about this bug go to: https://bugs.launchpad.net/location-service/+bug/1387708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378126] Re: Passcode screen misses keypresses
** Branch linked: lp:~mzanetti/unity8/keep-suspended-while-locked -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1378126 Title: Passcode screen misses keypresses Status in Ubuntu Keyboard: Incomplete Status in “unity8” package in Ubuntu: Triaged Bug description: For some reason the passcode entry screen / lock screen feels very laggy when entering my passcode. It frequently misses my keypresses, so i end up typing insufficient characters. I don't know if the hit area for the numbers is too small and I'm mis-hitting or if there is a lag/delay. I'm not typing stupendously fast, but pretty quick. Any slower and it feels very deliberate, like I'm typing a PIN into an ATM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1378126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377939] Re: Scope using location cause a dialog An unconfined application wants to access your current location
** Changed in: trust-store (Ubuntu RTM) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1377939 Title: Scope using location cause a dialog An unconfined application wants to access your current location Status in Ubuntu UX bugs: Triaged Status in Unity Online Music Scope: Invalid Status in “location-service” package in Ubuntu: Invalid Status in “trust-store” package in Ubuntu: Fix Released Status in “trust-store” package in Ubuntu RTM: Fix Released Bug description: Swiping to the flickr scope yields a confusing dialog. Build: 20141006 Clean install (--wipe) What you expected to happen If flickr/a scope wants to access my location, I expected to be asked that What happened instead I was asked if an unconfined app could use my location. unconfined An unconfined applications wants to access your current location [deny] [allow] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1377939/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391265] ProcEnviron.txt
apport information ** Attachment added: ProcEnviron.txt https://bugs.launchpad.net/bugs/1391265/+attachment/4258179/+files/ProcEnviron.txt ** Attachment removed: Dependencies.txt https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1391265/+attachment/4258178/+files/Dependencies.txt ** Attachment removed: ProcEnviron.txt https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1391265/+attachment/4258179/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10 Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1,
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10
apport information ** Tags added: apport-collected third-party-packages trusty ** Description changed: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3975 #18 0x77844045 in gtk_main () at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkmain.c:1192 #19 0x0040945e in ?? () #20 0x004097f8 in ?? () #21 0x00408c30 in ?? () #22 0x74fe5ec5 in __libc_start_main (main=0x408c20, argc=1, argv=0x7fffdd28, init=optimized out, fini=optimized out, rtld_fini=optimized out, stack_end=0x7fffdd18) at libc-start.c:287 #23 0x00408c60 in ?? ()
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10
Oops, apport-collect on a wrong computer. ** Tags removed: apport-collected third-party-packages trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10 Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3975 #18 0x77844045 in gtk_main () at /build/buildd/gtk+3.0-3.12.2/./gtk/gtkmain.c:1192 #19 0x0040945e in ?? ()
[Touch-packages] [Bug 1384357] Re: Current composition is not canceled when a text input field is cleared programmatically
The bug still happens as described here, not sure what's the difference between our devices, could be an osk configuration... -- 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/1384357 Title: Current composition is not canceled when a text input field is cleared programmatically Status in Oxide Webview: Confirmed Status in Ubuntu Keyboard: Invalid Status in Web Browser App: Invalid Status in “webbrowser-app” package in Ubuntu: Invalid Bug description: Using rtm 122 - start the webbrowser - go on google.com - type ubuntu in the google page text entry - tap the x symbol at the right of the entry - the entry is cleared and then the text is restored once you hit that issue, you can also hit another bug - type the delete key until emptying the entry, then another time - the text is restored and the delete key loop over the content To manage notifications about this bug go to: https://bugs.launchpad.net/oxide/+bug/1384357/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391452] [NEW] lxc-net fails to start properly after system crash: lock file
Public bug reported: The presence of /var/lock/lxc-net causes service lxc-net start to claim success but actually just do nothing useful. When the system goes down hard, /var/lock/lxc-net is not removed, fair enough. This means that systems require manual intervention after booting. You can reproduce the problem by crashing some processes and fiddling with lock-files, but this happens at every single hard reboot: faux@alohura:~% sudo service lxc-net stop lxc-net stop/waiting ## the presence of other dnsmasqs makes this all confusing to me, so let's just kill them anyway, even if they were started by NetworkManager faux@alohura:~% sudo killall dnsmasq faux@alohura:~% sudo killall dnsmasq dnsmasq: no process found ## simulate the lock-file being left over from a hard reboot faux@alohura:~% sudo touch /var/lock/lxc-net faux@alohura:~% sudo service lxc-net start lxc-net start/running ## we haven't bothered to start dnsmasq (or create the bridge interface or..) faux@alohura:~% ps aux | fgrep dnsmasq faux 10592 0.0 0.0 13680 2064 pts/4S+ 09:58 0:00 grep -F dnsmasq ## so containers won't start faux@alohura:~% lxc-start -n new lxc-start: lxc_start.c: main: 337 The container failed to start. lxc-start: lxc_start.c: main: 339 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 341 Additional information can be obtained by setting the --logfile and --logpriority options. faux@alohura:~% lxc-start -F -n new Error attaching veth494WIK to lxcbr0 Quota reached lxc-start: start.c: lxc_spawn: 930 failed to create the configured network lxc-start: start.c: __lxc_start: 1087 failed to spawn 'new' lxc-start: lxc_start.c: main: 337 The container failed to start. lxc-start: lxc_start.c: main: 341 Additional information can be obtained by setting the --logfile and --logpriority options. faux@alohura:~% The error message from lxc-start is very poor, too. This can be worked around by blowing away the lockfile, then restarting lxc-net. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: lxc 1.1.0~alpha2-0ubuntu3 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 Date: Tue Nov 11 09:54:59 2014 InstallationDate: Installed on 2014-04-16 (209 days ago) InstallationMedia: KernLog: ProcEnviron: SHELL=/bin/bash TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 XDG_RUNTIME_DIR=set SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug third-party-packages utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1391452 Title: lxc-net fails to start properly after system crash: lock file Status in “lxc” package in Ubuntu: New Bug description: The presence of /var/lock/lxc-net causes service lxc-net start to claim success but actually just do nothing useful. When the system goes down hard, /var/lock/lxc-net is not removed, fair enough. This means that systems require manual intervention after booting. You can reproduce the problem by crashing some processes and fiddling with lock-files, but this happens at every single hard reboot: faux@alohura:~% sudo service lxc-net stop lxc-net stop/waiting ## the presence of other dnsmasqs makes this all confusing to me, so let's just kill them anyway, even if they were started by NetworkManager faux@alohura:~% sudo killall dnsmasq faux@alohura:~% sudo killall dnsmasq dnsmasq: no process found ## simulate the lock-file being left over from a hard reboot faux@alohura:~% sudo touch /var/lock/lxc-net faux@alohura:~% sudo service lxc-net start lxc-net start/running ## we haven't bothered to start dnsmasq (or create the bridge interface or..) faux@alohura:~% ps aux | fgrep dnsmasq faux 10592 0.0 0.0 13680 2064 pts/4S+ 09:58 0:00 grep -F dnsmasq ## so containers won't start faux@alohura:~% lxc-start -n new lxc-start: lxc_start.c: main: 337 The container failed to start. lxc-start: lxc_start.c: main: 339 To get more details, run the container in foreground mode. lxc-start: lxc_start.c: main: 341 Additional information can be obtained by setting the --logfile and --logpriority options. faux@alohura:~% lxc-start -F -n new Error attaching veth494WIK to lxcbr0 Quota reached lxc-start: start.c: lxc_spawn: 930 failed to create the configured network lxc-start: start.c: __lxc_start: 1087 failed to spawn 'new' lxc-start: lxc_start.c: main: 337 The container failed to start. lxc-start: lxc_start.c: main: 341 Additional information
[Touch-packages] [Bug 1316156] Re: speakers audio won't work - pavucontrol is switching continually between speakers and headphones
I am also affected by this bug, using 14.04 LTS. Hardware: Asus Pro52H Notebook Sound-Chip is as described above: Intel HDA, AD1986A NM10/ICH7 The symptom is also as described above: In the alsamixer the port is continually switching between Speakers and Headphones. In result on the desktop you can see a constantly blinking volume display. This happens just with the basic installation (auto detection), so the default installation already leads to the bug. In can confirm that the bug is related to the auto mute feature, it only happens when auto mute is enabled. On the other hand having it disabled, I got no sound at all (though at least no blinking volume display on the screen). Currently I am using this setting in alsa-base.conf: options snd-hda-intel model=laptop-eapd position_fix=1 With this at least I got the headphones working and the blinking volume display does not appear any more. As said, speaker not working, already the speaker port is said to be not available in the sound control. Using that manual option last year I already had a fully working sound in an earlier release, I think it was 13.04, though I am not 100% sure. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1316156 Title: speakers audio won't work - pavucontrol is switching continually between speakers and headphones Status in “pulseaudio” package in Ubuntu: Confirmed Bug description: The port is continually switching between Speakers and Heaphones and no audio is outputting from the speakers. I have tried various distributions and have found that this problems is NOT present in Ubuntu 11.04, 12.04, 13.04. I have not tried 11.10, or 12.10. But have found 13.10 and 14.04 to show this identical problem. My main concern is for the 14.04 LTS version I am currently using. - I tried regulating the audio from alsamixer -by disabling auto-mute in alsamixer i managed to stop it switching from one port to the other. Still, no audio from speakers (only a regular and low-volume BUMP comes out) - I tried modifying the /etc/modprobe.d/alsa-base.conf file. Since i could not find my pc (Packard Bell EasyNote MX45) in the alsa-configuration list, i have tried using only the audio boards main info as referral (Intel HDA AD1986A NM10/ICH7). Thus i have added to the alsa-base.conf the following and rebooted after trying each and every new line (added only once per try, not all of them together). -options snd-hda-intel model=laptop -options snd-hda-intel model=laptop-eapd -options snd-hda-intel model=3stack -options snd-hda-intel model=generic - Also tried the position_fix quirking suggested on the ubuntu documentation pages -options snd-hda-intel position_fix= 1 -options snd-hda-intel position_fix= 2 The audio outputted from the speakers kept being a regular BUMP and nothing more, regardless of the input. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: xubuntu3690 F pulseaudio CasperVersion: 1.340 Date: Mon May 5 13:48:40 2014 LiveMediaBuild: Xubuntu 14.04 LTS Trusty Tahr - Release i386 (20140416.2) ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=it_IT.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/11/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T12FvNC.203 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EasyNote_MX45 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12FvNC.203:bd10/11/2006:svnPackardBellBV:pnEasyNote_MX45:pvrPB64H00206:rvnPackardBellBV:rnEasyNote_MX45:rvr1.0:cvnPackardBellBV:ct10:cvr: dmi.product.name: EasyNote_MX45 dmi.product.version: PB64H00206 dmi.sys.vendor: Packard Bell BV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1316156/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330041] Re: Bad / incorrect display accented letters in Window title bar [ast]
Confirmed. I've followed the steps in #6 and this bug affects me in 14.10 but maybe they are separated bugs. The most important issue is the inability to write accents. -- 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/1330041 Title: Bad / incorrect display accented letters in Window title bar [ast] Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: In Unity desktop, the accented letters (á , é, í, ó, ú..) aren't displayed correctly in the Window title bar when using Asturian language The bug is only reproduced in Unity. If you change to Gnome desktop (sudo apt-get install gnome-panel), window title bars are displayed correctly. In the same way, I have tested the problem and is not present in another languages like [es, ca..] To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1330041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391265] Re: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10
** Bug watch added: IBus bugs #1748 http://code.google.com/p/ibus/issues/detail?id=1748 ** Also affects: ibus via http://code.google.com/p/ibus/issues/detail?id=1748 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1391265 Title: ibus-ui-gtk3 crashed with SIGTRAP right after changing keybinding in Kubuntu 14.10 Status in IBus: Unknown Status in “ibus” package in Ubuntu: New Bug description: ## Reproduce steps 1. Launch ibus-setup 2. Change switch input method keybinding to ctrlshiftrelease 3. Restart ibus ## Expected behavior ibus running normally with the new keybinding setuped. ## Current behavior ibus crashed right after restarting with ``` traps: ibus-ui-gtk3[4182] trap int3 ip:7fb5db001d30 sp:7fffb2526670 error:0 ``` in kernel log ## Stacktrace ` (gdb) run Starting program: /usr/lib/ibus/ibus-ui-gtk3 [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. [New Thread 0x7fffedbad700 (LWP 6386)] [New Thread 0x7fffed3ac700 (LWP 6387)] [New Thread 0x7fffecbab700 (LWP 6389)] (ibus-ui-gtk3:6382): Gdk-ERROR **: The program 'ibus-ui-gtk3' received an X Window System error. This probably reflects a bug in the program. The error was 'BadValue (integer parameter out of range for operation)'. (Details: serial 647 error_code 2 request_code 131 (XInputExtension) minor_code 54) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Program received signal SIGTRAP, Trace/breakpoint trap. g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 1046/build/buildd/glib2.0-2.42.0/./glib/gmessages.c: 沒有此一檔案或目錄. (gdb) bt #0 g_logv (log_domain=0x7744c166 Gdk, log_level=G_LOG_LEVEL_ERROR, format=optimized out, args=args@entry=0x7fffd510) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1046 #1 0x755f7f6f in g_log (log_domain=log_domain@entry=0x7744c166 Gdk, log_level=log_level@entry=G_LOG_LEVEL_ERROR, format=format@entry=0x774681d7 %s) at /build/buildd/glib2.0-2.42.0/./glib/gmessages.c:1079 #2 0x7742397b in _gdk_x11_display_error_event (display=display@entry=0x687000, error=error@entry=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkdisplay-x11.c:2536 #3 0x7742c351 in gdk_x_error (xdisplay=0x6796e0, error=0x7fffd6c0) at /build/buildd/gtk+3.0-3.12.2/./gdk/x11/gdkmain-x11.c:302 #4 0x767547ed in _XError (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x80b970) at ../../src/XlibInt.c:1463 #5 0x767517e7 in handle_error (dpy=dpy@entry=0x6796e0, err=0x80b970, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:213 #6 0x767528b1 in _XReply (dpy=dpy@entry=0x6796e0, rep=rep@entry=0x7fffd880, extra=extra@entry=0, discard=discard@entry=0) at ../../src/xcb_io.c:699 #7 0x7651070d in _XIPassiveGrabDevice (dpy=0x6796e0, deviceid=1, grabtype=grabtype@entry=1, detail=optimized out, grab_window=157, cursor=cursor@entry=0, grab_mode=1, paired_device_mode=1, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:88 #8 0x7651086c in XIGrabKeycode (dpy=optimized out, deviceid=optimized out, keycode=optimized out, grab_window=optimized out, grab_mode=optimized out, paired_device_mode=optimized out, owner_events=1, mask=0x7fffd980, num_modifiers=8, modifiers_inout=0x80b9a0) at ../../src/XIPassiveGrab.c:130 #9 0x0040dffe in ?? () #10 0x00411385 in ?? () #11 0x00412d66 in ?? () #12 0x00408f5d in ?? () #13 0x75bcf274 in emit_signal_instance_in_idle_cb (data=0x7fffe80088a0) at /build/buildd/glib2.0-2.42.0/./gio/gdbusconnection.c:3753 #14 0x755f0b6d in g_main_dispatch (context=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3111 #15 g_main_context_dispatch (context=context@entry=0x673e20) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3710 #16 0x755f0f48 in g_main_context_iterate (context=0x673e20, block=block@entry=1, dispatch=dispatch@entry=1, self=optimized out) at /build/buildd/glib2.0-2.42.0/./glib/gmain.c:3781 #17 0x755f1272 in g_main_loop_run (loop=0x6c54d0) at
[Touch-packages] [Bug 1378618] Re: volume notification looks bad when an indicator is open
** Changed in: unity8 (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-sound in Ubuntu. https://bugs.launchpad.net/bugs/1378618 Title: volume notification looks bad when an indicator is open Status in Ubuntu UX bugs: Confirmed Status in “indicator-sound” package in Ubuntu: Invalid Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu RTM: Fix Released Bug description: I found this while testing silo 11 with krilling #88. Steps to reproduce: Open an indicator. Press a volume button. (see the attached screenshot) You will see that the notification appears, but it's the same color as the header. It has no borders, so you can't tell it's a popup. It looks like the header changed to something that's no properly aligned. phablet@ubuntu-phablet:~$ apt-cache policy indicator-sound indicator-sound: Instalados: 12.10.2+14.10.20141007-0ubuntu1 Candidato: 12.10.2+14.10.20141007-0ubuntu1 Tabla de versión: *** 12.10.2+14.10.20141007-0ubuntu1 0 500 http://ppa.launchpad.net/ci-train-ppa-service/landing-011/ubuntu-rtm/ 14.09/main armhf Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1378618/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391120] Re: Webapp-container problem with meteofrance website
I just installed the app from the store on my krillin (RTM proposed, #155), and it works fine. Can you try deleting the app’s cache, and let me know if it makes things better? In the terminal app on the device, just issue the following command: rm -r ~/.local/share/com.ubuntu.developer.kpeignot.meteofrance ** Changed in: webbrowser-app (Ubuntu) Status: New = Incomplete -- 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/1391120 Title: Webapp-container problem with meteofrance website Status in “webbrowser-app” package in Ubuntu: Incomplete Bug description: Hi I report this bug because there is something since the RTM with a webapp I made (webapp meteofrance). The corresponding website is http://www.meteo-france.mobi In my tests, it works well if opened manually in the web browser app but not in the webapp. In the webapp, the website begin to load but stay on an empty page with just the blue background. I never changed anything in the app and it stopped working a day (I discovered it reading comments in the software center). I tried removing the webapp patterns and remake the webapp from scratch, nothing works, it seems the problem is in the webapp- container itself (see the logs from the ubuntu sdk joined to the bug report). ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: webapp-container 0.23+14.10.20141028~rtm-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Mon Nov 10 12:18:55 2014 InstallationDate: Installed on 2014-10-31 (9 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20141031-175022) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1391120/+subscriptions -- Mailing list: https://launchpad.net/~touch-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: unity8 (Ubuntu) Status: In Progress = Fix Released ** Changed in: unity-notifications (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-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: In Progress 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 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()
I am trying to run the patch with the command: sudo patch -p1 0001-upowerd-Fix-cleanup-in-up_device_idevice_coldplug- fi.patch but the terminal get stuck for a long time without giving any output. Am I doing it wrong? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1305699 Title: upowerd crashed with SIGSEGV in service_client_free() Status in “upower” package in Ubuntu: Confirmed Bug description: it looks like nothing happend. When I switch on the PC and after loging in this window with 'report an error/bug' appeard. so I guess it is minor. thanks for doing :) ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 Date: Wed Apr 9 15:37:43 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-04-04 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta i386 (20140326) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Segfault happened at: 0xb74e9919 service_client_free+25: mov (%esi),%eax PC (0xb74e9919) ok source (%esi) (0x302e) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: upower StacktraceTop: service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 property_list_service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 ?? () g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: upowerd crashed with SIGSEGV in service_client_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391470] [NEW] returning buzz on high quality resample
Public bug reported: When I change to higher resampling it happens every few minutes repeating buzz resample-method = src-sinc-medium-quality default-sample-format = s24le default-sample-rate = 96000 $ pacmd list-sinks | grep sample sample spec: s24le 2ch 96000Hz sample spec: s32le 2ch 96000Hz I have two sound cards, the symptom emerges on the external usb X-Fi soundcard. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: pulseaudio 1:4.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: mastier 24128 F...m pulseaudio /dev/snd/controlC1: mastier 24128 F pulseaudio /dev/snd/controlC0: mastier 24128 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 11 11:56:16 2014 InstallationDate: Installed on 2012-10-25 (747 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: pulseaudio UpgradeStatus: Upgraded to utopic on 2014-11-01 (10 days ago) dmi.bios.date: 03/12/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCET98WW (2.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 34352NG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET98WW(2.58):bd03/12/2014:svnLENOVO:pn34352NG:pvrThinkPadX230Tablet:rvnLENOVO:rn34352NG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34352NG dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2014-11-11T11:31:45.523371 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1391470 Title: returning buzz on high quality resample Status in “pulseaudio” package in Ubuntu: New Bug description: When I change to higher resampling it happens every few minutes repeating buzz resample-method = src-sinc-medium-quality default-sample-format = s24le default-sample-rate = 96000 $ pacmd list-sinks | grep sample sample spec: s24le 2ch 96000Hz sample spec: s32le 2ch 96000Hz I have two sound cards, the symptom emerges on the external usb X-Fi soundcard. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: pulseaudio 1:4.0-0ubuntu22 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC1D0p: mastier 24128 F...m pulseaudio /dev/snd/controlC1: mastier 24128 F pulseaudio /dev/snd/controlC0: mastier 24128 F pulseaudio CurrentDesktop: Unity Date: Tue Nov 11 11:56:16 2014 InstallationDate: Installed on 2012-10-25 (747 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: pulseaudio UpgradeStatus: Upgraded to utopic on 2014-11-01 (10 days ago) dmi.bios.date: 03/12/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GCET98WW (2.58 ) dmi.board.asset.tag: Not Available dmi.board.name: 34352NG dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGCET98WW(2.58):bd03/12/2014:svnLENOVO:pn34352NG:pvrThinkPadX230Tablet:rvnLENOVO:rn34352NG:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 34352NG dmi.product.version: ThinkPad X230 Tablet dmi.sys.vendor: LENOVO modified.conffile..etc.pulse.daemon.conf: [modified] mtime.conffile..etc.pulse.daemon.conf: 2014-11-11T11:31:45.523371 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1391470/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 969489] Re: lightdm tries (and fails) to start too early?
It's me, again. The N54L works now, but I don't remember the changes. But today I failed to add SSD based EnhanceIO to several iSCSI based Ubuntu desktops (Intel G530 and G1610). They hung up with a blank screen and a mouse cursor in the middle. The kernel hung up, I cannot ping it. But when I booted with text mode and then sudo service lightdm start, it worked for the most times and failed for several times. It seems that lightdm or X failed if the machine STARTED TOO SOON. I tried all the walkarounds above but no one works. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/969489 Title: lightdm tries (and fails) to start too early? Status in Upstart: Confirmed Status in “lightdm” package in Ubuntu: Triaged Bug description: Sometimes lightdm comes up fine. Other times it appears to fail. x-0.log shows it tried to load 'nv' (rather than 'nvidia' which is what actually exists). When I then log into console and 'start lightdm', it comes up fine (on :1). I've not had it come up ok today, so I don't know if, when it comes up fine, it starts on :0. No idea if the lightdm.conf needs a change to 'start on'clause, or if this is just a case of a bad shipped config file (for module 'nv'). ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: lightdm 1.1.9-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12 Uname: Linux 3.2.0-20-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0-0ubuntu1 Architecture: amd64 Date: Fri Mar 30 13:40:27 2012 InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120323) ProcEnviron: TERM=xterm PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354924] Re: Networkmanager does not autoconnect to wireless network
Hi, I have a similar problem on my X230. I was previously using Arch and didn't have that bug. How can I help? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1354924 Title: Networkmanager does not autoconnect to wireless network Status in “network-manager” package in Ubuntu: Confirmed Bug description: When adding a net wireless network and enable connect automatically' networkmanager does not automatically connect to the network wenever possible. I'm running kubuntu 14.10 daily. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: network-manager 0.9.8.8-0ubuntu23 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: KDE Date: Sun Aug 10 21:30:03 2014 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-07-11 (29 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Alpha amd64 (20140710) IpRoute: default via 192.168.0.2 dev wlan0 proto static 192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.213 metric 9 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH wlan0 802-11-wireless connected /org/freedesktop/NetworkManager/Devices/1 eth0 802-3-ethernetunavailable /org/freedesktop/NetworkManager/Devices/0 nmcli-nm: RUNNING VERSIONSTATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN running 0.9.8.8connected enabled enabled enabledenabled disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1354924/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389204] Re: No Calls Today and No Messages Today go to screens with empty buttons
*** This bug is a duplicate of bug 1389225 *** https://bugs.launchpad.net/bugs/1389225 ** This bug has been marked a duplicate of private bug 1389225 -- 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/1389204 Title: No Calls Today and No Messages Today go to screens with empty buttons Status in “unity8” package in Ubuntu: Invalid Bug description: Ubuntu 14.10 r6 0. If you have made/sent/received any calls or messages today, wipe the phone. 1. Go to the Dashboard screen. 2. Tap No Calls Today or No Messages Today. 3. Tap the button. What happens: 2. You end up on a screen labelled Dashboard containing the text No Calls Today or No Messages Today and an empty button. 3. The screen goes black except for a close button in the corner. What should happen: either 2. Nothing happens, you don't end up on a separate screen; or 3. the screen does not contain a button that goes nowhere. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390490] Re: Race between connectivity-api and network-manager
This bug was fixed in the package location-service - 2.1+15.04.20141110.1-0ubuntu1 --- location-service (2.1+15.04.20141110.1-0ubuntu1) vivid; urgency=low [ thomas-voss ] * Make sure that devices being added/removed by NetworkManager are handled correctly. (LP: #1390490) -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 10 Nov 2014 20:30:56 + ** Changed in: location-service (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1390490 Title: Race between connectivity-api and network-manager Status in “location-service” package in Ubuntu: Fix Released Status in “ubuntu-location-provider-here” package in Ubuntu: Fix Released Bug description: Hi, https://bugs.launchpad.net/ubuntu/+source/location- service/+bug/1389874 was a symptom for an issue with connectivity API which doesn't work when it starts before network-manager is started or when leaving airplane mode. To reproduce, create an upstart job like connectivity.conf with: start on started dbus console log respawn respawn limit unlimited script GLOG_logtostderr=1 GLOG_v=200 export GLOG_logtostderr GLOG_v exec /home/phablet/connectivity end script with connectivity from http://people.canonical.com/~lool/connectivity Then boot with airplane mode enabled, and leave airplane mode: only cell data is logged, not wifi data. Cheers, To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1390490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389192] Re: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action
Bug still present in ubuntu-rtm/14.09-proposed-customized 14.10 r214; reopening. Now it says Please add a fitbi…, but I guess that's a layout problem on top of the contents problem. If unity8 isn't the appropriate place, please move it there. I can't be expected to know the name for a project that isn't listed on https://wiki.ubuntu.com/Avengers. ** Changed in: unity8 (Ubuntu) Status: Invalid = 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/1389192 Title: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action Status in “unity8” package in Ubuntu: New Bug description: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. What you see: Please setup an account in system settings What's wrong with this: A. Setup is a noun, so Please setup is ungrammatical. B. System Settings is a proper noun, so system settings is miscapitalized. C. A caption is a complete sentence (sometimes more than one), and this sentence is missing its period. D. There's no explanation of why you *should* set up an account. E. In system settings is a useless direction. The word Fitbit does not appear anywhere on the System Settings screen, leaving you lost. F. Sending people to System Settings is the wrong thing to do in the first place: they might already have a Fitbit account set up. What you should see: something like Track your fitness activities here using a Fitbit account. ( Use Fitbit… ) ( No Thanks ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390098] Re: Active call panel incorrectly displayed when recieving a call
I think the callIndicatorVisible flag should only be set if there are active calls and if the live call window is not active or about to be. -- 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/1390098 Title: Active call panel incorrectly displayed when recieving a call Status in Dialer app for Ubuntu Touch: Confirmed Status in “unity8” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: rtm build 140 on krillin Steps to reproduce: - open dialer - call the phone - answer the call Expected results: - dialer live call view should be displayed - no Active call panel visible Actual results: - dialer live call view displayed - Active call panel is briefly displayed and then hidden To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1390098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390098] Re: Active call panel incorrectly displayed when recieving a call
So the reason is that when the user accepts a call, the live call window takes a short while to load. Between accepting the call and the live call window showing, the CallManager.callindicatorVisible flag is set, which causes the active call hint to display. Then when the live call shows, it is unset, which hides the active call hint in the panel. I'm not sure that unity can manage this any more than it already does. ** Changed in: dialer-app Status: Incomplete = 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/1390098 Title: Active call panel incorrectly displayed when recieving a call Status in Dialer app for Ubuntu Touch: Confirmed Status in “unity8” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: rtm build 140 on krillin Steps to reproduce: - open dialer - call the phone - answer the call Expected results: - dialer live call view should be displayed - no Active call panel visible Actual results: - dialer live call view displayed - Active call panel is briefly displayed and then hidden To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1390098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391490] [NEW] indicator-power reports incorrect charge level
Public bug reported: I had my krillin sitting on a table for multiple days and now that I picked it up I immediately noticed something is wrong. indicator-power reports that there is 89% of battery left even with days of standby and this is clearly impossible based on empirical data. ** Affects: indicator-power (Ubuntu) Importance: Undecided Assignee: Charles Kerr (charlesk) Status: New ** Changed in: indicator-power (Ubuntu) Assignee: (unassigned) = Charles Kerr (charlesk) -- 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/1391490 Title: indicator-power reports incorrect charge level Status in “indicator-power” package in Ubuntu: New Bug description: I had my krillin sitting on a table for multiple days and now that I picked it up I immediately noticed something is wrong. indicator-power reports that there is 89% of battery left even with days of standby and this is clearly impossible based on empirical data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1391490/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391493] [NEW] Location tagging doesn't work for videos
Public bug reported: Steps to reproduce: 1. Open the Camera application 2. Switch to Video mode 3. Swipe up to reveal the sub-controls 4. Tap on Location 5. Tap On 6. Wait for several minutes to allow a fix to be retrieved 7. Record a short video Expected result: When viewing EXIF data for the video, location information is present Actual result: When viewing EXIF data, location information is not present ** Affects: camera-app (Ubuntu) Importance: Undecided Status: New ** Tags: qa-daily-testing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to camera-app in Ubuntu. https://bugs.launchpad.net/bugs/1391493 Title: Location tagging doesn't work for videos Status in “camera-app” package in Ubuntu: New Bug description: Steps to reproduce: 1. Open the Camera application 2. Switch to Video mode 3. Swipe up to reveal the sub-controls 4. Tap on Location 5. Tap On 6. Wait for several minutes to allow a fix to be retrieved 7. Record a short video Expected result: When viewing EXIF data for the video, location information is present Actual result: When viewing EXIF data, location information is not present To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/camera-app/+bug/1391493/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1296133] Re: Suspend and hibernate missing from KMenu and Power Management in System settings
14.04 LTS Pressed the power button today to suspend ( just like everyday for the past four years on this laptop ) and nothing happened. Sure enough, 'suspend' has vanished from all the KDE options. However upower -d reports: Daemon: daemon-version: 0.9.23 can-suspend: yes Toggling Power Manager off and on again had no effect. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1296133 Title: Suspend and hibernate missing from KMenu and Power Management in System settings Status in “upower” package in Ubuntu: Confirmed Bug description: I have used install scripts to install Kubuntu 14.04 on three completely different systems. Although the packages installed are basically the same, one of the system has no Suspend/hibernate options in the KMenu nor in the Power management in the KDE System settings. Since this is a laptop, this also means that the battery life is greatly reduced, because it cannot go to standby when lid is closed or when it's idle. Interestingly, If I logout, there is a Standby button on the lighdm login screen. If I click it, the laptop goes to standby and wakes up without problems. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 CurrentDesktop: KDE Date: Sat Mar 22 21:18:53 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-14 (8 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Alpha amd64 (20140130) SourcePackage: upower UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1296133/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389195] Re: Fitbit section in Dashboard goes to an empty screen when tapped
Bug still present in ubuntu-rtm/14.09-proposed-customized 14.10 r214; reopening. Now the screen has its own title (good!), and it isn't completely empty, but only because it contains the same awkward text as the parent screen did (bug 1389192). If the parent screen was sufficiently explanatory, you shouldn't be able to get to this screen at all. But if you can get to it, it should contain much more -- for example, a semi-transparent mockup of how the screen might look once you set up your account. If unity8 isn't the appropriate place for this bug report, please move it there. I can't be expected to know the name for a project that isn't listed on https://wiki.ubuntu.com/Avengers. ** Changed in: unity8 (Ubuntu) Status: Invalid = New ** Description changed: - Ubuntu 14.10 r6 + Ubuntu 14.10 RTM r6 + Ubuntu 14.10 RTM-proposed r214 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. 2. Tap anywhere in the section, which is quite easy to do by accident. What happens: - * You end up on a Dashboard screen that is completely empty. - * If you didn't notice that a Back button has appeared next to Dashboard, you might reasonably conclude that the Dashboard has broken. + * You end up on a Dashboard screen that contains only vague text about setting up an account (same as bug 1389192). What should happen: either * If you have no Fitbit account, the section should not go to a separate screen, or - * if it does go to a separate screen, it should not be called Dashboard and should not be empty. + * if it does go to a separate screen, it should contain more obvious explanation of the benefit and method of adding an account. ** Summary changed: - Fitbit section in Dashboard goes to an empty screen when tapped + Fitbit section in Dashboard goes to a near-empty screen when tapped -- 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/1389195 Title: Fitbit section in Dashboard goes to a near-empty screen when tapped Status in “unity8” package in Ubuntu: New Bug description: Ubuntu 14.10 RTM r6 Ubuntu 14.10 RTM-proposed r214 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. 2. Tap anywhere in the section, which is quite easy to do by accident. What happens: * You end up on a Dashboard screen that contains only vague text about setting up an account (same as bug 1389192). What should happen: either * If you have no Fitbit account, the section should not go to a separate screen, or * if it does go to a separate screen, it should contain more obvious explanation of the benefit and method of adding an account. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1292434] Re: rsyslog cannot start from /etc/init.d
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: rsyslog (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1292434 Title: rsyslog cannot start from /etc/init.d Status in “rsyslog” package in Ubuntu: Confirmed Bug description: Hi folks, I am running rsyslog on the new Trusty and I got the issue starting the process with old init.d system: - root@trusty01:~# /etc/init.d/rsyslog status * rsyslogd is running root@trusty01:~# /etc/init.d/rsyslog stop root@trusty01:~# /etc/init.d/rsyslog status * rsyslogd is running root@trusty01:~# service rsyslog stop rsyslog stop/waiting root@trusty01:~# /etc/init.d/rsyslog status * rsyslogd is not running root@trusty01:~# /etc/init.d/rsyslog start root@trusty01:~# /etc/init.d/rsyslog status * rsyslogd is not running root@trusty01:~# service rsyslog start rsyslog start/running, process 1130 - About the package I am running : rsyslog 7.4.4-1ubuntu2amd64 on Release: 14.04 I would expect it either to stop and start the daemon correctly or to exit with a nice error message saying I am deprecated, please use ... Thanks, Remi Debay To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1292434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387714] Re: Automatic space insertion fails when top replying to emails in gmail
** Changed in: ubuntu-keyboard Status: In Progress = Fix Released -- 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/1387714 Title: Automatic space insertion fails when top replying to emails in gmail Status in Ubuntu Keyboard: Fix Released Status in “ubuntu-keyboard” package in Ubuntu: Fix Released Status in “ubuntu-keyboard” package in Ubuntu RTM: Fix Released Bug description: Steps to reproduce 1) Reply to an email in gmail 2) Type a sentence above the quoted text and press full stop 3) Enter another word and press space Expected result A space is entered after the new word Actual result No space is entered. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1387714/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391498] Re: [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps
** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New ** No longer affects: unity8 ** Changed in: unity8 (Ubuntu) Status: New = Invalid ** Also affects: unity-scope-click (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1391498 Title: [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps Status in Ubuntu UX bugs: Fix Committed Status in “unity-scope-click” package in Ubuntu: New Status in “unity8” package in Ubuntu: Invalid Bug description: [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 853865] Re: Multi Monitor: Option to hide unity's top panel on the second monitor
I would like to have this option... -- 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/853865 Title: Multi Monitor: Option to hide unity's top panel on the second monitor Status in Unity: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: Some presentations are given full screen on the second monitor while someone is still working on another screen. Many people use lyricue for example. But the panel is very distractive being always on top, thus making unity unacceptable for presentations. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/853865/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390098] Re: Active call panel incorrectly displayed when recieving a call
** Branch linked: lp:~nick-dedekind/dialer-app/lp1390098.active-call- hint ** Changed in: dialer-app Assignee: Gustavo Pichorim Boiko (boiko) = Nick Dedekind (nick-dedekind) -- 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/1390098 Title: Active call panel incorrectly displayed when recieving a call Status in Dialer app for Ubuntu Touch: Confirmed Status in “unity8” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: rtm build 140 on krillin Steps to reproduce: - open dialer - call the phone - answer the call Expected results: - dialer live call view should be displayed - no Active call panel visible Actual results: - dialer live call view displayed - Active call panel is briefly displayed and then hidden To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1390098/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391498] Re: [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps
** No longer affects: unity8 (Ubuntu) -- 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/1391498 Title: [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps Status in Ubuntu UX bugs: Fix Committed Status in “unity-scope-click” package in Ubuntu: New Bug description: [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391498/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] [NEW] Calendar reminders should not use the alarm role
Public bug reported: 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) ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid ** Also affects: ubuntu-ux Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1391501 Title: Calendar reminders should not use the alarm role 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/ubuntu-ux/+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 1377334] Re: cancel content-hub operation crash contacts
** Changed in: content-hub Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1377334 Title: cancel content-hub operation crash contacts Status in Address Book App: Invalid Status in Camera App: Invalid Status in Content sharing/picking infrastructure and service: Fix Released Status in Dialer app for Ubuntu Touch: Invalid Status in “content-hub” package in Ubuntu: Fix Released Status in “content-hub” package in Ubuntu RTM: Fix Released Bug description: i couldn't find the contacts app project, so i thought maybe dialer is correct I signed into google and accepted terms to sync contacts i went to contacts to create a new one filled out name, ph# etc took a picture before i could save it, a pop up said syncing contacts i hit cancel. The app became completely unresponsive. shell and other apps were fine. To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1377334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388582] Re: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks
- #23: With 3stack model, i have the same behavior of missing sound in speakers when i plug-in/plug-out, and even is worse, because appears 3 inputs (Mic, Internal Mic, Line In) recording only Mic with a lot of noise. - #24: About the cuestion, I think it's a problem of upgrading VS. clean install. I have a similar problem, i have 13.10 (Installed first in 12.04 and upgrading until 13.10) with sound working but if i use the 13.10 liveCD the sound isn't working. Maybe some config files kept or else makes using AD198x instead AD1986A in my case, and when i made a clean install i discover the problem. In his case, the sound don't work properly in 12.04... but in my case with the liveCD 12.04.5 works, maybe there is something different there... - #22: do you think i should send this bug to the kernel bugtracker with all the information? I want first be sure it isn't a mismatch configuration, common bug related to the distrubution, or a fixed bug in a newer kernel version. Isn't it? -- 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/1388582 Title: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have a fresh install of KUbuntu 14.10 with this problem and i come of a KUbuntu 13.10 without problems. I don't have any sound from speakers or headphone, i think the driver isn't loaded, but the microphone works, it records. The sound playback works too, but the sound doesn't go through speakers or headphones. I was testing with a lot of LiveCD KUbuntu when the problem comes. With LiveCDs KUbuntu 12.04.5 LTS, 12.10, 13.04 the sound works, they configs the sound system as HDA Intel AD198x. Since LiveCDs 13.10, 14.04.1 LTS and, of course, 14.10 Live CD and my install, i have this problem, because the sound system is now AD1986A. I will attach the alsa-info output for all this systems in my computer. But with HDA_Analyzer http://www.alsa- project.org/main/index.php/HDA_Analyzer i found the details of the problem: i can create a python script to brought back the sound working in a basic mode, like as previously. The details are activating EAPD in Card 0, Codec 0, Node 0x1b PIN (In my computer, it could be different in another) what brought back the sound to the speakers, and unmuting Output Amplifier in Card 0, Codec 0, Node 0x1a VAL[0] and VAL[1] to brought back sound to the headphones when they are plugged. I will attach too the output of this diff and the python script created by HDA_Analyzer for my system. At least, the basic working state should be back, because with a untoching fresh install there isn't any sound. There are related bugs here and other post in internet, but i collected all information i found and can give more if it's necessary. For additional information: Searching the solution, i tested too all the models availables for HDA Intel AD1986A (editing /etc/modprobe.d /alsa-base.conf with AD1986A models /usr/share/doc/alsa-base/driver /HD-Audio-Models.txt.gz) and i found the default one doesn't fit my system and anothers are better, but have problems of no sound too and i don't found how to fix these problem. When this bug is corrected, i want to help to found a better model for my computer, i don't know how now, but first it brought back the sound. Also, i test with snd-hda- tools https://launchpad.net/~diwic/+archive/ubuntu/hda and with hda- jack-sense-test the Green Line Out sense doesn't work (always NO present) but the Pink Mic sense works without problems. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thywalls 2380 F pulseaudio CurrentDesktop: KDE Date: Sun Nov 2 16:24:36 2014 InstallationDate: Installed on 2014-10-30 (3 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T12JNC.206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EasyNote_MX65 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12JNC.206:bd09/28/2006:svnPackardBellBV:pnEasyNote_MX65:pvrPB63E03104:rvnPackardBellBV:rnEasyNote_MX65:rvr1.0:cvnPackardBellBV:ct10:cvr:
[Touch-packages] [Bug 1382283] Re: wifi toggle interrupts sound playback
This bug hasn't been reassigned to a lower level component. I want to make sure this gets assigned to the correct module and on someone's backlog to fix this as it's a pretty visible bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1382283 Title: wifi toggle interrupts sound playback Status in “network-manager” package in Ubuntu: Confirmed Bug description: Not really sure where this bug should go, but on recent rtm krillin images (such as 112), turning wifi on/off in the network indicator causes a brief interruption in music playback. Steps to reproduce the issue: 1. Start playing a song in the music app. 2. Pull down the network indicator. 3. Toggle wi-fi on or off. For some reason, this makes the sound pause for a moment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1382283/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389192] Re: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action
Marking invalid and moving to hanloon, as I mentioned before on IRC since this is not a public scope. ** Changed in: unity8 (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1389192 Title: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action Status in “unity8” package in Ubuntu: Invalid Bug description: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. What you see: Please setup an account in system settings What's wrong with this: A. Setup is a noun, so Please setup is ungrammatical. B. System Settings is a proper noun, so system settings is miscapitalized. C. A caption is a complete sentence (sometimes more than one), and this sentence is missing its period. D. There's no explanation of why you *should* set up an account. E. In system settings is a useless direction. The word Fitbit does not appear anywhere on the System Settings screen, leaving you lost. F. Sending people to System Settings is the wrong thing to do in the first place: they might already have a Fitbit account set up. What you should see: something like Track your fitness activities here using a Fitbit account. ( Use Fitbit… ) ( No Thanks ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389192] Re: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action
Moved to https://bugs.launchpad.net/hanloon/+bug/1391512 -- 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/1389192 Title: Fitbit text in Dashboard has poor grammar, capitalization, punctuation, and call to action Status in “unity8” package in Ubuntu: Invalid Bug description: Ubuntu 14.10 r6 0. Remove your Fitbit account from the phone if you have one. 1. Go to the Dashboard screen and scroll to Fitbit. What you see: Please setup an account in system settings What's wrong with this: A. Setup is a noun, so Please setup is ungrammatical. B. System Settings is a proper noun, so system settings is miscapitalized. C. A caption is a complete sentence (sometimes more than one), and this sentence is missing its period. D. There's no explanation of why you *should* set up an account. E. In system settings is a useless direction. The word Fitbit does not appear anywhere on the System Settings screen, leaving you lost. F. Sending people to System Settings is the wrong thing to do in the first place: they might already have a Fitbit account set up. What you should see: something like Track your fitness activities here using a Fitbit account. ( Use Fitbit… ) ( No Thanks ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1389192/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391521] [NEW] can't type accented letters in ubuntu 14.10 [ast]
Public bug reported: Hi, after a fresh install of Ubuntu 14.10, ( and repositories proposed, and backports enabled ) , and a full update, it's impossible to use/type/write accented letters in Asturian languages. I've tested in other languages and this issue is not present. If user choose Asturian language, and Asturian keyboard, it's impossible to type á,é,í,ó,ú, ü, ñ. Steps to reproduce it: 1- Change language to Asturian 2- Change keyboard (Launcher--System settings--Text entry--Asturian (Spain, with bottom-dot H and bottom-dot L). 3- Add it. 4- In the top panel, clic and select the text entry: Asturian 5- Open a .txt file, and try to type á,é,í, ó,ú, ü,ñ (it will doesn't work) (if language system is another one, all keyboards works. If we choose Asturian, no one keyboard works, and is not possible to use accents) I thought this bug was related to: https://bugs.launchpad.net/unity/+bug/1330041 but we think they are different issues. Anyway, this bug has high importance for Asturian users, because they can't write a document, search in browser or write an email properly. More information: lsb_release -rd Description:Ubuntu 14.10 Release:14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Nov 11 14:39:13 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- 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/1391521 Title: can't type accented letters in ubuntu 14.10 [ast] Status in “unity” package in Ubuntu: New Bug description: Hi, after a fresh install of Ubuntu 14.10, ( and repositories proposed, and backports enabled ) , and a full update, it's impossible to use/type/write accented letters in Asturian languages. I've tested in other languages and this issue is not present. If user choose Asturian language, and Asturian keyboard, it's impossible to type á,é,í,ó,ú, ü, ñ. Steps to reproduce it: 1- Change language to Asturian 2- Change keyboard (Launcher--System settings--Text entry--Asturian (Spain, with bottom-dot H and bottom-dot L). 3- Add it. 4- In the top panel, clic and select the text entry: Asturian 5- Open a .txt file, and try to type á,é,í, ó,ú, ü,ñ (it will doesn't work) (if language system is another one, all keyboards works. If we choose Asturian, no one keyboard works, and is not possible to use accents) I thought this bug was related to: https://bugs.launchpad.net/unity/+bug/1330041 but we think they are different issues. Anyway, this bug has high importance for Asturian users, because they can't write a document, search in browser or write an email properly. More information: lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Nov 11 14:39:13 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) 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/1391521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330041] Re: Bad / incorrect display accented letters in Window title bar [ast]
I've open a separated bug, because maybe they are different issues. This bug is for Unity displaying accented letters in window title bar. This one: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1391521 is for the impossibility to type/write accented letters when using Asturian language. -- 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/1330041 Title: Bad / incorrect display accented letters in Window title bar [ast] Status in Unity: Confirmed Status in Unity 7.2 series: Confirmed Status in “unity” package in Ubuntu: Confirmed Bug description: In Unity desktop, the accented letters (á , é, í, ó, ú..) aren't displayed correctly in the Window title bar when using Asturian language The bug is only reproduced in Unity. If you change to Gnome desktop (sudo apt-get install gnome-panel), window title bars are displayed correctly. In the same way, I have tested the problem and is not present in another languages like [es, ca..] To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1330041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391522] [NEW] tel:/// URLs dispatched when phone is locked are not respected
Public bug reported: Steps to reproduce: * have a passcode-locked phone * run: $ gdbus call -e -d com.canonical.URLDispatcher -o /com/canonical/URLDispatcher -m com.canonical.URLDispatcher.DispatchURL 'tel:///1234' '' * type the passcode Expected: * dialer opens with 1234 typed in the number box Current: * dialer opens blank or with 1234 that resets to blank a split second later ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20141106-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf Date: Tue Nov 11 14:29:21 2014 InstallationDate: Installed on 2014-11-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (2014-020204) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: dialer-app (Ubuntu) Importance: Undecided Assignee: Gustavo Pichorim Boiko (boiko) Status: New ** Tags: apport-bug armhf vivid -- 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/1391522 Title: tel:/// URLs dispatched when phone is locked are not respected Status in “dialer-app” package in Ubuntu: New Bug description: Steps to reproduce: * have a passcode-locked phone * run: $ gdbus call -e -d com.canonical.URLDispatcher -o /com/canonical/URLDispatcher -m com.canonical.URLDispatcher.DispatchURL 'tel:///1234' '' * type the passcode Expected: * dialer opens with 1234 typed in the number box Current: * dialer opens blank or with 1234 that resets to blank a split second later ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20141106-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf Date: Tue Nov 11 14:29:21 2014 InstallationDate: Installed on 2014-11-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (2014-020204) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1391522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391522] Re: tel:/// URLs dispatched when phone is locked are not respected
** Changed in: dialer-app (Ubuntu) Assignee: (unassigned) = Gustavo Pichorim Boiko (boiko) -- 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/1391522 Title: tel:/// URLs dispatched when phone is locked are not respected Status in “dialer-app” package in Ubuntu: New Bug description: Steps to reproduce: * have a passcode-locked phone * run: $ gdbus call -e -d com.canonical.URLDispatcher -o /com/canonical/URLDispatcher -m com.canonical.URLDispatcher.DispatchURL 'tel:///1234' '' * type the passcode Expected: * dialer opens with 1234 typed in the number box Current: * dialer opens blank or with 1234 that resets to blank a split second later ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: dialer-app 0.1+15.04.20141106-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu10 Architecture: armhf Date: Tue Nov 11 14:29:21 2014 InstallationDate: Installed on 2014-11-11 (0 days ago) InstallationMedia: Ubuntu Vivid Vervet (development branch) - armhf (2014-020204) SourcePackage: dialer-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dialer-app/+bug/1391522/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1387031] Re: No packages recognized as official until first update
** Summary changed:
- software-properties is *not* an offical package from Ubuntu -- can't
create bug report
+ No packages recognized as official until first update
** Description changed:
Steps to reproduce this:
- Open up a Terminal, then type:
+ 1. Install Ubuntu and start it for the first time.
+ 2. In a terminal, type: ubuntu-bug {any package name}
- sudo ubuntu-bug software-properties-common
-
- After a few seconds a window opens up and it says:
+ What happens: After a few seconds a window opens up and it says:
Das Problem kann nicht gemeldet werden:
Dies ist kein offizielles Ubuntu-Paket. Bitte entfernen Sie alle Pakete von
Drittanbietern und wiederholen Sie den Vorgang.
Translation:
(The problem can not reported:
- This is not a offical Ubuntu package. Please remove all packages from 3rd
Party and retry the process.)
+ This is not a official Ubuntu package. Please remove all packages from 3rd
Party and retry the process.)
** Changed in: software-properties (Ubuntu)
Status: Incomplete = New
** Package changed: software-properties (Ubuntu) = apport (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1387031
Title:
No packages recognized as official until first update
Status in “apport” package in Ubuntu:
New
Bug description:
Steps to reproduce this:
1. Install Ubuntu and start it for the first time.
2. In a terminal, type: ubuntu-bug {any package name}
What happens: After a few seconds a window opens up and it says:
Das Problem kann nicht gemeldet werden:
Dies ist kein offizielles Ubuntu-Paket. Bitte entfernen Sie alle Pakete von
Drittanbietern und wiederholen Sie den Vorgang.
Translation:
(The problem can not reported:
This is not a official Ubuntu package. Please remove all packages from 3rd
Party and retry the process.)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1387031/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305699] Re: upowerd crashed with SIGSEGV in service_client_free()
This is a source code patch, you would need to rebuild the package after you apply it so a source. patch -p1 0001-upowerd-Fix-cleanup-in-up_device_idevice_coldplug- fi.patch - this is how you can apply it to the source. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upower in Ubuntu. https://bugs.launchpad.net/bugs/1305699 Title: upowerd crashed with SIGSEGV in service_client_free() Status in “upower” package in Ubuntu: Confirmed Bug description: it looks like nothing happend. When I switch on the PC and after loging in this window with 'report an error/bug' appeard. so I guess it is minor. thanks for doing :) ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: upower 0.9.23-2ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic i686 ApportVersion: 2.14.1-0ubuntu1 Architecture: i386 Date: Wed Apr 9 15:37:43 2014 ExecutablePath: /usr/lib/upower/upowerd InstallationDate: Installed on 2014-04-04 (5 days ago) InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Beta i386 (20140326) ProcCmdline: /usr/lib/upower/upowerd ProcEnviron: SegvAnalysis: Segfault happened at: 0xb74e9919 service_client_free+25: mov (%esi),%eax PC (0xb74e9919) ok source (%esi) (0x302e) not located in a known VMA region (needed readable region)! destination %eax ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: upower StacktraceTop: service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 property_list_service_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 lockdownd_client_free () from /usr/lib/i386-linux-gnu/libimobiledevice.so.4 ?? () g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0 Title: upowerd crashed with SIGSEGV in service_client_free() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1305699/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383277] Re: Power dialog sometimes shown on resume
In my experience, this was because we load the greeter synchronously, blocking handling of the power-release event. If loading the greeter took longer than 2s, the dialog would come up because it never saw the power-release event. And often loading the background image could slow that down enough for 2s. Or maybe that dbus-daemon hogging the CPU could also exacerbate it. But the branch that was linked *was* relevant because it made the problem exceedingly difficult to experience (I never did), despite the fact that it didn't *fix* the problem of synchronously loading. But with the linked branch [1] we are just loading QML code instead of image files, which is small enough to not delay loading over 2s. Simply making the greeter load async (by setting asynchronous: true on its loader) is actually a little tough, because of timing issues. [1] https://code.launchpad.net/~mterry/unity8/cache-greeter- bg/+merge/239144 -- 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/1383277 Title: Power dialog sometimes shown on resume Status in “unity8” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: Unfortunately no good steps to reproduce, other than resume your phone, from time to time you'll get the power dialog displayed on screen. The reason for this could be twofold: a) you pressed the power button in your pocket b) input is confused and keyUp event does not reach unity8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383277/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1386682] Re: Facebook share is broken
** Branch linked: lp:~abreu-alexandre/webbrowser-app/fix-facebook-hub- share-rtm-09 ** Description changed: - Facebook share is broken + Facebook share is broken. + + Testing: + - make sure that you have a facebook account in the system settings, + - go to the gallery app, + - select a photo, + - go to the share menu at the top and click share, + - select the facebook app, + - the app should start, there should be a sharing dialog with the picture, + - enter some text in the text field and click share, + - the screen should refresh (after the post is done) and you should see the picture with the text in your wall, ** Changed in: webbrowser-app (Ubuntu RTM) Status: New = In Progress ** Changed in: webbrowser-app (Ubuntu RTM) Assignee: (unassigned) = Alexandre Abreu (abreu-alexandre) -- 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/1386682 Title: Facebook share is broken Status in The Webapps-core project: Fix Released Status in Web Browser App: Fix Released Status in “webbrowser-app” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu RTM: In Progress Bug description: Facebook share is broken. Testing: - make sure that you have a facebook account in the system settings, - go to the gallery app, - select a photo, - go to the share menu at the top and click share, - select the facebook app, - the app should start, there should be a sharing dialog with the picture, - enter some text in the text field and click share, - the screen should refresh (after the post is done) and you should see the picture with the text in your wall, To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1386682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385331] Re: Notification LED stays on when no messages in notification center
** Branch linked: lp:~nick-dedekind/unity8/lp1385331.led -- 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/1385331 Title: Notification LED stays on when no messages in notification center Status in “unity8” package in Ubuntu: New Bug description: Observed the notification LED staying on even though there were no notifications in the indicators and the notification icon was greyed out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1389336] Re: Use geoclue-2.0
Seb, this bug is about finding some solution for the geoclue-2.0 world, such as patching geoclue-2.0 directly or some such. I had assumed we didn't plan on staying with geoclue-1.0 forever? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtlocation-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1389336 Title: Use geoclue-2.0 Status in “empathy” package in Ubuntu: New Status in “gnome-settings-daemon” package in Ubuntu: New Status in “libunity-webapps” package in Ubuntu: New Status in “qtlocation-opensource-src” package in Ubuntu: New Status in “ubuntu-geoip” package in Ubuntu: New Status in “webkitgtk” package in Ubuntu: New Bug description: Geoclue2 (source package geoclue-2.0) is a separate, parallel- installable version of geoclue1 (source package geoclue). We will likely shortly have both in main (see MIR bug 1388294) and it would be great to be able to demote geoclue1 to universe and only support one version of the service. The packages associated with this bug all have a reverse depends on geoclue1 in some form or patches to remove support for geoclue-2.0 because it wasn't in main yet (e.g. gnome-settings-daemon). Porting from geoclue-1.0 to 2.0 apparently isn't terribly trivial. But we have at least six months to do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/1389336/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1260981] Re: multiple certificate prompts for self-signed certificate
Looks like this was fixed at some point, I’m now getting only one security warning, and it’s not a prompt anymore. ** Changed in: webbrowser-app Status: Triaged = Fix Released ** Changed in: webbrowser-app (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1260981 Title: multiple certificate prompts for self-signed certificate Status in Web Browser App: Fix Released Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: If I go to a site that serves content with a self-signed or otherwise invalid certificate, I get a prompt that says: This connection is untrusted You are trying to securely reach foo, but the security certificate of this website is not trusted. Proceed Anyway Back to safety However, if the site delivers lots of content via https, multiple prompts are given to the user. I couldn't remember the site that I discovered this on, so I googled and found: https://www.pcwebshop.co.uk Navigating to this site in webbrowser-app will prompt the user with 7-14 certificate prompts. Furthermore, clicking 'Back to safety' I need to click through 3 times and it doesn't seem to actually do anything (ie, the site is still displayed-- perhaps in reduced form, I'm not sure). To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1260981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391521] Re: can't type accented letters in ubuntu 14.10 [ast]
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/1391521 Title: can't type accented letters in ubuntu 14.10 [ast] Status in “unity” package in Ubuntu: Confirmed Bug description: Hi, after a fresh install of Ubuntu 14.10, ( and repositories proposed, and backports enabled ) , and a full update, it's impossible to use/type/write accented letters in Asturian languages. I've tested in other languages and this issue is not present. If user choose Asturian language, and Asturian keyboard, it's impossible to type á,é,í,ó,ú, ü, ñ. Steps to reproduce it: 1- Change language to Asturian 2- Change keyboard (Launcher--System settings--Text entry--Asturian (Spain, with bottom-dot H and bottom-dot L). 3- Add it. 4- In the top panel, clic and select the text entry: Asturian 5- Open a .txt file, and try to type á,é,í, ó,ú, ü,ñ (it will doesn't work) (if language system is another one, all keyboards works. If we choose Asturian, no one keyboard works, and is not possible to use accents) I thought this bug was related to: https://bugs.launchpad.net/unity/+bug/1330041 but we think they are different issues. Anyway, this bug has high importance for Asturian users, because they can't write a document, search in browser or write an email properly. More information: lsb_release -rd Description: Ubuntu 14.10 Release: 14.10 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity 7.3.1+14.10.20141016-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7 Uname: Linux 3.16.0-25-generic x86_64 ApportVersion: 2.14.7-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CurrentDesktop: Unity Date: Tue Nov 11 14:39:13 2014 InstallationDate: Installed on 2014-11-10 (0 days ago) InstallationMedia: Ubuntu 14.10 Utopic Unicorn - Release amd64 (20141022.1) 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/1391521/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315634] Re: gdb does not show heap arrays in fortran
Worked around by installing gdb from opensuse RPM package with alien. It issues a lot of warnings and sometimes crashes, but nore or less usable in Ubuntu. -- 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/1315634 Title: gdb does not show heap arrays in fortran Status in “gdb” package in Ubuntu: New Bug description: The problem description can be found in many places over the internet, e.g. here: http://numericalnoob.blogspot.fi/2012/08/fortran-allocatable-arrays-and-pointers.html When debugging simple program program test integer, parameter :: ndata = 8, ndim = 2 real :: my_stack(ndata) real, allocatable, target:: my_heap(:) real, pointer:: my_ptr(:,:,:) allocate(my_heap(ndata)) ! read stuff do i=1,ndata my_stack(i) = real(i) end do my_heap = my_stack my_ptr(1:ndim,1:ndim,1:ndim) = my_heap write(*,*) my_stack write(*,*) my_heap write(*,*) my_ptr end program test With gdb from distro (GNU gdb (Ubuntu 7.7-0ubuntu3) 7.7) I get: Breakpoint 1, test () at test.f90:13 13write(*,*) my_stack (gdb) p my_stack $1 = (1, 2, 3, 4, 5, 6, 7, 8) (gdb) p my_heap $2 = (0) (gdb) p my_ptr $3 = (( ( 0) ) ) (gdb) With properly compiled gdb on another computer (GNU gdb (GDB) SUSE (7.5.1-0.7.29)) i get Breakpoint 1, test () at test.f90:13 13write(*,*) my_stack (gdb) p my_stack $1 = (1, 2, 3, 4, 5, 6, 7, 8) (gdb) p my_heap $2 = (1, 2, 3, 4, 5, 6, 7, 8) (gdb) p my_ptr $3 = (( ( 1, 2) ( 3, 4) ) ( ( 5, 6) ( 7, 8) ) ) (gdb) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1315634/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391498] Re: [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps
** Changed in: unity-scope-click (Ubuntu) Importance: Undecided = Critical -- 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/1391498 Title: [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps Status in Ubuntu UX bugs: Fix Committed Status in “unity-scope-click” package in Ubuntu: New Bug description: [Dash] In the app scope, replace the Ubuntu icon in the header with the word Apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1391498/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385331] Re: Notification LED stays on when no messages in notification center
** Branch linked: lp:~nick-dedekind/qmenumodel/lp1385331.led -- 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/1385331 Title: Notification LED stays on when no messages in notification center Status in “unity8” package in Ubuntu: New Bug description: Observed the notification LED staying on even though there were no notifications in the indicators and the notification icon was greyed out. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1385331/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388235] Re: Battery icon turns red at 30%
I'd just follow what we have with some other phones, and showing low battery only when 15% -- 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/1388235 Title: Battery icon turns red at 30% Status in Ubuntu UX bugs: Confirmed Status in “indicator-power” package in Ubuntu: Confirmed Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1388235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1332440] Re: apt-get update very slow when ulimit -n is big
I can also confirm this running docker with the library/ubuntu:14.04
image on a virtualbox host running ubuntu 14.04
running apt-get update times out or takes an extremely long time.
Host Virtualbox:
$ ulimit -n
1024
docker container:
root@1518e024f53a:/# ulimit -n
524288
root@1518e024f53a:/# time apt-get update
real0m47.489s
user0m24.408s
sys 0m21.516s
root@1518e024f53a:/# ulimit -n 10
root@1518e024f53a:/# time apt-get update
real0m11.165s
user0m6.598s
sys 0m4.359s
root@1518e024f53a:/# ulimit -n 1024
root@1518e024f53a:/# time apt-get update
real0m3.109s
user0m2.543s
sys 0m0.374s
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1332440
Title:
apt-get update very slow when ulimit -n is big
Status in “apt” package in Ubuntu:
Confirmed
Bug description:
I use strace to see why apt-get update is too slow,
finally I found apt-get loop 3~n to '(? , F_SETFD, FD_CLOEXEC) = 0'
ubuntu 14.04
root@dev2:/tmp/apt-1.0.1ubuntu2.1# apt-cache show apt
Package: apt
Priority: important
Section: admin
Installed-Size: 3576
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
Original-Maintainer: APT Development Team de...@lists.debian.org
Architecture: amd64
Version: 1.0.1ubuntu2.1
Replaces: manpages-it ( 2.80-4~), manpages-pl ( 20060617-3~),
openjdk-6-jdk ( 6b24-1.11-0ubuntu1~), sun-java5-jdk ( 0), sun-java6-jdk (
0)
Depends: libapt-pkg4.12 (= 0.9.16), libc6 (= 2.15), libgcc1 (= 1:4.1.1),
libstdc++6 (= 4.6), ubuntu-keyring, gnupg
Suggests: aptitude | synaptic | wajig, dpkg-dev (= 1.17.2), apt-doc,
python-apt
Conflicts: python-apt ( 0.7.93.2~)
Breaks: manpages-it ( 2.80-4~), manpages-pl ( 20060617-3~), openjdk-6-jdk
( 6b24-1.11-0ubuntu1~), sun-java5-jdk ( 0), sun-java6-jdk ( 0)
Filename: pool/main/a/apt/apt_1.0.1ubuntu2.1_amd64.deb
Size: 952374
[pid 20525]
stat(/var/lib/apt/lists/mirrors.163.com_ubuntu_dists_trusty-updates_universe_i18n_Translation-en%5fUS,
0x7fffaabe5b30) = -1 ENOENT (No such file or directory)
[pid 20525] stat(/usr/lib/apt/methods/bzip2, {st_mode=S_IFREG|0755,
st_size=23056, ...}) = 0
[pid 20525] pipe([9, 11]) = 0
[pid 20525] pipe([13, 14]) = 0
[pid 20525] fcntl(9, F_SETFD, FD_CLOEXEC) = 0
[pid 20525] fcntl(11, F_SETFD, FD_CLOEXEC) = 0
[pid 20525] fcntl(13, F_SETFD, FD_CLOEXEC) = 0
[pid 20525] fcntl(14, F_SETFD, FD_CLOEXEC) = 0
[pid 20525] clone(child_stack=0,
flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD,
child_tidptr=0x7f99f1ea9a50) = 20538
Process 20538 attached
[pid 20525] fcntl(9, F_GETFL) = 0 (flags O_RDONLY)
[pid 20525] fcntl(9, F_SETFL, O_RDONLY|O_NONBLOCK) = 0
[pid 20538] rt_sigaction(SIGPIPE, {SIG_DFL, [PIPE], SA_RESTORER|SA_RESTART,
0x7f99f0e72ff0}, unfinished ...
[pid 20525] fcntl(14, F_GETFL unfinished ...
[pid 20538] ... rt_sigaction resumed {SIG_IGN, [PIPE],
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
[pid 20525] ... fcntl resumed ) = 0x1 (flags O_WRONLY)
[pid 20538] rt_sigaction(SIGQUIT, {SIG_DFL, [QUIT], SA_RESTORER|SA_RESTART,
0x7f99f0e72ff0}, unfinished ...
[pid 20525] fcntl(14, F_SETFL, O_WRONLY|O_NONBLOCK unfinished ...
[pid 20538] ... rt_sigaction resumed {SIG_DFL, [], 0}, 8) = 0
[pid 20525] ... fcntl resumed ) = 0
[pid 20538] rt_sigaction(SIGINT, {SIG_DFL, [INT], SA_RESTORER|SA_RESTART,
0x7f99f0e72ff0}, unfinished ...
[pid 20525] close(11 unfinished ...
[pid 20538] ... rt_sigaction resumed {SIG_DFL, [], 0}, 8) = 0
[pid 20525] ... close resumed ) = 0
[pid 20538] rt_sigaction(SIGWINCH, {SIG_DFL, [WINCH], SA_RESTORER|SA_RESTART,
0x7f99f0e72ff0}, unfinished ...
[pid 20525] close(13 unfinished ...
[pid 20538] ... rt_sigaction resumed {0x409140, [WINCH],
SA_RESTORER|SA_RESTART, 0x7f99f0e72ff0}, 8) = 0
[pid 20525] ... close resumed ) = 0
[pid 20538] rt_sigaction(SIGCONT, {SIG_DFL, [CONT], SA_RESTORER|SA_RESTART,
0x7f99f0e72ff0}, unfinished ...
[pid 20525] select(10, [9], NULL, NULL, NULL unfinished ...
[pid 20538] ... rt_sigaction resumed {SIG_DFL, [], 0}, 8) = 0
[pid 20538] rt_sigaction(SIGTSTP, {SIG_DFL, [TSTP], SA_RESTORER|SA_RESTART,
0x7f99f0e72ff0}, {SIG_DFL, [], 0}, 8) = 0
[pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
[pid 20538] fcntl(3, F_SETFD, FD_CLOEXEC) = 0
[pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
[pid 20538] fcntl(4, F_SETFD, FD_CLOEXEC) = 0
[pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
[pid 20538] fcntl(5, F_SETFD, FD_CLOEXEC) = 0
[pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
[pid 20538] fcntl(6, F_SETFD, FD_CLOEXEC) = 0
[pid 20538] getrlimit(RLIMIT_NOFILE, {rlim_cur=100, rlim_max=100}) = 0
[pid 20538] fcntl(7, F_SETFD, FD_CLOEXEC) = 0
[pid 20538]
[Touch-packages] [Bug 1383277] Re: Power dialog sometimes shown on resume
OK, so that branch fixes one instance of the problem. -- 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/1383277 Title: Power dialog sometimes shown on resume Status in “unity8” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu RTM: Triaged Bug description: Unfortunately no good steps to reproduce, other than resume your phone, from time to time you'll get the power dialog displayed on screen. The reason for this could be twofold: a) you pressed the power button in your pocket b) input is confused and keyUp event does not reach unity8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1383277/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26
Kindly forwarding this bug, please express your thoughts on Launchpad. I believe that was a direct request for me. My thoughts: it's unfortunate that PulseAudio doesn't support mixer elements with more than 2 volume channels. It would be nice if someone would fix that. Due to lack of time, I won't be that someone, at least in the short (or even medium) term. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26 Status in “pulseaudio” package in Ubuntu: New Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1193236] Re: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-*
same on Ubuntu 14.04.1 when runing light-locker. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to at-spi2-core in Ubuntu. https://bugs.launchpad.net/bugs/1193236 Title: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-* Status in Assistive Technology Service Provider Interface: New Status in “at-spi2-core” package in Ubuntu: Confirmed Status in “at-spi2-core” package in Debian: Confirmed Bug description: Since a few days, xsession-errors is fullfilled by that kind of errors: ** (nautilus:22621): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused ** (gedit:22640): WARNING **: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-uUkE07qdBK: Connection refused Similar errors are reported all over the net, but Debian have tried to fix it already: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=702517 But some other devs seems to blame an atk-bridge: https://groups.google.com/forum/#!topic/yad-common/nYP0RutlxNA And some others suggest a dbus/gdbus race; the good thing is that seems not disturbing that much the system. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: libgdk-pixbuf2.0-0 2.28.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.9.0-6.14-generic 3.9.6 Uname: Linux 3.9.0-6-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.10.2-0ubuntu1 Architecture: i386 Date: Fri Jun 21 08:35:40 2013 MarkForUpload: True SourcePackage: gdk-pixbuf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/at-spi/+bug/1193236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383732] Re: E-book content type
** Branch linked: lp:~michael-sheldon/webbrowser-app/ebook-mimetypes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1383732 Title: E-book content type Status in “content-hub” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu: New Bug description: I'm writing an Epub reader which I'd like to interface with the Content Hub. To do this, we need an e-book content type. There are several different formats for e-books (txt, html, epub, mobi, pdf, etc.). I don't know if all of them should be combined into a single type or if each should have their own. Also, some of those formats are used for purposes other than e-books. My reader only supports epubs at the moment. These have mimetype application/epub+zip and .epub file extension. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1383732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377332] Re: UI randomly freezes
From the trace above it looks like recvmsg blocks in thread 29, resulting in the rest of the shell to go to sleep. -- 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/1377332 Title: UI randomly freezes Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: New Bug description: Summary UI randomly freezes steps: 1. unlock greeter 2. open app 3. pull down random indicator 4. close indicator 5. open app 6. swipe to view all open apps 7. open launcher 8. close some open apps 9. repeat until ui freezes device info: [service] base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/ubuntu-rtm/14.09-proposed device: krillin build_number: 79 version_detail: ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377332] Re: UI randomly freezes
I got this today when trying to unlock the phone, got some symbols: http://pastebin.ubuntu.com/8942307/ -- 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/1377332 Title: UI randomly freezes Status in “unity8” package in Ubuntu: In Progress Status in “unity8” package in Ubuntu RTM: New Bug description: Summary UI randomly freezes steps: 1. unlock greeter 2. open app 3. pull down random indicator 4. close indicator 5. open app 6. swipe to view all open apps 7. open launcher 8. close some open apps 9. repeat until ui freezes device info: [service] base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/ubuntu-rtm/14.09-proposed device: krillin build_number: 79 version_detail: ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1377332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388582] Re: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks
static models were dropped https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda/patch_analog.c?id=632408adfe70be6706cb89522b0d5b3dce188d84 you need to report bug to kernel bugzilla by providing output of alsa-info.sh when ad1986a is working and not working -- 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/1388582 Title: Easynote MX65, AD1986A, No sound output in speakers/headphones, some with tricks Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: I have a fresh install of KUbuntu 14.10 with this problem and i come of a KUbuntu 13.10 without problems. I don't have any sound from speakers or headphone, i think the driver isn't loaded, but the microphone works, it records. The sound playback works too, but the sound doesn't go through speakers or headphones. I was testing with a lot of LiveCD KUbuntu when the problem comes. With LiveCDs KUbuntu 12.04.5 LTS, 12.10, 13.04 the sound works, they configs the sound system as HDA Intel AD198x. Since LiveCDs 13.10, 14.04.1 LTS and, of course, 14.10 Live CD and my install, i have this problem, because the sound system is now AD1986A. I will attach the alsa-info output for all this systems in my computer. But with HDA_Analyzer http://www.alsa- project.org/main/index.php/HDA_Analyzer i found the details of the problem: i can create a python script to brought back the sound working in a basic mode, like as previously. The details are activating EAPD in Card 0, Codec 0, Node 0x1b PIN (In my computer, it could be different in another) what brought back the sound to the speakers, and unmuting Output Amplifier in Card 0, Codec 0, Node 0x1a VAL[0] and VAL[1] to brought back sound to the headphones when they are plugged. I will attach too the output of this diff and the python script created by HDA_Analyzer for my system. At least, the basic working state should be back, because with a untoching fresh install there isn't any sound. There are related bugs here and other post in internet, but i collected all information i found and can give more if it's necessary. For additional information: Searching the solution, i tested too all the models availables for HDA Intel AD1986A (editing /etc/modprobe.d /alsa-base.conf with AD1986A models /usr/share/doc/alsa-base/driver /HD-Audio-Models.txt.gz) and i found the default one doesn't fit my system and anothers are better, but have problems of no sound too and i don't found how to fix these problem. When this bug is corrected, i want to help to found a better model for my computer, i don't know how now, but first it brought back the sound. Also, i test with snd-hda- tools https://launchpad.net/~diwic/+archive/ubuntu/hda and with hda- jack-sense-test the Green Line Out sense doesn't work (always NO present) but the Pink Mic sense works without problems. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4 Uname: Linux 3.16.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.7-0ubuntu8 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thywalls 2380 F pulseaudio CurrentDesktop: KDE Date: Sun Nov 2 16:24:36 2014 InstallationDate: Installed on 2014-10-30 (3 days ago) InstallationMedia: Kubuntu 14.10 Utopic Unicorn - Release i386 (20141022.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/28/2006 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T12JNC.206 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: EasyNote_MX65 dmi.board.vendor: Packard Bell BV dmi.board.version: 1.0 dmi.chassis.type: 10 dmi.chassis.vendor: Packard Bell BV dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT12JNC.206:bd09/28/2006:svnPackardBellBV:pnEasyNote_MX65:pvrPB63E03104:rvnPackardBellBV:rnEasyNote_MX65:rvr1.0:cvnPackardBellBV:ct10:cvr: dmi.product.name: EasyNote_MX65 dmi.product.version: PB63E03104 dmi.sys.vendor: Packard Bell BV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1388582/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330041] Re: Bad / incorrect display accented letters in Window title bar [ast]
I can confirm the UTF-8 text is rendered incorrectly in window title bars when LANG=ast_ES.UTF-8. The very same text (eg. working directory pathname in titlebar of Gnome-Terminal) renders correctly in other locales. It's unclear if this is a problem in the text rendering or in the local definition. ** Changed in: unity Importance: Undecided = Medium ** Changed in: unity Status: Confirmed = Triaged ** Changed in: unity/7.2 Status: Confirmed = Triaged ** Changed in: unity (Ubuntu) Importance: Undecided = Medium ** Changed in: unity (Ubuntu) Status: Confirmed = Triaged ** Changed in: unity/7.2 Importance: Undecided = Medium -- 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/1330041 Title: Bad / incorrect display accented letters in Window title bar [ast] Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: In Unity desktop, the accented letters (á , é, í, ó, ú..) aren't displayed correctly in the Window title bar when using Asturian language The bug is only reproduced in Unity. If you change to Gnome desktop (sudo apt-get install gnome-panel), window title bars are displayed correctly. In the same way, I have tested the problem and is not present in another languages like [es, ca..] To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1330041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1378126] Re: Passcode screen misses keypresses
** 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/1378126 Title: Passcode screen misses keypresses Status in Ubuntu Keyboard: Incomplete Status in “unity8” package in Ubuntu: In Progress Bug description: For some reason the passcode entry screen / lock screen feels very laggy when entering my passcode. It frequently misses my keypresses, so i end up typing insufficient characters. I don't know if the hit area for the numbers is too small and I'm mis-hitting or if there is a lag/delay. I'm not typing stupendously fast, but pretty quick. Any slower and it feels very deliberate, like I'm typing a PIN into an ATM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-keyboard/+bug/1378126/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388235] Re: Battery icon turns red at 30%
@rsalveti - According to the current indicators specs, the charge level should be visually supported through the different states of the battery indicator icon (i.e. 20%, 40%, 60%, 80%,100% battery charged) in the status bar (https://drive.google.com/a/canonical.com/#folders/0BzbnWoHmYF3ablBITVByRnpzdEk) In this case, when the phone drops below 20% power, the battery indicator should turn red giving a nudge to recharge. -- 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/1388235 Title: Battery icon turns red at 30% Status in Ubuntu UX bugs: Confirmed Status in “indicator-power” package in Ubuntu: Confirmed Bug description: This seems a bit pessimistic since the phone still has a great deal of capacity and time left, perhaps 15 or 20% is a better threshold To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1388235/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1383732] Re: E-book content type
** Changed in: webbrowser-app (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to content-hub in Ubuntu. https://bugs.launchpad.net/bugs/1383732 Title: E-book content type Status in “content-hub” package in Ubuntu: Fix Released Status in “webbrowser-app” package in Ubuntu: In Progress Bug description: I'm writing an Epub reader which I'd like to interface with the Content Hub. To do this, we need an e-book content type. There are several different formats for e-books (txt, html, epub, mobi, pdf, etc.). I don't know if all of them should be combined into a single type or if each should have their own. Also, some of those formats are used for purposes other than e-books. My reader only supports epubs at the moment. These have mimetype application/epub+zip and .epub file extension. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/content-hub/+bug/1383732/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391286] Re: Fails to generate thumbnail for small videos recorded with camera-app
** Changed in: thumbnailer Importance: Undecided = High ** Also affects: thumbnailer (Ubuntu) Importance: Undecided Status: New ** Changed in: thumbnailer (Ubuntu) Importance: Undecided = High ** Tags added: rtm14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1391286 Title: Fails to generate thumbnail for small videos recorded with camera-app Status in Thumbnail generator for all kinds of files: New Status in “thumbnailer” package in Ubuntu: New Bug description: Videos with less than one sec recorded by camera-app (like when you click on the record button and immediately stops the recording process) have problems while generating thumbnail. This seems to be a problem to gallery-app since if we have one file like this on the collection the thumbnails took a long time to generate. I added an unit test that seems to fail on this branch: lp:~artmello/thumbnailer/thumbnailer-no_thumbnail_video Attached a video sample that seems to fail To manage notifications about this bug go to: https://bugs.launchpad.net/thumbnailer/+bug/1391286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391556] [NEW] gles symbols incorrect
Public bug reported: The gles symbols got an incorrect treatment during 5.3.2 transition: https://launchpadlibrarian.net/188155119/qtbase-opensource-src_5.3.0%2Bdfsg-2ubuntu9_5.3.2%2Bdfsg-4ubuntu1.diff.gz (search for libqt5gui5.symbols). This causes: python-pyqt5.qtopengl/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python-pyqt5.qtopengl-dbg/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python3-pyqt5.qtopengl/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python3-pyqt5.qtopengl-dbg/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#pyqt5) ** Affects: qtbase-opensource-src (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1391556 Title: gles symbols incorrect Status in “qtbase-opensource-src” package in Ubuntu: New Bug description: The gles symbols got an incorrect treatment during 5.3.2 transition: https://launchpadlibrarian.net/188155119/qtbase-opensource-src_5.3.0%2Bdfsg-2ubuntu9_5.3.2%2Bdfsg-4ubuntu1.diff.gz (search for libqt5gui5.symbols). This causes: python-pyqt5.qtopengl/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python-pyqt5.qtopengl-dbg/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python3-pyqt5.qtopengl/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python3-pyqt5.qtopengl-dbg/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#pyqt5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1391556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391286] Re: Fails to generate thumbnail for small videos recorded with camera-app
The troubling part is that when a thumbnail like this is encountered, it seems to invalidate all of the other thumbnails that have already been loaded. For example, open the Photos tab of the gallery app and wait for the thumbnails to load, scroll up and down. Everything gets loaded. Then copy in the attached file into the ~/Videos directory. This failing thumbnail seems to make the other thumbnail reloaded quite often and things get slower. ** Changed in: thumbnailer (Ubuntu) Assignee: (unassigned) = Jussi Pakkanen (jpakkane) ** Changed in: thumbnailer Assignee: (unassigned) = Jussi Pakkanen (jpakkane) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1391286 Title: Fails to generate thumbnail for small videos recorded with camera-app Status in Thumbnail generator for all kinds of files: New Status in “thumbnailer” package in Ubuntu: New Bug description: Videos with less than one sec recorded by camera-app (like when you click on the record button and immediately stops the recording process) have problems while generating thumbnail. This seems to be a problem to gallery-app since if we have one file like this on the collection the thumbnails took a long time to generate. I added an unit test that seems to fail on this branch: lp:~artmello/thumbnailer/thumbnailer-no_thumbnail_video Attached a video sample that seems to fail To manage notifications about this bug go to: https://bugs.launchpad.net/thumbnailer/+bug/1391286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391558] [NEW] package udev 204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev] failed to install/upgrade: subprocess new pre-installation script returned error exit
Public bug reported: a ProblemType: Package DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev] ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: udev: Install udev: Configure systemd-services: Configure libpam-systemd: Configure Architecture: i386 Date: Tue Nov 11 16:49:02 2014 DpkgTerminalLog: Preparing to unpack .../udev_204-5ubuntu20.8_i386.deb ... DuplicateSignature: package:udev:204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev]:subprocess new pre-installation script returned error exit status 139 ErrorMessage: subprocess new pre-installation script returned error exit status 139 InstallationDate: Installed on 2012-05-02 (922 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=477c8345-1b95-4f17-89d0-878af1bd6232 ro quiet splash SourcePackage: systemd Title: package udev 204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev] failed to install/upgrade: subprocess new pre-installation script returned error exit status 139 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UdevLog: UpgradeStatus: Upgraded to trusty on 2014-04-25 (199 days ago) dmi.bios.date: 03/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 trusty -- 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/1391558 Title: package udev 204-5ubuntu20.7 [modified: usr/share/initramfs- tools/hooks/udev] failed to install/upgrade: subprocess new pre- installation script returned error exit status 139 Status in “systemd” package in Ubuntu: New Bug description: a ProblemType: Package DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev] ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: udev: Install udev: Configure systemd-services: Configure libpam-systemd: Configure Architecture: i386 Date: Tue Nov 11 16:49:02 2014 DpkgTerminalLog: Preparing to unpack .../udev_204-5ubuntu20.8_i386.deb ... DuplicateSignature: package:udev:204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev]:subprocess new pre-installation script returned error exit status 139 ErrorMessage: subprocess new pre-installation script returned error exit status 139 InstallationDate: Installed on 2012-05-02 (922 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=477c8345-1b95-4f17-89d0-878af1bd6232 ro quiet splash SourcePackage: systemd Title: package udev 204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev] failed to install/upgrade: subprocess new pre-installation script returned error exit status 139 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UdevLog: UpgradeStatus: Upgraded to trusty on 2014-04-25 (199 days ago) dmi.bios.date: 03/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to:
[Touch-packages] [Bug 1391558] Re: package udev 204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev] failed to install/upgrade: subprocess new pre-installation script returned error exit s
** Tags removed: need-duplicate-check -- 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/1391558 Title: package udev 204-5ubuntu20.7 [modified: usr/share/initramfs- tools/hooks/udev] failed to install/upgrade: subprocess new pre- installation script returned error exit status 139 Status in “systemd” package in Ubuntu: New Bug description: a ProblemType: Package DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev] ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 AptOrdering: udev: Install udev: Configure systemd-services: Configure libpam-systemd: Configure Architecture: i386 Date: Tue Nov 11 16:49:02 2014 DpkgTerminalLog: Preparing to unpack .../udev_204-5ubuntu20.8_i386.deb ... DuplicateSignature: package:udev:204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev]:subprocess new pre-installation script returned error exit status 139 ErrorMessage: subprocess new pre-installation script returned error exit status 139 InstallationDate: Installed on 2012-05-02 (922 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=477c8345-1b95-4f17-89d0-878af1bd6232 ro quiet splash SourcePackage: systemd Title: package udev 204-5ubuntu20.7 [modified: usr/share/initramfs-tools/hooks/udev] failed to install/upgrade: subprocess new pre-installation script returned error exit status 139 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UdevLog: UpgradeStatus: Upgraded to trusty on 2014-04-25 (199 days ago) dmi.bios.date: 03/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1391558/+subscriptions -- Mailing list: https://launchpad.net/~touch-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
This bug was fixed in the package unity8 - 8.01.1+15.04.2014~rtm- 0ubuntu1 --- unity8 (8.01.1+15.04.2014~rtm-0ubuntu1) 14.09; urgency=medium [ Michael Terry ] * Skip second SIM unlock dialog if user presses Emergency Call on first one (LP: #1387925) [ Mirco Müller ] * Replace ComboButton in snap-decision notifications, used for additional actions ( 3 actions), with custom widget immune to accidental taps. (LP: #1384730) -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 11 Nov 2014 09:12:40 + ** Branch linked: lp:~ps-jenkins/unity8/ubuntu-rtm-14.09-proposed ** 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/1384730 Title: [notifications] remove combo button from incoming call snap Status in Ubuntu UX bugs: Fix Committed 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 1391556] Re: gles symbols incorrect
** Branch linked: lp:~kubuntu-packagers/kubuntu-packaging/qtbase- opensource-src -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1391556 Title: gles symbols incorrect Status in “qtbase-opensource-src” package in Ubuntu: New Bug description: The gles symbols got an incorrect treatment during 5.3.2 transition: https://launchpadlibrarian.net/188155119/qtbase-opensource-src_5.3.0%2Bdfsg-2ubuntu9_5.3.2%2Bdfsg-4ubuntu1.diff.gz (search for libqt5gui5.symbols). This causes: python-pyqt5.qtopengl/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python-pyqt5.qtopengl-dbg/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python3-pyqt5.qtopengl/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python3-pyqt5.qtopengl-dbg/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#pyqt5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1391556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307535] Re: Installing apps manually does not refresh the scope
** Changed in: unity-scope-click (Ubuntu) Importance: Low = Medium -- 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/1307535 Title: Installing apps manually does not refresh the scope Status in “unity-scope-click” package in Ubuntu: Triaged Bug description: When installing apps from the command line, the scope is not refreshed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1307535/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1388139] Re: package udev 204-5ubuntu20.7 failed to install/upgrade: postinst segfault
Hi Martin Do you think there will be a fix for this, or should I just backup and reinstall the system? Currently I can't get security updates, or install new packages. -- 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/1388139 Title: package udev 204-5ubuntu20.7 failed to install/upgrade: postinst segfault Status in “systemd” package in Ubuntu: Incomplete Bug description: Happened during normal system update. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: udev 204-5ubuntu20.7 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.6 Architecture: i386 Date: Fri Oct 31 16:21:06 2014 DpkgTerminalLog: Preparing to unpack .../udev_204-5ubuntu20.8_i386.deb ... Segmentation fault (core dumped) dpkg: error processing archive /var/cache/apt/archives/udev_204-5ubuntu20.8_i386.deb (--unpack): subprocess new pre-installation script returned error exit status 139 DuplicateSignature: package:udev:204-5ubuntu20.7:subprocess new pre-installation script returned error exit status 139 ErrorMessage: subprocess new pre-installation script returned error exit status 139 InstallationDate: Installed on 2012-05-02 (911 days ago) InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Beta i386 (20120328) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic root=UUID=477c8345-1b95-4f17-89d0-878af1bd6232 ro quiet splash SourcePackage: systemd Title: package udev 204-5ubuntu20.7 failed to install/upgrade: subprocess new pre-installation script returned error exit status 139 UdevDb: Error: [Errno 2] No such file or directory: 'udevadm' UpgradeStatus: Upgraded to trusty on 2014-04-25 (188 days ago) dmi.bios.date: 03/18/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0803 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M4A785-M dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0803:bd03/18/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A785-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1388139/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391556] Re: gles symbols incorrect
https://launchpad.net/~ci-train-ppa- service/+archive/ubuntu/landing-014/+packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1391556 Title: gles symbols incorrect Status in “qtbase-opensource-src” package in Ubuntu: New Bug description: The gles symbols got an incorrect treatment during 5.3.2 transition: https://launchpadlibrarian.net/188155119/qtbase-opensource-src_5.3.0%2Bdfsg-2ubuntu9_5.3.2%2Bdfsg-4ubuntu1.diff.gz (search for libqt5gui5.symbols). This causes: python-pyqt5.qtopengl/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python-pyqt5.qtopengl-dbg/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python3-pyqt5.qtopengl/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python3-pyqt5.qtopengl-dbg/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#pyqt5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1391556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377332] Re: UI randomly freezes
More symbols in thread 1 http://pastebin.ubuntu.com/8942528/ revealed that connection to cgmanager failed. There were also errors in cgmanager.log http://pastebin.ubuntu.com/8942980/ -- 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/1377332 Title: UI randomly freezes Status in “ubuntu-app-launch” package in Ubuntu: New Status in “unity8” package in Ubuntu: In Progress Status in “ubuntu-app-launch” package in Ubuntu RTM: New Status in “unity8” package in Ubuntu RTM: New Bug description: Summary UI randomly freezes steps: 1. unlock greeter 2. open app 3. pull down random indicator 4. close indicator 5. open app 6. swipe to view all open apps 7. open launcher 8. close some open apps 9. repeat until ui freezes device info: [service] base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/ubuntu-rtm/14.09-proposed device: krillin build_number: 79 version_detail: ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1377332/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] [NEW] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image
Public bug reported: 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. ** Affects: ubuntu-ux Importance: Undecided Status: New ** Affects: unity8 (Ubuntu) Importance: Undecided Status: Incomplete ** Also affects: ubuntu-ux Importance: Undecided Status: New ** Changed in: unity8 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1391560 Title: 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 1385630] Re: systemd 215 hangs during boot
Here is the attachment /boot/initrd.img-* ** Attachment added: initrd.img-3.16.0-24-generic https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+attachment/4258396/+files/initrd.img-3.16.0-24-generic -- 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/1385630 Title: systemd 215 hangs during boot Status in “systemd” package in Ubuntu: Incomplete Bug description: I just installed (for testing) the newest systemd from Vivid proposed repositories. Yes, that is only a proposed package. The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8). After the installation I found that every now and then booting or rebooting fails. It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing. After each failure the next booting is successful, however. My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu. The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD. This may also be some sort of race situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1385630] Re: systemd 215 hangs during boot
Martin, The command cpio -tv /boot/initrd.img-3.16.0-24-generic did nothing. Terminal just started a neverending process (but not getting stuck). I did wait for several minutes. The size of /boot/intitrd.img-3.16.0-24-generic is 19.2 Mb. -- 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/1385630 Title: systemd 215 hangs during boot Status in “systemd” package in Ubuntu: Incomplete Bug description: I just installed (for testing) the newest systemd from Vivid proposed repositories. Yes, that is only a proposed package. The version is 215-5ubuntu1. Also the new plymouth was needed to do this (version 0.9.0-0ubuntu8). After the installation I found that every now and then booting or rebooting fails. It fails in a system-fsck line. So, nowhere to go from that, no tty's, no nothing. After each failure the next booting is successful, however. My setup is extremely fast, I am able to get to the desktop in about 5 seconds from grub menu. The setup contains Intel Core i7 4790 processor and Samsung 850 Pro SSD. This may also be some sort of race situation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1385630/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1377332] Re: UI randomly freezes
Per discussion on IRC we're going to make the connections timeout if they can't be made. This makes the situation more robust, in that the user can keep working. But they might loose a resume or pausing of an app because we can't get PIDs for it. We can then look at this bug more carefully in a less critical manner. ** Also affects: ubuntu-app-launch (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-app-launch (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: ubuntu-app-launch (Ubuntu) Assignee: (unassigned) = Ted Gould (ted) ** Changed in: ubuntu-app-launch (Ubuntu RTM) Assignee: (unassigned) = Ted Gould (ted) -- 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/1377332 Title: UI randomly freezes Status in “ubuntu-app-launch” package in Ubuntu: New Status in “unity8” package in Ubuntu: In Progress Status in “ubuntu-app-launch” package in Ubuntu RTM: New Status in “unity8” package in Ubuntu RTM: New Bug description: Summary UI randomly freezes steps: 1. unlock greeter 2. open app 3. pull down random indicator 4. close indicator 5. open app 6. swipe to view all open apps 7. open launcher 8. close some open apps 9. repeat until ui freezes device info: [service] base: system-image.ubuntu.com http_port: 80 https_port: 443 channel: ubuntu-touch/ubuntu-rtm/14.09-proposed device: krillin build_number: 79 version_detail: ubuntu=20141002,device=20141002-d5938d7,custom=1412208099,version=79 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1377332/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1330041] Re: Bad / incorrect display accented letters in Window title bar [ast]
to comment #11 Hi Stephen, Do you think that the other issue, (disscussed here and in https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1391521 ) are related? -- 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/1330041 Title: Bad / incorrect display accented letters in Window title bar [ast] Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in “unity” package in Ubuntu: Triaged Bug description: In Unity desktop, the accented letters (á , é, í, ó, ú..) aren't displayed correctly in the Window title bar when using Asturian language The bug is only reproduced in Unity. If you change to Gnome desktop (sudo apt-get install gnome-panel), window title bars are displayed correctly. In the same way, I have tested the problem and is not present in another languages like [es, ca..] To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1330041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391563] [NEW] [VIA8233 - VIA 8235, playback] No sound at all
Public bug reported: No sound at all from my integrated sound system on a ASUS A7V8X-X motherboard, under Xubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fn 1705 F pulseaudio fn 2080 F pulseaudio CurrentDesktop: XFCE Date: Tue Nov 11 17:01:59 2014 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:V8235 failed Symptom_Card: MPU-401 UART - MPU-401 UART Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fn 1705 F pulseaudio fn 2080 F pulseaudio fn 8825 F alsamixer Symptom_Type: No sound at all Title: [VIA8233 - VIA 8235, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS A7V8X-X ACPI BIOS Revision 1006 dmi.board.name: A7V8X-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSA7V8X-XACPIBIOSRevision1006:bd08/06/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA7V8X-X:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 trusty -- 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/1391563 Title: [VIA8233 - VIA 8235, playback] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: No sound at all from my integrated sound system on a ASUS A7V8X-X motherboard, under Xubuntu 14.04 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8 Uname: Linux 3.13.0-39-generic i686 ApportVersion: 2.14.1-0ubuntu3.5 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fn 1705 F pulseaudio fn 2080 F pulseaudio CurrentDesktop: XFCE Date: Tue Nov 11 17:01:59 2014 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:V8235 failed Symptom_Card: MPU-401 UART - MPU-401 UART Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fn 1705 F pulseaudio fn 2080 F pulseaudio fn 8825 F alsamixer Symptom_Type: No sound at all Title: [VIA8233 - VIA 8235, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/06/2003 dmi.bios.vendor: Award Software, Inc. dmi.bios.version: ASUS A7V8X-X ACPI BIOS Revision 1006 dmi.board.name: A7V8X-X dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: REV 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 7 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAwardSoftware,Inc.:bvrASUSA7V8X-XACPIBIOSRevision1006:bd08/06/2003:svnSystemManufacturer:pnSystemName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnA7V8X-X:rvrREV1.xx:cvnChassisManufacture:ct7:cvrChassisVersion: dmi.product.name: System Name dmi.product.version: System Version dmi.sys.vendor: System Manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1391563/+subscriptions -- Mailing list: https://launchpad.net/~touch-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] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image
** Summary changed: - Develop a strategy to keep fonts readable wherever we allow the user setting his own background image + [themes] Develop a strategy to keep fonts readable wherever we allow the user setting his own background image ** Tags added: ota-2 -- 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] 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 1391556] Re: gles symbols incorrect
** Changed in: qtbase-opensource-src (Ubuntu) Assignee: (unassigned) = Timo Jyrinki (timo-jyrinki) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1391556 Title: gles symbols incorrect Status in “qtbase-opensource-src” package in Ubuntu: New Bug description: The gles symbols got an incorrect treatment during 5.3.2 transition: https://launchpadlibrarian.net/188155119/qtbase-opensource-src_5.3.0%2Bdfsg-2ubuntu9_5.3.2%2Bdfsg-4ubuntu1.diff.gz (search for libqt5gui5.symbols). This causes: python-pyqt5.qtopengl/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python-pyqt5.qtopengl-dbg/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python3-pyqt5.qtopengl/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) python3-pyqt5.qtopengl-dbg/armhf unsatisfiable Depends: libqt5gui5-gles (= 5.2.0) (http://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#pyqt5) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1391556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1391286] Re: Fails to generate thumbnail for small videos recorded with camera-app
It seems that when gallery requests the thumbnail for this file, even if it was generated before, all the process of getting new thumbnails for gallery collection, or getting pointers for the previous generated ones, get a lot of time to complete. That seems to be the reason why all the thumbnails enter in a reloading state. Its worse if the problematic file is the first one on the collection, since if it is not a couple of requests seems to be answered before the one that crashes. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to thumbnailer in Ubuntu. https://bugs.launchpad.net/bugs/1391286 Title: Fails to generate thumbnail for small videos recorded with camera-app Status in Thumbnail generator for all kinds of files: New Status in “thumbnailer” package in Ubuntu: New Bug description: Videos with less than one sec recorded by camera-app (like when you click on the record button and immediately stops the recording process) have problems while generating thumbnail. This seems to be a problem to gallery-app since if we have one file like this on the collection the thumbnails took a long time to generate. I added an unit test that seems to fail on this branch: lp:~artmello/thumbnailer/thumbnailer-no_thumbnail_video Attached a video sample that seems to fail To manage notifications about this bug go to: https://bugs.launchpad.net/thumbnailer/+bug/1391286/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1390592] Re: 'ptrace peer=@{profile_name}' does not work on 14.04 (at least) with docker
I may need to take another approach instead of replacing add-decimal-
interp.patch with upstream commit r2456. While this bug is fixed, the
regression test suite hits some new failures. The commit message of
upstream commit r2541 explains the problem (and changes the tests):
Earlier fixes to the parser's handling of escape sequences involving '\'
caused a behavioral change that profiles no longer needed to contain
'\\' before an octal escape sequence.
I don't feel like that kind of change is acceptable in an SRU. I'll dig
into the r2456 patch some more and see if I can pull out only the binary
encoding bug fix.
** Changed in: apparmor (Ubuntu Trusty)
Status: Triaged = In Progress
** Changed in: apparmor (Ubuntu Trusty)
Assignee: (unassigned) = Tyler Hicks (tyhicks)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1390592
Title:
'ptrace peer=@{profile_name}' does not work on 14.04 (at least) with
docker
Status in “apparmor” package in Ubuntu:
Fix Released
Status in “apparmor” source package in Trusty:
In Progress
Bug description:
I was helping a docker user out in #apparmor on OFTC and I think we
found a kernel bug in the 14.04 kernel (14.10 kernel seems fine, see
below).
Workaround: install the https://launchpad.net/ubuntu/+source/linux-
lts-utopic kernel.
$ cat /proc/version_signature
Ubuntu 3.13.0-37.64-generic 3.13.11.7
Steps to reproduce:
1. adjust /etc/apparmor.d/abstractions/base to have:
ptrace peer=@{profile_name},
2. sudo apt-get install docker.io
3. sudo docker pull ubuntu:trusty
4. Run 'ps' inside docker:
$ sudo docker run -i -t ubuntu:trusty bash
root@5039d725a41d:/# ps
...
root@5039d725a41d:/# exit
$
Then observe the following denials on the host, which should have been
addressed in the rule added in step 1:
Nov 7 13:43:42 sec-trusty-amd64 kernel: [24258.018580] type=1400
audit(1415389422.303:68): apparmor=DENIED operation=ptrace
profile=docker-default pid=27542 comm=ps requested_mask=trace
denied_mask=trace peer=docker-default
Nov 7 13:43:42 sec-trusty-amd64 kernel: [24258.020832] type=1400
audit(1415389422.307:69): apparmor=DENIED operation=ptrace
profile=docker-default pid=27542 comm=ps requested_mask=read
denied_mask=read peer=docker-default
Nov 7 13:43:42 sec-trusty-amd64 kernel: [24258.020893] type=1400
audit(1415389422.307:70): apparmor=DENIED operation=ptrace
profile=docker-default pid=27542 comm=ps requested_mask=read
denied_mask=read peer=docker-default
Using 'ptrace peer=docker-default,' also did not work. Ubuntu 14.10
works as expected (note, the policy is different on 14.10 and it
already has the rule from step 1). Ubuntu 14.04 with the linux-lts-
utopic backport kernel also works (from trusty-proposed: sudo apt-get
install linux-headers-3.16.0-25-generic linux-image-3.16.0-25-generic
linux-image-extra-3.16.0-25-generic).
Note, docker is different than most applications in that it embeds its
policy inside the docker binary and this binary when launched as a
daemon (ie, via the upstart job) will unconditionally write out the
policy to /etc/apparmor.d/docker-default. As such, to modify the
policy:
0. install docker.io and pull a trusty image # only has to be done once
1. update /etc/apparmor.d/abstractions/base to have the new ptrace rules
2. sudo stop docker.io # 'docker' on 14.10
3. sudo apparmor_parser -R /etc/apparmor.d/docker
4. sudo rm -f /etc/apparmor.d/docker /etc/apparmor.d/cache/docker
5. sudo start docker.io # 'docker' on 14.10
6. Run 'ps' inside docker:
$ sudo docker run -i -t ubuntu:trusty bash
root@5039d725a41d:/# ps
...
root@5039d725a41d:/# exit
$
(Docker just added a way to specify an alternate existing profile in
https://docs.docker.com/reference/run/#security-configuration).
Reference: https://github.com/docker/docker/issues/7276
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1390592/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
