[Touch-packages] [Bug 1123107] Re: Jockey should install the linux-$flavour metapackage
** Changed in: software-properties (Ubuntu Quantal) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1123107 Title: Jockey should install the linux-$flavour metapackage Status in “jockey” package in Ubuntu: Fix Committed Status in “software-properties” package in Ubuntu: Confirmed Status in “ubuntu-drivers-common” package in Ubuntu: Fix Released Status in “jockey” source package in Precise: Fix Released Status in “software-properties” source package in Quantal: Confirmed Status in “ubuntu-drivers-common” source package in Quantal: Won't Fix Bug description: Neither binary graphics drivers nor dkms depends on the linux-headers any longer. This means that we need Jockey to at least try to install the correct linux-$flavour metapackage so that users get the correct linux headers together with linux updates. In raring we already do this in ubuntu-drivers-common and software- properties-gtk. In precise we could build upon what we have thanks to LP: #567699 and reuse the code from u-d-c. Note: while it's true that Ubiquity already does the right thing, this bug report aims to cover cases in which, for example, the metapackages are not there any more for some reason or because users have installed a different kernel flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jockey/+bug/1123107/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1314848] Re: not possible to create connection with no IP addresses
This issue affects me as well. Setting IPv4 to Disabled, IPv6 to Ignore, and clicking Save... gives the error, "The property 'NMSettingIP6Config' / 'method' is invalid: 1". Ubuntu 14.04 (amd64) with network-manager version 0.9.8.8-0ubuntu7. Is an interface not intended to *only* receive incoming frames ? -- 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/1314848 Title: not possible to create connection with no IP addresses Status in “network-manager” package in Ubuntu: Confirmed Bug description: It does not seem to be possible to create network connections with no IP addresses., for example for passive monitoring of existing link. To reproduce: (1) In nm-connection-editor, create a new connection of type 'Ethernet'. (2) In "IPv4 settings", set Method to "Disabled" (3) In "IPv6 settings", set Method to "Ignore". (4) Hit "Save" (5) Click on newly-created connection and hit "Edit". Look at the IPv6 tab What I expected to happen: The Method is set to Ignore. What happened instead: The Method is set to Automatic. Follow up: (6) set Method to "Ignore" (7) Hit "Save". Observe error message: The property 'NMSettingIP6Config' / 'method' is invalid: 1 (8) Try to repeat same operation with kde-nm-connection-editor. This editor will silently ignore any errors which disable both connections. Other info: $ lsb_release -rd Description:Ubuntu 14.04 LTS Release:14.04 $ apt-cache policy network-manager network-manager: Installed: 0.9.8.8-0ubuntu7 Candidate: 0.9.8.8-0ubuntu7 Version table: *** 0.9.8.8-0ubuntu7 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1314848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1324580] Re: alarm will only ring for a minute and stop whether or not the user interacted with it
** Changed in: indicator-datetime (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1324580 Title: alarm will only ring for a minute and stop whether or not the user interacted with it Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu Clock App reboot series: Confirmed Status in “indicator-datetime” package in Ubuntu: In Progress Bug description: When an alarm goes off, it will ring for only a minute and after that, whether or not the user disabled it, it stays quiet forever more. It would be interesting adding a second or even third ring after the first if the alarm was not properly disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1324580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1191909] Re: gold and -flto always fails with an internal error on arm-linux-gnueabi*
This bug was fixed in the package binutils - 2.24.51.20140709-1ubuntu1
---
binutils (2.24.51.20140709-1ubuntu1) utopic; urgency=medium
* Merge with Debian, remaining changes:
- Build from upstream sources.
binutils (2.24.51.20140709-1) unstable; urgency=medium
* Snapshot, taken from the trunk 20140709.
- Fix PR gold/15639, -flto and ld.gold on ARM.
Closes: #712189. LP: #1191909.
-- Matthias KloseWed, 09 Jul 2014 20:00:32 +0200
** Changed in: binutils (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to binutils in Ubuntu.
https://bugs.launchpad.net/bugs/1191909
Title:
gold and -flto always fails with an internal error on arm-linux-
gnueabi*
Status in binutils:
Confirmed
Status in Linaro Binutils:
Fix Committed
Status in “binutils” package in Ubuntu:
Fix Released
Status in “binutils” source package in Trusty:
New
Status in “binutils” package in Debian:
Fix Released
Bug description:
seen with gcc-4.7 and binutils 2.22, and 4.8 and binutils trunk,
$ echo "int main() {return 0;}" >a.c
$ gcc -fuse-ld=gold -flto a.c
/usr/bin/ld.gold: internal error in do_read_symbols, at ../../gold/arm.cc:6735
collect2: error: ld returned 1 exit status
To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1191909/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318683] Re: I couldn't set different time zones from system settings or indicator applet complete
[Expired for indicator-datetime (Ubuntu) because there has been no activity for 60 days.] ** Changed in: indicator-datetime (Ubuntu) Status: Incomplete => Expired -- 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/1318683 Title: I couldn't set different time zones from system settings or indicator applet complete Status in “indicator-datetime” package in Ubuntu: Expired Bug description: I couldn't set different time zones from system settings or indicator applet complete I can set different locations when I add clock to my panel, but from system settings there is no clock settings. also, I couldn't set time zones (locations) on indicator applet complete! ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gnome-session-fallback 3.2.1-0ubuntu8 ProcVersionSignature: Ubuntu 3.11.0-20.35~precise1-generic 3.11.10.6 Uname: Linux 3.11.0-20-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Mon May 12 17:26:09 2014 InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1318683/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1086288] Re: Output of "date" command with Swedish locale is wrong
[Expired for coreutils (Ubuntu) because there has been no activity for 60 days.] ** Changed in: coreutils (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1086288 Title: Output of "date" command with Swedish locale is wrong Status in “coreutils” package in Ubuntu: Expired Bug description: Output of "date" command in Ubuntu 12.10: $ date tis 4 dec+ 2012 09.24.+12 CET $ echo $LC_TIME sv_SE.UTF-8 Expected output: $ date tis 4 dec 2012 09:24:12 CET To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1086288/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313968] Re: [RJ180AA-AB9 a1629.pt, Realtek ALC888, Green Line Out, Rear] fails after a while
[Expired for alsa-driver (Ubuntu) because there has been no activity for 60 days.] ** Changed in: alsa-driver (Ubuntu) Status: Incomplete => Expired -- 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/1313968 Title: [RJ180AA-AB9 a1629.pt, Realtek ALC888, Green Line Out, Rear] fails after a while Status in “alsa-driver” package in Ubuntu: Expired Bug description: Hi, sounds work for a while, then it goes off...after a while *long( it comes back...and so on...an so on... ubuntu 14.04 LTS N unable to locate package pkgname continuous sound uncontinuous sound ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: zuppaflai 1627 F pulseaudio /dev/snd/pcmC0D0p: zuppaflai 1627 F...m pulseaudio CurrentDesktop: Unity Date: Mon Apr 28 23:43:20 2014 InstallationDate: Installed on 2014-01-16 (102 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release i386 (20131016.1) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA ATI SB Symptom_Jack: Green Line Out, Rear Symptom_Type: Sound works for a while, then breaks Title: [RJ180AA-AB9 a1629.pt, Realtek ALC888, Green Line Out, Rear] fails after a while UpgradeStatus: Upgraded to trusty on 2014-04-21 (7 days ago) dmi.bios.date: 01/18/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.24 dmi.board.name: Asterope3 dmi.board.vendor: ECS dmi.board.version: 1.1 dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.24:bd01/18/2007:svnHPPavilion061:pnRJ180AA-AB9a1629.pt:pvr0ny0111RE101ASTE300:rvnECS:rnAsterope3:rvr1.1:cvnHewlett-Packard:ct3:cvr: dmi.product.name: RJ180AA-AB9 a1629.pt dmi.product.version: 0ny0111RE101ASTE300 dmi.sys.vendor: HP Pavilion 061 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1313968/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317316] Re: [HP ProBook 6560b Notebook PC] Ubuntu 14.04 intermittent screen or window freeze
[Expired for xorg (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg (Ubuntu) Status: Incomplete => Expired -- 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/1317316 Title: [HP ProBook 6560b Notebook PC] Ubuntu 14.04 intermittent screen or window freeze Status in “xorg” package in Ubuntu: Expired Bug description: Either the whole screen freezes (clock stuck, mouse/kb frozen. Requires a force reboot) or a single window freezes for 5-30 seconds while other processes continue to work. CTRL-F1 and then back to CTRL-F7 works sometimes. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8 ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl .tmp.unity.support.test.0: ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell,dbus,staticswitcher] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Wed May 7 19:58:12 2014 DistUpgraded: 2014-04-24 12:26:50,788 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bcmwl, 6.30.223.141+bdcom, 3.11.0-20-generic, x86_64: installed bcmwl, 6.30.223.141+bdcom, 3.13.0-24-generic, x86_64: installed virtualbox, 4.3.10, 3.11.0-20-generic, x86_64: installed virtualbox, 4.3.10, 3.13.0-24-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Device [103c:1619] InstallationDate: Installed on 2013-08-28 (252 days ago) InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820.1) MachineType: Hewlett-Packard HP ProBook 6560b ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=873a25ec-298a-4961-80b8-b4d44915dea4 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to trusty on 2014-04-24 (13 days ago) dmi.bios.date: 08/26/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SCE Ver. F.08 dmi.board.name: 1619 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 97.45 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCEVer.F.08:bd08/26/2011:svnHewlett-Packard:pnHPProBook6560b:pvrA0001D02:rvnHewlett-Packard:rn1619:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP ProBook 6560b dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard 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: Wed May 7 15:23:14 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: product id5537 vendor CMO xserver.version: 2:1.15.1-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1317316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1294978] Re: unity-system-compositor is frozen/hung
** Changed in: mir Status: New => Incomplete ** Changed in: unity-system-compositor Status: New => Incomplete ** Changed in: unity-system-compositor (Ubuntu) Status: New => Incomplete ** Changed in: mir Milestone: 0.5.0 => None -- 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/1294978 Title: unity-system-compositor is frozen/hung Status in Mir: Incomplete Status in Unity System Compositor: Incomplete Status in “unity-system-compositor” package in Ubuntu: Incomplete Bug description: unity-system-compositor is frozen/hung. It was running XMir just fine. And then I did: sudo mir_demo_client_egltriangle which usually works and did work for a split-second. Then the screen froze. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity-system-compositor 0.0.2+14.04.20140317.2-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-18.38-generic 3.13.6 Uname: Linux 3.13.0-18-generic x86_64 ApportVersion: 2.13.3-0ubuntu1 Architecture: amd64 Date: Thu Mar 20 14:32:18 2014 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:05a4] InstallationDate: Installed on 2013-12-21 (88 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131221) ProcEnviron: SourcePackage: unity-system-compositor UpgradeStatus: No upgrade log present (probably fresh install) version.libdrm: libdrm2 2.4.52-1 version.lightdm: lightdm 1.9.12-0ubuntu1 version.mesa: libegl1-mesa-dev 10.1.0-1ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1294978/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 879790] Re: [Lenovo Thinkpad T60] Sound doesn't play properly after upgrade from 11.04->11.10
I was one of the affected (I thought back then). I am now running 14.04 on my X1 carbon, and the sound does not have any problems. I don't recall when the problem was fixed, but it is fixed for me. -- 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/879790 Title: [Lenovo Thinkpad T60] Sound doesn't play properly after upgrade from 11.04->11.10 Status in X.org XServer - ATI gfx chipset driver: Confirmed Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: After the upgrade from Natty to Oneiric the sound that is played (by any program ex. banshee, VLC, Flash) sound very awkward, like if the whole sound is slightly gargling. My computer: Thinkpad T60 Already tried to solve the problem: The german ubuntuforum has a wiki- page to solve sound problems (http://wiki.ubuntuusers.de/Sound_Problembehebung). Unfortunately, nothing helped - even a reinstalling of the Alsa-Module didn't solve the problem. Hence I think this is a bug. Special: In the thread that I opened in the german forum (http://forum.ubuntuusers.de/topic/nach-upgrade-11-04-auf-11-10 -ueberschlaegt-der-ton/) there was another user that has the same Problem AND he has the same computer as I do. Therefore, I'm not sure if it is a computerspecific problem that may be connected with the chipset of the T60... Thanks Quesst To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-driver-ati/+bug/879790/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1335481] Re: unity-system-compositor crashed with SIGABRT - assertion failed at buffer_queue.cpp:136 - "!pending_client_notifications.empty()"
** Changed in: mir Status: New => Triaged ** Changed in: mir/0.4 Status: New => Triaged ** Package changed: unity-system-compositor (Ubuntu) => mir (Ubuntu) ** Changed in: mir (Ubuntu) Status: New => Triaged ** Also affects: unity-system-compositor (Ubuntu) Importance: Undecided Status: New ** Changed in: unity-system-compositor (Ubuntu) Status: New => Invalid -- 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/1335481 Title: unity-system-compositor crashed with SIGABRT - assertion failed at buffer_queue.cpp:136 - "!pending_client_notifications.empty()" Status in Mir: Triaged Status in Mir 0.4 series: Triaged Status in “mir” package in Ubuntu: Triaged Status in “unity-system-compositor” package in Ubuntu: Invalid Bug description: Can't say so much, opened the launched an had a crash. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity-system-compositor 0.0.4+14.10.20140625-0ubuntu1 ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 ApportVersion: 2.14.3-0ubuntu2 Architecture: amd64 BootLog: * Setting up X socket directories... [160G [154G[ OK ] * Starting automatic crash report generation: apport [160G [154G[ OK ] Date: Sat Jun 28 20:23:03 2014 ExecutablePath: /usr/sbin/unity-system-compositor GraphicsCard: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) [8086:2a02] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Device [1025:0136] Subsystem: Acer Incorporated [ALI] Device [1025:0136] InstallationDate: Installed on 2014-06-19 (9 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64+mac (20140619) ProcCmdline: /usr/sbin/unity-system-compositor --file /run/mir_socket --from-dm-fd 10 --to-dm-fd 13 --vt 7 ProcEnviron: Signal: 6 SourcePackage: unity-system-compositor SystemImageInfo: Error: [Errno 2] No such file or directory: 'system-image-cli' Title: unity-system-compositor crashed with SIGABRT in __assert_fail_base() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: version.libdrm: libdrm2 2.4.54-1 version.lightdm: lightdm 1.11.3-0ubuntu1 version.mesa: libegl1-mesa-dev N/A To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1335481/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329089] Re: g++-4.9 binary incompatibilities with libraries built with g++-4.8
** Changed in: mir/0.4 Status: New => In Progress ** Changed in: mir/0.4 Milestone: None => 0.4.2 ** Changed in: mir/0.4 Importance: Undecided => Medium ** Changed in: mir/0.4 Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1329089 Title: g++-4.9 binary incompatibilities with libraries built with g++-4.8 Status in Mir: Fix Committed Status in Mir 0.4 series: In Progress Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: Triaged Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1329089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1329089] Re: g++-4.9 binary incompatibilities with libraries built with g++-4.8
** Also affects: mir/0.4 Importance: Undecided Status: New -- 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/1329089 Title: g++-4.9 binary incompatibilities with libraries built with g++-4.8 Status in Mir: Fix Committed Status in Mir 0.4 series: New Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: Triaged Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1329089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341890] Re: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all
i reset and restarted pulse as detailed in your comment, Daniel, and the sound works again (thank you so much [as a musician, this is a big deal to me])! however, this didn't do anything for the microphone. any ideas? -- 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/1341890 Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: I've been trying to fix this myself for a while now, and just a day or two ago, the speakers stopped working, too. Neither the internal nor external speakers I've been using with my laptop have been working, with two exceptions: the bongos noise when the login screen comes up, and the tones made during a system test. I have tried the commands "alsamixer" and "gstreamer-properties" in terminal and have had success with neither of them, and have also tried using the pulse audio volume controls to no avail. My assumption is that there is an issue with the drivers, as even the microphone produced a few sporadic noises ONLY when I was playing with the mic volume controls, but at no other point in no other program has it been so responsive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio CurrentDesktop: Unity Date: Mon Jul 14 20:25:02 2014 InstallationDate: Installed on 2014-05-23 (52 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.403:bd11/26/2013:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA 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/1341890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340195] Re: Ubuntu store canned query doesn't always reflect Apps search
This bug was fixed in the package unity-scope-click - 0.1+14.10.20140714-0ubuntu1 --- unity-scope-click (0.1+14.10.20140714-0ubuntu1) utopic; urgency=medium [ Alejandro J. Cura (alecu) ] * New upstream release. - New DepartmentsDb class for storing package-department mapping. - Fix store queries started in the apps scope. (LP: #1340195) - Introduced explicit sqlite3 >= 3.8.5 runtime dependency to ensure support for recursive SQL. -- Ubuntu daily releaseMon, 14 Jul 2014 18:38:55 + ** Changed in: unity-scope-click (Ubuntu) Status: Confirmed => Fix Released -- 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/1340195 Title: Ubuntu store canned query doesn't always reflect Apps search Status in “unity-scope-click” package in Ubuntu: Fix Released Bug description: Search string carried by canned query of the orange "Ubuntu Store" item doesn't match current Apps search and instead it's the 1st search entered in Apps. Step to reproduce: 1) Go to Apps 2) Slowly type "Book" 4) Click on the orange "Ubuntu store" icon (which should say "Search for 'Book') - you should be carried to the store. 5) Reveal search box to see what was the search query - it says "B" (should be "Book"). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1340195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341262] Re: 6 core apps take you to preview when clicked, don't open in #128
This bug was fixed in the package unity8 - 7.90+14.10.20140714-0ubuntu1 --- unity8 (7.90+14.10.20140714-0ubuntu1) utopic; urgency=low [ Michał Sawicz ] * Activate all results in click scope by default. (LP: #1341262) [ Mirco Müller ] * Added support for utilization of the ComboButton SDK-element for snap-decision notifications with many actions. -- Ubuntu daily releaseMon, 14 Jul 2014 18:20:25 + ** Changed in: unity8 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1341262 Title: 6 core apps take you to preview when clicked, don't open in #128 Status in “unity8” package in Ubuntu: Fix Released Bug description: Update phone to #128 Note the new icons for the 6 core apps at the top of the click scope. see screenshot. Tap one of them, they go to a preview rather than opening. I would expect to open an app when tapping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1341262/+subscriptions -- Mailing list: https://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 1341890] [NEW] [X550LA, Realtek ALC3236, Mic, Internal] No sound at all
Yeah I'm acknowledged in the troubleshooting but sorry I'm really busy I'll keep you in mind. On Jul 14, 2014 5:40 PM, "Saman" wrote: > Public bug reported: > > I've been trying to fix this myself for a while now, and just a day or > two ago, the speakers stopped working, too. Neither the internal nor > external speakers I've been using with my laptop have been working, with > two exceptions: the bongos noise when the login screen comes up, and the > tones made during a system test. I have tried the commands "alsamixer" > and "gstreamer-properties" in terminal and have had success with neither > of them, and have also tried using the pulse audio volume controls to no > avail. My assumption is that there is an issue with the drivers, as even > the microphone produced a few sporadic noises ONLY when I was playing > with the mic volume controls, but at no other point in no other program > has it been so responsive. > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu4 > ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 > Uname: Linux 3.13.0-30-generic x86_64 > ApportVersion: 2.14.1-0ubuntu3.2 > Architecture: amd64 > AudioDevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC1: jake 1815 F pulseaudio > /dev/snd/controlC0: jake 1815 F pulseaudio > /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio > CurrentDesktop: Unity > Date: Mon Jul 14 20:25:02 2014 > InstallationDate: Installed on 2014-05-23 (52 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 > (20140417) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed > Symptom_Card: Built-in Audio - HDA Intel PCH > Symptom_DevicesInUse: > USERPID ACCESS COMMAND > /dev/snd/controlC1: jake 1815 F pulseaudio > /dev/snd/controlC0: jake 1815 F pulseaudio > /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio > Symptom_Jack: Mic, Internal > Symptom_Type: No sound at all > Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all > UpgradeStatus: No upgrade log present (probably fresh install) > dmi.bios.date: 11/26/2013 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: X550LA.403 > dmi.board.asset.tag: ATN12345678901234567 > dmi.board.name: X550LA > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: 1.0 > dmi.chassis.asset.tag: ATN12345678901234567 > dmi.chassis.type: 10 > dmi.chassis.vendor: ASUSTeK COMPUTER INC. > dmi.chassis.version: 1.0 > dmi.modalias: > dmi:bvnAmericanMegatrendsInc.:bvrX550LA.403:bd11/26/2013:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: > dmi.product.name: X550LA > dmi.product.version: 1.0 > dmi.sys.vendor: ASUSTeK COMPUTER INC. > > ** Affects: alsa-driver (Ubuntu) > Importance: Undecided > Status: New > > > ** Tags: amd64 apport-bug trusty > > -- > You received this bug notification because you are a member of Ubuntu > Audio Team, which is subscribed to alsa-driver in Ubuntu. > https://bugs.launchpad.net/bugs/1341890 > > Title: > [X550LA, Realtek ALC3236, Mic, Internal] No sound at all > > Status in “alsa-driver” package in Ubuntu: > New > > Bug description: > I've been trying to fix this myself for a while now, and just a day or > two ago, the speakers stopped working, too. Neither the internal nor > external speakers I've been using with my laptop have been working, > with two exceptions: the bongos noise when the login screen comes up, > and the tones made during a system test. I have tried the commands > "alsamixer" and "gstreamer-properties" in terminal and have had > success with neither of them, and have also tried using the pulse > audio volume controls to no avail. My assumption is that there is an > issue with the drivers, as even the microphone produced a few sporadic > noises ONLY when I was playing with the mic volume controls, but at no > other point in no other program has it been so responsive. > > ProblemType: Bug > DistroRelease: Ubuntu 14.04 > Package: alsa-base 1.0.25+dfsg-0ubuntu4 > ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 > Uname: Linux 3.13.0-30-generic x86_64 > ApportVersion: 2.14.1-0ubuntu3.2 > Architecture: amd64 > AudioDevicesInUse: >USERPID ACCESS COMMAND >/dev/snd/controlC1: jake 1815 F pulseaudio >/dev/snd/controlC0: jake 1815 F pulseaudio >/dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio > CurrentDesktop: Unity > Date: Mon Jul 14 20:25:02 2014 > InstallationDate: Installed on 2014-05-23 (52 days ago) > InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 > (20140417) > PackageArchitecture: all > SourcePackage: alsa-driver > Symptom: audio > Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed > Sympto
[Touch-packages] [Bug 1339700] Re: [regression] Device locks randomly on welcome screen
Yeah image 119 only has Mir 0.4.0 so doesn't have the fix for this yet. Wait a day or so I guess and the mir packages upgrade to 0.4.1. -- 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/1339700 Title: [regression] Device locks randomly on welcome screen Status in Mir: Fix Committed Status in Mir 0.4 series: Fix Released Status in “mir” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Invalid Bug description: Unity8 welcome screen will occasionally lock. Lock effects: No launcher available Can't swipe left or right Can't drag down indicators Doesn't recover from tapping the power button a couple of times. Randomness: Locks so far have been happening on and off from image U114 The phone seems to lock up for me more on waking from suspend, however rsalveti pointed out that for him it happened on phone hang up. For me the lock happened a couple of times over the weekend images U114 and U115, and then not again till today U122. Manta seems more prone to lock ups that flo or mako. STEPS: (It seems flo has an issue identical when opening settings app) On flo update to U123 1. Once updated, open the settings app This seems to land you in the state described. Apparently this is only a temporary version if you leave the device for a while it will unlock. But I think that is possibly because you are moved away from the app and it is unlocked by the system waking from suspend possibly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.90+14.10.20140707-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu1 Architecture: armhf Date: Wed Jul 9 13:48:14 2014 InstallationDate: Installed on 2014-07-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140709-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1339700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1275398] Re: i915 driver/i945 hardware: Mir GL clients are rendered as black or transparent windows when using i945 graphics
** Summary changed: - i945: Mir GL clients are rendered as black or transparent windows when using i945 graphics + i915 driver/i945 hardware: Mir GL clients are rendered as black or transparent windows when using i945 graphics -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1275398 Title: i915 driver/i945 hardware: Mir GL clients are rendered as black or transparent windows when using i945 graphics Status in Mir: Triaged Status in “linux” package in Ubuntu: Incomplete Status in “mesa” package in Ubuntu: Confirmed Bug description: Running Mir on a Pentium D system with integrated i945 graphics, appears to work at first. The server starts and software clients are rendered correctly. However hardware (GL) clients are rendered as all black or transparent windows, despite logging to stdout that they think they are rendering: $ sudo bin/mir_demo_client_egltriangle Current active output is 1920x1200 +0+0 Server supports 2 of 6 surface pixel formats. Using format: 4 libEGL warning: unsupported platform (null) 1 FPS 33 FPS 60 FPS 60 FPS 60 FPS 60 FPS To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1275398/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1324580] Re: alarm will only ring for a minute and stop whether or not the user interacted with it
** Branch linked: lp:~charlesk/indicator-datetime/lp-1324580-set-snap- decision-timeout -- 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/1324580 Title: alarm will only ring for a minute and stop whether or not the user interacted with it Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu Clock App reboot series: Confirmed Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: When an alarm goes off, it will ring for only a minute and after that, whether or not the user disabled it, it stays quiet forever more. It would be interesting adding a second or even third ring after the first if the alarm was not properly disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1324580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341262] Re: 6 core apps take you to preview when clicked, don't open in #128
** Branch linked: lp:ubuntu/utopic-proposed/unity8 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1341262 Title: 6 core apps take you to preview when clicked, don't open in #128 Status in “unity8” package in Ubuntu: In Progress Bug description: Update phone to #128 Note the new icons for the 6 core apps at the top of the click scope. see screenshot. Tap one of them, they go to a preview rather than opening. I would expect to open an app when tapping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1341262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340195] Re: Ubuntu store canned query doesn't always reflect Apps search
** Branch linked: lp:ubuntu/utopic-proposed/unity-scope-click -- 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/1340195 Title: Ubuntu store canned query doesn't always reflect Apps search Status in “unity-scope-click” package in Ubuntu: Confirmed Bug description: Search string carried by canned query of the orange "Ubuntu Store" item doesn't match current Apps search and instead it's the 1st search entered in Apps. Step to reproduce: 1) Go to Apps 2) Slowly type "Book" 4) Click on the orange "Ubuntu store" icon (which should say "Search for 'Book') - you should be carried to the store. 5) Reveal search box to see what was the search query - it says "B" (should be "Book"). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-scope-click/+bug/1340195/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336642] Re: Add support for tumblr in friends
Apparently the Friends project is going to be deprecated. ** Changed in: friends (Ubuntu) Status: Confirmed => Won't Fix ** No longer affects: friends -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to friends in Ubuntu. https://bugs.launchpad.net/bugs/1336642 Title: Add support for tumblr in friends Status in “friends” package in Ubuntu: Won't Fix Bug description: Friends now have support for quite a few new social networks like Instagram, Foursquare. It would be great to have tumblr too. Tumblr is originally considered as micro blogging platform & api can be found here: http://www.tumblr.com/docs/en/api/v2 And there is a python library on github: https://github.com/tumblr/pytumblr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/friends/+bug/1336642/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341890] Re: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all
So you had sound before a few days ago? It looks like a pulseaudio issue (no analog output profile). Try resetting the user config and restarting pulse: rm -r ~/.config/pulse* pulseaudio -k -- 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/1341890 Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: I've been trying to fix this myself for a while now, and just a day or two ago, the speakers stopped working, too. Neither the internal nor external speakers I've been using with my laptop have been working, with two exceptions: the bongos noise when the login screen comes up, and the tones made during a system test. I have tried the commands "alsamixer" and "gstreamer-properties" in terminal and have had success with neither of them, and have also tried using the pulse audio volume controls to no avail. My assumption is that there is an issue with the drivers, as even the microphone produced a few sporadic noises ONLY when I was playing with the mic volume controls, but at no other point in no other program has it been so responsive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio CurrentDesktop: Unity Date: Mon Jul 14 20:25:02 2014 InstallationDate: Installed on 2014-05-23 (52 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.403:bd11/26/2013:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA 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/1341890/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341898] Re: [MS-7920, Realtek ALC1150, Red Line Out, Rear] Underruns, dropouts or crackling sound
Probably duplicate of: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1321421 Try workaround command and mark duplicate if it works. echo "options snd-hda-intel vid=8086 pid=8ca0 snoop=0" | sudo tee /etc/modprobe.d/fix-sound-intel97.conf ** Changed in: alsa-driver (Ubuntu) Status: New => Incomplete -- 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/1341898 Title: [MS-7920, Realtek ALC1150, Red Line Out, Rear] Underruns, dropouts or crackling sound Status in “alsa-driver” package in Ubuntu: Incomplete Bug description: Sound appears to have trouble buffering at times playing too fast or slow and glitching like a bad mp3. Posts here have not resolved the issue: http://askubuntu.com/questions/464877/ubuntu-14-04-sound-glitch https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1019693 - Not 100% it's the same issue http://askubuntu.com/questions/157554/choppy-stuttery-sped-up-sound- after-update ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nandemonai 2849 F pulseaudio /dev/snd/controlC2: nandemonai 2849 F pulseaudio /dev/snd/controlC0: nandemonai 2849 F pulseaudio CurrentDesktop: GNOME Date: Tue Jul 15 10:30:01 2014 InstallationDate: Installed on 2014-07-05 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Red Line Out, Rear Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [MS-7920, Realtek ALC1150, Red Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97I GAMING AC (MS-7920) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/22/2014:svnMSI:pnMS-7920:pvr1.0:rvnMSI:rnZ97IGAMINGAC(MS-7920):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7920 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1318997] Re: Provide a way to change alarm sound
** Changed in: indicator-datetime Status: Fix Committed => Fix Released -- 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/1318997 Title: Provide a way to change alarm sound Status in The Date and Time Indicator: Fix Released Status in Clock application for Ubuntu devices: New Status in Ubuntu Clock App reboot series: In Progress Status in Ubuntu UX bugs: New Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: The alarms API provides to way to set different alarm sounds for every alarm. Let's provide that feature to the users so that they can change the alarm sound while creating an alarm. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-datetime/+bug/1318997/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341898] [NEW] [MS-7920, Realtek ALC1150, Red Line Out, Rear] Underruns, dropouts or crackling sound
Public bug reported: Sound appears to have trouble buffering at times playing too fast or slow and glitching like a bad mp3. Posts here have not resolved the issue: http://askubuntu.com/questions/464877/ubuntu-14-04-sound-glitch https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1019693 - Not 100% it's the same issue http://askubuntu.com/questions/157554/choppy-stuttery-sped-up-sound- after-update ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nandemonai 2849 F pulseaudio /dev/snd/controlC2: nandemonai 2849 F pulseaudio /dev/snd/controlC0: nandemonai 2849 F pulseaudio CurrentDesktop: GNOME Date: Tue Jul 15 10:30:01 2014 InstallationDate: Installed on 2014-07-05 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Red Line Out, Rear Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [MS-7920, Realtek ALC1150, Red Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97I GAMING AC (MS-7920) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/22/2014:svnMSI:pnMS-7920:pvr1.0:rvnMSI:rnZ97IGAMINGAC(MS-7920):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7920 dmi.product.version: 1.0 dmi.sys.vendor: MSI ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1341898 Title: [MS-7920, Realtek ALC1150, Red Line Out, Rear] Underruns, dropouts or crackling sound Status in “alsa-driver” package in Ubuntu: New Bug description: Sound appears to have trouble buffering at times playing too fast or slow and glitching like a bad mp3. Posts here have not resolved the issue: http://askubuntu.com/questions/464877/ubuntu-14-04-sound-glitch https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1019693 - Not 100% it's the same issue http://askubuntu.com/questions/157554/choppy-stuttery-sped-up-sound- after-update ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nandemonai 2849 F pulseaudio /dev/snd/controlC2: nandemonai 2849 F pulseaudio /dev/snd/controlC0: nandemonai 2849 F pulseaudio CurrentDesktop: GNOME Date: Tue Jul 15 10:30:01 2014 InstallationDate: Installed on 2014-07-05 (9 days ago) InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed Symptom_Card: Built-in Audio - HDA Intel Symptom_Jack: Red Line Out, Rear Symptom_Type: Underruns, dropouts, or "crackling" sound Title: [MS-7920, Realtek ALC1150, Red Line Out, Rear] Underruns, dropouts or crackling sound UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/22/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V1.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97I GAMING AC (MS-7920) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.0:bd04/22/2014:svnMSI:pnMS-7920:pvr1.0:rvnMSI:rnZ97IGAMINGAC(MS-7920):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7920 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341898/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.l
[Touch-packages] [Bug 1341890] [NEW] [X550LA, Realtek ALC3236, Mic, Internal] No sound at all
Public bug reported: I've been trying to fix this myself for a while now, and just a day or two ago, the speakers stopped working, too. Neither the internal nor external speakers I've been using with my laptop have been working, with two exceptions: the bongos noise when the login screen comes up, and the tones made during a system test. I have tried the commands "alsamixer" and "gstreamer-properties" in terminal and have had success with neither of them, and have also tried using the pulse audio volume controls to no avail. My assumption is that there is an issue with the drivers, as even the microphone produced a few sporadic noises ONLY when I was playing with the mic volume controls, but at no other point in no other program has it been so responsive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio CurrentDesktop: Unity Date: Mon Jul 14 20:25:02 2014 InstallationDate: Installed on 2014-05-23 (52 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.403 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.403:bd11/26/2013:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1341890 Title: [X550LA, Realtek ALC3236, Mic, Internal] No sound at all Status in “alsa-driver” package in Ubuntu: New Bug description: I've been trying to fix this myself for a while now, and just a day or two ago, the speakers stopped working, too. Neither the internal nor external speakers I've been using with my laptop have been working, with two exceptions: the bongos noise when the login screen comes up, and the tones made during a system test. I have tried the commands "alsamixer" and "gstreamer-properties" in terminal and have had success with neither of them, and have also tried using the pulse audio volume controls to no avail. My assumption is that there is an issue with the drivers, as even the microphone produced a few sporadic noises ONLY when I was playing with the mic volume controls, but at no other point in no other program has it been so responsive. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio CurrentDesktop: Unity Date: Mon Jul 14 20:25:02 2014 InstallationDate: Installed on 2014-05-23 (52 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jake 1815 F pulseaudio /dev/snd/controlC0: jake 1815 F pulseaudio /dev/snd/pcmC0D3p: jake 1815 F...m pulseaudio Symptom_Jack: Mic, Internal Symptom_Type: No sound at all Title: [X55
[Touch-packages] [Bug 1317869] Re: Keyboard shortcuts overlay does not show up when workspaces are enabled at 1366x768
** Description changed: + [Impact] + The shortcut hint is not shown when workspaces are enabled in displays with 1366x768 resolution. + + [Test case] + 1. Run unity in a monitor with 1366x768 resolution. + 2. From Unity Control Center -> Appearance -> Behavior -> enable the workspaces + 3. Hold Super and keep it pressed, the shortcut should show up + + [Regression potential] + The potential of regression is basically none, we just resized the view to make sure there's enough space for showing in smaller resolutions. + + + My notebook has a 1366x768 screen - it is a very common screen resolution. When I boot Ubuntu 14.04 liveISO the keyboard shortcuts overlay is displayed and works very well - therefore my screen resolution is large enough for it. But after I installed 14.04 on my hard disk, the shortcuts overlay does not show anymore. The attachment is a screenshot of the shortcuts overlay working on the liveISO. -- 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/1317869 Title: Keyboard shortcuts overlay does not show up when workspaces are enabled at 1366x768 Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] The shortcut hint is not shown when workspaces are enabled in displays with 1366x768 resolution. [Test case] 1. Run unity in a monitor with 1366x768 resolution. 2. From Unity Control Center -> Appearance -> Behavior -> enable the workspaces 3. Hold Super and keep it pressed, the shortcut should show up [Regression potential] The potential of regression is basically none, we just resized the view to make sure there's enough space for showing in smaller resolutions. My notebook has a 1366x768 screen - it is a very common screen resolution. When I boot Ubuntu 14.04 liveISO the keyboard shortcuts overlay is displayed and works very well - therefore my screen resolution is large enough for it. But after I installed 14.04 on my hard disk, the shortcuts overlay does not show anymore. The attachment is a screenshot of the shortcuts overlay working on the liveISO. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317348] Re: Switcher (Alt-Tab) does not respect monitor-defined scaling factor
** Description changed: [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. [Test case] 1. From Unity Control Center -> Displays -> Change the monitor scaling to somewhat -different from 1.0 (might be both bigger and smaller, your choice). + different from 1.0 (might be both bigger and smaller, your choice). 2. Open some windows and press Alt+Tab 3. Both Switcher icons, application names and spreaded windows (when pressing down, or -right-clicking on an icon) decorations should be scaled to match the selected -scaling factor. + right-clicking on an icon) decorations should be scaled to match the selected + scaling factor. +In Multi-monitor scenario it should match the scaling factor of the monitor where the +view opens (so where the mouse is). - [Regression potential] - The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. + [Regression potential]The potential of regression is basically none, + since we just moved from fixed sizes to relative sizes and unless the + scale value is set to an invalid value, this should work as it happens + in other unity views that do support scaling currently. -- 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/1317348 Title: Switcher (Alt-Tab) does not respect monitor-defined scaling factor Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. [Test case] 1. From Unity Control Center -> Displays -> Change the monitor scaling to somewhat different from 1.0 (might be both bigger and smaller, your choice). 2. Open some windows and press Alt+Tab 3. Both Switcher icons, application names and spreaded windows (when pressing down, or right-clicking on an icon) decorations should be scaled to match the selected scaling factor. In Multi-monitor scenario it should match the scaling factor of the monitor where the view opens (so where the mouse is). [Regression potential]The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317356] Re: Shortcut hint does not respect monitor scaling factor
** Description changed: + [Impact] The shortcut hint is not properly scaled in HiDPI monitors + + [Test case] + 1. From Unity Control Center -> Displays -> Change the monitor scaling to somewhat +different from 1.0 (might be both bigger and smaller, your choice; but scaling down is +recommended if your monitor has a small resolution or next point will fail). + 2. Hold Super and keep it pressed unless the shortcut hint won't show up +(note: this might not happen if the monitor resolution is not big enough to contain +all the shortcuts; see point above) + 3. The shortcuts view and all its text should be scaled to match the defined monitor +scaling factor. +In Multi-monitor scenario it should match the scaling factor of the monitor where the +view opens (so where the mouse is). + + + [Regression potential]The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. ** Description changed: [Impact] The shortcut hint is not properly scaled in HiDPI monitors [Test case] 1. From Unity Control Center -> Displays -> Change the monitor scaling to somewhat -different from 1.0 (might be both bigger and smaller, your choice; but scaling down is -recommended if your monitor has a small resolution or next point will fail). + different from 1.0 (might be both bigger and smaller, your choice; but scaling down is + recommended if your monitor has a small resolution or next point will fail). 2. Hold Super and keep it pressed unless the shortcut hint won't show up -(note: this might not happen if the monitor resolution is not big enough to contain -all the shortcuts; see point above) + (note: this might not happen if the monitor resolution is not big enough to contain + all the shortcuts; see point above) 3. The shortcuts view and all its text should be scaled to match the defined monitor -scaling factor. -In Multi-monitor scenario it should match the scaling factor of the monitor where the -view opens (so where the mouse is). + scaling factor. + In Multi-monitor scenario it should match the scaling factor of the monitor where the + view opens (so where the mouse is). - - [Regression potential]The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. + [Regression potential] + The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. -- 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/1317356 Title: Shortcut hint does not respect monitor scaling factor Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] The shortcut hint is not properly scaled in HiDPI monitors [Test case] 1. From Unity Control Center -> Displays -> Change the monitor scaling to somewhat different from 1.0 (might be both bigger and smaller, your choice; but scaling down is recommended if your monitor has a small resolution or next point will fail). 2. Hold Super and keep it pressed unless the shortcut hint won't show up (note: this might not happen if the monitor resolution is not big enough to contain all the shortcuts; see point above) 3. The shortcuts view and all its text should be scaled to match the defined monitor scaling factor. In Multi-monitor scenario it should match the scaling factor of the monitor where the view opens (so where the mouse is). [Regression potential] The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317348] Re: Switcher (Alt-Tab) does not respect monitor-defined scaling factor
** Description changed: + [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. + + [Test case] + 1. From Unity Control Center -> Displays -> Change the monitor scaling to somewhat +different from 1.0 (might be both bigger and smaller, your choice). + 2. Open some windows and press Alt+Tab + 3. Both Switcher icons, application names and spreaded windows (when pressing down, or +right-clicking on an icon) decorations should be scaled to match the selected +scaling factor. + + [Regression potential] + The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. -- 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/1317348 Title: Switcher (Alt-Tab) does not respect monitor-defined scaling factor Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. [Test case] 1. From Unity Control Center -> Displays -> Change the monitor scaling to somewhat different from 1.0 (might be both bigger and smaller, your choice). 2. Open some windows and press Alt+Tab 3. Both Switcher icons, application names and spreaded windows (when pressing down, or right-clicking on an icon) decorations should be scaled to match the selected scaling factor. In Multi-monitor scenario it should match the scaling factor of the monitor where the view opens (so where the mouse is). [Regression potential]The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 924840] Re: Keyboard shortcuts overlay text too long
** Description changed: + [Inpact] + The shortcut overlay window listes some truncated keybindings and descriptions although there's enough horizontal space to show them all. + + [Test case] + The test case for this bug depends a lot on the locale used and thus there's not an universal way to verify it, this is generally valid for English locale but should apply to others as well: + + 1. In Unity Control Center -> Appearance -> Behavior enable the workspaces + 2. Hold down the super key unless the shortcut overlay window is not show (if it's +supported, minimum resolution is 1366x768) + 3. Both the keybindings and the descriptions should not be ellipsised if there's enough +horizontal space to present them, for example the "Super + Alt + Cursor ke.." +keybinding should be instead "Super + Alt + Cursor keys" + + [Regression potential] + The view might be too large in some locales and thus not to show at all, although we should generally handle this as it used to be before. + + -- + When I hold down Super I get a popup image detailing the shortcut keys. There are a few issues with this image which I have filed as separate bugs. Workspaces Text too long to fit. I see "Super + Alt + Cursor ke.." Which I presume should say "Cursor keys" -- 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/924840 Title: Keyboard shortcuts overlay text too long Status in Ayatana Design: New Status in Ubuntu Translations: New Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Inpact] The shortcut overlay window listes some truncated keybindings and descriptions although there's enough horizontal space to show them all. [Test case] The test case for this bug depends a lot on the locale used and thus there's not an universal way to verify it, this is generally valid for English locale but should apply to others as well: 1. In Unity Control Center -> Appearance -> Behavior enable the workspaces 2. Hold down the super key unless the shortcut overlay window is not show (if it's supported, minimum resolution is 1366x768) 3. Both the keybindings and the descriptions should not be ellipsised if there's enough horizontal space to present them, for example the "Super + Alt + Cursor ke.." keybinding should be instead "Super + Alt + Cursor keys" [Regression potential] The view might be too large in some locales and thus not to show at all, although we should generally handle this as it used to be before. -- When I hold down Super I get a popup image detailing the shortcut keys. There are a few issues with this image which I have filed as separate bugs. Workspaces Text too long to fit. I see "Super + Alt + Cursor ke.." Which I presume should say "Cursor keys" To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/924840/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317348] Re: Switcher (Alt-Tab) does not respect monitor-defined scaling factor
** Changed in: unity (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1317348 Title: Switcher (Alt-Tab) does not respect monitor-defined scaling factor Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] Unity switcher doesn't get properly scaled on HiDPI monitors. [Test case] 1. From Unity Control Center -> Displays -> Change the monitor scaling to somewhat different from 1.0 (might be both bigger and smaller, your choice). 2. Open some windows and press Alt+Tab 3. Both Switcher icons, application names and spreaded windows (when pressing down, or right-clicking on an icon) decorations should be scaled to match the selected scaling factor. [Regression potential] The potential of regression is basically none, since we just moved from fixed sizes to relative sizes and unless the scale value is set to an invalid value, this should work as it happens in other unity views that do support scaling currently. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317348/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 839728] Re: Launcher - dragging a item on top of a launcher tile that is a valid drop receptacle in the Launcher should cause that launcher tile to glow
** Description changed: + [Impact] + The drag and drop launcher icons are not correctly marked as targets + + [Test case] + 1) Drag a file a launcher icon + 2) The launcher icon under the mouse pointer should have a glowing tile + + 3) When the mouse pointer leaves the launcher icon area or the mouse is released +the icon should not glow anymore (unless is not an urgent icon). + + + [Regression Potential] + An icon that is not urgent might be left with a glowing tile when leaving the DnD or an urgent icon might not being glowing anymore after leaving the Dnd. + + + - + Launcher - dragging a item on top of a launcher tile that is a valid drop receptacle in the Launcher should cause that launcher tile to glow. This glow only persists as long as the dragged item is directly over the launcher tile, as soon as the dragged item is moved off the launcher tile, the glow should stop. Use cases: - User drags a .png file over the Firefox icon in the Launcher. As soon as the .png file is over the Firefox icon, the firefox icon starts to glow. The user then moves the .png file off the Firefox launcher icon, and the Firefox launcher immediately stops glowing. - User drags a launcher tile from it's position in the launcher to the trash can. As soon as the Launcher tile is above the trash can, the trash can starts to glow. The user then moves the launcher tile off the trash can and the trash can stops glowing. -- 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/839728 Title: Launcher - dragging a item on top of a launcher tile that is a valid drop receptacle in the Launcher should cause that launcher tile to glow Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] The drag and drop launcher icons are not correctly marked as targets [Test case] 1) Drag a file a launcher icon 2) The launcher icon under the mouse pointer should have a glowing tile 3) When the mouse pointer leaves the launcher icon area or the mouse is released the icon should not glow anymore (unless is not an urgent icon). [Regression Potential] An icon that is not urgent might be left with a glowing tile when leaving the DnD or an urgent icon might not being glowing anymore after leaving the Dnd. - Launcher - dragging a item on top of a launcher tile that is a valid drop receptacle in the Launcher should cause that launcher tile to glow. This glow only persists as long as the dragged item is directly over the launcher tile, as soon as the dragged item is moved off the launcher tile, the glow should stop. Use cases: - User drags a .png file over the Firefox icon in the Launcher. As soon as the .png file is over the Firefox icon, the firefox icon starts to glow. The user then moves the .png file off the Firefox launcher icon, and the Firefox launcher immediately stops glowing. - User drags a launcher tile from it's position in the launcher to the trash can. As soon as the Launcher tile is above the trash can, the trash can starts to glow. The user then moves the launcher tile off the trash can and the trash can stops glowing. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/839728/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 727902] Re: Launcher icon highlighting should not switch off as soon the cursor moves after the app spread appears.
** Description changed: + [Impact] + When dragging a file to an application with multiple windows open and the spread is triggered, any movement of the mouse switches off the selective highlighting and dimming of valid/non-valid drop receptacles. + + [Test Case] + 1) Open two windows instances of the same application (say firefox) + 2) Drag a file from the file-manager or the desktop and hover the firefox icon + 3) After one second the firefox icon is hovered, the spread will occur + 4) Dragging the icon outside the launcher and in the spread area (both over a window or +not) should keep the desaturated icons as they were before. + + [Regression Potential] + Launcher icon might be not saturated again when exiting from spread. + + -- + Description. When a file is dragged and held over a application icon in the Launcher a spread of the app windows appear. The user can then drag and drop the file on to one of the windows to specify the window in which they would like the file to be loaded. The bug is that after the spread appears, any movement of the mouse switches off the selective highlighting and dimming of valid/non-valid drop receptacles. Desired behaviour - The highlighting and dimming of Launcher icons should persist until the user drops the file. - Note that the 'spread when a item is held over a launcher icon' behaviour seems to be broken in the Oneiric final freeze release (nothing happens). -- 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/727902 Title: Launcher icon highlighting should not switch off as soon the cursor moves after the app spread appears. Status in Ayatana Design: Fix Committed Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] When dragging a file to an application with multiple windows open and the spread is triggered, any movement of the mouse switches off the selective highlighting and dimming of valid/non-valid drop receptacles. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) Dragging the icon outside the launcher and in the spread area (both over a window or not) should keep the desaturated icons as they were before. [Regression Potential] Launcher icon might be not saturated again when exiting from spread. -- Description. When a file is dragged and held over a application icon in the Launcher a spread of the app windows appear. The user can then drag and drop the file on to one of the windows to specify the window in which they would like the file to be loaded. The bug is that after the spread appears, any movement of the mouse switches off the selective highlighting and dimming of valid/non-valid drop receptacles. Desired behaviour - The highlighting and dimming of Launcher icons should persist until the user drops the file. - Note that the 'spread when a item is held over a launcher icon' behaviour seems to be broken in the Oneiric final freeze release (nothing happens). To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/727902/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
** Description changed: - [Impact]After upgrading from Maverick to Natty, I can no longer use the - Super (windows) key in Virtual Machine Manager. Previously, as long as I - had the Virtual Machine Manager console window in the foreground, I - could press the Super key and the start menu would pop up. Since - upgrading to Natty, this no longer works, and the search box appears in - the upper left. + [Impact] + After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Buggy Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. -- 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/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Compiz Core: Triaged Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Buggy Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/741869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 754580] Re: Cannot move tabs between multiple Firefox or Chromium windows while using Unity unless windows are both unmaximized, unminimized, and visible.
** Description changed: - Binary package hint: unity + [Impact] + It's not possible to drag firefox or chromium tabs to the relative launcher icon in order to select a different window as drop target. + + [Test case] + 1. Open two Chromium or Firefox windows, with two tabs open in each. + 2. Start dragging a browser tab over a browser icon in the Launcher + 3. Unity should displays a spread of the two browser windows + 4. It will be possible to drop the tab in one of the browser windows, +after selecting it in spread. + + [Regression Potential] + As it happened with bug #727902 this codepath was disabled in the past, thus there's basically no regression potential. + + --- With Metacity, one would need only to drag the tab to the bottom bar, mouse-over the destination window, and then release the tab in the newly focused window. There is no equivalent behavior with Unity. Dragging tabs to its bar does nothing. - - Desired resolution: Users should be able to move tabs between browser windows irrespective of window state (minimised, restored or maximised) by dragging and dropping the via the Launcher app spread. - - Use case - 1. User opens two Chromium or Firefox windows, with two tabs open in each. - 2. User starts dragging a browser tab - 3. Unity slides out the Launcher with valid drop receptacles highlighted - 4. User drags the tab over a browser icon in the Launcher - 5. Unity displays a spread of the two browser windows - 6. User continues the drag, and drags and drops the tab into the other browser window - 7. Unity shifts the tab to the other browser window. If this window is minimised it is restored and brought into focus. If this window is maximised or restored it is brought into focus. -- 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/754580 Title: Cannot move tabs between multiple Firefox or Chromium windows while using Unity unless windows are both unmaximized, unminimized, and visible. Status in Ayatana Design: Fix Committed Status in Chromium Browser: New Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “chromium-browser” package in Ubuntu: Triaged Status in “firefox” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] It's not possible to drag firefox or chromium tabs to the relative launcher icon in order to select a different window as drop target. [Test case] 1. Open two Chromium or Firefox windows, with two tabs open in each. 2. Start dragging a browser tab over a browser icon in the Launcher 3. Unity should displays a spread of the two browser windows 4. It will be possible to drop the tab in one of the browser windows, after selecting it in spread. [Regression Potential] As it happened with bug #727902 this codepath was disabled in the past, thus there's basically no regression potential. --- With Metacity, one would need only to drag the tab to the bottom bar, mouse-over the destination window, and then release the tab in the newly focused window. There is no equivalent behavior with Unity. Dragging tabs to its bar does nothing. - Desired resolution: Users should be able to move tabs between browser windows irrespective of window state (minimised, restored or maximised) by dragging and dropping the via the Launcher app spread. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/754580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 607796] Re: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application
** Description changed: - If the user drags and hold a file over a running application in the - Launcher, all the windows of that application should be shown with the - spread. The user should then be able to drag and drop the file in a - windows in the spread to load the file into that specific window. + [Impact] + If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. + + [Test Case] + 1) Open two windows instances of the same application (say firefox) + 2) Drag a file from the file-manager or the desktop and hover the firefox icon + 3) After one second the firefox icon is hovered, the spread will occur + 4) You should be able to hover one of the firefox windows and it should +show a spinner, after 750ms (by default) the hovered windows should be focused +and raised + 5) You should now be able to drop the content you're dragging (if the selected +application supports that content). + + [Regression Potential] + This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. + + + ### + Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as "buggybutclosed" for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. -- 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/607796 Title: Launcher, Window management - Dragging and holding a selection over an entry in the Launcher should spread out windows belonging to that application Status in Ayatana Design: Fix Committed Status in Compiz: Fix Committed Status in Compiz 0.9.11 series: In Progress Status in One Hundred Papercuts: Fix Released Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact] If the user drags and hold a file over a running application in the Launcher, all the windows of that application should be shown with the spread. The user should then be able to drag and drop the file in a windows in the spread to load the file into that specific window. [Test Case] 1) Open two windows instances of the same application (say firefox) 2) Drag a file from the file-manager or the desktop and hover the firefox icon 3) After one second the firefox icon is hovered, the spread will occur 4) You should be able to hover one of the firefox windows and it should show a spinner, after 750ms (by default) the hovered windows should be focused and raised 5) You should now be able to drop the content you're dragging (if the selected application supports that content). [Regression Potential] This codepath was mostly disabled in the current compiz and unity code because it was buggy, so the regression potential is very low, although it might happen that, if some race-condition happens, when closing the scale the launcher might be still painted as if it would be in scale mode (desaturated) even if it's not the case anymore. ### Bug #727903 needs to be fixed at the same time. --- History: This bug had been previously fixed as "buggybutclosed" for Unity on 2011-04-18, leaving this function with other bugs: https://bugs.launchpad.net/ayatana-design/+bug/727903 https://bugs.launchpad.net/ayatana-design/+bug/727904 https://bugs.launchpad.net/ayatana-design/+bug/727902 https://bugs.launchpad.net/ayatana-design/+bug/764424 https://bugs.launchpad.net/ayatana-design/+bug/832988 On 2011-10-18, it was reopened for regression in Oneiric. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/607796/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpa
[Touch-packages] [Bug 1315060] Re: Allow --confdir to look for system jobs in more than one directory
In silo 3: http://people.canonical.com/~platform/citrain_dashboard//#?q=landing-003 ** Changed in: upstart Status: Fix Committed => Fix Released ** Changed in: upstart (Ubuntu Utopic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1315060 Title: Allow --confdir to look for system jobs in more than one directory Status in The Savilerow project: In Progress Status in Upstart: Fix Released Status in “upstart” package in Ubuntu: Fix Committed Status in “upstart” source package in Utopic: Fix Committed Bug description: A requirement from OEMs/Carriers for customization is to allow for customized upstart jobs/overrides. It seems that the best way to do this would be to allow --confdir to take multiple directories, so that we can include a directory under /custom. As for session jobs, I assume we can just set /custom as an XDG_CONFIG_DIR, and have /custom/upstart with jobs there. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 1 12:30:09 2014 InstallationDate: Installed on 2013-04-26 (370 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=610268d4-9acd-4bf8-a1a1-95c88b3ccf59 ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: Upgraded to trusty on 2013-11-23 (158 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: init (upstart 1.12.1) UpstartRunningSystemVersion: init (upstart 1.12.1) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1315060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
** Description changed: [Impact]After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) - Actual Result: the super key acts in the host and the Unity Dash is displayed + Buggy Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. -- 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/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Compiz Core: Triaged Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact]After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Buggy Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/741869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1313280] Re: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen
** Description changed: [Impact] A fullscreen window set to "always on top" hides the lockscreem. [Test Case] (1) Open a video in Totem (2) Right-click on the titlebar and set Totem to "Always on Top" (3) Make Totem full screen (eg. with the F11 key or clicking on the control) (4) Manually Lock the screen using Super+L - (5) Notice that the lockscreen is hidden by totem. + + (5) The lockscreen should go above the Totem window now. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. [Regression Potential]Two cases may potentially source regressions. - (1) windows that need to appear above the lockscreen, such as on-screen keyboards, - (2) applications presenting fullscreen windows using unusual or non-standard toolkits.It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. + (1) windows that need to appear above the lockscreen, such as on-screen keyboards,(2) applications presenting fullscreen windows using unusual or non-standard toolkits.It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. (3) Indicator menus might be not being drawn -- 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/1313280 Title: Fullscreen window set to "Always on Top" in single-monitor will hide the lockscreen Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Status in “unity” source package in Trusty: In Progress Bug description: [Impact] A fullscreen window set to "always on top" hides the lockscreem. [Test Case] (1) Open a video in Totem (2) Right-click on the titlebar and set Totem to "Always on Top" (3) Make Totem full screen (eg. with the F11 key or clicking on the control) (4) Manually Lock the screen using Super+L (5) The lockscreen should go above the Totem window now. If you don't lock it manually and just pause the video and let it lock automatically this will show the same behavior. The same behavior occurs with any application that can enter full screen mode. [Regression Potential]Two cases may potentially source regressions. (1) windows that need to appear above the lockscreen, such as on-screen keyboards,(2) applications presenting fullscreen windows using unusual or non-standard toolkits.It is unlikely that regressions in either of these cases would be introduced by this bug fix, but rather would be pre-existing problems not fixed here. (3) Indicator menus might be not being drawn To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1313280/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
** Description changed: [Impact]After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine - (2) while in the virtual machine, press the Super key + (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Actual Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. -- 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/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Compiz Core: Triaged Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact]After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Buggy Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/741869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 741869] Re: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs.
** Description changed: - [Impact] - After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. + [Impact]After upgrading from Maverick to Natty, I can no longer use the + Super (windows) key in Virtual Machine Manager. Previously, as long as I + had the Virtual Machine Manager console window in the foreground, I + could press the Super key and the start menu would pop up. Since + upgrading to Natty, this no longer works, and the search box appears in + the upper left. Also see bug #934921 [Test Case] - (1) Install virt-manager and qemu-system, create and boot a virtual machine + (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine, press the Super key - Expected Result: the super key acts inside the VM + Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Actual Result: the super key acts in the host and the Unity Dash is displayed - [regression Potential] - This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. + [regression Potential]This patch plays with key grabs and ungrabs: the + most likely potential for regression is (a) the existing grabs continue + and no fix obtains or (2) the grab is not resumed when returning control + from the VM and the Super key does not invoke the Unity Dash. -- 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/741869 Title: Unity/compiz intercepts Super and Alt keypresses from grabbed windows like VMs. Status in Ayatana Design: Fix Committed Status in Compiz: Triaged Status in Compiz Core: Triaged Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “compiz” package in Ubuntu: Triaged Status in “unity” package in Ubuntu: Fix Released Bug description: [Impact]After upgrading from Maverick to Natty, I can no longer use the Super (windows) key in Virtual Machine Manager. Previously, as long as I had the Virtual Machine Manager console window in the foreground, I could press the Super key and the start menu would pop up. Since upgrading to Natty, this no longer works, and the search box appears in the upper left. Also see bug #934921 [Test Case] (1) Install virtualbox or virt-manager and qemu-system, create and boot a virtual machine (2) while in the virtual machine (and it should grab the keyboard), press the Super key Expected Result: the super key acts inside the VM (check by install unity on it or using xev) Actual Result: the super key acts in the host and the Unity Dash is displayed [regression Potential]This patch plays with key grabs and ungrabs: the most likely potential for regression is (a) the existing grabs continue and no fix obtains or (2) the grab is not resumed when returning control from the VM and the Super key does not invoke the Unity Dash. To manage notifications about this bug go to: https://bugs.launchpad.net/ayatana-design/+bug/741869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
The problem is gone... I haven't changed anything (or been on this PC much since my original posting actually) and according to the changelogs there hasn't been an update in either Firefox or hud since then. No idea what caused this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Confirmed Status in “hud” package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int&) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointer) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const&, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, Q
[Touch-packages] [Bug 1336741] Re: test_outgoing_answer_remote_hangup failed on mako #108
** Changed in: dialer-app
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dialer-app in Ubuntu.
https://bugs.launchpad.net/bugs/1336741
Title:
test_outgoing_answer_remote_hangup failed on mako #108
Status in Dialer app for Ubuntu Touch:
Fix Released
Status in “dialer-app” package in Ubuntu:
Fix Released
Bug description:
This test is failing on mako image #108 with the following error:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dialer_app/tests/test_calls.py",
line 123, in test_outgoing_answer_remote_hangup
elapsed_time = self.main_view.live_call_page.get_elapsed_call_time()
File "/usr/lib/python2.7/dist-packages/dialer_app/emulators.py", line 46,
in get_elapsed_call_time
return self.wait_select_single(objectName='stopWatch').elapsed
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 520, in __getattr__
self.refresh_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 474, in refresh_state
_, new_state = self.get_new_state()
File "/usr/lib/python2.7/dist-packages/autopilot/introspection/dbus.py",
line 564, in get_new_state
raise StateNotFoundError(self.__class__.__name__, id=self.id)
StateNotFoundError: Object not found with name 'StopWatch' and properties
{'id': 33}.
This can be reproduced locally but only happens once every 2-3 runs,
maybe less frequently. Running the test in a loop 10 times should
produce at least a couple of failures.
To manage notifications about this bug go to:
https://bugs.launchpad.net/dialer-app/+bug/1336741/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328147] Re: update for suru icon theme
** Changed in: dialer-app Status: New => Fix Released ** Changed in: gallery-app Status: In Progress => Fix Released ** Changed in: messaging-app Status: New => Fix Released ** Changed in: camera-app Status: In Progress => Fix Released ** Changed in: address-book-app Status: New => Fix Released ** Changed in: notes-app 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/1328147 Title: update for suru icon theme Status in Address Book App: Fix Released Status in Camera App: Fix Released Status in Dialer app for Ubuntu Touch: Fix Released Status in Gallery App: Fix Released Status in Media Player App: In Progress Status in Messaging App: Fix Released Status in Notes App: Fix Released Status in Web Browser App: Fix Released Status in “webbrowser-app” package in Ubuntu: Fix Released Bug description: update the icons and assets as specified in this blueprint: https://blueprints.launchpad.net/ubuntu/+spec/client-1410-suru-icon-switch talk to Saviq and Jouni for further details and assets To manage notifications about this bug go to: https://bugs.launchpad.net/address-book-app/+bug/1328147/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1227018] Re: [Dialer app] Call happens in the background without UI for user to manage
** Changed in: dialer-app Status: Confirmed => Fix Released ** Changed in: dialer-app (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1227018 Title: [Dialer app] Call happens in the background without UI for user to manage Status in Dialer app for Ubuntu Touch: Fix Released Status in Ubuntu UX bugs: Fix Committed Status in “dialer-app” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Incomplete Bug description: design comment- when user is moved away from the live call (either while making a call or on an active call); there should be an indicator in the indicator section, the user can then navigate back to the call (dialer app) as per spec. -- "STEPS to reproduce: 1. Add number to address book 2. Touch the number and navigate out the app immediately, to the home screen 3. The dialer never comes up but the call happens in the background without any way for the user to disengage" ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: address-book-app 0.2+13.10.20130830.3-0ubuntu1 Uname: Linux 3.4.0-3-mako armv7l ApportVersion: 2.12.1-0ubuntu4 Architecture: armhf Date: Wed Sep 18 09:28:25 2013 InstallationDate: Installed on 2013-09-16 (1 days ago) InstallationMedia: Ubuntu Saucy Salamander (development branch) - armhf (20130916.3) MarkForUpload: True ProcEnviron: TERM=linux PATH=(custom, no user) SourcePackage: address-book-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1227018/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1222906] Re: [dialer-app] Refactor the dialpad view so that it can be imported and used from greeter
** Changed in: dialer-app (Ubuntu) Status: New => Fix Released ** Changed in: dialer-app Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dialer-app in Ubuntu. https://bugs.launchpad.net/bugs/1222906 Title: [dialer-app] Refactor the dialpad view so that it can be imported and used from greeter Status in Dialer app for Ubuntu Touch: Fix Released Status in “dialer-app” package in Ubuntu: Fix Released Bug description: The dialpad view of dialer-app needs to changed to make it possible for it to be imported/used from the greeter to allow for emergency calling. To manage notifications about this bug go to: https://bugs.launchpad.net/dialer-app/+bug/1222906/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317869] Re: Keyboard shortcuts overlay does not show up when workspaces are enabled at 1366x768
** Changed in: unity (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1317869 Title: Keyboard shortcuts overlay does not show up when workspaces are enabled at 1366x768 Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: My notebook has a 1366x768 screen - it is a very common screen resolution. When I boot Ubuntu 14.04 liveISO the keyboard shortcuts overlay is displayed and works very well - therefore my screen resolution is large enough for it. But after I installed 14.04 on my hard disk, the shortcuts overlay does not show anymore. The attachment is a screenshot of the shortcuts overlay working on the liveISO. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1317356] Re: Shortcut hint does not respect monitor scaling factor
** Changed in: unity (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1317356 Title: Shortcut hint does not respect monitor scaling factor Status in Unity: Fix Released Status in Unity 7.2 series: In Progress Status in “unity” package in Ubuntu: Fix Released Bug description: The shortcut hint is not properly scaled in HiDPI monitors To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1317356/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339700] Re: [regression] Device locks randomly on welcome screen
FWIW, it seems after OTA updates this issue happens more often. After running (r119, manta): $ ubuntu-device-flash --channel=devel I had no trouble with this issue lately. :-) -- 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/1339700 Title: [regression] Device locks randomly on welcome screen Status in Mir: Fix Committed Status in Mir 0.4 series: Fix Released Status in “mir” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Invalid Bug description: Unity8 welcome screen will occasionally lock. Lock effects: No launcher available Can't swipe left or right Can't drag down indicators Doesn't recover from tapping the power button a couple of times. Randomness: Locks so far have been happening on and off from image U114 The phone seems to lock up for me more on waking from suspend, however rsalveti pointed out that for him it happened on phone hang up. For me the lock happened a couple of times over the weekend images U114 and U115, and then not again till today U122. Manta seems more prone to lock ups that flo or mako. STEPS: (It seems flo has an issue identical when opening settings app) On flo update to U123 1. Once updated, open the settings app This seems to land you in the state described. Apparently this is only a temporary version if you leave the device for a while it will unlock. But I think that is possibly because you are moved away from the app and it is unlocked by the system waking from suspend possibly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.90+14.10.20140707-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu1 Architecture: armhf Date: Wed Jul 9 13:48:14 2014 InstallationDate: Installed on 2014-07-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140709-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1339700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341682] Re: Does not refresh the list of contexts from ofono when a new context is added
phablet@ubuntu-phablet:~$ date Mon Jul 14 16:00:45 EDT 2014 phablet@ubuntu-phablet:~$ /usr/share/ofono/scripts/create-mms-context Found context /ril_0/context7 Log is attached but while watching it I did not see anything related -- 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/1341682 Title: Does not refresh the list of contexts from ofono when a new context is added Status in “network-manager” package in Ubuntu: Incomplete Bug description: Add a context via the command line scripts or via the QML api. A context added signal is issued by ofono (per dbus-monitor --system "interface=org.ofono.ConnectionManager" and QML signal) The list of connections in network manager does not change (per nmcli con) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1341682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341682] Re: Does not refresh the list of contexts from ofono when a new context is added
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1341682/+attachment/4152456/+files/syslog -- 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/1341682 Title: Does not refresh the list of contexts from ofono when a new context is added Status in “network-manager” package in Ubuntu: Incomplete Bug description: Add a context via the command line scripts or via the QML api. A context added signal is issued by ofono (per dbus-monitor --system "interface=org.ofono.ConnectionManager" and QML signal) The list of connections in network manager does not change (per nmcli con) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1341682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341682] Re: Does not refresh the list of contexts from ofono when a new context is added
Could you try this with NetworkManager running in debug mode? It would be useful to have all the logs from NetworkManager. To do this, you can edit /etc/init/network-manager.conf; to add --log- level=debug to the Exec line. The logs will be in /var/log/syslog. ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- 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/1341682 Title: Does not refresh the list of contexts from ofono when a new context is added Status in “network-manager” package in Ubuntu: Incomplete Bug description: Add a context via the command line scripts or via the QML api. A context added signal is issued by ofono (per dbus-monitor --system "interface=org.ofono.ConnectionManager" and QML signal) The list of connections in network manager does not change (per nmcli con) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1341682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341708] Re: wpa_supplicant[1306]: nl80211: send_and_recv->nl_recvmsgs failed: -33
** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1341708/+attachment/4152426/+files/syslog -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1341708 Title: wpa_supplicant[1306]: nl80211: send_and_recv->nl_recvmsgs failed: -33 Status in “wpa” package in Ubuntu: New Bug description: Jul 14 15:01:51 caravena-530U3C-530U4C wpa_supplicant[1306]: wlan0: CTRL-EVENT-SCAN-STARTED Jul 14 15:01:57 caravena-530U3C-530U4C wpa_supplicant[1306]: nl80211: send_and_recv->nl_recvmsgs failed: -33 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wpasupplicant 2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4 Uname: Linux 3.16.0-3-lowlatency x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 14 15:00:14 2014 InstallationDate: Installed on 2014-04-27 (78 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1341708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341708] [NEW] wpa_supplicant[1306]: nl80211: send_and_recv->nl_recvmsgs failed: -33
Public bug reported: Jul 14 15:01:51 caravena-530U3C-530U4C wpa_supplicant[1306]: wlan0: CTRL-EVENT-SCAN-STARTED Jul 14 15:01:57 caravena-530U3C-530U4C wpa_supplicant[1306]: nl80211: send_and_recv->nl_recvmsgs failed: -33 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wpasupplicant 2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4 Uname: Linux 3.16.0-3-lowlatency x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 14 15:00:14 2014 InstallationDate: Installed on 2014-04-27 (78 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: wpa (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug utopic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1341708 Title: wpa_supplicant[1306]: nl80211: send_and_recv->nl_recvmsgs failed: -33 Status in “wpa” package in Ubuntu: New Bug description: Jul 14 15:01:51 caravena-530U3C-530U4C wpa_supplicant[1306]: wlan0: CTRL-EVENT-SCAN-STARTED Jul 14 15:01:57 caravena-530U3C-530U4C wpa_supplicant[1306]: nl80211: send_and_recv->nl_recvmsgs failed: -33 ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: wpasupplicant 2.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4 Uname: Linux 3.16.0-3-lowlatency x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CurrentDesktop: GNOME Date: Mon Jul 14 15:00:14 2014 InstallationDate: Installed on 2014-04-27 (78 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) SourcePackage: wpa UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1341708/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341085] Re: system crashes even the BIOS
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- 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/1341085 Title: system crashes even the BIOS Status in “apport” package in Ubuntu: New Bug description: I have been using 13.10 but upgraded to 14.04 from 13.10 OS upgrade package since then my laptop crashes frequently and even corrupts the BIOS which results in no BIOS loading and opening laptop physically desoldering the CMOS battary and after 10 minutes recovering BIOS to normal this has happend 100's of times and I am frustated of this i had a dual boot config but Ubuntu has even corrupted windows and now It fails to load windows OS further Lenovo one key recovery has also failed to repair windows problems and even restoring factory image. Now I am struck with a faulty Ubuntu 14.04 which crashes veery now and then and every time i have to open it's motherboard to reset BIOS and even then system crashes without any warning and fails to restart pls help. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apport 2.14.1-0ubuntu3.2 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportLog: ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Sat Jul 12 14:36:55 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2013-10-28 (256 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) PackageArchitecture: all SourcePackage: apport UpgradeStatus: Upgraded to trusty on 2014-04-19 (83 days ago) mtime.conffile..etc.apport.crashdb.conf: 2014-07-12T14:22:08.256868 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1341085/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997269] Re: dovecot imap broken by apparmor policy
For me it has been fixed by 14.04 and can now run with the different dovecot apparmor profiles swithed on -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy Status in “apparmor” package in Ubuntu: Incomplete Status in “dovecot” package in Ubuntu: Invalid Status in “apparmor” package in Debian: Confirmed Bug description: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor="ALLOWED" operation="getattr" parent=10922 profile="/usr/sbin/dovecot//null-107 //null-10b//null-118" name="/home/foobar/Maildir/.foobar/dovecot.index.log" pid=10937 comm="imap" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has "flags=(complain)", but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the "usr.lib.dovecot.imap" policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in "complain" mode. What are these "//null-NNN/" strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) --- ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) Package: apparmor 2.7.102-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=7e6df5b7-d31e-4757-a388-f4f477187a63 ro ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Tags: precise Uname: Linux 3.2.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1315060] Re: Allow --confdir to look for system jobs in more than one directory
** Changed in: savilerow Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1315060 Title: Allow --confdir to look for system jobs in more than one directory Status in The Savilerow project: In Progress Status in Upstart: Fix Committed Status in “upstart” package in Ubuntu: In Progress Status in “upstart” source package in Utopic: In Progress Bug description: A requirement from OEMs/Carriers for customization is to allow for customized upstart jobs/overrides. It seems that the best way to do this would be to allow --confdir to take multiple directories, so that we can include a directory under /custom. As for session jobs, I assume we can just set /custom as an XDG_CONFIG_DIR, and have /custom/upstart with jobs there. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu May 1 12:30:09 2014 InstallationDate: Installed on 2013-04-26 (370 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=UUID=610268d4-9acd-4bf8-a1a1-95c88b3ccf59 ro quiet splash vt.handoff=7 SourcePackage: upstart UpgradeStatus: Upgraded to trusty on 2013-11-23 (158 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: init (upstart 1.12.1) UpstartRunningSystemVersion: init (upstart 1.12.1) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1315060/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1304754] Re: gccgo has issues when page size is not 4kB
@Matthias, Thanks for the work on this. We are blocked running Juju on power8le. Will gcc be updated in the archives as of July 17, or go into proposed at that time? -thanks, Antonio -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gccgo-4.9 in Ubuntu. https://bugs.launchpad.net/bugs/1304754 Title: gccgo has issues when page size is not 4kB Status in The GNU Compiler Collection: Fix Released Status in “gcc-4.9” package in Ubuntu: Fix Released Status in “gccgo-4.9” package in Ubuntu: Invalid Status in “gcc-4.9” source package in Trusty: Invalid Status in “gccgo-4.9” source package in Trusty: In Progress Status in “gcc-4.9” source package in Utopic: Fix Released Status in “gccgo-4.9” source package in Utopic: Invalid Bug description: On kernels 3.13-18 and 3.13-23 (there may be others) the kernel is killing gccgo compiled binaries [18519.444748] jujud[19277]: bad frame in setup_rt_frame: nip lr [18519.673632] init: juju-agent-ubuntu-local main process (19220) killed by SEGV signal [18519.673651] init: juju-agent-ubuntu-local main process ended, respawning In powerpc/kernel/signal_64.c: sys_rt_sigreturn is jumping to the badframe: label and executing an unconditional force_sigsegv which is delivered to the userland process. Like C++, gccgo tries to decode SIGSEGV as a nil pointer access and blame some random function that happened to be the top stack frame. Reverting to the 3.13-08 kernel appears to resolve the issue which (weakly) points the finger at the recent switch to 64k pages. To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1304754/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1326467] Re: Need vertical journal category layout to improve single-column views.
** Changed in: savilerow Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1326467 Title: Need vertical journal category layout to improve single-column views. Status in The Savilerow project: Fix Released Status in The Unity 8 shell: Fix Released Status in “unity8” package in Ubuntu: Fix Released Bug description: When the results are shown as horizontal cards, there is way too large of a gap in between results To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1326467/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1337508] Re: All review widgets are changable
** Changed in: savilerow 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-click in Ubuntu. https://bugs.launchpad.net/bugs/1337508 Title: All review widgets are changable Status in The Savilerow project: Fix Released Status in “unity-scope-click” package in Ubuntu: Invalid Status in “unity8” package in Ubuntu: Fix Released Bug description: When a "reviews" widget exists in a preview, it's always changable by the user, even when it's not a rating-input widget. When a reviews widget is showing someone else's review, it shouldn't be changable ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 (not installed) ProcVersionSignature: Ubuntu 3.15.0-6.11-generic 3.15.0 Uname: Linux 3.15.0-6-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.4-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Jul 3 14:52:57 2014 InstallationDate: Installed on 2013-04-26 (433 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: unity8 UpgradeStatus: Upgraded to utopic on 2014-06-10 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/savilerow/+bug/1337508/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1337408] Re: veritcal-journal with single result does not display
** Changed in: savilerow
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1337408
Title:
veritcal-journal with single result does not display
Status in The Savilerow project:
Fix Released
Status in The Unity 8 shell:
Fix Released
Status in “unity8” package in Ubuntu:
Fix Released
Bug description:
When I use vertical-journal, if there is only a single result, it does not
display. when there is more than one result, they all display.
{
"schema-version" : 1,
"template" : {
"category-layout" : "vertical-journal",
"card-size": "20"
},
"components" : {
"title" : "title",
"art" : "art"
}
}
When using grid layout, my results always display, even with there is only
one.
{
"schema-version" : 1,
"template" : {
"category-layout" : "grid",
"card-size": "small"
},
"components" : {
"title" : "title",
"art" : "art"
}
}
Please see attachments.
To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1337408/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341623] Re: systemd-logind assert failure: alloc.c:315: Assertion failed in nih_free: ptr != NULL
Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=81354.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
On 2014-07-14T16:51:15+00:00 Cristian Aravena Romero wrote:
Open bug in launchpad.net:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1341623
Crash.
#0 0x7f179fb4c117 in __GI_raise (sig=sig@entry=6) at
../nptl/sysdeps/unix/sysv/linux/raise.c:56
resultvar = 0
pid = 1045
selftid = 1045
#1 0x7f179fb4d808 in __GI_abort () at abort.c:89
save_stage = 2
act = {__sigaction_handler = {sa_handler = 0x8a64d0, sa_sigaction =
0x8a64d0}, sa_mask = {__val = {9137825, 4354759, 9137552, 4350346, 1,
4294967296, 4322088, 9139344, 206158430256, 140737480192464, 140737480192256,
0, 139739453006202, 0, 140737480192368, 9137520}}, sa_flags = 9137825,
sa_restorer = 0x4272c7}
sigs = {__val = {32, 0 }}
#2 0x7f17a0537309 in nih_free (ptr=0x0) at alloc.c:318
ctx =
__FUNCTION__ = "nih_free"
#3 0x00422ae0 in cgm_get (controller=0x4272c7 "systemd",
cgroup_path=0x8b6ea1 "user/1000.user/c2.session", cgroup_path@entry=0x8b6ea0
"/user/1000.user/c2.session", key=key@entry=0x433f05 "tasks") at
../src/shared/cgmanager.c:143
nerr = 0x8b6d90
result = 0x0
ret = 0x0
__func__ = "cgm_get"
#4 0x00420aa7 in cg_enumerate_tasks (controller=0x42618a
"name=systemd", path=0x8b6ea0 "/user/1000.user/c2.session",
_f=_f@entry=0x7f837248) at ../src/shared/cgroup-util.c:128
fs = 0x0
f =
r =
value = 0x0
template = 0x0
fd =
__PRETTY_FUNCTION__ = "cg_enumerate_tasks"
#5 0x00420c6a in cg_is_empty (controller=,
path=, ignore_self=true) at ../src/shared/cgroup-util.c:1125
f = 0x0
pid = 0
self_pid =
found = false
r =
#6 0x00420dcb in cg_is_empty_recursive
(controller=controller@entry=0x42618a "name=systemd", path=0x8b6ea0
"/user/1000.user/c2.session", ignore_self=ignore_self@entry=true) at
../src/shared/cgroup-util.c:1171
d = 0x0
fn = 0x18
r =
children = 0x0
p1 =
i = 0
__PRETTY_FUNCTION__ = "cg_is_empty_recursive"
#7 0x0040feab in session_terminate_cgroup (s=0x8b6960) at
../src/login/logind-session.c:651
r =
k =
#8 session_stop (s=s@entry=0x8b6960) at ../src/login/logind-session.c:709
__PRETTY_FUNCTION__ = "session_stop"
__func__ = "session_stop"
#9 0x00409630 in manager_dispatch_other (fd=23, m=0x8a5010) at
../src/login/logind.c:1262
s = 0x8b6960
i =
b =
#10 manager_run (m=m@entry=0x8a5010) at ../src/login/logind.c:1795
event = {events = 16, data = {ptr = 0x1d, fd = 29, u32 = 29, u64 = 29}}
n =
msec =
__PRETTY_FUNCTION__ = "manager_run"
__func__ = "manager_run"
#11 0x0040622c in main (argc=, argv=) at
../src/login/logind.c:1872
m = 0x8a5010
r = 0
__func__ = "main"
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1341623/comments/6
On 2014-07-14T17:27:40+00:00 Lennart-poettering wrote:
nig_free? THat's not an upstream symbol. Please file a bug against
Ubuntu.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1341623/comments/7
** Changed in: systemd
Status: Unknown => Won't Fix
** Changed in: systemd
Importance: Unknown => Critical
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1341623
Title:
systemd-logind assert failure: alloc.c:315: Assertion failed in
nih_free: ptr != NULL
Status in systemd:
Won't Fix
Status in “systemd” package in Ubuntu:
New
Bug description:
Crash.
ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: systemd 204-12ubuntu1
ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4
Uname: Linux 3.16.0-3-lowlatency x86_64
ApportVersion: 2.14.4-0ubuntu2
Architecture: amd64
AssertionMessage: alloc.c:315: Assertion failed in nih_free: ptr != NULL
Date: Mon Jul 14 09:39:48 2014
ExecutablePath: /lib/systemd/systemd-logind
InstallationDate: Installed on 2014-04-27 (78 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64
(20140416.2)
ProcCmdline: /lib/systemd/systemd-logind
ProcEnviron:
Signal: 6
SourcePackage: systemd
StacktraceTop:
nih_free () from /lib/x86_64-linux-gnu/libnih.so.1
?? ()
?? ()
?? ()
?? ()
Title: systemd-logind a
[Touch-packages] [Bug 1341686] [NEW] headphones output device briefly disappears, then immediately re-appears
Public bug reported: in the sound settings control panel that the headphones output device briefly disappears, then immediately re-appears ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ady13 3039 F pulseaudio /dev/snd/controlC0: ady13 3039 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 14 21:04:30 2014 InstallationDate: Installed on 2014-07-14 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: SPDIF Out, Internal Symptom_Type: Sound works for a while, then breaks Title: [Z87X-UD3H, Realtek ALC898, SPDIF Out, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87X-UD3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/17/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87X-UD3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-07-14T19:34:16.451925 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1341686 Title: headphones output device briefly disappears, then immediately re- appears Status in “alsa-driver” package in Ubuntu: New Bug description: in the sound settings control panel that the headphones output device briefly disappears, then immediately re-appears ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: alsa-base 1.0.25+dfsg-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ady13 3039 F pulseaudio /dev/snd/controlC0: ady13 3039 F pulseaudio CurrentDesktop: Unity Date: Mon Jul 14 21:04:30 2014 InstallationDate: Installed on 2014-07-14 (0 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: SPDIF Out, Internal Symptom_Type: Sound works for a while, then breaks Title: [Z87X-UD3H, Realtek ALC898, SPDIF Out, Internal] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/17/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z87X-UD3H-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd04/17/2013:svnGigabyteTechnologyCo.,Ltd.:pnZ87X-UD3H:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ87X-UD3H-CF:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: Z87X-UD3H dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. mtime.conffile..etc.modprobe.d.alsa.base.conf: 2014-07-14T19:34:16.451925 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1341686/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1301160] Re: Gtk-message: Failed to load module "unity-gtk-module"
14 July 2014 - the bug is still present from terminal almost any app complain about : Failed to load module "unity-gtk-module -- 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/1301160 Title: Gtk-message: Failed to load module "unity-gtk-module" Status in “unity” package in Ubuntu: Confirmed Bug description: Trusty i386, logged as gnome-shell (genuine trusty archive package) Found that error logged into: .cache/upstart/gnome-session-gnome.log Join a strace about unity-gtk-module nb: i really does not know about the package to report against ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity 7.1.2+14.04.20140328.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-21.43-generic 3.13.8 Uname: Linux 3.13.0-21-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.14-0ubuntu1 Architecture: i386 CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell] CurrentDesktop: GNOME Date: Wed Apr 2 07:55:32 2014 InstallationDate: Installed on 2013-10-25 (158 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021.1) SourcePackage: unity UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1301160/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341262] Re: 6 core apps take you to preview when clicked, don't open in #128
I've updated the click scope testplan to include this check: https://wiki.ubuntu.com/Process/Merges/TestPlan/unity-scope-click -- 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/1341262 Title: 6 core apps take you to preview when clicked, don't open in #128 Status in “unity8” package in Ubuntu: In Progress Bug description: Update phone to #128 Note the new icons for the 6 core apps at the top of the click scope. see screenshot. Tap one of them, they go to a preview rather than opening. I would expect to open an app when tapping To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1341262/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341682] [NEW] Does not refresh the list of contexts from ofono when a new context is added
Public bug reported: Add a context via the command line scripts or via the QML api. A context added signal is issued by ofono (per dbus-monitor --system "interface=org.ofono.ConnectionManager" and QML signal) The list of connections in network manager does not change (per nmcli con) ** Affects: network-manager (Ubuntu) Importance: Undecided Assignee: Mathieu Trudel-Lapierre (mathieu-tl) Status: New ** Changed in: network-manager (Ubuntu) Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl) -- 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/1341682 Title: Does not refresh the list of contexts from ofono when a new context is added Status in “network-manager” package in Ubuntu: New Bug description: Add a context via the command line scripts or via the QML api. A context added signal is issued by ofono (per dbus-monitor --system "interface=org.ofono.ConnectionManager" and QML signal) The list of connections in network manager does not change (per nmcli con) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1341682/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1283065] Re: Use the existing audio stack to play event sounds
This bug was fixed in the package indicator-datetime - 13.10.0+14.10.20140714.1-0ubuntu1 --- indicator-datetime (13.10.0+14.10.20140714.1-0ubuntu1) utopic; urgency=low [ Charles Kerr ] * Use GStreamer's API directly to play sound instead of using libcanberra. (LP: #1283065) -- Ubuntu daily releaseMon, 14 Jul 2014 13:40:44 + ** Changed in: indicator-datetime (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-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1283065 Title: Use the existing audio stack to play event sounds Status in “indicator-datetime” package in Ubuntu: Fix Released Bug description: This merge introduced several new packages in order to produce sounds on calendar events https://code.launchpad.net/~charlesk/indicator-datetime/alarms/+merge/204420 We should rather use existing APIs in QtMultimedia or go directly to the media service in the platform api. - reduce number of packages supported - allow coordination for audio playback from multiple sources - support multiple encoding formats To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1283065/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340869] Re: friends-service should be dropped from 14.10 framework and disallowed by the SDK
** Changed in: click-reviewers-tools (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1340869 Title: friends-service should be dropped from 14.10 framework and disallowed by the SDK Status in Qt Creator plugins for Ubuntu: Fix Committed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: New Status in “click-reviewers-tools” package in Ubuntu: Fix Committed Status in “qtcreator-plugin-ubuntu” package in Ubuntu: New Bug description: 'friends' does not actually fit the phone security model (any app with access can impersonate the user with impunity on social media). friends-app is being dropped from the phone, and friends-service should also be dropped from the framework definition for 14.10. We need to keep friends-service on the phone as long as we support the 14.04 framework, but it should not be allowed by the SDK when targeting 14.10. To manage notifications about this bug go to: https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1340869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1228093] Re: Dash content flickers when the touchpad is used to scroll it.
** Branch linked: lp:~3v1n0/nux/horizontal-scroll-delta -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nux in Ubuntu. https://bugs.launchpad.net/bugs/1228093 Title: Dash content flickers when the touchpad is used to scroll it. Status in Nux: In Progress Status in “nux” package in Ubuntu: In Progress Bug description: When the touchpad is used to scroll the dash sometimes scroll down is dected as scroll up and vice versa. Two fingers scroll must be ON! This is because horizontal scrolling is now enabled by default and can't be disabled using g-c-c. To manage notifications about this bug go to: https://bugs.launchpad.net/nux/+bug/1228093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339709] Re: Dialog does not appear to support anchorToKeyboard
** Changed in: ubuntu-ui-toolkit (Ubuntu) Status: New => Fix Released ** Changed in: ubuntu-ui-toolkit Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-ui-toolkit in Ubuntu. https://bugs.launchpad.net/bugs/1339709 Title: Dialog does not appear to support anchorToKeyboard Status in Ubuntu UI Toolkit: Fix Released Status in “ubuntu-ui-toolkit” package in Ubuntu: Fix Released Bug description: When using a Dialog object, it is very easy for the OSK to cover elements in the Dialog. Even with the MainView setting anchorToKeyboard: true. I ran into this when looking at the set-a-password Dialog in ubuntu- system-settings. And it seems like it has bit us a couple times in testing: bug 1339616 for sudoku-app and bug 1339627 for calendar-app. Can we have it respect anchorToKeyboard please? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1339709/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1337189] Re: No access to Service Numbers on SIM
This has been implemented in system settings in the Phone panel ** Changed in: address-book-app (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to address-book-app in Ubuntu. https://bugs.launchpad.net/bugs/1337189 Title: No access to Service Numbers on SIM Status in “address-book-app” package in Ubuntu: Fix Released Bug description: Test case: - Insert a SIM card with service numbers stored (in the EF_SDN file of the SIM). - The numbers are correctly listed as oFono property org.ofono.SimManager.ServiceNumbers ... - ... but nowhere in the UI. Examples of are operators' customer support numbers, or even local emergency service numbers (see bug 1334860 for a real-life example). This is less complex to implement than the user phonebook (in the EF_ADN file of the SIM, see bug 1331346), as the SDNs are read-only, and the oFono support exists today. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/address-book-app/+bug/1337189/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1324580] Re: alarm will only ring for a minute and stop whether or not the user interacted with it
** Changed in: indicator-datetime (Ubuntu) Importance: Undecided => High ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed => Triaged ** Changed in: indicator-datetime (Ubuntu) Assignee: (unassigned) => Charles Kerr (charlesk) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-datetime in Ubuntu. https://bugs.launchpad.net/bugs/1324580 Title: alarm will only ring for a minute and stop whether or not the user interacted with it Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu Clock App reboot series: Confirmed Status in “indicator-datetime” package in Ubuntu: Triaged Bug description: When an alarm goes off, it will ring for only a minute and after that, whether or not the user disabled it, it stays quiet forever more. It would be interesting adding a second or even third ring after the first if the alarm was not properly disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1324580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341623] Re: systemd-logind assert failure: alloc.c:315: Assertion failed in nih_free: ptr != NULL
** Bug watch added: freedesktop.org Bugzilla #81354 https://bugs.freedesktop.org/show_bug.cgi?id=81354 ** Also affects: systemd via https://bugs.freedesktop.org/show_bug.cgi?id=81354 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1341623 Title: systemd-logind assert failure: alloc.c:315: Assertion failed in nih_free: ptr != NULL Status in systemd: Unknown Status in “systemd” package in Ubuntu: New Bug description: Crash. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: systemd 204-12ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4 Uname: Linux 3.16.0-3-lowlatency x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AssertionMessage: alloc.c:315: Assertion failed in nih_free: ptr != NULL Date: Mon Jul 14 09:39:48 2014 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2014-04-27 (78 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: Signal: 6 SourcePackage: systemd StacktraceTop: nih_free () from /lib/x86_64-linux-gnu/libnih.so.1 ?? () ?? () ?? () ?? () Title: systemd-logind assert failure: alloc.c:315: Assertion failed in nih_free: ptr != NULL UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1341623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340869] Re: friends-service should be dropped from 14.10 framework and disallowed by the SDK
** Also affects: click-reviewers-tools (Ubuntu) Importance: Undecided Status: New ** Also affects: apparmor-easyprof-ubuntu (Ubuntu) Importance: Undecided Status: New ** Changed in: click-reviewers-tools (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1340869 Title: friends-service should be dropped from 14.10 framework and disallowed by the SDK Status in Qt Creator plugins for Ubuntu: Fix Committed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: New Status in “click-reviewers-tools” package in Ubuntu: In Progress Status in “qtcreator-plugin-ubuntu” package in Ubuntu: New Bug description: 'friends' does not actually fit the phone security model (any app with access can impersonate the user with impunity on social media). friends-app is being dropped from the phone, and friends-service should also be dropped from the framework definition for 14.10. We need to keep friends-service on the phone as long as we support the 14.04 framework, but it should not be allowed by the SDK when targeting 14.10. To manage notifications about this bug go to: https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1340869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1340869] Re: friends-service should be dropped from 14.10 framework and disallowed by the SDK
** Changed in: qtcreator-plugin-ubuntu Status: Confirmed => Fix Committed ** Changed in: qtcreator-plugin-ubuntu Assignee: (unassigned) => Zoltan Balogh (bzoltan) ** Changed in: click-reviewers-tools (Ubuntu) Assignee: (unassigned) => Zoltan Balogh (bzoltan) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1340869 Title: friends-service should be dropped from 14.10 framework and disallowed by the SDK Status in Qt Creator plugins for Ubuntu: Fix Committed Status in “apparmor-easyprof-ubuntu” package in Ubuntu: New Status in “click-reviewers-tools” package in Ubuntu: In Progress Status in “qtcreator-plugin-ubuntu” package in Ubuntu: New Bug description: 'friends' does not actually fit the phone security model (any app with access can impersonate the user with impunity on social media). friends-app is being dropped from the phone, and friends-service should also be dropped from the framework definition for 14.10. We need to keep friends-service on the phone as long as we support the 14.04 framework, but it should not be allowed by the SDK when targeting 14.10. To manage notifications about this bug go to: https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1340869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339700] Re: [regression] Device locks randomly on welcome screen
This bug was fixed in the package mir - 0.4.1+14.10.20140714-0ubuntu1 --- mir (0.4.1+14.10.20140714-0ubuntu1) utopic; urgency=medium [ Daniel van Vugt ] * Bug fix release 0.4.1 (https://launchpad.net/mir/+milestone/0.4.1) fixes: - [regression] Device locks randomly on welcome screen (LP: #1339700) -- Ubuntu daily releaseMon, 14 Jul 2014 13:13:37 + ** Changed in: mir (Ubuntu) Status: Triaged => Fix Released -- 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/1339700 Title: [regression] Device locks randomly on welcome screen Status in Mir: Fix Committed Status in Mir 0.4 series: Fix Released Status in “mir” package in Ubuntu: Fix Released Status in “unity8” package in Ubuntu: Invalid Bug description: Unity8 welcome screen will occasionally lock. Lock effects: No launcher available Can't swipe left or right Can't drag down indicators Doesn't recover from tapping the power button a couple of times. Randomness: Locks so far have been happening on and off from image U114 The phone seems to lock up for me more on waking from suspend, however rsalveti pointed out that for him it happened on phone hang up. For me the lock happened a couple of times over the weekend images U114 and U115, and then not again till today U122. Manta seems more prone to lock ups that flo or mako. STEPS: (It seems flo has an issue identical when opening settings app) On flo update to U123 1. Once updated, open the settings app This seems to land you in the state described. Apparently this is only a temporary version if you leave the device for a while it will unlock. But I think that is possibly because you are moved away from the app and it is unlocked by the system waking from suspend possibly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.90+14.10.20140707-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu1 Architecture: armhf Date: Wed Jul 9 13:48:14 2014 InstallationDate: Installed on 2014-07-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140709-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1339700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341623] Re: systemd-logind assert failure: alloc.c:315: Assertion failed in nih_free: ptr != NULL
** 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 systemd in Ubuntu. https://bugs.launchpad.net/bugs/1341623 Title: systemd-logind assert failure: alloc.c:315: Assertion failed in nih_free: ptr != NULL Status in “systemd” package in Ubuntu: New Bug description: Crash. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: systemd 204-12ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-3.8-lowlatency 3.16.0-rc4 Uname: Linux 3.16.0-3-lowlatency x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 AssertionMessage: alloc.c:315: Assertion failed in nih_free: ptr != NULL Date: Mon Jul 14 09:39:48 2014 ExecutablePath: /lib/systemd/systemd-logind InstallationDate: Installed on 2014-04-27 (78 days ago) InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2) ProcCmdline: /lib/systemd/systemd-logind ProcEnviron: Signal: 6 SourcePackage: systemd StacktraceTop: nih_free () from /lib/x86_64-linux-gnu/libnih.so.1 ?? () ?? () ?? () ?? () Title: systemd-logind assert failure: alloc.c:315: Assertion failed in nih_free: ptr != NULL UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1341623/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339387] Re: Can't lookup DNS for akamaihd.net
I have eventually added 8.8.8.8, 8.8.4.4 as static DNSs - could that be the explanation for that line? Removing the static DNSs makes no difference. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1339387 Title: Can't lookup DNS for akamaihd.net Status in “resolvconf” package in Ubuntu: Incomplete Bug description: Ubuntu 14.04 on ThinkPad W530 My Ubuntu machine can't lookup the DNS for akamaihd.net. I tried different WiFis, other computers do work. All other domains (seem to) work. Accesing through proxies work and online services can recognize it's DNS (which I can ping if entering the IP-address by hand). $ host akamaihd.net # does not terminate $ ping akamaihd.net # does not terminate, no output $ sudo dpkg-reconfigure resolvconf # + reboot did not make a difference $ sudo /etc/init.d/dns-clean # makes no difference $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.1.1 search localdomain Modifying the /etc/hosts file fixes the issue. (E.g. I added "77.109.171.19 fbstatic-a.akamaihd.net" and then that partial service worked.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1339387/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339700] Re: [regression] Device locks randomly on welcome screen
** Branch linked: lp:ubuntu/utopic-proposed/mir -- 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/1339700 Title: [regression] Device locks randomly on welcome screen Status in Mir: Fix Committed Status in Mir 0.4 series: Fix Released Status in “mir” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: Invalid Bug description: Unity8 welcome screen will occasionally lock. Lock effects: No launcher available Can't swipe left or right Can't drag down indicators Doesn't recover from tapping the power button a couple of times. Randomness: Locks so far have been happening on and off from image U114 The phone seems to lock up for me more on waking from suspend, however rsalveti pointed out that for him it happened on phone hang up. For me the lock happened a couple of times over the weekend images U114 and U115, and then not again till today U122. Manta seems more prone to lock ups that flo or mako. STEPS: (It seems flo has an issue identical when opening settings app) On flo update to U123 1. Once updated, open the settings app This seems to land you in the state described. Apparently this is only a temporary version if you leave the device for a while it will unlock. But I think that is possibly because you are moved away from the app and it is unlocked by the system waking from suspend possibly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.90+14.10.20140707-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu1 Architecture: armhf Date: Wed Jul 9 13:48:14 2014 InstallationDate: Installed on 2014-07-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140709-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1339700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339700] Re: [regression] Device locks randomly on welcome screen
** Changed in: mir/0.4 Status: In Progress => Fix Committed ** Changed in: mir/0.4 Status: Fix Committed => Fix Released -- 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/1339700 Title: [regression] Device locks randomly on welcome screen Status in Mir: Fix Committed Status in Mir 0.4 series: Fix Released Status in “mir” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: Invalid Bug description: Unity8 welcome screen will occasionally lock. Lock effects: No launcher available Can't swipe left or right Can't drag down indicators Doesn't recover from tapping the power button a couple of times. Randomness: Locks so far have been happening on and off from image U114 The phone seems to lock up for me more on waking from suspend, however rsalveti pointed out that for him it happened on phone hang up. For me the lock happened a couple of times over the weekend images U114 and U115, and then not again till today U122. Manta seems more prone to lock ups that flo or mako. STEPS: (It seems flo has an issue identical when opening settings app) On flo update to U123 1. Once updated, open the settings app This seems to land you in the state described. Apparently this is only a temporary version if you leave the device for a while it will unlock. But I think that is possibly because you are moved away from the app and it is unlocked by the system waking from suspend possibly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.90+14.10.20140707-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu1 Architecture: armhf Date: Wed Jul 9 13:48:14 2014 InstallationDate: Installed on 2014-07-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140709-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1339700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341638] [NEW] New upstream bugfix release 1.0.5 (LXC MRE)
Public bug reported: We have released LXC 1.0.5 upstream: https://linuxcontainers.org/news This will be the second upstream bugfix release to hit trusty. The upstream changes are detailed at the URL above. The MRE was reviewed by Martin Pitt here: https://lists.ubuntu.com/archives/technical-board/2014-April/001869.html As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now. Utopic is now on the LXC 1.1 alpha branch which bugfixes for 1.0.5 have been taken from, so although they aren't identical anymore, all the changes in 1.0.5 are already in utopic. ** Affects: lxc (Ubuntu) Importance: Undecided Status: Invalid ** Affects: lxc (Ubuntu Trusty) Importance: Medium Assignee: Stéphane Graber (stgraber) Status: In Progress ** Also affects: lxc (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: lxc (Ubuntu) Status: New => Invalid ** Changed in: lxc (Ubuntu Trusty) Status: New => In Progress ** Changed in: lxc (Ubuntu Trusty) Importance: Undecided => Medium ** Changed in: lxc (Ubuntu Trusty) Assignee: (unassigned) => Stéphane Graber (stgraber) -- 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/1341638 Title: New upstream bugfix release 1.0.5 (LXC MRE) Status in “lxc” package in Ubuntu: Invalid Status in “lxc” source package in Trusty: In Progress Bug description: We have released LXC 1.0.5 upstream: https://linuxcontainers.org/news This will be the second upstream bugfix release to hit trusty. The upstream changes are detailed at the URL above. The MRE was reviewed by Martin Pitt here: https://lists.ubuntu.com/archives/technical- board/2014-April/001869.html As for testing, this version went through both automated testing (all the tests present in lxc-tests + the python3 API tests) as well as manual testing done by myself, LXC contributors and LXC users who've been building the git stable branch for a while now. Utopic is now on the LXC 1.1 alpha branch which bugfixes for 1.0.5 have been taken from, so although they aren't identical anymore, all the changes in 1.0.5 are already in utopic. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1341638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1341625] Re: compiz crashed with SIGABRT in __libc_message()
*** This bug is a duplicate of bug 1307081 *** https://bugs.launchpad.net/bugs/1307081 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1307081, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/1341625/+attachment/4152324/+files/CoreDump.gz ** Attachment removed: "Disassembly.txt" https://bugs.launchpad.net/bugs/1341625/+attachment/4152326/+files/Disassembly.txt ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/1341625/+attachment/4152328/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/1341625/+attachment/4152329/+files/ProcStatus.txt ** Attachment removed: "Registers.txt" https://bugs.launchpad.net/bugs/1341625/+attachment/4152330/+files/Registers.txt ** Attachment removed: "Stacktrace.txt" https://bugs.launchpad.net/bugs/1341625/+attachment/4152331/+files/Stacktrace.txt ** Attachment removed: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/1341625/+attachment/4152332/+files/ThreadStacktrace.txt ** This bug has been marked a duplicate of private bug 1307081 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1341625 Title: compiz crashed with SIGABRT in __libc_message() Status in “unity” package in Ubuntu: New Bug description: Dash sometimes crashes. ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity 7.3.0+14.10.20140711-0ubuntu1 ProcVersionSignature: Ubuntu 3.16.0-3.8-generic 3.16.0-rc4 Uname: Linux 3.16.0-3-generic x86_64 ApportVersion: 2.14.4-0ubuntu2 Architecture: amd64 CrashCounter: 1 CurrentDesktop: Unity Date: Mon Jul 14 19:03:31 2014 ExecutablePath: /usr/bin/compiz InstallationDate: Installed on 2014-01-06 (189 days ago) InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) ProcCmdline: compiz Signal: 6 SourcePackage: unity StacktraceTop: __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fd3a4515610 "*** %s ***: %s terminated\n") at ../sysdeps/posix/libc_fatal.c:175 __GI___fortify_fail (msg=) at fortify_fail.c:37 longjmp_chk () at ../sysdeps/unix/sysv/linux/x86_64/longjmp_chk.S:100 __longjmp_chk (env=0x1, val=1) at ../setjmp/longjmp.c:38 ?? () from /usr/lib/x86_64-linux-gnu/libfreetype.so.6 Title: compiz crashed with SIGABRT in __libc_message() UpgradeStatus: Upgraded to utopic on 2014-07-07 (6 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1341625/+subscriptions -- Mailing list: https://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 1329089] Re: g++-4.9 binary incompatibilities with libraries built with g++-4.8
On Mon, Jul 14, 2014 at 08:22:04AM -, Daniel van Vugt wrote: > Why don't we just keep utopic on g++-4.8 until 4.9 is no longer > experimental? 4.9 is not experimental. *C++11 support in gcc upstream* is experimental. There is a single rebuild required here for the move from 4.8 to 4.9, no further rebuilds will be required for ABI changes within gcc 4.9. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1329089 Title: g++-4.9 binary incompatibilities with libraries built with g++-4.8 Status in Mir: Fix Committed Status in “dbus-cpp” package in Ubuntu: In Progress Status in “firefox” package in Ubuntu: New Status in “gcc-4.9” package in Ubuntu: Confirmed Status in “gcc-defaults” package in Ubuntu: Fix Released Status in “location-service” package in Ubuntu: Invalid Status in “mir” package in Ubuntu: Triaged Status in “process-cpp” package in Ubuntu: Invalid Status in “qtbase-opensource-src” package in Ubuntu: New Status in “unity” package in Ubuntu: New Status in “unity-scope-click” package in Ubuntu: New Status in “unity-scopes-api” package in Ubuntu: New Status in “unity-scopes-shell” package in Ubuntu: New Status in Debian GNU/Linux: New Bug description: The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic, when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the default), fails the package build in its test suite. 2/14 Test #2: acceptance_tests ..***Failed 30.54 sec DBus daemon: unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b task-0: Started with PID: 13031 task-0: [==] Running 2 tests from 1 test case. task-0: [--] Global test environment set-up. task-0: [--] 2 tests from LocationServiceStandalone task-0: [ RUN ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of 30 seconds. (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: assertion 'all_tasks(service, all_tasks_finished_helper)' failed task-0: Shutting down DBus daemon: Shutdown This test suite does *not* fail if either dbus-cpp is rebuilt with g++-4.9, or if location-service is built with g++-4.8. This implies a binary compatibility problem for C++ libraries in g++ 4.9, which is critical to resolve. To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1329089/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1339700] Re: [regression] Device locks randomly on welcome screen
** Branch unlinked: lp:~mir-team/mir/fix-1339700-take2-in-0.4 -- 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/1339700 Title: [regression] Device locks randomly on welcome screen Status in Mir: Fix Committed Status in Mir 0.4 series: In Progress Status in “mir” package in Ubuntu: Triaged Status in “unity8” package in Ubuntu: Invalid Bug description: Unity8 welcome screen will occasionally lock. Lock effects: No launcher available Can't swipe left or right Can't drag down indicators Doesn't recover from tapping the power button a couple of times. Randomness: Locks so far have been happening on and off from image U114 The phone seems to lock up for me more on waking from suspend, however rsalveti pointed out that for him it happened on phone hang up. For me the lock happened a couple of times over the weekend images U114 and U115, and then not again till today U122. Manta seems more prone to lock ups that flo or mako. STEPS: (It seems flo has an issue identical when opening settings app) On flo update to U123 1. Once updated, open the settings app This seems to land you in the state described. Apparently this is only a temporary version if you leave the device for a while it will unlock. But I think that is possibly because you are moved away from the app and it is unlocked by the system waking from suspend possibly. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: unity8 7.90+14.10.20140707-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.4-0ubuntu1 Architecture: armhf Date: Wed Jul 9 13:48:14 2014 InstallationDate: Installed on 2014-07-09 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140709-020204) SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mir/+bug/1339700/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308011] Re: SIM unlock UI shifts a half-gridunit when starting and breaks easily
** Changed in: unity8 (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity8 in Ubuntu. https://bugs.launchpad.net/bugs/1308011 Title: SIM unlock UI shifts a half-gridunit when starting and breaks easily Status in The Unity 8 shell: In Progress Status in “unity8” package in Ubuntu: In Progress Bug description: Get examples from lp:unity-notifications, and a few different symptoms can be seen: 1. ./sd-example-simunlock.py → SIM unlock UI shifts a little from the top, potentially related to those messages: file:///usr/share/unity8/Greeter/Lockscreen.qml:71: ReferenceError: backgroundTopMargin is not defined file:///usr/share/unity8/Notifications/Notification.qml:170:9: QML Column: Cannot specify top, bottom, verticalCen ter, fill or centerIn anchors for items inside Column. Column will not function. file:///usr/share/unity8/Notifications/Notification.qml:170:9: QML Column: Cannot specify top, bottom, verticalCen ter, fill or centerIn anchors for items inside Column. Column will not function. 2. ./sd-example-simunlock.py → Ctrl+C → shell is locked with a grey overlay 3. I also saw some real bad lockup with the SIM UI half down the screen... but can't reproduce - will report back if it happens again ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.85+14.04.20140410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 15 13:19:59 2014 SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1308011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1324580] Re: alarm will only ring for a minute and stop whether or not the user interacted with it
** Changed in: ubuntu-clock-app/reboot Importance: High => Critical -- 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/1324580 Title: alarm will only ring for a minute and stop whether or not the user interacted with it Status in Clock application for Ubuntu devices: Confirmed Status in Ubuntu Clock App reboot series: Confirmed Status in “indicator-datetime” package in Ubuntu: Confirmed Bug description: When an alarm goes off, it will ring for only a minute and after that, whether or not the user disabled it, it stays quiet forever more. It would be interesting adding a second or even third ring after the first if the alarm was not properly disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1324580/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 921478] Re: gnome-control-center crashed with SIGABRT in g_assertion_message()
Happend to me too 3 times connecting to my vodafone K3772-Z mobile broadband usb using Ubuntu 14.10 alpha -- 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/921478 Title: gnome-control-center crashed with SIGABRT in g_assertion_message() Status in “network-manager” package in Ubuntu: Confirmed Bug description: WiFi was crashed ProblemType: Crash DistroRelease: Ubuntu 12.04 Package: gnome-control-center 1:3.2.2-2ubuntu3 ProcVersionSignature: Ubuntu 3.2.0-10.18-generic 3.2.1 Uname: Linux 3.2.0-10-generic i686 ApportVersion: 1.91-0ubuntu1 Architecture: i386 CrashCounter: 1 Date: Wed Jan 25 11:52:29 2012 ExecutablePath: /usr/bin/gnome-control-center InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2) ProcCmdline: gnome-control-center Signal: 6 SourcePackage: gnome-control-center StacktraceTop: raise () from /lib/i386-linux-gnu/libc.so.6 abort () from /lib/i386-linux-gnu/libc.so.6 g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0 g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0 nm_utils_security_valid () from /usr/lib/libnm-util.so.2 Title: gnome-control-center crashed with SIGABRT in raise() UpgradeStatus: Upgraded to precise on 2012-01-25 (0 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare usr_lib_gnome-control-center: deja-dup 21.2-0ubuntu4 gnome-bluetooth3.2.1-1ubuntu4 indicator-datetime 0.3.1-0ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/921478/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1336274] Re: HDMI Audio and all other audio disappeared from input sources and output sources in the audio control panel and stereo system is looping between audio is coming and
I fixed it on my end by re-installing Ubuntu from scratch. You should probably look into my logs to find out what could have caused it though. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1336274 Title: HDMI Audio and all other audio disappeared from input sources and output sources in the audio control panel and stereo system is looping between audio is coming and audio is not coming from the computer. Status in “pulseaudio” package in Ubuntu: New Bug description: After I did an update via system update, my system stopped working with audio. I then viewed the audio control panel and non of my output/input sources appear. I'm assuming that a component that Pulse Audio uses has been updated and ether Pulse Audio does not know how to communicate with it, or the component was not tested before being released. I have not changed any of my hardware configurations, so it cannot be a hardware issue. Also using XBMC and I'm guessing XBMC backed down to using ASLA, I am able to set HDMI out (which I had to change from previous configuration which I'm assuming is because Pulse Audio is unable to start) and it works fine until I stop using it for awhile. After I stop using it for awhile, I have to reboot the system to get XBMC working again. The way my stereo system (A Yamaha Receiver) is reacting to this is it's showing it has audio coming from the computer one second, then the other second it doesn't have audio. I'm assuming this is the daemon of Pulse Audio restarting over and over again after it cannot start. I ran pulse audio in verbose mode to show what module is causing it to fail to load, and it is module-systemd-login. The reason it is failing to load is "Failed to create session monitor: No space left on device" but none of my disks are anywhere near being used up, nor is my ram, so I have no idea as to what it could be referring to... Maybe it's referring to space in the audio hardware??? I do not know... I have attached the logs on here. Any help would be useful in getting my audio back, I'm a hacker/developer/all around geek who loves the terminal, so please ask any questions! Please do feel free to email me, I want my audio back! ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: pulseaudio 1:4.0-0ubuntu11 ProcVersionSignature: Ubuntu 3.13.0-30.54-generic 3.13.11.2 Uname: Linux 3.13.0-30-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/pcmC1D2c', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D8p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Tue Jul 1 08:34:09 2014 InstallationDate: Installed on 2014-05-18 (43 days ago) InstallationMedia: It ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/02/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V2.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85-G41 PC Mate(MS-7850) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV2.4:bd12/02/2013:svnMSI:pnMS-7850:pvr1.0:rvnMSI:rnB85-G41PCMate(MS-7850):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.name: MS-7850 dmi.product.version: 1.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1336274/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1323871] Re: Lag when adjusting sound
Same problem
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to indicator-sound in Ubuntu.
https://bugs.launchpad.net/bugs/1323871
Title:
Lag when adjusting sound
Status in “indicator-sound” package in Ubuntu:
Confirmed
Bug description:
When I adjust the volume - either by hovering the cursor over the
indicator and scroling, or by clicking on the indicator and dragging
the widget - the volume will jump up and down rather than smoothly
increasing or decreasing.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: indicator-sound 12.10.2+14.04.20140401-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Uname: Linux 3.13.0-24-generic x86_64
ActionStates: ({'mute': (true, signature '', []), 'phone-settings':
(true, '', []), 'mic-volume': (true, '', [<0.1600189208984375>]), 'scroll':
(true, 'i', []), 'desktop-settings': (true, '', []), 'rhythmbox.desktop':
(true, '', [<{'running': , 'state': <'Paused'>}>]),
'previous.rhythmbox.desktop': (true, '', []), 'volume': (true, 'i',
[<0.5999298095703125>]), 'root': (true, '', [<{'title': <'Sound'>,
'accessible-desc': <'Volume (59%)'>, 'icon': <('themed',
<['audio-volume-medium-panel', 'audio-volume-medium', 'audio-volume',
'audio']>)>, 'visible': }>]), 'play.rhythmbox.desktop': (true, '',
[<'Paused'>]), 'play-playlist.rhythmbox.desktop': (true, 's', []),
'next.rhythmbox.desktop': (true, '', [])},)
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
CurrentDesktop: Unity
Date: Tue May 27 17:35:28 2014
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-02-22 (94 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140221)
SourcePackage: indicator-sound
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1323871/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1307215] Re: destroy-environment fails to clear lxc containers
** Changed in: juju-core Status: New => Triaged -- 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/1307215 Title: destroy-environment fails to clear lxc containers Status in juju-core: Triaged Status in “lxc” package in Ubuntu: New Bug description: Running destroy-environment with --force happily cleans up evan-local- machine-1, but fails to remove 2 or 3. I think this is what led to bug 1303778 for me. % juju destroy-environment local --force WARNING! this command will destroy the "local" environment (type: local) This includes all machines, services, data and other resources. Continue [y/N]? y [sudo] password for evan: ERROR failed to destroy lxc container: error executing "lxc-destroy": lxc_container: Error destroying rootfs for evan-local-machine-2; Destroying evan-local-machine-2 failed ERROR error executing "lxc-destroy": lxc_container: Error destroying rootfs for evan-local-machine-2; Destroying evan-local-machine-2 failed ERROR exit status 1 % sudo lxc-ls -f NAME STATEIPV4 IPV6 AUTOSTART - evan-local-machine-2 STOPPED - - YES evan-local-machine-3 STOPPED - - YES juju-precise-template STOPPED - - NO % juju destroy-environment local --force WARNING! this command will destroy the "local" environment (type: local) This includes all machines, services, data and other resources. Continue [y/N]? y ERROR failed to destroy lxc container: error executing "lxc-destroy": lxc_container: Error destroying rootfs for evan-local-machine-3; Destroying evan-local-machine-3 failed ERROR error executing "lxc-destroy": lxc_container: Error destroying rootfs for evan-local-machine-3; Destroying evan-local-machine-3 failed ERROR exit status 1 % sudo lxc-ls -f NAME STATEIPV4 IPV6 AUTOSTART - evan-local-machine-2 STOPPED - - YES evan-local-machine-3 STOPPED - - YES juju-precise-template STOPPED - - NO % juju destroy-environment local --force WARNING! this command will destroy the "local" environment (type: local) This includes all machines, services, data and other resources. Continue [y/N]? y % sudo lxc-ls -f NAME STATEIPV4 IPV6 AUTOSTART - evan-local-machine-2 STOPPED - - YES evan-local-machine-3 STOPPED - - YES juju-precise-template STOPPED - - NO To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1307215/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1292041] Vacation reply
-- 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/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in “gnome-screensaver” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308011] Re: SIM unlock UI shifts a half-gridunit when starting and breaks easily
** Branch linked: lp:~larsu/qmenumodel/add-nameowner-property -- 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/1308011 Title: SIM unlock UI shifts a half-gridunit when starting and breaks easily Status in The Unity 8 shell: In Progress Status in “unity8” package in Ubuntu: New Bug description: Get examples from lp:unity-notifications, and a few different symptoms can be seen: 1. ./sd-example-simunlock.py → SIM unlock UI shifts a little from the top, potentially related to those messages: file:///usr/share/unity8/Greeter/Lockscreen.qml:71: ReferenceError: backgroundTopMargin is not defined file:///usr/share/unity8/Notifications/Notification.qml:170:9: QML Column: Cannot specify top, bottom, verticalCen ter, fill or centerIn anchors for items inside Column. Column will not function. file:///usr/share/unity8/Notifications/Notification.qml:170:9: QML Column: Cannot specify top, bottom, verticalCen ter, fill or centerIn anchors for items inside Column. Column will not function. 2. ./sd-example-simunlock.py → Ctrl+C → shell is locked with a grey overlay 3. I also saw some real bad lockup with the SIM UI half down the screen... but can't reproduce - will report back if it happens again ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.85+14.04.20140410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 15 13:19:59 2014 SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1308011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
I still have the same problem described at #30. -- 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/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in “gnome-screensaver” package in Ubuntu: Invalid Status in “unity” package in Ubuntu: Fix Released Bug description: The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't trun off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997269] Re: dovecot imap broken by apparmor policy
** Changed in: apparmor (Ubuntu) Status: Expired => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy Status in “apparmor” package in Ubuntu: Incomplete Status in “dovecot” package in Ubuntu: Invalid Status in “apparmor” package in Debian: Confirmed Bug description: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor="ALLOWED" operation="getattr" parent=10922 profile="/usr/sbin/dovecot//null-107 //null-10b//null-118" name="/home/foobar/Maildir/.foobar/dovecot.index.log" pid=10937 comm="imap" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has "flags=(complain)", but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the "usr.lib.dovecot.imap" policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in "complain" mode. What are these "//null-NNN/" strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) --- ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) Package: apparmor 2.7.102-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=7e6df5b7-d31e-4757-a388-f4f477187a63 ro ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Tags: precise Uname: Linux 3.2.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1300957] Re: qmlplugindump running at 100% cpu
This bug was fixed in the package unity-webapps-qml - 0.1+14.10.20140709-0ubuntu1 --- unity-webapps-qml (0.1+14.10.20140709-0ubuntu1) utopic; urgency=low [ Alexandre Abreu ] * Fix issue with qmlplugindump using 100% cpu Fix and expanded AP tests to properly test the installed webapps case (LP: #1300957) -- Ubuntu daily releaseWed, 09 Jul 2014 20:05:56 + ** Changed in: unity-webapps-qml (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-webapps-qml in Ubuntu. https://bugs.launchpad.net/bugs/1300957 Title: qmlplugindump running at 100% cpu Status in Qt Creator plugins for Ubuntu: Confirmed Status in Unity WebApps QML component: New Status in “unity-webapps-qml” package in Ubuntu: Fix Released Bug description: I noticed my fan running, and saw qmlplugindump using 100% I killed qtc and it went away. I had been build and running a simple console app prior to that To manage notifications about this bug go to: https://bugs.launchpad.net/qtcreator-plugin-ubuntu/+bug/1300957/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1308011] Re: SIM unlock UI shifts a half-gridunit when starting and breaks easily
** Branch linked: lp:~macslow/unity-notifications/fix-1308011 -- 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/1308011 Title: SIM unlock UI shifts a half-gridunit when starting and breaks easily Status in The Unity 8 shell: In Progress Status in “unity8” package in Ubuntu: New Bug description: Get examples from lp:unity-notifications, and a few different symptoms can be seen: 1. ./sd-example-simunlock.py → SIM unlock UI shifts a little from the top, potentially related to those messages: file:///usr/share/unity8/Greeter/Lockscreen.qml:71: ReferenceError: backgroundTopMargin is not defined file:///usr/share/unity8/Notifications/Notification.qml:170:9: QML Column: Cannot specify top, bottom, verticalCen ter, fill or centerIn anchors for items inside Column. Column will not function. file:///usr/share/unity8/Notifications/Notification.qml:170:9: QML Column: Cannot specify top, bottom, verticalCen ter, fill or centerIn anchors for items inside Column. Column will not function. 2. ./sd-example-simunlock.py → Ctrl+C → shell is locked with a grey overlay 3. I also saw some real bad lockup with the SIM UI half down the screen... but can't reproduce - will report back if it happens again ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unity8 7.85+14.04.20140410.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu2 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 15 13:19:59 2014 SourcePackage: unity8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/unity8/+bug/1308011/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 997269] Re: dovecot imap broken by apparmor policy
** Changed in: apparmor (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/997269 Title: dovecot imap broken by apparmor policy Status in “apparmor” package in Ubuntu: Expired Status in “dovecot” package in Ubuntu: Invalid Status in “apparmor” package in Debian: Confirmed Bug description: Syslog output: Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fcntl(unlock) locking failed for file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:06 host12 dovecot: imap(foobar): Error: fstat() failed with file /home/foobar/Maildir/dovecot.index.log: No such file or directory Apr 29 10:59:37 dovecot: last message repeated 122 times Apr 29 11:00:38 dovecot: last message repeated 248 times Apr 29 11:01:54 dovecot: last message repeated 203 times audit.log, lots of entries similar to the following: type=AVC msg=audit(1335712674.515:655016): apparmor="ALLOWED" operation="getattr" parent=10922 profile="/usr/sbin/dovecot//null-107 //null-10b//null-118" name="/home/foobar/Maildir/.foobar/dovecot.index.log" pid=10937 comm="imap" requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000 The apparmor policy is as shipped with 12.04. The strange thing here is that audit.log says that the access was allowed and the apparmor policy has "flags=(complain)", but the imap server still fails accessing some files in the Maildir folders. Workaround: # ln -s /etc/apparmor.d/usr.sbin.dovecot /etc/apparmor.d/disable/ After disabling the usr.sbin.dovecot apparmor policy everything works fine. There is no need to disable the "usr.lib.dovecot.imap" policy. It looks like the imap process is incorrectly running under the dovecot main daemon's apparmor profile. And for some odd reason the profile is enforcing things even though it should be in "complain" mode. What are these "//null-NNN/" strings in the logged apparmor profile name? I do not know apparmor well enough to debug this further at this point. Someone else has encountered this also, see thread at: http://comments.gmane.org/gmane.mail.imap.dovecot/60533 ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: dovecot-imapd 1:2.0.19-0ubuntu1 ProcVersionSignature: User Name 3.2.0-24.37-virtual 3.2.14 Uname: Linux 3.2.0-24-virtual x86_64 ApportVersion: 2.0.1-0ubuntu7 Architecture: amd64 Date: Wed May 9 18:36:11 2012 ProcEnviron: SHELL=/bin/bash TERM=screen LANG=en_US.UTF-8 SourcePackage: dovecot UpgradeStatus: Upgraded to precise on 2012-04-27 (12 days ago) --- ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 DistroRelease: Ubuntu 12.04 InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release amd64 (20120424.1) Package: apparmor 2.7.102-0ubuntu3.1 PackageArchitecture: amd64 ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=7e6df5b7-d31e-4757-a388-f4f477187a63 ro ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Tags: precise Uname: Linux 3.2.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/997269/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
