[Touch-packages] [Bug 1354110] Re: please merge openssl from debian
The new release as you said is almost all incorporating the patches, this is why should be harmless to merge. A good reason for a merge is that we reduce a lot the debian delta, moreover there are two or three fixes in the debian packaging that might be useful to cherry-pick (restart services for example). But I think we can merge after utopic, it is up to you ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1354110 Title: please merge openssl from debian Status in “openssl” package in Ubuntu: Incomplete Bug description: debdiff attached To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1354110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347721] Re: Saucy - Trusty upgrade failed: procps fails to configure
Installed and updated Saucy, enabled proposed, and ran apt-get install apt: Start-Date: 2014-08-11 23:15:49 Commandline: apt-get install apt Upgrade: apt:i386 (0.9.9.1~ubuntu3.2, 0.9.9.1~ubuntu3.3), libapt-pkg4.12:i386 (0.9.9.1~ubuntu3.2, 0.9.9.1~ubuntu3.3) End-Date: 2014-08-11 23:16:02 Then disabled proposed, refreshed the cache using update-manager and was offered the upgrade via GUI so I proceeded and all went perfectly so I'm marking this verification-done. Many thanks. ** Tags removed: verification-needed ** Tags added: verification-done -- 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/1347721 Title: Saucy - Trusty upgrade failed: procps fails to configure Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Saucy: Fix Committed Status in “apt” source package in Trusty: Triaged Status in “apt” source package in Utopic: Fix Released Bug description: Test Case: 1. Install Saucy + the task ubuntu-dekstop^ 2. Upgrade with do-release-upgrade Result: Upgrade fails with: Setting up libprocps3:i386 (1:3.3.9-1ubuntu2) ... dpkg: dependency problems prevent configuration of procps: procps depends on initscripts; however: Package initscripts is not configured yet. dpkg: error processing package procps (--configure): dependency problems - leaving unconfigured == Original Description == I'm just performing 14.04.1 pre-release testing and decided to try a Saucy - Trusty upgrade even though Saucy recently reached EOL. I'd expected to be told no upgrade was available (or was impossible) early in the process if it were not possible at this point in time but the upgrade appeared to be in progress until the attached warning appeared (I'd guess about half-way into the upgrade process based on lapsed time) . No idea what will happen on reboot so I wanted to file this prior to reboot. I'll follow up later. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CrashDB: ubuntu CurrentDesktop: GNOME Date: Wed Jul 23 09:03:39 2014 InstallationDate: Installed on 2014-07-17 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131015) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2014-07-23 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1347721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354067] Re: Auto-Login service for GMail accounts gives Applications can no longer access online account error
Does the problem go away if you disable the Calendar service from the Google account, in the Online Accounts panel in System Settings? If so, this might be a duplicate of bug 1029289. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1354067 Title: Auto-Login service for GMail accounts gives Applications can no longer access online account error Status in “account-plugins” package in Ubuntu: Confirmed Status in “friends” package in Ubuntu: Invalid Bug description: The auto-login service for GMail accounts gives Applications can no longer access online accounts error everytime it attempts to connect. It also cannot sustain connections for other online services (facebook, yahoo, etc.) and requires me to grant access to the services again and again. I can confirm my passwords are correct. Also, granting access to yahoo mail and facebook works flawlessly, but the GMail 'Grant Access' interface is buggy, and just doesn't work. On entering password and clicking 'Done' it brings back the same screen, as though nothing happened. Over and over again. If you click cancel a few times, it brings you back to the screen with the list of online accounts, while it attempts to connect to the services, in vain. Also, overall the friends service is buggy. It doesn't show me notifications from facebook, nor has it synced events from my google calenders. I cannot tell you when this problem started exactly, neither can i guess what might have caused the problem. If you need some log files, please tell me, i'll upload them asap. I don't have accounts in many of the services listed there, so i might not be able to help you with other services. I really hope there's a solution to this, because its always lovely to see a well polished desktop environment :) I use Ubuntu 14.04 LTS (Trusty Tahr) Version of 'friends' package installed: 0.2.0+14.04.20140217.1-0ubuntu1 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: friends-dispatcher 0.2.0+14.04.20140217.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Aug 7 20:47:49 2014 InstallationDate: Installed on 2014-04-20 (108 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) PackageArchitecture: all SourcePackage: friends UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/account-plugins/+bug/1354067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354189] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:11:QCoreApplication::notifyInternal:MInputContext::updatePreeditInternally:MInputContext::updatePreedit:MInputContext::
I searched for qplatforminputcontext and dbus related commits in 5.3.x, but none seemed to touch the places in code where the trace points to. But in doing that, I figured out that while QDBus is in qtbase, MInputContext is not in platforminputcontext (in qtbase) where I thought it'd be, but instead it's in maliit-framework. Michael, could you take a look at this crasher in MInputContext::updatePreedit? ** Package changed: qtbase-opensource-src (Ubuntu) = maliit-framework (Ubuntu) -- 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/1354189 Title: /usr/lib/arm-linux- gnueabihf/qt5/bin/qmlscene:11:QCoreApplication::notifyInternal:MInputContext::updatePreeditInternally:MInputContext::updatePreedit:MInputContext::qt_static_metacall:QMetaObject::activate Status in “maliit-framework” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding qtdeclarative-opensource-src. This problem was most recently seen with version 5.3.0-3ubuntu8, the problem page at https://errors.ubuntu.com/problem/50ffdb4caf743ab085b5cdaa290c32dad7c24c7e contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1354189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319075] Re: Dark screen when stopping mouse on launcher icons or launching app
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/1319075 Title: Dark screen when stopping mouse on launcher icons or launching app Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Ubuntu release: 14.04 desktop unity version: 7.2.0+14.04.20140423-0ubuntu1.2 compiz version: 1:0.9.11+14.04.20140423-0ubuntu1 What expected to happen: showing running apps and/or desktop while launcher or dash is showing at the same time. What happened instead: When the mouse stop on any icons on launcher, the whole screen except unity goes dark. The same thing also happens when launching apps from launcher, dash or hotkeys, eg alt+ctrl+T - terminal. A captured screen is attached for reference. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 13 22:39:38 2014 DistUpgraded: 2014-05-13 21:16:28,072 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.10, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3047] Subsystem: Lenovo Device [17aa:3047] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c3ef9e78-03fa-466c-bc92-e6e774840d89 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-13 (0 days ago) dmi.bios.date: 12/10/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT37AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT37AUS:bd12/10/2008:svnLENOVO:pn7188RY4:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 7188RY4 dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 13 22:31:08 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImPS/2 Logitech Wheel Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 505 vendor SAM xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1319075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348236] Re: Fails to scan mp3 and consumes all the system memory when scanning
That mp3 file is causing problems with GStreamer itself. To replicate, simply do apt-get install gstreamer1.0-plugins-base-apps gst-discoverer-1.0 Existance.mp3 On the desktop it works just fine. On the phone this happens: Analyzing file:///home/phablet/mdtest/Existance.mp3 Done discovering file:///home/phablet/mdtest/Existance.mp3 An error was encountered while discovering the file No valid frames decoded before end of stream -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1348236 Title: Fails to scan mp3 and consumes all the system memory when scanning Status in “mediascanner2” package in Ubuntu: Confirmed Bug description: Image 148 on mako/flo, try importing file http://people.canonical.com/~rsalveti/Existance.mp3, and you'll see mediascanner consuming most of the resources available, until killed. Probably an issue with gstreamer itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1348236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1319075] Re: Dark screen when stopping mouse on launcher icons or launching app
I suspect I'm affected by this issue too. It started after the upgrade to Ubuntu 14.04. However, directly after the upgrade the behaviour was a bit different compared to the bug description. Booting into the desktop the screen was black except for the line of launcher icons to the left. Moving the mouse over the any of the launcher icons would reveal the desktop, but as soon as I moved the mouse back onto the desktop it went black again. After some trial and error I managed to switch to Low graphics mode (using unsettings). This reversed the behaviour so that it now behaves as described in this bug report. The desktop and launcher is works fine but as soon as I move the mouse cursor over any of the launcher icons and let it linger until the tooltip text with the name of the application is shown the desktop goes black. The desktop going black seems to be directly linked to the tooltip text showing. Quickly moving the cursor over the launcher icons will trigger the bug. However lingering log enough for the tooltip to be shown, or right-click on an icon to show its menu, will immediately cause the desktop to go black. My computer is also equipped with a Intel Corporation 4 Series Chipset Integrated Graphics Controller. -- 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/1319075 Title: Dark screen when stopping mouse on launcher icons or launching app Status in Unity: New Status in “unity” package in Ubuntu: Confirmed Bug description: Ubuntu release: 14.04 desktop unity version: 7.2.0+14.04.20140423-0ubuntu1.2 compiz version: 1:0.9.11+14.04.20140423-0ubuntu1 What expected to happen: showing running apps and/or desktop while launcher or dash is showing at the same time. What happened instead: When the mouse stop on any icons on launcher, the whole screen except unity goes dark. The same thing also happens when launching apps from launcher, dash or hotkeys, eg alt+ctrl+T - terminal. A captured screen is attached for reference. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.2.0+14.04.20140423-0ubuntu1.2 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Tue May 13 22:39:38 2014 DistUpgraded: 2014-05-13 21:16:28,072 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: vboxhost, 4.3.10, 3.11.0-20-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Lenovo Device [17aa:3047] Subsystem: Lenovo Device [17aa:3047] ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c3ef9e78-03fa-466c-bc92-e6e774840d89 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to trusty on 2014-05-13 (0 days ago) dmi.bios.date: 12/10/2008 dmi.bios.vendor: LENOVO dmi.bios.version: 5CKT37AUS dmi.board.name: LENOVO dmi.chassis.vendor: LENOVO dmi.chassis.version: NONE dmi.modalias: dmi:bvnLENOVO:bvr5CKT37AUS:bd12/10/2008:svnLENOVO:pn7188RY4:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE: dmi.product.name: 7188RY4 dmi.product.version: ThinkCentre M58p dmi.sys.vendor: LENOVO version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 13 22:31:08 2014 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputVideo BusKEYBOARD, id 7 inputPower Button KEYBOARD, id 8 inputAT Translated Set 2 keyboard KEYBOARD, id 9 inputImPS/2 Logitech Wheel Mouse MOUSE, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id 505 vendor
[Touch-packages] [Bug 1355111] [NEW] newgrp fails with crypt: Invalid argument
You have been subscribed to a public bug: entry from /etc/passwd: user:x:1000:1000:User,,,:/home/user:/bin/bash entry from /etc/group: dummy:x:200:user entry from /etc/gshadow: dummy:*:: logged on as user the command newgrp dummy asks for a password and fails with crypt: Invalid argument after removing the line for dummy from gshadow newgrp works A similar bug was reported on the redhat tracker: https://bugzilla.redhat.com/show_bug.cgi?id=988184 cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS ** Affects: shadow (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- newgrp fails with crypt: Invalid argument https://bugs.launchpad.net/bugs/1355111 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow 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 1355111] Re: newgrp fails with crypt: Invalid argument
** Package changed: ubuntu = shadow (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1355111 Title: newgrp fails with crypt: Invalid argument Status in “shadow” package in Ubuntu: New Bug description: entry from /etc/passwd: user:x:1000:1000:User,,,:/home/user:/bin/bash entry from /etc/group: dummy:x:200:user entry from /etc/gshadow: dummy:*:: logged on as user the command newgrp dummy asks for a password and fails with crypt: Invalid argument after removing the line for dummy from gshadow newgrp works A similar bug was reported on the redhat tracker: https://bugzilla.redhat.com/show_bug.cgi?id=988184 cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=14.04 DISTRIB_CODENAME=trusty DISTRIB_DESCRIPTION=Ubuntu 14.04 LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1355111/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354406] Re: PIN-locked phone becomes unresponsive after simultaneous alarms
Feels like unity8 is involved if the phone becomes unresponsive in this case... ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1354406 Title: PIN-locked phone becomes unresponsive after simultaneous alarms Status in “indicator-datetime” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: Steps to reproduce 1. Run recent image (I'm on #178 on mako) 2. Setup pin lock in system settings 3. Enter two events for the same time, soon, in your google calendar 4. Have your phone sync your google calendar using system settings - accounts 5. Lock screen 6. Wait for the events What happens * Multiple alarms go off, notification on screen. You can hear two rings at once (separate bug) * Tap notification to make it go away * Sound continues, but there's no notification on screen. At this point you cannot unlock the phone. You can swipe away the welcome screen, but the display dims a bit once you do, and nothing is clickable - can't click numbers in pin unlock, can't swipe down indicators.. You have to reboot the phone to get past this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1354406/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355673] [NEW] corrupted thumbnails for some videos
Public bug reported: mako #185 last known good image: ? For this video http://trailers.divx.com/divx_prod/profiles/Micayala_DivX1080p_ASP.divx the thumbnail in the video scope corrupted (cf screenshot) The video plays fine in mediaplayer. TEST CASE: 1. Download http://trailers.divx.com/divx_prod/profiles/Micayala_DivX1080p_ASP.divx 2. Go to the video scope. ACTUAL RESULT Thumbnail is corrupted. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-scope-mediascanner2 0.2+14.10.20140811-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Tue Aug 12 11:09:40 2014 InstallationDate: Installed on 2014-08-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140812-020204) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity-scope-mediascanner (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic ** Attachment added: 0c0118ddebe1763dc8fb6ad19f6f52f6.png https://bugs.launchpad.net/bugs/1355673/+attachment/4175220/+files/0c0118ddebe1763dc8fb6ad19f6f52f6.png ** Description changed: mako #185 last known good image: ? - For this video - http://trailers.divx.com/divx_prod/profiles/Micayala_DivX1080p_ASP.divx - the thumbnail in the video scope corrupted (cf screenshot) + For this video http://trailers.divx.com/divx_prod/profiles/Micayala_DivX1080p_ASP.divx the thumbnail in the video scope corrupted (cf screenshot) + The video plays fine in mediaplayer. TEST CASE: 1. Download http://trailers.divx.com/divx_prod/profiles/Micayala_DivX1080p_ASP.divx 2. Go to the video scope. ACTUAL RESULT Thumbnail is corrupted. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-scope-mediascanner2 0.2+14.10.20140811-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Tue Aug 12 11:09:40 2014 InstallationDate: Installed on 2014-08-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140812-020204) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1355673 Title: corrupted thumbnails for some videos Status in “unity-scope-mediascanner” package in Ubuntu: New Bug description: mako #185 last known good image: ? For this video http://trailers.divx.com/divx_prod/profiles/Micayala_DivX1080p_ASP.divx the thumbnail in the video scope corrupted (cf screenshot) The video plays fine in mediaplayer. TEST CASE: 1. Download http://trailers.divx.com/divx_prod/profiles/Micayala_DivX1080p_ASP.divx 2. Go to the video scope. ACTUAL RESULT Thumbnail is corrupted. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-scope-mediascanner2 0.2+14.10.20140811-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Tue Aug 12 11:09:40 2014 InstallationDate: Installed on 2014-08-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140812-020204) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1355673/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354431] Re: Videos recorded with the camera do not appear in the media scope
cannot reproduce anymore. ** Changed in: unity-scope-mediascanner (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scope-mediascanner in Ubuntu. https://bugs.launchpad.net/bugs/1354431 Title: Videos recorded with the camera do not appear in the media scope Status in “unity-scope-mediascanner” package in Ubuntu: Fix Released Bug description: mako #178 Videos recorded with the camera are visible in the photo roll of the camera-app but are visible on the media scope. TEST CASE 1. Launch the camera and record a video 2. Switch to photo roll - verify that the video has been recorded and is correct 3. Switch to the media scope - Verify that a screenshot of the video is displayed and you can play it. ACTUAL RESULT The video exists in ~/Videos/camera, it can be played with the mediaplayer but it is not listed in the media scope even in the category 'My Videos/Everything' ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity-scope-mediascanner2 0.2+14.10.20140801.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Fri Aug 8 14:47:21 2014 InstallationDate: Installed on 2014-08-08 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140808-020205) SourcePackage: unity-scope-mediascanner UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-mediascanner/+bug/1354431/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347721] Update Released
The verification of the Stable Release Update for apt has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1347721 Title: Saucy - Trusty upgrade failed: procps fails to configure Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Saucy: Fix Released Status in “apt” source package in Trusty: Triaged Status in “apt” source package in Utopic: Fix Released Bug description: Test Case: 1. Install Saucy + the task ubuntu-dekstop^ 2. Upgrade with do-release-upgrade Result: Upgrade fails with: Setting up libprocps3:i386 (1:3.3.9-1ubuntu2) ... dpkg: dependency problems prevent configuration of procps: procps depends on initscripts; however: Package initscripts is not configured yet. dpkg: error processing package procps (--configure): dependency problems - leaving unconfigured == Original Description == I'm just performing 14.04.1 pre-release testing and decided to try a Saucy - Trusty upgrade even though Saucy recently reached EOL. I'd expected to be told no upgrade was available (or was impossible) early in the process if it were not possible at this point in time but the upgrade appeared to be in progress until the attached warning appeared (I'd guess about half-way into the upgrade process based on lapsed time) . No idea what will happen on reboot so I wanted to file this prior to reboot. I'll follow up later. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CrashDB: ubuntu CurrentDesktop: GNOME Date: Wed Jul 23 09:03:39 2014 InstallationDate: Installed on 2014-07-17 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131015) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2014-07-23 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1347721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347721] Re: Saucy - Trusty upgrade failed: procps fails to configure
This bug was fixed in the package apt - 0.9.9.1~ubuntu3.3 --- apt (0.9.9.1~ubuntu3.3) saucy-proposed; urgency=low * apt-pkg/packagemanager.cc: - fix incorrect configure ordering in the SmartConfigure step by skiping packages that do not need immediate action (LP: #1347721) -- Michael Vogt michael.v...@ubuntu.com Tue, 29 Jul 2014 21:37:01 +0200 ** Changed in: apt (Ubuntu Saucy) Status: Fix Committed = Fix Released -- 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/1347721 Title: Saucy - Trusty upgrade failed: procps fails to configure Status in “apt” package in Ubuntu: Fix Released Status in “apt” source package in Saucy: Fix Released Status in “apt” source package in Trusty: Triaged Status in “apt” source package in Utopic: Fix Released Bug description: Test Case: 1. Install Saucy + the task ubuntu-dekstop^ 2. Upgrade with do-release-upgrade Result: Upgrade fails with: Setting up libprocps3:i386 (1:3.3.9-1ubuntu2) ... dpkg: dependency problems prevent configuration of procps: procps depends on initscripts; however: Package initscripts is not configured yet. dpkg: error processing package procps (--configure): dependency problems - leaving unconfigured == Original Description == I'm just performing 14.04.1 pre-release testing and decided to try a Saucy - Trusty upgrade even though Saucy recently reached EOL. I'd expected to be told no upgrade was available (or was impossible) early in the process if it were not possible at this point in time but the upgrade appeared to be in progress until the attached warning appeared (I'd guess about half-way into the upgrade process based on lapsed time) . No idea what will happen on reboot so I wanted to file this prior to reboot. I'll follow up later. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: ubuntu-release-upgrader-core 1:0.220.2 ProcVersionSignature: Ubuntu 3.11.0-26.45-generic 3.11.10.12 Uname: Linux 3.11.0-26-generic i686 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: i386 CrashDB: ubuntu CurrentDesktop: GNOME Date: Wed Jul 23 09:03:39 2014 InstallationDate: Installed on 2014-07-17 (5 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release i386 (20131015) PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader UpgradeStatus: Upgraded to trusty on 2014-07-23 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1347721/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304074] Re: [X550CC, Realtek ALC270, Black Headphone Out, Left] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New = Confirmed -- 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/1304074 Title: [X550CC, Realtek ALC270, Black Headphone Out, Left] No sound at all Status in “alsa-driver” package in Ubuntu: Confirmed Bug description: I have sound from the laptop, but no sound when i use the jack. It works when running windows. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1734 F pulseaudio /dev/snd/pcmC0D0p: daniel 1734 F...m pulseaudio Date: Mon Apr 7 23:17:24 2014 InstallationDate: Installed on 2014-02-26 (40 days ago) InstallationMedia: Ubuntu-GNOME 13.10 Saucy Salamander - Release amd64 (20131017) MarkForUpload: True PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 1734 F pulseaudio /dev/snd/pcmC0D0p: daniel 1734 F...m pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [X550CC, Realtek ALC270, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550CC.217 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550CC dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550CC.217:bd10/16/2013:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550CC dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1304074/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340510] Re: session screen seen upon quick power key strike
Alright, I'm preparing to propose a fix/workaround in Mir. Although sadly that won't do us any good if Unity8 still takes a second or so to respond to wakeup. My Mir solution depends on all clients (and nested servers like Unity8) responding to wakeup and providing a new frame (the greeter) in less than half a second (preferably faster than that). If Unity8 doesn't do that (or prepare a greeter screen earlier when the display turns off) then no improvement to Mir will help. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1340510 Title: session screen seen upon quick power key strike Status in Mir: In Progress Status in Mir 0.4 series: Won't Fix Status in Mir 0.5 series: Won't Fix Status in Mir 0.6 series: Triaged Status in Unity System Compositor: New Status in The Unity 8 shell: New Status in “mir” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: Image #125 on N4 1) boot phone and unlock phone to display dash 2) strike power key to blank unblank screen quickly 3) the dash is seen instead of lockscreen for a brief moment logging against u-s-c as this was fixed, but power policy changes may have effected this To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1340510/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
Good question! I'm on Utopic development version (i. e. 14.10) and there is no way to get network back on automatically after hibernate! (suspend often caused my machine to hard-lock so I can only use hibernate in my case) It's a shame everyone ignores us, saying this is of minor importance. BTW, it worked fine in Saucy, so this is evidence enough that someone dabbled with the code and broke it AGAIN. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355700] [NEW] Two spaces erroneously translates to fullstop-space every time
Public bug reported: space-space translates to fullstop-space, which is not wanted in many situations. I have no keyboard helping options enabled in system settings - language text. Open any app which has a text input including browser and the new clock reboot- alarm screen. Press space multiple times - perhaps to pad some text. Each space-space turns into fullstop-space, which might be useful on the first occasion, but if you're putting in 10 spaces to pad some text, you get a load of full stops. See screenshots. ** Affects: ubuntu-keyboard (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: device-2014-08-12-104839.png https://bugs.launchpad.net/bugs/1355700/+attachment/4175258/+files/device-2014-08-12-104839.png -- 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/1355700 Title: Two spaces erroneously translates to fullstop-space every time Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: space-space translates to fullstop-space, which is not wanted in many situations. I have no keyboard helping options enabled in system settings - language text. Open any app which has a text input including browser and the new clock reboot- alarm screen. Press space multiple times - perhaps to pad some text. Each space-space turns into fullstop-space, which might be useful on the first occasion, but if you're putting in 10 spaces to pad some text, you get a load of full stops. See screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1355700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355700] Re: Two spaces erroneously translates to fullstop-space
** Attachment added: device-2014-08-12-104946.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1355700/+attachment/4175259/+files/device-2014-08-12-104946.png -- 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/1355700 Title: Two spaces erroneously translates to fullstop-space every time Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: space-space translates to fullstop-space, which is not wanted in many situations. I have no keyboard helping options enabled in system settings - language text. Open any app which has a text input including browser and the new clock reboot- alarm screen. Press space multiple times - perhaps to pad some text. Each space-space turns into fullstop-space, which might be useful on the first occasion, but if you're putting in 10 spaces to pad some text, you get a load of full stops. See screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1355700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355700] Re: Two spaces erroneously translates to fullstop-space
** Attachment added: device-2014-08-12-105025.png https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1355700/+attachment/4175260/+files/device-2014-08-12-105025.png ** Summary changed: - Two spaces erroneously translates to fullstop-space + Two spaces erroneously translates to fullstop-space every time -- 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/1355700 Title: Two spaces erroneously translates to fullstop-space every time Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: space-space translates to fullstop-space, which is not wanted in many situations. I have no keyboard helping options enabled in system settings - language text. Open any app which has a text input including browser and the new clock reboot- alarm screen. Press space multiple times - perhaps to pad some text. Each space-space turns into fullstop-space, which might be useful on the first occasion, but if you're putting in 10 spaces to pad some text, you get a load of full stops. See screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1355700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355700] Re: Two spaces erroneously translates to fullstop-space every time
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: ubuntu-keyboard (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-keyboard in Ubuntu. https://bugs.launchpad.net/bugs/1355700 Title: Two spaces erroneously translates to fullstop-space every time Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: space-space translates to fullstop-space, which is not wanted in many situations. I have no keyboard helping options enabled in system settings - language text. Open any app which has a text input including browser and the new clock reboot- alarm screen. Press space multiple times - perhaps to pad some text. Each space-space turns into fullstop-space, which might be useful on the first occasion, but if you're putting in 10 spaces to pad some text, you get a load of full stops. See screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1355700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355700] Re: Two spaces erroneously translates to fullstop-space every time
Most annoying if you have ended a question with a ? hit 2 spaces to start typing something else and a fullstop appears -- 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/1355700 Title: Two spaces erroneously translates to fullstop-space every time Status in “ubuntu-keyboard” package in Ubuntu: Confirmed Bug description: space-space translates to fullstop-space, which is not wanted in many situations. I have no keyboard helping options enabled in system settings - language text. Open any app which has a text input including browser and the new clock reboot- alarm screen. Press space multiple times - perhaps to pad some text. Each space-space turns into fullstop-space, which might be useful on the first occasion, but if you're putting in 10 spaces to pad some text, you get a load of full stops. See screenshots. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyboard/+bug/1355700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355706] [NEW] Indicator icon should be monochrome
Public bug reported: Currrently, if you have undisplayed notifications, the notification icon shows as a green bell. Since all the other notification icons are monochromatic, I think the behaviour should be: - no undisplayed notifications: show an unfilled white bell (or simply don't display the icon?) - undisplayed notifications: show a filled white bell. Using image r185. ** Affects: indicator-messages (Ubuntu) Importance: Undecided Status: New ** Tags: avengers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-messages in Ubuntu. https://bugs.launchpad.net/bugs/1355706 Title: Indicator icon should be monochrome Status in “indicator-messages” package in Ubuntu: New Bug description: Currrently, if you have undisplayed notifications, the notification icon shows as a green bell. Since all the other notification icons are monochromatic, I think the behaviour should be: - no undisplayed notifications: show an unfilled white bell (or simply don't display the icon?) - undisplayed notifications: show a filled white bell. Using image r185. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1355706/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 525128] Re: Australian timezone incorrectly labelled in date output
** Changed in: tzdata (Debian) Status: Won't Fix = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/525128 Title: Australian timezone incorrectly labelled in date output Status in “tzdata” package in Ubuntu: Fix Released Status in “tzdata” package in Debian: Fix Released Bug description: Binary package hint: firefox-3.5 When running the date command with my timezone set to Australia/Canberra (or any of the Australian Eastern seaboard sites), the timezone is displayed as EST. This is likely to cause confusion with the American EST timezone. The correct label for Australian Eastern Standard Time is AEST. In addition, the label for Australian Eastern Daylight Time doesn't appear to exist. This should be AEDT. As an example, a nearby timezone, the New Zealand Daylight Time (NZDT) label is correctly displayed when daylight time is in effect. The non-existence of the AEDT timezone causes a lot of trouble when you are working with hosts across states in the Australian Eastern timezones. One of these states, Queensland, does not have daylight time in summer. So when you are looking at the date on a host in Sydney that should be in AEDT, and a host in Brisbane that should be in AEST, both are reporting they are in EST, but an hour apart. This problem is not limited to the Ubuntu distribution; it also exists in RHEL, that I'm aware of. ProblemType: Bug Architecture: amd64 Date: Sun Feb 21 13:43:12 2010 DistroRelease: Ubuntu 9.10 InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) NonfreeKernelModules: fglrx Package: firefox 3.5.7+nobinonly-0ubuntu0.9.10.1 PackageArchitecture: all ProcEnviron: LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-19.56-generic SourcePackage: firefox-3.5 Uname: Linux 2.6.31-19-generic x86_64 XsessionErrors: (gnome-settings-daemon:3710): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (gnome-settings-daemon:3710): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed (polkit-gnome-authentication-agent-1:3813): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed (nautilus:3809): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed (firefox:3897): GLib-WARNING **: g_set_prgname() called multiple times To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/525128/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348334] Re: Actions aren't sending state over the bus
This bug was fixed in the package platform-api - 2.2.0+14.10.20140808-0ubuntu1 --- platform-api (2.2.0+14.10.20140808-0ubuntu1) utopic; urgency=low [ thomas-voss ] * Implement installation of changed handlers. Subscribe to state properties. (LP: #1348334) -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 08 Aug 2014 02:07:56 + -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1348334 Title: Actions aren't sending state over the bus Status in Indicator Location: Confirmed Status in Location Service: New Status in Platform API: In Progress Status in “indicator-location” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Fix Released Status in “platform-api” package in Ubuntu: Fix Released Bug description: Trying to use QDBusActionGroup it toggle gps enabled in system- settings I found that the enabled state isn't being sent. Same is true when toggling from inside the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1348334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348334] Re: Actions aren't sending state over the bus
This bug was fixed in the package location-service - 2.0.1+14.10.20140811-0ubuntu1 --- location-service (2.0.1+14.10.20140811-0ubuntu1) utopic; urgency=low [ thomas-voss ] * Make sure that state property changes are correctly reported to the bus. (LP: #1348334) [ Ubuntu daily release ] * New rebuild forced -- Ubuntu daily release ps-jenk...@lists.canonical.com Mon, 11 Aug 2014 10:21:20 + ** Branch linked: lp:ubuntu/utopic-proposed/indicator-location ** Branch linked: lp:ubuntu/utopic-proposed/location-service ** Branch linked: lp:ubuntu/utopic-proposed/platform-api ** Changed in: location-service (Ubuntu) Status: New = Fix Released ** Changed in: platform-api (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1348334 Title: Actions aren't sending state over the bus Status in Indicator Location: Confirmed Status in Location Service: New Status in Platform API: In Progress Status in “indicator-location” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Fix Released Status in “platform-api” package in Ubuntu: Fix Released Bug description: Trying to use QDBusActionGroup it toggle gps enabled in system- settings I found that the enabled state isn't being sent. Same is true when toggling from inside the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1348334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355422] Re: Can't dismiss notification bubbles
An idea I've had is to have the notification area act slightly similarly to an app. For example if you have a busy gmail account and are trying to watch a movie you don't to be interrupted by it. The possible solution would be to be able to click on the app you had open and have it sticky to the foreground until the app is closed or swipe and then have the notifications continue to appear. If you swipe the app away to open another you can then tap the Scope (as it is an app) and then that gets foreground attention freezing up the notifications again. Another possibly easier solution would be to add a cross or swipe action similar to Alan suggestion to just get rid of the notification. -- 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/1355422 Title: Can't dismiss notification bubbles Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: Confirmed Bug description: On a phone with accounts setup for twitter, facebook and 2x google accounts I get a fair number of notifications. Often times these notifications appear while I'm actually using the phone. This presents issues in multiple areas:- * If I'm in the dash I am blocked from using the search function because a notification covers the search button * If I'm in the dash and already searching, having typed something, I'm blocked from seeing what I'm typing by the notification * In apps I can't go back because the notification blocks the button You get the idea. Basically notifications slow me down, because I have to wait for them to disappear. I'd like to be able to dismiss them. On iOS you swipe up which is indicated with a horizontal bar to grab and swipe away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1355422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348334] Re: Actions aren't sending state over the bus
This bug was fixed in the package indicator-location - 13.10.0+14.10.20140808-0ubuntu1 --- indicator-location (13.10.0+14.10.20140808-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Fix bug that let controller-ualc's state get out of sync with the platform-api's ualc state. (LP: #1348334) [ CI bot ] * Resync trunk -- Ubuntu daily release ps-jenk...@lists.canonical.com Fri, 08 Aug 2014 02:03:44 + ** Changed in: indicator-location (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-location in Ubuntu. https://bugs.launchpad.net/bugs/1348334 Title: Actions aren't sending state over the bus Status in Indicator Location: Confirmed Status in Location Service: New Status in Platform API: In Progress Status in “indicator-location” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Fix Released Status in “platform-api” package in Ubuntu: Fix Released Bug description: Trying to use QDBusActionGroup it toggle gps enabled in system- settings I found that the enabled state isn't being sent. Same is true when toggling from inside the indicator. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-location/+bug/1348334/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355422] Re: Can't dismiss notification bubbles
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New = 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/1355422 Title: Can't dismiss notification bubbles Status in Ubuntu UX bugs: New Status in “unity8” package in Ubuntu: Confirmed Bug description: On a phone with accounts setup for twitter, facebook and 2x google accounts I get a fair number of notifications. Often times these notifications appear while I'm actually using the phone. This presents issues in multiple areas:- * If I'm in the dash I am blocked from using the search function because a notification covers the search button * If I'm in the dash and already searching, having typed something, I'm blocked from seeing what I'm typing by the notification * In apps I can't go back because the notification blocks the button You get the idea. Basically notifications slow me down, because I have to wait for them to disappear. I'd like to be able to dismiss them. On iOS you swipe up which is indicated with a horizontal bar to grab and swipe away. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ux/+bug/1355422/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343919] Re: USC does not respond to power key to turn screen on after 'sudo restart lightdm' while screen is on
** Changed in: unity-system-compositor Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-system-compositor in Ubuntu. https://bugs.launchpad.net/bugs/1343919 Title: USC does not respond to power key to turn screen on after 'sudo restart lightdm' while screen is on Status in Unity System Compositor: Fix Released Status in “unity-system-compositor” package in Ubuntu: Fix Released Bug description: Steps to reproduce: 0. phablet-shell to phone 1. Ensure screen is ON 2. sudo stop lightdm 3. sudo start lightdm 4. Press power button to turn screen off 5. Press power button to turn screen on again Expected behavior: Screen turns on Actual behavior: Nothing happens USC is stuck at PowerdMediator::wait_for_state() Note that this doesn't happen if we stop lightdm while the screen is OFF. A quick read of the powerd logs indicates that somehow the state of powerd is messed up, it's not consistent with reality. I am not familiar enough with powerd to tell if this is USC's or powerd's problem. I have attached the powerd log for the problematic screen off/on case, and for the normal case for comparison. To manage notifications about this bug go to: https://bugs.launchpad.net/unity-system-compositor/+bug/1343919/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1346367] Re: Window stack reports app in focus even when lockscreen is up.
** Changed in: qtmir Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-mir in Ubuntu. https://bugs.launchpad.net/bugs/1346367 Title: Window stack reports app in focus even when lockscreen is up. Status in Qt integration with the Mir display server: Fix Committed Status in Unity Mir: In Progress Status in “qtmir” package in Ubuntu: New Status in “unity-mir” package in Ubuntu: New Bug description: This means that (push) notifications for an application aren't presented if that application was in the foreground when the screen is locked or turned off, which is bad -- that's very often when you most want them presented. With ubuntu-push-client 0.49 or greater (if you install it by hand make sure you restart the user-session job ubuntu-push-client), you can try presenting a notification by doing gdbus call -e -d com.ubuntu.Postal -o /com/ubuntu/Postal/_ -m com.ubuntu.Postal.Post _ubuntu-system-settings 'null' To manage notifications about this bug go to: https://bugs.launchpad.net/qtmir/+bug/1346367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1273752] Re: Can't Copy Crash Report Details to Clipboard
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1273752 Title: Can't Copy Crash Report Details to Clipboard Status in “apport” package in Ubuntu: Confirmed Bug description: Often times, after receiving a crash report, if I click the Continue button it doesn't launch the browser for me to submit my crash to launchpad.net. Because of this, I'd always like to copy the crash report to my clipboard before clicking the continue button, so that I can manually provide this information into a bug report to launchpad.net. However, this option is not available. More over, there is absolutely *no way* to copy any text from this crash report's dialog window! 1) You cannot ctrl-a to select all. 2) Ctrl-c doesn't copy anything 3) Right-clicking doesn't produce a context menu where you can select Copy. This is an unfinished design. You should always give the user the ability to copy any text displayed in the UI. Next to the Show/Hide details button, I suggest adding a Copy to Clipboard button. If not this, please offer some way to achieve this from the GUI. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-gtk 2.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl ApportLog: ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 28 10:21:00 2014 InstallationDate: Installed on 2013-10-07 (113 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1273752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1273752] Re: Can't Copy Crash Report Details to Clipboard
jordanbowman, why don't you add yourself to the affects me too list? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1273752 Title: Can't Copy Crash Report Details to Clipboard Status in “apport” package in Ubuntu: Confirmed Bug description: Often times, after receiving a crash report, if I click the Continue button it doesn't launch the browser for me to submit my crash to launchpad.net. Because of this, I'd always like to copy the crash report to my clipboard before clicking the continue button, so that I can manually provide this information into a bug report to launchpad.net. However, this option is not available. More over, there is absolutely *no way* to copy any text from this crash report's dialog window! 1) You cannot ctrl-a to select all. 2) Ctrl-c doesn't copy anything 3) Right-clicking doesn't produce a context menu where you can select Copy. This is an unfinished design. You should always give the user the ability to copy any text displayed in the UI. Next to the Show/Hide details button, I suggest adding a Copy to Clipboard button. If not this, please offer some way to achieve this from the GUI. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-gtk 2.13.2-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0 Uname: Linux 3.13.0-5-generic x86_64 NonfreeKernelModules: wl ApportLog: ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jan 28 10:21:00 2014 InstallationDate: Installed on 2013-10-07 (113 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-01-08 (19 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1273752/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355728] [NEW] The apport-gtk details window is not resizeable
Public bug reported: This seems to be an old (once fixed) bug (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/865754) resurfacing. The window is not unreadable small but still too small to see longer lines without scrolling (see screenshot) and it is not resizeable. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-gtk 2.14.1-0ubuntu3.3 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 12:20:00 2014 ExecutablePath: /usr/share/apport/apport-gtk InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-05-01 (103 days ago) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug regression-release third-party-packages trusty ** Attachment added: Screenshot from 2014-08-12 12:19:12.png https://bugs.launchpad.net/bugs/1355728/+attachment/4175275/+files/Screenshot%20from%202014-08-12%2012%3A19%3A12.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1355728 Title: The apport-gtk details window is not resizeable Status in “apport” package in Ubuntu: New Bug description: This seems to be an old (once fixed) bug (https://bugs.launchpad.net/ubuntu/+source/apport/+bug/865754) resurfacing. The window is not unreadable small but still too small to see longer lines without scrolling (see screenshot) and it is not resizeable. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport-gtk 2.14.1-0ubuntu3.3 ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4 Uname: Linux 3.13.0-33-generic x86_64 ApportLog: ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 12:20:00 2014 ExecutablePath: /usr/share/apport/apport-gtk InterpreterPath: /usr/bin/python3.4 PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-05-01 (103 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1355728/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314367] Re: Flickering with Ubuntu 14.04 and nvidia card reappeared
The bug is not fixed in 340.24. With 14.04.1 desktop 64b and this nvidia driver version the issue is still there. I checked the Force full screen redraws (buffer swap) on repaint option in compiz and this works for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1314367 Title: Flickering with Ubuntu 14.04 and nvidia card reappeared Status in “xorg” package in Ubuntu: Confirmed Bug description: As requested in Bug #1310633 I'm opening a new bug. With a previous version of Ubuntu I already had this flickering. With additional options for the kernel module I was able to fix the flickering. options nvidia NVreg_RegistryDwords=PerfLevelSrc=0x NVreg_Mobile=3 NVreg_ModifyDeviceFiles=0 With version 14.04 and the nvidia-331 (331.38-0ubuntu7) driver the flickering reappeared although the line is still present in options.conf. Using modprobe --resolve-alias nvidia I found the correct driver module name which in my case is nvidia_331. Changing the module name in options.conf to nvidia_331 X doesn't start anymore. Removing the NVreg_ModifyDeviceFiles option X is starting again, but does not solve the issue. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 331.38 Wed Jan 8 19:32:30 PST 2014 GCC version: gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: Unity Date: Tue Apr 29 21:09:41 2014 DistUpgraded: 2014-04-17 23:47:50,572 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 3.13.0-24-generic, x86_64: installed nvidia-331, 331.38, 3.13.0-24-generic, x86_64: installed vboxhost, 4.3.10, 3.13.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GT215GLM [Quadro FX 1800M] [10de:0cbc] (rev a2) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1521] InstallationDate: Installed on 2012-11-17 (528 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) MachineType: Hewlett-Packard HP EliteBook 8540w PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver pata_pcmcia ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=c6af930a-63f1-4015-9c42-bdde793e3e5a ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-17 (11 days ago) dmi.bios.date: 09/13/2013 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68CVD Ver. F.24 dmi.board.name: 1521 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 32.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8540w dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11+14.04.20140409-0ubuntu1 version.ia32-libs: ia32-libs 20090808ubuntu36 version.libdrm2: libdrm2 2.4.52-1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue Apr 29 21:06:04 2014 xserver.configfile: default xserver.errors: open /dev/fb0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1314367/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355726] Re: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard)
There's a suspicion env isn't set up properly after the wizard. ** Also affects: unity8 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1355726 Title: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard) Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: Do a 185 --wipe upgrade. Pass the initial boot wizard. Go to unity 8 and see black screen. Gave it 5 minutes then rebooted (using the phone UI to do it). The problem goes away after that reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1355726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355726] Re: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard)
Although: phablet@ubuntu-phablet:~$ initctl list-env -g | grep MIR MIR_SERVER_NAME=session-0 MIR_SERVER_PROMPT_FILE=1 MIR_SOCKET=/run/user/32011/mir_socket UNITY_MIR_SOCKET=/run/mir_socket WIZARD_ORIG_MIR_SOCKET=/run/mir_socket phablet@ubuntu-phablet:~$ initctl list-env unity8-dash | grep MIR MIR_SERVER_NAME=session-0 MIR_SERVER_PROMPT_FILE=1 MIR_SOCKET=/run/user/32011/mir_socket UNITY_MIR_SOCKET=/run/mir_socket WIZARD_ORIG_MIR_SOCKET=/run/mir_socket -- 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/1355726 Title: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard) Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: Do a 185 --wipe upgrade. Pass the initial boot wizard. Go to unity 8 and see black screen. Gave it 5 minutes then rebooted (using the phone UI to do it). The problem goes away after that reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1355726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355726] Re: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard)
But still, unity8-dash.log: UbuntuClientIntegration: connection to Mir server failed. Check that a Mir server is running, and the correct socket is being used and is accessible. The shell may have rejected the incoming connection, so check its log file -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1355726 Title: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard) Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: New Bug description: Do a 185 --wipe upgrade. Pass the initial boot wizard. Go to unity 8 and see black screen. Gave it 5 minutes then rebooted (using the phone UI to do it). The problem goes away after that reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1355726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1252121] Re: missing PrepareForSleep signal after resuming, causing networking to stay disabled
@andi3 Does hibernation work in Utopic? It is disabled for some unknown reasons in ubuntu for a long time, and I miss it very much. In addition to all now I'm back to Windows 7 and waiting for the fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd-shim in Ubuntu. https://bugs.launchpad.net/bugs/1252121 Title: missing PrepareForSleep signal after resuming, causing networking to stay disabled Status in NetworkManager: New Status in wicd: New Status in “systemd-shim” package in Ubuntu: Confirmed Status in “systemd-shim” source package in Saucy: Confirmed Status in “systemd-shim” source package in Trusty: Confirmed Bug description: As per request from bug #1184262, this is a new report, along with dbus (to be attached) ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: systemd-services 204-0ubuntu19 Uname: Linux 3.12.0-custom x86_64 ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Sun Nov 17 20:24:41 2013 MarkForUpload: True SourcePackage: systemd UpgradeStatus: Upgraded to saucy on 2013-10-17 (31 days ago) SRU INFORMATION: FIX: https://github.com/desrt/systemd-shim/commit/9e1ebe3ab (in trusty already) Regression potential: Low. Flushing the session bus was introduced in version 4 and is obviously bogus as in a system D-BUS service there is no session bus. This causes lots of confusing error messages and unnecessary overhead like trying to start dbus-launch. Flushing the system bus is low-risk, in most cases it's a no-op and it would otherwise prevent losing signals after waking up. No known regressions. TEST CASE: Run several suspend/resume cycles with the lid, session indicator menu, and verify that the network comes back up. It is known that this fix is necessary but not sufficient, so it is not expected to fix all cases. But it should not make things worse, so if network now does not come up any more on a machine where it previously worked this would count as failure/regression. To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1252121/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308169] Re: apport-bug on .crash file does not send report
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1308169 Title: apport-bug on .crash file does not send report Status in “apport” package in Ubuntu: Confirmed Bug description: When giving apport-bug a .crash file and telling it to send the report, it writes an empty .upload file, but does not appear to send the report: ryan@feh:~$ sudo apport-bug /var/crash/_usr_lib_squid3_pinger.0.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (63.2 KB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): s ryan@feh:~$ ls -lsa /var/crash/_usr_lib_squid3_pinger.0.* 64 -rw-r- 1 root root 63854 Apr 15 10:33 /var/crash/_usr_lib_squid3_pinger.0.crash 0 -rw-r--r-- 1 root root 0 Apr 15 10:44 /var/crash/_usr_lib_squid3_pinger.0.upload ryan@feh:~$ ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportLog: ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: called for pid 10115, signal 11, core limit 0 ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: executable: /usr/lib/squid3/pinger (command line (pinger)) ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment ERROR: apport (pid 16419) Tue Apr 15 07:37:43 2014: wrote report /var/crash/_usr_lib_squid3_pinger.0.crash ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CrashReports: 640:0:0:16086:2014-04-12 19:58:08.832940604 -0700:2014-04-13 03:55:12.546230475 -0700:/var/crash/_usr_lib_mailman_bin_list_lists.0.crash 640:0:0:63854:2014-04-15 10:33:06.036259174 -0700:2014-04-15 10:36:21.278098132 -0700:/var/crash/_usr_lib_squid3_pinger.0.crash 644:0:0:0:2014-04-15 10:36:23.354031253 -0700:2014-04-15 10:36:23.354031253 -0700:/var/crash/_usr_lib_squid3_pinger.0.upload 640:33:33:982302:2014-04-12 19:47:16.481460672 -0700:2014-04-13 03:55:12.478232672 -0700:/var/crash/_usr_bin_php5.33.crash 640:0:0:42350107:2014-04-15 05:24:07.978228219 -0700:2014-04-15 05:23:28.267508485 -0700:/var/crash/_usr_sbin_apache2.0.crash Date: Tue Apr 15 10:40:38 2014 InstallationDate: Installed on 2012-04-17 (728 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Beta amd64 (20120415) PackageArchitecture: all ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-04-13 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1308169/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1338697] Re: Alarm sound url read from a saved alarm is always empty
Fix committed into lp:ubuntu-ui-toolkit/staging at revision None, scheduled for release in ubuntu-ui-toolkit, milestone Unknown ** Changed in: ubuntu-ui-toolkit Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtorganizer5-eds in Ubuntu. https://bugs.launchpad.net/bugs/1338697 Title: Alarm sound url read from a saved alarm is always empty Status in Clock application for Ubuntu devices: In Progress Status in Ubuntu UI Toolkit: Fix Committed Status in “qtorganizer5-eds” package in Ubuntu: Invalid Bug description: In the clock app, I am trying to add the option to set custom sounds for an alarm. Creating a new alarm and choosing a custom sound works properly. When the alarm is triggered, it rings using the correct sound. However when you read that alarm from the alarm model and output the sound url, it is always empty. As a result, one cannot check an alarm to see what sound was assigned to it. I have created a sample alarms app to illustrate the issue at lp:~nik90/ubuntu-clock-app/alarmtest Steps to reproduce bug: 1. Create a new alarm by pressing the + header button 2. Set alarm to ring in the next 10-15 seconds 3. Set a custom alarm sound by choosing one in the option selector 4. Save alarm In the main page, click on the created alarm What happens: The alarm sound value is empty What should happen: The alarm sound correctly points to the path of the chosen sound To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1338697/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355726] Re: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard)
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: unity8 (Ubuntu) Status: New = 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/1355726 Title: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard) Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: Do a 185 --wipe upgrade. Pass the initial boot wizard. Go to unity 8 and see black screen. Gave it 5 minutes then rebooted (using the phone UI to do it). The problem goes away after that reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1355726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354560] Re: Indicator doesn't show connected status when associated with hidden network
** Changed in: indicator-network (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1354560 Title: Indicator doesn't show connected status when associated with hidden network Status in “indicator-network” package in Ubuntu: New Bug description: After connecting to a hidden wifi network the indicator does not correctly show the connection status. Instead of the connected icon in the top bar there's just a blank space, the hidden network shows up in the indicator's network list twice, and there's no check mark next to either of the entries in the network list. The phone is associated with the wireless network however and has a functioning network connection. I'm attaching screenshots of the indicator when this is happening as well as other data requested in bug #1202806. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1354560/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355726] Re: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard)
After some digging this isn't the Wizzard causing the issue, If you do a reboot then remove the ~/.config/ubuntu-system-settings/wizard-has- run the wizzard runs and is closed correctly and the unity8-dash appears as expected. ** Tags added: mako qa-daily-testing rtn14 u185 ** Tags removed: rtn14 ** Tags added: rtm14 -- 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/1355726 Title: image 185 --wipe causes unity 8 not to show up on first boot (after welcome wizard) Status in “ubuntu-system-settings” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Bug description: Do a 185 --wipe upgrade. Pass the initial boot wizard. Go to unity 8 and see black screen. Gave it 5 minutes then rebooted (using the phone UI to do it). The problem goes away after that reboot. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1355726/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1352660] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:11:changed:ModemManager::Private::ofono_appeared:ModemManager::Private::Private:ModemManager
*** This bug is a duplicate of bug 1352744 *** https://bugs.launchpad.net/bugs/1352744 ** This bug has been marked a duplicate of bug 1352744 indicator-network crash on org.freedesktop.DBus.Error.UnknownMethod: Method GetProperties with signature on interface org.ofono.SimManager doesn't exist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1352660 Title: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network- service:11:changed:ModemManager::Private::ofono_appeared:ModemManager::Private::Private:ModemManager::ModemManager:construct Status in “indicator-network” package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding indicator-network. This problem was most recently seen with version 0.5.1+14.10.20140725-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/f86b8466c22fb672265bf786a4a78ccf2bd109b3 contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1352660/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1305966] Re: tracker-extract crashed with SIGSEGV in gst_base_parse_push_frame()
*** This bug is a duplicate of bug 1301914 *** https://bugs.launchpad.net/bugs/1301914 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tracker (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tracker in Ubuntu. https://bugs.launchpad.net/bugs/1305966 Title: tracker-extract crashed with SIGSEGV in gst_base_parse_push_frame() Status in “tracker” package in Ubuntu: Confirmed Bug description: gnome-shell startup after general freeze and reboot ProblemType: Crash DistroRelease: Ubuntu 14.04 Package: tracker-extract 0.16.2-1ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 NonfreeKernelModules: wl fglrx ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CrashCounter: 1 CurrentDesktop: GNOME Date: Thu Apr 10 16:57:08 2014 ExecutablePath: /usr/lib/tracker/tracker-extract InstallationDate: Installed on 2013-05-15 (330 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) ProcCmdline: /usr/lib/tracker/tracker-extract SegvAnalysis: Segfault happened at: 0x7fdd805fdc4f:mov%r12,0x48(%rax) PC (0x7fdd805fdc4f) ok source %r12 ok destination 0x48(%rax) (0x0048) not located in a known VMA region (needed writable region)! Stack memory exhausted (SP below stack segment) SegvReason: writing NULL VMA Signal: 11 SourcePackage: tracker StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstaudio-1.0.so.0 ?? () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0 gst_base_parse_push_frame () from /usr/lib/x86_64-linux-gnu/libgstbase-1.0.so.0 Title: tracker-extract crashed with SIGSEGV in gst_base_parse_push_frame() UpgradeStatus: Upgraded to trusty on 2014-04-05 (4 days ago) UserGroups: adm cdrom dialout dip libvirtd lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1305966/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350610] Re: Apps scope title is not the ubuntu logo
** Changed in: unity-scope-click (Ubuntu) Assignee: (unassigned) = Pawel Stolowski (stolowski) -- 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/1350610 Title: Apps scope title is not the ubuntu logo Status in “unity-scope-click” package in Ubuntu: Triaged Bug description: It's titled Apps, but it should be the ubuntu logo according to designs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1350610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1351916] Re: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work
you need to ask the realtek engineer who add support of alc271 https://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/pci/hda?id=fe3eb0a73ca052ee9346a1544f4c00e697cc9a4e -- 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/1351916 Title: [Aspire V5-571G, Realtek ALC271X] 4-pin jack mic doesn't work Status in “alsa-driver” package in Ubuntu: New Bug description: I have an Acer Aspire V5-571G with a Realtek soundcard in which there is one 4-pin jack (for mic and headset). When i plug a 4-pin headset only output is detected while input remains the same (it still using the integrated computer mic). Right now im using Ubuntu 14.04.1 LTS but anyway it neither work in previous versions. EDIT: My soundcard is Realtek but in ubuntu is called HDA Intel PCH. --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas3548 F pulseaudio /dev/snd/pcmC0D0p: nicolas3548 F...m pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 14.04 InstallationDate: Installed on 2014-07-16 (17 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417) Package: alsa-driver (not installed) ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 Tags: trusty Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm bumblebee cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/21/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: V2.18 dmi.board.asset.tag: No Asset Tag dmi.board.name: Aspire V5-571G dmi.board.vendor: Acer dmi.board.version: V2.18 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: Acer dmi.chassis.version: V2.18 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrV2.18:bd06/21/2013:svnAcer:pnAspireV5-571G:pvrV2.18:rvnAcer:rnAspireV5-571G:rvrV2.18:cvnAcer:ct9:cvrV2.18: dmi.product.name: Aspire V5-571G dmi.product.version: V2.18 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1351916/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347147] Re: krb5 database operations enter infinite loop
Here's an ubdated debdiff that includes the security update applied to
trusty. I'm still waiting for a sponsor for this.
** Patch removed: debdiff between current trusty and linked branch
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1347147/+attachment/4166949/+files/krb5-trusty-stable.debdiff
** Patch added: Debdiff of lp:~hartmans/ubuntu/trusty/krb5/gss-infinite-loop
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1347147/+attachment/4175346/+files/krb5_1.12%2Bdfsg-2ubuntu5.debdiff
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1347147
Title:
krb5 database operations enter infinite loop
Status in The GNU Compiler Collection:
Fix Released
Status in Network Authentication System:
Unknown
Status in “gcc-4.8” package in Ubuntu:
Fix Released
Status in “gcc-4.9” package in Ubuntu:
Fix Released
Status in “krb5” package in Ubuntu:
Fix Released
Status in “gcc-4.8” source package in Trusty:
Confirmed
Status in “krb5” source package in Trusty:
Triaged
Bug description:
[Impact]
On krb5 KDC databases with more than a few hundred principals,
operations can enter an infinite loop in the database library. This
affects both read and write operations. If operators are fortunate,
they will encounter this bug while testing a migration. If they are
not so fortunate, they will encounter this bug in a production KDC
when the number of principals crosses the threshold where this bug
manifests, resulting in a service outage and possible database
corruption. Probably the only way to restore service in that
situation is to install a patched KDC or to downgrade to an unaffected
version.
Both Trusty and Utopic amd64 have been verified to have this issue.
One concrete reported example is an invocation of kdb5_util load (as
part of a slave KDC propagation) spinning:
http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html
Additional failure modes are likely
A branch is linked including the upstream work around for this bug,
along with two other patches to bugs already nominated for trusty
applied to the krb5 in trusty.
For utopic, the simplest fix is to rebuild krb5 with the compiler
currently in utopic. An alternative is to request that the Debian
maintainers (both monitoring this bug for such a request) upload the
upstream work around to Debian and sync that. You could do an ubuntu-
specific upload but it seems undesirable to introduce a change between
Ubuntu and Debian when all the right parties are happy to avoid it.
The upstream patch works around a compiler optimizer bug in the
gcc-4.8 series, which incorrectly deduces that a strict aliasing
violation has occurred and miscompiles part of the bundled libdb2
library that the KDC database back end depends upon. The
miscompilation causes a data structure to contain an inappropriate
cycle, which leads to an infinite loop when the structure is
traversed.
[Test Case]
apt-get install krb5-kdc krb5-admin-server
kdb5_util -W -r T create -s
awk 'BEGIN{ for (i = 0; i 1024; i++) { printf(ank -randkey a%06d\n, i) }
}' /dev/null | kadmin.local -r T
(Enter any password for the master key when requested.)
On platforms with this issue, kadmin.local spins consuming 100% CPU
after a few hundred principals have been created. (This is a000762
on two examples.)
To clean up,
rm /etc/krb5kdc/principal*
or
krb5kdc -r T destroy
but the latter can possibly enter the same infinite loop.
[Regression Potential]
Negligible.
It is theoretically possible that our upstream workaround, which
involves using TAILQ macros instead of CIRCLEQ macros in the bundled
libdb2 that backs the KDC database, will have some as-yet undiscovered
bugs or compiler interactions with consequences worse than this
current issue. I think this is rather unlikely.
The patched libdb2 passes both the extensive libdb2 test suite and the
rest of the krb5 test suite. Prior to patching, compiling krb5 with
an affected gcc would cause the krb5 test suite to stall when it
reached the libdb2 test suite. (The test suite stall is how we became
aware of the gcc optimizer bug.)
The BSD TAILQ macros are generally considered to be safer than the
CIRCLEQ macros, and the various open-source BSD derivatives have made
the corresponding change to their libdb sources years ago, with no
reported ill effects that I can see.
Original report from Ben Kaduk:
==
In some conditions, propagating a kerberos database to a slave KDC server can
stall.
This is due to a misoptimization by gcc 4.8 of the CIRCLEQ famliy of macros,
apparently due to overzealous strict aliasing deductions.
One case of this stall is reported at
http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html (and
the rest of the thread), and
[Touch-packages] [Bug 1355760] [NEW] mako fails to update
Public bug reported: Tried to update this morning and it failed, just hung. This was during the DC network outage we had in the UK AM. 185 is available but I can't upgrade to it. Tried rebooting. Now it's in a state where it won't update. phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 184 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/utopic-proposed last update: 2014-08-11 20:15:41 version version: 184 version ubuntu: 20140811.1 version device: 20140811.1 phablet@ubuntu-phablet:~$ system-image-cli -n phablet@ubuntu-phablet:~$ ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: system-image-cli 2.3.2-0ubuntu2 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Tue Aug 12 12:37:21 2014 InstallationDate: Installed on 2014-08-11 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140811-172006) PackageArchitecture: all SourcePackage: system-image UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: system-image (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1355760 Title: mako fails to update Status in “system-image” package in Ubuntu: New Bug description: Tried to update this morning and it failed, just hung. This was during the DC network outage we had in the UK AM. 185 is available but I can't upgrade to it. Tried rebooting. Now it's in a state where it won't update. phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 184 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/utopic-proposed last update: 2014-08-11 20:15:41 version version: 184 version ubuntu: 20140811.1 version device: 20140811.1 phablet@ubuntu-phablet:~$ system-image-cli -n phablet@ubuntu-phablet:~$ ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: system-image-cli 2.3.2-0ubuntu2 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Tue Aug 12 12:37:21 2014 InstallationDate: Installed on 2014-08-11 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140811-172006) PackageArchitecture: all SourcePackage: system-image UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1355760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350610] Re: Apps scope title is not the ubuntu logo
** Changed in: unity-scope-click (Ubuntu) Status: Triaged = In Progress -- 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/1350610 Title: Apps scope title is not the ubuntu logo Status in “unity-scope-click” package in Ubuntu: In Progress Bug description: It's titled Apps, but it should be the ubuntu logo according to designs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1350610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329712] Re: Lack of signal is not obvious
There is now a dedicated icon for no signal. ** Changed in: indicator-network (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1329712 Title: Lack of signal is not obvious Status in “indicator-network” package in Ubuntu: Fix Released Bug description: 1. Go somewhere you have no cellular signal, for example a tunnel or basement. 2. Look at the status bar. What you see: The same cellular signal icon as usual, just with zero bars. What you should see: Something more obvious. https://wiki.ubuntu.com/Networking#menu: * 'No signal' if there is no signal for the selected cellular network... [Originally reported by Sam Bull on ubuntu-phone@. https://lists.launchpad.net/ubuntu-phone/msg08491.html] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1329712/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1325742] Re: indicator-network crash on #61 on mako
14.04 is not supported for indicator-network. fixed in 14.10. ** Changed in: indicator-network (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1325742 Title: indicator-network crash on #61 on mako Status in “indicator-network” package in Ubuntu: Fix Released Bug description: Maybe related to bug 1325740 and/or bug 1325738 - after updating over the air on mako I get a crash of indicator-network crash file attached. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: indicator-network 0.5.1+14.10.20140526.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.3-0ubuntu1 Architecture: armhf Date: Mon Jun 2 22:05:07 2014 InstallationDate: Installed on 2014-06-02 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140602.1) SourcePackage: indicator-network UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1325742/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355773] [NEW] Home (Ubuntu) launcher has no effect when dash overview is active
Public bug reported: mako #185 TEST CASE 1: 1. From the app scope do a bottom edge swipe to open the dash overview 2. Reveal the launcher 3. Tap the Ubuntu icon Actual result Nothing happens and the dash overview is still active. Expected behaviour User is back to the app scope TEST CASE 2 1. From the app scope do a bottom edge swipe to open the dash overview 2. Tap on 'All' to show all the categories 3. Scroll down to find 'My Music' 4. Tap on the icon to open 'My Music' scope 5. Reveal the launcher 6. Tap on the Ubuntu icon Actual result Nothing happens Note that if from the app scope, the user goes to the Music/My Music scope without using the dash overview, then the 'Go home' action in the launcher behaves as expected. Expected result User is back to the app scope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140811-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Tue Aug 12 14:02:30 2014 InstallationDate: Installed on 2014-08-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140812-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: unity8 (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug armhf qa-daily-testing rtm14 utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1355773 Title: Home (Ubuntu) launcher has no effect when dash overview is active Status in “unity8” package in Ubuntu: New Bug description: mako #185 TEST CASE 1: 1. From the app scope do a bottom edge swipe to open the dash overview 2. Reveal the launcher 3. Tap the Ubuntu icon Actual result Nothing happens and the dash overview is still active. Expected behaviour User is back to the app scope TEST CASE 2 1. From the app scope do a bottom edge swipe to open the dash overview 2. Tap on 'All' to show all the categories 3. Scroll down to find 'My Music' 4. Tap on the icon to open 'My Music' scope 5. Reveal the launcher 6. Tap on the Ubuntu icon Actual result Nothing happens Note that if from the app scope, the user goes to the Music/My Music scope without using the dash overview, then the 'Go home' action in the launcher behaves as expected. Expected result User is back to the app scope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140811-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Tue Aug 12 14:02:30 2014 InstallationDate: Installed on 2014-08-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140812-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1355773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1350610] Re: Apps scope title is not the ubuntu logo
** Branch linked: lp:~stolowski/unity-scope-click/ubuntu-logo -- 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/1350610 Title: Apps scope title is not the ubuntu logo Status in “unity-scope-click” package in Ubuntu: In Progress Bug description: It's titled Apps, but it should be the ubuntu logo according to designs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1350610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355776] [NEW] WiFi shown as enabled in indicator while enabled in status bar
Public bug reported: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. ** Affects: indicator-network (Ubuntu) Importance: Undecided Status: New ** Attachment added: wifi_mako.png https://bugs.launchpad.net/bugs/1355776/+attachment/4175384/+files/wifi_mako.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1355776 Title: WiFi shown as enabled in indicator while enabled in status bar Status in “indicator-network” package in Ubuntu: New Bug description: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354755] Re: Libav security fixes Aug 2014
Problems with Libav dependencies for ubuntu precise, the files in question are 5 packets, (libavcodec53, 4:0.8.15-0ubuntu0.12.04.1), (libavdevice53, 4:0.8.15-0ubuntu0.12.04.1), (libavformat53, 4:0.8.15-0ubuntu0.12.04.1), (libpostproc52, 4:0.8.15-0ubuntu0.12.04.1), (libswscale2, 4:0.8.15-0ubuntu0.12.04.1) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1354755 Title: Libav security fixes Aug 2014 Status in “libav” package in Ubuntu: Confirmed Status in “libav” source package in Precise: Fix Released Status in “libav” source package in Trusty: In Progress Bug description: Trusty should get version 9.16: version 9.16: - vp3: Copy all 3 frames for thread updates (CVE-2011-3934) - mpegts: Do not try to write a PMT larger than SECTION_SIZE (CVE-2014-2263) - mpegts: Define the section length with a constant - error_concealment: avoid using the picture if not fully setup (CVE-2013-0860) - svq1: do not modify the input packet - cdgraphics: do not return 0 from the decode function - cdgraphics: switch to bytestream2 (CVE-2013-3674) - huffyuvdec: check width size for yuv422p (CVE-2013-0848) - mmvideo: check horizontal coordinate too (CVE-2013-3672) - wmalosslessdec: fix mclms_coeffs* array size (CVE-2014-2098) - lavc: Check the image size before calling get_buffer (CVE-2011-3935) - huffyuv: Check and propagate function return values (CVE-2013-0868) - h264: prevent theoretical infinite loop in SEI parsing (CVE-2011-3946) - h264_sei: check SEI size - pgssubdec: Check RLE size before copying (CVE-2013-0852) - fate: Add dependencies for dct/fft/mdct/rdft tests - video4linux2: Avoid a floating point exception - vf_select: Drop a debug av_log with an unchecked double to enum conversion - eamad: use the bytestream2 API instead of AV_RL (CVE-2013-0851) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1354755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354755] Re: Libav security fixes Aug 2014
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: libav (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1354755 Title: Libav security fixes Aug 2014 Status in “libav” package in Ubuntu: Confirmed Status in “libav” source package in Precise: Fix Released Status in “libav” source package in Trusty: In Progress Bug description: Trusty should get version 9.16: version 9.16: - vp3: Copy all 3 frames for thread updates (CVE-2011-3934) - mpegts: Do not try to write a PMT larger than SECTION_SIZE (CVE-2014-2263) - mpegts: Define the section length with a constant - error_concealment: avoid using the picture if not fully setup (CVE-2013-0860) - svq1: do not modify the input packet - cdgraphics: do not return 0 from the decode function - cdgraphics: switch to bytestream2 (CVE-2013-3674) - huffyuvdec: check width size for yuv422p (CVE-2013-0848) - mmvideo: check horizontal coordinate too (CVE-2013-3672) - wmalosslessdec: fix mclms_coeffs* array size (CVE-2014-2098) - lavc: Check the image size before calling get_buffer (CVE-2011-3935) - huffyuv: Check and propagate function return values (CVE-2013-0868) - h264: prevent theoretical infinite loop in SEI parsing (CVE-2011-3946) - h264_sei: check SEI size - pgssubdec: Check RLE size before copying (CVE-2013-0852) - fate: Add dependencies for dct/fft/mdct/rdft tests - video4linux2: Avoid a floating point exception - vf_select: Drop a debug av_log with an unchecked double to enum conversion - eamad: use the bytestream2 API instead of AV_RL (CVE-2013-0851) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1354755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1347147] Re: krb5 database operations enter infinite loop
Thanks Sam. I'm sorry I can't sponsor krb5, only triage the bug and
guide it through to sponsorship. It looks like you know what you're
doing here, so I guess we'll just need to wait for a sponsor to look at
it. I can see that it's in the queue and working its way up.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1347147
Title:
krb5 database operations enter infinite loop
Status in The GNU Compiler Collection:
Fix Released
Status in Network Authentication System:
Unknown
Status in “gcc-4.8” package in Ubuntu:
Fix Released
Status in “gcc-4.9” package in Ubuntu:
Fix Released
Status in “krb5” package in Ubuntu:
Fix Released
Status in “gcc-4.8” source package in Trusty:
Confirmed
Status in “krb5” source package in Trusty:
Triaged
Bug description:
[Impact]
On krb5 KDC databases with more than a few hundred principals,
operations can enter an infinite loop in the database library. This
affects both read and write operations. If operators are fortunate,
they will encounter this bug while testing a migration. If they are
not so fortunate, they will encounter this bug in a production KDC
when the number of principals crosses the threshold where this bug
manifests, resulting in a service outage and possible database
corruption. Probably the only way to restore service in that
situation is to install a patched KDC or to downgrade to an unaffected
version.
Both Trusty and Utopic amd64 have been verified to have this issue.
One concrete reported example is an invocation of kdb5_util load (as
part of a slave KDC propagation) spinning:
http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html
Additional failure modes are likely
A branch is linked including the upstream work around for this bug,
along with two other patches to bugs already nominated for trusty
applied to the krb5 in trusty.
For utopic, the simplest fix is to rebuild krb5 with the compiler
currently in utopic. An alternative is to request that the Debian
maintainers (both monitoring this bug for such a request) upload the
upstream work around to Debian and sync that. You could do an ubuntu-
specific upload but it seems undesirable to introduce a change between
Ubuntu and Debian when all the right parties are happy to avoid it.
The upstream patch works around a compiler optimizer bug in the
gcc-4.8 series, which incorrectly deduces that a strict aliasing
violation has occurred and miscompiles part of the bundled libdb2
library that the KDC database back end depends upon. The
miscompilation causes a data structure to contain an inappropriate
cycle, which leads to an infinite loop when the structure is
traversed.
[Test Case]
apt-get install krb5-kdc krb5-admin-server
kdb5_util -W -r T create -s
awk 'BEGIN{ for (i = 0; i 1024; i++) { printf(ank -randkey a%06d\n, i) }
}' /dev/null | kadmin.local -r T
(Enter any password for the master key when requested.)
On platforms with this issue, kadmin.local spins consuming 100% CPU
after a few hundred principals have been created. (This is a000762
on two examples.)
To clean up,
rm /etc/krb5kdc/principal*
or
krb5kdc -r T destroy
but the latter can possibly enter the same infinite loop.
[Regression Potential]
Negligible.
It is theoretically possible that our upstream workaround, which
involves using TAILQ macros instead of CIRCLEQ macros in the bundled
libdb2 that backs the KDC database, will have some as-yet undiscovered
bugs or compiler interactions with consequences worse than this
current issue. I think this is rather unlikely.
The patched libdb2 passes both the extensive libdb2 test suite and the
rest of the krb5 test suite. Prior to patching, compiling krb5 with
an affected gcc would cause the krb5 test suite to stall when it
reached the libdb2 test suite. (The test suite stall is how we became
aware of the gcc optimizer bug.)
The BSD TAILQ macros are generally considered to be safer than the
CIRCLEQ macros, and the various open-source BSD derivatives have made
the corresponding change to their libdb sources years ago, with no
reported ill effects that I can see.
Original report from Ben Kaduk:
==
In some conditions, propagating a kerberos database to a slave KDC server can
stall.
This is due to a misoptimization by gcc 4.8 of the CIRCLEQ famliy of macros,
apparently due to overzealous strict aliasing deductions.
One case of this stall is reported at
http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html (and
the rest of the thread), and there is an entry in the upstream
bugtracker at http://krbdev.mit.edu/rt/Ticket/Display.html?id=7860 .
gcc 4.9 (as used in Debian unstable at present) is not believed to
induce this problem. Upstream has patched their code to use the
[Touch-packages] [Bug 1353041] Re: Logging out of the Unity8 desktop preview session hangs
Marking bugs as confirmed since the associated branches *do not* fix this issue. ** Changed in: unity8 (Ubuntu) Status: Fix Released = 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/1353041 Title: Logging out of the Unity8 desktop preview session hangs Status in “unity8” package in Ubuntu: Confirmed Status in “unity8-desktop-session” package in Ubuntu: Confirmed Bug description: When logging out of a Unity8 desktop preview session, it hangs and keeps displaying the Logout dialogue but nothing else happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1353041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1299376] Re: FAAC is missing, libgstfaac.so is not present in any package
Hello, I noticed this bug when re-compiling audio-recorder for Ubuntu 14.10. Ref: http://bazaar.launchpad.net/~osmoma/audio-recorder/trunk/view/head:/src/media-profiles.c I also tried the avenc_aac from the gstreamer1.0-libav package but the recorded file content (test.aac) got bad. gst-launch-1.0 -e pulsesrc ! queue ! audioconvert ! audioresample ! avenc_aac compliance=-2 ! filesink location=test.aac It records, but file content is bad. Maybe it needs other parameters? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1299376 Title: FAAC is missing, libgstfaac.so is not present in any package Status in “gst-plugins-bad1.0” package in Ubuntu: Confirmed Bug description: When gstreamer-plugins-bad is built, libgstfaac.so is omitted from every package. I tried to build the package manually and it didn't help. The library itself is compiled and built, but it is not included in any of the resulting debian packages. In previous version of GStreamer libgstfaac.so was present in gstreamer0.10-plugins-bad-multiverse. Every software that will try to use FAAC in gstreamer 1.0 will not work. :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1299376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343556] [NEW] Signon error at startup
You have been subscribed to a public bug: 2014-07-17 15:59:29,474 - CRITICAL - ../../../../lib/SignOn/connection- manager.cpp 106 setupSocketConnection p2p error: QDBusError(org.freedesktop.DBus.Error.FileNotFound, Failed to connect to socket /run/user/32011/signond/socket: No such file or directory) 1 is shown in the log whenever system settings starts up ** Affects: signon (Ubuntu) Importance: Undecided Assignee: Alberto Mardegan (mardy) Status: Fix Committed -- Signon error at startup https://bugs.launchpad.net/bugs/1343556 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon 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 1355760] Re: mako fails to update
Time passes, and trying again it now works! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to system-image in Ubuntu. https://bugs.launchpad.net/bugs/1355760 Title: mako fails to update Status in “system-image” package in Ubuntu: New Bug description: Tried to update this morning and it failed, just hung. This was during the DC network outage we had in the UK AM. 185 is available but I can't upgrade to it. Tried rebooting. Now it's in a state where it won't update. phablet@ubuntu-phablet:~$ system-image-cli --info current build number: 184 device name: mako channel: ubuntu-touch/devel-proposed alias: ubuntu-touch/utopic-proposed last update: 2014-08-11 20:15:41 version version: 184 version ubuntu: 20140811.1 version device: 20140811.1 phablet@ubuntu-phablet:~$ system-image-cli -n phablet@ubuntu-phablet:~$ ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: system-image-cli 2.3.2-0ubuntu2 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Tue Aug 12 12:37:21 2014 InstallationDate: Installed on 2014-08-11 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140811-172006) PackageArchitecture: all SourcePackage: system-image UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/system-image/+bug/1355760/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1343556] Re: Signon error at startup
** Package changed: ubuntu-system-settings (Ubuntu) = signon (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to signon in Ubuntu. https://bugs.launchpad.net/bugs/1343556 Title: Signon error at startup Status in “signon” package in Ubuntu: Fix Committed Bug description: 2014-07-17 15:59:29,474 - CRITICAL - ../../../../lib/SignOn /connection-manager.cpp 106 setupSocketConnection p2p error: QDBusError(org.freedesktop.DBus.Error.FileNotFound, Failed to connect to socket /run/user/32011/signond/socket: No such file or directory) 1 is shown in the log whenever system settings starts up To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1343556/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354755] Re: Libav security fixes Aug 2014
At least for precise, libav-extra also needs to be updated to 0.8.15 ** Also affects: libav-extra (Ubuntu) Importance: Undecided Status: New ** Changed in: libav-extra (Ubuntu Trusty) Status: New = Invalid ** Changed in: libav-extra (Ubuntu Precise) Importance: Undecided = High ** Changed in: libav-extra (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1354755 Title: Libav security fixes Aug 2014 Status in “libav” package in Ubuntu: Fix Released Status in “libav-extra” package in Ubuntu: Invalid Status in “libav” source package in Precise: Fix Released Status in “libav-extra” source package in Precise: Confirmed Status in “libav” source package in Trusty: Fix Released Status in “libav-extra” source package in Trusty: Invalid Bug description: Trusty should get version 9.16: version 9.16: - vp3: Copy all 3 frames for thread updates (CVE-2011-3934) - mpegts: Do not try to write a PMT larger than SECTION_SIZE (CVE-2014-2263) - mpegts: Define the section length with a constant - error_concealment: avoid using the picture if not fully setup (CVE-2013-0860) - svq1: do not modify the input packet - cdgraphics: do not return 0 from the decode function - cdgraphics: switch to bytestream2 (CVE-2013-3674) - huffyuvdec: check width size for yuv422p (CVE-2013-0848) - mmvideo: check horizontal coordinate too (CVE-2013-3672) - wmalosslessdec: fix mclms_coeffs* array size (CVE-2014-2098) - lavc: Check the image size before calling get_buffer (CVE-2011-3935) - huffyuv: Check and propagate function return values (CVE-2013-0868) - h264: prevent theoretical infinite loop in SEI parsing (CVE-2011-3946) - h264_sei: check SEI size - pgssubdec: Check RLE size before copying (CVE-2013-0852) - fate: Add dependencies for dct/fft/mdct/rdft tests - video4linux2: Avoid a floating point exception - vf_select: Drop a debug av_log with an unchecked double to enum conversion - eamad: use the bytestream2 API instead of AV_RL (CVE-2013-0851) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1354755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354755] Re: Libav security fixes Aug 2014
Ah, yes, I seem to have forgotten to update libav-extra once again. I'll push out an update in a few minutes. ** Changed in: libav-extra (Ubuntu Precise) Assignee: (unassigned) = Marc Deslauriers (mdeslaur) ** Changed in: libav (Ubuntu Trusty) Status: In Progress = Fix Released ** Changed in: libav (Ubuntu) Status: Confirmed = Fix Released ** Changed in: libav-extra (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1354755 Title: Libav security fixes Aug 2014 Status in “libav” package in Ubuntu: Fix Released Status in “libav-extra” package in Ubuntu: Invalid Status in “libav” source package in Precise: Fix Released Status in “libav-extra” source package in Precise: Confirmed Status in “libav” source package in Trusty: Fix Released Status in “libav-extra” source package in Trusty: Invalid Bug description: Trusty should get version 9.16: version 9.16: - vp3: Copy all 3 frames for thread updates (CVE-2011-3934) - mpegts: Do not try to write a PMT larger than SECTION_SIZE (CVE-2014-2263) - mpegts: Define the section length with a constant - error_concealment: avoid using the picture if not fully setup (CVE-2013-0860) - svq1: do not modify the input packet - cdgraphics: do not return 0 from the decode function - cdgraphics: switch to bytestream2 (CVE-2013-3674) - huffyuvdec: check width size for yuv422p (CVE-2013-0848) - mmvideo: check horizontal coordinate too (CVE-2013-3672) - wmalosslessdec: fix mclms_coeffs* array size (CVE-2014-2098) - lavc: Check the image size before calling get_buffer (CVE-2011-3935) - huffyuv: Check and propagate function return values (CVE-2013-0868) - h264: prevent theoretical infinite loop in SEI parsing (CVE-2011-3946) - h264_sei: check SEI size - pgssubdec: Check RLE size before copying (CVE-2013-0852) - fate: Add dependencies for dct/fft/mdct/rdft tests - video4linux2: Avoid a floating point exception - vf_select: Drop a debug av_log with an unchecked double to enum conversion - eamad: use the bytestream2 API instead of AV_RL (CVE-2013-0851) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1354755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355773] Re: Home (Ubuntu) launcher has no effect when dash overview is active
*** This bug is a duplicate of bug 1355359 *** https://bugs.launchpad.net/bugs/1355359 ** This bug has been marked a duplicate of bug 1355359 Overview should close on left edge and Ubuntu button in launcher -- 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/1355773 Title: Home (Ubuntu) launcher has no effect when dash overview is active Status in “unity8” package in Ubuntu: New Bug description: mako #185 TEST CASE 1: 1. From the app scope do a bottom edge swipe to open the dash overview 2. Reveal the launcher 3. Tap the Ubuntu icon Actual result Nothing happens and the dash overview is still active. Expected behaviour User is back to the app scope TEST CASE 2 1. From the app scope do a bottom edge swipe to open the dash overview 2. Tap on 'All' to show all the categories 3. Scroll down to find 'My Music' 4. Tap on the icon to open 'My Music' scope 5. Reveal the launcher 6. Tap on the Ubuntu icon Actual result Nothing happens Note that if from the app scope, the user goes to the Music/My Music scope without using the dash overview, then the 'Go home' action in the launcher behaves as expected. Expected result User is back to the app scope ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140811-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf Date: Tue Aug 12 14:02:30 2014 InstallationDate: Installed on 2014-08-12 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140812-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1355773/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354189] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:11:QCoreApplication::notifyInternal:MInputContext::updatePreeditInternally:MInputContext::updatePreedit:MInputContext::
I think this is being caused by the unchecked use of qGuiApp-focusObject() in minputcontext.cpp:488, it looks like its possible to cause a crash by typing whilst changing focus, resulting in maliit attempting to send the event somewhere invalid. There seems to be a fair amount of unchecked uses of qGuiApp-focusObject() in minputcontext.cpp, however it looks like this was actually addressed upstream nearly a year ago: https://github.com/maliit/framework/commit/17fdf8699c53ddfb2c15df8e11d46804e782fec5 I'll see if we can get our maliit-framework package updated and hopefully that should resolve this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1354189 Title: /usr/lib/arm-linux- gnueabihf/qt5/bin/qmlscene:11:QCoreApplication::notifyInternal:MInputContext::updatePreeditInternally:MInputContext::updatePreedit:MInputContext::qt_static_metacall:QMetaObject::activate Status in “maliit-framework” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding qtdeclarative-opensource-src. This problem was most recently seen with version 5.3.0-3ubuntu8, the problem page at https://errors.ubuntu.com/problem/50ffdb4caf743ab085b5cdaa290c32dad7c24c7e contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1354189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318533] Re: provide unity-notifications-service virtual package
oh, and: 5. introduce unity-indicator-service virtual package and apply steps 1, 2, 3, 4 to it as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1318533 Title: provide unity-notifications-service virtual package Status in Network Menu: Triaged Status in The Unity 8 shell: New Status in “indicator-network” package in Ubuntu: Triaged Bug description: indicator-network 0.5.1+14.04.20140409.1-0ubuntu1, Ubuntu 14.04 1. apt-cache show indicator-network | grep Depends What happens: The result includes unity8. What should happen: The result does not include unity8. This prevents indicator-network from being used in Elementary Pantheon, for example. [Originally reported by Carlin Mangar in https://code.launchpad.net/~voldyman/indicator-network/onlyshowin- add-pantheon/+merge/215570.] To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1318533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318533] Re: Inappropriately depends on unity8
Indicator-network depends on unity8 as it's the only notification- service implementation that has all of the required extended menuitems and snap decisions. For indicator-network to be usable outside unity8, few things have to happen: 1. We need to introduce a virtual package unity-notifications-service 2. unity8 must claim to provide unity-notifications-service 3. indicator-network must depend on this virtual package 4. Pantheon must implement the extended menuitems and snap decisions and have it's notification service of choice to claim to provide unity-notifications-service Unless somebody from the community commits to 4. this will stay in the wishlist category. ** Also affects: unity8 Importance: Undecided Status: New ** Also affects: indicator-network Importance: Undecided Status: New ** Changed in: indicator-network Status: New = Triaged ** Changed in: indicator-network (Ubuntu) Status: New = Triaged ** Changed in: indicator-network Importance: Undecided = Wishlist ** Changed in: unity8 Importance: Undecided = Wishlist ** Changed in: indicator-network (Ubuntu) Importance: Undecided = Wishlist ** Summary changed: - Inappropriately depends on unity8 + add unity-notifications-service virtual package ** Summary changed: - add unity-notifications-service virtual package + provide unity-notifications-service virtual package -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1318533 Title: provide unity-notifications-service virtual package Status in Network Menu: Triaged Status in The Unity 8 shell: New Status in “indicator-network” package in Ubuntu: Triaged Bug description: indicator-network 0.5.1+14.04.20140409.1-0ubuntu1, Ubuntu 14.04 1. apt-cache show indicator-network | grep Depends What happens: The result includes unity8. What should happen: The result does not include unity8. This prevents indicator-network from being used in Elementary Pantheon, for example. [Originally reported by Carlin Mangar in https://code.launchpad.net/~voldyman/indicator-network/onlyshowin- add-pantheon/+merge/215570.] To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1318533/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268056] Re: Save/Restore state when app killed
** Branch linked: lp:ubuntu/utopic-proposed/webbrowser-app -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1268056 Title: Save/Restore state when app killed Status in The Webapps-core project: Invalid Status in Web Browser App: In Progress Status in “webbrowser-app” package in Ubuntu: In Progress Bug description: The browser should remember the previously open tabs between runs. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: webbrowser-app 0.22+14.04.20131107-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.7-0ubuntu6 Architecture: armhf Date: Sat Jan 11 01:23:48 2014 InstallationDate: Installed on 2014-01-10 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140110) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1268056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355776] Re: WiFi shown as enabled in indicator while enabled in status bar
** Changed in: indicator-network (Ubuntu) Status: New = Incomplete ** Changed in: indicator-network (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1355776 Title: WiFi shown as enabled in indicator while enabled in status bar Status in “indicator-network” package in Ubuntu: Incomplete Bug description: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
Re: [Touch-packages] [Bug 1347147] Re: krb5 database operations enter infinite loop
Robie == Robie Basak 1347...@bugs.launchpad.net writes:
Robie Thanks Sam. I'm sorry I can't sponsor krb5, only triage the
Robie bug and guide it through to sponsorship. It looks like you
Robie know what you're doing here, so I guess we'll just need to
Robie wait for a sponsor to look at it. I can see that it's in the
Robie queue and working its way up.
Actually, your reassurance that we've done the right things process wise
is really helpful.
I've been involved in Debian for over 10 years but haven't done a huge
bunch of stuff with Ubuntu so I'm mostly just reading the wikis and
trying to figure it out:-)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu.
https://bugs.launchpad.net/bugs/1347147
Title:
krb5 database operations enter infinite loop
Status in The GNU Compiler Collection:
Fix Released
Status in Network Authentication System:
Unknown
Status in “gcc-4.8” package in Ubuntu:
Fix Released
Status in “gcc-4.9” package in Ubuntu:
Fix Released
Status in “krb5” package in Ubuntu:
Fix Released
Status in “gcc-4.8” source package in Trusty:
Confirmed
Status in “krb5” source package in Trusty:
Triaged
Bug description:
[Impact]
On krb5 KDC databases with more than a few hundred principals,
operations can enter an infinite loop in the database library. This
affects both read and write operations. If operators are fortunate,
they will encounter this bug while testing a migration. If they are
not so fortunate, they will encounter this bug in a production KDC
when the number of principals crosses the threshold where this bug
manifests, resulting in a service outage and possible database
corruption. Probably the only way to restore service in that
situation is to install a patched KDC or to downgrade to an unaffected
version.
Both Trusty and Utopic amd64 have been verified to have this issue.
One concrete reported example is an invocation of kdb5_util load (as
part of a slave KDC propagation) spinning:
http://mailman.mit.edu/pipermail/kerberos/2014-July/020007.html
Additional failure modes are likely
A branch is linked including the upstream work around for this bug,
along with two other patches to bugs already nominated for trusty
applied to the krb5 in trusty.
For utopic, the simplest fix is to rebuild krb5 with the compiler
currently in utopic. An alternative is to request that the Debian
maintainers (both monitoring this bug for such a request) upload the
upstream work around to Debian and sync that. You could do an ubuntu-
specific upload but it seems undesirable to introduce a change between
Ubuntu and Debian when all the right parties are happy to avoid it.
The upstream patch works around a compiler optimizer bug in the
gcc-4.8 series, which incorrectly deduces that a strict aliasing
violation has occurred and miscompiles part of the bundled libdb2
library that the KDC database back end depends upon. The
miscompilation causes a data structure to contain an inappropriate
cycle, which leads to an infinite loop when the structure is
traversed.
[Test Case]
apt-get install krb5-kdc krb5-admin-server
kdb5_util -W -r T create -s
awk 'BEGIN{ for (i = 0; i 1024; i++) { printf(ank -randkey a%06d\n, i) }
}' /dev/null | kadmin.local -r T
(Enter any password for the master key when requested.)
On platforms with this issue, kadmin.local spins consuming 100% CPU
after a few hundred principals have been created. (This is a000762
on two examples.)
To clean up,
rm /etc/krb5kdc/principal*
or
krb5kdc -r T destroy
but the latter can possibly enter the same infinite loop.
[Regression Potential]
Negligible.
It is theoretically possible that our upstream workaround, which
involves using TAILQ macros instead of CIRCLEQ macros in the bundled
libdb2 that backs the KDC database, will have some as-yet undiscovered
bugs or compiler interactions with consequences worse than this
current issue. I think this is rather unlikely.
The patched libdb2 passes both the extensive libdb2 test suite and the
rest of the krb5 test suite. Prior to patching, compiling krb5 with
an affected gcc would cause the krb5 test suite to stall when it
reached the libdb2 test suite. (The test suite stall is how we became
aware of the gcc optimizer bug.)
The BSD TAILQ macros are generally considered to be safer than the
CIRCLEQ macros, and the various open-source BSD derivatives have made
the corresponding change to their libdb sources years ago, with no
reported ill effects that I can see.
Original report from Ben Kaduk:
==
In some conditions, propagating a kerberos database to a slave KDC server can
stall.
This is due to a misoptimization by gcc 4.8 of the CIRCLEQ famliy of macros,
apparently due to overzealous strict aliasing deductions.
One case of this
[Touch-packages] [Bug 1299376] Re: FAAC is missing, libgstfaac.so is not present in any package
Adding an avmux_* after encoder might make the pipeline work. Obrigado. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in Ubuntu. https://bugs.launchpad.net/bugs/1299376 Title: FAAC is missing, libgstfaac.so is not present in any package Status in “gst-plugins-bad1.0” package in Ubuntu: Confirmed Bug description: When gstreamer-plugins-bad is built, libgstfaac.so is omitted from every package. I tried to build the package manually and it didn't help. The library itself is compiled and built, but it is not included in any of the resulting debian packages. In previous version of GStreamer libgstfaac.so was present in gstreamer0.10-plugins-bad-multiverse. Every software that will try to use FAAC in gstreamer 1.0 will not work. :( To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1299376/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355776] Re: WiFi shown as enabled in indicator while enabled in status bar
~# dbus-send --system --print-reply --dest=org.freedesktop.URfkill /org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.GetAll string:org.freedesktop.URfkill.Killswitch method return sender=:1.2 - dest=:1.67 reply_serial=2 array [ dict entry( string state variant int32 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/1355776 Title: WiFi shown as enabled in indicator while enabled in status bar Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Incomplete Status in “urfkill” package in Ubuntu: Incomplete Bug description: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355776] Re: WiFi shown as enabled in indicator while enabled in status bar
The issue is critical, but marking it as Incomplete as far as i-network goes as we don't have enough information to decide where the actual problem is right now. Could I get the output of: dbus-send --system --print-reply --dest=org.freedesktop.URfkill /org/freedesktop/URfkill/WLAN org.freedesktop.DBus.Properties.GetAll string:org.freedesktop.URfkill.Killswitch ** Also affects: network-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: urfkill (Ubuntu) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu) Status: New = Incomplete ** Changed in: urfkill (Ubuntu) Status: New = Incomplete ** Changed in: network-manager (Ubuntu) Importance: Undecided = Critical ** Changed in: urfkill (Ubuntu) Importance: Undecided = Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1355776 Title: WiFi shown as enabled in indicator while enabled in status bar Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Incomplete Status in “urfkill” package in Ubuntu: Incomplete Bug description: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355776] Re: WiFi shown as enabled in indicator while enabled in status bar
State 0 means unblocked, so indicator-network is showing the state correctly as reported by URfkill. ** Changed in: indicator-network (Ubuntu) Status: Incomplete = Invalid -- 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/1355776 Title: WiFi shown as enabled in indicator while enabled in status bar Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Incomplete Status in “urfkill” package in Ubuntu: Incomplete Bug description: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 941826] Re: PyQt cannot compile shaders with Ubuntu's Nvidia drivers
The first entry of libGL.so in ldconfig -p points to /usr/lib/x86_64-linux-gnu/libGL.so, which is a symlink to the mesa driver. After deleting that link pyqt works fine as expected. That symlink belongs to the libgl1-mesa-dev package and seems to overrule the libGL.so entries in ldconfig for the nvidia driver. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/941826 Title: PyQt cannot compile shaders with Ubuntu's Nvidia drivers Status in NVIDIA Drivers Ubuntu: New Status in “mesa” package in Ubuntu: New Status in “nvidia-graphics-drivers-331-updates” package in Ubuntu: Confirmed Status in “pyqt5” package in Ubuntu: New Status in “python-qt4” package in Ubuntu: Confirmed Bug description: I'm having trouble with a combination of NVIDIA + Python + Qt + Opengl. I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and errors like this these: QGLShader: could not create shader Vertex shader for simpleShaderProg (MainVertexShader PositionOnlyVertexShader) failed to compile This is an example application triggering the problem: http://pastebin.com/R0aa8ejs The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact behavior when using PySide instead of PyQt4 by the way. I'm also seeing this error when trying the original demo application from python-qt4-doc. Also, calling QtGui.QApplication.setGraphicsSystem(opengl) produces the same errors. I'm experiencing this problems on 11.10 and 12.04 with the ubuntu- provided nvidia drivers (where 12.04 includes the most recent driver for now). After installing the driver using the original NVidia installer, the applications work as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355776] Re: WiFi shown as enabled in indicator while enabled in status bar
# /usr/share/urfkill/scripts/enumerate /org/freedesktop/URfkill/devices/100 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/100 Printing props for Ofono device: /org/freedesktop/URfkill/devices/100 soft: 0 name: Fake Manufacturer Fake Modem Model urftype: org.freedesktop.URfkill.Device.Ofono index: 100 type: 5 platform: 0 /org/freedesktop/URfkill/devices/0 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/0 Printing props for Kernel device: /org/freedesktop/URfkill/devices/0 soft: 0 name: phy0 urftype: org.freedesktop.URfkill.Device.Kernel index: 0 type: 1 hard: 0 platform: 1 /org/freedesktop/URfkill/devices/1 Printing props for unspecialized device: /org/freedesktop/URfkill/devices/1 Printing props for Kernel device: /org/freedesktop/URfkill/devices/1 soft: 0 name: hci0 urftype: org.freedesktop.URfkill.Device.Kernel index: 1 type: 2 hard: 0 platform: 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/1355776 Title: WiFi shown as enabled in indicator while enabled in status bar Status in “indicator-network” package in Ubuntu: Invalid Status in “network-manager” package in Ubuntu: Incomplete Status in “urfkill” package in Ubuntu: Incomplete Bug description: After disabling WiFi and rebooting, WiFi appears as enabled in indicator-network and system settings. This contradicts what is shown in the status bar (see attached screenshot). WiFi interface exists, but it is down: # ip address 22: wlan0: BROADCAST,MULTICAST mtu 1500 qdisc noop state DOWN group default qlen 100 link/ether 10:68:3f:7a:92:d5 brd ff:ff:ff:ff:ff:ff While wifi RF is not blocked: # rfkill list 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no 1: hci0: Bluetooth Soft blocked: no Hard blocked: no Which is coherent with urfkill persistent state: # cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=false ... However, saved-states was before rebooting (after disabling wifi): ~# cat /var/lib/urfkill/saved-states [ALL] soft=false [WLAN] soft=true ... Difficult to say were exactly is the error, but apparently something is powering on WiFi. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1355776/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354543] Re: mediascanner fails to watch removable devices if /media/$USER doesn't exist when starting
** Branch linked: lp:~jpakkane/mediascanner2/premountwatcher -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1354543 Title: mediascanner fails to watch removable devices if /media/$USER doesn't exist when starting Status in “mediascanner2” package in Ubuntu: Confirmed Bug description: If the system has never mounted a removable device then /media/$USER does not exist which causes mediascanner to fail it's watch with this error: Mount directory does not exist if something is mounted after this, then it just doesn't notice it. starting mediascanner after /media/$USER is created allows everything to work. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: mediascanner2.0 0.102+14.10.20140805-0ubuntu1 Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.5-0ubuntu3 Architecture: armhf Date: Fri Aug 8 14:39:22 2014 InstallationDate: Installed on 2014-08-08 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140808-020205) SourcePackage: mediascanner2 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1354543/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1353041] Re: Logging out of the Unity8 desktop preview session hangs
Since the branches associated with this bug do not fix the issue, I'm removing them to avoid confusion. ** Also affects: qtmir (Ubuntu) Importance: Undecided Status: New ** Changed in: qtmir (Ubuntu) Status: New = Confirmed ** Changed in: qtmir (Ubuntu) Assignee: (unassigned) = Gerry Boland (gerboland) ** Changed in: qtmir (Ubuntu) Importance: Undecided = High ** Changed in: unity8 (Ubuntu) Importance: Undecided = High ** Changed in: unity8-desktop-session (Ubuntu) Importance: Undecided = High ** Branch unlinked: lp:ubuntu/utopic-proposed/unity8 ** Branch unlinked: lp:ubuntu/utopic-proposed/unity8-desktop-session ** Branch unlinked: lp:~bregma/unity8-desktop-session/merge-upstart-jobs ** Branch unlinked: lp:~bregma/unity8/merge-desktop-upstart-job -- 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/1353041 Title: Logging out of the Unity8 desktop preview session hangs Status in “qtmir” package in Ubuntu: Confirmed Status in “unity8” package in Ubuntu: Confirmed Status in “unity8-desktop-session” package in Ubuntu: Confirmed Bug description: When logging out of a Unity8 desktop preview session, it hangs and keeps displaying the Logout dialogue but nothing else happens. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1353041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318192] Re: 14.04 host can not ssh to a Cisco router
*** This bug is a duplicate of bug 1287222 *** https://bugs.launchpad.net/bugs/1287222 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: openssh (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1318192 Title: 14.04 host can not ssh to a Cisco router Status in “openssh” package in Ubuntu: Confirmed Bug description: I can not connect from a freshly installed 14.04 box to a Cisco CSR1000V. 12.04 connects with no issues. Debugging this, the symptoms are identical to this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1026430 see the logs below (hostnames, addresses, and usernames below are edited). Failing attempt (the default settings): $ ssh -vvv username@router.example OpenSSH_6.6, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to router.example [2001:db8::1] port 22. debug1: Connection established. debug1: SELinux support disabled debug1: identity file /home/ubuntu/.ssh/id_rsa type -1 debug1: identity file /home/ubuntu/.ssh/id_rsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_dsa type -1 debug1: identity file /home/ubuntu/.ssh/id_dsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_ecdsa type -1 debug1: identity file /home/ubuntu/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_ed25519 type -1 debug1: identity file /home/ubuntu/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6p1 Ubuntu-2ubuntu1 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-...@openssh.com,aes256-...@openssh.com,chacha20-poly1...@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se debug2: kex_parse_kexinit: hmac-md5-...@openssh.com,hmac-sha1-...@openssh.com,umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-ripemd160-...@openssh.com,hmac-sha1-96-...@openssh.com,hmac-md5-96-...@openssh.com,hmac-md5,hmac-sha1,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5-...@openssh.com,hmac-sha1-...@openssh.com,umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-ripemd160-...@openssh.com,hmac-sha1-96-...@openssh.com,hmac-md5-96-...@openssh.com,hmac-md5,hmac-sha1,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc debug2: kex_parse_kexinit: hmac-sha1,hmac-sha1-96 debug2: kex_parse_kexinit: hmac-sha1,hmac-sha1-96 debug2: kex_parse_kexinit: none debug2: kex_parse_kexinit: none debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: setup hmac-sha1 debug1: kex: server-client aes128-ctr hmac-sha1 none debug2: mac_setup: setup hmac-sha1 debug1: kex: client-server aes128-ctr hmac-sha1 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102476808192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Connection closed by 2001:db8::1 Working attempt: $ ssh -vvv -o KexAlgorithms=diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 username@router.example OpenSSH_6.6, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to router.example [2001:db8::1] port 22. debug1: Connection established. debug1: identity file /home/ubuntu/.ssh/id_rsa type -1 debug1: identity file /home/ubuntu/.ssh/id_rsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_dsa type -1 debug1: identity file /home/ubuntu/.ssh/id_dsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_ecdsa type -1 debug1:
[Touch-packages] [Bug 1355813] [NEW] LXC containers reset bridge MTU on start/restart
Public bug reported: Context: juju + MAAS deployed OpenStack environment, misc services deployed under LXC on the bootstrap node, interfaces configured for jumbo frames - note that I had to manually set the LXC container interfaces to mtu 9000 before the bridge would do the same. Action: Reboot one of the containers; MTU on br0 resets from 9000 - 1500. This feels like more of a 'we need a better way to orchestrate MTU configuration across different services' so raising tasks for MAAS and Juju as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 13:26:00 2014 KernLog: 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: juju-core Importance: Undecided Status: New ** Affects: maas Importance: Undecided Status: New ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty uec-images ** Also affects: juju-core Importance: Undecided Status: New ** Also affects: maas Importance: Undecided Status: New ** Description changed: Context: juju + MAAS deployed OpenStack environment, misc services deployed under LXC on the bootstrap node, interfaces configured for jumbo frames - note that I had to manually set the LXC container interfaces to mtu 9000 before the bridge would do the same. Action: - Reboot on of the containers; MTU on br0 resets from 9000 - 1500. + Reboot one of the containers; MTU on br0 resets from 9000 - 1500. This feels like more of a 'we need a better way to orchestrate MTU configuration across different services' so raising tasks for MAAS and Juju as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 13:26:00 2014 KernLog: - + 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 + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: -- 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/1355813 Title: LXC containers reset bridge MTU on start/restart Status in juju-core: New Status in MAAS: New Status in “lxc” package in Ubuntu: New Bug description: Context: juju + MAAS deployed OpenStack environment, misc services deployed under LXC on the bootstrap node, interfaces configured for jumbo frames - note that I had to manually set the LXC container interfaces to mtu 9000 before the bridge would do the same. Action: Reboot one of the containers; MTU on br0 resets from 9000 - 1500. This feels like more of a 'we need a better way to orchestrate MTU configuration across different services' so raising tasks for MAAS and Juju as well. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.5-0ubuntu0.1 ProcVersionSignature: User Name 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Tue Aug 12 13:26:00 2014 KernLog: 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: To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1355813/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355388] Re: /usr/bin/telephony-service-handler:11:Tp::Contact::presence:AccountEntry::connected:TelepathyHelper::updateConnectedStatus:TelepathyHelper::onAccountManagerReady:Tel
** Changed in: telephony-service (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to telephony-service in Ubuntu. https://bugs.launchpad.net/bugs/1355388 Title: /usr/bin/telephony-service- handler:11:Tp::Contact::presence:AccountEntry::connected:TelepathyHelper::updateConnectedStatus:TelepathyHelper::onAccountManagerReady:TelepathyHelper::qt_static_metacall Status in “telephony-service” package in Ubuntu: In Progress Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding telephony-service. This problem was most recently seen with version 0.1+14.10.20140807-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/2700a4ad522dd0a1cfd06a1e2e0c569c3c9a8c3f contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/telephony-service/+bug/1355388/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1324853] Re: interface to get manifest corresponding to file in installed package
** Changed in: click (Ubuntu) Status: In Progress = Fix Committed ** Changed in: click (Ubuntu) Assignee: (unassigned) = Michael Vogt (mvo) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click in Ubuntu. https://bugs.launchpad.net/bugs/1324853 Title: interface to get manifest corresponding to file in installed package Status in “click” package in Ubuntu: Fix Committed Bug description: For reporting crashes from click packages, we need an interface to get the package manifest corresponding to a file name in a click package. Currently this requires something like running click pkgdir FILENAME and then appending .click/info/PACKAGE-NAME.manifest, which is pretty awkward (not to mention requiring decomposing the directory name from pkgdir to find the package name) and we should wrap this up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click/+bug/1324853/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1268056] Re: Save/Restore state when app killed
This bug was fixed in the package webbrowser-app - 0.23+14.10.20140812-0ubuntu1 --- webbrowser-app (0.23+14.10.20140812-0ubuntu1) utopic; urgency=low [ Olivier Tilloy ] * Save/restore browsing sessions for webbrowser-app and webapp- container. For now, only the list of currently open tabs (URLs) is persisted (current URL for the container), not the complete state for each webview. (LP: #1268056) * Fix a harmless warning that was issued when closing the last open tab. -- Ubuntu daily release ps-jenk...@lists.canonical.com Tue, 12 Aug 2014 08:26:26 + ** Changed in: webbrowser-app (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 webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1268056 Title: Save/Restore state when app killed Status in The Webapps-core project: Invalid Status in Web Browser App: In Progress Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: The browser should remember the previously open tabs between runs. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: webbrowser-app 0.22+14.04.20131107-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.7-0ubuntu6 Architecture: armhf Date: Sat Jan 11 01:23:48 2014 InstallationDate: Installed on 2014-01-10 (0 days ago) InstallationMedia: Ubuntu Trusty Tahr (development branch) - armhf (20140110) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/webapps-core/+bug/1268056/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355825] [NEW] qmlscene crashed with SIGSEGV in InverseMouseAreaType::mapEventToArea()
Public bug reported: Steps to reproducde: 1 start the ubuntu touch notes-app 2 start editing a note or add a new note 3 hit the text field with two or more fingers ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: qmlscene 5.3.0-3ubuntu8 Uname: Linux 3.4.0-6-manta armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf CrashCounter: 1 CurrentDesktop: Unity Date: Tue Aug 12 13:39:00 2014 ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene InstallationDate: Installed on 2014-08-10 (2 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140810-020204) ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ -I ./usr/lib/arm-linux-gnueabihf/qt5/qml NotesApp.qml Signal: 11 SourcePackage: qtdeclarative-opensource-src StacktraceTop: InverseMouseAreaType::mapEventToArea(QObject*, QEvent*, QPoint) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so InverseMouseAreaType::eventFilter(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 Title: qmlscene crashed with SIGSEGV in InverseMouseAreaType::mapEventToArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video ** Affects: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided Status: New ** Tags: apport-crash armhf local-libs need-armhf-retrace utopic ** Information type changed from Private to Public -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1355825 Title: qmlscene crashed with SIGSEGV in InverseMouseAreaType::mapEventToArea() Status in “qtdeclarative-opensource-src” package in Ubuntu: New Bug description: Steps to reproducde: 1 start the ubuntu touch notes-app 2 start editing a note or add a new note 3 hit the text field with two or more fingers ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: qmlscene 5.3.0-3ubuntu8 Uname: Linux 3.4.0-6-manta armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf CrashCounter: 1 CurrentDesktop: Unity Date: Tue Aug 12 13:39:00 2014 ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene InstallationDate: Installed on 2014-08-10 (2 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140810-020204) ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ -I ./usr/lib/arm-linux-gnueabihf/qt5/qml NotesApp.qml Signal: 11 SourcePackage: qtdeclarative-opensource-src StacktraceTop: InverseMouseAreaType::mapEventToArea(QObject*, QEvent*, QPoint) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so InverseMouseAreaType::eventFilter(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 Title: qmlscene crashed with SIGSEGV in InverseMouseAreaType::mapEventToArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1355825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1255097] Re: No confirmation that wi-fi hardware is turned on/off
** Changed in: indicator-network Importance: Undecided = Low ** Changed in: indicator-network (Ubuntu) Importance: Undecided = Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1255097 Title: No confirmation that wi-fi hardware is turned on/off Status in Network Menu: Confirmed Status in “indicator-network” package in Ubuntu: Confirmed Bug description: On a PC with a wi-fi or Bluetooth hotkey: 1. Turn off wi-fi or Bluetooth. 2. Turn on wi-fi or Bluetooth. What you see: 1. Nothing. 2. Nothing. What you should see: 1. Some kind of visible confirmation. 2. Some kind of visible confirmation. As described in public bug 404658, this is implemented for a Canonical OEM project in private bug 1213507, using a separate hotkey daemon. https://launchpadlibrarian.net/157232247/MOV_1319.mp4 It is probably better implemented in indicator-network, tracking actual rfkill events rather than hotkeys that might or might not be heeded. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1255097/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354189] Re: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene:11:QCoreApplication::notifyInternal:MInputContext::updatePreeditInternally:MInputContext::updatePreedit:MInputContext::
** Changed in: maliit-framework (Ubuntu) Assignee: (unassigned) = Michael Sheldon (michael-sheldon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to maliit-framework in Ubuntu. https://bugs.launchpad.net/bugs/1354189 Title: /usr/lib/arm-linux- gnueabihf/qt5/bin/qmlscene:11:QCoreApplication::notifyInternal:MInputContext::updatePreeditInternally:MInputContext::updatePreedit:MInputContext::qt_static_metacall:QMetaObject::activate Status in “maliit-framework” package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding qtdeclarative-opensource-src. This problem was most recently seen with version 5.3.0-3ubuntu8, the problem page at https://errors.ubuntu.com/problem/50ffdb4caf743ab085b5cdaa290c32dad7c24c7e contains more details. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maliit-framework/+bug/1354189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355825]
StacktraceTop: toPoint (this=0x18) at /usr/include/arm-linux-gnueabihf/qt5/QtCore/qpoint.h:391 pos (this=0x0) at /usr/include/arm-linux-gnueabihf/qt5/QtGui/qevent.h:120 InverseMouseAreaType::mapEventToArea (this=this@entry=0x10e08c8, target=optimized out, event=event@entry=0xbee1ec60, point=...) at inversemouseareatype.cpp:425 InverseMouseAreaType::eventFilter (this=0x10e08c8, object=optimized out, event=0xbee1ec60) at inversemouseareatype.cpp:442 QCoreApplicationPrivate::sendThroughObjectEventFilters (this=this@entry=0xe58fd0, receiver=receiver@entry=0x1086c68, event=event@entry=0xbee1ec60) at kernel/qcoreapplication.cpp:1031 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1355825 Title: qmlscene crashed with SIGSEGV in toPoint() Status in “qtdeclarative-opensource-src” package in Ubuntu: New Bug description: Steps to reproducde: 1 start the ubuntu touch notes-app 2 start editing a note or add a new note 3 hit the text field with two or more fingers ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: qmlscene 5.3.0-3ubuntu8 Uname: Linux 3.4.0-6-manta armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf CrashCounter: 1 CurrentDesktop: Unity Date: Tue Aug 12 13:39:00 2014 ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene InstallationDate: Installed on 2014-08-10 (2 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140810-020204) ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ -I ./usr/lib/arm-linux-gnueabihf/qt5/qml NotesApp.qml Signal: 11 SourcePackage: qtdeclarative-opensource-src StacktraceTop: InverseMouseAreaType::mapEventToArea(QObject*, QEvent*, QPoint) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so InverseMouseAreaType::eventFilter(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 Title: qmlscene crashed with SIGSEGV in InverseMouseAreaType::mapEventToArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1355825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1348236] Re: Fails to scan mp3 and consumes all the system memory when scanning
I'm starting to look at this issue and seeking within an mp3 song captured in the following bugs: https://bugs.launchpad.net/media-hub/+bug/1335345 https://bugs.launchpad.net/ubuntu/+source/media-hub/+bug/1346821 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mediascanner2 in Ubuntu. https://bugs.launchpad.net/bugs/1348236 Title: Fails to scan mp3 and consumes all the system memory when scanning Status in “mediascanner2” package in Ubuntu: Confirmed Bug description: Image 148 on mako/flo, try importing file http://people.canonical.com/~rsalveti/Existance.mp3, and you'll see mediascanner consuming most of the resources available, until killed. Probably an issue with gstreamer itself. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mediascanner2/+bug/1348236/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355830] [NEW] ListItems height breaks when put in a Loader
Public bug reported: See the attached .qml file. As soon as you put a ListItem in a Loader, its expansion breaks miserably. This prevents dynamic creation of UIs based on expandable items. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1181+14.10.20140806-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 12 15:37:08 2014 SourcePackage: ubuntu-ui-toolkit SystemImageInfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-ui-toolkit (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic ** Attachment added: testsel.qml https://bugs.launchpad.net/bugs/1355830/+attachment/4175509/+files/testsel.qml -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1355830 Title: ListItems height breaks when put in a Loader Status in “ubuntu-ui-toolkit” package in Ubuntu: New Bug description: See the attached .qml file. As soon as you put a ListItem in a Loader, its expansion breaks miserably. This prevents dynamic creation of UIs based on expandable items. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: qtdeclarative5-ubuntu-ui-toolkit-plugin 1.1.1181+14.10.20140806-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-6.11-generic 3.16.0-rc7 Uname: Linux 3.16.0-6-generic x86_64 NonfreeKernelModules: nvidia wl ApportVersion: 2.14.5-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Tue Aug 12 15:37:08 2014 SourcePackage: ubuntu-ui-toolkit SystemImageInfo: Error: [Errno 2] Nie ma takiego pliku ani katalogu: 'system-image-cli' UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1355830/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355825] Stacktrace.txt
** Attachment added: Stacktrace.txt https://bugs.launchpad.net/bugs/1355825/+attachment/4175515/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1355825 Title: qmlscene crashed with SIGSEGV in toPoint() Status in “qtdeclarative-opensource-src” package in Ubuntu: New Bug description: Steps to reproducde: 1 start the ubuntu touch notes-app 2 start editing a note or add a new note 3 hit the text field with two or more fingers ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: qmlscene 5.3.0-3ubuntu8 Uname: Linux 3.4.0-6-manta armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf CrashCounter: 1 CurrentDesktop: Unity Date: Tue Aug 12 13:39:00 2014 ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene InstallationDate: Installed on 2014-08-10 (2 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140810-020204) ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ -I ./usr/lib/arm-linux-gnueabihf/qt5/qml NotesApp.qml Signal: 11 SourcePackage: qtdeclarative-opensource-src StacktraceTop: InverseMouseAreaType::mapEventToArea(QObject*, QEvent*, QPoint) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so InverseMouseAreaType::eventFilter(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 Title: qmlscene crashed with SIGSEGV in InverseMouseAreaType::mapEventToArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1355825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1110869] Re: [indicators] [network] Duplicate SSIDs shown in menu
** Changed in: indicator-network Status: Incomplete = Fix Released ** Changed in: indicator-network (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1110869 Title: [indicators] [network] Duplicate SSIDs shown in menu Status in Network Menu: Fix Released Status in “indicator-network” package in Ubuntu: Fix Released Bug description: Some businesses and schools may configure multiple access points with the same SSID/security scheme in order to provide an environment where Wi-Fi devices can seamlessly roam from one access point to another. The network indicator should filter SSIDs so that if it finds multiple instances of an SSID with matching security scheme, it should filter out the duplicates and only show a single entry. This was tested on a Nexus10 ( manta ) running phablet-image #49. Steps to Reproduce: 1. Ensure that you have multiple access points with the same SSID/Security scheme present and active. 2. Open the network indicator Expected Result: You should only see a single menu item for the associated network Actual Result: Menu items for each instance of the SSID are shown To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1110869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355825] StacktraceSource.txt
** Attachment added: StacktraceSource.txt https://bugs.launchpad.net/bugs/1355825/+attachment/4175516/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1355825 Title: qmlscene crashed with SIGSEGV in toPoint() Status in “qtdeclarative-opensource-src” package in Ubuntu: New Bug description: Steps to reproducde: 1 start the ubuntu touch notes-app 2 start editing a note or add a new note 3 hit the text field with two or more fingers ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: qmlscene 5.3.0-3ubuntu8 Uname: Linux 3.4.0-6-manta armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf CrashCounter: 1 CurrentDesktop: Unity Date: Tue Aug 12 13:39:00 2014 ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene InstallationDate: Installed on 2014-08-10 (2 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140810-020204) ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ -I ./usr/lib/arm-linux-gnueabihf/qt5/qml NotesApp.qml Signal: 11 SourcePackage: qtdeclarative-opensource-src StacktraceTop: InverseMouseAreaType::mapEventToArea(QObject*, QEvent*, QPoint) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so InverseMouseAreaType::eventFilter(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 Title: qmlscene crashed with SIGSEGV in InverseMouseAreaType::mapEventToArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1355825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1355825] ThreadStacktrace.txt
** Attachment added: ThreadStacktrace.txt https://bugs.launchpad.net/bugs/1355825/+attachment/4175517/+files/ThreadStacktrace.txt ** Attachment removed: CoreDump.gz https://bugs.launchpad.net/bugs/1355825/+attachment/4175480/+files/CoreDump.gz ** Changed in: qtdeclarative-opensource-src (Ubuntu) Importance: Undecided = Medium ** Summary changed: - qmlscene crashed with SIGSEGV in InverseMouseAreaType::mapEventToArea() + qmlscene crashed with SIGSEGV in toPoint() ** Tags removed: need-armhf-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtdeclarative-opensource- src in Ubuntu. https://bugs.launchpad.net/bugs/1355825 Title: qmlscene crashed with SIGSEGV in toPoint() Status in “qtdeclarative-opensource-src” package in Ubuntu: New Bug description: Steps to reproducde: 1 start the ubuntu touch notes-app 2 start editing a note or add a new note 3 hit the text field with two or more fingers ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: qmlscene 5.3.0-3ubuntu8 Uname: Linux 3.4.0-6-manta armv7l ApportVersion: 2.14.5-0ubuntu4 Architecture: armhf CrashCounter: 1 CurrentDesktop: Unity Date: Tue Aug 12 13:39:00 2014 ExecutablePath: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene InstallationDate: Installed on 2014-08-10 (2 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140810-020204) ProcCmdline: /usr/lib/arm-linux-gnueabihf/qt5/bin/qmlscene $@ -I ./usr/lib/arm-linux-gnueabihf/qt5/qml NotesApp.qml Signal: 11 SourcePackage: qtdeclarative-opensource-src StacktraceTop: InverseMouseAreaType::mapEventToArea(QObject*, QEvent*, QPoint) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so InverseMouseAreaType::eventFilter(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/qt5/qml/Ubuntu/Components/libUbuntuComponents.so QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5 Title: qmlscene crashed with SIGSEGV in InverseMouseAreaType::mapEventToArea() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm autopilot cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1355825/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1354755] Re: Libav security fixes Aug 2014
OK, updated libav-extra has been published. ** Changed in: libav-extra (Ubuntu Precise) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libav in Ubuntu. https://bugs.launchpad.net/bugs/1354755 Title: Libav security fixes Aug 2014 Status in “libav” package in Ubuntu: Fix Released Status in “libav-extra” package in Ubuntu: Invalid Status in “libav” source package in Precise: Fix Released Status in “libav-extra” source package in Precise: Fix Released Status in “libav” source package in Trusty: Fix Released Status in “libav-extra” source package in Trusty: Invalid Bug description: Trusty should get version 9.16: version 9.16: - vp3: Copy all 3 frames for thread updates (CVE-2011-3934) - mpegts: Do not try to write a PMT larger than SECTION_SIZE (CVE-2014-2263) - mpegts: Define the section length with a constant - error_concealment: avoid using the picture if not fully setup (CVE-2013-0860) - svq1: do not modify the input packet - cdgraphics: do not return 0 from the decode function - cdgraphics: switch to bytestream2 (CVE-2013-3674) - huffyuvdec: check width size for yuv422p (CVE-2013-0848) - mmvideo: check horizontal coordinate too (CVE-2013-3672) - wmalosslessdec: fix mclms_coeffs* array size (CVE-2014-2098) - lavc: Check the image size before calling get_buffer (CVE-2011-3935) - huffyuv: Check and propagate function return values (CVE-2013-0868) - h264: prevent theoretical infinite loop in SEI parsing (CVE-2011-3946) - h264_sei: check SEI size - pgssubdec: Check RLE size before copying (CVE-2013-0852) - fate: Add dependencies for dct/fft/mdct/rdft tests - video4linux2: Avoid a floating point exception - vf_select: Drop a debug av_log with an unchecked double to enum conversion - eamad: use the bytestream2 API instead of AV_RL (CVE-2013-0851) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libav/+bug/1354755/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336885] Re: network signal strength always 0
** Changed in: indicator-network (Ubuntu) Assignee: (unassigned) = Antti Kaijanmäki (kaijanmaki) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1336885 Title: network signal strength always 0 Status in “indicator-network” package in Ubuntu: New Bug description: I have two sim cards here and the problem is only reproducible with one of them. Also, the problem only occurs when the indicator-network-service is launched during the boot. If I manually kill the indicator-network-service process after that, it respawns and the bug is gone. The signal strength is 61 according to ofono. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1336885/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283763] Re: Cannot connect to WPA Enterprise networks
** Changed in: indicator-network Importance: Medium = Wishlist ** Changed in: unity8 Importance: Medium = Wishlist -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1283763 Title: Cannot connect to WPA Enterprise networks Status in Network Menu: Triaged Status in The Unity 8 shell: Confirmed Status in “indicator-network” package in Ubuntu: Triaged Bug description: I cannot connect to a wireless network that uses enterprise WPA (which asks not only for a password but also for a username) on a Touch device. It seems like there is just no GUI implemented to handle that, as nothing happens when I ty to connect. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-network/+bug/1283763/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336433] Re: Network data signal does not show information about 3g or 2g
** Changed in: indicator-network (Ubuntu) Status: Incomplete = Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1336433 Title: Network data signal does not show information about 3g or 2g Status in “indicator-network” package in Ubuntu: Fix Released Bug description: Some places of my city does not have 3g signal (underground parking lot, shopping malls, country side, etc...) in these areas androids shows a different symbol/icon in the network indicator to notify the user that he is using a low quality network, but using the ubuntu phone I did not notice any change it always shows 3g icon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1336433/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
